CN102546794B - Method for directly communicating browser client with back-end server as well as gateway and communication system - Google Patents

Abstract

Embodiments of the present invention provide a method, a gateway and a communication system for direct communication between a browser client and a backend server, so as to improve resource utilization while realizing end-to-end full-duplex communication between the browser client and the backend server. The method includes: receiving the user request message sent by the browser client through the transmission control protocol TCP connection between the gateway and the browser client; querying the message forwarding table according to the IP address and port of the browser client, and obtaining the The IP address and the port of the back-end server associated with the IP address of the client and the port; According to the IP address and the port of the back-end server, the TCP connection between the gateway and the back-end server sends the user request message to the The backend server corresponding to the IP address and port of the above backend server. The method provided by the invention does not need to consume additional resources to implement the protocol conversion between HTTP and the backend server, thus saving overhead.

Description

Method, gateway and communication system for direct connection between browser client and backend server

technical field

The invention relates to the field of communication, in particular to a method, a gateway and a communication system for direct communication between a browser client and a backend server.

Background technique

Real-time Web is a class of Internet applications in the Web 2.0 system, and its typical representatives mainly include Internet social networking sites Facebook and Twitter. In real-time web applications such as social networking sites Facebook and twitter Weibo, the website server needs to actively push the output (Feed) information of the user's friends to the user in real time, so that the user and his friends can generate and share feed information anytime and anywhere. and consume content. Other Web applications such as monitoring, instant messaging, and instant quotation systems also require the server to transmit changes in the background to the client in real time. It can be seen that the main characteristics of real-time Web applications are high interactivity and real-time performance, that is, it is very necessary to provide end-to-end, two-way (full-duplex) real-time communication between the browser and the back-end server.

Existing methods for achieving real-time interaction between the browser and the back-end server to obtain real-time update information include Hypertext Transfer Protocol (Hypertext Transfer Protocol, HTTP) polling (Polling) and HTTP long-connection-based "server push" technology (i.e. Comet technology). )wait. Taking HTTP-based polling as an example, the method for obtaining real-time update information through real-time interaction between the browser and the back-end server provided by the prior art is described below, including the following steps:

S11, the browser connects to the web application server through the web, and sends an HTTP request to the web application server based on HTTP;

S12, the web application server receives and parses the HTTP request of the browser, and converts the HTTP request into a call to its extended custom application service program;

S13, expand the custom application service program to analyze the Web application logic and protocol, and convert these Web application logic and protocol into a standard API or message call to the back-end server;

S14, the extended custom application service program calls the corresponding message client program, for example, RSS (Really Simple Syndication) client, JMS (Java Message Service) client, EJB (Enterprise Java Bean) client or XMPP (The Extensible Messaging and Presence Protocol) client program, establishes a full-duplex TCP/IP connection to the back-end server, and interacts based on the corresponding message protocol to obtain update information from the back-end server;

S14, the browser requests the web server based on HTTP polling, or the web server uses the Comet technology to send information to the browser for display.

In the method for obtaining real-time update information through real-time interaction between the browser and the back-end server provided by the above-mentioned prior art, the session between the browser and the Web application server and the session between the Web application server and the back-end server are completely independent and fragmented, Therefore, there is following defective in above-mentioned prior art:

1) Serious waste of resources. Since the information carried by the HTTP protocol is often only a few bytes, and the HTTP header is too large (nearly 1K), that is, there are many invalid information loads, therefore, frequent polling causes large system bandwidth consumption and high delay;

2) The system has a performance bottleneck. Since the web server between the browser and the back-end server needs to run the main business logic and calculation, the performance of the web server becomes the performance bottleneck of the system;

3) End-to-end full-duplex communication cannot be realized. The communication between the browser and the web application server is based on the HTTP protocol, such as the traditional HTTP polling or Comet technology, to obtain real-time information; since the traditional HTTP polling is half-duplex, the Comet technology based on the HTTP protocol needs to be in two Two-way communication is realized on the connection, so it consumes more server resources, and end-to-end full-duplex communication cannot be well realized between the browser and the back-end server.

Contents of the invention

Embodiments of the present invention provide a method, a gateway and a communication system for direct communication between a browser client and a backend server, so as to improve resource utilization while realizing end-to-end full-duplex communication between the browser client and the backend server.

An embodiment of the present invention provides a method for direct communication between a browser client and a backend server, the method comprising: receiving a user request message sent by the browser client through a transmission control protocol TCP connection between the gateway and the browser client, and the user The request message includes: the IP address and port of the browser client;

According to the IP address and port query message forwarding table of the browser client, obtain the IP address and port of the back-end server associated with the IP address and port of the browser client;

According to the IP address and port of the back-end server, the user request message is sent to the back-end server corresponding to the IP address and port of the back-end server through the TCP connection between the gateway and the back-end server.

An embodiment of the present invention provides a gateway, and the gateway includes:

The receiving module is used to receive the user request message sent by the browser client through the transmission control protocol TCP connection between the gateway and the browser client, and the user request message includes: the IP address and port of the browser client;

The first acquisition module is used to query the message forwarding table according to the IP address and port of the browser client, and obtain the IP address and port of the back-end server associated with the IP address and port of the browser client;

A sending module, configured to send the user request message to the back-end server corresponding to the IP address and port of the back-end server through the TCP connection between the gateway and the back-end server according to the IP address and port of the back-end server end server.

An embodiment of the present invention provides a communication system, and the communication system includes: a browser client, a gateway, and a backend server;

The browser client is configured to send a user request message through a transmission control protocol TCP connection with the gateway, and the user request message includes: the IP address and port of the browser client;

The gateway is configured to receive the user request message sent by the browser client through the TCP connection with the browser client; query the message forwarding table according to the IP address and port of the browser client in the user request message, and obtain The IP address and the port of the back-end server associated with the IP address and port of the browser client; according to the IP address and the port of the back-end server, the user request message is sent through the TCP connection with the back-end server Send to the back-end server corresponding to the IP address and port of the back-end server;

The backend server is configured to receive the user request message forwarded by the gateway. As can be seen from the above-mentioned embodiment of the present invention, because what the gateway establishes with the browser client and the back-end server is a TCP long connection, on the one hand, the browser client can realize full-duplex communication with the back-end server, and the real-time information of the browser client It can be sent to the back-end server in real time at almost the release time, so the real-time performance is strong; on the other hand, the gateway is responsible for forwarding the user request message between the browser client and the back-end server through the TCP connection, and the main business logic and calculation distribution In the browser client and back-end server, the gateway does not need to undertake the main business logic and calculation, and does not need to consume additional resources to realize the protocol conversion between HTTP and the back-end server, thus saving overhead.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the prior art or the accompanying drawings that need to be used in the description of the embodiments. Obviously, the accompanying drawings in the following description are only some of the present invention. Embodiment, for those skilled in the art, other drawings can also be obtained like these drawings.

FIG. 1 is a schematic flow diagram of a method for direct communication between a browser client and a backend server provided by an embodiment of the present invention;

Fig. 2 is a schematic diagram of the interaction between the browser client, the WebSocket gateway and the back-end server in the direct connection method between the browser client and the back-end server provided by the embodiment of the present invention;

FIG. 3 is a schematic diagram of a gateway structure provided by an embodiment of the present invention;

Fig. 4 is a schematic diagram of a gateway structure provided by another embodiment of the present invention;

Fig. 5 is a schematic diagram of a gateway structure provided by another embodiment of the present invention;

Fig. 6 is a schematic diagram of a gateway structure provided by another embodiment of the present invention;

FIG. 7 is a schematic structural diagram of a communication system provided by an embodiment of the present invention;

Fig. 8 is a schematic diagram of the physical connection of the communication system provided by the embodiment of the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention belong to the protection scope of the present invention.

Please refer to FIG. 1 , which is a schematic flowchart of a method for direct communication between a browser client and a backend server provided by an embodiment of the present invention. The method of accompanying drawing 1 example is that the communication protocol that the browser is a webpage (Web) browser, the gateway is a WebSocket gateway, and the communication protocol that the WebSocket gateway communicates with the browser client and the back-end server is the HTML5 standard WebSocket protocol as an example. The subject can be a WebSocket gateway, which mainly includes steps:

S101. Receive a user request message sent by the browser client through a transmission control protocol TCP connection between the gateway and the browser client, where the user request message includes: the IP address and port of the browser client.

Optionally, the method may also include: receiving a handshake request message sent by the browser client through a TCP connection between the gateway and the browser client, the handshake request message including the IP address and port of the backend server; according to the handshake The request message establishes the TCP connection between the gateway and the back-end server; the IP address and the port of the browser client are associated with the IP address and the port of the back-end server, and the association is updated to the message forwarding Publishing. Wherein, the establishment of the TCP connection between the gateway and the back-end server according to the handshake request message may be: extracting the IP address and port of the back-end server included in the handshake request message; The IP address and port to establish a TCP connection between the gateway and the backend server.

In the embodiment of the present invention, when a user accesses the gateway, the browser client sends an application download request to the gateway, and the web application is downloaded from the gateway to the browser client. Thereafter, in order to obtain real-time information from the back-end server, the user runs the web application program on the browser client to request to establish a transmission control protocol (Transmission Control Protocol, TCP) connection with the gateway.

After the TCP connection between the browser client and the gateway is established, the browser client can send to the gateway through the TCP connection, and the gateway receives a user request message through the TCP, for example, a subscription request, and the user request message contains the IP address of the browser client. Information such as address and port indicating the source of the message. In order to improve the efficiency of message transmission between the browser client and the gateway, after the browser client establishes a TCP connection with the gateway, the browser client can send a handshake request message to the gateway, and the handshake request message is based on the HTTP protocol. The gateway receives the handshake request message sent by the browser client through its TCP connection with the browser client. When the gateway sends a handshake success response message to the browser client, the negotiation between the browser client and the gateway is successful, and the subsequent interaction between the browser client and the gateway is based on the WebSocket protocol. WebSocket protocol messages can be passed through The TCP connection is used for transmission. Because the message head (Head) of WebSocket protocol message is very small and the overhead of message is little, therefore, compared with browser and Web application server in prior art, adopt HTTP protocol to transmit, efficiency will be high; On the other hand, because gateway and The communication protocol between the browser client and the back-end server is the HTML5 standard WebSocket protocol instead of a private custom protocol, so it has good versatility.

The handshake request message received by the gateway can include information such as the IP address, port, and communication protocol of the backend server of the backend server, wherein the communication protocol of the backend server is an optional item in the handshake request message, that is, the handshake request message can be The communication protocol of the backend server is not included, and the information of the communication protocol of the backend server can be preconfigured. Information such as the IP address and port of the back-end server and the communication protocol of the back-end server can be formed by adding cells in the handshake request message, as shown below, which is the HTTP Upgrade handshake of adding cells in the handshake request message Example of request message:

Among them, the newly added information element "DestHost: tcp://myDestHostAddress: 9960" is used to declare the IP address and port of the back-end server and the communication protocol of the back-end server. In this embodiment, the back-end server's The communication protocol is TCP.

After receiving the handshake request message sent by the browser client, the gateway establishes its TCP connection with the backend server according to the handshake request message. Specifically, the gateway extracts the IP address and port of the backend server included in the handshake request message, and then establishes a TCP connection from the gateway to the backend server according to the IP address and port of the backend server.

S102. Query a message forwarding table according to the IP address and port of the browser client, and obtain the IP address and port of the backend server associated with the IP address and port of the browser client.

In the embodiment of the present invention, the gateway maintains a message forwarding table, and when a new connection is established, the gateway can update the message forwarding table. For example, after the gateway receives the handshake request message and establishes the TCP connection between the gateway and the back-end server accordingly, it can update the message forwarding table, that is, record the IP address, port, and port number of the back-end server. information such as the communication protocol and the IP address and port of the browser client. In the implementation of the present invention, after the gateway establishes the TCP connection between the gateway and the back-end server according to the handshake request message sent by the browser client, the IP address and the port of the browser client are associated with the IP address and the port of the back-end server, and update the association relationship into the message forwarding table. Therefore, the updated message forwarding table includes information such as the IP address and port of the backend server, the communication protocol of the backend server, and the IP address and port of the browser client, and can record the information of the browser client The IP address and port of the client are associated with the IP address and port of the back-end server. The significance of these associations recorded in the message forwarding table is that, according to the IP address and port of the browser client, by querying the message forwarding table, the IP address and port of the associated back-end server can be obtained, or vice versa, according to the IP address and port of the back-end server. IP address, port, by querying the message forwarding table, you can obtain the IP address and port of the browser client associated with it.

It should be noted that since the back-end server can broadcast the "connection establishment request" message, the gateway can also establish a TCP connection with the back-end server after listening to these broadcasted "connection establishment request" messages. The way of establishing the TCP connection with the backend server is not limited.

S103, according to the IP address and port of the back-end server, send the user request message to the back-end server corresponding to the IP address and port of the back-end server through the TCP connection between the gateway and the back-end server.

When the user sends a request message through the browser client, the gateway receives the request message sent by the browser client. Due to the network protocol layer (for example, IP layer) below the application layer, the gateway can resolve the IP address of the backend server, the port, and the communication protocol of the backend server contained in the request message. Therefore, the gateway can query the updated The message forwarding table, that is, the gateway queries the message forwarding table according to the IP address and port of the browser client to obtain the IP address and port of the back-end server associated with the IP address and port of the browser client. Then, according to the acquired IP address and port of the back-end server, the request message is sent to the back-end server corresponding to the IP address and the port of the back-end server, thereby realizing communication with the back-end through the gateway The TCP connection of the server forwards the interactive messages between the browser client and the backend server.

Optionally, the method provided in the embodiment of the present invention may further include: receiving a request response message sent by the backend server through a TCP connection between the gateway and the backend server, the request response message including: the IP address of the backend server address and port; query the message forwarding table according to the IP address and port of the back-end server, obtain the IP address and port of the browser client associated with the IP address and port of the back-end server; according to the browser IP address and port of the client, sending the request response message to the browser client corresponding to the IP address and port of the browser client through the TCP connection between the gateway and the browser client.

When the backend server receives the request message forwarded by the gateway, it sends a request response message to the gateway. The gateway receives the request response message sent by the backend server through its TCP connection with the backend server, and the request response message is a response to the user request message sent by the browser client, which includes the IP address and port of the backend server , and can also contain information such as the communication protocol of the backend server.

Due to the network protocol layer (for example, IP layer) below the application layer, the gateway can resolve information such as the IP address of the back-end server, the port, and the communication protocol of the back-end server contained in the request response message, so the gateway can query all The updated message forwarding table, that is, the gateway queries the updated message forwarding table according to the IP address and port of the back-end server, and obtains the IP address of the browser client associated with the IP address and port of the back-end server address, port. Then, according to the obtained IP address and port of the browser client, the request response message is forwarded to the browser client corresponding to the IP address and port of the browser client, so as to realize the connection with the gateway established in advance. The TCP connection of the browser client forwards the interactive messages between the browser client and the backend server.

It can be known from the browser client and the back-end server direct communication method provided by the above-mentioned embodiments of the present invention that since the gateway can establish a TCP long connection with the browser client and the back-end server, on the one hand, the browser client can communicate with the back-end server. The end server realizes full-duplex communication, and the real-time information of the browser client can be sent to the back-end server in real time almost at the release time, so the real-time performance is strong; on the other hand, the gateway is responsible for forwarding the browser client to the back-end through the TCP connection For user request messages between servers, the main business logic and calculation are distributed between the browser client and the back-end server. The gateway does not need to undertake the main business logic and calculation, and does not need to consume additional resources to implement the protocol between HTTP and the back-end server. conversion, thus saving overhead.

The following takes the interaction between the browser client, the WebSocket gateway and the back-end server, and the browser client sends a message subscription request to the WebSocket gateway through the established TCP connection to request to subscribe to new messages as an example to further illustrate the relationship between the browser and the back-end server. For the direct connection method of the end-server, please refer to Figure 2. The interaction between the browser client, the WebSocket gateway and the back-end server mainly includes:

S201. The browser client sends a web application download request to the WebSocket gateway.

The web application download request is sent to the WebSocket gateway by the browser client after receiving the access request when the user accesses the gateway.

S202, the WebSocket gateway downloads the Web application to the browser client.

S203, the browser client runs the web application program.

S204. The browser client receives a real-time information request message input by the user.

S205, the browser client sends a handshake request message to the WebSocket gateway through the web application program.

At the beginning of the communication, the browser client can send a HTTP-based handshake request message to the gateway to request to negotiate a communication protocol with the gateway. The handshake request message includes the IP address and port of the backend server, and optionally, the communication protocol of the backend server and the like. The IP address and port of the back-end server, optionally, information such as the communication protocol of the back-end server can also be included by adding new cells in the handshake request message. The following are new cells in the handshake request message An example of the HTTP Upgrade handshake request message:

Among them, the newly added information element "DestHost: tcp://myDestHostAddress: 9960" is used to declare the IP address and port of the back-end server and the communication protocol of the back-end server. In this embodiment, the back-end server's The communication protocol is TCP.

S206, the WebSocket gateway parses the handshake request message.

The gateway parses the handshake request message, extracts the IP address and port of the back-end server contained therein, and then establishes a TCP connection between the gateway and the back-end server according to the IP address and port of the back-end server, including:

S207, the WebSocket gateway sends a TCP connection establishment request to the backend server.

S208. The backend server returns a response message to the WebSocket gateway.

S209, the WebSocket gateway updates the message forwarding table.

That is, the WebSocket gateway records the IP address and port of the backend server, the communication protocol of the backend server and the IP address and port of the browser client in the message forwarding table, and the updated message forwarding table includes all information such as the IP address and port of the back-end server, the communication protocol of the back-end server, and the IP address and port of the browser client, and can record the IP address and port of the browser client in relation to the back-end The IP address and port association of the server. In this implementation, after the gateway establishes the TCP connection between the gateway and the backend server according to the handshake request message sent by the browser client, the IP address and port of the browser client are associated with the IP address and port of the backend server, and The association relationship is updated in the message forwarding table. Therefore, the updated message forwarding table includes information such as the IP address and port of the backend server, the communication protocol of the backend server, and the IP address and port of the browser client, and includes information such as the IP address and port of the browser client. The IP address, port and the IP address and port association relationship of the backend server. The significance of these associations recorded in the message forwarding table is that, according to the IP address and port of the browser client, by querying the message forwarding table, the IP address and port of the associated back-end server can be obtained, or vice versa, according to the IP address and port of the back-end server. IP address, port, by querying the message forwarding table, you can obtain the IP address and port of the browser client associated with it.

S210, the WebSocket gateway sends a handshake request response message to the browser client.

The handshake request response message sent by the WebSocket gateway to the browser client indicates that the WebSocket gateway has successfully established a TCP connection with the browser client and the backend server, and subsequent message interactions between the browser client and the backend server can be carried out through this TCP connection .

S211. The browser client sends a message subscription request to the WebSocket gateway.

For the network protocol layer below the application layer, for example, the IP layer, the message subscription request includes information such as the IP address and port of the backend server, and the communication protocol of the backend server.

S212. The WebSocket gateway parses the message subscription request.

At the network protocol layer (for example, IP layer) below the application layer, the WebSocket gateway can resolve information such as the IP address of the back-end server, the port, and the communication protocol of the back-end server contained in the message subscription request. Therefore, The WebSocket gateway can query the updated message forwarding table in step S209, that is, the WebSocket gateway queries the message forwarding table according to the IP address and port of the browser client, and obtains the IP address and the IP address of the backend server associated with the browser client. port.

S213, the WebSocket gateway sends a message subscription request to the backend server.

The WebSocket gateway sends the message subscription request to the backend server corresponding to the IP address and port of the backend server according to the acquired IP address and port of the backend server.

S214. The backend server sends a request response message corresponding to the message subscription request to the WebSocket gateway.

For the network protocol layer below the application layer, for example, the IP layer, the response message corresponding to the message subscription request includes the IP address and port of the backend server, and may also include information such as the communication protocol of the backend server.

S215. The WebSocket gateway forwards the response message of the backend server to the browser client.

S216. The backend server sends an update message to the WebSocket gateway.

The update message is the message requested to be subscribed by the message subscription request.

S217, the WebSocket gateway parses the response message corresponding to the message subscription request.

Due to the network protocol layer (for example, IP layer) below the application layer, the WebSocket gateway can resolve the IP address of the back-end server, the port and the IP address of the back-end server contained in the request response message corresponding to the message subscription request. communication protocol and other information, therefore, the WebSocket gateway can query the updated message forwarding table in step S209, that is, the WebSocket gateway queries the updated message forwarding table according to the IP address and port of the back-end server, and obtains the information related to the The IP address and port of the browser client associated with the end server.

S218, the WebSocket gateway forwards the update message to the browser client.

After the IP address and the port of the browser client associated with the described back-end server obtained, the WebSocket gateway inquires about the corresponding browser communication connection through the IP address and port of the browser client, and sends the back-end server in step S216 to the WebSocket The update message sent by the gateway is forwarded to the browser client corresponding to the IP address and port of the browser client.

S219, the browser client sends a response message corresponding to the update message to the WebSocket gateway.

This response message is an acknowledgment of the update message forwarded by the WebSocket gateway.

S220, the WebSocket gateway sends a response message corresponding to the update message to the backend server.

Please refer to FIG. 3 , which is a schematic diagram of a gateway structure provided by an embodiment of the present invention. For ease of description, only parts related to the embodiments of the present invention are shown. The gateway illustrated in FIG. 3 may be a WebSocket gateway, and the communication protocol for communicating with the browser client and the backend server may be the HTML5 standard WebSocket protocol. The gateway illustrated in Figure 3 includes a receiving module 301, a first acquiring module 302 and a sending module 303, wherein:

The receiving module 301 is used to receive the user request message sent by the browser client through the transmission control protocol TCP connection between the gateway and the browser client, and the user request message includes: the IP address and port of the browser client;

The first obtaining module 302 is used to query the message forwarding table according to the IP address and port of the browser client, and obtain the IP address and port of the back-end server associated with the IP address and port of the browser client;

The sending module 303 is configured to send the user request message to the IP address and port corresponding to the back-end server through the TCP connection between the gateway and the back-end server according to the IP address and port of the back-end server backend server.

When the user sends a request message through the browser client, the receiving module 301 receives the request message sent by the browser client. Due to the network protocol layer (for example, IP layer) below the application layer, the gateway can resolve the IP address of the back-end server, the port, and the communication protocol of the back-end server contained in the request message. Therefore, the first acquisition module 302 can query The updated message forwarding table, that is, the first obtaining module 302 queries the message forwarding table according to the IP address and port of the browser client to obtain the IP address of the back-end server associated with the IP address and port of the browser client. address and port. Then, the sending module 303 sends the request message to the back-end server corresponding to the IP address and port of the back-end server according to the acquired IP address and port of the back-end server, thereby realizing communication with the back-end server through the gateway The TCP connection of the back-end server is forwarded, and the interactive message between the browser client and the back-end server is forwarded.

From the gateway provided by the above-mentioned embodiments of the present invention, it can be seen that since the gateway, the browser client and the back-end server can establish a TCP long connection, on the one hand, the browser client can realize full-duplex communication with the back-end server, and the browser The real-time information of the client can be sent to the back-end server in real time almost at the release time, so the real-time performance is strong; on the other hand, the gateway is responsible for forwarding the user request message sent by the browser client to the back-end server through the TCP connection. The business logic and calculation are distributed between the browser client and the back-end server. The gateway does not need to undertake the main business logic and calculation, and does not need to spend additional resources to realize the protocol conversion between HTTP and the back-end server, thus saving costs.

It should be noted that in the above implementation of the gateway, the division of each functional module is only an example. In practical applications, the above functions can be allocated according to needs, such as the configuration requirements of corresponding hardware or the convenience of software implementation. The functional modules are completed, that is, the internal structure of the gateway is divided into different functional modules to complete all or part of the functions described above. Moreover, in practical applications, the corresponding functional modules in this embodiment can be implemented by corresponding hardware, or can be completed by corresponding hardware executing corresponding software. For example, the aforementioned receiving module can be implemented with The transmission control protocol TCP connection of the browser client is the hardware that receives the user request message sent by the browser client, such as the receiver, or it can be a general processor or other hardware device that can execute the corresponding computer program to complete the aforementioned functions; as mentioned above The first obtaining module can be to have the IP address and port of the back-end server associated with the IP address and port of the browser client to obtain the IP address and port associated with the browser client according to the IP address and port query message forwarding table of the aforementioned browser client. Functional hardware, such as the first acquirer, may also be a general processor or other hardware device capable of executing corresponding computer programs to complete the aforementioned functions (the above description principles can be applied to each embodiment provided in this specification). The gateway illustrated in Figure 3 may further include a handshake message receiving module 401, a connection establishment module 402, and an update module 403, as shown in Figure 4, the gateway provided by another embodiment of the present invention, wherein:

The handshake message receiving module 401 is used to receive the handshake request message sent by the browser client through the TCP connection between the gateway and the browser client, and the handshake request message includes the IP address and port of the backend server;

In order to improve the efficiency of message transmission between the browser client and the gateway, after the browser client establishes a TCP connection with the gateway, the browser client can send a handshake request message to the gateway, and the handshake request message is based on the HTTP protocol. The handshake message receiving module 401 receives the handshake request message sent by the browser client through the TCP connection between the gateway and the browser client. When the gateway sends a handshake success response message to the browser client, the negotiation between the browser client and the gateway is successful, and the subsequent interaction between the browser client and the gateway is based on the WebSocket protocol. WebSocket protocol messages can be passed through The TCP connection is used for transmission. Because the message head (Head) of WebSocket protocol message is very small and the overhead of message is little, therefore, compared with browser and Web application server in prior art, adopt HTTP protocol to transmit, efficiency will be high; On the other hand, because gateway and The communication protocol between the browser client and the back-end server is the HTML5 standard WebSocket protocol instead of a private custom protocol, so it has good versatility.

The handshake request message received by the handshake message receiving module 401 may include information such as the IP address of the backend server, the port, and the communication protocol of the backend server, wherein the communication protocol of the backend server is an optional item in the handshake request message, namely The handshake request message may not include the communication protocol of the backend server, and the information of the communication protocol of the backend server may be preconfigured. Information such as the IP address and port of the back-end server and the communication protocol of the back-end server can be formed by adding cells in the handshake request message, as shown below, which is the HTTP Upgrade handshake of adding cells in the handshake request message Example of request message:

Among them, the newly added information element "DestHost: tcp://myDestHostAddress: 9960" is used to declare the IP address and port of the back-end server and the communication protocol of the back-end server. In this embodiment, the back-end server's The communication protocol is TCP.

A connection establishment module 402, configured to establish a TCP connection between the gateway and the backend server according to the handshake request message;

An update module 403, configured to associate the IP address and port of the browser client with the IP address and port of the backend server, and update the association relationship into the message forwarding table. The gateway illustrated in Figure 3 may further include a response message receiving module 501, a second obtaining module 502, and a response message sending module 503, such as the gateway provided in another embodiment of the present invention shown in Figure 5, wherein:

Response message receiving module 501, configured to receive the request response message sent by the back-end server through the TCP connection between the gateway and the back-end server, the request response message including: the IP address and port of the back-end server;

The second obtaining module 502 is used to query the message forwarding table according to the IP address and port of the back-end server, and obtain the IP address and port of the browser client associated with the IP address and port of the back-end server;

The response message sending module 503 is used to send the request response message to the IP address and port of the browser client through the TCP connection between the gateway and the browser client according to the IP address and port of the browser client corresponding browser client.

It should be understood that the gateway illustrated in FIG. 4 may further include a response message receiving module 501, a second obtaining module 502, and a response message sending module 503 as shown in FIG. 5. The functions are as above and will not be repeated here.

In the embodiment of the present invention, the gateway maintains a message forwarding table, and when a new connection is established, the update module 403 can update the message forwarding table. For example, after the connection establishment module 402 receives the handshake request message and establishes the TCP connection between the gateway and the backend server accordingly, the update module 403 can update the message forwarding table, that is, record the IP address and port of the backend server , the communication protocol of the backend server, the IP address and port of the browser client, and other information. In the implementation of the present invention, after the connection establishment module 402 establishes the TCP connection between the gateway and the backend server according to the handshake request message sent by the browser client, the update module 403 compares the IP address and port of the browser client with the IP address and port of the backend server. Associating the IP address with the port, and updating the association relationship into the message forwarding table. Therefore, the updated message forwarding table includes information such as the IP address and port of the backend server, the communication protocol of the backend server, and the IP address and port of the browser client, and can record the information of the browser client The IP address and port of the client are associated with the IP address and port of the back-end server. The significance of the association relationship recorded in the message forwarding table is that the first acquisition module 302 can obtain the IP address and port of the associated back-end server by querying the message forwarding table according to the IP address and port of the browser client, or vice versa. The second acquiring module 502 can acquire the IP address and port of the browser client associated with the backend server by querying the message forwarding table according to the IP address and port of the backend server.

In the gateway illustrated in FIG. 4 , the connection establishment module 402 may further include an analysis unit 601 and an establishment unit 602, such as the gateway provided by another embodiment of the present invention shown in FIG. 6 , wherein:

The parsing unit 601 is used to extract the IP address and port of the backend server included in the handshake request message;

The establishing unit 602 is configured to establish a TCP connection between the gateway and the back-end server according to the IP address and port of the back-end server.

Please refer to FIG. 7 , which shows a communication system provided by an embodiment of the present invention. For ease of description, only parts related to the embodiments of the present invention are shown. The communication system illustrated in accompanying drawing 7 includes a browser client 701, a backend server 703 and a gateway 702 in any example of accompanying drawing 3 to accompanying drawing 6, wherein:

The browser client 701 is used for sending a user request message through a transmission control protocol TCP connection with the gateway, and the user request message includes: the IP address and port of the browser client;

Gateway 702, configured to receive the user request message sent by the browser client through the TCP connection with the browser client; query the message forwarding table according to the IP address and port of the browser client in the user request message, Obtain the IP address and port of the back-end server associated with the IP address and port of the browser client; according to the IP address and port of the back-end server, connect the user request with the TCP connection with the back-end server The message is sent to the back-end server corresponding to the IP address and port of the back-end server;

The backend server 703 is configured to receive the user request message forwarded by the gateway.

In the communication system illustrated in accompanying drawing 7, the browser client 701 is also used to send a handshake request message through the TCP connection with the gateway 702, and the handshake request message includes the IP address and port of the backend server; The gateway 702 is also configured to receive the handshake request message sent by the browser client 701 through the TCP connection with the browser client 701; establish the connection with the backend server 703 according to the handshake request message Described TCP connection; The IP address of described browser client 701, port are associated with the IP address of described back-end server, port, and described association relation is updated in described message forwarding table.

In the communication system illustrated in FIG. 7 , the backend server 703 is also configured to send a request response message to the gateway 702 through a TCP connection with the gateway 702, and the request response message includes: the IP address of the backend server address and port; the gateway 702 is also used to receive the request response message sent by the backend server 703 through the TCP connection with the backend server; according to the IP address and the IP address of the backend server 703 in the request response message Port query the message forwarding table, obtain the IP address and port of the browser client 701 associated with the IP address and port of the back-end server 703; according to the IP address and port of the browser client 701, through the The TCP connection of the browser client 701 sends the request response message to the browser client corresponding to the IP address and port of the browser client 701; the browser client 701 is also used for: receiving The request response message sent by the gateway.

Fig. 8 is a schematic diagram of the physical connection (actual deployment) of the communication system illustrated in Fig. 7 . The gateway 702 of accompanying drawing 7 example can be WebSocket gateway, adopts WebSocket protocol to interact with browser client, through the TCP connection that browser client, back-end server establishes, forwards the real-time interaction between browser client and back-end server information.

From the implementation of the above-mentioned present invention, it can be known that because what the gateway and the browser client and the back-end server set up is a TCP long connection, on the one hand, the browser client can realize full-duplex communication with the back-end server, and the real-time information of the browser client is almost It can be sent to the back-end server in real time as soon as the release time is near, so the real-time performance is strong; on the other hand, the gateway is responsible for forwarding the user request message between the browser client and the back-end server through the TCP connection, and the main business logic and calculation are distributed in The browser client and back-end server, the gateway does not need to undertake the main business logic and calculation, and does not need to consume additional resources to realize the protocol conversion between HTTP and the back-end server, thus saving overhead.

It should be noted that the information interaction and execution process between the modules/units of the above-mentioned device are based on the same idea as the method embodiment of the present invention, and the technical effect it brings is the same as that of the method embodiment of the present invention. The specific content can be Refer to the descriptions in the method embodiments of the present invention, and details are not repeated here.

Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above-mentioned embodiments can be completed by instructing related hardware through a program, such as one or more or all of the following various methods:

Receive the user request message sent by the browser client through the transmission control protocol TCP connection between the gateway and the browser client, and the user request message includes: the IP address and the port of the browser client;

According to the IP address and port query message forwarding table of the browser client, obtain the IP address and port of the back-end server associated with the IP address and port of the browser client;

According to the IP address and port of the back-end server, the user request message is sent to the back-end server corresponding to the IP address and port of the back-end server through the TCP connection between the gateway and the back-end server.

Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above-mentioned embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, and the storage medium can include: Read Only Memory (ROM, Read Only Memory), Random Access Memory (RAM, Random Access Memory), disk or CD, etc.

The method, gateway, and communication system for direct communication between the browser client and the back-end server provided by the embodiment of the present invention have been described above in detail. In this paper, specific examples are used to illustrate the principle and implementation of the present invention. The above embodiments The description is only used to help understand the method of the present invention and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation and scope of application. In summary , the contents of this specification should not be construed as limiting the present invention.

Claims (8)

1. A method for direct communication between a browser client and a back-end server, characterized in that the method comprises: Receive the HTTP protocol-based handshake request message sent by the browser client through the pre-established TCP connection between the gateway and the browser client, and send a handshake success response message to the browser client, and the response message uses To indicate that the negotiation between the browser client and the gateway is successful; the handshake request message includes the IP address and port of the backend server; Establishing a TCP connection between the gateway and the backend server according to the handshake request message; Associating the IP address and port of the browser client with the IP address and port of the back-end server, and updating the association relationship into the message forwarding table; Receive the user request message based on the WebSocket protocol sent by the browser client through the pre-established transmission control protocol TCP connection between the gateway and the browser client, and the user request message includes: the IP address and port of the browser client; According to the IP address and port query message forwarding table of the browser client, obtain the IP address and port of the back-end server associated with the IP address and port of the browser client; According to the IP address and port of the back-end server, the user request message is sent to the back-end server corresponding to the IP address and port of the back-end server through the TCP connection between the gateway and the back-end server. 2. The method according to claim 1, characterized in that the method further comprises: Receive the request response message sent by the back-end server through the TCP connection between the gateway and the back-end server, and the request response message includes: the IP address and port of the back-end server; Query the message forwarding table according to the IP address and the port of the back-end server, and obtain the IP address and the port of the browser client associated with the IP address and the port of the back-end server; According to the IP address and port of the browser client, send the request response message to the browser corresponding to the IP address and port of the browser client through the pre-established TCP connection between the gateway and the browser client. server client. 3. The method according to claim 1, wherein said establishing the TCP connection between the gateway and the back-end server according to the handshake request message specifically comprises: Extracting the IP address and port of the backend server included in the handshake request message; Establish a TCP connection between the gateway and the back-end server according to the IP address and port of the back-end server. 4. A gateway, characterized in that the gateway comprises: The handshake message receiving module is used to receive the handshake request message based on the HTTP protocol sent by the browser client through the pre-established TCP connection between the gateway and the browser client, and send a successful handshake response to the browser client message, the response message is used to indicate that the negotiation between the browser client and the gateway is successful; the handshake request message includes the IP address and port of the backend server; A connection establishment module, configured to establish a TCP connection between the gateway and the backend server according to the handshake request message; An update module, configured to associate the IP address and port of the browser client with the IP address and port of the back-end server, and update the association relationship into the message forwarding table; The receiving module is configured to receive a user request message based on the WebSocket protocol sent by the browser client through the pre-established transmission control protocol TCP connection between the gateway and the browser client, and the user request message includes: the browser client IP address and port; The first acquisition module is used to query the message forwarding table according to the IP address and port of the browser client, and obtain the IP address and port of the back-end server associated with the IP address and port of the browser client; A sending module, configured to send the user request message to the back-end server corresponding to the IP address and port of the back-end server through the TCP connection between the gateway and the back-end server according to the IP address and port of the back-end server end server. 5. The gateway according to claim 4, further comprising: A response message receiving module, configured to receive a request response message sent by the back-end server through a TCP connection between the gateway and the back-end server, the request response message including: the IP address and port of the back-end server; The second acquisition module is used to query the message forwarding table according to the IP address and port of the back-end server, and obtain the IP address and port of the browser client associated with the IP address and port of the back-end server; A response message sending module, configured to send the request response message to the browser client through the pre-established TCP connection between the gateway and the browser client according to the IP address and port of the browser client The browser client corresponding to the IP address and port. 6. The gateway according to claim 4, wherein the connection establishment module specifically comprises: A parsing unit, configured to extract the IP address and port of the backend server included in the handshake request message; An establishing unit, configured to establish a TCP connection between the gateway and the back-end server according to the IP address and port of the back-end server. 7. A communication system, characterized in that, the communication system includes a browser client, a gateway and a backend server; The browser client is used to send a handshake request message based on the HTTP protocol through the pre-established TCP connection between the gateway and the browser client, and the handshake request message includes the IP address and port of the back-end server; The pre-established transmission control protocol TCP connection between the gateways sends a user request message based on the WebSocket protocol, and the user request message includes: the IP address and port of the browser client; The gateway is configured to receive a handshake request message based on the HTTP protocol sent by the browser client through a pre-established TCP connection between the gateway and the browser client, and send a handshake success response message to the browser client, The response message is used to indicate that the negotiation between the browser client and the gateway is successful; the handshake request message includes the IP address and port of the backend server; the gateway and the backend are established according to the handshake request message The TCP connection of server; The IP address of described browser client, port are associated with the IP address of described back-end server, port, and described association relation is updated in described message forwarding table; Through with browser client The TCP connection pre-established between receives the user request message based on the WebSocket protocol sent by the browser client; according to the IP address and port query message forwarding table of the browser client in the user request message, obtain the information related to the The IP address and the port of the back-end server associated with the IP address of the browser client and the port; According to the IP address and the port of the back-end server, the user request message is sent to the client with the TCP connection with the back-end server The IP address of the back-end server and the back-end server corresponding to the port; The backend server is configured to receive the user request message forwarded by the gateway. 8. The system of claim 7, wherein: The backend server is further configured to send a request response message to the gateway through a TCP connection with the gateway, and the request response message includes: the IP address and port of the backend server; The gateway is also used to receive the request response message sent by the back-end server through the TCP connection with the back-end server; query the message forwarding table according to the IP address and port of the back-end server in the request response message , obtain the IP address and port of the browser client associated with the IP address and port of the back-end server; according to the IP address and port of the browser client, through the pre-established TCP with the browser client Connect and send the request response message to the browser client corresponding to the IP address and port of the browser client; The browser client is further configured to: receive the request response message sent by the gateway.