Connect public, paid and private patent data with Google Patents Public Datasets

Systems and methods for direction of communication traffic

Download PDF

Info

Publication number
US20050027882A1
US20050027882A1 US10837614 US83761404A US2005027882A1 US 20050027882 A1 US20050027882 A1 US 20050027882A1 US 10837614 US10837614 US 10837614 US 83761404 A US83761404 A US 83761404A US 2005027882 A1 US2005027882 A1 US 2005027882A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
traffic
internet
address
dns
web
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10837614
Inventor
Alan Sullivan
Mark Lewyn
Phillip Gross
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Paxfire Inc
Original Assignee
Paxfire Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/15Directories; Name-to-address mapping
    • H04L61/1505Directories; Name-to-address mapping involving standard directories or standard directory access protocols
    • H04L61/1511Directories; Name-to-address mapping involving standard directories or standard directory access protocols using domain name system [DNS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12047Directories; name-to-address mapping
    • H04L29/12056Directories; name-to-address mapping involving standard directories and standard directory access protocols
    • H04L29/12066Directories; name-to-address mapping involving standard directories and standard directory access protocols using Domain Name System [DNS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/02Network-specific arrangements or communication protocols supporting networked applications involving the use of web-based technology, e.g. hyper text transfer protocol [HTTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/32Network-specific arrangements or communication protocols supporting networked applications for scheduling or organising the servicing of application requests, e.g. requests for application data transmissions involving the analysis and optimisation of the required network resources
    • H04L67/327Network-specific arrangements or communication protocols supporting networked applications for scheduling or organising the servicing of application requests, e.g. requests for application data transmissions involving the analysis and optimisation of the required network resources whereby the routing of a service request to a node providing the service depends on the content or context of the request, e.g. profile, connectivity status, payload or application type
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32High level architectural aspects of 7-layer open systems interconnection [OSI] type protocol stacks
    • H04L69/322Aspects of intra-layer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329Aspects of intra-layer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer, i.e. layer seven

Abstract

An Internet traffic redirection architecture is disclosed that allows for directing of trash traffic to specified sites. The system or method allows a controller, such as an ISP, to benefit from mistyped Internet addresses so that participating partners of the ISP are presented to the customer when the requests a web site that is not found or does not exist. The system decreases lost traffic by means of capturing unresolved “trash” traffic on the Internet and redirecting said traffic to a search engine partner and/or other partners.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • [0001]
    This application claims the benefit of U.S. Provisional Application No. 60/467,246 filed May 5, 2003, entitled “Traffic redirection system for phones, the web, SMS and instant messaging,” which is incorporated by reference herein in its entirety.
  • BACKGROUND OF THE INVENTION
  • [0002]
    1. Field of the Invention
  • [0003]
    The present invention relates generally to traffic direction within a communications network. More specifically, the present invention relates to systems and methods for directing communication traffic to a specified location when an original location is not reachable.
  • [0004]
    2. Background of the Invention
  • [0005]
    Directing search traffic on the web is a common and lucrative process. For example, popular web browsers, such as Microsoft Internet Explorer, typically redirect misspelled and mistyped web pages on to the web browser's own personal incomplete search page, such as MSN Search. Such search pages provide the user with possible search options and advertising. The essence of the concept is that it captures the mistyped or misspelled traffic at either the browser level or application level. These methods lack the capability to function at the DNS level thus limiting their overall functionality and ability to be able to provide business services.
  • [0006]
    Various methods of routing or redirecting traffic are known in the art. For example, methods of routing traffic are taught within U.S. Pat. No. 6,631,402. Methods of redirecting or routing of data traffic are taught within U.S. Pat. No. 6,608,893, U.S. Pat. No. 5,933,490, U.S. Pat. No. 6,205,477, and patent application publication U.S. 2004/0042447 A1. Methods of routing error corrections are taught within U.S. Pat. No. 6,601,208. Routing methods for load balancing are taught within U.S. Pat. No. 6,182,139 and U.S. Pat. No. 5,774,660. Internet traffic routing is taught within U.S. Pat. No. 5,987,611. Methods for dealing with invalid requests are taught within patent application publication U.S. 2004/0030780 A1.
  • [0007]
    Likewise, methods of marketing and traffic selling are known. For example, such methods are taught within patent application publication U.S. 2004/0044566 A1. URL (uniform resource locator) redirect methods are taught within patent application publication U.S. 2004/004622 A1. DNS (domain name server/service) resource lookup methods are taught within patent application publication U.S. 2004/0044791 A1. Methods of implementing a web-based proxy are taught within U.S. Pat. No. 6,631,402.
  • [0008]
    Although there are numerous drawbacks to the systems and methods currently available, a drawback of conventional redirect methods is that they lack the ability to perform service task at the DNS level of operation, thus limiting the functionality and capability of such methods.
  • [0009]
    Furthermore conventional redirect methods are diminished in capacity due to the level at which these elements operate within the Internet infrastructure or Internet architecture, thus limiting the ability of conventional redirect methods in conducting reliable business services, such as payment processing, e-commerce, ENUM, IP telephony, VoIP, filtering, security, URL forwarding, and associated tracking methods, such as market channel tracking, webpage usages, DNS statistics, traffic redirection, and information storage or backup.
  • [0010]
    Thus there is a need in the art for a method of traffic direction or redirection that is not limited in the level at which it is able to function and allows for conducting reliable business services and associated tracking methods.
  • SUMMARY OF THE INVENTION
  • [0011]
    The present invention provides systems and methods for redirection of improper or incorrect requests. The system and methods redirect such requests to a proxy host, which analyzes the erroneous request and provides a context-relevant search result rather than an error message. The methods and systems reside at the service provider level (i.e., at the DNS or ISP level) rather than the user level.
  • [0012]
    The present invention accordingly provides systems and methods for conducting business using computers. The systems and methods include identifying queries containing errors and redirecting these erroneous queries to web pages that contain relevant information, which can be provided by advertisers who pay the ISP or DNS operator for inclusion of their content on the redirect web page.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0013]
    FIG. 1 shows a request and response generated in accordance with an exemplary embodiment of the invention with no traffic direction initiated.
  • [0014]
    FIG. 2 shows an exemplary implementation of controls used to implement the direction method when a malformed request is initiated.
  • [0015]
    FIG. 3 shows an implementation of controls used to implement the direction method in accordance with an exemplary embodiment of the present invention wherein a spoof request is initiated.
  • [0016]
    FIG. 4 shows an implementation of controls used to implement the direction method in accordance with an exemplary embodiment of the present invention wherein a response to the spoof request is supplied to the customer.
  • [0017]
    FIG. 5 shows an implementation of controls used to implement the direction method in accordance with the invention wherein the use of local plug-ins is initiated.
  • [0018]
    FIG. 6 shows an implementation of the direction method in accordance with an exemplary embodiment of the present invention wherein two components of the invention, the Lookup Proxy (PLP) and the Search Profiler (PSP), exchange information and control data.
  • [0019]
    FIG. 7 shows an implementation of the overall architecture used to implement the direction system and method in accordance with an exemplary embodiment of the present invention.
  • DETAILED DESCRIPTION OF THE INVENTION
  • [0020]
    The Internet provides a user a quick and efficient direction to a particular web site if the user knows the exact web site address. The majority of Internet users properly type in the exact address of the web site that they are seeking and thus are directed to such sites. However, a user will quite often type in an address that is not recognized, thereby leading the user to an error page or a specific search engine page. Such undesired direction of the user is considered as unwanted, unused or unresolved traffic. Another popular name for URL addresses that lead to no proper destination is “trash traffic.”
  • [0021]
    The present invention offers a recycling solution to trash traffic by directing such trash traffic to a particular predetermined location. Such predetermined location may be a search engine or an advertising page or some combination of both or other page that allows the controller to benefit from the redirection of the user traffic. Such a controller may be, for example, an ISP. The limitations and difficulties in the current state of the art in the area of redirecting network traffic are addressed by the present invention, which reside in the systems and methods for the direction of trash traffic and resulting production of capital for various applications.
  • [0022]
    The systems and methods according to the present invention are suitable for use in any computer-driven communications system, such as Internet systems and telephony. As such, the present methods and systems can be implemented at the DNS or ISP level.
  • [0023]
    The exemplary systems and methods according to the present invention will provide a more robust experience for the Internet user allowing the local computer to conduct other tasks. As providers of DNS service begin redirecting more traffic away from browser providers, they will look for the “IP address of the redirect host” that is being returned through the DNS, or domain name system. Once the DNS service providers know that information, they will replace that IP address with their own redirect host. This will enable them to recapture the traffic. The invention as described herein provides a way to eliminate the need to redirect lost or trash traffic at the application level but to do so at the DNS level. This will eliminate companies from being able to filter a single IP address because multiple IP addresses will be returned from a pool of IP addresses from network of machines.
  • [0024]
    An issue in Internet traffic redirection design is the communications between the customer and ISP. Conventional systems and methods are relatively inflexible with respect to the manner in which they generate the required code transfers for such rerouting or redirecting of Internet traffic at the DNS level of operation.
  • [0025]
    Exemplary systems and methods in accordance with the present invention are accomplished by incorporating the use of a unique means of traffic direction or redirection, being used synonymously herein and through this application, wherein the use of DNS level protocols is applied in a manner that creates advantages over conventional redirect systems. This is accomplished by integrating redirection instruction software, labeled as Lookup Proxy (“PLP”), within the ISP server machines wherein lost traffic is thus converted into profit for the ISPs through direction of traffic to a predetermined web site. Such profits may be distributed through participating partners and/or stored for later use in an online account when the customer can take action, thus increasing the overall efficiency of the monetary exchange system and adding stability and safety to the customers funds.
  • [0026]
    Moreover, it has been discovered that other features present have applications to reduce computer usage at the customer level by using the infrastructure in such a way that when a query occurs, there is minimal impact upon the end user and greatly minimized computer usage required by the end customer thus improving the efficient use of the Internet infrastructure. There is an added benefit in that when the query is initiated there is a seamless integration with the entire network.
  • [0027]
    Although the present disclosure is directed to Internet trash traffic as an example, the present invention is not limited to this exemplary embodiment. Other communication direction is also within the purview of the present invention. For example, in an exemplary embodiment of the present invention as applied to the field of telephony, unused traffic might be a misdialed phone number that may then be redirected to a telemarketer or other location or for other services, such as a directory function. In the area of Instant Messaging (“IM”), unused traffic may be generated, for example, by someone who typed in an incorrect “screen name.” That mistyped screen may then be redirected to an advertiser who might flash up a message and/or link or to another location or for other services, such as a directory function.
  • [0028]
    If processed correctly, unwanted, unused and/or unresolved traffic would be a very valuable business resource to those seeking such traffic. Indeed, many Internet registries and corporate web sites are unaware that they possess this valuable business asset. Today, they view this traffic as the World Wide Web equivalent of “trash.” But, as with many industries, “trash” can often be recycled and turned into new products. One way to do that is by means of directing such unwanted, unused and/or unresolved traffic.
  • [0029]
    The systems and methods for which traffic can be identified as “unwanted,” “unused” or “unresolved” within the World Wide Web may be accomplished by several means which will be described herein.
  • [0030]
    At the DNS level of the Internet infrastructure, a registry, such as, for example, VeriSign, would look at the internet traffic by considering what the customer has typed into the web browser and then see if there is a domain name associated with what the customer has typed in. If there is no such domain name, then the traffic would be classified as “unresolved” and made available to be redirected wherein such a system or method could be implemented at the ISP level and/or web browser level.
  • [0031]
    Corporate web sites could identify traffic as unwanted through a number of means. A corporate web site, for instance, may define traffic from overseas as “unwanted” if it were not profitable to ship overseas. Thus, one could identify if the traffic came from overseas by analyzing the IP address. Alternatively, a web site owner might only want traffic at certain times, and not at other times and/or geographic location. Thus, such traffic could be sorted by time and/or geographic location wherein such specified portions could be identified and made available as redirected traffic.
  • [0032]
    In the area of telephony, unwanted telephone traffic might take the form of a misdialed phone number or a misdirected Internet call. Or, perhaps, the person typed in the right telephone number, but there is no person associated with that number or they may no longer work there or have a different phone number. In either case, that piece of telephone traffic could be redirected, perhaps to a telemarketer or to someone within the company that the person is trying to contact, or an outside company to where the person may have transferred. Other options are also possible.
  • [0033]
    In the instant messaging (IM) world, an “unresolved” piece of traffic would be, for example, a piece of traffic for which there is no screen name associated such as when a customer types in a screen name that doesn't exist. If it cannot be resolved in the IM database, then the traffic is identified as unresolved and thus may be redirected, and a marketing message and/or website link can be delivered to the consumer.
  • [0034]
    As shown and described, many possible examples exist for the directing or redirecting of electronic communication signals that are not able to find their intended targets. Although many such forms exist, with non-limiting examples being described above in terms of internet traffic, telephone calls and the like, the examples described herein are provided with respect to lost Internet traffic for sake of simplicity. However, the concepts and architecture is the same with other forms of electronic communication and thus the present invention has a scope that encompasses all electronic communication, beyond that for lost Internet traffic as described in the following series of figures.
  • [0035]
    An exemplary embodiment of the present invention is shown in FIG. 1, wherein a system or method of the DNS Proxy (PLP) is shown in the example where an Internet address is properly types in and located. As is illustrated, an ISP customer sends a request 1 for an IP address lookup to the PLP, which then relays a message 2 to the ISP DNS. The DNS collects the necessary statistics relating to the specific Internet address requested by the user and returns 3 the IP address requested with a domain name that is resolved to the PLP. The PLP returns 4 the requested IP address to the ISP customer. In such a system or method, the DNS proxy will collect information and statistics about all DNS requests made to the ISP DNS thus building a database for said system and method.
  • [0036]
    However, as is often the case, an Internet user does not properly type in a desired Internet address. FIG. 2. shows an example of a malformed DNS request in which a redirect IP address is returned from the nearest PSP node. The ISP customer makes a malformed request for an address lookup 1. The PLP relays 2 the malformed request to the ISP DNS and collects statistical data in a data base then the ISP DNS returns 3 an error such as “no such address.” Then the PLP returns 4 an IP address of the nearest PSP such that the ISP customer receives a redirect IP address to this request instead of a DNS error of “no such address.”
  • [0037]
    Following the sequences shown in FIG. 2 are a series of events according to the present invention, as shown in FIG. 3. This is an example of the events after the customer receives the redirect IP address from the nearest PSP node. After a malformed DNS request 1,2, the customer will use the redirect IP address 3,4 to send 5 a web request to a PSP node which acts as a web server. The PSP web server will dynamically create 6 a web landing page with a search bar included in the landing page wherein the web landing page will be returned to the customer. In the usual case, the customer will be assured of sending only web requests to the PSP by actions of the browser plug-in, referred to as the Search Manager (PSM). However, if the customer is not using the PSM, or if for any other reason a non-web request is sent to a PSP, the PSP will filter out the non-web traffic and return an error response appropriate for the request.
  • [0038]
    Based on the type of inquiry that is being made, FIG. 4 shows how the PSP will return customer specific content based upon the profile stored for that customer or ISP. The participating partner, which could be an advertising partner or search engine partner, returns 7 content for the specific customer. This can be done through a common API to the advertisers or search engines. The PSP builds 8 and sends a launch page with content from advertising partner or search engine. This launch page is built in real time based upon profile information stored for the ISP or based upon the IP address of the requestor. The IP address may be used to localize the requestor all the way down to a known individual user.
  • [0039]
    FIG. 5. shows how the ISP uses a web browser to communicate with the PLP DNS proxy for the purpose of configuring and managing the DNS proxy 3 and the status of the PLP DNS proxy is returned 4. The customer uses a browser plug-in 1 for being redirected by the PLP directly from the browser 2. The web browser also allows the ISP to configure other components including the ISP profile contained at the PSP. The customer uses a browser plug-in 1 for being redirected by the PLP directly from the browser 2. The browser plug-in is optional and can be used for either an opt-in or opt-out of the redirect function.
  • [0040]
    In order to keep its records continuously updated, FIG. 6 shows how the PSP provides a mechanism for communicating with the PLP DNS proxy and the PLP DNS proxy platform 1,2. This may be used for updates 1,2 and self-coordination between the PLP and PSP 1,2. This update may be initiated by the PSP or PLP, automatically or initiated by the PLP or PSP. The updates further may be module, software, or data updates. They may also be used to deploy new PLP service modules. The data that the PSP provides to the PLP includes the IP address which is to be returned when an unresolved domain name request is made.
  • [0041]
    As shown in the exemplary sequences of FIGS. 1-6, the ISP information directing methods and systems according to the present invention involve a number of components. FIG. 7 is a description of the components of the PLP platform and an individual PSP platform. A key aspect of the PLP/PSP/PSM architecture is that the PLP is a general purpose software engine which can also run other software modules to deliver other services at this infrastructure level.
  • [0042]
    DNS Proxy intercepts DNS requests at port 53 and passes on those requests to the DNS of the ISP. If an error is returned by the DNS, the DNS proxy will return an IP address of the PSP node.
  • [0043]
    The PSN protocol module is what communicates between the PLP and PSP. This allows real-time data updates between the PLP and PSP. The PLP can send information, such as, for example, DNS stats, status, information about the owner of IP addresses, status and information from additional service modules. The PSN can add new servers modules to the PLP, can update the PLP software, can return response to queries, can return the IP addresses to be returned in place of error messages from the DNS.
  • [0044]
    The DNS Stats module collects statistics about the DNS requests and status of the requests. It can collect those stats or send that information to the PSP via the PSN protocol module. Additional services modules can be added to the PLP. The PSP Request Handler handles the request from ISP customers when they are directed to an error landing page. The request handler employs the Port Filter to filter out any non-HTTP protocol or other port requests other than HTTP. The Profiler is used to define the look and feel and layout of a landing page. It can contain profile information about the ISP or the customer. The Page Builder module builds the PSP landing page in real-time in response to the profile of either the user, the ISP, or both that are stored in the Profiler.
  • [0045]
    For example, an integral component, which will run as a module in the general purpose software engine, is the collection and analysis of DNS and other traffic. This opens opportunities to partner with researchers and ISP's to study Internet performance. With the PLP/PSP/PSM technology widely distributed at participating ISP's, the general purpose software engine of the PLP architecture will make it possible to deliver additional services such as “DNS forwarding” for known changes to DNS names, “URL filtering” to control access to undesirable web sites, detection and diagnosis of DDOS attacks, and detection and diagnosis of Spam sources.
  • [0046]
    A failed-lookup service is useful to customers. Customers will be given appropriate controls (e.g., opt-out feature). The technical model shown and described assures other applications work as expected. The model creates opportunities for other useful services for customers. This model creates a network uniquely positioned to instrument and study Internet performance dynamics. It is not a rigidly enforced mechanism and offers complete choice to the user; ISP's can participate without redirection (e.g., for other services) or ISP customers have choice to opt-out. The options are in place for both the customer and the ISP.
  • [0047]
    In a preferred embodiment, for simple traffic redirection, the system can identify a piece of unwanted, unused or unresolved traffic and point it to a particular location, such as a search engine and/or any IP address and/or any IP address of a web server and/or any IP address of any server for any port or protocol. Other options are also possible and are left to the controller of the system and method as described herein.
  • [0048]
    In a preferred embodiment for use with traffic direction and processing, the traffic is processed before it is redirected. Such processing may, for example, include identifying or approximating the location and/or demographics of the entity that initiated the traffic. This may be accomplished, for example, using geo-location and/or demographic analysis. The IP address of the requestor may be discovered ahead of time by any ISP that delegates either a static IP address or uses a dynamic means such as DHCP to delegate an IP address to a particular user. When the secondary request is made, for example another web landing page, the identity of the user can then be determined by the IP address of the requester to bind a particular DNS request with a particular requester.
  • [0049]
    In another exemplary embodiment, traffic is offered on an exchange that would allow potential buyers to bid on the traffic before it is redirected. This embodiment can involve simple traffic redirection, in which case the traffic can be sold on an individual basis or in bulk, for example. Alternatively, this embodiment can involve a processing step allowing the traffic to be classified by one or more criteria such as geographic location and/or demographics for the purpose of selling the traffic to parties interested in receiving such traffic from a particular location and/or demographic.
  • [0050]
    A variety of different systems and methods may be employed within the scope of the present invention to both identify unwanted, unused or unresolved traffic and to redirect such traffic, once identified as such.
  • [0051]
    Exemplary systems and methods according to the present invention have a variety of industrial and corporate uses. In one non-limiting example in the corporate arena, World Wide Web merchants receive a significant amount of traffic that they do not want or need. For instance, any traffic a merchant received from overseas is worthless to him if it's unprofitable or illegal for that merchant to ship its product overseas. Another use area includes World Wide Web registries, which help direct traffic from a customer to its final destination on the World Wide Web, which frequently cannot figure out where to send a unit of traffic. This traffic may be classified as unresolved traffic. This happens billions of times a day on the World Wide Web.
  • [0052]
    In one non-limiting every day example, an average Internet user who is seeking out a dentist with a distinct web address may accidentally type in the wrong address. The exemplary systems and methods of the present invention may then determine that the wrong address is a result of the user's interest in seeking out a dentist. An advantage of the present invention is that the exemplary system then determines the general location of the computer of the user, for example through zip code. Then the exemplary system does a search of all dentists in its participating (advertising) partner database to determine which are available in the zip code of the particular user. The system then presents the user with a web page of information that relate to dentists in the same zip code. Although the user types in the wrong email address relating to a particular dentist, the ISP provider was able to provide the user with a list of dentists in the user's area. This service is beneficial for the user who is seeking a dentist (and may have been seeking one who is closer or more economical), the ISP provider (who gains from the advertising costs), and the dentist (who has paid for advertising to the ISP and is now having customers directed to him).
  • [0053]
    Other similar examples are limitless and within the scope of the present invention. For example, misdialed telephone calls may operate under the same structure, providing the caller with additional options other than the party that the caller had intended to call (but whose number the caller misdialed).
  • [0054]
    Yet another example involves broken links. There are literally billions of links on the web that are “broken,” meaning that when a consumer clicks on the link, he doesn't end up where he intended, but, rather, on an “error” page. These broken links can be collected and then the traffic they generate can be redirected to another place, perhaps a related page.
  • [0055]
    Yet another example includes parked domains. “Parked” domains are domains that have been registered by a consumer or business, but for which there is no web site attached by the registered owner of that domain. These parked domains are typically maintained by the “Registrars” that sold the domain. Even though there is no website attached to these domains, they still generate traffic. This traffic can be redirected to another place.
  • [0056]
    Many other uses are possible. These include:
      • (1) the instant after a query is made. Redirecting traffic from one supplier of traffic to one buyer of traffic. This may be called “one-to-one” business system;
      • (2) redirecting traffic from one supplier to many buyers. This may be called “one to many” business system;
      • (3) redirecting traffic from many suppliers to many buyers of traffic. This may be called “many to many” business system;
      • (4) any combination of the above embodiments may be used in addition to that of current systems currently used, thus aiding the usefulness of current system as well as reducing the associated maintenance cost by reducing the rate of misguided request.
  • [0061]
    Further advantages of the invention are to reduce overhead usage of the components involved in the end users computer system, add stability to the internet infrastructure structure, and increase reliability, while reducing the needed maintenance associated with current internet redirect systems. An advantage of the exemplary embodiments of the present invention is that they provide means for recovering unresolved traffic and converting such traffic into monies for the ISP's and/or participating business partners. Another result of exemplary embodiments of the invention is to provide a system or method for Internet traffic redirection, which permits a myriad of services to be implemented to the customer directly through the ISP and/or participating partner.
  • [0062]
    The foregoing disclosure of the preferred embodiments of the present invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many variations and modifications of the embodiments described herein will be apparent to one of ordinary skill in the art in light of the above disclosure. For example, the principles of the invention in their broader aspects may be applied to other network systems such as for telephony. The scope of the invention is to be defined only by the claims appended hereto, and by their equivalents.
  • [0063]
    Further, in describing representative embodiments of the present invention, the specification may have presented the method and/or process of the present invention as a particular sequence of steps. However, to the extent that the method or process does not rely on the particular order of steps set forth herein, the method or process should not be limited to the particular sequence of steps described. As one of ordinary skill in the art would appreciate, other sequences of steps may be possible. Therefore, the particular order of the steps set forth in the specification should not be construed as limitations on the claims. In addition, the claims directed to the method and/or process of the present invention should not be limited to the performance of their steps in the order written, and one skilled in the art can readily appreciate that the sequences may be varied and still remain within the spirit and scope of the present invention.

Claims (20)

1. A method for directing communication, the method comprising:
receiving a request from an Internet user for a specific address;
relaying the request to an ISP DNS to determine its location;
responding to the request by providing an Internet address when the requested Internet address is located;
directing the Internet user to a predetermined search network when the requested Internet address is not located;
choosing at least one appropriate target through the search network and sending a request for information from that target; and
providing a result page to the Internet user, the result page being a culmination of information received from the at least one target.
2. The method of claim, wherein the request is for a telephone number of a designated callee.
3. The method of claim 1 wherein a DNS based proxy intercepts the request at a name level to return a contrived IP address in general and a web server IP address in particular for a web server landing page in place of an unresolved domain name request.
4. The method of claim 1, wherein the targets are predetermined partners and associated with the ISP DNS.
5. The method of claim 1, wherein all steps occur within an Internet structure.
6. The method of claim 1, wherein the Internet user may opt-out of failed lookup redirection.
7. A system for directing communication, the method comprising:
means for receiving a request from an Internet user for a specific Internet address;
means for relaying the request to an ISP DNS to determine its location;
means for responding to the request by providing an Internet address location when the requested Internet address is located;
means for directing the Internet user to a predetermined search network when the requested Internet address is not located;
means for choosing at least one appropriate target and sending a request for information from that target; and
means for providing a result page to the Internet user, the result page being a culmination of information received from the at least one target.
8. The system of claim 7, wherein the request is for a telephone number of a designated callee.
9. The system of claim 7 wherein a DNS based proxy intercepts the request at a name level to return a contrived IP address in general and a web server IP address in particular for a web server landing page in place of an unresolved domain name request.
10. The system of claim 7, wherein the targets are predetermined partners and associated with the ISP DNS.
11. The system of claim 7, wherein all steps occur within an Internet structure.
12. The system of claim 7, wherein the Internet user may opt-out of failed lookup redirection.
13. A method for directing communication, the method comprising:
sending a request from an Internet user for a specific Internet address;
relaying the request to an ISP DNS to determine its location;
responding to the request by providing an Internet address location when the requested Internet address is located;
directing the Internet user to a predetermined search network when the requested Internet address is not located;
choosing at least one appropriate target and sending a request for information from that target; and
receiving a result page to the Internet user, the result page being a culmination of information received from the at least one or more targets.
14. The method of claim 13 wherein the request is for a telephone number of a designated callee.
15. The method of claim 13 wherein the combination of redirect system (PLP, PSP) with an optional browser plug-in system (PSM) is used within the redirect system and the system operates on a DNS based proxy to intercept the request at the name level to return a contrived IP address in general and a web server IP address in particular for a web server landing page in place of an unresolved domain name request.
16. The method of claim 13, wherein the targets are predetermined partners and associated with the ISP DNS.
17. The method of claim 13, wherein all steps occur within an Internet structure.
18. The method of claim 13, wherein the Internet user may opt-out of failed lookup redirection.
19. The method of claim 13, wherein an accounting is made of the number of times that the target is presented to different Internet users.
20. The method of claim 13, wherein an ISP maintains control over the steps described.
US10837614 2003-05-05 2004-05-04 Systems and methods for direction of communication traffic Abandoned US20050027882A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US46724603 true 2003-05-05 2003-05-05
US10837614 US20050027882A1 (en) 2003-05-05 2004-05-04 Systems and methods for direction of communication traffic

Applications Claiming Priority (14)

Application Number Priority Date Filing Date Title
US10837614 US20050027882A1 (en) 2003-05-05 2004-05-04 Systems and methods for direction of communication traffic
US11019369 US20050105513A1 (en) 2002-10-27 2004-12-23 Systems and methods for direction of communication traffic
PCT/US2005/015381 WO2005109226B1 (en) 2004-05-04 2005-05-04 Systems and methods for direction of communication traffic
CA 2565776 CA2565776A1 (en) 2004-05-04 2005-05-04 Systems and methods for direction of communication traffic
JP2007511511A JP4762231B2 (en) 2004-05-04 2005-05-04 System and method for Direction of communication traffic
EP20050744498 EP1756732A2 (en) 2004-05-04 2005-05-04 Systems and methods for direction of communication traffic
US11568631 US20070291739A1 (en) 2004-05-04 2005-05-04 Systems and Methods for Direction of Communication Traffic
CN 200580022490 CN1981284A (en) 2004-05-04 2005-05-04 Systems and methods for direction of communication traffic
US11555386 US7631101B2 (en) 2003-05-05 2006-11-01 Systems and methods for direction of communication traffic
US11556235 US20070038755A1 (en) 2002-10-27 2006-11-03 Systems and methods for direction of communication traffic
US12697261 US20100138559A1 (en) 2003-05-05 2010-01-31 Systems and methods for direction of communication traffic
US12947400 US20110066724A1 (en) 2002-10-27 2010-11-16 Systems and methods for direction of communication traffic
US12947339 US20110066716A1 (en) 2002-10-27 2010-11-16 Systems and methods for direction of communication traffic
US12954042 US20110072124A1 (en) 2003-05-05 2010-11-24 Systems and methods for direction of communication traffic

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10065529 Continuation-In-Part US7310686B2 (en) 2002-10-27 2002-10-27 Apparatus and method for transparent selection of an Internet server based on geographic location of a user

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US11019369 Continuation-In-Part US20050105513A1 (en) 2002-10-27 2004-12-23 Systems and methods for direction of communication traffic

Publications (1)

Publication Number Publication Date
US20050027882A1 true true US20050027882A1 (en) 2005-02-03

Family

ID=46205210

Family Applications (4)

Application Number Title Priority Date Filing Date
US10837614 Abandoned US20050027882A1 (en) 2003-05-05 2004-05-04 Systems and methods for direction of communication traffic
US11555386 Expired - Fee Related US7631101B2 (en) 2003-05-05 2006-11-01 Systems and methods for direction of communication traffic
US12697261 Abandoned US20100138559A1 (en) 2003-05-05 2010-01-31 Systems and methods for direction of communication traffic
US12954042 Abandoned US20110072124A1 (en) 2003-05-05 2010-11-24 Systems and methods for direction of communication traffic

Family Applications After (3)

Application Number Title Priority Date Filing Date
US11555386 Expired - Fee Related US7631101B2 (en) 2003-05-05 2006-11-01 Systems and methods for direction of communication traffic
US12697261 Abandoned US20100138559A1 (en) 2003-05-05 2010-01-31 Systems and methods for direction of communication traffic
US12954042 Abandoned US20110072124A1 (en) 2003-05-05 2010-11-24 Systems and methods for direction of communication traffic

Country Status (1)

Country Link
US (4) US20050027882A1 (en)

Cited By (72)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040254926A1 (en) * 2001-11-01 2004-12-16 Verisign, Inc. Method and system for processing query messages over a network
US20060004710A1 (en) * 2004-06-16 2006-01-05 Veritas Operating Corporation System and method for directing query traffic
US20070067416A1 (en) * 2005-09-16 2007-03-22 Advanced Digital Broadcast S. A. Method for referencing remote element of content, method for providing content with remote elements and system for distributing content
WO2007087390A2 (en) * 2006-01-23 2007-08-02 Intersearch Group, Inc. System and method for redirecting internet traffic
US20070260518A1 (en) * 2005-09-16 2007-11-08 Ofer Ronen Electronic marketplace used to lease domain names and redirect web surfers from leased domain names
US20080155694A1 (en) * 2005-07-08 2008-06-26 Kt Corporation Malignant bot confrontation method and its system
US20080189192A1 (en) * 2005-09-16 2008-08-07 Ofer Ronen Domain name marketplace
US20090043855A1 (en) * 2007-08-08 2009-02-12 Blake Bookstaff System for providing information to originator of misdirected email
US20090327098A1 (en) * 2005-09-16 2009-12-31 Sendori, Inc. Enhancements for domain name leasing marketplace
US7805379B1 (en) * 2007-12-18 2010-09-28 Amazon Technologies, Inc. Method and system for leasing or purchasing domain names
US20100318858A1 (en) * 2009-06-15 2010-12-16 Verisign, Inc. Method and system for auditing transaction data from database operations
US20110022678A1 (en) * 2009-07-27 2011-01-27 Verisign, Inc. Method and system for data logging and analysis
US20110047292A1 (en) * 2009-08-18 2011-02-24 Verisign, Inc. Method and system for intelligent routing of requests over epp
US20120089712A1 (en) * 2010-10-12 2012-04-12 Apple Inc. Systems and methods for providing network resource address management
US8159352B2 (en) 2007-09-11 2012-04-17 Colgate-Palmolive Company Personal care implement having a display
US8175098B2 (en) 2009-08-27 2012-05-08 Verisign, Inc. Method for optimizing a route cache
US8527945B2 (en) 2009-05-07 2013-09-03 Verisign, Inc. Method and system for integrating multiple scripts
US20140289319A1 (en) * 2009-03-27 2014-09-25 Amazon Technologies, Inc. Request routing using popularity information
US8856344B2 (en) 2009-08-18 2014-10-07 Verisign, Inc. Method and system for intelligent many-to-many service routing over EPP
US8982882B2 (en) 2009-11-09 2015-03-17 Verisign, Inc. Method and system for application level load balancing in a publish/subscribe message architecture
US9021129B2 (en) 2007-06-29 2015-04-28 Amazon Technologies, Inc. Request routing utilizing client location information
US9021128B2 (en) 2008-06-30 2015-04-28 Amazon Technologies, Inc. Request routing using network computing components
US9021127B2 (en) 2007-06-29 2015-04-28 Amazon Technologies, Inc. Updating routing information based on client location
US9047589B2 (en) 2009-10-30 2015-06-02 Verisign, Inc. Hierarchical publish and subscribe system
US9083743B1 (en) 2012-03-21 2015-07-14 Amazon Technologies, Inc. Managing request routing information utilizing performance information
US9106701B2 (en) 2010-09-28 2015-08-11 Amazon Technologies, Inc. Request routing management based on network components
US9130756B2 (en) 2009-09-04 2015-09-08 Amazon Technologies, Inc. Managing secure content in a content delivery network
US9135048B2 (en) 2012-09-20 2015-09-15 Amazon Technologies, Inc. Automated profiling of resource usage
US9154551B1 (en) 2012-06-11 2015-10-06 Amazon Technologies, Inc. Processing DNS queries to identify pre-processing information
US9160703B2 (en) 2010-09-28 2015-10-13 Amazon Technologies, Inc. Request routing management based on network components
US9176894B2 (en) 2009-06-16 2015-11-03 Amazon Technologies, Inc. Managing resources using resource expiration data
US9185012B2 (en) 2010-09-28 2015-11-10 Amazon Technologies, Inc. Latency measurement in resource requests
US9191338B2 (en) 2010-09-28 2015-11-17 Amazon Technologies, Inc. Request routing in a networked environment
US9210235B2 (en) 2008-03-31 2015-12-08 Amazon Technologies, Inc. Client side cache management
US9208097B2 (en) 2008-03-31 2015-12-08 Amazon Technologies, Inc. Cache optimization
US9237114B2 (en) 2009-03-27 2016-01-12 Amazon Technologies, Inc. Managing resources in resource cache components
US9235829B2 (en) 2009-10-30 2016-01-12 Verisign, Inc. Hierarchical publish/subscribe system
US9246776B2 (en) 2009-10-02 2016-01-26 Amazon Technologies, Inc. Forward-based resource delivery network management techniques
US9253065B2 (en) 2010-09-28 2016-02-02 Amazon Technologies, Inc. Latency measurement in resource requests
US9251112B2 (en) 2008-11-17 2016-02-02 Amazon Technologies, Inc. Managing content delivery network service providers
US9269080B2 (en) 2009-10-30 2016-02-23 Verisign, Inc. Hierarchical publish/subscribe system
US9294391B1 (en) 2013-06-04 2016-03-22 Amazon Technologies, Inc. Managing network computing components utilizing request routing
US9292612B2 (en) 2009-04-22 2016-03-22 Verisign, Inc. Internet profile service
US9323577B2 (en) 2012-09-20 2016-04-26 Amazon Technologies, Inc. Automated profiling of resource usage
US9332078B2 (en) 2008-03-31 2016-05-03 Amazon Technologies, Inc. Locality based content distribution
US9391949B1 (en) 2010-12-03 2016-07-12 Amazon Technologies, Inc. Request routing processing
US9407681B1 (en) 2010-09-28 2016-08-02 Amazon Technologies, Inc. Latency measurement in resource requests
US9407699B2 (en) 2008-03-31 2016-08-02 Amazon Technologies, Inc. Content management
US9444759B2 (en) 2008-11-17 2016-09-13 Amazon Technologies, Inc. Service provider registration by a content broker
US9451046B2 (en) 2008-11-17 2016-09-20 Amazon Technologies, Inc. Managing CDN registration by a storage provider
US9479476B2 (en) 2008-03-31 2016-10-25 Amazon Technologies, Inc. Processing of DNS queries
US9495338B1 (en) 2010-01-28 2016-11-15 Amazon Technologies, Inc. Content distribution network
US9497259B1 (en) 2010-09-28 2016-11-15 Amazon Technologies, Inc. Point of presence management in request routing
US9515949B2 (en) 2008-11-17 2016-12-06 Amazon Technologies, Inc. Managing content delivery network service providers
US9525659B1 (en) 2012-09-04 2016-12-20 Amazon Technologies, Inc. Request routing utilizing point of presence load information
US9531581B1 (en) 2007-12-18 2016-12-27 Amazon Technologies, Inc. Method and system for identifying and automatically registering domain names
US9544394B2 (en) 2008-03-31 2017-01-10 Amazon Technologies, Inc. Network resource identification
US9569753B2 (en) 2009-10-30 2017-02-14 Verisign, Inc. Hierarchical publish/subscribe system performed by multiple central relays
US9571389B2 (en) 2008-03-31 2017-02-14 Amazon Technologies, Inc. Request routing based on class
US9628554B2 (en) 2012-02-10 2017-04-18 Amazon Technologies, Inc. Dynamic content delivery
US9712484B1 (en) 2010-09-28 2017-07-18 Amazon Technologies, Inc. Managing request routing information utilizing client identifiers
US9734472B2 (en) 2008-11-17 2017-08-15 Amazon Technologies, Inc. Request routing utilizing cost information
US9742795B1 (en) 2015-09-24 2017-08-22 Amazon Technologies, Inc. Mitigating network attacks
US9762405B2 (en) 2009-10-30 2017-09-12 Verisign, Inc. Hierarchical publish/subscribe system
US9774619B1 (en) 2015-09-24 2017-09-26 Amazon Technologies, Inc. Mitigating network attacks
US9787775B1 (en) 2010-09-28 2017-10-10 Amazon Technologies, Inc. Point of presence management in request routing
US9794281B1 (en) 2015-09-24 2017-10-17 Amazon Technologies, Inc. Identifying sources of network attacks
US9819567B1 (en) 2015-03-30 2017-11-14 Amazon Technologies, Inc. Traffic surge management for points of presence
US9832229B2 (en) 2015-12-14 2017-11-28 Bank Of America Corporation Multi-tiered protection platform
US9832200B2 (en) 2015-12-14 2017-11-28 Bank Of America Corporation Multi-tiered protection platform
US9832141B1 (en) 2015-05-13 2017-11-28 Amazon Technologies, Inc. Routing based request correlation
US9888089B2 (en) 2015-12-07 2018-02-06 Amazon Technologies, Inc. Client side cache management

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050027882A1 (en) * 2003-05-05 2005-02-03 Sullivan Alan T. Systems and methods for direction of communication traffic
CN101371246A (en) * 2006-01-20 2009-02-18 派克斯费尔有限公司 Systems and methods for discerning and controlling communication traffic
US7958258B2 (en) * 2009-09-09 2011-06-07 Verizon Patent And Licensing, Inc. Mobile communication device domain name system redirection
US8566465B2 (en) 2010-09-17 2013-10-22 At&T Intellectual Property I, L.P. System and method to detect and mitigate distributed denial of service attacks using random internet protocol hopping
US9064261B2 (en) * 2011-05-20 2015-06-23 Google Inc. Auto-suggested content item requests
US9325771B2 (en) * 2013-09-11 2016-04-26 Theplatform, Llc Systems and methods for data management
US9779113B2 (en) * 2014-03-20 2017-10-03 NSONE Inc. Systems and methods for improving domain name system traffic routing
US9118582B1 (en) * 2014-12-10 2015-08-25 Iboss, Inc. Network traffic management using port number redirection
US20170085619A1 (en) * 2015-09-22 2017-03-23 International Business Machines Corporation Maintaining continuous access to web content

Citations (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6009459A (en) * 1997-01-10 1999-12-28 Microsoft Corporation Intelligent automatic searching for resources in a distributed environment
US6092100A (en) * 1997-11-21 2000-07-18 International Business Machines Corporation Method for intelligently resolving entry of an incorrect uniform resource locator (URL)
US6332158B1 (en) * 1998-12-03 2001-12-18 Chris Risley Domain name system lookup allowing intelligent correction of searches and presentation of auxiliary information
US20020055848A1 (en) * 2000-11-08 2002-05-09 Kyung-Sung Jae Method and apparatus of business transaction using inherent identification numbers of hardwares
US20020065842A1 (en) * 2000-07-27 2002-05-30 Ibm System and media for simplifying web contents, and method thereof
US20030014539A1 (en) * 2001-06-12 2003-01-16 Reznick Josh L. System and method for traffic management
US20030018726A1 (en) * 2001-04-27 2003-01-23 Low Sydney Gordon Instant messaging
US6526450B1 (en) * 1998-11-19 2003-02-25 Cisco Technology, Inc. Method and apparatus for domain name service request resolution
US20030110161A1 (en) * 1999-04-05 2003-06-12 Eric Schneider Method, product, and apparatus for providing search results
US6594697B1 (en) * 1999-05-20 2003-07-15 Microsoft Corporation Client system having error page analysis and replacement capabilities
US20030135548A1 (en) * 2001-12-17 2003-07-17 Bushkin Arthur A. System and method for disseminating knowledge over a global computer network
US6615237B1 (en) * 2000-02-04 2003-09-02 Microsoft Corporation Automatic searching for data in a network
US20030231754A1 (en) * 1999-08-20 2003-12-18 David Stein Telephone call redirection system
US20040030780A1 (en) * 2002-08-08 2004-02-12 International Business Machines Corporation Automatic search responsive to an invalid request
US20040044566A1 (en) * 2002-08-30 2004-03-04 Bostelmann Janet K. Landing page and channel identifier in multichannel marketing system
US6760746B1 (en) * 1999-09-01 2004-07-06 Eric Schneider Method, product, and apparatus for processing a data request
US6799214B1 (en) * 2000-03-03 2004-09-28 Nec Corporation System and method for efficient content delivery using redirection pages received from the content provider original site and the mirror sites
US20050015512A1 (en) * 2003-05-23 2005-01-20 International Business Machines Corporation Targeted web page redirection
US20050065806A1 (en) * 2003-06-30 2005-03-24 Harik Georges R. Generating information for online advertisements from Internet data and traditional media data
US20050135264A1 (en) * 2003-12-23 2005-06-23 Jeff Popoff Method for implementing an intelligent content rating middleware platform and gateway system
US20050198068A1 (en) * 2004-03-04 2005-09-08 Shouvick Mukherjee Keyword recommendation for internet search engines
US20050235044A1 (en) * 2004-04-20 2005-10-20 Tazuma Stanley K Apparatus and methods relating to web browser redirection
US7010537B2 (en) * 2000-04-27 2006-03-07 Friskit, Inc. Method and system for visual network searching
US7035921B1 (en) * 2000-11-14 2006-04-25 Hewlett-Packard Development Company, L.P. Method of and apparatus for providing web service using a network of servers
US7110399B2 (en) * 2002-03-28 2006-09-19 International Business Machines Corporation System and method for redirecting network addresses for deferred rendering
US20060218242A1 (en) * 2000-09-26 2006-09-28 Theron Tock Method and system for modifying requests for remote resources

Family Cites Families (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5794210A (en) 1995-12-11 1998-08-11 Cybergold, Inc. Attention brokerage
US5974451A (en) 1996-10-07 1999-10-26 Novaville Ag System and method for distributing bulletins to external computers accessing wide area computer networks
US6070185A (en) 1997-05-02 2000-05-30 Lucent Technologies Inc. Technique for obtaining information and services over a communication network
US5892919A (en) * 1997-06-23 1999-04-06 Sun Microsystems, Inc. Spell checking universal resource locator (URL) by comparing the URL against a cache containing entries relating incorrect URLs submitted by users to corresponding correct URLs
GB2330430B (en) * 1997-10-16 2002-07-17 Ibm Error handler for a proxy server computer system
US6006197A (en) 1998-04-20 1999-12-21 Straightup Software, Inc. System and method for assessing effectiveness of internet marketing campaign
US6564243B1 (en) 1998-09-14 2003-05-13 Adwise Ltd. Method and system for injecting external content into computer network interactive sessions
US7664864B2 (en) * 1998-11-13 2010-02-16 Verisign, Inc. Meta content distribution network
US6532493B1 (en) * 1998-10-29 2003-03-11 Cisco Technology, Inc. Methods and apparatus for redirecting network cache traffic
US6442529B1 (en) * 1998-11-17 2002-08-27 Novaweb Technologies, Inc. Methods and apparatus for delivering targeted information and advertising over the internet
US7188138B1 (en) * 1999-03-22 2007-03-06 Eric Schneider Method, product, and apparatus for resource identifier registration and aftermarket services
US6202087B1 (en) * 1999-03-22 2001-03-13 Ofer Gadish Replacement of error messages with non-error messages
US6339761B1 (en) 1999-05-13 2002-01-15 Hugh V. Cottingham Internet service provider advertising system
WO2000079765A1 (en) 1999-06-23 2000-12-28 At & T Wireless Services, Inc. Reverse tunneling methods and apparatus for use with private computer networks
US7010568B1 (en) 1999-09-01 2006-03-07 Eric Schneider Search engine request method, product, and apparatus
US6968313B1 (en) 1999-11-15 2005-11-22 H Three, Inc. Method and apparatus for facilitating and tracking personal referrals
US6589352B1 (en) * 1999-12-10 2003-07-08 Applied Materials, Inc. Self aligning non contact shadow ring process kit
US7430531B1 (en) * 2000-02-04 2008-09-30 Verisign, Inc. System and method for assisting customers in choosing a bundled set of commodities using customer preferences
US20020023160A1 (en) 2000-03-20 2002-02-21 Garrett John W. Service selection in a shared access network providing access control
US7200863B2 (en) * 2000-05-16 2007-04-03 Hoshiko Llc System and method for serving content over a wide area network
US7032031B2 (en) 2000-06-23 2006-04-18 Cloudshield Technologies, Inc. Edge adapter apparatus and method
US6728767B1 (en) * 2000-08-18 2004-04-27 Cisco Technology, Inc. Remote identification of client and DNS proxy IP addresses
US20020032766A1 (en) * 2000-09-08 2002-03-14 Wei Xu Systems and methods for a packeting engine
US20020056053A1 (en) * 2000-10-26 2002-05-09 Ben Vine System and method for handling web failures
US7219298B2 (en) * 2001-03-15 2007-05-15 International Business Machines Corporation Method, system, and program for verifying network addresses included in a file
US20020161757A1 (en) * 2001-03-16 2002-10-31 Jeffrey Mock Simultaneous searching across multiple data sets
US20030163368A1 (en) * 2001-05-21 2003-08-28 Frank Bastone Method for promoting a web site using services of a web site host
ES2183728B1 (en) 2001-07-16 2004-06-16 Airtel Movil, S.A. Appointment system domains (dns) for access to databases.
US7069336B2 (en) 2002-02-01 2006-06-27 Time Warner Cable Policy based routing system and method for caching and VPN tunneling
US7424459B2 (en) * 2002-03-01 2008-09-09 Lightsurf Technologies, Inc. System providing methods for dynamic customization and personalization of user interface
US20030233328A1 (en) 2002-04-23 2003-12-18 Scott David A. Method and system for securely communicating data in a communications network
US7120833B2 (en) * 2002-04-26 2006-10-10 Alcatel Error codes in Agent X
US20030236729A1 (en) 2002-06-21 2003-12-25 Kenneth Epstein Systems and methods of directing, customizing, exchanging, negotiating, trading and provisioning of information, goods and services to information users
US8132219B2 (en) 2002-06-21 2012-03-06 Tivo Inc. Intelligent peer-to-peer system and method for collaborative suggestions and propagation of media
US7058633B1 (en) * 2002-09-09 2006-06-06 Cisco Technology, Inc. System and method for generalized URL-rewriting
US7136922B2 (en) 2002-10-15 2006-11-14 Akamai Technologies, Inc. Method and system for providing on-demand content delivery for an origin server
US20040225518A1 (en) * 2002-12-10 2004-11-11 David Bain Bounty system for generating charitable contributions
US7899932B2 (en) * 2003-01-15 2011-03-01 Panasonic Corporation Relayed network address translator (NAT) traversal
US20050027882A1 (en) * 2003-05-05 2005-02-03 Sullivan Alan T. Systems and methods for direction of communication traffic
EP1661018A4 (en) * 2003-08-15 2009-08-26 Oversee Net Internet domain keyword optimization
US20070078714A1 (en) * 2005-09-30 2007-04-05 Yahoo! Inc. Automatically matching advertisements to media files

Patent Citations (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6009459A (en) * 1997-01-10 1999-12-28 Microsoft Corporation Intelligent automatic searching for resources in a distributed environment
US6092100A (en) * 1997-11-21 2000-07-18 International Business Machines Corporation Method for intelligently resolving entry of an incorrect uniform resource locator (URL)
US6526450B1 (en) * 1998-11-19 2003-02-25 Cisco Technology, Inc. Method and apparatus for domain name service request resolution
US6332158B1 (en) * 1998-12-03 2001-12-18 Chris Risley Domain name system lookup allowing intelligent correction of searches and presentation of auxiliary information
US20030110161A1 (en) * 1999-04-05 2003-06-12 Eric Schneider Method, product, and apparatus for providing search results
US6594697B1 (en) * 1999-05-20 2003-07-15 Microsoft Corporation Client system having error page analysis and replacement capabilities
US20030231754A1 (en) * 1999-08-20 2003-12-18 David Stein Telephone call redirection system
US6760746B1 (en) * 1999-09-01 2004-07-06 Eric Schneider Method, product, and apparatus for processing a data request
US6615237B1 (en) * 2000-02-04 2003-09-02 Microsoft Corporation Automatic searching for data in a network
US6799214B1 (en) * 2000-03-03 2004-09-28 Nec Corporation System and method for efficient content delivery using redirection pages received from the content provider original site and the mirror sites
US7010537B2 (en) * 2000-04-27 2006-03-07 Friskit, Inc. Method and system for visual network searching
US20020065842A1 (en) * 2000-07-27 2002-05-30 Ibm System and media for simplifying web contents, and method thereof
US20060218242A1 (en) * 2000-09-26 2006-09-28 Theron Tock Method and system for modifying requests for remote resources
US20020055848A1 (en) * 2000-11-08 2002-05-09 Kyung-Sung Jae Method and apparatus of business transaction using inherent identification numbers of hardwares
US7035921B1 (en) * 2000-11-14 2006-04-25 Hewlett-Packard Development Company, L.P. Method of and apparatus for providing web service using a network of servers
US20030018726A1 (en) * 2001-04-27 2003-01-23 Low Sydney Gordon Instant messaging
US20030014539A1 (en) * 2001-06-12 2003-01-16 Reznick Josh L. System and method for traffic management
US20030135548A1 (en) * 2001-12-17 2003-07-17 Bushkin Arthur A. System and method for disseminating knowledge over a global computer network
US7110399B2 (en) * 2002-03-28 2006-09-19 International Business Machines Corporation System and method for redirecting network addresses for deferred rendering
US20040030780A1 (en) * 2002-08-08 2004-02-12 International Business Machines Corporation Automatic search responsive to an invalid request
US20040044566A1 (en) * 2002-08-30 2004-03-04 Bostelmann Janet K. Landing page and channel identifier in multichannel marketing system
US20050015512A1 (en) * 2003-05-23 2005-01-20 International Business Machines Corporation Targeted web page redirection
US20050065806A1 (en) * 2003-06-30 2005-03-24 Harik Georges R. Generating information for online advertisements from Internet data and traditional media data
US20050135264A1 (en) * 2003-12-23 2005-06-23 Jeff Popoff Method for implementing an intelligent content rating middleware platform and gateway system
US20050198068A1 (en) * 2004-03-04 2005-09-08 Shouvick Mukherjee Keyword recommendation for internet search engines
US20050235044A1 (en) * 2004-04-20 2005-10-20 Tazuma Stanley K Apparatus and methods relating to web browser redirection

Cited By (105)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8630988B2 (en) 2001-11-01 2014-01-14 Verisign, Inc. System and method for processing DNS queries
US8682856B2 (en) 2001-11-01 2014-03-25 Verisign, Inc. Method and system for processing query messages over a network
US8171019B2 (en) 2001-11-01 2012-05-01 Verisign, Inc. Method and system for processing query messages over a network
US20040254926A1 (en) * 2001-11-01 2004-12-16 Verisign, Inc. Method and system for processing query messages over a network
US20090106211A1 (en) * 2001-11-01 2009-04-23 Verisign, Inc. System and Method for Processing DNS Queries
US20060004710A1 (en) * 2004-06-16 2006-01-05 Veritas Operating Corporation System and method for directing query traffic
US7987181B2 (en) 2004-06-16 2011-07-26 Symantec Operating Corporation System and method for directing query traffic
US20080155694A1 (en) * 2005-07-08 2008-06-26 Kt Corporation Malignant bot confrontation method and its system
US8112804B2 (en) * 2005-07-08 2012-02-07 Kt Corporation Malignant BOT confrontation method and its system
US20080189192A1 (en) * 2005-09-16 2008-08-07 Ofer Ronen Domain name marketplace
US20070260518A1 (en) * 2005-09-16 2007-11-08 Ofer Ronen Electronic marketplace used to lease domain names and redirect web surfers from leased domain names
US20090327098A1 (en) * 2005-09-16 2009-12-31 Sendori, Inc. Enhancements for domain name leasing marketplace
US7711851B2 (en) * 2005-09-16 2010-05-04 Sendori, Inc. Domain name marketplace
US20070067416A1 (en) * 2005-09-16 2007-03-22 Advanced Digital Broadcast S. A. Method for referencing remote element of content, method for providing content with remote elements and system for distributing content
US7711850B2 (en) * 2005-09-16 2010-05-04 Sendori, Inc. Electronic marketplace used to lease domain names and redirect web surfers from leased domain names
US8271682B2 (en) 2005-09-16 2012-09-18 Sendori, Inc. Enhancements for domain name leasing marketplace
US20070192246A1 (en) * 2006-01-23 2007-08-16 Intersearch Group, Inc. System and method for redirecting internet traffic
WO2007087390A2 (en) * 2006-01-23 2007-08-02 Intersearch Group, Inc. System and method for redirecting internet traffic
WO2007087390A3 (en) * 2006-01-23 2008-04-24 Michael Dennis Futamase System and method for redirecting internet traffic
US9021129B2 (en) 2007-06-29 2015-04-28 Amazon Technologies, Inc. Request routing utilizing client location information
US9021127B2 (en) 2007-06-29 2015-04-28 Amazon Technologies, Inc. Updating routing information based on client location
US20090043855A1 (en) * 2007-08-08 2009-02-12 Blake Bookstaff System for providing information to originator of misdirected email
US8159352B2 (en) 2007-09-11 2012-04-17 Colgate-Palmolive Company Personal care implement having a display
US8681008B2 (en) 2007-09-11 2014-03-25 Colgate-Palmolive Company Personal care implement having a display
US7805379B1 (en) * 2007-12-18 2010-09-28 Amazon Technologies, Inc. Method and system for leasing or purchasing domain names
US8200583B1 (en) 2007-12-18 2012-06-12 Amazon Technologies, Inc. Method and system for leasing or purchasing domain names
US9531581B1 (en) 2007-12-18 2016-12-27 Amazon Technologies, Inc. Method and system for identifying and automatically registering domain names
US9621660B2 (en) 2008-03-31 2017-04-11 Amazon Technologies, Inc. Locality based content distribution
US9407699B2 (en) 2008-03-31 2016-08-02 Amazon Technologies, Inc. Content management
US9332078B2 (en) 2008-03-31 2016-05-03 Amazon Technologies, Inc. Locality based content distribution
US9479476B2 (en) 2008-03-31 2016-10-25 Amazon Technologies, Inc. Processing of DNS queries
US9571389B2 (en) 2008-03-31 2017-02-14 Amazon Technologies, Inc. Request routing based on class
US9544394B2 (en) 2008-03-31 2017-01-10 Amazon Technologies, Inc. Network resource identification
US9208097B2 (en) 2008-03-31 2015-12-08 Amazon Technologies, Inc. Cache optimization
US9210235B2 (en) 2008-03-31 2015-12-08 Amazon Technologies, Inc. Client side cache management
US9608957B2 (en) 2008-06-30 2017-03-28 Amazon Technologies, Inc. Request routing using network computing components
US9021128B2 (en) 2008-06-30 2015-04-28 Amazon Technologies, Inc. Request routing using network computing components
US9734472B2 (en) 2008-11-17 2017-08-15 Amazon Technologies, Inc. Request routing utilizing cost information
US9444759B2 (en) 2008-11-17 2016-09-13 Amazon Technologies, Inc. Service provider registration by a content broker
US9451046B2 (en) 2008-11-17 2016-09-20 Amazon Technologies, Inc. Managing CDN registration by a storage provider
US9515949B2 (en) 2008-11-17 2016-12-06 Amazon Technologies, Inc. Managing content delivery network service providers
US9251112B2 (en) 2008-11-17 2016-02-02 Amazon Technologies, Inc. Managing content delivery network service providers
US9787599B2 (en) 2008-11-17 2017-10-10 Amazon Technologies, Inc. Managing content delivery network service providers
US9590946B2 (en) 2008-11-17 2017-03-07 Amazon Technologies, Inc. Managing content delivery network service providers
US9191458B2 (en) * 2009-03-27 2015-11-17 Amazon Technologies, Inc. Request routing using a popularity identifier at a DNS nameserver
US20140289319A1 (en) * 2009-03-27 2014-09-25 Amazon Technologies, Inc. Request routing using popularity information
US9237114B2 (en) 2009-03-27 2016-01-12 Amazon Technologies, Inc. Managing resources in resource cache components
US9742723B2 (en) 2009-04-22 2017-08-22 Verisign, Inc. Internet profile service
US9292612B2 (en) 2009-04-22 2016-03-22 Verisign, Inc. Internet profile service
US8527945B2 (en) 2009-05-07 2013-09-03 Verisign, Inc. Method and system for integrating multiple scripts
US20100318858A1 (en) * 2009-06-15 2010-12-16 Verisign, Inc. Method and system for auditing transaction data from database operations
US9535971B2 (en) 2009-06-15 2017-01-03 Verisign, Inc. Method and system for auditing transaction data from database operations
US8510263B2 (en) 2009-06-15 2013-08-13 Verisign, Inc. Method and system for auditing transaction data from database operations
US9176894B2 (en) 2009-06-16 2015-11-03 Amazon Technologies, Inc. Managing resources using resource expiration data
US20110022678A1 (en) * 2009-07-27 2011-01-27 Verisign, Inc. Method and system for data logging and analysis
US8977705B2 (en) 2009-07-27 2015-03-10 Verisign, Inc. Method and system for data logging and analysis
US20110047292A1 (en) * 2009-08-18 2011-02-24 Verisign, Inc. Method and system for intelligent routing of requests over epp
US9455880B2 (en) 2009-08-18 2016-09-27 Verisign, Inc. Method and system for intelligent routing of requests over EPP
US8327019B2 (en) 2009-08-18 2012-12-04 Verisign, Inc. Method and system for intelligent routing of requests over EPP
US8856344B2 (en) 2009-08-18 2014-10-07 Verisign, Inc. Method and system for intelligent many-to-many service routing over EPP
US8175098B2 (en) 2009-08-27 2012-05-08 Verisign, Inc. Method for optimizing a route cache
US9130756B2 (en) 2009-09-04 2015-09-08 Amazon Technologies, Inc. Managing secure content in a content delivery network
US9712325B2 (en) 2009-09-04 2017-07-18 Amazon Technologies, Inc. Managing secure content in a content delivery network
US9246776B2 (en) 2009-10-02 2016-01-26 Amazon Technologies, Inc. Forward-based resource delivery network management techniques
US9569753B2 (en) 2009-10-30 2017-02-14 Verisign, Inc. Hierarchical publish/subscribe system performed by multiple central relays
US9762405B2 (en) 2009-10-30 2017-09-12 Verisign, Inc. Hierarchical publish/subscribe system
US9047589B2 (en) 2009-10-30 2015-06-02 Verisign, Inc. Hierarchical publish and subscribe system
US9269080B2 (en) 2009-10-30 2016-02-23 Verisign, Inc. Hierarchical publish/subscribe system
US9235829B2 (en) 2009-10-30 2016-01-12 Verisign, Inc. Hierarchical publish/subscribe system
US8982882B2 (en) 2009-11-09 2015-03-17 Verisign, Inc. Method and system for application level load balancing in a publish/subscribe message architecture
US9124592B2 (en) 2009-11-09 2015-09-01 Verisign, Inc. Method and system for application level load balancing in a publish/subscribe message architecture
US9495338B1 (en) 2010-01-28 2016-11-15 Amazon Technologies, Inc. Content distribution network
US9160703B2 (en) 2010-09-28 2015-10-13 Amazon Technologies, Inc. Request routing management based on network components
US9497259B1 (en) 2010-09-28 2016-11-15 Amazon Technologies, Inc. Point of presence management in request routing
US9800539B2 (en) 2010-09-28 2017-10-24 Amazon Technologies, Inc. Request routing management based on network components
US9712484B1 (en) 2010-09-28 2017-07-18 Amazon Technologies, Inc. Managing request routing information utilizing client identifiers
US9253065B2 (en) 2010-09-28 2016-02-02 Amazon Technologies, Inc. Latency measurement in resource requests
US9407681B1 (en) 2010-09-28 2016-08-02 Amazon Technologies, Inc. Latency measurement in resource requests
US9106701B2 (en) 2010-09-28 2015-08-11 Amazon Technologies, Inc. Request routing management based on network components
US9794216B2 (en) 2010-09-28 2017-10-17 Amazon Technologies, Inc. Request routing in a networked environment
US9185012B2 (en) 2010-09-28 2015-11-10 Amazon Technologies, Inc. Latency measurement in resource requests
US9787775B1 (en) 2010-09-28 2017-10-10 Amazon Technologies, Inc. Point of presence management in request routing
US9191338B2 (en) 2010-09-28 2015-11-17 Amazon Technologies, Inc. Request routing in a networked environment
US8631156B2 (en) * 2010-10-12 2014-01-14 Apple Inc. Systems and methods for providing network resource address management
US20120089712A1 (en) * 2010-10-12 2012-04-12 Apple Inc. Systems and methods for providing network resource address management
US9391949B1 (en) 2010-12-03 2016-07-12 Amazon Technologies, Inc. Request routing processing
US9628554B2 (en) 2012-02-10 2017-04-18 Amazon Technologies, Inc. Dynamic content delivery
US9083743B1 (en) 2012-03-21 2015-07-14 Amazon Technologies, Inc. Managing request routing information utilizing performance information
US9172674B1 (en) 2012-03-21 2015-10-27 Amazon Technologies, Inc. Managing request routing information utilizing performance information
US9154551B1 (en) 2012-06-11 2015-10-06 Amazon Technologies, Inc. Processing DNS queries to identify pre-processing information
US9525659B1 (en) 2012-09-04 2016-12-20 Amazon Technologies, Inc. Request routing utilizing point of presence load information
US9135048B2 (en) 2012-09-20 2015-09-15 Amazon Technologies, Inc. Automated profiling of resource usage
US9323577B2 (en) 2012-09-20 2016-04-26 Amazon Technologies, Inc. Automated profiling of resource usage
US9294391B1 (en) 2013-06-04 2016-03-22 Amazon Technologies, Inc. Managing network computing components utilizing request routing
US9887932B1 (en) 2015-03-30 2018-02-06 Amazon Technologies, Inc. Traffic surge management for points of presence
US9819567B1 (en) 2015-03-30 2017-11-14 Amazon Technologies, Inc. Traffic surge management for points of presence
US9887931B1 (en) 2015-03-30 2018-02-06 Amazon Technologies, Inc. Traffic surge management for points of presence
US9832141B1 (en) 2015-05-13 2017-11-28 Amazon Technologies, Inc. Routing based request correlation
US9794281B1 (en) 2015-09-24 2017-10-17 Amazon Technologies, Inc. Identifying sources of network attacks
US9774619B1 (en) 2015-09-24 2017-09-26 Amazon Technologies, Inc. Mitigating network attacks
US9742795B1 (en) 2015-09-24 2017-08-22 Amazon Technologies, Inc. Mitigating network attacks
US9888089B2 (en) 2015-12-07 2018-02-06 Amazon Technologies, Inc. Client side cache management
US9832200B2 (en) 2015-12-14 2017-11-28 Bank Of America Corporation Multi-tiered protection platform
US9832229B2 (en) 2015-12-14 2017-11-28 Bank Of America Corporation Multi-tiered protection platform
US9887915B2 (en) 2017-01-17 2018-02-06 Amazon Technologies, Inc. Request routing based on class

Also Published As

Publication number Publication date Type
US7631101B2 (en) 2009-12-08 grant
US20070038729A1 (en) 2007-02-15 application
US20110072124A1 (en) 2011-03-24 application
US20100138559A1 (en) 2010-06-03 application

Similar Documents

Publication Publication Date Title
US6012090A (en) Client-side parallel requests for network services using group name association
US7136932B1 (en) Fictitious domain name method, product, and apparatus
US6304906B1 (en) Method and systems for allowing data service system to provide class-based services to its users
US7530099B2 (en) Method and system for a single-sign-on mechanism within application service provider (ASP) aggregation
US7337910B2 (en) Methods and devices for responding to request for unregistered domain name to indicate a predefined type of service
US6026430A (en) Dynamic client registry apparatus and method
US6347085B2 (en) Method and apparatus for establishing communications between packet-switched and circuit-switched networks
US7675903B2 (en) Dynamic contact list management system and method
US8635340B1 (en) Method, product, and apparatus for requesting a network resource
US5867667A (en) Publication network control system using domain and client side communications resource locator lists for managing information communications between the domain server and publication servers
US5884035A (en) Dynamic distributed group registry apparatus and method for collaboration and selective sharing of information
US20020055956A1 (en) Method and system for assembling concurrently-generated content
US6836476B1 (en) Business model, system and method for voice and/or data communications with local business
US5867665A (en) Domain communications server
US5870562A (en) Universal domain routing and publication control system
US20020107925A1 (en) Method and system for e-mail management
US7308475B1 (en) Method and system for accessing network services
US7143195B2 (en) HTTP redirector
US20090316687A1 (en) Peer to peer inbound contact center
US7694016B2 (en) Composite DNS zones
US20030163730A1 (en) System and method for distributed authentication service
US20030046405A1 (en) Processing network address identifiers
US20020156812A1 (en) Method and system for assembling concurrently-generated content
US20040260749A1 (en) Systems and methods for event semantic binding in networks
US20100024008A1 (en) Managing Resource Allocations

Legal Events

Date Code Title Description
AS Assignment

Owner name: PAXFIRE, INC., DISTRICT OF COLUMBIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SULLIVAN, ALAN;LEWYN, MARK;GROSS, PHILLIP;REEL/FRAME:015924/0375;SIGNING DATES FROM 20040930 TO 20041011