The present application is a national phase application of PCT/EP2008/063270, filed pursuant to 35 U.S.C. §371, which claims priority to EP 07118409.7, filed Oct. 12, 2007. Both applications are incorporated herein by reference in their entirety.
This invention relates to the configuration of network elements such as routers to effectively handle requests for IP addresses using Dynamic Host Configuration Protocal (DHCP).
For the function of the control and provisioning system 20, the network can be considered in an abstract way as comprising a core 22 having one or more cells 24, each cell having one or more network elements 26 as is shown in
Internet Protocol (IP) is the common form of communication used in most networks. Data communication using IP relies on addressing for the various parts of the network to be able to communicate with each other. An IP address (Internet Protocol address) is a unique address that certain electronic devices use in order to identify and communicate with each other on a computer network utilizing the Internet Protocol standard (IP). Any participating network device—including routers, computers, time-servers, printers, Internet fax machines, and some telephones—can have their own unique address.
IP addresses can be static or dynamic. A static IP address is one in which a device uses the same address every time a user logs on to a network. With a static IP address, a computer's identity can be easily identified by others, and users can easily connect with it. Such an approach is commonly used for websites, email servers and the like.
A dynamic IP address is one in which the address is assigned to a device, usually by a remote server which is acting as a Dynamic Host Configuration Protocol (DHCP) server. IP addresses assigned using DHCP may change depending on the addresses available in the defined pool assigned to that server. Dynamic IP addresses are used because they provide efficient use of a limited pool of available addresses. When there is no need to assign a specific IP Address to each device, users can simply log in and out and use the network without having to have previously obtained an assigned IP address.
The Dynamic Host Configuration Protocol (DHCP) is a set of rules used by communications devices to allow the device to request and obtain an IP address (and other parameters such as the default gateway, subnet mask, and IP addresses of DNS servers) from a server which has a list of addresses available for assignment. The DHCP server ensures that all IP addresses are unique, e.g., no IP address is assigned to a second client while the first client's assignment is valid (i.e. its ‘lease’ has not expired). Thus IP address pool management is done by the server and not by a human network administrator.
The procedure by which an IP address is obtained from a DHCP server is shown schematically in
On connection to the router R, the client C requests an IP address by sending a DHCP discover message (i) to the router R. On receipt of the DHCP discover, the router R relays it on to the network, including the DHCP server extDHCP (ii). The DHCP server responds to this message by issuing a DHCP offer (indicating that an IP address is available to meet the request) which is communicated to the router R (iii) and is in turn, relayed to the client C (iv). On receipt of the DHCP offer, the client issues a DHCP request to the router R (v) which in turn is relayed to the network (and DHCP server) (vi). The DHCP server assigns a particular IP address and issues an acknowledgement, including the assigned IP address (vii) which in turn is relayed by the router R to the client (viii). Steps v to viii are repeated periodically to maintain the lease to that IP address while the client is connected. In the event that the client disconnects (or is timed out), the IP address is released and steps i to viii must be repeated again to obtain a new IP address.
The static configuration of the router makes it difficult for the network to adapt to the changing needs of the clients.
According to a first aspect of the invention there is provided a method of configuring a router to provide DHCP IP address services to a number of network clients sending messages to the router to request IP addresses, wherein the network clients connect to a network via the router which is under the control of a control system, the method comprising the steps of:
i) obtaining configuration instructions for the router by sending messages from the router to the control system to request configurations for DHCP services;
ii) sending configuration instructions from the control system to the router; and
iii) configuring the router in accordance with the configuration instructions to:
By operating the router under the control of the control system, it is possible to have dynamic configuration of the router such that the manner in which a router handles a DHCP request can vary according to the nature of the request.
In one embodiment, the method preferably further comprises analysing the request from the client to determine a service type to which the request relates and creating a configuration instruction according to the determined service type. In this case, the step of obtaining a configuration instruction can comprise creating the configuration instruction in the router from one of a number of configuration templates according to the service type.
In a further embodiment, the method comprises analysing the request from the client to determine a service type to which the request relates; sending a message from the router to the control system to request a configuration for DHCP services according to the determined service type; and sending a configuration instruction from the control system to the router.
The configuration instruction can comprise an instruction including an IP address pool from which the router can assign an address to the client when acting as a DHCP server or an instruction including the identity of the external DHCP server to which the IP address request is relayed.
Where the router act as a relay agent the method can comprise sending relay agent information with the request to the external DHCP server. In such a case, more than one external DHCP server may be identified.
When the router is configured to act as a relay agent, the router may send an update message to the control system when forwarding the IP address from the external DHCP server to the client.
According to a second aspect of the invention there is provided a network system comprisings a number of routers, a number of network clients, and a network control system, wherein each network client connects to a network via an associated router and the router is under the control of the control system, the control system being configured so as to perform the steps of the method in accordance to the first aspect of the invention.
The system may further comprise at least one external DHCP server.
Other changes may be made within the scope of the invention.
Referring now to
In the embodiment of
In the case of
The router R relays the DHCP discover to the designated server and includes “option 82” (relay agent) information if not already present, step 3a. The DHCP server responds with a DHCP offer, step 3b. This is relayed to the client C, step 4. The client C then responds with a DHCP request, step 5 as before. This is relayed by the router R to the DHCP server 5a. The server responds with a DHCP acknowledgement, step 5b which is relayed to the client C by the router R, step 6. The router also sends a context update, step 7 to the control system CS so that the address and service assignment to the client C on the relevant interface can be known to the control system. Steps 5, 5a, 5b and 6 are repeated to maintain the IP address lease open as needed.
In the context of the client, whether the system is configured as in
At the end of an IP address lease, the address is released and the client loses its IP connection. The next DHCP discover from that client on that interface will be treated as new and may be handled in a different way to the way in which it was previously.
The dynamic nature of the router configuration means that it is relatively easy to control the system to adapt to new services or providers, and does not require manual re-configuration of each router. This avoids the need to manually reconfigure every router once a new server or service is added to the system.
Further changes can be made within the scope of the invention. For example, in one further embodiment, some control system functionality is provided in the router R. In one example of such functionality, the control system may inspect the clients' DHCP discover message, in particular fields containing the client MAC address and the vendor-id field which are used to determine what type of client service causes the request for the IP address. Moving this functionality to the router R involves providing a set of service templates in the router R. When the client issues a DHCP discover, the router R inspects the DHCP discover message and attempts to match it against templates in a service list of client conditions. If a match is found in the list, that means that the particular service can be provided to the client. The service template can in turn also indicate that the packet should be relayed to an external DHCP server, the router's own internal DHCP server used, or a query sent to the control system for additional configuration information for the client.
This approach has the advantage that it provides a way to avoid the control system from the signalling chain, thus reducing the potential for every IP address assignment to be a possible single-point-of-failure. This general process would comprise analysing the message from the client to determine the service type, and then either configuring the router according to a stored template to either act as the DHCP server or to relay the request to an external DHCP server, or to pass the message on to the control system and respond in the same manner as is discussed above.
Number | Date | Country | Kind |
---|---|---|---|
07118409 | Oct 2007 | EP | regional |
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/EP2008/063270 | 10/3/2008 | WO | 00 | 8/9/2010 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2009/047215 | 4/16/2009 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
5586255 | Tanaka et al. | Dec 1996 | A |
5659736 | Hasegawa et al. | Aug 1997 | A |
5684988 | Pitchaikani et al. | Nov 1997 | A |
5689598 | Dean, Jr. et al. | Nov 1997 | A |
5802042 | Natarajan et al. | Sep 1998 | A |
5832503 | Malik et al. | Nov 1998 | A |
5913037 | Spofford et al. | Jun 1999 | A |
6028769 | Zurek | Feb 2000 | A |
6059614 | Shelby et al. | May 2000 | A |
6122639 | Babu et al. | Sep 2000 | A |
6222852 | Gandy | Apr 2001 | B1 |
6233616 | Reid | May 2001 | B1 |
6286038 | Reichmeyer et al. | Sep 2001 | B1 |
6393472 | Anerousis et al. | May 2002 | B1 |
6430621 | Srikanth et al. | Aug 2002 | B1 |
6560236 | Varghese et al. | May 2003 | B1 |
6680945 | Merchant et al. | Jan 2004 | B1 |
6769124 | Schoening et al. | Jul 2004 | B1 |
6839749 | Bera | Jan 2005 | B1 |
6876667 | Synnestvedt et al. | Apr 2005 | B1 |
6885657 | Rabenko et al. | Apr 2005 | B1 |
6954436 | Yip et al. | Oct 2005 | B1 |
6958996 | Xiong | Oct 2005 | B2 |
7054309 | Hoot et al. | May 2006 | B1 |
7082463 | Bradley et al. | Jul 2006 | B1 |
7099158 | Bjorklund | Aug 2006 | B1 |
7139818 | Kinnear, Jr. et al. | Nov 2006 | B1 |
7200145 | Edsall et al. | Apr 2007 | B1 |
7218827 | Vongseng et al. | May 2007 | B2 |
7222359 | Freund et al. | May 2007 | B2 |
7290046 | Kumar | Oct 2007 | B1 |
7293077 | Teo et al. | Nov 2007 | B1 |
7386629 | Rover et al. | Jun 2008 | B2 |
7467229 | Briggs et al. | Dec 2008 | B1 |
7536464 | Dommety et al. | May 2009 | B1 |
7581024 | Yip et al. | Aug 2009 | B1 |
7640287 | Gai et al. | Dec 2009 | B1 |
7640340 | Stapp et al. | Dec 2009 | B1 |
7702732 | Squire et al. | Apr 2010 | B1 |
7711826 | Ford | May 2010 | B2 |
7760984 | Solheid et al. | Jul 2010 | B2 |
7788345 | Sukiman et al. | Aug 2010 | B1 |
7801133 | Siegel | Sep 2010 | B2 |
7826463 | Patel et al. | Nov 2010 | B2 |
7882169 | Droms et al. | Feb 2011 | B1 |
7929452 | Diamant et al. | Apr 2011 | B2 |
7945164 | Theodoras, II | May 2011 | B2 |
7948993 | Kini et al. | May 2011 | B2 |
7966409 | Daruwalla et al. | Jun 2011 | B1 |
7969880 | Yano et al. | Jun 2011 | B2 |
7983190 | Hirota | Jul 2011 | B2 |
7990994 | Yeh et al. | Aug 2011 | B1 |
8054804 | Small et al. | Nov 2011 | B2 |
8098659 | Shida | Jan 2012 | B2 |
8296400 | Gorthy et al. | Oct 2012 | B2 |
8296438 | Brown et al. | Oct 2012 | B2 |
20020023174 | Garrett et al. | Feb 2002 | A1 |
20020075844 | Hagen | Jun 2002 | A1 |
20020103878 | Moncibais | Aug 2002 | A1 |
20020161801 | Hind et al. | Oct 2002 | A1 |
20030039249 | Basso et al. | Feb 2003 | A1 |
20030056225 | Bione | Mar 2003 | A1 |
20030131107 | Godse et al. | Jul 2003 | A1 |
20030165140 | Tang et al. | Sep 2003 | A1 |
20030200285 | Hansen et al. | Oct 2003 | A1 |
20030206548 | Bannai et al. | Nov 2003 | A1 |
20040013126 | Yun | Jan 2004 | A1 |
20040017829 | Gray et al. | Jan 2004 | A1 |
20040047353 | Umayabashi et al. | Mar 2004 | A1 |
20040049568 | Nguyen et al. | Mar 2004 | A1 |
20040052216 | Roh | Mar 2004 | A1 |
20040090965 | Lin | May 2004 | A1 |
20040128367 | Piercy et al. | Jul 2004 | A1 |
20040160464 | Reyna | Aug 2004 | A1 |
20040172412 | Files et al. | Sep 2004 | A1 |
20040213152 | Matuoka et al. | Oct 2004 | A1 |
20040258074 | Williams et al. | Dec 2004 | A1 |
20040267949 | Rover et al. | Dec 2004 | A1 |
20050044265 | Vinel et al. | Feb 2005 | A1 |
20050049886 | Grannan et al. | Mar 2005 | A1 |
20050129379 | Reagan et al. | Jun 2005 | A1 |
20050216584 | Chisholm | Sep 2005 | A1 |
20050281526 | Vongseng et al. | Dec 2005 | A1 |
20050286517 | Babbar et al. | Dec 2005 | A1 |
20060002324 | Babbar et al. | Jan 2006 | A1 |
20060026228 | Kim | Feb 2006 | A1 |
20060047791 | Bahl | Mar 2006 | A1 |
20060085532 | Chu et al. | Apr 2006 | A1 |
20060261116 | Brandeis | Nov 2006 | A1 |
20060277603 | Kelso et al. | Dec 2006 | A1 |
20070058538 | Chiang et al. | Mar 2007 | A1 |
20070058638 | Guichard et al. | Mar 2007 | A1 |
20070061458 | Lum | Mar 2007 | A1 |
20070168547 | Krywaniuk | Jul 2007 | A1 |
20070174522 | Lee | Jul 2007 | A1 |
20070203999 | Townsley et al. | Aug 2007 | A1 |
20070286198 | Muirhead et al. | Dec 2007 | A1 |
20080162609 | Bigian et al. | Jul 2008 | A1 |
20080219281 | Akin et al. | Sep 2008 | A1 |
20080285569 | Stademann et al. | Nov 2008 | A1 |
20110161360 | Lundstrom | Jun 2011 | A1 |
Number | Date | Country |
---|---|---|
1 039 698 | Sep 2000 | EP |
1780941 | May 2007 | EP |
2 069 767 | Jan 1981 | GB |
20010038481 | May 2001 | KR |
WO9534975 | Dec 1995 | WO |
WO 9826549 | Jun 1998 | WO |
WO 00 60864 | Oct 2000 | WO |
WO 0235797 | May 2002 | WO |
WO 2008068316 | Jun 2008 | WO |
WO 2008113852 | Sep 2008 | WO |
WO 2008113854 | Sep 2008 | WO |
WO 2009007327 | Jan 2009 | WO |
WO 2009019300 | Feb 2009 | WO |
WO 2009027513 | Mar 2009 | WO |
WO 2009035719 | Mar 2009 | WO |
WO 2009047334 | Apr 2009 | WO |
WO 2009047345 | Apr 2009 | WO |
Entry |
---|
Bodzinga, Anne, et al., “Interworking IPTV Services with IMS”, Telecommunications Network Strategy and Planning Symposium 2006 pp. 1-5. |
Cohen, Reuven, et al., “Video-on-Demand Session Management”, IEEE Journal on Selected Areas in Communications vol. 14, No. 6. |
European Search Report issued in EP Application 06125497, Publication 1931085, mailed Jan. 9, 2009, 8 pages. |
International Search Report and Written Opinion for PCT/EP2008/053369, mailed Jul. 2, 2008, 10 pages. |
International Search Report and Written Opinion for PCT/EP2008/060384, mailed Nov. 11, 2008, 10 pages. |
International Search Report and Written Opinion for PCT/EP2008/061403, mailed Dec. 18, 2008, 12 pages. |
International Search Report and Written Opinion for PCT/EP2007/063467, mailed Mar. 4, 2008, 7 pages. |
International Search Report for PCT/EP2008/053374, mailed Sep. 25, 2009, 3 pages. |
International Search Report and Written Opinion for PCT/EP2008/056563, mailed Aug. 21, 2008, 11 pages. |
International Search Report for PCT/EP2008/063667, mailed Jul. 30, 2009, 3 pages. |
International Search Report for PCT/EP2008/063639, mailed Oct. 1, 2009, 2 pages. |
International Search Report for PCT/EP2008/063270, mailed Jan. 21, 2009, 3 pages. |
International Search Report and Written Opinion for PCT/EP2008/056565, mailed Jan. 19, 2009. |
European Search Report issued in EP Application 07104707, Publication 1973269, dated Aug. 27, 2007, 7 pages. |
Pezeshki, Ali et al., “A network for recursive extraction of canonical coordinates” Neural Networks 16 (2003) 801-808. |
Number | Date | Country | |
---|---|---|---|
20100312818 A1 | Dec 2010 | US |