Method for joining a plurality of networks and seceding therefrom

Abstract: A method for joining and seceding from communications networks includes steps (a), (b) and (c). Step (a) is to register, at a first one of the communications networks (NW1 - NW5) indicated by first address information, second address information in first system definition information (1), the second address information registered in the first system definition information concerning the first one of the communications networks indicating a second one of the communications networks with which the first one of the communications networks requests to communicate. Step (b) is to register, at the first one of the communications networks, the second address information in second system definition information (2), the second address information registered in the second system definition information indicating that the first one of the communications networks is allowed to communicate with the second one of the communications networks. Step (c) is to assign, at the first one of the communications networks, a management number (3) to the first address information and the second address information so as to be operatively linked together, whereby the first one of the communications networks can communicate with the second one of the communications networks by using the second system definition information referred to by the management number.

Description: BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention generally relates to a communications system including a plurality of networks, and more particularly to a method for joining such networks and seceding therefrom. 2. Description of the Prior Art There is in present technology a communications system having a plurality of networks coupled to each other. Each communications network is allowed to communicate with one or a plurality of remote communications networks which are previously registered. If a communications network generates a request to communicate with (join) a remote communications network which has not been registered, a network system address indicating the above communications network is registered in the remote communications network, and a network system address indicating the remote communications network is registered in the communications network which has generated the above request. When a communications network has a request to secede from the above remote communications network, the network system address indicating the communications network having the above request is deleted from the remote communications network, and the network system address indicating the remote communications network is also deleted from the communications network having the above request. Conventionally, the registration and seceding processes are manually carried out in a state in which communications services provided by the communications networks being considered are interrupted. EP-A-0 474 427 discloses a method according to the preamble of claim 1. That is, each network is assigned a common network address and a second network address in order to exchange messages with another network. Each network is served by a LAN access module (LAM). At the time of forming a request message from an originating network, the associated LAM assigns the second address so that a potential recipient may identify the originating network, and subsequently assigns to the destination network a destination address, both addresses being stored in a routing table. Each LAM stores its own routing table in order to track addresses assigned and received. SUMMARY OF THE INVENTION It is an object of the present invention to provide a process for automatically joining a plurality of communications networks and seceding therefrom without interrupting communications services. The above object of the present invention is achieved by a method for joining and seceding from communications networks, comprising the step of: (a) registering, at a first network of the communication networks indicated by first address information, second address information in an own system definition information, said second address information registered in the own system definition information concerning said first network indicating a second network of the communications networks with which said first network requests to communicate; and characterized by the further steps of: (b) registering, at said first network, said second address information in remote system definition information of the first network, the second address information registered in the remote system definition of the first network indicating that said first network is allowed to communicate with the second network; and (c) assigning, at said first network, a management number to the first address information and the second address information so as to be operatively linked together, whereby said first network can communicate with said second network by using the remote system definition information of the first network referred to by the management number. Preferably, the above method comprises the step of (d) registering, at the second one of the communications networks indicated by the second address information, the first address information in a remote system definition information together with the management number, the first address information registered in the third system definition information indicating that the second one of the communications networks is allowed to communicate with the first one of the communications networks. Preferably, the above method comprises the steps of: (d) deleting the second address information from the first system definition information when the first one of the communications networks stops a communication with the second one of the communications networks; (e) deleting the second address information from the second system definition information when the first one of the communications networks stops the communication with the second one of the communications networks; and (f) canceling the management number when the first one of the communications networks stops said communication with the second one of the communications networks. Preferably, the above method comprises the step of: (e) deleting the second address information and the management number from the third system definition information when the first one of the communications networks stops a communication with the second one of the communications networks. BRIEF DESCRIPTION OF THE DRAWINGS Other objects, features and advantages of the present invention will become more apparent from the following detailed description when read in conjunction with the accompanying drawings, in which: Fig. 1 is a block diagram of a communication system having a plurality of communications networks according to an embodiment of the present invention; Fig. 2 is a diagram of a host's own system definition information and remote system definition information according to the embodiment of the present invention: Figs. 3A and 3B are diagrams of formats of a network system address according to the embodiment of the present invention; Fig. 4 is a flowchart of the operation of the embodiment of the present invention; Fig. 5 is a flowchart of the operation of the embodiment of the present invention; and Fig. 6 is a diagram showing how host devices join networks and secede therefrom. DESCRIPTION OF THE PREFERRED EMBODIMENTS Fig. 1 is a block diagram of a communications system having a plurality of communications networks NW1, NW2, NW3, NW4 and NW5. The communications network NW1 is connected to the communications networks NW2 through NW5 by means of communications media, such as cables. The communications networks NW1 through NW5 respectively form their own systems. The communications networks NW1 through NW5 have respective host devices HST1 through HST5, to which terminals TE1 through TE5 are respectively connected. In practice, a plurality of terminals are accommodated in the networks NW1 through NW5. Each of the communications networks manages its own system definition information 1 as shown in Fig. 2. The information shown in Fig. 2 is information managed by the host device HST1 of the communications network NW1. Each of the other host devices HST2 through HST5 of the communications networks NW2 through NW5 manages its own system definition information in the same way as the host device HST1. For example, the network system addresses registered in the own system definition information 1 managed by the host device HST1 indicate the host devices (networks) that the host device HST1 (network NW1) joins and requests to communicate with. More particularly, the system definition information 1 managed by the host device HST1 of the network NW1 includes an information item including a pointer, a management number 3 and a network system address (NSAP). The pointer is used to serially link items contained in the system definition information 1, as shown in Fig. 2. As shown in Fig. 2, the information items can be formed for the respective communications networks NW1 through NW5. In the case shown in Fig. 2, the information item shown on the leftmost side of Fig. 2 relates to the network NW1, and the information item next to the above item relates to the network NW2. The pointer of the information item relating to the network NW1 indicates the beginning of the information item relating to the network NW2. The management number 3 is serially assigned to the information items. In the case shown in Fig. 2, the information items of the networks NW1, NW2 and NW4 are assigned management numbers 0, 1 and 2, respectively. The network system addresses nsap1, nsap2, nsap3, nsap4, ..., nsapn (n is an integer equal to 5 in the communications system shown in Fig. 1) are assigned to the communications networks NW1 through NW5. Each of the host devices HST1 through HST5 of the communications networks NW1 through NW5 manages, using the above-mentioned management number, the network system addresses of other remote networks as remote system definition information 2 shown in Fig. 2. The information 2 shown in Fig. 2 is information managed by the host computer HST1 of the network NW1 and is related to the communications network NW2. The remote system definition information 2 managed by the host device HST1 includes a host address number of the network system address NSAP. In the case shown in Fig. 2, the network system address is nsap2, and the host address number is 1, which is the management number related to the communications network NW2 and managed by the host device HST1 of the network NW1. For example, the network addresses registered in the remote system definition information 2 and managed by the host device HST1 indicate the host devices (networks) that the host device HST (network NW1) is capable of communicating with. Fig. 3A shows a format of the network system address NSAP of each of the host devices HST1 of the networks NW1 through NW5. The network system address NSAP includes information indicating the network type and the network identification number, and node addresses. The network type is, for example, a LAN (Local Area Network) or a WAN (Wide Area Network). The network identification number indicates the corresponding communications network. The node addresses indicate the addresses of nodes connected to the communications network related to the host device managing the network system address NSAP shown in Fig. 3A. Fig. 3B shows the network system address NSAP according to the E. 164 format. As shown in Fig. 3B, the E. 164 format of the network system address NSAP includes: 45 country code subscriber number area ID end-system ID NSAP selector. The host device HST1 of the network NW1 stores the system definition information items of the other networks with which the network NW1 requests to communicate. A description will now be given, with reference to Figs. 4, 5 and 6, of a case where the host HST1 of the network NW1 generates a request to communicate with the host device ST2 of the network NW2 and the host device HST4 of the network NW4 when the host device HST1 is communicating with the terminal TE1. Referring to Fig. 4, the host device HST1 of the network NW1 communicates with terminal TE1 accommodated in the network NW1 in step S1. In step S2, the host device HST1 adds the network system address nsap2 of the network NW2 to the system definition information 1 managed by the host device HST1, as indicated by [1] in Fig. 6. Originally, the system definition information managed by the host device HST1 includes information concerning its own network NW1. In step S3, the host device HST1 creates system information concerning the remote network NW2, as indicated by [2] shown in Fig. 6, and the host device HST2 creates system information concerning the remote network NW1, as indicated by [3] shown in Fig. 6. The created system information concerning the network NW1 (host device HST1) is registered in the remote system definition information 2 managed by the host device HST2. In step S4, the host device HST1 activates the system definition information concerning the network NW2, and the host device HST2 activates the system definition information concerning the network NW1. Thereby, the host device HST1 becomes capable of communicating with the host device HST2, and the host device HST2 becomes capable of communicating with the host device HST1. That is, the host device HST1 has joined the network NW2. Similarly, in step S5, the host device HST1 adds the network system address nsap4 of the network NW4 to the system definition information 1 managed by the host device HST1, as indicated by [4] shown in Fig. 6. In step S6, the host device HST1 creates system information concerning the remote network NW4, as indicated by [5] shown in Fig. 6, and the host device HST4 creates system information concerning the remote network NW1, as indicated by [6] shown therein. The created system information concerning the remote network NW4 is registered in the remote system definition 2 managed by the host device HST1. The created system information concerning the network NW1 (host device HST1) is registered in the remote system definition information 2 managed by the host device HST4. In step S7, the host device HST1 activates the system definition information concerning the network NW4, and the host device HST4 activates the system definition information concerning the network NW1. Thereby, the host device HST1 becomes capable of communicating with the host device HST4, and the host device HST4 becomes capable of communicating with the host device HST1. That is, the host device HST1 has joined the network NW4, and the host device HST4 has joined the network NW1. Similarly, as indicated by [8] shown in Fig. 6, the system definition information concerning the host device HST2 is registered in the remote system definition information 2 managed by the host system HST4. Further, as indicated by [7] shown in Fig. 6, the system definition information concerning the host device HST4 is registered in the remote system definition information 2 managed by the host system HST2. In step S8, communications among the host devices HST1, HST2 and HST4 take place. In the state in which the host device HST1 of the network NW1 is communicating with the terminal TE1, the host devices HST1, HST2 and HST4 mutually create their own system definition information 1 and the remote system definition information 2 and activate the information 1 and information 2. Hence, it becomes possible for the host devices HST1, HST2 and HST4 to communicate with one another. Fig. 5 is a flowchart of a process for adding the network system address NSAP to the system definition information. The process can be manually or automatically performed. In step S11, an operator of the host device HST1 of the network NW1 inputs a command to the host device HST1 via a keyboard or the like, and inputs a desired network system address NSAP and a management number corresponding to the desired network system address NSAP. For example, the operator inputs the network system address nsap2. At this time, the management number may be automatically and assigned in response to the input of the network system address nsap2. In the case shown in Fig. 2, management number "1" is assigned to the network system address nsap2. In step S12, it is determined whether or not a network system address (NSAP) storage area corresponding to the network system address input in step S11 has been captured. In Fig. 2, such a network system address storage area is indicated by an oval. When the result of step S12 is YES, step S15 is processed. When the result of step S12 is NO, in step S13, a network system address storage area corresponding to the network system address input in step S11 is captured. Then, in step S14, the pointer address indicating the captured storage area is set in the network system address storage area to which the captured storage area should be chained, as shown in Fig. 2 In step S15, the network system address input in step S11 is stored in the network address storage area captured in step S13 in accordance with the management number. For example, the network system address nsap2 is stored in the storage area to which management number "3" is assigned. In step S16, the network system address NSAP is finally registered in the system definition information 1 managed by the host device HST1. In the above-mentioned manner, if the storage area corresponding to the network system address input in step S11 has not been registered, the above storage area is dynamically captured and registered in connection with the management number, so that entry of the host device HST1 is completed. As has been described previously, Fig. 6 shows how the own system definition information 1 and the remote system definition information 2 are set when communications among the networks NW1, NW2 and NW4 take place. Before the own system definition information 1 and the remote system definition information 2 are updated, the host devices HST1, HST2 and HOST4 have their own system definition information 1 as follows: HST1: nsap1 HST2: nsap2 HST4: nsap4. After the host devices HST1, HST2 and HST4 are mutually connected and communications can take place between these devices, the host device HST1 has its own system definition information as follows: HST1; nsap1, nsap2, nsap4. Further, the host device HST1 has the following remote system definition information 2: nsap2, address no. "1" regarding HST2 (NW2) nsap4, address no. "2" regarding HST4 (NW4). As has been described previously, the address number corresponds to the management number. That is, the address number "1" corresponds to the management number "1". The host device HST2 has its own system definition information 1 indicating only its own address nsap2, and the remote system definition information 2 indicating the remote networks (host devices) nsap1 and nsap4. By referring to the definition information 2, the host device HST2 can communicate with the host devices HST1 and HST4. Similarly, the host device HST4 manages its own system definition information 1 and the remote system definition information 2. As shown in Fig. 1 and Fig. 6, the own system definition information 1 and the remote system definition information 2 are registered so that the information 1 and the information 2 are linked by the management number. Hence, the networks NW1, NW2 and NW4 can communicate with one another. Further, Fig. 6 shows how to secede from the networks. In the seceding procedure, items of the remote system definition information 2 indicated by ovals are deleted from tat the host devices HST1, HST2 and HST4. Each of the host devices HST1 through HST5 includes a CPU, a memory, a communications controller, and an input/output device. Similarly, each of the terminals TE1 through TE5 has a CPU, a memory, a communications controller and an input/output device. It will be noted that the hardware configurations of the host devices and the terminals are known. It is possible for the terminal to perform the procedures shown in Figs. 4 through 6 instead of the host devices. The present invention is not limited to the specifically disclosed embodiments, and variations and modifications may be made without departing from the scope of the present invention.

Claims: A method for joining and seceding from communications networks, comprising the step of: (a) registering, at a first network of the communication networks (NW1-NWn) indicated by first address information, second address information in an own system definition information (1), said second address information registered in the own system definition information concerning said first network indicating a second network of the communications networks with which said first network requests to communicate; and characterised by the further steps of: (b) registering, at said first network, said second address information in remote system definition information (2) of the first network, the second address information registered in the remote system definition of the first network indicating that said first network is allowed to communicate with the second network; and (c) assigning, at said first network, a management number (3) to the first address information and the second address information so as to be operatively linked together, whereby said first network can communicate with said second network by using the remote system definition information of the first network referred to by the management number. The method as claimed in claim 1, further comprising: (d) registering, at the second network indicated by the second address information, the first address information in a remote system definition of the second network together with said management number, the first address information registered in the remote system definition information of the second network indicating that said second network is allowed to communicate with said first network. The method as claimed in claim 1, further comprising the step of: (d) deleting the second address information from the own system definition information when said first network stops a communication with the second network; (e) deleting the second address information from the remote system definition information of the first network when said first network stops said communication with the second network; and (f) cancelling the management number when said first network stops said communication with the second network. The method as claimed in claim 2, further comprising the step of: (e) deleting the second address information and the management number from the remote system definition information of the second network when said first network stops a communication with said second network. The method as claimed in claim 1, wherein said second address information contains information indicating a type of said second network. The method as claimed in claim 1, wherein: the step (a) comprises the step of forming a first storage area in which the own definition information is stored; and the step (b) comprises the step of forming a second storage area in which the remote definition information of the first network is stored; wherein said management number operatively links the first storage area and the second storage area.

Inventors: IDE AKIRA, IDE, AKIRA, Ide, Akira, c/o FUJITSU LIMITED, Patent Department
Applicants: FUJITSU LTD, FUJITSU LIMITED
Application year: 1993
Main classification: H04L12
IPC codes: H04L12, H04L29, G06F15, G06F13