[go: up one dir, main page]

WO2013091346A1 - Procédé, dispositif et système de préchargement de contenu de page internet - Google Patents

Procédé, dispositif et système de préchargement de contenu de page internet Download PDF

Info

Publication number
WO2013091346A1
WO2013091346A1 PCT/CN2012/075779 CN2012075779W WO2013091346A1 WO 2013091346 A1 WO2013091346 A1 WO 2013091346A1 CN 2012075779 W CN2012075779 W CN 2012075779W WO 2013091346 A1 WO2013091346 A1 WO 2013091346A1
Authority
WO
WIPO (PCT)
Prior art keywords
webpage
user
access
request
subsequent
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2012/075779
Other languages
English (en)
Chinese (zh)
Inventor
林文旭
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2013091346A1 publication Critical patent/WO2013091346A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/957—Browsing optimisation, e.g. caching or content distillation
    • G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching

Definitions

  • the present invention relates to the field of the Internet, and in particular, to a webpage content preloading method, apparatus, and system.
  • B/S architecture namely browser and server architecture
  • 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.
  • 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.
  • 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.
  • EAI Edge Fragment
  • 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 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;
  • 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;
  • the subsequent access request is sent by the user on the basis of the webpage requested by the user;
  • 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:
  • 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;
  • 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;
  • 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.
  • 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
  • FIG. 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
  • FIG. 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
  • HTTP Hyper Text Transfer Protocol
  • 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:
  • the web browser 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.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • the network management system hereinafter referred to as the network management
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the browser 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.
  • Step 204 The browser analyzes the displayed webpage, and collects the feature metadata of the webpage.
  • 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
  • URL Uniform Resource Locator
  • 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.
  • 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 preloading policy table includes the corresponding relationship between the feature metadata of the webpage and the preloaded webpage;
  • 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.
  • 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.
  • FIG. 3 is a schematic diagram of a preloading policy table according to an embodiment of the present invention.
  • the preload policy table consists of two parts: the currently accessed URL and the URL of the preloaded web page.
  • 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.
  • 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.
  • the cache here may be a browser-local cache or other cache that is physically or logically connected to the browser.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the webpage data returned by the server is composed of a status line, a response header, a blank line, and a response data.
  • 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.
  • 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.
  • 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 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 feature metadata of the webpage 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. ;
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the cache here may be a browser-local cache or other cache that is physically or logically connected to the browser.
  • 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.
  • 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.
  • the communication method provided by the embodiment of the present invention further includes:
  • Step 408 Update the preloading policy table according to the plurality of feature metadata of the webpage accessed by the user.
  • 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.
  • 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.
  • 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.
  • 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.
  • the preloading policy table can be updated in real time according to the user's preference to achieve the best. user experience.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the server is configured to send webpage data corresponding to the webpage access request received by the browser to the browser.
  • 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;
  • the page data returned by the server is composed of a status line, a response header, a blank line, and a response data.
  • 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.
  • 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.
  • the feature metadata of the webpage such as the user name and the function classification
  • a part of the data such as the UL
  • 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;
  • 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.
  • 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.
  • FIG. 3 is a schematic diagram of a preloading policy table according to an embodiment of the present invention.
  • the preload policy table consists of two parts: the URL currently accessed and the U L of the preloaded web page.
  • 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.
  • 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.
  • the storage unit 7203 may be a browser-local cache or other cache that is physically or logically connected to the browser.
  • 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.
  • 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:
  • 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.
  • 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 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 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 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.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Conformément à un mode de réalisation, la présente invention concerne un procédé de préchargement de contenu de page Internet, lequel procédé consiste à : acquérir les métadonnées de caractéristique d'une page Internet selon les informations de page Internet auxquelles un utilisateur accède actuellement; rechercher une table de politique de préchargement selon les métadonnées de caractéristique acquises et obtenir les données préchargées; et charger les données préchargées obtenues dans une mémoire cache. Conformément au mode de réalisation, la présente invention concerne également un dispositif de préchargement de contenu de page Internet, un procédé d'établissement de table de politique de préchargement et un système de communication. Dans la solution technique ci-dessus, un module de cache stocke à l'avance les données de la page Internet suivante auxquelles un utilisateur peut accéder, sans interrompre la navigation, par l'utilisateur, sur la page Internet courante, permettant à l'utilisateur de lire directement des données provenant de la mémoire cache lorsqu'il demande la page Internet suivante, résolvant le problème dans un système de gestion de réseau selon lequel un utilisateur doit attendre pendant longtemps après avoir réalisé une opération de premier plan en raison du fait qu'un navigateur a besoin de lire une grande quantité de données provenant d'un serveur, permettant ainsi d'améliorer l'expérience d'utilisateur.
PCT/CN2012/075779 2011-12-22 2012-05-19 Procédé, dispositif et système de préchargement de contenu de page internet Ceased WO2013091346A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110434586.9A CN102446222B (zh) 2011-12-22 2011-12-22 一种网页内容预加载方法、装置及系统
CN201110434586.9 2011-12-22

Publications (1)

Publication Number Publication Date
WO2013091346A1 true WO2013091346A1 (fr) 2013-06-27

Family

ID=46008718

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/075779 Ceased WO2013091346A1 (fr) 2011-12-22 2012-05-19 Procédé, dispositif et système de préchargement de contenu de page internet

Country Status (2)

Country Link
CN (1) CN102446222B (fr)
WO (1) WO2013091346A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10169477B2 (en) 2013-12-30 2019-01-01 Samsung Electronics Co., Ltd. Method and system for rendering a web page free of inappropriate URLs
CN110855778A (zh) * 2019-11-13 2020-02-28 首都经济贸易大学 一种基于网络嗅探器的数据加载方法、装置和系统

Families Citing this family (81)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102446222B (zh) * 2011-12-22 2014-12-10 华为技术有限公司 一种网页内容预加载方法、装置及系统
CN103530292B (zh) * 2012-07-02 2016-05-25 阿里巴巴集团控股有限公司 网页显示方法和装置
CN103678307B (zh) * 2012-08-31 2016-07-13 腾讯科技（深圳）有限公司 页面显示方法及客户端
CN103677554B (zh) * 2012-09-17 2017-07-21 腾讯科技（深圳）有限公司 一种顺畅滑屏方法及装置
CN102831249A (zh) * 2012-09-19 2012-12-19 河南锐之旗信息技术有限公司 一种静态页面生成方法
CN103777868B (zh) * 2012-10-23 2016-08-24 福建星网视易信息系统有限公司 一种以页面为单位且具有后台加载和缓存逻辑的划屏方法
CN102968322B (zh) * 2012-11-22 2016-05-25 用友优普信息技术有限公司 数据加载装置和数据加载方法
CN103152426B (zh) * 2013-03-19 2016-12-28 北京奇虎科技有限公司 预加载客户端浏览的网页的服务器、系统和方法
CN104063392B (zh) * 2013-03-20 2018-07-03 腾讯科技（深圳）有限公司 一种阅读内容的加载方法及装置
CN103246713B (zh) * 2013-04-24 2016-05-11 优视科技有限公司 一种网页浏览方法及装置
CN103312785B (zh) * 2013-05-16 2016-10-26 新浪网技术(中国)有限公司 一种访问关系的确定方法及装置
CN103279538B (zh) * 2013-06-03 2016-09-28 北京奇虎科技有限公司 预加载访问网站中网页的服务器、浏览器客户端和方法
CN103338249B (zh) * 2013-06-26 2018-05-25 优视科技有限公司 缓存方法及装置
US10778680B2 (en) 2013-08-02 2020-09-15 Alibaba Group Holding Limited Method and apparatus for accessing website
CN104581753B (zh) * 2013-10-09 2018-06-26 中国移动通信集团设计院有限公司 一种计算网页加载时延的方法、装置及终端
CN103530160A (zh) * 2013-10-21 2014-01-22 迈普通信技术股份有限公司 一种页面加载的方法和装置
US9798827B2 (en) 2013-10-25 2017-10-24 Uc Mobile Co., Ltd. Methods and devices for preloading webpages
CN103729438B (zh) * 2013-12-30 2017-06-16 优视科技有限公司 网页预加载方法及装置
CN103544288B (zh) * 2013-10-28 2018-02-13 东莞宇龙通信科技有限公司 浏览器网页加载控制方法及装置
CN104636392B (zh) * 2013-11-13 2018-07-27 腾讯科技（北京）有限公司 进行推荐信息下发的方法、系统、服务器及浏览器
CN103559307A (zh) * 2013-11-18 2014-02-05 中国农业银行股份有限公司 一种查询的缓存方法及装置
US8924850B1 (en) 2013-11-21 2014-12-30 Google Inc. Speeding up document loading
CN103744862B (zh) * 2013-12-06 2017-02-22 长春吉大工易软件有限公司 一种基于Sencha Touch的移动办公应用的预加载优化方法
CN103618936A (zh) * 2013-12-16 2014-03-05 乐视致新电子科技（天津）有限公司 智能电视及其浏览器中链接页面的预加载方法和装置
CN104731817B (zh) * 2013-12-23 2019-11-22 腾讯科技（深圳）有限公司 一种网页展现方法和装置
CN103714172A (zh) * 2013-12-31 2014-04-09 华为技术有限公司 页面处理方法、装置及系统
CN105095253B (zh) * 2014-05-06 2020-11-24 腾讯科技（深圳）有限公司 网页显示方法及装置
CN105094861A (zh) * 2014-05-06 2015-11-25 腾讯科技（深圳）有限公司 网页应用程序加载方法、装置及系统
CN105095280B (zh) * 2014-05-13 2020-02-14 腾讯科技（深圳）有限公司 一种浏览器缓存方法和装置
CN105450579B (zh) * 2014-05-30 2019-03-29 广州市动景计算机科技有限公司 网络资源预加载方法、客户端及中间件服务器
CN104166569B (zh) * 2014-08-15 2017-09-22 北京彩云动力教育科技有限公司 一种前端页面加载的方法及系统
CN104361067B (zh) * 2014-11-05 2018-07-20 百纳（武汉）信息技术有限公司 一种浏览器网页信息的智能加载方法及系统
CN104298780B (zh) * 2014-11-05 2018-01-12 百纳（武汉）信息技术有限公司 一种浏览器网页信息的预获取方法及系统
CN104580521A (zh) * 2015-01-30 2015-04-29 宁波凯智信息科技有限公司 客户端顺畅访问服务器端数据的预加载方法及系统
CN104765812A (zh) * 2015-04-02 2015-07-08 天脉聚源（北京）教育科技有限公司 一种下载方法及系统
CN104731974A (zh) * 2015-04-13 2015-06-24 上海新炬网络信息技术有限公司 基于大数据流式计算的动态页面加载方法
CN105677381B (zh) * 2015-05-29 2019-07-12 深圳Tcl数字技术有限公司 预加载媒体文件的方法及装置
CN105094524A (zh) * 2015-06-17 2015-11-25 深圳市美贝壳科技有限公司 用于应用界面切换的数据刷新方法及系统
CN104991916B (zh) * 2015-06-24 2019-03-01 小米科技有限责任公司 网页的加载方法及装置
CN105117213B (zh) * 2015-07-30 2021-10-19 青岛海尔智能家电科技有限公司 一种基于发布-订阅模式的预处理方法及装置
CN105242960B (zh) * 2015-09-21 2020-02-18 青岛海信电器股份有限公司 一种处理系统功能调用请求的方法及浏览器
EP4300328B1 (fr) * 2015-10-28 2025-09-24 Snappi, Inc. Suggestion produite par machine en fonction du temps
CN105939208B (zh) * 2015-11-26 2019-05-07 杭州迪普科技股份有限公司 采样数据的传输方法及装置
CN105634972A (zh) * 2016-01-29 2016-06-01 四川长虹电器股份有限公司 一种提高Web客户端访问效率的方法
CN107145490B (zh) * 2016-03-01 2020-10-30 腾讯科技（深圳）有限公司 网页加载展示方法及网页加载展示装置
CN106210007B (zh) * 2016-06-30 2019-11-08 北京小米移动软件有限公司 资源下载方法及装置
CN106250529A (zh) * 2016-08-05 2016-12-21 成都佳荣科技有限公司 网页页面加载方法
CN106294682A (zh) * 2016-08-05 2017-01-04 成都佳荣科技有限公司 网页页面智能加载方法
CN106446174A (zh) * 2016-09-28 2017-02-22 江西博瑞彤芸科技有限公司 应用中页面加载的方法
CN106878372B (zh) 2016-11-07 2020-10-02 阿里巴巴集团控股有限公司 信息推送方法及装置
CN108073610B (zh) * 2016-11-11 2021-03-02 聚好看科技股份有限公司 实现网页页面加载的方法及装置
CN108228640A (zh) * 2016-12-21 2018-06-29 天脉聚源（北京）科技有限公司 一种互联网商城网页加载的方法和系统
CN106685715B (zh) * 2016-12-28 2019-11-08 重庆可兰达科技有限公司 客户端无限信息流免停顿分段加载数据的方法
CN106899689B (zh) * 2017-03-15 2020-05-05 腾讯科技（深圳）有限公司 一种信息预下发的方法及服务器
CN107016081A (zh) * 2017-03-30 2017-08-04 北京小米移动软件有限公司 页面加载方法及装置
US10749988B2 (en) * 2017-04-24 2020-08-18 Google Llc Methods, systems, and media for retrieving content associated with links
CN107229397A (zh) * 2017-06-08 2017-10-03 惠州Tcl移动通信有限公司 一种提高终端流畅度的方法、系统、终端以及存储装置
CN107404486B (zh) * 2017-08-04 2020-05-22 厦门市美亚柏科信息股份有限公司 解析Http数据的方法、装置、终端设备及存储介质
CN109429101B (zh) * 2017-08-31 2021-03-05 中国电信股份有限公司 交互式网络电视的桌面加载方法和装置
CN107544898A (zh) * 2017-09-08 2018-01-05 北京小米移动软件有限公司 数据获取方法、装置、设备和存储介质
CN109408751B (zh) * 2018-09-27 2022-08-30 腾讯科技(成都)有限公司 一种数据处理方法、终端、服务器及存储介质
CN109684575A (zh) * 2018-10-30 2019-04-26 平安科技（深圳）有限公司 网页数据的处理方法及装置、存储介质、计算机设备
CN110007978A (zh) * 2018-11-20 2019-07-12 阿里巴巴集团控股有限公司 一种预加载页面的方法、装置及设备
CN109889656B (zh) * 2018-12-29 2021-04-20 深圳Tcl新技术有限公司 一种数据读取方法、装置、设备及存储介质
CN111767485A (zh) * 2019-04-01 2020-10-13 广州精选速购网络科技有限公司 一种网页展示方法、系统、电子设备及介质
CN110162720B (zh) * 2019-04-16 2023-07-18 平安科技（深圳）有限公司 网页页面加载方法、装置、计算机设备及存储介质
CN111859077B (zh) * 2019-04-24 2024-09-20 北京沃东天骏信息技术有限公司 数据处理方法、装置、系统、计算机可读存储介质
CN110489696B (zh) * 2019-07-31 2023-07-04 上海艾融软件股份有限公司 缓存更新方法、装置及电子设备、存储介质
CN110795655B (zh) * 2019-10-30 2022-07-08 中国人民解放军63850部队 一种基于爬虫的预测性显示信息加载算法
US11899733B2 (en) * 2020-01-14 2024-02-13 Google Llc Method and system for activity prediction, prefetching and preloading of computer assets by a client-device
CN111460004B (zh) * 2020-04-06 2023-04-14 北方工业大学 一种融合用户行为及Web页面依赖关系的数据挖掘方法
CN111639276A (zh) * 2020-04-23 2020-09-08 北京达佳互联信息技术有限公司 资源预加载方法、装置及存储介质
CN111562913B (zh) * 2020-04-28 2023-03-14 抖音视界有限公司 视图组件的预创建方法、装置、设备及计算机可读介质
CN112035766A (zh) * 2020-08-05 2020-12-04 北京三快在线科技有限公司 网页访问方法、装置、存储介质及电子设备
CN112138371A (zh) * 2020-09-15 2020-12-29 北京智明星通科技股份有限公司 基于关联访问次数的游戏场景加载方法、系统及服务器
CN113204726A (zh) * 2021-07-07 2021-08-03 苏州浪潮智能科技有限公司 一种bs架构页面响应时间优化方法、装置、设备及介质
CN113515713B (zh) * 2021-07-13 2024-04-09 中国工商银行股份有限公司 网页缓存策略生成方法及装置、网页缓存方法及装置
CN114118043A (zh) * 2021-11-17 2022-03-01 粤港澳国际供应链(广州)有限公司 一种动态生成pdf的方法
CN114428930A (zh) * 2022-01-26 2022-05-03 拉扎斯网络科技（上海）有限公司 基于h5页面的数据预加载方法、装置及电子设备
CN116776022A (zh) * 2023-06-28 2023-09-19 中国建设银行股份有限公司 请求响应方法、装置、设备及存储介质
CN117131304A (zh) * 2023-08-11 2023-11-28 北京无忧创想信息技术有限公司 一种网页资源加载方法、系统、电子设备及介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030061451A1 (en) * 2001-09-27 2003-03-27 Beyda William J. Method and system for web caching based on predictive usage
US6584498B2 (en) * 1996-09-13 2003-06-24 Planet Web, Inc. Dynamic preloading of web pages
CN1635734A (zh) * 2003-12-29 2005-07-06 北京中视联数字系统有限公司 一种数字电视数据广播系统利用缓存接收网页的方法
CN102033935A (zh) * 2010-12-20 2011-04-27 深圳市五巨科技有限公司 一种移动终端浏览器预加载的方法、装置和系统
CN102446222A (zh) * 2011-12-22 2012-05-09 华为技术有限公司 一种网页内容预加载方法、装置及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3764291B2 (ja) * 1999-03-02 2006-04-05 株式会社東芝 情報配信システム、移動計算機、情報サーバ装置、キャッシュサーバ装置及び先読みキャッシュ処理方法
JP2003228534A (ja) * 2001-11-30 2003-08-15 Ntt Docomo Inc 情報配信システム、記述データ配信装置、コンテンツ位置管理装置、データ変換装置、受信端末装置、情報配信方法
CN102222098A (zh) * 2011-06-20 2011-10-19 北京邮电大学 一种网页预取方法和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6584498B2 (en) * 1996-09-13 2003-06-24 Planet Web, Inc. Dynamic preloading of web pages
US20030061451A1 (en) * 2001-09-27 2003-03-27 Beyda William J. Method and system for web caching based on predictive usage
CN1635734A (zh) * 2003-12-29 2005-07-06 北京中视联数字系统有限公司 一种数字电视数据广播系统利用缓存接收网页的方法
CN102033935A (zh) * 2010-12-20 2011-04-27 深圳市五巨科技有限公司 一种移动终端浏览器预加载的方法、装置和系统
CN102446222A (zh) * 2011-12-22 2012-05-09 华为技术有限公司 一种网页内容预加载方法、装置及系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10169477B2 (en) 2013-12-30 2019-01-01 Samsung Electronics Co., Ltd. Method and system for rendering a web page free of inappropriate URLs
CN110855778A (zh) * 2019-11-13 2020-02-28 首都经济贸易大学 一种基于网络嗅探器的数据加载方法、装置和系统

Also Published As

Publication number Publication date
CN102446222A (zh) 2012-05-09
CN102446222B (zh) 2014-12-10

Similar Documents

Publication Publication Date Title
CN102446222B (zh) 一种网页内容预加载方法、装置及系统
US12212475B1 (en) Applying updated configuration dynamically to remote capture agents
US12204531B1 (en) Dynamically modifying remote capture agent event stream destinations
US10951474B2 (en) Configuring event stream generation in cloud-based computing environments
US9369520B2 (en) Enhancement of upload and/or download performance based on client and/or server feedback information
CN112486708B (zh) 页面操作数据的处理方法和处理系统
US10839038B2 (en) Generating configuration information for obtaining web resources
US20150295775A1 (en) Graphical configuration of event streams for network data capture and processing
CN105912587A (zh) 一种数据采集方法和系统
WO2008064593A1 (fr) Procédé et système d'analyse de journal basés sur un réseau de calcul distribué
WO2013163843A1 (fr) Procédé, dispositif et terminal de réalisation de signet graphique pour navigateur intégré
CN102523296B (zh) 无线网页浏览资源优化方法、装置及系统
Chen et al. Optimization research and application of enterprise website based on web service
CN112699021A (zh) 信息处理方法、装置、终端设备和服务器
CN111723324A (zh) 一种网站导航的更新方法、装置、计算机设备和存储介质
CN102694802B (zh) 网络访问信息记录方法和装置
WO2018077138A1 (fr) Procédé de configuration de données, procédé de gestion d'index, appareil associé et dispositif informatique
Liu et al. WRT: Constructing Users' Web Request Trees from HTTP Header Logs
US20130205015A1 (en) Method and Device for Analyzing Data Intercepted on an IP Network in order to Monitor the Activity of Users on a Website
CN105447077A (zh) 基于OpenFlow的查询词抽取方法及系统
CN115729925A (zh) 一种数据处理方法、装置、设备及存储介质
CN111736926A (zh) 在Java Web程序中低侵入式使用CDN加速服务的方法以及系统
Shen et al. Performance comparison of adaptation approaches for mobile information system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12860030

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12860030

Country of ref document: EP

Kind code of ref document: A1