Application page display method and electronic equipment

Abstract

The invention provides an application page display method and electronic equipment. The method comprises the steps of displaying a first page of a first application; in response to a first operation of a user, a first page is displayed in the first area, a second page of the first application is displayed in the second area, and the first area and the second area do not coincide; receiving a second operation of the user on the first page; in response to the second operation, displaying a third page of the first application in the first area, and displaying a second page in the second area; and / or receiving a third operation of the user on the second page; and in response to the third operation, displaying the first page in the first area, and displaying a fourth page of the first application in the second area. Therefore, different split screens of the electronic equipment can be decoupled to independently display a plurality of pages of any application, a new page opened in any split screen does not interfere with pages displayed in other split screens, and multi-task or immersive experience is provided for a user.

Description

[0001] This application is a divisional application. The application number of the original application is 202010955785.3, and the filing date of the original application is September 11, 2020. The entire content of the original application is incorporated herein by reference. Technical Field

[0002] This application relates to the field of electronic technology, and in particular, to an application page display method and an electronic device. Background Art

[0003] In large-screen electronic devices, based on the technology of equal-proportion magnification, the display effect is very unsatisfactory, and various problems such as large icons, large fonts, large pictures, stretching and deformation, dislocation, and truncation of pages / fonts / pictures occur. If the screen ratio of the electronic device needs to be adapted, the development workload of the application program is too large.

[0004] In the current in-application split-screen display solution, the pages displayed in the left and right split-screens have a strongly coupled correlation relationship, that is, the new pages opened in the left split-screen page will be displayed in the right split-screen, resulting in the previously displayed page in the right split-screen being washed away, and the new pages opened in the right split-screen will wash away the page displayed in the left split-screen, affecting the user's multitasking operation. And once the in-application split-screen display solution is started, all pages can only be opened in the split-screen display mode and cannot be freely switched between full-screen display and split-screen display according to the user's needs. Summary of the Invention

[0005] This application provides an application page display method and an electronic device, which can decouple the independent display of multiple pages of any application in different split-screens of the electronic device, and the new pages opened in any split-screen will not interfere with the pages displayed in other split-screens, providing the user with a multitasking or immersive experience.

[0006] In a first aspect, an application page display method according to this application includes: displaying a first page of a first application; in response to a first operation of the user, displaying the first page in a first area and displaying a second page of the first application in a second area, where the first area and the second area do not overlap.

[0007] Receiving a second operation of the user on the first page; in response to the second operation, displaying a third page of the first application in the first area and displaying the second page in the second area. And / or,

[0008] Receiving a third operation of the user on the second page; in response to the third operation, displaying the first page in the first area and displaying a fourth page of the first application in the second area.

[0009] Among them, the first operation can be a multiple-click operation, a single-click operation, a long-press operation, or other types of single or multiple operations, or a single or multiple operations after combining different types. This application does not limit the specific implementation manner of the first operation.

[0010] Among them, the first page can be any page in the first application. For example, the first page can be the main page of the first application, or a page other than the main page in the first application. The second page can be any page in the first application, and the page content of the first page and the second page can be the same or different. This application does not limit this.

[0011] Among them, both the first area and the second area are the display areas of the electronic device. This application does not limit the area sizes of the first area and the second area. In addition, the first area and the second area can cover the entire display area of the electronic device, or the first area and the second area can cover a partial display area of the electronic device. This application does not limit this.

[0012] In some embodiments, if the electronic device is in the landscape screen state, the first area is the display area of the left screen of the electronic device, and the second area can be the display area of the right screen of the electronic device; or, the first area is the display area of the right screen of the electronic device, and the second area can be the display area of the left screen of the electronic device. If the electronic device is in the portrait screen state, the first area is the display area of the upper screen of the electronic device, and the second area can be the display area of the lower screen of the electronic device; or, the first area is the display area of the lower screen of the electronic device, and the second area can be the display area of the upper screen of the electronic device.

[0013] In a possible design, the area sizes of the first area and the second area are equal. Thereby, the visual experience of the user browsing the first page and the second page is improved.

[0014] Among them, the second operation is an operation triggered on the first page, and the types of the second operation include but are not limited to at least one of click, long-press, drag, etc. The third operation is an operation triggered on the second page, and the types of the third operation include but are not limited to at least one of click, long-press, drag, etc.

[0015] Among them, the third page can be other pages in the first application except the first page, and the fourth page can be other pages in the first application except the second page. This application does not limit this.

[0016] Those skilled in the art can understand that an Activity is a display component of an Android application (APP). An Activity provides a window for interaction with users and is used to display the content of the APP. An Activity is usually a separate window that can fill the display area of the electronic device's display screen or be smaller than the display area of the electronic device and float above other windows. An APP is usually composed of multiple loosely related Activities. Usually, an APP can specify a certain Activity as the main Activity, which refers to the Activity presented to the user when the APP is first launched. Correspondingly, the window presented by the main Activity is the main page in the APP. For example, the main page of the WeChat application is the page corresponding to the chat dialog list.

[0017] A Task is a collection of Activities. It manages the Activities in the stack (i.e., the task stack), and this stack is also called the back stack. The order of the Activities in the stack is stored in the order in which the Activities are opened.

[0018] Furthermore, the page mentioned in this application can be understood as an Activity presented to the user by the application, and the area mentioned in this application can be understood as the area displayed by the task stack where the Activity of the application is located. Thus, the display area of any Activity in the task stack corresponding to the first area is less than or equal to the first area, and the display area of any Activity in the task stack corresponding to the second area is less than or equal to the second area.

[0019] Since the first area and the second area do not overlap, the task stack corresponding to the first area is different from the task stack corresponding to the second area, which can ensure that the pages displayed in the first area and the second area do not interfere with each other.

[0020] Based on the foregoing description, when the first page is displayed in the first area and the second page is displayed in the second area, the first task stack corresponding to the first page is different from the second task stack corresponding to the second page, thus ensuring that the display of the first page does not interfere with the display of the second page.

[0021] The task stack corresponding to the third page is different from the task stack corresponding to the second area, which can ensure that the display of the third page does not interfere with the display of the pages such as the second page or the fourth page in the second area. Among them, the task stack corresponding to the third page can be the first task stack or other task stacks other than the first task stack and the second task stack.

[0022] If the task stack corresponding to the fourth page is different from the task stack corresponding to the first area, it can be ensured that the display of the fourth page does not interfere with the display of pages such as the first page or the third page in the first area. Among them, the task stack corresponding to the fourth page can be the second task stack or other task stacks other than the first task stack and the second task stack.

[0023] It should be noted that the above-mentioned task stacks such as the first task stack, the second task stack, and other task stacks are all task stacks of the first application.

[0024] Through the application page display method of the first aspect, when the user processes multiple tasks in parallel, the electronic device can switch any application from the full-screen display main page to the split-screen display of other pages of the application, and the new page opened from any split screen will destroy the page displayed in that split screen and be displayed in that split screen, solving the problem in the related art that the new page opened from any split screen will destroy the pages displayed in other split screens due to the coupling relationship between different split screens, avoiding the display interference between the pages in different split screens, enabling the pages in different split screens to run independently, and providing the user with a multi-task or immersive experience. In addition, after the application starts the in-application split-screen function, the electronic device can, based on the user's needs, switch from the split-screen display of multiple pages of the application to the full-screen display of one page of the application, or switch from the full-screen display of one page of the application to the split-screen display of multiple pages of the application, providing the user with an efficient and flexible multi-window multi-task experience.

[0025] In a possible design, the method further includes: receiving a fourth operation from the user on the third page. In response to the fourth operation, the first page is displayed in the first area, and the second page is displayed in the second area. And / or, receiving a fifth operation from the user on the fourth page. In response to the fifth operation, the first page is displayed in the first area, and the second page is displayed in the second area.

[0026] Among them, the fourth operation is an operation triggered on the third page, and the types of the fourth operation include but are not limited to at least one type such as clicking, long pressing, dragging, etc. In some embodiments, the third page may include a control for indicating the jump from the display of the third page to the display of the first page. And this application does not limit the parameters such as the shape, position, and size of the control. Therefore, the fourth operation is an operation triggered on the control.

[0027] Among them, the fifth operation is an operation triggered on the fourth page, and the types of the fifth operation include but are not limited to at least one type such as clicking, long pressing, dragging, etc. In some embodiments, the fourth page may include a control for indicating the jump from the display of the fourth page to the display of the second page. And this application does not limit the parameters such as the shape, position, and size of the control. Therefore, the fifth operation is an operation triggered on the control.

[0028] Thus, the electronic device can jump from the split-screen display of the third page and the second page to the split-screen display of the first page and the second page, or from the split-screen display of the third page and the fourth page to the split-screen display of the first page and the second page, or from the split-screen display of the first page and the fourth page to the split-screen display of the first page and the second page, thereby being closer to the user's operation and being beneficial to improving the user experience.

[0029] In a possible design, after displaying the first page of the first application and before responding to the first operation of the user, the method further includes: receiving a sixth operation of the user on the second page. In response to the sixth operation, a first control is displayed, and the first control is used to represent splitting the first page and the second page for split-screen display. Receiving the first operation on the first control.

[0030] Wherein, the sixth operation is an operation triggered on the second page, and the types of the sixth operation include but are not limited to at least one of clicking, long-pressing, dragging, etc. And this application does not limit the parameters such as the shape, position, and size of the first control. Therefore, after the first page is displayed, the electronic device can display the second page to the user. At this time, based on the user's willingness to split the screen, when the electronic device receives the second operation on the second page, the first control is displayed. When the electronic device receives the first operation on the first control, the first page can be displayed in the first area, and the second page of the first application can be displayed in the second area, and the first area and the second area do not overlap. Thus, based on the user's willingness, a possible implementation manner for splitting the first page and the second page for split-screen display is provided, which is more in line with the user's usage habits.

[0031] In a possible design, before responding to the first operation of the user, the method further includes: receiving the first operation on the first page. In some embodiments, the first page may include a control, and the control is used to represent splitting the first page and the second page for split-screen display. And this application does not limit the parameters such as the shape, position, and size of the control. Therefore, the fifth operation is an operation triggered on the control.

[0032] In summary, when the electronic device receives the first operation on the first page, the first page can be displayed in the first area, and the second page of the first application can be displayed in the second area, and the first area and the second area do not overlap. Thus, another possible implementation manner for splitting the first page and the second page for split-screen display is provided, providing a smooth browsing experience for the user.

[0033] In one possible design, the method further includes: displaying a second control in an adjacent area of ​​the first area and the second area, the second control being used to adjust the area of ​​the first area and the second area. The adjacent area of ​​the first area and the second area may be an area between the first area and the second area. The present application does not limit parameters such as the shape, position, and size of the second control. Thus, based on the user's wishes, a possible implementation method is provided for adjusting the area of ​​the first area and the second area, which is conducive to improving the user experience.

[0034] In one possible design, the method also includes: receiving a seventh operation of the user on the first page and / or the second page; in response to the seventh operation, displaying a third control, the third control being used to indicate that the first page is displayed in full screen; receiving an eighth operation on the third control; and in response to the eighth operation, displaying the first page.

[0035] Among them, the seventh operation can be an operation triggered on the first page, or an operation triggered on the second page, or an operation triggered on the first page and the second page, and this application does not limit this. In some embodiments, the second page may include a control for displaying a third control. And this application does not limit the shape, position, size and other parameters of the control and the third control. In addition, the type of the seventh operation includes but is not limited to at least one type such as click, long press, and drag.

[0036] The eighth operation may be an operation triggered on the third control, and the type of the eighth operation includes but is not limited to at least one type such as clicking, long pressing, and dragging.

[0037] In summary, when the first page and the second page are displayed in split screen, the electronic device can display the third control when receiving the seventh operation. When the electronic device receives the eighth operation on the third control, it can display the first page. Therefore, based on the user's wishes, a possible implementation method is provided for converting the split screen display of the first page and the second page to the display of the first page, which is more in line with the user's usage habits. Thus, when the application starts the in-application split-screen function for display, any page in the application can be freely switched between full-screen display and split-screen display according to user needs, providing users with an efficient and flexible multi-window multi-tasking experience.

[0038] In one possible design, the method further includes: receiving a ninth operation of the user on the second page. In response to the ninth operation, displaying the first page.

[0039] Among them, the ninth operation may be an operation triggered on the second page, and the types of the ninth operation include, but are not limited to, at least one of clicking, long-pressing, dragging, etc. In some embodiments, the second page may include a control for representing full-screen display of the first page. Moreover, this application does not limit parameters such as the shape, position, and size of this control. Therefore, the ninth operation is an operation triggered on this control.

[0040] In summary, when the first page and the second page are in split-screen display, when the electronic device receives the first operation, the first page can be displayed. Thus, it provides another possible implementation method for converting the split-screen display of the first page and the second page into the display of the first page, providing a smooth browsing experience for the user. Therefore, when this application starts the in-application split-screen function for display, any page in this application can be freely switched between full-screen display and split-screen display according to the user's needs, providing an efficient and flexible multi-window multi-tasking experience for the user.

[0041] Among them, the full-screen display of the first page may include various display methods.

[0042] In a possible design, the first page is displayed in the third area, and the third area includes the first area and the second area. Thus, it provides a possible implementation method for the full-screen display of the first page, showing the first page to the user as large as possible, which is beneficial for the user to browse the first page.

[0043] In a possible design, the first page is displayed in the first area, and the fifth page of the first application is displayed in the second area, and the fifth page is different from both the first page and the second page. Among them, the fifth page may be other pages in the first application except the first page, and the task stack of the fifth page is the same as the first task stack. Thus, it provides another possible implementation method for the full-screen display of the first page, enabling the user to view the page content of more pages.

[0044] In a possible design, the first page is displayed in the fourth area, and the fourth area at least includes part of the first area and part of the second area. Thus, it provides another possible implementation method for the full-screen display of the first page, providing a more comfortable browsing experience for the user.

[0045] In a possible design, the first page corresponds to the first task stack. In response to the user's first operation, the first page is displayed in the first area, and the second page of the first application is displayed in the second area. The first area and the second area do not overlap. Specifically: In response to the first operation, a second task stack is established, and a first message is sent to the first application. The first message is used to identify the first operation, and the first operation is related to the second page. The second page corresponds to the second task stack, and the first task stack is different from the second task stack. A second message is received from the first application. The second message is used to indicate that the first page and the second page are to be displayed in split screen. In response to the second message, the first page is displayed in the first area, and the second page is displayed in the second area.

[0046] Among them, the specific implementation manners of the first message and the second message are not limited in this application. The execution order of the step of the electronic device establishing the second task stack and the step of the electronic device sending the first message to the first application is not sequential. They can be executed sequentially or simultaneously, and this application does not limit this either. Moreover, the step of the electronic device establishing the second task stack needs to be before the electronic device receives the second message.

[0047] Among them, the start mode of the second page is set to the mode of creating a new task stack. Therefore, in response to the first operation, the electronic device can establish the second task stack corresponding to the second page.

[0048] In a possible design, in response to the second message, displaying the first page in the first area and the second page in the second area includes:

[0049] When it is determined based on the second message that the second task stack exists, that the first application supports the in-application split screen function, and that the second page meets the preset requirements for split screen display, based on the identifier of the first task stack, the identifier of the second task stack, and the split screen parameters of the second page, the first page is displayed in the first area in the first task stack, and the second page is displayed in the second area in the second task stack.

[0050] Or,

[0051] When it is determined based on the second message that the first task stack is in the non-split screen mode, that the first application supports the in-application split screen function, and that the second page meets the preset requirements for split screen display, based on the identifier of the first task stack, the identifier of the second task stack, and the split screen parameters of the second page, the first page is displayed in the first area in the first task stack, and the second page is displayed in the second area in the second task stack.

[0052] Thus, when the second task stack has been established, based on the above conditions, the electronic device can realize the process of displaying the first page in the first area in the first task stack and displaying the second page in the second area in the second task stack.

[0053] It should be noted that the condition of determining that the first task stack is in the non-split screen mode can also be replaced by determining whether there is such a task stack as the first task stack.

[0054] In a possible design, the second message includes: a first identifier, a second identifier, and a third identifier. The first identifier is used to indicate splitting the first page and any one page for display. The second identifier is used to represent the split screen position of any one page. The third identifier is the identifier of any one page or the identifier of the second task stack.

[0055] In a possible design, the first page corresponds to the first task stack. In response to the user's first operation, the first page is displayed in the first area, and the second page of the first application is displayed in the second area. The first area and the second area do not overlap. Specifically: in response to the first operation, a third message is sent to the first application. The third message is used to identify the first operation. The first operation is related to the second page, and the second page corresponds to the first task stack; a fourth message is received from the first application. The fourth message is used to indicate splitting the first page and the second page for display; in response to the fourth message, a second task stack is established. The second page is changed from corresponding to the first task stack to corresponding to the second task stack. The first task stack and the second task stack are different; and the first page is displayed in the first area, and the second page is displayed in the second area.

[0056] Among them, the specific implementation manners of the third message and the fourth message in this application are not limited.

[0057] Among them, the start mode of the second page is set to a mode that does not create a new task stack. Therefore, in response to the first operation, the electronic device will not establish the second task stack corresponding to the second page, and at this time, the task stack corresponding to the second page is the first task stack. When the electronic device determines that the fourth message is used to indicate splitting the first page and the second page for display, it establishes the second task stack, and the second page corresponding to the first task stack is changed to corresponding to the second task stack, that is, the Activity of the second page is in the second task stack.

[0058] In a possible design, displaying the first page in the first area and the second page in the second area includes:

[0059] When, based on the fourth message, it is determined that the second page corresponds to the first task stack, the first application supports the in-application split screen function, and the second page meets the preset requirements for split screen display, based on the identifier of the first task stack, the identifier of the second task stack, and the split screen parameters of the second page, the first page is displayed in the first area in the first task stack, and the second page is displayed in the second area in the second task stack. Or,

[0060] When it is determined, based on the fourth message, that the first task stack is in the non-split-screen mode, that the first application supports the in-application split-screen function, and that the second page meets the preset requirements for split-screen display, based on the identifier of the first task stack, the identifier of the second task stack, and the split-screen parameters of the second page, the first page is displayed in the first area in the first task stack, and the second page is displayed in the second area in the second task stack.

[0061] Thus, when the second task stack is not established, based on the above conditions, the electronic device can establish the second task stack and implement the process of displaying the first page in the first area in the first task stack and the second page in the second area in the second task stack.

[0062] It should be noted that the condition of determining that the first task stack is in the non-split-screen mode can also be replaced by determining whether there is such a task stack as the first task stack.

[0063] In a possible design, the fourth message includes: a fourth identifier, a fifth identifier, and a sixth identifier. The fourth identifier is used to indicate split-screen display of the first page and any one page. The fifth identifier is used to represent the split-screen position of any one page. The sixth identifier is the identifier of any one page or the identifier of the first task stack.

[0064] In a possible design, in response to the second operation, the third page of the first application is displayed in the first area. Specifically: receive a fifth message, where the fifth message is used to represent opening the third page from the first page, and the third page corresponds to the first task stack; in response to the fifth message, determine whether the first task stack is in the split-screen mode; when the first task stack is in the split-screen mode, based on the identifier of the first task stack, the identifier of the third page, and the split-screen parameters of the third page, display the third page in the first area in the first task stack. Here, the specific implementation manner of the fifth message in this application is not limited.

[0065] Thus, when the electronic device determines to open the third page from the first page, it can determine whether the first task stack is in the split-screen mode, that is, whether the first page is in the split-screen display state. Thus, when it is determined that the first task stack is in the split-screen mode, the electronic device can display the third page in the first area, and the page in the second area continues to be displayed.

[0066] It should be noted that in addition to the Activity corresponding to the third page being in the first task stack, the Activity corresponding to the third page can also be in other task stacks other than the first task stack and the second task stack, and the task stack corresponding to the first area becomes this other task stack, and the above judgment conditions for displaying the third page remain unchanged.

[0067] In a possible design, in response to a third operation, a fourth page of a first application is displayed in a second region, specifically: receiving a sixth message for indicating opening the fourth page from a second page, where the fourth page corresponds to a second task stack; in response to the sixth message, determining whether the second task stack is in a split-screen mode; when the second task stack is in the split-screen mode, based on the identifier of the second task stack, the identifier of the fourth page, and the split-screen parameters of the fourth page, displaying the fourth page in the second region in the second task stack. Herein, the specific implementation manner of the sixth message in this application is not limited.

[0068] Thus, when the electronic device determines to open the fourth page from the second page, it can determine whether the second task stack is in the split-screen mode, that is, whether the second page is in the split-screen display state. Therefore, when it is determined that the second task stack is in the split-screen mode, the electronic device can display the fourth page in the second region, and the page in the first region continues to be displayed.

[0069] It should be noted that in addition to the Activity corresponding to the fourth page being in the second task stack, the Activity corresponding to the fourth page can also be in other task stacks other than the second task stack and the first task stack, and the task stack corresponding to the second region becomes this other task stack, and the above judgment conditions for displaying the fourth page remain unchanged.

[0070] In a second aspect, this application provides an electronic device, including: a memory and a processor; the memory is used to store program instructions; the processor is used to call the program instructions in the memory to enable the electronic device to execute the application page display method in the first aspect and any possible design of the first aspect.

[0071] In a third aspect, this application provides a chip system, and the chip system is applied to an electronic device including a memory, a display screen, and a sensor; the chip system includes: a processor; when the processor executes the computer instructions stored in the memory, the electronic device executes the application page display method in the first aspect and any possible design of the first aspect.

[0072] In a fourth aspect, this application provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the electronic device is enabled to execute the application page display method in the first aspect and any possible design of the first aspect.

[0073] In a fifth aspect, this application provides a computer program product, including: execution instructions, and the execution instructions are stored in a readable storage medium. At least one processor of the electronic device can read the execution instructions from the readable storage medium, and at least one processor executes the execution instructions to enable the electronic device to implement the application page display method in the first aspect and any possible design of the first aspect. Description of the Drawings

[0074] Figure 1 A structural schematic diagram of an electronic device provided by an embodiment of the present application;

[0075] Figure 2a A software structure block diagram of an electronic device provided by an embodiment of the present application;

[0076] Figure 2b For Figure 2a The software structure block diagram of the parallel window manager (HwMagicWindowManager) in

[0077] Figures 3A - 3F A flowchart of a method for displaying an application page provided by an embodiment of the present application;

[0078] Figures 4A - 4W A schematic diagram of a human-computer interaction interface provided by an embodiment of the present application;

[0079] Figures 5A - 5F A flowchart of a method for displaying an application page provided by an embodiment of the present application;

[0080] Figures 6A - 6K A schematic diagram of a human-computer interaction interface provided by an embodiment of the present application;

[0081] Figures 7A - 7G A schematic diagram of a human-computer interaction interface provided by an embodiment of the present application;

[0082] Figure 8 A flowchart of a method for displaying an application page provided by the present application;

[0083] Figures 9A - 9C A schematic diagram of a human-computer interaction interface provided by an embodiment of the present application. Detailed implementation manners

[0084] In this application, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the relationship between related objects and indicates that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one of the following" or its similar expressions refer to any combination of these items, including any combination of single items or plural items. For example, at least one of a alone, b alone, or c alone can represent: a alone, b alone, c alone, the combination of a and b, the combination of a and c, the combination of b and c, or the combination of a, b, and c, where a, b, and c can be single or multiple. In addition, the terms "first" and "second" are only used for descriptive purposes and cannot be construed as indicating or implying relative importance.

[0085] This application provides an application page display method and an electronic device, which can decouple different split screens of the electronic device to independently display multiple pages of any application, and the newly opened pages in any split screen will not interfere with the pages displayed in other split screens, providing users with a multitasking or immersive experience. In addition, when the application starts the in-application split screen function for display, any page in the application can freely switch between full-screen display and split-screen display according to user needs, providing users with an efficient and flexible multi-window multitasking experience.

[0086] Among them, the in-application split screen function mentioned in this application can be understood as: the electronic device can simultaneously achieve the split-screen independent display of different pages of any application, and the newly opened pages in any split screen will not interfere with the pages displayed in other split screens. In addition, the split screen mentioned in this application refers to a left-right split screen or an up-down split screen.

[0087] Among them, the electronic device can be a tablet computer, a mobile phone (such as a foldable mobile phone, a large-screen mobile phone, etc.), a wearable device, a vehicle-mounted device, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), a smart TV, a smart screen, a high-definition TV, a 4K TV, a smart speaker, a smart projector, etc., which are Internet of Things (IOT) devices. This application does not impose any restrictions on the specific type of the electronic device.

[0088] Next, taking the electronic device as a tablet computer as an example, in combination withFigure 1 , introduce the electronic device involved in this application.

[0089] Figure 1 It is a schematic structural diagram of an electronic device provided by an embodiment of this application. As Figure 1 shown, 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 speaker 170A, a receiver 170B, a microphone 170C, a headphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. Among them, the sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0090] It can be understood that the structure illustrated in this application does not constitute a specific limitation on the electronic device 100. In other embodiments, the electronic device 100 may include more or fewer components than those shown in the figure, or combine certain components, or split certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0091] The processor 110 may include one or more processing units. 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.

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

[0093] A memory can also be set in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can save the instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can directly call it from the said memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0094] In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0095] The I2C interface is a two-way synchronous serial bus, including a serial data line (SDA) and a serial clock line (derail clock line, SCL). In some embodiments, the processor 110 may include multiple groups of I2C buses. The processor 110 can be respectively coupled to the touch sensor 180K, charger, flash, camera 193, etc. through different I2C bus interfaces. For example: The processor 110 can be coupled to the touch sensor 180K through the I2C interface, enabling the processor 110 to communicate with the touch sensor 180K through the I2C bus interface to implement the touch function of the electronic device 100.

[0096] The I2S interface can be used for audio communication. In some embodiments, the processor 110 may include multiple groups of I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the I2S interface to implement the function of answering a call through a Bluetooth headset.

[0097] The PCM interface can also be used for audio communication to sample, quantize, and encode analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via the PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface to implement the function of answering a call through a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0098] The UART interface is a general-purpose serial data bus for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 110 and the wireless communication module 160. For example: The processor 110 communicates with the Bluetooth module in the wireless communication module 160 via the UART interface to implement the Bluetooth function. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the UART interface to implement the function of playing music through a Bluetooth headset.

[0099] The MIPI interface can be used to connect the processor 110 to peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes the camera serial interface (CSI), the display serial interface (DSI), etc. In some embodiments, the processor 110 and the camera 193 communicate via the CSI interface to implement the shooting function of the electronic device 100. The processor 110 and the display screen 194 communicate via the DSI interface to implement the display function of the electronic device 100.

[0100] The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 to the camera 193, the display screen 194, the wireless communication module 160, the audio module 170, the sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0101] The USB interface 130 is an interface that complies with the USB standard specifications. Specifically, it can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transfer data between the electronic device 100 and peripheral devices. It can also be used to connect headphones to play audio. This interface can also be used to connect other electronic devices, such as AR devices, etc.

[0102] It can be understood that the interface connection relationships between the modules illustrated in this application are only illustrative descriptions and do not constitute a structural limitation on the electronic device 100. In other embodiments, the electronic device 100 can also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0103] The charging management module 140 is used to receive a charging input from a charger. Among them, the charger can be a wireless charger or a wired charger. In some embodiments of wired charging, the charging management module 140 can receive the charging input of the wired charger through the USB interface 130. In some embodiments of wireless charging, the charging management module 140 can receive the wireless charging input through the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also supply power to the electronic device through the power management module 141.

[0104] 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 and supplies power to the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, the wireless communication module 160, etc. The power management module 141 can also be used to monitor parameters such as the battery capacity, the number of battery cycles, and the battery health status (leakage, impedance). In some other embodiments, the power management module 141 can also be disposed in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be disposed in the same device.

[0105] The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modulation and demodulation processor, and the baseband processor, etc.

[0106] The antenna 1 and the antenna 2 are used to transmit and receive 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: the antenna 1 can be multiplexed as the diversity antenna of the wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0107] The mobile communication module 150 may provide solutions for wireless communications such as 2G / 3G / 4G / 5G applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 may receive electromagnetic waves through the antenna 1, filter, amplify, and perform other processes on the received electromagnetic waves, and then transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modulation and demodulation processor and convert it into electromagnetic waves through the antenna 1 for radiation. In some embodiments, at least some functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be disposed in the same device.

[0108] The modulation and demodulation processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. Subsequently, the demodulator transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, receiver 170B, etc.), or displays an image or video through the display screen 194. In some embodiments, the modulation and demodulation processor may be an independent device. In other embodiments, the modulation and demodulation processor may be independent of the processor 110 and be disposed in the same device as the mobile communication module 150 or other functional modules.

[0109] The wireless communication module 160 may provide solutions for wireless communications applied to the electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite systems (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 may also receive signals to be sent from the processor 110, perform frequency modulation and amplification on them, and convert them into electromagnetic waves through the antenna 2 for radiation.

[0110] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, such that electronic device 100 can communicate with a network and other devices via wireless communication technologies. The wireless communication technologies may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS), and / or satellite based augmentation systems (SBAS).

[0111] Electronic device 100 implements a display function via a GPU, display screen 194, and an application processor, etc. The GPU is a microprocessor for image processing, and is connected to display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or change display information.

[0112] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

[0113] The electronic device 100 can implement the shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, etc.

[0114] The ISP is used to process the data fed back by the camera 193. For example, when taking a photo, the shutter is opened, and light passes through the lens and is transmitted to the camera photosensitive element. The optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converts it into an image visible to the naked eye. The ISP can also perform algorithm optimization on the noise, brightness, and skin color of the image. The ISP can also optimize parameters such as the exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 193.

[0115] The camera 193 is used to capture static images or videos. An object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard format such as RGB or YUV. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0116] The digital signal processor is used to process digital signals. Besides being able to process digital image signals, it can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy, etc.

[0117] The video codec is used to compress or decompress digital videos. The electronic device 100 can support one or more video codecs. In this way, the electronic device 100 can play or record videos in multiple encoding formats, such as: Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0118] The NPU is a neural-network (NN) computing processor. By drawing on the structure of the biological neural network, such as the transmission mode between human brain neurons, it can quickly process the input information and can also continuously self-learn. Through the NPU, applications such as intelligent cognition of the electronic device 100 can be realized, such as: image recognition, face recognition, speech recognition, text understanding, etc.

[0119] 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 achieve the data storage function. For example, files such as music and videos are saved in the external memory card.

[0120] 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. The internal memory 121 can include a program storage area and a data storage area. Among them, the program storage area can store the operating system, application programs required for at least one function (such as the sound playback function, image playback function, etc.). The data storage area can store the data created during the use of the electronic device 100 (such as audio data, phone book, etc.). In addition, the internal memory 121 can include high-speed random access memory and can also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0121] The electronic device 100 can implement audio functions through the audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and the application processor, etc. For example, music playback, recording, etc.

[0122] 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 audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 can be disposed in the processor 110, or some functional modules of the audio module 170 can be disposed in the processor 110.

[0123] The speaker 170A, also known as the "loudspeaker", is used to convert an audio electrical signal into a sound signal. The electronic device 100 can listen to music or hands-free calls through the speaker 170A.

[0124] The receiver 170B, also known as the "earpiece", is used to convert an audio electrical signal into a sound signal. When the electronic device 100 answers a call or a voice message, the voice can be listened to by bringing the receiver 170B close to the human ear.

[0125] The microphone 170C, also known as the "microphone" or "transmitter", is used to convert a sound signal into an electrical signal. When making a call or sending a voice message, the user can speak by bringing the mouth close to the microphone 170C to input the sound signal into the microphone 170C. The electronic device 100 can be provided with at least one microphone 170C. In some other embodiments, the electronic device 100 can be provided with two microphones 170C, which can not only collect sound signals but also implement a noise reduction function. In some other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C, which can collect sound signals, reduce noise, identify the sound source, and implement functions such as directional recording.

[0126] The headphone jack 170D is used to connect a wired headphone. The headphone jack 170D can be a USB interface 130, or a 3.5 mm open mobile terminal platform (OMTP) standard interface, or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0127] The pressure sensor 180A is used to sense pressure signals and can convert pressure signals into electrical signals. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. The capacitive pressure sensor may include at least two parallel plates having conductive materials. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of the pressure according to the change in capacitance. When a touch operation acts on the display screen 194, the electronic device 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic device 100 can also calculate the position of the touch according to the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities may correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, the instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, the instruction to create a new short message is executed.

[0128] The gyroscope sensor 180B can be used to determine the motion posture of the electronic device 100. In some embodiments, the angular velocity of the electronic device 100 around three axes (i.e., the x, y, and z axes) can be determined by the gyroscope sensor 180B. The gyroscope sensor 180B can be used for anti-shake during shooting. Exemplarily, when the shutter is pressed, the gyroscope sensor 180B detects the angle of jitter of the electronic device 100, calculates the distance that the lens module needs to compensate according to the angle, and makes the lens offset the jitter of the electronic device 100 through reverse movement to achieve anti-shake. The gyroscope sensor 180B can also be used for navigation and somatosensory game scenarios.

[0129] The barometric pressure sensor 180C is used to measure barometric pressure. In some embodiments, the electronic device 100 calculates the altitude according to the barometric pressure value measured by the barometric pressure sensor 180C to assist in positioning and navigation.

[0130] The magnetic sensor 180D includes a Hall sensor. The electronic device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip leather case. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 can detect the opening and closing of the flip according to the magnetic sensor 180D. Furthermore, according to the detected opening and closing state of the leather case or the opening and closing state of the flip, features such as automatic flip unlocking are set.

[0131] The acceleration sensor 180E can detect the magnitude of the acceleration of the electronic device 100 in various directions (generally three axes). When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of the electronic device and is applied to applications such as horizontal and vertical screen switching and pedometers.

[0132] A distance sensor 180F for measuring distance. The electronic device 100 can measure the distance by infrared or laser. In some embodiments, when shooting a scene, the electronic device 100 can use the distance sensor 180F to measure the distance to achieve fast focusing.

[0133] The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light outward through the light emitting diode. The electronic device 100 uses the photodiode to detect the infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, the electronic device 100 can determine that there is no object near the electronic device 100. The electronic device 100 can use the proximity light sensor 180G to detect when the user holds the electronic device 100 close to the ear for a call, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used for automatic unlocking and locking of the holster mode and pocket mode.

[0134] An ambient light sensor 180L is used to sense the ambient light brightness. The electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the sensed ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in the pocket to prevent accidental touch.

[0135] A fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to achieve fingerprint unlocking, access application locks, fingerprint photography, fingerprint answering of incoming calls, etc.

[0136] A temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device 100 executes a temperature processing strategy using the temperature detected by the temperature sensor 180J. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 reduces the performance of the processor near the temperature sensor 180J to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 heats the battery 142 to avoid abnormal shutdown of the electronic device 100 caused by low temperature. In other some embodiments, when the temperature is lower than yet another threshold, the electronic device 100 boosts the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.

[0137] The touch sensor 180K, also known as the "touch panel". The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 together form a touch screen, also known as the "touch display screen". The touch sensor 180K is used to detect touch operations acting thereon or nearby. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In some other embodiments, the touch sensor 180K can also be disposed on the surface of the electronic device 100, at a different position from that of the display screen 194.

[0138] The bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire vibration signals of the vibrating bone mass of the human vocal tract. The bone conduction sensor 180M can also contact the human pulse to receive blood pressure pulsation signals. In some embodiments, the bone conduction sensor 180M can also be disposed in the earphone to form a bone conduction earphone. The audio module 170 can parse out voice signals based on the vibration signals of the vibrating bone mass acquired by the bone conduction sensor 180M to implement the voice function. The application processor can parse out heart rate information based on the blood pressure pulsation signals acquired by the bone conduction sensor 180M to implement the heart rate detection function.

[0139] The button 190 includes a power-on button, a volume button, etc. The button 190 can be a mechanical button or a touch button. The electronic device 100 can receive button inputs to generate key signal inputs related to the user settings and function controls of the electronic device 100.

[0140] The motor 191 can generate vibration prompts. The motor 191 can be used for incoming call vibration prompts and also for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playing, etc.) can correspond to different vibration feedback effects. Touch operations acting on different regions of the display screen 194 can also correspond to different vibration feedback effects for the motor 191. Different application scenarios (such as time reminder, receiving messages, alarm clock, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0141] The indicator 192 can be an indicator light and can be used to indicate the charging state, power change, and can also be used to indicate messages, missed calls, notifications, etc.

[0142] The SIM card interface 195 is used to connect to a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to achieve contact with and separation from the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The types of the multiple cards can be the same or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as calls and data communication. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0143] The software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservices architecture, or a cloud architecture. In this application, the Android system with a layered architecture is taken as an example to exemplarily illustrate the software structure of the electronic device 100. Among them, the type of the operating system of the electronic device in this application is not limited. For example, Android system, Linux system, Windows system, iOS system, Harmony operating system (Harmony OS), etc.

[0144] Figure 2a This is a software structure block diagram of an electronic device provided in an embodiment of this application. As Figure 2a shown, the layered architecture 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 Android system is divided into four layers, from top to bottom are the application layer (APP), the application framework layer (APP framework), the Android runtime, the system libraries, and the kernel layer.

[0145] The application layer can include a series of application packages.

[0146] As Figure 2a shown, the application packages can include applications (APP) such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, game, chat, shopping, travel, instant messaging (such as short message), smart home, device control, etc.

[0147] Among them, the smart home application can be used to control or manage home devices with networking functions. For example, home devices can include electric lights, TVs, and air conditioners. Another example is that home devices can also include anti-theft door locks, speakers, floor cleaning robots, sockets, body fat scales, table lamps, air purifiers, refrigerators, washing machines, water heaters, microwave ovens, rice cookers, curtains, fans, TVs, set-top boxes, doors, and windows, etc.

[0148] In addition, the application package can also include: the home screen (i.e., the desktop), the minus one screen, the control center, the notification center, and other applications.

[0149] Among them, the minus one screen, also known as the "-1 screen", refers to the user interface (UI) obtained by swiping the screen of the electronic device to the right on the home screen until the leftmost split screen is reached. For example, the minus one screen can be used to place some quick service functions and notification messages, such as global search, quick access to a certain page of an application (payment code, WeChat, etc.), instant messages and reminders (express delivery information, expenditure information, commuting traffic conditions, taxi ride information, schedule information, etc.), and follow-up dynamics (football stands, basketball stands, stock information, etc.). The control center is the upward sliding message notification bar of the electronic device, that is, the user interface displayed by the electronic device when the user starts an upward sliding operation at the bottom of the electronic device. The notification center is the downward sliding message notification bar of the electronic device, that is, the user interface displayed by the electronic device when the user starts a downward operation at the top of the electronic device.

[0150] 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.

[0151] As Figure 2a shown, the application framework layer can include a third-party interface layer (EasyGoSDK), an activity manager, a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, a parallel window manager (HwMagicWindowManager), etc.

[0152] Third-party interface layer (EasyGoSDK): An interface layer for docking with third-party applications, which is adapted to each third-party application. Generally, applications can be divided into system applications and third-party applications. Among them, system applications can be understood as applications that are not independent and rely on the software system. Third-party applications are applications other than system applications, and third-party applications can include, but are not limited to: self-developed applications of device manufacturers (such as Huawei welink) and applications of non-device manufacturers (such as WeChat / Taobao), etc.

[0153] Activity manager: Interacts with all running activities in the software system, manages and maintains information related to all running activities in the software system (such as tasks, memory, services, processes, APPs, etc.); provides corresponding interfaces for obtaining information related to activities.

[0154] Among them, an Activity is a display component of an Android APP. An Activity provides a window for interaction with users and is used to display the content of the APP. An Activity is usually a separate window, which can fill the display area of the electronic device's display screen or be smaller than the display area of the electronic device and float above other windows. An APP is usually composed of multiple loosely related Activities. Usually, an APP can specify a certain Activity as the main Activity, which refers to the Activity presented to the user when the APP is first launched. Correspondingly, the window presented by the main Activity is the main page in the APP. For example, the main page of the WeChat application is the page corresponding to the chat dialog list.

[0155] The window manager is used to manage window programs, such as managing window states, properties, view addition, deletion, update, window order, message collection and processing, etc. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc. And the window manager is the entry for external access to windows.

[0156] The content provider is used to store and obtain data and make this data accessible to application programs. The data can include videos, images, audio, dialed and received calls, browsing history and bookmarks, phone books, etc.

[0157] 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 application programs. The display interface can be composed of one or more views. For example, a display interface including a text message notification icon can include a view for displaying text and a view for displaying pictures.

[0158] The phone manager is used to provide the communication function of the electronic device 100. For example, the management of call states (including connection, disconnection, etc.).

[0159] The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files (layout xml) of the user interface, video files, fonts, colors, identity document numbers (identity document, ID) of user interface components (userinterface module, UI components), etc. Moreover, the resource manager is used to uniformly manage the aforementioned resources.

[0160] The notification manager enables the application to display notification information in the status bar. It can be used to convey notification-type messages, which can automatically disappear after a short stay without user interaction. For example, the notification manager is used to inform that the download is complete, message reminders, etc. 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 a notification that appears on the screen in the form of a dialog window. For example, it can prompt text information in the status bar, emit a prompt sound, vibrate the electronic device, blink the indicator light, etc.

[0161] The Parallel Window Manager (HwMagicWindowManager) is a customization service for the software system, namely HwMagicWindowService, which runs in the system server. Its main function is to encapsulate a series of policy interfaces by combining multiple data modules inside the service, embed a stubbing process in the processes of starting, managing, and displaying Activities in the native application framework layer, execute the policies of HwMagicWindowService, and provide a basic framework for each application to implement the in-app split-screen function (MagicWindow).

[0162] Among them, the stubbing process refers to the code used to replace associated code or unimplemented code, that is, writing or generating stub code. One of the uses of the stubbing process is to set the behavior of the code related to the policies of HwMagicWindowService during testing to meet the test requirements.

[0163] Please refer to Figure 2b , Figure 2b which shows the software structure block diagram of the Parallel Window Manager (HwMagicWindowManager). As Figure 2b shown, the Parallel Window Manager (HwMagicWindowManager) can include: a policy module, a configuration module, a data management module, a background layer drawing module, and an animation effect module.

[0164] Policy module: Executes the policies of the in-app split-screen function, including Activity startup policies, process startup policies, window display policies, etc.

[0165] Configuration module: Load feature configuration parameters. Among them, the feature configuration parameters are, for example, the boundary (bounds) information of the window size, such as the window size and the split-screen size.

[0166] Data management module: Set user-selected data on the device. Among them, the user-selected data on the device can be understood as the configuration parameters corresponding to whether to enable the in-app split-screen function for each application in the settings application of the electronic device. In addition, the data management module can also be associated with other data.

[0167] Background layer drawing module: When there is a window switch on the electronic device, implement the display of the background UI. Among them, the background UI can be a wallpaper processed by Gaussian blur, or a certain page processed by Gaussian blur, or a full black display, or the main interface, etc. This application does not make any restrictions on this.

[0168] For example, when the electronic device switches from split-screen to full-screen, implement the display of the background UI. Another example is when the electronic device switches from full-screen to split-screen, implement the display of the background UI. Another example is when switching between left and right split-screens, implement the display of the background UI.

[0169] Animation effect module: A custom animation effect interface module after the in-app split-screen function is started, such as window startup animation effects, split-screen / full-screen window switching animation effects, left and right split-screen window closing animation effects, etc. interfaces.

[0170] The Android runtime includes a core library and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

[0171] The core library consists of two parts: one part is the functional functions that need to be called by the Java language, and the other part is the core library of the Android system.

[0172] The application layer and the application framework layer run in the virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0173] The system library can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing library (for example: OpenGLES), 2D graphics engine (for example: SGL), etc.

[0174] The surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.

[0175] The media library supports the playback and recording of multiple common audio and video formats, as well as static image files, etc. The media library can support multiple audio and video coding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

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

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

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

[0179] The following takes the scenario of playing sound using a smart speaker as an example to exemplarily illustrate the working processes of the software and hardware of the electronic device 100.

[0180] When the touch sensor 180K receives a touch operation, the corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into a raw input event (including information such as touch coordinates and the timestamp of the touch operation). The raw input event is stored in the kernel layer. The application framework layer obtains the raw input event from the kernel layer and identifies the control corresponding to the input event. Taking the touch operation as a touch click operation and the control corresponding to the click operation being the control of the smart speaker icon as an example, the smart speaker application calls the interface of the application framework layer to start the smart speaker application, and then starts the audio driver by calling the kernel layer, and converts the audio electrical signal into a sound signal through the speaker 170A.

[0181] It can be understood that the structure illustrated in this application does not constitute a specific limitation on the electronic device 100. In other embodiments, 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. The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

[0182] Based on the foregoing description, for any application installed in an electronic device, the electronic device supports in-application split-screen display of multiple pages of the application, implementing the in-application split-screen function of the application. The in-application split-screen display here can be understood as that two pages within the application are respectively displayed using two windows, and these two windows can be split horizontally or vertically. Horizontal split-screen means that when the two pages of the application are respectively displayed on the electronic device, the windows corresponding to the two pages are arranged side by side in the display screen of the electronic device. Usually, the electronic device can achieve horizontal split-screen display when in the landscape screen state. Vertical split-screen means that when the two pages of the application are respectively displayed on the electronic device, the windows corresponding to the two pages are arranged vertically in the display screen of the electronic device. Usually, the electronic device can achieve horizontal split-screen display when in the portrait screen state.

[0183] Assume that page A is the main page in the application, that is, the Activity corresponding to page A is the main Activity of the application.

[0184] Page a0 is a default page (i.e., a secondary page) in the application, and the Activity corresponding to page A and the Activity corresponding to page a0 run in the same task (which can be understood as the same stack / task stack). Additionally, page a0 is usually custom-set by a third-party developer. After the application is launched, page A and page a0 are simultaneously displayed on the display screen of the electronic device, and page a0 plays a role in aesthetic decoration, enabling the display page of the application to better adapt to the display screen of the electronic device and achieving a better display effect. Among them, page a0 can include the icon of the application or can also include controls that provide certain functions of the application to the user. This application does not limit the specific content of page a0.

[0185] Page a1 is a sub-page of page A and can be any page other than page A in the application. Among them, the Activity corresponding to page A can start the Activity corresponding to page a1, and the Activity corresponding to page A and the Activity corresponding to page a1 run in the same task (which can be understood as the same stack / task stack).

[0186] Control B is used to trigger the display of page B. Among them, the user can trigger control B from page A or can also trigger control B from page a1. This application does not limit this. Among them, the ways of triggering the control mentioned in this application can include various implementation methods such as clicking, long-pressing, swiping, voice search, long-pressing, text input, etc. And the controls mentioned in this application can include but are not limited to buttons, input boxes, icons, text, etc.

[0187] Page B is a page in the application other than the main page and Page a1. For example, when the application is the WeChat application, Page B can be any page of a certain official account in the WeChat application, or Page B can be the page of a certain webpage in the WeChat application, or Page B can be any page of a certain mini-program in the WeChat application. Another example is that when the application is a video application, Page B can be any page other than the main page in the video application, such as the page of a certain video. Another example is that when the application is the Toutiao application, Page B can be any page other than the main page in the Toutiao application, such as the page of a certain news item.

[0188] In this application, when Page A and Page B are displayed in split screen, the Activity corresponding to Page A and the Activity corresponding to Page B run in different tasks (which can be understood as different stacks / task stacks).

[0189] In some embodiments, the launch mode of the Activity corresponding to Page B is set to the singleInstance mode to ensure the uniqueness of the Activity corresponding to Page B in its task stack. Furthermore, the launch method of Page B is newtask launch. Thus, when triggering the display of Page B, the software system of the electronic device establishes a new task stack, and the Activity corresponding to Page B runs in this new task stack.

[0190] In some other embodiments, the launch mode of the Activity corresponding to Page B is not set to the singleInstance mode. When triggering the display of Page B, the software system of the electronic device does not establish a new task stack. Instead, after receiving the user's trigger on the split screen control in Page B and when the electronic device determines that Page A and Page B need to be displayed in split screen, a new task stack is established, and the Activity corresponding to Page B runs in this new task stack.

[0191] In some embodiments, the user can trigger Control D from Page B, and Control D is used to trigger the display of Page D. Page D is a page in the application other than Page B.

[0192] Then, based on the foregoing description, taking the scenario where the electronic device is in the landscape screen state and the two pages of the application are displayed in left - right split screen as an example in combination with Scenario 1 and Scenario 2, the specific implementation process of the in - application split screen function of the application on the electronic device is introduced.

[0193] Scenario 1

[0194] In Scenario 1, after the electronic device detects the operation of triggering Control B on Page A indicated by the user, split-screen display of Page A and Page B can be achieved, thereby realizing the in-application split-screen function of the application.

[0195] Please refer to Figures 3A - 3F , Figures 3A - 3F which is a schematic flowchart of a method for displaying application pages provided in an embodiment of the present application. Among them, Figure 3A shows the process of displaying from the current page of the application to the next page, Figure 3B shows the process of returning from the current page of the application to the previous page, and Figures 3A - 3B the displayed pages in

[0196] 0. Display of Page A

[0197] When the electronic device is in the landscape screen state, the display screen of the electronic device can display an interface as shown in Figure 3A (1a) of this document. This interface includes Page A and Page a0.

[0198] Figure 3A In (1a) of this document, Control B is included in the displayed Page A of this interface, indicating that the user can trigger Control B from Page A. Control C1 is also included in the displayed Page A of this interface, indicating that the user can trigger Control C1 from Page A. Among them, Control C1 is used to trigger the display of Page C1, and Page C1 is a page other than the main page and Page B in this application. Page C1 may or may not include Page a1, and the present application does not make any limitations in this regard.

[0199] Among them, Page A can be displayed full-screen, as shown in Figure 3A (1b) of this document, or it can be displayed in a partial display area of the display screen, such as only Page A is displayed in a partial display area of the display screen (as shown in Figure 3A (1c) of this document) or Page A and Page a0 are split-screen displayed left and right (as shown in Figure 3A (1a) of this document). The present application does not make any limitations on the display method of Page A, and it is specifically set according to the configuration parameters of the application itself and the configuration parameters of the software system. For the sake of convenience of description, in Scenario 1, an example is given with Page A displayed in the left split screen and Page a0 displayed in the right split screen as shown in Figure 3A (1a) of this document for illustration.

[0200] In some embodiments, the displayed Page A of this interface may further include a return control 01 ( Figure 3Ais not shown in the figure), and is used to indicate that the user can trigger the return control 01 from page A, and the return control 01 is used to trigger exiting page A or exiting the application. For example, the user can trigger the return control 01 from page A, and the electronic device can pop up the Activity corresponding to page A, so that the display screen of the electronic device shows the desktop of the electronic device.

[0201] 1. Split-screen display of page A and page B on the left and right (corresponding to Figure 3A the step S11 shown in

[0202] In some embodiments, after the electronic device detects the operation 101 of the user indicating to trigger the control B in page A, if the launch mode of the Activity corresponding to page B is set to the singleInstance mode, a new Task (that is, a task stack different from the task stack corresponding to page A) can be established, and the Activity corresponding to page B is launched in this new Task.

[0203] Among them, the aforementioned new Task and the Task corresponding to page A are different Tasks, which can be understood as the Activity corresponding to page B enters a task different from the Activity corresponding to page A. The control B can be referred to the previous description and will not be elaborated here.

[0204] After the Activity corresponding to page B is launched, the electronic device can default to display page B (that is, full-screen display as shown in Figure 3A (2) or display in a partial display area). And, page B includes a split-screen / full-screen control, which is used to indicate that the user can trigger the split-screen / full-screen control from page B, and the split-screen / full-screen control is used for split-screen display or full-screen display of page B.

[0205] After the electronic device detects the operation 102 of the user indicating to trigger the split-screen / full-screen control in page B, it can send message 1 to the application. Message 1 is used to identify the aforementioned operation 102, so that the application can obtain the taskID of the Activity corresponding to page B from the software system of the electronic device, determine the split-screen position of page B based on the aforementioned operation 102, and determine the method name (referred to as setTaskPosition) of method 1 for split-screen display within the application based on the aforementioned operation 102. Method 1 is used to indicate split-screen display of page A and page B. The present application does not limit the representation method of message 1. For example, message 1 can include the reporting point coordinates of the aforementioned operation 102.

[0206] Among them, the aforementioned split-screen position can be the entire display area of the display screen (i.e., full screen), or the left display area of the display screen (i.e., left split screen), or the right display area of the display screen (i.e., right split screen), and this application does not make any restrictions on this. For the convenience of description, the split-screen position can be represented by targetPosition. Generally, when any page is displayed full screen, targetPosition is set to 0; when any page is displayed in left split screen, targetPosition is set to 1; when any page is displayed in right split screen, targetPosition is set to 2. In some embodiments, the application can set targetPosition to 2, that is, set the B page to be displayed in right split screen.

[0207] Therefore, since the aforementioned operation 102 is triggered on the split-screen / full-screen control in the B page, and the electronic device can obtain that the electronic device was displayed full screen before the aforementioned operation 102, that is, targetPosition is set to 0. Therefore, when the electronic device receives the aforementioned operation 102, the electronic device can determine that the user's intention is to display the A page and the B page in split screen. Furthermore, the electronic device determines the split-screen position of the B page, that is, targetPosition is set to 1 or 2. It should be noted that usually when the A page and the B page are displayed in split screen, targetPosition is default set to 2.

[0208] In summary, the software system of the electronic device notifies the application of the aforementioned operation 102, so that the application can obtain the taskID of the Activity corresponding to the B page, the split-screen position of the B page, and the method name (referred to as setTaskPosition) of method 1 for split-screen display within the application.

[0209] It should be noted that for the execution steps of establishing a new Task in response to operation 101 by the electronic device, the software system of the electronic device sends the execution steps of the aforementioned operation 101 to the application, and there is no sequence in time, and they can be executed simultaneously or sequentially, and this application does not make any restrictions on this.

[0210] Based on the description of the foregoing embodiments, the application can call the invoke interface in the third-party interface layer (EasyGoSDK) of the electronic device, and transmit message 2. Message 2 carries the method name (setTaskPosition) of method 1, the split-screen position (targetPosition), and the taskID of the Activity corresponding to the B page.

[0211] Among them, the present application does not limit the representation method of Message 2. For example, the split screen position (targetPosition) and the task ID of the Activity corresponding to Page B can be passed using the parameter params1. It should be noted that the task ID of the Activity corresponding to Page B can be replaced by the ID of Page B. The present application does not limit this, and only the identifier used to represent Page B needs to be transmitted. Among them, the present application does not limit this identifier.

[0212] In addition, the definition of the invoke interface is shown in Table 1:

[0213] Table 1 Definition of the invoke interface

[0214]

[0215] Based on Table 1, taking the function of implementing the switching of the task split screen position as an example, the usage instructions of the invoke interface can be represented by the following code:

[0216] Parameters:

[0217] function = "magicwindow"

[0218] method = "setTaskPosition" / / Identify the method name

[0219] params.put("@int:taskID") / / Identify the effective task ID

[0220] params.put("@int:targetPosition") / / Identify targetPosition, and the value range of targetPosition is 0, 1 or 2

[0221] Return value:

[0222] easyGoRet.code = 0 / / The call is successful

[0223] Based on the above description, taking the setting of the window position as an example, the specific implementation method of the invoke interface is represented by the following code:

[0224] String function = "magicwindow";

[0225] String method = "setTaskPosition";

[0226] JSONObject params = new JSONObject();

[0227] try {

[0228] int taskID = getTaskID();

[0229] params.put("@int:taskID", taskID);

[0230] params.putInt("@int:targetPosition", position);

[0231] } catch (JSONException e) {

[0232] Log.e(TAG, e.getMessage());

[0233] }

[0234] EasyGoRet ret = mEasyGo.invokeSync(funtion, method, params, null);

[0235] Log.i("EasyGo", ret.code + "");

[0236] Log.i("EasyGo", ret.result.get("int") + "");

[0237] In summary, the third - party interface layer (EasyGoSDK) can obtain the method name (setTaskPosition) of Method 1, the split - screen position (targetPosition), and the taskID of the Activity corresponding to Page B. And the third - party interface layer (EasyGoSDK) can also obtain (such as actively querying) the package name of this application.

[0238] The third - party interface layer (EasyGoSDK) sends the method name (setTaskPosition) of Method 1, the split - screen position (targetPosition), the taskID of the Activity corresponding to Page B, and the package name of this application to the parallel window manager (HwMagicWindowManager) of the electronic device.

[0239] Among them, the package name, target position of the split screen, and the task ID of the Activity corresponding to page B of the application can be passed using the parameter params2.

[0240] Based on Figure 2b the structure shown, using the policy module, configuration module, data management module, background layer drawing module, and animation effect module, the parallel window manager (HwMagicWindowManager) can implement the following process:

[0241] The parallel window manager (HwMagicWindowManager) determines whether the method name (setTaskPosition) of method 1 and the content of params2 are empty. When the method name (setTaskPosition) of method 1 and the content of params2 are not empty, the parallel window manager (HwMagicWindowManager) can perform the following three steps:

[0242] Step 11-1: The parallel window manager (HwMagicWindowManager) can determine whether the Activity corresponding to the task ID is the top Activity of the current task stack (i.e., determine whether the focus task stack exists) based on the task ID of the Activity corresponding to page B. Furthermore, when the Activity corresponding to the task ID is the top Activity of the current task stack, the electronic device can ensure the existence of the current task stack.

[0243] Among them, step 11-1 is an optional step.

[0244] Step 11-2: The parallel window manager (HwMagicWindowManager) can determine whether the application corresponding to the package name supports in-application split screen based on the package name of the application. Furthermore, when the electronic device determines that the application corresponding to the package name supports in-application split screen, the electronic device can ensure that the application can support split screen display of multiple pages of the application.

[0245] Among them, the specific process for the electronic device to determine whether the application corresponding to the package name supports in-application split screen can be: The electronic device can determine whether the application corresponding to the package name itself supports in-application split screen, and determine whether the electronic device enables the in-application split screen function of the application.

[0246] When the electronic device can determine that the application corresponding to the package name itself supports in-application split screen and the electronic device enables the in-application split screen function of the application, the electronic device can determine that the application corresponding to the package name supports in-application split screen.

[0247] Among them, the electronic device can store in advance the package names of the applications that support the in-application split-screen function (such as setting a whitelist), or can obtain from the AndroidManifest.xml file of each application an identifier indicating whether the application supports the in-application split-screen function. This application does not make any limitations in this regard. Furthermore, the electronic device can determine whether the application corresponding to the package name itself supports the in-application split-screen function based on the foregoing description.

[0248] Among them, the data management module stores the user selection data of each application in the settings application. The user selection data of each application can be used to indicate whether the electronic device enables the in-application split-screen function of the application. Furthermore, the electronic device can obtain from the data management module the user selection data of the application corresponding to the package name in the settings application, and based on the user selection data of the application corresponding to the package name, determine whether the electronic device enables the in-application split-screen function of the application. Furthermore, the electronic device can determine whether the application corresponding to the package name itself supports the in-application split-screen function.

[0249] Step 11-3: Based on the split-screen position (targetPosition), the parallel window manager (HwMagicWindowManager) can determine whether the moving position of page B meets the preset requirements for split-screen display (for example, the secondary screen (such as the right split-screen) or full screen, such as determining whether the value of targetPosition is 1 or 2). Furthermore, when the moving position of page B meets the preset requirements for split-screen display, the electronic device can determine that the right-screen display of page B can be achieved.

[0250] Among them, the preset requirements for split-screen display are related to the way the electronic device displays page B (that is, split-screen or full-screen display).

[0251] When the electronic device displays page B in full screen, the preset requirements for split-screen display can indicate that page B can be in split-screen display. For example, the value of targetPosition can be set to 1 or 2. Thus, when the electronic device needs to implement split-screen display for the full-screen displayed page B, it can determine whether the value of targetPosition is 1 or 2. If the value of targetPosition is 1 or 2, the electronic device determines that the moving position of page B meets the preset requirements for split-screen display.

[0252] When the electronic device is in split-screen display on page B, the preset requirements for split-screen display can indicate that page B cannot be split-screen displayed and can be full-screen displayed. For example, the value of targetPosition can be set to 0. Thus, when the electronic device needs to full-screen display page B in split-screen display, it can check whether the value of targetPosition is 0. If the value of targetPosition is 0, the electronic device determines that the moving position of page B meets the preset requirements for split-screen display.

[0253] Among them, the execution order of steps 11-1, 11-2, and 11-3 is not in sequence. They can be executed sequentially or simultaneously. This application does not make any limitations in this regard.

[0254] When the judgment results of steps 11-1, 11-2, and 11-3 are all yes, the parallel window manager (HwMagicWindowManager) can determine the taskID of the Activity corresponding to page A based on the package name of the application.

[0255] The parallel window manager (HwMagicWindowManager) can determine split-screen parameters such as split-screen boundaries (bounds) and moving animation effects of page B based on the split-screen position (targetPosition) and the taskID of the Activity corresponding to page B, or split-screen parameters such as split-screen boundaries (bounds) and moving animation effects of page A and page B.

[0256] The parallel window manager (HwMagicWindowManager) simultaneously displays two independent tasks on the left and right split-screens of the display screen based on the taskID of the Activity corresponding to page A, the taskID of the Activity corresponding to page B, and the split-screen parameters of page B, that is, as Figure 3A shown in (3) of the figure, page A is displayed on the left split-screen of the electronic device and page B is displayed on the right split-screen of the electronic device.

[0257] Based on the foregoing description, combined with Figure 3C , the implementation process of the electronic device to achieve split-screen display of page A and page B is specifically described.

[0258] As Figure 3C shown, the specific implementation process of the application page display method of this application can include the following steps:

[0259] S31. The electronic device displays page A.

[0260] When the electronic device receives the user's operation 101 on page A, a new Task (i.e., a task stack different from the task stack corresponding to page A) is established, and the Activity corresponding to page B is started in the new Task, and page B is displayed.

[0261] When the electronic device receives the user's operation 102 on page B, a message 1 is sent to the application, and message 1 is used to identify operation 102.

[0262] In response to message 1, the application obtains the method name (referred to as setTaskPosition) of method 1, the split-screen position (targetPosition) of page B, and the taskID of the Activity corresponding to page B.

[0263] The application sends message 2 to the third-party interface layer (EasyGoSDK), and message 2 carries the method name (referred to as setTaskPosition) of method 1, the split-screen position (targetPosition) of page B, and the taskID of the Activity corresponding to page B.

[0264] The third-party interface layer (EasyGoSDK) sends the method name (referred to as setTaskPosition) of method 1, the split-screen position (targetPosition) of page B, the taskID of the Activity corresponding to page B, and the package name of the application to the parallel window manager (HwMagicWindowManager).

[0265] S361: The parallel window manager (HwMagicWindowManager) determines whether the Activity corresponding to the taskID of the Activity corresponding to page B is the top Activity of the current task stack.

[0266] Step S361 is an optional step.

[0267] S362: The parallel window manager (HwMagicWindowManager) determines whether the application corresponding to the package name (packagename) of the application supports the in-app split-screen function.

[0268] S363: The parallel window manager (HwMagicWindowManager) determines whether the moving position of page B meets the preset requirements for split-screen display based on the split-screen position (targetPosition) of page B.

[0269] When the judgment results of S361, S362, and S363 by the parallel window manager (HwMagicWindowManager) are all yes, based on the package name of the application, determine the task ID of the Activity corresponding to page A, and based on the split-screen position (targetPosition) and the task ID of the Activity corresponding to page B, determine the split-screen parameters of page B.

[0270] In addition, when the judgment result of any one of the steps S361, S362, and S363 by the parallel window manager (HwMagicWindowManager) is no, continue to display page B.

[0271] S38. The parallel window manager (HwMagicWindowManager) simultaneously displays page A and page B based on the task ID of the Activity corresponding to page A, the task ID of the Activity corresponding to page B, and the split-screen parameters of page B.

[0272] It should be noted that Figure 3C For the specific implementation process shown by way of example, reference may be made to the foregoing content, and details are not described herein again.

[0273] In some other embodiments, after the electronic device detects the operation 101 of the control B in page A indicated by the user, if the launch mode of the Activity corresponding to page B is set to the singleInstance mode, a new Task (i.e., a task stack different from the task stack corresponding to page A) can be established, and the Activity corresponding to page B is started in a new Task.

[0274] Among them, the foregoing new Task and the Task corresponding to page A are different Tasks, which can be understood as the Activity corresponding to page B enters a task different from the Activity corresponding to page A. The control B can be referred to the foregoing description, and details are not described herein again.

[0275] Moreover, the electronic device can send Message 3 to the application. Message 3 is used to identify the aforementioned Operation 101. In response to the aforementioned Operation 101, the application can obtain the ID of the task (referred to as taskID) of the Activity corresponding to Page B from the software system of the electronic device, determine the split-screen position of Page B based on the aforementioned Operation 101, and determine the method name (referred to as setTaskPosition) of Method 1 for split-screen display within the application based on the aforementioned Operation 101. Method 1 is used to indicate the split-screen display of Page A and Page B. Herein, the present application does not limit the representation manner of Message 3. For example, Message 3 can be the reporting point coordinates of the aforementioned Operation 101.

[0276] Among them, the split-screen position mentioned above can refer to the description of the split-screen position mentioned above, which will not be elaborated herein.

[0277] In summary, the software system of the electronic device notifies the application of the aforementioned Operation 101, so that the application can obtain the taskID of the Activity corresponding to Page B, the split-screen position of Page B, and the method name (referred to as setTaskPosition) of Method 1 for split-screen display within the application.

[0278] It should be noted that for the execution steps of establishing a new Task in response to Operation 101 by the electronic device, the software system of the electronic device sends the execution steps of the aforementioned Operation 101, and there is no sequence in time, and they can be executed simultaneously or sequentially. The present application does not limit this.

[0279] Based on the description of the foregoing embodiment, the application can call the invoke interface in the third-party interface layer (EasyGoSDK) of the electronic device, and transmit Message 4. Message 4 carries the method name (setTaskPosition) of Method 1, the split-screen position (targetPosition), and the taskID of the Activity corresponding to Page B.

[0280] Herein, the present application does not limit the representation manner of Message 4. For example, the split-screen position (targetPosition) and the taskID of the Activity corresponding to Page B can be transmitted using parameter params1. It should be noted that the taskID of the Activity corresponding to Page B can be replaced by the ID of Page B. The present application does not limit this, and only the identifier used to represent Page B needs to be transmitted. Herein, the present application does not limit this identifier.

[0281] In summary, the third-party interface layer (EasyGoSDK) can obtain the method name of Method 1 (setTaskPosition), the split-screen position (targetPosition), and the task ID of the Activity corresponding to Page B. Moreover, the third-party interface layer (EasyGoSDK) can also obtain (such as actively querying) the package name of the application (package name).

[0282] The third-party interface layer (EasyGoSDK) sends the method name of Method 1 (setTaskPosition), the split-screen position (targetPosition), the task ID of the Activity corresponding to Page B, and the package name of the application (package name) to the parallel window manager (HwMagicWindowManager) of the electronic device.

[0283] Among them, the package name of the application (package name), the split-screen position (targetPosition), and the task ID of the Activity corresponding to Page B can be passed using the parameter params2.

[0284] Based on Figure 2b the structure shown, using the policy module, configuration module, data management module, background layer drawing module, and animation effect module, the parallel window manager (HwMagicWindowManager) can implement the following process: The parallel window manager (HwMagicWindowManager) determines whether the method name of Method 1 (setTaskPosition) and the content of params2 are empty. When the method name of Method 1 (setTaskPosition) and the content of params2 are not empty, the parallel window manager (HwMagicWindowManager) can perform the following three steps:

[0285] Step 12-1. Based on the package name of the application, the Parallel Window Manager (HwMagicWindowManager) can determine whether the task stack of the Activity corresponding to Page A is in a non-split-screen mode (i.e., whether Page A corresponding to the Activity is not in a split-screen display state). Among them, the Parallel Window Manager (HwMagicWindowManager) can determine whether the number of task stacks corresponding to the pages currently displayed on the electronic device is one, so as to judge whether the task stack of the Activity corresponding to Page A is in a non-split-screen mode. Thus, when it is determined that the number of task stacks corresponding to the pages currently displayed on the electronic device is one, the Parallel Window Manager (HwMagicWindowManager) can determine that the task stack of the Activity corresponding to Page A is in a non-split-screen mode.

[0286] Alternatively, the Parallel Window Manager (HwMagicWindowManager) can obtain an indication flag from the electronic device, where the indication flag indicates whether the task stack of the Activity corresponding to Page A is in a non-split-screen mode. Thus, when the indication flag indicates that the task stack corresponding to the Activity is in a non-split-screen mode, the Parallel Window Manager (HwMagicWindowManager) can determine that the task stack of the Activity corresponding to Page A is in a non-split-screen mode.

[0287] It should be noted that this application is not limited to the foregoing two implementation manners to determine whether the task stack of the Activity corresponding to Page A is in a non-split-screen mode.

[0288] Step 12-2. Based on the package name of the application, the Parallel Window Manager (HwMagicWindowManager) can determine whether the application corresponding to the package name supports the in-application split-screen function. Furthermore, when the electronic device determines that the application corresponding to the package name supports the in-application split-screen function, it can ensure that the application can support the split-screen display of multiple pages of the application.

[0289] For the specific implementation manner of Step 12-2, reference can be made to the description of Step 11-2, which will not be elaborated here.

[0290] Step 12-3. Based on the split-screen position (targetPosition), the Parallel Window Manager (HwMagicWindowManager) can determine whether the moving position of Page B meets the preset requirements for split-screen display (for example, the secondary screen (such as the right split-screen) or the full screen, such as judging whether the value of targetPosition is 2). Furthermore, when the moving position of Page B meets the preset requirements for split-screen display, the electronic device can determine that the right-screen display of Page B can be achieved.

[0291] Among them, the specific implementation method of step 12-3 can refer to the description of step 11-3, and will not be elaborated here.

[0292] In addition, the execution order of step 12-1, step 12-2, and step 12-3 is not in sequence. They can be executed sequentially or simultaneously, and this application does not make any limitations on this.

[0293] When the judgment results of step 12-1, step 12-2, and step 12-3 are all yes, the parallel window manager (HwMagicWindowManager) can determine the taskID of the Activity corresponding to page A based on the package name of the application.

[0294] Based on the split-screen position (targetPosition) and the taskID of the Activity corresponding to page B, the parallel window manager (HwMagicWindowManager) can determine split-screen parameters such as the split-screen boundary (bounds) and moving animation effects of page B, or split-screen parameters such as the split-screen boundary (bounds) and moving animation effects of page A and page B.

[0295] Based on the taskID of the Activity corresponding to page A, the taskID of the Activity corresponding to page B, and the split-screen parameters of page B, the parallel window manager (HwMagicWindowManager) simultaneously displays two independent tasks on the left and right split-screens of the display screen, that is, as Figure 3A shown in (3) of, page A is displayed on the left split-screen of the electronic device and page B is displayed on the right split-screen of the electronic device.

[0296] Based on the foregoing description, combined with Figure 3D , the implementation process of split-screen display of page A and page B on the electronic device is specifically elaborated.

[0297] As Figure 3D shown, the specific implementation process of the application page display method of this application may include the following steps:

[0298] S31. The electronic device displays page A.

[0299] S32'. When the electronic device receives the user operation 101 on page A, a new Task (that is, a task stack different from the task stack corresponding to page A) is established, and the Activity corresponding to page B is started in the new Task, and a message 3 is sent to the application. Message 3 is used to identify operation 101.

[0300] S33'. The application obtains the method name of method 1 (referred to as setTaskPosition), the split-screen position of page B (targetPosition), and the task ID of the Activity corresponding to page B in response to message 3.

[0301] S34. The application sends message 4 to the third-party interface layer (EasyGoSDK). Message 4 carries the method name of method 1 (referred to as setTaskPosition), the split-screen position of page B (targetPosition), and the task ID of the Activity corresponding to page B.

[0302] S35. The third-party interface layer (EasyGoSDK) sends the method name of method 1 (referred to as setTaskPosition), the split-screen position of page B (targetPosition), the task ID of the Activity corresponding to page B, and the package name of the application to the parallel window manager (HwMagicWindowManager).

[0303] S361'. Based on the package name of the application (packagename), the parallel window manager (HwMagicWindowManager) can determine whether the task stack of the task ID of the Activity corresponding to page A is in a non-split-screen mode (i.e., whether the A page corresponding to the Activity is not in a split-screen display state).

[0304] S362. The parallel window manager (HwMagicWindowManager) determines whether the application corresponding to the package name of the application (packagename) supports the in-application split-screen function.

[0305] S363. Based on the split-screen position of page B (targetPosition), the parallel window manager (HwMagicWindowManager) determines whether the moving position of page B meets the preset requirements for split-screen display.

[0306] S37. When the judgment results of S361', S362, and S363 are all yes, the parallel window manager (HwMagicWindowManager) determines the task ID of the Activity corresponding to page A based on the package name of the application (package name), and determines the split-screen parameters of page B based on the split-screen position (targetPosition) and the task ID of the Activity corresponding to page B.

[0307] In addition, when the judgment result in any one of steps S361, S362, and S363 by the parallel window manager (HwMagicWindowManager) is negative, the A page continues to be displayed.

[0308] S38. The parallel window manager (HwMagicWindowManager) simultaneously displays the A page and the B page based on the task ID of the Activity corresponding to the A page, the task ID of the Activity corresponding to the B page, and the split-screen parameters of the B page.

[0309] It should be noted that Figure 3D For the specific implementation process shown by way of example, reference may be made to the foregoing content and will not be elaborated here. And Figure 3C different from Figure 3D steps S321, S322 - S33 of Figure 3C and steps S32'-S33' of Figure 3D and step S361 of Figure 3C and step S361' of Figure 3D the remaining steps are all the same.

[0310] In addition, Figure 3C and Figure 3D operation 101 in Figure 3C is used to identify different meanings and can be operations of the same type or different types. Figure 3D Operation 101 in

[0311] is used to identify the jump from displaying the A page in one task stack to displaying the B page in another task stack.

[0312] After the Activity corresponding to the B page is launched, the electronic device can default to displaying the B page (i.e., full-screen display as shown in (2) of Figure 3A or display in a partial display area). And the B page includes a split-screen / full-screen control for indicating that the user can trigger the split-screen / full-screen control from the B page, and the split-screen / full-screen control is used for split-screen display or full-screen display of the B page.

[0313] After detecting the operation 102 of the user instructing to trigger the split-screen / full-screen control in the B page, the electronic device can send a message 5 to the application. The message 5 is used to identify the aforementioned operation 102, so that the application can obtain the task ID of the Activity corresponding to the A page from the software system of the electronic device, determine the split-screen position of the B page based on the aforementioned operation 102, and determine the method name (referred to as setTaskPosition) of the method (method) 1 for split-screen display within the application. The method 1 is used to represent the split-screen display of the A page and the B page. Among them, the present application does not limit the representation method of the message 5. For example, the message 5 may include the reporting point coordinates of the aforementioned operation 102.

[0314] Among them, the split-screen position mentioned above can refer to the description of the split-screen position mentioned above, and will not be elaborated here.

[0315] In summary, the software system of the electronic device sends the aforementioned operation 102 to the application, so that the application can obtain the task ID of the Activity corresponding to the A page, the split-screen position of the B page, and the method name (referred to as setTaskPosition) of the method (method) 1 for split-screen display within the application. Based on the description of the foregoing embodiments, the application can call the invoke interface in the third-party interface layer (EasyGoSDK) of the electronic device and transmit a message 6. The message 6 carries the method name (setTaskPosition) of the method 1, the split-screen position (targetPosition), and the task ID of the Activity corresponding to the A page.

[0316] Among them, the present application does not limit the representation method of the message 6. For example, the split-screen position (targetPosition) and the task ID of the Activity corresponding to the A page can be transmitted using the parameter params1. It should be noted that the task ID of the Activity corresponding to the A page can be replaced by the ID of the A page. The present application does not limit this, and only the identifier used to represent the A page needs to be transmitted. Among them, the present application does not limit this identifier.

[0317] In summary, the third-party interface layer (EasyGoSDK) can obtain the method name (setTaskPosition) of the method 1, the split-screen position (targetPosition), and the task ID of the Activity corresponding to the A page. And the third-party interface layer (EasyGoSDK) can also obtain (such as actively querying) the package name of the application.

[0318] The third-party interface layer (EasyGoSDK) sends the method name of Method 1 (setTaskPosition), the split-screen position (targetPosition), the task ID of the Activity corresponding to Page A, and the package name of the application to the parallel window manager (HwMagicWindowManager) of the electronic device.

[0319] Among them, the package name of the application (package name), the split-screen position (targetPosition), and the task ID of the Activity corresponding to Page A can be passed using the parameter params2.

[0320] Based on Figure 2b the structure shown, using the policy module, configuration module, data management module, background layer drawing module, and animation effect module, the parallel window manager (HwMagicWindowManager) can implement the following process:

[0321] The parallel window manager (HwMagicWindowManager) determines whether the method name of Method 1 (setTaskPosition) and the content of params2 are empty. When the method name of Method 1 (setTaskPosition) and the content of params2 are not empty, the parallel window manager (HwMagicWindowManager) can perform the following three steps:

[0322] Step 13-1: The parallel window manager (HwMagicWindowManager) can determine whether the task stack corresponding to the task ID is the current task stack based on the task ID of the Activity corresponding to Page A. Furthermore, when the task stack corresponding to the task ID is the current task stack on the electronic device, it can ensure that there is a current task stack.

[0323] Among them, Step 13-1 is an optional step.

[0324] Step 13-2: The parallel window manager (HwMagicWindowManager) can determine whether the application corresponding to the package name supports in-application split-screen functionality based on the package name of the application (packagename). Furthermore, when the electronic device determines that the application corresponding to the package name supports in-application split-screen functionality, it can ensure that the application can support split-screen display of multiple pages of the application.

[0325] Among them, the specific implementation method of Step 13-2 can refer to the description of Step 11-2 and will not be elaborated here.

[0326] Step 13-3: Based on the split screen position (targetPosition), the Parallel Window Manager (HwMagicWindowManager) can determine whether the moving position of page B meets the preset requirements for split screen display (for example, the secondary screen (such as the right split screen) or full screen, such as determining whether the value of targetPosition is 2). Furthermore, when the moving position of page B meets the preset requirements for split screen display, the electronic device can determine that the right screen display of page B can be achieved.

[0327] Among them, for the specific implementation method of step 13-3, reference can be made to the description of step 11-3, which will not be elaborated here.

[0328] In addition, the execution order of step 13-1, step 13-2, and step 13-3 is not sequential. They can be executed sequentially or simultaneously. This application does not make any limitations in this regard.

[0329] When the judgment results of step 13-1, step 13-2, and step 13-3 are all yes, the Parallel Window Manager (HwMagicWindowManager) can create a new Task (that is, a task stack different from the task stack corresponding to page A), and start the Activity corresponding to page B in this new Task.

[0330] Among them, the aforementioned new Task and the Task corresponding to page A are different Tasks, which can be understood as the Activity corresponding to page B enters a task different from the Activity corresponding to page A.

[0331] Based on the split screen position (targetPosition) and the taskID of the Activity corresponding to page B (that is, the ID of the new Task), the Parallel Window Manager (HwMagicWindowManager) can determine split screen parameters such as the split screen boundary (bounds) and moving animation effects of page B, or split screen parameters such as the split screen boundary (bounds) and moving animation effects of page A and page B.

[0332] Based on the taskID of the Activity corresponding to page A, the taskID of the Activity corresponding to page B, and the split screen parameters of page B, the Parallel Window Manager (HwMagicWindowManager) simultaneously displays two independent tasks on the left and right split screens of the display screen, that is, as shown in (3) of Figure 3A Page A is displayed on the left split screen of the electronic device and page B is displayed on the right split screen of the electronic device.

[0333] Based on the foregoing description, combined with Figure 3E, the implementation process of split - screen display of page A and page B on the electronic device is described in detail.

[0334] As Figure 3E shown, the specific implementation process of the application page display method of this application may include the following steps:

[0335] S51. The electronic device displays page A.

[0336] S521. When the electronic device receives the user operation 101 on page A, it displays page B. Among them, the task stack corresponding to page B and the task stack corresponding to page A are the same task stack, and the Activity corresponding to page B is started in this task stack to realize the display of page B.

[0337] S522. When the electronic device receives the user operation 102 on page B, it sends message 5 to the application, and message 5 is used to identify operation 102.

[0338] S53. The application responds to message 5, obtains the method name (referred to as setTaskPosition) of method 1, the split - screen position (targetPosition) of page B, and the taskID of the Activity corresponding to page A.

[0339] S54. The application sends message 6 to the third - party interface layer (EasyGoSDK), and message 6 carries the method name (referred to as setTaskPosition) of method 1, the split - screen position (targetPosition) of page B, and the taskID of the Activity corresponding to page A.

[0340] S55. The third - party interface layer (EasyGoSDK) sends the method name (referred to as setTaskPosition) of method 1, the split - screen position (targetPosition) of page B, the taskID of the Activity corresponding to page A, and the package name of the application to the parallel window manager (HwMagicWindowManager).

[0341] S561. The parallel window manager (HwMagicWindowManager) determines whether the task stack corresponding to the taskID of the Activity corresponding to page A is the current task stack.

[0342] Step S561 is an optional step.

[0343] The parallel window manager (HwMagicWindowManager) determines whether the application corresponding to the package name of the application supports the in-application split-screen function.

[0344] S563. The parallel window manager (HwMagicWindowManager) determines whether the moving position of page B meets the preset requirements for split-screen display based on the split-screen position (targetPosition) of page B.

[0345] S57. When the judgment results of S561, S562, and S563 are all yes, the parallel window manager (HwMagicWindowManager) creates a new Task (i.e., a task stack different from the task stack corresponding to page A), and starts the Activity corresponding to page B in the new Task, and determines the split-screen parameters of page B based on the split-screen position (targetPosition) and the task ID of the Activity corresponding to page B.

[0346] In addition, when the judgment result of any one of the steps S561, S562, and S563 by the parallel window manager (HwMagicWindowManager) is no, page B continues to be displayed.

[0347] S58. The parallel window manager (HwMagicWindowManager) simultaneously displays page A and page B based on the task ID of the Activity corresponding to page A, the task ID of the Activity corresponding to page B, and the split-screen parameters of page B.

[0348] It should be noted that Figure 3E For the specific implementation process shown by way of example, reference can be made to the foregoing content, and details are not elaborated here. And Figure 3E Compared with Figure 3C The difference is that: Figure 3E The timing of creating a new task stack in step S57 of Figure 3C is different from the timing of creating a new task stack in S321 of Figure 3E and the task ID of the Activity corresponding to page A transmitted in Figure 3C is different from the task ID of the Activity corresponding to page B in

[0349] In addition, Figure 3C and Figure 3E The operation 101 in Figure 3CThe operation 101 therein is used to identify the jump from displaying page A in one task stack to displaying page B in another task stack. Figure 3E The operation 101 therein is used to identify the jump from displaying page A in one task stack to displaying page B in the same task stack.

[0350] In some other embodiments, after the electronic device detects the operation 101 of the user indicating to trigger the control B in page A, if the launch mode of the Activity corresponding to page B is not set to the singleInstance mode, the electronic device may send message 7 to the application. Message 7 is used to identify the foregoing operation 101. Then, in response to the foregoing operation 101, the application may obtain the ID of the task (simply referred to as taskID) of the Activity corresponding to page A from the software system of the electronic device, determine the split-screen position of page B based on the foregoing operation 101, and determine the method name (referred to as setTaskPosition) of method 1 for split-screen display within the application based on the foregoing operation 101. Method 1 is used to represent the split-screen display of page A and page B. Herein, the present application does not limit the representation manner of message 7. For example, message 7 may be the reporting point coordinates of the foregoing operation 101.

[0351] Among them, the split-screen position mentioned above can refer to the description of the split-screen position mentioned above, which will not be elaborated here. In summary, the software system of the electronic device sends the foregoing operation 101 to the application, so that the application can obtain the taskID of the Activity corresponding to page A, the split-screen position of page B, and the method name (referred to as setTaskPosition) of method 1 for split-screen display within the application.

[0352] Based on the description of the foregoing embodiments, the application may call the invoke interface in the third-party interface layer (EasyGoSDK) of the electronic device, and transmit message 8. Message 8 carries the method name (setTaskPosition) of method 1, the split-screen position (targetPosition), and the taskID of the Activity corresponding to page A.

[0353] Herein, the present application does not limit the representation manner of message 8. For example, the split-screen position (targetPosition) and the taskID of the Activity corresponding to page A may be transmitted using parameter params1. It should be noted that the taskID of the Activity corresponding to page A may be replaced by the ID of page A. The present application does not limit this, as long as the identifier used to represent page A is transmitted. Herein, the present application does not limit this identifier.

[0354] In summary, the third-party interface layer (EasyGoSDK) can obtain the method name of Method 1 (setTaskPosition), the split-screen position (targetPosition), and the task ID of the Activity corresponding to Page A. Moreover, the third-party interface layer (EasyGoSDK) can also obtain (such as actively querying) the package name of the application (package name).

[0355] The third-party interface layer (EasyGoSDK) sends the method name of Method 1 (setTaskPosition), the split-screen position (targetPosition), the task ID of the Activity corresponding to Page A, and the package name of the application (package name) to the parallel window manager (HwMagicWindowManager) of the electronic device.

[0356] Among them, the package name of the application (package name), the split-screen position (targetPosition), and the task ID of the Activity corresponding to Page A can be passed using the parameter params2.

[0357] Based on Figure 2b the shown structure, using the policy module, configuration module, data management module, background layer drawing module, and animation effect module, the parallel window manager (HwMagicWindowManager) can implement the following process:

[0358] The parallel window manager (HwMagicWindowManager) determines whether the method name of Method 1 (setTaskPosition) and the content of params2 received are empty. When the method name of Method 1 (setTaskPosition) and the content of params2 are not empty, the parallel window manager (HwMagicWindowManager) can perform the following three steps:

[0359] Step 14-1: The parallel window manager (HwMagicWindowManager) can determine whether the task stack corresponding to the task ID is in a non-split-screen mode (that is, whether Page A corresponding to the Activity is not in a split-screen display state) based on the task ID of the Activity corresponding to Page A.

[0360] Among them, the specific implementation method of Step 14-1 can refer to the description of Step 12-1 and will not be elaborated here.

[0361] Step 14-2: The parallel window manager (HwMagicWindowManager) can determine whether the application corresponding to the package name supports the in-application split-screen function based on the package name of the application. Furthermore, when the electronic device determines that the application corresponding to the package name supports the in-application split-screen function, it can ensure that the application can support the split-screen display of multiple pages of the application.

[0362] Among them, for the specific implementation method of step 14-2, please refer to the description of step 13-2, which will not be elaborated here.

[0363] Step 14-3: The parallel window manager (HwMagicWindowManager) can determine whether the moving position of page B meets the preset requirements for split-screen display (for example, the secondary screen (such as the right split-screen) or the full screen, such as determining whether the value of targetPosition is 2) based on the split-screen position (targetPosition). Furthermore, when the moving position of page B meets the preset requirements for split-screen display, the electronic device can determine that the right-screen display of page B can be achieved.

[0364] Among them, for the specific implementation method of step 14-3, please refer to the description of step 13-3, which will not be elaborated here.

[0365] In addition, the execution order of step 14-1, step 14-2, and step 14-3 is not in sequence. They can be executed sequentially or simultaneously, and this application does not make any restrictions on this.

[0366] When the judgment results of step 14-1, step 14-2, and step 14-3 are all yes, the parallel window manager (HwMagicWindowManager) can create a new Task (that is, a task stack different from the task stack corresponding to page A), and start the Activity corresponding to page B in this new Task.

[0367] Among them, the aforementioned new Task and the Task corresponding to page A are different Tasks, which can be understood as the Activity corresponding to page B enters a task different from the Activity corresponding to page A.

[0368] The parallel window manager (HwMagicWindowManager) can determine split-screen parameters such as the split-screen boundary (bounds) and moving animation effects of page B, or split-screen parameters such as the split-screen boundary (bounds) and moving animation effects of page A and page B based on the split-screen position (targetPosition) and the task ID of the Activity corresponding to page B (that is, the ID of the new Task).

[0369] The parallel window manager (HwMagicWindowManager) displays two independent tasks on the left and right split screens of the display screen based on the task ID of the Activity corresponding to page A, the task ID of the Activity corresponding to page B, and the split screen parameters of page B. That is, as shown in (3) of Figure 3A page A is displayed on the left split screen of the electronic device and page B is displayed on the right split screen of the electronic device as shown.

[0370] Based on the foregoing description, combined with Figure 3F , the implementation process of split screen display of page A and page B on the electronic device is specifically described.

[0371] As Figure 3F shown, the specific implementation process of the application page display method of this application may include the following steps:

[0372] S51. The electronic device displays page A.

[0373] S52'. When the electronic device receives the user operation 101 on page A, it sends message 7 to the application, and message 7 is used to identify operation 101.

[0374] S53'. The application responds to message 7 and obtains the method name (referred to as setTaskPosition) of method 1, the split screen position (targetPosition) of page B, and the task ID of the Activity corresponding to page A.

[0375] S54. The application sends message 8 to the third-party interface layer (EasyGoSDK), and message 8 carries the method name (referred to as setTaskPosition) of method 1, the split screen position (targetPosition) of page B, and the task ID of the Activity corresponding to page A.

[0376] S55. The third-party interface layer (EasyGoSDK) sends the method name (referred to as setTaskPosition) of method 1, the split screen position (targetPosition) of page B, the task ID of the Activity corresponding to page A, and the package name of the application to the parallel window manager (HwMagicWindowManager).

[0377] S561', the parallel window manager (HwMagicWindowManager) determines whether the task stack corresponding to the task ID of the Activity corresponding to page A is in a non-split-screen mode (that is, whether the page A corresponding to the Activity is not in a split-screen display state).

[0378] S562, the parallel window manager (HwMagicWindowManager) determines whether the application corresponding to the package name of the application supports the in-application split-screen function.

[0379] S563, the parallel window manager (HwMagicWindowManager) determines whether the moving position of page B meets the preset requirements for split-screen display based on the split-screen position (targetPosition) of page B.

[0380] S57, when the judgment results of S561, S562, and S563 are all yes, the parallel window manager (HwMagicWindowManager) creates a new Task (that is, a task stack different from the task stack corresponding to page A), and starts the Activity corresponding to page B in the new Task, and determines the split-screen parameters of page B based on the split-screen position (targetPosition) and the task ID of the Activity corresponding to page B.

[0381] In addition, when the judgment result of any one of S561, S562, and S563 by the parallel window manager (HwMagicWindowManager) is no, page A continues to be displayed.

[0382] S58, the parallel window manager (HwMagicWindowManager) simultaneously displays page A and page B based on the task ID of the Activity corresponding to page A, the task ID of the Activity corresponding to page B, and the split-screen parameters of page B.

[0383] It should be noted that Figure 3F For the specific implementation process shown by way of example, reference can be made to the foregoing content, and details are not described herein. And Figure 3E and Figure 3F different from: Figure 3E Steps S521, S522 - S53 of Figure 3F and steps S52' - S53' of Figure 3E and step S561 of Figure 3F and step S561' of

[0384] In addition, Figure 3E andFigure 3C The differences are as follows: Figure 3E In step S57 of Figure 3C the timing of establishing a new task stack is different from that in S321 of Figure 3E and the taskID of the Activity corresponding to page A transmitted is different from that of the Activity corresponding to page B of Figure 3C The remaining steps are similar.

[0385] Moreover, Figure 3C and Figure 3E operation 101 in Figure 3C is used to identify different meanings and can be operations of the same type or different types. Figure 3E Operation 101 in

[0386] is used to identify the jump from page A in one task stack to page B displayed in another task stack. Figure 3B Operation 101 in

[0387] is used to identify the jump from page A in one task stack to page B in the same task stack. In summary, the launch mode of the Activity corresponding to page B affects the timing of the software system of the electronic device to establish a new task stack. In addition, the software system of the electronic device sends a message corresponding to the trigger operation of the split-screen control or a certain trigger operation of the user to the application, which affects whether the application can call the third-party interface layer (EasyGoSDK) in the software system of the electronic device. Figure 3B As shown in (2) and (3) of

[0388] Page B may further include a return control 1, which is used to indicate that the user can trigger the return control 1 from page B, and the return control 1 is used to exit the display of page B. Figure 3B After the electronic device detects the operation 201 of the user indicating to trigger the return control 1 in page B, it can exit the Activity corresponding to page B, so that the electronic device can return from the user interface shown in (2) or (3) of Figure 3B to the user interface shown in (1) of

[0389] 3. Open a new page from page A displayed in the left split screen, and the new page replaces page A displayed in the left split screen (corresponding to step S131 or step S132 as shown in Figure 3A ).

[0390] 31. Open page C1 from page A displayed in the left split screen, and page C1 replaces page A displayed in the left split screen (corresponding to step S131 or step S132 as shown in Figure 3AThe step S131 shown

[0391] When the electronic device detects an operation 301 of triggering the control C1 in the A page indicated by the user, it can send the parameters policy1 and params3 to the parallel window manager (HwMagicWindowManager).

[0392] Among them, due to the operation 301 performed by the user on the A page, and the A page is displayed in the left split screen, therefore, the parameter policy1 is used to represent the policy adopted when opening the C1 page from the A page displayed in the left split screen, and the parameter policy1 can be represented in forms such as numbers, strings, letters, etc.

[0393] Among them, params3 may include but are not limited to: the token of the Activity corresponding to the A page (i.e., the focus Activity), the token of the Activity corresponding to the C1 page, and the configuration parameters of the intent used to start the Activity corresponding to the C1 page.

[0394] Those skilled in the art can understand that the token can identify the corresponding Activity and ensure a one-to-one correspondence of the corresponding Activity at different levels. Therefore, the token of the Activity corresponding to the A page can identify the Activity corresponding to the A page, and the token of the Activity corresponding to the C1 page can identify the Activity corresponding to the C1 page.

[0395] Those skilled in the art can understand that an intent provides an abstract description for direct interaction between Activities and can be run by startActivity. The intent provides a medium for mutual invocation of components, achieving decoupling between the invoker and the invoked. The configuration parameters of an intent, i.e., the settings of the attributes in the intent, can include but are not limited to: action (the action to be typically performed), data (the data to be operated on when performing the action, represented by a URL pointing to the data in Android. For different actions, the types of URL data are different), category (additional information for the action to be performed), type (explicitly specify the data type (MIME) of the intent), component (specify the class name of the target component of the intent), extras (a combination of all other additional information, using extras can provide extended information for the component). Usually, the intent resolution mechanism mainly determines the matching intent by searching for all intentFilters registered in the AndroidManifest.xml file and the intents defined therein. In this resolution process, the software system makes judgments based on these three attributes: action, type, and category. Therefore, the configuration parameters of the intent used to start the Activity corresponding to Page C1 can start the Activity corresponding to Page C1.

[0396] Based on the token of the Activity corresponding to Page A, the Parallel Window Manager (HwMagicWindowManager) can determine whether the task stack corresponding to this Activity is in split-screen mode (i.e., whether the Page A corresponding to this Activity is in a split-screen display state).

[0397] Among them, the Parallel Window Manager (HwMagicWindowManager) can determine the task stacks corresponding to the pages currently displayed on the electronic device (i.e., the task stack corresponding to Page A and the task stack corresponding to Page B), and determine whether the task stack corresponding to this Activity is in split-screen mode by whether the task stack corresponding to Page A and the task stack corresponding to Page B are different task stacks. Thus, when it is determined that the task stack corresponding to Page A and the task stack corresponding to Page B are different task stacks, the Parallel Window Manager (HwMagicWindowManager) can determine that the task stack corresponding to this Activity is in split-screen mode.

[0398] Alternatively, the parallel window manager (HwMagicWindowManager) can obtain an indication identifier from the electronic device, where the indication identifier indicates whether the task stack corresponding to the Activity is in split-screen mode. Thus, when the indication identifier indicates that the task stack corresponding to the Activity is in split-screen mode, the parallel window manager (HwMagicWindowManager) can determine that the task stack corresponding to the Activity is in split-screen mode.

[0399] It should be noted that this application is not limited to the foregoing two implementation manners to determine whether the task stack corresponding to the Activity is in split-screen mode.

[0400] When the parallel window manager (HwMagicWindowManager) determines that the task stack corresponding to the Activity is in split-screen mode, based on the token of the Activity corresponding to the C1 page, it starts the configuration parameters of the intent used to start the Activity corresponding to the C1 page, so that the Activity corresponding to the C1 page is started. Furthermore, the parallel window manager (HwMagicWindowManager) can determine split-screen parameters such as the split-screen boundary (bounds) and moving animation effects of the C1 page, so that the C1 page replaces the A page and is displayed in the left split screen of the electronic device, as Figure 3A shown in (41) of

[0401] Among them, the Activity corresponding to the C1 page can be set to any one of the four launch modes of the Activity. If the launch mode of the Activity corresponding to the C1 page is set to the singleInstance mode, the start mode of the C1 page is newtask start, then the split-screen boundary (bounds) of the C1 page can limit the window size of the C1 page.

[0402] 32. Open the B page from the A page displayed in the left split screen, and the B page replaces the A page displayed in the left split screen (corresponding to the step S132 as shown in Figure 3A ).

[0403] After the electronic device detects the operation 302 of the control B in the A page indicated by the user, it can send the parameter policy2 and params4 to the parallel window manager (HwMagicWindowManager).

[0404] Among them, due to the operation 302 performed by the user on page A, and page A is displayed in the left split screen, therefore, the parameter policy2 is used to identify the policy adopted when opening page B from page A displayed in the left split screen. The parameter policy2 can be represented in forms such as numbers, strings, letters, etc. params4 can include, but are not limited to: the token of the Activity corresponding to page A (i.e., the focus Activity), the token of the Activity corresponding to page B, and the configuration parameters of the intent used to start the Activity corresponding to page B.

[0405] Among them, the token of the Activity corresponding to page A is used to identify the Activity corresponding to page A. The token of the Activity corresponding to page B is used to identify the Activity corresponding to page B. The configuration parameters of the intent used to start the Activity corresponding to page B are used to start the Activity corresponding to page B.

[0406] Based on the token of the Activity corresponding to page A, the parallel window manager (HwMagicWindowManager) can determine whether the task stack corresponding to this Activity is in split screen mode (i.e., whether the page A corresponding to this Activity is in the state of split screen display).

[0407] Among them, the parallel window manager (HwMagicWindowManager) can determine the task stacks corresponding to the pages currently displayed on the electronic device (i.e., the task stack corresponding to page A and the task stack corresponding to page B), and determine whether the task stack corresponding to this Activity is in split screen mode by whether the task stack corresponding to page A and the task stack corresponding to page B are different task stacks. Thus, when it is determined that the task stack corresponding to page A and the task stack corresponding to page B are different task stacks, the parallel window manager (HwMagicWindowManager) can determine that the task stack corresponding to this Activity is in split screen mode.

[0408] Alternatively, the parallel window manager (HwMagicWindowManager) can obtain an indication flag from the electronic device, where this indication flag indicates whether the task stack corresponding to this Activity is in split screen mode. Thus, when this indication flag indicates that the task stack corresponding to this Activity is in split screen mode, the parallel window manager (HwMagicWindowManager) can determine that the task stack corresponding to this Activity is in split screen mode.

[0409] It should be noted that the present application is not limited to the foregoing two implementation manners to determine whether the task stack corresponding to the Activity is in the split-screen mode.

[0410] When the parallel window manager (HwMagicWindowManager) determines that the task stack corresponding to the Activity is in the split-screen mode, since the launch mode of the Activity corresponding to the B page is set to the singleInstance mode, the electronic device can create a new Task (i.e., a task stack different from the task stack corresponding to the A page and the task stack corresponding to the B page displayed in the right split screen), and based on the token of the Activity corresponding to the B page, start the configuration parameters of the intent used to start the Activity corresponding to the B page, so that the Activity corresponding to the B page is started in this new Task. Furthermore, the parallel window manager (HwMagicWindowManager) can determine split-screen parameters such as the split-screen boundary (bounds) and the moving animation effect of the B page, so that the B page replaces the A page and is displayed in the left split screen of the electronic device, as Figure 3A shown in (42).

[0411] Among them, Figure 3A The specific implementation manner of the step S132 shown is similar to Figure 3A the step S131 shown.

[0412] 41. The C1 page displayed in the left split screen exits the display (corresponding to the step S141 as shown in Figure 3B (41))

[0413] As Figure 3B shown in (41), the C1 page displayed in the left split screen may include a return control 2, which is used to indicate that the user can trigger the return control 2 from the C1 page, and the return control 2 is used to exit the display of the C1 page.

[0414] After the electronic device detects the operation 401 of the user indicating to trigger the return control 2 in the C1 page, it can exit the Activity corresponding to the C1 page, so that the electronic device returns from the user interface shown in the exemplary (41) to the user interface shown in the exemplary (3). Figure 3B shown in (41) Figure 3B shown in (3).

[0415] 42. The B page displayed in the left split screen exits the display (corresponding to the step S142 as shown in Figure 3B (42))

[0416] As Figure 3BAs shown in (42), the B page displayed on the left split screen may also include a return control 3, which is used to indicate that the user can trigger the return control 3 from the B page, and the return control 3 is used to exit the B page display.

[0417] After the electronic device detects the operation 402 of triggering the return control 3 in the B page indicated by the user, the activity corresponding to the B page in the left split screen can be exited, so that the electronic device changes from displaying the Figure 3B The user interface shown in (42) returns to the display as shown in the example Figure 3B (3) The user interface shown as an example.

[0418] 43. Exit the B page displayed on the right split screen (corresponding to Figure 3B Step S161 and step S162 shown in FIG.

[0419] like Figure 3B As shown in (41) and (42), the B page displayed on the right split screen may also include a return control 1, which is used to indicate that the user can trigger the return control 1 from the B page, and the return control 1 is used to exit the B page display.

[0420] After the electronic device detects the operation 403 of triggering the return control 1 in the B page indicated by the user, the activity corresponding to the B page in the right split screen can be exited, so that the electronic device changes from displaying the Figure 3B The user interface shown in (41) returns to the display as shown in the example Figure 3B The user interface shown in (1) or (2) of the example, or the electronic device is changed from displaying Figure 3B The user interface shown in (42) returns to the display as shown in the example Figure 3B The user interface shown in (1) or (2) as an example.

[0421] 5. Open a new page (i.e., page D) from page B displayed on the right split screen. Page D replaces page B displayed on the right split screen (corresponding to Figure 3A Step S15 shown)

[0422] After detecting the operation 501 of triggering the control D in the B page indicated by the user, the electronic device may send parameters policy3 and params5 to the parallel window manager (HwMagicWindowManager).

[0423] Among them, due to the operation 501 performed by the user on page B, and page B is displayed in the right split screen, therefore, the parameter policy3 is used to identify the policy adopted when opening page D from page B displayed in the right split screen. The parameter policy3 can be represented in forms such as numbers, strings, letters, etc. params5 can include, but are not limited to: the token of the Activity corresponding to page B (i.e., the focus Activity), the token of the Activity corresponding to page D, and the configuration parameters of the intent used to start the Activity corresponding to page D.

[0424] Among them, the token of the Activity corresponding to page B is used to identify the Activity corresponding to page B. The token of the Activity corresponding to page D is used to identify the Activity corresponding to page D. The configuration parameters of the intent used to start the Activity corresponding to page D are used to start the Activity corresponding to page D.

[0425] Based on the token of the Activity corresponding to page B, the Parallel Window Manager (HwMagicWindowManager) can determine whether the task stack corresponding to this Activity is in split screen mode (i.e., whether the page B corresponding to this Activity is in the state of split screen display).

[0426] Among them, the Parallel Window Manager (HwMagicWindowManager) can determine the task stacks corresponding to the pages currently displayed on the electronic device (i.e., the task stack corresponding to page A and the task stack corresponding to page B), and judge whether the task stack corresponding to this Activity is in split screen mode by whether the task stack corresponding to page A and the task stack corresponding to page B are different task stacks. Thus, when it is determined that the task stack corresponding to page A and the task stack corresponding to page B are different task stacks, the Parallel Window Manager (HwMagicWindowManager) can determine that the task stack corresponding to this Activity is in split screen mode.

[0427] Alternatively, the Parallel Window Manager (HwMagicWindowManager) can obtain an indication flag from the electronic device, where this indication flag indicates whether the task stack corresponding to this Activity is in split screen mode. Thus, when this indication flag indicates that the task stack corresponding to this Activity is in split screen mode, the Parallel Window Manager (HwMagicWindowManager) can determine that the task stack corresponding to this Activity is in split screen mode.

[0428] It should be noted that the present application is not limited to the aforementioned two implementation methods for determining whether the task stack corresponding to the Activity is in split-screen mode.

[0429] When the parallel window manager (HwMagicWindowManager) determines that the task stack corresponding to the Activity is in split-screen mode, it starts the configuration parameters of the intent for starting the Activity corresponding to the D page based on the token of the Activity corresponding to the D page, so that the Activity corresponding to the D page is started. Then, the parallel window manager (HwMagicWindowManager) can determine the split-screen parameters of the D page, such as the split-screen boundaries and moving animations, so that the D page replaces the B page and is displayed in the right split screen of the electronic device, such as Figure 3A If not, return.

[0430] The activity corresponding to the D page can be set to any of the four launch modes of the activity. If the launch mode of the activity corresponding to the D page is set to singleInstance mode, the launch mode of the D page is newtask launch, and the split screen boundary of the D page can limit the window size of the D page.

[0431] in, Figure 3A The specific implementation of step S15 shown is the same as Figure 3A The steps S131 and S132 shown are similar.

[0432] 6. Exit the D page displayed on the right split screen (corresponding to Figure 3B Step S18 shown)

[0433] like Figure 3B As shown in (5), the D page may also include a return control 4, which is used to indicate that the user can trigger the return control 4 from the D page, and the return control 4 is used to exit the D page display.

[0434] After the electronic device detects the operation 601 of triggering the return control 4 in the D page indicated by the user, the activity corresponding to the D page can be exited, so that the electronic device can return to the displayed page from the D page. Figure 3B The user interface shown in (5) returns to display Figure 3B (4) is an exemplary user interface shown.

[0435] In scenario 1, based on the above description, the electronic device can implement the following functions:

[0436] 1) When the electronic device responds to an operation triggered by the user, it can switch from the full-screen display of Page A to the split-screen display of Page A and Page B.

[0437] 2) When Page A and Page B are in split-screen display, if C1 page is opened from Page A, then C1 page destroys Page A and is displayed in the area where Page A was displayed, and Page B will not be destroyed.

[0438] 3) When Page A and Page B are in split-screen display, if D page is opened from Page B, then D page destroys Page B and is displayed in the area where Page B was displayed, and Page A will not be destroyed.

[0439] 4) When Page A and Page B are in split-screen display, closing C1 page will not affect the display of Page B.

[0440] 5) When Page A and Page B are in split-screen display, closing D page will not affect the display of Page A.

[0441] 6) Page B can freely switch between full-screen display and split-screen display.

[0442] Thus, when the user is processing multiple tasks in parallel, the electronic device can switch any application from the full-screen display of the main page to the split-screen display of other pages of the application, and the new page opened from any split screen will destroy the page displayed in that split screen and be displayed in that split screen, solving the problem in the related art that the new page opened from any split screen will destroy the pages displayed in other split screens due to the coupling relationship between different split screens, avoiding the display interference between the pages in different split screens, enabling the pages in different split screens to run independently, and providing the user with a multi-tasking or immersive experience. In addition, after the application starts the in-application split-screen function, based on the user's needs, the electronic device can switch from the split-screen display of multiple pages of the application to the full-screen display of one page of the application, or from the full-screen display of one page of the application to the split-screen display of multiple pages of the application, providing the user with an efficient and flexible multi-window multi-tasking experience.

[0443] Based on Figures 3A - 3F the description shown, combined with Figures 4A - 4L , introduce the specific implementation process for the electronic device to complete the split-screen display of multiple pages of any application. For the convenience of explanation, Figures 4A - 4LIn this example, the electronic device is a tablet computer, the application is the WeChat application, page A is the chat dialog list, the icon of the WeChat application is centered on page a0, page a1 is a specific chat dialog window, page B is the main page of the XX video browsing web page / XX video mini-program in the WeChat application, and the launch mode of page B is set to the singleInstance mode. Page C1 is page a1, and page D is the page of video 1 corresponding to the icon of video 1 on page B.

[0444] Please refer to Figures 4A - 4L , Figures 4A - 4L which is a schematic diagram of a human-computer interaction interface provided by an embodiment of the present application.

[0445] The tablet computer can display a user interface 11 as shown in Figure 4A the exemplary illustration. Among them, the user interface 11 can be the main interface (Home screen) of the desktop. The user interface 11 can include but is not limited to: a status bar, a navigation bar, a calendar indicator, a weather indicator, and multiple application icons, etc. The application icons at least include: the icon 401 of the WeChat application, and can also include: icons such as a calculator, an icon of Huawei Video, an icon of a browser, an icon of a camera, an icon of music, an icon of settings, an icon of email, an icon of a memo, etc.

[0446] After the tablet computer detects an operation of the user instructing to open the WeChat application (such as clicking on the icon 401 of the WeChat application), it can display Figure 4B the user interfaces 12a and 12b shown in the exemplary illustration, and the user interface 12a is displayed in the left split screen, and the user interface 12b is displayed in the right split screen. Among them, the user interface 12a can be used to display the main page of the WeChat application (i.e., page A). The user interface 12b can be used to display the secondary page of the WeChat application (i.e., page a0).

[0447] Among them, the display area areas of the user interfaces 12a and 12b can be the same or different, and the present application does not limit this. In addition, operation buttons for adjusting the display area areas of the user interfaces 12a and 12b can be set in the overlapping boundary area between the user interfaces 12a and 12b, so as to adjust the display area areas of the user interfaces 12a and 12b in real time based on user needs.

[0448] It should be noted that in addition to Figure 4B the user interfaces 12a and 12b shown in the exemplary illustration, the tablet computer can also display the main page of the WeChat application (i.e., page A) in full screen, or can also display the main page of the WeChat application (i.e., page A) in a partial display area (such as centered), and the present application does not limit this.

[0449] After the tablet computer detects that the user performs an operation such as clicking on the search control 402 in the user interface 12a shown in Figure 4B , the left split screen can change from displaying the Figure 4B exemplary user interface 12a shown to displaying the Figure 4C exemplary user interface 13a. Among them, the user interface 13a can be an interface for searching for searchable content in the WeChat application. And the tablet computer can continue to display the Figure 4C exemplary user interface 12b in the right split screen.

[0450] Among them, the search control 402 is schematically shown by taking a search icon as an example in Figure 4B . The search control 402 is used to enter an interface for searching for searchable content in the WeChat application. The searchable content in the WeChat application can include but is not limited to: mini programs, Moments, official accounts, articles, browsing web pages, etc.

[0451] It should be noted that in addition to the user clicking on the search control 402 shown in Figure 4B to provide the user with a way to search for XX video web pages / XX video mini programs, after the tablet computer detects that the user performs an operation such as pulling down and long-pressing in the user interface 12a indicated by the user, a mini program interface can be displayed, and thus a way to search for XX video web pages / XX video mini programs can be provided to the user. Or, after the tablet computer detects that the user performs a click operation on the contact icon in the user interface 12a indicated by the user, a search box can be displayed, and thus a way to search for XX video web pages / XX video mini programs can be provided to the user. This application does not limit the way to search for XX video web pages / XX video mini programs.

[0452] After the tablet computer detects that the user performs an input operation on the search box 403 in the user interface 13a shown in Figure 4C , the left split screen can change from displaying the Figure 4C exemplary user interface 13a shown to displaying the Figure 4D exemplary user interface 14a. Among them, the user interface 14a is used to display the search results 404 of XX video web pages / XX video mini programs. And the tablet computer can continue to display the Figure 4D exemplary user interface user interface 12b in the right split screen.

[0453] Among them, the search box 403 is used to search for searchable content in the WeChat application. The input operations performed by the user on the search box 403 in the user interface 13a can include text input, voice input, or video input, etc. For example, as Figure 4DAs shown, when the user enters the text XX Video in the search box 403, the tablet computer can search for the XX Video website / XX Video mini-program, and display the search results 404 of the XX Video website / XX Video mini-program.

[0454] When the XX Video mini-program has not been used in the WeChat application, the search results 404 do not include the controls of the used mini-programs. When the XX Video mini-program has been used in the WeChat application, the search results 404 may include the controls of the used mini-programs, and the controls of the used mini-programs include text such as Figure 4D shown, XX Video. Among them, the controls of the used mini-programs can be represented by text and / or icons for the mini-programs used in the WeChat application. In addition, the search results 404 at least include the "Search" control. The "Search" control is used to provide the user with other ways to search for the XX Video website / XX Video mini-program. The "Search" control can be represented by text and / or icons, such as Figure 4D the icon, the text "Search", and the text XX Video and mini-programs, Moments, official accounts, articles, browsing web pages, etc. shown.

[0455] After the tablet computer detects that the user performs an operation such as clicking on the text XX Video in the Figure 4D search results 404 shown, it can display Figure 4E the exemplary user interface 15. The user interface 15 is used to display the main page of the XX Video website / XX Video mini-program (i.e., page B, and the task stack corresponding to page B is a newly created task stack, different from the task stack corresponding to page A).

[0456] It should be noted that all the operations triggered by the user to display page B from Figures 4B - 4D can be regarded as the operation 101 corresponding to the control B triggered by the user on page A. Figure 3C in.

[0457] The user interface 15 at least includes: a multi-functional control 405 ( Figure 4E schematically shown by three solid dots in), a return control 406 ( Figure 4E schematically shown by a solid circle in a hollow circle in), and the page content of page B.

[0458] Among them, the multi-functional control 405 is used to enter the windows of functions such as sharing, removing, split-screen / full-screen display, floating window display, setting, feedback and complaint, re-entering, etc. of the XX Video website / XX Video mini-program.

[0459] Among them, the return control 406 is used to exit the XX Video website / XX Video mini-program, so that the tablet computer returns from the current user interface (such as the user interface 15 and the user interfaces 16b, 18b, and 19 mentioned later) and displaysFigure 4B Exemplarily shown user interfaces 12a and 12b. The return control 406 here can be regarded as Figure 3A and Figure 3B the return control 1 in

[0460] After the tablet computer detects that the user performs an operation such as clicking the multi-functional control 405 in the Figure 4E shown user interface 15, it can display on the user interface 15 Figure 4F exemplarily shown window 407, and the window 407 at least includes: control 4071.

[0461] Among them, the window 407 can be a window for functions such as sharing, removing, split-screen / full-screen display, floating window display, setting, feedback and complaint, re-entry, etc. of the XX video browsing web page / XX video mini-program, and is used to display functions such as sharing, removing, split-screen / full-screen display, floating window display, setting, feedback and complaint, re-entry, etc. of the XX video web page / XX video mini-program.

[0462] Among them, the control 4071 is used to implement the split-screen display of page B, and can be represented by an icon and / or text. For example, Figure 4F the control 4071 in is represented by the text "Display in split screen" and the icon Figure 3A and Figure 3B the split-screen / full-screen control in Figure 3C Here, the operation of clicking the multi-functional control 405 can be regarded as Figure 3C operation 101 in

[0463] After the tablet computer detects that the user indicates to perform an operation such as clicking the control 4071 in the Figure 4F shown window 407, it can display Figure 4G exemplarily shown user interfaces 16a and 16b, and the user interface 16a is displayed in the left split screen, and the user interface 16b is displayed in the right split screen. Among them, the user interface 16a is used to display the main page of the WeChat application (i.e., page A). The user interface 16b is used to display page B of the XX video web page / XX video mini-program.

[0464] Among them, the display area sizes of the user interfaces 16a and 16b may be the same or different, and the present application does not limit this. The display positions of the user interfaces 16a and 16b may be swapped, that is, the user interface 16a is displayed in the right split screen, and the user interface 16b is displayed in the left split screen. In addition, controls for adjusting the display area sizes of the user interfaces 16a and 16b may be provided in the overlapping boundary area between the user interfaces 16a and 16b, so as to adjust the display area sizes of the user interfaces 16a and 16b in real time based on user needs.

[0465] It should be noted that, in addition to the above method, when the tablet computer detects that the user performs an operation such as clicking on the text XX video in Figure 4D the search result 404 shown, the user interfaces 16a and 16b shown exemplarily can be displayed, and the user interface 16a is displayed in the left split screen, and the user interface 16b is displayed in the right split screen. That is, Figure 4G Figures 4E - 4F the description of the illustrated embodiment is an optional step. The operation of clicking on the text XX video here can be regarded as Figure 3D the operation 101 in

[0466] Thus, the tablet computer can display the main page of the WeChat application in the left split screen, and at the same time, display the XX video web page / XX video mini program in the WeChat application in the right split screen, enabling the user to perform operations such as clicking, swiping, and long pressing on pages A and B, and synchronously realizing functions such as content browsing, video watching, and instant messaging, improving the user experience.

[0467] In summary, Figures 4A - 4G according to the description of the illustrated embodiment, the electronic device can display page A in the left split screen of the electronic device and page B in the right split screen of the electronic device, thereby completing the in-application split screen display function of the WeChat application, that is, A on the left and B on the right.

[0468] It should be noted that, according to Figures 4A - 4G the description of the illustrated embodiment, the electronic device can realize the jump from displaying page A in the left split screen to displaying page B in the left split screen, and page B continues to be displayed in the right split screen, thereby completing the in-application split screen function of the WeChat application. Among them, a return control may also be included in page B displayed in the left split screen. The return control is used to exit page B displayed in the left split screen, so that the tablet computer returns from the current user interface and displays Figure 4G the user interfaces 16a and 16b shown exemplarily. The return control here can be regarded as Figure 3A and Figure 3B the return control 3 in

[0469] ​After the tablet computer detects that the user performs an operation such as clicking on the control 408 in the user interface 16a shown in Figure 4G , the left split screen can change from displaying the user interface 16a shown in the exemplary Figure 4G to displaying the user interface 17a shown in the exemplary Figure 4H . Among them, the user interface 17a can be a page for the user to chat with Xiaoyi (i.e., the C1 page). Thus, it is convenient for the user to browse the XX video website / XX video applet page while chatting with Xiaoyi on WeChat. And the tablet computer can continue to display the user interface 16b shown in the exemplary Figure 4H in the right split screen.

[0470] Among them, the control 408 is used to enter the page for the user to chat with Xiaoyi (i.e., the C1 page). The specific implementation manner of the control 408 in this application is not limited. In addition, the user interface 17a at least further includes a return control 410 ( Figure 4H uses a left arrow as an example for illustration). The return control 410 is used to exit the C1 page, so that the tablet computer can return from the user interface 17a and display the user interface 16a shown in the exemplary Figure 4G , facilitating the user to use other functions of the WeChat application. The return control 410 here can be regarded as the return control 2 in Figure 3A and Figure 3B .

[0471] In summary, Figures 4G - 4H according to the description of the illustrated embodiment, when the electronic device displays in a left - right split screen of the A page and the B page, the new page opened from the A page can replace the A page for display, rather than replacing the B page for display, realizing the independent and separate display of multiple pages in the application in the left - right split screen, avoiding the display interference between multiple pages in the application, that is, left - click and left - exit. In addition, the electronic device can also return from the new page to the A page for display, that is, the left - right tasks are independent.

[0472] After the tablet computer detects that the user performs an operation such as clicking on the control 409 in the user interface 16b shown in Figure 4G , the right split screen can change from displaying the user interface 16b shown in the exemplary Figure 4G to displaying the user interface 18b shown in the exemplary Figure 4I . Among them, the user interface 18b can be a page of Video 1 (i.e., the D page). Thus, it is convenient for the user to use the WeChat application while watching Video 1. And the tablet computer can continue to display the user interface 16a shown in the exemplary Figure 4I in the left split screen.

[0473] Among them, the control 409 is used to enter the page of Video 1 (i.e., the D page). The specific implementation manner of the control 409 is not limited in this application. In addition, the user interface 17a at least further includes a return control 411 ( Figure 4I taking an arrow pointing to the left as an example for illustration in Figure 4I ), and the return control 411 is used to exit the D page, so that the tablet computer can return from the user interface 18b and display Figure 4G the exemplary user interface 16b shown in Figure 4G , facilitating the user to use other functions of XX Video to browse the web / XX Video mini-program. The return control 411 here can be regarded as Figure 3A and Figure 3B the return control 4 in Figure 3B .

[0474] It should be noted that after the tablet computer detects that the user performs an operation such as clicking the control 409 in the user interface 16b shown in Figure 4H Figure 4H , it can change from displaying the exemplary user interface 16b shown in Figure 4H Figure 4H to displaying the exemplary user interface 18b shown in Figure 4I Figure 4I in the right split screen. Among them, the user interface 18b can be the page of Video 1 (i.e., the D page), thereby facilitating the user to chat with Xiaoyi while watching Video 1. And the tablet computer can continue to display the exemplary user interface 17a shown in Figure 4I Figure 4I in the left split screen. The foregoing method is another feasible implementation manner for the user to watch Video 1 on the tablet computer.

[0475] In summary, Figure 4G and Figure 4I as described in the embodiments shown in Figure 4I , when the electronic device displays the A page and the B page in a left - right split screen, the new page opened from the B page can replace the B page for display, rather than replacing the A page for display, realizing the independent and separate display of multiple pages in the application in a left - right split screen, avoiding the display interference between multiple pages in the application, that is, right - click and right - out. In addition, the electronic device can also return from the new page to the B page for display, that is, the left - right tasks are independent.

[0476] After the tablet computer detects that the user performs an operation such as clicking the multi - function control 405 in the user interface 18b shown in Figure 4I Figure 4I , it can display the exemplary window 407 shown in Figure 4J Figure 4J on the user interface 18b. The window 407 at least includes: a control 4072.

[0477] Among them, for the specific implementation manner of the window 407, reference can be made to the description of the embodiments shown in Figure 4F Figure 4F , which will not be elaborated here. The control 4072 is used to implement the full - screen display of the B page, and can be represented by an icon and / or text. For example, Figure 4JThe control 4072 in it is represented by the text "Exit split - screen display / Switch to full - screen display" and the icon as an example. The control 4072 here can be regarded as Figure 3A and Figure 3B the split - screen / full - screen control in. It should be noted that the control 4072 can also be displayed in the window 407 without being displayed through an operation such as clicking the multi - function control 405.

[0478] It should be noted that the control 4071 and the control 4072 are usually not displayed in the window 407 at the same time and are switched and displayed in the same area in the window 407. Among them, when the B page is in full - screen display, the tablet computer can display the control 4071 in the window 407, thus facilitating the user to switch the B page from full - screen display to split - screen display. When the B page is in split - screen display, the tablet computer can display the control 4072 in the window 407, thus facilitating the user to switch the B page from split - screen display to full - screen display.

[0479] After the tablet computer detects that the user performs an operation of clicking the control 4072 in the Figure 4J shown window 407, it can display Figure 4K the exemplary user interface 19, where the user interface 19 is used to full - screen display the B page of the XX video website / XX video mini - program, thus facilitating the user to watch the video 1 in full - screen.

[0480] In summary, Figures 4I - 4K through the description of the shown embodiment, the electronic device can realize the switch of the video 1 from split - screen display to full - screen display.

[0481] After the tablet computer detects that the user performs an operation such as clicking the multi - function control 405 in the Figure 4K shown user interface 19, it can display Figure 4L the exemplary window 407 on the user interface 19, and the window 407 at least includes: the control 4071.

[0482] Among them, the specific implementation manners of the window 407 and the control 4071 can be referred to Figure 4F or Figure 4J the description of the shown embodiment, and will not be elaborated here.

[0483] After the tablet computer detects that the user performs an operation of clicking the control 4071 in the Figure 4L shown window 407, it can display Figure 4I the exemplary user interface 16a and user interface 18b, thus facilitating the user to run the WeChat application while watching the video 1.

[0484] In summary, Figure 4K 、 Figure 4L 、 Figure 4IDescription of the illustrated embodiment, the electronic device can implement the video 1 from full-screen display to split-screen display.

[0485] Based on Figures 3A - 3B the illustrated description, combined with Figure 4A , Figures 4M - 4W , introduce the specific implementation process of the electronic device to complete the split-screen display of multiple pages of any application. For the convenience of description, Figure 4A , Figures 4M - 4W , take the electronic device as a tablet computer, the application as the WeChat application, the A page as the chat dialog list, the a0 page includes the icon of the WeChat application set in the center, the a1 page is the main page of the XX Express Cabinet public account in the WeChat application, the a2 page is any page other than the main page of the XX Express Cabinet public account in the WeChat application, the B page is any page other than the main page of the XX Express Cabinet public account in the WeChat application, and the launch mode of the B page is not set to the singleInstance mode, the C1 page is the a1 page, and the D page is any page other than the main page of the XX Express Cabinet public account in the WeChat application as an example for illustration.

[0486] Please refer to Figure 4A , Figures 4M - 4W , Figures 4M - 4W which is a schematic diagram of the human-computer interaction interface provided by an embodiment of the present application.

[0487] The tablet computer can display the user interface 11 as shown in Figure 4A exemplarily. After the tablet computer detects the operation of the user instructing to open the WeChat application (such as clicking the icon 401 of the WeChat application), it can display Figure 4M the user interface 12a and the user interface 12b shown exemplarily, and the user interface 12a is displayed in the left split screen, and the user interface 12b is displayed in the right split screen. The user interface 12a can be used to display the main page of the WeChat application (i.e., the A page). The user interface 12b can be used to display the secondary page of the WeChat application (i.e., the a0 page).

[0488] Among them, the specific description of the user interface 11 can be referred to the previous description, and the specific description of the user interface 12a and the user interface 12b can be referred to Figure 4B the exemplary description, which will not be elaborated here. Which will not be elaborated here.

[0489] The tablet computer detects that the user is in Figure 4M the user interface 12a shown, and after performing an operation such as clicking the search control 412, it can change from displaying Figure 4M the user interface 12b shown exemplarily in the right split screen to displaying Figure 4NThe exemplary user interface 41b. Among them, the user interface 41b can be used to display the main page (i.e., the a1 page) of the XX Express Cabinet official account in the WeChat application. And, the tablet computer can continue to display in the left split screen Figure 4N The exemplary user interface 12a. The user interface 41b at least includes: a control 413 ( Figure 4N taking a pattern similar to a person as an example for illustration), a return control 414 ( Figure 4N taking a left arrow as an example for illustration) and the page content of the a1 page. Among them, the control 413 is used to implement the display of the B page. The present application does not limit the specific implementation manner of the control 413. The return control 414 is used to exit the XX Express Cabinet official account, so that the tablet computer can return from the user interface 41b and display Figure 4M The exemplary user interface 12b, which is convenient for users to use other functions of the WeChat application.

[0490] It should be noted that in addition to the way that the user clicks on the search control 412 as Figure 4M shown to provide the main page of the XX Express Cabinet official account to the user, after the tablet computer detects that the user clicks on the search button on the main page shown in the user interface 12 as indicated by the user, a search box can be displayed, and thus a way to search for the XX Express Cabinet official account can be provided to the user. Or, after the tablet computer detects that the user clicks on the icon of the address book in the user interface 12a as indicated by the user, a search box can be displayed, and thus a way to search for the XX Express Cabinet official account can be provided to the user. The present application does not limit the way to search for the XX Express Cabinet official account.

[0491] After the tablet computer detects that the user performs an operation such as clicking on the control 413 in the Figure 4N shown user interface 41b, it can change from displaying the Figure 4N exemplary user interface 41b to displaying the Figure 4O exemplary user interface 42b in the right split screen. Among them, the user interface 42b is used to display any interface (i.e., the a2 page) of the XX Express Cabinet official account in the WeChat application other than the main page. And, the tablet computer can continue to display in the left split screen Figure 4O the exemplary user interface 12a.

[0492] Among them, the user interface 42b at least includes: a control 415 ( Figure 4O taking picture 1 and the text aaa as an example for illustration). The control 415 is used to implement the display of the B page. The present application does not limit the specific implementation manner of the control 415. In some embodiments, the control 415 can be represented in at least one form such as a link, a video, a picture, a string or text.

[0493] In addition, the user interface 42b may also include: a return control 416 ( Figure 4O The return control 416 is used to exit the a1 page, so that the tablet computer can return from the user interface 42b and display Figure 4N The user interface 41b shown as an example facilitates users to use other functions of the XX Express Cabinet public account in the WeChat application.

[0494] The tablet detects that the user is Figure 4O After performing an operation such as clicking the control 415 in the user interface 42b shown in FIG. Figure 4P The user interface 43 is shown as an example. The user interface 43 is used to display any page of the XX Express Cabinet public account in the WeChat application except the main page (ie, page B, and the task stack corresponding to page B is the same as the task stack corresponding to page A).

[0495] It should be noted that from Figures 4M - 4O All operations that the user triggers to display page B can be regarded as the corresponding operations that the user triggers control B on page A. Figure 3E Operation 101 in.

[0496] The user interface 43 at least includes: a multi-function control 417 ( Figure 4P Three solid dots are used as an example), return control 418 ( Figure 4P In the figure, a solid circle in a hollow circle is used as an example for illustration) and the page content of page B.

[0497] Among them, the multi-function control 417 is used to enter the B page of the XX express cabinet official account, such as sending to friends, split screen to friends circle, reading, favorites, opening in the browser, split screen / full screen display, floating window display, complaint, copy link, refresh, search page content, full text translation, adjust font and other functions.

[0498] The return control 418 is used to exit the B page, so that the tablet computer returns from the current user interface (such as the user interface 43 and the user interface 44b, user interface 46b and user interface 47 mentioned later) and displays Figure 4O The user interface 12a and the user interface 42b are shown as examples. The return control 418 here can be seen as Figure 3A and Figure 3B Return control 1 in .

[0499] The tablet detects that the user is Figure 4P After performing an operation such as clicking the multi-function control 417 in the user interface 43 shown in the figure, the user interface 43 may display Figure 4Q The window 419 shown as an example includes at least: a control 4191.

[0500] Among them, the window 419 can be a window for functions such as sending to friends, splitting the screen to the circle of friends, "liking", collecting, opening in the browser, splitting / full-screen display, floating window display, complaining, copying the link, refreshing, searching for page content, full text translation, adjusting the font, etc. on page B of the XX express delivery cabinet official account, and is used to display functions such as sending to friends, splitting the screen to the circle of friends, "liking", collecting, opening in the browser, splitting / full-screen display, floating window display, complaining, copying the link, refreshing, searching for page content, full text translation, adjusting the font, etc. on page B of the XX express delivery cabinet official account.

[0501] Among them, the control 4191 is used to implement the split-screen display of page B, and can be represented by an icon and / or text. For example, Figure 4Q the control 4191 in is represented by the text "Display in split screen" and an icon Figure 3A and Figure 3B as an example. The control 4191 here can be regarded as the split-screen / full-screen control in Figure 3E . The operation of clicking the multi-functional control 417 here can be regarded as the operation 101 in Figure 3E , and the operation of clicking the control 4191 here can be regarded as the operation 102 in

[0502] After the tablet computer detects the operation of clicking the control 4191 in the window 419 shown in Figure 4Q , it can display the user interfaces 44a and 44b shown exemplarily, and the user interface 44a is displayed in the left split screen, and the user interface 44b is displayed in the right split screen. Among them, the user interface 44a is used to display the main page (i.e., page A) of the WeChat application. The user interface 44b is used to display page B other than the main page of the XX express delivery cabinet official account in the WeChat application. The task stack corresponding to page B here is a newly created task stack, which is different from the task stack corresponding to page A. Figure 4R

[0503] Among them, the display area areas of the user interfaces 44a and 44b can be the same or different, and the present application does not limit this. The display positions of the user interfaces 44a and 44b can be interchanged, that is, the user interface 44a is displayed in the right split screen, and the user interface 44b is displayed in the left split screen. In addition, a control for adjusting the display area areas of the user interfaces 44a and 44b can be set in the overlapping boundary area of the user interfaces 44a and 44b, so as to adjust the display area areas of the user interfaces 44a and 44b in real time based on user needs.

[0504] ​It should be noted that, in addition to the above methods, after the tablet computer detects that the user performs an operation such as clicking on the control 415 in the user interface 42b shown in Figure 4O it can display the user interfaces 44a and 44b shown exemplarily in Figure 4R where the user interface 44a is displayed in the left split screen and the user interface 44b is displayed in the right split screen. That is, Figures 4P - 4Q the description of the illustrated embodiment is an optional step. The operation of clicking on the control 415 here can be regarded as Figure 3F the operation 101 in

[0505] Thus, the tablet computer can display the main page of the WeChat application in the left split screen, and at the same time, display any page of the XX courier cabinet official account in the WeChat application in the right split screen, enabling the user to perform operations such as clicking, swiping, and long pressing on pages A and B, and synchronously realizing functions such as content browsing, video watching, and instant messaging, improving the user experience.

[0506] In summary, Figure 4A 、 Figures 4M - 4R According to the description of the illustrated embodiment, the electronic device can display page A in the left split screen of the electronic device and page B in the right split screen of the electronic device, thereby completing the in-application split screen display function of the WeChat application, that is, A on the left and B on the right.

[0507] After the tablet computer detects that the user performs an operation such as clicking on the control 420 in the user interface 44a shown in Figure 4R it can change from displaying the user interface 14a shown exemplarily in Figure 4R to displaying the user interface 45a shown exemplarily in Figure 4S in the left split screen, where the user interface 45a can be a page for the user to chat with xiaoyi (i.e., page C1), thereby facilitating the user to browse page B while chatting with xiaoyi on WeChat. And the tablet computer can continue to display the user interface 44b shown exemplarily in Figure 4S in the right split screen.

[0508] Among them, for the specific implementation method of the user interface 45a, reference can be made to the description of the user interface 16a shown in Figure 4G and for the specific implementation method of the control 420, reference can be made to the description of the control 408 in the user interface 16a shown in Figure 4G which will not be elaborated here.

[0509] In summary, Figures 4R - 4SIn the description of the illustrated embodiment, when the electronic device displays in a split screen on the left and right between page A and page B, a new page opened from page A can replace page A for display, rather than replacing page B for display, achieving independent and separate display of multiple pages within the application in a split screen on the left and right, avoiding display interference between multiple pages within the application, that is, left-click and left-out. In addition, the electronic device can also return from the new page to page A for display, that is, the left and right tasks are independent.

[0510] After the tablet computer detects that the user performs an operation such as swiping up in the Figure 4R user interface 44b shown, it can change from displaying the Figure 4R[[END exemplary user interface 44b in the right split screen to displaying the ​ exemplary user interface 46a. Among them, the user interface 46a can be used to display any page (i.e., page D) other than the main page of the XX courier cabinet official account in the WeChat application, thereby facilitating the user to use the WeChat application while also being able to view page D. And the tablet computer can continue to display the ​ exemplary user interface 44b in the right and left split screens.

[0511] In addition, after the tablet computer detects that the user performs an operation such as swiping down in the ​ user interface 46b shown, it can return from the user interface 46b and display the ​ exemplary user interface 44b, facilitating the user to view page B again. The operation such as swiping down here can be regarded as the ​ and ​ return control 4 in.

[0512] It should be noted that after the tablet computer detects that the user performs an operation such as swiping up in the ​ user interface 44b shown, it can change from displaying the ​ exemplary user interface 44b in the right split screen to displaying the ​ exemplary user interface 46b. Among them, the user interface 46a can be used to display any page (i.e., page D) other than the main page of the XX courier cabinet official account in the WeChat application, thereby facilitating the user to use the WeChat application while also being able to view page D. And the tablet computer can continue to display the ​ exemplary user interface 45a in the left split screen. The foregoing method is another feasible implementation for the user to view page D on the tablet computer.

[0513] In summary, ​ and ​In the description of the illustrated embodiment, when the electronic device displays in a split screen on the left and right between page A and page B, a new page opened from page B can replace page B for display, rather than replacing page A for display, realizing independent and separate display of multiple pages in the application in a split screen on the left and right, avoiding display interference between multiple pages in the application, that is, right-clicking to exit on the right. In addition, the electronic device can also return from the new page to page B for display, that is, the left and right tasks are independent.

[0514] The tablet computer, after detecting that the user performs an operation such as clicking the multi-functional control 417 in ​ the illustrated user interface 46b, can display ​ the exemplary window 419 on the user interface 46b. The window 419 at least includes: the control 4192.

[0515] Among them, for the specific implementation manner of the window 419, reference can be made to ​ the description of the illustrated embodiment, which will not be elaborated here. The control 4192 is used to implement full-screen display of page B and can be represented by an icon and / or text. For example, ​ the control 4192 in is represented by the text "Exit split screen display / Switch to full screen display" and an icon ​ as an example. The control 4192 here can be regarded as ​ the split screen / full screen control in

[0516] It should be noted that the control 4191 and the control 4192 are usually not displayed in the window 419 at the same time and are switched and displayed in the same area in the window 419. Among them, when page B is in full-screen display, the tablet computer can display the control 4191 in the window 419, thus facilitating the user to switch page B from full-screen display to split-screen display. When page B is in split-screen display, the tablet computer can display the control 4192 in the window 419, thus facilitating the user to switch page B from split-screen display to full-screen display.

[0517] The tablet computer, after detecting that the user performs an operation of clicking the control 4192 in ​ the illustrated window 419, can display ​ the exemplary user interface 47. Among them, the user interface 47 is used to full-screen display page D of the XX express cabinet official account, thus facilitating the user to view page D in full screen.

[0518] In summary, ​ in the description of the illustrated embodiment, the electronic device can realize the switch of page D from split-screen display to full-screen display.

[0519] The tablet computer, after detecting that the user is in​ After performing an operation such as clicking the multi-function control 417 in the user interface 47 shown in the figure, the user interface 47 may display Figure 4W The window 419 shown as an example includes at least: a control 4191.

[0520] The specific implementation of window 419 and control 4191 can be found in Figure 4Q or Figure 4U The description of the illustrated embodiment is not repeated here.

[0521] The tablet detects that the user is Figure 4W After the operation of clicking the control 4191 is executed in the window 419 shown in FIG. Figure 4T The user interface 44a and user interface 46b shown as examples make it convenient for users to browse the D page of the XX Express Cabinet public account while running the WeChat application.

[0522] In summary, Figure 4V , Figure 4W , Figure 4T According to the description of the illustrated embodiment, the electronic device can realize the D page from full-screen display to split-screen display.

[0523] based on Figures 4A - 4L ,as well as Figure 4A , Figures 4M - 4W As described in the embodiment, for various forms of pages such as browsing web pages, mini-programs, and public accounts in the WeChat application, the electronic device can display multiple pages of the WeChat application in split screen, realizing the in-application split screen function of the WeChat application. Thus, for any application, the electronic device can realize the split screen display function of the application.

[0524] Scene 2

[0525] In scenario 1, the electronic device detects that the user triggers control B in page A. In scenario 2, the electronic device detects that the user triggers control B in page a1. The difference between scenario 1 and scenario 2 is that the pages where control B is located are different, so that the electronic device implements different pages for split-screen display of the application.

[0526] Thus, after the electronic device detects the user's instruction to trigger the operation of the control B in the a1 page, the a1 page and the B page can be displayed in split screen, thereby realizing the in-application split-screen function of the application.

[0527] See also Figures 5A - 5F , Figures 5A - 5F A schematic diagram of a process for implementing split-screen display within an application provided by an embodiment of the present application. Figure 5A It shows the process from the current page display of the application to the next page, Figure 5BShows the process of returning from the current page of the application to the previous page, and Figures 5A - 5B the display pages in

[0528] 0. Display of a1 page

[0529] When the electronic device is in the landscape screen state, the display screen of the electronic device can display an interface as shown in Figure 5A (1a) of this. This interface includes page A and page a1.

[0530] Figure 5A In (1a) of this, the a1 page displayed in this interface includes control B, which is used to indicate that the user can trigger control B from the a1 page. The a1 page displayed in this interface also includes control C2, which is used to indicate that the user can trigger control C2 from the a1 page. Among them, control C2 is used to trigger the display of page C2, and page C2 is all the pages in this application except for page a1 and page B. Page C2 may or may not include page A, and this application does not make any limitations on this.

[0531] Among them, the a1 page can be displayed full screen, as shown in Figure 5A (1b) of this, or it can be displayed in a partial display area of the display screen, such as only the a1 page is displayed in a partial display area of the display screen (as shown in Figure 5A (1c) of this) or page A and page a1 are split-screen displayed left and right (as shown in Figure 5A (1a) of this). This application does not make any limitations on the display method of the a1 page, and it is specifically set according to the configuration parameters of the application itself and the configuration parameters of the software system. For the sake of easy explanation, in scenario two, the example of page A being displayed in the left split screen and page a1 being displayed in the right split screen as shown in Figure 5A (1a) of this is used for illustration.

[0532] In some embodiments, the a1 page displayed in this interface may further include a return control 02 ( Figure 5A not shown in this), which is used to indicate that the user can trigger the return control 02 from the a1 page. The return control 02 is used to trigger exiting the a1 page or entering the main page of this application (i.e., page A). For example, the user can trigger the return control 02 from the a1 page, and the electronic device can pop up the Activity corresponding to the a1 page and start the Activity corresponding to page A, so that the display screen of the electronic device displays page A, or the electronic device can pop up the Activity corresponding to the a1 page, so that the display screen of the electronic device displays a pre-stored picture, such as the logo of the WeChat application, etc.

[0533] 1. Left and right split-screen display of page a1 and page B (corresponding to step S21 as shown in Figure 5A this)

[0534] In some embodiments, after the electronic device detects the operation 701 of the control B in the a1 page indicated by the user, if the launch mode of the Activity corresponding to the B page is set to the singleInstance mode, a new Task (i.e., a task stack different from the task stack corresponding to the a1 page) can be established, and the Activity corresponding to the B page can be launched in a new Task.

[0535] Among them, the aforementioned new Task and the Task corresponding to the a1 page are different Tasks, which can be understood as the Activity corresponding to the B page entering a task different from the Activity corresponding to the a1 page. The control B can be referred to the description above, and will not be elaborated here.

[0536] After the Activity corresponding to the B page is launched, the electronic device can default to display the B page (i.e., full-screen display as shown in (2) of Figure 5A or display in a partial display area). And, the B page includes a split-screen / full-screen control, which is used to indicate that the user can trigger the split-screen / full-screen control from the B page, and the split-screen / full-screen control is used for split-screen display or full-screen display of the B page.

[0537] After the electronic device detects the operation 702 of the split-screen / full-screen control in the B page indicated by the user, it can send a message 9 to the application. The message 9 is used to identify the aforementioned operation 702, so that the application can obtain the taskID of the Activity corresponding to the B page from the software system of the electronic device, determine the split-screen position of the B page based on the aforementioned operation 702, and determine the method name (referred to as setTaskPosition) of the method (method) 2 for split-screen display within the application based on the aforementioned operation 702. The method 2 is used to indicate split-screen display of the a1 page and the B page. Among them, the present application does not limit the representation method of the message 9. For example, the message 9 can be the reporting point coordinates of the aforementioned operation 702.

[0538] Among them, the split-screen position mentioned above can be referred to the description of the split-screen position in Scenario 1, and will not be elaborated here.

[0539] In summary, the software system of the electronic device notifies the aforementioned operation 702 to the application, so that the application can obtain the taskID of the Activity corresponding to the B page, the split-screen position of the B page, and the method name (referred to as setTaskPosition) of the method (method) 2 for split-screen display within the application.

[0540] It should be noted that for the execution steps of the electronic device to establish a new Task in response to operation 701, the software system of the electronic device sends the execution steps of the aforementioned operation 701 to the application. There is no order in terms of timing, and they can be executed simultaneously or sequentially. This application does not make any restrictions on this.

[0541] Based on the description of the foregoing embodiments, the application can call the invoke interface in the third-party interface layer (EasyGoSDK) of the electronic device, and pass message 10. Message 10 carries the method name (setTaskPosition) of method 2, the split-screen position (targetPosition), and the task ID of the Activity corresponding to page B.

[0542] Among them, this application does not make any restrictions on the representation of message 10. For example, the split-screen position (targetPosition) and the task ID of the Activity corresponding to page B can be passed using parameter params6. The definition of the invoke interface can be referred to the description in Scenario 1 and will not be elaborated here. It should be noted that the task ID of the Activity corresponding to page B can be replaced by the ID of page B. This application does not make any restrictions on this, and only the identifier used to represent page B needs to be transmitted. Among them, this application does not make any restrictions on this identifier.

[0543] In summary, the third-party interface layer (EasyGoSDK) can obtain the method name (setTaskPosition) of method 2, the split-screen position (targetPosition), and the task ID of the Activity corresponding to page B. And the third-party interface layer (EasyGoSDK) can also obtain (such as actively querying) the package name of the application.

[0544] The third-party interface layer (EasyGoSDK) sends the method name (setTaskPosition) of method 2, the split-screen position (targetPosition), the task ID of the Activity corresponding to page B, and the package name of the application to the parallel window manager (HwMagicWindowManager) of the electronic device.

[0545] Among them, the package name of the application, the split-screen position (targetPosition), and the task ID of the Activity corresponding to page B can be passed using parameter params7.

[0546] Based on Figure 2bFor the structure shown, by using a policy module, a configuration module, a data management module, a background layer drawing module, and an animation effect module, the parallel window manager (HwMagicWindowManager) can implement the following process:

[0547] The parallel window manager (HwMagicWindowManager) can determine whether the method name (setTaskPosition) of method 2 and the content of params7 are empty. When the method name (setTaskPosition) of method 2 and the content of params7 are not empty, the parallel window manager (HwMagicWindowManager) can perform the following three steps:

[0548] Step 21-1: The parallel window manager (HwMagicWindowManager) can, based on the taskID of the Activity corresponding to page B, determine whether the Activity corresponding to this taskID is the top Activity of the current task stack (i.e., determine whether the focused task stack exists). Furthermore, when the Activity corresponding to this taskID is the top Activity of the current task stack, the electronic device can ensure that the current task stack exists.

[0549] Among them, step 21-1 is an optional step.

[0550] Step 21-2: Based on the package name (packagename) of the application, the parallel window manager (HwMagicWindowManager) can determine whether the application corresponding to this package name supports the in-app split-screen function. Furthermore, when the electronic device determines that the application corresponding to this package name supports the in-app split-screen function, the electronic device can ensure that the application can support the split-screen display of multiple pages of this application.

[0551] Among them, the specific process for the electronic device to determine whether the application corresponding to this package name supports the in-app split-screen function can be: The electronic device can determine whether the application corresponding to this package name itself has the in-app split-screen function, and determine whether the electronic device has enabled the in-app split-screen function of this application.

[0552] When the electronic device can determine that the application corresponding to this package name itself supports the in-app split-screen function and the electronic device has enabled the in-app split-screen function of this application, the electronic device can determine that the application corresponding to this package name supports the in-app split-screen function.

[0553] Among them, the electronic device can store in advance the package names of the applications that support the in-application split-screen function (such as setting a whitelist), or obtain from the AndroidManifest.xml file of each application an identifier indicating whether the application supports the in-application split-screen function. This application does not make any limitations in this regard. Furthermore, the electronic device can determine whether the application corresponding to the package name itself supports the in-application split-screen function based on the foregoing description.

[0554] Among them, the data management module stores the user selection data of each application in the settings application. The user selection data of each application can be used to indicate whether the electronic device enables the in-application split-screen function of the application. Furthermore, the electronic device can obtain the user selection data of the application corresponding to the package name in the settings application from the data management module, and determine whether the electronic device enables the in-application split-screen function of the application based on the user selection data of the application corresponding to the package name. Furthermore, the electronic device can determine whether the application corresponding to the package name itself supports the in-application split-screen function.

[0555] Step 21-3: Based on the split-screen position (targetPosition), the parallel window manager (HwMagicWindowManager) can determine whether the moving position of page B meets the preset requirements for split-screen display (for example, the secondary screen (such as the right split-screen) or full screen, such as determining whether the value of targetPosition is 1 or 2). Furthermore, when the moving position of page B meets the preset requirements for split-screen display, the electronic device can determine that split-screen display of page B can be achieved.

[0556] Among them, the preset requirements for split-screen display are related to the way the electronic device displays page B (that is, split-screen or full-screen display).

[0557] When the electronic device displays page B in full screen, the preset requirements for split-screen display can indicate that page B can be in split-screen display. For example, the value of targetPosition can be set to 1 or 2. Thus, when the electronic device needs to achieve split-screen display of the full-screen displayed page B, it can check whether the value of targetPosition is 1 or 2. If the value of targetPosition is 1 or 2, the electronic device determines that the moving position of page B meets the preset requirements for split-screen display.

[0558] When the electronic device displays page B in split screen, the preset requirements for split-screen display can indicate that page B cannot be in split-screen display and can be in full-screen display. For example, the value of targetPosition can be set to 0. Thus, when the electronic device needs to achieve full-screen display of the split-screen displayed page B, it can check whether the value of targetPosition is 0. If the value of targetPosition is 0, the electronic device determines that the moving position of page B meets the preset requirements for split-screen display.

[0559] Among them, the execution order of steps 21-1, 21-2, and 21-3 is not sequential. They can be executed sequentially or simultaneously. This application does not make any restrictions on this.

[0560] When the judgment results of steps 21-1, 21-2, and 21-3 are all yes, the parallel window manager (HwMagicWindowManager) can determine the taskID of the Activity corresponding to page a1 based on the package name of the application.

[0561] Based on the split-screen position (targetPosition) and the taskID of the Activity corresponding to page B, the parallel window manager (HwMagicWindowManager) can determine split-screen parameters such as the split-screen boundary (bounds) and moving animation effects of page B, or the split-screen parameters such as the split-screen boundary (bounds) and moving animation effects of page a1 and page B.

[0562] Based on the taskID of the Activity corresponding to page a1, the taskID of the Activity corresponding to page B, and the split-screen parameters of page B, the parallel window manager (HwMagicWindowManager) simultaneously displays two independent tasks on the left and right split-screens of the display screen, that is, as shown in (3) below, page a1 is displayed on the left split-screen of the electronic device and page B is displayed on the right split-screen of the electronic device. Figure 5A as shown in (3) below, page a1 is displayed on the left split-screen of the electronic device and page B is displayed on the right split-screen of the electronic device.

[0563] Based on the foregoing description, combined with Figure 5C ,the implementation process of split-screen display of page a1 and page B on the electronic device is specifically described.

[0564] As Figure 5C shown, the specific implementation process of the application page display method of this application may include the following steps:

[0565] S41. The electronic device displays page a1.

[0566] S421. When the electronic device receives the user's operation 701 on page a1, a new Task is established (that is, a task stack different from the task stack corresponding to page a1), and the Activity corresponding to page B is started in the new Task, and page B is displayed.

[0567] S422. When the electronic device receives the user's operation 702 on page B, a message 9 is sent to the application, and message 9 is used to identify operation 702.

[0568] S43. In response to message 9, the application obtains the method name of method 2 (referred to as setTaskPosition), the split-screen position of page B (targetPosition), and the task ID of the Activity corresponding to page B.

[0569] S44. The application sends message 10 to the third-party interface layer (EasyGoSDK). Message 10 carries the method name of method 2 (referred to as setTaskPosition), the split-screen position of page B (targetPosition), and the task ID of the Activity corresponding to page B.

[0570] S45. The third-party interface layer (EasyGoSDK) sends the method name of method 2 (referred to as setTaskPosition), the split-screen position of page B (targetPosition), the task ID of the Activity corresponding to page B, and the package name of this application to the parallel window manager (HwMagicWindowManager).

[0571] S461. The parallel window manager (HwMagicWindowManager) determines whether the Activity corresponding to the task ID of the Activity corresponding to page B is the top Activity of the current task stack.

[0572] Step S461 is an optional step.

[0573] S462. The parallel window manager (HwMagicWindowManager) determines whether the application corresponding to the package name of this application supports the in-application split-screen function.

[0574] S463. The parallel window manager (HwMagicWindowManager) determines whether the moving position of page B meets the preset requirements for split-screen display based on the split-screen position of page B (targetPosition).

[0575] S47. When the judgment results of S461, S462, and S463 are all yes, the parallel window manager (HwMagicWindowManager) determines the task ID of the Activity corresponding to page a1 based on the package name of this application, and determines the split-screen parameters of page B based on the split-screen position (targetPosition) and the task ID of the Activity corresponding to page B.

[0576] In addition, when the judgment result in any one of steps S461, S462, and S463 by the parallel window manager (HwMagicWindowManager) is negative, the B page continues to be displayed.

[0577] S48. The parallel window manager (HwMagicWindowManager) simultaneously displays the a1 page and the B page based on the task ID of the Activity corresponding to the a1 page, the task ID of the Activity corresponding to the B page, and the split-screen parameters of the B page.

[0578] It should be noted that Figure 5C For the specific implementation process shown by way of example, reference may be made to the foregoing content, and details are not described herein again.

[0579] In some other embodiments, after the electronic device detects the operation 701 of the user instructing to trigger the control B in the a1 page, if the launch mode of the Activity corresponding to the B page is set to the singleInstance mode, a new Task (i.e., a task stack different from the task stack corresponding to the a1 page) can be established, and the Activity corresponding to the B page is started in a new Task.

[0580] Among them, the foregoing new Task and the Task corresponding to the a1 page are different Tasks, which can be understood as the Activity corresponding to the B page enters a task different from the Activity corresponding to the a1 page. The control B can be referred to the foregoing description, and details are not described herein again.

[0581] Moreover, the electronic device can send a message 11 to the application, and the message 11 is used to identify the foregoing operation 701. Then, in response to the foregoing operation 701, the application can obtain the ID of the task (abbreviation: taskID) of the Activity corresponding to the B page from the software system of the electronic device, determine the split-screen position of the B page based on the foregoing operation 701, and determine the method name (referred to as setTaskPosition) of the method 2 for split-screen display within the application based on the foregoing operation 701. The method 2 is used to represent splitting the a1 page and the B page for display. Among them, the present application does not limit the representation manner of the message 11. For example, the message 11 can be the reported point coordinates of the foregoing operation 701.

[0582] Among them, the split-screen position mentioned above can be referred to the description of the split-screen position mentioned above, and details are not described herein again.

[0583] In summary, the software system of the electronic device notifies the application of the foregoing operation 701, so that the application can obtain the task ID of the Activity corresponding to page B, the split-screen position of page B, and the method name (referred to as setTaskPosition) of method 2 for split-screen display within the application.

[0584] It should be noted that for the execution steps of establishing a new Task in response to operation 701 by the electronic device, the software system of the electronic device sends the execution steps of the foregoing operation 701 to the application, and there is no order in time sequence. They can be executed simultaneously or sequentially. The present application does not make any limitations in this regard.

[0585] Based on the description of the foregoing embodiments, the application can call the invoke interface in the third-party interface layer (EasyGoSDK) of the electronic device, and transmit message 12. Message 12 carries the method name (setTaskPosition) of method 2, the split-screen position (targetPosition), and the task ID of the Activity corresponding to page B.

[0586] Among them, the present application does not limit the representation method of message 12. For example, the split-screen position (targetPosition) and the task ID of the Activity corresponding to page B can be transmitted using parameter params6. The definition of the invoke interface can be referred to the description in Scenario 1 and will not be elaborated here. It should be noted that the task ID of the Activity corresponding to page B can be replaced by the ID of page B. The present application does not make any limitations in this regard, as long as the identifier used to represent page B is transmitted. Among them, the present application does not limit this identifier.

[0587] In summary, the third-party interface layer (EasyGoSDK) can obtain the method name (setTaskPosition) of method 2, the split-screen position (targetPosition), and the task ID of the Activity corresponding to page B. Moreover, the third-party interface layer (EasyGoSDK) can also obtain (such as actively querying) the package name of the application.

[0588] The third-party interface layer (EasyGoSDK) sends the method name (setTaskPosition) of method 2, the split-screen position (targetPosition), the task ID of the Activity corresponding to page B, and the package name of the application to the parallel window manager (HwMagicWindowManager) of the electronic device.

[0589] Among them, the package name of the application, the split-screen position (targetPosition), and the taskID of the Activity corresponding to page B can be passed using the parameter params7.

[0590] Based on Figure 2b the structure shown, using the policy module, configuration module, data management module, background layer drawing module, and animation effect module, the parallel window manager (HwMagicWindowManager) can implement the following process:

[0591] The parallel window manager (HwMagicWindowManager) can determine whether the method name (setTaskPosition) of method 2 and the content of params7 are empty. When the method name (setTaskPosition) of method 2 and the content of params7 are not empty, the parallel window manager (HwMagicWindowManager) can perform the following three steps:

[0592] Step 22-1: Based on the package name (packagename) of the application, the parallel window manager (HwMagicWindowManager) can determine whether the task stack of the Activity corresponding to page a1 is in the non-split-screen mode (that is, whether the a1 page corresponding to the Activity is not in the split-screen display state).

[0593] Among them, the parallel window manager (HwMagicWindowManager) can determine whether the number of task stacks corresponding to the page currently displayed on the electronic device is one, to determine whether the task stack of the Activity corresponding to page a1 is in the non-split-screen mode. Thus, when it is determined that the number of task stacks corresponding to the page currently displayed on the electronic device is one, the parallel window manager (HwMagicWindowManager) can determine that the task stack of the Activity corresponding to page A is in the non-split-screen mode.

[0594] Alternatively, the parallel window manager (HwMagicWindowManager) can obtain an indication flag from the electronic device, where the indication flag indicates whether the task stack of the Activity corresponding to page a1 is in the non-split-screen mode. Thus, when the indication flag indicates that the task stack corresponding to the Activity is in the non-split-screen mode, the parallel window manager (HwMagicWindowManager) can determine that the task stack of the Activity corresponding to page a1 is in the non-split-screen mode.

[0595] It should be noted that this application is not limited to the foregoing two implementation manners to determine whether the task stack of the Activity corresponding to the a1 page is in a non-split screen mode.

[0596] Step 22-2: Based on the package name of the application, the HwMagicWindowManager can determine whether the application corresponding to the package name supports the in-application split screen function. Furthermore, when the electronic device determines that the application corresponding to the package name supports the in-application split screen function, it can ensure that the application can support the split screen display of multiple pages of the application.

[0597] For the specific implementation manner of step 22-2, reference can be made to the description of step 21-2, which will not be elaborated here.

[0598] Step 21-3: Based on the split screen position (targetPosition), the HwMagicWindowManager can determine whether the moving position of the B page meets the preset requirements for split screen display (for example, the secondary screen (such as the right split screen) or the full screen, such as determining whether the value of targetPosition is 1 or 2). Furthermore, when the moving position of the B page meets the preset requirements for split screen display, the electronic device can determine that the split screen display of the B page can be achieved.

[0599] For the specific implementation manner of step 22-3, reference can be made to the description of step 21-3, which will not be elaborated here.

[0600] In addition, the execution order of step 22-1, step 22-2, and step 22-3 is not sequential. They can be executed sequentially or simultaneously. This application does not make any limitations in this regard.

[0601] When the judgment results of step 22-1, step 22-2, and step 22-3 are all yes, based on the package name of the application, the HwMagicWindowManager can determine the taskID of the Activity corresponding to the a1 page.

[0602] Based on the split screen position (targetPosition) and the taskID of the Activity corresponding to the B page, the HwMagicWindowManager can determine split screen parameters such as the split screen boundary (bounds) and the moving animation effect of the B page, or the split screen parameters such as the split screen boundary (bounds) and the moving animation effect of the a1 page and the B page.

[0603] The parallel window manager (HwMagicWindowManager) simultaneously displays two independent tasks on the left and right split screens of the display screen based on the task ID of the Activity corresponding to page a1, the task ID of the Activity corresponding to page B, and the split screen parameters of page B. That is, as shown in (3) of Figure 5A , page a1 is displayed on the left split screen of the electronic device and page B is displayed on the right split screen of the electronic device. Figure 5A The left split screen of the electronic device shows page a1 and the right split screen shows page B as shown in (3) of Figure 5A .

[0604] Based on the foregoing description, combined with Figure 5D , the implementation process of split screen display of page a1 and page B on the electronic device is specifically described. Figure 5D Based on the foregoing description, in combination with Figure 5D , the implementation process of split screen display of page a1 and page B on the electronic device is specifically elaborated.

[0605] As Figure 5D shown, the specific implementation process of the application page display method of this application may include the following steps:

[0606] S41. The electronic device displays page a1.

[0607] S42'. When the electronic device receives the user operation 701 on page a1, a new Task (i.e., a task stack different from the task stack corresponding to page a1) is established, and the Activity corresponding to page B is started in the new Task, and a message 11 is sent to the application. Message 11 is used to identify operation 701.

[0608] S43'. In response to message 11, the application obtains the method name (referred to as setTaskPosition) of method 2, the split screen position (targetPosition) of page B, and the task ID of the Activity corresponding to page B.

[0609] S44. The application sends message 12 to the third-party interface layer (EasyGoSDK). Message 12 carries the method name (referred to as setTaskPosition) of method 2, the split screen position (targetPosition) of page B, and the task ID of the Activity corresponding to page B.

[0610] S45. The third-party interface layer (EasyGoSDK) sends the method name (referred to as setTaskPosition) of method 2, the split screen position (targetPosition) of page B, the task ID of the Activity corresponding to page B, and the package name of the application to the parallel window manager (HwMagicWindowManager).

[0611] S461', the parallel window manager (HwMagicWindowManager) can determine whether the task stack of the task ID of the Activity corresponding to page a1 is in a non-split screen mode (that is, whether the a1 page corresponding to the Activity is not in a split screen display state) based on the package name (packagename) of the application.

[0612] Step S461 is an optional step.

[0613] S462, the parallel window manager (HwMagicWindowManager) determines whether the application corresponding to the package name (packagename) of the application supports the in-application split screen function.

[0614] S463, the parallel window manager (HwMagicWindowManager) determines whether the moving position of page B meets the preset requirements for split screen display based on the split screen position (targetPosition) of page B.

[0615] S47, when the judgment results of S461, S462, and S463 are all yes, the parallel window manager (HwMagicWindowManager) determines the task ID of the Activity corresponding to page a1 based on the package name (package name) of the application, and determines the split screen parameters of page B based on the split screen position (targetPosition) and the task ID of the Activity corresponding to page B.

[0616] In addition, when the judgment result of any one of the steps S461, S462, and S463 by the parallel window manager (HwMagicWindowManager) is no, page a1 continues to be displayed.

[0617] S48, the parallel window manager (HwMagicWindowManager) simultaneously displays page a1 and page B based on the task ID of the Activity corresponding to page a1, the task ID of the Activity corresponding to page B, and the split screen parameters of page B.

[0618] It should be noted that Figure 5D For the specific implementation process shown exemplarily, reference can be made to the foregoing content and will not be elaborated here. And Figure 5C Compared with Figure 5D The difference is: Figure 5C Steps S421, S422 - S43 of Figure 5C and steps S42' - S43' of Figure 5C and step S461 of Figure 5DStep S461', and the remaining steps are the same.

[0619] In addition, Figure 5C and Figure 5D the operation 701 in is used to identify different meanings, and can be operations of the same type or different types. Figure 5C The operation 701 in is used to identify the jump from displaying the a1 page in a task stack to displaying the B page in another task stack. Figure 5D The operation 701 in is used to identify the jump from displaying the a1 page in a task stack to simultaneously displaying the a1 page in a task stack and the B page in another task stack.

[0620] In some other embodiments, after the electronic device detects the operation 101 that triggers the control B in the a1 page indicated by the user, if the launch mode of the Activity corresponding to the B page is not set to the singleInstance mode, the B page is displayed, and the Activity corresponding to the a1 page and the Activity corresponding to the B page are both in the same task.

[0621] After the Activity corresponding to the B page is launched, the electronic device can default to display the B page (i.e., full-screen display as shown in (2) of or display in a partial display area). And, the B page includes a split-screen / full-screen control, which is used to indicate that the user can trigger the split-screen / full-screen control from the B page, and the split-screen / full-screen control is used for split-screen display or full-screen display of the B page. Figure 5A After the electronic device detects the operation 702 that triggers the split-screen / full-screen control in the B page indicated by the user, it can send a message 13 to the application. The message 13 is used to identify the foregoing operation 702, so that the application can obtain the taskID of the Activity corresponding to the a1 page from the software system of the electronic device, determine the split-screen position of the B page based on the foregoing operation 702, and determine the method name (referred to as setTaskPosition) of the method (method) 2 for split-screen display within the application based on the foregoing operation 702. The method 2 is used to indicate the split-screen display of the a1 page and the B page. Among them, the present application does not limit the representation method of the message 13. For example, the message 13 may include the reporting point coordinates of the foregoing operation 702.

[0622] In summary, the software system of the electronic device sends the foregoing operation 702 to the application, so that the application can obtain the taskID of the Activity corresponding to the a1 page, the split-screen position of the B page, and the method name (referred to as setTaskPosition) of the method (method) 2 for split-screen display within the application.

[0623]

[0624] ​Among them, for the split-screen positions mentioned above, refer to the description of the split-screen positions in Scenario 1, and details are not elaborated here.

[0625] Based on the description of the foregoing embodiments, the application can call the invoke interface in the third-party interface layer (EasyGoSDK) of the electronic device, and transmit Message 14. Message 14 carries the method name (setTaskPosition) of Method 2, the split-screen position (targetPosition), and the task ID of the Activity corresponding to Page a1.

[0626] Among them, the present application does not limit the representation method of Message 14. For example, the split-screen position (targetPosition) and the task ID of the Activity corresponding to Page a1 can be transmitted using parameter params6. The definition of the invoke interface can be referred to the description in Scenario 1, and details are not elaborated here. It should be noted that the task ID of the Activity corresponding to Page a1 can be replaced by the ID of Page a1. The present application does not limit this, as long as the identifier used to represent Page a1 is transmitted. Among them, the present application does not limit this identifier.

[0627] In summary, the third-party interface layer (EasyGoSDK) can obtain the method name (setTaskPosition) of Method 2, the split-screen position (targetPosition), and the task ID of the Activity corresponding to Page a1. Moreover, the third-party interface layer (EasyGoSDK) can also obtain (such as actively querying) the package name of the application.

[0628] The third-party interface layer (EasyGoSDK) sends the method name (setTaskPosition) of Method 2, the split-screen position (targetPosition), the task ID of the Activity corresponding to Page a1, and the package name of the application to the parallel window manager (HwMagicWindowManager) of the electronic device.

[0629] Among them, the package name of the application, the split-screen position (targetPosition), and the task ID of the Activity corresponding to Page a1 can be transmitted using parameter params7.

[0630] Based on Figure 2bFor the structure shown, by using a policy module, a configuration module, a data management module, a background layer drawing module, and an animation effect module, the parallel window manager (HwMagicWindowManager) can implement the following process:

[0631] The parallel window manager (HwMagicWindowManager) can determine whether the method name (setTaskPosition) of method 2 and the content of params7 are empty. When the method name (setTaskPosition) of method 2 and the content of params7 are not empty, the parallel window manager (HwMagicWindowManager) can perform the following three steps:

[0632] Step 23-1: The parallel window manager (HwMagicWindowManager) can, based on the taskID of the Activity corresponding to page a1, determine whether the Activity corresponding to this taskID is the current task stack. Furthermore, when the Activity corresponding to this taskID is the current task stack, the electronic device can ensure that there is a current task stack.

[0633] Among them, step 23-1 is an optional step.

[0634] Step 23-2: The parallel window manager (HwMagicWindowManager), based on the package name (packagename) of this application, can determine whether the application corresponding to this package name supports the in-app split-screen function. Furthermore, when the electronic device determines that the application corresponding to this package name supports the in-app split-screen function, it can ensure that this application can support the split-screen display of multiple pages of this application.

[0635] Among them, the specific implementation method of step 23-2 can refer to the description of step 21-2, and will not be elaborated here.

[0636] Step 23-3: The parallel window manager (HwMagicWindowManager), based on the split-screen position (targetPosition), can determine whether the moving position of page B meets the preset requirements for split-screen display (for example, the secondary screen (such as the right split-screen) or the full screen, such as determining whether the value of targetPosition is 1 or 2). Furthermore, when the moving position of page B meets the preset requirements for split-screen display, the electronic device can determine that the split-screen display of page B can be achieved.

[0637] Among them, the specific implementation method of step 23-3 can refer to the description of step 21-3, and will not be elaborated here.

[0638] In addition, the execution order of step 23-1, step 23-2, and step 23-3 is not sequential. They can be executed sequentially or simultaneously, and the present application does not limit this.

[0639] When the judgment results of step 23-1, step 23-2, and step 23-3 are all yes, the parallel window manager (HwMagicWindowManager) can create a new Task (i.e., a task stack different from the task stack corresponding to the a1 page), and start the Activity corresponding to the B page in this new Task.

[0640] Among them, the aforementioned new Task and the Task corresponding to the a1 page are different Tasks, which can be understood as the Activity corresponding to the B page entering a task different from the Activity corresponding to the a1 page.

[0641] Based on the split-screen position (targetPosition) and the task ID of the Activity corresponding to the B page (i.e., the ID of the new Task), the parallel window manager (HwMagicWindowManager) can determine split-screen parameters such as the split-screen boundary (bounds) and movement animation effects of the B page, or the split-screen parameters such as the split-screen boundary (bounds) and movement animation effects of the a1 page and the B page.

[0642] Based on the task ID of the Activity corresponding to the a1 page, the task ID of the Activity corresponding to the B page, and the split-screen parameters of the B page, the parallel window manager (HwMagicWindowManager) simultaneously displays the two independent tasks on the left and right split-screens of the display screen, that is, Figure 5A as shown in (3) of the figure, the a1 page is displayed on the left split-screen of the electronic device and the B page is displayed on the right split-screen of the electronic device.

[0643] Based on the foregoing description, combined with Figure 5E the implementation process of split-screen display of the a1 page and the B page on the electronic device will be specifically described.

[0644] As Figure 5E shown, the specific implementation process of the application page display method of the present application may include the following steps:

[0645] S61. The electronic device displays the a1 page.

[0646] S621. When the electronic device receives the user operation 701 on the a1 page, it displays the B page. Among them, the task stack corresponding to the B page and the task stack corresponding to the a1 page are the same task stack, and the Activity corresponding to the B page is started in this task stack to implement the display of the B page.

[0647] When the electronic device receives the user operation 702 on the B page, it sends a message 13 to the application, and the message 13 is used to identify the operation 702.

[0648] S63. In response to the message 13, the application obtains the method name (referred to as setTaskPosition) of method 2, the split-screen position (targetPosition) of the B page, and the task ID of the Activity corresponding to the a1 page.

[0649] S64. The application sends a message 14 to the third-party interface layer (EasyGoSDK), and the message 14 carries the method name (referred to as setTaskPosition) of method 2, the split-screen position (targetPosition) of the B page, and the task ID of the Activity corresponding to the a1 page.

[0650] S65. The third-party interface layer (EasyGoSDK) sends the method name (referred to as setTaskPosition) of method 2, the split-screen position (targetPosition) of the B page, the task ID of the Activity corresponding to the a1 page, and the package name of the application to the parallel window manager (HwMagicWindowManager).

[0651] S661. The parallel window manager (HwMagicWindowManager) determines whether the Activity corresponding to the task ID of the Activity corresponding to the a1 page is the current task stack.

[0652] Step S461 is an optional step.

[0653] S662. The parallel window manager (HwMagicWindowManager) determines whether the application corresponding to the package name (packagename) of the application supports the in-app split-screen function.

[0654] S663. The parallel window manager (HwMagicWindowManager) determines whether the moving position of the B page meets the preset requirements for split-screen display based on the split-screen position (targetPosition) of the B page.

[0655] When the judgment results of S661, S662, and S663 in the parallel window manager (HwMagicWindowManager) are all yes, a new Task is created (i.e., a task stack different from the task stack corresponding to the a1 page), and the Activity corresponding to page B is started in this new Task. Then, based on the split-screen position (targetPosition) and the task ID of the Activity corresponding to page B, the split-screen parameters of page B are determined.

[0656] In addition, when the judgment result of any one of the steps S661, S662, and S663 in the parallel window manager (HwMagicWindowManager) is no, page B continues to be displayed.

[0657] S68: The parallel window manager (HwMagicWindowManager) simultaneously displays page a1 and page B based on the task ID of the Activity corresponding to page a1, the task ID of the Activity corresponding to page B, and the split-screen parameters of page B.

[0658] It should be noted that Figure 5E For the specific implementation process shown by way of example, reference can be made to the foregoing content, and details will not be elaborated here. And Figure 5E different from Figure 5C is that: Figure 5E the timing of creating a new task stack in step S67 of Figure 5C and the timing of creating a new task stack in S421 of Figure 5E and the task ID of the Activity corresponding to page a1 transmitted in Figure 5C and the task ID of the Activity corresponding to page B in

[0659] In addition, Figure 5C and Figure 5E the operation 701 in Figure 5C is used to identify different meanings and can be operations of the same type or different types. Figure 5E The operation 701 in

[0660] In some other embodiments, after the electronic device detects an operation 701 that triggers a control B on page a1 indicated by the user, if the launch mode of the Activity corresponding to page B is not set to the singleInstance mode, the electronic device may send a message 15 to the application. The message 15 is used to identify the foregoing operation 701. In response to the foregoing operation 701, the application may obtain the ID of the task (abbreviated as taskID) of the Activity corresponding to page a1 from the software system of the electronic device, determine the split-screen position of page B based on the foregoing operation 701, and determine the method name (referred to as setTaskPosition) of method 2 for split-screen display within the application based on the foregoing operation 701. Method 2 is used to indicate that page a1 and page B are displayed in a split screen. Herein, the present application does not limit the representation manner of the message 15. For example, the message 15 may be the reporting point coordinates of the foregoing operation 701.

[0661] Among them, the split-screen position mentioned above may refer to the description of the split-screen position mentioned above, and will not be elaborated herein.

[0662] In summary, the software system of the electronic device notifies the application of the foregoing operation 701, so that the application can obtain the taskID of the Activity corresponding to page a1, the split-screen position of page B, and the method name (referred to as setTaskPosition) of method 2 for split-screen display within the application.

[0663] It should be noted that for the execution steps of the electronic device to establish a new Task in response to the operation 701, the software system of the electronic device sends the execution steps of the foregoing operation 701, and there is no sequence in time, and they may be executed simultaneously or sequentially. The present application does not limit this.

[0664] Based on the description of the foregoing embodiments, the application may call the invoke interface in the third-party interface layer (EasyGoSDK) of the electronic device, and transmit a message 16. The message 16 carries the method name (setTaskPosition) of method 2, the split-screen position (targetPosition), and the taskID of the Activity corresponding to page a1.

[0665] Among them, this application does not limit the representation method of message 16. For example, the split-screen position (targetPosition) and the taskID of the Activity corresponding to page a1 can be passed using parameter params6. The definition of the invoke interface can be referred to the description in Scenario 1 and will not be elaborated here. It should be noted that the taskID of the Activity corresponding to page a1 can be replaced by the ID of page a1. This application does not limit this, and only the identifier used to represent page a1 needs to be transmitted. Among them, this application does not limit this identifier.

[0666] In summary, the third-party interface layer (EasyGoSDK) can obtain the method name of Method 2 (setTaskPosition), the split-screen position (targetPosition), and the taskID of the Activity corresponding to page a1. And the third-party interface layer (EasyGoSDK) can also obtain (such as actively querying) the package name of this application.

[0667] The third-party interface layer (EasyGoSDK) sends the method name of Method 2 (setTaskPosition), the split-screen position (targetPosition), the taskID of the Activity corresponding to page a1, and the package name of this application to the parallel window manager (HwMagicWindowManager) of the electronic device.

[0668] Among them, the package name of this application (package name), the split-screen position (targetPosition), and the taskID of the Activity corresponding to page a1 can be passed using parameter params7.

[0669] Based on Figure 2b the shown structure, using the policy module, configuration module, data management module, background layer drawing module, and animation effect module, the parallel window manager (HwMagicWindowManager) can implement the following process:

[0670] The parallel window manager (HwMagicWindowManager) can determine whether the method name of Method 2 (setTaskPosition) and the content of params7 received are empty. When the method name of Method 2 (setTaskPosition) and the content of params7 are not empty, the parallel window manager (HwMagicWindowManager) can perform the following three steps:

[0671] Step 24-1: Based on the task ID of the Activity corresponding to page a1, the Parallel Window Manager (HwMagicWindowManager) can determine whether the task stack corresponding to this task ID is in a non-split-screen mode (i.e., whether the a1 page corresponding to this Activity is not in a split-screen display state).

[0672] Among them, for the specific implementation method of Step 24-1, refer to the description of Step 22-1, which will not be elaborated here.

[0673] Step 24-2: Based on the package name (packagename) of this application, the Parallel Window Manager (HwMagicWindowManager) can determine whether the application corresponding to this package name supports the in-application split-screen function. Furthermore, when the electronic device determines that the application corresponding to this package name supports the in-application split-screen function, it can ensure that this application can support the split-screen display of multiple pages of this application.

[0674] Among them, for the specific implementation method of Step 24-2, refer to the description of Step 23-2, which will not be elaborated here.

[0675] Step 24-3: Based on the split-screen position (targetPosition), the Parallel Window Manager (HwMagicWindowManager) can determine whether the moving position of page B meets the preset requirements for split-screen display (for example, the secondary screen (such as the right split-screen) or the full screen, such as determining whether the value of targetPosition is 1 or 2). Furthermore, when the moving position of page B meets the preset requirements for split-screen display, the electronic device can determine that the split-screen display of page B can be achieved.

[0676] Among them, for the specific implementation method of Step 24-3, refer to the description of Step 23-3, which will not be elaborated here.

[0677] In addition, the execution order of Step 24-1, Step 24-2, and Step 24-3 is not in sequence. They can be executed sequentially or simultaneously. This application does not make any restrictions on this.

[0678] When the judgment results of Step 24-1, Step 24-2, and Step 24-3 are all yes, the Parallel Window Manager (HwMagicWindowManager) can create a new Task (i.e., a task stack different from the task stack corresponding to page a1), and start the Activity corresponding to page B in a new Task.

[0679] Among them, the aforementioned new Task and the Task corresponding to page a1 are different Tasks. It can be understood that the Activity corresponding to page B enters a task different from the Activity corresponding to page a1.

[0680] The parallel window manager (HwMagicWindowManager) can determine split-screen parameters of page B, such as split-screen boundaries (bounds) and moving effects, based on the split-screen position (targetPosition) and the task ID of the Activity corresponding to page B (i.e., the ID of the new Task), or the split-screen parameters of page a1 and page B, such as split-screen boundaries (bounds) and moving effects.

[0681] The parallel window manager (HwMagicWindowManager) displays two independent tasks simultaneously on the left and right split-screens of the display screen based on the task ID of the Activity corresponding to page a1, the task ID of the Activity corresponding to page B, and the split-screen parameters of page B, that is, Figure 5A as shown in (3) of the figure, page a1 is displayed on the left split-screen of the electronic device and page B is displayed on the right split-screen of the electronic device.

[0682] Based on the foregoing description, combined with Figure 5F this, the implementation process of split-screen display of page a1 and page B on the electronic device is specifically described.

[0683] As Figure 5F shown, the specific implementation process of the application page display method of this application may include the following steps:

[0684] S61. The electronic device displays page a1.

[0685] S62'. When the electronic device receives the user's operation 701 on page a1, it sends message 15 to the application, and message 15 is used to identify operation 701.

[0686] S63'. In response to message 15, the application obtains the method name (referred to as setTaskPosition) of method 2, the split-screen position (targetPosition) of page B, and the task ID of the Activity corresponding to page a1.

[0687] S64. The application sends message 16 to the third-party interface layer (EasyGoSDK), and message 16 carries the method name (referred to as setTaskPosition) of method 2, the split-screen position (targetPosition) of page B, and the task ID of the Activity corresponding to page a1.

[0688] S65. The third - party interface layer (EasyGoSDK) sends the method name of method 2 (called setTaskPosition), the split - screen position of page B (targetPosition), the task ID of the Activity corresponding to page a1, and the package name of this application to the parallel window manager (HwMagicWindowManager).

[0689] S661'. The parallel window manager (HwMagicWindowManager) determines whether the task stack corresponding to the task ID of the Activity corresponding to page a1 is in a non - split - screen mode (that is, whether the A page corresponding to this Activity is not in a split - screen display state).

[0690] S662. The parallel window manager (HwMagicWindowManager) determines whether the application corresponding to the package name of this application supports the in - app split - screen function.

[0691] S663. The parallel window manager (HwMagicWindowManager) determines whether the moving position of page B meets the preset requirements for split - screen display based on the split - screen position of page B (targetPosition).

[0692] S67. When the judgment results of S661, S662, and S663 are all yes, the parallel window manager (HwMagicWindowManager) creates a new Task (that is, a task stack different from the task stack corresponding to page a1), starts the Activity corresponding to page B in this new Task, and determines the split - screen parameters of page B based on the split - screen position (targetPosition) and the task ID of the Activity corresponding to page B.

[0693] In addition, when the judgment result of any one of the steps in S661, S662, and S663 is no, the parallel window manager (HwMagicWindowManager) continues to display page B.

[0694] S68. The parallel window manager (HwMagicWindowManager) simultaneously displays page a1 and page B based on the task ID of the Activity corresponding to page a1, the task ID of the Activity corresponding to page B, and the split - screen parameters of page B.

[0695] It should be noted that Figure 5FThe specific implementation process shown by way of example can be referred to the foregoing content and will not be elaborated here. And, Figure 5E different from Figure 5F is that: Figure 5E Steps S621, S562 - S63 of Figure 5F and steps S62'-S63' of Figure 5E Steps S661 of Figure 5F and steps S661' of

[0696] are the same, and the remaining steps are all the same. Figure 6E different from Figure 6C is that: Figure 6E The timing of establishing a new task stack in step S67 of Figure 6C and the timing of establishing a new task stack in S421 of Figure 6E and the taskID of the Activity corresponding to page a1 transmitted Figure 6C and the taskID of the Activity corresponding to page B of

[0697] are different. The remaining steps are similar. Figure 6C and Figure 6E Operation 701 in is used to identify different meanings and can be operations of the same type or different types. Figure 6C Operation 701 in is used to identify the jump from displaying page a1 in a task stack to displaying page B in another task stack. Figure 6E Operation 701 in is used to identify the jump from displaying page a1 in a task stack to displaying page B in the same task stack.

[0698] 2. Exit the display of page B (corresponding to step S221 or step S222 as shown in Figure 5B )

[0699] As shown in (2) and (3) of Figure 5B , page B may further include a return control 5, which is used to indicate that the user can trigger the return control 5 from page B, and the return control 5 is used to exit the display of page B.

[0700] After the electronic device detects the operation 801 of the user indicating to trigger the return control 5 in page B, it can exit the Activity corresponding to page B, so that the electronic device can return from the user interface shown in (2) or (3) of Figure 5B exemplarily shown to the user interface shown in (1) of Figure 5B exemplarily shown.

[0701] 3. Open a new page from the a1 page displayed in the left split screen, and the new page replaces the a1 page displayed in the left split screen (corresponding to step S231 or step S232 as shown in Figure 5A )

[0702] 31. Open the C2 page from the a1 page displayed in the left split screen. The C2 page replaces the a1 page displayed in the left split screen (corresponding to step S231 as shown in Figure 5A ).

[0703] When the electronic device detects an operation 901 that triggers the control C2 in the a1 page indicated by the user, it can send the parameters policy4 and params8 to the parallel window manager (HwMagicWindowManager).

[0704] Among them, due to the operation 901 performed by the user on the a1 page, and the a1 page is displayed in the left split screen, therefore, the parameter policy4 is used to identify the policy adopted when opening the C2 page from the a1 page displayed in the left split screen. The parameter policy4 can be represented in forms such as numbers, strings, letters, etc. params8 can include, but are not limited to: the token of the Activity corresponding to the a1 page (i.e., the focus Activity), the token of the Activity corresponding to the C2 page, and the configuration parameters of the intent used to start the Activity corresponding to the C2 page.

[0705] Among them, the token of the Activity corresponding to the a1 page can identify the Activity corresponding to the a1 page, and the token of the Activity corresponding to the C2 page can identify the Activity corresponding to the C2 page. The configuration parameters of the intent used to start the Activity corresponding to the C2 page can start the Activity corresponding to the C2 page.

[0706] Based on the token of the Activity corresponding to the a1 page, the parallel window manager (HwMagicWindowManager) can determine whether the task stack corresponding to this Activity is in the split screen mode (i.e., whether the a1 page corresponding to this Activity is in the split screen display state).

[0707] Among them, the parallel window manager (HwMagicWindowManager) can determine the task stacks corresponding to the pages currently displayed on the electronic device (i.e., the task stack corresponding to the a1 page and the task stack corresponding to the B page), and determine whether the task stack corresponding to this Activity is in split-screen mode by whether the task stack corresponding to the a1 page and the task stack corresponding to the B page are different task stacks. Thus, when it is determined that the task stack corresponding to the a1 page and the task stack corresponding to the B page are different task stacks, the parallel window manager (HwMagicWindowManager) can determine that the task stack corresponding to this Activity is in split-screen mode.

[0708] Alternatively, the parallel window manager (HwMagicWindowManager) can obtain an indication flag from the electronic device, where the indication flag indicates whether the task stack corresponding to this Activity is in split-screen mode. Thus, when the indication flag indicates that the task stack corresponding to this Activity is in split-screen mode, the parallel window manager (HwMagicWindowManager) can determine that the task stack corresponding to this Activity is in split-screen mode.

[0709] It should be noted that this application is not limited to the foregoing two implementation manners to determine whether the task stack corresponding to this Activity is in split-screen mode.

[0710] When the parallel window manager (HwMagicWindowManager) determines that the task stack corresponding to this Activity is in split-screen mode, based on the token of the Activity corresponding to the C2 page, it starts the configuration parameters of the intent used to start the Activity corresponding to the C2 page, so that the Activity corresponding to the C2 page is started. Furthermore, the parallel window manager (HwMagicWindowManager) can determine split-screen parameters such as the split-screen boundary (bounds) and moving animation effects of the C2 page, so that the C2 page replaces the a1 page and is displayed in the left split screen of the electronic device, as Figure 5A shown in (41) of

[0711] Among them, the Activity corresponding to the C2 page can be set to any one of the four launch modes of the Activity. If the launch mode of the Activity corresponding to the C2 page is set to the singleInstance mode, the launch method of the C2 page is newtask launch, then the split-screen boundary (bounds) of the C2 page can limit the window size of the C2 page.

[0712] 32. Open the B page from the a1 page displayed in the left split screen, and the B page replaces the a1 page displayed in the left split screen (corresponding to step S232 as shown in Figure 5A ).

[0713] After the electronic device detects the operation 902 of the user instructing to trigger the control B in the a1 page, it can send the parameter policy5 and params9 to the parallel window manager (HwMagicWindowManager).

[0714] Among them, due to the operation 902 performed by the user on the a1 page, and the a1 page is displayed in the left split screen, therefore, the parameter policy5 is used to identify the policy adopted when opening the B page from the a1 page displayed in the left split screen, and the parameter policy5 can be represented in forms such as numbers, strings, letters, etc. params9 can include but are not limited to: the token of the Activity corresponding to the a1 page (i.e., the focus Activity), the token of the Activity corresponding to the B page, and the configuration parameters of the intent used to start the Activity corresponding to the B page.

[0715] Among them, the token of the Activity corresponding to the a1 page can identify the Activity corresponding to the a1 page, and the token of the Activity corresponding to the B page can identify the Activity corresponding to the B page. The configuration parameters of the intent used to start the Activity corresponding to the B page can start the Activity corresponding to the B page.

[0716] Based on the token of the Activity corresponding to the a1 page, the parallel window manager (HwMagicWindowManager) can determine whether the task stack corresponding to this Activity is in the split screen mode (i.e., whether the a1 page corresponding to this Activity is in the split screen display state).

[0717] Among them, the parallel window manager (HwMagicWindowManager) can determine the task stacks corresponding to the pages currently displayed on the electronic device (i.e., the task stack corresponding to the a1 page and the task stack corresponding to the B page), and judge whether the task stack corresponding to this Activity is in the split screen mode by whether the task stack corresponding to the a1 page and the task stack corresponding to the B page are different task stacks. Thus, when it is determined that the task stack corresponding to the a1 page and the task stack corresponding to the B page are different task stacks, the parallel window manager (HwMagicWindowManager) can determine that the task stack corresponding to this Activity is in the split screen mode.

[0718] Alternatively, the parallel window manager (HwMagicWindowManager) can obtain an indication identifier from the electronic device, where the indication identifier indicates whether the task stack corresponding to the Activity is in split-screen mode. Thus, when the indication identifier indicates that the task stack corresponding to the Activity is in split-screen mode, the parallel window manager (HwMagicWindowManager) can determine that the task stack corresponding to the Activity is in split-screen mode.

[0719] It should be noted that the present application is not limited to the foregoing two implementation manners to determine whether the task stack corresponding to the Activity is in split-screen mode.

[0720] When the parallel window manager (HwMagicWindowManager) determines that the task stack corresponding to the Activity is in split-screen mode, since the launch mode of the Activity corresponding to the B page is set to the singleInstance mode, the electronic device can create a new Task (i.e., a task stack different from both the task stack corresponding to the a1 page and the task stack corresponding to the B page displayed in the right split screen), and based on the token of the Activity corresponding to the B page, start the configuration parameters of the intent used to start the Activity corresponding to the B page, so that the Activity corresponding to the B page is started. Furthermore, the parallel window manager (HwMagicWindowManager) can determine split-screen parameters such as the split-screen boundary (bounds) and moving animation effects of the B page, so that the B page replaces the a1 page and is displayed in the left split screen of the electronic device, as Figure 5A shown in (42).

[0721] Among them, Figure 5A The specific implementation manner of step S232 shown is similar to Figure 5A step S231 shown.

[0722] 41. The C2 page displayed in the left split screen exits the display (corresponding to step S241 as shown in Figure 5B shown)

[0723] As Figure 5B shown in (41), the C2 page displayed in the left split screen may include a return control 6, which is used to indicate that the user can trigger the return control 6 from the C2 page, and the return control 6 is used to exit the display of the C2 page.

[0724] After the electronic device detects the operation 1001 of the user indicating to trigger the return control 6 in the C2 page, it can exit the Activity corresponding to the C2 page, so that the electronic device changes from displaying as Figure 5BThe user interface shown in the (41) exemplary returns to display as Figure 5B the user interface shown in the (3) exemplary.

[0725] 42. Exit the display of page B in the left split screen (corresponding to Figure 5B the step S242 shown as

[0726] As Figure 5B shown in (42), page B in the left split screen may further include a return control 7, which is used to indicate that the user can trigger the return control 7 from page B, and the return control 7 is used to exit the display of page B.

[0727] After the electronic device detects the operation 1002 of the user indicating to trigger the return control 7 in page B, it can exit the Activity corresponding to page B in the left split screen, so that the electronic device returns from the user interface shown in the (42) exemplary as Figure 5B to the user interface shown in the (3) exemplary as Figure 5B shown.

[0728] 43. Exit the display of page B in the right split screen (corresponding to Figure 5B the step S261 and step S262 shown as

[0729] As Figure 5B shown in (41) and (42), page B in the right split screen may further include a return control 5, which is used to indicate that the user can trigger the return control 5 from page B, and the return control 5 is used to exit the display of page B.

[0730] After the electronic device detects the operation 1003 of the user indicating to trigger the return control 5 in page B, it can exit the Activity corresponding to page B in the right split screen, so that the electronic device returns from the user interface shown in the (41) exemplary as Figure 5B to the user interface shown in the (1) or (2) exemplary as Figure 5B shown, or, so that the electronic device returns from the user interface shown in the (42) exemplary as Figure 5B to the user interface shown in the (1) or (2) exemplary as Figure 5B shown.

[0731] 5. Open a new page (i.e., page D) from page B in the right split screen, and page D replaces page B in the right split screen (corresponding to Figure 5A the step S25 shown as

[0732] After detecting the operation 1101 of the control D in page B indicated by the user, the electronic device can send the parameters policy6 and params10 to the parallel window manager (HwMagicWindowManager).

[0733] Among them, due to the operation 1101 performed by the user on page B, and page B is displayed in the right split screen, therefore, the parameter policy6 is used to identify the policy adopted when opening page D from page B displayed in the right split screen, and the parameter policy6 can be represented in forms such as numbers, strings, letters, etc. params10 can include but are not limited to: the token of the Activity corresponding to page B (i.e., the focus Activity), the token of the Activity corresponding to page D, and the configuration parameters of the intent used to start the Activity corresponding to page D.

[0734] Among them, the token of the Activity corresponding to page B is used to identify the Activity corresponding to page B. The token of the Activity corresponding to page D is used to identify the Activity corresponding to page D. The configuration parameters of the intent used to start the Activity corresponding to page D are used to start the Activity corresponding to page D.

[0735] Based on the token of the Activity corresponding to page B, the parallel window manager (HwMagicWindowManager) can determine whether the task stack corresponding to this Activity is in the split screen mode (i.e., whether the page B corresponding to this Activity is in the split screen display state).

[0736] Among them, the parallel window manager (HwMagicWindowManager) can determine the task stacks corresponding to the pages currently displayed on the electronic device (i.e., the task stack corresponding to page a1 and the task stack corresponding to page B), and judge whether the task stack corresponding to this Activity is in the split screen mode by whether the task stack corresponding to page a1 and the task stack corresponding to page B are different task stacks. Thus, when it is determined that the task stack corresponding to page a1 and the task stack corresponding to page B are different task stacks, the parallel window manager (HwMagicWindowManager) can determine that the task stack corresponding to this Activity is in the split screen mode.

[0737] Alternatively, the parallel window manager (HwMagicWindowManager) can obtain an indication identifier from the electronic device, where the indication identifier indicates whether the task stack corresponding to the Activity is in split-screen mode. Thus, when the indication identifier indicates that the task stack corresponding to the Activity is in split-screen mode, the parallel window manager (HwMagicWindowManager) can determine that the task stack corresponding to the Activity is in split-screen mode.

[0738] It should be noted that this application is not limited to the foregoing two implementation manners to determine whether the task stack corresponding to the Activity is in split-screen mode.

[0739] When the parallel window manager (HwMagicWindowManager) determines that the task stack corresponding to the Activity is in split-screen mode, based on the token of the Activity corresponding to page D, it starts the configuration parameters of the intent used to start the Activity corresponding to page D, so that the Activity corresponding to page D is started. Furthermore, the parallel window manager (HwMagicWindowManager) can determine split-screen parameters such as the split-screen boundary (bounds) and movement animation effects of page D, so that page D replaces page B and is displayed in the right split screen of the electronic device, as Figure 5A shown in (5) of. If not, return.

[0740] Among them, the Activity corresponding to page D can be set to any one of the four launch modes of the Activity. If the launch mode of the Activity corresponding to page D is set to the singleInstance mode, the launch method of page D is newtask launch, then the split-screen boundary (bounds) of page D can limit the window size of page D.

[0741] Among them, Figure 5A The specific implementation manner of step S25 shown is similar to Figure 5A step S231 or step S232 shown.

[0742] 6. The D page displayed in the right split screen exits the display (corresponding to step S48 as shown in Figure 5B ).

[0743] As Figure 5B shown in (5) of, the D page may further include a return control 8, which is used to indicate that the user can trigger the return control 8 from the D page, and the return control 8 is used to exit the display of the D page.

[0744] After the electronic device detects the operation 1201 of the return control 8 indicated by the user on the D page, it can exit the Activity corresponding to the D page, so that the electronic device can switch from the user interface shown in the (5) exemplification to the user interface shown in the (4) exemplification. Figure 5B shown to the user interface shown in Figure 5B (4) exemplification.

[0745] In Scenario 2, based on the foregoing description, the electronic device can implement the following functions:

[0746] 1) In response to the operation triggered by the user, the electronic device can switch from displaying the a1 page to split-screen display of the a1 page and the B page.

[0747] 2) When the a1 page and the B page are in split-screen display, if the C2 page is opened from the a1 page, the C1 page will destroy the a1 page and be displayed in the area where the a1 page was displayed, and the B page will not be destroyed.

[0748] 3) When the a1 page and the B page are in split-screen display, if the D page is opened from the B page, the D page will destroy the B page and be displayed in the area where the B page was displayed, and the a1 page will not be destroyed.

[0749] 4) When the a1 page and the B page are in split-screen display, closing the C1 page will not affect the display of the B page.

[0750] 5) When the a1 page and the B page are in split-screen display, closing the D page will not affect the display of the a1 page.

[0751] 6) The B page can freely switch between full-screen display and split-screen display.

[0752] Thus, when the user is processing multiple tasks in parallel, the electronic device can switch any application from full-screen display of a sub-page to split-screen display of other pages of the application, and the new page opened from any split screen will destroy the page displayed in that split screen and be displayed in that split screen, solving the problem in the related art that the new page opened from any split screen will destroy the pages displayed in other split screens due to the coupling relationship between different split screens, avoiding the display interference between the pages in different split screens, enabling the pages in different split screens to run independently, and providing the user with a multi-task or immersive experience. In addition, after the application starts the in-application split-screen function, based on the user's needs, the electronic device can switch from split-screen display of multiple pages of the application to full-screen display of one page of the application, or from full-screen display of one page of the application to split-screen display of multiple pages of the application, providing the user with an efficient and flexible multi-window multi-task experience.

[0753] Based on Figures 5A - 5F the description shown, combined with Figures 6A - 6K, the specific implementation process of the split-screen display of multiple pages of any application on the electronic device is introduced. For the sake of convenience of description, Figures 6A - 6K In Figures 6A - 6K , taking the electronic device as a tablet computer, the application as the WeChat application, the A page as the chat dialog list, the a0 page includes the icon of the WeChat application set in the center, the a1 page is a specific chat dialog window, the B page is the page of the XX video mini-program in the WeChat application, the C2 page is the A page, and the D page is the page of Video 1 corresponding to the icon of Video 1 on the B page as an example for illustration.

[0754] Please refer to Figures 6A - 6K , Figures 6A - 6K which is the schematic diagram of the human-computer interaction interface provided by an embodiment of the present application.

[0755] The tablet computer can display the user interface 21 as shown in Figure 6A exemplarily. Among them, the user interface 21 can be the main interface (Home screen) of the desktop. The user interface 21 can include but is not limited to: the status bar, the navigation bar, the calendar indicator, the weather indicator, and multiple application icons, etc. The application icons at least include: the icon 601 of the WeChat application, and can also include: the icon of the calculator, the icon of Huawei Video, the icon of the browser, the icon of the camera, the icon of the music, the icon of the settings, the icon of the email, the icon of the memo, etc.

[0756] After the tablet computer detects the operation of opening the WeChat application indicated by the user (such as clicking the icon 401 of the WeChat application), it can display Figure 6B the user interface 22a and the user interface 22b as shown in exemplarily, and the user interface 22a is displayed in the left split screen, and the user interface 22b is displayed in the right split screen. Among them, the user interface 22a can be used to display the main page of the WeChat application (i.e., the A page). The user interface 22b can be used to display the secondary page of the WeChat application (i.e., the a0 page).

[0757] Among them, the display area areas of the user interface 22a and the user interface 22b can be the same or different, and the present application does not limit this. In addition, a control for adjusting the display area areas of the user interface 22a and the user interface 22b can be set in the overlapping boundary area between the user interface 22a and the user interface 22b, so as to adjust the display area areas of the user interface 22a and the user interface 22b in real time based on the user's needs.

[0758] It should be noted that in addition to Figure 6B the user interface 22a and the user interface 22b shown in exemplarily, the tablet computer can also display the main page of the WeChat application (i.e., the A page) full screen, or can display the main page of the WeChat application (i.e., the A page) in a partial display area (such as in the center), and the present application does not limit this.

[0759] After the tablet computer detects that the user performs an operation such as clicking on the control 602 in the user interface 22a shown in Figure 6B it, the right split screen can change from displaying the user interface 22b shown in the example to displaying Figure 6B the user interface 23b shown in the example. Among them, the user interface 23b can be a sub-page of the WeChat application (such as the page of the chat conversation between the user and xiaoyi (i.e., the a1 page)), thereby facilitating the user to have a WeChat chat with xiaoyi. And, the tablet computer can continue to display Figure 6C the user interface 22a shown in the example in the left split screen, thereby facilitating the user to implement other functions of the WeChat application. Figure 6C

[0760] Among them, the control 602 is used to enter the page of the chat conversation between the user and xiaoyi (i.e., the a1 page). The specific implementation manner of the control 602 in this application is not limited.

[0761] Among them, the user interface 23b at least includes a control 603. Among them, the control 603 is used to display the main page of the XX video browsing web page / XX video mini-program (i.e., the B page). The control 603 can be represented in the form of a link, video, picture, string, or text, etc.

[0762] In addition, the user interface 22b may also include a return control 6041 ( Figure 6C taking an arrow pointing to the left as an example for illustration in Figure 6B ), and the return control 6041 is used to exit the a1 page, so that the tablet computer can return from the user interface 22b and display Figure 5A the user interface 22b shown in the example. The return control 6041 here can be regarded as

[0763] the return control 02 in

[0764] After the tablet computer detects that the user performs an operation such as clicking on the control 603 in the user interface 23b shown in Figure 6C it, it can display Figure 6D the user interface 24 shown in the example, and the user interface 24 is used to display the main page of the XX video browsing web page / XX video mini-program (i.e., the B page).

[0765] It should be noted that when the user is in​Figure 6C The operation of clicking the control 603 in the user interface 23b shown in the figure can be regarded as the user triggering the corresponding control B in the page a1. Figure 5C or Figure 5E Operation 701 in .

[0766] The user interface 24 includes at least: a multi-function control 605 ( Figure 6D Three solid dots are used as an example), return control 606 ( Figure 6D In the figure, a solid circle in a hollow circle is used as an example for illustration) and the page content of page B.

[0767] Among them, the multi-function control 605 is used to enter the window of the XX video browsing web page / XX video applet with functions such as sharing, removing, split screen / full screen display, floating window display, settings, feedback and complaints, and re-entry.

[0768] The return control 606 is used to exit the XX video browsing webpage / XX video applet, so that the tablet computer returns from the current user interface (such as user interface 24 and user interface 25b, user interface 26b, user interface 27b and user interface 28 mentioned later) and displays Figure 6C The user interface 22a and the user interface 23b are shown as examples. The return control 606 here can be seen as Figure 5A and Fi...

Claims

1. A method for displaying an application page, which is applied to an electronic device, and is characterized in that, Comprising: Displaying a first page of a first application; In response to a first operation, displaying the first page in a first area and displaying a second page of the first application in a second area, where the first area does not coincide with the second area; Receiving a second operation on the first page; In response to the second operation, displaying a third page of the first application in the first area and displaying the second page in the second area; Receiving a third operation on the third page; In response to the third operation, exiting the display of the third page, displaying the first page of the first application in the first area, and displaying the second page in the second area; Receiving a fourth operation on the second page; In response to the fourth operation, displaying the first page in the first area and displaying a fourth page of the first application in the second area.

2. The method according to claim 1, wherein The method further comprises: Receiving a fifth operation on the fourth page; In response to the fifth operation, displaying the first page in the first area and displaying the second page in the second area.

3. The method according to claim 1 or 2, characterized in that After displaying the first page of the first application and before responding to the first operation, the method further comprises: Receiving a sixth operation on the second page; In response to the sixth operation, displaying a first control for indicating split-screen display of the first page and the second page; Receiving the first operation on the first control.

4. The method according to claim 1 or 2, characterized in that, Before responding to the first operation, the method further comprises: Receiving the first operation on the first page.

5. The method according to any one of claims 1-4, characterized in that, The second page is a mini-program page or the second page is a public account page.

6. The method according to any one of claims 1-5, characterized in that The method further comprises: Displaying a second control in an adjacent area of the first area and the second area, where the second control is used to adjust the area sizes of the first area and the second area.

7. The method according to any one of claims 1-6, characterized in that, The area sizes of the first area and the second area are equal.

8. The method according to any one of claims 1 to 7, characterized in that, The method further comprises: Receiving a seventh operation on the first page and / or the second page; In response to the seventh operation, displaying a third control for indicating full-screen display of the first page; Receiving an eighth operation on the third control; In response to the eighth operation, displaying the first page.

9. The method according to any one of claims 1-8, characterized in that, The method further comprises: Receiving a ninth operation on the second page; In response to the ninth operation, displaying the first page.

10. The method according to any one of claims 1-9, characterized in that, Displaying the first page includes: displaying the first page in a third area, where the third area includes the first area and the second area; or, Displaying the first page in the first area and displaying a fifth page of the first application in the second area, where the fifth page is different from both the first page and the second page; or, Displaying the first page in a fourth area, where the fourth area at least includes a part of the first area and a part of the second area.

11. The method according to any one of claims 1-8, characterized in that, The first page corresponds to a first task stack. The step of, in response to the first operation, displaying the first page in the first area and displaying the second page of the first application in the second area, where the first area does not coincide with the second area, specifically is: In response to the first operation, a second task stack is established, and a first message is sent to the first application. The first message is used to identify the first operation, which is related to the second page. The second page corresponds to the second task stack, and the first task stack is different from the second task stack; Receive a second message from the first application. The second message is used to indicate that the first page and the second page are to be displayed in split-screen mode; In response to the second message, display the first page in the first area and display the second page in the second area.

12. The method according to claim 11, wherein The step of "In response to the second message, display the first page in the first area and display the second page in the second area" includes: When, based on the second message, it is determined that the second task stack exists, the first application supports the in-application split-screen function, and the second page meets the preset requirements for split-screen display, based on the identifier of the first task stack, the identifier of the second task stack, and the split-screen parameters of the second page, display the first page in the first area in the first task stack and display the second page in the second area in the second task stack; or, When, based on the second message, it is determined that the first task stack is in a non-split-screen mode, the first application supports the in-application split-screen function, and the second page meets the preset requirements for split-screen display, based on the identifier of the first task stack, the identifier of the second task stack, and the split-screen parameters of the second page, display the first page in the first area in the first task stack and display the second page in the second area in the second task stack.

13. The method according to claim 11 or 12, characterized in that The second message includes: a first identifier, a second identifier, and a third identifier. The first identifier is used to indicate that the first page and any page are to be displayed in split-screen mode. The second identifier is used to represent the split-screen position of the any page. The third identifier is the identifier of the any page or the identifier of the second task stack.

14. The method according to any one of claims 1 to 10, characterized in that, The first page corresponds to the first task stack. The step of "In response to the first operation, display the first page in the first area and display the second page of the first application in the second area, where the first area and the second area do not overlap" specifically is: In response to the first operation, send a third message to the first application. The third message is used to identify the first operation, which is related to the second page. The second page corresponds to the first task stack; Receive a fourth message from the first application. The fourth message is used to indicate that the first page and the second page are to be displayed in split-screen mode; In response to the fourth message, establish a second task stack. The second page is changed from corresponding to the first task stack to corresponding to the second task stack. The first task stack is different from the second task stack; And display the first page in the first area and display the second page in the second area.

15. The method according to claim 14, wherein The step of "display the first page in the first area and display the second page in the second area" includes: When, based on the fourth message, it is determined that the second page corresponds to the first task stack, that the first application supports in-application split-screen functionality, and that the second page meets the preset requirements for split-screen display, based on the identifier of the first task stack, the identifier of the second task stack, and the split-screen parameters of the second page, display the first page in the first area in the first task stack and display the second page in the second area in the second task stack; or, When, based on the fourth message, it is determined that the first task stack is in a non-split-screen mode, that the first application supports in-application split-screen functionality, and that the second page meets the preset requirements for split-screen display, based on the identifier of the first task stack, the identifier of the second task stack, and the split-screen parameters of the second page, display the first page in the first area in the first task stack and display the second page in the second area in the second task stack.

16. The method according to claim 14 or 15, characterized in that, The fourth message includes: a fourth identifier, a fifth identifier, and a sixth identifier. The fourth identifier is used to indicate split-screen display of the first page and any one page. The fifth identifier is used to represent the split-screen position of the any one page. The sixth identifier is the identifier of the any one page or the identifier of the first task stack.

17. The method according to any one of claims 11-16, characterized in that, The fifth page corresponds to the first task stack.

18. The method according to any one of claims 11-17, characterized in that, In response to the second operation, display the third page of the first application in the first area, specifically: Receive a fifth message, which is used to indicate opening the third page from the first page. The third page corresponds to the first task stack; In response to the fifth message, determine whether the first task stack is in a split-screen mode; When the first task stack is in a split-screen mode, based on the identifier of the first task stack, the identifier of the third page, and the split-screen parameters of the third page, display the third page in the first area in the first task stack.

19. The method according to any one of claims 11-18, characterized in that, In response to the fourth operation, display the fourth page of the first application in the second area, specifically: Receive a sixth message, which is used to indicate opening the fourth page from the second page. The fourth page corresponds to the second task stack; In response to the sixth message, determine whether the second task stack is in a split-screen mode; When the second task stack is in a split-screen mode, based on the identifier of the second task stack, the identifier of the fourth page, and the split-screen parameters of the fourth page, display the fourth page in the second area in the second task stack.

20. An electronic device, characterized in that, Includes: A memory and a processor; The memory is used to store program instructions; The processor is used to call the program instructions in the memory to cause the electronic device to execute the application page display method according to any one of claims 1-19.

21. A chip system, characterized in that, The chip system is applied to an electronic device including a memory, a display screen, and a sensor; the chip system includes: a processor; when the processor executes computer instructions stored in the memory, the electronic device executes the application page display method according to any one of claims 1-20.

22. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor to cause the electronic device to execute, it implements the application page display method according to any one of claims 1-21.

Images