Page generation method, device and computer equipment

Abstract

The application relates to a page generation method, device and computer equipment. The method comprises the following steps: in response to a page generation request, performing a hit experiment on page skeletons in a preset page skeleton resource library based on the page generation request, obtaining page skeletons hit by the page generation request, generating a page skeleton data set, and the page skeletons are at least one; obtaining a page skeleton satisfying the page generation request from the page skeleton data set according to a preset funnel filtering rule, and defining the page skeleton as a basic page skeleton; based on the basic page skeleton and the page generation request, performing content covering on page components and page units of the page according to a preset page skeleton hierarchical relationship, so as to generate the page.

Description

Technical Field

[0001] This application relates to the field of page generation technology, and in particular to a page generation method, apparatus and computer device. Background Technology

[0002] With the rapid development of the Internet, 4G / 5G network technology has become fully mature and mobile Internet technology has become widespread. The page generation method described in patent number "CN113268233A" is only to avoid adaptation conflicts between page components when generating pages. It can no longer solve the actual problem of page content not matching the individual needs of users in practical applications.

[0003] However, in current technologies, the display and layout of resource slots in apps or embedded H5 pages are hardcoded in the front-end code. If UI adjustments are needed, developers must create corresponding changes, and a version must be released after testing. This process is lengthy and involves multiple teams. In the context of rapid internet development, operations teams need to respond quickly and edit the content of resource slots for specific scenarios or key business needs. This places high demands on the real-time responsiveness of content management. However, existing page generation methods are labor-intensive and inefficient in updating pages.

[0004] In high-traffic apps, impressions and clicks are two crucial metrics. Traffic conversion rate can significantly boost an app company's revenue. Therefore, improving click-through rate (CTR) is a key consideration for every business. Attracting users' attention is a suitable tactic, but different users have different priorities. Ensuring users see, or are highly likely to see, the content they need and find relevant is a critical factor in "attracting" attention.

[0005] In practical applications, different users may have different business models, and the pages displayed should be tailored to these models. For example, loan users might be unapproved, have been approved but haven't borrowed, or have borrowed and are about to default. For unapproved users, we need to guide them to apply for credit so we can continue to provide better services; for users who have been approved but haven't borrowed, we need to guide them to borrow; and for users who have borrowed and are about to default, we need to remind them to repay to avoid negatively impacting their credit scores. Therefore, users with different business models focus on different content, and thus the displayed pages will also differ. At the same time, users with the same business model also have different personal needs and preferences. For example, some users might not click on the same displayed icons, while others might be interested and click. Therefore, ensuring that users are likely to see content that interests them and thus be motivated to click is also a problem that needs to be solved.

[0006] Therefore, there is an urgent need to propose a page generation method, device, computer equipment, and storage medium that can meet the needs of user groups and adapt to individual user characteristics. Summary of the Invention

[0007] Therefore, it is necessary to provide a page generation method, apparatus, computer equipment, and storage medium that can meet the needs of user groups and adapt to individual user characteristics in order to address the above-mentioned technical problems.

[0008] On the one hand, a page generation method is provided, the method comprising:

[0009] In response to a page generation request, a hit experiment is performed on page skeletons in a preset page skeleton resource library based on the page generation request to obtain the page skeletons hit by the page generation request and generate a page skeleton dataset, wherein the page skeleton is at least one;

[0010] According to the preset funnel filtering rules, obtain the page skeleton that satisfies the page generation request from the page skeleton dataset, and define the page skeleton as the basic page skeleton;

[0011] Based on the basic page skeleton and the page generation request, the page components and page units of the page are overwritten with content according to the preset page skeleton hierarchy to generate the page.

[0012] In one embodiment, a hit experiment is performed on page skeletons in a preset page skeleton resource library based on the page generation request to obtain the page skeletons that the page generation request hits. This includes: obtaining the page generation request, which includes client type, page type, page generation request issuance time, and user group; based on the page generation request issuance time, selecting page skeletons from the preset skeleton resource library whose validity period has not exceeded the page generation request issuance time to generate an initial page skeleton set; and based on the client type and the page type, selecting page skeletons from the initial page skeleton set that are compatible with both the client type and the page type to generate a target page skeleton set.

[0013] In one embodiment, obtaining a page skeleton that satisfies the page generation request from the page skeleton dataset according to a preset funnel filtering rule includes: obtaining attribute information of the page skeletons included in the target page skeleton set; determining whether the page skeleton has user group restrictions based on the attribute information of the page skeleton; if the page skeleton has user group restrictions, determining whether the user group included in the page generation request conforms to the user group restrictions of the page skeleton; if the user group included in the page generation request does not conform to the user group restrictions of the page skeleton, deleting the page skeleton from the page skeleton set and updating the target page skeleton set.

[0014] In one embodiment, obtaining page skeletons that satisfy the page generation request from the page skeleton dataset according to a preset funnel filtering rule further includes: randomly publishing page skeletons contained in the target page skeleton set to the client, wherein there is at least one page skeleton; obtaining the business impact of each page skeleton in a closed loop; discarding page skeletons whose business impact does not meet the preset business impact requirements, and updating the target page skeleton set.

[0015] In one embodiment, obtaining a page skeleton that satisfies the page generation request from the page skeleton dataset according to a preset funnel filtering rule further includes: obtaining a page generation request, the page generation request including a page skeleton application scenario, the page skeleton application scenario including a mobile phone brand, an application, and a placement entry; based on the page skeleton application scenario, determining whether there is a page skeleton in the target skeleton that is compatible with the mobile phone brand, the page skeleton that is compatible with the mobile phone brand including a specific page skeleton and a default page skeleton; when there is a specific page skeleton in the target skeleton that is compatible with the mobile phone brand, the default page skeleton is discarded and the target page skeleton set is updated; when there is no specific page skeleton in the target skeleton that is compatible with the mobile phone brand, the default page skeleton is retained and the target page skeleton set is updated.

[0016] In one embodiment, obtaining a page skeleton that satisfies the page generation request from the page skeleton dataset according to a preset funnel filtering rule further includes: obtaining the page skeleton corresponding to the maximum preset weight value based on a preset weight value of the page skeletons in the target page skeleton set, wherein the preset weight value is unique; defining the page skeleton as a base page skeleton, wherein the base page skeleton is one.

[0017] In one embodiment, based on the basic page skeleton and the page generation request, content overlay is performed on the page components and page units of the page according to a preset page skeleton hierarchy, including: based on the basic page skeleton, obtaining the page floor framework associated with the basic page skeleton, wherein the validity period of the page floor framework does not exceed the time when the page generation request was issued; based on the page floor framework, traversing each floor in the page floor framework to obtain a floor component relationship table for the floor; based on the floor component relationship table, obtaining page components adapted to the floor, performing content overlay on the page components of the floor, and based on the page components, obtaining a component unit relationship table for the page components; based on the component unit relationship table, obtaining the page unit information of the page components, performing content overlay on the page units of the page components to generate the page.

[0018] In one embodiment, based on the floor component relationship table, page component information of the floor is obtained, and content overlay is performed on the page components of the floor, including: based on the floor component relationship table, obtaining page components adapted to the floor, wherein the page component is at least one; based on the attribute information of the page component, determining whether the page component is restricted to a user group; if the page component is restricted to a user group, determining whether the user group included in the page generation request matches the user group restricted by the page component; if the user group included in the page generation request does not match the user group restricted by the page component, discarding the page component; otherwise, retaining the page component.

[0019] In one embodiment, based on the floor component relationship table, obtaining the page component information of the floor and performing content coverage on the page components of the floor further includes: obtaining the reserved page components and determining whether the number of page components is one; if the number of page components is not one, randomly distributing the page components to the floor, obtaining the business impact of each page component in a closed loop, obtaining the page component corresponding to the optimal value of the business impact, and performing content coverage on the floor based on the page components; if the number of page components is one, performing content coverage on the floor based on the page components.

[0020] On the other hand, a page generation apparatus is provided, the apparatus comprising:

[0021] An execution unit, in response to a page generation request, performs a hit experiment on page skeletons in a preset page skeleton resource library based on the page generation request, obtains the page skeletons hit by the page generation request, and generates a page skeleton dataset, wherein the page skeleton is at least one.

[0022] The acquisition unit is used to acquire a page skeleton that satisfies the page generation request from the page skeleton dataset according to a preset funnel filtering rule, and to define the page skeleton as a base page skeleton.

[0023] The content overlay unit is used to overlay the page components and page units of the page according to a preset page skeleton hierarchy, based on the basic page skeleton and the page generation request, in order to generate the page.

[0024] In another aspect, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to perform the following steps:

[0025] In response to a page generation request, a hit experiment is performed on page skeletons in a preset page skeleton resource library based on the page generation request to obtain the page skeletons hit by the page generation request and generate a page skeleton dataset, wherein the page skeleton is at least one;

[0026] According to the preset funnel filtering rules, obtain the page skeleton that satisfies the page generation request from the page skeleton dataset, and define the page skeleton as the basic page skeleton;

[0027] Based on the basic page skeleton and the page generation request, the page components and page units of the page are overwritten with content according to the preset page skeleton hierarchy to generate the page.

[0028] In another aspect, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0029] In response to a page generation request, a hit experiment is performed on page skeletons in a preset page skeleton resource library based on the page generation request to obtain the page skeletons hit by the page generation request and generate a page skeleton dataset, wherein the page skeleton is at least one;

[0030] According to the preset funnel filtering rules, obtain the page skeleton that satisfies the page generation request from the page skeleton dataset, and define the page skeleton as the basic page skeleton;

[0031] Based on the basic page skeleton and the page generation request, the page components and page units of the page are overwritten with content according to the preset page skeleton hierarchy to generate the page.

[0032] The aforementioned page generation method, apparatus, computer equipment, and storage medium, the method comprising: responding to a page generation request; performing a hit experiment on page skeletons in a preset page skeleton resource library based on the page generation request; obtaining page skeletons that are hit by the page generation request; generating a page skeleton dataset, wherein the page skeleton is at least one; obtaining page skeletons that satisfy the page generation request from the page skeleton dataset according to a preset funnel filtering rule; defining the page skeleton as a basic page skeleton; and, based on the basic page skeleton and the page generation request, performing content coverage on the page components and page units of the page according to a preset page skeleton hierarchy to generate the page. Based on the above technical solution, this application can respond to content management in real time and efficiently, with low labor costs and fast page update efficiency;

[0033] Specifically, a hit experiment is performed on page skeletons in a preset page skeleton resource library based on the page generation request to obtain the page skeletons that are hit by the page generation request and generate a page skeleton dataset, wherein there is at least one page skeleton; page skeletons that meet the page generation request are obtained from the page skeleton dataset according to a preset funnel filtering rule, and pages that are highly adapted to users are generated based on user characteristics, which helps to stimulate users' desire to click and enhance their access impulse. Attached Figure Description

[0034] Figure 1 This is a diagram illustrating the application environment of a page generation method in one embodiment;

[0035] Figure 2 This is a flowchart illustrating a page generation method in one embodiment;

[0036] Figure 3 This is a flowchart illustrating the page skeleton filtering step in a page generation method in one embodiment.

[0037] Figure 4 This is a flowchart illustrating the page component filtering step in a page generation method in one embodiment.

[0038] Figure 5 This is a flowchart illustrating a page generation method in one embodiment;

[0039] Figure 6 This is a schematic diagram illustrating the process of generating a preset page skeleton resource library in the embodiment.

[0040] Figure 7This is a structural block diagram of a page generation device in one embodiment;

[0041] Figure 8 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0042] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0043] The page generation method provided in this application can be applied to, for example... Figure 1 In the application environment shown, terminal 102 communicates with server 104 via a network. Terminal 102 sends page generation requests to server 104 via the network. Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices. Server 104 can be a standalone server or a server cluster consisting of multiple servers. Server 104 communicates with operator terminal 106 via a network. Server 104 stores a preset set of page skeleton resources generated by operator terminal 106. Operator terminal performs differentiated configuration based on different user groups to achieve personalized page resource configuration, improve the real-time performance of resource configuration, and allow page resource changes to be immediately reflected in the client display without relying on client-side adjustments.

[0044] In one embodiment, such as Figure 2 As shown, a page generation method is provided, which can be applied to... Figure 1 Taking the server in the example, the following steps are included:

[0045] In response to a page generation request, a hit experiment is performed on page skeletons in a preset page skeleton resource library based on the page generation request to obtain the page skeletons hit by the page generation request and generate a page skeleton dataset, wherein the page skeleton is at least one;

[0046] According to the preset funnel filtering rules, obtain the page skeleton that satisfies the page generation request from the page skeleton dataset, and define the page skeleton as the basic page skeleton;

[0047] Based on the basic page skeleton and the page generation request, the page components and page units of the page are overwritten with content according to the preset page skeleton hierarchy to generate the page.

[0048] In one embodiment, before performing a hit experiment on the page skeleton in the preset page skeleton resource library based on the page generation request, the method further includes: generating a preset page skeleton resource library, and synchronously updating the page skeleton in the page skeleton resource library to separate cache and local cache to ensure the consistency between multi-level cache and original data. The entire process is continuous, and the entire continuous process is completed in the same transaction according to the atomicity principle.

[0049] Specifically, the pre-defined page skeleton resource library includes, but is not limited to, page type definitions, page unit configurations, page component configurations, and page information configurations.

[0050] The page type definition involves defining the page type, name, and encoding. For example, common app pages include the homepage, user center page, facial recognition page, and loan application page; these are page names defined based on the page type. It's important to understand that the page type is merely a front-end / back-end convention. This is because content information is assembled and configured independently on a page-by-page basis. Therefore, specifying the page type or page name explicitly informs the server of the dynamic content information details through API calls.

[0051] Configuring page units includes generating icons for displaying the page units based on their functions and types, and adding text descriptions at the bottom of each icon to clearly inform users of the function corresponding to that icon. Page units may also include jump links, badge text, and animations. It should be understood that, when necessary, those skilled in the art may also attach a validity period to the page unit.

[0052] Page components are configured based on page units. A page is composed of page units, and a page component can contain several page units. Page units include, but are not limited to, icons and text descriptions below them, as well as jump links, badge text, etc. It's important to understand that page units must exist within page components; page units can only form page components. The relationship between page units and page components is necessary and fixed. The fixed relationship between page units and page components means that there is a one-to-one correspondence, meaning that page units can only form page components, and page components include page units. The units within a page are arranged. A unit is the smallest unit of content management. Page units cannot be arranged randomly or arbitrarily; they must be arranged according to certain rules. For example, the page component menu bar displayed on the application's homepage. In a traditional application, the purpose of page components is to quickly provide users with access to application functions, typically in a 2x5 format, but other layouts may exist, such as 1x5. The 2x5 layout above means there are two rows, each displaying 5 icons, containing a total of 10 page units. Meanwhile, page components also correspond to different business attributes. Users with the same business attribute can be grouped into the same customer group; that is, there is a corresponding relationship between page components and user groups. For example, users with the business attribute of "registered but not yet granted credit" can be grouped into the "pending credit" user group, while users with the business attribute of "granted credit but not yet borrowed" can be grouped into the "pending loan" user group. The display method of page units within page components corresponding to different user groups also differs. In other words, a key step in configuring page components is to select the expected target user group for that page component and then select appropriate page units based on that target user group. For example, if the expected target user group for a page component is "registered but not yet granted credit," then the page unit configured to guide users to grant credit should be selected within that page component. It is important to understand that when generating page components based on page units, if the page unit has an expiration date, the page component should be generated based on the page unit that is still within its expiration period.

[0053] A page skeleton is generated based on page components and page types. Furthermore, the association between the client and the page skeleton is established based on client type, and the association between the application and the page skeleton is established based on application version. Additionally, those skilled in the art can attach an expiration date to the page skeleton according to application needs.

[0054] In one embodiment, such as Figure 3As shown, a hit experiment is performed on page skeletons in a preset page skeleton resource library based on the page generation request. This includes ensuring that the hit page skeletons meet preset hard conditions. These hard conditions are static, mandatory conditions to avoid configuration disorder. For example, the time of the page generation request included in the page request must not exceed the validity period of the current page skeleton. Furthermore, based on the client type included in the page request, the page skeleton is ensured to be compatible with the client type. For instance, different clients such as iOS, Android, H5, and WeChat Mini Programs have different rendering formats and may require different types of page resource content, i.e., different page skeletons are needed. Also, different page types, such as homepage, personal center page, and process page, have different page content, and their page skeletons will also differ. For the same user request, the number of page skeletons obtained from the preset page skeleton resource library is at least one. When the number of page skeletons exceeds one, a page skeleton dataset is generated based on the page skeletons.

[0055] like Figure 3As shown, according to the preset funnel filtering rules, the page skeletons in the page skeleton set are filtered, selecting those that meet the page generation request and discarding those that do not. Finally, only one page skeleton with the highest adaptability to the page generation request remains, and this skeleton is defined as the base page skeleton. Specifically, firstly, user group filtering is performed. Each page skeleton can be configured with user group conditions. The user group is implemented by calling the user group module interface using user information identifiers. The interface returns whether the user group is matched. If matched, the current page skeleton passes the filter; otherwise, it is discarded. Then, a bucket test is performed on the user. This bucket test is an A / B test layer filtering test. The user information identifier is used as the judgment standard. A balanced hash of the user information identifier is performed, and the modulo operation is used to obtain an integer result between 1 and 100. This result is completely distributed within the bucket test threshold coverage range. If it meets a pre-configured sub-experiment, it is considered to have met this bucket test, and the page skeleton can enter the next funnel filtering layer; otherwise, it is discarded. Secondly, sub-channel downgrading is performed on the client side. Sub-channel downgrading means that when the existing page skeleton's channel package is compatible with the client, the page is displayed using the lowest-configuration channel package that is compatible with the current client. For example, for Android apps, there may be multiple channel packages. For example, Xiaomi, Huawei, and Vivo have different channel packages customized by developers for different app stores. Similarly, the applicable channels in H5 scenarios are also different. For example, the H5 entry embedded in the iQiyi app or the H5 entry embedded in the ZhongAn Insurance app are distinguished based on the current partner's channel scenario. If the input parameter, i.e., the channel of the current environment, can be found in the configuration with a corresponding page skeleton, these sub-channel type page skeletons can be passed to the next layer for filtering. Page skeletons that do not conform to the sub-channel type need to be placed in the discard area. However, configuring sub-channel pages is a lot of work for the operations side, and it is impossible to cover all sub-channel types. If a sub-channel type exists, it can be understood that the operations side requires that this sub-channel type must have special display content. If it does not exist, it needs to be downgraded to use the default version. Therefore, the default channel under the default channel is the "default channel," which will be configured for resource content of type "default" regardless of whether it's an app, an H5 page, or a WeChat mini-program. In a downgrade scenario, all page skeletons matching the sub-channel type "default" are retrieved and filtered further. Finally, based on preset page skeleton weights, the initial page skeleton corresponding to the maximum weight is obtained, and this initial page skeleton is defined as the base page skeleton. The weight values ​​of page skeletons based on the same page skeleton dataset are unique.

[0056] In one embodiment, such as Figure 4As shown, based on the basic page skeleton and the page generation request, the page components and page units of the page are overwritten with content according to a preset page skeleton hierarchy to generate the page. This includes: obtaining the page floor framework associated with the basic page skeleton; traversing each floor in the page floor framework to obtain a floor component relationship table; obtaining the page component information of the floor based on the floor component relationship table, overwriting the page components of the floor with content, and obtaining a component unit relationship table of the page components; and obtaining the page unit information of the page components based on the component unit relationship table, overwriting the page units of the page components with content, to generate the page.

[0057] Specifically, based on the page skeleton, the page information of the page skeleton is obtained, including page number, adapted product, adapted platform, page type, and validity period. Based on the page floor framework of the page skeleton, the page skeleton is horizontally cut to generate multiple floors, each floor with individually configured content. The floor information corresponding to each floor includes floor number and validity period. Based on each floor, the floor component relationship table of the floor is obtained, the page component information of the floor is obtained, the page components of the floor are content-overwritten, and based on the page components, the component unit relationship table of the page components is obtained; based on the component relationship table, the page unit information of the page components is obtained, and the page content of the page components is content-overwritten, thus generating the page.

[0058] Specifically, for each floor, a floor component relationship table is obtained, and page component information for that floor is acquired. Content overlay is then applied to the page components of that floor. This includes: obtaining a page floor framework associated with the page skeleton code based on the page skeleton code of the basic page skeleton; obtaining a floor component relationship table for each floor within the page floor framework, where the floor component relationship table represents the associated floors and page components. Specifically, based on the floor code, component information associated with the floor code is obtained, including component code, component weight, component validity period, and component type. Finally, the page component corresponding to the highest weight is obtained, and content overlay is applied to the page components of that floor. Based on the page component code of the page component, unit information of the page unit associated with the page component is obtained, including unit code and unit fields. Based on the unit information, content overlay is applied to the page units of the component to generate the page.

[0059] In one embodiment, such as Figure 2 As shown, this application proposes a page generation method, the method comprising:

[0060] In response to a page generation request, a hit experiment is performed on page skeletons in a preset page skeleton resource library based on the page generation request to obtain the page skeletons hit by the page generation request and generate a page skeleton dataset, wherein the page skeleton is at least one;

[0061] According to the preset funnel filtering rules, obtain the page skeleton that satisfies the page generation request from the page skeleton dataset, and define the page skeleton as the basic page skeleton;

[0062] Based on the basic page skeleton and the page generation request, the page components and page units of the page are overwritten with content according to the preset page skeleton hierarchy to generate the page.

[0063] In one embodiment, a hit experiment is performed on page skeletons in a preset page skeleton resource library based on the page generation request to obtain the page skeletons that the page generation request hits. This includes: obtaining the page generation request, which includes client type, page type, page generation request issuance time, and user group; based on the page generation request issuance time, selecting page skeletons from the preset skeleton resource library whose validity period has not exceeded the page generation request issuance time to generate an initial page skeleton set; and based on the client type and the page type, selecting page skeletons from the initial page skeleton set that are compatible with both the client type and the page type to generate a target page skeleton set.

[0064] In one embodiment, obtaining a page skeleton that satisfies the page generation request from the page skeleton dataset according to a preset funnel filtering rule includes: obtaining attribute information of the page skeletons included in the target page skeleton set; determining whether the page skeleton has user group restrictions based on the attribute information of the page skeleton; if the page skeleton has user group restrictions, determining whether the user group included in the page generation request conforms to the user group restrictions of the page skeleton; if the user group included in the page generation request does not conform to the user group restrictions of the page skeleton, deleting the page skeleton from the page skeleton set and updating the target page skeleton set.

[0065] In one embodiment, obtaining page skeletons that satisfy the page generation request from the page skeleton dataset according to a preset funnel filtering rule further includes: randomly publishing page skeletons contained in the target page skeleton set to the client, wherein there is at least one page skeleton; obtaining the business impact of each page skeleton in a closed loop; discarding page skeletons whose business impact does not meet the preset business impact requirements, and updating the target page skeleton set.

[0066] In one embodiment, obtaining a page skeleton that satisfies the page generation request from the page skeleton dataset according to a preset funnel filtering rule further includes: obtaining a page generation request, the page generation request including a page skeleton application scenario, the page skeleton application scenario including a mobile phone brand, an application, and a placement entry; based on the page skeleton application scenario, determining whether there is a page skeleton in the target skeleton that is compatible with the mobile phone brand, the page skeleton that is compatible with the mobile phone brand including a specific page skeleton and a default page skeleton; when there is a specific page skeleton in the target skeleton that is compatible with the mobile phone brand, the default page skeleton is discarded and the target page skeleton set is updated; when there is no specific page skeleton in the target skeleton that is compatible with the mobile phone brand, the default page skeleton is retained and the target page skeleton set is updated.

[0067] In one embodiment, obtaining a page skeleton that satisfies the page generation request from the page skeleton dataset according to a preset funnel filtering rule further includes: obtaining the page skeleton corresponding to the maximum preset weight value based on a preset weight value of the page skeletons in the target page skeleton set, wherein the preset weight value is unique; defining the page skeleton as a base page skeleton, wherein the base page skeleton is one.

[0068] In one embodiment, based on the basic page skeleton and the page generation request, content overlay is performed on the page components and page units of the page according to a preset page skeleton hierarchy, including: based on the basic page skeleton, obtaining the page floor framework associated with the basic page skeleton, wherein the validity period of the page floor framework does not exceed the time when the page generation request was issued; based on the page floor framework, traversing each floor in the page floor framework to obtain a floor component relationship table for the floor; based on the floor component relationship table, obtaining page components adapted to the floor, performing content overlay on the page components of the floor, and based on the page components, obtaining a component unit relationship table for the page components; based on the component unit relationship table, obtaining the page unit information of the page components, performing content overlay on the page units of the page components to generate the page.

[0069] In one embodiment, such as Figure 5As shown, based on the floor component relationship table, the page component information of the floor is obtained, and the page components of the floor are overridden in terms of content. This includes: based on the floor component relationship table, obtaining a page component that is compatible with the floor, wherein there is at least one page component; based on the attribute information of the page component, determining whether the page component is restricted to a specific user group; if the page component is restricted to a specific user group, determining whether the user group included in the page generation request matches the user group restricted by the page component; if the user group included in the page generation request does not match the user group restricted by the page component, discarding the page component; otherwise, retaining the page component.

[0070] In one embodiment, based on the floor component relationship table, obtaining the page component information of the floor and performing content coverage on the page components of the floor further includes: obtaining the reserved page components and determining whether the number of page components is one; if the number of page components is not one, randomly distributing the page components to the floor, obtaining the business impact of each page component in a closed loop, obtaining the page component corresponding to the optimal value of the business impact, and performing content coverage on the floor based on the page components; if the number of page components is one, performing content coverage on the floor based on the page components.

[0071] In one embodiment, the method further includes: generating a preset page skeleton resource library; such as Figure 6 As shown, generating the preset page skeleton resource library includes: overriding styles on page units in the page skeleton to obtain page unit skeletons of the page units in the page skeleton; combining the page unit skeletons to generate page component skeletons; generating page skeletons based on the page component skeletons; obtaining information identifiers of the page skeletons; grouping the page skeletons based on the information identifiers of the page skeletons to generate page skeleton groups; and generating the preset page skeleton resource library based on the page skeleton groups.

[0072] It should be understood that, although Figure 2-6 The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figure 2-6 At least some of the steps in the process may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.

[0073] In one embodiment, such as Figure 7 As shown, a page generation apparatus is provided, comprising: an execution unit, an acquisition unit, and a content overlay unit, wherein:

[0074] An execution unit, in response to a page generation request, performs a hit experiment on page skeletons in a preset page skeleton resource library based on the page generation request, obtains the page skeletons hit by the page generation request, and generates a page skeleton dataset, wherein the page skeleton is at least one.

[0075] The acquisition unit is used to acquire a page skeleton that satisfies the page generation request from the page skeleton dataset according to a preset funnel filtering rule, and to define the page skeleton as a base page skeleton.

[0076] The content overlay unit is used to overlay the page components and page units of the page according to a preset page skeleton hierarchy, based on the basic page skeleton and the page generation request, in order to generate the page.

[0077] In one embodiment, the acquisition unit is further configured to acquire the page generation request, the page generation request including client type, page type, page generation request issuance time, and user group; based on the page generation request issuance time, to select page skeletons from a preset skeleton resource library whose validity period has not exceeded the page generation request issuance time, and generate an initial page skeleton set; based on the client type and the page type, to select page skeletons from the initial page skeleton set that are compatible with both the client type and the page type, and generate a target page skeleton set.

[0078] In one embodiment, the acquisition unit is further configured to acquire attribute information of page skeletons included in the target page skeleton set, and based on the attribute information of the page skeletons, determine whether the page skeletons have user group restrictions; if the page skeletons have user group restrictions, determine whether the user group included in the page generation request conforms to the user group restrictions of the page skeletons; if the user group included in the page generation request does not conform to the user group restrictions of the page skeletons, delete the page skeletons from the page skeleton set and update the target page skeleton set.

[0079] In one embodiment, the acquisition unit is further configured to randomly publish page skeletons contained in the target page skeleton set to the client, wherein there is at least one page skeleton; acquire the business impact of each page skeleton in a closed loop; discard page skeletons whose business impact does not meet the preset business impact requirements, and update the target page skeleton set.

[0080] In one embodiment, the acquisition unit is further configured to acquire a page generation request, the page generation request including a page skeleton application scenario, the page skeleton application scenario including a mobile phone brand, an application, and a delivery entry point; based on the page skeleton application scenario, determine whether there is a page skeleton in the target skeleton that is compatible with the mobile phone brand, the page skeleton that is compatible with the mobile phone brand including a specific page skeleton and a default page skeleton; when there is a specific page skeleton in the target skeleton that is compatible with the mobile phone brand, the default page skeleton is discarded and the target page skeleton set is updated; when there is no specific page skeleton in the target skeleton that is compatible with the mobile phone brand, the default page skeleton is retained and the target page skeleton set is updated.

[0081] In one embodiment, the acquisition unit is further configured to acquire the page skeleton corresponding to the maximum preset weight value based on the preset weight value of the page skeletons in the target page skeleton set, wherein the preset weight value is unique; and define the page skeleton as a basic page skeleton, wherein the basic page skeleton is one.

[0082] In one embodiment, the content overlay unit is further configured to: obtain a page floor framework associated with the basic page skeleton based on the basic page skeleton, wherein the validity period of the page floor framework does not exceed the time when the page generation request is issued; traverse each floor in the page floor framework based on the page floor framework to obtain a floor component relationship table for the floor; obtain page components adapted to the floor based on the floor component relationship table, perform content overlay on the page components of the floor, and obtain a component unit relationship table for the page components based on the page components; obtain page unit information of the page components based on the component unit relationship table, and perform content overlay on the page units of the page components to generate the page.

[0083] In one embodiment, the content overlay unit is further configured to: obtain a page component adapted to the floor based on the floor component relationship table, wherein the page component is at least one; determine whether the page component is restricted to a user group based on the attribute information of the page component; if the page component is restricted to a user group, determine whether the user group included in the page generation request conforms to the user group restricted by the page component; if the user group included in the page generation request does not conform to the user group restricted by the page component, discard the page component; otherwise, retain the page component.

[0084] In one embodiment, the content coverage unit is further configured to obtain the reserved page components, determine whether the number of page components is one; if the number of page components is not one, randomly distribute the page components to the floor, obtain the business impact of each page component in a closed loop, obtain the page component corresponding to the optimal value of the business impact, and perform content coverage on the floor based on the page components; if the number of page components is one, perform content coverage on the floor based on the page components.

[0085] For specific limitations regarding the page generation device, please refer to the limitations on the page generation method above, which will not be repeated here. Each module in the aforementioned page generation device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0086] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 8 As shown, the computer device includes a processor, memory, network interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The network interface is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements a page generation method. The display screen can be an LCD screen or an e-ink display screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the computer device casing, or an external keyboard, touchpad, or mouse.

[0087] Those skilled in the art will understand that Figure 8 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0088] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to perform the following steps:

[0089] In response to a page generation request, a hit experiment is performed on page skeletons in a preset page skeleton resource library based on the page generation request to obtain the page skeletons hit by the page generation request and generate a page skeleton dataset, wherein the page skeleton is at least one;

[0090] According to the preset funnel filtering rules, obtain the page skeleton that satisfies the page generation request from the page skeleton dataset, and define the page skeleton as the basic page skeleton;

[0091] Based on the basic page skeleton and the page generation request, the page components and page units of the page are overwritten with content according to the preset page skeleton hierarchy to generate the page.

[0092] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0093] The process involves obtaining the page generation request, which includes the client type, page type, page generation request issuance time, and user group; based on the page generation request issuance time, selecting page skeletons from a preset skeleton resource library whose validity period has not exceeded the page generation request issuance time to generate an initial page skeleton set; and based on the client type and the page type, selecting page skeletons from the initial page skeleton set that are compatible with both the client type and the page type to generate a target page skeleton set.

[0094] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0095] Obtain the attribute information of the page skeletons contained in the target page skeleton set. Based on the attribute information of the page skeletons, determine whether the page skeletons have user group restrictions. If the page skeletons have user group restrictions, determine whether the user group included in the page generation request meets the user group restrictions of the page skeletons. If the user group included in the page generation request does not meet the user group restrictions of the page skeletons, delete the page skeletons from the page skeleton set and update the target page skeleton set.

[0096] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0097] Randomly publish the page skeletons contained in the target page skeleton set to the client, wherein there is at least one page skeleton; obtain the business impact of each page skeleton in a closed loop; discard page skeletons whose business impact does not meet the preset business impact requirements, and update the target page skeleton set.

[0098] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0099] A page generation request is retrieved, which includes a page skeleton application scenario, comprising a mobile phone brand, an application, and a targeting entry point. Based on the page skeleton application scenario, it is determined whether a page skeleton adapted to the mobile phone brand exists in the target skeleton. The page skeleton adapted to the mobile phone brand includes a specific page skeleton and a default page skeleton. If a specific page skeleton adapted to the mobile phone brand exists in the target skeleton, the default page skeleton is discarded, and the target page skeleton set is updated. If no specific page skeleton adapted to the mobile phone brand exists in the target skeleton, the default page skeleton is retained, and the target page skeleton set is updated.

[0100] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0101] Based on the preset weight values ​​of the page skeletons in the target page skeleton set, where each preset weight value is unique, obtain the page skeleton corresponding to the maximum preset weight value, and define the page skeleton as the basic page skeleton, where the basic page skeleton is one.

[0102] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0103] Based on the basic page skeleton, obtain the page floor framework associated with the basic page skeleton, wherein the validity period of the page floor framework does not exceed the time when the page generation request is sent; based on the page floor framework, traverse each floor in the page floor framework and obtain the floor component relationship table of the floor; based on the floor component relationship table, obtain the page component that matches the floor, perform content overlay on the page component of the floor, and based on the page component, obtain the component unit relationship table of the page component; based on the component unit relationship table, obtain the page unit information of the page component, perform content overlay on the page unit of the page component to generate the page.

[0104] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0105] Based on the floor component relationship table, obtain a page component that matches the floor, wherein there is at least one page component; based on the attribute information of the page component, determine whether the page component is restricted to a user group; if the page component is restricted to a user group, determine whether the user group included in the page generation request matches the user group restricted by the page component; if the user group included in the page generation request does not match the user group restricted by the page component, discard the page component; otherwise, retain the page component.

[0106] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0107] Obtain the reserved page components and determine whether the number of page components is one; if the number of page components is not one, randomly distribute the page components to the floor, obtain the business impact of each page component in a closed loop, obtain the page component corresponding to the optimal value of the business impact, and perform content coverage on the floor based on the page components; if the number of page components is one, perform content coverage on the floor based on the page components.

[0108] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0109] In response to a page generation request, a hit experiment is performed on page skeletons in a preset page skeleton resource library based on the page generation request to obtain the page skeletons hit by the page generation request and generate a page skeleton dataset, wherein the page skeleton is at least one;

[0110] According to the preset funnel filtering rules, obtain the page skeleton that satisfies the page generation request from the page skeleton dataset, and define the page skeleton as the basic page skeleton;

[0111] Based on the basic page skeleton and the page generation request, the page components and page units of the page are overwritten with content according to the preset page skeleton hierarchy to generate the page.

[0112] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0113] The process involves obtaining the page generation request, which includes the client type, page type, page generation request issuance time, and user group; based on the page generation request issuance time, selecting page skeletons from a preset skeleton resource library whose validity period has not exceeded the page generation request issuance time to generate an initial page skeleton set; and based on the client type and the page type, selecting page skeletons from the initial page skeleton set that are compatible with both the client type and the page type to generate a target page skeleton set.

[0114] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0115] Obtain the attribute information of the page skeletons contained in the target page skeleton set. Based on the attribute information of the page skeletons, determine whether the page skeletons have user group restrictions. If the page skeletons have user group restrictions, determine whether the user group included in the page generation request meets the user group restrictions of the page skeletons. If the user group included in the page generation request does not meet the user group restrictions of the page skeletons, delete the page skeletons from the page skeleton set and update the target page skeleton set.

[0116] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0117] Randomly publish the page skeletons contained in the target page skeleton set to the client, wherein there is at least one page skeleton; obtain the business impact of each page skeleton in a closed loop; discard page skeletons whose business impact does not meet the preset business impact requirements, and update the target page skeleton set.

[0118] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0119] A page generation request is obtained, which includes a page skeleton application scenario, comprising a mobile phone brand, an application, and a targeting entry point. Based on the page skeleton application scenario, it is determined whether a page skeleton adapted to the mobile phone brand exists in the target skeleton. The page skeleton adapted to the mobile phone brand includes a specific page skeleton and a default page skeleton. When a specific page skeleton adapted to the mobile phone brand exists in the target skeleton, the default page skeleton is discarded, and the target page skeleton set is updated. When no specific page skeleton adapted to the mobile phone brand exists in the target skeleton, the default page skeleton is retained, and the target page skeleton set is updated.

[0120] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0121] Based on the preset weight values ​​of the page skeletons in the target page skeleton set, where each preset weight value is unique, obtain the page skeleton corresponding to the maximum preset weight value, and define the page skeleton as the basic page skeleton, where the basic page skeleton is one.

[0122] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0123] Based on the basic page skeleton, obtain the page floor framework associated with the basic page skeleton, wherein the validity period of the page floor framework does not exceed the time when the page generation request is sent; based on the page floor framework, traverse each floor in the page floor framework and obtain the floor component relationship table of the floor; based on the floor component relationship table, obtain the page component that matches the floor, perform content overlay on the page component of the floor, and based on the page component, obtain the component unit relationship table of the page component; based on the component unit relationship table, obtain the page unit information of the page component, perform content overlay on the page unit of the page component to generate the page.

[0124] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0125] Based on the floor component relationship table, obtain a page component that matches the floor, wherein there is at least one page component; based on the attribute information of the page component, determine whether the page component is restricted to a user group; if the page component is restricted to a user group, determine whether the user group included in the page generation request matches the user group restricted by the page component; if the user group included in the page generation request does not match the user group restricted by the page component, discard the page component; otherwise, retain the page component.

[0126] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0127] Obtain the reserved page components and determine whether the number of page components is one; if the number of page components is not one, randomly distribute the page components to the floor, obtain the business impact of each page component in a closed loop, obtain the page component corresponding to the optimal value of the business impact, and perform content coverage on the floor based on the page components; if the number of page components is one, perform content coverage on the floor based on the page components.

[0128] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0129] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0130] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A page generation method, characterized in that, The method includes: In response to a page generation request, a hit experiment is performed on the page skeletons in the preset page skeleton resource library based on the page generation request to obtain the page skeletons hit by the page generation request and generate a target page skeleton set, wherein the page skeleton is at least one; According to a preset funnel filtering rule, page skeletons that satisfy the page generation request are obtained from the target page skeleton set, including: obtaining attribute information of the page skeletons contained in the target page skeleton set; based on the attribute information of the page skeletons, determining whether the page skeletons have user group restrictions; if the page skeletons have user group restrictions, determining whether the user group included in the page generation request conforms to the user group restrictions of the page skeletons; if the user group included in the page generation request does not conform to the user group restrictions of the page skeletons, deleting the page skeletons from the target page skeleton set and updating the target page skeleton set; defining the page skeletons that satisfy the page generation request as base page skeletons. Based on the basic page skeleton and the page generation request, the page components and page units of the page are overwritten with content according to the preset page skeleton hierarchy to generate the page.

2. The page generation method according to claim 1, characterized in that, Based on the page generation request, a hit experiment is performed on the page skeletons in the preset page skeleton resource library to obtain the page skeletons that the page generation request hits, including: Obtain the page generation request, which includes the client type, page type, page generation request sending time, and user group. Based on the page generation request sending time, page skeletons with a validity period not exceeding the page generation request sending time are selected from the preset page skeleton resource library to generate an initial page skeleton set; Based on the client type and the page type, page skeletons that are compatible with both the client type and the page type are selected from the initial page skeleton set to generate a target page skeleton set.

3. The page generation method according to claim 2, characterized in that, According to a preset funnel filtering rule, the method further includes obtaining page skeletons that satisfy the page generation request from the target page skeleton set, and also includes: Randomly publish the page skeletons contained in the target page skeleton set to the client, wherein there is at least one page skeleton; The business impact of each page skeleton is obtained in a closed loop; Discard page skeletons whose business impact does not meet the preset business impact requirements, and update the target page skeleton set.

4. The page generation method according to claim 3, characterized in that, According to a preset funnel filtering rule, the method further includes obtaining page skeletons that satisfy the page generation request from the target page skeleton set, and also includes: Obtain a page generation request, the page generation request including a page skeleton application scenario, the page skeleton application scenario including mobile phone brand, application, and advertising entry point; Based on the application scenario of the page skeleton, it is determined whether there is a page skeleton that is compatible with the mobile phone brand in the target page skeleton set. The page skeleton that is compatible with the mobile phone brand includes a specific page skeleton and a default page skeleton. The specific page skeleton includes preset display content. If a specific page skeleton that is compatible with the mobile phone brand exists in the target page skeleton set, then the default page skeleton is discarded and the target page skeleton set is updated. If there is no specific page skeleton in the target page skeleton set that is compatible with the mobile phone brand, then the default page skeleton is retained and the target page skeleton set is updated.

5. The page generation method according to claim 4, characterized in that, According to a preset funnel filtering rule, the method further includes obtaining page skeletons that satisfy the page generation request from the target page skeleton set, and also includes: Based on the preset weight values ​​of the page skeletons in the target page skeleton set, where each preset weight value is unique, the page skeleton corresponding to the maximum preset weight value that satisfies the page generation request is obtained. The page skeleton corresponding to the maximum preset weight value that satisfies the page generation request is defined as the basic page skeleton, and the basic page skeleton is one.

6. The page generation method according to claim 5, characterized in that, Based on the basic page skeleton and the page generation request, and according to the preset page skeleton hierarchy, content coverage is performed on the page components and page units of the page, including: Based on the basic page skeleton, obtain the page floor frame associated with the basic page skeleton, and the validity period of the page floor frame does not exceed the time when the page generation request is sent. Based on the page floor framework, traverse each floor in the page floor framework to obtain the floor component relationship table of the floor; Based on the floor component relationship table, obtain the page components that are compatible with the floor, cover the content of the page components of the floor, and obtain the component unit relationship table of the page components based on the page components. Based on the component unit relationship table, the page unit information of the page component is obtained, and the page unit of the page component is overwritten with content to generate the page.

7. The page generation method according to claim 6, characterized in that, Based on the floor component relationship table, obtain the page component information of the floor, and perform content overwriting on the page components of the floor, including: Based on the floor component relationship table, obtain the page component that is compatible with the floor, wherein the page component is at least one; Based on the attribute information of the page component, determine whether the page component restricts the user group; If the page component has a user group restriction, then determine whether the user group included in the page generation request matches the user group restricted by the page component; If the user group included in the page generation request does not conform to the user group restricted by the page component, the page component is discarded; otherwise, the page component is retained.

8. The page generation method according to claim 7, characterized in that, Based on the floor component relationship table, the page component information of the floor is obtained, and content overlay is performed on the page components of the floor, which also includes: Obtain the retained page components and determine whether the number of the page components is one; If the number of page components is not one, the page components are randomly distributed to the floor, the business impact of each page component is obtained in a closed loop, the page component corresponding to the optimal value of the business impact is obtained, and the content is covered on the floor based on the page components. If the number of page components is one, then the content of the floor is covered based on the page components.

9. A page generation device, characterized in that, The device includes: An execution unit, in response to a page generation request, performs a hit experiment on page skeletons in a preset page skeleton resource library based on the page generation request, obtains the page skeletons hit by the page generation request, and generates a target page skeleton set, wherein the page skeleton is at least one. The acquisition unit is used to acquire page skeletons that satisfy the page generation request from the target page skeleton set according to a preset funnel filtering rule, including: acquiring attribute information of page skeletons included in the target page skeleton set; determining whether the page skeleton has user group restrictions based on the attribute information of the page skeleton; if the page skeleton has user group restrictions, determining whether the user group included in the page generation request meets the user group restrictions of the page skeleton; if the user group included in the page generation request does not meet the user group restrictions of the page skeleton, deleting the page skeleton from the target page skeleton set and updating the target page skeleton set; and defining a page skeleton that satisfies the page generation request as a base page skeleton. The content overlay unit is used to overlay the page components and page units of the page according to a preset page skeleton hierarchy, based on the basic page skeleton and the page generation request, in order to generate the page.

Images