Intelligent menu management method and device, computer equipment and storage medium

By counting user historical operation data, the menu pages are divided, and the commonly used pages are loaded first and the very useful pages are released, which solves the problem that the menu page management method in the existing technology cannot be optimized according to user habits, improves the interface response speed and resource utilization rate, and improves the User experience and system performance.

CN119025210APending Publication Date: 2024-11-26SHENZHEN ZHANYIN TECH CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202411211538.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-30
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

The menu page management method of existing electronic devices cannot be optimized and adjusted according to the user's actual usage habits, resulting in slow interface response speed and low system resource utilization, especially on devices with resource constraints.

Method used

By obtaining user history operation menu page information, count the frequency of use of menu pages, divide it into commonly used and extremely useful pages, prioritize loading of commonly used pages and release of extremely useful pages when switching backends, to improve interface response speed and resource utilization.

Benefits of technology

It enables users to access required content more quickly, reduces waiting time, optimizes interface switching fluency, improves user experience and system performance, and avoids lag caused by excessive loading of infrequently used pages.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119025210A_ABST
    Figure CN119025210A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of user interface optimization of electronic equipment. The invention relates to an intelligent menu management method and device, computer equipment and a storage medium, and the method comprises the steps: obtaining user historical operation menu page information, carrying out the statistics of menu page use frequency according to the user historical operation menu page information, and carrying out the management of a menu through the menu page use frequency. A menu page is divided into a common menu page and a non-common menu page, when the menu page is switched, the common menu page is loaded preferentially, and when the menu page is switched to a background, the non-common menu page is released. The method has the effect of improving the user interface response speed and the resource utilization rate.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of electronic device user interface optimization, and in particular to an intelligent menu management method, device, computer equipment and storage medium. Background Art

[0002] With the popularity of electronic devices and the continuous increase in their functions, the friendliness and response speed of the user interface have become important indicators for measuring device performance. The menu page is the main entrance for users to interact with the device, and the quality of its management directly affects the user experience.

[0003] At present, the menu page management of most electronic devices adopts a static or preset loading method, which cannot be optimized and adjusted according to the actual usage habits of users. As a result, when switching menu pages, users often have to wait for a long time for the loading process, especially on resource-constrained devices, this waiting is more obvious. At the same time, unnecessary menu pages occupy system resources for a long time, which not only reduces the overall performance of the system, but also may cause other running applications to be affected. Therefore, how to intelligently manage menu pages according to user usage habits and improve interface response speed and system resource utilization has become a problem that needs to be solved urgently. Summary of the invention

[0004] In order to improve the user interface response speed and resource utilization, the present application provides an intelligent menu management method, apparatus, computer equipment and storage medium.

[0005] The above-mentioned invention objective of the present application is achieved through the following technical solutions: An intelligent menu management method, the intelligent menu management method comprising: Get the user's historical operation menu page information; According to the menu page information of the user's historical operation, counting the usage frequency of the menu pages, and dividing the menu pages into frequently used menu pages and infrequently used menu pages according to the usage frequency of the menu pages; When the menu page is switched, the frequently used menu page is loaded first, and the uncommon menu page is released when the menu page is switched to the background.

[0006] By adopting the above technical solution, by counting the user's historical operation data and dividing the menu pages into frequently used and uncommonly used pages, frequently used pages can be loaded first when the user switches menus. This allows users to access the required content more quickly and reduce waiting time. When the menu page is switched to the background, uncommonly used menu pages are released, unnecessary resource usage is reduced, and the device's memory and processing power are effectively utilized. Prioritizing the loading of frequently used pages can make the interface switching smoother, improve the user's overall experience, and avoid freezes caused by loading too many uncommonly used pages.

[0007] In a preferred example, the present application may be further configured as follows: the acquisition of user history operation menu page information further includes: Initialize the menu page.

[0008] By adopting the above technical solution, by initializing the menu page after obtaining the user's historical operation menu page information, the availability and stability of the menu page in subsequent operations can be ensured, thereby improving the user's smooth experience in interface operations.

[0009] In a preferred example, the present application may be further configured as follows: counting the usage frequency of menu pages according to the user's historical operation menu page information, and dividing the menu pages into commonly used menu pages and uncommon menu pages according to the menu page usage frequency, including: Obtaining the menu page access frequency and the menu page stay time from the user's historical operation menu page information; The menu page usage frequency is calculated based on the menu page access frequency, the menu page stay time and a preset initial usage frequency value; The menu pages are divided into the frequently used menu pages and the infrequently used menu pages according to the usage frequency of the menu pages.

[0010] By adopting the above technical solution, by obtaining the menu page access frequency and the menu page stay time from the user's historical operation menu page information, and calculating the menu page usage frequency based on these data, it is possible to more accurately reflect the actual usage of each menu page, thereby further optimizing the division of frequently used menu pages and infrequently used menu pages and improving resource utilization.

[0011] In a preferred example, the present application may be further configured as follows: the menu page usage frequency is calculated based on the menu page access frequency, the menu page stay time and the preset initial usage frequency value, including: The usage frequency of the menu page is determined by the following formula: Ui=S i ×W i , where U i refers to the frequency of use of the menu page, W i refers to the access frequency weight, S i It refers to the weight of the length of stay.

[0012] By adopting the above technical solution and introducing the calculation formula of access frequency weight and stay time weight, it is possible to more reasonably reflect the actual usage of menu pages by users, ensure that frequently used pages are loaded first, and thus improve the response speed of the user interface and the utilization rate of resources.

[0013] In a preferred example, the present application can be further configured as follows: The menu page usage frequency is determined by the following formula: Ui=S i ×W i , where U i refers to the frequency of use of the menu page, W i refers to the access frequency weight, S i Refers to the length of stay weight, including: Among them, W i refers to the access frequency weight, F i refers to the number of visits, P0 refers to the preset initial frequency of use, α and β are weight coefficients, and α+β=1; Among them, S i Refers to the length of stay weight, T i refers to the length of stay, P0 refers to the preset initial usage frequency value, γ and δ are weight coefficients, and γ+δ=1.

[0014] By adopting the above technical solution, formulas are used to calculate the access frequency weight and the stay time weight respectively, so that the usage frequency of menu pages can be distinguished in detail. This method not only takes into account the number of times the menu page is visited, but also takes into account the time the user stays on the page, thereby improving the calculation accuracy of the menu page usage frequency and making the division of menu pages more in line with the user's actual usage habits.

[0015] In a preferred example, the present application can be further configured as follows: when the menu page is switched, the commonly used menu page is loaded first, and when the menu page is switched to the background, the uncommon menu page is released, including: Detecting the usage frequency of the menu page, and when the menu page is the frequently used menu page, directly loading the frequently used menu page; When the menu page is the uncommon menu page and memory resources are insufficient, delaying loading of the uncommon menu page; When the menu page is switched to the background, the frequently used menu page is retained and the uncommonly used menu page is released.

[0016] By adopting the above technical solution, commonly used menu pages are loaded first when switching menu pages, and uncommonly used menu pages are released when the menu page is switched to the background. This can ensure the rational use of system memory resources and the rapid response of user commonly used functions, thereby improving user experience and system performance.

[0017] In a preferred example, the present application may be further configured as follows: when the menu page is the uncommon menu page and memory resources are insufficient, delaying loading of the uncommon menu page includes: Determining the memory resource state, and when it is detected that the memory resource is insufficient, marking the uncommonly used menu page as being in a to-be-loaded state; When the memory resources are restored to an available state, the loading condition of the infrequently used menu page is re-evaluated, and when the memory resources are sufficient, the infrequently used menu page is loaded.

[0018] By adopting the above technical solution, the loading of uncommon menu pages is delayed when memory resources are insufficient, and the loading conditions are re-evaluated after the memory resources are restored. The loading strategy of the menu pages can be dynamically adjusted to ensure that the system can still run stably under limited resources, thereby improving the system's fault tolerance and stability.

[0019] The second object of the invention is achieved by the following technical solutions: An intelligent menu management device, the intelligent menu management device comprising: Information acquisition module, used to obtain user history operation menu page information; A menu page division module is used to count the usage frequency of menu pages according to the menu page history operation information of the user, and divide the menu pages into commonly used menu pages and uncommon menu pages according to the usage frequency of the menu pages; The page loading selection module is used to preferentially load the commonly used menu page when the menu page is switched, and release the uncommonly used menu page when the menu page is switched to the background.

[0020] By adopting the above technical solution, by counting the user's historical operation data and dividing the menu pages into frequently used and uncommonly used pages, frequently used pages can be loaded first when the user switches menus. This allows users to access the required content more quickly and reduce waiting time. When the menu page is switched to the background, uncommonly used menu pages are released, unnecessary resource usage is reduced, and the device's memory and processing power are effectively utilized. Prioritizing the loading of frequently used pages can make the interface switching smoother, improve the user's overall experience, and avoid freezes caused by loading too many uncommonly used pages.

[0021] The third objective of the present application is achieved through the following technical solutions: A computer device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above-mentioned intelligent menu management method when executing the computer program.

[0022] The fourth objective of the present application is achieved through the following technical solutions: A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above-mentioned intelligent menu management method are implemented.

[0023] In summary, the present application includes at least one of the following beneficial technical effects: 1. By counting the user's historical operation data and dividing the menu pages into frequently used and uncommonly used pages, frequently used pages can be loaded first when the user switches menus. This allows users to access the required content more quickly and reduce waiting time. When the menu page is switched to the background, uncommonly used menu pages are released to reduce unnecessary resource usage and effectively utilize the device's memory and processing power. Prioritizing the loading of frequently used pages can make the interface switching smoother, improve the user's overall experience, and avoid freezes caused by loading too many uncommonly used pages; 2. The frequency of use of menu pages is calculated through a formula, including the weight of access frequency and the weight of stay time, which can more scientifically determine the frequency of use of menu pages, making the loading strategy of menu pages more intelligent, thereby improving the flexibility and efficiency of the system in processing different types of menu pages; 3. Prioritize loading frequently used menu pages when switching menu pages, and release uncommon menu pages when the menu page switches to the background. This can ensure the rational use of system memory resources and the rapid response of user-common functions, thereby improving user experience and system performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 is a flow chart of an intelligent menu management method in one embodiment of the present application; Figure 2 This is a flowchart of the implementation of the intelligent menu management method after step S10 in one embodiment of the present application; Figure 3 This is a flowchart of the implementation of step S20 of the intelligent menu management method in one embodiment of the present application; Figure 4 This is a flowchart of the implementation of step S202 of the intelligent menu management method in one embodiment of the present application; Figure 5 This is a flowchart of the implementation of step S2021 of the intelligent menu management method in one embodiment of the present application; Figure 6 This is a flowchart of the implementation of step S30 of the intelligent menu management method in one embodiment of the present application; Figure 7 This is a flowchart of the implementation of step S302 of the intelligent menu management method in one embodiment of the present application; Figure 8This is a principle block diagram of an intelligent menu management device in one embodiment of the present application; Fig. 9 It is a schematic diagram of a device in an embodiment of the present application. DETAILED DESCRIPTION

[0025] The present application is further described in detail below in conjunction with the accompanying drawings.

[0026] In one embodiment, if Figure 1 As shown, the present application discloses an intelligent menu management method, which specifically includes the following steps: S10: Obtaining user history operation menu page information.

[0027] In this embodiment, the user's historical operation menu page information refers to the information generated when the user operates each menu page on the device, including but not limited to the number of menu page visits, visit duration, visit time period, and the type of operation performed by the user on each page, etc. Through analysis, the user's usage habits and preferences can be obtained.

[0028] Specifically, each time a user operates a menu page, the page's visit frequency and duration are automatically recorded, as well as other interactive information about the page, such as buttons clicked by the user, settings adjusted, etc. Whenever the user returns to the main interface or closes the app, the system saves this operation information and performs data integration in the background so that this historical operation information can be quickly read and analyzed when needed.

[0029] Furthermore, the system refers to a comprehensive technical architecture that integrates hardware resources, operations, applications, and algorithms to work together to achieve intelligent management and resource optimization of menu pages.

[0030] S20: Counting the usage frequency of the menu pages according to the historical operation information of the user, and dividing the menu pages into frequently used menu pages and infrequently used menu pages according to the usage frequency of the menu pages.

[0031] In this embodiment, the frequently used menu page refers to a menu page that users visit frequently and stay on for a long time. The infrequently used menu page refers to a page that users visit less frequently and stay on for a short time.

[0032] Specifically, the number of visits and the length of stay on each page are extracted from the user's historical operation menu page information. Then, these data are weighted based on the preset weight value. Weighting means that the system assigns a weight value to the number of visits and the length of stay on each page, indicating their importance to the frequency of page usage. The weight value of the visit frequency (Wi) is used to measure the impact of the number of page visits on the frequency of use, while the weight value of the length of stay (S i) is used to evaluate the impact of page dwell time on usage frequency. The system multiplies the page's access frequency by the access frequency weight, and multiplies the page's dwell time by the dwell time weight to get the weighted value. The system adds the weighted access frequency value and dwell time value, and then adds a preset initial usage frequency value (P0) to get the final usage frequency value (U) of the page. i ). The initial usage frequency value is a basic value used to provide an initial frequency reference for new pages when there is no user operation data. Finally, the system will sort the usage frequency values ​​of all pages and set a page threshold. Pages exceeding this threshold will be classified as frequently used menu pages, while pages below this threshold will be classified as uncommon menu pages.

[0033] Furthermore, the weighted calculation process is to comprehensively consider the impact of different factors on the frequency of page usage and ensure the accuracy of classification. For example, a page with a large number of visits but a short stay time may be regarded as a frequently used page, while a page with a small number of visits but a long stay time may also be classified as a frequently used page. Therefore, through weighted calculation, the system can balance these factors and obtain classification results that are more in line with the actual operating habits of users. The page threshold refers to a critical value of the usage frequency set when classifying menu pages, which is used to divide menu pages into frequently used pages and infrequently used pages. After calculating the usage frequency of each page, the system will compare these frequency values ​​with the preset page threshold. Pages exceeding this threshold will be classified as frequently used menu pages, which means that these pages are more frequently used by users; and pages below this threshold will be classified as infrequently used menu pages, which means that these pages are less frequently used by users.

[0034] S30: When switching menu pages, frequently used menu pages are loaded first, and uncommon menu pages are released when the menu page switches to the background.

[0035] Specifically, when a user requests to switch menu pages, the system will first detect whether the requested page belongs to a frequently used menu page. If it is a frequently used menu page, the system will give priority to loading the page directly from the memory to ensure a quick response to the user's operation request and reduce the waiting time for page loading. For uncommon menu pages, if the memory resources are sufficient, the system will gradually load the page in the background for subsequent use, but if the memory resources are insufficient, the system will temporarily delay loading the page and perform the loading operation after the memory resources are restored. When the user no longer uses a page and the page is switched to the background, the system will decide whether to release the memory resources of the page based on the frequency of use of the page. If it is an uncommon menu page, the system will give priority to releasing the memory it occupies to provide more available resources for other operations. At the same time, frequently used menu pages will be retained in memory so that users can load them quickly when they visit again.

[0036] In one embodiment, if Figure 2 As shown, after step S10, the user history operation menu page information is obtained, and then the following steps are further included: S11: Initialize the menu page.

[0037] Specifically, all basic menu page data, including page layout, buttons, text, icons and other elements, are loaded and stored in memory for quick access. At the same time, the system will preload frequently used pages based on the user's historical operation data to reduce the loading time when the user visits.

[0038] In one embodiment, if Figure 3 As shown, in step S20, the menu page usage frequency is counted according to the user's historical operation menu page information, and the menu pages are divided into commonly used menu pages and uncommon menu pages according to the menu page usage frequency, including: S201: Obtaining the menu page access frequency and the menu page stay time from the user's historical operation menu page information.

[0039] In this embodiment, the menu page access frequency refers to the total number of times a user visits a specific menu page within a period of time, reflecting the user's use frequency of the page. The menu page stay time refers to the total time a user stays on the page, reflecting the user's attention to the page content or operation needs.

[0040] Specifically, when a user opens or switches to a menu page, the access frequency is recorded. At the same time, the system starts counting. When the user leaves the page or switches to another page, the count ends and the total time the user stays on the page is recorded. These data will be continuously accumulated and stored in the user's historical operation records, forming a dynamically updated database for subsequent statistics and analysis.

[0041] Furthermore, a dynamically updated database refers to a database that records and updates user operation data at any time. The database is automatically updated with each operation of the user, and stores the user's access records and interaction information on different menu pages. This dynamic update feature means that the data in the dynamically updated database changes in real time and can accurately reflect the user's current usage habits. Every time a user visits, stays on, or performs other operations on a menu page, these operation data will be immediately recorded in the dynamically updated database.

[0042] S202: Calculate the menu page usage frequency based on the menu page access frequency, the menu page stay time and a preset initial usage frequency value.

[0043] In this embodiment, the preset initial usage frequency value refers to the initial frequency value assigned to each menu page by default when there is no user operation history data, so as to ensure that all pages have a basic usage frequency when the system is first run.

[0044] Specifically, a weighted formula is used to combine the access frequency and dwell time of each page with the preset initial usage frequency value to calculate the final usage frequency of the page. The access frequency and dwell time are multiplied by the system's preset weight values, which reflect the relative importance of the number of visits and dwell time in the frequency calculation. Then, the weighted access frequency and dwell time are added together and added to the initial usage frequency value to obtain the total usage frequency of the page.

[0045] S203: Dividing the menu pages into frequently used menu pages and infrequently used menu pages according to the usage frequencies of the menu pages.

[0046] Specifically, all calculated menu page usage frequencies are sorted and compared with the preset page threshold. Pages with usage frequencies exceeding the threshold will be classified as frequently used menu pages, which means they will be loaded first in subsequent operations. On the contrary, pages with usage frequencies below the threshold are classified as uncommon menu pages, which may be delayed in loading when users access them or released when system resources are tight. Through this classification method, the system optimizes the allocation and use of memory resources, ensuring that frequently used pages can respond to user operations at a faster speed, while uncommon pages only occupy system resources when needed.

[0047] In one embodiment, if Figure 4 As shown, in step S202, the menu page usage frequency is calculated based on the menu page access frequency, the menu page stay time and the preset initial usage frequency value, including: S2021: Determine the frequency of menu page usage using the following formula: Ui=S i ×W i , where U i Refers to the frequency of menu page usage, W i refers to the access frequency weight, S i It refers to the weight of the length of stay.

[0048] Specifically, the menu page usage frequency U i is determined by dividing the access frequency weight W i and the length of stay weight S i First, the system will calculate the access frequency weight W of each menu page based on the user's historical operation data. i and the length of stay weight S i. Access frequency weight W i The weight Si reflects the relative importance of the user's visit frequency to a menu page among all pages, while the dwell time weight Si reflects the relative importance of the user's dwell time on the page. By multiplying these two weights, the system can comprehensively evaluate the overall usage frequency U of each menu page. i , which is the user's usage intensity and preference for the page. For example, if a page is visited frequently and stays there for a long time, then the usage frequency of the page is U i The page usage frequency U will be higher, which indicates that the page is more important to the user. On the contrary, if the page is visited less frequently and the stay time is shorter, then the page usage frequency U i The page usage will also be relatively low, and the system can classify it as a non-usable page, thereby reducing the priority loading or resource allocation of this page in subsequent operations.

[0049] In one embodiment, if Figure 5 As shown, in step S2021, the menu page usage frequency is determined by the following formula: Ui = S i ×W i , where U i Refers to the frequency of menu page usage, W i refers to the access frequency weight, S i Refers to the length of stay weight, including: S20211: Among them, W i refers to the access frequency weight, F i refers to the number of visits, P0 refers to the preset initial usage frequency value, α and β are weight coefficients, and α+β=1.

[0050] Specifically, F i Refers to the number of visits, P0 refers to the preset initial frequency of use value, α and β are weight coefficients, and α+β=1. The access frequency weight is calculated by multiplying the number of visits Fi of each menu page by the corresponding weight coefficient α, and then adding the preset initial frequency of use value P0 multiplied by another weight coefficient β. On this basis, the result is divided by the sum of the number of visits to all pages to ensure that the access frequency weight of each page reflects its importance in the user's usage habits. For example, if a page has 50 visits, an initial frequency of use value of 5, and weight coefficients α=0.7 and β=0.3, the access frequency weight of the page will be calculated by the formula, which is then used to determine the overall frequency of use of the page.

[0051] S20212: Among them, S i refers to the length of stay weight, T irefers to the length of stay, P0 refers to the preset initial frequency of use, γ and δ are weight coefficients, and γ+δ=1.

[0052] Specifically, T i Refers to the length of stay, P0 refers to the preset initial frequency of use value, γ and δ are weight coefficients, and γ+δ=1. The calculation method of the length of stay weight is similar to the calculation of the access frequency weight, which is obtained by multiplying the length of stay Ti of each menu page by the corresponding weight coefficient γ, and then adding the preset initial frequency of use value P0 multiplied by another weight coefficient δ. The result is then divided by the total length of stay of all pages to ensure that the length of stay weight of each page reflects the actual stay of the user on it. For example, if the length of stay of a page is 120 seconds, the initial frequency of use value is 5, and the weight coefficients γ=0.6 and δ=0.4, the length of stay weight of the page will be calculated by the above formula, and finally combined with the access frequency weight to determine the total frequency of use of the page.

[0053] In one embodiment, if Figure 6 As shown, in step S30, that is, when the menu page is switched, the commonly used menu page is loaded first, and the uncommon menu page is released when the menu page is switched to the background, including: S301: Detect the usage frequency of the menu page, and when the menu page is a frequently used menu page, directly load the frequently used menu page.

[0054] Specifically, the usage frequency U of each menu page is calculated by collecting and recording the user's operation data on each menu page in real time, combining the access frequency (i.e., the number of times a user accesses a menu page within a specific time period) and the stay time (i.e., the time the user stays on the menu page). i This frequency is usually calculated using a set of weighted formulas, such as U i =W i ×S i , where W i is the access frequency weight, S i is the dwell time weight. The system will compare these frequency data with the preset common menu threshold. If the usage frequency of a menu page is U iAbove this threshold, the system will mark the menu page as a frequently used menu page. Subsequently, when a user requests access to such a frequently used menu page, the system will immediately allocate the required memory resources and load the corresponding page. The loading process includes initializing the user interface of the menu page, loading related static resources such as images, icons, text, and setting the interactive logic of the page, so that the user can respond immediately when clicking on the menu page without any additional loading time. For example, when a user frequently visits the "Settings" menu many times, the system recognizes that the page is a frequently used page. The next time the user clicks it, the system will immediately load the "Settings" menu and quickly display the corresponding content.

[0055] S302: When the menu page is a not-so-common menu page and the memory resources are insufficient, delay loading of the not-so-common menu page.

[0056] Specifically, by analyzing the usage frequency U of each menu page i , pages with a usage frequency lower than a preset threshold are identified as infrequently used menu pages. Next, when users request to load these infrequently used menu pages, the system will first evaluate the memory resources to determine whether the currently available memory is sufficient to support the new page loading operation. If it is detected that the current memory resources are insufficient, that is, the remaining amount of system memory is lower than a certain set safety threshold (for example, the remaining memory is insufficient to support the loading and running of multiple pages at the same time), the system will decide to delay the loading of infrequently used menu pages. This decision is based on the global management of memory, giving priority to the normal operation of commonly used pages and important system processes, and avoiding excessive consumption of memory resources that leads to system performance degradation. The system will put the loading request of infrequently used pages into a queue, mark it as "pending", and load it again after the memory resources are restored. For example, when a user tries to open a rarely used "Help" menu, if the current system memory is close to full capacity, the system will choose not to load the "Help" menu temporarily, but record its request and wait until the memory resources are sufficient to load the page.

[0057] S303: When the menu page is switched to the background, the frequently used menu pages are retained and the uncommonly used menu pages are released.

[0058] Specifically, when the user switches applications or returns to the main interface, the background management program will be automatically triggered, which is responsible for managing the various menu pages currently in operation. First, the system will calculate the usage frequency U iDetermine which pages are frequently used and which are infrequently used. For frequently used pages, the system will continue to keep them resident in memory, which means that these pages will not be released when switched to the background, and the memory and resources they occupy will still be retained so that users can quickly switch back to the page when needed without reloading. For infrequently used pages, the system will automatically release the memory resources they occupy in the background to make room for other more important tasks. The release process includes cleaning up all UI elements, image resources, and processes and data associated with the page loaded in memory by the page, so as to reallocate resources to other high-priority operations. This strategy not only improves memory utilization efficiency, but also significantly improves the overall performance of the system, especially in embedded devices with limited memory resources. For example, when a user switches from an infrequently used "Statistics" menu to other applications, the system will immediately release all resources of the "Statistics" menu, while retaining the resources of the frequently used "Main Menu" page, so that users do not need to wait when switching back to the main menu.

[0059] In one embodiment, if Figure 7 As shown, in step S302, when the menu page is a non-common menu page and the memory resources are insufficient, the non-common menu page is loaded in a delayed manner, including: S3021: Determine the memory resource status, and when insufficient memory resources are detected, mark the menu page that is not frequently used as a waiting-to-be-loaded state.

[0060] Specifically, after receiving a request to load a non-common menu page, a series of memory resource detection operations are first performed. These operations include scanning the total amount of memory occupied by all currently running processes and pages, evaluating the specific value of the current available memory, and comparing the value with the memory safety threshold preset by the system. If the detection result shows that the current available memory is lower than the safety threshold, for example, lower than 20% of the total memory, the system will determine that the current memory resources are insufficient to support the loading of the new non-common page. In this case, the system will not load the non-common page immediately, but will temporarily put the loading request of the page on hold and mark it as "pending loading". The marking process involves storing the relevant information of the non-common page (such as page identifier, request time, etc.) in a pending queue, waiting for the system memory resources to return to a safe level before processing. This strategy can effectively prevent memory overflow or system crashes caused by insufficient memory, and ensure that the system can still run stably under high load. For example, when the system detects that the current memory usage has exceeded 80%, the "Feedback" page that the user attempts to open will be marked as "pending loading" and will be loaded after the memory is released.

[0061] S3022: When the memory resources are restored to an available state, the loading conditions of the uncommonly used menu pages are re-evaluated, and when the memory resources are sufficient, the uncommonly used menu pages are loaded.

[0062] Specifically, the usage of memory resources is continuously monitored, and the system will perform memory detection operations more frequently, especially when memory resources are tight. Once the system detects that memory resources have been restored to an available state, that is, the available memory has risen above the safety threshold, such as the available memory reaching more than 30% of the total memory, the system will re-evaluate the loading conditions of all non-common menu pages marked as "to be loaded". The re-evaluation process includes checking the current memory usage, analyzing the priority of non-common pages in the pending queue, and evaluating whether the loading of these pages will have a negative impact on system performance. If the evaluation results show that memory resources are sufficient and loading non-common pages will not cause resource shortages for other important tasks, the system will start to take non-common pages out of the waiting queue and perform actual loading operations. The loading process includes allocating sufficient memory resources, initializing the elements and interaction logic of the page, loading related static and dynamic resources, and ensuring that the various functions of the page can operate normally. Through this mechanism, the system can respond to the user's loading request in a timely manner when resource conditions permit, ensuring smooth access to the page without affecting other operations. For example, when memory resources are restored, the system will first load the "Help" page with a higher priority in the waiting queue to ensure that users can access it normally.

[0063] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0064] In one embodiment, a smart menu management device is provided, which corresponds one-to-one to the smart menu management method in the above embodiment. Figure 8 As shown, the intelligent menu management device includes an information acquisition module, a menu page division module and a page loading selection module. The detailed description of each functional module is as follows: Information acquisition module, used to obtain user history operation menu page information; The menu page division module is used to count the usage frequency of menu pages according to the user's historical operation menu page information, and divide the menu pages into frequently used menu pages and uncommon menu pages according to the usage frequency of menu pages; The page loading selection module is used to prioritize loading of commonly used menu pages when switching menu pages, and to release uncommonly used menu pages when the menu page switches to the background.

[0065] Optionally, the information acquisition module includes: Page initialization module, used to initialize the menu page.

[0066] Optionally, the menu page division module includes: The historical information acquisition submodule is used to obtain the menu page access frequency and menu page stay time from the user's historical operation menu page information; The page usage frequency submodule is used to calculate the menu page usage frequency based on the menu page access frequency, the menu page stay time and the preset initial usage frequency value; The page division submodule is used to divide the menu pages into frequently used menu pages and infrequently used menu pages according to the frequency of use of the menu pages.

[0067] Optionally, the page usage frequency submodule includes: The formula calculation unit is used to determine the menu page usage frequency by the following formula: Ui=S i ×W i , where U i Refers to the frequency of menu page usage, W i refers to the access frequency weight, S i It refers to the weight of the length of stay.

[0068] Optionally, the formula calculation unit includes: Access frequency subunit, used for Among them, W i refers to the access frequency weight, F i refers to the number of visits, P0 refers to the preset initial frequency of use, α and β are weight coefficients, and α+β=1; Dwell time unit, used for Among them, S i refers to the length of stay weight, T i refers to the length of stay, P0 refers to the preset initial frequency of use, γ and δ are weight coefficients, and γ+δ=1.

[0069] Optionally, the page loading selection module includes: The frequently used menu page submodule is used to detect the usage frequency of the menu page. When the menu page is a frequently used menu page, the frequently used menu page is directly loaded; The submodule of the uncommon menu page is used to delay the loading of uncommon menu pages when the menu page is an uncommon menu page and the memory resources are insufficient; The page release submodule is used to retain the commonly used menu pages and release the uncommonly used menu pages when the menu page is switched to the background.

[0070] Optional, less commonly used menu page submodules include: The waiting-to-load unit is used to determine the memory resource status. When insufficient memory resources are detected, the menu page that is not frequently used is marked as waiting-to-load status. The release unit is used to re-evaluate the loading conditions of the infrequently used menu pages when the memory resources are restored to an available state, and load the infrequently used menu pages when the memory resources are sufficient.

[0071] For the specific definition of the intelligent menu management device, please refer to the definition of the intelligent menu management method above, which will not be repeated here. Each module in the above intelligent menu management device can be implemented in whole or in part by software, hardware and a combination thereof. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0072] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Fig. 9 As shown. The computer device includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is a dynamically updated database. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, an intelligent menu management method is implemented.

[0073] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program: Get the user's historical operation menu page information; According to the historical operation information of the user, the frequency of use of the menu pages is counted, and the menu pages are divided into frequently used menu pages and uncommon menu pages according to the frequency of use of the menu pages; When switching menu pages, frequently used menu pages are loaded first, and uncommon menu pages are released when the menu page switches to the background.

[0074] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented: Get the user's historical operation menu page information; According to the historical operation information of the user, the frequency of use of the menu pages is counted, and the menu pages are divided into frequently used menu pages and uncommon menu pages according to the frequency of use of the menu pages; When switching menu pages, frequently used menu pages are loaded first, and uncommon menu pages are released when the menu page switches to the background.

[0075] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0076] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0077] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. An intelligent menu management method, characterized in that: The intelligent menu management method comprises: Get the user's historical operation menu page information; According to the menu page information of the user's historical operation, counting the usage frequency of the menu pages, and dividing the menu pages into frequently used menu pages and infrequently used menu pages according to the usage frequency of the menu pages; When the menu page is switched, the frequently used menu page is loaded first, and the uncommon menu page is released when the menu page is switched to the background.

2. The intelligent menu management method according to claim 1, characterized in that: The method of obtaining the user's historical operation menu page information further includes: Initialize the menu page.

3. The intelligent menu management method according to claim 1, characterized in that: The counting of the usage frequency of the menu pages according to the menu page history operation information of the user, and dividing the menu pages into frequently used menu pages and uncommon menu pages according to the usage frequency of the menu pages, comprises: Obtaining the menu page access frequency and the menu page stay time from the user's historical operation menu page information; The menu page usage frequency is calculated based on the menu page access frequency, the menu page stay time and a preset initial usage frequency value; The menu pages are divided into the frequently used menu pages and the infrequently used menu pages according to the usage frequency of the menu pages.

4. The intelligent menu management method according to claim 2, characterized in that: The calculating the menu page usage frequency based on the menu page access frequency, the menu page stay time and the preset initial usage frequency value includes: The usage frequency of the menu page is determined by the following formula: Ui=S i ×W i , where U i refers to the frequency of use of the menu page, W i refers to the access frequency weight, S i It refers to the weight of the length of stay.

5. The intelligent menu management method according to claim 2, characterized in that: The menu page usage frequency is determined by the following formula: Ui=S i ×W i , where U i refers to the frequency of use of the menu page, W i refers to the access frequency weight, S i Refers to the length of stay weight, including: Among them, W i refers to the access frequency weight, F i refers to the number of visits, P0 refers to the preset initial frequency of use, α and β are weight coefficients, and α+β=1; Among them, S i Refers to the length of stay weight, T i refers to the length of stay, P0 refers to the preset initial usage frequency value, γ and δ are weight coefficients, and γ+δ=1.

6. The intelligent menu management method according to claim 1, characterized in that: The method of loading the commonly used menu page first when the menu page is switched, and releasing the uncommonly used menu page when the menu page is switched to the background, comprises: Detecting the usage frequency of the menu page, and when the menu page is the frequently used menu page, directly loading the frequently used menu page; When the menu page is the uncommon menu page and memory resources are insufficient, delaying loading of the uncommon menu page; When the menu page is switched to the background, the frequently used menu page is retained and the uncommonly used menu page is released.

7. The intelligent menu management method according to claim 6, characterized in that: When the menu page is the uncommon menu page and memory resources are insufficient, delaying loading of the uncommon menu page includes: Determining the memory resource state, and when it is detected that the memory resource is insufficient, marking the uncommonly used menu page as being in a to-be-loaded state; When the memory resources are restored to an available state, the loading condition of the infrequently used menu page is re-evaluated, and when the memory resources are sufficient, the infrequently used menu page is loaded.

8. An intelligent menu management device, characterized in that: The intelligent menu management device comprises: Information acquisition module, used to obtain user history operation menu page information; A menu page division module is used to count the usage frequency of menu pages according to the menu page history operation information of the user, and divide the menu pages into commonly used menu pages and uncommon menu pages according to the usage frequency of the menu pages; The page loading selection module is used to preferentially load the commonly used menu page when the menu page is switched, and release the uncommonly used menu page when the menu page is switched to the background.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the intelligent menu management method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the intelligent menu management method according to any one of claims 1 to 7 are implemented.

Citation Information

Cited By

  • Browser-based AI intelligent interactive software upgrading method

    CN122064418A