WO2018014710A1 - 一种未知组播报文的处理方法和装置 - Google Patents

一种未知组播报文的处理方法和装置 Download PDF

Info

Publication number
WO2018014710A1
WO2018014710A1 PCT/CN2017/090946 CN2017090946W WO2018014710A1 WO 2018014710 A1 WO2018014710 A1 WO 2018014710A1 CN 2017090946 W CN2017090946 W CN 2017090946W WO 2018014710 A1 WO2018014710 A1 WO 2018014710A1
Authority
WO
WIPO (PCT)
Prior art keywords
unknown multicast
multicast stream
record
unknown
database
Prior art date
Application number
PCT/CN2017/090946
Other languages
English (en)
French (fr)
Inventor
李大鹏
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018014710A1 publication Critical patent/WO2018014710A1/zh

Links

Images

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for processing unknown multicast packets.
  • a Central Processing Unit runs a multicast-related routing protocol, and routes the forwarding to an Application Specific Integrated Circuit (ASIC).
  • ASIC Application Specific Integrated Circuit
  • the chip searches for internal entries, determines the multicast replication exit, and forwards the packet to each outbound interface.
  • the ASIC chip generally provides two operations to choose from, one is to discard directly, and the other is to send to the CPU.
  • the packets are sent to the CPU for analysis by the multicast routing protocol stack. Before waiting for the analysis result, a large number of multicast packets are sent, which causes a heavy burden on the CPU.
  • the traditional method is to perform the forwarding of the multicast data stream without waiting for the special processing.
  • the multicast data stream is sent to the CPU and the formal forwarding entry is sent. In this way, a large number of unknown multicast packets are sent to the protocol stack before the official forwarding entry is sent. This may cause the CPU usage to be too high and affect other normal services.
  • the purpose of the embodiments of the present invention is to provide a method for processing an unknown multicast packet, which solves the problem that a large number of unknown multicast packets are sent to the protocol stack, causing the CPU usage to be too high and affecting other normal services.
  • the embodiment of the present invention provides a method for processing an unknown multicast packet, including:
  • the rate limit table is configured to send the interface to the ASIC, and the rate limit table is used to control the unknown multicast packet. Continue to send.
  • the embodiment of the present invention further provides a computer storage medium, where the computer storage medium stores one or more programs executable by a computer, and when the one or more programs are executed by the computer, the computer is executed as described above.
  • the embodiment of the present invention receives the unknown multicast packet sent by the ASIC; determines whether the unknown multicast stream where the unknown multicast packet is located exists in the unknown multicast stream database; if not, sends the packet to the protocol stack. And the unknown multicast packet is added to the unknown multicast stream database, and the unknown multicast stream record is added to the unknown multicast stream database, and the dedicated multicast stream record is added to the dedicated multicast stream database.
  • the rate limit table of the integrated circuit is configured to control that the unknown multicast packet is not sent continuously. This prevents a large number of packets from being sent and affects the performance of the CPU and other normal business modules.
  • FIG. 1 is a schematic flowchart of a method for processing an unknown multicast packet according to an embodiment of the present disclosure
  • FIG. 2 is a schematic flowchart of another method for processing an unknown multicast packet according to an embodiment of the present disclosure
  • FIG. 3 is an example of a method for processing an unknown multicast packet according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of another apparatus for processing unknown multicast packets according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of another apparatus for processing unknown multicast packets according to an embodiment of the present invention.
  • FIG. 7 is another apparatus for processing an unknown multicast packet according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of another apparatus for processing unknown multicast packets according to an embodiment of the present invention.
  • an embodiment of the present invention provides a method for processing an unknown multicast packet, including the following steps:
  • Step S101 Receive an unknown multicast message sent by the application specific integrated circuit.
  • the unknown multicast packet may be the multicast packet that is received by the ASIC chip when the MPLS chip receives the multicast packet and searches for the hardware forwarding entry.
  • the ASIC chip After receiving the unknown multicast packet, the ASIC chip sends the unknown multicast packet to the chip driver, and is received by the chip driver.
  • Step S102 Determine whether there is a record in the unknown multicast stream database of the unknown multicast stream where the unknown multicast message is located.
  • the foregoing unknown multicast stream database may be pre-established, and the unknown multicast stream database may be used to store the unknown multicast stream record.
  • the foregoing determining whether the unknown multicast stream in which the unknown multicast packet is located has a record in the unknown multicast stream database may be querying the unknown multicast stream record in the unknown multicast stream database, and determining that the unknown multicast stream is in the foregoing Whether there is a record in the unknown multicast stream database.
  • the unknown multicast packet may be the unknown multicast packet received in step S101.
  • Step S103 If the record does not exist, send the unknown multicast packet to the protocol stack, and add the unknown multicast stream record to the unknown multicast stream database.
  • the chip driver sends the unknown multicast packet to the protocol stack, and adds the unknown multicast stream record to the unknown multicast stream database, where the record may be It is recorded in a variety of ways, which is not limited in this embodiment.
  • the unknown multicast data stream is not queried in the unknown multicast stream database, and the driver chip sends the unknown multicast packet to the protocol stack, and adds the unknown multicast stream record to the unknown multicast stream database. And add a send tag to the record.
  • Step S104 After the unknown multicast stream record is added to the unknown multicast stream database, send a rate limit table with an interface to the ASIC, and the rate limit table is used to control the unknown multicast. The message is no longer sent.
  • the speed limit table may be a forwarding entry that is sent by the chip driver to the ASIC, and the speed limit table may be a forwarding entry that is empty, and is used to control that the unknown multicast packet is not sent.
  • the chip driver sends a speed limit table to the ASIC, and the outbound interface of the speed limit table is empty, and can be used to control that the unknown multicast message does not continue to be sent. This is only an example, and the embodiment does not limit this.
  • the chip driver After the unknown multicast stream record is added to the unknown multicast stream database, the chip driver sends the rate limit entry to the ASIC to control that the unknown multicast message is not sent.
  • the above method can be applied to a switch.
  • the embodiment of the present invention receives an unknown multicast packet sent by the ASIC; and determines whether the unknown multicast stream where the unknown multicast packet is located has a record in the unknown multicast stream database; if the record does not exist, The protocol stack sends the unknown multicast packet, and adds the unknown multicast stream record to the unknown multicast stream database; after adding the unknown multicast stream record to the unknown multicast stream database, The ASIC sends an empty rate limit table to control that the unknown multicast message does not continue to be sent. This prevents a large number of packets from being sent and affects the performance of the CPU and other normal business modules.
  • FIG. 2 is a method for processing an unknown multicast packet according to an embodiment of the present invention, including:
  • Step S201 Receive an unknown multicast message sent by the application specific integrated circuit.
  • Step S202 Determine whether there is a record in the unknown multicast stream database of the unknown multicast stream where the unknown multicast message is located.
  • Step S203 If the record does not exist, send the unknown multicast packet to the protocol stack, and add the unknown multicast stream record in the unknown multicast stream database, where the unknown multicast stream record is recorded.
  • the uploading flag is added, and a count is created for the unknown multicast stream record, where the sending flag is used to record that the unknown multicast packet has been sent.
  • the foregoing sending flag is used to record that the unknown multicast packet has been sent to the protocol stack, and the foregoing sending label may be marked in multiple forms, which is not limited in this embodiment. After the above-mentioned unknown multicast packet is added with the sent tag, a count is created for the record.
  • adding the foregoing sending flag to the unknown multicast stream record and creating a count for the unknown multicast stream record can better count the unknown multicast stream record.
  • Step S204 After the unknown multicast stream record is added to the unknown multicast stream database, send a rate limit table with an empty interface to the ASIC, and the rate limit table is used to control the unknown multicast. The message is no longer sent.
  • the foregoing embodiment may further include the following steps:
  • Step S205 After receiving the unknown multicast packet, the protocol stack receives the official forwarding entry sent by the protocol stack, and determines whether the unknown multicast stream exists in the unknown multicast stream database. recording.
  • the protocol stack After receiving the unknown multicast packet sent by the chip driver, the protocol stack sends a formal forwarding entry to the chip driver, where the formal forwarding entry may be a forwarding table sent by the protocol stack after several timing cycles. Item, ending the loop process of the several timing cycles.
  • the chip driver receives the official forwarding entry, queries the unknown multicast stream database, and determines whether the unknown multicast stream record exists in the unknown multicast stream database.
  • Step S206 If the unknown multicast stream record does not exist, send the formal forwarding entry to the application specific integrated circuit.
  • the forwarding entry sent by the protocol stack ends the cyclic process of the several timing cycles.
  • Step S207 If the unknown multicast stream record exists, delete the unknown multicast stream record in the unknown multicast stream database, and send the official forwarding entry to the application specific integrated circuit.
  • the unknown multicast stream record is deleted, deleting the unknown multicast stream record in the unknown multicast stream database, deleting the unknown multicast stream record, and sending the official forwarding entry to the ASIC chip to cover the ASIC chip.
  • the speed limit entry delivered before the completion of the conversion of the speed limit table to the official forwarding table, the ASIC chip is forwarded according to the official forwarding table.
  • the transmission efficiency of the formal forwarding table can be improved, and the packets are prevented from being sent in a large amount, which affects the performance of the CPU.
  • the foregoing embodiment may further include the following steps:
  • the unknown multicast stream record exists in the unknown multicast stream database, determining whether the uplink multicast packet exists in the unknown multicast stream record;
  • the unknown multicast packet is sent to the protocol stack, and the sending flag is added to the unknown multicast stream where the unknown multicast packet is located.
  • the uploading flag is used to record that the unknown multicast packet has been sent.
  • Determining whether the above-mentioned uploading flag exists in the unknown multicast stream record If the sending flag is sent, the unknown multicast packet is sent, and the unknown multicast packet is discarded; if the sending flag is not present, The above-mentioned unknown multicast packet has been sent to the protocol stack, and the above-mentioned uplink packet is added to the unknown multicast stream where the unknown multicast packet is located. The unknown multicast packet has been sent.
  • the unknown multicast packet can be separately processed in a targeted manner to improve the efficiency of processing the unknown multicast packet.
  • the foregoing embodiment may further include the following steps:
  • the protocol stack sends the unknown multicast packet again before sending the formal forwarding entry to the ASIC;
  • the unknown multicast stream record is deleted, and the forwarding entry corresponding to the unknown multicast stream record is deleted.
  • the timer may start from receiving the unknown multicast packet, and when the timer reaches the preset time, the chip driver traverses the unknown multicast stream database record, and after finding the record, the current traversal is performed.
  • a count of 1 is added to indicate that the record has experienced a timing period. For example, the count of records currently traversed is 5, and the count is 6 after the count of records currently traversed is incremented by one.
  • the foregoing threshold value may be a preset threshold value, and the foregoing threshold value may be received in advance by the user, or may be generated in advance and stored in the switch, or the switch is set at the time of leaving the factory, which is not limited in this embodiment.
  • the chip driver deletes the uplink sending flag in the unknown multicast record, updates the record to the unknown multicast stream database, and sends a speed limit table whose interface is a CPU to the ASIC chip.
  • the rate limit table is used to restore the unknown multicast packets that need to be sent to the CPU after a timing period.
  • Chip resources are released after a period of time.
  • the unknown multicast stream is periodically sent to the CPU, and the resource of the driver chip is controlled to be used, thereby preventing a large number of packets from being sent and affecting the performance of the CPU and other normal service modules.
  • FIG. 3 is an example of a method for processing an unknown multicast packet according to an embodiment of the present invention.
  • the chip driver when the chip driver receives the unknown multicast packet, the chip driver extracts the unknown multicast packet information to find out whether the unknown multicast packet exists in the unknown multicast stream database.
  • the multicast stream record if not present, the chip driver sends the unknown multicast packet to the protocol stack, and adds the unknown multicast stream record of the unknown multicast packet to the unknown multicast stream database. And adding a sent flag to the record, and creating a count of the record, the mark is used to record that the unknown multicast message has been sent.
  • the chip driver sends a speed limit table with an empty interface to the ASIC chip, and the above unknown multicast stream is restricted from being sent.
  • the unknown multicast stream record exists in the unknown multicast stream database, the unknown multicast stream record is determined to have the uplink sending flag, and if the sending flag is present, the unknown group is The broadcast message is directly discarded. If the above-mentioned upload flag does not exist, it indicates that the unknown multicast stream has experienced a timing period and should be sent to the protocol stack, and the unknown multicast packet is sent to the protocol stack. And adding an upload flag to the unknown multicast stream record, and updating to the unknown multicast stream database.
  • the chip driver sends a speed limit table with an empty interface to the ASIC chip, and the above unknown multicast stream is restricted from being sent.
  • the driver traverses the unknown multicast stream database record, and increments the count of the traversed record by 1, indicating that the record has undergone a timing period. Determining whether the count of the record is greater than a preset threshold, if not greater than the preset threshold, the chip driver deletes the upload flag of the unknown multicast stream record, and updates the record to the unknown multicast database, and The rate limit table is sent to the CPU and the unknown multicast packets are sent to the CPU.
  • the unknown multicast stream record When the count of the unknown multicast stream record is greater than the preset threshold, the unknown multicast stream record is directly deleted, and the forwarding entry corresponding to the unknown multicast stream record is deleted to control the chip occupied by the useless part. Resources are released after a certain amount of time.
  • the protocol stack After receiving the unknown multicast packet, the protocol stack sends a formal forwarding entry to the chip driver, and the chip driver receives the official forwarding entry to find out whether the unknown multicast packet exists in the unknown multicast stream database.
  • Multicast stream record if the above unknown multicast stream is not found Recording, the chip driver sends the official forwarding entry to the ASIC chip; if the chip driver finds the unknown multicast stream record in the unknown multicast stream database, deleting the unknown multicast stream record, and then deleting the unknown multicast stream record The chip sends a formal forwarding entry.
  • an ASIC chip sends an unknown multicast packet to the CPU.
  • the subsequent packet is discarded by the air interface rate limit table until the formal forwarding entry is sent by the protocol stack. This prevents a large number of packets from being sent and affects the performance of the CPU and other normal business modules.
  • FIG. 4 is a device for processing an unknown multicast packet according to an embodiment of the present invention.
  • the device may be applied to a switch.
  • the unknown multicast packet processing device 400 includes: a receiving module 401.
  • the receiving module 401 is configured to receive an unknown multicast packet sent by the application specific integrated circuit.
  • the first determining module 402 is configured to determine whether the unknown multicast stream where the unknown multicast packet is located has a record in the unknown multicast stream database.
  • the first sending module 403 is configured to: if the record does not exist, send the unknown multicast packet to the protocol stack, and add the unknown multicast stream record to the unknown multicast stream database;
  • a second sending module 404 configured to: after adding the unknown multicast stream record in the unknown multicast stream database, send a speed limit table with an empty interface to the ASIC, where the speed limit table is used for controlling The unknown multicast packet is no longer sent.
  • the first determining module 402 block includes:
  • the adding unit 4021 is configured to add the unknown multicast stream record in the unknown multicast stream database, add a sending flag to the unknown multicast stream record, and create a count for the unknown multicast stream record.
  • the sending flag is used to record that the unknown multicast packet has been sent.
  • the apparatus further includes:
  • the second judging module 405 is configured to determine, if the unknown multicast stream record exists in the unknown multicast stream database, whether the uplink multicast packet exists in the unknown multicast stream record;
  • the discarding module 406 is configured to discard the unknown multicast packet if the sending flag is present;
  • the sending module 407 is configured to: if the uplink sending flag does not exist, send the unknown multicast packet The method is sent to the protocol stack, and the sending flag is added to the unknown multicast stream where the unknown multicast packet is located.
  • the apparatus further includes:
  • the timing module 408 is configured to set a timer, start timing when the unknown multicast packet is received, and traverse the unknown multicast stream database record when the timer time reaches a preset time, and traverse the current traversal The count of records is increased by 1;
  • the first deleting module 409 is configured to: if the counting is not greater than a preset threshold, delete the sending flag in the unknown multicast stream record, and send a forwarding entry to the application specific integrated circuit, where The forwarding entry is used to send the unknown multicast packet again before the protocol stack sends the formal forwarding entry to the ASIC;
  • the second deleting module 410 is configured to delete the unknown multicast stream record and delete the forwarding entry corresponding to the unknown multicast stream record if the count is greater than the preset threshold.
  • the apparatus further includes:
  • the third determining module 411 is configured to: after receiving the unknown multicast packet, the protocol stack receives the official forwarding entry sent by the protocol stack, and determines whether the unknown multicast stream database exists in the unknown multicast stream database. Describe the unknown multicast stream record;
  • the third sending module 412 is configured to send the formal forwarding entry to the application specific integrated circuit if the unknown multicast stream record does not exist;
  • a third deleting module 413 configured to delete the unknown multicast stream record in the unknown multicast stream database if the unknown multicast stream record exists, and send the formal forwarding table to the ASIC item.
  • the unknown multicast packet processing apparatus 400 can be applied to a switch.
  • the unknown multicast packet processing apparatus 400 can implement the various processes in the embodiment of the embodiment of FIG. 1 to FIG. 2, and details are not described herein.
  • the unknown multicast packet processing apparatus 400 can prevent a large number of packets from being sent and affect the performance of the CPU and other normal service modules.
  • the rate limit table is configured to send the interface to the ASIC, and the rate limit table is used to control the unknown multicast packet. Continue to send.
  • the adding the unknown multicast stream record in the unknown multicast stream database includes:
  • Adding the unknown multicast stream record to the unknown multicast stream database adding a sending flag to the unknown multicast stream record, and creating a count for the unknown multicast stream record, where the sending The flag is used to record that the unknown multicast packet has been sent.
  • the method further includes:
  • the unknown multicast stream record exists in the unknown multicast stream database, determining whether the uplink multicast packet exists in the unknown multicast stream record;
  • the unknown multicast packet is sent to the protocol stack, and the sending flag is added to the unknown multicast stream where the unknown multicast packet is located.
  • the method further includes:
  • the unknown multicast stream record is deleted, and the forwarding entry corresponding to the unknown multicast stream record is deleted.
  • the method further includes:
  • the protocol stack After receiving the unknown multicast packet, the protocol stack receives the official forwarding entry sent by the protocol stack, and determines whether the unknown multicast stream record exists in the unknown multicast stream database.
  • the storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the foregoing technical solution provided by the embodiment of the present invention can be applied to the process of processing an unknown multicast packet by receiving an unknown multicast packet sent by the application specific integrated circuit, and determining the unknown multicast stream where the unknown multicast packet is located. Whether there is a record in the unknown multicast stream database; if not, sending the unknown multicast message to the protocol stack, and adding the unknown multicast stream record to the unknown multicast stream database; After the unknown multicast stream record is added to the unknown multicast stream database, the rate limit table with an empty interface is sent to the ASIC to control that the unknown multicast packet is not sent. This prevents a large number of packets from being sent and affects the performance of the CPU and other normal business modules.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明提供一种未知组播报文的处理方法和装置,该方法可包括:接收专用集成电路发送的未知组播报文;判断所述未知组播报文所在的未知组播流在未知组播流数据库中是否存在记录;若不存在所述记录,则向协议栈发送所述未知组播报文,并在所述未知组播流数据库中添加所述未知组播流记录;在所述未知组播流数据库中添加所述未知组播流记录后,向所述专用集成电路发送接口为空的限速表,所述限速表用于控制所述未知组播报文不再继续上送。本发明实施例可以解决由于大量未知组播报文上送协议栈,导致CPU占用率过高,影响其他正常业务的问题。

Description

一种未知组播报文的处理方法和装置 技术领域
本发明涉及通信技术领域,特别涉及一种未知组播报文的处理方法和装置。
背景技术
目前,对于组播,中央处理器(Central Processing Unit,简称CPU)运行组播相关路由协议,并将转发路由给专用集成电路(Application Specific Integrated Circuit,ASIC芯片),当组播报文进入ASIC芯片时,芯片查找内部表项,确定组播复制出口,并向各个出接口转发报文。当接收的报文没有找到内部表项时,ASIC芯片一般提供两个操作可供选择,一是直接丢弃,二是上送CPU。一般情况下,需要将报文上送CPU供组播路由协议栈分析,在等待协议分析结果前,会有大量组播报文上送,给CPU造成较大负担。
传统的方法是不做特殊处理,组播数据流持续上送,等待CPU协议分析完成下发正式的转发表项,这时未知组播已经可以查到转发表项,根据表项进行转发。这样,在正式转发表项下发前会有大量的未知组播报文上送协议栈,容易导致CPU占用率过高,影响其他正常业务。
发明内容
本发明实施例的目的在于提供一种未知组播报文的处理方法,解决了大量未知组播报文上送协议栈,导致CPU占用率过高,影响其他正常业务的问题。
为了达到上述目的,本发明实施例提供一种未知组播报文的处理方法,包括:
接收专用集成电路发送的未知组播报文;
判断所述未知组播报文所在的未知组播流在未知组播流数据库中是否存在记录;
若不存在所述记录,则向协议栈发送所述未知组播报文,并在所述未知组播流数据库中添加所述未知组播流记录;
在所述未知组播流数据库中添加所述未知组播流记录后,向所述专用集成电路发送接口为空的限速表,所述限速表用于控制所述未知组播报文不再继续上送。
本发明实施例还提供一种计算机存储介质,所述计算机存储介质中存储有计算机可执行的一个或多个程序,所述一个或多个程序被所述计算机执行时使所述计算机执行如上述提供的一种未知组播报文的处理方法。
上述技术方案中的一个技术方案具有如下优点或有益效果:
本发明实施例接收专用集成电路发送的未知组播报文;判断所述未知组播报文所在的未知组播流在未知组播流数据库中是否存在记录;若不存在,则向协议栈发送所述未知组播报文,并在所述未知组播流数据库中添加所述未知组播流记录;在所述未知组播流数据库中添加所述未知组播流记录后,向所述专用集成电路发送接口为空的限速表,以控制所述未知组播报文不再继续上送。这样能够防止报文大量上送而影响CPU性能及其他正常业务模块的运行。
附图说明
图1为本发明实施例提供的一种未知组播报文的处理方法流程示意图;
图2为本发明实施例提供的另一种未知组播报文的处理方法流程示意图;
图3为本发明实施例提供的一种未知组播报文的处理方法举例;
图4为本发明实施例提供的一种未知组播报文的处理装置;
图5为本发明实施例提供的另一种未知组播报文的处理装置;
图6为本发明实施例提供的另一种未知组播报文的处理装置;
图7为本发明实施例提供的另一种未知组播报文的处理装置;
图8为本发明实施例提供的另一种未知组播报文的处理装置。
具体实施方式
为使本发明要解决的技术问题、技术方案和优点更加清楚,下面将结合附图及具体实施例进行详细描述。
如图1所示,本发明实施例提供一种未知组播报文的处理方法,包括以下步骤:
步骤S101、接收专用集成电路发送的未知组播报文。
上述未知组播报文可以是ASIC芯片接收上述组播报文并查找硬件转发表项,未匹配到转发表项时所述的组播报文。
上述ASIC芯片接收上述未知组播报文后,将上述未知组播报文发送至芯片驱动,由上述芯片驱动接收。
步骤S102、判断所述未知组播报文所在的未知组播流在未知组播流数据库中是否存在记录。
上述未知组播流数据库可以是预先建立的,上述未知组播流数据库可以用于存放上述未知组播流记录。上述判断上述未知组播报文所在的未知组播流在未知组播流数据库中是否存在记录可以是查询上述未知组播流数据库中的上述未知组播流记录,判断上述未知组播流在上述未知组播流数据库中是否存在记录。其中,上述未知组播报文可以是步骤S101中接收到的上述未知组播报文。
步骤S103、若不存在所述记录,则向协议栈发送所述未知组播报文,并在所述未知组播流数据库中添加所述未知组播流记录。
若上述未知组播流数据库中不存在上述未知组播流记录,芯片驱动向协议栈发送上述未知组播报文,并在上述未知组播流数据库中添加上述未知组播流记录,上述记录可以是采用多种方式来记录,本实施例对此不作限定。
例如,在上述未知组播流数据库中没有查询到上述未知组播数据流,驱动芯片向上述协议栈发送上述未知组播报文,并在上述未知组播流数据库中添加上述未知组播流记录,并在该记录中添加上送标记。
步骤S104、在所述未知组播流数据库中添加所述未知组播流记录后,向所述专用集成电路发送接口为空的限速表,所述限速表用于控制所述未知组播报文不再继续上送。
上述限速表可以是上述芯片驱动向专用集成电路发送的的转发表项,上述限速表可以是出接口为空的转发表项,用于控制上述未知组播报文不再继续上送。例如,芯片驱动向专用集成电路发送限速表,上述限速表的出接口为空,可以用于控制上述未知组播报文不再继续上送。此处仅是举例,本实施例对此不作限定。
在所述未知组播流数据库中添加所述未知组播流记录后,上述芯片驱动向上述专用集成电路发送上述限速表项,控制上述未知组播报文不再继续上送。
本实施例中,上述方法可以应用于交换机。
本发明实施例接收专用集成电路发送的未知组播报文;判断所述未知组播报文所在的未知组播流在未知组播流数据库中是否存在记录;若不存在所述记录,则向协议栈发送所述未知组播报文,并在所述未知组播流数据库中添加所述未知组播流记录;在所述未知组播流数据库中添加所述未知组播流记录后,向所述专用集成电路发送接口为空的限速表,以控制所述未知组播报文不再继续上送。这样能够防止报文大量上送而影响CPU性能及其他正常业务模块的运行。
如图2所示,图2为本发明实施例提供的另一种未知组播报文的处理方法,包括:
步骤S201、接收专用集成电路发送的未知组播报文。
步骤S202、判断所述未知组播报文所在的未知组播流在未知组播流数据库中是否存在记录。
步骤S203、若不存在所述记录,则向协议栈发送所述未知组播报文,并在所述未知组播流数据库中添加所述未知组播流记录,在所述未知组播流记录中添加上送标记,并为所述未知组播流记录创建计数,其中,所述上送标记用于记录所述未知组播报文已经上送。
上述上送标记用于记录上述未知组播报文已经上送至上述协议栈,上述上送标记可以是以多种形式进行标记,本实施例对此不作限定。在上述未知组播报文添加已上送标记后,为该条记录创建计数。
这样,在上述未知组播流记录中添加上述上送标记,并为上述未知组播流记录创建计数,可以更好地统计上述未知组播流记录。
步骤S204、在所述未知组播流数据库中添加所述未知组播流记录后,向所述专用集成电路发送接口为空的限速表,所述限速表用于控制所述未知组播报文不再继续上送。
可选的,上述实施例还可以包含以下步骤:
步骤S205、在所述协议栈接收所述未知组播报文后,接收所述协议栈发送的所述正式转发表项,判断在所述未知组播流数据库中是否存在所述未知组播流记录。
上述协议栈接收芯片驱动上送的上述未知组播报文后,向芯片驱动发送正式转发表项,上述正式转发表项可以是用于在若干个上述定时周期后,由协议栈发送的转发表项,结束该若干个定时周期的循环过程。上述芯片驱动接收上述正式转发表项,查询上述未知组播流数据库,判断在上述未知组播流数据库中是否存在上述未知组播流记录。
步骤S206、若不存在所述未知组播流记录,则向所述专用集成电路发送所述正式转发表项。
判断上述未知组播流数据库中是否存在上述未知组播流记录,若不存在上述未知组播流记录,则向上述ASIC芯片发送上述正式转发表项,上述正式转发表项可以是在若干个上述定时周期后,由协议栈发送的转发表项,结束该若干个定时周期的循环过程。
步骤S207、若存在所述未知组播流记录,则删除所述未知组播流数据库中的所述未知组播流记录,并向所述专用集成电路发送所述正式转发表项。
若存在上述未知组播流记录,则删除上述未知组播流数据库中的上述未知组播流记录,则删除上述未知组播流记录,向上述ASIC芯片发送上述正式转发表项,覆盖上述ASIC芯片里的之前下发的限速表项,完成限速表到正式转发表的转换,上述ASIC芯片按照正式转发表进行转发。
本实施例能够提高正式转发表的发送效率,防止报文大量上送,影响CPU性能。
可选的,上述实施例还可以包含以下步骤:
若所述未知组播流数据库存在所述未知组播流记录,则判断所述未知组播流记录是否存在所述上送标记;
若存在所述上送标记,则丢弃所述未知组播报文;
若不存在所述上送标记,则将所述未知组播报文上送至所述协议栈,并为所述未知组播报文所在的未知组播流添加所述上送标记。
判断上述未知组播报文所在的未知组播流在上述未知组播流数据库中是否存在记录,若存在上述记录,则判断上述未知组播流记录是否存在上述上送标记。上送标记用于记录所述未知组播报文已经上送。
判断上述未知组播流记录是否存在上述上送标记,若存在上述上送标记,则说明上述未知组播报文已经上送,则丢弃上述未知组播报文;若不存在上述上送标记,则说明上述未知组播流已经超过了一个定时周期,将上述未知组播报文继续上送至协议栈,并为上述未知组播报文所在的未知组播流添加上述上送标记,记录上述未知组播报文已经上送。
本实施例通过判断上述未知组播流是否已经上送,可以对上述未知组播报文有针对性地分别进行处理,提高处理上述未知组播报文的效率。
可选的,上述实施例还可以包含以下步骤:
设置计时器,在所述接收未知组播报文的同时开始计时,当计时器时 间到达预先设定的时间时,遍历所述未知组播流数据库记录,并将当前遍历的记录的计数加1;
若所述计数不大于预设的阈值,则删除所述未知组播流记录中的所述上送标记,并向所述专用集成电路发送转发表项,所述转发表项用于在所述协议栈向所述专用集成电路发送正式转发表项前再次上送所述未知组播报文;
若所述计数大于所述预设的阈值,则删除该未知组播流记录,并删除该未知组播流记录对应的所述转发表项。
其中,上述计时器可以是从上述接收未知组播报文开始计时,当计时器到达上述预先设定的时间时,芯片驱动遍历上述未知组播流数据库记录,查找到记录后,将当前遍历到的记录的计数加1,表示该条记录经历了一个计时周期。例如,当前遍历到的记录的计数为5,在当前遍历到的记录的计数加1后计数为6。
其中,上述阈值可以是预先设定的阈值,上述阈值可以是预先接收用户输入的,或者预先生成并存储于交换机上的或者交换机出厂时设置的等等,本实施例对此不作限定。
若上述计数不大于预设的阈值,上述芯片驱动删除上述未知组播记录中的上述上送标记,将记录更新至上述未知组播流数据库,并向ASIC芯片发送接口为CPU的限速表,该限速表用于使需要上送至CPU的未知组播报文在一个定时周期后,恢复上送。
若上述计数大于上述预设的阈值,则删除该条未知组播流在数据库中的记录,并删除该条未知组播流记录对应的上述转发表项,这样,可以使一些无用表项占用的芯片资源在一段时间后得到释放。
本实施例通过设置计时器,控制上述未知组播流周期性地上送至上述CPU,并控制上述驱动芯片资源合理利用,能够防止报文大量上送而影响CPU性能及其他正常业务模块的运行。
为方便说明上述实施例,对上述实施例进行举例说明。
图3为本发明实施例的一种未知组播报文的处理方法的举例。如图3所示,在芯片驱动接收上述未知组播报文时开始计时,芯片驱动提取上述未知组播报文信息,查找在未知组播流数据库中是否存在上述未知组播报文所在的未知组播流记录,如果不存在,则上述芯片驱动将上述未知组播报文上送给协议栈,并在上述未知组播流数据库中添加上述未知组播报文所在的未知组播流记录,并为该记录添加已上送标记,创建该记录的计数,上述标记用于记录上述未知组播报文已上送。芯片驱动向ASIC芯片发送出接口为空的限速表,限制上述未知组播流继续上送。
若上述未知组播流数据库中存在上述未知组播报文所在的未知组播流记录,则判断上述未知组播流记录是否存在上述上送标记,若存在上述上送标记,则将该未知组播报文直接丢弃,若不存在上述上送标记,则说明该未知组播流已经经历了一个定时周期,应该继续上送至协议栈,则将上述未知组播报文上送至协议栈,并为该未知组播流记录添加上送标记,更新到上述未知组播流数据库。芯片驱动向ASIC芯片发送出接口为空的限速表,限制上述未知组播流继续上送。
当上述计时器时间到了预先设定的时间时,驱动遍历上述未知组播流数据库记录,将遍历到的记录的计数加1,表示该条记录经历了一个计时周期。判断该条记录的计数是否大于预设的阈值,若不大于上述预设的阈值,则上述芯片驱动删除该未知组播流记录的上送标记,并将记录更新至上述未知组播数据库,并下发出接口为CPU的限速表,使未知组播报文恢复上送至CPU。
当未知组播流记录的计数大于预设的阈值时,直接删除该条未知组播流记录,并删除该未知组播流记录对应的上述转发表项,以控制部分无用的表项占用的芯片资源在一定时间后得到释放。
上述协议栈接收到上述未知组播报文后,向芯片驱动发送正式转发表项,芯片驱动接收到上述正式转发表项,查找未知组播流数据库中是否存在上述未知组播报文所在的未知组播流记录,如果未找到上述未知组播流 记录,则上述芯片驱动向ASIC芯片发送上述正式转发表项;如果上述芯片驱动在上述未知组播流数据库中查找到上述未知组播流记录,则删除该未知组播流记录,然后向上述ASIC芯片发送正式转发表项。
在每一个计时周期内,都会由ASIC芯片向CPU上送一份未知组播报文,后续报文由空接口限速表丢弃,直至协议栈下发正式转发表项结束这一循环过程。这样能够防止报文大量上送而影响CPU性能及其他正常业务模块的运行。
如图4所示,图4为本发明实施例提供的未知组播报文的处理装置,所述装置可以应用于交换机,如图4,未知组播报文处理装置400包括:接收模块401,第一判断模块402,第一发送模块403,第二发送模块404。
接收模块401,用于接收专用集成电路发送的未知组播报文;
第一判断模块402,用于判断所述未知组播报文所在的未知组播流在未知组播流数据库中是否存在记录;
第一发送模块403,用于若不存在所述记录,则向协议栈发送所述未知组播报文,并在所述未知组播流数据库中添加所述未知组播流记录;
第二发送模块404,用于在所述未知组播流数据库中添加所述未知组播流记录后,向所述专用集成电路发送接口为空的限速表,所述限速表用于控制所述未知组播报文不再继续上送。
可选的,如图5所示,所述第一判断模402块包括:
添加单元4021,用于在所述未知组播流数据库中添加所述未知组播流记录,在所述未知组播流记录中添加上送标记,并为所述未知组播流记录创建计数,其中,所述上送标记用于记录所述未知组播报文已经上送。
可选的,如图6所示,所述装置还包括:
第二判断模块405,用于若所述未知组播流数据库存在所述未知组播流记录,则判断所述未知组播流记录是否存在所述上送标记;
丢弃模块406,用于若存在所述上送标记,则丢弃所述未知组播报文;
上送模块407,用于若不存在所述上送标记,则将所述未知组播报文 上送至所述协议栈,并为所述未知组播报文所在的未知组播流添加所述上送标记。
可选的,如图7所示,所述装置还包括:
计时模块408,用于设置计时器,在所述接收未知组播报文的同时开始计时,当计时器时间到达预先设定的时间时,遍历所述未知组播流数据库记录,并将当前遍历的记录的计数加1;
第一删除模块409,用于若所述计数不大于预设的阈值,则删除所述未知组播流记录中的所述上送标记,并向所述专用集成电路发送转发表项,所述转发表项用于在所述协议栈向所述专用集成电路发送正式转发表项前再次上送所述未知组播报文;
第二删除模块410,用于若所述计数大于所述预设的阈值,则删除该未知组播流记录,并删除该未知组播流记录对应的所述转发表项。
可选的,如图8所示,所述装置还包括:
第三判断模块411,用于在所述协议栈接收所述未知组播报文后,接收所述协议栈发送的所述正式转发表项,判断在所述未知组播流数据库中是否存在所述未知组播流记录;
第三发送模块412,用于若不存在所述未知组播流记录,则向所述专用集成电路发送所述正式转发表项;
第三删除模块413,用于若存在所述未知组播流记录,则删除所述未知组播流数据库中的所述未知组播流记录,并向所述专用集成电路发送所述正式转发表项。
本实施例中,上述未知组播报文处理装置400可以应用于交换机。
未知组播报文处理装置400能够实现图1至图2的方式实施例中的各个过程,为避免重复,这里不再赘述。未知组播报文处理装置400能够防止报文大量上送而影响CPU性能及其他正常业务模块的运行。
本领域普通技术人员可以理解实现上述实施例方法的全部或者部分步骤是可以通过程序指令相关的硬件来完成,所述的程序可以存储于一计 算机可读取介质中,该程序在执行时,包括以下步骤:
接收专用集成电路发送的未知组播报文;
判断所述未知组播报文所在的未知组播流在未知组播流数据库中是否存在记录;
若不存在所述记录,则向协议栈发送所述未知组播报文,并在所述未知组播流数据库中添加所述未知组播流记录;
在所述未知组播流数据库中添加所述未知组播流记录后,向所述专用集成电路发送接口为空的限速表,所述限速表用于控制所述未知组播报文不再继续上送。
可选的,所述在所述未知组播流数据库中添加所述未知组播流记录包括:
在所述未知组播流数据库中添加所述未知组播流记录,在所述未知组播流记录中添加上送标记,并为所述未知组播流记录创建计数,其中,所述上送标记用于记录所述未知组播报文已经上送。
可选的,所述方法还包括:
若所述未知组播流数据库存在所述未知组播流记录,则判断所述未知组播流记录是否存在所述上送标记;
若存在所述上送标记,则丢弃所述未知组播报文;
若不存在所述上送标记,则将所述未知组播报文上送至所述协议栈,并为所述未知组播报文所在的未知组播流添加所述上送标记。
可选的,所述方法还包括:
设置计时器,在所述接收未知组播报文的同时开始计时,当计时器时间到达预先设定的时间时,遍历所述未知组播流数据库记录,并将当前遍历的记录的计数加1;
若所述计数不大于预设的阈值,则删除所述未知组播流记录中的所述上送标记,并向所述专用集成电路发送转发表项,所述转发表项用于在所述协议栈向所述专用集成电路发送正式转发表项前再次上送所述未知组 播报文;
若所述计数大于所述预设的阈值,则删除该未知组播流记录,并删除该未知组播流记录对应的所述转发表项。
可选的,所述方法还包括:
在所述协议栈接收所述未知组播报文后,接收所述协议栈发送的所述正式转发表项,判断在所述未知组播流数据库中是否存在所述未知组播流记录;
若不存在所述未知组播流记录,则向所述专用集成电路发送所述正式转发表项;
若存在所述未知组播流记录,则删除所述未知组播流数据库中的所述未知组播流记录,并向所述专用集成电路发送所述正式转发表项。
所述的存储介质,如只读存储器(Read-Only Memory,简称ROM)、随机存取存储器(Random Access Memory,简称RAM)、磁碟或者光盘等。
显然,本领域的技术人员应该明白,上述的本发明的各模块或各步骤可以用通用的计算装置来实现,它们可以集中在单个的计算装置上,或者分布在多个计算装置所组成的网络上,可选地,它们可以用计算装置可执行的程序代码来实现,从而,可以将它们存储在存储装置中由计算装置来执行,并且在某些情况下,可以以不同于此处的顺序执行所示出或描述的步骤,或者将它们分别制作成各个集成电路模块,或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样,本发明不限制于任何特定的硬件和软件结合。
以上所述是本发明的优选实施方式,应当指出,对于本技术领域的普通技术人员来说,在不脱离本发明所述原理的前提下,还可以作出若干改进和润饰,这些改进和润饰也应视为本发明的保护范围。
工业实用性
本发明实施例提供的上述技术方案,可以应用于未知组播报文的处理过程中,通过接收专用集成电路发送的未知组播报文;判断所述未知组播报文所在的未知组播流在未知组播流数据库中是否存在记录;若不存在,则向协议栈发送所述未知组播报文,并在所述未知组播流数据库中添加所述未知组播流记录;在所述未知组播流数据库中添加所述未知组播流记录后,向所述专用集成电路发送接口为空的限速表,以控制所述未知组播报文不再继续上送。这样能够防止报文大量上送而影响CPU性能及其他正常业务模块的运行。

Claims (10)

  1. 一种未知组播报文的处理方法,包括:
    接收专用集成电路发送的未知组播报文;
    判断所述未知组播报文所在的未知组播流在未知组播流数据库中是否存在记录;
    若不存在所述记录,则向协议栈发送所述未知组播报文,并在所述未知组播流数据库中添加所述未知组播流记录;
    在所述未知组播流数据库中添加所述未知组播流记录后,向所述专用集成电路发送接口为空的限速表,所述限速表用于控制所述未知组播报文不再继续上送。
  2. 如权利要求1所述的方法,其中,所述在所述未知组播流数据库中添加所述未知组播流记录包括:
    在所述未知组播流数据库中添加所述未知组播流记录,在所述未知组播流记录中添加上送标记,并为所述未知组播流记录创建计数,其中,所述上送标记用于记录所述未知组播报文已经上送。
  3. 如权利要求2所述的方法,其中,所述方法还包括:
    若所述未知组播流数据库存在所述未知组播流记录,则判断所述未知组播流记录是否存在所述上送标记;
    若存在所述上送标记,则丢弃所述未知组播报文;
    若不存在所述上送标记,则将所述未知组播报文上送至所述协议栈,并为所述未知组播报文所在的未知组播流添加所述上送标记。
  4. 如权利要求3所述的方法,其中,所述方法还包括:
    设置计时器,在所述接收未知组播报文的同时开始计时,当计时器时间到达预先设定的时间时,遍历所述未知组播流数据库记录,并将当前遍历的记录的计数加1;
    若所述计数不大于预设的阈值,则删除所述未知组播流记录中的所述上送标记,并向所述专用集成电路发送转发表项,所述转发表项用于在所述协议栈向所述专用集成电路发送正式转发表项前再次上送所述未知组 播报文;
    若所述计数大于所述预设的阈值,则删除该未知组播流记录,并删除该未知组播流记录对应的所述转发表项。
  5. 如权利要求1至4任一权利要求所述的方法,其中,所述方法还包括:
    在所述协议栈接收所述未知组播报文后,接收所述协议栈发送的所述正式转发表项,判断在所述未知组播流数据库中是否存在所述未知组播流记录;
    若不存在所述未知组播流记录,则向所述专用集成电路发送所述正式转发表项;
    若存在所述未知组播流记录,则删除所述未知组播流数据库中的所述未知组播流记录,并向所述专用集成电路发送所述正式转发表项。
  6. 一种未知组播报文的处理装置,包括:
    接收模块,用于接收专用集成电路发送的未知组播报文;
    第一判断模块,用于判断所述未知组播报文所在的未知组播流在未知组播流数据库中是否存在记录;
    第一发送模块,用于若不存在所述记录,则向协议栈发送所述未知组播报文,并在所述未知组播流数据库中添加所述未知组播流记录;
    第二发送模块,用于在所述未知组播流数据库中添加所述未知组播流记录后,向所述专用集成电路发送接口为空的限速表,所述限速表用于控制所述未知组播报文不再继续上送。
  7. 如权利要求6所述的装置,其中,所述判断模块包括:
    添加单元,用于在所述未知组播流数据库中添加所述未知组播流记录,在所述未知组播流记录中添加上送标记,并为所述未知组播流记录创建计数,其中,所述上送标记用于记录所述未知组播报文已经上送。
  8. 如权利要求7所述的装置,其中,所述装置还包括:
    第二判断模块,用于若所述未知组播流数据库存在所述未知组播流记 录,则判断所述未知组播流记录是否存在所述上送标记;
    丢弃模块,用于若存在所述上送标记,则丢弃所述未知组播报文;
    上送模块,用于若不存在所述上送标记,则将所述未知组播报文上送至所述协议栈,并为所述未知组播报文所在的未知组播流添加所述上送标记。
  9. 如权利要求8所述的装置,其中,所述装置还包括:
    计时模块,用于设置计时器,在所述接收未知组播报文的同时开始计时,当计时器时间到达预先设定的时间时,遍历所述未知组播流数据库记录,并将当前遍历的记录的计数加1;
    第一删除模块,用于若所述计数不大于预设的阈值,则删除所述未知组播流记录中的所述上送标记,并向所述专用集成电路发送转发表项,所述转发表项用于在所述协议栈向所述专用集成电路发送正式转发表项前再次上送所述未知组播报文;
    第二删除模块,用于若所述计数大于所述预设的阈值,则删除该未知组播流记录,并删除该未知组播流记录对应的所述转发表项。
  10. 如权利要求6至9任一权利要求所述的装置,其中,所述装置还包括:
    第三判断模块,用于在所述协议栈接收所述未知组播报文后,接收所述协议栈发送的所述正式转发表项,判断在所述未知组播流数据库中是否存在所述未知组播流记录;
    第三发送模块,用于若不存在所述未知组播流记录,则向所述专用集成电路发送所述正式转发表项;
    第三删除模块,用于若存在所述未知组播流记录,则删除所述未知组播流数据库中的所述未知组播流记录,并向所述专用集成电路发送所述正式转发表项。
PCT/CN2017/090946 2016-07-20 2017-06-29 一种未知组播报文的处理方法和装置 WO2018014710A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610571457.7A CN107645452B (zh) 2016-07-20 2016-07-20 一种未知组播报文的处理方法和装置
CN201610571457.7 2016-07-20

Publications (1)

Publication Number Publication Date
WO2018014710A1 true WO2018014710A1 (zh) 2018-01-25

Family

ID=60992984

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/090946 WO2018014710A1 (zh) 2016-07-20 2017-06-29 一种未知组播报文的处理方法和装置

Country Status (2)

Country Link
CN (1) CN107645452B (zh)
WO (1) WO2018014710A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111224882A (zh) * 2018-11-23 2020-06-02 中兴通讯股份有限公司 报文处理方法及装置、存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111130816B (zh) * 2019-12-27 2022-06-24 北京东土军悦科技有限公司 一种报文转发处理设备、方法、装置和存储介质
CN115514721B (zh) * 2022-09-23 2023-11-07 北京东土军悦科技有限公司 未知组播数据的处理方法及装置、计算设备、存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101789905A (zh) * 2010-02-05 2010-07-28 杭州华三通信技术有限公司 防止未知组播攻击cpu的方法和设备
CN102916892A (zh) * 2012-11-05 2013-02-06 杭州迪普科技有限公司 一种组播报文的处理方法及装置
CN103166867A (zh) * 2011-12-19 2013-06-19 迈普通信技术股份有限公司 一种流控方法和装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1326340C (zh) * 2003-10-21 2007-07-11 华为技术有限公司 无源光网络的动态带宽分配装置及方法
CN100466606C (zh) * 2005-08-24 2009-03-04 杭州华三通信技术有限公司 未知组播报文的处理方法
CN101426014B (zh) * 2008-12-02 2013-04-03 中兴通讯股份有限公司 防止组播源攻击的方法及***
CN102223269B (zh) * 2011-06-23 2015-06-17 瑞斯康达科技发展股份有限公司 一种报文处理方法、mac地址漂移的检测方法及装置
US8824297B2 (en) * 2012-04-26 2014-09-02 Cisco Technology, Inc. Adaptive storm control
CN104753796A (zh) * 2013-12-30 2015-07-01 上海斐讯数据通信技术有限公司 优化组播路由表建立的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101789905A (zh) * 2010-02-05 2010-07-28 杭州华三通信技术有限公司 防止未知组播攻击cpu的方法和设备
CN103166867A (zh) * 2011-12-19 2013-06-19 迈普通信技术股份有限公司 一种流控方法和装置
CN102916892A (zh) * 2012-11-05 2013-02-06 杭州迪普科技有限公司 一种组播报文的处理方法及装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111224882A (zh) * 2018-11-23 2020-06-02 中兴通讯股份有限公司 报文处理方法及装置、存储介质

Also Published As

Publication number Publication date
CN107645452B (zh) 2022-06-07
CN107645452A (zh) 2018-01-30

Similar Documents

Publication Publication Date Title
KR102317523B1 (ko) 패킷 제어 방법 및 네트워크 기기
JP5514913B2 (ja) フローアウェアネットワークノード内でデータパケットを処理するための方法
WO2018014710A1 (zh) 一种未知组播报文的处理方法和装置
US9705808B2 (en) Flow aware buffer management for data center switches
WO2015149488A1 (zh) 一种令牌桶限速方法、装置及计算机存储介质
US20170041230A1 (en) Forwarding data packets
WO2015131486A1 (zh) 一种组播报文的转发方法及装置
WO2017161967A1 (zh) 包每秒流量监管方法、装置和计算机存储介质
WO2015081715A1 (zh) 一种网站的在线用户统计方法和装置
US20210307026A1 (en) Dejittering System
EP3121995A1 (en) Method and device for maintaining multicast members
WO2016202113A1 (zh) 一种队列管理方法、装置及存储介质
CN107819697B (zh) 数据传输方法、交换机及数据中心
CN113904845A (zh) 一种攻击流量统计方法及装置
WO2021073103A1 (zh) 随流信息遥测能力的确认方法和设备
US11303573B2 (en) Method and system for managing the download of data
US20170272192A1 (en) Synchronization of Data and Control Planes of Routers
CN113518017B (zh) 一种网络状态分析方法、装置、设备及机器可读存储介质
WO2021254307A1 (zh) 确定报文发送路径的方法及装置
WO2009121261A1 (zh) 路由管理方法、装置和***
WO2016078212A1 (zh) 一种报文处理方法、装置及存储介质
CN112242932B (zh) 时延检测方法和***
WO2019114779A1 (zh) 信息收集
US9813319B1 (en) Method of detecting packet loss in a communication network
WO2024055584A1 (zh) 时延测量方法、电子设备、计算机可读介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17830344

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17830344

Country of ref document: EP

Kind code of ref document: A1