A method for caching page data and related equipment

Abstract

The embodiment of the present application provides a method for caching page data and related equipment, which are used to reduce the loading time of the page and improve the user experience. The embodiment of the present application provides a method for caching page data, which is applied to a client, and the method includes: when the application of the client is started, the target cache configuration information is obtained from the cache interface of the server corresponding to the application, and the target cache configuration information includes all target page parameter information of the target page; according to the target page parameter information, a data cache instruction is sent to the cache interface to obtain the target page cache information; the target page cache information is saved locally in a preset format; when any sub-page in the target page is accessed, any sub-page is rendered according to the locally saved target page cache information.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of software technology, and in particular to a method for caching page data and related devices thereof. Background Art

[0002] With the development of mobile Internet technology, the functions of applications (APP) are becoming more and more powerful. At the same time, HTML5 (H5 for short) pages are becoming more and more popular in APP due to their high flexibility, low development cost and short production cycle.

[0003] As the functions of APP development become more and more complete, the resource data in APP is getting larger and larger. Although the cache optimization of resources is done in the APP environment, when the H5 page in the APP is opened for the first time, it is usually necessary to request the main interface to obtain the data required for the page to be rendered, and then perform the logic processing page rendering. Once the data interface of the main interface is affected by the network and the request returns slowly, it will cause the first screen loading time of the page to increase significantly, which will have a greater impact on users who visit the page and worsen the experience. Summary of the invention

[0004] The embodiments of the present application provide a method for caching page data and related devices thereof, which are used to reduce page loading time and improve user experience.

[0005] A first aspect of an embodiment of the present application provides a method for caching page data, which is applied to a client and includes:

[0006] When the application of the client is started, the target cache configuration information is obtained from the cache interface of the server corresponding to the application, and the target cache configuration information includes all target page parameter information of the target page;

[0007] Sending a data cache instruction to the cache interface according to the target page parameter information to obtain target page cache information;

[0008] Saving the target page cache information locally according to a preset format;

[0009] When any sub-page in the target page is accessed, the any sub-page is rendered according to the locally stored cache information of the target page.

[0010] Optionally, the target cache configuration information further includes target page identification information that matches the target page parameter information one by one. Before sending the data cache instruction to the cache interface according to the target page parameter information, the method further includes:

[0011] When accessing a first sub-page, obtaining first page parameter information of the first sub-page and first page identification information matching the first page parameter information;

[0012] Verifying whether the first page identification information is the same as any page identification information in the target page identification information and whether the client has not saved the first page identification information;

[0013] If they are the same and the first page identification information is not saved, the step of sending a data cache instruction to the cache interface according to the target page parameter information to obtain the target page cache information is executed.

[0014] Optionally, the locally saving the target page cache information according to a preset format includes:

[0015] Setting the target page parameter information as the target key value of the target page cache information;

[0016] The target page cache information and the target key value of the target page cache information are saved.

[0017] Optionally, the target cache configuration information further includes target page identification information that matches the target page parameter information one by one. After the page data cache information is saved in a preset format, the method further includes:

[0018] Naming the target page cache information according to the matching relationship between the target page parameter information and the target page identification information to form naming information of the target page cache information;

[0019] Saving the target page cache information to the client according to the format of the naming information;

[0020] The target matching relationship between the target page parameter information and the naming information is saved to the client.

[0021] Optionally, after the target matching relationship between the target page parameter information and the naming information is saved to the client, the method further includes:

[0022] When accessing the second sub-page, obtaining second page parameter information of the second sub-page;

[0023] Determining whether to update the target matching relationship according to the second page parameter information;

[0024] If yes, obtaining first cache configuration information corresponding to the second sub-page from the cache interface to determine whether the first cache configuration information has page identification information that is the same as the target page identification information;

[0025] If not, access the second sub-page according to the hypertext transfer HTTPS protocol.

[0026] Optionally, the first cache configuration information includes second page identification information matching the second page parameter information, and determining whether the first cache configuration information includes page identification information that is the same as the target page identification information includes:

[0027] Determine whether the target page identification information contains the second page identification information;

[0028] If yes, update the target page parameter information to the second page parameter information;

[0029] If not, execute the step of accessing the second sub-page according to the hypertext transfer HTTPS protocol.

[0030] Optionally, after the target page cache information is locally saved in a preset format, the method further includes:

[0031] If any page is not in the login state, log in to any page, and any page includes the target page and any sub-page;

[0032] Determining whether the application saves the target cache configuration information;

[0033] If so, executing the step of rendering any of the sub-pages according to the locally stored cache information of the target page;

[0034] If not, receive the target page cache information sent by the server through the cache interface, and render the page according to the target page cache information.

[0035] Optionally, the locally saving the target page cache information according to a preset format includes:

[0036] When acquiring the target page cache information, acquiring real-time time information;

[0037] The real-time information is written into the target page cache information, and the target page cache information after the real-time information is written is stored locally.

[0038] Optionally, after writing the real-time information into the target page cache information and saving the target page cache information locally, the method further includes:

[0039] If the application is closed, the current time information of closing the application is obtained;

[0040] Calculate the real-time time information and the current time information to obtain a calculation result;

[0041] Determining whether the calculation result is greater than a preset threshold;

[0042] If so, delete the target page cache information.

[0043] A second aspect of an embodiment of the present application provides a system for caching page data, which is applied to a client and includes:

[0044] An acquisition unit, configured to acquire target cache configuration information from a cache interface of a server corresponding to the application when the application of the client is started, wherein the target cache configuration information includes all target page parameter information of the target page;

[0045] A sending unit, configured to send a data cache instruction to the cache interface according to the target page parameter information to obtain target page cache information;

[0046] A storage unit, used for locally storing the target page cache information according to a preset format;

[0047] The rendering unit is used to render any sub-page in the target page according to the locally stored cache information of the target page when accessing the sub-page.

[0048] Optionally, the target cache configuration information further includes target page identification information that matches the target page parameter information one by one, and the system further includes: a verification unit and an execution unit;

[0049] The acquisition unit is further configured to acquire, when accessing the first sub-page, first page parameter information of the first sub-page and first page identification information matching the first page parameter information;

[0050] The verification unit is used to verify whether the first page identification information is the same as any page identification information in the target page identification information and whether the client has not saved the first page identification information;

[0051] The execution unit is used to execute the step of sending a data cache instruction to the cache interface according to the target page parameter information to obtain the target page cache information when the first page identification information is the same as any page identification information in the target page identification information and the first page identification information is not saved.

[0052] Optionally, the system further comprises: a setting unit and a saving unit;

[0053] The setting unit is used to set the target page parameter information as the target key value of the target page cache information;

[0054] The saving unit is used to save the target page cache information and the target key value of the target page cache information.

[0055] Optionally, the target cache configuration information further includes target page identification information that matches the target page parameter information one by one, and the system further includes: a naming unit;

[0056] The naming unit is used to name the target page cache information according to the matching relationship between the target page parameter information and the target page identification information to form the naming information of the target page cache information;

[0057] The storage unit is further used to save the target page cache information to the client according to the format of the naming information;

[0058] The storage unit is further used to save the target matching relationship between the target page parameter information and the naming information to the client.

[0059] Optionally, the system further comprises: an updating unit and an accessing unit;

[0060] The acquisition unit is further configured to acquire second page parameter information of the second sub-page when accessing the second sub-page;

[0061] The updating unit is used to determine whether to update the target matching relationship according to the second page parameter information;

[0062] The acquisition unit is further configured to acquire, when updating the target matching relationship, first cache configuration information corresponding to the second sub-page from the cache interface to determine whether the first cache configuration information has page identification information that is the same as the target page identification information;

[0063] The access unit is used to access the second sub-page according to the hypertext transfer HTTPS protocol when the target matching relationship is not updated.

[0064] Optionally, the system further comprises: a judgment unit;

[0065] The judging unit is used to judge whether the target page identification information contains the second page identification information;

[0066] The updating unit is specifically configured to update the target page parameter information to the second page parameter information when the second page identification information exists;

[0067] The execution unit is specifically used to execute the step of accessing the second sub-page according to the hypertext transfer HTTPS protocol when the second page identification information does not exist.

[0068] Optionally, the system further comprises: a landing unit and a receiving unit;

[0069] The login unit is used to log in to any page when any page is in a non-login state, and the any page includes the target page and any sub-page;

[0070] The determining unit is further configured to determine whether the application program saves the target cache configuration information;

[0071] The execution unit is further configured to execute the step of rendering any sub-page according to the locally stored target page cache information when the application saves the target cache configuration information;

[0072] The receiving unit is used to receive the target page cache information sent by the server through the cache interface when the application does not save the target cache configuration information, and perform page rendering according to the target page cache information.

[0073] Optionally,

[0074] The acquisition unit is specifically used to acquire real-time time information when acquiring the target page cache information;

[0075] The storage unit is specifically used to write the real-time information into the target page cache information, and store the target page cache information after writing the real-time information locally.

[0076] Optionally, the system further comprises: a calculation unit and a deletion unit;

[0077] The acquisition unit is further configured to acquire current time information of closing the application program when closing the application program;

[0078] The calculation unit is used to calculate the real-time time information and the current time information to obtain a calculation result;

[0079] The judging unit is further configured to judge whether the calculation result is greater than a preset threshold;

[0080] The deleting unit is used to delete the target page cache information when the calculation result is greater than a preset threshold.

[0081] The second aspect of the embodiments of the present application provides a method for executing the method described in the first aspect.

[0082] A third aspect of an embodiment of the present application provides a device for caching page data, including:

[0083] CPU, memory, input and output interfaces, wired or wireless network interfaces, and power supply;

[0084] The memory is a short-term storage memory or a persistent storage memory;

[0085] The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method described in the first aspect.

[0086] A fourth aspect of an embodiment of the present application provides a computer-readable storage medium, characterized in that the computer-readable storage medium includes instructions, and when the instructions are executed on a computer, the computer executes the method described in the first aspect.

[0087] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0088] A method for page data caching applied to a client is proposed in an embodiment of the present application. When the client application is started, the target cache configuration information is obtained from the cache interface of the server corresponding to the application. Then, a data cache instruction is sent to the cache interface according to the target page parameter information to obtain the target page cache information. The target page cache information is then saved locally in a preset format. Finally, when any sub-page in the target page is accessed, any sub-page is rendered according to the locally saved target page cache information. Therefore, when opening a page, the page cache information can be directly used to replace the request interface data, thereby reducing the time consumed for loading the page, achieving the effect of opening in seconds, and providing a better customer experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0089] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0090] Figure 1 A schematic diagram of a system architecture of a page data cache disclosed in an embodiment of the present application;

[0091] Figure 2 A schematic diagram of a flow chart of a page data caching method disclosed in an embodiment of the present application;

[0092] Figure 3 A flowchart of another page data caching method disclosed in an embodiment of the present application;

[0093] Figure 4 A flowchart of another page data caching method disclosed in an embodiment of the present application;

[0094] Figure 5 A schematic diagram of the structure of a page data cache system disclosed in an embodiment of the present application;

[0095] Figure 6 A schematic diagram of the structure of a page data cache device disclosed in an embodiment of the present application. DETAILED DESCRIPTION

[0096] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0097] It should be noted that the descriptions involving "first", "second", etc. in this application are only for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in this field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by this application.

[0098] With the development of mobile Internet technology, the functions of application APP are becoming more and more powerful. At the same time, H5 pages are becoming more and more popular in APP due to their high flexibility, low development cost and short production cycle.

[0099] As the functions of APP development become more and more complete, the resource data in APP is getting larger and larger. Although the cache optimization of resources is done in the APP environment, when opening an H5 page for page rendering, it is usually necessary to obtain the data content through a main interface before rendering the first screen. It should be noted that the main interface refers to the background data interface that needs to be obtained for page rendering, such as the product information data interface, the advertising space material data interface, etc. For the convenience of understanding and description, the specific content contained in the main interface will not be restricted in the future, and it will not be repeated in the future.

[0100] As a result, two problems are likely to arise: 1. Although resource cache optimization is done in the APP environment, when the H5 page in the APP is opened for the first time, it is usually necessary to request the main interface to obtain the data required for the page to be rendered, and then perform logical processing to render the page. 2. Once the data interface of the main interface is affected by the network and the request returns slowly, the first screen loading time of the page will be greatly increased, which will have a relatively large impact on the customer experience of page access.

[0101] Therefore, an embodiment of the present application proposes a page data caching method, which makes an advance request for the cached data needed for H5 page rendering when the APP is started. When the H5 page is opened in the subsequent process, the cached data is directly used to replace the request interface data, thereby reducing the time consumed in loading the first screen of the H5 page and achieving the effect of opening in seconds.

[0102] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0103] See also Figure 1 , Figure 1 The schematic diagram of the system architecture of a page data cache disclosed in the embodiment of the present application includes a server 101 and a client 102 .

[0104] like Figure 1As shown, the system architecture may include a server 101 and a client 102, and the client 102 may include: client 102a, client 102b, client 102c, ..., client 102n and other clients. Among them, the above-mentioned server 101 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud database, cloud service, cloud computing, cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, CDN, and big data and artificial intelligence platform. The client (including client 102a, client 102b, client 102c, ..., client 102n) can be a smart phone, tablet computer, laptop computer, desktop computer, PDA, mobile Internet device (MID, mobile internet device), wearable device (such as smart watch, smart bracelet, etc.), smart computer, smart car and other smart terminals. Among them, the server 101 can establish a communication connection with each client in the client 102. In other words, the server 101 can establish a communication connection with each of the clients 102a, 102b, 102c, ..., 102n, for example, a communication connection can be established between the client 102a and the server 101. The above communication connection does not limit the connection mode, and can be directly or indirectly connected through a wired communication mode, or directly or indirectly connected through a wireless communication mode, etc., which can be determined according to the actual application scenario, and this application does not limit it here.

[0105] It should be understood that Figure 1 Each client in the client cluster shown in FIG. 1 may be installed with an application client. When the application client runs in each client, it may be respectively connected to the above-mentioned Figure 1The servers 101 shown in the figure perform data interaction, so that each client can receive business data from the server 101 (such as image cache data sent by the server). Among them, the application APP on the client 102 can be a social application, instant messaging application, live broadcast application, game application, short video application, video application, music application, karaoke application, shopping application, novel application, payment application, etc., which has the function of displaying text, images, audio and video and other data information. The specific requirements can be determined according to the actual application scenario requirements, and no limitation is made here. Among them, the client 102 can be an independent client or an embedded sub-client integrated in a client (such as an instant messaging client, a social client, etc.), which can be determined according to the actual application scenario, and no limitation is made here. Taking the shopping application as an example, when the customer uses the shopping application through the client 102, the server 101 can send the corresponding page cache information to the client 102 in advance according to the cache configuration information on the shopping application. The shopping applications on each client (client 102a, client 102b, client 102c, ..., client 102n) that establishes a communication connection with the server 101 can obtain the corresponding page cache information. Figure 1 The server 101 shown in FIG. 100 may also be executed by a client (eg, Figure 1 The process may be executed by any one of the client 102a, client 102b, ..., client 102n shown in the figure, or may be executed jointly by the client and the server 101. The specific process may be determined according to the actual application scenario and is not limited here.

[0106] For ease of understanding and description, a page data caching method proposed in an embodiment of the present application is described in detail below. Figure 2 , Figure 2 This is a flow chart of a page data caching method disclosed in an embodiment of the present application, including steps 201 to 204.

[0107] 201. When the client application is started, the target cache configuration information is obtained from the cache interface of the server corresponding to the application.

[0108] When you open an APP on the client, WKWebView will be initialized in advance. It should be noted that WKWebView is a browser control. Correspondingly, it initializes the browser process environment in the APP, which can make the first opening of the H5 page faster (the H5 page is opened through the browser webview in the APP).

[0109] Specifically, when hot starting the APP, the client will obtain the offline cache protocol JSON configuration list from the cache interface of the server corresponding to the APP. It should be noted that the offline cache protocol JSON configuration list described in this embodiment is the target cache configuration information described in the above section.

[0110] Correspondingly, the target cache configuration information is the configuration information written in advance by the OA management platform. It should be added that the OA management platform can not only perform configuration management, but also is a JSON protocol generation platform (just enter the page URL), and can also provide a query interface, that is, a cache interface. It should also be added that the OA management platform also has other functions, which are not described in detail in this embodiment, and the specific functions of the OA management platform will not be described later. Among them, it should be added that every web page on the Internet has a unique name identifier, usually referred to as a uniform resource locator (URL). It is the uniform resource locator of www. Simply put, URL is a web address, commonly known as a "website address". For the convenience of description and understanding, the URL will not be described in detail later.

[0111] Specifically, the APP on the client sends an interface request message to the server, thereby obtaining the target cache configuration information, that is, the JSON configuration list, sent by the server through the cache interface. Among them, the target cache configuration information includes all target page parameter information of the target page. In other words, the OA management platform can set up the pages that need to be cached in advance in the APP, and correspondingly, it is necessary to set the page parameter information of the page that needs to be cached in advance, that is, the page URL.

[0112] Furthermore, each time you hot start the app, you can request the server to get the latest JSON list. It should be added that hot start refers to the process of switching the mobile phone app to the background and then opening it from the background to the interface.

[0113] 202. Send a data cache instruction to the cache interface according to the target page parameter information to obtain the target page cache information.

[0114] After obtaining the target page parameter information, that is, the corresponding page URL, a pre-request is made to the server's cache interface according to the determined target page parameter information, thereby requesting the interface cache. Specifically, a data cache instruction is sent to the server's cache interface, thereby requesting the server to send the target page cache information corresponding to the page URL, that is, the cache data of the page.

[0115] 203. Save the target page cache information locally according to a preset format.

[0116] After the request obtains the interface data, that is, after obtaining the target page cache information, the data is written into the memory according to the format defined by result_format.

[0117] Specifically, one embodiment of the specific format may be:

[0118]

[0119] Each URL corresponds to a cache data. It is not difficult to understand that the present embodiment does not limit the number of URLs, and will not be described in detail later. Thus, the client can save the target page cache information in the local cache pool according to the above format.

[0120] Furthermore, after the client saves the target page cache information, it can also provide JSAPI parameter transmission for the page to read data. Among them, JSAPI is the bridge for APP and H5 to communicate, the application programming interface (API). Correspondingly, parameter transmission means that H5 tells APP the parameters (URL is the parameter), and APP returns the corresponding target page cache information to H5 based on this parameter, that is, the cache interface data stored corresponding to the URL.

[0121] 204. When any sub-page in the target page is accessed, any sub-page is rendered according to the locally stored cache information of the target page.

[0122] When a user enters an activity page in some APP through operations such as clicking, that is, when accessing any sub-page in the target page, the sub-page can send the URL parameters that need to be loaded in this page to the client, so that the client finds the cache data corresponding to the URL parameters in the target page cache information according to the URL parameters, and sends the cache data required by the page to the sub-page, so that the sub-page renders the page according to the read cache data, that is, the corresponding target page cache information.

[0123] Through the method of page data caching applied to the client proposed in this embodiment, when the client application is started, the target cache configuration information is obtained from the cache interface of the server corresponding to the application, and then the data cache instruction is sent to the cache interface according to the target page parameter information to obtain the target page cache information, and then the target page cache information is saved locally according to the preset format, and finally, when any sub-page in the target page is accessed, any sub-page is rendered according to the locally saved target page cache information. Therefore, when opening a page, the page cache information can be directly used to replace the request interface data, thereby reducing the time consumed for loading the page, achieving the effect of opening in seconds, and providing a better customer experience.

[0124] See also Figure 3 , Figure 3 This is a flow chart of another method for caching page data disclosed in an embodiment of the present application, including steps 301 to 307. It should be noted that this embodiment is mainly applied to an application APP on a client.

[0125] 301. When the client application is started, the target cache configuration information is obtained from the cache interface of the server corresponding to the application.

[0126] In this embodiment, step 301 is the same as the aforementioned Figure 2 The step 201 is similar and will not be described in detail here. However, it should be noted that a specific embodiment of a target cache configuration information, that is, a corresponding offline cache protocol JSON configuration list, can be, wherein the JSON data format is as follows:

[0127]

[0128]

[0129] It is not difficult to understand that the above is only one specific embodiment of the JSON data format, and this embodiment does not limit the specific implementation code in the JSON data format.

[0130] 302. When accessing the first sub-page, first page parameter information of the first sub-page and first page identification information matching the first page parameter information are obtained.

[0131] When a user clicks on a page on the application interface, that is, when the client accesses the first sub-page, the first page parameter information of the first sub-page and the first page identification information matching the first page parameter information can be obtained. It should be noted that the first page parameter information is the page URL, and the first page identification information is the message digest algorithm (MD5), which is an encrypted string and a widely used cryptographic hash function that can generate a 128-bit hash value to ensure the integrity and consistency of information transmission.

[0132] Furthermore, before accessing the first sub-page, the WEEX_BRIDGE or H5_BRIDGE corresponding to Weex or H5 will provide file cache writing to JSAPI, so that the APP can provide the corresponding JSAPI parameter passing method for the H5 page to read data. It should be noted that the file cache described above can also be understood as the page parameter information of the sub-page and the page identification information matching the page parameter information. For example, when the client accesses the first sub-page, the page URL of the first sub-page written by H5_BRIDGE and the corresponding MD5 can be obtained.

[0133] 303 , verify whether the first page identification information is the same as any page identification information in the target page identification information and whether the client has not saved the first page identification information. If so, execute step 304 .

[0134] As can be seen from step 301, the target cache configuration information also includes target page identification information that matches the target page parameter information one by one. Specifically, each segment of the target page parameter information corresponds to a segment of the target page identification information.

[0135] Specifically, the target page parameter information in the target cache configuration information can be queried or read according to the first page parameter information, that is, the first page URL (filter parameter). Correspondingly, the loading resource list of the first sub-page in the protocol JSON is queried / read according to the page URL.

[0136] Then, it is checked whether the identification information of the first page after the visit is the same as the target page identification information in the target cache configuration information. Correspondingly, it is checked whether the MD5 corresponding to the URL of the first page after the visit is equal to the MD5 in the JSON configuration table.

[0137] If the MD5 corresponding to the first page URL is equal to the MD5 in the JSON configuration table, it is determined whether the first page identification information, that is, the MD5 corresponding to the first page URL, is saved locally on the client.

[0138] If the MD5 corresponding to the URL of the first page is not equal to the MD5 in the JSON configuration table, the process ends directly without executing subsequent steps.

[0139] After determining whether the first page identification information is stored locally on the client, if there is no MD5 corresponding to the first URL in the local cache, step 304 is executed; if there is an MD5 corresponding to the first URL in the local cache, steps 304 to 306 are no longer executed, which is equivalent to caching the target page cache information. Step 307 can be executed directly.

[0140] Furthermore, when the client accesses the main page on the APP, the same action as step 303 is also performed, and the details are not repeated here.

[0141] 304. Send a data cache instruction to the cache interface according to the target page parameter information to obtain the target page cache information.

[0142] In this embodiment, step 304 is similar to the above Figure 2 It is similar to step 202, and will not be described in detail here. However, it should be noted that since the request protocol rules are configured in step 301, specifically, according to the requestData field (which is at the same level as the directory of the url field in coreResourceList), the cache interface is cached in accordance with the offline cache protocol, that is, a data cache instruction is sent to the cache interface. Among them, it should be noted that requestData refers to some request protocol rules that I have set in advance below. If get is passed in, APP will use get for interface request, and if post is passed in, post will be used for interface request.

[0143] Furthermore, since json defines the coreResourceList field, url is the corresponding mapping, which means that the APP stores the data cached by the interface request in advance according to this url. Later, the H5 page can communicate with the app according to the url to obtain data, and the H5 page does not need to request the interface.

[0144] 305. Set the target page parameter information as the target key value of the target page cache information, and save the target page cache information and the target key value of the target page cache information.

[0145] In this embodiment, step 305 is the same as the aforementioned Figure 2The above is similar to step 203, and the details are not repeated here. However, it should be noted that when the target page cache information is written into the client's memory, the target page parameter information can be set as the target key value of the target page cache information, and the target page cache information and the target key value of the target page cache information can be saved. Specifically, according to the format in the JSON configuration table in step 301, the htm url is used as the key value, that is, the target key value. Then, the target page cache information corresponding to each segment of the url and the target key value, that is, the key value, are saved in a one-to-one correspondence, so that when the H5 page is accessed, the H5 page can also directly read the corresponding target page cache information according to the key value.

[0146] Furthermore, the target page cache information can also be named according to the matching relationship between the target page parameter information and the target page identification information to form the naming information of the target page cache information, and then the target page cache information is saved to the client in the format of the naming information, and the target matching relationship between the target page parameter information and the naming information is also saved to the client. Specifically, the resource file in the JSON protocol (the page cache information corresponding to the URL, which may specifically include js, css, png and other files) is cached locally on the client with MD5 as the name, and a mapping of url: MD5 is cached. Among them, the naming information of the APP local file cache can be MD5_1, MD5_2, MD5_3, ... and so on. The specific number of names is related to the number of fields of the target page parameter information (URL), and this embodiment does not limit this. Then, correspondingly, the mapping of the APP local cache is URL1: MD5_1, URL2: MD5_2, URL3: MD5_3, ... and so on. For the convenience of description, the specific meaning of the resource file and the content contained therein will not be repeated in the future.

[0147] 306. When the target page cache information is obtained, the real-time time information is obtained, and the real-time time information is written into the target page cache information, and the target page cache information after the real-time time information is written is saved locally.

[0148] When the APP local cache pool obtains the target page cache information, that is, when the interface data is stored in the memory, the real-time time when the target page cache information is obtained will be obtained. When storing the target page cache information, the obtained real-time time, that is, the current time field, will be written into the target page cache information. Specifically, a timestamp will be recorded when the APP requests the interface. Then the target page cache information written with the real-time time is saved locally.

[0149] Furthermore, when the APP is closed, that is, when the APP process is closed, the client will obtain the current time when the APP is closed at this time. By calculating the current time and the real-time time, the calculation result is obtained, and then it is determined whether the calculation result is greater than the preset threshold. If it is greater than the preset threshold, the target page cache information is deleted. Specifically, the time when the calculated file most recently accessed the H5 page can be compared with the real-time time of the target page cache information obtained above to determine whether it is greater than a certain threshold. For example, it can be set to 10s or 5s. It can be modified according to the page's requirements for the real-time nature of the cached data. The specific value of the threshold is not limited here, and it will not be repeated later. When the threshold is exceeded, the resource file corresponding to the MD5 of the H5 page in the target page cache information is deleted, so that the client can execute the above steps to obtain the latest JSON file to obtain the latest target page cache information.

[0150] Furthermore, the real-time information can be used to tell H5 whether to use the target page cache information. Some business scenarios have high requirements for the real-time performance of cached data, so it may not be used. When the business scenario does not have high requirements for the real-time performance of cached data or does not need it, step 306 can be skipped, thereby achieving business protection.

[0151] 307. When any sub-page in the target page is accessed, any sub-page is rendered according to the locally stored cache information of the target page.

[0152] In this embodiment, step 307 is the same as the aforementioned Figure 2 The process is similar to step 204, and will not be described in detail here.

[0153] Through the page data caching method proposed in this embodiment, the application APP on the client can obtain the corresponding target page cache information from the server through the configured target cache configuration information. At the same time, the APP stores the HTML file content in advance through the pre-request of the cache interface, and stores the cache data with a specific mapping relationship, which makes it convenient for the H5 page to call the cache data according to the specific mapping relationship, thereby improving the feasibility of the solution.

[0154] See also Figure 4 , Figure 4 This is a flowchart of another page data caching method disclosed in an embodiment of the present application. It includes steps 401 to 410. It should be noted that this embodiment is mainly used when accessing H5 pages. It should also be noted that the various types of page parameter information, page configuration information and page identification information mentioned in this embodiment can be found in the execution steps when obtaining in steps 301 to 307, and the specific obtaining steps will not be repeated in this embodiment.

[0155] 401. When accessing a second sub-page, obtain second page parameter information of the second sub-page.

[0156] APP startup refers to the time when the APP is opened. At this time, the H5 page has not been accessed. Only when the user enters some activity pages through clicks and other operations, these are called accessing the H5 page. APP startup is a pre-condition, so data can be cached in advance at this time. When H5 is accessed, there is no need to request the interface and directly use the cached data.

[0157] Specifically, when the user enters the second sub-page in the APP through operations such as clicking, the second sub-page will send the second page parameter information (page URL) to the client, so that the client can obtain the second page parameter information of the second sub-page.

[0158] Furthermore, when the first sub-page is accessed for the first time, the first sub-page and the second sub-page may be the same sub-page.

[0159] 402. Determine whether to update the target matching relationship according to the second page parameter information. If yes, execute step 403; if not, execute step 404.

[0160] After the client obtains the second page parameter information, it can determine whether to update the target matching relationship stored in the client according to the second page parameter information. Figure 3 If yes, go to step 403; if no, go to step 404.

[0161] Specifically, the page URL (filter parameter) is used to determine whether the HTML file is intercepted in the mapping table, where interception means whether to read the cache, in other words, whether to update it. Since there is a mapping of the APP local cache in the mapping table, the corresponding target page parameter information can be read according to the second page parameter information URL.

[0162] 403. Obtain first cache configuration information corresponding to the second sub-page from the cache interface.

[0163] If the target page cache information needs to be updated, the corresponding second sub-page can obtain the first cache configuration information corresponding to the second sub-page from the server through the cache interface. Specifically, the second sub-page can obtain the JSON protocol configured by the OA management platform through the cache interface, and the JSON protocol at this time is the latest JSON protocol of the page. At this time, the second sub-page can query the latest JSON protocol of the page. Among them, the first cache configuration information includes the second page parameter information and the second page identification information matching the second page parameter information.

[0164] 404. Access the second subpage according to the hypertext transfer HTTPS protocol.

[0165] If the target page cache information does not need to be updated, or the MD5 in the latest JSON protocol does not exist in the local cache, the Hypertext Transport Protocol Server (HTTPS) is used directly.

[0166] 405. Determine whether the target page identification information contains the second page identification information. If so, execute step 406; if not, execute step 404.

[0167] After obtaining the latest target cache configuration information, that is, the first cache configuration information, it is determined whether the target page identification information in the local cache exists with the second page identification information in the first cache configuration information. Specifically, it is determined whether the latest JSON protocol MD5 exists in the cache. If so, execute step 406; if not, execute step 404.

[0168] 406. Update the target page parameter information to the second page parameter information.

[0169] When the MD5 of the JSON protocol exists in the local cache, the target page parameter information is updated to the second page parameter information. Specifically, the page URL is updated.

[0170] Furthermore, since the page URL corresponds to the pictures, videos, etc. required for page rendering, it can also be understood as intercepting and replacing the resource files (pictures, videos, etc.). In other words, it is to replace the displayed pictures or videos of the sub-pages.

[0171] 407. If any page is not in the logged-in state, log in to any page.

[0172] After replacing the target page parameter information, it is necessary to determine whether the user has logged in on the page. Specifically, this involves some business logic, such as the case of different recommendations for different users (different recommended data is returned for each user). This may be because the user has not logged in when the APP is first opened, so the page cache data is naturally not logged in. After the user logs in, due to the different recommendations for different users, the interface data returned by each user is inconsistent, so the data needs to be cleared again, and the page cache data request is made again with the current login state to replace the previous page cache data.

[0173] When any page is in a non-logged-in state, in this embodiment, when the second sub-page is in a non-logged-in state, log in to the second sub-page. At this time, after successfully logging in through the native login page, the JSON list inside will be called back to update the pre-requested page cache data. For details, please refer to Figure 3 After step 301, the steps after obtaining the target cache configuration information are not described in detail here. For the convenience of description, the H5 page is described as the second sub-page in the following, and no further description is given in the following.

[0174] It should be added that callback means that after logging in through the APP, the APP will send a login success message to the H5 page and re-request the data interface to obtain the latest cache information of the target page.

[0175] It should also be added that any page includes the target page and any sub-page.

[0176] 408. Determine whether the application program saves the target cache configuration information. If yes, execute step 409; if no, execute step 410.

[0177] When the second sub-page is in the login state, it is determined whether the local cache of the APP has the target cache configuration information, specifically, it is determined whether the html has the cache interface data. If so, step 409 is executed; if not, step 410 is executed.

[0178] It should be added that the target cache configuration information for specific caches can be found in Figure 3 In step 304, the target page cache information is obtained according to the latest target page parameter information obtained.

[0179] 409. Render any sub-page according to the locally stored target page cache information.

[0180] If the local cache has the target page cache information, the second sub-page is rendered according to the locally stored target page cache information.

[0181] Furthermore, any sub-page is rendered according to the locally stored target page cache information.

[0182] 410. Receive target page cache information sent by the server through the cache interface, and render the page according to the target page cache information.

[0183] If the target page cache information is not cached locally, it is determined whether to return to the original H5 page after logging in. In this embodiment, it can be understood that after the second sub-page login is successful, and the target page cache information is not cached locally, the user needs to determine whether to return to the second sub-page.

[0184] If so, the second sub-page needs to send a request to the server through the cache interface according to the second page parameter information corresponding to the second sub-page, thereby requesting the online interface data, that is, the page cache information of the second sub-page. The business logic involved at this time can refer to the situation of one thousand faces for one thousand people in step 407.

[0185] After the page cache information of the second sub-page is obtained, the second sub-page can be rendered according to the page cache information of the second sub-page.

[0186] Furthermore, when returning to any page, the user needs to determine whether to return to the page. If determined to return, the corresponding page cache information can be obtained according to the page parameter information (page URL) of the page, so that the page can be rendered according to the page cache information.

[0187] Through the page data caching method proposed in this embodiment, by building a general H5 data offline caching solution system, important pages in the APP can be opened in seconds. At the same time, the APP stores the pre-request of the interface in the HTML file in advance. When the access page determines that the interface cache data exists, it does not request the interface again, thereby speeding up the rendering of the first screen content of the page and improving the feasibility of the solution.

[0188] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0189] If the plan involves sensitive information (such as customer information, corporate information), it should be stated that the collection, use and processing of sensitive information must comply with the laws, regulations and standards of relevant countries and regions, and must be carried out with the permission or consent of the relevant entities (such as customers or companies).

[0190] See also Figure 5 , Figure 5 This is a system structure diagram of a page data cache disclosed in an embodiment of the present application. It includes:

[0191] The acquisition unit 501 is used to acquire target cache configuration information from the cache interface of the server corresponding to the application when the application of the client is started, and the target cache configuration information includes all target page parameter information of the target page;

[0192] The sending unit 502 is used to send a data cache instruction to the cache interface according to the target page parameter information to obtain the target page cache information;

[0193] A saving unit 503 is used to save the target page cache information locally according to a preset format;

[0194] The rendering unit 504 is used to render any sub-page in the target page according to the locally stored target page cache information when accessing any sub-page in the target page.

[0195] Exemplarily, the target cache configuration information also includes target page identification information that matches the target page parameter information one by one, and the system also includes: a verification unit 505 and an execution unit 506;

[0196] The acquisition unit 501 is further configured to acquire first page parameter information of the first subpage and first page identification information matching the first page parameter information when accessing the first subpage;

[0197] A verification unit 505 is used to verify whether the first page identification information is the same as any page identification information in the target page identification information and whether the client has not saved the first page identification information;

[0198] The execution unit 506 is used to execute the step of sending a data cache instruction to the cache interface according to the target page parameter information to obtain the target page cache information when the first page identification information is the same as any page identification information in the target page identification information and the first page identification information is not saved.

[0199] Exemplarily, the system further includes: a setting unit 507 and a saving unit 503;

[0200] A setting unit 507, used to set the target page parameter information as the target key value of the target page cache information;

[0201] The saving unit 503 is used to save the target page cache information and the target key value of the target page cache information.

[0202] Exemplarily, the target cache configuration information also includes target page identification information that matches the target page parameter information one by one, and the system further includes: a naming unit 508;

[0203] A naming unit 508, configured to name the target page cache information according to the matching relationship between the target page parameter information and the target page identification information, so as to form naming information of the target page cache information;

[0204] The saving unit 503 is further used to save the target page cache information to the client in the format of the naming information;

[0205] The saving unit 503 is further used to save the target matching relationship between the target page parameter information and the naming information to the client.

[0206] Exemplarily, the system further includes: an updating unit 509 and an accessing unit 510;

[0207] The acquisition unit 501 is further used to acquire the second page parameter information of the second sub-page when accessing the second sub-page;

[0208] An updating unit 509, configured to determine whether to update the target matching relationship according to the second page parameter information;

[0209] The acquisition unit 501 is further configured to acquire, when updating the target matching relationship, the first cache configuration information corresponding to the second sub-page from the cache interface to determine whether the first cache configuration information has page identification information identical to the target page identification information;

[0210] The access unit 510 is used to access the second sub-page according to the hypertext transfer HTTPS protocol when the target matching relationship is not updated.

[0211] Exemplarily, the system further includes: a judgment unit 511;

[0212] A judging unit 511 is used to judge whether the target page identification information contains second page identification information;

[0213] The updating unit 509 is specifically configured to update the target page parameter information to the second page parameter information when the second page identification information exists;

[0214] The execution unit 506 is specifically configured to execute the step of accessing the second sub-page according to the hypertext transfer HTTPS protocol when the second page identification information does not exist.

[0215] Exemplarily, the system further includes: a login unit 512 and a receiving unit 513;

[0216] A login unit 512, used to log in to any page when any page is in a non-login state, and any page includes a target page and any sub-page;

[0217] The judging unit 511 is further used to judge whether the application program saves the target cache configuration information;

[0218] The execution unit 506 is further configured to execute the step of rendering any sub-page according to the locally stored target page cache information when the application saves the target cache configuration information;

[0219] The receiving unit 513 is used to receive the target page cache information sent by the server through the cache interface when the application does not save the target cache configuration information, and perform page rendering according to the target page cache information.

[0220] For example,

[0221] The acquisition unit 501 is specifically used to acquire real-time time information when acquiring target page cache information;

[0222] The saving unit 508 is specifically used to write the real-time information into the target page cache information, and save the target page cache information after the real-time information is written locally.

[0223] Exemplarily, the system further includes: a calculation unit 514 and a deletion unit 515;

[0224] The acquisition unit 501 is also used to acquire the current time information of closing the application when closing the application;

[0225] A calculation unit 514, used to calculate the real-time time information and the current time information to obtain a calculation result;

[0226] The judging unit 511 is further used to judge whether the calculation result is greater than a preset threshold;

[0227] The deleting unit 515 is used to delete the target page cache information when the calculation result is greater than a preset threshold.

[0228] See below Figure 6 , a schematic diagram of the structure of a page data cache device disclosed in an embodiment of the present application, the device includes:

[0229] CPU 601, memory 605, input / output interface 604, wired or wireless network interface 603 and power supply 602;

[0230] The memory 605 is a temporary storage memory or a permanent storage memory;

[0231] The CPU 601 is configured to communicate with the memory 605 and execute the instructions in the memory 605 to perform the aforementioned Figures 2 to 4 The method of any one of the embodiments shown in .

[0232] The embodiment of the present application also provides a chip system, characterized in that the chip system includes at least one processor and a communication interface, the communication interface and the at least one processor are interconnected through a line, and the at least one processor is used to run a computer program or instruction to execute the aforementioned Figures 2 to 4 The method of any one of the embodiments shown in .

[0233] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0234] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0235] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0236] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0237] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk and other media that can store program code.

Claims

1. A method for caching page data, characterized in that: Applied to a client, the method comprises: When the application of the client is started, the target cache configuration information is obtained from the cache interface of the server corresponding to the application, wherein the target cache configuration information is a JSON configuration list and includes all target page parameter information of the target page; Sending a data cache instruction to the cache interface according to the target page parameter information to obtain target page cache information; The target page cache information is locally saved according to a preset format; the preset format is a format defined according to result_format; When accessing any sub-page in the target page, rendering the any sub-page according to the locally stored cache information of the target page; The target cache configuration information also includes target page identification information that matches the target page parameter information one by one. Before sending the data cache instruction to the cache interface according to the target page parameter information, the method also includes: When accessing the first subpage, obtaining first page parameter information of the first subpage and first page identification information matching the first page parameter information; the first page identification information is a message digest algorithm MD5; Verifying whether the first page identification information is the same as any page identification information in the target page identification information and whether the client has not saved the first page identification information; If they are the same and the first page identification information is not saved, executing the step of sending a data cache instruction to the cache interface according to the target page parameter information to obtain the target page cache information; After the page data cache information is saved in a preset format, the method further includes: Naming the target page cache information according to the matching relationship between the target page parameter information and the target page identification information to form naming information of the target page cache information; Saving the target page cache information to the client according to the format of the naming information; The target matching relationship between the target page parameter information and the naming information is saved to the client.

2. The method for caching page data according to claim 1, characterized in that: The locally storing the target page cache information in a preset format includes: Setting the target page parameter information as the target key value of the target page cache information; The target page cache information and the target key value of the target page cache information are saved.

3. The method for caching page data according to claim 1, characterized in that: After the target matching relationship between the target page parameter information and the naming information is saved to the client, the method further includes: When accessing the second sub-page, obtaining second page parameter information of the second sub-page; Determining whether to update the target matching relationship according to the second page parameter information; If yes, obtaining first cache configuration information corresponding to the second sub-page from the cache interface to determine whether the first cache configuration information has page identification information that is the same as the target page identification information; If not, access the second sub-page according to the hypertext transfer HTTPS protocol.

4. The method for caching page data according to claim 3, characterized in that: The first cache configuration information includes second page identification information matching the second page parameter information, and the determining whether the first cache configuration information has page identification information identical to the target page identification information includes: Determine whether the target page identification information contains the second page identification information; If yes, update the target page parameter information to the second page parameter information; If not, execute the step of accessing the second sub-page according to the hypertext transfer HTTPS protocol.

5. The method for caching page data according to claim 1, characterized in that: After the target page cache information is locally saved according to a preset format, the method further includes: If any page is not in the login state, log in to any page, and any page includes the target page and any sub-page; Determining whether the application saves the target cache configuration information; If so, executing the step of rendering any of the sub-pages according to the locally stored cache information of the target page; If not, receive the target page cache information sent by the server through the cache interface, and render the page according to the target page cache information.

6. The method for caching page data according to claim 1, characterized in that: The locally storing the target page cache information in a preset format includes: When acquiring the target page cache information, acquiring real-time time information; The real-time time information is written into the target page cache information, and the target page cache information after the real-time time information is written is stored locally.

7. The method for caching page data according to claim 6, characterized in that: After writing the real-time time information into the target page cache information and storing the target page cache information locally, the method further includes: If the application is closed, the current time information of closing the application is obtained; Calculate the real-time time information and the current time information to obtain a calculation result; Determining whether the calculation result is greater than a preset threshold; If so, delete the target page cache information.

8. A system for caching page data, characterized in that: Applied to a client, the system comprises: An acquisition unit, configured to acquire target cache configuration information from a cache interface of a server corresponding to the application when the application of the client is started, wherein the target cache configuration information includes all target page parameter information of the target page; A sending unit, configured to send a data cache instruction to the cache interface according to the target page parameter information to obtain target page cache information; A storage unit, used for locally storing the target page cache information according to a preset format; A rendering unit, configured to render any sub-page in the target page according to the locally stored cache information of the target page when accessing the sub-page; The target cache configuration information also includes target page identification information that matches the target page parameter information one by one. The system also includes: a verification unit and an execution unit; The acquisition unit is further used to acquire first page parameter information of the first subpage and first page identification information matching the first page parameter information when accessing the first subpage; the first page identification information is a message digest algorithm MD5; The verification unit is used to verify whether the first page identification information is the same as any page identification information in the target page identification information and whether the client has not saved the first page identification information; The execution unit is used to execute the step of sending a data cache instruction to the cache interface according to the target page parameter information to obtain the target page cache information when the first page identification information is the same as any page identification information in the target page identification information and the first page identification information is not saved; The system further comprises: a naming unit; A naming unit, used to name the target page cache information according to the matching relationship between the target page parameter information and the target page identification information, so as to form the naming information of the target page cache information; The saving unit is further used to save the target page cache information to the client in the format of the naming information; The saving unit is also used to save the target matching relationship between the target page parameter information and the naming information to the client.

9. A device for caching page data, characterized in that: The device comprises: CPU, memory, input and output interfaces, wired or wireless network interfaces, and power supply; The memory is a short-term storage memory or a persistent storage memory; The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium comprises instructions, and when the instructions are executed on a computer, the computer is caused to perform the method according to any one of claims 1 to 7.

Images