WO2002003616A2 - Plug and play installation of router for use in a network such as a cellular telecommunications network - Google Patents

Abstract

A new node (3) is initially connected to a network as a host. The new node (3) is first configured as a host in the network. The new node receives an address (e.g., IP address) during the host configuration process. This address is then used to transfer router configuration data from another node in the network to the new node in order to configure the new node as a router. When the new node has received the router configuration data, it can switch from a host mode to a router mode and thereafter function at least as a router in the network. This enables a router to be configured at least partially in an automatic manner after being connected to a network. Certain manual router configuration requirements of the prior art may thus be avoided in certain embodiments.

Description

PLUG AND PLAY INSTALLATION OF ROUTER FOR USE IN A NETWORK SUCH AS A CELLULAR TELECOMMUNICATIONS NETWORK

This invention relates to a system and method for automatically configuring a router upon its connection to a network. More particularly, this invention relates to a system and method for initially configuring a node as a host upon its connection to a network, and thereafter configuring the node/host as a router so that it can function in the network as a router.

BACKGROUND OF THE INVENTION

Networks (e.g., Internet Protocol (IP) networks) typically include a number of interconnected nodes. A network may include a plurality of subnetworks, each subnetwork including one or more nodes. Nodes are usually either "hosts" or "routers." A "host" is end-user equipment which originates and receives packets (including but not limited to IP packets). A personal computer (PC) is an example of a host. A "router", on the other hand, is equipment which routes and forwards packets (including but not limited to IP packets) to their destination(s). Thus, a router is often characterized as a computer that attaches two or more subnetworks/networks or devices and forwards packets from one to the other. In a non-limiting example of an IP network, a router uses the destination IP address on an IP datagram (or message) to choose where to forward the datagram. Often, there are a vast number of hosts in a network, but not so many routers. It is known to automatically configure a host upon its connection to a network. For example, a host may be connected to a network port and configuration data automatically downloaded to the host from a Dynamic Host Configuration Protocol (DHCP) server. For example, see U.S. Patent No. 5,884,024, the disclosure of which is hereby incorporated herein by reference. A DHCP type of automatic host configuration may enable savings of time and/or expense for system administrators of large networks including many hosts. Unfortunately, manual techniques are currently used to configure routers upon their connection to a network. Such manual configuration may be in the form of an on- site configuration by a command line interface, or remotely via Simple Network Management Protocol (SNMP) or Common Object Request Broker Architecture (CORBA). Problems arise in the context of building and/or administering an IP- network including many routers (e.g., hundreds or even thousands of routers). Manual router configuration in such vast networks would be undesirably burdensome as to time and/or cost. Moreover, the more routers in a network to be manually configured, the greater the risk of configuration error by an operator during configuration. Thus, it will be apparent to those skilled in the art that there exists a need in the art for a system for enabling a router(s) to be automatically configured upon connection to a network (e.g., to an IP network or any other type of network).

SUMMARY OF THE INVENTION

An object of this invention is to provide a system and/or method for automatically configuring a router upon its connection to a network. While some information may be pre-configured in the router prior to its connection to the network, and/or some information may be manually configured after its connection, at least some router configuration data information is automatically downloaded from another node following the router's connection to the network, so that the router is said to be automatically configured upon connection to the network.

In an exemplary embodiment of this invention, a new node is initially connected to a network as a host. The node is automatically configured (e.g., by a DHCP server) as a host in the network. The new node receives at least one address (e.g., IP address) during the host configuration process. This address(es) is then used to transfer router configuration data from another node (e.g., a management server) in the network to the new node in order to configure the new node as a router. When the new node has received the router configuration data, it can switch from a host mode to a router mode and thereafter function at least as a router in the network. In certain embodiments, the new node may function as both a host and router. Certain manual router configuration techniques of the prior art may thus be avoided.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a flowchart illustrating certain steps performed during the course of configuring a router according to an exemplary embodiment of this invention.

Figure 2 is a schematic diagram illustrating a portion of a network according to an embodiment of this invention, in which a new router may be configured when connected to the network.

Figure 3 is a schematic diagram of a cellular telecommunications network including an IP network in which exemplary embodiments of this invention may be implemented.

Figure 4 is a functional block diagram illustrating certain components of a node according to an embodiment of this invention.

Figure 5 is a diagram of the protocol structure of the node of Fig. 4 according to an exemplary embodiment of this invention.

Figure 6 is a functional diagram illustrating how first and second nodes according to an embodiment of this invention may communicate using ATM connections.

Figure 7 is a schematic diagram illustrating how a new node is initially configured as a host upon connection to an IP network according to an exemplary embodiment of this invention, with the received address (e.g., IP address) being registered with a DNS server.

Figure 8 is a schematic diagram illustrating the new node of Fig. 7 using the host parameters it received in the Fig. 7 process to fetch router configuration data from a management node, according to an embodiment of this invention.

Figure 9 is a functional chart illustrating how the new node is configured as a host during the Fig. 7 process. Figure 10 is a schematic diagram illustrating how the new node of Figs. 7-8 can optionally fetch an IP address via a second interface, with the new address being registered with a DNS server.

DETAILED DESCRIPTION OF THE DRAWINGS In the following description, for purposes of explanation and not limitation, specific details are set forth in order to provide an understanding of certain embodiments of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known devices, circuits, OSI models, protocols, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail. Referring now more particularly to the accompanying drawings in which like reference numerals indicate like parts throughout the several views.

Figure 1 is a flowchart illustrating certain steps taken in automatically configuring a router upon its connection to a network according to an exemplary embodiment of this invention. A router is first connected to the network as a host. After connection to the network, it is first automatically configured using conventional automatic host configuration techniques (e.g., DHCP and/or BOOTP). Thereafter, once configured as a host, it downloads router configuration data from another server in the network. After it has been configured as a router, it can switch from a host mode over to a router mode. The resulting node may function solely as a router in the network, or may function as both a host and router in the network. In certain embodiments, the router may include local DHCP capability for clients/hosts which connect to the router's subnetwork. Referring to Figures 1-2, the new node (to be configured as a router) 3 is initially connected to the network with an interface link 7 to a neighboring node 5 (see step 2 in Figure 1). Knowledge of this link 7 may be pre-configured or pre-programmed into the new node 3 prior to its installation, or even just after it has been installed/connected. The new node 3 may be pre-configured to initially act as a host in the network; and a host name may be manually configured into node 3 either before or after the new node is connected to the network.

After being connected to the network, new node 3 automatically starts an automatic host configuration process in which it communicates with neighboring node 5. Node 5 may be an immediately adjacent node, or may be a distant node with which the new node 3 can communicate through a plurality of intermediate/interconnected routers. New node 3 is automatically configured as a host using a conventional host configuration technique (see step 4 in Figure 1). This automatic host configuration may be carried out via a stand-alone DHCP server node 5. Alternatively, this automatic host configuration may be carried out via BOOTP (instead of DHCP), or any other suitable method/process. In still further embodiments, node 5 may be a DHCP server incorporated into a UTRAN node. This automatic host configuration may be carried out via a DHCP server in existing router node 5 (i.e., in the neighboring node).

In embodiments where the DHCP server 5 is a stand-alone node, the new node 3 may either contact it directly or alternatively through another node (e.g., an exiting UTRAN node). In the latter case, in the UTRAN node to which the new node is connected, a BOOTP relay agent may be used to reach the stand-alone or central DHCP server 5.

For example, in an IP network an IP address(es) may be provided automatically to the new node 3 using the Dynamic Host Configuration Protocol (DHCP) per Internet RFC 1541, hereby incorporated herein by reference. DHCP is an extension of the Bootstrap Protocol (BOOTP), allowing hosts on a TCP/IP network to dynamically obtain basic configuration information (e.g. IP address(es)). DHCP provides for dynamic automatic set-up of IP addresses for stations in a network. For example, after the new node is turned on, it and a DHCP server at another node 5 of the network may exchange (either directly or indirectly through other node(s)) DHCPDISCOVERY (node 3 asking DHCP server for an IP address), DHCP OFFER (DHCP server offering node 3 an address), DHCPREQUEST (node 3 attempting to accept the offer), and DHCPACK (DHCP server leases or otherwise provides IP address to the new node 3) messages during the IP address allocation process (see Fig. 9). The IP address provided to the new node 3 by the DHCP server may expire after a given period of time, or alternatively may be static, in different embodiments of this invention. Moreover, it is noted that this invention is not limited to DHCP type host configuration; and any other type of suitable host configuration (e.g., BOOTP-protocol) may instead be used to initially configure the new node as a host in the network and/or to provide it with a network layer address.

In the automatic host configuration process, new node 3 thus receives an address (e.g., IP address) from the DHCP server. The DHCP seryer at node 5 then updates a Domain Name System (DNS) server 9 of the network with data about the new node/host 3 (e.g., its assigned IP address, etc.), optionally via one or more intermediate router(s) 11. At this point, new node 3 is connected to the network as a host (see step 6).

The new node 3 is programmed (either before or after it is connected to the network) to determine whether or not it is to become a router (see step 8). If the new node determines that it is not to become a router in the network, then the new node will simply continue to function as a host in the network (see step 10). However, if the new node 3 determines that it is to become a router at step 8, then it contacts a management node 13 in the network and begins to automatically download router configuration data from the management node (see step 12). Management node 13 may be or include a Lightweight Directory Access Protocol (LDAP) server or any other type of suitable server which is capable of downloading router configuration data to the new node 3. In other embodiments, the downloading of router configuration data may be done from an FTP/TFTP server node 13. It is noted that in certain embodiments, the new node 3 will have received the address to the LDAP or FTP/TFTP server 13 and/or the file name of the router configuration file thereat from node 5 (e.g., DHCP server node).

As shown in Figure 2, the new node 3 may communicate with the management node 13 (e.g., LDAP server) via one or more intermediate routers 5, 11, or may even directly communicate with the management node 13 in certain embodiments. Thus, in step 12, data is downloaded from management node 13 to the new node 3; such data including information needed for the new node 3 to work as a router in the network. This information may include, for example and without limitation, knowledge of all connected interfaces as well as other necessary router configuration information. Once the router configuration data has been received and stored in memory by the new node 3, the new node switches from a host mode to at least a partial router mode so as to thereafter function at least as a router in the network (see step 14).

Thus, it is possible to connect routers in a plug-and-play manner so as to minimize or reduce the need for certain types of time consuming manual router configuration. However, it is recognized that in certain embodiments of this invention some limited amount of manual router configuration may take place before and/or after the router has been initially connected to the network (e.g., a host name may be manually configured into the router, identity of other node(s) in the network may be manually configured into the router, etc.). Nonetheless, the new node is still said herein to be automatically configured as a router due to the router configuration data that is automatically downloaded to the new node from another node in the network.

As will be appreciated by those of skill in the art, the invention illustrated and described with respect to Figures 1 and 2 may be implemented in an Internet Protocol (IP) network. However, the invention is not so limited and may be implemented in any other type of suitable network which may use different type(s) of protocol(s). Set forth below with reference to Figures 3-10 is an exemplary embodiment of this invention where the invention is implemented in the context of an IP network of a cellular telecommunications network. Again, it will be recognized by those of skill in the art that the invention is not so limited, as it may instead be implemented in non-cellular communication networks and other types of IP and non-IP networks.

Referring to Figures 3-10, one advantageous application of the present invention is now described in the non-limiting example context of a Universal Mobile Telecommunications System (UMTS) 15. With particular reference to Figure 3, a representative, circuit-switched external core network 17 may be, for example, the public switched telephone network (PSTN) and/or the Integrated Service Digital Network (ISDN). Another circuit-switched external core network may correspond to the Public Land Mobile radio Network (PLMN) 19. A representative packet-switched external core network 21 may be, for example, an IP network such as the Internet. The core networks are coupled to corresponding network service nodes 23. The

PSTN/ISDN network 17 and other PLMN network (s) 19 may be connected to a circuit- switch core node 25, such as a Mobile Switching Center (MSC) that provides circuit switched services. It is further noted that UMTS 15 may coexist with an existing cellular network, such as the Global System for Mobile Communications (GSM) where MSC 25 is connected over an interface 27 to a base station subsystem 29 which in turn is connected to radio base station (BS) 31 over an interface 33.

Packet-switched network 21 may be connected over interface 35 to a packet- switched core node (PSCN), e.g., a General Packet Radio Service (GPRS) node 37 tailored to provide packet-switched type services. Each of core network service nodes 25 and 37 also connects to UMTS Terrestrial Radio Access Network (UTRAN) 41 over a radio access network interface. The UTRAN 41 includes one or more Radio Network Subsystems (RNS) 43 each with at least one radio network controller (RNC) 45 coupled to a plurality of base stations (BS) 47 and to other RNCs in the UTRAN 41. As will be seen below, the implementation of certain embodiments of this invention may be within UTRAN 41, as the UTRAN utilizes an IP network so as to allow, inter alia, nodes 45, 47 to communicate with one another. The IP network in UTRAN 41 may be used only for operation and maintenance of the UTRAN network (not for user traffic); but in alternative embodiments this IP network of the UTRAN may be used for user traffic only or in addition to operation and/or maintenance traffic. Still referring to Figure 3, radio access over radio interface 49 may be based upon Wideband Code Division Multiple Access (WCDMA) with individual radio channels allocated using CDMA channelization or spreading codes. Of course, other access methods may instead be employed, such as TDMA and/or other types of CDMA. WCDMA provides wide bandwidth for multi-media services and other high transmission rate demands, as well as robust features like diversity handoff to ensure high quality communication service in frequently changing environments. Each Mobile Station (MS) 51 may be assigned its own scrambling code for a base station (BS) 47 to identify transmissions from that particular MS 51. Each MS 51 may also use its own scrambling code to identify transmissions from a base station 47 either on a general broadcast or common channel, or transmissions specifically intended for that MS. As illustrated, mobile stations 51 communicate with base stations 31, 47 over radio interface 49, using common and/or dedicated radio channels.

Still referring to Figure 3, the UTRAN 41 is made up of a large number of nodes in an IP network. For example, each base station (BS) 47 and each RNC 45 in UTRAN 41 is a node, with each of these often functioning as an IP router. The IP network uses the infrastructure of the UTRAN. IP packets are transported over asynchronous transfer mode (ATM) connections between nodes (e.g., between base stations, between RNCs, and or between a base station and an RNC). Moreover, in certain embodiments of this invention, IP based management systems may be connected to nodes in UTRAN 41 via Ethernet Local Area Networks (LAN) attached to physical Ethernet interfaces on the UTRAN nodes. Thus, many if not all UTRAN nodes (e.g., 45, 47) contain IP host and router functionality which makes it possible to send IP packets to any node in the UTRAN, and reach it/them via routing in intermediate nodes. The IP functionality in UTRAN 41 may be used for operation and maintenance purposes, and/or user data functionality. For purposes of example, IP may be used in UTRAN 41 for management communication, to make it possible to create an IP-based intra-network between UTRAN nodes where all nodes can be reached with high reliability, to make it possible to collect performance information from UTRAN nodes, and/or to ensure that management traffic does not interfere with communications in the user plane. IP support within UTRAN need not be for real time communications in preferred embodiments, although it may be used for that purpose in alternative embodiments of this invention.

Within the IP network of the UTRAN, nodes are identified by network layer addresses such as IP addresses. These addresses provide a simple mechanism for identifying the source and destination of messages within the network. For example, an IP address may be a 32-bit (or more) binary number with a format of four or more bytes, divided into four or more 8-bit parts. Typically, each byte of an IP address (e.g. 140.179.220.200) is a number from 0 to 255, with one part of the address identifying the network or subnetwork and another part the node. Exemplary IP addresses are shown in Figs. 7-8 and 10 (e.g., node 103 has in IP address of 10.0.0.1).

There may be tens, hundreds, or even thousands of different nodes in UTRAN 41. Again, many if not all of such nodes include router functionality. Those of skill in the art will recognize the benefit of being able to reduce manual configuration needs for routers (e.g., for RNC and BS nodes) added to the UTRAN. Prior to description of an exemplary embodiment of this invention, Figures 4-6 are referred to for a general understanding of an exemplary node(s) of the UTRAN. Figure 5 illustrates a protocol stack of an exemplary node (e.g., including router functionality) in the UTRAN. The node behaves conceptuality as a multihomed host and a router (e.g., OSPF router). When the node is configured as a router, a router protocol application (e.g., OSPF) 61 is connected to the stack via, for example, a raw socket interface 63. Open Shortest Path First (OSPF) Interior Gateway Protocol (OSPFIGP) is an OSPF specific protocol used to propagate network reachability and routing information within an OSPF system. In other embodiments, a Boarder Gateway Protocol (BGP) may be used as a router protocol instead of OSPF. The protocols and respective applications of the Fig. 5 node are stored in corresponding memory locations.

From other nodes in the UTRAN, applications 53 of a node can be reached with any of the addresses of the attached interfaces (e.g., IP addresses). The configuration data of the node determines how interfaces are attached to the IP stack 55. It is possible to configure one or more Ethernet interface(s) 57 and a plurality of ATM interfaces 59. Virtual Path Identifiers (VPI) and Virtual Circuit Identifiers (VCI) (see VP/VC in Fig. 5) are two known fields of an ATM connection identifier. The illustrated node is further configured with data defining the operation of Transmission Control Protocol (TCP) 65 and User Datagram Protocol (UDP) transport services. TCP is a known reliable connection oriented transport layer protocol defined in the Internet suite of protocols. A TCP connection is typically a byte stream type of connection using a higher layer protocol if package oriented service is wanted. UDP is a protocol layer above IP, which provides a less reliable but more efficient datagram service. The service is available to applications via the socket interface. Examples of utilities that use this service are DHCP, TFTP, and BOOTP. BOOTstrap Protocol is known in the art and may be used by a host to obtain start-up information, including an IP address from a server. Optionally, the node can also be configured so as to include DHCP server 67 capability for serving hosts on a site LAN and/or other nodes. As shown in Figures 5-6, certain types of basic communication between respective nodes in the UTRAN are provided by point-to-point links based upon ATM connections via respective interfaces 59. Each point-to-point link between nodes may utilize a pair of virtual channels (VC), intended for high and low prioritized traffic as illustrated. IP messages communicated between nodes may be packed in LLC/AAL 5 frames using VP/VC ATM connections. ATM Adaption Layer 5 (AAL5) is a protocol above ATM used to send conventional data packets across an ATM network.

Figure 4 illustrates that each UTRAN node may include one or more processors 69 as is known in the art. In an exemplary embodiment, the IP stack and OSPF protocol of a node may execute together on one processor 69 in the cluster. ATM connections that are used for IP communication with other nodes may terminate on this same processor. Plug and play utilities here may also execute on this same processor. Other processors 69 may perform functions known in the art as to RNC and BS nodes.

Figures 7-8 illustrate an embodiment of this invention which may be implemented in UTRAN 41. Included in the UTRAN are DNS server 103, management node 105 (e.g., including an LDAP server), root nodes 107, new node 109 to be added/connected to the network and automatically configured as a router, and a plurality of existing nodes (e.g., routers) 111. Existing nodes 111 may be, for example, base stations 47, RNCs 45, or any other type of node in the UTRAN. It is noted that thin lines 115 represent ATM connections while thicker lines 117 represent Ethernet connections. The network of Figs. 7-8 is basically tree-shaped, so that uplink and downlink relations between nodes may be defined. Each node may know a primary uplink interface through which an initial network connection is typically established (e.g., a type of ATM connection or point-to-point link). Via a primary uplink interface of a node, the node can reach specific management nodes (e.g., 103, 105, or 107) and network configuration information can be fetched. Each node by default may support the OSPFIGP routing protocol. Nodes are interconnected by point-to-point ATM connections that on the IP level may be handled as separate subnets. Thus, many or all nodes connected via ATM can have IP-router to IP-router connections. Referring to Figure 7, new node 109 (that is eventually to be a router) is first connected to the network with an interface link 115, 121 (see reference numeral 119) to a neighboring router node 111 having DHCP server capability (see the darkened in node 111 in Fig. 7, having IP address 10.0.3.2). The new node 109 may contact DHCP server node 111 either directly, or indirectly via other node(s). Furthermore, node 111 may be a stand-alone DHCP server in certain embodiments of this invention, or alternatively may be incorporated into a UTRAN node in other embodiments. Thus, in addition to embodiments where DHCP server node 111 is a stand-alone DHCP node, it may instead be a base station, an RNC, or any other type of node in network 41. Preferably, the new node contacts the DHCP server node 111 via a broadcast message. Alternatively, knowledge of this link may have been pre-configured in new node 109 prior to or just after its connection to the network. Optionally, the new node also may have been pre-configured to act as a host, and a host name may have been pre- configured into the new node 109 either before or just after the new node's connection to the network. Using pre-configuration, new node 109 starts a DHCP host configuration process toward its primary ATM link 121 to the darkened neighboring node 111 in Fig. 7. This neighboring or other node 111 includes a DHCP server therein, or at least local DHCP server capability. The DHCP process for configuring new node 109 as a host is shown in Figure 9. First, the new node 109 broadcasts a DHCPDISCOVER message looking for the appropriate neighboring node including the DHCP server. The DHCP server at neighboring node 111 receives the DHCPDISCOVER message, looks up an IP address for the new node, and makes a provisional IP address lease allocation in its DHCP table. The DHCP server then sends a DHCPOFFER message to the new node 109 via link 115 offering the new node this IP address. If the new node decides to accept this IP address, it sends a DHCPREQUEST message back to the DHCP server at darkened node 111. If the IP address lease is still available, the DHCP server at node 111 sends a DHCPACK message to the new node leasing the IP address to the new node (see IP address 10.0.8.2 of new node 109 in Fig. 7). This IP address (10.0.8.2) may be leased to the new node 109 either for a predetermined period of time, or alternatively in a static manner. Furthermore, it is noted that the DHCP server may also provide the new node 109 with other needed parameters during the host configuration process. For example, the DHCP server may also provide the new node with the address of the LDAP FTP/TFTP server (see node 13 or node 105) and/or the file name of the router configuration file. The DHCP server at neighboring node 111 then registers the new IP address

(10.0.8.2) for new node 109 with the DNS server 103. In certain embodiments, when addresses are dynamically allocated by a DHCP server to a host (node 9), the server may be responsible for registering the name to address (DNS A record) and/or address to name (PTR record) information in a Dynamic DNS (DDNS). DDNS is a protocol which may or may not be used together with DHCP to bind human-readable machine names into dynamic allocated IP addresses. Thus, the name of node 109 may be multiply registered. New node 109, having IP address 10.0.8.2, is now connected to the network as a host.

Referring now to Figure 8, the new node 109 uses certain parameter(s) (e.g., IP address, management node address, and/or router configuration file ID) received during the host configuration process to contact management node 105 and download therefrom router configuration data. Node 105 may include, for example, an LDAP server or any other type of suitable server capable of downloading router configuration data to the new node. The downloaded router configuration information includes data needed for the new node 109 to function as a router in the network. For example, the router configuration data transferred from management node 105 to new node 109 may include IP address per attached interface, IP network mask per attached interface, IP default router list per attached interface, DNS server list, LDAP server list, SNMP trap destination IP address, etc. Thus, one or more of these router configuration data may be obtained automatically as opposed to manually because of this invention.

After the router configuration data has been downloaded to new node 109, the new node will be aware of all its interfaces in the network topology. Once the router configuration data has been received by new node 109, the new node switches from a host mode to at least a router mode in the network. The new node may now function as a router, or as both as a host and router in the network.

In certain optional embodiments of this invention, after switching to a router mode the new node 109 may add a second ATM link (see reference numeral 131 in Figure 8). In this case, the new node repeats the above-described process of Figures 7 and 9 to obtain another IP address via the node's second interface via another neighboring node 111. As shown in Figure 10 at 133, the router node 109 and the darkened node 111 (having IP address 10.0.8.5) which includes a DHCP server, perform a DHCP type host configuration (see Figure 9). As a result, new router 109 receives an IP address (10.0.8.6) on the second interface. This address is then registered with DNS server 103 by the DHCP server (see reference numeral 135 in Figure 10) at node 111.

In other optional embodiments of this invention, a local DHCP server may be activated at node 109 to serve hosts in the Ethernet LAN 117 of node 109. Optionally, thin clients (TCs) 141 may now also be made part of the network with the help of the DHCP server support in new node 109. TCs may be, for example, portable PCs equipped with LAN-interface and a web browser. The host name of each thin client 141 can be automatically provided and registered by the local DHCP server support and/or DHCP server and DNS server 103. Thus, the DHCP server of node 109 may be set up with a locally configured address pool to use. Alternatively, a BOOTP relay agent may be used instead of a DHCP server, in which case IP addresses can be received from a management node.

While the invention has been described in connection with what is presently considered to be the most practical and preferred embodiments, it is to be understood that the invention is not to be limited to the disclosed embodiments, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims. For example, while this invention may be used in the context of new nodes being connected to a network for the first time, the invention may also be used in the context of nodes which are being connected to the network after having been repaired or taken off line. All such nodes are considered "new" nodes herein.

Claims

WHAT IS CLAIMED IS:

1. A method of configuring a new node upon connection of the new node to

a network, the method including connecting the new node to the network, the method

being characterized by:

automatically configuring the new node as a host in the network; and

after the new node has been configured as a host, downloading router

configuration data to the new node in order to configure the new node as a router.

2. The method of claim 1, further characterized by the new node switching

from a host mode to a router mode after the new node has been configured as a router.

3. The method of claim 1 , further characterized in that said configuring the

node as a host step further comprises configuring the node as a host using one of

Dynamic Host Configuration Protocol (DHCP) and BOOTP protocol.

4. The method of claim 3, further characterized by:

providing a DHCP server at a node of the network; and

wherein said configuring the node as a host step further comprises configuring

the new node as a host using Dynamic Host Configuration Protocol (DHCP) via the

DHCP server.

5. The method of claim 1, further characterized by:

providing a management node in the network and a DHCP server node in the

network;

wherein said configuring the new node as a host in the network step includes the

new node receiving an IP address from the DHCP server node; the new node determining whether or not it is to become a router in the network;

and

wherein said downloading router configuration data step includes downloading

the router configuration data to the new node from the management node, wherein the

management node and the DHCP server node are different nodes in the network.

6. The method of claim 1, further characterized in that the network

comprises an Internet Protocol (IP) network.

7. The method of claim 6, further characterized in that at least part of the IP

network is part of a UTRAN of a cellular telecommunications network.

8. The method of claim 1, further characterized in that the new node

comprises one of a base station (BS) and a radio network controller (RNC) in a cellular

telecommunications network.

9. A node for connection to a network, the node including a processor for

executing a router protocol, said node characterized in that:

the node is configured so as to be automatically configured as a host in a

network to which it is to be connected, and to thereafter be automatically configured as

a router via another node in the network so that the node can switch from a host mode

to a router mode after it has been configured as a router.

10. The node of claim 9, further characterized in that the node comprises one

of a base station (BS) and a radio network controller (RNC) to be connected to a

cellular telecommunications network.

11. A cellular telecommunications network including an Internet Protocol

(IP) network having a plurality of base stations (BSs) and a plurality of radio network

controllers (RNCs); at least one DHCP server node; at least one management node; and

wherein the cellular telecommunications network is characterized in that:

a new node connected to the IP network is initially configured as a host via the

DHCP server node and is thereafter configured as a router via the management mode.

12. The cellular telecommunications network of claim 11, further

characterized in that the new node, after being configured as a router, functions as both

a router and a host in the IP network.

13. The cellular telecommunications network of claim 11 , further

characterized in that the DHCP server node comprises one of a stand-alone DHCP

server node, a base station, and a RNC of the cellular telecommunications network.

14. The cellular telecommunications network of claim 11, further

characterized in that the management node comprises a LDAP server.

15. The cellular telecommunications network of claim 11, further

characterized in that the IP network comprises a UTRAN of a cellular

telecommunications network.

16. The cellular telecommunications network of claim 11, further

characterized in that the new node, the DHCP node, and the management node

communicate with one another via ATM interfaces and connections.

17. The cellular telecommunications network of claim 11, further

characterized in that the new node switches from a host mode to a router mode after the

new node is configured as a router.

18. A method of configuring a new node upon connection of the new node to

a network, the method including connecting the new node to the network, and being

characterized by:

configuring the new node as a host in the network; and

after the new node has been configured as a host, downloading router

configuration data to the new node in order to configure the new node as a router.