CN113507406B

CN113507406B - Message management method and related equipment

Info

Publication number: CN113507406B
Application number: CN202110694182.7A
Authority: CN
Inventors: 谭泳发; 徐传印
Original assignee: Honor Device Co Ltd
Current assignee: Shanghai Glory Smart Technology Development Co ltd
Priority date: 2021-06-22
Filing date: 2021-06-22
Publication date: 2022-06-10
Anticipated expiration: 2041-06-22
Also published as: CN113507406A

Abstract

The embodiment of the application provides a message management method and related equipment, and relates to the technical field of terminals. The method analyzes the key attribute of the notification message, and determines whether the notification message belongs to a transaction which has already occurred according to the key attribute when the message type of the notification message is determined to be the consumption message. When determining that the notification message belongs to the transaction, the message history record corresponding to the transaction exists, and the similar message of the notification message is displayed on the screen, the method combines or deletes the notification message and the similar message, or executes the updating operation of the reading state. By utilizing the embodiment, the efficiency of message management can be effectively improved.

Description

Message management method and related equipment

Technical Field

The embodiment of the application relates to the technical field of terminals, in particular to a message management method and related equipment.

Background

Mobile payment has become a high-frequency daily activity for a large number of users. On-line payment is rapidly developed, a plurality of on-line payment platforms exist in the market, and a plurality of payment platforms are generally used on an electronic device (for example, a smart phone, a tablet computer and the like) of one user, and each payment platform is associated with a bank card account of the user. Therefore, when the bank card account of the user generates one bank card transaction, the notification bar of the electronic device receives the information about the bank card transaction pushed by the plurality of platforms. Therefore, the number of the messages is increased inevitably, so that the memory is occupied, and the effective information is not convenient to view in time.

Disclosure of Invention

The embodiment of the application discloses a message management method and related equipment, which can optimize the display of notification messages of electronic equipment.

A first aspect of the present application discloses a message management method applied to an electronic device, including: receiving a notification message, and analyzing key attributes of the notification message, wherein the key attributes comprise a message source, a message type, a consumption state, an amount, a bank name, a bank card number and transaction time, and the consumption state comprises income and expenditure; if the message type of the notification message is determined to be a consumption message, determining whether the notification message belongs to an occurred transaction according to the key attribute of the notification message; and if the notification message is determined to belong to the transaction and a message history record corresponding to the transaction exists and the similar message showing the notification message is determined, carrying out merging processing or deleting processing on the notification message and the similar message showing the notification message or executing updating operation of a reading state.

By adopting the technical scheme, when the similar messages belonging to the same transaction with the newly received notification message are confirmed to be displayed, the newly received notification message and the similar messages can be subjected to merging processing or deleting processing or updating operation of the reading state, so that the function of the electronic equipment for displaying the notification message is optimized.

In some optional embodiments, the method further comprises: if the fact that the same kind of messages are displayed is determined, displaying the notification messages on a notification bar; according to the key attribute, combining the notification message and the similar message which is being displayed to obtain a combined message; and deleting the notification message and the similar message being displayed from the notification bar and displaying the combined message. By adopting the technical scheme, the notification message and the similar message are combined according to the key attribute, the notification message and the similar message displayed in the notification bar are deleted, and the combined message is displayed in the notification bar, so that the content displayed in the notification bar can be simplified, and the user can conveniently read the notification message.

In some optional embodiments, the method further comprises: if the fact that the same kind of messages are displayed is determined, the notification messages are not displayed in the notification bar; according to the key attribute, combining the notification message and the similar message which is being displayed to obtain a combined message; and deleting the same kind of messages from the notification bar and displaying the combined messages in the notification bar. By adopting the technical scheme, the notification message is not displayed on the notification bar, the notification message and the similar message are combined according to the key attribute, the similar message displayed on the notification bar is deleted, and the combined message is displayed on the notification bar, so that the content displayed on the notification bar can be further simplified, and the user can read the notification message conveniently.

In some optional embodiments, the method further comprises: if the similar messages are determined to be displayed, the notification messages are displayed or not displayed on a notification bar; combining the notification message and the similar message being displayed to obtain the combined message; and displaying the combined message in the notification bar, and folding and displaying the notification message and the displayed same type of message below the combined message. By adopting the technical scheme, the notification message and the similar messages are combined, the combined message is displayed in the notification bar, and the notification message and the similar messages are displayed in a folding manner, so that the user can conveniently read the notification message and simultaneously look up the content corresponding to each message.

In some optional embodiments, the method further comprises: if the same type of message is determined to be displayed, determining a reserved message from the notification message and the same type of message which is displayed; and deleting other messages from the notification bar, wherein the other messages are messages except the retention message in the notification message and the similar message in the display.

In some optional embodiments, the method further comprises: if the similar messages are confirmed to be displayed, the notification messages are displayed; determining a reservation message from said notification message and said peer message being presented; and marking the reading state of other messages as a read state, and deleting the other messages from the notification bar, wherein the other messages represent messages except the retention messages in the notification messages and the similar messages being displayed.

By adopting the technical scheme, the display of the message content by the notification bar can be simplified, and the user is prevented from reading the same message.

In some optional embodiments, the method further comprises: acquiring read buttons corresponding to the other messages, wherein the read buttons are used for marking the reading states of the other messages as the read states; clicking the read button marks the read status of the other messages as read.

In some optional embodiments, the reservation message is any one of the notification message and the similar message being presented.

In some optional embodiments, the reservation message is the earliest received message or the latest received message in the notification message and the similar message being presented.

In some optional embodiments, the reservation message is a message originating from a set message source in the notification message and the similar message being presented.

In some optional embodiments, the method further comprises: and providing a setting interface, responding to the user operation, and setting a message source. By adopting the technical scheme, the display of the notification message can be managed according to the requirement of the user.

In some optional embodiments, the method further comprises: storing the notification message in a message history for the transaction.

In some optional embodiments, the method further comprises: a message template of the combined message is created in advance; and filling the message template according to the key attribute to obtain a combined message. By adopting the technical scheme, the combined message can be quickly obtained by obtaining the combined message based on the created message template.

In some optional embodiments, the method further comprises: presetting a notification channel by using a notification manager; presetting a plurality of fields for the notification channel by using the notification manager, wherein the fields correspond to the attributes of the consumption messages one by one; and if the notification manager receives the notification message, the notification manager is utilized to analyze the notification message according to the fields and obtain the key attribute.

In some optional embodiments, the method further comprises: acquiring the titles and the contents of all notification messages in the notification bar by using the notifiationListenerService of the notification manager; and extracting key attributes from the titles and contents of the acquired notification messages by using a Natural Language Processing (NLP) technology.

By adopting the technical scheme, the key attribute can be accurately obtained from the notification message.

In some alternative embodiments, the key attributes include message origin, message type, consumption status, amount, bank name, bank card number, transaction time.

In some optional embodiments, the method further comprises formatting the key attribute.

In some optional embodiments, the method further comprises storing the notification message to a message history corresponding to the notification message if it is determined that the notification message does not belong to the transaction.

In some optional embodiments, the method further comprises creating a corresponding message history record for the transaction if it is determined that the notification message belongs to the transaction but no message history record corresponding to the transaction exists.

In some optional embodiments, the homogeneous message refers to a message that has been stored in a message history record corresponding to the transaction and is received within a predetermined time period before the notification message is received.

In some optional embodiments, the method further comprises: and if the similar messages are not displayed, displaying the notification messages or not displaying the notification messages in the notification bar.

In some optional embodiments, the method further comprises: marking two or more consumption messages from the same message source within a preset time according to the sequence of received messages so as to distinguish a plurality of different transactions which occur in sequence; and merging the consumption messages belonging to the same transaction but coming from different message sources based on the pre-created message template according to the mark.

In some optional embodiments, the method further comprises: the method for merging the messages which belong to different transactions and have the same consumption state in the preset time comprises the following steps: counting a total transaction amount based on the transaction amounts involved in the different transactions; and generating a consolidated message based on the message template and the total transaction amount.

In some optional embodiments, the method further comprises: the method for combining the messages which belong to different transactions and have different consumption states in the preset time comprises the following steps: counting a total transaction amount based on the transaction amounts involved in the different transactions; and generating a consolidated message based on the message template and the total transaction amount.

By adopting the technical scheme, the user can conveniently know the overall situation of personal consumption.

A second aspect of the application discloses an electronic device comprising a processor and a memory; the memory to store instructions; the processor is used for calling the instruction in the memory so that the electronic equipment executes the message management method.

A third aspect of the present application discloses a computer-readable storage medium having stored thereon at least one instruction, which when executed by a processor, implements the message management method.

For technical effects brought by the second aspect to the third aspect, reference may be made to the description related to the methods in the above method section, and details are not described herein again.

Drawings

Fig. 1 is a schematic diagram of an application scenario of a message management method.

Fig. 2A to fig. 2E are schematic application scenarios of the message management method provided in this embodiment.

Fig. 3 is a flowchart of a message management method according to an embodiment of the present application.

Fig. 4A to fig. 4E are schematic diagrams of a message management method according to an embodiment of the present application.

Fig. 5A to fig. 5D are schematic diagrams of a message management method according to an embodiment of the present application.

Fig. 6A to fig. 6E are schematic diagrams of a message management method according to an embodiment of the present application.

Fig. 7A to fig. 7C are schematic diagrams of a message management method according to an embodiment of the present application.

Fig. 8A to fig. 8C are schematic diagrams illustrating a message management method according to an embodiment of the present application.

Fig. 9A to fig. 9C are schematic diagrams of a message management method according to an embodiment of the present application.

Fig. 10A to fig. 10C are schematic diagrams illustrating a message management method according to an embodiment of the present application.

Fig. 11A to fig. 11E are schematic diagrams illustrating a message management method according to an embodiment of the present application.

Fig. 12A to fig. 12J are schematic diagrams illustrating a message management method according to an embodiment of the present application.

Fig. 13 is a flowchart of a message management method according to an embodiment of the present application.

Fig. 14 is a flowchart of a message management method according to an embodiment of the present application.

Fig. 15 is a flowchart of another message management method provided in an embodiment of the present application.

Fig. 16A-16B are schematic diagrams illustrating another message management method according to an embodiment of the present application.

Fig. 17 is a schematic structural diagram of an electronic device provided in an embodiment of the present application.

Fig. 18 is a block diagram of a software structure of an electronic device according to an embodiment of the present application.

Detailed Description

In the embodiments of the present application, "at least one" means one or more, "and" a plurality "means two or more than two. "and/or" describes an association relationship of associated objects, meaning that three relationships may exist, e.g., A and/or B may represent: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The terms "first," "second," "third," "fourth," and the like in the description and in the claims and drawings of the present application, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

As shown in FIG. 1, the electronic device presents three notification messages in the notification bar, the three notification messages respectively coming from the tenderer bank^®Application (App), Payment^®App and short message platform. The three notification messages include the same attributes of consumption status (i.e., spending), transaction time (e.g., 9: 59/4/1/4/2021), amount (i.e., 0.01 yuan), etc. I.e. the three notification messages are actually messages corresponding to the same transaction. Therefore, the electronic device repeatedly shows three same notification messages for the user, which affects the message management efficiency and the user experience.

Fig. 2A to fig. 2E are schematic diagrams of an application scenario provided in an embodiment of the present application.

As shown in fig. 2A-2B, after the transaction D1 occurs, the electronic device receives a notification message M1 from the recruiter bank App followed by a message M1' from the paymate App. As shown in FIG. 2C, the electronic device merges messages M1 and M1' with the same properties into message N1 and displays message N1 in the notification bar. As shown in fig. 2D, the electronic device then receives the message M1 ″ from the sms platform, and merges the message M1 ″ and the message N1 into a message N1 '(i.e., merges the messages M1, M1', and M1 '), and shows that the message N1' is as shown in fig. 2E. That is, the electronic device provided in the embodiment of the present application can merge messages M1, M1', and M1 ″ received in sequence and having different sources but the same attribute, so that the message management efficiency is effectively improved, and a user can conveniently and timely refer to the messages. The specific method is described with reference to fig. 3.

Fig. 3 is a flowchart of a message management method according to an embodiment of the present application. The message management method provided by the embodiment of the Application can be applied to an electronic device, and in particular, can be applied to a Notification Manager (Notification Manager) of an Application Framework layer (Application Framework) of the electronic device (i.e., the following steps S11-S20 can be executed by the Notification Manager). The message management method may also be applied to an application layer of the electronic device, implemented as one application (i.e., the following steps S11-S20 may be performed by the application).

Specifically, the message management method includes:

s11, when a transaction occurs, a transaction record corresponding to the transaction is created.

For example, when transaction D1 occurs, a transaction record is created for transaction D1.

In one embodiment of the present application, the transaction record includes, but is not limited to, a bank name, a bank card number, a consumption status (or "consumption type"), a transaction time, an amount, etc.

And S12, receiving the notification message and analyzing the key attribute of the notification message.

In particular, the notification message received by the electronic device may be a message generated by the transaction, a message generated by another transaction, or a message not generated by the transaction.

Taking the notification message as the message generated by the transaction as an example, assuming that the user's payment App is associated with the account C1 of the user's tenderer bank, after the user completes a transaction D1 with the payment App, the tenderer bank App generates a notification message and pushes the notification message to the electronic device. In addition, the Payment App also generates a notification message based on the transaction D1 and pushes the notification message to the electronic device.

In one embodiment of the present application, the key attributes include message origin, message type, consumption status, amount. In other embodiments, the key attributes may further include a bank name, a bank card number, and a transaction time.

It should be noted that, specifically, according to the actual service requirement, the attribute may be continuously added to have higher accuracy when the same message is determined in the following (for example, step S18), or part of the attribute may be reduced to adapt to more message source formats, but the accuracy may be reduced when the same message is determined in the following. The judgment about the same message will be described in detail later (e.g., step S18).

In an embodiment of the present application, the message source refers to a platform for sending the notification message, and may be, for example, a bank App (e.g., a tenderer bank)^®Palm life^®China Bank^®Colorful life^®Etc.), payment platform App (e.g., pay pal)^®WeChat, WeChat^®Cloud flash payment^®Etc.), system messages, and IM platform messages (e.g., short messages, mailboxes, WeChats, etc.). The message types include, but are not limited to, a consumption type message, a communication type message, an advertisement type message, and a reminder type message. The consumption status may refer to expenditure or income.

Taking the notification manager that the message management method is applied to the application framework layer as an example, in an embodiment of the present application, in order to be able to implement analysis of the key attribute of the notification message, a notification channel (notification channel) may be preset by using the notification manager, and named for the notification channel, for example, named as a transaction; and presetting a plurality of fields for the notification channel, namely defining a plurality of fields for the consumption type message, wherein the fields correspond to the attributes of the consumption type message one by one. Reference is made in particular to the description of fig. 12 below.

For example, the contents of the fields are in one-to-one correspondence with key attributes of the consumption type message, such as message source, message type, bank name, bank card number, transaction time, consumption state and amount.

It should be noted that, the above is only described by taking the consumption message as an example, and the content formats of the fields may be designed according to actual service needs.

For application programs (such as bank apps (such as tenderer banks, palm lives, China banks, colorful lives and the like), payment platform apps (such as payment treasures, WeChat, cloud flash payment and the like), system messages, IM platform messages (such as short messages, mailboxes, WeChat and the like) which need to push the consumption messages, the contents of the consumption messages can be filled according to the fields, and the consumption messages are pushed to the notification manager according to the notification channel. Therefore, when the notification manager receives the notification message, the notification message can be analyzed according to the definition of the fields in advance to obtain key attributes, such as message source, message type, bank name, bank card number, transaction time, consumption state, amount and the like.

Specifically, when such an application program requiring pushing of the consumer message is developed, the consumer message to be pushed can be matched to the notification channel, so that the content of the consumer message can be filled according to the fields to obtain the notification message to be pushed, and the notification message can be pushed to the notification manager.

In an embodiment of the present application, when the key attribute of the notification message is obtained through parsing, formatting processing is further performed on the key attribute.

Taking the example of formatting the bank name, for example, the tendering bank and the tendering bank can be unified into a tendering bank; taking the example of formatting the bank card number, for example, the bank card number can be unified into four digits of the end number of the bank card number; taking the example of formatting the amount of money, for example, 1 minute of money and 0.01 yuan may be unified into 0.01 yuan; taking the format processing of the transaction time as an example, for example, the year, month, day, hour and minute can be unified into hour and minute; taking the example of formatting the consumption status as an example, the payment, expense, consumption and expense can be unified into an expense, that is, the payment, expense, consumption and expense are the same consumption status. It should be noted that, in this embodiment, the income and the expense are not the same consumption state; recharge and payment are not the same consumption state. For example, at a certain time and a certain minute, a person a pays the amount d yuan of an order by using the bank card c, and the transaction t1 is completed, so that the consumption state corresponding to the transaction t1 is a expenditure; for another example, if another person b transfers the d element to the bank card c of a within a preset time (within a short time, for example, within 1 minute) after the transaction t1 is completed, and the transaction t2 is completed, the consumption state corresponding to the transaction t2 is income. It should be noted here that, since the consumption states of the transactions t1 and t2 are different, the transactions t1 and t2 belong to two different transactions.

In other embodiments of the present application, the message source of the notification message may be determined according to the platform that sent the notification message. For example, when the received notification message is derived from a pay pal App, the message source of the notification message may be determined to be the pay pal App.

In another embodiment, for example, the message management method is applied to an application layer of an electronic device, and in an embodiment of the present application, to enable analysis of key attributes of the notification message, the application may obtain TITLEs and contents (notification.extra _ TITLE, notification.extra _ TEXT) of all notification messages in a notification bar by using a notification listenerservice in a notification manager; the application program extracts entities with key attributes such as a bank name, a bank card number, transaction time, consumption status, amount of money, etc. from the title and contents of the acquired notification message by using a Natural Language Processing (NLP) technique. Reference is made in particular to the description of fig. 14 below.

S13, determining whether the message type of the notification message is a consumption message. If the message type of the notification message is determined to be a consumption message, executing S14; if it is determined that the message type of the notification message is not the consumption type message, S20 is performed.

In other embodiments of the present application, only the message type of the notification message may be analyzed at S12, and if it is determined at S13 that the message type of the notification message is a consumption type message, then at S14, other attributes of the notification message, such as message source, consumption status, amount, bank name, bank card number, transaction time, and the like, may be identified.

S14, if the message type of the notification message is determined to be a consumption message, determining whether the notification message belongs to the transaction according to the key attribute of the notification message. If the notification message is determined not to belong to the transaction, executing S15; if the notification message is determined to belong to the transaction, S16 is executed.

As previously described, a transaction record is created for a transaction as it occurs, including, but not limited to, bank name, bank card number, consumption status, transaction time, amount, etc. In an embodiment of the present application, a key attribute of the notification message may be compared with the transaction record, and if a bank name, a bank card number, a consumption status, a transaction time, and an amount included in the key attribute are consistent with those recorded in the transaction record, it is determined that the notification message belongs to the transaction.

S15, if the notice message is not determined to belong to the transaction, storing the notice message in the message history record corresponding to the notice message, and then, the flow goes to step S20.

For example, assuming that the notification message does not belong to the transaction D1 occurring in S11 but belongs to the transaction D2, the notification message is stored into the message history of the transaction D2 corresponding to the notification message.

And S16, if the notification message is determined to belong to the transaction, determining whether a message history record corresponding to the transaction exists. If no message history record corresponding to the transaction exists, executing S17; if the message history record corresponding to the transaction exists, executing S18.

In an embodiment of the present application, if it is determined that the notification message belongs to the transaction but no message history record corresponding to the transaction exists, it may be determined that the notification message is a first received consumption-type message belonging to the transaction. If the notification message is determined to belong to the transaction and the message history record corresponding to the transaction already exists, it is determined that the notification message is not a first received consumption message belonging to the transaction, that is, the notification message is a newly received message belonging to the transaction.

In an embodiment of the present application, when receiving a consumption message belonging to each transaction for the first time, the electronic device creates a message history record for each transaction, that is, one message history record for each transaction. For example, transaction D1 corresponds to message history L1; transaction D2 corresponds to message history L2. In one embodiment of the present application, the message history record corresponding to each transaction may be stored in a memory of the electronic device.

In one embodiment of the present application, the message history record corresponding to each transaction is a list including a plurality of fields for recording the consumption type messages belonging to each transaction. The plurality of fields include, but are not limited to, time of receipt of the message, message source, message type, bank name, bank card number, transaction time, consumption status, amount, etc.

S17, if the message history record corresponding to the transaction does not exist, creating the message history record corresponding to the transaction, storing the notification message in the message history record corresponding to the transaction, and then, the flow goes to step S20.

For example, if the notification message belongs to the transaction D1, and the message history L1 corresponding to the transaction D1 does not exist in the memory, that is, the notification message is a consumption message belonging to the transaction D1 and received by the electronic device for the first time, a corresponding message history L1 is created for the transaction D1, and the notification message is stored in the message history L1 corresponding to the transaction D1. Specifically, the time when the notification message is received, the message source of the notification message, the message type, the bank name, the bank card number, the transaction time, the consumption status, the amount of money, and the like are correspondingly stored in each field of the message history L1.

S18, if there is a message history record corresponding to the transaction, determining whether a similar message (i.e. a message with the same attribute as the notification message) of the notification message is being displayed, where the similar message is already stored in the message history record of the transaction. If the same kind of message is confirmed to be displayed, S19 is executed, and if the same kind of message is not confirmed to be displayed, S20 is executed.

In one embodiment of the present application, the homogeneous message refers to a message that has been stored in a message history record corresponding to the transaction and is received within a predetermined time period (e.g., within 5 minutes) before the notification message is received.

In one embodiment of the present application, the messages with the same attribute may refer to messages with the same message type, different message sources, and the same bank name, bank card number, transaction time, consumption status, and amount. In other embodiments, messages with the same attribute may also refer to messages with message types being consumption messages, message sources being different, but the amount and consumption status being the same. Specifically, according to actual service needs, in order to ensure higher judgment accuracy, more attributes of the message may be compared and judged to determine the same message, or the judgment of part of the attributes may be reduced to adapt to more message source formats, but the accuracy may be reduced.

S19, if the similar message is confirmed to be displayed, carrying out merging processing or deleting processing or executing updating operation of the reading state on the notification message and the similar message; and storing the notification message to a message history record for the transaction.

In the first embodiment of the application, if it is determined that the similar messages are being displayed, the electronic device displays the notification messages in a notification bar; according to the key attribute, combining the notification message and the similar message being displayed to obtain a combined message; and deleting the notification message and the similar message being displayed from a notification bar and displaying the combined message.

The electronic equipment can also display the notification message and play a preset first prompt sound effect at the same time, and display the combined message and play a preset second prompt sound effect at the same time. The first and second cue sound effects may be the same or different.

The electronic device also stores the consolidated message into a message history for the transaction.

In an embodiment of the application, the electronic device may create a message template of the merged message in advance; and filling the message template according to the key attribute to obtain a combined message.

For example, the message template is "①And (3) notification: your②③In that④⑤⑥(ii) a Is combined from⑦App message, from (1) to (c), representing the need to fill in the templateThe related contents of (1) to (c) respectively represent the message type, bank name, bank card number, transaction time, consumption state, amount, source of the notification message and the source of the similar message being displayed of the notification message. In one embodiment, for the merged message, the text corresponding to the source of the notification message may be further associated with the notification message, and the text corresponding to the source of the similar message being displayed may be associated with the similar message being displayed; and when receiving a signal generated by clicking the characters corresponding to the sources of the similar messages displayed by the user from the combined message, displaying the detailed contents of the similar messages.

In an embodiment of the present application, when the message management method is applied to a notification manager, the notification manager may be used to merge the notification message and the similar message being displayed to obtain a merged message, and delete the notification message and/or delete the similar message being displayed from a notification bar, and simulate an application program to push the merged message to the notification manager (i.e., itself) by using the notification manager, and display the merged message in the notification bar.

In an embodiment of the present application, when the message management method is implemented in an application layer by an application, the application merges the notification message and the similar message being presented to obtain a merged message, deletes the notification message and the similar message being presented from a notification bar by using a cancelNotification method of notificationsistenerservice, and pushes the merged message to a notification manager, thereby displaying the merged message in the notification bar by using the notification manager.

For a clear description of the first embodiment of the present application, please refer to fig. 4A to 4E, which specifically take an example that after the transaction D1 occurs, the electronic device receives notification messages M1, M1 ', and M1 ″ belonging to the transaction D1 with different sources in sequence, and merges the messages M1, M1', and M1 ″.

Assuming that after the transaction D1 occurs, the electronic device receives the message M1 from the recruiter bank App, key attributes of the message M1, such as message origin, message type, bank name, bank card number, transaction time, consumption status, amount, etc., are parsed. Assuming that the message type of the message M1 is a consumption message, when it is determined that the message M1 belongs to the transaction D1 according to the key attribute of the message M1, and it is determined that a message history record of the transaction D1 does not exist (that is, the message M1 is a first received consumption message belonging to the transaction D1), as shown in fig. 4A, the electronic device creates a message history record L1 for the transaction D1, and displays the message M1 in a notification bar and outputs a prompt signal (e.g., a notification sound S1 is played) to prompt the user to refer to the message M1.

Assuming that the electronic device subsequently receives a new message M1 ' generated by the transaction D1, similarly, the electronic device parses the key attribute of the new message M1 ', determines that the message M1 ' belongs to the transaction D1 according to the key attribute of the message M1 ' if the message type of the message M1 ' is a consumption message, and determines that a message history record of the transaction D1 already exists (that is, the message M1 ' is not a first received consumption message belonging to the transaction D1), it is determined whether the notification bar is showing a message with the same attribute as the message M1 ', that is, a similar message. If it is determined that the notification bar is showing the same kind of message M1, as shown in fig. 4B, the electronic device shows the message M1' in the notification bar and simultaneously plays the notification sound S2. Then, as shown in fig. 4C, the messages M1' and M1 are merged to obtain a merged message N1, the merged message N1 is displayed in the notification bar, and a notification sound S3 is played to prompt the user to read the merged message N1. Additionally, as shown in FIG. 4C, in one embodiment, when a signal is received from the consolidated message N1 that the user clicks on the text "Bingbank," the contents of the message M1 may be presented. When a signal that the user clicks the word "pay for Bao" is received from the merged message, the content of the message M1' is presented.

Assume that the electronic device subsequently receives a new message M1 '' generated by the transaction D1. Similarly, the electronic device parses the key attribute of the new message M1 ″, determines that the message M1 ″, if the message type of the message M1 ″, is a consumption message, determines that the message M1 ″, belongs to the transaction D1 according to the key attribute of the message M1 ″, and determines whether a message history record of the transaction D1 already exists (i.e., the message M1 ″, which is not the first received consumption message belonging to the transaction D1), determines whether the notification bar is showing a similar message. If it is determined that the notification bar is showing a message with the same attribute as the message M1 ", i.e., a homogeneous message N1, the message M1" is shown and a notification sound S4 is played, as shown in fig. 4D. Then, the messages M1 ″ and N1 are merged to obtain a merged message N1 ', as shown in fig. 4E, the messages M1 ″ and N1 are cleared in the notification bar, and the merged message N1 ' is displayed in the notification bar and a notification sound S5 is played to prompt the user to read the merged message N1 '.

For a clear description of the first embodiment of the present application, please refer to fig. 5A to 5D, specifically, after the transaction D1 occurs, the electronic device receives notification messages M1 and M1 ' belonging to the transaction D1 with different sources in sequence, and also receives the message M2 generated by the non-transaction D1 during the period of receiving the messages M1 and M1 ', and performs an example of merging the messages M1 and M1 '.

Suppose that after the electronic device receives the consumption message M1 belonging to the transaction D1, it determines that there is no message history record of the transaction D1, creates a message history record L1 for the transaction D1, and displays the message M1 in the notification bar and plays a notification sound S1 as shown in fig. 5A.

Assume that the electronic device subsequently receives the message M2 generated by the non-transaction D1, and presents the message M2 in the notification bar and plays the notification sound S2 as shown in FIG. 5B; thereafter, the electronic device receives the consumption message M1 ' belonging to the transaction D1, and when it is determined that the message M1 ' is the same as the message M1 being presented, the electronic device presents the consumption message M1 ' in the notification bar and plays a notification sound S3 as shown in fig. 5C, and further merges the messages M1 and M1 ' to obtain a merged message N1, and clears the messages M1 and M1 ' from the notification bar, and displays the merged message N1 below the message M2 in the notification bar as shown in fig. 5D.

In a second embodiment of the present application, if it is determined that the similar message is being displayed, the electronic device does not display the notification message in a notification bar; the electronic equipment combines the notification message and the similar message which is being displayed according to the key attribute to obtain the combined message; and deleting the same kind of messages from the notification bar and displaying the combined messages in the notification bar. The electronic equipment can also play a prompt sound effect when the combined message is displayed. Likewise, the electronic device also stores the consolidated message within a message history for the transaction.

It should be noted that the second embodiment of the present application is different from the first embodiment in that the electronic device does not display the notification message in the notification bar.

In a third embodiment of the present application, if it is determined that the similar message is being displayed, the electronic device displays the notification message in a notification bar; combining the notification message and the similar message being displayed to obtain a combined message; and displaying the merged message in a notification bar, and folding and displaying the notification message and the displayed same type of message below the merged message. Similarly, the electronic equipment can play a prompt sound effect when the notification message is displayed; and playing a prompt sound effect when the combined message is displayed in the notification bar. The electronic device also stores the consolidated message into a message history for the transaction.

In one embodiment of the application, the electronic device further deletes the merged message or deletes the folded and displayed message in response to a sliding operation of the user on the merged message to the left or to the right. That is, the user only needs to slide the merged message to the left or the right to delete the merged message and the message displayed in a folding manner.

For a clear description of the third embodiment of the present application, please refer to fig. 6A to 6E, specifically, after the transaction D1 occurs, the electronic device receives notification messages M1, M1 ', and M1 ″ from different sources and belonging to the transaction D1, merges the messages M1, M1 ', and M1 ″ to obtain a merged message N1, and receives M1, M1 ', and M1 ″ under N1 as an example for description.

Assuming that after the transaction D1 occurs, the electronic device receives the message M1 from the recruiter bank App, and the key attributes of the message M1, such as message source, message type, bank name, bank card number, transaction time, consumption status, and amount, are parsed. Assuming that the message type of the message M1 is a consumption message, judging that the message M1 belongs to the transaction D1 according to the key attribute of the message M1, and determining that a message history record of the transaction D1 does not exist (that is, the message M1 is a first received consumption message belonging to the transaction D1), the electronic device creates a message history record L1 for the transaction D1, displays the message M1 in a notification bar, and plays a notification sound S1 to prompt the user to refer to the message M1 as shown in fig. 6A.

Assuming that the electronic device subsequently receives a new message M1 ' generated by the transaction D1, the electronic device parses the key attribute of the new message M1 ', determines that the message M1 ' belongs to the transaction D1 according to the key attribute of the message M1 ' if the message type of the message M1 ' is a consumption message, and determines that a message history record of the transaction D1 already exists (i.e., the message M1 ' is not a first received consumption message belonging to the transaction D1), determines whether the notification bar is showing a message with the same attribute as the message M1 ', i.e., a similar message. If the notification bar shows the same kind of message M1, the message M1' is shown and a notification sound S2 is played as shown in fig. 6B. Then the messages M1 'and M1 are merged to obtain a merged message N1, the merged message N1 is displayed in a notification bar, and the messages M1' and M1 are displayed below the merged message N1 in a folding mode. The electronic device may also play a notification sound S3 to prompt the user to read the merged message N1 as shown in fig. 6C.

Assume that the electronic device subsequently receives a new message M1 '' generated by the transaction D1. Similarly, the electronic device parses the key attribute of the new message M1 ″, and if the message type of the message M1 ″, determines that the message M1 ″, which is the key attribute of the message M1 ″, belongs to the transaction D1, and determines that there is a message history record of the transaction D1 (that is, the message M1 ″, which is not the first received consumption message belonging to the transaction D1), determines whether the notification bar is showing a message with the same attribute as the message M1 ″, i.e., a similar message. If the notification bar is judged to show the same kind of message N1, the message M1 ' ' is shown below the notification bar showing the folding messages M1 ' and M1 and the notification sound S4 is played as shown in FIG. 6D. Then the messages M1 '' and N1 are merged to obtain a merged message N1 ', then the merged message N1 is deleted in a notification bar, the merged message N1' is displayed, and the messages M1 '', M1 'and M1 are displayed below the merged message N1' in a folding mode. The electronic device may also play a notification sound S5 to prompt the user to read the consolidated message N1' as shown in fig. 6E.

In a fourth embodiment of the present application, if it is determined that the similar message is being displayed, the electronic device does not display the notification message in a notification bar; the electronic equipment combines the notification message and the similar message being displayed to obtain the combined message; and displaying the combined message in a notification bar, and folding and displaying the notification message and the displayed same kind of message below the combined message. Likewise, the electronic device can play a cue sound effect while the notification bar shows the merged message. The electronic device also stores the consolidated message into a message history for the transaction.

The fourth embodiment of the present application is different from the third embodiment in that the electronic device does not display the notification message in the notification bar.

In a fifth embodiment of the present application, if it is determined that the similar message is being presented, the electronic device determines a retained message (i.e., a message that needs to be retained) from the notification message and the similar message being presented, and deletes (scratches) other messages from the notification bar, where the other messages are messages other than the retained message, from the notification message and the similar message being presented.

In one embodiment of the present application, the reservation message may be any one of the notification message and the similar message being presented. In one embodiment of the present application, the reservation message may be the earliest received message or the latest received message of the notification message and the similar message being presented. In one embodiment of the present application, the reservation message may be a message originating from a set message source, among the notification message and the similar message being presented. In one embodiment of the present application, a settings interface may be provided to set a source of a message in response to a user action. For example, a message source such as a payment treasure, a bank, and a short message may be selected as an option for the user in the setting interface, and if the user sets the bank as the message source, the message originating from the bank in the notification message and the similar message being displayed is used as a reservation message when it is determined that the similar message is being displayed.

For the purpose of clearly illustrating the fifth embodiment of the present application, referring to fig. 7A to 7C, specifically, after the transaction D1 occurs, the electronic device receives messages M1, M1', and M1 ″ from different sources belonging to the transaction D1, and only the earliest received message M1 is retained, and other messages are not displayed.

Assuming that the electronic device receives the message M1 from the tenderer bank App after the transaction D1 occurs, key attributes of the message M1, such as message source, message type, bank name, bank card number, transaction time, consumption status, and amount of money, are parsed. Assuming that the message type of the message M1 is a consumption message, judging that the message M1 belongs to the transaction D1 according to the key attribute of the message M1, and determining that a message history record of the transaction D1 does not exist (that is, the message M1 is a first received consumption message belonging to the transaction D1), the electronic device creates a message history record L1 for the transaction D1, displays the message M1 in a notification bar, and plays a notification sound S1 to prompt the user to refer to the message M1 as shown in fig. 7A.

Assuming that the electronic device subsequently receives a new message M1 'originated from the paypal App generated by the transaction D1, the electronic device parses the key attribute of the new message M1', determines that the message M1 'belongs to the transaction D1 according to the key attribute of the message M1' if the message type of the message M1 'is a consumption message, and determines that a message history record of the transaction D1 already exists (i.e., the message M1' is not the first consumption message belonging to the transaction D1), and determines whether the notification bar is showing a similar message. If the notification bar shows the message with the same attribute as the message M1 ', that is, the similar message M1, the message M1 that is received earliest is retained, and the message M1' is not shown in the notification bar and the prompt sound effect is not played, as shown in fig. 7B.

Assume that the electronic device subsequently receives a new message M1 ' ' from the recruiter's bank credit App generated by transaction D1. Similarly, the electronic device parses the key attribute of the new message M1 ″, determines that the message M1 ″, if the message type of the message M1 ″, is a consumption message, determines that the message M1 ″, belongs to the transaction D1 according to the key attribute of the message M1 ″, and determines whether a message history record of the transaction D1 already exists (i.e., the message M1 ″, which is not the first received consumption message belonging to the transaction D1), determines whether the notification bar is showing a similar message. If it is determined that the notification bar shows the same kind of message M1, the message M1 that is the earliest received message is retained, and the message M1 ″ is not shown in the notification bar and no prompt sound effect is played, as shown in fig. 7C.

In a sixth embodiment of the present application, if it is determined that the similar message is being displayed, the electronic device displays the notification message; determining a reservation message from said notification message and said peer message being presented; and marking the reading status of the other messages as read status and deleting the other messages from the notification bar. The other messages refer to the messages except the retention message in the notification message and the similar messages being displayed.

Likewise, in one embodiment of the present application, the reservation message may be any one of the notification message and the peer message being presented. In one embodiment of the present application, the reservation message may be the earliest received message or the latest received message of the notification message and the similar message being presented. In one embodiment of the present application, the reservation message may be a message originating from a set message source, among the notification message and the similar message being presented. In one embodiment of the present application, a settings interface may be provided to set a source of a message in response to a user action. For example, a message source such as a payment treasure, a bank, and a short message may be selected as an option for the user in the setting interface, and if the user sets the bank as the message source, the message originating from the bank in the notification message and the similar message being displayed is used as a reservation message when it is determined that the similar message is being displayed.

In one embodiment of the present application, the method for marking the reading status of the other message as the read status includes, but is not limited to: acquiring read buttons corresponding to other messages respectively, wherein the read buttons are used for marking the reading states of the other messages as read states, and clicking the read buttons to mark the reading states of the other messages as read states; if the read button corresponding to the other message cannot be acquired, acquiring a target address of the other message and jumping to a target page corresponding to the target address; and destroying the target page. The target page is not visible to the user after loading.

For clarity, referring to fig. 8A to 8C, specifically, after the transaction D1 occurs, the electronic device receives messages M1, M1', and M1 ″ from different sources belonging to the transaction D1, so as to determine that the message M1 received earliest is a reserved message, and mark the read status of other messages as read.

Assuming that after the transaction D1 occurs, the electronic device receives the consumer message M1 belonging to the transaction D1 for the first time, the electronic device presents the message M1 in the notification bar and plays the notification sound S1 to prompt the user to review the message M1 as shown in FIG. 8A.

If the electronic device subsequently receives a new message M1 ' belonging to the transaction D1, the electronic device displays the message M1 ' as shown in fig. 8B if it is determined that the notification bar is displaying a message with the same attribute as the message M1 ', i.e., a similar message M1; if the earliest received homogeneous message M1 is determined to be the reserved message, the electronic device marks the reading status of the message M1 'as read, and deletes the message M1' from the notification bar as shown in FIG. 8C.

And S20, if the similar messages are not shown, the notification messages are shown or not shown in the notification bar.

In an embodiment of the present application, if the type of the notification message does not belong to the message of the consumer category (i.e., from S13 to S20), the electronic device may display the notification message in a notification bar or not display the notification message. The electronic equipment can also play a preset prompt sound effect while displaying the notification message.

In an embodiment of the present application, if the type of the notification message belongs to the consumer type message and does not belong to the transaction (i.e., from S15 to S20), the electronic device may display the notification message in a notification bar or not display the notification message. Similarly, the electronic device can also play a preset prompt sound effect while displaying the notification message.

In one embodiment of the present application, if the type of the notification message belongs to the consumer message and belongs to the transaction, and no message history record of the transaction exists, the electronic device displays the notification message in the notification bar after creating the message history record of the transaction D1 (i.e., from S17 to S20). Similarly, the electronic device can also play a prompt sound effect preset by the prompt while displaying the notification message.

For example, assuming that after the transaction D1 occurs, the electronic device receives the consumption message M1 belonging to the transaction D1, and when it is determined that the message history of the transaction D1 does not exist, the electronic device displays the message M1 on the notification bar after creating the message history of the transaction D1 and plays a notification sound S1 to prompt the user to refer to the message M1 as shown in fig. 9A.

In one embodiment of the present application, if the type of the notification message belongs to the consumer message and belongs to the transaction, and there is a message history of the transaction, and the notification bar does not show the same kind of message (i.e., from S18 to S20), the electronic device shows the notification message on the notification bar and plays a prompt sound effect.

For example, assuming that after the electronic device shown in fig. 9A displays the message M1 in the notification bar, the electronic device deletes the message M1 from the notification bar in response to the user ' S operation as shown in fig. 9B, and then the electronic device receives the consumer message M1 ' belonging to the transaction D1, if the message M1 ' is received, the electronic device displays the message M1 ' in the notification bar and plays the prompt sound effect S2 as shown in fig. 9C because the notification bar does not display the same message as the message M1 '.

In another embodiment of the present application, if the type of the notification message belongs to the consumer message and belongs to the transaction, and there is a message history record of the transaction, and the notification bar does not show the generic message (i.e. from S18 to S20), the electronic device processes the notification message according to the last processing manner of the generic message. The similar messages are processed in a manner including, but not limited to, not displaying the similar messages, modifying the reading status of the similar messages to read, and deleting the similar messages from the notification bar. Thus, the electronic device may not display, delete, or automatically mark as read directly when the notification message arrives.

For clarity, please refer to fig. 10A-10C, which particularly take the example that after the transaction D1 occurs, the electronic device receives the consumption message M1 belonging to the transaction D1, and then the user clears the message M1, and continues to receive the message M1'.

Assuming that after the transaction D1 occurs, the electronic device receives the consumer message M1 belonging to the transaction D1 for the first time, the electronic device presents the message M1 in the notification bar and plays the notification sound S1 to prompt the user to review the message M1 as shown in FIG. 10A.

Assume that the electronic device subsequently deletes the message M1 from the notification bar in response to the user's operation as shown in fig. 10B, i.e., does not display the message M1; subsequently, the electronic device receives a new message M1 'belonging to the transaction D1 and being identical to the message M1, and then the electronic device does not display the message M1' in the notification bar according to the processing of the previous identical message M1 as shown in fig. 10C.

For clarity, please refer to fig. 11A-11E again, specifically, after the transaction D1 occurs, the electronic device receives the consumption messages M1 and M1 'belonging to the transaction D1 in sequence, merges the messages M1 and M1' into a message N1, and deletes the message N1 from the notification bar in response to the user operation, and then continues to receive the message M1 ″.

Assuming that after the transaction D1 occurred, the electronic device received for the first time a consumer message M1 belonging to the transaction D1 and originating from the recruiter bank App, the electronic device presents the message M1 in the notification bar and plays a notification sound S1 to prompt the user to review the message M1 as shown in fig. 11A.

Assuming that the electronic device subsequently receives a consumer message M1 ' belonging to said transaction D1 originating from the paypal App and identical to the message M1, the electronic device presents said message M1 ' in a notification bar and plays a notification sound S2 prompting the user to review the message M1 ' as shown in fig. 11B. The electronic device then merges the messages M1, M1 'into a merged message N1, deletes the messages M1, M1' from the notification bar, and presents the merged message N1 in the notification bar and plays a notification sound S3 to prompt the user to refer to the merged message N1 as shown in fig. 11C.

As shown in FIG. 11D, assume that the electronic device subsequently deletes the merged message N1 from the notification bar in response to the user's operation; the electronic device then receives a consumer message M1 '' from the SMS platform pertaining to transaction D1, and as shown in FIG. 11E, the electronic device does not display the message M1 '' in the notification bar based on processing the previous same message N1.

It should be noted that, in the embodiment of the present application, in order to avoid misjudging two or more consumption-type messages from the same message source into the same transaction according to the previously defined factor, that is, the key attribute, the electronic device may mark two or more consumption-type messages from the same message source within a preset time according to the sequence of the received messages, and then, for a plurality of messages from each message source, may align the messages with the same sequence marks in different message sources according to the sequence marks in each message source, respectively, to distinguish different transactions that occur (for example, the sequence marks of an App of a sponsor bank are 01, 02, and 03 messages, and are merged with the sequence marks of an App of a paypal, where each factor of the 01, 02, and 03 messages from the same message source may be the same, these several messages may be misinterpreted as the same transaction according to previous designs. ) (ii) a The consumer messages belonging to the same transaction (for example, the message with the serial number marked as No. 01 of the Adp of the tenderer bank and the message with the serial number marked as No. 01 of the Payment Bap are considered to be the same transaction according to the key factors and the serial number marks of the two parties) but from different message sources can be merged according to the mark based on the pre-created message template.

For example, two or more transactions with the same transaction amount occur within a short time, for example, within 1 minute, the electronic device receives two or more consumption messages from the same message source in sequence within a short time, and the electronic device can mark each of the two or more consumption messages from the same message source to distinguish messages belonging to different transactions; and then merging the consumption messages belonging to the same transaction but coming from different message sources according to the mark based on the pre-created message template.

For clarity of explanation, referring to FIGS. 12A-12F, assume that transaction D1 occurred at time point 09:59, and that the electronic device subsequently received a consumer message M1 from a Bid App belonging to transaction D1 for the first time, the electronic device may mark message M1, e.g., mark message M1 with a mark 09:59-01 to indicate that message M1 belongs to transaction D1, and present the message M1 in a notification bar and play a notification sound S1 to prompt the user to review message M1 as shown in FIG. 12A. Assuming that the electronic device receives a further consumer message M2 from the recruiter bank App pertaining to transaction D2 within a short time, e.g., 1 minute, the electronic device may tag message M2, e.g., tag message M2 with a tag 09:59-02 to indicate that message M2 pertains to transaction D2, and present the message M2 in the notification bar and play a notification sound S2 to prompt the user to review message M2 as shown in fig. 12B. The electronic device then receives a new message M1 'from the Payment platform pertaining to transaction D1, and the electronic device may mark message M1', e.g., as 09:59-01, to indicate that the message M1 'pertains to transaction D1, and present the message M1' in the notification bar and play a notification sound S1 'to prompt the user to review the message M1' as shown in FIG. 12C. Since the electronic device is showing the same kind of message M1 belonging to the transaction D1 when receiving the new message M1 ', the electronic device merges the messages M1 and M1' from different message sources belonging to the same transaction D1 based on the pre-created message template according to the tag to obtain a merged message N1, and plays a notification sound SN1 to prompt the user to refer to the message N1 as shown in fig. 12D. Assuming that the electronic device then receives a consumer message M2 ' from the PAY platform pertaining to transaction D2, the electronic device may tag message M2 ' with the same tag 09:59-02 to indicate that message M2 ' pertains to transaction D2 for message M2 ', present the message M2 ' in the notification bar and play a notification sound S2 ' to prompt the user to review message M2 ' as shown in FIG. 12E. Since the electronic device is showing the same kind of message M2 belonging to the transaction D2 when receiving the new message M2 ', the electronic device merges the messages M2 and M2' from different message sources belonging to the same transaction D2 based on the pre-created message template according to the mark to obtain a merged message N2, and plays a notification sound SN2 to prompt the user to refer to the message N2 as shown in fig. 12F.

Further, in an embodiment of the present application, the electronic device may further perform a merging process on messages belonging to different transactions but in the same consumption state (the transaction amount may be the same or different) within a preset time (within a short time, for example, within 1 minute), including: counting a total transaction amount based on the transaction amounts involved in the different transactions; and generating a consolidated message based on the message template and the total transaction amount.

For example, referring to fig. 12G, the electronic device currently displays the merged message N1 belonging to the transaction D1 and the merged message N2 belonging to the transaction D2, the consumption states of the messages N1 and N2 are the same, the transaction time is 09:59, and the electronic device counts the transaction amounts related to the messages N1 and N2 to obtain the total transaction amount as 0.02 yuan of expenditure; the electronic equipment generates a combined message CN1 based on the message template and the counted total transaction amount; messages N1, N2 were deleted from the notification bar and a consolidated message CN1 was presented in the notification bar along with a play notification sound SCN1 to prompt the user to review message CN 1.

Further, in an embodiment of the present application, the electronic device may also perform a merging process on messages belonging to different transactions and having different consumption states (the transaction amounts may be the same or different) in a short time, including: obtaining a total transaction amount based on transaction amount statistics related to different transactions; and generating a consolidated message based on the message template and the total transaction amount.

For example, referring to fig. 12I, the electronic device currently displays a merged message N1 belonging to transaction D1 and a merged message N2 belonging to transaction D2, the consumption state of message N1 is expenditure, the consumption state of message N2 is income, the transaction time included in messages N1 and N2 is 09:59, and the electronic device performs statistics on the transaction amounts related to messages N1 and N2 to obtain a total transaction amount of 0.99 yuan; the electronic equipment generates a combined message CN1 based on the combined message template and the counted total transaction amount; messages N1, N2 are deleted from the notification bar and the consolidated message CN1 is presented in the notification bar and the notification sound SCN1 is played to prompt the user to review the message CN1 as shown in fig. 12J.

Fig. 13 is a flowchart of a message management method according to an embodiment of the present application, which is mainly described by taking an example that the message management method is applied to a notification manager of an application framework layer of an electronic device.

S121, the notification manager presets a notification channel named transaction, and presets a plurality of fields for the notification channel.

S122, the application program for pushing the consumption message fills the content of the consumption message according to the fields, and pushes the consumption message to a notification manager according to the notification channel.

And S123, informing the manager to acquire the two successive consumption messages and analyzing the content of each field.

S124, when the notification manager judges that the contents of the two consumption messages are consistent, the notification manager hides or deletes the two consumption messages, and simulates an application program to push a new message to the notification manager.

Fig. 14 is a flowchart of a message management method according to an embodiment of the present application, and mainly illustrates, by way of example, an application program of an application layer of an electronic device to which the message management method is applied.

S131, the application acquires the TITLEs and contents (notification.extra _ tlle, notification.extra _ TEXT) of all notification messages in the notification bar using the notification listenerservice in the notification manager.

S132, the application program extracts entities with key attributes such as bank, card number, transaction time, consumption status, amount of money, etc. from the title and content of the acquired notification message by using NLP technology.

S133, the application program compares the entities of the two notification messages which arrive successively to judge whether the two notification messages are the same.

S134, when the application program determines that the two notification messages are the same, the application program may delete the two notification messages by using the cancelNotification method of the Notification ListenerService, and push a new message to the notification manager, where the new message is assembled from the key attributes of the two notification messages.

In addition, the above embodiment is described by taking the consumption message of different source generated by the transaction as an example. The message management method provided by the application can also be used for managing flight travel class messages from different platforms. Fig. 15 is a flowchart of another message management method provided in an embodiment of the present application, when flight itinerary messages from different platforms are managed. Likewise, the message management method shown in fig. 15 may also be applied to a notification manager of an Application Framework layer (Application Framework) of the electronic device (i.e., the following S141-S147 may be performed by the notification manager). The message management method may also be applied to an application layer of the electronic device, implemented as one application (i.e., the following S141-S147 may be performed by the application).

Specifically, the message management method comprises the following steps:

s141, receiving the notification message, and analyzing key attributes of the notification message, wherein the key attributes comprise message type, source, navigation department, shift number, occurrence time, shift state and address.

S142, determining whether the message type of the notification message is a journey type message. If the message type of the notification message is determined to be the travel class message, executing S143; if the message type of the notification message is determined not to be the journey type message, S147 is executed.

And S143, if the message type of the notification message is determined to be the travel type message, determining whether a notification record of the travel type message exists. If the notification record of the travel type message does not exist, executing S144, and if the notification record of the travel type message exists, executing S145.

And S144, if the notification record of the travel type message does not exist, creating the notification record of the travel type message, and storing the notification message into the notification record.

S145, if there is a notification record of the travel type message, determining whether a message (i.e. a similar message) having the same attribute as the notification message is being displayed. If the same kind of message is being displayed, executing S146; if the same kind of message is not shown, S147 is executed.

S146, if the similar messages are displayed, combining the notification messages and the similar messages, or deleting or updating the reading state; and storing the notification message to the notification record.

And S147, displaying the notification message.

For example, referring to fig. 16A, when the electronic device receives the same travel type message from the cruise crossbar App and the hainan aviation App, the electronic device merges the travel type messages sent by the cruise crossbar App and the hainan aviation App to obtain a merged message; as shown in fig. 16B, the travel class messages respectively sent by the cruise crossbar App and the hainan aviation App are deleted from the notification bar, and the merged message is displayed.

Fig. 17 is a schematic structural diagram of an electronic device 100 according to an embodiment of the present application. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identification Module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It is to be understood that the illustrated structure of the embodiment of the present application does not specifically limit the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown, or combine certain components, or split certain components, or arrange different components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a memory, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. The different processing units may be separate devices or may be integrated into one or more processors.

Wherein the controller may be a neural center and a command center of the electronic device 100. The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to reuse the instructions or data, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose-input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, a bus or Universal Serial Bus (USB) interface, and the like.

The I2C interface is a bi-directional synchronous serial bus that includes a serial data line (SDA) and a Serial Clock Line (SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, charger, flash, camera 193, etc. through different I2C bus interfaces, respectively. For example: the processor 110 may be coupled to the touch sensor 180K via an I2C interface, such that the processor 110 and the touch sensor 180K communicate via an I2C bus interface to implement the touch functionality of the electronic device 100.

The I2S interface may be used for audio communication. In some embodiments, processor 110 may include multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may communicate audio signals to the wireless communication module 160 via the I2S interface, enabling answering of calls via a bluetooth headset.

The PCM interface may also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled by a PCM bus interface. In some embodiments, the audio module 170 may also transmit the audio signal to the wireless communication module 160 through the PCM interface, so as to implement the function of answering a call through the bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communications. The bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 110 with the wireless communication module 160. For example: the processor 110 communicates with a bluetooth module in the wireless communication module 160 through a UART interface to implement a bluetooth function. In some embodiments, the audio module 170 may transmit the audio signal to the wireless communication module 160 through a UART interface, so as to realize the function of playing music through a bluetooth headset.

MIPI interfaces may be used to connect processor 110 with peripheral devices such as display screen 194, camera 193, and the like. The MIPI interface includes a Camera Serial Interface (CSI), a Display Serial Interface (DSI), and the like. In some embodiments, processor 110 and camera 193 communicate through a CSI interface to implement the capture functionality of electronic device 100. The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the electronic device 100.

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

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the electronic device 100, and may also be used to transmit data between the electronic device 100 and a peripheral device. And the method can also be used for connecting a headset and playing audio through the headset. The interface may also be used to connect other electronic devices, such as AR devices and the like.

It should be understood that the interface connection relationship between the modules illustrated in the embodiments of the present application is only an illustration, and does not limit the structure of the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection manners or a combination of multiple interface connection manners in the above embodiments.

The charging management module 140 is configured to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive a wireless charging input through a wireless charging coil of the electronic device 100. The charging management module 140 may also supply power to the electronic device through the power management module 141 while charging the battery 142.

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 charge management module 140 and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be used to monitor parameters such as battery capacity, battery cycle count, battery state of health (leakage, impedance), etc. In some other embodiments, the power management module 141 may also be disposed in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be disposed in the same device.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

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

The wireless communication module 160 may provide a solution for wireless communication applied to the electronic device 100, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), bluetooth (bluetooth, BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

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 so that electronic device 100 can communicate with networks and other devices through wireless communication techniques. 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), fifth Generation wireless communication system (5G, the 5th Generation of wireless communication system), BT, GNSS, WLAN, NFC, FM, and/or IR technology, etc. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).

The electronic device 100 implements display functions via the GPU, the display screen 194, and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, video, and the like. The display screen 194 includes a display panel. The display panel may adopt a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), and the like. In some embodiments, the electronic device 100 may include 1 or N display screens 194, with N being a positive integer greater than 1.

The electronic device 100 may implement a shooting function through the ISP, the camera 193, the video codec, the GPU, the display 194, the application processor, and the like.

The ISP is used to process the data fed back by the camera 193. For example, when a photo is taken, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converting into an image visible to naked eyes. The ISP can also carry out algorithm optimization on noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into image signal in standard RGB, YUV and other formats. In some embodiments, electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process digital image signals and other digital signals. For example, when the electronic device 100 selects a frequency bin, the digital signal processor is used to perform fourier transform or the like on the frequency bin energy.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record video in a variety of encoding formats, such as: moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and the like.

The NPU is a neural-network (NN) computing processor that processes input information quickly by using a biological neural network structure, for example, by using a transfer mode between neurons of a human brain, and can also learn by itself continuously. Applications such as intelligent recognition of the electronic device 100 can be realized through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, and the like.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the memory capability of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music, video, etc. are saved in an external memory card.

The internal memory 121 may be used to store computer-executable program code, which includes instructions. The processor 110 executes various functional applications of the electronic device 100 and data processing by executing instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. The storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required by at least one function, and the like. The storage data area may store data (such as audio data, phone book, etc.) created during use of the electronic device 100, and the like. In addition, the internal memory 121 may include a high speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, a Universal Flash Storage (UFS), and the like.

The electronic device 100 may implement audio functions via the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or some functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also called a "horn", is used to convert the audio electrical signal into an acoustic signal. The electronic apparatus 100 can listen to music through the speaker 170A or listen to a handsfree call.

The receiver 170B, also called "earpiece", is used to convert the electrical audio signal into an acoustic signal. When the electronic apparatus 100 receives a call or voice information, it can receive voice by placing the receiver 170B close to the ear of the person.

The microphone 170C, also referred to as a "microphone," is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can input a voice signal to the microphone 170C by speaking the user's mouth near the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C to achieve a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 100 may further include three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, perform directional recording, and so on.

The headphone interface 170D is used to connect a wired headphone. The headset interface 170D may be the USB interface 130, or may be a 3.5mm open mobile electronic device platform (OMTP) standard interface, a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used for sensing a pressure signal, and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A can be of a wide variety, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a sensor comprising at least two parallel plates having an electrically conductive material. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the electronic apparatus 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic apparatus 100 may also calculate the touched position from the detection signal of the pressure sensor 180A. In some embodiments, the touch operations that are applied to the same touch position but different touch operation intensities may correspond to different operation instructions. For example: and when the touch operation with the touch operation intensity smaller than the first pressure threshold value acts on the short message application icon, executing an instruction for viewing the short message. And when the touch operation with the touch operation intensity larger than or equal to the first pressure threshold value acts on the short message application icon, executing an instruction of newly building the short message.

The gyro sensor 180B may be used to determine the motion attitude of the electronic device 100. In some embodiments, the angular velocity of electronic device 100 about three axes (i.e., the x, y, and z axes) may be determined by gyroscope sensor 180B. The gyro sensor 180B may be used for photographing anti-shake. Illustratively, when the shutter is pressed, the gyro sensor 180B detects a shake angle of the electronic device 100, calculates a distance to be compensated for the lens module according to the shake angle, and allows the lens to counteract the shake of the electronic device 100 through a reverse movement, thereby achieving anti-shake. The gyroscope sensor 180B may also be used for navigation, somatosensory gaming scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, electronic device 100 calculates altitude, aiding in positioning and navigation, from barometric pressure values measured by barometric pressure sensor 180C.

The magnetic sensor 180D includes a hall sensor. The electronic device 100 may detect the opening and closing of the flip holster using the magnetic sensor 180D. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 may detect the opening and closing of the flip according to the magnetic sensor 180D. And then according to the opening and closing state of the leather sheath or the opening and closing state of the flip cover, the automatic unlocking of the flip cover is set.

The acceleration sensor 180E may detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). The magnitude and direction of gravity can be detected when the electronic device 100 is stationary. The method can also be used for recognizing the posture of the electronic equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 180F for measuring a distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, taking a picture of a scene, the electronic device 100 may utilize the distance sensor 180F to range to achieve fast focus.

The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light to the outside through the light emitting diode. The electronic device 100 detects infrared reflected light from nearby objects using a photodiode. 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, the electronic device 100 may determine that there are no objects near the electronic device 100. The electronic device 100 can utilize the proximity sensor 180G to detect that the user holds the electronic device 100 close to the ear for talking, so as to automatically turn off the screen to save power. The proximity light sensor 180G may also be used in a holster mode, a pocket mode automatically unlocks and locks the screen.

The ambient light sensor 180L is used to sense the ambient light level. Electronic device 100 may adaptively adjust the brightness of display screen 194 based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust the white balance when taking a picture. The ambient light sensor 180L may also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches.

The fingerprint sensor 180H is used to collect a fingerprint. The electronic device 100 can utilize the collected fingerprint characteristics to unlock the fingerprint, access the application lock, photograph the fingerprint, answer an incoming call with the fingerprint, and so on.

The temperature sensor 180J is used to detect temperature. In some embodiments, electronic device 100 implements a temperature processing strategy using the temperature detected by temperature sensor 180J. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 performs a reduction in performance of a processor located near the temperature sensor 180J, so as to reduce power consumption and implement thermal protection. In other embodiments, the electronic device 100 heats the battery 142 when the temperature is below another threshold to avoid the low temperature causing the electronic device 100 to shut down abnormally. In other embodiments, when the temperature is lower than a further threshold, the electronic device 100 performs boosting on the output voltage of the battery 142 to avoid abnormal shutdown due to low temperature.

The touch sensor 180K is also referred to as a "touch panel". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is used to detect a touch operation acting thereon or nearby. The touch sensor can communicate the detected touch operation to the application processor to determine the touch event type. Visual output associated with the touch operation may be provided through the display screen 194. In other embodiments, the touch sensor 180K may be disposed on a surface of the electronic device 100, different from the position of the display screen 194.

The bone conduction sensor 180M may acquire a vibration signal. In some embodiments, the bone conduction sensor 180M may acquire a vibration signal of the human vocal part vibrating the bone mass. The bone conduction sensor 180M may also contact the human pulse to receive the blood pressure pulsation signal. In some embodiments, the bone conduction sensor 180M may also be disposed in a headset, integrated into a bone conduction headset. The audio module 170 may analyze a voice signal based on the vibration signal of the bone mass vibrated by the sound part acquired by the bone conduction sensor 180M, so as to implement a voice function. The application processor can analyze heart rate information based on the blood pressure beating signal acquired by the bone conduction sensor 180M, so as to realize the heart rate detection function.

The keys 190 include a power-on key, a volume key, and the like. The keys 190 may be mechanical keys. Or may be touch keys. The electronic apparatus 100 may receive a key input, and generate a key signal input related to user setting and function control of the electronic apparatus 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration cues, as well as for touch vibration feedback. For example, touch operations applied to different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also respond to different vibration feedback effects for touch operations applied to different areas of the display screen 194. Different application scenes (such as time reminding, receiving information, alarm clock, game and the like) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

Indicator 192 may be an indicator light that may be used to indicate a state of charge, a change in charge, or a message, missed call, notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be brought into and out of contact with the electronic apparatus 100 by being inserted into the SIM card interface 195 or being pulled out of the SIM card interface 195. The electronic device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support a Nano SIM card, a Micro SIM card, a SIM card, etc. The same SIM card interface 195 can be inserted with multiple cards at the same time. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as communication and data communication. In some embodiments, the electronic device 100 employs esims, namely: an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

The software system of the electronic device 100 may employ a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes an Android system with a layered architecture as an example, and exemplarily illustrates a software structure of the electronic device 100.

Fig. 18 is a block diagram of a software structure of the electronic device 100 according to an embodiment of the present application. The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, an application layer, an application framework layer, an Android runtime (Android runtime) and system library, and a kernel layer from top to bottom. The application layer may include a series of application packages.

As shown in fig. 18, the application packages may include camera, gallery, calendar, phone call, map, navigation, WLAN, bluetooth, music, video, short message, etc. applications.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 18, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions of the electronic device 100. Such as management of call status (including on, off, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and the like.

The notification manager enables the application to display notification information in the status bar, can be used to convey notification-type messages, can disappear automatically after a short dwell, and does not require user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, sounding a prompt tone, vibrating the electronic device, flashing an indicator light, etc.

The Android Runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), Media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), and the like.

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

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, and the like.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

The modules integrated by the electronic device 100 may be stored in a computer-readable storage medium if they are implemented in the form of software functional modules and sold or used as separate products. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by the present application, and can also be realized by hardware related to computer readable instructions, which can be stored in a computer readable storage medium, and when the computer readable instructions are executed by a processor, the steps of the above described method embodiments can be realized. Wherein the computer readable instructions comprise computer readable instruction code which may be in source code form, object code form, an executable file or some intermediate form, and the like. The computer-readable medium may include: any entity or device capable of carrying the computer readable instruction code, recording medium, U disk, removable hard disk, magnetic disk, optical disk, computer memory, Read Only Memory (ROM), Random Access Memory (RAM), etc.

The present embodiment also provides a computer storage medium, where computer instructions are stored, and when the computer instructions are run on an electronic device, the electronic device is caused to execute the above related method steps to implement the message management method in the above embodiments.

The present embodiment also provides a computer program product, which, when running on an electronic device, causes the electronic device to execute the above related steps to implement the message management method in the above embodiments.

In addition, embodiments of the present application also provide an apparatus, which may be specifically a chip, a component or a module, and the apparatus may include a processor and a memory connected to each other; the memory is used for storing computer execution instructions, and when the device runs, the processor can execute the computer execution instructions stored in the memory, so that the chip can execute the message management method in the above-mentioned method embodiments.

The electronic device, the computer storage medium, the computer program product, or the chip provided in this embodiment are all configured to execute the corresponding method provided above, so that the beneficial effects achieved by the electronic device, the computer storage medium, the computer program product, or the chip may refer to the beneficial effects in the corresponding method provided above, and are not described herein again.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical functional division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or multiple physical units, that is, may be located in one place, or may be distributed in multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or may also be implemented in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope disclosed in the present application should be covered within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A message management method is applied to electronic equipment, and is characterized by comprising the following steps:

receiving a notification message, and analyzing key attributes of the notification message, wherein the key attributes comprise a message source, a message type, a consumption state, a money amount, a bank name, a bank card number and transaction time, and the consumption state comprises income and expense;

if the message type of the notification message is determined to be a consumption message, determining whether the notification message belongs to an occurred transaction according to the key attribute of the notification message; and

if the notification message is determined to belong to the transaction and a message history record corresponding to the transaction exists and the similar message of the notification message is determined to be displayed, carrying out merging processing or deleting processing on the notification message and the similar message displayed or executing updating operation of a reading state;

the method further comprises the following steps: marking two or more consumption messages from the same message source within a preset time according to the sequence of received messages so as to distinguish a plurality of different transactions which occur in sequence; and

merging the consumption messages which belong to the same transaction but come from different message sources according to the mark based on a pre-established message template;

the step of marking two or more consumption messages from the same message source within a preset time according to the sequence of the received messages comprises the following steps: marking two or more first consumption information from a first message source within preset time according to the sequence of received messages; marking two or more second consumption information from a second message source within preset time according to the sequence of received messages;

the merging processing of the consumption type messages which belong to the same transaction but come from different message sources based on the pre-created message template according to the mark comprises the following steps:

aligning the sequence number mark of the first message source with the sequence number mark of the second message source; if the serial number mark of first consumption information is aligned with the serial number mark of second consumption information and the key attribute of the first consumption information is consistent with the key attribute of the second consumption information, determining the first consumption information and the second consumption information as the same transaction; and merging the first consumption information and the second consumption information based on a pre-created message template.

2. The message management method of claim 1, wherein the method further comprises:

the method for merging the messages which belong to different transactions and have the same consumption state in the preset time comprises the following steps:

counting a total transaction amount based on the transaction amounts involved in the different transactions; and

generating a consolidated message based on the message template and a total transaction amount;

or

The method for combining the messages which belong to different transactions and have different consumption states in the preset time comprises the following steps:

generating a consolidated message based on the message template and the total transaction amount.

3. The message management method according to claim 1 or 2, characterized in that the method further comprises:

if the similar messages are confirmed to be displayed, displaying the notification messages on a notification bar;

according to the key attribute, combining the notification message and the similar message which is being displayed to obtain a combined message; and

deleting the notification message and the similar message being displayed from the notification bar and displaying the combined message.

4. The message management method according to claim 1 or 2, characterized in that the method further comprises:

if the similar messages are confirmed to be displayed, the notification messages are not displayed on the notification bar;

and deleting the same kind of messages from the notification bar and displaying the combined messages in the notification bar.

5. The message management method according to claim 1 or 2, characterized in that the method further comprises:

if the similar messages are determined to be displayed, the notification messages are displayed or not displayed on a notification bar;

combining the notification message and the similar message being displayed to obtain the combined message; and

and displaying the merged message in the notification bar, and folding and displaying the notification message and the displayed same type of message below the merged message.

6. The message management method according to claim 1 or 2, characterized in that the method further comprises:

if the same type of message is determined to be displayed, determining a reserved message from the notification message and the same type of message which is displayed; and

and deleting other messages from the notification bar, wherein the other messages are messages except the retention message in the notification message and the similar messages in the display.

7. The message management method according to claim 1 or 2, characterized in that the method further comprises:

if the similar messages are confirmed to be displayed, the notification messages are displayed;

determining a reservation message from said notification message and said peer message being presented; and

and marking the reading state of other messages as a read state, and deleting the other messages from the notification bar, wherein the other messages represent messages except the retention messages in the notification messages and the similar messages being displayed.

8. The message management method of claim 7, wherein the method further comprises:

acquiring read buttons corresponding to the other messages, wherein the read buttons are used for marking the reading states of the other messages as the read states; clicking the read button marks the read status of the other messages as read.

9. The message management method as claimed in claim 6, wherein the reservation message is any one of the notification message and the homogeneous message being presented.

10. The message management method according to claim 6, wherein the reservation message is one of the notification message and the same kind of message being presented, which is received earliest or received latest.

11. The message management method according to claim 6, wherein the reservation message is a message originating from a set message source among the notification message and the same kind of message being presented.

12. The message management method of claim 1, wherein the method further comprises:

presetting a notification channel by using a notification manager;

presetting a plurality of fields for the notification channel by using the notification manager, wherein the fields correspond to the attributes of the consumption messages one by one;

and if the notification manager receives the notification message, the notification manager is utilized to analyze the notification message according to the fields and obtain the key attribute.

13. The message management method according to any of claims 1, 2, 8 to 11, characterized in that the method further comprises:

acquiring the titles and the contents of all notification messages in the notification bar by using the notifiationListenerService of the notification manager; and extracting key attributes from the titles and contents of the acquired notification messages by using a Natural Language Processing (NLP) technology.

14. An electronic device comprising a processor and a memory; the memory to store instructions; the processor, configured to invoke the instructions in the memory, to cause the electronic device to perform the message management method according to any one of claims 1 to 13.

15. A computer-readable storage medium storing at least one instruction which, when executed by a processor, implements a message management method as recited in any of claims 1-13.