APP page management system and method and medium

Abstract

The invention provides an APP page management system and method and a medium, and the system comprises a page management module which is used for configuring and managing page layout; the shunting rule module is used for dynamically generating page content to be displayed of the user according to the real-time data of the user; the component management module is used for configuring and managing the component content of the page according to the request of the page management module; the element management module is used for carrying out element management according to the component content of the component management module and realizing management of minimum-granularity visual elements; wherein the shunting rule module is further used for collecting behavior data of the user and automatically optimizing page content to be displayed of the user according to the behavior data; according to the method, automatic management and automatic optimization of the page can be realized, the long-term maintenance cost is reduced, and various complex business requirements can be met through flexible component combination and a dynamic content filling mechanism.

Description

Technical Field

[0001] The present application belongs to the field of APP management technology, and relates to an APP page management technology, and in particular to an APP page management system, method and medium. Background Art

[0002] With the rapid development of mobile Internet, software (AppApplication, APP) has become an important channel for enterprises to connect with users and provide services. In order to meet the diverse needs of users, App developers hope to display different page content and layout for different users, that is, to achieve a personalized experience of "one thousand faces for one thousand people".

[0003] The existing App development models are mainly the following:

[0004] 1. Fixed page structure: This is the most traditional method, where all users see the same page structure and content. For example, most early mobile banking apps adopted this method, and the interface they saw was exactly the same regardless of whether the user was a high-net-worth customer or an ordinary user.

[0005] 2. Predefined multiple templates: Some apps try to achieve simple personalized display by pre-defining multiple page templates. For example, an e-commerce app may design different homepage templates for new users and old users. This method is described in detail in the book "Mobile Application Development Practice".

[0006] 3. Server dynamic rendering: Some more advanced apps use server-side dynamic rendering to generate different page content on the server based on user attributes.

[0007] However, these development models are difficult to meet the diverse needs of users due to the limited number of templates; the maintenance costs are high, the performance cannot meet the requirements, and there is a lack of fine-grained personalization capabilities. Summary of the invention

[0008] The purpose of the present application is to provide an APP page management system, method and medium, which are used to solve the problem that the page management efficiency in the prior art is low and cannot meet the usage requirements.

[0009] In a first aspect, the present application provides an APP page management system, including:

[0010] Page management module, used to configure and manage page layout;

[0011] A traffic diversion rule module, which is in communication with the page management module and is used to dynamically generate the page content to be displayed for the user according to the user's real-time data;

[0012] A component management module, which is in communication with the page management module and is used to configure and manage the component content of the page according to the request of the page management module;

[0013] An element management module, which is in communication with the component management module and is used to manage elements according to the component content of the component management module, so as to achieve management of visual elements with minimum granularity;

[0014] The diversion rule module is also used to collect user behavior data and automatically optimize the content to be displayed on the page of the user according to the behavior data.

[0015] In an implementation of the first aspect, the page management module includes a page template unit, a layout management unit and a resource bit configuration unit. The page template unit is used to divide the resource bits to define the basic structure of the page. The resource bit configuration unit is communicatively connected to the page template unit for performing content configuration on the divided resource bits. The layout management unit is communicatively connected to the resource bit configuration unit for performing layout management on the components in the configured resource bits.

[0016] In an implementation of the first aspect, the process of the page template unit defining a basic structure of a page includes:

[0017] Divide the page into multiple resource locations, configure a corresponding component for each resource location, and set display parameters for each component;

[0018] The resource location configuration unit configures the resource location with content including location attributes, display rules, component mapping and permission control. The location attributes include the location and size of the resource location on the page, the display rules include the display method of the configuration content of the resource location, the component mapping includes the component types that can be placed in the resource location, and the permission control includes the display permission of the resource location.

[0019] In an implementation of the first aspect, the component management module includes a component construction unit, a component attribute unit and a version control unit. The component construction unit is communicatively connected to the resource position configuration unit for constructing a corresponding component for each resource position. The component attribute unit is communicatively connected to the component construction unit for configuring the attributes of the component constructed by the component construction unit. The version control unit is communicatively connected to the component construction unit for managing the version of the component constructed by the component construction unit.

[0020] In an implementation manner of the first aspect, the process of the component construction unit constructing the component corresponding to the resource bit includes:

[0021] Defining basic information of each of the components in the resource slot and configuring elements in the components;

[0022] Configure element information and layout for each of the elements, set interactive behaviors and bind data for the components, and configure the status and life cycle behaviors of the components;

[0023] Complete the registration of the component in the component library.

[0024] In an implementation of the first aspect, the basic information of the component includes a unique component identifier, a component name, a component version, a component description, a component hierarchy, and component creation information; the element information includes an element type, an element identifier, basic attributes, and a default display state; the layout of the elements includes setting a layout mode, setting an arrangement direction and alignment of the elements, and setting a spacing and margin between elements; the state configuration of the component includes defining a state variable of the component, setting an initial state value, specifying a state update mode, and configuring a processing logic for state changes; the life cycle formation configuration of the component includes setting an initialization operation of the component at creation, data loading at mounting, refresh logic at update, and cleanup at destruction; and the registration of the component includes sequentially verifying the configuration integrity of the component, generating a complete definition of the component, registering the component to a component library, and establishing index information of the component.

[0025] In an implementation of the first aspect, the properties configured for the component by the component property unit include basic properties inherited from elements within the component, the basic properties include visual properties, interaction properties, and animation properties, and the component property unit is also used to expand the properties of the component, and the extended properties of the component include business property extension and functional property extension.

[0026] In an implementation of the first aspect, when the component triggers an upgrade condition, the version control unit selects a corresponding method to manage the version of the component according to the usage of the current page, and the upgrade condition includes at least one of a change in the user's business needs, a need to update the component function, and a need to adjust the component style.

[0027] In an implementation of the first aspect, the element management module includes an element definition unit, an element attribute unit and an element behavior unit. The element definition unit is communicatively connected to the component construction unit for configuring the corresponding element of the component constructed by the component construction unit. The element attribute unit is communicatively connected to the element definition unit for setting the attributes of the element. The element behavior unit is communicatively connected to the element definition unit for configuring the trigger event of the element.

[0028] In an implementation of the first aspect, the diversion rule module includes a diversion rule setting unit and a user group division unit. The diversion rule setting unit is used to set the diversion rules for the user, and the diversion rules include customer group rules, directional rules and experimental rules. The user group division unit is used to divide the users into groups according to the diversion rules after collecting the user data. The page template unit is communicatively connected with the user group division unit to define the basic structure of the user's page according to the group division resource bits after the users are divided.

[0029] In an implementation of the first aspect, the page template unit is also used to collect user data collected by the user group segmentation unit, and obtain user characteristics, scenario characteristics and component characteristics of the user, and automatically optimize the basic structure of the user's page according to the algorithm model.

[0030] In a second aspect, the present application provides an APP page management method, including:

[0031] After receiving the page request from the client, a data request is sent to the diversion rule module through the page management module;

[0032] After receiving the data request, the diversion rule module obtains user data, and divides the user into user groups according to the user data to obtain a division result;

[0033] According to the division result, configuring the user's page through the page management module;

[0034] According to the page configuration result, after configuring the components for the resource positions of the user's page through the component management module, the element management module configures the elements according to the configured components;

[0035] According to the result of the configuration, after the corresponding page is generated by the page management module, the page is sent to the client.

[0036] In a third aspect, the present application provides a computer-readable storage medium on which a computer program is stored, which implements the above-mentioned APP page management method when executed.

[0037] As described above, the APP page management system, method and medium described in this application have the following beneficial effects:

[0038] This application scheme splits the page into more fine-grained parts: compared with traditional page-level templates, this technology realizes refined control at the component level and element level; unlike predefined templates, this scheme can dynamically generate content based on real-time data, and can realize automatic optimization of page structure through machine learning algorithms, rather than fixed manual design; at the same time, it moves part of the personalized decision logic to the client to improve response speed and offline experience, and can realize a truly "one thousand faces for one thousand people" personalized experience. Centralized component management and automated optimization processes reduce long-term maintenance costs. Flexible component combination and dynamic content filling mechanism can cope with various complex business needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 Shown is a structural block diagram of the APP page management system described in an embodiment of the present application.

[0040] Figure 2 Shown is a schematic diagram of the process of constructing components by the component construction unit in the APP page management system described in an embodiment of the present application.

[0041] Figure 3 Shown is a schematic diagram of the working process of each module in the APP page management system described in an embodiment of the present application.

[0042] Figure 4 Shown is a flowchart of the APP page management method described in an embodiment of the present application. DETAILED DESCRIPTION

[0043] The following describes the embodiments of the present application through specific examples, and those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0044] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present application, and thus the drawings only show components related to the present application rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed at will, and the component layout may also be more complicated.

[0045] See also Figures 1 to 3. The following embodiments of the present application provide an APP page management system, method and medium, which splits the page in a more fine-grained manner: compared with traditional page-level templates, this technology realizes refined control at the component level and element level; unlike predefined templates, this solution can dynamically generate content based on real-time data, and can realize automatic optimization of page structure through machine learning algorithms, rather than fixed manual design; at the same time, part of the personalized decision logic is moved forward to the client to improve the response speed and offline experience, and can realize a truly "one thousand faces for one thousand people" personalized experience, centralized component management and automated optimization process, reduce long-term maintenance costs, flexible component combination and dynamic content filling mechanism, and can cope with various complex business needs.

[0046] The technical solutions in the embodiments of the present application will be described in detail below in conjunction with the drawings in the embodiments of the present application.

[0047] This embodiment provides an APP page management system. Figure 1 ,include:

[0048] Page management module 1, used to configure and manage page layout;

[0049] A traffic diversion rule module 2 is connected to the page management module 1 for dynamically generating the page content to be displayed for the user according to the user's real-time data;

[0050] The component management module 3 is in communication with the page management module 1 and is used to configure and manage the component content of the page according to the request of the page management module 1;

[0051] An element management module 4 is connected to the component management module 3 for performing element management according to the component content of the component management module 3 to achieve management of the smallest granularity visual element;

[0052] The diversion rule module 2 is also used to collect user behavior data, and automatically optimize the content to be displayed on the page of the user according to the behavior data.

[0053] In some embodiments, the page management module 3 includes a page template unit 31, a layout management unit 32 and a resource bit configuration unit 33. The page template unit 31 is used to divide the resource bits to define the basic structure of the page. The resource bit configuration unit 33 is communicated with the page template unit 31 for performing content configuration on the divided resource bits. The layout management unit 32 is communicated with the resource bit configuration unit 33 for performing layout management on the components in the configured resource bits.

[0054] In the process of page management, the basic structure of the page is first defined by the page template unit 31, and then the resource bit configuration unit 33 configures the content of the divided resource bits according to the basic structure of the page, and the layout management unit 32 manages the layout of the components in the resource bits.

[0055] In some other embodiments, the process of the page template unit 31 defining the basic structure of the page includes:

[0056] Divide the page into multiple resource locations, configure a corresponding component for each resource location, and set display parameters for each component;

[0057] The resource location configuration unit configures the resource location with content including location attributes, display rules, component mapping and permission control. The location attributes include the location and size of the resource location on the page, the display rules include the display method of the configuration content of the resource location, the component mapping includes the component types that can be placed in the resource location, and the permission control includes the display permission of the resource location.

[0058] With respect to the page structure, from top to bottom, they are page, resource position, component and element. The page includes multiple resource positions. As a container for carrying components, the resource position can be configured with different components to provide a configurable content display area, support dynamic switching and replacement of components, and realize flexible layout and personalized display of the page. The component is the business function unit of the page. A component is composed of multiple elements, and the element is the smallest display unit of the page, including buttons and texts. When configuring the page, first divide multiple resource positions on the page, and configure the corresponding component for each resource position, and set specific display parameters for each component.

[0059] After the page template unit 31 configures the resource bits for the page, the resource bit configuration unit 33 defines the configurable content location of each resource bit, including location attributes, display rules, component mapping and permission control. The location attributes include the location and size of the resource bit on the page, the display rules include the display method of the configured content of the resource bit, such as carousel and static, the component mapping includes the component types that can be placed in the resource bit, and the permission control includes the display permission of the resource bit. After the page template unit 31 divides the page into resource bits and configures the resource bits with components, the layout management unit 32 manages the layout of the components in each resource bit, thereby facilitating the management of the components of each resource bit in the page.

[0060] In some other embodiments, the component management module 2 includes a component construction unit 21, a component attribute unit 22 and a version control unit 23. The component construction unit 21 is communicatively connected to the resource position configuration unit 33 for constructing a corresponding component for each resource position. The component attribute unit 22 is communicatively connected to the component construction unit 21 for configuring the attributes of the component constructed by the component construction unit 21. The version control unit 23 is communicatively connected to the component construction unit 21 for managing the version of the component constructed by the component construction unit 21.

[0061] In this embodiment, after the page management module 3 completes the configuration of the page structure, the component management module 2 configures and manages the components of each resource position on the page to facilitate the definition, assembly and version management of the components, which can meet the configuration requirements of different components.

[0062] Specifically, after the resource location configuration unit 33 completes the configuration of the content of each resource location of the page, the component construction unit 21 determines the component type that can be placed in each resource location according to the component mapping, and configures the component of the corresponding type on the resource location. The component attribute unit 22 is used to configure the attributes of the component constructed by the component construction 21. The attribute configuration of the component by the component attribute unit 22 comes from the inheritance of the element attributes of the component on the one hand, and from the extension of the component attributes on the other hand.

[0063] In some embodiments, reference Figure 2 The process of the component construction unit 21 constructing the component corresponding to the resource position includes:

[0064] S201, defining basic information of each of the components in the resource location, and configuring elements in the components;

[0065] S202, configuring element information and layout for each of the elements, setting interaction behaviors and binding data for the components, and configuring the status and life cycle behaviors of the components;

[0066] S203: Complete registration of the component in the component library.

[0067] Among them, the basic information of the component includes the component unique identification, component name, component version, component description, component hierarchy and component creation information; the element information includes element type, element identifier, basic attributes and default display state; the layout of the element includes setting the layout mode, setting the arrangement direction and alignment of the elements, and setting the spacing and margins between elements; the state configuration of the component includes defining the state variables of the component, setting the initial state value, specifying the state update method and configuring the processing logic of the state change; the life cycle formation configuration of the component includes setting the initialization operation of the component at creation, data loading at mounting, refresh logic at update and cleanup at destruction; the registration of the component includes verifying the configuration integrity of the component, generating a complete definition of the component, registering the component to the component library, and establishing the index information of the component.

[0068] Component construction is a process of combining basic elements into a fully functional UI unit. Specifically, in this embodiment, after the resource position configuration unit 33 completes the configuration of the resource position, the component construction unit 21 first defines the basic information of each component in the resource position, including component unique identification, component name, component version, component description, component hierarchy and component creation information, wherein the component unique identification is used to identify the component in the system, the component name is a component description for developers to understand, the component version is used for version control and management of the component, and the component description is used to explain the purpose and function of the component. Since each component includes sub-components and elements, and sub-components may also include sub-components and elements, the component hierarchy is used to explain the next-level components and elements contained in each component, so as to facilitate the subsequent configuration of the next-level sub-components and elements of the component according to the component hierarchy. The creation information includes information such as the creator and creation time of the component.

[0069] After completing the basic information definition of the component, first declare the basic elements contained in each component, so that the subsequent element management module 1 can configure the elements in the component. Specifically, determine the basic element type of the component, such as pictures, texts, or buttons, assign a unique identifier to each element in the component, set the basic attributes of the element, such as color, size, font and other information, and configure the default display state of the element. Then, perform layout design on the arrangement relationship of the elements in the component, including selecting a suitable layout method, such as elastic layout or grid layout, setting the arrangement direction and alignment of the elements, and configuring the spacing and margins between the elements.

[0070] After completing the layout structure design of the element, define the interactive behavior of the element to add interactive capabilities to the component. Defining the interactive behavior of the element includes defining the event types that the element can trigger, such as clicking and sliding, setting event processing functions, configuring event parameters and response logic, and establishing linkage relationships between elements to complete the process of defining the interactive behavior of the element.

[0071] After defining the interactive behavior of the elements, the components need to be data bound. Specifically, the data required by each component is first determined, and then the mapping relationship between data and elements is established. At the same time, the trigger conditions for data updates are set, and the response method for data changes is configured to complete the data binding of the elements. When the trigger conditions for data updates or the response method for data changes are met, it is ensured that the data corresponding to each element can be updated and changed in time to adapt to the needs of page changes.

[0072] On the other hand, the state of the component needs to be managed and configured to manage the internal state of the component. Specifically, it is done by defining the state variables inside the component, setting the initial value of the state variables, the update method of the state variables, and the change logic when the state variables change, such as the change function, so that when the state variables inside the component meet the change conditions, the state variables are updated in time according to the configured change function. I will not go into details here.

[0073] Furthermore, in the process of component construction by the component construction unit 21, in order to better manage the component, the life cycle behavior of the component is configured, including the initialization operation when the component is created, the data loading process when the component is mounted, the refresh logic when the component is updated, and the cleanup process when the component is destroyed, to ensure that the component has corresponding processing measures throughout the entire life cycle.

[0074] After the component construction process is completed, in order to verify the performance of the constructed component, the component is also registered in the component library. On the one hand, the performance of the component is verified, and on the other hand, it is convenient to find the corresponding component in the component library later. Specifically, after the component is built, the integrity of the component configuration is first verified. After confirming that it is complete, the complete definition of the component is generated, and the component is registered in the component library. At the same time, the index information of the component is established in the component library to facilitate quick search in the component library.

[0075] In some other embodiments, the properties configured for the component by the component property unit 22 include basic properties inherited from elements within the component, the basic properties include visual properties, interaction properties, and animation properties. The component property unit is also used to expand the properties of the component, and the extended properties of the component include business property expansion and functional property expansion.

[0076] In this embodiment, after the component construction unit 21 completes the construction of the component in the resource position, the component attribute unit 22 configures the attributes of the component. The process of the component attribute unit 22 configuring the attributes of the component includes attribute inheritance and attribute extension. The basic attributes of the component are inherited from the basic attributes of the element, including visual attributes, interactive attributes and animation attributes. The visual attributes include style attributes such as width, height, background color, and border. The interactive attributes include basic interactive events such as click, touch, and slide. The animation attributes include dynamic effect related attributes such as gradient and transition. As for attribute extension, it includes business attribute extension and functional attribute extension. Business attribute extension is based on the basic attributes to expand the relevant business attributes of the component, including data attributes, business parameters and interaction rules. The data attributes of the component include data source configuration, refresh interval and cache strategy. Business parameters include business identification, jump connection and embedding information. Interaction rules include information such as permission control, display conditions and business rules. Functional attribute extension is to add component-level functional attributes to the component. The functional attributes include life cycle functions, state management and communication interfaces. The life cycle functions include processing functions of components at nodes such as initialization, update and destruction. The state management includes the definition and processing methods of the internal state of the component. The communication interface is used for the interaction between the component and other components or systems.

[0077] By extending the properties of components based on the basic properties of the elements they inherit, you can give them richer business functions, enhance their configurability and flexibility, and support more complex interaction scenarios. You can also optimize the development experience, reduce repetitive development work, provide a unified property management method, and simplify the communication mechanism between components. You can also improve the reuse efficiency of components, achieve functional reuse through property configuration, support differentiated business needs, and facilitate component maintenance and upgrades.

[0078] In some other embodiments, when the component triggers an upgrade condition, the version control unit 23 selects a corresponding method to manage the version of the component according to the usage of the current page, and the upgrade condition includes at least one of a change in the user's business needs, a need to update the component function, and a need to adjust the component style.

[0079] After the component construction unit 21 completes the construction of the component, due to the update of the page version and the APP version, the component version sometimes needs to be updated. The version control unit 23 can effectively manage the component version to meet different usage scenarios.

[0080] Specifically, component version upgrade scenarios generally include: when business requirements change, when component functions need to be updated, and when component styles need to be adjusted. The version control unit 23 controls component versions in the following ways:

[0081] Keep the original version: the pages that have been used continue to use the original version components to ensure that the existing business is not affected;

[0082] Create new versions: Create new versions of components to meet new business needs;

[0083] Version number increment: The version number increases by 1 after each update, for example, v1.0 is upgraded to v2.0.

[0084] For example, for a product card component, its corresponding versions have different functions:

[0085] V1.0: Basic product display functions, including pictures, titles, and prices;

[0086] V2.0 version: added member price display function;

[0087] V3.0 version: added product label display;

[0088] In specific use, old pages continue to use version V1.0, pages that require member prices use version V2.0, and new pages that need to use label display use version V3.0, so as to ensure that the new and old businesses of the page do not affect each other, component functions are upgraded smoothly, and maintenance costs are controllable.

[0089] In some other embodiments, the element management module 1 includes an element definition unit 11, an element attribute unit 12 and an element behavior unit 13. The element definition unit 11 is communicatively connected to the component construction unit 21 for configuring elements corresponding to the component configuration constructed by the component construction unit 21. The element attribute unit 12 is communicatively connected to the element definition unit 11 for setting the attributes of the element. The element behavior unit 13 is communicatively connected to the element definition unit 11 for configuring the triggering event of the element.

[0090] In this embodiment, after the component construction process is completed by the component construction unit 21, the element definition unit 11 configures corresponding elements for each component according to the basic element type in the constructed component, including buttons (BUTTON), text labels (LABEL), input boxes (INPUT), etc., and the element attribute unit 12 sets corresponding attributes for each element, including display attributes and behavior attributes, and the element behavior unit 13 configures corresponding trigger behaviors for each element, including click (click), display (show), and input (input).

[0091] In some other embodiments, the diversion rule module 4 includes a diversion rule setting unit 41 and a user group division unit 42. The diversion rule setting unit 41 is used to set the diversion rules for the user, and the diversion rules include customer group rules, directional rules and experimental rules. The user group division unit 42 is used to divide the users into groups according to the diversion rules after collecting the user data. The page template unit 31 is communicated with the user group division unit 42 to define the basic structure of the user's page according to the group division resource bits after the users are divided.

[0092] In this embodiment, before the page management module 3 configures the page, the corresponding diversion rules are set by the diversion rule setting unit 41 in the diversion rule module 4, so that the user group division unit 42 can divide the users into groups according to the diversion rules, so that the subsequent page template unit 31 can configure the basic structure of the page according to the group to which the user belongs based on the result of the group division.

[0093] refer to Figure 3 After the page management module 3 receives the user's page request, the page management module 3 sends a request to the diversion rule module 4 for user grouping information, and the diversion rule module 4 obtains the user portrait in the data storage layer to obtain user data, so that the diversion rule module 4 can group the user data. Specifically, the diversion rules set by the diversion rule setting unit 41 include three main types, namely customer group rules, directional rules and experimental rules, among which the customer group rules include:

[0094] Layout scenario: layout configuration for specific scenarios;

[0095] Layout name: the specific identification name of the scene;

[0096] Application scenario: the specific business scenario to which the rule applies;

[0097] Effective time: the effective time range of the rule;

[0098] Targeting rules include:

[0099] User dimensions: such as user attributes, behaviors, etc.

[0100] Time dimension: such as visit time and activity period;

[0101] Device dimensions: such as device type and system version;

[0102] Geographical dimension: such as the city, region, etc.

[0103] The experimental rules include:

[0104] Rule scenario: the specific scenario setting of the experiment;

[0105] Experimental subjects: targeted user groups;

[0106] Experimental content: the specific content that needs to be verified;

[0107] Data comparison: compare experimental results;

[0108] Experiment duration: the duration of the experiment.

[0109] The diversion rules are set in the above manner, so that the user group segmentation unit 42 can subsequently segment the user groups according to the diversion rules. When segmenting, the aforementioned diversion rules are first used as the diversion basis, including customer group rules based on scenarios and KPI indicators, directional rules based on user attributes and behaviors, and experimental rules based on experimental scenario requirements.

[0110] When making specific divisions, we first collect user information, including basic attributes, behavioral data, and scenario information. Then, we match the diversion rules according to the priority level based on the collected user information. We determine user groups based on the matching results of the diversion rules and divide users into corresponding groups. At the same time, we dynamically adjust the grouping results based on user behavior, thereby dynamically updating the grouping of user groups.

[0111] On the other hand, after the diversion rule module 4 completes the user diversion to realize the user group division, the page management module 3 realizes differentiated display for different users according to the user group division result after the diversion by the diversion rule module 4. Specifically, when a user requests a page, the diversion rule module 4 identifies the group corresponding to the user, and then the page management module 3 obtains the page configuration of the user corresponding group, so as to configure the page according to the page configuration, including defining the basic structure of the page, configuring the resource position and controlling the position and arrangement of the components in the resource position, constructing the components corresponding to the resource position through the component construction module 2, and configuring the elements of the component through the element management module 1, and finally displaying the rendered personalized page after the configuration is completed to the user. Differentiated display for different users is realized, so that different groups see different page layouts, the same resource position of different users displays different component contents, and the same component of different users displays different business data. In this way, the system can accurately identify users and provide personalized page display.

[0112] For example, taking the App homepage as an example, when the user group division unit 42 determines that the current user is a new user, the page management module 3 defines the resource position of the page as a novice guide position, configures the component configured in the resource position as a novice tutorial component, and configures the content of the component as registration rewards and function guides;

[0113] When the user group division unit 42 determines that the current user is a high-frequency user, the page management module 3 defines the resource position of the page as a personalized recommendation position, and configures the component of the personalized recommendation position as a product list component, and configures the component content as common functions and historical records, thereby enabling different users to see different personalized content through rule matching and multi-level dynamic configuration.

[0114] In some other embodiments, the page template unit 3 is further used to collect user data collected by the user group segmentation unit 42, and obtain user characteristics, scene characteristics and component characteristics of the user, and automatically optimize the basic structure of the user's page according to the algorithm model, wherein the user data includes client buried point data and server buried point data.

[0115] Specifically, after the page template unit 3 completes the configuration of the user's page template, the user's behavior data is collected in real time on the user's client, including click behavior, dwell time, conversion indicators and operation tracks, where click behavior includes regional click-through rate and click flow path; dwell time includes page / component dwell time; operation track includes sliding path and interaction mode. On the server side, business action data, business process data and conversion indicators are collected, and conversion indicators include function usage rate and transaction conversion rate.

[0116] Then, based on the collected user behavior data, the user characteristics, scene characteristics and component characteristics of the user are extracted respectively. The user characteristics include usage habits and interest preferences, the scene characteristics include time, location, and equipment, and the component characteristics include location, style, and content type. After obtaining the above characteristics, the above characteristics are analyzed according to the machine learning algorithm model, including heat sorting, correlation analysis, and predicted recommendation results. The popularity of different components in the page is determined according to the heat sorting, the correlation between different components is calculated according to the correlation analysis, and the user's preferred components are predicted according to the predicted recommendation results. Then, the page is optimized in layout, display, content, and process according to the predicted results. Layout optimization includes adjusting the position and order of components, display optimization includes optimizing the display form of components, content optimization includes intelligent filtering of component content, and process optimization includes selecting page processes that can improve conversion rates. Specifically, the predicted user preference components, the most popular components, and the associated components are displayed first, and the page process with a higher conversion rate is selected. The content, layout, position, order, display form, etc. of the components are optimized to provide users with a better experience. This enables the system to automatically adjust the page structure and content display according to the optimization results to improve the user experience.

[0117] It should be noted that the machine learning algorithm model used in the above solution is a model in the prior art. This solution does not involve improvements to the model itself. The model can be used by training it only through the collected user data, which will not be elaborated here.

[0118] The present invention also provides an APP page management method, referring to Figure 4 , including the following steps:

[0119] S401, after receiving a page request from a client, a data request is sent to a diversion rule module through a page management module;

[0120] S402, obtaining user data after receiving the data request through the diversion rule module, and dividing the user into user groups according to the user data to obtain a division result;

[0121] S403, configuring the user's page through the page management module according to the division result;

[0122] S404, after configuring components for resource locations of the user's page through the component management module according to the page configuration result, the element management module configures elements according to the configured components;

[0123] S405: after generating a corresponding page through the page management module according to the result of the configuration, the page is sent to the client.

[0124] Exemplarily, after the user opens the client and sends a page request, the page management module 3 first requests the diversion rule module 4 for user grouping information, and the diversion rule module 4 directly obtains the user portrait in the data layer to obtain the user data, and returns the user data to the diversion rule module 4. The diversion rule module 4 divides the users into groups according to the set diversion rules and obtains the user group division results, that is, the grouping results, and sends the grouping results to the page management module 3. The page management module 3 configures the user's page template according to the grouping results, including the configuration of resource positions, components and elements, and sends the configuration results of the page to the component management module to configure the resource positions respectively. At the same time, the element management module configures the component configuration elements and content configured by each component configuration module, thereby completing the configuration of the entire page. After the configuration is completed, the configuration results are returned to the page management module, and the page management module sends the final configured page structure to the user's client to display the final page on the user's client.

[0125] It should be noted that since the above page management method is basically the same as the page management process in the aforementioned page management system, it will not be repeated here.

[0126] An embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by an electronic device, the above-mentioned APP page management method is implemented.

[0127] A person of ordinary skill in the art can understand that all or part of the steps in the method for implementing the above-mentioned embodiment can be completed by instructing a processor through a program, and the program can be stored in a computer-readable storage medium, and the storage medium is a non-transitory medium, such as a random access memory, a read-only memory, a flash memory, a hard disk, a solid-state hard disk, a magnetic tape, a floppy disk, an optical disc, and any combination thereof. The above-mentioned storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more available media. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a digital video disc (DVD)), or a semiconductor medium (for example, a solid-state disk (SSD)), etc.

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

[0129] The modules / units described as separate components may or may not be physically separated, and the components displayed as modules / units may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules / units may be selected according to actual needs to achieve the purpose of the embodiments of the present application. For example, the functional modules / units in the various embodiments of the present application may be integrated into one processing module, or each module / unit may exist physically separately, or two or more modules / units may be integrated into one module / unit.

[0130] Those of ordinary skill in the art should further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0131] The descriptions of the processes or structures corresponding to the above-mentioned figures have different emphases. For parts that are not described in detail in a certain process or structure, please refer to the relevant descriptions of other processes or structures.

[0132] The above embodiments are merely illustrative of the principles and effects of the present application and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application.

Claims

1. An APP page management system, characterized in that: include: Page management module, used to configure and manage page layout; A traffic diversion rule module, which is in communication with the page management module and is used to dynamically generate the page content to be displayed for the user according to the user's real-time data; A component management module, which is in communication with the page management module and is used to configure and manage the component content of the page according to the request of the page management module; An element management module, which is in communication with the component management module and is used to manage elements according to the component content of the component management module, so as to achieve management of visual elements with minimum granularity; The diversion rule module is also used to collect user behavior data and automatically optimize the content to be displayed on the page of the user according to the behavior data.

2. The APP page management system according to claim 1, characterized in that: The page management module includes a page template unit, a layout management unit and a resource bit configuration unit. The page template unit is used to divide the resource bits to define the basic structure of the page. The resource bit configuration unit is communicated with the page template unit and is used to perform content configuration on the divided resource bits. The layout management unit is communicated with the resource bit configuration unit and is used to perform layout management on the components in the configured resource bits.

3. The APP page management system according to claim 2, characterized in that: The process of defining the basic structure of a page by the page template unit includes: Divide the page into multiple resource locations, configure a corresponding component for each resource location, and set display parameters for each component; The resource location configuration unit configures the resource location with content including location attributes, display rules, component mapping and permission control. The location attributes include the location and size of the resource location on the page, the display rules include the display method of the configuration content of the resource location, the component mapping includes the component types that can be placed in the resource location, and the permission control includes the display permission of the resource location.

4. The APP page management system according to claim 2, characterized in that: The component management module includes a component construction unit, a component attribute unit and a version control unit. The component construction unit is communicatively connected to the resource position configuration unit for constructing a corresponding component for each resource position. The component attribute unit is communicatively connected to the component construction unit for configuring the attributes of the component constructed by the component construction unit. The version control unit is communicatively connected to the component construction unit for managing the version of the component constructed by the component construction unit.

5. The APP page management system according to claim 4, characterized in that: The process of constructing the component corresponding to the resource bit by the component construction unit includes: Defining basic information of each of the components in the resource slot and configuring elements in the components; Configure element information and layout for each of the elements, set interactive behaviors and bind data for the components, and configure the status and life cycle behaviors of the components; Complete the registration of the component in the component library.

6. The APP page management system according to claim 5, characterized in that: The basic information of the component includes the component unique identifier, component name, component version, component description, component hierarchy and component creation information; the element information includes the element type, element identifier, basic attributes and default display state; the layout of the element includes setting the layout mode, setting the arrangement direction and alignment of the elements, and setting the spacing and margins between elements; the state configuration of the component includes defining the state variables of the component, setting the initial state value, specifying the state update method and configuring the processing logic of the state change; the life cycle formation configuration of the component includes setting the initialization operation of the component at creation, data loading at mounting, refresh logic at update and cleanup at destruction; the registration of the component includes verifying the configuration integrity of the component, generating a complete definition of the component, registering the component to the component library and establishing index information of the component in sequence.

7. The APP page management system according to claim 4, characterized in that: The properties configured for the component by the component property unit include basic properties inherited from elements within the component, and the basic properties include visual properties, interaction properties, and animation properties. The component property unit is also used to expand the properties of the component, and the extended properties of the component include business property expansion and functional property expansion.

8. The APP page management system according to claim 4, characterized in that: When the component triggers an upgrade condition, the version control unit selects a corresponding method to manage the version of the component according to the usage of the current page. The upgrade condition includes at least one of a change in the user's business needs, a need to update the component function, and a need to adjust the component style.

9. The APP page management system according to claim 1, characterized in that: The element management module includes an element definition unit, an element attribute unit and an element behavior unit. The element definition unit is communicatively connected to the component construction unit for configuring the corresponding element for the component constructed by the component construction unit. The element attribute unit is communicatively connected to the element definition unit for setting the attribute of the element. The element behavior unit is communicatively connected to the element definition unit for configuring the trigger event of the element.

10. The APP page management system according to claim 2, characterized in that: The diversion rule module includes a diversion rule setting unit and a user group division unit. The diversion rule setting unit is used to set the diversion rules for the user. The diversion rules include customer group rules, directional rules and experimental rules. The user group division unit is used to divide the users into groups according to the diversion rules after collecting the user data. The page template unit is communicatively connected with the user group division unit to define the basic structure of the user's page according to the group division resource bits after the users are divided.

11. The APP page management system according to claim 10, characterized in that: The page template unit is also used to collect the user data collected by the user group division unit, and obtain the user characteristics, scene characteristics and component characteristics of the user, and automatically optimize the basic structure of the user's page according to the algorithm model.

12. A method for managing an APP page, characterized in that: include: After receiving the page request from the client, a data request is sent to the diversion rule module through the page management module; After receiving the data request, the diversion rule module obtains user data, and divides the user into user groups according to the user data to obtain a division result; According to the division result, configuring the user's page through the page management module; According to the page configuration result, after configuring the components for the resource positions of the user's page through the component management module, the element management module configures the elements according to the configured components; According to the result of the configuration, after the corresponding page is generated by the page management module, the page is sent to the client.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed, the APP page management method described in claim 12 is implemented.

Images