Multi-service scenario fusion applet management system and method

Abstract

The application relates to the technical field of applet management, in particular to an applet management system and method for multi-service scene fusion. The method comprises the following steps: acquiring behavior data of an applet visitor, judging whether the visitor has the permission to load an applet display page based on the behavior data; adjusting the display order of service scene units on the applet display page according to the timeliness sequence of the visitor, and displaying the applet display page on the mobile terminal corresponding to the visitor with the permission; acquiring the service scene units clicked by the visitor on the applet display page, and respectively calculating the correlation index between the service scene units clicked by the visitor and other service scene units on the applet display page; and updating the timeliness sequence based on the correlation index, wherein the updated timeliness sequence is used for management analysis of the next visit, and the problem that the arrangement order and display mode of the applet service scene units cannot be dynamically adjusted according to the real-time demand and use scene of the user can be solved.

Description

Technical Field

[0001] This invention relates to the field of mini-program management technology, specifically to a mini-program management system and method that integrates multiple service scenarios. Background Technology

[0002] As the core architecture supporting the stable operation of mini-programs and efficient user service, the importance of mini-program management systems is increasingly prominent. On the one hand, existing mini-program management systems often only consider the current access request when making permission judgments, failing to fully utilize users' historical behavior data to predict future behavior trends and thus unable to achieve dynamic permission adjustments. On the other hand, the layout of most mini-program display pages currently adopts a fixed pattern; the arrangement and display method of service scenario units are determined during the development phase, making it difficult to dynamically adjust according to users' real-time needs and usage scenarios. Different users see the same page layout when accessing mini-programs at different times, lacking personalization and dynamic optimization, and failing to meet users' personalized needs.

[0003] Therefore, there is an urgent need for a mini-program management system and method that integrates multiple service scenarios to solve the above problems. Summary of the Invention

[0004] The purpose of this invention is to provide a mini-program management system and method that integrates multiple service scenarios: aiming to solve the problem that the arrangement order and display method of mini-program service scenario units cannot be dynamically adjusted according to the user's real-time needs and usage scenarios.

[0005] The objective of this invention can be achieved through the following technical solutions:

[0006] On the one hand, a mini-program management system integrating multiple service scenarios, the system includes:

[0007] The permission judgment module is used to respond to the access requests of mini-program visitors to obtain the visitor's behavior data, and to determine whether the visitor has the permission to load the mini-program's display page based on the behavior data;

[0008] The management and analysis module is used to adjust the display order of service scenario units on the mini-program display page according to the timeliness sequence of visitors, and to display the mini-program display page on the mobile terminal corresponding to the authorized visitor;

[0009] The correlation calculation module is used to obtain the service scenario units clicked by visitors on the mini program display page, and calculate the correlation index between the service scenario units clicked by visitors and other service scenario units on the mini program display page.

[0010] The timeliness sequence update module is used to update the timeliness sequence based on the correlation index. The updated timeliness sequence is used for management analysis on the next access.

[0011] Furthermore, determining whether a visitor has permission to load and display the mini-program page based on behavioral data specifically includes the following process:

[0012] Based on behavioral data, the loading characteristics and cache overflow risk values ​​of the mobile terminal within a preset time period before the visitor sends an access request are obtained. The applications loaded on the mobile terminal are numbered in chronological order of loading time, and all loaded applications are marked as execution objects. The execution code is composed of the numbers of all execution objects within the preset time period. The key of the visitor within the preset time period is composed of the loading characteristics, the cache overflow risk value, and the execution code. The key is decrypted and verified. If the decryption and verification are successful, it is determined that the visitor has the permission to load the mini-program display page. If the decryption and verification are unsuccessful, it is determined that the visitor does not have the permission to load the mini-program display page.

[0013] Furthermore, obtaining the loading characteristics of the mobile terminal within a preset time period before the visitor sends an access request based on behavioral data specifically includes the following process:

[0014] The download speed of the mobile terminal is obtained within a preset time period before the visitor sends an access request based on behavioral data. The preset time period includes several detection moments, each corresponding to a download speed. A rectangular coordinate system is established with the download speed at each detection moment as the Y-axis and the execution time at each detection moment as the X-axis. A download speed characterization curve is generated by plotting points. The lower peak and lower valley values ​​in the download speed characterization curve are statistically analyzed. The lower peak value is the maximum value of the download speed, and the lower valley value is the minimum value of the download speed. The peak-valley difference between the lower peak and lower valley values ​​is calculated. Perpendicular lines are drawn from the two endpoints of the download speed characterization curve to the X-axis to obtain two perpendicular line segments. A graph is formed by the download speed characterization curve, the two perpendicular line segments, and the X-axis. The area of ​​the graph is calculated, and the product of the area of ​​the graph and the peak-valley difference after unifying the dimensions is recorded as the download speed characterization value.

[0015] Furthermore, obtaining the cache overflow risk value of the mobile terminal within a preset time period before the visitor sends an access request based on behavioral data specifically includes the following process:

[0016] The system acquires the running and closing status information of mini-programs on various mobile terminals within a preset time period, which includes several detection times. It obtains the number of mini-programs running and closing at each detection time. A Cartesian coordinate system is established with the number of detection times as the X-axis and the number of mini-programs running and closing as the Y-axis. Mini-program running curves and mini-program closing curves are plotted by plotting points. The system then obtains the number of all rising segments from the running curves, the sum of the number of rising segments, falling segments, and horizontal segments, and calculates the ratio between the number of rising segments and the sum of the sum of the numbers. This ratio is marked as the processing evaluation value. Simultaneously, the system acquires the portion of the mini-program closing curve whose slope exceeds a preset slope threshold. This portion is recorded as the overflow trend curve. The integral value of the overflow trend curve is calculated and recorded as the overflow trend evaluation value. Finally, the difference between the processing evaluation value and the overflow trend evaluation value after data normalization is obtained, and this difference is recorded as the cache overflow risk value.

[0017] Furthermore, the decryption and verification of the key specifically includes the following process:

[0018] Retrieve the stored encrypted key; decrypt the encrypted key using the server's decryption key to obtain the original key string; parse the decrypted key string according to the format it was generated in, separating the load representation value, buffer overflow risk value, and executable code; check if the load representation value is within a first preset range. If it exceeds the first preset range, the verification fails; if it does not exceed the first preset range, the verification succeeds; similarly, check if the buffer overflow risk value is within a second preset range. If it exceeds the second preset range, the verification fails; if it does not exceed the second preset range, the verification succeeds; retrieve the list of applications currently loaded on the mobile terminal, number them according to their loading time, generate the executable code for the current moment, and compare the generated executable code with the executable code parsed from the key. If they are completely identical, the executable code verification passes; otherwise, the verification fails.

[0019] Furthermore, obtaining the timeliness sequence of visitors specifically includes the following processes:

[0020] Obtain the timeliness sequence value of each service scenario unit, and sort all service scenario units in descending order of their timeliness sequence values. The sorted sequence generates a sequence, which is the visitor's timeliness sequence. Obtaining the timeliness sequence value of each service scenario unit includes:

[0021] For each service scenario unit, the timeliness parameter of each service scenario unit is obtained. The timeliness parameter acquisition includes: identifying the content keywords contained in each service scenario unit based on the bag-of-words model; using the identified content keywords to obtain the timeliness parameter of each service scenario unit through a search engine; obtaining the historical usage frequency of each service scenario unit; and substituting the timeliness parameter SX and the historical usage frequency SY of each service scenario unit into the calculation formula to obtain the timeliness sequence value of each service scenario unit. The calculation formula is as follows: ,in, For time-sensitive sequence values, , These are the weighting coefficients for the timeliness parameter and the weighting coefficients for the historical usage frequency, respectively.

[0022] Furthermore, adjusting the display order of service scenario units on the mini-program display page according to the timeliness sequence of visitors specifically includes the following process:

[0023] Determine the service scenario units that need adjustment based on the timeliness sequence. And determine the service scenario units that need to be adjusted. Position in the original display order;

[0024] If the service scenario unit needs adjustment If it is located at the first position in the original display order, then the service scene unit that needs to be adjusted is obtained. The timeliness sequence value of the corresponding adjacent service scenario unit on the right The timeliness sequence value corresponding to the service scene unit located in the original display order. If the service scenario unit needs to be adjusted Time-of-life sequence value Greater than and less than Then the service scenario units that need to be adjusted will be... Move to The right side of the corresponding service scenario unit, up to the service scenario unit that needs adjustment. The timeliness sequence values ​​on both sides of the adjacent sequence are greater than ;

[0025] If the service scenario unit needs adjustment If a service scenario unit is located in the middle or at the end of its original display order, its display order on the mini-program display page will be adjusted according to the timeliness of the visitor's information.

[0026] Furthermore, calculating the correlation index between the service scenario unit clicked by the visitor and other service scenario units displayed on the mini-program page specifically includes the following process:

[0027] Extract the service scenario field name of the service scenario unit clicked by the visitor and the service scenario unit clicked by the visitor;

[0028] Perform PCA analysis on the field names to obtain the dependencies between the service scenario unit clicked by the visitor and the field names of other service scenario units.

[0029] The correlation index between the service scenario unit clicked by the visitor and other service scenario units displayed on the mini program page is determined based on the dependency relationship.

[0030] Furthermore, the process of updating the novel sequence based on the correlation index specifically includes the following steps:

[0031] Load the correlation index threshold, compare each correlation index with the correlation index threshold, if the correlation index is greater than the correlation index threshold, calculate the difference between the correlation index and the correlation index threshold, add the difference to the timeliness sequence value corresponding to the service scenario unit clicked by the visitor, and obtain the updated timeliness sequence value. If the correlation index is greater than the correlation index threshold, calculate the difference between the correlation index and the correlation index threshold, subtract the difference from the timeliness sequence value corresponding to the service scenario unit clicked by the visitor, and obtain the updated timeliness sequence value. Update the timeliness sequence based on the updated timeliness sequence value.

[0032] On the other hand, a method for managing mini-programs that integrates multiple service scenarios includes:

[0033] Respond to access requests from mini-program visitors to obtain their behavioral data, and determine whether the visitor has permission to load the mini-program's display page based on the behavioral data; adjust the display order of service scenario units on the mini-program's display page according to the visitor's timeliness sequence, and display the mini-program's display page on the mobile terminal corresponding to the authorized visitor; obtain the service scenario units clicked by the visitor on the mini-program's display page, and calculate the correlation index between the clicked service scenario units and other service scenario units on the mini-program's display page; update the timeliness sequence based on the correlation index, and use the updated timeliness sequence for management and analysis of the next visit.

[0034] Compared to existing solutions, the beneficial effects achieved by this invention are:

[0035] The permission judgment module of this invention can respond to the access requests of mini-program visitors in real time, comprehensively acquire the visitor's behavioral data, and accurately judge whether the visitor has the permission to load the mini-program display page based on this data, thereby avoiding the damage to the system caused by the leakage of sensitive information and malicious operations, and building a solid security defense for mini-program operation.

[0036] Based on the timeliness of visitors, service scenario units are arranged sequentially on the mini-program display page and accurately displayed on the mobile terminals corresponding to authorized visitors. This intelligent page layout fully considers user habits and preferences, enabling users to quickly find the service scenario units they need, greatly reducing the time and effort spent searching among numerous options. Compared with traditional fixed page layouts, it can provide personalized displays based on the characteristics of different users, improving the convenience and smoothness of user operation.

[0037] By acquiring the service scenario units clicked by visitors on the mini-program's display page and deeply calculating their correlation index with other service scenario units, operators can optimize service recommendation strategies based on these correlation indices, providing users with more accurate and personalized service recommendations and increasing user acceptance and usage of recommended services. Attached Figure Description

[0038] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this invention. For those skilled in the art, other drawings can be obtained based on these drawings.

[0039] Figure 1 This is a system block diagram of a mini-program management system that integrates multiple service scenarios according to an embodiment of the present invention;

[0040] Figure 2 This is a flowchart of a mini-program management system that integrates multiple service scenarios according to an embodiment of the present invention;

[0041] Figure 3 This is a flowchart of a mini-program management method that integrates multiple service scenarios according to an embodiment of the present invention. Detailed Implementation

[0042] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0043] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more exemplary embodiments. Numerous specific details are provided in the following description to give a full understanding of exemplary embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced with one or more of the specific details omitted, or other methods, components, steps, etc., can be employed. In other instances, well-known structures, methods, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0044] This embodiment provides a mini-program management system that integrates multiple service scenarios. Figure 1 This is a system block diagram of a mini-program management system integrating multiple service scenarios according to an embodiment of the present invention, such as... Figure 1 As shown, the system includes:

[0045] The permission judgment module is used to respond to the access requests of mini-program visitors to obtain the visitor's behavior data, and to determine whether the visitor has the permission to load the mini-program's display page based on the behavior data;

[0046] The management and analysis module is used to adjust the display order of service scenario units on the mini-program display page according to the timeliness sequence of visitors, and to display the mini-program display page on the mobile terminal corresponding to the authorized visitor;

[0047] The correlation calculation module is used to obtain the service scenario units clicked by visitors on the mini program display page, and calculate the correlation index between the service scenario units clicked by visitors and other service scenario units on the mini program display page.

[0048] The timeliness sequence update module is used to update the timeliness sequence based on the correlation index. The updated timeliness sequence is used for management analysis on the next access.

[0049] In summary, this invention can respond to access requests from mini-program visitors in real time, comprehensively acquire visitor behavior data, and accurately determine whether visitors have the permission to load the mini-program display page based on this data. This avoids damage to the system caused by sensitive information leakage and malicious operations. Based on the visitor's timeliness sequence, service scenario units are arranged sequentially on the mini-program display page and accurately displayed on the mobile terminal corresponding to the authorized visitor. The intelligent page layout fully considers user habits and preferences, enabling users to quickly find the required service scenario units. Compared with traditional fixed page layouts, it can provide personalized displays based on the characteristics of different users, improving the convenience and smoothness of user operation. By acquiring the service scenario units clicked by visitors on the mini-program display page and deeply calculating their correlation index with other service scenario units, operators can optimize service recommendation strategies based on these correlation indices, providing users with more accurate and personalized service recommendations, and improving user acceptance and usage rates of recommended services.

[0050] It is worth noting that the embodiments of the present invention can be applied to a housekeeping service mini-program, and the service scenario units may include annual service, fine window cleaning, appliance cleaning, deep cleaning, caregiver / maternity nurse services, soft furnishing cleaning, new home cleaning, and organization.

[0051] In some embodiments, determining whether a visitor has permission to load the mini-program's display page based on behavioral data specifically includes the following process:

[0052] Based on behavioral data, the loading characteristics and cache overflow risk values ​​of the mobile terminal within a preset time period before the visitor sends an access request are obtained. The applications loaded on the mobile terminal are numbered in chronological order of loading time, and all loaded applications are marked as execution objects. The execution code is composed of the numbers of all execution objects within the preset time period. The key of the visitor within the preset time period is composed of the loading characteristics, the cache overflow risk value, and the execution code. The key is decrypted and verified. If the decryption and verification are successful, it is determined that the visitor has the permission to load the mini-program display page. If the decryption and verification are unsuccessful, it is determined that the visitor does not have the permission to load the mini-program display page.

[0053] In some embodiments, obtaining the loading characteristics of the mobile terminal within a preset time period before a visitor sends an access request based on behavioral data specifically includes the following process:

[0054] The download speed of the mobile terminal is obtained within a preset time period before the visitor sends an access request based on behavioral data. The preset time period includes several detection moments, each corresponding to a download speed. A rectangular coordinate system is established with the download speed at each detection moment as the Y-axis and the execution time at each detection moment as the X-axis. A download speed characterization curve is generated by plotting points. The lower peak and lower valley values ​​in the download speed characterization curve are statistically analyzed. The lower peak value is the maximum value of the download speed, and the lower valley value is the minimum value of the download speed. The peak-valley difference between the lower peak and lower valley values ​​is calculated. Perpendicular lines are drawn from the two endpoints of the download speed characterization curve to the X-axis to obtain two perpendicular line segments. A graph is formed by the download speed characterization curve, the two perpendicular line segments, and the X-axis. The area of ​​the graph is calculated, and the product of the area of ​​the graph and the peak-valley difference after unifying the dimensions is recorded as the download speed characterization value.

[0055] In some embodiments, obtaining the cache overflow risk value of the mobile terminal within a preset time period before a visitor sends an access request based on behavioral data specifically includes the following process:

[0056] The system acquires the running and closing status information of mini-programs on various mobile terminals within a preset time period, which includes several detection times. It obtains the number of mini-programs running and closing at each detection time. A Cartesian coordinate system is established with the number of detection times as the X-axis and the number of mini-programs running and closing as the Y-axis. Mini-program running curves and mini-program closing curves are plotted by plotting points. The system then obtains the number of all rising segments from the running curves, the sum of the number of rising segments, falling segments, and horizontal segments, and calculates the ratio between the number of rising segments and the sum of the sum of the numbers. This ratio is marked as the processing evaluation value. Simultaneously, the system acquires the portion of the mini-program closing curve whose slope exceeds a preset slope threshold. This portion is recorded as the overflow trend curve. The integral value of the overflow trend curve is calculated and recorded as the overflow trend evaluation value. Finally, the difference between the processing evaluation value and the overflow trend evaluation value after data normalization is obtained, and this difference is recorded as the cache overflow risk value.

[0057] Furthermore, the decryption and verification of the key specifically includes the following process:

[0058] Retrieve the stored encrypted key; decrypt the encrypted key using the server's decryption key to obtain the original key string; parse the decrypted key string according to the format it was generated in, separating the load representation value, buffer overflow risk value, and executable code; check if the load representation value is within a first preset range. If it exceeds the first preset range, the verification fails; if it does not exceed the first preset range, the verification succeeds; similarly, check if the buffer overflow risk value is within a second preset range. If it exceeds the second preset range, the verification fails; if it does not exceed the second preset range, the verification succeeds; retrieve the list of applications currently loaded on the mobile terminal, number them according to their loading time, generate the executable code for the current moment, and compare the generated executable code with the executable code parsed from the key. If they are completely identical, the executable code verification passes; otherwise, the verification fails.

[0059] In some embodiments, for each service scenario unit, a timeliness parameter is obtained. This timeliness parameter acquisition includes: identifying content keywords contained in each service scenario unit based on a bag-of-words model. The bag-of-words model can extract and identify content keywords based on stored content keywords. For example, content keywords could be "window cleaning" or "caregiver." The identified content keywords are then used by a search engine to obtain the timeliness parameter for each service scenario unit. Specifically, this value is 0 when the webpage content is first crawled and gradually increases over time. The search engine sets a maximum timeliness value for each page. When the timeliness value of the page content reaches this maximum value, the search engine re-crawls the page to update its timeliness parameter. The time since the last crawl: This metric reflects the time interval since the search engine last crawled the page content. The shorter the time interval, the higher the update frequency of the page content and the stronger its timeliness.

[0060] Obtain the historical usage frequency for each service scenario unit, and substitute the timeliness parameter SX and historical usage frequency SY for each service scenario unit into the calculation formula to obtain the timeliness sequence value for each service scenario unit. The calculation formula is as follows: ,in, For time-sensitive sequence values, , These are the weighting coefficients for the timeliness parameter and the weighting coefficients for the historical usage frequency, respectively.

[0061] Furthermore, the timeliness sequence value of each service scenario unit is obtained, and all service scenario units are sorted in descending order of their timeliness sequence values. After sorting, a sequence is generated, which is the timeliness sequence of the visitor.

[0062] In some embodiments, adjusting the display order of service scenario units on the mini-program display page according to the visitor's timeliness sequence specifically includes the following process:

[0063] Determine the service scenario units that need adjustment based on the timeliness sequence. And determine the service scenario units that need to be adjusted. Position in the original display order;

[0064] If the service scenario unit needs adjustment If it is located at the first position in the original display order, then the service scene unit that needs to be adjusted is obtained. The timeliness sequence value of the corresponding adjacent service scenario unit on the right The timeliness sequence value corresponding to the service scene unit located in the original display order. If the service scenario unit needs to be adjusted Time-of-life sequence value Greater than and less than Then the service scenario units that need to be adjusted will be... Move to The right side of the corresponding service scenario unit, up to the service scenario unit that needs adjustment. The timeliness sequence values ​​on both sides of the adjacent sequence are greater than ;

[0065] If the service scenario unit needs adjustment If a service scenario unit is located in the middle or at the end of its original display order, its display order on the mini-program display page will be adjusted according to the timeliness of the visitor's information.

[0066] In some embodiments, Figure 2 This is a flowchart of a mini-program management system integrating multiple service scenarios according to an embodiment of the present invention, such as... Figure 2 As shown, the specific process for calculating the correlation index between the service scenario unit clicked by the visitor and other service scenario units on the mini-program display page includes the following steps:

[0067] Step S201: Extract the extracted service scenario field name of the service scenario unit clicked by the visitor and other service scenario units respectively;

[0068] Specifically, the extracted service scenario field names of the service scenario units clicked by visitors and other service scenario units are extracted based on natural language processing technology;

[0069] Step S202: Perform PCA analysis on the field names to obtain the dependency relationships between the service scenario unit clicked by the visitor and the field names of other service scenario units;

[0070] (1) Form a matrix T from the associated fields and calculate the covariance matrix S of the samples in matrix T;

[0071] (2) Calculate the eigenvectors of the covariance matrix S , ,…, And eigenvalues, t = 1,2,…,n;

[0072] (3) Project the data onto the space of the feature vectors using the formula:

[0073]

[0074] in, The value is the value of the corresponding dimension in the original sample.

[0075] The goal of PCA is to find r (r < n) new variables that reflect the main characteristics of a subject, compress the size of the original data matrix, reduce the dimensionality of the eigenvectors, and select the least dimensional variable to summarize the most important features. Each new variable is a linear combination of the original variables, reflecting the combined effect of the original variables and having a certain practical meaning. These r new variables are called "principal components," and they can largely reflect the influence of the original n variables. Furthermore, these new variables are uncorrelated and orthogonal. Through principal component analysis, the data space is compressed, allowing the characteristics of multivariate data to be intuitively represented in a low-dimensional space. Furthermore, it visually demonstrates the dependencies between field names.

[0076] Step S203: Determine the correlation index between the service scenario unit clicked by the visitor and other service scenario units on the mini program display page based on the dependency relationship.

[0077] Specifically, it determines whether there is common upstream data or data source among the field names. If so, it determines that the relationship between the service scenario unit clicked by the visitor and other service scenario units on the mini program display page is a data flow-based relationship. Then, it queries the data flow relationship table to query the correlation index, where the data flow relationship table stores a pre-defined correlation index. If not, the correlation index is 0.

[0078] Furthermore, the process of updating the novel sequence based on the correlation index specifically includes the following steps:

[0079] Load the correlation index threshold, compare each correlation index with the correlation index threshold, if the correlation index is greater than the correlation index threshold, calculate the difference between the correlation index and the correlation index threshold, add the difference to the timeliness sequence value corresponding to the service scenario unit clicked by the visitor, and obtain the updated timeliness sequence value. If the correlation index is greater than the correlation index threshold, calculate the difference between the correlation index and the correlation index threshold, subtract the difference from the timeliness sequence value corresponding to the service scenario unit clicked by the visitor, and obtain the updated timeliness sequence value. Update the timeliness sequence based on the updated timeliness sequence value.

[0080] In some embodiments, the present invention also provides a method for managing mini-programs that integrates multiple service scenarios. Figure 3 This is a flowchart of a multi-service scenario integration mini-program management method according to an embodiment of the present invention, as shown below. Figure 3 As shown, the method includes the following steps:

[0081] Step S301: Respond to the access request of the mini-program visitor to obtain the visitor's behavior data, and determine whether the visitor has the permission to load the mini-program display page based on the behavior data;

[0082] Step S302: Adjust the display order of service scenario units on the mini-program display page according to the timeliness sequence of visitors, and display the mini-program display page on the mobile terminal corresponding to the authorized visitor;

[0083] Step S303: Obtain the service scenario unit clicked by the visitor on the mini program display page, and calculate the correlation index between the service scenario unit clicked by the visitor and other service scenario units on the mini program display page;

[0084] Step S304: Update the timeliness sequence based on the correlation index. The updated timeliness sequence is used for management analysis of the next visit.

[0085] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0086] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0087] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0088] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0089] The units described as separate components may or may not be physically separate. The components shown as units 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 units can be selected to achieve the purpose of this embodiment according to actual needs.

[0090] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A mini-program management system integrating multiple service scenarios, characterized in that: The system includes: The permission judgment module is used to respond to the access requests of mini-program visitors to obtain the visitor's behavior data, and to determine whether the visitor has the permission to load the mini-program's display page based on the behavior data; The process of determining whether a visitor has permission to load and display a page in a mini-program based on behavioral data includes the following steps: Based on behavioral data, the loading characteristics and cache overflow risk values ​​of the mobile terminal within a preset time period before the visitor sends an access request are obtained. The applications loaded on the mobile terminal are numbered in chronological order of loading time, and all loaded applications are marked as execution objects. The execution code is composed of the numbers of all execution objects within the preset time period. The key of the visitor within the preset time period is composed of the loading characteristics, the cache overflow risk value, and the execution code. The key is decrypted and verified. If the decryption and verification are successful, it is determined that the visitor has the permission to load the mini-program display page. If the decryption and verification are unsuccessful, it is determined that the visitor does not have the permission to load the mini-program display page. The management and analysis module is used to adjust the display order of service scenario units on the mini-program display page according to the timeliness sequence of visitors, and to display the mini-program display page on the mobile terminal corresponding to the authorized visitor; Specifically, the timeliness sequence value of each service scenario unit is obtained, and all service scenario units are sorted in descending order of their timeliness sequence values. This sorting generates a sequence, which is the visitor's timeliness sequence. Obtaining the timeliness sequence value of each service scenario unit includes: For each service scenario unit, the timeliness parameter of each service scenario unit is obtained. The timeliness parameter acquisition includes: identifying the content keywords contained in each service scenario unit based on the bag-of-words model; using the identified content keywords to obtain the timeliness parameter of each service scenario unit through a search engine; obtaining the historical usage frequency of each service scenario unit; and substituting the timeliness parameter SX and the historical usage frequency SY of each service scenario unit into the calculation formula to obtain the timeliness sequence value of each service scenario unit. The calculation formula is as follows: ,in, For time-sensitive sequence values, , These are the weighting coefficients for the timeliness parameter and the weighting coefficients for historical usage frequency, respectively. The correlation calculation module is used to obtain the service scenario units clicked by visitors on the mini program display page, and calculate the correlation index between the service scenario units clicked by visitors and other service scenario units on the mini program display page. The timeliness sequence update module is used to update the timeliness sequence based on the correlation index. The updated timeliness sequence is used for management analysis on the next access.

2. The mini-program management system for multi-service scenario integration according to claim 1, characterized in that, Obtaining the loading characteristics of the mobile terminal within a preset time period before a visitor sends an access request based on behavioral data specifically includes the following process: The download speed of the mobile terminal is obtained within a preset time period before the visitor sends an access request based on behavioral data. The preset time period includes several detection moments, each corresponding to a download speed. A rectangular coordinate system is established with the download speed at each detection moment as the Y-axis and the execution time at each detection moment as the X-axis. A download speed characterization curve is generated by plotting points. The lower peak and lower valley values ​​in the download speed characterization curve are statistically analyzed. The lower peak value is the maximum value of the download speed, and the lower valley value is the minimum value of the download speed. The peak-valley difference between the lower peak and lower valley values ​​is calculated. Perpendicular lines are drawn from the two endpoints of the download speed characterization curve to the X-axis to obtain two perpendicular line segments. A graph is formed by the download speed characterization curve, the two perpendicular line segments, and the X-axis. The area of ​​the graph is calculated, and the product of the area of ​​the graph and the peak-valley difference after unifying the dimensions is recorded as the download speed characterization value.

3. The mini-program management system for multi-service scenario integration according to claim 1, characterized in that, Based on behavioral data, the specific cache overflow risk value of the mobile terminal within a preset time period before the visitor sends an access request is obtained. The process includes the following: The system acquires the running and closing status information of mini-programs on various mobile terminals within a preset time period, which includes several detection times. It obtains the number of mini-programs running and closing at each detection time. A Cartesian coordinate system is established with the number of detection times as the X-axis and the number of mini-programs running and closing as the Y-axis. Mini-program running curves and mini-program closing curves are plotted by plotting points. The system then obtains the number of all rising segments from the running curves, the sum of the number of rising segments, falling segments, and horizontal segments, and calculates the ratio between the number of rising segments and the sum of the sum of the numbers. This ratio is marked as the processing evaluation value. Simultaneously, the system acquires the portion of the mini-program closing curve whose slope exceeds a preset slope threshold. This portion is recorded as the overflow trend curve. The integral value of the overflow trend curve is calculated and recorded as the overflow trend evaluation value. Finally, the difference between the processing evaluation value and the overflow trend evaluation value after data normalization is obtained, and this difference is recorded as the cache overflow risk value.

4. The mini-program management system for multi-service scenario integration according to claim 1, characterized in that, Decryption and verification of the key in detail The process includes the following: Retrieve the stored encrypted key; Use the server's decryption key to decrypt the encrypted key and obtain the original key string; The decrypted key string is parsed according to the format it was generated in, separating the load representation value, buffer overflow risk value, and execution code; Check if the loaded representation value is within the first preset range. If it exceeds the first preset range, the verification fails; if it does not exceed the first preset range, the verification succeeds. Similarly, check whether the cache overflow risk value is within the second preset range. If it exceeds the second preset range, the verification fails; if it does not exceed the second preset range, the verification succeeds. Obtain the list of applications currently loaded on the mobile terminal, number them in chronological order of loading time, generate the execution code for the current moment, and compare the generated execution code with the execution code parsed from the key. If the two are completely identical, the execution code verification passes; otherwise, the verification fails.

5. The mini-program management system for multi-service scenario integration according to claim 1, characterized in that, Adjusting the display order of service scenario units on the mini-program display page according to the timeliness of visitors is specifically... The process includes the following: Determine the service scenario units that need adjustment based on the timeliness sequence. And determine the service scenario units that need to be adjusted. Position in the original display order; If the service scenario unit needs adjustment If it is located at the first position in the original display order, then the service scene unit that needs to be adjusted is obtained. The timeliness sequence value of the corresponding adjacent service scenario unit on the right The timeliness sequence value corresponding to the service scene unit located in the original display order. If the service scenario unit needs to be adjusted Time-of-life sequence value Greater than and less than Then the service scenario units that need to be adjusted will be... Move to The right side of the corresponding service scenario unit, up to the service scenario unit that needs adjustment. The timeliness sequence values ​​on both sides of the adjacent sequence are greater than ; If the service scenario unit needs adjustment If a service scenario unit is located in the middle or at the end of its original display order, its display order on the mini-program display page will be adjusted according to the timeliness of the visitor's information.

6. The mini-program management system for multi-service scenario integration according to claim 1, characterized in that, The specific process for calculating the correlation index between the service scenario unit clicked by the visitor and other service scenario units displayed on the mini-program page includes the following steps: Extract the service scenario field name of the service scenario unit clicked by the visitor and the service scenario unit clicked by the visitor; Perform PCA analysis on the field names to obtain the dependencies between the service scenario unit clicked by the visitor and the field names of other service scenario units. The correlation index between the service scenario unit clicked by the visitor and other service scenario units displayed on the mini program page is determined based on the dependency relationship.

7. The mini-program management system for multi-service scenario integration according to claim 1, characterized in that, The process of updating the novel sequence based on the correlation index specifically includes the following steps: Load the correlation index threshold, compare each correlation index with the correlation index threshold, if the correlation index is greater than the correlation index threshold, calculate the difference between the correlation index and the correlation index threshold, add the difference to the timeliness sequence value corresponding to the service scenario unit clicked by the visitor, and obtain the updated timeliness sequence value. If the correlation index is greater than the correlation index threshold, calculate the difference between the correlation index and the correlation index threshold, subtract the difference from the timeliness sequence value corresponding to the service scenario unit clicked by the visitor, and obtain the updated timeliness sequence value. Update the timeliness sequence based on the updated timeliness sequence value.

8. A method for managing mini-programs that integrates multiple service scenarios, characterized in that: The method, applicable to the mini-program management system for multi-service scenario integration as described in any one of claims 1 to 7, comprises: Respond to access requests from mini-program visitors to obtain their behavioral data, and determine whether the visitor has permission to load the mini-program display page based on the behavioral data; adjust the display order of service scenario units on the mini-program display page according to the visitor's timeliness sequence, and display the mini-program display page on the mobile terminal corresponding to the authorized visitor; obtain the service scenario units clicked by the visitor on the mini-program display page, and calculate the correlation index between the clicked service scenario units and other service scenario units on the mini-program display page; update the timeliness sequence based on the correlation index, and use the updated timeliness sequence for management and analysis of the next visit; The process of determining whether a visitor has permission to load and display a page in a mini-program based on behavioral data includes the following steps: Based on behavioral data, the loading characteristics and cache overflow risk values ​​of the mobile terminal within a preset time period before the visitor sends an access request are obtained. The applications loaded on the mobile terminal are numbered in chronological order of loading time, and all loaded applications are marked as execution objects. The execution code is composed of the numbers of all execution objects within the preset time period. The key of the visitor within the preset time period is composed of the loading characteristics, the cache overflow risk value, and the execution code. The key is decrypted and verified. If the decryption and verification are successful, it is determined that the visitor has the permission to load the mini-program display page. If the decryption and verification are unsuccessful, it is determined that the visitor does not have the permission to load the mini-program display page. Specifically, the timeliness sequence value of each service scenario unit is obtained, and all service scenario units are sorted in descending order of their timeliness sequence values. This sorting generates a sequence, which is the visitor's timeliness sequence. Obtaining the timeliness sequence value of each service scenario unit includes: For each service scenario unit, the timeliness parameter of each service scenario unit is obtained. The timeliness parameter acquisition includes: identifying the content keywords contained in each service scenario unit based on the bag-of-words model; using the identified content keywords to obtain the timeliness parameter of each service scenario unit through a search engine; obtaining the historical usage frequency of each service scenario unit; and substituting the timeliness parameter SX and the historical usage frequency SY of each service scenario unit into the calculation formula to obtain the timeliness sequence value of each service scenario unit. The calculation formula is as follows: ,in, For time-sensitive sequence values, , These are the weighting coefficients for the timeliness parameter and the weighting coefficients for the historical usage frequency, respectively.

Images