Page processing method and device, storage medium and electronic equipment

Abstract

The application discloses a page processing method and device, a storage medium and an electronic device, and relates to the technical field of human-computer interaction. The method comprises the following steps: receiving a target request of a user on a target page, wherein the target request is used for requesting a target page layout scheme stored by the user in a historical time period; based on the target request, obtaining a target data structure corresponding to the target page layout scheme from a server, wherein the target data structure is used for storing metadata information, a query condition, display configuration information and a display state of a condition item of a page; based on a target algorithm, applying the target page layout scheme on the target page according to the target data structure, wherein the target algorithm is used for identifying difference information between the target page and the target page layout scheme, and adjusting the target page based on the difference information. The application solves the technical problem that the state storage of a data query interface is incomplete and inefficient in the technical field of human-computer interaction, and the user experience is poor.

Description

Technical Field

[0001] This application relates to the field of human-computer interaction technology, and more specifically, to a page processing method, apparatus, storage medium, and electronic device. Background Technology

[0002] In the field of human-computer interaction technology, especially in the design of query interfaces for database management systems, business intelligence analysis tools, and enterprise application software, optimizing user experience has always been a goal pursued by developers. However, existing interface state storage and recovery technologies have significant shortcomings, greatly affecting user operational efficiency and experience. Traditional storage solutions often focus only on saving SQL query parameters and simple interface configuration information, such as the status of query conditions and the basic column widths of tables, while ignoring more complex interface elements, such as the hiding status of columns, sorting rules, and the display control of condition items. This forces users to manually readjust these neglected interface configurations when restoring the query interface, adding an extra operational burden.

[0003] On the other hand, even for basic configuration items, traditional methods fail to provide an efficient recovery mechanism. When switching query schemes, users need to perform multiple manual operations to completely restore the interface to its saved state, especially when a large number of query conditions and complex table configurations are involved, the recovery process becomes particularly cumbersome and time-consuming.

[0004] There is currently no effective solution to the above problems. Summary of the Invention

[0005] This application provides a page processing method, apparatus, storage medium, and electronic device to at least solve the technical problem in the field of human-computer interaction technology that incomplete storage and low recovery efficiency of data query interface state lead to poor user experience.

[0006] According to one aspect of this application, a page processing method is provided, comprising: receiving a target request from a user on a target page, wherein the target request is used to request a target page layout scheme stored by the user in a historical time period; based on the target request, obtaining a target data structure corresponding to the target page layout scheme from a server, wherein the target data structure is used to store the page's metadata information, query conditions, display configuration information, and display status of condition items; and based on a target algorithm, applying the target page layout scheme to the target page according to the target data structure, wherein the target algorithm is used to identify the difference information between the target page and the target page layout scheme, and adjust the target page based on the difference information.

[0007] Optionally, before receiving the user's target request on the target page, the method further includes: receiving the user's save instruction, wherein the save instruction is used to save the user's modification operation on the target page; after receiving the save instruction, constructing a target data structure based on the modification operation; and sending the target data structure to the server for storage.

[0008] Optionally, the target data structure includes at least the following structures: a first-level structure, wherein the first-level structure stores metadata information of the target page layout scheme, wherein the metadata information includes the scheme name, business identifier, and version identifier of the target page layout scheme; a second-level structure, wherein the second-level structure stores query conditions of the target page layout scheme, wherein the query conditions represent data filtering information set by the user on the target page; a third-level structure, wherein the third-level structure stores display configuration information of the target page layout scheme, wherein the display configuration information represents page layout information set by the user on the target page; and a fourth-level structure, wherein the fourth-level structure stores the display status of the condition items in the target page layout scheme.

[0009] Optionally, the page processing method further includes: listening to target events at the table container level in the target page, wherein the target events are used to capture dynamic changes in the table; detecting N change information of the table at preset intervals using the target events, wherein N is an integer greater than or equal to 1; when N change information of the table is detected within the preset interval, aggregating the N change information and storing the aggregated N change information locally.

[0010] Optionally, the version identifier includes a system identifier. Based on the target algorithm, the target page layout scheme is applied to the target page according to the target data structure, including: detecting whether the system identifier in the version identifier corresponding to the target data structure is the same as the target identifier stored on the server; when the system identifier is detected to be the same as the target identifier, the target page layout scheme is applied to the target page according to the target data structure based on the target algorithm; when the system identifier is detected to be different from the target identifier, the target data structure is updated according to the first algorithm, wherein the first algorithm is used to adjust the format of the information in the target data structure; and the target page layout scheme is applied to the target page according to the updated target data structure based on the target algorithm.

[0011] Optionally, based on the target algorithm, the target page layout scheme is applied to the target page according to the updated target data structure, including: obtaining the updated target data structure from the server, and determining the difference information between the page state of the target page and the target data structure based on the target algorithm; and applying the target page layout scheme to the target page based on the difference information.

[0012] Optionally, the target data structure is sent to the server for storage, including: storing the information in the target data structure into a first database and a second database on the server according to user requirements; wherein the first database is an in-memory database and the second database is a relational database, the first database is used to store information in the target data structure whose access frequency is greater than or equal to a first preset threshold, and the second database is used to store information in the target data structure whose change frequency is less than a second preset threshold.

[0013] According to another aspect of this application, a page processing apparatus is also provided, comprising: a receiving unit, configured to receive a target request from a user on a target page, wherein the target request is used to request a target page layout scheme stored by the user in a historical time period; an obtaining unit, configured to obtain a target data structure corresponding to the target page layout scheme from a server based on the target request, wherein the target data structure is used to store the page's metadata information, query conditions, display configuration information, and display status of condition items; and an application unit, configured to apply the target page layout scheme to the target page based on a target algorithm and the target data structure, wherein the target algorithm is used to identify the difference information between the target page and the target page layout scheme, and adjust the target page based on the difference information.

[0014] According to another aspect of this application, a computer-readable storage medium is also provided, which includes a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the page processing method described above.

[0015] According to another aspect of this application, an electronic device is also provided, including one or more processors and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform the page processing method described above.

[0016] This application first receives a target request from a user on a target page. This target request requests a target page layout scheme stored in historical time periods. Then, based on the target request, it retrieves the target data structure corresponding to the target page layout scheme from the server. This target data structure stores the page's metadata, query conditions, display configuration information, and the display status of condition items. Next, based on a target algorithm, the target page layout scheme is applied to the target page according to the target data structure. This target algorithm identifies the differences between the target page and the target page layout scheme and adjusts the target page accordingly. In other words, by integrating a composite storage structure of user behavior with intelligent partial updates, it achieves complete storage and efficient recovery of the interface state. This significantly improves the efficiency and accuracy of interface state recovery, optimizes the user experience, and solves the technical problem in human-computer interaction technology where incomplete data query interface state storage and low recovery efficiency lead to poor user experience. Attached Figure Description

[0017] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0018] Figure 1 This is a flowchart of an optional page processing method according to an embodiment of this application;

[0019] Figure 2 This is a schematic diagram of an optional composite storage structure according to an embodiment of this application;

[0020] Figure 3 This is a schematic diagram of an optional network request for a page processing method according to an embodiment of this application;

[0021] Figure 4 This is a schematic diagram of the front-end and back-end interaction of an optional page processing method according to an embodiment of this application;

[0022] Figure 5 This is a schematic diagram of an optional page processing method applied to a software development management platform according to an embodiment of this application;

[0023] Figure 6 This is a schematic diagram of an optional page processing method applied to an e-commerce order management platform according to an embodiment of this application;

[0024] Figure 7 This is a schematic diagram of an optional page processing apparatus according to an embodiment of this application. Detailed Implementation

[0025] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0026] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0027] It should be noted that the information collected in this application (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data used for analysis, etc.) are information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of this data all comply with relevant laws, regulations, and standards, necessary confidentiality measures have been taken, and they do not violate public order and good morals. Corresponding access points are provided for users to choose to authorize or refuse. For example, interfaces are set up between this system and relevant users or organizations, providing users with corresponding access points to choose to agree to or refuse automated decision-making results; if the user chooses to refuse, the process proceeds to the expert decision-making stage.

[0028] According to an embodiment of this application, a method embodiment for page processing is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0029] It should be noted that an intelligent processing system can serve as the execution subject of the page processing method in the embodiments of this application. It is understood that the page processing method provided in the embodiments of this application can also be executed by other systems or devices, and the embodiments of this application do not specifically limit this.

[0030] Figure 1 This is a flowchart of an optional page processing method according to an embodiment of this application, such as... Figure 1 As shown, the method includes the following steps:

[0031] Step S101: Receive the user's target request on the target page.

[0032] In step S101, the target request is used to request the target page layout scheme stored by the user in the historical time period.

[0033] Optionally, the target page is the query interface that the user is currently using, which includes elements such as a query condition setting area, a result display table, and a condition item operation panel.

[0034] Optionally, the target request is a user-initiated request action specific to a query interface layout scheme saved before the request, i.e., the user wants to restore to a certain historical state.

[0035] Optionally, historical time period storage refers to the interface state saved by the user at a certain point in the past. The term "historical time period" is used to emphasize the effectiveness and traceability of storage in the time dimension.

[0036] Optionally, when a user needs to restore the previous interface state, they can trigger the system to execute by clicking or selecting a saved scheme. After receiving the user's target request, the intelligent processing system immediately enters the data acquisition preparation state, preparing to retrieve the historical interface layout scheme data specified by the user from the server.

[0037] Step S102: Based on the target request, obtain the target data structure corresponding to the target page layout scheme from the server.

[0038] In step S102, the target data structure is used to store the page's metadata information, query conditions, display configuration information, and display status of condition items.

[0039] Optionally, the target data structure is a key component of this invention, used to encapsulate the target page's metadata information, query conditions, display configuration information, and the display status of condition items. Specifically, it includes: metadata information such as the scheme's unique identifier (resId) and business identifier (ywkey); query conditions such as user-defined filtering parameters like product type and order status; display configuration information such as column width, column hiding status, and sorting rules for the results display table; and the display status of condition items, specifically the display or hiding status of each item in the condition panel.

[0040] Optionally, the intelligent processing system sends a request to the server pointing to a specific target data structure. The server then uses the information provided in the request (such as resId) to locate and extract the corresponding interface state data, encapsulates it into JSON or other structured data formats, and returns it to the front end via the network. This process ensures an accurate match between the user request and the specific storage solution, providing basic data support for the rapid recovery of the interface state.

[0041] Step S103: Based on the target algorithm, apply the target page layout scheme to the target page according to the target data structure.

[0042] In step S103, the target algorithm is used to identify the difference information between the target page and the target page layout scheme, and adjust the target page based on the difference information.

[0043] Optionally, the target algorithm, specifically the difference recovery algorithm in this embodiment, focuses on comparing the differences between the interface state in the target data structure and the current page state, rather than performing a full update. By identifying changes (such as changes in the hidden state of columns, updates to query conditions, etc.), this algorithm can accurately adjust the target page to restore it to the state when the layout scheme was saved.

[0044] Optionally, the difference information refers to the difference between the current state of the target page and the state saved in the target page layout scheme. This can be a change in the query conditions, a difference in column configuration, or a change in the display status of the condition items.

[0045] Optionally, after receiving the target data structure returned by the server, the intelligent processing system initiates a target algorithm to perform difference analysis and identify all elements that need to be updated. Subsequently, based on the difference information obtained from the analysis, the intelligent processing system automatically adjusts the corresponding interface components (such as table columns, conditional panel, etc.) to ensure that the target page accurately presents the layout scheme requested by the user. This algorithm not only significantly improves the efficiency of page restoration and avoids unnecessary resource consumption, but also ensures the consistency and continuity of the user experience. Even in the face of system upgrades or environmental changes, the user's personalized interface settings can be effectively preserved.

[0046] Optionally, this embodiment can be adapted to different industry sectors, and the composite storage structure can significantly improve efficiency in various business scenarios.

[0047] As described in steps S101 to S103, this application first receives a target request from a user on a target page. This target request requests a target page layout scheme stored by the user within a historical time period. Then, based on the target request, the application retrieves the target data structure corresponding to the target page layout scheme from the server. This target data structure stores the page's metadata, query conditions, display configuration information, and the display status of condition items. Next, based on a target algorithm, the target page layout scheme is applied to the target page according to the target data structure. This target algorithm identifies the differences between the target page and the target page layout scheme and adjusts the target page based on these differences. In other words, by integrating a composite storage structure of user behavior with intelligent partial updates, the application achieves complete storage and efficient recovery of the interface state. This significantly improves the efficiency and accuracy of interface state recovery, optimizes the user experience, and solves the technical problem in human-computer interaction technology where incomplete data query interface state storage and low recovery efficiency lead to a poor user experience.

[0048] In one optional embodiment, before receiving the user's target request on the target page, the intelligent processing system first receives the user's save instruction, wherein the save instruction is used to save the user's modification operation on the target page. After receiving the save instruction, the system constructs a target data structure based on the modification operation and then sends the target data structure to the server for storage.

[0049] Optionally, before a user begins interacting with and modifying the target page, the intelligent processing system remains in standby mode, ready to respond to any user commands. Once the user has completed a series of modifications, such as adjusting query criteria, changing column widths in the results table, or setting the display status of condition items, the system waits for the user to issue a save command. This command is an action initiated by the user, indicating that the user wishes to save the current interface state so that it can be quickly restored to this state in the future.

[0050] Optionally, when the intelligent processing system detects a user's save command, it immediately activates its internal state capture mechanism. This mechanism remains in a listening state throughout the entire user interaction process, capturing every minute change on the target page, whether it's a change in the selection of query conditions, a fine-tuning of column configuration, or a switch in the display status of condition items; all of these are recorded in real time.

[0051] Optionally, upon receiving a save command, the intelligent processing system begins the process of constructing the target data structure. This data structure is complex and ingeniously designed, organizing all captured modification operations, including query conditions, display configuration information, and the display status of condition items, in a hierarchical manner. The construction of this data structure not only requires the intelligent processing system to accurately identify and classify different modification operations, but also necessitates its powerful integration capabilities to integrate this scattered information into a highly abstract data template. This step is crucial for ensuring the accuracy of subsequent storage and recovery operations.

[0052] Optionally, after construction, the intelligent processing system sends the target data structure to the server via a network request. On the server, a dedicated storage module receives these data structures, performs preliminary validation and format checks, and then stores them in the database. This storage process employs special strategies, such as using resId version identifiers, to ensure the long-term availability of the data structures and seamless compatibility between versions.

[0053] As described above, this embodiment allows users to easily save their current working environment. With just a simple save command and target request, the interface can be restored to its state at the time of saving, significantly saving time and effort and improving user efficiency and satisfaction in data query and analysis tasks. Furthermore, the construction and storage strategy of the target data structure provides a solid foundation for long-term system maintenance and version upgrades, ensuring that even when the system architecture changes or is updated, the user-saved interface state can still be accurately preserved and restored, thereby promoting continuous optimization and improvement of the user experience.

[0054] In one optional embodiment, the target data structure includes at least the following structures: a first-layer structure, wherein the first-layer structure is used to store metadata information of the target page layout scheme, wherein the metadata information includes the scheme name, business identifier, and version identifier of the target page layout scheme; a second-layer structure, wherein the second-layer structure is used to store query conditions of the target page layout scheme, wherein the query conditions are used to characterize data filtering information set by the user on the target page; a third-layer structure, wherein the third-layer structure is used to store display configuration information of the target page layout scheme, wherein the display configuration information is used to characterize page layout information set by the user on the target page; and a fourth-layer structure, wherein the fourth-layer structure is used to store the display status of the condition items in the target page layout scheme.

[0055] Optionally, to address the issue of separating query conditions from display configurations in traditional interface state storage solutions, and to improve the efficiency and accuracy of interface state recovery, this embodiment proposes a hierarchical target data structure construction method. This data structure aims to comprehensively capture the user's operational state on the target page, including but not limited to data filtering, page layout configuration, and preference settings for displaying conditional items, thereby providing complete state saving and one-click recovery functionality.

[0056] Optionally, in the first step of constructing the target data structure, the intelligent processing system creates a first-level structure to store metadata information about the target page layout scheme. This includes the scheme's name (e.g., "financial statement query scheme") for quick identification and searching; a business identifier (ywkey), a unique identifier related to specific business logic, which helps the system accurately locate the layout scheme related to the current query within a large database; and a version identifier (resId), used to track interface version changes, ensuring that the scheme can still be correctly understood and applied after system upgrades. This first-level structure forms the skeleton of the data structure, determining the context and validity scope of subsequent layers.

[0057] Optionally, following the first layer, the intelligent processing system builds a second layer structure, focusing on encapsulating all the query conditions set by the user on the target page. Query conditions include, but are not limited to, filter parameters entered by the user in the form, such as "product category" and "order date range," which are the basis for data filtering and querying. By storing query conditions in this layer structure, the intelligent processing system can ensure that even if other parts of the interface change, the user can quickly restore the previously set filter conditions without having to manually enter them again.

[0058] Optionally, the third layer is dedicated to storing display configuration information, i.e., user-defined page layout information on the target page. This includes the hiding and showing status of table columns, column width adjustments, sorting rules, etc., which are important factors affecting the user's intuitive experience and ease of operation. By recording this display configuration information, the system can remember the user's preferred result display style, such as hiding redundant fields, highlighting key data, or adjusting column widths to adapt to different screen resolutions or reading habits, thereby providing a personalized interface display on the next visit.

[0059] Optionally, the final layer, the fourth layer, is specifically used to record the display status of condition items in the target page layout. In complex data query interfaces, users may selectively show or hide certain condition items to reduce visual clutter or focus on specific filtering options. The introduction of this layer ensures that the display status of condition items can also be completely preserved, which is undoubtedly a great convenience for users who frequently need to adjust the layout of condition items.

[0060] Optionally, the target data structure includes:

[0061] Meta layer (first layer structure): Records metadata such as scheme name, business identifier (ywkey), resource ID (resId), etc., and supports multi-scheme management;

[0062] The condition layer (second-level structure) stores dynamic query conditions (such as input values ​​and selector states) using a key-value pair structure (e.g., "status":{"value":null}).

[0063] The display layer (third layer structure) independently stores the result display configuration (such as table column width and hiding status), which is implemented through the gridSettingData object (unlike the traditional method of only saving query conditions);

[0064] Condition item status layer (fourth layer structure): The display status of the condition item.

[0065] Optionally, Figure 2 This is a schematic diagram of an optional composite storage structure according to an embodiment of this application, such as... Figure 2 As shown, this composite storage structure includes: a condition layer, a display layer, a condition item status layer, and a meta layer. The condition layer stores dynamic query conditions, such as various parameters entered or selected by the user in the query form. Each condition (field) has an associated value and operator. For example, field 1: status = {value:"Processed", operator:13} indicates that the status query condition is "Processed", and the operator is 13. Field 2 can also store corresponding content in the format {value}. The display layer mainly stores the result display configuration, i.e., the column display status (whether it is hidden), column width, etc. Figure 2This includes a `gridSettingData` object, which contains the state configuration of table columns, such as column name, hidden status, and width; `list.cols.colModels`: a collection of columns containing the configuration models for all table columns. For example, column 1: `name="Order Number", hidden="false", width="150"` describes the display status and width of the "Order Number" column. Column 2 can be configured similarly. The condition item state layer records the display status of condition items, allowing the system to know which condition items are visible and which are hidden. For example, condition 1's state value 2 indicates display, and condition 2's state value 4 indicates hiding. The Meta layer: a metadata layer that stores basic information about the query scheme, such as scheme name (`name`), business identifier (`ywkey`), and resource ID (`resId`). The business identifier is used to distinguish different business scenarios, while the resource ID is used for version control to ensure scheme compatibility.

[0066] As described above, by employing the composite target data structure construction method, the intelligent processing system can comprehensively and meticulously save the user's operational state on the data query interface, covering all aspects from query condition settings to result display layout. This means that users can not only quickly restore to a specific data filtering state, but also reproduce their previous page layout and condition item display preferences with a single click, greatly improving operational efficiency and user experience. More importantly, by storing metadata information, query conditions, display configuration information, and condition item display states in different layer structures, this embodiment ensures that even with system updates or environmental changes, the user's saved interface state can be accurately restored. For example, when a system upgrade introduces new condition items, the old scheme can use version identifier (resId) comparison and difference recovery algorithms to supplement missing configurations, ensuring the continued effectiveness and adaptability of the scheme.

[0067] In one optional embodiment, the intelligent processing system listens for target events at the table container level in the target page. The target events are used to capture dynamic changes in the table. The system detects N change information of the table at preset intervals for the target events, where N is an integer greater than or equal to 1. When N change information of the table is detected within the preset interval, the system aggregates the N change information and stores the aggregated N change information locally.

[0068] Optionally, in the field of human-computer interaction technology, especially in data query systems, users often need to adjust column widths, hide or show certain columns, and perform sorting operations when browsing and analyzing table data. To capture these dynamic changes, this embodiment adopts a strategy of listening to target events at the table container level to achieve real-time monitoring and optimization of the stored table state.

[0069] Optionally, the intelligent processing system deploys event listeners at the table container level of the target page. This level covers all elements of the table, including column headers, data rows, and sorting icons. Target events encompass all operations that may cause changes to the table's state, such as users dragging column borders to adjust column widths, clicking column headers to sort, or hiding columns using mouse menus. By listening to target events at this level, the system can promptly capture any minor adjustments made to the table by the user, ensuring that no important user actions are missed.

[0070] Optionally, to avoid processing and storing user operations too frequently, the intelligent processing system employs a timing strategy. The system sets a preset listening period (e.g., every 500 milliseconds). Within this period, the event listener records all user operations on the table. For example, if within 500 milliseconds, the user adjusts column widths, hides a column, and sorts another column, the system will record these N changes, where N is the actual number of operations, at least one.

[0071] Optionally, once the monitoring period ends, the intelligent processing system will aggregate all the change information recorded during that period. The purpose of aggregation is to reduce unnecessary data transmission and storage. By merging similar items, the system can compress N change messages into a single, more concise status update message. For example, if a user adjusts the width of the same column multiple times within the same period, the system will only record the final width value, not each adjustment record. The aggregated change information will be temporarily stored in the front-end's local storage, such as sessionStorage or localStorage, in preparation for subsequent real-time storage or scenario saving.

[0072] Optionally, the intelligent processing system listens for events such as columnResized at the table container level, rather than listening for each column individually. It aggregates state changes every 500ms, which can significantly reduce the processing frequency.

[0073] As described above, the intelligent processing system significantly improves the accuracy and efficiency of table status monitoring by listening to target events at the table container level and combining this with a strategy of timed detection and change information aggregation. Every minute adjustment made by the user during operation is accurately captured, and through aggregation processing, invalid network requests and storage operations caused by frequent changes can be avoided. The local storage strategy not only reduces the overhead of real-time storage but also provides users with the ability to resume interrupted access. Even if the user suddenly disconnects or leaves the page before initiating a formal save, their latest operation status can be preserved, improving user experience and data security.

[0074] The implementation of this technical strategy not only solves the problem of incomplete interface state preservation in traditional storage solutions, but also improves system response speed and performance by reducing network transmission volume and optimizing storage mechanisms. Furthermore, for enterprise applications, this optimization can effectively reduce server load in environments with large-scale concurrent user operations, ensuring service stability and high efficiency.

[0075] In one optional embodiment, the intelligent processing system detects whether the system identifier in the version identifier corresponding to the target data structure is the same as the target identifier stored on the server; when the system identifier is detected to be the same as the target identifier, the system applies the target page layout scheme on the target page based on the target algorithm and the target data structure; when the system identifier is detected to be different from the target identifier, the system updates the target data structure based on the first algorithm, wherein the first algorithm is used to adjust the format of the information in the target data structure, and then the system applies the target page layout scheme on the target page based on the updated target data structure.

[0076] Optionally, to ensure that the target page layout scheme saved by the user can still be accurately restored and applied after system upgrades or architecture changes, the intelligent processing system adopts a two-pronged strategy of version identifier detection and data structure adjustment.

[0077] Optionally, when a user selects a saved layout scheme on the target page, the intelligent processing system first detects the version identifier contained in the target data structure. This identifier includes system identifier information, which reflects the characteristics of the current operating environment, such as the operating system version, browser type, or software platform. It is used to identify the current state of the system. The system compares the system identifier stored in the target data structure with the target identifier (the system identifier stored on the server). This comparison process is crucial because it directly relates to the compatibility and effectiveness of the scheme. If they match, it means that the saved scheme is compatible with the current system environment, and the target algorithm can be directly applied to restore the interface state.

[0078] Optionally, if the system identifier matches the target identifier, the intelligent processing system will directly read and apply the information in the target data structure based on the target algorithm. The target algorithm can identify the differences between the target page and the saved layout scheme, and then accurately adjust the target page to achieve a fast and complete restoration of the user interface state. This process typically involves a series of operations such as updating query conditions, adjusting table column configurations, and controlling the display status of condition items to ensure that the user interface presents a state completely consistent with that at the time of saving.

[0079] Optionally, when the intelligent processing system detects a mismatch between the system identifier and the target identifier, it means that the user-saved solution may not be directly applicable to the current system environment. This could be due to reasons such as software version upgrades, API changes, or adjustments to the interface element structure. In this case, the intelligent processing system will activate the first algorithm (version conversion algorithm) to adjust the information format in the target data structure. The task of the first algorithm is to convert the saved interface state data into a format acceptable to the current system environment to resolve version compatibility issues and ensure data availability and the effectiveness of the solution.

[0080] Specifically, the first algorithm iterates through each layer of the target data structure, such as query conditions, display configurations, and condition item statuses, and performs format conversion on data items that do not conform to the current system standards. For example, if an old version used a deprecated query field, the first algorithm will replace it with an equivalent field in the new version, or complete the data structure by adding missing fields to make it match the current system environment.

[0081] As described above, the intelligent processing system significantly enhances the robustness and flexibility of interface state saving and restoration by introducing version identifier detection and dynamic data structure adjustment mechanisms. Regardless of changes in the system environment, users can rely on this mechanism to ensure that their carefully customized interface layout schemes can be accurately restored without worrying about scheme failures due to software upgrades or version changes. This strategy not only protects users' investment and reduces repetitive work but also improves system maintainability and user-friendliness. By ensuring that the format of the target data structure remains consistent with the current system environment, the intelligent processing system can smoothly transition between system versions without affecting user experience, avoiding user confusion and system failures caused by version incompatibility, thereby maintaining stable system operation and service quality. Furthermore, this mechanism reserves space for future system upgrades and expansions, allowing developers greater freedom to innovate without excessive concern about damaging user-saved data.

[0082] In one optional embodiment, the intelligent processing system obtains the updated target data structure from the server, determines the difference information between the page state of the target page and the target data structure based on the target algorithm, and then applies the target page layout scheme on the target page based on the difference information.

[0083] Optionally, when a user selects a historically saved layout scheme on the target page, the intelligent processing system sends a request to the server to obtain the target data structure corresponding to that scheme. Given potential system updates or other changes, the server may have already adjusted and stored the target data structure based on the latest system environment using the first algorithm. Therefore, the intelligent processing system obtains an optimized, updated target data structure compatible with the current operating environment.

[0084] Optionally, upon receiving the updated target data structure, the intelligent processing system does not blindly apply the entire structure. Instead, it first activates the target algorithm to determine the discrepancies. The target algorithm analyzes the current state of the target page against the state stored in the target data structure, identifying any inconsistencies. This process may involve comparing query conditions, verifying display configurations, and checking the display status of condition items. The aim is to identify the minimum necessary adjustments, rather than a full update, to reduce unnecessary computational resource consumption and improve recovery efficiency.

[0085] Specific implementation details may include: Query condition comparison: By comparing the condition values ​​in the target data structure with the condition values ​​currently displayed on the target page, determine which conditions need to be adjusted or supplemented; Display configuration difference identification: Check the column widths, sorting rules, and hidden status of the tables in the target data structure, match them with the actual layout of the target page, and find the configuration items that need to be changed; Condition item status verification: Ensure that the display status of the condition items in the target data structure is consistent with the current status of the target page, and update them if necessary.

[0086] Optionally, after determining the discrepancy information, the intelligent processing system applies the target page layout scheme to the target page based on this information. This process is guided by a target algorithm and operates only on the interface elements that need adjustment, avoiding unnecessary redrawing of parts that do not need to be changed. For example, if the discrepancy information indicates that the hidden state of a column is inconsistent with that at the time of saving, the target algorithm will only change the display state of that column without affecting other columns or other attributes of the entire table.

[0087] As can be seen from the above, the core of this embodiment lies in achieving efficient and accurate interface state restoration through the determination and precise application of difference information. This means that when users restore historically saved page layouts, the system can quickly identify the smallest set of adjustments, avoiding the delays and resource waste caused by full updates, while also ensuring that the restored interface state is completely consistent with the one saved, meeting users' needs for reproducing customized interface states. Specific technical effects are as follows: By applying difference information in a targeted manner, rather than a full update, the interface state restoration time is significantly shortened, improving the user experience; the intelligent processing system avoids a full redraw of page elements, reducing the consumption of computing resources, especially for large table data and complex layout adjustments, this effect is more pronounced; the combination of the server-side update mechanism and the difference information determination by the intelligent processing system ensures that the interface state solution remains effective after system upgrades, strengthening the system's long-term maintainability and user experience continuity.

[0088] In one optional embodiment, the intelligent processing system stores the information in the target data structure into a first database and a second database on the server according to user needs; wherein, the first database is an in-memory database and the second database is a relational database, the first database is used to store information in the target data structure whose access frequency is greater than or equal to a first preset threshold, and the second database is used to store information in the target data structure whose change frequency is less than a second preset threshold.

[0089] Optionally, to address the information storage problem in the target data structure, the intelligent processing system proposes a distributed storage scheme aimed at improving data query efficiency while ensuring data security and persistence. Based on the access and change frequency of the information, the system stores the information in the data structure in two types of databases on the server: an in-memory database (first database) and a relational database (second database).

[0090] Optionally, the intelligent processing system first analyzes the information in the target data structure to determine which information is accessed frequently and which information changes infrequently. This evaluation process, based on historical data analysis and user behavior patterns, can be dynamically adjusted to adapt to constantly changing usage scenarios. For example, "product category" in the query criteria may be considered high-frequency access information because users switch frequently, while "hidden settings of table columns" may be considered low-frequency change information because users rarely modify them.

[0091] Optionally, after determining the information attributes, the intelligent processing system stores information with an access frequency greater than or equal to a first preset threshold (such as query conditions, recently used scheme names, etc.) in a first database, i.e., an in-memory database. This type of database features fast read and write speeds, making it particularly suitable for storing data requiring rapid access. Since the first database resides in RAM, the time for information to be accessed in memory is almost zero, greatly accelerating query speeds and improving user response efficiency. However, considering the non-persistent nature of in-memory data, the system only stores frequently accessed, small-volume, and non-critical information in the in-memory database to ensure that important data is not lost even if the system restarts.

[0092] Optionally, simultaneously, information with a change frequency less than a second preset threshold, such as the specific configuration of table columns (column width, position, etc.) and the display status of condition items, is stored in a second database, namely a relational database. Relational databases are known for their high data consistency and durability, making them suitable for storing information that needs to be preserved for a long time and is not easily changed. By storing this type of information in a relational database, the intelligent processing system ensures data security and long-term access capability, so that even during system upgrades or architecture adjustments, the user-saved interface state data will not be compromised.

[0093] It's worth noting that the intelligent processing system also has the ability to dynamically adjust storage strategies. This means that as user habits change, the system can automatically update the first and second preset thresholds to adapt to changes in the frequency of information access and changes. For example, if the system detects that "column width settings," which were originally considered to have a low frequency of change, have become a high-frequency access item due to recent frequent adjustments by users, it will re-evaluate and migrate this information from the relational database to the in-memory database to improve read speed.

[0094] As shown above, by implementing this distributed storage strategy, the intelligent processing system not only optimizes the storage efficiency of the data query interface state but also improves data security and durability. High-frequency access information, stored in an in-memory database, can achieve near-instantaneous read and update, significantly reducing user waiting time and enhancing user experience. Conversely, low-frequency change information, through persistent storage in a relational database, ensures that even after long time intervals or system failures, the user-saved interface layout can still be fully restored. Furthermore, the ability to dynamically adjust the storage strategy allows the system to flexibly adapt to different usage scenarios and user needs, ensuring efficient resource utilization, reducing unnecessary data loading and transmission overhead, and improving overall system performance. This mechanism not only improves user efficiency in daily operations but also saves costs for enterprises at the operational level, increasing system scalability and robustness.

[0095] In one alternative embodiment, Figure 3 This is a schematic diagram of an optional network request for a page processing method according to an embodiment of this application, such as... Figure 3 As shown, the system comprises three parts: user, front-end, and back-end. First, the user modifies the page (interface) state on the front-end. The front-end captures all user changes (capture changes), including query conditions, display configuration information, and condition item statuses. Then, the user clicks "save scheme." At this point, the front-end sends an HTTP POST request (POST / uploadQueryScheme) to the back-end, sending the captured composite data structure (including metadata information, query conditions, display configuration, and condition item statuses) to the server (back-end). After receiving the data from the front-end, the back-end is responsible for storing this composite data structure. This may involve classifying and storing the data in different databases, such as storing high-frequency access information in an in-memory database and low-frequency change information in a relational database. If the data storage is successful, the back-end will return a success response (usually an HTTP status code of 200 OK), confirming the save status of the scheme. Then, when the user selects a previously saved interface layout scheme on the interface, the front end sends a GET request (GET / getQuerySchemes) to the back end to retrieve all layout schemes stored under a specific business identifier. The back end system retrieves all relevant schemes from the database based on the request identifier, and then returns the list of found schemes to the front end so that the front end can display them to the user for selection. The user selects a specific scheme from the returned scheme list to restore the complete state of the scheme applied on the front end.

[0096] In one alternative embodiment, Figure 4 This is a schematic diagram illustrating the front-end and back-end interaction of an optional page processing method according to an embodiment of this application, such as... Figure 4 As shown, users adjust query conditions, table column states, and show / hide condition items on the front-end page. The front-end event listener captures these changes and updates the value field, gridSettingData, and conditionItems through the state collector. Then, when the user clicks to save the scheme, the front-end obtains the updated complete state, encapsulates it into a composite data structure, and sends a POST request (POST / uploadQueryScheme) to the back-end to save the interface state scheme. After successful saving, the back-end generates a 200 OK response.

[0097] In one optional embodiment, within a software development management platform, users may frequently use complex query functions (such as requirement queries), including 50+ query conditions (status, product, module, etc.), a data table with 45+ columns (adjustable column width, hidden columns, sorting, etc.), and dynamically show / hide condition items. Applying this solution based on this context can significantly improve page recovery efficiency. Figure 5 This is a schematic diagram of an optional page processing method applied to a software development management platform according to an embodiment of this application, such as... Figure 5 As shown, the user sets query conditions (e.g., status = processed, belongProd = financial core system) and adjusts table columns (e.g., hiding the "customer name" column, adjusting the width of the "priority" column) on the front-end page. The user then clicks the "Save Scheme" button to save these changes. The front-end system captures these changes, assembles them into a composite data structure, and sends a POST request (POST / uploadQueryScheme) to the back-end system to save the interface status scheme. The back-end system receives the request from the front-end, verifies the integrity of the data structure, and stores the data in an appropriate database according to the different levels of the data structure. After successful storage, the back-end generates a 200 OK response, confirming that the status data has been properly saved, and displays a successful save on the front-end page. The next day, when the user logs back into the system and selects the previously saved scheme 1, the front-end sends a GET request (GetQuerySchemeByYwkey) to the back-end to retrieve the scheme data corresponding to scheme 1 based on the business identifier (Ywkey). The back-end responds by querying the corresponding scheme data from the database and returning the scheme. This scheme is then applied to the front-end page, ultimately displaying the fully restored page.

[0098] The following example uses code to illustrate this:

[0099] 1. State capture phase (physical process: user operation → data recording):

[0100]

[0101] 2. Data structure assembly (physical process: memory data → network transmission):

[0102]

[0103]

[0104] 3. Server-side storage (physical process: data persistence):

[0105]

[0106]

[0107] 4. State Restoration Phase (Physical Process: Data Parsing → Interface Rendering):

[0108]

[0109]

[0110] In one optional embodiment, in an e-commerce backend management system, operators frequently need to query order data, including 20+ query conditions (order status, payment method, order time, etc.), an order data table with 30+ columns (adjustable column width, hidden columns, sorting, etc.), and dynamically show / hide condition items (such as "logistics company"). Applying this solution based on this context can significantly improve page recovery efficiency. Figure 6 This is a schematic diagram of an optional page processing method applied to an e-commerce order management platform according to an embodiment of this application, such as... Figure 6 As shown, operators set query conditions (e.g., order status = paid, payment method = Alipay) and adjusted table columns on the front-end page (e.g., hiding the "user's mobile number" column and adjusting the width of the "order amount" column). When the user clicks the "Save Scheme" button, the changes are saved. The front-end system captures these changes, assembles them into a composite data structure, and sends a POST request to the back-end system, requesting the saving of the interface status scheme. The back-end system receives the request from the front-end, verifies the integrity of the data structure, and stores the data in an appropriate database based on the different levels of the data structure. Upon successful storage, the back-end generates a 200 OK response, confirming that the status data has been properly saved, and displays a successful save on the front-end page. Later, when operators switch computers and log back into the system, they can directly select the previously saved "Alipay order scheme." The front-end then sends a GET request (Get / order / queryScheme) to the back-end to retrieve the scheme data corresponding to the Alipay order scheme. The back-end responds, queries the corresponding scheme data from the database, returns the scheme, and then applies the scheme to the front-end page, ultimately displaying the fully restored page.

[0111] This application also provides a page processing apparatus. It should be noted that the page processing apparatus of this application can be used to execute the page processing method provided in this application. The page processing apparatus provided in this application is described below.

[0112] According to an embodiment of this application, an apparatus for implementing the above-described page processing method is also provided. Figure 7 This is a schematic diagram of an optional page processing apparatus according to an embodiment of this application, such as... Figure 7 As shown, the device includes: a receiving unit 701, configured to receive a target request from a user on a target page, wherein the target request requests a target page layout scheme stored by the user in a historical time period; an obtaining unit 702, configured to obtain a target data structure corresponding to the target page layout scheme from a server based on the target request, wherein the target data structure stores the page's metadata information, query conditions, display configuration information, and display status of condition items; and an application unit 703, configured to apply the target page layout scheme to the target page based on a target algorithm and the target data structure, wherein the target algorithm identifies the difference information between the target page and the target page layout scheme, and adjusts the target page based on the difference information.

[0113] Optionally, the page processing apparatus further includes: a first receiving unit, a first constructing unit, and a first sending unit. The first receiving unit is used to receive a user's save instruction, wherein the save instruction is used to save the user's modifications on the target page; the first constructing unit is used to construct a target data structure based on the modifications after receiving the save instruction; and the first sending unit is used to send the target data structure to the server for storage.

[0114] Optionally, the page processing device further includes: a first-layer structure, wherein the first-layer structure is used to store metadata information of the target page layout scheme, wherein the metadata information includes the scheme name, business identifier, and version identifier of the target page layout scheme; a second-layer structure, wherein the second-layer structure is used to store query conditions of the target page layout scheme, wherein the query conditions are used to represent data filtering information set by the user on the target page; a third-layer structure, wherein the third-layer structure is used to store display configuration information of the target page layout scheme, wherein the display configuration information is used to represent page layout information set by the user on the target page; and a fourth-layer structure, wherein the fourth-layer structure is used to store the display status of the condition items in the target page layout scheme.

[0115] Optionally, the page processing device further includes: a first listening unit, a first detection unit, and a first processing unit. The first listening unit is used to listen for target events at the table container level in the target page, wherein the target events are used to capture dynamic changes in the table; the first detection unit is used to detect N change information points of the table at preset time intervals based on the target events, wherein N is an integer greater than or equal to 1; the first processing unit is used to aggregate the N change information points when N change information points of the table are detected within the preset time interval, and store the aggregated N change information points locally.

[0116] Optionally, the application unit 703 includes: a first detection subunit, a first application subunit, a first update subunit, and a second application subunit. The first detection subunit is used to detect whether the system identifier in the version identifier corresponding to the target data structure is the same as the target identifier stored on the server. The first application subunit is used to apply the target page layout scheme on the target page based on the target algorithm and the target data structure when the system identifier and target identifier are detected to be the same. The first update subunit is used to update the target data structure based on the first algorithm when the system identifier and target identifier are detected to be different, wherein the first algorithm is used to adjust the format of information in the target data structure. The second application subunit is used to apply the target page layout scheme on the target page based on the updated target data and the target algorithm.

[0117] Optionally, the second application subunit includes: a first determining module and a first application module. The first determining module is used to obtain the updated target data structure from the server and determine the difference information between the page state of the target page and the target data structure based on the target algorithm; the first application module is used to apply the target page layout scheme to the target page based on the difference information.

[0118] Optionally, the first sending unit includes: a first storage subunit, used to store information in the target data structure into a first database and a second database on the server according to user requirements; wherein, the first database is an in-memory database and the second database is a relational database, the first database is used to store information in the target data structure whose access frequency is greater than or equal to a first preset threshold, and the second database is used to store information in the target data structure whose change frequency is less than a second preset threshold.

[0119] According to another aspect of this application, a computer-readable storage medium is also provided, which includes a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the page processing method described above.

[0120] According to another aspect of this application, an electronic device is also provided, including one or more processors and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform the page processing method described above.

[0121] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0122] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

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

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

[0125] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0126] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0127] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A page processing method, characterized in that, include: Receive a target request from a user on a target page, wherein the target request is used to request a target page layout scheme stored by the user in a historical time period; Based on the target request, the target data structure corresponding to the target page layout scheme is obtained from the server. The target data structure is used to store the page's metadata information, query conditions, display configuration information, and display status of the condition items. Based on the target algorithm, the target page layout scheme is applied to the target page according to the target data structure, wherein the target algorithm is used to identify the difference information between the target page and the target page layout scheme, and adjust the target page based on the difference information; The metadata information includes the scheme name, business identifier, and version identifier of the target page layout scheme; The version identifier includes a system identifier. Based on the target algorithm, the target page layout scheme is applied to the target page according to the target data structure, including: The system identifier in the version identifier corresponding to the target data structure is checked to see if it is the same as the target identifier stored on the server. When the system identifier is found to be the same as the target identifier, the target page layout scheme is applied to the target page according to the target data structure based on the target algorithm. When the system identifier is found to be different from the target identifier, the target data structure is updated according to the first algorithm, wherein the first algorithm is used to adjust the format of the information in the target data structure. Based on the target algorithm, the target page layout scheme is applied to the target page according to the updated target data structure.

2. The page processing method according to claim 1, characterized in that, Before receiving the user's target request on the target page, the method further includes: Receive the user's save instruction, wherein the save instruction is used to save the user's modification operation on the target page; After receiving the save instruction, the target data structure is constructed based on the modification operation; The target data structure is sent to the server for storage.

3. The page processing method according to claim 1, characterized in that, The target data structure includes at least the following structures: The first layer structure is used to store metadata information of the target page layout scheme; The second layer structure is used to store the query conditions of the target page layout scheme, wherein the query conditions are used to characterize the data filtering information set by the user on the target page; The third layer structure is used to store the display configuration information of the target page layout scheme, wherein the display configuration information is used to represent the page layout information set by the user on the target page; The fourth layer structure is used to store the display status of the condition items in the target page layout scheme.

4. The page processing method according to claim 1, characterized in that, The method further includes: In the target page, the table container layer listens for target events, wherein the target events are used to capture dynamic changes in the table; The table is checked for N changes at preset intervals for the target event, where N is an integer greater than or equal to 1. When the table detects N changes within a preset time period, the N changes are aggregated and stored locally.

5. The page processing method according to claim 1, characterized in that, Based on the target algorithm, the target page layout scheme is applied to the target page according to the updated target data structure, including: The updated target data structure is obtained from the server, and the difference information between the page state of the target page and the target data structure is determined based on the target algorithm. Based on the difference information, the target page layout scheme is applied to the target page.

6. The page processing method according to claim 2, characterized in that, Sending the target data structure to the server for storage includes: Based on user requirements, the information in the target data structure is stored in the first database and the second database on the server, respectively; The first database is an in-memory database, and the second database is a relational database. The first database is used to store information in the target data structure whose access frequency is greater than or equal to a first preset threshold, and the second database is used to store information in the target data structure whose change frequency is less than a second preset threshold.

7. A page processing apparatus, characterized in that, include: A receiving unit is configured to receive a target request from a user on a target page, wherein the target request is used to request a target page layout scheme stored by the user in a historical time period; The acquisition unit is used to acquire the target data structure corresponding to the target page layout scheme from the server based on the target request, wherein the target data structure is used to store the page's metadata information, query conditions, display configuration information, and display status of the condition items; An application unit is used to apply the target page layout scheme to the target page based on the target algorithm and the target data structure, wherein the target algorithm is used to identify the difference information between the target page and the target page layout scheme, and adjust the target page based on the difference information; The metadata information includes the scheme name, business identifier, and version identifier of the target page layout scheme; The version identifier includes a system identifier, and the application unit is further used for: The system identifier in the version identifier corresponding to the target data structure is checked to see if it is the same as the target identifier stored on the server. When the system identifier is found to be the same as the target identifier, the target page layout scheme is applied to the target page according to the target data structure based on the target algorithm. When the system identifier is found to be different from the target identifier, the target data structure is updated according to the first algorithm, wherein the first algorithm is used to adjust the format of the information in the target data structure. Based on the target algorithm, the target page layout scheme is applied to the target page according to the updated target data structure.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein when the computer program is executed, the device on which the computer-readable storage medium is located performs the page processing method according to any one of claims 1 to 6.

9. An electronic device, characterized in that, It includes one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to perform the page processing method according to any one of claims 1 to 6.

Images