Bill management method and electronic equipment

Abstract

The invention provides a bill management method and electronic equipment. The electronic device for implementing the bill management method provided by the invention can be a mobile phone, a tablet computer, a notebook computer and other terminal devices. In the process of implementing the bill management method provided by the invention, the electronic equipment can count the monthly bills of the user, and when the first bill processing deadline of the month is close, the bill calendar card containing all the bills of the month is displayed on an interface such as a desktop or a negative screen. The card can systematically display the processing deadline of all bills in the month, the type of each bill and other information, so that a user can reasonably arrange an expenditure plan.

Description

Technical Field

[0001] This application relates to the field of terminals, and more particularly to billing management methods and electronic devices. Background Technology

[0002] With the widespread use of online payments, users receive multiple bills each month, such as credit card bills, loan bills, online shopping bills, utility bills, and so on. Faced with a large number of complex bills, users need to put in extra effort to manage the due dates of each bill to ensure that none are overdue and to balance their monthly spending. Summary of the Invention

[0003] This application provides a bill management method and an electronic device. The electronic device implementing the bill management method provided in this application can be a mobile phone, tablet computer, laptop computer, or other terminal device. During the implementation of the bill management method, the electronic device can compile the user's monthly bills and, as the first bill processing deadline of the month approaches, display a bill calendar card containing all bills for that month on the desktop or negative one screen. This card systematically displays the processing deadlines for all bills for the month, as well as information such as the type of each bill, to help the user rationally plan their spending.

[0004] In a first aspect, this application provides a bill management method, which includes: displaying a first card on a desktop or a negative one screen; the first card displays a first date and all dates of a first month, the all dates of the first month including the date corresponding to the bill, the date corresponding to the bill including the date carrying a first identifier, the bill including a first type of bill, the date carrying the first identifier being the processing deadline of the first type of bill, the first card also including first category information, the first category information being used to indicate the specific type of the first type of bill; wherein, the first date is the current date; in response to an operation on the first card, displaying a first interface of a calendar application; the first interface including all dates of the first month and a schedule list, the all dates of the first month in the first interface including the date corresponding to the bill, and the schedule list including detailed information of the bill.

[0005] Implementing the method provided in the first aspect, electronic devices can display a repayment calendar card (i.e., the first card) on the desktop or negative one screen, including all bill processing deadlines for the month. This allows users to intuitively and clearly understand all bill processing deadlines for the month, as well as the types of bills corresponding to each deadline, thereby enabling them to rationally plan their spending. Furthermore, users can quickly access a calendar application through the aforementioned repayment calendar card to obtain more billing information, including all the information in the repayment calendar card, such as the bill issuer, amount, date, and countdown.

[0006] In conjunction with the method provided in the first aspect, in some embodiments, the date corresponding to the bill also includes a date carrying a second identifier, the bill also includes a second type of bill, the date carrying the second identifier is the processing period of the second type of bill, and the first card also includes second category information, which is used to indicate the specific type of the second type of bill.

[0007] Bills can be divided into repayment bills and utility bills. Repayment bills can include: credit card repayments, loan repayments, and internet finance repayments; utility bills can include: electricity bills, water bills, gas bills, and telephone bills.

[0008] In one specific implementation, an electronic device may use one identifier to mark a repayment bill and another identifier to mark a payment bill. For example, the first type of bill may be a repayment bill, and the second type of bill may be a payment bill; correspondingly, the first identifier is for marking a repayment bill, and the second identifier is for marking a payment bill.

[0009] In another specific implementation, the electronic device can further differentiate between different types of bills in the repayment bill and payment bill. For example, the electronic device can use three identifiers to mark credit card repayments, loan repayments, and internet finance repayments in the repayment bill, and use four other identifiers to mark electricity bills, water bills, gas bills, and telephone bills in the payment bill. In this case, for example, the first type of bill can be a credit card repayment bill, and the second type of bill can be a loan repayment bill; correspondingly, the first identifier is for marking credit card repayment bills, and the second identifier is for marking loan repayment bills.

[0010] In this way, when browsing the first card, users can directly and intuitively determine the bill type corresponding to each processing period.

[0011] In conjunction with the method provided in the first aspect, in some embodiments, the first date is N days earlier than the processing deadline of the earliest due bill in the first month, where N is a positive integer, and displaying the first card on the desktop or negative one screen includes: when the first date arrives, starting to display the first card on the desktop or negative one screen.

[0012] In this way, electronic devices can flexibly start displaying the first card as the processing deadline for the first bill of the month approaches, in order to maximize the effectiveness of reminders to users.

[0013] In some embodiments, in conjunction with the method provided in the above embodiments, the method further includes: stopping the display of the first card after a fourth duration of displaying the first card.

[0014] In this way, electronic devices can avoid continuously displaying the first card on the desktop or negative one screen for extended periods, which would cause information redundancy on the desktop or negative one screen and compromise its simplicity.

[0015] In conjunction with the method provided in the first aspect, in some embodiments, the method further includes: displaying a first control in response to an operation on a first schedule in the schedule list; and directly displaying a repayment interface for the bill corresponding to the first schedule in response to an operation on the first control. The first schedule is any schedule in the schedule list.

[0016] At this point, users can quickly access the control to perform the repayment operation while browsing various bills through the calendar application. Then, through the shortcuts provided by the control, they can directly jump to the repayment page or payment interface to complete the repayment or payment.

[0017] In conjunction with the methods provided in the above embodiments, in some embodiments, the repayment interface or interface is provided by a first application; wherein, when the electronic device has the official online payment application of the bill issuer installed, the official online payment application of the bill issuer is the first application; when the electronic device does not have the official online payment application of the bill issuer installed, the online payment application with the highest usage frequency installed on the electronic device is the first application.

[0018] By implementing the method provided in the above embodiments, when providing users with fast repayment or payment services, the electronic device can first determine the most suitable official online payment application for providing fast repayment or payment services based on the bill issuer. It then utilizes the repayment or payment services provided by the aforementioned official online payment application to help users quickly repay / pay their bills. When the user has not installed the bill issuer's official online payment application, the electronic device can obtain repayment / payment services from other online payment applications, similarly helping users quickly repay / pay their bills.

[0019] In this way, electronic devices do not need to rely on user specifications to determine which application provides the repayment or express service. On the other hand, users do not need to specify the repayment or express service application, saving user time and effort.

[0020] In conjunction with the method provided in the first aspect, in some embodiments, the method further includes: detecting an operation on a second control in a first interface and displaying multiple labels; detecting an operation on a first label among the multiple labels and adding one or more third identifiers to all dates in the first month; the dates carrying the third identifiers are dates with one or more of the following types of schedules: meetings, learning, and entertainment.

[0021] In addition to tracking monthly bill processing deadlines, the electronic device can also track other monthly schedules for users, such as meetings, study sessions, entertainment activities, and daily purchases. The device can be tagged with each of these categories. When a user opens the calendar by interacting with a bill calendar card, the device automatically matches the bill tags and then marks the bill processing deadline for that month only in the calendar for that month.

[0022] By implementing the above method, the electronic device can support users switching tags. The electronic device can update the markers and related information in the calendar based on the switched tag. At this point, the user can browse another type of schedule for the month. For example, the user can switch the tag from "Bills" to "Meetings." The electronic device can then remove the marker originally used to indicate the bill processing deadline and display a marker indicating the meeting schedule. In some embodiments, the electronic device can also support marking all schedules in the calendar for the month, including bills, meetings, learning, entertainment activities, and daily purchases. This allows the user to browse all schedules for the month at once.

[0023] In conjunction with the method provided in the first aspect, in some embodiments, the method further includes: obtaining a first type of bill via a received SMS message and / or notification.

[0024] By implementing the method provided in the above embodiments, electronic devices can manage users' SMS messages and notifications, obtain users' bills by parsing the content of SMS messages and notifications, and then generate bill calendar cards to remind users of necessary expenses for the month and help users manage their funds reasonably.

[0025] In conjunction with the method provided in the first aspect, in some embodiments, the method further includes: upon reaching the third date, displaying a second card corresponding to the second date on the desktop or the negative one screen, wherein the second date is the processing deadline for the first bill in the first month, and the third date is after the first date and before the second date; the second card displays the bill information of the first bill, the bill information including one or more of the following: bill issuer, amount, date, countdown.

[0026] By implementing the method provided in the above embodiments, when the processing deadline of a certain bill (i.e., the first bill) is approaching, for example, 3 days before the processing deadline of the first bill, the electronic device can display a bill reminder card (i.e., the second card) on the desktop or the negative one screen, which specifically displays the details of the bill. In this way, the user can more clearly and directly understand that the bill is about to expire, and at the same time confirm the bill issuer and amount, without any other operation.

[0027] In conjunction with the method provided in the above embodiments, in some embodiments, the second card further includes a third control, and the method further includes: in response to an operation on the third control, directly displaying the repayment interface corresponding to the first bill.

[0028] In the repayment scenario, users can directly access the repayment interface by using the repayment control (i.e., the third control) displayed in the second card, and complete the repayment operation without having to manually identify the application corresponding to the bill that can perform the repayment operation, and then open that application to perform the repayment operation; nor is it necessary to enter the calendar application and access the repayment interface through the methods provided in the calendar application.

[0029] In some embodiments, the second card further includes a third control, and the method further includes: detecting an operation on the third control and directly displaying the payment interface corresponding to the first bill; detecting an operation on the input box in the payment interface, displaying a touch keyboard and displaying the bill information of the first bill in the candidate area of ​​the touch keyboard; detecting an operation on the bill information and filling the bill information into the input box.

[0030] In the payment scenario, users can directly access the payment interface by using the payment control (i.e., the third control) displayed in the second card, and complete the payment operation without having to manually identify the application that can perform the payment operation for the bill, and then open that application to make the payment; nor is it necessary to enter the calendar application and access the payment interface through the methods provided in the calendar application.

[0031] When making payments through the payment interface, in scenarios where payment information needs to be entered, the electronic device can also display relevant information obtained from SMS or notifications in the candidate area of ​​the keyboard for the user to select and then directly enter into the relevant input boxes on the payment interface, simplifying the user operation and helping the user to pay quickly.

[0032] In some embodiments, the method further includes: detecting that the first bill has been successfully processed before the end of the second date, displaying a third card and stopping the display of the second card, wherein the third card displays a fourth identifier indicating that the bill has been successfully processed; and stopping the display of the third card after a second duration of displaying the third card.

[0033] Implementing the method provided in the above embodiments, before the bill processing deadline, after detecting that the corresponding bill has been successfully processed, the electronic device can switch the bill reminder card that reminds the user to process the bill to a processed card indicating that the bill has been successfully processed. After displaying the processed card for a period of time, the electronic device can stop displaying the processed card to avoid redundancy and maintain the simplicity of the desktop or negative one screen.

[0034] In some embodiments, the method further includes: after the second date has ended and no successful processing of the first bill has been detected, displaying a fourth card and stopping the display of the second card, wherein the fourth card displays a fifth identifier indicating overdue processing; and stopping the display of the fourth card after a third period of displaying the fourth card.

[0035] Implementing the method provided in the above embodiments, after the bill processing period has ended and no corresponding bill has been detected for successful processing, the electronic device can switch the bill reminder card that reminds the user to process the bill to an overdue card indicating that the bill is overdue, so as to remind the user to process the bill as soon as possible and avoid greater financial losses. Similarly, after displaying the overdue card for a period of time, the electronic device can stop displaying the overdue card to avoid redundancy and maintain the simplicity of the desktop or negative one screen.

[0036] The first bill can be a single bill or include multiple bills. When the first bill includes multiple bills, meaning a single processing period applies to multiple bills simultaneously, the electronic device can display multiple second cards accordingly. These second cards can be displayed flat or stacked. Each card displays the billing information for one bill.

[0037] At this point, users can directly and clearly obtain the billing information for multiple bills with the same processing deadline through the aforementioned multiple second cards, and then process these bills separately.

[0038] In conjunction with the method provided in the first aspect, in some embodiments, after displaying the first card on the desktop or negative one screen, the method further includes: obtaining a second bill with a processing period of the fourth date of the first month, the second bill being a first type of bill; and displaying a first identifier on the fourth date in the first card.

[0039] In some scenarios, after the monthly payment calendar card is displayed, the electronic device may receive another bill with a processing deadline in the same month (i.e., a second bill). At this point, the electronic device can update the payment calendar card (first card) to mark the processing deadline of the newly added second bill.

[0040] In conjunction with the method provided in the above embodiments, in some embodiments, the method further includes: displaying a fifth card on the desktop or negative one screen, the fifth card displaying billing information of the second bill, the billing information including one or more of the following: bill issuer, amount, date, countdown; and stopping the display of the fifth card after a fifth duration of display.

[0041] Upon receiving a new bill, the electronic device can also simultaneously display a separate card (i.e., a fifth card) for that bill, showing the details of the newly received bill to notify the user to confirm the new bill.

[0042] In conjunction with the method provided in the first aspect, in some embodiments, the method further includes: detecting an operation on a fourth control in the first card and displaying a third interface; receiving bill information of a third bill input by a user through the third interface, the bill information including one or more of the following: bill issuer, amount, date, countdown; displaying a sixth identifier on a fifth date in the first card, the fifth date being the processing period for the third bill, the sixth identifier being different from the first identifier.

[0043] By implementing the method provided in the above embodiments, users can also add bills themselves. In this way, for some bills that cannot be obtained via SMS or notification, the electronic device obtains them through the user's addition operation, and then manages the user-added bills together, helping users to more comprehensively manage all their bills.

[0044] In a second aspect, this application provides an electronic device including one or more processors and one or more memories; wherein the one or more memories are coupled to one or more processors, and the one or more memories are used to store computer program code, the computer program code including computer instructions, which, when executed by one or more processors, cause the electronic device to perform the method described in the first aspect and any possible implementation thereof.

[0045] Thirdly, embodiments of this application provide a chip system applied to an electronic device. The chip system includes one or more processors, which are used to invoke computer instructions to cause the electronic device to perform the methods described in the first aspect and any possible implementation thereof.

[0046] Fourthly, this application provides a computer-readable storage medium including instructions that, when executed on an electronic device, cause the electronic device to perform the method described in the first aspect and any possible implementation thereof.

[0047] Fifthly, this application provides a computer program product containing instructions that, when the computer program product is run on an electronic device, cause the electronic device to perform the method described in the first aspect and any possible implementation thereof.

[0048] Understandably, the electronic device provided in the second aspect, the chip system provided in the third aspect, the computer storage medium provided in the fourth aspect, and the computer program product provided in the fifth aspect are all used to execute the method provided in this application. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here. Attached Figure Description

[0049] Figures 1A-1JThis is a set of user interface diagrams illustrating the implementation of the above-described billing management method provided in the embodiments of this application; Figures 2A-2C This is a schematic diagram of a user interface for displaying repayment reminder cards provided in an embodiment of this application; Figures 3A-3G This is a user interface diagram of a set of updated repayment reminder cards provided in an embodiment of this application; Figure 4 This is a schematic diagram of the user interface for updating the repayment calendar card after a new bill is received, provided in an embodiment of this application. Figures 5A-5D This is a set of user interface diagrams for users to add bills themselves, provided in an embodiment of this application; Figures 5E-5G This is another set of user interface diagrams for users to add bills themselves, provided in an embodiment of this application; Figure 5H This is a schematic diagram of a user interface for displaying a set of multiple consecutive repayment calendar cards provided in an embodiment of this application; Figures 6A-6G This is a set of user interface diagrams for setting target applications provided in the embodiments of this application; Figures 7A-7B This is a set of user interface diagrams showing repayment calendar cards and payment calendar cards respectively, provided in an embodiment of this application; Figures 7C-7D This is a schematic diagram of a set of user interfaces for inputting payment information provided in an embodiment of this application; Figure 8 This is a schematic diagram of the structure of the billing management application provided in the embodiments of this application; Figure 9 A schematic diagram of the structure of the electronic device 100 is shown. Detailed Implementation

[0050] The terminology used in the following embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be a limitation of this application.

[0051] With the widespread use of online payments, users receive multiple bills every month, such as credit card bills from Bank A, online consumption bills from Internet finance company B, electricity bills from the municipal power supply bureau, and water bills from the municipal water supply bureau.

[0052] Often, users don't immediately process a bill upon receiving it, such as making a payment or bill payment right away. When multiple bills accumulate, especially with different due dates, users can easily forget which bills have been processed and which haven't, resulting in one or more overdue bills, causing financial losses or negatively impacting their credit score.

[0053] Therefore, this application provides a billing management method. This method can be applied to smart terminal devices such as mobile phones and tablets. These smart terminal devices can be referred to as electronic devices 100.

[0054] Not limited to mobile phones and tablets, electronic device 100 can also be a desktop computer, laptop computer, handheld computer, notebook computer, ultra-mobile personal computer (UMPC), netbook, as well as cellular phone, personal digital assistant (PDA), augmented reality (AR) device, virtual reality (VR) device, artificial intelligence (AI) device, wearable device, in-vehicle device, smart home device and / or smart city device. The specific type of electronic device is not particularly limited in the embodiments of this application.

[0055] By implementing the bill management method provided in this application embodiment, the electronic device 100 can obtain the user's bills and determine the repayment date / payment date for each bill. On the first day of the month or at a preset time before the first billing date of each month, the electronic device 100 can display a bill calendar card. The bill calendar card displays all the dates of the month, and also displays a special mark on the repayment date / payment date of the month to indicate that the date is the repayment date / payment date.

[0056] Electronic device 100 can set the display time for bill calendar cards. After a period of display, electronic device 100 can turn off the card, i.e., stop displaying it to avoid redundancy. Alternatively, it can display the card corresponding to a bill when it is due and then turn off the bill calendar card. Upon receiving a new bill, electronic device 100 can update the currently displayed bill calendar card, marking the new due date / payment date. For cards that have been turned off, electronic device 100 can re-display them after marking the new due date / payment date to remind the user of the due date / payment date for the month, especially new due dates / payment dates that the user has not previously paid attention to.

[0057] Furthermore, before the due date / payment date of a bill in the bill calendar card arrives, the electronic device 100 can display a reminder card corresponding to that bill. This card can display detailed bill information, such as the bill issuer, due date / payment date, and amount. The electronic device 100 can also display controls within the card for quick access to the bill processing interface, allowing users to process the bill quickly and conveniently, avoiding overdue payments.

[0058] Figures 1A-1J This is a set of user interface diagrams illustrating the implementation of the above-described billing management method provided in the embodiments of this application.

[0059] Figure 1A This is the main interface (homepage) of an electronic device 100 provided in this application embodiment.

[0060] The main interface is the first page of the desktop system of the electronic device 100. Multiple pages are also located on the right side of the main interface. The electronic device 100 can display these other pages on the right side of the main interface by swiping left. The main interface and the other pages on the right side of the main interface are collectively referred to as the desktop of the electronic device 100. The left side of the main interface may include a negative one screen, which the electronic device can display in response to the user's right swipe.

[0061] like Figure 1A As shown, the main interface may include a status bar 111, a page indicator 112, a frequently used application icon tray 113, and multiple other application icons 114. Among them, the status bar may include one or more signal strength indicators for mobile communication signals (also known as cellular signals), a wireless fidelity (Wi-Fi) signal strength indicator, a battery status indicator, and a time indicator.

[0062] Page indicator 112 can be used to indicate the positional relationship between the currently displayed page (i.e., the main interface) and other pages.

[0063] The tray icon 113 for frequently used applications can include multiple application icons, such as the camera application icon, the contacts application icon, the phone application icon, and the messaging application icon. The application icons in the tray icon 113 for frequently used applications remain displayed when switching desktops.

[0064] Other application icons 114 may include multiple application icons. For example, settings app icon, app store app icon, gallery app icon, weather app icon, etc. Other application icons 114 may also include third-party application icons, such as WeChat. ® Application icons, etc., will not be listed here one by one.

[0065] Other application icons (114) can be distributed across multiple pages, and page indicators can also be used to show which page on the desktop the user is currently viewing. Users can browse application icons on other pages by swiping left or right. Understandably, Figure 1A The illustration of one user interface of the electronic device 100 is merely illustrative and should not be construed as limiting the embodiments of this application.

[0066] In this embodiment of the application, the electronic device 100 can obtain the user's bill via SMS and / or notification.

[0067] In the method of obtaining a bill via notification, firstly, the electronic device 100 can identify all applications providing financial services (i.e., financial applications, online payment applications) installed on the device through application tags. Then, the electronic device 100 can receive notifications from these financial applications and determine, through methods such as keyword extraction and semantic recognition, whether the notification includes billing information such as the bill issuer, payment / repayment date, and amount. Obtaining a set of billing information through a single notification by the electronic device 100 can be considered as obtaining a single bill.

[0068] Similarly, after receiving a text message, electronic device 100 can determine whether the message includes billing information such as the bill sender, payment / repayment date, and amount through methods such as keyword extraction and semantic recognition. Obtaining a set of billing information from a single text message can also be considered as obtaining a single bill.

[0069] Understandably, the electronic device 100 can deduplicate the acquired bills. When multiple bills contain identical information, the electronic device 100 will merge these multiple bills into one.

[0070] For example, electronic device 100 can successively obtain three bills with repayment dates of May 5th, May 15th, and May 28th. The specific bill information for these three bills is shown in Table 1: Table 1

[0071] Electronic device 100 can categorize all received bills according to the payment due date. Bills with the same payment due date in the same month are considered same-month bills. The three bills shown in Table 1 all have payment due dates in May (the first month), and are therefore same-month bills.

[0072] On the N1 day before the first bill of the month, electronic device 100 generates a repayment calendar card based on all bills for the month and displays it on the main interface of electronic device 100. For example, N1=5, as in the example above, all bills for May can be displayed on April 30th. Not limited to the main interface, electronic device 100 can also display it on other pages of the desktop, such as the negative one screen. Users can intuitively and clearly obtain all repayment dates for the month through the repayment calendar card displayed on the main interface or other pages of the desktop, thus rationally arranging their repayment plan and avoiding overdue payments.

[0073] like Figure 1A As shown, five days before the first bill payment due date in May (May 5th) (April 30th), the electronic device 100 can display card 115 (the first card) on its main interface. Card 115 is a repayment calendar card provided exemplary in this application. The five days before the first bill payment due date in card 115, i.e., the aforementioned April 30th, can be referred to as the first date. The aforementioned five days are an exemplary example, and other numbers can also be set, which are not limited in this embodiment.

[0074] As shown in card 115, electronic device 100 can display all dates for May on card 115. Above all dates, the words "Bill - May" can be displayed to indicate that the dates displayed on card 115 represent all dates in May. Furthermore, electronic device 100 can determine all payment due dates for the May bill and mark the payment due dates among all dates displayed on card 115, making it easy for users to clearly see all payment due dates for the month. Based on the payment due dates for the May bill shown in Table 1, the payment due dates marked with circles on card 115 include: May 5th, May 15th, and May 28th.

[0075] Optionally, the electronic device 100 can also mark different bill types on the repayment calendar card. For example, bill types may include: credit card bills, loan (mortgage / car loan) bills, and internet finance bills (such as Alipay Huabei bills, JD.com Baitiao bills, etc.). In this case, the electronic device 100 can use different colors or graphics to mark the repayment date, thereby simultaneously distinguishing the bill type corresponding to each repayment date.

[0076] For example, referring to card 115, electronic device 100 can use a gray circle to mark 5.5 days to indicate that 5.5 days is the repayment date for a credit card bill; electronic device 100 can use a dashed circle to mark 5.15 days to indicate that 5.15 days is the repayment date for a loan; electronic device 100 can use a black circle to mark 5.28 days to indicate that 5.28 days is the repayment date for internet finance loans.

[0077] At this point, any of the above-mentioned types of bills can be called a first-type bill, such as a credit card bill, loan bill, or internet finance bill. Correspondingly, the identifier used to mark this type of bill can be called a first identifier, such as a gray circle, a dotted circle, or a black circle. The information next to the first identifier, such as "credit card," "loan," or "internet finance," can be called first-category information. A bill of a different type than the first-type bill can be called a second-type bill. Correspondingly, the identifier used to mark this type of bill can be called a second identifier, and the information next to the second identifier can be called second-category information.

[0078] The electronic device 100 also features a negative one screen. The negative one screen is the first page located on the left side of the main interface. The electronic device 100 can display the negative one screen based on a user's left swipe operation on the main interface.

[0079] Figure 1B This is the negative one screen of an electronic device 100 provided in this application embodiment.

[0080] The negative one screen can display one or more cards. For example, the negative one screen can display card 121, card 122, and card 123. One card can correspond to one application, displaying one or more services provided by that application. One card can also correspond to multiple applications, displaying one or more services provided by each application.

[0081] For example, card 121 can be a card corresponding to multiple applications. Card 121 may include multiple controls, such as control 121A, control 121B, control 121C, and control 121D. One control corresponds to one service. The two services corresponding to any two controls can be provided by the same application or by two different applications.

[0082] For example, control 121A (“Payment Code”) corresponds to the payment service provided by application A. After detecting a user operation on control 121A, electronic device 100 can display a payment interface including the payment code provided by application A, providing the user with online payment services. Control 121B (“Ride Code”) corresponds to the ride service provided by application B. After detecting a user operation on control 121B, electronic device 100 can display a payment interface including the ride code provided by application B, providing the user with a QR code ride service. Control 121C (“Scan”) corresponds to the image recognition service provided by application C, control 121D (“Payment Code”) corresponds to the online payment service provided by application D, and so on, without further examples.

[0083] For example, card 122 and card 123 can be cards corresponding to a single application.

[0084] For example, card 122 can correspond to a news and information application, and card 123 can correspond to a map navigation application. Card 122 can display the day's trending news terms pushed by the news and information application. Card 123 can display one or more controls (such as "Go Home" control, "Go to Office" control, "Ride" control) to allow users to quickly access navigation, travel, and other services provided by the map navigation application.

[0085] refer to Figure 1B Five days before the first bill payment due date in May (May 5th) (April 30th), electronic device 100 can also display a payment calendar card (card 115) on the negative one screen. In this way, the payment calendar card serves as a reminder without taking up display area on the main interface or affecting the display area of ​​application icons on the main interface.

[0086] In one possible implementation, card 115 can also be displayed on both the negative one screen and the main interface.

[0087] The electronic device 100 can set the display time of the repayment calendar card. After displaying the repayment calendar card for a period of time, the electronic device 100 can turn off the card, that is, stop displaying the card, to ensure the simplicity of the desktop or negative one screen of the electronic device 100 and avoid redundancy.

[0088] For example, electronic device 100 can set the display time of the repayment calendar card to 3 days. During these 3 days, electronic device 100 can keep displaying the repayment calendar card, such as card 115 mentioned above. After these 3 days, electronic device 100 can turn off the repayment calendar card, that is, stop displaying the repayment calendar card. The preset display time of the repayment calendar card, such as 3 days, can be referred to as the fourth duration.

[0089] During the display of the repayment calendar card, the electronic device 100 can detect user actions performed on the repayment calendar card, such as a click. In response to such actions, the electronic device 100 can expand the repayment calendar card to display detailed information for each bill.

[0090] by Figure 1A The example shown is of a repayment calendar card displayed on the main interface. Figure 1C The electronic device 100 can detect the tapping of card 115. In response to the above operation, the electronic device 100 can display... Figure 1D The user interface shown is used to display detailed information for each bill. Figure 1D The user interface shown is also called the first interface of the calendar application.

[0091] like Figure 1DAs shown, the electronic device 100 can display information bars 101, 102, and 103, etc. The list composed of these information bars can be called a schedule list. Information bar 101 can be used to display detailed information about bill 001 with a repayment date of May 5th. Information bar 102 can be used to display detailed information about bill 002 with a repayment date of May 15th. Information bar 103 can be used to display detailed information about bill 003 with a repayment date of May 28th. Taking information bar 101 as an example, users can obtain the source of the bill with a repayment date of May 5th through information bar 101, such as bank C. Furthermore, users can determine the corresponding consumption amount and other information for the bill, so that users can confirm the bill and perform the repayment operation.

[0092] In addition, the details of any bill may include a redirect interface. This redirect interface is also called the first control. The redirect interface is associated with the repayment application corresponding to the bill. After detecting a user operation on the redirect interface, the electronic device 100 can display the repayment interface provided by the associated repayment application for the user to perform the repayment operation.

[0093] For example, refer to Figures 1E-1F The electronic device 100 can detect user actions performed on the information bar 101. In response to this action, the electronic device 100 can expand the information bar 101 to display all bill information for the corresponding bill. The bill schedule shown in the information bar 101 can be referred to as the first schedule. At this time, the electronic device 100 can also display control 124. Control 124 is also called a jump interface, i.e., the first control. The electronic device 100 can detect user actions performed on control 124, and in response to this action, the electronic device 100 can display the repayment interface provided by the repayment application associated with the aforementioned bill, as shown in the reference. Figure 1G .

[0094] like Figure 1G As shown, the repayment interface displays billing information such as the repayment amount, transaction details, and repayment method. The repayment interface also includes control 125. After confirming the billing information and repayment method, the user can click control 125 to make the repayment. Upon detecting this operation, the electronic device 100 can send a repayment instruction to the third-party platform (bank, internet finance institution, etc.) indicated by the repayment method to complete the repayment operation. Understandably... Figure 1G This is merely an illustrative user interface for providing repayment services and should not be construed as limiting the embodiments of this application.

[0095] refer to Figure 1H In some embodiments, in the display Figure 1D Following the user interface shown, the electronic device 100 can detect user actions performed on control 117. Control 117 is also referred to as a second control. (See reference) Figure 1IIn response to the above operations, the electronic device 100 can display a window 126 with multiple tabs. These tabs may include, for example, "Meetings," "Study," and "Entertainment." Each tab corresponds to a type of scheduled activity. Based on the currently selected tab, the electronic device can display the corresponding type of scheduled activity in the calendar for that month. For example, as... Figure 1D As shown, after selecting the repayment label, the electronic device can mark the dates in the May calendar where repayments are scheduled.

[0096] After displaying window 126, refer to Figure 1I The electronic device 100 can detect a user action of selecting all tags. In response to this action, the electronic device 100 can mark the dates in the May calendar where various events are scheduled. (Reference) Figure 1J After selecting all tags, a small dot will appear in the lower right corner of the date May 1st, a triangle will appear in the lower right corner of the date May 2nd, and a five-pointed star will appear in the lower right corner of the date May 7th, etc., to indicate that the user needs to pay attention to the above dates. The aforementioned small dot, triangle, and five-pointed star marks can be referred to as third-party identifiers.

[0097] Furthermore, based on the information displayed in information bar 127, users can determine that May 1st is Labor Day; based on the information displayed in information bar 128, users can determine that there is a meeting they need to attend on May 2nd; and based on the information displayed in information bar 129, users can determine that there is a movie they have booked on May 7th.

[0098] In this way, when a month includes a large number of different types of schedules, in order to make it easier for users to obtain the schedule information of the month more clearly, the electronic device 100 can selectively display each schedule in the calendar of the month according to the schedule type, thereby improving the user experience.

[0099] When the repayment date is approaching on any repayment date in the repayment calendar card, the electronic device 100 can display a repayment reminder card (second card) for the corresponding bill on that repayment date, further reminding the user to make the repayment and avoid overdue payment.

[0100] For example, electronic device 100 may start displaying a payment reminder card for the bill corresponding to the payment due date 3 days before the due date. Figure 2A This is the user interface for displaying repayment reminder cards provided in this application embodiment. For example... Figure 2A As shown, electronic device 100 can begin displaying card 211 three days before the repayment date of May 5th (May 2nd). Card 211 can be referred to as the repayment reminder card for bill 001 corresponding to the repayment date of May 5th. In the example above, the repayment date of May 5th can be referred to as the second date; three days before the repayment date of May 5th, i.e., May 2nd, can be referred to as the third date; and bill 001 is the first bill.

[0101] In the scenario exemplified in this application embodiment, the time when the repayment reminder card is triggered (May 2nd) falls within the preset display time range of the repayment calendar card (April 30th to May 2nd), such as... Figure 2A As shown, the electronic device 100 can independently display a repayment calendar card (e.g., card 115) and a repayment reminder card (e.g., card 211). Specifically, after entering May, the words "Bill - May" can be removed from all dates on card 115 to simplify the card content.

[0102] refer to Figure 2B In other embodiments, when the display times of the repayment reminder card and the repayment calendar card overlap, the electronic device 100 may display only the repayment reminder card and stop displaying the repayment calendar card, even if it is currently within the preset display time range of the repayment calendar card.

[0103] Figure 2A The method of displaying both the repayment calendar card and the repayment reminder card simultaneously, as shown, is called tiled display. When tiled, users can view both the repayment calendar card and the repayment reminder card at the same time.

[0104] refer to Figure 2C In some embodiments where the repayment calendar card and repayment reminder card are displayed independently, the electronic device 100 can also display the repayment calendar card and repayment reminder card in a stacked manner to reduce the display area and save display resources. When stacked, a user can only view one card at a time; that is, the user cannot view both the repayment calendar card and the repayment reminder card simultaneously. In this case, the electronic device 100 can scroll through the repayment calendar card and repayment reminder card so that the user can access all the content of both cards. Optionally, the electronic device 100 can also support the user manually switching the currently displayed repayment reminder card, for example, by swiping up or down to switch between different cards, so that the user can more quickly and conveniently access the card they want to view.

[0105] by Figure 2B The user interface shown is an example of a repayment reminder card. Figure 2B As shown, card 211 can display information such as the bill issuer (e.g., "Bank C"), amount, payment due date ("May 5th"), and a countdown to the payment due date ("Payment within 3 days") for the user to confirm the bill.

[0106] Card 211 also includes controls 212 (also known as the "Paid" control) and 213 (also known as the "Go to Pay" control). Control 213 is the same as... Figure 1F The control shown is 124. The aforementioned "Repay" control is also called a third-party control. Users can perform the repayment operation through control 213. (See reference) Figures 3A-3BThe electronic device 100 can detect user operations applied to the control 213. In response to the above operations, the electronic device 100 can directly display... Figure 3B The repayment interface shown provides users with convenient repayment services. It displays information directly without showing any other content in the center. Figure 3B The repayment interface shown is the same Figure 1G The repayment interface shown here will not be described in detail here.

[0107] After successful repayment confirmation, the electronic device 100 can update the repayment reminder card. (Reference) Figure 3C The electronic device 100 can display card 215 (the third card). Card 215 may include an identifier 216, also known as a "paid" identifier (the fourth identifier). In this way, the electronic device 100 can remind the user that the bill has been processed through the "paid" identifier. Card 215 is also called a paid card.

[0108] The electronic device 100 can display the repaid card for a period of time, such as 2 hours (second duration). The above-mentioned period of time can be set based on experience. After the above-mentioned period of time ends, the electronic device 100 can turn off the card 215 to save display area on the main interface and avoid redundancy.

[0109] In some embodiments, when a user is detected passing through Figure 3B After completing the repayment on the shown repayment interface, the electronic device 100 will receive a text message / notification from the bill issuer confirming the repayment. Through this text message / notification, the electronic device 100 can automatically determine the bill corresponding to card 211, i.e., bill 001 with a repayment date of May 5th, and confirm successful repayment. In other embodiments, when the electronic device 100 cannot determine whether the repayment was successful via text message / notification, the electronic device 100 can determine whether the repayment was successful via control 212. The user then... Figure 3B After completing the repayment on the shown repayment interface, the user can click control 212. Upon detecting this user action, the electronic device 100 can also confirm that bill 001 has been successfully repaid.

[0110] In some embodiments, after confirming successful repayment, the electronic device 100 may directly close the original repayment reminder card 211 without updating the repayment reminder card 211 to the form shown in card 215.

[0111] In some scenarios, after the repayment reminder card is displayed, users do not immediately make the repayment and may forget about the bill over time. If the user has not made the repayment by the due date, the corresponding bill will be overdue. The "end of a certain day" mentioned in this application refers to after 23:59 on that day.

[0112] In this embodiment, the electronic device 100 may display a repayment reminder card for a period of time after the due date, reminding the user to make the repayment as soon as possible to avoid greater losses. After the aforementioned period of time ends, the electronic device 100 may delete the repayment reminder card. The repayment reminder card after the due date is also called an overdue reminder card.

[0113] refer to Figure 3D Upon overdue payment, the electronic device 100 can display card 217, replacing the original repayment reminder card 211. Card 217 is an example of providing an overdue reminder card (fourth card) in this application embodiment. Card 217 may include a mark 218, also known as an "overdue" mark (fifth mark). Users can determine that the bill is overdue through the "overdue" mark in card 217.

[0114] In this embodiment, the card 217 may also include a control 213 ("Go to Repayment" control). After detecting a user operation on the control 213, the electronic device 100 may display a repayment interface to provide the user with convenient repayment services, so that the user can complete the repayment operation as soon as possible and avoid greater losses or more serious consequences.

[0115] Similarly, the electronic device 100 can also set the display time (third duration) of the overdue reminder card. This display time can be set based on experience. After the preset display time ends, the electronic device 100 can turn off the overdue reminder card to save display area on the main interface and avoid redundancy. For example, the electronic device 100 can set the display time of the overdue reminder card to 2 days. After 2 days of overdue payment, the electronic device 100 can turn off the repayment reminder card.

[0116] refer to Figures 3A-3D As shown, when the next payment due date is approaching, the electronic device 100 can display payment reminder cards, paid-up cards, overdue reminder cards for other bills, and switch and close each card in the same way as described above.

[0117] refer to Figure 3E Approaching the second payment due date of May, May 15th, electronic device 100 can similarly display a payment reminder card (card 221) for the corresponding bill due on May 15th, starting three days in advance. Card 221 is the payment reminder card for bill 002 with a payment due date of May 15th. Users can obtain information such as the bill issuer, amount, payment due date, and countdown timer for bill 002 from card 221. Card 221 may also include "Paid" and "Pay Now" controls. (See reference) Figure 3FWhen a user action is detected on the "Paid" control, the electronic device 100 can display the paid card 222, or the electronic device 100 can directly close the card 221. When a user action is detected on the "Pay Now" control, the electronic device 100 can display the repayment interface to provide users with convenient repayment services.

[0118] Similarly, refer to Figure 3G After the payment is overdue, the electronic device 100 can display an overdue reminder card 223. The user can use the card 223 to confirm that the bill 002 corresponding to the repayment date of May 15th is overdue, and thus complete the repayment operation as soon as possible to avoid greater losses or more serious consequences.

[0119] In some scenarios, electronic device 100 may receive multiple bills with the same due date, or multiple bills with adjacent due dates. In this case, electronic device 100 can independently display the payment reminder card for each bill. For example, electronic device 100 may receive bill 001 from bank C with a payment date of May 5th, and also bill 004 from bank G with a payment date of May 5th. On May 2nd, electronic device 100 may display the payment reminder card for bill 001 (e.g., card 211 mentioned above), and simultaneously, electronic device 100 may also display the payment reminder card for bill 004, which will not be elaborated further here.

[0120] In some embodiments, when multiple bill payment reminder cards exist simultaneously, the electronic device 100 may refer to Figure 2A The tiled display method shown above displays the payment reminder cards for the aforementioned multiple bills.

[0121] In other embodiments, when multiple bill payment reminder cards exist simultaneously, the electronic device 100 may also refer to... Figure 2C The stacked display method shown reduces the display area and saves display resources by showing multiple bill payment reminder cards. Similarly, when stacked, a user can only view one of the multiple payment reminder cards at a time. The electronic device 100 can scroll through these payment reminder cards so the user can browse them. The electronic device 100 also allows the user to manually switch the currently displayed payment reminder card for faster and more convenient access to the desired card.

[0122] The billing date (i.e., the date the user receives the bill SMS / notification) and the payment due date differ between different bill issuers. Therefore, in some scenarios, even after the monthly payment calendar card is turned off, that is, after the bill calendar card displayed on the desktop or negative one screen disappears, the electronic device 100 can still receive the new bill for the current month.

[0123] For example, refer to Figure 1A After displaying the May payment calendar card (card 115), electronic device 100 receives a new bill via SMS / notification, designated as bill 005 (second bill). The payment due date for bill 005 is also in May; for example, electronic device 100 receives bill 005 on May 20th (fourth date). The billing information for bill 005 can be seen in Table 2 below: Table 2

[0124] refer to Figure 4 Upon receiving bill 005, the electronic device 100 can first display card 411 (the fifth card). Card 411 is also known as the billing reminder card. Card 411 can display information such as the issuer, amount, and due date of the newly received bill 005. It should be noted that for credit card bills mentioned above, the billing reminder card can be displayed first upon receiving the billing information or notification.

[0125] At the same time, electronic device 100 can redisplay the May repayment calendar card. For example... Figure 4 As shown, electronic device 100 can display card 412. As shown on card 412, the payment due date for this month also includes the newly added May 25th, marked with a black circle. At this time, the user can see the newly received bill through the updated card 412 and directly and conveniently obtain the payment due date of the new bill. Furthermore, when redisplaying the payment calendar card for the month, the redisplayed payment calendar card may no longer display the payment due dates of already processed bills. As shown on card 412, the already processed payment due dates May 5th and May 15th are no longer indicated on card 412.

[0126] Electronic device 100 may display a single reminder card for a period of time (the fifth duration). This period generally does not exceed one day. For example, electronic device 100 may display it for two hours. After two hours, electronic device 100 may stop displaying the single reminder card. Optionally, electronic device 100 may also determine whether the user has read the card through methods such as eye gaze recognition. Upon detecting that the card has been read, electronic device 100 may immediately stop displaying the single reminder card to avoid redundancy and ensure the simplicity of the content displayed on the desktop.

[0127] Then, refer to Figures 3A-3D As shown, electronic device 100 can also display a payment reminder card for bill 005 when the payment due date of bill 005 is approaching; display a payment card for bill 005 after successful payment confirmation; and display an overdue reminder card for bill 005 after confirmation of overdue payment. These details will not be elaborated here.

[0128] In some scenarios, when a new payment due date is received for a bill within the current month, the payment calendar card is still displayed on the main interface. For example, electronic device 100 may receive a new bill within the display time range of the payment calendar card (April 30th - May 2nd). In this case, electronic device 100 can directly update the currently displayed payment calendar card, marking the payment due date of the newly received bill in the payment calendar card.

[0129] Table 3 shows the reminder stage for credit card bills provided in the embodiments of this application.

[0130] Table 3

[0131] Electronic device 100 can display a single reminder card based on SMS / notification detection of bill generation, and subsequently create and display such a card. Figure 4 The card 411 shown; when the repayment date is approaching (the repayment period), the electronic device 100 can display a repayment reminder card, for example... Figure 3A Card 211 shown Figure 3E The card 221 shown; during the repayment phase, the electronic device 100 can display the repaid card, for example... Figure 3C Card 215 shown Figure 3F Card 222 shown; when the card is overdue, the electronic device 100 can display the overdue card, for example Figure 3D Card 217 shown Figure 3G Card 223 is shown.

[0132] In some embodiments, different types of bills correspond to different reminder stages. In this case, the electronic device 100 can set reminder cards corresponding to each stage of the various types of bills.

[0133] For example, in a loan transaction, the electronic device 100 can also receive other reminders about the bill from the bill issuer. In this case, the electronic device 100 can display a card that includes the aforementioned other reminders to provide more granular, real-time alerts.

[0134] Table 4 shows the reminder stage of the loan bill provided in the embodiments of this application.

[0135] Table 4

[0136] For loans, after a successful loan application, the electronic device 100 will receive a notification indicating successful loan application. At this time, the electronic device 100 will display a successful application card based on the notification. The successful application card will display information such as the loan lender (i.e., the bill issuer), loan amount, and disbursement date. After the bill issuer sends the funds to the user's account, the electronic device 100 will receive a successful loan disbursement notification. At this time, the electronic device 100 will display a successful loan disbursement card based on the notification. The successful loan disbursement card will display information such as the bill issuer, loan amount, and repayment date. Other notification stages are similar to those for credit card statements and will not be elaborated here.

[0137] In internet finance consumption, some internet finance transactions, such as Alipay Huabei and JD Baitiao, can refer to the reminder rules for credit cards; others, such as Alipay Jiebei and JD Jintiao, can refer to the reminder rules for loans. These will not be elaborated here.

[0138] In some embodiments, the electronic device 100 can also support users adding new bills. In this way, bills that the electronic device 100 cannot obtain via notification / SMS can be added to the repayment calendar card through the user's action, making the bills in the repayment calendar card more comprehensive and allowing the user to arrange repayments more effectively.

[0139] refer to Figure 5A Card 115 may also include control 511 (fourth control). Control 511 can be used to create a new repayment schedule. Electronic device 100 can retrieve the user's bill based on the repayment schedule created by the user.

[0140] refer to Figure 5B The electronic device 100 can detect user operations applied to the control 511. In response to the above operation, the electronic device 100 can display... Figure 5C The user interface shown is also called the new schedule interface (third interface).

[0141] like Figure 5C As shown, the new schedule interface can include items such as title, location, and time. Users can set these items, and the electronic device can respond to the user's settings and record the relevant information of the new schedule. In addition, this interface may also include item 512, also known as a label. The display is controlled via control 511 upon detection. Figure 5C After the newly added schedule interface is displayed, the electronic device 100 can set the label to "Repayment" by default. Then, the electronic device 100 can detect the user operation on the control 513. In response to the above operation, the electronic device 100 can save the schedule information recorded on the current interface (e.g., [Bank G] Repayment..., date May 25, label "Repayment").

[0142] Electronic device 100 can determine that the user's newly added schedule is a billing schedule based on the "Repayment" label. Then, electronic device 100 can generate a bill (third bill) based on the schedule information in the aforementioned billing schedule. This bill is a bill added by the user himself.

[0143] Electronic device 100 can extract billing information such as the issuer and amount from items like the title and location using keyword extraction and semantic recognition, and determine the user-set schedule as the payment due date. Then, electronic device 100 can determine the corresponding month for the bill based on the payment due date, i.e., in which month's payment calendar card it should be displayed. For example, electronic device 100 can confirm that the user-added bill is a May bill based on the date May 25th. At this point, electronic device 100 can update the currently displayed payment calendar card, marking the payment due date of the new bill, such as May 25th, in the payment calendar card.

[0144] refer to Figure 5D Electronic device 100 can update card 115 to card 116. Compared to card 115, the date May 25th in card 116 can carry a bold gray circle style (sixth identifier). The bold gray circle style can be used to indicate bills added by the user without specifying a bill type, i.e., other categories. At this time, through card 116, the user can intuitively obtain all the repayment dates for the month, including the repayment dates of bills added by the user. Understandably, when the user specifies the bill type during the creation of the schedule, electronic device 100 can use the corresponding graphic or color identifier to mark the repayment date.

[0145] For user-added bills, when the electronic device 100 expands card 116 to display more bill information, the electronic device 100 may display the detailed information of the user-added bills. For example, the electronic device 100 may detect an action of clicking on card 116. In response to the above action, the electronic device 100 may refer to... Figure 1D The user interface shown displays more information about all current bills. At this point, the "all bills" list includes bills added by the user.

[0146] Understandably, according to the display rules of the repayment calendar card: it is displayed for a period of time (e.g., 3 days) and then turned off. After the repayment calendar card is turned off, the electronic device 100 can allow users to access the above-mentioned device through entry points provided by other applications such as calendar applications and memo applications. Figure 5C The newly added schedule interface is shown. At this point, electronic device 100 will not default to selecting the "Repayment" tab, but will instead select other tabs, such as "Meeting," "Study," or "Entertainment." Then, refer to... Figures 5E-5GIf a user needs to add a bill reminder and wants the payment due date of the added bill to be displayed in the payment calendar card, the user needs to click the label (item 512) control and select the "Payment" label to create a new bill schedule. Similar to adding a bill manually via control 511, after successfully creating a new bill schedule, the electronic device 100 can update the payment calendar card for that month, displaying the payment due date of the newly added bill. If the bill calendar card on the desktop has disappeared, it can be re-displayed on the desktop.

[0147] In some embodiments, for user-added bills, the electronic device 100 may automatically continue to mark the payment due date of the bill in subsequent payment calendar cards. In other embodiments, the electronic device 100 may also only display the payment due date of the bill in the month specified by the user. After the month specified by the user ends, the electronic device 100 stops marking the payment due date of the bill.

[0148] Furthermore, the electronic device 100 can determine whether the aforementioned bill is periodic based on tags or notes added by the user. For example, if a tag or note in a user-added bill indicates that the bill is an internet installment payment bill, the electronic device 100 can automatically continue to mark the repayment date of the aforementioned bill in subsequent repayment calendar cards. If a tag or note in a user-added bill indicates that the bill is a loan between friends, the electronic device 100 will no longer continue to mark the repayment date of the aforementioned bill after the end of the month specified by the user.

[0149] Generally, users' spending habits are relatively fixed and do not change in a short period of time. This means that, in most cases, users' monthly repayment dates are basically the same. In this case, users can determine which dates are repayment dates without the need for a repayment calendar card reminder.

[0150] Therefore, for the above scenarios, in some embodiments, the electronic device 100 can calculate all of a user's bills for each month. When all the bills for a month are completely consistent with all the bills for several consecutive months, the electronic device 100 may not display a repayment calendar card. Complete consistency includes the same number of bills, the same issuer, and the same repayment date. When all the bills for a month are not completely consistent with all the bills for the previous month, the electronic device 100 may display a repayment calendar card for that month. Inconsistency includes different numbers of bills, and / or, one or more bills having different issuers, and / or, one or more bills having different repayment dates.

[0151] refer to Figure 5HIn clauses (a) to (c), electronic device 100 may display a May repayment calendar card on April 30th with the first repayment date being May 5th, showing all repayment dates for May as the 5th, 15th, and 28th of that month; it may display a June repayment calendar card on May 31st with the first repayment date being June 5th, showing all repayment dates for June as the 5th, 15th, and 28th of that month; and it may display a July repayment calendar card on June 30th with the first repayment date being July 5th, showing all repayment dates for July as the 5th, 15th, and 28th of that month. When all repayment dates for August continue to be the 5th, 15th, and 28th, electronic device 100 may no longer display the August repayment calendar card. (See reference...) Figure 5H (d)

[0152] After August, if the bill received for the current month differs from that of the previous month, the electronic device can display the bill calendar card again.

[0153] refer to Figure 3A After displaying the repayment reminder card (i.e., card 211), the electronic device 100 can detect the user operation on the control 213, and based on the operation, the electronic device 100 can automatically jump to and display the repayment interface. In this process, the electronic device 100 first needs to determine which application's repayment service to use to perform the repayment operation, and then the electronic device 100 displays the repayment interface provided by that application.

[0154] The application program that provides repayment services and performs repayment operations, as determined by electronic device 100, can be referred to as the target application. In this embodiment, electronic device 100 can determine the target application according to a preset mapping relationship. The above mapping relationship is determined based on common experience and user habits. The above mapping relationship is as follows: S1. Identify the official online payment application of the bill issuer as the target application; S2. When multiple official online payment applications are installed, the official online payment application with the highest user frequency is identified as the target application; when no official online payment application is installed, other online payment applications with higher user frequency are identified as the target application. These other online payment applications are typically applications that aggregate payment capabilities from multiple parties, such as Alipay and UnionPay QuickPass.

[0155] For example, taking a bill issued by Bank C as shown in card 211 as an example, electronic device 100 first determines Bank C's official online payment application APP1 based on Bank C. When APP1 is installed on electronic device 100, electronic device 100 can determine APP1 as the target application and then display the repayment interface provided by APP1. Bank C's official online payment application APP1 may include multiple applications, such as APP1-1 and APP1-2. In this case, electronic device 100 can determine the official online payment application that the user uses more frequently, such as APP1-1, as the user's target application. When electronic device 100 does not have APP1-1 or any of the other official online payment applications installed, electronic device 100 can obtain other online payment applications installed on its device, such as Alipay and UnionPay QuickPass as mentioned above. Among them, when multiple other online payment applications are detected, electronic device 100 can determine the other online payment application that the user uses more frequently, such as Alipay, as the target application.

[0156] Furthermore, the electronic device 100 can also determine a mapping relationship suitable for a certain type of bill based on different bill types.

[0157] For example, for credit card or internet finance bills, electronic device 100 can determine the target application for providing repayment services according to the above mapping relationship. For loan bills, electronic device 100 can determine the target application for providing repayment services according to the following mapping relationship: S3. Identify the official online payment application of the user's main income bank as the target application; S4. When multiple official online payment applications from major revenue banks are installed, identify the official online payment application that users use more frequently as the target application; when no official online payment application from major revenue banks is installed, identify other online payment applications that users use more frequently as the target application.

[0158] The primary income bank manages the user's income. Electronic device 100 allows users to set their primary income bank. Optionally, with permitted permissions, electronic device 100 can also track income and expenditure for each account in installed financial applications, determining the bank corresponding to the account with the highest income as the user's primary income bank.

[0159] For example, in a scenario where a user's primary income source is bank C, upon receiving a loan repayment statement from bank C, electronic device 100 can identify bank C's official online payment application APP1 as the target application. In a scenario where a user's primary income source is bank D, upon receiving a loan repayment statement from bank C, electronic device 100 can identify bank D's official online payment application APP2 as the target application. When electronic device 100 does not have an official online payment application from its primary income source bank, it can identify other frequently used online payment applications that are installed as the target application; this will not be elaborated further here.

[0160] Based on any of the mapping relationships described above, after detecting a user action on the "Pay Now" control, the electronic device 100 can automatically determine the target application associated with the current bill, and then display the repayment interface provided by the target application to provide repayment services to the user. For example, refer to... Figures 3A-3B When bank C is installed on electronic device 100, after detecting a user action by clicking control 213, electronic device 100 can determine that the target application associated with the current bill is APP1. Therefore, electronic device 100 can display the repayment interface provided by APP1. The repayment interfaces provided by different target applications often differ, and are not listed here.

[0161] Optionally, the electronic device 100 may also allow users to modify the mapping relationship between the bill issuer and the target application providing the repayment service. Figures 6A-6G This is a set of user interfaces for setting mapping relationships provided in the embodiments of this application.

[0162] Figure 6A This is the settings interface of the electronic device 100 provided in this application embodiment. The settings interface may include multiple settings options. For example... Figure 6A As shown, the above-mentioned multiple setting options may include a smart assistant option. After detecting a user action on the smart assistant option, the electronic device 100 may display... Figure 6B The user interface shown is also called the Smart Assistant settings interface. The Smart Assistant settings interface includes several settings options. These options may include YOYO suggestions. Upon detecting a user action on the YOYO suggestions option, the electronic device 100 can display... Figure 6C The user interface shown is also known as the YOYO suggested settings interface.

[0163] like Figure 6C As shown, YOYO suggests that the settings interface may include a repayment assistant option. This repayment assistant option is used to set up repayment reminder cards. Upon detecting a user action on the repayment assistant option, the electronic device 100 may display... Figure 6DThe user interface shown is also called the repayment reminder card settings interface. This interface may include control 611. Control 611 can be used to turn the repayment reminder card on / off. For example, refer to Figure 3A , Figure 3E When the repayment reminder card is enabled, the electronic device 100 can display the corresponding repayment reminder card, such as card 211 or card 221, as the repayment date approaches. Conversely, when the repayment reminder card is disabled, the electronic device 100 will not display the repayment reminder card as the repayment date approaches.

[0164] The repayment reminder card settings interface also includes control 612. Control 612 can be used to set the target application. After detecting a user operation on control 612, the electronic device 100 can display... Figure 6E The user interface shown is also called the repayment app settings interface. The repayment app settings interface can be used to set the mapping relationship between the bill issuer and the repayment app (i.e., the target app) that performs the repayment operation.

[0165] like Figure 6E As shown, for example, if electronic device 100 has four financial applications installed: APP1 (the official online payment application of bank C), APP2 (the official online payment application of bank D), APP3 (another online payment application), and APP4 (another online payment application), and the application used by the user is APP1, then electronic device 100 can determine, based on common experience and user habits, the repayment application matched with bank C is APP1; the repayment application matched with bank D is APP2; the repayment application matched with bank G is APP3 (another online payment application used by the user more frequently), and so on. These will not be listed one by one here.

[0166] Based on this, users can also click Figure 6E The various settings options shown allow you to change the repayment app corresponding to the bill issuer. For example, refer to... Figures 6E-6G The electronic device 100 can detect user actions by clicking the Bank D option. In response to this action, the electronic device 100 can display window 613, which displays financial applications installed on the electronic device 100 that can provide repayment services, such as APP1, APP2, APP3, and APP4. The electronic device 100 can detect user actions by clicking APP3. In response to this action, the electronic device 100 can change the matching repayment application with Bank D from the original APP2 (Bank D's official online payment application) to APP3 (another online payment application selected by the user). Thus, when the user action of clicking the "Go to Repay" control in the corresponding Bank D repayment reminder card is detected, the electronic device 100 can access the repayment interface provided by APP3 and provide repayment services to the user.

[0167] Not limited to repayment bills issued by banks / internet finance companies, electronic devices can also receive daily utility bills such as water, electricity, and gas via SMS / notification.

[0168] In one embodiment, the electronic device 100 can distinguish between repayment bills and payment bills. In this case, the electronic device 100 can also separately compile the user's utility payment bills and generate a payment calendar card based on all of the user's utility payment bills. The payment calendar card only marks the payment date of the payment bill. The electronic device 100 can display / disable the payment calendar card according to the aforementioned display / disable rules for repayment calendar cards.

[0169] Figure 7A This is a user interface provided in this application embodiment that simultaneously displays the repayment calendar card and the payment calendar card. (Reference) Figure 7A On May 1st (five days before the first payment date in May), the electronic device 100 can also display card 711 on its main interface. Card 711 can be called a payment calendar card. Card 711 can display the payment dates for all of the user's payment bills. Similarly, different graphics or colors can be used on card 711 to distinguish different types of payment bills.

[0170] In conjunction with the foregoing embodiments, on May 1st, the electronic device 100 will also simultaneously display a repayment calendar card. In the aforementioned embodiments that distinguish between repayment bills and payment bills, when setting multiple cards such as repayment calendar cards and payment calendar cards, the electronic device 100 can display these multiple calendar cards in a tiled display manner. Similarly, the electronic device 100 can also display these multiple cards in a stacked display manner to reduce the display area and save display resources. Further details will not be elaborated here.

[0171] refer to Figures 3A-3D The method shown allows the electronic device 100 to display detailed billing information for any payment date as it approaches, providing users with a fast payment service. In this embodiment, the time range from N days prior to a given day to that day can be referred to as "approaching a certain day."

[0172] refer to Figure 7B For example, when the electricity bill payment due date is approaching on May 6th, electronic device 100 may display card 712. Card 712 may be referred to as a payment reminder card. The payment reminder card may display detailed bill information, including but not limited to: payee (e.g., "XX City Power Supply Bureau"), amount (e.g., "300.00 yuan"), payment date (e.g., "due on May 5th"), etc. The user can verify the bill through the above bill information and determine whether to perform the payment operation.

[0173] Card 712 includes a "Paid" control and a "Go to Pay" control. When a user action is detected on the "Go to Pay" control, the electronic device 100 can display... Figure 7C The payment interface shown is as described above. The process of displaying the payment page on electronic device 100 is similar to the process of displaying the repayment page described above, and will not be repeated here.

[0174] like Figure 7C As shown, when making a payment, the user first needs to enter account information such as the account number on the payment interface. In existing technology, users need to either memorize and enter the account number one by one; or open a text messaging application, search for payment reminder messages, and then copy the account number from those messages; or use a control provided on the payment interface, such as control 721, to retrieve the account number in real time. This increases the difficulty of payment for users and results in a poor user experience.

[0175] In this embodiment of the application, after detecting a user's action to start filling in account information, i.e., after activating the keyboard, the electronic device 100 can obtain account information such as the account number from the payment bill corresponding to the payment reminder card and display it in the candidate area of ​​the keyboard. For example... Figure 7C As shown, the electronic device 100 can display the account number, for example, 09500500008503288, in area 722 of the keyboard. The user can then directly click on the account number displayed in area 722. (Reference) Figure 7D Upon detecting a user action in area 722, the electronic device 100 automatically fills in the household number in the input field, eliminating the need for manual input by the user. This allows users to quickly and conveniently complete the payment information.

[0176] Understandably, before confirming payment, Figure 7C The payment interface shown may also include other account information that the user needs to fill in, such as the account name. At this time, the electronic device 100 can sequentially display the account information obtained from the payment bill in the candidate area of ​​the keyboard for the user to quickly fill in.

[0177] In this way, while ensuring account security, electronic devices can also reduce the difficulty of operation and bring users a more convenient payment experience.

[0178] In some embodiments, the electronic device 100 may not distinguish between repayment bills and payment bills. In this case, the electronic device 100 can directly mark the payment date of the aforementioned utility payment bill in the repayment calendar card. As any repayment / payment date approaches, the electronic device 100 can display the detailed bill information of the payment bill corresponding to that repayment / payment date, i.e., display the corresponding repayment reminder card / payment reminder card, thereby providing users with a fast payment service.

[0179] exist Figures 7A-7D In the embodiment shown, Figure 7A May 1st can be referred to as the first date, card 711 can be referred to as the first card, card 712 can be referred to as the second card, payment date May 5th can be referred to as the second date, the payment bill corresponding to card 712 can be referred to as the first bill, and the "Go to Payment" control in card 712 can be referred to as the third control.

[0180] Figure 8 This is a schematic diagram of the structure of the billing management application provided in the embodiments of this application. Figure 8 As shown, the billing management application may include a data acquisition module, a card management module, and a callback interface.

[0181] The data acquisition module can be used to retrieve bills. Electronic device 100 can retrieve bills via SMS and / or notification.

[0182] In the method of obtaining a bill via notification, firstly, the electronic device 100 can identify all applications providing financial services (i.e., financial applications) installed on the device through application tags. Then, the electronic device 100 can obtain notifications from these financial applications and determine, through methods such as keyword extraction and semantic recognition, whether the notification includes billing information such as the bill issuer, due date / payment date, and amount. Obtaining a set of billing information through a single notification by the electronic device 100 can be considered as obtaining a single bill.

[0183] Similarly, after receiving a text message, electronic device 100 can determine whether the message includes billing information such as the bill sender, payment / repayment date, and amount through methods such as keyword extraction and semantic recognition. Obtaining a set of billing information from a single text message can also be considered as obtaining a single bill.

[0184] refer to Figures 5B-5D The user interface diagram shown indicates that the data acquisition module can also retrieve bills based on the user's creation of a repayment schedule.

[0185] The data acquisition module categorizes bills based on their payment due date / payment date, and compiles statistics for all bills with the same payment due date / payment date within the same month. On the first bill payment due date of the month, the data acquisition module sends all bills for that month to the card management module. The card management module then generates a bill calendar card for that month based on all the bills.

[0186] Then, the card management module can control the display / display of the bill calendar card according to preset rules. For example, the card management module can keep the bill calendar card displayed for the first 3 days of the first bill of a preset month; after these 3 days, the card management module can turn off the bill calendar card.

[0187] In some embodiments, the card management module can divide a monthly bill into a repayment bill and a payment bill based on repayments and payments. The card management module can generate a repayment calendar card for the repayment bill, for example... Figure 7A The card shown is 115. The repayment calendar card only marks the repayment date for this month. Simultaneously, the card management module can generate a payment calendar card for each payment bill, for example... Figure 7A The card shown is 711. The payment calendar card only marks the payment date for this month. The repayment calendar card and payment calendar card are collectively referred to as the billing calendar card. The card management module can display these repayment calendar cards and payment calendar cards in a tiled or stacked manner.

[0188] In some embodiments, the card management module may not distinguish between repayment bills and payment bills. The card management module can generate and display a master bill calendar card (also referred to as the first card). This card marks both the repayment date and the payment date for the current month. In this case, the marker used to mark the repayment date can be called the first identifier, and the marker used to indicate the payment date can be called the second identifier. Correspondingly, the bill calendar card can also display application repayment and payment instructions, indicating which identifier corresponds to the repayment and which corresponds to the payment.

[0189] After displaying the bill calendar card, the data acquisition module can obtain the bill for the corresponding month on the currently displayed bill calendar card via SMS / notification / user-created repayment schedule. At this point, the data acquisition module can immediately send the bill to the card management module. The card management module can then update the currently displayed bill calendar card based on the new bill.

[0190] In some scenarios, the data acquisition module obtains the new bill within the time frame for displaying the bill calendar card, such as within 3 days before the first bill of the month. In this case, the card management module can update the currently displayed bill calendar card, marking the newly added payment / due date on it. In other scenarios, the data acquisition module obtains the new bill outside the time frame for displaying the bill calendar card, such as after 3 days before the first bill of the month. In this case, the card management module can redisplay the bill calendar card for that month, displaying an updated card that includes the newly added payment / due date.

[0191] After the updated bill calendar card is re-displayed based on the new bill for a period of time, the card management module can also turn off the bill calendar card to avoid redundant reminders. This period of time can be set based on experience. For example, this period includes 3 days.

[0192] The card management module is also used to control the display / display of bill reminder cards, for example... Figure 2A The repayment reminder card shown is 211. Figure 7B The payment reminder card shown is 712.

[0193] The card management module can determine all repayment and payment dates for the month. When approaching any repayment / payment date, such as 3 days before any repayment / payment date, the card management module can generate and display a reminder card based on the corresponding bill for that repayment / payment date.

[0194] In addition to displaying the bill information for the corresponding bill, the bill reminder cards (payment reminder cards and payment reminder cards) also include controls for quickly navigating to the bill processing interface. Each control corresponds to a callback interface. After detecting a user action on the control, the callback interface can retrieve the payment or payment interface from the associated target application.

[0195] The callback interface is also used to return processing results. After completing a repayment or payment operation through the repayment or payment interface provided by the target application, the callback interface can send the repayment result (e.g., repayment successful, repayment failed) or payment result (e.g., payment successful, payment failed) back to the card management module. The card management module can then determine whether to close or update the corresponding repayment reminder card or payment reminder card based on the above processing results.

[0196] Once the above processing result indicates successful repayment / payment, the card management module can switch the repayment / payment reminder card to the corresponding repaid / paid card and turn off the reminder after a certain period. If the repayment / payment due date has passed and no successful repayment / payment has been detected, the card management module can switch the repayment / payment reminder card to the corresponding overdue card to continue reminding the user to handle the matter promptly.

[0197] Figure 9 A schematic diagram of the structure of the electronic device 100 is shown.

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

[0199] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0200] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0201] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0202] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

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

[0204] USB port 130 is a USB standard compliant interface, specifically a Mini USB port, Micro USB port, USB Type-C port, etc. USB port 130 can be used to connect a charger to charge electronic device 100, and can also be used for data transfer between electronic device 100 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as AR devices.

[0205] It is understood that the interface connection relationships between the modules illustrated in the embodiments of the present invention are merely illustrative and do not constitute a structural limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0206] The charging management module 140 receives charging input from the charger. While charging the battery 142, the charging management module 140 can also supply power to the electronic device through the power management module 141.

[0207] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, internal memory 121, display 194, camera 193, and wireless communication module 160, etc.

[0208] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0209] Antennas 1 and 2 are used to transmit and receive electromagnetic wave signals. Mobile communication module 150 can provide solutions for wireless communication applications, including 2G / 3G / 4G / 5G, applied to electronic device 100. The modem processor can include a modulator and a demodulator. Wireless communication module 160 can provide solutions for wireless communication applications, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies, applied to electronic device 100.

[0210] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0211] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0212] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD). The display panel can also be manufactured using organic light-emitting diodes (OLEDs), active-matrix organic light-emitting diodes (AMOLEDs), flexible light-emitting diodes (FLEDs), miniled, microled, micro-OLEDs, quantum dot light-emitting diodes (QLEDs), etc. In some embodiments, the electronic device may include one or N displays 194, where N is a positive integer greater than 1.

[0213] In this embodiment, the electronic device 100 can display information via the display functions provided by the GPU, the display screen 194, and the application processor. Figures 1A-1J , Figures 2A-2C , Figures 3A-3G , Figure 4 , Figures 5A-5H , Figures 6A-6G , Figures 7A-7D The user interface shown.

[0214] Electronic device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0215] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs can enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0216] In this embodiment of the application, the electronic device 100 can use the computing power provided by the NPU to parse the received SMS messages and / or notifications, identify whether they are SMS messages and / or notifications for repayment / payment reminders, and then obtain bill information.

[0217] Internal memory 121 may include one or more random access memory (RAM) and one or more non-volatile memory (NVM).

[0218] Random access memory (RAM) can be directly read and written by the processor 110. It can be used to store executable programs (such as machine instructions) of the operating system or other running programs, as well as user and application data. Non-volatile memory can also store executable programs and user and application data. Executable programs and user and application data can be pre-loaded into the RAM for direct reading and writing by the processor 110.

[0219] In this embodiment of the application, the executable program code and user data of the billing management method described in this embodiment can be stored in non-volatile memory. When implementing the above-described billing management method, the electronic device 100 can load the executable program code and user data from the non-volatile memory into random access memory to implement the billing management function provided by the above-described billing management method.

[0220] The external memory interface 120 can be used to connect to external non-volatile memory, thereby expanding the storage capacity of the electronic device 100. The external non-volatile memory communicates with the processor 110 through the external memory interface 120 to perform data storage functions. For example, music, video, and other files can be stored in the external non-volatile memory.

[0221] Electronic device 100 can implement audio functions through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0222] Pressure sensor 180A is used to sense pressure signals and can convert the pressure signals into electrical signals. In some embodiments, pressure sensor 180A may be disposed on display screen 194. Electronic device 100 may also calculate the position of touch based on the detection signal of pressure sensor 180A.

[0223] A gyroscope sensor 180B can be used to determine the motion posture of the electronic device 100. A barometric pressure sensor 180C is used to measure barometric pressure. A magnetic sensor 180D includes a Hall effect sensor. The electronic device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip cover. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 can detect the opening and closing of the flip cover based on the magnetic sensor 180D. Then, based on the detected opening and closing state of the cover or the flip cover, features such as automatic flip unlocking can be set. An accelerometer sensor 180E can detect the magnitude of the acceleration of the electronic device 100 in various directions (generally three axes). A distance sensor 180F is used to measure distance. A proximity sensor 180G may include, for example, a light-emitting diode (LED) and a photodetector, such as a photodiode. The electronic device 100 emits infrared light outward through the LED. The electronic device 100 uses the photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, electronic device 100 can determine that there is no object nearby. Ambient light sensor 180L is used to sense ambient light intensity. Fingerprint sensor 180H is used to collect fingerprints. Temperature sensor 180J is used to detect temperature.

[0224] Touch sensor 180K, also known as a "touch device," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touchscreen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be located on the surface of electronic device 100, in a different position than display screen 194.

[0225] In this embodiment, the electronic device 100 can detect user operations applied to any area of ​​the screen via a touchscreen composed of a touch sensor 180K and a display screen 194, and then display... Figures 1A-1J , Figures 2A-2C , Figures 3A-3G , Figure 4 , Figures 5A-5H , Figures 6A-6G , Figures 7A-7D The user interface shown allows users to receive bill reminders and complete repayments / payments.

[0226] The bone conduction sensor 180M can acquire vibration signals. Buttons 190 include a power button, volume buttons, etc. The electronic device 100 can receive button inputs and generate key signal inputs related to user settings and function control. The motor 191 can generate vibration alerts. The indicator 192 can be an indicator light, used to indicate charging status, battery level changes, and also to indicate messages, missed calls, notifications, etc. The SIM card interface 195 is used to connect a SIM card.

[0227] The term "user interface (UI)" used in the specification, claims, and drawings of this application refers to the medium through which an application or operating system interacts and exchanges information with the user. It converts the internal form of information into a form acceptable to the user. The user interface of an application is source code written in a specific computer language such as Java or Extensible Markup Language (XML). This source code is parsed and rendered on the terminal device, ultimately presenting user-recognizable content, such as images, text, buttons, and other controls. Controls, also known as widgets, are the basic elements of the user interface. Typical controls include toolbars, menu bars, text boxes, buttons, scroll bars, images, and text. The attributes and content of controls in the interface are defined through tags or nodes, such as in XML. <textview> 、 <imgview> 、 <videoview>Nodes define the controls contained in the interface. A node corresponds to a control or property in the interface, and after parsing and rendering, the node is presented as the content visible to the user. In addition, many applications, such as hybrid applications, often contain web pages within their interfaces. A web page, also known as a page, can be understood as a special control embedded in the application interface. Web pages are source code written in a specific computer language, such as Hypertext Markup Language (HTML), Cascading Style Sheets (CSS), JavaScript (JS), etc. Web page source code can be loaded and displayed as user-readable content by a browser or a web page display component with browser-like functionality. The specific content contained in a web page is also defined through tags or nodes in the web page source code; for example, HTML uses tags or nodes to define the content. 、 、 <video> 、 <canvas>Used to define the elements and attributes of a webpage.

[0228] The most common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be an interface element such as an icon, window, or control displayed on the screen of an electronic device. The control can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets.

[0229] As used in the specification and appended claims of this application, the singular expressions "a," "an," "the," "the," "the," and "this" are intended to include the plural expressions as well, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and includes any or all possible combinations of one or more of the listed items. As used in the above embodiments, depending on the context, the term "when" can be interpreted as meaning "if..." or "after..." or "in response to determining..." or "in response to detecting...". Similarly, depending on the context, the phrase "when determining..." or "if (the stated condition or event) is interpreted as meaning "if determining..." or "in response to determining..." or "when (the stated condition or event) is detected" or "in response to detecting (the stated condition or event)."

[0230] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive), etc.

[0231] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.< / canvas> < / video> < / videoview> < / imgview> < / textview>

Claims

1. A billing management method applied to electronic devices, characterized in that, The method includes: Display the first card on the desktop or the negative one screen; The first card displays a first date and all dates of the first month. The dates of the first month include the dates corresponding to the bills. The dates corresponding to the bills include dates carrying a first identifier. The bills include a first type of bill. The dates carrying the first identifier are the processing period for the first type of bill. The first card also includes first category information, which is used to indicate the specific type of the first type of bill. Wherein, the first date is the current date; In response to an operation on the first card, the first interface of the calendar application is displayed; The first interface includes a list of all dates and schedules for the first month. The all dates for the first month in the first interface include the dates corresponding to the bill, and the schedule list includes detailed information about the bill.

2. The method according to claim 1, characterized in that, The date corresponding to the bill also includes a date carrying a second identifier. The bill also includes a second type of bill. The date carrying the second identifier is the processing period for the second type of bill. The first card also includes second category information, which is used to indicate the specific type of the second type of bill.

3. The method according to claim 1 or 2, characterized in that, The first date is N days earlier than the processing deadline of the earliest due bill in the first month, where N is a positive integer. Displaying the first card on the desktop or the negative one screen includes: When the first date arrives, the first card begins to be displayed on the desktop or the negative one screen.

4. The method according to claim 3, characterized in that, The method further includes: After displaying the first card for a fourth duration, the display of the first card is stopped.

5. The method according to claim 1, characterized in that, The method further includes: In response to an operation on the first schedule in the schedule list, a first control is displayed; In response to the operation of the first control, the repayment interface of the bill corresponding to the first schedule is displayed directly.

6. The method according to claim 5, characterized in that, The repayment interface is provided by the first application; Wherein, when the electronic device is equipped with the official online payment application of the bill issuer, the official online payment application of the bill issuer is the first application; When the electronic device does not have the official online payment application of the bill issuer installed, the most frequently used online payment application installed on the electronic device is the first application.

7. The method according to claim 1, characterized in that, The method further includes: An operation on the second control in the first interface is detected, and multiple labels are displayed; Upon detecting an operation on the first tag among the plurality of tags, one or more third identifiers are displayed across all dates in the first month; The date carrying the third identifier is a date with one or more of the following types of schedules: meetings, studies, and entertainment.

8. The method according to claim 1, characterized in that, The method further includes: The first type of bill is obtained through received SMS messages and / or notifications.

9. The method according to claim 1, characterized in that, The method further includes: Upon reaching the third date, a second card corresponding to the second date is displayed on the desktop or negative one screen, wherein the second date is the processing deadline for the first bill in the first month, and the third date is after the first date and before the second date; The second card displays the billing information of the first bill, which includes one or more of the following: bill issuer, amount, date, and countdown.

10. The method according to claim 9, characterized in that, The second card also includes a third control, and the method further includes: in response to an operation on the third control, directly displaying the repayment interface corresponding to the first bill.

11. The method according to claim 9, characterized in that, The second card also includes a third control, and the method further includes: Upon detecting an operation on the third control, the payment interface corresponding to the first bill is directly displayed. Upon detecting an operation on the input box in the payment interface, a touch keyboard is displayed, and the bill information of the first bill is shown in the candidate area of ​​the touch keyboard; Upon detecting an operation on the billing information, the billing information is entered into the input box.

12. The method according to any one of claims 9-11, characterized in that, The method further includes: If the first bill is successfully processed before the end of the second date, the third card is displayed and the display of the second card is stopped. The third card displays a fourth identifier indicating that the bill has been successfully processed. After the third card has been displayed for a second duration, the display of the third card will stop.

13. The method according to any one of claims 9-11, characterized in that, The method further includes: After the second date has ended and no successful processing of the first bill has been detected, the fourth card is displayed and the display of the second card stops. The fourth card displays a fifth identifier indicating that the bill is overdue. After displaying the fourth card for a third period of time, the display of the fourth card stops.

14. The method according to claim 9, characterized in that, The first bill includes multiple bills, and the second card includes multiple cards that are tiled or stacked, with each card displaying the billing information of one bill.

15. The method according to claim 1, characterized in that, After displaying the first card on the desktop or negative one screen, the method further includes: A second bill with a processing deadline of the fourth date of the first month is obtained; the second bill is a bill of the first type. The first identifier is displayed on the fourth date mentioned in the first card.

16. The method according to claim 15, characterized in that, The method further includes: A fifth card is displayed on the desktop or negative one screen. The fifth card displays the billing information of the second bill. The billing information includes one or more of the following: bill issuer, amount, date, and countdown. After the fifth card has been displayed for a fifth duration, the display of the fifth card will stop.

17. The method according to claim 1, characterized in that, The method further includes: An operation on the fourth control in the first card is detected, and the third interface is displayed; The third interface receives bill information from the user-input third bill, which includes one or more of the following: bill issuer, amount, date, and countdown. A sixth identifier is displayed on the fifth date in the first card, the fifth date being the processing deadline for the third bill, and the sixth identifier is different from the first identifier.

18. The method according to claim 1, characterized in that, The bill type includes one or more of the following: credit card repayment, loan repayment, and internet finance repayment.

19. An electronic device, characterized in that, The method includes one or more processors and one or more memories; wherein the one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program code, the computer program code including computer instructions, which, when executed by the one or more processors, cause the method of any one of claims 1-18 to be performed.

20. A computer-readable storage medium comprising instructions, characterized in that, When the instructions are executed on an electronic device, they cause the method described in any one of claims 1-18 to be performed.

Images