CN108494860B

CN108494860B - WEB access system, WEB access method and device for client

Info

Publication number: CN108494860B
Application number: CN201810265512.9A
Authority: CN
Inventors: 邱晓娜; 王正意
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2018-03-28
Filing date: 2018-03-28
Publication date: 2021-08-27
Anticipated expiration: 2038-03-28
Also published as: CN108494860A

Abstract

The embodiment of the application discloses a WEB access system, a WEB access method and a device for a client. One embodiment of the system comprises: the system comprises a routing end, a domain name resolution end and a proxy server end, wherein: the route end is used for responding to a received request of the client for acquiring the DNS server address and returning the preferred DNS server information of the route end to the client, wherein the preferred DNS server information of the route end is the IP address of the domain name resolution end; the domain name resolution end is used for responding to a received domain name resolution request of the client and returning the IP address of the proxy server to the client; the agent server is used for processing the WEB access request received from the client and returning a processing result to the client. The implementation mode realizes that the client side carries out WEB access through the proxy server side.

Description

WEB access system, WEB access method and device for client

Technical Field

The embodiment of the application relates to the technical field of computers, in particular to a WEB access system, a WEB access method for a client and a device.

Background

With the continuous development of internet technology, the traffic consumption of the client becomes one of the concerns of the user.

At present, there are two methods for acquiring client traffic. One is to count the size of the data volume by capturing the WEB (World Wide WEB) access request and the return data sent by the client through a third-party tool (e.g., Charles (is an HTTP proxy), Fiddler (is an HTTP protocol debugging proxy), Wireshark (is an ethernet packet analysis software), TcpDump (a network data collection analysis tool in Linux), etc.). The other method is to obtain the data size of the WEB access request and the return data of the application by reading the system file of the client.

Disclosure of Invention

The embodiment of the application provides a WEB access system, a WEB access method for a client and a device.

In a first aspect, an embodiment of the present application provides a WEB access system, where the system includes: the system comprises a routing end, a domain name resolution end and a proxy server end, wherein: the route end is used for responding to a received request of the client for acquiring the DNS server address and returning the preferred DNS server information of the route end to the client, wherein the preferred DNS server information of the route end is the IP address of the domain name resolution end; the domain name resolution end is used for responding to a received domain name resolution request of the client and returning the IP address of the proxy server to the client; the agent server is used for processing the WEB access request received from the client and returning a processing result to the client.

In some embodiments, the agent server is further configured to determine data traffic consumed by the WEB access request and data traffic consumed by the processing result.

In some embodiments, the proxy server is further configured to generate a processing result based on the WEB access request.

In some embodiments, the proxy server is specifically configured to: determining an IP address corresponding to domain name information in the WEB access request through a DNS (domain name server); forwarding the WEB access request to a WEB server corresponding to the determined IP address; and returning the processing result of the WEB access request received from the WEB server to the client.

In a second aspect, an embodiment of the present application provides a WEB access method for a client, where the client is communicatively connected to a router, and the method includes: receiving a WEB access request, wherein the WEB access request comprises domain name information; acquiring system DNS server information of a routing end, wherein the preferred DNS server information of the routing end is configured to be an IP address of a domain name resolution end; sending the domain name information to a domain name resolution end, wherein the domain name resolution end is used for returning the IP address of the proxy server end to the client end; sending the WEB access request to an agent server; and receiving a processing result of the WEB access request from the agent server.

In some embodiments, the method further comprises: acquiring data traffic consumed by a WEB access request and data traffic consumed by a processing result, which are determined by an agent server; and updating the data traffic information of the client based on the data traffic consumed by the WEB access request and the data traffic consumed by the processing result.

In some embodiments, the processing result is generated by the proxy server based on the WEB access request.

In some embodiments, the processing result is obtained by the proxy server side through the following steps: determining an IP address corresponding to the domain name information through a DNS server; forwarding the WEB access request to a WEB server corresponding to the determined IP address; and receiving a processing result of the WEB access request from the WEB server.

In some embodiments, the method further comprises: and recording the domain name information, the data traffic consumed by the WEB access request and the data traffic consumed by the processing result into a data traffic log.

In a third aspect, an embodiment of the present application provides a WEB access apparatus for a client, where the apparatus includes: the request receiving unit is configured to receive a WEB access request, and the WEB access request comprises domain name information; the system comprises a DNS acquisition unit, a DNS acquisition unit and a DNS processing unit, wherein the DNS acquisition unit is configured to acquire preferred DNS server information of a routing end, and the preferred DNS server information of the routing end is configured to be an IP address of a domain name resolution end; the domain name resolution unit is configured to send domain name information to a domain name resolution end, and the domain name resolution end is used for returning the IP address of the proxy server to the client; the request sending unit is configured to send the WEB access request to the proxy server; and the result receiving unit is configured to receive a processing result of the WEB access request from the proxy server.

In some embodiments, the apparatus further comprises: the flow determining unit is configured to acquire data flow consumed by the WEB access request and data flow consumed by the processing result, which are determined by the proxy server; and the flow updating unit is configured to update the data flow information of the client based on the data flow consumed by the WEB access request and the data flow consumed by the processing result.

In some embodiments, the apparatus further comprises: and the log unit is configured to record the domain name information, the data traffic consumed by the WEB access request and the data traffic consumed by the processing result into a data traffic log.

In a fourth aspect, an embodiment of the present application provides an electronic device, including: one or more processors; storage means for storing one or more programs; when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method as described in any implementation of the second aspect.

In a fifth aspect, the present application provides a computer-readable medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the method as described in any implementation manner of the second aspect.

According to the WEB access system, the WEB access method and the WEB access device for the client, the preferred DNS server information is configured into the routing end of the IP address of the domain name resolution end, the domain name resolution end which resolves the domain name information into the IP address of the proxy server end and the proxy server end which receives the WEB access request and returns the processing result, the client is enabled to carry out WEB access through the proxy server end, and therefore the WEB access request of the client can be monitored and managed under the condition that the system permission of the client is not required to be obtained, and the WEB access method and the device are not limited by the network protocol of the WEB access request.

Drawings

Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:

FIG. 1 is an exemplary architecture diagram of a Web access system according to the present application;

FIG. 2 is a timing diagram of one embodiment of a WEB access system according to the present application;

FIG. 3 is a flow diagram of one embodiment of a WEB access method for a client according to the present application;

FIG. 4 is a schematic diagram of an application scenario of a WEB access method for a client according to the present application;

FIG. 5 is a schematic block diagram illustrating an embodiment of a WEB access device for a client according to the present application;

FIG. 6 is a schematic block diagram of a computer system suitable for use in implementing an electronic device according to embodiments of the present application.

Detailed Description

The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.

It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.

FIG. 1 illustrates an exemplary architecture 100 of a WEB access system according to the present application.

As shown in fig. 1, the system architecture 100 may include a client 101, a network 102, a routing side 103, a domain name resolution side 104, and a proxy server 105. Network 102 serves as a medium for providing communication links between clients 101, routing peers 103, domain name resolution peers 104, and proxy servers 105. Network 102 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

A user may use a client 101 to interact with a routing peer 103, a domain name resolution peer 104, a proxy server 105, to receive or send messages, etc., over a network 102. The client 101 may have various communication client applications installed thereon, such as a terminal management application, a web browser application, a shopping application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like.

The client 101 may be hardware or software. When the client 101 is hardware, it may be various electronic devices having a display screen and supporting WEB access, including but not limited to a smart phone, a tablet computer, an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III, motion Picture Experts Group Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer IV, motion Picture Experts Group Audio Layer 4), a laptop computer, a desktop computer, and the like. When the client 101 is software, it can be installed in the electronic devices listed above. It may be implemented as multiple pieces of software or software modules (e.g., to provide distributed services) or as a single piece of software or software module. And is not particularly limited herein.

The router 103 may be a routing device configured with preferred DNS (Domain Name System) server information, including but not limited to a router, a set-top box, and the like. The routing end 103 may receive a request for the client 101 to obtain the DNS server address, and return an IP (Internet Protocol) address of the domain name resolution end 104 to the client 101.

The domain name resolution end 104 may be a server providing domain name resolution, and the domain name resolution end 104 may receive domain name information sent by the client 101 and return the IP address of the proxy server 105 to the client 101.

The proxy server 105 may be a server providing a WEB access proxy service, and the proxy server 105 may perform processing such as monitoring and forwarding on a WEB access request sent by the client 101, and return a processing result (for example, return data, data traffic, and the like) to the client 101.

It should be noted that, the WEB access method for the client provided in the embodiment of the present application is generally executed by the client 101, and accordingly, the WEB access apparatus for the client is generally disposed in the client 101.

It should be noted that the routing end, the domain name resolution end, and the proxy server end may be hardware or software. When the routing end, the domain name resolution end and the proxy server end are hardware, a distributed device cluster formed by a plurality of devices can be realized, and a single device can also be realized. When the router, the domain name resolution node, and the proxy server are software, they may be implemented as multiple software or software modules (for example, to provide distributed services), or as a single software or software module, and are not limited herein.

It should be understood that the number of clients, networks, routing ends, domain name resolution ends, and proxy servers in fig. 1 are merely illustrative. There may be any number of clients, networks, routing terminals, domain name resolution terminals, and proxy servers, as desired for implementation.

With continued reference to FIG. 2, a timing diagram 200 of one embodiment of a WEB access system according to the present application is shown.

The WEB access system of this embodiment includes: the system comprises a routing end, a domain name resolution end and a proxy server end. The route end is used for responding to a received request of a client for acquiring a DNS server address and returning preferred DNS server information of the route end to the client, wherein the preferred DNS server information of the route end is an IP address of a domain name resolution end; the domain name resolution end is used for responding to a received domain name resolution request of the client and returning the IP address of the proxy server to the client; the agent server is used for processing the WEB access request received from the client and returning a processing result to the client.

As shown in fig. 2, in step 201, the client receives a WEB access request containing domain name information.

In this embodiment, a client (e.g., the client 101 shown in fig. 1) may receive a WEB access request input by a user, where the WEB access request includes domain name information. Here, the WEB access refers to a network service that performs data interaction by a network Protocol (for example, HTTP (Hypertext Transfer Protocol), HTTPs (Secure Hypertext Transfer Protocol), or the like). A Domain Name (Domain Name) refers to the Name of a certain computer or group of computers of the internet (e.g., "www.domain.com") that is a string of characters separated by ". times", and is used to identify the electronic location of the computer when data is exchanged. In general, a domain name represents an IP resource, such as a personal computer used to access the internet, a server computer hosting a website, or the website itself or any other service delivered over the internet. The user may input a WEB access request to the client via an input device (e.g., a touch screen, a mouse, a keyboard, etc.).

In step 202, the client sends an acquisition request of the DNS server address to the router.

In this embodiment, a client (e.g., the client 101 shown in fig. 1) may send a request to a routing end (e.g., the routing end 103 shown in fig. 1) through a wired connection manner or a wireless connection manner, and acquire a DNS server address (e.g., an IP address) so as to resolve domain name information in a WEB access request.

In some optional implementations of this embodiment, the routing end is a wireless router. The client (e.g., a smart phone, a tablet computer, etc.) may be in communication connection with the wireless router through a wireless connection. The wireless connection means may include, but is not limited to, a 3G/4G connection, a WiFi connection, a bluetooth connection, a WiMAX connection, a Zigbee connection, a uwb (ultra wideband) connection, and other wireless connection means now known or developed in the future.

In step 203, the router returns the IP address of the domain name resolution end to the client.

In this embodiment, in response to receiving an acquisition request of a DNS server address, a routing end (e.g., the routing end 103 shown in fig. 1) returns preferred DNS server address information to a client (e.g., the client 101 shown in fig. 1), where the preferred DNS server address information of the routing end is configured as an IP address of a domain name resolution end (e.g., the domain name resolution end 104 shown in fig. 1).

In step 204, the client sends the domain name information in the WEB access request to the domain name resolution end.

In this embodiment, based on the received preferred DNS server address information (i.e., the IP address of the domain name resolution server) of the router (e.g., the router 103 in fig. 1), the client (e.g., the client 101 in fig. 1) sends a domain name resolution request to the domain name resolution server (e.g., the domain name resolution server 104 in fig. 1), where the domain name resolution request includes the domain name information (e.g., "www.domain.com") included in the WEB access request.

In step 205, the domain name resolution end returns the IP address of the proxy server to the client.

In this embodiment, in response to receiving the domain name resolution request, the domain name resolution end (e.g., the domain name resolution end 104 shown in fig. 1) may return the IP address of the proxy server (e.g., the proxy server 105 shown in fig. 1) to the client (e.g., the client 101 shown in fig. 1).

Here, the domain name resolution side does not resolve the received domain name information, but directly returns the IP address of the proxy server to the client. That is, the client receives the IP address of the proxy server no matter what domain name information the client sends to the domain name resolution server.

In step 206, the client sends the WEB access request to the proxy server.

In this embodiment, based on the received IP address of the proxy server, the client (e.g., the client 101 shown in fig. 1) sends the WEB access request input by the user to the proxy server (e.g., the proxy server 105 shown in fig. 1).

In step 207, the proxy server returns the processing result to the client.

In this embodiment, the proxy server (e.g., the proxy server 105 shown in fig. 1) may process the WEB access request received in step 206, and then return the processing result to the client (e.g., the client 101 shown in fig. 1).

As can be seen from steps 201 to 207, in the WEB access system provided in this embodiment of the present application, the preferred DNS server information is configured as a routing end for a domain name resolution end IP address, a domain name resolution end for resolving domain name information into a proxy server IP address, and a proxy server for receiving a WEB access request and returning a processing result, so that a client performs WEB access via the proxy server, and thus, the WEB access request of the client can be monitored and managed without acquiring a client system permission, and is not limited by a network protocol of the WEB access request. For example, WEB access requests and processing results transmitted in a custom network protocol may be monitored.

Since the IP address of the proxy server is not obtained by analyzing the domain name information (that is, the proxy server is not a WEB server corresponding to the domain name information in the WEB access request), in practical applications, the proxy server generally needs to perform domain name analysis, request forwarding, and other processing on the received WEB access request.

In some optional implementation manners of this embodiment, the proxy server is specifically configured to: determining an IP address corresponding to the domain name information in the WEB access request through a DNS (domain name server); forwarding the WEB access request to a WEB server corresponding to the determined IP address; and returning the processing result of the WEB access request received from the WEB server to the client.

In some optional implementation manners of this embodiment, the proxy server is further configured to: and determining the data traffic consumed by the WEB access request and the data traffic consumed by the processing result. The proxy server may store the data traffic consumed by the WEB access request and the data traffic consumed by the processing result locally, so as to be acquired by a client (which may be the client or another client) and/or another server. For example, the data traffic consumed by the WEB access request and the data traffic consumed by the processing result may be returned to the client, so that the client updates the data traffic information; the data traffic consumed by the WEB access request and the data traffic consumed by the processing result may also be returned to other clients (for example, a PC) for presentation, analysis, and the like. In this implementation manner, the WEB access system of this embodiment can determine the data traffic consumed by the client through the proxy server, thereby improving the accuracy of the data traffic information of the client.

In some optional implementation manners of this embodiment, the proxy server is further configured to generate a processing result based on the WEB access request. Since the client performs WEB access via the proxy server, the proxy server may generate a processing result directly based on the WEB access request and return the processing result to the client. For example, in a scenario of performing a mock test on server data (the mock test refers to a test method in which some objects which are not easily constructed or easily obtained are created by using a virtual object for testing) during a test process, the proxy server may simulate a real server to generate a processing result and return the processing result to the client, and the real server does not need to process the WEB access request and return the processing result, so that difficulty in the mock test of the server data can be reduced, and test efficiency is improved.

With continued reference to FIG. 3, a flow 300 of one embodiment of a method for WEB access for a client in accordance with the present application is shown. The WEB access method for the client comprises the following steps:

step 301, receiving a WEB access request, where the WEB access request includes domain name information.

In this embodiment, an execution subject of the WEB access method for the client (for example, the client 101 shown in fig. 1) may receive a WEB access request input by a user, where the WEB access request includes domain name information. Here, the WEB access refers to a network service that performs data interaction by a network Protocol (for example, HTTP (Hypertext Transfer Protocol), HTTPs (Secure Hypertext Transfer Protocol), or the like). A Domain Name (Domain Name) refers to the Name of a certain computer or group of computers of the internet (e.g., "www.domain.com") that is a string of characters separated by ". times", and is used to identify the electronic location of the computer when data is exchanged. In general, a domain name represents an IP resource, such as a personal computer used to access the internet, a server computer hosting a website, or the website itself or any other service delivered over the internet. The user may input a WEB access request to the execution main body through an input device (e.g., an input device such as a touch screen, a mouse, a keyboard, etc.).

Step 302, system DNS server information of the routing end is obtained, wherein the preferred DNS server information of the routing end is configured as an IP address of the domain name resolution end.

In this embodiment, an execution subject (for example, the client 101 shown in fig. 1) of the WEB access method for the client may acquire the preferred DNS server address information of the routing end in a wired connection manner or a wireless connection manner, where the preferred DNS server information of the routing end is configured as an IP address of the domain name resolution end.

In some optional implementations of this embodiment, the routing end is a wireless router. The electronic device (e.g., a smart phone, a tablet computer, etc.) may be in communication connection with the wireless router through a wireless connection. The wireless connection means may include, but is not limited to, a 3G/4G connection, a WiFi connection, a bluetooth connection, a WiMAX connection, a Zigbee connection, a uwb (ultra wideband) connection, and other wireless connection means now known or developed in the future.

Step 303, sending the domain name information to a domain name resolution end, where the domain name resolution end is used to return the IP address of the proxy server to the client.

In this embodiment, based on the received preferred DNS server address information (i.e., the IP address of the domain name resolution end) of the router, the execution subject of the WEB access method for the client (e.g., the client 101 shown in fig. 1) may send the domain name information (e.g., "www.domain.com") in the WEB access request to the domain name resolution end for domain name resolution, and then receive the resolution result (i.e., the IP address of the proxy server) from the domain name resolution end. The domain name resolution end is used for resolving the received domain name information into the IP address of the proxy server.

Here, the domain name resolution side does not resolve the received domain name information, but directly returns the IP address of the proxy server to the execution main body. That is, the execution agent receives the IP address of the proxy server no matter what domain name information the execution agent sends to the domain name resolution peer.

And step 304, sending the WEB access request to the proxy server.

In the present embodiment, based on the received IP address of the proxy server, the execution body of the WEB access method for the client (for example, the client 101 shown in fig. 1) may transmit the WEB access request input by the user to the proxy server.

And 305, receiving a processing result of the WEB access request from the proxy server.

In the present embodiment, an execution subject of the WEB access method for the client (e.g., the client 101 shown in fig. 1) may receive a processing result from the proxy server.

Since the IP address of the proxy server is not obtained by analyzing the domain name information (that is, the proxy server is not a WEB server corresponding to the domain name information in the WEB access request), in practical applications, the processing result is usually obtained by the proxy server performing processing such as domain name analysis and request forwarding on the received WEB access request.

In some optional implementation manners of this embodiment, the processing result is obtained by the proxy server side through the following steps: determining an IP address corresponding to the domain name information in the WEB access request through a DNS (domain name server); forwarding the WEB access request to a WEB server corresponding to the determined IP address; the processing result of the WEB access request received from the WEB server is returned to the execution subject (i.e., the client).

In some optional implementations of this embodiment, the method further includes: acquiring data traffic consumed by the WEB access request and data traffic consumed by the processing result, wherein the data traffic consumed by the WEB access request and the data traffic consumed by the processing result are determined by the proxy server; and updating the data traffic information of the client based on the data traffic consumed by the WEB access request and the data traffic consumed by the processing result. In this implementation manner, the WEB access method for the client according to this embodiment can determine the data traffic consumed by the client through the proxy server, thereby improving the accuracy of the data traffic information of the client.

In some optional implementations of this embodiment, the processing result is generated by the proxy server based on the WEB access request. Since the execution agent performs WEB access via the proxy server, the proxy server may generate a processing result directly based on the WEB access request and return the processing result to the execution agent. For example, in a scenario of performing a mock test on server data (the mock test refers to a test method for testing some objects that are not easily constructed or easily obtained during the test process, a virtual object is used to create the object, so as to be tested), the proxy server may simulate a real server to generate a processing result and return the processing result to the execution main body, and the real server does not need to process the WEB access request and return the processing result, so that difficulty in the mock test of the server data can be reduced, and the test efficiency can be improved.

In some optional implementations of this embodiment, the method further includes: and recording the domain name information, the data traffic consumed by the WEB access request and the data traffic consumed by the processing result into a data traffic log. In this implementation, subsequent analysis (e.g., production data traffic reports) may be performed based on the data traffic log, facilitating reasonable use of the data traffic by the user. For example, when different applications perform WEB access to the application installed in the execution agent, the requested domain name information is usually different, and statistical analysis is performed on the data traffic log, so that data traffic information consumed by each application can be acquired, and traffic management can be performed, for example, to limit the applications with high data traffic consumption.

With continued reference to fig. 4, fig. 4 is a schematic diagram of an application scenario 400 of the WEB access method for the client according to the embodiment. In the application scenario 400 of fig. 4, first, a client 401 receives a WEB access request input by a user 406, where the WEB access request includes domain name information (e.g., "www.domain.com"); then, client 401 sends a DNS server address request to wireless router 402, and receives a preferred DNS server address of router 402, i.e., an IP address of domain name resolver 403; then, the client 401 sends the domain name information to the domain name resolver 403, and receives a resolution result of the domain name resolver 403, that is, an IP address of the proxy server 404; subsequently, the client 401 sends the WEB access request input by the user 406 to the proxy server 404, and the proxy server 404 forwards the WEB access request to the WEB server 405 corresponding to the IP address indicated by the domain name information and receives the processing result and returns the processing result to the client 401, thereby realizing that the client 401 performs WEB access via the proxy server 404.

According to the WEB access method for the client, the preferred DNS server information is configured into the routing end of the IP address of the domain name resolution end, the domain name resolution end which resolves the domain name information into the IP address of the proxy server end and the proxy server end which receives the WEB access request and returns the processing result, so that the client can perform WEB access through the proxy server end, the WEB access request of the client can be monitored and managed under the condition that the system permission of the client is not required to be acquired, and the WEB access method is not limited by the network protocol of the WEB access request. For example, WEB access requests and processing results transmitted in a custom network protocol may be monitored.

With further reference to fig. 5, as an implementation of the methods shown in the above-mentioned figures, the present application provides an embodiment of a WEB access apparatus for a client, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 3, and the apparatus may be specifically applied to the client.

As shown in fig. 5, the WEB access apparatus 500 for a client according to the present embodiment includes: a request receiving unit 501, a DNS acquisition unit 502, a domain name resolution unit 503, a request sending unit 504, and a result receiving unit 505. The request receiving unit 501 is configured to receive a WEB access request, where the WEB access request includes domain name information; the DNS obtaining unit 502 is configured to obtain preferred DNS server information of a routing end, where the preferred DNS server information of the routing end is configured as an IP address of a domain name resolution end; the domain name resolution unit 503 is configured to send domain name information to a domain name resolution end, where the domain name resolution end is configured to return an IP address of the proxy server to the client; the request sending unit 504 is configured to send a WEB access request to the proxy server; and the result receiving unit 505 is configured to receive the processing result of the WEB access request from the proxy server.

In this embodiment, the request receiving unit 501 of the WEB access apparatus 500 for a client may receive a WEB access request input by a user, where the WEB access request includes domain name information. Here, the WEB access refers to a network service that performs data interaction by a network Protocol (for example, HTTP (Hypertext Transfer Protocol), HTTPs (Secure Hypertext Transfer Protocol), or the like). A Domain Name (Domain Name) refers to the Name of a certain computer or group of computers of the internet (e.g., "www.domain.com") that is a string of characters separated by ". times", and is used to identify the electronic location of the computer when data is exchanged. In general, a domain name represents an IP resource, such as a personal computer used to access the internet, a server computer hosting a website, or the website itself or any other service delivered over the internet. A user may input a WEB access request to a client via an input device (e.g., a touch screen, mouse, keyboard, etc.).

In this embodiment, the DNS obtaining unit 502 may obtain the preferred DNS server address information of the routing end in a wired connection manner or a wireless connection manner, where the preferred DNS server information of the routing end is configured as an IP address of a domain name resolution end.

In some optional implementations of this embodiment, the routing end is a wireless router. The client (e.g., a smart phone, a tablet computer, etc.) may be in communication with the wireless router via a wireless connection. The wireless connection means may include, but is not limited to, a 3G/4G connection, a WiFi connection, a bluetooth connection, a WiMAX connection, a Zigbee connection, a uwb (ultra wideband) connection, and other wireless connection means now known or developed in the future.

In this embodiment, based on the received preferred DNS server address information (i.e., the IP address of the domain name resolution end) of the router, the domain name resolution unit 503 may send the domain name information (e.g., "www.domain.com") in the WEB access request to the domain name resolution end for domain name resolution, and then receive the resolution result (i.e., the IP address of the proxy server) from the domain name resolution end. The domain name resolution end is used for resolving the received domain name information into the IP address of the proxy server.

In this embodiment, the request sending unit 504 may send the WEB access request input by the user to the proxy server based on the received IP address of the proxy server.

In this embodiment, the result receiving unit 505 may receive a processing result from the proxy server.

In some optional implementation manners of this embodiment, the processing result is obtained by the proxy server side through the following steps: determining an IP address corresponding to the domain name information in the WEB access request through a DNS (domain name server); forwarding the WEB access request to a WEB server corresponding to the determined IP address; and returning the processing result of the WEB access request received from the WEB server to the client.

In some optional implementations of this embodiment, the apparatus further includes a flow determining unit and a flow updating unit. The flow determining unit is configured to obtain data flow consumed by the WEB access request and data flow consumed by the processing result, and the data flow consumed by the WEB access request and the data flow consumed by the processing result are determined by the proxy server; the traffic updating unit is configured to update the data traffic information of the client based on the data traffic consumed by the WEB access request and the data traffic consumed by the processing result. In this implementation manner, the WEB access apparatus for the client according to this embodiment can determine the data traffic consumed by the client through the proxy server, thereby improving the accuracy of the data traffic information of the client.

In some optional implementations of this embodiment, the processing result is generated by the proxy server based on the WEB access request. Since the client performs WEB access via the proxy server, the proxy server may generate a processing result directly based on the WEB access request and return the processing result to the client. For example, in a scenario of performing a mock test on server data (the mock test refers to a test method in which some objects which are not easily constructed or easily obtained are created by using a virtual object for testing) during a test process, the proxy server may simulate a real server to generate a processing result and return the processing result to the client, and the real server does not need to process the WEB access request and return the processing result, so that difficulty in the mock test of the server data can be reduced, and test efficiency is improved.

In some optional implementations of this embodiment, the apparatus further includes a logging unit. The log unit is configured to record domain name information, data traffic consumed by the WEB access request, and data traffic consumed by the processing result into a data traffic log. In this implementation, subsequent analysis (e.g., production data traffic reports) may be performed based on the data traffic log, facilitating reasonable use of the data traffic by the user. For example, when different applications perform WEB access to the applications installed on the client, the requested domain name information is usually different, and statistical analysis is performed on the data traffic log, so that data traffic information consumed by each application can be acquired, and traffic management can be performed, for example, an application with high data traffic consumption is restricted.

The WEB access device for the client provided in the above embodiment of the present application configures, as a routing end of an IP address of a domain name resolution end, a domain name resolution end that resolves domain name information into an IP address of a proxy server, and a proxy server that receives a WEB access request and returns a processing result through preferred DNS server information, so that the client performs WEB access through the proxy server, and can monitor and manage a WEB access request of the client without acquiring a system permission of the client, and is not limited by a network protocol of the WEB access request. For example, WEB access requests and processing results transmitted in a custom network protocol may be monitored.

Referring now to FIG. 6, shown is a block diagram of a computer system 600 suitable for use in implementing the electronic device of an embodiment of the present application. The electronic device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.

As shown in fig. 6, the computer system 600 includes a Central Processing Unit (CPU)601 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the computer system 600 are also stored. The CPU 601, ROM 602, and RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, a mouse, and the like; an output portion 607 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The driver 610 is also connected to the I/O interface 605 as needed. A removable medium 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 610 as necessary, so that a computer program read out therefrom is mounted in the storage section 608 as necessary.

In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 609, and/or installed from the removable medium 611. The computer program performs the above-described functions defined in the method of the present application when executed by a Central Processing Unit (CPU) 601.

It should be noted that the computer readable medium described herein can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor includes a request receiving unit, a DNS obtaining unit, a domain name resolution unit, a request sending unit, and a result receiving unit. Here, the names of these units do not constitute a limitation to the unit itself in some cases, and for example, the request receiving unit may also be described as a "unit that receives a WEB access request".

As another aspect, the present application also provides a computer-readable medium, which may be contained in the apparatus described in the above embodiments; or may be present separately and not assembled into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to: receiving a WEB access request, wherein the WEB access request comprises domain name information; acquiring system DNS server information of a routing end, wherein the preferred DNS server information of the routing end is configured to be an IP address of a domain name resolution end; sending the domain name information to a domain name resolution end, wherein the domain name resolution end is used for returning the IP address of the proxy server end to the client end; sending the WEB access request to an agent server; and receiving a processing result of the WEB access request from the agent server.

The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the invention. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.

Claims

1. A global wide area network (WWAN) WEB access system comprises a routing end, a domain name resolution end and an agent service end, wherein:

the routing terminal is used for responding to a request of a client terminal for acquiring a Domain Name System (DNS) server address and returning preferred DNS server information of the routing terminal to the client terminal, wherein the preferred DNS server information of the routing terminal is an Internet Protocol (IP) address of the domain name resolution terminal;

the domain name resolution end is used for responding to domain name information in a received WEB access request of the client and returning the IP address of the proxy server end to the client, wherein the IP address of the proxy server end is not obtained by resolution according to the domain name information, and the proxy server end is not a WEB server corresponding to the domain name information in the WEB access request;

the agent server is used for processing the WEB access request received from the client and returning a processing result to the client;

the proxy server is specifically configured to:

determining an IP address corresponding to domain name information in the WEB access request through a DNS (domain name server);

forwarding the WEB access request to a WEB server corresponding to the determined IP address;

and returning the processing result of the WEB access request received from the WEB server to the client.

2. The system of claim 1, wherein the broker service is further configured to determine data traffic consumed by the WEB access request and data traffic consumed by the processing result.

3. The system of claim 1, wherein the broker service is further configured to generate the processing result based on the WEB access request.

4. A global area network (ww an) WEB access method for a client, the client being communicatively connected to a router, the method comprising:

receiving a WEB access request, wherein the WEB access request comprises domain name information;

acquiring preferred Domain Name System (DNS) server information of the routing end, wherein the preferred DNS server information of the routing end is configured as an Internet Protocol (IP) address of a domain name resolution end;

sending the domain name information to the domain name resolution end, wherein the domain name resolution end is used for returning an IP address of an agent server to the client, the IP address of the agent server is not obtained by resolution according to the domain name information, and the agent server is not a WEB server corresponding to the domain name information in a WEB access request;

sending the WEB access request to the agent server;

receiving a processing result of the WEB access request from the agent server;

the processing result is obtained by the proxy server through the following steps:

determining an IP address corresponding to the domain name information through a DNS server;

and receiving a processing result of the WEB access request from the WEB server.

5. The method of claim 4, wherein the method further comprises:

acquiring data traffic consumed by the WEB access request and data traffic consumed by the processing result, which are determined by the proxy server;

and updating the data traffic information of the client based on the data traffic consumed by the WEB access request and the data traffic consumed by the processing result.

6. The method of claim 4, wherein the processing result is generated by the broker service based on the WEB access request.

7. The method of claim 5, wherein the method further comprises:

and recording the domain name information, the data traffic consumed by the WEB access request and the data traffic consumed by the processing result into a data traffic log.

8. A global area network, WEB, access apparatus for a client, the client communicatively coupled to a router, the apparatus comprising:

the system comprises a request receiving unit, a request processing unit and a processing unit, wherein the request receiving unit is configured to receive a WEB access request, and the WEB access request comprises domain name information;

a DNS acquisition unit configured to acquire preferred domain name system DNS server information of the routing end, wherein the preferred DNS server information of the routing end is configured as an internet protocol IP address of a domain name resolution end;

the domain name resolution unit is configured to send the domain name information to the domain name resolution end, the domain name resolution end is used for returning an IP address of an agent service end to the client, the IP address of the agent service end is not obtained through resolution according to the domain name information, and the agent service end is not a WEB server corresponding to the domain name information in the WEB access request;

the request sending unit is configured to send the WEB access request to the proxy server;

a result receiving unit configured to receive a processing result of the WEB access request from the proxy server;

9. An electronic device, comprising:

one or more processors;

storage means for storing one or more programs;

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 4-7.

10. A computer-readable medium, on which a computer program is stored, wherein the program, when executed by a processor, implements the method of any one of claims 4-7.