CN114745434A

CN114745434A - Method, device, equipment and storage medium for proxy network request

Info

Publication number: CN114745434A
Application number: CN202210359878.9A
Authority: CN
Inventors: 王飞; 陈潼; 郝志南
Original assignee: Beijing Sankuai Online Technology Co Ltd
Current assignee: Beijing Sankuai Online Technology Co Ltd
Priority date: 2022-04-06
Filing date: 2022-04-06
Publication date: 2022-07-12

Abstract

The application discloses a method, a device, equipment and a storage medium for proxying a network request, belonging to the technical field of computers. The method comprises the following steps: responding to a network request sent by a terminal system as a DNS request, and acquiring an IP address corresponding to the DNS request based on DNS-HOOK; based on a protocol-HOOK HOOK adopted by a transport layer, sending a network request to a first target server corresponding to the IP address; and receiving a network request result sent by the first target server. When the network request is sent to the first target server, any terminal system can obtain the IP address corresponding to the first target server based on DNS-HOOK, and then any terminal system sends the network request to the first target server based on the protocol adopted by the transport layer, namely HOOK HOOK, without the support of the specific capacity of the terminal system, thereby improving the reliability of the proxy network request.

Description

Method, device, equipment and storage medium for proxy network request

Technical Field

The embodiment of the application relates to the technical field of computers, in particular to a method, a device, equipment and a storage medium for proxying a network request.

Background

The vehicle-mounted machine is a vehicle-mounted device running on a vehicle and is a customized terminal system. Since the terminal system is in a private network environment and network access is limited, the terminal system can only access an IP (Internet Protocol) address in a white list. The white list has the problems of high risk, long period of newly added white list and high maintenance cost. In the face of this situation, the network request may be proxied through the front-end processor of the end system.

In the related art, one solution is to intercept and forward a network request sent by a terminal system to a front-end processor of the terminal system through ProxyDroid (proxy robot), and then proxy the network request through the front-end processor. Another solution is to intercept and forward a Network request sent by the terminal system to a front-end processor of the terminal system through a VPN (Virtual Private Network), and then proxy the Network request through the front-end processor.

Both of the above two schemes require the support of the specific capability of the terminal system in the stage of intercepting the network request. The proxydroi proxy scheme requires root rights, but part of the terminal systems cannot open the root rights. The VPN scheme relies on a built-in VPN module of the terminal system, and a tun (point-to-point device) driver needs to be installed, and at present, part of the terminal system cannot meet the above requirements. Therefore, the two schemes have larger limitations, and the reliability of the proxy network request is reduced.

Disclosure of Invention

The embodiment of the application provides a method, a device, equipment and a storage medium for proxying a network request, which can be used for solving the problems in the related art. The technical scheme is as follows:

in one aspect, an embodiment of the present application provides a method for proxying a network request, where the method includes:

responding to a DNS (Domain Name System) request sent by a terminal System, and acquiring an IP (Internet protocol) address corresponding to the DNS request based on DNS-HOOK (Domain Name System-HOOK);

sending the network request to a first target server corresponding to the IP address based on a protocol-HOOK (protocol-HOOK) adopted by a transport layer;

and receiving a network request result sent by the first target server.

In a possible implementation manner, the obtaining an IP address corresponding to the DNS request based on DNS-HOOK includes:

sending the DNS request to a second target server based on the DNS-HOOK, wherein the second target server is used for analyzing the DNS request to obtain a corresponding IP address;

and acquiring the IP address returned by the second target server based on the DNS-HOOK.

In a possible implementation manner, the sending the network request to the first target server corresponding to the IP address based on a HOOK adopted by a transport layer includes:

and responding to the network request, sending the network request to a first target server corresponding to the IP address by adopting a Transmission Control Protocol (TCP) on a Transmission layer based on a Transmission Control Protocol (TCP-HOOK), and connecting the terminal system and the first target server through the TCP-HOOK.

In a possible implementation manner, the terminal system is connected with a first pre-processor proxy service based on the TCP-HOOK, and the first pre-processor proxy service is connected with the first target server.

responding to the network request, and sending the network request to a first target server corresponding to the IP address based on a first UDP-HOOK by adopting a UDP (User Datagram Protocol) in a transmission layer;

the receiving of the network request result sent by the first target server includes:

and receiving the network request result sent by the first target server based on a second UDP-HOOK.

In one possible implementation manner, the sending the DNS request to a second target server based on the DNS-HOOK includes:

encapsulating the DNS request as a first data packet based on the DNS-HOOK;

and sending the first data packet to the second target server based on the DNS-HOOK.

In a possible implementation manner, the obtaining the IP address returned by the second destination server based on the DNS-HOOK includes:

receiving a second data packet returned by the second target server based on the DNS-HOOK, wherein the second data packet comprises response result data corresponding to the DNS request;

and resolving the second data packet based on the DNS-HOOK to obtain the IP address.

In one possible implementation manner, the sending the network request to the first target server corresponding to the IP address based on the first UDP-HOOK includes:

packaging the network request to obtain a third data packet based on the first UDP-HOOK, and sending the third data packet to the first target server based on the first UDP-HOOK;

the receiving the network request result sent by the first target server based on the second UDP-HOOK comprises:

and analyzing a fourth data packet sent by the first target server through a second front-end processor proxy service based on the second UDP-HOOK to obtain a network request result, wherein the fourth data packet is the network request result corresponding to the third data packet.

based on the first UDP-HOOK, packaging and encrypting the data corresponding to the IP address and the network request to obtain a fifth data packet, and based on the first UDP-HOOK, sending the fifth data packet to the first target server;

and analyzing and decrypting a sixth data packet sent by the first target server through a third front-end processor proxy service based on the second UDP-HOOK to obtain the network request result, wherein the sixth data packet is the network request result corresponding to the fifth data packet.

In another aspect, an apparatus for proxying network requests is provided, the apparatus comprising:

the acquisition module is used for responding to a Domain Name System (DNS) request sent by a terminal system and acquiring an Internet Protocol (IP) address corresponding to the DNS request based on a domain name system-HOOK (DNS-HOOK);

a sending module, configured to send the network request to a first target server corresponding to the IP address based on a protocol adopted by a transport layer, namely HOOK;

and the receiving module is used for receiving the network request result sent by the first target server.

In a possible implementation manner, the obtaining module is configured to send the DNS request to a second target server based on the DNS-HOOK, where the second target server is configured to resolve the DNS request to obtain a corresponding IP address; and acquiring the IP address returned by the second target server based on the DNS-HOOK.

In one possible implementation manner, the sending module is configured to send, in response to the network request, the network request to a first destination server corresponding to the IP address based on the TCP-HOOK by using a transmission control protocol TCP at a transport layer, where the terminal system and the first destination server are connected through the TCP-HOOK.

In one possible embodiment, the terminal system connects to a first pre-processor proxy service based on the TCP-HOOK, and the first pre-processor proxy service connects to the first destination server.

In one possible implementation manner, the sending module is configured to send, in response to the network request, the network request to a first target server corresponding to the IP address based on a first UDP-HOOK by using a User Datagram Protocol (UDP) at a transport layer;

a receiving module, configured to receive the network request result sent by the first target server based on a second UDP-HOOK.

In a possible implementation manner, the obtaining module is configured to encapsulate the DNS request as a first data packet based on the DNS-HOOK; and sending the first data packet to the second target server based on the DNS-HOOK.

In a possible implementation manner, the obtaining module is configured to receive, based on the DNS-HOOK, a second data packet returned by the second target server, where the second data packet includes response result data corresponding to the DNS request; and resolving the second data packet based on the DNS-HOOK to obtain the IP address.

In a possible implementation manner, the sending module is configured to encapsulate the network request to obtain a third data packet based on the first UDP-HOOK, and send the third data packet to the first destination server based on the first UDP-HOOK;

and the receiving module is used for analyzing a fourth data packet sent by the first target server through a second front-end processor proxy service based on the second UDP-HOOK to obtain a network request result, wherein the fourth data packet is the network request result corresponding to the third data packet.

In a possible implementation manner, the sending module is configured to encapsulate and encrypt data corresponding to the IP address and the network request based on the first UDP-HOOK to obtain a fifth data packet, and send the fifth data packet to the first destination server based on the first UDP-HOOK;

and the receiving module is configured to analyze and decrypt a sixth data packet sent by the first target server through a third front-end processor proxy service based on the second UDP-HOOK to obtain the network request result, where the sixth data packet is a network request result corresponding to the fifth data packet.

In another aspect, a computer device is provided, which includes a processor and a memory, where at least one computer program is stored in the memory, and the at least one computer program is loaded by the processor and executed to enable the computer device to implement any one of the above methods for proxying network requests.

In another aspect, a computer-readable storage medium is provided, in which at least one computer program is stored, and the at least one computer program is loaded and executed by a processor, so as to make a computer implement any of the above methods for proxying network requests.

In another aspect, a computer program product or a computer program is also provided, comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions to cause the computer device to execute any one of the above proxy network request methods.

The technical scheme provided by the embodiment of the application at least has the following beneficial effects:

according to the technical scheme provided by the embodiment of the application, when the network request is sent to the first target server, any terminal system can obtain the IP address corresponding to the first target server based on DNS-HOOK, and then any terminal system sends the network request to the first target server based on the protocol adopted by the transport layer, namely HOOK HOOK. The above scheme is based on DNS-HOOK and the protocol adopted by the transport layer-HOOK to proxy the network request, without the support of the specific capability of the terminal system, thereby improving the reliability of proxy network request.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a schematic illustration of an implementation environment provided by an embodiment of the present application;

fig. 2 is a flowchart of a method for proxying a network request according to an embodiment of the present application;

fig. 3 is a flowchart of a method for acquiring an IP address according to an embodiment of the present disclosure;

FIG. 4 is a flow chart of another method for proxying network requests provided by embodiments of the present application;

FIG. 5 is a flow chart of another method for proxying a network request according to an embodiment of the present application;

fig. 6 is a schematic diagram of an apparatus for proxying a network request according to an embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram of a computer device according to an embodiment of the present disclosure;

fig. 8 is a schematic structural diagram of another computer device provided in an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

It is noted that the terms "first," "second," and the like (if any) in the description and claims of this application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

Aiming at a customized terminal system in a private network environment such as a vehicle machine (also called a vehicle-mounted terminal or vehicle-mounted equipment), and the like, because network access is limited, the embodiment of the application provides a method for acting a network request. For example, the method provided by the embodiment of the application intercepts the request of the application (App) through api transmitted by a hook system native (native) underlying network, and forwards the request to the intranet proxy service, so that the network problem brought by a private network environment is solved.

Please refer to fig. 1, which illustrates a schematic diagram of an implementation environment of a method provided in an embodiment of the present application. The implementation environment may include: a terminal system 11 and a server 12.

The terminal system 11 may send the network request to the server 12 by applying the method provided in the embodiment of the present application. The server 12 may respond to the network request to obtain a network request result, and then transmit the network request result to the terminal system 11. The terminal system 11 may receive the network request result transmitted by the server 12.

Alternatively, the terminal system 11 may be any electronic product capable of performing human-Computer interaction with a user through one or more modes of a keyboard, a touch pad, a touch screen, a remote controller, voice interaction or handwriting equipment, such as a vehicle-mounted terminal (also called a car machine), a PC (Personal Computer), a mobile phone, a smart phone, a PDA (Personal Digital Assistant), a wearable device, a PPC (Pocket PC, palmtop), a tablet Computer, a smart car machine, a smart television, a smart speaker, and the like. The server 12 may be a server, a server cluster composed of a plurality of servers, or a cloud computing service center. The terminal system 11 establishes a communication connection with the server 12 through a wired or wireless network.

It should be understood by those skilled in the art that the terminal system 11 and the server 12 are only examples, and other existing or future terminals or servers may be suitable for the present application, and are included within the scope of the present application and are incorporated herein by reference.

Based on the implementation environment shown in fig. 1, an embodiment of the present application provides a method for proxying a network request, which is applied to a terminal system as an example. As shown in fig. 2, the method provided by the embodiment of the present application may include the following steps 201 to 203.

Step 201, responding to the terminal system sending the DNS request, and acquiring the IP address corresponding to the DNS request based on DNS-HOOK.

In a possible implementation manner, when a terminal system has a need to obtain data and the like, a network request needs to be sent to a corresponding first target server, and the first target server may respond to the network request and send a corresponding network request result to the terminal system. When the terminal system only acquires the DNS corresponding to the first target server and does not acquire the IP address corresponding to the first target server, the terminal system needs to first send a DNS request to the second target server, acquire the IP address corresponding to the DNS based on the second target server, and then send a network request to the first target server corresponding to the IP address. The terminal system can obtain the IP address corresponding to the DNS request based on the DNS-HOOK.

Optionally, obtaining the IP address corresponding to the DNS request based on DNS-HOOK includes: sending a DNS request to a second target server based on DNS-HOOK, wherein the second target server is used for analyzing the DNS request to obtain a corresponding IP address; and acquiring the IP address returned by the second target server based on the DNS-HOOK.

Optionally, sending the DNS request to the second target server based on DNS-HOOK includes: encapsulating the DNS request into a first data packet based on DNS-HOOK; and sending the first data packet to a second target server based on the DNS-HOOK.

The location of the DNS-HOOK is not limited in the embodiment of the present application, and for example, the DNS-HOOK may be set in a location where the terminal system resolves the DNS request.

The method for encapsulating the DNS request by the DNS-HOOK is not limited in the embodiment of the present application, and for example, the DNS request may be encapsulated by using UDP to obtain the first data packet.

The embodiment of the present application does not limit the manner of sending the first data packet based on DNS-HOOK, and for example, the first data packet may be sent to a front-end processor of the terminal system based on DNS-HOOK, and then the front-end processor sends the first data packet to the second target server. The embodiment of this application also does not limit the manner in which the front-end processor sends the first packet, for example, the front-end processor may send the first packet to the second destination server using DNSmasq (proxy service for forwarding the first packet). The second target server may be capable of resolving the DNS request, for example, the second target server may be a 114DNS server.

Optionally, acquiring the IP address returned by the second destination server based on DNS-HOOK includes: receiving a second data packet returned by the second target server based on the DNS-HOOK, wherein the second data packet comprises response result data corresponding to the DNS request; and resolving the second data packet based on the DNS-HOOK to obtain the IP address.

In a possible implementation manner, the second target server responds to the DNS request, then encapsulates the response result data into a second data packet, sends the second data packet to the front-end processor of the terminal system, and then sends the second data packet to the DNS-HOOK by the front-end processor. Thus, the end system may receive the second packet based on DNS-HOOK. The method for encapsulating the response result data is not limited in the embodiment of the present application, and the method for encapsulating the response result data may be the same as the method for encapsulating the DNS request, for example, UDP may be used to encapsulate the response result data to obtain the second data packet.

The embodiment of the application does not limit the way of analyzing the second data packet based on the DNS-HOOK, for example, when the second data packet is a data packet encapsulated by using UDP, the DNS-HOOK may analyze the second data packet by using UDP to obtain an IP address corresponding to the DNS request.

Because the IP address corresponding to the DNS request is obtained based on DNS-HOOK, the support of any specific capability of the terminal system is not needed, any terminal system can obtain the corresponding IP address, and the reliability of the proxy network request is improved.

Step 202, based on the HOOK adopted by the transport layer, sending a network request to the first target server corresponding to the IP address.

In a possible embodiment, in the case that the IP address is known to the end system, the end system needs to send a network request to the first target server corresponding to the IP address. The terminal system may send the network request to the first target server corresponding to the IP address based on a HOOK, which is a protocol adopted by the transport layer.

In one possible embodiment, the transport layer uses a different protocol, and sends the network request to the first destination server corresponding to the IP address based on the HOOK adopted by the transport layer, including but not limited to the following two cases.

The first condition is as follows: based on a protocol-HOOK HOOK adopted by a transport layer, the method for sending the network request to the first target server corresponding to the IP address comprises the following steps: and responding to the network request, adopting TCP in a transmission layer, sending the network request to a first target server corresponding to the IP address based on TCP-HOOK, and connecting the terminal system and the first target server through TCP-HOOK.

Optionally, the terminal system is connected to a first pre-processor proxy service based on TCP-HOOK, and the first pre-processor proxy service is connected to the first destination server.

The embodiment of the present application does not limit the location of the TCP-HOOK, and for example, the TCP-HOOK may be set at the location of a connect function of the terminal system.

Illustratively, the manner in which the terminal system connects to the first pre-processor proxy service based on TCP-HOOK may be implemented by modifying, by TCP-HOOK, the IP address of the first target server and the port number of the first target server service at the connection function location to the IP address of the pre-processor of the terminal system and the port number of the first pre-processor proxy service, where the network request corresponds to the IP address of the first target server obtained in step 201. The method for obtaining the port number of the first target server service and the port number of the first front-end processor proxy service are not limited in the embodiment of the application, and for example, the port number can be obtained by terminal system configuration.

Illustratively, the connection between the first pre-processor proxy service and the first target server may be implemented by sending an IP address of the first target server and a port number of the first target server service corresponding to the network request to the first pre-processor proxy service through TCP-HOOK.

After the terminal system connects with the first pre-processor proxy service based on the TCP-HOOK and the first pre-processor proxy service connects with the first destination server, the terminal system may send a network request to the first destination server corresponding to the IP address based on the TCP-HOOK. For example, the end system may send the network request to a first pre-processor proxy service, which in turn sends the network request to a first target server. The first pre-processor proxy service needs to be able to support TCP, for example, Socks5Server (firewall security session transfer protocol 5 proxy service) may be used.

In case two, the sending the network request to the first target server corresponding to the IP address based on the HOOK adopted by the transport layer includes: and responding to the network request, adopting UDP at a transport layer, and sending the network request to a first target server corresponding to the IP address based on the first UDP-HOOK.

The embodiment of the present application does not limit the position of the first UDP-HOOK, and for example, the first UDP-HOOK may be set at the position of the sendto function of the terminal system.

Optionally, sending, based on the first UDP-HOOK, a network request to the first target server corresponding to the IP address includes: and encapsulating the network request to obtain a third data packet based on the first UDP-HOOK, and sending the third data packet to the first target server based on the first UDP-HOOK.

The first UDP-HOOK may encapsulate the network request using UDP to obtain a third data packet.

For example, the terminal system may send the third data packet to the second pre-processor proxy service based on the first UDP-HOOK, and then the second pre-processor proxy service parses the third data packet to obtain an address of the first destination server and other data included in the network request, where the address includes an IP address of the first destination server and a port number of the first destination server service. The second pre-processor proxy service may then send a network request to the first target server based on the address.

The method for sending the third data packet to the second front-end processor proxy service based on the first UDP-HOOK is not limited in the embodiment of the present application, for example, the third data packet may be sent in a manner that the first UDP-HOOK modifies an IP address of the first target server and a port number of the first target server in the sendto function position to an IP address of the front-end processor of the terminal system and a port number of the second front-end processor proxy service. Wherein the second pre-processor proxy service needs to be able to support UPD and does not need to perform encryption and decryption operations on the data therein, for example, the second pre-processor proxy service may use Socks5 Server.

Optionally, sending, based on the first UDP-HOOK, a network request to the first target server corresponding to the IP address includes: and encapsulating and encrypting the data corresponding to the IP address and the network request based on the first UDP-HOOK to obtain a fifth data packet, and sending the fifth data packet to the first target server based on the first UDP-HOOK.

Wherein the first UDP-HOOK may encapsulate the network request using UDP. In addition, the embodiment of the present application does not limit the encryption method.

For example, the terminal system may send the fifth data packet to the third pre-processor proxy service based on the first UDP-HOOK, and then the third pre-processor proxy service parses and decrypts the fifth data packet to obtain an address of the first target server and other data included in the network request, where the address includes an IP address of the first target server and a port number of the first target server service. The third pre-processor proxy service may then send a network request to the first target server based on the address.

The method for sending the fifth data packet to the third front-end processor proxy service based on the first UDP-HOOK is not limited in the embodiment of the present application, for example, the fifth data packet may be sent in a manner that the first UDP-HOOK modifies an IP address of the first target server and a port number of the first target server in the sendto function position to an IP address of the front-end processor of the terminal system and a port number of the third front-end processor proxy service. Among other things, the third pre-processor proxy service needs to be able to support UPD and needs to perform encryption and decryption operations on data therein, for example, sharwsocks 5Server (proxy service) may be used as the third pre-processor proxy service.

The embodiment of the application sends the network request to the first target server corresponding to the IP address based on the HOOK which is a protocol adopted by a transport layer, and can enable any terminal to send the network request to the first target server without the support of any specific capability of a terminal system, thereby improving the reliability of the proxy network request.

Step 203, receiving the network request result sent by the first target server.

In a possible implementation manner, the case of sending the network request satisfies the above-mentioned case one, and optionally, receiving a result of the network request sent by the first target server includes:

the first target server sends the network request result to the first front-end proxy service, and then the first front-end proxy service sends the received network request result to the terminal system.

In a possible implementation, the case of sending the network request satisfies the second case, optionally, receiving a result of the network request sent by the first target server includes: and receiving the network request result sent by the first target server based on the second UDP-HOOK.

The location of the second UDP-HOOK is not limited in the embodiments of the present application, and for example, the second UDP-HOOK may be set at the location of a recvfrom function of the terminal system.

Optionally, in a case where the third packet is sent to the first destination server based on the first UDP-HOOK, receiving, based on the second UDP-HOOK, a network request result sent by the first destination server, including: and analyzing a fourth data packet sent by the first target server through the second front-end processor proxy service based on the second UDP-HOOK to obtain a network request result, wherein the fourth data packet is the network request result corresponding to the third data packet.

Illustratively, the first target server responds to the network request and sends network request response data to the second front-end proxy service, and the second front-end proxy service encapsulates the network request response data to obtain a fourth data packet and sends the fourth data packet to the second UDP-HOOK. The second front-end proxy service may encapsulate the network request response data using UDP. The second UDP-HOOK may parse the fourth packet, and the end system may then receive the network request result based on the second UDP-HOOK.

Optionally, in a case where the fifth packet is sent to the first destination server based on the first UDP-HOOK, receiving, based on the second UDP-HOOK, a network request result sent by the first destination server, including: and analyzing and decrypting a sixth data packet sent by the first target server through the third front-end processor proxy service based on the second UDP-HOOK to obtain a network request result, wherein the sixth data packet is the network request result corresponding to the fifth data packet.

Illustratively, the first target server responds to the network request and sends network request response data to the third front-end proxy service, and the third front-end proxy service encapsulates and encrypts the network request response data to obtain a sixth data packet and sends the sixth data packet to the second UDP-HOOK. The second front-end proxy service may encapsulate the network request response data using UDP. The second UDP-HOOK may decrypt and parse the sixth data packet, and the end system may then receive the network request result based on the second UDP-HOOK.

In this embodiment of the present application, when sending the network request to the first target server, any terminal system may first obtain the IP address corresponding to the first target server based on DNS-HOOK, and then send the network request to the first target server based on a protocol adopted by a transport layer, that is, HOOK-HOOK. The above scheme is based on DNS-HOOK and the protocol adopted by the transport layer-HOOK to proxy the network request, without the support of the specific capability of the terminal system, thereby improving the reliability of proxy network request. Even if the terminal system is in a private network environment, the terminal system can be free from network access limitation, the private network limitation under the vehicle-mounted service scene is broken through, the follow-up vehicle-mounted service is not limited by the private network, and the network problem brought by the private network environment is solved.

Referring to fig. 3, an embodiment of the present application provides a method for acquiring an IP address, where the method includes steps 301 to 310.

301, the end system sends a DNS request.

And 302, responding to the DNS request sent by the terminal system, and acquiring an IP address corresponding to the DNS request based on the DNS-HOOK. The terminal system encapsulates the DNS-HOOK request as a first data packet based on DNS-HOOK.

303, the front-end processor receives the DNS request. I.e. the front-end processor receives the first data packet.

The front-end processor forwards the DNS request based on DNSmasq 304. I.e. the front-end processor sends a DNS request (first packet) to the second destination server.

The second destination server resolves 305 the DNS request, i.e. resolves the first data packet.

The second destination server returns the second packet to the front-end processor 306.

307, the front-end processor receives and returns the second packet to DNS-HOOK.

308, the terminal system resolves the second data packet based on the DNS-HOOK.

309, the terminal system obtains the IP address based on DNS-HOOK and returns the IP address to the terminal system.

The end system sends a network request through the IP address 310.

The terminal system obtains an IP address corresponding to the DNS request based on DNS-HOOK, and then the terminal system may send a network request to the first destination server corresponding to the IP address.

The implementation manners of the method steps provided in fig. 3 can all refer to step 201 described above, and are not described herein again.

Referring to fig. 4, an embodiment of the present application provides a method for proxying a network request, taking a protocol adopted by a transport layer as TCP as an example, and the method includes steps 401 to 413.

401, the end system creates a socket instance.

At 402, TCP-HOOK is set at the location of the connect function of the end system.

403, the terminal system connects Socks5Server based on TCP-HOOK. The implementation of this step can be referred to above as step 202, and is not described here again.

404, the Socks5Server establishes connection with the terminal system. The implementation of this step can be referred to above as step 202, and is not described here again.

The end system sends 405 the destination address to Socks5Server based on TCP-HOOK. The destination address includes an IP address of the first destination server and a port number serviced by the first destination server. The implementation of this step can be referred to above as step 202, and is not described here again.

406, Socks5Server connects to the first target Server. The implementation of this step can be referred to above as step 202, and is not described here again.

407, the first target Server establishes a connection with Socks5 Server. The implementation of this step can be referred to above as step 202, and is not described here again.

408, the end system sends a network request to Socks5 Server. The implementation of this step can be referred to above as step 202, and is not described here again.

409, Socks5Server sends the network request to the first target Server. The implementation of this step can be referred to above as step 202, and is not described here again.

The first target server receives 410 a network request.

411, the first target Server sends the network request result to Socks5 Server. The first target Server responds to the network request and sends a network request result to the Socks5Server based on the connection of the first target Server and the Socks5 Server.

412, the Socks5Server sends the network request result to the terminal system. And the Socks5Server transmits the network request result to the terminal system based on the connection between the Socks5Server and the terminal system.

413, the end system receives the network request result.

Referring to fig. 5, an embodiment of the present application provides a method for proxying a network request, taking a protocol adopted by a transport layer as UDP as an example, and the method includes steps 501 to 513.

501, the terminal system creates a socket instance.

The end system sends a network request 502.

And 503, the terminal system encapsulates and encrypts the IP address and the network request based on the first UDP-HOOK to obtain a fifth data packet. Exemplarily, the first UDP-HOOK may be set at the location of the sendto function of the end system. The implementation of this step can be referred to above as step 202, and is not described here again.

The end system sends 504 a fifth packet to the sharowskks 5Server based on the first UDP-HOOk. The implementation of this step can be referred to above as step 202, and is not described here again.

505, the sharowclocks 5Server decrypts and analyzes the fifth data packet to obtain other data with the IP address corresponding to the network request. The implementation of this step can be referred to above as step 202, and is not described here again.

506, the Shadowclocks 5Server sends a network request to the first target Server. The implementation of this step can be referred to above as step 202, and is not described here again.

At 507, the first target server receives the network request.

508, the first target Server sends the network request result to the Shadowclocks 5 Server. The implementation manner of this step can be referred to the above step 203, and is not described herein again.

509, the sharowclocks 5Server encapsulates and encrypts the network request result to obtain a sixth data packet. The implementation manner of this step can be referred to the above step 203, and is not described herein again.

510, Shadowclocks 5Server sends the sixth packet to UDP-HOOK. The implementation manner of this step can be referred to the above step 203, and is not described herein again.

And 511, the terminal system decrypts and analyzes the sixth data packet based on the UDP-HOOK to obtain a network request result. The second UDP-HOOK may be placed, for example, at the location of the recvfrom function of the end system. The implementation manner of this step can be referred to the above step 203, and is not described herein again.

And 512, the terminal system sends the network request result to the terminal system based on the UDP-HOOK. The implementation manner of this step can be referred to the above step 203, and is not described herein again.

513, the end system receives the network request result.

Referring to fig. 6, an embodiment of the present application provides an apparatus for proxying a network request, where the apparatus includes:

an obtaining module 601, configured to respond to a DNS request sent by a terminal system, and obtain an IP address corresponding to the DNS request based on DNS-HOOK;

a sending module 602, configured to send a network request to a first target server corresponding to the IP address based on a HOOK adopted by the transport layer;

the receiving module 603 is configured to receive a network request result sent by the first target server.

Optionally, the obtaining module 601 is configured to send a DNS request to a second target server based on DNS-HOOK, where the second target server is configured to resolve the DNS request to obtain a corresponding IP address; and acquiring the IP address returned by the second target server based on the DNS-HOOK.

Optionally, the sending module 602 is configured to send, in response to the network request, the network request to the first target server corresponding to the IP address based on TCP-HOOK by using TCP at a transport layer, where the terminal system is connected to the first target server through TCP-HOOK.

Optionally, the terminal system is connected with a first pre-processor proxy service based on TCP-HOOK, and the first pre-processor proxy service is connected with the first target server.

Optionally, the sending module 602 is configured to send, in response to the network request, a network request to the first target server corresponding to the IP address based on the first UDP-HOOK by using UDP in the transport layer;

a receiving module 603, configured to receive a network request result sent by the first target server based on the second UDP-HOOK.

Optionally, the obtaining module 601 is configured to encapsulate the DNS request as a first data packet based on DNS-HOOK; and sending the first data packet to a second target server based on the DNS-HOOK.

Optionally, the obtaining module 601 is configured to receive a second data packet returned by the second target server based on DNS-HOOK, where the second data packet includes response result data corresponding to the DNS request; and resolving the second data packet based on the DNS-HOOK to obtain the IP address.

Optionally, the sending module 602 is configured to obtain a third data packet based on the first UDP-HOOK encapsulation network request, and send the third data packet to the first target server based on the first UDP-HOOK;

the receiving module 603 is configured to analyze a fourth data packet sent by the first target server through the second front-end processor proxy service based on the second UDP-HOOK to obtain a network request result, where the fourth data packet is a network request result corresponding to the third data packet.

Optionally, the sending module 602 is configured to encapsulate and encrypt data corresponding to the IP address and the network request based on the first UDP-HOOK to obtain a fifth data packet, and send the fifth data packet to the first target server based on the first UDP-HOOK;

a receiving module 603, configured to analyze and decrypt a sixth data packet sent by the first target server through the third front-end processor proxy service based on the second UDP-HOOK to obtain a network request result, where the sixth data packet is a network request result corresponding to the fifth data packet.

In this embodiment of the present application, when sending the network request to the first target server, any terminal system may first obtain the IP address corresponding to the first target server based on DNS-HOOK, and then send the network request to the first target server based on the HOOK adopted by the transport layer. The scheme is based on DNS-HOOK and HOOK adopted by a transport layer to proxy the network request, the support of specific capability of a terminal system is not needed, and the reliability of the proxy network request is improved.

It should be noted that, when the apparatus provided in the foregoing embodiment implements the functions thereof, only the division of the functional modules is illustrated, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the apparatus may be divided into different functional modules to implement all or part of the functions described above. In addition, the apparatus and method embodiments provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments for details, which are not described herein again.

Fig. 7 is a schematic structural diagram of a computer device provided in this embodiment, where the server may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 701 and one or more memories 702, where the one or more memories 702 store at least one computer program, and the at least one computer program is loaded and executed by the one or more processors 701, so as to enable the server to implement the proxy network request method provided in the foregoing method embodiments. Of course, the server may also have components such as a wired or wireless network interface, a keyboard, and an input/output interface, so as to perform input/output, and the server may also include other components for implementing the functions of the device, which are not described herein again.

Fig. 8 is a schematic structural diagram of a computer device according to an embodiment of the present application. The device may be a terminal, and may be, for example: a vehicle-mounted terminal (also called a car machine), a smart phone, a tablet computer, an MP3(Moving Picture Experts Group Audio Layer III, motion video Experts compression standard Audio Layer III) player, an MP4(Moving Picture Experts Group Audio Layer IV, motion video Experts compression standard Audio Layer 4) player, a notebook computer or a desktop computer. A terminal may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, etc.

Generally, a terminal includes: a processor 801 and a memory 802.

The processor 801 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so forth. The processor 801 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 801 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 801 may be integrated with a GPU (Graphics Processing Unit) which is responsible for rendering and drawing the content required to be displayed by the display screen. In some embodiments, the processor 801 may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.

Memory 802 may include one or more computer-readable storage media, which may be non-transitory. Memory 802 may also include high speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in the memory 802 is used for storing at least one instruction for execution by the processor 801 to cause the terminal to implement the method for proxying network requests provided by the method embodiments herein.

In some embodiments, the terminal may further optionally include: a peripheral interface 803 and at least one peripheral. The processor 801, memory 802 and peripheral interface 803 may be connected by bus or signal lines. Various peripheral devices may be connected to peripheral interface 803 by a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of a radio frequency circuit 804, a display 805, a camera assembly 806, an audio circuit 807, a positioning assembly 808, and a power supply 809.

The peripheral interface 803 may be used to connect at least one peripheral related to I/O (Input/Output) to the processor 801 and the memory 802. In some embodiments, the processor 801, memory 802, and peripheral interface 803 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 801, the memory 802, and the peripheral interface 803 may be implemented on separate chips or circuit boards, which are not limited by this embodiment.

The Radio Frequency circuit 804 is used for receiving and transmitting RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuitry 804 communicates with communication networks and other communication devices via electromagnetic signals. The rf circuit 804 converts an electrical signal into an electromagnetic signal to be transmitted, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 804 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuit 804 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: metropolitan area networks, various generation mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the radio frequency circuit 804 may further include NFC (Near Field Communication) related circuits, which are not limited in this application.

The display screen 805 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display 805 is a touch display, the display 805 also has the ability to capture touch signals on or above the surface of the display 805. The touch signal may be input to the processor 801 as a control signal for processing. At this point, the display 805 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the display 805 may be one, disposed on a front panel of the terminal; in other embodiments, the display 805 may be at least two, which are respectively disposed on different surfaces of the terminal or in a folding design; in other embodiments, the display 805 may be a flexible display, disposed on a curved surface or on a folded surface of the terminal. Even further, the display 805 may be configured as a non-rectangular irregular figure, i.e., a shaped screen. The Display 805 can be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), and other materials.

The camera assembly 806 is used to capture images or video. Optionally, camera assembly 806 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments, camera assembly 806 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp and can be used for light compensation under different color temperatures.

The audio circuit 807 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 801 for processing or inputting the electric signals to the radio frequency circuit 804 to achieve voice communication. For the purpose of stereo sound collection or noise reduction, a plurality of microphones can be arranged at different parts of the terminal respectively. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 801 or the radio frequency circuit 804 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, the audio circuitry 807 may also include a headphone jack.

The positioning component 808 is used to locate the current geographic Location of the terminal to implement navigation or LBS (Location Based Service). The Positioning component 808 may be a Positioning component based on the GPS (Global Positioning System) in the united states, the beidou System in china, the graves System in russia, or the galileo System in the european union.

The power supply 809 is used to supply power to various components in the terminal. The power supply 809 can be ac, dc, disposable or rechargeable. When the power source 809 comprises a rechargeable battery, the rechargeable battery may support wired or wireless charging. The rechargeable battery may also be used to support fast charge technology.

In some embodiments, the terminal also includes one or more sensors 810. The one or more sensors 810 include, but are not limited to: acceleration sensor 811, gyro sensor 812, pressure sensor 813, fingerprint sensor 814, optical sensor 815 and proximity sensor 816.

The acceleration sensor 811 may detect the magnitude of acceleration in three coordinate axes of a coordinate system established with the terminal. For example, the acceleration sensor 811 may be used to detect components of the gravitational acceleration in three coordinate axes. The processor 801 may control the display 805 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 811. The acceleration sensor 811 may also be used for acquisition of motion data of a game or a user.

The gyro sensor 812 may detect a body direction and a rotation angle of the terminal, and the gyro sensor 812 may cooperate with the acceleration sensor 811 to acquire a 3D motion of the user with respect to the terminal. From the data collected by the gyro sensor 812, the processor 801 may implement the following functions: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.

Pressure sensors 813 may be disposed on the side frames of the terminal and/or underneath the display 805. When the pressure sensor 813 is arranged on the side frame of the terminal, the holding signal of the user to the terminal can be detected, and the processor 801 performs left-right hand identification or shortcut operation according to the holding signal collected by the pressure sensor 813. When the pressure sensor 813 is disposed at a lower layer of the display screen 805, the processor 801 controls the operability control on the UI interface according to the pressure operation of the user on the display screen 805. The operability control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.

The fingerprint sensor 814 is used for collecting a fingerprint of the user, and the processor 801 identifies the identity of the user according to the fingerprint collected by the fingerprint sensor 814, or the fingerprint sensor 814 identifies the identity of the user according to the collected fingerprint. Upon identifying that the user's identity is a trusted identity, the processor 801 authorizes the user to perform relevant sensitive operations including unlocking a screen, viewing encrypted information, downloading software, paying for and changing settings, etc. The fingerprint sensor 814 may be disposed on the front, back, or side of the terminal. When a physical button or a manufacturer Logo (trademark) is provided on the terminal, the fingerprint sensor 814 may be integrated with the physical button or the manufacturer Logo.

The optical sensor 815 is used to collect the ambient light intensity. In one embodiment, processor 801 may control the display brightness of display 805 based on the ambient light intensity collected by optical sensor 815. Specifically, when the ambient light intensity is high, the display brightness of the display screen 805 is increased; when the ambient light intensity is low, the display brightness of the display 805 is reduced. In another embodiment, the processor 801 may also dynamically adjust the shooting parameters of the camera assembly 806 based on the ambient light intensity collected by the optical sensor 815.

A proximity sensor 816, also called a distance sensor, is typically provided on the front panel of the terminal. The proximity sensor 816 is used to collect the distance between the user and the front face of the terminal. In one embodiment, when the proximity sensor 816 detects that the distance between the user and the front surface of the terminal is gradually reduced, the display 805 is controlled by the processor 801 to switch from a bright screen state to a dark screen state; when the proximity sensor 816 detects that the distance between the user and the front face of the terminal is gradually increased, the display 805 is controlled by the processor 801 to switch from a rest screen state to a bright screen state.

Those skilled in the art will appreciate that the configuration shown in fig. 8 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be used.

In an exemplary embodiment, a computer device is also provided, the computer device comprising a processor and a memory, the memory having at least one computer program stored therein. The at least one computer program is loaded and executed by one or more processors to cause the computer device to perform any of the methods described above for proxying network requests.

In an exemplary embodiment, a computer-readable storage medium is also provided, in which at least one computer program is stored, the at least one computer program being loaded and executed by a processor of a computer device to cause the computer to implement any of the above methods for proxying network requests.

In one possible implementation, the computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a Compact Disc Read-Only Memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, and the like.

In an exemplary embodiment, a computer program product or computer program is also provided, the computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform any of the above methods of proxying network requests.

It should be noted that the information, data and signals referred to in this application are all authorized by the user or fully authorized by each party, and the collection, use and processing of the relevant data need to comply with relevant laws and regulations and standards in relevant countries and regions. For example, the data, the first data packet, the second data packet, the third data packet, the IP address, the identity of the user, and the like, acquired by the terminal system referred to in this application are all acquired under sufficient authorization.

It should be understood that reference to "a plurality" herein means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

The above description is only exemplary of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like that are made within the principles of the present application should be included in the protection scope of the present application.

Claims

1. A method of proxying network requests, the method comprising:

responding to a Domain Name System (DNS) request sent by a terminal system, and acquiring an Internet Protocol (IP) address corresponding to the DNS request based on a Domain Name System (DNS) -HOOK (HOOK);

sending the network request to a first target server corresponding to the IP address based on a protocol (HOOK HOOK) adopted by a transport layer;

and receiving a network request result sent by the first target server.

2. The method according to claim 1, wherein the obtaining an internet protocol IP address corresponding to the DNS request based on a domain name system-HOOK, DNS-HOOK, comprises:

3. The method of claim 1, wherein sending the network request to the first target server corresponding to the IP address based on a HOOK adopted by the transport layer comprises:

and responding to the network request, adopting a Transmission Control Protocol (TCP) at a transmission layer, sending the network request to a first target server corresponding to the IP address based on the TCP-HOOK, and connecting the terminal system and the first target server through the TCP-HOOK.

4. The method of claim 3, wherein the end system connects to a first pre-processor proxy service based on the TCP-HOOK, and wherein the first pre-processor proxy service connects to the first destination server.

5. The method of claim 1, wherein sending the network request to the first target server corresponding to the IP address based on a HOOK adopted by the transport layer comprises:

responding to the network request, adopting a User Datagram Protocol (UDP) at a transmission layer, and sending the network request to a first target server corresponding to the IP address based on a first UDP-HOOK;

6. The method of claim 2, wherein sending the DNS request to a second target server based on the DNS-HOOK comprises:

encapsulating the DNS request as a first data packet based on the DNS-HOOK;

7. The method of claim 2, wherein the obtaining the IP address returned by the second destination server based on the DNS-HOOK comprises:

8. The method of claim 5, wherein sending the network request to the first target server corresponding to the IP address based on the first UDP-HOOK comprises:

9. The method of claim 5, wherein sending the network request to the first target server corresponding to the IP address based on the first UDP-HOOK comprises:

10. A proxy network request device, the device comprising:

the acquisition module is used for responding to a Domain Name System (DNS) request sent by a terminal system and acquiring an Internet Protocol (IP) address corresponding to the DNS request based on a Domain Name System (DNS) -HOOK;

11. A computer device comprising a processor and a memory, the memory having stored therein at least one computer program, the at least one computer program being loaded and executed by the processor to cause the computer device to perform the method of proxying network requests according to any one of claims 1 to 9.

12. A computer-readable storage medium, having stored therein at least one computer program, which is loaded and executed by a processor, to cause a computer to implement the method of proxying network requests according to any one of claims 1 to 9.

13. A computer program product, characterized in that it comprises a computer program or computer instructions, which is loaded and executed by a processor, to cause a computer to implement a method of proxying network requests according to any one of claims 1 to 9.