WO2013097401A1

WO2013097401A1 - Method, gateway and communication system for browser client directly communicating with back-end server

Info

Publication number: WO2013097401A1
Application number: PCT/CN2012/075776
Authority: WO
Inventors: 关国锋; 朱建峰; 范家星
Original assignee: 华为技术有限公司
Priority date: 2011-12-30
Filing date: 2012-05-19
Publication date: 2013-07-04
Also published as: CN102546794A; CN102546794B

Abstract

The embodiments of the invention provide a method, gateway and communication system for a browser client directly communicating with a back-end server, in order to improve resource utilization while achieving end-to-end full-duplex communication between the browser client and the back-end server. The method comprises: receiving a user request message sent by the browser client through a transmission control protocol TCP connection between the gateway and the browser client; inquiring a 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 which are relevant to the IP address and port of the browser client; and sending 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 based on the IP address and port of the back-end server. The method provided by the invention achieves the protocol conversion between HTTP and the back-end server without consuming extra resources, thereby saves the expenses.

Description

TECHNICAL FIELD The present invention relates to the field of communications, and in particular, to a method, a gateway, and a communication system for a browser client to communicate with a backend server. BACKGROUND Real-time Web is a kind of Internet application in the Web2.0 system, and its typical representative mainly includes the social networking websites Facebook and Twitter. In real-time web applications such as social networking sites Facebook and twitter microblogging, the web server needs to actively push the user's friend's output (feed) information to the user in real time, so that users and their friends can generate and share anytime, anywhere. And consumer content. Other web applications such as monitoring, instant messaging, and real-time quoting systems also require the server to deliver changes in the background to the client in real time. It can be seen that the main features of real-time web applications are high interactivity and real-time, 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 real-time interaction between the browser and the back-end server to obtain real-time update information are based on Hypertext Transfer Protocol (HTTP) polling (Polling) and HTTP server-based "server push" technology (ie Comet technology) )Wait. The following is an example of HTTP-based polling, which illustrates a method for real-time interaction between a browser provided by a prior art and a back-end server to obtain real-time update information, including the following steps: S11, the browser connects to the web application server through the web, and is based on HTTP to the web. The application server sends an HTTP request; 512. The web application server receives and parses the browser's HTTP request, and converts the HTTP request into a call to the extended custom application service program;

513. The extended custom application service program parses the web application logic and protocol, and converts the web application logic and protocol into a standard API or message call to the backend server; and S14, the extended custom application service program invokes 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, establish a full-duplex TCP/IP connection to a backend server, and based on the corresponding message protocol interaction, obtaining update information from the backend server; S14, the browser requests the web server based on HTTP polling, or the web server uses

Comet technology sends the information to the browser for display. In the method for real-time interaction between the browser and the back-end server to obtain real-time update information, 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 separated. Therefore, the above prior art has the following drawbacks: 1) The resource waste is serious. 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 payloads. Therefore, frequent polling causes system bandwidth consumption and high latency;

2) The system has a performance bottle head. 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) the 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 implement two-way communication on two connections, so it is more expensive to use the server. Resources, end-to-end full-duplex communication cannot be achieved between the browser and the back-end server. Summary of the invention

Embodiments of the present invention provide a method, a gateway, and a communication system for a browser client to communicate with a backend server to achieve end-to-end full-duplex communication between a browser client and a backend server while improving resource utilization.

An embodiment of the present invention provides a method for a browser client to communicate with a backend server. The method includes: receiving, by a gateway, a TCP control connection of a browser client, a user request message sent by a browser client, where the user The request message includes: an IP address and a port of the browser client;

Obtaining an IP address and a port of the backend server associated with the IP address and port of the browser client according to the IP address and port query message forwarding table of the browser client;

And sending, according to the IP address and port of the backend server, the user request message to a backend server corresponding to the IP address and port of the backend server through a TCP connection of the gateway to the backend server.

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

a receiving module, configured to receive, by using a gateway, a transmission control protocol (TCP) connection of the browser client, a user request message sent by the browser client, where the user request message includes: an IP address and a port of the browser client; a first obtaining module, configured to obtain, according to an IP address and a port query message forwarding table of the browser client, an IP address and a port of a backend server associated with an IP address and a port of the browser client;

a sending module, configured to send, by using a TCP connection between the gateway and the backend server, the user request message to the IP address and port corresponding to the backend server according to an IP address and a port of the backend server End server. An embodiment of the present invention provides a communication system, where the communication system includes: a browser client, a gateway, and a backend server; and the browser client is configured to send a user request by using a TCP connection with the gateway of the gateway. a message, the user request message includes: an IP address and a port of the browser client; the gateway, configured to receive, by using the TCP connection with a browser client, the user request message sent by a browser client; The user request message in the browser client's IP address and port query message forwarding table, obtain the IP address and port of the backend server associated with the browser client's IP address and port; according to the IP of the backend server An address and a port, the user request message is sent to a backend server corresponding to an IP address and a port of the backend server by a TCP connection with the backend server; the backend server is configured to receive User request message forwarded by the gateway.

As can be seen from the above embodiments of the present invention, since the gateway establishes a TCP long connection with the browser client and the backend server, on the one hand, the browser client can implement full duplex communication with the backend server, and the real time information of the browser client Nearly the release time can be sent to the back-end server in real 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 server through the TCP connection. The user request message, the main business logic and calculation are distributed in 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 use additional resources to realize the protocol conversion between the HTTP and the back-end server. This saves overhead.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the prior art or the embodiments will be briefly described below. Obviously, the drawings in the following description are only the present invention. For some embodiments, other figures may also be obtained as those skilled in the art from these figures.

1 is a schematic flowchart of a method for directly connecting a browser client and a backend server according to an embodiment of the present invention;

2 is a schematic diagram of interaction between a browser client, a WebSocket gateway, and a backend server in a method in which a browser client and a backend server are directly connected according to an embodiment of the present invention;

3 is a schematic structural diagram of a gateway according to an embodiment of the present invention;

4 is a schematic structural diagram of a gateway according to another embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a gateway according to another embodiment of the present invention;

6 is a schematic structural diagram of a gateway according to another embodiment of the present invention;

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

FIG. 8 is a schematic diagram of a physical connection of a communication system according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, instead of All embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention are within the scope of the present invention.

1 is a schematic flowchart of a method for directly connecting a browser client and a backend server according to an embodiment of the present invention. The method illustrated in FIG. 1 is a communication protocol in which a browser is a web browser, a gateway is a Web socket gateway, a web socket gateway communicates with a browser client, and a back server is an HTML5 standard WebSocket protocol, and its execution is performed. The subject can be

WebSocket gateway, mainly includes steps:

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

Optionally, the method may further include: receiving, by using a TCP connection between the gateway and the browser client, a handshake request message sent by the browser client, where the handshake request message includes an IP address and a port of the backend server; The request message establishes a TCP connection between the gateway and the backend server; associates an IP address and a port of the browser client with an IP address and a port of the backend server, and updates the association relationship to the message Published. The establishing a TCP connection between the gateway and the backend server according to the handshake request message may be: extracting an IP address and a port of the backend server included in the handshake request message; according to the backend server The IP address and port establish a TCP connection between the gateway and the backend server.

In the embodiment of the present invention, when the user accesses the gateway, the browser client sends an application download request to the gateway, and downloads the web application from the gateway to the browser client. Thereafter, in order to obtain real-time information from the backend server, the user runs the web application on the browser client to request to establish a 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 the gateway to the gateway through the TCP connection, and the gateway receives the user request message through the TCP, for example, a subscription request, where the user request message includes the IP of the browser client. Information such as address and port indicates the source. 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 may 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 response message to the browser client, the negotiation between the browser client and the gateway is successful. The interaction between the browser client and the gateway is based on the WebSocket protocol. The WebSocket protocol message can pass. The TCP connection is transmitted. Since the header of the WebSocket protocol message is very small, that is, the overhead of the message is small, it is more efficient than the transmission of the HTTP protocol by the browser and the web application server in the prior art; on the other hand, due to the gateway and The communication protocol for the browser client and the backend server to communicate is the HTML5 standard WebSocket protocol instead of the private custom protocol, so the versatility is good.

The handshake request message received by the gateway may include information such as an IP address of the backend server, a port, and a communication protocol of the backend server, where the communication protocol of the backend server is an option in the handshake request message, that is, the handshake request message may be The communication protocol of the backend server is not included, and the communication protocol of the backend server can be preconfigured. The IP address of the backend server, the port, and the communication protocol of the backend server can be obtained by adding a cell to the handshake request message, as shown below, which is an HTTP Upgrade handshake of the newly added cell in the handshake request message. Example of a request message:

GET /realtime-info HTTP/1.1

Upgrade: WebSocket

Connection: Upgrade Host: mysite.com

Origin: http://mysite.com

DestHost: tcp:// myDestHostAddress: 9960

The new cell "DestHost: tcp: 〃 myDestHostAddress: 9960,," is used to declare the IP address of the backend server, the port, and the communication protocol of the backend server. In this embodiment, the backend server 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 an IP address and a port of the backend server included in the handshake request message, and then establishes a TCP connection of 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 an IP address and a 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 may update the message forwarding table. For example, after receiving the handshake request message and establishing a TCP connection of the gateway to the backend server, the gateway may update the message forwarding table, that is, record the IP address, port, and the backend server of the backend server. Communication protocol and information such as the IP address and port of the browser client. In the implementation of the present invention, after the gateway establishes a TCP connection between the gateway and the backend server according to the handshake request message sent by the browser client, the gateway sets the IP address of the browser client, the IP address of the port and the server of the backend server, and the port. Associating, and updating the association relationship to the message forwarding table. Therefore, the updated message forwarding table includes an IP address of the backend server, a port, a communication protocol of the backend server, and an IP address of the browser client. Information such as a port, and can record an IP address of the browser client, an IP address of the port and the backend server, and a port association relationship. The meaning of the message forwarding table recording these associations is that, according to the IP address and port of the browser client, by querying the message forwarding table, the IP address, port, or vice versa of the backend server associated with it can be obtained, according to the backend server. The IP address and port can be obtained by querying the message forwarding table to obtain the IP address and port of the browser client associated with it. It should be noted that since the backend server can broadcast the "establish connection request" message, the gateway can also establish the connection with the backend server after listening to the "establishment connection request" message of these broadcasts.

TCP connection, the present invention does not limit the manner in which the gateway establishes a TCP connection with the backend server.

S103. Send a user request message to the backend server corresponding to the IP address and port of the backend server by using a TCP connection between the gateway and the backend server according to the IP address and port of the backend 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, the IP layer) below the application layer, the gateway can parse out the IP address of the back-end server included in the request message, the port, and the communication protocol of the back-end server. Therefore, the gateway can query the update. Message forwarding table, ie, the gateway is based on the browser client

The IP address, port query message forwarding table, obtains the IP address and port of the backend server associated with the browser client's IP address and port. And sending, according to the obtained backend server IP address and port, the request message to a backend server corresponding to the IP address and port of the backend server, thereby implementing the gateway and the A TCP connection of the backend server, forwarding a message of interaction between the browser client and the backend server.

Optionally, the method provided by the embodiment of the present invention may further include: using a gateway and a backend server The TCP connection receives the request response message sent by the backend server, where the request response message includes: an IP address and a port of the backend server; and querying the message forwarding table according to the IP address and port of the backend server, Obtaining an IP address and port of a browser client associated with the IP address and port of the backend server; and according to the IP address and port of the browser client, the request is made through a TCP connection between the gateway and the browser client The response message is sent to a browser client corresponding to the IP address and port of the browser client.

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

Due to the network protocol layer (for example, the IP layer) below the application layer, the gateway can parse out the IP address of the backend server included in the request response message, the communication protocol of the port and the backend server, etc., so the gateway can query the location. The updated message forwarding table, that is, the gateway queries the updated message forwarding table according to the IP address and port of the backend server, and obtains the IP of the browser client associated with the IP address and port of the backend server. Address, port. Then, the request response message is forwarded to a browser client corresponding to the IP address and port of the browser client according to the acquired IP address and port of the browser client, thereby implementing the establishment established by the front gateway. The TCP connection of the browser client forwards a message exchanged between the browser client and the backend server.

The method for the direct connection between the browser client and the backend server provided by the embodiment of the present invention can be seen that, since the gateway and the browser client and the backend server can establish a TCP long connection, on the one hand, the browser client can be followed by The end server implements full-duplex communication, and the real-time information of the browser client The release time can be sent to the backend server in real time, so the real-time performance is strong; on the other hand, the gateway passes

The TCP connection is responsible for forwarding the user request message sent by the browser client to the back-end server. The main business logic and calculation are distributed among 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 enable protocol conversion between HTTP and the backend server, thus saving overhead.

The following is an interaction between the browser client, the WebSocket gateway, and the backend server, and the browser client sends a message subscription request to the WebSocket gateway through the established TCP connection to request to subscribe to the new message as an example, further explaining the browser and the latter. For the method of direct server connection, please refer to FIG. 2. The interaction between the browser client, the WebSocket gateway and the backend server mainly includes:

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

The web application download request is that when the user accesses the gateway, the browser client sends the access request to the WebSocket gateway.

5202, The WebSocket gateway downloads the web application to the browser client.

5203, the browser client runs the web application.

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.

At the beginning of the communication, the browser client can send a handshake request message based on the HTTP format to the gateway to request to negotiate a communication protocol with the gateway. The handshake request message includes an IP address and a port of the backend server, and optionally, a communication protocol of the backend server, and the like. The IP address and port of the backend server may optionally include information such as a communication protocol of the backend server. In order to add a cell to the handshake request message, the following is an example of an HTTP Upgrade handshake request message for adding a new cell in the handshake request message:

GET /realtime-info HTTP/1.1

Upgrade: WebSocket

Connection: Upgrade

Host: mysite.com

Origin: http://mysite.com

DestHost: tcp:// myDestHostAddress: 9960

The new cell "DestHost: tcp: 〃 myDestHostAddress: 9960," is used to declare the IP address of the backend server, the port, and the communication protocol of the backend server. In this embodiment, the backend server The communication protocol is TCP.

5206. The WebSocket gateway parses the handshake request message.

The gateway resolves the handshake request message, extracts the IP address and port of the backend server included therein, and then establishes a TCP connection between the gateway and the backend server according to the IP address and port of the backend server, including:

5207. The WebSocket gateway sends a TCP connection establishment request to the backend server.

5208, the backend server returns a response message to the WebSocket gateway.

5209, WebSocket Gateway updates the message forwarding table.

That is, the WebSocket gateway records the IP address of the backend server, the port, 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 The IP address, port, and the backend server of the backend server The communication protocol and the information such as the IP address and port of the browser client, and the IP address of the browser client, the IP address of the port and the backend server, and the port association relationship may be recorded. In this implementation, the gateway establishes a TCP connection between the gateway and the backend server according to the handshake request message sent by the browser client, and associates the IP address and port of the browser client with the IP address and port of the backend server, and Updating the association relationship to the message forwarding table. Therefore, the updated message forwarding table includes information such as an IP address of the backend server, a port, a communication protocol of the backend server, and an IP address and port of the browser client, and includes the browser client. The IP address and port are associated with the IP address and port of the backend server. The meaning of the message forwarding table recording these associations is that, according to the IP address and port of the browser client, by querying the message forwarding table, the IP address, port, or vice versa of the backend server associated with it can be obtained, according to the backend server. The IP address and port can be obtained by querying the message forwarding table to obtain the IP address and port of the browser client associated with it.

5210. 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 successfully establishes a TCP connection with the browser client and the backend server, and subsequent message interaction between the browser client and the backend server can be performed through the TCP connection. .

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

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

S212. The WebSocket gateway parses the message subscription request.

The network protocol layer (for example, the IP layer) below the application layer, the WebSocket gateway can parse out The message subscription request includes information about the IP address of the backend server, the port, and the communication protocol of the backend server. Therefore, the WebSocket gateway can query the updated message forwarding table in step S209, that is, the WebSocket gateway browses according to the message. The IP address and port of the client, query the message forwarding table, and obtain the IP address and port of the backend server associated with the browser client.

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 obtained IP address and port of the backend server.

5214. 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 contain information such as the communication protocol of the backend server.

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

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

The update message is the message requested by the message subscription request.

5217. The WebSocket gateway parses a response message corresponding to the message subscription request.

Due to the network protocol layer (for example, the IP layer) below the application layer, the WebSocket gateway can parse the IP address, port, and backend server of the backend server backend server included in the request response message corresponding to the message subscription request. The information such as the communication protocol, 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 backend server, and obtains the information forwarding table. Server The IP address and port of the associated browser client.

5218. The WebSocket gateway forwards the update message to the browser client.

The WebSocket gateway queries the corresponding browser communication connection through the IP address and port of the browser client according to the obtained IP address and port of the browser client associated with the backend server, and sends the backend server to the WebSocket in step S216. The update message sent by the gateway is forwarded to the browser client corresponding to the IP address and port of the browser client.

5219. The browser client sends a response message corresponding to the update message to the WebSocket gateway. The response message is an acknowledgment of the update message forwarded by the WebSocket gateway.

5220. The WebSocket gateway sends a response message corresponding to the update message to the backend server. Referring to FIG. 3, it is a schematic diagram of a gateway structure provided by an embodiment of the present invention. For the convenience of description, only parts related to the embodiment of the present invention are shown. The gateway illustrated in Figure 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 FIG. 3 includes a receiving module 301, a first obtaining module 302, and a transmitting module 303, where:

The receiving module 301 is configured to receive, by using a gateway and a transmission control protocol TCP connection of the browser client, a user request message sent by the browser client, where the user request message includes: an IP address and a port of the browser client;

The first obtaining module 302 is configured to query the message forwarding table according to the IP address and port of the browser client, and obtain an IP address and a port of the backend server associated with the IP address and port of the browser client.

a sending module 303, configured to use, according to the IP address and port of the backend server, by using a gateway The TCP connection of the backend server sends the user request message to a backend server corresponding to the IP address and port of the 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. Because the network protocol layer (for example, the IP layer) below the application layer can parse the IP address of the back-end server included in the request message, the port, and the communication protocol of the back-end server, the first obtaining module 302 can query The updated message forwarding table, that is, the first obtaining module 302 obtains the IP of the backend server associated with the IP address and port of the browser client according to the IP address of the browser client and the port query message forwarding table. Address and port. Then, the sending module 303 sends the request message to the backend server corresponding to the IP address and port of the backend server according to the obtained backend server IP address and port, thereby implementing the gateway and the A TCP connection of the backend server, forwarding a message of interaction between the browser client and the backend server.

According to the gateway provided by the foregoing embodiment of the present invention, since the gateway and the browser client and the backend server can establish a TCP long connection, on the one hand, the browser client can implement full duplex communication with the backend server, and the browser The real-time information of the client can be sent to the back-end server in real time near 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 main Business logic and calculations are distributed across browser clients and back-end servers. The gateway does not need to undertake major business logic and calculations, and does not require additional resources to implement protocol conversion between HTTP and back-end servers, thus saving overhead.

It should be noted that, in the implementation manner of the foregoing gateway, the division of each functional module is only an example. In actual applications, the foregoing functional allocation may be different according to requirements, such as configuration requirements of corresponding hardware or convenience of implementation of software. The functional module is completed, that is, the internal structure of the gateway is divided. Different functional modules to complete all or part of the functions described above. Moreover, in practical applications, the corresponding functional modules in this embodiment may be implemented by corresponding hardware, or may be executed by corresponding hardware. For example, the foregoing receiving module may have the foregoing The transmission control protocol TCP connection of the browser client receives the hardware of the user request message sent by the browser client, such as a receiver, or a general processor or other hardware device capable of executing the corresponding computer program to perform the foregoing functions; The first obtaining module may be configured to execute the foregoing to forward the table according to the IP address and port query message 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. The functional hardware, such as the first acquirer, may also be a general processor or other hardware device capable of executing a corresponding computer program to perform the aforementioned functions (the various embodiments provided herein may apply the above described principles). The gateway illustrated in FIG. 3 may further include a handshake message receiving module 401, a connection establishing module 402, and an update module 403. As shown in FIG. 4, a gateway provided by another embodiment of the present invention, wherein:

The handshake message receiving module 401 is configured to receive, by using a TCP connection between the gateway and the browser client, a handshake request message sent by the browser client, where the handshake request message includes an IP address and a 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 may 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 response message to the browser client, the negotiation between the browser client and the gateway is successful. The interaction between the browser client and the gateway is based on the WebSocket protocol. The message can be transmitted over the TCP connection. Since the header of the WebSocket protocol message is very small, that is, the overhead of the message is small, it is more efficient than the transmission of the HTTP protocol by the browser and the web application server in the prior art; on the other hand, due to the gateway and The communication protocol for the browser client and the backend server to communicate is the HTML5 standard WebSocket protocol instead of the private custom protocol, so the versatility is good.

The handshake request message received by the handshake message receiving module 401 may include information such as an IP address of the backend server, a port, and a communication protocol of the backend server, where the communication protocol of the backend server is an option in the handshake request message, that is, 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 pre-configured. The IP address of the backend server, the port, and the communication protocol of the backend server can be obtained by adding a cell to the handshake request message, as shown below, which is an HTTP Upgrade handshake of the newly added cell in the handshake request message. Example of a request message:

GET /realtime-info HTTP/1.1

Upgrade: WebSocket

Connection: Upgrade

Host: mysite.com

Origin: http://mysite.com

DestHost: tcp:// myDestHostAddress: 9960

The new cell "DestHost: tcp: 〃 myDestHostAddress: 9960,," is used to declare the IP address of the backend server, the port, and the communication protocol of the backend server. In this embodiment, the backend server The communication protocol is TCP. a connection establishing module 402, configured to establish, according to the handshake request message, a TCP connection between the gateway and the backend server;

The update module 403 is configured to associate an IP address and a port of the browser client with an IP address and a port of the backend server, and update the association relationship into the message forwarding table. The gateway illustrated in FIG. 3 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 gateway provided by another embodiment of the present invention, where: the response message receiving module 501 Receiving a request response message sent by the backend server by using a TCP connection between the gateway and the backend server, where the request response message includes: an IP address and a port of the backend server;

The second obtaining module 502 is configured to query the message forwarding table according to the IP address and port of the backend server, and obtain an IP address and a port of a browser client associated with an IP address and a port of the backend server;

The response message sending module 503 is configured to send the request response message to the IP address and port of the browser client by using a TCP connection between the gateway and the browser client according to the IP address and port of the browser client. The 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, and the functions are as described above, and details are not described herein again.

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 may update the message forwarding table. For example, after the connection establishment module 402 receives the handshake request message and establishes a TCP connection of the gateway to the backend server, the update module 403 The message forwarding table may be updated, that is, the IP address of the backend server, the port, the communication protocol of the backend server, and the IP address and port of the browser client are recorded. In the implementation of the present invention, after the connection establishment module 402 establishes a TCP connection between the gateway and the backend server according to the handshake request message sent by the browser client, the update module 403 sets the IP address, port and backend server of the browser client. The IP address, port association, and update the association relationship to the message forwarding table. Therefore, the updated message forwarding table includes information such as an IP address of the backend server, a port, a communication protocol of the backend server, and an IP address and port of the browser client, and may record the browser client. The IP address and port of the terminal are associated with the IP address and port of the backend server. The meaning of the association relationship recorded by the message forwarding table is that the first ear module 302 can obtain the IP address and port of the backend server associated with it by querying the message forwarding table according to the IP address and port of the browser client. Or vice versa, the second obtaining module 502 can obtain the IP address and port of the browser client associated with the message forwarding table according to the IP address and port of the backend server.

In the gateway illustrated in FIG. 4, the connection establishing module 402 may further include a parsing unit 601 and an establishing unit 602, such as the gateway provided by another embodiment of the present invention, as shown in FIG.

The parsing unit 601 is configured to extract an IP address and a 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 backend server according to the IP address and port of the backend server.

Referring to FIG. 7, a communication system provided by an embodiment of the present invention. For the convenience of description, only parts related to the embodiment of the present invention are shown. The communication system illustrated in FIG. 7 includes a browser client 701, a backend server 703, and a gateway 702 of any of FIGS. 3 through 6, wherein: The browser client 701 is configured to send, by using a transmission control protocol TCP connection with the gateway, a user request message, where the user request message includes: an IP address and a port of the browser client;

The gateway 702 is configured to receive, by using the TCP connection with the browser client, the user request message sent by the browser client, according to the IP address and the port query message forwarding table of the browser client in the user request message, Obtaining an IP address and a port of the backend server associated with the IP address and port of the browser client; according to the IP address and port of the backend server, the user request is made through a TCP connection with the backend server Sending a message to a backend server corresponding to the IP address and port of the backend server;

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

In the communication system illustrated in FIG. 7, the browser client 701 is further configured to send a handshake request message by using a TCP connection with the gateway 702, where the handshake request message includes an IP address and a port of the backend server; The gateway 702 is further configured to receive, by using a TCP connection with the browser client 701, the handshake request message sent by the browser client 701; and establish a session with the backend server 703 according to the handshake request message. Describe the TCP connection; associate the IP address and port of the browser client 701 with the IP address and port of the backend server, and update the association relationship to the message forwarding table.

In the communication system illustrated in FIG. 7, the backend server 703 is further configured to send a request response message to the gateway 702 through a TCP connection with the gateway 702, where the request response message includes: an IP of the backend server The gateway 702 is further configured to receive, by using a TCP connection with the backend server, a request response message sent by the backend server 703; according to the IP address of the backend server 703 in the request response message The port queries the message forwarding table, obtains the location The IP address of the backend server 703 and the IP address and port of the browser client 701 associated with the port; according to the IP address and port of the browser client 701, through the browser client 701 The TCP connection sends the request response message to a browser client corresponding to the IP address and port of the browser client 701; the browser client 701 is further configured to: receive the Request response message.

Figure 8 is a schematic diagram of the physical connection (actual deployment) of the communication system illustrated in Figure 7. The gateway 702 of the example shown in FIG. 7 may be a WebSocket gateway, which interacts with a browser client by using a WebSocket protocol, and forwards the real-time interaction between the browser client and the back-end server through a TCP connection established by the browser client and the back-end server. information.

As can be seen from the implementation of the present invention, since the gateway establishes a TCP long connection with the browser client and the backend server, on the one hand, the browser client can implement full duplex communication with the backend server, and the real time information of the browser client The release time can be sent to the back-end server in real 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 are distributed in the Browser clients and back-end servers, the gateway does not need to undertake the main business logic and calculations, without the need to spend additional resources to achieve protocol conversion between HTTP and back-end servers, thus saving overhead.

It should be noted that the information interaction, the execution process, and the like between the modules/units of the foregoing device are the same as the embodiment of the method of the present invention. Reference is made to the description in the method embodiment of the present invention, and details are not described herein again.

One of ordinary skill in the art will appreciate that all or part of the various steps of the above-described embodiments may be performed by a program to instruct related hardware, such as one or more or all of the following various methods: The user request message sent by the browser client is received by the gateway and the transmission control protocol TCP connection of the browser client, where the user request message includes: an IP address and a port of the browser client;

A person skilled in the art may understand that all or part of the various steps of the foregoing embodiments may be completed by a program instructing related hardware. The program may be stored in a computer readable storage medium, and the storage medium may include: Read only memory (ROM, Read Only Memory), random access memory (RAM), disk or optical disk.

The method and gateway type of the browser client and the back-end server provided by the embodiment of the present invention are described above. The description of the above embodiments is only for helping to understand the method and core idea of the present invention; The present invention is not limited by the scope of the present invention, and the details of the present invention are not limited by the scope of the present invention.

Claims

Rights request

A method for directly connecting a browser client to a backend server, wherein the method comprises:

And receiving, by the gateway and the browser client, a TCP connection, a user request message sent by the browser client, where the user request message includes: an IP address and a port of the browser client;

The method according to claim 1, wherein the method further comprises: receiving, by using a TCP connection between the gateway and the browser client, a handshake request message sent by the browser client, where the handshake request message includes a backend server IP address and port;

Establishing a TCP connection between the gateway and the backend server according to the handshake request message; associating an IP address and a port of the browser client with an IP address and a port of the backend server, and updating the association relationship to The message forwarding table.

The method according to claim 1 or 2, wherein the method further comprises: receiving, by using a TCP connection between the gateway and the backend server, a request response message sent by the backend server, where the request response message includes : the IP address and port of the backend server;

Querying the message forwarding table according to the IP address and port of the backend server, and obtaining an IP address and a port of a browser client associated with the IP address and port of the backend server; And sending, according to the IP address and port of the browser client, the request response message to a browser client corresponding to the IP address and port of the browser client through a TCP connection between the gateway and the browser client.

The method according to claim 2, wherein the establishing a TCP connection between the gateway and the backend server according to the handshake request message specifically includes:

Extracting an IP address and a port of the backend server included in the handshake request message; establishing a TCP connection between the gateway and the backend server according to an IP address and a port of the backend server.

A gateway, wherein the gateway includes:

The receiving module is configured to receive, by using a gateway, a transmission control protocol TCP connection of the browser client, a user request message sent by the browser client, where the user request message includes: an IP address and a port of the browser client;

a first obtaining module, configured to obtain, according to the IP address of the browser client and the port query message, the IP address and port of the backend server associated with the IP address and port of the browser client;

a sending module, configured to send, by using a TCP connection between the gateway and the backend server, the user request message to the IP address and port corresponding to the backend server according to an IP address and a port of the backend server End server.

The gateway according to claim 5, wherein the gateway further comprises:

The handshake message receiving module is configured to receive, by using a TCP connection between the gateway and the browser client, a handshake request message sent by the browser client, where the handshake request message includes an IP address and a port of the backend server; a connection establishing module, configured to establish, according to the handshake request message, a TCP connection between the gateway and the backend server;

And an update module, configured to associate an IP address and a port of the browser client with an IP address and a port of the backend server, and update the association relationship into the message forwarding table.

The gateway according to claim 5 or 6, wherein the gateway further comprises: a response message receiving module, configured to receive a request response message sent by the backend server by using a TCP connection between the gateway and the backend server The request response message includes: an IP address and a port of the backend server;

a second obtaining module, configured to query the message forwarding table according to an IP address and a port of the backend server, and obtain an IP address and a port of a browser client associated with an IP address and a port of the backend server;

a response message sending module, configured to send, by using a TCP connection between the gateway and the browser client, the request response message to an IP address and a port corresponding to the browser client according to an IP address and a port of the browser client Browser client.

The gateway according to claim 6, wherein the connection establishing module specifically includes: a parsing unit, configured to extract an IP address and a port of the backend server included in the handshake request message;

And a 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 backend server.

9. A communication system, characterized in that the communication system comprises a browser client, a gateway and a backend server;

The browser client, configured to send by using a transmission control protocol TCP connection with the gateway a user request message, the user request message includes: an IP address and a port of the browser client, and the gateway is configured to receive, by using the TCP connection with a browser client, the user request message sent by a browser client Obtaining an IP address and a port of the backend server associated with the IP address and port of the browser client according to the IP address and port query message forwarding table of the browser client in the user request message; according to the backend server The IP address and port, the user request message is sent to a backend server corresponding to the IP address and port of the backend server through a TCP connection with the backend server;

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

10. The system of claim 9 wherein:

The browser client is further configured to send a handshake request message by using a TCP connection with the gateway, where the handshake request message includes an IP address and a port of the backend server;

The gateway is further configured to receive, by using a TCP connection with the browser client, the handshake request message sent by the browser client, and establish, according to the handshake request message, the TCP connection with the backend server; Associating the IP address and port of the browser client with the IP address and port of the backend server, and updating the association relationship to the message forwarding table.

11. A system according to claim 9 or 10, characterized in that

The backend server is further configured to send a request response message to the gateway by using a TCP connection with the gateway, where the request response message includes: an IP address and a port of the backend server;

The gateway is further configured to receive a request response message sent by the backend server by using a TCP connection with the backend server; query the message forwarding table according to an IP address and a port of the backend server in the request response message. Obtaining the IP address and port of the browser client associated with the IP address and port of the backend server; and according to the IP address and port of the browser client, The TCP connection of the browser client sends the request response message to a 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.