KR20050027898A - System for notifying event on network and method thereof - Google Patents

Abstract

A system and a method for notifying event generation on the network to a user are provided to efficiently notify the event generation by generating an event according to a set condition and offer load/expense reduction according to message transfer to a system side. An event notification system(100) is connected to multiple user terminals(301-30n) through the network(200) and includes the first/second connection server(10,20), a notification server(30), and a database server(40). The first and the second connection servers process connection for users connected through the wired or wireless communication network. The notification server selectively notifies the user of the event such as mail transmission/reception, or registration of a question or an answer generated from the first and the second mail server(50,60), or a knowledge sharing server(70) depending on the set condition. The notification server includes an event generation receiver(31), an event generator(32), and an event notification part(33).

Description

Event notification system over network and method thereof {SYSTEM FOR NOTIFYING EVENT ON NETWORK AND METHOD THEREOF}

The present invention relates to an event notification system and method through a network, and more particularly, to a system and method for notifying a user of an event occurrence on a network.

Today, there is a wide range of services that provide users with a place to communicate online, such as on the Internet. Users use these spaces to socialize and ask other users for help by asking questions. do. Such services include e-mail services and knowledge sharing services that allow other users to answer a user's questions using the Internet. A representative knowledge sharing service widely used today is the knowledge iN service of Naver (http://www.naver.com).

In recent years, to help users use these services more quickly and conveniently, they can send mail to the user by sending a short message service (SMS) or long message service (LMS) or registering an answer when a mail is sent or an answer is registered. Service to inform you that is being done.

However, this notification service is usually performed unconditionally whenever a mail is received or a reply is registered. Therefore, a large load is placed on the system in order to send a notification message every time a user receives a mail or registers an answer. Therefore, system performance is degraded. In addition, the cost of sending the notification message is increased.

In addition, on the user's side, if the notification message (URL SMS) that has not been checked is duplicated, or if the operator limits the number of notification messages sent per unit time, unnecessary spam or unhelpful answer may cause inappropriate contents. Problems such as losing the chance to receive.

Therefore, the technical problem to be achieved by the present invention is to solve such a conventional problem, to provide a system and method for informing users of event notifications on a network more efficiently.

The event notification method according to an aspect of the present invention for achieving the technical problem, a) when the event is generated by a first user connected through a network, providing a reception number of the second user to be notified of the event occurrence Receiving step; And b) selectively transmitting a notification message indicating the event occurrence to a terminal of a second user corresponding to the reception number according to a setting condition.

In addition, the event notification method according to another aspect of the present invention, a) when the event is generated by a first user connected via a network, receiving a receiving number of the second user to be notified of the event occurrence; b) generating a notification message indicating the event occurrence; c) determining whether the notification message previously sent by the second user has been confirmed; And d) when the second user confirms the previous notification message, transmitting the generated notification message to a terminal of the second user corresponding to the received number.

Event notification system according to another aspect of the present invention, the connection server for performing the connection process for the first users connecting through the network; An event processing server for processing an event according to the user's request; And a notification server configured to receive a notification number indicating the occurrence of the event to a terminal of the second user corresponding to the reception number according to a setting condition after receiving the reception number of the second user to be notified of the event occurrence. .

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention.

In an embodiment of the present invention, notification for various events occurring on a network is not performed in real time, but is performed according to a set condition.

Here, the event includes all activities that occur on the network and need to inform the user whether or not they occur, for example, sending and receiving mail, registering a question or answer in knowledge sharing, or registering another user as an interested person. Activity status, new posts on the bulletin board, etc. The embodiments described below are described based on notifying the registration of questions and answers according to e-mail transmission and reception and knowledge sharing, but the present invention is not limited thereto and can be applied to all events generated on a network.

Next, the structure and operation of an event notification system through a network according to an embodiment of the present invention will be described.

1 illustrates the structure of an event notification system according to an embodiment of the present invention.

As shown in FIG. 1, the event notification system 100 through a network according to an embodiment of the present invention includes a plurality of networks through a network 200, including all types of networks in various forms such as a telephone network, a wired Internet, and a wireless Internet. Is connected to the user terminals 301 to 30n.

The user terminals 301 to 30n are communication devices that can connect to the event notification system 100 through the network 200. For example, various communication devices such as a wired telephone, a wireless terminal, a computer, and a TV that can be connected to the Internet may be used. Can be used. Therefore, users can access the event notification system 100 conveniently and quickly using PC communication, wired Internet, or wireless Internet.

The event notification system 100 connected to the terminal 300 includes first and second access servers 10 and 20, a notification server 30, and a database server 40. It optionally includes a mail server 50, 60, or a knowledge sharing server 70.

The first access server 10 performs a connection process for users connecting through a wired communication network (for example, the first network may be referred to as a wired Internet, etc.) and is called a web server. Can be named. The second access server 20 performs a connection process for users accessing through a wireless communication network (for example, may be referred to as a second network through wireless Internet, etc.), and is called a wireless application protocol (WAP). It can be called a server.

The first mail server 50 provides a mail transmission / reception service to users connected through the first network, and may be called a web mail server. The second mail server 60 provides a mail transmission / reception service to users connecting through the second network, and may also be called a swap mail server.

The knowledge sharing server 70 performs a question and answer registration process by the questioner and answerer connecting through the first and second networks, respectively. In an embodiment, the first and second mail servers 50 and 60 and the knowledge sharing server 70 may be collectively referred to as an event processing server that processes the generated event and notifies the notification server 30.

The notification server 30 selectively receives events such as mail transmission and reception or registration of questions and answers generated by the first and second mail servers 50 and 60 or the knowledge sharing server 70 according to the user's setting conditions. Inform.

To this end, the notification server 30 includes an event generation receiver 31, a message generator 32, and an event notification unit 33 that performs an event occurrence notification according to a set condition. The event occurrence receiver 31 receives the event occurrence information and the user information provided from the event processing server and transfers the event occurrence information and the user information to the message generator 32 and the event notification unit 33, respectively. The message generator 32 generates a notification message according to the event occurrence information, and the event notification unit 33 transmits the generated message to the corresponding terminal according to the user information. In particular, in an embodiment of the present invention, after sending a notification message to the user according to the occurrence of the event, the notification message is transmitted only for the event generated after the user checks the message (setting condition). Here, the notification message may be an SMS or an LMS, and may also be an EMS (Enhanced Message), an MMS (Multimedia Message, etc.) In addition, the generated event (content such as an e-mail, an answer, a question, etc.) may be a predetermined swap page. In the present embodiment, an SMS including a URL of the corresponding swap page is transmitted to the user's wireless terminal so that the user can check the generated event. However, the present invention is not limited thereto, and the message may be transmitted in the form of URL LMS, URL EMS, URL MMS, or the like.

The database server 40 includes a user database 41 and a flag database 42 in which a telephone number (hereinafter, referred to as a radio number) of a user's wireless terminal is stored.

The user database 41 stores a user's radio number corresponding to the user's ID or mail address.

The flag database 41 stores flag information (also known as status information) indicating the notification message confirmation status of the user for each user. The flag is initially set to "T (true)", for example, and then set to "F (false)" when sending a notification message to the user, and then back to "T" when the user acknowledges the notification message. . The event notification unit 33 notifies the user of the event occurrence only when the flag information of the corresponding user is set to "T" when the event occurs. In order to set the flag, the notification server 30 may further include a state setting unit 34 for changing the flag information of the user after recognizing the message confirmation of the user.

In the event notification system according to an embodiment of the present invention as described above, each of the servers 10 to 70 are classified in terms of their function, and the present disclosure is not limited thereto. In addition, each component of the notification server may be implemented as an independent server to handle the corresponding function. Further, the databases 61 to 62 are also not limited to being classified as described above.

Next, the operation of the event notification system according to an embodiment of the present invention will be described based on such a structure.

2 schematically illustrates an interworking relationship between components that are performed when event notification is performed according to an embodiment of the present invention, and the event occurrence notification process according to the embodiment is sequentially illustrated in FIG. 3.

First, as illustrated in FIGS. 2 and 3, a user who wants to generate an event such as sending a mail through a network, asking a question about something, trying to answer a question, or the like, for example, When a URL for connecting to the event notification system 100 is input while a program for connecting to the Internet (for example, a web browser) is run on a PC or the like, this URL information is transferred to a hypertext transfer protocol (HTTP) in the web browser. Is converted and packetized and then transmitted to the event notification system 100 via the Internet (wired Internet). Accordingly, the first access server 10 transmits a web page corresponding to the URL information to the user terminal, and the transmitted web page is converted and displayed in a window state on a web browser, thereby making web connection of the terminal.

On the other hand, when a user connects using a wireless terminal, the URL information is converted into a wireless markup language (WML) through a WAP gateway, and then transmitted to a mobile communication service system (not shown) through a wireless network. The system connects the interrogator's wireless terminal to the second access server 20 of the event notification system 100 according to this URL information. Accordingly, the second access server 20 generates and provides a swap page corresponding to the URL so that the receiver can receive the service through the wireless Internet (S100 to S110).

As described above, after a connection to the event notification system is made via wired or wireless Internet, the user can send an email, ask a question about a specific item, reply to a question, or post a new bulletin board. You can trigger events such as posting posts.

When a user requests to send a mail to a predetermined mail address through a wired or wireless Internet, the first or second mail server 50 or 60 sends the mail to the mail address and then sends the mail to the notification server 30. Notify the occurrence of the event. At the time of notification, event generation information (e-mail transmission completion) and receiving user information (ID or e-mail address of the mail receiver) are provided to the notification server 30 (S120 to S130).

In addition, when a user inputs a question about a specific matter through a wired or wireless Internet, the knowledge sharing server 70 registers the question and notifies the notification server 30 of the question registration, that is, the occurrence of an event. Upon notification, the event occurrence information (question registration) and the receiving user information (where the receiving user may be experts in the category to which the question belongs or those who will request to be notified when a new question is registered in that category, such receiving user ID's, etc.) are provided to the notification server 30 (S140 to S150).

In addition, when a user inputs an answer to a specific question through a wired or wireless Internet, the knowledge sharing server 70 registers the answer and notifies the notification server 30 of the answer registration, that is, the occurrence of an event. Upon notification, the event generation information (answer registration) and user information (where the receiving user is a user who registered a question corresponding to the answer, and the IDs of these receiving users are provided) are provided to the notification server 30 (S160 to S170). ).

As described above, when the event processing completion is notified after the event according to the user's request is performed, the event occurrence receiving unit 31 of the notification server 30 may provide the event occurrence information and the received user information to the event notification unit ( 33) (S180).

When the event notification unit 33 is notified of the occurrence of the event, the event notification unit 33 first searches the flag database 62 based on the received user information to determine a message checking state of the current receiving user (S190). Specifically, when the flag database 62 is searched based on the ID of the user, and the flag corresponding to the ID of the receiving user is activated as "T", that is, when the receiving user confirms a notification message generated previously, As described in the following, the event occurrence notification is performed, and if the flag is not activated as "F", the event occurrence notification is not performed and the next event generation is waited (S200 to S210).

In step S200, when the flag is activated, the event notification unit 33 searches the user database 61 based on the ID (or mail address) of the receiving user, extracts the receiving user's radio number, and generates a message. The unit 32 generates a message for notifying occurrence of an event, for example, a mail transmission notification message when an e-mail is transmitted, a question registration notification message when a question is registered, and a response registration notification message when an answer is registered. (S220 to S230).

Next, the event notification unit 33 transmits the generated notification message to the terminal having the radio number of the corresponding receiving user, so that the receiving user can recognize the event (S240). Then, the flag of the receiving user is set to "F" and deactivated, so that an event generated later is selectively performed according to whether the receiving user checks the message (S250).

In this case, the message transmitted to the receiving user may include a parameter, that is, a URL, for a page (e.g., a mail content providing page, a question providing page, an answer providing page, etc.) capable of confirming the generated event. As shown in the figure, callbacks are based on messages to connect to the system and check for events.

As such, when a receiving user checks an event generated by accessing a system using a message, that is, checking a received mail, checking a question, or confirming an answer, a state setting unit (not shown) of the notification server 30 may be used. 34) sets the flag information of the receiving user to " T " so that a notification message for this event is notified to the receiving user when an event occurs later.

4 shows an example of an event occurrence notification made as described above.

For example, when a user (web intellectual) answers a question, since the flag is initially set to "T", as shown in FIG. 4, the message for registering an answer, that is, the URL SMS 1 is a questioner Is sent to (A). At this time, the flag is changed from "T" to "F".

Then, when the questioner checks the SMS (B), the flag changes from "F" to "T" so that when another web intellectual answers the question, an answer registration notification message (URL SMS 2) is also sent to the questioner. Transmitted (C).

However, if the questioner does not confirm the message sent in step C, the message (URL SMS 3) is not transmitted to the questioner even if a new answer is registered in the next step (D). Thereafter, the interrogator checks the message (URL SMS2) previously transmitted (E), and when a new answer is registered, transmits the message (URL SMS 4) to the interrogator again (F).

In this way, the message according to the occurrence of the event is retransmitted only when the user confirms the message, thereby preventing the user from accumulating unnecessary messages.

Meanwhile, in the above-described embodiment, the setting condition for transmitting the message is whether or not the user confirms the previously transmitted message. However, the setting condition according to the present invention is not limited thereto and may be used for selectively transmitting the message. Conditions can be used. For example, the message may be set only by sending a message only when an event occurs more than a set number, or by sending a message only for an event generated every set time.

In addition, in the above-described embodiment, as a method of measuring a user's message confirmation, it is determined that the user has confirmed the message based on the callback using the message, but the present invention is not limited thereto and may be used in the art. These can all be used.

In addition, in the above embodiment, the notification message is transmitted to the wireless terminal of the user, but the present invention is not limited thereto and may be transmitted to the wired terminal of the user. In this case, the user database 61 preferably corresponds to a number of the wired terminal (for example, a messenger mail address, an e-mail address, a wired telephone number, etc.) corresponding to identification information such as an ID. Accordingly, the number (wired or wireless number) of the user terminal receiving the notification message may be called a reception number.

In addition, in the above embodiment, an example of notifying a mail receiving user of a notification message when a mail transmission occurs is illustrated, but the same may be applied to notifying a user when a mail is received by a predetermined user instead of a mail transmission.

Meanwhile, in the above embodiment, the first and second access servers and the first and second mail servers are implemented as being included in one system, but may be implemented separately from each other. That is, the first or / and second connection server is included in the first system, the first or / and second mail server is implemented in the form of the second system, so that the user is connected to the first system Mail can be sent and received via the mail server of the second system. Even in this case, the event notification as described above may be applied in the same manner, and the event notification may be made through a notification server included in the first system or the second system.

Although specific embodiments of the present invention have been described so far, various modifications are possible without departing from the scope of the present invention.

Therefore, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concept of the present invention as defined in the following claims also fall within the scope of the present invention.

As described above, according to the present invention, the event occurrence notification is performed more efficiently by performing the event generation according to the setting condition.

Therefore, in terms of the system, it is possible to obtain the effect of reducing the load and cost by sending a message.

In addition, on the user's side, if the notification message (URL SMS) that has not been checked is duplicated, or if the operator limits the number of notification messages sent per unit time, unnecessary spam or unhelpful answer may cause inappropriate contents. It is possible to prevent cases such as losing a chance to receive.

1 is a structural diagram of an event notification system according to an embodiment of the present invention.

2 is an exemplary diagram illustrating an interworking relationship between components performed when event notification is performed according to an exemplary embodiment of the present invention.

3 is a flowchart illustrating an event notification process according to an embodiment of the present invention.

4 is an example of event occurrence notification according to an embodiment of the present invention.

Claims (1)

a) when an event is generated by a first user connecting through a network, receiving a reception number of a second user to be notified of the event occurrence; And b) selectively transmitting a notification message indicating the occurrence of the event to a terminal of a second user corresponding to the received number according to a setting condition; Recording medium in which a program implemented with a function including the stored.