JP2014107636A - History management apparatus, history management method, portable terminal device and computer program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To present a big-picture view of communications for each of topics even in the case where a plurality of kinds of communication means such as voice call and electronic mail are mixed.SOLUTION: A history management apparatus 1 comprises: a thread generation section 2 in which, in the case where a custom header is included in a first message 101 (MSG1), on the basis of information on a second message (MSG2) acquired from the custom header, a data group forming a hierarchical structure with the MSG2 as a parent and the MSG1 as a child is generated; and a message creation section 3 which creates a third message generated by executing custom header generation processing on the basis of third communication means information 104 used for transmitting a reply to the MSG1, a message ID 103 identifying the MSG1, and first communication means information 102 used for transmitting/receiving the MSG1, and storing the created third message in a message database 5.

Description

  The present invention relates to a technical field for managing messages transmitted and received between electronic devices, for example.

  Commonly known communication support devices such as smartphones and mobile phones include a plurality of communications such as voice calls (hereinafter simply referred to as “calls”) and e-mails (hereinafter simply referred to as “mails”). There are devices that support the means.

  For example, the user may make an answer to a communication item notified by e-mail by voice call. On the other hand, there are cases where the user develops a summary of the contents spoken in the voice call by e-mail.

  As described above, communication means such as voice calls and e-mails may be used in a mixed manner depending on the usage status of the user.

  Furthermore, for example, the history of voice calls, e-mails, etc. is generally managed for each communication means (that is, separately).

  Against this background, there is a need to integrate and manage message histories via a plurality of communication means.

  Here, as a related technique existing prior to the application of the present application, Patent Document 1 discloses a technique related to display of different types of transmission information that are threaded together.

  More specifically, the method disclosed in Patent Document 1 defines a group including a user or a telephone as a member who exchanges voice calls and text mails, and manages the defined group in association with each message. To do.

  Furthermore, the method disclosed in Patent Document 1 extracts a history of messages (voice calls and text mails) associated with the same group. In this method, the extracted history is displayed in the order of occurrence time of the history.

  As a result, the method disclosed in Patent Document 1 can grasp the overall image of exchanges via a plurality of communication means such as voice calls and text mails.

  That is, the method disclosed in Patent Document 1 can grasp how the exchange has progressed with the counterparts constituting the group.

  Patent Document 2 discloses a technique related to a mobile terminal device, a screen display method, and a program.

  More specifically, the apparatus disclosed in Patent Document 2 displays a response screen that allows the user to select either telephone call or mail transmission as a response to the caller when a call is received.

  Next, the apparatus disclosed in Patent Document 2 executes the operation selected on the response screen. Further, Patent Document 2 displays a history of incoming / outgoing calls and mail transmission / reception exchanged for each communication partner in order of time.

  Patent Document 3 discloses a technology related to a telephone terminal and a communication history management method for the telephone terminal.

  More specifically, the terminal disclosed in Patent Document 3 gives a request ID (identifier: hereinafter referred to as “ID”, also referred to as “identifier”) to calls and e-mails.

  Furthermore, this terminal extracts the outgoing / incoming calls and e-mail transmission / reception histories of calls having the same business ID, and displays the extracted transmission / reception histories.

  And when the terminal transmits a call or transmits an e-mail, it is necessary to assign a business ID according to an instruction from the operator.

  Next, Patent Document 4 discloses a technology related to an information terminal, a server, an information display system, and an information display method.

  More specifically, the terminal disclosed in Patent Document 4 records communication histories by a plurality of communication means in the history management unit and holds the communication histories.

  Furthermore, this terminal records the processing status for the communication history held in the history management unit in the information management table in the information terminal or server, and holds the processing status.

  That is, in the terminal disclosed in Patent Document 4, for example, when a history is designated by the user and a reply process is performed on the designated history, the processing status performed is stored in the information management table.

  The terminal disclosed in Patent Literature 4 displays the history information held in the history management unit and the processing status for the history information held in the information management table in association with each other by the information history list display unit.

  Thus, according to Patent Document 4, for example, the user can confirm whether or not a reply process has been performed on the communication history in the information terminal or the server.

Special table 2012-504905 gazette JP 2009-273026 A JP 2010-283704 A WO01 / 035229

  By the way, in a generally known electronic mail system, for example, a relationship between a received mail (hereinafter abbreviated as “received mail”) and a reply to the received mail is a thread (that is, mail belonging to one topic, Management and display as a summary of remarks.

  As a result, the electronic mail system can easily grasp the overall image of the communication belonging to the topic.

  However, in such an e-mail system, for example, when a user uses a communication means different from mail such as mail and voice call, the relationship between the reply between the received mail and the incoming call in voice call is managed as a thread. It is difficult to display.

  The technique disclosed in Patent Literature 1 cannot display a history for each of a plurality of topics when a plurality of topics progress in an exchange with a partner defined in the same group.

  More specifically, as an example, when a plurality of topics that are not related to each other are performed in parallel with the same partner, Patent Document 1 does not display a history of exchange for each topic.

  That is, in the technique disclosed in Patent Document 1, the history of exchanges related to the same defined group is mixed and arranged in time order. Therefore, in Patent Document 1, it is not possible to recognize the overall image of the exchange for each topic.

  Further, Patent Document 2 only describes that the outgoing and incoming calls and mail transmission / reception histories exchanged for each communication partner are mixed and displayed in time order. It is not described how to display the history of transmission / reception in a mixed manner for each topic.

  For example, in addition to operations for making and receiving calls and sending and receiving e-mails, the operator in Patent Document 3 requires an instruction for assigning a business ID to a call and e-mail.

  For this reason, the operator in Patent Document 3 has time to give a business ID. Further, such an operator has a problem that the operation becomes complicated.

  In the technique disclosed in Patent Document 4, when a reply process is performed on a history, the process is recorded in an information management table in the own apparatus and the processing status is held.

  That is, Patent Document 4 only describes that the reply process for the communication history performed in the own apparatus is described, and the reply process for the communication history performed in another apparatus different from the own apparatus can be confirmed. Can not.

  More specifically, as an example, it is assumed that the user A in Patent Document 4 has replied to the message A received from the user B by voice call.

  Next, the user B transmits a message B to the user A in response to the reply by the voice call. Further, it is assumed that user A has received message B from user B.

  In this case, the user A in Patent Document 4 can confirm that the reply to the message A has been made by a voice call, but cannot confirm that the message B is a reply to the voice call.

  The reason is that in the technique disclosed in Patent Document 4, the reply to the message A by the user A is recorded in the information management table, while the message B is a reply to the voice call. This is because they are not recorded in the information management table.

  Thus, it is difficult for the information display system in Patent Document 4 to grasp the overall image of the exchange for each topic.

  A main object of the present invention is to provide a history management device or the like that can present an overall image of exchange for each topic even when a plurality of communication means such as voice calls and electronic mails coexist.

  In order to achieve the above object, a history management apparatus according to the present invention has the following configuration.

That is, the history management device according to the present invention is
The first message is stored in the database, and it is determined whether or not a custom header is included in the header of the first message. If the custom header is included, the second message obtained from the custom header is stored. The second message is extracted from the database based on the second communication means information used for transmission / reception of the message and the message ID for identifying the second message, and the extracted second message is A thread generation unit that generates a data group having a hierarchical structure in which the first message is associated with the first message as a child of the parent, and a third used when a third message is transmitted as a reply to the first message. Communication means information and a message ID for identifying the first message And generating the custom header that differs according to the third communication means information by executing a custom header generation process based on the first communication means information used when the first message is transmitted / received And a message creating unit for creating the third message including the custom header and storing the created third message in the database.

  Alternatively, the same object can be achieved by a portable terminal device including the history management device described above.

  In order to achieve the object, the history management method according to the present invention is characterized by having the following configuration.

That is, the history management method according to the present invention includes:
The first message is stored in the database, and it is determined whether or not a custom header is included in the header of the first message. If the custom header is included, the second message obtained from the custom header is stored. The second message is extracted from the database based on the second communication means information used for transmission / reception of the message and the message ID for identifying the second message, and the extracted second message is Third communication means information used when generating a data group having a hierarchical structure in which the first message is associated with the first message as a child of the parent and transmitting the third message as a reply to the first message A message ID for identifying the first message, and the first message. The custom header generation process is executed based on the first communication means information used when the message is transmitted / received, thereby generating a different custom header according to the third communication means information. The third message including a header is created, and the created third message is stored in the database.

  The same object is achieved by a history management device and a history management method having the above-described configurations, a computer program for realizing the mobile terminal device by a computer, and a readable storage medium in which the computer program is stored. Is also achieved.

  According to the present invention, even when a plurality of communication means such as voice calls and e-mails coexist, it is possible to present an overall image of exchange for each topic.

It is a block diagram which shows the structure of the log | history management apparatus in the 1st Embodiment of this invention. It is a block diagram which shows the structure of the log | history management apparatus in the 2nd Embodiment of this invention. It is a block diagram which illustrates the structure of the portable terminal device containing the log | history management apparatus in the 3rd Embodiment of this invention. It is a flowchart which shows the operation | movement at the time of receiving the 1st message which the portable terminal device in the 3rd Embodiment of this invention performs. It is a flowchart which shows the operation | movement at the time of transmitting the 3rd message which the portable terminal device in the 3rd Embodiment of this invention performs. It is a flowchart which shows the operation | movement of the custom header production | generation process which the 1st message preparation part in the 3rd Embodiment of this invention performs. It is a figure explaining operation | movement of the custom header production | generation process which the 1st message preparation part in the 3rd Embodiment of this invention performs. It is the figure which illustrated notionally the message database in the 3rd Embodiment of this invention. It is a figure which illustrates notionally the thread | sled displayed using the display part in the Example which concerns on the 3rd Embodiment of this invention. It is a figure which illustrates the header containing custom header CH contained in the 6th message in the example concerning the 3rd embodiment of the present invention. It is a figure which illustrates the header containing the custom header CH contained in the 8th message in the Example which concerns on the 3rd Embodiment of this invention. It is a block diagram which illustrates the structure of the log | history management apparatus in the 4th Embodiment of this invention. It is a block diagram explaining illustratively the hardware constitutions of the portable terminal which can realize each embodiment concerning the present invention.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  First, the description "communication means" is used in the following description and the drawings referred to in the description, but this is not a description including a so-called patent technical meaning, but is generally known when used for communication. It is a collective term for electronic mail, voice call, voice mail, and the like (the same applies to the following embodiments and claims).

<First Embodiment>
FIG. 1 is a block diagram showing the configuration of the history management apparatus 1 according to the first embodiment of the present invention.

  In FIG. 1, the history management apparatus 1 includes a thread generation unit 2 and a first message creation unit 3.

  More specifically, the thread generation unit 2 is configured to send a message (first message) transmitted by a plurality of communication means via a communication network (not shown) (hereinafter, “communication network” is simply abbreviated as “network”). Message 101) is received.

  In the following description, for convenience of description, the received message is referred to as a first message 101 as an example.

  A message transmitted / received before receiving the first message 101 (that is, past the time when the first message 101 was received) is referred to as a second message (the same applies to the following embodiments).

  Note that the first message 101 and the second message will be described later in the third embodiment.

  The thread generation unit 2 stores the received first message 101 in the message database 5 for each communication means (the message database 5 will be described later in the third embodiment).

  Next, the thread generation unit 2 determines whether or not the received first message 101 includes information indicating a reply (that is, a reply) to the second message.

  That is, the thread generation unit 2 determines whether or not the custom header CH is included in the header of the first message 101.

  Here, the custom header CH includes a message identifier for identifying the second message (hereinafter referred to as “ID”, and also referred to as “second message ID” for convenience of description) and the second message. Information including communication means information used for transmission / reception (hereinafter referred to as “second communication means information” for convenience of explanation) is stored (described). (It will be described later in the form).

  That is, the thread generation unit 2 can determine whether or not the first message 101 is a reply message of the second message by analyzing the custom header CH in the received first message 101.

  When the thread generation unit 2 determines that the custom header CH is included in the first message 101, the thread generation unit 2 extracts the first reply information from the custom header CH included in the header in the first message 101.

  Here, the first reply information includes a message ID for identifying the second message included in the custom header CH and second communication means information used when the second message is transmitted / received ( The same applies to the following embodiments).

  The message ID is a Message-Id or SIP (Session_Initiation_Protocol: hereinafter referred to as “SIP”) message (that is, a session start message in a voice call) included in a header of a currently known e-mail or the like. This is an ID for uniquely identifying a message such as Call-id included in the header. Therefore, detailed description in this embodiment is omitted (the same applies to the following embodiments).

  In addition, since the SIP technology itself in the voice call according to the present embodiment can now employ a general technology, detailed description in the present embodiment is omitted (the same applies to the following embodiments).

  The thread generation unit 2 stores the second message stored in the message database 5 based on the message ID for identifying the second message included in the first reply information extracted from the custom header CH and the second communication means information. And the retrieved second message is extracted.

  As a result, the thread generation unit 2 uses the searched second message as a parent and the hierarchical structure (hereinafter also referred to as “tree structure”) associated with the received first message 101 as a child of the parent. Create a data group.

  That is, the thread generation unit 2 creates a thread by using the retrieved second message as a parent and associating the received first message 101 as a child of the parent.

  More specifically, as an example, the thread is configured in the form of a thread having a parent-child relationship between the message reply source and the reply.

  In the embodiment described above, for convenience of explanation, as an example, the thread generation unit 2 has described an example in which a thread is configured based on the retrieved second message and the received first message 101. However, the present invention is not limited to such a configuration, and the thread generation unit 2 uses a thread based on the information stored in the header of the second message and the information stored in the header of the first message 101. Or a thread may be created based on information stored in the custom header CH included in the header of the first message 101 (the same applies to the following embodiments).

  The thread generation unit 2 provides the user with the thread by outputting the created thread to a display unit (not shown) such as a generally known display (for example, the display unit 31 shown in FIG. 3).

  Thereby, for example, the user can confirm the whole image of the exchanged message in the form of a thread. For this reason, the user can more easily understand the context and overall relationship of messages.

  Next, the storage unit 4 has a message database 5.

  More specifically, the storage unit 4 is a readable / writable storage device. More specifically, as an example, the storage unit 4 is a nonvolatile storage such as a flash memory (Flash_memory) or a hard disk drive (Hard_disk_drive: hereinafter referred to as “HDD”) mounted on an electronic device such as a portable terminal device or a server. An element can be employed.

  For example, the storage unit 4 may employ a storage device (not shown) connected to a network (not shown). However, the present invention described using this embodiment as an example is not limited to these (the same applies to the following embodiments).

  Next, the first message creation unit 3 acquires the first communication means information 102, the message ID 103 (hereinafter also referred to as “first message ID” for convenience of explanation), and the third communication means information 104 ( The operation when receiving) will be described in detail.

  In the following description, for convenience of explanation, as an example, a message transmitted as a reply to the first message 101 is referred to as a third message (the same applies to the following embodiments).

  The first message creation unit 3 receives the first communication means information 102, the message ID 103, and the third communication means information 104.

  Here, the third communication means information 104 is information indicating a communication means used when a third message is transmitted / received as a reply to the first message 101.

  The message ID 103 is an ID that uniquely identifies the first message 101. Further, the first communication means information 102 is communication means information used when the first message 101 is transmitted / received.

  More specifically, as an example, the first communication means information 102, the second communication means information, and the third communication means information 104 are set to “email” when a message is transmitted and received using e-mail. . The first communication means information 102, the second communication means information, and the third communication means information 104 are “sip” when making and receiving calls using voice calls.

  In the embodiment described above, for convenience of explanation, as an example, the first communication means information 102, the second communication means information, and the third communication means information 104 are assumed to be “email” or “sip”. did. However, the present invention is not limited to such a configuration, and the first communication means information 102, the second communication means information, and the third communication means information 104 may be configured using flags (the following implementations). The same applies to the form).

  In that case, as an example, the first communication means information 102, the second communication means information, and the third communication means information 104 are set to “0” when a message is transmitted / received using an electronic mail, It may be set to “1” when a call is made / received. However, the present invention described using this embodiment as an example is not limited to these (the same applies to the following embodiments).

  The first message creation unit 3 creates a different custom header CH according to the type of the third communication unit information 104 based on the message ID 103 and the first communication unit information 102 (by the first message creation unit 3). The operation for generating the custom header CH will be described later in the third embodiment).

  The first message creation unit 3 creates a reply message (third message) based on the third communication means information 104 by embedding the generated custom header CH in the header of the third message.

  Further, the first message creation unit 3 stores the created third message in the message database 5 and transmits the third message via a network (not shown).

  As described above, according to the history management apparatus 1 according to the present embodiment, even when a plurality of communication means such as a voice call and an electronic mail are mixed, an overall image of exchange can be presented for each topic.

  The reason is that the history management apparatus 1 stores the relationship between the reply source and the reply destination as a custom header CH in the header which is control information of each communication means when transmitting a message, and the stored custom header. It has a function to convey to the destination by including CH in the header of the message.

  Furthermore, when receiving the message, the history management device 1 identifies the relationship between the reply source and the reply by analyzing the custom header CH included in the message, and sets the reply source and the reply to the thread. This is because it has a function of displaying depending on the form.

<Second Embodiment>
Next, a second embodiment based on the history management device 1 according to the first embodiment of the present invention described above will be described. In the following description, the characteristic part according to the present embodiment will be mainly described. At this time, the same reference numerals are assigned to the same configurations as those in the above-described embodiments, and duplicate descriptions are omitted.

  A history management apparatus 10 according to a second embodiment of the present invention will be described with reference to FIG.

  FIG. 2 is a block diagram showing the configuration of the history management apparatus 10 according to the second embodiment of the present invention.

  In FIG. 2, the history management apparatus 10 further includes a message selection unit 11 in addition to the history management apparatus 1 described in the first embodiment.

  For example, when the message selection unit 11 replies to a desired message, the user selects a desired message (for example, the first message) from a thread displayed on a display unit (not illustrated) (for example, the display unit 31 illustrated in FIG. 3). 1 is detected.

  Furthermore, the message selection unit 11 displays (presents) the communication means used for the reply using the display unit in response to detecting such an operation.

  Here, the message selection unit 11 displays one or more communication means using a display unit.

  Next, for example, when the user selects one communication unit from among a plurality of communication units displayed using a display unit (not shown), the message selection unit 11 detects the selected operation.

  Thereby, for example, the user can select the first message 101 from the thread displayed using the display unit. Further, the user can select a desired communication means to be used when transmitting a reply message (that is, a third message) to the first message 101 from a plurality of communication means displayed using the display unit. .

  That is, when replying to the first message 101, the user can easily select a communication means (that is, a communication means such as e-mail or voice call).

  The message selection unit 11 acquires a message ID (that is, the message ID 103) associated with the message desired by the user (first message 101) from the thread by detecting the user's operation.

  Further, the message selection unit 11 generates communication means information desired by the user (third communication means information 104) by detecting a user operation.

  The message selection unit 11 searches the message database 5 based on the acquired message ID 103 to acquire the first communication means information 102 associated with (associated with) the message ID 103.

  More specifically, the message selection unit 11 searches the message database 5 based on the acquired message ID 103.

  Next, the message selection unit 11 extracts the first message 101 associated (associated) with the acquired message ID 103.

  Further, the message selection unit 11 determines the type of header in the extracted first message 101.

  The message selection unit 11 determines the communication means used when the first message 101 is transmitted / received, and generates the first communication means information 102 based on the determined communication means.

  In the above-described embodiment, for convenience of explanation, as an example, the message selection unit 11 determines the type of header in the first message 101 to thereby use the communication means used when the first message 101 is transmitted and received. An example of determining the above has been described. However, the present invention is not limited to such a configuration, and the message selection unit 11 may determine the communication means based on the acquired message ID 103 or based on information included in the header of the first message 101. Thus, the communication means may be determined (the same applies to the following embodiments).

  In the embodiment described above, for convenience of explanation, as an example, the message selection unit 11 extracts the first message 101 from the message database 5 based on the acquired message ID 103, and extracts the first message 101 extracted. The configuration of acquiring the first communication means information 102 from the header in FIG. However, the present invention is not limited to such a configuration, and the message selection unit 11 may acquire the first message 101 itself from the message database 5 based on the acquired message ID 103. The message ID 103 and the first communication means information 102 may be acquired from the thread, or a configuration in which the header information in the first message 101 is acquired from the thread may be employed.

  When acquiring the first message 101 itself, the message selection unit 11 may acquire the first communication means information 102 from the header in the first message 101.

  Further, when the message ID 103 and the first communication means information 102 and the header of the first message 101 are acquired from the thread, the message ID 103 and the first communication means information 102 may be added to the thread. The first message 101 itself may be added to. However, the present invention described using this embodiment as an example is not limited to these (the same applies to the following embodiments).

  The message selection unit 11 transmits the first communication means information 102, the message ID 103, and the third communication means information 104 to the first message creation unit 3.

  The operation when the first message creation unit 3 receives the first communication means information 102, the message ID 103, and the third communication means information 104 is the same as the operation described in the first embodiment. . Therefore, the overlapping description is omitted.

  As described above, according to the history management apparatus 10 according to the present embodiment, the effect described in the first embodiment described above can be enjoyed, and a desired message can be easily selected from the thread. Further, for example, the user can easily select a desired communication means from one or more communication means.

  The reason is that, for example, when the user transmits a reply message for a desired message, the message selection unit 11 in the history management apparatus 10 detects one or more operations according to detection of an operation for selecting the desired message from the thread. This is because communication means can be presented.

<Third Embodiment>
Next, a third embodiment based on the history management device according to each embodiment of the present invention described above will be described. In the following description, the characteristic part according to the present embodiment will be mainly described. At this time, the same reference numerals are assigned to the same configurations as those in the above-described embodiments, and duplicate descriptions are omitted.

  A history management apparatus 20 according to the third embodiment of the present invention will be described with reference to FIGS.

  FIG. 3 is a block diagram illustrating the configuration of the mobile terminal device 30 including the history management device 20 according to the third embodiment of the invention.

  In FIG. 3, the mobile terminal device 30 roughly includes a history management device 20, a storage unit 4, a display unit 31, and a communication unit 32.

  More specifically, the history management apparatus 20 further includes a custom header analysis unit 21 in the history management apparatus 10 described in the second embodiment.

  The mobile terminal device 30 applies the history management device 20 to a commonly known mobile terminal device such as a smartphone or a mobile phone.

  The communication unit 32 communicatably connects to, for example, a mobile terminal device 30 different from its own device via the communication network 110 (hereinafter, “communicatively connected” is simply referred to as “connection” in the present application).

  The communication network 110 is a general communication line such as, for example, various communication lines owned by a mobile phone operator, the Internet provided by an Internet service provider, or the like. However, the present invention described using this embodiment as an example is not limited to these (the same applies to the following embodiments).

  The display unit 31 is a generally known display or the like.

The custom header analysis unit 21 and the thread generation unit 22 correspond to the thread generation unit 2 in each embodiment described above.

  That is, the custom header analysis unit 21 and the thread generation unit 22 share the operation in the thread generation unit 2.

  More specifically, a more specific operation of the history management apparatus 20 according to the third embodiment of the present invention will be described.

  FIG. 4 is a flowchart illustrating an operation when the mobile terminal device 30 according to the third embodiment of the present invention receives the first message 101. The operation procedure of the mobile terminal device 30 will be described along the flowchart.

  Here, as an example, the operation when the mobile terminal device 30 receives the first message 101 via the communication network 110 will be described in detail.

Step S1:
The custom header analysis unit 21 receives the first message 101 via the communication unit 32 and stores the received first message 101 in the message database 5 for each communication means.

  In the following description, the messages (first message 101, second message, and third message) are, for example, an e-mail message, a SIP message (that is, a session start message in a voice call), or the like. However, the present invention described using this embodiment as an example is not limited to these (the same applies to the following embodiments).

  Note that generally known voice mail is realized by attaching a voice file to an electronic mail. Therefore, the voice mail is included in the electronic mail message.

Step S2:
The custom header analysis unit 21 determines whether or not the received first message 101 includes information indicating a reply. That is, the custom header analysis unit 21 determines whether or not the custom header CH is included in the header of the first message 101.

“NO” in step S3:
As a result of determining whether or not the custom header CH is included in the header of the first message 101, the custom header analysis unit 21 determines that the custom header CH is not included (that is, there is no custom header CH). In this case, the first message 101 is transmitted to the thread generation unit 22, and the process proceeds to step S6.

  That is, in this case, it means that the first message 101 is not a reply message for the second message that has already been transmitted and received.

“YES” in step S3:
As a result of determining whether or not the custom header CH is included in the header of the first message 101, the custom header analysis unit 21 determines that the custom header CH is included (that is, the custom header CH is present). If so, the process proceeds to step S4.

  That is, in this case, it means that the first message 101 is a reply message for the second message that has already been transmitted and received.

Step S4:
The custom header analysis unit 21 extracts and extracts the first reply information (message ID and second communication means information in the second message) described in the custom header CH from the header in the first message 101. The first reply information is transmitted to the thread generation unit 22.

  More specifically, as an example, when the first message 101 is an e-mail message, the first reply information is an optional header “X−” described in the custom header CH included in the header of the first message 101. It is stored (described) in the “UC-In-Reply-To” field.

  For example, when the first message 101 is a SIP message requesting the start of a voice call (that is, an INVITE request in SIP), the first reply information is a custom included in the header of the first message 101. It is stored (described) in the optional header “P-UC-In-Reply-To” field described in the header CH.

Step S5:
The thread generation unit 22 searches the second message stored in the message database 5 based on the first reply information received from the custom header analysis unit 21 and extracts the searched second message.

  More specifically, the thread generation unit 22 searches the message database 5 based on the message ID and the second communication means information in the second message included in the first reply information, and the searched second Extract messages.

Step S6:
The thread generation unit 22 creates a thread by using the searched second message as a parent and associating the received first message 101 as a child of the parent.

  On the other hand, when there is no second message (that is, “NO” in step S3), the thread generation unit 22 creates a thread in the first message 101.

Step S7:
The thread generation unit 22 transmits the created thread to the display unit 31. The display unit 31 displays the thread received from the thread generation unit 22.

  Next, FIG. 5 is a flowchart showing an operation when transmitting a third message performed by the mobile terminal device 30 according to the third embodiment of the present invention. The operation procedure of the mobile terminal device 30 will be described along the flowchart.

  Here, as an example, the operation when the mobile terminal device 30 transmits a reply message (third message) to the first message 101 via the communication network 110 will be described in detail.

Step S21:
The message selection unit 11 detects, for example, an operation in which the user has selected a desired message (first message 101) to be replied from the thread displayed on the display unit 31.

  Furthermore, the message selection unit 11 displays (presents) communication means used for reply on the display unit 31 in response to detecting such an operation.

  Next, the message selection unit 11 selects a communication unit when, for example, the user selects one communication unit (third communication unit) from one or more communication units displayed on the display unit 31. Detected operation.

  The message selection unit 11 acquires the message ID 103 associated with the message desired by the user (first message 101) from the thread by detecting the user's operation.

  Further, the message selection unit 11 generates communication means information desired by the user (third communication means information 104) by detecting a user operation.

  The message selection unit 11 searches the message database 5 based on the acquired message ID 103 to acquire the first communication means information 102 associated with (associated with) the message ID 103.

  More specifically, the message selection unit 11 searches the message database 5 based on the acquired message ID 103.

  Next, the message selection unit 11 extracts the first message 101 associated (associated) with the acquired message ID 103.

  Further, the message selection unit 11 determines the type of header in the extracted first message 101.

  The message selection unit 11 determines the communication means used when the first message 101 is transmitted / received, and generates the first communication means information 102 based on the determined communication means.

  The message selection unit 11 transmits the first communication means information 102, the message ID 103, and the third communication means information 104 to the first message creation unit 3.

Step S22:
The first message creation unit 3 receives the first communication means information 102, the message ID 103, and the third communication means information 104 from the message selection unit 11.

Step S23:
The first message creation unit 3 generates a different custom header CH according to the type of the third communication means information 104 based on the message ID 103 and the first communication means information 102.

  That is, the first message creation unit 3 executes the custom header generation process (step S23) described below based on the first communication means information 102, the message ID 103, and the third communication means information 104.

  FIG. 6 is a flowchart showing the operation of the custom header generation process performed by the first message creation unit 3 in the third embodiment of the present invention. A detailed operation procedure of the custom header generation process in S23 will be described along the flowchart.

Step S31:
The first message creation unit 3 generates a character string based on the received message ID 103 and the first communication means information 102.

  More specifically, the first message creation unit 3 generates a character string by combining the received message ID 103 and the first communication means information 102.

  That is, when the first communication means information 102 indicates an e-mail, the first message creation unit 3 arranges the character string “email: message” by arranging “email” at the beginning and “message ID 103” at the end. ID "is generated.

  On the other hand, when the first communication means information 102 indicates a voice call, the first message creation unit 3 arranges the character string “sip:” by arranging “sip” at the head and “message ID 103” at the tail. Message ID "is generated.

  Next, the 1st message preparation part 3 advances a process to step S32.

Step S32:
The first message creation unit 3 determines the type of the received third communication means information 104.

  That is, the first message creation unit 3 determines the type of communication means used when transmitting / receiving the third message based on the received third communication means information 104.

“NO” in step S33:
If the first message creation unit 3 determines the type of the communication means based on the third communication means information 104 and determines that it is not a voice call, the process proceeds to step S34.

  That is, the third communication means information 104 means a communication means such as electronic mail or voice mail.

“YES” in step S33:
If the first message creation unit 3 determines the type of the communication means based on the third communication means information 104 and determines that the call is a voice call, the process proceeds to step S35.

Step S34:
The first message creation unit 3 creates a custom header CH based on the character string created in step S31.

  More specifically, as an example, the first message creation unit 3 generates a header “X-UC-In-Reply-To” field starting with “X-” that can be used as an arbitrary header in the e-mail in step S31. A custom header CH is generated based on the character string.

  That is, the first message creation unit 3 stores (describes) the character string generated in step S31 in the header “X-UC-In-Reply-To” field.

  More specifically, as an example, the custom header CH is set to “X-UC-In-Reply-To: email: message ID” when the first communication means information 102 indicates an electronic mail.

  On the other hand, the custom header CH is “X-UC-In-Reply-To: SIP: Message ID” when the first communication means information 102 indicates a voice call.

  The first message creation unit 3 ends the custom header generation process.

Step S35:
The first message creation unit 3 creates a custom header CH based on the character string created in step S31.

  More specifically, as an example, the first message creation unit 3 generates a header “P-UC-In-Reply-To” field starting with “P-” that can be used as an arbitrary header in SIP in step S31. Based on the character string, a custom header CH is generated.

  That is, the first message creation unit 3 stores (describes) the character string generated in step S31 in the header “P-UC-In-Reply-To” field.

  More specifically, as an example, the custom header CH is “P-UC-In-Reply-To: email: message ID” when the first communication means information 102 indicates an electronic mail.

  On the other hand, the custom header CH is “P-UC-In-Reply-To: SIP: Message ID” when the first communication means information 102 indicates a voice call.

  The first message creation unit 3 ends the custom header generation process.

  Here, in the above-described embodiment, as an example, the header “X-UC-In-Reply-To” field and the “P-UC-In-Reply-To” field include the reply source message (first message). 101) and information for identifying the communication means used when transmitting / receiving the message.

  In addition, when transmitting the newly created message, the first message creation unit 3 transmits the newly created message by executing the processes of step S25 and step S26.

Step S24:
The first message creating unit 3 embeds (includes) the generated custom header CH in a part of the header of the e-mail message or the SIP message, thereby making a reply message (third message) based on the third communication means information 104 ).

  That is, the first message creation unit 3 creates a third message as a reply to the first message 101 by embedding the generated custom header CH in a part of the header of the email message or SIP message.

  If the third message is not sent as a reply to another message (that is, the first message 101), the custom header indicating the other message is not included.

  FIG. 7 is a diagram for explaining the operation of the custom header generation process performed by the first message creation unit 3 according to the third embodiment of the present invention.

  That is, FIG. 7 is a diagram conceptually illustrating the operation of the custom header generation process performed by the first message creation unit 3 in the third embodiment of the present invention described in FIG. 6 in a table format.

  More specifically, FIG. 7 shows the third communication means used when transmitting and receiving the third message in the first column. FIG. 7 shows the first communication means used when transmitting / receiving the first message 101 in the second column.

  Next, FIG. 7 illustrates a method for generating a character string in the third column. FIG. 7 illustrates a method for generating a custom header CH in the fourth column.

Step S25:
The first message creation unit 3 stores the created reply message (third message) in the message database 5.

  That is, the first message creation unit 3 divides the header and the message body in the reply message for each communication means used when transmitting / receiving the third message, based on the third communication means information 104, in the message database 5. To store.

  FIG. 8 is a diagram conceptually illustrating the message database 5 in the third embodiment of the present invention.

  FIG. 8 has a storage table (e-mail storage table, voice call storage table) for each communication means used when sending and receiving messages.

  The storage table (e-mail storage table, voice call storage table) shown in FIG. 8 stores the header entity in the message transmitted and received in the first column. The storage table stores the substance of the mail text or the call data in the message in the second column. However, the present invention described using this embodiment as an example is not limited to these (the same applies to the following embodiments).

  Note that the technique itself stored in the storage table in the first message creation unit 3 can be a general technique at present, and thus a detailed description in this embodiment will be omitted (also in the following embodiments). The same).

Step S26:
The first message creating unit 3 transmits the generated third message via the communication network 110 via the communication unit 32.

  In the above-described embodiment, for the sake of convenience of explanation, the history management device 20 has been described as an example configured inside the mobile terminal device 30. However, the present invention is not limited to such a configuration, and the history management device 20 may be configured separately from the mobile terminal device 30.

  That is, for example, in the history management device 20, a server connected to the mobile terminal device 30 via the communication network 110 may have the history management device 20, or the first message constituting the history management device 20. The creation unit 3, the thread generation unit 22, the message database 5, and the like may be arranged on different servers.

  In that case, the thread generation unit 22 may present the thread on the display unit 31 in the mobile terminal device 30 via the communication network 110. However, the present invention described using this embodiment as an example is not limited to these (the same applies to the following embodiments).

  Further, a thread may be generated by employing a generally known header “References” field technique.

  In that case, as an example, the first message creation unit 3 includes all the threads constituting the thread for each topic in the header “X-UC-References” field starting with “X-” that can be used as an arbitrary header in the e-mail. Information related to the message may be stored and the header field may be included in the custom header CH.

  On the other hand, as an example, the first message creation unit 3 relates to all messages constituting a thread for each topic in a header “P-UC-References” field starting with “P-” that can be used as an arbitrary header in SIP. In addition to storing information, the header field may be included in the custom header CH.

  More specifically, the custom header CH acquires information of the header “P-UC-References” field described in the custom header CH in the second message in the header “P-UC-References” field, for example.

  Further, the custom header CH stores (describes) information obtained by adding the character string generated in step S31 to the tail of the acquired information of the header “P-UC-References” field.

  Accordingly, the thread generation unit 22 can generate a thread based on information in the header “X-UC-References” field or the header “P-UC-References” field.

  Note that the technology itself for generating threads based on the information in the “X-UC-References” field or the “P-UC-References” field in the thread generation unit 22 is currently the information in the general header “References” field. Since a technique for generating threads based on the above can be adopted, detailed description in this embodiment will be omitted (the same applies to the following embodiments).

  Thus, according to the mobile terminal device 30 according to the present embodiment, the effects described in the first and second embodiments described above can be enjoyed. That is, the portable terminal device 30 can present an overall image of exchange for each topic even when a plurality of communication means coexist.

  The reason is that the portable terminal device 30 stores all the exchanged messages in the message database 5 when communicating with the portable terminal device 30 different from the own device. Therefore, the thread generation unit 22 in the mobile terminal device 30 acquires the reply source message from the message database 5 based on the custom header CH included in the message, and based on the acquired reply source message and the received message. This is because a thread can be generated.

(Example)
Next, an example based on the history management apparatus 20 according to the third embodiment of the present invention described above will be described. In the following description, the characteristic part according to the present embodiment will be mainly described. At this time, the same reference numerals are assigned to the same configurations as those in the above-described embodiments, and duplicate descriptions are omitted.

  Next, a history management apparatus 20 in an example according to the third embodiment of the present invention will be described with reference to FIGS. 9 to 11.

  In the following description, for convenience of explanation, as an example, an operation when exchanging between the first user (Taro Nidec) and the second user (Hanako Nidec) will be described in detail.

  Here, in the following description, for convenience of explanation, as an example, the first user and the second user have a portable terminal device 30 including the history management device 20, and this portable terminal device 30 is used. To communicate.

  Furthermore, for convenience of explanation, the mobile terminal device 30 used by the first user is referred to as a first mobile terminal device. The mobile terminal device 30 used by the second user is referred to as a second mobile terminal device.

  The portable terminal device 30 is, for example, a generally known terminal device such as a smartphone or a tablet terminal.

  For convenience of explanation, the above-described configuration will be described as an example, but the present invention is not limited to this.

  FIG. 9 is a diagram conceptually illustrating threads displayed using the display unit 31 in the example according to the third embodiment of the present invention.

  The thread shown in FIG. 9 shows “item number” in the first column, “title” in the second column, “sender” in the third column, and “content” in the fourth column.

  In the embodiment described above, for convenience of explanation, as an example, the thread has been described by taking the configuration indicating the item number, title, sender, and content as an example. However, the present invention is not limited to such a configuration, and the thread may adopt, for example, a configuration indicating time information, message importance, and the like. However, the present invention described using this embodiment as an example is not limited to these (the same applies to the following embodiments).

  Further, as an example, the thread shown in FIG. 9 displays all messages exchanged between the first user and the second user.

  In the above-described embodiment, for the sake of convenience of explanation, as an example, the thread has been described with an example of a configuration in which all messages exchanged between the first user and the second user are displayed. However, the present invention is not limited to such a configuration, and the thread may display a received message or may adopt a configuration for displaying a transmitted message. However, the present invention described using this embodiment as an example is not limited to these (the same applies to the following embodiments).

  More specifically, the first line shown in FIG. 9 is an electronic mail message (referred to as a fourth message in the following description for convenience of description) transmitted by the first user who started the thread.

  The head of the title in the first line shown in FIG. 9 indicates a communication means when the fourth message is transmitted / received. However, the present invention described using this embodiment as an example is not limited to these (the same applies to the following embodiments).

  Here, the fourth message means that messages are exchanged in “Email” (that is, electronic mail).

  More specifically, the fourth message is sent from the mobile terminal device 30 (first mobile terminal device) used by the first user to the mobile terminal device 30 (second mobile terminal device) used by the second user. The data is transmitted via the communication network 110 via the communication unit 32 in the device itself.

  Here, since the fourth message is not a reply to another message, the custom header CH indicating the reply source is not included.

  When transmitting the fourth message, the first message creating unit 3 in the first portable terminal device stores the generated fourth message in the message database 5 in the own device.

  The custom header analysis unit 21 in the second mobile terminal device receives the fourth message via the communication unit 32 in the second mobile terminal device, and receives the received fourth message for each communication means. The message is stored in the message database 5 in the portable terminal device.

  The custom header analysis unit 21 in the second mobile terminal device determines that the custom header CH is not included (is absent) in the header of the fourth message, and sends the fourth message to the thread in the second mobile terminal device. It transmits to the production | generation part 22.

  The thread generation unit 22 creates a thread based on the fourth message and transmits the created thread to the display unit 31 in the second portable terminal device.

  At this time, only the first line shown in FIG. 9 is displayed on the display unit 31.

  The second line shown in FIG. 9 is an SIP message transmitted when the second user makes a call to the first user (in the following description, for convenience of explanation, this is referred to as a fifth message).

  The fifth message means that the second user exchanged a reply to the fourth message with the first user in “Tel” (ie, voice call).

  As an example, “content” in the second row shown in FIG. 9 may be displayed as a blank, or may have a function of reproducing the content of a voice call and the voice call, for example. However, the present invention described using this embodiment as an example is not limited to these (the same applies to the following embodiments).

  In that case, for example, when the voice call session between the first portable terminal device and the second portable terminal device is established, the first message creating unit 3 establishes a connection between the first user and the second user. Start recording the voice call.

  Further, the first message creation unit 3 is configured to store the voice call main body between the first user and the second user when the voice call session between the first portable terminal device and the second portable terminal device is disconnected. When recording is completed, the recorded data is stored in the message database 5 in association with the header in the SIP message.

  The first message creation unit 3 may extract, for example, voice for a predetermined time from the recorded data as text data, and store the extracted text data in the header of the SIP message.

  Thereby, the “content” in the thread can have a function of reproducing the contents of the voice call (that is, text data) and the voice call (that is, the recording data).

  Since the first message creating unit 3 described above records a voice call and extracts text data from the recorded data, a generally known technique can be adopted at present. Detailed description in the embodiment will be omitted (the same applies to the following embodiments).

  More specifically, the message selection unit 11 in the second mobile terminal device detects an operation in which the second user selects the fourth message from the thread displayed on the display unit 31 in the second mobile terminal device. In response to this, a context menu (that is, popping up one or more communication means, for example, in response to detecting an operation that has selected a message) is displayed.

  Thereby, the second user can select a desired communication means from the context menu and execute the selected communication means.

  Note that since the technology itself for displaying the context menu in the message selection unit 11 can now employ a general technology, detailed description in this embodiment will be omitted (the same applies to the following embodiments).

  Here, the second user selects “reply by voice call” from the context menu.

  Further, for convenience of explanation, as an example, the message ID associated with the fourth message is set as the message ID 103. The communication means used when the fourth message is transmitted / received is referred to as first communication means information 102.

  The message selection unit 11 in the second portable terminal device acquires the message ID 103 associated with the fourth message selected by the second user from the thread by detecting the operation of the second user and acquires the message ID 103. Based on the message ID 103, the first communication means information 102 used when the fourth message is transmitted / received from the message database 5 in the second portable terminal device is acquired.

  Further, the message selection unit 11 generates communication means information desired by the user (third communication means information 104) by detecting a user operation.

  The message selection unit 11 transmits the first communication unit information 102, the message ID 103, and the third communication unit information 104 to the first message creation unit 3 in the second portable terminal device.

  The first message creation unit 3 executes the custom header generation process shown in FIG. 6 based on the received first communication means information 102, message ID 103, and third communication means information 104.

  The first message creating unit 3 creates the fifth message by including the generated custom header CH in the header of the SIP message.

  The first message creation unit 3 stores the created fifth message in the message database 5 in the second portable terminal device.

  The 1st message preparation part 3 makes a call by transmitting the produced | generated 5th message via the communication network 110 via the communication part 32 in a 2nd portable terminal device.

  Next, the custom header analysis unit 21 in the first portable terminal device receives the fifth message via the communication unit 32 in the first portable terminal device, and the received fifth message for each communication means. The message is stored in the message database 5 in the first portable terminal device.

  The custom header analysis unit 21 determines that the header in the fifth message includes (has) the custom header CH, and the first reply information described in the custom header CH from the header in the fifth message. To extract.

  Further, the custom header analysis unit 21 transmits the extracted first reply information to the thread generation unit 22 in the first mobile terminal device.

  The thread generation unit 22 searches for the fourth message stored in the message database 5 and extracts the searched fourth message based on the received first reply information.

  The thread generation unit 22 creates a thread by using the retrieved fourth message as a parent and associating the received fifth message as a child of the parent, and creates the created thread as the first portable terminal. It transmits to the display part 31 in an apparatus.

  At this time, the display unit 31 displays the first and second lines shown in FIG.

Next, the third line shown in FIG. 9 is a SIP message transmitted when the first user makes a call to the second user (in the following description, for convenience of explanation, it is referred to as a sixth message).

  The sixth message means that the first user exchanged a reply to the fifth message with the second user in “Tel” (that is, voice call).

  Note that when the first user sends a reply to the second message to the second user in “Tel” (that is, a voice call), the above-mentioned second user replies to the fourth message. The operation is the same as that when the first user is exchanged in “Tel” (ie, voice call). Therefore, the overlapping description is omitted.

  At this time, the first line, the second line, and the third line shown in FIG. 9 are displayed in the thread in the display unit 31.

  That is, the thread is configured by associating a fifth message whose parent is the fourth message with a sixth message whose parent is the fifth message.

  FIG. 10 is a diagram illustrating a header including a custom header CH included in the sixth message in the example according to the third embodiment of the present invention.

  The header “To” field in the first line shown in FIG. 10 stores (describes) a destination address. Further, the header “From” field in the second line shown in FIG. 10 stores the address of the transmission source.

  Next, the header “Subject” field in the third line shown in FIG. 10 stores the subject (title) of the message.

  In addition, the header “In-Reply-To” field in the fourth line shown in FIG. 10 stores the message ID of the reply source in order to indicate which message the reply is for.

  More specifically, for example, the header “In-Reply-To” field stores the message ID of the fifth message that is the reply source of the sixth message.

  Here, the message ID in the fifth message means “aaa-0000002@sip.com” in the fourth line shown in FIG.

  The header “Call-ID” field in the fifth line shown in FIG. 10 stores the message ID in this message (that is, the sixth message).

  Here, the message ID in the sixth message means “aaa-0000003@sip.com” in the fifth line shown in FIG.

  Note that the above-mentioned “To” field, “From” field, “Subject” field, “In-Reply-To” field, and “Call-ID” field are added to the headers of currently known e-mails and the like. The technology adopted. Therefore, detailed description in this embodiment is omitted (the same applies to the following embodiments).

  Further, the header “P-UC-In-Reply-To” field in the sixth line shown in FIG. 10 stores “second communication means information: message ID” described in the third embodiment. .

  More specifically, the header “P-UC-In-Reply-To” field stores “sip: <aaa-0000002@sip.com>” in the sixth line shown in FIG.

  The header “P-UC-References” field in the seventh line shown in FIG. 10 includes the header “P-UC-References” field described in the custom header CH in the fifth message described in the third embodiment. Information with “second communication means information: message ID” added to the tail of the information is stored.

  More specifically, the header “P-UC-References” field stores “email: <aaa-0000001@email.com> _sip: <aaa-0000002@sip.com>” in the seventh line shown in FIG. Has been.

  That is, in the header “P-UC-References” field, the communication means information used when the fourth message and the fifth message are transmitted / received as the constituent elements of the thread, the message ID in the fourth message, and the fifth The message ID of the message is stored.

  Next, the fourth line shown in FIG. 9 is a voice mail message transmitted from the second user to the first user (in the following description, for convenience of explanation, it is referred to as the seventh message).

  The seventh message means that the second user exchanged a reply to the sixth message with the first user in “Vmail” (that is, voice mail).

  More specifically, when the second portable terminal device transmits the seventh message, the second portable terminal device executes the steps shown in FIGS. 5 and 6 described in the third embodiment, thereby obtaining the custom header CH. A seventh message containing is sent.

  In this case, the second user can select “reply by voice mail” from the context menu in the message selection unit 11 and transmit the seventh message by the selected voice mail.

  Further, when the first portable terminal device receives the seventh message, the first portable terminal device generates a thread generated by executing steps S1 to S7 shown in FIG. 4 described in the third embodiment. It displays on the display part 31 in a terminal device.

  That is, the thread generation unit 22 in the first mobile terminal device creates a thread by using the sixth message as a parent and associating the received seventh message as a child of the parent.

  At this time, the display unit 31 displays the first to fourth lines shown in FIG.

  That is, the thread includes a fifth message whose parent is the fourth message, a sixth message whose parent is the fifth message, and a seventh message whose parent is the sixth message. Has been.

  Next, the fifth line shown in FIG. 9 is an e-mail message transmitted from the first user to the second user (in the following description, for convenience of description, this is referred to as an eighth message).

  The eighth message means that the first user exchanged a reply to the seventh message with the second user by “Email” (that is, voice mail).

  More specifically, when the first mobile terminal device transmits the eighth message, the first mobile terminal device sets the custom header CH by executing the steps shown in FIGS. 5 and 6 described in the third embodiment. An eighth message containing is sent.

  In addition, when the second portable terminal device receives the eighth message, the second portable terminal device generates the thread generated by executing Steps S1 to S7 shown in FIG. 4 described in the third embodiment. It can be displayed on the display unit 31 in the terminal device.

  That is, the thread generation unit 22 in the second portable terminal device creates a thread by using the seventh message as a parent and associating the received eighth message as a child of the parent.

  At this time, the first to fifth lines shown in FIG. 9 are displayed on the display unit 31.

  That is, the thread sends a fifth message whose parent is the fourth message, a sixth message whose parent is the fifth message, a seventh message whose parent is the sixth message, and a seventh message. An eighth message as a parent is associated with the eighth message.

  FIG. 11 is a diagram illustrating a header including a custom header CH included in the eighth message in the example according to the third embodiment of the invention.

  The “To” field, “From” field, “Subject” field, and “In-Reply-To” field in the first to fifth lines shown in FIG. 11 are the same as the fields described in FIG. Therefore, the overlapping description is omitted.

  More specifically, the header “Message-ID” field in the fourth line shown in FIG. 11 stores the message ID of this message (that is, the eighth message).

  Here, the message ID in the eighth message means “aaa-0000005@email.com” in the fourth line shown in FIG.

  For example, the header “In-Reply-To” field stores the message ID of the seventh message that is the reply source of the eighth message.

  Here, the message ID in the seventh message means “aaa-0000004@email.com” in the fifth line shown in FIG.

  Next, the header “References” field in the sixth line shown in FIG. 11 stores a message ID column in the e-mail among the messages constituting the message.

  More specifically, the header “References” field stores a message ID in the fourth message and a message ID in the seventh message.

  Here, the header “References” field means the message ID “aaa-0000001@email.com” in the fourth message and the message ID “aaa-0000004@email.com” in the seventh message.

  The seventh to ninth lines shown in FIG. 11 are the same as the sixth and seventh lines described in FIG. Therefore, the overlapping description is omitted.

  More specifically, the header “P-UC-In-Reply-To” field stores “email: <aaa-0000004@email.com>” in the seventh line shown in FIG.

  That is, the header “P-UC-In-Reply-To” field stores the communication means information when the seventh message as the reply source of the eighth message is transmitted / received and the message ID in the seventh message. ing.

  The header “P-UC-References” field includes “email: <aaa-0000001@email.com> _sip: <aaa-0000002@sip.com> _sip: in the 8th and 9th lines shown in FIG. <Aaa-0000003@sip.com> _email: <aaa-0000004@email.com> "is stored.

  In the header “P-UC-References” field, communication means information when the fourth message to the seventh message are transmitted / received as a thread component and the message ID in the fourth message to the seventh message are exchanged. Are stored in the order in which they were made.

  That is, in the “P-UC-References” field, the second communication means information and the message ID in the message are additionally written by repeating the exchange of messages, so that the value of the field increases.

  The eleventh and subsequent lines shown in FIG. 11 show the text in the eighth message.

  As described above, according to the mobile terminal device 30 according to the present embodiment, the effects described in the above-described embodiments can be enjoyed. Moreover, the portable terminal device 30 is suitable for application to terminal devices such as generally known smartphones, personal computers, and tablet terminals.

<Fourth Embodiment>
Next, a fourth embodiment based on the history management apparatus 20 according to the third embodiment of the present invention described above will be described. In the following description, the characteristic part according to the present embodiment will be mainly described. At this time, the same reference numerals are assigned to the same configurations as those in the above-described embodiments, and duplicate descriptions are omitted.

  A history management apparatus 40 according to the fourth embodiment of the present invention will be described with reference to FIG.

  FIG. 12 is a block diagram illustrating the configuration of the history management device 40 according to the fourth embodiment of the invention.

  In FIG. 12, the history management device 40 includes a message selection unit 11, a custom header analysis unit 21, a thread generation unit 22, and a second message creation unit 41.

  More specifically, the history management device 40 further includes a second message creation unit 41 in the history management device 20 described in the third embodiment.

  The second message creation unit 41 corresponds to the first message creation unit 3 described in the third embodiment.

  Therefore, in the present embodiment, the difference operation between the first message creation unit 3 and the second message creation unit 41 will be described in detail.

  The second message creation unit 41 stores (describes) the custom header CH generated by executing the custom header CH generation processing described in the third embodiment in the reply message (third message) text.

  In this case, the custom header analysis unit 21 and the thread generation unit 22 may perform processing based on the custom header CH stored in the third message body when receiving the third message.

  Thus, according to the history management apparatus 40 according to the present embodiment, the effects described in the above-described embodiments can be enjoyed.

(Hardware configuration example)
Each unit illustrated in the drawings in the above-described embodiments may be realized by dedicated hardware. Alternatively, each unit can be regarded as a functional unit (software module) of a software program executed by a computer. An example of a hardware environment (resource) when the computer is applied to a mobile terminal device will be described with reference to FIG.

  FIG. 13 is a diagram for exemplarily explaining the configuration of the mobile terminal device 300 capable of executing the history management device according to the exemplary embodiment of the present invention. That is, FIG. 13 shows the history management device 1 shown in FIG. 1, or the history management device 10 shown in FIG. 2, the history management device 20 shown in FIG. 3, and the history management device 40 shown in FIG. It is a configuration of a mobile terminal device such as a smartphone or a tablet terminal that can be partially realized, and represents a hardware environment that can realize each function in the above-described embodiment.

  The mobile terminal device 300 illustrated in FIG. 13 includes a CPU (Central_Processing_Unit) 301, a ROM (Read_Only_Memory) 302, a RAM (Random_Access_Memory) 303, an input device 304, a microphone 305, a speaker 307, a display 308, a wireless transmission / reception circuit 309, and an antenna 310. These are general mobile terminal devices in which these configurations are connected via a bus 306 (communication line).

  The present invention described by taking the above-described embodiment as an example is a block diagram (FIGS. 1, 2, 3, and 12) referred to in the description of the mobile terminal device 300 shown in FIG. This is achieved by supplying a computer program capable of realizing the functions of the flowcharts (FIGS. 4 to 6) and then reading and executing the computer program on the CPU 301 of the hardware. The computer program supplied to the apparatus may be stored in a storage device such as a readable / writable volatile storage memory (RAM 303).

  In the above case, the computer program can be supplied to the hardware by a method of installing it in the apparatus via various recording media such as a memory card, or from the outside via a communication line such as the Internet. Currently, a general procedure can be adopted, such as a downloading method. In such a case, the present invention can be regarded as being configured by a code constituting the computer program or a storage medium storing the code.

  The present invention is not limited to the embodiments described above. The present invention can be applied to an electronic apparatus having a plurality of communication means used for transmitting and receiving messages such as a personal computer, a portable terminal, a tablet terminal, and a server.

DESCRIPTION OF SYMBOLS 1 History management apparatus 2 Thread generation part 3 1st message preparation part 4 Storage part 5 Message database 10 History management apparatus 11 Message selection part 20 History management apparatus 21 Custom header analysis part 22 Thread generation part 30 Portable terminal device 31 Display part 32 Communication unit 40 History management device 41 Second message creation unit 101 First message 102 First communication means information 103 Message ID
104 Third communication means information 110 Communication network 300 Mobile terminal device 301 CPU
302 ROM
303 RAM
304 Input Device 305 Microphone 306 Bus 307 Speaker 308 Display 309 Wireless Transmission / Reception Circuit 310 Antenna

Claims (8)

The first message is stored in the database, and it is determined whether or not a custom header is included in the header of the first message. If the custom header is included, the second message obtained from the custom header is stored. The second message is extracted from the database based on the second communication means information used for transmission / reception of the message and the message ID for identifying the second message, and the extracted second message is A thread generation unit that generates a data group having a hierarchical structure in which the first message is associated as a parent and a child of the parent;
Used when transmitting the third message as a reply to the first message, the third communication means information used when transmitting the third message, the message ID for identifying the first message, and the first message being transmitted / received Based on the first communication means information, a custom header generation process is executed to generate a different custom header according to the third communication means information, and the third message including the custom header is Creating a message creating unit for storing the created third message in the database;
A history management device comprising: The custom header generation process
Generating a character string based on the first communication means information and the message ID for identifying the first message;
When the type of the third communication means information is determined and the information indicating the voice call is included as a result of the determination, it can be stored in the header of the message requesting the start of the voice call based on the character string. And generating the custom header that can be stored in the header of the email message based on the character string when the information representing the email is included. The history management device according to claim 1. In addition, in response to detecting an operation that has selected the desired first message to be replied from the data group, one or more communication means used for the reply are presented and the first message is identified. Obtaining the message ID;
The third communication means for detecting an operation in which one third communication means is selected from the one or more communication means and for identifying the selected third communication means in accordance with the detected operation. 3. The information processing apparatus according to claim 1, further comprising: a message selection unit configured to acquire the first communication means information as a result of generating information and searching the database based on the acquired message ID. History management device. The database is
Header information and text information are associated and stored for each of the one or more communication means information including the first communication means information, the second communication means information, and the third communication means information. The history management device according to any one of claims 1 to 3. A portable terminal device capable of transmitting and receiving messages via a communication line,
A portable terminal device including the history management device according to claim 1. The first message is stored in the database, and it is determined whether or not a custom header is included in the header of the first message. If the custom header is included, the second message obtained from the custom header is stored. The second message is extracted from the database based on the second communication means information used for transmission / reception of the message and the message ID for identifying the second message, and the extracted second message is Generating a data group having a hierarchical structure in which the first message is associated with the first message as a child of the parent;
Used when transmitting the third message as a reply to the first message, the third communication means information used when transmitting the third message, the message ID for identifying the first message, and the first message being transmitted / received Based on the first communication means information, a custom header generation process is executed to generate a different custom header according to the third communication means information, and the third message including the custom header is A history management method comprising creating and storing the created third message in the database. Generating a character string based on the first communication means information and the message ID for identifying the first message;
When the type of the third communication means information is determined and the information indicating the voice call is included as a result of the determination, it can be stored in the header of the message requesting the start of the voice call based on the character string. And generating the custom header that can be stored in the header of the email message based on the character string when the information representing the email is included. The history management method according to claim 6. A computer program for controlling the operation of the history management device, the computer program,
The first message is stored in the database, and it is determined whether or not a custom header is included in the header of the first message. If the custom header is included, the second message obtained from the custom header is stored. The second message is extracted from the database based on the second communication means information used for transmission / reception of the message and the message ID for identifying the second message, and the extracted second message is A function of generating a data group having a hierarchical structure in which the first message is associated as a parent and a child of the parent;
Used when transmitting the third message as a reply to the first message, the third communication means information used when transmitting the third message, the message ID for identifying the first message, and the first message being transmitted / received Based on the first communication means information, the different custom header is generated according to the third communication means information, the third message including the custom header is created, and the created third message A computer program for causing a computer to realize a function of storing a message in the database.

Images