CN104243188A - Searching method and device for network nodes not supporting WebSocket data forwarding - Google Patents

Abstract

The present invention is applicable to the communication field, and particularly relates to a method and device for searching network nodes that do not support WebSocket. The method includes: receiving an instruction to search for a network node that does not support WebSocket data forwarding; The two terminals establish a routing link for transmitting WebSocket data; if the routing link is connected, record the network node on the routing link as a network node that can support WebSocket data forwarding; the default may not support WebSocket data forwarding Delete the network nodes that can support WebSocket data forwarding from the network node database. The implementation process of the embodiment of the present invention is simple, and as the number of tests increases, the network node library that does not support WebSocket data forwarding will become more and more accurate.

Description

Method and device for searching network nodes that do not support WebSocket data forwarding

technical field

The invention belongs to the communication field, and in particular relates to a method and a device for searching network nodes not supported by WebSocket.

Background technique

At present, HTTP (English full name: hypertext transport protocol, Chinese full name: hypertext transfer protocol) in browsers is generally used to realize one-way communication; comet ("server push" technology based on HTTP long connection) can be used to a certain extent The two-way communication is simulated on the Internet, but the efficiency is low, and the server needs better support; the socket and xmlsocket in the flash can realize the real two-way communication, and these two functions can be used in javascript through flex, Ajax or bridge.

WebSocket protocol is a new protocol of HTML5. With the improvement of users' requirements for two-way real-time communication on web pages, WebSocket protocol will definitely become a basic protocol of HTML5 in the future. If there is a proxy server on the network that cannot forward or deliver WebSocket data packets, it will It will bring great trouble to WebSocket-based applications. Whether it is on the Internet or in the intranet, there are often a large number of proxy servers used. It is very difficult and almost impossible to check whether WebSocket is supported one by one. Therefore, how to effectively find out which ones cannot support The proxy server for WebSocket data forwarding will become a more important issue.

Contents of the invention

The purpose of the embodiments of the present invention is to provide a method for searching network nodes that do not support WebSocket data forwarding, so as to solve the problem of difficulty in finding network nodes that cannot support WebSocket data forwarding in the prior art.

The first aspect of the present invention provides a method for searching a network node that does not support WebSocket data forwarding, and the method includes the following steps:

Receive instructions to find network nodes that do not support WebSocket data forwarding;

According to the instruction, a routing link for transmitting WebSocket data is established between the first terminal and the second terminal;

judging whether the routing link is connected;

If the routing link is connected, record that the network node on the routing link is a network node that can support WebSocket data forwarding, and the network node on the routing link includes the network node that the routing link passes through and is located at the first all network nodes between a terminal and said second terminal;

The network node that can support WebSocket data forwarding is deleted from the preset network node library that may not support WebSocket data forwarding.

In a first possible implementation manner of the first aspect, the method further includes:

If the routing link is disconnected, determine whether the network node on the routing link is a recorded network node that can support WebSocket data forwarding;

If the network node on the routing link is not a recorded network node that can support WebSocket data forwarding, store the network node on the routing link into the preset network node library that may not support WebSocket data forwarding Or form the network nodes on the routing link into a network node library that may not support WebSocket data forwarding.

In the second possible implementation manner of the first aspect, the first terminal includes a client with a browser, the second terminal includes a server supporting WebSocket protocol for communication, and according to the instruction, in Before the step of establishing a routing link for transmitting WebSocket data between the first terminal and the second terminal, the method further includes:

Detecting whether the browser of the client is a browser supporting WebSocket protocol communication;

If the browser of the client is a browser that does not support WebSocket protocol communication, then end the search;

If the browser of the client is a browser supporting WebSocket protocol communication, then execute the step of establishing a routing link for transmitting WebSocket data between the first terminal and the second terminal according to the instruction.

In a third possible implementation of the first aspect, before the first terminal and the second terminal establish a routing link for transmitting WebSocket data according to the instruction in the step, the method further includes:

Detecting whether the first terminal and the second terminal can be connected through the POST mode of the hypertext transfer protocol, if not, then judging the link for transmitting the POST request between the first terminal and the second terminal Whether the network node on is a recorded network node that can support WebSocket data forwarding;

If the network node on the link that transmits the POST request is not a recorded network node that can support WebSocket data forwarding, store the network node on the link that transmits the POST request into the preset may not support WebSocket A network node library for data forwarding.

In a fourth possible implementation manner of the first aspect, the method further includes:

The network nodes that are recorded as being capable of supporting WebSocket data forwarding are stored in a database of network nodes capable of supporting WebSocket data forwarding.

In a second aspect, a device for searching a network node that does not support WebSocket data forwarding is provided, and the device includes:

The receiving unit is used to receive an instruction to find a network node that does not support WebSocket data forwarding;

A routing link establishment unit, configured to establish a routing link for transmitting WebSocket data between the first terminal and the second terminal according to the instruction received by the receiving unit;

a first judging unit, configured to judge whether the routing link established by the routing link establishing unit is connected;

A recording unit, configured to record that the network node on the routing link is a network node that can support WebSocket data forwarding if the routing link judged by the first judging unit is connected, and the network node on the routing link The nodes include all network nodes located between the first terminal and the second terminal through which the routing link passes;

The deleting unit is configured to delete the network node capable of supporting WebSocket data forwarding recorded by the recording unit from the preset network node library that may not support WebSocket data forwarding.

In a first possible implementation manner of the second aspect, the device further includes:

The second judging unit is configured to judge whether the network node on the routing link is a recorded network node that can support WebSocket data forwarding if the routing link judged by the first judging unit is disconnected;

The first network node storage unit is used to save the network node on the routing link if the network node on the routing link judged by the second judging unit is not a recorded network node that can support WebSocket data forwarding Enter the preset network node library that may not support WebSocket data forwarding or configure the network nodes on the routing link to form a network node library that may not support WebSocket data forwarding.

In a second possible implementation of the second aspect, the first terminal includes a client with a browser, the second terminal includes a server that supports the WebSocket protocol to be accessed, and the device further includes:

The first detection unit is used to detect whether the browser of the client is a browser that supports WebSocket protocol communication; if the browser of the client is a browser that does not support WebSocket protocol communication, then end the search; if the client's If the browser is a browser supporting WebSocket protocol communication, then transfer to the routing link establishment unit for execution.

In a third possible implementation manner of the second aspect, the device further includes:

The second detection unit is used to detect whether the first terminal and the second terminal can be connected through the POST mode of the hypertext transfer protocol, and if not, judge the connection between the first terminal and the second terminal Whether the network node of the link that transmits the POST request is a recorded network node that can support WebSocket data forwarding;

The second network node storage unit is used to store the network node on the routing link into the stored network node if the network node on the link transmitting the POST request is not a recorded network node that can support WebSocket data forwarding. The preset network node library that may not support WebSocket data forwarding.

In a fourth possible implementation manner of the second aspect, the device further includes:

The third network node storage unit is configured to store the record as a network node capable of supporting WebSocket data forwarding into a database of network nodes capable of supporting WebSocket data forwarding.

A method for searching a network node that does not support WebSocket data forwarding is provided in a third aspect, wherein the method includes the following steps:

Receive instructions to find network nodes that do not support WebSocket data forwarding;

According to the instruction, initiate a connection request for establishing a routing link for transmitting WebSocket data to the second terminal, so as to establish a routing link for transmitting WebSocket data with the second terminal;

judging whether the routing link is connected;

If the routing link is connected, record the network node of the routing link as a network node that can support WebSocket data forwarding, and the network node on the routing link includes that the routing link is connected to the second terminal All network nodes that establish connections between;

The network node that can support WebSocket data forwarding is deleted from the preset network node library that may not support WebSocket data forwarding.

In the first possible implementation manner of the third aspect, the second terminal is a server, and the step of judging whether the routing link is connected is specifically:

Invoke the traceroute service of the server to obtain the network nodes of the routing link, and determine whether the routing link is connected.

In a second possible implementation of the third aspect, the connection request is sent by the browser, and before the step initiates a connection request to the second terminal to establish a routing link for transmitting WebSocket data according to the instruction, the The method also includes:

Detect whether the browser supports the data access of the WebSocket protocol, and if it does not support the data access of the WebSocket protocol, end the search;

If the browser supports data access of the WebSocket protocol, perform the step of initiating a connection request to the second terminal to establish a routing link for transmitting WebSocket data.

In a third possible implementation of the third aspect, the connection request is sent by the browser, and before the step initiates a connection request to the server to establish a routing link for transmitting WebSocket data according to the instruction, the method Also includes:

Detect whether the browser and the server can be connected through the POST mode of the hypertext transfer protocol. If not, determine whether the network node of the link transmitting the POST request between the browser and the server is a recorded one that can support WebSocket data forwarding network node;

If the network node of the link transmitting the POST request is not a recorded network node capable of supporting WebSocket data forwarding, store the network node of the link transmitting the POST request into the database of network nodes that may not support WebSocket data forwarding.

In the fourth aspect, a device for searching a network node that does not support WebSocket data forwarding is provided, and the device includes:

A receiving module, configured to receive an instruction to find a network node that does not support WebSocket data forwarding;

A connection request sending module, configured to initiate a connection request to the second terminal to establish a routing link for transmitting WebSocket data according to the instruction received by the receiving module, so as to establish a routing link for transmitting WebSocket data with the second terminal;

A first judging module, configured to judge whether the routing link is connected;

The first recording module is configured to record the network nodes on the routing link as network nodes that can support WebSocket data forwarding if the routing link is connected, and the network nodes on the routing link include the routing link The paths are all network nodes establishing connections with the second terminal;

A deletion module, configured to delete the network node that can support WebSocket data forwarding from the preset network node library that may not support WebSocket data forwarding.

In the first possible implementation manner of the fourth aspect, the second terminal is a server, and the first obtaining and judging module is specifically configured to invoke the traceroute service of the server to obtain the network node of the route link, and judge the route Whether the link is connected.

In a second possible implementation manner of the fourth aspect, the connection request is sent by a browser, and the device further includes:

The first detection module is used to detect whether the browser supports the data access of the WebSocket protocol, if it does not support the data access of the WebSocket protocol, then ends the search, and if the browser supports the data access of the WebSocket protocol, then forwards to the connection request sending module implement.

In a third possible implementation manner of the fourth aspect, the connection request is sent by a browser, and the device further includes:

The second detection module is used to detect whether the browser and the server can be connected through the POST mode of the hypertext transfer protocol, if not, then judge whether the network node of the link transmitting the POST request between the browser and the server is recorded A network node that can support WebSocket data forwarding;

The first network node storage module is used to store the network node of the link that transmits the POST request into the network node that may not A network node library that supports WebSocket data forwarding.

A fifth aspect provides a terminal device, which includes the device for finding a network node that does not support WebSocket data forwarding according to any one of the fourth aspect.

In the sixth aspect, a method for searching a network node that does not support WebSocket data forwarding is provided, and the method includes the following steps:

receiving a connection request sent by the first terminal to establish a routing link for transmitting WebSocket data;

Establishing a routing link for transmitting WebSocket data with the first terminal according to the request;

judging the connectivity of the routing link;

If the routing link is connected, record the network node of the routing link as a network node that can support WebSocket data forwarding,

The network node that can support WebSocket data forwarding is deleted from the preset network node library that may not support WebSocket data forwarding.

In a first possible implementation manner of the sixth aspect, the method further includes:

If the routing link is disconnected, determine whether the network node on the routing link is a recorded network node that can support WebSocket data forwarding;

If the network nodes on the routing link are not recorded network nodes that can support WebSocket data forwarding, store the network nodes on the routing link in a network node database that may not support WebSocket data forwarding.

In a second possible implementation manner of the sixth aspect, the method further includes:

The network nodes that are recorded as being capable of supporting WebSocket data forwarding are stored in a database of network nodes capable of supporting WebSocket data forwarding.

In the seventh aspect, a device for searching a network node that does not support WebSocket data forwarding is provided, and the device includes:

A connection request receiving module, configured to receive a connection request sent by the first terminal to establish a routing link for transmitting WebSocket data;

A routing link establishing module, configured to establish a routing link for transmitting WebSocket data with the first terminal according to the request received by the connection request receiving module;

A second judging module, configured to judge the connectivity of the routing link established by the routing link establishing module;

The second recording module is used for judging by the second judging module that if the routing link is connected, record the network node of the routing link as a network node that can support WebSocket data forwarding;

The second deletion module is configured to delete the network node that can support WebSocket data forwarding from the preset network node library that may not support WebSocket data forwarding.

In a first possible implementation manner of the seventh aspect, the device further includes:

A network node judging module, used to judge whether the network node of the routing link is a recorded network node that can support WebSocket data forwarding if the routing link is disconnected;

The second network node storage module is used to store the network node on the routing link into a network node that may not support WebSocket data if the network node on the routing link is not a recorded network node that can support WebSocket data forwarding The forwarding network node library or the network nodes on the routing link constitute a network node library that may not support WebSocket data forwarding.

In a second possible implementation manner of the seventh aspect, the device further includes:

The second storing module is configured to store the network nodes that are recorded as being capable of supporting WebSocket data forwarding into a database of network nodes capable of supporting WebSocket data forwarding.

The eighth aspect provides a server, characterized in that the server includes the device for finding network nodes that do not support WebSocket data forwarding according to any one of the seventh aspect.

In the embodiment of the present invention, after receiving an instruction to find a network node that does not support WebSocket data forwarding, a routing link for transmitting WebSocket data is established between the first terminal and the second terminal according to the instruction, and if the routing link is connected, By deleting the network node of the routing link in the preset network node database that may not support WebSocket data forwarding, a more accurate network node database that may not support WebSocket data forwarding can be obtained. Through the connection of the routing link between the first terminal and the second terminal, it can be obtained that the network nodes on the routing link are all network nodes that can support WebSocket data forwarding, and in the preset network that may not support WebSocket data forwarding After the node library is deleted, the obtained network node library that may not support WebSocket data forwarding is more accurate, and the entire implementation process is simple to implement. With the increase in the number of tests, the network node library that does not support WebSocket data forwarding will become more and more accurate , which can facilitate the more reliable implementation of various future solutions based on WebSocket data forwarding.

Description of drawings

Fig. 1 is the realization flowchart of the search of the network node that does not support WebSocket data forwarding that the first embodiment of the present invention provides;

Fig. 2 is the realization flowchart of the search of the network node that does not support WebSocket data forwarding provided by the second embodiment of the present invention;

Fig. 3 is the implementation flowchart of the search of the network node based on the client that does not support WebSocket data forwarding provided by the third embodiment of the present invention;

Fig. 4 is the implementation flowchart of searching for the network node that does not support WebSocket data forwarding provided by the fourth embodiment of the present invention;

5 is a schematic structural diagram of a search device for a network node that does not support WebSocket data forwarding provided by a fifth embodiment of the present invention;

6 is a schematic structural diagram of a search device for a network node that does not support WebSocket data forwarding provided by a sixth embodiment of the present invention;

7 is a schematic structural diagram of a search device for a network node that does not support WebSocket data forwarding provided by an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a terminal device that does not support searching for a network node that forwards WebSocket data provided by an embodiment of the present invention.

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present invention, not to limit the present invention.

In the embodiment of the present invention, a search method for a network node that does not support WebSocket data forwarding is provided, and an instruction to search for a network node that does not support WebSocket data forwarding is received; according to the instruction, the first terminal and the second terminal establish Send the routing link of WebSocket data; determine whether the routing link is connected; if the routing link is connected, record the network node on the routing link as a network node that can support WebSocket data forwarding, and the routing link The network nodes on the road include all network nodes between the first terminal and the second terminal that the routing link passes through; delete the A network node that supports WebSocket data forwarding. By establishing a routing link for transmitting WebSocket data between the first terminal and the second terminal, if the routing link is connected, the network node of the routing link will be selected in the preset network node library that may not support WebSocket data forwarding Delete it to get more accurate network node libraries that may not support WebSocket data forwarding. Through the connection of the routing link between the first terminal and the second terminal, it can be obtained that the network nodes on the routing link are all network nodes that can support WebSocket data forwarding, and in the preset network that may not support WebSocket data forwarding After the node library is deleted, the obtained network node library that may not support WebSocket data forwarding is more accurate, and the entire implementation process is simple to implement. With the increase in the number of tests, the network node library that does not support WebSocket data forwarding will become more and more accurate , which can facilitate the more reliable implementation of various future solutions based on WebSocket data forwarding.

Embodiment one:

Fig. 1 shows the implementation process of searching for network nodes that do not support WebSocket data forwarding provided by the first embodiment of the present invention, and the details are as follows:

In step S101, an instruction to find a network node that does not support WebSocket data forwarding is received.

The implementation form of the receiving instruction can be setting an advertisement box embedded with test codes on the WEB page or setting a corresponding function button, and the corresponding instruction can be triggered when the user clicks on the corresponding advertisement or clicks on the corresponding function button. Embedding the touch command into the WEB page can receive trigger commands from a wider range of user terminals through browsers. Certainly, the embodiment of the present invention is not limited thereto, and an instruction from the user terminal to search for a network node that does not support WebSocket data forwarding may also be received through various applications or client forms of the client.

In step S102, according to the instruction, a routing link for transmitting WebSocket data is established between the first terminal and the second terminal.

The routing link includes the best path determined by a plurality of links, that is, including a plurality of lines from one network node to an adjacent network node.

The instruction includes two terminals that need to establish a routing link for transmitting WebSocket data. If the instruction is received in a browser or other applications, one of the ends (the first terminal or the second terminal) is the browser or the second terminal. The terminal where the application is located, and the other terminal is the server set in the command, such as Netease, Sina, etc., set the server that can receive WebSocket data access.

Establishing a handshake for routing links between the client and the server to transmit WebSocket data generally includes the following three steps:

1. The client sends a connection request to the server;

2. The server determines that it is a connection request of the WebSocket protocol and responds to the connection request, establishes a connection for transmitting WebSocket data packets between the client and the server, and the client starts to transmit WebSocket data packets to the server.

In step S103, it is judged whether the routing link is connected.

Judging whether the routing link is connected can be based on whether the data returned by the handshake request is normal. If the data is normal, it means that the current routing link is a routing link that can be connected.

In step S104, if the routing link is connected, record that the network node of the routing link is a network node that can support WebSocket data forwarding. The network nodes on the routing link include all network nodes between the first terminal and the second terminal that the routing link passes through, excluding the first terminal and the second terminal.

When the data returned by the handshake request is normal or data can be sent and received normally, it means that the current routing link can be connected, and all network nodes on the current routing link support WebSocket data forwarding.

In this step, the network node information of the routing link needs to be obtained, and the network node information of the routing link can be obtained by invoking the traceroute command through the server or a terminal that supports the traceroute service.

In step S105, the network node that can support WebSocket data forwarding is deleted from the preset network node library that may not support WebSocket data forwarding.

The preset network node library that may not support WebSocket data forwarding includes network nodes that support WebSocket data forwarding, and may also include network nodes that do not support WebSocket data forwarding. The network node library can be pre-set on the server or the first The third-party server can also establish itself during the test process. The database obtained during the test process will become more and more complete as the test progresses. Wherein, the process of self-improving the network node library in the testing process can be:

If the routing link is disconnected, determine whether the network node of the routing link is a recorded network node that can support WebSocket data forwarding;

If the network node of the routing link is not a recorded network node that can support WebSocket data forwarding, store the network node of the routing link in a network node library that may not support WebSocket data forwarding.

As the test progresses, delete more and more network nodes that support WebSocket data forwarding after testing in the network node library that may not support WebSocket data forwarding, so that the network in the network node library that may not support WebSocket data forwarding The accuracy of the nodes is getting higher and higher. In this way, various subsequent solutions based on WebSocket data forwarding can be implemented more reliably.

Embodiment two:

Fig. 2 is the implementation process of searching for network nodes that do not support WebSocket data forwarding provided by the second embodiment of the present invention. The method is based on a client with a browser and a server that supports the WebSocket protocol to be accessed, and the client does not It is limited to computer terminals, and may also include clients composed of mobile terminals such as mobile phones and PADs. The method comprises the steps of:

In step S201, an instruction to find a network node that does not support WebSocket data forwarding is received.

The client receives the user's instruction to find a network node that does not support WebSocket data forwarding through the browser. The instruction can be set in a web page, application program or advertisement. The client accesses the corresponding page from the server through the browser and receives the click instruction to trigger ask. Due to the large number of users pushed by web pages, application clients or advertisements, many routing links from clients to servers can be established during the test process, including as many transit routes and other network nodes as possible .

In step S202, it is detected whether the browser of the client is a browser supporting the data communication of the WebSocket protocol, and if the browser does not support the data access of the WebSocket protocol, the search is ended.

The browsers in the existing clients have different extensions or supported protocols according to different versions. Newer versions of browsers, such as IE9 and other newer versions of browsers, can support data communication of the WebSocket protocol. The detection method may detect the model version of the browser or corresponding protocol identification information.

As an optional implementation of the present invention, it may also include steps S203 and S204. In step S203, it is detected whether the client and the server can communicate through the POST mode of the hypertext transfer protocol, if not , it is judged whether the network node on the link transmitting the POST request between the client and the server is a recorded network node that can support WebSocket data forwarding.

In step S204, if the network node on the link transmitting the POST request is not a recorded network node that can support WebSocket data forwarding, store the network node on the link transmitting the POST request into the preset The network node library that may not support WebSocket data forwarding. The client and the server in this embodiment may correspond to the first terminal and the second terminal in the first embodiment.

In step S205, according to the instruction, a routing link for transmitting WebSocket data is established between the client and the server.

To establish a routing link between the server and the client for transmitting WebSocket data, the browser of the client can initiate a handshake request for transmitting WebSocket data, and after getting a response from the server, establish a routing link for transmitting data connection.

In step S206, it is judged whether the routing link is connected.

When the data returned by the handshake request is normal, it means that the current routing link can be connected, and all network nodes on the current routing link support WebSocket data forwarding.

In step S207, if the routing link is disconnected, it is judged whether the network node of the routing link is a recorded network node that can support WebSocket data forwarding.

In step S208, if the network node on the routing link is not a recorded network node that can support WebSocket data forwarding, store the network node on the routing link into the preset that may not support WebSocket data The forwarding network node library or the network nodes on the routing link constitute a network node library that may not support WebSocket data forwarding.

Before the network node library that may not support WebSocket data forwarding is established, if the network node on the routing link is not a recorded network node that can support WebSocket data forwarding, form the network node on the routing link A network node library that may not support WebSocket data forwarding.

After the network node library that may not support WebSocket data forwarding is established, if the network node on the routing link is not a recorded network node that can support WebSocket data forwarding, store the network node on the routing link Enter the preset network node library that may not support WebSocket data forwarding.

In step S209, if the routing link is connected, record the network node of the routing link as a network node that can support WebSocket data forwarding, and the network nodes on the routing link include the All network nodes located between the first terminal and the second terminal.

In step S210, the network node that can support WebSocket data forwarding is deleted from the preset network node library that may not support WebSocket data forwarding.

In step S211, the network nodes recorded as being capable of supporting WebSocket data forwarding are stored in a database of network nodes capable of supporting WebSocket data forwarding.

The embodiment of the present invention obtains many clients by accessing the test page from the webpage, thus can establish a large number of routing links with the server, so that it can include a large number of different routing links, so that the same network node of the test may have multiple Among the routing links, after the network node in one of the routing links is a network node that can support WebSocket data forwarding, the cause of the disconnection caused by the network node can be eliminated in other disconnected routing links. When there are N network nodes in a disconnected routing link, and N-1 network nodes have been recorded as network nodes that support WebSocket data forwarding, then the remaining network node is a network that does not support WebSocket data forwarding Node, and record it to the network node library that does not support WebSocket data forwarding, the network node library can provide accurate data for future solution implementation.

Embodiment three:

FIG. 3 is a schematic flow diagram of a client-based search for a network node that does not support WebSocket data forwarding provided by the third embodiment of the present invention, and is described in detail as follows:

In step S301, an instruction to find a network node that does not support WebSocket data forwarding is received.

Based on the first terminal, it can be a client. The client receives the search instruction input by the user when browsing the page or using the application through the web page or the application program. Since the more clients are tested, the more routing links are established. The test result is also more accurate, therefore, you can choose a more commonly used web page or application program to receive the test instruction and execute the subsequent test process.

In step S302, according to the instruction, a connection request for establishing a routing link for transmitting WebSocket data is initiated to the second terminal, so as to establish a routing link for transmitting WebSocket data with the second terminal.

The client receives an instruction to search for a network node that does not support WebSocket data forwarding, and initiates a handshake request to the second terminal, which can be a server, etc. After the handshake request is completed, a routing link for transmitting WebSocket data is established.

In step S303, it is judged whether the routing link is connected.

Obtain the network node of the routing link on the client side. Considering that the general client may not be able to execute the traceroute command, the network node of the routing link can be obtained by calling the traceroute service of the server, and the obtained routing link Data from network nodes is returned to the client.

In step S304, if the routing link is connected, record that the network node on the routing link is a network node that can support WebSocket data forwarding, and the network node on the routing link includes that the routing link is All network nodes establishing connections with the second terminal.

In step S305, the network node that can support WebSocket data forwarding is deleted from the preset network node library that may not support WebSocket data forwarding.

Wherein, when the data returned by the handshake request is normal or data can be sent and received normally, it means that the current routing link can be connected. The preset network node library that may not support WebSocket data forwarding can be preset by the tester, or a disconnected routing link is obtained during the test, and the network nodes of the disconnected routing link are stored Enter the network node library that may not support WebSocket data forwarding, and the network node library can be in the specified server.

For improving the test efficiency of the network node of routing link, before step S303, also can include detecting whether browser supports the data access of WebSocket agreement; If do not support the data access of WebSocket agreement, then end search; If described browser supports WebSocket protocol data access, execute the step of initiating a connection request to the second terminal to establish a routing link for transmitting WebSocket data. Or it includes detecting whether the browser and the server can be connected through the POST mode of the hypertext transfer protocol, and if not, then judging whether the network node of the link transmitting the POST request between the browser and the server is a recorded WebSocket data that can be supported forwarding network node; if the network node of the link that transmits the POST request is not a recorded network node that can support WebSocket data forwarding, store the network node of the link that transmits the POST request into the network node that may not support WebSocket data forwarding Network node library.

Embodiment four:

Fig. 4 is the search method of the network node that does not support WebSocket data forwarding provided by the fourth embodiment of the present invention, the embodiment of the present invention describes its implementation process based on the server end, specifically includes the following steps:

In step S401, a connection request for establishing a routing link for transmitting WebSocket data sent by a first terminal is received.

In step S402, according to the request, a routing link for transmitting WebSocket data is established with the first terminal.

Establish a routing link for transmitting WebSocket data with the first terminal. The browser of the first terminal can initiate a handshake request for transmitting WebSocket data. After receiving a response from the server, establish a routing link for transmitting data connection

In step S403, the connectivity of the routing link is judged.

In step S404, if the routing link is connected, record that the network node of the routing link is a network node that can support WebSocket data forwarding.

In step S405, the network node that can support WebSocket data forwarding is deleted from the preset network node library that may not support WebSocket data forwarding.

Wherein, the preset network node library that may not support WebSocket data forwarding can be obtained in the following manner: after step S402, if the routing link is not connected, it is judged whether the network node of the routing link It is a recorded network node that can support WebSocket data forwarding;

If the network node of the routing link is not a recorded network node that can support WebSocket data forwarding, store the network node of the routing link in the network node library that may not support WebSocket data forwarding or save the routing link The network nodes on constitute a library of network nodes that may not support WebSocket data forwarding.

Before the network node library that may not support WebSocket data forwarding is established, if the network node on the routing link is not a recorded network node that can support WebSocket data forwarding, form the network node on the routing link A network node library that may not support WebSocket data forwarding.

After the network node library that may not support WebSocket data forwarding is established, if the network node on the routing link is not a recorded network node that can support WebSocket data forwarding, store the network node on the routing link Enter the preset network node library that may not support WebSocket data forwarding.

The network node database can be stored in a server or other third-party server, which can facilitate the sharing of modified network node data information.

In addition, the network nodes that are recorded as being able to support WebSocket data forwarding can also be stored in the network node database that can support WebSocket data forwarding, so as to facilitate future calls.

Embodiment five:

FIG. 5 is a schematic structural diagram of a search device 500 for a network node that does not support WebSocket data forwarding provided by a fifth embodiment of the present invention. The details are as follows:

The search device 500 for a network node that does not support WebSocket data forwarding in the embodiment of the present invention includes:

The receiving unit 501 is configured to receive an instruction to find a network node that does not support WebSocket data forwarding;

A routing link establishment unit 502, configured to establish a routing link for transmitting WebSocket data between the first terminal and the second terminal according to the instruction received by the receiving unit 501;

A first judging unit 503, configured to judge whether the routing link established by the routing link establishing unit 502 is connected;

The recording unit 504 is configured to record that the network node on the routing link is a network node that can support WebSocket data forwarding if the routing link judged by the first judging unit 503 is connected, and the routing link on the routing link The network nodes include all network nodes located between the first terminal and the second terminal through which the routing link passes;

The deleting unit 505 is configured to delete the network node capable of supporting WebSocket data forwarding recorded by the recording unit from the preset network node library that may not support WebSocket data forwarding.

Wherein, in order to improve the data information of the network node library that may not support WebSocket data forwarding, the device may also include:

The second judging unit 506 is configured to judge whether the network node on the routing link is a recorded network node that can support WebSocket data forwarding if the routing link judged by the first judging unit is disconnected;

The first network node storage unit 507 is configured to save the network node on the routing link if the network node on the routing link judged by the second judging unit is not a recorded network node that can support WebSocket data forwarding Store the preset network node library that may not support WebSocket data forwarding or form the network nodes on the routing link into a network node library that may not support WebSocket data forwarding.

Can further improve the detection efficiency, the first terminal is a client with a browser, the second terminal is a server that supports the WebSocket protocol to be accessed, and the device also includes:

The first detection unit 508 is used to detect whether the browser of the client is a browser that supports WebSocket protocol communication, if the browser of the client is a browser that does not support WebSocket protocol communication, then end the search; if the client If the browser at the end is a browser supporting WebSocket protocol communication, transfer to the routing link establishing unit 502 for execution. Or the device can also have a second detection unit 509 and a second network node storage unit 510, wherein the second detection unit 509 is used to detect whether the first terminal and the second terminal use the POST mode of the hypertext transfer protocol It can be connected, and if not, it is judged whether the network node of the link transmitting the POST request between the first terminal and the second terminal is a recorded network node that can support WebSocket data forwarding.

The second network node storage unit 510 is used to store the network node on the routing link into the network node if the network node on the link transmitting the POST request is not a recorded network node that can support WebSocket data forwarding. The preset network node library that may not support WebSocket data forwarding.

Correspondingly, the embodiments of the present invention may also include a system composed of the devices described in this embodiment.

The device described in the embodiment of the present invention corresponds to the method embodiment described in Embodiment 1 and Embodiment 2 of the present invention, and details are not repeated here.

Embodiment six:

FIG. 6 is a schematic structural diagram of a search device 600 for a network node that does not support WebSocket data forwarding provided by the sixth embodiment of the present invention. The details are as follows:

The device described in the embodiment of the present invention includes:

The receiving module 601 is configured to receive an instruction to find a network node that does not support WebSocket data forwarding;

The connection request sending module 602 is configured to initiate a connection request to the second terminal to establish a routing link for transmitting WebSocket data according to the instruction received by the receiving module 601, so as to establish a routing link for transmitting WebSocket data with the second terminal;

A first acquisition judging module 603, configured to judge whether the routing link is connected;

The first recording module 604 is configured to record the network node on the routing link as a network node that can support WebSocket data forwarding if the routing link is connected, and the network node on the routing link includes the route The links are all network nodes establishing connections with the second terminal;

A deletion module 605, configured to delete the network node that can support WebSocket data forwarding from the preset network node library that may not support WebSocket data forwarding.

Specifically, the second terminal may be a server, and the first obtaining and judging module 603 is specifically configured to call a traceroute service of the server to obtain the network node of the routing link, and judge whether the routing link is connected.

When the connection request is sent by the browser, the device may further include:

The first detection module 606 is used to detect whether the browser supports the data access of the WebSocket protocol, if the data access of the WebSocket protocol is not supported, the search is ended, and if the browser supports the data access of the WebSocket protocol, then the connection request is sent module execution; or

The second detection module 607 is used to detect whether the browser and the server can be connected through the POST mode of the hypertext transfer protocol, if not, then judge whether the network node of the link transmitting the POST request between the browser and the server is established Recorded network nodes that can support WebSocket data forwarding;

The first network node storage module 608 is used to store the network node of the link that transmits the POST request into a possible A network node library that does not support WebSocket data forwarding.

The embodiment of the present invention also provides a terminal device, and the terminal device includes the device for finding a network node that does not support WebSocket data forwarding according to the embodiment of the present invention.

The device embodiment in the present invention corresponds to the method embodiment in the third embodiment of the present invention, and details are not repeated here.

Embodiment seven:

7 is a schematic structural diagram of a search device 700 for a network node that does not support WebSocket data forwarding provided by an embodiment of the present invention, and is described in detail as follows:

The search device 700 for a network node that does not support WebSocket data forwarding in the embodiment of the present invention includes:

A connection request receiving module 701, configured to receive a connection request sent by the first terminal to establish a routing link for transmitting WebSocket data;

A routing link establishment module 702, configured to establish a routing link for transmitting WebSocket data with the first terminal according to the request received by the connection request receiving module;

The second judging module 703 is configured to judge the connectivity of the routing link established by the routing link establishing module 702;

The second recording module 704 is used for judging by the second judging module 703 that if the routing link is connected, record the network node of the routing link as a network node that can support WebSocket data forwarding;

The second deletion module 705 is configured to delete the network node that can support WebSocket data forwarding from the preset network node library that may not support WebSocket data forwarding.

In order to make the data of the network node library that may not support WebSocket data forwarding more comprehensive, the device also includes a network node judging module 706, which is used to judge whether the network node of the routing link is connected if the routing link is disconnected. It is a recorded network node that can support WebSocket data forwarding;

The second network node storage module 707 is used to store the network node on the routing link into a network node that may not support WebSocket if the network node on the routing link is not a recorded network node that can support WebSocket data forwarding. The network node library for data forwarding or the network nodes on the routing link constitute a network node library that may not support WebSocket data forwarding.

To better facilitate subsequent data calls, the device further includes a second storage module 708, configured to store the network nodes that are recorded as supporting WebSocket data forwarding into the network node library that supports WebSocket data forwarding.

An embodiment of the present invention provides a server, including the device for finding network nodes that do not support WebSocket data forwarding described in this embodiment.

The device embodiment of the present invention corresponds to the method embodiment described in Embodiment 4, and will not be repeated here.

Embodiment eight:

FIG. 8 is a terminal device 80 for searching network nodes that do not support WebSocket data forwarding provided by an embodiment of the present invention, including: a processor 81 , a memory 82 and a network module 83 . in,

The processor 81 is used for executing programs.

In Embodiment 8 of the present invention, the program may include program code, and the program code includes computer operation instructions.

Processor 81 may be a central processing unit CPU, or one or more integrated circuits configured to implement embodiments of the present invention.

The memory 82 is used to store programs.

The memory 82 may include random-access memory (English: Random-access memory, abbreviation: RAM), and may also include a non-volatile memory (English: Non-volatile memory, abbreviation: NVRAM).

The network module 83 is used to send data in the terminal device to the server, and receive data information sent by the service, such as a data packet based on the WebSocket protocol;

When the terminal device for searching the network node that does not support WebSocket data forwarding is running, the processor 81 is used to execute the program stored in the memory 82 so that the terminal device for searching the network node that does not support WebSocket data forwarding performs the following steps method:

The processor 81 receives an instruction to find a network node that does not support WebSocket data forwarding;

The processor 81 initiates a connection request to the second terminal to establish a routing link for transmitting WebSocket data according to the instruction;

The processor 81 obtains the network node of the routing link, and judges whether the routing link is connected

When the routing link is connected, the processor 81 records the network node of the routing link as a network node that can support WebSocket data forwarding, and deletes the network node that can support WebSocket data forwarding from the preset network node library that may not support WebSocket data forwarding. For network nodes that support WebSocket data forwarding, get a more accurate library of network nodes that do not support WebSocket data forwarding.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus necessary general-purpose hardware, and of course also by hardware, but in many cases the former is a better embodiment . Based on this understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product is stored in a readable storage medium, such as a floppy disk of a computer , a hard disk or an optical disk, etc., including several instructions for enabling a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments of the present invention.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present invention should be included in the protection of the present invention. within range.

Claims (26)

1. A method for searching a network node which does not support WebSocket data forwarding is characterized by comprising the following steps:

receiving an instruction for searching a network node which does not support WebSocket data forwarding;

establishing a routing link for transmitting WebSocket data between the first terminal and the second terminal according to the instruction;

judging whether the routing links are connected or not;

if the routing link is communicated, recording that the network nodes on the routing link are network nodes capable of supporting WebSocket data forwarding, wherein the network nodes on the routing link comprise all network nodes which are located between the first terminal and the second terminal and passed by the routing link;

and deleting the network nodes capable of supporting the WebSocket data forwarding from a preset network node library which may not support the WebSocket data forwarding.

2. The method of claim 1, further comprising:

if the routing link is disconnected, judging whether the network node on the routing link is a recorded network node capable of supporting WebSocket data forwarding;

if the network node on the routing link is not the recorded network node which can support WebSocket data forwarding, the network node on the routing link is stored into the preset network node library which possibly does not support WebSocket data forwarding or the network node on the routing link is formed into the network node library which possibly does not support WebSocket data forwarding.

3. The method of claim 1, wherein the first terminal comprises a client with a browser, wherein the second terminal comprises a server supporting WebSocket protocol communication, and wherein before the step of establishing, according to the instruction, a routing link for transmitting WebSocket data between the first terminal and the second terminal, the method further comprises:

detecting whether the browser of the client is a browser supporting WebSocket protocol communication;

if the browser of the client side is a browser which does not support WebSocket protocol communication, finishing searching;

and if the browser of the client is the browser supporting WebSocket protocol communication, executing the step of establishing a routing link for transmitting WebSocket data between the first terminal and the second terminal according to the command.

4. The method of claim 1, wherein before the establishing, according to the instruction, a routing link for transmitting WebSocket data between the first terminal and the second terminal, the method further comprises:

detecting whether the first terminal and the second terminal can be communicated through a POST mode of a hypertext transfer protocol, if not, judging whether a network node on a link for transmitting a POST request between the first terminal and the second terminal is a recorded network node capable of supporting WebSocket data forwarding;

and if the network node on the link transmitting the POST request is not the recorded network node capable of supporting WebSocket data forwarding, storing the network node on the link transmitting the POST request into the preset network node library which possibly does not support WebSocket data forwarding.

5. The method of claim 1, further comprising:

and storing the network nodes recorded as the network nodes capable of supporting WebSocket data forwarding into a network node library capable of supporting WebSocket data forwarding.

6. A lookup apparatus for a network node that does not support WebSocket data forwarding, the apparatus comprising:

the receiving unit is used for receiving an instruction for searching a network node which does not support WebSocket data forwarding;

a routing link establishing unit, configured to establish, according to the instruction received by the receiving unit, a routing link that transmits WebSocket data between the first terminal and the second terminal;

a first judging unit, configured to judge whether the routing links established by the routing link establishing unit are connected;

a recording unit, configured to record, if the routing link determined by the first determining unit is connected, that a network node on the routing link is a network node capable of supporting WebSocket data forwarding, where the network node on the routing link includes all network nodes located between the first terminal and the second terminal, and the network nodes pass through by the routing link;

and the deleting unit is used for deleting the network nodes which are recorded by the recording unit and can support the WebSocket data forwarding in a preset network node library which can not support the WebSocket data forwarding.

7. The apparatus of claim 6, further comprising:

a second judging unit, configured to judge whether a network node on the routing link is a recorded network node that can support WebSocket data forwarding if the routing link judged by the first judging unit is not connected;

and the first network node storing unit is used for storing the network nodes on the routing link into the preset network node library which possibly does not support the WebSocket data forwarding or forming the network nodes on the routing link into the network node library which possibly does not support the WebSocket data forwarding if the network nodes on the routing link judged by the second judging unit are not the recorded network nodes which can support the WebSocket data forwarding.

8. The apparatus of claim 6, wherein the first terminal comprises a client with a browser, wherein the second terminal comprises a server supporting WebSocket protocol communication, and wherein the apparatus further comprises:

the first detection unit is used for detecting whether the browser of the client side is a browser supporting WebSocket protocol communication; if the browser of the client side is a browser which does not support WebSocket protocol communication, finishing searching; and if the browser of the client is the browser supporting WebSocket protocol communication, switching to the routing link establishing unit for execution.

9. The apparatus of claim 6, further comprising:

the second detection unit is used for detecting whether the first terminal and the second terminal can be communicated through a POST mode of a hypertext transfer protocol, and if not, judging whether a network node of a link for transmitting a POST request between the first terminal and the second terminal is a recorded network node capable of supporting WebSocket data forwarding;

and the second network node storing unit is used for storing the network node on the routing link into the preset network node library which possibly does not support the WebSocket data forwarding if the network node on the link transmitting the POST request is not the recorded network node which can support the WebSocket data forwarding.

10. The apparatus of claim 6, further comprising:

and the third network node storing unit is used for storing the network nodes which are recorded as the network nodes capable of supporting the WebSocket data forwarding into a network node library capable of supporting the WebSocket data forwarding.

11. A method for searching a network node which does not support WebSocket data forwarding is characterized by comprising the following steps:

receiving an instruction for searching a network node which does not support WebSocket data forwarding;

initiating a connection request for establishing a routing link for transmitting the WebSocket data to the second terminal according to the instruction so as to establish the routing link for transmitting the WebSocket data with the second terminal;

judging whether the routing links are connected or not;

if the routing link is communicated, recording that the network nodes on the routing link are network nodes capable of supporting WebSocket data forwarding, wherein the network nodes on the routing link comprise all network nodes which establish connection with the second terminal;

and deleting the network nodes capable of supporting the WebSocket data forwarding from a preset network node library which may not support the WebSocket data forwarding.

12. The method according to claim 11, wherein the second terminal is a server, and the step of determining whether the routing links are connected specifically comprises:

and calling traceroute service of a server to acquire the network node of the routing link and judge whether the routing link is communicated.

13. The method of claim 11, wherein the connection request is sent by a browser, and before the step of initiating a connection request for establishing a routing link for transmitting WebSocket data to the second terminal according to the instruction, the method further comprises:

detecting whether the browser supports data access of a WebSocket protocol;

if the data access of the WebSocket protocol is not supported, finishing the search;

and if the browser supports the data access of the WebSocket protocol, executing the step of initiating a connection request for establishing a routing link for transmitting the WebSocket data to the second terminal.

14. The method of claim 11, wherein the connection request is sent by a browser, and before the step of initiating a connection request for establishing a routing link for transmitting WebSocket data to a server according to the instruction, the method further comprises:

detecting whether the browser and the server can be communicated through a POST mode of a hypertext transfer protocol, and if not, judging whether a network node of a link for transmitting a POST request between the browser and the server is a recorded network node capable of supporting WebSocket data forwarding;

if the network node of the link transmitting the POST request is not the recorded network node capable of supporting WebSocket data forwarding, the network node of the link transmitting the POST request is stored into a network node library which may not support WebSocket data forwarding.

15. A lookup apparatus for a network node that does not support WebSocket data forwarding, the apparatus comprising:

the receiving module is used for receiving an instruction for searching a network node which does not support WebSocket data forwarding;

the connection request sending module is used for initiating a connection request for establishing a routing link for transmitting the WebSocket data to the second terminal according to the instruction received by the receiving module so as to establish the routing link for transmitting the WebSocket data with the second terminal;

the first judging module is used for judging whether the routing links are communicated or not;

a first recording module, configured to record, if the routing link is connected, that the network nodes on the routing link are network nodes capable of supporting WebSocket data forwarding, where the network nodes on the routing link include all network nodes in which the routing link is connected to the second terminal;

and the deleting module is used for deleting the network nodes which can support the WebSocket data forwarding from a preset network node library which may not support the WebSocket data forwarding.

16. The apparatus according to claim 15, wherein the second terminal is a server, and the first determining module is specifically configured to invoke a traceroute service of the server to obtain a network node of the routing link, and determine whether the routing link is connected.

17. The apparatus of claim 15, wherein the connection request is sent by a browser, the apparatus further comprising:

the first detection module is used for detecting whether the browser supports data access of the WebSocket protocol, if not, the search is finished, and if the browser supports the data access of the WebSocket protocol, the connection request sending module is switched to execute the search.

18. The apparatus of claim 15, wherein the connection request is sent by a browser, the apparatus further comprising:

the second detection module is used for detecting whether the browser and the server can be communicated through a POST mode of a hypertext transfer protocol, and if not, judging whether a network node of a link for transmitting a POST request between the browser and the server is a recorded network node capable of supporting WebSocket data forwarding;

and the first network node storing module is used for storing the network node of the link transmitting the POST request into a network node library which may not support the WebSocket data forwarding if the network node of the link transmitting the POST request is not the recorded network node which can support the WebSocket data forwarding.

19. A terminal device, characterized in that the terminal device comprises the lookup apparatus of any one of claims 15 to 18 for a network node that does not support WebSocket data forwarding.

20. A method for searching a network node which does not support WebSocket data forwarding is characterized by comprising the following steps:

receiving a connection request for establishing a routing link for transmitting WebSocket data, which is sent by a first terminal;

establishing a routing link for transmitting WebSocket data with the first terminal according to the request;

judging the connectivity of the routing link;

if the routing link is connected, recording that the network node of the routing link is a network node capable of supporting WebSocket data forwarding,

and deleting the network nodes capable of supporting the WebSocket data forwarding from a preset network node library which may not support the WebSocket data forwarding.

21. The method of claim 20, further comprising:

if the routing link is disconnected, judging whether the network node on the routing link is a recorded network node capable of supporting WebSocket data forwarding;

if the network nodes on the routing link are not recorded network nodes capable of supporting WebSocket data forwarding, storing the network nodes on the routing link into a network node library which possibly does not support WebSocket data forwarding or forming the network nodes on the routing link into a network node library which possibly does not support WebSocket data forwarding.

22. The method of claim 20, further comprising:

and storing the network nodes recorded as the network nodes capable of supporting WebSocket data forwarding into a network node library capable of supporting WebSocket data forwarding.

23. A lookup apparatus for a network node that does not support WebSocket data forwarding, the apparatus comprising:

the device comprises a connection request receiving module, a first terminal and a second terminal, wherein the connection request receiving module is used for receiving a connection request which is sent by the first terminal and used for establishing a routing link for transmitting WebSocket data;

the routing link establishing module is used for establishing a routing link for transmitting WebSocket data with the first terminal according to the request received by the connection request receiving module;

a second judging module, configured to judge connectivity of the routing link established by the routing link establishing module;

the second recording module is used for judging that if the routing link is communicated, the second judging module records that the network node of the routing link is a network node capable of supporting WebSocket data forwarding;

and the second deleting module is used for deleting the network nodes capable of supporting the WebSocket data forwarding in a preset network node library which may not support the WebSocket data forwarding.

24. The apparatus of claim 23, further comprising:

the network node judging module is used for judging whether the network node of the routing link is a recorded network node which can support WebSocket data forwarding or not if the routing link is not communicated;

and the second network node storing module is used for storing the network nodes on the routing link into a network node library which possibly does not support WebSocket data forwarding or forming the network nodes on the routing link into a network node library which possibly does not support WebSocket data forwarding if the network nodes on the routing link are not recorded network nodes which can support WebSocket data forwarding.

25. The apparatus of claim 23, further comprising:

and the second storing module is used for storing the network nodes which are recorded as being capable of supporting WebSocket data forwarding into a network node library capable of supporting WebSocket data forwarding.

26. A server, characterized in that it comprises lookup means of a network node not supporting WebSocket data forwarding according to any of claims 23 to 25.