Transaction management method and electronic equipment

Abstract

The invention provides a transaction management method and electronic equipment, the method is mainly characterized in that a transaction management function is built in a calendar application, all transactions of the day are intensively displayed by setting a card display area and a time axis display area, the transactions which need to be emphatically managed and checked by a user are recommended and displayed in the card display area, and the time axis display area is used for displaying the transactions which need to be emphatically managed and checked by the user. For example, transactions with time conflicts can be displayed in the card display area in the form of reminding cards, transactions on the day are connected in series in the time axis display area through the time axis, and the transactions are managed through linkage between the card display area and the time axis display area. According to the scheme, affairs needing to be focused and managed by a user are displayed in a centralized mode through the card display area, all affairs needing to be processed in one day are connected in series from the time dimension through the time axis display area, and through linkage operation of the two display areas, the user can conveniently and rapidly check and manage the affairs.

Description

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on November 3, 2023, with application number 202311464467.7 and application name “Transaction Management Method and Electronic Device”, all contents of which are incorporated by reference in this application. Technical Field

[0002] The present application relates to the technical field of electronic equipment, and in particular to a transaction management method and electronic equipment. Background Art

[0003] In order to avoid forgetting things, users often create alarm reminders, calendar reminders or schedules to remind themselves not to miss things. However, these reminders are scattered in different applications, which may cause users to forget which application they created the reminder in, and there may be time conflicts between the created tasks, but it is difficult for users to find out.

[0004] Therefore, how to better manage affairs is a technical problem that needs to be solved urgently. Summary of the invention

[0005] The present application provides a transaction management method and an electronic device, which can centrally manage all transactions of the same day, so that users can better plan all transactions of the day based on this.

[0006] In a first aspect, a transaction management method is provided, the method comprising: displaying a first interface of a calendar application, the first interface comprising a first control; in response to a first operation of a user on the first control, displaying a second interface of the calendar application, the second interface comprising a card display area and a timeline display area; wherein the card display area comprises a conflicting transaction reminder card; the timeline display area comprises a timeline and a card of a first transaction, the first transaction corresponds to a first time node on the timeline; in response to a second operation of the user on the conflicting transaction reminder card, displaying a third interface of the calendar application, the third interface comprises a card of a second transaction and a card of a third transaction, the cards of the second transaction and the third transaction are located in the timeline display area, the second transaction corresponds to a second time node on the timeline, the third transaction corresponds to a third time node on the timeline, and there is a time conflict between the second transaction and the third transaction.

[0007] In the technical solution of the present application, the affairs that need to be focused and managed by the user are displayed in a centralized manner mainly through the card display area, and all the affairs that need to be handled in a day are connected in series from the time dimension through the timeline display area, and the linkage operation of the two display areas is convenient for users to quickly view and manage affairs. In the timeline display area, all reminder affairs of the whole day are displayed in a centralized manner according to the timeline, and the centralized management of all affairs that need to be handled on the target date from the time dimension is realized, so that users can not only know what things need to be done on the target date, but also know what to do first and what to do later on this day, so that users can better plan their affairs for the whole day based on this. In the card display area, affairs that need to be focused and managed by users, such as conflicting affairs, are displayed in a centralized manner, that is, the affairs that are most likely to meet the user's management needs are presented in the form of reminder cards in the card display area, which can facilitate users to quickly find the affairs that need to be managed. The linkage operation between the two display areas can facilitate users to quickly view and manage affairs. For example, here, users can click on the conflicting affairs reminder card in the card display area to locate the corresponding affairs on the timeline display area, and then manage the corresponding affairs.

[0008] It should be understood that the transaction management for the target date may be the advance review and management before the target date, or it may be the review and management during the target date.

[0009] In conjunction with the first aspect, in certain implementations of the first aspect, the conflicting transaction reminder card includes a viewing control, and the second operation is an operation of clicking the viewing control. In this implementation, the display of the third interface is mainly triggered by clicking the viewing control in the conflicting transaction reminder card, that is, the positioning display of the transaction corresponding to the conflicting transaction reminder card in the timeline display area. Setting the viewing control can more clearly indicate to the user how to use the conflicting transaction reminder card.

[0010] In addition to the click operation of the above-mentioned viewing control, the conflicting transaction reminder card can also be clicked to trigger the positioning display of the transaction corresponding to the conflicting transaction reminder card in the timeline display area. In other words, the second operation can also be the operation of clicking the conflicting transaction reminder card. In this case, the conflicting transaction reminder card may not include a viewing control.

[0011] In combination with the first aspect, in certain implementations of the first aspect, the card of the second transaction is fully displayed in the third interface; and / or the card of the third transaction is fully displayed in the third interface. In this implementation, when the third interface is displayed under the triggering of the second operation, it is ensured that at least one card of the conflicting transaction is fully displayed in the third interface. This facilitates the user to view and manage conflicting transactions.

[0012] In combination with the first aspect, in some implementations of the first aspect, the method further includes: when it is detected that the time conflict between the second transaction and the third transaction is resolved, the conflicting transaction reminder card is stopped from being displayed in the card display area; or, when it is detected that the execution time period of the second transaction and / or the execution time period of the third transaction is over, the conflicting transaction reminder card is stopped from being displayed in the card display area. In this implementation, the display of the conflicting transaction reminder card can be stopped when the conflict between the conflicting transactions is resolved, or when the conflicting transactions do not need to be investigated for their conflicts due to the advancement of natural time. For the case where the conflicting transaction reminder card is stopped when the execution time period of only one transaction has not ended, it can be understood that when the execution time period of one of the two conflicting transactions has ended, there is only one transaction that needs to be processed immediately or is being processed at the current time, and at this time, there is no need to investigate the conflict between the currently executing transaction and the ended transaction. For the case where the conflicting transaction reminder card is stopped when the execution time period of all transactions has ended, it can be understood that when the execution time periods of the two conflicting transactions have ended, there is no need to investigate the conflict between the two ended transactions at the current time.

[0013] In combination with the first aspect, in some implementations of the first aspect, the third interface also includes a card of a fourth transaction, the card of the fourth transaction is located in the timeline display area, and the fourth transaction corresponds to a fourth time node on the timeline; the fourth transaction has a time conflict with the second transaction, and / or the fourth transaction has a time conflict with the third transaction, and the above method also includes: when it is detected that the time conflict between any two transactions among the second transaction, the third transaction and the fourth transaction is resolved, the conflict information in the conflict transaction reminder card is updated in the card display area; or, when it is detected that all time conflicts between the second transaction, the third transaction and the fourth transaction are resolved, the conflict transaction reminder card is stopped from being displayed in the card display area; or, when it is detected that at most one of the second transaction, the third transaction and the fourth transaction has not ended, the conflict transaction reminder card is stopped from being displayed in the card display area. In this implementation, mainly for the situation where there are conflicts among three transactions, when the conflicts between only some of the transactions are resolved, the conflict information in the conflict transaction reminder card is updated, and the display of the conflict reminder card can be stopped when the conflicts between all transactions are resolved, or when there are conflicting transactions, due to the advancement of natural time, there is only at most one transaction whose execution time period has not ended, the display of the conflict reminder card is stopped.

[0014] It should also be understood that the situation where there are conflicts among four or more transactions is similar to the handling method of the above three transactions, that is, when the conflicts between only some of the transactions are resolved, the conflict information in the conflict transaction reminder card is updated, and the display of the conflict reminder card can be stopped when the conflicts between all transactions are resolved, or when there are conflicting transactions and due to the natural advancement of time, there is only one transaction whose execution time period has not ended, the display of the conflict reminder card is stopped. The only difference from the above is the total number of conflicting transactions.

[0015] In combination with the first aspect, in certain implementations of the first aspect, after displaying the second interface of the calendar application, the method further includes: in response to a user sliding operation on a card of the first transaction, displaying at least one management control, the at least one management control including at least one of an important transaction marking control, a transaction deletion control, an ignore reminder control, and a postpone reminder control, wherein the important transaction marking control is used to indicate that the first transaction is marked as an important transaction, the transaction deletion control is used to indicate that the card of the first transaction in the timeline display area is deleted, the ignore reminder control is used to indicate that the first transaction is no longer reminded, and the postpone reminder control is used to indicate that a new time node corresponding to the first transaction is determined on the timeline; in response to a user clicking operation on a first management control in at least one management control, managing the first transaction according to the instruction of the first management control. In this implementation, the management of the card of the transaction in the timeline display area is mainly given, the management control is displayed by sliding the card, and the corresponding management is realized by operating the controls corresponding to different management targets.

[0016] In combination with the first aspect, in some implementations of the first aspect, the timeline display area includes a first folding control, and the first folding control corresponds to a first time period on the timeline. The above method also includes: in response to a user clicking the first folding control, the time period identifier of the first time period and the number of transactions in the first time period are displayed in the timeline display area, and the card corresponding to the first time period in the timeline display area is hidden. In this implementation, by setting a folding control in the timeline display area, it is convenient for users to fold and hide transactions according to time periods. Correspondingly, the user can also release the folding state by operating the expansion control, so that the folded and hidden transactions are re-displayed in the interface.

[0017] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: when entering the second interface at the first time, a card for the fifth transaction is included in the timeline display area, the fifth transaction corresponds to the fifth time node on the timeline, and the fifth time node is determined according to the first time; when entering the second interface at the second time, a card for the sixth transaction is included in the timeline display area, the sixth transaction corresponds to the sixth time node on the timeline, and the sixth time node is determined according to the second time. In this implementation, when entering the second interface at different times, different interface contents will be presented, that is, the display of the second interface will locate the time node on the timeline according to the time point of entry and display the card of the transaction corresponding to the time node.

[0018] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: when entering the second interface at the first time, displaying the first part of the timeline as the first color, the second part of the timeline as the second color, the first part being the part of the timeline before the first time, and the second part being the part of the timeline after the first time; when entering the second interface at the second time, displaying the third part of the timeline as the first color, the fourth part of the timeline as the second color, the third part being the part of the timeline before the second time, and the fourth part being the part of the timeline after the second time. In this implementation, when entering the second interface at different times, different timeline color distributions will be seen, that is, the color distribution of the timeline in the second interface will locate the time node on the timeline according to the time point of entry, and display the color before the time node and the color after the time node as two different colors, respectively.

[0019] In conjunction with the first aspect, in certain implementations of the first aspect, the timeline display area includes an all-day affairs portion and a time-divided affairs portion, and the timeline of the all-day affairs portion and the timeline of the time-divided affairs portion are different in form, the all-day affairs portion is used to display cards for affairs whose execution time period is a whole day, and the time-divided affairs portion is used to display affairs whose execution time period is not a whole day. In this implementation, affairs without a clear execution time period (all-day affairs) and affairs with a clear execution time period (time-divided affairs) are displayed separately and in a centralized manner, and they are also distinguished on the timeline, which can facilitate users to view and manage the two types of affairs separately.

[0020] In conjunction with the first aspect, in certain implementations of the first aspect, the card of the first transaction includes at least one of the following: a title of the first transaction, an execution time period of the first transaction, a location of the first transaction, and an application source mark of the first transaction. In this implementation, the content of the transaction card is described, and it should be understood that the cards of other transactions connected in series on the timeline can be the same as the card of the first transaction.

[0021] In combination with the first aspect, in certain implementations of the first aspect, the card of the first transaction includes a jump control, and the method further includes: in response to a user clicking the jump control, displaying a fourth interface of the first application, the first application being an application corresponding to the jump control, and the fourth interface being an initial interface of the first application or an interface corresponding to the jump control. In this implementation, by setting a jump control in the card of the transaction, it is convenient for the user to switch applications with one click, which can be switching to the homepage (initial interface) of another application (non-calendar application), or directly jumping to an interface corresponding to the jump control in another application.

[0022] In combination with the first aspect, in certain implementations of the first aspect, the card display area also includes at least one of a departure reminder card, a basic card, a tomorrow's schedule reminder card, a time anomaly reminder card, and a special day reminder card; the departure reminder card is used to remind departures for matters that require travel in the timeline display area, the basic card is used to display date information and weather information, the tomorrow's schedule reminder card is used to display statistics for the next day's affairs, the time anomaly reminder card is used to display matters that need to be arranged in advance for the next day, and the special day reminder card is used to display date information and matter content for special days. In this implementation, other cards that can be displayed in the card display area are explained, that is, the card display area can display different types of reminder cards to enrich the display content and better meet the management needs of users.

[0023] In combination with the first aspect, in some implementations of the first aspect, the method further includes: displaying a first reminder card in a card display area in the second interface; and displaying a second reminder card in the card display area of ​​the second interface in response to a third operation of the user on the card display area in the second interface, wherein the third operation is used to switch the card displayed in the card display area. In this implementation, the reminder card currently displayed in the card display area can be switched by the third operation. It should be understood that the first reminder card and the second reminder card here can be any of the above reminder cards.

[0024] When the card display area is pinned on top of the timeline display area and the reminder card is arranged horizontally (horizontally) in the card display area, the third operation may be a horizontal sliding operation on the card display area; when the card display area and the timeline display area are distributed left and right and the reminder card is arranged vertically in the card display area, the third operation may be a vertical sliding operation on the card display area.

[0025] In combination with the first aspect, in certain implementations of the first aspect, in the second interface, the cards in the card display area and the timeline display area correspond to the first date; after displaying the second interface of the calendar application, the method further includes: in response to the user's date switching operation in the second interface, displaying the fifth interface of the calendar application, in which the cards in the card display area and the timeline display area correspond to the second date, and the date switching operation is a swipe up operation, a swipe down operation, or a click operation on the date switching control. In this implementation, a method for switching to a transaction management interface of another date is provided, which can mainly switch to the previous day or the next day by swiping up or swiping down, and independently select a date by clicking on the date switching control.

[0026] In a second aspect, a transaction management device is provided, which includes a unit composed of software and / or hardware for executing any one of the methods of the first aspect.

[0027] According to a third aspect, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, any one of the methods of the first aspect can be implemented.

[0028] In a fourth aspect, a chip is provided, comprising a processor, wherein the processor is used to read and execute a computer program stored in a memory, and when the computer program is executed by the processor, any one of the methods of the first aspect can be implemented.

[0029] Optionally, the chip also includes a memory, and the memory is electrically connected to the processor.

[0030] Optionally, the chip may also include a communication interface.

[0031] According to a fifth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, any one of the methods of the first aspect can be implemented.

[0032] According to a sixth aspect, a computer program product is provided. The computer program product comprises a computer program, and when the computer program is executed by a processor, any one of the methods of the first aspect can be implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 It is a schematic diagram of the transaction management interface of an embodiment of the present application.

[0034] Figure 2 A schematic diagram of a transaction management interface in an embodiment of the present application.

[0035] Figure 3 It is a schematic diagram of a timeline display area of ​​an embodiment of the present application.

[0036] Figure 4 It is a schematic diagram of a method for setting a folded or unfolded calendar according to an embodiment of the present application.

[0037] Figure 5 This is a schematic diagram of the automatic positioning display according to the current time in an embodiment of the present application.

[0038] Figure 6 It is a design schematic diagram of the schedule arrangement style and the to-do list style of the embodiment of the present application.

[0039] Figure 7 It is a schematic diagram of the execution process of a management schedule type in an embodiment of the present application.

[0040] Figure 8 It is a schematic diagram of an execution process of managing to-do item types according to an embodiment of the present application.

[0041] Fig. 9 It is a schematic diagram of an execution process of postponing reminders for to-do items in an embodiment of the present application.

[0042] Fig.10 It is a schematic diagram of a reminder card format according to an embodiment of the present application.

[0043] Fig.11 It is a schematic diagram of a departure reminder card according to an embodiment of the present application.

[0044] Fig.12 It is a schematic diagram of a conflict reminder card according to an embodiment of the present application.

[0045] Fig.13 It is a schematic diagram of tomorrow's schedule reminder card and time anomaly reminder card in an embodiment of the present application.

[0046] Fig.14 It is a schematic diagram of a basic card of an embodiment of the present application.

[0047] Fig.15 It is a schematic diagram of a special day reminder card and a time abnormality reminder card according to an embodiment of the present application.

[0048] Fig.16 It is a schematic diagram of an interactive process of switching a target date according to an embodiment of the present application.

[0049] Fig.17 It is a schematic diagram of another interactive process of switching the target date according to an embodiment of the present application.

[0050] Fig.18 It is a schematic diagram of another interactive process of switching the target date according to an embodiment of the present application.

[0051] Fig.19 It is a schematic flowchart of a transaction management method in an embodiment of the present application.

[0052] Fig. 20 It is a schematic diagram of the hardware structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0053] The scheme of the embodiment of the present application is introduced below with reference to the accompanying drawings.

[0054] In traditional solutions, the management of reminder transactions is decentralized. For ease of understanding, a specific example is used to illustrate. Suppose that on August 30, a user subscribed to a game event that started at 15:00 on September 3 and created a reminder for the event (it could be created from the game application or manually in the calendar application), that is, a transaction was created, which was "Attend the game event at 15:00 on September 3"; later on September 2, the user created a reminder for a friend's birthday party that started at 18:00 on September 3 (that is, a transaction was created "Attend the friend's birthday party at 18:00 on September 3"), but the user forgot that he had also created a reminder for online course registration from 17:00 to 19:00 on September 3 on August 20 (that is, a transaction was created "Online course registration from 17:00 to 19:00 on September 3"). In this example, since reminders are created separately, and tasks may be managed separately in different applications such as notes / memos and calendars after they are created, it is difficult for users to find the conflicts. Moreover, when September 3 arrives, users cannot clearly know what they need to do that day, nor can they know what to do first and what to do later that day.

[0055] In other words, in traditional solutions, since the creation and management of transactions are decentralized, users cannot plan and coordinate all transactions without missing any transactions just because of reminders.

[0056] In response to the above problems, the present application provides a new transaction management method, which realizes the centralized management of all possible transactions from the time dimension by centrally displaying all transactions of the whole day according to the timeline, that is, connecting all transactions of the whole day with the timeline, so that users can not only know what things need to be done on the target date, but also know what to do first and what to do later on this day, so that users can better plan their affairs for the whole day based on this. In addition, for conflicting transactions, they will be displayed in the card display area through conflicting transaction reminder cards, and users can also quickly locate conflicting transactions on the timeline through conflicting transaction reminder cards, so as to manage these transactions. In addition, regardless of whether these reminder transactions come from different applications, or whether the creation dates are far apart, there will no longer be a series of problems in traditional solutions that are missed or conflicts cannot be discovered due to decentralized management.

[0057] Figure 1 Schematic diagram of the transaction management interface of the embodiment of the present application. Figure 1 As shown, a "My Day" function can be added to the calendar application. After the user turns on the "My Day" function, the electronic device can display the display interface of "My Day". Figure 1 (a) and Figure 1 (c) shows an example of the "My Day" display interface. Figure 1 The calendar app is an example of a calendar app like the one below. Figure 1 The "My Day" interface shown is an example of a transaction management interface. Figure 1 The date shown for My Day is an example of a target date.

[0058] exist Figure 1 In the example, the calendar application includes three functions: "Calendar", "My Day" and "To Do". The "Calendar" in the function bar corresponds to the month view interface, "My Day" corresponds to the transaction management interface, and "To Do" corresponds to the to-do management interface.

[0059] exist Figure 1 (a) and Figure 1 The display interface shown in (c) is the management interface of the "My Day" function. Assume that the user is Figure 1 In the display interface shown in (a), click "Calendar" in the function bar to enter (switch to) the month view interface. Figure 1 As shown in (b). Figure 1 (b) shows an example of a month view interface. Figure 1 In the month view interface shown in (b), click "My Day" in the function bar to switch the display interface from the month view interface back to the "My Day" display interface (that is, the transaction management interface).

[0060] exist Figure 1 The transaction management interface shown in (a) includes a card display area and a timeline display area. The card display area is used to display at least one reminder card, which can be understood as displaying the transactions that the user may need to pay attention to and manage in a more eye-catching and centralized manner in the card display area in the form of cards, which is convenient for user management. The card display area is mainly used to centrally display transactions that meet the user's management expectations, so the card display area can also be understood as a recommendation area for transaction management. The timeline display area displays all transaction cards in series according to the timeline, which is convenient for users to view and manage from a time dimension.

[0061] The card display area can be arranged vertically with the timeline display area (that is, vertically distributed), for example Figure 1 As shown in (a), the card display area is located at the top of the timeline display area. For larger screen electronic devices, such as large folding screen mobile phones, due to the larger screen, more content can be displayed. The card display area and the timeline display area can be arranged left and right (that is, distributed left and right), for example, the card display area can be located on the left and the timeline display area can be located on the right. Figure 1 As shown in (c).

[0062] In one embodiment, suppose the calendar application is started and displays Figure 1 In the interface shown in (b) (an example of the first interface), in response to the user clicking the "My Day" (an example of the first control) in the function bar (an example of the first operation), the Figure 1 The interface shown in (a) (an example of the second interface) responds to the user Figure 1 The second operation of the conflicting transaction reminder card (an example of the at least one reminder card mentioned above) in the card display area shown in (a) can display the third interface, in which the card of the transaction corresponding to the conflicting transaction reminder card is positioned and displayed in the timeline display area.

[0063] Figure 1 The electronic device shown can be any type of electronic device such as a mobile phone, a tablet computer, a touch screen laptop computer, etc., as long as it can remind and manage transactions.

[0064] The display content and management details of the card, as well as how the transaction is displayed and managed are described in detail below with reference to the attached figure. The following mainly introduces the example that the card display area and the timeline display area are distributed vertically, and the card display area is located at the top of the timeline display area.

[0065] Figure 2 A schematic diagram of a transaction management interface in an embodiment of the present application. Figure 2 It can be seen as Figure 1An example of a transaction management interface is shown in (a). Figure 2 As shown, the card display area shows a travel reminder card. The travel reminder card includes information such as travel reminder, estimated time and transaction content, and also includes a "navigation control" so that users can start the map application for navigation by clicking the navigation control. However, it should be understood that the card display area is an area that centrally displays some transactions recommended to users for management. The travel reminder card is just one of the various reminder cards. Other reminder cards that may appear will be introduced in detail below. For the sake of brevity, they will not be repeated here.

[0066] Figure 2 The timeline display area in the app includes two parts, the all-day affairs part and the time-divided affairs part. The timeline of the all-day affairs part can use dotted lines, and the timeline of the time-divided affairs reminder part can use solid lines. However, it should be understood that other lines can also be used to distinguish the all-day affairs part from the time-divided affairs part. On the timeline, the all-day affairs part shows the affairs with an execution time period of the whole day, or it can be understood as affairs that can be done at any time of the day, so as long as the user completes the affairs according to the actual situation, there is no need to limit the execution time of the affairs. On the timeline, the time-divided affairs reminder part shows the affairs with an execution time period of not the whole day, or it can be understood as the affairs that need to be executed at a specific time period or time point. Figure 2 The full-day transactions include car maintenance and bank repayments, while the time-divided transactions include getting up, outdoor running, and other transactions. The start time of each transaction corresponds to a time starting point on the timeline. Or it can be understood that the timeline includes at least one time node, each time node corresponds to a transaction, and the time node can be the time starting point of each transaction. Each transaction can include the transaction name and application source in the card in the timeline display area. The cards in the timeline display area can also include icons or interfaces that can jump to other applications (examples of jump controls). For example, the "8:14 high-speed rail trip" transaction can jump to the map application through the map application icon in the transaction card.

[0067] It should be understood that each card on the timeline corresponds to a transaction, which can be understood as these cards on the timeline displaying relevant information about the transaction, and each card displays relevant information about one transaction. The cards in the card display area are used to centrally display transactions that are more in line with the user's management expectations, and to supplement transactions that are not on the timeline. As mentioned above, the card display area can be seen as a recommendation area for transactions to be managed that best meet the user's expectations. The special day reminder card below is a reminder card for which there is no corresponding transaction card in the timeline display area.

[0068] Figure 2It is also shown that the time axis can use different colors to distinguish between the time that has passed and the time that has not yet arrived. Assume that the user enters the "My Day" interface on the target date. Figure 2 The time in the upper right corner of the interface shows that it is 7:15 now, that is, the user opened "My Day" in the calendar app at 7:15 on the target date and saw Figure 2 The color distribution of the time axis shown is that the time before 7:15 is the time that has passed, and the time axis is displayed in black (an example of the first color), and the time after 7:15 is the time that has not yet arrived, and the time axis is displayed in blue (an example of the second color). It should be understood that as long as the time that has passed and the time that has not yet arrived are distinguished by different colors, there is no limitation on which specific colors are used. However, the time that has passed is black or gray, and the time that has not arrived is colored, which makes the time axis part that has not arrived relatively eye-catching, and better meets the user's usage needs.

[0069] Figure 2 The example of entering "My Day" at 7:15 on the target date is used. However, it should be understood that the user can enter "My Day" at any time within the target date without limitation. The displayed content in the display interface will vary depending on the time of entering the interface. For example, if the user enters "My Day" at 12:00 on the target date, Figure 2 The "My Day" interface shown, Figure 2 The immediate departure travel reminder card in the middle card display area disappears, the timeline before 12:00 is black, and the timeline after 12:00 is blue. Other possible display differences are not listed one by one. In short, users will see different display content when entering "My Day" at different times.

[0070] It should be understood that in addition to using different colors to distinguish between the time that has passed and the time that has not arrived on the timeline, the thickness of the line can also be used for distinction. For example, the timeline line corresponding to the time that has passed can be thinner, and the timeline line corresponding to the time that has not arrived can be thicker. In addition, it is also possible to distinguish by setting other different axis states. For example, the thickness and color of the line can be combined, that is, two distinction schemes are superimposed. In other words, the embodiment of the present application does not impose any restrictions on the specific display form (such as position, size, shape) of the timeline in the timeline display area. Taking into account the user's usage habits, it can be set based on the principle that the timeline portion corresponding to the unreached time is more eye-catching.

[0071] Figure 3 It is a schematic diagram of a timeline display area of ​​an embodiment of the present application. Figure 3 It can be seen as Figure 2An example of the timeline display area in .

[0072] like Figure 3 As shown, the time axis of the all-day affairs part (all-day period) is taken as an example by a dotted line, and the time axis of the time-divided affairs part is taken as an example by a solid line. Figure 3 The "Car Maintenance" transaction is a full-day transaction, which comes from the local calendar and is a full-day schedule; the "XX Bank Repayment Day" transaction is also a full-day transaction, which comes from the SMS application and is obtained here through SMS recognition. It is a full-day to-do item. When the full-day to-do item has been completed, the control of whether the full-day to-do item is completed can be marked as completed (that is, Figure 3 ). Completed to-do items can also be marked with a strikethrough to make them more eye-catching and let users know that the to-do items no longer need to be processed.

[0073] It should be noted that in the embodiments of the present application, a transaction can be understood as something that a user needs to do. A transaction often needs to include what to do (transaction content), and may also include where to do it (location), how to do it (processing method), when to do it (execution time), etc. Transactions may include schedules and to-do items. Schedules can also be understood as travel arrangements, which often need to include what to do at what time and at what specific location. To-do items are for recording things that need to be done but have not been done yet. To-do items may not have strict time and location restrictions, and may only require that the things to be done be completed before a certain time node. Combined with Figure 3 "XX Bank Repayment Date" is a to-do item, which may only require some operations on the electronic device to complete, rather than having to go to a specific place at a specific time to complete. "Check-in at a certain hotel" is a schedule, which requires going to the specific place of the hotel to check in during the specific time period of 12:00-13:00, so the schedule card also includes a detailed address column to indicate the execution location of the user. "Registering at A Dental Clinic" is a to-do item. Although a specific execution time is agreed upon, that is, after 12:00, there is no agreed location. Although "A Dental Clinic" is a specific location, registration does not necessarily have to be done on-site. It can also be done on the electronic device side, online registration (remote registration). It can be seen that there is no very strict boundary between to-do items and schedules. All transactions are divided into schedules and to-do items according to certain characteristics to facilitate user management. In some cases, it can also be understood that when a user creates a transaction, it is created as a schedule, and the transaction type here is a schedule. When a user creates a transaction, it is created as a to-do item, and the transaction type here is a to-do item. Scheduling is more dependent on the attributes of time and place.

[0074] As mentioned above, you can divide transactions into all-day transactions and time-divided transactions according to whether the execution time period is all day; you can also divide transactions into schedules and to-do items according to the type of transaction created and / or the degree of dependence on time and location. In other words, you can divide transactions into different categories based on different classification criteria to facilitate classification display and management. The above two classifications can be superimposed. For example Figure 3 The "XX Bank Repayment Day" is a to-do item and a full-day affair, so it can be called a full-day agency item.

[0075] Still Figure 3 As shown, the time-divided task reminder part can start from the wake-up task at 6:00 a.m. The wake-up task at 6:00 a.m. comes from the alarm clock application (or clock application), and the task includes a system source identifier, that is, an identifier indicating that the task comes from the system application-clock.

[0076] The outdoor running event starting at 7:00 is a schedule from the Sports Health app. It is a sports plan synchronized from the Sports Health app, and the synchronized sports goal is also displayed in the event card. Figure 3 In the example shown, click on the source logo of running health and it will not jump. Because sports health needs to display less information, the content displayed in the card can basically meet the needs of users. It doesn't matter whether to establish a jump link to jump to the sports health application. If you set a jump link, you need to complete more synchronization design on the background process. If you don't set a jump link, you don't need to do subsequent synchronization design.

[0077] The "

[12306] Shanghai 11A-Nanjing South Station G7271" corresponding to 8:14-9:14 is a high-speed rail travel transaction, which is a schedule, including information such as the schedule time period (8:14-9:14), location (Shanghai Hongqiao Station) and starting and ending stations (Shanghai 11A and Nanjing South Station). The transaction originates from the SMS application and is obtained by identifying the SMS content. The card of the schedule also includes an icon of a map application (an example of a jump control), which can be regarded as a control in the card of the schedule. Clicking the icon of the map application can open the map application (an example of the first application) to start navigation. After clicking the icon of the map application, in one case, the map application can be started and the homepage of the map application can be displayed (an example of the fourth interface). In another case, the map application can be started to display the navigation page of the map application (another example of the fourth interface), and the address information can be loaded (filled in) in the navigation page. For example, "Shanghai Hongqiao Station" can be filled in the destination column. It should be understood that both of the above situations are achievable, and which one to use can be set on the electronic device as needed. If the map application allows data to be written directly across applications, the first or second situation can be selected; if the map application does not allow data to be written directly across applications, the first situation can be selected.

[0078] like Figure 3 As shown, an example of a caring message is given at noon: "Take a short break and be full of energy." In one example, a time threshold can be set for the caring message. When the time interval between the end time of the last schedule in the morning period and the start time of the first schedule in the period after noon is greater than or equal to the preset time threshold of the caring message, the caring message is displayed; otherwise, the caring message is not displayed. The time threshold can be, for example, two hours. Figure 3 As shown, the end time of the high-speed rail travel transaction from 8:14 to 9:14 is 9:14, and the start time of the hotel check-in transaction from 12:00 to 13:00 is 12:00. The time difference is greater than two hours. Caring words can be displayed between the card of the high-speed rail travel transaction from 8:14 to 9:14 and the card of the hotel check-in transaction from 12:00 to 13:00.

[0079] like Figure 3 As shown, there is a "check-in at a certain hotel" transaction from 12:00 to 13:00, which is a schedule from the SMS application. There is also a "register for a dental appointment at A" transaction from 12:00, which is a to-do item from the life application.

[0080] Figure 3 An example of a time conflict between two transactions starting at 12:00 is given in Figure 2, this conflict will generate a conflict reminder card, which will be displayed in the card display area to remind users to manage the conflicting affairs more prominently. The specific management method will be introduced below and will not be repeated here.

[0081] Figure 3 Also shown is the "Cooperation and Exchange with XX Company" event from 16:00 to 18:00 in the afternoon, which is a schedule from the third-party application "Office Application #1". The card of this event also includes a link icon (an example of a jump control) that can jump to the video conference interface in Office Application #1. The jump can be completed by clicking it.

[0082] Figure 3 Also shown is a reminder of new movie releases from 20:30 to 21:30 in the evening, which is a to-do item. By clicking on a link (an example of a jump control), the video application #2 (a third-party application, an example of the first application) can be opened to watch the new movie.

[0083] like Figure 3 As shown, the time axis before 16:00 is gray, and the time axis after 16:00 is colored (blue here), that is, Figure 3 The corresponding actual time is before 16:00. In this example, the time axis corresponding to the time that has passed is gray, and the time axis corresponding to the time that has not yet arrived is blue.

[0084] Assume that the color of the timeline is updated at the start time of a transaction, that is, every time the start time of a transaction is reached, the timeline before the time node of the transaction on the timeline is set to gray, and the timeline after the time node remains in color. Assume that the color of the timeline is updated at the end time of a transaction, that is, every time the end time of a transaction is reached, the timeline before the end time on the timeline is set to gray, and the timeline after the time node remains in color. Figure 3 , assuming that the update is done in the first way, that is, updating the color of the timeline at the start time of the transaction, then Figure 3 The corresponding real time (actual time) is after 12:00 and before 16:00; assuming that it is updated in the second way, that is, updating the color of the time axis at the end time of the transaction, then Figure 3 The corresponding real time (actual time) is after 13:00 and before 16:00. In addition, since some transactions do not have a clear end time, for conflicting transactions, the end time of the previous transaction may be after the start time of the next transaction, so it may be relatively difficult to update the color according to the end time. In this case, you can first update according to the end time of the transaction, and when the transaction has no end time, update it according to the start time of the transaction.

[0085] In one example, when a user enters the "My Day" interface, he or she can obtain the current time (actual time) and determine the transaction on the timeline whose start time is closest to the current time based on the current time, and which is a transaction that has not yet started. All timelines before the transaction are set to black or gray, and all timelines after the transaction are set to color.

[0086] from Figure 3 It can be seen that these transactions are connected in series with time as the axis. These transactions can be schedules or to-do items, and can also jump to other applications through the set jump controls.

[0087] Suppose the user clicks Figure 3 Clicking the small clock icon (an example of a folding control) on the timeline for the morning, noon, afternoon, and evening periods in the game will fold all the tasks for the corresponding period. For example, clicking the small clock icon on the "morning" timeline will fold the three tasks of getting up, outdoor running, and high-speed rail travel. If the user clicks the small clock icon on the "noon" timeline, the two tasks of checking in at a certain hotel and registering for an appointment at a dental clinic A will be folded. Other situations will not be listed one by one.

[0088] In addition to the manual folding method mentioned above, you can also use the automatic folding method. In the automatic folding method, based on the time when the user enters the transaction management interface, the time period that has ended before that time can be automatically folded. For example, if the user enters the transaction management interface at 14:00, all transactions in the "morning" period can be automatically folded. In addition, the division of the time period can be divided into multiple time periods as needed, such as Figure 3 There are four time periods: morning, noon, afternoon and evening. Figure 4 The example in the text gives three time periods: morning, afternoon and evening.

[0089] Figure 4 Schematic diagram of the method for setting a folded or unfolded calendar in an embodiment of the present application. Assume that a whole day is divided into three time periods: morning, afternoon and evening. Figure 4 The following figure shows the result after the three time periods and the time period of the all-day transaction are manually collapsed. The cards of two transactions are collapsed and hidden in the all-day transaction, the cards of three transactions are collapsed and hidden in the morning, the cards of two transactions are collapsed and hidden in the afternoon, and the card of one transaction is collapsed and hidden in the evening. If the user clicks the expansion control of a time period, the cards of all transactions in the time period can be expanded, that is, the collapsed and hidden cards are displayed again on the interface.

[0090] Assuming that it is an automatic folding situation, the time period that has ended can be automatically folded. However, it should be understood that in this example, because the corresponding time period of the all-day affairs part is the whole day, it will not be automatically folded unless all the time of the whole day is over. In other words, the user will not see the all-day affairs part automatically folded when entering the "My Day" interface at any time on the target date.

[0091] Figure 5 Schematic diagram of automatic positioning display according to the current time in an embodiment of the present application. Figure 5 As shown, assuming that the current time is 20:20 on the target date, after the user enters the "My Day" function, the electronic device will fully display the cards of the transactions corresponding to the current time in the timeline display area, combined with Figure 5 That is, the card of the new film online transaction between 20:30 and 21:30 is automatically located and displayed completely. The transaction corresponding to the current time can be the transaction closest to the current time but whose start time has not yet arrived. Figure 2 and Figure 5 , assuming that the user enters the "My Day" interface at 7:15 (an example of the first time), the current time on the positioned timeline is 7:15, and the corresponding transaction is the high-speed rail travel transaction from 8:14 to 9:14 (an example of the fifth transaction). The positioned display is to fully display the card of the high-speed rail travel transaction from 8:14 to 9:14. If the card of the transaction is already in the display interface, no action is performed. If the card of the transaction is partially or completely not in the display interface, the positioned display is to fully display the card of the transaction that was originally not in the display interface in the display interface. Suppose that the user enters the "My Day" interface at 20:20 (an example of the second time), and assuming that the initial interface after entering is as follows Figure 2 As shown in FIG. 1 , the time axis cannot fully display the events after 20:20, so the card of the event “20:30-21:30 new film online” (an example of the sixth event) which is the most recent event after 20:20 is fully displayed on the display interface through positioning display, such as Figure 5 shown.

[0092] In addition to the positioning display, the display content in the display interface will also change due to the change of the entry time. The automatic management strategy for cards in the past time period will also change the display content. If the user performs some card management operations before the current time, the display content will also change. Figure 5 As shown, in addition to the cards in the timeline display area and Figure 2 In addition to the changes, the color distribution on the time axis is compared to Figure 2 There have also been changes, and Figure 5The cards displayed in the card display area are also compared to Figure 2 Something has changed.

[0093] For elapsed time periods, Figure 5 For example, the timeline is set to gray, but the cards in the timeline display area of ​​the past time period on the timeline are not set to gray. When the target date is over, all the cards of all transactions can be set to gray.

[0094] Figure 6 Schematic diagram of the design of the schedule and to-do list of the embodiment of the present application. Figure 6 As shown in (a), the schedule includes a title (in order to prevent the title from being too long and requiring too much display area, it can be set to display only one or two lines at most), an execution time period (if it is an all-day transaction, the execution time period does not need to be displayed, and only time-divided transactions need to display the execution time period), a location, and an application source (which application it comes from).

[0095] like Figure 6 As shown in (b), the schedule may also include an operation button (which may be a jump link or a start link for jumping to a related page of a related application).

[0096] like Figure 6 As shown in (c), the schedule may also include a system application source icon to more prominently indicate which system application the schedule comes from.

[0097] like Figure 6 As shown in (d), the to-do list includes the title (to prevent the title from being too long and requiring too much display area, it can be set to display only one or two lines at most), the execution time period (if it is a full-day transaction, the execution time period does not need to be displayed, only the time-divided transactions need to display the execution time period) and the application source (which application it comes from). Compared with the schedule, the to-do list does not have a location item, because to-do items such as car washing, shopping, and repayment often do not require going to a specific location, so there is no need to display the location. For example, the to-do items such as phone recharge and life payment do not involve specific locations at all.

[0098] like Figure 6 As shown in (e), the to-do list may also include a mark indicating whether it is completed, a check mark indicating completed items, and a blank circle indicating uncompleted items. It should be understood that other methods may also be used to mark whether the items are completed.

[0099] It should also be understood that whether a transaction is displayed as a schedule or a to-do item in "My Day" can be determined based on whether the transaction type created by the user when creating the transaction is a schedule or a to-do item, or based on whether the location can be identified during the intelligent recognition process. For example, suppose the user creates a schedule when creating a transaction. Even if the schedule does not have a location note, it will still be displayed as a schedule in "My Day". Suppose the user creates a to-do item when creating a transaction. Even if the to-do item has a location note, it will still be displayed as a to-do item in "My Day". Suppose the source of the transaction is obtained through intelligent recognition from other applications, such as Figure 2-Figure 5 SMS recognition in the system can determine the transaction category based on whether it meets the content requirements of the schedule or to-do list. Assuming that the title, execution time period, location and application source can be identified based on SMS recognition (the application source is the SMS application in this example), it can be created as a schedule; assuming that the title, execution time period and application source can be identified based on SMS recognition but the location cannot be identified, it can be created as a to-do list.

[0100] For all-day transactions and time-divided transactions, it is similar to the above. The transaction type can be determined based on whether the transaction type created by the user is an all-day transaction or a time-divided transaction when the user creates the transaction, or whether the specific time period can be identified during the intelligent recognition process. For example, assuming that when the user creates a transaction, it is an all-day transaction, it will be displayed as an all-day transaction in "My Day". Suppose when the user creates a transaction, it is a time-divided transaction, it will be displayed as a time-divided transaction in "My Day". Suppose the source of the transaction is obtained through intelligent recognition from other applications, for example Figure 2-Figure 5 The SMS recognition in the process can determine the transaction category based on whether there is a specific time period. If the execution time period can be identified based on SMS recognition, it is a time-divided transaction, otherwise it is a full-day transaction.

[0101] Figure 7 It is a schematic diagram of an execution process of managing a schedule according to an embodiment of the present application. Figure 7 by Figure 3 Taking the management of the check-in affairs of a certain hotel from 12:00 to 13:00 as an example, the management of affairs of other schedule types is similar and will not be repeated. Figure 7 As shown in (a), the user can slide on the card of the transaction on the timeline. Here, swiping left is taken as an example. In response to the sliding operation, the electronic device can display Figure 7 The management controls shown in (b) in FIG. 1 include the important transaction marking control, the ignore reminder control, and the delete transaction control. Assume that the user Figure 7In (b), the important event mark control is clicked, and in response to the click operation, the electronic device displays Figure 7 As shown in (c), the color of the small flag in the control changes to indicate that the control is selected (that is, important matters and non-important matters can be distinguished by such a small colored flag as a mark). After that, when the user does not perform other interactive operations, the electronic device will display Figure 7 As shown in (d), an important transaction mark is added to the transaction card. Here, the important transaction mark is a small red flag, which is used to indicate that the transaction is an important transaction. Figure 7 (a) and Figure 7 As can be seen in (d), ordinary transactions (non-important transactions) have no small flag, while important transactions include a small colored flag (which can be seen as an example of an important transaction mark).

[0102] Figure 7 (a)-(d) in the figure give an example of the interactive process of setting the status of a schedule-type transaction to an important transaction. Important transactions can be distinguished from non-important transactions by marking them.

[0103] Assume that the user is Figure 7 In (b), the control clicked is the ignore reminder control. In response to the user's click operation on the ignore reminder control, the electronic device displays Figure 7 In the case shown in (e), the transaction is changed to a simplified display mode, that is, detailed information such as time and location are no longer displayed, only the title is displayed, and the title is grayed out. However, it should be understood that in practice, as long as it is convenient for users to distinguish whether the transaction has been ignored or not, other methods can be used to display the ignored reminder transactions.

[0104] Figure 7 (a), (b), and (e) in the figure give examples of the interactive process of setting the status of a schedule-type transaction to an ignored reminder transaction. The ignored transactions can be distinguished from the non-ignored transactions by deleting part of the information of the ignored transactions.

[0105] Assume that the user is Figure 7 In (b), the control clicked is the delete transaction control. In response to the user's click operation on the ignore reminder control, the electronic device displays Figure 7 As shown in (f) in the figure, the transaction can be deleted. Figure 7 In the example shown in (f), the card of the transaction and the time node on the timeline are deleted.

[0106] Figure 7 (a), (b), and (f) in the figure give examples of the interactive process of deleting a schedule-type transaction.

[0107] It should be understood that Figure 7 (a)-(f) in the figure only capture a part of the interface for illustration to facilitate understanding. In practice, each of them corresponds to a complete display interface. Figure 7 (a)-(f) in the figure do not show the complete display interface; there may be other transactions on the timeline that is not shown. Figure 8 and Figure 7 resemblance. Figure 7 The main example is the management of schedule. Figure 8 This article gives an example of managing to-do items.

[0108] Figure 8 It is a schematic diagram of an execution process of managing to-do items according to an embodiment of the present application. Figure 8 by Figure 3 Taking the management of the "XX Bank Repayment Day" transaction of the full-day transaction in as an example, the management of other types of to-do items is similar and will not be repeated here. Figure 8 As shown in (a), a sliding operation is performed on the card of the transaction on the timeline. Here, a left slide is taken as an example. In response to the sliding operation, the electronic device displays Figure 8 The management controls shown in (b) in the figure include the important transaction marking control, the postponement reminder control, and the transaction deletion control. Figure 8 In (b), the important event mark control is clicked, and in response to the click operation, the electronic device displays Figure 8 As shown in (c), the color of the small flag in the control changes to indicate that the control is selected. After that, if the user does not perform other interactive operations, the electronic device displays Figure 8 As shown in (d), an important transaction mark is added to the transaction card, which is a small red flag. Figure 8 (a) and Figure 8 As can be seen in (d), ordinary affairs have no small flag, while important affairs include a small colored flag.

[0109] Figure 8 (a)-(d) in the figure give an example of the interactive process of setting the status of a to-do type transaction to an important transaction. Important transactions can be distinguished from non-important transactions by marking them.

[0110] Assume that the user is Figure 8 In (b), the control clicked is the delete transaction control. In response to the user's click operation on the delete transaction control, the electronic device displays Figure 8 As shown in (e), the transaction can be deleted. Figure 8 In the example shown in (e), the card of the transaction and the time node on the timeline are deleted.

[0111] Figure 8 (a), (b), and (e) in FIG. 5 give examples of the interactive process of deleting a to-do type transaction.

[0112] Fig. 9 It is a schematic diagram of an execution process of postponing reminders for to-do items in an embodiment of the present application. Figure 8 by Figure 3 Taking the extension reminder management of the task "A Oral Registration" starting at 12:00 as an example, the extension reminder management of other types of to-do items is similar and will not be repeated here. Fig. 9 As shown in (a), a sliding operation is performed on the card of the transaction on the timeline. Here, a left slide is taken as an example. In response to the sliding operation, the electronic device displays Fig. 9 The management controls shown in (b) in the figure include the important transaction marking control, the postponement reminder control, and the transaction deletion control. Fig. 9 In (b), the delay reminder control is clicked, and in response to the click operation, the electronic device displays Fig. 9 The pop-up window shown in (c) is used to instruct the user to select the target time for the extension. Fig. 9 In the interface shown in (c), after clicking on the option to postpone to one hour, the electronic device displays Fig. 9 As shown in (d), the position of the transaction card on the timeline is updated to the delayed time. Fig. 9 (a) and Fig. 9 As can be seen from (d) in the figure, the corresponding position of the transaction on the time axis has changed. It should also be understood that if the user Fig. 9 If you select a different delayed target time in the pop-up window shown in (c), the transaction will be updated to the delayed time node. If the user selects one day later, the transaction will not be visible on the timeline of the target date. Fig. 9 In the interface shown in (c), click "Custom Time" to manually set the target time for extension.

[0113] Fig. 9 An example of the interactive process of postponing a to-do item-type transaction is given. The position of the transaction on the timeline can be updated by selecting the target time after postponement.

[0114] from Figure 7-Figure 9It can be seen that different management controls can be set according to the characteristics of two different types of affairs, schedules and to-do items. Since schedules are more dependent on time, there is no postponement reminder control for schedules, but an ignore reminder control is set. For example, assuming that a schedule is a high-speed rail trip at a certain time, the probability of users having a postponement reminder is low. Because even if the user clicks the postponement reminder control for a postponement reminder, due to the particularity of high-speed rail travel, the postponement will inevitably cause the time, location and number of high-speed rail travel to change, and the user will still buy tickets again, so a new schedule may be generated based on SMS recognition after the ticket purchase. For another example, assuming that a to-do item is to buy an item, then compared to ignoring reminders, postponement reminders may better meet user management needs. Because ignoring reminders will result in no more reminders, and postponement reminders can continue to remind users to buy the item later. For another example, assuming that a schedule for attending a meeting, the user arrives at the meeting place earlier than the meeting start time, then the user may have the need to turn off the reminder of this schedule, and at this time the user can execute Figure 7 The interaction processes shown in (a), (b), and (e) ignore reminders.

[0115] In short, different management controls can be set for different types of transactions to facilitate user management.

[0116] The above embodiments mainly describe the possible structure of the transaction management interface and the functions and contents of each part, and introduce in detail the design and management methods for the transaction cards in the timeline display area. The following embodiments will describe the design and management methods for the card display area in conjunction with the accompanying drawings.

[0117] Fig.10 Schematic diagram of a reminder card in the embodiment of the present application. Fig.10 As shown in (a), a reminder card can include a title area (or title or summary description), a content area, a theme area, and a button area. The theme area and the button area are both optional, and a button can also be understood as a control. Text represents the title content, and action represents the button (control) name.

[0118] like Fig.10 As shown in (b), in order to ensure the complete display of the content, a blank border area can be set in the title area. In order to enrich the display content, a small circle icon display area can also be set. Here, the icon display area of ​​the small circle is 16dp (pixels) as an example. In practice, any appropriate value can be used as needed, and other shapes other than circles can be selected, such as rounded rectangles, etc. There is no limitation. It should be understood that Fig.10As shown in (b), the title area, content area and button area all have 12dp of blank space on the left and right. The size of the small circle icon in the title area is 16dp, 8dp of blank space is reserved between the small circle icon boundary and the title text, 8dp of blank space is reserved between the upper and lower adjacent areas, and 12dp of blank space is reserved at the bottom of the button area. These are only for illustrative purposes and there is no numerical limitation.

[0119] Fig.11 It is a schematic diagram of a departure reminder card according to an embodiment of the present application. Fig.11 The card shown in (a) can be used Fig.10 The layout design shown in the figure is obtained. Fig.10 The title of the departure reminder card shown is the estimated arrival time for immediate departure at the current moment "Depart immediately, expected to arrive at 7:45", the content is the road traffic conditions and estimated time "The road is clear, and it will arrive in about 30 minutes", and the theme is the travel purpose "High-speed rail travel - Shanghai Hongqiao Station". The "Navigation" control is used for one-click navigation, that is, by clicking the navigation control, you can start the map application to start navigation.

[0120] The appearance of the travel reminder card can be triggered immediately to remind the user to leave immediately, that is, after the user opens the event management interface of the target date, the travel reminder card can be displayed. When the schedule corresponding to the travel reminder card starts, the travel reminder card disappears. Figure 2 and Fig.11 As an example, assume that the user enters the "My Day" interface at 7:15 a.m., and the interface displays the following information: Figure 2 As shown, the card display area includes Fig.11 Assume that the user enters the "My Day" interface after 8:14, that is, the actual time is later than the start time of the high-speed rail travel event of 8:14-9:14. At this time, the travel reminder card is no longer displayed, that is, Figure 2 The travel reminder card in will be deleted. Figure 5 For example, when a user enters the "My Day" management interface, he will not see the travel reminder card corresponding to the high-speed rail travel event from 8:14 to 9:14 in the card display area.

[0121] It should be understood that there can be only one or more travel reminder cards, and each travel-required event corresponds to a travel reminder card. For example, if there are multiple travel schedules on a certain day, at different locations, multiple travel reminder cards can be generated.

[0122] like Fig.11As shown in (a), the user can start the map application for navigation by clicking on the navigation control. When starting the application for navigation, in one case, the map application corresponding to the navigation control can be started and the homepage of the map application can be displayed. In another case, the map application can be started to display the navigation page of the map application, and the address information can be loaded (filled in) in the navigation page. For example, "Shanghai Hongqiao Station" can be filled in the destination column. It should be understood that both of the above situations can be implemented, and the specific one can be set on the electronic device as needed. If the map application allows data to be written directly across applications, you can choose the first or second one; if the map application does not allow data to be written directly across applications, choose the first one.

[0123] exist Fig.11 In (a), in one case, the user can click on the main area of ​​the travel reminder card (which can be understood as any area of ​​the card except the navigation control) to enter the details of the schedule of the travel reminder card in the month view interface, such as Fig.11 In another case, the user can click on the trunk area of ​​the travel reminder card to locate and fully display the card of the transaction corresponding to the travel reminder card in the timeline display area. Figure 2 As shown, in this case, the user may click Figure 2 The travel reminder card shown in the middle card display area (that is, Fig.11 The card shown in (a) in Figure 2 The timeline display area shown locates and fully displays the card for the high-speed rail travel schedule from 8:14 to 9:14.

[0124] It should also be understood that in the embodiments of the present application, the schedule often requires going to a specific place, while most of the to-do items do not require going to a specific place, so the travel reminder card is mainly aimed at the travel needs of the schedule. The to-do items may not require travel at all, such as bank repayments, car washing, shopping, watching new movies, paying for daily life, recharging phone bills, etc., which are all to-do items that do not require going to a specific place.

[0125] Fig.12 It is a schematic diagram of a conflict reminder card according to an embodiment of the present application. Fig.12 The cards shown can be Fig.10 The layout design shown in the figure is obtained. Fig.12The title of the conflict reminder card shown is "Conflict Reminder", the content is "There are 2 time period schedule conflicts" (that is, there is a time conflict between 2 time period schedules), the subject is "Please arrange the schedule time reasonably" (that is, instructing the user to check and modify the schedule time), and the viewing control "View Now" is used to locate and fully display the cards of the two conflicting schedules in the timeline display area.

[0126] Time conflict can be understood as the overlap between the execution time periods of transactions. For example, there is a conflict between a transaction from 8:00-9:00 and a transaction from 8:00-10:00. Another example is a conflict between a transaction from 8:00-9:00 and a transaction from 8:30-10:00. Other situations are not listed one by one. However, it should be understood that for all-day transactions, there is no restriction on the execution time period, so all-day transactions will not appear in the conflict reminder card.

[0127] The conflict reminder card may appear immediately. After the user enters the transaction management interface, the conflict reminder cards corresponding to all conflicting transactions after the current time are displayed. The conflict reminder card may also appear when a conflict occurs. That is, if the user manages the transaction card in the management interface, a conflict occurs between the managed transaction and other transactions. For example, if the user enters the transaction management interface at 11:00, when the user postpones the reminder of a transaction starting at 13:00 to 15:00, if 15:00 is already in the execution time period of other transactions, a time conflict will occur. At this time, the conflict reminder card will be updated in the card display area. If there is no conflict reminder card corresponding to the transaction including these two transactions in the card display area, a new conflict reminder card can be added or the number of conflicting transactions in the conflict reminder card can be modified on the original conflict reminder card. If there is a conflict reminder card corresponding to the transaction including at least one of the two transactions in the card display area, the conflict information can be updated in the conflict reminder card.

[0128] The conflict reminder card may disappear because the conflict is resolved, or because the execution time period of all transactions corresponding to the conflict reminder card has ended, or because only one transaction among all transactions corresponding to the conflict reminder card has not ended. The following is a breakdown of the explanation.

[0129] In one example, the conflict reminder card can disappear because the conflict is resolved. The following example illustrates this. Fig.12 Click the "View Now" control in the conflict reminder card to locate the start position of the conflicting schedule in the timeline display area. Figure 2 and Fig.12For example, assuming Figure 2 The card display area contains Fig.12 The conflict reminder card shown above, when the user Figure 2 The card display area shown is clicked Fig.12 The "View Now" control in the conflict reminder card shown above can be used to Figure 2 The timeline display area shown locates and fully displays the card with the earliest start time indicated by the conflict reminder card, combined with Figure 2 It locates and fully displays "Hotel check-in from 12:00 to 13:00", from Figure 2 It can be seen that the check-in transaction of Hotel X from 12:00 to 13:00 and the registration transaction of Dental Clinic A at 12:00 are in conflict. If the user wants to resolve the conflict, he can refer to Figure 7-Figure 9 The method shown in the figure resolves the conflict by managing one or both of the two transactions. Figure 7 The method shown in the figure is to schedule "check-in at a certain hotel from 12:00 to 13:00", and then swipe left and click "Ignore reminder control" or "Important task mark control" or "Delete task control" to resolve the conflict. Figure 8 The method shown is to remove the conflict by swiping left on the to-do item "12:00 Oral Clinic A Registration" and clicking "Important Item Marking Control" or "Delete Item Control". Fig. 9 In the method shown, for the to-do item "12:00 Oral Clinic A registration", swipe left, click "Postponement reminder control" and select the appropriate postponed target time to resolve the conflict. For another example, the two tasks can be managed the same or differently to resolve the conflict, such as deleting both, or deleting one and marking the other as important, or ignoring the reminder of one and marking the other as important, etc., which will not be listed one by one.

[0130] It should be understood that when one of the two conflicting transactions is marked as important and the other is not marked as important, the conflict is resolved, which is equivalent to giving priority to the important transaction, and then dealing with the unmarked important transaction when there is remaining time. At this time, there is no need to delete the unmarked important transaction. In other words, resolving the conflict does not necessarily require deleting the conflicting transaction. As long as it is a combination of reasonable management methods, the conflict can be resolved. After the conflicts between all transactions corresponding to the conflict reminder card are resolved, the conflict reminder card in the card display area disappears. However, it should also be noted that a new conflict reminder card may be generated after the conflict is resolved. This situation mainly occurs in the postponement reminder of to-do items. New conflicts may arise after the postponement. At this time, a new conflict reminder card will appear in the card display area, and users can continue to manage transactions based on the prompts of the new conflict reminder card.

[0131] In another example, the conflict reminder card can disappear when the execution time periods of all transactions corresponding to the conflict reminder card have ended. For example, suppose there are three transactions with execution time periods of 8:00-9:00, 8:30-9:30 and 9:00-10:00, and there is a conflict. In this example, when the time is after 10:00, the conflict reminder cards corresponding to these three transactions can be deleted in the card display area. From the user's perspective, if the user enters the transaction management interface after 10:00, the conflict reminder cards of the above three transactions will not be displayed in the card display area.

[0132] In another example, the conflict reminder card can disappear when only one of the transactions corresponding to the conflict reminder card has not yet ended. For example, suppose there are three transactions with execution time periods of 8:00-9:00, 8:30-9:30 and 9:00-10:00, and there is a conflict. In this example, when the time is after 9:30, the conflict reminder cards corresponding to these three transactions can be deleted in the card display area. From the user's perspective, if the user enters the transaction management interface after 9:30, the conflict reminder cards of the above three transactions will not be displayed in the card display area. In this example, it can be understood that at the current time, only one transaction is still in the execution time period. Although other transactions conflict with it, the execution time period has ended. As far as the current time and later are concerned, there are no transactions that need to be processed at the same time.

[0133] It should also be understood that there can be only one conflict reminder card, which centrally counts and displays all conflicting transactions, and disappears only when all conflicts are resolved (or disappears after the time periods of all conflicting transactions are over). There can also be multiple conflict reminder cards, which is equivalent to displaying conflicting transactions in groups. For example, there may be three conflict reminder cards, which respectively indicate that there are three conflicting transactions between 8:00-10:00, two conflicting transactions between 12:00-13:00, and five conflicting transactions between 20:00-23:00. It should be understood that this example is for the convenience of understanding the solution, and there is no numerical limitation.

[0134] Fig.13 It is a schematic diagram of tomorrow's schedule reminder card and time anomaly reminder card in an embodiment of the present application. Fig.13 (a) in the figure shows a reminder card for tomorrow's schedule. Fig.13 (b) shows a time anomaly reminder card. Fig.13 The cards in the Fig.10 The layout design shown in the figure is obtained. Fig.13In the tomorrow schedule reminder card shown in (a), the title is the statistics of tomorrow's affairs "Tomorrow there are 12 schedules and 2 to-do items", and the content is the details of the first schedule, including the schedule content "cooperation and communication with a certain company", the time period "7:30-12:00" and the application source "office application C". Fig.13 In the time anomaly reminder card shown in (b), the title content is the statistics of tomorrow's affairs "Tomorrow there are 12 schedules and 2 to-do items", and the content is the prompt "The first schedule starts at 7:30, please arrange in advance", which is used to remind the user to pay attention to the time of the earliest schedule. The subject is the title of the first schedule "Cooperation and communication with a certain company". The "Set strong reminder" control is used to set this earliest schedule as a normal tomorrow's schedule reminder card, that is, it is displayed as Fig.13 Tomorrow's schedule reminder card shown in (a).

[0135] The time abnormality reminder card is mainly used to remind the schedule that is earlier than the preset time point, so that the user can make arrangements in advance. The preset time point can be, for example, 8 o'clock in the morning, or 9 o'clock in the morning, or working hours on weekdays, so the time abnormality reminder card can also be called the tomorrow morning schedule reminder card.

[0136] Tomorrow's schedule reminder card is mainly used to display statistical data of the affairs of the day after the target date. If the user wants to preview tomorrow's full-day affairs in advance, he can click on tomorrow's schedule reminder card to enter the affairs management interface of the day after the target date, that is, "My Day" of the next day.

[0137] In terms of sorting, tomorrow's schedule reminder card and time anomaly reminder card are not very urgent and need to be processed immediately compared to the target date, so they can be sorted later, for example, after the travel reminder card and conflict reminder card.

[0138] Tomorrow's schedule reminder card and time anomaly reminder card are mainly used to preview the approximate situation of the next day, so there is no need to set many of them, which will waste the display resources of the card display area. You can set only one of each.

[0139] The time anomaly reminder card can be converted into an ordinary tomorrow schedule reminder card after setting a strong reminder. The tomorrow schedule reminder card can disappear after passing zero, that is, after tomorrow arrives. It is equivalent to deleting this tomorrow schedule reminder and generating a new tomorrow schedule reminder after tomorrow becomes today. It can be understood as replacing the tomorrow schedule reminder card that has become today with the tomorrow schedule reminder card of the next tomorrow. Combined with the example, assuming that the target date is January 3, this day in "My Day" refers to January 3, then the tomorrow reminder card in the target date shows the statistics of all transactions for the whole day of January 4. When the time comes to January 4, the target date is January 4, and this day in "My Day" refers to January 4. The tomorrow reminder card in the target date shows the statistics of all transactions for the whole day of January 5.

[0140] Fig.14 It is a schematic diagram of a basic card of an embodiment of the present application. Fig.14 The cards in the Fig.10 The layout design shown in the figure is obtained. Fig.14 In the basic card shown in (a), the title content is the location city and weather information, the content is a message to encourage users, and the subject is the date information of the target date. Fig.14 In the basic card shown in (b), the title content is the location city and weather information, the content is a message to encourage the user, and the theme is the date information of the target date and the countdown to the number of days until the special day.

[0141] Fig.13 The date information in the calendar application comes from the weather application, and the weather information comes from the weather application. Different messages can be displayed at different time periods throughout the day, for example, different time periods can include morning, noon and evening.

[0142] Basic cards are permanent cards in the card display area. It can be understood that the card display area will always display a basic card. Basic cards will not appear or disappear with user operations. When a user enters "My Day" at any time, he will see at least one card in the card display area, including a basic card.

[0143] As mentioned above, other types of cards have their own opportunities for appearance and disappearance. For example, a travel reminder card will only be generated when there is a transaction with a travel reminder demand. When the travel reminder demand disappears (the transaction corresponding to the travel reminder card is deleted or ignored, or the execution time period of the transaction corresponding to the travel reminder card has begun, the travel reminder demand disappears), the travel reminder card disappears. For another example, a conflict reminder card can be displayed immediately when a conflict exists, and disappear when the conflict is resolved or the time period corresponding to the card ends. For another example, the tomorrow schedule reminder card will exist all day today, disappear when tomorrow arrives (at midnight, tomorrow becomes today), and then a new tomorrow schedule reminder card will be generated. For another example, the special day reminder card below will appear within the preset date before the special day arrives, disappear when the special day arrives, or disappear when the user manually deletes the card.

[0144] In one example, the base card cannot perform any actions and the message is pre-set in the electronic device and cannot be manually changed.

[0145] In another example, when the base card is clicked, a weather application can be launched on the electronic device so that the user can view detailed weather information.

[0146] Fig.15 It is a schematic diagram of a special day reminder card according to an embodiment of the present application. Fig.15 (a) and (b) in the figure show important day reminder cards. Fig.15 The one shown in (c) is a birthday reminder card. Fig.15 The cards in the Fig.10 The layout design shown in the figure is obtained. Fig.15 In the important day reminder card shown in (a), the title content is the category of special days "Important Day", the content is "Final Exam", that is, what kind of important day is the important day, and the theme is the date of the important day "September 10, the 15th day of the eighth month in the lunar calendar". Fig.14 In the important day reminder card shown in (b), the title content is the category of special days "Important Day", the content is "F City Coffee Festival", the theme is the date of the important day "September 10th, the 15th day of the eighth month of the lunar calendar" and the countdown days to the current day are "3 days left". Fig.14 In the birthday reminder card shown in (b), the title content is the category of special days "Birthday", the content is "Qiuxiang's Birthday", the theme is the birthday date "September 10th, the 15th day of the eighth month in the lunar calendar" and the countdown days to the current day are "3 days left".

[0147] Special days may include at least one of birthdays, holidays, important days and anniversaries. Birthdays can be captured by keywords and can be synchronized here when the user creates a birthday reminder transaction (which can be a schedule or a to-do item) in the calendar application. Holidays can also be synchronized through the calendar application. It should also be understood that some holidays may not necessarily require preparation in advance, and there will be reminders in other ways, such as ordinary calendar pages, or date display cards on the desktop of electronic devices, etc., so in some cases, special days may not include holidays. Important days can be identified by intelligent recognition. For example, a series of key words can be captured, especially for matters that need to be arranged and planned in advance, which can be set as important day reminders. For example, the final exams and coffee festivals here. Anniversaries can be captured by keywords and can be synchronized here when the user creates an anniversary reminder in the calendar application.

[0148] Fig.16 FIG. 1 is a schematic diagram of an interactive process of switching a target date in an embodiment of the present application. Assume that the user Fig.16 In the interface shown in (a), in response to the upward sliding operation, the electronic device displays Fig.16 In the reminder pop-up window shown in (b), the user is instructed to switch dates by swiping up. For example, the prompt #1 here is "Swipe up to view the next day's affairs". Assuming that the user completes the swiping operation, that is, after lifting the hand to end the swiping, the electronic device displays in response to the swiping operation Fig.16 The interface shown in (c) above. That is, the corresponding date of "My Day" is changed from today to the next day. Fig.16 (a) and Fig.16 The content of “My Day” shown in (c) is different, and different filling colors are used for illustration, but it should be understood that there may not be any filling colors in practice. Fig.16 The interface shown in (a) includes a card display area 1 and a timeline display area 1, and the card display area includes card 1 and card 2. Fig.16 The interface shown in (c) includes a card display area 2 and a timeline display area 2, and the card display area includes a card 3.

[0149] Fig.17 FIG. 1 is a schematic diagram of another interactive process of switching the target date in an embodiment of the present application. Assume that the user Fig.17 In the interface shown in (a), the electronic device displays the following display in response to the sliding operation: Fig.17 In the reminder pop-up window shown in (b), the user is instructed to switch dates by sliding down. For example, the prompt #2 here is "Swipe down to view the previous day's affairs". Assuming that the user completes the sliding operation, that is, after lifting the hand to end the sliding, the electronic device responds to the sliding operation and displays Fig.17 The interface shown in (c) above. That is, the corresponding date of "My Day" is changed from today to the previous day. Fig.17 (a) and Fig.17 The content of “My Day” shown in (c) is different, and different filling colors are used for illustration, but it should be understood that there may not be any filling colors in practice. Fig.17 The interface shown in (a) includes a card display area 1 and a timeline display area 1, and the card display area includes card 1 and card 2. Fig.17 The interface shown in (c) includes a card display area 3 and a timeline display area 3, and the card display area includes cards 4.

[0150] It can be seen Fig.16 and Fig.17 The example of switching the target date by sliding operation is given. This interaction method is relatively simple, but it can only switch one day at a time.

[0151] Fig.18 FIG. 1 is a schematic diagram of another interactive process of switching the target date in an embodiment of the present application. Assume that the user Fig.18 In the interface shown in (a), the target date management control is clicked. Here, the management control is located in the upper right corner as an example. In response to the click operation, the electronic device displays Fig.18 The date selection pop-up window shown in (b) in the date selection pop-up window instructs the user to select a switching date. Fig.18 In the interface (b), "September 3" is selected, and the electronic device displays a Fig.18 The interface shown in (c) above. That is, the corresponding date of "My Day" is changed from today to September 3. In order to distinguish Fig.18 (a) and Fig.18 The content of “My Day” shown in (c) is different, and different filling colors are used for illustration, but it should be understood that there may not be any filling colors in practice. Fig.18 The interface shown in (a) includes a card display area 1 and a timeline display area 1, and the card display area includes card 1 and card 2. Fig.18 The interface shown in (c) includes a card display area 3 and a timeline display area 3, and the card display area includes cards 4.

[0152] Fig.18 The method of switching the target date shown can make the user more flexible in selecting the date they want to switch. However, if the user only wants to view the previous day or the next day, Fig.16 and Fig.17 The method shown is more convenient and quick to operate. In other words, Fig.16 and Fig.17 The method shown is more suitable when the switching date is close to the target date. Fig.18 The method shown is more suitable when the switching date is far from the target date. However, it should be understood that both switching methods can achieve the purpose of switching the target date.

[0153] It should also be understood that the above-mentioned switching target date refers to the target date corresponding to the switching of "My Day", which can be understood as a one-day transaction in which the content in the "My Day" interface is replaced with the date after the switch.

[0154] Fig.19 This is a schematic flow chart of a transaction management method according to an embodiment of the present application. Fig.19 The steps shown are introduced below. Fig.19 Can be used Figure 1-Figure 18 or Fig. 20 Any electronic device in the embodiment of the present invention is used for execution.

[0155] S1901. Display a first interface of a calendar application, where the first interface includes a first control.

[0156] Combination Figure 1 and Figure 2 In one implementation, the first interface may be a month view interface or an "Agent" interface of a calendar application. The first control may be "My Day" in a function bar.

[0157] S1902: In response to a first operation of the user on the first control, display a second interface of the calendar application.

[0158] The second interface includes a card display area and a timeline display area; wherein the card display area includes a conflicting transaction reminder card; the timeline display area includes a timeline and a card of the first transaction, and the first transaction corresponds to the first time node on the timeline.

[0159] Combination Figure 1 and Figure 2 , the second interface can be Figure 1 Middle (a), Figure 1 (c) or Figure 2 The display interface of the "My Day" function shown in the figure. The card display area may include at least one reminder card, and the at least one reminder card may include a conflicting transaction reminder card. The timeline display area may include timeline and transaction cards. The timeline display area mainly connects transactions in series through the timeline, so each transaction will correspond to a time node on the timeline. The first transaction may be, for example, Figure 2 Any transaction on the timeline, for example, the 6:00 wake-up alarm can be regarded as an example of the first transaction. The time node 6:00 on the timeline is an example of the first time node. Other situations will not be listed one by one.

[0160] It should be understood that in the embodiment of the present application, the card display area and the timeline display area can be distributed vertically or horizontally, and the arrangement of reminder cards in the card display area can also be arranged horizontally or vertically. Figure 1 In terms of Figure 1 As shown in (a), the card display area and the timeline display area are distributed vertically, and the card display area is located on the top of the timeline display area, and the cards in the card display area are arranged horizontally. Figure 1 As shown in (c), the card display area and the timeline display area are distributed left and right, and the card display area is located on the left side of the timeline display area, and the cards in the card display area are arranged vertically. Figure 1 When the reminder card in the card display area shown in (a) is displayed, it can be executed by sliding horizontally. Figure 1 When switching the reminder card in the card display area shown in (c), it can be executed by a vertical sliding operation. That is, the direction of the sliding operation to switch the reminder card corresponds to the arrangement direction of the reminder card in the card display area.

[0161] In one implementation, the method further includes: displaying a first reminder card in a card display area in the second interface; and displaying a second reminder card in the card display area of ​​the second interface in response to a third operation of the user on the card display area in the second interface, wherein the third operation is used to switch the card displayed in the card display area. In this implementation, the reminder card currently displayed in the card display area can be switched by the third operation. It should be understood that the first reminder card and the second reminder card here can be any of the above reminder cards.

[0162] When the card display area is pinned on top of the timeline display area and the reminder card is arranged horizontally (horizontally) in the card display area, the third operation may be a horizontal sliding operation on the card display area; when the card display area and the timeline display area are distributed left and right and the reminder card is arranged vertically in the card display area, the third operation may be a vertical sliding operation on the card display area.

[0163] In one implementation, after displaying the second interface of the calendar application, the method further includes: in response to a user sliding operation on the card of the first transaction, displaying at least one management control, the at least one management control including at least one of an important transaction marking control, a transaction deletion control, an ignore reminder control, and a postpone reminder control, wherein the important transaction marking control is used to indicate that the first transaction is marked as an important transaction, the transaction deletion control is used to indicate that the card of the first transaction in the timeline display area is deleted, the ignore reminder control is used to indicate that the first transaction is no longer reminded, and the postpone reminder control is used to indicate that a new time node corresponding to the first transaction is determined on the timeline; in response to a user clicking operation on the first management control in the at least one management control, managing the first transaction according to the instruction of the first management control. In this implementation, the management of the card of the transaction in the timeline display area is mainly given, the management control is displayed by sliding the card, and the corresponding management is realized by operating the controls corresponding to different management targets. Figure 7-Figure 9 An example of this implementation is given.

[0164] In one implementation, the timeline display area includes a first folding control, and the first folding control corresponds to a first time period on the timeline. The above method further includes: in response to a user clicking the first folding control, displaying a time period identifier of the first time period and the number of transactions in the first time period in the timeline display area, and hiding the card corresponding to the first time period in the timeline display area. In this implementation, by setting a folding control in the timeline display area, it is convenient for users to fold and hide transactions according to time periods. Correspondingly, users can also release the folding state by operating the folding control, so that the folded and hidden transactions are re-displayed in the interface. Figure 4 An example of this implementation is given, Figure 4 The small icons of "all day", "morning", "noon" and "evening" can all be used as the above-mentioned first folding control, and the text descriptions of all day, morning, noon and evening can be used as the above-mentioned time period identifiers.

[0165] In another implementation, the timeline display area includes a second expansion control, and the second expansion control corresponds to a second time period on the timeline. The method further includes: in response to a user clicking the first expansion control, displaying the cards in the second time period hidden in the timeline display area. In this implementation, by setting an expansion control in the timeline display area to facilitate users to re-expand transactions that have been folded and hidden according to time periods, it can be understood as releasing the folding state, so that the folded and hidden transactions are re-displayed in the interface. Figure 4 The “expanding control for each time period” in can be used as an example of the second expanding control mentioned above.

[0166] In one implementation, the method further includes: when entering the second interface at the first time, a card for the fifth transaction is included in the timeline display area, the fifth transaction corresponds to the fifth time node on the timeline, and the fifth time node is determined based on the first time; when entering the second interface at the second time, a card for the sixth transaction is included in the timeline display area, the sixth transaction corresponds to the sixth time node on the timeline, and the sixth time node is determined based on the second time. In this implementation, when entering the second interface at different times, different interface contents will be presented, that is, the display of the second interface will locate the time node on the timeline according to the time point of entry and display the card of the transaction corresponding to the time node. Combined with Figure 2 and Figure 5 It can be seen that Figure 2 The display interface of "My Day" (an example of the second interface) is entered at 7:15 (an example of the first time). Figure 5 The "My Day" interface is entered at 20:20 (an example of the second time). After entering at two different times, the cards contained in the timeline display area are different. Figure 2 There is no 20:30 event in Figure 5 The event at 20:30 is shown in the figure. If the event at 20:30 is regarded as the sixth event, then 20:30 on the timeline is the sixth time node mentioned above.

[0167] In one implementation, the method further includes: when entering the second interface at the first time, displaying the first part of the timeline as the first color, the second part of the timeline as the second color, the first part being the part of the timeline before the first time, and the second part being the part of the timeline after the first time; when entering the second interface at the second time, displaying the third part of the timeline as the first color, the fourth part of the timeline as the second color, the third part being the part of the timeline before the second time, and the fourth part being the part of the timeline after the second time. In this implementation, when entering the second interface at different times, different timeline color distributions will be seen, that is, the color distribution of the timeline in the second interface will locate the time node on the timeline according to the time point of entry, and display the color before the time node and the color after the time node as two different colors, respectively. Combined with Figure 2 and Figure 5 It can be seen that Figure 2 The display interface of "My Day" (an example of the second interface) is entered at 7:15 (an example of the first time). Figure 5 The "My Day" display interface is entered at 20:20 (an example of the second time). After entering at two different times, the color distribution of the time axis is different. Figure 2Before 7:00, it is black (an example of the first color), and after 7:00, it is blue (an example of the second color); Figure 5 In the middle, it is black before 20:30 and blue after 20:30. Figure 3 It can also be inferred that the time node corresponding to the real time of entering the second interface on the time axis is 16:00, so Figure 3 The time axis in the figure is displayed with different colors for the time before 16:00 and after 16:00.

[0168] In one implementation, the timeline display area includes an all-day transaction section and a time-segment transaction section. The timeline of the all-day transaction section and the time-segment transaction section are different in form. The all-day transaction section is used to display cards for transactions with a full-day execution period, and the time-segment transaction section is used to display transactions with a period that is not a full-day execution period. In this implementation, transactions without a clear execution period (all-day transactions) and transactions with a clear execution period (time-segment transactions) are displayed separately and are distinguished on the timeline, making it convenient for users to view and manage the two types of transactions separately. Figure 3 It can be seen that the timeline for all-day affairs can be represented by a dotted line, and the timeline for time-phased affairs can be represented by a solid line (i.e., the timeline for the all-day affairs part and the timeline for the time-phased affairs part have different shapes).

[0169] In one implementation, the card of the first transaction includes at least one of the following: a title of the first transaction, an execution time period of the first transaction, a location of the first transaction, and an application source mark of the first transaction. In this implementation, the content of the transaction card is described, and it should be understood that the cards of other transactions connected in series on the timeline can be the same as the card of the first transaction. Figure 6 gives an example of what the card contains, Figure 6 The contents of several cards are not exactly the same.

[0170] In one implementation, the card of the first transaction includes a jump control, and the method further includes: in response to a user clicking the jump control, displaying the fourth interface of the first application, the first application being the application corresponding to the jump control, and the fourth interface being the initial interface of the first application or the interface corresponding to the jump control. In this implementation, by setting a jump control in the card of the transaction, it is convenient for the user to switch applications with one click, which can be switching to the homepage (initial interface) of another application (non-calendar application), or directly jumping to the interface corresponding to the jump control in another application. Figure 6 (b) shows a card that contains a jump control. Figure 3 As shown in , the jump control can be an identifier of a related application or a jump link. Figure 3The example that the first application may be a map application, an office application #1, and a video application #2 is also given. The user can quickly enter the associated application through the jump control.

[0171] In one implementation, the card display area also includes at least one of a departure reminder card, a basic card, a tomorrow's schedule reminder card, a time anomaly reminder card, and a special day reminder card; the departure reminder card is used to remind the departure of the affairs that need to be traveled in the timeline display area, the basic card is used to display date information and weather information, the tomorrow's schedule reminder card is used to display the statistical data of the affairs of the next day, the time anomaly reminder card is used to display the affairs that need to be arranged in advance on the next day, and the special day reminder card is used to display the date information and affairs content of the special day. In this implementation, the other cards that can be displayed in the card display area are explained, that is, the card display area can display different types of reminder cards, enrich the display content, and better meet the management needs of users. Figure 11-Figure 15 Examples of various reminder cards are given.

[0172] S1903: In response to the user's second operation on the conflicting transaction reminder card, display a third interface of the calendar application.

[0173] The third interface includes a card for the second transaction and a card for the third transaction. The card for the second transaction and the card for the third transaction are located in the timeline display area. The second transaction corresponds to the second time node on the timeline, and the third transaction corresponds to the third time node on the timeline. There is a time conflict between the second transaction and the third transaction.

[0174] Combination Figure 2 , assuming Figure 2 The conflicting transaction reminder card is displayed in the middle card display area. When the user performs the second operation on the conflicting transaction reminder card, the cards of the second and third transactions that conflict with the conflicting transaction reminder card are displayed in the timeline display area in the third interface. Figure 2 The two transactions at 12:00 in the figure can be regarded as examples of the second transaction and the third transaction respectively.

[0175] In one implementation, the conflicting transaction reminder card includes a viewing control, and the second operation is an operation of clicking the viewing control. In this implementation, the display of the third interface is mainly triggered by clicking the viewing control in the conflicting transaction reminder card, that is, the positioning display of the transaction corresponding to the conflicting transaction reminder card in the timeline display area. Setting the viewing control can more clearly indicate to the user how to use the conflicting transaction reminder card. Fig.12 The "View Now" in the example can be regarded as an example of a view control, and the click operation of the view control can be regarded as an example of a second operation.

[0176] In addition to the click operation of the above-mentioned viewing control, the conflicting transaction reminder card can also be clicked to trigger the positioning display of the transaction corresponding to the conflicting transaction reminder card in the timeline display area. In other words, the second operation can also be the operation of clicking the conflicting transaction reminder card. In this case, the conflicting transaction reminder card may not include the viewing control. Fig.12 In other words, it is assumed Fig.12 The card shown does not include viewing controls, and a tap anywhere on the card can be used as a secondary action.

[0177] In one implementation, the card of the second transaction is fully displayed in the third interface; and / or, the card of the third transaction is fully displayed in the third interface. In this implementation, when the third interface is displayed under the triggering of the second operation, it is ensured that at least one card of the conflicting transaction is fully displayed in the third interface. This facilitates the user to view and manage conflicting transactions. Figure 2 or Figure 5 , the two transactions at 12:00 can be regarded as the second transaction and the third transaction respectively. Then, in this implementation, the card of at least one of the two transactions is fully displayed in the interface. Figure 2 There are many transactions before 12:00, which causes the two conflicting transactions at 12:00 not to be displayed. Figure 2 In the interface shown, that is, this is the second interface, then in the above implementation, when the user performs the second operation, the card of at least one of the two conflicting transactions at 12:00 will be fully displayed in the third interface. It should also be understood that for three or more conflicting transactions, in this implementation, the card of at least one transaction is still fully displayed in the third interface.

[0178] In one implementation, the method further includes: when it is detected that the time conflict between the second transaction and the third transaction is resolved, the conflicting transaction reminder card is stopped from being displayed in the card display area; or, when it is detected that the execution time period of the second transaction and / or the execution time period of the third transaction is over, the conflicting transaction reminder card is stopped from being displayed in the card display area. In this implementation, the display of the conflicting transaction reminder card can be stopped when the conflict between the conflicting transactions is resolved, or when the conflicting transactions do not need to be investigated for their conflicts due to the natural progress of time. For the case where the conflicting transaction reminder card is stopped when the execution time period of only one transaction has not ended, it can be understood that when the execution time period of one of the two conflicting transactions has ended, there is only one transaction that needs to be processed immediately or is being processed at the current time, and at this time, there is no need to investigate the conflict between the currently executing transaction and the ended transaction. For the case where the conflicting transaction reminder card is stopped when the execution time period of all transactions has ended, it can be understood that when the execution time periods of the two conflicting transactions have ended, there is no need to investigate the conflict between the two ended transactions at the current time.

[0179] In one implementation, the third interface also includes a card for a fourth transaction, the card for the fourth transaction is located in the timeline display area, and the fourth transaction corresponds to a fourth time node on the timeline; the fourth transaction has a time conflict with the second transaction, and / or the fourth transaction has a time conflict with the third transaction, and the above method also includes: when it is detected that the time conflict between any two of the second transaction, the third transaction and the fourth transaction is resolved, updating the conflict information in the conflict transaction reminder card in the card display area; or, when it is detected that all time conflicts between the second transaction, the third transaction and the fourth transaction are resolved, stopping displaying the conflict transaction reminder card in the card display area; or, when it is detected that at most one of the second transaction, the third transaction and the fourth transaction has not ended, stopping displaying the conflict transaction reminder card in the card display area. In this implementation, mainly for the situation where there are conflicts among three transactions, when the conflicts between only some of the transactions are resolved, updating the conflict information in the conflict transaction reminder card, when the conflicts between all transactions are resolved, the display of the conflict reminder card can be stopped, or when there are conflicting transactions, due to the advancement of natural time, there is only at most one transaction whose execution time period has not ended, stopping the display of the conflict reminder card.

[0180] It should also be understood that the situation where there are conflicts among four or more transactions is similar to the handling method of the above three transactions, that is, when the conflicts between only some of the transactions are resolved, the conflict information in the conflict transaction reminder card is updated, and the display of the conflict reminder card can be stopped when the conflicts between all transactions are resolved, or when there are conflicting transactions and due to the natural advancement of time, there is only one transaction whose execution time period has not ended, the display of the conflict reminder card is stopped. The only difference from the above is the total number of conflicting transactions.

[0181] In one implementation, in the second interface, the cards in the card display area and the timeline display area correspond to the first date; after displaying the second interface of the calendar application, the method further includes: in response to the user's date switching operation in the second interface, displaying the fifth interface of the calendar application, in which the cards in the card display area and the timeline display area correspond to the second date, and the date switching operation is a swipe up operation, a swipe down operation, or a click operation on the date switching control. In this implementation, a method for switching to a transaction management interface of another date is provided, which can mainly switch to the previous day or the next day by swiping up or swiping down, and independently select a date by clicking on the date switching control. Figure 16-Figure 18 An example of how to interactively switch the date corresponding to "My Day" is given.

[0182] Fig.19 The method shown mainly displays the transactions that need to be focused and managed by the user in a centralized manner through the card display area, connects all the transactions that need to be processed in a day from the time dimension through the timeline display area, and the linkage operation of the two display areas facilitates users to quickly view and manage transactions. In the timeline display area, all reminder transactions for the whole day are centrally displayed according to the timeline, realizing the centralized management of all transactions that need to be processed on the target date from the time dimension, so that users can not only know what to do on the target date, but also know what to do first and what to do later on this day, so that users can better plan their affairs for the whole day based on this. In the card display area, transactions that need to be focused and managed by the user, such as conflicting transactions, are centrally displayed, that is, the transactions that are most likely to meet the user's management needs are presented in the card display area in the form of reminder cards, which can facilitate users to quickly find transactions that need to be managed. The linkage operation between the two display areas can facilitate users to quickly view and manage transactions. For example, here, the user can click the conflicting transaction reminder card in the card display area to locate the corresponding transaction on the timeline display area, and then manage the corresponding transaction.

[0183] The above mainly introduces the method of the embodiment of the present application in conjunction with the accompanying drawings. It should be understood that although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence, these steps are not necessarily performed in sequence in the order shown in the figure. Unless clearly stated in this article, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the various embodiments described above may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times, and the execution order of these steps or stages is not necessarily performed in sequence, but can be performed in turn or alternately with other steps or at least a part of the steps or stages in other steps. The device of the embodiment of the present application is introduced below in conjunction with the accompanying drawings.

[0184] Fig. 20 Schematic diagram of the hardware structure of an electronic device according to an embodiment of the present application. Fig. 20 As shown, the electronic device 900 may include a processor 910, an external memory interface 920, an internal memory 921, a universal serial bus (USB) interface 930, a charging management module 940, a power management module 941, a battery 942, an antenna 1, an antenna 2, a mobile communication module 950, a wireless communication module 960, an audio module 970, a speaker 970A, a receiver 970B, a microphone 970C, an earphone interface 970D, a sensor module 980, a button 990, a motor 991, an indicator 992, a camera 993, a display screen 994, and a subscriber identification module (SIM) card interface 995, etc.

[0185] Among them, the sensor module 980 may include a pressure sensor 980A, a gyroscope sensor 980B, an air pressure sensor 980C, a magnetic sensor 980D, an acceleration sensor 980E, a distance sensor 980F, a proximity light sensor 980G, a fingerprint sensor 980H, a temperature sensor 980J, a touch sensor 980K, an ambient light sensor 980L, a bone conduction sensor 980M, etc.

[0186] It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 900. In other embodiments of the present application, the electronic device 900 may include more or fewer components than shown in the figure, or combine some components, or split 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.

[0187] For example, Fig. 20The processor 910 shown may include one or more processing units, for example, the processor 910 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors.

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

[0189] In the embodiment of the present application, the processor 910 is mainly used to start the application loading page and respond to the interactive operations input by the user.

[0190] The processor 910 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 910 is a cache memory. The memory may store instructions or data that the processor 910 has just used or cyclically used. If the processor 910 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 910, and thus improves the efficiency of the system.

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

[0192] The display screen 994 is used to display images, videos, etc. The display screen 994 includes a display panel. In some embodiments, the electronic device 900 may include 1 or N display screens 994, where N is a positive integer greater than 1.

[0193] In the embodiment of the present application, each interface is presented to the user mainly through the display screen 994, for example Figure 1-Figure 14 Each interface in .

[0194] 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 900 can be realized, such as image recognition, face recognition, voice recognition, text understanding, etc.

[0195] In the embodiment of the present application, the NPU can be used to identify a transaction that can generate a card and instruct the processor 910 to generate a card. For example, the NPU can instruct the processor 910 to generate a card according to Fig. 9 Generate cards in the form shown.

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

[0197] In the embodiment of the present application, the pressure sensor 980A is mainly used to collect user interaction operations, such as sliding operations, clicking operations, etc.

[0198] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0199] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0200] An embodiment of the present application also provides an electronic device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, wherein the processor can implement the steps in any of the above methods when executing the computer program.

[0201] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0202] An embodiment of the present application provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0203] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device that can carry the computer program code to the camera / electronic device, recording medium, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals and telecommunication signals.

[0204] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0205] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0206] In the embodiments provided in the present application, it should be understood that the disclosed devices / equipment and methods can be implemented in other ways. For example, the device / equipment embodiments described above are merely schematic, for example, the division of the modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0207] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0208] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0209] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0210] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.

[0211] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0212] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0213] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A transaction management method, characterized in that: include: Display a first interface of a calendar application, wherein the first interface includes a first control; In response to a first operation of the user on the first control, a second interface of the calendar application is displayed, wherein the second interface includes a card display area and a timeline display area; wherein the card display area includes a conflicting transaction reminder card; the timeline display area includes a timeline and a card of a first transaction, and the first transaction corresponds to a first time node on the timeline; In response to the user's second operation on the conflicting transaction reminder card, a third interface of the calendar application is displayed, the third interface including a card for the second transaction and a card for the third transaction, the card for the second transaction and the card for the third transaction are located in the timeline display area, the second transaction corresponds to the second time node on the timeline, the third transaction corresponds to the third time node on the timeline, and there is a time conflict between the second transaction and the third transaction.

2. The method according to claim 1, characterized in that The conflicting transaction reminder card includes a view control, and the second operation is an operation of clicking the view control.

3. The method according to claim 1, characterized in that The card of the second transaction is fully displayed in the third interface; and / or the card of the third transaction is fully displayed in the third interface.

4. The method according to claim 1, characterized in that: The method further comprises: When it is detected that the time conflict between the second transaction and the third transaction is resolved, stop displaying the conflicting transaction reminder card in the card display area; or, When it is detected that the execution time period of the second transaction and / or the execution time period of the third transaction ends, the display of the conflicting transaction reminder card in the card display area stops.

5. The method according to claim 1, characterized in that The third interface further includes a card of a fourth transaction, the card of the fourth transaction is located in the timeline display area, the fourth transaction corresponds to a fourth time node on the timeline; the fourth transaction has a time conflict with the second transaction, and / or the fourth transaction has a time conflict with the third transaction, and the method further includes: When it is detected that the time conflict between any two of the second transaction, the third transaction and the fourth transaction is resolved, updating the conflict information in the conflicting transaction reminder card in the card display area; or, When it is detected that all time conflicts among the second transaction, the third transaction and the fourth transaction are resolved, stop displaying the conflicting transaction reminder card in the card display area; or, When it is detected that the execution time period of at least one transaction among the second transaction, the third transaction and the fourth transaction has not yet ended, the display of the conflicting transaction reminder card in the card display area is stopped.

6. The method according to claim 1, characterized in that After displaying the second interface of the calendar application, the method further includes: In response to a user sliding operation on the card of the first transaction, at least one management control is displayed, wherein the at least one management control includes at least one of an important transaction marking control, a transaction deletion control, an ignore reminder control, and a postpone reminder control, wherein the important transaction marking control is used to indicate that the first transaction is marked as an important transaction, the transaction deletion control is used to indicate that the card of the first transaction in the timeline display area is deleted, the ignore reminder control is used to indicate that the first transaction is no longer reminded, and the postpone reminder control is used to indicate that a new time node corresponding to the first transaction is determined on the timeline; In response to a user clicking operation on a first management control among the at least one management control, the first transaction is managed according to an instruction of the first management control.

7. The method according to any one of claims 1 to 6, characterized in that The timeline display area includes a first folding control, and the first folding control corresponds to a first time period on the timeline. The method further includes: In response to a user clicking operation on the first folding control, a time period identifier of the first time period and the number of transactions in the first time period are displayed in the timeline display area, and a card corresponding to the first time period in the timeline display area is hidden.

8. The method according to any one of claims 1 to 6, characterized in that The method further comprises: When entering the second interface at the first time, a card of a fifth transaction is included in the timeline display area, the fifth transaction corresponds to a fifth time node on the timeline, and the fifth time node is determined according to the first time; When entering the second interface at the second time, the timeline display area includes a card for the sixth transaction, the sixth transaction corresponds to the sixth time node on the timeline, and the sixth time node is determined according to the second time.

9. The method according to any one of claims 1 to 6, characterized in that The method further comprises: When entering the second interface at a first time, displaying the first part of the timeline in a first color and the second part of the timeline in a second color, the first part being the part of the timeline before the first time and the second part being the part of the timeline after the first time; When entering the second interface at the second time, the third part of the timeline is displayed in the first color, the fourth part of the timeline is displayed in the second color, the third part is the part of the timeline before the second time, and the fourth part is the part of the timeline after the second time.

10. The method according to any one of claims 1 to 6, characterized in that The timeline display area includes an all-day affairs part and a time-phase affairs part. The timeline of the all-day affairs part and the time-phase affairs part are different in form. The all-day affairs part is used to display cards of affairs whose execution time period is a whole day, and the time-phase affairs part is used to display affairs whose execution time period is not a whole day.

11. The method according to any one of claims 1 to 6, characterized in that The card of the first transaction includes at least one of the following: a title of the first transaction, an execution time period of the first transaction, a location of the first transaction, and an application source mark of the first transaction.

12. The method according to any one of claims 1 to 6, characterized in that The card of the first transaction includes a jump control, and the method further includes: In response to a user clicking operation on the jump control, a fourth interface of the first application is displayed, the first application is an application corresponding to the jump control, and the fourth interface is an initial interface of the first application or an interface corresponding to the jump control.

13. The method according to any one of claims 1 to 6, characterized in that The card display area also includes at least one of a departure reminder card, a basic card, a tomorrow's schedule reminder card, a time anomaly reminder card and a special day reminder card; the departure reminder card is used to provide departure reminders for matters that require travel in the timeline display area, the basic card is used to display date information and weather information, the tomorrow's schedule reminder card is used to display statistical data for next day's matters, the time anomaly reminder card is used to display matters that need to be arranged in advance for the next day, and the special day reminder card is used to display date information and matter content of special days.

14. The method according to any one of claims 1 to 6, characterized in that The method further comprises: Displaying a first reminder card in the card display area in the second interface; In response to a third operation performed by the user on the card display area in the second interface, a second reminder card is displayed in the card display area of ​​the second interface, wherein the third operation is used to switch the card displayed in the card display area.

15. The method according to any one of claims 1 to 6, characterized in that In the second interface, the cards in the card display area and the timeline display area correspond to the first date; after displaying the second interface of the calendar application, the method further includes: In response to the user's date switching operation in the second interface, the fifth interface of the calendar application is displayed. In the fifth interface, the cards in the card display area and the timeline display area correspond to the second date, and the date switching operation is a swipe up operation, a swipe down operation, or a click operation on the date switching control.

16. An electronic device comprising a memory, one or more processors, and a computer program stored in the memory and executable on the processors, characterized in that: When the one or more processors execute the computer program, the electronic device implements the method according to any one of claims 1 to 15.

17. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by an electronic device, the method according to any one of claims 1 to 15 is implemented.

Images