Page caching methods, systems, devices, terminal equipment, servers, storage media, and program products

Abstract

This invention discloses a page caching method, system, apparatus, terminal device, server, storage medium, and program product. The method, configured on a client, includes: responding to a page access request by sending a page identifier of a first page to be accessed and an object identifier of a requesting object to access the first page to a target server; receiving an access probability returned by the target server for the page identifier and object identifier; and caching a second page if the access probability determines that a second page needs to be cached; wherein the access probability is the probability that a requesting object requests access to a second page through the first page, and the access probability is predicted based on the matching result between the page features associated with the first page and the object features of the requesting object. The technical solution of this invention, through an active page caching process, can improve page access speed.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of computer technology, and in particular to a page caching method, system, device, terminal equipment, server, storage medium and program product. Background Technology

[0002] With the continuous development of internet technology, there are more and more applications (APPs) that can be used on terminal devices. When a user requests access to a page of an APP, the ability to quickly open that page and allow the user to browse the page data is crucial for improving page access speed and reducing user waiting time.

[0003] Currently, many apps on the market use page caching solutions to optimize this experience.

[0004] In the process of realizing this invention, the inventors discovered the following technical problems in the prior art: the current page caching scheme cannot effectively improve page access speed, and urgently needs to be solved. Summary of the Invention

[0005] This invention provides a page caching method, system, device, terminal equipment, server, storage medium, and program product, which solves the problem of not being able to effectively improve page access speed.

[0006] According to one aspect of the present invention, a page caching method is provided, configured on a client, the method comprising:

[0007] In response to a page access request, the page identifier of the first page to be accessed and the object identifier of the request object to access the first page are sent to the target server.

[0008] Receive the access probability returned by the target server for the page identifier and object identifier, and cache the second page if it is determined that the second page needs to be cached based on the access probability;

[0009] The access probability is the probability that a requesting object accesses a second page through a request on the first page. The access probability is predicted based on the matching results between the page features associated with the first page and the object features of the requesting object.

[0010] According to another aspect of the present invention, a page caching method is provided, configured on a feature analysis server, the method comprising:

[0011] Receive the page features and object identifier sent by the target server, and obtain the object features of the request object represented by the object identifier. The page features are associated with the first page, which is the page that the request object requests to access through the client.

[0012] Based on the matching results between page features and object features, predict the probability of the requesting object accessing the second page through the first page request;

[0013] The access probability is returned to the client through the target server, so that the client can cache the second page if it determines that the second page needs to be cached based on the received access probability.

[0014] According to another aspect of the present invention, a page caching system is provided, which may include: a client, a target server, and a feature analysis server; wherein,

[0015] The client is used to respond to page access requests by sending the page identifier of the first page to be accessed and the object identifier of the request object to be accessed to the first page to the target server.

[0016] The target server receives the page identifier and the object identifier, and sends the page features corresponding to the page identifier and the object identifier to the feature analysis server. The page features are associated with the first page.

[0017] The feature analysis server is used to receive page features and object identifiers, and obtain the object features of the request object represented by the object identifier;

[0018] The feature analysis server is also used to predict the probability of a requesting object accessing the second page through the first page based on the matching results between page features and object features, and return the access probability to the target server.

[0019] The target server is also used to return the received access probability to the client;

[0020] The client is also used to cache the second page if it is determined that the second page needs to be cached based on the received access probability.

[0021] According to another aspect of the present invention, a page caching device is provided, configured on a client, the device comprising:

[0022] The object identifier sending module is used to respond to a page access request by sending the page identifier of the first page to be accessed and the object identifier of the request object to be accessed to the first page to the target server.

[0023] The page caching module is used to receive the access probability returned by the target server for the page identifier and the object identifier, and cache the second page if it is determined that the second page needs to be cached based on the access probability.

[0024] The access probability is the probability that a requesting object accesses a second page through a request on the first page. The access probability is predicted based on the matching results between the page features associated with the first page and the object features of the requesting object.

[0025] According to another aspect of the present invention, a page caching device is provided, configured on a feature analysis server, the device comprising:

[0026] The object feature acquisition module is used to receive page features and object identifiers sent by the target server, and obtain the object features of the request object represented by the object identifier. The page features are associated with the first page, which is the page that the request object accesses through the client request.

[0027] The access probability prediction module is used to predict the access probability of a requesting object accessing the second page through the first page, based on the matching results between page features and object features.

[0028] The access probability return module is used to return the access probability to the client through the target server, so that the client can cache the second page if it determines that the second page needs to be cached based on the received access probability.

[0029] According to another aspect of the present invention, a terminal device is provided, which may include:

[0030] At least one processor; and

[0031] A memory that is communicatively connected to at least one processor; wherein,

[0032] The memory stores a computer program that can be executed by at least one processor, such that when the at least one processor executes the program, it implements the page caching method provided in any embodiment of the present invention.

[0033] According to another aspect of the present invention, a feature analysis server is provided, which may include:

[0034] At least one processor; and

[0035] A memory that is communicatively connected to at least one processor; wherein,

[0036] The memory stores a computer program that can be executed by at least one processor, such that when the at least one processor executes the program, it implements the page caching method provided in any embodiment of the present invention.

[0037] According to another aspect of the present invention, a computer-readable storage medium is provided having computer instructions stored thereon for causing a processor to execute and implement the page caching method provided in any embodiment of the present invention.

[0038] According to another aspect of the present invention, a computer program product is provided, on which a computer program is stored, which, when executed by a processor, implements the page caching method provided in any embodiment of the present invention.

[0039] In this invention, the client, in response to a page access request, sends the page identifier of the requested first page and the object identifier of the requesting object to the target server. The target server then uses these two identifiers to determine the probability that the requesting object will access a second page via the first page. This access probability can be predicted based on the matching results between the page features associated with the first page and the object features of the requesting object. The application of page features and object features ensures the accuracy of the access probability prediction. The client receives the access probability returned by the target server for these two identifiers and, if it determines that the second page needs to be cached based on this probability, caches the second page. This proactive page caching scheme significantly improves page access speed when the requesting object requests access to a page (i.e., the first page).

[0040] It should be understood that the description in this section is not intended to identify key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0041] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 This is a flowchart of a page caching method provided according to an embodiment of the present invention;

[0043] Figure 2This is a schematic diagram of the probability prediction result in a page caching method provided according to an embodiment of the present invention;

[0044] Figure 3 This is a flowchart of another page caching method provided according to an embodiment of the present invention;

[0045] Figure 4 This is a schematic diagram of the object feature analysis process in another page caching method provided according to an embodiment of the present invention;

[0046] Figure 5 This is a structural block diagram of a page caching system provided according to an embodiment of the present invention;

[0047] Figure 6a This is a schematic diagram of an optional example of a page caching system provided according to an embodiment of the present invention;

[0048] Figure 6b This is a flowchart of an optional example of a page caching system provided according to an embodiment of the present invention;

[0049] Figure 7 This is a structural block diagram of a page caching device according to an embodiment of the present invention;

[0050] Figure 8 This is a structural block diagram of another page caching device provided according to an embodiment of the present invention;

[0051] Figure 9 This is a schematic diagram of the structure of a terminal device or feature analysis server that implements the page caching method of this invention. Detailed Implementation

[0052] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0053] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. The same applies to "target," "original," etc., and will not be repeated here. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0054] It should be noted that the collection, use, storage, sharing, and transfer of user personal information involved in the technical solution of this invention all comply with the provisions of relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Furthermore, it is necessary to inform the user and obtain their consent or authorization. Where applicable, user personal information has undergone de-identification and / or anonymization and / or encryption technical processing.

[0055] Before introducing the embodiments of the present invention, we will first provide an exemplary explanation of the reasons why the currently used page caching schemes cannot effectively improve page access speed, so as to better understand why the page caching scheme proposed in the embodiments of the present invention can improve page access speed.

[0056] For example, a current page caching solution involves caching the page previously requested by the user locally. This allows the page data to be retrieved directly from the cache and displayed when the user requests the page again. This is a passive page caching solution.

[0057] However, in cases where the user is currently accessing a page that has not been accessed before, has been accessed before but the parameters used in the previous access are different from those used in the current access, or has expired due to the user accessing it a long time ago, the corresponding page data cannot be retrieved from the cache. This results in the need to request page data again from the data source server, thus affecting the page access speed.

[0058] To address this, this invention proposes a page caching scheme that proactively caches pages. When a user requests access to a page, this scheme proactively caches pages that the user might subsequently access. This allows the user to directly retrieve the corresponding page data from the cache and display the page when they later access those potentially accessible pages, thereby improving page access speed. The page caching scheme will be described in detail below.

[0059] Figure 1 This is a flowchart of a page caching method provided in an embodiment of the present invention. This embodiment is applicable to page caching, especially to proactive page caching, and particularly suitable for proactively caching pages that the requesting object may further access through that page when it requests access to that page. This method can be executed by the page caching device provided in this embodiment of the present invention, which can be implemented in software and / or hardware, and can be configured on the client (consumer, C) side.

[0060] The client can be understood as a program that the requesting object can directly use and interact with. In this embodiment of the invention, the program may optionally be an APP, a mini-program, or a Web H5, which depends on the actual situation and is not specifically limited here. The client can be integrated into the terminal device.

[0061] The target server communicating with the client can be understood as the server that returns the access probability to the client. In this embodiment of the invention, optionally, the target server can be modified based on the data source server that provides page data. This helps to achieve the joint request of access probability and page data, and further reduce the number of network requests. Of course, the target server can also be an independently designed server, which can be set according to actual needs and is not specifically limited here.

[0062] The aforementioned data source server can integrate various data sources, such as data sources that provide page data for the homepage and data sources that provide product data for product detail pages.

[0063] See Figure 1 The method of this invention specifically includes the following steps:

[0064] S110. In response to the page access request, send the page identifier of the first page to be accessed and the object identifier of the request object to be accessed to the first page to the target server.

[0065] Here, a page access request can be understood as a request triggered by the client to access the first page in the client. In response to the page access request, the object identifier of the request object and the page identifier of the first page are obtained, and all the obtained identifiers are sent to the target server.

[0066] S120. Receive the access probability returned by the target server for the page identifier and the object identifier, and cache the second page if it is determined that the second page needs to be cached based on the access probability.

[0067] The access probability is the probability that a requesting object accesses a second page through a request on the first page. The access probability is predicted based on the matching results between the page features associated with the first page and the object features of the requesting object.

[0068] The second page can be understood as a page accessible to the requesting object through the first page. This second page may be a different page from the first page; for example, the requesting object might jump to another page by triggering a link on the first page. In this case, the first page can be called the current page, and the second page can be called the next page after the current page. Alternatively, they may be the same page; for example, the requesting object might swipe through the first page to browse more page data. In this case, the page containing the page data before swiping is called the first page, and the page containing the page data after swiping is called the second page. However, at the underlying implementation, the first page and the second page can be the same page, that is, they present different page data within the same page. The specific number of second pages is not specified here. The number of second pages can be one, two, or more, depending on the actual situation, and is not specifically limited here.

[0069] For each of the all second pages, the access probability of that second page can be understood as the probability that the requesting object accesses that second page through the first page. For example, taking the homepage as the first page, see [link to relevant documentation]. Figure 2 The homepage shown has a first column and a second column. It is predicted that the probability of the requesting object clicking on the first column is 10% and the probability of clicking on the second column is 20%. In addition, it is predicted that the probability of the requesting object scrolling up the homepage is 15%. This means that the probability of the requesting object requesting to access the second page 1 represented by the first column is 10%, the probability of requesting to access the second page 2 represented by the second column is 20%, and the probability of requesting to access the second page 3, which is the same page as the homepage, is 15%.

[0070] Page features can be understood as features associated with the first page. In this embodiment of the invention, optionally, the page features can be obtained by performing feature analysis on at least one of the first page data in the first page, page data associated with the first page data, second page data in the second page, and page data associated with the second page data, without specific limitations.

[0071] Object characteristics can be understood as the characteristics of the request object. In this embodiment of the invention, optionally, the object characteristics can be obtained by performing feature analysis on the attribute information of the request object; in particular, they can be obtained by performing feature analysis on the interaction data between the request object and the client, which can be offline interaction data and / or real-time interaction data, etc.; of course, they can also be obtained by other means, which are not specifically limited here.

[0072] After receiving the page identifier and object identifier, the target server can return the access probability obtained from these two identifiers to the client. This access probability can be predicted based on the matching results between page features and object features. This prediction process can be implemented using a prediction model, which can be at least one of the following: linear regression model, logistic regression model, decision tree and random forest, support vector machine, cluster analysis, time series model, Bayesian network, neural network model, and large language model, etc., without specific limitations. This prediction process can be implemented on the target server or on a server other than the target server, such as on a feature analysis server, without specific limitations.

[0073] Furthermore, the client determines whether to cache the second page corresponding to the access probability returned by the target server. For example, the client can determine whether to cache the second page based on the numerical relationship between the access probability and a preset access probability threshold. If so, the second page is cached so that when the requesting object requests access to the second page later, it can directly retrieve the second page from the cache and display the page, thereby improving the page access speed of the second page.

[0074] In this invention, the client, in response to a page access request, sends the page identifier of the requested first page and the object identifier of the requesting object to the target server. The target server then uses these two identifiers to determine the probability that the requesting object will access a second page via the first page. This access probability can be predicted based on the matching results between the page features associated with the first page and the object features of the requesting object. The application of page features and object features ensures the accuracy of the access probability prediction. The client receives the access probability returned by the target server for these two identifiers and, if it determines that the second page needs to be cached based on this probability, caches the second page. This proactive page caching scheme significantly improves page access speed when the requesting object requests access to a page (i.e., the first page).

[0075] An optional technical solution, the above page caching method, further includes:

[0076] Obtain the caching strategy for the adapted page that matches the client;

[0077] Accordingly, the page identifier of the first page requested for access and the object identifier of the request object for accessing the first page are sent to the target server, including:

[0078] If the page access information associated with the page access request meets the page caching strategy, the page identifier of the first page to be accessed and the object identifier of the request object to access the first page will be sent to the target server.

[0079] The adapted page caching strategy can be understood as a strategy adapted to the client to determine whether to cache the page associated with the first page currently being requested. Based on this, and considering the application scenarios that may be involved in the embodiments of this invention, the adapted page caching strategy can represent at least one of page access time interval, page access frequency, and a page cache list, where the pages represented by the page cache list can be understood as pages that can be actively cached.

[0080] Page access information can be understood as information that characterizes page access status, and more specifically, information related to page access requests that characterize page access status. Based on this, and referring to the example of the adapted page caching strategy given above, the page access information may, for example, include at least one of the following: the time interval between a page access request and the previous access request; the number of page access requests occurring within a preset time period (e.g., 1 minute) corresponding to the page access request; the page identifier corresponding to the page access request; etc., without specific limitations here.

[0081] To determine whether the page access information meets the page caching adaptation strategy, continuing with the above example, for instance, if the time interval is greater than the page access time interval, the number of accesses is less than the page access frequency, and the page identifier is in at least one of the page cache lists, it can be determined that the page access information meets the page caching adaptation strategy. This means that the page associated with the first page can be cached. Then, the two identifiers are sent to the target server to perform subsequent operations.

[0082] Compared to caching every first page requested, the above solution only caches the first page that is suitable for caching, thereby improving page access speed while saving computing resources.

[0083] In addition to this, the above page caching methods may optionally include:

[0084] Send the policy filtering information associated with the client to the policy server;

[0085] Obtain the caching strategy for the adapted page that is compatible with the client, including:

[0086] Get the adapted page caching strategy returned by the strategy server. The adapted page caching strategy is a pre-configured page caching strategy that is adapted to the client, which is selected by the strategy server from at least one pre-configured page caching strategy based on the strategy filtering information.

[0087] The pre-configured page caching strategy can be understood as a strategy that is pre-configured in the strategy server and can instruct page X. The number of such strategies can be one or more, depending on the actual situation, and no specific limit is made here. Page X can be understood as a page that can be cached.

[0088] Policy filtering information can be understood as information used to filter one or more pre-configured page caching policies, and more specifically, as information associated with the client to filter out the appropriate page caching policy from the one or more pre-configured page caching policies.

[0089] The client sends policy filtering information to the policy server, especially after the client starts up. The policy server can then select the appropriate page caching policy from the pre-configured page caching policies based on the policy filtering information and return it to the client application.

[0090] For example, policy filtering information may include the number of page access requests that the data source server communicating with the client can handle, as well as the traffic consumption of the requested object under different network conditions. This allows the policy server to return the page access time interval to the client accordingly.

[0091] For example, policy filtering information may include the request object's interaction habits with the client, allowing the policy server to return page access frequency to the client based on this. When the request object frequently switches pages, the uncertainty is high; page access frequency can be used to suppress inaccurate proactive caching processes.

[0092] For example, policy filtering information may include the device information of the terminal device (such as storage and network conditions), which allows the policy server to return the corresponding adapted page caching policy.

[0093] For another example, the strategy server can return the code information of the code that needs to be preloaded in different active caching scenarios to the client, thereby improving page loading speed.

[0094] In the above technical solution, the client calls the strategy server, which then selects the appropriate page caching strategy from the various pre-configured page caching strategies and returns it to the client. This ensures that the client can apply the appropriate page caching strategy, thereby guaranteeing the effective implementation of page caching.

[0095] Another alternative technical solution is to integrate the client on the terminal device, and the target server is a data source server that can provide the data for the second page in the second page;

[0096] Cache the second page, including:

[0097] By loading the code related to the second page stored on the terminal device, the second page is preheated to achieve caching of the second page; and / or,

[0098] The system requests data from the data source server for the second page and preloads the requested data onto the terminal device to achieve caching of the second page.

[0099] Page caching can be manifested in two aspects: page warm-up and page data preloading.

[0100] Specifically, for page preheating, the client loads the code related to the second page stored on the terminal device. For example, the code can be extracted from the terminal device's hard drive and loaded into memory. Then, the code is executed in memory via the Central Processing Unit (CPU), thereby achieving page preheating and improving the page loading speed during the page access process.

[0101] To preload page data, the client can request second page data from the data source server and preload the requested second page data onto the terminal device, thereby achieving page data preloading.

[0102] In this way, during the access process of the second page, since the second page has been preheated, it can be loaded (i.e. opened) quickly, and since the data of the second page has been preloaded, the data of the second page can be rendered quickly in the opened second page, so that the requesting object can quickly access the second page.

[0103] The above technical solution achieves effective caching of the second page by preheating the second page and / or preloading the data of the second page.

[0104] Another alternative technical solution is to integrate the client on the terminal device, and the target server is a data source server that can provide the data of the first page in the first page;

[0105] The above page caching methods also include:

[0106] If the first page data is cached on the terminal device, retrieve the first page data from the terminal device and display the first page based on the first page data; and / or,

[0107] If the first page data is not cached on the terminal device, request the first page data from the data source server and display the first page based on the requested first page data.

[0108] In this process, the client, upon receiving a page access request for the first page, can determine whether the first page data is cached on the terminal device. Optionally, it can also determine whether the cached first page data is valid. If so, the first page data can be directly retrieved from the terminal device, which has been pre-cached using either an active or passive page caching scheme. Otherwise, a network request can be initiated to the data source server to retrieve the first page data. Furthermore, based on the retrieved first page data, the first page is displayed.

[0109] The above technical solution obtains the first page data in different ways under different circumstances, thereby enabling the requesting object to effectively access the first page.

[0110] Figure 3 This is a flowchart of another page caching method provided in this embodiment of the invention. This embodiment is applicable to page caching, especially to proactive page caching, and particularly suitable for proactively caching pages that the requesting object may further access through that page when it requests access to that page. This method can be executed by the page caching device provided in this embodiment of the invention, which can be implemented in software and / or hardware, and can be integrated into a feature analysis server. The explanations of terms that are the same as or corresponding to those in the above embodiments are not repeated here.

[0111] See Figure 3 The method in this embodiment may specifically include the following steps:

[0112] S210. Receive the page features and object identifier sent by the target server, and obtain the object features of the requested object represented by the object identifier. The page features are associated with the first page, which is the page requested by the requested object through the client.

[0113] After receiving the page identifier and object identifier sent by the client, the target server can obtain the page features associated with the first page represented by the page identifier. In practical applications, the page features can optionally be obtained by the target server in real time or in advance, or can be obtained in advance by other servers besides the target server and then sent to the target server; etc., without specific limitations.

[0114] After receiving the page features and object identifier sent by the target server, the feature analysis server can obtain the object features of the request object represented by the object identifier. These object features can be obtained by the feature analysis server in advance or in real time, which can be set according to actual needs and is not specifically limited here.

[0115] S220. Based on the matching results between page features and object features, predict the probability that the requesting object will access the second page through the first page request.

[0116] S230. The access probability is returned to the client through the target server, so that the client can cache the second page if it determines that the second page needs to be cached based on the received access probability.

[0117] The technical solution of this invention can significantly improve page access speed through active page caching.

[0118] An optional technical solution involves obtaining the object characteristics of the request object represented by the object identifier, including:

[0119] Retrieve the interaction data between the request object represented by the object identifier and the client;

[0120] Based on the interaction data, the object characteristics of the requested object are obtained.

[0121] Interaction data can be understood as data generated by the requesting object during its interaction with the client. This data may include, for example, trigger data of the requesting object on certain controls on the client and / or browsing data of certain pages on the client. This browsing data can be represented by swipe data and / or dwell data, which depends on the actual situation and is not specifically limited here.

[0122] Based on this, and considering the application scenarios that may be involved in the embodiments of the present invention, optionally, the interaction data can be offline interaction data, which can be understood as interaction data generated before the time period in which the page access request is triggered; the interaction data can also be real-time interaction data, which can be understood as interaction data generated within that time period.

[0123] The feature analysis server acquires interaction data and performs feature analysis on this data to obtain object features. In this technical solution, this feature analysis process can be implemented using a model.

[0124] The above technical solution, since the interaction data can characterize the interaction process between the requesting object and the client, the object features obtained by using the interaction data can characterize the interaction tendency of the requesting object towards the client. Based on this, since the first page is a page in the client, the object features can be used to accurately analyze the probability of the requesting object accessing the second page that can be accessed through the first page.

[0125] Based on this, optionally, the interaction data includes real-time interaction data. Based on the interaction data, the object characteristics of the requested object are obtained, including:

[0126] The offline interaction features are obtained by performing feature analysis on the offline interaction data between the request object and the client.

[0127] Perform feature analysis on real-time interactive data to obtain real-time interactive features;

[0128] Based on offline and real-time interaction characteristics, the object characteristics of the requested object are obtained.

[0129] Since offline interaction data can be obtained in advance, feature analysis can be performed on the offline interaction data in advance to obtain offline interaction features, which can then be directly obtained during the object feature analysis process.

[0130] Since real-time interactive data is acquired in real time, it can be used to perform feature analysis during object feature analysis to obtain real-time interactive features.

[0131] Furthermore, considering that offline interaction features characterize the historical interaction tendencies of the requesting object towards the client, while real-time interaction features characterize the current interaction tendencies of the requesting object towards the client, combining offline and real-time interaction features improves the accuracy of object feature analysis.

[0132] To better understand this technical solution, specific examples are provided below. For examples, see [link to example]. Figure 4 Big data servers can be used to store interaction data between request objects and clients. Specifically, they can provide the ability to provide real-time notification feature analysis of server interaction data and store it in a database.

[0133] Specifically, the client (i.e., the C-end) can report the interaction data between itself and the requesting object to the big data server. The big data server can consume the interaction data in two ways: one is to record it in the database for later use as offline interaction data; the other is to send it to the feature analysis server in the form of a message so that the feature analysis server can obtain the real-time interaction data.

[0134] Based on this, the feature analysis server extracts offline interaction data from the database prior to today at regular intervals each day, and performs offline feature analysis using a model to obtain offline interaction features. Afterwards, the real-time interaction data of the requesting object is notified via messages. At this point, object features can be generated by combining preset recommendation algorithms, models pre-trained based on offline interaction data, and large language models for subsequent predictions.

[0135] Another alternative technical solution is that the target server is a data source server used to provide page data, and the page data includes at least the first page data in the first page and the second page data in the second page;

[0136] Page features are obtained through pre-analysis in the following manner:

[0137] Determine the page type of the first page, and based on the page type, read feature analysis data from the page data;

[0138] Perform feature analysis on the feature analysis data to obtain page features;

[0139] After obtaining the page characteristics, the above page caching method also includes:

[0140] The page features are returned to the data source server so that the page features can be associated with the first page on the data source server.

[0141] The page data provided by the data source server includes at least the first page data and the second page data. Optionally, it may also include page data associated with the first page data and / or page data associated with the second page data, etc., without specific limitations.

[0142] The page type can characterize the type of the first page. Based on this, and in combination with the application scenarios that may be involved in the embodiments of the present invention, the type may be, for example, homepage service, category service, product details service, activity page service, recipe service, video service, or review service, etc., without specific limitations.

[0143] It should be noted that pages of different types have their own characteristics. Therefore, to ensure the accuracy of page feature analysis and thus the accuracy of access probability prediction, the feature analysis server can interface with the data source server. Specifically, it can interface with various data sources integrated into the data source server. This allows feature analysis data to be read from the page data provided by the data source server based on the page type. This feature analysis data can be understood as data applicable to feature analysis of pages of that specific page type. Then, feature analysis is performed on this data, for example, using a model to obtain page features. Optionally, in this technical solution, the page features can be represented based on a set of feature values, where each feature value corresponds one-to-one with each of the second pages corresponding to the first page.

[0144] Furthermore, the feature analysis server can return the analyzed page features to the data source server, whereby the data source server associates the page features with the first page. In this way, upon receiving the page identifier of the first page from the client, the data source server can obtain the page features corresponding to that page identifier and send these page features to the feature analysis server for predicting the access probability.

[0145] Based on this, to provide a more vivid understanding of the page feature analysis process in this technical solution, several specific examples are given here for illustrative purposes. Examples:

[0146] For the homepage service, the feature analysis server connects with the data source responsible for building and operating the homepage. For each section on the homepage, it can analyze the section data and continue to explore the data source of the next level page of the section to analyze the page data of the corresponding page. Based on this data, the section features of the section can be generated, and thus the page features of the homepage can be obtained based on the features of each section.

[0147] For classification services, the feature analysis server can connect with the data source responsible for providing classification data to generate category features for the corresponding categories by analyzing product data under different categories.

[0148] For product detail page services, we can explore the product characteristics displayed on the product detail page.

[0149] For event page services, event page data, such as products, videos, and images, can be probed, and page characteristics can be summarized through analysis of this event page data.

[0150] For recipe services, data from recipe pages can be probed and combined with related products to analyze page characteristics.

[0151] For video services, video content can be analyzed, and video characteristics can be summarized by combining related product activities and other information.

[0152] For the product review service, the published content can be analyzed, and relevant characteristics can be summarized through related products.

[0153] The above technical solution allows the feature analysis server to connect to the data source server and, based on the page type, read feature analysis data from the page data provided by the data source server that is suitable for analyzing page features associated with that page type, thereby ensuring the accuracy of page feature analysis.

[0154] Figure 5 This is a structural block diagram of a page caching system provided in an embodiment of the present invention. This embodiment is applicable to page caching, especially to proactive page caching, and particularly suitable for proactively caching pages that the requesting object may further access through that page when it requests access to that page.

[0155] See Figure 5 The page caching system described in this embodiment of the invention may include: a client 310, a target server 320, and a feature analysis server 330; wherein,

[0156] Client 310 can respond to a page access request by sending the page identifier of the first page to be accessed and the object identifier of the request object to be accessed to the first page to the target server 320.

[0157] The target server 320 can receive page identifiers and object identifiers, and send the page features corresponding to the page identifiers and the object identifiers to the feature analysis server 330, wherein the page features are associated with the first page;

[0158] The feature analysis server 330 is used to receive page features and object identifiers, and obtain the object features of the request object represented by the object identifier;

[0159] The feature analysis server 330 can also be used to predict the access probability of a requesting object accessing the second page through the first page based on the matching results between page features and object features, and return the access probability to the target server 320.

[0160] The target server 320 can also be used to return the received access probability to the client 310;

[0161] Client 310 can also be used to cache the second page if it is determined that the second page needs to be cached based on the received access probability.

[0162] The technical solution of this invention can significantly improve page access speed through active page caching.

[0163] To better understand the various technical solutions described above, specific examples are provided below. For examples, see [link to example]. Figure 6a The page caching system shown includes: C-end, big data server, data source server, feature analysis server, and strategy server.

[0164] In this process, the client (C-end) transmits the interaction data generated by the interaction between the requested object and itself to the big data server. The feature analysis server analyzes the object characteristics of the requested object using real-time and offline interaction data from the big data server. The data source server provides page data to the client, while the feature analysis server also reads page data from the data source server, performs page feature analysis, and feeds back the analyzed page features to the data source server so that the corresponding page is marked with those features. Simultaneously, the feature analysis server can provide the previously analyzed object features to the strategy server, allowing the strategy server to combine various pre-configured page caching strategies with the real-time analyzed object features sent to the client by the feature analysis server to issue an adapted page caching strategy, guiding the client to cache pages.

[0165] For another example, since the client (C-end) has already obtained the adapted page caching strategy from the strategy server during startup, when the requesting object accesses a page (taking the first page as an example here) through the client, it can trigger the following: Figure 6b The page caching process shown is as follows:

[0166] When a requesting object requests access to the first page, it first determines whether the first page is in the page cache list issued by the policy server.

[0167] If the first page data is not available, there's no need to call the data source server for page feature queries or the feature analysis server for access probability prediction when requesting the first page data. In this case, the data source server directly returns the first page data, which the client-side can then render. This concludes the page access.

[0168] If it's in the page cache manifest, it means we need to call the data source server to query page features and the feature analysis server to predict access probability. Further, check the page access time interval and page access frequency issued by the strategy server to determine if they are satisfied.

[0169] If the conditions are not met, it indicates that the requesting object is accessing the page at a high frequency, indicating strong uncertainty. Therefore, initiating another prediction is not allowed at this time. Figure 6b Simply follow the steps. This page visit is now complete.

[0170] If the conditions are met, it indicates that the requesting object is accessing the page infrequently and may be deciding on the next page. Therefore, initiating the next prediction is permitted, and the first page data is requested, informing the data source server that a prediction is needed. Specifically, while querying the first page data, the data source server also calls the feature analysis server based on the page features associated with the first page and the object identifier. Then, the feature analysis server uses the page features and the object features corresponding to the object identifier to perform model processing, predicting the probability of the requesting object accessing each second page corresponding to the first page. Finally, the feature analysis server returns each access probability to the C-end through the data source server.

[0171] The client (C-side) compares each access probability with the access probability threshold issued by the policy server to obtain a list of second pages. The second pages in this list are the ones that need to be cached from all the second pages. Here, we take... Figure 2Taking a 15% access probability threshold as an example, the second page 1 corresponding to the second category and the second page 2 obtained by swiping up the first page need to be cached. The client-side can pre-load the second page 1 and its second page data 1 by loading code, thus achieving caching of the second page 1. Similarly, the client-side can pre-load the second page data 2, thus achieving caching of the second page 2. This example involves three application scenarios: automatically loading more page data on the same page, pre-loading code used for the next page on the current page (i.e., the first page), and pre-loading page data for the next page on the current page. All of these can help the requesting object browse subsequent page rendering faster and more smoothly, thereby improving page access speed.

[0172] Figure 7 This is a structural block diagram of a page caching device provided in an embodiment of the present invention. This device is used to execute the page caching method provided in any of the above embodiments. This device and the page caching methods of the above embodiments belong to the same inventive concept. Details not described in detail in the embodiments of the page caching device can be found in the embodiments of the page caching methods described above. See also... Figure 7 The device is configured on the client and may specifically include: an object identifier sending module 410 and a page caching module 420.

[0173] The object identifier sending module 410 is used to respond to a page access request by sending the page identifier of the first page to be accessed and the object identifier of the request object to be accessed to the first page to the target server.

[0174] The page caching module 420 is used to receive the access probability returned by the target server for the page identifier and the object identifier, and cache the second page if it is determined that the second page needs to be cached based on the access probability.

[0175] The access probability is the probability that a requesting object accesses a second page through a request on the first page. The access probability is predicted based on the matching results between the page features associated with the first page and the object features of the requesting object.

[0176] Optionally, the above-mentioned page caching device may further include:

[0177] The adaptation page caching strategy acquisition module is used to obtain the adaptation page caching strategy that is compatible with the client.

[0178] The object identifier sending module 410 includes:

[0179] The object identifier sending unit is used to send the page identifier of the first page to be accessed and the object identifier of the request object to be accessed to the target server, provided that the page access information associated with the page access request meets the page caching strategy.

[0180] In addition, optionally, the above-mentioned page caching device may further include:

[0181] The policy filtering information sending module is used to send the policy filtering information associated with the client to the policy server;

[0182] The module for adapting page caching strategies is specifically used for:

[0183] Get the adapted page caching strategy returned by the strategy server. The adapted page caching strategy is a pre-configured page caching strategy that is adapted to the client, which is selected by the strategy server from at least one pre-configured page caching strategy based on the strategy filtering information.

[0184] Optionally, the client is integrated on the terminal device, and the target server is a data source server that can provide the data for the second page in the second page;

[0185] Page caching module 420 may include:

[0186] The first page caching unit is used to preheat the second page by loading the code related to the second page stored on the terminal device, thereby achieving caching of the second page; and / or,

[0187] The second page caching unit is used to request second page data from the data source server and preload the requested second page data onto the terminal device to achieve caching of the second page.

[0188] Optionally, the client is integrated on the terminal device, and the target server is a data source server that can provide the data for the first page in the first page; the aforementioned page caching device may further include:

[0189] The first page display module is used to retrieve the first page data from the terminal device when the first page data is cached on the terminal device, and to display the first page based on the first page data; and / or,

[0190] The second page display module is used to request the first page data from the data source server when the first page data is not cached on the terminal device, and to display the first page based on the requested first page data.

[0191] The page caching device provided in this embodiment of the invention can improve page access speed through the cooperation of various modules.

[0192] The page caching device provided in the embodiments of the present invention can execute the page caching method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0193] It is worth noting that in the embodiments of the above-mentioned page caching device, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of the present invention.

[0194] Figure 8 This is a structural block diagram of a page caching device provided in an embodiment of the present invention. This device is used to execute the page caching method provided in any of the above embodiments. This device and the page caching methods of the above embodiments belong to the same inventive concept. Details not described in detail in the embodiments of the page caching device can be found in the embodiments of the page caching methods described above. See also... Figure 8 The device is configured on a feature analysis server and may specifically include: an object feature acquisition module 510, an access probability prediction module 520, and an access probability return module 530.

[0195] The object feature acquisition module 510 is used to receive page features and object identifiers sent by the target server, and obtain the object features of the request object represented by the object identifier. The page features are associated with the first page, which is the page that the request object requests to access through the client.

[0196] The access probability prediction module 520 is used to predict the access probability of a requesting object accessing the second page through the first page based on the matching results between page features and object features.

[0197] The access probability return module 530 is used to return the access probability to the client through the target server, so that the client can cache the second page if it determines that the second page needs to be cached based on the received access probability.

[0198] Optionally, the object feature acquisition module 510 may include:

[0199] The interactive data acquisition unit is used to acquire the interactive data between the request object represented by the object identifier and the client.

[0200] The object feature acquisition unit is used to obtain the object features of the requested object based on the interaction data.

[0201] Based on this, optionally, the interactive data includes real-time interactive data, and the object feature is obtained as a unit, specifically used for:

[0202] The offline interaction features are obtained by performing feature analysis on the offline interaction data between the request object and the client.

[0203] Perform feature analysis on real-time interactive data to obtain real-time interactive features;

[0204] Based on offline and real-time interaction characteristics, the object characteristics of the requested object are obtained.

[0205] Optionally, the target server is a data source server used to provide page data, and the page data includes at least the first page data in the first page and the second page data in the second page;

[0206] Page features are obtained through pre-analysis using the following modules:

[0207] The feature analysis data reading module is used to determine the page type of the first page and read feature analysis data from the page data according to the page type.

[0208] The page feature acquisition module is used to perform feature analysis on feature analysis data to obtain page features;

[0209] The aforementioned page caching device may further include:

[0210] The page feature association module is used to return the page features to the data source server after obtaining the page features, so that the page features can be associated with the first page on the data source server.

[0211] The page caching device provided in this embodiment of the invention can improve page access speed through the cooperation of various modules.

[0212] The page caching device provided in the embodiments of the present invention can execute the page caching method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0213] It is worth noting that in the embodiments of the above-mentioned page caching device, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of the present invention.

[0214] Figure 9A schematic diagram of a terminal device or feature analysis server (hereinafter collectively referred to as electronic device) 10 that can be used to implement embodiments of the present invention is shown. Electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. Electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0215] like Figure 9 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded into the RAM 13 from storage unit 18. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0216] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0217] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as page caching methods.

[0218] In some embodiments, the page caching method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or mounted on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the page caching method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the page caching method by any other suitable means (e.g., by means of firmware).

[0219] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0220] Computer programs used to implement the methods of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer programs can be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0221] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0222] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0223] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0224] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0225] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0226] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A page caching method, characterized in that, Applied to a client, the method includes: In response to a page access request, the page identifier of the first page to be accessed and the object identifier of the request object to access the first page are sent to the target server. Receive the access probability returned by the target server for the page identifier and the object identifier, and cache the second page if it is determined that the second page needs to be cached based on the access probability; The access probability is the probability that the requesting object requests access to the second page through the first page. The access probability is predicted based on the matching result between the page features associated with the first page and the object features of the requesting object.

2. The method according to claim 1, characterized in that, Also includes: Obtain the page caching strategy adapted to the client; Sending the page identifier of the first page to be accessed and the object identifier of the request object to access the first page to the target server includes: If the page access information associated with the page access request satisfies the adapted page caching strategy, the page identifier of the first page to be accessed and the object identifier of the request object to access the first page are sent to the target server.

3. The method according to claim 2, characterized in that, Also includes: The policy filtering information associated with the client is sent to the policy server; The step of obtaining the adaptation page caching strategy adapted to the client includes: Obtain the adapted page caching strategy returned by the strategy server, wherein the adapted page caching strategy is a pre-configured page caching strategy that is adapted to the client, selected by the strategy server from at least one pre-configured page caching strategy according to the strategy filtering information.

4. The method according to claim 1, characterized in that, The client is integrated on the terminal device, and the target server is a data source server that can provide the data of the second page in the second page. The caching of the second page includes: By loading the code related to the second page stored on the terminal device, the second page is preheated to achieve caching of the second page; And / or, The system requests the second page data from the data source server and preloads the requested second page data onto the terminal device to achieve caching of the second page.

5. The method according to claim 1, characterized in that, The client is integrated on the terminal device, and the target server is a data source server that can provide the data of the first page in the first page. The method further includes: If the first page data is cached on the terminal device, the first page data is retrieved from the terminal device, and the first page is displayed based on the first page data; and / or, If the first page data is not cached on the terminal device, the first page data is requested from the data source server, and the first page is displayed based on the requested first page data.

6. A page caching method, characterized in that, The method, applied to a feature analysis server, includes: Receive page features and object identifiers sent by the target server, and obtain the object features of the request object represented by the object identifier, wherein the page features are associated with a first page, which is the page that the request object requests to access through the client. Based on the matching results between the page features and the object features, the probability of the requesting object accessing the second page through the first page is predicted; The access probability is returned to the client through the target server, so that the client can cache the second page if it determines that the second page needs to be cached based on the received access probability.

7. The method according to claim 6, characterized in that, The process of obtaining the object characteristics of the request object represented by the object identifier includes: Obtain the interaction data between the request object represented by the object identifier and the client; Based on the interaction data, the object characteristics of the requested object are obtained.

8. The method according to claim 7, characterized in that, The interaction data includes real-time interaction data, and obtaining the object characteristics of the requested object based on the interaction data includes: Obtain offline interaction features, wherein the offline interaction features are obtained by performing feature analysis on the offline interaction data between the request object and the client; The real-time interaction data is subjected to feature analysis to obtain real-time interaction features; Based on the offline interaction characteristics and the real-time interaction characteristics, the object characteristics of the requested object are obtained.

9. The method according to claim 6, characterized in that, The target server is a data source server for providing page data, and the page data includes at least the first page data in the first page and the second page data in the second page; The page features are obtained in advance through the following analysis: Determine the page type of the first page, and read feature analysis data from the page data based on the page type; The page features are obtained by performing feature analysis on the feature analysis data; After obtaining the page features, the method further includes: The page features are returned to the data source server so that the page features are associated with the first page on the data source server.

10. A page caching system, characterized in that, include: Client, target server, and feature analysis server; among them, The client is configured to respond to a page access request by sending the page identifier of the first page to be accessed and the object identifier of the request object to access the first page to the target server. The target server is configured to receive the page identifier and the object identifier, and send the page feature corresponding to the page identifier and the object identifier to the feature analysis server, wherein the page feature is associated with the first page; The feature analysis server is used to receive the page features and the object identifier, and obtain the object features of the request object represented by the object identifier; The feature analysis server is also used to predict the access probability of the requesting object accessing the second page through the first page based on the matching result between the page features and the object features, and return the access probability to the target server. The target server is also used to return the received access probability to the client; The client is also configured to cache the second page if it is determined, based on the received access probability, that the second page needs to be cached.

11. A page caching device, characterized in that, Configured on a client, the device includes: The object identifier sending module is used to respond to a page access request by sending the page identifier of the first page to be accessed and the object identifier of the request object to be accessed to the first page to the target server. The page caching module is used to receive the access probability returned by the target server for the page identifier and the object identifier, and cache the second page if it is determined that the second page needs to be cached based on the access probability; The access probability is the probability that the requesting object requests access to the second page through the first page. The access probability is predicted based on the matching result between the page features associated with the first page and the object features of the requesting object.

12. A page caching device, characterized in that, Configured on the feature analysis server, the device includes: The object feature acquisition module is used to receive page features and object identifiers sent by the target server, and obtain the object features of the request object represented by the object identifier, wherein the page features are associated with a first page, which is the page that the request object requests to access through the client. The access probability prediction module is used to predict the access probability of the requesting object accessing the second page through the first page based on the matching result between the page features and the object features. An access probability return module is used to return the access probability to the client through the target server, so that the client can cache the second page if it determines that the second page needs to be cached based on the received access probability.

13. A terminal device, characterized in that, include: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to cause the at least one processor to perform the page caching method as described in any one of claims 1-5.

14. A feature analysis server, characterized in that, include: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to cause the at least one processor to perform the page caching method as described in any one of claims 6-9.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute and implement the page caching method as described in any one of claims 1-5, or the page caching method as described in any one of claims 6-9.

16. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the page caching method as described in any one of claims 1-5, or the page caching method as described in any one of claims 6-9.

Images