DE202016009170U1 - Electronic device for associating notification messages - Google Patents

Abstract

An electronic device comprising:
a memory configured to store an instruction;
a processor coupled to the memory, the instruction causing the electronic device to be configured to:
receiving a first notification message, the first notification message including express delivery information;
receiving a second notification message, the second notification message including a password of an express service kiosk and a location of the express service kiosk, the express service kiosk containing a physical express package specified by the express delivery information of the first notification message;
associating the first notification message with the second notification message; and
Presenting the express delivery information, password and location of the express service kiosk in a common interface.

Description

TECHNICAL AREA

The present invention relates to the field of information technologies and more particularly to an electronic device for associating notification messages.

BACKGROUND

With the continuous development of intelligent electronic devices and mobile terminals, a user is increasingly accustomed to receiving various notification messages via a cellular phone. An express delivery tracking notification message is used as an example. 1 Fig. 12 is a schematic diagram of an interface in which a mobile phone presents information for tracking prior art express deliveries. A user typically opens an application (e.g., a Taobao application) or logs into a website (e.g., Taobao.com) to request a tracking status from a server using a tracking number , whereupon the mobile phone the in 1 shown express delivery information presented. The express delivery information includes pickup information, transit information, signing information, and the like. Because the express delivery information is entered on the server after a package is delivered by a courier, it will be delayed. Also, when delivering a package, the courier, as a rule, notifies the user in the form of an SMS message or a phone call when and where to pick up the package. Therefore, the user needs to perform a variety of operations in order to obtain complete express delivery tracking information. More specifically, the user must first enter the in 1 Enter the interface shown to confirm shipment information and a shipping status. Then the user must consult an address book or an SMS message to confirm the courier's delivery information. In addition, if the user does not personally sign for the package, the user must open an SMS application to enter a smart self-express service machine and password. Consequently, both operational efficiency and user-friendliness are relatively poor.

SUMMARY

The present invention provides an electronic apparatus for associating notification messages to solve a technical problem in the prior art that information about the same event is scattered and a user needs to open a plurality of applications to perform a plurality of operations to be performed, resulting in low operational efficiency and poor user-friendliness.

According to a first aspect, an electronic device is provided. The electronic device includes: a memory configured to store an instruction, a processor coupled to the memory, the instruction causing the electronic device to be configured to: receive a first notification message, the first notification message contains express delivery information; receive a second notification message, the second notification message including a password of an express service kiosk and a location of the express service kiosk, the express service kiosk including a physical express package specified by the express delivery information of the first notification message ; associate the first notification message with the second notification message; and to present the express delivery information, password and location of the express service kiosk in a single interface.

In one possible embodiment, the electronic device is configured to determine when a first event related to the first notification message and a second event related to the second notification message represent the same event.

In one possible embodiment, the first notification message indicates that the same event is in a first status, the second notification message indicates that the same event is in a second status, the memory being further configured such that, before it receives the receiving the first notification message, stores a status of the same event as the second status, and wherein the instruction further causes the electronic device to be configured to update the status of the same event to the first status after receiving the first notification message.

In one possible embodiment, the first status is in a flow of the same event, and the instruction further causes the electronic device to be configured to notify a user that after the status of the same event is updated to the first status, the status of the same event is the first status.

In one possible embodiment, the electronic device is configured to: a first obtain a th semantic feature value of the first notification message, the first semantic feature value indicating a first semantic feature of the first notification message; obtain a second semantic feature value of the second notification message, the second semantic feature value indicating a second semantic feature of the second notification message; and to determine that the second semantic feature value of the second notification message is equal or similar to the first semantic feature value of the first notification message.

In one possible embodiment, the electronic device can be configured to sequentially present the first notification message and the second notification message based on a progress sequence of an event in the same interface.

In one possible configuration, a first interface element is configured in the same interface presenting the first notification message and the second notification message, the electronic device also having an input device which is coupled to the processor and configured in such a way that, for triggering the first interface element, it has a receives input from a user, the instruction further causing the electronic device to be configured to invoke an application according to the input to trigger the first interface element, and a third semantic characteristic value of the application with a first semantic characteristic value of the first notification message or a second semantic feature value of the second notification message.

In one possible embodiment, the same interface that presents the express delivery information and the password has a first interface in a first application, a second interface in a second application, or a third interface generated by the electronic device.

In one possible embodiment, the first notification message contains a first point in time and information about an action to be taken at this first point in time, the first point in time representing a future point in time, and the instruction also causes the electronic device to be configured to take the action specified in the first to obtain the first time contained in the notification message, and to generate an appointment reminder based on the first time and the information about the action to be taken at the first time, the appointment reminder reminding a user of the action to be taken at the first time before the first time.

In one possible embodiment, the first notification message contains a first location and information about an action to be taken at this first location, the instruction also causing the electronic device to be configured to determine a current location of the mobile terminal device and to provide a reminder element generate if the deviation between the current location of the mobile terminal and the first location is within a preset deviation range, the reminder element invoking the information about the action to be taken at the first location.

In one possible embodiment, the semantic feature value of the first notification message comprises at least one of the following types: a type of event, the status of the event, a time associated with the event, a location associated with the event, an order number associated with the event, a with person associated with the event, a time when the mobile terminal receives the first notification message, and a sender of the first notification message.

The electronic device is configured to display the express delivery information, password and location of the express service kiosk in a single interface. In this way, the user can conveniently view associated events and notification messages originating from different channels, thereby improving operational efficiency and user-friendliness.

character list

• 1 ist ein schematisches Diagramm einer Schnittstelle, in der nach dem Stand der Technik auf einem Mobiltelefon Informationen zur Verfolgung von Expresszustellungen angezeigt werden;
• 2 ist ein schematisches Diagramm eines Mitteilungsnachrichten-Konzepts gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 3 ist ein schematisches Strukturdiagramm eines mobilen Endgeräts zum Assoziieren von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 4 ist ein schematisches Strukturdiagramm eines mobilen Endgeräts zum Assoziieren von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 5 ist ein schematisches Flussdiagramm eines Verfahrens zum Assoziieren von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 6A bis 6C zeigen ein schematisches Flussdiagramm eines Verfahrens zur Assoziierung von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 7 ist ein schematisches Flussdiagramm eines Verfahrens zum Assoziieren von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 8 ist ein schematisches Diagramm einer Schnittstelle zur Darstellung von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 9 ist ein schematisches Diagramm einer Schnittstelle zur Darstellung von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 10 ist ein schematisches Diagramm einer Schnittstelle zur Darstellung von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 11 ist ein schematisches Diagramm einer Schnittstelle zur Darstellung von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 12 ist ein schematisches Diagramm einer Schnittstelle zur Darstellung von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 13 ist ein schematisches Diagramm einer Schnittstelle zur Darstellung von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 14 ist ein schematisches Diagramm einer Schnittstelle zur Darstellung von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 15 ist ein schematisches Diagramm einer Schnittstelle zur Darstellung von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 16 ist ein schematisches Diagramm einer Schnittstelle zur Darstellung von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 17 ist ein schematisches Diagramm einer Schnittstelle zur Darstellung von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 18 ist ein schematisches Diagramm einer Schnittstelle zur Darstellung von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 19 ist ein schematisches Diagramm einer Schnittstelle zur Darstellung von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 20 ist ein schematisches Diagramm einer Schnittstelle zur Darstellung von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 21 ist ein schematisches Diagramm einer Schnittstelle zur Darstellung von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel;
• 22 ist ein schematisches Strukturdiagramm eines mobilen Endgeräts zum Assoziieren von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel; und
• 23 ist ein schematisches Strukturdiagramm einer Vorrichtung zum Assoziieren von Mitteilungsnachrichten gemäß einem zum Verständnis der Erfindung notwendigen Beispiel.

In order to make the technical solutions in the embodiments of the present invention clearer, the accompanying drawings necessary for the description of the embodiments or the prior art are briefly introduced below. It is to be understood that the accompanying drawings in the following description illustrate only some embodiments of the present invention, and a person of ordinary skill in the art can derive other drawings from these accompanying drawings without being creative.

• 1 Fig. 12 is a schematic diagram of an interface for displaying express delivery tracking information on a mobile phone according to the prior art;
• 2 Fig. 12 is a schematic diagram of a notification message concept according to an example necessary for understanding the invention;
• 3 Fig. 12 is a schematic structural diagram of a mobile terminal for associating notification messages according to an example necessary for understanding the invention;
• 4 Fig. 12 is a schematic structural diagram of a mobile terminal for associating notification messages according to an example necessary for understanding the invention;
• 5 Fig. 12 is a schematic flow diagram of a method for associating notification messages according to an example necessary for understanding the invention;
• 6A until 6C show a schematic flow diagram of a method for associating notification messages according to an example necessary for understanding the invention;
• 7 Fig. 12 is a schematic flow diagram of a method for associating notification messages according to an example necessary for understanding the invention;
• 8th Fig. 12 is a schematic diagram of an interface for displaying notification messages according to an example necessary for understanding the invention;
• 9 Fig. 12 is a schematic diagram of an interface for displaying notification messages according to an example necessary for understanding the invention;
• 10 Fig. 12 is a schematic diagram of an interface for displaying notification messages according to an example necessary for understanding the invention;
• 11 Fig. 12 is a schematic diagram of an interface for displaying notification messages according to an example necessary for understanding the invention;
• 12 Fig. 12 is a schematic diagram of an interface for displaying notification messages according to an example necessary for understanding the invention;
• 13 Fig. 12 is a schematic diagram of an interface for displaying notification messages according to an example necessary for understanding the invention;
• 14 Fig. 12 is a schematic diagram of an interface for displaying notification messages according to an example necessary for understanding the invention;
• 15 Fig. 12 is a schematic diagram of an interface for displaying notification messages according to an example necessary for understanding the invention;
• 16 Fig. 12 is a schematic diagram of an interface for displaying notification messages according to an example necessary for understanding the invention;
• 17 Fig. 12 is a schematic diagram of an interface for displaying notification messages according to an example necessary for understanding the invention;
• 18 Fig. 12 is a schematic diagram of an interface for displaying notification messages according to an example necessary for understanding the invention;
• 19 Fig. 12 is a schematic diagram of an interface for displaying notification messages according to an example necessary for understanding the invention;
• 20 Fig. 12 is a schematic diagram of an interface for displaying notification messages according to an example necessary for understanding the invention;
• 21 Fig. 12 is a schematic diagram of an interface for displaying notification messages according to an example necessary for understanding the invention;
• 22 Fig. 12 is a schematic structural diagram of a mobile terminal for associating notification messages according to an example necessary for understanding the invention; and
• 23 Fig. 12 is a schematic structural diagram of an apparatus for associating notification messages according to an example necessary for understanding the invention.

DESCRIPTION OF EXAMPLES AND EMBODIMENTS

In order to clarify the objects, technical solutions and advantages of the present invention, the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. All other embodiments that can be achieved by those skilled in the art without the use of creative work fall within the scope of the present invention. In specific descriptions of the following embodiments, related concepts are further explained based on the technical understanding of those skilled in the art. It should be noted that these concepts are not intended to be limiting provide explanations of a concept and term well known in the art.

A mobile terminal, which may also be referred to as user equipment (UE) or intelligent terminal, includes, but is not limited to, a mobile phone, a mobile computer, a tablet computer, a personal digital assistant (PDA), a media player , smart TV, smart watch, smart glasses, smart bracelet and the like. A method for updating a notification message in the present invention can be applied to various mobile terminals. A specific implementation is described below using a mobile terminal device, which carries out the method by way of example. In other implementations of the present invention, well-known matters (methods, process, components, circuits) are not described in detail.

An operating system (OS) is a computer program that manages a computer's hardware and software resources and is a core and cornerstone of a computer system. The development of mobile communication technologies brings with it a rapid development of the technologies of mobile devices. An operating system running on a terminal device can be a Linux kernel-based operating system, such as Android in a mobile version, Ubuntu in a mobile version or Tizen, a Windows phone system and an iOS system, as well as a BlackBerry system or a Symbian System, but it can also be a desktop operating system, such as, but not limited to, Windows, Mac OS, or Linux. Android is used as an example. As a platform for a mobile device, Android has a hierarchical software structure with an operating system (OS), a middleware (MiddleWare) and an application (Application). The hierarchical software structure of Android is divided into the following layers from the bottom up: first, an operating system layer (OS), second, various libraries (Libraries) and Android Runtime (RunTime), third, an application framework (Application Framework), and fourth, an application (Application). The specific content of each layer is not described in detail.

A semantic feature can be understood as follows: a semantic class is divided from a certain point of view, so words belonging to a same semantic class can have different values with respect to a semantic feature or some semantic features, creating a difference between highlighted in these words. The values of the semantic feature or semantic features are semantic feature values, where the semantic feature value is used to indicate a semantic feature of an application, notification message or field. For example, if an application is "Jingdong" or "Taobao," a mobile device, after performing a semantic analysis of the application, may recognize that a semantic attribute value of the application represents "shopping,""e-commerce," or the like. If an application is "Baidu Maps", the mobile device can determine that a semantic characteristic value of the application represents "map", "city", "landmark" or the like. In this solution, the semantic feature value may include at least one of the following types: a type of event related to a notification message, a status of the event related to the notification message, a time of the event related to the notification message, a location of the event related to the notification message-related event, an order number of the notification message-related event, a person attending the notification message-related event, a time when the mobile terminal receives the notification message, a sender of the notification message, and the like. For example, the mobile device assigns an in 1 shown notification message as express delivery as the type of delivery and performs a semantic analysis of a field in the notification message to obtain semantic feature values such as an event type, event status information and time information of the notification message. For example, it is determined that the event type of the notification message is an express delivery, that the event status in relation to the notification message is indicated in the following order as "has been picked up", "being transported", "being delivered", "signed" and the like that the times related to the notification message are respective times related to the respective status, and that related to the notification message, an express delivery number 32045687464564 exists, and so on.

In the embodiments of the present invention, a notification message can be understood as a message of the notification message type that is sent from one object to another object, as in 2 shown. The object can be a server or a mobile device. The notification message can be a data message exchanged between the server and the mobile terminal or a data message exchanged between mobile terminals. After the notification message has been analyzed, an event type, sending object, event status, and the like associated with the notification message can be determined. The notification message is transmitted in various forms. The mobile terminal can display the notification message to the user via a user interface (UI, graphical user interface) or render the notification message in the form of a voice output. The notification message can be, for example, an SMS message transmitted in text form in an SMS application, or a multimedia message transmitted in image form; it can be a message displayed in a shopping application (e.g. Taobao) in a similar way as in 1 is pictured; or it may be content delivered in spoken form via phone call or voice chat, e.g. B. a voice chat in a phone call to a friend or in a chat with a friend via WeChat. Examples of the notification message are as follows: a shopping-type notification message generated when a user shops online, and a correspondingly generated express delivery-type notification message, the content of the shopping-type notification message containing at least an order number, an item purchased, a purchase date and the like, and the content of the express delivery type notification message may include at least an express delivery number, an express delivery status, a time for each status and the like; a flight type notification message generated when a user books an air ticket, the content of the flight type notification message may include at least a flight number, a flight time, a departure airport, and a landing airport; a movie-type notification message generated when a user books a movie ticket, wherein the content of the movie-type notification message may include at least a movie title, a season, a theater name, and the like; and a bank type notification message generated when a user transacts a banking service, wherein the content of the bank type notification message may include at least a processing time, a processing item, a processing location, and the like. Given the technical understanding of one of ordinary skill in the art, the notification message may be received and displayed in a system notification bar, with the user being reminded of the notification message by a ring or vibration; however, the notification message can also be received by an application within the mobile terminal, whereby the user is not reminded of the notification message.

The notification message contains several types of content, and the associated key information can be referred to as key content. The key content can be defined as an object and content that, in order to implement a function or take an action, must be unique, e.g. B. a type, a time, a place, a destination, a status and an order number, which are part of the notification message. Any object field or content field identifying the key content may be referred to as a key field. The key field has various forms and can represent any language content, any text content, or a specific format field. The notification message type is used to represent a notification message type, e.g. B. whether the type of notification message is an express delivery type, a flight type, a bank type, an e-commerce type or the like. The time is a time related to the notification message, e.g. B. a sending time or an arrival time of the notification message or a time of occurrence of an event related to the notification message. The location is a location related to the notification message, e.g. B. the place of occurrence of the event related to the notification message, or a destination of the event. The status is used to show the history of the event related to the notification message, e.g. a package picked up or signed for, or a flight being delayed. A more detailed key field indicates high accuracy, with more captured content indicating higher accuracy and better practicality. It should be noted that in the embodiments of the present invention, the key field and the semantic feature value describe the same content from different perspectives, and the key field and the semantic feature value essentially correspond to each other. In some scenarios, a value of the key field is consistent with a value of the semantic characteristic value, where the key field is equal to the semantic characteristic value.

In the prior art, a mobile terminal typically receives a notification message from a plurality of channels. Even with a plurality of notification messages on the same settlement transaction, the mobile terminal cannot effectively merge the notification messages from the plurality of channels because the notification messages are expressed differently, are in different forms, and are distributed over a plurality of applications. As a result, it is difficult for a user to associate the plurality of notification messages with a particular transaction. As a result, the user has to perform a plurality of operations to obtain the entire information, and the efficiency of the operations is relatively low. To solve this problem, the present invention provides an embodiment form of a mobile terminal, with a schematic structural diagram of the mobile terminal in 3 is shown. It should be noted that the mobile terminal 300 shown in the figure is only an example, and a common product has more or fewer parts than those in FIG 3 shown, combine two or more parts, or have different part configurations. The mobile terminal shown in the figure can be designed so that it is an in 5 , 6A until 6C or 7 carried out the procedure shown. Various in 3 portions shown may be implemented in hardware comprising signal processing and/or application specific integrated circuit(s), in software, or in a combination of hardware and software. As shown in the figure, the mobile terminal 300 includes parts such as a radio frequency (RF) circuit 310, a memory 320, an input unit 330, a display unit 340, a sensor 350, an audio frequency circuit 360, a Wi- Fi (Wireless Fidelity) module 370, a processor 380 and a power supply 390. The components are described in detail below.

The RF circuitry 310 may be configured to receive and transmit a signal in an information receiving and transmitting process or a calling process. In particular, upon receiving downlink information from a base station, the RF circuitry 310 sends the downlink information to the processor 380 for processing and sends associated uplink data to the base station. The RF circuitry typically includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, an LNA (Low Noise Amplifier), a duplexer, etc. In addition, the RF circuitry 310 can communicate with a network and another device via wireless communication. Any communication standard or protocol may be used for wireless communication, the communication standard or protocol including but not limited to GSM (Global System of Mobile Communication, Global System for Mobile Communications), GPRS (General Packet Radio Service), CDMA (Code Division multiple access), WCDMA (Wideband Code Division Multiple Access), LTE (Long Term Evolution), email, SMS (Short Messaging Service) and the like.

The memory 320 may be configured to store a software program and a module, with the processor 380 executing the software program and the module stored in the memory 320 to perform various functional applications of the mobile terminal 300 and data processing. The memory 320 may mainly include a program storage area and a data storage area. The program storage area can store an operating system, an application required for at least one function (e.g., an audio playback function and an image playback function), and the like. The data storage area can store data (e.g., audio data and a phone book) created based on use of the mobile terminal 300, and the like. Additionally, memory 320 may include high-speed random access memory and non-volatile memory, e.g. B. at least one magnetic disk storage device, a flash memory device or other volatile solid state storage device.

The input unit 330 may be configured to receive input digit or character information and generate key signal inputs related to user setting and function control of the mobile terminal 300 . In particular, the input unit 330 may include a touch panel 331 and another input device 132 . Touchpad 331, also referred to as a touchscreen, can detect a touch operation performed by a user on or near the touchpad (e.g., an operation performed by the user on or near touchpad 331 using an appropriate object or tool such as a finger or a pen is carried out), whereby a corresponding connection device can be controlled according to a preset program. Optionally, the touchpad 331 may include two parts: a touch recognizer and a touch controller. The touch detection device detects a user's touch location, detects a signal evoked by the touch, and transmits the signal to the touch controller. The touch controller receives touch information from the touch recognition device, converts the touch information into touch point coordinates, and then sends the touch point coordinates to the processor 380 and may receive and execute a command sent by the processor 380 . Moreover, the touch panel 331 can be implemented by using a plurality of types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 331 , the input unit 330 may include another input device 132 . In particular, the other input device 132 may be one or more physical keyboards, a function key (e.g., a volume up control button or an on/off button), a trackball, a mouse, a joystick, and the like, but is not limited thereto.

The display unit 340 may be configured to display information input by the user or information provided to the user and various menus of the mobile terminal 300 . The display unit 340 can have a display panel 341 . Optionally, the display panel 341 may be in the form of an LCD (Liquid Crystal Display), an OLED (Organic Light-Emitting Diode), or the like. In addition, the touch panel 331 may cover the display panel 341 . When the touch is detected on or near touchpad 331, touchpad 331 transmits the touch to processor 380 to determine a type of touch event, upon which processor 380 provides a corresponding visual output on display panel 341 based on the type of touch event. In 3 the touch panel 331 and the display panel 341 serve as two independent components to implement input and output functions of the mobile terminal 300. In some embodiments, however, to implement the input and output functions of the mobile terminal 300, the touch panel 331 and the display panel 341 be integrated.

The mobile terminal 300 can also have at least one sensor 350, such as e.g. B. a fingerprint sensor, a light sensor, a motion sensor and another sensor. In particular, the fingerprint sensor is designed in such a way that it recognizes the fingerprint information entered by the user. The light sensor can represent an ambient light sensor and a proximity sensor. The ambient light sensor may adjust the brightness of the display panel 341 based on the luminance of the ambient light, and the proximity sensor may disable the display panel 341 and/or the backlight when the mobile terminal 300 is held to the ear. As a motion sensor, an acceleration sensor can detect a value of acceleration in any direction (usually along three axes), can detect a value and a direction of gravity in a static state, and can be designed to use a posture app of the mobile terminal (such as e.g., switching between a landscape and a portrait mode, an associated game and magnetometer posture calibration), a feature related to vibration detection (such as a pedometer and a shock), and the like. Other sensors, such as B. a gyroscope, a barometer, a hygrometer, a thermometer and an infrared sensor can be further formed in the mobile terminal 300, the details are not described here.

The audio frequency circuitry 360, a speaker 361 and a microphone 362 can form an audio interface between the user and the mobile terminal 300. The audio frequency circuitry 360 may convert received audio data into an electrical signal and then transmit the electrical signal to the speaker 361, where the speaker 361 converts the electrical signal into an audio signal for output. In addition, the microphone 362 converts the captured audio signal into an electrical signal, the audio frequency circuitry 360 receives the electrical signal, converts the electrical signal into audio data, and then outputs the audio data to the RF circuitry 108 to transmit the audio data to, for example, another mobile Terminal to send or output the audio data for further processing to the memory 320.

Wi-Fi is one of the short-range wireless transmission technologies. The mobile terminal 300 can help the user to receive and send an email, browse a web page, access streaming media, and so on with the help of the Wi-Fi module 370 . The Wi-Fi module 370 provides the user with broadband wireless Internet access. Although 3 shows a Wi-Fi module 370, the Wi-Fi module 370 is not a mandatory part of the mobile terminal 300 and can be omitted as needed without changing the gist of the present invention.

As the control center of the mobile terminal 300, the processor 380 is connected to each part of the entire mobile terminal through various interfaces and cables, and executes or executes the software program and/or module stored in the memory 320 and calls those stored in the memory 320 Data from to perform various functions of the mobile terminal 300 and data processing, so as to perform an overall monitoring of the mobile terminal. Optionally, processor 380 may include one or more processing units. Preferably, processor 380 may integrate an applications processor and a modem processor. The application processor mainly processes an operating system, an interface (user interface), an application, and the like. The modem processor primarily handles wireless communications. It should be noted that the modem processor may alternatively not be integrated into the processor 380.

The mobile terminal 300 further includes the power supply 390 (e.g., a battery) that supplies power to each part. Preferably, the power supply may be logically connected to the processor 380 using a power management system to implement functions such as charge management, discharge management, and power consumption management using the power management system.

Although not shown in the figure, the mobile terminal 300 may also include a camera, a Bluetooth module, and the like. Details are not described here.

As in 4 As shown, the operating system stored in memory 320 may include an application 410, a content gathering module 420, a semantic analysis module 430, and a notification message management module 440. Application 410 is a set of applications related to everyday use of a mobile phone, e.g. B. A set of applications such as an SMS message, a phone, WeChat and Taobao. Content capture module 420 may capture the content of a notification message related to an application in application 410, e.g. B. Information such as an SMS message, a WeChat notification message, words on a Taobao page and a recording in a phone call or WeChat. After capturing the content of the notification message, the content capture module 420 may send the message content to the semantic analysis module 430 . The semantic analysis module 430 performs a semantic analysis of the content of the notification message to extract the key content of the notification message and sends the key content to the notification message management module 440. After receiving the key content, the notification message management module 440 searches based on the key field for a locally stored notification message. When a notification message matching the key field is stored, the notification message management module 440 updates the format of the stored notification message; or, if there is no notification message matching the key field, the notification message management module 440 creates a record, stores the content of the notification message, and updates the content of the notification message upon receipt of a corresponding notification message. Those skilled in the art will recognize that the content capture module 420, the semantic analysis module 430, and the notification message management module 440 may be software modules stored in memory. From a hardware implementation perspective, the processor 380 can call the module code in the memory 320 to implement the solution of the present invention.

• S501. Ein mobiles Endgerät erhält eine erste Mitteilungsnachricht in einer ersten Anwendung.

5 is a schematic flow diagram of a method for associating notification messages according to an example necessary for understanding the invention, the method comprising the following steps:

• S501. A mobile terminal receives a first notification message in a first application.

A mobile terminal receiving a first notification message in a first application may look like this: after receiving the first notification message, the mobile terminal sends the first notification message to the first application for processing; or the mobile terminal can receive the first notification message using the first application. For example, the mobile terminal receives an SMS message in an SMS application, WeChat information in a WeChat application, an Express delivery type notification message in a Taobao application, a notification message in a Bank type application, a notification message in an application of the shopping type and the like.

S502. The mobile terminal obtains a semantic feature value of the first notification message, the semantic feature value being used to indicate a semantic feature of the first notification message.

After receiving the first notification message, the mobile terminal performs a semantic analysis of the first notification message. Semantic analysis technology is relatively mature and is a powerful technology used to obtain and understand textual information by analyzing information exchanged between nodes in a social network. The semantic feature value of the first notification message can be determined based on the analysis of the first notification message.

S503. The mobile terminal determines a second notification message in a second application, with a semantic feature value of the second notification message matching the semantic feature value of the first notification message, with the second notification message already being stored in the mobile terminal.

After receiving the semantic feature value of the first notification message, the mobile terminal can search for a stored notification message based on the semantic feature value. For example, leads the mobile terminal a table with semantic feature values of notification messages. The mobile terminal looks up the table to acquire the second notification message whose semantic property value matches the semantic property value of the first notification message. That a semantic feature value of a second notification message matches the semantic feature value of the first notification message implies the following: an event related to the second notification message and an event related to the first notification message are one and the same event. For example, an SMS message in the SMS application and a notification message in an e-commerce application refer to the same order number or the same express delivery number. Alternatively, the semantic feature value of the second notification message is the same as or similar to the semantic feature value of the first notification message. For example, the semantic feature values refer to different attributes of the same place, but refer to the same place. For example, both the capital of China and the political center of China refer to Beijing. In particular, the mobile terminal can match the semantic feature value of the first notification message and the semantic feature value of the second notification message. A comparison standard can be based on whether the semantic feature values are the same or similar. The former can include at least whether the meanings of the notification messages are the same, whether the feature values match each other, etc. The latter can include at least whether the notification messages have a correlation, whether the notification messages match in context, whether the feature values are synonyms, and so on.

S504. The mobile terminal associates the first notification message with the second notification message.

In particular, the association can be understood in a broad sense, i.e. the first notification message and the second notification message can be expressed in any form, including various forms for the display and presentation of the notification messages, such as a visual form, an auditory form and a tactile form Shape. Examples of this can be at least the following:

In a visual presentation scenario, the first notification message and the second notification message are presented in the same interface; or the first notification message and the second notification message are successively presented in the same interface based on a time series of receipt of the notification messages; or the first notification message and the second notification message are sequentially presented in the same interface based on a progress sequence of the event, e.g. B. based on a sequence of collection, shipping, delivery and receipt of a package; or the first notification message is provided with a hyperlink-like button, whereby the second notification message can be opened directly by tapping the button. The interface in which the first notification message and the second notification message are presented is an interface in the first application; or the interface in which the first notification message and the second notification message are presented is an interface in the second application; or the interface in which the first notification message and the second notification message are presented is an interface newly generated by the mobile terminal. The newly generated interface can be an interface in a third application or an interface that is generated separately by the mobile device and does not belong to a third-party application.

In an auditory scenario, the first notification message and the second notification message may be played in the same context, further including the first notification message and the second notification message being played in the same context based on a time sequence in succession.

In a tactile environment, when a mobile phone is provided with a tactile password, the first notification message and the second notification message can be delivered to a user sequentially in a tactile form in a same context according to a corresponding password rule.

It should be noted that the time sequence mentioned above can be understood as a sequence of events related to the notification message. For example, a package is first picked up, then handed over and finally signed. For example, in a flight, a ticket is first issued, then passengers board the plane, and finally the plane takes off. The chronological sequence can also be understood as the point in time at which the mobile terminal device receives the notification message.

In an example necessary for understanding the invention, when the first notification message and the second notification message are presented in the form of a visual effect, a first Interface element formed in the first notification message and the second notification message representing interface. The method further includes the steps of: receiving an instruction to trigger the first interface element from the user and invoking a third application. A semantic property value of the third application matches the semantic property value of the first notification message, or a semantic property value of the third application matches the semantic property value of the second notification message. The interface element is a component of a terminal interface and typically includes text, image, icon, audio, video, widget, and the like. The interface element can be understood as a command line used to quickly start a task, e.g. B. a link provided by a system to quickly start a program or open a file or folder. The interface element is mostly in the form of an icon and resembles a shortcut. The shortcut is a collective term for a number of possible operating entries. The shortcut can be, but is not limited to, an application, a specific function, a contact, a setting option, a notification message bar, a shortcut bar, and the like. In this example necessary for understanding the invention, the shortcut may represent a link to launch an application, for example a link to launch one of the following applications: WeChat, Google Search, a camera and the like; or it consists of a link to launch an item within an application, for example a link to launch a contact in a Contacts application, a link to launch an SMS message in an SMS application, or a link to activate a feature setting in a Settings application . Launching an item within a program is understood to mean that the item is displayed within the program or that the item is triggered within the program. Tapping the interface item in the interface can quickly open a related application, making calling the application more efficient.

6A until 6C are flow charts of a method for associating notification messages according to an example necessary for understanding the invention. An express delivery type notification message is used below as an example for a specific description. An implementation principle of another type of notification messages is similar to this. As in the 6A until 6C shown, a method of processing the express delivery notification message is as follows:

S601. A mobile terminal receives a notification message, or a mobile terminal opens an application and reads a notification message, or a mobile terminal is in a call and reads a notification message in the form of voice output. The notification message can be an SMS message in an SMS application (e.g. the message is used to inform a user when and where to pick up a package), express delivery information (as in 1 shown) in a Taobao application, voice information in a calling application (e.g. the information is used to inform a user when and where to pick up a package), or the like. To simplify the description, an SMS message will be used as an example, and the notification message will be referred to as a first express delivery SMS message.

S602. The mobile terminal captures the content of the first express delivery SMS message, i. H. the content detection module 420 extracts the message content from the first express delivery SMS message and transmits the extracted message content to the semantic analysis module 430. The message content may contain all words, a sender, the time of receipt and the like of the first express delivery SMS message.

S603. The mobile terminal performs a semantic analysis of the first express delivery SMS message, i. That is, the semantic analysis module 430 determines a key field of the SMS message through analysis. The key field can contain at least one of the following fields: a message type (an express delivery type), an event (an element associated with this SMS message, such as pickup, delivery, or receipt), an express delivery number, an express delivery company, a logistics status, a time of receipt of the SMS message, a time of the event associated with the SMS message, a location of the event associated with the SMS message, and other information associated therewith. After the field is obtained by parsing, the semantic analysis module 430 sends a semantic analysis result to the notification message management module 440 so that the notification message management module 440 performs a subsequent process.

S604. The notification message management module matches the first express delivery SMS message with an existing notification message and performs S605 if the match fails, or S606 if the match succeeds. The existing notification message is a notification message previously stored in the mobile terminal and can be stored in tabular form, in particular, based on the key field obtained through semantic analysis.

For a specific matching procedure, see S701 to S705 in 7 . 7 Figure 12 is a flow chart of message matching according to an example necessary to understand the invention. From a software implementation perspective, message matching may be performed by the notification message management module 440 . From a hardware implementation perspective, the processor can call the code in memory to get the in 7 carry out the process steps shown. In S701, the notification message management module 440 receives the key field sent from the semantic analysis module 430 and extracts a key field of a message type. For example, the extracted message type is an express delivery type. In S702, the notification message management module 440 matches the express delivery type and a type of a notification message stored in the mobile terminal to determine whether there is a notification message whose type matches or is similar to the express delivery type. If the matching is successful, the notification message management module 440 performs step S703 to select an existing notification message corresponding to the message type of the express delivery type, and then performs S704. If a value assigned to the message type field in the key field sent by the semantic analysis engine is null, or if a value assigned to the message type field corresponds to the express delivery type, but the mobile terminal does not have a notification message of the express delivery type locally stores, the notification message management module 440 confirms that the matching has failed and executes step S704. In S704, the notification message management module 440 extracts a key field of a notification message ID. The notification message ID serves to uniquely identify the notification message and can be an order number of an event, e.g. an express delivery number or a flight number, or it may be an identifier located in the terminal and used to read and write the notification message, e.g. B. an identifier in binary form. If the notification message management module 440 confirms that there is a notification message whose ID matches the ID of the notification message, the notification message management module 440 confirms that the matching was successful and executes step S706. If the notification message module 440 does not receive the notification message ID, ie a value assigned to the notification message ID is zero, the notification message management module 440 confirms that the mobile terminal does not store a notification message related to the event associated with the notification message. When the notification message is an express delivery message, it can be assumed that the mobile terminal does not store a notification message related to an express delivery number of the express delivery, executing step S705. In S705, the fact that the notification message management module 440 updates all notification messages can be understood as the notification message management module 440 storing the notification message in the memory of the mobile terminal. Updating all notification messages here may be updating all types of notification messages stored in the mobile terminal, e.g. B. updating notification messages of all kinds, such. B. an express delivery, a flight and a chat, or updating this type of notification messages stored in the mobile terminal. If the notification message is an express delivery message, all notification messages of the express delivery type are updated, and another type of notification message is not updated.

More specifically, in step S604, a successful match may include a case where the first express delivery SMS and the existing notification message match in at least one of two key fields: the message type and the ID of the notification message. A failed match in the broadest sense can include at least two cases. First case: a key field in a notification message is invalid or has no value. In this case the reconciliation cannot be performed, which can be regarded as a reconciliation error. Second case: A notification message contains a key field which, however, differs from or is not similar to a key field stored in the mobile device.

S605. If the matching fails, the notification message management module 440 updates the existing notification message in the mobile terminal. See the description of S705 for details.

S606. If the comparison is successful, ie if it is confirmed that the mobile terminal has an SMS relating to the first express delivery saves notification message, the notification message management module 440 obtains an express delivery status related to the first express delivery SMS and compares the express delivery status with a saved express delivery status to determine whether the express delivery status stored in the mobile terminal needs to be updated. The notification message management module 440 performs step S607 when the express delivery status needs to be updated, or ends the process when the express delivery status does not need to be updated.

For a specific implementation, see S706 to S708 in 7 . For example, the content of the first express delivery SMS message consists of delivery information. As in 9 shown, the content of the SMS message is "[STO.Express] Your STO package 12045687464564 has arrived at the south gate of your residential area. Please collect it before 11:00 am". The sender's phone number is 13546785456. A notification message stored in the mobile device and relating to the express delivery is in 8th displayed and contains pick-up information, transport information, delivery information and the like. In S706, the notification message management module 440 obtains the notification message stored in the mobile terminal and related to the express delivery. In S707, the notification message management module 440 obtains a key field of an event status of the first express delivery SMS message and compares the event status with an event status stored in the terminal and related to the express delivery. If the field in the notification message is null, i.e. the notification message contains no express delivery status information, or the event status field in the notification message shows that an event status of the notification message is a status stored in the mobile terminal, the notification message management module 440 performs step S705. When the event status field of the notification message actually indicates that an event status of the notification message is a status that is not stored in the mobile terminal and is a new status, the notification message management module 440 executes step S708. In particular, the event status of the first express delivery SMS message shows that an express delivery status is a pick-up notification and is in a status instructing a user to pick up a package. The notification message management module 440 compares the pickup notification with the pickup information, the transit information, the delivery information, and the like contained in 8th are shown, and determines that the status of the pick-up notification does not match the status stored in the mobile device. In this case, the notification message management module 440 determines that the notification message of the express delivery needs to be updated and executes step S708 to update the status of the express delivery event. More specifically, in an example necessary to understand the invention, the first notification message is used to indicate that the event is in a first state, while the second notification message is used to indicate that the event is in a second state. Before the first notification message is received in the first application in S501, the method further comprises storing a status of the event as the second status. After the first notification message is received in the first application in S501, eg after S504, the method further comprises updating a current status of the event to the first status. If the first status is an important status in the course of the event, such as a pickup status, a handover status, or a delivery status of the package, after updating the event status to the first status, the method further includes notifying the user that the current status of the event is the first status is on, e.g. notifying the user that the current status of the package is "in delivery". There are different types of notification message, eg conventional visual, audio and electronic forms, or a highlighted display in an interface, or a prompt information in a notification message bar. This is not a limitation.

S607. After determining that the status of the event related to the notification message needs to be updated, the notification message management module 440 updates the status to update the express delivery status to a status related to the first express delivery SMS message. The update can only consist of saving the first express delivery SMS, or, as in 10 shown, only from the presentation of the content of the first express delivery SMS together with content that is stored in addition to the storage of the first express delivery SMS in the mobile terminal.

Specifically, when the user fails to pick up the package on time due to some delay caused, a courier puts the package in an intelligent self-express service kiosk and sends a location and password of the intelligent self-express service kiosk via SMS message to the user, as in 11 shown. The content capture module 420 that semantic analysis module 430 and notification message management module 440 perform the above process flow again, ie, S601 to S607, as in FIG 6A and 6B presented to capture the stored content and the content mentioned in the SMS message, such as the location and password of the intelligent self-express service kiosk, and finally an in 12 presented interface. That is, the SMS message is associated with the previously stored express delivery related content to present the SMS message and content in a common interface.

S608. After updating the express delivery status, the notification message management module 440 can also determine whether the pickup notification represents an important status of the express delivery event, i.e. determine whether the updated status is an important status of the event and if the updated status is related to important status information , carry out S609, or if the updated status is not related to important status information, end the process.

An important status is a status that plays a key role in an overall process of the event as a whole in the course of an event. For example "collected", "will be handed over", "will be delivered", "signed" and similar in an express delivery context; booking, boarding, departure, landing and similar in a flight context; Ordering, car pickup, payment, car return and the like in a car rental context; ordering, payment, usage and the like in a context of online movie ticket purchase; or a settlement transaction, processing time, processing location, associated amount and the like in the context of a bank's payment reminder. The important status can be customized by a user, can be determined by the mobile terminal based on semantic analysis, can be generated by the terminal through a plurality of learning processes, or can be sent from a server after analyzing a large amount of data be transmitted to the mobile device. In this embodiment, pickup notification is an important element in a delivery stage. If a user is not informed when and where to pick up a package, express delivery may not be completed. Therefore, the pickup notification is associated with the important status information, and S609 is executed.

S609. After determining that the updated status is an important status of the event, the notification message management module 440 reminds the user that the status of the event has been updated, i. That is, it reminds the user that the express delivery status has been updated and prompts the user to check the express delivery status in time. The manner of the reminder is not limiting and can be at least one of the reminder functions such as e.g. B. a sound, a light or a vibration. Alternatively, the user can be reminded via a wearable device such as a bracelet or watch. Alternatively, in a particular environment, a possible peripheral device can be used to remind the user. In a vehicle environment, for example, an animation can be played on a screen in a vehicle.

In the above example necessary for understanding the invention, the notification message management module 440 according to FIG 6B and 6C steps S604 to S610 are performed, after which in 7 steps S701 to S11 are performed by the notification message management module 440.

In another example necessary for understanding the invention, the 5 , 6A until 6C and 7 methods shown can alternatively be applied to another type of notification message. In the following, a flight notification and an online shopping notification are used as an example for the purpose of brief description. For the description of the same or an equivalent method, reference is made to the description of the notification message of the express delivery type.

13 , 14 , 15 , 16 , 17 and 18 12 are schematic representations of a flight-type notification message according to an example necessary for understanding the invention. As in 13 shown, a user wants to book a flight ticket from Beijing to Shenzhen. The user does not select a specific airline or price range, but taps a "search button" to search for the flight ticket. It is assumed that the user has the in 14 finds the flight information shown and determines a flight number, a flight time, a passenger's name, a price, and the like. In this case, the user is in an order confirmation phase without paying for the order. The user taps the in 14 Proceed to Checkout button shown, where after the payment is complete, an in 15 job information page shown is displayed. An order status indicates that the current status is in is a stage where the ticket has been purchased but not yet issued. After issuing the ticket, the airline will send an in 16 displayed SMS message to the user. The SMS message is used to inform the user that the ticket has been issued and to ask them to check the flight details and flight information. Throughout the process appears according to 13 until 16 a variety of interfaces. Almost all interfaces contain notification message information, with each notification message information having a corresponding content. Due to the implementation of the method provided in this embodiment of the present invention, the mobile terminal can finally use an in 17 display the interface shown to inform the user of the progress of the flight type notification message. It should be noted that 17 is complete in relation to information regarding the flight. Of course, some notification messages can also be displayed in the course of booking the flight ticket. For example, only the bottom notification message can be displayed, i.e. when the payment has been completed but no confirmation SMS message has been received.

17 shows an interface in which the key fields are finally presented on the basis of a time sequence, after which, in order to extract the key fields from the notification messages, the mobile terminal has carried out a semantic analysis of the in 13 until 16 performed the notification messages shown and arranged the key fields according to a certain rule. For the sake of simplicity, the numbers 1, 2 and 3 are used to identify the aforementioned notification messages. A message record numbered 1 is information that is displayed after the mobile device has performed a semantic analysis of the in 13 until 15 displayed notification messages. A message record numbered 2 is information that is displayed after the mobile device, in order to capture a key field, performs a semantic analysis of the in 16 displayed SMS message. Message record number 3 is an appointment reminder that is automatically generated by the mobile terminal for some items having a deadline after the mobile terminal has performed a semantic analysis of the items. More specifically, after performing a semantic analysis of “Check-in ends 45 minutes before departure”, in which in 16 contain the SMS message shown, the mobile device will generate a reminder element one hour before departure to remind the user to check-in as soon as possible. More precisely, in an example necessary for understanding the invention, the first notification message can contain a first point in time and information about an action to be taken at the first point in time, the first point in time representing a future point in time. This in 5 The method described may further include the steps of: receiving the first time contained in the first notification message, and automatically generating an appointment reminder based on the first time and the information about the action to be taken at the first time. The appointment reminder is used to remind the user before the first time of the action to be taken at the first time. Concretely, in this embodiment, the first point in time (45 minutes before 18:00 on August 15) is in 16 shown, with "boarding" representing the action information. After receiving the SMS message, the mobile terminal automatically generates a reminder item based on the content of the SMS message. The reminder element is used to remind the user to complete boarding before 5:15 p.m. on August 15th. The appointment reminder can be two or three hours before departure or set by the user.

As in 18 shown, records a message record numbered 4 in 18 also the airport pickup information booked by the user. The airport pickup information may be information collected by the mobile device when the user uses the 13 until 15 subscribed to website interfaces shown, or information collected by the processor when a server sends an SMS message to the mobile terminal after the user has placed an order, or information collected by the processor when the user places an order in a third-party online driving service software (e.g. Uber). More specifically, based on a semantic analysis, e.g. B. the user's schedule, display the associated notification messages in the same interface. In this way, the efficiency of the user's handling of received information is improved, which makes it easier for the user to use and significantly improves the user experience. In addition, the mobile terminal can list other main information in a higher part of the interface, e.g. For example, presenting several keywords in the display interface: "2016-08-15, departure from Shenzhen, business trip to Beijing" to help the user to quickly learn about a topic related to the news entry in the interface.

19 , 20 and 21 12 are schematic representations of an on-line shopping type notification message according to an example necessary to understand the invention. Buying a movie ticket online is an example of online shopping. After an order for a movie ticket is placed and payment is successfully completed, an in 19 interface shown. Information such as the title of the film, a cinema, a seat number, a mobile phone number and a two-dimensional code for ticket collection are stored in the interface. After the payment is completed and the cinema has successfully issued the ticket, the server will send an in 20 shown SMS message to the mobile terminal to inform the user of the order number, cinema, ticket collection number, cinema address and the like. After capturing the notification messages in 19 and 20 the mobile device generates an in 21 UI interface diagram shown by using the in 5 or in the 6A until 6C carried out the procedure shown.

21 shows an interface in which key fields are finally presented based on a time sequence after, in order to extract the key fields from the notification messages, the mobile terminal has performed a semantic analysis of the in 19 and 20 shown notification messages and arranged the key fields according to a certain rule. The bottom message record is information displayed after the mobile terminal performs a semantic analysis of an in 19 shown notification message. The mean message record is information displayed after the mobile terminal performs a semantic analysis of an in 20 displayed SMS message. The top message record is an appointment reminder that is automatically generated by the mobile device for some appointment-based elements after a semantic analysis of the elements has been carried out. More specifically, after performing a semantic analysis for "18:00-20:00", the mobile terminal generates as in 19 or 20 shown, a reminder message half an hour before the start of a movie to remind the user to watch the movie. As in 21 shown, the shortcuts "one-tap navigation" and "one-tap map pickup" are displayed in the top message record of the interface. The user taps the shortcut “One-tap navigation”, after which the mobile terminal automatically runs a mapping software to navigate using “No. 16 Houhai Avenue, Nanshan District, Shenzhen,” what the SMS message said in 20 specified as a destination to carry out a navigation process. The user taps on the "One-tap card pickup" key combination, after which the mobile device automatically enters the two-dimensional code for the card pickup in the message in 19 in a full screen, allowing the user to scan the two-dimensional card pickup code and collect the card. Alternatively, the mobile terminal device and the ticket collection machine are in a contactless connection, eg a Bluetooth or NFC connection. After the user taps "One-tap card pickup", the mobile terminal invokes the Bluetooth or NFC connection to send an electronic package to the card pickup machine. The electronic package contains information about the two-dimensional code for the Ticket collection or information about the ticket collection number.After receiving the electronic package, the ticket collector will check whether the electronic package is valid, and after successful verification, will print the movie ticket.By providing the shortcut, the user can conveniently call an application or process, which is associated with an event of the notification message, thereby reducing the number of operations performed by the user and effectively improving the user's operational efficiency.Also, the mobile terminal can further list essential information in an upper area of the interface, eg several Present keywords in the display interface: "2016-08-12, watch movie in Taikoo Shing" to help the user quickly learn about a topic related to the news item in the interface.

In an optional implementation, the first notification message includes a first location and information about an action to be taken at that first location. This in 5 The method described can also have the following steps: determining a current location of the mobile terminal device and automatically generating a reminder element if the deviation between the current location of the mobile terminal device and the first location falls within a preset deviation range. The reminder element is used to request the information about the action to be taken at the first location. In this embodiment, the in 20 SMS message shown the first location (No.16 Houhai Avenue, Nanshan District, Shenzhen) and the action information (watching a movie). If a mobile phone carried by the user records real-time geographic location information of the user and a real-time geographic location of the user is in the vicinity of the first location, the mobile phone generates a reminder element to remind the user to watch the movie near the location. Furthermore, a location-based reminder element can be combined with a time-based reminder element. More specifically, the time-based reminder element can also be used to remind of a location of an action to be taken, where the location-based reminder element can also be used to remind of a time of the action to be taken.

22 12 is a schematic structural diagram of a mobile terminal according to an embodiment. For the mobile end device, the in 3 shown structure of the mobile terminal referenced. The mobile terminal can be designed in such a way that it 5 , 6A until 6C and 7 shown procedures. A mutual reference can be made for a same or corresponding technical feature. In detail, the mobile terminal comprises one or more processors 2202 and a memory 2201. The processor 2201 is connected to the memory 2202. Memory 2201 is configured to store one or more applications. Processor 2202 executes the one or more applications to receive a first notification message in a first application; to obtain a semantic feature value of the first notification message, the semantic feature value being used to indicate a semantic feature of the first notification message; to determine a second notification message in a second application, wherein a semantic feature value of the second notification message matches the semantic feature value of the first notification message, wherein the second notification message is already stored in the mobile terminal; and to associate the first notification message with the second notification message.

In an example necessary for understanding the invention, the processor determines that a semantic feature value of a second notification message matches the semantic feature value of the first notification message in the following way: The processor determines that an event relating to the second notification message , and an event related to the first notification message are one and the same event. Further, the first notification message is used to indicate that the event is in a first status, and the second notification message is used to indicate that the event is in a second status. The memory is further configured to store a status of the event as the second status before the first notification message is received in the first application. The processor is further configured to update a current status of the event to the first status after receiving the first notification message in the first application. In the course of the event, if the first status represents an important status, the processor is further arranged, after updating the status of the event to the first status, to inform a user that the current status of the event is the first status . In the foregoing implementation, the mobile terminal also includes an output device. Specifically, the processor associates the first notification message with the second notification message by instructing the output device to sequentially present the first notification message and the second notification message in the same interface according to a progression sequence of the event.

In an example necessary for understanding the invention, the processor is also designed in such a way that it determines the semantic feature value of the second notification message. The processor determines that a semantic feature value of a second notification message matches the semantic feature value of the first notification message, in particular by the processor determining that the semantic feature value of the second notification message is the same or similar to the semantic feature value of the first notification message.

In the above example necessary for understanding the invention, the mobile terminal further comprises an output device. Specifically, the processor associates the first notification message with the second notification message by instructing the output device to present the first notification message and the second notification message in the same interface; or by instructing the output device to sequentially present the first notification message and the second notification message in the same interface based on a timing of receipt of the notification messages; or by instructing the output device to sequentially output the first notification message and the second notification message in the form of a voice output based on a time sequence.

In an implementation of this example, which is necessary for understanding the invention, a first interface element representing the first notification message and the second notification message is formed in the interface. The mobile terminal also includes an input device. The input device is designed in such a way that it receives an instruction from the user to trigger the first interface element. The processor is further configured to execute, according to the instruction, a third application, which serves to trigger the first interface element and which is received from the input device. A semantic feature value of the third application matches the semantic feature value of the first notification message, or a semantic feature value of the third application matches the semantic feature value of the second notification message.

In an implementation of this example necessary for understanding the invention, the output device presents the first notification message and the second notification message in an interface in the first application; or the output device presents the first notification message and the second notification message in an interface in the second application; or the processor regenerates an interface, after which the output device presents the first notification message and the second notification message in the newly generated interface.

In the above example, which is necessary for understanding the invention, the first notification message contains a first point in time and information about an action to be taken at the first point in time, with the first point in time representing a future point in time. The processor is further configured to capture the first time contained in the first notification message and to automatically generate an appointment reminder about the action to be taken at the first time based on the first time and the information. The appointment reminder is used to remind the user before the first time of the action to be taken at the first time. Alternatively, the first notification includes a first location and information about an action to be taken at that first location. The processor is further configured to determine a current location of the mobile device and to automatically generate a reminder item if the deviation between the current location of the mobile device and the first location falls within a preset deviation range. The reminder element is used to request the information about the action to be taken at the first location.

23 12 is a schematic structural diagram of an apparatus for associating notification messages according to an embodiment. The device for associating notification messages may be part of the structure of the in 3 or 22 shown mobile device or an independent mobile device, as in 4 shown. The device for associating notification messages may be arranged to use the in 5 , 6A until 6C and 7 shown procedures. A mutual reference can be made for a same or corresponding technical feature. More specifically, the device comprises one or more first acquisition modules 2301, a second acquisition module 2302, a determination module 2303 and an association module 2304. The first acquisition module 2301 is connected to the second acquisition module 2302, the second acquisition module 2302 is connected to the determination module 2303, and the Determination module 2303 is connected to association module 2304 . The first collection module 2301 is configured to retrieve a first notification message in a first application. The second collection module 2302 is configured to obtain a semantic feature value of the first notification message, the semantic feature value being used to indicate a semantic feature of the first notification message. The determination module 2303 is designed to determine a second notification message in a second application, with a semantic feature value of the second notification message matching the semantic feature value of the first notification message, with the second notification message already being stored in the mobile terminal. The association module 2304 is configured to associate the first notification message with the second notification message.

In an example necessary for understanding the invention, the determination module determines that a semantic characteristic value of a second notification message matches the semantic characteristic value of the first notification message, in that the determination module determines that an event in relation to the second notification message and an event represent the same event in relation to the first notification message. Furthermore, the first notification message is used to indicate that the event is in a first status, while the second notification message is used to indicate that the event is in a second status. The device further includes a storage module configured to store a status of the event as the second status before the first detecting module receives the first notification message in the first application, and an update module configured to store a current Status of the event updated to the first status after the first capture module receives the first notification message in the first application ten has. The device also contains a prompting module. The prompting module is configured to inform a user that the current status of the event is the first status after the updating module updates the current status of the event to the first status. Specifically, in the above implementation, the association module may be configured to sequentially present the first notification message and the second notification message in the same interface based on a progression sequence of the event.

In an example necessary for understanding the invention, the device further comprises a third detection module. The third detection module is designed in such a way that it detects the semantic feature value of the second notification message. The determination module determines that a semantic feature value of a second notification message matches the semantic feature value of the first notification message, in particular by the determination module determining that the semantic feature value of the second notification message is the same or similar to the semantic feature value of the first notification message.

In the previous example necessary for understanding the invention, the association module is designed in particular to present the first notification message and the second notification message in the same interface, or to present the first notification message and the second notification message on the basis of a chronological sequence of the receipt of the notification messages in the same interface to present sequentially, or to sequentially output the first notification message and the second notification message based on a time sequence in the form of a voice output.

In an example necessary for understanding the invention, a first interface element is formed in the interface, which presents the first notification message and the second notification message. The device further comprises a fourth detection module and an invoking module. The fourth detection module is configured to detect an instruction from the user to trigger the first interface element. The invocation module is configured to execute a third application according to the instruction received from the fourth detection module. A semantic property value of the third application matches the semantic property value of the first notification message, or a semantic property value of the third application matches the semantic property value of the second notification message.

In an example necessary for understanding the invention, the interface presenting the first notification message and the second notification message represents an interface in the first application; or the interface presenting the first notification message and the second notification message presents an interface in the second application; or the interface presenting the first notification message and the second notification message is an interface newly generated by the mobile terminal.

In the above example, which is necessary for understanding the invention, the first notification message contains a first point in time and information about an action to be taken at the first point in time, the first point in time representing a future point in time. The device further comprises a fifth acquisition module configured to acquire the first point in time contained in the first notification message, and a first generating module configured to generate, based on the first point in time and the information about the action to be taken at the first time automatically generates an appointment reminder. The appointment reminder is used to remind the user before the first time of the action to be taken at the first time. Alternatively, the first notification message includes a first location and information about an action to be taken at that first location. The device comprises a sixth acquisition module configured to acquire a current location of the mobile terminal device, and a second generating module configured such that when the deviation between the current location of the mobile terminal device and the first location in falls within a preset deviation range, a reminder element is automatically generated. The reminder element is used to request the information about the action to be taken at the first location.

An example necessary for understanding the invention further provides a computer-readable storage medium which stores one or more programs. The one or more programs include an instruction, wherein when the instruction is executed by a mobile terminal having a plurality of applications, the mobile terminal is enabled to perform the method in the in 5 , 6A until 6C and 7 perform the embodiment shown.

Note that in the embodiments of the present invention, descriptions like "first" and "second" are only used to distinguish between described objects and have no actual meaning. A portable electronic device is synonymous with a mobile terminal.

The functional modules in the embodiments of the present invention may be integrated into one processing unit/module, or each of the modules may physically stand alone, or two or more modules may be integrated into one module. The integrated module may be implemented in some form of hardware or may be implemented in some form of hardware in addition to a software entity.

It will be clear to those skilled in the art that, for the purpose of a concise and concise description, the breakdown of the aforesaid functional modules is given as an example for illustration. In actual application, the above functions can be assigned to different function modules and implemented as required, i.e. an internal structure of a device can be divided into different function modules to implement all or some of the functions described above. For a detailed working process of the device, reference is made to a corresponding process in the embodiments of the method. An implementation principle and a technical effect of the device are similar to those of the method embodiments, so a same or corresponding technical feature is not described again here.

Finally, it should be noted that the above embodiments only serve to describe the technical solutions of the present invention, not to limit the present invention. Although the present invention is described in detail with reference to the above embodiments, a person of ordinary skill in the art should understand that the technical solutions of the above embodiments can still be changed or some or all technical features can be equivalently substituted without to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims (11)

An electronic device comprising: a memory configured to store an instruction; a processor coupled to the memory, the instruction causing the electronic device to be configured to: receiving a first notification message, the first notification message including express delivery information; receiving a second notification message, the second notification message including a password of an express service kiosk and a location of the express service kiosk, the express service kiosk containing a physical express package specified by the express delivery information of the first notification message; associating the first notification message with the second notification message; and Presenting the express delivery information, password and location of the express service kiosk in a common interface. The electronic device after claim 1 , wherein the instruction further causes the electronic device to be configured to recognize when a first event related to the first notification message and a second event related to the second notification message are the same event. The electronic device after claim 2 , wherein the first notification message indicates that the same event is in a first status, wherein the second notification message indicates that the same event is in a second status, the memory being further arranged to store a status of the same event as the second saves status before receiving the first notification message, and wherein the instruction further causes the electronic device to be configured to update the status of the same event to the first status after receiving the first notification message. The electronic device after claim 3 , wherein the first status is in a flow of the same event, and wherein the instruction further causes the electronic device to be configured to notify a user that the status of the same event is the first status after the status of the same event has been updated to the first status. The electronic device after claim 1 , wherein the instruction further causes the electronic device to be configured to obtain a first semantic feature value of the first notification message, the first semantic feature value indicating a first semantic feature of the first notification message; obtain a second semantic feature value of the second notification message, wherein the second semantic feature value indicates a second semantic feature of the second notification message; and to determine that the second semantic feature value of the second notification message is equal or similar to the first semantic feature value of the first notification message. The electronic device after claim 1 , wherein the instruction further causes the electronic device to be configured to sequentially present the first notification message and the second notification message in the same interface based on a progression sequence of an event. The electronic device after claim 6 , wherein a first interface element is formed in the same interface that presents the first notification message and the second notification message, wherein the electronic device further comprises an input device which is coupled to the processor and configured to receive an input for triggering the first interface element by a to capture users, the instruction further causing the electronic device to be configured to invoke an application in accordance with the input to trigger the first interface element, and wherein a third semantic feature value of the application matches a first semantic feature value of the first notification message or a second semantic Feature value of the second notification message matches. The electronic device after claim 1 wherein the same interface in which the express delivery information and the password are presented comprises a first interface in a first application, a second interface in a second application, or a third interface generated by the electronic device. The electronic device after claim 1 , wherein the first notification message includes a first time and information about an action to be taken at the first time, the first time representing a future time, and wherein the instruction further causes the electronic device to be configured to: obtain the first time contained in the first notification message; and to generate an appointment reminder based on the first time and the information about the action to be taken at the first time, the appointment reminder reminding a user of the action to be taken at the first time prior to the first time. The electronic device after claim 1 wherein the first notification message includes a first location and information about an action to be taken at the first location, and wherein the instruction further causes the electronic device to be configured to: obtain a current location of the mobile device; and to generate a reminder item if the deviation between the current location of the mobile terminal and the first location is within a preset deviation range, the reminder item invoking the information about the action to be taken at the first location. The electronic device after claim 1 , wherein the semantic feature value of the first notification message comprises at least one of the following types: a type of the event, the status of the event, a time associated with the event, a location associated with the event, an order number associated with the event, an order number associated with the event related person, a time when the mobile terminal receives the first notification message, and a sender of the first notification message.

Images