Window display method and related device

Abstract

The embodiment of the invention provides a window display method and a related device, and relates to the technical field of terminals. According to the embodiment of the invention, the electronic equipment can display the independent embedded window after receiving the preset operation of the user, the embedded window can comprise the function page of a certain application program, so that the user can conveniently use the function of the application program, and the embedded window is independent of any application program installed in the electronic equipment. Therefore, display and interaction of the embedded window cannot cause interruption to the application program running in the electronic equipment.

Description

Window display method and related device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 22, 2022, with application number 202211158219.5 and application name “Window Display Method and Related Devices”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of terminal technology, and in particular to a window display method and related devices. Background Art

[0003] With the development of terminal technology, electronic devices can support the operation of various types of application programs.

[0004] In some implementations, for an application loaded in an electronic device, if a user wants to use a certain function of the application, the user needs to click the application icon in the electronic device. After the application is started, the user finds the function one level at a time in the various pages of the application before using the function.

[0005] However, in the above implementation, the operations of the user when using the application are relatively cumbersome, which affects the user experience.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide a window display method and related devices, which simplify the way to open the function of an application.

[0008] In a first aspect, an embodiment of the present application provides a window display method, applied to an electronic device, comprising:

[0009] Display a first interface, which includes page content corresponding to a first task of a first application; receive a first preset operation; in response to the first preset operation, display an embedded window on an upper layer of the first interface without interrupting execution of the first task, the embedded window including page content corresponding to a second task of a second application; receive a second preset operation; in response to the second preset operation, cancel the display of the embedded window and restore the display of the page content corresponding to the first task of the first application.

[0010] In this way, the embedded window can be displayed based on the convenience of user operation, and some tasks can be provided to the user in the embedded window, so that the user can conveniently use the tasks in the embedded window, and the embedded window will not interrupt the applications already running in the electronic device when it is displayed, so that the applications already running in the electronic device have better continuity, reduce the interference with the user's use of the application, and prompt the user experience.

[0011] In one possible implementation, the page content corresponding to the second task of the second application is displayed in the first area of ​​the embedded window. The embedded window also includes a second area. On the upper layer of the first interface, the second area of ​​the embedded window also displays: a first icon corresponding to the second task, and a second icon corresponding to the third task; wherein the first icon is in a selected state and the second icon is in an unselected state. In this way, multiple tasks can be provided in the embedded window, allowing users to use multiple applications conveniently. The task that is displaying the page content is in a selected state in the second area, and other tasks that do not display the page content can be marked as unselected, which makes it easier for users to understand the name of the task they are using.

[0012] In one possible implementation, before receiving the second preset operation, the method further includes: receiving a third preset operation in the embedded window for switching the second task to the third task; in response to the third preset operation, displaying interface content corresponding to the third task in the first area of ​​the embedded window, and displaying a first icon and a second icon in the second area of ​​the embedded window; wherein the first icon is in an unselected state and the second icon is in a selected state. In this way, the user can flexibly switch between multiple tasks in the embedded window, increasing the convenience of the user in using multiple tasks.

[0013] In one possible implementation, after displaying the interface content corresponding to the third task in the first area of ​​the embedded window, the method further includes: receiving a swipe-up operation in the first area of ​​the embedded window; in response to the swipe-up operation, displaying a first button in the first area of ​​the embedded window; and when receiving a trigger operation for the first button, displaying the page content associated with the third task with the first button in the first area of ​​the embedded window. This can enrich the content of the embedded window, allowing users to access more services based on the embedded window.

[0014] In one possible implementation, the first button includes a second button within the page content associated with the third task, and the method further includes: upon receiving a triggering operation on the second button, restoring the interface content corresponding to the first task in the first area of ​​the embedded window. In this way, the user can also conveniently return to the previous page in the embedded window.

[0015] In one possible implementation, the third task is a task of the first application, a task of the second application, or a task of the third application. In this way, the user can use different tasks of different applications based on the embedded window, which increases the richness and convenience of use.

[0016] In one possible implementation, the page content corresponding to the second task of the second application includes a third button, and the method further includes: displaying an input box in the embedded window when the third button is triggered; displaying a keyboard when the input box is triggered; and displaying input received on the keyboard in the input box. This allows the user to conveniently input in the embedded window.

[0017] In one possible implementation, after displaying the embedded window on the upper layer of the first interface, the method further includes: upon receiving a notification message; continuing to display the embedded window, and displaying the notification message in a capsule or banner format on the upper layer of the embedded window. This allows the user to instantly see the notification message even when the user is in the embedded window.

[0018] In one possible implementation, the method further includes: displaying a second interface, the second interface including a first switch; when a trigger operation for turning on the first switch is received, displaying a third interface, the third interface including an added column and an unadded column, the added column including identifiers of one or more tasks customized by the user, and the unadded column including identifiers of one or more tasks provided by the electronic device but not added by the user; when an operation for deleting the first target task in the added column is received, canceling the display of the identifier of the first target task in the added column and displaying the identifier of the first target task in the unadded column; or, when an operation for adding a second target task in the unadded column is received, canceling the display of the identifier of the second target task in the unadded column and displaying the identifier of the second target task in the added column. This can support users in conveniently customizing the tasks they need.

[0019] In one possible implementation, the "Not Added" column includes an identifier for a third target task, and the application corresponding to the third target task is not installed on the electronic device. The method further includes: upon receiving an operation for adding the third target task in the "Not Added" column, displaying a prompt message prompting the user to install the application corresponding to the third target task. This allows the user to customize a variety of tasks, not limited to applications already installed on the electronic device.

[0020] In one possible implementation, the third interface further includes a second switch, and the method further includes: upon receiving a trigger operation for turning on the second switch, displaying a recommendation indicator in a blank area of ​​the added column. In this way, the electronic device can recommend appropriate tasks to the user based on the user's situation.

[0021] In one possible implementation, in response to a first preset operation, an embedded window is displayed on the upper layer of the first interface, and the embedded window includes the page content corresponding to the second task of the second application, including: in response to the first preset operation, when the second switch is determined to be on, determining the second task of the second application based on a recommendation algorithm, the recommendation algorithm being related to one or more of the following: time information, the user's geographical fence, or user-related information in the user profile; and displaying the embedded window on the upper layer of the first interface, and the embedded window including the page corresponding to the second task of the second application. In this way, the electronic device can recommend appropriate quick task cards to the user based on the user's scenario, thereby improving the user experience.

[0022] In one possible implementation, determining the second task of the second application based on the recommendation algorithm includes: when the recommendation algorithm determines that the user will travel, determining the second task of the second application as a travel task; or, when the recommendation algorithm determines that the user will clock in, determining the second task of the second application as a clock-in task; or, when the recommendation algorithm determines that the user will pay, determining the second task of the second application as a payment task; or, when the recommendation algorithm determines that the user will ride a bus, determining the second task of the second application as a bus code task. In this way, the electronic device can recommend appropriate quick task cards to the user based on the user's scenario, thereby improving the user experience.

[0023] In one possible implementation, the first application includes an application that supports playing video or audio content. When the electronic device displays the embedded window, the electronic device keeps playing the video or audio by the first application. In this way, the application originally running on the electronic device can continue to run.

[0024] In one possible implementation, the method further includes: when the electronic device receives a first preset operation in a black screen or off screen state, lighting up the display screen of the electronic device; displaying a lock screen interface, wherein the lower layer of the lock screen interface includes an embedded window; and displaying the embedded window when a correct unlock input is received in the lock screen interface. In this way, the electronic device can display the embedded window from a black screen or off screen state based on a simple user trigger.

[0025] In one possible implementation, the method further includes: when the electronic device receives a first preset operation in the screen-on / lock state, displaying a lock screen interface, wherein the lower layer of the lock screen interface includes an embedded window; and when a correct unlock input is received in the lock screen interface, displaying the embedded window. In this way, the electronic device can display the embedded window in the screen-on / lock state based on a simple user trigger.

[0026] In one possible implementation, in response to a first preset operation, an embedded window is displayed on the upper layer of the first interface without interrupting the execution of the first task, and the embedded window includes the page content corresponding to the second task of the second application, including: in response to the first preset operation, a new task task is created for the second application, and the embedded window is displayed on the upper layer of the first interface without interrupting the execution of the first task, and the embedded window includes the page content corresponding to the second task of the second application. In this way, the second application can provide the page content corresponding to the second task to the embedded window based on the newly created task, without the electronic device jumping to the second application, so that the operation of the second application can also have better continuity.

[0027] In a possible implementation, receiving the first preset operation includes: receiving an operation of double-clicking the back of the electronic device. Such an operation is relatively convenient and easy for the user to implement.

[0028] In a second aspect, an embodiment of the present application provides a window display device, which may be an electronic device or a chip or chip system within an electronic device. The window display device may include a display unit and a processing unit. When the window display device is an electronic device, the display unit may be a display screen. The display unit is configured to perform the display step so that the electronic device implements a window display method described in the first aspect or any possible implementation of the first aspect. When the window display device is an electronic device, the processing unit may be a processor. The window display device may also include a storage unit, which may be a memory. The storage unit is configured to store instructions, and the processing unit executes the instructions stored in the storage unit so that the electronic device implements a window display method described in the first aspect or any possible implementation of the first aspect. When the window display device is a chip or chip system within an electronic device, the processing unit may be a processor. The processing unit executes the instructions stored in the storage unit so that the electronic device implements a window display method described in the first aspect or any possible implementation of the first aspect. The storage unit may be a storage unit within the chip (eg, a register, a cache, etc.), or a storage unit within the electronic device that is located outside the chip (eg, a read-only memory, a random access memory, etc.).

[0029] Exemplarily, the display unit is used to display a first interface, which includes page content corresponding to a first task of a first application; the processing unit is used to receive a first preset operation; the display unit is also used to display an embedded window on the upper layer of the first interface in response to the first preset operation without interrupting the execution of the first task, and the embedded window includes page content corresponding to a second task of a second application; the processing unit is also used to receive a second preset operation; the display unit is also used to cancel the display of the embedded window in response to the second preset operation, and restore the display of the page content corresponding to the first task of the first application.

[0030] In one possible implementation, the page content corresponding to the second task of the second application is displayed in the first area of ​​the embedded window. The embedded window also includes a second area. On the upper layer of the first interface, the second area of ​​the embedded window also displays: a first icon corresponding to the second task, and a second icon corresponding to the third task; wherein the first icon is in a selected state and the second icon is in an unselected state.

[0031] In one possible implementation, the processing unit is further used to receive a third preset operation for switching the second task to the third task in the embedded window; the display unit is further used to display the interface content corresponding to the third task in the first area of ​​the embedded window in response to the third preset operation, and display the first icon and the second icon in the second area of ​​the embedded window; wherein the first icon is in an unselected state and the second icon is in a selected state.

[0032] In one possible implementation, the processing unit is further used to receive a swipe-up operation in the first area of ​​the embedded window; the display unit is further used to display the first button in the first area of ​​the embedded window in response to the swipe-up operation; the display unit is further used to display the page content associated with the first button in the third task in the first area of ​​the embedded window when a trigger operation on the first button is received.

[0033] In one possible implementation, the first button includes a second button in the page content associated with the third task, and the display unit is further used to restore the display of the interface content corresponding to the first task in the first area of ​​the embedded window when a trigger operation on the second button is received.

[0034] In a possible implementation, the third task is: a task of the first application, or a task of the second application, or a task of the third application.

[0035] In one possible implementation, the page content corresponding to the second task of the second application includes a third button, and the display unit is also used to display an input box in the embedded window when the third button is triggered; display a keyboard when the input box is triggered; and display the input content received in the keyboard in the input box.

[0036] In a possible implementation, the display unit is further configured to continue displaying the embedded window upon receiving the notification message, and to display the notification message in a capsule or banner form on an upper layer of the embedded window.

[0037] In one possible implementation, the display unit is also used to display a second interface, which includes a first switch; when a trigger operation for turning on the first switch is received, a third interface is displayed, which includes an added column and an unadded column, the added column includes identifiers of one or more tasks customized by the user, and the unadded column includes identifiers of one or more tasks provided by the electronic device that have not been added by the user; when an operation for deleting the first target task in the added column is received, the display of the identifier of the first target task is canceled in the added column, and the identifier of the first target task is displayed in the unadded column; or, when an operation for adding a second target task in the unadded column is received, the display of the identifier of the second target task is canceled in the unadded column, and the identifier of the second target task is displayed in the added column.

[0038] In one possible implementation, the not added column includes an identifier of the third target task, and the application corresponding to the third target task is not installed in the electronic device. The display unit is also used to display a prompt message when an operation for adding the third target task in the not added column is received, and the prompt message is used to prompt the installation of the application corresponding to the third target task.

[0039] In a possible implementation, the third interface further includes a second switch and a display unit, and is further configured to display a recommendation identifier in a blank area of ​​the added column when a trigger operation for turning on the second switch is received.

[0040] In one possible implementation, the processing unit is specifically configured to respond to a first preset operation, and when it is determined that the second switch is in the on state, determine the second task of the second application based on a recommendation algorithm, and the recommendation algorithm is related to one or more of the following: time information, the geographic fence in which the user is located, or user-related information in the user portrait; and display an embedded window on the upper layer of the first interface, and the embedded window includes a page corresponding to the second task of the second application.

[0041] In one possible implementation, the processing unit is specifically used to determine that the second task of the second application is a travel task when it is determined based on the recommendation algorithm that the user will travel; or, when it is determined based on the recommendation algorithm that the user will punch in, determine that the second task of the second application is a punch-in task; or, when it is determined based on the recommendation algorithm that the user will pay, determine that the second task of the second application is a payment task; or, when it is determined based on the recommendation algorithm that the user will take a bus, determine that the second task of the second application is a bus code task.

[0042] In a possible implementation, the first application includes an application that supports playing video or audio content. When the electronic device displays the embedded window, the electronic device keeps the first application playing the video or audio.

[0043] In one possible implementation, the processing unit is also used to light up the display screen of the electronic device when the electronic device receives a first preset operation in a black screen or screen-off state; the display unit is also used to display a lock screen interface, and the lower layer of the lock screen interface includes an embedded window; the display unit is also used to display the embedded window when a correct unlock input is received in the lock screen interface.

[0044] In one possible implementation, the display unit is also used to display the lock screen interface when the electronic device receives a first preset operation in the screen-on lock state, and the lower layer of the lock screen interface includes an embedded window; the display unit is also used to display the embedded window when the correct unlock input is received in the lock screen interface.

[0045] In one possible implementation, the processing unit is further used to create a new task for the second application in response to the first preset operation, and the display unit is further used to display an embedded window on the upper layer of the first interface without interrupting the execution of the first task, and the embedded window includes page content corresponding to the second task of the second application.

[0046] In a possible implementation, the processing unit is specifically configured to receive a double-click operation on the back of the electronic device.

[0047] In a third aspect, an embodiment of the present application provides an electronic device, comprising a processor and a memory, wherein the memory is used to store code instructions, and the processor is used to run the code instructions to execute the method described in the first aspect or any possible implementation of the first aspect.

[0048] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is run on a computer, the computer executes the method described in the first aspect or any possible implementation of the first aspect.

[0049] In a fifth aspect, an embodiment of the present application provides a computer program product comprising a computer program, which, when the computer program runs on a computer, enables the computer to execute the method described in the first aspect or any possible implementation of the first aspect.

[0050] In a sixth aspect, the present application provides a chip or chip system, comprising at least one processor and a communication interface, wherein the communication interface and the at least one processor are interconnected via a line, and the at least one processor is configured to execute a computer program or instruction to perform the method described in the first aspect or any possible implementation of the first aspect. The communication interface in the chip may be an input / output interface, a pin, or a circuit.

[0051] In one possible implementation, the chip or chip system described above in this application further includes at least one memory, in which instructions are stored. The memory may be a storage unit within the chip, such as a register, a cache, etc., or a storage unit of the chip (e.g., a read-only memory, a random access memory, etc.).

[0052] It should be understood that the second to sixth aspects of the present application correspond to the technical solutions of the first aspect of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] FIG1 is a schematic structural diagram of an electronic device 100 provided in an embodiment of the present application;

[0054] FIG2 is a schematic diagram of the software structure of the electronic device 100 provided in an embodiment of the present application;

[0055] FIG3 is a schematic diagram of an interface provided in an embodiment of the present application;

[0056] FIG4 is a schematic diagram of the hardware and software framework provided in an embodiment of the present application;

[0057] FIG5 is a schematic diagram of module interaction provided in an embodiment of the present application;

[0058] FIG6 is a schematic diagram of an interface for setting a task provided in an embodiment of the present application;

[0059] FIG7 is a schematic diagram of another interface for setting tasks provided in an embodiment of the present application;

[0060] FIG8 is a schematic diagram of an interface for adjusting the order of tasks provided in an embodiment of the present application;

[0061] FIG9 is a schematic diagram of an interface from a black screen to displaying an embedded window provided by an embodiment of the present application;

[0062] FIG10 is a schematic diagram of an interface from a lock screen to displaying an embedded window provided by an embodiment of the present application;

[0063] FIG11 is a schematic diagram of an interface from a desktop to a display embedded window provided by an embodiment of the present application;

[0064] FIG12 is a schematic diagram of an interface from a video application screen to a display embedded window provided by an embodiment of the present application;

[0065] FIG13 is a schematic diagram of an interface from application A to displaying an embedded window provided by an embodiment of the present application;

[0066] FIG14 is a schematic diagram of an interface from a cold start or loading failure to displaying an embedded window provided by an embodiment of the present application;

[0067] FIG15 is a schematic diagram of an interface showing several possible tasks displayed in an embedded window according to an embodiment of the present application;

[0068] FIG16 is a schematic diagram of an interface for displaying payment tasks in an embedded window according to an embodiment of the present application;

[0069] FIG17 is a schematic diagram of an interface for displaying payment tasks in another embedded window according to an embodiment of the present application;

[0070] FIG18 is a schematic diagram of an interface for displaying outgoing tasks in an embedded window provided by an embodiment of the present application;

[0071] FIG19 is a schematic diagram of an interface for receiving a notification message when an embedded window is displayed according to an embodiment of the present application;

[0072] FIG20 is a schematic diagram of an interface for exiting an embedded window provided in an embodiment of the present application;

[0073] FIG21 is a schematic diagram of another interface for exiting an embedded window provided in an embodiment of the present application;

[0074] FIG22 is a schematic diagram of a window display process provided by an embodiment of the present application;

[0075] FIG23 is a schematic diagram of the hardware structure of the chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0076] To facilitate a clear description of the technical solutions of the embodiments of the present application, some of the terms and technologies involved in the embodiments of the present application are briefly introduced below:

[0077] 1. Launcher: Launcher can be understood as a desktop application (application, APP), which is the entrance to applications for electronic devices using the Android system. It can manage applications and provide functions such as windows.

[0078] 2. System UI: This is also known as the system user interface. In the Android system, System UI runs as an application. It provides the basic display interface for the system, such as the status bar at the top of the screen, the navigation bar at the bottom of the screen, the quick settings bar in the drop-down interface, the notification bar, the lock screen interface, the volume adjustment dialog box, the screenshot display interface, and other interfaces.

[0079] 3. Quick Task Card: This can be understood as a page displaying a specific application function within a window. When a window supports switching between multiple application function pages, it can be said that the window supports switching between multiple Quick Task Cards. The display of Quick Task Cards can be managed by the Launcher, and the specific service content of the Quick Task Cards can be provided by SystemUI.

[0080] It should be noted that the quick task card in the embodiment of the present application is not limited to the same meaning as the card in the negative one screen or the main interface, but can be understood as a custom name for the convenience of description. In possible implementations, the quick task card may also be called any of the following: quick service card, quick function card, task card, quick card, card, quick function page, quick function interface, function page, function interface, etc., which is not specifically limited in the embodiment of the present application.

[0081] 4. Other terms

[0082] In the embodiments of this application, terms such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. For example, the terms "first chip" and "second chip" are used solely to distinguish between different chips and do not define their order. Those skilled in the art will understand that terms such as "first" and "second" do not define the quantity or execution order, and do not necessarily define differences.

[0083] It should be noted that in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0084] In the embodiments of the present application, "at least one" refers to one or more, and "more" 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 previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, a--c, bc, or abc, where a, b, c can be single or multiple.

[0085] 5. Electronic devices

[0086] The electronic devices of the embodiments of the present application may include handheld devices, vehicle-mounted devices, etc. with image processing functions. For example, some electronic devices include: mobile phones, tablet computers, PDAs, laptop computers, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving cars, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks. The terminal equipment in the network (PLMN), etc., is not limited to this in the embodiments of the present application.

[0087] As an example and not a limitation, in the embodiments of the present application, the electronic device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0088] In addition, in the embodiments of the present application, the electronic device can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0089] The electronic devices in the embodiments of the present application may also be referred to as: terminal equipment, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.

[0090] In the embodiments of the present application, the electronic device or each network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also known as main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as the Linux operating system, the Unix operating system, the Android operating system, the iOS operating system, or the Windows operating system. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software.

[0091] In some implementations, if a user wants to use a function of an application loaded on an electronic device, they must click the application icon on the electronic device. After the application is launched, the user must navigate through the various levels of the application's pages to find the function before using it. However, in this implementation, the user's operation of using the application is cumbersome, affecting the user experience.

[0092] Alternatively, in some implementations, users can quickly open an application by tapping on the electronic device, first displaying the application's homepage, and then displaying a page for a specific function within the application. However, in this implementation, a single tap can only open a specific function within one application, and the display process causes the application's page to change, impacting the user experience. Furthermore, if the user wants to open a function in another application, they must perform another tap or other operation, or they must open another application and search for the function within that application's page, which is cumbersome and impacts the user experience.

[0093] In view of this, an embodiment of the present application provides a window display method, in which an electronic device can display an independent window after receiving a preset operation from a user. The window may include a function page of a certain application, so that the user can conveniently use the functions of the application. The window may also provide identification of one or more other functions of the application, and / or identification of one or more functions of other applications. In this way, based on the identification of each function in the window, the user can flexibly switch between different functions of different applications.

[0094] Among them, the independent window can be understood as: the window is not a window in a certain application opened by the user, but can be an independent window provided by the system of the electronic device, the independent window can be covered above any application page displayed by the electronic device, the independent window can embed one or more task entries of the application, and when the task in the independent window is executed, a new task can be established for the application corresponding to the task, so that the execution of the task is independent of other already running tasks in the application, so that the operation of any application displayed on the electronic device is not interrupted when the task of the embedded window is triggered. In this way, the call of the window will not affect the user's current operation, thereby improving the user experience. For example, when a user is watching a video or playing a game on an electronic device, if the user triggers the electronic device to display the window, the video and game can be uninterrupted when the window is displayed.

[0095] An independent window may also be referred to as a window, an embedded window, a quick card pop-up window, a pop-up window, a card application window, a quick card window, a quick function window, a quick function pop-up window, etc., which is not specifically limited in the embodiments of the present application.

[0096] In order to better understand the embodiments of the present application, the structure of the electronic device according to the embodiments of the present application is introduced below:

[0097] 1 shows a schematic structural diagram of an electronic device 100. 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 194, and a subscriber identification module (SIM) card interface 195. 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.

[0098] It should be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

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

[0100] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

[0101] 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 instruction or data again, it can retrieve it from the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

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

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

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

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

[0106] The pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, the pressure sensor 180A can be set on the display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. A capacitive pressure sensor can be a device comprising at least two parallel plates with conductive material. When force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of the pressure based on the change in capacitance. When a touch operation is applied to the display screen 194, the electronic device 100 detects the intensity of the touch operation based on the pressure sensor 180A. The electronic device 100 can also calculate the position of the touch based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities can correspond to different operation instructions.

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

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

[0109] The touch sensor 180K is also called a "touch-sensitive device." 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, at a location different from that of the display screen 194.

[0110] The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture, etc. In the embodiment of the present application, the Android system with a layered architecture is used as an example to exemplify the software structure of the electronic device 100 .

[0111] FIG2 is a block diagram of the software structure of the electronic device 100 according to an embodiment of the present application.

[0112] A layered architecture divides software into several layers, each with distinct roles and responsibilities. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

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

[0114] As shown in FIG2 , the application package may include applications such as camera, system user interface (systemUI), phone, map, phone, music, settings, desktop (launcher), video, social, etc.

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

[0116] As shown in FIG2 , the application framework layer may include a window manager service (WMS), an activity manager service (AMS), a content provider, a resource manager, a view system (view), a notification manager, and the like.

[0117] The window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, touch the screen, drag the screen, take screenshots, etc.

[0118] AMS is used to manage the life cycle of applications, start or kill application processes, schedule tasks, etc.

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

[0120] The view system includes visual controls, such as controls for displaying text and images. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images. The view system in embodiments of the present application can include a View or a Surface View.

[0121] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0122] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically, without requiring user interaction. For example, the Notification Manager can be used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include displaying text messages in the status bar, emitting alert sounds, vibrating the device, or flashing indicator lights.

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

[0124] 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 Android core library.

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

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

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

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

[0129] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

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

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

[0132] For example, in combination with FIG2 , FIG3 shows some interfaces between the application layer and the application framework layer in an embodiment of the present application.

[0133] As shown in Figure 3, the application layer may include an embedded window component package, which may be part of a launcher and may interact with the AMS, WMS, view, and input manager service (input manager service, inputMS) of the application framework layer.

[0134] For example, the embedded window component package may include a startup control module, a task management and state synchronization module, a view embedding and display control module, an interaction control module, and an agent service module.

[0135] The startup control module can interact with the AMS based on the activity startup and exit interface, so that the AMS can start and exit the interface based on the activity, thereby realizing the activity startup management and activity life cycle management of the embedded window.

[0136] The Task management and status synchronization module can interact with WMS based on the Task management and status synchronization interface, and the interaction control module can interact with WMS based on the interface interaction and event delivery interface, so that WMS can implement one or more of the following management based on the Task management and status synchronization interface, as well as the interface interaction and event delivery interface: Task stack management, activity jump control, focus switching control, window visibility management, window hierarchy management, conflg update and compatibility management, insets window management, and input method window management.

[0137] The View embedding and display control module can interact with the view based on the surface control interface, so that the view can implement surface display control based on the surface control interface.

[0138] The proxy service may correspond to the embedded window capability access interface (or task access interface).

[0139] InputMS can be used to dispatch events when receiving user triggers in the embedded window.

[0140] Based on the functional modules of the application layer and the application framework layer in FIG3 , the electronic device can implement an embedded window displayed across tasks, thereby not interrupting the user's current scene.

[0141] For example, when an electronic device receives a user trigger and needs to display an embedded window, the startup control module can call AMS based on the activity startup and exit interface to manage the activity startup and activity lifecycle of the embedded window. The task management and status synchronization module can call WMS based on the task management and status synchronization interface to manage the task stack and create a new task or a new stack. The interaction control module can call WMS's activity jump control based on the interface interaction and event transmission interface to obtain the page content to be displayed in the embedded window from the application accessed by the proxy service. The view embedding and display control module can call the surface view obtained by converting the page content to be displayed in the View based on the surface control interface to display the embedded window. When the embedded window is displayed, WMS can configure the basic parameters of the embedded window based on conflg update and compatibility management. WMS can also manage the status bar (such as WiFi logo, operator logo, etc.) and navigation bar (such as virtual buttons) in the display screen other than the embedded window based on insets window management, so that the status bar and navigation bar will not affect the display of the embedded window.

[0142] During the display process of the embedded window, the embedded window may also receive trigger operations and generate trigger events. InputMS can dispatch these events, and the corresponding modules of WMS will respond to and process these events. For example, when the embedded window receives an operation to switch tasks, the focus switching control of WMS can control the focus switching; when the embedded window receives an operation to enter a lower or upper page, the window hierarchy management of WMS can control the change of the hierarchy in the window; when the embedded window receives an input operation, the input method window management of WMS can manage the input method; when the embedded window receives an operation to cancel the embedded window display, the window visibility management of WMS can control the cancellation of the embedded window display.

[0143] In an embodiment of the present application, when an embedded window is displayed, a new task or a new stack is created so that the running task in the embedded window is independent of the running task of the application, thereby not interrupting the task running by the application.

[0144] It is understandable that when implementing the window display method of the embodiment of the present application, both software logic in the electronic device and some hardware in the electronic device are required. For example, FIG4 shows a schematic diagram of a software and hardware architecture for implementing the method of the embodiment of the present application.

[0145] In a possible implementation, the system application, artificial intelligence (AI) middle platform, and infrastructure in Figure 4 can all be applications running at the application layer. The chip platform and chip algorithm can run at the kernel layer or the application framework layer, and this embodiment of the application does not specifically limit this.

[0146] The following is an example of the workflow of the software and hardware of the electronic device 100, using a scenario in which a user taps the back of a mobile phone to trigger the window display method of an embodiment of the present application.

[0147] When the accelerometer and / or gyroscope detects a tap, a corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the tap into a raw input event, which can include values ​​collected by the accelerometer, gyroscope, audio signals, and / or touch panel (TP) signals. The raw input event is then stored in the kernel layer. The chip algorithm can identify whether the original input event is a mobile phone back knock event based on the mobile phone back knock recognition algorithm, where knocking can refer to multiple consecutive knocks or a single knock. The mobile phone back knock recognition algorithm can include pre-judgment of the information in the original input event, feature extraction, neural network recognition and result output, where the values ​​collected by the acceleration sensor and the gyroscope in the original input event can be core features, and the audio signal and TP signal can be auxiliary features. The neural network can be a model obtained based on machine learning or deep learning training for identifying knocks on the back of the mobile phone. After identifying the mobile phone back knock event, the chip platform can perform software channel interface adaptation in the application framework layer based on the back knock software channel adaptation. The application framework layer can encapsulate the events on the software channel side into an interface callable by the system application. The application layer can call the interface encapsulated by the application framework layer to start an embedded pop-up window. The content to be displayed in the embedded pop-up window may include the function pages of one or more applications configured locally by the user on the mobile phone, and / or, the function pages of one or more applications configured in the cloud. In a possible implementation, the AI ​​middle station can identify the scene in which the user is located. The scene can be related to the user's usage habits, the time the user is in, the user's location, and / or the user's property, etc., and then the AI ​​middle station can determine the quick task card displayed in the embedded window in the content to be displayed based on the scene in which the user is located, and the terminal device can display the quick task card.

[0148] Corresponding to FIG4 , FIG5 exemplarily shows a schematic diagram of the interaction process between the modules in the embodiment of the present application.

[0149] Implementing the window display method of the embodiment of the present application may include a setup phase and a usage phase. The setup phase may refer to the phase of setting the quick task card in the window for subsequent window display. The usage phase may refer to the phase of the electronic device realizing the window display after receiving a user trigger.

[0150] For example, as shown in FIG5 , during the setup phase, the electronic device may provide auxiliary functions in the setup application. The auxiliary functions may include a switch for controlling the quick task card function to be turned on or off, and a settable quick task card identifier. When the switch for controlling the quick task card function to be turned on or off is on, the electronic device may receive one or more quick task card identifiers selected by the user on the auxiliary function page, and / or one or more quick task card identifiers recommended by the cloud. The setup application may then obtain the new quick task card identifier set this time. The setup application may also obtain the previously set quick task card identifier from the database of the desktop application, thereby obtaining a new task list result including the new quick task card identifier set this time and the previously set quick task card identifier. It is understandable that the desktop application database may contain the previously set quick task card identifier, or may not contain the previously set quick task card identifier. The task list result may also be referred to as a task list, a service list result, or a service list, etc., which is not specifically limited in the embodiments of the present application.

[0151] The settings application can further write the status of the switch and the new task list results into the database of the desktop application, thereby updating the database of the desktop application.

[0152] During the use phase: When the electronic device receives a double-click on the back operation, the operation can be processed into a double-click on the back event. The software path based on the chip algorithm transmits the double-click on the back event to the chip platform, and the application framework layer can encapsulate the double-click on the back event of the chip platform through an interface. The desktop application makes an interface callback to the interface encapsulated by the application framework layer. The desktop application loads the task list results from the database of the desktop application and obtains the scene service from the AI ​​center. When the AI ​​returns the current scene service, the desktop application can determine the quick task card corresponding to the current scene service in the task list results in combination with the current scene service, and give priority to displaying the quick task card corresponding to the current scene service. For example, if the current scene service indicates that the user is at the subway entrance, the quick task card that is displayed first may be the quick task card corresponding to the boarding code function.

[0153] When displaying the quick task card, the desktop application can open a window including the quick task card and obtain the service content of the quick task card from the system UI. The system UI can further obtain the service content from the application framework layer and return the surface view to the desktop application. The desktop application can control the display of the quick task card based on the surface view.

[0154] Figures 3 to 5 above implement the logic from the inside of the electronic device, and exemplify the internal implementation of the quick task card window popping up on the electronic device when the user taps the back of the electronic device twice in a row. The possible interface interactions when the window of the embodiment of the present application is displayed will be described in detail below in conjunction with the user interface. The subsequent user interface diagrams will be divided into the quick task card setting stage, the quick task card use stage, and the quick task card closing stage for separate example explanations. Among them, the quick task card setting stage can correspond to Figures 6-8, the quick task card use stage can correspond to Figures 9-19, and the quick task card closing stage can correspond to Figures 20-21.

[0155] It is understandable that the double-clicking operation on the back in Figures 3-5 above can also be replaced by any of the following: N-times tapping the back, N-times tapping function keys (such as volume keys, power keys, power keys, etc.), N-times tapping any area of ​​the electronic device (such as the front, back, side, etc.), specific gesture operations, specific sliding touch operations, sound control, etc. The embodiment of the present application does not limit the specific operation of triggering the display of the embedded window, and it is sufficient to realize the quick display of the embedded window based on one operation. N is a natural number. For the sake of ease of description, the subsequent user interfaces are all explained by taking the double-clicking on the back to trigger the embedded window display of the mobile phone as an example, and the adapted prompt information also prompts to realize the quick task by double-clicking on the back. This example does not constitute a limitation on the operation and prompt information that triggers the display of the embedded window.

[0156] As shown in FIG6 (a), the electronic device may provide an interface for setting up quick function cards, which may include a main switch 601 for turning on or off the quick task cards. The state of the main switch 601 can be on or off. In the interface shown in FIG6 (a), the main switch 601 is in the off state. The interface shown in FIG6 (a) may display a prompt message for prompting "Tap the back of the phone twice to achieve the quick task", and no quick tasks that can be added are displayed.

[0157] Among them, there are at least the following ways to enter the interface as shown in Figure 6 (a): Method 1, in the settings application, trigger in sequence in the order of "Settings-Accessibility-Quick Start and Gestures" to enter the interface of the setting shortcut function card as shown in Figure 6 (a). Method 2, when the embedded window is displayed, a shortcut control for entering the interface of the setting shortcut function card as shown in Figure 6 (a) is provided in the embedded window. The identifier of the shortcut control can be a setting identifier or an editing identifier, etc., which will be explained in conjunction with the diagram when explaining the embedded window display later, and will not be repeated here. Of course, the electronic device can also provide other ways to enter the interface of the setting shortcut function card as shown in Figure 6 (a), and the embodiments of the present application do not specifically limit this.

[0158] When a trigger operation for turning on the main switch 601 is received in the interface shown in FIG. 6 ( a ), the interface shown in FIG. 6 ( b ) may be entered.

[0159] As shown in the interface of Figure 6 (b), the main switch is in the on state. Optionally, there can be a smart recommendation switch 602 below the main switch. The state of the smart recommendation switch 602 can be on or off. When the smart recommendation switch 602 is on, it can support the electronic device to recommend the quick task card displayed in the embedded window to the user based on the scene in which the user is located. When the smart recommendation switch 602 is off, it does not support the electronic device to recommend the quick task card displayed in the embedded window to the user based on the scene in which the user is located. The quick task card displayed in the embedded window is the default or user-defined setting. In the interface shown in Figure 6 (b), the smart recommendation switch 602 is used as an example of the off state. The situation where the smart recommendation switch 602 is on will be described in detail in Figure 7 and will not be described here.

[0160] The interface shown in (b) of Figure 6 also includes an added column and an unadded column. The added column includes the identifiers of M quick task cards that will be displayed in the embedded window pop-up window later, and the unadded column includes the identifiers of L quick task cards provided by the electronic device and capable of supporting display when the embedded window pop-up window is displayed. The number of M and L is not specifically limited in the embodiments of the present application. The identifier of the quick task card in the unadded column can be moved to the added column based on the user's add operation, and the identifier of the quick task card in the added column can be moved to the unadded column based on the user's remove operation.

[0161] For example, as shown in FIG6(b), the identifier of any quick task card in the added column may include: the quick task icon, the name of the quick task, the name of the application described in the quick task, and a removal control 603 for removing the quick task. A quick task can be understood as any function, task, or service in an application. For example, quick tasks can include payment services, scan services, travel services, and clock-in services for various payment applications. In some implementations, functions that support schemes and ShortCut can be used as quick tasks.

[0162] The identifier of any quick task card without an added column may include: the icon of the quick task, the name of the quick task, the name of the application described by the quick task, and an add control 604 for implementing adding the quick task.

[0163] It should be noted that the identifiers of the quick task cards included in the added column and the not added column may belong to tasks in one application or tasks in multiple applications. The identifiers of the quick task cards included in the added column belong to tasks in applications installed in the electronic device. The identifiers of the quick task cards included in the not added column may belong to tasks in applications installed in the electronic device or tasks in applications not installed in the electronic device. For example, task a and task b belong to application A, task c, task d and task e belong to application B, task f belongs to application C, application A and application B belong to applications installed in the electronic device, and application C belongs to an application not installed in the electronic device. The identifier of the quick task card corresponding to the not installed application C can be distinguished from the installed application A and application B by color, size, etc.

[0164] When the add control of task d in the unadded column as shown in Figure 6 (b) receives a user trigger, you can enter the interface shown in Figure 6 (c). As shown in Figure 6 (c), task d is added to the added column, and task d in the adapted unadded column disappears.

[0165] When the add control of task f without an added column as shown in FIG6 (c) receives a user trigger, because application C to which task f belongs is not installed in the electronic device, the interface shown in FIG6 (d) can be entered. As shown in FIG6 (d), a prompt box can be displayed to indicate that application C is not installed and needs to be installed before it can be used, and a control for proceeding to download and a control for canceling download are provided. When the electronic device receives a trigger for the control for proceeding to download, it can jump to the download interface. After completing the download and installation of application C, it can then enter the interface shown in FIG6 (c). The embodiments of the present application do not limit the implementation of downloading and installing and jumping.

[0166] When the electronic device receives a trigger for canceling the download control, it may enter an interface as shown in FIG6(e), which may be the same as FIG6(c), and is not described in detail.

[0167] The user can continue to add content to the added column until the upper limit of the number of tasks allowed to be added to the added column is reached. For example, when the add control of task e in the unadded column as shown in Figure 6 (e) receives a user trigger, the interface shown in Figure 6 (f) can be entered. As shown in Figure 6 (f), task e is added to the added column, task e in the adapted unadded column disappears, and the number of tasks in the added column reaches the upper limit.

[0168] It is understood that in any of the interfaces shown in Figures 6(b)-(e), if the user turns off the main switch, the interface can be returned to Figure 6(a). In any of the interfaces shown in Figures 6(b)-(e), if the user performs a remove control operation on any task in the Added column, the task can be removed from the Added column and displayed in the Unadded column (not shown in the figure).

[0169] Figure 6 illustrates the interface for customizing a quick task card using the smart recommendation switch in the off state. Figure 7 illustrates the interface for customizing a quick task card using the smart recommendation switch in the on state.

[0170] For example, when the smart recommendation switch shown in FIG6(f) receives a user trigger, the interface shown in FIG7(a) may be entered. As shown in FIG7(a), the smart recommendation switch is turned on, and the added column contains 5 tasks customized by the user. Thus, when the user subsequently triggers the display of the embedded window, because the smart recommendation is turned on, the first task displayed by the electronic device in the embedded window may not be the first task a of the 5 tasks customized by the user. Instead, based on the user's scenario, the task that best matches the scenario can be selected from the 5 tasks and any tasks provided by the electronic device's installed application to display as a quick task card.

[0171] That is to say, when the smart recommendation switch is turned on, the electronic device can select one or more tasks that match the scenario of the device from the tasks corresponding to all services that can be provided by the applications installed on the electronic device, and display them in the quick task card.

[0172] When the removal control of task e shown in FIG7 (a) receives a user trigger, the interface shown in FIG7 (b) can be entered. As shown in FIG7 (b), task e is displayed in the unadded column, and task e in the adapted added column disappears. At the same time, a virtual frame mark for prompting the recommendation is displayed in the position behind the task in the added column. In this way, when the user subsequently triggers the display of the embedded window, when the electronic device displays the first task in the embedded window, it can select the task that best matches the scenario from any tasks that can be provided by the applications installed on the electronic device based on the scenario in which the user is located, and display it in a quick task card.

[0173] When the removal control of task d as shown in FIG7 (b) receives a user trigger, the interface as shown in FIG7 (c) can be entered. As shown in FIG7 (c), task d is displayed in the unadded column, and task d in the adapted added column disappears. At the same time, two virtual box logos for prompting recommendations are displayed behind the task in the added column. In this way, when the user subsequently triggers the display of the embedded window and the electronic device displays the first task in the embedded window, it can select the task that best matches the scenario based on the user's scenario and display it in the quick task card from any tasks that can be provided by the applications installed on the electronic device. The specific recommendation method will be explained in the subsequent quick task card usage stage and will not be elaborated here.

[0174] It is understandable that the user can turn off the smart recommendation switch at any time. For example, when the smart recommendation switch receives a user trigger as shown in Figure 7 (c), the interface shown in Figure 7 (d) can be entered, and the smart recommendation switch is in the off state. The virtual box icon for prompting the recommendation is not displayed in the added column.

[0175] The user can also continue to remove tasks from the added column. For example, based on the interface shown in (c) of Figure 7, the electronic device can continue to receive the user's removal operation, remove all tasks from the added task bar, and enter the interface shown in (e) of Figure 7, where all tasks in the added column are displayed as virtual box icons for prompting recommendations. In a possible implementation, the electronic device can also provide a control (not shown in the figure) for removing all tasks in the added task bar with one click in any interface of Figure 7, so as to realize convenient removal of tasks from the added task bar.

[0176] When the smart recommendation switch as shown in Figure 7 (e) receives a user trigger, you can enter the interface shown in Figure 7 (f), and the added column can be automatically filled with the default 5 tasks. The default 5 tasks are applications installed in the electronic device.

[0177] In Figures 6 and 7, the main switch, smart recommendation switch, and added taskbar can all have some features. For example, the main switch can be on or off by default, and the electronic device can also remember the user's operation. The next time the interface including the main switch is displayed, the state of the main switch is the last remembered user setting state. The smart recommendation switch can be on or off by default, and the electronic device can also remember the user's operation. The next time the interface including the smart recommendation switch is displayed, the state of the smart recommendation switch is the last remembered user setting state. The added taskbar can support Changan dragging to adjust the order of tasks.

[0178] For example, FIG8 shows a schematic diagram of an interface for adjusting the order of tasks in an added task bar.

[0179] In the interface shown in Figure 8 (a), the smart recommendation switch is off, and the dotted box icon for prompting recommendations is not displayed in the added task bar. When the user long-presses the icon of task a and moves it toward the position of task c, the interface shown in Figure 8 (b) can be entered. As shown in Figure 8 (b), the positions of tasks a and c in the added task bar have changed. In this way, when the user subsequently triggers the display of the embedded window, the quick-connect task card corresponding to the task at the first position in the added bar can be displayed by default first.

[0180] In the interface shown in FIG8 (a), if the smart recommendation switch receives a user trigger, the interface shown in FIG8 (c) can be entered, and the smart recommendation switch becomes on, and a virtual frame mark for prompting the recommendation is displayed in the added task bar. When the icon of task a in the interface shown in FIG8 (c) receives a long press by the user and moves to the position of task c, the interface shown in FIG8 (d) can be entered. As shown in FIG8 (b), in the added task bar, the positions of task a and task c change, and the position of the virtual frame mark for prompting the recommendation does not change. In this way, when the user subsequently triggers the display of the embedded window, the quick task card corresponding to the task located at the first position of the added bar can be displayed first, or the recommended quick task card corresponding to the scene in which the user is located can be displayed.

[0181] It is understandable that any interface showing an added column in FIG. 6 and FIG. 7 can support adjustment of tasks in the added column, which is similar to the description of FIG. 8 and is not repeated here.

[0182] Figures 6-8 illustrate the interfaces that may be involved in the quick task card setting stage. The following examples illustrate the interfaces that may be involved when the electronic device displays the quick task card in the embedded window based on user triggering after the setting is completed.

[0183] When a user triggers the display of an embedded window, the electronic device may be in different states, for example, the electronic device is in a black screen (or off screen), the electronic device is in a bright screen and locked screen state, the electronic device displays the desktop, the electronic device displays the interface of any application, etc. The way in which the electronic device implements quick display in different states may be different. Figures 9-14 respectively show several possible ways of triggering the display of an embedded window.

[0184] Figure 9 shows a schematic diagram of the interface of an electronic device from a black screen to displaying an embedded window. As shown in Figure 9 (a), the electronic device is a black screen. When the electronic device receives the operation of double-clicking the back, the electronic device can light up the screen and enter the interface shown in Figure 9 (b). There are two possible implementations: Implementation 1. No password is set in the electronic device or the electronic device recognizes a face that can be unlocked, then the electronic device can enter the interface shown in Figure 9 (d) from the interface shown in Figure 9 (b). Implementation 2. The electronic device needs to be unlocked based on the password entered by the user, then the electronic device can first enter the unlocking interface shown in Figure 9 (c) from the interface shown in Figure 9 (b). The next layer of the unlocking interface can display a reduced-scale embedded window (for example, reduced to 90%). After receiving the correct password input on the unlocking interface shown in Figure 9 (c), it enters the interface shown in Figure 9 (d) to display the embedded window.

[0185] The interface shown in (d) of FIG9 can be understood as an interface of an embedded window. The embedded window can be displayed floating on the upper layer of other applications of the electronic device. The embedded window can have a certain degree of transparency. The embedded window can include a detail display area 901 and a task bar 902.

[0186] The details display area 901 can display a quick task card for a task, and the content of the quick task card can be the detailed page of the task. The task bar 902 can display the identifiers of multiple tasks, which can include icons and / or text, etc. The arrangement order of the multiple task identifiers can be the same as or different from the arrangement order in the aforementioned added column. The task displayed in the details display area 901 is one of the tasks in the task bar 902. The identifier of the task displayed in the details display area 901 can be distinguished from the identifiers of other tasks in the task bar 902 based on color, shape, size, selection mark, etc.

[0187] The embedded window as shown in FIG9( d ) may further include an editing control. When the user clicks the editing control, the user may enter the interface for setting a quick task card as shown in FIG6 , which will not be described in detail here.

[0188] In a possible implementation, if the interface shown in FIG9(d) is displayed for a period of time without receiving any user operation, the embedded window display can be exited and the electronic device can re-enter the black screen, thereby saving power consumption caused by false triggering of the embedded window display.

[0189] Figure 10 shows an interface diagram of an electronic device from a lock screen interface to displaying an embedded window. As shown in Figure 10 (a), the electronic device is on and displays the lock screen interface. When the electronic device receives the operation of double-clicking the back, the electronic device can have two possible implementations: Implementation one, if there is no password set in the electronic device or the electronic device recognizes a face that can be unlocked, the electronic device can enter the interface shown in Figure 10 (c) from the interface shown in Figure 10 (a) to the interface shown in Figure 10 (c). Implementation two, if the electronic device needs to be unlocked based on the password entered by the user, the electronic device can first enter the interface shown in Figure 10 (b) from the interface shown in Figure 10 (a), and after receiving the correct password input in the interface shown in Figure 10 (b), enter the interface shown in Figure 10 (c). In a possible implementation, if the interface shown in Figure 10 (c) does not receive any user operation for a period of time, the display of the embedded window can be exited, and the electronic device redisplays the lock screen interface, which can save power consumption caused by false triggering of the embedded window display.

[0190] FIG11 shows a schematic diagram of an electronic device's interface from the desktop to displaying an embedded window. As shown in FIG11 (a), the electronic device displays the desktop. When the electronic device receives an operation of double-clicking the back, the electronic device can enter the interface shown in FIG11 (b) from the interface shown in FIG11 (a). In a possible implementation, if the interface shown in FIG11 (b) is displayed for a period of time without receiving any user operation, the display of the embedded window can be exited, and the electronic device redisplays the desktop.

[0191] Figure 12 shows a schematic diagram of an electronic device's interface from a video application interface to an embedded window display. As shown in Figure 12 (a), the electronic device displays the interface of the video application. When the electronic device receives a double-click operation on the back, the electronic device can enter the interface shown in Figure 12 (b) from the interface shown in Figure 12 (a). When the electronic device displays the interface shown in Figure 12 (b), the video application can be uninterrupted. After the embedded window exits, the electronic device continues to display the playing video, thereby achieving continuous playback of the video application.

[0192] Figure 13 shows an interface diagram of an electronic device from the a interface of application A to the display of an embedded window. As shown in Figure 13 (a), the electronic device displays the a interface of application A. When the electronic device receives the operation of double-clicking the back, the electronic device can enter the interface shown in Figure 13 (b) from the interface shown in Figure 13 (a). The embedded window shown in Figure 13 (b) can also display other pages corresponding to task a of application A. After the embedded window exits, the electronic device continues to display the a interface of application A, and does not affect the operation of application A itself. In other words, the embedded window of the embodiment of the present application is independent of application A and will not interrupt the operation of application A.

[0193] It should be noted that the contents of the embedded windows in the interface shown in (d) of Figure 9, the interface shown in (c) of Figure 10, the interface shown in (b) of Figure 11, the interface shown in (b) of Figure 12, and the interface shown in (b) of Figure 13 are all the same. The difference is that the interface covered under the embedded window is the interface before the embedded window is displayed. Therefore, the contents of the embedded windows in the five interfaces can refer to each other and will not be repeated here.

[0194] It is understandable that when an electronic device starts an embedded window, there may be a cold start or loading failure. After starting the embedded window, the content of the quick task card may not be displayed normally. Before the normal content of the quick task card is displayed, a cold start interface or loading interface may also be displayed in the details display area.

[0195] Exemplarily, Figure 14 shows a schematic diagram of the possible interfaces when the electronic device has a cold start or fails to load. Figure 14 (b) may be the interface shown in Figure 9 (d), the interface shown in Figure 10 (c), the interface shown in Figure 11 (b), the interface shown in Figure 12 (b), or the interface shown in Figure 13 (b). If the electronic device is cold started, before displaying Figure 14 (b), the cold start interface may also be displayed in the embedded window shown in Figure 14 (a). If the electronic device fails to load the content of the quick task card due to poor network or other reasons, before displaying Figure 14 (b), the loading interface may also be displayed in the embedded window shown in Figure 14 (c), and the loading interface may include a loading control. When a trigger for the loading control is received, the interface shown in Figure 14 (b) may be entered.

[0196] It should be noted that the interface shown in (d) of Figure 9, the interface shown in (c) of Figure 10, the interface shown in (b) of Figure 11, the interface shown in (b) of Figure 12, the interface shown in (b) of Figure 13, and the six interfaces shown in (b) of Figure 14 are all explained by taking the quick task card corresponding to task a of application A displayed in the embedded window as an example.

[0197] In a possible implementation, the embedded windows of the six interfaces can also be replaced to display any one of the following: a quick task card corresponding to task b of application A as shown in (a) of Figure 15, a quick task card corresponding to task c of application B as shown in (b) of Figure 15, a quick task card corresponding to task d of application B as shown in (c) of Figure 15, and a quick task card corresponding to task e of application B as shown in (d) of Figure 15.

[0198] When the embedded windows of the six interfaces pop up, the first quick task card displayed is the quick task card of which task, which may be related to whether the smart switch is turned on.

[0199] For example, when the smart recommendation switch is off, the first quick task card displayed when the embedded window pops up can be: the quick task card corresponding to the first task in the added column, or the quick task card corresponding to the task the user last used, or the quick task card corresponding to any task in the added column.

[0200] When the Smart Recommendation switch is on, the first quick task card displayed when the embedded window pops up may be the quick task card corresponding to the task calculated based on the recommendation algorithm. The recommendation algorithm may be based on the user's travel patterns, the current time, the user's geofence, the user's usage habits, the user's occupation, and other factors. In a possible implementation, the user's travel patterns, usage habits, and occupation may be obtained from the user profile based on the user's authorization.

[0201] For example, when the electronic device learns based on the user's itinerary information that the user is about to depart for another destination, after detecting a double-click on the back, the first quick task card displayed when the embedded window pops up may be the quick task card corresponding to the travel task, such as the quick task card corresponding to task e of application B shown in (d) of Figure 15 .

[0202] For example, when the electronic device determines that the user needs to punch in based on the current time, after detecting a double-click on the back, the first quick task card displayed when the embedded window pops up may be the quick task card corresponding to the punch in task (not shown in the figure).

[0203] For example, when the electronic device detects that the user is about to make a payment based on the user's current geofence and detects a double-click on the back, the first quick task card displayed when the embedded window pops up may be the quick task card corresponding to the payment task, such as the quick task card corresponding to Task a of Application A shown in FIG14(b), or the quick task card corresponding to Task c of Application B shown in FIG15(b). Specifically, whether the quick task card corresponding to Task a of Application A or the quick task card corresponding to Task c of Application B is to be determined can also be determined based on the user's usage habits. For example, if the user uses the quick task card corresponding to Task a of Application A more frequently or more times, the quick task card corresponding to Task a of Application A may be displayed first. Alternatively, if the user uses the quick task card corresponding to Task c of Application B more frequently or more times, the quick task card corresponding to Task c of Application B may be displayed first.

[0204] For example, when the electronic device detects that the user is about to take the subway or bus based on the user's current geo-fence, and detects a double-click on the back, the first quick task card displayed when the embedded window pops up may be the quick task card corresponding to the subway boarding code or bus boarding code task (not shown in the figure). Of course, if the user's marked occupation is a subway worker and the user frequently goes to the subway station, the quick task card corresponding to the subway boarding code or bus boarding code task may not be recommended when the user is at the subway station.

[0205] For example, when the electronic device obtains information based on the user's current geographic fence (such as a courier locker fence) about the user scanning a code, and detects a double-click on the back, the first quick task card displayed when the embedded window pops up may be the quick task card corresponding to the code scanning task, such as the quick task card corresponding to task b of application A shown in (a) of FIG15 , or the quick task card corresponding to task d of application B shown in (c) of FIG15 . Whether it is the quick task card corresponding to task b of application A or the quick task card corresponding to task d of application B can also be determined based on the user's usage habits. For example, if the user uses the quick task card corresponding to task b of application A more frequently or more times, the quick task card corresponding to task b of application A can be displayed first, or if the user uses the quick task card corresponding to task d of application B more frequently or more times, the quick task card corresponding to task d of application B can be displayed first.

[0206] The recommendation algorithm can of course be implemented in other ways in combination with actual situations, and the present embodiment does not specifically limit this. It should be noted that the acquisition of any data in the present embodiment is authorized and compliant.

[0207] After the electronic device displays the first quick task card in the embedded window, the embedded window can support the user to switch between quick task cards of various tasks.

[0208] In one possible implementation, the user can swipe left and right or up and down in the embedded window to switch the quick task cards of adjacent tasks. For example, when the quick task card corresponding to task b of application A shown in Figure 15 (a) receives a swipe to the right, the quick task card corresponding to task c of application B as shown in Figure 15 (b) can be entered. When the quick task card corresponding to task c of application B as shown in Figure 15 (b) receives a swipe to the right, the quick task card corresponding to task d of application B as shown in Figure 15 (c) can be entered. When the quick task card corresponding to task d of application B as shown in Figure 15 (c) receives a swipe to the right, the quick task card corresponding to task e of application B as shown in Figure 15 (d) can be entered. Of course, if the quick task card corresponding to task e of application B as shown in Figure 15 (d) receives a swipe to the left, the quick task card corresponding to task d of application B as shown in Figure 15 (c) can be entered, and so on.

[0209] In another possible implementation, the user can trigger any task identifier in the task bar of the embedded window, so that the quick task card displayed in the embedded window switches to the quick task card corresponding to the task identifier triggered by the user. For example, when the task bar below the quick task card corresponding to task b of application A shown in Figure 15 (a) receives a trigger for the identifier of task c, you can enter the quick task card corresponding to task c of application B as shown in Figure 15 (b). Or, when the task bar below the quick task card corresponding to task b of application A shown in Figure 15 (a) receives a trigger for the identifier of task d, you can enter the quick task card corresponding to task d of application B as shown in Figure 15 (c). Or, when the task bar below the quick task card corresponding to task b of application A shown in Figure 15 (a) receives a trigger for the identifier of task e, you can enter the quick task card corresponding to task e of application B as shown in Figure 15 (d). The quick task card displayed in the embedded window can have a variety of interface changes when in use. For example, Figures 16-19 show some relevant interface schematics when using several quick task cards.

[0210] It can be understood that each task in the embedded window can be associated with the interface of the application to which the task belongs. When the quick task card of a task is displayed in the embedded window, the embedded window can start the operation of the task module in the application through the interface of the application associated with the task, thereby providing the embedded window with specific content displayed on the quick task card based on the application, and when a trigger is received in the quick task card, further interface display after being triggered in the quick task card is realized based on the application's own execution logic. The execution logic of the application itself is not specifically limited in the embodiment of this application.

[0211] Figure 16 exemplifies a schematic diagram of the interface changes of the quick task card of the payment task after the payment is completed. As shown in (a) of Figure 16, the embedded window can display the quick task card of the payment task a of application A based on the content provided by the module for implementing task a in application A. The quick task card can include a barcode or QR code that can be used to pay or collect money. After the electronic device determines that the barcode or QR code has been scanned to complete the payment or collection, it can enter the interface shown in (b) of Figure 16 based on application A. The quick task card position can display a prompt message for prompting the completion of payment. In one possible implementation, after the prompt message for prompting the completion of payment is displayed, the embedded window can be exited, and the electronic device is restored to the interface before the embedded window popped up. In this way, the embedded window can be used and exited immediately, which not only provides convenient operation but also does not interrupt the user's use of the electronic device.

[0212] Optionally, the quick task card of the payment task a of application A may also include other payment methods and some hidden content, which may also support user triggering.

[0213] For example, Figure 17 shows a schematic diagram of the interface changes when using hidden options in a quick task card for a payment task. As shown in Figure 17(a), the embedded window displays a quick task card for a payment task a of application A. The quick task card also includes a barcode, a QR code, a payment method a option, and some hidden options. The quick task card for task a shown in Figure 17(a) can also be understood as the root interface.

[0214] When the user slides up in the quick task card in the interface shown in Figure 17 (a), the interface shown in Figure 17 (b) can be entered. As shown in Figure 17 (b), the barcode and QR code in the quick task card move up, and the previously hidden options such as QR code payment, appreciation code and group payment are displayed in the quick task card.

[0215] When the user's trigger operation for group payment is received in the interface shown in Figure 17 (b), the interface shown in Figure 17 (c) can be entered. As shown in Figure 17 (c), the group payment interface is displayed in the quick task card, and the group payment interface can display controls for selecting a chat group.

[0216] When a user triggers a control for selecting a chat group in the interface shown in FIG17(c), the interface shown in FIG17(d) is entered. As shown in FIG17(d), an interface for selecting a chat is displayed in the quick task card. The interface for selecting a chat can display one or more recently forwarded groups and one or more recently chatted groups. Furthermore, the user can select a group in the interface shown in FIG17(d) to initiate a group payment to members of the group.

[0217] When the user triggers the return button in the interface shown in (d) of Figure 17, the quick task card can first return to the previous interface of the interface shown in (d) of Figure 17, and enter the interface shown in (e) of Figure 17. The interface shown in (e) of Figure 17 can be the same as the interface content shown in (c) of Figure 17, and will not be repeated here.

[0218] When the user triggers the return button in the interface shown in Figure 17 (e), the quick task card can return to the previous interface of the interface shown in Figure 17 (e) and enter the interface shown in Figure 17 (f). The interface shown in Figure 17 (f) can be the same as the interface content shown in Figure 17 (b), and will not be repeated.

[0219] It can be understood that the interface shown in (b) of Figure 17 is the root interface of the quick task card of task a, so it does not support returning. If the user triggers the return button in the interface shown in (b) of Figure 17, shaking or other animation effects can be added to the embedded window to prompt the user that the return can no longer be executed.

[0220] For example, Figure 18 shows the interface changes when a keyboard is displayed in a travel-related quick task card. As shown in Figure 18 (a), the embedded window displays a quick task card for travel-related task e from application B. The quick task card includes options such as a ride QR code, ride mode options (such as tools, subway, taxi, and cycling), travel discounts, route planning, and ride history.

[0221] When a trigger operation for route planning is received in the interface shown in (a) of FIG18 , the interface shown in (b) of FIG18 may be entered. As shown in (b) of FIG18 , the route planning interface is displayed in the embedded card. The route planning interface may include options such as setting travel addresses and itinerary reminders.

[0222] When a trigger operation of the input box for inputting an address is received in the interface shown in (b) of Figure 18, if the user has not set the travel address before, the electronic device can enter the interface shown in (c) of Figure 18. As shown in (c) of Figure 18, the electronic device can pop up a keyboard, and at the same time, the height of the quick task card can be reduced, and the quick task card can be moved to the top of the electronic device, so that the user can use the keyboard to input relevant information such as the travel address. After the user finishes using the keyboard, the keyboard display can be further canceled and the display of the quick task card can be restored (not shown in the figure), which will not be described in detail. In this way, when the user triggers the route planning again, the route planning interface with the destination as the travel address can be displayed based on the travel address that the user has entered.

[0223] When the embedded window is displayed, a notification message may also be received. Figure 19 shows a schematic diagram of the interface changes when a notification message is received when using a quick task card.

[0224] As shown in (a) of Figure 19, the quick task card of payment task a of application A is displayed in the embedded window. At this time, if notification message 1 is received, you can enter the interface shown in (b) of Figure 19. The embedded window continues to be displayed as shown in (b) of Figure 19, and message 1 can be displayed in the upper layer of the embedded window in the form of a banner or capsule.

[0225] In the interface shown in (b) of Figure 19, if a trigger operation for opening message 1 is received (such as pulling down a notification or clicking a notification), the interface shown in (c) of Figure 19 can be entered. As shown in (c) of Figure 19, the electronic device can cancel the display of the embedded window and enter the interface corresponding to message 1. Optionally, when returning to the previous page in the interface corresponding to message 1, it is possible to return to the upper-level interface of the message 1 interface in the application of message 1, and the embedded window is no longer displayed. Of course, it is also possible to return to the interface displayed by the embedded window as shown in (a) of Figure 19, which is not specifically limited in the embodiment of the present application.

[0226] In the interface shown in (b) of Figure 19, if Message 1 is not triggered for a period of time, or a trigger to close Message 1 is received, Message 1 can be canceled, and the electronic device continues to display the interface including the embedded window as shown in (a) of Figure 19. In the interface shown in (a) of Figure 19, if the user wants to view the notification message again, the user can perform a pull-down operation from the top of the screen, etc., to enter the interface of the message notification as shown in (d) of Figure 19. The interface of the message notification may include multiple messages, and the embedded window may also be displayed in the lower layer of the message notification interface. If the interface of the message notification is slid up by the user, the electronic device may continue to display the interface including the embedded window as shown in (a) of Figure 19. If a trigger operation for opening Message 1 is received among multiple messages, the interface of Message 1 as shown in (c) of Figure 19 may also be entered.

[0227] It is understood that if the electronic device receives an incoming call while the embedded window is displayed, the incoming call contact information, answer control, and hang-up control may also be displayed in the form of capsules on the upper layer of the embedded window (not shown in the figure). If the user triggers the hang-up control, the electronic device hangs up the call and the embedded window may remain displayed. If the user triggers the answer control, the electronic device answers the call and the embedded window may remain displayed, with the call interface displayed in the form of capsules, or the embedded window may be canceled and the electronic device displays the call interface.

[0228] It should be noted that the above examples describe the possible interfaces involved when using quick task cards. In actual applications, quick task cards can also support providing alternative user interaction interfaces, and implement other tasks, or use other interfaces to implement the above interactions. The above examples do not necessarily limit the use of quick task cards.

[0229] The following is an example of the interface that may be involved in closing the embedded window.

[0230] In one possible implementation, when an electronic device displays an embedded window, if the electronic device detects that the embedded window does not receive a trigger operation within a preset time, the electronic device may close the embedded window. The preset time may be set based on the actual application, for example, it may be set to a shorter time to reduce the interference of the embedded window on the application running in the electronic device.

[0231] Among them, no trigger operation is received within the preset time, which may include: no trigger operation is received within the preset time from the beginning of the embedded window popping up, or no trigger operation is received within the preset time after the interactive process such as scanning the code is completed in the embedded window.

[0232] After the embedded window is closed, the electronic device can restore the interface displayed before the embedded window popped up. The interface that the electronic device can display before the embedded window popped up may include: black screen, off screen, lock screen, desktop, and the interface of any application.

[0233] For example, FIG20 shows an interface diagram in which an embedded window pops up from interface a of application A, a function related to task a of application A is executed in the embedded window, and then the embedded window is closed to return to interface a of application A.

[0234] As shown in (a) of Figure 20, the electronic device can display the a interface of application A. At this time, if the electronic device detects the operation of double-clicking the back of the electronic device, it can enter the interface shown in (b) of Figure 20. As shown in (b) of Figure 20, the electronic device displays an embedded window on the upper layer of the a interface of application A. The embedded window includes a quick task card of payment task a of application A. The quick task card of task a can include a payment code. When the electronic device detects that the payment code is scanned and the payment is completed, it can display the interface shown in (c) of Figure 20. As shown in (c) of Figure 20, the quick task card of task a prompts that the payment is completed. The electronic device can close the embedded window after a preset time and enter the interface shown in (d) of Figure 20 to restore the display of the a interface of application A. The interface shown in (d) of Figure 20 can be the same as the interface content shown in (a) of Figure 20. Of course, if the electronic device displays the interface shown in (b) of Figure 20, if it detects that no trigger or scan is received in the embedded window after the preset time, the electronic device can also enter from the interface shown in (b) of Figure 20 to the interface shown in (d) of Figure 20, and restore the display of interface a of application A.

[0235] That is, in the embodiment of the present application, no matter what kind of interface interaction is performed in task a of application A in the embedded window, when the electronic device closes the embedded window, the electronic device can restore the display of interface a of application interface. The embedded window in the embodiment of the present application is a newly created task and will not cause any interruption or impact on the tasks of other applications.

[0236] In another possible implementation, the electronic device may also close the embedded window based on a user trigger.

[0237] For example, when an electronic device displays an embedded window, if the user swipes up from the bottom of the electronic device screen and holds the swipe up button, the electronic device does not trigger the display of recent tasks, but instead closes the embedded window. Alternatively, if the user swipes inward from the side of the electronic device screen and holds the swipe up button, the electronic device does not trigger the sidebar, but instead closes the embedded window.

[0238] Alternatively, a control for displaying recent tasks may be provided in the embedded window. When the user triggers the control for displaying recent tasks, the embedded window may be closed and the recent tasks may be displayed.

[0239] As shown in Figure 21 (a), the electronic device displays an embedded window, which includes a quick task card for task a of application A and a control for displaying recent tasks. When a user triggers the control for displaying recent tasks, the embedded window can be closed, and the interface shown in Figure 21 (b) can be entered.

[0240] As shown in (b) of Figure 21, a floating window of the most recently run task can be displayed in the interface. If a trigger for the most recently run task 1 is received in the interface shown in (b) of Figure 21, the task 1 interface shown in (c) of Figure 21 can be entered.

[0241] It is understandable that if there is no recently run task, the electronic device can close the embedded window and display the desktop when receiving the user's operation of triggering the control for displaying the most recent task in the interface as shown in (a) of Figure 21.

[0242] Of course, in another possible implementation, a control for closing the embedded window can also be provided in the embedded window (not shown in the figure). When the user operates the control in the embedded window for closing the embedded window, the electronic device can restore the interface displayed before the embedded window pops up.

[0243] Alternatively, upon receiving a preset operation such as a press operation, a touch operation, or a slide operation on some areas in the embedded window, the electronic device may close the embedded window and restore the interface displayed before the embedded window popped up.

[0244] Alternatively, when the electronic device receives a tap operation, voice control, gesture control, etc. for closing the embedded window, it can close the embedded window and restore the interface displayed before the embedded window popped up.

[0245] Alternatively, the electronic device may include functional or physical buttons such as a return button, a desktop button, and a lock screen button. When the electronic device receives a trigger for the return button, it closes the embedded window and restores the interface displayed before the embedded window pops up; when the electronic device receives a trigger for the desktop button, it closes the embedded window and displays the desktop; when the electronic device receives a trigger for the lock screen button, it closes the embedded window and displays the lock screen interface, etc.

[0246] The embodiment of the present application does not limit the specific implementation of closing the embedded window.

[0247] The following is a schematic introduction to the process embodiment of the window display method provided by the embodiment of the present application. It should be noted that the "at..." in the embodiment of the present application can be the instant when a certain situation occurs, or it can be a period of time after the occurrence of a certain situation. The embodiment of the present application does not specifically limit this. As shown in Figure 22, the method includes:

[0248] S2201: Displaying a first interface, where the first interface includes page content corresponding to a first task of a first application.

[0249] The first interface of the embodiment of the present application can be an interface of any application displayed on the electronic device. For example, the first interface can correspond to the interface shown in (a) of Figure 11, (a) of Figure 12, or (a) of Figure 13.

[0250] The first application can be an application currently displayed on the electronic device. The first application can be any application installed on the electronic device, such as a desktop application, a video application, or a game application. The first task of the first application can be any task of the first application, and the page content corresponding to the first task can be provided by the first application. The embodiments of the present application do not limit the specific content displayed on the first interface.

[0251] S2202: Receive a first preset operation.

[0252] In one possible implementation, the first preset operation may be a double-click operation on the back of the electronic device. This operation method is more convenient and easy for users to implement.

[0253] Of course, the first preset operation may also be any alternative to the double-click back operation described in the above embodiment, which will not be described in detail here.

[0254] S2203: In response to the first preset operation, display an embedded window on an upper layer of the first interface without interrupting execution of the first task, wherein the embedded window includes page content corresponding to the second task of the second application.

[0255] The embedded window of the embodiment of the present application can be a window provided by the system of the electronic device that is independent of the first application and the second application. The role and possible names of the embedded window can refer to the records of the aforementioned embodiments. The specific content of the embedded window can refer to the interfaces shown in Figure 9 (d), Figure 10 (c), Figure 11 (b), Figure 12 (b), Figure 13 (b), Figure 14 (b) or Figure 15 (a), (b), (c), (d), etc., which will not be repeated here.

[0256] The running of the embedded window may not affect the execution of the first task. For example, when the first application includes an application that supports playing video or audio content, while the electronic device displays the embedded window, the electronic device keeps the first application playing the video or audio, so that the application originally running on the electronic device can continue to run.

[0257] The second application can be the same application as the first application or a different application from the first application. The second task of the second application can be any application in the second application. The embodiments of the present application do not specifically limit the second application and the second task.

[0258] In a possible implementation, the electronic device can create a new task for the second application corresponding to the second task in the embedded window, so that the second application can provide the page content corresponding to the second task for the embedded window based on the newly created task, without the electronic device jumping to the second application.

[0259] It is understandable that even if the second task of the second application is running in the embedded window and the second application is also running in the background on the electronic device, based on the method of the embodiment of the present application, when the electronic device exits the embedded window displaying the page of the second task of the second application, it can also return to the interface remembered before the second application was running in the background without interrupting the previous operation of the second application. In other words, the task executed by the second application in the embedded window can be independent of the task executed by the second application in the foreground or background of the electronic device.

[0260] S2204: Receive a second preset operation.

[0261] In the embodiment of the present application, the second preset operation can be any operation for exiting the embedded window. For example, reference can be made to Figures 20, 21 or any operation for exiting the embedded window recorded in the above embodiments.

[0262] S2205: In response to the second preset operation, cancel the display of the embedded window and resume displaying the page content corresponding to the first task of the first application.

[0263] In an embodiment of the present application, after the embedded window is canceled, the electronic device can restore the page content of the application before the embedded window pops up, so that the display of the embedded window does not interfere with the application originally running in the electronic device.

[0264] In summary, in the embodiments of the present application, an embedded window can be displayed based on user convenience, and some tasks can be provided to the user in the embedded window, so that the user can conveniently use the tasks in the embedded window, and the embedded window will not interrupt the applications already running in the electronic device when it is displayed, so that the applications already running in the electronic device have better continuity, reduce the interference with the user's use of the application, and improve the user experience.

[0265] In one possible implementation, the page content corresponding to the second task of the second application is displayed in the first area of ​​the embedded window. The embedded window also includes a second area. On the upper layer of the first interface, the second area of ​​the embedded window also displays: a first icon corresponding to the second task, and a second icon corresponding to the third task; wherein the first icon is in a selected state and the second icon is in an unselected state.

[0266] In the embodiment of the present application, the first area can be understood as an area for displaying a quick task card (i.e., the specific page content corresponding to the task), and the second area can be understood as an area for displaying multiple task identifiers. Multiple task identifiers can be user-defined settings, or they can be default or recommended by the electronic device. The task identifier can be a task icon. The task that is displaying the quick task card can be in a selected state in the second area, and other task identifiers that do not display the quick task card can be in an unselected state. The task icon in the selected state can be distinguished from the icon in the unselected state in terms of color, font, animation, etc.

[0267] The contents displayed in the first and second areas of the embedded window can refer to the interfaces shown in (d) of Figure 9, (c) of Figure 10, (b) of Figure 11, (b) of Figure 12, (b) of Figure 13, (b) of Figure 14, or (a), (b), (c), (d) of Figure 15, etc., which will not be further described here.

[0268] In one possible implementation, before receiving the second preset operation, it also includes: receiving a third preset operation for switching the second task to the third task in the embedded window; in response to the third preset operation, displaying the interface content corresponding to the third task in the first area of ​​the embedded window, and displaying the first icon and the second icon in the second area of ​​the embedded window; wherein the first icon is in an unselected state and the second icon is in a selected state.

[0269] In the embodiment of the present application, the third task can be: a task of the first application, a task of the second application, or a task of the third application. In other words, the embedded window can display multiple tasks of one application, or multiple tasks of multiple applications. In this way, users can use different tasks of different applications based on the embedded window, which increases the richness and convenience of use.

[0270] The third preset operation for switching the second task to the third task may be a sliding operation or an operation of triggering a task icon in the second area. For details, please refer to the corresponding description in FIG. 15 , which will not be elaborated here.

[0271] In one possible implementation, after displaying the interface content corresponding to the third task in the first area of ​​the embedded window, the method also includes: receiving a swipe-up operation in the first area of ​​the embedded window; displaying a first button in the first area of ​​the embedded window in response to the swipe-up operation; and when receiving a trigger operation on the first button, displaying the page content associated with the third task of the first button in the first area of ​​the embedded window.

[0272] In an embodiment of the present application, an embedded window can support displaying part of a task page, and hidden content not displayed in the page can be displayed based on a swipe-up operation. The button in the embedded window can also support the content displayed in the embedded window to jump to the next level or multiple levels of pages. This can enrich the content of the embedded window and enable users to achieve more services based on the embedded window. For details, please refer to the description of (a) and (b) of Figure 17. The first button can correspond to the "Group Collection" in Figure 17, which will not be repeated here.

[0273] In one possible implementation, the first button includes a second button in the page content associated with the third task, and the method further includes: when a trigger operation on the second button is received, restoring the display of the interface content corresponding to the first task in the first area of ​​the embedded window.

[0274] In an embodiment of the present application, the second button may refer to a return button, and the embedded window may also support returning to the parent interface based on triggering the return button. For details, please refer to the descriptions of (d), (e) and (f) in Figure 17, which will not be repeated here.

[0275] In one possible implementation, the page content corresponding to the second task of the second application includes a third button, and the method further includes: when the third button is triggered, an input box is displayed in the embedded window; when the input box is triggered, a keyboard is displayed; and the input content received in the keyboard is displayed in the input box.

[0276] In the embodiment of the present application, the embedded window can support keyboard input, so that the user can conveniently input in the embedded window. For details, please refer to the description of (a), (b) and (c) of Figure 18. The third button can correspond to the input box in Figure 18, which is not described here.

[0277] In a possible implementation, after the embedded window is displayed on the upper layer of the first interface, it also includes: receiving a notification message; continuing to display the embedded window, and displaying the notification message in the form of a capsule or banner on the upper layer of the embedded window.

[0278] In the embodiment of the present application, if a notification message is received while an embedded window is displayed, the embedded window can continue to be displayed, and the notification message can be displayed in the form of a capsule or banner above the embedded window. This allows the user to immediately see the notification message even when the embedded window is open. For details, please refer to the descriptions of (a), (b), (c), and (d) of Figure 19, which will not be repeated here.

[0279] In one possible implementation, the method also displays a second interface, which includes a first switch; when a trigger operation for turning on the first switch is received, a third interface is displayed, which includes an added column and an unadded column, the added column includes identifiers of one or more tasks customized by the user, and the unadded column includes identifiers of one or more tasks provided by the electronic device that are not added by the user; when an operation for deleting the first target task in the added column is received, the display of the identifier of the first target task is canceled in the added column, and the identifier of the first target task is displayed in the unadded column; or, when an operation for adding a second target task in the unadded column is received, the display of the identifier of the second target task is canceled in the unadded column, and the identifier of the second target task is displayed in the added column.

[0280] Among them, the second interface can be an interface for displaying the main switch, for example, it can correspond to (a) of Figure 6. The third interface can be an interface for setting tasks, for example, it can correspond to (b) of Figure 6. The first target task can be any task in the added column, and the second target task can be any application that has been installed on the electronic device in the unadded column. The specific setting process can refer to the description of Figure 6 or Figure 7, which is not repeated here. This can support users to conveniently customize the tasks they need.

[0281] In one possible implementation, the not added column includes an identifier of the third target task, and the application corresponding to the third target task is not installed in the electronic device. The method also includes: when an operation for adding the third target task in the not added column is received, a prompt message is displayed, and the prompt message is used to prompt the installation of the application corresponding to the third target task.

[0282] In an embodiment of the present application, when a user selects a task for an application that is not installed on the electronic device, the electronic device can prompt the user to install the application. This allows the user to customize a variety of tasks and is not limited to applications already installed on the electronic device. The third target task can, for example, correspond to "Task f" in Figure 6.

[0283] In one possible implementation, the third interface further includes a second switch, and the method further includes: when a trigger operation for turning on the second switch is received, displaying a recommendation logo in a blank area of ​​the added column.

[0284] The second switch of the embodiment of the present application can correspond to the smart recommendation switch of the above embodiment. When the smart recommendation switch is turned on, if the amount of tasks in the added column does not reach the upper limit of the amount of tasks that can be displayed, a recommendation mark can be displayed in the added column. The recommendation mark can be a virtual box and / or text, etc. For details, please refer to the interface of Figure 7, which will not be repeated here.

[0285] After the smart recommendation switch is turned on, if the user triggers the electronic device to display an embedded window, the task corresponding to the first quick task card displayed in the embedded window can be obtained based on the recommendation algorithm.

[0286] Exemplarily, in one possible implementation, an embedded window is displayed on the upper layer of the first interface, and the embedded window includes the page content corresponding to the second task of the second application, including: in response to the first preset operation, when the second switch is determined to be in the on state, determining the second task of the second application based on a recommendation algorithm, and the recommendation algorithm is related to one or more of the following: time information, the geographical fence where the user is located, or user-related information in the user portrait; an embedded window is displayed on the upper layer of the first interface, and the embedded window includes the page corresponding to the second task of the second application.

[0287] For example, determining the second task of the second application based on the recommendation algorithm includes: when it is determined based on the recommendation algorithm that the user will travel, determining the second task of the second application as a travel task; or, when it is determined based on the recommendation algorithm that the user will punch in, determining the second task of the second application as a punch-in task; or, when it is determined based on the recommendation algorithm that the user will pay, determining the second task of the second application as a payment task; or, when it is determined based on the recommendation algorithm that the user will take a bus, determining the second task of the second application as a bus code task.

[0288] The relevant contents of the recommendation algorithm of the embodiment of the present application can be referred to the records of the aforementioned embodiment, and will not be repeated here. In this way, the electronic device can recommend appropriate quick task cards to the user based on the scene in which the user is located, thereby improving the user experience.

[0289] In one possible implementation, when the electronic device receives a first preset operation in a black screen or screen-off state, the display screen of the electronic device is turned on; the lock screen interface is displayed, and the lower layer of the lock screen interface includes an embedded window; when the correct unlock input is received in the lock screen interface, the embedded window is displayed.

[0290] In the embodiment of the present application, the electronic device can display an embedded window from a black screen or screen-off state based on a simple trigger by the user. For details, please refer to the description of Figure 9, which will not be repeated here.

[0291] In one possible implementation, the method also includes: when the electronic device receives a first preset operation in the screen-on / lock state, displaying the lock screen interface, the lower layer of the lock screen interface includes an embedded window; when the correct unlock input is received in the lock screen interface, displaying the embedded window.

[0292] In the embodiment of the present application, the electronic device can display an embedded window from the screen-on / lock state based on a simple trigger by the user. For details, please refer to the description in Figure 10, which will not be repeated here.

[0293] The window display method according to the embodiment of the present application has been described above. The following describes the apparatus for executing the above-described window display method provided by the embodiment of the present application. Those skilled in the art will appreciate that the method and apparatus may be combined and referenced with each other, and the relevant apparatus provided by the embodiment of the present application may execute the steps in the above-described window display method.

[0294] In order to achieve the above functions, the device for implementing window display includes hardware structures and / or software modules corresponding to the execution of each function. It should be readily apparent to those skilled in the art that, in combination with the method steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0295] In the embodiment of the present application, the functional modules of the device for implementing the window display method can be divided according to the above method examples. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The integrated module can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, other division methods may be used.

[0296] FIG23 is a schematic diagram of the structure of a chip provided in an embodiment of the present application. The chip 2300 includes one or more (including two) processors 2301 , a communication line 2302 , a communication interface 2303 , and a memory 2304 .

[0297] In some embodiments, the memory 2304 stores the following elements: executable modules or data structures, or a subset thereof, or an extended set thereof.

[0298] The method described in the above embodiment of the present application can be applied to the processor 2301, or implemented by the processor 2301. The processor 2301 may be an integrated circuit chip with signal processing capabilities. During the implementation process, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor 2301 or an instruction in the form of software. The above-mentioned processor 2301 can be a general-purpose processor (for example, a microprocessor or a conventional processor), a digital signal processor (digital signal processing, DSP), an application specific integrated circuit (application specific integrated circuit, ASIC), a field-programmable gate array (field-programmable gate array, FPGA) or other programmable logic devices, discrete gates, transistor logic devices or discrete hardware components. The processor 2301 can implement or execute the methods, steps and logic block diagrams related to each processing disclosed in the embodiment of the present application.

[0299] The steps of the method disclosed in the embodiments of the present application can be directly implemented as being executed by a hardware decoding processor, or can be implemented by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as a random access memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable read-only memory (EEPROM). The storage medium is located in the memory 2304, and the processor 2301 reads the information in the memory 2304 and performs the steps of the above method in combination with its hardware.

[0300] The processor 2301 , the memory 2304 and the communication interface 2303 can communicate with each other through the communication line 2302 .

[0301] In the above embodiment, the instructions stored in the memory for execution by the processor may be implemented in the form of a computer program product, wherein the computer program product may be pre-written in the memory or downloaded and installed in the memory in the form of software.

[0302] The present application also provides a computer program product including one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or data center that includes one or more available media integrated. For example, the available medium can include magnetic media (e.g., floppy disk, hard disk or tape), optical media (e.g., digital versatile disc (DVD)), or semiconductor media (e.g., solid state disk (SSD)).

[0303] The present application also provides a computer-readable storage medium. The methods described in the above embodiments can be implemented in whole or in part via software, hardware, firmware, or any combination thereof. Computer-readable media can include computer storage media and communication media, and can also include any medium that can transfer a computer program from one location to another. The storage medium can be any target medium that can be accessed by a computer.

[0304] As one possible design, computer-readable media may include compact disc read-only memory (CD-ROM), RAM, ROM, EEPROM or other optical disc storage; computer-readable media may include magnetic disk storage or other magnetic disk storage devices. Moreover, any connecting line may also be appropriately referred to as a computer-readable medium. For example, if the software is transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of medium. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically using lasers.

[0305] The present application embodiment is described with reference to the flow chart and / or block diagram according to the method, device (system) and computer program product of the embodiment of the present application.It should be understood that each flow process and / or box in the flow chart and / or block diagram and the combination of the flow process and / or box in the flow chart and / or block diagram can be realized by computer program instructions.These computer program instructions can be provided to the processing unit of general-purpose computer, special-purpose computer, embedded processing machine or other programmable data processing equipment to produce a machine, so that the instruction executed by the processing unit of computer or other programmable data processing equipment produces the device for realizing the function specified in one flow chart flow chart or multiple flow charts and / or one block or multiple blocks of block diagram.

Claims

1. A window display method, applied to an electronic device, characterized in that: include: Displaying a first interface, wherein the first interface includes page content corresponding to the first task of the first application; Receiving a first preset operation; In response to the first preset operation, displaying an embedded window on an upper layer of the first interface without interrupting execution of the first task, the embedded window including page content corresponding to the second task of the second application; receiving a second preset operation; In response to the second preset operation, the display of the embedded window is canceled, and the page content corresponding to the first task of the first application is restored to display.

2. The method according to claim 1, characterized in that The page content corresponding to the second task of the second application is displayed in the first area of ​​the embedded window. The embedded window also includes a second area. On the upper layer of the first interface, the second area of ​​the embedded window also displays: a first icon corresponding to the second task, and a second icon corresponding to the third task; wherein the first icon is in a selected state and the second icon is in an unselected state.

3. The method according to claim 2, characterized in that Before receiving the second preset operation, the method further includes: receiving, in the embedded window, a third preset operation for switching the second task to the third task; In response to the third preset operation, the interface content corresponding to the third task is displayed in the first area of ​​the embedded window, and the first icon and the second icon are displayed in the second area of ​​the embedded window; wherein, the first icon is in an unselected state and the second icon is in a selected state.

4. The method according to claim 3, characterized in that After displaying the interface content corresponding to the third task in the first area of ​​the embedded window, the method further includes: Receiving a swipe-up operation in the first area of ​​the embedded window; In response to the swipe-up operation, displaying a first button in the first area of ​​the embedded window; When a triggering operation on the first button is received, the page content associated with the third task by the first button is displayed in the first area of ​​the embedded window.

5. The method according to claim 4, characterized in that The first button includes a second button in the page content associated with the third task, and the method further includes: When a trigger operation on the second button is received, the interface content corresponding to the first task is restored to display in the first area of ​​the embedded window.

6. The method according to any one of claims 2 to 5, characterized in that: The third task is: a task of the first application, or a task of the second application, or a task of the third application.

7. The method according to any one of claims 1 to 6, characterized in that The page content corresponding to the second task of the second application includes a third button, and the method further includes: When the third button is triggered, an input box is displayed in the embedded window; When a trigger for the input box is received, displaying the keyboard; The input content received in the keyboard is displayed in the input box.

8. The method according to any one of claims 1 to 7, characterized in that After the embedded window is displayed on the upper layer of the first interface, the method further includes: Receive notification message; The embedded window continues to be displayed, and the notification message is displayed in a capsule or banner form on an upper layer of the embedded window.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: displaying a second interface, wherein the second interface includes a first switch; When a trigger operation for turning on the first switch is received, a third interface is displayed, the third interface including an added column and a not added column, the added column including identifiers of one or more tasks customized by the user, and the not added column including identifiers of one or more tasks provided by the electronic device but not added by the user; When an operation for deleting the first target task in the added column is received, canceling the display of the identifier of the first target task in the added column, and displaying the identifier of the first target task in the not-added column; Alternatively, when an operation for adding the second target task in the not-added column is received, the display of the identifier of the second target task in the not-added column is canceled, and the identifier of the second target task is displayed in the added column.

10. The method according to claim 9, characterized in that The not-added column includes an identifier of a third target task, and an application corresponding to the third target task is not installed in the electronic device. The method further includes: When an operation for adding the third target task in the unadded column is received, prompt information is displayed, where the prompt information is used to prompt the user to install an application corresponding to the third target task.

11. The method according to claim 9 or 10, characterized in that The third interface further includes a second switch, and the method further includes: When a trigger operation for turning on the second switch is received, a recommendation logo is displayed in a blank area of ​​the added column.

12. The method according to claim 11, characterized in that In response to the first preset operation, displaying an embedded window on an upper layer of the first interface, wherein the embedded window includes page content corresponding to the second task of the second application, includes: In response to the first preset operation, when it is determined that the second switch is in the on state, determining a second task for the second application based on a recommendation algorithm, the recommendation algorithm being related to one or more of: time information, a geofence where the user is located, or user-related information in a user profile; An embedded window is displayed on an upper layer of the first interface, and the embedded window includes a page corresponding to the second task of the second application.

13. The method according to claim 12, characterized in that Determining a second task of the second application based on a recommendation algorithm includes: When it is determined based on the recommendation algorithm that the user will travel, determining the second task of the second application to be a travel-related task; Alternatively, when it is determined based on the recommendation algorithm that the user will clock in, determining the second task of the second application to be a clock-in task; Alternatively, when it is determined based on the recommendation algorithm that the user will make a payment, determining the second task of the second application to be a payment task; Alternatively, when it is determined based on the recommendation algorithm that the user will take a ride, the second task of the second application is determined to be a ride code task.

14. The method according to any one of claims 1 to 13, characterized in that The first application includes an application that supports playing video or audio content. During the process of the electronic device displaying the embedded window, the electronic device keeps the first application playing the video or audio.

15. The method according to any one of claims 1 to 14, characterized in that The method further comprises: When the electronic device receives the first preset operation in a black screen or screen-off state, lighting up the display screen of the electronic device; Displaying a lock screen interface, wherein the lower layer of the lock screen interface includes the embedded window; When a correct unlock input is received in the lock screen interface, the embedded window is displayed.

16. The method according to any one of claims 1 to 15, characterized in that The method further comprises: When the electronic device receives the first preset operation in the screen-on / locked state, the electronic device displays a lock screen interface, wherein the lower layer of the lock screen interface includes the embedded window; When a correct unlock input is received in the lock screen interface, the embedded window is displayed.

17. The method according to any one of claims 1 to 16, characterized in that In response to the first preset operation, displaying an embedded window on an upper layer of the first interface without interrupting execution of the first task, wherein the embedded window includes page content corresponding to the second task of the second application, including: In response to the first preset operation, a new task is created for the second application, and an embedded window is displayed on the upper layer of the first interface without interrupting the execution of the first task. The embedded window includes page content corresponding to the second task of the second application.

18. The method according to any one of claims 1 to 17, characterized in that The receiving of the first preset operation includes: A double-click operation on the back of the electronic device is received.

19. An electronic device, characterized in that: include: A memory and a processor, the memory being used to store a computer program, and the processor being used to execute the computer program to perform the method according to any one of claims 1 to 18.

20. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, which, when executed, enable a computer to perform the method according to any one of claims 1 to 18.

21. A computer program product, characterized in that The device comprises a computer program, which, when executed, causes the electronic device to perform the method according to any one of claims 1 to 18.

Images