An application page processing method and device
Patent Information
- Application Number
- CN202010772544.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-08-04
- Publication Date
- 2026-10-16
- Estimated Expiration
- 2040-08-04
Smart Images
Figure CN114064165B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data display, specifically to an application page processing method and apparatus. Background Technology
[0002] With the widespread adoption of mobile devices such as smartphones, more and more users are becoming increasingly reliant on them. In this context, various business applications have developed application clients. The user experience of these application clients directly impacts users' interest in using the products. Many factors influence user experience, among which application loading time is playing an increasingly important role. For example, among different products that perform the same function, if one product's loading time is significantly shorter than that of other products, it will greatly improve the user experience and increase user stickiness.
[0003] To avoid users frequently switching between applications, application clients often integrate browser plugins. This allows users to access other related functions within an application client using these plugins. For example, a user can access membership features or interest-based communities within an instant messaging software client using a browser plugin. When users use these functions, the client needs to request the corresponding page structure data from the server. After receiving this data, the client renders the page using the browser plugin to display the appropriate content.
[0004] In practical applications, the process of requesting data from the client may take around 300 milliseconds, and client rendering also takes around 20 milliseconds. Current technology only displays the business page after the page rendering is complete, showing a waiting screen during the interim. This display method results in an excessively long waiting screen display time, for example, around 320 milliseconds, meaning the user needs to wait approximately 320 milliseconds to see the application page, impacting user experience. This is especially true if the function involves multiple pages; when switching between these pages, each 320-millisecond wait further increases the user's waiting time, negatively affecting the user experience.
[0005] Application content
[0006] This application provides an application page processing method and apparatus to at least solve the technical problem of excessively long waiting times for page display in existing application page processing technologies.
[0007] To address the aforementioned technical problems, this application provides the following technical solutions:
[0008] This application provides an application page processing method, which is applied to a client and includes:
[0009] When a target service is detected to be triggered, the service identifier of the target service and the homepage identifier of the homepage are obtained.
[0010] Send a page retrieval request to the business server, the page retrieval request carrying the business identifier and the homepage identifier;
[0011] Receive the homepage structure data of the container page and homepage page of the target service returned by the service server;
[0012] Display the container page;
[0013] Based on the container page, the homepage page is rendered according to the homepage structure data;
[0014] The homepage is displayed.
[0015] This application provides an application page processing method, which is applied to a business server, including:
[0016] Receive a page retrieval request from the client, the page retrieval request carrying a business identifier and a homepage identifier;
[0017] Obtain the container page of the target service corresponding to the service identifier;
[0018] Obtain the homepage structure data of the homepage based on the homepage identifier;
[0019] Return the container page and homepage structure data of the target service to the client.
[0020] This application provides an application page processing method, which includes:
[0021] When the client detects that the target service has been triggered, it obtains the service identifier of the target service and the homepage identifier of the homepage, and sends a page retrieval request to the service server. The page retrieval request carries the service identifier and the homepage identifier.
[0022] The service server receives a page retrieval request from the client, retrieves the container page of the target service corresponding to the service identifier, retrieves the homepage structure data of the homepage page according to the homepage page identifier, and returns the container page and homepage structure data of the target service to the client.
[0023] The client receives the container page and homepage structure data of the target service returned by the service server, displays the container page, renders the homepage based on the container page and the homepage structure data, and displays the homepage.
[0024] This application provides an application page processing apparatus, which is applied to a client and includes:
[0025] The first acquisition module is used to acquire the service identifier of the target service and the homepage identifier of the homepage when the target service is detected to be triggered.
[0026] The first sending module is used to send a page retrieval request to the business server, the page retrieval request carrying the business identifier and the homepage identifier;
[0027] The first receiving module is used to receive the homepage structure data of the container page and homepage page of the target service returned by the service server;
[0028] The display module is used to display the container page;
[0029] The rendering module is used to render the homepage page based on the container page and the homepage structure data.
[0030] The display module is also used to display the homepage.
[0031] This application provides an application page processing apparatus, which is applied to a business server, including:
[0032] The second receiving module is used to receive a page retrieval request from the client, the page retrieval request carrying a business identifier and a homepage identifier;
[0033] The second acquisition module is used to acquire the container page of the target service corresponding to the service identifier;
[0034] The third acquisition module is used to acquire the homepage structure data of the homepage based on the homepage identifier;
[0035] The second sending module is used to return the homepage structure data of the container page and homepage page of the target service to the client.
[0036] This application provides a computer device including a processor and a memory. The memory stores multiple instructions, which are adapted for loading by the processor to execute the steps in the above-described method.
[0037] This application provides a computer-readable storage medium storing multiple instructions adapted for loading by a processor to execute the steps in the above-described method.
[0038] This application provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the steps in the above-described method.
[0039] This application provides a novel application page processing method and apparatus. In this method, when a client detects that a target service has been triggered, it obtains the service identifier of the target service and the homepage identifier of the homepage, and sends a page retrieval request to a service server. The page retrieval request carries the service identifier and the homepage identifier. The service server receives the page retrieval request from the client, obtains the container page of the target service corresponding to the service identifier, obtains the homepage structure data of the homepage based on the homepage identifier, and returns the container page and the homepage structure data of the target service to the client. The client receives the container page and the homepage structure data of the target service returned by the service server, displays the container page, renders the homepage based on the container page and the homepage structure data, and displays the homepage. Because this... This application innovatively introduces a container page for business functions. This container page includes some features of the application page. After receiving the container page, the client uses it instead of a waiting page, allowing users to see some content of the application page more quickly, instead of a tedious waiting page. Furthermore, the pre-storage of these page structure data is completed before the user clicks on other pages, so that it can be rendered and displayed directly after the user clicks, eliminating the need for the user to wait for a long time to obtain page structure data, but only requiring a short rendering time. That is, when displaying the homepage, this application can first display the container page that does not require much rendering, avoiding excessively long waiting time for page display. When the user switches to another application page, this application can render directly without requiring the user to wait for page structure data, resulting in a better user experience and solving the technical problem of excessively long waiting time for page display in existing application page processing technologies. Attached Figure Description
[0040] To more clearly illustrate the technical solutions in the embodiments of this application, 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 this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0041] Figure 1 This is a network diagram of the communication system provided in the embodiments of this application.
[0042] Figure 2 This is a flowchart illustrating the application page processing method provided in the embodiments of this application.
[0043] Figures 3a to 3b This is a schematic diagram illustrating the specific process of the application page processing method provided in the embodiments of this application.
[0044] Figures 4a to 4c This is a schematic diagram of the scenario flow of the application page processing method provided in the embodiments of this application.
[0045] Figures 5a to 5b This is a schematic diagram of the structure of the application page processing device provided in the embodiments of this application.
[0046] Figure 6 This is a schematic diagram of the structure of the computer device provided in the embodiments of this application.
[0047] Figures 7a to 7e This is a schematic diagram of a page provided in an embodiment of this application. Detailed Implementation
[0048] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0049] In this embodiment, the page structure data includes HTML data used to form the page, hereinafter referred to as sphtml. The homepage structure data refers to the page structure data corresponding to the homepage, and the non-homepage structure data refers to the page structure data corresponding to the non-homepage. The homepage refers to the first application page that the terminal needs to display after the user opens a certain function, while the non-homepage pages are other application pages of the function. In different scenarios, the homepage can be any one of the multiple application pages under the function.
[0050] In this application embodiment, the container page is an intermediate interface uniquely introduced in this application. Communication between multiple application pages is implemented based on the container page, which is an abstraction of all or multiple application pages for a certain function, such as... Figure 7a As shown, the container page only includes Figure 7b The homepage shown Figure 7c as well as Figure 7d The common page parameters of the non-homepage shown, such as only the page size and the page switching buttons at the bottom of the page, are also sent as structured data when the server sends the container page to the client. However, the data structure of the container page is simple. After receiving the structured data of the container page, the client can instantly complete the drawing and rendering of the container page based on the browser plugin and display it instantly. The drawing and rendering time of the container page is less than 1 millisecond, which can be ignored. Therefore, it can be considered that the client can directly complete the display of the container page after receiving the structured data of the container page, replacing the waiting interface and reducing the user's waiting time.
[0051] In the embodiments of this application, the page rendering, page structure data processing, and other procedures can refer to the implementation schemes in the art, and will not be described in detail here. In the server, the page structure data of each page is stored corresponding to the page identifier of that page.
[0052] Please see Figure 1 , Figure 1 This is a schematic diagram of a communication system provided in an embodiment of this application. The system may include user-side devices and server-side devices. The user-side devices and server-side devices are connected via various gateways or the Internet, etc., which will not be described in detail here. The user-side devices include multiple terminals 11, and the server-side devices include multiple servers 12; wherein:
[0053] Terminal 11 includes, but is not limited to, portable terminals such as mobile phones and tablets, as well as fixed terminals such as computers, kiosks, and advertising machines. It is a service port that users can use and operate. In this application, the terminal provides users with various functions such as data query, data modification, data addition, and registration. For ease of explanation below, terminal 11 is defined as platform terminal 11a and user terminal 11b. Platform terminal 11a is used by backend maintenance personnel to view application running data, while user terminal 11b is equipped with various application clients for users to access various services, etc.
[0054] Server 12 provides users with various business services or service support, including business server 12a, storage server 12b, etc. Business server 12a provides various services such as instant messaging, while storage server 12b provides data storage services and data support for other businesses. In this application, storage server 12b can be implemented using a distributed server.
[0055] In this application, when the terminal 11b equipped with a client detects that a target service has been triggered, such as when a user opens a service link URL (Uniform Resource Locator) sent by another user, or when a user clicks on a trigger component corresponding to another function in the application client, such as an interest group control in an instant messaging client, the terminal 11b obtains the service identifier of the target service and the homepage identifier of the homepage, and sends a page retrieval request to the service server. The page retrieval request carries the service identifier and the homepage identifier.
[0056] The service server 12a receives a page retrieval request from the client and retrieves the target service corresponding to the service identifier, such as... Figure 7a The container page shown retrieves the homepage structure data of the homepage based on the homepage identifier, and returns the container page and homepage structure data of the target service to the client.
[0057] The client receives the container page and homepage structure data of the target service returned by the service server, and displays the data as follows: Figure 7a The container page shown is rendered based on the homepage structure data. Figure 7b The homepage shown is the homepage page.
[0058] It should be noted that, Figure 1 The system scenario diagram shown is merely an example. The server and scenario described in this application embodiment are for the purpose of more clearly illustrating the technical solution of this application embodiment and do not constitute a limitation on the technical solution provided by this application embodiment. As those skilled in the art will know, with the evolution of the system and the emergence of new business scenarios, the technical solution provided by this application embodiment is also applicable to similar technical problems.
[0059] Figure 2 This is a flowchart illustrating the application page processing method provided in this application embodiment. Please refer to it. Figure 2 The application page processing method includes the following steps:
[0060] 201: When the client detects that the target service has been triggered, it obtains the service identifier of the target service and the homepage identifier of the homepage, and sends a page retrieval request to the service server. The page retrieval request carries the service identifier and the homepage identifier.
[0061] 202: The business server receives a page retrieval request from the client, retrieves the container page of the target business corresponding to the business identifier, retrieves the homepage structure data of the homepage page according to the homepage page identifier, and returns the container page and homepage structure data of the target business to the client.
[0062] 203: The client receives the container page and homepage structure data of the target service returned by the service server, displays the container page, renders the homepage based on the container page and the homepage structure data, and displays the homepage.
[0063] Through the execution of the above steps, when the client requests the homepage, the server sends the container page and the homepage structure data to the client. After receiving the container page, the client directly displays the container page instead of the waiting page and begins rendering the container page to obtain the homepage. For the user, this is a dynamic process in which the homepage appears slowly (e.g., 20 milliseconds). Compared to the existing technology where the client can only replace the waiting page after the homepage has been rendered, the user can see part of the homepage content (i.e., the content displayed on the container page) earlier (e.g., 20 milliseconds earlier), reducing the user's waiting time.
[0064] 204: The client determines whether a non-homepage page exists based on the container page. When a non-homepage page exists, the client sends a non-homepage page retrieval request to the business server. The non-homepage page retrieval request carries the non-homepage page identifier.
[0065] 205: The service server receives a request to obtain a non-homepage page from the client, obtains the non-homepage structure data of the non-homepage page according to the non-homepage page identifier, and sends the non-homepage structure data of the non-homepage page to the client.
[0066] 206: The client receives and stores the non-homepage structure data of the non-homepage page sent by the business server according to the non-homepage page identifier.
[0067] 207: When the client detects that the non-homepage page has been triggered, it renders and displays the non-homepage page based on the container page and the non-homepage structure data.
[0068] Through the execution of steps 204 to 207, the client completes the pre-storage of these page structure data when the user does not click on other pages of the service. After the user clicks, the corresponding non-homepage page can be directly rendered and displayed without the user having to wait for a long time to obtain the page structure data, but only a short rendering time.
[0069] The specific implementation of each step involved in this embodiment is described below.
[0070] This embodiment provides an application page processing method that innovatively introduces a container page for business functions. This container page includes some features of the application page. After receiving the container page, the client uses it to replace the waiting page, allowing users to see part of the application page content more quickly instead of a tedious waiting page. Furthermore, the pre-storage of these page structure data is completed before the user clicks on other pages, so that the page can be rendered and displayed directly after the user clicks, eliminating the need for the user to wait for a long time to obtain page structure data, but only requiring a short rendering time. That is, when displaying the homepage, this application can first display the container page that does not require much rendering, avoiding excessively long page display time. When the user switches application pages, this application can render directly without requiring the user to wait for page structure data, resulting in a better user experience and solving the technical problem of excessively long page display time in existing application page processing technologies.
[0071] exist Figure 2 Based on the description of the overall implementation of the application page processing method provided in this application within a communication system, the following is a further explanation in conjunction with the accompanying drawings. Figure 2 The specific details of each step are described.
[0072] Figure 3a This is a schematic flowchart illustrating a specific application page processing method provided in an embodiment of this application. It specifically demonstrates the implementation of this method on user terminal 11a (i.e., the client). Please refer to [link / reference]. Figure 3a The application page processing method includes the following steps:
[0073] 301: When the target service is detected to be triggered, obtain the service identifier of the target service and the homepage identifier of the homepage.
[0074] In one embodiment, this step is performed in one of the following ways: determining the service identifier and the homepage page identifier based on the clicked Uniform Resource Locator; or determining the service identifier and the homepage page identifier from the application configuration based on the clicked service function control. For example, when a user clicks on the URL of a certain service, it is determined that the target service has been triggered. In this case, the client directly uses the content corresponding to the URL of the service as the service identifier and the homepage page identifier. As another example, when a user clicks on the Interest Tribe control, the terminal uses the Interest Tribe identifier as the service identifier of the target service, and uses the page corresponding to the default open page of Interest Tribe configured in the client as the homepage page, using its page identifier as the homepage page identifier. The following will provide a detailed explanation based on specific scenarios.
[0075] 302: Send a page retrieval request to the business server, the page retrieval request carrying the business identifier and the homepage identifier.
[0076] 303: Receive the homepage structure data of the container page and homepage page of the target service returned by the service server.
[0077] 304: The container page is displayed.
[0078] 305: Based on the container page, the homepage page is rendered according to the homepage structure data.
[0079] In one embodiment, this step includes: obtaining the homepage floating frame page element of the container page; controlling the container page to write the homepage structure data into the homepage floating frame page element; and enabling the homepage floating frame page element to perform page rendering based on the homepage structure data to obtain the homepage page.
[0080] 306: Displays the aforementioned homepage.
[0081] Steps 301 to 306 above complete the loading of the homepage. Afterwards, other pages can be preloaded. Specifically, in one embodiment, after displaying the homepage, the following steps are included: determining whether a non-homepage page exists based on the container page; when a non-homepage page exists, sending a non-homepage page retrieval request to the business server, the request carrying the non-homepage page identifier; receiving and storing the non-homepage structure data sent by the business server based on the non-homepage page identifier; and when the non-homepage page is detected as being triggered, rendering and displaying the non-homepage page based on the container page and the non-homepage structure data.
[0082] In one embodiment, the step of rendering and displaying a non-homepage page based on the container page and the non-homepage structure data includes: controlling the container page to dynamically create a non-homepage floating frame page element; controlling the container page to write the non-homepage structure data into the non-homepage floating frame page element; enabling the non-homepage floating frame page element to render the page according to the non-homepage structure data to obtain the non-homepage page; and controlling the container page to set other pages to hidden and set the non-homepage page to visible.
[0083] In one embodiment, before the step of sending a non-homepage page retrieval request to the business server, the method further includes: determining the number of non-homepage pages; if the number of pages is less than a threshold, directly sending a non-homepage page retrieval request to the business server; if the number of pages is greater than the threshold, sending a non-homepage page retrieval request corresponding to each non-homepage page to the business server according to a preset method. For example, if the threshold is 1.5, if there is only one non-homepage page, a single AJAX element can be used to retrieve the page structure data of that page; if there are at least two non-homepage pages, a corresponding number of AJAX elements can be used to retrieve the page structure data of these pages in parallel or sequentially.
[0084] By executing these steps, the client can pre-store the page structure data before the user clicks on other pages of the service. Once the user clicks, the page can be rendered and displayed directly without requiring the user to wait for a long time to retrieve the page structure data. Instead, the user only needs to wait for a short rendering time.
[0085] Figure 3b This is another specific flowchart illustrating the application page processing method provided in this application embodiment, specifically demonstrating the implementation of the method in the business server 12a. Please refer to [link / reference]. Figure 3b The application page processing method includes the following steps:
[0086] 311: Receive a page retrieval request from the client, the page retrieval request carrying a business identifier and a homepage identifier.
[0087] In one embodiment, prior to this step, the method further includes: obtaining all application pages included in the target service; constructing the container page based on all service pages, wherein the container page includes at least the common page parameters of all application pages of the target service.
[0088] In one embodiment, after the step of constructing the container page, the method further includes: obtaining page structure data corresponding to each application page based on the page data of each application page and the page data of the container page.
[0089] 312: Obtain the container page of the target service corresponding to the service identifier.
[0090] 313: Obtain the homepage structure data of the homepage based on the homepage identifier.
[0091] In one embodiment, this step includes: checking whether corresponding page structure data exists based on the homepage identifier of the homepage page; if it exists, using the found page structure data as the homepage structure data; if it does not exist, obtaining the homepage structure data of the homepage page based on the page data of the homepage page and the page data of the container page. In the business server, the page structure data of the page can be pre-stored based on the page identifier, or it can be obtained in real time, as will be explained in detail below.
[0092] 314: Return the homepage structure data of the container page and homepage of the target service to the client.
[0093] The above steps complete the sending of the container page and homepage structure data, allowing the client to display the relevant content of the homepage relatively quickly.
[0094] To enable the client to pre-store other pages, in one embodiment, after the step of returning the container page and homepage structure data of the target service to the client, the method further includes: receiving a non-homepage page acquisition request from the client, the non-homepage page acquisition request carrying the non-homepage page identifier; acquiring the non-homepage structure data of the non-homepage page; and sending the non-homepage structure data of the non-homepage page to the client.
[0095] Based on this step, the server has completed the pre-sending of other page structure data. In subsequent processes, the client and server no longer need to communicate on page structure data, thus reducing the network burden.
[0096] exist Figures 3a to 3b Based on the illustrated embodiment, multiple pages are grouped together into a single container page with only minimal necessary modifications to the existing pages. This container page facilitates cross-linking and improves user conversion rates. The loading speed of the homepage remains consistent with existing technologies, without affecting user retention rates, and may even allow for earlier display of some homepage content. Asynchronous loading of non-homepage pages significantly reduces white screen time during transitions, further enhancing user retention.
[0097] In some scenarios, all business-related pages in this application are rendered using iframes (floating frames, where an iframe element creates an inline frame containing another page). When a user opens a business page, the server requests the container page (containing only elements related to page switching) and the homepage structure data. The server can pre-request the HTML structure data of the homepage (hereinafter referred to as sphtml, which does not include the structure data of the container page) via methods such as AJAX (Asynchronous JavaScript and XML, a web development technique for creating interactive, fast, and dynamic web applications that can update parts of a webpage without reloading the entire page) and return it to the browser. After receiving the response, the terminal browser retrieves the sphtml of the homepage and renders it using an iframe. Specifically, the container page can obtain its own iframe element and then render it using ifr.contentWindow.document.write(sphtml) or ifr.contentDocument.write(sphtml). `te(sphtml)` writes the sphtml to the iframe, and then the browser starts rendering the page itself. After the homepage is rendered and loaded, the terminal requests the sphtml of non-homepage pages from the server via AJAX or other methods and caches them. When the user switches pages, an iframe element is dynamically created within the container page, and then the sphtml is written to the iframe for rendering using `ifr.contentWindow.document.write(sphtml)` or `ifr.contentDocument.write(sphtml)`. At the same time, other pages are hidden, and the iframe is set to be visible. This process is very fast and greatly reduces the white screen time when switching.
[0098] Now combined Figures 4a to 4c The present application and the prior art are explained and illustrated with specific application scenarios to clarify the technological progress and significant effects of the present application.
[0099] In this scenario, another user sends a service URL to the current user: https: / / ...com / ... / yellow?...; the user clicks this URL to access the corresponding service. The pages involved in this scenario include: Figure 7a The container page shown Figure 7b The premium membership page shown Figure 7c The member page shown Figure 7d The Yellow Diamond page shown Figure 7eThe waiting page shown (in actual applications, this page is a blank page).
[0100] When a user activates this service, the existing technology process is as follows: Figure 4a As shown, it includes the following steps:
[0101] 401 to 402: The client requests the homepage structure data from the business server and completes the homepage rendering and display.
[0102] See Figure 4c At time t0, the user clicks the URL to enter the service interface, and steps 401 and 402 are executed to obtain the homepage structure data. At this time, the time enters time t1, and then the homepage is rendered. After rendering is completed, the time enters time t2, and the display begins. Figure 7b The premium membership page shown is displayed on the client side continuously from time t0 to t2, for example, within 320 milliseconds. Figure 7e The waiting page shown.
[0103] 403 to 404: The client requests the first non-homepage structure data from the business server and completes the rendering and display of the non-homepage.
[0104] See Figure 4c At time t3, the user clicks Figure 7b The member control on the page requested access to the member page. Steps 403 and 404 were executed to obtain the first non-homepage structure data, at which point time t5 was reached. Then, the non-homepage was rendered, and after rendering was completed, time t6 was reached, at which point the page began to be displayed. Figure 7c The member page shown is displayed on the client continuously from time t3 to t6, for example, within 320 milliseconds. Figure 7e The waiting page shown.
[0105] 405 to 406: The client requests the second non-homepage structure data from the business server and completes the rendering and display of the non-homepage.
[0106] See Figure 4c At time t7, the user clicks Figure 7c The Yellow Diamond control on the page requested access to the Yellow Diamond page. Steps 405 and 406 were executed to obtain the second non-homepage structure data. At this point, time entered time t9, and then the non-homepage was rendered. After rendering was completed, time entered time t10, and the display began. Figure 7d The Yellow Diamond page shown is displayed on the client continuously during the time interval t7 to t10, for example, within 320 milliseconds. Figure 7e The waiting page shown.
[0107] Based on the above description, it can be seen that users need to wait approximately 320 milliseconds when switching pages.
[0108] When a user activates this service, the application process is as follows: Figure 4b As shown, it includes the following steps:
[0109] 411 to 412: The client requests the homepage structure data from the business server and completes the homepage rendering and display.
[0110] See Figure 4c At time t0, if the user clicks the URL to enter the interface of this service, steps 411 and 412 are executed to complete the container page and homepage structure data (this data is different from the data in step 402). Figure 4b The data in step 402 (referred to as difference data, lacking some container page data compared to the data in step 402) is acquired. At this point, time t1 is entered, and then the homepage is rendered. After rendering is complete, time t2 is entered, at which point the display begins. Figure 7b The premium membership page shown is displayed on the client side within 300 milliseconds, from time t0 to t1. Figure 7e The waiting page shown is displayed by the client within 20 milliseconds, from time t1 to t2. Figure 7a The container page shown.
[0111] 413 to 416: When the client displays the homepage, the backend obtains the page structure data of other non-homepage pages (this data does not include the structure data corresponding to the container page, reducing the transmission of duplicate data). This process lasts for about 600 milliseconds. Since the client is displaying the homepage, the user is unaware of this data acquisition process.
[0112] Based on this, the rendering and display of other pages can be completed.
[0113] See Figure 4c At time t3, the user clicks Figure 7b The member control on the page shown requests access to the member page. At this point, the client directly renders the member page, and the time reaches t4, at which point the display begins. Figure 7c The member page shown is displayed on the client continuously during the time interval t3 to t4, for example, within 20 milliseconds. Figure 7a The container page shown.
[0114] See Figure 4c At time t7, the user clicks Figure 7c The Yellow Diamond control on the page shown requests access to the Yellow Diamond page. At this point, the client directly renders the Yellow Diamond page. After rendering is complete, time t8 is entered, and the display begins. Figure 7d The Yellow Diamond page shown is displayed on the client continuously during time t7 to t8, for example, within 20 milliseconds. Figure 7a The container page shown.
[0115] Based on the above description, users only need to wait about 20 milliseconds when switching pages.
[0116] To implement the above method, this application also provides a corresponding application page processing device, which will now be described in conjunction with the accompanying drawings.
[0117] Correspondingly, Figure 5a This is a schematic diagram of an application page processing device provided in an embodiment of this application, which specifically illustrates the implementation of the device on the client side. Please refer to [link / reference]. Figure 5a The application page processing device includes the following modules:
[0118] The first acquisition module 501 is used to acquire the service identifier of the target service and the homepage identifier of the homepage when the target service is detected to be triggered.
[0119] The first sending module 502 is used to send a page retrieval request to the business server, the page retrieval request carrying the business identifier and the homepage identifier;
[0120] The first receiving module 503 is used to receive the homepage structure data of the container page and homepage page of the target service returned by the service server;
[0121] Display module 504 is used to display the container page;
[0122] Rendering module 505 is used to render a homepage based on the container page and the homepage structure data.
[0123] The display module 504 is also used to display the homepage.
[0124] In one embodiment, the rendering module 505 is specifically configured to: obtain the homepage floating frame page element of the container page; control the container page to write the homepage structure data into the homepage floating frame page element; and enable the homepage floating frame page element to perform page rendering according to the homepage structure data to obtain the homepage page.
[0125] In one embodiment, the first acquisition module 501 is specifically used to implement one of the following methods: determining the business identifier and the homepage identifier based on the clicked Uniform Resource Locator; or determining the business identifier and the homepage identifier from the application configuration based on the clicked business function control.
[0126] In one embodiment, after displaying the homepage, the display module 504 is further configured to: determine whether a non-homepage exists based on the container page; when a non-homepage exists, trigger the first sending module 502 to send a non-homepage retrieval request to the business server, the non-homepage retrieval request carrying the non-homepage identifier; trigger the first receiving module 503 to receive and store the non-homepage structure data of the non-homepage sent by the business server based on the non-homepage identifier; and when the non-homepage is detected to be triggered, trigger the rendering module 505 to render the non-homepage based on the container page and the non-homepage structure data, and display the non-homepage.
[0127] In one embodiment, the display module 504 is specifically configured to: control the container page to dynamically create a non-homepage floating frame page element; control the container page to write the non-homepage structure data into the non-homepage floating frame page element; enable the non-homepage floating frame page element to perform page rendering based on the non-homepage structure data to obtain the non-homepage page; and control the container page to set other pages to hidden and set the non-homepage page to visible.
[0128] In one embodiment, before sending a non-homepage page retrieval request to the service server, the first sending module 502 is further configured to: determine the number of non-homepage pages; if the number of pages is less than a threshold, directly send a non-homepage page retrieval request to the service server; if the number of pages is greater than the threshold, send a non-homepage page retrieval request corresponding to each non-homepage page to the service server according to a preset method.
[0129] Correspondingly, Figure 5b This is another structural diagram of the application page processing device provided in the embodiments of this application, which specifically illustrates the embodiment of the device of this application in the business server. Please refer to [link / reference]. Figure 5b The application page processing device includes the following modules:
[0130] The second receiving module 511 is used to receive a page acquisition request from the client, wherein the page acquisition request carries a service identifier and a homepage identifier;
[0131] The second acquisition module 512 is used to acquire the container page of the target service corresponding to the service identifier;
[0132] The third acquisition module 513 is used to acquire the homepage structure data of the homepage based on the homepage identifier;
[0133] The second sending module 514 is used to return the homepage structure data of the container page and homepage page of the target service to the client.
[0134] In one embodiment, such as Figure 5b As shown, the device further includes: a processing module 515, configured to obtain all application pages included in the target service before receiving a page retrieval request from the client; and to construct the container page based on all the service pages, wherein the container page includes at least the common page parameters of all application pages of the target service.
[0135] In one embodiment, after constructing the container page, the processing module 515 is further configured to: obtain page structure data corresponding to each application page based on the page data of each application page and the page data of the container page.
[0136] In one embodiment, the third acquisition module 513 is specifically used to: search for whether there is corresponding page structure data based on the homepage identifier of the homepage page; if it exists, use the found page structure data as the homepage structure data; if it does not exist, obtain the homepage structure data of the homepage page based on the page data of the homepage page and the page data of the container page.
[0137] In one embodiment, the second receiving module 511 is further configured to: receive a non-homepage page acquisition request from the client, the non-homepage page acquisition request carrying the non-homepage page identifier; the third acquisition module 513 is further configured to: acquire the non-homepage structure data of the non-homepage page; and the second sending module 514 is further configured to: send the non-homepage structure data of the non-homepage page to the client.
[0138] Accordingly, this application also provides a computer device, which includes a server or terminal (with a client installed), to implement the application page processing device in any of the above embodiments.
[0139] like Figure 6 As shown, the computer device may include a radio frequency (RF) circuit 601, a memory 602 including one or more computer-readable storage media, an input unit 603, a display unit 604, a sensor 605, an audio circuit 606, a wireless Fidelity (WiFi) module 607, a processor 608 including one or more processing cores, and a power supply 609, among other components. Those skilled in the art will understand that... Figure 6 The computer device structure shown does not constitute a limitation on the computer device and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein:
[0140] RF circuit 601 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and hands it over to one or more processors 608 for processing; additionally, it transmits uplink data to the base station. Memory 602 can be used to store software programs and modules. Processor 608 executes various functional applications and data processing by running the software programs and modules stored in memory 602. Input unit 603 can be used to receive input digital or character information and generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control.
[0141] The display unit 604 can be used to display information input by the user or information provided to the user, as well as various graphical user interfaces of computer devices, which can be composed of graphics, text, icons, videos, and any combination thereof.
[0142] The computer device may also include at least one sensor 605, such as a light sensor, a motion sensor, and other sensors. Audio circuitry 606 includes a speaker and a microphone that provide an audio interface between the user and the computer device.
[0143] WiFi is a short-range wireless transmission technology. Computer devices using the WiFi module 607 can help users send and receive emails, browse web pages, and access streaming media, providing users with wireless broadband internet access. Although Figure 6 WiFi module 607 is shown, but it is understood that it is not a necessary component of computer equipment and can be omitted as needed without changing the nature of the application.
[0144] The processor 608 is the control center of the computer device. It connects various parts of the mobile phone through various interfaces and lines. By running or executing software programs and / or modules stored in the memory 602, and calling data stored in the memory 602, it performs various functions of the computer device and processes data, thereby monitoring the mobile phone as a whole.
[0145] The computer device also includes a power supply 609 (such as a battery) that supplies power to various components. Preferably, the power supply can be logically connected to the processor 608 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.
[0146] Although not shown, the computer device may also include a camera, Bluetooth module, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 608 in the computer device loads the executable files corresponding to the processes of one or more applications into the memory 602 according to the following instructions, and the processor 608 runs the applications stored in the memory 602 to achieve the following functions:
[0147] When a target service is detected to be triggered, the service identifier of the target service and the homepage identifier of the homepage are obtained.
[0148] Send a page retrieval request to the business server, the page retrieval request carrying the business identifier and the homepage identifier;
[0149] Receive the homepage structure data of the container page and homepage page of the target service returned by the service server;
[0150] Display the container page;
[0151] Based on the container page, the homepage page is rendered according to the homepage structure data;
[0152] The homepage is displayed.
[0153] Or achieve the following functionality:
[0154] Receive a page retrieval request from the client, the page retrieval request carrying a business identifier and a homepage identifier;
[0155] Obtain the container page of the target service corresponding to the service identifier;
[0156] Obtain the homepage structure data of the homepage;
[0157] Return the container page and homepage structure data of the target service to the client.
[0158] Or achieve the following functionality:
[0159] When the client detects that the target service has been triggered, it obtains the service identifier of the target service and the homepage identifier of the homepage, and sends a page retrieval request to the service server. The page retrieval request carries the service identifier and the homepage identifier.
[0160] The service server receives a page retrieval request from the client, retrieves the container page of the target service corresponding to the service identifier, retrieves the homepage structure data of the homepage, and returns the container page and homepage structure data of the target service to the client.
[0161] The client receives the container page and homepage structure data of the target service returned by the service server, displays the container page, renders the homepage based on the container page and the homepage structure data, and displays the homepage.
[0162] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the detailed description above, and they will not be repeated here.
[0163] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.
[0164] Therefore, embodiments of this application provide a computer-readable storage medium storing a plurality of instructions that can be loaded by a processor to perform the following functions:
[0165] When a target service is detected to be triggered, the service identifier of the target service and the homepage identifier of the homepage are obtained.
[0166] Send a page retrieval request to the business server, the page retrieval request carrying the business identifier and the homepage identifier;
[0167] Receive the homepage structure data of the container page and homepage page of the target service returned by the service server;
[0168] Display the container page;
[0169] Based on the container page, the homepage page is rendered according to the homepage structure data;
[0170] The homepage is displayed.
[0171] Or achieve the following functionality:
[0172] Receive a page retrieval request from the client, the page retrieval request carrying a business identifier and a homepage identifier;
[0173] Obtain the container page of the target service corresponding to the service identifier;
[0174] Obtain the homepage structure data of the homepage;
[0175] Return the container page and homepage structure data of the target service to the client.
[0176] Or achieve the following functionality:
[0177] When the client detects that the target service has been triggered, it obtains the service identifier of the target service and the homepage identifier of the homepage, and sends a page retrieval request to the service server. The page retrieval request carries the service identifier and the homepage identifier.
[0178] The service server receives a page retrieval request from the client, retrieves the container page of the target service corresponding to the service identifier, retrieves the homepage structure data of the homepage, and returns the container page and homepage structure data of the target service to the client.
[0179] The client receives the container page and homepage structure data of the target service returned by the service server, displays the container page, renders the homepage based on the container page and the homepage structure data, and displays the homepage.
[0180] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.
[0181] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.
[0182] Since the instructions stored in the storage medium can execute the steps of any of the methods provided in the embodiments of this application, the beneficial effects that any of the methods provided in the embodiments of this application can achieve can be realized, as detailed in the preceding embodiments, and will not be repeated here.
[0183] Therefore, embodiments of this application provide a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various optional implementations described above. For example, the following functions are implemented:
[0184] When a target service is detected to be triggered, the service identifier of the target service and the homepage identifier of the homepage are obtained.
[0185] Send a page retrieval request to the business server, the page retrieval request carrying the business identifier and the homepage identifier;
[0186] Receive the homepage structure data of the container page and homepage page of the target service returned by the service server;
[0187] Display the container page;
[0188] Based on the container page, the homepage page is rendered according to the homepage structure data;
[0189] The homepage is displayed.
[0190] Or achieve the following functionality:
[0191] Receive a page retrieval request from the client, the page retrieval request carrying a business identifier and a homepage identifier;
[0192] Obtain the container page of the target service corresponding to the service identifier;
[0193] Obtain the homepage structure data of the homepage;
[0194] Return the container page and homepage structure data of the target service to the client.
[0195] Or achieve the following functionality:
[0196] When the client detects that the target service has been triggered, it obtains the service identifier of the target service and the homepage identifier of the homepage, and sends a page retrieval request to the service server. The page retrieval request carries the service identifier and the homepage identifier.
[0197] The service server receives a page retrieval request from the client, retrieves the container page of the target service corresponding to the service identifier, retrieves the homepage structure data of the homepage, and returns the container page and homepage structure data of the target service to the client.
[0198] The client receives the container page and homepage structure data of the target service returned by the service server, displays the container page, renders the homepage based on the container page and the homepage structure data, and displays the homepage.
[0199] The above provides a detailed description of an application page processing method and apparatus provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.
Claims
1. An application page processing method, characterized in that, Applied to the client side, including: When a target service is detected to be triggered, the service identifier of the target service and the homepage identifier of the homepage are obtained. Send a page retrieval request to the business server, the page retrieval request carrying the business identifier and the homepage identifier; Receive the homepage structure data of the container page and homepage page of the target service returned by the service server, wherein the container page includes at least the common page parameters of all application pages of the target service; Display the container page; Retrieve the homepage floating frame element of the container page; Control the container page to write the homepage structure data into the homepage floating frame page element; Enable the homepage floating frame page elements to render the page according to the homepage structure data to obtain the homepage page; Display the homepage; When a non-homepage page is detected as being triggered, the container page is controlled to dynamically create a non-homepage floating frame page element; Control the container page to write the non-homepage structure data of the non-homepage page into the non-homepage floating frame page element; Enable the non-homepage floating frame page elements to render the page based on the non-homepage structure data to obtain the non-homepage page; The container page is controlled to hide other pages and make the non-homepage pages visible, so as to display the non-homepage pages.
2. The application page processing method according to claim 1, characterized in that, The step of obtaining the business identifier of the target service and the homepage identifier of the homepage includes one of the following methods: Based on the clicked Uniform Resource Locator, determine the business identifier and the homepage identifier; Alternatively, the business identifier and the homepage identifier can be determined from the application configuration based on the clicked business function control.
3. The application page processing method according to any one of claims 1 to 2, characterized in that, Following the step of displaying the homepage, the method further includes: Determine whether a non-homepage page exists based on the container page; When a non-homepage page exists, a non-homepage page retrieval request is sent to the business server. The non-homepage page retrieval request carries the non-homepage page identifier of the non-homepage page. Receive and store the non-homepage structure data of the non-homepage page sent by the business server according to the non-homepage page identifier.
4. The application page processing method according to claim 3, characterized in that, Before the step of sending a non-homepage page retrieval request to the business server, the method further includes: Determine the number of non-homepage pages; If the number of pages is less than the threshold, a request to retrieve non-homepage pages is sent directly to the business server. If the number of pages exceeds the threshold, a request to retrieve the non-homepage page corresponding to each non-homepage page is sent to the business server according to a preset method.
5. An application page processing method, characterized in that, Applied to business servers, including: Receive a page retrieval request from the client, the page retrieval request carrying a business identifier and a homepage identifier; Obtain the container page of the target business corresponding to the business identifier, wherein the container page includes at least the common page parameters of all application pages of the target business; Obtain the homepage structure data of the homepage based on the homepage identifier; The system returns the homepage structure data of the container page and homepage page of the target service to the client, so that the client can display the container page; obtains the homepage floating frame page element of the container page; controls the container page to write the homepage structure data into the homepage floating frame page element; enables the homepage floating frame page element to perform page rendering based on the homepage structure data to obtain the homepage page; displays the homepage page; when a non-homepage page is detected to be triggered, controls the container page to dynamically create a non-homepage floating frame page element; controls the container page to write the non-homepage structure data of the non-homepage page into the non-homepage floating frame page element; enables the non-homepage floating frame page element to perform page rendering based on the non-homepage structure data to obtain the non-homepage page; controls the container page to set other pages to hidden and set the non-homepage page to visible, so as to display the non-homepage page.
6. The application page processing method according to claim 5, characterized in that, Before the step of receiving a page retrieval request from the client, the method further includes: Obtain all application pages included in the target service; Based on all the application pages, construct the container page.
7. The application page processing method according to claim 6, characterized in that, Following the step of constructing the container page, the method further includes: Based on the page data of each application page and the page data of the container page, the page structure data corresponding to each application page is obtained.
8. The application page processing method according to claim 5, characterized in that, The step of obtaining the homepage structure data of the homepage includes: Based on the homepage identifier of the homepage, check if there is corresponding page structure data; If it exists, the found page structure data will be used as the homepage structure data; If it does not exist, the homepage structure data of the homepage is obtained based on the page data of the homepage and the page data of the container page.
9. The application page processing method according to any one of claims 5 to 8, characterized in that, After the step of returning the container page and homepage structure data of the target service to the client, the method further includes: Receive a non-homepage page retrieval request from the client, the non-homepage page retrieval request carrying a non-homepage page identifier; Obtain the non-homepage structure data of the non-homepage page based on the non-homepage page identifier; Send the non-homepage structure data of the non-homepage page to the client.
10. An application page processing method, characterized in that, include: When the client detects that the target service has been triggered, it obtains the service identifier of the target service and the homepage identifier of the homepage, and sends a page retrieval request to the service server. The page retrieval request carries the service identifier and the homepage identifier. The business server receives a page retrieval request from the client, retrieves the container page of the target business corresponding to the business identifier, retrieves the homepage structure data of the homepage page according to the homepage page identifier, and returns the container page and homepage structure data of the target business to the client. The container page includes at least the common page parameters of all application pages of the target business. The client receives the homepage structure data of the container page and homepage page of the target service returned by the service server, displays the container page, obtains the homepage floating frame page element of the container page, and controls the container page to write the homepage structure data into the homepage floating frame page element; Enable the homepage floating frame page element to render the page according to the homepage structure data to obtain the homepage page; display the homepage page; when a non-homepage page is detected to be triggered, control the container page to dynamically create a non-homepage floating frame page element; control the container page to write the non-homepage structure data of the non-homepage page into the non-homepage floating frame page element; Enable the non-homepage floating frame page element to render the page according to the non-homepage structure data to obtain the non-homepage page; control the container page to set other pages to hidden and set the non-homepage page to visible in order to display the non-homepage page.
11. The application page processing method according to claim 10, characterized in that, Also includes: The client determines whether there is a non-homepage page based on the container page. When a non-homepage page exists, it sends a non-homepage page retrieval request to the business server. The non-homepage page retrieval request carries the non-homepage page identifier of the non-homepage page. The service server receives a non-homepage page retrieval request from the client, retrieves the non-homepage structure data of the non-homepage page according to the non-homepage page identifier, and sends the non-homepage structure data of the non-homepage page to the client. The client receives and stores the non-homepage structure data of the non-homepage page sent by the business server according to the non-homepage page identifier.
12. An application page processing device, characterized in that, Applied to the client side, including: The first acquisition module is used to acquire the service identifier of the target service and the homepage identifier of the homepage when the target service is detected to be triggered. The first sending module is used to send a page retrieval request to the business server, the page retrieval request carrying the business identifier and the homepage identifier; The first receiving module is used to receive the homepage structure data of the container page and homepage page of the target service returned by the service server. The container page includes at least the common page parameters of all application pages of the target service. The display module is used to display the container page; The rendering module is used to obtain the homepage floating frame page element of the container page; control the container page to write the homepage structure data into the homepage floating frame page element; and enable the homepage floating frame page element to perform page rendering according to the homepage structure data to obtain the homepage page. The display module is also used to display the homepage page; when a non-homepage page is detected to be triggered, it controls the container page to dynamically create a non-homepage floating frame page element; it controls the container page to write the non-homepage structure data of the non-homepage page into the non-homepage floating frame page element; it enables the non-homepage floating frame page element to perform page rendering based on the non-homepage structure data to obtain the non-homepage page; and it controls the container page to set other pages to hidden and set the non-homepage page to visible in order to display the non-homepage page.
13. An application page processing device, characterized in that, Applied to business servers, including: The second receiving module is used to receive a page retrieval request from the client, the page retrieval request carrying a business identifier and a homepage identifier; The second acquisition module is used to acquire the container page of the target business corresponding to the business identifier, wherein the container page includes at least the common page parameters of all application pages of the target business; The third acquisition module is used to acquire the homepage structure data of the homepage based on the homepage identifier; The second sending module is used to return the homepage structure data of the container page and homepage page of the target service to the client, so that the client can display the container page; obtain the homepage floating frame page element of the container page; control the container page to write the homepage structure data into the homepage floating frame page element; enable the homepage floating frame page element to perform page rendering according to the homepage structure data to obtain the homepage page; display the homepage page; when a non-homepage page is detected to be triggered, control the container page to dynamically create a non-homepage floating frame page element; control the container page to write the non-homepage structure data of the non-homepage page into the non-homepage floating frame page element; enable the non-homepage floating frame page element to perform page rendering according to the non-homepage structure data to obtain the non-homepage page; control the container page to set other pages to hidden and set the non-homepage page to visible, so as to display the non-homepage page.
Citation Information
Patent Citations
Page display method and apparatus, and electronic device
CN107066631A
Page processing method and device, computer device and storage medium
CN110442811A