CN113239301A

CN113239301A - Page loading request method and device and electronic equipment

Info

Publication number: CN113239301A
Application number: CN202110438157.2A
Authority: CN
Inventors: 方晓华
Original assignee: Vivo Mobile Communication Hangzhou Co Ltd
Current assignee: Vivo Mobile Communication Hangzhou Co Ltd
Priority date: 2021-04-22
Filing date: 2021-04-22
Publication date: 2021-08-10
Anticipated expiration: 2041-04-22
Also published as: CN113239301B

Abstract

The application discloses a page loading request method, a page loading request device and electronic equipment, and belongs to the technical field of communication. Specifically, the method comprises the following steps: determining N first page data requests from a page data request queue, wherein N is an integer greater than 1; according to the sequence of the N first page data requests in the page data request queue, respectively searching a target domain name corresponding to each first page data request in a domain name pool, and respectively splicing each first page data request with the corresponding target domain name and sending the spliced first page data request to a server; the domain name pool comprises M domain names, and the sum of the upper limit of the concurrency number corresponding to each domain name in the M domain names is larger than or equal to the maximum concurrency number of the preset page data request.

Description

Page loading request method and device and electronic equipment

Technical Field

The application belongs to the technical field of communication, and particularly relates to a page loading request method and device and electronic equipment.

Background

With the development of computer technology and communication technology, more and more services are implemented through web pages of electronic devices. In the related art, the presentation of the web page is usually realized by hypertext 5.0(HTML5, H5) technology. The H5 page content display needs to initiate a HTTP network request to a corresponding web server through a web client for a page data request corresponding to the page content, and then the web server receives the request and responds to the corresponding data request to the H5 page. The speed and slowness of the H5 page content loading depends largely on the speed of the page presentation content resource request and response.

However, in a high concurrency scenario, the electronic device needs to initiate tens of data requests to the server, and the web client can only send a few data requests at a time, so when loading a page, the data requests need to be sent to the server in batches, and thus the loading speed of the page is slow.

Disclosure of Invention

The embodiment of the application aims to provide a page loading request method, a page loading request device and electronic equipment, and can solve the problems that in the page loading request process of the electronic equipment, due to the limitation of concurrent requests of a web client, the page loading request speed is influenced, and the waiting time of a user is increased.

In a first aspect, an embodiment of the present application provides a page loading request method, where the method includes: determining N first page data requests from a page data request queue, wherein N is a positive integer; according to the sequence of the N first page data requests in the page data request queue, respectively searching a target domain name corresponding to each first page data request in a domain name pool, and respectively splicing each first page data request with the corresponding target domain name and sending the spliced first page data request to a server; the domain name pool comprises M domain names, and the sum of the upper limit of the concurrency number corresponding to each domain name in the M domain names is larger than or equal to the maximum concurrency number of the preset page data request.

In a second aspect, an embodiment of the present application provides a page loading request apparatus, where the apparatus includes: the determining module is used for determining N first page data requests from the page data request queue, wherein N is an integer greater than 1; the searching module is used for respectively searching a target domain name corresponding to each first page data request in the domain name pool according to the sequence of the N first page data requests in the page data request queue determined by the determining module, splicing each first page data request with the corresponding target domain name respectively and sending the spliced first page data request to the server; the domain name pool comprises M domain names, and the sum of the upper limit of the concurrency number corresponding to each domain name in the M domain names is larger than or equal to the maximum concurrency number of the preset page data request.

In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor, and when executed by the processor, the program or instructions implement the steps of the method according to the first aspect.

In a fourth aspect, embodiments of the present application provide a readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the method according to the first aspect.

In a fifth aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the method according to the first aspect.

In the embodiment of the application, in the page data request process, the electronic device determines N first page data requests from a page data request queue, wherein N is a positive integer greater than 1; according to the sequence of the N first page data requests in the page data request queue, respectively searching a target domain name corresponding to each first page data request in a domain name pool, and respectively splicing each first page data request with the corresponding target domain name and sending the spliced first page data request to a server. According to the scheme, the domain name pool comprises M domain names, and the sum of the upper limit of the concurrency quantity corresponding to each domain name in the M domain names is larger than or equal to the preset maximum concurrency quantity of the page data request, so that the web client can send the page data request to the server once in the page data request process, the waiting time of page loading can be reduced, and the page data request speed can be further improved.

Drawings

Fig. 1 is a schematic flowchart of a page loading request method according to an embodiment of the present application;

fig. 2 is a schematic diagram of a domain name pool applied to a page load request method according to an embodiment of the present application;

fig. 3 is a second schematic flowchart of a page loading request method according to an embodiment of the present application;

fig. 4 is a schematic block diagram of a page content block corresponding to a page data request applied in a page loading request method according to an embodiment of the present application;

fig. 5 is a schematic diagram of a page data request queue applied to a page loading request method according to an embodiment of the present application;

fig. 6 is one of schematic domain name queues applied to a page loading request method according to an embodiment of the present application;

fig. 7 is a second schematic diagram of a domain name queue applied to a page loading request method according to an embodiment of the present application;

fig. 8 is a third schematic diagram of a domain name queue applied to a page loading request method according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a page load request apparatus according to an embodiment of the present application;

fig. 10 is a second schematic structural diagram of a page loading request apparatus according to an embodiment of the present application;

fig. 11 is a hardware schematic diagram of an electronic device according to an embodiment of the present disclosure;

fig. 12 is a second hardware schematic diagram of an electronic device according to an embodiment of the present disclosure.

Detailed Description

The technical solutions in the embodiments of the present application will be described clearly below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of the present disclosure.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that embodiments of the application may be practiced in sequences other than those illustrated or described herein, and that the terms "first," "second," and the like are generally used herein in a generic sense and do not limit the number of terms, e.g., the first term can be one or more than one. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

Technical terms mentioned in the embodiments of the present application will be exemplified below.

The H5 page or H5 is hereinafter referred to as the H5 page, and the webpage display technology is mainly used for webpage display of the mobile terminal.

A mobile phone browser or an App is internally provided with webview: hereinafter collectively referred to as a web client, for loading a terminal displaying the h5 page.

Server or web server: hereinafter collectively referred to as web servers, where the H5 page data originates, the H5 page requests the web servers to obtain the required data via the HTTP protocol.

And page data request: in the page loading process, data to be displayed on a page comes from data inquired on a server, and the page is required to initiate an HTTP request to the server through a web client, so that the data to be displayed on the page is acquired.

Page data request queue: in the page loading process, usually, page data requests to be concurrently sent in a page need to be put into a data request queue, which is a page data request queue.

web client concurrent request restriction: the web client has a limit on the number of concurrencies of page data requests under a single domain name, the number of the concurrencies is generally 2-8 (web clients with different cores may be different), redundant requests can only be queued for waiting, and the limit is also a key reason for limiting the page loading speed.

Domain name: the system is used for positioning identification (generally pointing to server resources) of a computer during data transmission, the identification character string of a domain name plus a port number can uniquely identify the address of the server, and the same domain name is obtained only if the domain name identification character string and the port number are the same.

Domain name pool: the domain name storage device is used for storing a plurality of standby domain names and is convenient for taking out one domain name from the standby domain name for use when needed.

HTTP: the hypertext transfer protocol (HTTP) is an application-layer protocol for transferring hypermedia documents (e.g., HTML) designed for communication between Web browsers and Web servers.

DNS delay: before a client requests a server through a domain name, a DNS resolution request needs to be carried out, and the time spent by the client is the DNS delay.

The TCP setup duration is: the time spent when the client establishes the network connection with the server through the domain name is required.

Ping time delay: and the client delays the network of the Ping data packet to the server through the domain name.

Ping jitter: mean square error of Ping delay for a plurality of times.

Ping packet loss rate: packet loss rate for multiple Ping operations.

In the related art, in the H5 page loading process, under a high concurrency scenario of a web client, for example, 20 chart data need to be loaded when a user opens one H5 page, but generally, the web client can only send 2 to 8 data requests at a time, that is, the concurrent requests of the web client have data request limitation, so that the web client cannot initiate 20 page data requests at a time or initiate at least 9 page data requests at a time, and thus the web client needs to send the page data requests to a server in batches, and further the parallel request mode becomes a serial request mode. Therefore, the loading and displaying speed of the page information is greatly influenced, the waiting time of a user is prolonged, and the user experience is seriously influenced.

The page loading request method provided by the embodiment of the application can be applied to a highly-concurrent page data request scene, and in the page data request process, the electronic equipment determines N first page data requests from a page data request queue; according to the sequence of the N first page data requests in the page data request queue, respectively searching a target domain name corresponding to each first page data request in a domain name pool, and respectively splicing each first page data request with the corresponding target domain name and sending the spliced first page data request to a server. The domain name pool comprises M domain names, and the sum of the upper limit of the concurrency quantity corresponding to each domain name in the M domain names is larger than or equal to the preset maximum concurrency quantity of the page data requests, so that the upper limit of the concurrent requests of the web client is increased. Therefore, in the page loading process, the page data request speed is improved, the waiting time of a user is reduced, and the user experience is improved.

The page loading request method provided by the embodiment of the present application is described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.

It should be noted that, in the embodiment of the present application, the page loading request method provided in the embodiment of the present application is exemplarily illustrated by taking loading of an H5 page as an example. In actual implementation, the page loading request method can also be applied to other highly-concurrent page data request scenarios, and specifically can be determined according to actual use requirements, and the embodiments of the present application are not limited.

As shown in fig. 1, an embodiment of the present application provides a page loading request method, which may include steps 101 to 102 described below.

Step 101, the electronic device determines N first page data requests from a page data request queue, where N is an integer greater than 1.

In an embodiment of the present application, the N first page data requests may be highly concurrent N first page data requests.

In this embodiment of the present application, the order of the N first page data requests in the page data request queue may be arranged according to the position of the page content of the target page, or may be preset.

Illustratively, taking a target page as an H5 page as an example, when an electronic device loads an H5 page, the electronic device needs to obtain data in a corresponding data list from a server, then add the obtained data to a data queue corresponding to the H5 page, generate a corresponding node based on the data in the data queue, and then construct a node tree of the H5 page based on the obtained node. The node tree comprises at least one node, and one node corresponds to one page content block.

It should be noted that one first page data request may correspond to one page content block, or may correspond to multiple page content blocks.

It should be noted that for the H5 page scenario with multiple concurrent data requests, the page data request concurrency can be reduced by merging multiple similar page data requests (i.e. associated page data requests), so as to increase the speed of the page data requests, that is, in a high-concurrency scenario, or in a case where the page data request concurrency exceeds a preset maximum concurrency number of page data requests, the associated page data requests can be merged, so as to reduce the page data request concurrency; or, the page data requests are sorted in the page data request queue according to the priority of the page content blocks corresponding to the page data requests, and then the page data requests can be sent according to the order of the arranged page content blocks, so that the speed of the page data requests is increased.

102, the electronic device respectively searches for a target domain name corresponding to each first page data request in a domain name pool according to the sequence of the N first page data requests in a page data request queue, and respectively splices each first page data request with the corresponding target domain name and sends the spliced first page data request to a server.

In the embodiment of the application, the domain name pool comprises M domain names, and the sum of the upper limit of the concurrency number corresponding to each domain name in the M domain names is greater than or equal to the preset maximum concurrency number of the page data request.

Optionally, the maximum concurrency number of the page data requests is preset, and the page data request may be a highly concurrent page data request.

In this embodiment of the present application, the domain name pool is created in advance at a client of the electronic device.

In the embodiment of the application, each domain name can bind to the same web server ip and can also bind to different web servers ip.

It should be noted that N may be a value smaller than the preset maximum concurrency number of the page data requests, so that the electronic device may send N page data requests in the page data request queue to the web server in parallel. Then, after the web server responds, the electronic device can acquire page content block data corresponding to each page data request, so that the electronic device can respectively render and display module data in the page content block data on a page.

For example, based on the preset maximum number of concurrent page data requests, the electronic device puts M domain names into the domain name pool in advance, as shown in fig. 2, the electronic device may put the domain names in fig. 2: and api-1.vivo.com, api-2.vivo.com, api-3.vivo.com, and api-4.vivo.com are preset in the domain name pool. Wherein, the domain names can point to the web servers corresponding to the target pages.

In an example, in the process that the electronic device searches for the target domain name corresponding to each first page data request, after the electronic device finds the target domain name corresponding to each first page data request, the first page data request and the corresponding target domain name may be spliced and sent to the server. And repeating the steps until the electronic equipment finishes sending the last first page data request.

For example, the electronic device may display request-1 (i.e., the first page data request) according to the sequence of the N first page data requests in the page data request queue, then search for a target domain name corresponding to the request-1 in the cyclic domain name pool, and concatenate the target domain name with the corresponding first page data request and send the result to the server.

In an example, in the process that the electronic device respectively searches for a target domain name corresponding to each first page data request, after the electronic device finds a target domain name corresponding to one first page data request, the electronic device may splice the first page data request with the corresponding target domain name, and so on until the electronic device completes the splicing of all first page data requests in the N first page requests with the corresponding target domain names, and then sends the N first page data requests including the target domain names to the server.

The page loading request method provided by the embodiment of the application can be used in a high concurrency scene, and the domain name pool comprises M domain names, and the sum of the upper limit of the concurrency quantity corresponding to each domain name in the M domain names is larger than or equal to the maximum concurrency quantity of the preset page data request, so that the web client can send the page data request to the server once in the page data request process, the speed of acquiring the web server data by the page content block is improved, the page loading waiting time can be reduced, and the page data request speed can be improved.

Optionally, in this embodiment of the present application, the target domain name corresponding to one first page data request may be an optimal domain name corresponding to the one page data request.

In an embodiment of the present application, in order to enable the electronic device to quickly determine the domain name of the first page data request in the domain name pool, the domain name in the domain name pool may include an identifier.

Optionally, the domain name pool includes M domain names, and each domain name includes at least one of the following: a first identifier and a second identifier.

The first identifier corresponding to any domain name may be used to characterize: the number of page data requests being sent by any of the domain names; the second identifier corresponding to any domain name can be used for characterizing: and the first response parameter and the second response parameter are used when a page data request is sent to the server through any domain name.

The first response parameter may include at least one of: the average value of DNS time delay, the average value of TCP built-up time length and the average value of Ping time delay; the second response parameter may include at least one of: ping jitter value, Ping packet loss rate.

Alternatively, the initial value of the parameter corresponding to the first identifier and the initial value of the parameter corresponding to the second identifier may be 0.

It should be noted that the first identifier (i.e., flag) corresponding to any domain name may be used to identify: the number of page data requests being sent by any of the above domain names.

Illustratively, the average value of the DNS delay in the first response parameter of the second identifier of any domain name may be marked with flag1, the average value of the TCP setup time may be marked with flag2, and the average value of the Ping delay may be marked with flag 3.

Wherein, flag1 may be: when a request is sent to the web server by using any domain name, the DNS time delay generated by the historical request is added and divided by the number of the request times, and the shorter the value is, the faster the DNS resolution of any domain name is.

flag2 may be that when a request is made to a web server using any of the domain names, the historical TCP connection setup time of the request is added to the request times, and a shorter value indicates a faster connection setup.

flag3 may be that when a request is made to a web server using any domain name, the sum of the Ping delays of historical requests is divided by the number of requests, and a smaller value of this number indicates a smaller delay and a better network status.

The Ping jitter value in the second response parameter of the second identifier of any domain name can be marked by flag4, and the packet loss rate of Ping packets can be marked by flag 5.

Wherein, flag4 may be: when any domain name is used for initiating a request to a web server, the Ping jitter value of any domain name is smaller, and the smaller the value is, the more stable the domain name is

The flag5 may be that when the any domain name is used to initiate a request to the web server, the smaller the packet loss rate of the ping packet of the any domain name, the better this value is, the more the domain name is connected.

Optionally, in this embodiment of the application, in order to quickly send the first page data request, the electronic device may determine an idle domain name in the domain name pool as a target domain name corresponding to the first page data request.

Based on this, in the embodiment of the present application, the step 102 may include the following steps 102a and 102 b:

step 102a, the electronic device traverses the N first page data requests according to the sorting of the N first page data requests in the page data request queue.

And 102b, the electronic equipment searches a target domain name corresponding to the currently traversed first page data request in the first domain name in the domain name pool.

The first domain name may be: domain names with the number of page data requests corresponding to the first identifier smaller than a preset threshold value

It should be noted that the domain name with the number of the page data requests corresponding to the first identifier smaller than the preset threshold may be an idle domain name.

Illustratively, the preset threshold may be a positive integer set according to the characteristics of the web client, for example, the preset threshold may be set to 4.

Example 1, as illustrated by setting the preset threshold value to 4, if the first flag (i.e., flag) of any domain name is less than 4, it indicates that the any domain name is an idle domain name, and if the flag of the any domain name is greater than or equal to 4, it indicates that the any domain name is busy (i.e., is a non-idle domain name).

Optionally, in this embodiment of the application, the electronic device may determine, according to the number of the first domain names, a target domain name corresponding to the first page data request.

Based on this, as shown in fig. 3, the step 102b may include the following step a1 or step a 2.

Step a1, if the number of the first domain names is 1, the electronic device uses the first domain names as target domain names of the currently traversed first page data request.

Step a2, if the number of the first domain names is greater than 1, the electronic device uses the first domain name meeting the predetermined condition as a target domain name of the currently traversed first page data request based on the sum of the average values in the first response parameters corresponding to the first domain names.

The first domain name satisfying the predetermined condition may include any one of:

a first domain name with a minimum sum of the average values in the first response parameter;

and the first domain name has the smallest sum of the average values in the first response parameters and the smallest sum of the Ping jitter value average value and the packet loss rate in the second response parameters.

Example 2, taking loading an H5 page as an example, assuming that a user opens an H5 page and needs to load 20 chart data at the same time, the electronic device needs to initiate 20 page data requests to the server (i.e., the above-mentioned N first page data requests are 20 first page data requests). As shown in fig. 4, fig. 4 includes 8 modules, each module may correspond to one H5 page content block, each H5 page content block corresponds to one page data request of an H5 page, the 8 modules in the figure are the first 8 page data requests in the above 20 page data requests, and each module needs to separately request a web server to obtain the display data of the corresponding H5 page content block in the page loading process.

Example 3, in combination with the above example 2, the electronic device puts the above 20 page data requests into a queue to be requested, so as to obtain a request queue as shown in fig. 5. Then, the electronic device may sequentially display the request information in the request queue according to the sequence of the 20 page data requests, circulate the domain names in the domain name pool, obtain an optimal domain name (i.e., a target domain name) corresponding to each page data request according to a specific algorithm, and splice the target domain name with the corresponding page data request to initiate a request to the web server. And the like until all the 20 page data requests in the request queue are spliced with the corresponding target domain name and sent to the web server.

Example 4, with reference to the above example 3, the method for obtaining the optimal domain name (i.e. the target domain name) of the page data request includes: traversing 20 page data requests according to the sequence of the 20 page data requests in the page data request queue; and searching a target domain name corresponding to the currently traversed first page data request in the first domain name in the domain name pool. And if the electronic equipment requests to find at least two first domain names in the domain name pool for the currently traversed page data, performing priority sequencing according to the indexes of flag1, flag2, flag3, flag4 and flag5 on each first domain name. For example, the sequence from good to bad may be: first, sum (flag1+ flag2+ flag3) is calculated, and then, according to the sorting from small to large of the sum value, the first domain name ranked first (i.e. the smallest sum value) is the optimal domain name, and thus, the first domain name ranked first is the target domain name of the currently traversed first page data request. If the sum values of the first domain names of the first and second bits are the same (i.e. there are two first domain names with the smallest sum values), the electronic device may compare the flag4 and flag5 indexes on the first domain names of the first and second bits, respectively, and select the first domain name with the smallest sum value of the flag4 and flag5 as the target domain name of the currently traversed first page data request. According to the method, the electronic equipment can select the high-quality domain name to request according to the parameters corresponding to the first identification and the second identification of the domain name, so that the speed of acquiring the web server data by each page content block of the H5 page is increased, the waiting time of a user is reduced, and the user experience is improved.

Optionally, as shown in fig. 6, in this embodiment of the application, the domain name pool may include a domain name queue, where the domain name queue includes the M domain names.

Wherein, the target domain name may be: a domain name of at least one second domain name of the M domain names; the second domain name may be: in the M domain names, the number of the page data requests corresponding to the first identifier is smaller than the domain name with a preset threshold value.

The at least one second domain name is ordered in the domain name queue according to a predetermined rule, and the predetermined rule may include any one of:

sorting according to the sum of the average values in the first response parameters corresponding to the second identifier of each second domain name;

and sorting according to the sum of the average values of the first response parameters corresponding to the second identifier of each second domain name and the sum of the second response parameters corresponding to the second identifier of each second domain name. Wherein the sum of the second response parameters may be: and the sum of the Ping jitter value average value in the second response parameter corresponding to the second identifier of each second domain name and the packet loss rate of Ping data packets. The at least one second domain name may be at least two second domain names.

Illustratively, the ordering in the above predetermined rule is generally ordered from small to large according to the sum of the corresponding parameters. Specifically, a number indicating the ordering may be added to each domain name, for example, in the order of arabic numbers: 0. 1, 2, 3, etc., and may be numbered in other orders as indicated, for example: a. b, c, d, etc.

Illustratively, referring to the domain name in FIG. 6: api-1.vivo.com, api-2.vivo.com, api-3.vivo.com, api-4.vivo.com, which are in the domain name pool queue, these domain names have a sequential identifier, 0, 1, 2, 3 respectively, to indicate their sorting position in the domain name pool.

Optionally, in this embodiment of the application, in order to quickly select a good domain name in the domain name pool for each first page data request, the electronic device may select a good domain name for each first page data request according to the domain name queue.

Based on this, in this embodiment of the present application, "in the domain name pool, respectively searching for the target domain name corresponding to each first page data request" in step 102 may be implemented by the following step 102 c.

And 102c, the electronic equipment allocates a corresponding target domain name for each first page data request in sequence according to the sequence of the domain names in the domain name queue.

And one domain name in the domain name queue corresponds to a first page data request.

Illustratively, how the electronic device allocates the corresponding target domain name to each first page data request is described by taking the sorting in the predetermined rule as an example, in which the sorting is from small to large according to the sum of the corresponding parameters: in the process of page loading request, a piece of request information is popped (i.e. displayed) in a page data request queue in the electronic device, referring to fig. 4, for example, a request-1 is popped first, then a first domain name in a domain name queue is directly taken, and the first domain name and a first piece of first page data request are spliced and sent to the server. And similarly, gradually popping up the request information in the page data request queue, and repeatedly executing the steps until the request information in the page data request queue is emptied. Because the first domain name in the domain name queue is usually an idle and best quality domain name, the electronic device does not need to go to the domain name pool to calculate and search the idle and good quality domain name when sending the request, thereby reducing the overhead of searching the idle domain name when sending the request.

Optionally, in this embodiment of the application, in order to quickly and accurately select a corresponding target domain name in the domain name pool for each first page data request, the electronic device may further update the identifier of the domain name.

Based on this, after the electronic device splices the target page data request and the target domain name corresponding to the target page data request and sends the spliced target domain name to the server, the page loading request method provided in the embodiment of the present application may further include the following step 103.

Step 103, the electronic device adds 1 to the number of page data requests corresponding to the first identifier of the target domain name corresponding to the target page data request.

The target page data request may be any one of the N first page data requests.

It should be noted that the number of page data requests corresponding to the first identifier of any target domain name may be: the number of page data requests being sent by any of the target domain names.

Example 5, if the preset threshold of the page data request corresponding to the first identifier of any target domain name is 4, if the number of the page data requests corresponding to the first identifier of any target domain name is 3 before any target domain name is spliced with the corresponding target page data request, after any target domain name is spliced with the corresponding target page data request and sent to the server, the number of the page data requests corresponding to the first identifier of any target domain name may be added by 1 (that is, 3 plus 1), and then the number of the page data requests corresponding to the first identifier of any target domain name is 4 at this time. Or after the arbitrary target domain name is spliced with the corresponding target page data request, the number of page data requests corresponding to the first identifier of the arbitrary target domain name may be increased by 1.

Exemplarily, if any one of the target domain names is a domain name in the domain name queue, after the number of the page data requests corresponding to the first identifier of any one of the target domain names is added by 1, if the number of the page data requests corresponding to the first identifier of any one of the target domain names is equal to a preset threshold, the any one of the target domain names is moved to a last position in the domain name queue. As shown in fig. 7, when the number of page data requests corresponding to the first identifier of the first domain name api-1.vivo.com in the domain name queue is equal to the preset threshold, the domain name is moved to the last position of the domain name queue, and other domain names are moved up in a forward direction. Therefore, the electronic equipment can select the high-quality domain name for each first page data request conveniently according to the domain name queue.

Example 6, in combination with example 5, if the number of page data requests corresponding to the first identifier of any target domain name is 4 (i.e., equal to the preset threshold), the any target domain name may be moved to the last position in the domain name queue.

Optionally, in this embodiment of the present application, after the target page data request and the target domain name corresponding to the target page data request are spliced and sent to the server, the page loading request method provided in this embodiment of the present application may further include the following steps 104 and 105.

And step 104, the electronic equipment acquires a target page data response corresponding to the target page data request from the server.

And 105, the electronic device updates the number of the page data requests corresponding to the first identifier of the target domain name corresponding to the target page data request according to the target page data response, and updates the first response parameter and the second response parameter corresponding to the second identifier of the target domain name corresponding to the target page data request.

For example, the electronic device may subtract 1 from the number of page data requests corresponding to the first identifier of the target domain name corresponding to the target page data request according to the target page data response.

For example, if the target domain name is a domain name in the domain name queue, the electronic device may further update the ordering of the target domain name in the domain name queue according to the updated first identifier and the updated second identifier of the target domain name. That is, according to the quality degree of each domain name, it is reinserted into the corresponding sorting position in the domain name queue, which can be referred to fig. 8.

Example 7, with reference to example 6, in a case that the number of page data requests corresponding to the first identifier of any target domain name is 4 (that is, equal to a preset threshold), if the electronic device obtains a target page data response corresponding to a target page data request corresponding to any target domain name, the electronic device decreases the number of page data requests corresponding to the first identifier of any target domain name from 4 to 1 (that is, to 3), and updates, according to the obtained target page data response, one of the first response parameters: the average value of DNS delay, the average value of TCP setup duration, the average value of Ping delay, and, in updating the second response parameter: ping jitter value, Ping packet loss rate. Therefore, the electronic device can quickly and accurately select the corresponding target domain name in the domain name pool for each first page data request according to the updated identification of the domain name.

It should be noted that, in the page loading request method provided in the embodiment of the present application, the execution main body may be a page loading request device, or a control module of the page loading request device, which is used for executing the page loading request method. In the embodiment of the present application, a method for a page load request device to execute a page load request is taken as an example, and a device for a page load request provided in the embodiment of the present application is described.

As shown in fig. 9, an embodiment of the present application provides a page loading request apparatus, including: a determination module 401 and a lookup module 402, wherein:

a determining module 401, configured to determine N first page data requests from the page data request queue, where N is an integer greater than 1.

A searching module 402, configured to search, in the domain name pool, target domain names corresponding to each first page data request according to the ordering of the N first page data requests in the page data request queue determined by the determining module 401, and splice and send each first page data request with the corresponding target domain name to the server;

optionally, the domain name pool includes M domain names, and a sum of upper limits of concurrency numbers corresponding to the respective domain names in the M domain names is greater than or equal to a preset maximum concurrency number of the page data request.

Optionally, each domain name of the M domain names included in the domain name pool includes at least one of: a first identifier and a second identifier.

The first identifier corresponding to any domain name is used for representing: the number of page data requests being sent by any of the domain names.

The second identifier corresponding to any domain name is used for characterizing: and the first response parameter and the second response parameter are used when a page data request is sent to the server through any domain name.

Wherein the first response parameter comprises at least one of: the average value of DNS time delay, the average value of TCP built-up time length and the average value of Ping time delay;

the second response parameter includes at least one of: ping jitter value, Ping packet loss rate.

Optionally, the searching module is further configured to traverse the N first page data requests according to the ordering of the N first page data requests in the page data request queue determined by the determining module; and searching a target domain name corresponding to the currently traversed first page data request in the first domain name in the domain name pool.

Wherein the first domain name is: and the number of the page data requests corresponding to the first identifier is less than the domain name with a preset threshold value.

Optionally, the search module is further configured to: if the number of the first domain names is 1, taking the first domain names as target domain names of the currently traversed first page data requests; or if the number of the first domain names is greater than 1, based on the sum of the average values in the first response parameters corresponding to the first domain names, taking the first domain name meeting the predetermined condition as the target domain name of the currently traversed first page data request.

Wherein the first domain name satisfying the predetermined condition includes any one of: a first domain name having a minimum sum of the average values in the first response parameter; and the first domain name has the smallest sum of the average values in the first response parameters and the smallest sum of the Ping jitter value average value and the packet loss rate in the second response parameters.

Optionally, the domain name pool includes a domain name queue, and the domain name queue includes the M domain names.

Wherein, the target domain name is: at least one of the M domain names is a second domain name.

The second domain name is: and in the M domain names, the number of the page data requests corresponding to the first identifier is less than the domain name with a preset threshold value.

Optionally, the at least one second domain name is sorted in the domain name queue according to a predetermined rule.

Optionally, the predetermined rule includes any one of: sorting according to the sum of the average values in the first response parameters corresponding to the second identifier of each second domain name; and sequencing according to the sum of the average values in the first response parameters corresponding to the second identifier of each second domain name, and the sum of the Ping jitter value average value and the packet loss rate in the second response parameters corresponding to the second identifier of each second domain name.

Optionally, the searching module is further configured to sequentially allocate a corresponding target domain name to each first page data request according to the sequence of the domain names in the domain name queue determined by the determining module; and one domain name in the domain name queue corresponds to a first page data request.

Optionally, with reference to fig. 9, as shown in fig. 10, the apparatus may further include: a calculation module 403.

The calculating module 403 is configured to add 1 to the number of page data requests corresponding to the first identifier of the target domain name corresponding to the target page data request after the searching module 402 splices the target page data request and the target domain name corresponding to the target page data request and sends the spliced target domain name to the server.

The target page data request is any one of the N first page data requests.

Optionally, with reference to fig. 10, the apparatus may further include: and an acquisition module.

An obtaining module, configured to, after the searching module 402 splices the target page data request and the target domain name corresponding to the target page data request and sends the spliced target domain name to the server, obtain, from the server, a target page data response corresponding to the target page data request.

The calculation module is further configured to, according to the target page data response obtained by the obtaining module, subtract 1 from the number of page data requests corresponding to the first identifier of the target domain name corresponding to the target page data request, and update the first response parameter and the second response parameter corresponding to the second identifier of the target domain name corresponding to the target page data request.

In the page loading request device provided by the embodiment of the application, in the page data request process, the electronic equipment determines N first page data requests from a page data request queue, wherein N is a positive integer greater than 1; according to the sequence of the N first page data requests, respectively searching a target domain name corresponding to each first page data request in a domain name pool, and respectively splicing each first page data request with the corresponding target domain name and sending the spliced first page data request to a server. According to the device, the domain name pool comprises M domain names, and the sum of the upper limits of the concurrency quantity corresponding to the M domain names is larger than or equal to the preset maximum concurrency quantity of the page data request, so that the web client can send the page data request to the server once in the page data request process, the waiting time for page loading can be reduced, and the page data request speed can be increased.

The page loading request device in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The device can be mobile electronic equipment or non-mobile electronic equipment. Illustratively, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palm top computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or a Personal Digital Assistant (PDA), and the like, and the non-mobile electronic device may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine, a self-service machine, and the like, and the embodiments of the present application are not particularly limited.

The page load request device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.

The page loading request device provided in the embodiment of the present application can implement each process implemented by the above method embodiment, and is not described here again to avoid repetition.

Optionally, as shown in fig. 11, an electronic device 500 is further provided in this embodiment of the present application, and includes a processor 501, a memory 502, and a program or an instruction stored in the memory 502 and capable of being executed on the processor 501, where the program or the instruction is executed by the processor 501 to implement each process of the above-mentioned page loading request method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

It should be noted that the electronic device in the embodiment of the present application includes the mobile electronic device and the non-mobile electronic device described above.

Fig. 12 is a schematic hardware structure diagram of an electronic device implementing an embodiment of the present application.

The electronic device 1000 includes, but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, and a processor 1010.

Those skilled in the art will appreciate that the electronic device 1000 may further comprise a power source (e.g., a battery) for supplying power to various components, and the power source may be logically connected to the processor 1010 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system. The electronic device structure shown in fig. 12 does not constitute a limitation of the electronic device, and the electronic device may include more or less components than those shown, or combine some components, or arrange different components, and thus, the description is not repeated here.

The processor 110 is configured to determine N first page data requests from a page data request queue, where N is an integer greater than 1; according to the sequence of the N first page data requests in the page data request queue, respectively searching a target domain name corresponding to each first page data request in a domain name pool, and respectively splicing each first page data request with the corresponding target domain name and sending the spliced first page data request to a server; the domain name pool comprises M domain names, and the sum of the upper limit of the concurrency number corresponding to each domain name in the M domain names is larger than or equal to the preset maximum concurrency number of the page data request.

According to the page loading request method provided by the embodiment of the application, the domain name pool comprises M domain names, and the sum of the upper limit of the concurrency quantity corresponding to each domain name in the M domain names is larger than or equal to the preset maximum concurrency quantity of the page data request, so that the web client can send the page data request to the server once in the page data request process, the speed of acquiring the web server data by the page content block is improved, the waiting time of page loading can be reduced, and the page data request speed can be improved.

It should be understood that, in the embodiment of the present application, the radio frequency unit 1001 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. The electronic device provides wireless broadband internet access to the user through the network module 1002, such as assisting the user in sending and receiving e-mails, browsing web pages, and accessing streaming media. The audio output unit 1003 may include, but is not limited to, a speaker, a buzzer, a receiver, and the like.

The input Unit 1004 may include a Graphics Processing Unit (GPU) 10041 and a microphone 10042, the Graphics processor 10041 Processing image data of still pictures or video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and other input devices 10072. The touch panel 10071 is also referred to as a touch screen. The touch panel 10071 may include two parts, a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein. The memory 1009 may be used to store software programs as well as various data, including but not limited to application programs and operating systems. Processor 1010 may integrate an application processor that handles primarily operating systems, user interfaces, applications, etc. and a modem processor that handles primarily wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 1010.

The embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the above-mentioned page loading request method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement each process of the above-mentioned page loading request method embodiment, and can achieve the same technical effect, and in order to avoid repetition, the description is omitted here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-on-chip, system-on-chip or system-on-chip, etc.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A page loading request method is characterized by comprising the following steps:

determining N first page data requests from a page data request queue, wherein N is an integer greater than 1;

according to the sequence of the N first page data requests in the page data request queue, respectively searching a target domain name corresponding to each first page data request in a domain name pool, and respectively splicing each first page data request with the corresponding target domain name and sending the spliced first page data request to a server;

the domain name pool comprises M domain names, and the sum of the upper limit of the concurrency number corresponding to each domain name in the M domain names is larger than or equal to the preset maximum concurrency number of the page data request.

2. The method according to claim 1, wherein the respectively searching for the target domain name corresponding to each first page data request in the domain name pool according to the sorting of the N first page data requests in the page data request queue comprises:

traversing the N first page data requests according to the sequence of the N first page data requests in the page data request queue;

searching a target domain name corresponding to the currently traversed first page data request in a first domain name in the domain name pool;

wherein the first domain name is: the method comprises the following steps that domain names with the number of page data requests corresponding to a first identifier smaller than a preset threshold value are used for representing: the number of page data requests being sent by any of the domain names.

3. The method of claim 2,

the searching for the target domain name corresponding to the currently traversed first page data request in the first domain name in the domain name pool includes:

if the number of the first domain names is 1, taking the first domain names as target domain names of the currently traversed first page data requests; alternatively, the first and second electrodes may be,

if the number of the first domain names is larger than 1, based on the sum of average values in the first response parameters corresponding to the first domain names, taking the first domain names meeting the preset conditions as target domain names of the currently traversed first page data request;

wherein the first domain name satisfying the predetermined condition includes any one of:

and the first domain name has the smallest sum of the average values in the first response parameter and the smallest sum of the Ping jitter value average value and the packet loss rate in the second response parameter.

4. The method of claim 3, wherein a domain name queue is included in the domain name pool, the domain name queue including the M domain names;

wherein the target domain name is: a domain name of at least one second domain name of the M domain names;

the second domain name is: in the M domain names, the number of the page data requests corresponding to the first identifier is smaller than a preset threshold;

the at least one second domain name is sorted in the domain name queue according to a preset rule;

the predetermined rule includes any one of:

sorting according to the sum of the average values in the first response parameters corresponding to the second identifier of each second domain name and the sum of the second response parameters corresponding to the second identifier of each second domain name;

the second identifier is used for characterizing: a first response parameter and a second response parameter when a page data request is sent to the server through any domain name;

the first response parameter includes at least one of: the average value of DNS time delay, the average value of TCP built-up time length and the average value of Ping time delay;

5. The method according to claim 4, wherein the separately searching for the target domain name corresponding to each first page data request in the domain name pool comprises:

according to the sequence of the domain names in the domain name queue, sequentially distributing corresponding target domain names for each first page data request;

6. The method according to claim 4 or 5, wherein after the target page data request and the target domain name corresponding to the target page data request are spliced and sent to a server, the method further comprises:

adding 1 to the number of page data requests corresponding to the first identifier of the target domain name corresponding to the target page data request;

acquiring a target page data response corresponding to the target page data request from the server;

according to the target page data response, updating the number of page data requests corresponding to the first identifier of the target domain name corresponding to the target page data request, and updating a first response parameter and a second response parameter corresponding to the second identifier of the target domain name corresponding to the target page data request;

wherein the target page data request is any one of the N first page data requests.

7. A page load request apparatus, the apparatus comprising:

the determining module is used for determining N first page data requests from the page data request queue, wherein N is an integer greater than 1;

the searching module is used for respectively searching a target domain name corresponding to each first page data request in the domain name pool according to the sequence of the N first page data requests in the page data request queue determined by the determining module, splicing each first page data request with the corresponding target domain name respectively and sending the spliced first page data request to the server;

8. The apparatus of claim 7,

the searching module is further configured to traverse the N first page data requests according to the ordering of the N first page data requests in the page data request queue determined by the determining module; searching a target domain name corresponding to the currently traversed first page data request in a first domain name in the domain name pool;

9. The apparatus of claim 8,

the search module is further configured to:

10. The apparatus of claim 9, wherein a domain name queue is included in the domain name pool, and wherein the domain name queue includes the M domain names;

the predetermined rule includes any one of:

sorting according to the sum of the average values in the first response parameters corresponding to the second identifier of each second domain name, and the sum of the Ping jitter value average value and the packet loss rate in the second response parameters corresponding to the second identifier of each second domain name;

11. The apparatus of claim 10,

the searching module is further configured to sequentially allocate a corresponding target domain name to each first page data request according to the sequence of the domain names in the domain name queue determined by the determining module;

12. The apparatus of claim 10 or 11, further comprising: a calculation module and an acquisition module, wherein,

the calculation module is used for adding 1 to the number of page data requests corresponding to the first identifier of the target domain name corresponding to the target page data request after the search module splices the target page data request with the target domain name corresponding to the target page data request and sends the spliced target domain name to the server;

the acquisition module is used for acquiring a target page data response corresponding to the target page data request from the server after the search module splices the target page data request and a target domain name corresponding to the target page data request and sends the spliced target page data request and the target domain name to the server;

the calculation module is further configured to update, according to the target page data response obtained by the obtaining module, the number of page data requests corresponding to the first identifier of the target domain name corresponding to the target page data request, and update the first response parameter and the second response parameter corresponding to the second identifier of the target domain name corresponding to the target page data request;

13. An electronic device comprising a processor, a memory and a program stored on the memory and executable on the processor, the program, when executed by the processor, implementing the steps of the page load request method according to any one of claims 1 to 6.

14. A readable storage medium, on which a program is stored, which program, when executed by a processor, carries out the steps of the page load request according to any one of claims 1 to 6.