JPS61136336A - Other system end node information obtaining system in multi-network system - Google Patents

Abstract

PURPOSE:To manage easily the constitution of a network by defining only an end node of the own system and holding it in a host, in each local network, respectively, and obtaining end node information of the other system from the host of each local network. CONSTITUTION:In case when a communication request has been generated in an end node 17 of a local network 2 from an end node 15 of a local network 1, a network managing part 5 executes an inquiry request to a communication processing part 15, and the processing part 13 transmits an inquiry message to each local network. When a communication processing part 14 receives an inquiry message from a host 3, a host 4 analyzes it, and delivers a confirmation request and an end node name of a communication request origin to an end node inquiry/response part 24 of the other system. Subsequently, the inquiry/ response part 24 derives confirmation with regard to an end node of an existence confirmation request, to an end node managing part 20 of the own system, and the managing part 20 retrieves an end node information file of the own system and returns its result.

Description

[Detailed Description of the Invention] [Field of Industrial Application] The present invention relates to a computer network system, and particularly relates to a method for acquiring configuration information of end nodes between networks in a multi-network system that combines a plurality of computer networks. .

[Conventional technology]

In a so-called multi-network system, where multiple computer networks (hereinafter referred to as local networks) each existing locally are further network-connected to form one global network, communication between end nodes of different local networks is difficult. To enable this, hosts in each local network need to know administrative information about end nodes (terminals) in other local networks.

Each local network host contains management information for end nodes in its own local network as well as management information for end nodes in other local networks, and uses this information to communicate between networks.

FIG. 2 shows, by way of example, a network communication mechanism for hosts within a local network. In the figure, 1 and 2 are local networks, 3.4 is a host,
5.6 is the network management section, 7.8 is the network information file, 9.10 is the end node management section, 11.1
2 is an end node information file, 13.14 is a communication processing unit, 15.16 is an end node under host 3, and 17° 18 (represents an end node under host 4).

The functions of host 3 and host 4 are almost the same.

Taking the host 3 as an example, the network management unit 5:
Management of network information file 7 1 communication processing unit 13
provides the network information necessary for communication.

The network information file 7 holds information such as connections and communication paths between all local networks in the multi-network system. Also, the end node management section 9
For example, it manages the end node information file 11 and provides end node information to the 1 communication processing unit 13. The end node information file 11 holds information such as end node names and device addresses regarding all end nodes in the own local network and other local networks.

Note that the end node name is uniquely defined for the entire system, but the device address is uniquely defined within the local network.

For example, end node 15 of local network 1
requests the host 3 to communicate with the end node 17 of the local network 2.

The end node name of the end node 17 is notified from the end node 15 to the host 3. Communication processing unit 13 of host 3
The network management unit 5 has one communication partner end node 1.
The information necessary to establish a session, such as the device address and host name of No. 7 and the communication path thereto, is inquired.

The network management unit 5 further includes an end node management unit 9
Please contact us. The end node management unit 9 determines the device address, host name, etc. of the end node 17 based on the end node information in the end node information file 11, and notifies the network management unit 5 of the information. Network management section 5
refers to the network information file and selects the communication path to host 4 on local network 2 based on the host name.

The information is returned to the communication processing unit 13 along with the device address of the end node 17.

The communication processing unit 13 sets up a communication path to the host 4 based on the information obtained from the network management unit 5, and communicates the device address of the end node 17 to the host 4 of the local network 2.

The communication processing unit 14 of the host 4 selects the end node 17 based on the received device address, and establishes a connection, that is, a session, with the end node 15 of the local network 1 .

In this way, end node-to-end node communication is enabled between any local networks.

[Problem that the invention seeks to solve]

In traditional multi-network systems, each local network host must define and maintain information about all end nodes in the system. Therefore, when a configuration change is made in one local network, such as adding or deleting an end node, hosts on all local networks must review the end node definition and update the end node information accordingly. Ta.

[Means for solving problems]

In order to solve the above problems, the present invention allows the host I of each local network 7 to hold only the end node information of its own local network.

Information regarding end nodes of other local networks is obtained from others when necessary.

The configuration for this is that in a multi-network system that combines multiple local networks, each including a host and an end node, each local network defines only its own end nodes, and the end node information is stored in the host. The end node information of other systems is acquired from the host of each local network].

〔Example〕

The details of the present invention will be explained below based on two examples.

FIG. 1 is a configuration diagram of a system according to an embodiment of the present invention,
This is shown as an improved version of the conventional system shown in FIG. In the figure, 1.2 is the local network, 3,
4 is the host, 5.6 is the network management section, 7.8 is the network information file, 13.14 is the communication processing section, 1
5.16 is an end node under host 3, 17.18 is an end node under host 4, 19.20 is the end node management section of the own system, 21.22 is the end node information file of the own system, and 23.24 is the other system End node information inquiry/
This is the response section.

In the system of this embodiment, the host in each local network manages only the end node information of its own local network, and the end node information of other local networks is required.

In other words, whenever there is a communication request from an end node in the own system to an end node in another system, an inquiry is made to all other local networks to confirm the existence of the end node name, and the corresponding local network is Control is performed to obtain end node information from the host.

Therefore, the own end node information files 21 and 22 hold only information such as end node names and device addresses regarding end nodes of the own local network, and are managed by the own end node management units 19 and 20, respectively.

The other-system end node information inquiry/response units 23 and 24 perform end-node information inquiry processing to other-system local networks and response processing to end-node information inquiries from other-system local networks.

For example, end node 15 of local network 1
Therefore, when a communication request is made to the end node 17 of the local network 2, the communication processing unit 13 passes the end node name of the communication partner received from the end node 15 to the network management unit 5, and sends the device address of the end node. etc. and information necessary for controlling the communication path.

The network management unit 5 includes the own end node management unit 19
Pass the end node name to the own end node management section 19.
searches the self-system end node information file 21 for the end node name.

If the corresponding end node name is detected, the end node information such as the device address is sent to the network management section 5. But in this example.

Because it fails to detect the corresponding end node name.

The own end node management unit 19 is the network management unit 5
Please reply to that effect.

Therefore, the network management unit 5 recognizes that the end node of one communication partner is not of its own system.

Next, refer to the network information file 7 to obtain connection information with other local networks.

An inquiry request is made to the communication processing unit 13 to confirm the existence of the end node name in each other local network.

The communication processing unit 13 thereby sends an inquiry message containing the end node name of the communication partner 9 and the end node name of the communication requesting end node 15 to each local network.

Wait for the answer.

When the communication processing unit 14 of each host in each other local network, for example, the host 4 of the local network 2, receives an inquiry message from the host 3, it analyzes the message and sends it to the other end node inquiry/response unit 24. , the name of the end node for which the existence confirmation request was made and the name of the end node that made the communication request for information identification are added and passed.

The other system end node information inquiry/response unit 24 requests the own system end node management unit 20 to confirm the name of the end node for which the presence confirmation request was made.

The own end node management unit 20 searches the own end node information file 22 and returns the results. If a corresponding end node of the own system cannot be detected, a response message of "not existing" is sent from the other system end node information inquiry/response section 24 to the host 3 via the communication processing section 14. However, in this example, the self-system end node management unit 20 is.

It is confirmed that the corresponding end node exists in the own system, and the other system end node information inquiry/response unit 24
sends a reply message to the host 3 via the communication processing unit 14, which includes the name of the communication request source end node for information identification in the end node information of the end node name whose existence has been confirmed.

The communication processing unit 13 of the host 3 analyzes each received reply message and passes it along with the sender host name 3 to the other system end node information inquiry/response unit 23.

The other system end node information inquiry/response section 23 is.

The end node information of the target end node name is acquired from the reply message from the host 4 whose existence has been confirmed, and the network management unit 5 acquires the end node information of the target end node name from the reply message from the host 4 whose existence has been confirmed.
pass it on to

The network management section 5 extracts information required for communication with the host 4 from the network information file 7 and passes it to the communication processing section 13 together with end node information. As a result, the 1 communication processing unit 13 executes a procedure to establish a session between the end node 15 and the end node 17, and performs communication processing after the session is established.

In this way, each local network host can
In the case of a communication request from an end node of the own system to an end node of an arbitrary other system, the own system does not have the end node information of the other system (in other words, the end node information cannot be easily retrieved from the corresponding host of the other system). can be obtained.

In the example system described above, each local network defines and holds only connection information between networks and information on its own end nodes, and end node information on other systems is determined when one communication request occurs. is obtained from other systems. but.

When starting up each local network, as an initialization process after establishing a session, the local networks mutually exchange information on all end nodes that each local network has opened to other systems, and retain it during network operation. It is also possible to

FIG. 3 is a conceptual diagram of one embodiment of such a system. In the figure, 25, 26, and 27 represent local networks A, B, and C, respectively.

Also, 28.29.30 is the session management function, 31°32
．． 33 is own system end node information, 34. 35°3
6 represents other system end node information.

Each local network A, B, and C defines only its own end node information 31, 32.33, and when starting up the system, the session management function 28.29.30'
After establishing a session to enable communication with other local networks, it exchanges end node information of its own system and other systems with each host, and transmits end node information of its own system. At the same time as sending out to other systems, end node information from other systems is taken in and held as other system end node information 34, 35, 36 during the operation period.

As a result, from now on, the same operation as in the conventional system shown in Figure 2 becomes possible, and a communication request from an end node of the own system to an end node of another system will be sent to the end node of the other system that was first received. By referring to the information, it is possible to immediately execute the procedure for establishing a session with the other end node.

In addition, as a modification of the method that eliminates the need to define end node names in each network, each network defines communication paths and host names between hosts, and discloses the host names and services available on that host to users. It is also possible to have the user specify the host name and service name.

For example, when a user (end node) a of a certain host A receives service b of a host B.

A connection request, that is, LOGON HO3T B-b, is issued to host A by specifying the host name (B) and service name (b).

Host) A analyzes the above join request, forwards the request to host B, and host B.

It accepts a connection request from host A and establishes a session between user (end node) a of host A and its own service b.

〔Effect of the invention〕

As described above, according to the present invention, each local network in a multi-network system only needs to define its own end nodes, and even if the end node configuration changes in one local network, Since there is no need to review the definitions in the local network, network configuration management becomes easier and the workload of the system administrator can be significantly reduced.

[Brief explanation of the drawing]

FIG. 1 is a configuration diagram of a system according to an embodiment of the present invention. FIG. 2 is a block diagram of a conventional system, and FIG. 3 is a block diagram of another embodiment of the system of the present invention. In the figure, 1 and 2 are local networks, 3 and 4 are hosts, 5.6 is a network management section, 7.8 is a network information file, 13.14 is a communication processing section, 15, 16.
17.18 is the end node. Reference numeral 19.20 indicates a self-system end node management section, 21.22 a self-system end node information file, and 23.24 an other-system end node information inquiry/response section.

Claims (3)

[Claims] (1) In a multi-network system that combines multiple local networks, each including a host and an end node, each local network defines only its own end nodes, stores the end node information in the host, and A system for obtaining end node information of other systems, characterized in that end node information of each system is obtained from hosts in each local network. (2) In the above paragraph 1, when a host of each local network receives a communication request from an end node of its own system to an end node of another system, the host of each local network inputs the end node name of the end node of the other system. It is sent to each host in the other system to inquire about its existence, each host in the other system checks the received end node name with its own end node information, and the host in the other system that has the corresponding end node information receives that end node information. A method for obtaining information on end nodes of other systems, which is characterized by responding to the host that is the source of the inquiry. (3) In paragraph 1 above, when a host in each local network establishes a session with a host in another system at the time of system startup, each host in the local network transfers its own end node information to the host in the other system. A method for acquiring end node information from other systems, which is characterized by transferring and retaining information from other end nodes.