Page generation method and device, electronic equipment and computer readable storage medium

Abstract

The embodiment of the invention discloses a page generation method and device, electronic equipment and a computer readable storage medium, and the method comprises the steps: screening and determining a to-be-configured function card set from a card pool according to a rule set of a user and user characteristics, generating page configuration information according to the to-be-configured function card set and a preset page description protocol, and generating and rendering a component tree according to the page configuration information to display a customized page of the user. Therefore, the function cards are screened in combination with the user characteristics, so that the customized page generated and rendered according to the screened to-be-configured function card set can better fit the actual situation of the user, and then the function difference of customized products can be improved.

Description

Technical Field

[0001] The present invention relates to the field of Internet technology, and in particular to a page generation method, device, electronic device and computer-readable storage medium. Background Art

[0002] For a long time, service products have provided customers with standardized products with the same user experience. However, as customer needs continue to change and become more diversified, standardized products can no longer fully meet customer expectations and needs. Products have begun to focus on building customized capabilities to meet a variety of customer needs. Compared with traditional service products, customized products can better meet customers' differentiated needs and improve customer experience and satisfaction.

[0003] Most of the existing customer service products remain at the stage of general products, which still cannot provide customized services to customers. At the same time, some existing customized products are only targeted at each specific customer, and the function page configuration information required by the customer is manually maintained, resulting in unclear differentiation of product customization functions and requiring a lot of usage and maintenance costs. Summary of the invention

[0004] In view of this, an object of the present invention is to provide a page generation method, device, electronic device and computer-readable storage medium to improve the functional differences of customized products.

[0005] In a first aspect, an embodiment of the present invention is intended to provide a page generation method, the method comprising:

[0006] Filter and determine the function card set to be configured from the card pool according to the user's rule set and user characteristics;

[0007] Generate page configuration information according to the set of function cards to be configured and in accordance with a preset page description protocol;

[0008] Generate and render a component tree according to the page configuration information to display the user's customized page.

[0009] Furthermore, the customized page includes a plurality of page areas, and the screening and determining of the function card set to be configured from the card pool according to the user's rule set and user characteristics includes:

[0010] Acquire a rule set of the user from a rule library, wherein the rule set includes at least one rule subset, and each rule subset has a corresponding page area;

[0011] Execute the rules in each rule subset based on the user characteristics of the user, and determine the execution result, wherein the execution result is used to characterize the matching degree between the user and the rule;

[0012] The set of function cards to be configured is determined according to the execution results of each of the rules.

[0013] Furthermore, each rule in the rule base is bound one-to-one with the function cards in the card pool, and determining the set of function cards to be configured according to the execution results corresponding to each rule includes:

[0014] In response to the execution result indicating that the user matches the rule, the function card bound to the corresponding rule is determined as the function card to be configured.

[0015] Furthermore, each of the rules has a priority order when being executed, and executing each of the rules based on the user characteristics of the user includes:

[0016] The rules are respectively executed based on the user characteristics of the users according to the priority order.

[0017] Furthermore, the priority order of the rules is determined based on the following steps:

[0018] Determine the corresponding rule weight according to the weight calculation of the user characteristics corresponding to each of the rules;

[0019] The corresponding priority order is determined according to the rule weight of each rule.

[0020] Furthermore, generating page configuration information according to the set of function cards to be configured according to a preset page description protocol includes:

[0021] Forming a page according to the area combination where each to-be-configured function card in the to-be-configured function card set is located;

[0022] Generate page configuration information corresponding to the page according to the page description protocol.

[0023] Further, generating and rendering a component tree according to the page configuration information to display the user's customized page includes:

[0024] Parsing the page configuration information to determine a parsing result;

[0025] Determine the component tree corresponding to the set of function cards to be configured according to the analysis result;

[0026] The component tree is rendered to display the user's customized page based on the rendered component tree.

[0027] Further, the determining, according to the parsing result, the component tree corresponding to the set of function cards to be configured comprises:

[0028] The data, events and interaction information of each component corresponding to the set of function cards to be configured are bound according to the configuration information in the parsing result to generate the component tree.

[0029] In a second aspect, an embodiment of the present invention is intended to provide a page generation device, the device comprising:

[0030] A screening unit, used to screen and determine a set of function cards to be configured from a card pool according to a set of user rules and user characteristics;

[0031] A configuration unit, configured to generate page configuration information according to the set of function cards to be configured in accordance with a preset page description protocol;

[0032] A rendering unit is used to generate and render a component tree according to the page configuration information to display the customized page of the user.

[0033] In a third aspect, an embodiment of the present invention aims to provide a computer program product, wherein the computer program product comprises a computer program / instructions, and when the computer program / instructions are executed by a processor, the method as described in any one of the above items is implemented.

[0034] In a fourth aspect, an embodiment of the present invention aims to provide an electronic device, comprising a memory and a processor, wherein the memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement a method as described in any one of the above items.

[0035] In a fifth aspect, an embodiment of the present invention aims to provide a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps as described in any one of the above items are implemented.

[0036] The technical solution of the embodiment of the present invention determines the set of function cards to be configured by screening from the card pool according to the user's rule set and user characteristics, generates page configuration information according to the set of function cards to be configured according to the preset page description protocol, generates and renders the component tree according to the page configuration information, and then displays the customized page of the user, so that the customized page formed by screening function cards in combination with user characteristics and generating and rendering according to the screened set of function cards to be configured can better fit the actual situation of the user, thereby improving the functional differences of customized products and enhancing the user's product usage experience. At the same time, the customized page generated and displayed in the above manner does not need to be manually maintained by the user through the function page configuration information required, which can reduce a lot of usage and maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The above and other objects, features and advantages of the present invention will become more apparent through the following description of the embodiments of the present invention with reference to the accompanying drawings, in which:

[0038] Figure 1 is a flow chart of a page generation method according to an embodiment of the present invention;

[0039] Figure 2 is a schematic diagram of the relationship between tags, rules, cards and pages in an embodiment of the present invention;

[0040] Figure 3 is a flow chart of determining a set of function cards to be configured according to an embodiment of the present invention;

[0041] Figure 4 is a flow chart of determining the priority order of each rule according to an embodiment of the present invention;

[0042] Figure 5 is a schematic diagram of a weight quadrant model of an embodiment of the present invention;

[0043] Figure 6 is a workflow diagram of a rule engine according to an embodiment of the present invention;

[0044] Figure 7 is a flow chart of generating page configuration information according to an embodiment of the present invention;

[0045] Figure 8 is a flow chart of generating a customized page according to an embodiment of the present invention;

[0046] Fig. 9 is a workflow diagram of a rule engine according to an embodiment of the present invention;

[0047] Fig.10 is a flow chart of a customized page generation method according to an embodiment of the present invention;

[0048] Fig.11 is a display schematic diagram of an example of a customized page according to an embodiment of the present invention;

[0049] Fig.12 is another schematic diagram showing an example of a customized page according to an embodiment of the present invention;

[0050] Fig.13 is a schematic diagram of a page generating device according to an embodiment of the present invention;

[0051] Fig.14 is another schematic diagram of the page generating device according to an embodiment of the present invention;

[0052] Fig.15 is a schematic diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0053] The present application is described below based on embodiments, but the present application is not limited to these embodiments. In the detailed description of the present application below, some specific details are described in detail. It is possible for those skilled in the art to fully understand the present application without the description of these details. In order to avoid confusing the essence of the present application, known methods, processes, flows, components and circuits are not described in detail.

[0054] In addition, persons of ordinary skill in the art will appreciate that the drawings provided herein are for illustration purposes and are not necessarily drawn to scale.

[0055] Unless the context clearly requires otherwise, the words "include", "comprising" and similar words throughout the application should be interpreted as including rather than exclusive or exhaustive; that is, the meaning is "including but not limited to".

[0056] In the description of this application, it should be understood that the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In addition, in the description of this application, unless otherwise specified, the meaning of "plurality" is two or more.

[0057] The solutions described in this specification and in the examples, if they involve the processing of personal information, will be processed on the premise of having a legal basis (such as obtaining the consent of the subject of personal information, or being necessary for the performance of a contract, etc.), and will only be processed within the scope of regulations or agreements. If a user refuses to process personal information other than the necessary information for basic functions, it will not affect the user's use of basic functions.

[0058] The groups targeted by existing customized services usually include individual users and corporate users. Taking corporate users as an example, customized products for corporate services usually manually maintain the configuration information of the functional pages required by the enterprise for each specific corporate user. When a corporate user enters the product service, the page configuration is first obtained based on the corporate ID, and the front end displays the corresponding page content based on the configuration information issued. Although this can meet the customization needs of the enterprise to a certain extent, the functional differentiation of customized products is not obvious, and it is difficult to meet the differentiated needs displayed for different corporate portrait characteristics, and it requires a lot of usage and maintenance costs. In view of this, the embodiments of the present invention aim to provide a page generation method and device to improve the functional differentiation of customized products, thereby enhancing the user experience.

[0059] Below, the customized page generation method in this embodiment is introduced with corporate users as the target users, but it should be understood that the method in this embodiment can also be oriented to individual users to meet the customized service needs of individual users, and does not limit the object-oriented nature of the method of this application.

[0060] Figure 1 FIG. 1 is a flow chart of a page generation method according to an embodiment of the present invention. Figure 1 As shown, the page generation method in this embodiment includes the following steps.

[0061] In step S100, a set of function cards to be configured is determined by screening from a card pool according to a rule set and user characteristics of the user.

[0062] In this embodiment, the function card set to be configured is screened from the card pool according to the user's rule set and the user features in the user portrait. Among them, the rule is a combination of conditions for a specific tag value, which is used to circle a specific type of user. User features refer to the features in the user portrait, and each user feature has a corresponding tag, which is used to describe information such as the user's type and status. The tag is an abstract classification and summary of user features. The card pool includes multiple cards, each of which corresponds to an independent business function module that can be viewed and interacted with on the product page.

[0063] Figure 2 Schematic diagram of the relationship between tags, rules, cards and pages in an embodiment of the present invention. Figure 2 As shown, in this embodiment, the tags in the tag library correspond to the portraits in the user portraits. Each rule in the rule library is composed of at least one tag, an operator and a target value, and the tags, operators and target values ​​are combined through the relationship of and / or. Each rule in the rule library is bound one-to-one to the function card in the card pool, and the card bound to the rule is issued when the rule is met. Different card combinations correspond to pages showing different contents.

[0064] Optionally, the user in this embodiment is an enterprise user. When establishing a rule base, customized rules are generated through manual configuration, a set of rule bases is established, and each rule is managed by the operation work platform. When establishing a card pool, different function cards are formulated according to different user demand scenarios and put into the card pool. After the rule base and the card pool are established, each rule in the rule base is associated and bound with the function cards in the card pool according to the business operation strategy. When the binding is successful, that is, when the user characteristics of the user meet the characteristic conditions corresponding to the rule, such as when the user characteristics match the user characteristics corresponding to the rule, the bound function card is sent to the user to display, so as to realize the function of dynamically recommending cards for a certain type of segmented users.

[0065] Furthermore, in this embodiment, the rule set of each user can be determined from a pre-set rule library. By screening the rules in the rule library, a rule set that better fits the user's characteristics and meets the user's requirements can be obtained, and then the corresponding set of function cards to be configured in the user's customized page can be determined based on the rule set.

[0066] Figure 3 FIG. 1 is a flow chart of determining a set of function cards to be configured according to an embodiment of the present invention. Figure 3 As shown, in this embodiment, the function card sets to be configured corresponding to different users are determined through the following steps.

[0067] In step S110, a rule set of the user is obtained from a rule base, wherein each rule in the rule base has a corresponding user feature.

[0068] Optionally, the customized service provided in this embodiment includes two modes, one of which is to directly generate a customized page for the user based on all the acquired user features such as the user ID. The other is a user-defined mode. In the customized mode, when the user enters the product page, the system presents a variety of different feature options to the user, and generates a customized page based on the feature options provided by the user. Regardless of the mode, it is necessary to first obtain the rule set corresponding to the user from the rule library according to the user ID, so as to determine the corresponding set of function cards to be configured according to the rule set of each user.

[0069] Optionally, since the customized page finally displayed includes page areas corresponding to multiple function cards, in order to improve page generation efficiency, the rule set in this embodiment includes at least one rule subset, and each rule subset has a corresponding page area. When determining the user rule set, in this embodiment, the rule subset corresponding to each page area is first determined, and then the rule subsets are combined to determine the rule set corresponding to the user.

[0070] In step S120, the rules in each rule subset are respectively executed based on the user characteristics of the user to determine the execution result, wherein the execution result is used to characterize the matching degree between the user and the rule.

[0071] In this embodiment, when executing the rules in each rule subset, the matching degree between the user and the rule is determined based on the user characteristics of the user and the user characteristics represented by the corresponding label of the rule. For example, if all the user characteristics of user A include feature a, and rule 1 also includes feature a, it indicates that user A matches rule 1 or has a certain matching degree.

[0072] Optionally, in order to distinguish the degree of adaptation of different rules of the same type to the user, the rules in the rule subset corresponding to each page area in this embodiment have a priority order when being executed. Correspondingly, when each of the rules is executed based on the user characteristics of the user, the user characteristics required for the rule execution are obtained according to the user's access service interface, and each rule is executed based on the user characteristics of the user according to the priority order, thereby determining the degree of matching between the user and each rule.

[0073] Optionally, the rules in each rule subset of this embodiment determine the priority level according to the weight combination of the user characteristics corresponding to the rules, and execute the rules in the rule set in order from high to low priority, and give priority to determining the execution results corresponding to the rules with high priorities. Therefore, by executing the rules in order of priority, it is possible to ensure that the rules are executed in an orderly manner and avoid conflicts between the rules.

[0074] Further, in this embodiment, by Figure 4 The method shown determines the priority order of each rule, and specifically includes the following steps.

[0075] In step S121, the corresponding rule weight is determined according to the weight calculation of the user feature corresponding to each rule.

[0076] In this embodiment, when determining the weight of each rule, the rule weight of the corresponding rule can be determined according to the sum of the weights of each user feature involved in the rule. For example, assuming that rule 1 includes user features a, b and c, and the weights of user features a, b and c are a0, b0 and c0 respectively, then the rule weight of rule 1 is (a0+b0+c0).

[0077] Optionally, since different types of user characteristics have different importance to user customization requirements, in this embodiment, the rule weight corresponding to each rule is determined by a two-dimensional weight quadrant model composed of user characteristics and weight values. The structure of the weight quadrant model is as follows: Figure 5 As shown, AZ on the vertical axis in the figure represents different feature levels, and the user feature closer to the horizontal axis has a higher level, that is, the level decreases from A to Z. 100-1 on the horizontal axis represents different weights, and the weight value closer to the vertical axis is larger, that is, the weight value decreases from 100 to 1. Further, the level in this embodiment can be a business level, that is, the weight of a user feature is described by the weight value of its business level and the current level. When determining the rule weight, first determine the level of each user feature corresponding to the rule (such as level AZ), then find the weight of each user feature in the level corresponding to the user feature, and finally combine and calculate the weight of all user features corresponding to the rule to determine the weight of the corresponding rule. For example, assuming that rule 1 includes two user features a and b, user features a and b are company ID and consumption amount, respectively, where the weight of the user feature of company ID is A100, and the weight of the user feature of consumption amount is B60, then the rule weight of rule 1 is (A100+B60).

[0078] In step S122, the corresponding priority order is determined according to the rule weight of each rule.

[0079] In this embodiment, the priority order of the rules in the rule set is determined by comparing the rule weights of each rule. When comparing, the weight values ​​in the high level are compared first in the order of the user feature levels from high to low. When the weights and sums of the high level are the same, the weights and sums in the next level are compared, and so on, until the comparison results between different rules are determined. When the weights and sums of the high levels are different, the rule with the larger weight and sum has a higher priority. For example, assuming that rule 1 includes user features a1 and b2, the rule weight is (A100+B50). Rule 2 includes user features a2 and b1, and the rule weight is (A99+B60). Rule 3 includes user features a1 and b1, and the rule weight is (A100+B60). When comparing the priority order of rules 1 and 2, since level A is higher than level B, and the weight value 100 is greater than 90, it is determined that the priority of rule 1 is higher than that of rule 2. When comparing the priority order of rules 1 and 3, since the weight values ​​of the user features under level A are the same (both are 100), it is necessary to continue to compare the weight values ​​of the user features under level B. Since the weight values ​​of the user characteristics of rule 1 and rule 3 at level B are 50 and 60 respectively, it is determined that the priority of rule 1 is lower than that of rule 3, and the priority order of rules 1-3 from high to low is rule 3, rule 1 and rule 2. Therefore, in this embodiment, the rule weights of each rule are compared through the above process, and then the priority order of each rule is determined according to the comparison result of the rule weights.

[0080] In step S130, a set of function cards to be configured is determined according to the execution results corresponding to each rule.

[0081] In this embodiment, the execution result of each rule is used to characterize whether the user matches or does not match the rule. When the execution result characterizes a match, it indicates that the user feature corresponding to the rule is the same as the user feature of the user or the similarity is greater than a threshold, and the sameness or similarity may include similarity in type and / or value.

[0082] For example, assuming that the user features corresponding to rule 1 are feature a and feature b, user A's user features include features a and b, and user B's user features include features c and d, then user A matches rule 1, and user B does not match rule 1.

[0083] For another example, assuming that the user features corresponding to rule 2 are feature a and feature b, the user features of user C include features a and c, and the user features of user D include features c and d, then user C matches rule 1, and user D does not match rule 1.

[0084] For another example, assuming that the user feature corresponding to rule 3 is feature c=c1, the user features of user E include feature c=c2, the user features of user F include feature c=c3, and c1<c2<c3, and the difference between c1 and c2 is less than the preset threshold, then user E matches rule 3, and user F does not match rule 3.

[0085] Furthermore, in this embodiment, in response to the execution result indicating that the user matches the rule, the function card bound to the corresponding rule is determined as the function card to be configured. Specifically, when the execution result of the rule indicates that the current rule matches the user, the function card bound to the current rule is determined through the binding relationship between the rule and the card, and the function card is determined as the function card to be configured for the page area corresponding to the rule subset described in the current rule. In addition, after determining the function cards to be configured corresponding to each page area, the set consisting of all the function cards to be configured is determined as the set of function cards to be configured corresponding to the customized page.

[0086] Optionally, in this embodiment, the above-mentioned method for determining the function cards to be configured can be executed by a rule engine. A rule engine is a processor that automatically obtains decision results by accepting the inflow of real-time feature fact data of an enterprise and performing calculations according to defined rules. Furthermore, in this embodiment, the use of the rule engine depends on a tag library, a rule library, a card pool, and a rule executor. The policy configuration is maintained through the tag library, the rule library, and the card pool, and the rule executor calculates whether the rules match. Therefore, in this embodiment, the function cards to be configured in each page area are determined by the rule engine, and then the set of function cards to be configured corresponding to the customized page is determined through the function cards to be configured in all page areas, which is conducive to improving the efficiency of determining the set of function cards to be configured, and then improving the efficiency of generating customized pages.

[0087] Figure 6 : is a workflow diagram of the rule engine of an embodiment of the present invention. Figure 6 As shown, in this embodiment, the determination of a function card to be configured corresponding to a page area is used as an example for explanation, and the function card to be configured corresponding to the user is determined through the following steps. Among them, the rule corresponding to the function card to be configured is the rule in the rule subset that matches the user, and is the rule with the highest priority among the rules that match the user.

[0088] In step S410, a rule subset is obtained.

[0089] In this embodiment, the rule subset corresponds to the page area in the customized page. Optionally, the corresponding rule subset is obtained from the rule library according to the user identifier and the page area identifier.

[0090] In step S420, sorting is performed according to the priority order.

[0091] In this embodiment, the priority order of each rule in the rule subset is determined according to the aforementioned method, and each rule is sorted according to the priority order.

[0092] In step S430, the rules are executed sequentially.

[0093] In this embodiment, each rule in the rule set is executed in order of priority to determine whether each rule matches the user.

[0094] In step S440, it is determined whether the currently executed rule matches.

[0095] In this embodiment, whether the corresponding rule matches the user is determined according to the execution result of the rule. If it is determined that the rule matches the user, step S450 is continued to be executed; if it is determined that the rule does not match the user, step S460 is continued to be executed.

[0096] In step S450, the matching rule information is returned.

[0097] In this embodiment, when determining whether the currently executed rule matches, it indicates that the currently executed rule is the rule with the highest priority that matches the user in the rule subset, and the rule can be used as the target rule for the corresponding page area, and the matching rule information is returned.

[0098] In step S460, it is determined whether the currently executed rule is the last rule.

[0099] In this embodiment, when the currently executed rule does not match, the rule with the highest priority that matches the user in the rule subset is screened by continuing to execute other rules in the rule subset. Optionally, in this embodiment, by determining whether the currently executed rule is the last rule, the determination of the execution results of other rules in the rule subset is triggered. Specifically, when it is determined that the currently executed rule is the last rule, it indicates that all rules in the corresponding page area in the rule subset have been executed, and step S480 is continued. When it is determined that the currently executed rule is not the last rule, it indicates that all rules in the rule set have not been fully executed, and step S470 is continued.

[0100] In step S470, the next rule is executed.

[0101] In this embodiment, when it is determined that the currently executed rule is not the last rule, the rules with a priority after the currently executed rule continue to be executed in order of priority, and after the execution of the next rule is completed, the process returns to step S440 until all rules in the rule set are executed.

[0102] In step S480, a matching failure result is returned.

[0103] In this embodiment, when it is determined that the currently executed rule does not match, it indicates that there is no longer a rule matching the user in the currently executed rule subset, and the matching rule information is returned.

[0104] Optionally, in this embodiment, after determining that there are no rules matching the user in the current rule subset, the rules in the rule subset can be re-screened by modifying or adding rules, adjusting matching similarity, or other methods; the screening of rules in the current rule subset can also be canceled according to the actual application scenario requirements.

[0105] The technical solution of this embodiment obtains a rule subset, executes each rule in order of priority, determines the rule with the highest priority that matches the user from the rule subset, and then determines the function card to be configured in the page area corresponding to the rule subset based on the binding relationship between the rule and the card. This is beneficial to improving the efficiency of determining the set of function cards to be configured corresponding to the customized page, and then improving the efficiency of generating customized pages.

[0106] In step S200, page configuration information is generated according to a set of function cards to be configured in accordance with a preset page description protocol.

[0107] In this embodiment, after determining the set of function cards to be configured corresponding to the customized page, since the information in the function cards to be configured cannot be directly displayed, page configuration information corresponding to the set of function cards to be configured is generated according to a preset page description protocol.

[0108] Figure 7 FIG. 1 is a flow chart of generating page configuration information according to an embodiment of the present invention. Figure 7 As shown, in this embodiment, page configuration information for the user is generated according to the following steps.

[0109] In step S210, a page is formed according to the area combination where each to-be-configured function card in the to-be-configured function card set is located.

[0110] In this embodiment, after the execution of each rule in the rule set is completed, according to the execution result calculated by the rule engine, the function cards bound to the rules with matching execution results are combined into a page according to the different areas where they are located. That is, a page is formed according to the area combination where each function card to be configured in the function card set to be configured is located, providing an overall framework for the customized page formed later.

[0111] In step S220, page configuration information corresponding to the page is generated according to the page description protocol.

[0112] In this embodiment, after the overall framework of the customized page is formed, in order to facilitate the use and display of the corresponding information of the function card, the page configuration information corresponding to the page will be generated according to the page description protocol. Optionally, in this embodiment, the standardized schema page configuration description protocol is used to generate the page configuration information in JSON format, so as to convert the card function information in text format through the page description protocol, facilitate the information transmission and function realization between the back-end page configuration and the front-end page display, and thus improve the generation efficiency of the customized page.

[0113] The technical solution of this embodiment forms a page according to the area composition of each function card to be configured, and generates page configuration information according to a standardized page description protocol. It can issue a page template for a customized page, fill in the card information according to the page template, and provide users with customized pages to meet users' product customization needs and enhance users' product usage experience.

[0114] In step S300, a component tree is generated and rendered according to the page configuration information to display the user's customized page.

[0115] In this embodiment, after the front end receives the page configuration information sent by the back end, it generates and renders a component tree according to the page configuration information, and then displays the user's customized page through the component tree.

[0116] Figure 8 is a flow chart of generating a customized page according to an embodiment of the present invention. Figure 8 As shown, in this embodiment, a customized page for a user is generated according to the following steps.

[0117] In step S310, the page configuration information is parsed to determine the parsing result.

[0118] In this embodiment, by parsing the page configuration information sent by the backend, the parsing result of each function card as a component node is determined, so as to determine the component tree including all function cards corresponding to the customized page according to the parsing result.

[0119] In step S320, the component tree corresponding to the function card set to be configured is determined according to the parsing result.

[0120] In this embodiment, the data, events and interaction information of each component corresponding to the set of function cards to be configured are bound according to the configuration information in the parsing result to generate a component tree.

[0121] Optionally, in this embodiment, each function card node is processed as a component by recursive traversal, and the data, interaction and events of the component are bound according to the node configuration information until all nodes are traversed, and finally a complete component tree is generated.

[0122] In step S330, the component tree is rendered to display the user's customized page based on the rendered component tree.

[0123] In this embodiment, after constructing the component tree corresponding to the set of function cards to be configured, a customized page for a specific user to be displayed is generated by rendering the component tree.

[0124] The technical solution of the embodiment of the present invention determines the set of function cards to be configured by screening from the card pool according to the user's rule set and user characteristics, generates page configuration information according to the set of function cards to be configured according to the preset page description protocol, generates and renders the component tree according to the page configuration information, and then displays the customized page of the user, so that the customized page formed by screening function cards in combination with user characteristics and generating and rendering according to the screened set of function cards to be configured can better fit the actual situation of the user, thereby improving the functional differences of customized products and enhancing the user's product usage experience. At the same time, the customized page generated and displayed in the above manner does not need to be manually maintained by the user through the function page configuration information required, which can reduce a lot of usage and maintenance costs.

[0125] Optionally, in this embodiment, a component tree is generated and rendered by a rendering engine, and then the user's customized page is displayed. The rule engine is a processor that converts page configuration template data into a visual page, and is used to process aspects such as page layout, style, data, and interactive logic. Furthermore, the rendering engine in this embodiment mainly includes a component library, a data source, an event pool, and a template interpreter module. The component library, the data source, and the event pool are the infrastructure of the front-end engineering, and the functions are decoupled to facilitate the customization and expansion of the card. The template interpreter is used to render the template data into a page.

[0126] Fig. 9 : is a workflow diagram of the rule engine of an embodiment of the present invention. Fig. 9 As shown, in this embodiment, the component tree is generated and rendered through the following steps.

[0127] In step S510, the page template is parsed.

[0128] In this embodiment, after receiving the page configuration information of the page template corresponding to the set of function cards to be configured sent by the backend, the front end will parse the page configuration information to determine the configuration information of the components corresponding to each function card.

[0129] In step S520, recursion starts.

[0130] In this embodiment, each function card component in the function card set to be configured is processed in a recursive manner.

[0131] In step S530, component processing is performed.

[0132] In this embodiment, when processing each component, steps S531-S533 are executed. In step S531, data is bound; in step S532, interaction is bound; and in step S533, events are bound.

[0133] In step S540, the error boundary is wrapped.

[0134] In this embodiment, the error boundary (i.e., Error Boundary) is a React component that can capture and print JavaScript errors that occur anywhere in its subcomponent tree and render a backup UI. The error boundary captures errors during rendering, in the life cycle, and in the constructor of the entire component tree. Thus, the error boundary wrapping operation is used to prevent errors that occur in a component during processing and rendering, which causes the entire component tree to be completely uninstalled, which is conducive to improving the generation and rendering efficiency of the component tree, and thus improving the efficiency of customized page generation.

[0135] In step S550, it is determined whether the recursion is completed.

[0136] In this embodiment, when it is determined that the recursion is completed, it indicates that the components in the function card set to be configured have been processed, and then step S560 is continued to be executed; when it is determined that the recursion is not completed, it indicates that the components in the function card set to be configured have not been processed, and then step S530 is returned to be executed.

[0137] In step S560, a component tree is generated.

[0138] In this embodiment, after traversing the nodes corresponding to all function cards in the set of function cards to be configured, a component tree is generated according to all processed card nodes.

[0139] In step S570, the page is rendered.

[0140] In this embodiment, after the component tree is generated, the component tree is rendered, and then the rendering of the customized page is completed, and an exclusive customized page is presented to the user to meet the customization requirements.

[0141] The technical solution of this embodiment is to determine the node configuration information of the components corresponding to each function card by parsing the page template after receiving the page configuration information of the page template, and process each component in turn in a recursive manner, bind the data, interaction and event of the component according to the node configuration information, until all nodes are traversed, generate the component tree corresponding to the set of function cards to be configured, and then render the component tree to generate a customized page for the current user, which can improve the functional differentiation of customized products while meeting the user's customization needs, and further enhance the user's product experience. At the same time, the customized page generated and displayed in the above manner does not need to manually maintain the function page configuration information required by the user, which can reduce a lot of usage and maintenance costs.

[0142] Fig.10 : is a flow chart of a customized page generation method according to an embodiment of the present invention. Fig.10 As shown, in this embodiment, when generating a customized page for a user, first obtain multiple customized rules in the rule library corresponding to the operation workbench and user characteristics corresponding to the user portrait of the target user (such as enterprise scale, recharge / consumption parameters, service activation content), filter the rules in the rule library according to the user characteristics of the target user to determine the rule set required for the customized page for the target user, execute each rule through the rule engine to determine the rule matching the target user from the rule set, and then determine the function card to be configured corresponding to each matching rule according to the binding relationship between the rule and the card, and determine the page template of the customized page according to the page area where each function card to be configured is located. After that, the function information of the function card in the function card set to be configured is converted into a format using the standardized schema page configuration description protocol to generate page configuration information in JSON format. The rendering engine parses the received page configuration information, processes and assembles the component nodes corresponding to each function card to be configured in combination with the component library, data source and event pool, generates a complete component tree, and renders the component tree. Finally, the page corresponding to the component tree after rendering is used as the customized function set page for the target user. Therefore, the technical solution of this embodiment starts with customized rules, and uses its own rule engine and rendering engine, as well as the establishment of business rule strategies to display different function sets for users with different characteristics, so that each customized page generated can better fit the user's actual situation and meet the different needs of different users for customized service functions, thereby improving the user experience of complex systems.

[0143] Fig.11 is a schematic diagram showing an example of a customized page according to an embodiment of the present invention. Fig.11As shown, the customized page in this embodiment displays multiple card functions, and users view corresponding data and events through the card function information displayed in different areas. In addition, the customized page in this embodiment also provides option controls (such as recharge, view details, etc.) in different regional card function parts. Users can enter the next level page by clicking the option control in the page and perform corresponding operations according to the displayed content. Therefore, in this embodiment, for different types of enterprises, the most relevant functions and services can be recommended to them according to the service categories they use (such as car use or business travel, etc.), and customized pages for corresponding users can be displayed. While improving the differentiation of user customized service product demand differences and user product usage experience, it can also provide users with convenient operation methods and comprehensive usage functions, thereby improving the convenience of user operation and product usage efficiency.

[0144] Fig.12 FIG. 1 is another schematic diagram showing an example of a customized page according to an embodiment of the present invention. Fig.12 As shown, in addition to displaying various card functions and operation option controls in different areas, the customized page in this embodiment can also display configuration guidance content (such as the business travel quick configuration shown in the figure). Therefore, for novice enterprise administrators, the most suitable functions and operation instructions can be recommended to them based on their registration information to help enterprises get started quickly. While improving the differentiation of user customized service product demand differences and improving user product usage experience, it can also provide convenient operation methods and comprehensive usage functions for users of different usage types, further improving the convenience of user operation and product usage efficiency.

[0145] Fig.13 Schematic diagram of a page generation device according to an embodiment of the present invention. Fig.13 As shown, the page generation device in this embodiment includes a screening unit 1, a configuration unit 2 and a rendering unit 3. Among them, the screening unit 1 is used to screen and determine the function card set to be configured from the card pool according to the user's rule set and user characteristics. The configuration unit 2 is used to generate page configuration information according to the function card set to be configured according to the preset page description protocol. The rendering unit 3 is used to generate and render a component tree according to the page configuration information to display the customized page of the user.

[0146] Fig.14 FIG. 2 is another schematic diagram of a page generation device according to an embodiment of the present invention. Fig.14As shown, the screening unit 1 in this embodiment includes an acquisition module 11, an execution module 12 and a determination module 13. Among them, the acquisition module 11 is used to obtain the rule set of the user from the rule base, and each rule in the rule base has a corresponding user feature. The execution module 12 is used to execute each of the rules based on the user's user features, determine the execution result, and the execution result is used to characterize the degree of match between the user and the rule. The determination module 13 is used to determine the set of function cards to be configured according to the execution results corresponding to each of the rules. Optionally, in this embodiment, each rule has a priority order when executed, and the execution module 12 is specifically used to execute each of the rules based on the user's user features according to the priority order. Furthermore, each rule in the rule base in this embodiment is bound one-to-one to the function card in the card pool, and the determination module 13 is specifically used to determine that the function card bound to the corresponding rule is the function card to be configured in response to the execution result characterizing that the user matches the rule.

[0147] Optionally, the configuration unit 2 in this embodiment is specifically used to form a page according to the area combination where each to-be-configured function card in the to-be-configured function card set is located, and generate page configuration information corresponding to the page according to a page description protocol.

[0148] Optionally, the rendering unit 3 in this embodiment includes a parsing module 31, an assembling module 32 and a rendering module 33. Among them, the parsing module 31 is used to parse the page configuration information and determine the parsing result. The assembling module 32 is used to determine the component tree corresponding to the set of function cards to be configured according to the parsing result. The rendering module 33 is used to render the component tree to display the user's customized page based on the rendered component tree. Furthermore, the assembling module 32 is specifically used to bind the data, events and interaction information of each component corresponding to the set of function cards to be configured according to the configuration information in the parsing result to generate the component tree.

[0149] Fig.15 Schematic diagram of an electronic device according to an embodiment of the present invention. Fig.15 As shown, Fig.15The electronic device shown is a general address query device, which includes a general computer hardware structure, which at least includes a processor 41 and a memory 42. The processor 41 and the memory 42 are connected via a bus 43. The memory 42 is suitable for storing instructions or programs executable by the processor 41. The processor 41 can be an independent microprocessor or a collection of one or more microprocessors. Thus, the processor 41 executes the instructions stored in the memory 42, thereby executing the method flow of the embodiment of the present invention as described above to realize the processing of data and the control of other devices. The bus 43 connects the above-mentioned multiple components together, and at the same time connects the above-mentioned components to the display controller 44 and the display device and the input / output (I / O) device 45. The input / output (I / O) device 45 can be a mouse, a keyboard, a modem, a network interface, a touch input device, a somatosensory input device, a printer, and other devices known in the art. Typically, the input / output device 45 is connected to the system via an input / output (I / O) controller 46.

[0150] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, devices (equipment) or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, the present application may adopt a computer program product implemented on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0151] The present application is described with reference to flowcharts of methods, apparatuses (devices) and computer program products according to embodiments of the present application. It should be understood that each process in the flowchart can be implemented by computer program instructions.

[0152] These computer program instructions may be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device that implements the process Figure 1 A function specified in a process or multiple processes.

[0153] These computer program instructions may also be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce the instructions for implementing the process Figure 1 A device that specifies functions in a process or multiple processes.

[0154] Another embodiment of the present invention relates to a non-volatile storage medium for storing a computer-readable program, wherein the computer-readable program is used for a computer to execute part or all of the above method embodiments.

[0155] That is, those skilled in the art can understand that all or part of the steps in the above-mentioned embodiment method can be completed by specifying relevant hardware through a program, and the program is stored in a storage medium, including several instructions for a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0156] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A page generation method, characterized in that: The method comprises: Filter and determine the function card set to be configured from the card pool according to the user's rule set and user characteristics; Generate page configuration information according to the set of function cards to be configured and in accordance with a preset page description protocol; Generate and render a component tree according to the page configuration information to display the user's customized page.

2. The method according to claim 1, characterized in that The customized page includes multiple page areas, and the function card set to be configured is screened and determined from the card pool according to the user's rule set and user characteristics, including: Acquire a rule set of the user from a rule library, wherein the rule set includes at least one rule subset, and each rule subset has a corresponding page area; Execute the rules in each rule subset based on the user characteristics of the user, and determine the execution result, wherein the execution result is used to characterize the matching degree between the user and the rule; The set of function cards to be configured is determined according to the execution results of each of the rules.

3. The method according to claim 2, characterized in that Each rule in the rule base is bound one-to-one with the function cards in the card pool, and determining the set of function cards to be configured according to the execution results corresponding to each rule includes: In response to the execution result indicating that the user matches the rule, the function card bound to the corresponding rule is determined as the function card to be configured.

4. The method according to claim 2, characterized in that: The rules have a priority order when being executed, and the executing the rules based on the user characteristics of the user includes: The rules are respectively executed based on the user characteristics of the users according to the priority order.

5. The method according to claim 4, characterized in that The priority order of the rules is determined based on the following steps: Determine the corresponding rule weight according to the weight calculation of the user characteristics corresponding to each of the rules; The corresponding priority order is determined according to the rule weight of each rule.

6. The method according to claim 1, characterized in that The step of generating page configuration information according to the set of function cards to be configured and in accordance with a preset page description protocol includes: Forming a page according to the area combination where each to-be-configured function card in the to-be-configured function card set is located; Generate page configuration information corresponding to the page according to the page description protocol.

7. The method according to claim 1, characterized in that The generating and rendering a component tree according to the page configuration information to display the user's customized page includes: Parsing the page configuration information to determine a parsing result; Determine the component tree corresponding to the set of function cards to be configured according to the analysis result; The component tree is rendered to display the user's customized page based on the rendered component tree.

8. The method according to claim 7, characterized in that Determining the component tree corresponding to the set of function cards to be configured according to the parsing result includes: The data, events and interaction information of each component corresponding to the set of function cards to be configured are bound according to the configuration information in the parsing result to generate the component tree.

9. A page generating device, characterized in that: The device comprises: A screening unit, used to screen and determine a set of function cards to be configured from a card pool according to a set of user rules and user characteristics; A configuration unit, configured to generate page configuration information according to the set of function cards to be configured in accordance with a preset page description protocol; A rendering unit is used to generate and render a component tree according to the page configuration information to display the customized page of the user.

10. A computer program product, characterized in that The computer program product comprises a computer program / instructions, and when the computer program / instructions are executed by a processor, the method according to any one of claims 1 to 8 is implemented.

11. An electronic device comprising a memory and a processor, characterized in that: The memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method according to any one of claims 1 to 8.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps of any one of claims 1 to 8 are implemented.

Images