Virtual power plant front-end layout dynamic optimization method and system based on user behavior driving

Abstract

The invention relates to the technical field of front-end page layout, in particular to a user behavior driven virtual power plant front-end layout dynamic optimization method and system, and the method comprises the steps: generating a dynamic behavior tag through clustering analysis based on interactive behavior data and in combination with predefined static business role information of a user, establishing a user interface preference model, and forming a unified multi-level user portrait containing static roles and dynamic behaviors at the same time; and executing the following operations through the dynamic layout engine to generate and output a personalized front-end layout: calculating the display priority of each menu item and functional component; automatically matching an interface layout template which is most adaptive to the current user portrait from a preset layout template library; and according to the display priority, carrying out differential explicit and implicit control and arrangement optimization on the functional components in the interface. The problems that an existing system is rigid in interface, low in operation efficiency and lack of intelligent perception and evolutionary ability are solved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of front-end page layout, in particular to a virtual power plant front-end layout dynamic optimization method and system based on user behavior driving. BACKGROUND

[0002] The virtual power plant management system is the core platform for coordinating distributed energy and power grid operation, and its users include dispatchers, traders, energy owners and other professional roles. The working responsibilities and core task flows of different roles are fundamentally different, however, the front-end interface of the existing system generally adopts a static and unified layout mode, which cannot adapt to such professional demand differences, resulting in low operation efficiency and high learning cost.

[0003] Specifically, the interface is rigid, and high-frequency functions are often buried in multiple levels of menus, which users need to click multiple times to access, and the navigation path is long. It cannot be optimized based on the actual use behavior of the user, and lacks the ability of personalized dynamic adjustment, and the user experience is stagnant. There is a scheme in the prior art that adjusts the web template by analyzing user browsing behavior. However, when this scheme is applied to a complex virtual power plant system, it exposes the following essential defects: first, its optimization only relies on generalized browsing behaviors such as clicks and scrolls, completely ignoring the "business role" context, resulting in an initial layout lacking precision; second, its optimization granularity is limited to column adjustment at the page level, and cannot perceive and understand the cross-functional coherent task flow in the virtual power plant, such as "monitoring-analysis-dispatching", and cannot achieve intelligent aggregation at a deep and component level.

[0004] Therefore, there is an urgent need in the art for a dynamic layout solution that can deeply integrate business roles and real-time behavior data, and has the ability of continuous learning and optimization, in order to improve the professional level and intelligent interaction experience of the virtual power plant management system. SUMMARY

[0005] To solve the above problems, the present application provides a virtual power plant front-end layout dynamic optimization method and system based on user behavior driving.

[0006] In a first aspect, the present application provides a virtual power plant front-end layout dynamic optimization method based on user behavior driving, comprising the following steps: S1, collecting user interaction behavior data in the virtual power plant management system; the interaction behavior data at least includes menu item click events, function module access and exit events, and interface jump events, wherein each data records a corresponding user identifier and a timestamp; S2, based on the collected interaction behavior data, and in combination with the user's pre-defined static business role information, generate dynamic behavior labels through cluster analysis, and establish a user interface preference model, forming a unified multi-level user portrait containing static roles and dynamic behaviors; S3, based on the multi-level user portrait, the following operations are performed by a dynamic layout engine to generate and output a personalized front-end layout: (a) calculating the display priority of each menu item and functional component; (b) automatically matching the interface layout template that best fits the current user portrait from the pre-set layout template library; (c) according to the display priority, differentiating the display and control of the functional components in the interface and optimizing the arrangement; S4, collect the subsequent interaction data of the user on the personalized front-end layout and feed it back to S1 for updating the user portrait and optimizing the layout decision.

[0007] As a further limitation of the technical solution of the application, S1 step includes: S11, by implanting data collection probes in the front-end interface components of the virtual power plant management system, real-time capture of user clicks, browsing duration and page jump events; S12, convert the captured events into structured behavior logs, which at least include user ID, timestamp, operation object and operation type; S13, based on the behavior log, divide the session by user ID and timestamp, and filter out meaningless false operation events and heartbeat events using a business rule-based cleaning algorithm to construct user operation sequences representing complete operation tasks.

[0008] It is ensured that the collected interaction behavior data is high-quality, structured and rich in semantic information. This lays a reliable data foundation for subsequent accurate user portrait construction, avoids the interference of noise data on the analysis results, and improves the accuracy and reliability of the entire system optimization.

[0009] As a further limitation of the technical solution of the application, in S2, the pre-defined static business role information includes at least dispatchers, traders and energy owners; the system pre-sets differentiated initial interface layout templates and function permission sets for each role. It is clear that dispatchers, traders, energy owners and other core business roles are the starting point of system design, and differentiated initial templates and permissions are pre-set for different roles. This ensures that the system can provide professional and accurate basic work interface from the beginning, realizes role-based coarse-grained personalization, and solves the problem that the interface cannot meet the needs of professional division of labor.

[0010] As a further limitation of the technical solution of the application, the steps of S2 include: S21. Extract user behavior feature vectors within a set statistical period from the interactive behavior data. The vectors include at least menu item click frequency, function usage duration, and operation sequence pattern. S22. Calculate the behavioral feature vector using an unsupervised clustering algorithm to divide users into different behavioral clusters; and assign a dynamic behavioral label to each behavioral cluster, the label including at least high-frequency scheduling type, data browsing type, and transaction-driven type; S23. For each type of dynamic behavior label, assign a set of interface component preference weight vectors, wherein the weight vectors quantify the degree of preference of the user for different functional modules, data panels and operation controls. S24. Associate and map the preference weight vector with the corresponding dynamic behavior labels to construct a preliminary user interface preference model; S25. Using the predefined static business role information as the base layer, integrate the dynamic behavior tags and the corresponding preliminary user interface preference model, and encapsulate them together into a unified user profile data entity that can be directly called by the dynamic layout engine, thus forming a unified multi-level user profile. S26. Analyze the timestamp information in the interaction behavior data to identify the user's function usage patterns on weekdays and holidays, and during peak and off-peak electricity consumption periods; use the identified time patterns as a correction factor to optimize the classification results of dynamic behavior tags in S22, and / or to optimize the weight allocation of the interface component preference weight vector in S23.

[0011] It can sense and adapt to patterns in user behavior that change with business rhythms (such as peak and off-peak electricity consumption, weekdays / holidays). This makes user profiles and layout recommendations no longer static, but dynamically adaptable to real business scenarios, improving the accuracy of layout recommendations in complex business environments.

[0012] As a further limitation of the technical solution of the present invention, in step S3(a), the display priority of each menu item and functional component is calculated, which is specifically achieved by the following formula:

[0013] in, To display priority scores, Use frequency weights for functions Weighting based on feature usage time Assigning weights to business roles To normalize the click-through rate, To normalize usage time, The role-function relevance is dynamically adjusted based on the dynamic behavior tags in the user profile, including the weights for function usage frequency, function usage duration, and business role. The role-function relevance is obtained by querying a predefined role-function weight mapping table, which is established based on the business rules of the virtual power plant and the responsibilities and permissions of different roles. The weight values ​​in the mapping table are periodically and dynamically adjusted based on the historical average behavior data of the user group under the same role.

[0014] By incorporating the weight of business roles and the correlation between role functions as core variables in the calculation, the layout decision-making process takes into account both the user's immediate behavioral preferences and the long-term rigid requirements determined by their job responsibilities, achieving an intelligent balance between dynamic needs and static responsibilities.

[0015] As a further limitation of the technical solution of the present invention, in step S3(b), automatically matching the most suitable interface layout template from the preset layout template library specifically includes: S31. Based on the predefined static business role information in the user profile, select a set of candidate templates that meet the role criteria from the template library; S32. Based on the interface component preference weight vector in the user profile, calculate the cosine similarity with the preset component layout of each template in the candidate template set. S33. Select the template with the highest cosine similarity to the interface component preference weight vector as the most suitable interface layout template.

[0016] By quickly narrowing down the template pool through role-based matching, the professionalism of the basic framework is ensured. Then, by calculating cosine similarity, the template that best matches the user's personal preferences is selected from the candidate templates. This method balances matching accuracy and efficiency, avoiding the performance overhead of global matching in a large template library.

[0017] As a further limitation of the technical solution of the present invention, in step S3 (c), according to the display priority, the functional components within the interface are subject to differentiated display / hiding control and arrangement optimization, specifically including: S34. In the main workspace of the most suitable interface layout template, prioritize rendering and displaying the top N functional components with the highest priority. S35: Aggregate the functional components with a priority ranking of Nth or lower into the secondary menu; S36. Within the same area, functional components are arranged in descending order according to their display priority scores.

[0018] The rules specify detailed interface optimization principles, allowing high-frequency functions to be rendered directly in the core area while low-frequency functions are aggregated into secondary menus. This reduces user navigation steps and time spent searching for functions, fundamentally improving operational efficiency.

[0019] As a further limitation of the technical solution of the present invention, after the execution of step S3, the system provides a multi-level configuration collaboration mechanism. This collaboration mechanism allows users to manually fine-tune the personalized layout automatically generated by the system, and the user's manual configuration has the highest priority and is recorded as feedback data in the user profile for optimizing subsequent automatic layout generation.

[0020] Above the automated layout, the highest priority for manual user intervention is introduced. This not only respects the user's personal choices and enhances the user's sense of control over the system, but more importantly, it transforms the user's manual adjustments into valuable feedback data for the system's learning, achieving collaborative and closed-loop optimization between human and machine intelligence.

[0021] As a further limitation of the technical solution of the present invention, step S4 includes: S41. Collect the user's subsequent interaction behavior with the personalized front-end layout. The subsequent interaction behavior includes at least the click rate of rearranged functional components, the access depth of functions in the sub-menu, and the user's manual adjustment of the layout. S42. Compare subsequent interactive behaviors with the user profile and layout decisions used to generate the personalized front-end layout, and evaluate the effectiveness of the layout decisions. S43. Based on the evaluation results, dynamically adjust the preference weight vector of relevant functional components in the user interface preference model; and / or, modify the function usage frequency weight, function usage duration weight, and business role weight in the calculation formula of step S3(a).

[0022] The feedback loop works by evaluating the effectiveness of layout decisions and then adjusting the user preference model and layout generation algorithm accordingly. This ensures the system can track changes in user preferences, continuously iterate and optimize, and provide a consistent and accurate personalized experience.

[0023] Secondly, the present invention also provides a user behavior-driven dynamic optimization system for the front-end layout of a virtual power plant, used to implement the method described in the first aspect, comprising: The behavior data acquisition module is used to collect user interaction behavior data in the virtual power plant management system. The interaction behavior data includes at least menu item click events, function module access and exit events, and interface jump events, and each data record has a corresponding user identifier and timestamp. The user profile building module is used to generate dynamic behavior tags through cluster analysis based on the collected interaction behavior data and combined with the user's predefined static business role information, and to establish a user interface preference model to form a unified multi-level user profile that includes both static roles and dynamic behaviors. The dynamic layout engine module is used to calculate the display priority of each menu item and functional component; automatically match the interface layout template that best suits the current user profile from the preset layout template library; and perform differentiated display and hiding control and arrangement optimization of functional components in the interface according to the display priority to generate and output a personalized front-end layout. The closed-loop feedback module is used to collect subsequent interaction data of the user with the personalized front-end layout and feed it back to the behavior data collection module for updating the user profile and optimizing layout decisions.

[0024] As a further limitation of the technical solution of the present invention, the behavioral data acquisition module includes: The front-end probe unit is used to capture user clicks, browsing duration, and page jump events in real time by embedding data acquisition probes into the front-end interface components of the virtual power plant management system. The log structuring unit is used to transform captured events into structured behavior logs, which at least include user ID, timestamp, operation object, and operation type. The session construction and cleaning unit is used to divide sessions according to user ID and timestamp based on the behavior log, and to filter out meaningless erroneous operation events and heartbeat keep-alive events using a business rule-based cleaning algorithm, so as to construct a user operation sequence that represents a complete operation task.

[0025] As a further limitation of the technical solution of the present invention, the user profile construction module includes: The role management unit is used to store and manage the predefined static business role information and its corresponding initial interface layout template and function permission set; The behavior analysis unit is used to extract user behavior feature vectors from the interaction behavior data within a set statistical period. These vectors include at least menu item click frequency, function usage duration, and operation sequence patterns. An unsupervised clustering algorithm is used to calculate the behavior feature vectors, dividing users into different behavior clusters. A dynamic behavior label is assigned to each behavior cluster, including at least high-frequency scheduling, data browsing, and transaction-driven labels. The unit analyzes the timestamp information in the interaction behavior data to identify user function usage patterns during weekdays and holidays, and peak and off-peak electricity consumption periods. The identified time patterns are used as a correction factor to optimize the classification results of the dynamic behavior labels and / or to optimize the weight allocation of the interface component preference weight vector. The preference model construction unit is used to assign a set of interface component preference weight vectors to each type of dynamic behavior label. The weight vectors quantify the degree of preference of users of this type for different functional modules, data panels and operation controls. The preference weight vectors are associated and mapped with the corresponding dynamic behavior labels to construct a preliminary user interface preference model. The profile encapsulation unit is used to integrate the dynamic behavior tags and the corresponding preliminary user interface preference model with the predefined static business role information as the base layer, and encapsulate them together into a unified user profile data entity that can be directly called by the dynamic layout engine, thus forming a unified multi-level user profile. As a further limitation of the technical solution of the present invention, the dynamic layout engine module includes: The priority calculation unit is used to calculate the display priority of each menu item and functional component based on the multi-level user profile and a preset algorithm. The template matching unit is used to automatically match the most suitable interface layout template from the preset layout template library based on the multi-level user profile. The interface optimization unit is used to perform differentiated display and hiding control and arrangement optimization of functional components in the interface according to the display priority. A multi-level configuration collaboration unit is used to execute a multi-level configuration collaboration mechanism and process user manual fine-tuning commands. The multi-level configuration collaboration mechanism allows users to manually fine-tune the personalized layout automatically generated by the system, and the user's manual configuration has the highest priority and is recorded as feedback data in the user profile for optimizing subsequent automatic layout generation.

[0026] As a further limitation of the technical solution of the present invention, the closed-loop feedback module includes: The feedback behavior collection unit is used to collect users' subsequent interaction behaviors with the personalized front-end layout; The decision evaluation unit is used to compare subsequent interactive behaviors with the user profile and layout decisions used to generate the personalized front-end layout, and to evaluate the effectiveness of the layout decisions. The model and algorithm update unit is used to dynamically adjust the preference weight vector of relevant functional components in the user interface preference model based on the evaluation results; and / or, correct the function usage frequency weight, function usage duration weight, and business role weight in the calculation formula.

[0027] As can be seen from the above technical solutions, this application has the following advantages: it constructs a complete technical closed loop from data collection to profile building, layout generation, and feedback optimization. It achieves deep integration of static business roles and dynamic behavioral data in the virtual power plant front-end layout and introduces a continuous self-optimization mechanism. It solves the problems of rigid interfaces, low operational efficiency, and lack of intelligent perception and evolutionary capabilities in existing systems, realizing a truly personalized and adaptive interface, and improving the efficiency and satisfaction of users with different professional roles. Attached Figure Description

[0028] To more clearly illustrate the technical solution of this application, the accompanying drawings used in the description will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0029] Figure 1 This is a flowchart illustrating the method provided in an embodiment of the present invention.

[0030] Figure 2 A block diagram of a system provided in an embodiment of the present invention. Detailed Implementation

[0031] To make the purpose, features, and advantages of this application more apparent and understandable, specific embodiments and accompanying drawings will be used to clearly and completely describe the technical solution protected by this application. Obviously, the embodiments described below are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0032] Unless otherwise defined, all technical and scientific terms used in this application have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. The terminology used in this application and in the specification of this invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.

[0033] like Figure 1 As shown, this embodiment of the invention provides a method for dynamic optimization of the front-end layout of a virtual power plant based on user behavior, including the following steps: S1. Collect user interaction data in the virtual power plant management system; the interaction data includes at least menu item click events, function module access and exit events, and interface jump events, wherein each data item records a corresponding user identifier and timestamp; this step specifically includes: S11. By embedding data acquisition probes into the front-end interface components of the virtual power plant management system, user clicks, browsing duration, and page jump events are captured in real time. In one specific embodiment of the present invention, the data acquisition probe is integrated into the front-end visualization framework of the virtual power plant management system in the form of a JavaScript code package. This probe listens for user interaction events with all interface components, for example: Click events: Listen for the onClick event of interactive elements such as menu items, buttons, and charts.

[0034] Browsing duration: The effective dwell time of a user within a single functional page or module is calculated by listening to the page's onLoad and onBeforeUnload events, or by listening to the visibilitychange API.

[0035] Page navigation: Listen for changes in the front-end route (such as the afterEach hook in Vue Router) to capture all interface switching behaviors.

[0036] The captured raw event data is immediately encapsulated into a data packet containing the event type, trigger element ID, current timestamp, and user session ID.

[0037] S12. Convert the captured events into structured behavior logs, which include at least user ID, timestamp, operation object, and operation type; The front-end probe captures data packets and sends them to the log collection server in real time via HTTP requests or WebSocket connections. A server-side log processing service (e.g., based on Logstash or a custom Node.js service) receives this data and standardizes it, transforming it into structured behavioral logs in a uniform JSON format.

[0038] S13. Based on the behavior log, sessions are divided according to user ID and timestamp, and a business rule-based cleaning algorithm is used to filter out meaningless erroneous operation events and heartbeat keep-alive events to construct a user operation sequence that represents a complete operation task.

[0039] This step is performed by a dedicated data preprocessing service. This service first groups the data by userID, and then sorts the data for each user by timestamp.

[0040] Session segmentation: A classic method based on timeout thresholds is used. If the time difference between two consecutive log entries exceeds 30 minutes, the user is considered to have started a new session. Each session represents a complete login usage cycle for the user.

[0041] Data cleaning: Logs within a session are filtered using a cleaning algorithm based on business rules. Rules include: Filtering out consecutive click events with extremely short durations (such as less than 300 milliseconds) is generally considered a mistake.

[0042] Identify and filter out heartbeat requests that are automatically initiated by the system to maintain the connection.

[0043] Filter out user behavior that involves entering and exiting the same page within a very short period of time (e.g., within 3 seconds), as this is usually considered navigation exploration rather than a valid task.

[0044] After cleaning, the meaningful sequence of events retained within a session is constructed as a user action sequence. This sequence clearly represents the series of actions performed by the user to complete a specific task, providing high-quality data input for subsequent behavior sequence analysis.

[0045] S2. Based on the collected interaction behavior data and combined with the user's predefined static business role information, dynamic behavior tags are generated through cluster analysis, and a user interface preference model is established to form a unified multi-level user profile that includes both static roles and dynamic behaviors; the predefined static business role information includes at least dispatchers, traders and energy owners; the system has a differentiated initial interface layout template and function permission set for each role.

[0046] It should be further noted that the steps in S2 include: S21. Extract user behavior feature vectors within a set statistical period from the interactive behavior data. The vectors include at least menu item click frequency, function usage duration, and operation sequence pattern. In this embodiment, the system sets a statistical period. The data processing service aggregates user interaction behavior data within this period and calculates the following features to construct a behavior feature vector: Menu item click frequency: Count the total number of times users click on each core menu item, and normalize the data to obtain a frequency vector that reflects the breadth and concentration of function usage.

[0047] Function usage time: Calculate the cumulative time users spend in each major functional module, and normalize it to form a time preference vector.

[0048] Operation sequence pattern: Using N-gram model or sequence embedding technology, the operation path frequently performed by users (such as "alarm list -> alarm details -> historical data comparison") is transformed into a fixed-length vector representation to capture their workflow habits.

[0049] Finally, the above vectors are concatenated to form a fixed-length behavioral feature vector for each user, which is then used as input for the clustering algorithm.

[0050] S22. Calculate the behavioral feature vector using an unsupervised clustering algorithm to divide users into different behavioral clusters; and assign a dynamic behavioral label to each behavioral cluster, the label including at least high-frequency scheduling type, data browsing type, and transaction-driven type; This step is performed by an analytics engine running on the server. This engine uses an unsupervised K-means clustering algorithm to cluster the behavioral feature vectors of all users. The optimal number of clusters is determined using the elbow rule or silhouette coefficient (K=3 in this embodiment). After clustering, combined with business expert knowledge, each behavioral cluster is assigned a dynamic behavioral label with business meaning. High-frequency scheduling type: This cluster of users is characterized by frequent clicks on functions such as real-time monitoring, alarm handling, and dispatch command issuance, with working hours far exceeding the average.

[0051] Data browsing type: Users in this cluster frequently access modules such as historical data reports, power generation forecast analysis, and market information, but rarely perform active operations.

[0052] Trading-driven: This group of users is characterized by their activity during electricity trading hours and their frequent use of functions such as quantity and price quotation, transaction result inquiry, and position management.

[0053] S23. For each type of dynamic behavior label, assign a set of interface component preference weight vectors, wherein the weight vectors quantify the degree of preference of the user for different functional modules, data panels and operation controls. The system maintains a global component-tag preference mapping library. Based on the dynamic behavior tags obtained in S22, a set of preset interface component preference weight vectors is assigned to each tag. This weight vector is an array, where each element corresponds to an interface function component (such as "real-time power curve graph", "alarm list card", "trading order panel"), and the element value (weight) quantifies the degree of preference of that type of user for that component.

[0054] For example, in the weight vector assigned to high-frequency scheduling labels, the weight values ​​of the real-time alarm list and the whole network power flow graph are preset to 0.95 (very high), while the weight of the monthly electricity bill report is preset to 0.1 (very low).

[0055] S24. Associate and map the preference weight vector with the corresponding dynamic behavior labels to construct a preliminary user interface preference model; The correspondence between the multiple dynamic behavior labels and preference weight vectors generated in S23 is organized into a key-value pair mapping table in memory or a database, or encapsulated into an independent model object. The core function of this model object is: input a dynamic behavior label, and it will output the corresponding complete interface component preference weight vector. This model is the preliminary user interface preference model.

[0056] S25. Using the predefined static business role information as the base layer, integrate the dynamic behavior tags and the corresponding preliminary user interface preference model, and encapsulate them together into a unified user profile data entity that can be directly called by the dynamic layout engine, thus forming a unified multi-level user profile.

[0057] The system creates a standardized user profile data entity (e.g., a JSON object or a database record). This entity has a clearly defined three-level structure: Baseline layer: Directly records the user's predefined static business role information (such as "role: dispatcher") and associates it with its initial interface layout template ID.

[0058] Classification layer: Records dynamic behavior labels obtained through S22 analysis (e.g., "Label: High-frequency scheduling type").

[0059] Preference layer: By querying the preliminary preference model constructed by S24, load the complete interface component preference weight vector corresponding to the dynamic behavior label.

[0060] This data entity, which contains a three-layer structure, is a unified multi-layered user profile, which is a complete digital description of a user's identity.

[0061] S26. Analyze the timestamp information in the interaction behavior data to identify the user's function usage patterns on weekdays and holidays, and during peak and off-peak electricity consumption periods; use the identified time patterns as a correction factor to optimize the classification results of dynamic behavior tags in S22, and / or to optimize the weight allocation of the interface component preference weight vector in S23.

[0062] The system adds a time pattern analyzer, whose execution cycle is synchronized with S21. This analyzer: Analyze the timestamps in users' historical behavior data to identify patterns. For example, it was found that a user frequently accessed the load forecasting function during 9:00-11:00 on weekdays (morning peak electricity consumption), and frequently used the transaction module during 14:00-16:00 (transaction hours).

[0063] If a user's behavior pattern during a specific time period is found to be significantly inconsistent with their current dynamic behavior label (e.g., a "data browsing" user exhibits strong trading behavior during a trading period), a "trading-driven" label component can be temporarily superimposed on them during that time period, or a re-clustering can be triggered.

[0064] Based on the baseline weight vector allocated in S23, the weights of specific functional components are dynamically increased according to the identified time patterns. For example, during the identified trading period, the weight of the order placement panel component for all users (regardless of their primary label) is temporarily increased by an offset (e.g., +0.2) to ensure that the interface layout can respond sensitively to changes in business rhythm.

[0065] S3. Based on multi-layered user profiles, perform the following operations using a dynamic layout engine to generate and output personalized front-end layouts: (a) Calculate the display priority of each menu item and functional component;

[0066] in, To display priority scores, Use frequency weights for functions Weighting based on feature usage time Assigning weights to business roles To normalize the click-through rate, To normalize usage time, The role-function relevance is dynamically adjusted based on the dynamic behavior tags in the user profile, including the weights for function usage frequency, function usage duration, and business role. The role-function relevance is obtained by querying a predefined role-function weight mapping table, which is established based on the business rules of the virtual power plant and the responsibilities and permissions of different roles. The weight values ​​in the mapping table are periodically and dynamically adjusted based on the historical average behavior data of the user group under the same role.

[0067] Normalized click-through rate (CTR) is used to eliminate the magnitude difference in the total number of clicks among different users, making the click frequencies of different users comparable.

[0068] Within a defined statistical period (e.g., one week), the normalized click-through rate (CTR) for a specific user is calculated using the following steps: The total number of clicks made by the user on all menu items and functional components in the system is recorded as follows: Statistics on the user's usage of specific functional components The number of clicks is recorded as .

[0069] Calculate the user's preference for a specific functional component Original click-through rate: .

[0070] To perform cross-user comparisons, for all users Normalization is performed, mapping it to the interval [0, 1]. The min-max normalization method is used:

[0071] For the statistical period, all users of this specific functional component raw click-through rate The maximum value.

[0072] For the statistical period, all users of this specific functional component raw click-through rate The minimum value.

[0073] This method allows users to access specific functional components. Normalized click-through rate This intuitively reflects the user's understanding of the function. Click preferences, and their relative position among all users.

[0074] Normalized usage time is designed to eliminate differences in total online time among different users and to fairly measure users' time investment preferences across different functions.

[0075] Similar to click-through rate, for a specific user and a specific functional component: The total effective session duration of this user within the statistical period is recorded as follows: .

[0076] Statistics on this user's usage of specific functional components The cumulative duration of stay is recorded as follows: .

[0077] Calculate the original proportion of usage time: .

[0078] Using all users' energy components within the statistical period The maximum and minimum values ​​of the original proportion of usage time are used to obtain the normalized usage time through cross-user comparison using the min-max normalization method. .

[0079] Role-function association measures the importance of a functional module to a business role.

[0080] Initial predefined: The system maintains a role-function association matrix. This matrix is ​​set by domain experts during system initialization, assigning a basic association degree to each pair (role, function). The value range is [0, 1].

[0081] For example: (Role = Dispatcher, Function = Real-time Load Forecasting) -> = 0.9; (Role = Dispatcher, Function = Electricity Trading Quote) -> = 0.2; Dynamic correction (dynamic part): The system periodically (e.g., monthly) analyzes the historical behavior data of all users under the same role and fine-tunes the basic correlation.

[0082] Calculate the average heatmap value of a certain function for all users under this role. The overall heat index of individual users is calculated by weighting normalized click-through rate and duration.

[0083] Correction formula:

[0084] in It is a mixing factor (0 < <1), used to control the weighting of business rules and group behavior data. For example, =0.7 indicates greater reliance on expert-defined basic rules, while making 30% adjustments based on group behavior.

[0085] (b) Automatically match the interface layout template that best suits the current user profile from the preset layout template library; specifically including: S31. Based on the predefined static business role information in the user profile, select a set of candidate templates that meet the role criteria from the template library; S32. Based on the interface component preference weight vector in the user profile, calculate the cosine similarity with the preset component layout of each template in the candidate template set. S33. Select the template with the highest cosine similarity to the interface component preference weight vector as the most suitable interface layout template.

[0086] (c) Based on the display priority, perform differentiated display control and arrangement optimization of functional components in the interface; S34. In the main work area of ​​the most suitable interface layout template, prioritize rendering the top N functional components with the highest display priority. S35: Aggregate the functional components with a priority ranking of Nth or lower into the secondary menu; S36. Within the same area, functional components are arranged in descending order according to their display priority scores.

[0087] After the S3 steps are executed, the system provides a multi-level configuration collaboration mechanism. This mechanism allows users to manually fine-tune the personalized layout automatically generated by the system. The user's manual configuration has the highest priority and is recorded as feedback data in the user profile to optimize subsequent automatic layout generation.

[0088] S4. Collect subsequent user interaction data on the personalized front-end layout and feed it back to S1 for updating the user profile and optimizing layout decisions. It should be noted that this step specifically includes: S41. Collect the user's subsequent interaction behavior with the personalized front-end layout. The subsequent interaction behavior includes at least the click rate of rearranged functional components, the access depth of functions in the sub-menu, and the user's manual adjustment of the layout. After rendering the personalized layout, the system immediately initiates a new round of front-end data collection, focusing on interactive behaviors that can verify the layout effect. These behaviors are encapsulated as feedback logs, whose core metrics include: (1) Click-through rate (CTR) of rearranged functional components: Click-through rate = Number of clicks on a specific component / Total number of impressions of that component The system records the number of times each component whose position is dynamically adjusted (such as being moved to the main workspace) is displayed and clicked in its new position.

[0089] (2) Access depth to functions within sub-menus: This counts the number of subsequent steps a user takes after clicking a submenu and accessing a hidden function. For example, if a user clicks "More" -> selects "Historical Data Report" -> clicks "Export," the access depth is counted as 3 steps.

[0090] The shallower the depth, the more difficult it is for users to find the function, and the greater the negative effects of this hidden decision may be.

[0091] (3) User-manual layout adjustment operation: The system captures user actions that directly intervene in the layout, such as dragging and dropping components to move them in / out of the main workspace, and fixing or unfixing components. It also records the target component, operation type, and timestamp of the operation.

[0092] S42. Compare subsequent interactive behaviors with the user profile and layout decisions used to generate the personalized front-end layout, and evaluate the effectiveness of the layout decisions, i.e., evaluate the effectiveness of the behavior; specifically including: If the click-through rate of a high-priority feature component that is highlighted is lower than the expected threshold during the display period, it is determined that there is a deviation in the priority calculation of that feature component in this layout decision. High-priority components have a low click-through rate (misjudged as high priority): For a component that is determined to be high priority by the S3 engine and placed in the main workspace, the system sets an expected click-through rate threshold (e.g., 5%). If the actual click-through rate of the component is lower than the expected click-through rate threshold within an evaluation period (set to 24 hours in this embodiment), a misjudgment of high priority is triggered.

[0093] If a user frequently moves a hidden functional component to the main workspace manually, it is determined that the layout decision has a deviation in controlling the visibility of that functional component.

[0094] Users frequently manually restore hidden features (misjudging low priority): For a component hidden in a secondary menu by the S3 engine, the system records the number of times the user manually moves it back to the main workspace. A manual restoration frequency threshold is set (e.g., if the same user performs this action twice within 3 days). If the frequency exceeds the threshold, a low-priority misjudgment is triggered.

[0095] S43. Based on the results of the behavioral effectiveness evaluation, dynamically adjust the preference weight vectors of relevant functional components in the user interface preference model; and / or modify the weight parameters in the formula used to calculate the display priority score. This step involves incremental updates to the model and parameters, specifically including: (1) Dynamically adjust the weight vector in the user interface preference model Directly correct the interface component preference weight vector assigned to dynamic behavior labels in S23.

[0096] Adjust the formula: For components that are mistakenly identified as having high priority: reduce their weight.

[0097]

[0098] in, The attenuation coefficient is set to 0.2 in this embodiment of the invention, which means that the weight is reduced by 20%.

[0099] For components that are mistakenly classified as low priority (frequent manual recovery): increase their weight.

[0100]

[0101] in, To enhance the coefficient, it is set to 0.3 in this embodiment of the invention, which means that the weight is increased by 30%.

[0102] (2) Correct the weight parameter in the formula for calculating the priority score. The priority calculation formula for S3(a) is revised. The weight parameters include: function usage frequency weight. Function usage time weight Business role weight .

[0103] Fine-tuning is performed using the gradient descent approach. First, the loss of the current decision is calculated.

[0104] Loss function definition: Loss = (Number of incorrectly predicted components) / (Total number of evaluated components) Based on loss, by learning rate The weight parameters are updated to a value of 0.05. The update direction is to reduce the overall loss. The following rules are adopted: If errors caused by misjudgment of click-through rate are the dominant factor, then appropriately reduce... and correspondingly improve and .

[0105]

[0106]

[0107]

[0108] If errors caused by manual recovery misjudgments dominate, it indicates that the system relies too heavily on historical behavior. , ), while ignoring the character's rigid requirements ( At this point, the increase should be made. .

[0109]

[0110] Once all adjustments are complete, the new weight vectors and formula parameters will take effect immediately and be used in the decision-making process for generating layouts for the user in the next iteration, thereby enabling the system to evolve itself.

[0111] like Figure 2 As shown, this embodiment of the invention also provides a user behavior-driven dynamic optimization system for the front-end layout of a virtual power plant, used to implement the methods described in the above embodiments, including: The behavior data acquisition module is used to collect user interaction behavior data in the virtual power plant management system. The interaction behavior data includes at least menu item click events, function module access and exit events, and interface jump events, and each data record has a corresponding user identifier and timestamp. The user profile building module is used to generate dynamic behavior tags through cluster analysis based on the collected interaction behavior data and combined with the user's predefined static business role information, and to establish a user interface preference model to form a unified multi-level user profile that includes both static roles and dynamic behaviors. The dynamic layout engine module is used to calculate the display priority of each menu item and functional component; automatically match the interface layout template that best suits the current user profile from the preset layout template library; and perform differentiated display and hiding control and arrangement optimization of functional components in the interface according to the display priority to generate and output a personalized front-end layout. The closed-loop feedback module is used to collect subsequent interaction data of the user with the personalized front-end layout and feed it back to the behavior data collection module for updating the user profile and optimizing layout decisions.

[0112] In some embodiments, the behavior data acquisition module includes: The front-end probe unit is used to capture user clicks, browsing duration, and page jump events in real time by embedding data acquisition probes into the front-end interface components of the virtual power plant management system. The log structuring unit is used to transform captured events into structured behavior logs, which at least include user ID, timestamp, operation object, and operation type. The session construction and cleaning unit is used to divide sessions according to user ID and timestamp based on the behavior log, and to filter out meaningless erroneous operation events and heartbeat keep-alive events using a business rule-based cleaning algorithm, so as to construct a user operation sequence that represents a complete operation task.

[0113] In some embodiments, the user profile building module includes: The role management unit is used to store and manage the predefined static business role information and its corresponding initial interface layout template and function permission set; The behavior analysis unit is used to extract user behavior feature vectors from the interaction behavior data within a set statistical period. These vectors include at least menu item click frequency, function usage duration, and operation sequence patterns. An unsupervised clustering algorithm is used to calculate the behavior feature vectors, dividing users into different behavior clusters. A dynamic behavior label is assigned to each behavior cluster, including at least high-frequency scheduling, data browsing, and transaction-driven labels. The unit analyzes the timestamp information in the interaction behavior data to identify user function usage patterns during weekdays and holidays, and peak and off-peak electricity consumption periods. The identified time patterns are used as a correction factor to optimize the classification results of the dynamic behavior labels and / or to optimize the weight allocation of the interface component preference weight vector. The preference model construction unit is used to assign a set of interface component preference weight vectors to each type of dynamic behavior label. The weight vectors quantify the degree of preference of users of this type for different functional modules, data panels and operation controls. The preference weight vectors are associated and mapped with the corresponding dynamic behavior labels to construct a preliminary user interface preference model. The profile encapsulation unit is used to integrate the dynamic behavior tags and the corresponding preliminary user interface preference model with the predefined static business role information as the base layer, and encapsulate them together into a unified user profile data entity that can be directly called by the dynamic layout engine, thus forming a unified multi-level user profile. In some embodiments, the dynamic layout engine module includes: The priority calculation unit is used to calculate the display priority of each menu item and functional component based on the multi-level user profile and a preset algorithm. The template matching unit is used to automatically match the most suitable interface layout template from the preset layout template library based on the multi-level user profile. The interface optimization unit is used to perform differentiated display and hiding control and arrangement optimization of functional components in the interface according to the display priority. A multi-level configuration collaboration unit is used to execute a multi-level configuration collaboration mechanism and process user manual fine-tuning commands. The multi-level configuration collaboration mechanism allows users to manually fine-tune the personalized layout automatically generated by the system, and the user's manual configuration has the highest priority and is recorded as feedback data in the user profile for optimizing subsequent automatic layout generation.

[0114] In some embodiments, the closed-loop feedback module includes: The feedback behavior collection unit is used to collect users' subsequent interaction behaviors with the personalized front-end layout; The decision evaluation unit is used to compare subsequent interactive behaviors with the user profile and layout decisions used to generate the personalized front-end layout, and to evaluate the effectiveness of the layout decisions. The model and algorithm update unit is used to dynamically adjust the preference weight vector of relevant functional components in the user interface preference model based on the evaluation results; and / or, correct the function usage frequency weight, function usage duration weight, and business role weight in the calculation formula.

[0115] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for dynamic optimization of front-end layout of a virtual power plant based on user behavior driving, characterized in that, The method comprises the following steps: S1, collecting user interaction behavior data in a virtual power plant management system; the interaction behavior data at least includes menu item click events, function module access and exit events, and interface jump events, wherein each data records a corresponding user identification and a timestamp; S2, based on the collected interaction behavior data, combining with the user's pre-defined static business role information, generating a dynamic behavior label through clustering analysis, and establishing a user interface preference model to form a unified multi-level user portrait containing static roles and dynamic behaviors; S3, based on the multi-level user portrait, the dynamic layout engine performs the following operations to generate and output personalized front-end layout: (a) calculating the display priority of each menu item and function component; (b) automatically matching the interface layout template that best fits the current user portrait from the preset layout template library; (c) according to the display priority, differentiating the display and control of the function components in the interface and optimizing the arrangement; S4, collecting the subsequent interaction data of the user to the personalized front-end layout, and feeding it back to S1 for updating the user portrait and optimizing the layout decision.

2. The method for dynamic optimization of virtual power plant front-end layout driven by user behavior according to claim 1, characterized in that, In S1 step, it includes: S11, by implanting data collection probes in the front-end interface components of the virtual power plant management system, real-time capture of user clicks, browsing time and page jump events; S12, convert the captured events into structured behavior logs, which at least include user ID, timestamp, operation object and operation type; S13, based on the behavior log, dividing the session by user ID and timestamp, and filtering out meaningless false operation events and heartbeat events using a business rule-based cleaning algorithm to build a user operation sequence representing a complete operation task.

3. The method of claim 2, wherein, In S2, the pre-defined static business role information at least includes dispatchers, traders and energy owners; the system presets different initial interface layout templates and function permission sets for each role.

4. The method of claim 3, wherein, The steps of S2 include: S21, extracting the behavior feature vector of the user within a set statistical period from the interaction behavior data, which at least includes menu item click frequency, function use time and operation sequence mode; S22, using an unsupervised clustering algorithm to calculate the behavior feature vector, dividing the user into different behavior clusters; and assigning a dynamic behavior label to each behavior cluster, which at least includes high-frequency scheduling type, data browsing type and transaction dominant type; S23, for each type of dynamic behavior label, a set of interface component preference weight vectors are assigned, which quantifies the preference degree of the user to different function modules, data panels and operation controls; S24, the preference weight vector is associated with the corresponding dynamic behavior label to construct a preliminary user interface preference model; S25, taking the pre-defined static business role information as the base layer, integrating the dynamic behavior label and the corresponding preliminary user interface preference model to jointly encapsulate a unified multi-level user portrait data entity that can be directly called by the dynamic layout engine, that is, a unified multi-level user portrait is formed. S26, analyze the timestamp information in the interaction behavior data, identify the user's function use mode in workdays and holidays, peak and off-peak power consumption periods; the identified time mode is used as a correction factor to optimize the classification result of the dynamic behavior label in S22, and / or to optimize the weight distribution of the interface component preference weight vector in S23.

5. The method of claim 4, wherein, In step (a) of S3, the display priority of each menu item and function component is calculated, which is realized by the following formula: wherein, is a function usage frequency weight, is a function usage time length weight, is a function usage time length weight, is a business role weight, is a normalized click rate, is a normalized usage time length, is a role-function correlation degree, the function usage frequency weight, the function usage time length weight, and the business role weight are dynamically adjusted according to a dynamic behavior label in the user portrait; the role-function correlation degree is obtained by querying a predefined role-function weight mapping table, the role-function weight mapping table is established based on business rules of the virtual power plant and responsibilities and permissions of different roles, and a weight value in the mapping table is periodically and dynamically adjusted according to historical average behavior data of a user group under the same role.

6. The method of claim 5, wherein, In step (b) of S3, the most suitable interface layout template is automatically matched from the preset layout template library, which specifically includes: S31, based on the pre-defined static business role information in the user portrait, filter out a candidate template set that meets the role basis from the template library; S32, based on the interface component preference weight vector in the user portrait, calculate the cosine similarity of the preset component layout of each template in the candidate template set; S33, select the template with the highest cosine similarity of the interface component preference weight vector as the most suitable interface layout template.

7. The method of claim 6, wherein, In step (c) of S3, according to the display priority, the function components in the interface are controlled and arranged, which specifically includes: S34, in the main work area of the most suitable interface layout template, the first N function components with the highest display priority are preferentially rendered and displayed; S35, the function components ranked after N in the display priority are aggregated into a secondary menu; S36, in the same area, the function components are arranged in descending order according to the display priority score.

8. The method of claim 7, wherein, After the execution of the steps of S3, the system provides a multi-level configuration cooperation mechanism, which allows the user to manually fine-tune the personalized layout generated by the system, and the user's manual configuration has the highest priority and is recorded in the user portrait as feedback data for optimizing subsequent automatic layout generation.

9. The method of claim 8, wherein, The steps of S4 include: S41, collect the subsequent interaction behavior of the user on the personalized front-end layout, which at least includes the click rate of the rearranged function components, the access depth of the functions in the secondary menu, and the user's manual adjustment of the layout; S42, compare the subsequent interaction behavior with the user portrait and layout decision relied on when generating the personalized front-end layout to evaluate the effectiveness of the layout decision; S43, based on the evaluation result, dynamically adjust the preference weight vector of the related function components in the user interface preference model; and / or, correct the function use frequency weight, function use time weight and business role weight in the calculation formula of step (a) of S3.

10. A user behavior driven virtual power plant front-end layout dynamic optimization system for implementing the method of any one of claims 1 to 9, characterized in that, It includes: A behavior data collection module is configured to collect interaction behavior data of a user in a virtual power plant management system; the interaction behavior data at least includes click events of menu items, access and exit events of function modules, and interface jump events, wherein each data records a corresponding user identifier and timestamp; The user portrait construction module is configured to generate a dynamic behavior label through cluster analysis and establish a user interface preference model based on the collected interaction behavior data and in combination with predefined static business role information of the user, so as to form a unified multi-level user portrait containing both static roles and dynamic behaviors. The dynamic layout engine module is configured to calculate display priorities of menu items and function components, automatically match an interface layout template most suitable for the current user portrait from a preset layout template library, and perform differentiated display control and arrangement optimization on the function components in the interface according to the display priorities, so as to generate and output a personalized front-end layout. The closed-loop feedback module is configured to collect subsequent interaction data of the user on the personalized front-end layout and feed the data back to the behavior data collection module, so as to update the user portrait and optimize the layout decision.

Images