JP2014222455A - Communication system, proxy server, communication method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent an increase in the number of WebSocket sessions in a communication system based on a WebSocket protocol.SOLUTION: A communication system comprises: a Web server on which a Web application operates; a terminal on which a Web browser operates; and a proxy server connected with the Web server and the terminal. The Web server includes a first proxy client that puts WebSocket sessions used by the Web application together and connects the resultant WebSocket session with the proxy server as a first WebSocket session. The terminal includes a second proxy client that puts WebSocket sessions used by the Web browser together and connects the resultant WebSocket session with the proxy server as a second WebSocket session. The proxy server includes a relay unit that relays the first WebSocket session and the second WebSocket session.

Description

  The present invention relates to a communication system, a proxy server, a communication method, and a program, and more particularly, to a communication system, a proxy server, a communication method, and a program based on WebSocket.

  As a communication standard for efficiently performing bidirectional communication between a Web server and a client terminal (hereinafter referred to as “terminal”), the WebSocket protocol is known.

  The WebSocket protocol is a technology for establishing a real-time bidirectional communication by extending a session between a Web server and a terminal end-to-end.

  As a related technology, in order to reduce the load on the client browser (browser on the terminal), a proxy server is provided between the client browser and the service providing server, and the information manipulation library executed by the client browser is used as the proxy In addition to executing the above, the client browser aggregates the information required to execute the information manipulation library into one message and sends it to the proxy server, while the proxy server aggregates the information acquired from each service into one message. A technique for returning to the client browser is described in Patent Document 1.

  Further, when a load control device is provided between the server and a plurality of clients (terminals), in order to reduce the number of TCP (Transmission Control Protocol) connections between the server and the load control device, A technique for aggregating TCP connections with a plurality of clients is described in Patent Document 2.

International Publication No. 2012/063282 International Publication No. 2007/1295942

  It is assumed that the entire disclosed contents of Patent Documents 1 and 2 are incorporated herein by reference. The following analysis was made by the present inventors.

  FIG. 3 is a diagram for explaining the problems of the related art. FIG. 3 shows a case where four Web servers 120 </ b> A to 120 </ b> D and three terminals 130 </ b> A to 130 </ b> C perform WebSocket communication via the Internet 40 and the carrier network 50 as an example.

  Since WebSocket sessions are extended end-to-end between the Web browser and Web server in the terminal, WebSocket sessions are extended by the number corresponding to the number of combinations of Web browsers and Web servers. In the example shown in FIG. 3, 12 (= 3 × 4) WebSocket sessions are established on the Internet 40, and 12 (= 3 × 4) WebSocket sessions are established on the carrier network 50.

  At this time, the number of sessions corresponding to the number of Web servers increases only by increasing the number of Web browsers in the terminal. Similarly, just by increasing the number of Web servers, the number of sessions corresponding to the number of Web browsers increases. As a result, there is a problem that the required amount of resources such as memory required for the network device through which communication between the Web browser and the Web server passes increases at a stretch as the number of Web browsers and Web servers increases.

  In addition, since the number of WebSocket sessions established from one terminal is limited to the range of resources held by that terminal (memory amount, etc.), the number of Web servers that can be connected simultaneously using a WebSocket session is limited. .

  As described above, when real-time bidirectional communication is realized by establishing a session end-to-end based on the WebSocket protocol, an increase in the number of sessions established in the network becomes a problem.

  Note that the technique described in Patent Document 1 aggregates information exchanged between the browser and the proxy server into one message, and does not reduce the number of socket communication sessions. In addition, the technique described in Patent Document 2 aggregates TCP connections with a plurality of clients by a load control device, and performs socket communication when the number of Web browsers used by each client increases. It does not reduce the number of sessions.

  Therefore, it is desired to prevent an increase in the number of WebSocket sessions in a communication system based on the WebSocket protocol. An object of the present invention is to provide a communication system, a proxy server, a communication method, and a program that contribute to such a demand.

The communication system according to the first aspect of the present invention is:
A web server running a web application,
A terminal running a web browser,
A proxy server connected to the web server and the terminal,
The Web server includes a first proxy client that aggregates WebSocket sessions used by the Web application and connects to the proxy server as a first WebSocket session;
The terminal has a second proxy client that aggregates WebSocket sessions used by the Web browser and connects to the proxy server as a second WebSocket session;
The proxy server includes a relay unit that relays the first WebSocket session and the second WebSocket session.

The proxy server according to the second aspect of the present invention is:
A proxy server connected to a web server running a web (web) application and a terminal running a web browser,
The Web server includes a first proxy client that aggregates WebSocket sessions used by the Web application and connects to the proxy server as a first WebSocket session;
The terminal has a second proxy client that aggregates WebSocket sessions used by the Web browser and connects to the proxy server as a second WebSocket session;
A relay unit configured to relay the first WebSocket session and the second WebSocket session;

The communication method according to the third aspect of the present invention is:
The proxy server is a Web server on which a Web (Web) application operates, and is connected to the Web server configured to aggregate a WebSocket session used by the Web application as a first WebSocket session. When,
Connecting to the proxy server configured to aggregate a WebSocket session used by the Web browser as a second WebSocket session, which is a terminal on which the Web browser operates;
Relaying the first WebSocket session and the second WebSocket session.

The program according to the fourth aspect of the present invention is:
A process of connecting to the Web server configured to aggregate a WebSocket session used by the Web application as a first WebSocket session, which is a Web server on which a Web (Web) application operates;
A process of connecting to the proxy server configured to aggregate a WebSocket session used by the Web browser as a second WebSocket session, which is a terminal on which the Web browser operates;
The computer executes the process of relaying the first WebSocket session and the second WebSocket session.
The program can be provided as a program product recorded on a non-transitory computer-readable recording medium.

  According to the communication system, proxy server, communication method, and program according to the present invention, it is possible to prevent an increase in the number of WebSocket sessions in a communication system based on the WebSocket protocol.

It is a figure which shows the structure of the communication system which concerns on one Embodiment as an example. It is a block diagram which shows the structure of the communication system which concerns on 1st Embodiment as an example. It is a figure for demonstrating the problem of related technology.

  First, an outline of one embodiment will be described. Note that the reference numerals of the drawings attached to this summary are merely examples for facilitating understanding, and are not intended to limit the present invention to the illustrated embodiment.

  FIG. 1 is a diagram illustrating an example of a schematic configuration of a communication system according to an embodiment. Referring to FIG. 1, the communication system includes Web servers 20A to 20D, terminals 30A to 30C, and a WebSocket proxy server 10 as an example.

  FIG. 2 is a block diagram illustrating a more detailed configuration of the communication system shown in FIG. Referring to FIG. 2, the communication system includes Web servers 20A to 20D on which a Web application 24 operates, terminals 30A to 30C on which Web browsers 34A to 34C operate, Web servers 20A to 20D, and terminals 30A to 30C. And a proxy server (WebSocket proxy server) 10 connected to. The number of Web servers and terminals and the number of Web browsers shown in FIGS. 1 and 2 are merely examples, and the present invention is not limited to the illustrated embodiment.

  The Web servers 20 </ b> A to 20 </ b> D have a first proxy client (server-side proxy client) 22 that aggregates WebSocket (web socket) sessions used by the Web application 24 and connects to the proxy server 10 as a first WebSocket session. On the other hand, the terminals 30A to 30C have a second proxy client (terminal-side proxy client) 32 that aggregates WebSocket sessions used by the Web browsers 34A to 34C and connects to the proxy server 10 as a second WebSocket session. The proxy server 10 includes a relay unit 12 that relays the first WebSocket session and the second WebSocket session.

  As described above, in the communication system according to the embodiment, the WebSocket session established between the Web browsers 34A to 34C and the Web servers 20A to 20C in the terminals 30A to 30C is transferred to the proxy client 22 on each of the Web browser side and the Web server side. It is aggregated by terminating at 32 and proxying to the other party.

  At this time, the number of WebSocket sessions increases when the number of terminals increases by one, and the number of WebSocket sessions increases when the number of Web servers increases by one. At this time, a resource amount equivalent to the number of additional Web servers may be added to the network device between the Web browser and the Web server.

  That is, according to the communication system according to the embodiment, in the related technology (FIG. 3), the number of WebSocket sessions established in the network by the number of combinations of terminals and Web servers is passed through the WebSocket proxy server arranged in the network. It is possible to reduce significantly by consolidating as such. At this time, it is possible to reduce resources (memory amount and the like) required for devices in the network through which the session passes.

<Embodiment 1>
Next, a communication system according to the first embodiment will be described with reference to the drawings. FIG. 2 is a block diagram illustrating an example of the configuration of the communication system according to the present embodiment.

  Referring to FIG. 2, the WebSocket proxy server 10 includes a relay unit 12 and a user management DB (Database) 14.

  The WebSocket proxy server 10 is connected to the Web servers 20A to 20D. In the Web server 20A, first, the server side proxy client 22 is connected to the front stage, and the Web application 24 is connected to the rear stage. Since the Web servers 20B to 20D have the same configuration as the Web server 20A, description thereof is omitted.

  The WebSocket proxy server 10 is connected to the terminals 30A to 30C. In the terminal 30A, first, the terminal side proxy client 32 is connected to the front stage, and the Web browsers 34A to 34C are connected to the rear stage. Note that the terminals 30B and 30C have the same configuration as the terminal 30A, and thus description thereof is omitted.

  The relay unit 12 of the WebSocket proxy server 10 is connected to each of the terminals 30A to 30C and the Web servers 20A to 20D, and mediates a WebSocket session between the terminal and the Web server. The relay unit 12 requests connection destination IP address information of the terminals 30A to 30C and the Web servers 20A to 20D from the user management DB 14 as necessary.

  The user management DB 14 manages the IP addresses held by the terminals 30A to 30C and the Web servers 20A to 20D, and provides connection destination IP address information in response to a request from the relay unit 12.

  Web servers 20A to 20D provide Web services using WebSocket to terminals 30A to 30C.

  The server-side proxy client 22 aggregates WebSocket sessions established by the Web application 24 and connects to the relay unit 12 of the WebSocket proxy server 10.

  The Web application 24 provides a Web service after a WebSocket session is established with the server-side proxy client 22.

  The terminals 30A to 30C provide a function for a user to use a web service provided by the web servers 20A to 20D.

  The terminal side proxy client 32 detects and aggregates WebSocket sessions established by the plurality of Web browsers 34 </ b> A to 34 </ b> C and connects to the relay unit 12 of the WebSocket proxy server 10.

  The Web browsers 34A to 34C extend a WebSocket session with the terminal side proxy client 32, and provide a screen for using the Web service provided by the Web servers 20A to 20D to the user.

  Next, the operation of the communication system of this embodiment will be described with reference to FIG.

  The terminal 30A includes a terminal side proxy client 32. WebSocket communication from the Web browsers 34A to 34C is collected in the terminal side proxy client 32 in the terminal 30A.

  On the other hand, the Web server 20 </ b> A includes a server-side proxy client 22. WebSocket communication from the Web application 24 is integrated into the server side proxy client 22 within the Web server 20A.

  Each of the terminal-side proxy client 32 and the server-side proxy client 22 notifies the WebSocket proxy server 10 of an IP (Internet Protocol) address allocated to itself in advance. The user management DB 14 of the WebSocket proxy server 10 manages connection destinations on the terminals 30A to 30C side and the Web servers 20A to 20D side. Each of the terminal-side proxy client 32 and the server-side proxy client 22 notifies the WebSocket proxy server 10 of the changed IP address each time the allocated IP address is changed.

  The terminal-side proxy client 32 and the server-side proxy client 22 connect to the relay unit 12 of the WebSocket proxy server 10 using WebSocket only at the timing when connection is required.

  When WebSocket communication is started, first, a handshake of a WebSocket session is performed by HTTP (Hypertext Transfer Protocol) communication. The terminal-side proxy client 32 detects the start of a WebSocket session by monitoring such handshake communication, and aggregates WebSocket sessions by passing subsequent WebSocket sessions via the terminal-side proxy client 32. Note that the terminal-side proxy client 32 may detect and aggregate only WebSocket communication.

  The server-side proxy client 22 releases the connection only when there is no terminal connected to the Web server 20A. The terminal-side proxy client 32 releases the connection only when there are no web browsers 34 connected to it under WebSocket.

  According to the communication system according to the present embodiment, the number of WebSocket sessions established in the network can be significantly reduced as compared with the related technology (FIG. 3). In addition, the number of WebSocket sessions that increase when the Web browser and Web server in the terminal are increased can be reduced. As a result, the amount of resources required for network devices in the network can also be reduced. Also, by consolidating the number of WebSocket sessions that are spread from one terminal to one and increasing the efficiency of resource usage within the terminal, the maximum number of Web servers that can be connected simultaneously with the same amount of terminal resources is increased. Is possible.

<Modification 1>
In the above embodiment, the IP address is managed by the user management DB 14 as the connection destination information of the Web server. On the other hand, as the connection destination information on the Web server side, a method of managing by URL (Uniform Resource Locator) instead of IP address may be adopted.

<Modification 2>
In the above embodiment, a method of notifying the IP address from the terminal as the connection destination information of the terminal is used. However, when the IP address is issued from the carrier network 50, since the issued IP address can be managed in the carrier network 50, the notification of the IP address from the terminal may be omitted.

In the present invention, the following modes are possible.
[Form 1]
The communication system according to the first aspect is as described above.
[Form 2]
The proxy server holds an identifier of the first proxy client and an IP (Internet Protocol) address assigned to the first proxy client in association with each other, and the identifier of the second proxy client and the second proxy client A management database that holds the IP address assigned to the proxy client
The communication system according to mode 1, wherein the relay unit relays the first WebSocket session and the second WebSocket session with reference to the management database.
[Form 3]
The first proxy client notifies the proxy server of an IP address assigned to the first proxy client;
The management database stores the identifier of the first proxy client and the IP address assigned to the first proxy client in association with each other based on the notification from the first proxy client. Communication system.
[Form 4]
The second proxy client notifies the proxy server of an IP address assigned to the second proxy client;
The management database holds the identifier of the second proxy client and the IP address assigned to the second proxy client in association with each other based on the notification from the second proxy client. The communication system according to 1.
[Form 5]
4. The communication system according to mode 2 or 3, wherein the management database associates and holds an identifier of the second proxy client and an IP address issued from the carrier network to the second proxy client.
[Form 6]
The proxy server holds the identifier of the first proxy client and the URL of the Web application in association with each other, and also stores the identifier of the second proxy client and the IP address assigned to the second proxy client. Have a management database
The communication system according to mode 1, wherein the relay unit relays the first WebSocket session and the second WebSocket session with reference to the management database.
[Form 7]
The first proxy client notifies the proxy server of a URL (Uniform Resource Locator) of the Web application,
The communication database according to mode 6, wherein the management database associates and holds an identifier of the first proxy client and a URL of the Web application in response to a notification from the first proxy client.
[Form 8]
The proxy server according to the second aspect is as described above.
[Form 9]
The identifier of the first proxy client and the IP (Internet Protocol) address assigned to the first proxy client are held in association with each other, and the identifier of the second proxy client and the second proxy client are assigned. A management database that holds the associated IP addresses in association with each other,
The proxy server according to mode 8, wherein the relay unit relays the first WebSocket session and the second WebSocket session with reference to the management database.
[Mode 10]
The first proxy client notifies the proxy server of an IP address assigned to the first proxy client;
The management database according to embodiment 9, wherein the management database associates and holds an identifier of the first proxy client and an IP address assigned to the first proxy client based on a notification from the first proxy client. Proxy server.
[Form 11]
The second proxy client notifies the proxy server of an IP address assigned to the second proxy client;
The management database holds the identifier of the second proxy client and the IP address assigned to the second proxy client in association with each other based on the notification from the second proxy client. Proxy server as described in.
[Form 12]
11. The proxy server according to mode 9 or 10, wherein the management database associates and holds an identifier of the second proxy client and an IP address assigned to the second proxy client from a carrier network.
[Form 13]
Management that holds the identifier of the first proxy client and the URL of the Web application in association with each other and holds the identifier of the second proxy client and the IP address assigned to the second proxy client in association with each other With a database,
The proxy server according to mode 8, wherein the relay unit relays the first WebSocket session and the second WebSocket session with reference to the management database.
[Form 14]
The first proxy client notifies the proxy server of a URL (Uniform Resource Locator) of the Web application,
The proxy server according to mode 13, wherein the management database associates and holds an identifier of the first proxy client and a URL of the Web application in response to a notification from the first proxy client.
[Form 15]
The communication method according to the third viewpoint is as described above.
[Form 16]
A web server running a web application,
A terminal running a web browser,
A communication method in a communication system comprising the Web server and a proxy server connected to the terminal,
The Web server aggregates WebSocket (Web socket) sessions used by the Web application and connects to the proxy server as a first WebSocket session;
The terminal aggregates WebSocket sessions used by the Web browser and connects to the proxy server as a second WebSocket session;
The proxy server includes a step of relaying the first WebSocket session and the second WebSocket session.
[Form 17]
The program is related to the fourth viewpoint.

  It should be noted that the entire disclosure content of Patent Document 1 or 2 is incorporated herein by reference. Within the scope of the entire disclosure (including claims) of the present invention, the embodiment can be changed and adjusted based on the basic technical concept. Further, various combinations or selections of various disclosed elements (including each element of each claim, each element of each embodiment, each element of each drawing, etc.) are possible within the scope of the claims of the present invention. It is. That is, the present invention of course includes various variations and modifications that could be made by those skilled in the art according to the entire disclosure including the claims and the technical idea. In particular, with respect to the numerical ranges described in this document, any numerical value or small range included in the range should be construed as being specifically described even if there is no specific description.

10 WebSocket proxy server 12 Relay unit 14 User management DB
20A-20D, 120A-120D Web server 22 Server side proxy client 24 Web application 30A-30C, 130A-130C Terminal 32 Terminal side proxy client 34A-34C Web browser 40 Internet 50 Carrier network

Claims (10)

A web server running a web application,
A terminal running a web browser,
A proxy server connected to the web server and the terminal,
The Web server includes a first proxy client that aggregates WebSocket sessions used by the Web application and connects to the proxy server as a first WebSocket session;
The terminal has a second proxy client that aggregates WebSocket sessions used by the Web browser and connects to the proxy server as a second WebSocket session;
The proxy server includes a relay unit that relays the first WebSocket session and the second WebSocket session. The proxy server holds an identifier of the first proxy client and an IP (Internet Protocol) address assigned to the first proxy client in association with each other, and the identifier of the second proxy client and the second proxy client A management database that holds the IP address assigned to the proxy client
The communication system according to claim 1, wherein the relay unit relays the first WebSocket session and the second WebSocket session with reference to the management database. The first proxy client notifies the proxy server of an IP address assigned to the first proxy client;
The management database holds the identifier of the first proxy client and the IP address assigned to the first proxy client in association with each other based on the notification from the first proxy client. The communication system described. The second proxy client notifies the proxy server of an IP address assigned to the second proxy client;
The management database associates and holds an identifier of the second proxy client and an IP address assigned to the second proxy client based on a notification from the second proxy client. 4. The communication system according to 3.   The communication system according to claim 2 or 3, wherein the management database associates and holds an identifier of the second proxy client and an IP address issued to the second proxy client from a carrier network. The proxy server holds the identifier of the first proxy client and the URL of the Web application in association with each other, and also stores the identifier of the second proxy client and the IP address assigned to the second proxy client. Have a management database
The communication system according to claim 1, wherein the relay unit relays the first WebSocket session and the second WebSocket session with reference to the management database. The first proxy client notifies the proxy server of a URL (Uniform Resource Locator) of the Web application,
The communication system according to claim 6, wherein the management database associates and holds an identifier of the first proxy client and a URL of the Web application in response to a notification from the first proxy client. A proxy server connected to a web server running a web (web) application and a terminal running a web browser,
The Web server includes a first proxy client that aggregates WebSocket sessions used by the Web application and connects to the proxy server as a first WebSocket session;
The terminal has a second proxy client that aggregates WebSocket sessions used by the Web browser and connects to the proxy server as a second WebSocket session;
A proxy server comprising a relay unit that relays the first WebSocket session and the second WebSocket session. The proxy server is a Web server on which a Web (Web) application operates, and is connected to the Web server configured to aggregate a WebSocket session used by the Web application as a first WebSocket session. When,
Connecting to the proxy server configured to aggregate a WebSocket session used by the Web browser as a second WebSocket session, which is a terminal on which the Web browser operates;
Relaying the first WebSocket session and the second WebSocket session. A process of connecting to the Web server configured to aggregate a WebSocket session used by the Web application as a first WebSocket session, which is a Web server on which a Web (Web) application operates;
A process of connecting to the proxy server configured to aggregate a WebSocket session used by the Web browser as a second WebSocket session, which is a terminal on which the Web browser operates;
A program that causes a computer to execute processing for relaying the first WebSocket session and the second WebSocket session.

Images