KR20080045948A - Apparatus for providing call and message service and method for managing call and message information - Google Patents

Abstract

A terminal for providing a call and message service and a method for managing call information and a message in a terminal are provided to allow a user to manage messages and call particulars easily as personal information. A phone book memory(210) stores personal information of an individual and related messages. A phone book controller(222) stores reception messages or origination messages as related messages according to individuals stored in the phone book memory. If at least one related message is stored in the phone book memory, the phone book controller allocates a region for storing the message. A display unit(230) displays the personal information of the individual stored in the phone book memory and related messages. The phone book controller displays the personal information of each individual stored in the phone book memory and related messages in response to a request of a user.

Description

{APPARATUS FOR PROVIDING CALL AND MESSAGE SERVICE AND METHOD FOR MANAGING CALL AND MESSAGE INFORMATION}

1 is a block diagram of a mobile communication system to which a terminal providing a call and message service according to an embodiment may be applied.

2 is a block diagram of a terminal providing a call and message service according to an exemplary embodiment.

3 is a diagram illustrating a data flow between a phone book controller and a phone book according to one embodiment;

4 is a diagram schematically illustrating a flow of data management in a terminal according to an embodiment.

5 is a flowchart illustrating a method of storing a message received at a terminal in a phonebook according to an embodiment.

6 is a flowchart illustrating a method for storing a message sent from a terminal in a phonebook according to an embodiment.

7 is a flowchart illustrating a method of storing a call history of a call partner in a phone book according to an embodiment.

8 is a flowchart illustrating a method of displaying, by a terminal, a message / call history stored in a phonebook to a user according to an exemplary embodiment.

9 is a flowchart illustrating a method of deleting a message and a call log in a terminal according to an exemplary embodiment.

10 is a flowchart of a method of displaying a call frequency in a terminal according to an embodiment.

11 is a flowchart illustrating a method of using personal talk time information in a terminal according to an exemplary embodiment.

* Description of the symbols for the main parts of the drawings *

210: memory, 212: phonebook,

222: phone book control unit, 320: phone number storage unit,

340: message storage unit, 360: call time storage unit,

380: Frequency storage unit.

The present invention relates to a method for managing call information and messages in a terminal and a terminal providing a call and message service, and more particularly, stores and manages messages or call information for each individual in a phonebook included in the terminal. It's about doing.

The mobile communication terminal (MS) moves freely in the service area formed by the corresponding base station (RAN: RADIO ACCESS NETWORK) of the registered mobile communication system, while the mobile switching station (MSC: MOBILE SWITCHING CENTER) Via a communication path established by monitoring, control and switching, it is possible to instantly wirelessly connect and communicate with a desired party anytime and anywhere.

Various additional services are provided to enhance the convenience of use of the mobile communication terminal (MS) and the use other than the purpose of communication. Examples of the additional service may include, for example, wireless internet provided by a mobile communication service provider, a text message, a multimedia message, a caller ID, a wireless online game, and the like. In addition, the additional service includes a phone book, a Bluetooth communication function, a ringtone setting service, a message writing function, a video recording function, a television watching function, a radio listening function, and the like, which are provided by a mobile terminal manufacturer. It is constantly being developed and added.

As such, it would be convenient if a function key button allocated to each service is installed on the mobile communication terminal (MS) to operate various additional services. However, the mobile communication terminal is made of small size and light weight for mobility and portability. Accordingly, the number of key buttons integrally provided due to the small surface area is very limited except for dialing and a few function key buttons. Accordingly, each function is operated to be searched and selected by using a soft key button or a menu method. However, with the development of electronic components and operational technologies, the data processing capability is greatly improved and thus the functions that can be utilized in the portable terminal are increased. There are problems such as the need for procedures and time and the complicated search process. In particular, additional services such as a phone book and a memo increase as the number of individuals known over time increases the amount of data such as contacts and information to be managed, and the time required for searching continues to increase.

As the capacity of the memory mounted in the mobile communication terminal increases, recently, hundreds to thousands of phone numbers can be stored and managed in the terminal. For example, an application program called a phone book, a phone book, or the like can be stored. It is equipped with a function to search or manage contacts such as phone numbers, fax numbers, mobile phone numbers, and email addresses for a number of stored individuals. However, only the personal information related to the individual is stored in the phone book of the conventional mobile communication terminal, and the storage and management of data is not universal compared to the vast memory capacity allocated to the phone book.

On the other hand, Short Message Service (SMS) is a two-way data radio calling service, and when data conforms to the Global System for Mobile Communications (GSM), data is transmitted at a maximum speed of 150 bytes per second between the mobile communication terminal and the mobile communication terminal. It is possible to transmit. Through a short message service, a message composed of letters and numbers may be exchanged between a mobile communication terminal or a network. Short message service types include short message transmission, urgent message display, date, time recording, message recognition, and the like. The short message in the mobile communication terminal is similar to the wireless calling and the implementation technology, and may provide the short message even when the mobile communication terminal is inoperable or is in an incapable area.

When the short message is received by the mobile communication terminal using the conventional short message, the short message may be stored and used in the memory. However, when the number of the short messages exceeds the capacity, the short message may not be stored and managed. Since only the data is stored in the area, a function for managing a message sent by a specific sender by sender has not been developed. As described above, in the case of a user receiving a short message using a mobile communication terminal, there is an inconvenience in managing the message.

In addition, the conventional mobile communication terminal is not able to provide effective time management because the communication time or the number of calls for a specific call counterpart cannot be provided in conjunction with the personal information of each individual stored in the phone book.

The present invention has been conceived to solve the above problems of the prior art, and it is easy to manage the message and call information by allowing the phonebook to manage the call information about the outgoing or received message, the call time or the number of calls in the phonebook for each individual and An object of the present invention is to provide a method for managing call information and messages in a terminal and a terminal for providing a call and message service with improved convenience.

According to one embodiment, a terminal providing a call and message service is provided. The terminal includes a phone book memory for storing personal information of a person and a related message, and a phone book controller for storing a received message or an outgoing message as a related message for each person stored in the phone book memory.

In one embodiment, the terminal further includes a display unit for displaying the personal information and related messages of the individual stored in the phonebook memory. The phone book control unit displays personal information and related messages for each individual stored in the phone book memory in response to a user's request. In one embodiment, the phonebook controller of the terminal deletes the related message of the phonebook memory in response to a user's request.

 According to another embodiment, a terminal providing a call service is provided. The terminal may include: a phone book memory for storing personal information and related call information of an individual; And a phone book controller for controlling the phone book memory.

According to another embodiment, there is provided a method for managing a message at a terminal providing a call and message service, including a phonebook memory for storing personal information and related messages of an individual. The method includes receiving / sending a message; And storing the received / sent message as a related message for each individual stored in the phonebook memory.

According to another embodiment, there is provided a method for managing call information in a terminal providing a call service, including a phonebook memory for storing personal information and related call information of an individual. The method includes initiating a call; And storing information on the disclosed call as related call information for each person stored in the phonebook memory.

Hereinafter, various embodiments of the present invention will be described with reference to the accompanying drawings. However, it will be apparent that these embodiments may be practiced without some or all of the specific details. For example, well-known procedure steps or elements have not been described in detail in order to avoid unnecessarily obscuring the description of embodiments of the present invention.

1 is a block diagram of a mobile communication system to which a terminal providing a call and message service according to an exemplary embodiment may be applied. The mobile communication system 100 includes a terminal A1-An, a mobile communication network 120, and a message service server 140.

In one embodiment, the mobile communication network 120 may include a base station, a base station controller, and a mobile switching center. The base station establishes a call channel under the control of a controller. The controller is located between the exchange and the base station to manage the base station and to set up or release calls between mobile terminals. The exchange matches data of the base station, the controller, and the message service server 140, forms a communication path between components in the mobile communication network 120, and performs its own operation and maintenance.

The message service server 140 is a server that provides a message service to a mobile terminal. For example, the message may include a short message, a video message, a video message, a music message, or an MMS message according to a multimedia messaging system (MMS). In the case of the short message, it is a short message within a capacity of about 150 bytes and may be transmitted in a paging manner using a voice network. In addition to the short message, the message service server 140 may use a voice network or another type of data network according to the corresponding message capacity, and may transmit one or more traffic channels by allocating one or more traffic channels.

Terminals A1-An are devices that provide call and message services to users. For example, at the time of incoming / outgoing call between the terminals A1-An, a call is established between the calling terminal and the called terminal A1-An via the mobile communication network 120. In addition, when the number of messages between the terminals A1-An and the call is sent, the message is transmitted from the calling terminal A1-An to the called terminal A1-An via the mobile communication network 120 and the message service server 140. do

2 is a block diagram of a terminal providing a call and message service according to an exemplary embodiment. The terminal 200 includes a memory 210 including a phone book area 212, a controller 220, a phone book controller 222, a display unit 230, a signal processor 250, and a radio frequency unit 240. , A key input unit 260, a speaker 270, a microphone 280, and an antenna 290. In FIG. 2, the phone book control unit 222 is illustrated separately from the control unit 220 so as to explain the control of the phone book area 212. However, the present invention is not limited thereto. 222 may be integrated into the controller 220.

As shown, the memory 210 includes an area in which an operation program is stored and a phonebook area 212 in which personal information of an individual and an individual related message or related call information are stored. For example, the memory 210 may be implemented as a ROM, an EEPROM, or a RAM, but is not limited thereto. Any suitable storage in which an operating program or personal information may be stored may be used. It may be implemented using a medium.

The control unit 220 controls the overall operation of the terminal 200 and interlocks with the phone book control unit 222 to provide a received message, an outgoing message or call information to the phone book control unit 222, and received from the phone book control unit 222. The display unit 230 is controlled to output the phone book area 212 data to the display unit 230.

The phonebook controller 222 classifies the received message, the outgoing message, or the call information for each individual stored in the phonebook area 212 and stores the received message, the related call information, or the related call information. The phone book control unit 222 also accesses the phone book 212 and cooperates with the control unit 220 to display the related message or the related call information on the display unit 230 for each stored individual.

3 is a diagram illustrating a data flow between the phone book controller 222 and the phone book area 212 according to an embodiment. In an embodiment, the phonebook area (or phonebook) 212 may include a phone number storage 320, a message storage 340, a call time storage 360 and a call number storage 380. . The phone number storage unit 320 stores information such as a name, a phone number, a title or an address, an e-mail address, etc., which are personal information of an individual. The message storage unit 340 is interlocked with the phone number storage unit 320 to store the outgoing and received messages for the individual stored in the phone number storage unit 320. The talk time storage unit 360 interworks with the phone number storage 320 to store talk time data for an individual stored in the phone number storage 320. The call frequency storage unit 380 stores call frequency (number) data for the individual stored in the phone number storage unit 320.

When the phonebook control unit 222 receives the outgoing / receiving message from the control unit 220, extracts the caller / caller information from the message, and the caller / caller is one of the individuals stored in the phone number storage unit 320. In addition, a specific memory area of the message storage unit 340 is allocated to the individual to store the outgoing / receiving message. In one embodiment, the phonebook controller 222 may allocate a memory area for each received / outgoing message and store the message. In addition, the phonebook controller 222 may extract (or reorder) relevant messages stored in the message storage unit 340 for each individual stored in the phone number storage unit 320 in response to a user's request. This may be displayed in cooperation with the display unit 230. The phonebook controller 222 may also delete related messages stored in the message storage unit 340 in response to a user's request.

When the phone book controller 222 receives the call counter's number and call time information from the controller 220, when the counter determined based on the information is one of individuals stored in the phone number storage 320, the call is controlled. A specific memory area of the time storage unit 360 is allocated to this individual to store talk time information. In an embodiment, the phonebook controller 222 may allocate memory areas for each incoming / outgoing call to store call time information. Here, the call time information includes call start time and call end time of the outgoing call and the incoming call for each person stored in the phonebook. For example, the talk time information may be divided into months, days, hours, and minutes and stored. The phone book controller 222 may calculate a call progress time for each person stored in the phone book by using the corresponding call start time and call end time, and store the calculated call progress time for each person in the call time storage unit 360. Can be. The phone book controller 222 may extract (or rearrange) the call time information stored in the call time storage unit 360 for each individual stored in the phone number storage unit 320 in response to a user's request. This may be displayed in conjunction with the display unit 230. The phone book controller 222 may also delete the related talk time information stored in the talk time storage 360 in response to a user's request.

The phone book controller 222 may update the talk frequency (number of times) stored in the talk frequency storage unit 380 while storing the above talk time information in the talk time storage unit 360. The call frequency may be stored for each individual stored in the phone number storage 320, for example, in a specific time zone, day, week, or month. The phonebook control unit 222 may extract (or reorder) the related call frequency stored in the call frequency storage unit 380 for each individual stored in the phone number storage unit 320 in response to a user's request. This may be displayed in cooperation with the display unit 230. The phonebook controller 222 may also delete the related call frequency stored in the call frequency storage unit 380 in response to a user's request.

Deletion of the above-mentioned related message, talk time or call frequency can be performed by, for example, designating a particular person on the phonebook menu displayed on the display unit 230 and selecting one of a plurality of deletion modes provided for the designated person. . The plurality of deletion modes may include, for example, a deletion mode of all information (related message, outgoing or incoming call time, call frequency) stored as classified as sub-information about a specific individual in the phonebook, and an individual information deletion mode. Here, the deletion mode of the individual data includes, for example, a deletion mode of an outgoing message, an incoming message, an outgoing time, an incoming time, a call progress time, and a call frequency. The deletion mode of the individual data may include a tree structure including a lower deletion mode (eg, distinguishing origination / reception in case of related messages).

Referring back to FIG. 2, the display unit 230 displays the state of the terminal 200 or the progress of the program under the control of the controller 220. For example, the display unit 230 may be implemented as a device such as a liquid crystal display (LCD).

The wireless processor 240 transmits call and message data to the base station through the antenna 290 under the control of the control unit 220 and receives from the base station. The signal processor 250 modulates the voice signal input from the microphone 280 to convert the voice signal into voice data, and demodulates the voice data input from the wireless processor 240 into the voice signal through a speaker 16. Output

The key input unit 260 includes a plurality of numeric keys and function keys for performing various functions. The key data is output to the control unit 220 by an external operation. In one embodiment, the key input unit 260 may include a key for requesting the display unit 230 to display information stored in the phonebook area 212. The key input unit 260 may also include a key for requesting deletion of a personally-related message or related call information stored in the phonebook area 212. Alternatively, the key input unit 260 may operate the general-purpose numeric key and the function key to perform the above-described deletion request. You can also run In addition, the key input unit 260 may be manipulated to request rearrangement of individual related messages and rearrangement of call information stored in the phonebook area 212.

According to the above-described embodiments, the message or call information such as the call time or the number of call is stored, displayed and managed for each individual stored in the phone book (or the phone book area in the memory) so that the user can manage the message and call information more conveniently and easily. Can be. Here, the management of the message and call information includes classifying the received / outgoing message or the call information and displaying, editing, or deleting the information on the display unit 230.

The configuration of the terminal 200 and the method of managing phonebook information using the same are not limited to the wireless mobile communication system 100, but are applicable to all terminals capable of voice and data communication such as wired terminals or Internet phones. Note that you can.

4 is a diagram schematically illustrating a flowchart of a method of data management in a terminal according to an embodiment. In step 410, the outgoing / incoming message or call history information is classified and stored for each individual stored in the phonebook area on the memory of the terminal. For example, as illustrated in FIG. 2, the phonebook controller 222 classifies and stores outgoing / receiving messages or call history information for each individual stored in the phonebook area 212. In step 420, the stored outgoing / received message or call history information is provided to the user for each individual stored in the phonebook area. Step 420 may be executed, for example, by the user selecting a particular person on the phonebook menu and requesting display of related message or call log information as sub information of the selected person. In step 430, the message or call history information stored for each individual in the phonebook is deleted.

5 is a flowchart illustrating a method of storing a message received at a terminal in a phonebook according to an embodiment. When the terminal receives the message (step 510), the caller information (CID; Caller IDentification) included in the received message is extracted (step 520). For example, as illustrated in FIG. 2, when receiving a message, the phonebook controller 222 or the controller 220 extracts caller information included in the received message. Next, using the extracted caller information (CID), it is determined whether the sender of the received message is one of individuals stored in the phone number storage of the phonebook area on the memory of the terminal (step 530). In one embodiment, the phone book controller 222 uses the extracted caller information (CID) to send the received message to the phone number storage unit 320 (FIG. 3) of the phone book 212 (FIG. 2-3). It is determined whether it is one of stored individuals (step 530). Next, if the caller is an individual stored in the phone number storage of the phonebook area, the message is recombined (step 540) and stored in the message storage of the phonebook (step 550). Here, recombination means modifying the message to be in any form suitable for being stored in the message storage area of the phone book. For example, the recombined message may include caller information, reception information indicating that the message is a reception message, and a message. have. On the other hand, if the caller is not an individual stored in the phonebook storage of the phonebook, the message is stored in the memory as normal (step 560). In one embodiment, if the caller is an individual stored in the phone number storage 320 of the phone book 212, the phone book control unit 222 recombines the received message (step 540), the message storage unit 340 ), And if the caller is not stored in the phone number storage unit 320 of the phone book 212, the phone book controller 222 stores the received message in the memory 210, that is, the phone book ( Instead of the message storage unit 340 (FIG. 3) of 212, the data is stored in the general memory 210 area (step 560).

As described above, since the received message is stored in the phone book 212 as the lower information of the individual, the user may designate the person in the phone book 212 and manage the received message for convenience.

6 is a flowchart illustrating a method of storing a message sent from a terminal in a phonebook according to an embodiment. When the message is sent (step 610), the incoming callee information is extracted (step 620). For example, as illustrated in FIG. 2, when the phonebook controller 222 or the controller 220 sends a message, the phonebook controller 222 extracts called party information included in the sent message (620). Next, the extracted recipient information is used to determine whether the receiver of the sent message is one of individuals stored in the phone number storage of the phonebook area on the memory of the terminal (step 630). In one embodiment, the phonebook control unit 222 determines whether the called party is an individual stored in the phone number storage unit 320 (FIG. 3) of the phonebook 212 (FIG. 2-3) using the extracted called party information. Determine (step 630). Next, if the writer is an individual stored in the phone number storage of the phonebook area, the message is recombined (step 640) and stored in the message storage of the phonebook (step 650). Here, recombination means modifying the message to be in any form suitable for being stored in the message storage area of the phonebook. For example, the recombined message may include sender information, outgoing information indicating that the message is an outgoing message, and a message. Can be. On the other hand, if the called party is not an individual stored in the phone number storage of the phonebook, the message is stored in the memory (step 660). In one embodiment, when the called party is an individual stored in the phone number storage unit 320 of the phone book 212, the phone book control unit 222 recombines the outgoing message (step 640), and the message storage unit 340 ), And when the called party is not stored in the phone number storage unit 320 of the phone book 212, the phone book controller 222 stores the received message in the memory 210, that is, the phone book ( Instead of storing the message storage unit 340 (FIG. 3) of 212, the data is stored in the general memory 210 area (step 660).

As described above, since the outgoing message is stored in the phonebook 212 as the bottom information of the individual, the user may manage the outgoing message by designating the individual in the phonebook 212 for convenience.

7 is a flowchart illustrating a method for storing a call history of a call partner in a phone book according to an embodiment. When the call is initiated (step 710), it is determined whether the call counterpart is an individual stored in the phone number storage of the phone book (step 720). For example, as illustrated in FIG. 2, the phonebook control unit 222 or the control unit uses an incoming phone number for an outgoing call and a call using information (CID) received (or extracted) for an incoming call. It is determined whether the other party is an individual stored in the phone book 212 (step 720). Next, when the call counterpart is an individual stored in the phonebook, the call start time and the call counterpart information are stored in the phonebook (step 730), and it is determined whether the call ends (step 740). When the call ends, the end time and the call progress time are stored in the phonebook (step 750), and the call frequency data for the call counterpart is updated (step 760). If the call counterpart is not an individual stored in the phone book, the call start time is stored in the general memory (770). In one embodiment, the phone book controller 222 stores the call / call start time and the callee / caller information in the call time storage 360 of the phone book 212 if the call counterpart is an individual stored in the phone book 212 ( In operation 730, whether the call is terminated may be monitored (operation 740), and when the call is terminated, the call termination time and call progress time may be stored in the call time storage 360 along with the above-mentioned call / call start time and caller / caller information. (Step 750). In one embodiment, the phone book controller 222 may update the call frequency of the called party / caller stored in the call frequency storage unit 380. On the other hand, when the call counterpart is not stored in the phone number storage unit 320 of the phone book 212, the phone book control unit 222 stores the call start time in the memory 210, that is, the call time of the phone book 212 Stored in the general memory 210 area, rather than the unit 360 (FIG. 3) (step 770).

As such, since the call time and the frequency of the call are stored in the phone book 212 as the lower information of the person, the user can designate the person in the phone book 212 and manage the call log for convenience. have.

8 is a flowchart illustrating a method of displaying, by a terminal, a message / call history stored in a phonebook to a user according to an exemplary embodiment. The terminal receives a request signal to select a specific individual in the phone book (step 810). Wait for reception of a request signal to display a message (step 820) or reception of a request signal to display a call history (step 870). For example, as illustrated in FIG. 2, the phone book controller 222 or the controller 220 may store the phone number storage 320 of the phone book 212 in the phone book mode (the phone book is activated on the display 230). In step 810, a signal for requesting selection of a specific individual is received. Thereafter, the phone book controller 222 checks whether a signal for requesting a message display or a call log display for the selected individual is received (step 820 or step 870).

If a message display request is received, the message list for the selected person is extracted / reordered and the extracted / reordered list is displayed (step 840). In one embodiment, the phonebook control unit 222 extracts and rearranges only the outgoing / receiving messages for the selected individual from the message storage unit 340 (FIG. 3) of the phonebook 212 (step 830). The list of messages extracted and rearranged as described above is displayed in cooperation with the control unit 220 and the display unit 230 (step 840). Next, when a signal for requesting selection of a specific item is received in the displayed list (step 850), the corresponding item is displayed (step 860). In an embodiment, the phonebook controller 222 receives a selection request signal for a specific message item of a list displayed through the key input unit 260 from the user (step 850), and controls the content of the selected message in the controller 220 and the display unit. In operation 860, the display unit 230 displays the display unit 230 in association with 230.

On the other hand, when the call history display request is received, the call history list of the selected individual is extracted / reordered (step 880). After that, a list of extracted call history information is displayed on the screen (step 840), and when a selection request signal for a specific call history item is received from the user (step 850), a call such as a call start time, end time, or end time History information is displayed (step 860). For example, the phonebook controller 222 extracts and rearranges only the call history information of the selected person from the call time storage unit 360 of the phone book 212 in response to the call history display request (step 880), and displays the display unit 230. And in conjunction with the controller 220. In one embodiment, the display of the message and call history information may be selectively displayed for each incoming or outgoing call based on the terminal 200. As described above with reference to Figs. 5-7, the stored message and call history information may be stored together with information (calling information, called information) indicating whether the call is received or received, and thus, the call is received using this information. Alternatively, only the sent one can be selectively extracted.

9 is a flowchart illustrating a method of deleting a message and a call log in a terminal according to an exemplary embodiment. When the selection signal for the specific person in the phonebook is received (step 910), the message / call history list for the selected person is extracted / reordered and displayed (step 920). For example, as illustrated in FIG. 2, the phone book controller 222 or the controller 220 may select a specific individual stored in the phone number storage unit 320 (FIG. 3) of the phone book 212 (FIG. 2) in the phone book mode. Receive a signal (step 910). Next, the phone book controller 222 extracts a list of relevant message and call history information of the selected person from the message storage unit 340 (FIG. 3) and the call time storage unit 360 (FIG. 3) of the phone book 212. The rearrangement is performed on the display unit 230 in association with the control unit 220 and the display unit 230 (step 920).

Next, at the user's request, delete the entire message and call history information for the selected person (step 930), delete all messages (step 940), and delete all call history (including start time, end start, call duration, etc.) In operation 950, all call progress times may be deleted (step 960) to delete all related messages or related call details. Alternatively, the selected message may be deleted from the displayed message / call history list by deleting the selected message (step 970) and deleting the selected call history (step 980).

10 is a flowchart of a logical method of displaying a call frequency in a terminal according to an embodiment. The phonebook mode is started (step 1010), and a signal for requesting extraction of a person with a low call frequency among individuals stored in the phonebook is received (step 1021). For example, as shown in FIG. 2, the phonebook mode is started in response to a user's request through the key input unit 260 (step 1010), and in this state, the phonebook control unit 222 or the control unit 220 may, for example, execute a key. The input unit 260 receives a signal for requesting extraction of a person having a low call frequency among individuals stored in the phone number storage unit 320 (FIG. 3) of the phone book 212 (step 1021). Next, the list is extracted / rearranged in descending order of call frequency (step 1031) and displayed (step 1040). In one embodiment, the phone book control unit 222 extracts and rearranges the list from the call frequency storage unit 380 (FIG. 3) in the order of the lowest call frequency (step 1031). In operation 1040, the display unit 230 interlocks with the display unit 230 and the display unit 230. Next, upon receiving a signal requesting selection of a specific individual from the displayed list (step 1050), the call history for the selected individual is extracted and displayed (step 1060). In one embodiment, when the phonebook controller 222 receives a signal for requesting the selection of a specific individual through a key input unit 260 (step 1050), the phonebook controller 222 receives a signal for the selected individual from the call time storage unit 360. The call history is extracted, and the call history extracted on the display unit 230 is displayed in cooperation with the controller 220 and the display unit 230 (step 1060). If a signal for requesting a call connection with the selected person is received (step 1070), the call connection is executed for the selected person (step 1080).

According to the above embodiments, the call frequency can be confirmed for each individual stored in the phone book 212, and thus, the individual management can be easily performed.

On the other hand, when receiving a signal requesting extraction of individuals with a high frequency of call among individuals stored in the phonebook (step 1022), the list is extracted and rearranged in the order of the highest frequency of call (step 1032), and as described above. It can be displayed on the screen and processed by receiving a personal selection signal from the user.

11 is a flowchart illustrating a method of using individual call time information in a terminal according to an embodiment. The phonebook mode is initiated (step 1110) and a signal is requested to extract an individual with a long talk time (step 1120). Accordingly, the list is extracted and rearranged in the order of the high call progress time (step 1130), and the list is displayed (step 1140). For example, as illustrated in FIG. 2, when the phonebook controller 222 or the controller 220 receives a signal for requesting to extract an individual having a long talk time from the user in the phonebook mode (steps 1110-1120), The phone book control unit 222 extracts and rearranges the list from the talk time storage unit 360 of the phone book 212 in the order of the high call progress time (step 1130), and the list of extracted / rearranged lists in the control unit 220 and The display unit 230 is displayed on the display unit 230 in conjunction with the display unit 230.

According to the above embodiment, it is possible to statistically identify the registrant with high call intimacy by displaying a list of individuals with a long talk duration regardless of the call frequency.

While the invention and its various functional components have been described in particular embodiments, the invention may be embodied in hardware, software, firmware, middleware, or a combination thereof, and may include systems, subsystems, components, or sub-configurations thereof. It should be understood that they can be used as elements. If implemented in software, the elements of the invention are instructions / code segments for performing the necessary tasks. The program or code segments may be stored in a machine readable medium, such as a processor readable medium, a computer program product, or via a transmission medium or communication link by a computer data signal embodied in a carrier wave or a signal modulated by a carrier. Can be sent. Machine readable media or processor readable media may include any medium that can store or transmit information in a form readable and executable by a machine (eg, processor, computer, etc.).

Although the present invention has been described and illustrated with reference to the embodiments, those skilled in the art, various modifications and equivalent other embodiments without departing from the spirit and scope of the present invention defined by the appended claims It will be appreciated that examples are possible.

Embodiments described above, by storing the message and call history for each individual of the phone book in the terminal to enhance the convenience of the terminal user later manages the message and call history as personal information.

Claims (23)

In the terminal providing a call and message service, Phonebook memory for storing personal information and related messages of the individual, and Phonebook control unit for storing the received message or the outgoing message as a related message for each individual stored in the phonebook memory Terminal comprising a. The method of claim 1, The phone book control unit allocates an area for storing a message when there is at least one related message stored in the phone book memory. The method of claim 1, Display unit for displaying the personal information and related messages of the individual stored in the phonebook memory The terminal further comprises a phone book control unit, in response to a user's request to display the personal information and related messages for each person stored in the phone book memory on the display unit. The method of claim 1, The phone book control unit, in response to a user request, deletes the related message of the phone book memory. In the terminal providing a call service, A phonebook memory for storing personal information and related call information of the individual; And Phonebook control unit for controlling the phonebook memory Terminal comprising a. The method of claim 4, wherein The related call information includes a call time or talk time with the individual. The method of claim 4, wherein Display unit for displaying the personal information and the related call information of the individual stored in the phonebook memory The terminal further includes the phone book control unit, in response to a user's request, displays the personal information and the related call information for each individual stored in the phone book memory on the display unit. The method of claim 4, wherein The phone book controller is configured to delete the call information of the phone book memory in response to a user's request. In the terminal providing a call and message service, Phonebook memory for storing personal information of a person, related messages and related call information, and Phonebook control unit for storing the received message or the outgoing message as a related message for each individual stored in the phonebook memory, and for storing the call information as the related call information Terminal comprising a. A terminal for providing a call and message service, wherein the terminal includes a phonebook memory for storing personal information of a person and related messages. Receiving a message, and Storing the received message as a related message for each individual stored in the phonebook memory; How to include. The method of claim 10, The storing of the received message as a related message for each individual stored in the phonebook memory may include: Extracting a sender from the received message; Determining whether the extracted caller is an individual stored in the phonebook; and If the extracted caller is an individual stored in the phonebook, storing the received message as a related message of the individual How to include. The method of claim 10, Displaying personal information and a related message for each individual stored in the phonebook memory in response to a user's request; How to include more. The method of claim 10, Deleting the relevant message in the phonebook memory in response to a user's request How to include more. A terminal for providing a call and message service, wherein the terminal includes a phonebook memory for storing personal information of a person and related messages. Sending a message, and Storing the sent message as a related message for each individual stored in the phonebook memory; How to include. The method of claim 14, The storing of the sent message as a related message for each individual stored in the phonebook memory may include: Extracting a called party from the sent message; Determining whether the extracted called party is an individual stored in the phone book; and If the extracted called person is an individual stored in the phone book, storing the sent message as a related message of the individual How to include. The method of claim 14, Displaying personal information and a related message for each individual stored in the phonebook memory in response to a user's request; How to include more. The method of claim 14, Deleting the relevant message in the phonebook memory in response to a user's request How to include more. A method for managing call information in a terminal providing a call service, wherein the terminal includes a phonebook memory for storing personal information of a person and related call information. Initiating a call, and Storing information about the initiated call as related call information for each individual stored in the phonebook memory; How to include. 19. The method of claim 18, wherein the storing of the information about the initiated call as related call information for each person stored in the phonebook memory includes: Extracting a call counterpart from the initiated call; Determining whether the extracted call counterpart is an individual stored in the phone book; and If the extracted call counterpart is an individual stored in the phone book, storing information on the initiated call as related call information of the individual How to include. The method of claim 18, Displaying personal information and related call information for each individual stored in the phonebook memory in response to a user's request; How to include more. The method of claim 18, Deleting relevant call information in the phonebook memory in response to a user's request How to include more. 19. The method of claim 18, wherein the relevant call information comprises a talk time or talk time with the individual. 23. A computer readable medium storing computer executable instructions for performing the method of any of claims 10-22.

Images