A page management method, medium, and device

Abstract

This application relates to the field of software technology, and more particularly to a page management method, medium, and device. The method includes: a page management component running after application startup, monitoring the application's page stack; the page management component determining the changed page indicated by the monitored page stack change information; the page management component performing the same push-pop operations on the page attribute information corresponding to the changed page in the page attribute stack of the page management component; and the page attribute information in the page attribute stack being used when the application performs cross-system page navigation. In this method, a page attribute stack is established to store page attribute information. This allows the page attributes of the changed page indicated by the change information to be set when the page stack changes, thereby achieving synchronization between the page and page attributes, ensuring that the page can still function normally after each page change.

Description

Technical Field

[0001] This application relates to the field of software technology, and more particularly to a page management method, medium, and device. Background Technology

[0002] In recent years, with the increase in payment methods, traditional bank card payment methods have been greatly impacted. In order to make payment more convenient for users and adapt to various scenarios, UnionPay has implemented unified management of payment methods of banks and other financial institutions.

[0003] One implementation involves integrating banking institutions into the Cloud Network Software Development Kit (SDK). In this approach, a payment and other application functions are completed through navigation between the bank's webpage and the Cloud Network SDK page. As more and more banking institutions integrate the Cloud Network SDK, the interaction between the SDK and the system pages of these institutions becomes increasingly complex. Current technology uses the recording of the previous page's attribute information at the page level to enable page navigation and backtracking. However, since the bank's webpage and the Cloud Network SDK page belong to different systems, the Cloud Network SDK page cannot determine whether the bank's webpage has recorded its attribute information during navigation. If not, a forced navigation or backtracking will result in attribute conflicts, rendering the page unusable.

[0004] Therefore, there is an urgent need for a page management method, medium, and device to ensure the normal operation of pages. Summary of the Invention

[0005] This application provides a page management method, medium, and device to ensure the normal operation of a page.

[0006] In a first aspect, embodiments of this application provide a page management method, the method comprising: a page management component running after an application starts, monitoring the page stack of the application; the page stack being used to sequentially store pages running in the application; the page management component determining a changed page indicated by the monitored change information of the page stack; the page management component performing the same push and pop operations on the page attribute information corresponding to the changed page in the page attribute stack of the page management component; and each page attribute information in the page attribute stack being used when the application performs cross-system page navigation.

[0007] The above method establishes a page attribute stack to store page attribute information. This allows the page attributes of the changed page, as indicated by the change information, to be set when the page stack changes, thus achieving synchronization between the page and its attributes. Furthermore, any changes in the page stack are monitored; therefore, when a page in the stack changes multiple times consecutively, its page attributes will also change accordingly. This ensures that operations on the page function correctly after each change.

[0008] In one possible implementation, the page management component determines the changed page indicated by the change information based on the monitored changes in the page stack, including: if the page management component detects that the change information in the page stack indicates the addition of a first page, then it determines that the second page displayed by the application is the changed page indicated by the change information; the page management component performs the same push and pop operations on the page attribute information corresponding to the changed page in the page attribute stack of the page management component, including: the page management component obtains the page attribute information of the second page from the application; and performs a push operation on the page attribute information of the second page in the page attribute stack of the page management component.

[0009] By employing the above method, when a page is added to the page stack, its corresponding attribute information is added to the attribute stack. On one hand, when navigating between pages, the attribute information of the previous page is saved promptly, preventing the loss of existing page attributes after the page disappears or its attributes change, thus ensuring a smooth transition back to the original page. On the other hand, storing the attribute information of the newly added page in the page attribute stack during page navigation ensures that page navigation and returning are normal even when an invisible page is added between two pages, making the page management component more compatible.

[0010] In one possible implementation, the page management component determines the changed page indicated by the monitored page stack change information, including: if the page management component detects that the page stack change information indicates the deletion of a third page, then the page indicated by the change information is the third page; the page management component performs the same push and pop operations on the page attribute information corresponding to the changed page in the page attribute stack of the page management component, including: the page management component performs a pop operation on the page attribute information of the third page in the page attribute stack of the page management component.

[0011] By using the above method, changes in the page attribute stack can be adjusted promptly based on changes in the page stack. When a page is deleted, the attribute information in the page attribute stack is promptly removed. This saves storage space in the page attribute stack and makes it easier to obtain target page attribute information by removing unused attribute information.

[0012] In one possible implementation, the page management component determines the changed page indicated by the change information based on the monitored changes in the page stack, including: if the page management component detects that the fourth page has been replaced by the fifth page, then it determines that the changed pages indicated by the change information are the fourth page and the fifth page; the page management component performs the same push and pop operations on the page attribute information corresponding to the changed page in the page attribute stack of the page management component, including: after performing a pop operation on the page attribute information of the fourth page in the page attribute stack of the page management component, the page management component performs a push operation on the page attribute information of the fifth page.

[0013] By using the above method, after a page is replaced by another page, the attribute information in the page attribute stack corresponding to this page is also replaced, thereby ensuring the synchronization between page attribute information and the page, and thus ensuring that the page attribute settings match the current page.

[0014] In one possible implementation, the method further includes: the page management component listening for cross-system page navigation operations of the application; the cross-system page navigation operation indicating navigation to a sixth page; the page management component obtaining the page attribute information of the sixth page through the page attribute stack; and the page management component pushing the page attribute information of the sixth page to the application. The page management component obtaining the page attribute information of the sixth page through the page attribute stack includes: the page management component performing a pop operation on page attribute information following the page attribute information of the sixth page in the page attribute stack until the page attribute information of the sixth page is obtained.

[0015] By employing the above method, in a stack-based storage system, unwanted page attribute information is popped from the stack while the required page attribute information is retrieved. This saves space in the page attribute stack and makes retrieving the necessary page attribute information more convenient.

[0016] In one possible implementation, the method further includes: after obtaining the page attribute information of the sixth page, the method further includes: sequentially pushing the page attribute information following the page attribute information of the sixth page onto the page attribute stack.

[0017] By using the above method, the information stored in the stack storage structure can be consistent with the actual page jump process, thus making it more convenient to perform pop and push operations during page jumps.

[0018] Secondly, embodiments of this application provide another page management method, the method including an application obtaining a cross-system page jump operation triggered by a user; the cross-system page jump operation is used to indicate a jump to a sixth page; the application obtains the sixth page from the application's page stack, and obtains the page attribute information of the sixth page based on the page attribute stack of the page management component; the application displays the sixth page according to the sixth page and the page attribute information of the sixth page.

[0019] Thirdly, embodiments of this application provide a page management component, which is used to run after the application starts and monitor the page stack of the application; the page stack is used to sequentially store the pages running in the application; the page management component is further used to determine the changed page indicated by the change information based on the monitored change information of the page stack; the page management component is further used to perform the same push and pop operations on the page attribute information corresponding to the changed page in the page attribute stack of the page management component as on the page stack; each page attribute information in the page attribute stack is used when the application performs cross-system page navigation.

[0020] In one possible implementation, the page management component is specifically configured to, upon detecting a change in the page stack indicating the addition of a first page, determine that the second page displayed by the application is the changed page indicated by the change information; the page management component is further configured to obtain page attribute information of the second page from the application; and perform a push operation on the page attribute information of the second page in the page attribute stack of the page management component.

[0021] In one possible implementation, the page management component is specifically used to, upon detecting a change in the page stack indicating the deletion of a third page, determine that the changed page indicated by the change information is the third page; the page management component is further used to, in the page attribute stack of the page management component, perform a pop operation on the page attribute information of the third page.

[0022] In one possible implementation, the page management component is specifically configured to, upon detecting a change in the page stack where the fourth page is replaced by the fifth page, determine that the changed pages indicated by the change information are the fourth page and the fifth page; the page management component is further configured to, in the page attribute stack of the page management component, perform a pop operation on the page attribute information of the fourth page and then perform a push operation on the page attribute information of the fifth page.

[0023] In one possible implementation, the page management component is further configured to listen for cross-system page navigation operations of the application; the cross-system page navigation operation is used to indicate navigation to the sixth page; the page management component obtains the page attribute information of the sixth page through the page attribute stack; and pushes the page attribute information of the sixth page to the application.

[0024] In one possible implementation, the page management component is specifically used to pop page attribute information from the page attribute stack that is located after the page attribute information of the sixth page, until the page attribute information of the sixth page is obtained.

[0025] In one possible implementation, the page management component is further configured to sequentially push page attribute information following the page attribute information of the sixth page onto the page attribute stack.

[0026] Fourthly, this application provides an application for: obtaining a cross-system page jump operation triggered by a user; the cross-system page jump operation is used to indicate a jump to a sixth page; obtaining the sixth page from the page stack of the application, and obtaining the page attribute information of the sixth page based on the page attribute stack of the page management component; and displaying the sixth page according to the sixth page and the page attribute information of the sixth page.

[0027] Fifthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when run, performs any one of the methods described in the first and second aspects above.

[0028] In a sixth aspect, embodiments of this application provide a computing device, including: a memory for storing program instructions; and a processor for calling the program instructions stored in the memory and executing the method in any one of the designs in the first and second aspects described above according to the obtained program.

[0029] In a seventh aspect, embodiments of this application provide a computer program product that, when run on a processor, implements the method as described in any of the first and second aspects above.

[0030] The beneficial effects of the second to seventh aspects mentioned above can be specifically referred to the beneficial effects that can be achieved by any of the designs in the first aspect mentioned above, and will not be elaborated here. Attached Figure Description

[0031] Figure 1 An exemplary schematic diagram of a scenario architecture provided by an embodiment of this application is shown;

[0032] Figure 2 This illustration shows a page navigation diagram provided in an embodiment of this application.

[0033] Figure 3 An exemplary diagram illustrates a page management method provided in an embodiment of this application;

[0034] Figure 4 An exemplary schematic diagram of a scenario architecture provided by an embodiment of this application is shown;

[0035] Figure 5 This illustration shows another scenario architecture diagram provided by an embodiment of this application;

[0036] Figure 6 A schematic diagram of another page management method provided in an embodiment of this application is shown as an example. Detailed Implementation

[0037] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this invention, and not all of them. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.

[0038] Figure 1 This illustration shows a scenario architecture diagram provided by an embodiment of this application. Figure 1 As shown, a payment process requires actions on multiple pages, with each action on a previous page triggering navigation to the next. For example... Figure 1As shown, page A is the navigation page, which may include multiple buttons such as a scan button, a payment code button, and a card management button. Users click on one of these buttons to proceed to the next page. Assuming the user clicks the payment code button on page A, page B will be the payment code page. The payment code page includes a payment barcode / QR code display area, a bank card selection button, a payment collection code button, and a privacy policy entry button. After the merchant scans the payment barcode / QR code, the corresponding amount is deducted from the account, and the user is redirected to page C, the payment completion page. The payment completion page includes a payment success indicator, payment amount, order information, payment method, and a "complete" button. Clicking the "complete" button returns the user to page A. This completes the payment process using the payment code.

[0039] The payment process described above can be conducted within a bank's application, such as clicking the "Scan" button on the homepage of the China Merchants Bank application. Because the navigation logic and page attributes of each page are configured by the bank itself within a bank's application, no errors will occur during user operation. Continuing... Figure 1 For example, when navigating from page A to page B, the attribute A of page A can be retrieved and stored in the page dimension of page B just before page A is hidden and page B is displayed. Similarly, the attribute of page B can be retrieved and stored in the page dimension of page C just before page B is hidden and page C is displayed. If it is necessary to return from page C to page B, page C can retrieve the attribute of page B in its page dimension to restore it and return to page B. If it is necessary to return from page C to page A, page C can return to page B, and page B can retrieve the attribute of page A in its own page dimension to restore it and return to page A. If page C needs to return directly to page A without going through page B, the return operation from page C to page A can be achieved by setting jump logic between page C and page A. In other words, in an application, the jump logic between pages is pre-configured, and how pages jump and return is deterministic logic that will not result in errors.

[0040] However, in scenarios where banking institutions access the cloud network SDK, the payment page repeatedly jumps between the bank's application page and the cloud network SDK page, and different payment pages belong to different system architectures. Figure 2 This illustration shows a page navigation diagram provided in an embodiment of this application, such as... Figure 2As shown, A1 and A2 represent bank pages, while B1, B2, and B3 represent cloud network SDK pages. In this application scenario, when navigating from page A1 to page B1, page B1 needs to record attribute A1 of page A1 for returning to page A1; similarly, when navigating from page B1 to page A1, page A1 needs to record attribute B1 of page B1 for returning to page B1. However, in this scenario, because pages A1, B1, and A2 belong to different system architectures, it's uncertain whether page A2 will record attribute B1 of page B1 in its page dimension. If page A2 does not record attribute B1, an error will occur when returning from page A2 to page B1.

[0041] For example, in page B1, the navigation bar's attribute is "0" (0 means the navigation bar is hidden, 1 means the navigation bar is shown). After navigating from page B1 to page A2, the navigation bar's attribute changes to "1". If you then return from page A2 to page B1, since page A2 doesn't record the original attribute of page B1 as "0", even though the page now displays as page B1, the attribute remains "1" from page A1, resulting in a mismatch between the application display and the page attribute.

[0042] In addition, Figure 2 In scenarios where multiple pages are navigated sequentially, if it can be ensured that each subsequent page records the attributes of the previous page, it's possible to retrace backwards from the last page. For example, to return from page B3 to page A1, one can first return to page B2 based on the recorded attributes of page B2, after which page B3 disappears. Similarly, one can return from page B2 to page A2, from page A2 to page B1, and finally from page B1 to page A1, restoring the attributes of page A1. In the above scenario, since page B3 does not record the attributes of page A1, it's necessary to retrace back to the previous page and set its attributes. While returning directly from B3 to A1 is possible at the page level, since page B3 doesn't record the attributes of page A1, the attributes of page A1 would be incorrect.

[0043] To address the aforementioned issues, this application provides a page management method to ensure normal navigation and return between pages belonging to different system architectures.

[0044] Figure 3 An exemplary illustration shows a page management method provided in an embodiment of this application, such as... Figure 4 As shown, the method includes:

[0045] Step 301: The page management component runs after the application starts and listens to the application's page stack; the page stack is used to store the pages running in the application in sequence.

[0046] Step 302: The page management component determines the changed page indicated by the change information based on the monitored page stack change information.

[0047] Step 303: The page management component performs the same push and pop operations on the page attribute information corresponding to the changed page in the page attribute stack of the page management component as on the page stack; the page attribute information in the page attribute stack is used when the application performs page navigation across systems.

[0048] Figure 4 This illustration shows a scenario architecture diagram provided by an embodiment of this application. Figure 3 The method shown can be Figure 4 Execute in the scenario shown. For example... Figure 4 The scenario shown includes a page management component and various page stacks, which run within the application.

[0049] The page management component includes page attribute stacks, which can have a one-to-one correspondence with each page stack, ensuring a relatively even distribution of page attributes within each stack. For example, page attribute stack 1 corresponds to page stack 1; page attribute stack 2 corresponds to page stack 2; page attribute stack 3 corresponds to page stack 3, and so on, with page attribute stack n corresponding to page stack n. If a page stack contains a small number of pages, one page attribute stack can manage one page stack.

[0050] A page management stack is a stack used to store pages. A page stack can store multiple pages. For example, page stack 1 can include all the pages needed to perform a payment operation. After page stack 1 is full, page stack 2 can be added to continue storing pages.

[0051] Figure 5 This illustration demonstrates yet another scenario architecture provided by an embodiment of this application. Figure 5 The example shown uses page property stack 1 as an example. Figure 5As shown, a single payment operation may require navigating to pages A1, B1, A2, B2, and B3. From a display perspective, the user sees the page from page A1 all the way to page B3 to complete the payment process. From a page stack perspective, each page navigation adds a new page to the stack. The page attribute stack stores page attribute information. This information can be used to set display or hidden attributes of a page. For example, attribute information can include gesture attributes. Gesture attributes include: swiping left from the edge of the page, swiping up from the bottom of the page, scrolling up and down the page's scrollbar, scrolling left and right the page's scrollbar, and long-pressing the page. Taking scrolling up and down as an example, the page attribute information could be "scrollable" or "scrollable not." The scrollability information may differ on different pages. Therefore, the page attribute information in the page attribute stack needs to perform the same operations as the pages in the stack.

[0052] The above method establishes a page attribute stack to store page attribute information. This allows the page attributes of the changed page, as indicated by the change information, to be set when the page stack changes, thus achieving synchronization between the page and its attributes. Furthermore, any changes in the page stack are monitored; therefore, when a page in the stack changes multiple times consecutively, its page attributes will also change accordingly. This ensures that operations on the page function correctly after each change.

[0053] The following describes some specific changes in the page stack:

[0054] Change Information 1: If the page management component detects a new first page in the page stack, it determines that the second page displayed by the application is the changed page indicated by the change information.

[0055] Continue according to Figure 5 The scenario architecture shown is explained below. In the page stack dimension, page B1 is added. The change information then refers to the newly added page B1, and the page indicated by the change information is page A1. Correspondingly, in the application display dimension, it represents a jump from page A1 to page B1. It should be noted that... Figure 5 In the scenario shown, page A1 in the page stack can be loaded when the application starts, that is, the stack push operation of page A1 is performed.

[0056] Corresponding to the change information, the page management component obtains the page attribute information of the second page from the application; and performs a push operation on the page attribute information of the second page in the page attribute stack of the page management component.

[0057] like Figure 5As shown, the page management component obtains the page attribute information of page A1 from the application and pushes the page attribute information of page A1 onto the page attribute stack.

[0058] In another possible implementation, after navigating from page A1 to page B1, a page C is added between A1 and B1. The page indicated by the change information is now page C. Therefore, page C is pushed onto the page stack, and it can be positioned above or below page B1. Similarly, page C's attributes are pushed onto the attribute stack. For ease of addressing, page C's attributes can be positioned below page B1's attributes.

[0059] Figure 5 The navigation between other pages can be performed in the same way as navigating from page A1 to page B1, and will not be elaborated on here.

[0060] After the attribute information of page A1 is pushed onto the stack, it is used to retrieve the attributes of page A1 from the page attribute stack based on the page name when returning from page B1 to page A1, and then reset the attributes of page A1 accordingly. It should be noted that when navigating from page A1 to page B1, the attributes of page A1 are changed, such as the navigation bar changing from visible to hidden. Therefore, if the attributes of page A1 are not reset when returning from page B1 to page A1, user actions on page A1 will result in errors.

[0061] By employing the above method, when a page is added to the page stack, its corresponding attribute information is added to the attribute stack. On one hand, when navigating between pages, the attribute information of the previous page is saved promptly to prevent the loss of existing page attributes after the page disappears or its attributes change, thus ensuring a smooth transition back to the original page. On the other hand, storing the attribute information of the newly added page in the page attribute stack during page navigation ensures that page navigation and returning are normal even when an unavoidable page is added between two pages, making the page management component more compatible.

[0062] Change Information 2: If the page management component detects a change in the page stack indicating that the third page has been deleted, then it determines that the changed page indicated by the change information is the third page.

[0063] In one possible implementation, continue according to Figure 5 The scenario architecture shown is explained below. Following the process described in change information 2 above, after the page navigates to page B2, it needs to return to page B1 from page B2. At this point, in the page stack dimension, pages B2 and A2 are deleted. The page that changes in the page display dimension change information in real time is page B2.

[0064] Corresponding to the second change information, the page management component performs a pop operation on the page attribute information of the third page in the page attribute stack of the page management component.

[0065] like Figure 5 As shown, the page management component retrieves the page properties of page B2 and page A2 from the page property stack, and then obtains the page properties of page B1 from the page property stack based on the page name of page B1, thereby allowing the properties of page B1 to be reset.

[0066] In another possible implementation, the pages visited during a page navigation can be deleted at any point. For example, in... Figure 5 In the process, after the page display dimension reaches page B2, the application determines that it will not return to page B2. Therefore, page B2 can be deleted from the page stack, and correspondingly, the page B2 attribute can be deleted from the page attribute stack.

[0067] By using the above method, changes in the page attribute stack can be adjusted promptly based on changes in the page stack. When a page is deleted, the attribute information in the page attribute stack is promptly removed. This saves storage space in the page attribute stack and makes it easier to obtain target page attribute information by removing unused attribute information.

[0068] Change Information 3: If the page management component detects a change in the page stack that the fourth page has been replaced by the fifth page, then it determines that the changed pages indicated by the change information are the fourth page and the fifth page.

[0069] Continue according to Figure 5 The scenario architecture shown is explained below. After navigating from page A1 to page B1, page A1 is replaced by page D. At this point, the change information indicates both page D and page A1. Therefore, in the page stack, page A1 is popped off the stack, and page D is pushed onto the stack.

[0070] Correspondingly, in the page attribute stack, the page management component performs a pop operation on the page attribute information of page A1 and then a push operation on the page attribute information of page D.

[0071] By using the above method, after a page is replaced by another page, the attribute information in the page attribute stack corresponding to this page is also replaced, thereby ensuring the synchronization between page attribute information and the page, and thus ensuring that the page attribute settings match the current page.

[0072] In one possible implementation, the page management component listens for cross-system page navigation operations in the application; the cross-system page navigation operation is used to indicate navigation to the sixth page; the page management component can obtain the page attribute information of the sixth page through the page attribute stack; the page management component pushes the page attribute information of the sixth page to the application.

[0073] Continue according to Figure 5 The scenario architecture shown is explained below. Following the process described in Change Information 2 above, after the page redirects to page B3, the payment process is completed. There is a "Complete" button on page B3. By clicking this button, the user returns to the initial page A1. Page A1 can be a page within a bank's app, while pages B3, B2, A2, and B1 can be pages within the UnionPay app. In this scenario, completing a payment operation spans two applications. When a page needs to return from page B1 to page A1, the page management component retrieves the A1 page attribute information from the page attribute stack based on the page name of A1 and pushes this information to the application containing page A1. This allows the application to set the attributes of page A1 based on the A1 page attribute information.

[0074] For example, when obtaining the page attribute information of the sixth page from the page attribute stack, the page attribute information of B2, A2, and B1 can all be popped from the stack until the page attribute information of A1 is obtained.

[0075] By employing the above method, in a stack-based storage system, unwanted page attribute information is popped from the stack while the required page attribute information is retrieved. This saves space in the page attribute stack and makes retrieving the necessary page attribute information more convenient.

[0076] To achieve the pop-out order described above, page attribute information can be pushed onto the stack in the order of page navigation. For example... Figure 5 As shown, after navigating to the last page B3, the page attribute stack, in the order of page navigation from top to bottom, contains the attribute information of page B2, page A2, page B1, and page A1.

[0077] By using the above method, the information stored in the stack storage structure can be consistent with the actual page jump process, thus making it more convenient to perform pop and push operations during page jumps.

[0078] Based on the same technical concept, this application also provides a page management method. Figure 6 An exemplary schematic diagram of another page management method provided in an embodiment of this application is shown in the figure. As shown, the method includes:

[0079] Step 601: The application obtains the cross-system page jump operation triggered by the user; the cross-system page jump operation is used to indicate the jump to the sixth page;

[0080] Step 602: The application retrieves the sixth page from the application's page stack and obtains the page attribute information of the sixth page based on the page attribute stack of the page management component.

[0081] Step 603: The application displays the sixth page based on the sixth page and its page attribute information.

[0082] Based on the same technical concept, this application also provides a page management component, which is used to run after the application starts and monitor the page stack of the application; the page stack is used to store the pages running in the application in sequence; the page management component is also used to determine the changed page indicated by the change information based on the monitored change information of the page stack; the page management component is also used to perform the same push and pop operations on the page attribute information corresponding to the changed page in the page attribute stack of the page management component as on the page stack; the page attribute information in the page attribute stack is used when the application performs cross-system page navigation.

[0083] In one possible implementation, the page management component is specifically configured to, upon detecting a change in the page stack indicating the addition of a first page, determine that the second page displayed by the application is the changed page indicated by the change information; the page management component is further configured to obtain page attribute information of the second page from the application; and perform a push operation on the page attribute information of the second page in the page attribute stack of the page management component.

[0084] In one possible implementation, the page management component is specifically used to, upon detecting a change in the page stack indicating the deletion of a third page, determine that the changed page indicated by the change information is the third page; the page management component is further used to, in the page attribute stack of the page management component, perform a pop operation on the page attribute information of the third page.

[0085] In one possible implementation, the page management component is specifically configured to, upon detecting a change in the page stack where the fourth page is replaced by the fifth page, determine that the changed pages indicated by the change information are the fourth page and the fifth page; the page management component is further configured to, in the page attribute stack of the page management component, perform a pop operation on the page attribute information of the fourth page and then perform a push operation on the page attribute information of the fifth page.

[0086] In one possible implementation, the page management component is further configured to listen for cross-system page navigation operations of the application; the cross-system page navigation operation is used to indicate navigation to the sixth page; the page management component obtains the page attribute information of the sixth page through the page attribute stack; and pushes the page attribute information of the sixth page to the application.

[0087] In one possible implementation, the page management component is specifically used to pop page attribute information from the page attribute stack that is located after the page attribute information of the sixth page, until the page attribute information of the sixth page is obtained.

[0088] In one possible implementation, the page management component is further configured to sequentially push page attribute information following the page attribute information of the sixth page onto the page attribute stack.

[0089] Based on the same technical concept, embodiments of the present invention also provide a computing device, including: a memory for storing program instructions;

[0090] The processor is used to call program instructions stored in the memory and execute them according to the obtained program. Figure 3 and Figure 6 The method shown.

[0091] Based on the same technical concept, embodiments of the present invention also provide a computer-readable storage medium, which, when the computer program product is run on a processor, implements the following: Figure 3 and Figure 6 The method shown.

[0092] Based on the same technical concept, embodiments of the present invention also provide a computer program product, which, when run on a processor, implements the following: Figure 3 and Figure 6 The method shown.

[0093] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0094] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0095] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0096] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0097] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A page management method, characterized in that, The method includes: The page management component runs after the application starts and monitors the application's page stack; the page stack is used to store the pages that are running in the application in sequence. The page management component determines the changed page indicated by the change information based on the monitored changes in the page stack. The page management component performs the same push and pop operations on the page attribute information corresponding to the changed page in the page attribute stack of the page management component. The page attribute information in the page attribute stack is used when the application performs cross-system page navigation. Cross-system pages refer to pages belonging to different system architectures. The page management component listens for cross-system page navigation operations of the application. These cross-system page navigation operations are used to indicate navigation to the sixth page. The cross-system page navigation operations of the application are triggered by the user. The page management component obtains the page attribute information of the sixth page through the page attribute stack; The page management component pushes the page attribute information of the sixth page to the application, which then... The application displays the sixth page based on the page attribute information of the sixth page and the sixth page obtained from the page stack.

2. The method as described in claim 1, characterized in that, The page management component determines the changed page indicated by the change information based on the monitored changes in the page stack, including: If the page management component detects a change in the page stack indicating the addition of a first page, it determines that the second page displayed by the application is the changed page indicated by the change information. The page management component performs the same push and pop operations on the page attribute stack as on the page attribute stack for the page attribute information corresponding to the changed page, including: The page management component obtains the page attribute information of the second page from the application; The page attribute information of the second page is pushed onto the page attribute stack of the page management component.

3. The method as described in claim 1, characterized in that, The page management component determines the changed page indicated by the change information based on the monitored changes in the page stack, including: If the page management component detects that the change information in the page stack indicates that the third page has been deleted, then it determines that the changed page indicated by the change information is the third page. The page management component performs the same push and pop operations on the page attribute stack as on the page attribute stack for the page attribute information corresponding to the changed page, including: The page management component performs a pop operation on the page attribute information of the third page in the page attribute stack of the page management component.

4. The method as described in claim 1, characterized in that, The page management component determines the changed page indicated by the change information based on the monitored changes in the page stack, including: If the page management component detects that the fourth page has been replaced by the fifth page in the page stack, it determines that the changed pages indicated by the change information are the fourth page and the fifth page. The page management component performs the same push and pop operations on the page attribute stack as on the page attribute stack for the page attribute information corresponding to the changed page, including: After popping the page attribute information of the fourth page from the page attribute stack, the page management component performs a push operation on the page attribute information of the fifth page.

5. The method as described in claim 1, characterized in that, The page management component obtains the page attribute information of the sixth page through the page attribute stack, including: The page management component pops page attribute information from the page attribute stack that follows the page attribute information of the sixth page until it obtains the page attribute information of the sixth page.

6. The method as described in claim 5, characterized in that, The method further includes, after obtaining the page attribute information of the sixth page, the following: Page attribute information following the page attribute information of the sixth page will be pushed onto the page attribute stack in sequence.

7. A page management method, characterized in that, The method includes: The application obtains a cross-system page navigation operation triggered by the user; the cross-system page navigation operation is used to indicate navigation to the sixth page; The application obtains the sixth page from the application's page stack and obtains the page attribute information of the sixth page based on the page attribute stack of the page management component. The page management component performs page management using the method described in any one of claims 1 to 6. The application displays the sixth page based on the sixth page and its page attribute information.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed, performs the method as described in any one of claims 1 to 7.

9. A computing device, characterized in that, include: Memory, used to store program instructions; A processor is configured to invoke program instructions stored in the memory and execute the method as described in any one of claims 1 to 7 according to the obtained program.

Images