Node configuration setup system with servers hunting through connection-oriented network for client's data

• US 6,314,088 B1
• Filed: 09/19/1997
• Issued: 11/06/2001
• Est. Priority Date: 09/20/1996
• Status: Expired due to Term

• Current Assignee: NEC Corporation
• Original Assignee: NEC Corporation
• Inventors: Yamano, Shigeki
• Primary Examiner(s): Nguyen, Chau
• Assistant Examiner(s): Boakye, Alexander O.
• Application Number:
  US08/933,927
• Time in Patent Office: 1,509 Days
• Field of Search: 370/216, 370/255, 370/217, 370/257, 370/395, 370/254, 370/389, 370/404, 370/410, 370/401, 455/200.33, 709/220, 709/221, 709/222, 709/203
• US Class Current: 370/254
• CPC Class Codes: H04L 2012/5631 Resource management and allocation
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/10 of different types

Abstract

A node configuration setup system comprises a configuration client node connected to a connection-oriented network, and a number of configuration server nodes interconnected via the network. A first configuration server node is responsive to an initial configuration inquiry message from the client node for returning a ready-to-accept message if it holds the client'"'"'s configuration data. If not, the first configuration server node selects a second configuration server node and causes the client node to download its configuration data from the second configuration server node either directly or via the first configuration server node if the client'"'"'s data is located in the second configuration server node.

Claims

1. A node configuration set-up system for a connection-oriented communication network, comprising:

a configuration client node connected to the network; and

a plurality of configuration server nodes interconnected via said network, a first one of the configuration server nodes being responsive to an initial configuration inquiry message from the configuration client node for transmitting a ready-to-accept message to the client node if client'"'"'s configuration data is located in the first configuration server node, selecting a second configuration server node from said plurality of configuration server nodes if said data is not located in the first configuration server, and causing the configuration client node to download the client'"'"'s data from the second configuration server node either directly or via said first configuration server node if the client'"'"'s data is located in the second configuration server node.

9. A node configuration setup system as claimed in claim 1, 2, 3 or 6, further comprising a name system server, wherein said first configuration server node is arranged to access said name system server to obtain address information of said second configuration server node.

10. A node configuration setup system as claimed in claim 1, 2, 3 or 6, wherein said network comprises an asynchronous transfer mode network.

11. A node configuration setup system as claimed in claim 1, 2, 3 or 6, wherein each of said configuration server nodes is arranged to transmit update message to the configuration client node when the client'"'"'s configuration data is updated,

said configuration client node being responsive to the update message for accessing the configuration server node from which the update message is received and downloading the updated client'"'"'s configuration data.

2. A node configuration set-up system for a connection-oriented communication network, comprising:

a configuration client node connected to the network; and

a plurality of configuration server nodes interconnected via said network, a first one of the configuration server nodes being responsive to an initial configuration inquiry message from the configuration client node for transmitting a ready-to-accept message to the client node if client'"'"'s configuration data is located in the first configuration server node, selecting a second configuration server node from said plurality of configuration server nodes if said data is located in the second configuration server rather than in the first configuration server node, and transmitting a change-server message to said configuration client node,

said configuration client node being responsive to the ready-to-accept message for downloading the client'"'"'s configuration data from the first configuration server node and responsive to the change-server message for accessing the second configuration server node and downloading the client'"'"'s configuration data therefrom.

3. A node configuration setup system for a connection-oriented communication network, comprising:

a configuration client node connected to the network; and

a plurality of configuration server nodes interconnected via said network, a first one of the configuration server nodes being responsive to an initial configuration inquiry message from the configuration client node for transmitting a first ready-to-accept message to the client node if client'"'"'s configuration data is located in the first configuration server node, selecting a second configuration server node from said plurality of configuration server nodes if said data is located in the second configuration server rather than in the first configuration server node, and receiving the client'"'"'s configuration data from the second configuration server node and transmitting a second ready-to-accept message to the configuration client node,

said configuration client node being responsive to either of the first and second ready-to-accept messages for downloading the client'"'"'s configuration data from the first configuration server node.

4. A node configuration setup system as claimed in claim 3, wherein said first configuration server node is arranged to select a third configuration server node from said plurality of configuration server nodes if said data is located in the third configuration server rather than in the second configuration server node, and receiving the client'"'"'s configuration data from the third configuration server node and transmitting said second ready-to-accept message to the configuration client node.

5. A node configuration setup system as claimed in claim 3, wherein said second configuration server node is arranged to select a third configuration server node from said plurality of configuration server nodes if said data is located in the third configuration server rather than in the second configuration server node, and transmitting a reply message to the first configuration server node, wherein said first configuration server node is responsive to the reply message for receiving the client'"'"'s configuration data from the third configuration server node and transmitting said second ready-to-accept message to the configuration client node.

6. A node configuration setup system for a connection-oriented communication network, comprising:

a configuration client node connected to the network; and

a plurality of configuration server nodes interconnected via said network, a first one of the configuration server nodes being responsive to an initial configuration inquiry message from the configuration client node for transmitting a ready-to-accept message to the client node if client'"'"'s configuration data is located in the first configuration server node, selecting a second configuration server node from said plurality of configuration server nodes if said data is located in the second configuration server rather than in the first configuration server node, and transmitting a direct-transfer request message to the second configuration server node,

said second configuration server node being responsive to the direct-transfer request message for transmitting a second ready-to-accept message to the configuration client node,

said configuration client node being responsive to the first ready-to-accept message for downloading the client'"'"'s configuration data from the first configuration server node and responsive to the second ready-to-accept message for downloading the client'"'"'s configuration data from the second configuration server node.

7. A node configuration setup system as claimed in claim 6, wherein said first configuration server node is arranged to select a third configuration server node from said plurality of configuration server nodes if said data is located in the third configuration server rather than in the second configuration server node and transmitting a direct-transfer message to the third configuration server node, wherein the third configuration server node is responsive to the direct-transfer message for transmitting said second ready-to-accept message to the configuration client node.

8. A node configuration setup system as claimed in claim 6, wherein said second configuration server node is arranged to select a third configuration server node from said plurality of configuration server nodes if said data is located in the third configuration server rather than in the second configuration server node, and transmitting a reply message to the first configuration server node, wherein said first configuration server node is responsive to the reply message for transmitting a direct-transfer message to the third configuration server node, wherein the third configuration server node is responsive to the direct-transfer message for transmitting said second ready-to-accept message to the configuration client node.

12. A node configuration setup method for a connection-oriented network, wherein a configuration client node is responsive to a ready-to-accept message from one of a plurality of configuration server nodes for downloading client'"'"'s configuration data therefrom, comprising:

a) determining, at a first configuration server node in response to an initial configuration inquiry message from said client node, whether or not said data is located in the first configuration server node;

b) if it is determined that said data is located in the first configuration server node, transmitting the ready-to-accept message from the first configuration server node to the client node;

c) if it is determined that said data is not located in the first configuration server node, selecting, at the first configuration server node, a second configuration server node and transmitting a change-server message from the first configuration server node to the client node;

d) transmitting, in response to said change-server message, an initial configuration inquiry message from the client node to the selected configuration server node;

e) determining, at the selected configuration server node in response to the inquiry message, whether or not client'"'"'s configuration data is located in the selected configuration server node;

f) if it is determined that said data is located in the selected configuration server node, transmitting said ready-to-accept message to the configuration client node; and

g) if it is determined that said data is not located in the second configuration server node, selecting, at the first configuration server node, a further configuration server node and transmitting a change-server message to the client node, and returning to the step (d).

16. The method of claim 12, 13 or 15, wherein the step (g) comprises:

determining, at the first configuration server node, a name of said further configuration server node;

transmitting said name from the first configuration server node to a name system server; and

receiving, at the first configuration server node, address information of the further configuration server node from the name system server.

18. The method of claim, 12, 13, 14, 15 or 17, wherein the step (c) comprises:

determining, at the first configuration server node, a name of said second configuration server node;

transmitting said name from the first configuration server node to a name system server; and

receiving, at the first configuration server node, address information of the second configuration server node from the name system server.

13. A node configuration setup method for a connection-oriented network, wherein a configuration client node is responsive to a ready-to-accept message from one of a plurality of configuration server nodes for downloading client'"'"'s configuration data therefrom, comprising:

a) determining, at a first configuration server node in response to an initial configuration inquiry message from said client node, whether or not said data is located in the first configuration server node;

b) if it is determined that said data is located in the first configuration server node, transmitting said ready-to-accept message from the first configuration server node to the client node;

c) if it is determined that said data is not located in the first configuration server node, selecting, at the first configuration server node, a second configuration server node;

d) transmitting a forward-transfer request message from the first configuration server node to the selected configuration server node;

e) determining, at the selected configuration server node in response to the forward-transfer request message, whether or not said data is located in the selected configuration server node;

f) if it is determined that said data is located in the selected configuration server node, transmitting said data from the selected configuration server node to the first configuration server node and transmitting said ready-to-accept message from the first configuration server node to the client node; and

g) if it is determined that said data is not located in the selected configuration server node, selecting, at the first configuration server node, a further configuration server node and returning to the step (d).

14. A node configuration setup method for a connection-oriented network, wherein a configuration client node is responsive to a ready-to-accept message from one of a plurality of configuration server nodes for downloading client'"'"'s configuration data therefrom, comprising:

a) determining, at a first configuration server node in response to an initial configuration inquiry message from the client node, whether or not said data is located in the first configuration server node;

b) if it is determined that said data is located in the first configuration server node, transmitting said ready-to-accept message from the first configuration server node to the client node;

c) if it is determined that said data is not located in the first configuration server node, selecting, at the first configuration server node, a second configuration server node;

d) transmitting a forward-transfer request message from the first configuration server node to the selected configuration server node;

e) determining, at the selected configuration server node in response to the forward-transfer request message, whether or not said data is located in the selected configuration server node;

f) if it is determined that said data is located in the selected configuration server node, transmitting said data from the selected configuration server node to the first configuration server node and transmitting said ready-to-accept message from the first configuration server node to the client node;

g) if it is determined that said data is not located in the selected configuration server node, selecting, at the selected configuration server node, a further configuration server node and transmitting a reply message from the previously selected configuration server node to the first configuration server node; and

h) transmitting, in response to the reply message, a forward-transfer request message from the first configuration server node to the configuration server node selected by the step (g), and returning to the step (e).

19. The method of claim 14 or 17, wherein the step (g) comprises:

determining, at the selected configuration server node, a name of said further configuration server node;

transmitting said name from the selected configuration server node to a name system server; and

receiving, at the selected configuration server node, address information of the further configuration server node from the name system server.

15. A node configuration setup method for a connection-oriented network, wherein a configuration client node is responsive to a ready-to-accept message from one of a plurality of configuration server nodes for downloading client'"'"'s configuration data therefrom, comprising:

a) determining, at a first configuration server node in response to an initial configuration inquiry message from said client node, whether or not said data is located in the first configuration server node;

b) if it is determined that said data is located in the first configuration server node, transmitting said ready-to-accept message from the first configuration server node to the client node;

c) if it is determined that said data is not located in the first configuration server node, selecting, at the first configuration server node, a second configuration server node;

d) transmitting a direct-transfer request message from the first configuration server node to the selected configuration server node;

e) determining, at the selected configuration server node in response to the direct-transfer request message, whether or not said data is located in the selected configuration server node;

f) if it is determined that said data is located in the selected configuration server node, transmitting said ready-to-accept message from the selected configuration server node to the client node; and

g) if it is determined that said data is not located in the selected configuration server node, selecting, at the first configuration server node, a further configuration server node and returning to the step (d).

17. A node configuration setup method for a connection-oriented oriented network, wherein a configuration client node is responsive to a ready-to-accept message from one of a plurality of configuration server nodes for downloading client'"'"'s configuration data therefrom, comprising:

a) determining, at a first configuration server node in response to an initial configuration inquiry message from said client node, whether or not said data is located in the first configuration server node;

b) if it is determined that said data is located in the first configuration server node, transmitting said ready-to-accept message from the first configuration server node to the client node;

c) if it is determined that said data is not located in the first configuration server node, selecting, at the first configuration server node, a second configuration server node;

d) transmitting a direct-transfer request message from the first configuration server node to the selected configuration server node;

e) determining, at the selected configuration server node in response to the direct-transfer request message, whether or not said data is located in the selected configuration server node;

f) if it is determined that said data is located in the selected configuration server node, transmitting said ready-to-accept message from the selected configuration server node to the client node;

g) if it is determined that said data is not located in the selected configuration server node, selecting, at the selected configuration server node, a further configuration server node and transmitting a reply message from the previously selected configuration server node to the first configuration server node; and

h) transmitting, in response to the reply message, a direct-transfer request message from the first configuration server node to the configuration server node selected by the step (g), and returning to the step (e).