Internal and external network connection test method and terminal

Abstract

The invention discloses an intranet and extranet connection test method and a terminal, and the method comprises the steps: loading resources on a webpage according to a pre-configured intranet resource address, and obtaining a resource loading result; if the resource loading result is that loading is successful, sending an intranet connection prompt; if the resource loading result is loading failure, waking up the VPN client to execute the connection operation, and returning to execute the step of loading the resources on the webpage according to the pre-configured intranet resource address; according to the method, the VPN client is automatically awakened to re-execute the connection operation, and the step of loading the resource through the intranet resource address is returned to be executed, so that a user side can realize non-inductive operation, and the user only needs to directly perform subsequent operation when the intranet connected signal is obtained, so that the manual operation of the user is liberated, and the user experience is improved. And the internal and external network connection process is simplified.

Description

[0001] This case is a divisional application of the patent application filed on April 19, 2023, with application number 202310420172.3 and titled "A Method and Terminal for Connecting Internal and External Networks". Technical Field

[0002] This invention relates to the field of network data processing, and in particular to a method and terminal for testing the connection between internal and external networks. Background Technology

[0003] Traditional VPN (Virtual Private Network) applications are generally used when users are in an internet environment but need to connect to an internal network. A more feasible and common approach is to use a VPN to establish a private network (internal network) on a public network (the internet). At the same time, the VPN network channel between the public network and the private network uses encrypted communication, which ensures both network accessibility and data security.

[0004] Enterprise application systems are typically deployed on internal networks, with internet access achieved through VPN tunnels. However, in typical internet environments, user clients need to pre-install VPN clients, manually open the VPN client, connect to the internal network, and then access the application system. This series of steps, mostly manual, results in a poor user experience and is cumbersome. Furthermore, sometimes the internal network isn't fully connected after the VPN connection is established. While users may perceive a connection based on the VPN notification, the application system may still be inaccessible, leading to numerous user complaints and increased maintenance workload. The connection process between public network application systems and VPN tunnels is complex and cannot achieve seamless integration. Summary of the Invention

[0005] The technical problem to be solved by the present invention is to provide a method and terminal for testing internal and external network connections, so as to achieve seamless internal and external network connections on the user side.

[0006] To solve the above-mentioned technical problems, the present invention adopts the following technical solution: A method for testing internal and external network connectivity, including the following steps: Load resources onto the webpage based on the pre-configured intranet resource address, and obtain the resource loading result; If the resource loading result is successful, a notification that the intranet is connected will be sent. If the resource loading result is a loading failure, the VPN client is woken up to perform a connection operation, and then the process returns to the step of loading intranet resources on the webpage according to the pre-configured intranet resource address.

[0007] To solve the above-mentioned technical problems, another technical solution adopted by the present invention is as follows: A terminal for connecting internal and external networks includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it performs the following steps: Load resources onto the webpage based on the pre-configured intranet resource address, and obtain the resource loading result; If the resource loading result is successful, a notification that the intranet is connected will be sent. If the resource loading result is a loading failure, the VPN client is woken up to perform a connection operation, and then the process returns to the step of loading resources on the webpage according to the pre-configured intranet resource address.

[0008] The beneficial effects of this invention are as follows: Resources are loaded on a webpage using a pre-configured intranet resource address. If the loading is successful, it indicates that the VPN dial-up connection is established, and actual network access between the internal and external networks has been established. This means the external network can access the internal network through the VPN network channel, and a notification indicating successful internal network connection is sent, allowing the user to know that the internal network is successfully connected and proceed with subsequent operations. If the resource loading fails, the VPN client is automatically activated to re-execute the connection operation and return to the step of loading resources via the intranet resource address. Because the entire process is automatic reconnection, it is seamless for the user. The user only needs to perform subsequent operations upon receiving the intranet connection signal, freeing them from manual operation and simplifying the process of connecting the internal and external networks. Attached Figure Description

[0009] Figure 1 This is a flowchart illustrating the steps of an internal / external network connection testing method according to an embodiment of the present invention. Figure 2 This is a schematic diagram of the structure of an internal / external network connection test terminal according to an embodiment of the present invention; Label Explanation: 1. A terminal for connecting internal and external networks; 2. A processor; 3. A memory. Detailed Implementation

[0010] To explain in detail the technical content, objectives, and effects of the present invention, the following description is provided in conjunction with the embodiments and accompanying drawings.

[0011] Please refer to Figure 1 A method for testing internal and external network connectivity, including the following steps: Load resources onto the webpage based on the pre-configured intranet resource address, and obtain the resource loading result; If the resource loading result is successful, a notification that the intranet is connected will be sent. If the resource loading result is a loading failure, the VPN client is woken up to perform a connection operation, and then the process returns to the step of loading intranet resources on the webpage according to the pre-configured intranet resource address.

[0012] As can be seen from the above description, the beneficial effects of this invention are as follows: Resources are loaded on a webpage using a pre-configured intranet resource address. If the loading is successful, it indicates that the VPN dial-up connection is established, and actual network access between the internal and external networks has been established. This means the external network can access the internal network through the VPN network channel, and a notification indicating successful internal network connection is sent, allowing the user to know that the internal network is successfully connected and proceed with subsequent operations. If the resource loading result is a failure, the VPN client is automatically woken up to re-execute the connection operation and return to the step of loading resources via the intranet resource address. Because the entire process is an automatic reconnection, it is seamless for the user. The user only needs to perform subsequent operations upon receiving the intranet connection signal, freeing them from manual operation and simplifying the process of connecting the internal and external networks.

[0013] Furthermore, the step of loading resources on the webpage according to the pre-configured intranet resource address includes: A pre-defined webpage is deployed on the external network; Obtain at least one resource tag on the webpage, and set the resource address corresponding to the resource tag as the intranet resource address.

[0014] As described above, deploying a webpage on the external network allows access to the webpage even before a connection is established between the internal and external networks. This avoids the user experience being negatively impacted by an immediate access failure message. Furthermore, by setting the resource address corresponding to at least one resource tag to an internal network resource address, the failure to load some resources will not affect the overall display of the webpage, and the loading results can be easily obtained, avoiding cross-domain issues caused by accessing internal network webpages.

[0015] Furthermore, the step of loading resources on a webpage based on a pre-configured intranet resource address to obtain the resource loading result includes: Obtain the resource tag and load the resource using the resource address corresponding to the resource tag; Set up a listener program to monitor the loading events corresponding to resource tags whose resource addresses are internal network resource addresses, and obtain the resource loading results.

[0016] As described above, resources are loaded through the resource address corresponding to the resource tag, and a listener is set up to listen for the loading event of the resource tag whose resource address is an intranet resource address, so as to obtain the resource loading result. By building a listener, the resource loading result can be obtained automatically without the user's extra attention.

[0017] Furthermore, the statement that the resource loading result is successful also includes: Obtain the system address corresponding to the target intranet application system; Open the target intranet application system based on the system address.

[0018] As described above, if the resource loading result is successful, the system will automatically access the target intranet system based on the system address and directly open the target intranet application system that the user needs to access. This further simplifies the user's operation steps. From the user's perspective, there is no need to know the connection result between the intranet and the external network. As long as the user can successfully access the target intranet application system from the external network, the corresponding target intranet application system can be opened directly when the loading result is successful, which can provide the user with a better user experience.

[0019] Furthermore, the step of waking up the VPN client to perform the connection operation includes: The VPN client is woken up via the AppLink protocol to perform a connection operation.

[0020] As described above, both opening the webpage and loading resources should be done on the webpage. At this time, the AppLink protocol can directly wake up the VPN client from the webpage, so that the user does not need to operate manually. It can automatically perform connection operations through the VPN client, re-establish the connection channel between the internal and external networks, and repeatedly verify whether the channel can be accessed. This ensures that the entire retry process is seamless on the user side, thereby improving the user experience.

[0021] A terminal for connecting internal and external networks includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it performs the following steps: Load resources onto the webpage based on the pre-configured intranet resource address, and obtain the resource loading result; If the resource loading result is successful, a notification that the intranet is connected will be sent. If the resource loading result is a loading failure, the VPN client is woken up to perform a connection operation, and then the process returns to the step of loading resources on the webpage according to the pre-configured intranet resource address.

[0022] The beneficial effects of this invention are as follows: Resources are loaded on a webpage using a pre-configured intranet resource address. If the loading is successful, it indicates that the VPN dial-up connection is established, and actual network access between the internal and external networks has been established. This means the external network can access the internal network through the VPN network channel, and a notification indicating successful internal network connection is sent, allowing the user to know that the internal network is successfully connected and proceed with subsequent operations. If the resource loading fails, the VPN client is automatically activated to re-execute the connection operation and return to the step of loading resources via the intranet resource address. Because the entire process is automatic reconnection, it is seamless for the user. The user only needs to perform subsequent operations upon receiving the intranet connection signal, freeing them from manual operation and simplifying the process of connecting the internal and external networks.

[0023] Furthermore, the step of loading resources on the webpage according to the pre-configured intranet resource address includes: A pre-defined webpage is deployed on the external network; Obtain at least one resource tag on the webpage, and set the resource address corresponding to the resource tag as the intranet resource address.

[0024] As described above, deploying a webpage on the external network allows access to the webpage even before a connection is established between the internal and external networks. This avoids the issue of an immediate failure message during webpage access, preventing further operations and impacting the user experience. Furthermore, by setting the resource address corresponding to at least one resource tag to an internal network resource address, the failure to load some resources will not affect the overall display of the webpage, and the loading results can be easily obtained, avoiding cross-domain issues caused by accessing internal network webpages.

[0025] Furthermore, the step of loading resources on a webpage based on a pre-configured intranet resource address to obtain the resource loading result includes: Obtain the resource tag and load the resource using the resource address corresponding to the resource tag; Set up a listener program to monitor the loading events corresponding to resource tags whose resource addresses are internal network resource addresses, and obtain the resource loading results.

[0026] As described above, resources are loaded through the resource address corresponding to the resource tag, and a listener is set up to listen for the loading event of the resource tag whose resource address is an intranet resource address, so as to obtain the resource loading result. By building a listener, the resource loading result can be obtained automatically without the user's extra attention.

[0027] Furthermore, the statement that the resource loading result is successful also includes: Obtain the system address corresponding to the target intranet application system; Open the target intranet application system based on the system address.

[0028] As described above, if the resource loading result is successful, the system will automatically access the target intranet system based on the system address and directly open the target intranet application system that the user needs to access. This further simplifies the user's operation steps. From the user's perspective, there is no need to know the connection result between the intranet and the external network. As long as the user can successfully access the target intranet application system from the external network, the corresponding target intranet application system can be opened directly when the loading result is successful, which can provide the user with a better user experience.

[0029] Furthermore, the step of waking up the VPN client to perform the connection operation includes: The VPN client is woken up via the AppLink protocol to perform a connection operation.

[0030] As described above, both opening the webpage and loading resources should be done on the webpage. At this time, the AppLink protocol can directly wake up the VPN client from the webpage, so that the user does not need to operate manually. It can automatically perform connection operations through the VPN client, re-establish the connection channel between the internal and external networks, and repeatedly verify whether the channel can be accessed. This ensures that the entire retry process is seamless on the user side, thereby improving the user experience.

[0031] The above-described method and terminal for testing intranet / extranet connectivity of the present invention are applicable to scenarios where it is necessary to access the intranet from an extranet setting, such as scenarios where it is necessary to access application systems or intranet web pages. The following is a detailed description of the specific implementation method.

[0032] Please refer to Figure 1 Embodiment 1 of the present invention is as follows: A method for testing internal and external network connectivity, including the following steps: S01. A preset webpage, which is deployed on the external network; S02. Obtain at least one resource tag on the webpage, and set the resource address of the resource corresponding to the resource tag as the intranet resource address; In one optional implementation, the preset webpage can be a preset webpage system configured with relevant information to guide and remind users, such as reminders like "Network is currently being tested, please wait." This allows users to know the current connection status, giving them a psychological expectation and further improving the user experience. Initially, the user's network environment is the external network. After opening the webpage system, the system automatically loads a resource with an internal network resource address to determine whether the internal and external networks are connected. If the webpage is directly set up on the internal network, the user cannot access the entire webpage or obtain configuration guidance or prompts if there is no connection to the internal network, resulting in a poor user experience. However, by setting up the webpage / preset webpage system on the external network, since it is a B / S system, the system loads the internal network address through the resource address in the webpage / preset webpage system for judgment, which is simple and convenient. It can directly identify the current connection status of the internal and external networks. Compared to loading an internal network address through AJAX in the webpage / preset webpage system, there is no cross-domain issue. For example, if you set the src attribute of the HTML resource tag img to an internal network resource address, the resource corresponding to the img will be retrieved based on the internal network resource address when the corresponding webpage is loaded; other resource tags in HTML can achieve the same effect. S1. Load resources onto the webpage according to the pre-configured intranet resource address, and obtain the resource loading results, including: S11. Obtain resource tags and load resources through the resource addresses corresponding to the resource tags; S12. Set up a listening program to monitor the loading events corresponding to resource tags whose resource addresses are internal network resource addresses, and obtain the resource loading results. If the resource loading result is successful, execute step S2; if the resource loading result is unsuccessful, execute step S3. If there are inconsistent resource loading results corresponding to resource tags, execute step S4. Inconsistent resource loading results mean that when the resource tag is greater than 1, there are resource tags with both successful and unsuccessful resource loading results. S2. Send a notification that the intranet is now connected; In one optional implementation, if the resource loading result is successful, the system address corresponding to the target intranet application system is obtained; the target intranet application system is opened according to the system address; this can be performed simultaneously with sending an intranet connection notification, or it can replace the step of sending an intranet connection notification. S3. Increment the loop count by 1 and determine whether the loop count has reached the preset value. If so, output a fault alarm; otherwise, wake up the VPN client to perform the connection operation and return to step S1. The step of waking up the VPN client to perform the connection operation includes: waking up the VPN client to perform the connection operation through the AppLink protocol (a protocol in a URL), which can directly open the local VPN client in a web environment, improve the continuity of operation, and avoid manual operation by the user; wherein the VPN client is a client in the prior art that can establish a connection channel between the internal and external networks; Step S4 includes the following steps: S41. Obtain all resource loading results and the time information corresponding to the resource loading results; S42. Sort the resource loading results according to the time information and obtain the latest target resource loading result. If the target resource loading result is successful, execute S43; if the target resource loading result is unsuccessful, execute S44. S43. Randomly select a resource tag and execute S1 again to get the resource loading result. If the loading is still successful, execute S2; if the loading fails, output a connection instability message. S44. Randomly select one resource tag and execute S1 a preset number of times, or randomly select multiple resource tags and execute S1 once at the same time, and obtain the resource loading results for the preset number of times. If all loading is successful, then execute S2; if both loading success and loading failure occur at the same time, output an unstable connection prompt; if both loading fails, output a fault prompt alarm. If only one resource tag is configured, the network connection quality cannot be determined from a single resource loading result. If multiple resource tags are configured, but their resource loading results are different, the time of the resource loading result can indicate whether the most recent connection was successful. If the most recent connection was successful, it may be because the previous connection was unstable, or it may be because the connection was recently established. Therefore, a resource tag is randomly selected again to repeatedly retrieve the resource. If this also succeeds, the connection is successful; if it fails, the connection is unstable. If the most recent resource loading result is a failure, it means that a connection was successfully established before. If loading a resource tag a preset number of times or a preset number of resource tags yields successful results, the connection is stable. If there are still both successes and failures, the connection is unstable. If there are both failures, a fault may have occurred. Based on the judgment of connection success, this system further implements the judgment of connection stability, i.e., quality.

[0033] Please refer to Figure 2 Embodiment two of the present invention is as follows: An internal / external network connection terminal 1 includes a processor 2, a memory 3, and a computer program stored in the memory 3 and executable on the processor 2. When the processor 2 executes the computer program, it implements the steps in Embodiment 1.

[0034] In summary, this invention provides a method and terminal for testing intranet and extranet connectivity. The entire process, from network identification to opening the internal application system, is seamlessly integrated and automatically processed, greatly improving the user experience when using a VPN network environment, i.e., improving the user experience when accessing the intranet and extranet. Furthermore, the entire process from opening a preset webpage on the extranet to opening the target intranet application system can be completed automatically without manual operation by the user, achieving a seamless user experience.

[0035] The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent modifications made based on the content of the present invention specification and drawings, or direct or indirect applications in related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A method for testing internal and external network connectivity, characterized in that, Including the following steps: A preset webpage is deployed on the external network; the preset webpage is configured with relevant information to guide or remind users. Obtain at least one resource tag on the webpage, and set the resource address of the resource corresponding to the resource tag as the intranet resource address; Load resources onto the webpage based on the pre-configured intranet resource address, and obtain the resource loading result; If there are inconsistencies in the resource loading results corresponding to resource tags, then obtain all resource loading results and the time information corresponding to the resource loading results. The resource loading results are sorted according to the time information, and the latest target resource loading result is obtained. If the target resource loading result is successful, a resource tag is randomly selected and the resource is loaded on the webpage again according to the pre-configured intranet resource address to obtain the resource loading result; if the loading fails, an unstable connection prompt is output.

2. The method for testing internal and external network connectivity according to claim 1, characterized in that, The process of loading resources on a webpage based on a pre-configured intranet resource address, and obtaining the resource loading result, includes: If the resource loading result is successful, a notification that the intranet is connected will be sent. If the resource loading result is a loading failure, the VPN client is woken up to perform a connection operation, and then the process returns to the step of loading resources on the webpage according to the pre-configured intranet resource address.

3. The method for testing internal and external network connectivity according to claim 1, characterized in that, The process of loading resources on a webpage based on a pre-configured intranet resource address, and obtaining the resource loading result, includes: Obtain the resource tag and load the resource using the resource address corresponding to the resource tag; Set up a listener program to monitor the loading events corresponding to resource tags whose resource addresses are internal network resource addresses, and obtain the resource loading results.

4. The method for testing internal and external network connectivity according to claim 2, characterized in that, If the resource loading result is successful, it also includes: Obtain the system address corresponding to the target intranet application system; Open the target intranet application system based on the system address.

5. The method for testing internal and external network connectivity according to claim 1, characterized in that, The process of randomly selecting a resource tag and loading the resource on the webpage again based on the pre-configured intranet resource address yields the following resource loading results: If loading still fails, a notification indicating that the intranet is connected will be sent.

6. A terminal for testing internal and external network connections, characterized in that, Includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, performs the following steps: A preset webpage is deployed on the external network; the preset webpage is configured with relevant information to guide or remind users. Obtain at least one resource tag on the webpage, and set the resource address of the resource corresponding to the resource tag as the intranet resource address; Load resources onto the webpage based on the pre-configured intranet resource address, and obtain the resource loading result; If there are inconsistencies in the resource loading results corresponding to resource tags, then obtain all resource loading results and the time information corresponding to the resource loading results. The resource loading results are sorted according to the time information, and the latest target resource loading result is obtained. If the target resource loading result is successful, a resource tag is randomly selected and the resource is loaded on the webpage again according to the pre-configured intranet resource address to obtain the resource loading result; if the loading fails, an unstable connection prompt is output.

7. The internal / external network connection testing terminal according to claim 1, characterized in that, The process of loading resources on a webpage based on a pre-configured intranet resource address, and obtaining the resource loading result, includes: If the resource loading result is successful, a notification that the intranet is connected will be sent. If the resource loading result is a loading failure, the VPN client is woken up to perform a connection operation, and then the process returns to the step of loading resources on the webpage according to the pre-configured intranet resource address.

8. The internal / external network connection testing terminal according to claim 6, characterized in that, The process of loading resources on a webpage based on a pre-configured intranet resource address, and obtaining the resource loading result, includes: Obtain the resource tag and load the resource using the resource address corresponding to the resource tag; Set up a listener program to monitor the loading events corresponding to resource tags whose resource addresses are internal network resource addresses, and obtain the resource loading results.

9. A test terminal for internal and external network connection according to claim 7, characterized in that, If the resource loading result is successful, it also includes: Obtain the system address corresponding to the target intranet application system; Open the target intranet application system based on the system address.

10. A test terminal for internal and external network connection according to claim 6, characterized in that, The process of randomly selecting a resource tag and loading the resource on the webpage again based on the pre-configured intranet resource address yields the following resource loading results: If loading still fails, a notification indicating that the intranet is connected will be sent.

Images