Method for page skipping between applications and electronic equipment

Abstract

The invention provides an inter-application page jumping method and electronic equipment, relates to the technical field of terminals, and aims to directly jump from a pulled-up page to a page of a pulling-up party without layer-by-layer jumping of multiple pages of the pulling-up party in the process, so that more time is not wasted, the page jumping efficiency is improved, and the user experience is improved. And the user experience is improved. In the method, the electronic equipment displays the first page of the first application, and the electronic equipment displays the second page of the second application after responding to the operation that the first application pulls up the second page of the second application. Wherein the second page is added into a main task stack of the second application, the second page is configured with a page mark, the main task stack is used for storing an opened page in the second application, and the page mark is used for indicating that the second page is pulled up by other applications. The electronic device receives a return gesture on the displayed second page and displays a first page of the first application in response to the return gesture.

Description

Technical Field

[0001] This application relates to the technical field of terminals, and in particular, to a method for page jumping between applications and an electronic device. Background Art

[0002] Currently, the mutual launching between applications enables one application to use the functions of another application. For example, when a user is purchasing goods using a shopping application and clicks the purchase control, the shopping application will launch the payment page of the payment application, and the user can complete the payment on the payment page. After that, if the user wants to continue browsing the goods, the user can make a return gesture on the payment page to trigger the device to redisplay the page of the shopping application, realizing the page jump.

[0003] However, if the user has browsed some pages in the payment application before the payment page is launched, then after the user makes a return gesture on the payment page, the device will sequentially display the historical pages that the user has browsed in the payment application. After the historical pages are displayed, the device will redisplay the page of the shopping application.

[0004] It can be seen that in the above process of page jumping, if the payment application has been browsed with a large number of pages before the payment page is launched, then when jumping back to the page of the shopping application, it takes a long time, which not only reduces the efficiency of page jumping but also affects the user experience. Summary of the Invention

[0005] This application provides a method for page jumping between applications and an electronic device, which can directly jump back to the page of the launching party from the launched page without experiencing multiple layer-by-layer jumps of the launched party pages, without wasting much time, thereby improving the efficiency of page jumping and enhancing the user experience.

[0006] To achieve the above object, the embodiments of this application adopt the following technical solutions:

[0007] In a first aspect, a method for page jumping between applications is provided. Taking the example that this method is applied to an electronic device, the electronic device displays a first page of a first application. After responding to an operation of the first application to launch a second page of a second application, the electronic device displays the second page of the second application. Among them, the second page is added to the main task stack of the second application, and the second page is configured with a page mark. The main task stack is used to save the pages opened in the second application, and the page mark is used to indicate that the second page is launched by other applications. The electronic device receives a return gesture on the displayed second page and, in response to the return gesture, displays the first page of the first application.

[0008] In the above method, after the second page is pulled up, the electronic device can save the second page with a page marker in the main task stack of the second application. After that, when the electronic device displays the second page with a page marker, it will respond to the return gesture and return to the first page of the first application, realizing page jumping between applications. Such page jumping is directly achieved across applications. If there are other pages in the main task stack of the second application before the second page, there is no need to perform page jumping layer by layer in the main task stack to return, thus saving the time for page jumping between applications and improving the efficiency of page jumping.

[0009] In an implementable manner of the first aspect, the second application includes multiple pages, and the multiple pages include a second page and a third page. After the second page of the second application is displayed, if the second application receives a page jumping event, then after the electronic device receives the page jumping event in the second application, it displays the third page of the second application, where the page jumping event is used to indicate jumping from the second page to the third page, and the third page is added to the main task stack of the second application. The electronic device receives a return gesture on the displayed third page and, in response to the return gesture, displays the second page of the second application.

[0010] In the above implementable manner, if the electronic device receives a return gesture when displaying a page without a page marker in the second application, then the electronic device will first perform page jumping in the main task stack, jumping the displayed page to the page before this page in the main task stack to achieve page jumping within the second application. When the electronic device displays the second page and then receives a return gesture, it will directly display and jump to the first page of the first application. In this way, direct page jumping between applications can also be achieved, thus saving time and improving the efficiency of page jumping.

[0011] In an implementable manner of the first aspect, the electronic device obtains parameter information from the first application, where the parameter information is used to indicate the second page. The electronic device sends the parameter information to the second application and obtains the second page determined by the second application according to the parameter information. After that, the electronic device displays the second page.

[0012] In the above implementable manner, when responding to the operation of the first application pulling up the page of the second application, the electronic device can more accurately determine the page of the second application to be pulled up and displayed through the parameter information sent by the first application, bringing a better user experience to the user.

[0013] In an implementable manner of the first aspect, the return gesture is a gesture of sliding from the edge of the screen towards the middle of the screen, such as a finger sliding right on the left edge of the screen or a finger sliding left on the right edge of the screen, etc.

[0014] In the above implementation manners, these return gestures are all return gestures that are commonly used or preferred by users. Therefore, when the user operates on the second page displayed by the electronic device or operates on the electronic device through these return gestures, it also conforms to the user's usage habits and ensures the user experience.

[0015] In an implementable manner of the first aspect, the electronic device responds to an operation of the first application to pull up the second page of the second application, including: the electronic device receives an operation of the user on the function control of the first page, and in response to this operation, displays the second page of the second application; wherein, the second page displays content associated with the first page or the function control.

[0016] In the above implementation manners, the user can trigger page jumps between applications through the function control on the first page of the first application. Exemplarily, the function control on the first page can provide functions such as payment and login. When the user operates on the function control, it can trigger the operation of the first application to pull up the second page of the second application, and the payment information, login information, etc. provided by the second application can be displayed on the second page.

[0017] In an implementable manner of the first aspect, after the electronic device responds to the operation of the first application to pull up the second page of the second application again, it displays the second page of the second application. Then, when the electronic device receives an operation to return to the desktop on the displayed second page, it cancels the page mark of the second page and displays the desktop.

[0018] It can be understood that the above page mark can be pre-configured by the developer of the application for the application page before the application is put on the shelf, or can be configured by the application itself after the application page is pulled up. When the electronic device receives an operation to return to the desktop on the displayed second page, it means that the call chain between the second application and the first application is disconnected, that is, the call relationship between the second page and the first page of the first application no longer exists. If the page mark is configured by the application itself after the application page is pulled up, then when the call chain is disconnected, the page mark of the second page does not need to exist either, so that the electronic device can cancel the page mark of the second page.

[0019] In the second aspect, a method for page jump between applications is provided. Taking this method as an example applied to an electronic device, the electronic device displays the first page of the first application. After responding to the operation of the first application to pull up the second page of the second application, the electronic device displays the second page of the second application, wherein the second page is added to the temporary task stack of the second application. The temporary task stack of the second application is at least used to save the second page pulled up through the first page, and the second page is the first page to be pushed onto the stack in the temporary task stack of the second application. Then, when the electronic device receives a return gesture on the displayed second page and responds to the return gesture, it displays the first page of the first application.

[0020] In the above method, after the second page is pulled up, the electronic device saves the second page in the temporary task stack of the second application. The electronic device will respond to the return gesture and return to the first page of the first application only when displaying the second page that was first pushed onto the stack in the temporary task stack (or the page at the top of the stack in the temporary task stack), thus realizing page jumping between applications. Such page jumping is directly achieved across applications. If there are other pages in the main task stack of the second application before the second page, there is no need to perform page jumping layer by layer in the main task stack to return, thereby saving the time for page jumping between applications and improving the efficiency of page jumping.

[0021] In an implementable manner of the second aspect, the temporary task stack is further used to save at least one page opened in the second application after the second page is pulled up. After displaying the second page of the second application, if the second application receives a page jumping event, then after the electronic device receives the page jumping event in the second application, it displays the third page of the second application, where the page jumping event is used to indicate jumping from the second page to the third page, and the third page is added to the temporary task stack of the second application. After that, the electronic device receives a return gesture on the displayed third page and, in response to the return gesture, displays the second page of the second application and removes the third page from the temporary task stack.

[0022] In the above implementable manner, if the electronic device receives a return gesture when the page displayed in the temporary task stack of the second application is not the page that was first pushed onto the stack, then the electronic device will first perform page jumping in the temporary task stack to jump the displayed page to the page before this page in the temporary task stack to achieve page jumping within the second application. When the electronic device displays the second page and then receives a return gesture again, it will directly display and jump to the first page of the first application. In this way, direct page jumping between applications can also be achieved, thereby saving time and improving the efficiency of page jumping.

[0023] In an implementable manner of the second aspect, after displaying the first page of the first application, the temporary task stack of the second application is destroyed; or, after the second application is placed in the background, the temporary task stack of the second application is destroyed.

[0024] In the above implementable manner, both the jump back of the displayed content from the second page to the first page and the second application being placed in the background indicate that the call chain between the first application and the second application is disconnected. The temporary task stack of the application does not affect the main task stack of the application. After the call chain between the first application and the second application is disconnected, the temporary task stack will be destroyed, while the main task stack of the second application will still exist. When the user resumes running the second application in the foreground of the mobile phone, the pages opened in the second application will be added to the main task stack of the second application.

[0025] In an implementable manner of the second aspect, after the second page of the second application is displayed, if the second application launches the fourth page of the third application, after the electronic device responds to the operation of the second application launching the fourth page of the third application, it displays the fourth page of the third application. The fourth page is added to the temporary task stack of the third application, and the fourth page is the first page to be pushed onto the temporary task stack of the third application. After that, the electronic device receives a return gesture on the displayed fourth page and, in response to the return gesture, displays the second page of the second application.

[0026] In the above implementation manner, the second application can also launch a page of the third application. In this case, after the fourth page of the third application is launched, the fourth page is saved in the temporary task stack of the third application. The electronic device will only respond to the return gesture and return to the second page of the second application when it displays the fourth page, which is the first page to be pushed onto the temporary task stack, thus realizing page jumping between applications. Such page jumping is directly implemented across applications. If there are other pages in the main task stack of the second application before the second page, there is no need to perform page jumping layer by layer in the main task stack to return, thereby saving the time for page jumping between applications and improving the efficiency of page jumping.

[0027] In an implementable manner of the second aspect, after the electronic device responds to the operation of the second application launching the fourth page of the third application, it destroys the temporary task stack of the second application; when there is at least one page still saved in the temporary task stack of the second application, it saves the at least one page to the main task stack of the second page; the main task stack is used to save the pages opened in the second application.

[0028] The above implementation manner can ensure that at least one page that has been opened in the second application will not be destroyed. In this way, when the user uses the second application again, they can still view the page they last browsed before, thus ensuring the user experience.

[0029] It can be understood that the life cycle of the main task stack of an application is consistent with the life cycle of the application, and the temporary task stack of an application only exists when the application is called by another application and the called application is in the foreground.

[0030] In an implementable manner of the second aspect, the electronic device obtains parameter information from the first application, where the parameter information is used to indicate the second page. The electronic device sends the parameter information to the second application and obtains the second page determined by the second application according to the parameter information. After that, the electronic device displays the second page.

[0031] In the above implementation, when responding to the operation of the first application to pull up the page of the second application, the electronic device can more accurately determine the page of the second application to be pulled up and displayed through the parameter information sent by the first application, bringing a better user experience to the user.

[0032] In an implementable manner of the second aspect, the electronic device's response to the operation of the first application to pull up the second page of the second application includes: the electronic device receives the user's operation on the function control of the first page and, in response to this operation, displays the second page of the second application; wherein, the second page displays content associated with the first page or the function control.

[0033] In the above implementation, the user can trigger the page jump between applications through the function control on the first page of the first application. Exemplarily, the function control on the first page can provide functions such as payment, login, etc. The user's operation on the function control can trigger the operation of the first application to pull up the second page of the second application, and the payment information, login information, etc. provided by the second application can be displayed on the second page.

[0034] In an implementable manner of the second aspect, the return gesture is a gesture of swiping from the edge of the screen towards the middle of the screen, such as swiping the finger from the left edge of the screen to the right or swiping the finger from the right edge of the screen to the left, etc.

[0035] These return gestures are all return gestures that users commonly use or are more accustomed to. Therefore, when the user operates on the second page displayed by the electronic device or operates on the electronic device through these return gestures, it also conforms to the user's usage habits and ensures the user experience.

[0036] In a third aspect, an electronic device is provided, including a memory and one or more processors; the memory is coupled to the processor; wherein, computer program code is stored in the memory, and the computer program code includes computer instructions. When the computer instructions are executed by the processor, the electronic device executes the method for page jump between applications as described in the first aspect and any of its implementable manners, or executes the method for page jump between applications as described in the second aspect and any of its implementable manners.

[0037] In a fourth aspect, a computer-readable storage medium is provided, including computer instructions. When the computer instructions run on an electronic device, the electronic device executes the method for page jump between applications as described in the first aspect and any of its implementable manners, or executes the method for page jump between applications as described in the second aspect and any of its implementable manners.

[0038] Fifth aspect, a computer program product is provided. When the computer program product runs on a computer, it causes the computer to execute the method for inter-application page jump described in the first aspect and any one of its implementation manners, or execute the method for inter-application page jump described in the second aspect and any one of its implementation manners.

[0039] For the electronic device provided in the third aspect above, the computer-readable storage medium provided in the fourth aspect, and the computer program product provided in the fifth aspect, the beneficial effects that can be achieved can refer to the beneficial effects that can be achieved in the first aspect and any one of its implementation manners, or refer to the beneficial effects that can be achieved in the second aspect and any one of its implementation manners, which will not be elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 The figure shows a schematic diagram of the task stack of the application provided in the embodiment of the present application;

[0041] Figure 2 The figure shows a schematic diagram of the return control provided in the embodiment of the present application;

[0042] Figure 3 The figure shows the structural schematic of the electronic device provided in the embodiment of the present application Figure 1 ;

[0043] Figure 4 The figure shows the structural schematic of the electronic device provided in the embodiment of the present application Figure 2 ;

[0044] Figure 5 The figure shows a schematic diagram of the processing process of the running management service in the electronic device provided in the embodiment of the present application;

[0045] Figure 6 The figure shows a schematic flow chart of the method for inter-application page jump provided in the embodiment of the present application Figure 1 ;

[0046] Figure 7 The figure shows a schematic diagram of inter-application page jump provided in the embodiment of the present application;

[0047] Figure 8 The figure shows a schematic diagram of the return gesture provided in the embodiment of the present application;

[0048] Figure 9 The figure shows a schematic diagram of page jump provided in the embodiment of the present application Figure 1 ;

[0049] Figure 10 The figure shows a schematic diagram of page jump provided in the embodiment of the present application Figure 2 ;

[0050] Figure 11The flowchart of the method for page jump between applications provided by the embodiments of the present application is shown Figure 2 ;

[0051] Figure 12 The schematic diagram of page jump provided by the embodiments of the present application is shown Figure 3 ;

[0052] Figure 13 The structural schematic diagram of the electronic device provided by the embodiments of the present application is shown Figure 3 . Detailed implementation manners

[0053] Next, the technical solutions in the embodiments of the present application will be described with reference to the accompanying drawings in the embodiments of the present application. Among them, in the description of the present application, unless otherwise specified, " / " means that the objects associated before and after are in an "or" relationship. For example, A / B may represent A or B; "and / or" in the present application is only a description of the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. These three situations, where A and B may be singular or plural. And, in the description of the present application, unless otherwise specified, "a plurality of" means two or more than two. "At least one (item)" or similar expressions below refer to any combination of these items, including any combination of single item (item) or plural items (items). For example, at least one (item) of a, b, or c may represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, c may be single or multiple. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and effects. Those skilled in the art can understand that the words such as "first" and "second" do not limit the quantity and execution order, and the words such as "first" and "second" do not necessarily limit to be different. At the same time, in the embodiments of the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of the present application should not be construed as being more preferred or more advantageous than other embodiments or design solutions. Exactly speaking, using words such as "exemplary" or "for example" aims to present relevant concepts in a specific way for easy understanding.

[0054] In addition, the business scenarios described in the embodiments of the present application are for more clearly explaining the technical solutions of the embodiments of the present application, and do not constitute a limitation to the technical solutions provided by the embodiments of the present application. Those of ordinary skill in the art know that with the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0055] Applications usually have their own task stacks, which are used to save or manage the opened pages in the applications. The task stack is a last-in-first-out data structure. The page that enters the stack first is placed at the bottom of the stack, and the page that enters the stack last is placed at the top of the stack.

[0056] Currently, the mutual launch between applications enables one application to use the functions of another application.

[0057] For example, when a user is using a shopping application to purchase goods and clicks the purchase control, the shopping application will launch the payment page of the payment application, and the user can complete the payment on the payment page. After the payment page is launched, the payment page will be added to the task stack of the payment application. Then, if the user wants to continue browsing the goods, the user can make a return gesture on the payment page to trigger the device to redisplay the page of the shopping application, realizing the page jump.

[0058] However, if the user has browsed some pages in the payment application before the payment page is launched, then before the payment page is pushed onto the stack, there are already some pages saved in the task stack. After the user makes a return gesture on the payment page, the device will, according to the characteristics of the task stack, sequentially display the historical pages that the user has browsed in the payment application in the task stack. After the historical pages are displayed, the device will display the page of the shopping application again, thus realizing the page jump between the payment application and the shopping application.

[0059] In the above process of page jump, if the payment application has been browsed with a large number of pages before the payment page is launched, then when jumping back to the page of the shopping application, it is necessary to perform the page return layer by layer in the payment application, which will waste a lot of time, thereby reducing the efficiency of page jump. Moreover, returning the pages layer by layer in this way will also affect the user experience.

[0060] In some solutions, the launched application page can be added to the task stack of the launching application, thereby realizing the page jump between applications. For example, as shown in Figure 1 When application A launches the page of application B, it only needs to add this page to the task stack of application A for management to achieve a one-step application jump. For example: after the user finishes the operation on the page of application B, the user jumps back to the page of application A through the back key or the return gesture. In this solution, since the page of application B is added to the task stack of application A, the task stack of application B itself remains independent and unaffected. However, the launched application page is not in the task stack of the launched application itself, which is not conducive to the management of the page by the launched application.

[0061] In some other solutions, when the pulled-up application page is displayed, a default return control or return button can be provided, and the user can click the return control to achieve page jumping between applications. For example, refer to Figure 2 As shown, a control corresponding to the "Shopping Application" is displayed in the upper left corner of the information page, thereby indicating that the currently displayed information page is the page pulled up by the shopping application. After the user views the information page, the user can click the control corresponding to the "Shopping Application" to directly jump back to the page of the shopping application.

[0062] In this solution, although the pulled-up page does not need to be added to the task stack of the pulling-up application, the return control or return button is set at the upper part of the page. For some devices with a larger screen, it is very inconvenient for the user to operate with one hand. In addition, during the daily use of the device, the user may be accustomed to using a global return gesture for page jumping operations. Implementing page jumping through the above-mentioned return control method will also split the user's operation from the usual usage habits and affect the user experience.

[0063] Based on the above content, the embodiments of the present application provide a method for page jumping between applications. In this method, the user can follow the daily usage habits and make a return gesture on the pulled-up page, so that the displayed page jumps back to the page of the pulling party, which can ensure the user experience; and the user can also control page jumping with one hand, making the user's operation more convenient; in addition, this method can also directly jump back from the pulled-up page to the page of the pulling party, without having to go through multiple layers of jumps of the pulled-up pages in the middle, without wasting too much time, thereby improving the efficiency of page jumping and improving the user experience.

[0064] Exemplarily, taking the above method applied to an electronic device as an example, the electronic device can display the first page of the first application. Through click operations, confirmation operations, or jump operations on the first page, etc., in response to the operation of the first application pulling up the second application, the electronic device can then display the second page of the second application, where the second page is added to the main task stack of the second application, and the second page is configured with a page mark; the main task stack is used to save the opened pages in the second application; the page mark is used to indicate the page of the second application that can be pulled up by other applications. After that, the electronic device receives a return gesture on the displayed second page and, in response to the return gesture, displays the first page.

[0065] In this solution, after the second page is pulled up, the electronic device saves the second page with the page mark in the task stack of the second application. When the electronic device displays the page with the page mark, it will respond to the return gesture and jump back to the first page of the first application to achieve page jumping between applications.

[0066] Exemplarily, taking the above method applied to an electronic device as an example, the electronic device can display a first page of a first application. By means of a click operation, a confirmation operation, a jump operation, etc. on the first page, the electronic device responds to the operation of pulling up a second application by the first application, and the electronic device can then display a second page of the second application, where the second page is added to the temporary task stack of the second application, and the temporary task stack of the second application is at least used to save the second page pulled up through the first page, and the second page is the page that is first pushed onto the stack in the temporary task stack. After that, the electronic device receives a return gesture on the displayed second page and responds to the return gesture to display the first page.

[0067] In this solution, after the second page is pulled up, the electronic device saves the second page in the temporary task stack of the second application. The electronic device will only respond to the return gesture and jump back to the first page of the first application when displaying the second page in the temporary task stack, thus realizing page jumping between applications.

[0068] When the above method is applied to an electronic device, in some embodiments, as shown in Figure 3 Figure 9, the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0069] It can be understood that the structure schematically shown in the embodiments of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or have different component arrangements.

[0070] The processor 110 may include one or more processing units ( Figure 3(not shown in the figure), for example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors.

[0071] Among them, the controller may be the nerve center and command center of the electronic device 100. The controller may generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching and executing instructions.

[0072] A memory may also be provided in the processor 110 for storing instructions and data.

[0073] In some embodiments, the processor 110 may include one or more interfaces ( Figure 3 (not shown in the figure).

[0074] Among them, the USB interface 130 is an interface that conforms to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc.

[0075] The charging management module 140 is used to receive charging input from a charger. Among them, the charger may be a wireless charger or a wired charger.

[0076] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives the inputs from the battery 142 and / or the charging management module 140 to supply power to the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, and the wireless communication module 160, etc. The power management module 141 may also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance).

[0077] The wireless communication function of the electronic device 100 may be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, and the baseband processor, etc.

[0078] Antenna 1 and Antenna 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization rate of the antennas. For example, Antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0079] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc. applied to the electronic device 100.

[0080] The wireless communication module 160 can provide solutions for wireless communications including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), etc. applied to the electronic device 100.

[0081] In some embodiments, Antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and Antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technologies.

[0082] The electronic device 100 realizes the display function through the GPU, the display screen 194, and the application processor, etc. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering.

[0083] The display screen 194 is used to display images, videos, etc.

[0084] In some examples, the display screen 194 (which can be referred to as the screen in subsequent embodiments) can display the icons of the applications in the electronic device 100. After the user clicks on the application icon, the application is launched, and the display screen 194 can further display the page of the application.

[0085] In some examples, when the user is using the first application, if certain operations are performed on the first application or on the page of the first application, such as click operations, confirmation operations, or jump operations, etc., it may trigger the first application to launch a page of the second application. After the page of the second application is launched, the display screen 194 will also display the page of the second application. When the display screen 194 displays the page of the second application, if the user makes a return gesture on the display screen 194, the display screen 194 will also display the page of the first application again, presenting the effect of jumping back from the page of the second application to the page of the first application for the user.

[0086] The electronic device 100 can implement the shooting function through the ISP, the camera 193, the video codec, the GPU, the display screen 194, and the application processor, etc. The ISP is used to process the data fed back by the camera 193. The camera 193 is used to capture still images or videos.

[0087] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. For example, music, videos, and other files are saved in the external memory card.

[0088] The internal memory 121 can be used to store computer-executable program code, and the executable program code includes instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121.

[0089] In some examples, when a certain page of an application is opened, the processor 110 can run the instructions stored in the internal memory 121 to save the page in the task stack of the application and control the screen to display the page.

[0090] In some examples, when the user is using the first application, if the first application launches a page of the second application, the processor 110 also runs the instructions stored in the internal memory 121 to save the page of the second application in the task stack of the second application and control the screen to change the displayed page of the first application to the page of the second application. After that, the processor 110 also runs the instructions stored in the internal memory 121 to identify whether there is a page mark on the gesture made by the user on the screen and the page displayed on the screen. If the user makes a return gesture and the page displayed on the screen has a page mark, then the processor 110 runs the instructions stored in the internal memory 121 to control the screen to change the displayed page of the second application to the page of the first application.

[0091] In some examples, when the user uses the first application and the first application launches a page of the second application, the processor 110 also runs the instructions stored in the internal memory 121 to save the page of the second application in the temporary task stack of the second application, and controls the screen to jump the page of the first application being displayed to the page of the second application. After that, the processor 110 also runs the instructions stored in the internal memory 121 to identify whether the gesture made by the user on the screen and the page displayed on the screen is the page at the bottom of the temporary task stack of the second application. If the user makes a return gesture and the page displayed on the screen is the page at the bottom of the temporary task stack of the second application, the processor 110 runs the instructions stored in the internal memory 121 to control the screen to jump the page of the second application being displayed to the page of the first application.

[0092] The audio module 170 is used to convert digital audio information into an analog audio signal for output, and is also used to convert an analog audio input into a digital audio signal. The keys 190 include a power-on key, volume keys, etc. The motor 191 can generate a vibration prompt. The indicator 192 can be an indicator light, which can be used to indicate the charging state, power change, and can also be used to indicate messages, missed calls, notifications, etc. The SIM card interface 195 is used to connect the SIM card.

[0093] When implementing the method for page jump between applications provided in the embodiments of the present application based on the above electronic device, the user can follow the daily usage habits and make a return gesture on the pulled-up page. The electronic device can jump back from the page of the pulled-up party being displayed to the page of the pulling party, which can ensure the user experience; and, the user can also control the page jump with one hand, making the user's operation more convenient; in addition, the above method can directly jump back from the pulled-up page to the page of the pulling party, without going through multiple layers of jumps of the pulled-up party pages in the middle, and will not waste too much time, thereby improving the efficiency of page jump and improving the user experience.

[0094] In some embodiments, the software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservices architecture, or a cloud architecture. In the embodiments of the present application, taking the mobile operating system with a layered architecture as an example, the software structure of the electronic device 100 is exemplarily described.

[0095] Among them, as shown in Figure 4 As shown, the layered architecture of the electronic device 100 divides the software into several layers, and each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the mobile operating system is divided into four layers, from top to bottom are the application layer, the application framework layer, the system service layer, and the kernel layer.

[0096] The application layer may include a series of application packages.

[0097] As Figure 4 shown, the application package may include applications such as shopping, payment, camera, calendar, call, gallery, map, navigation, Bluetooth, music, video, short message, etc.

[0098] The application framework layer provides application programming interfaces (APIs) and programming frameworks for the applications in the application layer. The application framework layer includes some predefined functions.

[0099] As Figure 4 shown, the application framework layer may include a window manager, a content provider, a view system, a telephone manager, a resource manager, a notification manager, etc.

[0100] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

[0101] The content provider is used to store and obtain data, and make this data accessible to applications. The data may include videos, images, audio, dialed and answered calls, browsing history and bookmarks, phone books, etc.

[0102] The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, etc. The view system can be used to build applications. The display interface can be composed of one or more views. For example, a display interface including a short message notification icon may include a view for displaying text and a view for displaying pictures.

[0103] The telephone manager is used to provide the communication function of the electronic device 100.

[0104] The resource manager provides various resources for applications, such as localized strings, icons, pictures, layout files, video files, etc.

[0105] The notification manager enables applications to display notification information in the status bar, can be used to convey notification-type messages, can automatically disappear after a short stay without user interaction. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as a notification of a background running application, or can be a notification that appears on the screen in the form of a dialogue window.

[0106] In some examples, the application framework layer may further include a routing framework. The routing framework can implement the jump of in-application pages. For example, the routing framework can implement the jump from page 1 of the first application to page 2 of the first application.

[0107] In some examples, the routing framework can also provide multiple interfaces, and different interfaces can implement in-application page jumps in different operating systems. Moreover, each interface can provide the function of marking application pages.

[0108] The developer of the application can configure the page mark of the application page through the above interfaces, and the page mark is used to indicate that the application page can be pulled up by other applications.

[0109] Alternatively, after the application is pulled up by other applications, the application can also call the above interfaces to configure the page mark for the pulled-up page.

[0110] When the currently displayed application page on the screen has a page mark and a return gesture is received, the electronic device 100 can implement page jumps between applications, that is, the currently displayed application page with a page mark can be switched to the page of other applications that pulled up the page.

[0111] The system service layer can include multiple functional modules. For example: Surface Manager, Media Libraries, 3D graphics processing library (e.g., OpenGL ES), 2D graphics engine (e.g., SGL, Vulkan), etc.

[0112] The Surface Manager is used to manage the display subsystem and provide the fusion of 2D and 3D layers for multiple application programs.

[0113] The Media Libraries support the playback and recording of various common audio and video formats, as well as static image files, etc. The Media Libraries can support multiple audio and video coding formats, such as: MPEG4, H.264, MP3, AAC, AMR, etc.

[0114] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, synthesis, and layer processing, etc.

[0115] The 2D graphics engine is a drawing engine for 2D drawing.

[0116] In some examples, the system service layer can also include a running management service. The running management service can manage the task stack of the application and implement the above-mentioned page jumps between applications. Among them, when one application pulls up another application, the running management service will record the pull-up relationship between the applications (or application pages).

[0117] For example, see Figure 5As shown in (a), when the user uses Application A, if Application A launches Page B3 of Application B, the running management service can add Page B3 to the task stack of Application B (Pages B1 and B2 of Application B already exist in the task stack), and instruct the screen to display Page B3. Since Page B3 is launched by Application A, Page B3 has a pre-configured page marker. After the user makes a return gesture on the screen displaying Page B3, the running management service determines that Page B3 has a page marker, and thus determines that Page B3 is launched by another application. The running management service then determines, based on the launch relationship, that Page B3 is launched by Application A, and thus instructs the screen to display the page of Application A, realizing the page jump between Application A and Application B without passing through Pages B2 and B1 in the task stack.

[0118] For another example, referring to Figure 5 As shown in (b), when the user uses Application A, if Application A launches Page B3 of Application B, the running management service can add Page B3 to the temporary task stack of Application B, and instruct the screen to display Page B3. The temporary task stack of Application B does not affect the task stack of Application B (i.e., the main task stack). The temporary task stack stores the pages of Application B launched by other applications and the pages of Application B opened after that page, while the main task stack stores the pages of Application B launched by the desktop or jumped within the application. After the user makes a return gesture on the screen displaying Page B3, if Page B3 is the page at the bottom of the temporary task stack, the running management service determines that Page B3 is launched by another application. The running management service then determines, based on the launch relationship, that Page B3 is launched by Application A, and thus instructs the screen to display the page of Application A, realizing the page jump between Application A and Application B.

[0119] The kernel layer is the layer between hardware and software. The kernel layer includes at least a display driver, a camera driver, an audio driver, and a sensor driver.

[0120] When implementing the method for page jump between applications provided in the embodiments of the present application based on the above electronic device, the user can follow the daily usage habit and make a return gesture on the launched page. The electronic device can jump back from the displayed page of the launched party to the page of the launching party, which can ensure the user experience; and the user can also control the page jump with one hand, making the user's operation more convenient; in addition, the above method can directly jump back from the launched page to the page of the launching party without going through multiple layers of jumps of the launched party pages in the middle, without wasting much time, thus improving the efficiency of page jump and improving the user experience.

[0121] The above-mentioned electronic device can be a terminal device such as a mobile phone, a tablet computer, a personal computer, a wearable device (such as a smart watch, a smart bracelet, etc.), a smart home device (such as a television, etc.), a car machine (such as a vehicle-mounted terminal), etc.

[0122] In the following embodiments, taking the electronic device as a mobile phone as an example, the method for page jumping between applications mentioned above will be described.

[0123] In some embodiments, before the application is put on the shelf, the developer of the application will call the interface provided by the operating system or the routing framework of the operating system to configure the page mark of the application page according to the operating system adapted by the application.

[0124] Exemplarily, the provided interface is StartActivity, the provided interface is pushViewController, HarmonyOS the provided interface is pushPath.

[0125] The above-mentioned page mark is used to indicate that the application page is a page pulled up by other applications, or is used to indicate that the application page can be pulled up by other applications. That is to say, in an application, pages pulled up by other applications are all configured with page marks.

[0126] In some embodiments, after the application is put on the shelf and installed on the mobile phone, as shown in Figure 6 the method for page jumping between applications mentioned above may include the following steps S601 - S604.

[0127] S601. The mobile phone displays the first page of the first application.

[0128] It can be understood that the first application represents the pulling party in the mobile phone that can pull up other applications.

[0129] In some examples, the first page can be any page in the first application, and when the user performs an operation on the first page, it can trigger the first application to pull up the page of other applications.

[0130] Exemplarily, when the first application is a shopping application, the first page can be an order confirmation page. When the user performs a payment operation on the order confirmation page, such as clicking a function control representing payment, etc., it can trigger the shopping application to pull up the payment page of the payment application.

[0131] Exemplarily, when the first application is a shopping application, the first page can be a login page. When the user performs an operation of logging in with the account of the chat application on the login page, such as clicking a function control representing login, etc., it can trigger the shopping application to pull up the authorization page of the chat application.

[0132] Exemplarily, when the first application is a video application, the first page can be a live page with a link to a certain product. When the user performs an operation of clicking on the product link on the live page, the video application can be triggered to pull up the product page of the shopping application.

[0133] S602. After the mobile phone responds to the operation of the first application to pull up the second page of the second application, it displays the second page of the second application.

[0134] It can be understood that the second application represents the pulled party that is pulled up by other applications in the mobile phone.

[0135] In some examples, the second page is a page in the second application that can be pulled up by other applications. In S602, the mobile phone can present the user with the page transition effect between the applications that jumps from the first page to the second page.

[0136] Exemplarily, the first application is a shopping application, the second application is a payment application, the first page is an order confirmation page, and the second page is a payment page. As shown in (a) of Figure 7 , after the payment page is pulled up by the shopping application, the page displayed on the mobile phone jumps from the order confirmation page to the payment page, and the payment page displays payment information such as price, account number, password prompt box, etc.

[0137] Exemplarily, the first application is a shopping application, the second application is a chat application, the first page is a login page, and the second page is an authorization page. As shown in (b) of Figure 7 , after the authorization page is pulled up by the shopping application, the page displayed on the mobile phone jumps from the login page to the authorization page, and the authorization page displays login information such as a prompt for authorized login.

[0138] Exemplarily, the first application is a video application, the second application is a shopping application, the first page is a live page, and the second page is a product page. As shown in (c) of Figure 7 , after the product page is pulled up by the video application, the page displayed on the mobile phone jumps from the live page to the product page.

[0139] In some examples, the first application and the second application each have their own main task stacks, where the main task stack is used to save the pages opened in the first application or the second application.

[0140] Exemplarily, after the user clicks on the icon of the application on the mobile phone desktop, the application is pulled up by the desktop of the mobile phone, that is, the application is opened. After the application is opened, the mobile phone displays the home page of the application. Correspondingly, the mobile phone will also add this page to the main task stack of the application. After that, if the user continues to click on the control or make a gesture on the home page of the application, causing other pages of the application to be opened, the mobile phone will also add the other pages to the main task stack of the application.

[0141] After the second page of the second application is launched by the first application, the mobile phone can add the second page to the main task stack corresponding to the second application.

[0142] In some examples, since the pages in the second application that can be launched by other applications are all pre-configured with page markers, the second page saved in the main task stack is also configured with a page marker.

[0143] In some examples, the mobile phone can also obtain parameter information for indicating the second page from the first application, and send the parameter information to the second application. The second application determines the second page according to the parameter information, and then the mobile phone displays the second page.

[0144] For example, after the user performs a certain operation on page A1 of application A, application A is triggered to launch page B3 of application B. In this case, application A will send parameter information indicating page B3 to the running management service in the mobile phone. The running management service will send the parameter information to application B, and application B determines the page B3 that needs to be launched according to the parameter information, so that the running management service then instructs the mobile phone to display page B3.

[0145] Or, after receiving the parameter information, the running management service can itself determine the page B3 of application B that needs to be launched according to the parameter information, so that the running management service then instructs the mobile phone to display page B3.

[0146] In this way, when responding to the operation of the first application to launch the page of the second application, the mobile phone can more accurately determine the page of the second application to be launched and displayed through the parameter information sent by the first application, bringing a better user experience to the user.

[0147] S603. The mobile phone receives a return gesture on the second page configured with a page marker being displayed.

[0148] In some examples, the above return gesture can be a return gesture that the user is accustomed to using when operating the mobile phone, and can also be called a global return gesture. The return gesture can be a gesture of swiping from the edge of the screen towards the middle of the screen. For example Figure 8 the gesture of the finger swiping right on the left edge of the screen shown in (a) in the figure, or, for another example Figure 8 the gesture of the finger swiping left on the right edge of the screen shown in (b) in the figure, etc.

[0149] Since these return gestures are all return gestures that are commonly used by the user or that the user is more accustomed to, when the user operates the second page displayed on the mobile phone or operates the mobile phone through these return gestures, it also conforms to the user's usage habits and ensures the user's experience.

[0150] S604. In response to a return gesture, the mobile phone displays the first page of the first application.

[0151] It can be understood that the second page is configured with a page marker. When the mobile phone displays the second page with the page marker, if it receives a return gesture, it will display the first page. For example, as shown in (a) of Figure 9 , when Application A pulls up Page B3 of Application B while displaying Page A1, when the mobile phone displays Page B3 with the page marker and receives a return gesture, it will display Page A1 of Application A. If the mobile phone receives a return gesture while displaying a page without a page marker, it will perform a page return within the application, that is, jump to display the previous page of this page in the main task stack of the application, or place the page in the background of the mobile phone and display the mobile phone desktop. For example, as shown in (b) of Figure 9 , when the mobile phone displays Page B2 of Application B and receives a return gesture, it will display Page B1 of Application B.

[0152] In S604, the mobile phone can present a page jump effect for the user to directly jump back from the second application to the first application.

[0153] In the solutions of S601 - S604 above, after the second page is pulled up, the mobile phone can save the second page with the page marker in the main task stack of the second application. After that, when the mobile phone displays the second page with the page marker, it will respond to the return gesture and return to the first page of the first application, realizing page jump between applications. Such a page jump is directly achieved across applications. If there are other pages in the main task stack of the second application before the second page, there is no need to perform page jumps layer by layer in the main task stack to return, thus saving the time for page jumps between applications and improving the efficiency of page jumps.

[0154] Moreover, in the above solutions, the page of the pulled-up second application remains in the main task stack of the second application, which is also convenient for the second application to manage the page. The user can use common return gestures according to usual usage habits, etc., to achieve page jumps between applications, which can ensure the user experience. In addition, the user can operate on the screen with one hand to control the page jump, making the user's operation more convenient.

[0155] In some examples, the above second application may include multiple pages. After the second application is pulled up by the first application and the second page is displayed, the user can continue to operate on the second page, causing the second application to receive a page jump event, so that the phone displays some other pages of the second application, such as the third page, and the user can also continue to browse some other pages of the second application. In this case, after the second page in the main task stack of the second application, the phone will continue to add some other pages of the second application. After that, if the phone receives a return gesture while displaying some other pages of the second application, a page return jump within the second application is realized.

[0156] For example, as shown in Figure 10 (a), the main task stack of Application B includes Page B1 and Page B2. After Page B3 of Application B is pulled up by Application A, the phone adds Page B3 to the main task stack (Page B3 is configured with a page marker), and the phone displays Page B3 of Application B. If Application B receives a page jump event, the phone displays Page B4 of Application B corresponding to the page jump event, where the page jump event is used to indicate that the displayed Page B3 jumps to Page B4. And, after Page B4 is jumped, the phone can add Page B4 to the above main task stack, and Page B4 is pushed onto the stack after Page B3.

[0157] After that, as shown in Figure 10 (b), the phone receives a return gesture while displaying Page B4, and in response to the return gesture, displays Page B3. Since Page B3 is not configured with a page marker, the phone can determine that Page B3 is not pulled up by other applications. Therefore, the phone does not perform a page jump between applications, but according to the structural characteristics of the main task stack, displays Page B3 before Page B4. After that, when the phone receives a return gesture while displaying Page B3, it responds to the return gesture and displays Page A1 of Application A.

[0158] The above page jump event can be triggered automatically by the second application or triggered by the second application after receiving a user operation. For example, when the phone displays the second page and the user makes an operation of swiping the finger upward on the phone screen, the second application receives a page jump event; for another example, when the phone displays the second page and the user clicks the "next page" control on the second page, the second application receives a page jump event; for another example, when the phone displays the second page and the user clicks on a certain title, a certain piece of content or a certain link on the second page, the second application receives a page jump event.

[0159] In the above example, if the mobile phone receives a return gesture on a page without a page mark configured in the second application being displayed, the mobile phone will first perform a jump of the page in the main task stack, jumping the displayed page to the page before this page in the main task stack to achieve page jumping within the second application. After the mobile phone displays the second page, if it receives a return gesture again, it will directly display and jump to the first page of the first application. In this way, direct page jumping between applications can also be achieved, thereby saving time and improving the efficiency of page jumping.

[0160] In some embodiments, the above page mark may not be pre-configured either, but is configured by the second application itself after the page of the second application is pulled up. In this case, after the electronic device responds to the operation of the first application pulling up the second page of the second application and displays the second page of the second application, then, when the electronic device receives an operation to return to the desktop on the displayed second page, it cancels the page mark of the second page and displays the desktop.

[0161] Among them, when the electronic device receives an operation to return to the desktop on the displayed second page, it means that the call chain between the second application and the first application is disconnected, that is, the call relationship between the second page and the first page of the first application no longer exists. Then, when the call chain is disconnected, the page mark of the second page does not need to exist either, so that the electronic device can cancel the page mark of the second page.

[0162] In some embodiments, as shown in Figure 11 the above method for page jumping between applications may further include the following steps S1101 - S1104.

[0163] S1101. The mobile phone displays the first page of the first application.

[0164] Among them, the first application and the first page may refer to the content in the foregoing embodiment S601, which will not be elaborated here.

[0165] S1102. After the mobile phone responds to the operation of the first application pulling up the second page of the second application, it displays the second page of the second application.

[0166] Among them, the second application and the second page may refer to the content in the foregoing embodiment S602, which will not be elaborated here. And, in S1102, the mobile phone can present the user with the page jumping effect between the applications that jumps from the first page to the second page.

[0167] In some examples, in addition to the main task stack of the second application, the mobile phone can also create a temporary task stack for the second application and save the second page in the temporary task stack. It can be understood that the second page is the first page to be pushed onto the temporary task stack.

[0168] In some examples, before creating a temporary task stack for the second application, the mobile phone also needs to obtain the type of launch for the second application or the second page being launched. Among them, the type of launch can indicate whether the second application or the second page is launched by the mobile phone desktop or by other applications. If the mobile phone determines that the second application or the second page is launched by other applications, the mobile phone will create a temporary task stack and add the second page to the temporary task stack; if the mobile phone determines that the second application or the second page is launched by the desktop, the mobile phone will add the second page to the main task stack of the second application.

[0169] For example, after the second page is launched, the running management service can obtain the information of the launcher, such as the mobile phone desktop or an application, etc. Then, the running management service determines the type of launch according to the launcher information. When the type of launch indicates that the second page is launched by other applications, the running management service will create a temporary task stack for the second application.

[0170] In some examples, the mobile phone can also obtain parameter information for indicating the second page from the first application, and send the parameter information to the second application. The second application determines the second page according to the parameter information, and then the mobile phone displays the second page. In this way, when responding to the operation of the first application to launch the page of the second application, the mobile phone can more accurately determine the page of the second application to be launched and displayed through the parameter information sent by the first application, bringing a better user experience to the user.

[0171] S1103. The mobile phone receives a return gesture on the second page being displayed.

[0172] Among them, the return gesture can refer to the content in the foregoing embodiment S603 and will not be elaborated here. Since these return gestures are all return gestures that are commonly used by users or that users are more accustomed to, therefore, when users operate on the second page displayed on the mobile phone or operate on the mobile phone through these return gestures, it also conforms to the user's usage habits and ensures the user's experience.

[0173] It can be understood that since the task stack is a data structure with first-in-last-out, and the second page is the page that is first pushed onto the temporary task stack, when the mobile phone displays the second page, the temporary task stack may only include the second page. Therefore, the above S603 can also be regarded as the mobile phone receiving a return gesture when displaying the page at the bottom of the temporary task stack.

[0174] S1104. In response to the return gesture, the mobile phone displays the first page of the first application.

[0175] It can be understood that the second page is the page that is first pushed onto the temporary task stack. When the mobile phone displays the second page that is first pushed onto the temporary task stack, if it receives a return gesture, it will display the first page. For example, seeFigure 12 As shown in (a) of Figure 12 Figure 12 , when the mobile phone displays page B3 of application B which is pulled up by application A when application A displays page A1 of the display page, and receives a return gesture when the mobile phone displays page B3 which first enters the temporary task stack, the page A1 of application A will be displayed. If the mobile phone receives a return gesture on other pages in the displayed temporary task stack, a page return within the application will be performed, that is, the previous page of this page in the temporary task stack will be jumped to and displayed. For example, see

[0176] In S1104, the mobile phone can present a page jump effect for the user to directly jump back from the second application to the first application.

[0177] It can be understood that the above temporary task stack stores the pages in the second application that are pulled up by other applications and other pages in the second application that are opened after this page. The main task stack stores the pages in the second application that are pulled up by the desktop or the pages that are opened within the application.

[0178] In some examples, after the mobile phone jumps back to display the first page of the first application, it means that the pull-up task of the second page has been completed, or it means that the call chain between the first application and the second application is disconnected. In this case, there are no pages left in the temporary task stack of the second application, and the temporary task stack of the second application can be destroyed. After the page of the second application is pulled up again by the first application or other applications, the mobile phone will create a temporary task stack for the second application again.

[0179] In some examples, after the second page is pulled up, the second application is placed in the foreground of the mobile phone to run, indicating that the call chain between the first application and the second application exists. After the second application is placed in the background of the mobile phone, it can indicate that the call chain between the first application and the second application is disconnected. In this case, the temporary task stack of the second application can be destroyed. After the page of the second application is pulled up again by the first application or other applications, the mobile phone will create a temporary task stack for the second application again.

[0180] The above-mentioned temporary task stack of the application will not affect the main task stack of the application. After the call chain between the first application and the second application is disconnected, the temporary task stack will be destroyed, while the main task stack of the second application will continue to exist. When the user places the second application in the foreground of the mobile phone again, the pages opened in the second application will be added to the main task stack of the second application.

[0181] In some examples, when the temporary task stack of the second application is destroyed, if at least one page is still saved in the temporary task stack of the second application, the at least one page is saved in the main task stack of the second application to ensure that at least one page that has been opened in the second application will not be destroyed. In this way, when the user uses the second application again, the user can still view the last page browsed before, thus ensuring the user experience.

[0182] For example, page B1 and page B2 are saved in the main task stack of the second application, and page B3, page B4, and page B5 are saved in the temporary task stack of the second application. When the temporary task stack is destroyed, the mobile phone saves page B3, page B4, and page B5 in the main task stack, so that the main task stack sequentially includes page B1, page B2, page B3, page B4, and page B5. After the user places the second application in the foreground of the mobile phone again, the page of the second application displayed is page B5. When the user makes a back gesture on page B5, the mobile phone can jump to display page B4. When the user makes a back gesture on page B4, the mobile phone can jump to display page B3. When the user makes a back gesture on page B3, the mobile phone can jump to display page B2...

[0183] In the solutions of S1101 - S1104 above, after the second page is pulled up, the mobile phone saves the second page in the temporary task stack of the second application. The mobile phone will only respond to the back gesture and return to the first page of the first application when displaying the second page that was first pushed onto the stack (or the page at the bottom of the temporary task stack) in the temporary task stack, realizing page jumping between applications. Such page jumping is directly achieved across applications. If there are other pages in the main task stack of the second application before the second page, there is no need to perform page jumping layer by layer in the main task stack to return, thus saving the time for page jumping between applications and improving the efficiency of page jumping.

[0184] Moreover, in the above solutions, the developer of the application does not need to configure page tags for the pages that can be pulled up. The user can also use common back gestures to achieve page jumping between applications according to usual usage habits, etc., which can ensure the user experience. In addition, the user can operate on the screen with one hand to control page jumping, making the user's operation more convenient.

[0185] In some examples, the above second application may include multiple pages. After the second application is launched by the first application and the second page is displayed, the user can continue to operate on the second page, causing the second application to receive a page jump event. As a result, the mobile phone displays some other pages of the second application, and the user can continue to browse some other pages of the second application. In this case, after the second page in the temporary task stack of the second application, the mobile phone will continue to add some other pages of the second application. After that, if the mobile phone receives a return gesture while displaying some other pages of the second application, a page return jump within the second application is achieved.

[0186] For example, after the second page is displayed, if the second application receives a page jump event, the mobile phone displays the third page of the second application corresponding to the page jump event, where the page jump event is used to indicate the jump from the displayed second page to the third page. And, after the third page is jumped to, the mobile phone can add the third page to the temporary task stack of the second application, and the third page is pushed onto the stack after the second page. After that, the mobile phone receives a return gesture while displaying the third page, and in response to the return gesture, the second page is displayed. Since the third page is not the first page pushed onto the temporary task stack (or not the page at the bottom of the temporary task stack), the mobile phone can determine that the third page is not launched by another application. Therefore, instead of performing a page jump between applications, the mobile phone displays the second page before the third page according to the structural characteristics of the temporary task stack. After that, when the mobile phone receives a return gesture while displaying the second page, it responds to the return gesture and displays the first page of the first application.

[0187] The above page jump event can refer to the content in the foregoing embodiments and will not be elaborated here.

[0188] In the above example, if the mobile phone receives a return gesture when it is not the first page pushed onto the temporary task stack of the second application, the mobile phone will first perform a page jump in the temporary task stack, jumping the displayed page to the page before this page in the temporary task stack to achieve a page jump within the second application. When the mobile phone displays the second page and then receives a return gesture, it will directly jump to the first page of the first application. In this way, a direct page jump between applications can also be achieved, saving time and improving the efficiency of page jumps.

[0189] In some examples, the second application can also launch the pages of other applications. After the first application launches the page of the second application, if the second application then launches another application, this situation can also indicate that the call chain between the first application and the second application is disconnected. The temporary task stack of the second application will also be destroyed, and the mobile phone can also create a temporary task stack for the other application. After that, the page jump method between the second application and the other application can refer to the page jump method between the first application and the second application in the foregoing embodiments. Herein, the other application can be an application other than the first application, or the other application can include the first application.

[0190] For example, after the mobile phone displays the second page, if the second application launches the fourth page of the third application, the mobile phone will display the fourth page, destroy the temporary task stack of the second application, and add the fourth page to the temporary task stack of the third application. Herein, the fourth page is the first page to be pushed onto the temporary task stack of the third application. After that, the mobile phone receives a return gesture on the displayed fourth page and, in response to the return gesture, displays the second page of the second application. Thus, page jumps between applications are realized.

[0191] In the above example, the second application can also launch the page of the third application. In this case, after the fourth page of the third application is launched, the fourth page is saved in the temporary task stack of the third application, and at the same time, the temporary task stack of the second application is destroyed. The mobile phone will only respond to the return gesture and return to the second page of the second application when displaying the fourth page, which is the first page to be pushed onto the temporary task stack, thus realizing page jumps between applications. Such page jumps are directly realized across applications. If there are other pages in the main task stack of the second application before the second page, there is no need to perform page jumps layer by layer in the main task stack to return, thereby saving the time for page jumps between applications and improving the efficiency of page jumps.

[0192] The above method in the embodiments of the present application can realize page jumps between applications. In some other embodiments, the above method can also realize jumps between applets in an application, jumps between an application and an applet in another application, etc. Herein, the developer of the applet can configure page markers for the applet page, or the mobile phone can create a temporary task stack for the applet. For more specific implementation methods, reference can be made to the content in the foregoing embodiments, which will not be elaborated herein.

[0193] In the above embodiments, the method for realizing page jumps between applications in the embodiments of the present application by the mobile phone is used as an example to illustrate this method. In some other embodiments, terminal devices such as tablet computers, personal computers, wearable devices, smart home devices, and vehicle-mounted devices can also realize the above method for page jumps between applications. For specific implementation methods, reference can be made to the content in the foregoing embodiments, which will not be elaborated herein.

[0194] An embodiment of the present application further provides an electronic device, such as Figure 13 shown, the electronic device may include one or more processors 1301, a memory 1302, and a communication interface 1303.

[0195] Among them, the memory 1302 and the communication interface 1303 are coupled to the processor 1301. For example, the memory 1302 and the communication interface 1303 may be coupled to the processor 1301 through a bus 1304.

[0196] Among them, the communication interface 1303 is used for data transmission with other devices. Computer program code is stored in the memory 1302. The computer program code includes computer instructions. When the computer instructions are executed by the processor 1301, the electronic device executes the method for page jump between applications in the embodiment of the present application.

[0197] Among them, the processor 1301 may be a processor or a controller. For example, it may be a CPU, a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in connection with the present disclosure. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.

[0198] Among them, the bus 1304 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The above bus 1304 may be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, Figure 13 only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

[0199] An embodiment of the present application further provides a computer-readable storage medium. The computer-readable storage medium includes computer instructions. When the computer instructions run on the electronic device, the electronic device executes the relevant method steps in the above method embodiment.

[0200] The embodiments of the present application also provide a computer program product. When the computer program product runs on a computer, it causes the computer to execute the relevant method steps in the above method embodiments.

[0201] Among them, the electronic device, computer-readable storage medium, or computer program product provided by the present application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be elaborated here.

[0202] Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and simplicity of description, only the above division of each functional module is used as an example. In actual applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

[0203] In several embodiments provided by the present application, it should be understood that the disclosed device and method can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some interfaces. The indirect coupling or communication connection of the device or unit can be in an electrical, mechanical or other form.

[0204] The unit described as a separate component may or may not be physically separated. The component displayed as a unit may be a physical unit or multiple physical units, that is, it may be located in one place, or it may be distributed to multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0205] In addition, each functional unit in the various embodiments of the present application can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0206] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of the present application, in essence, or the part that makes a contribution, or all or part of the technical solution, can be embodied in the form of a software product. The software product is stored in a storage medium and includes several instructions for causing a device (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, read only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

Claims

1. A method for page jumping between applications, applied to an electronic device, characterized in that, Including: Displaying a first page of a first application; After an operation of pulling up a second page of a second application in response to the first application, displaying the second page of the second application; wherein, the second page is added to a main task stack of the second application, the second page is configured with a page marker; the main task stack is used to save the pages opened in the second application; the page marker is used to indicate that the second page is pulled up by another application; Receiving a return gesture on the displayed second page; In response to the return gesture, displaying the first page of the first application.

2. The method according to claim 1, wherein The second application includes multiple pages, and the multiple pages include the second page and a third page; after displaying the second page of the second application, the method further includes: After the second application receives a page jump event, displaying the third page of the second application; the page jump event is used to indicate a jump from the second page to the third page; the third page is added to the main task stack of the second application; Receiving a return gesture on the displayed third page; In response to the return gesture, displaying the second page of the second application.

3. The method according to claim 1 or 2, characterized in that, The displaying the second page of the second application includes: Obtaining parameter information from the first application; the parameter information is used to indicate the second page; Sending the parameter information to the second application; Obtaining the second page determined by the second application according to the parameter information; Displaying the second page.

4. The method according to any one of claims 1-3, characterized in that, The return gesture is a gesture of swiping from the edge of the screen towards the middle of the screen.

5. The method according to any one of claims 1 to 4, characterized in that, The operation of pulling up the second page of the second application in response to the first application includes: Receiving an operation of a user on a function control of the first page; In response to the operation, displaying the second page; wherein, the second page displays content associated with the first page or the function control.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: After an operation of pulling up the second page of the second application again in response to the first application, displaying the second page of the second application; Receiving an operation of returning to the desktop on the displayed second page, canceling the page marker of the second page; Displaying the desktop.

7. A method for page jumping between applications, which is applied to an electronic device, characterized in that, Including: Displaying a first page of a first application; After an operation of pulling up a second page of a second application in response to the first application, displaying the second page of the second application; the second page is added to a temporary task stack of the second application; The temporary task stack of the second application is at least used to save the second page pulled up through the first page, and the second page is the first page to be pushed onto the temporary task stack of the second application; Receiving a return gesture on the displayed second page; In response to the return gesture, displaying the first page of the first application.

8. The method according to claim 7, wherein The temporary task stack is further used to save at least one page opened in the second application after the second page is pulled up; after displaying the second page of the second application, the method further includes: After the second application receives a page jump event, display the third page of the second application; the page jump event is used to indicate a jump from the second page to the third page; the third page is added to the temporary task stack of the second application; Receive a return gesture on the displayed third page; In response to the return gesture, display the second page of the second application and remove the third page from the temporary task stack.

9. The method according to claim 7 or 8, characterized in that After the first page of the first application is displayed, the temporary task stack of the second application is destroyed; or, after the second application is placed in the background, the temporary task stack of the second application is destroyed.

10. The method according to any one of claims 7-9, characterized in that After the second page of the second application is displayed, the method further includes: After responding to an operation of the second application to launch the fourth page of the third application, display the fourth page of the third application; the fourth page is added to the temporary task stack of the third application; the fourth page is the first page to be pushed onto the temporary task stack of the third application; Receive a return gesture on the displayed fourth page; In response to the return gesture, display the second page of the second application.

11. The method according to claim 10, wherein The method further includes: After responding to an operation of the second application to launch the fourth page of the third application, destroy the temporary task stack of the second application; When at least one page is still saved in the temporary task stack of the second application, save the at least one page to the main task stack of the second application; the main task stack is used to save the pages opened in the second application.

12. The method according to any one of claims 7-11, characterized in that, The displaying the second page of the second application includes: Obtain parameter information from the first application; the parameter information is used to indicate the second page; Send the parameter information to the second application; Obtain the second page determined by the second application according to the parameter information; Display the second page.

13. The method according to any one of claims 7 to 12, characterized in that The responding to an operation of the first application to launch the second page of the second application includes: Receive an operation of the user on the function control of the first page; In response to the operation, display the second page; wherein, the second page displays content associated with the first page or the function control.

14. The method according to any one of claims 7-13, characterized in that, The return gesture is a gesture of swiping from the edge of the screen towards the middle of the screen.

15. An electronic device, characterized in that, Comprising a memory and one or more processors; the memory is coupled to the processor; wherein, computer program code is stored in the memory, and the computer program code includes computer instructions, and when the computer instructions are executed by the processor, the electronic device is caused to execute the method for inter-application page jump according to any one of claims 1-6, or execute the method for inter-application page jump according to any one of claims 7-14.

16. A computer-readable storage medium, characterized in that, Comprising computer instructions, and when the computer instructions run on an electronic device, the electronic device is caused to execute the method for inter-application page jump according to any one of claims 1-6, or execute the method for inter-application page jump according to any one of claims 7-14.

17. A computer program product, characterized in that, When the computer program product runs on a computer, the computer is caused to execute the method for inter-application page jump according to any one of claims 1-6, or execute the method for inter-application page jump according to any one of claims 7-14.

Images