JP5137200B2 - Hypertext transfer protocol network and data transfer method - Google Patents

Description

  The present invention relates to a technology that constitutes an Internet communication technology for performing data communication using a hypertext transfer protocol represented by WWW (World Wide Web). In particular, the Internet communication field belongs to the VPN communication field for securely accessing a VPN (Virtual Private Network) outside the company from an intranet closed within the company.

A conventional hibertext transfer protocol network includes a proxy device and a reverse proxy device as service relay devices. The proxy device and the reverse proxy device are positioned as a relay device using a hypertext transfer protocol between a user and a web server terminal, and are mainly realized by using programs called apache and squid.
The proxy device does not have a destination uniform resource location specifier conversion function, and simply transfers hypertext transfer protocol data according to the destination uniform resource location specifier.
On the other hand, the reverse proxy device has a destination unified resource location specifier conversion function. This conversion function not only has the effect of concealing the unified resource location specifier and the Internet protocol address of the server terminal from the client terminal, but also has the effect of load distribution among a plurality of server terminals. (See Non-Patent Document 1 and Patent Document 1 below)
For example, when performing load balancing, the user describes the identifier of the reverse proxy device in the host identifier of the destination uniform resource location specifier, and transmits data to the reverse proxy device. The reverse proxy device converts the host identifier addressed to itself into the host identifier of the actual web server terminal, and transfers the data to the web server terminal. At this time, the load is distributed among the plurality of web server terminals by transferring the data by converting the data to a different host identifier of the web server terminal for each data relay.

As prior art documents related to the invention of the present application, there are the following.
Performance Evaluation of a Load Balancing Control Algorithm and Application Areas Performance Evaluation of a Load Balancing Routing Algorithm for a Cache Server Array Hiroyoshi Tonami Kazunori Kumagai Shinya Nogami Takeo Abe Technical report of IEICE. NS, Network System IEICF technical report Vo1.101, No.8 (20010412) pp.15-20, NS2001-3 JP 2003-50756 A

In a conventional network, a plurality of transfer destination web server terminals can be installed by using a reverse proxy device. However, even if an individual web server terminal is installed for each user, it is not possible to uniquely designate and transfer the destination web server terminal for each transmission user in a single reverse proxy device.
For example, as a configuration example of the network, the first network is positioned as a corporate intranet, a user is allocated, the second network is positioned as an application service provider network, and a web server terminal is allocated. And the second network are connected to each other only through the reverse proxy device.
In this configuration, in the first network, only the host identifier and the address in the unified resource location specifier addressed to the reverse proxy device are covered regardless of the addition of the web server terminal in the second network. good.
On the other hand, in the second network, it is possible to add web server terminals without affecting the second network.
However, in a single reverse proxy device, since it was not possible to uniquely specify and transfer the destination web server terminal for each sending user, a service is provided by preparing an individual web server terminal for each user in the second network. The offer could not be made.
The present invention has been made to solve the above-described problems of the prior art, and an object of the present invention is to provide a hypertext transfer protocol network and a data transfer method that can uniquely specify a destination web server terminal for each transmission user. It is to provide.
The above and other objects and novel features of the present invention will become apparent from the description of this specification and the accompanying drawings.

Of the inventions disclosed in this application, the outline of typical ones will be briefly described as follows.
The present invention includes a first subnetwork, a second subnetwork, and a service relay device arranged at a boundary between the first subnetwork and the second subnetwork, and The sub-network accommodates a plurality of client terminals, the second sub-network accommodates a plurality of server terminals, and is a data transfer method in a hypertext transfer protocol network for transferring hypertext transfer protocol data, The source client terminal describes in the host identifier of the destination uniform resource location specifier the identifier of the service relay device viewed from the first subnetwork and the identifier of the first subnetwork, and the destination uniform resource location The destination server as seen from the first sub-network in the directory identifier of the specifier Send the youngest identifier, and the first of the second sub-network as viewed from the sub-network identifier, describes the directory identifier within the destination server terminal, a hypertext transfer protocol data, the service The relay apparatus has a destination server terminal identifier as seen from the first subnetwork, a set of identifiers of the second subnetwork as seen from the first subnetwork, and a perspective as seen from the second subnetwork. A conversion table that associates an identifier of a destination server terminal with a set of identifiers of the second subnetwork, and the service relay device refers to the conversion table and receives the hyper received from the first subnetwork. It is described in the directory identifier of the destination Uniform resource locators text transfer protocol data The destination server terminal seen from the second subnetwork from the identifier of the destination server terminal seen from the first subnetwork and the identifier of the second subnetwork seen from the first subnetwork. description and identifier to said second generate an identifier of the sub-network, host identifier, the identifier of the destination server terminal as viewed from the to the generated second sub-network, and an identifier of the second sub-network Then , the directory identifier in the destination server terminal is described in the directory identifier, and the hypertext transfer protocol data obtained by converting the destination unified resource location specifier is transmitted into the second sub-network. .

In the present invention, the source client terminal, the directory identifier of the destination Uniform Resource locators, describes the identifier of the source client terminal as viewed from the first sub-network, Hypertext Transfer Protocol The service relay device transmits data for each set of the identifier of the transmission source client terminal viewed from the first subnetwork and the identifier of the second subnetwork viewed from the first subnetwork. , Having an authentication table describing “transfer” or “discard” as the data processing contents, and the service relay device has the destination uniform resource location specifier of the hypertext transfer protocol data received from the first subnetwork . before viewed from the first sub-network described in the directory identifier An identifier of the source client terminal, the first based on the identifier of the second sub-network as viewed from the sub-network, by referring to the authentication table, the not destined server terminal Gasa-bis provide target client terminal However , it is characterized in that the data transmitted to the server terminal is specified and is not transferred.
In the present invention, the first sub-network and the second sub-network have different unified resource location specifiers and Internet protocol address systems, respectively.
In the present invention, the service relay device has two subnetwork interfaces independent of each other.
The present invention is also a hypertext transfer protocol network for executing the data transfer method.

The effects obtained by the representative ones of the inventions disclosed in the present application will be briefly described as follows.
According to the present invention, it is possible to uniquely specify a destination web server terminal for each transmission user.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
In all the drawings for explaining the embodiments, parts having the same functions are given the same reference numerals, and repeated explanation thereof is omitted.
FIG. 1 is a diagram showing a schematic configuration of a hypertext transfer protocol network according to an embodiment of the present invention.
The hypertext transfer protocol network 100 according to this embodiment includes a common subnetwork 10, an individual subnetwork # 1 (20), and an individual subnetwork # 2 (30).
The common subnetwork 10 accommodates client terminals # 1 (11) and client terminals # 2 (12). In addition, the common subnetwork 10 includes a proxy terminal # 1 (13) as a relay device.
The individual subnetwork # 1 (20) accommodates the server terminal # 1 (21) and the server terminal # 2 (22). The individual subnetwork # 1 (20) has a proxy terminal # 2 (23) as a relay device.
The individual subnetwork # 2 (30) accommodates a server terminal # 3 (31) and a server terminal # 4 (32). The individual subnetwork # 2 (30) has a proxy terminal # 3 (33) as a relay device.
The common subnetwork 10, the individual subnetwork # 1 (20), and the individual subnetwork # 2 (30) are connected via the service relay device 40.
The service relay device 40 accommodates the common subnetwork 10 at the subnetwork interface # 1 (41), the individual subnetwork # 1 (20) at the subnetwork interface # 2 (42), and the subnetwork interface # 3 ( 43) accommodates the individual subnetwork # 2 (30).

FIG. 2 is a diagram showing a name system viewed from the common subnetwork 10 shown in FIG.
The common subnetwork 10 has “subnet0”, the individual subnetwork # 1 (20) has “subnet1”, the client terminal # 1 (11) has “client1”, and the client terminal # 2 (12) has “Client2”, server server # 1 (21) has “server1”, server terminal # 2 (22) has “server2”, server terminal # 3 (31) has “server3”, server terminal # 4 (32) is “server4”, proxy terminal # 1 (13) is “proxy1”, proxy terminal # 2 (23) is “proxy2”, and proxy terminal # 3 (33) is “proxy3”. The service relay device 40 is given a name “service1”.
FIG. 3 is a diagram showing a name system viewed from the individual subnetwork # 1 (20) shown in FIG.
The common subnetwork 10 has subnet 0, the individual subnetwork # 1 (20) has “net1”, the client terminal # 1 (11) has “client1”, and the client terminal # 2 (12) has “client2”. "Server 5" for server terminal # 1 (21), "server 6" for server terminal # 2 (22), "proxy0" for proxy terminal # 2 (23), and service relay device 40 , “Service0” is given a name.
Here, it should be noted that the name system seen from the common subnetwork 10 and the name system seen from the individual subnetwork # 1 (20) are different.

FIG. 4 is a diagram showing a destination uniform resource position specifier designated by the client terminal.
The destination uniform resource location specifier is composed of an access means identifier 50, a host identifier 51, and a directory identifier 52.
Here, the host identifier 51 includes the identifier 53A of the service relay device 40 viewed from the common subnetwork 10 to which the transmission source client terminal belongs, and the transmission source client terminal viewed from the common subnetwork 10 to which the transmission source client terminal belongs. It consists of the subnetwork identifier 53B to which it belongs.
The directory identifier 52 includes an identifier 53C of the transmission source client terminal viewed from the common subnetwork 10 to which the transmission source client terminal belongs, an identifier 53D of the destination server terminal viewed from the common subnetwork 10 to which the transmission source client terminal belongs, A subnetwork identifier 53E to which the destination server terminal belongs as viewed from the common subnetwork 10 to which the transmission source client terminal belongs, and a directory identifier 53F in the destination server terminal.
In this example, “http” is used as the access means identifier 50, and “service1” is used as the identifier 53A of the service relay device 40 viewed from the common subnetwork 10 to which the transmission source client terminal belongs. “Subnet0” as the subnetwork identifier 53B to which the transmission source client terminal belongs as seen from the network 10, and “client1” as the transmission source client terminal identifier 53C from the common subnetwork 10 to which the transmission source client terminal belongs. As an identifier 53D of the destination server terminal viewed from the common subnetwork 10 to which the transmission source client terminal belongs, “server1” is set, and the destination server terminal viewed from the common subnetwork 10 to which the transmission source client terminal belongs. As an identifier 53E belonging subnetwork, "subnet1", as Tirekutori identifier 53F in the destination server terminal, "folder1 / contents1" is designated

FIG. 5 is a diagram illustrating a conversion example of the destination unified resource position specifier in the service relay device 40.
In FIG. 5, the destination uniform resource position specifier before conversion shown in the upper part and the destination uniform resource position specifier after conversion shown in the lower part are configured.
In the example shown in FIG. 5, “http” is designated as the access means identifier 50 in the destination uniform resource position specifier before conversion.
The host identifier 51 is “service1” as the identifier 53A of the service relay device 40 viewed from the common subnetwork 10 to which the transmission source client terminal belongs, and the transmission source viewed from the common subnetwork 10 to which the transmission source client terminal belongs. “Subnet0” is designated as the identifier 53B of the subnetwork to which the client terminal belongs.
Further, the directory identifier 52 is “client1” as the source client terminal identifier 53C seen from the common subnetwork 10 to which the source client terminal belongs, and the destination server seen from the common subnetwork 10 to which the source client terminal belongs. “Server1” as the terminal identifier 53D, “subnet1” as the subnetwork identifier 53E to which the destination server terminal belongs as seen from the common subnetwork 10 to which the transmission source client terminal belongs, and the directory identifier 53F in the destination server terminal “Folder1 / contents1” is designated as “Access” and “http” is designated as the access means identifier 50 in the destination unified resource location specifier after conversion.
The host identifier 51 is “server5” as the identifier 53G of the destination server terminal viewed from the individual subnetwork # 1 (20) to which the destination server terminal belongs, and the individual subnetwork # 1 (20) to which the destination server terminal belongs. “Net1” is designated as the identifier 53H of the individual subnetwork # 1 (20) to which the destination server terminal belongs as seen from FIG.
Furthermore, the directory identifier 52 is designated as “folder1 / contents1” as the directory identifier 53F in the destination server terminal.

FIG. 6 is a diagram showing a conversion table in the service relay device 40 shown in FIG.
In the conversion table shown in FIG. 6, the identifier 53D of the destination server terminal seen from the common subnetwork 10 to which the transmission source client terminal belongs and the destination seen from the common subnetwork 10 to which the transmission source client terminal belongs. From the set of subnetwork identifiers 53E to which the server terminal belongs, the destination server terminal identifier 53G as seen from the subnetwork to which the destination server terminal belongs after conversion, and the destination server as seen from the subnetwork to which the destination server terminal belongs A set of identifiers 53H of the subnetwork to which the terminal belongs is derived.
For example, “server5.net1” after conversion is derived from “server1.subnet1” before conversion, and “server6.net1” after conversion is derived from “server2.subnet1” before conversion. Here, “.” Is a symbol indicating a boundary point between identifiers.

FIG. 7 is a diagram showing an authentication table in the service relay device 40 shown in FIG.
In the authentication table shown in FIG. 7 , the identifier 53C of the transmission source client terminal viewed from the common subnetwork 10 to which the transmission source client terminal belongs and the destination subnetwork viewed from the common subnetwork 10 to which the transmission source client terminal belongs. From the set of identifiers 53D, “transfer” or “discard” is derived as the data processing content.
For example, “transfer” is derived from the set of “client1” and “subnet1”, and “discard” is derived from the set of “client2” and “subnet2”.

[Operation example]
Hereinafter, an operation example in the above-described configuration will be described.
Here, an example in which the client terminal # 1 (11) accesses “folder1 / contents1” of the server terminal # 1 (21) in the hypertext transfer protocol layer in FIG. 1 will be described.
Client terminal # 1 (11) transmits the hypertext transfer protocol data with the destination uniform resource location specifier “http: //service1.subnet0/client1/server1.subnet1/folder1/contents1” shown in FIG. To do.
At this time, if proxy terminal # 1 (13) (proxy1) is assigned as the proxy device, the transmission data reaches proxy terminal # 1 (13).
The proxy terminal # 1 (13) refers to the destination uniform resource position specifier of the received hypertext transfer protocol data and specifies the host identifier “service1” of the service relay device 40 as the destination host identifier. Transfer to service relay device 40.
The service relay device 40 basically operates in the same manner as the reverse proxy device. However, in the following description, an operation different from that of the reverse proxy device is performed.
When the service relay device 40 receives the hypertext transfer protocol data at the sub-network interface # 1 (41), the service relay device 40, based on the authentication table shown in FIG. 7, sets the destination uniform resource location specifier “http: //service1.subnet0”. /client1/server1.subnet1/folder1/contents1 ”,“ client1 ”that is the identifier 53C of the source client terminal viewed from the common subnetwork 10 to which the source client terminal belongs, and the common sub to which the source client terminal belongs. “Transfer” as data processing content is derived from “subnet1” which is the identifier 53E of the subnetwork to which the destination server terminal belongs as seen from the network 10.
If the identifier 53C of the source client terminal viewed from the common subnetwork 10 to which the source client terminal belongs is “client2”, the identifier 53E of the destination subnetwork viewed from the common subnetwork 10 to which the source client terminal belongs is In the case of “subnet 2”, “discard” is guided as the data processing content, so that the corresponding data is discarded and the processing ends here.

Here, since “transfer” is derived as the data processing content, the transfer processing of the corresponding data is performed.
Specifically, referring to the conversion table shown in FIG. 6, “server1” that is the identifier 53D of the destination server terminal viewed from the common subnetwork 10 to which the transmission source client terminal belongs, and the common to which the transmission source client terminal belongs. From the set of “subnet1”, which is the subnetwork identifier 53E to which the destination server terminal belongs as seen from the subnetwork 10, is the identifier 53G of the destination server terminal seen from the subnetwork to which the destination server terminal belongs after conversion. server5 ”and a group“ net1 ”that is the identifier 53H of the subnetwork to which the destination server terminal belongs as viewed from the subnetwork to which the destination server terminal belongs.
From this result, as shown in FIG. 5, the destination uniform resource location specifier is changed from “http: //service1.subnet0/client1/server1.subnet1/folder1/contents1” to “http: //server5.net1/folder1”. / contents1 ".
Thereafter, the hypertext transfer protocol data to which the destination uniform resource location specifier after conversion is added is transmitted from the subnetwork interface # 2 (42) connected to “Subnet1” or “net1”.
At this time, if the proxy terminal # 2 (23) (proxy0) is designated as the proxy device, the corresponding data is transferred via the proxy terminal # 2 (23).
Eventually, the corresponding data is transferred to the server terminal # 1 (21) in the individual subnetwork # 1 (20) according to the host identifier “server5” of the destination unified resource location specifier after conversion.
The server terminal # 1 (21) extracts the corresponding data by referring to the directory identifier “folder1 / contents1” of the destination unified resource location specifier and returns it.
Return data from the server terminal # 1 (21) to the client terminal # 1 (11) is transferred in a conventional sequence by the service relay device 40 operating in the same manner as the reverse proxy device.
As a result, the client terminal # 1 (11) can access the “folder1 / contents1” of the server terminal # 1 (21) in the hypertext transfer protocol layer.

As described above, according to the present embodiment, after the two sub-networks having different unified resource location specifiers and Internet protocol address systems are interconnected by the service relay device 40, the client terminal In the uniform resource location specifier, describe the identifier of the service relay device, the data that the destination server terminal can identify, the data that the source client terminal can identify, and the data that can identify the directory in the destination server terminal, Hypertext transfer protocol data can be transmitted, and the network can also deliver the data to the destination server terminal via the service relay device.
In addition, when the destination server terminal transmits data from a client terminal that is not a service provision target to the corresponding server terminal, the corresponding data can not be transferred.
As mentioned above, the invention made by the present inventor has been specifically described based on the above embodiments. However, the present invention is not limited to the above embodiments, and various modifications can be made without departing from the scope of the invention. Of course.

It is a figure which shows schematic structure of the hypertext transfer protocol network of the Example of this invention. It is a figure which shows the name system seen from the common subnetwork shown in FIG. It is a figure which shows the name system seen from separate subnetwork # 1 shown in FIG. It is a figure which shows the destination uniform resource position designator which the client terminal shown in FIG. 1 designates. It is a figure which shows the conversion example of the destination uniform resource position designator in the service relay apparatus shown in FIG. It is a figure which shows the conversion table in the service relay apparatus shown in FIG. It is a figure which shows the authentication table in the service relay apparatus shown in FIG.

Explanation of symbols

10 Common subnetwork # 1
11 Client terminal # 1
12 Client terminal # 2
13 Proxy terminal # 1
20 Individual subnetwork # 1
21 Server terminal # 1
22 Server terminal # 2
23 Proxy terminal # 2
30 Individual subnetwork # 2
31 Server terminal # 3
32 Server terminal # 4
33 Proxy terminal # 3
40 Service relay device 41 Subnetwork interface # 1
42 Subnetwork interface # 2
43 Subnetwork interface # 3
100 Hypertext Transfer Protocol Network

Claims (8)

A first subnetwork;
A second subnetwork;
A service relay device disposed at a boundary between the first subnetwork and the second subnetwork;
The first subnetwork accommodates a plurality of client terminals,
The second subnetwork accommodates a plurality of server terminals,
A data transfer method in a hypertext transfer protocol network for transferring hypertext transfer protocol data,
The source client terminal describes in the host identifier of the destination uniform resource location specifier the identifier of the service relay device viewed from the first subnetwork and the identifier of the first subnetwork, and the destination uniform resource location The directory identifier of the specifier includes an identifier of the destination server terminal viewed from the first subnetwork, an identifier of the second subnetwork viewed from the first subnetwork, and a directory in the destination server terminal Describe the identifier , send hypertext transfer protocol data,
The service relay device includes a set of an identifier of a destination server terminal viewed from the first subnetwork, a set of identifiers of the second subnetwork viewed from the first subnetwork, and the second subnetwork. A conversion table that associates the identifier of the viewed destination server terminal with the set of identifiers of the second subnetwork;
The service relay device refers to the conversion table and is described in the directory identifier of the destination uniform resource locator of the hypertext transfer protocol data received from the first subnetwork. An identifier of the destination server terminal viewed from the first subnetwork, an identifier of the destination server terminal viewed from the second subnetwork, an identifier of the destination server terminal viewed from the second subnetwork, and the second generating a sub-network identifier, a host identifier, the identifier of the destination server terminal as viewed from the to the generated second sub-network, describes the identifier of the second sub-network, the directory identifier, wherein It describes the directory identifier in the destination server terminal, varying the destination uniform resource locators Data transfer method and transmits the the Hypertext Transfer Protocol data into the second subnetwork. The source client terminal, the directory identifier of the destination Uniform Resource locators, the first describes an identifier of the source client terminal as viewed from the sub-network, transmits a hypertext transfer protocol data,
The service relay apparatus performs data processing contents for each set of the identifier of the transmission source client terminal viewed from the first subnetwork and the identifier of the second subnetwork viewed from the first subnetwork. Has an authentication table that describes "transfer" or "discard"
The service relay device has the source client terminal as viewed from the first subnetwork described in the directory identifier of the destination uniform resource locator of the hypertext transfer protocol data received from the first subnetwork . an identifier, based on the identifier of the said viewed from the first subnetwork second subnetwork, by referring to the authentication table, the client terminal that the not destined server terminal Gasa-bis providing object, the server terminal 2. The data transfer method according to claim 1, wherein the data transmitted toward is identified and is not transferred. 3. The data transfer method according to claim 1, wherein the first subnetwork and the second subnetwork have different unified resource location specifiers and Internet protocol address systems, respectively. .   The data transfer method according to claim 3, wherein the service relay device has two subnetwork interfaces independent of each other. A first subnetwork;
A second subnetwork;
A service relay device disposed at a boundary between the first subnetwork and the second subnetwork;
The first subnetwork accommodates a plurality of client terminals,
The second subnetwork accommodates a plurality of server terminals,
A hypertext transfer protocol network for transferring hypertext transfer protocol data,
The client terminal describes, in the host identifier of the destination uniform resource location specifier, the identifier of the service relay device viewed from the first subnetwork and the identifier of the first subnetwork, and specifies the destination uniform resource location designation The child directory identifier includes an identifier of the destination server terminal viewed from the first subnetwork, an identifier of the second subnetwork viewed from the first subnetwork, and a directory identifier in the destination server terminal And has means for transmitting hypertext transfer protocol data,
The service relay device includes a set of an identifier of a destination server terminal viewed from the first subnetwork, a set of identifiers of the second subnetwork viewed from the first subnetwork, and the second subnetwork. A conversion table associating the identifier of the viewed destination server terminal with the set of identifiers of the second subnetwork;
The destination server terminal as seen from the first subnetwork described in the directory identifier of the destination uniform resource locator of the hypertext transfer protocol data received from the first subnetwork with reference to the conversion table , The identifier of the second subnetwork viewed from the first subnetwork, the identifier of the destination server terminal viewed from the second subnetwork, and the identifier of the second subnetwork Means for generating;
In the host identifier, the identifier of the destination server terminal viewed from the generated second subnetwork and the identifier of the second subnetwork are described . In the directory identifier, the directory identifier in the destination server terminal is described. A hypertext transfer protocol network comprising: means for writing and transmitting hypertext transfer protocol data into which the destination uniform resource location specifier is converted into the second sub-network. The means of the client terminal describes the identifier of the source client terminal viewed from the first subnetwork in the directory identifier of the destination unified resource locator , transmits hypertext transfer protocol data,
The service relay apparatus performs data processing contents for each set of the identifier of the transmission source client terminal viewed from the first subnetwork and the identifier of the second subnetwork viewed from the first subnetwork. An authentication table describing "forwarding" or "discarding";
The identifier of the source client terminal viewed from the first subnetwork described in the directory identifier of the destination uniform resource locator of the hypertext transfer protocol data received from the first subnetwork , and the first based of the identifier of the second sub-network as viewed from the sub-network, by referring to the authentication table, the client terminal where the destination server terminal is not the object of the service provided, and transmitted to the server terminal data The hypertext transfer protocol network according to claim 5, further comprising: means for specifying and not transferring the hypertext transfer protocol network.   7. The hypertext transfer according to claim 5, wherein the first subnetwork and the second subnetwork have different unified resource locator and Internet protocol address systems, respectively. Protocol network.   The hypertext transfer protocol network according to claim 7, wherein the service relay apparatus has two subnetwork interfaces independent of each other.

Images