KR20100034174A - Apparatus for blocking ip application spam and method thereof - Google Patents

Abstract

PURPOSE: An apparatus for blocking IP application spam and a method thereof are provided to block spam using a registration result from other IP service users. CONSTITUTION: A list management unit(310) manages an originator list using a receiver to prevent application spam reception based on an IP. A policy management unit(320) manages the policy for determining spam from originators using a receiver. A spam score management unit(330) calculates and manages a spam score of an originator based on a list managed by the list management unit. An application spam blocking unit(340) distinguishes whether mail is spam through the policy managed by the policy management unit and the spam score of an originator. The application spam blocking unit prevents spam from being transmitted to a receiver.

Description

Apparatus for blocking IP application spam and method

The present invention relates to network technology, and more particularly, to an additional service technology of a communication network.

This study is derived from the research conducted as part of the Information Communication Standards Development Support Project of the Ministry of Knowledge Economy and the Korea Institute of Information and Telecommunications Research and Development. [Task Management Number: 2008-P1-13-06K83, Internet Telephony Emergency Communication and MoIP Application Standard Development] ]

Spam is not easy to define as one, but it can generally be defined as a large amount of unsolicited advertising mail. E-mail spam is still occurring in large quantities, damaging many service users. In addition to the activation of mobile phones, SMS spam is damaging mobile communication service users. Recently, with the development of IP application services such as Internet telephony, Internet access, and instant messaging, spam based on these services is emerging as a new threat. Spam for these IP application services is mainly discussed with Spam over Instant Messaging (SPIM) and Spam over Internet Telephony (SPIT).

Due to the technical characteristics of the IP application service, it is not easy to prepare an effective countermeasure compared to the existing email, and it is also difficult to apply the existing spam response solution. Typically, filtering through content analysis is widely used to block email spam, but in the case of IP application service, the media used is not limited to text, and often has real-time spam filtering through content analysis. It's a very difficult situation.

On the other hand, black list and white list have been used as one of countermeasures against email spam. Blacklists are lists for registering spammers. When the called party registers the spammer on the blacklist, the spammer registered on the blocklist regards the email as spam when the sender sends the email again. Whitelisting is the opposite of blacklisting, so only those registered on the whitelist can send email.

In the case of a messenger service based on a buddy list, a white list is introduced. However, unlike the messenger service, email can be blocked using blacklist and whitelist, but the effect is not so great. The reason is as follows.

Using blacklists, in principle, e-mails from people registered on the blacklists are considered spam and can be blocked. However, blacklists can be created because the number of spammers is very large and a single sender can create many email accounts. The effectiveness of e-mail spam blocking is not high. In addition, when using a white list in an e-mail service, there is a problem such as having an introduction problem that requires a procedure of requesting to register on a white list. .

However, most of the email services are provided free of charge, which makes it difficult for service providers to provide a list management for effective spam blocking, while various IP application services such as internet phones are provided for a fee. The difference is that it is more advanced than email. The Applicant has derived the present invention based on these differences.

The present invention is derived from this background, it is an object of the present invention to propose a technical method to effectively block the IP application spam.

In accordance with an aspect of the present invention, there is provided an IP application spam blocking device comprising: a list manager configured to manage a sender list for each called party for preventing IP (IP) based application spam incoming; A policy management unit managing a policy for determining spam for senders for each called party; A spam score manager configured to calculate and manage a spam score for each sender based on the list managed by the list manager; And an application spam blocking unit for identifying whether the spam is received by the called party by identifying whether the spam is received through the policy managed by the policy management unit and the spam score of the sender.

The caller list managed by the list manager includes a white list that allows incoming calls and a black list that does not allow incoming calls.

The policy management unit manages a reference spam score for each called party, and the application spam blocking unit compares the reference spam score of the called party managed by the policy management unit with the spam score of the sender to identify whether the spam is spam.

The spam score manager calculates a spam score in consideration of the number of blacklist registrations and the number of whitelist registrations.

On the other hand, the IP application spam blocking method of the present invention for achieving the above-described technical problem is based on the spam score of the sender and the sender of the called party calculated based on the blacklists that do not receive the incoming call and the whitelists that allow the incoming call. Identifying a reference spam score for the; Comparing the spam score with the identified reference spam score to identify whether an IP (IP) call or message to be delivered from the sender to the called party is spam; And if the identification result is spam, blocking the transfer of the IP call or the message.

The method includes verifying that a caller is registered in the called party's whitelist; And confirming whether the sender is registered in the called party's blacklist. The checking of the reference spam score is performed when the sender is not registered in both the whitelist and the blacklist of the called party. It is done.

The present invention has solved the problem of the conventional spam blocking technology using a list, so that it is possible to block spam by using not only the list owned by the individual but also the registration result of other IP service users if necessary. In addition, in order to alleviate the introduction problem of the white list, the concept of the existing white list is changed slightly and applied to the present invention.

Specifically, in the existing spam blocking technology, a person who is not registered on the white list was not able to send an e-mail. However, the initial anti-spam technology may request registration on the white list by introducing itself through e-mail transmission only once. However, in the present invention, the whitelist may be referred to as a collection of registered identifiers determined that the called party is not a spammer, and a person who is not registered in the whitelist cannot transmit an IP call or a message. However, unlike the person registered in the white list, the person who is not registered in the white list can pass an IP call or a message through the spam judgment process through an additional procedure.

As described above, the present invention creates the effect of reducing the damage caused by spam that can occur on the IP application service.

In the present invention, in order to provide IP application spam blocking services using blacklists and whitelists, IP multimedia application service providers provide functions such as management of personal lists, personal IP spam blocking policies, and management of public lists. to provide. In order to perform this function, the present invention proposes to introduce an "IP application spam blocking application server".

In general, an IP application server may perform various functions to provide an IP application service and various additional services. In this aspect, in the present invention, the IP application service provider operates the "IP application spam blocking server" to perform the IP application spam blocking function of the method proposed by the present invention.

The "IP application spam blocking server" having the list management and IP spam response policy management function of the service user proposed by the present invention is logically separated from other application servers, but is physically separated from other application servers like a general application server. Or an integrated server. The "IP Application Spam Protection Server" can also form part of a specific server with various functions for IP application spam protection. However, the part about the physical configuration of the server is outside the scope of the present invention.

In addition to the operation of the "IP application spam blocking server" of the IP service provider, what is necessary for the realization of the present invention is that a method for allowing a called party to register a specific sender on his or her own blacklist or whitelist should be provided.

The foregoing and further aspects of the present invention will become more apparent through the preferred embodiments described with reference to the accompanying drawings. Hereinafter, the present invention will be described in detail to enable those skilled in the art to easily understand and reproduce the present invention.

1 is a block diagram of an overall network for spam blocking IP multimedia application according to the present invention.

Caller 100 may be connected to IP network 500 or may be connected to a non-IP network such as PSTN / mobile network 400. However, since the called party 200 needs to be provided with an IP application service in the present invention, it should be connected to the IP network 600. The application server 300 performs various functions for providing the IP application service and various additional services to the called party 200, and additionally filters the IP application spam according to the characteristic aspect of the present invention.

2 is a block diagram of a server (apparatus) for blocking IP multimedia application spam in accordance with the present invention.

First, the sender 100 and the receiver 200 other than the IP application spam blocking server 300 will be described. The sender 100 attempts to generate an IP call or deliver an IP message, and the call or message generated may or may not be spam. The called party 200 receives an IP call or message and preferably has a list update module 210. The list update module 210 is a module that provides a function for the called party 200 to register an identifier for a specific IP application service user to his / her blacklist or whitelist. When a specific identifier is registered in the list using the called party's IP terminal, a shortcut button or a menu on the IP terminal can be used. In relation to the registration time, it may be registered by simple button operation during or immediately after the call or at the time desired by the called party regardless of call connection. In addition, it may be possible to register a list through a website provided by a service provider, not a called party terminal.

As shown, the IP application spam blocking server 300 includes a list manager 310, a policy manager 320, a spam score manager 330, and an application spam blocker 340. The list manager 310 manages a caller list for each called party. Here, the list is used to prevent incoming IP application spam, and senders are registered. In one embodiment, the caller list for each called party managed by the list manager 310 is divided into a white list and a black list. Callers who are allowed to receive IP calls or messages are registered in the whitelist, and callers who are not allowed to receive IP calls or messages are registered in the blacklist. In one embodiment, these lists are provided from the list update module 210 described above.

The policy manager 320 is a module for managing a policy for determining an IP application spam for each service user. According to a characteristic aspect of the present invention, the policy management unit 320 holds a reference spam score value for each called party. This reference spam score is used as a reference value for making an IP application spam judgment for senders by recipients. The reference spam score is a value set by the called party based on his or her preference for IP application spam blocking. For example, the smaller the value, the lower the rigor against spam blocking.

The spam score manager 330 calculates and manages a spam score of each sender based on the list managed by the list manager 310. Preferably, the spam score manager 330 integrates the blacklist and the whitelist, accumulates and holds the list registration number for each sender, and calculates, holds and manages the spam score for each sender based on this. The specific method for calculating the spam score according to the number of registrations of each sender may be arbitrarily determined by the IP application service provider. For example, a rule in which the spam score increases as the number of registrations in the blacklist increases, and the spam score decreases as the number of registrations in the whitelist increases.

The data held and managed by the spam score management unit 330 may be generated using only the list registration result accumulated by the service users of one IP service provider, or may be integrated with the spam scores of other operators. It is possible. With regard to the generation of spam score data held by the spam score management unit 330, the part of cooperation with other operators is outside the scope of the present invention.

The application spam blocking unit 340 performs a major decision related to performing an IP application spam blocking function using a list, and includes various modules in the server, that is, a list manager 310, a policy manager 320, and a spam score manager 330. Corresponds to the core module for interacting with the spam report material generation unit 350. The application spam blocking unit 340 determines whether or not the sender's IP call or message is spam based on the policy of the service user managed by the policy management unit 320 and the spam score managed by the spam score management unit 330. .

In detail, the application spam blocking unit 340 compares the spam score of the sender 100 managed by the spam score manager 330 with the reference spam score of the called party 200 managed by the policy manager 320. If the spam score value of 100) is higher than or equal to the spam score value of the called party 200, the IP call or message of the sender 100 is regarded as spam and blocked from being delivered to the called party 200.

Meanwhile, the spam report data generation unit 350 additionally implemented in the IP application spam blocking server 300 is used to report to the called party about the blocked IP call or message determined by the application spam blocking unit 340 as spam. Function module to generate data. The data can be in text format or in any other format. The spam report material generator 350 may deliver the generated data to the called party 200 or may provide the called material to the called person 200 through a web page permitted.

3 is an IP multimedia application spam blocking flowchart performed in an application server according to the present invention.

When a call connection or message delivery is attempted to an IP service user managed by the IP application spam blocking server 300, the application spam blocking unit 340 may be connected with the list manager 310 to determine whether the corresponding call or message is spam. By interacting, it is checked whether the caller identifier is registered on the called party's white list (step S300). If the caller identifier is on the whitelist, the call or message is considered non-spam and is forwarded to the called party in the same way as a normal call and message.

If the caller identifier is not registered on the whitelist, the application spam blocker 340 interacts with the list manager 310 to determine whether the call or message is spam and the caller identifier is displayed on the called party's blacklist. Check whether it is registered (step S310). If the sender identifier is registered on the blacklist, the application spam blocking unit 340 considers the call or message as spam and blocks the call or message, and generates a spam report for the spam report material generating unit 350 to report to the called party. To create it. In the procedures up to now, the order of steps S300 and S310 may be reversed.

If the sender identifier is not registered on the blacklist, the application spam blocking unit 340 recognizes that spam determination is not possible only by interaction with the list management unit 310, and requests the policy management unit 320 to determine the criteria of the called party. The spam score value is obtained, and the spam score management unit 330 is requested to obtain a spam score value of the sender (step S320). Then, the obtained two values are compared (step S330).

If the called party's reference spam score value is larger than the sender's spam score, the call or message is regarded as not spam and the call or message is blocked (step S350). Then, the spam report data generation unit 350 generates a spam report (step S360).

So far I looked at the center of the preferred embodiment for the present invention. Those skilled in the art will appreciate that the present invention can be implemented in a modified form without departing from the essential features of the present invention. Therefore, the disclosed embodiments should be considered in descriptive sense only and not for purposes of limitation. The scope of the present invention is shown in the claims rather than the foregoing description, and all differences within the scope will be construed as being included in the present invention.

1 is an overall network configuration for spam blocking IP multimedia application according to the present invention.

2 is a block diagram of an application server for blocking IP multimedia application spam in accordance with the present invention.

3 is an IP multimedia application spam blocking flowchart performed in an application server according to the present invention.

<Description of the symbols for the main parts of the drawings>

310: list management unit 320: policy management unit

330: spam score management unit 340: application spam blocker

350: spam report data generation unit

Claims (10)

A list manager for managing a sender list for each called party to prevent IP-based application spam incoming; A policy management unit managing a policy for determining spam for senders for each called party; A spam score manager configured to calculate and manage a spam score for each sender based on the list managed by the list manager; And An application spam blocker that identifies spam based on a policy managed by the policy manager and a spam score of the sender, thereby preventing spam from being received by the called party; IP application spam blocking device comprising a. The method of claim 1, The sender list managed by the list manager includes an IP list spam blocking device including a white list that allows incoming calls and a black list that does not allow incoming calls. The method of claim 1, The policy management unit manages a reference spam score for each called party, The application spam blocking unit, IP application spam blocking device, characterized in that identifying the spam by comparing the spam score of the sender and the reference spam score of the called party managed by the policy management unit. The method of claim 2, The spam score management unit calculates a spam score in consideration of the number of registrations of the black list and the number of registrations of the white list. The method of claim 4, wherein The spam score management unit may increase the spam score when the number of registrations of the black list increases, and decrease the spam score when the number of registrations of the white list decreases. The method of claim 2, The blacklist and the whitelist, IP application spam blocking device, characterized in that provided from the communication recipient. The method of claim 1, A spam report data generation unit for generating data for reporting to the called party about the IP call or message identified as spam by the application spam blocking unit; IP application spam blocking device further comprising a. Confirming the spam score of the sender and the reference spam score for the sender of the called party calculated based on the unlisted blacklists and the whitelists allowing the incoming callers; Comparing the spam score with the identified reference spam score to identify whether an IP (IP) call or message to be delivered from the sender to the called party is spam; And If the identification result is spam, blocking transmission of the IP call or message; IP application spam blocking method comprising a. The method of claim 8, Checking that the caller is registered in the called party's whitelist; And Checking whether the caller is registered in the blacklist of the called party; The checking of the reference spam score is performed if the sender is not registered in both the whitelist and the blacklist of the called party. The method of claim 8, Generating data for reporting to the called party about the IP call or message identified as spam; IP application spam blocking method further comprising a.

Images