WO2018001124A1

WO2018001124A1 - Webpage file sending method, webpage rendering method and apparatus, and webpage rendering system

Info

Publication number: WO2018001124A1
Application number: PCT/CN2017/088637
Authority: WO
Inventors: 王卓
Original assignee: 阿里巴巴集团控股有限公司
Priority date: 2016-06-28
Filing date: 2017-06-16
Publication date: 2018-01-04
Also published as: TWI670611B; CN106897336A; TW201800962A

Abstract

A webpage file sending method, a webpage rendering method and apparatus, and a webpage rendering system. The webpage file sending method comprises: a server receiving a webpage request sent by a terminal and carrying user agent information corresponding to the terminal; according to the user agent information, the server determining device information, corresponding to the user agent information, about the terminal; and the server acquiring a webpage file corresponding to the device information and sending same to the terminal. Before webpage rendering, the determination of device information about a terminal and the determination of a webpage file corresponding to the device information are both executed by a server, so that the problem of excessively consuming processing resources of the terminal due to the fact that the terminal executes the above-mentioned steps is avoided, so as to improve the performance of the terminal in rendering a webpage.

Description

Web file sending method, webpage rendering method and device, webpage rendering system

The present application claims priority from the Chinese Patent Application No. 201610488238.2, entitled "Web File Sending Method, Web Page Rendering Method and Apparatus, Web Page Rendering System", which is filed on June 28, 2016, the entire contents of which are incorporated by reference. In this application.

Technical field

The present application relates to the field of Internet technologies, and in particular, to a webpage file sending method, a webpage rendering method and apparatus, and a webpage rendering system.

Background technique

Nowadays, accessing various web pages through the browser of the browser or application app has become one of the channels for people to obtain information. At present, various terminals used by people often have different device information (such as the size of the terminal screen), and different web page styles can be displayed on the terminal for different device information of the terminal. For example, Sina.com (http://www.sina.com.cn/) is displayed on mobile phones and computers in different webpage styles.

Generally, the terminal may render different webpage styles by acquiring different webpage files from the server, and the webpage files may include: CSS (Cascading Style Sheets) files, pictures, and the like. In the prior art, in the process of requesting a webpage through a browser or a client, first, the terminal sends a webpage request to the server, and then, in response to the webpage request, the server returns to the terminal, which may be used during the webpage loading process. Web page file. After receiving the webpage file returned by the server, the terminal needs to detect its own device information, and uses a media query method to determine a webpage style that is adapted to the device information and a loading required to render the webpage style. Web page file. Finally, the terminal may select a webpage file (such as a CCS file, a picture, etc.) currently loaded from the webpage file returned by the server, and use the webpage file to render the webpage.

The above prior art has at least the following problems:

Before the terminal renders the webpage, the media query method is needed to determine the webpage style that is adapted to the device information of the terminal, and the webpage file that needs to be loaded to render the webpage style, and select the currently loaded webpage from the webpage file returned by the server. Web page file. Since the above steps performed by the terminal before rendering the webpage need to consume certain processing resources of the terminal, the performance of the terminal is affected to some extent.

Summary of the invention

The purpose of the embodiment of the present application is to provide a webpage file sending method, a webpage rendering method and device, and a webpage rendering Dyeing systems to solve the above problems in the prior art.

To solve the above technical problem, the webpage file sending method, the webpage rendering method and apparatus, and the webpage rendering system provided by the embodiments of the present application are implemented as follows:

A method for sending a webpage file, comprising:

The server receives a webpage request sent by the terminal and carries user agent information corresponding to the terminal;

Determining, by the server, device information of the terminal corresponding to the user agent information according to the user agent information;

The server acquires a webpage file corresponding to the device information and sends the webpage file to the terminal.

A web page rendering method, comprising:

Sending, by the terminal, a webpage request that carries user agent information corresponding to the terminal to the server;

Receiving, by the terminal, a webpage file corresponding to the device information of the terminal returned by the server; the device information is determined by the server according to the user agent information;

The terminal performs rendering of the webpage by using a webpage file corresponding to the device information.

A webpage file transmitting apparatus, comprising: a receiving unit, a determining unit, an obtaining unit, and a sending unit; the receiving unit receiving a webpage request sent by the terminal and carrying user agent information corresponding to the terminal; the determining unit according to the The user agent information, the device information of the terminal corresponding to the user agent information is determined; the obtaining unit acquires a webpage file corresponding to the device information; and the sending unit sends a corresponding to the device information to the terminal Web page file.

A webpage rendering apparatus includes: a sending unit, a receiving unit, and a rendering unit; the sending unit sends a webpage request carrying user agent information corresponding to the terminal to the server; the receiving unit receives the terminal returned by the server and the terminal The webpage file corresponding to the device information; the device information is determined by the server according to the user agent information; and the rendering unit performs rendering of the webpage by using a webpage file corresponding to the device information.

A webpage rendering system includes a server, a first database, and a second database, wherein the first database stores a mapping relationship between user agent information and device information, and the second database stores a webpage file corresponding to device information. Receiving, by the server, a webpage request that is sent by the terminal and carrying the user agent information, and querying, from the first database, device information corresponding to the user agent information carried in the webpage request, where the server obtains from the second database And the webpage file corresponding to the device information, and sending the obtained webpage file to the terminal.

The above at least one technical solution adopted by the embodiment of the present application can achieve the following beneficial effects:

In the process of requesting the webpage by the terminal, the server determines the device information of the terminal corresponding to the user agent information according to the user agent information carried by the webpage request sent by the terminal, and determines various types corresponding to the device according to the device information. The webpage file is sent to the terminal, so that the terminal performs rendering of the webpage by using the webpage file corresponding to the device information. Compared with the prior art, before the rendering of the webpage, determining the device information of the terminal and determining that the webpage file corresponding to the device information is executed by the server, the execution of the foregoing process by the terminal is avoided, thereby avoiding that the terminal performs the above steps. Excessive consumption of processing resources of the terminal, improving the performance of the terminal.

DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings to be used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only It is a few embodiments described in the present application, and other drawings can be obtained from those skilled in the art without any inventive labor.

FIG. 1 is a flowchart of a webpage request process according to an embodiment of the present application;

Figure 2 shows an example of displaying different web page styles on different terminals;

FIG. 3 is a flowchart of a method for sending a webpage file based on a server according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a webpage rendering apparatus and a webpage file sending apparatus according to an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application are clearly and completely described in the following, in which the technical solutions in the embodiments of the present application are clearly and completely described. The embodiments are only a part of the embodiments of the present application, and not all of them. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope shall fall within the scope of the application.

Currently, a web page can be displayed in various browsers or clients of a client or application APP, and a browser or client loads various webpage files and uses the webpage file to render the webpage speed. It directly affects the user experience. The rendering process of a web page refers to the HTML (Hyper Text Mark-up Language) returned by the server (web server or application server) according to the rules defined by CSS (Cascading Style Sheets). , Hypertext Markup Language) The process of displaying code in a browser or client window.

In view of the problem that a server existing in the prior art may return a part of a webpage file that does not need to be loaded to the terminal, the following technical solution is proposed to solve at least this problem.

FIG. 1 is a process of requesting a webpage according to an embodiment of the present application, where the process is completed by a terminal and a server. The user requests access to a webpage by inputting a certain web address (domain name) in a browser or a client on the terminal, and the server is a server corresponding to the web address requested by the terminal. In this embodiment, the foregoing webpage request process includes the following steps:

Step S101: The terminal sends a webpage request carrying the user agent information corresponding to the terminal to the server.

Generally, a user can request access to a web page by entering a web address in a browser or client of the terminal. After entering the web address, the terminal needs to send a web page request (ie, an HTTP request) to the server corresponding to the web address. Before sending the above webpage request, the browser or the client first needs to establish a connection with the web server through the network, and the connection can be completed by using the TCP protocol. Once the terminal establishes a connection with the server, the browser or client can send a web page request to the server. The webpage request may include: a request method URI protocol/version, a request header (Request Header) information, and a request body. The request header information may include some information corresponding to the client environment and information corresponding to the request body. For example, the request header information can declare the language used by the browser or client, the length of the request body, and the like.

The following is an example of a web request:

GET/sample.jspHTTP/1.1

Accept:image/gif.image/jpeg,*/*

Accept-Language: zh-cn

Connection: Keep-Alive

Host:localhost

User-Agent: Mozila/4.0 (compatible; MSIE5.01; Window NT5.0)

Accept-Encoding: gzip, deflate

Username=jinqiao&password=1234

In the above example, the first line of the web page request is "method URL discussion/version": GET/sample.jsp HTTP/1.1; the request header (Request Header) information is:

Accept:image/gif.image/jpeg.*/*

Accept-Language: zh-cn

Connection: Keep-Alive

Host:localhost

User-Agent: Mozila/4.0 (compatible: MSIE5.01: Windows NT5.0)

Accept-Encoding: gzip, deflate

A line may generally be blank between the request header information and the request body, indicating that the request header information has ended, followed by the request body. In the above example, the request body can contain query string information submitted by the user: Username=jinqiao&password=1234. In the above example, the request body has only one line of content. Of course, in practical applications, the request body can contain more content.

In the embodiment of the present application, the webpage request includes user-agent (UA) information, and the user agent information refers to the identifier information unique to the browser or the client of the terminal, including: a hardware platform, system software, and application software. And personal preferences of the user. An example of user agent information for a mobile terminal is as follows:

Mozilla/5.0 (Linux; U; Android 4.1.1; zh-cn; GT-I9100Build/JRO03H; CyanogenMod-10) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0Mobile Safari/534.30

Step S102: The server determines device information corresponding to the user agent information according to the user agent information.

In the process of requesting a webpage, for a terminal having different device information, the style of the webpage to be rendered is not the same, that is, the style of the webpage finally rendered on the browser or the client of the terminal needs to be based on the terminal. Device information to determine. In the embodiment of the present application, after receiving the webpage request, the server determines the device information corresponding to the terminal that sends the webpage request. The device information includes, but is not limited to, display information of the terminal, other hardware information of the terminal, operating system information of the terminal, and the like. The display information may include resolution information of the screen, or pixel density information, or a size of the screen, and the like. In summary, according to the device information of the terminal, a webpage style adapted to the device information can be rendered.

Figure 2 shows an example of displaying different web page styles on different terminals. In this FIG. 2, the

terminals

10, 20 each have different device information, such as different resolutions of the screen. It is assumed that a certain webpage includes webpage modules A, B, and C, and the webpage module may be, for example, a picture, a text, a button, or the like. It can be seen that when the terminal 10, 20 requests the webpage, the rendered webpage styles may be different, and different webpage styles may be embodied in the size of the text, the position and layout of the webpage module, and the like.

In an embodiment of the present application, before the step S102, the method further includes the following steps:

The server pre-generates a mapping relationship between user agent information and device information, and the generated mapping relationship may be stored in a database of the web server.

For example: with user agent information: "Mozilla/5.0 (Linux; U; Android 4.1.1; zh-cn; GT-I9100Build/JRO03H; CyanogenMod-10) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0Mobile Safari/534.30" mapped device information: 480px*800px; and user agent information: "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: 0.9.4) Gecko/20011128Netscape6/6.2.1 The phase-mapped device information is: 1920px*1080px; and so on.

Correspondingly, the foregoing step S102 specifically includes:

The server searches for device information of the terminal that is mapped with the user agent information according to a mapping relationship between the user agent information and the device information that are generated in advance.

After receiving the webpage request sent by the terminal (browser or client), the server may extract the carried user agent information from the webpage request, and search the pre-formed database according to the user proxy information to find To device information mapped to the user agent information. Generally, for each user agent information in the database, there will be device information (such as display information) uniquely mapped to the user agent information. Of course, there is also the possibility that the device information mapped to the current user agent information cannot be found because there is no corresponding record in the database. For this case, the solution will be specifically described below.

It is to be noted that, in other embodiments of the present application, before the step S102, the method may further include the following steps:

The server stores the mapping relationship between the device information and the feature information; wherein the feature information is included in the user agent information. The above feature information may be any one of the following: device brand model information, operating system information of the device, and the like. For example, a user agent information is: Mozilla/5.0 (Linux; U; Android 4.1.1; zh-cn; GT-I9100Build/JRO03H; CyanogenMod-10) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0Mobile Safari/534.30, the device brand model information is: "GT-I9100", the operating system information of the device is: "Android 4.1.1". It should be noted that the mapping relationship between the device information and the feature information may be pre-generated by the server. Or, it is gradually generated by the server through a self-learning process. Or, the mapping relationship between the device information and the feature information described above is configured by the administrator (ie, not necessarily generated by the server).

Correspondingly, the above step S102 may specifically include the following steps:

The server extracts the feature information included in the user agent information; the server determines the device information of the terminal corresponding to the feature information according to the mapping relationship between the device information and the feature information generated in advance. In addition, the server can obtain device information corresponding to the user agent information by analyzing the user agent information. For example, the server can determine the device information corresponding to the “GT-I9100” by extracting the device brand model information carried in the user agent information: “GT-I9100” (eg, the pixel information of the screen is: 480px*800px, the screen) The size information is: 4.3 inches); for example, the server can determine the possible range of device information corresponding to "Android 4.1.1" by extracting the operating system information carried in the user agent information: "Android 4.1.1". Interval (eg, the size of the screen is: 3.0 to 5.3 inches, the pixel information of the screen is: (480px ~ 800px) * (800px ~ 1280px)).

Step S103: The server acquires a webpage file corresponding to the device information and sends the webpage file to the terminal.

The webpage file may include: an HTML file, a CSS file, a JS (JavaScript) file, a picture, etc. Wait. Web pages are generally rendered based on the various web page files described above. In addition, the webpage file may also be referred to as a webpage resource, and the webpage resource may include a static resource and a dynamic resource.

In the embodiment of the present application, before the step S103, the method further includes the following steps:

a) the server determines, according to the device information, a file identifier of a webpage file corresponding to the device information, where the file identifier may be, for example, a URL (Uniform Resource Locator) or a file of a webpage file. Name, the URL is for example:

*image:

"HTTP://static.ak.fbcdn.net/rsrc.php/z12E0/hash/8q2anwu7.gif"

"HTTP://static.ak.fbcdn.net/rsrc.php/zBS5C/hash/7hwy7at6.gif"

*CSS file:

"HTTP://static.ak.fbcdn.net/rsrc.php/z448Z/hash/2plh8s4n.css"

"HTTP://static.ak.fbcdn.net/rsrc.php/zANE1/hash/cvtutcee.css"

*JS file:

"HTTP://static.ak.fbcdn.net/rsrc.php/zEMOA/hash/c8yzb6ub.js"

"HTTP://static.ak.fbcdn.net/rsrc.php/z6R9L/hash/cq2lgbs8.js"

For another example, when the width of the resolution of the terminal screen (ie, the device information) is 400px, the file name (ie, the file identifier) of the CSS file (one of the webpage files) corresponding to the device information is determined as: “400.css” When the width of the resolution of the terminal screen (ie, device information) is 800px, it is determined that the file name (ie, file identifier) of the CSS file corresponding to the device information is: "800.css".

b) The server sends a file (ie, an HTML file) containing the file identifier to the terminal.

Generally, after receiving the webpage request of the terminal, the server (the server of the web server or the application APP) needs to return a corresponding HTTP response (HTTP Response) to the terminal in response to the webpage request (HTTP request) sent by the terminal. The HTTP response (ie, the above HTML file) may include: protocol status version code description information, Response Header information, and response body. The returned HTML response may include the file identifier determined above, such as the URL or file name of the CSS file of the desired application, the URL of the image of the desired application, and the like. The HTML file may only include the file identifier of the webpage file that the browser or the client needs to adopt in the subsequent webpage rendering process. According to the above example, if the screen resolution of the current terminal is 400px*800px, the CSS file to be used in the rendering process should be “400.css”, and the HTML file returned by the server should contain: <link href=“400.css”/ >This information; if the current terminal's screen resolution is 800px*1280px, the CSS file to be used in the rendering process should be "800.css", the HTML returned by the server. The file should contain: <link href=“800.css”/> this information. That is to say, the server may return an HTML file containing file identifiers of different webpage files to the terminal according to the determined device information, and the returned HTML file generally does not include the file identifiers of the remaining webpage files that need not be loaded. . According to the above example, in the prior art, whether the screen resolution of the terminal is "400px*800px" or "800px*1280px", the above CSS file needs to be returned to the terminal: "400.css" and "800.css For a terminal with a screen resolution of "400px*800px", the above CSS file: "800.css" is a webpage file that does not need to be loaded (ie, a webpage file that does not need to be used in the rendering process of the webpage). Compared with the prior art, the embodiment of the present application can specifically return a webpage file corresponding to the device information to the terminal according to different screen resolutions (device information) of the terminal.

Correspondingly, based on the above content, the foregoing step S103 specifically includes the following steps:

c) The server receives a file acquisition request sent by the terminal and carries the file identifier.

Generally, after receiving the HTML file returned by the server, the browser or the client can obtain various webpage files (such as CSS files and pictures) embedded in the current webpage style by sending a corresponding file acquisition request to the server. The file acquisition request carries the URL of the webpage file.

d) The server sends a webpage file corresponding to the file identifier to the terminal in response to the file acquisition request.

It should be noted that, in other embodiments of the present application, the server may determine the webpage style to be rendered corresponding to the current device information, and obtain various webpage files to be applied to the current webpage style, and directly The obtained webpage files are returned to the terminal for rendering of the webpage, that is, after the terminal (browser or client) sends the HTTP request to the server, it may not need to send to the server to obtain each A file acquisition request for a web page file.

Step S104: The terminal receives the webpage file corresponding to the device information, and performs rendering of the webpage by using the received webpage file to display the corresponding webpage style on the screen of the terminal. Since the web page rendering process is a technique well known in the art, it will not be described in detail herein.

FIG. 3 is a flowchart of a method for sending a webpage file based on a server according to an embodiment of the present application. Referring to the embodiment described in FIG. 1 above, in an embodiment of the present application, if the technical solution is implemented from the perspective of a server, the method for sending a webpage file includes the following steps:

S201: The server receives a webpage request sent by the terminal and carries user agent information corresponding to the terminal.

S202: The server determines device information of the terminal corresponding to the user agent information according to the user agent information.

S204: The server acquires a webpage file corresponding to the device information, and sends the webpage file to the terminal.

The above step S201 can refer to the content of the above step S101. The above step S202 can refer to the content of the above step S102. The above step S204 can refer to the content of the above step S103, and details are not described herein again.

In an optional embodiment of the present application, the foregoing method for sending a webpage file further includes:

Step S203: It is determined whether the device information corresponding to the user agent information is found. If it is found, the process proceeds to step S204; if not, the process proceeds to step S205 described below.

Step S205: The server returns a basic resource package corresponding to the webpage request to the terminal.

The basic resource package may generally include various webpage files that are required to be loaded by all possible rendered webpage styles, that is, a terminal having any device information may receive the basic resource bundle according to the basic resource bundle after receiving the basic resource bundle. Select the web page file to be loaded to the web page style that matches the device information. After receiving the basic resource package, the terminal may collect its own device information (such as display information), and then dynamically determine a webpage style suitable for its own device information, and various required loadings corresponding to the webpage style. The webpage file, and selects the webpage file to be loaded from the basic resource package, and finally uses the selected webpage file to render the webpage.

Step S206: The server receives the device information and user agent information corresponding to the terminal returned by the terminal. The device information is obtained by the terminal when the webpage is loaded by using the basic resource package.

In this embodiment, the terminal (browser or client) can dynamically collect the device information of the current terminal through a certain method (such as JavaScript) while performing webpage rendering, such as: resolution information of the screen, pixel density of the screen. Information, screen size information, operating system information used, hardware platform information, and more.

Step S207: The server generates a mapping relationship between the returned device information and the user agent information and stores it.

The terminal may send a request command for carrying the device information and the user agent information to the server, so that the server forms a certain mapping relationship between the collected device information and the user agent information, and stores the data in the database. Through the above steps S205-S207, when the device information corresponding to the user agent information is not queried, the data in the current database (the correspondence between the user agent information and the device information) may be supplemented by the manner of the terminal collection. Perfect, thus achieving the "self-learning process" of the database. Through the above-mentioned "self-learning process", in the process of the server subsequently querying the database, there is no problem that the device information corresponding to the user agent information cannot be found, that is, the matching result can always be found, thereby making the server The execution efficiency can be continuously improved.

The embodiment described in FIG. 3 above illustrates the technical solution of the present application from the perspective of a server. In fact, the present application can also be implemented from the perspective of a terminal, and the above problem can be solved as well. Referring to the embodiment introduced in FIG. 1 above, a webpage rendering method provided by an embodiment of the present application includes the following steps:

The terminal sends a webpage request carrying the user agent information corresponding to the terminal to the server.

The terminal receives a webpage file corresponding to the device information of the terminal returned by the server. The device information is determined by the server according to the user agent information.

As described above, in the webpage file sending method and the webpage rendering method provided by the foregoing embodiments, the server determines the device information of the terminal corresponding to the user agent information according to the user agent information carried by the webpage request sent by the terminal. And determining, according to the device information, various webpage files corresponding to the device and sending the webpage file to the terminal, so that the terminal performs rendering of the webpage by using the webpage file corresponding to the device information. Compared with the prior art, before the server returns the webpage file required by the webpage rendering process to the terminal, the device information of the terminal needs to be determined, and the webpage file corresponding to the device information is obtained, so that the final server returns to the terminal. The webpage file required by the webpage rendering process, and avoiding returning other webpage files that do not need to be loaded to the above terminal, can reduce the consumption of network resources to a certain extent.

On the other hand, in the prior art, since the terminal (browser or client) generally needs to collect its own device information, and uses a Media Query method to determine the webpage style corresponding to the current device information and The webpage style needs to load various webpage files, and select various webpage files to be loaded from the webpage file returned by the server. It can be seen that in addition to the problem that the additional and redundant resource downloading cost is added (that is, the network resource is additionally consumed), resulting in poor loading performance, the following problems exist in the prior art: before the terminal performs webpage rendering It is necessary to determine the device information of the device, and also need to use the media query method to determine the webpage file to be loaded, and select the webpage file to be loaded from the webpage file returned by the server. To some extent, the terminal needs to perform the above steps. Consume processing resources of its own. That is to say, in the process of rendering the webpage, the terminal also needs to consider which webpage style is to be rendered, and which webpage conditions need to be applied, which will inevitably affect the performance of the webpage rendered by the browser or the client, and reduce the response of the webpage. speed. It can be seen that, by using the foregoing method provided by the embodiment of the present application, before the webpage is rendered, determining the device information of the terminal and determining that the webpage file corresponding to the device information is performed by the server, avoiding performing the foregoing process by the terminal, thereby avoiding The terminal performs the above steps to excessively consume the processing resources of the terminal, thereby improving the performance of the terminal rendering the webpage and improving the response speed of the webpage.

It should be noted that the execution bodies of the steps of the methods provided by the foregoing embodiments may all be the same device, or the method may also be performed by different devices. For example, the execution subject of step S201 and step S202 may be device 1, and the execution subject of step S203 may be device 2; for example, the execution subject of step S201 may be device 1, and the execution subject of step S202 and step S203 may be device 2 ;and many more.

FIG. 4 is a schematic diagram of a webpage rendering apparatus and a webpage file sending apparatus according to an embodiment of the present application. Reference map As shown in FIG. 4, in an embodiment of the present application, the terminal 100 includes a browser or client 101, a webpage rendering apparatus 110, and the server 200 includes a webpage file transmitting apparatus 210, wherein the webpage rendering apparatus 110 and the webpage file transmitting apparatus 210 are The terminal 100 and the server 200 may be present in software, hardware, or a combination of hardware and software, respectively. The server 200 and the terminal 100 described above can communicate with each other through a network. The terminal 100 and the server 200 may include hardware such as a display screen, a processing unit, a memory, a nonvolatile memory, a bus, an input/output device, and the like. In addition to the above hardware, the above terminal 100 and server 200 also include corresponding software. It should be noted that the functions that can be implemented by each unit in the webpage rendering apparatus are similar to those of the steps in the webpage rendering method described above. Therefore, the specific details of the webpage rendering apparatus can be implemented by referring to the webpage rendering method. The content of the example will not be repeated here. Similarly, the specific details of the webpage file transmitting apparatus may refer to the content of the embodiment of the webpage file transmitting method.

Referring to FIG. 4, in the embodiment of the present application, the webpage file sending apparatus 210 includes: a receiving unit 211, a determining unit 213, an obtaining unit 215, and a sending unit 217. The receiving unit 211 receives a webpage request that is sent by the sending unit 111 of the terminal 100 and carries user agent information corresponding to the terminal 100. The determining unit 213 determines, according to the user agent information, that the user agent information is corresponding to the user agent information. The device information of the terminal; the obtaining unit 215 acquires a webpage file corresponding to the device information; and the sending unit 217 sends a webpage file corresponding to the device information to the terminal. The determining unit 213 may search for the device information corresponding to the user agent information by searching the first database 300. The first database 300 may pre-store the mapping relationship between the user agent information and the device information. In addition, the foregoing obtaining unit 215 may acquire various webpage files by sending a request to the second database 400, and the sent request may be HTTP header information carrying the device information. The foregoing second database 400 can be stored in various webpage files (resources), such as: HTML files, CSS files, pictures, JS files, etc., and various webpage files stored in the second database 400 are mapped with device information. In this way, the obtaining unit 215 can obtain various webpage files corresponding to the device information from the second database 400 according to the currently determined device information.

With the above webpage file sending device, the embodiment of the present application can achieve at least the following technical effects:

Compared with the prior art, before the server returns the webpage file required by the webpage rendering process to the terminal, the device information of the terminal needs to be determined, and the webpage file corresponding to the device information is obtained, so that the final server returns to the terminal. The webpage file required by the webpage rendering process, and avoiding returning other webpage files that do not need to be loaded to the above terminal, can reduce the consumption of network resources to a certain extent. In addition, the foregoing method provided by the embodiment of the present application determines the device information of the terminal and determines that the webpage file corresponding to the device information is executed by the server before the rendering of the webpage, thereby avoiding performing the foregoing process by the terminal, thereby avoiding The terminal performs the above steps However, the problem of processing resources of the terminal is excessively consumed, thereby improving the performance of the terminal rendering webpage and improving the response speed of the webpage.

In an optional embodiment of the present application, the webpage file sending apparatus 210 further includes:

Generating a unit to generate a mapping relationship between user agent information and device information in advance;

Then, the determining unit 213 searches for device information of the terminal that is mapped with the user agent information according to a mapping relationship between the user agent information and the device information that are generated in advance;

In another embodiment, the webpage file sending apparatus 210 further includes:

a generating unit, configured to generate a mapping relationship between the device information and the feature information in advance; wherein the feature information is included in the user agent information;

Then, the determining unit 213 includes: an information extracting unit and an information query unit; the information extracting unit extracts feature information included in the user agent information; and the mapping of the information query unit according to the device information and the feature information generated in advance And determining device information of the terminal corresponding to the feature information.

With reference to FIG. 4, in the embodiment of the present application, a webpage rendering apparatus 110 includes: a sending unit 111, a receiving unit 113, and a rendering unit 115. The sending unit 111 sends a carrying to the receiving unit 211 of the server 200 to carry the corresponding terminal. a webpage request of the user agent information; the receiving unit 113 receives a webpage file corresponding to the device information of the terminal 100 returned by the server; the device information is determined by the determining unit 213 of the server 200 according to the user agent The information is determined; the rendering unit 115 performs rendering of the webpage by using a webpage file corresponding to the device information.

In an optional embodiment of the present application, the webpage rendering apparatus 110 further includes:

a file receiving unit, configured to receive a file returned by the server; the file includes a file identifier of a webpage file corresponding to device information of the terminal;

Sending a request, sending an acquisition request carrying the file identifier to the server;

The receiving unit 113 receives a webpage file corresponding to the device information of the terminal returned by the server in response to the obtaining request.

With the above webpage rendering device, the embodiment of the present application can achieve at least the following technical effects:

Compared with the prior art, before the server returns the webpage file required by the webpage rendering process to the terminal, the device information of the terminal needs to be determined, and the webpage file corresponding to the device information is obtained, so that the final server returns to the terminal. The webpage file required by the webpage rendering process, and avoiding returning other webpage files that do not need to be loaded to the above terminal, can reduce the consumption of network resources to a certain extent. In addition, the foregoing method provided by the embodiment of the present application determines the device information of the terminal and determines the webpage text corresponding to the device information before the webpage is rendered. The device is executed by the server, which avoids the above-mentioned process performed by the terminal, thereby avoiding the problem of excessively consuming the processing resources of the terminal due to the terminal performing the above steps, thereby improving the performance of the terminal rendering the webpage and improving the response speed of the webpage.

With reference to FIG. 4, in the embodiment of the present application, a webpage rendering system includes: a server 200, a first database 300, and a second database 400. The first database 300 stores a mapping relationship between user agent information and device information. The second database 400 stores a webpage file corresponding to the device information, and the server 200 receives the webpage request that carries the user agent information sent by the terminal 100, and queries from the first database 300 to carry with the webpage request. The server 200 obtains the webpage file corresponding to the device information from the second database 400, and sends the obtained webpage file to the terminal 100.

In an optional embodiment of the present application, the foregoing system may further include: a Web API (Application Programming Interface) and a TFS (Team Foundation Server) interface, the Web API and the TFS interface. Both are based on the two interfaces of the server 200 and the first database 300 for providing services to the upper layer service, and the above Web API and the TFS interface may be used to return different results (such as HTML and pictures) from the second database 400. Etc.) is packaged into a corresponding API (such as Ajax), so that various upper-layer services can call the above API, thereby facilitating the implementation of the service and enhancing the user experience.

For the convenience of description, the above devices are described separately by function into various units. Of course, the functions of each unit may be implemented in the same software or software and/or hardware when implementing the present application.

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

These computer program instructions can also be stored in a particular computer capable of booting a computer or other programmable data processing device In a computer readable memory that operates in a computer readable memory, causing instructions stored in the computer readable memory to produce an article of manufacture comprising instruction means implemented in a block or in a flow or a flow diagram and/or block diagram of the flowchart The functions specified in the boxes.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

It is also to be understood that the terms "comprises" or "comprising" or "comprising" or any other variations are intended to encompass a non-exclusive inclusion, such that a process, method, article, Other elements not explicitly listed, or elements that are inherent to such a process, method, commodity, or equipment. An element defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device including the element.

Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, system, or computer program product. Thus, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment in combination of software and hardware. Moreover, the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

The application can be described in the general context of computer-executable instructions executed by a computer, such as a program module. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types. The present application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including storage devices.

The various embodiments in the specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.

The above description is only an embodiment of the present application and is not intended to limit the application. Various changes and modifications can be made to the present application by those skilled in the art. Any modifications, equivalents, improvements, etc. made within the spirit and scope of the present application are intended to be included within the scope of the appended claims.

Claims

A webpage file sending method, comprising:

The server receives a webpage request sent by the terminal and carries user agent information corresponding to the terminal;

Determining, by the server, device information of the terminal corresponding to the user agent information according to the user agent information;

The server acquires a webpage file corresponding to the device information and sends the webpage file to the terminal.
The method according to claim 1, wherein before the server obtains a webpage file corresponding to the device information and sends the webpage file to the terminal, the method further includes:

Determining, by the server, a file identifier of a webpage file corresponding to the device information according to the device information;

Sending, by the server, a file that includes the file identifier to the terminal;

The server obtains a webpage file corresponding to the device information, and sends the webpage file to the terminal, which specifically includes:

Receiving, by the server, a file obtaining request that is sent by the terminal and carrying the file identifier;

The server acquires a webpage file corresponding to the device information and sends the webpage file to the terminal in response to the file acquisition request.
The method according to claim 1, wherein the method further includes: before the determining, by the server, the device information of the terminal corresponding to the user agent information, according to the user agent information, the method further includes:

The server stores a mapping relationship between user agent information and device information;

Determining, by the server, the device information of the terminal corresponding to the user agent information according to the user agent information, specifically:

The server searches for device information of the terminal that is mapped with the user agent information according to a mapping relationship between user agent information and device information generated in advance;

or,

Before the determining, by the server, the device information of the terminal that is corresponding to the user agent information, the method further includes:

The server stores a mapping relationship between the device information and the feature information; the feature information is included in the user agent information;

Determining, by the server, the device information of the terminal corresponding to the user agent information according to the user agent information, specifically:

The server extracts feature information included in the user agent information;

The server queries the corresponding feature information according to the mapping relationship between the stored device information and the feature information. Device information of the terminal.
The method according to claim 3, wherein the server searches for device information of the terminal mapped with the user agent information according to a mapping relationship between user agent information and device information generated in advance, The method also includes:

If the device information of the terminal that is mapped with the user agent information is not found, the server returns a basic resource package corresponding to the webpage request to the terminal;

The server receives the device information and the user agent information corresponding to the terminal returned by the terminal, and generates a mapping relationship between the returned device information and the user agent information, and stores the mapping relationship.
The method according to any one of claims 1 to 4, wherein the device information comprises display information.
The method of claim 5 wherein said display information comprises resolution information or pixel density information or screen size information.
A webpage rendering method, comprising:

Sending, by the terminal, a webpage request that carries user agent information corresponding to the terminal to the server;

Receiving, by the terminal, a webpage file corresponding to the device information of the terminal returned by the server; the webpage file received by the terminal is obtained by the server according to the device information, and the device information is the server Determined according to the user agent information;

The terminal performs rendering of the webpage by using a webpage file corresponding to the device information.
The method according to claim 7, wherein the method further comprises: before the terminal receives the webpage file corresponding to the device information of the terminal that is returned by the server, the method further includes:

Receiving, by the terminal, a file returned by the server; the file includes a file identifier of a webpage file corresponding to device information of the terminal;

Sending, by the terminal, an acquisition request that carries the file identifier to the server;

Receiving, by the terminal, a webpage file that is returned by the server and corresponding to the device information of the terminal, specifically:

The terminal receives a webpage file corresponding to the device information of the terminal returned by the server in response to the obtaining request.
The method of claim 7, wherein the method further comprises:

If the server does not determine the device information of the terminal corresponding to the user agent information, the terminal receives the basic resource package corresponding to the webpage request by the server;

The terminal uses the basic resource package to perform webpage loading, and collects device information and user agent information corresponding to the terminal;

The terminal sends the device information and the user agent information corresponding to the device information to the server.
The method according to any one of claims 7 to 9, wherein the device information comprises display information.
A webpage file transmitting apparatus, comprising: a receiving unit, a determining unit, an obtaining unit, and a sending unit; the receiving unit receiving a webpage request sent by the terminal and carrying user agent information corresponding to the terminal; the determining Determining device information of the terminal corresponding to the user agent information according to the user agent information; the acquiring unit acquires a webpage file corresponding to the device information; and the sending unit sends the device to the terminal The web page file corresponding to the device information.
The device according to claim 11, wherein the device further comprises:

a storage unit that stores a mapping relationship between user agent information and device information;

And the determining unit searches for device information of the terminal that is mapped with the user agent information according to the mapping relationship between the stored user agent information and the device information;

or,

The device also includes:

a storage unit, where the mapping relationship between the device information and the feature information is stored; the feature information is included in the user agent information;

The determining unit includes: an information extracting unit and an information query unit;

The information extracting unit extracts feature information included in the user agent information;

The information querying unit queries the device information of the terminal corresponding to the feature information according to the mapping relationship between the stored device information and the feature information.
A webpage rendering apparatus, comprising: a sending unit, a receiving unit, and a rendering unit; the sending unit sends a webpage request carrying user agent information corresponding to the terminal to the server; the receiving unit receives the return of the server a webpage file corresponding to the device information of the terminal; the webpage file received by the terminal is obtained by the server according to the device information, and the device information is determined by the server according to the user agent information; The rendering unit performs rendering of the webpage by using a webpage file corresponding to the device information.
The device according to claim 13, wherein the device further comprises:

a file receiving unit, which receives a file returned by the server; the file includes a device information corresponding to the terminal File identifier of the web page file;

Sending a request, sending an acquisition request carrying the file identifier to the server;

The receiving unit receives a webpage file corresponding to the device information of the terminal returned by the server in response to the obtaining request.
A webpage rendering system, comprising: a server, a first database, and a second database, wherein the first database stores a mapping relationship between user agent information and device information, and the second database stores information corresponding to device information. a webpage file, the server receives a webpage request that is sent by the terminal and carries the user agent information, and queries, from the first database, device information corresponding to the user agent information carried in the webpage request, the server from the first The second database acquires a webpage file corresponding to the device information, and sends the obtained webpage file to the terminal.