WO2016074366A1 - Method and device for testing multicast function of access device - Google Patents

Abstract

The present invention provides a method and a device for testing the multicast function of an access device. The method comprises: a multicast server receiving multicast protocol packets sent from an access device, said packets being used to call a designated multicast server port capable of executing a loop back function; calculating a multicast packet flow value on the designated port; on the basis of calculation results, determining whether the access device is able to perform a multicast function. In the related art, when testing whether an access device is able to perform a multicast function normally, a technician must personally visit the site of the access device to perform testing. The present invention solves this problem and increases access device testing efficiency while reducing expenses.

Description

Method and device for detecting multicast function of access device Technical field

The present invention relates to the field of communications, and in particular, to a method and apparatus for detecting a multicast function of an access device.

Background technique

With the continuous development of broadband access technology, almost all residential buildings and hotels and other places can watch the live broadcast of Internet Protocol Television (IPTV).

At the same time of the rapid expansion of the access device, a large number of access devices need to verify whether the user can perform normal IPTV live broadcast services during the deployment process. The access devices in the related technologies are generally far away from the central office and are in the user. In the vicinity, that is, when the access device needs to be detected, the relevant engineer needs to perform a large number of repeated manual acceptance work with the portable computer near the user, and the workload of the access device can be imagined for such a large number of access devices. Large, it requires a lot of manpower and financial resources for such opening and acceptance work. In the actual commercial process, if there is a complaint that the access device cannot be accessed normally or abnormally accessed, the relevant engineer needs to go to the user to obtain the relevant information of the access device to facilitate the analysis and resolution of the multicast function.

In the related art, when it is necessary to verify whether the access device can perform the multicast function normally, the related worker needs to go to the access device to check the problem personally, and no effective solution has been proposed yet.

Summary of the invention

The main purpose of the present invention is to provide a method and a device for detecting the multicast function of an access device, so as to at least solve the related art, when it is required to verify whether the access device can perform the multicast function normally, the related worker needs to access the user personally. The problem of inspection at the equipment.

According to an embodiment of the present invention, a method for detecting a multicast function of an access device is provided, including: a multicast server receiving a multicast protocol packet sent by an access device, where the multicast protocol packet is used. The specified port of the multicast server that can perform the loopback function is called; the traffic value of the specified port multicast packet is counted; and the access device is configured to perform the multicast function according to the statistics.

Preferably, the multicast protocol packet includes a multicast join message and a multicast leave message.

Preferably, when the multicast protocol packet is the multicast join message, the statistics of the traffic value of the specified port multicast packet includes: the multicast server receives the loopback of the specified port. After the message, the specified The port is added to the preset multicast forwarding table. The multicast forwarding table is used to forward the multicast packet to the specified port. The traffic value of the multicast packet on the specified port is counted.

Preferably, the multicast protocol packet further includes: a multicast query message, before the statistics of the traffic value of the multicast packet on the specified port, the method further includes: the multicast server periodically sending a multicast query Transmitting the packet to the access device; the multicast server receiving the multicast join message sent by the access device in response to the query message, to determine that the access device can forward the multicast packet normally Text.

Preferably, determining whether the access device is capable of performing a multicast function according to the statistical result includes: determining whether the traffic value is greater than a predetermined threshold, and when the determining result is yes, the access device is capable of performing a multicast packet. Forwarding; when the judgment result is no, the access device cannot perform forwarding of the multicast packet.

Preferably, when the multicast protocol packet is the multicast leaving packet, the statistics of the traffic value of the specified port multicast packet includes: the multicast server receiving the multicast sent by the access device The leaving message, where the leaving message is used to indicate that the preset multicast forwarding table is cleared; after the multicast forwarding table is emptied, the forwarding of the specified port multicast packet is interrupted; and the specified port is counted. The traffic value of the multicast packet.

Preferably, determining whether the access device can perform the multicast function according to the statistics includes: determining whether the traffic value is less than a predetermined threshold, and when the determining result is yes, the access device is capable of executing the multicast report. The interruption of the text; when the judgment result is no, the access device is unable to perform the interruption of the multicast message.

According to another embodiment of the present invention, a device for detecting a multicast function of an access device is provided, which is located in a multicast server, and includes: a receiving module, configured to receive a multicast protocol packet sent by the access device, where The multicast protocol packet is used to invoke a specified port of the multicast server that can perform the loopback function; the statistics module is configured to collect the traffic value of the specified port multicast packet; the determining module is set according to the statistical result. Determining whether the access device is capable of performing a multicast function.

Preferably, the multicast protocol packet includes a multicast join message and a multicast leave message.

Preferably, when the multicast protocol packet is the multicast join message, the statistics module further includes: a joining unit, configured to: after receiving the join message of the specified port loopback, The designated port is added to the preset multicast forwarding table. The forwarding unit is configured to forward the multicast packet to the designated port according to the preset multicast forwarding table. The first statistical unit is configured to perform the specified Indicates the traffic value of the multicast packet on the port.

Preferably, the multicast protocol message further includes: a multicast query message, the statistics module further includes: a sending unit, configured to periodically send a multicast query message to the access device; and the first receiving unit , set to receive The access device sends a multicast join message in response to the query message to determine that the access device can forward the multicast packet normally.

Preferably, the determining module includes: a first determining unit, configured to determine whether the traffic value is greater than a predetermined threshold, wherein, when the determination result is yes, the access device can perform forwarding of the multicast packet; When the judgment result is no, the access device cannot perform forwarding of the multicast packet.

Preferably, when the multicast protocol packet is the multicast leave message, the statistic module includes: a second receiving unit, configured to receive a multicast leave message sent by the access device, where The leaving message is used to indicate that the preset multicast forwarding table is cleared; the interrupting unit is configured to interrupt the forwarding of the specified port multicast packet after the multicast forwarding table is emptied; the second statistical unit sets The traffic value of the multicast packet of the specified port is counted.

Preferably, the determining module includes: a second determining unit, configured to determine whether the traffic value is less than a predetermined threshold, wherein, when the determining result is yes, the access device is capable of performing the interruption of the multicast packet When the judgment result is no, the access device cannot perform the interruption of the multicast message.

The multicast server is configured to receive the multicast protocol packet sent by the access device, where the multicast protocol packet is used to invoke the designated port of the multicast server that can perform the loopback function; The value of the traffic is determined based on the statistics. The method of determining whether the access device can perform the multicast function is based on the statistics. In the related art, when it is necessary to check whether the access device can perform the multicast function normally, the relevant worker needs to go to the access device in person. The problem of inspection has improved the efficiency of inspection of access equipment and saved expenses.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

1 is a flowchart of a method for detecting a multicast function of an access device according to an embodiment of the present invention;

2 is a structural block diagram of a device for detecting a multicast function of an access device according to an embodiment of the present invention;

3 is a block diagram 1 of an optional structure of a device for detecting a multicast function of an access device according to an embodiment of the present invention;

4 is a block diagram 2 of an optional structure of a device for detecting a multicast function of an access device according to an embodiment of the present invention;

5 is a block diagram 3 of an optional structure of a device for detecting a multicast function of an access device according to an embodiment of the present invention;

6 is a block diagram 4 of an optional structure of a device for detecting a multicast function of an access device according to an embodiment of the present invention;

7 is a block diagram 5 of an optional structure of a device for detecting a multicast function of an access device according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of protocol packets and multicast flow directions during a test according to an alternative embodiment of the present invention.

detailed description

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

In this embodiment, a method for detecting a multicast function of an access device is provided. FIG. 1 is a flowchart of a method for detecting a multicast function of an access device according to an embodiment of the present invention. As shown in FIG. The following steps:

Step S102: The multicast server receives the multicast protocol packet sent by the access device.

The multicast protocol packet is used to invoke a designated port in the multicast server that can perform the loopback function.

Step S104: Count the traffic value of the multicast packet of the specified port.

Step S106: Determine, according to the statistical result, whether the access device can perform the multicast function.

In this embodiment, the multicast server is configured to receive the multicast protocol packet sent by the access device, where the multicast protocol packet is used to invoke the designated port of the multicast server that can perform the loopback function; If the access device is capable of performing the multicast function according to the statistics, it is resolved that the related worker needs to go to the access device personally when it is necessary to check whether the access device can perform the multicast function normally. The problem of inspection has improved the efficiency of inspection of access equipment and saved expenses.

The specified port involved in the above steps in the present embodiment is preferably a loopback interface, and the loopback function means that after the loopback interface is invoked, the loopback interface sends the multicast packet to the port of the access device. At this time, the port of the access device is connected, and the multicast packet is looped back to the port of the access device. The loopback interface receives the multicast protocol packet sent by the access device. Check whether the access device receives the packet normally.

After the above test is complete, the loopback function is disabled to prevent the downstream device from being looped back. This causes the impact of the uplink device. Therefore, after the loopback is successful, you need to disable the loopback function.

There are a plurality of multicast protocol packets involved in this embodiment. In an optional implementation manner of this embodiment, the multicast join message and the multicast leave message may be used.

In this embodiment, the method for determining whether a multicast packet can reach the access device normally is different. In an optional implementation manner of this embodiment, the multicast protocol packet is used for multicast join message. In the following manner, the method includes the following steps:

Step S11: After receiving the join message of the loopback of the specified port, the multicast server adds the designated port to the preset multicast forwarding table.

Step S12: Forward the multicast packet on the designated port according to the preset multicast forwarding table.

Step S13: Count the traffic value of the multicast packet of the specified port.

In the optional implementation manner of this embodiment, the traffic value can be obtained by counting the number of packets per second or the number of packets per second in the multicast packet. The manner of the above-mentioned statistical flow rate is only an optional embodiment of the present embodiment, and is not limited to the present invention. Other ways of collecting the multicast packet traffic value are also within the protection scope of the present invention.

In addition, before the foregoing step S13, in order to be able to calculate the correct traffic value, the optional embodiment in this embodiment adopts the following manner to determine whether the access device is still forwarding the multicast packet, and the method includes the following steps:

Step 21: The multicast server periodically sends a multicast query message to the access device.

Step 22: The multicast server receives the multicast join message in response to the query message, and determines that the access device can forward the multicast packet normally.

In an optional embodiment of the present embodiment, whether the access device can perform normal multicast packet forwarding is determined according to the following manner: determining whether the traffic value is greater than a predetermined threshold. If the result of the determination is yes, the access device can perform the forwarding of the multicast packet. If the determination result is no, the access device cannot forward the multicast packet. It should be noted that the above-described manners are merely exemplary embodiments of the present invention, and are not intended to limit the present invention.

In another optional implementation manner of this embodiment, a method for determining whether a multicast packet can be normally interrupted is provided. In this embodiment, the multicast protocol packet is a multicast leaving packet, and therefore, statistics are performed. The traffic value of a specified port multicast packet can be implemented in the following manner:

Step S31: The multicast server receives the multicast leaving message sent by the access device, where the leaving message is used to indicate to clear the preset multicast forwarding table.

Step S32: After the multicast forwarding table is cleared, the multicast forwarding of the designated port is interrupted.

Step S33: Count the traffic value of the multicast packet of the specified port.

In the foregoing optional embodiment, the terminal that determines whether the access device can perform the multicast packet according to the statistical result may be implemented by: determining whether the traffic value is less than a predetermined threshold, and when the determination result is yes, the access device The multicast device can be interrupted. If the judgment result is no, the access device cannot interrupt the multicast packet.

In this embodiment, a device for detecting the multicast function of the access device is further provided, and the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

2 is a structural block diagram of a device for detecting a multicast function of an access device according to an embodiment of the present invention. As shown in FIG. 2, the device includes: a receiving module 22, configured to receive a multicast protocol packet sent by an access device, The multicast protocol packet is used to invoke the specified port of the multicast server that can perform the loopback function. The statistic module 24 is coupled to the receiving module 22 and configured to collect the traffic value of the specified port multicast packet. The statistic module 24 is coupled to the statistic module 24, and is configured to determine, according to the statistical result, whether the access device can perform the multicast function.

Optionally, the multicast protocol packet includes a multicast join message and a multicast leave message.

FIG. 3 is a block diagram of an optional structure of a device for detecting a multicast function of an access device according to an embodiment of the present invention. As shown in FIG. 3, when the multicast protocol packet is a multicast join message, the statistics module 24 includes: The joining unit 32 is configured to: after receiving the join message of the specified port loopback, add the designated port to the preset multicast forwarding table; the forwarding unit 34 is coupled to the joining unit 32 and is set according to the preset group. The broadcast forwarding table forwards the multicast packet on the designated port. The first statistic unit 36 is coupled to the forwarding unit 34 and configured to collect the traffic value of the multicast packet of the specified port.

FIG. 4 is a block diagram of an optional structure of a device for detecting a multicast function of an access device according to an embodiment of the present invention. The multicast protocol message further includes: a multicast query message. As shown in FIG. 4, the statistics module 24 further includes The sending unit 42 is coupled to the forwarding unit 34 and configured to periodically send a multicast query message to the access device. The first receiving unit 44 is coupled to the sending unit 42 and configured to receive the access device to send a response in response to the query. The multicast packet of the packet is added to the device to ensure that the access device can forward multicast packets.

FIG. 5 is a block diagram 3 of an optional structure of a device for detecting a multicast function of an access device according to an embodiment of the present invention. As shown in FIG. 5, the determining module 26 includes: a first determining unit 52, configured to determine whether the traffic value is greater than a predetermined value. The threshold value, when the judgment result is yes, the access device can perform the forwarding of the multicast packet; if the judgment result is no, the access device cannot perform the forwarding of the multicast packet.

FIG. 6 is a block diagram of an optional structure of a device for detecting a multicast function of an access device according to an embodiment of the present invention. As shown in FIG. 6, when the multicast protocol packet is a multicast leave message, the statistics module 24 further includes The second receiving unit 62 is configured to receive the multicast leaving message sent by the access device, where the leaving message is used to indicate to clear the preset multicast forwarding table; the interrupting unit 64 is coupled to the second receiving unit 62. After the multicast forwarding table is emptied, the multicast packet forwarding of the specified port is interrupted. The second statistic unit 66 is coupled to the interrupting unit 64 and configured to collect the traffic value of the multicast packet of the specified port.

FIG. 7 is a block diagram 5 of an optional structure of a device for detecting a multicast function of an access device according to an embodiment of the present invention. As shown in FIG. 7, the determining module 26 further includes: a second determining unit 72, configured to determine whether the traffic value is smaller than If the result of the determination is YES, the access device can perform the interruption of the multicast packet. If the determination result is no, the access device cannot perform the interruption of the multicast packet.

In order to better illustrate the present invention, the following alternative embodiments are exemplified.

The purpose of this alternative embodiment is to provide a method for multicast remote acceptance. The acceptance function in the method of multicast remote acceptance includes a multicast protocol report: a join message, a leave message, a query test, a multicast forwarding table write hardware, and Whether the multicast service flow actually reaches the test of the user port. Its purpose is to determine whether the multicast service is normal and self-test judgment in engineering applications.

The method for remote multicast acceptance includes the following two aspects: 1) normal processing and forwarding of multicast protocol reports; 2) normal replication and interruption of multicast traffic.

For the above two aspects, the implementation method of the multicast remote acceptance test function includes the following parts:

Step S41: adding a message to be sent;

Step S42: A method for determining whether the multicast stream arrives at the user normally;

Step S43: determining the premise of the multicast service by using traffic monitoring;

Step S44: sending the leaving message;

Step S45: A method for determining whether the multicast stream is suspended;

Step S46: Query the sending of the message.

In order to better understand the optional embodiments of the present invention, the embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

FIG. 8 is a schematic diagram of a protocol packet and a multicast flow direction during a test according to an alternative embodiment of the present invention. The virtual arrow in FIG. 8 indicates the direction of the multicast media stream, and the solid arrow indicates the direction of the report, leave, and query packets. With reference to FIG. 8, the implementation method of the multicast remote acceptance test function of the optional example of the present invention includes:

Step S1: adding a message to be sent;

The multicast module constructs a report packet, and sends the packet to the bearer through the MUX packet sending interface, and the loopback interface is invoked to enable the loopback function. The loopback interface sends the packet to the client to be tested (may be a single Port, you can also test multiple ports. After calling this loopback interface, the port to be tested will report the link-up as a link-up, and the packet will be looped back at the client end to simulate the port receiving the client. The report packet is sent to check whether the line card is properly received. In order to prevent the incoming multicast stream from being looped back, the impact on the uplink device is successful. After the loopback function is successfully returned, the report packet is sent. If the loopback is successful, the loopback function should be turned off immediately.

If the multicast enable is enabled, the multicast module sends the report packet to the imgp module for processing. The multicast forwarding table is written to the chip. Pass through), then switch out to the configured source port.

After receiving the report of the NE, the multicast server directs the multicast stream to the NE to be tested. The network element is based on the multicast forwarding table (Virtual Local Area Network (VLAN), Media Access Control (Media). Access Control (MAC), port (PORT), is copied and switched to the corresponding user receiving port.

Step S2: determining whether the multicast stream reaches the user normally;

In the optional embodiment of the present invention, the multicast video stream monitoring may be used to determine whether the multicast stream is normal or not by using a video-monitor module. Because video-monitor can count a certain multicast at the entrance of the switch chip, for example, according to the number of packets per second of the multicast MAC or multicast channel IP stream, or the number of packets per second, bps After the multicast traffic monitoring or statistics function is enabled, the multicast stream will not be switched to the user side. Therefore, there is no risk of looping back the multicast stream after the loopback interface is enabled before sending the packet. The multicast traffic (pps/bps) is reported to the NMS through the Simple Network Management Protocol (SNMP).

It should be noted that if the flooding flow is to see if the chip has the function of dropping the unknown multicast stream, the 9806/F822 currently has this function. Otherwise, it will affect the statistics of the monitored multicast traffic.

After the report is successfully sent, the loopback interface is disabled. The port to be tested is in the link-down state. The statistics on the port, including multicast (protocol, media data), may not be counted. .

Step S3: determining the premise of the multicast service by using traffic monitoring;

Among them, the premise includes the following two aspects:

A. The network management first obtains the multicast configuration of the NE. For the configuration that does not match, the error is directly returned. The normal configuration of multicast is as follows: multicast vlan, source port (port-port), receive port (receive-port), and whether the group is correctly configured.

B. As the multicast channel for the simulation test, the user's on-demand situation of the channel will be cleared before the report is sent, and since the video-monitor terminates the multicast stream to be monitored on the switch chip, it will not send to the user port. It will affect the situation of other ports watching this multicast channel, so as a multicast channel for analog test, there can be no other users to watch.

Step S4: sending the leaving message;

The multicast module is configured to leave the leave message, and the packet is sent to the bearer through the multiplexing/multiplexing/multicast (MultipleXing, MUX) packet sending interface, and the bearer loopback interface is invoked to construct the packet. The packet is sent to the user to be tested. The packet is looped back on the client. The analog port receives the leave packet from the client. After the loopback function is successfully enabled, the loopback function is disabled immediately after the packet is successfully sent. If the multicast enable is enabled, it is sent to the multicast module through the MUX module for processing (clearing the multicast forwarding entry and stopping the multicast forwarding to the user interface). If the imgp is passed, the source port is exchanged to the configured source port. .

After the multicast server receives the leave packet from the NE, the multicast stream is interrupted.

Step S5: determining whether the multicast stream is suspended;

As with the method of joining the message, the data collected by the monitored multicast channel can be transmitted to the network management system.

Step S6: querying the sending of the message;

The query packet sent by the multicast server is sent to the multicast module after being exchanged by the switch chip. In this case, in response to the query report, the multicast stream is not interrupted, and the multicast module is similar to a proxy (proxy). In the case of the mode response, the report report of the query does not forward the query report to the user port. For the received general query or special query package, the simulated multicast group will respond accordingly.

The following is a description of the multicast protocol packets involved in this optional instance:

A: Obtain the source IP address in the IP header in the multicast protocol packet.

The source IP address in the IP header of the multicast protocol packet can be filled in. The IP address obtained by DHCP can be used as the source IP address of the imgp. You can also statically configure an IP address as the source IP address of the imgp. Optional on the network management software. The Multi-Service Access Platform (MAP) can use the existing Dynamic Host Configure Protocol (DHCP) module to obtain the source IP address.

B: The source MAC address in the Ethernet header is obtained in the multicast protocol packet;

The source MAC address in the Ethernet header of the multicast protocol packet can be used as the MAC address in the MAC pool, or a randomly generated MAC address, or an inband MAC address.

Through the remote management analog multicast method of the foregoing optional embodiment, the efficiency of the access device acceptance and fault resolution is effectively improved, and all operations and result displays are completed remotely, which not only helps improve work efficiency, but also helps Assist engineers in the acceptance of related functions such as multicast.

The above are only the preferred embodiments of the present invention, and are not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

According to the foregoing technical solution provided by the embodiment of the present invention, the multicast server receives the multicast protocol packet sent by the access device, where the multicast protocol packet is used to invoke a designated port in the multicast server that can perform the loopback function; This section describes how to collect the statistics of the multicast packets on the specified port. If the access device can perform the multicast function, you need to check whether the access device can perform the multicast function. The problem of personal inspection at the access device improves the efficiency of checking the access device and saves expenses.

Claims (14)

A method for detecting a multicast function of an access device includes: The multicast server receives the multicast protocol packet sent by the access device, where the multicast protocol packet is used to invoke a designated port in the multicast server that can perform the loopback function; Counts the traffic value of the specified port multicast packet; It is judged according to the statistical result whether the access device is capable of performing a multicast function. The method according to claim 1, wherein the multicast protocol message comprises a multicast join message and a multicast leave message. The method according to claim 2, wherein, when the multicast protocol packet is a packet for the multicast join, the statistics of the traffic value of the specified port multicast packet includes: After receiving the join message of the specified port, the multicast server adds the specified port to the preset multicast forwarding table. And forwarding the multicast packet on the designated port according to the preset multicast forwarding table; Counts the traffic value of the multicast packet on the specified port. The method of claim 3, wherein the multicast protocol message further comprises: a multicast query message, before the statistics of the traffic value of the multicast packet on the specified port, the method further includes: The multicast server periodically sends a multicast query message to the access device; The multicast server receives the multicast join message sent by the access device in response to the query message, to determine that the access device can forward the multicast packet normally. The method according to claim 1, wherein determining whether the access device is capable of performing a multicast function according to the statistical result comprises: Determining whether the traffic value is greater than a predetermined threshold, and when the determination result is yes, the access device can perform forwarding of the multicast packet; When the judgment result is no, the access device cannot perform forwarding of the multicast packet. The method of claim 2, wherein, when the multicast protocol packet is the multicast leaving packet, the statistics of the traffic value of the specified port multicast packet includes: The multicast server receives the multicast leave message sent by the access device, where the leave message is used to indicate to clear the preset multicast forwarding table. After the multicast forwarding table is emptied, the forwarding of the multicast packet of the designated port is interrupted; Counts the traffic value of the multicast packet of the specified port. The method according to claim 6, wherein determining whether the access device is capable of performing a multicast function according to the statistical result comprises: Determining whether the traffic value is less than a predetermined threshold, and when the determination result is yes, the access device can perform the interruption of the multicast packet; When the judgment result is no, the access device cannot perform the interruption of the multicast message. A device for detecting a multicast function of an access device, which is applied to a multicast server, and includes: a receiving module, configured to receive a multicast protocol packet sent by the access device, where the multicast protocol packet is used to invoke a designated port in the multicast server that can perform a loopback function; The statistics module is configured to collect the traffic value of the multicast packet of the specified port. The determining module is configured to determine, according to the statistical result, whether the access device is capable of performing a multicast function. The device according to claim 8, wherein the multicast protocol message comprises a multicast join message and a multicast leave message. The device according to claim 9, wherein, when the multicast protocol message is the multicast join message, the statistics module further includes: After the joining unit is configured to receive the join message of the specified port, the specified port is added to the preset multicast forwarding table. The forwarding unit is configured to forward the multicast packet on the designated port according to the preset multicast forwarding table; The first statistic unit is configured to collect the traffic value of the multicast packet on the specified port. The device of claim 10, wherein the multicast protocol message further comprises: a multicast query message, the statistics module further comprising: a sending unit, configured to periodically send a multicast query message to the access device; The first receiving unit is configured to receive, by the access device, a multicast join message that is sent in response to the query message, to determine that the access device can forward the multicast packet normally. The apparatus of claim 8 wherein said determining module comprises: The first determining unit is configured to determine whether the traffic value is greater than a predetermined threshold, wherein, when the determination result is yes, the access device can perform forwarding of the multicast packet; when the determination result is negative, the connecting The inbound device cannot forward multicast packets. The apparatus according to claim 9, wherein when the multicast protocol message is the multicast leaving message, the statistics module includes: a second receiving unit, configured to receive a multicast leaving message sent by the access device, where the leaving message is used to indicate to clear a preset multicast forwarding table; The interrupting unit is configured to interrupt the forwarding of the multicast packet of the designated port after the multicast forwarding table is emptied; The second statistic unit is configured to collect the traffic value of the multicast packet of the specified port. The apparatus of claim 13, wherein the determining module comprises: The second determining unit is configured to determine whether the traffic value is less than a predetermined threshold, wherein, when the determination result is yes, the access device can perform the interruption of the multicast packet; when the determination result is no, the The access device cannot perform the interruption of the multicast packet.

Images