|Publication number||US7386632 B1|
|Application number||US 11/651,671|
|Publication date||Jun 10, 2008|
|Filing date||Jan 9, 2007|
|Priority date||Jun 7, 2002|
|Publication number||11651671, 651671, US 7386632 B1, US 7386632B1, US-B1-7386632, US7386632 B1, US7386632B1|
|Inventors||Aravind Sitaraman, Joseph F. Mann, Maria Alice Dos Santos, Shuxian Lou, Sampath Kumar Sthothra Bhasham|
|Original Assignee||Cisco Technology, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (51), Non-Patent Citations (14), Referenced by (4), Classifications (20), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application is a divisional of application Ser. No. 10/164,515, entitled “DYNAMIC IP ADDRESSING AND QUALITY OF SERVICE ASSURANCE” by Aravind Sitaraman, Joseph F. Mann, Maria Alice Dos Santos, Shuxian Lou and Sampath Kumar Sthothra Bhasham, filed on Jun. 7, 2002 now U.S. Pat. No. 7,165,117.
1. Field of the Invention
The present invention relates to managing addresses and network bandwidth. More particularly, the present invention relates to managing dynamically allocated addresses and applying in a consistent manner a quality of service scheme which manages network bandwidth associated with the dynamically allocated addresses.
2. The Background
As shown in
Regardless of the access method used, each device (e.g., a host or router) that receives, sends and/or routes information between or among other devices on Internet 10 is configured to communicate with other devices using a communication protocol that may be understood by the other devices. The current communication protocol used by these devices on the Internet is TCP/IP (transmission control protocol/internet protocol). In addition, each device that can send or receive information (e.g., a host device) must also have a unique address. The type of address used for the Internet, or an equivalent switched network that uses TCP/IP, is commonly referred to as an IP address. A standard TCP/IP address is presently 32 bits in length, providing a total of 232 possible IP addresses. Those of ordinary skill in the art will readily recognize that not all of these possible IP addresses are available due to administrative expediencies, such as reserving blocks of IP addresses for future use.
Sending or receiving information using the TCP/IP protocol requires encapsulating information into packets. Each packet includes a header and a payload. The header contains information related to the handling of the payload by a receiving host or routing device, while the payload contains part or all of the user information. The information in the header includes the sender's and the recipient's addresses and is used to route the packet through the Internet until the packet is received by a host having an IP address that matches the packet's destination address. (When referring to the source address and destination address of a packet, the source address and destination address are commonly referred to as “SA” and “DA”, respectively.) This approach enables users to accurately exchange information with one another through their respective host computers.
By implementing a protocol common to all devices using Internet 10, users may send and receive information with other users on the Internet in a seamless manner regardless of geographic location or the type of host and/or interconnected network used. This ability for users to access or provide information to others regardless of geographic boundaries is one factor fueling the rapid increase in the number of users using Internet 10. This increase has depleted the number of addresses and has increased the amount of packet traffic on Internet 10.
One solution for mitigating the effect of the number of users requiring addresses is to dynamically allocate addresses for users who do not have dedicated connections to Internet 10, such as users who use dial-up access methods to connect to an ISP. Dynamic allocation of IP addresses entails having a pool of IP addresses, such as FP address pool 32, from which an ISP, such as ISP 34 can draw each time a valid subscriber (who does not use a dedicated connection or a connection that does not have a framed IP address, i.e., a static IP address) seeks to access the Internet. Once the subscriber logs on to an ISP and is properly authenticated, the ISP allocates an IP address for use by the user. Upon log-off, the assigned/allocated IP address is then released, rendering that IP address available for subsequent use by another user. In this way, a set of IP addresses can be used to provide access to a number of users that exceed the number of IP address comprising the IP address pool, assuming that at any given time the number of users seeking to log-on and obtain dynamic IP addresses is less than or equal to the number of IP addresses available in the IP address pool.
Attempting to mitigate the effect of high levels of packet traffic on the Internet has resulted in different solutions. One solution, albeit an expensive one, is to increase bandwidth throughout the Internet such as by providing an Internet backbone that has a higher bandwidth, i.e., providing a larger pipe. Another solution is to manage bandwidth used by Internet users according to some defined set of criteria so as to decrease the latency period experienced by a packet while being routed from an access point to an Internet backbone. This approach is commonly known as QoS (Quality of Service). QoS may be thought of as a solution that does not create a bigger pipe through which packets may flow but a solution that picks which packets will go first, i.e., some packets have precedence over others.
Packet precedence may be based or the address used by a user's host machine. For example, a user may have service level agreement with an ISP that requires ISP 34 to give precedence to packets associated with the user. Packets given precedence are selected according to the source address held by each packet. To ensure that precedence is provided consistently, the user is given a static or permanent IP address that when encapsulated in a packet and received by a router, such as router 36, is given precedence over another user that does not have the same service level agreement. This decreases transmission delay experienced by packets originating from the user's host machine when being routed from access point 14 onto the Internet backbone 12.
However, basing QoS or precedence on a static IP address precludes ISPs from using dynamically assigned IP addresses because the same user may have different addresses each time the user logs on. Moreover, if the same user decides to obtain Internet access at an area serviced by a access point (sometimes referred to as a PoP or “Point of Presence”), provided by the same or different ISP, the ISP will not know the user's static IP address. Static IP addresses are not shared between access points, such as access points 14 and 16, that are connected to Internet backbone 12. This precludes the ISP from providing the same QoS to its user simply because the user is a roaming user (i.e. a user that uses an access point that is other than the user's home PoP location) even though the PoP or access point is serviced by the same ISP that services the user's home PoP.
Accordingly there is a need for managing the dynamic allocation of an address to a host device which is selected to obtain network access from any access point within a given communications network. Further, there is a need for maintaining a network bandwidth management scheme that is consistently applied to a user's network bandwidth usage regardless of the access point used by the user.
In a first aspect of the present invention, an address is allocated to a host device which is selected to obtain network access from any access point within a given communications system, while maintaining a network bandwidth management scheme that is consistently applied to a user's network bandwidth usage regardless of the access point used by the user. This is accomplished using a communications network having at least one access point associated with a forwarding device, such as a router, which is configured to forward packets at a forwarding rate based on a source address contained in each of the packets. A user profile is assigned to each subscriber belonging to an access point. Each user profile includes a pool identifier which corresponds to a forwarding rate to be used by the forwarding device for packets transmitted by the subscriber. If a subscriber attempts to log-on to an access point, a source address is selected from an address pool using the address pool identifier, the source address is assigned to the subscriber, and each packet is forwarded at a forwarding rate based on the source address contained within each of the packets.
In a second aspect of the present invention, the communications system includes a global memory which contains all of the user profiles stored for the communications system. The global memory provides the pertinent user profile to any access point from which a subscriber seeks to obtain access when the subscriber does not have a user profile contained within the local memory of the access point, such as in the case of a roaming subscriber.
In the following description, a preferred embodiment of the invention is described with regard to preferred process steps and data structures. However, those skilled in the art will recognize, after perusal of this application, that embodiments of the invention may be implemented using at least one general purpose computer operating under program control, and that modification of the general purpose computer to implement the components, process steps, and/or data structures described herein would not require undue invention.
In accordance with a presently preferred embodiment of the present invention, the components, process steps, and/or data structures are implemented using C++ programs running on an Enterprise 2000 server™ running SunSolaris™ as its operating system. The Enterprise 2000 server™ and SunSolaris™ operating system are available from Sun MicroSystems, Inc. of Mountain View, Calif. This implementation is not intended to be limiting in any way. Different implementations may be used and may include other types of operating systems, computing platforms, and/or computer programs. In addition, those of ordinary skill in the art will readily recognize that devices of a less general purpose nature, such as hardwired devices, devices relying on FPGA (field programmable gate array) or ASIC (application specific integrated circuit) technology, or the like, may also be used without departing from the scope and spirit of the inventive concepts disclosed herewith.
Communications system 60 includes at least one access point 62 having at least one client 64 and a protocol gateway 66 having a local memory 68 Client 64 and protocol gateway 66 are shown coupled to a switched backbone 70 via a router 72. Communications system 60 also includes a network operations center 74 having a global memory 76, at least one security server 78, and a configuration server 80 having a pool of addresses 81 for dynamic allocation.
Local memory 68 and global memory 76 are intended to store the subscriber information (user profiles) and are implemented as memory caches although such an implementation is not intended to be limiting. Other types of memory may be used which preferably offer low memory latency. Protocol gateway 66 functions as an interface that allows access requests received from client 64 to be serviced using components that may communicate using different protocols, such as security server 78 and configuration server 80.
Switched backbone 70 is any high bandwidth medium that allows data to be passed from one access point to another access point. In accordance with a presently preferred embodiment of the present invention, switched backbone 70 is implemented by using an Internet backbone. The use of an Internet backbone is not intended to be limiting in any way. Other types (or any number) of backbones, WANs (wide area networks), or equivalent networks, may be used as long as it supports the communication protocols used by devices which connect to the backbone, such as TCP/IP based protocols or equivalent.
Access point 62 represents a location within communications system 60 to which stations or hosts may connect to obtain communication services provided by communications system 60. Access point 62 is associated with at least one client which is capable of communicating with a host employed by a user to establish a session with communications system 60. In accordance with a presently preferred embodiment of the present invention, at least one of the clients is capable of providing dial-up services, such as PPP (point to point protocol), SLIP (serial line internet protocols), rlogin, telnet, ftp (file transfer protocol), and the like. Additional clients may also be implemented for providing other types of services, such as an ADSL 84 (Asynchronous Digital Subscriber Line) client and/or its digital subscriber line equivalents, e.g., RADSL, VDSL, HDSL, and SDSL; Voice Over IP; or any other equivalent client. It is presently contemplated that each of the clients will communicate with protocol gateway 66 using the RADIUS (Remote Authentication Dial In user Service) protocol. However, other types of protocols may also be used as well, such as TACAS+ or Diameter. RADIUS, TACAS+, and Diameter are protocols known by those of ordinary skill in the art and thus, will not be further discussed other than in the context of the present invention in order to avoid over-complicating the disclosure.
In accordance with a presently preferred embodiment of the present invention, the client used for supporting dial-up services is a network access server 82 (NAS). As known by those of ordinary skill in the art, a network access server is capable of supporting TCP/IP-based dial-up services. The use of a network access server is not intended to be limiting in any way. Other types of clients may be used. Moreover, the use of TCP/IP-based dial-up services is also not intended to be limiting in any way. Any other type of dial-up service using a different protocol may be implemented as long as the protocol is compatible with the pertinent devices used in communications system 60.
Those of ordinary skill in the art will recognize that dial-up access to network access server 82 by a user 90 through host 88 may be accomplished by using a modem (not shown) coupled to a POTS (plain old telephone system) network 92. Providing and establishing a TCP/IP-based dial-up connection is well known by those of ordinary skill in the art. Using host 88 having a modem connected to network access server 82 is not intended to limit the present invention in any way. Other equivalent devices may be implemented. For example, host 88 may alternatively be provided using a server providing modem services to devices on a LAN (not shown), or any equivalent device that permits a user to obtain a dial-up session with network access server 82.
Access point 62 enables a network services provider, such as an ISP (Internet Services Provider), to provide a point of presence (PoP) to users within a given geographical area. Communication system 60 is shown having PoP 94, 96, and 98 where PoP 94 is provided by access point 62 and PoP 96 and 98 are provided by access points 100 and 102, respectively. Access points 100 and 102 are similar to access point 62 because they are also associated with at least one client. The number of PoPs shown is not intended to limit the present invention in any way and any number of PoPs may be included in communications system 60.
Since, in The preferred embodiment, switched backbone 70 is implemented as an Internet backbone, a Domain Name Server (DNS) is used to return Internet domain names that correspond to an address received from an access point. For example, if DNS 110 receives an IP address from access point 62 through protocol gateway 66, it returns the domain name corresponding to that IP address. Alternatively, if DNS 110 receives a domain name from protocol gateway 66, it returns the IP address that corresponds to that domain name.
Those of ordinary skill in the art will recognize that there are many domain name servers used on the Internet. The domain name servers support a group of access points that provide PoPs within adjacent geographical areas. For example, domain name server 110 in
Routers, such as router 72, used by the access points in communications system 60 forward packets at a rate based on a specified criteria, such as forwarding the packets according to an order of precedence based on the specified criteria. In accordance with a presently preferred embodiment of the present invention, the specified criteria is based on the source address contained in a packet. Router 72 operates under a committed access rate (CAR) which requires it to forward packets having a certain source address at a selected rate. This may require router 72 to provide precedence to at least one packet over another packet in order to maintain the committed access rate for the packet given precedence. This ensures that packets that have payloads which are sensitive to transmission latency, such as video data, voice data, or equivalent data, such as data that require “real time” presentation to a recipient, are routed first. Packets carrying text data are not greatly affected by routing latency as compared to video data and voice data, and thus, may be safely routed after packets carrying such time-sensitive data.
In accordance with a presently preferred embodiment of the present invention, each router configured to provide a committed access rate includes a CAR look-up table (or equivalent memory) which holds a list of addresses which are categorized according to committed access rates. When a packet is received by router 72 from a client 64, such as network access server 82, the source address of the packet is compared with the addresses listed in CAR look-up table 115. If a match is found, the committed access rate for that address is then provided. If prior packets are queued ahead of the packet and the committed access rate for the packet cannot be met without the packet taking precedence over the prior packets in the queue, then the packet is given precedence for forwarding over packets having lower precedence. As shown in
Using precedential routing to provide a committed access rate for a router in communications system 60 is not intended to be limiting in any way. Other types of bandwidth management or Quality of Service (QoS) may be implemented alone or in conjunction with precedential routing, such as through the use of the resource reservation protocol, weighted fair queuing, and others.
Also, using a router or a CAR look-up table is not intended to be in any way limiting. Other types of devices may be used to forward packets at a rate based on the a specified criteria, such as the source address contained by the packets to be forwarded.
Configuration server 80 is shown having a plurality of address pools 81. Configuration server 80 allocates (or de-allocates) addresses from plurality of address pools 81 to subscribers through clients such as network access server 82. Plurality of address pools 81 has at least two address pools or groups, such as group A (200), group B (202), and group C (204). The number of groups used is not intended to be in any way limiting and is disclosed as a preferred embodiment only. In accordance with a presently preferred embodiment of the present invention, configuration server 80 is a Dynamic Host Configuration Protocol (DHCP) server, which is known to those of ordinary skill in the art. The type of addresses maintained by a DHCP server are IP addresses.
Local memory 68 stores a set of user profiles 206. A user profile includes one home PoP identifier 206 a, a pool identifier 206 b, and a user name 206 c for each subscriber belonging to a PoP serviced by an access point. For example, user profile 208 would be created for subscriber 90 since subscriber 90 belongs to PoP 94. The user profile of a subscriber 210 that belongs to another PoP, such as PoP 96, is not stored within local memory 68 but is stored in local memory 212 associated with protocol gateway 214, as shown in
A home PoP identifier assigned to a user corresponds to the ISP to which the user is subscribed. For example, subscriber/user 90 would have a home PoP identifier corresponding to the ISP servicing PoP 94. The pool identifier reflects the type of network service contracted for by the subscriber with the subscriber's ISP and is used to determine what type of address to allocate to the subscriber when the subscriber logs on. For example, if subscriber 90 requires a connection that is well-suited for video data (or any data that needs to be presented in approximately real-time), the subscriber will be given a pool identifier that will be used to select an address, which upon use by subscriber 90 will be given a committed access rate by router 72 that reflects the service contracted for by subscriber 90 with the subscriber's ISP.
During selected intervals, such as when a local memory is updated with new user profiles, the user profiles held by the local memory are sent and stored within global memory 76. Global memory 76 contains all of the user profiles from each local memory in communications systems 60. For example, referring again to
For example, if a subscriber seeks a connection through PoP 98, such as through a point to point (PPP) dial-up session with a network access server 216, network access server 216 will send an access request to protocol gateway 218. Protocol gateway 218, in turn, will send an access request to a security server 220. In accordance with a presently preferred embodiment of the present invention, a security server 78 is an authentication, authorization, and accounting (AAA) server. An authentication, authorization and accounting server is responsible for receiving user access requests, authenticating the user and then returning all configuration information necessary for a network access server (or equivalent client) to deliver service to the user. Such servers also keep track of network utilization for use in accounting functions as well known to those of ordinary skill in the art.
In accordance with a presently preferred embodiment of the present invention, the security servers described herein are implemented using a RADIUS protocol based server. However, other types of authentication, authorization, and accounting protocols may also be used as well, such as TACAS+ or Diameter discussed above.
Upon receipt of the access request, security server 220 will attempt to access a user profile from local memory 222. Since the subscriber 90 is not subscribed to PoP 98, the user profile corresponding to subscriber 90 will not be available locally, and hence, the attempt to obtain the user profile will fail. This will result in local memory 222 requesting the user profile from the network operating center 74. The network operation center 74 searches global memory 76 for the user profile corresponding to subscriber 90 and when it is found, returns it to local memory 222 which provides it to security server 220. In accordance with a presently preferred embodiment of the present invention, local memory 222 and global memory 76 communicate via a RADIUS protocol. This application layer protocol is used in conjunction with the UDP (user datagram protocol) and IP protocols to support network communication between local memory 222 and global memory 76.
UDP is a transport level, unreliable, connectionless protocol. The term “unreliable” is commonly used to describe a protocol which does not correct for dropped, duplicate, and/or out of order packets—thus, applications using UDP will need to provide their own mechanisms for ensuring proper packet delivery and reception; if desired. The lack of error correction is not a major disadvantage, however, because there are very few transmission errors on modern networks and designers have leeway in the amount of transmission error control they want to implement in their applications. This renders UDP an efficient solution for applications that require very simple exchanges, such as exchanges that include one reply following every query. To impose error correction in such a connection would not be efficient because the connection would have to be torn down immediately after a single packet exchange. The term “connectionless” is commonly used to describe a protocol which does not rely on a predefined circuit for transmission. UDP is known to those of ordinary skill in the art and therefore will not be further described herein to avoid overcomplicating the disclosure.
Upon proper authentication and authorization, an address request is generated to configuration server 224 to provide an address that corresponds to the pool identifier found with the user profile obtained from global memory 76. This address will eventually be provided to host 216. Upon receipt of packets from host 216, router 226 will forward the packets at a committed access rate listed for the packets within a committed access rate table 228. In accordance with a presently preferred embodiment of the present invention, the address request is based on the UDP protocol. The use of the UDP protocol is not intended in any way to the limit the present invention. Any other protocol may be used as long as the functions of requesting, allocating, and de-allocating addresses can be sought from and provided by configuration server 80.
The components listed in
At reference number 300, a subscriber, such as subscriber 90, attempts through host machine 88 to establish a connection with network access server 82. This results in network access server 82 receiving an access request from host machine 88 which includes the subscriber's user name or other identification information.
At reference number 302, network access server 82 responds by generating an access request and directs it to protocol gateway 66. The type of access request sent to protocol gateway 66 conforms to the protocol used to communicate between network access server 82 and protocol gateway 66. In the preferred embodiment of the present invention, RADIUS is the protocol used and hence, a RADIUS access request is the type of request generated by network access server 82.
At reference number 304, protocol gateway directs the access request generated by network access server 82 to security server 78.
At reference number 306, security server 78 forwards the access request to local memory 68.
At reference number 308, local memory 68 determines whether a user profile having the subscriber's user name exists. If not, the process flow proceeds to reference number 310.
At reference number 310, local memory 68, through protocol gateway 66, sends a packet containing a query to global memory 76 to determine whether global memory 76 contains a user profile corresponding to subscriber 90. In accordance with a presently preferred embodiment of the present invention, the packet is based on a RADIUS protocol. This protocol is used in conjunction with the UDP and IP protocols to support network communication between local memory 68 and global memory 76. However, those of ordinary skill in the art will recognize that other types of communication protocols may be used which will enable a local memory to perform a query function that is equivalent to the act(s) performed in reference number 310 without departing from the inventive concepts disclosed herein.
At reference number 312, upon receipt, global memory 76 determines whether it contains a user profile corresponding to subscriber 90. If so, the process flow proceeds to reference number 314.
At reference number 314, global memory 76 returns the subscriber's user profile as a packet to protocol gateway 66 which directs the packet to security server 78.
At reference number 316, security server 78 determines whether to accept or reject the access request based upon the information contained within the user profile provided by the packet and various other criteria such as the time of day the session is being requested, the number of open sessions, and the like. If authorization server 78 accepts the access request, the process flow proceeds to reference number 318.
At reference number 318, security server 78 returns an access-accept packet, which includes the user profile returned by global memory 76 at reference number 314, to protocol gateway 66. In accordance with a presently preferred embodiment of the present invention, the access-accept packet is based on the RADIUS protocol and includes an extended vender specific attribute for holding the pool identifier contained in the user profile.
At reference number 320, protocol gateway 66 receives the packet and uses the access-accept packet to ascertain whether a static or dynamic address, such as an EP address, should be allocated to subscriber 90. If a dynamic address is required, protocol gateway 66 proceeds to reference number 322. In accordance with a presently preferred embodiment of the present invention, the determination as to whether a static or dynamic address should be allocated is based on whether the access-accept packet includes a Framed-IP-Address attribute. If a Framed-IP Address attribute is not included, protocol gateway 66 assumes that a dynamic address is required.
At reference number 322, protocol gateway 66 attempts to procure an address for subscriber 90 by obtaining from the access-accept packet a pool identifier and using the pool identifier to make a request to configuration server 80 for an address that corresponds to the pool identifier.
At reference number 324, configuration server 80 returns an address that corresponds to the pool identifier by allocating an available address that belongs within an address pool corresponding to the pool identifier.
At reference number 326, protocol gateway 66 receives the allocated address and inserts the address and home PoP identifier into a control packet In accordance with a presently preferred embodiment of the present invention, the control packet is based on the RADIUS protocol although other types of protocols may be used as long as the protocol chosen is supported by the receiving device, such as network access server 82.
At reference number 328, protocol gateway 66 sends the packet containing the address and the PoP identifier to network access server 82, which in turn, forwards the packet to host 88.
At reference number 330, host 88 receives the address and uses it as a source address for each packet transmitted to network access server 82, or equivalent client, for forwarding to a backbone router, such as router 72.
At reference number 332, network access server 82 receives the packets transmitted by host 88 and forwards them to router 72.
At reference number 334, upon receipt, router 72 determines the source address contained within each packet and forwards the packets at a forwarding rate corresponding to the source address. In accordance to a presently prey erred embodiment of the present invention, the forwarding rate is determined by using the source address as an index to a look up table which contains a forwarding rate defined for the source address. The forwarding rate is then used as the minimum rate in which the packets are to be forwarded.
If, at reference number 308, a user profile was found in local memory 68, the process flow proceeds to reference number 336. At reference number 336, the user file is sent to security server 78 and the process flow proceeds to reference number 316.
If, at reference number 316, security server 78 determines (using the returned user profile) that authorization should not be given to subscriber 90, the process flow proceeds to reference number 338.
At reference number 338, security server generates an access reject packet and sends it to protocol gateway 66 which sends it to network security server 82 which in turn, forwards it to host 88.
If, at reference number 312, global memory 76 determines that it does not contain a user profile corresponding to subscriber 90, the process flow proceeds to reference number 342. At reference number 342, global memory 76 notifies security server 78 that authorization is denied by sending a reject packet. The process flow then proceeds to reference number 316.
If, at reference number 320, protocol gateway 66 determines that the access-accept packet includes a user profile indicating that subscriber 90 is to receive a static address, it obtains the static address and provides it for encapsulation at reference number 326. In accordance with a presently preferred embodiment of the present invention, the determination as to whether a static (or dynamic) address should be allocated is based on whether the access-accept packet includes a Framed-IP-Address attribute. If a Framed-IP Address attribute is present, protocol gateway 66 treats the Framed-IP Address attribute as the static address.
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.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4769810||Dec 31, 1986||Sep 6, 1988||American Telephone And Telegraph Company, At&T Bell Laboratories||Packet switching system arranged for congestion control through bandwidth management|
|US4769811||Dec 31, 1986||Sep 6, 1988||American Telephone And Telegraph Company, At&T Bell Laboratories||Packet switching system arranged for congestion control|
|US4933937||Nov 23, 1987||Jun 12, 1990||Kabushiki Kaisha Toshiba||Network adapter for connecting local area network to backbone network|
|US5014265||Nov 30, 1989||May 7, 1991||At&T Bell Laboratories||Method and apparatus for congestion control in a data network|
|US5224099||May 17, 1991||Jun 29, 1993||Stratacom, Inc.||Circuitry and method for fair queuing and servicing cell traffic using hopcounts and traffic classes|
|US5303237||Jul 31, 1992||Apr 12, 1994||International Business Machines Corporation||Frame relay system capable of handling both voice and data frames|
|US5367517||Dec 16, 1992||Nov 22, 1994||International Business Machines Corporation||Method and system of requesting resources in a packet-switched network with minimal latency|
|US5408472||Sep 20, 1993||Apr 18, 1995||Motorola, Inc.||Device and method for cell processing in cell relay nodes|
|US5423002||Feb 28, 1994||Jun 6, 1995||3Com Corporation||System for extending network resources to remote networks|
|US5430715||Sep 15, 1993||Jul 4, 1995||Stratacom, Inc.||Flexible destination address mapping mechanism in a cell switching communication controller|
|US5502725||Apr 14, 1994||Mar 26, 1996||Nokia Telecommunications Oy||Method and system for sending shorter service number in place of all but first packet, in place of longer destination address, for increasing user data content of packet data transfer|
|US5509006||Apr 18, 1994||Apr 16, 1996||Cisco Systems Incorporated||Apparatus and method for switching packets using tree memory|
|US5570360||Mar 20, 1995||Oct 29, 1996||Stratacom, Inc.||Method and apparatus for implementing communication service contract using cell arrival information|
|US5570361||Jul 6, 1994||Oct 29, 1996||Fujitsu Limited||Apparatus and a method for supervising and controlling ATM traffic|
|US5592470||Dec 21, 1994||Jan 7, 1997||At&T||Broadband wireless system and network architecture providing broadband/narrowband service with optimal static and dynamic bandwidth/channel allocation|
|US5596744||May 20, 1993||Jan 21, 1997||Hughes Aircraft Company||Apparatus and method for providing users with transparent integrated access to heterogeneous database management systems|
|US5610910||Aug 17, 1995||Mar 11, 1997||Northern Telecom Limited||Access to telecommunications networks in multi-service environment|
|US5668857||Mar 29, 1996||Sep 16, 1997||Netspeed, Inc.||Communication server apparatus and method|
|US5671354||Feb 23, 1996||Sep 23, 1997||Hitachi, Ltd.||Method of assisting server access by use of user authentication information held in one of servers and a method of assisting management user account for use of servers|
|US5678006||Feb 1, 1996||Oct 14, 1997||Cisco Systems, Inc.||Network switch having network management agent functions distributed among multiple trunk and service modules|
|US5699521||Mar 22, 1995||Dec 16, 1997||Hitachi, Ltd.||Communication system and communication method|
|US5734654||Aug 2, 1994||Mar 31, 1998||Fujitsu Limited||Frame relay switching apparatus and router|
|US5771381||May 28, 1997||Jun 23, 1998||Microsoft Corporation||Method and system for adding configuration files for a user|
|US5778182||Nov 7, 1995||Jul 7, 1998||At&T Corp.||Usage management system|
|US5805595||Oct 23, 1996||Sep 8, 1998||Cisco Systems, Inc.||System and method for communicating packetized data over a channel bank|
|US5835725||Oct 21, 1996||Nov 10, 1998||Cisco Technology, Inc.||Dynamic address assignment and resolution technique|
|US5835727||Dec 9, 1996||Nov 10, 1998||Sun Microsystems, Inc.||Method and apparatus for controlling access to services within a computer network|
|US5838683||Mar 13, 1995||Nov 17, 1998||Selsius Systems Inc.||Distributed interactive multimedia system architecture|
|US5852607||Feb 26, 1997||Dec 22, 1998||Cisco Technology, Inc.||Addressing mechanism for multiple look-up tables|
|US5854901||Jul 23, 1996||Dec 29, 1998||Cisco Systems, Inc.||Method and apparatus for serverless internet protocol address discovery using source address of broadcast or unicast packet|
|US5922051||May 14, 1997||Jul 13, 1999||Ncr Corporation||System and method for traffic management in a network management system|
|US5926458||Jan 31, 1997||Jul 20, 1999||Bay Networks||Method and apparatus for servicing multiple queues|
|US5959990||Mar 12, 1996||Sep 28, 1999||Bay Networks, Inc.||VLAN frame format|
|US5970477||Jul 15, 1996||Oct 19, 1999||Bellsouth Intellectual Property Management Corporation||Method and system for allocating costs in a distributed computing network|
|US5991828||Oct 7, 1997||Nov 23, 1999||Fujitsu Limited||System for automatically connecting portable device to network using network environment information including domain name of naming device and community name of network management protocol|
|US6009103||Dec 23, 1997||Dec 28, 1999||Mediaone Group, Inc.||Method and system for automatic allocation of resources in a network|
|US6023724||Sep 26, 1997||Feb 8, 2000||3Com Corporation||Apparatus and methods for use therein for an ISDN LAN modem that displays fault information to local hosts through interception of host DNS request messages|
|US6026441||Dec 16, 1997||Feb 15, 2000||At&T Corporation||Method for establishing communication on the internet with a client having a dynamically assigned IP address|
|US6035281||Jun 16, 1997||Mar 7, 2000||International Business Machines Corporation||System and method of multiparty billing for Web access|
|US6052725||Jul 2, 1998||Apr 18, 2000||Lucent Technologies, Inc.||Non-local dynamic internet protocol addressing system and method|
|US6081840||Oct 14, 1997||Jun 27, 2000||Zhao; Yan||Two-level content distribution system|
|US6091951||Sep 3, 1997||Jul 18, 2000||Telxon Corporation||Seamless roaming among multiple networks|
|US6119160||Oct 13, 1998||Sep 12, 2000||Cisco Technology, Inc.||Multiple-level internet protocol accounting|
|US6119171||Jan 29, 1998||Sep 12, 2000||Ip Dynamics, Inc.||Domain name routing|
|US6151629||Mar 2, 1998||Nov 21, 2000||Compaq Computer Corporation||Triggered remote dial-up for internet access|
|US6175869||Apr 8, 1998||Jan 16, 2001||Lucent Technologies Inc.||Client-side techniques for web server allocation|
|US6253327||Dec 2, 1998||Jun 26, 2001||Cisco Technology, Inc.||Single step network logon based on point to point protocol|
|US6324584||Nov 26, 1997||Nov 27, 2001||International Business Machines Corp.||Method for intelligent internet router and system|
|US6976066||Nov 13, 2000||Dec 13, 2005||Microsoft Corporation||Network and method for implementing network platform services for a computing device|
|US6999458||Feb 14, 2003||Feb 14, 2006||Theglobe.Com||Internet telephony network and methods for using the same|
|WO1999053408A1||Apr 14, 1999||Oct 21, 1999||Juno Online Services, Inc.||Method and apparatus to control a client in a communications network|
|1||"NAT-PC Webopaedia Definition and Links", 1998 Mecklermedia Corporation, printed from http://webopedia.internet.com/TERM/N/NAT.html, on Sep. 19, 1998, 1 page.|
|2||"Network Address Translation Information", printed from http://www.uq.edu.au/+gadmacka/content/natinformation.htm, on Sep. 19, 1998.|
|3||"Three Ways to Manage IP Addresses", PC Magazine:IP Address Management, printed from http://www.zdnet.com/pcmag/features/ipmanage/ip-s2.htm, on Sep. 10, 1998.|
|4||Active Software, Inc., "Active Software's Integration System", printed from http://www.activesw.com/products/products.html, on Jul. 24, 1998.|
|5||Ascend Communications, Inc., "Access Control Product Information", 4 pages.|
|6||Ascend Communications, Inc., "Remote Access Network Security", printed from http://www/ascend.com/1103.html, on Jul. 24, 1998, pp. 1-8.|
|7||Carrel, D. et al., The TACACS+Protocol, Version 1.78, Cisco Systems, Inc., printed from ftp://ftp-eng.cisco.com/gdweber/tac-rfc.1.78.txt on Oct. 23, 2000.|
|8||Droms, R., Dynamic Host Configuration Protocol, Network Working Group, RFC 1531, Oct. 1993.|
|9||NAT and Networks, printed from http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/node4.html, on Sep. 19, 1998.|
|10||Network Registrar, "Hot Products & Solutions", American Internet Corporation, printed from http://www.american.com/networkregistrar.html, on Jul. 24, 1998.|
|11||Network Registrar, "Hot Products & Solutions-Deploying Class of Service Using Network Registrar", American Internet Corporation, Bedford, MA, printed form http://american.com/applicationsCOS-network.html, on Jul. 24, 1998.|
|12||Network Registrar, "Hot Products & Solutions-IP Address Management: A White Paper", American Internet Corporation, Bedford, MA, printed from http://www.american.com/ip-mgmt.html, on Jul. 24, 1998.|
|13||Network Registrar, "Regain Confidence and Control Over Your IP Address Infrastructure", American Internet Corporation, Bedford, MA.|
|14||Rigney, et al., "Remote Authentication Dial In User Service (RADIUS)", Network Working Group, RFC 2138, Apr. 1997, pp. 1-57.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US9104482 *||Dec 11, 2009||Aug 11, 2015||Hewlett-Packard Development Company, L.P.||Differentiated storage QoS|
|US20110145449 *||Dec 11, 2009||Jun 16, 2011||Merchant Arif A||Differentiated Storage QoS|
|CN102546631A *||Jan 6, 2012||Jul 4, 2012||福建星网锐捷网络有限公司||Communication method and device for wireless virtual access point and access point equipment|
|CN102546631B *||Jan 6, 2012||Aug 19, 2015||福建星网锐捷网络有限公司||一种无线虚拟接入点的通信方法、装置及接入点设备|
|U.S. Classification||709/242, 709/250, 709/245|
|Cooperative Classification||H04L47/2425, H04L29/12933, H04L61/2061, H04L29/12283, H04L47/2416, H04L61/6068, H04L61/2015, H04L47/10|
|European Classification||H04L47/10, H04L61/60F, H04L61/20A1, H04L47/24B, H04L61/20E, H04L47/24C, H04L29/12A3E, H04L29/12A9F|
|Jan 9, 2007||AS||Assignment|
Owner name: CISCO TECHNOLOGY, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SITARAMAN, ARAVIND;MANN, JOSEPH F.;SANTOS, MARIA ALICE DOS;AND OTHERS;REEL/FRAME:018781/0951
Effective date: 19990112
|Dec 12, 2011||FPAY||Fee payment|
Year of fee payment: 4
|Dec 10, 2015||FPAY||Fee payment|
Year of fee payment: 8