A page management method and device, electronic equipment and storage medium

Abstract

The application discloses a page management method, device and equipment and a storage medium. The method comprises the following steps: if a page stack virtualization trigger condition is detected to be met, acquiring resource location identifiers of each page in the page stack; generating a virtual stack matched with the page stack according to the resource location identifiers of the pages, so as to acquire association relationship information between the pages through the virtual stack when a page return operation of a mobile terminal is detected; and removing the pages in the page stack that meet the virtualization condition from the page stack. The technical scheme solves the problem of memory crash caused by too many page stack levels, can effectively avoid the memory crash phenomenon, ensures that the pages are returned in the access order when the return operation is performed, and is beneficial to improving the access experience of users.

Description

Technical Field

[0001] This invention relates to the field of Internet technology, and in particular to a page management method, apparatus, electronic device, and storage medium. Background Technology

[0002] Mobile applications are typically hybrid page applications, which can include native pages, Weex pages, Flutter pages, and H5 pages developed based on different frameworks. Among hybrid pages, Weex pages consume a lot of memory, and the deeper the page hierarchy accessed by the user, the more prone they are to memory crashes.

[0003] To avoid memory crashes, existing technologies offer two solutions: (1) Limiting the number of pages in the page stack: By controlling the number of access levels, excessive pages in the page stack can be prevented. (2) Page reuse: Before opening a new page, it is determined whether the same page exists in the page stack. If it does, the page is reused.

[0004] However, with the method of limiting the number of pages in the page stack, when the page stack reaches its maximum level, continuing to access a new page requires deleting existing pages from the stack to meet the page level limit. Therefore, when a user triggers a back operation, pages cannot be returned level by level in the order they were accessed. For the page reuse method, memory growth is still unavoidable when the accessed page is different from the pages in the page stack. Summary of the Invention

[0005] This invention provides a page management method, apparatus, device, and storage medium to solve the memory crash problem caused by excessive page stack levels. It can effectively avoid memory crashes while ensuring that pages are returned level by level in the order of access during return operations, which helps to improve the user's access experience.

[0006] According to one aspect of the present invention, a page management method is provided, the method comprising:

[0007] If the page stack virtualization trigger condition is detected to be met, the resource location identifier of each page in the page stack is obtained.

[0008] Based on the resource location identifiers of each page, a virtual stack matching the page stack is generated so that when a page return operation is detected on the mobile terminal, the association information between pages can be obtained through the virtual stack.

[0009] Remove pages that meet the virtualization conditions from the page stack.

[0010] According to another aspect of the present invention, a page management device is provided, the device comprising:

[0011] The location identifier acquisition module is used to acquire the resource location identifiers of each page in the page stack if the page stack virtualization trigger condition is met.

[0012] The virtual stack generation module is used to generate a virtual stack matching the page stack based on the resource location identifier of each page, so as to obtain the association information between pages through the virtual stack when a page return operation of the mobile terminal is detected.

[0013] The page removal module is used to remove pages that meet the virtualization conditions from the page stack.

[0014] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0015] At least one processor; and

[0016] A memory communicatively connected to the at least one processor; wherein,

[0017] The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the page management method according to any embodiment of the present invention.

[0018] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the page management method described in any embodiment of the present invention.

[0019] The technical solution of this invention, upon detecting a page stack virtualization trigger condition, obtains the resource location identifiers of each page in the page stack. Then, based on the resource location identifiers of each page, a virtual stack matching the page stack is generated. When a page return operation is detected on the mobile terminal, the association information between pages is obtained through the virtual stack. Finally, pages that meet the virtualization conditions are removed from the page stack. This technical solution solves the memory crash problem caused by excessive page stack levels. It can effectively avoid memory crashes while ensuring that pages return sequentially in the access order during return operations, thus improving the user experience.

[0020] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

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

[0022] Figure 1 This is a flowchart of a page management method provided according to Embodiment 1 of the present invention;

[0023] Figure 2A This is a flowchart of a page management method provided according to Embodiment 2 of the present invention;

[0024] Figure 2B This is a schematic diagram of page management provided according to Embodiment 2 of the present invention;

[0025] Figure 3 This is a schematic diagram of the structure of a page management device according to Embodiment 3 of the present invention;

[0026] Figure 4 This is a schematic diagram of the structure of an electronic device that implements the page management method of this invention. Detailed Implementation

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

[0028] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention 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 used interchangeably where appropriate so that the embodiments of the invention 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 device 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 devices. The acquisition, storage, use, and processing of data in the technical solutions of this application all comply with the relevant provisions of national laws and regulations.

[0029] Example 1

[0030] Figure 1 The flowchart illustrates a page management method according to Embodiment 1 of the present invention, which is applicable to page management scenarios on mobile devices. This method can be executed by a page management device, which can be implemented in hardware and / or software and can be configured in an electronic device.

[0031] like Figure 1 As shown, the method includes:

[0032] S110. If the page stack virtualization trigger condition is met, obtain the resource location identifier of each page in the page stack.

[0033] This solution can be executed by mobile terminals such as smartphones and tablets. When a user accesses a page in an application deployed on the mobile terminal, the mobile terminal pushes that page onto the application's corresponding page stack. The mobile terminal can determine whether the current page stack poses a memory crash risk based on the page stack virtualization trigger conditions. If the page stack virtualization trigger conditions are met, the current page stack is at risk of memory crash; if the page stack virtualization trigger conditions are not met, the current page stack is not at risk of memory crash. When the current page stack meets the page stack virtualization trigger conditions, the mobile terminal can sequentially read the resource location identifiers of each page in the page stack to construct a virtual stack based on these identifiers.

[0034] In this scheme, optionally, the page stack virtualization triggering condition includes at least one of the following:

[0035] A request to clear storage space from the mobile terminal has been received.

[0036] A page access operation from a mobile terminal is detected, and the number of remaining pages in the page stack is less than or equal to a preset capacity threshold.

[0037] A page access operation from a mobile terminal is detected, and the remaining page storage space in the page stack is less than or equal to a preset storage space threshold.

[0038] Understandably, users can manually trigger the cleanup of the current application's page stack storage space, for example, by clicking the storage space cleanup button. The mobile terminal's application frontend can generate a storage space cleanup request and send it to the mobile terminal's application backend. After receiving the storage space cleanup request, the application backend starts the page stack virtualization task. Too many pages in the page stack and too large a page storage space can easily lead to page stack memory crashes. Therefore, after detecting a page access operation, the mobile terminal can determine whether the number of remaining pages in the page stack is less than or equal to a preset capacity threshold. If the number of remaining pages is less than or equal to the preset capacity threshold, the page stack is at risk of memory crashing, and the page stack virtualization task can be started. The mobile terminal can also start the page stack virtualization task when both the number of remaining pages and the remaining page storage space are less than or equal to the preset capacity threshold.

[0039] This solution can effectively avoid page stack memory crashes and promptly implement page virtualization measures. Specifically, it uses a virtual stack to store the resource location identifiers of each page in the page stack and removes removable pages from the page stack to provide sufficient memory space for storing newly accessed pages by users.

[0040] S120. Based on the resource location identifiers of each page, generate a virtual stack matching the page stack, so as to obtain the association information between pages through the virtual stack when a page return operation of the mobile terminal is detected.

[0041] Mobile terminals can generate a virtual stack that matches the page stack based on the resource location identifiers of each page and their arrangement in the page stack. Specifically, the mobile terminal can pre-create a blank stack, and then push the resource location identifiers of each page into the blank stack according to the order of the pages in the page stack, thus obtaining the virtual stack that matches the page stack. In simple terms, the virtual stack stores the relationship information between the pages in the page stack, such as the access order between pages, which can provide a basis for responding to the user's page return operation.

[0042] S130. Remove the pages that meet the virtualization conditions from the page stack.

[0043] After obtaining a matching virtual stack, the mobile terminal can remove virtualizable pages from the page stack to reduce the memory space occupied by the page stack. The virtualization condition can be a non-identical page that supports virtualization. Identical pages can include pages that represent page stack attributes, such as the bottom page and top page. Non-identical pages can be any pages in the page stack other than the iconic pages.

[0044] It should be noted that page virtualization in the page stack can apply to all pages in the stack, or it can apply only to pages of a preset page type, such as Weex pages. Therefore, the virtualization condition can also include the preset page type, and the mobile terminal can virtualize pages of the preset page type according to the virtualization condition.

[0045] In one feasible solution, removing pages that meet the virtualization conditions from the page stack includes:

[0046] If the current page is a preset page in the page stack, then the current page does not meet the virtualization conditions; wherein, the preset page includes the bottom page of the stack, the top page of the stack, and the adjacent pages of the top page of the stack.

[0047] Specifically, the mobile terminal can sequentially determine the virtualization conditions for each page in the page stack and remove pages that meet the virtualization conditions from the page stack. If the current page is a preset marker page in the page stack, such as the bottom page, the top page, or a page adjacent to the top page, then it is determined that the current page does not meet the virtualization conditions.

[0048] In another feasible solution, removing pages that meet the virtualization conditions from the page stack includes:

[0049] If the current page is not a preset page in the page stack, the configuration information of the current page is obtained, and the virtualization condition judgment result of the current page is determined based on the configuration information of the current page.

[0050] If the current page is not a pre-defined landmark page in the page stack, the mobile terminal can obtain the configuration information of the current page and determine whether the current page meets the virtualization conditions based on the configuration information. The configuration information may include page structure, page content, and page functionality. Based on the page structure, page content, and page functionality, the mobile terminal can determine whether the current page can be virtualized. For example, if the page content includes user-entered information, then the current page cannot be virtualized.

[0051] This solution can determine whether the current page can be virtualized based on its configuration information. It can retain pages closely related to the user in the page stack, which helps to provide a better user experience.

[0052] Based on the above scheme, optionally, the configuration information includes virtualization configuration items;

[0053] The step of determining the virtualization condition judgment result of the current page based on the configuration information of the current page includes:

[0054] If the virtualization configuration options on the current page indicate that the current page supports virtualization, then the current page meets the virtualization requirements.

[0055] If the virtualization configuration options on the current page indicate that the current page does not support virtualization, then the current page does not meet the virtualization requirements.

[0056] As is easily understood, the page's configuration information can include virtualization configuration items, allowing page developers to define whether the page supports virtualization. If the current page's virtualization configuration items determine that it supports virtualization, then the current page meets the virtualization requirements; conversely, if the current page's virtualization configuration items determine that it does not support virtualization, then the current page does not meet the virtualization requirements.

[0057] It should be noted that virtualization configuration options can include whether virtualization is supported, as well as virtualization priority. Mobile terminals can determine which pages to remove based on their virtualization priority within the page stack, thus achieving hierarchical management of the pages in the stack.

[0058] The technical solution of this invention, upon detecting a page stack virtualization trigger condition, obtains the resource location identifiers of each page in the page stack. Then, based on the resource location identifiers of each page, a virtual stack matching the page stack is generated. When a page return operation is detected on the mobile terminal, the association information between pages is obtained through the virtual stack. Finally, pages that meet the virtualization conditions are removed from the page stack. This technical solution solves the memory crash problem caused by excessive page stack levels. It can effectively avoid memory crashes while ensuring that pages return sequentially in the access order during return operations, thus improving the user experience.

[0059] Example 2

[0060] Figure 2A This is a flowchart of a page management method provided in Embodiment 2 of the present invention. This embodiment is based on the above embodiment and refines the page return process. Figure 2A As shown, the method includes:

[0061] S210. If the page stack virtualization trigger condition is met, obtain the resource location identifier of each page in the page stack.

[0062] S220. Generate a virtual stack matching the page stack based on the resource location identifier of each page.

[0063] S230. Remove the pages that meet the virtualization conditions from the page stack.

[0064] S240. If a page return operation of the mobile terminal is detected, the return page is determined according to the top page in the page stack.

[0065] Understandably, the top page of the page stack is usually the page currently displayed on the mobile terminal. After removing pages that meet the virtualization conditions from the page stack, if the user is detected to be performing a page return operation through the mobile terminal, the mobile terminal can use the next page after the top page of the page stack as the return page and jump to the return page.

[0066] S250: Obtain the resource location identifier of the previous accessed page from the virtual stack.

[0067] After receiving the returned page, in order to ensure that the user's next page return operation can be responded to in a timely and accurate manner, the mobile terminal can obtain the resource location identifier of the previous page visited in the virtual stack based on the resource location identifier of the returned page.

[0068] S260. Based on the resource location identifier, load the previously accessed page and place the previously accessed page at the target position in the page stack.

[0069] Based on the resource location identifier of the previously visited page, the mobile terminal can load the previously visited page and, after loading is complete, place the previously visited page at the target position in the page stack. The target position can be the page following the page to be returned.

[0070] Optionally, in this solution, placing the previously accessed page at the target position in the page stack includes:

[0071] Determine the target location based on the position of the returned page in the page stack;

[0072] Place the previously accessed page at the target location.

[0073] Specifically, the mobile terminal can determine the position of the return page in the page stack, pop the return page from the stack, push the previously visited page onto the page stack, and then push the return page onto the page stack again, so that the previously visited page is below the return page.

[0074] Figure 2B This is a schematic diagram of page management according to Embodiment 2 of the present invention. Figure 2B In the specific example shown, before the page stack virtualization trigger condition is met, there are 5 pages in the page stack, pages 1 through 5. Before the user pushes the newly accessed page 6 onto the page stack, the mobile terminal detects that if page 6 is pushed onto the page stack, the page stack faces the risk of memory crash. Therefore, based on the resource location identifiers of each page in the page stack, such as the URL (Uniform Resource Identifier), the page stack is constructed. Figure 2B The virtual stack corresponding to the page stack in the middle stage ( Figure 2B (Mid-stage one virtual stack). For example Figure 2B As shown in Phase Two, after constructing the virtual stack, the mobile terminal can remove pages 2-3 from the page stack that meet the virtualization conditions to provide sufficient memory space to push page 6 onto the page stack. Simultaneously, the mobile terminal pushes the resource location identifier of page 6 onto the virtual stack. After page 6 is pushed onto the page stack, page 4 is no longer an adjacent page to the top page, thus meeting the virtualization conditions and can be removed from the page stack.

[0075] like Figure 2B In Phase 3, before detecting a page back operation, the user is currently accessing page 6. After detecting the page back operation, page 6 is removed from the page stack, and the user now wants to access page 5. The mobile terminal can determine page 5 as the page to return to. At this time, page 5 is the top page of the page stack. To ensure smooth page loading during the page back process, the mobile terminal can determine the previous accessed page of page 5 as page 4 in the virtual stack, obtain the resource location identifier of page 4, load page 4 according to the resource location identifier of page 4, and place page 4 below page 5 in the page stack so that page 4 can be provided in a timely manner during the next page back.

[0076] The technical solution of this invention, upon detecting that the page stack virtualization trigger condition is met, obtains the resource location identifiers of each page in the page stack, then generates a virtual stack matching the page stack based on the resource location identifiers of each page, and finally removes the pages in the page stack that meet the virtualization condition from the page stack. This technical solution solves the memory crash problem caused by too many page stack levels. It can effectively avoid memory crashes while ensuring that pages are returned level by level in the access order during return operations, which is beneficial to improving the user's access experience.

[0077] Example 3

[0078] Figure 3 This is a schematic diagram of a page management device provided in Embodiment 3 of the present invention. Figure 3As shown, the device includes:

[0079] The location identifier acquisition module 310 is used to acquire the resource location identifier of each page in the page stack if the page stack virtualization trigger condition is detected to be met.

[0080] The virtual stack generation module 320 is used to generate a virtual stack matching the page stack according to the resource location identifier of each page, so as to obtain the association information between pages through the virtual stack when the page return operation of the mobile terminal is detected.

[0081] The page removal module 330 is used to remove pages that meet the virtualization conditions from the page stack.

[0082] Optionally, in this solution, the device may further include:

[0083] The return page determination module is used to determine the return page based on the top page of the page stack after removing pages that meet the virtualization conditions from the page stack.

[0084] The previous page identifier acquisition module is used to acquire the resource location identifier of the previous accessed page of the returned page in the virtual stack;

[0085] The previous access page placement module is used to load the previous access page according to the resource location identifier and place the previous access page at the target position in the page stack.

[0086] Based on the above solution, optionally, the previous access page placement module is specifically used for:

[0087] Determine the target location based on the position of the returned page in the page stack;

[0088] Place the previously accessed page at the target location.

[0089] In this embodiment, optionally, the page stack virtualization triggering condition includes at least one of the following:

[0090] A request to clear storage space from the mobile terminal has been received.

[0091] A page access operation from a mobile terminal is detected, and the number of remaining pages in the page stack is less than or equal to a preset capacity threshold.

[0092] A page access operation from a mobile terminal is detected, and the remaining page storage space in the page stack is less than or equal to a preset storage space threshold.

[0093] In one feasible solution, optionally, the page removal module 330 is further configured to:

[0094] If the current page is a preset page in the page stack, then the current page does not meet the virtualization conditions; wherein, the preset page includes the bottom page of the stack, the top page of the stack, and the adjacent pages of the top page of the stack.

[0095] Optionally, based on the above solution, the page removal module 330 is further configured to:

[0096] If the current page is not a preset page in the page stack, the configuration information of the current page is obtained, and the virtualization condition judgment result of the current page is determined based on the configuration information of the current page.

[0097] In a preferred embodiment, the configuration information includes virtualization configuration items;

[0098] The page removal module 330 is specifically used for:

[0099] If the virtualization configuration options on the current page indicate that the current page supports virtualization, then the current page meets the virtualization requirements.

[0100] If the virtualization configuration options on the current page indicate that the current page does not support virtualization, then the current page does not meet the virtualization requirements.

[0101] The page management device provided in the embodiments of the present invention can execute the page management method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of executing the method.

[0102] Example 4

[0103] Figure 4 A schematic diagram of an electronic device 410 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0104] like Figure 4As shown, the electronic device 410 includes at least one processor 411 and a memory, such as a read-only memory (ROM) 412 or a random access memory (RAM) 413, communicatively connected to the at least one processor 411. The memory stores computer programs executable by the at least one processor. The processor 411 can perform various appropriate actions and processes based on the computer program stored in the ROM 412 or loaded from storage unit 418 into the RAM 413. The RAM 413 may also store various programs and data required for the operation of the electronic device 410. The processor 411, ROM 412, and RAM 413 are interconnected via a bus 414. An input / output (I / O) interface 415 is also connected to the bus 414.

[0105] Multiple components in electronic device 410 are connected to I / O interface 415, including: input unit 416, such as keyboard, mouse, etc.; output unit 417, such as various types of displays, speakers, etc.; storage unit 418, such as disk, optical disk, etc.; and communication unit 419, such as network card, modem, wireless transceiver, etc. Communication unit 419 allows electronic device 410 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0106] Processor 411 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 411 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 411 performs the various methods and processes described above, such as page management methods.

[0107] In some embodiments, the page management method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 418. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 410 via ROM 412 and / or communication unit 419. When the computer program is loaded into RAM 413 and executed by processor 411, one or more steps of the page management method described above may be performed. Alternatively, in other embodiments, processor 411 may be configured to perform the page management method by any other suitable means (e.g., by means of firmware).

[0108] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transferring data and instructions to the storage system, the at least one input device, and the at least one output device.

[0109] Computer programs used to implement the methods of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to the processor of a general-purpose computer, a special-purpose computer, or other programmable page management device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer programs can be executed entirely on the machine, partially on the machine, as a standalone software package partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0110] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0111] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0112] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0113] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0114] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0115] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A page management method, characterized in that, The method includes: If the page stack virtualization trigger condition is detected to be met, the resource location identifier of each page in the page stack is obtained. Based on the resource location identifiers of each page, a virtual stack matching the page stack is generated so that when a page return operation is detected on the mobile terminal, the association information between pages can be obtained through the virtual stack. Remove pages that meet the virtualization conditions from the page stack; After removing pages that meet the virtualization conditions from the page stack, the method further includes: If a page return operation is detected on the mobile terminal, the return page is determined based on the top page in the page stack; wherein, the top page in the page stack is the page currently displayed on the mobile terminal. Obtain the resource location identifier of the previously accessed page from the virtual stack; Based on the resource location identifier, load the previously accessed page and place the previously accessed page at the target position in the page stack; The step of removing pages that meet the virtualization conditions from the page stack includes: If the current page is a preset page in the page stack, then it is determined that the current page does not meet the virtualization conditions, and the current page is retained in the page stack; wherein, the preset page includes the bottom page of the stack, the top page of the stack, and the adjacent page of the top page of the stack; If the current page is not a preset page in the page stack, then obtain the configuration information of the current page; If the current page is determined to support virtualization based on its virtualization configuration options, then the current page meets the virtualization requirements, and the current page is removed from the page stack. If it is determined that the current page does not support virtualization based on the virtualization configuration items of the current page, then the current page does not meet the virtualization conditions, and the current page is retained in the page stack; wherein, the configuration information includes virtualization configuration items.

2. The method according to claim 1, characterized in that, The step of placing the previously accessed page at the target position in the page stack includes: Determine the target location based on the position of the returned page in the page stack; Place the previously accessed page at the target location.

3. The method according to claim 1, characterized in that, The page stack virtualization triggering condition includes at least one of the following: A request to clear storage space from the mobile terminal has been received. A page access operation from a mobile terminal is detected, and the number of remaining pages in the page stack is less than or equal to a preset capacity threshold. A page access operation from a mobile terminal is detected, and the remaining page storage space in the page stack is less than or equal to a preset storage space threshold.

4. A page management device, characterized in that, include: The location identifier acquisition module is used to acquire the resource location identifiers of each page in the page stack if the page stack virtualization trigger condition is met. The virtual stack generation module is used to generate a virtual stack matching the page stack based on the resource location identifier of each page, so as to obtain the association information between pages through the virtual stack when a page return operation of the mobile terminal is detected. A page removal module is used to remove pages that meet the virtualization conditions from the page stack. The device further includes: The return page determination module is used to determine the return page based on the top page of the page stack after removing pages that meet the virtualization conditions from the page stack; wherein, the top page of the page stack is the currently displayed page of the mobile terminal. The previous page identifier acquisition module is used to acquire the resource location identifier of the previous accessed page of the returned page in the virtual stack; The previous access page placement module is used to load the previous access page according to the resource location identifier and place the previous access page at the target position of the page stack; The page removal module is used for: If the current page is a preset page in the page stack, then it is determined that the current page does not meet the virtualization conditions, and the current page is retained in the page stack; wherein, the preset page includes the bottom page of the stack, the top page of the stack, and the adjacent page of the top page of the stack; If the current page is not a preset page in the page stack, the configuration information of the current page is obtained, and the virtualization condition judgment result of the current page is determined based on the configuration information of the current page; the configuration information includes virtualization configuration items. If the current page is determined to support virtualization based on its virtualization configuration options, then the current page meets the virtualization requirements, and the current page is removed from the page stack. If the virtualization configuration options of the current page determine that the current page does not support virtualization, then the current page does not meet the virtualization conditions, and the current page is retained in the page stack.

5. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the page management method according to any one of claims 1-3.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the page management method according to any one of claims 1-3.

Images