KR100922139B1 - System and method for blocking a multicast spam in pim multicast protocol - Google Patents

Abstract

The multicast spam blocking system in the PIM multicast protocol according to the present invention receives a multicast packet generated from an originating terminal through the Internet, and determines whether the multicast packet is spam or not to request a multicast spam processing request. A receiving terminal transmitting to the receiving router and a spammer list in which spammer information is registered, and updating the spammer list according to the multicast spam processing request received through the receiving router, and connected with the calling terminal transmitting multimedia spam packets. Rendezvous points for deleting multimedia spam packets in conjunction with the originating router.

As described above, in the present invention, the spam information is managed at the rendezvous point in the PIM protocol-based multicast network and the spam information is shared with the sender, thereby multicasting the PIM protocol, for example, the PIM-SM protocol and the BIDIR-PIM protocol. It can be applied to the network to minimize the occurrence of multicast spam to protect the PIM network from multicast spam.

PIM, Spam, Spam Response, PIM-SM, BIDIR-PIM

Description

SYSTEM AND METHOD FOR BLOCKING A MULTICAST SPAM IN PIM MULTICAST PROTOCOL}

The present invention relates to a multicast spam blocking system and method in the PIM multicast protocol that distinguishes and blocks spam when using a protocol independent multicast (PIM) protocol in a multicast network.

The present invention is derived from the research conducted as part of the information and communication standard development support project of the Ministry of Information and Communication and the Ministry of Information and Telecommunication Research and Development. .

Various multimedia services are currently provided, many of which can provide services in a multicast environment. The PIM multicast protocol, which is the most representative protocol among the multicast protocols, can easily provide a multicast service while saving network resources.

As such, multimedia services such as IPTV or multi-chat are very effective when they are serviced using multicast, but are serviced in unicast form due to various problems of the multicast protocol. When the service is provided in the unicast form, network resources are wasted and it is difficult to provide an effective service, which makes it difficult to provide a number of applications in a multicast environment.

One problem with the multicast protocol is spam, which is used in a variety of applications to send unwanted messages, including unwanted advertisements, to a large number of recipients. In particular, the multicast function is a very good environment for spammers, since multiple people, such as IPTV and chat, receive messages simultaneously.

On the other hand, the PIM protocol is a technology that enables multicast communication without a multicast receiver and a multicast sender defined. For this reason, multicast networks using the PIM protocol are exposed to spam.

Conventionally, only the risk of spam is mentioned in a multicast network using the PIM protocol, and no method for blocking the spam is described. In other words, it is possible to easily service IPTV or multi-chatting using the PIM protocol. However, since PIM is not verified, it is difficult to use it in an actual network.

As described above, since a method for preventing spam is not described with respect to the PIM protocol, spam is likely to occur in a network to which the PIM protocol is applied. The reason is that when spammers deliver their advertising messages using only the multicast address, the recipients of the service to that multicast address simply receive the advertising messages sent by the spammers. You can send

The present invention stabilizes the PIM protocol-based multicast network from spam so that numerous services provided by PIM-based multicast can be protected from spam.

The present invention prevents spamming by stopping the multicast spam sending of the terminal sending the multicast spam, increasing the time required for the spam sending process.

As a first aspect of the present invention, the multicast spam blocking system in the PIM multicast protocol is provided with a multicast packet generated from an originating terminal through the Internet, and determines whether the multicast packet is spam by determining whether the multicast packet is spam. A receiving terminal for transmitting a cast spam processing request to a receiving router, a spammer list in which spammer information is registered, updating the spammer list according to the multicast spam processing request received through the receiving router, and receiving a multimedia spam packet. And a rendezvous point for deleting the multimedia spam packet in association with an originating router connected to a transmitting originating terminal.

As a second aspect of the present invention, a method for blocking multicast spam packets in a PIM protocol-based multicast network includes the steps of (a) providing a multicast service between a calling terminal and a receiving terminal over the Internet, and (b) Requesting, by the receiving terminal receiving the multicast spam packet, the multicast transmission packet to the calling router connected to the calling terminal through the receiving router in the process of providing the multicast service, and (c) multicasting at the calling router. Stopping the service.

In the present invention, by managing the spam information at the rendezvous point in the multicast network based on the PIM protocol, and sharing the spam information with the sender, PIM protocol, for example, PIM-SM (Protocol Independent Multicast-Sparse Mode, hereinafter 'PIM- SM ') and BIDIR (BI-DIRectional) -PIM protocols can be applied to multicast networks to minimize the occurrence of multicast spam, thereby protecting the PIM network from multicast spam.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In addition, in describing the present invention, when it is determined that the detailed description of the related known configuration or function may obscure the gist of the present invention, the detailed description thereof will be omitted.

1 is a diagram showing the structure of a PIM-based multicast network for multicast spam blocking according to the present invention, which is based on the Internet 100, and requests all multicast traffic and multicast services by the PIM protocol. It includes a rendezvous point 110, the originating terminal 120 and the receiving terminal 130 receives the. Here, the Internet 100 can be used for an IPv4 network or an IPv6 network.

The rendezvous point 110 includes a spammer list 110a, and a spammer candidate list and a spammer main list exist in the spammer list 110a. The spammer list 110a is updated by the rendezvous point 110 based on the user spam report of the multicast service user, that is, the receiving terminal 130.

The rendezvous point 110 registers information on the originating terminal that has received a spam report of a predetermined number of times or more, that is, spammer information in the spammer main list of the spammer list 110a, and receives spammer information for which a spam report has been received less than a predetermined number of times. By registering in the spammer candidate list, the spammer list 110a is managed.

Each spammer information registered in the spammer candidate list has a counter value incremented based on a spam report, and spammer information having a counter value equal to or greater than a predetermined policy threshold is registered in the spammer main list.

Waiting time is set for each spammer information in the spammer list 110a, and the spammer information (spammer information in the spammer main list) that does not transmit a multicast spam packet during the waiting time is deleted from the spammer main list, Spam information without spam reports from any receiving terminal is deleted from the spam candidate list. Here, the spammer information deleted from the spammer main list will be registered in the spammer candidate list.

The originating terminal 120 is serviced by the originating router 115, the originating terminal 120 reported by the multicast service user of the originating terminal 120 in the network configuration for spam blocking of the present invention multicast Become a spammer.

The originating router 115 has a local spammer list 115a and blocks the multicast spam packets generated at the originating terminal 120 based on the local spammer list 115a. That is, when the originating terminal 120 registered in the local spammer list 115a generates a multicast spam packet, the originating terminal 120 deletes it to block the generation of spam traffic.

The local spammer list 115a is updated at the request of the rendezvous point 110.

Each spammer in the local spammer list 115a has a waiting time set in the spammer list 110a as described above, and the waiting time is determined by a time value specified in the multicast spam block processing request of the rendezvous point 110. Is set.

The originating router 115 transmits a predetermined message to the originating terminal 120 based on the multicast spam blocking processing request of the rendezvous point 110, for example, a message such as "multicast spam interruption", and the receiving router 125. Block the transmission of PIM multicast packets at the request of.

In addition, the originating router 115 deletes the spammer information that does not transmit the multicast spam packet from the local spammer list 115a during the waiting time.

The receiving terminal 130 is connected to the Internet 100 by the receiving router 125, and the receiving router 125 rendezvous points the multicast spam registration and blocking request according to the multicast spam processing request of the receiving terminal 130. 110 and the originating router 115 to transmit.

The user of the receiving terminal 130, that is, the receiver, may request the blocking of spam by using a spam blocking remote control 130a or a device or software that can inform that the content received from the network is spam. ) Processes the spam blocking request through interworking with the receiving router 125.

2 is a block diagram showing the internal configuration of the rendezvous point, originating router, receiving router, originating terminal and receiving terminal according to the present invention.

As illustrated in FIG. 2, the rendezvous point 110 includes a rendezvous point function 202 for providing a PIM multicast router function and a spammer list management function 204 for managing a spammer list 110a. In addition, the network operator includes a spam policy setting function 206 for setting a policy for blocking spam, a spam blocking function 208 for blocking actual spam, and the like.

The originating router 115, as a router at the originating terminal side, includes a PIM multicast routing function 210 and a multicast server function 212 for providing PIM multicast service, and originating terminal 110 for sending spam. There is a local spammer list 115a, a multicast spam packet processing function 214, a multicast spam blocking function 216, and a multicast outage request function 218, which store a list for the user (originating spammers) of.

The originating terminal 120 has a multicast client function 220 for providing a general multicast service and a multicast call interruption notification function 222 for preventing spam.

The reception router 125 has a PIM multicast routing function 224 and a multicast server function 226 for providing a general multicast service, and a multicast spam processing request function 228 for blocking spam.

The receiving terminal 130 includes a multicast client function 230 to provide a multicast service, a sprint multicast information notification function 232, and a multicast spam processing request function 234 to block spam.

A process of blocking spam in a network configuration having the above configuration will be described with reference to FIG. 3.

3 is a diagram illustrating a process for blocking spam on a PIM-SM protocol according to an embodiment of the present invention.

Referring to FIG. 3, a general multicast packet processing process is started first in the PIM-SM protocol, that is, a multicast packet transmission process from an originating terminal 120 to a receiving terminal 130 is initially delivered in the PIM-SM protocol. Multicast packets are forwarded according to the scheme (301, 302, 303, 304).

In addition, when the process of processing the PIM-SM protocol between the originating router 115 and the receiving router 125 is completed (305), multicast packet transmission from the originating terminal 120 to the receiving terminal 130 is defined in the PIM-SM protocol. After the PIM-SM protocol is processed, the multicast packet is delivered according to the delivery scheme (306, 307, 308).

The above processes are packet forwarding by the general PIM-SM multicast protocol.

Through the above process, the receiving terminal 130 checks the information of the received multicast packet to determine whether it is a spam packet (309). If the received multicast packet is a spam packet as a result of the determination of step 309, the receiving terminal 130 130 operates the multicast information notification function 232 to request a spam block. That is, when the multicast information notification function 232 of the receiving terminal 130 is operated, the receiving terminal 130 requests 310 to the receiving router 125 the interruption of the multicast transmission according to the general multicast function. The request for processing the multicast spam packet is forwarded to the receiving router 125 (311).

The reason for separately transmitting the multicast transmission stop request and the multicast spam processing request in the present invention is to add a multicast spam packet processing function without interfering with a general multicast protocol.

Upon receipt of the multicast transmission stop request, the receiving router 125 requests 312 to stop the PIM-SM multicast transmission to the originating router 115, whereby the originating router 115 blocks the multicast spam blocking function 218. Blocking the transmission of the multicast packet, which is requested to stop using (313).

Meanwhile, the reception router 125 receiving the multicast spam processing request from the reception terminal 130 transmits the multicast spam registration request 314 to the rendezvous point 110. The rendezvous point 110 reviews the content and updates the spammer candidate list 110a (315). That is, if the sender who sent the multicast spam is the first registration, the sender information (spammer information) is registered in the spammer candidate list. If the caller was previously reported, only the counter value in the spammer candidate list is incremented to update the spammer candidate list 110a.

In addition, if there is spammer information in which the counter value exceeds a policy threshold by examining each counter value in the spammer candidate list of the spammer candidate list 110a, the rendezvous point 110 includes the spammer information in excess of the threshold value in the spammer list. After registration (316) and sends a multicast spam block processing request to the originating router 115 (317). At this time, the multicast spam blocking request includes spammer information newly registered in the spammer list.

The originating router 115 registers the spammer information included in the multicast spam blocking request in the local spammer list 214 (318), and requests the spam termination to the originating terminal 120 corresponding to the spammer information (319). At this time, even if the spam terminal originating terminal 120 continues to transmit the multicast spam packet 320 even if the spam stop request, the originating router 115 is the originating terminal 120 registered in the local spammer list 214 The multicast packet transmitted from the network is directly deleted without transferring the multicast packet to the Internet 100 (321).

4 is a flowchart illustrating a process for blocking spam on the BIDIR-PIM protocol according to another embodiment of the present invention.

Referring to the difference between the PIM-SM protocol and the BIDIR-PIM protocol, the PIM-SM protocol confirms the multicast sender and the receiver at the rendezvous point 110, and provides the sender information to the multicast receiver to the next. It includes the function of receiving the multicast packet directly from the calling party. The BIDIR-PIM protocol receives the multicast packet through the rendezvous point 110 without providing the calling party information to the receiving party. This is useful when providing a multi-point service.

In the BIDIR-PIM protocol, as shown in FIG. 4, the general multicast packet processing process is started first, and when the multicast packet is determined to be spam, the spam blocking function is operated. Thus, in the multicast packet transmissions 401, 402, 403, and 404 from the originating terminal 110 to the receiving terminal 130, the multicast packets are delivered according to the delivery scheme defined in the BIDIR-PIM protocol. This process is a packet delivery method using the general BIDIR-PIM multicast protocol.

Through the above process, the receiving terminal 130 checks the information of the received multicast packet to determine whether it is a spam packet (405). If the received multicast packet is a spam packet as a result of the determination of step 405, the receiving terminal ( 130 operates the multicast information notification function 232 to request spam blocking. That is, when the multicast information notification function 232 of the receiving terminal 130 is operated, the receiving terminal 130 requests 406 the multicast transmission interruption according to the general multicast function to the receiving router 125. The request for processing the multicast spam packet is forwarded to the receiving router 125 (407).

The receiving router 125 receiving the transmission stop request transmits the BIDIR-PIM transmission stop request 408 to the rendezvous point 110. Thus, the rendezvous point 110 performs a general BIDIR-PIM interruption function 409.

In addition, the receiving router 125 receiving the spam packet processing request forwards the multicast spam registration request 410 to the rendezvous point 110. The rendezvous point 110 reviews the multicast spam registration request and updates the spammer candidate list 110a (411). That is, if the sender who sent the multicast spam is the first registration, the sender information (spammer information) is included in the spammer candidate list. Register and update the spammer candidate list 110a by incrementing only the counter value in the spammer candidate list if the sender was previously reported.

In addition, if there is spammer information in which the counter value exceeds a policy threshold by examining each counter value in the spammer candidate list of the spammer candidate list 110a, the rendezvous point 110 includes the spammer information in excess of the threshold value in the spammer list. After registering (412), the originating router 115 sends a multicast spam blocking processing request (413). At this time, the multicast spam blocking request includes spammer information newly registered in the spammer list.

The originating router 115 registers the spammer information included in the multicast spam blocking request in the local spammer list 214 (414), and requests the spam termination to the originating terminal 120 corresponding to the spammer information (415). . At this time, when the spam terminal originating terminal 120 continues to transmit the multicast spam packet (416) even if receiving a request to stop spam, the originating router 115 from the originating terminal 120 registered in the local spammer list 214 The transmitted multicast packet is immediately deleted without being transferred to the Internet 100 (417).

5 is a flowchart illustrating a process of releasing a registered spammer according to the present invention.

Referring to FIG. 5, when a multicast packet is continuously transmitted 501 from the originating terminal 120 registered as a spammer, that is, the originating terminal 120 corresponding to the spammer information registered in the locale spammer list 214, the originating terminal 120 is transmitted. The router 115 deletes the packet (502).

However, if there is no multicast packet transmission registered as spam from the originating terminal 120 for a predetermined time, the originating router 115 does not transmit the multicast packet registered as spam for a predetermined time in the local spammer list 214. After deleting 503 information 503, the multicast spam cancel request 504 is transmitted to the rendezvous point 110.

The rendezvous point 110 deletes caller information from the spammer list of the spammer list 110a and registers it in the spammer candidate list (505).

The rendezvous point 110 deletes the caller information from the spammer candidate list (507) when there is no multicast spam registration request corresponding to the caller information from the receiving side, that is, the receiving router 125 for a predetermined time (506).

Accordingly, the multicast packet generated in the originating terminal 120 is transmitted to the receiving terminal 130 by the general PIM protocol (508, 509, 510).

6 is a flowchart illustrating a process for blocking multicast spam at an originating terminal which is a spammer terminal according to the present invention.

In general, the originating terminal 120 registered as a spammer terminal does not have a special function for blocking spam because it is operated according to the spammer's will, but by informing the originating terminal 120 that spamming is being made, Spamming can be prevented.

First, as shown in FIG. 6, the originating terminal 120 registered as a spammer terminal transmits 602 a multicast packet to the originating router 115 when there is a multicast packet transmission request 601 in the application.

The originating terminal 120 receives the packet from the originating router 115 (611), analyzes the message in the packet (612), and if the multicast spam stop request, the "spam" in the display window (not shown) of the originating terminal 120 A message " Aborting Request " "

7 is a flowchart illustrating a process for blocking multicast spam in an originating router according to the present invention.

Referring to FIG. 7, when a multicast packet is received from an originating terminal 120 registered as a spammer terminal (651), the originating router 115 determines whether the packet is sent from an originating terminal in its local spammer list 214. Judge (652). As a result of the determination in step 652, when the originating terminal registered in the local spammer list 214 is a packet sent, the originating router 115 deletes the packet, initializes 653 the waiting time set in the local spammer list 214, Otherwise, the multicast packet is transmitted to the rendezvous point 110 or the neighboring router (654).

On the other hand, when the originating router 115 receives the multicast protocol packet from the outside (661), it checks whether the multicast protocol packet is the multicast spam blocking processing request 662, otherwise it performs the general multicast protocol processing 663, If yes, add the originating spammer's information to the local spammer list 214 and set the waiting time specified in the message (664). The originating router 115 then sends a multicast spam abort request 665 to the originating terminal 120, which is the originating spammer.

The outgoing router 115 manages the local spammer list 214, that is, each spammer information registered in the local spammer list 214 has a waiting time set, and the outgoing router 115 has corresponding spammer information during the waiting time. If there is no reception of the multicast spam packet from the originating terminal 120 corresponding to (671), the originating router 115 deletes the spammer information that has exceeded the waiting time from the local spammer list 115a (672), and the rendezvous point ( 110, a multicast spam release request 673 is sent.

8 is a flowchart illustrating a process for blocking multicast spam at a rendezvous point according to the present invention.

Referring to FIG. 8, when the rendezvous point 110 receives the multicast packet (701), the rendezvous point 110 checks whether the packet is in the spammer list 110a (702). If the check result of step 702 indicates that the packet is a spammer packet, the packet is deleted (703). Otherwise it sends 704 a multicast packet to a neighboring router if necessary by the general multicast function.

When the rendezvous point 110 receives the multicast protocol packet 711 and then the received multicast protocol packet is a multicast spammer registration request 712 message, it is determined whether the spammer information exists in the spammer list 110a (713). do.

As a result of the determination in step 713, if the spammer information is present in the spammer main lease of the spammer list 110a, the rendezvous point 110 ignores the packet (714); otherwise, the spammer is in the spammer candidate list of the spammer list 110a. Verify that the information exists (715).

As a result of the determination in step 715, if spammer information exists in the spammer candidate list, the counter value in the spammer candidate list is incremented (717); otherwise, the received spammer information is added to the spammer candidate list (716).

After performing steps 716 and 717, the rendezvous point 110 checks the counter value of spammer information in the spammer candidate list.

If the counter value in the spammer candidate list is greater than the spammer counter policy threshold defined by the network operator (718), the rendezvous point 110 adds the corresponding spammer information to the spammer list in the spammer candidate list (719) and then sends the originating router ( Send a multicast antispam processing 720 message.

On the other hand, the flow proceeds to step S718 after step 716.

If the multicast protocol packet received by the rendezvous point 110 is a multicast anti-spam request 721 message, the corresponding spammer information is deleted from the spammer list of the spammer list 110a (722) and the spammer information is added to the spammer candidate list. Add.

If the multicast protocol packet received by the rendezvous point 110 is a general multicast protocol 731 message, general multicast protocol processing 732 is performed.

If the multicast spammer registration request is not received for a predetermined time, that is, a preset waiting time, for all spammer information registered in the spammer candidate list managed by the rendezvous point 110 (741), the rendezvous point 110 corresponds to the spammer candidate list. The spammer information is deleted (742).

9 is a flowchart illustrating a process for blocking multicast spam in a reception router according to the present invention.

Referring to FIG. 9, when the receiving router 125 receives the multicast packet 801, the receiving router 125 transmits the multicast packet to the receiving terminal 130 (802). This is the same as general multicast packet processing. As the receiving router 125 receives the multicast protocol packet 811, if the received multicast protocol packet is not the multicast spam processing request 812 message, the receiving router 125 performs the general multicast protocol processing 813. If the multicast protocol packet is a spam processing request message, a multicast spam registration request 814 is made to the rendezvous point 110.

10 is a flowchart illustrating a process for blocking multicast spam in a receiving terminal according to the present invention.

Referring to FIG. 10, when the receiving terminal 130 receives 851 a multicast packet, the receiving terminal 130 determines whether it is a spam packet, which is determined by a user who uses the receiving terminal 130.

As a result of the determination in step 852, if the multicast packet is not a spam packet, the receiving terminal 130 performs normal packet processing 853. If the multicast packet is a spam packet, the service user will designate spam in various ways. A multicast spam processing request 854 message is sent to 125.

It has been described so far limited to one embodiment of the present invention, it is obvious that the technology of the present invention can be easily modified by those skilled in the art. Such modified embodiments should be included in the technical spirit described in the claims of the present invention.

1 is a diagram illustrating a structure of a PIM-based multicast network for multicast spam blocking according to the present invention.

2 is a block diagram showing the internal configuration of the rendezvous point, the originating router, the receiving router, the calling terminal and the receiving terminal according to the present invention;

3 is a diagram illustrating a process for blocking spam on a PIM-SM protocol according to an embodiment of the present invention.

4 is a flowchart illustrating a process for blocking spam on a BIDIR-PIM protocol according to another embodiment of the present invention.

5 is a flowchart illustrating a process of releasing a registered spammer according to the present invention;

6 is a flowchart illustrating a process for blocking multicast spam at an originating terminal which is a spammer terminal according to the present invention.

7 is a flowchart illustrating a process for blocking multicast spam in an outgoing router according to the present invention;

8 is a flowchart illustrating a process for blocking multicast spam at a rendezvous point according to the present invention;

9 is a flowchart illustrating a process for blocking multicast spam in a reception router according to the present invention.

10 is a flowchart illustrating a process for blocking multicast spam in a receiving terminal according to the present invention.

<Description of the code | symbol about the principal part of drawing>

100: Internet 110: Rendezvous Point

110a: Spammer List 115: Outgoing Router

120: outgoing terminal 125: receiving router

130: receiving terminal 115a: local spammer list

Claims (25)

Anti-spam system in multicast network based on PIM protocol, A receiving terminal receiving a multicast packet generated from an originating terminal through the Internet, determining whether the multicast packet is spam, and sending the multicast spam processing request to a receiving router; A spammer list having spammer information registered therein, the spammer list being updated according to a multicast spam processing request received through the receiving router, and linked with an originating router connected to an originating terminal transmitting multimedia spam packets; Rendezvous point to drop spam packets Multicast spam blocking system in the PIM multicast protocol comprising a. The method of claim 1, The PIM protocol is a multicast spam blocking system in the PIM multicast protocol, characterized in that the PIM-SM protocol or BIDIR-PIM protocol. The method of claim 2, When the PIM protocol is the PIM-SM protocol, the receiving router requests the originating router to stop transmitting the multicast packet in response to the multicast spam processing request to stop the transmission of the multicast packet. Multicast Antispam System in Cast Protocol. The method of claim 2, When the PIM protocol is the BIDIR-PIM protocol, the receiving router requests the rendezvous point to stop the multicast packet in response to the multicast spam processing request to stop transmission of the multicast packet. Multicast Antispam System in Cast Protocol. The method of claim 1, The spammer list includes a spammer main list in which spammer information in which the multicast spam processing request has been received is registered, and a spammer information in which the multicast spam processing request is received in less than the predetermined number of times is registered. A multicast spam blocking system in the PIM multicast protocol, characterized by a spammer candidate list. The method of claim 5, wherein Each spammer in the spammer list has a waiting time set in the multicast spam blocking system according to the PIM multicast protocol. The method of claim 6, In the PIM multicast protocol, the rendezvous point deletes spammer information in the spammer main list without transmission of multicast spam packets during the waiting time from the spammer main list, and registers the spammer candidate list in the spammer candidate list. Multicast Anti-Spam System. The method of claim 6, The rendezvous point deletes the spammer information in the spammer candidate list without a multicast spam processing request from any receiving terminal during the waiting time from the spammer candidate list. system. The method of claim 5, wherein In each spammer registered in the spammer candidate list, a counter value is set, and when there is a multicast spam registration request for any spammer information registered in the spammer candidate list from the receiving router, the random spammer information Multicast spam blocking system in the PIM multicast protocol, characterized in that to increase the counter value of. The method of claim 9, The rendezvous point registers spammer information having the counter value equal to or greater than a predetermined policy threshold value in the spammer main list. The method of claim 5, wherein The originating router includes a local spammer list in which spammer information is registered based on a multicast spam block processing request generated at the rendezvous point as the spam router is added to the spammer main list of the spammer list. Multicast Anti-Spam System in. The method of claim 11, Each spammer in the local spammer list has a waiting time set in the multicast spam blocking system according to the PIM multicast protocol. The method of claim 12, The wait time is a time specified in the multicast spam blocking processing request, multicast spam blocking system in the PIM multicast protocol. The method of claim 12, The originating router deletes any spammer information that does not transmit a multicast spam packet during the waiting time from the local spammer list, and requests the rendezvous point to deregister the multicast spam. Multicast Anti-Spam System in. The method of claim 14, The rendezvous point deletes the arbitrary spammer information from the spammer main list based on the multicast spam release request, and registers the random spammer information in the spam candidate list. Multicast Anti-Spam System in. The method of claim 11, The outgoing router, The multicast spam blocking system of the PIM multicast protocol according to claim 1, wherein the multicast spam blocking processing request is transmitted from the rendezvous point to an originating terminal transmitting a multicast spam packet. A method for processing multicast spam packets in a multicast network based on the PIM protocol, (a) providing a multicast service between a calling terminal and a receiving terminal through the Internet; (b) the receiving terminal receiving the multicast spam packet in the process of providing the multicast service, requesting to stop the multicast transmission to the calling router connected to the calling terminal through the receiving router; (c) stopping the multicast service at the originating router Multicast spam blocking method in the PIM multicast protocol comprising a. The method of claim 17, The spam processing method, Sending, by the receiving router, a multicast spam processing request to a rendezvous point of the internet; Updating a spammer list having a spammer list and a spammer candidate list based on the multicast spam processing request of the receiving terminal at the rendezvous point; Multicast spam blocking method in the PIM multicast protocol further comprising. The method of claim 18, The spam processing method, Requesting multicast spam blocking processing from the originating router after updating the spammer list; Deleting the multicast spam packets generated at the originating terminal at the originating router according to the multicast spam blocking processing request; Multicast spam blocking method in the PIM multicast protocol comprising a. The method of claim 19, Dropping the multicast spam packet, Updating a local spammer list in which the spammer information is registered in the originating router according to the multicast spam blocking processing request; Transmitting a message to a calling terminal transmitting the multicast spam based on the multicast spam blocking processing request; Multicast spam blocking method in the PIM multicast protocol further comprising. The method of claim 20, Updating the local spammer list, In the PIM multicast protocol, a waiting time is set in the spammer information for the originating terminal transmitting the multicast spam packet using the time value set in the multicast spam blocking processing request and registered in the local spammer list. How to block multicast spam. The method of claim 21, The spam processing method, Deleting any spammer information when there is no transmission of a multicast spam packet from an originating terminal corresponding to the random spammer information for a waiting time set in the random spammer information in the local spammer list; Initializing a waiting time for the random spammer information when there is a transmission of a multicast spam packet from a source terminal corresponding to the arbitrary spammer information within the waiting time set for the arbitrary spammer information; Multicast spam blocking method in the PIM multicast protocol further comprising. The method of claim 18, Updating the spammer list, And increasing a counter value for spammer information in the spammer candidate list or registering in the spammer candidate list based on the multicast spam registration request. The method of claim 23, The spam processing method, Comparing a counter value of spammer information in the spammer candidate list with a preset policy threshold; Registering spammer information having the counter value equal to or greater than a predetermined policy threshold value in the spammer list as a result of the comparison; Multicast spam blocking method in the PIM multicast protocol comprising a. The method of claim 17, The spam processing method, When the PIM protocol is a BIDIR-PIM protocol, requesting the receiving terminal to stop multicast transmission through the receiving router through the receiving router; Stopping the multicast service at the originating router Multicast spam blocking method in the PIM multicast protocol comprising a.

Images