KR101919832B1 - System and method for transmitting and receiving a event message - Google Patents

Abstract

A method and system for sending and receiving event messages, the method comprising: receiving phonebook data from at least one terminal and storing the phonebook data; Receiving an event message; Confirming caller information corresponding to a transmitting terminal that has transmitted the event message; Searching phonebook data of at least one receiving terminals stored in phone book data of the transmitting terminal; Checking whether the caller information exists in the searched phonebook data; And transmitting the event message to the receiving terminal when the calling party information is present.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention [0001] The present invention relates to a system and method for transmitting /

The present invention relates to a method and system for sending and receiving event messages, and more particularly, to a method and system for sending and receiving event messages in which phone book data is registered in a server for managing event messages and event messages are registered in phonebook data.

Recently, due to the remarkable development of information communication technology and semiconductor technology, the spread and use of mobile terminals are rapidly increasing. In particular, recent mobile terminals have reached the stage of mobile convergence, which does not stay in the conventional inherent domain but covers other terminals. Typically, in the case of a mobile communication terminal, in addition to general communication functions such as voice communication and message transmission / reception, a TV broadcasting function (for example, a mobile broadcasting such as a DMB (Digital Multimedia Broadcasting) or a DVB (Digital Video Broadcasting) MP3 (MPEG Audio Layer-3), photo shooting function, data communication function, internet access function and short range wireless communication function.

Meanwhile, as a mobile communication service has been developed and a portable terminal has become a necessity of modern people, users who are notified of events (first birthday, marriage, advertisement, etc.) by using a portable terminal are increasing. However, in the related art, there has been an inconvenience that a call is individually made, a text message, or an e-mail is transmitted using a portable terminal. In addition, when transmitting an advertisement message, conventionally, the advertisement message is unilaterally transmitted to an unspecified number regardless of a doctor. Accordingly, it is difficult to expect the effect of advertisement exposure or information provision in the conventional message transmission method. There is a problem that the user is displeased due to the spam message.

SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and it is an object of the present invention to provide a method and apparatus for registering phone book data stored in a terminal of a user on a server, And a method and system for transmitting and receiving event messages.

It is another object of the present invention to provide a method and system for sending and receiving an event message, which can improve the exposure effect of an event message by displaying an event message related to the other party in a call request screen.

The present invention also provides a method and system for sending and receiving an event message for notifying a user that an event message exists based on a phonebook.

According to another aspect of the present invention, there is provided a system for transmitting and receiving event messages, the system comprising: a transmitting terminal for generating an event message and transmitting the event message and sender information; Receiving at least one phone book data from at least one terminal and storing at least one receiving terminal including the caller information in phone book data among receiving terminals included in phone book data of the transmitting terminal when receiving the event message, An event message service server for transmitting the event message to the searched at least one receiving terminal; And a receiving terminal for receiving the event message transmitted by the event message service server and notifying the user of the received event message.

According to another aspect of the present invention, there is provided a method for transmitting and receiving event messages, the method comprising: receiving phonebook data from at least one terminal and storing the phonebook data; Receiving the event message; Confirming caller information corresponding to a transmitting terminal that has transmitted the received event message; Searching phonebook data of at least one receiving terminals stored in phone book data of the transmitting terminal; Checking whether the caller information exists in the searched phonebook data; And transmitting the event message to the receiving terminal when the calling party information exists in the searched phonebook data.

According to another aspect of the present invention, there is provided a method of transmitting an event message, the method comprising: generating an event message; And transmitting the generated event message and sender information to an event message service server.

According to another aspect of the present invention, there is provided a method of receiving an event message, the method comprising: receiving an event message; And displaying an icon indicating that the event message is received on one side of the phonebook menu of the home screen.

As described above, the event message transmission and reception method and system according to the embodiment of the present invention can transmit a personal event message such as a birthday party, a wedding, etc. to other registered users. In addition, the present invention can transmit a business event message such as a discount coupon, a new product launch event, news, time sale information, etc. to a plurality of users storing business information (e.g., name, phone number, etc.). Accordingly, a business entity (a company or a small business) can maximize the advertisement effect by transmitting an event message to a large number of users storing their own information, rather than an unspecified number of users. In addition, The cost can be reduced. Meanwhile, the users can only receive event messages related to other users (individuals or carriers) stored in the phone book. This prevents the user from receiving spam characters. In addition, the present invention does not require a separate application program for event message management by notifying reception of an event message in cooperation with a phone book.

FIG. 1 is a view schematically showing an event message transmission / reception system according to an embodiment of the present invention.
2A is a flowchart schematically illustrating a method of transmitting an event message according to the first embodiment of the present invention.
2B is a flowchart illustrating an event message transmission method according to a second embodiment of the present invention.
3A is a flowchart illustrating a recipient search method for transmitting an event message of a system according to an embodiment of the present invention.
3B is a flowchart illustrating a method of updating a phone book of a provider in a system according to an embodiment of the present invention.
4 is a block diagram schematically illustrating a configuration of a mobile terminal according to an embodiment of the present invention.
5 is a flowchart illustrating an event message generation method according to an embodiment of the present invention.
FIG. 6A is a diagram for explaining a method of generating an event message using a phonebook screen according to an embodiment of the present invention. FIG.
FIG. 6B is a diagram for explaining a method of generating an event message using a web page according to an embodiment of the present invention.
FIG. 7 is a view for explaining a method of receiving an event message in a mobile terminal according to an embodiment of the present invention. Referring to FIG.
FIG. 8 is a flowchart illustrating a method of displaying an event message when a call is made / received according to an embodiment of the present invention.
9 is a diagram illustrating a method of displaying an event message when a call is made / received according to an embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. Note that, in the drawings, the same components are denoted by the same reference numerals as possible. Further, the detailed description of known functions and configurations that may obscure the gist of the present invention will be omitted.

It should be noted that the embodiments of the present invention disclosed in the present specification and drawings are only illustrative of the present invention in order to facilitate the understanding of the present invention and are not intended to limit the scope of the present invention. It is to be understood by those skilled in the art that other modifications based on the technical idea of the present invention are possible in addition to the embodiments disclosed herein.

FIG. 1 is a view schematically showing an event message transmission / reception system according to an embodiment of the present invention.

1, the event message transmitting / receiving system includes a transmitting terminal 100, an event message service server 200, a receiving terminal 300, a mobile communication network 400, an Internet network 500, a web server 600, And a PC 700. < RTI ID = 0.0 >

The transmitting terminal 100 is a terminal for generating and transmitting an event message, and the receiving terminal 300 is a terminal for receiving an event message. The event message may include a personal event message such as a birthday party, wedding, etc. and a business event message such as an advertisement (coupon, news, new product launch, etc.). The transmitting terminal 100 and the receiving terminal 300 may be a mobile communication terminal capable of transmitting and receiving a message (e.g., a text message, a multimedia message, etc.) through the mobile communication network 400, a tablet personal computer (PC) Smart Phone). The transmitting terminal 100 and the receiving terminal 300 may transmit their phone book data to the event message service server 200. [

The transmitting terminal 100 may provide an application for creating an event message. Alternatively, the transmitting terminal 100 may operate similarly to the PC 700 connected to the web server 600 when providing the Internet access function. That is, the transmitting terminal 100 may provide a web page screen for generating an event message.

The transmitting terminal 100 and the receiving terminal 300 may function as the receiving terminal 300 and the receiving terminal 300 may be a transmitting terminal 100).

The event message service server 200 is a server for managing event message transmission and reception and can receive telephone book data from at least one terminal (including the transmitting terminal 100, the receiving terminal 300 and the PC 700) . That is, the event message service server 200 can receive, store, and update phone book data from an individual or a business. Upon receiving the event message, the event message service server 200 searches the phone book data among the receiving terminals 300 included in the phone book data of the transmitting terminal 100 for the receiving terminal 300 including the calling party information And transmit the event message to the searched receiving terminal 300. When the event message service server 200 registers an event message through the PC 700, the event message service server 200 may transmit an event message to at least one receiving terminal 300 that stores business information of a business entity that registered the event message have. At this time, the event message service server 200 may transmit an event message for each group.

The event message service server 200 may include an event message management server 210, a phone book server 220, and a push server 230. The phone book server 220 stores the phone book data of the transmitting terminal 100, the phone book data of the receiving terminal 300, and the phone book data of the provider in the event message management server 210 And the push server 230 is a server that supports updating of an event message. The event message service server 200 may receive phone book data from a plurality of terminals (or a subscriber), compare phone book data when receiving an event message, and transmit event messages when the phone numbers are mutually registered. Although the event message management server 210, the phone book server 220, and the push server 230 have been described above, they may be configured as one server.

The web server 600 provides a web service for generating and managing event messages in the PC 700 such as a notebook PC (Personal Computer), a desktop PC, a netbook, etc. rather than the transmitting terminal 100 Server. The PC 700 accesses a web page of the web server 600 to generate an event message and transmits an event message to the event message service server 200 through the Internet 500 and the mobile communication network 400 . As described above, according to the present invention, not only an individual but also a business (such as a corporation, a small business person, etc.) can use the phone book data to transmit an event message (for example, an advertisement such as a discount coupon, Message). For this purpose, the provider can transmit phone book data including phone numbers of customers to the phone book server 220 based on their mutual names, and store and manage the phone book data. More specifically, the business operator can register the telephone number of the business partner and the business partner in the phone book server 220. [ The phone book server 220 can automatically update phone book data of the provider. FIG. 2A is a flowchart illustrating an event message transmission method according to the first embodiment of the present invention. Referring to FIG.

Referring to FIG. 2A, the transmitting terminal 100 generates an event message (a personal event message or a provider event message) according to a user's request in step 21, and transmits the generated event message to the event message service server (200). At this time, the transmitting terminal 100 may transmit caller information (e.g., its own telephone number) together. The event message may be generated through an application program or a web page for generating an event message. The method of generating the event message will be described in detail with reference to FIGS. 5, 6A and 6B. In step 25, the event message service server 200 receiving the event message can search for the recipient using the sender information. In detail, the event message service server 200 may store an event message in the event message management server 210 and send caller information (e.g., a phone number) to the phone book server 220. The phonebook server 220 can extract at least one recipient information by searching the phone book data of the sender corresponding to the sender information. Then, the phone book server 220 can check whether caller information is included in phonebook data of the preliminary recipients corresponding to the respective recipient information. If the phone book server 220 includes the sender information, the phone book server 220 can determine the actual recipient, that is, the receiving terminal 300.

The push server 230 of the event message service server 200 transmits the event message to at least one receiving terminal 300 in step 27. [ In step 29, the receiving terminal 300 notifies the user that an event message has been received. For example, the receiving terminal 300 receiving the event message can notify the user that an event message has been received through icon display, sound output, vibration occurrence, or the like. A detailed description of the event message receiving method will be described later with reference to FIG.

In the foregoing, a method of transmitting an event message has been described using the transmitting terminal 100 as an example. However, the present invention is not limited thereto. That is, the user can generate and transmit an event message using the PC 700. [

2B is a flowchart illustrating an event message transmission method according to a second embodiment of the present invention.

Referring to FIG. 2, the transmitting terminal 100 generates an event message (a personal event message or a provider event message) in response to a user's request in step 201, and transmits the generated event message to an event message service server 200). The method of generating the event message will be described later with reference to FIGS. 5, 6A and 6B. The event message service server 200 receiving the event message can search for the recipient using the sender information in step 205. In detail, the event message service server 200 may store an event message in the event message management server 210 and send caller information (e.g., a phone number) to the phone book server 220. The phonebook server 220 can extract at least one recipient information stored in the phone book data of the sender corresponding to the sender information and check whether the sender information is included in the phone book data of the recipient corresponding to each recipient information.

Using the result of the check, the phonebook server 220 can check whether the caller and the recipient are registered with each other in step 207. In case of mutual registration, the event message service server 200 can proceed to step 217 described later. On the other hand, if the event message service server 200 is not mutually registered, the event message service server 200 may transmit to the corresponding receiving terminal 300 a registration request message requesting registration of caller information to the preliminary receiver in step 209. [ The receiving terminal 300 may transmit a response message to the event message service server 200 in step 211. [ Upon receiving the response message, the event message service server 200 can confirm whether the registration request is permitted through the response message in step 213. If it is not permitted in step 213, the event message service server 200 may stop transmitting the event message. On the other hand, if the event message service server 200 is permitted in step 213, the event message service server 200 may add caller information to the recipient's phone book data in step 215. In step 217, the push server 230 of the event message service server 200 transmits an event message to the recipient terminal 300, which is registered with each other. In step 219, the receiving terminal 300 notifies the user that an event message has been received. For example, the receiving terminal 300 receiving the event message can notify the user that an event message has been received through icon display, sound output, vibration occurrence, or the like.

In the above description, the recipient's phone book data included in the phone book data of the sender is searched for in recipient search, but the present invention is not limited thereto. For example, the phone book server 220 may further search for a recipient using the telephone number of the caller. That is, the phone book server 220 searches for phone book data of users who do not exist in the phone book data of the sender, and transmits the event message to a receiver who is not present in the phone book data of the sender but registers the sender in the phone book.

In the foregoing, a method of transmitting an event message has been described using the transmitting terminal 100 as an example. However, the present invention is not limited thereto. That is, the user can generate and transmit an event message using the PC 700. [

3A is a flowchart illustrating a recipient search method for transmitting an event message of a system according to an embodiment of the present invention.

Referring to FIG. 3A, the phonebook server 220 may receive phone book data from at least one terminal in step 301 and store the phone book data. The phonebook data may be periodically synchronized and managed.

In step 303, the phonebook server 200 can confirm whether an event message is received. If the event message is not received, the phone book server 220 may perform the corresponding function in step 305. [ For example, the phonebook server 220 may perform phonebook data synchronization or maintain a standby state. On the other hand, if the event message is received, the phonebook server 220 may check the sender information that transmitted the event message in step 307 and extract the preliminary receiver from the phone book data of the caller in step 309. [

The phonebook server 220 can check whether the phonebook data of the preliminary recipients extracted in step 311 exists. If there is no phone book data of the extracted preliminary recipients, the phone book server 220 can proceed to step 321 described later. On the other hand, if there is phone book data of the extracted preliminary recipients, the phonebook server 220 searches phone book data of the preliminary recipient in step 313 and confirms that the phone number of the caller exists in the phone book data of the preliminary recipient . The phone book server 220 may request the event message management server 210 to update the event message in step 317. If the phone number of the caller exists, Thereafter, the event message management server 210 may transmit an event message to the corresponding receiving terminal in step 319 via the push server 230.

On the other hand, if the phone number of the sender does not exist in the phone book data of the preliminary recipient in step 315, the phonebook server 220 can transmit a sender information registration request message to the corresponding receiving terminal in step 321. In step 325, the phone book server 220 checks whether a permission message is received from the corresponding receiving terminal, and if so, adds caller information (phone number and name) to the phone book data of the recipient. Then, the phonebook server 220 proceeds to step 317 described above. On the other hand, if not authorized, the phonebook server 220 does not transmit an event message to the corresponding receiving terminal.

In the above description, the recipient's phone book data included in the phone book data of the sender is searched for in the recipient search, but the present invention is not limited thereto. For example, the phone book server 220 may further search for a recipient using the telephone number of the caller. Specifically, the phone book server 220 searches phone book data of users who are not present in the phone book data of the calling party, searches for the receiving terminals that are not present in the phone book data of the calling party but registered the calling party in the phone book, Can be transmitted. This is useful for corporate advertisement message transmission. That is, it is possible to transmit the advertisement message only to the user storing the telephone number of the company, without transmitting the advertisement message indiscriminately using the personal information. This allows the enterprise to reduce the cost of sending advertising messages. In addition, companies can improve their advertising effectiveness by delivering event messages to customers who are interested in them.

3B is a flowchart illustrating a method of updating a phone book of a provider in a system according to an embodiment of the present invention.

Referring to FIG. 3B, a business entity (such as a corporation, a small business corporation, etc.) who wishes to use the event message transmission service according to the present invention can subscribe to an event message transmission service in step 331. At this time, the service provider subscribed to the event message transmission service can register customer information (telephone number, e-mail address, etc.). That is, the service provider can register customer information in the phone book server 220 of the event message service server 200.

In step 333, the phonebook server 220 can check whether the phone book data of a specific user is updated. That is, the phone book server 220 can confirm whether the user has added phone book data to his / her phone book. For this, the phonebook server 220 may periodically synchronize phonebook data of a plurality of registered users.

If the update of the user's phone book data is not detected, the phone book server 220 may return to step 333. On the other hand, if the phone book data update of the user is detected, the phone book server 220 proceeds to step 335 and can check whether the added phone book data includes the carrier information (at least one of mutual and telephone numbers). To this end, the phonebook server 220 extracts a telephone number and a registered name of a business operator from the added phonebook data, and compares the telephone number and the registered name of the business operator with the previously registered business information to check whether there is business information matching (matching).

If the added phone book data does not include the carrier information, the phone book server 220 can update the phone book data of the user in step 339. On the other hand, when the added phone book data includes the carrier information, the phone book server 220 proceeds to step 337 to automatically add phone book data of the business place by adding the phone number of the specific user to the phone book data of the business, The user can proceed to step 339 to update the phone book data of the user. When the update of the phone book data of the provider and the user is completed, the phone book server 220 returns to step 333 and repeats the above-described process.

3B, the user's phone number is automatically added to the phone book data of the provider. However, the present invention is not limited thereto. For example, if the carrier information is deleted from the phone book data of the user, the phone book server 220 may delete the user information from the phone book data of the corresponding carrier.

4 is a block diagram schematically illustrating a configuration of a mobile terminal according to an embodiment of the present invention. At this time, the mobile terminal 100/300 can act as the transmitting terminal 100 and the receiving terminal 300 according to circumstances. Hereinafter, the portable terminal will be generally referred to for convenience of description.

4, the portable terminal 100/300 includes an audio processing unit 160, a wireless communication unit 150, an input unit 140, a display unit 130, a storage unit 120, and a control unit 110 can do. The storage unit 120 may store the phone book 20.

The audio processing unit 160 may be formed as an acoustic component that transmits and receives an audio signal and encodes and decodes the audio signal. The audio processing unit 160 may include a codec and an audio amplifier (Amp). The audio processing unit 160 is connected to a microphone (MIC) and a speaker (SPK). The audio processing unit 160 converts an analog audio signal input from the microphone (MIC) into a digital audio signal and transmits the data to the control unit 110, The digital audio signal input from the control unit 110 can be converted into an analog audio signal and outputted through the speaker SPK. In addition, the audio processor 160 may output various audio signals generated by the portable terminal 100/300 through a speaker SPK. For example, the audio processing unit 160 may output an audio signal according to playback of an MP3 file or a moving picture file through a speaker SPK. In particular, the audio processor 160 according to the present invention can output an effect sound for notifying reception of an event message.

The wireless communication unit 150 may form a communication channel for communication and a communication channel for data transmission. That is, the wireless communication unit 150 can form a voice communication channel, a video communication channel, and a data communication channel with the base station. The wireless communication unit 150 may transmit a voice signal and an image signal to the partner terminal through the voice call channel and the video call channel under the control of the controller 110, or may receive the voice signal and the image signal from the partner terminal. The radio communication unit 150 includes a radio frequency transmitter (not shown) for up-converting and amplifying a frequency of a transmitted signal, a radio frequency receiver (not shown) for performing low-noise amplification and frequency down-conversion of a received signal, And a transmission / reception separation unit (not shown) for separation. In particular, the wireless communication unit 150 according to the present invention may transmit an event message to the event message service server 200 or an event message from the event message service server 200. Also, the wireless communication unit 150 may transmit phone book data to the event message service server 200 and may periodically synchronize phone book data. When the portable terminal 100/300 operates as the receiving terminal 300, the wireless communication unit 150 receives a caller information addition request message from the phone book server 220 of the event message service server 200 , And transmits a response message to the event message service server 200. The wireless communication unit 150 may form a communication channel with the web server 600 through the mobile communication network 400 and the Internet network 500. Alternatively, the wireless communication unit 150 may form a communication channel with the web server 600 using a wired Internet network (not shown) such as Wi-Fi or a wired cable. At this time, the mobile terminal 100/300 may operate similar to the PC 700 as described above.

The input unit 140 may include input keys and function keys for inputting numbers or various character information, setting various functions, and controlling functions of the portable terminal 100/300. For example, the input unit 140 may include a call key for a voice call request, a video call key for requesting a video call, an end key for requesting a voice call or video call termination, a volume key for adjusting an output volume of the audio signal, A direction key, and the like. Particularly, the input unit 140 according to the present invention can transmit a signal related to the generation of an event message and a request for outputting a received event message to the control unit 110. The input unit 140 may be any one of input means such as a touch pad, a touch screen, a button type key pad, a joystick, a wheel key, Or a combination thereof.

The display unit 130 displays various types of menus of the portable terminal 100/300, information input by the user or information to be provided to the user. For example, the display unit 130 may provide various screens such as a standby screen, a message creation screen, a call screen, and the like according to the use of the portable terminal 100/300. In particular, the display unit 130 according to the present invention may display a screen for generating an event message, a screen for receiving an event message, a screen for outputting a received event message, and the like. A detailed description thereof will be described later with reference to Figs. 6A, 6B, 7, and 9. The display unit 130 may be a liquid crystal display (LCD), an organic light emitting diode (OLED), or an active matrix organic light emitting diode (AMOLED). Meanwhile, when the display unit 130 is formed as a touch screen, the display unit 130 may perform the function of the input unit 140.

The storage unit 120 may store user data and the like as well as programs necessary for the functional operation according to the embodiment of the present invention. For example, the storage unit 120 may include a program for controlling the overall operation of the portable terminal 100/300, an operating system (OS) for booting the portable terminal 100 / For example, a camera function, a sound reproducing function, an image or moving picture reproducing function, an application program for a short-range wireless communication function, and the like. The storage unit 120 may store user data, such as a text message, a game file, a music file, a movie file, and the like, which are generated according to the use of the portable terminal 100/300. In particular, the storage unit 120 according to the present invention may store the phone book 20. The phone book 20 is transmitted to the phone book server 220 of the event message service server 200 and can be managed in synchronization. In addition, the storage unit 120 may store an application program for generating an event message. The application program may be provided separately. Alternatively, the event message generating application program may be included in the phonebook application program. That is, the phone book application program of the portable terminal 100 according to the present invention may include a routine for managing phone book information and a routine for managing generation and reception of event messages. When the event message generating application program is included in the phone book application program, the phone book 20 can be managed in association with the event message. For example, when the phone book list is output, the presence or absence of an event message may be displayed for each item of the list. The presence or absence of the event message may be represented by a numeric icon. A detailed description thereof will be given later.

The controller 110 may control the overall operation of the mobile terminal 100/300 and the signal flow between the internal blocks of the mobile terminal 100/300. In particular, the controller 110 according to the present invention can control generation of an event message, reception of an event message, and display of an event message. Details of the control unit 110 will be described later with reference to FIGS. 5 to 9. FIG.

Although not shown in FIG. 4, the portable terminal 100/300 according to the present invention includes a camera module for photographing images or moving pictures, a broadcast receiving module for receiving broadcasts, a digital sound source reproducing module such as an MP3 module, A proximity sensor module for proximity sensing, and the like, as shown in FIG. These components can not be enumerated because of various variations according to the convergence trend of the digital device. However, the portable terminal 100/300 according to the present invention can not classify all of the components As shown in FIG.

FIG. 5 is a flowchart illustrating a method of generating an event message in a mobile terminal according to an exemplary embodiment of the present invention. FIG. 6A is a diagram illustrating a method of generating an event message using a phonebook according to an exemplary embodiment of the present invention, FIG. 6B is a diagram for explaining a method of generating an event message using a web page according to an embodiment of the present invention. Hereinafter, a case where a web page for generating an event message is connected to a mobile terminal will be described as an example. It will be apparent to those skilled in the art that the event message generation method described below may be applied to a notebook PC, a desktop PC, a tablet PC, and the like.

Referring to FIGS. 4 and 6B, the controller 110 can check whether an event message generation request is generated in step 501. FIG. The event message generation request may be generated through a pre-set hot key input or a menu. For example, the event message creation request may be generated when the user touches the " Create " menu 60 located at the upper right corner of the phonebook screen of the portable terminal as shown in the screen example of the identification code 610 of FIG. 6A.

Alternatively, when accessing a web page for generating an event message using the Internet access function, the event message creation request may include an event message generated by an event located at one side of the web page screen, This can occur when the message generation menu (6) is selected. At this time, the event message creation menu 6 may include a news menu 6a, an event menu 6b, and a coupon menu 6c according to the type of the event message. However, the present invention is not limited thereto. That is, the event message generation menu 6 can be variously set according to the designer's intention. In addition, the event message creation screen may further include an event message history previously generated and transmitted by a business entity, customer information scheduled to have an event (e.g., a birthday, a wedding anniversary, etc.), and group information. At this time, the business entity can select the customer or the specific group for which the event is scheduled to generate an event message.

If the event message generation request signal is not generated, the controller 110 may perform the corresponding function in step 503. For example, the control unit 110 may perform a music playback function, a file transmission function, a broadcast playback function, or the like in response to a user request, or may maintain a standby state. On the other hand, if the event message generation request signal is generated, the controller 110 may control the display unit 130 to output an event message generation screen in step 505. [ For example, the display unit 130 may output an event message generation screen as shown in an exemplary screen of the identification code 620. The event message creation screen includes a text message input area 61, an image attachment area 62, a return menu 63 to return to the previous step, a first transmission menu 64 for requesting transmission of the created event message, A slide menu 65 including sub-menus such as image selection, special character selection, and the like. The figure of the screen of the identification code 620 shows a case in which a birthday invitation message is created.

Meanwhile, if any one of the event message generation menus 6 is selected on the same web page screen as the screen example of the identification code 630, the controller 110 generates an event message The window 67 can be popped up. The event message generation window 67 includes an event message setting area 67 including an area for inputting an event title, an area for selecting an event type, an area for setting an event date, an area for inputting an event place, (68) and a preview area (69) for previewing the generated event message.

The controller 110 checks whether a transmission request is input in step 507. If the transmission request is not input, the controller 110 may maintain step 507. [ On the other hand, when the transmission request is input, the controller 110 may transmit the event message generated in operation 509 to the event message service server 200. [ For example, the first transmission menu 64 is selected on the phone book screen of the screen example of the identification code 620 or the second transmission menu 66 of the event message generation window 67 of the screen example of the identification code 640 is selected The control unit 110 may transmit the generated event message to the event message service server 200 and may be transmitted to the recipient terminal 300. [

In the event message generation according to the present invention described above, unlike general message generation, even if the receiver information is not inputted, the phone book server 220 compares phone book data to search for recipients to transmit an event message, It is possible to improve the convenience of the user.

In the above description, an event message is generated in the portable terminal 100 as an example. However, the present invention is not limited thereto. For example, the event message may be generated by accessing a web server 600 that manages event message generation and registration using the PC 700.

FIG. 7 is a view for explaining a method of receiving an event message in a mobile terminal according to an embodiment of the present invention. Referring to FIG.

1 to 7, when an event message is received, the controller 110 may display an icon or an image on the display unit 130 to inform the user of the event message. For example, the control unit 110 may display a numeric icon 71 on one side of the phone book menu 70 on the home screen as shown in the screen example of the identification code 710. The number is changed corresponding to the number of event messages not confirmed by the user. Meanwhile, the icon 71 may be displayed in an indicator area in which an icon indicating a battery remaining amount, a receiving strength, and the like is displayed.

When the user touches the phonebook menu 70, the display unit 130 can display the phonebook screen. For example, the display unit 130 may output the phonebook screen as shown in the screen example of the identification code 720. [ The phonebook screen may include a Notification menu 80 for requesting to output only a group name and a list in which a new event message is present. At this time, a number icon indicating the number of new event messages included in each group may be output to one side of the group name. Referring to the screen of the identification code 720, the user can know that one new event message exists in the family group, one new event message exists in the friend group, and three new event messages exist in the company group have. The user can select a group in which a new event message exists and confirm a new event message existing in the corresponding group.

On the other hand, when the user touches the notification menu 80, the display unit 130 can output only the phonebook list in which the new event message exists, such as the screen example of the identification code 730. [ At this time, a number icon indicating the number of new event messages may be output to one side of each phonebook list. The user can select any one item from the list and confirm the corresponding event message. For example, when the user touches " Hong Kil Dong " in the same state as the identification code 730, the controller 110 displays the event message (birthday invitation message) Can be controlled. Referring to FIG. 7, the event message screen includes a return menu 72 for returning to the previous step and an edit menu 73 for editing the event message. The user can edit the event message through the edit menu 73, and reuse the event message or retransmit the event message to another person.

In the above description, the phonebook screen indicating the group name is displayed when the phonebook menu is touched, but the present invention is not limited thereto. For example, when the phonebook menu is touched, the display unit 130 may output a phonebook screen for outputting the entire list of phonebooks as shown in the screen example of the identification code 750. At this time, each item of the phone book list may include a number icon indicating the number of new event messages. The user can select any item from the phonebook list and confirm information of the item (e.g., an event message or a telephone number). For example, in the screen example of the identification code 750, when the user touches " Hong Kil Dong ", the control unit 110 displays the phone book detailed information display screen as shown in the screen example of the identification code 760 130). The phonebook detailed information display screen may include a phonebook information display area 81 for displaying phonebook information such as a mobile phone number and a home phone number, and an event information display area 82 for displaying event information. When an event item is touched in the event information display area 82, an event message screen corresponding to the selected event item may be output as illustrated in the screen example of the identification code 740. Meanwhile, although only one event information is shown in the screen diagram of the identification code 760, when a plurality of event messages are received, the controller 110 may display a plurality of event information in the event information display area 82 .

FIG. 8 is a flowchart illustrating a method of displaying an event message at the time of a call request according to an embodiment of the present invention. FIG. 9 illustrates a method of displaying an event message when a call is received / Fig.

Referring to FIGS. 4 to 9, the controller 110 can check whether a call request is received in step 801. FIG. The call request may include a call for requesting a call to another terminal and a call for receiving a call request of another terminal. If the call request does not occur, the controller 110 may perform the corresponding function in step 803. [ For example, the control unit 110 may perform a music playback function, a photo shooting function, a game function, and the like in response to a user's request. On the other hand, if a call request is generated, the controller 110 searches for an event message corresponding to the counterpart terminal in step 805, and confirms presence of the event message in step 807. [ If the corresponding event message does not exist, the controller 110 may display a preset call request screen in step 809. FIG. On the other hand, if there is the corresponding event message, the controller 110 may display a call screen including at least a part of the event message in step 811. 9, the display unit 130 displays a part 90 of the event message on one side of the call request screen including the counterpart information (counterpart image, counterpart phone number) Can be displayed. In FIG. 9, only a part of the event message is displayed, but the present invention is not limited thereto. For example, the display unit 130 may display the event message as a call request screen upon a call request. Such an event message can be prevented from being output when a predetermined period of time has elapsed. Or a period during which an event message is displayed when an event message is generated. For example, if an event date is specified, such as a birthday party, the event message can be set to no longer display the event message on the call screen. Alternatively, in another embodiment of the present invention, only a new event message not confirmed by the user may be output on the call screen.

The method of transmitting / receiving an event message according to an embodiment of the present invention as described above may be implemented in the form of a program command that can be executed through various computer means and recorded in a computer-readable recording medium. At this time, the computer readable recording medium may include a program command, a data file, a data structure, or the like, alone or in combination. On the other hand, the program instructions recorded on the recording medium may be those specially designed and configured for the present invention or may be available to those skilled in the art of computer software.

The computer-readable recording medium includes magnetic media such as a hard disk, a floppy disk and a magnetic tape, an optical medium such as a CD-ROM and a DVD, and a magnetic recording medium such as a floppy disk. Optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. The program instructions also include machine language code, such as those generated by the compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the present invention.

Although the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. The present invention is not limited to the above-described embodiments. That is, it is apparent to those skilled in the art that various embodiments based on the technical idea of the present invention are possible.

100: transmitting terminal 200: event message service server
300: receiving terminal 400: mobile communication network
500: Internet network 600: Web server
700: computer 110: control unit
120: storage unit 130: display unit
140: input unit 150: wireless communication unit
160: Audio processing unit

Claims (35)

In an event message service server,
Receiving and storing phone book data from at least one transmitting terminal,
When receiving the event message, compares phone book data of each of the receiving terminals included in the phone book data of the transmitting terminal to select at least one receiving terminal including the calling party information of the transmitting terminal in the phone book data of the receiving terminals,
And transmits the event message to the selected at least one receiving terminal. The method according to claim 1,
The event message service server
When detecting the update of the phone book data from any one of the terminals, confirms whether or not the provider information previously registered in the phone book data of the terminal requesting update is included, and adds the phone number of the user to the phone book data of the provider And the event message service server. The method according to claim 1,
The event message service server
And transmits a caller information registration request message to at least one receiving terminal which does not include caller information of the transmitting terminal in the phone book data of the receiving terminals of the receiving terminals included in the phone book data of the transmitting terminal. Service server. The method of claim 3,
The event message service server
The method of claim 1, further comprising the steps of: receiving a response message to the registration request message; adding caller information of the transmitting terminal to at least one receiving terminal's phonebook data that approves the registration request; And transmits the event message. 5. The method of claim 4,
The event message service server
Selecting at least one receiving terminal that does not include the phone book data of the transmitting terminal and includes the calling party information in its phone book data among the remaining terminals stored in the event message service server, And transmits the event message. The method according to claim 1,
The receiving terminal
And notifies the user of the event message by using at least one of time, hearing and tactile sense when receiving the event message. The method according to claim 6,
The receiving terminal
Wherein when the event message is received, an icon indicating that an event message has been received is displayed on one side of the phone book menu of the home screen. 8. The method of claim 7,
The receiving terminal
When the phonebook menu is selected, displays a phonebook list and displays an icon indicating that an event message has been received in a phonebook item corresponding to the transmitting terminal that has transmitted the event message. 9. The method of claim 8,
The receiving terminal
And outputs an event message screen for outputting an event message when the phonebook item in which the icon is displayed is selected. 8. The method of claim 7,
The receiving terminal
And outputs a phonebook screen including a notification menu when the phonebook menu is selected, and outputs a phonebook list including only phonebook items including a new event message not confirmed by the user when the notification menu is selected. The method according to claim 1,
The receiving terminal
Wherein the display unit displays a call request screen including at least a part of the associated event message if the event message related to the called party exists when the call request is made, . The method according to claim 1,
A web server for providing a web service capable of generating and managing the event message; And
Further comprising a computer for accessing the web server to generate the event message. 13. The method of claim 12,
The transmitting terminal
And generates the event message by accessing the web server. The method according to claim 1,
The transmitting terminal
And an application program for generating the event message. A method for transmitting and receiving an event message,
Receiving phone book data from at least one terminal and storing the phone book data;
Receiving the event message;
Confirming caller information corresponding to a transmitting terminal that has transmitted the received event message;
Comparing the phone book data of at least one receiving terminals stored in the phone book data of the transmitting terminal to select at least one receiving terminal including caller information of the transmitting terminal in the phone book data of the receiving terminals; And
And transmitting the event message to the selected receiving terminal. 16. The method of claim 15,
And transmitting and receiving phone book data from the at least one terminal,
Transmitting and storing phone book data of an individual user and a provider; And
And periodically updating the phone book data of the individual user. 17. The method of claim 16,
Checking whether the personal user's phonebook data update includes the carrier information registered in the phone book data of the individual user when the update of the phone book data is detected and adding the phone number of the individual user to the phone book data of the carrier when the carrier information includes the carrier information Further comprising the steps of: 16. The method of claim 15,
Transmitting a registration request message of the calling party information to the receiving terminal if the calling party information of the calling terminal does not exist in the phone book data of the receiving terminals;
Receiving a response message for the registration request message; And
And adding the sender information to the phone book data of the receiving terminal when the response message indicates approval, and transmitting the event message to the corresponding receiving terminal. 16. The method of claim 15,
Determining whether the caller information exists by checking phonebook data of the remaining terminals stored in the event message service server without being included in phone book data of the transmitting terminal; And
And transmitting the event message to at least one receiving terminal in which the caller information exists among the remaining terminals. 16. The method of claim 15,
Further comprising the step of notifying that the receiving terminal having received the event message has received the event message in at least one of a visual, auditory, and tactile manner. 21. The method of claim 20,
The process of notifying
And displaying an icon indicating that an event message has been received on one side of the phonebook menu of the home screen. 22. The method of claim 21,
The process of notifying
And outputting a phonebook list when the phonebook menu is selected, and displaying an icon indicating that an event message has been received in a phone book item corresponding to the transmitting terminal that has transmitted the event message. 23. The method of claim 22,
The process of notifying
And outputting an event message screen for outputting an event message upon selecting the phone book item in which the icon is displayed. 22. The method of claim 21,
The process of notifying
Outputting a phonebook screen including a notification menu when the phonebook menu is selected; And
And outputting a phonebook list including only phonebook items including a new event message not confirmed by the user when the notification menu is selected. 22. The method of claim 21,
The process of notifying
Checking the counterpart terminal information requested to be called when a call request is generated;
Checking whether there is an event message related to the checked counterpart terminal information; And
And outputting a call request screen including at least a part of the related event message if the related event message exists. delete delete delete delete delete delete delete delete delete delete

Images