Patent Description:
As mobile communication technologies are widely used in real life of people, more and more users choose to carry mobile terminals (such as a mobile phone or a tablet computer) as necessary communication device every day to receive short message services (Short Message Service, SMS for short below) from family members, friends or colleagues, receive and send emails (Email), answer and make phone calls (Phone Call), and so on. Especially, as smart phones and tablet computers are gradually popularized nowadays, mobile terminal users increasingly rely on the mobile terminals to handle daily businesses or life affairs, for example, use a mobile phone calendar to schedule meetings, use a mobile phone to store electronic business cards of others, or record various sorts of information in a notepad.

The mobile terminal users receive various messages (such as short message services, emails and contact calls) every day, and these messages may contain data such as telephone numbers, websites, Email addresses or electronic business cards in a vCard format; if the data need to be stored, in the conventional art, a mobile terminal user needs to store the data one by one manually into a memory of the mobile terminal through a graphical user interface (Graphical User Interface, GUI for short below) interface. Such a data processing method greatly reduces an intelligent interaction capability between a mobile terminal and a user, and also reduces data processing efficiency of the mobile terminal.

<CIT> provides a system and method for flexible data provision to mobile communication devices, which enables the user to selectively download data to the mobile communication device from a remote computer. The selective data download may optionally apply to one or more of a single item of data, to multiple items of data, one or more categories of data and the like.

<CIT> provides a method that comprises receiving a notification to share contact information for a contact in an address book of a sender with a recipient; retrieving the contact information for the contact; and delivering the contact information to the recipient.

<CIT> provides a method for generating electronic meeting communications for multiple formats and a messaging server adapted in accordance with the method, wherein the method comprises: receiving on the messaging server a first electronic meeting communication having a first meeting component in a first format, the first meeting component comprising event information; determining a second meeting component in a second format different from the first format, the second meeting component comprising substantially the same event information as the first meeting component; and sending a second electronic meeting communication comprising at least the first and second meeting components from the messaging server to one or more recipient devices.

Accordingly, embodiments of the present invention provide a method and a mobile terminal for processing data in a message, so as to solve a problem of a low intelligent interaction capability between a mobile terminal and a user, and low data processing efficiency in the conventional art.

The present application is defined in the appended independent claims. Further implementations are disclosed in the pending dependent claims.

The application provides a method for processing data in a message, including:.

With the embodiments of the present invention, related data, such as contact information, schedule information and text information, is intelligently extracted from a received message, and the data is stored into a corresponding function module, so that an intelligent interaction capability between a mobile terminal and a user is enhanced, and the transaction processing efficiency of the mobile terminal is improved.

To illustrate the technical solutions in the embodiments of the present invention or in the conventional art more clearly, the following briefly describes the accompanying drawings required for describing the embodiments or the conventional art. Apparently, the accompanying drawings in the following description merely show some embodiments of the present invention, and persons of ordinary skill in the art can derive other drawings from the accompanying drawings without creative efforts.

It should be noted that the invention is restricted to displaying first data in a first preset form and a first sender in a specific display form; and displaying second data in a second preset form and the first sender in the specific display form, wherein the first sender is comprised in an extracted first data attribute of the first data and in an extracted second data attribute of the second data. Therefore, the following examples, even if termed "embodiments", are not embodiments of the invention.

To make the objectives, features, and advantages of the present invention clearer, the following describes the embodiments of the present invention in detail with reference to accompanying drawings.

The terms used in the embodiments of the present invention are merely for the purpose of illustrating specific embodiments, and are not intended to limit the present invention. The terms "a", "said" and "the" of singular forms used in the embodiments and the appended claims of the present invention are also intended to include plural forms, unless otherwise specified in the context clearly. It should also be understood that, the term "and/or" used herein indicates and includes any or all possible combinations of one or more associated listed items.

Embodiment <NUM> of the present invention provides a method for processing data in a message, and referring to <FIG>, the method specifically includes the following steps:
Step <NUM>: A mobile terminal receives a message sent by a network side or another device, where the message carries data. For persons skilled in the art, the mobile terminal may communicate in a wireless manner with wireless networks, such as Internet (Internet), wireless local area networks (Wireless Local Area Networks, WLAN for short below) and cellular mobile phone networks, and with another device through various wireless communication protocols. Wireless communication may use any one of multiple communication standards, protocols and technologies. These communication standards, protocols and technologies include, but are not limited to, global system for mobile communication (Global System For Mobile Communication, GSM for short below), enhanced data rate for GSM evolution (Enhanced Data Rate for GSM Evolution, EDGE for short below), high speed downlink packet access (High Speed Downlink Packet Access, HSDPA for short below), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA for short below), code division multiple access (Code Division Multiple Access, CDMA for short below), time division multiple access (Time Division Multiple Access, TDMA for short below), Bluetooth standards, wireless fidelity (Wireless Fidelity, Wi-Fi for short below), protocols for emails (such as an Internet message access protocol (Internet Message Access Protocol, IMAP for short below) and a post office protocol (Post Office Protocol, POP for short below)), protocols for instant messaging presence services (Instant Massaging Presence Services, IMPS for short below), protocols for short message services (Short Message Service, SMS for short below), or any other standards, protocols and technologies applicable to wireless communication.

A mobile terminal may communicate in a wireless manner with a network side through the above various wireless communication standards, protocols and technologies, and may receive messages sent by the network side. These received messages include, but are not limited to, an email (Email), a short message service (SMS), and an instant message (Instant Message, IM for short below), and so on. The mobile terminal may also receive Bluetooth information or Wi-Fi information, where the Bluetooth information is packaged through a Bluetooth standard protocol by another mobile terminal or other equipments and the Wi-Fi information is sent through a Wi-Fi protocol by another mobile terminal or other equipments. Persons skilled in the art may learn that, a received message may carry data of multiple data types. For example, it could be data of two or more data types.

Step <NUM>: The mobile terminal identifies a data type of the data in the message.

After receiving each of the above messages, the mobile terminal parses the message, and may identify the data type of the data in the message. The data type refers to a format of the data, for example, the data type may be a TXT format, a vCard format, a vCalendar format, a BMP (Bitmap) format, a JPG format, an AVI (Audio Video Interleaved, AVI for short below) format, an RMVB (RealMedia Variable Bitrate, RMVB for short herein after) format, an MEPG (Moving Picture Experts Group, MPEG for short below) format, and so on.

The mobile terminal may identify the data type of the data in the message according to the conventional art. For example, the message is a short message service and carries data in the vCard format, and the mobile terminal may identify the data in the vCard format from the short message service.

The vCard is referred to as a virtual business card or an electronic business card (virtual business cards or electronic business cards), which is a file format standard of a contact electronic business card. The vCard may include information, such as a name, address information, a telephone number, URL (Uniform Resource Locator), logo, and a photo. The specification of the vCard allows public exchange of personal data interchange (Personal Data Interchange, PDI for short below) information. Data in the vCard format may be transmitted in any information through various wireless communication manners, for example, a message, such as an email or a short message service sent by the network side may also include data in the vCard format.

The mobile terminal identifies whether data in the vCard format is in the received SMS by parsing the received SMS and determining whether a "BEGIN:VCARD" character string is included in the message. Of course, persons skilled in the art may understand that, the mobile terminal may also identify whether data in the vCard format is in the message by parsing the received message and determining whether an "END:VCARD" character string is included in the message. The embodiment of the present invention does not limit the method for identifying data in the vCard format.

For another example, the message received by the mobile terminal may also include calendar data in the vCalendar format. An RFC <NUM> (Internet Calendaring and Scheduling Core Object Specification) is a standard of calendar data exchange; the RFC <NUM> defines content, such as a specific format of iCalendar or vCalendar (Virtual Calendar). Generally, the vCalendar allows a user to send a "meeting request" or "task" to an addressee through an email (Email). However, the vCalendar may also be used independently without being limited to a certain transmit protocol. For example, sharing and modification may be implemented through a WebDav server or a mobile data synchronization protocol (Synchronization Markup Language, SyncML for short below). A simple web server (HTTP protocol) is also usually used to distribute public event data in the vCalendar format, or release a personal time planning schedule.

By parsing the received message (such as an Email) and determining whether a "BEGIN:VCALENDAR" character string is included in the message, the mobile terminal identifies whether data in the vCalendar format is in the received email. Of course, persons skilled in the art may understand that, the mobile terminal may also identify whether data in the vCalendar format is in the received email by parsing the received message and determining whether an "END:VCALENDAR" character string is included in the message. The embodiment of the present invention does not limit the method for identifying data in the vCalendar format.

For another example, the mobile terminal receives a short message service, and may identify that the short message service includes data of a numeric character string type. For example, the short message service may include the following content: "Zhang San, my telephone number is changed to <NUM>. " and the mobile terminal may identify the numeric character string "<NUM>".

For another example, the mobile terminal receives a phone call (such as a missed call or an answered call) which is stored in a call log in the form of a telephone message. The mobile terminal may identify data in the call log.

For another example, the mobile terminal receives a multimedia messaging service (Multimedia Messaging Service, MMS for short below). The multimedia messaging service may deliver content of various formats; the information includes information in various multimedia formats, such as text, image, sound, and data. The mobile terminal may identify data of a TXT text file (Text File) in the multimedia messaging service through the file name extension ". TXT", and may identify data in image formats in the multimedia messaging service through image formats with file name extensions such as ". TIFF" and ".

Step <NUM>: The mobile terminal stores the data into a function module corresponding to the data type of the data according to a corresponding relationship list, where the corresponding relationship list is a list of correspondence between data types and function modules.

The data type refers to the format of the data, for example, the data type may be a TXT format, a vCard format, a vCalendar format, a BMP format, a JPG format, an AVI format, an RMVB format, an MEPG format, and so on. The function module refers to the module capable of storing the data of the above data types, and the function module is a part of an internal structure of the mobile terminal. For example, the mobile terminal is a mobile phone, and an address book module is stored in the memory of the mobile phone. Persons skilled in the art may learn that, the address book module may store data in a vcf (The Visual Component Framework, vcf for short below) format, and contact information is stored in the data in the vcf format. The contact information may be information, such as a name and a telephone number. Meanwhile, the address book module may also store data in the vCard format. For another example, a notepad module is stored in the memory, and the notepad module may store data in the TXT format. The correspondence between data types and function modules is stored in the corresponding relationship list, for example, the TXT format is corresponding to the notepad module; the vCard format is corresponding to the address book module; the BMP format and the JPG format are corresponding to an image management module; the AVI format, the RMVB format, and the MEPG format are corresponding to a player module.

Table <NUM> shows a list of correspondence between data types and function modules, where a function module is a part of the internal structure of the mobile terminal. Specifically, for example, a short message service may include data in the TXT format, and may also include data in the vCard format. When the mobile terminal identifies that the received short message service includes data in the vCard format, the type of data in the vCard format is corresponding to an address book module according to the corresponding relationship list <NUM>, and then the data in the vCard format is stored into the address book module. For example, when the mobile terminal identifies that the received message includes data in the TXT format, the type of data in the TXT format is corresponding to a notepad module according to the corresponding relationship list <NUM>, and then the data in the TXT format is stored into the notepad module. When the mobile terminal identifies that the data in the short message service is data in a numeric character string format, it is found that the data in the numeric character string format is corresponding to the address book module according to the corresponding relationship list <NUM> between data types and function modules, and then the data in the numeric character string format is stored into the address book module. For another example, when the mobile terminal identifies that the received message includes both data in the TXT format and data in the vCard format, the data in the TXT format is stored into the notepad module according to the corresponding relationship list <NUM>, and the data in the vCard format is stored into the address book module. Detailed description is provided in the subsequent steps.

For another example, the mobile terminal receives a phone call (such as a missed call or an answered call) which is stored in the call log (call log) in the form of a telephone message. The mobile terminal may identify data in the numeric character string format from the call log. According to the corresponding relationship list <NUM> between data types and function modules, it is found that the data in the numeric character string format is corresponding to the address book module, and then the data of the telephone message is stored into the address book module.

For another example, the mobile terminal receives an MMS message, and identifies that data in the image format (such as JPG, BMP, TIFF and GIF formats) is included in the multimedia messaging service through the image formats with the file name extensions ". GIF", and so on. The mobile terminal finds that data in the JPG format, the BMP format, the TIFF format, and the GIF format is corresponding to an image management module according to the corresponding relationship list <NUM> between data types and function modules, and then stores the data in the JPG format, the BMP format, the TIFF format, and the GIF format into the image management module.

For another example, the message received by the mobile terminal includes data in the AVI format. The mobile terminal finds that the data in the AVI format is corresponding to the player module according to the corresponding relationship list <NUM> between data types and function modules, and then stores the data in the AVI format into the player module.

In some other embodiments, the list of correspondence between data types and function modules may be stored at the network side or stored locally. When the corresponding relationship list is stored at the network side, the mobile terminal acquires, according to the identified data type of the data, information of a function module corresponding to the data type from the network side, and stores the data into the function module.

In some other embodiments, when the message includes data of multiple data types, identifying the data type of the data in step <NUM> may specifically include: identifying at least one data type of the data. Therefore, in step <NUM>, storing the data into the function module corresponding to the data type according to the corresponding relationship list may specifically include: storing the data of at least one data type into the function module corresponding to the data type according to the corresponding relationship list.

With the embodiment of the present invention, data of various data types, such as contact business card vCard, schedule information vCalendar, text information TXT is identified from the received message, and the data is stored into function modules related to the mobile terminal, thereby enhancing the intelligent interaction capability between the mobile terminal and the user, and also improving the transaction processing efficiency of the mobile terminal.

Optionally, as shown in <FIG>, after step <NUM>, the method of the embodiment may further include the following steps:
Step <NUM>: The function module prompts the user of the stored data according to a preset form.

For example, the function module may also be a calendar module. After the calendar module stores the data in the vCalendar format, a schedule is generated in the calendar module according to the preset form and a prompt is given to the user.

For example, the function module may also be a notepad module. After the notepad module stores the data in the TXT format, note information is generated in the notepad module according to the preset form and a prompt is given to the user.

In some other embodiments, the function module may also prompt the user of the stored data in the preset form according to a received operation command. The operation command may specifically command the function module to display the data. For example, specifically, the function module may be an address book module. After the address book module receives the operation command that commands the address book module to display the data, a contact is generated in an address book on the basis of the data in the vCard format and the numeric character string format, and a prompt may be given to the user according to a contact display form preset by the mobile terminal.

Optionally, as shown in <FIG>, after step <NUM> and before step <NUM>, the method may further include the following steps:
Step <NUM>: Determine whether data that is the same as the data is already stored in the function module; if the data is already stored, perform step <NUM>; if the data is not stored yet, perform step <NUM>.

Step <NUM>: Prompt the user, so that the user performs a management operation on the data. The prompting manner may specifically be: displaying a graphical user interface in a touch screen, prompting the user that the same data already exists in the function module, prompting the user whether to continue a storing operation, and so on. For example, the function module is specifically an address book module. After the address book module receives the data in the vCard format, a contact is generated in the address book on the basis of the data in the vCard format. Of course, it may be understood that, if information of the generated contact (such as a name and a mobile phone number) is the same as a contact already stored in the address book, the mobile terminal may prompt the user to perform a corresponding management operation, for example, prompt the user whether to continue storing the generated contact, and so on.

Step <NUM>: The mobile terminal receives, from the user, the command for performing a management operation on the data, and processes the data (for example, performing deletion processing on the data).

Optionally, step <NUM>, step <NUM>, step <NUM>, and step <NUM> may all exist in the method of the embodiment of the present invention, as shown in <FIG>, and the detailed process of the method is not described herein again.

Persons skilled in the art may learn that, a short message service, an Email and an instant message sent by the network side and received by the mobile terminal all have the same fields, for example, a sender field, an addressee field, a sending time field, a receiving time field, and a message content field.

Therefore, optionally, in some other embodiments, after step <NUM> and before step <NUM>, the method may further include the following step:
Step <NUM>: Extract a data attribute of the data from the message. The data attribute may specifically include a sender of the message, and may also specifically include the sender and the sending time of the message.

Therefore, the above step <NUM> may further include:
storing the data attribute of the data into the function module corresponding to the data type of the data. In this way, both the data and the data attribute of the data may be stored into the function module corresponding to the data type of the data.

In the embodiment of the present invention, the data attribute may specifically include the sender of the message, and may also specifically include the sender and the sending time of the message. For example, the mobile terminal receives a multimedia messaging service sent by the network side. The specific fields and content in the multimedia messaging service are shown in Table <NUM>.

After the mobile terminal parses the multimedia messaging service and identifies data in the GIF format and data in the TXT format in the multimedia messaging service, the data attribute (the sender, or the sender and the sending time) of the data in the GIF format and the data attribute of the data in the TXT format are extracted from the message. The data in the GIF format and the data attribute are stored into the function module corresponding to the data type of the data, and the data in the TXT format and the data attribute are stored into the function module corresponding to the data type of the data.

When the function module prompts the user of the stored data according to the preset form, the mobile terminal displays the data in the GIF format and TXT format, and also displays data attributes. A specific display form of a data attribute is not limited in the embodiment of the present invention, for example, the data attribute of the data in the TXT format and the data attribute of the data in the GIF format may be displayed as "a multimedia messaging service from Zhang San on Saturday, December <NUM>, <NUM>", or "from Zhang San", and so on.

The specific content in the data attribute may be preset by the mobile terminal, or may be set by the user. When data needs to be prompted to the user, the data attribute of the data may be prompted to the user. In this way, the user may intuitively learn the message source of the data, which is more beneficial to the intelligent interaction capability between the mobile terminal and the user, and meanwhile improves the use experience of the user.

In some other embodiments of the present invention, the data attribute of the data may be indicated by naming the file of the data. Still, the multimedia messaging service is taken as an example. After the data in the GIF format is identified, the file of the data is automatically named as "a multimedia messaging service from Zhang San on Saturday, December <NUM>, <NUM>", or "a multimedia messaging service from Zhang San", and so on.

The embodiment of the present invention provides a mobile terminal, and as shown in <FIG>, the mobile terminal specifically includes an RF (Radio Frequency) circuit <NUM>, a memory <NUM>, and a central processing unit <NUM>. The memory <NUM> includes at least one function module <NUM>.

The RF circuit <NUM> is configured to receive a message, where the message carries data. The message may include the data of multiple data types: data of two or more data types may be included. The message may specifically include an email, a short message service, or an instant message.

The central processing unit <NUM> is configured to identify the data type of the data in the message received by the RF circuit <NUM>, and store the data into a function module corresponding to the data type of the data according to a corresponding relationship list. The corresponding relationship list is a list of correspondence between data types and function modules. For detailed content of the corresponding relationship list, reference may be made to the related content in Embodiment <NUM>, and details are not described herein again.

The function module <NUM> is configured to store the data.

The function module <NUM> includes at least one of a notepad module, an address book module, a calendar module, an image management module or a player module.

Optionally, as shown in <FIG>, the central processing unit <NUM> specifically includes:.

Optionally, the mobile terminal may further include a display <NUM>, where the display <NUM> is configured to display the data stored in the function module <NUM> to a user according to an operation command of the central processing unit <NUM>.

It may be understood that, in the embodiment of the present invention, the received message may specifically be the short message service, instant message, email, short message service, and so on in Embodiment <NUM>, and the identified data may also be the data in the vCard format, the vCalendar format, the JPG format, the BMP format, the TIFF format, the GIF format and the TXT format in Embodiment <NUM>. It may be understood that, the specific technical solution in the method embodiment <NUM> may be implemented in the mobile terminal of the embodiment of the present invention. The specific technical solution is described in detail in Embodiment <NUM>, and is not described herein again.

In addition, it may be further understood that, the above function module <NUM> in the embodiment of the present invention may be a part in the memory, and it is also possible that the function module <NUM> and the memory <NUM> are two hardware structures independent of each other, and the embodiment of the present invention is not limited thereto.

As shown in <FIG>, a mobile phone is taken as an example in this embodiment to describe the present invention in detail.

It may be understood that, a mobile phone <NUM> shown in the figure is merely an example of a mobile terminal, and the mobile phone <NUM> may have components more or less than components shown in the figure, may combine two or more components, or may have different component configurations. Each component shown in the figure may be implemented through hardware including one or more signal processing circuits and/or dedicated integrated circuits, software or a combination of the hardware and software.

A mobile phone is taken as an example for detailed description. <FIG> is a schematic structural diagram of a mobile phone for processing a message according to Embodiment <NUM> of the present invention. As shown in <FIG>, the mobile phone includes a memory <NUM>, a central processing unit (Central Processing Unit, CPU for short below) <NUM>, a peripheral interface <NUM>, an RF circuit <NUM>, an audio circuit <NUM>, a loudspeaker <NUM>, a power management chip <NUM>, an input/output (I/O) subsystem <NUM>, other input/control equipments <NUM>, and an external port <NUM>; these components communicate through one or more communication buses or signal wires <NUM>.

It may be noted that, the mobile phone provided in the embodiment is merely an example of the mobile terminal. The mobile terminal involved in the embodiment of the present invention may have components more or less than components shown in <FIG>, may combine two or more components, or may have different component configurations or settings. Each component may be implemented in hardware including one or more signal processing circuits and/or dedicated integrated circuits, software or a combination of the hardware and software.

The mobile phone for processing a message provided by the embodiment is described in detail below.

The memory <NUM>: the memory <NUM> may be accessed by the CPU <NUM>, the peripheral interface <NUM>, and so on; the memory <NUM> may include a high speed random access memory, and may also include a nonvolatile memory, such as one or more disk memory devices, flash memory devices, or other volatile solid memory devices.

The peripheral interface <NUM>: the peripheral interface may connect input and output peripherals of the equipment to the CPU <NUM> and the memory <NUM>.

The I/O subsystem <NUM>: the I/O subsystem <NUM> may connect the input and output peripherals on the equipment, such as a touch screen <NUM> (which is equivalent to a display in the above embodiment) and other input/control equipments <NUM>, to the peripheral interface <NUM>. The I/O subsystem <NUM> may include a display controller <NUM> and one or more input controllers <NUM> for controlling other input/control equipments <NUM>. The one or more input controllers <NUM> receive electric signals from other input/control equipments <NUM> or send electric signals to other input/control equipments <NUM>; other input/control equipments <NUM> may include a physical button (press button, rocker button, and so on), a dial, a slide switch, an operation rod and a tap scroll wheel. It may be noted that, the input controller <NUM> may be connected to any one of a keypad, an infrared port, a USB interface, and an indication equipment such as a mouse.

A touch screen <NUM>: the touch screen <NUM> is the input interface and output interface between a mobile terminal and a user, and displays visual output to the user, where the visual output may include a graph, a text, an icon, a video, and so on.

The display controller <NUM> in the I/O subsystem <NUM> receives an electric signal from the touch screen <NUM> or sends an electric signal to the touch screen <NUM>. The touch screen <NUM> detects a touch on the touch screen. The display controller <NUM> converts the detected touch into interaction with a user interface object displayed on the touch screen <NUM>, that is, to implement human-machine interaction. The user interface object displayed on the touch screen <NUM> may be an icon for a running game, an icon for connecting to a corresponding network, and so on. It may be noted that, the equipment may further include an optical mouse. The optical mouse is a touch-sensitive surface that does not display visual output, or the extension of a touch-sensitive surface formed by the touch screen.

The RF circuit <NUM> is mainly configured to establish communication between the mobile phone and a wireless network (namely, a network side), so as to implement data receiving and transmitting between the mobile phone and the wireless network, such as receiving and sending a short message service and an email. Specifically, the RF circuit <NUM> receives and transmits an RF signal, where the RF signal is also referred to as an electromagnetic signal. The RF circuit <NUM> converts an electric signal into an electromagnetic signal or converts an electromagnetic signal into an electric signal, and communicates with a communication network or another equipment through the electromagnetic signal. The RF circuit <NUM> may include known circuits for performing these functions, which include, but are not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chip set, and a subscriber identity module (Subscriber Identity Module, SIM).

The audio circuit <NUM> is mainly configured to receive audio data from the peripheral interface <NUM>, convert the audio data into an electric signal, and send the electric signal to the loudspeaker <NUM>.

The loudspeaker <NUM> is configured to restore an audio signal received from the wireless network by the mobile phone through the RF circuit <NUM> into a sound and play the sound to the user.

The power management chip <NUM> is configured to supply power to the CPU <NUM>, the I/O subsystem and the hardware connected to the peripheral interface, and perform power management.

<FIG> is a structural diagram of an interior of the mobile phone. In the embodiment of the present invention, software components stored in the memory <NUM> may include an operating system <NUM>, a communication module <NUM>, a touch/move module <NUM>, a graphic module <NUM> and a function module <NUM>.

The operating system <NUM> (for example, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or embedded operating systems such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (for example, memory management, memory equipment control, power management, and so on), and facilitates communication between various hardware and software components.

The communication module <NUM> facilitates communication with another equipment through one or more external ports <NUM>, and also includes various software components for processing data received by the RF circuit <NUM> and/or the external port <NUM>.

The touch/move module <NUM> may detect a touch on the touch screen <NUM> (interacting with the display controller <NUM>) and other touch-sensitive equipments (such as a touch pad or physical click scroll wheel). The touch/move module <NUM> includes various software components for performing various operations related to touch detection. The foregoing operations may be, for example, determining whether a touch occurs, determining whether the touch moves and tracking the movement on the touch screen <NUM>, and determining whether the touch is disconnected (that is, whether the touch is ended). The determining the movement of a touch point may include determining a rate (amplitude), a speed (amplitude and direction) and/or an accelerated speed (change of amplitude and/or direction) of a touch point. These operations may be applied to a single touch (for example, touch with one finger) or multiple synchronous touches (for example, "multiple touches" /multi-finger touch). In some embodiments, the touch/move module <NUM> and the display controller <NUM> further detect touches on a touch pad.

The graphic module <NUM> includes various known software components for displaying graphs on the touch screen <NUM>, including components for changing brightness of the displayed graphs, for example, receiving a command from the central processing unit <NUM> and displaying graphic user interfaces of various software on the touch screen <NUM>.

The function module <NUM> may specifically include at least one of the following modules:.

The RF circuit <NUM> receives a message sent by the network side or by another equipment, where the message includes an email, a short message service or an instant message, and specifically, the message may be the message in Embodiment <NUM> or Embodiment <NUM>. It may be understood that, the received message may also be a message of another type, which is not limited in the embodiment of the present invention. Persons skilled in the art may learn that, the received message may carry data of various data types. It may be data of two or more data types.

The central processing unit <NUM> identifies the data type of the data in the message received by the RF circuit <NUM>, and stores the data into a function module corresponding to the data type of the data according to a corresponding relationship list, where the corresponding relationship list is a list of correspondence between data types and function modules. The function module <NUM> may specifically be at least one of the address book module <NUM>, the image management module <NUM>, the player module <NUM>, the calendar module <NUM> and the notepad module <NUM>. It may be understood that, in the embodiment of the present invention, the central processing unit <NUM> may identify data in various formats in the manner described in the foregoing embodiments, and details are not described herein again.

Specifically, for example, if the central processing unit <NUM> identifies that a short message service includes data in a vCard format, a TXT format, a JPG format and an AVI format, then according to the corresponding relationship list <NUM> (as the corresponding relationship list <NUM> described in Embodiment <NUM>), the central processing unit <NUM> sends the data in the vCard format to the address book module <NUM>, sends the data in the TXT format to the notepad module <NUM>, sends the data in the JPG format to the image management module <NUM>, and sends the data in the AVI format to the player module <NUM>. Each of the above function modules stores the data forwarded by the central processing unit <NUM>. It may be understood that, after receiving an operation command from the central processing unit <NUM>, the function module <NUM> may display the data on the touch screen <NUM> according to a preset form through the graphic module <NUM>, so that the user performs a specific operation on the data.

Optionally, the central processing unit <NUM> may extract a data attribute of the data from the received message. The data attribute may specifically include a sender of the message, and may also specifically include the sender and the sending time of the message. The central processing unit <NUM> may send the data of various data types and the data attribute of the data to the function module <NUM> corresponding to the data type of the data. The touch screen <NUM> may display the data and the data attribute of the data in the preset form on the touch screen <NUM> through the graphic module <NUM> according to the operation command of the central processing unit <NUM>. The specific technical solution is described in detail in Embodiment <NUM>, and details are not described herein again.

Optionally, the central processing unit <NUM> may determine whether the data to be forwarded is already stored in the function module <NUM>. If the central processing unit <NUM> determines that the data is already stored in the function module <NUM>, the central processing unit <NUM> does not forward the data; if the data is not yet stored in the function module <NUM>, the central processing unit <NUM> forwards the data to the function module <NUM>. The central processing unit <NUM> may command the graphic module <NUM> to invoke a GUI interface, command the display controller <NUM> to control the touch screen <NUM> to display the GUI interface and prompt the user of information, where the prompt information is specifically used to prompt the user that the data is already stored in the function module <NUM>, prompt the user whether to perform subsequent management operations, such as combining data and deleting data. It may be understood that, the specific internal structure of the central processing unit <NUM> may be the same as the specific structure form in Embodiment <NUM>, and details are not described herein again.

In the above embodiment, the central processing unit <NUM> may be a Pentium processor or an Itanium processor manufactured by the Intel Corporation.

With the embodiment of the present invention, related data, such as a contact business card, schedule information and text information, is intelligently extracted from the received message, and a prompt is given to the user in a related application program, thereby enhancing the intelligent interaction capability between the mobile terminal and the user and improving the transaction processing efficiency of the mobile terminal.

In the above embodiments of the present invention, the mobile terminal includes, but is not limited to, a mobile communication equipment, such as a mobile phone, a personal digital assistant (Personal Digital Assistant, PDA) and a tablet.

Claim 1:
A method for processing data in a message, comprising:
receiving (<NUM>) a message sent by a first sender, wherein the message comprises first data in a first data type and second data in a second data type;
identifying (<NUM>) the first data type of the first data and the second data type of the second data;
extracting (<NUM>) a first data attribute of the first data from the message and a second data attribute of the second data from the message, wherein the first data attribute comprises the first sender of the message and the second data attribute comprises the first sender of the message;
storing (<NUM>) the first data in the first data type in a corresponding first function module and the second data in the second data type in a corresponding second function module according to a corresponding relationship, wherein the corresponding relationship comprises correspondence between data types and function modules;
displaying (<NUM>) the first data in a first preset form and the first sender in a specific display form; and
displaying (<NUM>) the second data in a second preset form and the first sender in the specific display form.