WO2005072473A2 - System and method for binding a client to a server - Google Patents

System and method for binding a client to a server Download PDF

Info

Publication number
WO2005072473A2
WO2005072473A2 PCT/US2005/003557 US2005003557W WO2005072473A2 WO 2005072473 A2 WO2005072473 A2 WO 2005072473A2 US 2005003557 W US2005003557 W US 2005003557W WO 2005072473 A2 WO2005072473 A2 WO 2005072473A2
Authority
WO
WIPO (PCT)
Prior art keywords
server
client
fit
addresses
list
Prior art date
Application number
PCT/US2005/003557
Other languages
French (fr)
Other versions
WO2005072473A3 (en
Inventor
John Cooney
Ali Awais
Fabrizio Talucci
Charlie Zimmerman
Original Assignee
I2 Telecom International, 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
Application filed by I2 Telecom International, Inc. filed Critical I2 Telecom International, Inc.
Publication of WO2005072473A2 publication Critical patent/WO2005072473A2/en
Publication of WO2005072473A3 publication Critical patent/WO2005072473A3/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/256—NAT traversal
    • H04L61/2575—NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1006—Server selection for load balancing with static server selection, e.g. the same server being selected for a specific client
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/101—Server selection for load balancing based on network conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1021—Server selection for load balancing based on client or server locations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access

Definitions

  • the present invention relates generally to implementation of client-server networks. More particularly, the present invention provides systems and methods for maintaining the binding of a client, particularly a client with limited computational and storage resources, with at least one server.
  • the Internet has had a profound impact on the way society communicates.
  • Today, the Internet is used for personal communications, for business communications, for shopping, for entertainment, for news, and more.
  • DNS Internet Distributed Name Service
  • a name server receives a name from a client, associates the name with an IP address, and sends the IP address to a client. The client then communicates with a server via the server's IP address.
  • the DNS is, however, far from simple. DNS servers receive millions of requests each day. Because a single DNS server may not know the address associated with a particular name, DNS servers must also be able to contact other DNS servers. A name server would start its search for an IP address by contacting one of the root name server ⁇ .
  • the root servers know the IP address for all of the name servers that handle the top-level domains. For example, a name server might "ask” a root server for the IP address associated with www.Yahoo.com, and the root might "respond” (assuming no caching), "I don't know the IP address for Yahoo.com, but here's the IP address for the COM name server.”
  • One of the keys to making this work is redundancy. There are multiple name servers at every level, so if one fails, there are others to handle the requests.
  • name servers cache the IP addresses returned in response to a request.
  • Name servers do not cache forever, though.
  • the caching has a component, called the Time To Live (TTL) that controls how long a server will cache a piece of information.
  • TTL Time To Live
  • the name server will cache the IP address for that period of time (ranging from minutes to days) and then discard it.
  • the TTL allows changes in name servers to propagate.
  • Embodiments of the present invention allow a client to receive and maintain a set of "best-fit" server IP addresses.
  • the best fit server IP addresses establish a hierarchy of server addresses that are used by a client to maintain a binding with a server without using the DNS.
  • the set of best-fit server IP addresses is relatively small.
  • an Internet Appliance maintains a set of three best-fit server IP addresses.
  • Communicating the set of best-fit server IP addresses to a specific client is accomplished using extensions of a network protocol already used to support client/server communications, thus minimizing the amount of code needed to support the additional information transfer.
  • Another aspect of the present invention is to minimize the overhead required to dynamically bind a client with a server without using DNS.
  • An embodiment of the present invention provides a method for maintaining the binding of a client with a server.
  • a server creates a list comprising of a list of best-fit server IP addresses for a client.
  • the list of best-fit server IP addresses are ordered according to network distribution criteria selected from the group consisting of the routing distance between the client and each server associated with each of the list of best-fit server IP addresses, message delivery latency, and server loading.
  • a transmission protocol used by the client and the server is extended for communications to transport the best-fit server IP list.
  • the best-fit server IP list is sent to the client.
  • an SIP protocol message is extended and the best-fit server IP list is sent to the client using an extended SIP protocol message comprising the best-fit server IP list.
  • Another method of the present invention provides for initiating the binding of a client with a server.
  • a best-fit server IP address is selected by a client from a list of best-fit server IP addresses.
  • a next best- fit server IP address is selected from a best-fit server IP address list.
  • the client makes a next attempt to initiate a session with a server using the next selected best-fit server IP address.
  • the best-fit server IP address list is ordered according to network distribution criteria.
  • the distribution criteria are selected from the group consisting of the routing distance between the client and each server associated with each of the list of best-fit server IP addresses, message delivery latency, and server loading.
  • Selecting the first and next best-fit server IP addresses from a best-fit server IP address list comprises selecting the best-fit server IP addresses according to the order in which the best-fit server IP addresses appear on the best-fit server IP address list.
  • Another method of the present invention provides for maintaining the binding of a client with a server.
  • a transmission protocol used by the client and the server is extended for communications.
  • the extended transmission protocol is used by a client to request a best-fit server IP list from a server, wherein the best-fit server IP list comprises a list of best-fit server IP addresses.
  • the best-fit server IP list is received and stored by the client.
  • the STUN protocol message is extended and used to request a best-fit server IP list.
  • the client determines whether the IP address of a server is on the best-fit IP address list.
  • the client terminates its association with the server and selects a best-fit server IP address from a best-fit server IP address list.
  • An attempt is made by the client to initiate a session using the selected best-fit server IP address.
  • a next best-fit server IP address is selected from a best-fit server IP address list.
  • a next attempt is made by the client to initiate a session using the next selected best-fit server IP address.
  • the best-fit server IP addresses are ordered according to network distribution criteria.
  • the network distribution criteria are selected from the group consisting of the routing distance between the client and each server associated with each of the list of best-fit server IP addresses, message delivery latency, and server loading.
  • the client determines whether a connection between the client and a server has been lost. In the event that the connection has been lost, a best-fit server IP address is selected from the best-fit server IP address list. An attempt is made by the client to initiate a session using the selected best-fit server IP address. In the event the first attempt to initiate a session fails, a next best-fit server IP address is selected from a best-fit server IP address list. The client makes a next attempt to initiate a session using the next selected best-fit server IP address.
  • the best-fit server IP addresses are ordered according to network distribution criteria.
  • the network distribution criteria are selected from the group consisting of the routing distance between the client and each server associated with each of the list of best-fit server IP addresses, message delivery latency, and server loading.
  • Figure 1 illustrates the interaction of an Internet Appliance with a server according to embodiments of the present invention.
  • Figure 2 illustrates a process according to embodiments of the present invention in which an Internet Appliance (client) uses best-fit IP address to create a binding with a server.
  • client Internet Appliance
  • Figure 3 illustrates a process of receiving and verifying a best-fit list by a client according to embodiments of the present invention.
  • Embodiments of the present invention allow a client to receive and maintain a set of "best-fit" server IP addresses.
  • the best fit server IP addresses establish a hierarchy of server addresses that are used by a client to maintain a binding with a server without using the DNS.
  • the set of best-fit server IP addresses is relatively small.
  • an Internet Appliance maintains a set of three best-fit server IP addresses. Communicating the set of best-fit server IP addresses to a specific client is accomplished using extensions of network protocols already used to support client/server communications, thus minimizing the amount of code needed to support the additional information transfer.
  • FIG. 1 illustrates the interaction of an Internet Appliance with a server according to embodiments of the present invention.
  • an Internet Appliance (client) 100 comprises a protocol engine 110 connected to the Internet 115.
  • the protocol engine 110 communicates via the Internet 115 with a corresponding protocol engine 145 in a server 140.
  • protocol message 160 comprising best-fit server IP addresses are passed from the server 140 to the Internet Appliance (client) 100.
  • the Internet Appliance (client) 100 extracts this information from the protocol message 160 and saves this information in persistent memory (not illustrated).
  • the protocol engine 145 on server 140 is integrated with a best-fit solutions database 155.
  • the best-fit solutions database 155 is updated by an optimizer program 150 that runs as a background application on the server 140.
  • the best-fit IP addresses are computed on-the-fly (by protocol engine 145 or a linked device) based on the latest routing and server availability information.
  • FIG. 2 illustrates a process according to embodiments of the present invention in which an Internet Appliance (client) uses best-fit IP address to create a binding with a server.
  • client Internet Appliance
  • a client initiates contact with a server using the first best-fit IP address in the list 200. If the connection is bound 210 the binding process ends 230. If the client is not bound to a server, a check is made to determine if the last-tried best-fit address was the last address 215. If the last-tried best-fit address was the last address, the binding process is restarted 225. If the last-tried best-fit address is not the last address, contact is initiated using the next best-fit address 220.
  • connection is checked 235 to determine if the connection has been lost 240. If the connection has not been lost, the checking process 235 is repeated. If the connection has been lost, the binding process is restarted 225. If none of the servers in the best-fit server IP address list 105 respond then, a "catastrophic" failure has occurred. This could be caused because the user's Internet access has been impaired, because a sufficiently large part of the Internet is disabled preventing access to any of the servers in the best-fit list, or because a sufficiently large physical event has caused all the servers in the best- fit list to become inoperable. When a "catastrophic" failure occurs, the client continues to contact the servers on its best-fit list until the network problem is corrected. This re-use of the initialization procedure helps address the constraint of scarce storage resources on the Internet Appliance.
  • the list of best-fit server IP addresses 105 is ordered such that elements closer to the top of the list are "more optimal" than lower items on the list.
  • the binding process illustrated in Figure 2 attempts to bind with the more optimal server first.
  • “more optimal” reflects the result of analysis done prior to the last down load of the best-fit list from the server to the client. Note subsequent to the last sending of the best-fit list and the time when the client is bound to a server, the physical location or Internet "routing distance" may have changed thereby changing the optimization of the best-fit list.
  • Figure 3 illustrates a process of receiving and verifying a best-fit list by a client according to embodiments of the present invention.
  • a client binds with a server 300.
  • a new best-fit server IP address list is received and stored by the client 305 for access during power up initialization. Once stored, the client determines whether it is currently bound to a server having the first best-fit address in the new list 310. If it is not, then the client initiates a binding process as illustrated in Figure 2.
  • the server determines the best-fit list of server IP addresses and communicates this information to the client via a extension of a network protocol currently used by the client and server to establish or maintain existing communications.
  • a protocol engine at the server is extended to accept a best-fit server IP address list and communicate it to each client associated with that server.
  • the server associated with a client is no longer on the list of best-fit server IP addresses, the client will terminate the association and attempt to connect with a server on the last-received list.
  • the server represented by the first IP address on the new best-fit list is then associated with the client.
  • An embodiment of the present invention extends a network protocol used by a client and server to convey information relating to the best-fit server IP address list.
  • a preferred protocol will support sessions initiated by the client that allow subsequent responses by the server. Additionally, the preferred protocol will support communication at a frequency that facilitates timely communication of new best- fit server IP address lists and be adaptable to accept the simple payload data required for the best-fit server IP address list.
  • a client and server use multiple protocols to send and update best-fit IP address information.
  • a server communicates with a client via the Session Initiation Protocol (SIP).
  • SIP Session Initiation Protocol
  • This protocol meets the preferred criteria that a session is initiated by the client while allowing the server to send the client a message at any time.
  • processing of the SIP protocol for both the client and the server requires considerable work. This is of particular concern where the client resides on an Internet Appliance with very little computation resources.
  • the client in this exemplary embodiment also uses the STUN protocol.
  • STUN lacks that quality of being able to respond to a server-generated message at any time, but has the advantage that it is very simple to process and extend.
  • These two protocols are used in combination to perform the tasks of sending a list of best-fist IP addresses to the client and sending the client notice that the list has been updated.
  • the server uses a SIP protocol extension to notify the client.
  • the client uses the STUN protocol to request and receive the new list.

Abstract

A system and method of binding a client with a server. Embodiments of the present invention allow a client to receive and maintain a set of “best-fit” server IP addresses. The best fit server IP addresses establish a hierarchy of server addresses that are used by a client to maintain a binding with a server without using the DNS. Communication the set of best-fit server IP addresses to a specific client is accomplished using extensions to one or more network protocols already used to support client/server communications, thus minimizing the amount of code needed to support the additional information transfer.

Description

SYSTEM AND METHOD OF BINDING A CLIENT TO A SERVER
CROSS REFERENCE TO RELATED APPLICATIONS
[0001 ] This application claims priority under 35 U.S.C. § 119(e) from provisional application number 60/539,768 filed January 28, 2004. The 60/539,768 provisional application is incorporated by reference herein, in its entirety, for all purposes. BACKGROUND
[0002] The present invention relates generally to implementation of client-server networks. More particularly, the present invention provides systems and methods for maintaining the binding of a client, particularly a client with limited computational and storage resources, with at least one server.
[0003] The Internet has had a profound impact on the way society communicates. Today, the Internet is used for personal communications, for business communications, for shopping, for entertainment, for news, and more.
[0004] There are many applications that rely on a client being in constant contact with a server in order to perform a task. Typically, this requirement is constrained by several factors: • The client resides on a small specialized computer, with extremely limited computational and storage resources (herein, an "Internet Appliance"). • The client to server connection (binding) is mission critical and must be maintained constantly. A tolerable interruption in communications is approximately thirty-seconds within a one-hour interval. • To remove the potential for a "single point of failure" multiple servers must be deployed, geographically separated and independently addressable on the Internet. The number of servers could range into the hundreds. • There are expected to be millions of clients, to reduce the impact of a server failing and to maintain responsiveness of client/server bindings, clients must be distributed across all available servers. • The binding between client and server must be dynamic. There are many potential causes for a client to need to change the server to which it is bound. [0005] The need for a dynamic binding between a client and server is dictated by a number of factors. To insure that combined server resources are being allocated to provide optimal service to all clients, clients are distributed among servers. The distribution takes into account the "routing distance" between a client and the server (the number of Internet hops as well as message delivery latency). As more clients are added, the distribution may become sub-optimum and require adjustment, requiring in turn that some clients be redirected to different servers. Another benefit of dynamic binding between client and server is to provide for continuity of client services in the event a server fails or is pulled off-line for maintenance.
[0006] The traditional approach for a client to identify and then bind with a server relies on the Internet Distributed Name Service (DNS), which can associate a static list of Internet IP addresses with a name. While machines respond to IP addresses in the form of number strings, humans are not adept at remembering them. A name server receives a name from a client, associates the name with an IP address, and sends the IP address to a client. The client then communicates with a server via the server's IP address.
[0007] The DNS is, however, far from simple. DNS servers receive millions of requests each day. Because a single DNS server may not know the address associated with a particular name, DNS servers must also be able to contact other DNS servers. A name server would start its search for an IP address by contacting one of the root name server^. The root servers know the IP address for all of the name servers that handle the top-level domains. For example, a name server might "ask" a root server for the IP address associated with www.Yahoo.com, and the root might "respond" (assuming no caching), "I don't know the IP address for Yahoo.com, but here's the IP address for the COM name server." One of the keys to making this work is redundancy. There are multiple name servers at every level, so if one fails, there are others to handle the requests.
[0008] To speed up the process, name servers cache the IP addresses returned in response to a request. Name servers do not cache forever, though. The caching has a component, called the Time To Live (TTL) that controls how long a server will cache a piece of information. When the server receives an IP address, it receives the TTL with it. The name server will cache the IP address for that period of time (ranging from minutes to days) and then discard it. The TTL allows changes in name servers to propagate. [0009] Not all name servers respect the TTL they receive, however. This means that new information and old information may reside in the DNS at the same time. Sometimes, it takes weeks for a change in an IP address to propagate throughout the Web. Additionally, implementing the DNS protocol on the Internet Appliance requires additional computational, program storage and data storage resources that may not be available or desirable to add.
[0010] What would be useful is a system and method for permitting a client running on an Internet Appliance to dynamically bind with at least one server without using DNS. DETAILED DESCRIPTION
[0011 ] Embodiments of the present invention allow a client to receive and maintain a set of "best-fit" server IP addresses. The best fit server IP addresses establish a hierarchy of server addresses that are used by a client to maintain a binding with a server without using the DNS. In the case of an Internet Appliance, the set of best-fit server IP addresses is relatively small. In one embodiment, an Internet Appliance maintains a set of three best-fit server IP addresses. However, this is not meant as a limitation. As will be apparent to those skilled in the art, any number best-fit server IP addresses may be maintained by a client/Internet Appliance without departing from the scope of the present invention. Communicating the set of best-fit server IP addresses to a specific client is accomplished using extensions of a network protocol already used to support client/server communications, thus minimizing the amount of code needed to support the additional information transfer.
[0012] It is therefore an aspect of the present invention to provide and maintain a set of best- fit server IP addresses with a client.
[0013] It is another aspect of the present invention to provide a set of best- fit server IP addresses to a client via a protocol used by the client and server to establish and/or conduct communications.
[0014] It is still another aspect of the present invention to use a set of best-fit server IP addresses to dynamically bind a client with a server, either at the initialization of a session between the client and server or as a result of a loss of connectivity between the client and server, without using DNS.
[0015] Another aspect of the present invention is to minimize the overhead required to dynamically bind a client with a server without using DNS. [0016] These and other embodiments of the present invention will become apparent from a review of the general and detailed descriptions that follow.
[0017] An embodiment of the present invention provides a method for maintaining the binding of a client with a server. A server creates a list comprising of a list of best-fit server IP addresses for a client. Optionally, the list of best-fit server IP addresses are ordered according to network distribution criteria selected from the group consisting of the routing distance between the client and each server associated with each of the list of best-fit server IP addresses, message delivery latency, and server loading. A transmission protocol used by the client and the server is extended for communications to transport the best-fit server IP list. The best-fit server IP list is sent to the client. In another embodiment of the present invention, an SIP protocol message is extended and the best-fit server IP list is sent to the client using an extended SIP protocol message comprising the best-fit server IP list.
[0018] Another method of the present invention provides for initiating the binding of a client with a server. A best-fit server IP address is selected by a client from a list of best-fit server IP addresses. An attempt to made by the client to initiate a session with a server using the selected best-fit server IP address. In the event the first attempt to initiate a session fails, a next best- fit server IP address is selected from a best-fit server IP address list. The client makes a next attempt to initiate a session with a server using the next selected best-fit server IP address. In another embodiment of the present invention, the best-fit server IP address list is ordered according to network distribution criteria. Optionally, the distribution criteria are selected from the group consisting of the routing distance between the client and each server associated with each of the list of best-fit server IP addresses, message delivery latency, and server loading. Selecting the first and next best-fit server IP addresses from a best-fit server IP address list comprises selecting the best-fit server IP addresses according to the order in which the best-fit server IP addresses appear on the best-fit server IP address list.
[0019] Another method of the present invention provides for maintaining the binding of a client with a server. A transmission protocol used by the client and the server is extended for communications. The extended transmission protocol is used by a client to request a best-fit server IP list from a server, wherein the best-fit server IP list comprises a list of best-fit server IP addresses. The best-fit server IP list is received and stored by the client. In an embodiment of the present invention, the STUN protocol message is extended and used to request a best-fit server IP list. [0020] In yet another embodiment of the present invention, the client determines whether the IP address of a server is on the best-fit IP address list. In the event that the server is not on the best-fit IP address list, the client terminates its association with the server and selects a best-fit server IP address from a best-fit server IP address list. An attempt is made by the client to initiate a session using the selected best-fit server IP address. In the event the first attempt to initiate a session fails, a next best-fit server IP address is selected from a best-fit server IP address list. A next attempt is made by the client to initiate a session using the next selected best-fit server IP address. Optionally, the best-fit server IP addresses are ordered according to network distribution criteria. The network distribution criteria are selected from the group consisting of the routing distance between the client and each server associated with each of the list of best-fit server IP addresses, message delivery latency, and server loading.
[0021 ] In another embodiment of the present invention, the client determines whether a connection between the client and a server has been lost. In the event that the connection has been lost, a best-fit server IP address is selected from the best-fit server IP address list. An attempt is made by the client to initiate a session using the selected best-fit server IP address. In the event the first attempt to initiate a session fails, a next best-fit server IP address is selected from a best-fit server IP address list. The client makes a next attempt to initiate a session using the next selected best-fit server IP address.
[0022] Optionally, the best-fit server IP addresses are ordered according to network distribution criteria. The network distribution criteria are selected from the group consisting of the routing distance between the client and each server associated with each of the list of best-fit server IP addresses, message delivery latency, and server loading.
DESCRIPTION OF THE FIGURES
[0023] Figure 1 illustrates the interaction of an Internet Appliance with a server according to embodiments of the present invention.
[0024] Figure 2 illustrates a process according to embodiments of the present invention in which an Internet Appliance (client) uses best-fit IP address to create a binding with a server.
[0025] Figure 3 illustrates a process of receiving and verifying a best-fit list by a client according to embodiments of the present invention. DETAILED DESCRIPTION
[0026] Embodiments of the present invention allow a client to receive and maintain a set of "best-fit" server IP addresses. The best fit server IP addresses establish a hierarchy of server addresses that are used by a client to maintain a binding with a server without using the DNS. In the case of an Internet Appliance, the set of best-fit server IP addresses is relatively small. In one embodiment, an Internet Appliance maintains a set of three best-fit server IP addresses. Communicating the set of best-fit server IP addresses to a specific client is accomplished using extensions of network protocols already used to support client/server communications, thus minimizing the amount of code needed to support the additional information transfer.
[0027] Figure 1 illustrates the interaction of an Internet Appliance with a server according to embodiments of the present invention. Referring to Figure 1, an Internet Appliance (client) 100 comprises a protocol engine 110 connected to the Internet 115. The protocol engine 110 communicates via the Internet 115 with a corresponding protocol engine 145 in a server 140. As part of this communication, protocol message 160 comprising best-fit server IP addresses are passed from the server 140 to the Internet Appliance (client) 100. The Internet Appliance (client) 100 extracts this information from the protocol message 160 and saves this information in persistent memory (not illustrated).
[0028] In order to construct the protocol message 160 comprising the best-fit IP addresses, the protocol engine 145 on server 140 is integrated with a best-fit solutions database 155. In this embodiment of the present invention, the best-fit solutions database 155 is updated by an optimizer program 150 that runs as a background application on the server 140. However, this is not meant as a limitation. As would be apparent to those skilled in the art, other means may be used to create the best-fit IP addresses. By way of illustration and not as a limitation, in an embodiment of the present invention, the best-fit IP addresses are computed on-the-fly (by protocol engine 145 or a linked device) based on the latest routing and server availability information.
[0029] Figure 2 illustrates a process according to embodiments of the present invention in which an Internet Appliance (client) uses best-fit IP address to create a binding with a server. Referring to Figure 2, a client initiates contact with a server using the first best-fit IP address in the list 200. If the connection is bound 210 the binding process ends 230. If the client is not bound to a server, a check is made to determine if the last-tried best-fit address was the last address 215. If the last-tried best-fit address was the last address, the binding process is restarted 225. If the last-tried best-fit address is not the last address, contact is initiated using the next best-fit address 220.
[0030] When a binding is successful (230), the connection is checked 235 to determine if the connection has been lost 240. If the connection has not been lost, the checking process 235 is repeated. If the connection has been lost, the binding process is restarted 225. If none of the servers in the best-fit server IP address list 105 respond then, a "catastrophic" failure has occurred. This could be caused because the user's Internet access has been impaired, because a sufficiently large part of the Internet is disabled preventing access to any of the servers in the best-fit list, or because a sufficiently large physical event has caused all the servers in the best- fit list to become inoperable. When a "catastrophic" failure occurs, the client continues to contact the servers on its best-fit list until the network problem is corrected. This re-use of the initialization procedure helps address the constraint of scarce storage resources on the Internet Appliance.
[0031 ] In an embodiment of the present invention, the list of best-fit server IP addresses 105 is ordered such that elements closer to the top of the list are "more optimal" than lower items on the list. Thus, the binding process illustrated in Figure 2 attempts to bind with the more optimal server first. In this context, "more optimal" reflects the result of analysis done prior to the last down load of the best-fit list from the server to the client. Note subsequent to the last sending of the best-fit list and the time when the client is bound to a server, the physical location or Internet "routing distance" may have changed thereby changing the optimization of the best-fit list.
[0032] Figure 3 illustrates a process of receiving and verifying a best-fit list by a client according to embodiments of the present invention. Referring to Figure 3, a client binds with a server 300. A new best-fit server IP address list is received and stored by the client 305 for access during power up initialization. Once stored, the client determines whether it is currently bound to a server having the first best-fit address in the new list 310. If it is not, then the client initiates a binding process as illustrated in Figure 2.
[0033] As previously noted, the server determines the best-fit list of server IP addresses and communicates this information to the client via a extension of a network protocol currently used by the client and server to establish or maintain existing communications. In an embodiment of the present invention, a protocol engine at the server is extended to accept a best-fit server IP address list and communicate it to each client associated with that server. In the event the server associated with a client is no longer on the list of best-fit server IP addresses, the client will terminate the association and attempt to connect with a server on the last-received list. The server represented by the first IP address on the new best-fit list is then associated with the client.
[0034] An embodiment of the present invention extends a network protocol used by a client and server to convey information relating to the best-fit server IP address list. In order to avoid issues with firewalls and network address translation systems, a preferred protocol will support sessions initiated by the client that allow subsequent responses by the server. Additionally, the preferred protocol will support communication at a frequency that facilitates timely communication of new best- fit server IP address lists and be adaptable to accept the simple payload data required for the best-fit server IP address list.
[0035] In an exemplary embodiment of the present invention, a client and server use multiple protocols to send and update best-fit IP address information. By way of illustration and not as a limitation, a server communicates with a client via the Session Initiation Protocol (SIP). This protocol meets the preferred criteria that a session is initiated by the client while allowing the server to send the client a message at any time. However, processing of the SIP protocol for both the client and the server requires considerable work. This is of particular concern where the client resides on an Internet Appliance with very little computation resources. In addition to SIP, the client in this exemplary embodiment also uses the STUN protocol. STUN lacks that quality of being able to respond to a server-generated message at any time, but has the advantage that it is very simple to process and extend. These two protocols, however, are used in combination to perform the tasks of sending a list of best-fist IP addresses to the client and sending the client notice that the list has been updated. The server uses a SIP protocol extension to notify the client. The client uses the STUN protocol to request and receive the new list.
[0036] A system and method for permitting a client running on an Internet Appliance to dynamically bind with at least one server without using DNS has been illustrated. It will be understood by those skilled in the art that the present invention may be embodied in other specific forms without departing from the scope of the invention disclosed and that the examples and embodiments described herein are in all respects illustrative and not restrictive. Those skilled in the art of the present invention will recognize that other embodiments using the concepts described herein are also possible.

Claims

WHAT IS CLAIMED IS:
1. A method for maintaining the binding of a client with a server comprising: at the server, creating a list of best-fit server IP addresses for the client; extending a transmission protocol used by the client and the server for communications to transport the best-fit server IP list; and sending the best-fit server IP list to the client.
2. The method for maintaining the binding of a client with a server of claim 1 , further comprising ordering the best-fit server IP addresses according to network distribution criteria.
3. The method for maintaining the binding of a client with a server of claim 2, wherein the network distribution criteria are selected from the group consisting of the routing distance between the client and each server associated with list of best-fit server IP addresses, message delivery latency, and server loading.
4. The method for maintaining the binding of a client with a server of claim 1, wherein extending a transmission protocol used by the client and server for communications to transport the best-fit server IP list comprises extending a SIP protocol message and wherein sending the sending the best-fit server IP list to the client comprises sending an extended SIP protocol message comprising the best-fit server IP list.
5. A method for initiating the binding of a client with a server comprising: selecting at the client a best-fit server IP address from a list of best-fit server IP addresses; at the client, making an attempt to initiate a session with the server using the selected best-fit server IP address; in the event the first attempt to initiate a session fails, then selecting a next best-fit server IP address from the list of best-fit server IP addresses; and at the client, making a next attempt to initiate the session using the next selected best- fit server IP address.
6. The method for initiating the binding of a client with a server of claim 5, wherein the list of best- fit server IP addresses is ordered according to network distribution criteria, and wherein selecting the first and next best-fit server IP addresses from the list of best-fit server IP addresses list comprises selecting the best-fit server IP addresses according to the order in which best-fit server IP addresses appear on the list of best-fit server IP addresses.
7. The method for initiating the binding of a client with a server of claim 6, wherein the network distribution criteria are selected from the group consisting of the routing distance between the client and each server associated with each of the list of best-fit server IP addresses, message delivery latency, and server loading.
8. A method for maintaining the binding of a client with a server comprising: extending a transmission protocol used by the client and the server for communications; and at the client, using the extended transmission protocol to request a list of best-fit server IP addresses from the server.
9. The method for maintaining the binding of a client with a server of claim 8, wherein the method further comprises: at the client, receiving the list of best-fit server IP addresses; and at the client, storing the list of best-fit server IP addresses.
10. The method for maintaining the binding of a client with a server of claim 8, wherein extending the transmission protocol used by the client and server for communications comprises extending a STUN protocol message, and wherein using the extended transmission protocol to request a list of best-fit server IP addresses from the server comprises sending an extended STUN protocol message comprising the request.
11. The method for maintaining the binding of a client with a server of claim 9, wherein the method further comprises: determining at the client whether the IP address of the server is on the list of best-fit server IP addresses; in the event that the server is not on the list of best-fit server IP addresses, then terminating the association of the client with the server; selecting at the client a best-fit server IP address from the list of best-fit server IP addresses; at the client, making an attempt to initiate a session with the server using the selected best-fit server IP address; in the event the first attempt to initiate a session fails, then selecting a next best-fit server IP address from the list of best-fit server IP addresses; and at the client, making a next attempt to initiate the session using the next selected best- fit server IP address.
12. The method for maintaining the binding of a client with a server of claim 11 , wherein the list of best-fit server IP addresses is ordered according to network distribution criteria, and wherein selecting the first and next best-fit server IP addresses from the list of best-fit server IP addresses comprises selecting the best-fit server IP addresses according to the order in which the best-fit server IP addresses appear on the list of best-fit server IP addresses.
13. The method for maintaining the binding of a client with a server of claim 11 , wherein the network distribution criteria are selected from the group consisting of the routing distance between the client and each server associated with each of the plurality of best-fit server IP addresses, message delivery latency, and server loading.
14. The method for maintaining the binding of a client with a server of claim 9, wherein the method further comprises: determining at the client whether a connection between the client and the server has been lost; in the event that the connection has been lost, then selecting at the client a best-fit server IP address from the list of best-fit server IP addresses; at the client, making an attempt to initiate a session using the selected best-fit server IP address; in the event the first attempt to initiate a session fails, selecting a next best-fit server IP address from the list of best-fit server IP addresses; and at the client, making a next attempt to initiate a session using the next selected best-fit server IP address.
15. The method for maintaining the binding of a client with a server of claim 14, wherein the best-fit server IP address list is ordered according to network distribution criteria, and wherein selecting the first and next best-fit server IP addresses from the list of best-fit server IP addresses comprises selecting the best-fit server JJP addresses according to the order in which the best-fit server IP addresses appear on the list of best-fit server IP addresses.
16. The method for maintaining the binding of a client with a server of claim 11 , wherein the network distribution criteria are selected from the group consisting of the routing distance between the client and each server associated with each of the plurality of best-fit server IP addresses, message delivery latency, and server loading
PCT/US2005/003557 2004-01-28 2005-01-28 System and method for binding a client to a server WO2005072473A2 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US53976804P 2004-01-28 2004-01-28
US60/539,768 2004-01-28
US11/043,680 2005-01-26
US11/043,680 US7676599B2 (en) 2004-01-28 2005-01-26 System and method of binding a client to a server

Publications (2)

Publication Number Publication Date
WO2005072473A2 true WO2005072473A2 (en) 2005-08-11
WO2005072473A3 WO2005072473A3 (en) 2007-03-29

Family

ID=34829774

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2005/003557 WO2005072473A2 (en) 2004-01-28 2005-01-28 System and method for binding a client to a server

Country Status (2)

Country Link
US (4) US7676599B2 (en)
WO (1) WO2005072473A2 (en)

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7957401B2 (en) * 2002-07-05 2011-06-07 Geos Communications, Inc. System and method for using multiple communication protocols in memory limited processors
US7379959B2 (en) * 2002-09-07 2008-05-27 Appistry, Inc. Processing information using a hive of computing engines including request handlers and process handlers
US7333474B2 (en) * 2002-11-19 2008-02-19 Cisco Technology, Inc. Extended handset functionality and mobility
US7606217B2 (en) 2003-07-02 2009-10-20 I2 Telecom International, Inc. System and method for routing telephone calls over a voice and data network
US7676599B2 (en) * 2004-01-28 2010-03-09 I2 Telecom Ip Holdings, Inc. System and method of binding a client to a server
EP1733492A2 (en) * 2004-03-11 2006-12-20 i2Telecom International, Inc. DYNAMICALLY ADAPTING THE TRANSMISSION RATE OF PACKETS IN REAL-TIME VoIP COMMUNICATIONS TO THE AVAILABLE BANDWIDTH
US8804758B2 (en) 2004-03-11 2014-08-12 Hipcricket, Inc. System and method of media over an internet protocol communication
US7782878B2 (en) 2004-08-16 2010-08-24 I2Telecom Ip Holdings, Inc. System and method for sharing an IP address
US20060117020A1 (en) * 2004-12-01 2006-06-01 John Toebes Arrangement for selecting a server to provide distributed services from among multiple servers based on a location of a client device
KR100744782B1 (en) * 2005-11-15 2007-08-02 엘지전자 주식회사 Mobile Terminal and Method for Acquisition Internet Protocol Address thereof
US20070189270A1 (en) * 2006-02-15 2007-08-16 Borislow Daniel M Network adapter
US8364850B2 (en) * 2006-07-20 2013-01-29 Qualcomm Incorporated Utility service in multi-processor environment
EP2060119B1 (en) * 2006-09-05 2010-06-09 TELEFONAKTIEBOLAGET LM ERICSSON (publ) IP unicast streaming service delivery
US7912962B2 (en) 2006-10-06 2011-03-22 Apple Inc. Invitation to bind to a device
CA2686971A1 (en) * 2007-04-03 2008-10-16 Ymax Communications Corp. Techniques for populating a contact list
US7979734B2 (en) * 2007-07-11 2011-07-12 Samsung Electronics Co., Ltd. Method and system for preventing service disruption of internet protocol (IP) based services due to domain name resolution failures
US8504048B2 (en) * 2007-12-17 2013-08-06 Geos Communications IP Holdings, Inc., a wholly owned subsidiary of Augme Technologies, Inc. Systems and methods of making a call
US20090209224A1 (en) * 2008-02-20 2009-08-20 Borislow Daniel M Computer-Related Devices and Techniques for Facilitating an Emergency Call Via a Cellular or Data Network
JP5470720B2 (en) * 2008-03-07 2014-04-16 日本電気株式会社 Event processing system and event processing method
US8433283B2 (en) * 2009-01-27 2013-04-30 Ymax Communications Corp. Computer-related devices and techniques for facilitating an emergency call via a cellular or data network using remote communication device identifying information
US8990411B2 (en) * 2010-04-22 2015-03-24 Microsoft Technology Licensing, Llc Dynamic connection management on mobile peer devices
US20120221603A1 (en) * 2010-07-02 2012-08-30 salesforces.com, Inc. Distributed mobile services
EP3089410A4 (en) * 2013-12-24 2016-12-07 Le Holdings Beijing Co Ltd Node distribution method and control center
US10230683B1 (en) * 2018-02-09 2019-03-12 Capital One Services, Llc Routing for large server deployments
US10681001B2 (en) 2018-03-29 2020-06-09 Akamai Technologies, Inc. High precision mapping with intermediary DNS filtering
US11588749B2 (en) * 2020-05-15 2023-02-21 Cisco Technology, Inc. Load balancing communication sessions in a networked computing environment

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020184376A1 (en) * 2001-05-30 2002-12-05 Sternagle Richard Henry Scalable, reliable session initiation protocol (SIP) signaling routing node
US20030023669A1 (en) * 2001-07-24 2003-01-30 Delima Roberto Dynamic HTTP load balancing method and apparatus
US20030110257A1 (en) * 2001-12-11 2003-06-12 Wook Hyun Method for performing a load distribution between session initiation protocol servers within an intra domain
US6618761B2 (en) * 1998-10-30 2003-09-09 Science Applications International Corp. Agile network protocol for secure communications with assured system availability
US20030204619A1 (en) * 2002-04-26 2003-10-30 Bays Robert James Methods, apparatuses and systems facilitating determination of network path metrics

Family Cites Families (146)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5274693A (en) * 1990-07-17 1993-12-28 Herbert Waldman Abbreviated and enhanced dialing apparatus and methods particularly adapted for cellular or other types of telephone systems
US5805676A (en) * 1995-05-19 1998-09-08 Pcpi Phone, Inc. Telephone/transaction entry device and system for entering transaction data into databases
US5809128A (en) * 1996-11-01 1998-09-15 Interactive Telecom Inc. Method and apparatus permitting notification and control of blocked incoming calls over a data network
US6125113A (en) * 1996-04-18 2000-09-26 Bell Atlantic Network Services, Inc. Internet telephone service
US6859525B1 (en) * 1996-10-23 2005-02-22 Riparius Ventures, Llc Internet telephony device
US6307853B1 (en) * 1996-11-21 2001-10-23 Net2Phone, Inc. Re-routing telephony communications traffic through a private branch exchange to a data network
US6256778B1 (en) * 1996-12-21 2001-07-03 Christopher Oliver Octet iterator template interface for protocol transfer syntax coding services
US6141345A (en) * 1997-03-06 2000-10-31 Lucent Technologies Inc. Signal processing resource allocation for internet-based telephony
US6445694B1 (en) * 1997-03-07 2002-09-03 Robert Swartz Internet controlled telephone system
US6542497B1 (en) * 1997-03-11 2003-04-01 Verizon Services Corp. Public wireless/cordless internet gateway
US6771594B1 (en) 1997-03-31 2004-08-03 Intel Corporation Reliable/non-reliable transmission of voice using TCP/UDP based on network quality of service
US6205154B1 (en) * 1997-04-15 2001-03-20 Lucent Technologies, Inc. Automatic path selection for fiber-optic transmission networks
CA2286338A1 (en) * 1997-04-22 1998-10-29 Telcordia Technologies, Inc. Apparatus and method for internet telephony routing
US6014440A (en) 1997-07-21 2000-01-11 Northern Telecom Limited Inter-half call protocol negotiation techniques
US6006264A (en) * 1997-08-01 1999-12-21 Arrowpoint Communications, Inc. Method and system for directing a flow between a client and a server
US6118768A (en) * 1997-09-26 2000-09-12 3Com Corporation Apparatus and methods for use therein for an ISDN LAN modem utilizing browser-based configuration with adaptation of network parameters
US6091732A (en) * 1997-11-20 2000-07-18 Cisco Systems, Inc. Method for configuring distributed internet protocol gateways with lan emulation
US6389005B1 (en) * 1997-12-01 2002-05-14 Nortel Networks Limited Automatic backup trunking for voice over the internet
US6185288B1 (en) * 1997-12-18 2001-02-06 Nortel Networks Limited Multimedia call signalling system and method
US6353614B1 (en) * 1998-03-05 2002-03-05 3Com Corporation Method and protocol for distributed network address translation
US6351730B2 (en) 1998-03-30 2002-02-26 Lucent Technologies Inc. Low-complexity, low-delay, scalable and embedded speech and audio coding with adaptive frame loss concealment
JP4304734B2 (en) 1998-04-17 2009-07-29 ソニー株式会社 REPRODUCTION DEVICE, DATA REPRODUCTION METHOD, AND RECORDING MEDIUM
US6104757A (en) 1998-05-15 2000-08-15 North Carolina State University System and method of error control for interactive low-bit rate video transmission
US6603774B1 (en) 1998-10-09 2003-08-05 Cisco Technology, Inc. Signaling and handling method for proxy transcoding of encoded voice packets in packet telephony applications
US6654891B1 (en) * 1998-10-29 2003-11-25 Nortel Networks Limited Trusted network binding using LDAP (lightweight directory access protocol)
US7165122B1 (en) * 1998-11-12 2007-01-16 Cisco Technology, Inc. Dynamic IP addressing and quality of service assurance
US6856612B1 (en) 1999-02-24 2005-02-15 Telefonaktiebolaget Lm Ericsson (Publ) Methods and systems for call routing and codec negotiation in hybrid voice/data/internet/wireless systems
US6636504B1 (en) * 1999-03-18 2003-10-21 Verizon Services Corp. Reverse billing of internet telephone calls
US6449251B1 (en) * 1999-04-02 2002-09-10 Nortel Networks Limited Packet mapper for dynamic data packet prioritization
US6954454B1 (en) * 1999-05-03 2005-10-11 Ut Starcom, Inc. Architecture for a central office using IP technology
US7275113B1 (en) * 1999-05-27 2007-09-25 3 Com Corporation Dynamic network address configuration system and method
US6496477B1 (en) 1999-07-09 2002-12-17 Texas Instruments Incorporated Processes, articles, and packets for network path diversity in media over packet applications
US6766348B1 (en) * 1999-08-03 2004-07-20 Worldcom, Inc. Method and system for load-balanced data exchange in distributed network-based resource allocation
US6434139B1 (en) * 1999-08-10 2002-08-13 Lucent Technologies Inc. Method for optimizing mobile wireless communications routed across plural interconnected networks
DE69935138T2 (en) * 1999-08-20 2007-11-22 International Business Machines Corp. System and method for optimizing the performance and availability of a DHCP service
US6760324B1 (en) * 1999-09-10 2004-07-06 Array Telecom Corporation Method, system, and computer program product for providing voice over the internet communication
US6351464B1 (en) * 1999-09-20 2002-02-26 Mci Worldcom, Inc. Virtual second line hybrid network communication system
US6788769B1 (en) * 1999-10-13 2004-09-07 Emediacy, Inc. Internet directory system and method using telephone number based addressing
US7092380B1 (en) * 1999-10-22 2006-08-15 Cisco Technology, Inc. Method and system for providing voice communication over data networks
US6901438B1 (en) * 1999-11-12 2005-05-31 Bmc Software System selects a best-fit form or URL in an originating web page as a target URL for replaying a predefined path through the internet
US6975613B1 (en) * 1999-12-06 2005-12-13 Telefonaktiebolaget L M Ericsson (Publ) System and method for scheduling communication sessions in an ad-hoc network
US7441045B2 (en) * 1999-12-13 2008-10-21 F5 Networks, Inc. Method and system for balancing load distribution on a wide area network
US7886023B1 (en) * 2000-01-21 2011-02-08 Cisco Technology, Inc. Method and apparatus for a minimalist approach to implementing server selection
EP1284069B1 (en) * 2000-01-31 2004-11-10 Aeptec Microsystems, Inc. Broadband communications access device
WO2001058186A1 (en) * 2000-02-01 2001-08-09 Markport Limited A messaging applications router
US6700956B2 (en) * 2000-03-02 2004-03-02 Actiontec Electronics, Inc. Apparatus for selectively connecting a telephone to a telephone network or the internet and methods of use
US6826174B1 (en) 2000-03-02 2004-11-30 3Com Corporation Voice-over-IP interface for standard household telephone
US7173923B2 (en) * 2000-03-17 2007-02-06 Symbol Technologies, Inc. Security in multiple wireless local area networks
WO2001071569A1 (en) * 2000-03-23 2001-09-27 Ali Habib Unified communications and commerce systems and methods, and device therefore
US7191236B2 (en) * 2000-05-02 2007-03-13 Canon Kabushiki Kaisha Transparent telecommunications system and apparatus
US6725303B1 (en) * 2000-08-31 2004-04-20 At&T Corp. Method and apparatus for establishing a personalized connection with a network
US20060074727A1 (en) * 2000-09-07 2006-04-06 Briere Daniel D Method and apparatus for collection and dissemination of information over a computer network
US6996615B1 (en) * 2000-09-29 2006-02-07 Cisco Technology, Inc. Highly scalable least connections load balancing
US6986030B2 (en) * 2000-10-27 2006-01-10 M-Systems Flash Disk Pioneers Ltd. Portable memory device includes software program for interacting with host computing device to provide a customized configuration for the program
US6901429B2 (en) * 2000-10-27 2005-05-31 Eric Morgan Dowling Negotiated wireless peripheral security systems
US7113500B1 (en) * 2000-11-03 2006-09-26 Insors Integrated Communications Method and dial plan for packet based voice communications functionality
US20020131604A1 (en) * 2000-11-08 2002-09-19 Amine Gilbert A. System and method for measuring and enhancing the quality of voice communication over packet-based networks
US7512686B2 (en) * 2000-12-21 2009-03-31 Berg Mitchell T Method and system for establishing a data structure of a connection with a client
US7221663B2 (en) 2001-12-31 2007-05-22 Polycom, Inc. Method and apparatus for wideband conferencing
US20020097843A1 (en) * 2001-01-19 2002-07-25 Ivoice.Com, Inc. Speech activated telephone device for connection to existing telephone
EP1225742A1 (en) * 2001-01-22 2002-07-24 Inventec Appliances Corp. Internet phone using USB interface to transmit signals
US20020138648A1 (en) * 2001-02-16 2002-09-26 Kuang-Chih Liu Hash compensation architecture and method for network address lookup
US6907031B1 (en) * 2001-02-26 2005-06-14 At&T Corp. Customer premises equipment call re-routing technique
WO2002071242A1 (en) * 2001-03-01 2002-09-12 Akamai Technologies, Inc. Optimal route selection in a content delivery network
US7292571B2 (en) * 2001-04-30 2007-11-06 Aol Llc, A Delaware Limited Liability Company Load balancing with direct terminal response
US7145900B2 (en) 2001-05-31 2006-12-05 Go2Call.Com, Inc. Packet-switched telephony call server
US20020191621A1 (en) * 2001-06-14 2002-12-19 Cypress Semiconductor Corp. Programmable protocol processing engine for network packet devices
US6775373B2 (en) 2001-06-14 2004-08-10 Ericsson Inc. System for and method of channel associated signaling backhaul in a routing system
US6944678B2 (en) * 2001-06-18 2005-09-13 Transtech Networks Usa, Inc. Content-aware application switch and methods thereof
US6947417B2 (en) * 2001-06-29 2005-09-20 Ip Unity Method and system for providing media services
US20030002479A1 (en) * 2001-07-02 2003-01-02 International Business Machines Corporation Virtual call center
US7853781B2 (en) * 2001-07-06 2010-12-14 Juniper Networks, Inc. Load balancing secure sockets layer accelerator
US7042841B2 (en) 2001-07-16 2006-05-09 International Business Machines Corporation Controlling network congestion using a biased packet discard policy for congestion control and encoded session packets: methods, systems, and program products
US7827292B2 (en) * 2001-07-23 2010-11-02 At&T Intellectual Property Ii, L.P. Flexible automated connection to virtual private networks
US7046683B1 (en) 2001-07-31 2006-05-16 Cisco Technology, Inc. VoIP over access network
EP1413119B1 (en) * 2001-08-04 2006-05-17 Kontiki, Inc. Method and apparatus for facilitating distributed delivery of content across a computer network
US7162549B2 (en) * 2001-10-29 2007-01-09 Onspec Electronics, Inc. Multimode controller for intelligent and “dumb” flash cards
US7917394B2 (en) * 2001-11-19 2011-03-29 Csg Systems, Inc. System and method for providing access to network services
DE10163478C2 (en) 2001-12-21 2003-12-18 Siemens Ag Method and arrangement for codec negotiation
US20030123388A1 (en) * 2001-12-28 2003-07-03 Patrick Bradd Admissions control in a connectionless communications network
US7212622B2 (en) * 2002-02-14 2007-05-01 Itxc Ip Holdings Sarl Call routing system
US20030161453A1 (en) * 2002-02-25 2003-08-28 Veschi Robert A. Flexible and scalable integrated access device
US9087319B2 (en) * 2002-03-11 2015-07-21 Oracle America, Inc. System and method for designing, developing and implementing internet service provider architectures
US7512702B1 (en) * 2002-03-19 2009-03-31 Cisco Technology, Inc. Method and apparatus providing highly scalable server load balancing
US20030214939A1 (en) * 2002-05-15 2003-11-20 Ismail I. Eldumiati Method and apparatus for providing life line service to access gateway telephony subscribers
US20030219006A1 (en) 2002-05-21 2003-11-27 Har Benjamin Yuh Loong Virtual end-to-end coder/decoder capability in H.323 gateways
US7957401B2 (en) * 2002-07-05 2011-06-07 Geos Communications, Inc. System and method for using multiple communication protocols in memory limited processors
US20040019539A1 (en) * 2002-07-25 2004-01-29 3Com Corporation Prepaid billing system for wireless data networks
US6763226B1 (en) * 2002-07-31 2004-07-13 Computer Science Central, Inc. Multifunctional world wide walkie talkie, a tri-frequency cellular-satellite wireless instant messenger computer and network for establishing global wireless volp quality of service (qos) communications, unified messaging, and video conferencing via the internet
US7653746B2 (en) * 2002-08-02 2010-01-26 University Of Southern California Routable network subnet relocation systems and methods
US7152111B2 (en) * 2002-08-15 2006-12-19 Digi International Inc. Method and apparatus for a client connection manager
AU2003263957A1 (en) * 2002-08-16 2004-03-03 Nuasis Corporation Contact center architecture
US20040032860A1 (en) 2002-08-19 2004-02-19 Satish Mundra Quality of voice calls through voice over IP gateways
US7139926B1 (en) * 2002-08-30 2006-11-21 Lucent Technologies Inc. Stateful failover protection among routers that provide load sharing using network address translation (LSNAT)
US7054420B2 (en) * 2002-09-11 2006-05-30 Telstrat International, Ltd. Voice over IP telephone recording architecture
US20040133668A1 (en) * 2002-09-12 2004-07-08 Broadcom Corporation Seamlessly networked end user device
US8392609B2 (en) * 2002-09-17 2013-03-05 Apple Inc. Proximity detection for media proxies
US7307982B2 (en) 2003-02-21 2007-12-11 Avaya Technology Corp. Apparatus and method for controlling telephony endpoints
US20060276230A1 (en) 2002-10-01 2006-12-07 Mcconnell Christopher F System and method for wireless audio communication with a computer
US20050180464A1 (en) * 2002-10-01 2005-08-18 Adondo Corporation Audio communication with a computer
US7734745B2 (en) * 2002-10-24 2010-06-08 International Business Machines Corporation Method and apparatus for maintaining internet domain name data
US20040086093A1 (en) * 2002-10-29 2004-05-06 Schranz Paul Steven VoIP security monitoring & alarm system
US7269180B2 (en) * 2002-11-04 2007-09-11 World Wide Packets, Inc. System and method for prioritizing and queuing traffic
US7283542B2 (en) * 2002-11-15 2007-10-16 Nortel Networks Limited Network address translator and secure transfer device for interfacing networks
US20040114581A1 (en) * 2002-12-16 2004-06-17 Hans Mathieu Claude Voice-over-IP communicator
US20040205165A1 (en) * 2003-01-21 2004-10-14 Eplication Networks Ltd. Method for improving quality of service from an Internet server employing heuristic optimization of downloading
US20040141758A1 (en) * 2003-01-22 2004-07-22 El-Reedy Jamil O. System and method for providing multiple services to a destination via a fiber optic link
US7411917B1 (en) * 2003-03-26 2008-08-12 Network Equipment Technologies, Inc. Method and system for providing registration-based SIP NAT traversal
US20040205023A1 (en) * 2003-04-08 2004-10-14 First Data Corporation Money transfer convenience card, systems and methods
GB2400522B (en) * 2003-04-12 2007-02-28 Hewlett Packard Development Co Method and associated apparatus for creating a network connection to a network
US7631055B1 (en) * 2003-04-23 2009-12-08 Cisco Technology, Inc. Method and apparatus providing automatic connection announcement from a modular network device to a network management point
US7567549B2 (en) * 2003-04-30 2009-07-28 Microsoft Corporation Computer telephony integration adapter
US7680957B1 (en) * 2003-05-09 2010-03-16 Symantec Operating Corporation Computer system configuration representation and transfer
US7342879B2 (en) * 2003-05-09 2008-03-11 Avaya Technology Corp. Method and apparatus for detection of prioritization and per hop behavior between endpoints on a packet network
US7430187B2 (en) * 2003-05-15 2008-09-30 At&T Intellectual Property I, Lp Methods, systems, and computer program products for providing different quality of service/bandwidth allocation to different susbscribers for interactive gaming
US20040248590A1 (en) 2003-06-06 2004-12-09 Kevin Chan Apparatus and method for presence-based call routing using computers
US7359963B1 (en) * 2003-06-09 2008-04-15 Microsoft Corporation System and method for maintaining and publishing web site content
US6795540B1 (en) * 2003-06-09 2004-09-21 John Beck Mow Premised based 3-way call detection device
US7746799B2 (en) 2003-06-20 2010-06-29 Juniper Networks, Inc. Controlling data link layer elements with network layer elements
US7606217B2 (en) * 2003-07-02 2009-10-20 I2 Telecom International, Inc. System and method for routing telephone calls over a voice and data network
US7287077B2 (en) * 2003-08-07 2007-10-23 International Business Machines Corporation Reservation of TCP/UDP ports using UID, GID or process name
US7599355B2 (en) * 2003-08-14 2009-10-06 Aksys Networks Inc. Server-less VoIP (voice over internet protocol) phone system
US7783777B1 (en) * 2003-09-09 2010-08-24 Oracle America, Inc. Peer-to-peer content sharing/distribution networks
US7539760B1 (en) * 2003-09-12 2009-05-26 Astute Networks, Inc. System and method for facilitating failover of stateful connections
US7324473B2 (en) * 2003-10-07 2008-01-29 Accenture Global Services Gmbh Connector gateway
US7325133B2 (en) * 2003-10-07 2008-01-29 Koolspan, Inc. Mass subscriber management
US7478169B2 (en) * 2003-10-16 2009-01-13 International Business Machines Corporation Accessing data processing systems behind a NAT enabled network
US7496648B2 (en) * 2003-10-23 2009-02-24 Microsoft Corporation Managed peer name resolution protocol (PNRP) interfaces for peer to peer networking
US7376129B2 (en) * 2003-10-29 2008-05-20 International Business Machines Corporation Enabling collaborative applications using Session Initiation Protocol (SIP) based Voice over Internet protocol Networks (VoIP)
US7213766B2 (en) * 2003-11-17 2007-05-08 Dpd Patent Trust Ltd Multi-interface compact personal token apparatus and methods of use
US7762470B2 (en) * 2003-11-17 2010-07-27 Dpd Patent Trust Ltd. RFID token with multiple interface controller
US7554981B2 (en) * 2003-11-26 2009-06-30 Wind River Systems, Inc. System and method for efficient storage and processing of IPv6 addresses
US7302053B2 (en) 2003-12-01 2007-11-27 International Business Machines Corporation System and method for providing a communication session
US7571235B2 (en) * 2003-12-19 2009-08-04 Nortel Networks Limited Computer telephone integration over a network
US7525925B2 (en) * 2003-12-31 2009-04-28 Stmicroelectronics Asia Pacific Pte. Ltd. System and method for selecting an optimal transport format combination using progressive set reduction
US7860978B2 (en) * 2004-01-22 2010-12-28 Toshiba America Research, Inc. Establishing a secure tunnel to access router
US7676599B2 (en) 2004-01-28 2010-03-09 I2 Telecom Ip Holdings, Inc. System and method of binding a client to a server
US7656895B2 (en) * 2004-03-04 2010-02-02 Wiline Networks, Inc. Method and device for coupling a POTS terminal to a non-PSTN communications network
EP1733492A2 (en) * 2004-03-11 2006-12-20 i2Telecom International, Inc. DYNAMICALLY ADAPTING THE TRANSMISSION RATE OF PACKETS IN REAL-TIME VoIP COMMUNICATIONS TO THE AVAILABLE BANDWIDTH
JP4574366B2 (en) * 2004-03-30 2010-11-04 要二 竹内 CD-ROM, management server, operation server, and IP telephone terminal registration method in which a program for functioning as an IP telephone terminal is recorded
US7596096B2 (en) * 2004-04-29 2009-09-29 Avaya Inc Method and apparatus for providing trace route and timing information for media streams
US7684549B2 (en) * 2004-07-08 2010-03-23 At&T Intellectual Property I, Lp System and method for managing messages in a packetized voice environment
EP1771998B1 (en) * 2004-07-23 2015-04-15 Citrix Systems, Inc. Systems and methods for optimizing communications between network nodes
EP1771979B1 (en) * 2004-07-23 2011-11-23 Citrix Systems, Inc. A method and systems for securing remote access to private networks
US7782878B2 (en) * 2004-08-16 2010-08-24 I2Telecom Ip Holdings, Inc. System and method for sharing an IP address
US7336654B2 (en) * 2004-10-20 2008-02-26 I2Telecom International, Inc. Portable VoIP service access module

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6618761B2 (en) * 1998-10-30 2003-09-09 Science Applications International Corp. Agile network protocol for secure communications with assured system availability
US20020184376A1 (en) * 2001-05-30 2002-12-05 Sternagle Richard Henry Scalable, reliable session initiation protocol (SIP) signaling routing node
US20030023669A1 (en) * 2001-07-24 2003-01-30 Delima Roberto Dynamic HTTP load balancing method and apparatus
US20030110257A1 (en) * 2001-12-11 2003-06-12 Wook Hyun Method for performing a load distribution between session initiation protocol servers within an intra domain
US20030204619A1 (en) * 2002-04-26 2003-10-30 Bays Robert James Methods, apparatuses and systems facilitating determination of network path metrics

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CAMARILLO G. ET AL.: 'Integration of Resource Management and SIP' RFC 3312 October 2002, XP015009089 *
ROSENBERG J. ET AL.: 'STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)' RFC 3489 March 2003, XP015009272 *
SCHULZRINNE H. ET AL.: 'Dynamic Host Configuration Protocol Option for SIP' RFC 3361 August 2002, XP015009120 *

Also Published As

Publication number Publication date
US20140181184A1 (en) 2014-06-26
US7676599B2 (en) 2010-03-09
US9888066B2 (en) 2018-02-06
US8606874B2 (en) 2013-12-10
US20090327414A1 (en) 2009-12-31
US9401974B2 (en) 2016-07-26
US20060031393A1 (en) 2006-02-09
WO2005072473A3 (en) 2007-03-29
US20160359961A1 (en) 2016-12-08

Similar Documents

Publication Publication Date Title
US7676599B2 (en) System and method of binding a client to a server
US11451472B2 (en) Request routing based on class
US11297167B2 (en) System providing faster and more efficient data communication
US6813635B1 (en) System and method for distributing load among redundant independent stateful world wide web server sites
US7409420B2 (en) Method and apparatus for session replication and failover
US7702791B2 (en) Hardware load-balancing apparatus for session replication
US5774660A (en) World-wide-web server with delayed resource-binding for resource-based load balancing on a distributed resource multi-node network
US8156199B1 (en) Centralized control of client-side domain name resolution using VPN services
US7415536B2 (en) Address query response method, program, and apparatus, and address notification method, program, and apparatus
EP1415236B1 (en) Method and apparatus for session replication and failover
US8850056B2 (en) Method and system for managing client-server affinity
US20070150602A1 (en) Distributed and Replicated Sessions on Computing Grids
US8423670B2 (en) Accessing distributed services in a network
CA2430416A1 (en) A method and apparatus for discovering client proximity using multiple http redirects
WO2004092884A2 (en) Method of executing and edge-enabled application in a content delivery network (cdn)
AU2002329602A1 (en) Method and apparatus for session replication and failover

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase