Recherche Images Maps Play YouTube Actualités Gmail Drive Plus »
Connexion
Les utilisateurs de lecteurs d'écran peuvent cliquer sur ce lien pour activer le mode d'accessibilité. Celui-ci propose les mêmes fonctionnalités principales, mais il est optimisé pour votre lecteur d'écran.

Brevets

  1. Recherche avancée dans les brevets
Numéro de publicationUS6141687 A
Type de publicationOctroi
Numéro de demandeUS 09/074,498
Date de publication31 oct. 2000
Date de dépôt8 mai 1998
Date de priorité8 mai 1998
État de paiement des fraisCaduc
Autre référence de publicationUS6526444
Numéro de publication074498, 09074498, US 6141687 A, US 6141687A, US-A-6141687, US6141687 A, US6141687A
InventeursDana L. Blair
Cessionnaire d'origineCisco Technology, Inc.
Exporter la citationBiBTeX, EndNote, RefMan
Liens externes: USPTO, Cession USPTO, Espacenet
Using an authentication server to obtain dial-out information on a network
US 6141687 A
Résumé
A method for using an authentication server to obtain dial-out information about a network including the steps of receiving a destination network address to the authentication server; obtaining a network number and a corresponding network mask from a database; applying said network mask to said destination network address and comparing the result to said network number; retrieving a profile corresponding to said network number and network mask from a database if said network number matches the result of applying said network mask to said destination network address; and repeating said obtaining, applying, and retrieving steps if said network number does not match the result of applying said network mask to said destination network address.
Images(2)
Previous page
Next page
Revendications(27)
What is claimed is:
1. A method for using an authentication server to obtain dial out information about a network, including the steps of:
receiving a destination network address;
obtaining a network number and a corresponding network mask from a database;
applying said network mask to said destination network address and comparing the result to said network number;
retrieving a profile from a server, said profile corresponding to said network number and network mask from a database if said network number matches the result of applying said network mask to said destination network address, wherein said profile includes a phone number; and
repeating said obtaining, applying, and retrieving steps if said network number does not match the result of applying said network mask to said destination network address.
2. The method of claim 1, wherein said obtaining step includes the steps of:
removing a profile from a database; and
obtaining a network number and a corresponding network mask from said profile.
3. The method of claim 2, wherein said profile from said removing step and said profile from said retrieving step are the same profile.
4. The method of claim 2, wherein said profile may contain more than one pair of network numbers and corresponding network masks.
5. The method of claim 1, further including the step of:
locating dial out information in said profile.
6. The method of claim 5, further including the step of:
forwarding said dial out information to an access server.
7. The method of claim 1, further including the step of:
forwarding said profile to an access server.
8. A method for using an authentication server, including the steps of:
receiving information;
determining if said information is a destination network address or a username;
obtaining a network number and a corresponding network mask from a database if said information is a destination network address;
applying said network mask to said destination network address and comparing the result to said network number if said information is a destination network address;
retrieving a profile from a server, said profile corresponding to said network number and network mask from a database if said network number matches the result of applying said network mask to said destination network address and if said information is a destination network address, wherein said profile includes a phone number;
repeating said obtaining, applying, and retrieving steps if said network number does not match the result of applying said network mask to said destination network address and if said information is a destination network address; and
extracting a profile from a server, said profile corresponding to said username from a database if said information is a username.
9. The method of claim 8, wherein said retrieving step includes the steps of:
removing a profile from a database; and
obtaining a network number and a corresponding network mask from said profile.
10. The method of claim 9, wherein said profile from said removing step and said profile from said retrieving step are the same profile.
11. The method of claim 9, wherein said profile may contain more than one pair of network numbers and corresponding network masks.
12. The method of claim 8, further including the step of:
locating dial out information in said profile.
13. The method of claim 12, further including the step of:
forwarding said dial out information to an access server.
14. The method of claim 8, further including the step of:
forwarding said profile to an access server.
15. An computer network including:
an authentication server;
an access server which passes a destination network address to an authentication server;
said authentication server including:
a first database searcher which obtains a network number and a corresponding network mask from a database;
a de-masker which applies said network mask to said destination network address and compares the result to said network number;
a second database searcher which retrieves a profile from a server, said profile corresponding to said network number and network mask from a database if said network number matches the result of applying said network mask to said destination network address, wherein said profile includes a phone number; and
a repeater which activates said first database searcher, said de-masker, and said second database searcher continuously until said network number matches the result of applying said network mask to said destination network address.
16. The computer network of claim 15, wherein said first database searcher includes:
a profile remover which removes a profile from a database; and
a profile reader which obtains a network number and a corresponding network mask from said profile.
17. The computer network of claim 16, wherein said first database searcher and said second database searcher retrieve the same profile.
18. The computer network of claim 15, wherein said profile may contain more than one pair of network numbers and corresponding network masks.
19. The computer network of claim 15, wherein said authentication server further includes:
a profile reader which locates dial out information in said profile.
20. The computer network of claim 19, wherein said authentication server further includes:
an information forwarder which forwards said dial out information to said access server.
21. The computer network of claim 15, wherein said authentication server further includes:
a profile forwarder which forwards said profile to an access server.
22. A computer network including:
an authentication server;
an access server which passes a destination network address to an authentication server;
said authentication server including:
a determiner which determines if said information is a destination network address or a username;
a first database searcher which obtains a network number and a corresponding network mask from a database if said information is a destination network address;
a de-masker which applies said network mask to said destination network address and compares the result to said network number if said information is a destination network address;
a second database searcher which retrieves a profile from a server, said profile corresponding to said network number and network mask from a database if said network number matches the result of applying said network mask to said destination network address and if said information is a destination network address, wherein said profile includes a phone number;
a repeater which activates said first database searcher, said de-masker, and said second database searcher continuously if said information is a destination network address until said network number matches the result of applying said network mask to said destination network address; and
a profile extractor which extracts a profile from a server, said profile corresponding to said username from a database if said information is a username.
23. The computer network of claim 22, wherein said first database searcher includes:
a profile remover which removes a profile from a database; and
a profile reader which obtains a network number and a corresponding network mask from said profile.
24. The computer network of claim 23, wherein said first database searcher and said second database searcher retrieve the same profile.
25. The computer network of claim 22, wherein said profile may contain more than one pair of network numbers and corresponding network masks.
26. The computer network of claim 22, wherein said authentication server further includes:
a profile reader which locates dial out information in said profile.
27. The computer network of claim 26, wherein said authentication server further includes:
an information forwarder which forwards said dial out information to said access server.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to the field of computer networking. More particularly, the present invention relates to using an authentication server to obtain dial-out information on a network, the dial-out information being used to dial another network for the purpose of forwarding a data packet.

2. The Background Art

There are two general types of dial operations that may be performed by a network. These are dial-in and dial-out. A dial-in operation is performed when a user, or even another network, wishes to gain access to a network. The remote user or network dials the network to connect to it. This dial operation may comprise using a modem and dialing a phone number through the phone company, or it may comprise any other type of network communication, including gaining access through a publicly switched network or similar high speed design. The remote user or network is therefore initiating contact, and the destination network simply performs a passive dial-in operation, which allows it to receive the call.

Many consumers are remote users, wherein they dial an Internet Service Provider (ISP) on their modem and log in to the remote user. There are other types of remote users as well, including users who dial directly into a server, but ISP access is the most popular. The process by which a network authenticates such a user is as follows. During this dial-in operation, when a connection is made, a device known as an access server prompts the user for a username and a password. This username and password is then passed to an authentication server. The authentication server looks up the username in a database which has been indexed by usernames. When it finds the username in the database it retrieves the appropriate password and other relevant information about the user. If either the username or the password is not correct, the user is denied access to the network, otherwise access is granted.

A remote network is most commonly used in telecommuting applications, where the user requires faster access to a network. The network inside the user's house is connected to a publicly switched network. Rather than using a modem, a router or bridge is initiating the connection process. Authentication of a user is accomplished in a similar manner to that of remote users. An authentication server verifies that the remote network should have access using the username and a password.

A dial-out operation provides for the opposite effect of a dial-in operation. Here, the network is initiating connection to a remote network. It is also possible for the network to attempt to connect to a remote user. This connection may be made in an effort to provide access for an extended period of time, such as a first network connecting to a second network for the purpose of performing a search in a database residing on the second network.

Many networks, however, such as the Internet, also use networks simply to forward information to another network. An example of this is depicted in FIG. 1. In FIG. 1, node A 2 on network X 4 passes information to node B 6 on network Z 8. In order to perform this, router 10 must pass the information to router 12. However, network X 4 and network Z 8 are not directly connected, but are instead separated by network Y 14 having router 16. Thus, router 10 must pass the information through router 16 to router 12. Router 16 is called a hop. Router 16 is expected to forward the information to another hop on the network or to the final destination of the information (if possible). Thus, in this example, the IP packet takes one hop to get to its destination.

In order to properly forward the information, a router must examine the intended address of the information, extract the information as to which network it must be forwarded, then look up the network in a database in order to determine how to connect to that network. Generally, this database will contain the phone number or other dial-out information on the appropriate network. In the Internet example depicted in FIG. 1, an access server on network Y 10 extracts the destination IP address from the IP packet that is being sent. It then looks up the address information in the database and retrieves a phone number for network Z 8, which it dials and then forwards the IP packet to that network.

The drawback of this method is that the steps are generally performed by the access server of the network. The access server is intended simply to be a device which connects devices to a network through network and terminal emulation software, not to perform searches on a database. The access server is not scalable and therefore the memory and speed of the access server is limited. Using the access server to look up the dial-out information in a database wastes valuable resources which could be used for network connection. It would be preferable to offload this process to another device. Currently, however, there are no network devices designed to perform this task other than an access server.

BRIEF DESCRIPTION OF THE INVENTION

A method for using an authentication server to obtain dial-out information about a network including the steps of receiving a destination network address; obtaining a network number and a corresponding network mask from a database; applying said network mask to said destination network address and comparing the result to said network number; retrieving a profile corresponding to said network number and network mask from a database if said network number matches the result of applying said network mask to said destination network address; and repeating said obtaining, applying, and retrieving steps if said network number does not match the result of applying said network mask to said destination network address.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing an example of a network having several subnetworks.

FIG. 2 is a diagram of the general format of a destination IP address.

FIG. 3 is a diagram showing an example of a destination IP address.

FIG. 4 is a diagram showing an example of a network mask.

FIG. 5 is a flow diagram showing a method of using an authentication server to obtain dial-out information on a network in accordance with a presently preferred embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

Those of ordinary skill in the art will realize that the following description of the present invention is illustrative only and not in any way limiting. Other embodiments of the invention will readily suggest themselves to such skilled persons.

Offloading the process of looking up dial out information on other networks from the access server to the authentication server would greatly increase the productivity of the network. The problem with incorporating this process into the authentication server is that authentication servers currently only has the ability to look up profiles based on the username it is passed. When dealing with information which is being passed through a network to a final destination outside the network (i.e. using the network as only a hop), a username is simply not provided within the packets transported to a network. However, the destination address is always provided in such a packet. It is therefore possible to use the destination address with the authentication server to retrieve the dial-out information needed.

In the Internet Protocol (IP), destination addresses are generally four octets long. Additionally, they make up two distinct parts: a network portion and a host portion. FIG. 2 depicts how a destination address may contain these parts. The network portion 20 contains a network number, which corresponds to the destination network of the IP packet. Network numbers are assigned when each link on a network is attached. Each of these network numbers is unique to each network. The host portion 22, on the other hand, contains a host number, which corresponds to the precise destination system of the IP packet.

The network and host portions of a destination IP address may be oriented in any fashion. FIG. 3 depicts the simplest example of their orientation, where the entire network portion 40 comes before the entire host portion 42. The lengths of the network and host portions are variable. Additionally, it is possible to have the network portion and the host portion intermixed within the destination IP address. However, many systems require that the portions be contiguous as non-contiguous portions can lead to ambiguities.

In order to split a destination address into its network portion and its host portion, a network mask is used. A network mask is a number which indicates which part of the destination address is the network portion and which part is the host portion. FIG. 4 depicts an example of a network mask. A "1" in a particular bit indicates that the corresponding bit in the destination address is part of the network portion while a "0" in a particular bit indicates that the corresponding bit in the destination address is part of the host portion. In FIG. 4, the network mask 50 contains 18 "1"s followed by 14 "0"s. This indicates that the first 18 bits of the destination address are the network portion and the last 14 bits are the host portion.

The presently preferred embodiment of the invention involves a system where the dial-out information for a particular network is stored in a database in a profile corresponding to the particular network. This profile may then be retrieved in accordance with the present invention. FIG. 5 depicts a method for obtaining dial-out information from an authentication server in accordance with a presently preferred embodiment of the present invention. At step 60, the destination IP address is received. Normally, the destination IP address would have originally been received by the access server, which would then pass it to the authentication server. At step 62, the authentication server obtains a network number and a corresponding network mask from a database. This pair will normally be contained in a profile which also contains the dial-out information which will be used later. Therefore, step 62 will normally include retrieving a profile and holding that profile in some sort of memory store in case the profile turns out to be the correct one. However, the retrieval of many different profiles until a match is found can be very time consuming. Therefore, the designer may wish to store the network mask and number pairs in a separate database,. This will result in having two separate profiles for each network number and network mask pair, one profile containing only the pair and a reference to a second profile, the second profile located in another database and containing the dial out information.

At step 64, the network mask is applied to the destination address and the result is compared to the network number. At step 66, if they do not match, the process moves back to step 62. If they do match, however, then the process moves to step 68 where a profile is retrieved from a database, the profile corresponding to the network number and network mask. Again, if the designer chooses to have each profile contain both the network number and network mask pair and the dial out information, then this step will really only involve referencing the profile that has already been retrieved. If, however, separate profiles are used, then this step involves retrieving the second profile from the separate database. It is also possible for each profile to contain multiple network number and mask pairs. This would occur in a situation where a network is assigned multiple network numbers.

At step 70, the dial out information in the profile is located. Then at step 72, this information may be passed to access server for use in dialing the network and passing the IP information to the network.

While embodiments and applications of this invention have been shown and described, it would be apparent to those skilled in the art that many more modifications than mentioned above are possible without departing from the inventive concepts herein. The invention, therefore, is not to be restricted except in the spirit of the appended claims.

Citations de brevets
Brevet cité Date de dépôt Date de publication Déposant Titre
US5003595 *29 août 198926 mars 1991At&T Bell LaboratoriesSecure dial access to computer systems
US5241599 *2 oct. 199131 août 1993At&T Bell LaboratoriesCryptographic protocol for secure communications
US5530963 *16 déc. 199325 juin 1996International Business Machines CorporationMethod and system for maintaining routing between mobile workstations and selected network workstation using routing table within each router device in the network
US5561703 *6 juil. 19941 oct. 1996Rolm CompanySystem and method for integration of a paging server into a private branch exchange environment
US5621721 *12 janv. 199515 avr. 1997Stratacom, Inc.Maintaining database integrity throughout a communication network
US5752242 *18 avr. 199612 mai 1998Electronic Data Systems CorporationSystem and method for automated retrieval of information
US5802316 *26 janv. 19961 sept. 1998Ito; YujiRouters connecting LANs through public network
US5809254 *20 oct. 199715 sept. 1998Nec CorporationData communication mechanism capable of producing data packet having optimal segment size in communication system
US5812776 *7 juin 199522 sept. 1998Open Market, Inc.Method of providing internet pages by mapping telephone number provided by client to URL and returning the same in a redirect command by server
US5835720 *17 mai 199610 nov. 1998Sun Microsystems, Inc.IP discovery apparatus and method
US5835727 *9 déc. 199610 nov. 1998Sun Microsystems, Inc.Method and apparatus for controlling access to services within a computer network
US5845070 *18 déc. 19961 déc. 1998Auric Web Systems, Inc.Security system for internet provider transaction
US5857074 *16 août 19965 janv. 1999Compaq Computer Corp.Server controller responsive to various communication protocols for allowing remote communication to a host computer connected thereto
US5898780 *9 oct. 199627 avr. 1999Gric Communications, Inc.Method and apparatus for authorizing remote internet access
US5901214 *12 nov. 19964 mai 1999Murex Securities, Ltd.One number intelligent call processing system
US5918016 *10 juin 199729 juin 1999Texas Instruments IncorporatedSystem with program for automating protocol assignments when newly connected to varing computer network configurations
US5958016 *13 juil. 199728 sept. 1999Bell Atlantic Network Services, Inc.Internet-web link for access to intelligent network service control
US5974453 *8 oct. 199726 oct. 1999Intel CorporationMethod and apparatus for translating a static identifier including a telephone number into a dynamically assigned network address
Citations hors brevets
Référence
1Bellare et al., "Keying Hash Functions for Message Authentication", 1996, Advances in Cryptology-Crypto 96 Proceedings, Lecture Notes in Computer Science, vol. 1109, N. Koblitz ed., Springer-Verlag.
2 *Bellare et al., Keying Hash Functions for Message Authentication , 1996, Advances in Cryptology Crypto 96 Proceedings, Lecture Notes in Computer Science, vol. 1109, N. Koblitz ed., Springer Verlag.
3Bellovin, Steven M., "Problem Areas for the IP Security Protocols", Jul. 22-25, 1996, Proceedings of the Sixth Usenix UNIX Security Symposium, San Jose, CA.
4 *Bellovin, Steven M., Problem Areas for the IP Security Protocols , Jul. 22 25, 1996, Proceedings of the Sixth Usenix UNIX Security Symposium, San Jose, CA.
Référencé par
Brevet citant Date de dépôt Date de publication Déposant Titre
US62533272 déc. 199826 juin 2001Cisco Technology, Inc.Single step network logon based on point to point protocol
US626336930 oct. 199817 juil. 2001Cisco Technology, Inc.Distributed architecture allowing local user authentication and authorization
US62860398 avr. 19984 sept. 2001Cisco Technology, Inc.Automatic static to dynamic IP address and DNS address management for remote communications network access
US62983834 janv. 19992 oct. 2001Cisco Technology, Inc.Integration of authentication authorization and accounting service and proxy service
US630161811 sept. 20009 oct. 2001Cisco Technology, Inc.Forced sequential access to specified domains in a computer network
US63112753 août 199830 oct. 2001Cisco Technology, Inc.Method for providing single step log-on access to a differentiated computer network
US632458519 nov. 199827 nov. 2001Cisco Technology, Inc.Method and apparatus for domain name service request resolution
US63816463 nov. 199830 avr. 2002Cisco Technology, Inc.Multiple network connections from a single PPP link with partial network address translation
US63856532 nov. 19987 mai 2002Cisco Technology, Inc.Responding to network access requests using a transparent media access and uniform delivery of service
US63968332 déc. 199828 mai 2002Cisco Technology, Inc.Per user and network routing tables
US642500322 janv. 199923 juil. 2002Cisco Technology, Inc.Method and apparatus for DNS resolution
US64271708 déc. 199830 juil. 2002Cisco Technology, Inc.Integrated IP address management
US64306196 mai 19996 août 2002Cisco Technology, Inc.Virtual private data network session count limitation
US64600849 avr. 19991 oct. 2002Cisco Technology, Inc.Forced network portal
US64669776 mai 199915 oct. 2002Cisco Technology, Inc.Proxy on demand
US646704915 oct. 199915 oct. 2002Cisco Technology, Inc.Method and apparatus for configuration in multi processing engine computer systems
US649029030 déc. 19983 déc. 2002Cisco Technology, Inc.Default internet traffic and transparent passthrough
US65021923 sept. 199831 déc. 2002Cisco Technology, Inc.Security between client and server in a computer network
US6526444 *29 sept. 200025 févr. 2003Cisco Technology, Inc.Using an authentication server to obtain dial-out information on a network
US65299556 mai 19994 mars 2003Cisco Technology, Inc.Proxy session count limitation
US653943110 août 199925 mars 2003Cisco Technology, Inc.Support IP pool-based configuration
US658746810 févr. 19991 juil. 2003Cisco Technology, Inc.Reply to sender DHCP option
US659130421 juin 19998 juil. 2003Cisco Technology, Inc.Dynamic, scaleable attribute filtering in a multi-protocol compatible network access environment
US662564511 juil. 200123 sept. 2003Cisco Technology, Inc.Automatic static to dynamic IP address and DNS address management for remote communications network access
US664378214 juin 20014 nov. 2003Cisco Technology, Inc.Method for providing single step log-on access to a differentiated computer network
US66548014 janv. 199925 nov. 2003Cisco Technology, Inc.Remote system administration and seamless service integration of a data communication network management system
US666828321 mai 199923 déc. 2003Cisco Technology, Inc.ISDN B-channel count limitation
US671846728 oct. 19996 avr. 2004Cisco Technology, Inc.Password based protocol for secure communications
US673217812 juil. 20024 mai 2004Cisco Technology, Inc.Forced network portal
US67421267 oct. 199925 mai 2004Cisco Technology, Inc.Method and apparatus for identifying a data communications session
US677166531 août 20003 août 2004Cisco Technology, Inc.Matching of RADIUS request and response packets during high traffic volume
US67924577 juin 200014 sept. 2004Cisco Systems, Inc.Multiple-level internet protocol accounting
US681690131 janv. 20039 nov. 2004Cisco Technology, Inc.Proxy session count limitation
US683932430 mars 19994 janv. 2005Cisco Technology, Inc.Method and apparatus providing dial on demand scaling
US68954343 janv. 200017 mai 2005Cisco Technology, Inc.Sharing of NAS information between PoPs
US691006720 juin 200221 juin 2005Cisco Technology, Inc.Virtual private data network session count limitation
US691804415 oct. 199912 juil. 2005Cisco Technology, Inc.Password protection for high reliability computer systems
US69524036 déc. 20044 oct. 2005Cisco Technology, Inc.Method and apparatus providing dial on demand scaling
US696600414 août 200315 nov. 2005Cisco Technology, Inc.Method for providing single step log-on access to a differentiated computer network
US698297828 févr. 20023 janv. 2006Cisco Technology, Inc.Per user and network routing tables
US698593520 déc. 200010 janv. 2006Cisco Technology, Inc.Method and system for providing network access to PPP clients
US698814819 janv. 200117 janv. 2006Cisco Technology, Inc.IP pool management utilizing an IP pool MIB
US703614211 févr. 200225 avr. 2006Cisco Technology, Inc.Single step network logon based on point to point protocol
US70435537 oct. 19999 mai 2006Cisco Technology, Inc.Method and apparatus for securing information access
US7047563 *7 déc. 200016 mai 2006Cisco Technology, Inc.Command authorization via RADIUS
US71651227 juin 200216 janv. 2007Cisco Technology, Inc.Dynamic IP addressing and quality of service assurance
US717794710 juin 200213 févr. 2007Cisco Technology, Inc.Method and apparatus for DNS resolution
US71975494 juin 200127 mars 2007Cisco Technology, Inc.On-demand address pools
US73466977 sept. 200418 mars 2008Cisco Technology, Inc.Multiple-level internet protocol accounting
US738935411 déc. 200017 juin 2008Cisco Technology, Inc.Preventing HTTP server attacks
US741198122 juin 200412 août 2008Cisco Technology, Inc.Matching of radius request and response packets during high traffic volume
US74209324 avr. 20022 sept. 2008Cisco Technology, Inc.Default internet traffic and transparent passthrough
US74438654 avr. 200228 oct. 2008Cisco Technology, Inc.Multiple network connections from a single PPP link with network address translation
US74933951 sept. 200417 févr. 2009Cisco Technology, Inc.Virtual private data network session count limitation
US750605430 juin 200317 mars 2009Cisco Technology, Inc.Local authentication of a client at a network device
US752982610 mars 20055 mai 2009Cisco Technology, Inc.Sharing of NAS information between PoPs
US7539194 *27 avr. 200526 mai 2009Cisco Technology, Inc.Per user and network routing tables
US754582025 mai 20059 juin 2009Cisco Technology, Inc.Apparatus and method for automatic cluster network device address assignment
US755495915 oct. 200330 juin 2009Cisco Technology, Inc.Apparatus and method for cluster network device discovery
US755886330 janv. 20037 juil. 2009Cisco Technology, Inc.Support IP pool-based configuration
US757063630 août 20054 août 2009Damaka, Inc.System and method for traversing a NAT device for peer-to-peer hybrid communications
US757772525 févr. 200018 août 2009Cisco Technology, Inc.IP address allocation in a network environment
US75809998 oct. 200325 août 2009Cisco Technology, Inc.Remote system administration and seamless service integration of a data communication network management system
US758749312 déc. 20058 sept. 2009Cisco Technology, Inc.Local network address management
US760624610 avr. 200620 oct. 2009Cisco Technology, Inc.Proxy on demand
US762347615 mai 200624 nov. 2009Damaka, Inc.System and method for conferencing in a peer-to-peer hybrid communications network
US762351629 déc. 200624 nov. 2009Damaka, Inc.System and method for deterministic routing in a peer-to-peer hybrid communications network
US76444398 sept. 20045 janv. 2010Cisco Technology, Inc.Timing attacks against user logon and network I/O
US765687015 mars 20052 févr. 2010Damaka, Inc.System and method for peer-to-peer hybrid communications
US777818729 déc. 200617 août 2010Damaka, Inc.System and method for dynamic stability in a peer-to-peer hybrid communications network
US778834513 sept. 200131 août 2010Cisco Technology, Inc.Resource allocation and reclamation for on-demand address pools
US793326017 oct. 200526 avr. 2011Damaka, Inc.System and method for routing and communicating in a heterogeneous network environment
US800032510 août 200916 août 2011Damaka, Inc.System and method for peer-to-peer hybrid communications
US800958627 janv. 200630 août 2011Damaka, Inc.System and method for data transfer in a peer-to peer hybrid communication network
US8050272 *15 mai 20061 nov. 2011Damaka, Inc.System and method for concurrent sessions in a peer-to-peer hybrid communications network
US807773823 juin 200813 déc. 2011Cisco Technology, Inc.Default internet traffic and transparent passthrough
US813957830 juin 200920 mars 2012Damaka, Inc.System and method for traversing a NAT device for peer-to-peer hybrid communications
US821844425 août 201110 juil. 2012Damaka, Inc.System and method for data transfer in a peer-to-peer hybrid communication network
US828584823 juil. 20099 oct. 2012Cisco Technology, Inc.IP address allocation in a network environment
US832156712 déc. 200527 nov. 2012Cisco Technology, Inc.IP pool management utilizing an IP pool MIB
US835256329 avr. 20108 janv. 2013Damaka, Inc.System and method for peer-to-peer media routing using a third party instant messaging system for signaling
US838085926 nov. 200819 févr. 2013Damaka, Inc.System and method for endpoint handoff in a hybrid peer-to-peer networking environment
US840622920 mars 201226 mars 2013Damaka, Inc.System and method for traversing a NAT device for peer-to-peer hybrid communications
US84073144 avr. 201126 mars 2013Damaka, Inc.System and method for sharing unsupported document types between communication devices
US843291715 sept. 201130 avr. 2013Damaka, Inc.System and method for concurrent sessions in a peer-to-peer hybrid communications network
US84373073 sept. 20087 mai 2013Damaka, Inc.Device and method for maintaining a communication session during a network transition
US844690018 juin 201021 mai 2013Damaka, Inc.System and method for transferring a call between endpoints in a hybrid peer-to-peer network
US846738720 mars 201218 juin 2013Damaka, Inc.System and method for peer-to-peer hybrid communications
US846801024 sept. 201018 juin 2013Damaka, Inc.System and method for language translation in a hybrid peer-to-peer environment
US847889015 juil. 20112 juil. 2013Damaka, Inc.System and method for reliable virtual bi-directional data stream communications with single socket point-to-multipoint capability
US861154023 juin 201017 déc. 2013Damaka, Inc.System and method for secure messaging in a hybrid peer-to-peer network
US868930719 mars 20101 avr. 2014Damaka, Inc.System and method for providing a virtual peer-to-peer environment
US869458717 mai 20118 avr. 2014Damaka, Inc.System and method for transferring a call bridge between communication devices
US872589515 févr. 201013 mai 2014Damaka, Inc.NAT traversal by concurrently probing multiple candidates
US874378111 oct. 20103 juin 2014Damaka, Inc.System and method for a reverse invitation in a hybrid peer-to-peer environment
US886216429 sept. 200814 oct. 2014Damaka, Inc.System and method for transitioning a communication session between networks that are not commonly controlled
US88675491 avr. 201321 oct. 2014Damaka, Inc.System and method for concurrent sessions in a peer-to-peer hybrid communications network
US887478517 août 201028 oct. 2014Damaka, Inc.System and method for signaling and data tunneling in a peer-to-peer environment
US889264625 août 201018 nov. 2014Damaka, Inc.System and method for shared session appearance in a hybrid peer-to-peer environment
US89481321 avr. 20133 févr. 2015Damaka, Inc.Device and method for maintaining a communication session during a network transition
US90152588 janv. 201321 avr. 2015Damaka, Inc.System and method for peer-to-peer media routing using a third party instant messaging system for signaling
US902703211 sept. 20135 mai 2015Damaka, Inc.System and method for providing additional functionality to existing software in an integrated manner
US90310052 juin 201412 mai 2015Damaka, Inc.System and method for a reverse invitation in a hybrid peer-to-peer environment
US904348829 mars 201026 mai 2015Damaka, Inc.System and method for session sweeping between devices
US91065093 juil. 201211 août 2015Damaka, Inc.System and method for data transfer in a peer-to-peer hybrid communication network
US912892716 mai 20138 sept. 2015Damaka, Inc.System and method for language translation in a hybrid peer-to-peer environment
US914348916 déc. 201322 sept. 2015Damaka, Inc.System and method for secure messaging in a hybrid peer-to-peer network
US91727027 mars 201327 oct. 2015Damaka, Inc.System and method for traversing a NAT device for peer-to-peer hybrid communications
US917270316 mai 201327 oct. 2015Damaka, Inc.System and method for peer-to-peer hybrid communications
US919141616 avr. 201017 nov. 2015Damaka, Inc.System and method for providing enterprise voice call continuity
US92102687 avr. 20148 déc. 2015Damaka, Inc.System and method for transferring a call bridge between communication devices
US926445814 janv. 201316 févr. 2016Damaka, Inc.System and method for endpoint handoff in a hybrid peer-to-peer networking environment
US935697217 nov. 201531 mai 2016Damaka, Inc.System and method for providing enterprise voice call continuity
US93569975 sept. 201431 mai 2016Damaka, Inc.System and method for sharing unsupported document types between communication devices
US935701618 oct. 201331 mai 2016Damaka, Inc.System and method for virtual parallel resource management
US943241223 avr. 201430 août 2016Damaka, Inc.System and method for routing and communicating in a heterogeneous network environment
US949123322 févr. 20168 nov. 2016Damaka, Inc.System and method for providing additional functionality to existing software in an integrated manner
US949712730 avr. 201515 nov. 2016Damaka, Inc.System and method for a reverse invitation in a hybrid peer-to-peer environment
US949718126 sept. 201415 nov. 2016Damaka, Inc.System and method for concurrent sessions in a peer-to-peer hybrid communications network
US957809219 oct. 201621 févr. 2017Damaka, Inc.System and method for providing additional functionality to existing software in an integrated manner
US964805118 sept. 20149 mai 2017Damaka, Inc.System and method for transitioning a communication session between networks that are not commonly controlled
US965456825 nov. 201516 mai 2017Damaka, Inc.System and method for endpoint handoff in a hybrid peer-to-peer networking environment
US971250716 sept. 201518 juil. 2017Damaka, Inc.System and method for secure messaging in a hybrid peer-to-peer network
US974284627 mai 201622 août 2017Damaka, Inc.System and method for sharing unsupported document types between communication devices
US978117327 mai 20163 oct. 2017Damaka, Inc.System and method for providing enterprise voice call continuity
US978125821 avr. 20153 oct. 2017Damaka, Inc.System and method for peer-to-peer media routing using a third party instant messaging system for signaling
US20030050962 *7 oct. 199913 mars 2003Robert Charles MonsenMethod and apparatus for securing information access
US20040146052 *27 janv. 200329 juil. 2004Tanli ChangApparatus and method for address filtering in a multi-host network interface
US20050044216 *7 sept. 200424 févr. 2005Shujin ZhangMultiple-level Internet protocol accounting
US20050044390 *8 sept. 200424 févr. 2005Cisco Technology, Inc., A California CorporationTiming attacks against user logon and network I/O
US20050083931 *6 déc. 200421 avr. 2005Cisco Technology, Inc.Method and apparatus providing dial on demand scaling
US20050198294 *10 mars 20058 sept. 2005Cisco Technology, Inc., A California CorporationSharing of NAS information between PoPs
US20050207414 *25 mai 200522 sept. 2005Cisco Technology, Inc.Apparatus and method for automatic cluster network device address assignment
US20050213560 *25 mai 200529 sept. 2005Cisco Technology, Inc., A California Corporation.Apparatus and method for automatic cluster network device address assignment
US20050286519 *15 mars 200529 déc. 2005Damaka, IncSystem and method for peer-to peer hybrid communications
US20060039365 *17 oct. 200523 févr. 2006Damaka, Inc.System and method for routing and communicating in a heterogeneous network environment
US20060050700 *30 août 20059 mars 2006Damaka, Inc.System and method for traversing a NAT device for peer-to peer hybrid communications
US20060095365 *14 déc. 20054 mai 2006Damaka, Inc.System and method for conducting an auction in a peer-to peer network
US20060120375 *27 janv. 20068 juin 2006Damaka, Inc.System and method for data transfer in a peer-to peer hybrid communication network
US20060203750 *15 mai 200614 sept. 2006Damaka, Inc.System and method for conferencing in a peer-to-peer hybrid communications network
US20060206310 *15 mai 200614 sept. 2006Damaka, Inc.System and method for natural language processing in a peer-to-peer hybrid communications network
US20060218624 *15 mai 200628 sept. 2006Damaka, Inc.System and method for concurrent sessions in a peer-to-peer hybrid communications network
US20060253896 *10 avr. 20069 nov. 2006Cisco Technology, Inc.Proxy on demand
US20070078720 *13 nov. 20065 avr. 2007Damaka, Inc.System and method for advertising in a peer-to-peer hybrid communications network
US20070165597 *29 déc. 200619 juil. 2007Damaka, Inc.System and method for deterministic routing in a peer-to-peer hybrid communications network
US20070165629 *29 déc. 200619 juil. 2007Damaka, Inc.System and method for dynamic stability in a peer-to-peer hybrid communications network
US20080256620 *23 juin 200816 oct. 2008Cisco Technology, Inc.Default Internet Traffic and Transparent Passthrough
US20090086681 *3 sept. 20082 avr. 2009Damaka, Inc.Device and method for maintaining a communication session during a network transition
US20090088150 *29 sept. 20082 avr. 2009Damaka, Inc.System and method for transitioning a communication session between networks that are not commonly controlled
US20090262742 *30 juin 200922 oct. 2009Damaka, Inc.System and method for traversing a nat device for peer-to-peer hybrid communications
US20090281833 *9 mai 200812 nov. 2009Tele Video Md, Inc.System and method for secure multi-party medical conferencing
US20090296606 *10 août 20093 déc. 2009Damaka, Inc.System and method for peer-to-peer hybrid communications
US20090307356 *23 juil. 200910 déc. 2009Cisco Technology, Inc.Ip address allocation in a network environment
US20100312902 *26 nov. 20089 déc. 2010Damaka, Inc.System and method for endpoint handoff in a hybrid peer-to-peer networking environment
US20100318678 *6 août 201016 déc. 2010Damaka, Inc.System and method for routing and communicating in a heterogeneous network environment
US20110202610 *17 août 201018 août 2011Damaka, Inc.System and method for signaling and data tunneling in a peer-to-peer environment
US20110231917 *19 mars 201022 sept. 2011Damaka, Inc.System and method for providing a virtual peer-to-peer environment
US20110238862 *29 mars 201029 sept. 2011Damaka, Inc.System and method for session sweeping between devices
US20110320220 *9 sept. 201129 déc. 2011Televideo Md, Inc.System and method for secure multi-party medical conferencing
USRE418112 oct. 20035 oct. 2010Cisco Technology, Inc.Integration of authentication authorization and accounting service and proxy service
Classifications
Classification aux États-Unis709/225, 709/224, 726/2, 709/223
Classification internationaleG06Q30/02, H04L29/06, H04L12/28
Classification coopérativeH04L63/08, G06Q30/02, H04L12/2874, H04L12/2856
Classification européenneG06Q30/02, H04L63/08, H04L12/28P1, H04L12/28P1D1B
Événements juridiques
DateCodeÉvénementDescription
29 juin 1998ASAssignment
Owner name: CISCO TECHNOLOGY, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BLAIR, DANA;REEL/FRAME:009298/0992
Effective date: 19980601
30 avr. 2004FPAYFee payment
Year of fee payment: 4
20 mars 2008FPAYFee payment
Year of fee payment: 8
11 juin 2012REMIMaintenance fee reminder mailed
31 oct. 2012LAPSLapse for failure to pay maintenance fees
18 déc. 2012FPExpired due to failure to pay maintenance fee
Effective date: 20121031