Multi-demand user terminal page updating method, device, equipment and medium

Abstract

The present application relates to the development field, and discloses a multi-demand user terminal page updating method, device, equipment and medium, which can be used for updating the platform webpage according to the target user demand on the insurance community webpage or the insurance App platform.The method comprises the following steps: performing a bucket operation on a user data set according to a business demand to obtain a plurality of bucket user data subsets; creating a plurality of user terminal pages corresponding to a plurality of business demands; determining the matching relationship between the plurality of bucket user data subsets and the plurality of user terminal pages according to the acquired version identifier; monitoring the click event triggered on the user terminal page, and collecting the user behavior data set corresponding to the click event by using the burying point; and selecting the target user terminal page corresponding to each business demand from the plurality of user terminal pages according to the plurality of user behavior data sets, and realizing the user terminal page updating by using a business interface.The present application can improve the user terminal page updating efficiency and is beneficial to improving the user stickiness.

Description

Technical Field

[0001] This invention relates to the field of development, and more particularly to a method, apparatus, device, and storage medium for updating client-side pages with multiple requirements. Background Technology

[0002] With the rapid development of the Internet, the demand for business product development is also gradually increasing. For example, in the financial field, some insurance business community websites or APP platforms need to change the UI design, operation functions and data display functions of community websites or APP platforms in order to accurately promote insurance products to target users and fully understand the target users' preferences for insurance products.

[0003] Current user-side page update methods are implemented for each product requirement. When there are multiple product requirements, frequent changes are needed to the UI design, operational functions, and data display functions. This frequent change leads to the following problems:

[0004] 1. Each change requires statistical analysis of page click metrics based on changes in business needs. For example, it's necessary to track user dwell time on the insurance community's user-side page or the number of clicks on insurance products. Each time a metric changes, staff need to summarize the data, resulting in high repetitive workload. Furthermore, each change requires the development team to rewrite and update the code, which takes a considerable amount of time to become effective. This leads to long update cycles for the user-side pages on the insurance community or insurance app, resulting in low update efficiency.

[0005] 2. Frequent changes require users to constantly adjust their operating habits on the user-side page, which can lead to frustration and reduce user stickiness to the business platform. Summary of the Invention

[0006] This invention provides a method, apparatus, device, and storage medium for updating user-end pages to meet various needs. Its main purpose is to improve the efficiency of updating user-end pages on insurance community web pages or insurance APP platforms, thereby increasing user stickiness.

[0007] To achieve the above objectives, the present invention provides a method for updating client-side pages with multiple requirements, comprising:

[0008] Obtain the user dataset and multiple business requirements of the business products, and perform bucketing operation on the user dataset according to the multiple business requirements to obtain multiple bucketed user data subsets;

[0009] Create multiple user-side pages corresponding to the multiple business requirements, obtain version identifiers of the multiple user-side pages, and determine the matching relationship between the multiple bucketed user data subsets and the multiple user-side pages based on the version identifiers;

[0010] Based on the matching relationship, monitor the click events triggered on the corresponding user terminal page for each of the bucketed user data subsets, and use data points to collect user behavior datasets corresponding to multiple click events;

[0011] Based on the collected user behavior datasets, select the target user page corresponding to each business requirement from the multiple user-end pages;

[0012] Obtain the current user-side page for each of the aforementioned business requirements, and update the current user-side page to the target user-side page corresponding to each of the aforementioned business requirements using a preset business interface.

[0013] Optionally, the step of bucketing the user dataset according to multiple business requirements to obtain multiple bucketed user data subsets includes:

[0014] The user dataset is filtered according to multiple business requirements to obtain an initial user dataset;

[0015] The initial user dataset is hashed to obtain its hash value, and the hash address of the hash value is extracted using a preset hash function.

[0016] The hash values ​​with the same hash address are clustered, and the clustered hash values ​​are distributed to preset hash buckets according to the clustering category to obtain multiple bucketed user data subsets.

[0017] Optionally, the step of collecting user behavior datasets corresponding to multiple click events using tracking points includes:

[0018] Obtain the event tracking identifiers from multiple user pages, and construct a no-code event mapping table based on the event tracking identifiers;

[0019] Obtain the static and dynamic parameters of the no-code mapping table;

[0020] Based on the static parameters, collect static parameter data triggered by multiple click events;

[0021] Based on the dynamic parameters, collect dynamic parameter data triggered by multiple click events;

[0022] Obtain the user identifier, and merge the collected static parameter data and dynamic parameter data based on the user identifier to obtain a user behavior dataset corresponding to multiple click events.

[0023] Optionally, creating multiple user-side pages corresponding to the multiple business requirements includes:

[0024] Receive request instructions to generate user-side pages according to multiple business requirements, and generate a component tree of user-side pages to be generated according to the request instructions;

[0025] Identify the editing operations performed on the user-side page to be generated in the preset page editor, and generate the configuration information of the user-side page to be generated based on the editing operations;

[0026] The configuration information is added to the component tree, and the component tree after adding the configuration information is parsed to obtain the component code. The component code is then inserted into a preset client page template to obtain the client page.

[0027] Optionally, updating the current user-side page using a preset business interface to the target user-side page corresponding to each business requirement includes:

[0028] Obtain the update instruction for the target user page corresponding to each of the aforementioned business requirements, and obtain the Uniform Resource Locator (URL) for the target user page based on the update instruction.

[0029] The unified resource locator is transmitted to the business interface, and the current user page is updated to the target user page corresponding to each business requirement through the business interface.

[0030] Optionally, after allocating the clustered hash values ​​to preset hash buckets according to clustering categories, the method further includes:

[0031] Obtain the spatial location of each hash value in any hash bucket, and calculate the maximum spatial distance between hash values ​​in any hash bucket based on the spatial location;

[0032] Obtain the target spatial distance between the hash value to be queried and the cluster center in any of the hash buckets, and compare the target spatial distance with the maximum spatial distance;

[0033] When the target spatial distance is not greater than the maximum spatial distance, the hash value to be queried is determined to be allocated to the hash bucket.

[0034] Optionally, after comparing the target spatial distance with the maximum spatial distance, the method further includes:

[0035] When the target spatial distance is greater than the maximum spatial distance, the updated maximum spatial distance of the hash value in the other hash bucket and the updated target spatial distance between the cluster center in the other hash bucket and the hash value to be queried are recalculated until the updated target spatial distance is not greater than the updated maximum spatial distance, and the hash value to be queried is determined to be assigned to the hash bucket.

[0036] To address the above problems, the present invention also provides a multi-demand client page update device, the device comprising:

[0037] The bucketing module is used to obtain the user dataset and multiple business requirements of the business products, and to perform bucketing operations on the user dataset according to the multiple business requirements to obtain multiple bucketed user data subsets.

[0038] The matching module is used to create multiple user-end pages corresponding to multiple business requirements, obtain version identifiers of multiple user-end pages, and determine the matching relationship between multiple bucketed user data subsets and multiple user-end pages based on the version identifiers.

[0039] The acquisition module is used to monitor click events triggered on the corresponding user terminal page for each of the bucketed user data subsets according to the matching relationship, and to collect user behavior datasets corresponding to multiple click events using tracking points.

[0040] The update module is used to select the target user page corresponding to each business requirement from multiple user-end pages based on the collected user behavior datasets; obtain the current user page for each business requirement; and update the current user page to the target user page corresponding to each business requirement using a preset business interface.

[0041] To address the above problems, the present invention also provides an electronic device, the electronic device comprising:

[0042] Memory, storing at least one computer program; and

[0043] The processor executes the computer program stored in the memory to implement the aforementioned multi-demand client page update method.

[0044] To address the aforementioned problems, the present invention also provides a computer-readable storage medium storing at least one computer program, which is executed by a processor in an electronic device to implement the aforementioned multi-demand client page update method.

[0045] In this embodiment of the invention, firstly, the user dataset is bucketed according to multiple business requirements to achieve user segmentation, which facilitates the subsequent improvement of the accuracy of matching bucketed user data subsets with multiple user-end pages. Secondly, by creating multiple user-end pages corresponding to multiple business requirements, the user-end page required for each business requirement can be automatically generated. Furthermore, click events triggered by each bucketed user data subset on the corresponding user-end page are monitored based on the matching relationship, and user behavior datasets corresponding to multiple click events are collected using tracking points. This can record all click events of each bucketed user data subset, eliminating the need for staff to perform click event statistics for changes in business requirements, reducing labor costs, and improving the efficiency of subsequent user-end page updates. Finally, by selecting the target user-end page corresponding to each business requirement from multiple user-end pages based on the user behavior dataset, the user-end page is updated. When business requirements change frequently, the development team does not need to rewrite the update page version code or change the user's operations on the page, improving the efficiency of user-end page updates and helping to improve user stickiness. Therefore, the multi-demand user-end page update method, apparatus, device, and storage medium proposed in the embodiments of the present invention can improve the update efficiency of user-end pages on insurance community web pages or insurance APP platforms, which is conducive to improving user stickiness. Attached Figure Description

[0046] Figure 1 This is a flowchart illustrating a multi-demand client page update method according to an embodiment of the present invention.

[0047] Figure 2 A detailed flowchart illustrating one step of a multi-demand client page update method provided in an embodiment of the present invention;

[0048] Figure 3 A detailed flowchart illustrating one step of a multi-demand client page update method provided in an embodiment of the present invention;

[0049] Figure 4 A schematic diagram of a multi-demand client page update device provided in an embodiment of the present invention;

[0050] Figure 5 This is a schematic diagram of the internal structure of an electronic device that implements a multi-demand client page update method according to an embodiment of the present invention.

[0051] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0052] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0053] This invention provides a method for updating client-side pages with multiple requirements. The executing entity of this method includes, but is not limited to, at least one of the following: a server, a terminal, or other electronic devices configured to execute the method provided in this application. In other words, the method can be executed by software or hardware installed on a terminal device or a server device, where the software may be a blockchain platform. The server includes, but is not limited to, a single server, a server cluster, a cloud server, or a cloud server cluster.

[0054] Reference Figure 1 The flowchart shown is a schematic diagram of a multi-demand client page update method provided in an embodiment of the present invention. In this embodiment, the multi-demand client page update method includes the following steps S1-S5:

[0055] S1. Obtain the user dataset and multiple business requirements of the business products, and perform bucketing operation on the user dataset according to the multiple business requirements to obtain multiple bucketed user data subsets.

[0056] In this embodiment of the invention, the user dataset refers to a collection of user data who have registered and used the business product's webpage or app. For example, in a life insurance community webpage, it is a collection of user data who have registered and logged into the community webpage.

[0057] Specifically, the aforementioned business requirements can be business development requirements, which can be proposed by users. For example, in insurance applications or community web pages, there may be a requirement to add pop-up or click-to-jump functionality to the user's page.

[0058] Specifically, the multiple bucketed user data subsets refer to the collection of user data with the same hash address, where the hash address refers to the hash address storing the multiple bucketed user data subsets.

[0059] As an embodiment of the present invention, reference is made to... Figure 2 As shown, the step of bucketing the user dataset according to multiple business requirements to obtain multiple bucketed user data subsets includes the following steps S11-S13:

[0060] S11. Filter the user dataset according to multiple business requirements to obtain an initial user dataset;

[0061] S12. Perform hash calculation on the initial user dataset to obtain the hash value of the initial user dataset, and extract the hash address of the hash value using a preset hash function;

[0062] S13. Cluster the hash values ​​with the same hash address, and distribute the clustered hash values ​​to preset hash buckets according to the clustering category to obtain multiple bucketed user data subsets.

[0063] The user dataset can be filtered based on multiple business requirements to select the appropriate dataset for each requirement. For example, if a business requirement is to add a redirect page for life insurance products to a life insurance community webpage, then the initial user dataset would be selected from users who have logged into the community webpage and viewed life insurance products.

[0064] In one embodiment of the present invention, the SHA algorithm can be used to transform the initial user dataset into a fixed-length combination of numbers and letters. The preset hash function is a function that maps hash values ​​to storage locations.

[0065] Furthermore, in this embodiment of the invention, the hash values ​​with the same hash address can be clustered using the approximate nearest neighbor algorithm, and the clustered hash values ​​can be allocated to hash buckets to obtain multiple bucketed user data subsets, wherein the number of the preset hash buckets is consistent with the clustering categories.

[0066] In an optional embodiment of the present invention, after allocating the clustered hash values ​​to preset hash buckets according to the clustering categories, the method further includes:

[0067] Obtain the spatial location of each hash value in any hash bucket, and calculate the maximum spatial distance between hash values ​​in any hash bucket based on the spatial location; obtain the target spatial distance between the hash value to be queried and the cluster center in any hash bucket, and compare the target spatial distance with the maximum spatial distance; when the target spatial distance is not greater than the maximum spatial distance, determine that the hash value to be queried is assigned to the hash bucket.

[0068] In this embodiment of the invention, due to the uneven distribution of data in the hash buckets, some hash buckets may contain a lot of data while other hash buckets contain very little data, which may affect the subsequent update effect of the user-side page.

[0069] Wherein, the spatial location is the position of the hash value mapped to the three-dimensional spatial matrix; the maximum spatial distance is the distance between the farthest hash values ​​in the same hash bucket, and the maximum spatial distance is the Euclidean distance.

[0070] In one embodiment of the present invention, the hash value to be queried and the hash value corresponding to the maximum spatial distance belong to the same hash bucket. By calculating the target spatial distance between the hash value to be queried and the cluster center in the hash bucket, the rationality of the data when the data is divided into buckets in each hash bucket can be checked, avoiding the situation where there is a lot of data in some hash buckets and very little data in other hash buckets.

[0071] In an optional embodiment of the present invention, after comparing the target spatial distance with the maximum spatial distance, the method further includes:

[0072] When the target spatial distance is greater than the maximum spatial distance, the updated maximum spatial distance of the hash value in the other hash bucket and the updated target spatial distance between the cluster center in the other hash bucket and the hash value to be queried are recalculated until the updated target spatial distance is not greater than the updated maximum spatial distance, and the hash value to be queried is determined to be assigned to the hash bucket.

[0073] The calculation methods for the updated maximum spatial distance and the updated target spatial distance are basically the same as those for the maximum spatial distance and the target spatial distance mentioned above, and will not be repeated here.

[0074] Furthermore, in this embodiment of the invention, when the target spatial distance is greater than the maximum spatial distance, the hash value to be queried is determined to be reassigned to a hash bucket until the target spatial distance between the hash value to be queried and the cluster center of the hash bucket is not greater than the maximum spatial distance, and then the hash value to be queried is determined to be assigned to a new hash bucket.

[0075] S2. Create multiple user-end pages corresponding to the multiple business requirements, obtain version identifiers of the multiple user-end pages, and determine the matching relationship between the multiple bucketed user data subsets and the multiple user-end pages based on the version identifiers.

[0076] In this embodiment of the invention, the user-end page may vary depending on different business scenarios, such as a life insurance product website page. The version identifier refers to the version number of each user-end page, which is generally composed of the user-end page name and the development code version number. For example, the version number of a certain user-end page may be "Life Insurance Webpage 1.0" or "Life Insurance Webpage 2.0", etc.

[0077] Specifically, the matching relationship describes the correspondence between the hash bucket numbers of multiple bucketed user data subsets and the user page version identifiers. Since the version identifier of each user page corresponds to the bucket number of a hash bucket with a preset range of different values, the matching relationship between multiple bucketed user data subsets and multiple user pages can be determined, and each hash bucket number has a corresponding version identifier.

[0078] For example, if the total number of hash buckets is 100, it can be determined that hash buckets numbered 1 to 33 match the first version identifier, that is, the version identifier of the first user page version matches hash buckets 1 to 33, the second user page version matches hash buckets numbered 34 to 67, and the remaining user page versions can be matched with hash buckets numbered 68 to 100.

[0079] As an embodiment of the present invention, the creation of multiple user-end pages corresponding to the multiple business requirements includes:

[0080] The system receives request instructions to generate a client-side page based on multiple business requirements, and generates a component tree for the client-side page to be generated based on the request instructions. It identifies editing operations on the client-side page to be generated in a preset page editor, and generates configuration information for the client-side page to be generated based on the editing operations. The configuration information is added to the component tree, and the component tree after adding the configuration information is parsed to obtain component code. The component code is then inserted into a preset client-side page template to obtain the client-side page.

[0081] The specific content of the request instruction may vary depending on different business scenarios. For example, the request instruction for generating a user-end page may be a request instruction for generating a user-end page for a life insurance community website. The component tree is a tree-structured component diagram composed of multiple components. Multiple components refer to encapsulating one or more code segments that perform their respective functions into one or more independent parts and using them to generate the user-end page. Multiple components may include component code such as text, images, input boxes, drop-down boxes, and button jump links.

[0082] In one embodiment of the present invention, the preset page editor is a tool for generating user-end pages. Through this page editor, multiple components can be customized or modified to obtain configuration information including component attribute parameters and component types.

[0083] Furthermore, by adding configuration information to the component tree, it is possible to add, delete, or modify the corresponding client-side page content according to business needs, thereby improving the efficiency of client-side page generation. Moreover, Babel (the compiler) can be used to traverse and parse the component tree, directly obtaining the component code corresponding to each component without requiring developers to rewrite the code, further improving the development efficiency of client-side pages.

[0084] S3. Based on the matching relationship, monitor the click events triggered by each of the user data subsets in the corresponding user terminal page, and use data points to collect user behavior datasets corresponding to multiple click events.

[0085] In this embodiment of the invention, the click event refers to each click a user makes on a page button on the user's device as an event. The user behavior dataset refers to the record generated for each click triggered by the user, such as records of browsing life insurance products or viewing the benefits of life insurance products.

[0086] In this embodiment of the invention, the "tracking points" refer to some program code added to the user-side page. When triggered, this program code can collect and statistically analyze the user's browsing, access data, and application usage on the user-side page.

[0087] This invention monitors click events triggered on the corresponding user-end page by each subset of user data in the bucket according to the matching relationship, and collects user behavior datasets corresponding to multiple click events using tracking points. This allows for real-time recording of user operations on the user-end page, facilitating subsequent updates based on the recorded data and improving the efficiency of user-end page updates.

[0088] Further, refer to Figure 3 As shown, the process of collecting user behavior datasets corresponding to multiple click events using data tracking includes the following steps S31-S35:

[0089] S31. Obtain the tracking point identifiers in multiple user pages, and construct a no-code mapping table based on the tracking point identifiers;

[0090] S32. Obtain the static and dynamic parameters of the no-code mapping table;

[0091] S33. Based on the static parameters, collect static parameter data triggered by multiple click events;

[0092] S34. Based on the dynamic parameters, collect dynamic parameter data triggered by multiple click events;

[0093] S35. Obtain user identifiers, and merge the collected static parameter data and dynamic parameter data according to the user identifiers to obtain user behavior datasets corresponding to multiple click events.

[0094] Wherein, the tracking point identifier refers to the tracking point ID that represents each tracking point; the no-code mapping table refers to the data table that stores tracking points and the corresponding click event parameters collected by the tracking points; the static parameters refer to the user-side page information; the dynamic parameters refer to the user's operation information on the user-side page; and the user identifier is the user ID that represents each user.

[0095] In one embodiment of the present invention, the static parameter data collected from multiple click events can include user login type, the time when the user starts logging into the user-side page, etc.; the dynamic parameter data collected from multiple click events can include the number of times the user clicks the page jump button, the number of times the user clicks the pop-up window, the number of times the user clicks the recommendation page, the number of times the user's page is exposed, and the duration of the user's stay on the page, etc.

[0096] In this embodiment of the invention, the static parameter data and dynamic parameter data of the user ID extracted from the tracking points are merged according to the user ID to obtain a user behavior dataset corresponding to multiple click events.

[0097] S4. Select the target user page corresponding to each business requirement from the multiple user behavior datasets collected.

[0098] In this embodiment of the invention, the target user page is a user page improved based on task requirements, such as a user page with added pop-up windows or page jump functions.

[0099] In one embodiment of the present invention, for a business requirement, multiple user-side page effects are first set, and each user-side page corresponds to a version identifier. The usage rates of the multiple user-side page effects are compared based on the user behavior dataset, and the user-side page corresponding to the user-side page effect with the high usage rate is selected as the target user-side page corresponding to the business requirement.

[0100] For example, a business requirement is to add product pop-ups and redirect pages to the existing life insurance community Q&A webpage. For this requirement, three types of user-side pages were defined: adding product pop-up information, adding redirect page information, and keeping the original user-side page information. User behavior data showed that the click-through rate (CTR) for the user-side page with added product pop-up information was 0.22, and the average page dwell time was 30 seconds; the CTR for the user-side page with added redirect page information was 0.68, and the average page dwell time was 180 seconds; the CTR for the original user-side page was 0.1, and the average page dwell time was 15 seconds. Comparing the CTR and dwell time of these three user-side pages, it can be seen that the user-side page with added redirect page information attracts more users and keeps them on the platform longer. Using the page with added redirect page information as the target user-side page can improve user stickiness on the business platform.

[0101] S5. Obtain the current user terminal page for each of the business requirements, and update the current user terminal page to the target user terminal page corresponding to each of the business requirements using a preset business interface.

[0102] In this embodiment of the invention, the current user-end page refers to the original user-end page; the preset business interface can be configured through Mybatis, and further, by configuring the address of the business interface and the code parameters for calling the business interface, the business interface can be connected to multiple user-end pages to realize interface calls through the calling code parameters.

[0103] As an embodiment of the present invention, updating the current user-side page using a preset business interface to the target user-side page corresponding to each business requirement includes:

[0104] Obtain the update instruction for the target user page corresponding to each of the business requirements, and obtain the Uniform Resource Locator (URL) of the target user page according to the update instruction; transmit the URL to the business interface, and update the current user page to the target user page corresponding to each of the business requirements through the business interface.

[0105] In one embodiment of the present invention, the address of the target user page can be located and the version identifier of the target user page can be read by receiving the URL of the target user page through the business interface, and the user page can be updated through the interface and the version identifier.

[0106] In this embodiment of the invention, firstly, the user dataset is bucketed according to multiple business requirements to achieve user segmentation, which facilitates the subsequent improvement of the accuracy of matching bucketed user data subsets with multiple user-end pages. Secondly, by creating multiple user-end pages corresponding to multiple business requirements, the user-end page required for each business requirement can be automatically generated. Furthermore, click events triggered by each bucketed user data subset on the corresponding user-end page are monitored based on the matching relationship, and user behavior datasets corresponding to multiple click events are collected using tracking points. This allows recording all click events for each bucketed user data subset, eliminating the need for staff to perform click event statistics for changes in business requirements, reducing labor costs and improving the efficiency of subsequent user-end page updates. Finally, by selecting the target user-end page corresponding to each business requirement from multiple user-end pages based on the user behavior dataset, the user-end page is updated. Even when business requirements change frequently, the development team does not need to rewrite the update page version code or change user actions on the page, improving the efficiency of user-end page updates and enhancing user stickiness. Therefore, the multi-requirement user-end page update method proposed in this embodiment of the invention can improve the efficiency of user-end page updates on insurance community web pages or insurance APP platforms, thus improving user stickiness.

[0107] like Figure 4 As shown, the multi-demand client page update device 100 of the present invention can be installed in an electronic device. Depending on the functions implemented, the multi-demand client page update device may include a bucketing module 101, a matching module 102, a data acquisition module 103, and an update module 104. The module in this invention can also be called a unit, which refers to a series of computer program segments that can be executed by the processor of an electronic device and can perform a fixed function, and which are stored in the memory of the electronic device.

[0108] In this embodiment, the functions of each module / unit are as follows:

[0109] In detail, each module in the multi-demand client page update device 100 described in this embodiment of the invention adopts the same approach as described above during use. Figures 1 to 3 The method used is the same as the client-side page update method for multiple needs described above, and it can produce the same technical effect, so it will not be repeated here.

[0110] In this embodiment of the invention, firstly, the user dataset is bucketed according to multiple business requirements to achieve user segmentation, which facilitates the subsequent improvement of the accuracy of matching bucketed user data subsets with multiple user-end pages. Secondly, by creating multiple user-end pages corresponding to multiple business requirements, the user-end page required for each business requirement can be automatically generated. Furthermore, click events triggered by each bucketed user data subset on the corresponding user-end page are monitored based on the matching relationship, and user behavior datasets corresponding to multiple click events are collected using tracking points. This allows recording all click events for each bucketed user data subset, eliminating the need for staff to perform click event statistics for changes in business requirements, reducing labor costs and improving the efficiency of subsequent user-end page updates. Finally, by selecting the target user-end page corresponding to each business requirement from multiple user-end pages based on the user behavior dataset, the user-end page is updated. Even when business requirements change frequently, the development team does not need to rewrite the update page version code or change user actions on the page, improving the efficiency of user-end page updates and enhancing user stickiness. Therefore, the multi-requirement user-end page update device proposed in this embodiment of the invention can improve the efficiency of user-end page updates and enhance user stickiness.

[0111] like Figure 5 The diagram shown is a structural schematic of an electronic device for implementing a multi-demand client page update method according to the present invention.

[0112] The electronic device may include a processor 10, a memory 11, a communication bus 12 and a communication interface 13, and may also include a computer program stored in the memory 11 and executable on the processor 10, such as a multi-demand client page update program.

[0113] The memory 11 includes at least one type of medium, such as flash memory, portable hard drive, multimedia card, card-type memory (e.g., SD or DX memory), magnetic memory, local disk, optical disk, etc. In some embodiments, the memory 11 can be an internal storage unit of an electronic device, such as a portable hard drive. In other embodiments, the memory 11 can be an external storage device of the electronic device, such as a plug-in portable hard drive, Smart Media Card (SMC), Secure Digital (SD) card, Flash Card, etc. Furthermore, the memory 11 can include both internal and external storage units of the electronic device. The memory 11 can be used not only to store application software and various types of data installed on the electronic device, such as the code of multi-demand client page update programs, but also to temporarily store data that has been output or will be output.

[0114] In some embodiments, the processor 10 may be composed of integrated circuits, such as a single packaged integrated circuit or multiple integrated circuits with the same or different functions, including combinations of one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and various control chips. The processor 10 is the control unit of the electronic device, connecting various components of the entire electronic device through various interfaces and lines. It executes programs or modules stored in the memory 11 (e.g., multi-demand client page update programs) and calls data stored in the memory 11 to perform various functions of the electronic device and process data.

[0115] The communication bus 12 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be divided into an address bus, a data bus, a control bus, etc. The communication bus 12 is configured to enable communication between the memory 11 and at least one processor 10, etc. For ease of illustration, only one thick line is used in the figure, but this does not indicate that there is only one bus or one type of bus.

[0116] Figure 5 Only electronic devices with components are shown; it will be understood by those skilled in the art that... Figure 5The structure shown does not constitute a limitation on the electronic device and may include fewer or more components than shown, or combine certain components, or have different component arrangements.

[0117] For example, although not shown, the electronic device may also include a power supply (such as a battery) to power the various components. Preferably, the power supply can be logically connected to the at least one processor 10 through a power management device, thereby enabling functions such as charging management, discharging management, and power consumption management. The power supply may also include one or more DC or AC power supplies, recharging devices, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components. The electronic device may also include various sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be described in detail here.

[0118] Optionally, the communication interface 13 may include a wired interface and / or a wireless interface (such as a Wi-Fi interface, a Bluetooth interface, etc.), which is typically used to establish communication connections between the electronic device and other electronic devices.

[0119] Optionally, the communication interface 13 may further include a user interface, which may be a display, an input unit (such as a keyboard), or, optionally, a standard wired or wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, or an OLED (Organic Light-Emitting Diode) touchscreen, etc. The display may also be appropriately referred to as a screen or display unit, used to display information processed in the electronic device and to display a visual user interface.

[0120] It should be understood that the embodiments described are for illustrative purposes only and are not limited to this structure in the scope of the patent application.

[0121] The multi-demand client page update program stored in the memory 11 of the electronic device is a combination of multiple computer programs that, when run in the processor 10, can achieve the following:

[0122] Obtain the user dataset and multiple business requirements of the business products, and perform bucketing operation on the user dataset according to the multiple business requirements to obtain multiple bucketed user data subsets;

[0123] Create multiple user-side pages corresponding to the multiple business requirements, obtain version identifiers of the multiple user-side pages, and determine the matching relationship between the multiple bucketed user data subsets and the multiple user-side pages based on the version identifiers;

[0124] Based on the matching relationship, monitor the click events triggered on the corresponding user terminal page for each of the bucketed user data subsets, and use data points to collect user behavior datasets corresponding to multiple click events;

[0125] Based on the collected user behavior datasets, select the target user page corresponding to each business requirement from the multiple user-end pages;

[0126] Obtain the current user-side page for each of the aforementioned business requirements, and update the current user-side page to the target user-side page corresponding to each of the aforementioned business requirements using a preset business interface.

[0127] Specifically, the processor 10's implementation method of the above-mentioned computer program can be found in [reference needed]. Figure 1 The descriptions of the relevant steps in the corresponding embodiments are not repeated here.

[0128] Furthermore, if the modules / units integrated into the electronic device are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable medium. The computer-readable medium can be non-volatile or volatile. The computer-readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, or a read-only memory (ROM).

[0129] This invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor of an electronic device, can perform the following:

[0130] Obtain the user dataset and multiple business requirements of the business products, and perform bucketing operation on the user dataset according to the multiple business requirements to obtain multiple bucketed user data subsets;

[0131] Create multiple user-side pages corresponding to the multiple business requirements, obtain version identifiers of the multiple user-side pages, and determine the matching relationship between the multiple bucketed user data subsets and the multiple user-side pages based on the version identifiers;

[0132] Based on the matching relationship, monitor the click events triggered on the corresponding user terminal page for each of the bucketed user data subsets, and use data points to collect user behavior datasets corresponding to multiple click events;

[0133] Based on the collected user behavior datasets, select the target user page corresponding to each business requirement from the multiple user-end pages;

[0134] Obtain the current user-side page for each of the aforementioned business requirements, and update the current user-side page to the target user-side page corresponding to each of the aforementioned business requirements using a preset business interface.

[0135] Furthermore, the computer-readable storage medium may primarily include a program storage area and a data storage area, wherein the program storage area may store the operating system, at least one application required for a function, etc.; and the data storage area may store data created based on the use of blockchain nodes, etc.

[0136] In the several embodiments provided by this invention, it should be understood that the disclosed media, devices, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and other division methods may be used in actual implementation.

[0137] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0138] Furthermore, the functional modules in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in the form of hardware plus software functional modules.

[0139] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the present invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention.

[0140] Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of the invention is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be embraced within the invention. No appended diagram markings in the claims should be construed as limiting the scope of the claims.

[0141] The blockchain referred to in this invention is a novel application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. Essentially, a blockchain is a decentralized database, a chain of data blocks linked together using cryptographic methods. Each data block contains information about a batch of network transactions, used to verify the validity of the information (anti-counterfeiting) and generate the next block. A blockchain can include an underlying blockchain platform, a platform product service layer, and an application service layer.

[0142] Furthermore, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices recited in a system claim may also be implemented by a single unit or device through software or hardware. The term "second class" is used to indicate names and does not indicate any specific order.

[0143] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention.

Claims

1. A method for updating client-side pages with multiple requirements, characterized in that, The method includes: Obtain the user dataset and multiple business requirements of the business products, and perform bucketing operation on the user dataset according to the multiple business requirements to obtain multiple bucketed user data subsets; Receive request instructions to generate user-side pages according to multiple business requirements, and generate a component tree of user-side pages to be generated according to the request instructions; Identify the editing operations performed on the user-side page to be generated in the preset page editor, and generate the configuration information of the user-side page to be generated based on the editing operations; The configuration information is added to the component tree, and the component tree after adding the configuration information is parsed to obtain the component code. The component code is then inserted into a preset client page template to obtain the client page. Obtain version identifiers of multiple user-end pages, and determine the matching relationship between multiple bucketed user data subsets and multiple user-end pages based on the version identifiers; Based on the matching relationship, monitor the click events triggered on the corresponding user terminal page for each of the bucketed user data subsets, and use data points to collect user behavior datasets corresponding to multiple click events; Based on the collected user behavior datasets, select the target user page corresponding to each business requirement from the multiple user-end pages; Obtain the current user-side page for each of the aforementioned business requirements, and update the current user-side page to the target user-side page corresponding to each of the aforementioned business requirements using a preset business interface.

2. The multi-demand client page update method as described in claim 1, characterized in that, The step of bucketing the user dataset according to multiple business requirements to obtain multiple bucketed user data subsets includes: The user dataset is filtered according to multiple business requirements to obtain an initial user dataset; The initial user dataset is hashed to obtain its hash value, and the hash address of the hash value is extracted using a preset hash function. The hash values ​​with the same hash address are clustered, and the clustered hash values ​​are distributed to preset hash buckets according to the clustering category to obtain multiple bucketed user data subsets.

3. The multi-demand client page update method as described in claim 1, characterized in that, The method of collecting user behavior datasets corresponding to multiple click events using data tracking includes: Obtain the event tracking identifiers from multiple user pages, and construct a no-code event mapping table based on the event tracking identifiers; Obtain the static and dynamic parameters of the no-code mapping table; Based on the static parameters, collect static parameter data triggered by multiple click events; Based on the dynamic parameters, collect dynamic parameter data triggered by multiple click events; Obtain the user identifier, and merge the collected static parameter data and dynamic parameter data based on the user identifier to obtain a user behavior dataset corresponding to multiple click events.

4. The multi-demand client page update method as described in any one of claims 1-3, characterized in that, The step of updating the current user-side page using a preset business interface to the target user-side page corresponding to each business requirement includes: Obtain the update instruction for the target user page corresponding to each of the aforementioned business requirements, and obtain the Uniform Resource Locator (URL) for the target user page based on the update instruction. The unified resource locator is transmitted to the business interface, and the current user page is updated to the target user page corresponding to each business requirement through the business interface.

5. The multi-demand client page update method as described in claim 2, characterized in that, After assigning the clustered hash values ​​to preset hash buckets according to clustering categories, the method further includes: Obtain the spatial location of each hash value in any hash bucket, and calculate the maximum spatial distance between hash values ​​in any hash bucket based on the spatial location; Obtain the target spatial distance between the hash value to be queried and the cluster center in any of the hash buckets, and compare the target spatial distance with the maximum spatial distance; When the target spatial distance is not greater than the maximum spatial distance, the hash value to be queried is determined to be allocated to the hash bucket.

6. The multi-demand client page update method as described in claim 5, characterized in that, After comparing the target spatial distance with the maximum spatial distance, the method further includes: When the target spatial distance is greater than the maximum spatial distance, the updated maximum spatial distance of the hash value in the other hash bucket and the updated target spatial distance between the cluster center in the other hash bucket and the hash value to be queried are recalculated until the updated target spatial distance is not greater than the updated maximum spatial distance, and the hash value to be queried is determined to be assigned to the hash bucket.

7. A multi-demand client-side page update apparatus, used to implement the multi-demand client-side page update method as described in any one of claims 1 to 6, characterized in that, The device includes: The bucketing module is used to obtain the user dataset and multiple business requirements of the business products, and to perform bucketing operations on the user dataset according to the multiple business requirements to obtain multiple bucketed user data subsets. The matching module is used to create multiple user-end pages corresponding to multiple business requirements, obtain version identifiers of multiple user-end pages, and determine the matching relationship between multiple bucketed user data subsets and multiple user-end pages based on the version identifiers. The acquisition module is used to monitor click events triggered on the corresponding user terminal page for each of the bucketed user data subsets according to the matching relationship, and to collect user behavior datasets corresponding to multiple click events using tracking points. The update module is used to select the target user page corresponding to each business requirement from multiple user-end pages based on the collected user behavior datasets; obtain the current user page for each business requirement; and update the current user page to the target user page corresponding to each business requirement using a preset business interface.

8. An electronic device, characterized in that, The electronic device includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor to enable the at least one processor to perform the multi-demand client page update method as described in any one of claims 1 to 6.

9. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the multi-demand client page update method as described in any one of claims 1 to 6.

Images