WO2013091346A1

WO2013091346A1 - Webpage content preloading method, device and system

Info

Publication number: WO2013091346A1
Application number: PCT/CN2012/075779
Authority: WO
Inventors: 林文旭
Original assignee: 华为技术有限公司
Priority date: 2011-12-22
Filing date: 2012-05-19
Publication date: 2013-06-27
Also published as: CN102446222A; CN102446222B

Abstract

Disclosed in an embodiment of the present invention is a webpage content preloading method, comprising: acquiring the characteristic metadata of a webpage according to the webpage information a user is currently accessing; searching a preloading policy table according to the acquired characteristic metadata and obtaining the preloaded data; and loading the obtained preloaded data to a cache. Also disclosed in the embodiment of the present invention are a webpage content preloading device, preloading policy table establishment method and communication system. In the above technical solution, a cache module stores in advance the data of the next webpage a user may access, without interrupting the current webpage browsing of the user, enabling the user to directly read data from the cache when requesting the next webpage, solving the problem in a network management system that a user has to wait a long time after performing a foreground operation because a browser needs to read a large amount of data from a server, thus improving user experience.

Description

Webpage content preloading method, device and system

Technical field

The present invention relates to the field of the Internet, and in particular, to a webpage content preloading method, apparatus, and system.

Background technique

Most of the key applications, such as telecom management systems, IT management systems, and enterprise network applications, use B/S architecture, namely browser and server architecture, to provide availability and save deployment costs. In this structure, the user interface (UI, User Interface) is presented by the WWW browser, and the main transaction logic is implemented on the server side, which greatly simplifies the client load and reduces system maintenance and upgrade. The cost and workload reduce the overall cost of the user. The user interface is also called the front end, and the server side is also called the background. However, in current network management systems and enterprise management applications, due to certain links, such as: alarm data, collection task network metadata, and collection task logs, a large amount of data update is often required, and the amount of updated data is required. The larger the response time of the front end for getting and loading data from the background, the longer the user waits and the poor user experience when operating on the front end.

In an existing B/S-based application system, a large amount of webpage data is preloaded by deploying an Edge Fragment (ESI) in a Web server or deploying a front-end page cache on a client. In the cache, the browser does not have to read data from the web server frequently, thereby reducing the time for the browser to load data from the web server.

The prior art solution cannot determine the data that the user is most likely to access, so a large amount of cache space needs to be deployed, so that the complexity and cost of the system are greatly increased, and it is difficult to be commercially large-scale in practice, and the B/S-based architecture cannot be effectively solved. Part of the application system takes too long to operate. Summary of the invention

The embodiment of the invention provides a webpage content preloading method, which implements preloading of webpage content based on user behavior analysis, reduces waiting time of the user in front end operation in the application system based on the B/S architecture, and improves user experience.

An embodiment of the present invention provides a webpage content preloading method, including: Responding to the webpage access request of the user, loading the webpage requested by the user from the server; analyzing the webpage, and collecting feature metadata of the webpage;

Querying a preloading policy table, and acquiring a preloaded webpage corresponding to the feature metadata of the webpage; the preloading webpage is a webpage with the highest probability of subsequent request access based on the webpage requested by the user; The preloading policy table includes a correspondence relationship between the feature metadata of the webpage and the preloaded webpage;

Cache the preloaded web page in a cache;

Receiving a subsequent webpage access request of the user, and querying, in the cache, whether the webpage accessed by the subsequent webpage access request request is cached; the subsequent access request is sent by the user on the basis of the webpage requested by the user;

If so, the webpage accessed by the subsequent webpage access request request is loaded from the cache. An embodiment of the present invention provides a webpage content preloading apparatus, including:

a first response unit, configured to load a webpage accessed by the user request from a server in response to a webpage access request of the user;

a feature collection unit, configured to analyze the webpage, and collect feature metadata of the webpage; a policy unit, configured to query a preloading policy table, and obtain a preloaded webpage corresponding to the feature metadata of the webpage; The webpage is a webpage with the highest probability of subsequent access requesting on the basis of the webpage requested by the user; the preloading policy table includes the corresponding relationship between the feature metadata of the webpage and the preloaded webpage;

a cache unit, configured to cache the preloaded webpage in a cache;

a second response unit, configured to receive a subsequent webpage access request of the user, to query whether a webpage accessed by the subsequent webpage access request request is cached in the cache; and the subsequent access request is that the user requests access by the user Issued on the basis of a web page;

a loading unit, configured to: when the cache has the webpage requested by the subsequent webpage access request, upload the webpage accessed by the subsequent webpage access request from the cache.

An embodiment of the present invention provides a method for establishing a preloading policy table, including:

Obtaining a plurality of feature metadata corresponding to the plurality of web pages accessed by the user;

The plurality of feature metadata is analyzed to obtain a plurality of webpage access records of the user; the plurality of webpage access records of the user are sorted according to the chronological order of the access, and the plurality of webpages accessed by the user are obtained at the access time. Association relationship And obtaining, according to the association relationship, a webpage with the highest probability of subsequent access on the basis of the user accessing any one of the plurality of webpages;

Establishing an association relationship between a Uniform Resource Locator URL of any one of the plurality of web pages and a URL of the webpage with the highest probability of subsequent access.

A communication system based on a browser/server architecture, comprising: a browser and a server, the browser is configured to receive a service request including web address information, and load, from the server, a request corresponding to the monthly service request Web page;

The server is configured to send the webpage data corresponding to the service request to the browser; the browser is further configured to: analyze the webpage, collect feature metadata of the webpage; and query a preloading policy table, Obtaining a preloaded webpage corresponding to the feature metadata of the webpage; the preloading webpage is a webpage with the highest probability of subsequent request access on the basis of the webpage requested by the user; the preloading policy table includes Corresponding relationship between the feature metadata of the webpage and the preloaded webpage;

Cache the preloaded web page in a cache;

Receiving a subsequent webpage access request of the user, and querying, in the cache, whether the webpage accessed by the subsequent webpage access request request is cached; the subsequent access request is sent by the user on the basis of the webpage requested by the user; Loading the webpage accessed by the subsequent webpage access request request from the cache.

The embodiment of the present invention determines the page that the user is most likely to access next time by collecting the feature metadata of the webpage and the query preloading policy table, and caches the user's possible access in advance when the user is normally browsed. The next page data, when the user requests the next page, directly reads the data from the cache, overcoming the problem that the user waits for too long after the user operates the front end, because the browser needs to read a large amount of data from the server. Improve the user experience. DRAWINGS

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

FIG. 1 is a schematic diagram of a network management system according to an embodiment of the present invention; 2 is a flowchart of a communication method based on a browser/server architecture according to an embodiment of the present invention; FIG. 3 is a schematic diagram of a preloading policy table according to an embodiment of the present invention;

4 is a flowchart of a webpage content preloading method according to an embodiment of the present invention;

FIG. 5 is a flowchart of a method for updating a preloading policy table according to an embodiment of the present invention;

6 is a schematic diagram of a webpage content preloading apparatus according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of a communication system based on a browser/server architecture according to an embodiment of the present invention; FIG. 8 is a flowchart of a method for establishing a preloading policy table according to an embodiment of the present invention. detailed description

BRIEF DESCRIPTION OF THE DRAWINGS The technical solutions in the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative work are within the scope of the present invention.

In order to enable a person skilled in the art to better understand the technical solution provided by the embodiment of the present invention, a simple introduction is made to the HTTP (Hyper Text Transfer Protocol) communication mechanism for web browsing:

One of the most widely used network protocols on the HTTP Internet, all WWW files must comply with this standard. The HTTP protocol defines how the Web client requests a Web page from a Web server, and how the server passes the Web page to the client. The HTTP protocol uses a request/response model. In a complete web browsing process, the following four steps are followed between the web browser and the web server following the HTTP protocol:

(1) establishing a TCP connection;

Before web browsing, the web browser first establishes a connection with the web server through the network. The connection is completed by TCP. The protocol and the IP protocol jointly build the Internet, that is, the famous TCP/IP protocol family, so the Internet is It is called a TCP/IP network. HTTP is a higher-level application layer protocol than TCP. According to the rules, only the lower layer protocol can be established before the connection of the layer protocol can be established. Therefore, the TCP connection must be established first. The port number of the general TCP connection is 80.

(2) the web browser sends a webpage request message to the web server;

Once the TCP connection is established, the web browser sends a web page request message to the web server. The web page request message includes: the requested method, the URL, the protocol version, the request header, and the request data. Its The request method has GET, POST, HEAD, PUT, DELETE, OPTIONS, TRACE, CONNECT, and the GET method is generally used for web browsing; the URL (Uniform Resource Locator) is also called the web address, The address of a standard resource on the Internet; the request header consists of a key/value pair, one pair per line, and the keyword and value are separated by the English colon ":". The request header notification server has information about the client request. Typical request headers are:

User-Agent: The type of browser that generated the request;

Accept: a list of content types identifiable by the client;

Host: The host name of the request, allowing multiple domain names to be in the same IP address, that is, the virtual host.

Request data is not used in the GET method, but in the POST method.

(3) the web server receives the request and returns the page data;

The web server parses the web page request message, locates the request resource, and writes the page data to the TCP socket, which is read by the client. The page data returned by the web server consists of a status line, a response header, a blank line, and a response data.

(4) The web browser loads and displays the page according to the received page data.

The first embodiment of the present invention provides a communication method based on a browser/server architecture. The method is applied to a network management system or an enterprise network management system. It should be noted that the network management system, hereinafter referred to as the network management, is A software-based distributed network application system, whose purpose is to manage the network and make the network operate efficiently; the functions of the network management are generally divided into five management functions: performance management, configuration management, security management, billing management, and fault management; The objects of network management generally include routers, switches, and HUBs. The main body of network management is the network administrator. Similar to the network management, the enterprise network management system is also a software-based distributed network application system. The main difference between the enterprise network management system and the network management is that the management object of the enterprise network management system is generally a service.

FIG. 1 is a schematic diagram of a network management system according to an embodiment of the present invention. According to FIG. 1, a client is configured to respond to a user operation, and a client is communicatively coupled to a server through a network, and the network may be a local area network or the Internet or both. The client can be a general-purpose personal computer including a processor, temporary and permanent storage devices, an input/output subsystem, and a bus that can form a communication channel between the general-purpose personal computer components, such as an Ethernet interface; the client can also It is a handheld device, a set-top terminal, a mobile phone, a PDA, etc., and multiple clients can be communicatively coupled to the network. When a user on the client wants to get data from the server, the user can utilize the browser, and the browser can be installed on the local client or its remote end. The browser sends a request to the server over the network, requesting that the specified content be obtained from the server's data storage device. The server responds to the browser's request and sends the specified content to the browser over the network.

2 is a flow chart of a communication method based on a browser/server architecture according to Embodiment 1 of the present invention. Referring to FIG. 2, the webpage content loading method provided by the embodiment of the present invention specifically includes the following steps: Step 201: The browser receives a service request including the web address information, and sends an HTTP request packet including the web address information and the user parameter to the server. ;

The service request may be a request initiated by the user directly inputting the web address in the browser client, or may be a request initiated by the "application side" after the user triggers or sets the service through the webpage.

Step 202: The server receives an HTTP request packet sent by the browser, and returns corresponding page data to the browser according to the HTTP request packet.

According to the HTTP communication mechanism of the web browsing described above, after receiving the HTTP request message sent by the browser, the server parses the HTTP request message, locates the request resource, and writes the corresponding page data to the TCP socket. The browser reads.

Step 203: The browser receives the page data returned by the server, parses the page data, and displays the page.

The page data returned by the server consists of a status line, a response header, a blank line, and response data. Specifically, in an embodiment, after receiving the page data returned by the server, the browser first parses the status line to view a status code indicating whether the request is successful; and then parses each response header, and the response header informs that the following is a number of bytes. The character set of the HTML document and the document; Finally, the browser reads the response data HTML, formats it according to the syntax of the HTML, and displays it in a browser window.

Step 204: The browser analyzes the displayed webpage, and collects the feature metadata of the webpage. For the characteristics of the network management, in one embodiment, the user feature metadata includes: a user name, a network element, a function classification, and a URL, where the user The name refers specifically to the user name of the administrator currently operating at the front end of the network management system; the network element represents which network element in the network is currently operating, such as a router, switch, or HUB; the function classification indicates the current network management page. Functions, such as performance management, configuration management, security management, accounting management, or fault management. URL (Uniform Resource Locator) is also called a web address. It refers to the resources of the page accessed by the current user in the server. address.

For another feature of the enterprise network management system, in another embodiment, the user feature metadata includes: a username, a service, a function classification, and a URL. The user name refers specifically to the user name of the administrator currently operating in the front end of the enterprise network management system; the service specifically refers to which type of front end of the enterprise network management system is currently being used. Services perform operations, such as video conferencing services, cloud computing services, etc.; functional classification indicates what operations are performed on the current service, such as configuration, testing, etc.; URL refers to the resource address of the page accessed by the current user in the server.

Specifically, a part of the user feature metadata, such as a user name and a function category, is included in a response header of the page data, and a part of the data, for example, the URL is included in the HTTP request message, and is in the HTTP message. The user character metadata can be obtained by parsing the URL and the response data header corresponding to the HTTP message.

Step 205: The browser queries the preloading policy table according to the collected feature metadata, and obtains a preloaded webpage corresponding to the feature metadata of the webpage. The preloading webpage is based on the webpage requested by the user. The webpage with the highest probability of subsequent access requests; the preloading policy table includes the corresponding relationship between the feature metadata of the webpage and the preloaded webpage;

It should be noted that the pre-loading policy table is a URL association table pre-defined according to the operation habits of most users in the network management system, and stores the correspondence between the feature metadata of the current webpage of the user and the pre-loaded webpage. The preloaded webpage is one or more webpages with the highest probability that the user is most likely to visit or subsequently access after the current webpage is accessed.

Specifically, in an embodiment, the server performs statistics on the URLs of multiple operations of multiple users in the front end based on the method of probability statistics. For each webpage accessed by the user, the statistical user accesses the webpage, and then the most Frequently accessed, that is, the URL of a webpage with the most access times. The UL is the URL of the preloaded webpage, and associates the UL with the URL of the currently visited webpage of the user, and adds it to the preloading policy table. It can be understood that, in another embodiment, there may be multiple pre-loaded webpages. Specifically, for each webpage accessed by the user, the user may count the most frequently accessed, ie, the number of visits, after accessing the webpage. The UL of the plurality of web pages, for example, three, associates the plurality of URLs with the URL of the currently accessed webpage of the user, and adds to the preloading policy table. FIG. 3 is a schematic diagram of a preloading policy table according to an embodiment of the present invention. According to Figure 3, the preload policy table consists of two parts: the currently accessed URL and the URL of the preloaded web page.

In an embodiment, when the query is performed, the URL in the collected feature metadata may be used as a key value, and a pre-loading policy table is used to find a pre-corresponding corresponding to the URL by using a hash index method. The URL of the web page is loaded, and then the preloaded data is obtained from the server according to the URL of the preloaded webpage found. It should be noted that the Hash index method has the advantage of quick search as a specific search method, which can improve the matching speed. Understandably, the hash index method is not a match. The only way to implement the hash index is as an example and should not be construed as limiting the embodiments of the present invention.

Step 206: The browser caches the obtained preloaded webpage in the cache.

Specifically, the cache here may be a browser-local cache or other cache that is physically or logically connected to the browser.

Further, the communication method provided by the embodiment of the present invention further includes:

Step 207: The browser receives the next service request, determines whether the requested page data has been preloaded into the cache, and if so, loads the page data from the cache, and displays the page.

Further, in order to perform the real-time update of the pre-loading policy table according to the user's preference to achieve an optimal user experience, the communication method provided by the embodiment of the present invention further includes:

Step 204a: The browser uploads the collected user feature metadata to the server, so that the server updates the preloading policy table according to the uploaded user feature metadata.

According to the foregoing technical solution, the network management system and the enterprise network management system collect the user's feature metadata and the query preloading policy table to determine the next most likely page to be accessed by the user, and ensure that the user browses the service normally. In case, the next page data that the user may access is cached in advance, so that when the user requests the next page, the data is directly read from the cache, which overcomes the problem that the user needs to read from the server after the user operates in the front end of the network management system. Taking a large amount of data and causing the user to wait too long, the user experience is improved; further, by analyzing the collected feature metadata and updating the preloading policy table based on the analysis result, the user's preference may be The preloaded policy table is updated in real time to achieve the best user experience.

Based on the description of the first embodiment of the present invention, those skilled in the art should understand that in the first embodiment of the present invention, the preloading of webpage content is mainly completed by a browser. In practical applications, these steps are not limited to using a browser. The implementation of the technical solution provided by the embodiment of the present invention is not limited to the network management or enterprise network management, and may be implemented by another entity, such as a browser control or a module. The system can be extended to all applications that use the B/S architecture, such as Internet web browsing. Based on this idea, the second embodiment of the present invention provides a webpage content preloading method. As shown in FIG. 4, the webpage content preloading method provided by the second embodiment of the present invention includes:

Step 401: In response to a webpage access request of the user, load a webpage requested by the user from the server; specifically, loading the server from the server according to the HTTP communication mechanism of the webpage browsing introduced previously. The process of requesting the accessed webpage data by the user is: after receiving the webpage access request of the user, the browser sends an HTTP request packet containing the webpage information to the server, and the server parses the HTTP request packet sent by the browser. The HTTP request message locates the request resource, and writes the corresponding page data to the TCP socket, which is read by the browser.

The webpage access request may be a request initiated by the user directly inputting the web address in the browser client, or may be a request initiated by the "application side" after the user triggers or sets the service through the webpage; in an embodiment, The webpage access request may further include a user parameter, and the user parameter may specifically include: a screen size of the client device, a display format supported by the device, and a computing capability of the device.

Step 402: Analyze the webpage requested by the user to collect the feature metadata of the webpage. It should be noted that the webpage data returned by the server is composed of a status line, a response header, a blank line, and a response data.

In an embodiment, the feature metadata of the webpage may include: a function of the webpage and a URL of the webpage; wherein the function of the webpage may be obtained by UL parsing the webpage, for example, the number of bars of the webpage to determine the webpage Hierarchy (from the beginning of the URL to the end of the question mark, no question mark to the end of the space), there are 3 slashes here, this means that the page is a third-level page; parsing the content between the slashes, you can get keywords, such as news , lady, the type or function of this page is female, news.

In an embodiment, for the characteristics of the network management, the feature metadata of the webpage may include: a user name, a network element, a function classification, and a UL, where the user name specifically refers to a user name of an administrator currently operating at the front end of the network management; The NE indicates which network element in the network is currently operating, such as a router, switch, or HUB. The function classification indicates the current network management page functions, such as performance management, configuration management, security management, accounting management, or fault. Management, etc.; URL (Uniform Resource Locator), also known as web address, refers to the resource address of the page accessed by the current user in the server.

For another feature of the enterprise network management system, in another embodiment, the feature metadata of the web page includes: a username, a service, a function classification, and a URL. The user name refers specifically to the user name of the administrator currently operating in the front end of the enterprise network management system; the service specifically refers to which service is currently being operated by the front end of the enterprise network management system, for example, a video conference service, a cloud computing service, etc.; The classification indicates what kind of operation is performed on the current service, such as configuration, testing, etc.; the URL refers to the page accessed by the current user on the server. The resource address in .

Specifically, the feature metadata of the webpage, such as the user name and the function classification, is included in the response header of the page data, and a part of the data, for example, the URL is included in the HTTP request packet, and the UL in the HTTP packet is The response data header corresponding to the HTTP message is parsed, and the feature metadata of the web page can be obtained.

Step 403: Query a preloading policy table, and obtain a preloaded webpage corresponding to the feature metadata of the webpage. The preloading webpage is a webpage with the highest probability of subsequent request access on the basis of the webpage requested by the user. ;

It should be noted that the preloading policy table stores the correspondence between the feature metadata of the webpage and the preloaded webpage; in one embodiment, the preloading policy table is pre-defined based on the user's operating habits. a URL association table, which stores a correspondence between a UL of each user currently visiting a webpage and a URL of a preloaded webpage, where the preloaded webpage is based on the user accessing the current webpage, and the probability of subsequent access is the largest or the most One or more web pages that are likely to be accessed.

Specifically, in an embodiment, the URL of the multiple operations of the multiple users in the front end may be counted according to the method of probability statistics. For each webpage accessed by each user, the user is counted after accessing the webpage. Next, the most frequently accessed, that is, the URL of the most visited webpage, which is the URL of the preloaded webpage, associates the URL with the URL of the currently visited webpage of the user, and adds it to the preloading policy table. It can be understood that, in another embodiment, there may be multiple pre-loaded webpages. Specifically, for each webpage accessed by the user, the user may count the most frequently accessed, ie, the number of visits, after accessing the webpage. The URLs of the plurality of web pages, for example, three, associate the plurality of URLs with the URL of the currently accessed webpage of the user, and add to the preloading policy table. FIG. 3 is a schematic diagram of a preloading policy table provided by an embodiment of the present invention. According to Figure 3, the preload policy table consists of two parts: the currently accessed URL and the URL of the preloaded web page.

In an embodiment, when the query is performed, the URL in the collected feature metadata may be used as a key value, and a pre-loading policy table is used to find a pre-corresponding corresponding to the URL by using a hash index method. The URL of the web page is loaded, and then the preloaded data is obtained from the server according to the URL of the preloaded webpage found. It should be noted that the Hash index method has the advantage of quick search as a specific search method, which can improve the matching speed. It is to be understood that the method of the hash index is not the only implementation of the matching, and the manner of the hash index is not to be construed as limiting the embodiment of the present invention. Step 404: Cache the obtained preloaded webpage in a cache.

Step 405: Receive a subsequent access request of the user, and query whether a webpage accessed by the access request request is cached in the cache; and the subsequent access request is sent by the user on the basis of the webpage requested by the user;

Step 406, if yes, loading the webpage accessed by the subsequent webpage access request request from the cache. Further, the communication method provided by the embodiment of the present invention further includes:

Step 407, if no, loading a webpage requested by the user from the server.

Step 408: Update the preloading policy table according to the plurality of feature metadata of the webpage accessed by the user.

In an embodiment, as shown in FIG. 5, the preloading policy table is updated according to the plurality of feature metadata of the webpage that is subsequently accessed by the user, and specifically includes:

Step 501: Obtain a plurality of feature metadata of a webpage that the user subsequently accesses;

Step 502: Analyze the plurality of feature metadata to obtain a plurality of webpage access records of the user. Step 503: Sort the plurality of webpage access records of the user according to a chronological order of the access, and obtain the user access. The relationship between multiple web pages in terms of access time;

Step 504: Based on the association relationship, obtain, according to the association relationship, a webpage that has the greatest probability of subsequent access on the basis of the user accessing any one of the plurality of webpages;

Step 505: Establish an association relationship between a Uniform Resource Locator URL of the webpage of any one of the plurality of webpages and a URL of the webpage with the highest probability of subsequent access.

In another embodiment, the preloading policy table is updated according to the plurality of feature metadata of the webpage accessed by the user, and the method may be as follows: after the server obtains the feature metadata of the webpage accessed by the user, the feature element is obtained according to the feature element. The data has the following logical meaning:

Webmaster: "User" operates "URL" on the "Function Classification" of "Network Element". Enterprise Network Management System: "User" operates "URL" on the "Function Classification" of "Service"; therefore, each user An operation can be abstracted into the above logical meaning. According to the logical meaning, the user's operation can be changed into a set of operation records sorted by time. When the preloading strategy is formed, The preloading policy table is updated by sorting each user's operation record, associating the user with the most operations and the next operation association.

In the second embodiment of the present invention, the feature metadata of the webpage and the query preloading policy table are used to determine the page that the user is most likely to access next time, and the user may access the cache in advance when the user is normally browsed. The next page data makes the user read the data directly from the cache when requesting the next page, which overcomes the problem that the user waits too long because the browser needs to read a large amount of data from the server when the user operates in the front end. The user experience is improved. Further, by analyzing the collected feature metadata and updating the preloading policy table based on the analysis result, the preloading policy table can be updated in real time according to the user's preference to achieve the best. user experience.

Embodiment 3 As shown in FIG. 6, Embodiment 3 of the present invention provides a webpage content preloading apparatus, including:

The first response unit 610 is configured to: in response to the webpage access request of the user, load a webpage requested by the user from the server;

a feature collection unit 620, configured to analyze the webpage, and collect feature metadata of the webpage; the policy unit 630 is configured to acquire a preloaded webpage corresponding to the feature metadata of the webpage; a webpage with the highest probability of subsequent access requests based on the webpage requested by the user; the preloading policy table includes the corresponding relationship between the feature metadata of the webpage and the preloaded webpage;

a cache unit 640, configured to cache the preloaded webpage in a cache;

The second response unit 650 is configured to receive a subsequent webpage access request of the user, and query whether the webpage accessed by the subsequent webpage access request request is cached in the cache; the subsequent access request is a webpage requested by the user at the user Issued on the basis of

The loading unit 660 is configured to: when the cache has the webpage requested by the subsequent webpage access request, load the webpage accessed by the subsequent webpage access request from the cache.

Further, in an embodiment, the loading unit 660 is further configured to: when the cache does not have the webpage accessed by the subsequent webpage access request, request the webpage accessed by the subsequent webpage access request from the server.

It should be noted that the specific working steps of the first response unit 610 may refer to step 401. The specific work of the feature collecting unit 620 may refer to step 402. The specific working steps of the policy unit 630 may be performed. Referring to step 403, the specific working steps of the buffer unit 640 may refer to step 404. The specific working steps of the second response unit 650 may refer to step 405. The specific working steps of the loading unit 660 may refer to step 406.

The third embodiment of the present invention determines the next most likely page to be accessed by the user by collecting feature metadata of the webpage and querying the preloading policy table. In the case of ensuring that the user browses the service normally, the user may access the cache in advance. The next page data, when the user requests the next page, directly reads the data from the cache, overcoming the problem that the user waits too long when the user needs to read a large amount of data from the server when the user operates in the front end. Improve the user experience.

Embodiment 4 As shown in FIG. 7, a fourth embodiment of the present invention provides a communication system based on a browser/server architecture, including: a browser and a server, where:

The browser is configured to receive a webpage access request of the user, load the webpage requested by the user from the server, and collect the feature metadata of the webpage by analyzing the page information, and query the preloading policy table based on the collected feature metadata. Obtaining a preloaded webpage corresponding to the feature metadata of the webpage, and buffering the obtained preloaded webpage into a cache; further, the browser is further configured to: receive a subsequent webpage access request of the user, and query whether the cache is cached a subsequent webpage access request requesting access to the webpage; if yes, loading the webpage accessed by the subsequent webpage access request request from the cache. The subsequent access request is sent by the user on the basis of the webpage requested by the user; the webpage access request may be a request initiated by the user directly by inputting a web address in the browser client, or may be a webpage of the user. A request initiated by the "app side" after triggering or setting up a business.

The server is configured to send webpage data corresponding to the webpage access request received by the browser to the browser.

Referring to FIG. 7, in the communication system of the embodiment of the present invention, the browser mainly includes: a first receiving module 710, a preloading module 720, a second receiving module 730, and a loading module 740.

The first receiving module 710 is configured to receive a webpage access request of the user, and load the webpage requested by the user from the server. It should be noted that the first receiving module 710 obtains webpage data requested by the user from the server according to the HTTP communication mechanism of the webpage browsing introduced earlier.

The preloading module 720 is configured to analyze the page loaded by the first receiving module 710, collect the feature metadata of the webpage, and obtain the next batch of page data that the user may access by querying the preloading policy table according to the collected feature metadata. Finally, the obtained page data is cached. Further, the preloading module 720 specifically includes: The collecting unit 7201 is configured to analyze a page loaded by the first receiving module 710, and collect feature metadata of the webpage;

According to the HTTP communication mechanism of the web browsing described earlier, the page data returned by the server is composed of a status line, a response header, a blank line, and a response data. Specifically, in an embodiment, the feature metadata of the webpage may include: a function of the webpage and a URL of the webpage; wherein the function of the webpage may be obtained by parsing a URL of the webpage, for example, the URL of the webpage is / News/lady/default.j sp?user=abc&refer=http://www.163.com/lady , to judge the page level according to the number of slashes (from the beginning of the URL to the end of the question mark, no question mark to the end of the space ), there are 3 slashes here, which means that this page is a third-level webpage; parsing the content between slashes, you can get keywords, such as news, lady, then the type or function of this webpage is female, news .

For another feature of the enterprise network management system, in another embodiment, the feature metadata of the webpage includes: a username, a service, a function classification, and a URL. The user name refers specifically to the user name of the administrator currently operating in the front end of the enterprise network management system; the service specifically refers to which service is currently being operated by the front end of the enterprise network management system, for example, a video conference service, a cloud computing service, etc.; Classification indicates what operations are performed on the current service, such as configuration, testing, etc.; URL refers to the resource address of the page accessed by the current user in the server.

Specifically, the feature metadata of the webpage, such as the user name and the function classification, is included in the response header of the page data, and a part of the data, such as the UL, is included in the HTTP request packet, and the collecting unit can obtain the feature element of the webpage. data.

The querying unit 7202 is configured to query the preloading policy table according to the collected feature metadata, and obtain a preloaded webpage corresponding to the feature metadata of the webpage; the preloading webpage is a basis of the webpage requested by the user to visit The page with the highest probability of subsequent request access; the preloading strategy table package Corresponding relationship between the feature metadata of the webpage and the preloaded webpage;

It should be noted that the pre-loading policy table is a URL association table pre-defined according to the operating habits of each user in the network management system, and stores the correspondence between the URL of the currently accessed webpage and the UL of the pre-loaded webpage. Loading a web page is one or more web pages that the user is most likely to access after visiting the current web page.

Specifically, in an embodiment, based on the method of probability statistics, statistics are performed on the URL of multiple operations of each user in the front end. For each webpage accessed by the user, after counting the webpage, the statistical user is most often followed. Access, that is, the UL of a webpage with the most access times, which is the URL of the preloaded webpage, associates the URL with the UL of the currently accessed webpage of the user, and adds it to the preloading policy table. It can be understood that, in another embodiment, there may be multiple pre-loaded webpages. Specifically, for each webpage accessed by the user, the user may count the most frequently accessed, ie, the number of visits, after accessing the webpage. The URLs of the plurality of web pages, for example, three, associate the plurality of URLs with the URL of the currently accessed webpage of the user, and add to the preloading policy table. FIG. 3 is a schematic diagram of a preloading policy table according to an embodiment of the present invention. According to Figure 3, the preload policy table consists of two parts: the URL currently accessed and the U L of the preloaded web page.

In an embodiment, when the query is performed, the URL in the collected feature metadata may be used as a key value, and a pre-loading policy table is used to find a pre-corresponding corresponding to the URL by using a hash index method. The URL of the web page is loaded, and then the preloaded data is obtained from the server according to the URL of the preloaded webpage found. It should be noted that the Hash index method has the advantage of quick search as a specific search method, which can improve the matching speed. It is to be understood that the method of the hash index is not the only implementation of the search. Therefore, the manner of the hash index is not to be construed as limiting the embodiment of the present invention.

The storage unit 7203 is configured to cache the preloaded webpage acquired by the query unit 7202.

Specifically, the storage unit 7203 may be a browser-local cache or other cache that is physically or logically connected to the browser.

Further, in order to update the preloading policy table in real time according to the user's preference, the preloading module 720 further includes: an uploading unit 7204, configured to upload the webpage feature metadata collected by the collecting unit 7201 to the server, so that the server according to the The feature metadata of the webpage is updated, and the preloading policy table is updated.

Correspondingly, in order to periodically update the preloading policy table, the server is further configured to: update the preloading policy table according to the feature metadata of the webpage uploaded by the uploading unit 7204. Specifically, the server implements the update of the preload policy table by the following steps:

(1) obtaining a plurality of feature metadata of a webpage subsequently accessed by the user;

(2) analyzing the plurality of feature metadata to obtain a plurality of webpage access records of the user;

(3) sorting the plurality of webpage access records of the user according to the chronological order of the access, and obtaining the association relationship of the plurality of webpages accessed by the user in the access time;

(4) based on the association relationship, obtaining, by the user, a webpage having the highest probability of subsequent access on the basis of accessing any one of the plurality of webpages;

(5) establishing an association relationship between a Uniform Resource Locator URL of any one of the plurality of web pages and a URL of the webpage having the highest probability of subsequent access.

The second receiving module 730 is configured to receive a subsequent webpage access request of the user, and query whether the webpage accessed by the subsequent webpage access request request is cached in the cache; the subsequent access request is based on the webpage requested by the user by the user. dispatched.

The loading module 740 is configured to: when the cache has the webpage requested by the subsequent webpage access request request, load the webpage accessed by the subsequent webpage access request request from the cache.

Further, the loading module 740 is further configured to: when the cache does not have the webpage requested by the subsequent webpage access request, upload the webpage accessed by the subsequent webpage access request request from the server.

The browser/server architecture-based communication system provided by the fourth embodiment of the present invention collects feature data of the webpage based on the webpage, and uses a preloading module to cache a page that the user may access in advance while ensuring that the user browses the service normally. The data, so that when the user requests the next page, the data is directly read from the cache, which overcomes the problem that the user waits for too long after the user operates the front end, because the browser needs to read a large amount of data from the server, and improves the problem. User experience; Further, by analyzing the collected feature metadata and updating the preloading policy table based on the analysis result, the preloading policy table can be updated in real time according to the user's preference to achieve the best user experience.

Embodiment 5 As shown in FIG. 8, Embodiment 5 of the present invention provides a method for establishing a preloading policy table, including:

Step 801: Obtain a plurality of feature metadata corresponding to multiple webpages accessed by the user;

Step 802: Analyze the plurality of feature metadata to obtain a plurality of webpage access records of the user. Step 803: Sort the plurality of webpage access records of the user according to a chronological order of the access, and obtain the user access The relationship between multiple web pages in terms of access time; Step 804: Based on the association relationship, obtain, according to the association relationship, a webpage that has the greatest probability of subsequent access on the basis of the user accessing any one of the plurality of webpages;

Step 805: Establish an association relationship between a Uniform Resource Locator URL of any one of the plurality of webpages and a URL of the webpage with the highest probability of subsequent access.

The fifth embodiment of the present invention, through the above technical solution, collects and analyzes the feature metadata of the webpage accessed by the user, and establishes a preloading policy table according to the user's preference based on the analysis result, so as to facilitate the subsequent access to the webpage directly from the preloading strategy. Get the preloaded page in the table.

A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium, the program When executed, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Finally, it should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that The technical solutions described in the foregoing embodiments are modified, or some of the technical features are equivalently replaced; and the modifications or substitutions do not deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

A webpage content preloading method, comprising:

Responding to the webpage access request of the user, loading the webpage requested by the user from the server; analyzing the webpage, and collecting feature metadata of the webpage;

Cache the preloaded web page in a cache;

Receiving a subsequent webpage access request of the user, and querying, in the cache, whether the webpage accessed by the subsequent webpage access request request is cached; the subsequent webpage access request is sent by the user on the basis of the webpage requested by the user to visit ;

If so, the webpage accessed by the subsequent webpage access request request is loaded from the cache.

2. The method of claim 1, further comprising: if not, loading a webpage accessed by the subsequent webpage access request from the server.

3. The method according to claim 1 or 2, further comprising:

Obtaining a plurality of feature metadata of the webpage subsequently accessed by the user;

The plurality of feature metadata is analyzed to obtain a plurality of webpage access records of the user; the plurality of webpage access records of the user are sorted according to the chronological order of the access, and the plurality of webpages accessed by the user are obtained at the access time. Association relationship

And obtaining, according to the association relationship, a webpage with the highest probability of subsequent access on the basis of the user accessing any one of the plurality of webpages; Establishing an association relationship between a uniform resource locator URL of any one of the plurality of web pages and a URL of the webpage with the highest probability of subsequent access.

The method according to any one of claims 1-3, wherein the cache is a cache local to the browser or another cache physically or logically connected to the browser.

5. A web content preloading device, comprising:

a cache unit, configured to cache the preloaded webpage in a cache;

The device of claim 5, wherein the loading unit is further configured to: load the subsequent webpage from the server when the webpage requested by the subsequent webpage access request request is not in the cache Access the web page requesting access.

7. A method for establishing a preloading policy table, comprising: Obtaining a plurality of feature metadata corresponding to the plurality of web pages accessed by the user;

Analyzing the plurality of feature metadata to obtain a plurality of webpage access records of the user;

The multiple webpage access records of the user are sorted according to the chronological order of the access, and the association relationship of the plurality of webpages accessed by the user in the access time is obtained;

And obtaining, according to the association relationship, a webpage with the highest probability of subsequent access on the basis of the user accessing any one of the plurality of webpages;

8. The method according to claim 7, wherein the feature metadata of the webpage comprises: a function of the webpage and a URL of the webpage.

A communication system based on a browser/server architecture, comprising: a browser and a server, wherein the browser is configured to receive a service request including web address information, and load and request the service from the server Corresponding web page;

Cache the preloaded web page in a cache;

Receiving a subsequent webpage access request of the user, and querying, in the cache, whether the webpage accessed by the subsequent webpage access request request is cached; the subsequent access request is that the user requests access by the user The web page is issued on the basis of the web page; if so, the web page accessed by the subsequent web page access request request is loaded from the cache.

The system of claim 9, wherein the browser is further configured to: upload feature metadata of the collected webpage to a server, so that the server collects feature metadata of the webpage, and updates the pre- Load the policy table.