Interface display method and related device

Abstract

An interface display method, which relates to the field of terminal software. The method comprises: receiving a first operation to display an event card management interface, wherein the event card management interface comprises a thumbnail of at least one event card, and an unfolded event card comprises a plurality of sub-task cards, each of which is a trigger entry for a sub-function of an application; and receiving a second operation to switch the event card management interface to an application window management interface. In the present application, a plurality of sub-task cards are aggregated in one event card, and each of the sub-task cards is used as a trigger entry for a sub-function of an application; and when a corresponding sub-task card has been selected, a terminal can jump to a corresponding application, such that a user performs operations by using sub-tasks under an event as the granularity, and when performing transaction management, corresponding applications can be triggered by means of directly selecting sub-tasks in an event card instead of opening different applications, thereby reducing operation costs of the user.

Description

Interface display method and related equipment

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on November 22, 2023, with application number 202311572254.6 and application name “An interface display method and related equipment”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of terminals, and in particular to an interface display method and related equipment. Background Art

[0003] The terminal operating system generally maintains a traditional application-centric approach to system interaction. In this application-centric architecture, users may need to switch between multiple applications to complete a task. For example, when traveling, users may use a ticket purchasing app to purchase a plane or train ticket, a hotel booking app to reserve a hotel, and an alarm clock to set a reminder to travel.

[0004] In the application-centric approach, users need to manage different subtasks of an event in multiple different applications. When multiple events exist at the same time, effective event management cannot be achieved.

[0005] Summary of the Invention

[0006] In the first aspect, the present application provides an interface display method, which includes: a terminal device can receive a first operation for triggering the display of an event card management interface, and display the event card management interface, wherein the event card management interface is different from the existing application management interface in that the event card management interface includes a thumbnail of at least one event card; wherein the expanded event card includes multiple sub-task cards, each of the sub-task cards is a trigger entry for a sub-function of the application; and the event card management interface can be switched to the application window management interface through certain operations.

[0007] In an embodiment of the present application, multiple subtask cards can be aggregated into an event card, and each subtask card serves as a trigger entry for a sub-function of an application. When the corresponding subtask card is selected, the terminal can jump to the corresponding application. At this time, the application corresponding to the subtask card can be started and occupy the front-end operation. Through the above method, the user can operate at the granularity of the subtasks under the event. When performing transaction management, there is no need to click on different applications, but directly select the subtask under the event card to trigger the corresponding application, thereby reducing the user's operating cost. And the subtask cards of an event card are aggregated into an event card, which only needs to be managed through the event card, which facilitates the parallel management of multiple events.

[0008] In one possible implementation, the first operation is: a swipe up operation on the bottom of the desktop, or an operation on a preset control, where the preset control is a terminal assistant or a navigation bar; or a selection operation on the first indication information of the at least one event card in the first interface; or a switching operation on the first thumbnail of the application window group in the second interface, and a selection operation on the first indication information of the at least one event card displayed in response to the switching operation.

[0009] In one possible implementation, the first interface also includes second indication information of the application window group; the second indication information of the application window group is arranged after the first indication information of the at least one event card; the second interface also includes second indication information of the at least one event card; the second indication information of the at least one event card is arranged after the first thumbnail of the application window group.

[0010] Among them, the first indication information of at least one event card can be; the first thumbnail of at least one event card; compared with the thumbnail of at least one event card in the event management interface, the first thumbnail of at least one event card is used to trigger the display of the event management interface, and the thumbnail of at least one event card in the event management interface is used to trigger the opening of the event card.

[0011] The second indication information of at least one event card may be: a second thumbnail of at least one event card;

[0012] The first indication information of the application window group may be: a first thumbnail of the application window group;

[0013] The second indication information of the application window group may be: a second thumbnail of the application window group;

[0014] In one possible implementation, the first operation is specifically a sliding operation for a preset control, and the effective distance of the sliding operation in the first operation is within a first preset range; the method also includes: receiving a third operation, displaying the second interface; wherein the third operation is a sliding operation for a preset control, and the effective distance of the sliding operation in the third operation is within a second preset range.

[0015] In a possible implementation, the method further includes: receiving a selection of a thumbnail of a target event card in the at least one event card in the event card management interface, and adding the thumbnail of the target event card to the system desktop for display.

[0016] In a possible implementation, the display status of the thumbnail of the event card in the event card management interface is related to the completion degree of the subtask card in the event card.

[0017] In a possible implementation, the display state is color or transparency.

[0018] In one possible implementation, the method also includes: receiving a fourth operation, displaying the event card corresponding to the to-do event; the fourth operation is selecting the thumbnail of the event card corresponding to the to-do event in the event card management interface; the event card corresponding to the to-do event includes multiple sub-task cards, and each sub-task card is a trigger entry for a sub-function of the application.

[0019] In a possible implementation, the method further includes: upon receiving a fifth operation, switching the event card corresponding to the to-do event to a first interface, where the first interface is an application interface, a system desktop, or an application window management interface.

[0020] In a possible implementation, the multiple subtask cards include a first subtask card and a second subtask card, the first subtask card and the second subtask card correspond to different applications, or the first subtask card and the second subtask card correspond to different functions of the same application.

[0021] In one possible implementation, the method further includes: receiving a request for creating a to-do event input by a user; determining, based on the creation request, requirement information for implementing a plurality of subtasks of the to-do event and an application for executing a function of each subtask;

[0022] The requirement information of the multiple subtasks is used as a query, and a requirement feedback result of each subtask is obtained through interaction with the corresponding application. The requirement feedback result is used to construct the multiple subtask cards.

[0023] In this embodiment of the present application, the system automatically determines associated applications by parsing the event card creation request and calls these associated applications to create subtask cards. This eliminates the need to access each associated application to implement multiple subtasks for a single event; all operations can be completed on the system desktop, eliminating the need for application switching or interface navigating, thus simplifying the event subtask processing process.

[0024] In a possible implementation, the requirement information of the multiple subtasks is information carried in the semantics of the creation request, or information supplemented by the user for the multiple subtasks.

[0025] In a possible implementation, the multiple subtasks include a first subtask and a second subtask;

[0026] The determining of the requirement information for implementing the plurality of subtasks of the to-do event includes:

[0027] Display the edit page of the first subtask;

[0028] receiving first requirement information of the first subtask input by a user on the editing page;

[0029] Upon receiving a sixth operation, switching the edit page of the first subtask to the edit page of the second subtask;

[0030] Requirement information of the second subtask input by the user on the editing page is received.

[0031] In one possible implementation, the method further includes:

[0032] Upon receiving the seventh operation, switching the editing page of the second subtask to the editing page of the first subtask including the first requirement information;

[0033] Second requirement information of the second subtask continuously input by the user on the editing page is received.

[0034] In a second aspect, the present application provides an interface display device, comprising:

[0035] A processing module is used to receive a first operation, trigger the display module to display an event card management interface, and the event card management interface includes a thumbnail of at least one event card; wherein the expanded event card includes multiple sub-task cards, each of which is a trigger entry for a sub-function of the application; and receive a second operation, trigger the display module to switch the event card management interface to the application window management interface.

[0036] In a possible implementation, the first operation is:

[0037] For the swipe-up operation at the bottom of the desktop, or for the operation of a preset control, the preset control is a terminal assistant or a navigation bar; or

[0038] a selection operation on the first indication information of the at least one event card in the first interface; or

[0039] A switching operation on the first thumbnail of the application window group in the second interface, and a selection operation on the first indication information of the at least one event card displayed in response to the switching operation.

[0040] In one possible implementation, the first interface also includes second indication information of the application window group; the second indication information of the application window group is arranged after the first indication information of the at least one event card; the second interface also includes second indication information of the at least one event card; the second indication information of the at least one event card is arranged after the first thumbnail of the application window group.

[0041] In one possible implementation, the first operation is specifically a sliding operation on a preset control, and an effective distance of the sliding operation in the first operation is within a first preset range; the processing module is further configured to:

[0042] A third operation is received, triggering the display module to display the second interface; wherein the third operation is a sliding operation on a preset control, and the effective distance of the sliding operation in the third operation is within a second preset range.

[0043] In a possible implementation, the processing module is further configured to:

[0044] Upon receiving a selection of a thumbnail of a target event card in the at least one event card in the event card management interface, the display module is triggered to add the thumbnail of the target event card to the system desktop for display.

[0045] In a possible implementation, the display status of the thumbnail of the event card in the event card management interface is related to the completion degree of the subtask card in the event card.

[0046] In a possible implementation, the display state is color or transparency.

[0047] In a possible implementation, the processing module is further configured to:

[0048] The fourth operation is received, triggering the display module to display the event card corresponding to the to-do event; the fourth operation is to select the thumbnail of the event card corresponding to the to-do event in the event card management interface; the event card corresponding to the to-do event includes multiple sub-task cards, and each sub-task card is a trigger entry for a sub-function of the application.

[0049] In a possible implementation, the processing module is further configured to:

[0050] Upon receiving the fifth operation, the display module is triggered to switch the event card corresponding to the to-do event to the first interface, where the first interface is an application interface, a system desktop, or an application window management interface.

[0051] In a possible implementation, the multiple subtask cards include a first subtask card and a second subtask card, the first subtask card and the second subtask card correspond to different applications, or the first subtask card and the second subtask card correspond to different functions of the same application.

[0052] In a possible implementation, the processing module is further configured to:

[0053] Receive a request to create a to-do event from the user;

[0054] Determining, based on the creation request, requirement information for implementing a plurality of subtasks of the to-do event and an application for executing a function of each subtask;

[0055] The requirement information of the multiple subtasks is used as a query, and a requirement feedback result of each subtask is obtained through interaction with the corresponding application. The requirement feedback result is used to construct the multiple subtask cards.

[0056] In a possible implementation, the requirement information of the multiple subtasks is information carried in the semantics of the creation request, or information supplemented by the user for the multiple subtasks.

[0057] In a possible implementation, the multiple subtasks include a first subtask and a second subtask;

[0058] The processing module is specifically used to:

[0059] Triggering the display module to display an editing page for the first subtask;

[0060] receiving first requirement information of the first subtask input by a user on the editing page;

[0061] Upon receiving a sixth operation, triggering the display module to switch the editing page of the first subtask to the editing page of the second subtask;

[0062] Requirement information of the second subtask input by the user on the editing page is received.

[0063] In a possible implementation, the processing module is further configured to:

[0064] Upon receiving the seventh operation, triggering the display module to switch the editing page of the second subtask to the editing page of the first subtask containing the first requirement information;

[0065] Second requirement information of the second subtask continuously input by the user on the editing page is received.

[0066] In the third aspect, the present application provides an interface display method, which includes: displaying an event card corresponding to a to-do event, the event card corresponding to the to-do event including multiple sub-task cards and indication information of the to-do event; each of the sub-task cards is a trigger entry for a sub-function of an application, and the event card corresponding to the to-do event indicates that the multiple sub-task cards are associated with the to-do event; upon receiving a fifth operation, switching the event card corresponding to the to-do event to a first interface, which is an application interface, a system desktop, or an application window management interface.

[0067] In an embodiment of the present application, multiple subtask cards can be aggregated into an event card, and each subtask card serves as a trigger entry for a sub-function of an application. When the corresponding subtask card is selected, the terminal can jump to the corresponding application. At this time, the application corresponding to the subtask card can be started and occupy the front-end operation. Through the above method, the user can operate at the granularity of the subtasks under the event. When performing transaction management, there is no need to click on different applications, but directly select the subtask under the event card to trigger the corresponding application, thereby reducing the user's operating cost. And the subtask cards of an event card are aggregated into an event card, which only needs to be managed through the event card, which facilitates the parallel management of multiple events.

[0068] In one possible implementation, before displaying the event card corresponding to the to-do event, the method also includes: receiving a fourth operation; wherein, the fourth operation is the selection of the event card corresponding to the to-do event in the system desktop or the event card management interface, and the system desktop or the event card management interface includes at least one event card including the to-do event; or, the fourth operation is the operation of a preset control, and the preset control is a terminal assistant or a navigation bar.

[0069] In a possible implementation, the multiple subtask cards include a first subtask card and a second subtask card, the first subtask card and the second subtask card correspond to different applications, or the first subtask card and the second subtask card correspond to different functions of the same application.

[0070] In one possible implementation, the method also includes: receiving a first operation, displaying an event card management interface, the event card management interface including at least one event card including the to-do event; wherein the first operation is: a swipe-up operation on the bottom of the desktop of the interface, or an operation on a preset control, the preset control is a terminal assistant or a navigation bar; or, a selection operation for the first indication information of the at least one event card in the first interface; or, a switching operation for the first thumbnail of the application window group in the second interface, and a selection operation for the first indication information of the at least one event card displayed in response to the switching operation.

[0071] In a possible implementation, before displaying the first interface, the method further includes: receiving a first operation, wherein the first operation is an upward swipe operation on the bottom of the desktop of the interface, or an operation on a preset control, and the preset control is a terminal assistant or a navigation bar.

[0072] In one possible implementation, the first interface also includes second indication information of the application window group; the second indication information of the application window group is arranged after the first indication information of the at least one event card; the second interface also includes second indication information of the at least one event card; the second indication information of the at least one event card is arranged after the first thumbnail of the application window group.

[0073] In one possible implementation, the first operation is specifically a sliding operation on a preset control, and the effective distance of the sliding operation is within a first preset range; the method also includes: receiving a third operation, displaying a second interface, the second interface including a first thumbnail of an application window group; wherein the third operation is a sliding operation on a preset control, and the effective distance of the sliding operation is within a second preset range.

[0074] In a possible implementation, the method further includes: receiving a selection of a thumbnail of a target event card in the at least one event card in the event card management interface, and adding the thumbnail of the target event card to the system desktop for display.

[0075] In a possible implementation, the display status of the thumbnail of the event card in the event card management interface is related to the completion degree of the subtask card in the event card.

[0076] In a possible implementation, the display state is color or transparency.

[0077] In a possible implementation, the method further includes: receiving a request for creating the to-do event input by a user;

[0078] Based on the creation request, determine the requirement information of multiple subtasks used to implement the to-do event, and the application used to execute the function of each subtask; use the requirement information of the multiple subtasks as a query, and obtain the requirement feedback results of each subtask through interaction with the corresponding application, and the requirement feedback results are used to construct the multiple subtask cards.

[0079] In this embodiment of the present application, the system automatically determines associated applications by parsing the event card creation request and calls these associated applications to create subtask cards. This eliminates the need to access each associated application to implement multiple subtasks for a single event; all operations can be completed on the system desktop, eliminating the need for application switching or interface navigating, thus simplifying the event subtask processing process.

[0080] In a possible implementation, the requirement information of the multiple subtasks is information carried in the semantics of the creation request, or information supplemented by the user for the multiple subtasks.

[0081] In a possible implementation, the multiple subtasks include a first subtask and a second subtask;

[0082] The determining of the requirement information for implementing the plurality of subtasks of the to-do event includes:

[0083] Display the edit page of the first subtask;

[0084] receiving first requirement information of the first subtask input by a user on the editing page;

[0085] Upon receiving a sixth operation, switching the edit page of the first subtask to the edit page of the second subtask;

[0086] Requirement information of the second subtask input by the user on the editing page is received.

[0087] In one possible implementation, the method further includes:

[0088] Upon receiving the seventh operation, switching the editing page of the second subtask to the editing page of the first subtask including the first requirement information;

[0089] Second requirement information of the second subtask continuously input by the user on the editing page is received.

[0090] In a fourth aspect, the present application provides an interface display device, comprising:

[0091] a processing module, configured to display an event card corresponding to a to-do event, wherein the event card corresponding to the to-do event includes a plurality of subtask cards and indication information of the to-do event; each subtask card is a triggering entry for a sub-function of an application, and the event card corresponding to the to-do event indicates that the plurality of subtask cards are associated with the to-do event;

[0092] Upon receiving the fifth operation, the event card corresponding to the to-do event is switched to the first interface, where the first interface is an application interface, a system desktop, or an application window management interface.

[0093] In a possible implementation, before displaying the event card corresponding to the to-do event, the processing module is further configured to:

[0094] A fourth operation is received; wherein,

[0095] The fourth operation is selecting an event card corresponding to the to-do event on the system desktop or the event card management interface, wherein the system desktop or the event card management interface includes at least one event card including the to-do event; or

[0096] The fourth operation is an operation on a preset control, and the preset control is a terminal assistant or a navigation bar.

[0097] In a possible implementation, the multiple subtask cards include a first subtask card and a second subtask card, the first subtask card and the second subtask card correspond to different applications, or the first subtask card and the second subtask card correspond to different functions of the same application.

[0098] In a possible implementation, the processing module is further configured to:

[0099] Displaying a first interface, wherein the first interface includes first indication information of at least one event card;

[0100] receiving a selection operation for the first indication information of the at least one event card, and displaying an event card management interface; the event card management interface includes at least one event card including the to-do event; or

[0101] A switching operation for the first thumbnail is received, and a second interface is displayed, where the second interface includes the first thumbnail of the application window group.

[0102] In a possible implementation, before displaying the first interface, the processing module is further configured to:

[0103] A first operation is received, wherein:

[0104] The first operation is a swipe-up operation on the bottom of the desktop of the interface, or an operation on a preset control, and the preset control is a terminal assistant or a navigation bar.

[0105] In one possible implementation, the first interface also includes second indication information of the application window group; the second indication information of the application window group is arranged after the first indication information of the at least one event card; the second interface also includes second indication information of the at least one event card; the second indication information of the at least one event card is arranged after the first thumbnail of the application window group.

[0106] In a possible implementation, the first operation is specifically a sliding operation on a preset control, and the effective distance of the sliding operation is within a first preset range; the processing module is further configured to:

[0107] Upon receiving a third operation, a second interface is displayed, wherein the second interface includes a first thumbnail of the application window group; wherein the third operation is a sliding operation on a preset control, and an effective distance of the sliding operation is within a second preset range.

[0108] In a possible implementation, the processing module is further configured to:

[0109] A selection of a thumbnail of a target event card in the at least one event card in the event card management interface is received, and the thumbnail of the target event card is added to the system desktop for display.

[0110] In a possible implementation, the display status of the thumbnail of the event card in the event card management interface is related to the completion degree of the subtask card in the event card.

[0111] In a possible implementation, the display state is color or transparency.

[0112] In a possible implementation, the processing module is further configured to:

[0113] Receiving a request for creating the to-do event input by a user;

[0114] Determining, based on the creation request, requirement information for implementing a plurality of subtasks of the to-do event and an application for executing a function of each subtask;

[0115] The requirement information of the multiple subtasks is used as a query, and a requirement feedback result of each subtask is obtained through interaction with the corresponding application. The requirement feedback result is used to construct the multiple subtask cards.

[0116] In a possible implementation, the requirement information of the multiple subtasks is information carried in the semantics of the creation request, or information supplemented by the user for the multiple subtasks.

[0117] In a possible implementation, the multiple subtasks include a first subtask and a second subtask;

[0118] The processing module is specifically used to:

[0119] Display the edit page of the first subtask;

[0120] receiving first requirement information of the first subtask input by a user on the editing page;

[0121] Upon receiving a sixth operation, switching the edit page of the first subtask to the edit page of the second subtask;

[0122] Requirement information of the second subtask input by the user on the editing page is received.

[0123] In a possible implementation, the processing module is further configured to:

[0124] Upon receiving the seventh operation, switching the editing page of the second subtask to the editing page of the first subtask including the first requirement information;

[0125] Second requirement information of the second subtask continuously input by the user on the editing page is received.

[0126] In a fifth aspect, an embodiment of the present application provides an interface display device, which may include a memory, a processor, and a bus system, wherein the memory is used to store programs, and the processor is used to execute the programs in the memory to perform the first aspect and any optional method thereof.

[0127] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer-readable storage medium is run on a computer, the computer executes the above-mentioned first aspect and any optional method thereof, and the above-mentioned third aspect and any optional method thereof.

[0128] In a seventh aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when run on a computer, enables the computer to execute the above-mentioned first aspect and any optional method thereof, and the above-mentioned third aspect and any optional method thereof.

[0129] In an eighth aspect, the present application provides a chip system comprising a processor configured to support an interface display device in implementing some or all of the functions described in the aforementioned aspects, such as transmitting or processing data or information described in the aforementioned methods. In one possible design, the chip system further comprises a memory configured to store program instructions and data necessary for executing or training the device. The chip system may consist solely of a chip or may include a chip and other discrete components. BRIEF DESCRIPTION OF THE DRAWINGS

[0130] Figure 1 is a schematic diagram of an application architecture;

[0131] Figure 2 is a schematic diagram of an application architecture;

[0132] Figure 3 is a schematic diagram of an application scenario;

[0133] FIG4 is a schematic diagram of an embodiment of an interface display method provided in an embodiment of the present application;

[0134] FIG5 is a schematic diagram of an interface in an embodiment of the present application;

[0135] FIG6 is a schematic diagram of an interface in an embodiment of the present application;

[0136] FIG7 is a schematic diagram of an interface in an embodiment of the present application;

[0137] FIG8 is a schematic diagram of an interface in an embodiment of the present application;

[0138] FIG9 is a schematic diagram of an interface in an embodiment of the present application;

[0139] FIG10 is a schematic diagram of an interface in an embodiment of the present application;

[0140] FIG11 is a schematic diagram of an interface in an embodiment of the present application;

[0141] FIG12A is a schematic diagram of an interface in an embodiment of the present application;

[0142] FIG12B is a schematic diagram of an interface in an embodiment of the present application;

[0143] FIG12C is a schematic diagram of an interface in an embodiment of the present application;

[0144] FIG12D is a schematic diagram of an interface in an embodiment of the present application;

[0145] FIG12E is a schematic diagram of an interface in an embodiment of the present application;

[0146] FIG12F is a schematic diagram of an interface in an embodiment of the present application;

[0147] FIG12G is a schematic diagram of an interface in an embodiment of the present application;

[0148] FIG12H is a schematic diagram of an interface in an embodiment of the present application;

[0149] FIG12I is a schematic diagram of an embodiment of an interface display method provided in an embodiment of the present application;

[0150] FIG13 is a schematic diagram of an embodiment of an interface display device provided in an embodiment of the present application;

[0151] FIG14 is a schematic structural diagram of an execution device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0152] The following describes the embodiments of the present invention in conjunction with the accompanying drawings. The terms used in the embodiments of the present invention are only used to explain the specific embodiments of the present invention, and are not intended to limit the present invention.

[0153] The embodiments of the present application are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0154] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, and this is merely a way of distinguishing the objects of the same attributes when describing them in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0155] It should be understood that when an element or layer is referred to as being “on,” “connected to,” or “coupled to” another element or layer, the element or layer can be directly on, directly connected to, or directly coupled to the other element or layer, or one or more intervening elements or layers may be present. It should also be understood that when an element or layer is referred to as being “between” two elements or layers, the element or layer can be the only element or layer between the two elements or layers, or one or more intervening elements or layers may also be present.

[0156] As used herein, the terms "substantially," "about," and similar terms are used as terms of approximation, not as terms of degree, and are intended to take into account the inherent variations in measurements or calculations that one of ordinary skill in the art would recognize. Furthermore, the use of "may" when describing embodiments of the present invention refers to "one or more possible embodiments." As used herein, the terms "use," "using," and "used" may be considered synonymous with the terms "utilize," "utilizing," and "utilized," respectively. Additionally, the term "exemplary" is intended to refer to an example or illustration.

[0157] Refer to FIG1 , which is a schematic structural diagram of an electronic device 100 provided in an embodiment of the present application.

[0158] The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0159] It should be understood that the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown, 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.

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

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

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

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

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

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

[0166] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface, enabling the function of answering calls via a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

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

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

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

[0170] The USB interface 130 is an interface that complies with USB standards and may be a Mini USB interface, a Micro USB interface, a USB Type-C interface, or the like. The USB interface 130 can be used to connect a charger to charge the electronic device 100, or to transfer data between the electronic device 100 and peripheral devices. It can also be used to connect headphones to play audio. This interface can also be used to connect other electronic devices, such as augmented reality devices.

[0171] It is understood that the interface connection relationship between the modules illustrated in the embodiment of the present invention is merely an illustrative illustration and does not constitute a structural limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods from the above embodiments, or a combination of multiple interface connection methods.

[0172] The charging management module 140 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also provide power to the electronic device via the power management module 141.

[0173] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and provides power to the processor 110, the internal memory 121, the display 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

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

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

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

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

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

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

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

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

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

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

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

[0185] The digital signal processor is used to process digital signals. In addition to processing digital image signals, it can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

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

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

[0188] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be stored on the external memory card.

[0189] The internal memory 121 can be used to store computer executable program codes, which include instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the electronic device 100 by running instructions stored in the internal memory 121 and / or instructions stored in a memory provided in the processor.

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

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

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

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

[0194] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to or disconnected from the electronic device 100 by inserting it into or removing it from the SIM card interface 195. The electronic device 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, and the like. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the multiple cards can be the same or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as calls and data communications. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

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

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

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

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

[0199] As shown in FIG2 , the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and short message.

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

[0201] As shown in FIG2 , the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.

[0202] 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, take screenshots, etc.

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

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

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

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

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

[0208] Android Runtime includes core libraries and a virtual machine. Android runtime is responsible for scheduling and management of the Android system.

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

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

[0211] The system library can include multiple functional modules, such as the surface manager, media libraries, and 3D graphics processing libraries (such as OpenGL ES).

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

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

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

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

[0216] Referring to Figure 3, Figure 3 is a schematic diagram of an application architecture of an embodiment of the present application, which includes user 001 and electronic device 002. User 001 is usually the owner of electronic device 002, and uses electronic device 002 to obtain network information and communicate with others. Electronic device 002 may be equipped with an operating system and have various software installed, such as call applications, text messages, instant messaging software, email applications, etc. The electronic device receives user input such as voice and gestures to change the presented interface.

[0217] The terminal operating system generally maintains a traditional application-centric approach to system interaction. In this application-centric architecture, users may need to switch between multiple applications to complete a task. For example, when traveling, users may use a ticket purchasing app to purchase a plane or train ticket, a hotel booking app to reserve a hotel, and an alarm clock to set a reminder to travel.

[0218] In the application-centric approach, users need to manage different subtasks of an event in multiple different applications. When multiple events exist at the same time, effective event management cannot be achieved.

[0219] The technical problem to be solved by the embodiments of the present application is that the existing operating system is application-centric, and users need to manage different subtasks of an event in multiple different applications. When multiple events exist at the same time, effective management of the events cannot be achieved.

[0220] To solve the above problem, referring to FIG. 4 , FIG. 4 is a flow chart of an interface display method provided in an embodiment of the present application. As shown in FIG. 4 , an interface display method provided in an embodiment of the present application includes:

[0221] 401. Upon receiving a first operation, an event card management interface is displayed, wherein the event card management interface includes a thumbnail of at least one event card; wherein the expanded event card includes multiple subtask cards, and each subtask card is a trigger entry for a sub-function of an application.

[0222] 402. Upon receiving a second operation, switch the event card management interface to an application window management interface.

[0223] Next, we will introduce how to enter the event card management interface:

[0224] Method 1: Operations on preset controls.

[0225] The preset control may be a terminal assistant or a navigation bar.

[0226] In a possible implementation, the event card management interface may be called out through a first operation on the terminal assistant or the navigation bar.

[0227] For example, if the terminal assistant is an AI assistant control, users can perform preset interactive operations with the AI ​​assistant control, which will display several obscured card decks on the back of the AI ​​assistant control. After the card decks appear, swipe up to enter the event card management interface. Alternatively, swipe up directly on the AI ​​assistant control to enter the event card management interface.

[0228] For example, referring to Figure 9, the user can first click the navigation bar to call out the AI ​​assistant control. Then, long-press the AI ​​assistant control to display several stacked cards on the back of the AI ​​assistant control. Alternatively, long-press the navigation bar to display the AI ​​assistant control and display several stacked cards on the back of the AI ​​assistant control.

[0229] The stacked cards on the back of the AI ​​Assistant control refer to event cards, and the number of stacked cards corresponds to the number of event cards. Swipe up again, and several stacked cards will be displayed on the back of the AI ​​Assistant control to expand and display all currently existing event cards, that is, enter the event card management interface. In this process, you can cooperate with the animation display to move the card on the back of the AI ​​Assistant control to the middle of the screen to indicate that the card on the back of the AI ​​Assistant is a thumbnail card of the event card, and the event card in the event card management page is the expansion of the card on the back of the AI ​​Assistant.

[0230] It should be understood that when the AI ​​assistant control is resident on the desktop, you can interact with the AI ​​assistant control directly without having to operate the navigation bar to trigger the AI ​​assistant control.

[0231] In one possible implementation, by operating the terminal assistant or navigation bar, the first thumbnail group of the event card group and the first thumbnail group of the application window group can be called out. The user can choose to enter the event card management interface or the application window management interface by selecting different card groups.

[0232] Specifically, in one possible implementation, the first thumbnail of the event card group or the first thumbnail of the application window group can be called out through the first operation on the terminal assistant or the navigation bar, and the user can choose to open the event card management interface or the application window management interface through the switching operation.

[0233] For example, the event card management interface can be opened by selecting the first indication information of at least one event card in the event card group in the first interface.

[0234] For example, the first thumbnail of the application window group can be switched to the first indication information of the at least one event card by a switching operation on the first thumbnail of the application window group in the second interface, and the event card management interface can be opened by a selection operation on the first thumbnail of the event card group with respect to the first indication information of the at least one event card in the first interface.

[0235] Taking the AI ​​Assistant as an example, in one possible implementation, after long pressing and swiping up on the AI ​​Assistant control, two card decks will be displayed: one for event cards (this card deck is not the event card management interface itself, but its thumbnail), and the other for application windows (this window group is not the application window management interface itself, but its thumbnail). Users can choose to enter the event card management interface or the application window management interface by selecting different card decks.

[0236] For example, using a continuous gesture, long press the AI ​​Assistant space and then swipe up. The interface will display two card groups. The event card group is displayed by default, and some application window groups can also be displayed. If you stay at the location of the time card group, you will enter the event card management interface. If you swipe right, the application window group will be fully displayed, and the event card group will not be displayed or only partially displayed. Then click the application window group to enter the application window management interface.

[0237] Figure 10 shows the event card management interface and the application window management interface entered under the same operation path. After long pressing the AI ​​assistant icon, swipe up to call out the card deck, and the event card deck is displayed on the screen by default. Move the touch point of the sliding gesture to the event card and release it, or release the sliding gesture and then click the event card deck to enter the event card management interface. This corresponds to the upper branch in Figure 10. After swiping up, continue to swipe right, or release the swipe up gesture and then perform the right swipe gesture. The event card group moves to the right and gradually displays the application window group. Click the application window group to enter the application window management interface. This corresponds to the lower branch in Figure 10.

[0238] In one possible implementation, in order to prompt the user to switch between the thumbnails of the application window management interface and the thumbnails of the event card management interface, the thumbnails of the event card group can also be displayed on the interface displaying the thumbnails of the application window management interface (the thumbnails of the event card management interface are not as conspicuous as the thumbnails of the application window management interface, for example, they can be arranged after the thumbnails of the application window management interface).

[0239] For example, a first interface can be displayed, and the first interface may include the first indication information of at least one event card, the first thumbnail of the event card group, and the second indication information of the application window group; and the second indication information of the application window group is arranged after the first thumbnail of the event card group of the first indication information of the at least one event card; after receiving a switching operation for the first thumbnail of the application window group in the second interface, the first interface can be switched to the second interface, and the second interface includes the first thumbnail of the application window group and the second indication information of the at least one event card; the second indication information of the at least one event card is arranged after the first thumbnail of the application window group.

[0240] Referring to Figure 12A, Figure 12A shows the interfaces of the thumbnail of the application window group and the thumbnail of the event card group, respectively. The thumbnail of the application window group and the thumbnail of the event card group have two layers of cards, which correspond to the thumbnail of the application window group and the thumbnail of the event card group, respectively, and are arranged front to back along the line of sight: in the thumbnail interface of the event card group, the event card list is located in the front, occupying a larger display area, and the application window list is located in the back; in the thumbnail interface of the event card group, the application window list is located in the front, occupying a larger display area, and the event card list is located in the back.

[0241] When a swipe-up gesture is performed in the blank area of ​​the thumbnail of the application window group and the thumbnail of the event card group in Figure 12A (or the display area of ​​the AI ​​assistant control), you can switch between the interfaces of the thumbnail of the application window group and the thumbnail of the event card group.

[0242] In Figure 12A, the application window group in the event card management interface may not support interaction, that is, sliding in the thumbnail area of ​​the application window group will not change the application windows in the application window group. Correspondingly, the event card group in the application window management interface may not support interaction, that is, sliding in the thumbnail area of ​​the event card group will not change the application windows in the event card group. Of course, the application window group in the event card management interface and the event card group in the application window management interface can also be designed to support interaction. When interaction is supported, by sliding left and right, the application windows in the application window group / event cards in the event card group can be driven to slide left and right.

[0243] Although the interfaces of the application window group thumbnail and the event card group thumbnail are described as two interfaces in the above description, it can be seen from Figure 12A that these two interfaces are essentially two displays of content with different focuses of one interface. Therefore, in other descriptions, they can also be described as two form switches of one interface.

[0244] In the example of the above embodiment, the desktop is used as an example for illustration. In the in-application scenario, still taking the AI ​​assistant control as an example, the AI ​​assistant control, as a system-level global control, can call out the AI ​​assistant control through a preset interactive method, so as to enter the time card management interface through the interaction of the AI ​​assistant control. For example, full-screen mobile phones are generally configured with a navigation bar at the bottom, and the AI ​​assistant control is called out by interacting with the navigation bar (such as replacing the navigation bar with the AI ​​assistant control, or displaying the AI ​​assistant control above the navigation bar). When the AI ​​assistant control is called out in the in-application interface, at least one event card can also be displayed, for example, in the form of a small window.

[0245] Refer to Figure 11. In Figure 11, a user long-presses the bottom navigation bar within the instant messaging software interface to bring up the AI ​​Assistant control, which displays the most recently created or recently opened event cards in a small window. After calling up the event card, the user can interact with the AI ​​Assistant control and perform preset actions such as long-pressing and swiping up to enter the event card management interface and perform event card management functions.

[0246] Method 2: Swipe up from the bottom of the desktop

[0247] It should be understood that, similar to the existing application window management interface, the display of the event card management interface can be triggered by sliding up on the bottom of the desktop of the interface.

[0248] The system can provide a preset gesture. Swipe up on the bottom of the desktop. If the swiping distance is within the preset range, the event card management interface will be entered.

[0249] As shown in Figure 8, the user swipes up from the bottom of the screen. If the swiping distance is within the preset range, the desktop enters the event card management interface from the main screen interface. Animation transition can be used in the middle. For example, the event cards in the event card list gradually appear from the bottom and move to the preset area on the screen with the swiping gesture.

[0250] In some cases, when an event involves a relatively simple task, users may also need to use a single application. For example, for a reading event, users only need to use a single reading app. Therefore, users also need to access application management through the multi-application management interface.

[0251] Therefore, in the operating system, there will be both event-centered and application-centered requirements. In the existing full-screen gestures, when the user swipes up from the bottom of the screen and the swipe distance meets the preset threshold, the application window management interface is entered.

[0252] In the solution of the present invention, the bottom of the screen is swiped up, and the swiping distance is used to determine whether to enter the event card management interface or the application window management interface. For example, three thresholds x1, x2, and x3 are defined respectively. If the swiping distance is within the interval (x1, x2), the event card management interface is entered. If the swiping distance is within the interval (x2, x3), the application window management interface is entered. The application window management interface displays a list of application windows currently running in the operating system.

[0253] In one possible implementation, the event card management interface displays not only the current event card but also a list of application windows, and can be switched from the event card management interface to the application window management interface by executing a preset operation. Correspondingly, the application window management interface also displays an event card group, and can be switched from the application window management interface to the event card management interface by executing a preset operation.

[0254] For example, in one possible implementation, the user's first operation can be received, and a thumbnail of the event card management interface is displayed (or the event card management interface is directly displayed), wherein the first operation is specifically a sliding operation on a preset control, and the effective distance of the sliding operation in the first operation is within a first preset range (for example, (x1, x2)); the user's third operation can also be received, and the second interface is displayed, and the second interface includes a thumbnail of the application window management interface (or the application window management interface is directly displayed); wherein the third operation is a sliding operation on a preset control, and the effective distance of the sliding operation in the third operation is within a second preset range (for example, (x2, x3)).

[0255] The above describes how to open the event card management interface and how to switch between the event card management interface and the application window management interface. Next, we will introduce other operations related to the event card management interface.

[0256] In one possible implementation, event cards can be managed on the event card management interface. Placing a touch on an event card and swiping up deletes the event card. If the swipe up distance is insufficient, the event card automatically returns to the event card list. After deletion, the event card is removed from the system and no longer displayed on the home screen.

[0257] In one possible implementation, you can select an event card and enter the event card. Optionally, the displayed content after selecting the event card can be the same as the result of clicking the event card on the desktop. The difference is that in the event card management interface, a thumbnail of the event card is displayed, and the content of the event card can be previewed, while the desktop is a preview of key information.

[0258] In one possible implementation, you can long press an event card to add the event card to the desktop, that is, when a selection of a thumbnail of a target event card in at least one event card in the event card management interface is received (for example, a long press operation), the thumbnail of the target event card is added to the system desktop for display.

[0259] In a possible implementation, the display state of the thumbnail of the event card in the event card management interface is related to the completion degree of the subtask card in the event card. For example, the display state is color or transparency.

[0260] Event cards can also use different colors and transparency levels to indicate the execution status of the corresponding event. When the task corresponding to the task card in the time card is completed, the corresponding transparency level will be changed. For example, you can define the event progress as 0, 25%, 50%, 75%, and 100%, corresponding to opacity to full transparency. When the subtask corresponding to a task card is completed, if the corresponding ratio is reached, the transparency level of the card will be changed.

[0261] In one possible implementation, event cards can also display their type through superscripts. For example, events corresponding to event cards can be categorized into long-term events and short-term events based on the number of subtasks they contain and the corresponding time span, with different superscripts used to indicate different types.

[0262] Similar to the application window management interface, the event card management interface can display thumbnails of one or more currently created event cards. However, unlike the application window management interface, event cards are added to the event card management interface after creation and can be viewed in the event card management interface, rather than only viewing event cards that are currently open or have been opened in the past time period. Optionally, in the event card management interface, multiple event cards can be stacked on top of each other. As the user slides, different event cards can be switched to the middle of the interface and displayed on the top layer.

[0263] In the embodiment of the present application, the operating system presents information to the user using events as the dimension. Therefore, the operating system also provides an event management interface (i.e., the event card management interface in the embodiment of the present application). The event card management interface displays all event cards created by the user that have not yet been destroyed. Optionally, if all subtask cards within an event card are completed, the event card can be automatically destroyed by the system, or the user can trigger the destruction of the event card by performing a preset operation on the event card.

[0264] For example, referring to Figure 6, Figure 6 shows an event card management page and an expanded event card. The event card management page in Figure 6 displays two stacked event cards. As shown in Figure 6, after clicking the Shanghai business trip event card on the event card management page, the event card expands (at this time, the system task is still a desktop application) and displays multiple subtask cards included in the event card. The subtask cards in Figure 6 include a flight card, an accommodation card, a weather card, and an alarm card. These four subtask cards are all subtasks directly related to the Shanghai business trip itinerary and serve the Shanghai business trip event.

[0265] When an event card corresponding to a to-do event is selected in the event card management interface, an event card may be presented. The event card corresponding to the to-do event includes multiple subtask cards and information indicating the to-do event; each subtask card is a trigger entry for a sub-function of an application, and the event card corresponding to the to-do event indicates that the multiple subtask cards are associated with the to-do event.

[0266] The event card corresponding to the to-do event is a page for managing the granularity of multiple subtasks associated with the to-do event.

[0267] Among them, the event in the embodiment of the present application can be a combination of multiple subtasks. In other words, the event can be a goal that the user needs to achieve, and the subtask is the specific means to achieve the goal. In the prior art, the granularity of user transaction management is subtask.

[0268] For example, a to-do event may be a business trip, and subtasks associated with the to-do event may include booking air tickets, booking hotels, setting alarms, checking the weather at the destination, and the like.

[0269] In existing implementations, in order to complete to-do events, users are required to open multiple applications separately to perform different subtasks. For example, they need to open a flight booking application to execute the flight booking task, open a hotel booking application to execute the hotel booking task, and open a weather query application to execute the destination weather query task.

[0270] In an embodiment of the present application, multiple subtask cards can be aggregated into an event card. Each subtask card serves as a trigger entry for a sub-function of an application. When the corresponding subtask card is selected, the terminal can jump to the corresponding application. At this time, the application corresponding to the subtask card can be started and occupy the front-end operation. Through the above method, users can operate at the granularity of subtasks under the event. When managing transactions, there is no need to click on different applications. Instead, the corresponding application can be triggered by directly selecting the subtask under the event card, thereby reducing the user's operating costs.

[0271] It should be understood that the functions implemented by different subtask cards may be sub-functions of different applications, or different sub-functions of the same application.

[0272] For example, subtask card A is sub-function A of application A, and subtask card B is sub-function B of application B.

[0273] For example, subtask card A is sub-function A of application A, and subtask card B is sub-function B of application A.

[0274] It should be understood that the application in the embodiments of the present application can be an application installed on the terminal, or it can be other forms of applications, such as H5 applications on the cloud side, and this application is not limited.

[0275] In one possible implementation, the information of the to-do event may be an event card, and the event card may indicate that multiple subtask cards are associated with the to-do event by aggregating multiple subtasks. In order to indicate the to-do event itself, the indication information of the to-do event may be displayed, for example, by using the text of the to-do event as a title to indicate the to-do event.

[0276] For example, referring to Figure 6, Figure 6 shows an event card management page and an expanded event card. The event card management page in Figure 6 displays two stacked event cards. As shown in Figure 6, after clicking the Shanghai business trip event card on the event card management page, the event card expands (at this time, the system task is still a desktop application) and displays multiple subtask cards included in the event card. The subtask cards in Figure 6 include a flight card, an accommodation card, a weather card, and an alarm card. These four subtask cards are all subtasks directly related to the Shanghai business trip itinerary and serve the Shanghai business trip event.

[0277] Referring to FIG. 12I , FIG. 12I is a flow chart of a display method, including:

[0278] 1201. Display the event card corresponding to the to-do event, wherein the event card corresponding to the to-do event includes multiple sub-task cards and indication information of the to-do event; each of the sub-task cards is a trigger entry for a sub-function of the application, and the event card corresponding to the to-do event indicates that the multiple sub-task cards are associated with the to-do event.

[0279] The event card corresponding to the to-do event is a page for managing the granularity of multiple subtasks associated with the to-do event.

[0280] Among them, the event in the embodiment of the present application can be a combination of multiple subtasks. In other words, the event can be a goal that the user needs to achieve, and the subtask is the specific means to achieve the goal. In the prior art, the granularity of user transaction management is subtask.

[0281] For example, a to-do event may be a business trip, and subtasks associated with the to-do event may include booking air tickets, booking hotels, setting alarms, checking the weather at the destination, and the like.

[0282] In existing implementations, in order to complete to-do events, users are required to open multiple applications separately to perform different subtasks. For example, they need to open a flight booking application to execute the flight booking task, open a hotel booking application to execute the hotel booking task, and open a weather query application to execute the destination weather query task.

[0283] In an embodiment of the present application, multiple subtask cards can be aggregated into an event card. Each subtask card serves as a trigger entry for a sub-function of an application. When the corresponding subtask card is selected, the terminal can jump to the corresponding application. At this time, the application corresponding to the subtask card can be started and occupy the front-end operation. Through the above method, users can operate at the granularity of subtasks under the event. When managing transactions, there is no need to click on different applications. Instead, the corresponding application can be triggered by directly selecting the subtask under the event card, thereby reducing the user's operating costs.

[0284] It should be understood that the functions implemented by different subtask cards may be sub-functions of different applications, or different sub-functions of the same application.

[0285] For example, subtask card A is sub-function A of application A, and subtask card B is sub-function B of application B.

[0286] For example, subtask card A is sub-function A of application A, and subtask card B is sub-function B of application A.

[0287] It should be understood that the application in the embodiments of the present application can be an application installed on the terminal, or it can be other forms of applications, such as H5 applications on the cloud side, and this application is not limited.

[0288] In one possible implementation, the information of the to-do event may be an event card, and the event card may indicate that multiple subtask cards are associated with the to-do event by aggregating multiple subtasks. In order to indicate the to-do event itself, the indication information of the to-do event may be displayed, for example, by using the text of the to-do event as a title to indicate the to-do event.

[0289] The event card corresponding to the to-do event can be the expanded interface of the event card. The following describes how to open the event card:

[0290] Method 1: By performing preset operations on the event card thumbnail on the system desktop

[0291] In one possible implementation, the system desktop may display one or more event card thumbnails (including event cards corresponding to to-do events). Users can select an event card thumbnail to fully display the event card and expand the subtask cards within the event card. An event card is not a loose card container, but rather a collection of multiple subtask cards closely related to the same event.

[0292] The event card thumbnail can display the information of the included subtasks (or key information, such as instruction information, based on which the user can know which subtasks the event card includes). Optionally, the event card thumbnail will display the information of at least one subtask card and can change over time, for example, preview information of all subtask cards included in the current event card thumbnail will be displayed in turn. The preview information can be a direct display of the task card, or it can be a rearranged display of the key information of the subtask card after extraction.

[0293] An event card is a card container provided by the desktop. When a user clicks an event card thumbnail and the card expands, the application running in the foreground remains on the desktop. When a user performs a preset action on a subtask card within the event card, the application that provided the subtask card is launched and takes over the foreground.

[0294] In one possible implementation, the system desktop may not display the application icons of the applications installed on the system, but instead display several event card thumbnails on the desktop (or display both the application icons and the event cards). The system desktop may use events as a dimension and may display event card thumbnails corresponding to one or more different events.

[0295] It should be understood that because users may have the same subtask requirements in different events, the same task card may exist in different event cards. For example, a user is on a business trip with a travel plan. They can create two event cards for the business trip and the travel. In both event cards, the user wants to check the weather. Therefore, the weather subtask card can exist in both the business trip event card and the travel event card.

[0296] Referring to Figure 5, Figure 5 shows the system desktop interface and the expanded event card respectively. In the system desktop of Figure 5, two event card thumbnails are displayed, corresponding to two events (Shanghai business trip event and HC conference event). No APP icon is displayed. The event card thumbnail will display the information of at least one subtask card, and can change over time. For example, the preview information of all subtask cards included in the current event card is displayed in turn. The preview information can be a direct display of the subtask card, or it can be the extraction of the key information of the subtask card and then rearranged for display. In addition to event cards, the system desktop can also add traditional widgets or other interactive entrances, such as the weather card in Figure 5.

[0297] As shown in Figure 5, after clicking on the Shanghai business trip event card, the event card expands (the system task is still a desktop application at this time), and displays multiple subtask cards included in the event card. The subtask cards in Figure 5 include flight cards, accommodation cards, weather cards and alarm cards. The four subtask cards are all subtasks directly related to the Shanghai business trip itinerary event and serve the Shanghai business trip event.

[0298] Method 2: By selecting the event card on the event card management interface

[0299] Similar to the application window management interface, the event card management interface can display thumbnails of one or more currently created event cards. However, unlike the application window management interface, event cards are added to the event card management interface after creation and can be viewed in the event card management interface, rather than only viewing event cards that are currently open or have been opened in the past time period. Optionally, in the event card management interface, multiple event cards can be stacked on top of each other. As the user slides, different event cards can be switched to the middle of the interface and displayed on the top layer.

[0300] In the embodiment of the present application, the operating system presents information to the user using events as the dimension. Therefore, the operating system also provides an event management interface (i.e., the event card management interface in the embodiment of the present application). The event card management interface displays all event cards created by the user that have not yet been destroyed. Optionally, if all subtask cards within an event card are completed, the event card can be automatically destroyed by the system, or the user can trigger the destruction of the event card by performing a preset operation on the event card.

[0301] For example, referring to Figure 6, Figure 6 shows an event card management page and an expanded event card. The event card management page in Figure 6 displays two stacked event cards. As shown in Figure 6, after clicking the Shanghai business trip event card on the event card management page, the event card expands (at this time, the system task is still a desktop application) and displays multiple subtask cards included in the event card. The subtask cards in Figure 6 include a flight card, an accommodation card, a weather card, and an alarm card. These four subtask cards are all subtasks directly related to the Shanghai business trip itinerary and serve the Shanghai business trip event.

[0302] How to enter the event card management interface will be introduced in subsequent embodiments.

[0303] Method 3: By operating the preset controls

[0304] Among them, the preset control can be a terminal assistant (such as an AI assistant. For the convenience of description, the terminal assistant is described as an AI assistant in the following embodiments) or a navigation bar.

[0305] For example, full-screen mobile phones are generally equipped with a navigation bar at the bottom. By interacting with the navigation bar, you can call out the AI ​​assistant control (such as replacing the navigation bar with the AI ​​assistant control, or displaying the AI ​​assistant control above the navigation bar). When the AI ​​assistant control is called out in the in-app interface, at least one event card can also be displayed, for example, in the form of a small window. The AI ​​assistant control can be permanently displayed on the desktop. It can also be called out after a preset operation, for example, there is a navigation bar at the bottom of the screen, and the AI ​​assistant control is called out by operating the navigation bar (such as long pressing). In this application, the AI ​​assistant control can replace the navigation bar, that is, after the AI ​​assistant control is displayed, the navigation bar may no longer be displayed, or the AI ​​assistant control can be considered to be displayed on the upper layer of the navigation bar.

[0306] In Figure 7, the user long-presses the bottom navigation bar to bring up the AI ​​Assistant widget, which displays a small window showing the most recently created or recently opened event cards. After bringing up the event cards, the user can tap on them to open the corresponding event card for the to-do event.

[0307] In one possible implementation, a fourth operation can be received, and an event card corresponding to the to-do event can be displayed in response to the fourth operation; wherein, the fourth operation is the selection of an event card thumbnail corresponding to the to-do event in the system desktop or the event card management interface, and the system desktop or the event card management interface includes at least one event card thumbnail including the to-do event; or, the fourth operation is the operation of a preset control, and the preset control is a terminal assistant or a navigation bar.

[0308] The above embodiment introduces an event card management interface, which can include at least one event card. Users can select event cards in the event card management interface to open the subtask card of the corresponding event, or edit the event card in the event card management interface (the editing process will be introduced in subsequent embodiments).

[0309] In a possible implementation, the first operation may be received to display the event card management interface. The following first introduces how to enter the event card management interface:

[0310] Method 1: Operations on preset controls.

[0311] The preset control may be a terminal assistant or a navigation bar.

[0312] In a possible implementation, the event card management interface may be called out through a first operation on the terminal assistant or the navigation bar.

[0313] For example, if the terminal assistant is an AI assistant control, users can perform preset interactive operations with the AI ​​assistant control, which will display several obscured card decks on the back of the AI ​​assistant control. After the card decks appear, swipe up to enter the event card management interface. Alternatively, swipe up directly on the AI ​​assistant control to enter the event card management interface.

[0314] For example, referring to Figure 9, the user can first click the navigation bar to call out the AI ​​assistant control. Then, long-press the AI ​​assistant control to display several stacked cards on the back of the AI ​​assistant control. Alternatively, long-press the navigation bar to display the AI ​​assistant control and display several stacked cards on the back of the AI ​​assistant control.

[0315] The stacked cards on the back of the AI ​​Assistant control refer to event cards, and the number of stacked cards corresponds to the number of event cards. Swipe up again, and several stacked cards will be displayed on the back of the AI ​​Assistant control to expand and display all currently existing event cards, that is, enter the event card management interface. In this process, you can cooperate with the animation display to move the card on the back of the AI ​​Assistant control to the middle of the screen to indicate that the card on the back of the AI ​​Assistant is a thumbnail card of the event card, and the event card in the event card management page is the expansion of the card on the back of the AI ​​Assistant.

[0316] It should be understood that when the AI ​​assistant control is resident on the desktop, you can interact with the AI ​​assistant control directly without having to operate the navigation bar to trigger the AI ​​assistant control.

[0317] In one possible implementation, by operating the terminal assistant or navigation bar, the first thumbnail group of the event card group and the first thumbnail group of the application window group can be called out. The user can choose to enter the event card management interface or the application window management interface by selecting different card groups.

[0318] Specifically, in one possible implementation, the first thumbnail of the event card group or the first thumbnail of the application window group can be called out through the first operation on the terminal assistant or the navigation bar, and the user can choose to open the event card management interface or the application window management interface through the switching operation.

[0319] For example, the event card management interface may be opened by selecting the first thumbnail of the first indication information event card group of the at least one event card in the first interface.

[0320] For example, the first thumbnail of the application window group can be switched to the first thumbnail of the first indication information event card group of the at least one event card by a switching operation on the first thumbnail of the application window group in the second interface, and the event card management interface can be opened by a selection operation on the first thumbnail of the first indication information event card group of the at least one event card in the first interface.

[0321] Taking the AI ​​Assistant as an example, in one possible implementation, after long pressing and swiping up on the AI ​​Assistant control, two card decks will be displayed: one for event cards (this card deck is not the event card management interface itself, but its thumbnail), and the other for application windows (this window group is not the application window management interface itself, but its thumbnail). Users can choose to enter the event card management interface or the application window management interface by selecting different card decks.

[0322] For example, using a continuous gesture, long press the AI ​​Assistant space and then swipe up. The interface will display two card groups. The event card group is displayed by default, and some application window groups can also be displayed. If you stay at the location of the time card group, you will enter the event card management interface. If you swipe right, the application window group will be fully displayed, and the event card group will not be displayed or only partially displayed. Then click the application window group to enter the application window management interface.

[0323] Figure 10 shows the event card management interface and the application window management interface entered under the same operation path. After long pressing the AI ​​assistant icon, swipe up to call out the card deck, and the event card deck is displayed on the screen by default. Move the touch point of the sliding gesture to the event card and release it, or release the sliding gesture and then click the event card deck to enter the event card management interface. This corresponds to the upper branch in Figure 10. After swiping up, continue to swipe right, or release the swipe up gesture and then perform the right swipe gesture. The event card group moves to the right and gradually displays the application window group. Click the application window group to enter the application window management interface. This corresponds to the lower branch in Figure 10.

[0324] In one possible implementation, in order to prompt the user to switch between the thumbnails of the application window management interface and the thumbnails of the event card management interface, the thumbnails of the event card group can also be displayed on the interface displaying the thumbnails of the application window management interface (the thumbnails of the event card management interface are not as conspicuous as the thumbnails of the application window management interface, for example, they can be arranged after the thumbnails of the application window management interface).

[0325] For example, a first interface can be displayed, and the first interface may include the first indication information of at least one event card, the first thumbnail of the event card group, and the second indication information of the application window group; and the second indication information of the application window group is arranged after the first thumbnail of the event card group of the first indication information of the at least one event card; after receiving a switching operation for the first thumbnail of the application window group in the second interface, the first interface can be switched to the second interface, and the second interface includes the first thumbnail of the application window group and the second indication information of the at least one event card; the second indication information of the at least one event card is arranged after the first thumbnail of the application window group.

[0326] Referring to Figure 12A, Figure 12A shows the event card management interface and the application window management interface respectively. The event card management interface and the application window management interface both have two layers of cards. The two layers of cards correspond to the thumbnails of the application window group and the thumbnails of the event card group respectively, and are arranged front to back along the line of sight: in the event card management interface, the event card list is located in the front, occupying a larger display area, and the application window list is located in the back; in the application window management interface, the application window list is located in the front, occupying a larger display area, and the event card list is located in the back.

[0327] When a swipe-up gesture is performed in the blank area of ​​the event card management interface and the application window management interface in Figure 12A (or the display area of ​​the AI ​​assistant control), you can switch between the event card management interface and the application window management interface.

[0328] In Figure 12A, the application window group in the event card management interface may not support interaction, that is, sliding in the thumbnail area of ​​the application window group will not change the application windows in the application window group. Correspondingly, the event card group in the application window management interface may not support interaction, that is, sliding in the thumbnail area of ​​the event card group will not change the application windows in the event card group. Of course, the application window group in the event card management interface and the event card group in the application window management interface can also be designed to support interaction. When interaction is supported, by sliding left and right, the application windows in the application window group / event cards in the event card group can be driven to slide left and right.

[0329] Although the application window management interface and the event card management interface are described as two interfaces in the above description, it can be seen from Figure 12A that these two interfaces are essentially two displays of content with different focuses of one interface. Therefore, in other descriptions, they can also be described as two form switches of one interface.

[0330] In the example of the above embodiment, the desktop is used as an example for illustration. In the in-application scenario, still taking the AI ​​assistant control as an example, the AI ​​assistant control, as a system-level global control, can call out the AI ​​assistant control through a preset interactive method, so as to enter the time card management interface through the interaction of the AI ​​assistant control. For example, full-screen mobile phones are generally configured with a navigation bar at the bottom, and the AI ​​assistant control is called out by interacting with the navigation bar (such as replacing the navigation bar with the AI ​​assistant control, or displaying the AI ​​assistant control above the navigation bar). When the AI ​​assistant control is called out in the in-application interface, at least one event card can also be displayed, for example, in the form of a small window.

[0331] Refer to Figure 11. In Figure 11, a user long-presses the bottom navigation bar within the instant messaging software interface to bring up the AI ​​Assistant control, which displays the most recently created or recently opened event cards in a small window. After calling up the event card, the user can interact with the AI ​​Assistant control and perform preset actions such as long-pressing and swiping up to enter the event card management interface and perform event card management functions.

[0332] Method 2: Swipe up from the bottom of the desktop

[0333] It should be understood that, similar to the existing application window management interface, the display of the event card management interface can be triggered by sliding up on the bottom of the desktop of the interface.

[0334] The system can provide a preset gesture. Swipe up on the bottom of the desktop. If the swiping distance is within the preset range, the event card management interface will be entered.

[0335] As shown in Figure 8, the user swipes up from the bottom of the screen. If the swiping distance is within the preset range, the desktop enters the event card management interface from the main screen interface. Animation transition can be used in the middle. For example, the event cards in the event card list gradually appear from the bottom and move to the preset area on the screen with the swiping gesture.

[0336] In some cases, when an event involves a relatively simple task, users may also need to use a single application. For example, for a reading event, users only need to use a single reading app. Therefore, users also need to access application management through the multi-application management interface.

[0337] Therefore, in the operating system, there will be both event-centered and application-centered requirements. In the existing full-screen gestures, when the user swipes up from the bottom of the screen and the swipe distance meets the preset threshold, the application window management interface is entered.

[0338] In the solution of the present invention, the bottom of the screen is swiped up, and the swiping distance is used to determine whether to enter the event card management interface or the application window management interface. For example, three thresholds x1, x2, and x3 are defined respectively. If the swiping distance is within the interval (x1, x2), the event card management interface is entered. If the swiping distance is within the interval (x2, x3), the application window management interface is entered. The application window management interface displays a list of application windows currently running in the operating system.

[0339] In one possible implementation, the event card management interface displays not only the current event card but also a list of application windows, and can be switched from the event card management interface to the application window management interface by executing a preset operation. Correspondingly, the application window management interface also displays an event card group, and can be switched from the application window management interface to the event card management interface by executing a preset operation.

[0340] For example, in one possible implementation, the user's first operation can be received, and a thumbnail of the event card management interface is displayed (or the event card management interface is directly displayed), wherein the first operation is specifically a sliding operation on a preset control, and the effective distance of the sliding operation in the first operation is within a first preset range (for example, (x1, x2)); the user's third operation can also be received, and the second interface is displayed, and the second interface includes a thumbnail of the application window management interface (or the application window management interface is directly displayed); wherein the third operation is a sliding operation on a preset control, and the effective distance of the sliding operation in the third operation is within a second preset range (for example, (x2, x3)).

[0341] The above describes how to open the event card management interface and how to switch between the event card management interface and the application window management interface. Next, we will introduce other operations related to the event card management interface.

[0342] In one possible implementation, event cards can be managed on the event card management interface. Placing a touch on an event card and swiping up deletes the event card. If the swipe up distance is insufficient, the event card automatically returns to the event card list. After deletion, the event card is removed from the system and no longer displayed on the home screen.

[0343] In one possible implementation, you can select an event card and enter the event card. Optionally, the displayed content after selecting the event card can be the same as the result of clicking the event card on the desktop. The difference is that in the event card management interface, a thumbnail of the event card is displayed, and the content of the event card can be previewed, while the desktop is a preview of key information.

[0344] In one possible implementation, you can long press an event card to add the event card to the desktop, that is, when a selection of a thumbnail of a target event card in at least one event card in the event card management interface is received (for example, a long press operation), the thumbnail of the target event card is added to the system desktop for display.

[0345] In a possible implementation, the display state of the thumbnail of the event card in the event card management interface is related to the completion degree of the subtask card in the event card. For example, the display state is color or transparency.

[0346] Event cards can also use different colors and transparency levels to indicate the execution status of the corresponding event. When the task corresponding to the task card in the time card is completed, the corresponding transparency level will be changed. For example, you can define the event progress as 0, 25%, 50%, 75%, and 100%, corresponding to opacity to full transparency. When the subtask corresponding to a task card is completed, if the corresponding ratio is reached, the transparency level of the card will be changed.

[0347] In one possible implementation, event cards can also display their type through superscripts. For example, events corresponding to event cards can be categorized into long-term events and short-term events based on the number of subtasks they contain and the corresponding time span, with different superscripts used to indicate different types.

[0348] 1202. Upon receiving a fifth operation, the event card corresponding to the to-do event is switched to a first interface, where the first interface is an application interface, a system desktop, or an application window management interface.

[0349] Among them, the fifth operation can be the selection of the application corresponding to the subtask card, and then the event card corresponding to the to-do event can be switched to the application interface.

[0350] Among them, the fifth operation can be an operation of returning to the system desktop, such as sliding up from the bottom and selecting the desktop key, and then the event card corresponding to the to-do event can be switched to the system desktop.

[0351] Among them, the fifth operation can be an operation to trigger entering the application window management interface, such as swiping up from the bottom, and operating on preset controls (such as navigation bar, terminal assistant control), and then the event card corresponding to the to-do event can be switched to the application window management interface.

[0352] Next, we will introduce the process of creating event cards with the help of the attached figure:

[0353] In one possible implementation, a creation request for the to-do event input by the user can be received. Based on the creation request, the requirement information of multiple subtasks for implementing the to-do event and the application for executing the function of each subtask can be determined. The requirement information of the multiple subtasks is used as a query input, and through interaction with the corresponding application, the requirement feedback result of each subtask is obtained. The requirement feedback result is used to construct the multiple subtask cards.

[0354] For example, the terminal device may receive a request to create a to-do event as an initial instruction, create an event card based on the received initial instruction, and display at least one subtask of the event card determined according to the initial instruction in the event card.

[0355] For example, a user can input a request to create a to-do event through voice interaction with the AI ​​assistant. The AI ​​assistant has a built-in large language model, or parses the request to create a to-do event by calling a large language model in the cloud.

[0356] Specifically, the terminal device can forward the received to-do event creation request to the AI ​​assistant, which will parse the to-do event creation request. If the parsing result meets the requirements for event card creation, an event card will be created and at least one subtask of the event will be presented in the event card.

[0357] For example, if keywords such as itinerary, task, to-do, travel, and tourism are recognized, it can be considered that the user needs to manage events, which triggers the creation of an event card. When creating an event, the event name, type, and other information are determined based on the analysis results.

[0358] An event's subtasks can be derived from the results of parsing the to-do event's creation request, or recommended by a large language model based on the event type. For example, for travel arrangements, subtasks such as flight / train ticket booking and hotel reservation can be included. After obtaining at least one subtask for an event, it is displayed on the event card.

[0359] It is understandable that within an event card, subtasks of the same type may be presented for user selection, for example, subtasks of air ticket booking and train ticket booking may be presented simultaneously.

[0360] As shown in Figure 12B, the user's to-do request is "Please arrange a business trip to Shanghai from next Sunday to Wednesday." Based on the parsing results, an event card for the business trip category is created, named "Shanghai Business Trip." Based on this business trip category, the user is recommended subtasks for booking a flight and booking a hotel, which are displayed within the event card.

[0361] After at least one subtask is displayed in the event card, the terminal device continues to receive user input and determines the target subtask according to the user input, that is, which subtask card or cards need to be added to the event card.

[0362] The user input may be a preset operation on the target subtask, such as clicking on the text / control corresponding to the target subtask. For example, in FIG12B , clicking on the control corresponding to “Book a flight” sets booking a flight as the target subtask.

[0363] After determining the target subtask, the associated applications for the target subtask can be determined according to pre-set rules. Specifically, target subtasks have different types, and corresponding applications also have at least one tag. By establishing a pre-set relationship between the target subtask type and the application tag, the associated applications for the target subtask can be determined from the local applications installed by the user.

[0364] For example, if the target subtask is "book a flight," the corresponding task type is the flight booking category within the transportation category. Application tags for the transportation category include travel, flight booking, and flight. Corresponding associated applications could be ticket booking software or flight search software.

[0365] In order to determine the associated application of the target subtask, it is also necessary to determine the information input into the associated application (that is, the demand information in the embodiment of the present application) so as to obtain the demand feedback result corresponding to the demand information from the associated application and present it to the user.

[0366] On the one hand, the demand information can be obtained through the semantic analysis results of the creation request of the to-do event, and can also be supplemented by the user in subsequent interactions with the user.

[0367] For example, when parsing a request to create a pending event, in addition to parsing whether it meets the requirements for creating an event card, some associated information related to the event corresponding to the event card will also be generated. This information may include: time information, location information.

[0368] For example, in the input of FIG12B , in addition to parsing the user's intention of arranging a business trip to Shanghai and the event type being the itinerary arrangement category, the time information “Sunday to Wednesday” and the location information “Shanghai” can also be obtained.

[0369] By combining the associated information with the target subtask, we can obtain demand information, which is then sent as query input to the associated application as input. In the above example, combining the time information "Sunday to Wednesday", the location information "Shanghai", and the target subtask of booking air tickets, the query input that can be determined is "Book a flight from my current city to Shanghai on Sunday."

[0370] In one possible implementation, a query process interface can be used to guide users in supplementing their required information. Optionally, the query process interface displays at least one query message, each corresponding to an associated application. Figure 12C shows a query process interface displaying two query messages, corresponding to APP1 and APP2, respectively, querying flight ticket information and flight on-time information.

[0371] In this solution, the query interface includes the identifiers of associated applications. By interacting with the associated application identifiers, you can switch to other associated applications of the same type. For example, in Figure 12D, clicking App1 will display a list of applications with the same label as App1—Flight Booking. You can switch to a different application by selecting an application from the list. If the selected application is not installed locally, it will be linked to the app store to download and install it before switching.

[0372] After receiving the query input, the associated application provides query results to the terminal based on the query input, and the terminal can filter the query results according to preset rules.

[0373] Specifically, depending on the target subtask, the terminal can filter information based on different dimensions. Common dimensions include departure date, departure time, price, punctuality, and transit time. Specific dimension information is built into the system. A filter information item can be displayed on the time card interface. This filter information provides the filter dimensions, which are presented as controls. By interacting with the dimension information control, you can change the filter dimension or enter detailed information for that dimension.

[0374] Figure 12D shows two situations of interacting with the dimension information control. They correspond to changing dimensions and entering dimension details respectively. In the left picture, click on the "price" dimension information control, and a small window pops up to list other dimension information currently available. Select one from them to replace the price as the filtering dimension. In the right picture, click on the flight date, a calendar window appears, and select the specific flight time. If the user does not interact with the dimension information, the system will filter according to the default unread target subtask. After filtering and obtaining the recommended information, the recommended information will be displayed in the event card. Figure 12E shows the display of recommended information in the event card. The user can select the target recommended information from the recommended information by touch or voice input. The recommended information can be determined as the target recommended information by detecting the recommended information corresponding to the touch input or by voice analysis.

[0375] After determining the target recommendation information, a task card corresponding to the target subtask can be created based on the target recommendation information. In Figure 12E, after the user selects one of the flight information, a flight task card can be created based on the flight information.

[0376] After creating a task card, you can continue to create new task cards based on the target subtasks in the event card.

[0377] In FIG12F , in order to save display space, before the task card corresponding to the target subtask is created, the created task card is displayed as a thumbnail in the task card. After the task card corresponding to the target subtask is created, the task card is fully displayed.

[0378] Multiple task cards can be batch processed when performing the same operation. For example, when paying for an order, users can access the payment interface by using the payment control within the card or by interacting with a single task card. Users can select task cards to pay collectively, or select only a subset of task cards to pay for those. If only one task card is selected, payment will be processed only for the order associated with that task card.

[0379] After creating the task card corresponding to the target subtask, the system can recommend task cards to the user based on the event card type. The user can then select and add the task card to the event card. In Figure 12G, after selecting a recommended card and clicking Add, the task card is added to the event card. If the user does not select a task card or performs a back gesture, the recommended card is not added.

[0380] In a possible implementation, when creating each subtask card, the user can interrupt the creation of the subtask card or switch to a different creation through a specific operation.

[0381] For example, the multiple subtasks include a first subtask and a second subtask. When switching to create subtasks, in one possible implementation, the editing page of the first subtask can be displayed; the first requirement information of the first subtask entered by the user on the editing page is received; and the sixth operation is received, the editing page of the first subtask is switched to the editing page of the second subtask, and the requirement information of the second subtask entered by the user on the editing page is received.

[0382] In one possible implementation, the creation process of the first subtask can be interrupted while the creation process of the second subtask is in progress, and the creation process of the first subtask can be continued. The creation process of the first subtask can then be returned to and continued, while retaining the creation content previously entered in the first subtask (it should be understood that the creation content is also the user's requirement information for the subtask). Specifically, the seventh operation can be received, switching the editing page of the second subtask to the editing page of the first subtask containing the first requirement information, and receiving the second requirement information of the second subtask that the user continues to enter on the editing page.

[0383] For example, when there are multiple subtasks, you can switch between different subtask cards by swiping up or down while creating a card. When switching to another subtask card, you can interrupt the creation of the current subtask card and save the creation progress. If the other subtask card has not been created, swipe up or down to jump to the subtask list interface. When switching back to the interrupted subtask card creation, the subtask card creation will continue.

[0384] When there are multiple subtask cards (including subtask cards that are interrupted / being created), you can use a preset gesture to call out the subtask card list during the creation process, and then enter the subtask card through the subtask card list to view, edit or continue creating.

[0385] Figure 12H shows the swipe up and long-press gestures during flight booking. Assuming the hotel reservation subtask has been completed before booking the flight, swiping up will switch to the hotel reservation card, which supports further operations such as payment and modification. Long-pressing will display a list of all subtask cards. If there are only two subtasks, the flight reservation card and hotel reservation card will be displayed.

[0386] In this embodiment of the present application, the system automatically determines associated applications by parsing the event card creation request and calls these associated applications to create subtask cards. This eliminates the need to access each associated application to implement multiple subtasks for a single event; all operations can be completed on the system desktop, eliminating the need for application switching or interface navigating, thus simplifying the event subtask processing process.

[0387] 13 , which is a schematic diagram of the structure of an interface display device provided in an embodiment of the present application, wherein the device 1300 includes:

[0388] The processing module 1301 is used to receive a first operation, trigger the display module 1302 to display an event card management interface, and the event card management interface includes a thumbnail of at least one event card; wherein the expanded event card includes multiple sub-task cards, and each sub-task card is a trigger entry for a sub-function of the application; and receive a second operation, triggering the display module 1302 to switch the event card management interface to the application window management interface.

[0389] In a possible implementation, the first operation is:

[0390] For the swipe-up operation at the bottom of the desktop, or for the operation of a preset control, the preset control is a terminal assistant or a navigation bar; or

[0391] a selection operation on the first indication information of the at least one event card in the first interface; or

[0392] A switching operation on the first thumbnail of the application window group in the second interface, and a selection operation on the first indication information of the at least one event card displayed in response to the switching operation.

[0393] In one possible implementation, the first interface also includes second indication information of the application window group; the second indication information of the application window group is arranged after the first indication information of the at least one event card; the second interface also includes second indication information of the at least one event card; the second indication information of the at least one event card is arranged after the first thumbnail of the application window group.

[0394] In one possible implementation, the first operation is specifically a sliding operation on a preset control, and an effective distance of the sliding operation in the first operation is within a first preset range; the processing module 1301 is further configured to:

[0395] A third operation is received, triggering the display module 1302 to display the second interface; wherein the third operation is a sliding operation on a preset control, and the effective distance of the sliding operation in the third operation is within a second preset range.

[0396] In a possible implementation, the processing module 1301 is further configured to:

[0397] Upon receiving a selection of a thumbnail of a target event card in the at least one event card in the event card management interface, the display module 1302 is triggered to add the thumbnail of the target event card to the system desktop for display.

[0398] In a possible implementation, the display status of the thumbnail of the event card in the event card management interface is related to the completion degree of the subtask card in the event card.

[0399] In a possible implementation, the display state is color or transparency.

[0400] In a possible implementation, the processing module 1301 is further configured to:

[0401] The fourth operation is received, triggering the display module 1302 to display the event card corresponding to the to-do event; the fourth operation is to select the thumbnail of the event card corresponding to the to-do event in the event card management interface; the event card corresponding to the to-do event includes multiple sub-task cards, and each sub-task card is a trigger entry for a sub-function of the application.

[0402] In a possible implementation, the processing module 1301 is further configured to:

[0403] Receiving the fifth operation triggers the display module 1302 to switch the event card corresponding to the to-do event to the first interface, where the first interface is an application interface, a system desktop, or an application window management interface.

[0404] In a possible implementation, the multiple subtask cards include a first subtask card and a second subtask card, the first subtask card and the second subtask card correspond to different applications, or the first subtask card and the second subtask card correspond to different functions of the same application.

[0405] In a possible implementation, the processing module 1301 is further configured to:

[0406] Receive a request to create a to-do event from the user;

[0407] Determining, based on the creation request, requirement information for implementing a plurality of subtasks of the to-do event and an application for executing a function of each subtask;

[0408] The requirement information of the multiple subtasks is used as a query, and a requirement feedback result of each subtask is obtained through interaction with the corresponding application. The requirement feedback result is used to construct the multiple subtask cards.

[0409] In a possible implementation, the requirement information of the multiple subtasks is information carried in the semantics of the creation request, or information supplemented by the user for the multiple subtasks.

[0410] In a possible implementation, the multiple subtasks include a first subtask and a second subtask;

[0411] The processing module 1301 is specifically configured to:

[0412] Triggering the display module 1302 to display the edit page of the first subtask;

[0413] receiving first requirement information of the first subtask input by a user on the editing page;

[0414] Receiving a sixth operation triggers the display module 1302 to switch the editing page of the first subtask to the editing page of the second subtask;

[0415] Requirement information of the second subtask input by the user on the editing page is received.

[0416] In a possible implementation, the processing module 1301 is further configured to:

[0417] Receiving the seventh operation triggers the display module 1302 to switch the editing page of the second subtask to the editing page of the first subtask containing the first requirement information;

[0418] Second requirement information of the second subtask continuously input by the user on the editing page is received.

[0419] In addition, the present application also provides an interface display device, comprising:

[0420] a processing module, configured to display an event card corresponding to a to-do event, wherein the event card corresponding to the to-do event includes a plurality of subtask cards and indication information of the to-do event; each subtask card is a triggering entry for a sub-function of an application, and the event card corresponding to the to-do event indicates that the plurality of subtask cards are associated with the to-do event;

[0421] Upon receiving the fifth operation, the event card corresponding to the to-do event is switched to the first interface, where the first interface is an application interface, a system desktop, or an application window management interface.

[0422] In a possible implementation, before displaying the event card corresponding to the to-do event, the processing module is further configured to:

[0423] A fourth operation is received; wherein,

[0424] The fourth operation is selecting an event card corresponding to the to-do event on the system desktop or the event card management interface, wherein the system desktop or the event card management interface includes at least one event card including the to-do event; or

[0425] The fourth operation is an operation on a preset control, and the preset control is a terminal assistant or a navigation bar.

[0426] In a possible implementation, the multiple subtask cards include a first subtask card and a second subtask card, the first subtask card and the second subtask card correspond to different applications, or the first subtask card and the second subtask card correspond to different functions of the same application.

[0427] In a possible implementation, the processing module is further configured to:

[0428] Displaying a first interface, the first interface including a first thumbnail of an event card group of first indication information of at least one event card;

[0429] Receiving a selection operation of a first thumbnail of the event card group of the first indication information for the at least one event card, displaying an event card management interface; the event card management interface includes at least one event card including the to-do event; or,

[0430] A switching operation for the first thumbnail is received, and a second interface is displayed, where the second interface includes the first thumbnail of the application window group.

[0431] In a possible implementation, before displaying the first interface, the processing module is further configured to:

[0432] A first operation is received, wherein:

[0433] The first operation is a swipe-up operation on the bottom of the desktop of the interface, or an operation on a preset control, and the preset control is a terminal assistant or a navigation bar.

[0434] In one possible implementation, the first interface also includes second indication information of the application window group; the second indication information of the application window group is arranged after the first thumbnail of the first indication information event card group of the at least one event card; the second interface also includes second indication information of the at least one event card; the second indication information of the at least one event card is arranged after the first thumbnail of the application window group.

[0435] In a possible implementation, the first operation is specifically a sliding operation on a preset control, and the effective distance of the sliding operation is within a first preset range; the processing module is further configured to:

[0436] Upon receiving a third operation, a second interface is displayed, wherein the second interface includes a first thumbnail of the application window group; wherein the third operation is a sliding operation on a preset control, and an effective distance of the sliding operation is within a second preset range.

[0437] In a possible implementation, the processing module is further configured to:

[0438] A selection of a thumbnail of a target event card in the at least one event card in the event card management interface is received, and the thumbnail of the target event card is added to the system desktop for display.

[0439] In a possible implementation, the display status of the thumbnail of the event card in the event card management interface is related to the completion degree of the subtask card in the event card.

[0440] In a possible implementation, the display state is color or transparency.

[0441] In a possible implementation, the processing module is further configured to:

[0442] Receiving a request for creating the to-do event input by a user;

[0443] Determining, based on the creation request, requirement information for implementing a plurality of subtasks of the to-do event and an application for executing a function of each subtask;

[0444] The requirement information of the multiple subtasks is used as a query, and a requirement feedback result of each subtask is obtained through interaction with the corresponding application. The requirement feedback result is used to construct the multiple subtask cards.

[0445] In a possible implementation, the requirement information of the multiple subtasks is information carried in the semantics of the creation request, or information supplemented by the user for the multiple subtasks.

[0446] In a possible implementation, the multiple subtasks include a first subtask and a second subtask;

[0447] The processing module is specifically used to:

[0448] Display the edit page of the first subtask;

[0449] receiving first requirement information of the first subtask input by a user on the editing page;

[0450] Upon receiving a sixth operation, switching the edit page of the first subtask to the edit page of the second subtask;

[0451] Requirement information of the second subtask input by the user on the editing page is received.

[0452] In a possible implementation, the processing module is further configured to:

[0453] Upon receiving the seventh operation, switching the editing page of the second subtask to the editing page of the first subtask including the first requirement information;

[0454] Second requirement information of the second subtask continuously input by the user on the editing page is received.

[0455] Next, an execution device provided in an embodiment of the present application is introduced. Please refer to Figure 14. Figure 14 is a structural schematic diagram of an execution device provided in an embodiment of the present application. The execution device 1400 can be specifically manifested as a mobile phone, a tablet, a laptop computer, a smart wearable device, etc., which is not limited here. Specifically, the execution device 1400 includes: a receiver 1401, a transmitter 1402, a processor 1403 and a memory 1404 (wherein the number of processors 1403 in the execution device 1400 can be one or more, and Figure 14 takes one processor as an example), wherein the processor 1403 may include an application processor 14031 and a communication processor 14032. In some embodiments of the present application, the receiver 1401, the transmitter 1402, the processor 1403 and the memory 1404 may be connected via a bus or other means.

[0456] Memory 1404 may include read-only memory and random access memory, and provides instructions and data to processor 1403. A portion of memory 1404 may also include non-volatile random access memory (NVRAM). Memory 1404 stores processor and operation instructions, executable modules, or data structures, or subsets or extended sets thereof. The operation instructions may include various operation instructions for implementing various operations.

[0457] Processor 1403 controls the operation of the execution device. In specific applications, the various components of the execution device are coupled together via a bus system. In addition to a data bus, the bus system may also include a power bus, a control bus, and a status signal bus. However, for clarity, all bus systems are referred to as a bus system in the figure.

[0458] The methods disclosed in the above embodiments of the present application can be applied to or implemented by processor 1403. Processor 1403 can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by hardware integrated logic circuits or software instructions in processor 1403. The above processor 1403 can be a general-purpose processor, a digital signal processor (DSP), a microprocessor, or a microcontroller, and can further include an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The processor 1403 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in conjunction with the embodiments of the present application can be directly implemented as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in memory 1404, and processor 1403 reads the information in memory 1404 and, in conjunction with its hardware, completes the steps of the above method.

[0459] Receiver 1401 can be used to receive input digital or character information and generate signal input related to executing relevant settings and function control of the device. Transmitter 1402 can be used to output digital or character information; transmitter 1402 can also be used to send instructions to the disk group to modify the data in the disk group.

[0460] In an embodiment of the present application, in one case, the processor 1403 is used to execute the steps of the interface display method in the embodiments corresponding to Figures 4 and 12I.

[0461] An embodiment of the present application also provides a computer program product including computer-readable instructions, which, when executed on a computer, enables the computer to execute the steps executed by the aforementioned execution device, or enables the computer to execute the steps executed by the aforementioned training device.

[0462] A computer-readable storage medium is also provided in an embodiment of the present application, which stores a program for signal processing. When the computer-readable storage medium is run on a computer, it enables the computer to execute the steps executed by the aforementioned execution device, or enables the computer to execute the steps executed by the aforementioned training device.

[0463] It should also be noted that the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed across multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment. In addition, in the drawings of the device embodiments provided in this application, the connection relationship between the modules indicates that there is a communication connection between them, which can be specifically implemented as one or more communication buses or signal lines.

[0464] Through the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course can also be implemented by special hardware including application-specific integrated circuits, special CPUs, special memories, special components, etc. In general, all functions performed by computer programs can be easily implemented with corresponding hardware, and the specific hardware structures used to implement the same function can also be diverse, such as analog circuits, digital circuits or special circuits, etc. However, for the present application, software program implementation is a better implementation method in most cases. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer's floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk or optical disk, etc., and includes a number of instructions to enable a computer device (which can be a personal computer, training equipment, or network equipment, etc.) to execute the methods described in each embodiment of the present application.

[0465] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0466] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in 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 devices. 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 a website, a computer, a training device or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website, a computer, a training device or a data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a training device, a data center, etc. that includes one or more available media integrations. The available medium can be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

Claims

1. An interface display method, characterized in that: The method comprises: Upon receiving the first operation, an event card management interface is displayed, wherein the event card management interface includes a thumbnail of at least one event card; wherein the event card includes a plurality of subtask cards, each of which is a trigger entry for a sub-function of an application; Upon receiving the second operation, the event card management interface is switched to an application window management interface.

2. The method according to claim 1, characterized in that The first operation is: For a swipe up operation at the bottom of the desktop, or for an operation on a preset control, the preset control is a terminal assistant or a navigation bar; or, A selection operation for the first indication information of the event card management interface in the first interface; or, A switching operation on the first indication information of the application window group in the second interface, and a selection operation on the first indication information of the event card management interface displayed in response to the switching operation.

3. The method according to claim 2, characterized in that The first interface also includes second indication information of the application window group; the second indication information of the application window group is arranged after the first indication information of the at least one event card; the second interface also includes second indication information of the at least one event card; the second indication information of the at least one event card is arranged after the first thumbnail of the application window group.

4. The method according to claim 2 or 3, characterized in that: The first operation is specifically a sliding operation on a preset control, and the effective distance of the sliding operation in the first operation is within a first preset range; the method further includes: A third operation is received and the second interface is displayed; wherein the third operation is a sliding operation on a preset control, and an effective distance of the sliding operation in the third operation is within a second preset range.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: A selection of a thumbnail of a target event card in at least one event card in the event card management interface is received, and the thumbnail of the target event card is added to the system desktop for display.

6. The method according to any one of claims 1 to 5, characterized in that: The display status of the thumbnail of the event card in the event card management interface is related to the completion degree of the subtask card in the event card.

7. The method according to claim 6, characterized in that The display state is color or transparency.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: The fourth operation is received, and the event card corresponding to the to-do event is displayed; the fourth operation is the selection of the thumbnail of the event card corresponding to the to-do event in the event card management interface; the event card corresponding to the to-do event includes multiple sub-task cards, and each sub-task card is a trigger entry for a sub-function of an application.

9. The method according to claim 8, characterized in that The method further comprises: Upon receiving the fifth operation, the event card corresponding to the to-do event is switched to a first interface, where the first interface is an application interface, a system desktop, or an application window management interface.

10. The method according to any one of claims 1 to 9, characterized in that: The plurality of subtask cards include a first subtask card and a second subtask card, the first subtask card and the second subtask card correspond to different applications, or the first subtask card and the second subtask card correspond to different functions of the same application.

11. The method according to any one of claims 1 to 10, characterized in that: The method further comprises: Receive a request for creating a to-do event input by the user; Determining, according to the creation request, requirement information for implementing a plurality of subtasks of the to-do event and an application for executing a function of each subtask; The requirement information of the multiple subtasks is used as a query, and a requirement feedback result of each subtask is obtained through interaction with a corresponding application. The requirement feedback result is used to construct the multiple subtask cards.

12. The method according to claim 11, characterized in that The requirement information of the multiple subtasks is information carried in the semantics of the creation request or information supplemented by the user for the multiple subtasks.

13. The method according to claim 11 or 12, characterized in that: The plurality of subtasks include a first subtask and a second subtask; The determining of the requirement information for implementing the plurality of subtasks of the to-do event includes: Display the edit page of the first subtask; receiving first requirement information of the first subtask input by a user on the editing page; Upon receiving a sixth operation, switching the edit page of the first subtask to the edit page of the second subtask; Requirement information of the second subtask input by the user on the editing page is received.

14. The method according to claim 13, characterized in that The method further comprises: Upon receiving the seventh operation, switching the editing page of the second subtask to the editing page of the first subtask including the first requirement information; The second requirement information of the second subtask which is continuously input by the user on the editing page is received.

15. An interface display device, characterized in that: The device comprises: A processing module is used to receive a first operation, trigger a display module to display an event card management interface, and the event card management interface includes a thumbnail of at least one event card; wherein the expanded event card includes multiple subtask cards, each of which is a trigger entry for a sub-function of an application; and receive a second operation, triggering the display module to switch the event card management interface to an application window management interface.

16. The device according to claim 15, characterized in that The first operation is: For a swipe up operation at the bottom of the desktop, or for an operation on a preset control, the preset control is a terminal assistant or a navigation bar; or, A selection operation for the first indication information of the at least one event card in the first interface; or, A switching operation on a first thumbnail of the application window group in the second interface, and a selection operation on first indication information of the at least one event card displayed in response to the switching operation.

17. The device according to claim 15 or 16, characterized in that The first interface also includes second indication information of the application window group; the second indication information of the application window group is arranged after the first indication information of the at least one event card; the second interface also includes second indication information of the at least one event card; the second indication information of the at least one event card is arranged after the first thumbnail of the application window group.

18. The device according to any one of claims 15 to 17, characterized in that The first operation is specifically a sliding operation on a preset control, and the effective distance of the sliding operation in the first operation is within a first preset range; the processing module is further used to: A third operation is received, triggering the display module to display the second interface; wherein the third operation is a sliding operation on a preset control, and an effective distance of the sliding operation in the third operation is within a second preset range.

19. The device according to claim 18, characterized in that The processing module is further used for: Receiving a selection of a thumbnail of a target event card in at least one event card in the event card management interface, triggering the display module to add the thumbnail of the target event card to the system desktop for display.

20. The device according to claim 18 or 19, characterized in that The display status of the thumbnail of the event card in the event card management interface is related to the completion degree of the subtask card in the event card.

21. The device according to claim 19 or 20, characterized in that The display state is color or transparency.

22. The device according to any one of claims 16 to 21, characterized in that The processing module is further used for: The fourth operation is received, triggering the display module to display the event card corresponding to the to-do event; the fourth operation is the selection of the thumbnail of the event card corresponding to the to-do event in the event card management interface; the event card corresponding to the to-do event includes multiple sub-task cards, and each sub-task card is a trigger entry for a sub-function of the application.

23. The device according to any one of claims 16 to 22, characterized in that The processing module is further used for: The fifth operation is received, triggering the display module to switch the event card corresponding to the to-do event to the first interface, where the first interface is an application interface, a system desktop, or an application window management interface.

24. The device according to claim 23, characterized in that The plurality of subtask cards include a first subtask card and a second subtask card, the first subtask card and the second subtask card correspond to different applications, or the first subtask card and the second subtask card correspond to different functions of the same application.

25. The device according to any one of claims 15 to 24, characterized in that The processing module is further used for: Receive a request for creating a to-do event input by a user; determine, based on the creation request, requirement information for implementing multiple subtasks of the to-do event and an application for executing a function of each subtask; The requirement information of the multiple subtasks is used as a query, and a requirement feedback result of each subtask is obtained through interaction with a corresponding application. The requirement feedback result is used to construct the multiple subtask cards.

26. The device according to claim 25, characterized in that The requirement information of the multiple subtasks is information carried in the semantics of the creation request or information supplemented by the user for the multiple subtasks.

27. The device according to claim 25 or 26, characterized in that The plurality of subtasks include a first subtask and a second subtask; The processing module is specifically used for: Trigger the display module to display the editing page of the first subtask; receive the first requirement information of the first subtask entered by the user on the editing page; receive the sixth operation, triggering the display module to switch the editing page of the first subtask to the editing page of the second subtask; receive the requirement information of the second subtask entered by the user on the editing page.

28. The device according to claim 27, characterized in that The processing module is further used for: The seventh operation is received, triggering the display module to switch the editing page of the second subtask to the editing page of the first subtask containing the first requirement information; and the second requirement information of the second subtask that the user continues to input on the editing page is received.

29. An interface display device, characterized in that: The device includes a memory and a processor; the memory stores codes, and the processor is configured to obtain the codes and execute the method according to any one of claims 1 to 14.

30. A computer-readable storage medium, characterized in that: The method comprises computer-readable instructions, which, when executed on a computer device, cause the computer device to execute the method according to any one of claims 1 to 14.

31. A computer program product, characterized in that The method comprises computer-readable instructions, and when the computer-readable instructions are executed on a computer device, the computer device is caused to execute the method according to any one of claims 1 to 14.

32. A user interface, characterized in that: include: An event card management interface, wherein the event card management interface includes a thumbnail of at least one event card; The event card includes a plurality of subtask cards, each of which is a trigger entry for a sub-function of the application.

Images