A page generation method and device, a terminal, a server, and a storage medium
By working collaboratively between the client and server, and adjusting page configurations using feedback from historical pages, the problem of frequent releases caused by changes in APP business requirements was solved, enabling flexible page generation and high-quality target page generation.
Patent Information
- Application Number
- CN202211368751.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-11-03
- Publication Date
- 2026-02-17
- Estimated Expiration
- 2042-11-03
AI Technical Summary
In existing technologies, changes in the business requirements of applications (APPs) lead to frequent releases, resulting in compressed development and testing time and making it difficult to guarantee the quality of the final product.
By working collaboratively between the client and server, and utilizing feedback from historical pages to adjust page configurations and generate target pages, the frequency of releases can be reduced, thereby improving the flexibility and robustness of business function iterations.
When business requirements change, only the configuration needs to be modified to generate target pages that match user preferences, reducing the release frequency and improving the flexibility and quality of page generation.
Smart Images

Figure CN115600031B_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present invention relate to the field of page processing technology, and in particular to a page generation method, apparatus, terminal, server and storage medium. Background Technology
[0002] Currently, products in many fields are facing frequent changes in business requirements.
[0003] For applications (APPs) used to implement product-related functions, when the product's business requirements change, the relevant pages in the APP will usually also change. Currently, the main way to generate the changed relevant pages is through release (i.e., releasing a new version of the APP).
[0004] However, frequent releases can compress development and testing time on each platform, making it difficult to guarantee quality after deployment. This issue needs to be addressed. Summary of the Invention
[0005] This invention provides a page generation method, apparatus, terminal, server, and storage medium to reduce the release frequency.
[0006] In a first aspect, embodiments of the present invention provide a page generation method, applied in a client, the method comprising:
[0007] In response to the page generation instruction, a page configuration request is sent to the server, wherein the page configuration request is used to request the page configuration of the target page to be generated;
[0008] The server receives the page configuration returned in response to the page configuration request. The page configuration is obtained by adjusting the historical configuration through feedback information associated with the historical page. The historical page corresponds to the target page and is generated based on the historical configuration before the target page is generated.
[0009] Based on the page configuration, the target component to be displayed and the display content to be displayed in the target component are determined from the candidate components. The display content is then assembled into the target component, and the target page is generated based on the assembled target component.
[0010] Secondly, embodiments of the present invention also provide a page generation method, applied in a server, the method comprising:
[0011] In response to a configuration adjustment command, a page configuration is obtained, wherein the page configuration is obtained by adjusting a historical configuration based on feedback information of a historical page, and the historical page is generated based on the historical configuration;
[0012] Receive a page configuration request sent by the client, wherein the page configuration request is used to request the page configuration of the target page to be generated corresponding to the historical page;
[0013] In response to the page configuration request, the page configuration is returned to the client, so that the client determines the target component to be displayed from each candidate component and the display content to be displayed in the target component according to the received page configuration, assembles the display content into the target component, and renders the assembled target component to generate the target page.
[0014] Thirdly, embodiments of the present invention also provide a page generation device configured in a client, the device comprising:
[0015] The page configuration request sending module is used to send a page configuration request to the server in response to the page generation instruction, wherein the page configuration request is used to request the page configuration of the target page to be generated;
[0016] A page configuration receiving module is used to receive the page configuration returned by the server in response to the page configuration request. The page configuration is obtained by adjusting the historical configuration through feedback information associated with the historical page. The historical page corresponds to the target page and is generated based on the historical configuration before the target page is generated.
[0017] The target page generation module is used to determine the target component to be displayed from each candidate component according to the page configuration, as well as the display content to be displayed in the target component, and to assemble the display content into the target component, and to render the target page based on the assembled target component.
[0018] Fourthly, embodiments of the present invention also provide a page generation device configured in a server, the device comprising:
[0019] A page configuration acquisition module is used to obtain page configuration in response to configuration adjustment instructions, wherein the page configuration is obtained by adjusting historical configurations based on feedback information of historical pages, and the historical pages are generated based on the historical configurations;
[0020] A page configuration request receiving module is used to receive a page configuration request sent by a client, wherein the page configuration request is used to request the page configuration of the target page to be generated corresponding to the historical page;
[0021] The page configuration return module is used to respond to the page configuration request and return the page configuration to the client, so that the client can determine the target component to be displayed from each candidate component and the display content to be displayed in the target component according to the received page configuration, assemble the display content into the target component, and render based on the assembled target component to generate the target page.
[0022] Fifthly, embodiments of the present invention also provide a terminal, the terminal comprising:
[0023] One or more processors;
[0024] A memory for storing one or more programs that, when executed by one or more processors, enable the one or more processors to implement a page generation method executed by a client as described in any embodiment of the present invention.
[0025] Sixthly, embodiments of the present invention also provide a server, the server comprising:
[0026] One or more processors;
[0027] A memory for storing one or more programs, which, when executed by one or more processors, enable the one or more processors to implement a page generation method executed by a server as described in any embodiment of the present invention.
[0028] In a seventh aspect, embodiments of the present invention also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a page generation method executed by a client or a server as described in any embodiment of the present invention.
[0029] In response to a page generation command, this embodiment of the invention sends a page configuration request to a server. The page configuration request requests the page configuration of the target page to be generated. The system receives the page configuration returned by the server in response to the request. This page configuration is obtained by adjusting historical configurations based on feedback information associated with historical pages. The historical pages correspond to the target page and are generated based on the historical configurations before the target page is generated. Based on the page configuration, the system determines the target component to be displayed from among the candidate components, along with the display content to be displayed within the target component. The display content is then assembled into the target component, and rendering is performed based on the assembled target component to generate the target page. This technical solution of the present invention achieves page generation through configuration. This means that when business requirements change, only the configuration needs to be modified, without requiring a new release. This improves the flexibility and robustness of client-side business function iteration while reducing the release frequency. Furthermore, since the final application's page configuration is obtained by adjusting historical configurations based on feedback information, it is more closely matched to user preferences, thus generating a target page that better matches user preferences. Attached Figure Description
[0030] Figure 1 This is a flowchart of a page generation method provided in Embodiment 1 of the present invention;
[0031] Figure 2 This is a flowchart of a page generation method provided in Embodiment 2 of the present invention;
[0032] Figure 3 This is a flowchart of an optional example of a page generation method provided in Embodiment 2 of the present invention;
[0033] Figure 4 This is a structural block diagram of the page generation device provided in Embodiment 3 of the present invention;
[0034] Figure 5 This is a structural block diagram of the page generation device provided in Embodiment 4 of the present invention;
[0035] Figure 6 This is a schematic diagram of the structure of a terminal provided in Embodiment 5 of the present invention. Detailed Implementation
[0036] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the invention and not the entire structure.
[0037] It should be noted that the acquisition, storage, use, and processing of data in the technical solution of this application all comply with the relevant provisions of national laws and regulations.
[0038] Example 1
[0039] Figure 1 This is a flowchart of a page generation method according to Embodiment 1 of the present invention. The page generation method provided in this embodiment is executed by a client, such as a mobile phone or tablet computer, and is applicable to situations requiring page generation, especially those with flexible page generation requirements. Specifically, this method can be executed by a page generation device, which can be implemented in software and / or hardware, and can be integrated into the terminal.
[0040] See Figure 1 The specific methods implemented in this way include:
[0041] S110. In response to the page generation instruction, a page configuration request is sent to the server, wherein the page configuration request is used to request the page configuration of the target page to be generated.
[0042] In this context, a page generation instruction can be understood as an instruction to generate the target page. A page generation instruction can be a direct instruction to generate the target page; it can also be other instructions that require generating the target page. For example, a page open instruction generated when opening a target page in an app can also serve as a page generation instruction to generate the target page. Similarly, a client launch instruction generated when starting an app can also serve as a page generation instruction to generate the target page within the app. The target page can be understood as the page currently required to be generated. Page configuration can be used to represent the page content within the target page. A page configuration request can be understood as a request for the server to return the page configuration.
[0043] It should be noted that in this embodiment of the invention, in response to the page generation instruction, the client does not directly request the server to generate and return the target page, but instead requests the server to return the page configuration of the target page. The client then generates the target page based on the page configuration, thereby reducing the computational burden on the server.
[0044] S120. Receive the page configuration returned by the server in response to the page configuration request. The page configuration is obtained by adjusting the historical configuration through feedback information associated with the historical page. The historical page corresponds to the target page and is generated based on the historical configuration before the target page is generated.
[0045] In this context, "historical pages" can be understood as pages generated in the past that correspond to the target page; that is, pages generated before the target page that are substantially identical to it. For example, a historical page might be a product details page generated two days ago, while the target page is a product details page generated today. Historical configurations can be used to represent the content of pages within historical pages. "Feedback information" can be understood as information provided by users regarding historical pages, indicating their interest in those pages. This information can be provided directly by the user or indirectly obtained based on user-authorized information; no specific limitations are imposed here. Feedback information can be associated with the historical page most recent to the current time, or it can be associated with all historical pages; no specific limitations are imposed here.
[0046] It is understandable that the client may have generated historical pages before the current target page is generated. For example, the client may have already generated a page before the current page is generated. In this embodiment of the invention, since feedback information can indicate whether the user is interested in historical pages, in order to generate a target page that better matches the user's preferences, the historical configuration can be adjusted based on the feedback information to obtain a page configuration that better matches the user's preferences, so that the target page can be generated based on the subsequent page configuration. For example, assuming that the feedback information determines that the user is not interested in the content displayed in component A of the historical page, the relevant configuration for component A in the historical configuration can be deleted; another example is that preset strategy rules may be included. In this embodiment of the invention, the historical configuration can be adjusted manually based on the feedback information, or the server can adjust the historical configuration automatically based on the feedback information, without specific limitations.
[0047] At this point, the server can obtain the page configuration. After receiving the page configuration request sent by the client, the server can return the page configuration to the client so that the client can receive the page configuration.
[0048] S130. Based on the page configuration, determine the target component to be displayed from each candidate component, as well as the display content to be displayed in the target component, and assemble the display content into the target component. Render the target page based on the assembled target component.
[0049] Candidate components can be understood as components that can be combined to obtain the target page, such as pop-up ad components, banner ad components, date components, or keyboard components. Candidate components can be reused in different scenarios and pages. In practical applications, candidate components are pure native components provided by the client. Target components can be understood as those candidate components that need to be displayed on the target page. Display content can be understood as the content displayed by the target component on the target page. The display content is assembled into the target component, and then rendered based on the assembled target component to generate the target page.
[0050] For example, assuming the target component determined from the candidate components according to the page configuration is the bottom navigation bar, and the content to be displayed in the bottom navigation bar is text and images, then the text and images are assembled into the bottom navigation bar, and the rendering is performed based on the assembled bottom navigation bar, thereby generating a target page with a bottom navigation bar filled with text and images.
[0051] This invention, in response to a page generation command, sends a page configuration request to a server. The page configuration request requests the page configuration of the target page to be generated. The server returns a page configuration in response to the request. This page configuration is obtained by adjusting historical configurations based on feedback information associated with historical pages. The historical pages correspond to the target page and are generated based on the historical configurations before the target page is generated. Based on the page configuration, the target component to be displayed and the content to be displayed within the target component are determined from candidate components. The display content is then assembled into the target component, and rendering is performed based on the assembled target component to generate the target page. This technical solution achieves page generation through configuration. Therefore, when business requirements change, only the configuration needs to be modified, without requiring a new release. This improves the flexibility and robustness of client-side business function iteration while reducing release frequency. Furthermore, since the final application's page configuration is obtained by adjusting historical configurations based on feedback information, it is more closely matched to user preferences, thus generating a target page that better matches user preferences.
[0052] An optional technical solution involves determining the target component to be displayed and the display content to be displayed within the target component from among the candidate components based on the page configuration, and assembling the display content into the target component. This includes: parsing the page configuration to obtain configuration parameters, and determining the target component to be displayed from among the candidate components based on the configuration parameters; passing the configuration parameters to the parameter configuration interface of the target component, so as to assemble the display content to be displayed within the target component corresponding to the configuration parameters into the target component.
[0053] In this context, configuration parameters can be understood as parameters used to determine the target component and the content displayed within it. For the latter, configuration parameters can be populated view options provided within the component, used to determine the specific content displayed. For example, the target component could be a banner ad, which can display specific ad content or a link that, when clicked, leads to the ad content. Based on this, if configuration parameter A is set to A, the banner ad will display the specific ad content; if configuration parameter B is set to B, the banner ad will display a link that, when clicked, leads to the ad content.
[0054] In this embodiment of the invention, the client parses the page configuration to obtain configuration parameters, and determines the target component to be displayed from each candidate component according to the configuration parameters; the configuration parameters are passed to the parameter configuration interface of the target component for receiving configuration parameters, and the display content to be displayed in the target component can be determined according to the configuration parameters, and the display content is assembled into the target component.
[0055] In this embodiment of the invention, the target component and the content to be displayed within the target component are determined according to the configuration parameters, so that the component content can be dynamically displayed in the same target component.
[0056] An optional technical solution involves determining the target component to be displayed from candidate components based on page configuration, including: determining the page type of the target page to be generated, and determining at least one type component corresponding to the page type from candidate components; and determining the target component to be displayed from at least one type component based on page configuration.
[0057] Among them, type components can be understood as candidate components that the page type of the target page can support.
[0058] It should be noted that, typically, the client can support three types of pages: pure native pages, HyperText Markup Language 5 (H5) pages, and React Native (RN) pages. Different page types support different component types; that is, each page type corresponds to one of three types of components, and each page is composed of components corresponding to its page type. In this embodiment of the invention, no specific limitation is made on the page types that the client can support.
[0059] In this embodiment of the invention, since the page types supported by each candidate component may differ, the page type of the target page to be generated can be determined first, then at least one type component corresponding to the page type can be determined from each candidate component, and then the target component to be displayed can be determined from at least one type component according to the page configuration, so that the determined target component can be supported by the target page.
[0060] An optional technical solution, the above page generation method further includes: sending a code resource request to a server, wherein the code resource request is used to request code resources for the target page to be generated; receiving code resources returned by the server in response to the code resource request; determining the target injection stage of the code resources in each stage of the page lifecycle according to the page configuration, based on the page lifecycle of the target page; injecting the code resources into the target page to be generated in the target stage to obtain code components corresponding to the code resources; and rendering based on the assembled target components to generate the target page, including: rendering based on the code components and the assembled target components to generate the target page.
[0061] In this context, code resources can be understood as resources capable of generating code components. The page lifecycle characterizes the page's behavior from its creation to its closure; it can have multiple phases, such as the start phase, loading phase, page initialization phase, and rendering phase. The target injection phase can be understood as the phase within the page lifecycle where code resources are injected. Code components are components generated based on code resources provided by the server, such as hybrid components like page entry / closing effects or new user navigation prompts. Hybrid components can define lifecycle hooks and predefined interaction methods such as JavaScript (JS) bridging methods. When the server assembles the code resource request and returns the corresponding JS resource to the client through a rules engine, the client injects the JS resource into the target page, achieving a dynamic display of the target page.
[0062] It is understandable that there is a need to display the effect rendered by the code component during the target injection phase of the target page. For example, after closing the target page, there is a need to prompt the user to confirm whether to close the page via a pop-up dialog. To achieve the above requirement, in this embodiment of the invention, the client can send a code resource request to the server and then receive the code resource returned by the server in response to the code resource request; based on the page lifecycle of the target page, the target injection phase of the code resource is determined according to the page configuration, that is, the phase in which the effect rendered by the code component is displayed is determined; during the target injection phase, the code resource is injected into the target page to be generated, resulting in a code component corresponding to the code resource; based on the code component and the assembled target component, rendering is performed to generate the target page, thereby realizing the dynamic display of page content.
[0063] In addition, in this embodiment of the invention, the client may inject the code resource into the target page to be generated after receiving the code resource returned by the server in response to the code resource request, thereby obtaining the code component corresponding to the code resource; during the target injection stage, the code component is rendered so as to update the target page according to the target page and the rendered code component.
[0064] Example 2
[0065] Figure 2 This is a flowchart of a page generation method according to Embodiment 2 of the present invention. The page generation method provided in this embodiment is executed by the server and is applicable to situations requiring page generation, especially those with flexible page generation requirements. Specifically, this method can be executed by a page generation device, which can be implemented in software and / or hardware and can be integrated into the server.
[0066] See Figure 2 The specific methods implemented in this way include:
[0067] S210. In response to the configuration adjustment instruction, obtain the page configuration, wherein the page configuration is obtained by adjusting the historical configuration based on the feedback information of the historical page, and the historical page is generated based on the historical configuration.
[0068] The configuration adjustment command can be understood as an instruction to adjust the historical configuration; the configuration adjustment command can adjust the historical configuration and use the adjusted historical configuration as the page configuration.
[0069] In this embodiment of the invention, after closing the history page, the client can send a configuration adjustment command to the server. The server responds to the configuration adjustment command, obtains the page configuration, and saves the page configuration on the server until a subsequent page configuration request is received from the client, at which point the saved page configuration is returned to the client. Alternatively, the configuration adjustment command can be automatically triggered by the server based on feedback information sent by the client, or it can be triggered by the user through the server, etc.
[0070] S220. Receive a page configuration request sent by the client, wherein the page configuration request is used to request the page configuration of the target page to be generated corresponding to the historical page.
[0071] S230. In response to the page configuration request, the page configuration is returned to the client so that the client can determine the target component to be displayed from the candidate components according to the received page configuration, as well as the display content to be displayed in the target component, assemble the display content into the target component, and render based on the assembled target component to generate the target page.
[0072] In this embodiment of the invention, the client may support multiple pages, so the server can store page configurations corresponding to multiple pages respectively; after receiving the page configuration request sent by the client, the server can determine the page configuration requested by the page configuration request from the page configurations stored on the server according to the page configuration request, and return it to the client.
[0073] This invention provides an embodiment of a page configuration obtained in response to a configuration adjustment command. The page configuration is derived by adjusting historical configurations based on feedback information from historical pages, and these historical pages are generated based on those historical configurations. The system receives a page configuration request from a client, requesting the page configuration for the target page to be generated corresponding to a historical page. In response to the page configuration request, the system returns the page configuration to the client, enabling the client to determine the target component to be displayed from among candidate components, along with the content to be displayed within the target component. The client then assembles the content into the target component and renders it based on the assembled target component to generate the target page. This technical solution achieves page generation through configuration. Therefore, when business requirements change, only the configuration needs to be modified, eliminating the need for a new release. This improves the flexibility and robustness of client-side business function iteration while reducing release frequency. Furthermore, since the final page configuration is obtained by adjusting historical configurations based on feedback information, it is more closely matched to user preferences, thus enabling the generation of a target page that better suits user preferences.
[0074] An optional technical solution involves having at least two page configurations and returning the page configurations to the client, including: determining the user group to which the client's application user belongs, and determining the group configuration from at least two page configurations based on the user group; and returning the group configuration as the page configuration to the client.
[0075] In this context, "group configuration" can be understood as the page configuration determined based on user groups. A user group can be understood as a group obtained by dividing users into subgroups, such as student groups, working professionals, or middle-aged and elderly groups.
[0076] In this embodiment of the invention, when a page configuration is obtained in response to a configuration adjustment command, at least two page configurations can be obtained by adjusting the historical configuration based on feedback information. For example, based on feedback from application users, it can be determined that users prefer to click on pushed articles, thus obtaining a page configuration with more pushed articles and a more rigorous article style, and a page configuration with more pushed articles and a more relaxed and lively article style. A group configuration matching the user group is determined from the at least two page configurations. For example, if the user group is office workers, the page configuration with more pushed articles and a more rigorous article style that matches the office worker group is selected as the group configuration. Then, the group configuration is returned to the client as the final determined page configuration.
[0077] In this embodiment of the invention, the above-mentioned configuration of at least two pages can be obtained by adjusting historical configurations as described above, or it can be pre-set in the server, without any specific limitation.
[0078] In this embodiment of the invention, by returning the group configuration as the page configuration to the client, the generated target page can be more closely matched with the application user, thereby improving the user experience.
[0079] To better understand the technical solutions of the above embodiments of the present invention, an optional example is provided herein. For example, see... Figure 3 The server sends historical configurations to the client, which then parses these configurations to render historical pages. Next, the client reports user feedback on these historical pages to the server. The server then adjusts the historical configurations based on this feedback to obtain the page configuration, which it sends back to the client. Finally, the client renders the received page configuration, resulting in a target page that better matches the user's preferences.
[0080] Example 3
[0081] Figure 4 This is a schematic diagram of a page generation apparatus according to Embodiment 3 of the present invention. This apparatus is used to execute the page generation method executed by the client provided in any of the above embodiments. This apparatus and the page generation methods executed by the client in the above embodiments belong to the same inventive concept. Details not described in detail in the embodiments of the page generation apparatus can be found in the embodiments of the page generation methods executed by the client described above. See also... Figure 4 Specifically, the device may include: a page configuration request sending module 310, a page configuration receiving module 320, and a target page generation module 330.
[0082] The page configuration request sending module 310 is used to send a page configuration request to the server in response to the page generation instruction. The page configuration request is used to request the page configuration of the target page to be generated.
[0083] The page configuration receiving module 320 is used to receive the page configuration returned by the server in response to the page configuration request. The page configuration is obtained by adjusting the historical configuration through feedback information associated with the historical page. The historical page corresponds to the target page and is generated based on the historical configuration before the target page is generated.
[0084] The target page generation module 330 is used to determine the target component to be displayed from each candidate component according to the page configuration, as well as the display content to be displayed in the target component, and to assemble the display content into the target component, and to render the target page based on the assembled target component.
[0085] Optionally, the target page generation module 330 may include:
[0086] The first target component determination unit is used to parse the page configuration, obtain the configuration parameters, and determine the target component to be displayed from each candidate component based on the configuration parameters;
[0087] The content assembly unit is used to pass configuration parameters to the parameter configuration interface of the target component, so as to assemble the display content corresponding to the configuration parameters to be displayed in the target component into the target component.
[0088] Optionally, the target page generation module 330 may include:
[0089] The type component determination unit is used to determine the page type of the target page to be generated, and to determine at least one type component corresponding to the page type from each candidate component;
[0090] The second target component determination unit is used to determine the target component to be displayed from at least one type of component based on the page configuration.
[0091] Optionally, the page generation device may also include:
[0092] The code resource request sending module is used to send code resource requests to the server. The code resource request is used to request the code resources of the target page to be generated.
[0093] The code resource receiving module is used to receive code resources returned by the server in response to code resource requests;
[0094] The target injection phase determination module is used to determine the target injection phase of code resources in each stage of the page lifecycle based on the page configuration, for the target page.
[0095] The code component module is used to inject code resources into the target page to be generated during the target injection phase, thereby obtaining the code component corresponding to the code resource.
[0096] The target page generation module 330 may include:
[0097] The target page generation unit is used to render the target page based on the code component and the assembled target component.
[0098] The page generation apparatus provided in Embodiment 3 of this invention responds to a page generation instruction by sending a page configuration request to a server via a page configuration request sending module. The page configuration request requests the page configuration of the target page to be generated. A page configuration receiving module receives the page configuration returned by the server in response to the page configuration request. This page configuration is obtained by adjusting historical configurations based on feedback information associated with historical pages. The historical pages correspond to the target page and are generated based on the historical configurations before the target page is generated. A target page generation module determines the target component to be displayed from candidate components based on the page configuration, along with the display content to be displayed within the target component. The display content is then assembled into the target component, and the target page is generated by rendering based on the assembled target component. This page generation apparatus of this embodiment achieves page generation through configuration. This means that when business requirements change, only the configuration needs to be modified, eliminating the need for a new release. This improves the flexibility and robustness of client-side business function iteration while reducing release frequency. Furthermore, since the final application's page configuration is obtained by adjusting historical configurations based on feedback information, it is more closely matched to user preferences, thus generating a target page that better matches user preferences.
[0099] The page generation apparatus provided in this embodiment of the invention can execute the page generation method executed by the client provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
[0100] It is worth noting that in the embodiments of the above-mentioned page generation device, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of the present invention.
[0101] Example 4
[0102] Figure 5 This is a schematic diagram of a page generation apparatus according to Embodiment 4 of the present invention. This apparatus is used to execute the page generation method executed by the server provided in any of the above embodiments. This apparatus and the page generation methods executed by the server in the above embodiments belong to the same inventive concept. Details not described in detail in the embodiments of the page generation apparatus can be found in the embodiments of the page generation methods executed by the server described above. See also... Figure 5 The device may specifically include: a page configuration acquisition module 410, a page configuration request receiving module 420, and a page configuration return module 430.
[0103] The page configuration module 410 is used to obtain the page configuration in response to the configuration adjustment instruction. The page configuration is obtained by adjusting the historical configuration based on the feedback information of the historical page. The historical page is generated based on the historical configuration.
[0104] The page configuration request receiving module 420 is used to receive page configuration requests sent by the client, wherein the page configuration request is used to request the page configuration of the target page to be generated corresponding to the historical page;
[0105] The page configuration return module 430 is used to respond to the page configuration request and return the page configuration to the client, so that the client can determine the target component to be displayed from the candidate components according to the received page configuration, as well as the display content to be displayed in the target component, assemble the display content into the target component, and render based on the assembled target component to generate the target page.
[0106] Optionally, the number of page configurations is at least two, and the page configuration returns module 430, which may include:
[0107] The group configuration determination unit is used to determine the user group to which the client's application users belong, and to determine the group configuration from at least two page configurations based on the user group;
[0108] The page configuration return unit is used to return the group configuration as page configuration to the client.
[0109] The page generation apparatus provided in Embodiment 4 of this invention obtains a page configuration through a page configuration acquisition module in response to a configuration adjustment command. This page configuration is obtained by adjusting historical configurations based on feedback information from historical pages, and the historical pages are generated based on these historical configurations. A page configuration request receiving module receives a page configuration request sent by a client, which requests the page configuration of the target page to be generated corresponding to the historical page. A page configuration return module responds to the page configuration request and returns the page configuration to the client, enabling the client to determine the target component to be displayed from among the candidate components based on the received page configuration, as well as the display content to be displayed within the target component. The client then assembles the display content into the target component and renders it based on the assembled target component to generate the target page. This page generation apparatus of this embodiment achieves page generation through configuration. This means that when business requirements change, only the configuration needs to be modified, eliminating the need for a new release. This improves the flexibility and robustness of client-side business function iteration while reducing the release frequency. Furthermore, since the final application page configuration is obtained by adjusting historical configurations based on feedback information, it is more closely matched to user preferences, thus generating a target page that better matches user preferences.
[0110] The page generation apparatus provided in this embodiment of the invention can execute the page generation method executed by the server provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
[0111] It is worth noting that in the embodiments of the above-mentioned page generation device, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of the present invention.
[0112] Example 5
[0113] Figure 6 This is a schematic diagram of the structure of a terminal according to Embodiment 5 of the present invention. Figure 6 As shown, this embodiment of the invention provides a terminal 512, which includes: one or more processors 516; a memory 528 for storing one or more programs; when one or more programs are executed by one or more processors, the one or more processors implement a page generation method executed by a client, including:
[0114] In response to the page generation instruction, a page configuration request is sent to the server. The page configuration request is used to request the page configuration of the target page to be generated.
[0115] The server receives the page configuration returned in response to the page configuration request. The page configuration is obtained by adjusting the historical configuration through feedback information associated with the historical page. The historical page corresponds to the target page and is generated based on the historical configuration before the target page is generated.
[0116] Based on the page configuration, the target component to be displayed and the display content to be displayed in the target component are determined from the candidate components. The display content is then assembled into the target component, and the target page is generated based on the assembled target component.
[0117] Figure 6 The terminal 512 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.
[0118] like Figure 6 As shown, terminal 512 is presented in the form of a general-purpose computing device. The components of terminal 512 may include, but are not limited to: one or more processors or processor 516, system memory 528, and bus 518 connecting different system components (including system memory 528 and processor 516).
[0119] Bus 518 represents one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus architectures. Examples of these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.
[0120] Terminal 512 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by terminal 512, including volatile and non-volatile media, removable and non-removable media.
[0121] System memory 528 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 530 and / or cache memory 532. Terminal 512 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 534 may be used to read and write non-removable, non-volatile magnetic media (… Figure 6 Not shown; usually referred to as a "hard drive"). Although Figure 6 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk") and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 518 via one or more data media interfaces. Memory 528 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of the present invention.
[0122] A program / utility 540 having a set (at least one) of program modules 542 may be stored, for example, in memory 528. Such program modules 542 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. Program modules 542 typically perform the functions and / or methods described in the embodiments of the present invention.
[0123] Terminal 512 can also communicate with one or more external devices 514 (e.g., keyboard, pointing device, display 524, etc.), and with one or more devices that enable a user to interact with the terminal 512, and / or with any device that enables the terminal 512 to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed via input / output (I / O) interface 522. Furthermore, terminal 512 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 520. As shown, network adapter 520 communicates with other modules of terminal 512 via bus 518. It should be understood that, although... Figure 6 As not shown in the diagram, other hardware and / or software modules can be used in conjunction with terminal 512, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0124] The processor 516 performs various functional applications and data processing by running at least one of the other programs among a plurality of programs stored in the system memory 528, such as implementing the page generation method executed by the client provided in the embodiments of the present invention.
[0125] This embodiment also provides a server, comprising: one or more processors; a memory for storing one or more programs; and a method for the one or more processors to implement a page generation method executed by the server when the one or more programs are executed, including:
[0126] In response to the configuration adjustment command, the page configuration is obtained. The page configuration is obtained by adjusting the historical configuration based on the feedback information of the historical page. The historical page is generated based on the historical configuration.
[0127] Receive a page configuration request sent by the client, wherein the page configuration request is used to request the page configuration of the target page to be generated corresponding to the historical page;
[0128] In response to a page configuration request, the page configuration is returned to the client, enabling the client to determine the target component to be displayed from among the candidate components, as well as the display content to be displayed within the target component, based on the received page configuration. The display content is then assembled into the target component, and the target page is generated based on the assembled target component.
[0129] Of course, those skilled in the art will understand that the processor can also implement the technical solution of the page generation method executed by the server provided in any embodiment of the present invention. The hardware structure and functions of the server can be found in the explanation of Embodiment 5.
[0130] Example 6
[0131] Embodiment 6 of the present invention provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to execute a page generation method executed by a client, the method comprising:
[0132] In response to the page generation instruction, a page configuration request is sent to the server. The page configuration request is used to request the page configuration of the target page to be generated.
[0133] The server receives the page configuration returned in response to the page configuration request. The page configuration is obtained by adjusting the historical configuration through feedback information associated with the historical page. The historical page corresponds to the target page and is generated based on the historical configuration before the target page is generated.
[0134] Based on the page configuration, the target component to be displayed and the display content to be displayed in the target component are determined from the candidate components. The display content is then assembled into the target component, and the target page is generated based on the assembled target component.
[0135] Of course, the computer-executable instructions provided in the embodiments of the present invention are not limited to the method operations described above, but can also perform related operations in the page generation method executed by the client provided in any embodiment of the present invention.
[0136] The computer storage medium of this invention can be any combination of one or more computer-readable media. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
[0137] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of sending, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.
[0138] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.
[0139] Computer program code for performing the operations of this invention can be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, and C++, as well as conventional procedural programming languages such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0140] This invention also provides another computer-readable storage medium, wherein the computer-executable instructions, when executed by a computer processor, are used to perform a page generation method executed by a server, the method comprising:
[0141] In response to the configuration adjustment command, the page configuration is obtained. The page configuration is obtained by adjusting the historical configuration based on the feedback information of the historical page. The historical page is generated based on the historical configuration.
[0142] Receive a page configuration request sent by the client, wherein the page configuration request is used to request the page configuration of the target page to be generated corresponding to the historical page;
[0143] In response to a page configuration request, the page configuration is returned to the client, enabling the client to determine the target component to be displayed from among the candidate components, as well as the display content to be displayed within the target component, based on the received page configuration. The display content is then assembled into the target component, and the target page is generated based on the assembled target component.
[0144] Of course, the computer-executable instructions included in the storage medium provided in this embodiment of the invention are not limited to the method operations described above, but can also perform related operations in the page generation method executed by the server provided in any embodiment of the invention. For a description of the storage medium, please refer to the explanation in Embodiment Six.
[0145] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.
Claims
1. A page generation method, characterized in that, Applied to a client, the method includes: In response to the page generation instruction, a page configuration request is sent to the server, wherein the page configuration request is used to request the page configuration of the target page to be generated; The server receives the page configuration returned in response to the page configuration request. The page configuration is obtained by adjusting the historical configuration through feedback information associated with the historical page. The historical page corresponds to the target page and is generated based on the historical configuration before the target page is generated. Based on the page configuration, the target component to be displayed and the display content to be displayed in the target component are determined from each candidate component, and the display content is assembled into the target component. The target page is generated by rendering based on the assembled target component. The method further includes: A code resource request is sent to the server, wherein the code resource request is used to request the code resources of the target page to be generated; Receive the code resource returned by the server in response to the code resource request; For the page lifecycle of the target page, the target injection stage of the code resource in each stage of the page lifecycle is determined according to the page configuration; wherein, the page lifecycle represents the behavior pattern of the page from birth to closing, and the page lifecycle includes the start stage, loading stage, page initialization stage and rendering stage; In the target injection phase, the code resource is injected into the target page to be generated to obtain the code component corresponding to the code resource; The step of rendering the target page based on the assembled target component to generate the target page includes: The target page is generated by rendering based on the code component and the assembled target component.
2. The method according to claim 1, characterized in that, The step of determining the target component to be displayed from each candidate component according to the page configuration, and the display content to be displayed in the target component, and assembling the display content into the target component, includes: The page configuration is parsed to obtain configuration parameters, and the target component to be displayed is determined from each candidate component based on the configuration parameters; The configuration parameters are passed to the parameter configuration interface of the target component to assemble the display content corresponding to the configuration parameters into the target component.
3. The method according to claim 1, characterized in that, The step of determining the target component to be displayed from the candidate components according to the page configuration includes: Determine the page type of the target page to be generated, and determine at least one type component corresponding to the page type from each candidate component; The target component to be displayed is determined from the at least one type of component based on the page configuration.
4. A page generation method, characterized in that, Applied to the server side, the method includes: In response to a configuration adjustment command, a page configuration is obtained, wherein the page configuration is obtained by adjusting a historical configuration based on feedback information of a historical page, and the historical page is generated based on the historical configuration; Receive a page configuration request sent by the client, wherein the page configuration request is used to request the page configuration of the target page to be generated corresponding to the historical page; In response to the page configuration request, the page configuration is returned to the client, so that the client determines the target component to be displayed from each candidate component and the display content to be displayed in the target component according to the received page configuration, assembles the display content into the target component, and renders the assembled target component to generate the target page; The method further includes: Receive a code resource request sent by the client, wherein the code resource request is used to request the code resources of the target page to be generated; In response to the code resource request, the code resource is returned to the client, so that the client, based on the page configuration, determines the target injection stage of the code resource in each stage of the page lifecycle of the target page, and injects the code resource into the target page to be generated in the target injection stage to obtain the code component corresponding to the code resource; wherein, the page lifecycle represents the behavior mode of the page from its creation to its closure, and the page lifecycle includes the start stage, loading stage, page initialization stage, and rendering stage; The step of rendering the assembled target component to generate the target page includes: The target page is generated by rendering based on the code component and the assembled target component.
5. The method according to claim 4, characterized in that, The number of page configurations is at least two, and returning the page configurations to the client includes: Determine the user group to which the application user of the client belongs, and determine the group configuration from the at least two page configurations based on the user group; The group configuration is then returned to the client as the page configuration.
6. A page generation apparatus, characterized in that, Configured in the client, the device includes: The page configuration request sending module is used to send a page configuration request to the server in response to the page generation instruction, wherein the page configuration request is used to request the page configuration of the target page to be generated; A page configuration receiving module is used to receive the page configuration returned by the server in response to the page configuration request. The page configuration is obtained by adjusting the historical configuration through feedback information associated with the historical page. The historical page corresponds to the target page and is generated based on the historical configuration before the target page is generated. The target page generation module is used to determine the target component to be displayed from each candidate component according to the page configuration, as well as the display content to be displayed in the target component, and to assemble the display content into the target component, and to render the target page based on the assembled target component. The page generation device further includes: A code resource request sending module is used to send a code resource request to the server, wherein the code resource request is used to request the code resources of the target page to be generated; A code resource receiving module is used to receive the code resource returned by the server in response to the code resource request; The target injection phase determination module is used to determine the target injection phase of the code resource in each stage of the page lifecycle based on the page configuration, for the target page; wherein, the page lifecycle represents the behavior pattern of the page from its creation to its closure, and the page lifecycle includes the start phase, loading phase, page initialization phase, and rendering phase; A code component obtaining module is used to inject the code resource into the target page to be generated during the target injection stage, thereby obtaining a code component corresponding to the code resource; The target page generation module includes: The target page generation unit is used to render the target page based on the code component and the assembled target component.
7. A page generation apparatus, characterized in that, Configured in the server, the device includes: A page configuration acquisition module is used to obtain page configuration in response to configuration adjustment instructions, wherein the page configuration is obtained by adjusting historical configurations based on feedback information of historical pages, and the historical pages are generated based on the historical configurations; A page configuration request receiving module is used to receive a page configuration request sent by a client, wherein the page configuration request is used to request the page configuration of the target page to be generated corresponding to the historical page; A page configuration return module is used to respond to the page configuration request and return the page configuration to the client, so that the client can determine the target component to be displayed from each candidate component and the display content to be displayed in the target component according to the received page configuration, assemble the display content into the target component, and render based on the assembled target component to generate the target page; The device is also used for: Receive a code resource request sent by the client, wherein the code resource request is used to request the code resources of the target page to be generated; In response to the code resource request, the code resource is returned to the client, so that the client, based on the page configuration, determines the target injection stage of the code resource in each stage of the page lifecycle of the target page, and injects the code resource into the target page to be generated in the target injection stage to obtain the code component corresponding to the code resource; wherein, the page lifecycle represents the behavior mode of the page from its creation to its closure, and the page lifecycle includes the start stage, loading stage, page initialization stage, and rendering stage; The step of rendering the assembled target component to generate the target page includes: The target page is generated by rendering based on the code component and the assembled target component.
8. A terminal, characterized in that, The terminal includes: One or more processors; Memory, used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement a page generation method as described in any one of claims 1-3.
9. A server, characterized in that, The server includes: One or more processors; Memory, used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement a page generation method as described in any one of claims 4-5.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the program implements a page generation method as described in any one of claims 1-5.
Citation Information
Patent Citations
Page information showing and generating method, device and system
CN108089878A
Activity page display calling method, server and client
CN111381900A
Multi-role page creation method and device, server and readable storage medium
CN113434122A
Page generation method and device and storage medium
CN113448577A