Application page display method and electronic device

Abstract

The present application provides an application page display method and an electronic device. The method includes: displaying a first page of a first application; in response to a first operation of a user, displaying the first page in a first area, and displaying a second page of the first application in a second area, and the first area and the second area do not overlap; receiving a second operation of a 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, receiving a third operation of a 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. Thus, different split screens of the electronic device can be decoupled to independently display multiple pages of any application, and a new page opened in any split screen will not interfere with pages displayed in other split screens, providing users with a multi-tasking or immersive experience.

Description

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on July 9, 2020, with application number 202010658161.5 and application name “A method and device for split-screen display of an application interface”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present 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, applications are based on proportional magnification technology, and the display effect is very unsatisfactory. Various inharmonious issues such as large icons, large fonts, large pictures, page / font / picture stretching, deformation, dislocation, and truncation appear. If the application needs to be adapted to the screen ratio of the electronic device, the development workload is too heavy.

[0004] In the current split-screen display solution within an app, the pages displayed on the left and right split screens have a strongly coupled relationship. That is, any new page opened in the left split screen will be displayed in the right split screen, causing the page originally displayed in the right split screen to be flushed away. The new page opened in the right split screen will in turn flush the page displayed in the left split screen, affecting the user's multitasking operations. Once the split-screen display solution within the app is activated, all pages can only be opened in split-screen display mode, and it is impossible to switch freely between full-screen display and split-screen display according to user needs. Summary of the Invention

[0005] The present 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 a new page opened in any split screen will not interfere with the pages displayed in other split screens, providing users with a multi-tasking or immersive experience.

[0006] In a first aspect, the present application provides an application page display method, comprising: displaying a first page of a first application; in response to a first operation of a user, displaying the first page in a first area, and displaying a second page of the first application in a second area, wherein the first area and the second area do not overlap.

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

[0008] A third operation of the user is received on the second page; in response to the third operation, the first page is displayed in the first area, and a fourth page of the first application is displayed in the second area.

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

[0010] The first page may be any page in the first application. For example, the first page may be the home page of the first application, or a page other than the home page in the first application. The second page may be any page in the first application, and the page content of the first page and the second page may be the same or different, which is not limited in this application.

[0011] The first area and the second area are both display areas of the electronic device. This application does not limit the area of ​​the first area and the second area. In addition, the first area and the second area may cover the entire display area of ​​the electronic device, or the first area and the second area may cover a portion of the display area of ​​the electronic device, which is not limited in this application.

[0012] In some embodiments, if the electronic device is in landscape mode, the first area is the display area of ​​the left screen of the electronic device, and the second area may be the display area of ​​the right screen of the electronic device; alternatively, the first area is the display area of ​​the right screen of the electronic device, and the second area may be the display area of ​​the left screen of the electronic device. If the electronic device is in portrait mode, the first area is the display area of ​​the top screen of the electronic device, and the second area may be the display area of ​​the bottom screen of the electronic device; alternatively, the first area is the display area of ​​the bottom screen of the electronic device, and the second area may be the display area of ​​the top screen of the electronic device.

[0013] In a possible design, the first area and the second area are equal in area, thereby improving the user's viewing experience when browsing the first page and the second page.

[0014] The second operation is an operation triggered on the first page, and the type of the second operation includes but is not limited to at least one type such as click, long press, and drag. The third operation is an operation triggered on the second page, and the type of the third operation includes but is not limited to at least one type such as click, long press, and drag.

[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, which is not limited in this application.

[0016] Those skilled in the art will understand that an Activity is a display component of an Android application (APP), and an Activity provides a window to interact with the user 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 display screen of the electronic device, or it can be smaller than the display area of ​​the electronic device and float above other windows. An APP is usually composed of multiple Activities that are loosely connected to each other. Usually, an APP can designate a certain Activity as the main Activity, which refers to the Activity presented to the user when the user first starts the APP. 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 uses a stack (task stack) to manage the activities in the stack. This stack is also called the back stack. The order of the activities in the stack is 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 region mentioned in this application can be understood as the area displayed in the task stack where the application activity is located. Therefore, the display area of ​​any activity in the task stack corresponding to the first region is smaller than or equal to the first region, and the display area of ​​any activity in the task stack corresponding to the second region is smaller than or equal to the second region.

[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, thereby ensuring that the pages displayed in the first area and the pages displayed in the second area do not interfere with each other.

[0020] Based on the above 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, thereby 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, so as to ensure that the display of the third page does not interfere with the display of pages in the second area, such as the second or fourth page. The task stack corresponding to the third page can be the first task stack, or it can be another task stack other than the first and second task stacks.

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

[0023] It should be noted that the first task stack, the second task stack, and other task stacks mentioned above 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 cut 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 on the split screen and display it in the split screen, which solves the phenomenon in the related art that due to the coupling relationship between different split screens, the new page opened in any split screen will destroy the pages displayed on other split screens, avoids the display interference between pages in different split screens, and enables pages in different split screens to run independently, providing users with a multi-tasking or immersive experience. In addition, after the application starts the in-application split-screen function, the electronic device can switch from displaying multiple pages of the application in split screen to displaying one page of the application in full screen based on user needs, or switch from displaying one page of the application in full screen to displaying multiple pages of the application in split screen, providing users with an efficient and flexible multi-window multi-tasking experience.

[0025] In one possible design, the method further includes: receiving a fourth user operation on the third page. In response to the fourth operation, displaying the first page in the first area and displaying the second page in the second area. And / or receiving a fifth user 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.

[0026] The fourth operation is an operation triggered on the third page. The types of the fourth operation include, but are not limited to, at least one of click, long press, and drag. In some embodiments, the third page may include a control that indicates a jump from the third page to the first page. This application does not limit parameters such as the shape, position, and size of this control. Therefore, the fourth operation is the operation triggered on this control.

[0027] The fifth operation is an operation triggered on the fourth page. The type of the fifth operation includes, but is not limited to, at least one of click, long press, and drag. In some embodiments, the fourth page may include a control that indicates a jump from the fourth page to the second page. This application does not limit parameters such as the shape, position, and size of the control. Therefore, the fifth operation is the operation triggered on the control.

[0028] As a result, the electronic device can jump from the split-screen display of the third and second pages to the split-screen display of the first and second pages, or jump from the split-screen display of the third and fourth pages to the split-screen display of the first and second pages, or jump from the split-screen display of the first and fourth pages to the split-screen display of the first and second pages, which is closer to user operations and helps to improve the user experience.

[0029] In one possible design, after displaying the first page of the first application and before responding to the first user operation, the method further includes: receiving a sixth user operation on the second page. In response to the sixth operation, displaying a first control, the first control being used to indicate split-screen display of the first and second pages. The first operation is received on the first control.

[0030] Among them, the sixth operation is an operation triggered on the second page, and the type of the sixth operation includes but is not limited to at least one type such as click, long press, and drag. 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 desire to split the screen, the electronic device displays the first control when it receives the second operation on the second page. When the electronic device receives the first operation on the first control, it can display the first page in the first area and display the second page of the first application in the second area, and the first area and the second area do not overlap. Therefore, based on the user's wishes, a possible implementation method is provided for the split-screen display of the first page and the second page, which is more in line with the user's usage habits.

[0031] In one possible design, before responding to the user's first operation, the method further includes: receiving the first operation on the first page. In some embodiments, the first page may include a control that indicates that the first page and the second page are displayed in a split-screen manner. This application does not limit parameters such as the shape, position, and size of this control. Therefore, the fifth operation is the operation triggered on this control.

[0032] In summary, when the electronic device receives a first operation on a first page, it can display the first page in the first area and the second page of the first application in the second area, and the first area and the second area do not overlap. This provides another possible implementation method for split-screen display of the first and second pages, providing users with a smooth browsing experience.

[0033] In one possible design, the method further includes: displaying a second control in an adjacent area between the first and second areas, the second control being used to adjust the area of ​​the first and second areas. The adjacent area between the first and second areas may be the area between the first and second areas. This 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 and second areas, 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, where the third control is 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 mode, the electronic device can display the third control when it receives the seventh operation. When the electronic device receives the eighth operation on the third control, it can display the first page. Thus, based on the user's wishes, a possible implementation method is provided for converting the split-screen display of the first and second pages into the display of the first page, which is more in line with the user's usage habits. Thus, when the application starts the split-screen function within the application 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] The ninth operation may be an operation triggered on the second page, and the type of the ninth operation includes but is not limited to at least one type such as click, long press, and drag. In some embodiments, the second page may include a control that is used to indicate that the first page is displayed full screen. This application does not limit the shape, position, size, and other parameters of the control. Therefore, the ninth operation is the operation triggered on the control.

[0040] In summary, when the first page and the second page are displayed in split-screen mode, the electronic device can display the first page upon receiving the first operation. This provides another possible implementation method for converting the split-screen display of the first and second pages into the display of the first page, providing users with a smooth browsing experience. Thus, when the application activates 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.

[0041] The full-screen display of the first page may include multiple display modes.

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

[0043] In one 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. The fifth page is different from the first and second pages. The fifth page can be a page other than the first page in the first application, and the task stack of the fifth page is the same as the task stack of the first page. This provides another possible implementation method for full-screen display of the first page, allowing users to browse the page content of more pages.

[0044] In one possible design, the first page is displayed in the fourth area, which includes at least a portion of the first area and a portion of the second area. This provides another possible implementation for full-screen display of the first page, providing users with a more comfortable browsing experience.

[0045] In one 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. The first operation is related to the second page. The second page corresponds to the second task stack. 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 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, this application does not limit the specific implementation of the first message and the second message. The order of execution of the steps 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 prioritized and can be executed sequentially or simultaneously, and this application does not limit this. The step of the electronic device establishing the second task stack needs to be performed before the electronic device receives the second message.

[0047] The startup mode of the second page is set to a mode for creating a new task stack. Therefore, the electronic device can create a second task stack corresponding to the second page in response to the first operation.

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

[0049] When, based on the second message, it is determined 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, based on the second message, it is determined that the first task stack is in non-split-screen mode, it is determined that 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.

[0052] Therefore, when the second task stack is established, the electronic device can 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 based on the above conditions.

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

[0054] In one possible design, 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 other page are displayed in split screen, the second identifier is used to indicate the split screen position of any one page, and the third identifier is the identifier of any one page or the identifier of the second task stack.

[0055] In one 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, and 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, and the fourth message is used to indicate that the first page and the second page are displayed in split screens; in response to the fourth message, a second task stack is established, and 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 the first page is displayed in the first area, and the second page is displayed in the second area.

[0056] Among them, this application does not limit the specific implementation method of the third message and the fourth message.

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

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

[0059] When it is determined based on the fourth message that the second page corresponds to the first task stack, that the first application supports the split-screen function within the application, 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. Or,

[0060] When, based on the fourth message, it is determined that the first task stack is in non-split-screen mode, it is determined that 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.

[0061] Therefore, when the second task stack is not established, the electronic device can establish the second task stack based on the above conditions and implement 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.

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

[0063] In one possible design, the fourth message includes: a fourth identifier, a fifth identifier and a sixth identifier, the fourth identifier is used to indicate that the first page and any other page are displayed in split screen, the fifth identifier is used to indicate the split screen position of any one page, and the sixth identifier is the identifier of any one page or the identifier of the first task stack.

[0064] In one possible design, in response to the second operation, the third page of the first application is displayed in the first area, specifically: receiving a fifth message, the fifth message is used to indicate opening the third page from the first page, and the third page corresponds to the first task stack; in response to the fifth message, determining whether the first task stack is in split-screen mode; when the first task stack is in 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, displaying the third page in the first area in the first task stack. This application does not limit the specific implementation of the fifth message.

[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 split-screen mode, that is, whether the first page is in a split-screen display state. Therefore, when it is determined that the first task stack is in split-screen mode, the electronic device can display the third page in the first area while 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 of the first area becomes the other task stack, and the above-mentioned judgment conditions for displaying the third page remain unchanged.

[0067] In one possible design, in response to the third operation, the fourth page of the first application is displayed in the second area, specifically: receiving a sixth message, the sixth message is used to indicate opening the fourth page from the second page, and the fourth page corresponds to the second task stack; in response to the sixth message, determining whether the second task stack is in split-screen mode; when the second task stack is in 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 area in the second task stack. This application does not limit the specific implementation of the sixth message.

[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 split-screen mode, that is, whether the second page is in a split-screen display state. Therefore, when it is determined that the second task stack is in split-screen mode, the electronic device can display the fourth page in the second area while the page in the first area 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 of the second area becomes the other task stack, and the above-mentioned judgment conditions for displaying the fourth page remain unchanged.

[0070] In a second aspect, the present application provides an electronic device comprising: 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 so that the electronic device executes the application page display method in the first aspect and any possible design of the first aspect.

[0071] In a third aspect, the present application provides a chip system, which 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 in the first aspect and any possible design of the first aspect.

[0072] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor in an electronic device, implements the application page display method in the first aspect and any possible design of the first aspect.

[0073] In a fifth aspect, the present application provides a computer program product, comprising: execution instructions, the execution instructions are stored in a readable storage medium, at least one processor of an electronic device can read the execution instructions from the readable storage medium, and at least one processor executes the execution instructions so that the electronic device implements the application page display method in the first aspect and any possible design of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0076] Figure 2b for Figure 2a The software structure diagram of the parallel window manager (HwMagicWindowManager);

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

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

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

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

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

[0082] Figure 8 A flowchart of a method for displaying an application page provided in this application;

[0083] Figures 9A-9C A schematic diagram of a human-computer interaction interface provided in one embodiment of the present application. DETAILED DESCRIPTION

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

[0085] This application provides an application page display method and electronic device that can decouple different split screens of the electronic device to independently display multiple pages of any application, and a new page opened in any split screen will not interfere with the pages displayed in other split screens, providing users with a multi-tasking or immersive experience. In addition, when the application activates the in-app 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.

[0086] The in-app split-screen function mentioned in this application can be understood as: the electronic device can simultaneously realize the independent display of different pages of any application in split screens, and the new page opened 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 left-right split screen or top-bottom split screen.

[0087] Among them, the electronic devices can be tablet computers, mobile phones (such as foldable screen mobile phones, large screen mobile phones, etc.), wearable devices, vehicle-mounted devices, augmented reality (AR) / virtual reality (VR) devices, laptops, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), smart TVs, smart screens, high-definition TVs, 4K TVs, smart speakers, smart projectors and other Internet of Things (IOT) devices. This application does not impose any restrictions on the specific types of electronic devices.

[0088] The following takes the electronic device as a tablet as an example, combined with Figure 1 , introduces the electronic equipment involved in this application.

[0089] Figure 1 This is a schematic diagram of the structure of an electronic device provided in one embodiment of the present application. Figure 1 As 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, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air 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 should 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, or may combine or separate certain components, or arrange the components differently. The components shown in the figure 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). The different processing units may be independent devices or integrated into one or more processors.

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

[0093] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

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

[0095] The I2C interface is a bidirectional synchronous serial bus that includes a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple I2C bus lines. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, and the like via different I2C bus interfaces. For example, the processor 110 may be coupled to the touch sensor 180K via the I2C interface, enabling communication between the processor 110 and the touch sensor 180K via the I2C bus interface, thereby implementing the touch function of the electronic device 100.

[0096] The I2S interface can be used for audio communication. In some embodiments, the processor 110 can include multiple 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, enabling the function of answering calls through a Bluetooth headset.

[0097] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via a 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, enabling the function of answering calls via a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0098] The UART interface is a universal serial data bus used 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 Bluetooth functionality. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the UART interface, enabling the function of playing music through Bluetooth headphones.

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

[0100] The GPIO interface can be configured via software. The GPIO interface can be configured as either a control signal or a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 to the camera 193, display 194, wireless communication module 160, audio module 170, 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 USB standards and may be a Mini USB interface, a Micro USB interface, a USB Type-C interface, or the like. The USB interface 130 can be used to connect a charger to charge the electronic device 100, or 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 augmented reality devices.

[0102] It is understood that the interface connection relationship between the modules illustrated in this application is only for illustrative purposes and does not constitute a structural limitation on the electronic device 100. In other embodiments, the electronic device 100 may also adopt different interface connection methods from the above embodiments, or a combination of multiple interface connection methods.

[0103] The charging management module 140 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also provide power to the electronic device via 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 input from the battery 142 and / or the charging management module 140, and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set 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 modem processor and the baseband processor.

[0106] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

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

[0108] The modem processor may include a modulator and a demodulator. 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. The demodulator then 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 passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0109] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0110] In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology 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. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0111] Electronic device 100 implements display functionality through a GPU, display screen 194, and an application processor. A GPU is a microprocessor for image processing that connects 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 that execute program instructions to generate or modify display information.

[0112] Display screen 194 is used to display images, videos, and the like. 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, or a quantum dot light-emitting diode (QLED). In some embodiments, electronic device 100 may include one or N display screens 194, where N is a positive integer greater than one.

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

[0114] The ISP processes data fed back by camera 193. For example, when taking a photo, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, which is then passed to the ISP for processing and converted into a visible image. The ISP can also perform algorithmic optimization on image noise, brightness, and skin tone. It can also optimize parameters such as exposure and color temperature of the captured scene. In some embodiments, the ISP can be located within camera 193.

[0115] The camera 193 is used to capture still images or videos. The 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 light signal into an electrical signal, and then passes the electrical signal to the ISP for conversion 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 RGB, YUV or other format. In some embodiments, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0116] The digital signal processor is used to process digital signals. In addition to processing 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.

[0117] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. This allows electronic device 100 to play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, and MPEG4.

[0118] The NPU is a neural network (NN) computing processor. Drawing on the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it rapidly processes input information and can continuously self-learn. The NPU can enable intelligent cognitive applications in electronic device 100, such as image recognition, face recognition, speech recognition, and text comprehension.

[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 via the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be stored on the external memory card.

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

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

[0122] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be provided in the processor 110, or some functional modules of the audio module 170 can be provided in the processor 110.

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

[0124] The receiver 170B, also called a "handset", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or a voice message, the user can place the receiver 170B close to the ear to hear the voice.

[0125] Microphone 170C, also known as "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their 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 other embodiments, the electronic device 100 can be provided with two microphones 170C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify the source of sound, realize directional recording function, etc.

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

[0127] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A can be located on display screen 194. There are many types of pressure sensors 180A, such as resistive, inductive, and capacitive. A capacitive pressure sensor can include at least two parallel plates made of conductive material. When force acts on pressure sensor 180A, the capacitance between the electrodes changes. Electronic device 100 determines the intensity of the pressure based on this change in capacitance. When a touch operation is applied to display screen 194, electronic device 100 detects the touch intensity based on pressure sensor 180A. Electronic device 100 can also calculate the touch location based on the detection signal from pressure sensor 180A. In some embodiments, touch operations applied to the same touch location but with different touch intensities can correspond to different operation instructions. For example, when a touch operation with an intensity less than a first pressure threshold is applied to a short message application icon, a command to view short messages is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to a short message application icon, a command 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., x, y, and z axes) can be determined by the gyroscope sensor 180B. The gyroscope sensor 180B can be used for anti-shake shooting. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of the electronic device 100 shaking, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to offset the shaking 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 scenes.

[0129] The air pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device 100 calculates the altitude using the air pressure value measured by the air 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 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 cover based on the magnetic sensor 180D. Based on the detected opening and closing status of the case or flip cover, features such as automatic unlocking of the flip cover can be configured.

[0131] Accelerometer 180E can detect the magnitude of acceleration of electronic device 100 in all directions (generally three axes). It can also detect the magnitude and direction of gravity when electronic device 100 is stationary. It can also be used to identify the electronic device's posture, enabling applications such as switching between landscape and portrait modes and pedometers.

[0132] The distance sensor 180F is used to measure distance. The electronic device 100 can measure distance using infrared or laser. In some embodiments, when shooting a scene, the electronic device 100 can use the distance sensor 180F to measure 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 a photodiode to detect 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 that the user is holding the electronic device 100 close to the ear to talk, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used in leather case mode and pocket mode to automatically unlock and lock the screen.

[0134] Ambient light sensor 180L is used to sense ambient light brightness. Electronic device 100 can adaptively adjust the brightness of display screen 194 based on the perceived ambient light. Ambient light sensor 180L can also be used to automatically adjust white balance when taking photos. Ambient light sensor 180L can also work with proximity light sensor 180G to detect whether electronic device 100 is in a pocket to prevent accidental touches.

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

[0136] The temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device 100 uses the temperature detected by the temperature sensor 180J to execute a temperature processing strategy. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 reduces the performance of the processor located 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 prevent the electronic device 100 from shutting down abnormally due to low temperature. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 boosts the output voltage of the battery 142 to prevent abnormal shutdown due to low temperature.

[0137] The touch sensor 180K is also called a "touch panel." The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen." The touch sensor 180K is used to detect touch operations applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operations to the application processor to determine the type of touch event. Visual output related to the touch operations can be provided via the display screen 194. In other embodiments, the touch sensor 180K can also be disposed on the surface of the electronic device 100, in a location different from that of the display screen 194.

[0138] The bone conduction sensor 180M can obtain vibration signals. In some embodiments, the bone conduction sensor 180M can obtain vibration signals from the vibrating bones of the human body. The bone conduction sensor 180M can also contact the human pulse to receive blood pressure pulse signals. In some embodiments, the bone conduction sensor 180M can also be set in headphones to form bone conduction headphones. The audio module 170 can parse out voice signals based on the vibration signals of the vibrating bones of the human body obtained by the bone conduction sensor 180M to implement voice functions. The application processor can parse heart rate information based on the blood pressure pulse signals obtained by the bone conduction sensor 180M to implement heart rate detection functions.

[0139] The buttons 190 include a power button, a volume button, and the like. The buttons 190 may be mechanical buttons or touch buttons. The electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 100.

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

[0141] The indicator 192 may be an indicator light, which may be used to indicate the charging status, power level changes, messages, missed calls, notifications, etc.

[0142] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to or disconnected from the electronic device 100 by inserting it into or removing it from the SIM card interface 195. The electronic device 100 can support 1 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, and the like. Multiple cards can be inserted into the same SIM card interface 195 at the same time. 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 communications. 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 micro-kernel architecture, a microservice architecture, or a cloud architecture. This application takes the Android system with a layered architecture as an example to illustrate the software structure of the electronic device 100. Among them, this application does not limit the type of operating system of the electronic device. For example, Android system, Linux system, Windows system, iOS system, Harmony operating system (Harmony OS), etc.

[0144] Figure 2a This is a software structure diagram of an electronic device provided in one embodiment of the present application. Figure 2a As shown, the layered architecture divides software into several layers, each with clear roles and divisions of labor. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: from top to bottom, the application layer (APP), the application framework layer (APP framework), the Android runtime (Android runtime) and system libraries (libraries), and the kernel layer (kernel).

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

[0146] like Figure 2a As shown, the application package may 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, and device control.

[0147] Smart home applications can be used to control or manage connected home devices. For example, home devices may include lights, televisions, and air conditioners. Alternatively, home devices may include security door locks, speakers, robot vacuums, electrical outlets, body fat scales, desk lamps, air purifiers, refrigerators, washing machines, water heaters, microwave ovens, rice cookers, curtains, fans, televisions, set-top boxes, doors, and windows.

[0148] In addition, the application package may also include: home screen (ie, desktop), negative one screen, control center, notification center and other applications.

[0149] Among them, the negative one screen, also known as the "-1 screen", refers to sliding the screen to the right on the main screen of the electronic device until sliding to the user interface (UI) of the leftmost split screen. For example, the negative one screen can be used to place some quick service functions and notification messages, such as global search, quick entry to a certain page of the application (payment code, WeChat, etc.), instant messages and reminders (express information, expenditure information, commuting conditions, taxi travel 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 to slide up at the bottom of the electronic device. The notification center is the pull-down message notification bar of the electronic device, that is, the user interface displayed by the electronic device when the user starts to slide down at the top of the electronic device.

[0150] The application framework layer provides an application programming interface (API) and programming framework for the applications in the application layer. The application framework layer includes some predefined functions.

[0151] like Figure 2a As shown, the application framework layer may 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), and the like.

[0152] Third-party interface layer (EasyGoSDK): An interface layer used to connect to third-party applications, adapted to various third-party applications. 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 depend on the software system. Third-party applications are applications other than system applications. Third-party applications may 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).

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

[0154] Among them, Activity is a display component of an Android APP. 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 it can be smaller than the display area of ​​the electronic device and float above other windows. An APP is usually composed of multiple Activities that are loosely connected to each other. Usually, an APP can designate a certain Activity as the main Activity, which refers to the Activity presented to the user when the user first starts the APP. 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] A window manager manages window programs, such as managing window status and properties, adding, removing, and updating views, window order, and message collection and processing. A window manager can obtain the display size, determine whether a status bar is present, lock the screen, and take screenshots. Furthermore, the window manager is the gateway for external access to windows.

[0156] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0157] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0158] The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including answering, hanging up, etc.).

[0159] The resource manager provides applications with various resources, such as localized strings, icons, images, user interface layout files (Layout XML), video files, fonts, colors, and identity documents (IDs) for user interface modules (UI components). Furthermore, the resource manager manages these resources in a unified manner.

[0160] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically without user interaction. For example, the Notification Manager is used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar of the system as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include text messages in the status bar, beeps, vibrations on electronic devices, and flashing indicator lights.

[0161] The parallel window manager (HwMagicWindowManager) is a customized service of the software system, namely HwMagicWindowService, which runs in the system server. Its most important function is to encapsulate a series of policy interfaces by combining multiple data modules within the service, embed the stubbing process in the process of launching, managing, and displaying Activities in the native application framework layer, execute the strategy of HwMagicWindowService, and provide a basic framework for each application to implement the split-screen function (MagicWindow) within the application.

[0162] The stub process is the process of writing or generating stub code to replace associated or unimplemented code. One purpose of the stub process is to set the behavior of the HwMagicWindowService's policy-related code during testing to meet test requirements.

[0163] See also Figure 2b , Figure 2b FIG. 4 shows a software structure diagram of the parallel window manager (HwMagicWindowManager). Figure 2b As shown, the parallel window manager (HwMagicWindowManager) may include: a policy module, a configuration module, a data management module, a background layer drawing module, and a motion effect module.

[0164] Policy module: Executes the strategy for the split-screen function within the application, including activity startup strategy, process startup strategy, window display strategy, etc.

[0165] Configuration module: loads feature configuration parameters, such as window size bounds information, such as window size and split screen size.

[0166] Data Management Module: This module includes user-selected settings data, such as the configuration parameters that users set in the electronic device's settings app to enable or disable split-screen functionality within each app. The data management module can also associate other data.

[0167] Background layer drawing module: This module displays the background UI when windows are switched on the electronic device. The background UI can be a wallpaper with Gaussian blur, a page with Gaussian blur, a completely black display, or the main interface, etc. This application does not limit this.

[0168] For example, when the electronic device switches from split screen to full screen, the background UI is displayed. For another example, when the electronic device switches from full screen to split screen, the background UI is displayed. For another example, when the left and right split screens are switched, the background UI is displayed.

[0169] Animation module: A customized animation interface module after the split-screen function is activated within the application, such as window startup animation, split-screen / full-screen window switching animation, left and right split-screen window closing animation, and other interfaces.

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

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

[0172] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0173] The system library can include multiple functional modules, such as surface manager, media libraries, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

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

[0175] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding 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, compositing, and layer processing.

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

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

[0179] The following is an example of the software and hardware workflow of the electronic device 100, using a scenario where a smart speaker is used to play sound.

[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 raw input events (including touch coordinates, timestamp of the touch operation, and other information). The raw input events are stored in the kernel layer. The application framework layer obtains the raw input events 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 is 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 should 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, or may combine or separate certain components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0182] Based on the above description, for any application installed in an electronic device, the electronic device supports the in-application split-screen display of multiple pages of the application, thereby realizing the in-application split-screen function of the application. The in-application split-screen display here can be understood as two pages within the application being displayed using two windows respectively, and these two windows can be split left and right or split up and down. Left and right split screen refers to when an electronic device displays two pages of the application respectively, and the windows corresponding to the aforementioned two pages are arranged side by side in the display screen of the electronic device. Usually, the electronic device can realize left and right split screen display when it is in a horizontal state. Top and bottom split screen refers to when an electronic device displays two pages of the application respectively, and the windows corresponding to the aforementioned two pages are arranged up and down in the display screen of the electronic device. Usually, the electronic device can realize left and right split screen display when it is in a vertical state.

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

[0184] The a0 page is a default page in the application (i.e., a sub-page), and the Activity corresponding to the A page and the Activity corresponding to the a0 page run in the same task (which can be understood as the same stack / task stack). In addition, the a0 page is usually customized by a third-party developer. After the application is started, the A page and the a0 page are displayed on the display screen of the electronic device at the same time. The a0 page plays an aesthetically pleasing decorative role, so that the display page of the application can be more adapted to the display screen of the electronic device and achieve a better display effect. Among them, the a0 page may include the icon of the application, and may also include controls that provide users with certain functions of the application. This application does not limit the specific content of the a0 page.

[0185] Page a1 is a subpage of page A and can be any page in the application except page A. The activity corresponding to page A can start the activity corresponding to page a1, and the activities corresponding to page A and page a1 run in the same task (which can be understood as the same stack).

[0186] Control B is used to trigger the display of page B. The user can trigger control B from page A or from page a1, and this application does not limit this. The methods of triggering controls mentioned in this application may include various implementation methods such as clicking, long pressing, sliding, voice search, long pressing, and text input. The controls mentioned in this application may include, but are not limited to, buttons, input boxes, icons, and text.

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

[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 (launchMode) of the activity corresponding to page B is set to singleInstance mode to ensure the uniqueness of the activity corresponding to page B within its task stack. Furthermore, page B is launched using the newtask launch method. Therefore, when page B is triggered to display, the electronic device's software system establishes a new task stack, and the activity corresponding to page B runs in this new task stack.

[0190] In other embodiments, the launch mode (launchMode) of the activity corresponding to page B is not set to singleInstance mode. When page B is triggered to display, the electronic device's software system does not create a new task stack. Instead, after receiving the user trigger for the split-screen control for page B, the electronic device creates a new task stack when it determines that pages A and B need to be displayed split-screen, and the activity corresponding to page B runs in the 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 other than page B in the application.

[0192] Then, based on the above description, combined with scenario one and scenario two, taking the electronic device in landscape mode and the electronic device displaying two pages of the application in left and right split screen as an example, the specific implementation process of the electronic device implementing the in-application split-screen function of the application is introduced.

[0193] Scene 1

[0194] In scenario one, after the electronic device detects the user's instruction to trigger the control B in page A, it can realize the split-screen display of page A and page B, thereby realizing the in-application split-screen function of the application.

[0195] See also Figure 3A-3F , Figure 3A-3F This is a flow chart of a method for displaying an application page provided in one embodiment of the present application. Figure 3A It shows the process from the current page display to the next page of the application. Figure 3B shows the process of returning from the current page of the application to the previous page, and Figure 3A-3B The display page is the same as in .

[0196] 0. Display of page A

[0197] When the electronic device is in landscape mode, the display screen of the electronic device may display the following Figure 3A The interface shown in (1a) includes page A and page a0.

[0198] Figure 3A In (1a), the page A displayed on the interface includes a control B, which is used to indicate that the user can trigger the control B from the page A. The page A displayed on the interface also includes a control C1, which is used to indicate that the user can trigger the control C1 from the page A. The control C1 is used to trigger the display of the C1 page, and the C1 page is all pages in the application except the main page and the B page. The C1 page may also include the a1 page, or may not include the a1 page, and this application does not limit this.

[0199] Among them, page A can be displayed in full screen, such as Figure 3A As shown in (1b), it can also 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 (such as Figure 3A (1c)) or the A page and a0 page are displayed in a split screen (as shown in Figure 3A (1a)), this application does not limit the display mode of page A, and it is set according to the configuration parameters of the application itself and the configuration parameters of the software system. For the sake of convenience, the following scenario is used in Figure 3A The example in which the A page shown in (1a) is displayed in the left split screen and the a0 page is displayed in the right split screen is used for illustration.

[0200] In some embodiments, the page A displayed on the interface may also include a return control 01 ( Figure 3A(not shown) indicates that the user can trigger the return control 01 from page A. 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 electronic device's display screen displays the electronic device's desktop.

[0201] 1. Left and right split screen display of page A and page B (corresponding to Figure 3A Step S11 shown)

[0202] In some embodiments, after the electronic device detects the user's instruction to trigger operation 101 of control B in page A, if the launch mode (launchMode) of the Activity corresponding to page B is set to singleInstance mode, a new Task (i.e., a task stack different from the task stack corresponding to page A) can be created and the Activity corresponding to page B can be started in this new Task.

[0203] The new Task is different from the Task corresponding to Page A. This means that the Activity corresponding to Page B enters a different Task from the Activity corresponding to Page A. For Control B, please refer to the previous description and will not be repeated here.

[0204] After the Activity corresponding to page B is started, the electronic device can display page B by default (i.e. Figure 3A In addition, page B includes a split-screen / full-screen control, which indicates 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 user's instruction to trigger the split-screen / full-screen control in page B, the electronic device may send a 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 of method 1 (called setTaskPosition) for split-screen display within the application based on the aforementioned operation 102. Method 1 is used to indicate that page A and page B are split-screen displayed. Among them, this application does not limit the representation method of message 1. For example, message 1 may include the reported point coordinates of the aforementioned operation 102.

[0206] Among them, the split-screen position mentioned above 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 limit this. For the sake of convenience, the split-screen position can be represented by targetPosition. Generally, when any page is displayed in 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 page B to be displayed in right split screen.

[0207] Therefore, since the aforementioned operation 102 is triggered on the split-screen / full-screen control on page B, and the electronic device can obtain that the electronic device was in full-screen display 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 page A and page B in a split-screen manner, and then the electronic device determines the split-screen position of page B, that is, setting targetPosition to 1 or 2. It should be noted that, usually when page A and page B are displayed in a split-screen manner, targetPosition is set to 2 by default.

[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 page B, the split-screen position of page B, and the method name of method 1 for split-screen display within the application (called setTaskPosition).

[0209] It should be noted that the electronic device establishes a new Task execution step in response to operation 101, and the software system of the electronic device sends the execution steps of the aforementioned operation 101 to the application. There is no particular order in terms of timing, and they can be executed simultaneously or sequentially. This application does not limit this.

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

[0211] Among them, this application does not limit the representation of message 2. For example, the split screen position (targetPosition) and the taskID of the Activity corresponding to page B can be passed using parameter params1. It should be noted that the taskID of the Activity corresponding to page B can be replaced with the ID of page B. This application does not limit this. It only needs to transmit the identifier used to represent page B. Among them, this 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 switching the task split screen position as an example, the instructions for calling the (invoke) interface can be expressed using the following code:

[0216] parameter:

[0217] function="magicwindow"

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

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

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

[0221] Return value:

[0222] easyGoRet.code=0 / / Call successful

[0223] Based on the above description, taking setting the window position as an example, the specific implementation of calling 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. The third-party interface layer (EasyGoSDK) can also obtain (e.g., actively query) the package name of the 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 (package name) of the application to the parallel window manager (HwMagicWindowManager) of the electronic device.

[0239] The package name (package name) of the application, the split-screen position (targetPosition) and the taskID of the Activity corresponding to page B can be transmitted using parameter params2.

[0240] based on Figure 2b The structure shown in the figure uses the policy module, configuration module, data management module, background layer drawing module, and animation module to implement the following process in the parallel window manager (HwMagicWindowManager):

[0241] The parallel window manager (HwMagicWindowManager) determines whether the method name (setTaskPosition) of the received method 1 and the content of params2 are empty. If the method name (setTaskPosition) of the 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 taskID of the activity corresponding to page B is the top activity of the current task stack (that is, determine whether the focus task stack exists). Then, the electronic device can ensure the existence of the current task stack when the activity corresponding to the taskID is the top activity 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 the in-application split-screen function based on the package name (packagename) of the application. Then, 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 split-screen display of multiple pages of the application.

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

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

[0247] The electronic device may store the package names of applications that support the in-app split-screen function in advance (e.g., by setting up a whitelist), or may obtain an identifier from each application's AndroidManifest.xml file to indicate whether the application supports the in-app split-screen function. This application does not limit this. Furthermore, based on the foregoing description, the electronic device may determine whether the application corresponding to the package name itself supports the in-app split-screen function.

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

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

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

[0251] When the electronic device displays page B in full screen, the preset requirements for split-screen display may indicate that page B can be displayed in split screen. For example, the value of targetPosition may be set to 1 or 2. Thus, when the electronic device needs to display page B in split screen from the full screen display, it may 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 moved position of page B meets the preset requirements for split-screen display.

[0252] When the electronic device displays page B in split screen, the preset requirements for split screen display may indicate that page B cannot be displayed in split screen and can be displayed in full screen. For example, the value of targetPosition may be set to 0. Thus, when the electronic device needs to display page B in full screen after the split screen is displayed, it may 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 step 11-1, step 11-2 and step 11-3 is not particular, and they can be executed sequentially or simultaneously, and this application does not limit this.

[0254] When the judgment results of step 11 - 1 , step 11 - 2 and step 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] Based on the split-screen position (targetPosition) and the taskID of the Activity corresponding to page B, the parallel window manager (HwMagicWindowManager) can determine the split-screen parameters of page B, such as the split-screen boundaries (bounds) and motion effects, or the split-screen parameters of pages A and B, such as the split-screen boundaries (bounds) and motion effects.

[0256] The parallel window manager (HwMagicWindowManager) displays two independent tasks on the left and right screens of the display at the same time 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. Figure 3A The A page shown in (3) 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.

[0257] Based on the above description, combined with Figure 3C , the implementation process of split-screen display of page A and page B in electronic devices is specifically explained.

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

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

[0260] S321. When the electronic device receives the user's operation 101 on page A, it creates a new Task (ie, a task stack different from the task stack corresponding to page A), starts the Activity corresponding to page B in the new Task, and displays page B.

[0261] S322 . When the electronic device receives the user's operation 102 on page B, it sends message 1 to the application. Message 1 is used to identify operation 102 .

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

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

[0264] S35. The third-party interface layer (EasyGoSDK) sends the method name of method 1 (called setTaskPosition), the split-screen position of page B (targetPosition), 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-application 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] S37. When the judgment results of S361, S362 and S363 are all yes, the parallel window manager (HwMagicWindowManager) determines the taskID of the activity corresponding to page A based on the package name of the application, and determines the split-screen parameters of page B based on the split-screen position (targetPosition) and the taskID of the activity corresponding to page B.

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

[0271] S38. The parallel window manager (HwMagicWindowManager) displays page A and page B simultaneously 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.

[0272] It should be noted that Figure 3C The specific implementation process shown in the example can be found in the above content and will not be repeated here.

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

[0274] The new Task is different from the Task corresponding to Page A. This means that the Activity corresponding to Page B enters a different Task from the Activity corresponding to Page A. For Control B, please refer to the previous description and will not be repeated here.

[0275] Furthermore, the electronic device may send a message 3 to the application, and the message 3 is used to identify the aforementioned operation 101. Then, in response to the aforementioned operation 101, the application may obtain the task ID (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 (called setTaskPosition) of method 1 for split-screen display within the application based on the aforementioned operation 101. Method 1 is used to indicate that page A and page B are split-screen displayed. This application does not limit the representation of message 3. For example, message 3 may be the reported point coordinates of the aforementioned operation 101.

[0276] Among them, the split-screen positions mentioned above can be found in the description of the split-screen positions mentioned above, and will not be repeated here.

[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 of method 1 for split-screen display within the application (called setTaskPosition).

[0278] It should be noted that the electronic device establishes a new Task execution step in response to operation 101, and the software system of the electronic device sends the execution steps of the aforementioned operation 101 to the application. There is no particular order in terms of timing, and they can be executed simultaneously or sequentially. This application does not limit this.

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

[0280] Among them, this application does not limit the representation of message 4. For example, the split screen position (targetPosition) and the taskID of the Activity corresponding to page B can be passed using parameter params1. It should be noted that the taskID of the Activity corresponding to page B can be replaced with the ID of page B. This application does not limit this. It only needs to transmit the identifier used to represent page B. Among them, this application does not limit this identifier.

[0281] 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. The third-party interface layer (EasyGoSDK) can also obtain (e.g., actively query) the package name of the application.

[0282] 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 (package name) of the application to the parallel window manager (HwMagicWindowManager) of the electronic device.

[0283] The package name (package name) of the application, the split-screen position (targetPosition) and the taskID of the Activity corresponding to page B can be transmitted using parameter params2.

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

[0285] Step 12-1, the parallel window manager (HwMagicWindowManager) can determine whether the task stack of the Activity corresponding to page A is in non-split-screen mode (that is, whether page A corresponding to the Activity is not in a split-screen display state) based on the package name (packagename) of the application. Among them, the parallel window manager (HwMagicWindowManager) can determine whether the number of task stacks corresponding to the page currently displayed by the electronic device is one to determine whether the task stack of the Activity corresponding to page A is in non-split-screen mode. Therefore, when it is determined that the number of task stacks corresponding to the page currently displayed by 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 non-split-screen mode.

[0286] Alternatively, the parallel window manager (HwMagicWindowManager) may obtain an indicator from the electronic device, wherein the indicator indicates whether the task stack of the activity corresponding to page A is in the non-split-screen mode. Thus, when the indicator indicates that the task stack corresponding to the activity is in the non-split-screen mode, the parallel window manager (HwMagicWindowManager) may determine that the task stack of the activity corresponding to page A is in the non-split-screen mode.

[0287] It should be noted that the present application is not limited to the aforementioned two implementation methods to determine whether the task stack of the Activity corresponding to page A is in non-split-screen mode.

[0288] Step 12-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 (packagename) of the application. Then, 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 split-screen display of multiple pages of the application.

[0289] The specific implementation of step 12-2 can be found in the description of step 11-2 and will not be repeated here.

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

[0291] The specific implementation of step 12-3 can be found in the description of step 11-3 and will not be repeated here.

[0292] In addition, the execution order of step 12-1, step 12-2 and step 12-3 is not specific, and they can be executed sequentially or simultaneously, and this application does not limit 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 the split-screen parameters of page B, such as the split-screen boundaries (bounds) and motion effects, or the split-screen parameters of pages A and B, such as the split-screen boundaries (bounds) and motion effects.

[0295] The parallel window manager (HwMagicWindowManager) displays two independent tasks on the left and right screens of the display at the same time 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. Figure 3A The A page shown in (3) 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.

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

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

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

[0299] S32', when the electronic device receives the user's operation 101 on page A, it creates a new Task (i.e., a task stack different from the task stack corresponding to page A), starts the Activity corresponding to page B in the new Task, and sends message 3 to the application, where message 3 is used to identify operation 101.

[0300] S33': In response to message 3, the application obtains the method name of method 1 (called setTaskPosition), the split-screen position of page B (targetPosition), and the taskID of the activity corresponding to page B.

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

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

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

[0304] S362. 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.

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

[0306] S37. When the judgment results of S361', S362 and S363 are all yes, the parallel window manager (HwMagicWindowManager) determines the taskID of the Activity corresponding to page A 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 taskID of the Activity corresponding to page B.

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

[0308] S38. The parallel window manager (HwMagicWindowManager) displays page A and page B simultaneously 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.

[0309] It should be noted that Figure 3D The specific implementation process shown in the example can be found in the above content and will not be described here in detail. Figure 3C and Figure 3D The difference is: Figure 3C Steps S321, S322-S33 and Figure 3D Steps S32'-S33', and Figure 3C Step S361 and Figure 3D Step S361′, the remaining steps are the same.

[0310] in addition, Figure 3C and Figure 3D The operation 101 is used to identify different meanings and can be operations of the same type or different types. Figure 3C Operation 101 in FIG. 1 is used to indicate a jump from displaying page A in one task stack to displaying page B in another task stack. Figure 3D Operation 101 in the example is used to indicate a jump from displaying page A in one task stack to simultaneously displaying page A in one task stack and page B in another task stack.

[0311] In other embodiments, after the electronic device detects the user's instruction to trigger operation 101 of control B in page A, if the launch mode (launchMode) of the Activity corresponding to page B is not set to singleInstance mode, page B is displayed, and the Activity corresponding to page A and the Activity corresponding to page B are both in the same task.

[0312] After the Activity corresponding to page B is started, the electronic device can display page B by default (i.e. Figure 3A In addition, page B includes a split-screen / full-screen control, which indicates 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.

[0313] After the electronic device detects the user's instruction to trigger the split-screen / full-screen control in page B, the electronic device may send a message 5 to the application. Message 5 is used to identify the aforementioned operation 102, so that the application can obtain the 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 aforementioned operation 102, and determine the method name of method 1 (called setTaskPosition) for split-screen display within the application based on the aforementioned operation 102. Method 1 is used to indicate that page A and page B are split-screen displayed. Among them, this application does not limit the representation method of message 5. For example, message 5 may include the reported point coordinates of the aforementioned operation 102.

[0314] Among them, the split-screen positions mentioned above can be found in the description of the split-screen positions mentioned above, and will not be repeated 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 taskID of the Activity corresponding to page A, the split-screen position of page B, and the method name of method 1 for split-screen display within the application (called setTaskPosition). Based on the description of the aforementioned embodiment, the application can call the call (invoke) interface in the third-party interface layer (EasyGoSDK) of the electronic device and transmit message 6, which carries the method name of method 1 (setTaskPosition), the split-screen position (targetPosition), and the taskID of the Activity corresponding to page A.

[0316] Among them, this application does not limit the representation of message 6. For example, the split screen position (targetPosition) and the taskID of the Activity corresponding to page A can be passed using parameter params1. It should be noted that the taskID of the Activity corresponding to page A can be replaced with the ID of page A. This application does not limit this. It only needs to transmit the identifier used to represent page A. Among them, this application does not limit this identifier.

[0317] 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 A. The third-party interface layer (EasyGoSDK) can also obtain (e.g., actively query) the package name of the application.

[0318] 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 A, and the package name (package name) of the application to the parallel window manager (HwMagicWindowManager) of the electronic device.

[0319] The package name (package name) of the application, the split-screen position (targetPosition) and the taskID of the Activity corresponding to page A can be transmitted using the parameter params2.

[0320] based on Figure 2b The structure shown in the figure uses the policy module, configuration module, data management module, background layer drawing module, and animation module to implement the following process in the parallel window manager (HwMagicWindowManager):

[0321] The parallel window manager (HwMagicWindowManager) determines whether the method name (setTaskPosition) of the received method 1 and the content of params2 are empty. If the method name (setTaskPosition) of the method 1 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 taskID is the current task stack based on the taskID of the Activity corresponding to page A, and then the electronic device can ensure the existence of the current task stack when the task stack corresponding to the taskID is the 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 the in-application split-screen function based on the package name (packagename) of the application. Then, 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 split-screen display of multiple pages of the application.

[0325] The specific implementation of step 13-2 can be found in the description of step 11-2 and will not be repeated here.

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

[0327] The specific implementation of step 13-3 can be found in the description of step 11-3 and will not be repeated here.

[0328] In addition, the execution order of step 13-1, step 13-2 and step 13-3 is not specific, and they can be executed sequentially or simultaneously, and this application does not limit this.

[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 (i.e., 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 is different from the Task corresponding to page A. It can be understood that 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 the split-screen parameters of page B, such as the split-screen boundaries (bounds) and motion effects, or the split-screen parameters of pages A and B, such as the split-screen boundaries (bounds) and motion effects.

[0332] The parallel window manager (HwMagicWindowManager) displays two independent tasks on the left and right screens of the display at the same time 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. Figure 3A The A page shown in (3) 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.

[0333] Based on the above description, combined with Figure 3E, the implementation process of split-screen display of page A and page B in electronic devices is specifically explained.

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

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

[0336] S521: When the electronic device receives the user's operation 101 on page A, it displays page B. The task stack corresponding to page B is the same as the task stack corresponding to page A. The activity corresponding to page B is started in the task stack to display page B.

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

[0338] S53 . In response to message 5 , the application obtains the method name of method 1 (called setTaskPosition ), the split-screen position of page B (targetPosition ), and the taskID of the activity corresponding to page A.

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

[0340] S55. The third-party interface layer (EasyGoSDK) sends the method name of method 1 (called setTaskPosition), the split-screen position of page B (targetPosition), 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] S562. 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.

[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 (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 taskID of the Activity corresponding to page B.

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

[0347] S58. The parallel window manager (HwMagicWindowManager) displays page A and page B simultaneously 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.

[0348] It should be noted that Figure 3E The specific implementation process shown in the example can be found in the above content and will not be described here in detail. Figure 3E and Figure 3C The difference is: Figure 3E The timing of establishing a new task stack in step S57 is the same as Figure 3C The timing of establishing a new task stack in S321, and Figure 3E The taskID of the Activity corresponding to the transferred A page is Figure 3C The taskID of the Activity corresponding to page B, and the rest of the steps are similar.

[0349] in addition, Figure 3C and Figure 3E The operation 101 is used to identify different meanings and can be operations of the same type or different types. Figure 3COperation 101 in FIG. 1 is used to indicate a jump from displaying page A in one task stack to displaying page B in another task stack. Figure 3E Operation 101 in FIG. 1 is used to indicate a jump from displaying page A in a task stack to displaying page B in the task stack.

[0350] In other embodiments, after the electronic device detects the user's instruction to trigger the operation 101 of the control B in page A, if the launch mode (launchMode) of the Activity corresponding to page B is not set to singleInstance mode, a message 7 can be sent to the application. Message 7 is used to identify the aforementioned operation 101. Then, in response to the aforementioned operation 101, the application can obtain the task ID (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 aforementioned operation 101, and determine the method name (called setTaskPosition) of method 1 for split-screen display within the application based on the aforementioned operation 101. Method 1 is used to indicate that page A and page B are to be split-screen displayed. Among them, this application does not limit the representation of message 7. For example, message 7 can be the reported point coordinates of the aforementioned operation 101.

[0351] The aforementioned split-screen positions can be found in the description of the aforementioned split-screen positions, which will not be repeated here. In summary, the software system of the electronic device sends the aforementioned 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 of method 1 (called setTaskPosition) for split-screen display within the application.

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

[0353] Among them, this application does not limit the representation of message 8. For example, the split screen position (targetPosition) and the taskID of the Activity corresponding to page A can be passed using parameter params1. It should be noted that the taskID of the Activity corresponding to page A can be replaced with the ID of page A. This application does not limit this. It only needs to transmit the identifier used to represent page A. Among them, this application does not limit this identifier.

[0354] 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 A. The third-party interface layer (EasyGoSDK) can also obtain (e.g., actively query) the package name of the application.

[0355] 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 A, and the package name (package name) of the application to the parallel window manager (HwMagicWindowManager) of the electronic device.

[0356] The package name (package name) of the application, the split-screen position (targetPosition) and the taskID of the Activity corresponding to page A can be transmitted using the parameter params2.

[0357] based on Figure 2b The structure shown in the figure uses the policy module, configuration module, data management module, background layer drawing module, and animation module to implement the following process in the parallel window manager (HwMagicWindowManager):

[0358] The parallel window manager (HwMagicWindowManager) determines whether the method name (setTaskPosition) of the received method 1 and the content of params2 are empty. If the method name (setTaskPosition) of the method 1 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 taskID is in non-split-screen mode (i.e., whether the page A corresponding to the activity is not in split-screen display) based on the taskID of the activity corresponding to page A.

[0360] The specific implementation of step 14-1 can be found in the description of step 12-1 and will not be repeated 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 (packagename) of the application. Then, 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 split-screen display of multiple pages of the application.

[0362] The specific implementation of step 14-2 can be found in the description of step 13-2 and will not be repeated here.

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

[0364] The specific implementation of step 14-3 can be found in the description of step 13-3 and will not be repeated here.

[0365] In addition, the execution order of step 14-1, step 14-2 and step 14-3 is not specific, and they can be executed sequentially or simultaneously, and this application does not limit 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 (i.e., 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 is different from the Task corresponding to page A. It can be understood that the Activity corresponding to page B enters a task different from the Activity corresponding to page A.

[0368] 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 the split-screen parameters of page B, such as the split-screen boundaries (bounds) and motion effects, or the split-screen parameters of pages A and B, such as the split-screen boundaries (bounds) and motion effects.

[0369] The parallel window manager (HwMagicWindowManager) displays two independent tasks on the left and right screens of the display at the same time 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. Figure 3A The A page shown in (3) 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.

[0370] Based on the above description, combined with Figure 3F , the implementation process of split-screen display of page A and page B in electronic devices is specifically explained.

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

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

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

[0374] S53': In response to message 7, the application obtains the method name of method 1 (called setTaskPosition), the split-screen position of page B (targetPosition), and the taskID of the activity corresponding to page A.

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

[0376] S55. The third-party interface layer (EasyGoSDK) sends the method name of method 1 (called setTaskPosition), the split-screen position of page B (targetPosition), the taskID 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 taskID of the Activity corresponding to page A is in non-split-screen mode (ie, whether 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 (packagename) 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 taskID of the Activity corresponding to page B.

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

[0382] S58. The parallel window manager (HwMagicWindowManager) displays page A and page B simultaneously 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.

[0383] It should be noted that Figure 3F The specific implementation process shown in the example can be found in the above content and will not be described here in detail. Figure 3E and Figure 3F The difference is: Figure 3E Steps S521, S522-S53 and Figure 3F Steps S52'-S53', and Figure 3E Step S561 and Figure 3F Step S561′, the remaining steps are the same.

[0384] in addition, Figure 3E and Figure 3C The difference is: Figure 3E The timing of establishing a new task stack in step S57 is the same as Figure 3C The timing of establishing a new task stack in S321, and Figure 3E The taskID of the Activity corresponding to the transferred A page is Figure 3C The taskID of the Activity corresponding to page B, and the rest of the steps are similar.

[0385] and, Figure 3C and Figure 3E The operation 101 is used to identify different meanings and can be operations of the same type or different types. Figure 3C Operation 101 in FIG. 1 is used to indicate a jump from displaying page A in one task stack to displaying page B in another task stack. Figure 3E Operation 101 in the example is used to indicate a jump from displaying page A in a task stack to displaying page B in the task stack. In summary, the launch mode (launchMode) of the Activity corresponding to page B has an impact on the timing of the electronic device's software system establishing a new task stack. In addition, the electronic device's software system sends a message to the application corresponding to the trigger operation of the split-screen control or a certain trigger operation of the user, which affects whether the application can call the third-party interface layer (EasyGoSDK) in the electronic device's software system.

[0386] 2. Exit the B page (corresponding to Figure 3B Step S121 or step S122 shown)

[0387] like Figure 3B As shown in (2) and (3), page B may also 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.

[0388] After detecting the user's instruction to trigger the return control 1 in the B page, the electronic device can exit the Activity corresponding to the B page, so that the electronic device can return to the displayed page. Figure 3B The user interface shown in (2) or (3) returns to the display Figure 3B The user interface shown in (1) is an example.

[0389] 3. Open a new page from the A page displayed on the left split screen. The new page will replace the A page displayed on the left split screen (corresponding to Figure 3A Step S131 or step S132 shown)

[0390] 31. Open page C1 from page A on the left split screen. Page C1 will replace page A on the left split screen (corresponding to Figure 3AStep S131 shown)

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

[0392] Among them, since the user performs operation 301 on page A, and page A is displayed in the left split screen, parameter policy1 is used to represent the strategy adopted when opening page C1 from page A displayed in the left split screen. Parameter policy1 can be represented in the form of numbers, strings, letters, etc.

[0393] Params3 may include but is not limited to: the token of the Activity corresponding to page A (ie, the focus Activity), the token of the Activity corresponding to page C1, and configuration parameters of the intent for starting the Activity corresponding to page C1.

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

[0395] Those skilled in the art will understand that an intent is an abstract description that provides direct interaction with an Activity and can be run by startActivity. Intents provide a medium for components to call each other, achieving decoupling between the caller and the callee. The configuration parameters of an intent, or the attribute settings within the intent, can include but are not limited to: action (typically the action to be performed), data (the data to be manipulated by the action; Android uses a URL pointing to the data. Different actions have different types of URL data), category (additional information about the action to be performed), type (the data type (MIME type) of the specified intent), component (the class name of the target component of the intent), and extras (a combination of all other additional information; extras can be used to provide extended information for components). Typically, the intent resolution mechanism primarily identifies matching intents by searching all intentFilters registered in the AndroidManifest.xml file and the intents defined therein. During this resolution process, the software system makes decisions based on the three attributes: action, type, and category. Therefore, the configuration parameters of an intent used to launch the activity corresponding to page C1 can actually launch the activity corresponding to page C1.

[0396] The parallel window manager (HwMagicWindowManager) can determine whether the task stack corresponding to the Activity is in split-screen mode (that is, whether the Page A corresponding to the Activity is in split-screen display state) based on the token of the Activity corresponding to the A page.

[0397] Among them, the parallel window manager (HwMagicWindowManager) can determine the task stack corresponding to the page currently displayed by 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 page A and the task stack corresponding to page B are different task stacks. Therefore, 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 the activity is in split-screen mode.

[0398] Alternatively, the parallel window manager (HwMagicWindowManager) may obtain an indicator from the electronic device, wherein the indicator indicates whether the task stack corresponding to the activity is in split-screen mode. Thus, when the indicator indicates that the task stack corresponding to the activity is in split-screen mode, the parallel window manager (HwMagicWindowManager) may determine that the task stack corresponding to the activity is in split-screen mode.

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

[0400] 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 C1 page based on the token of 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 the split-screen parameters of the C1 page, such as the split-screen boundaries and moving effects, so that the C1 page replaces the A page and is displayed in the left split screen of the electronic device, such as Figure 3A As shown in (41).

[0401] The activity corresponding to the C1 page can be set to any of the four launch modes. If the launch mode of the activity corresponding to the C1 page is set to singleInstance mode, the C1 page is launched as a newtask, and the split-screen boundaries of the C1 page can limit the window size of the C1 page.

[0402] 32. Open page B from page A on the left split screen, and page B will replace page A on the left split screen (corresponding to Figure 3A Step S132 shown)

[0403] After detecting the user-instructed operation 302 of triggering the control B in the A page, the electronic device may send parameters policy2 and params4 to the parallel window manager (HwMagicWindowManager).

[0404] Since the user performs operation 302 on page A, and page A is displayed in the left split screen, parameter policy2 is used to identify the policy to be adopted when opening page B from page A displayed in the left split screen. Parameter policy2 can be represented in the form of numbers, strings, letters, etc. params4 can include, but is 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 configuration parameters for the intent used to start the activity corresponding to page B.

[0405] 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 for starting the activity corresponding to page B are used to start the activity corresponding to page B.

[0406] The parallel window manager (HwMagicWindowManager) can determine whether the task stack corresponding to the Activity is in split-screen mode (that is, whether the Page A corresponding to the Activity is in split-screen display state) based on the token of the Activity corresponding to the A page.

[0407] Among them, the parallel window manager (HwMagicWindowManager) can determine the task stack corresponding to the page currently displayed by 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 page A and the task stack corresponding to page B are different task stacks. Therefore, 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 the activity is in split-screen mode.

[0408] Alternatively, the parallel window manager (HwMagicWindowManager) may obtain an indicator from the electronic device, wherein the indicator indicates whether the task stack corresponding to the activity is in split-screen mode. Thus, when the indicator indicates that the task stack corresponding to the activity is in split-screen mode, the parallel window manager (HwMagicWindowManager) may determine that the task stack corresponding to the activity is in split-screen mode.

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

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

[0411] in, Figure 3A The specific implementation of step S132 shown is the same as Figure 3A The step S131 shown is similar.

[0412] 41. Exit the C1 page displayed on the left split screen (corresponding to Figure 3B Step S141 shown)

[0413] like Figure 3B As shown in (41), the C1 page displayed on 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 C1 page display.

[0414] After detecting the user's instruction to trigger the operation 401 of the return control 2 in the C1 page, the electronic device can exit the Activity corresponding to the C1 page, so that the electronic device goes from displaying the Figure 3B The user interface shown in (41) returns to the display as shown in FIG. Figure 3B The user interface shown in (3) is an example.

[0415] 42. Exit the B page displayed on the left split screen (corresponding to Figure 3B Step S142 shown)

[0416] like 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 detecting the user's instruction to trigger the return control 3 in the B page, the electronic device can exit the activity corresponding to the B page in the left split screen, so that the electronic device returns to the page displayed as shown in FIG. Figure 3B The user interface shown in (42) returns to the display as shown in FIG. Figure 3B The user interface shown in (3) is an example.

[0418] 43. Exit the B page displayed on the right split screen (corresponding to Figure 3B Steps S161 and S162 shown)

[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 detecting the user's instruction to trigger the return control 1 operation 403 in the B page, the electronic device can exit the Activity corresponding to the B page in the right split screen, so that the electronic device goes from displaying the Figure 3B The user interface shown in (41) returns to the display as shown in FIG. Figure 3B (1) or (2) of the exemplary user interface, or, so that the electronic device from the display as shown Figure 3B The user interface shown in (42) returns to the display as shown in FIG. Figure 3B The user interface shown in (1) or (2) is exemplified.

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

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

[0423] Since the user performs operation 501 on page B, and page B is displayed in the right split screen, parameter policy3 is used to identify the policy to be adopted when opening page D from page B displayed in the right split screen. Parameter policy3 can be represented in the form of numbers, strings, letters, etc. params5 can include, but is 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 configuration parameters for the intent used to start the activity corresponding to page D.

[0424] 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 for starting the activity corresponding to page D are used to start the activity corresponding to page D.

[0425] The parallel window manager (HwMagicWindowManager) can determine whether the task stack corresponding to the Activity is in split-screen mode (that is, whether the B page corresponding to the Activity is in split-screen display state) based on the token of the Activity corresponding to the B page.

[0426] Among them, the parallel window manager (HwMagicWindowManager) can determine the task stack corresponding to the page currently displayed by 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 page A and the task stack corresponding to page B are different task stacks. Therefore, 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 the activity is in split-screen mode.

[0427] Alternatively, the parallel window manager (HwMagicWindowManager) may obtain an indicator from the electronic device, wherein the indicator indicates whether the task stack corresponding to the activity is in split-screen mode. Thus, when the indicator indicates that the task stack corresponding to the activity is in split-screen mode, the parallel window manager (HwMagicWindowManager) may determine that the task stack corresponding to the 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 (bounds) and the moving animation, 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. If the launch mode of the activity corresponding to the D page is set to singleInstance mode, the D page is launched as a newtask, and the split-screen boundaries of the D page can limit the size of the D page window.

[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 detecting the user's instruction to trigger the return control 4 in the D page, the electronic device can exit the Activity corresponding to the D page, so that the electronic device can return to the displayed page. Figure 3B The user interface shown in (5) is returned to the display Figure 3B The user interface shown in (4) is an example.

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

[0436] 1) In response to an operation triggered by a user, the electronic device may switch from displaying page A in full screen to displaying page A and page B in split screen.

[0437] 2) When pages A and B are displayed in split screen, if page C1 is opened from page A, page C1 will destroy page A and display in the area where page A is displayed, without destroying page B.

[0438] 3) When pages A and B are displayed in split screen, if page D is opened from page B, page D will destroy page B and be displayed in the area where page B is displayed, without destroying page A.

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

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

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

[0442] Thus, when the user processes multiple tasks in parallel, the electronic device can cut 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 on the split screen and be displayed in the split screen, which solves the phenomenon in the related art that the new page opened in any split screen will destroy the pages displayed on other split screens due to the coupling relationship between different split screens, avoids the display interference between pages in different split screens, and enables pages in different split screens to run independently, providing users with a multi-tasking or immersive experience. In addition, after the application starts the in-application split-screen function, 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 based on user needs, providing users with an efficient and flexible multi-window multi-tasking experience.

[0443] based on Figure 3A-3F The description shown, combined with Figures 4A-4L , introduces the specific implementation process of electronic devices to complete the split-screen display of multiple pages of any application. For the sake of explanation, Figures 4A-4LIn the figure, the electronic device is a tablet computer, the application is the WeChat application, page A is a chat dialog list, page a0 includes the WeChat application icon set in the center, page a1 is a specific chat dialog window, page B is the main page of the XX video browsing webpage / XX video applet in the WeChat application, and the launch mode (launchMode) of page B is set to 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] See also Figures 4A-4L , Figures 4A-4L A schematic diagram of a human-computer interaction interface provided in one embodiment of the present application.

[0445] The tablet can display Figure 4A User interface 11 is shown as an example. User interface 11 may be the home screen of a desktop. User interface 11 may include, but is not limited to, a status bar, a navigation bar, a calendar indicator, a weather indicator, and multiple application icons. Application icons include at least WeChat application icon 401 and may also include icons for calculators, Huawei Video, browsers, cameras, music, settings, email, and memos.

[0446] After detecting the user's instruction to open the WeChat application (such as clicking the WeChat application icon 401), the tablet computer may display Figure 4B The user interface 12a and user interface 12b are shown as examples, with user interface 12a displayed on the left split screen and user interface 12b displayed on the right split screen. User interface 12a can be used to display the main page (i.e., page A) of the WeChat application. User interface 12b can be used to display the secondary page (i.e., page a0) of the WeChat application.

[0447] The display areas of the user interfaces 12a and 12b may be the same or different, and this application does not impose any restrictions thereon. Furthermore, an operation button for adjusting the display areas of the user interfaces 12a and 12b may be provided in the overlapping boundary area of ​​the user interfaces 12a and 12b, so that the display areas of the user interfaces 12a and 12b can be adjusted in real time based on user needs.

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

[0449] The tablet detects that the user is Figure 4B After performing an operation such as clicking the search control 402 in the user interface 12a shown in FIG. 1 , the left split screen can be used to display the search results. Figure 4B The user interface 12a shown as an example becomes a display Figure 4C The user interface 13a shown as an example. Among them, the user interface 13a can be an interface for searching for searchable content in the WeChat application. In addition, the tablet computer can continue to display the right split screen. Figure 4C The user interface 12b is shown as an example.

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

[0451] It should be noted that, in addition to the user clicking Figure 4B In addition to providing the user with a way to search for the XX video webpage / XX video mini-program, the tablet computer may, upon detecting a user-directed operation such as a pull-down and long-press operation in the user interface 12a, display the mini-program interface, thereby providing the user with a way to search for the XX video webpage / XX video mini-program. Alternatively, upon detecting a user-directed operation such as a click operation on the address book icon in the user interface 12a, the tablet computer may display a search box, thereby providing the user with a way to search for the XX video webpage / XX video mini-program. This application does not limit the method for searching for the XX video webpage / XX video mini-program.

[0452] The tablet detects that the user is Figure 4C After the input operation is performed in the search box 403 in the user interface 13a shown in the figure, the left split screen can be used to select the search box 403 in the left split screen. Figure 4C The user interface 13a shown as an example becomes a display Figure 4D The user interface 14a is shown as an example. The user interface 14a is used to display the search results 404 of the XX video webpage / XX video applet. In addition, the tablet computer can continue to display the Figure 4D The user interface shown is exemplarily user interface 12b.

[0453] The search box 403 is used to search for searchable content in the WeChat application. The input operation performed by the user in the search box 403 in the user interface 13a may include text input, voice input or video input. For example, Figure 4DAs shown, the user enters the text XX video in the search box 403, and the tablet computer can search for the XX video webpage / XX video applet and display the search results 404 of the XX video webpage / XX video applet.

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

[0455] The tablet detects that the user is Figure 4D After clicking on the text XX video in the search result 404, the following information will be displayed: Figure 4E The user interface 15 shown as an example is used to display the main page of the XX video webpage / XX video applet (i.e., page B, and the task stack corresponding to page B is a newly created task stack, which is different from the task stack corresponding to page A).

[0456] It should be noted that, from Figure 4B-4D All operations that the user triggers to display the B page can be regarded as the user triggering the corresponding control B on page A. Figure 3C Operation 101 in.

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

[0458] Among them, the multi-function control 405 is used to enter the window of the XX video webpage / XX video applet with functions such as sharing, removal, split screen / full screen display, floating window display, settings, feedback and complaints, and re-entry.

[0459] Among them, the return control 406 is used to exit the XX video webpage / XX video applet, so that the tablet computer returns from the current user interface (such as user interface 15 and user interface 16b, user interface 18b and user interface 19 mentioned later) and displays Figure 4B The user interface 12a and the user interface 12b are shown as examples. The return control 406 here can be seen as Figure 3A and Figure 3B Return control 1 in .

[0460] The tablet detects that the user is Figure 4E After performing an operation such as clicking the multi-function control 405 in the user interface 15 shown in FIG. 1 , the user interface 15 may display Figure 4F The window 407 shown as an example includes at least: a control 4071.

[0461] Among them, window 407 can be a window for the XX video browsing webpage / XX video applet with functions such as sharing, removal, split-screen / full-screen display, floating window display, settings, feedback and complaints, and re-entry, and is used to display the XX video webpage / XX video applet with functions such as sharing, removal, split-screen / full-screen display, floating window display, settings, feedback and complaints, and re-entry.

[0462] Among them, the control 4071 is used to realize the split-screen display of page B, which can be represented by icons and / or text. For example, Figure 4F Control 4071 in the text "Show in split screen" and the icon Here, the control 4071 can be seen as Figure 3A and Figure 3B The operation of clicking the multi-function control 405 here can be regarded as Figure 3C The operation 101 in the example, the operation of clicking the control 4071 here can be regarded as Figure 3C It should be noted that the control 4071 can also be displayed in the window 407, without being displayed by an operation such as clicking the multi-function control 405.

[0463] The tablet detects the user's instruction Figure 4F After performing an operation such as clicking the control 4071 in the window 407 shown, the Figure 4G User interface 16a and user interface 16b are shown as examples, with user interface 16a displayed on the left split screen and user interface 16b displayed on the right split screen. User interface 16a is used to display the main page of the WeChat application (i.e., page A). User interface 16b is used to display page B with the XX video webpage / XX video mini-program.

[0464] The display areas of user interface 16a and user interface 16b may be the same or different, and this application does not impose any restrictions thereon. The display positions of user interface 16a and user interface 16b may be interchangeable, i.e., user interface 16a is displayed on the right split screen, and user interface 16b is displayed on the left split screen. In addition, a control for adjusting the display areas of user interface 16a and user interface 16b may be provided in the overlapping boundary area of ​​user interface 16a and user interface 16b, so as to adjust the display areas of user interface 16a and user interface 16b in real time based on user needs.

[0465] It should be noted that, in addition to the above methods, the tablet computer can detect that the user is Figure 4D After clicking on the text XX video in the search result 404, the video will be displayed. Figure 4G The user interface 16a and the user interface 16b are shown as examples, and the user interface 16a is displayed on the left split screen and the user interface 16b is displayed on the right split screen. Figure 4E-4F The description of the embodiment shown is an optional step. The operation of clicking the text XX video here can be regarded as Figure 3D Operation 101 in.

[0466] Therefore, 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 webpage / XX video applet in the WeChat application in the right split screen, so that the user can perform operations such as clicking, sliding, and long pressing on page A and page B, and simultaneously realize functions such as content browsing, video watching, and instant chatting, thereby improving the user experience.

[0467] In summary, Figure 4A-4G As described in 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, i.e., A on the left and B on the right.

[0468] It should be noted that according to Figure 4A-4G According to the description of the embodiment shown, the electronic device can jump from the left split screen displaying page A to the left split screen displaying page B, and the right split screen continues to display page B, thereby completing the in-application split screen function of the WeChat application. Among them, the left split screen displaying page B can also include a return control, wherein the return control is used to exit the page B displayed on the left split screen, so that the tablet computer returns from the current user interface and displays Figure 4G The user interface 16a and the user interface 16b are shown as examples. The return control here can be seen as Figure 3A and Figure 3B The return control 3 in the right split screen is different from the return control 406 in the B page.

[0469] The tablet detects that the user is Figure 4G After performing an operation such as clicking the control 408 in the user interface 16a shown in FIG. 1 , the left split screen can be used to display the Figure 4G The user interface 16a shown as an example changes to display Figure 4H The user interface 17a is shown as an example, wherein the user interface 17a can be a page for the chat dialogue between the user and Xiaoyi (i.e., C1 page), thereby facilitating the user to browse the XX video webpage / XX video applet page while chatting with Xiaoyi on WeChat. In addition, the tablet computer can continue to display the right split screen. Figure 4H User interface 16b is shown as an example.

[0470] Among them, the control 408 is used to enter the page of the chat dialogue between the user and xiaoyi (i.e., C1 page). This application does not limit the specific implementation of the control 408. In addition, the user interface 17a also includes at least a return control 410 ( Figure 4H 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 Figure 4G The user interface 16a shown as an example facilitates the user to use other functions of the WeChat application. The return control 410 here can be seen as Figure 3A and Figure 3B Return control 2 in .

[0471] In summary, Figure 4G-4H In the illustrated embodiment, when the electronic device displays pages A and B in a split-screen display, a new page opened from page A can replace page A for display, rather than replacing page B. This enables independent and separate display of multiple pages in the application's left and right split-screens, preventing interference between the multiple pages within the application, i.e., clicking left and displaying left. Furthermore, the electronic device can return to page A from the new page, ensuring independent left and right tasks.

[0472] The tablet detects that the user is Figure 4G After performing an operation such as clicking on the control 409 in the user interface 16b shown in FIG. 16b, the user can select the display Figure 4G The user interface 16b shown in the example becomes a display Figure 4I The user interface 18b is shown as an example, wherein the user interface 18b can be a page of video 1 (ie, D page), thereby facilitating the user to use the WeChat application while watching video 1. In addition, the tablet computer can continue to display the video in the left split screen. Figure 4I The user interface 16a is shown as an example.

[0473] Among them, the control 409 is used to enter the page of video 1 (ie, D page). This application does not limit the specific implementation of the control 409. In addition, the user interface 17a also includes at least a return control 411 ( Figure 4I 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 user interface 16b shown in the example facilitates the user to use the XX video to browse the web page / XX video applet other functions. The return control 411 here can be seen as Figure 3A and Figure 3B Return control 4 in .

[0474] It should be noted that the tablet computer detects that the user is Figure 4H After performing an operation such as clicking the control 409 in the user interface 16b shown in FIG. 16b, the user can select the display Figure 4H The user interface 16b shown in the example becomes a display Figure 4I The user interface 18b shown in the example, wherein the user interface 18b can be the page of video 1 (ie, D page), thereby facilitating the user to chat with xiaoyi while watching video 1. In addition, the tablet computer can continue to display the left split screen. Figure 4I The user interface 17a is shown as an example. The above method is another feasible implementation method for a user to watch the video 1 on a tablet computer.

[0475] In summary, Figure 4G and Figure 4I In the illustrated embodiment, when the electronic device displays pages A and B in a split-screen display, a new page opened from page B can replace page B for display, rather than replacing page A. This enables independent and separate display of multiple pages in the application's split-screen display, preventing interference between the multiple pages within the application, similar to the "right click, right exit" approach. Furthermore, the electronic device can return to page B from the new page, ensuring independent left and right tasks.

[0476] The tablet detects that the user is Figure 4I After performing an operation such as clicking the multi-function control 405 in the user interface 18b shown in FIG. 1 , the user interface 18b may display Figure 4J The window 407 shown as an example includes at least: a control 4072.

[0477] The specific implementation of window 407 can be found in Figure 4F The description of the embodiment shown is not repeated here. Control 4072 is used to realize full screen display of page B, which can be represented by icons and / or text. For example, Figure 4JControl 4072 in the text "Exit split screen display / switch to full screen display" and icon Here, the control 4072 can be seen as Figure 3A and Figure 3B It should be noted that the control 4072 can also be displayed in the window 407, without having to be displayed by an operation such as clicking the multi-function control 405.

[0478] It should be noted that controls 4071 and 4072 are typically not displayed simultaneously in window 407, and are switched between display in the same area of ​​window 407. When page B is displayed full screen, the tablet computer may display control 4071 in window 407, thereby facilitating the user's switching from full-screen to split-screen display of page B. When page B is displayed split screen, the tablet computer may display control 4072 in window 407, thereby facilitating the user's switching from split-screen to full-screen display of page B.

[0479] The tablet detects that the user is Figure 4J After the operation of clicking the control 4072 is executed in the window 407 shown, the Figure 4K The user interface 19 is shown as an example, wherein the user interface 19 is used to display the B page of the XX video webpage / XX video applet in full screen, thereby facilitating the user to watch the video 1 in full screen.

[0480] In summary, Figure 4I-4K As described in the illustrated embodiment, the electronic device can realize the transition of video 1 from split-screen display to full-screen display.

[0481] The tablet detects that the user is Figure 4K After performing an operation such as clicking the multi-function control 405 in the user interface 19 shown in FIG. 1 , the user interface 19 may display Figure 4L The window 407 shown as an example includes at least: a control 4071.

[0482] The specific implementation of the window 407 and the control 4071 can be found in Figure 4F or Figure 4J The description of the illustrated embodiment is omitted here.

[0483] The tablet detects that the user is Figure 4L After the operation of clicking the control 4071 is executed in the window 407 shown, the Figure 4I The exemplary user interface 16a and user interface 18b make it convenient for the user to run the WeChat application while watching the video 1.

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

[0485] based on Figure 3A-3B The description shown, combined with Figure 4A 、 Figure 4M-4W , introduces the specific implementation process of electronic devices to complete the split-screen display of multiple pages of any application. For the sake of explanation, Figure 4A 、 Figure 4M-4W In the figure, the electronic device is a tablet computer, the application is the WeChat application, page A is a chat dialog box list, page a0 includes the WeChat application icon set in the center, page a1 is the main page of the XX express cabinet public account in the WeChat application, page a2 is any page of the XX express cabinet public account in the WeChat application except the main page of the XX express cabinet public account, page B is any page of the XX express cabinet public account in the WeChat application except the main page of the XX express cabinet public account, and the launch mode (launchMode) of page B is not set to singleInstance mode, page C1 is page a1, and page D is any page of the XX express cabinet public account in the WeChat application except the main page of the XX express cabinet public account.

[0486] See also Figure 4A 、 Figure 4M-4W , Figure 4M-4W A schematic diagram of a human-computer interaction interface provided in one embodiment of the present application.

[0487] The tablet can display Figure 4A The user interface 11 shown in the example. After detecting the user's instruction to open the WeChat application (such as clicking the WeChat application icon 401), the tablet computer can display Figure 4M The user interface 12a and user interface 12b are shown as examples, with user interface 12a displayed on the left split screen and user interface 12b displayed on the right split screen. User interface 12a can be used to display the main page (i.e., page A) of the WeChat application. User interface 12b can be used to display the secondary page (i.e., page a0) of the WeChat application.

[0488] The detailed description of the user interface 11 can be found in the above description, and the detailed description of the user interface 12a and the user interface 12b can be found in the above description. Figure 4B This is an exemplary description and will not be repeated here.

[0489] The tablet detects that the user is Figure 4M After performing an operation such as clicking the search control 412 in the user interface 12a shown in FIG. 1 , the search result can be displayed in the right split screen. Figure 4M The user interface 12b shown in the example becomes a display Figure 4NThe user interface 41b is shown as an example. The user interface 41b can be used to display the main page (i.e., page a1) of the XX Express Cabinet public account in the WeChat application. In addition, the tablet computer can continue to display the left split screen. Figure 4N The user interface 12a is shown as an example. The user interface 41b includes at least: a control 413 ( Figure 4N A human-like pattern is used as an example), return control 414 ( Figure 4N The control 413 is used to realize the display of page B. The specific implementation of the control 413 is not limited in this application. The return control 414 is used to exit the XX express cabinet public account, so that the tablet computer can return from the user interface 41b and display Figure 4M The exemplary user interface 12b is used to facilitate users to use other functions of the WeChat application.

[0490] It should be noted that, in addition to the user clicking Figure 4M In addition to the way in which the search control 412 shown provides the user with the main page of the XX express cabinet official account, the tablet computer can display a search box after detecting that the user has performed an operation such as a click on the search button on the main page shown in the user interface 12, thereby providing the user with a way to search for the XX express cabinet official account. Alternatively, the tablet computer can display a search box after detecting that the user has performed an operation such as a click on the address book icon in the user interface 12a, thereby providing the user with a way to search for the XX express cabinet official account. This application does not limit the way to search for the XX express cabinet official account.

[0491] The tablet detects that the user is Figure 4N After performing an operation such as clicking the control 413 in the user interface 41b shown, the display Figure 4N The user interface 41b shown in the example becomes a display Figure 4O The user interface 42b is shown as an example. The user interface 42b is used to display any interface (i.e., page a2) of the XX Express Cabinet public account in the WeChat application except the main page. In addition, the tablet computer can continue to display the left split screen. Figure 4O The user interface 12a is shown as an example.

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

[0493] In addition, the user interface 42b may further 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 official 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 Figure 4M-Figure 4O All operations that the user triggers to display the B page can be regarded as the user triggering the corresponding control B on page A. Figure 3E Operation 101 in.

[0496] The user interface 43 includes at least: 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, favorite, 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 FIG. 4 , the user interface 43 may display Figure 4Q The window 419 shown as an example includes at least: a control 4191.

[0500] Among them, window 419 can be a window of the B page of the XX express cabinet official account with functions such as sending to friends, split screen to friends circle, reading, favorite, opening in browser, split screen / full screen display, floating window display, complaint, copy link, refresh, search page content, full text translation, font adjustment, etc., which is used to display the B page of the XX express cabinet official account with functions such as sending to friends, split screen to friends circle, reading, favorite, opening in browser, split screen / full screen display, floating window display, complaint, copy link, refresh, search page content, full text translation, font adjustment, etc.

[0501] Among them, the control 4191 is used to realize the split-screen display of page B, which can be represented by icons and / or text. For example, Figure 4Q The control in 4191 is displayed with the text "Show in Split Screen" and the icon Here, the control 4191 can be seen as Figure 3A and Figure 3B The split screen / full screen control in the . Clicking the multi-function control 417 here can be seen as Figure 3E The operation 101 in the example, the operation of clicking the control 4191 here can be seen as Figure 3E It should be noted that the control 4191 can also be displayed in the window 419 without being displayed through an operation such as clicking the multi-function control 417.

[0502] The tablet detects the user's instruction Figure 4Q After performing an operation such as clicking the control 4191 in the window 419 shown, the Figure 4R The user interface 44a and user interface 44b are shown as examples, with user interface 44a displayed on the left split screen and user interface 44b displayed on the right split screen. Among them, user interface 44a is used to display the main page (i.e., page A) of the WeChat application. User interface 44b is used to display page B of the XX Express Cabinet official account in the WeChat application in addition to the main page. 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.

[0503] The display areas of user interface 44a and user interface 44b may be the same or different, and this application does not impose any restrictions thereon. The display positions of user interface 44a and user interface 44b may be interchangeable, i.e., user interface 44a is displayed on the right split screen, and user interface 44b is displayed on the left split screen. In addition, a control for adjusting the display areas of user interface 44a and user interface 44b may be provided in the overlapping boundary area of ​​user interface 44a and user interface 44b, so as to adjust the display areas of user interface 44a and user interface 44b in real time based on user needs.

[0504] It should be noted that, in addition to the above methods, the tablet computer can detect 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 4R The user interface 44a and the user interface 44b are shown as examples, and the user interface 44a is displayed on the left split screen and the user interface 44b is displayed on the right split screen. Figure 4P-Figure 4Q The description of the embodiment shown is an optional step. The operation of clicking the control 415 here can be regarded as Figure 3F Operation 101 in.

[0505] Therefore, 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 express cabinet public account in the WeChat application in the right split screen, so that the user can perform operations such as clicking, sliding, and long pressing on pages A and B, and simultaneously realize functions such as content browsing, video watching, and instant chatting, thereby improving the user experience.

[0506] In summary, Figure 4A 、 Figure 4M-4R As described in 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, i.e., A on the left and B on the right.

[0507] The tablet detects that the user is Figure 4R After performing an operation such as clicking the control 420 in the user interface 44a shown, the left split screen can be used to display Figure 4R The user interface 14a shown as an example changes to display Figure 4S The user interface 45a is shown as an example, wherein the user interface 45a can be a page for the chat conversation between the user and Xiaoyi (i.e., C1 page), thereby facilitating the user to browse the B page while chatting with Xiaoyi on WeChat. In addition, the tablet computer can continue to display the right split screen. Figure 4S User interface 44b is shown as an example.

[0508] The specific implementation of the user interface 45a can be found in Figure 4G The description of the user interface 16a shown in FIG. 4 and the specific implementation of the control 420 can be found in FIG. Figure 4G The description of the control 408 in the user interface 16a is not repeated here.

[0509] In summary, Figure 4R-4SIn the illustrated embodiment, when the electronic device displays pages A and B in a split-screen display, a new page opened from page A can replace page A for display, rather than replacing page B. This enables independent and separate display of multiple pages in the application's left and right split-screens, preventing interference between the multiple pages within the application, i.e., clicking left and displaying left. Furthermore, the electronic device can return to page A from the new page, ensuring independent left and right tasks.

[0510] The tablet detects that the user is Figure 4R After performing an operation such as sliding upward in the user interface 44b shown, the user can select the display Figure 4R The exemplary user interface 44b is changed to display Figure 4T The user interface 46a shown as an example, wherein the user interface 46a can be used to display any page (i.e., D page) of the XX Express Cabinet public account in the WeChat application except the main page, thereby facilitating the user to browse the D page while using the WeChat application. In addition, the tablet computer can continue to display the right and left split screens. Figure 4T User interface 44b is shown as an example.

[0511] In addition, the tablet detects that the user is Figure 4T After performing an operation such as sliding down in the user interface 46b shown, the user interface 46b can be returned to and displayed. Figure 4R The user interface 44b shown in the example is convenient for the user to review page B. The operation of sliding down here can be regarded as Figure 3A and Figure 3B Return control 4 in .

[0512] It should be noted that the tablet computer detects that the user is Figure 4S After performing an operation such as sliding upward in the user interface 44b shown, the user can select the display Figure 4S The exemplary user interface 44b is changed to display Figure 4T The user interface 46b is shown as an example, wherein the user interface 46a can be used to display any page (i.e., D page) of the XX Express Cabinet public account in the WeChat application except the main page, thereby facilitating the user to browse the D page while using the WeChat application. In addition, the tablet computer can continue to display the left split screen. Figure 4S The user interface 45a is shown as an example. The above method is another feasible implementation method for a user to browse D pages on a tablet computer.

[0513] In summary, Figure 4R and Figure 4TIn the illustrated embodiment, when the electronic device displays pages A and B in a split-screen display, a new page opened from page B can replace page B for display, rather than replacing page A. This enables independent and separate display of multiple pages in the application's split-screen display, preventing interference between the multiple pages within the application, similar to the "right click, right exit" approach. Furthermore, the electronic device can return to page B from the new page, ensuring independent left and right tasks.

[0514] The tablet detects that the user is Figure 4T After performing an operation such as clicking the multi-function control 417 in the user interface 46b shown in FIG. 4 , the user interface 46b may display Figure 4U The window 419 shown as an example includes at least: a control 4192.

[0515] The specific implementation of window 419 can be found in Figure 4Q The description of the embodiment shown is not repeated here. Control 4192 is used to realize full screen display of page B, which can be represented by icons and / or text. For example, Figure 4U Control 4192 in the text "Exit split screen display / switch to full screen display" and icon Here, the control 4192 can be seen as Figure 3A and Figure 3B It should be noted that the control 4192 can also be displayed in the window 419 without being displayed by an operation such as clicking the multi-function control 417.

[0516] It should be noted that controls 4191 and 4192 are typically not displayed simultaneously in window 419, and are switched between display in the same area of ​​window 419. When page B is displayed full screen, the tablet computer may display control 4191 in window 419, thereby facilitating the user's switching from full-screen to split-screen display of page B. When page B is displayed split screen, the tablet computer may display control 4192 in window 419, thereby facilitating the user's switching from split-screen to full-screen display of page B.

[0517] The tablet detects that the user is Figure 4U After the operation of clicking the control 4192 is executed in the window 419 shown, the Figure 4V The user interface 47 is shown as an example, wherein the user interface 47 is used to display the D page of the XX express cabinet public account in full screen, thereby facilitating users to browse the D page in full screen.

[0518] In summary, Figure 4T-Figure 4V As described in the illustrated embodiment, the electronic device can realize the transition of the D page from split-screen display to full-screen display.

[0519] The tablet detects that the user is Figure 4V After performing an operation such as clicking the multi-function control 417 in the user interface 47 shown in FIG. 4 , 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 the window 419 and the control 4191 can be found in Figure 4Q or Figure 4U The description of the illustrated embodiment is omitted 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, the 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 official account while running the WeChat application.

[0522] In summary, Figure 4V 、 Figure 4W 、 Figure 4T As described in the illustrated embodiment, the electronic device can implement the D page from full-screen display to split-screen display.

[0523] based on Figures 4A-4L ,as well as Figure 4A 、 Figure 4M-4W As described in the embodiments, for various forms of pages in the WeChat application, such as browsing web pages, mini-programs, and official accounts, electronic devices can display multiple pages of the WeChat application in split-screen display, realizing the WeChat application's in-app split-screen function. Therefore, 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 has triggered control B on page A. In Scenario 2, the electronic device detects that the user has triggered control B on page a1. The difference between Scenario 1 and Scenario 2 is that control B is located on different pages, causing the electronic device to implement different pages for the split-screen display of the application.

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

[0527] See also Figures 5A-5F , Figures 5A-5F This is a flow chart of an application implementing split-screen display in an embodiment of the present application. Figure 5A It shows the process from the current page display to the next page of the application. Figure 5Bshows the process of returning from the current page of the application to the previous page, and Figure 5A-5B The display page is the same as in .

[0528] 0. Display of a1 page

[0529] When the electronic device is in landscape mode, the display screen of the electronic device may display the following Figure 5A The interface shown in (1a) includes page A and page a1.

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

[0531] Among them, the a1 page can be displayed in full screen, such as Figure 5A As shown in (1b), it can also 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 (such as Figure 5A (1c)) or the A page and the a1 page are displayed in a split screen (as shown in Figure 5A (1a) of the present application), the display mode of the a1 page is not limited, and 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, the second scenario adopts the following Figure 5A The example in which the A page shown in (1a) is displayed in the left split screen and the a1 page is displayed in the right split screen is used for illustration.

[0532] In some embodiments, the a1 page displayed on the interface may also include a return control 02 ( Figure 5A (not shown in the figure) indicates that the user can trigger the return control 02 from the a1 page. The return control 02 is used to trigger the exit of the a1 page or the entry of the main page of the application (i.e., the A page). 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 the A page, so that the display screen of the electronic device displays the A page. Alternatively, 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.

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

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

[0535] The new task is different from the task corresponding to page a1. This means that the activity corresponding to page B enters a different task from the activity corresponding to page a1. For control B, please refer to the previous description and will not be repeated here.

[0536] After the Activity corresponding to page B is started, the electronic device can display page B by default (i.e. Figure 5A In addition, page B includes a split-screen / full-screen control, which indicates 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.

[0537] After the electronic device detects the user-instructed operation 702 to trigger the split-screen / full-screen control in page B, it can send a message 9 to the application. Message 9 is used to identify the aforementioned operation 702, 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 702, and determine the method name of method 2 (called setTaskPosition) for split-screen display within the application based on the aforementioned operation 702. Method 2 is used to indicate that page a1 and page B are split-screen displayed. Among them, this application does not limit the representation method of message 9. For example, message 9 can be the reported point coordinates of the aforementioned operation 702.

[0538] Among them, the split-screen positions mentioned above can be found in the description of the split-screen positions in scene one, and will not be repeated here.

[0539] In summary, the software system of the electronic device notifies the application of the aforementioned operation 702, 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 of method 2 for split-screen display within the application (called setTaskPosition).

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

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

[0542] Among them, this application does not limit the representation of message 10. For example, the split screen position (targetPosition) and the taskID of the Activity corresponding to page B can be passed using parameter params6. The definition of the invoke interface can be found in the description of scenario one and will not be repeated here. It should be noted that the taskID of the Activity corresponding to page B can be replaced with the ID of page B. This application does not limit this. It only needs to transmit the identifier used to represent page B. Among them, this application does not limit 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 taskID of the activity corresponding to page B. The third-party interface layer (EasyGoSDK) can also obtain (e.g., actively query) 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 taskID of the Activity corresponding to page B, and the package name (package name) of the application to the parallel window manager (HwMagicWindowManager) of the electronic device.

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

[0546] based on Figure 2bThe structure shown in the figure uses the policy module, configuration module, data management module, background layer drawing module, and animation module to implement the following process in the parallel window manager (HwMagicWindowManager):

[0547] The parallel window manager (HwMagicWindowManager) can determine whether the method name (setTaskPosition) of method 2 and the content of params7 are empty. If 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 determine whether the activity corresponding to the taskID is the top activity of the current task stack (i.e., determine whether the focus task stack exists) based on the taskID of the activity corresponding to page B. Then, the electronic device can ensure the existence of the current task stack when the activity corresponding to the taskID is the top activity of the current task stack.

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

[0550] Step 21-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 (packagename) of the application. Then, 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 split-screen display of multiple pages of the application.

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

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

[0553] The electronic device may store the package names of applications that support the in-app split-screen function in advance (e.g., by setting up a whitelist), or may obtain an identifier from each application's AndroidManifest.xml file to indicate whether the application supports the in-app split-screen function. This application does not limit this. Furthermore, based on the foregoing description, the electronic device may determine whether the application corresponding to the package name itself supports the in-app split-screen function.

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

[0555] Step 21-3, the parallel window manager (HwMagicWindowManager) can determine whether the moving position of page B meets the preset requirements of split-screen display (for example, secondary screen (such as right split screen) or full screen, such as determining whether the value of targetPosition is 1 or 2) based on the split-screen position (targetPosition). Then, when the moving position of page B meets the preset requirements of 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 (ie, split-screen or full-screen display).

[0557] When the electronic device displays page B in full screen, the preset requirements for split-screen display may indicate that page B can be displayed in split screen. For example, the value of targetPosition may be set to 1 or 2. Thus, when the electronic device needs to display page B in split screen from the full screen display, it may 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.

[0558] When the electronic device displays page B in split screen, the preset requirements for split screen display may indicate that page B cannot be displayed in split screen and can be displayed in full screen. For example, the value of targetPosition may be set to 0. Thus, when the electronic device needs to display page B in full screen after the split screen is displayed, it may 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 step 21-1, step 21-2 and step 21-3 is not particular, and they can be executed sequentially or simultaneously. This application does not limit this.

[0560] When the judgment results of step 21 - 1 , step 21 - 2 and step 21 - 3 are all yes, the parallel window manager (HwMagicWindowManager) can determine the taskID of the Activity corresponding to the a1 page 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 the split-screen parameters of page B, such as the split-screen boundaries (bounds) and motion effects, or the split-screen parameters of page a1 and page B, such as the split-screen boundaries (bounds) and motion effects.

[0562] The parallel window manager (HwMagicWindowManager) displays two independent tasks on the left and right screens of the display at the same time 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, as shown in the following example: Figure 5A The a1 page shown in (3) 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.

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

[0564] like Figure 5C As shown, the specific implementation process of the application page display method of the present 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, it creates a new Task (ie, a task stack different from the task stack corresponding to page a1), starts the Activity corresponding to page B in the new Task, and displays page B.

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

[0568] S43 . In response to message 9 , the application obtains the method name of method 2 (called setTaskPosition ), the split-screen position of page B (targetPosition ), and the taskID 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 (called setTaskPosition), the split-screen position of page B (targetPosition), and the taskID of the activity corresponding to page B.

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

[0571] S461. 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.

[0572] Step S461 is an optional step.

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

[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 (targetPosition) of page B.

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

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

[0577] S48. The parallel window manager (HwMagicWindowManager) displays page a1 and page B simultaneously 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.

[0578] It should be noted that Figure 5C The specific implementation process shown in the example can be found in the above content and will not be repeated here.

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

[0580] The new task is different from the task corresponding to page a1. This means that the activity corresponding to page B enters a different task from the activity corresponding to page a1. For control B, please refer to the previous description and will not be repeated here.

[0581] Furthermore, the electronic device may send a message 11 to the application, and the message 11 is used to identify the aforementioned operation 701. Then, in response to the aforementioned operation 701, the application may obtain the task ID (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 701, and determine the method name (called setTaskPosition) of method 2 for split-screen display within the application based on the aforementioned operation 701. Method 2 is used to indicate that page a1 and page B are to be split-screen displayed. In this application, the representation of message 11 is not limited. For example, message 11 may be the reported point coordinates of the aforementioned operation 701.

[0582] Among them, the split-screen positions mentioned above can be found in the description of the split-screen positions mentioned above, and will not be repeated here.

[0583] In summary, the software system of the electronic device notifies the application of the aforementioned operation 701, 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 of method 2 for split-screen display within the application (called setTaskPosition).

[0584] It should be noted that the electronic device establishes a new Task execution step in response to operation 701, and the software system of the electronic device sends the execution steps of the aforementioned operation 701 to the application. There is no particular order in terms of timing, and they can be executed simultaneously or sequentially. This application does not limit this.

[0585] Based on the description of the previous embodiment, the application can call the call (invoke) interface in the third-party interface layer (EasyGoSDK) of the electronic device and pass message 12, which carries the method name of method 2 (setTaskPosition), the split-screen position (targetPosition) and the taskID of the Activity corresponding to page B.

[0586] Among them, this application does not limit the representation of message 12. For example, the split screen position (targetPosition) and the taskID of the Activity corresponding to page B can be passed using parameter params6. The definition of the invoke interface can be found in the description of scenario one and will not be repeated here. It should be noted that the taskID of the Activity corresponding to page B can be replaced with the ID of page B. This application does not limit this. It only needs to transmit the identifier used to represent page B. Among them, this application does not limit the 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 taskID of the activity corresponding to page B. The third-party interface layer (EasyGoSDK) can also obtain (e.g., actively query) 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 taskID of the Activity corresponding to page B, and the package name (package name) of the application to the parallel window manager (HwMagicWindowManager) of the electronic device.

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

[0590] based on Figure 2b The structure shown in the figure uses the policy module, configuration module, data management module, background layer drawing module, and animation module to implement the following process in the parallel window manager (HwMagicWindowManager):

[0591] The parallel window manager (HwMagicWindowManager) can determine whether the method name (setTaskPosition) of method 2 and the content of params7 are empty. If 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. The parallel window manager (HwMagicWindowManager) can determine whether the task stack of the activity corresponding to the a1 page is in non-split-screen mode (that is, whether the a1 page corresponding to the activity is not in split-screen display state) based on the package name (packagename) of the application.

[0593] 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 non-split-screen mode. Therefore, 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 non-split-screen mode.

[0594] Alternatively, the parallel window manager (HwMagicWindowManager) may obtain an indicator from the electronic device, wherein the indicator indicates whether the task stack of the activity corresponding to page a1 is in the non-split-screen mode. Thus, when the indicator indicates that the task stack corresponding to the activity is in the non-split-screen mode, the parallel window manager (HwMagicWindowManager) may 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 the present application is not limited to the aforementioned two implementation methods for determining whether the task stack of the Activity corresponding to the a1 page is in the non-split-screen mode.

[0596] Step 22-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 (packagename) of the application. Then, 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 split-screen display of multiple pages of the application.

[0597] The specific implementation of step 22-2 can be found in the description of step 21-2 and will not be repeated here.

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

[0599] The specific implementation of step 22-3 can be found in the description of step 21-3 and will not be repeated here.

[0600] In addition, the execution order of step 22-1, step 22-2 and step 22-3 is not specific, and they can be executed sequentially or simultaneously, and this application does not limit this.

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

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

[0603] The parallel window manager (HwMagicWindowManager) displays two independent tasks on the left and right screens of the display at the same time 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, as shown in the following example: Figure 5A The a1 page shown in (3) 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.

[0604] Based on the above description, combined with Figure 5D , the implementation process of split-screen display of page a1 and page B in electronic devices is specifically explained.

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

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

[0607] S42', when the electronic device receives the user's operation 701 on page a1, it creates a new Task (i.e., a task stack different from the task stack corresponding to page a1), starts the Activity corresponding to page B in the new Task, and sends message 11 to the application, where message 11 is used to identify operation 701.

[0608] S43 ′: In response to message 11 , the application obtains the method name of method 2 (called setTaskPosition), the split-screen position of page B (targetPosition), and the taskID 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 of method 2 (called setTaskPosition), the split-screen position of page B (targetPosition), and the taskID of the activity corresponding to page B.

[0610] S45. The third-party interface layer (EasyGoSDK) sends the method name of method 2 (called setTaskPosition), the split-screen position of page B (targetPosition), the taskID 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 taskID of the Activity corresponding to the a1 page is in 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 taskID of the activity corresponding to page a1 based on the package name of the application, and determines the split-screen parameters of page B based on the split-screen position (targetPosition) and the taskID of the activity corresponding to page B.

[0616] In addition, when the result of determination in any one of steps S461, S462 and S463 is negative, the parallel window manager (HwMagicWindowManager) continues to display the a1 page.

[0617] S48. The parallel window manager (HwMagicWindowManager) displays page a1 and page B simultaneously 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.

[0618] It should be noted that Figure 5D The specific implementation process shown in the example can be found in the above content and will not be described here in detail. Figure 5C and Figure 5D The difference is: Figure 5C Steps S421, S422-S43 and Figure 5C Steps S42'-S43', and Figure 5C Step S461 and Figure 5DStep S461′, the remaining steps are the same.

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

[0620] In other embodiments, after the electronic device detects the user's instruction to trigger the operation 101 of the control B in the a1 page, if the launch mode (launchMode) 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 page B is started, the electronic device can display page B by default (i.e. Figure 5A In addition, page B includes a split-screen / full-screen control, which indicates 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.

[0622] After the electronic device detects the user's instruction to trigger the split-screen / full-screen control in page B, the electronic device may send a message 13 to the application. Message 13 is used to identify the aforementioned operation 702, so that the application can obtain the 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 aforementioned operation 702, and determine the method name of method 2 (called setTaskPosition) for split-screen display within the application based on the aforementioned operation 702. Method 2 is used to indicate that page a1 and page B are split-screen displayed. Among them, this application does not limit the representation method of message 13. For example, message 13 may include the reported point coordinates of the aforementioned operation 702.

[0623] In summary, the software system of the electronic device sends the aforementioned operation 702 to the application, 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 of method 2 for split-screen display within the application (called setTaskPosition).

[0624] Among them, the split-screen positions mentioned above can be found in the description of the split-screen positions in scene one, and will not be repeated here.

[0625] Based on the description of the above embodiment, the application can call the invoke interface in the third-party interface layer (EasyGoSDK) of the electronic device and pass message 14, which carries the method name of method 2 (setTaskPosition), the split-screen position (targetPosition) and the taskID of the Activity corresponding to the a1 page.

[0626] Among them, this application does not limit the representation of message 14. For example, the split screen position (targetPosition) and the taskID of the Activity corresponding to the a1 page can be passed using the parameter params6. The definition of the invoke interface can be found in the description of scenario one and will not be repeated here. It should be noted that the taskID of the Activity corresponding to the a1 page can be replaced with the ID of the a1 page. This application does not limit this. It only needs to transmit the identifier used to represent the a1 page. Among them, this 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 taskID of the activity corresponding to page a1. The third-party interface layer (EasyGoSDK) can also obtain (e.g., actively query) 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 taskID of the Activity corresponding to the a1 page, and the package name (package name) of the application to the parallel window manager (HwMagicWindowManager) of the electronic device.

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

[0630] based on Figure 2bThe structure shown in the figure uses the policy module, configuration module, data management module, background layer drawing module, and animation module to implement the following process in the parallel window manager (HwMagicWindowManager):

[0631] The parallel window manager (HwMagicWindowManager) can determine whether the method name (setTaskPosition) of method 2 and the content of params7 are empty. If 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 determine whether the activity corresponding to the taskID is the current task stack based on the taskID of the activity corresponding to the a1 page, and then the electronic device can ensure that the current task stack exists when the activity corresponding to the taskID is the current task stack.

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

[0634] Step 23-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 (packagename) of the application. Then, 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 split-screen display of multiple pages of the application.

[0635] The specific implementation of step 23-2 can be found in the description of step 21-2 and will not be repeated here.

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

[0637] The specific implementation of step 23-3 can be found in the description of step 21-3 and will not be repeated here.

[0638] In addition, the execution order of step 23-1, step 23-2 and step 23-3 is not specific, and they can be executed sequentially or simultaneously, and this 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 page a1) and start the Activity corresponding to page B in this new Task.

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

[0641] 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 the split-screen parameters of page B, such as the split-screen boundaries (bounds) and motion effects, or the split-screen parameters of page a1 and page B, such as the split-screen boundaries (bounds) and motion effects.

[0642] The parallel window manager (HwMagicWindowManager) displays two independent tasks on the left and right screens of the display at the same time 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, as shown in the following example: Figure 5A The a1 page shown in (3) 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 above description, combined with Figure 5E , the implementation process of split-screen display of page a1 and page B in electronic devices is specifically explained.

[0644] like Figure 5E As 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 page a1.

[0646] S621: When the electronic device receives the user's operation 701 on page a1, it displays page B. The task stack corresponding to page B is the same as the task stack corresponding to page a1, and the activity corresponding to page B is started in the task stack to display page B.

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

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

[0649] S64. The application sends message 14 to the third-party interface layer (EasyGoSDK). Message 14 carries the method name of method 2 (called setTaskPosition), the split-screen position of page B (targetPosition), and the taskID of the activity corresponding to page a1.

[0650] 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 taskID of the activity corresponding to page a1, 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 taskID 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-application split-screen function.

[0654] 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 (targetPosition) of page B.

[0655] 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), 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 taskID of the Activity corresponding to page B.

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

[0657] S68. The parallel window manager (HwMagicWindowManager) displays page a1 and page B simultaneously 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.

[0658] It should be noted that Figure 5E The specific implementation process shown in the example can be found in the above content and will not be described here in detail. Figure 5E and Figure 5C The difference is: Figure 5E The timing of establishing a new task stack in step S67 is the same as Figure 5C The timing of establishing a new task stack in S421, and Figure 5E The taskID of the Activity corresponding to the transferred a1 page is Figure 5C The taskID of the Activity corresponding to page B, and the rest of the steps are similar.

[0659] in addition, Figure 5C and Figure 5E The operation 701 in the example is used to identify different meanings and can be operations of the same type or different types. Figure 5C Operation 701 in FIG. 1 is used to indicate a jump from displaying page a1 in one task stack to displaying page B in another task stack. Figure 5E Operation 701 in FIG. 1 is used to indicate a jump from displaying page a1 in a task stack to displaying page B in the task stack.

[0660] In other embodiments, after the electronic device detects the user-instructed operation 701 to trigger the control B in the a1 page, if the launch mode (launchMode) of the Activity corresponding to the B page is not set to singleInstance mode, a message 15 may be sent to the application. Message 15 is used to identify the aforementioned operation 701. Then, in response to the aforementioned operation 701, the application may obtain the task ID (referred to as 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 aforementioned operation 701, and determine the method name (called setTaskPosition) of the method 2 for split-screen display within the application based on the aforementioned operation 701. Method 2 is used to indicate that the a1 page and the B page are split-screen displayed. Among them, this application does not limit the representation method of message 15. For example, message 15 can be the reported point coordinates of the aforementioned operation 701.

[0661] Among them, the split-screen positions mentioned above can be found in the description of the split-screen positions mentioned above, and will not be repeated here.

[0662] In summary, the software system of the electronic device notifies the application of the aforementioned 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 of method 2 for split-screen display within the application (called setTaskPosition).

[0663] It should be noted that the electronic device establishes a new Task execution step in response to operation 701, and the software system of the electronic device sends the execution steps of the aforementioned operation 701 to the application. There is no particular order in terms of timing, and they can be executed simultaneously or sequentially. This application does not limit this.

[0664] Based on the description of the above embodiment, the application can call the invoke interface in the third-party interface layer (EasyGoSDK) of the electronic device and pass message 16, which carries the method name of method 2 (setTaskPosition), the split-screen position (targetPosition) and the taskID of the Activity corresponding to the a1 page.

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

[0666] In summary, the third-party interface layer (EasyGoSDK) can obtain the method name (setTaskPosition) of method 2, the split-screen position (targetPosition), and the taskID of the activity corresponding to page a1. The third-party interface layer (EasyGoSDK) can also obtain (e.g., actively query) the package name of the application.

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

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

[0669] based on Figure 2b The structure shown in the figure uses the policy module, configuration module, data management module, background layer drawing module, and animation module to implement the following process in the parallel window manager (HwMagicWindowManager):

[0670] The parallel window manager (HwMagicWindowManager) can determine whether the method name (setTaskPosition) of method 2 and the content of params7 are empty. If 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:

[0671] Step 24-1. The parallel window manager (HwMagicWindowManager) can determine whether the task stack corresponding to the taskID is in non-split-screen mode (i.e., whether the a1 page corresponding to the Activity is not in split-screen display) based on the taskID of the Activity corresponding to the a1 page.

[0672] The specific implementation of step 24-1 can be found in the description of step 22-1 and will not be repeated here.

[0673] Step 24-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 (packagename) of the application. Then, 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 split-screen display of multiple pages of the application.

[0674] The specific implementation of step 24-2 can be found in the description of step 23-2 and will not be repeated here.

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

[0676] The specific implementation of step 24-3 can be found in the description of step 23-3 and will not be repeated here.

[0677] In addition, the execution order of step 24-1, step 24-2 and step 24-3 is not specific, and they can be executed sequentially or simultaneously, and this application does not limit 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 (ie, a task stack different from the task stack corresponding to page a1 ) and start the Activity corresponding to page B in the new Task.

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

[0680] 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 the split-screen parameters of page B, such as the split-screen boundaries (bounds) and motion effects, or the split-screen parameters of page a1 and page B, such as the split-screen boundaries (bounds) and motion effects.

[0681] The parallel window manager (HwMagicWindowManager) displays two independent tasks on the left and right screens of the display at the same time 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, as shown in the following example: Figure 5A The a1 page shown in (3) 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.

[0682] Based on the above description, combined with Figure 5F , the implementation process of split-screen display of page a1 and page B in electronic devices is specifically explained.

[0683] like Figure 5F As shown, the specific implementation process of the application page display method of the present 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 a message 15 to the application. The message 15 is used to identify the operation 701 .

[0686] S63 ′: In response to message 15 , the application obtains the method name of method 2 (called setTaskPosition), the split-screen position of page B (targetPosition), and the taskID of the activity corresponding to page a1 .

[0687] S64. The application sends message 16 to the third-party interface layer (EasyGoSDK). Message 16 carries the method name of method 2 (called setTaskPosition), the split-screen position of page B (targetPosition), and the taskID 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 taskID of the activity corresponding to page a1, and the package name of the application to the parallel window manager (HwMagicWindowManager).

[0689] S661', the parallel window manager (HwMagicWindowManager) determines whether the task stack corresponding to the taskID of the Activity corresponding to the a1 page is in non-split-screen mode (ie, whether the A page corresponding to the 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 (packagename) of the application supports the in-application 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 (targetPosition) of page B.

[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), 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 taskID of the Activity corresponding to page B.

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

[0694] S68. The parallel window manager (HwMagicWindowManager) displays page a1 and page B simultaneously 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.

[0695] It should be noted that Figure 5FThe specific implementation process shown in the example can be found in the above content and will not be described here in detail. Figure 5E and Figure 5F The difference is: Figure 5E Steps S621, S562-S63 and Figure 5F Steps S62'-S63', and Figure 5E Step S661 and Figure 5F Step S661′, the remaining steps are the same.

[0696] in addition, Figure 6E and Figure 6C The difference is: Figure 6E The timing of establishing a new task stack in step S67 is the same as Figure 6C The timing of establishing a new task stack in S421, and Figure 6E The taskID of the Activity corresponding to the transferred a1 page is Figure 6C The taskID of the Activity corresponding to page B, and the rest of the steps are similar.

[0697] in addition, Figure 6C and Figure 6E The operation 701 in the example is used to identify different meanings and can be operations of the same type or different types. Figure 6C Operation 701 in FIG. 1 is used to indicate a jump from displaying page a1 in one task stack to displaying page B in another task stack. Figure 6E Operation 701 in FIG. 1 is used to indicate a jump from displaying page a1 in a task stack to displaying page B in the task stack.

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

[0699] like Figure 5B As shown in (2) and (3), page B may also 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 detecting the user's instruction to trigger the return control 5 in the B page, the electronic device can exit the Activity corresponding to the B page, so that the electronic device can return to the displayed page. Figure 5B The user interface shown in (2) or (3) returns to the display Figure 5B The user interface shown in (1) is an example.

[0701] 3. Open a new page from the a1 page displayed on the left split screen. The new page will replace the a1 page displayed on the left split screen (corresponding to Figure 5A Step S231 or step S232 shown)

[0702] 31. Open the C2 page from the left split screen a1 page, and the C2 page will replace the left split screen a1 page (corresponding to Figure 5A Step S231 shown)

[0703] When the electronic device detects operation 901 of triggering the control C2 in the a1 page as instructed by the user, it may send parameters policy4 and params8 to the parallel window manager (HwMagicWindowManager).

[0704] Since the user performed operation 901 on page a1, and page a1 is displayed in the left split screen, parameter policy4 is used to identify the policy to be adopted when opening page C2 from page a1 displayed in the left split screen. Parameter policy4 can be represented by numbers, strings, letters, etc. params8 can include, but is not limited to: a token of the activity corresponding to page a1 (i.e., the focus activity), a token of the activity corresponding to page C2, and configuration parameters for the intent used to start the activity corresponding to page C2.

[0705] The token of the activity corresponding to page a1 can identify the activity corresponding to page a1, and the token of the activity corresponding to page C2 can identify the activity corresponding to page C2. The configuration parameters of the intent for starting the activity corresponding to page C2 can start the activity corresponding to page C2.

[0706] The parallel window manager (HwMagicWindowManager) can determine whether the task stack corresponding to the activity is in split-screen mode (that is, whether the a1 page corresponding to the activity is in split-screen display state) based on the token of the activity corresponding to the a1 page.

[0707] Among them, the parallel window manager (HwMagicWindowManager) can determine the task stack corresponding to the page currently displayed by the electronic device (i.e., the task stack corresponding to page a1 and the task stack corresponding to page B), and determine whether the task stack corresponding to page a1 and the task stack corresponding to page B are different task stacks. Therefore, 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 the activity is in split-screen mode.

[0708] Alternatively, the parallel window manager (HwMagicWindowManager) may obtain an indicator from the electronic device, wherein the indicator indicates whether the task stack corresponding to the activity is in split-screen mode. Thus, when the indicator indicates that the task stack corresponding to the activity is in split-screen mode, the parallel window manager (HwMagicWindowManager) may determine that the task stack corresponding to the activity is in split-screen mode.

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

[0710] 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 C2 page based on the token of 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 the split-screen parameters of the C2 page, such as the split-screen boundaries and moving effects, so that the C2 page replaces the a1 page and is displayed in the left split screen of the electronic device, such as Figure 5A As shown in (41).

[0711] The activity corresponding to the C2 page can be set to any of the four launch modes. If the launch mode of the activity corresponding to the C2 page is set to singleInstance mode, the C2 page is launched as a newtask, and the split-screen boundaries of the C2 page can limit the size of the C2 page window.

[0712] 32. Open page B from page a1 on the left split screen. Page B will replace page a1 on the left split screen (corresponding to Figure 5A Step S232 shown)

[0713] After detecting the user-instructed operation 902 of triggering the control B in the a1 page, the electronic device may send parameters policy5 and params9 to the parallel window manager (HwMagicWindowManager).

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

[0715] The token of the activity corresponding to page a1 can identify the activity corresponding to page a1, and the token of the activity corresponding to page B can identify the activity corresponding to page B. The configuration parameters of the intent for starting the activity corresponding to page B can start the activity corresponding to page B.

[0716] The parallel window manager (HwMagicWindowManager) can determine whether the task stack corresponding to the activity is in split-screen mode (that is, whether the a1 page corresponding to the activity is in split-screen display state) based on the token of the activity corresponding to the a1 page.

[0717] Among them, the parallel window manager (HwMagicWindowManager) can determine the task stack corresponding to the page currently displayed by the electronic device (i.e., the task stack corresponding to page a1 and the task stack corresponding to page B), and determine whether the task stack corresponding to page a1 and the task stack corresponding to page B are different task stacks. Therefore, 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 the activity is in split-screen mode.

[0718] Alternatively, the parallel window manager (HwMagicWindowManager) may obtain an indicator from the electronic device, wherein the indicator indicates whether the task stack corresponding to the activity is in split-screen mode. Thus, when the indicator indicates that the task stack corresponding to the activity is in split-screen mode, the parallel window manager (HwMagicWindowManager) may 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 aforementioned two implementation methods for determining 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 (launchMode) of the Activity corresponding to page B is set to singleInstance mode, the electronic device can establish a new Task (i.e., a task stack that is different from the task stack corresponding to page a1 and the task stack corresponding to page B displayed on the right split screen), and based on the token (token) of the Activity corresponding to page B, start the configuration parameters of the intent for starting the Activity corresponding to page B, so that the Activity corresponding to page B is started. Furthermore, the parallel window manager (HwMagicWindowManager) can determine the split-screen parameters of page B, such as split-screen boundaries (bounds) and moving animations, so that page B replaces page a1 and is displayed in the left split screen of the electronic device, such as Figure 5A As shown in (42).

[0721] in, Figure 5A The specific implementation of step S232 shown is the same as Figure 5A The step S231 shown is similar.

[0722] 41. Exit the C2 page displayed on the left split screen (corresponding to Figure 5B Step S241 shown)

[0723] like Figure 5B As shown in (41), the C2 page displayed on 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 C2 page display.

[0724] After detecting the user's instruction to trigger the operation 1001 of the return control 6 in the C2 page, the electronic device can exit the Activity corresponding to the C2 page, so that the electronic device returns to the state shown in FIG. Figure 5BThe user interface shown in (41) returns to the display as shown in FIG. Figure 5B The user interface shown in (3) is an example.

[0725] 42. Exit the B page displayed on the left split screen (corresponding to Figure 5B Step S242 shown)

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

[0727] After detecting the user's instruction to trigger the return control 7 in the B page, the electronic device can exit the activity corresponding to the B page in the left split screen, so that the electronic device returns to the page displayed as shown in FIG. Figure 5B The user interface shown in (42) returns to the display as shown in FIG. Figure 5B The user interface shown in (3) is an example.

[0728] 43. Exit the B page displayed on the right split screen (corresponding to Figure 5B Steps S261 and S262 shown)

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

[0730] After detecting the user's instruction to trigger the return control 5 in the B page, the electronic device can exit the activity corresponding to the B page in the right split screen, so that the electronic device returns to the page displayed as shown in FIG. Figure 5B The user interface shown in (41) returns to the display as shown in FIG. Figure 5B (1) or (2) of the exemplary user interface, or, so that the electronic device from the display as shown Figure 5B The user interface shown in (42) returns to the display as shown in FIG. Figure 5B The user interface shown in (1) or (2) is exemplified.

[0731] 5. Open a new page (i.e., page D) from the B page displayed on the right split screen. Page D will replace the B page displayed on the right split screen (corresponding to Figure 5A Step S25 shown)

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

[0733] Since the user performs operation 1101 on page B, and page B is displayed in the right split screen, parameter policy6 is used to identify the policy to be adopted when opening page D from page B displayed in the right split screen. Parameter policy6 can be represented by numbers, strings, letters, etc. params10 can include, but is not limited to: a token for the activity corresponding to page B (i.e., the focus activity), a token for the activity corresponding to page D, and configuration parameters for the intent used to launch the activity corresponding to page D.

[0734] 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 for starting the activity corresponding to page D are used to start the activity corresponding to page D.

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

[0736] Among them, the parallel window manager (HwMagicWindowManager) can determine the task stack corresponding to the page currently displayed by the electronic device (i.e., the task stack corresponding to page a1 and the task stack corresponding to page B), and determine whether the task stack corresponding to page a1 and the task stack corresponding to page B are different task stacks. Therefore, 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 the activity is in split-screen mode.

[0737] Alternatively, the parallel window manager (HwMagicWindowManager) may obtain an indicator from the electronic device, wherein the indicator indicates whether the task stack corresponding to the activity is in split-screen mode. Thus, when the indicator indicates that the task stack corresponding to the activity is in split-screen mode, the parallel window manager (HwMagicWindowManager) may determine that the task stack corresponding to the activity is in split-screen mode.

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

[0739] 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 (bounds) and the moving animation, so that the D page replaces the B page and is displayed in the right split screen of the electronic device, such as Figure 5A If not, return.

[0740] The activity corresponding to the D page can be set to any of the four launch modes. If the launch mode of the activity corresponding to the D page is set to singleInstance mode, the D page is launched as a newtask, and the split-screen boundaries of the D page can limit the size of the D page window.

[0741] in, Figure 5A The specific implementation of step S25 shown is the same as Figure 5A The steps S231 and S232 shown are similar.

[0742] 6. Exit the D page displayed on the right split screen (corresponding to Figure 5B Step S48 shown)

[0743] like Figure 5B As shown in (5), the D page may also 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 D page display.

[0744] After detecting the user's instruction to trigger the return control 8 in the D page, the electronic device can exit the Activity corresponding to the D page, so that the electronic device can return to the displayed page. Figure 5B The user interface shown in (5) is returned to the display Figure 5B The user interface shown in (4) is an example.

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

[0746] 1) In response to an operation triggered by a user, the electronic device may switch from displaying page a1 to displaying page a1 and page B in split screen.

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

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

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

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

[0751] 6) Page B can be switched freely between full screen display and split screen display.

[0752] Thus, when the user processes multiple tasks in parallel, the electronic device can cut any application from displaying a sub-page in full screen to displaying other pages of the application in split screen, and the new page opened from any split screen will destroy the page displayed in the split screen and be displayed in the split screen, which solves the phenomenon in the related art that due to the coupling relationship between different split screens, the new page opened in any split screen will destroy the pages displayed in other split screens, avoids the display interference between pages in different split screens, and enables pages in different split screens to run independently, providing users with a multi-tasking or immersive experience. In addition, after the application starts the in-application split-screen function, the electronic device can switch from displaying multiple pages of the application in split screen to displaying one page of the application in full screen, or from displaying one page of the application in full screen to displaying multiple pages of the application in split screen based on user needs, providing users with an efficient and flexible multi-window multi-tasking experience.

[0753] based on Figures 5A-5F The description shown, combined with Figures 6A-6K, introduces the specific implementation process of electronic devices to complete the split-screen display of multiple pages of any application. For the sake of explanation, Figures 6A-6K In the figure, the electronic device is a tablet computer, the application is the WeChat application, page A is a chat dialog list, page a0 includes the WeChat application icon set in the center, page a1 is a specific chat dialog window, page B is the page of the XX video applet in the WeChat application, page C2 is page A, and page D is the page of video 1 corresponding to the icon of video 1 on page B.

[0754] See also Figures 6A-6K , Figures 6A-6K A schematic diagram of a human-computer interaction interface provided in one embodiment of the present application.

[0755] The tablet can display Figure 6A The user interface 21 is shown as an example. The user interface 21 may be the home screen of the desktop. The user interface 21 may include, but is not limited to, a status bar, a navigation bar, a calendar indicator, a weather indicator, and multiple application icons. The application icons include at least the WeChat application icon 601 and may also include icons for a calculator, Huawei Video, a browser, a camera, music, settings, email, and memos.

[0756] After detecting the user's instruction to open the WeChat application (such as clicking the WeChat application icon 401), the tablet computer may display Figure 6B The user interface 22a and user interface 22b are shown as examples, with user interface 22a displayed on the left split screen and user interface 22b displayed on the right split screen. Among them, user interface 22a can be used to display the main page (i.e., page A) of the WeChat application. User interface 22b can be used to display the secondary page (i.e., page a0) of the WeChat application.

[0757] The display areas of user interface 22a and user interface 22b may be the same or different, and this application does not impose any restrictions thereon. Furthermore, a control for adjusting the display areas of user interface 22a and user interface 22b may be provided in the overlapping boundary area of ​​user interface 22a and user interface 22b, so as to adjust the display areas of user interface 22a and user interface 22b in real time based on user needs.

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

[0759] The tablet detects that the user is Figure 6B After performing an operation such as clicking the control 602 in the user interface 22a shown in FIG. 1 , the user can select the display Figure 6B The user interface 22b shown in the example becomes a display Figure 6C The user interface 23b is shown as an example. The user interface 23b may be a sub-page of the WeChat application (such as the page of the chat dialogue between the user and Xiaoyi (i.e., page a1)), thereby facilitating the user to chat with Xiaoyi on WeChat. In addition, the tablet computer may continue to display the content in the left split screen. Figure 6C The exemplary user interface 22a further facilitates users to implement other functions of the WeChat application.

[0760] Among them, the control 602 is used to enter the page of the chat dialogue between the user and xiaoyi (ie, page a1). This application does not limit the specific implementation of the control 602.

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

[0762] In addition, the user interface 22b may further include a return control 6041 ( Figure 6C 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 6B The user interface 22b shown in the example. The return control 6041 here can be seen as Figure 5A Return control 02 in .

[0763] The display areas of user interface 22a and user interface 23b may be the same or different, and this application does not impose any restrictions thereon. Furthermore, a control for adjusting the display areas of user interface 22a and user interface 23b may be provided in the overlapping boundary area of ​​user interface 22a and user interface 23b, so as to adjust the display areas of user interface 22a and user interface 23b in real time based on user needs.

[0764] The tablet detects that the user is Figure 6C After performing an operation such as clicking the control 603 in the user interface 23b shown in FIG. Figure 6D The user interface 24 shown as an example is used to display the main page (i.e., page B) of the XX video browsing webpage / XX video applet.

[0765] It should be noted that users Figure 6C The operation of clicking the control 603 in the user interface 23b shown 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 webpage / XX video applet with functions such as sharing, removal, split screen / full screen display, floating window display, settings, feedback and complaints, and re-entry.

[0768] Among them, 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 Figure 5B Return control 5 in .

[0769] The tablet detects that the user is Figure 6D After performing an operation such as clicking the multi-function control 605 in the user interface 24 shown in FIG. Figure 6E The window 607 shown as an example includes at least: a control 6071.

[0770] Among them, window 607 can be a window for 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, and is used to display 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.

[0771] Among them, the control 6071 is used to realize the split-screen display of page B, which can be represented by icons and / or text. For example, Figure 6D The control 6071 in the text "Show in split screen" and the icon Here, the control 6071 can be seen as Figure 5A and Figure 5B The operation of clicking the multi-function control 605 here can be regarded as Figure 5C or Figure 5E The operation 701 in the example, the operation of clicking the control 6071 here can be seen as Figure 5C or Figure 5E It should be noted that the control 6071 can also be displayed in the window 607, without being displayed through an operation such as clicking the multi-function control 605.

[0772] The tablet detects the user's instruction Figure 6E After performing an operation such as clicking the control 6071 in the window 607 shown, the Figure 6F User interface 25a and user interface 25b are shown as examples, with user interface 25a displayed on the left split screen and user interface 25b displayed on the right split screen. User interface 25a is used to display a subpage of the WeChat application (i.e., page a1). User interface 25b is used to display page B of the XX video browsing webpage / XX video mini-program. This allows users to browse the XX video browsing webpage / XX video mini-program while also chatting with Xiaoyi on WeChat.

[0773] The display areas of user interface 25a and user interface 25b may be the same or different, and this application does not impose any restrictions thereon. The display positions of user interface 25a and user interface 25b may be interchangeable, i.e., user interface 25a is displayed on the right split screen, and user interface 25b is displayed on the left split screen. In addition, a control for adjusting the display areas of user interface 25a and user interface 25b may be provided in the overlapping boundary area of ​​user interface 25a and user interface 25b, so as to adjust the display areas of user interface 25a and user interface 25b in real time based on user needs.

[0774] It should be noted that, in addition to the above methods, the tablet computer can detect that the user is Figure 6C After performing an operation such as clicking the control 603 in the user interface 23b shown in FIG. Figure 6F The user interface 25a and the user interface 25b are shown as examples, and the user interface 25a is displayed on the left split screen and the user interface 25b is displayed on the right split screen. Figure 6D-6E The description of the embodiment shown is an optional step. The operation of clicking the control 603 here can be regarded as Figure 5D or Figure 5F Operation 701 in.

[0775] Therefore, the tablet computer can run the WeChat application in the left split screen, and at the same time, run the XX video browsing web page / XX video applet in the right split screen, allowing users to perform operations such as clicking, sliding, and long pressing on the a1 page and the B page, and simultaneously realize functions such as video watching and instant chatting, thereby improving the user experience.

[0776] In summary, Figures 6A-6F As described in the illustrated embodiment, the electronic device can display page a1 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 of the WeChat application, i.e., a1 on the left and B on the right.

[0777] It should be noted that according to Figures 6A-6F As described in the embodiment shown, the electronic device can realize that page B is displayed in the left split screen of the electronic device and page B is displayed in the right split screen of the electronic device, thereby completing the in-application split screen of the WeChat application. In addition, the page B displayed on the left split screen can also include a return control, wherein the return control is used to exit page B, so that the tablet computer returns from the current user interface and displays Figure 6F The user interface 25a and the user interface 25b are shown as examples. The return control here can be seen as Figure 5A and Figure 5B The return control 7 in the right split screen is different from the return control 606 in the B page.

[0778] The tablet detects that the user is Figure 6F In the user interface 25a shown, the following steps are executed: Figure 6F After the operation (using a left arrow as an example), you can select Figure 6F The user interface 25a shown as an example becomes a display Figure 6G The user interface 26a shown as an example, wherein the user interface 26a can be the main page of the WeChat application (i.e., page A), thereby facilitating the user to browse the XX video browsing webpage / XX video applet page while also using other functions of the WeChat application. In addition, the tablet computer can continue to display the Figure 6G User interface 25b is shown as an example.

[0779] Among them, the control 6042 is used to enter the main page of the WeChat application (i.e., page A). This application does not limit the specific implementation of the control 6042. In addition, the user interface 26a also includes at least a return control 602 ( Figure 6G The return control 602 is used to exit the C1 page, that is, to display the a1 page, so that the tablet computer can return from the user interface 26a and display Figure 6F The user interface 25a shown in the example facilitates the user to chat with Xiaoyi on WeChat. The return control 6042 here can be seen as Figure 5A and Figure 5B Return control 6 in .

[0780] In summary, Figure 6F-6GIn the illustrated embodiment, when the electronic device displays page a1 and page B in a split-screen display, a new page opened from page a1 replaces page a1 for display, without replacing page B. This achieves independent and separate display of the left and right split screens, avoiding display interference, i.e., clicking on the left results in a left display. Furthermore, the electronic device can return to page a1 from the new page, ensuring independent left and right tasks.

[0781] The tablet detects that the user is Figure 6F After performing an operation such as clicking on the control 608 in the user interface 25b shown in FIG. 1 , the user can select the display Figure 6F The user interface 25b shown as an example becomes a display Figure 6H The user interface 27b shown in the example, wherein the user interface 27b can be the page of video 1 (ie, D page), thereby facilitating the user to chat with Xiaoyi on WeChat while watching video 1. In addition, the tablet computer can continue to display the video in the left split screen. Figure 6H User interface 25a is shown as an example.

[0782] Among them, the control 608 is used to enter the page of video 1 (ie, D page). The present application does not limit the specific implementation of the control 608. In addition, the user interface 27a also includes at least a return control 609 ( Figure 6H The return control 6H is used to exit the D page, so that the tablet computer can return from the user interface 27b and display Figure 6F The user interface 25b shown in the example facilitates the user to use the XX video to browse the web page / XX video applet other functions. The return control 609 here can be seen as Figure 5A and Figure 5B Return control 8 in.

[0783] It should be noted that the tablet detects that the user is Figure 6F After performing...

Claims

1. A method for displaying an application page, characterized in that: include: Displaying a first page of a first application; In response to a first operation of a user, displaying the first page in a first area, and displaying a second page of the first application in a second area, wherein the first area does not overlap with the second area; 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, 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; After displaying the third page of the first application in the first area, the method further includes: receiving a seventh operation on the third page; In response to the seventh operation, displaying a third control, wherein the third control is used to indicate that the third page is displayed in full screen; receiving an eighth operation on the third control; In response to the eighth operation, displaying the third page in full screen; After displaying the third page in full screen: In response to the tenth operation, the third page exits full-screen display, the first page of the first application is displayed in the first area, and the second page of the first application is displayed in the second area.

2. The method according to claim 1, characterized in that The method further comprises: receiving a fourth operation of the user on the third page; In response to the fourth operation, displaying the first page in the first area and displaying the second page in the second area; and / or, receiving a fifth operation of 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.

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 of the user, the method further includes: receiving a sixth operation from the user on the second page; In response to the sixth operation, displaying a first control, wherein the first control is used to indicate that the first page and the second page are displayed in split screens; The first operation is received on the first control.

4. The method according to claim 1 or 2, characterized in that: Before responding to the first operation of the user, the method further includes: The first operation is received on the first page.

5. The method according to claim 1 or 2, characterized in that: The method further comprises: A second control is displayed in an area adjacent to the first area and the second area, and the second control is used to adjust the area of ​​the first area and the second area.

6. The method according to claim 1 or 2, characterized in that: The first region and the second region have the same area.

7. The method according to claim 1 or 2, characterized in that: The method further comprises: receiving a ninth operation of the user on the second page; In response to the ninth operation, the first page is displayed.

8. The method according to claim 1 or 2, characterized in that: Displaying the first page includes: displaying the first page in a third area, the third area including 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, wherein the fifth page is different from both the first page and the second page; or, The first page is displayed in a fourth area, the fourth area including at least a portion of the first area and a portion of the second area.

9. The method according to claim 8, characterized in that The first page corresponds to a first task stack, and in response to a first operation of the user, the first page is displayed in a first area, and a second page of the first application is displayed in a second area, and the first area does not overlap with the second area, specifically: In response to the first operation, a second task stack is established, and a first message is sent to the first application, where the first message is used to identify the first operation, 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; receiving a second message from the first application, where the second message is used to instruct to display the first page and the second page 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.

10. The method according to claim 9, characterized in that The step of displaying the first page in the first area and the second page in the second area in response to the second message includes: 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; or, When it is determined, based on the second message, that the first task stack is in 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.

11. The method according to claim 9, 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 other page are displayed in split screen, the second identifier is used to indicate the split screen position of the any one page, and the third identifier is the identifier of the any one page or the identifier of the second task stack.

12. The method according to claim 1 or 2, characterized in that: The first page corresponds to a first task stack, and in response to a first operation of the user, the first page is displayed in a first area, and a second page of the first application is displayed in a second area, and the first area does not overlap with the second area, specifically: In response to the first operation, sending a third message 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; receiving a fourth message from the first application, where the fourth message is used to instruct to display the first page and the second page in split screen; 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, and the first task stack is different from the second task stack; The first page is displayed in the first area, and the second page is displayed in the second area.

13. The method according to claim 12, characterized in that The displaying the first page in the first area and the displaying the second page in the second area includes: When it is determined, based on the fourth message, that the second page corresponds to the first task stack, 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; or, When it is determined, based on the fourth message, that the first task stack is in 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.

14. The method according to claim 12, characterized in that The fourth message includes: a fourth identifier, a fifth identifier and a sixth identifier, the fourth identifier is used to indicate that the first page and any other page are displayed in split screen, the fifth identifier is used to indicate the split screen position of the any one page, and the sixth identifier is the identifier of the any one page or the identifier of the first task stack.

15. The method according to claim 9, characterized in that The fifth page corresponds to the first task stack.

16. The method according to any one of claims 9-11, 13-15, characterized in that: In response to the second operation, displaying the third page of the first application in the first area is specifically: receiving a fifth message, wherein the fifth message is used to indicate that the third page is opened from the first page, and the third page corresponds to the first task stack; In response to the fifth message, determining whether the first task stack is in a split-screen mode; When the first task stack is in the split-screen mode, the third page is displayed in the first area in the first task stack based on the identifier of the first task stack, the identifier of the third page, and the split-screen parameters of the third page.

17. The method according to any one of claims 9-11, 13-15, characterized in that: In response to the third operation, displaying a fourth page of the first application in the second area is specifically: receiving a sixth message, wherein the sixth message is used to indicate that the fourth page is opened from the second page, and the fourth page corresponds to the 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, the fourth page is displayed in the second area in the second task stack based on the identifier of the second task stack, the identifier of the fourth page, and the split-screen parameters of the fourth page.

18. An electronic device, characterized in that: include: Memory and processor; The memory is used to store program instructions; The processor is used to call the program instructions in the memory so that the electronic device executes the application page display method according to any one of claims 1-17.

19. 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 as described in any one of claims 1-17.

20. A computer-readable storage medium having a computer program stored thereon, characterized in that: The computer program is executed by a processor in an electronic device to implement the application page display method according to any one of claims 1 to 17.

Images