Interface display method and related equipment

Abstract

An interface display method relates to the field of terminal software, and comprises the following steps: receiving a first operation, and displaying an event card management interface which comprises a thumbnail of at least one event card; wherein the unfolded event card comprises a plurality of sub-task cards, and each sub-task card is a trigger entrance of a sub-function of an application; and receiving a second operation, and switching the event card management interface into an application window management interface. According to the application, a plurality of sub-task cards are aggregated in one event card, each sub-task card is used as a trigger entry of one sub-function of the application, and when the corresponding sub-task card is selected, the terminal can jump to the corresponding application, so that a user can operate by taking the sub-task under the event as granularity, and when transaction management is carried out, the user experience is improved. According to the embodiment of the invention, different applications do not need to be clicked, and the corresponding application can be triggered by directly selecting the subtasks under the event card, so that the operation cost of a user is reduced.

Description

Technical Field

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

[0002] For the terminal operating system, the overall interaction mode of the system is based on the traditional application-centric interaction mode. In the application-centric architecture mode, when a user wants to complete an intention task, he may need to switch between multiple different applications. For example, when traveling, you need to use the ticket purchase application to buy a plane or train ticket; then use the hotel reservation application to book a hotel; and use the alarm clock to add an alarm to remind you to travel.

[0003] 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. Summary of the invention

[0004] 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 which 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.

[0005] 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 subtask 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.

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

[0007] In a 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.

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

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

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

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

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

[0013] In a possible implementation, the method further includes: receiving a selection of a thumbnail of a target event card in 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.

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

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

[0016] In a possible implementation, the method also includes: receiving a fourth operation, displaying an event card corresponding to the to-do event; the fourth operation is selecting a 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, each of which is a trigger entry for a sub-function of an application.

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

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

[0019] In a possible implementation, the method further includes: receiving a request for creating a to-do event input by a 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;

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

[0021] In the embodiment of the present application, the associated application can be automatically determined at the system level by parsing the creation request of the event card, and the associated application can be called to create a subtask card. There is no need to enter each associated application to implement multiple subtasks under an event. All operations can be completed on the system desktop without the need for application switching, interface jump, etc., which simplifies the subtask processing flow of the event.

[0022] 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 a user for the multiple subtasks.

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

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

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

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

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

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

[0029] In a possible implementation, the method further includes:

[0030] 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;

[0031] The second requirement information of the second subtask which is continuously input by the user on the editing page is received.

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

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

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

[0035] 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,

[0036] a selection operation for the first indication information of the at least one event card in the first interface; or,

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

[0038] In a 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.

[0039] In a 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 used to:

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

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

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

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

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

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

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

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

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

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

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

[0051] Receive a request for creating a to-do event input by the user;

[0052] 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;

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

[0054] 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 a user for the multiple subtasks.

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

[0056] The processing module is specifically used for:

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

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

[0059] 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;

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

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

[0062] receiving a seventh operation, triggering the display module to switch the editing page of the second subtask to the editing page of the first subtask including the first requirement information;

[0063] The second requirement information of the second subtask which is continuously input by the user on the editing page is received.

[0064] In the third aspect, the present application provides an interface display method, the method comprising: displaying an event card corresponding to a to-do event, the event card corresponding to the to-do event comprising 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, the first interface being an application interface, a system desktop, or an application window management interface.

[0065] 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 subtask 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.

[0066] 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 a selection of an event card corresponding to the to-do event in a system desktop or an 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 an operation on a preset control, and the preset control is a terminal assistant or a navigation bar.

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

[0068] In a 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 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.

[0069] In a possible implementation, before displaying the first interface, the method further includes: receiving a first operation, 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, and the preset control is a terminal assistant or a navigation bar.

[0070] In a 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.

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

[0072] In a possible implementation, the method further includes: receiving a selection of a thumbnail of a target event card in 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.

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

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

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

[0076] Based on the creation request, determine the requirement information of multiple subtasks for implementing the to-do event and the application for executing 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.

[0077] In the embodiment of the present application, the associated application can be automatically determined at the system level by parsing the creation request of the event card, and the associated application can be called to create a subtask card. There is no need to enter each associated application to implement multiple subtasks under an event. All operations can be completed on the system desktop without the need for application switching, interface jump, etc., which simplifies the subtask processing flow of the event.

[0078] 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 a user for the multiple subtasks.

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

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

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

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

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

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

[0085] In a possible implementation, the method further includes:

[0086] 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;

[0087] The second requirement information of the second subtask which is continuously input by the user on the editing page is received.

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

[0089] 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 of the subtask 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 plurality of subtask cards are associated with the to-do event;

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

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

[0092] A fourth operation is received; wherein,

[0093] The fourth operation is selecting an event card corresponding to the to-do event in the system desktop or 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

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

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

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

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

[0098] 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,

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

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

[0101] A first operation is received, wherein:

[0102] The first operation is a swiping 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.

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

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

[0105] When a third operation is received, 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.

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

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

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

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

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

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

[0112] 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;

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

[0114] 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 a user for the multiple subtasks.

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

[0116] The processing module is specifically used for:

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

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

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

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

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

[0122] 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;

[0123] The second requirement information of the second subtask which is continuously input by the user on the editing page is received.

[0124] 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 execute the first aspect and any optional method thereof.

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

[0126] In the seventh aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when executed 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.

[0127] In an eighth aspect, the present application provides a chip system, which includes a processor for supporting an interface display device to implement some or all of the functions involved in the above aspects, such as sending or processing data involved in the above methods; or, information. In one possible design, the chip system also includes a memory, which is used to store program instructions and data necessary for executing the device or training the device. The chip system can be composed of a chip, or it can include a chip and other discrete devices. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0130] Figure 3 This is an illustration of an application scenario;

[0131] Figure 4 An example of an interface display method provided in an embodiment of the present application is shown;

[0132] Figure 5 This is a schematic diagram of an interface in an embodiment of the present application;

[0133] Figure 6 This is a schematic diagram of an interface in an embodiment of the present application;

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

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

[0136] Fig. 9 This is a schematic diagram of an interface in an embodiment of the present application;

[0137] Fig.10 This is a schematic diagram of an interface in an embodiment of the present application;

[0138] Fig.11 This is a schematic diagram of an interface in an embodiment of the present application;

[0139] Fig. 12A This is a schematic diagram of an interface in an embodiment of the present application;

[0140] Fig. 12B This is a schematic diagram of an interface in an embodiment of the present application;

[0141] Fig. 12C This is a schematic diagram of an interface in an embodiment of the present application;

[0142] Fig.12D This is a schematic diagram of an interface in an embodiment of the present application;

[0143] Fig.12E This is a schematic diagram of an interface in an embodiment of the present application;

[0144] Fig.12F This is a schematic diagram of an interface in an embodiment of the present application;

[0145] Figure 12G This is a schematic diagram of an interface in an embodiment of the present application;

[0146] Fig.12H This is a schematic diagram of an interface in an embodiment of the present application;

[0147] Fig.12I An example of an interface display method provided in an embodiment of the present application is shown;

[0148] Fig.13 An example of an interface display device provided in an embodiment of the present application is shown;

[0149] Fig.14 A schematic diagram of the structure of an execution device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0150] The embodiments of the present invention are described below in conjunction with the accompanying drawings in the embodiments of the present invention. The terms used in the implementation mode 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.

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

[0152] 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 need not be 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, which is only to describe the distinction mode adopted by the objects of the same attributes when describing 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.

[0153] 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 may 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 may be the only element or layer between the two elements or layers, or one or more intervening elements or layers may also be present.

[0154] As used herein, the terms "substantially," "about," and the like are used as terms of approximation, not as terms of degree, and are intended to take into account the inherent deviations of measurements or calculations that one of ordinary skill in the art would know. In addition, the use of "may" when describing embodiments of the present invention means "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. In addition, the term "exemplary" is intended to refer to an example or illustration.

[0155] refer to Figure 1 , is a structural diagram of an electronic device 100 provided in an embodiment of the present application.

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

[0157] It is to be understood that the structure illustrated in the embodiment 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 in the figure, or combine some components, or separate some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0158] 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 processor (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), etc. Different processing units may be independent devices or integrated into one or more processors.

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

[0160] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

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

[0162] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple groups of I2C buses. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces. For example: the processor 110 may be coupled to the touch sensor 180K through the I2C interface, so that the processor 110 communicates with the touch sensor 180K through the I2C bus interface, thereby realizing the touch function of the electronic device 100.

[0163] 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 achieve communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit an audio signal to the wireless communication module 160 via the I2S interface to achieve the function of answering a call through a Bluetooth headset.

[0164] 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 to realize the function of answering calls via a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0165] The UART interface is a universal serial data bus for asynchronous communication. The 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 generally 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 through the UART interface to implement the Bluetooth function. In some embodiments, the audio module 170 can transmit an audio signal to the wireless communication module 160 through the UART interface to implement the function of playing music through a Bluetooth headset.

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

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

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

[0169] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present invention is only a schematic 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 in the above embodiments, or a combination of multiple interface connection methods.

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

[0171] 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 supplies power to the processor 110, the internal memory 121, the display screen 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 number, battery health status (leakage, impedance), etc. 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.

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

[0173] 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 the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0174] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., 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.

[0175] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent 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 the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a 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.

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

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

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

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

[0180] The electronic device 100 can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.

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

[0182] 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 optical signal into an electrical signal, and then passes the electrical signal to the ISP to be converted 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.

[0183] The digital signal processor is used to process digital signals, and can process not only digital image signals but also other digital signals. For example, when the electronic device 100 is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0184] Video codecs are used to compress or decompress digital videos. The electronic device 100 may support one or more video codecs. Thus, the electronic device 100 may play or record videos in a variety of coding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

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

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

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

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

[0189] The key 190 includes a power key, a volume key, etc. The key 190 may be a mechanical key or a touch key. The electronic device 100 may receive key input and generate key signal input related to user settings and function control of the electronic device 100.

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

[0191] Indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, messages, missed calls, notifications, etc.

[0192] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to and separated from the electronic device 100 by inserting it into the SIM card interface 195 or pulling it out 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.

[0193] The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the present invention, the Android system of the layered architecture is taken as an example to exemplify the software structure of the electronic device 100.

[0194] Figure 2 1 is a software structure block diagram of the electronic device 100 according to an embodiment of the present invention.

[0195] The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system library, and the kernel layer.

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

[0197] like Figure 2 As shown, the application package may include camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message and other applications.

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

[0199] like Figure 2 As shown, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.

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

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

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

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

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

[0205] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, an electronic device vibrates, an indicator light flashes, etc.

[0206] Android Runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.

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

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

[0209] The system library may include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), etc.

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

[0211] The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

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

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

[0214] Reference Figure 3 , Figure 3This is a schematic diagram of an application architecture of an embodiment of the present application, which includes a user 001 and an electronic device 002. The user 001 is usually the owner of the electronic device 002, and obtains network information and communicates with others through the electronic device 002. The electronic device 002 may be equipped with an operating system and may be installed with a variety of software, such as call applications, text messages, instant messaging software, and email applications. The electronic device receives inputs such as voice and gestures from the user to change the presented interface.

[0215] For the terminal operating system, the overall interaction mode of the system is based on the traditional application-centric interaction mode. In the application-centric architecture mode, when a user wants to complete an intention task, he may need to switch between multiple different applications. For example, when traveling, you need to use the ticket purchase application to buy a plane or train ticket; then use the hotel reservation application to book a hotel; and use the alarm clock to add an alarm to remind you to travel.

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

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

[0218] To solve the above problems, refer to Figure 4 , Figure 4 A schematic diagram of a process of an interface display method provided in an embodiment of the present application is shown as follows: Figure 4 As shown, an interface display method provided in an embodiment of the present application includes:

[0219] 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 a plurality of subtask cards, and each subtask card is a trigger entry for a sub-function of an application.

[0220] 402. Upon receiving a second operation, the event card management interface is switched to an application window management interface.

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

[0222] Method 1: Operations on preset controls.

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

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

[0225] Taking the terminal assistant as an AI assistant control as an example, the user can perform preset interactive operations with the AI ​​assistant control, and display several obscured card groups on the back of the AI ​​assistant control. After the card groups appear, perform a swipe up gesture to enter the event card management interface. Alternatively, perform a swipe up gesture directly at the location of the AI ​​assistant control to enter the event card management interface.

[0226] For example, refer to Fig. 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. Or long press the navigation bar to display the AI ​​assistant control and display several stacked cards on the back of the AI ​​assistant control.

[0227] 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 move the card on the back of the AI ​​assistant control to the middle of the screen with animation display 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.

[0228] 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 operating the navigation bar to trigger the AI ​​assistant control.

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

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

[0231] For example, the event card management interface may be opened by a selection operation on the first indication information of at least one event card in the event card group in the first interface.

[0232] 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 the first indication information of the at least one event card in the first interface.

[0233] Taking the AI ​​assistant as an example, in one possible implementation, after long pressing and sliding up the AI ​​assistant control, two card groups will be displayed: one is the card group of event cards (this card group is not the event card management interface itself, but its thumbnail), and the other is the window group of 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 groups.

[0234] For example, you can use continuous gestures to complete it. 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.

[0235] Fig.10 The figure shows how to enter the event card management interface and application window management interface under the same operation path. Long press the AI ​​assistant icon and swipe up to call out the card group. The event card group 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 group to enter the event card management interface. Fig.10 After swiping up, continue to swipe right, or release the swipe up gesture and then swipe right. 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. Fig.10 Lower middle branch.

[0236] 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, can be arranged after the thumbnails of the application window management interface).

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

[0238] Reference Fig. 12A , Fig. 12A The interfaces of the thumbnails of the application window group and the thumbnails of the event card group are shown respectively. Both the thumbnails of the application window group and the thumbnails of the event card group have two layers of cards, which 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 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.

[0239] When Fig. 12A By swiping up on the blank area in the thumbnails of the application window group and the thumbnails of the event card group (or the display area of ​​the AI ​​assistant control), you can switch between the interfaces of the thumbnails of the application window group and the thumbnails of the event card group.

[0240] Fig. 12A In the event card management interface, 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 supporting interaction, sliding left and right can drive the application windows in the application window group / event cards in the event card group to slide left and right.

[0241] Although the above description describes the application window group thumbnail and event card group thumbnail interfaces as two interfaces, Fig. 12A It can be seen that these two interfaces are essentially two displays of content with different focuses on one interface. Therefore, in other descriptions, they can also be described as two forms of switching of one interface.

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

[0243] Reference Fig.11 ,exist Fig.11 In the instant messaging software interface, the user long presses the bottom navigation bar to call out the AI ​​assistant control, and a small window displays the latest created or recently opened event cards. After calling out the event card, the user can interact with the AI ​​assistant control and perform preset operations such as long press and swipe up to enter the event card management interface and perform event card management functions.

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

[0245] 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 swiping up on the bottom of the desktop of the interface.

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

[0247] like Figure 8 As shown, 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. An 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.

[0248] In some cases, when the task contained in an event is relatively simple, users 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 enter the management of the application through the multi-application management interface.

[0249] Therefore, in the operating system, there will be both event-centric and application-centric 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.

[0250] In the solution of the present invention, the bottom slides up, and the sliding distance determines 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 sliding distance is within the interval (x1, x2), the event card management interface is entered. If the sliding distance is within the interval (x2, x3), the application window management interface is entered. The application window management interface displays the list of application windows currently running in the operating system.

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

[0252] For example, in one possible implementation, a first operation of the user can be received, and a thumbnail of an 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)); a third operation of the user can also be received, and the second interface is displayed, and the second interface includes a thumbnail of an 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)).

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

[0254] In a possible implementation, event cards can be managed in the event card management interface. Place the touch point on an event card and perform an upward swipe gesture to delete the event card. If the upward swipe distance is not sufficient, the event card automatically bounces back to the event card list. After the deletion is executed, the event card is deleted from the system and the main screen no longer displays the event card.

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

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

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

[0258] Event cards can also use different colors / transparency to indicate the execution status of the event corresponding to the event card. When the task corresponding to the task card in the time card is completed, the corresponding transparency change can be triggered. For example, the event progress can be defined as 0, 25%, 50%, 75%, and 100%, corresponding to opaque to completely transparent. When the subtask corresponding to a task card is completed, if the corresponding ratio is reached, the transparency state of the card will be changed.

[0259] In a possible implementation, the event card can also display the type of the event card through a superscript. For example, the events corresponding to the event card are classified into long-term events and short-term events according to the number of subtasks included, the corresponding time span, etc., and different superscripts are used to represent different types.

[0260] Similar to the application window management interface, the event card management interface can present one or more currently created event card thumbnails, but 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 the event cards that are currently open or have been opened in the historical time period. Optionally, in the event card management interface. Multiple event cards can be stacked on each other, and as the user slides, different event cards can be switched to the middle of the interface and displayed on the top layer.

[0261] In the embodiment of the present application, the operating system presents information to the user based on events. Therefore, the operating system also provides an event management interface (that is, 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 in the event card are completed, the event card can be automatically destroyed by the system, or the user triggers the destruction of the event card after performing a preset operation on the event card.

[0262] For example, refer to Figure 6 , Figure 6 An event card management page and an expanded event card are shown respectively. Figure 6 The event card management page shows two stacked event cards, such as Figure 6 As shown in the figure, on the event card management page, after clicking the Shanghai business trip event card, the event card is expanded (the system task is still a desktop application at this time), and multiple subtask cards included in the event card are displayed. Figure 6 The subtask cards in the program include flight card, accommodation card, weather card and alarm card. All four subtask cards are directly related to the business trip to Shanghai and serve the event of the business trip to Shanghai.

[0263] For the selection of an event card corresponding to a to-do event in the event card management interface, an event card may be presented. The event card corresponding to the to-do event includes a plurality of subtask cards and indication information of the to-do event; each of the subtask cards 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.

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

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

[0266] 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 weather conditions at the destination, and the like.

[0267] In the existing implementation, in order to complete the to-do events, the user needs to open multiple applications separately to perform different subtasks, for example, open the flight booking application to execute the flight booking task, open the hotel booking application to execute the hotel booking task, and open the weather query application to execute the destination weather query task.

[0268] In the 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. In the above manner, the user can operate at the granularity of the subtask under the event. When managing transactions, 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.

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

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

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

[0272] It should be understood that the application in the embodiments of the present application may be an application program installed on a terminal, or may be an application in other forms, such as an H5 application on the cloud side, and the present application is not limited thereto.

[0273] In a 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, the to-do event may be indicated by using the text of the to-do event as a title.

[0274] For example, refer to Figure 6 , Figure 6 An event card management page and an expanded event card are shown respectively. Figure 6 The event card management page shows two stacked event cards, such as Figure 6 As shown in the figure, on the event card management page, after clicking the Shanghai business trip event card, the event card is expanded (the system task is still a desktop application at this time), and multiple subtask cards included in the event card are displayed. Figure 6 The subtask cards in the program include flight card, accommodation card, weather card and alarm card. All four subtask cards are directly related to the business trip to Shanghai and serve the event of the business trip to Shanghai.

[0275] Refer to the figure Fig.12I , Fig.12I A flow chart of a display method is shown, including:

[0276] 1201. Display an event card corresponding to a 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 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.

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

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

[0279] 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 weather conditions at the destination, and the like.

[0280] In the existing implementation, in order to complete the to-do events, the user needs to open multiple applications separately to perform different subtasks, for example, open the flight booking application to execute the flight booking task, open the hotel booking application to execute the hotel booking task, and open the weather query application to execute the destination weather query task.

[0281] In the 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. In the above manner, the user can operate at the granularity of the subtask under the event. When managing transactions, 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.

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

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

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

[0285] It should be understood that the application in the embodiments of the present application may be an application program installed on a terminal, or may be an application in other forms, such as an H5 application on the cloud side, and the present application is not limited thereto.

[0286] In a 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, the to-do event may be indicated by using the text of the to-do event as a title.

[0287] 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:

[0288] Method 1: Perform preset operations on the event card thumbnail on the system desktop

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

[0290] The event card thumbnail can display the information of the included subtasks (or key information, such as indication 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, the preview information of all subtask cards included in the current event card thumbnail is displayed in turn. The preview information can be a direct display of the task card, or it can be a display after extracting the key information of the subtask card and rearranging it.

[0291] The event card is a card container provided by the desktop. When the user clicks the event card thumbnail and the event card is expanded, the application running in the front end is still the desktop. When the user performs a preset operation on the subtask card in the event card, the application that provides the subtask card can be jumped to. At this time, the application corresponding to the subtask card is started and occupies the front end.

[0292] In a possible implementation, the system desktop may not display the application icons of the applications installed on the system, but may display several event card thumbnails on the desktop (or display the application icons and event cards at the same time). The system desktop may be based on events as a dimension, and may present event card thumbnails corresponding to one or more different events.

[0293] It should be understood that since users may have the same subtask requirements in different events, the same task card may exist in different event cards. For example, a user goes on a business trip to a certain place, but has a travel arrangement in between. An event card is created for the business trip and the travel respectively. In both time 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.

[0294] Reference Figure 5 , Figure 5 The system desktop interface and the expanded event card are shown respectively. Figure 5The system desktop shows two event card thumbnails, corresponding to two events (the Shanghai business trip event and the HC conference event). No APP icon is shown. 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 will be displayed in turn. The preview information can be a direct display of the subtask card, or it can be a rearranged display after extracting the key information of the subtask card. In addition to event cards, the system desktop can also add traditional widgets or other interactive entrances, such as Figure 5 Weather card in .

[0295] like Figure 5 As shown in the figure, after clicking the Shanghai business trip event card, the event card is expanded (the system task is still a desktop application at this time), and multiple subtask cards included in the event card are displayed. Figure 5 The subtask cards in the program include flight card, accommodation card, weather card and alarm card. All four subtask cards are directly related to the event of the business trip to Shanghai, and serve the event of the business trip to Shanghai.

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

[0297] Similar to the application window management interface, the event card management interface can present one or more currently created event card thumbnails, but 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 the event cards that are currently open or have been opened in the historical time period. Optionally, in the event card management interface. Multiple event cards can be stacked on each other, and as the user slides, different event cards can be switched to the middle of the interface and displayed on the top layer.

[0298] In the embodiment of the present application, the operating system presents information to the user based on events. Therefore, the operating system also provides an event management interface (that is, 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 in the event card are completed, the event card can be automatically destroyed by the system, or the user triggers the destruction of the event card after performing a preset operation on the event card.

[0299] For example, refer to Figure 6 , Figure 6 An event card management page and an expanded event card are shown respectively. Figure 6 The event card management page shows two stacked event cards, such as Figure 6As shown in the figure, on the event card management page, after clicking the Shanghai business trip event card, the event card is expanded (the system task is still a desktop application at this time), and multiple subtask cards included in the event card are displayed. Figure 6 The subtask cards in the program include flight card, accommodation card, weather card and alarm card. All four subtask cards are directly related to the business trip to Shanghai and serve the event of the business trip to Shanghai.

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

[0301] Method 3: By operating the preset controls

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

[0303] For example, full-screen mobile phones are generally equipped with a navigation bar at the bottom. By interacting with the navigation bar, the AI ​​assistant control can be called out (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. The AI ​​assistant control can be displayed permanently 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 can no longer be displayed, or the AI ​​assistant control can be considered to be displayed on the upper layer of the navigation bar.

[0304] Figure 7 In the app, users can long press the bottom navigation bar to call out the AI ​​assistant control, and a small window will be used to display the latest created or recently opened event cards. After calling out the event card, users can open the event card corresponding to the to-do event by clicking on the event card.

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

[0306] The above embodiment introduces an event card management interface, which may 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).

[0307] In a possible implementation, the first operation may be received to display the event card management interface. Next, the method of entering the event card management interface is introduced:

[0308] Method 1: Operations on preset controls.

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

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

[0311] Taking the terminal assistant as an AI assistant control as an example, the user can perform preset interactive operations with the AI ​​assistant control, and display several obscured card groups on the back of the AI ​​assistant control. After the card groups appear, perform a swipe up gesture to enter the event card management interface. Alternatively, perform a swipe up gesture directly at the location of the AI ​​assistant control to enter the event card management interface.

[0312] For example, refer to Fig. 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. Or long press the navigation bar to display the AI ​​assistant control and display several stacked cards on the back of the AI ​​assistant control.

[0313] 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 move the card on the back of the AI ​​assistant control to the middle of the screen with animation display 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.

[0314] 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 operating the navigation bar to trigger the AI ​​assistant control.

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

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

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

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

[0319] Taking the AI ​​assistant as an example, in one possible implementation, after long pressing and sliding up the AI ​​assistant control, two card groups will be displayed: one is the card group of event cards (this card group is not the event card management interface itself, but its thumbnail), and the other is the window group of 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 groups.

[0320] For example, you can use continuous gestures to complete it. 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.

[0321] Fig.10 The figure shows how to enter the event card management interface and application window management interface under the same operation path. Long press the AI ​​assistant icon and swipe up to call out the card group. The event card group 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 group to enter the event card management interface. Fig.10After swiping up, continue to swipe right, or release the swipe up gesture and then swipe right. 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. Fig.10 Lower middle branch.

[0322] 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, can be arranged after the thumbnails of the application window management interface).

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

[0324] Reference Fig. 12A , Fig. 12A The event card management interface and the application window management interface are shown respectively. Both the event card management interface and the application window management interface 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.

[0325] When Fig. 12A You can switch between the event card management interface and the application window management interface by swiping up in the blank area of ​​the event card management interface and the application window management interface (or the display area of ​​the AI ​​assistant control).

[0326] Fig. 12AIn the event card management interface, 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 supporting interaction, sliding left and right can drive the application windows in the application window group / event cards in the event card group to slide left and right.

[0327] Although the application window management interface and the event card management interface are described as two interfaces in the above description, Fig. 12A It can be seen that these two interfaces are essentially two displays of content with different focuses on one interface. Therefore, in other descriptions, they can also be described as two forms of switching of one interface.

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

[0329] Reference Fig.11 ,exist Fig.11 In the instant messaging software interface, the user long presses the bottom navigation bar to call out the AI ​​assistant control, and a small window displays the latest created or recently opened event cards. After calling out the event card, the user can interact with the AI ​​assistant control and perform preset operations such as long press and swipe up to enter the event card management interface and perform event card management functions.

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

[0331] 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 swiping up on the bottom of the desktop of the interface.

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

[0333] like Figure 8As shown, 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. An 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.

[0334] In some cases, when the task contained in an event is relatively simple, users 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 enter the management of the application through the multi-application management interface.

[0335] Therefore, in the operating system, there will be both event-centric and application-centric 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.

[0336] In the solution of the present invention, the bottom slides up, and the sliding distance determines 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 sliding distance is within the interval (x1, x2), the event card management interface is entered. If the sliding distance is within the interval (x2, x3), the application window management interface is entered. The application window management interface displays the list of application windows currently running in the operating system.

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

[0338] For example, in one possible implementation, a first operation of the user can be received, and a thumbnail of an 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)); a third operation of the user can also be received, and the second interface is displayed, and the second interface includes a thumbnail of an 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)).

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

[0340] In a possible implementation, event cards can be managed in the event card management interface. Place the touch point on an event card and perform an upward swipe gesture to delete the event card. If the upward swipe distance is not sufficient, the event card automatically bounces back to the event card list. After the deletion is executed, the event card is deleted from the system and the main screen no longer displays the event card.

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

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

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

[0344] Event cards can also use different colors / transparency to indicate the execution status of the event corresponding to the event card. When the task corresponding to the task card in the time card is completed, the corresponding transparency change can be triggered. For example, the event progress can be defined as 0, 25%, 50%, 75%, and 100%, corresponding to opaque to completely transparent. When the subtask corresponding to a task card is completed, if the corresponding ratio is reached, the transparency state of the card will be changed.

[0345] In a possible implementation, the event card can also display the type of the event card through a superscript. For example, the events corresponding to the event card are classified into long-term events and short-term events according to the number of subtasks included, the corresponding time span, etc., and different superscripts are used to represent different types.

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

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

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

[0349] 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 a navigation bar, terminal assistant controls), so that the event card corresponding to the to-do event can be switched to the application window management interface.

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

[0351] In one possible implementation, a creation request for the to-do event input by a user can be received, and based on the creation request, requirement information of multiple subtasks for implementing the to-do event and an application for executing the function of each subtask can be determined, and the requirement information of the multiple subtasks can be used as a query input. Through interaction with the corresponding application, the requirement feedback results of each subtask can be obtained, and the requirement feedback results are used to construct the multiple subtask cards.

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

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

[0354] Specifically, the terminal device may forward the received to-do event creation request to the AI ​​assistant, and the AI ​​assistant parses the to-do event creation request. If the parsing result meets the requirements for event card creation, an event card is created, and at least one subtask of the event is presented in the event card.

[0355] For example, if keywords such as itinerary, task, to-do, travel, and tourism are identified, 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.

[0356] The subtasks of an event can be obtained based on the parsing results of the creation request of the pending event, or can be recommended by the large language model based on the type of event. For example, for itinerary arrangements, subtasks such as air ticket booking / train ticket booking and hotel booking can be included. After obtaining at least one subtask of an event, the subtask is displayed in the event card.

[0357] It is understandable that in 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 at the same time.

[0358] like Fig. 12B , the user's request to create a to-do event is "Help me arrange a business trip to Shanghai from next Sunday to Wednesday", then according to the parsing result, create an event card of the business trip itinerary type, and the name of the event card is "Shanghai business trip itinerary". Based on the business trip itinerary type event, the subtasks of booking flights and booking hotels are recommended to the user and displayed in the event card.

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

[0360] The user's input may be a preset operation on the target subtask, for example, clicking the text / control corresponding to the target subtask. Fig. 12B , click the control corresponding to "Book a flight" to set booking a flight as the target subtask.

[0361] After determining the target subtask, the associated application of the target subtask can be determined according to the preset rules. Specifically, the target subtask has different types, and correspondingly, the application also has at least one tag. By establishing a preset relationship between the type of the target subtask and the application tag, the associated application of the target subtask can be determined from the local applications installed by the user.

[0362] For example, the target subtask is "booking air tickets", and the corresponding task type is the air ticket booking category in the transportation category. The application tags corresponding to the transportation category include travel, air ticket booking, and flight. The corresponding associated applications can be ticket booking software and flight query software.

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

[0364] 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 the subsequent interaction with the user.

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

[0366] For example, Fig. 12B In the input, in addition to parsing the user's intention - arranging a business trip to Shanghai, and the event type being the itinerary arrangement class, the time information "Sunday to Wednesday" and the location information "Shanghai" can also be obtained.

[0367] In this way, by combining the associated information and the target subtask, the demand information can be obtained, and the demand information is sent as a query input to the associated application as an input of the associated application. In the above example, by combining the time information "Sunday to Wednesday", the location information "Shanghai" and the target subtask of air ticket booking, the query input that can be determined is "book an air ticket from the current city to Shanghai on Sunday".

[0368] In a possible implementation, a query process interface may be used to guide the user to supplement the required information. Optionally, the query process interface displays at least one query information, and each query information corresponds to a related application. Fig. 12C The query process interface is shown, showing 2 query information, corresponding to APP1 and APP2, respectively querying flight ticket information and flight punctuality information.

[0369] In this solution, the query process interface includes the identifier of the associated application, and other associated applications of the same type can be switched by interacting with the identifier of the associated application. Fig.12D In the menu, click APP1, and a list of apps with the same label as APP1 - Flight Booking - will be displayed. You can switch to different apps by selecting an app in the list. If the selected app is not installed locally, it will be linked to the app market to download and install it before switching.

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

[0371] Specifically, depending on the target subtask, the terminal can filter information according to different dimensions. Common dimensions include: departure date, departure time, price, punctuality, and time spent on the way. Specific dimension information is built-in by the system. A filtering information can be presented on the time card interface. The filtering information provides the filtering dimension. The dimension information is presented in the form of a control. By interacting with the dimension information control, you can change the filtering dimension or enter detailed information about the dimension.

[0372] Fig.12DTwo situations of interacting with the dimension information control are shown respectively. They correspond to changing the dimension and entering dimension details. In the left picture, click the "price" dimension information control, and a small window pops up to list other dimension information currently available for selection. Select one from them to replace the price as the filtering dimension. In the right picture, click 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 of the target subtask. After filtering and obtaining the recommended information, the recommended information will be displayed in the event card. Fig.12E The display of recommended information in the event card is shown. The user can select target recommended information from the recommended information by touch or voice input. The recommended information corresponding to the touch input can be detected as the target recommended information or the recommended information can be determined as the target recommended information according to voice analysis.

[0373] After determining the target recommendation information, you can create a task card corresponding to the target subtask based on the target recommendation information. Fig.12E In the example, after the user selects one of the ticket information, a flight task card can be created based on the ticket information.

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

[0375] Fig.12F In order not to occupy the display area, before the task card corresponding to the end target subtask is created, the created task card is displayed as a thumbnail in the task card. After the task card corresponding to the end target subtask is created, the task card is fully displayed.

[0376] When multiple task cards are performing the same operation, batch processing can be achieved. For example, when paying for an order, through the payment control in the card, or interacting with a single task card to enter the payment interface, the user can select task cards to make a unified payment, or select only some task cards to pay for those task cards. When only one task card is selected, only the order of that task card will be paid.

[0377] After the task card corresponding to the end target subtask is created, the task card can also be recommended to the user based on the type of event card, and the user can choose to add the task card to the event card. Figure 12G In the task card list, select the recommended card and click Add. The task card is added to the event card. If you do not select it or perform a back gesture, the recommended card will not be added.

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

[0379] 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 a sixth operation is received to switch the editing page of the first subtask 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.

[0380] In a possible implementation, the creation process of the first subtask can be interrupted while the creation process of the second subtask is being created, and the creation process of the second subtask can be performed, and then the first subtask can be returned to continue to be created, and the creation content that has been previously entered in the first subtask is retained (it should be understood that the creation content is the user's requirement information for the subtask). Specifically, the seventh operation can be received, the editing page of the second subtask is switched 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 enter on the editing page is received.

[0381] For example, when there are multiple subtasks, you can switch between different subtask cards by swiping up / down during the card creation process. When switching to other subtask cards, you can interrupt the creation of the current subtask card and save the creation progress; if other subtask cards have not been created, swipe up / down to jump to the subtask list interface. When switching back to the interrupted subtask card creation, continue to create the subtask card.

[0382] When there are multiple subtask cards (including interrupted / created subtask cards), 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.

[0383] Fig.12H The swipe up gesture and long press gesture operations in the process of booking a flight are shown respectively. Assuming that the hotel booking subtask has been completed before booking a flight, swipe up to switch to display the hotel booking card, and support further payment, modification and other operations. Long press to display a list of all subtask cards. Currently, there are only two subtasks, so the flight booking card and hotel booking card are displayed.

[0384] In the embodiment of the present application, the associated application can be automatically determined at the system level by parsing the creation request of the event card, and the associated application can be called to create a subtask card. There is no need to enter each associated application to implement multiple subtasks under an event. All operations can be completed on the system desktop without the need for application switching, interface jump, etc., which simplifies the subtask processing flow of the event.

[0385] Reference Fig.13 , Fig.13 The structure of an interface display device provided in an embodiment of the present application is schematically shown, wherein the device 1300 includes:

[0386] 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, each of which is a trigger entry for a sub-function of an application; and receive a second operation, triggering the display module 1302 to switch the event card management interface to an application window management interface.

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

[0388] 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,

[0389] a selection operation for the first indication information of the at least one event card in the first interface; or,

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

[0391] In a 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.

[0392] In a 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:

[0393] 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 an effective distance of the sliding operation in the third operation is within a second preset range.

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

[0395] Receiving a selection of a thumbnail of a target event card in 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.

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

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

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

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

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

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

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

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

[0404] Receive a request for creating a to-do event input by the user;

[0405] 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;

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

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

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

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

[0410] Trigger the display module 1302 to display an editing page for the first subtask;

[0411] Receive first requirement information of the first subtask input by the user on the editing page;

[0412] Receive a sixth operation, and trigger the display module 1302 to switch the editing page of the first subtask to an editing page of the second subtask;

[0413] Receive requirement information of the second subtask input by the user on the editing page.

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

[0415] Receive a seventh operation, and trigger the display module 1302 to switch the editing page of the second subtask to an editing page of the first subtask including the first requirement information;

[0416] Receive second requirement information of the second subtask continuously input by the user on the editing page.

[0417] In addition, the present application further provides an interface display device, including:

[0418] A processing module, configured to display an event card corresponding to a to-do event, where the event card corresponding to the to-do event includes a plurality of subtask cards and indication information of the to-do event; each of the subtask 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 plurality of subtask cards are associated with the to-do event;

[0419] Receive a fifth operation, and switch 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.

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

[0421] Receive a fourth operation; where

[0422] The fourth operation is selecting an event card corresponding to the to-do event in the system desktop or 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

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

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

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

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

[0427] receiving a selection operation of a first thumbnail of the first indication information event card group for 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,

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

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

[0430] A first operation is received, wherein:

[0431] The first operation is a swiping 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.

[0432] In a 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.

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

[0434] When a third operation is received, 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.

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

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

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

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

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

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

[0441] 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;

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

[0443] 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 a user for the multiple subtasks.

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

[0445] The processing module is specifically used for:

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

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

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

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

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

[0451] 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;

[0452] The second requirement information of the second subtask which is continuously input by the user on the editing page is received.

[0453] Next, an execution device provided by an embodiment of the present application is introduced. Fig.14 , Fig.14 This is a schematic diagram of a structure of an execution device provided in an embodiment of the present application. The execution device 1400 can be specifically 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, Fig.14 In the example of FIG. 1403 , 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.

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

[0455] The processor 1403 controls the operation of the execution device. In a specific application, the various components of the execution device are coupled together through a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus, and a status signal bus, etc. However, for the sake of clarity, various buses are referred to as bus systems in the figure.

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

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

[0458] In one embodiment of the present application, the processor 1403 is configured to execute Figure 4 as well as Fig.12I The steps of the interface display method in the corresponding embodiment.

[0459] The 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.

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

[0461] It should also be noted that the device embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, 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 over multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, in the drawings of the device embodiments provided by the present application, the connection relationship between the modules indicates that there is a communication connection between them, which may be specifically implemented as one or more communication buses or signal lines.

[0462] Through the description of the above implementation mode, the technicians in the field can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course, it can also be implemented by special hardware including special integrated circuits, special CPUs, special memories, special components, etc. In general, all functions completed by computer programs can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be various, such as analog circuits, digital circuits or special circuits. However, for the present application, software program implementation is a better implementation mode in more cases. Based on such an 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 floppy disk, a U disk, a mobile hard disk, a ROM, a RAM, a disk or an optical disk, etc., including a number of instructions to enable a computer device (which can be a personal computer, a training device, or a network device, etc.) to execute the methods described in each embodiment of the present application.

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

[0464] 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 may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may 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 may be transmitted from a website site, 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 site, computer, training device, or data center. The computer-readable storage medium may 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 may 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)), etc.

Claims

1. An interface display method, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is characterized in that The display state is color or transparency.

8. The method according to any one of claims 1 to 7, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is characterized in that The display state is color or transparency.

22. The device according to any one of claims 16 to 21, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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, It is 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