Information processing method and device

Abstract

The embodiment of the invention discloses an information processing method. The information processing method can be applied to control management equipment. The control management equipment can obtain at least one first SAV table item used for source address verification by a first communication device, and store the first SAV table item. Therefore, by utilizing the scheme, the control management equipment can obtain and store the first SAV table item, so that the monitoring of the SAV table item used by the first communication device for source address verification is realized, the reliability of the SAV table item used by the first communication device for source address verification is improved, and correspondingly, the security of the first communication device is improved. The reliability of source address verification performed by the first communication device based on the SAV table entry is improved.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to an information processing method and device. Background Art

[0002] Network attackers can use source addresses to attack the network. In order to reduce source address attacks, the source address of the traffic transmitted in the network can be verified.

[0003] Currently, the communication device can use a distributed source address validation (DSAV) scheme to verify the source address of the traffic. In one example, the communication device can use one or more SAV entries stored locally to verify the source address of the traffic to prevent source address attacks.

[0004] However, the reliability of the current communication device using the SAV table entry to verify the source address cannot be guaranteed. Therefore, a solution is urgently needed to solve the above problem. Summary of the invention

[0005] The embodiments of the present application provide an information processing method and device, which can improve the reliability of a communication device performing source address verification using a SAV table entry.

[0006] In the first aspect, an embodiment of the present application provides an information processing method, which can be applied to a control management device. The control management device can obtain at least one first SAV table entry used by the first communication device for source address verification, and save the first SAV table entry. It can be seen that, using this solution, the control management device can obtain and save the first SAV table entry, thereby realizing the monitoring of the SAV table entry used by the first communication device for source address verification, thereby improving the reliability of the SAV table entry used by the first communication device for source address verification, and correspondingly, improving the reliability of the first communication device for source address verification based on the SAV table entry.

[0007] In one possible implementation, when the control management device obtains the at least one first SAV table entry, it can receive a first Border Gateway Protocol Monitoring Protocol (BMP) message sent by the first communication device, the first BMP message includes a first source path discovery (SPD) message, the first SPD message includes a second SPD message received by the first communication device and interface information of the first communication device receiving the second SPD message, and further generate the at least one first SAV table entry based on the first SPD message.

[0008] In one possible implementation, the first BMP message includes a common header, and the message type field of the common header indicates that the first BMP message includes a first BGP route refresh message. In a specific example, the message type field in the common header of the first BMP message is used to indicate a new BMP message type, for example, the newly added BMP message type is: BMP route refresh monitoring (route refresh monitoring, RRM). BMP RRM is used by the communication device to report the BGP route refresh messages received and / or sent by the communication device to the control management device. In an example, the first BGP route refresh message may include first indication information, and the first indication information is used to indicate that the first BGP route refresh message is the first SPD message.

[0009] In a possible implementation manner, the protocol data unit (Protocol Data Unit, PDU) of the first BMP message may include a BMP RRM message, and the BMP RRM message includes the aforementioned first BGP route refresh message.

[0010] In a possible implementation, the PDU of the first BMP message may be a BMP route refresh monitoring PDU, and the BMP route refresh monitoring PDU includes the first BGP route refresh message.

[0011] In a possible implementation, the first indication information may be a subtype field of the first BGP route refresh message. In this case, even if the first communication device also supports BGP outbound route filtering (ORF) capability, it is possible to determine that the first BGP route refresh message is a first SPD message based on the subtype field.

[0012] In a possible implementation, the first indication information may be a length field of the first BGP route refresh message. For example, when the first communication device does not enable BGP ORF capability, the first BGP route refresh message may be determined to be a first SPD message based on the length field of the first BGP route refresh message.

[0013] In one possible implementation, the first SPD message also includes first verification mode information, which indicates the verification mode adopted by the first communication device to verify the source address based on the at least one first SAV table entry, so that the control management device can determine the verification mode of the first SAV table entry.

[0014] In one possible implementation, the control and management device may also obtain at least one second SAV table item generated by the first communication device based on the second SPD message, and perform consistency verification on the at least one first SAV table item and the at least one second SAV table item. As a specific example, the control and management device may compare the at least one first SAV table item and the at least one second SAV table item to determine whether the at least one first SAV table item and the at least one second SAV table item are consistent. If they are inconsistent, the control and management device may, for example, output an alarm message to prompt the operation and maintenance personnel to investigate the cause of the inconsistency between the at least one first SAV table item and the at least one second SAV table item, thereby improving network security.

[0015] In a possible implementation, the control management device acquires the at least one first SAV table item by receiving a BGP link state (LS) message from the first communication device, and the BGP LS message includes the at least one first SAV table item. In this case, there is no need to use a manual collection method, and the first communication device can report the at least one first SAV table item through a BGP LS message to realize automatic reporting of the SAV table item.

[0016] In one possible implementation, the BGP LS message includes network layer reachability information (NLRI), and the NLRI includes prefix type length values ​​(type length value, TLV) corresponding to each entry in the at least one first SAV table entry, and each prefix TLV is used to carry the source prefix in the entry corresponding to the prefix TLV.

[0017] In one possible implementation, the prefix TLV also includes second verification mode information, which indicates the verification mode adopted by the first communication device to verify the source address based on the table entry corresponding to the prefix TLV, so that the control management device can determine the verification mode of the corresponding SAV table entry.

[0018] In one possible implementation, considering that there may be multiple types of SAV table entries used by the first communication device for source address verification, the prefix TLV may include indication information indicating the type corresponding to the first SAV table entry corresponding to the prefix TLV. In a specific example, the type field of the prefix TLV can be used to indicate the table entry type of the SAV table entry corresponding to the prefix TLV.

[0019] In a possible implementation manner, the BGP LS message further includes an interface TLV, where the interface TLV is used to carry the inbound interface information in the at least one first SAV table entry.

[0020] In a possible implementation manner, the interface TLV is carried by the NLRI or BGP path attribute of the BGP LS message.

[0021] In a possible implementation, the control management device can verify whether there is a conflict between different types of entries when the at least one first SAV entry includes multiple types of entries. In one example, if there is a conflict between the different types of entries, the control management device can, for example, output an alarm message to prompt the operation and maintenance personnel to investigate the cause of the conflict between the at least one first SAV entry, thereby improving network security.

[0022] In one possible implementation, the control and management device can also receive a second BMP message sent by a second communication device, wherein the second BMP message includes a basic BGP route refresh message exchanged between the second communication device and a third communication device, and the basic BGP route refresh message is used to exchange routing update requests between the second communication device and the third communication device, thereby monitoring the basic BGP route refresh messages exchanged between the communication devices.

[0023] In one possible implementation, the second BMP message includes a common header, and the message type field of the common header indicates that the second BMP message includes a second BGP route refresh message. In a specific example, the message type field in the common header of the second BMP message is used to indicate a new BMP message type, for example, the newly added BMP message type is: BMP RRM. BMPRRM is used by the communication device to report the BGP route refresh messages received and / or sent by the communication device to the control and management device. In an example, the second BGP route refresh message may include second indication information, and the second indication information is used to indicate that the second BGP route refresh message is the basicBGP route refresh message.

[0024] In a possible implementation manner, the PDU of the second BMP message may include a BMP RRM message, and the BMP RRM message includes the aforementioned basic BGP route refresh message.

[0025] In a possible implementation manner, the PDU of the second BMP message may be a BMP route refresh monitoring PDU, and the BMP route refresh monitoring PDU includes the second BGP route refresh message.

[0026] In a possible implementation manner, the second indication information may be a subtype field or a length field of the first BGP routerefresh message.

[0027] In a possible implementation, the control management device may also receive a third BMP message sent by the fourth communication device, wherein the third BMP message includes an ORF message exchanged between the fourth communication device and the fifth communication device, thereby monitoring the BGP ORF messages exchanged between the communication devices.

[0028] In one possible implementation, the third BMP message includes a common header, and the message type field of the common header indicates that the third BMP message includes a third BGP route refresh message. In a specific example, the message type field in the common header of the third BMP message is used to indicate a new BMP message type, for example, the newly added BMP message type is: BMP RRM. BMPRRM is used by the communication device to report the BGP route refresh messages received and / or sent by the communication device to the control and management device. In an example, the third BGP route refresh message may include third indication information, and the third indication information is used to indicate that the third BGP route refresh message is the ORF message.

[0029] In a possible implementation manner, the PDU of the third BMP message may include a BMP RRM message, and the BMP RRM message includes the aforementioned third BGP route refresh message.

[0030] In a possible implementation manner, the PDU of the third BMP message may be a BMP route refresh monitoring PDU, and the BMP route refresh monitoring PDU includes the third BGP route refresh message.

[0031] In a possible implementation, the third indication information may be a subtype field of the third BGP route refresh message. In this case, even if the first communication device also supports receiving and / or sending SPD messages, it can be determined that the third BGP route refresh message is an ORF message based on the subtype field.

[0032] In a possible implementation, the third indication information may be a length field of the third BGP route refresh message. For example, when the first communication device does not support receiving and / or sending SPD messages, the third BGP route refresh message may be determined to be an ORF message based on the length field of the third BGP route refresh message.

[0033] In a possible implementation, the control management device may also locate the reason why the number of routing prefixes sent by the fourth communication device and the number of routing prefixes received by the fifth communication device are inconsistent based on the ORF message. For example, it is determined that the reason why the number of routing prefixes sent by the fourth communication device and the number of routing prefixes received by the fifth communication device are inconsistent is because the fifth communication device is configured with a prefix-based ingress policy, rather than a network failure.

[0034] In the second aspect, an information processing method provided by an embodiment of the present application can be applied to a first communication device. The first communication device can obtain a Border Gateway Protocol Monitoring Protocol (BMP) message, and the BMP message includes a BGP route refresh message exchanged between the first communication device and the second communication device. After the first communication device obtains the BMP message, it can send the BMP message to the control and management device. Using this solution, the control and management device can monitor the BGP route refresh messages exchanged between the communication devices, thereby improving the reliability of the network. In one example, when the BGP route refresh message is a message related to the SAV table entry, using this solution, the control and management device can monitor the SAV table entry used by the first communication device for source address verification, thereby improving the reliability of the SAV table entry used by the first communication device for source address verification, and accordingly, improving the reliability of the first communication device for source address verification based on the SAV table entry.

[0035] In a possible implementation manner, the message type field in the common header of the BMP message indicates that the message carried in the PDU of the BMP message is a BGP route refresh message.

[0036] In a possible implementation manner, the message type field in the common header of the BMP message indicates that the BMP message is a BMP RRM, and the message carried in the PDU of the BMP RRM is a BGP route refresh message.

[0037] In a possible implementation manner, the PDU of the BMP message is a BMP RRM PDU.

[0038] In a possible implementation, the BGP route refresh message is a first source path discovery SPD message, and the first SPD message includes a second SPD message received by the first communication device and interface information of the first communication device receiving the second SPD message.

[0039] In a possible implementation, the message type field in the common header of the BMP message indicates that the BMP message includes the BGP route refresh message, and the BGP route refresh message includes first indication information, and the first indication information indicates that the BGP route refresh message is the first SPD message.

[0040] In a possible implementation manner, the first indication information is a subtype field of the first BGP route refresh message.

[0041] In a possible implementation, the first SPD message further includes first verification mode information, where the first verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the at least one first SAV table entry.

[0042] In a possible implementation manner, the BGP route refresh message is a basic BGP route refresh message, and the basic BGP route refresh message is used to exchange route update requests between the first communication device and the second communication device.

[0043] In a possible implementation, the message type field in the common header of the BMP message indicates that the BMP message includes the BGP route refresh message, the BGP route refresh message includes second indication information, and the second indication information indicates that the BGP route refresh message is the basic BGP route refresh message.

[0044] In a possible implementation manner, the BGP route refresh message is an egress route filtering ORF message.

[0045] In a possible implementation, the message type field in the common header of the BMP message indicates that the BMP message includes the BGP route refresh message, the BGP route refresh message includes third indication information, and the third indication information indicates that the BGP route refresh message is the ORF message.

[0046] On the third aspect, an embodiment of the present application provides an information processing method, which can be applied to a first communication device. The first communication device can obtain a BGP link state (LS) message, and the BGP LS message includes at least one SAV table item used by the first communication device to perform source address verification. After the first communication device obtains the BGP LS message, it can send the BGP LS message to the control and management device. It can be seen that, using the solution of the embodiment of the present application, the control and management device can obtain at least one SAV table item used by the first communication device to perform source address verification, thereby realizing the monitoring of the SAV table item used by the first communication device for source address verification, thereby improving the reliability of the SAV table item used by the first communication device for source address verification, and accordingly, improving the reliability of the first communication device for source address verification based on the SAV table item.

[0047] In a possible implementation, the BGP LS message includes network layer reachability information NLRI, the NLRI includes prefix type length value TLVs corresponding to each entry in the at least one SAV table entry, each prefix TLV is used to carry the source prefix in the entry corresponding to the prefix TLV.

[0048] In a possible implementation manner, the prefix TLV further includes verification mode information, where the verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the table entry corresponding to the prefix TLV.

[0049] In a possible implementation manner, the type field of the prefix TLV indicates the entry type of the entry corresponding to the prefix TLV.

[0050] In a possible implementation manner, the BGP LS message further includes an interface TLV, where the interface TLV is used to carry the inbound interface information in the at least one SAV table entry.

[0051] In a possible implementation manner, the interface TLV is carried by the NLRI or BGP path attribute.

[0052] In the fourth aspect, an embodiment of the present application provides an information processing method, which can be applied to a first communication device. The first communication device can obtain a BMP message, and the BMP message includes a first source path discovery (Source path discovery, SPD) message received by the first communication device and the interface information of the first communication device receiving the first SPD message. After the first communication device obtains the BMP message, it can send the BMP message to the control management device. It can be seen that, using this scheme, the control management device can obtain the first SPD message received by the first communication device and the interface information of the first communication device receiving the first SPD message, thereby obtaining the SAV table entry used by the first communication device for source address verification, thereby realizing the monitoring of the SAV table entry used for source address verification of the first communication device, thereby improving the reliability of the SAV table entry used by the first communication device for source address verification, and correspondingly, improving the reliability of the first communication device for source address verification based on the SAV table entry.

[0053] In a possible implementation, the BMP message includes a BGP route refresh message, the BGP route refresh message is a second SPD message, and the second SPD message includes the first SPD message received by the first communication device and interface information of the first communication device receiving the first SPD message.

[0054] In a possible implementation, the message type field in the common header of the BMP message indicates that the BMP message includes a BGP Proute refresh message, and the BGP route refresh message includes indication information, and the indication information indicates that the BGP route refresh message is the second SPD message.

[0055] In a possible implementation manner, the indication information is a subtype field of the BGP route refresh message.

[0056] In the fifth aspect, an embodiment of the present application provides an information processing method that can be applied to a first communication device. The first communication device can obtain a BMP message, and the BMP message includes a basic BGP route refresh message exchanged between the first communication device and the second communication device, and the basic BGP route refresh message is used to exchange routing update requests between the first communication device and the second communication device. After the first communication device obtains the BMP message, it can send the BMP message to a control and management device. It can be seen that, using the solution of the embodiment of the present application, the control and management device can monitor the basic BGP route refresh messages exchanged between communication devices, which is beneficial to improving the reliability of the network.

[0057] In a possible implementation, the message type field in the common header of the BMP message indicates that the BMP message includes a BGP route refresh message, and the BGP route refresh message includes indication information, and the indication information indicates that the BGP route refresh message is the basic BGP route refresh message.

[0058] In the sixth aspect, an embodiment of the present application provides an information processing method that can be applied to a first communication device. The first communication device can obtain a BMP message, and the BMP message includes a BGP outbound route filtering (ORF) message exchanged between the first communication device and the second communication device. After the first communication device obtains the BMP message, it can send the BMP message to a control and management device. It can be seen that by using the solution of the embodiment of the present application, the control and management device can monitor the BGP ORF messages exchanged between the first communication device and the second communication device, which is beneficial to improving the reliability of the network.

[0059] In a possible implementation, the message type field in the common header of the BMP message indicates that the BMP message includes a BGP ORF message, and the BGP route refresh message includes indication information, and the indication information indicates that the BGP route refresh message is the BGP ORF message.

[0060] In one possible implementation, before obtaining the BMP message, the method also includes: receiving a BGP route refresh message sent by the second communication device, the subtype field of the BGP route refresh indicating that the BGP refresh message includes the BGP ORF message; or, sending a BGP route refresh message to the second communication device, the subtype field of the BGP route refresh indicating that the BGPrefresh message includes the BGP ORF message.

[0061] In a seventh aspect, an embodiment of the present application provides an information processing device, which is applied to a control management device and is used to execute the information processing method executed by the control management device described in the first aspect above. The device includes: an acquisition unit, which is used to acquire at least one first source address verification SAV table entry used by a first communication device to perform source address verification; and a processing unit, which is used to save the at least one first SAV table entry.

[0062] In one possible implementation, the acquisition unit is used to: receive a first Border Gateway Protocol Monitoring Protocol BMP message sent by the first communication device, the first BMP message including a first Source Path Discovery SPD message, the first SPD message including a second SPD message received by the first communication device and interface information of the first communication device receiving the second SPD message; and generate at least one first SAV table entry based on the first SPD message.

[0063] In a possible implementation, the message type field in the common header of the first BMP message indicates that the first BMP message includes a first BGP route refresh message, the first BGP route refresh message includes first indication information, and the first indication information indicates that the first BGP route refresh message is the first SPD message.

[0064] In a possible implementation manner, the first indication information is a subtype field of the first BGP route refresh message.

[0065] In a possible implementation, the first SPD message further includes first verification mode information, where the first verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the at least one first SAV table entry.

[0066] In a possible implementation, the acquisition unit is further used to: acquire at least one second SAV table entry generated by the first communication device based on the second SPD message; the processing unit is further used to verify the consistency of the at least one first SAV table entry and the at least one second SAV table entry.

[0067] In one possible implementation, the device also includes: a receiving unit, used to receive a second BMP message sent by a second communication device, the second BMP message including a basic BGP route refresh message exchanged between the second communication device and a third communication device, and the basic BGP route refresh message is used to exchange routing update requests between the second communication device and the third communication device.

[0068] In one possible implementation, the message type field in the common header of the second BMP message indicates that the second BMP message includes a second BGP route refresh message, the second BGP route refresh message includes second indication information, and the second indication information indicates that the second BGP route refresh message is the basicBGP route refresh message.

[0069] In a possible implementation, the device includes a receiving unit further configured to: receive a third BMP message sent by a fourth communication device, wherein the third BMP message includes an egress routing filter ORF message exchanged between the fourth communication device and a fifth communication device.

[0070] In one possible implementation, the message type field in the common header of the third BMP message indicates that the third BMP message includes a third BGP route refresh message, the third BGP route refresh message includes third indication information, and the third indication information indicates that the third BGP route refresh message is the ORF message.

[0071] In a possible implementation, the processing unit is further configured to locate, based on the ORF message, a reason why the number of routing prefixes sent by the fourth communication device and the number of routing prefixes received by the fifth communication device are inconsistent.

[0072] In a possible implementation manner, the acquiring unit is configured to: receive a BGP link state LS message from the first communication device, wherein the BGP LS message includes the at least one first SAV table entry.

[0073] In one possible implementation, the BGP LS message includes network layer reachability information NLRI, the NLRI includes prefix type length value TLVs corresponding to each entry in the at least one first SAV table entry, and each prefix TLV is used to carry the source prefix in the entry corresponding to the prefix TLV.

[0074] In a possible implementation manner, the prefix TLV further includes second verification mode information, where the second verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the table entry corresponding to the prefix TLV.

[0075] In a possible implementation manner, the type field of the prefix TLV indicates the entry type of the entry corresponding to the prefix TLV.

[0076] In a possible implementation manner, the BGP LS message further includes an interface TLV, where the interface TLV is used to carry the inbound interface information in the at least one first SAV table entry.

[0077] In a possible implementation manner, the interface TLV is carried by the NLRI or BGP path attribute.

[0078] In a possible implementation manner, the processing unit is further configured to: when the at least one first SAV table entry includes multiple types of table entries, verify whether there is a conflict between different types of table entries.

[0079] In an eighth aspect, an embodiment of the present application provides an information processing device, applied to a first communication device, the device comprising: a processing unit and a sending unit.

[0080] In a specific example, the information processing device is used to execute the information processing method performed by the first communication device as described in the second aspect above. Correspondingly, the processing unit is used to obtain a Border Gateway Protocol Monitoring Protocol BMP message, wherein the BMP message includes a BGP route refresh message exchanged between the first communication device and the second communication device; and the sending unit is used to send the BMP message to the control management device.

[0081] In a possible implementation, the BGP route refresh message is a first source path discovery SPD message, and the first SPD message includes a second SPD message received by the first communication device and interface information of the first communication device receiving the second SPD message.

[0082] In a possible implementation, the message type field in the common header of the BMP message indicates that the BMP message includes the BGP route refresh message, and the BGP route refresh message includes first indication information, and the first indication information indicates that the BGP route refresh message is the first SPD message.

[0083] In a possible implementation manner, the first indication information is a subtype field of the first BGP route refresh message.

[0084] In a possible implementation, the first SPD message further includes first verification mode information, where the first verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the at least one first SAV table entry.

[0085] In a possible implementation manner, the BGP route refresh message is a basic BGP route refresh message, and the basic BGP route refresh message is used to exchange route update requests between the first communication device and the second communication device.

[0086] In a possible implementation, the message type field in the common header of the BMP message indicates that the BMP message includes the BGP route refresh message, the BGP route refresh message includes second indication information, and the second indication information indicates that the BGP route refresh message is the basic BGP route refresh message.

[0087] In a possible implementation manner, the BGP route refresh message is an egress route filtering ORF message.

[0088] In a possible implementation, the message type field in the common header of the BMP message indicates that the BMP message includes the BGP route refresh message, the BGP route refresh message includes third indication information, and the third indication information indicates that the BGP route refresh message is the ORF message.

[0089] In another specific example, the information processing device is used to execute the information processing method performed by the first communication device as described in the third aspect above. In this case, the processing unit is used to obtain a BGP link state LS message, wherein the BGP LS message includes at least one source address verification SAV table entry used by the first communication device for source address verification; and the sending unit is used to send the BGP LS message to the control management device.

[0090] In a possible implementation, the BGP LS message includes network layer reachability information NLRI, the NLRI includes prefix type length value TLVs corresponding to each entry in the at least one SAV table entry, each prefix TLV is used to carry the source prefix in the entry corresponding to the prefix TLV.

[0091] In a possible implementation manner, the prefix TLV further includes verification mode information, where the verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the table entry corresponding to the prefix TLV.

[0092] In a possible implementation manner, the type field of the prefix TLV indicates the entry type of the entry corresponding to the prefix TLV.

[0093] In a possible implementation manner, the BGP LS message further includes an interface TLV, where the interface TLV is used to carry the inbound interface information in the at least one SAV table entry.

[0094] In a possible implementation manner, the interface TLV is carried by the NLRI or BGP path attribute.

[0095] In a specific example, the information processing device is used to execute the information processing method performed by the first communication device as described in the fourth aspect above. In this case, the processing unit is used to obtain a Border Gateway Protocol Monitoring Protocol BMP message, and the BMP message includes: a first source path discovery SPD message received by the first communication device and interface information of the first communication device receiving the first SPD message; the sending unit is used to send the BMP message to the control management device.

[0096] In a possible implementation, the BMP message includes a BGP route refresh message, the BGP route refresh message is a second SPD message, and the second SPD message includes the first SPD message received by the first communication device and interface information of the first communication device receiving the first SPD message.

[0097] In another specific example, the information processing device is used to execute the information processing method performed by the first communication device as described in the fifth aspect above. In this case, the processing unit is used to obtain a Border Gateway Protocol Monitoring Protocol BMP message, wherein the BMP message includes a basic Border Gateway Protocol route refresh basic BGP route refresh message exchanged between the first communication device and the second communication device, wherein the basic BGP route refresh message is used to exchange route update requests between the first communication device and the second communication device; and the sending unit is used to send the BMP message to the control management device.

[0098] In another specific example, the information processing device is used to execute the information processing method performed by the first communication device as described in the sixth aspect above. In this case, the processing unit is used to obtain a Border Gateway Protocol Monitoring Protocol BMP message, wherein the BMP message includes a Border Gateway Protocol Export Routing Filtering BGP ORF message exchanged between the first communication device and the second communication device; and the sending unit is used to send the BMP message to the control management device.

[0099] In a possible implementation, the device further includes: a receiving unit, configured to receive a BGP route refresh message sent by the second communication device before acquiring the BMP message, wherein the subtype field of the BGP route refresh indicates that the BGP refresh message includes the BGP ORF message.

[0100] In a possible implementation, the sending unit is further configured to send a BGP route refresh message to the second communication device before acquiring the BMP message, and a subtype field of the BGP route refresh indicates that the BGP refresh message includes the BGP ORF message.

[0101] In a ninth aspect, an embodiment of the present application provides a communication device, characterized in that it includes: a processor and a memory;

[0102] The memory is used to store instructions; the processor is used to execute the instructions, so that the communication device executes the method described in the first aspect and any one of the first aspect, or the communication device executes the method described in the second aspect and any one of the second aspect, or the communication device executes the method described in the third aspect and any one of the third aspect, or the communication device executes the method described in the fourth aspect and any one of the fourth aspect, or the communication device executes the method described in the fifth aspect and any one of the fifth aspect, or the communication device executes the method described in the sixth aspect and any one of the sixth aspect.

[0103] In the tenth aspect, an embodiment of the present application provides a computer-readable storage medium, including instructions or computer programs. When the instructions or computer programs are executed on a processor, the methods described in the first aspect and any one of the first aspect are implemented, or the methods described in the second aspect and any one of the second aspect are implemented, or the methods described in the third aspect and any one of the third aspect are implemented, or the methods described in the fourth aspect and any one of the fourth aspect are implemented, or the methods described in the fifth aspect and any one of the fifth aspect are implemented, or the methods described in the sixth aspect and any one of the sixth aspect are implemented.

[0104] In the eleventh aspect, an embodiment of the present application provides a computer program product, including a computer program product, which, when running on a processor, implements the method described in the first aspect and any one of the first aspects, or implements the method described in the second aspect and any one of the second aspects, or implements the method described in the third aspect and any one of the third aspects, or implements the method described in the fourth aspect and any one of the fourth aspects, or implements the method described in the fifth aspect and any one of the fifth aspects, or implements the method described in the sixth aspect and any one of the sixth aspects.

[0105] In the twelfth aspect, an embodiment of the present application provides a communication system, which includes the control management device described in any one of the seventh aspect above, and the first communication device described in any one of the eighth aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0106] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For those skilled in the art, other drawings can be obtained based on these drawings without paying any creative work.

[0107] Figure 1a A schematic diagram of the structure of a BGP message header provided in an embodiment of the present application;

[0108] Figure 1b A schematic diagram of the structure of MP_REACH_NLRI provided in an embodiment of the present application;

[0109] Figure 1c A schematic diagram of the structure of a BGP refresh message provided in an embodiment of the present application;

[0110] Figure 1d A schematic diagram of the structure of another BGP refresh message provided in an embodiment of the present application;

[0111] Figure 1e A schematic diagram of the structure of a link state NLRI provided in an embodiment of the present application;

[0112] Figure 1f A schematic diagram of the structure of a BMP message provided in an embodiment of the present application;

[0113] Figure 2a A schematic diagram of the structure of an SPD message provided in an embodiment of the present application;

[0114] Figure 2b A schematic diagram of an exemplary application scenario provided for an embodiment of the present application;

[0115] Figure 3 A schematic diagram of an exemplary application scenario provided for an embodiment of the present application;

[0116] Figure 4 A flowchart of an information processing method provided in an embodiment of the present application;

[0117] Figure 5a A schematic diagram of the structure of a BGP LS SAVNET Prefix NLRI provided in an embodiment of the present application;

[0118] Figure 5b A schematic diagram of the structure of a prefix TLV provided in an embodiment of the present application;

[0119] Figure 5c A schematic diagram of the structure of an interface TLV provided in an embodiment of the present application;

[0120] Figure 6a A flowchart of an information processing method provided in an embodiment of the present application;

[0121] Figure 6b A flowchart of another information processing method provided in an embodiment of the present application;

[0122] Figure 6c A flowchart of another information processing method provided in an embodiment of the present application;

[0123] Figure 6d A flowchart of another information processing method provided in an embodiment of the present application;

[0124] Figure 6e A flowchart of another information processing method provided in an embodiment of the present application;

[0125] Figure 6f A flowchart of another information processing method provided in an embodiment of the present application;

[0126] Figure 7 A schematic diagram of the structure of a control management device provided in an embodiment of the present application;

[0127] Figure 8 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0128] Fig. 9 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0129] Fig.10 A schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0130] The embodiments of the present application provide an information processing method and device, which can improve the reliability of a communication device performing source address verification using a SAV table entry.

[0131] For ease of understanding, the relevant technologies involved in the embodiments of the present application are first introduced.

[0132] 1.BGP

[0133] BGP is a dynamic routing protocol used between autonomous systems (AS). As the standard for internet external routing protocols, BGP is widely used between internet service providers (ISPs). Currently, the most widely used protocol is Multi-Protocol Extensions for BGP (MP-BGP), which is based on BGP version 4 (BGP-4).

[0134] BGP messages consist of two parts: the BGP message header and the message content. As shown in Table 1, BGP has five message types as shown in Table 2. These five message types have the same BGP message header. These messages are transmitted through the Transmission Control Protocol (TCP). The maximum length of a message is 65535 bytes and the minimum length is 19 bytes (including only the BGP message header). Figure 1a As shown, Figure 1a A schematic diagram of the structure of a BGP message header provided in an embodiment of the present application. Figure 1a As shown in FIG. 1 , the BGP message header includes three parts, namely, a marker field, a length field, and a type field. The three parts of the BGP message header can be understood in conjunction with the following Table 1.

[0135] Table 1

[0136]

[0137]

[0138] Table 2

[0139] type value Message Type 1 open 2 update 3 notification 4 keepalive 5 route refresh

[0140] in:

[0141] BGP open messages, BGP notification messages, and BGP keepalive messages are not described in detail here.

[0142] BGP update messages are used to advertise routes;

[0143] In one example, the communication devices may announce routes through MP-BGP. Specifically, the BGP messages exchanged between the communication devices for announcing routes include Multi-Protocol reachnetwork layer reachability information (MP_REACH_NLRI), and MP_REACH_NLRI is used to carry routes. In one example, the structure of MP_REACH_NLRI is as follows: Figure 1b As shown, Figure 1b A schematic diagram of the structure of MP_REACH_NLRI provided in an embodiment of the present application. Figure 1bAs shown, the MP_REACH_NLRI includes an address family identifier (AFI), a subsequent address family identifier (SAFI), a next hop information length field, a next hop information field and an NLRI field.

[0144] As an example, the AFI field can identify the network layer protocol, for example, the value of the AFI field is 1 to identify IPv4, the value of the AFI field is 2 to identify IPv6, and the value of the AFI field can refer to the relevant description of the address family number (AddressFamily Number) in RFC1700, which is not described in detail here. The SAFI field identifies the type of the sub-address family, for example, the value of the SAFI field is 1 to identify unicast, the value of the SAFI field is 2 to identify multicast, the value of the SAFI field is 74 to identify SD-WAN, and the value of the SAFI field is 128 to identify a virtual private network (VPN).

[0145] In an example, the aforementioned next-hop network address may refer to the network address of the next device on the path to the destination device.

[0146] In an example, the NLRI field may include one or more NLRIs, each NLRI includes a length field and an NLRI value field, and the specific content of the NLRI value may be determined according to a combination of the AFI field and the SAFI field.

[0147] The NLRI information field includes a route type field, a length field, and a type specific value field, wherein the route type field is used to indicate the route type, the length field is the length of the type specific value field, and the type specific value field is used to carry a value related to the type corresponding to the route type field.

[0148] The BGP route refresh message can include multiple messages, one of which is the basic BGP route refresh message, which is used to dynamically request the BGP route publisher to republish the update message for route update. The message format of the basic BGP route refresh message complies with the format of the Route-REFRESH Message (type 5) defined in the request for comments (RFC) 2918. Another is the BGP ORF message mentioned below, and another is the SPD message mentioned below. Among them, the "basic" in the basic BGP route refresh message is used to distinguish the Route-REFRESH Message defined in RFC2918 from other BGP route refresh messages that are extended on the basis of the Route-REFRESH Message defined in RFC2918.

[0149] In one example, the structure of a BGP route refresh message may be as follows: Figure 1c As shown, Figure 1c A schematic diagram of the structure of a BGP refresh message provided in an embodiment of the present application. Figure 1c As shown, the BGP refresh message includes a BGP message header, an AFI field, a reserved field, and a SAFI field.

[0150] The AFI field is used to carry address family information;

[0151] The SAFI field is used to carry sub-address value information;

[0152] The subtype field can be used to identify the specific message type of the BGP route refresh message.

[0153] In one example, the reserved field can be extended to a subtype field. For example, RFC7313 Figure 1c The BGP refresh message shown in FIG. 1 is extended to expand the reserved field to a subtype field, and the Figure 1d The BGP routerefresh message shown is Figure 1d The BGP route refresh message shown may also be called an enhanced BGP route refresh message.

[0154] The subtype field can be understood in conjunction with Table 3.

[0155] Table 3

[0156]

[0157] Regarding BGP ORF messages, it is necessary to explain:

[0158] RFC5291 and RFC5292 specify the prefix-based ORF capability of BGP, which can send the prefix-based ingress policy configured by the local device to the BGP neighbor through the route refresh message. The BGP neighbor constructs the egress policy based on these policies and filters the routes when sending them. This not only prevents the local device from receiving a large number of useless routes and reduces the utilization rate of the central processing unit (CPU) of the local device, but also effectively reduces the configuration work of BGP neighbors and reduces the occupancy rate of link bandwidth. For example: communication device A and communication device B establish a direct BGP neighbor relationship. After communication device A and communication device B negotiate the prefix-based ORF capability, communication device A sends the locally configured prefix-based ingress policy to communication device B through the route refresh message. Communication device B constructs the egress policy based on the received route refresh message. Communication device A only receives the routes it needs, and communication device B does not have to maintain the routing policy, which reduces the configuration work.

[0159] 2. BGP LS

[0160] BGP-LS is a way to collect network topology, which can make topology collection simpler and more efficient.

[0161] Based on the original BGP, BGP-LS introduces a series of new NLRs to carry information about links, nodes, and IPv4 prefixes or IPv6 prefixes. This new NLRI is called link-state NLRI. In an example, BGP-LS uses the MP_REACH_NLRI attribute as a container for link-state NLRI, that is, the link-state NLRI is carried in the BGP Update message as an MP_REACH_NLRI attribute. Figure 1e , Figure 1e A schematic diagram of the structure of a link state NLRI provided in an embodiment of the present application. Figure 1e As shown, the link state NLRI includes an NLRI type field, a total NLRI length field and a link-state NLRI field.

[0162] The NLRI type field is used to indicate the NLRI type, which can be understood by referring to the following Table 4;

[0163] The total NLRI length field indicates the length of the entire NLRI;

[0164] The link-state NLRI field is used to carry specific content. The content of the link-state NLRI field is determined according to the value of the NLRI type field.

[0165] Table 4

[0166] NLRI Type Value Link-State NLRI Type 1 Node NLRI 2 Link NLRI 3 IPv4 Topology Prefix NLRI 4 IPv6 Topology Prefix NLRI

[0167] 3. BMP

[0168] BMP can monitor the BGP operation status of devices in the network in real time, including the establishment and termination of peer relationships, routing information refresh, etc. Before BMP was implemented, the BGP operation status of devices could only be obtained through manual query, which was inefficient; after BMP was implemented, devices could report their operation status information to the monitoring server through the connection with the monitoring server, greatly improving the efficiency of network monitoring.

[0169] The monitored device establishes a TCP connection with the control and management device (such as a monitoring server). The monitoring server does not need to send any instructions to the monitored device. The monitored device will send BGP operation status information to the monitoring server. The monitoring server parses the received BGP message and presents it in the monitoring view.

[0170] BMP messages include initialization messages, peer up notification (PU) messages, route monitoring (RM) messages, peer down notification (PD) messages, status statistics (SR) messages, termination messages, route mirroring messages, and route policy and attribute trace (ROFT) messages. The above-mentioned BMP messages can be understood in conjunction with the following Table 5.

[0171] Table 5

[0172]

[0173] In an example, the structure of a BMP message can refer to Figure 1f To understand, Figure 1f A schematic diagram of the structure of a BMP message provided in an embodiment of the present application. Figure 1f As shown, the BMP message includes: a BMP common header, a per-peer header, and a PDU.

[0174] The BMP common header includes a version field, a message length field, and a message type field. The version field indicates the BMP version; the message length field indicates the length of the BMP message; and the message type field indicates the message type.

[0175] For the structure of the per-peer header, please refer to the relevant description of RFC7854, which is not described in detail here. The monitoring server can distinguish which BGP neighbor the BMP message comes from based on the per-peer header in the BMP message.

[0176] The PDU is related to the specific type of the BMP message. For example, when the BMP message is a PU message, the PDU is a BMPPeerUp Notification PDU; when the BMP message is a RM message, the PDU is a BGP Update PDU; etc., which will not be described in detail here.

[0177] 4.DSAV:

[0178] Currently, the communication device can use the distributed source address verification DSAV solution to verify the source address of the traffic. For example, a SAV table entry can be configured on the communication device, and the communication device verifies the source address of the traffic based on the configured SAV table entry. For another example, in one example, the communication device can generate a SAV table entry based on a SPA message and an SPD message. Among them:

[0179] The SPA message is used to trigger the communication device to establish a corresponding relationship between a router ID and a source prefix. The SPA message can be carried by a BGPupdate message.

[0180] The SPD message is used to determine the legal inbound interface of the traffic corresponding to the router ID, and further obtain the SAV table entry based on the correspondence between the router ID and the source prefix, wherein the SAV table entry includes the correspondence between the legal inbound interface and the source prefix.

[0181] The SPD message can be carried by the BGP router refresh message. When the value of the SAFI field in the BGP route refresh message is source address validation networks (SAVNET), the SAFI field of the BGP Route-Refresh message will carry the SPD TLV. Figure 2a , Figure 2a A schematic diagram of the structure of an SPD message provided in an embodiment of the present application. Figure 2a As shown, the SPD message includes: Figure 1c The BGP message header, AFI field, subtype field, SAFI field, and SPDTLV field are shown.

[0182] The SPDTLV field may include: a type field, a subtype field, a length field, a sequence number field, an origin router-id field, an optional data length field, an optional data field, and a destination list field.

[0183] Origin router-id is used to carry the router-id of the communication device that sends the SPD message;

[0184] The Dest List field can carry one or more target router-ids, and the communication device corresponding to the destination router-id generates a corresponding SAV table entry based on the SPD message;

[0185] The other fields in the SPD TLV are not described in detail here.

[0186] As described above, the length of the SPD message is also greater than 23 bytes. For a certain communication device, if it supports BGP ORF capability, it cannot support the announcement or reception of SPD messages. If it supports the announcement or reception of SPD messages, it cannot support BGP ORF capability, because both SPD messages and BGP ORF messages are carried by BGP router refresh messages, and the message lengths of both are greater than 23 bytes. If the communication device supports BGP ORF capability and the announcement or reception of SPD messages at the same time, it cannot correctly parse whether the BGProuter refresh message it processes is a BGP ORF message or an SPD message.

[0187] Can be combined Figure 2bThe scenario shown introduces the implementation method of generating SAV table entries based on SPA messages and SPD messages. Figure 2b A schematic diagram of an exemplary application scenario provided for an embodiment of the present application.

[0188] like Figure 2b As shown, subnet 1 is connected to communication device A, and subnet 1 has prefix P1. Communication device A can notify source prefix P1 to communication devices B, C and D respectively through SPA message. Accordingly, communication devices B, C and D can all save the correspondence between routerID of communication device A and source prefix P1.

[0189] Furthermore, the communication device A can send an SPD message to the communication devices B, C, and D along the real forwarding path of the traffic. As shown in FIG2 , the communication device A can send an SPD message 1 to the communication devices B and C through the outgoing interface a1, and send an SPD message 2 to the communication device D through the outgoing interface a2. The Origin router-id in the SPD message 1 and the SPD message 2 both include the router ID of the communication device A.

[0190] The Dest List field of the SPD message 1 includes the router ID of the communication device B and the router ID of the communication device C. The communication device B receives the SPD message 1 through the interface b1, and then searches for the correspondence between the router ID of the communication device A and the source prefix P1 stored locally according to the router ID of the communication device A included in the SPD message 1, obtains the source prefix P1, and further obtains the SAV table entry shown in the following Table 6.

[0191] Table 6

[0192] Legal input interface Source Prefix b1 P1

[0193] Further, the communication device B may delete the router ID of the communication device B in the Dest List field in the SPD message 1 to obtain the SPD message 1', and send the SPD message 1' to the communication device C through the interface b2.

[0194] Similarly, communication device C receives SPD message 1' through interface c1, and then searches for the correspondence between the router ID of communication device A and source prefix P1 stored locally according to the Originrouter-id of SPD message 1', obtains source prefix P1, and further obtains the SAV table entry shown in Table 7 below. Since the Dest List field of SPD message 1' no longer includes other router IDs except the router ID of communication device C, SPD message 1' terminates at communication device C.

[0195] Table 7

[0196] Legal input interface Source Prefix c1 P1

[0197] The Dest List field of SPD message 2 includes the router ID of communication device D. Communication device D receives SPD message 2 through interface d1, and then searches for the correspondence between the router ID of communication device A and source prefix P1 stored locally according to the Origin router-id of SPD message 2, obtains source prefix P1, and further obtains the SAV table entry shown in the following Table 8. Since the Dest List field of SPD message 2 no longer includes other router IDs except the router ID of communication device D, SPD message 2 terminates at communication device D.

[0198] Table 8

[0199] Legal input interface Source Prefix d1 P1

[0200] However, the reliability of the current communication device using SAV table entries to verify the source address cannot be guaranteed. In one example, the SAV table entries are generated by the communication device itself, and there are no relevant monitoring measures, so it cannot be guaranteed that the SAV table entries used by the communication device for source address verification have not been tampered with. In another example, when the communication device performs source address verification based on multiple SAV table entries at the same time, it is impossible to determine whether there is a conflict between multiple types of SAV table entries.

[0201] In order to solve the above problems, the embodiments of the present application provide an information processing method and device, which can improve the reliability of the communication device using the SAV table entry to verify the source address.

[0202] The communication device mentioned in the embodiments of the present application may be a network device such as a switch or a router, or may be a component of a network device, such as a single board or a line card on the network device, or may be a functional module on the network device, or may be a chip for implementing the method of the present application, which is not specifically limited in the embodiments of the present application. The communication devices may be directly connected, for example, via an Ethernet cable or an optical cable, but are not limited thereto.

[0203] See also Figure 3 , which is a schematic diagram of an exemplary application scenario provided in an embodiment of the present application.

[0204] like Figure 3As shown, the control management device can monitor the operating status of the provider edge device (provider edge, PE) and the provider backbone device (provider, P) in the network 100. The network 100 mentioned here can be, for example, a provider backbone network. In an embodiment of the present application, the control management device can monitor the SAV table entries used by the communication device for source address verification, thereby improving the reliability of the communication device using the SAV table entries for source address verification.

[0205] See also Figure 4 , which is a flow chart of an information processing method provided in an embodiment of the present application. Figure 4 The information processing method 100 shown can be applied to a control and management device. The control and management device mentioned in the embodiment of the present application can be, for example, a device running a network management system (NMS), or a controller. The control and management device can be a functional module that implements control and / or management functions, or a physical entity that runs relevant functional modules. The above-mentioned physical entity can be, for example, a server with relevant software installed, and the relevant software is used to implement the functions of the control and management entity. The embodiments of the present application are not specifically limited. In a specific example, the control and management entity can be the monitoring server mentioned above.

[0206] The communication device in the following method 100 may correspond to Figure 3 PE or P as shown.

[0207] In one example, the method 100 may include the following S101 - S102 .

[0208] S101: The control management device obtains at least one SAV table entry 1 used by the communication device 1 to perform source address verification.

[0209] In one example, when S101 is implemented, the control management device may generate the at least one SAV table entry 1. As a specific example, the control management device may perform the following steps A1-A2 to generate the at least one SAV table entry 1.

[0210] A1: Receive BMP message 1 sent by communication device 1, where BMP message 1 includes SPD message 1, and SPD message 1 includes SPD message 2 received by communication device 1 and interface information of communication device 1 receiving SPD message 2.

[0211] As can be seen from the previous description of the BMP message, the BMP message 1 includes a common header. In an embodiment of the present application, the message type field of the common header indicates that the BMP message 1 includes a BGP route refresh message 1. In a specific example, the message type field in the common header of the BMP message 1 is used to indicate a new BMP message type. For example, the newly added BMP message type is: BMPRRM. BMP RRM is used by a communication device to report BGP route refresh messages received and / or sent by the communication device to a control and management device. In this case, the PDU of the BMP message 1 may include a BMP RRM message, and the BMP RRM message includes a BGP route refresh message 1. In a specific example, the BMP message 1 may include a BMP route refresh monitoringPDU1, and the BMP route refresh monitoringPDU1 is used to carry the BGP route refresh message 1. In an example, the BGP route refresh message 1 may include indication information 1, and the indication information 1 is used to indicate that the BGP route refresh message 1 is the SPD message 1.

[0212] In one example, when BGP route refresh message 1 uses Figure 1d In the structure shown, the indication information 1 may be the subtype field of the BGP route refresh message 1. As can be seen from the previous description of the subtype field of the BGP route refresh message, the current subtype field values ​​3-254 are not allocated, so a value may be selected from the values ​​3-254 to indicate an SPD message. For example, when the value of the subtype field of the BGP route refresh message 1 is 3, it indicates that the BGP route refresh message 1 is an SPD message 1. In this case, even if the communication device 1 also supports the BGPORF capability, it can be determined that the BGP route refresh message 1 is an SPD message 1 based on the subtype field.

[0213] In another example, the indication information 1 may be a length field of the BGP route refresh message 1. For example, when the communication device 1 does not enable the BGP ORF capability, the indication information 1 may be a length field of the BGP route refresh message 1. When the length of the BGP route refresh message 1 is greater than 23, it indicates that the BGP route refresh message 1 is an SPD message 1.

[0214] In an example, the SPD message 1 may include an SPD message 2 and TLV1, where the TLV1 is used to carry the interface information.

[0215] A2: Generate the at least one SAV table entry 1 according to the SPD message 1.

[0216] After the control and management device receives the SPD message 1, it can generate at least one SAV table entry 1 based on the SPD message 1. Specifically, the control and management device 1 can generate the at least one SAV table entry based on the SPA message reported by the communication device 1 and the SPD message 1. The specific implementation of the control and management device generating at least one SAV table entry 1 based on the SPD message 1 and the SPA message is the same as the way in which the communication device 1 generates the SAV table entry based on the SPA message and the SPD message. Therefore, regarding the specific implementation of the control and management device 1 generating the at least one SAV table entry based on the SPA message reported by the communication device 1 and the SPD message 1, you can refer to the description part of the communication device generating the SAV table entry based on the SPA message and the SPD message in the previous text, and no repeated description will be made here.

[0217] In one example, the SPD message 1 may also include verification mode information 1, and the verification mode information 1 is used to indicate the verification mode adopted by the communication device 1 to verify the source address based on the at least one SAV table entry, so as to facilitate the control management device to determine the verification mode corresponding to the at least one generated SAV table entry 1. In one example, the SPD message 1 may include TLV2, and the TLV2 is used to carry the verification mode information 1. The TLV2 mentioned here and the aforementioned TLV1 may be the same TLV or different TLVs, and the embodiments of the present application do not make specific limitations.

[0218] In an embodiment of the present application, the verification mode may include a whitelist verification mode, a blacklist verification mode, or a graylist verification mode.

[0219] in:

[0220] Whitelist verification mode means: blocking any data packets with unknown or illegal source addresses from reaching this interface. For example: 10 known SAV entries are set on interface 1, and the verification mode of these 10 SAV entries is set to whitelist verification mode. Data packets entering interface 1 will only be allowed to pass if the source address is within the range of these 10 SAV entries.

[0221] Blacklist verification mode means: blocking packets with known illegal source addresses from reaching this interface, and packets with unknown source addresses are accepted in this mode. For example: 10 known SAV entries are set on interface 2, and the verification mode of these 10 SAV entries is set to blacklist verification mode. When the source address of the packets entering interface 2 is within the range of these 10 SAV entries, they are not allowed to pass.

[0222] Greylist verification mode means: only packets with "known source addresses but illegal arrival interfaces" are discarded, and packets with unknown source addresses are accepted in this mode. This mode saves SAV table entries with prefixes as indexes, and each prefix carries a list of interfaces that allow or do not allow traffic to pass through. For example: for prefix 1, do not allow traffic to pass through interfaces 3, 4, and 5; for prefix 3, do not allow traffic to pass through interfaces 6, 7, and 8; after the device receives a data packet, if its source address is in the prefix 1 range, check whether its inbound interface is 3, 4, or 5. If so, do not allow the traffic to continue to be forwarded. If not, allow the traffic to continue to be forwarded.

[0223] In another example, when S101 is specifically implemented, the control management device may receive a BGP LS message 1 from a communication device 1, and the BGP LS message 1 includes the at least one SAV table item 1. In this case, there is no need to use a manual collection method, and the communication device 1 may report the at least one SAV table item 1 through a BGP LS message to realize automatic reporting of the SAV table item.

[0224] As can be seen from the previous description of the BGP LS message, the BGP LS message 1 includes an NLRI. In one example, the NLRI includes prefix TLVs corresponding to the respective entries in the at least one first SAV table entry, and each prefix TLV is used to carry the source prefix in the table entry corresponding to the prefix TLV. In one example, the NLRI in the BGP message 1 can be a newly defined link state NLRI, for example, the NLRI can be a BGP LS SAVNET Prefix NLRI. See Figure 5a To understand, Figure 5a A schematic diagram of the structure of a BGP LS SAVNET Prefix NLRI provided in an embodiment of the present application. Figure 5a As shown, the BGP LSSAVNET Prefix NLRI includes: a protocol identifier (Protocol-ID) field, an identifier (identifier) ​​field, a local node descriptor (Local Node Descriptors) TLV field and a SAVNET prefix description (Prefix Descriptors) TLVs field. Among them:

[0225] The Protocol-ID field is used to identify the protocol, such as intermediate system to intermediate system (IS-IS), open shortest path first (OSPF), OSPF version 3 (OSPFv3), and BGP.

[0226] The Identifier field is used to identify different protocol instances when running IS-IS, OSPF multi-instance, and OSPFv3 multi-instance.

[0227] The Local Node Descriptors TLV consists of a series of node descriptor sub-TLVs and carries information about the local node. This field is optional.

[0228] The SAVNET Prefix Descriptors TLVs are composed of a series of SAVNET prefix descriptor sub-TLVs. At least one of the prefix TLVs may correspond to a SAVNET prefix descriptor sub-TLV.

[0229] In one example, the prefix TLV may also include verification mode information 2, and the verification mode information 2 is used to indicate the verification mode adopted by the communication device 1 to verify the source address based on the table item corresponding to the prefix TLV, so as to facilitate the control management device to determine the verification mode corresponding to the at least one SAV table item 1. Regarding the verification mode, please refer to the relevant description part of the previous text, and no repeated description is made here. In one example, considering that there may be multiple types of SAV table items used by the communication device 1 for source address verification, the prefix TLV may include indication information indicating the type corresponding to the SAV table item 1 corresponding to the prefix TLV. In a specific example, the type field of the prefix TLV can be used to indicate the table item type of the SAV table item corresponding to the prefix TLV.

[0230] The entry types of the SAV entry may be understood in conjunction with the following Table 9, which shows several possible entry types.

[0231] Regarding the prefix TLV, you can combine Figure 5b To understand, Figure 5b A schematic diagram of the structure of a prefix TLV provided in an embodiment of the present application. Figure 5b As shown, the prefix TLV includes: a type field, a length field, a prefix length field, an IP prefix field and a mode field. Among them:

[0232] The type field may be used to indicate the entry type of the SAV entry corresponding to the prefix TIV; the entry type and the value of the type field may be understood in conjunction with the following Table 9.

[0233] The length field indicates the length of the prefix TLV;

[0234] The prefix length field indicates the length of the IP prefix field;

[0235] The IP prefix field is used to carry the source prefix;

[0236] The mode field is used to carry the verification mode corresponding to the SAV table entry corresponding to the prefix TIV.

[0237] Table 9

[0238]

[0239] In Table 9 above, BAR-SAV refers to source address verification using Border Gateway Protocol update messages, Autonomous System Provider Authorization, and Route Origin Authorization, where BAR is the abbreviation of BGP update message, Autonomous System Provider Authorization (ASPA), and Route Origin Authorization (ROA).

[0240] In an example, the BGP LS message 1 may include an interface TLV, and the interface TLV is used to carry the inbound interface information in the at least one SAV table entry 1. Figure 5c To understand, Figure 5c This is a schematic diagram of the structure of an interface TLV provided in an embodiment of the present application. Figure 5c As shown, the interface TLV includes: a type field, a length field, and an interface information field. Among them:

[0241] The type field indicates the type of the interface TLV;

[0242] The length field indicates the length of the interface TLV;

[0243] The interface information field is used to carry interface information, which includes but is not limited to: one or more of an interface identifier (ID), an interface name (name), an interface tag (tag), and an interface group (group) to which the interface belongs.

[0244] In one example, the interface TLV may be carried by the NLRI of the aforementioned BGP LS message 1, that is, both the aforementioned prefix TLV and the interface TLV are carried by the NLRI of the BGP LS message 1. In another example, the interface TLV may be carried by the BGP path attribute in the BGP LS message 1, for example, by extending a new BGP path attribute to carry the interface TLV, or by using an existing BGP path attribute to carry the interface TLV.

[0245] In another example, the BGP LS message 1 may not include the interface TLV. In this case, the at least one SAV table entry 1 may be applicable to all interfaces of the communication device 1 .

[0246] S102: Control the management device to save the at least one SAV table entry 1.

[0247] After the control management device acquires the at least one SAV table entry 1, the at least one SAV table entry 1 may be saved. For example, the at least one SAV table entry 1 may be saved locally.

[0248] In one example, if the at least one SAV table entry is an entry generated by the control management device based on the SPD message 1. Then in one example, the control management device can also obtain at least one SAV table entry 2 generated by the communication device 1 based on the aforementioned SPD message 2. For example, the control management device can collect the at least one SAV table entry 2 manually. For another example, the control management device can receive a BGP LS message 2 sent by the communication device 1, and the BGP LS message 2 includes the at least one SAV table entry 2. Regarding the BGP LS message 2, reference can be made to the description of the BGP LS message 1 in the previous text, and no repeated description is made here. After the control management device obtains the at least one SAV message 2, the consistency of the at least one SAV table entry 1 and the at least one SAV table entry 2 can be verified. As a specific example, the control management device can compare the at least one SAV table entry 1 with the at least one SAV table entry 2 to determine whether the at least one SAV table entry 1 and the at least one SAV table entry 2 are consistent. If they are consistent, it can be considered that there is no abnormality in the SAV table entry 2 used by the communication device 1 to perform source address verification. If they are inconsistent, the control and management device can, for example, output an alarm message to prompt the operation and maintenance personnel to investigate the cause of the inconsistency between the at least one SAV table entry 1 and the at least one SAV table entry 2, thereby improving network security.

[0249] In another example, if the at least one SAV table entry is reported to the control and management device by the communication device 1 through the BGP LS message 1, the control and management device can also verify whether there is a conflict between different types of entries when the at least one SAV table entry includes multiple types of entries. For example, for different types of SAV table entries 1 including the same source prefix, verify whether there is a conflict in their legal input interfaces. In one example, if there is no conflict between the different types of entries, it can be considered that there is no abnormality in the SAV table entry 1 used by the communication device 1 for source address verification. If there is a conflict between the different types of entries, the control and management device can, for example, output an alarm message to prompt the operation and maintenance personnel to investigate the cause of the conflict in the at least one SAV table entry 1, thereby improving network security.

[0250] From the above description, it can be seen that by utilizing this solution, the control management device monitors the SAV table entries used by the communication device 1 for source address verification, thereby improving the reliability of the SAV table entries used by the communication device 1 for source address verification, and correspondingly, improving the reliability of the communication device 1 for source address verification based on the SAV table entries.

[0251] In one example, the control management device may also receive a BMP message 2 sent by the communication device 2, wherein the BMP message 2 includes a basic BGP route refresh message exchanged between the communication device 2 and the communication device 3, and the basic BGP route refresh message is used to exchange route update requests between the communication device 2 and the communication device 3. In this way, the basic BGP route refresh message exchanged between the communication device 2 and the communication device 3 can be monitored.

[0252] The basic BGP route refresh message mentioned here may be a basic BGP route refresh message sent by communication device 2 to communication device 3, or a basic BGP route refresh message sent by communication device 3 to communication device 2, and the embodiment of the present application does not make any specific limitation.

[0253] In one example, the communication device 2 mentioned here and the aforementioned communication device 1 may be the same communication device. In another example, the communication device 2 and the aforementioned communication device 1 may also be different communication devices.

[0254] In one example, BMP message 2 includes a common header. In an embodiment of the present application, the message type field of the common header of the BMP message 2 indicates that the BMP message 2 includes a BGP route refresh message 2. In a specific example, the message type field in the common header of the BMP message 2 is used to indicate a new BMP message type, for example, the newly added BMP message type is: BMPRRM. BMP RRM is used by a communication device to report a BGP route refresh message received and / or sent by the communication device to a control and management device. In this case, the PDU of the BMP message 2 may include a BMP RRM message, and the BMP RRM message includes a BGP route refresh message 2. In a specific example, the BMP message 2 may include a BMP route refresh monitoringPDU2, and the BMP route refresh monitoringPDU2 is used to carry the BGP route refresh message 2. In an example, the BGP route refresh message 2 may include indication information 2, and the indication information 2 is used to indicate that the BGP route refresh message 2 is the basicBGP route refresh message. In an example, the indication information 2 may be the length field of the BGP route refresh message 2. When the length of the BGP route refresh message 2 is 23, it indicates that the BGP route refresh message 1 is a basic BGP route refresh message.

[0255] In one example, the control and management device can determine, based on the BMP message 2, that the reason why a large number of BGP update messages are exchanged between the communication device 2 and the communication device 3 is that the communication device 2 actively requests the communication device 3 to update the route, or the communication device 3 actively requests the communication device 2 to update the route, rather than the large number of BGP update messages being exchanged between the communication device 2 and the communication device 3 due to network fluctuations.

[0256] In one example, the control management device may also receive a BMP message 3 sent by the communication device 4, wherein the BMP message 3 includes an ORF message exchanged between the communication device 4 and the communication device 5. In this way, the ORF message exchanged between the communication device 4 and the communication device 5 may be monitored.

[0257] The BGP ORF message mentioned here may be a BGP ORF message sent by the communication device 4 to the communication device 5, or may be a BGP ORF message sent by the communication device 5 to the communication device 4, and this embodiment of the present application does not make any specific limitation.

[0258] In one example, the communication device 4 mentioned here and the aforementioned communication device 1 may be the same communication device. In another example, the communication device 4 and the aforementioned communication device 1 may also be different communication devices.

[0259] In one example, the BMP message 3 includes a common header. In an embodiment of the present application, the message type field of the common header of the BMP message 3 indicates that the BMP message 3 includes a BGP route refresh message 3. In a specific example, the message type field in the common header of the BMP message 3 is used to indicate a new BMP message type. For example, the newly added BMP message type is: BMPRRM. BMP RRM is used by a communication device to report BGP route refresh messages received and / or sent by the communication device to a control and management device. In this case, the PDU of the BMP message 3 may include a BMP RRM message, and the BMP RRM message includes a BGP route refresh message 3. In a specific example, the BMP message 3 may include a BMP route refresh monitoringPDU3, and the BMP route refresh monitoringPDU3 is used to carry the BGP route refresh message 3. In an example, the BGP route refresh message 3 may include indication information 3, and the indication information 3 is used to indicate that the BGP route refresh message 3 is the BGPORF message.

[0260] In one example, when the BGP route refresh message 3 uses Figure 1dIn the structure shown, the indication information 3 may be a subtype field of the BGP route refresh message 3. As can be seen from the previous description of the subtype field of the BGP route refresh message, the current subtype field values ​​3-254 are not allocated, so a value may be selected from the values ​​3-254 to indicate an ORF message. For example, when the value of the subtype field of the BGP route refresh message 3 is 4, it indicates that the BGP route refresh message 3 is an ORF message. In this case, even if the communication device 4 also supports announcing or receiving SPD messages, it can be determined that the BGP route refresh message 3 is an ORF message based on the subtype field.

[0261] In another example, the indication information 3 may be a length field of the BGP route refresh message 3. For example, when the communication device 4 does not support announcing or receiving an SPD message, the indication information 3 may be a length field of the BGP route refresh message 3. When the length of the BGP route refresh message 3 is greater than 23, it indicates that the BGP route refresh message 1 is an ORF message.

[0262] In one example, the control and management device can also locate the reason why the number of routing prefixes sent by the communication device 4 and the number of routing prefixes received by the fifth communication device are inconsistent based on the ORF message. For example: Communication device 5 notifies communication device 4 of the aforementioned ORF message, and the ORF message carries the prefix-based ingress policy configured by the communication device 5. Communication device 4 configures a prefix-based egress policy based on the ingress policy. Before executing the egress policy, communication device 4 notifies 1000 routing prefixes to at least one communication device including communication device 5 through a BGP update message in a packaged manner. In addition, communication device 4 reports the BGPupdate message including the notification of the 1000 routing prefixes to the control and management device. Therefore, the control and management device determines that communication device 4 notifies communication device 5 of 1000 routing prefixes. Based on its ingress strategy, the communication device 5 receives 800 routing prefixes out of the aforementioned 1000 routing prefixes, and reports the BGP update message including the 800 routing prefixes to the control management device, so the control management device determines that the communication device 5 receives the 800 routing prefixes announced by the communication device 4. That is, the control management device determines that the number of routing prefixes sent by the communication device 4 is inconsistent with the number of routing prefixes received by the communication device 5.

[0263] In traditional technology, the control and management device cannot locate the reason why the number of routing prefixes sent by the communication device 4 and the number of routing prefixes received by the communication device 5 are inconsistent. After using this solution, after the control and management device receives the BMP message 3 reported by the communication device 4, it can determine based on the ORF message included in the BMP message 3 that the reason for the inconsistency between the number of routing prefixes sent by the communication device 4 and the number of routing prefixes received by the communication device 5 is: the communication device 5 is configured with a prefix-based entry policy, which filters out some of the routing prefixes announced by the communication device 4 to the communication device 5.

[0264] See also Figure 6a , which is a flow chart of an information processing method provided in an embodiment of the present application.

[0265] Figure 6a The information processing method 200 shown can be applied to a control management device to execute the steps executed by the control management device in the above method 100. In an example, the method 200 can include the following S201-S202.

[0266] S201: Acquire at least one first source address verification SAV table entry used by a first communication device to perform source address verification.

[0267] S202: Save the at least one first SAV table entry.

[0268] The first communication device in method 200 may correspond to the communication device 1 in method 100 ; the first SAV table entry in method 200 may correspond to the SAV table entry 1 in method 100 .

[0269] In one possible implementation, obtaining at least one first source address verification SAV table entry used by the first communication device to perform source address verification includes: receiving a first Border Gateway Protocol Monitoring Protocol BMP message sent by the first communication device, the first BMP message including a first Source Path Discovery SPD message, the first SPD message including a second SPD message received by the first communication device and interface information of the first communication device receiving the second SPD message; generating the at least one first SAV table entry according to the first SPD message.

[0270] The first BMP message in method 200 may correspond to BMP message 1 in method 100 ; the first SPD message in method 200 may correspond to SPD message 1 in method 100 ; and the second SPD message in method 200 may correspond to SPD message 2 in method 100 .

[0271] In a possible implementation, the message type field in the common header of the first BMP message indicates that the first BMP message includes a first BGP route refresh message, the first BGP route refresh message includes first indication information, and the first indication information indicates that the first BGP route refresh message is the first SPD message.

[0272] The first BGP route refresh message in method 200 may correspond to the BGP route refresh message 1 in method 100 ; the first indication information in method 200 may correspond to the indication information 1 in method 100 .

[0273] In a possible implementation manner, the first indication information is a subtype field of the first BGP route refresh message.

[0274] In a possible implementation, the first SPD message further includes first verification mode information, where the first verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the at least one first SAV table entry.

[0275] The first verification mode information in method 200 may correspond to the verification mode information 1 in method 100 .

[0276] In a possible implementation, the method further includes: acquiring at least one second SAV table entry generated by the first communication device based on the second SPD message; and performing consistency verification on the at least one first SAV table entry and the at least one second SAV table entry.

[0277] The second SAV table entry in method 200 may correspond to SAV table entry 2 in method 100 .

[0278] In one possible implementation, the method also includes: receiving a second BMP message sent by a second communication device, the second BMP message including a basic BGP route refresh message exchanged between the second communication device and a third communication device, the basic BGP route refresh message being used to exchange route update requests between the second communication device and the third communication device.

[0279] The second BMP message in method 200 may correspond to BMP message 2 in method 100 ; the second communication device in method 200 may correspond to communication device 2 in method 100 ; and the third communication device in method 200 may correspond to communication device 3 in method 100 .

[0280] In one possible implementation, the message type field in the common header of the second BMP message indicates that the second BMP message includes a second BGP route refresh message, the second BGP route refresh message includes second indication information, and the second indication information indicates that the second BGP route refresh message is the basicBGP route refresh message.

[0281] The second BGP route refresh message in method 200 may correspond to the BGP route refresh message 2 in method 100 ; the second indication information in method 200 may correspond to the indication information 2 in method 100 .

[0282] In a possible implementation manner, the method further includes: receiving a third BMP message sent by a fourth communication device, wherein the third BMP message includes an egress routing filter ORF message exchanged between the fourth communication device and the fifth communication device.

[0283] The third BMP message in method 200 may correspond to BMP message 3 in method 100 ; the fourth communication device in method 200 may correspond to communication device 4 in method 100 ; and the fifth communication device in method 200 may correspond to communication device 5 in method 100 .

[0284] In one possible implementation, the message type field in the common header of the third BMP message indicates that the third BMP message includes a third BGP route refresh message, the third BGP route refresh message includes third indication information, and the third indication information indicates that the third BGP route refresh message is the ORF message.

[0285] The third BGP route refresh message in method 200 may correspond to the BGP route refresh message 3 in method 100 ; the third indication information in method 200 may correspond to the indication information 3 in method 100 .

[0286] In a possible implementation manner, the method further includes: locating, according to the ORF message, a reason why the number of routing prefixes sent by the fourth communication apparatus and the number of routing prefixes received by the fifth communication apparatus are inconsistent.

[0287] In a possible implementation, obtaining at least one first source address verification SAV table entry used by the first communication device for source address verification includes: receiving a BGP link state LS message from the first communication device, wherein the BGP LS message includes the at least one first SAV table entry.

[0288] The BGP LS message in method 200 may correspond to BGP LS message 1 in method 100 .

[0289] In one possible implementation, the BGP LS message includes network layer reachability information NLRI, the NLRI includes prefix type length value TLVs corresponding to each entry in the at least one first SAV table entry, and each prefix TLV is used to carry the source prefix in the entry corresponding to the prefix TLV.

[0290] In a possible implementation manner, the prefix TLV further includes second verification mode information, where the second verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the table entry corresponding to the prefix TLV.

[0291] The second verification mode information in method 200 may correspond to the verification mode information 2 in method 100 .

[0292] In a possible implementation manner, the type field of the prefix TLV indicates the entry type of the entry corresponding to the prefix TLV.

[0293] In a possible implementation manner, the BGP LS message further includes an interface TLV, where the interface TLV is used to carry the inbound interface information in the at least one first SAV table entry.

[0294] In a possible implementation manner, the interface TLV is carried by the NLRI or BGP path attribute.

[0295] In a possible implementation, the method further includes:

[0296] In the case that the at least one first SAV entry includes entries of multiple types, it is verified whether there is a conflict between entries of different types.

[0297] See also Figure 6b , which is a flow chart of another information processing method provided in an embodiment of the present application.

[0298] Figure 6bThe information processing method 300 shown can be applied to a first communication device to execute the steps executed by the communication device in the above method 100. In an example, the method 300 can include the following S301-S302.

[0299] S301: Obtain a Border Gateway Protocol Monitoring Protocol (BMP) message, where the BMP message includes a BGP route refresh message exchanged between the first communication device and the second communication device.

[0300] S302: Send the BMP message to the control management device.

[0301] In one example, the first communication device in method 300 may correspond to communication device 1 in method 100, and accordingly, the BMP message in method 200 may correspond to BMP message 1 in method 100, and the BGP routerefresh message in method 300 may correspond to BGP route refresh message 1 in method 100.

[0302] In one example, the first communication device in method 300 may correspond to communication device 2 in method 100, and accordingly, the BMP message in method 200 may correspond to BMP message 2 in method 100, and the BGP routerefresh message in method 300 may correspond to BGP route refresh message 2 in method 100.

[0303] In one example, the first communication device in method 300 may correspond to the communication device 4 in method 100, and accordingly, the BMP message in method 200 may correspond to the BMP message 3 in method 100, and the BGP routerefresh message in method 300 may correspond to the BGP route refresh message 3 in method 100.

[0304] In a possible implementation, when the first communication device in the method 300 corresponds to the communication device 1 in the method 100, the BGP route refresh message is a first source path discovery SPD message, and the first SPD message includes a second SPD message received by the first communication device and interface information of the first communication device receiving the second SPD message.

[0305] The first SPD message in method 300 may correspond to SPD message 1 in method 100 ; the second SPD message in method 300 may correspond to SPD message 2 in method 100 .

[0306] In a possible implementation, the message type field in the common header of the BMP message indicates that the BMP message includes the BGP route refresh message, and the BGP route refresh message includes first indication information, and the first indication information indicates that the BGP route refresh message is the first SPD message.

[0307] The first indication information in method 300 may correspond to indication information 1 in method 100 .

[0308] In a possible implementation manner, the first indication information is a subtype field of the first BGP route refresh message.

[0309] In a possible implementation, the first SPD message further includes first verification mode information, where the first verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the at least one first SAV table entry.

[0310] The first verification mode information in method 300 may correspond to the verification mode information 1 in method 100 .

[0311] In a possible implementation, when the first communication device in the method 300 corresponds to the communication device 2 in the method 100, the BGP route refresh message is a basic BGP route refresh message, and the basic BGP route refresh message is used to exchange route update requests between the first communication device and the second communication device.

[0312] The second communication device in method 300 may correspond to the communication device 2 in method 100 .

[0313] In a possible implementation, the message type field in the common header of the BMP message indicates that the BMP message includes the BGP route refresh message, the BGP route refresh message includes second indication information, and the second indication information indicates that the BGP route refresh message is the basic BGP route refresh message.

[0314] The second indication information in method 300 may correspond to indication information 2 in method 100 .

[0315] In a possible implementation, when the first communication device in the method 300 may correspond to the communication device 4 in the method 100, the BGP route refresh message is an egress route filtering ORF message.

[0316] In a possible implementation, the message type field in the common header of the BMP message indicates that the BMP message includes the BGP route refresh message, the BGP route refresh message includes third indication information, and the third indication information indicates that the BGP route refresh message is the ORF message.

[0317] The third indication information in method 300 may correspond to indication information 3 in method 100 .

[0318] See also Figure 6c , which is a flow chart of another information processing method provided in an embodiment of the present application.

[0319] Figure 6c The information processing method 400 shown can be applied to a first communication device to execute the steps executed by the communication device 1 in the above method 100. In an example, the method 400 can include the following S401-S402.

[0320] S401: Obtain a BGP link state LS message, wherein the BGP LS message includes at least one source address verification SAV table entry used by the first communication device to perform source address verification.

[0321] S402: Send the BGP LS message to the control management device.

[0322] The BGP LS message in method 400 may correspond to BGP LS message 1 in method 100 .

[0323] The SAV table entry in method 400 may correspond to the first SAV table entry in method 100 .

[0324] In a possible implementation, the BGP LS message includes network layer reachability information NLRI, the NLRI includes prefix type length value TLVs corresponding to each entry in the at least one SAV table entry, each prefix TLV is used to carry the source prefix in the entry corresponding to the prefix TLV.

[0325] In a possible implementation manner, the prefix TLV further includes verification mode information, where the verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the table entry corresponding to the prefix TLV.

[0326] In a possible implementation manner, the type field of the prefix TLV indicates the entry type of the entry corresponding to the prefix TLV.

[0327] In a possible implementation manner, the BGP LS message further includes an interface TLV, where the interface TLV is used to carry the inbound interface information in the at least one SAV table entry.

[0328] In a possible implementation manner, the interface TLV is carried by the NLRI or BGP path attribute.

[0329] See also Figure 6d , which is a flow chart of another information processing method provided in an embodiment of the present application.

[0330] Figure 6d The information processing method 500 shown can be applied to a first communication device to execute the steps executed by the communication device 1 in the above method 100. In an example, the method 500 can include the following S501-S502.

[0331] S501: Obtain a Border Gateway Protocol Monitoring Protocol (BMP) message, where the BMP message includes: a first source path discovery (SPD) message received by the first communication device and interface information of the first communication device receiving the first SPD message.

[0332] S502: Send the BMP message to the control management device.

[0333] The BMP message in method 500 may correspond to the BMP message 1 in method 100 ; the first SPD message in method 500 may correspond to the SPD message 2 in method 100 .

[0334] In a possible implementation, the BMP message includes a BGP route refresh message, the BGP route refresh message is a second SPD message, and the second SPD message includes the first SPD message received by the first communication device and interface information of the first communication device receiving the first SPD message.

[0335] The BGP route refresh message in method 500 may correspond to the BGP route refresh message 1 in method 100 ; the second SPD message in method 500 may correspond to the SPD message 1 in method 100 .

[0336] See also Figure 6e , which is a flow chart of another information processing method provided in an embodiment of the present application.

[0337] Figure 6e The information processing method 600 shown can be applied to a first communication device to execute the steps executed by the communication device 2 in the above method 100. In an example, the method 600 can include the following S601-S602.

[0338] S601: Obtain a Border Gateway Protocol Monitoring Protocol (BMP) message, wherein the BMP message includes a basic BGP route refresh message for interacting between the first communication device and the second communication device, wherein the basic BGP route refresh message is used to interact with route update requests between the first communication device and the second communication device.

[0339] S602: Send the BMP message to the control management device.

[0340] The BMP message in method 600 may correspond to the BMP message 2 in method 100 ; the second communication device in method 600 may correspond to the communication device 3 in method 100 .

[0341] See also Figure 6f , which is a flow chart of another information processing method provided in an embodiment of the present application.

[0342] Figure 6f The information processing method 700 shown can be applied to a first communication device to execute the steps executed by the communication device 4 in the above method 100. In an example, the method 700 can include the following S701-S702.

[0343] S701: Obtain a Border Gateway Protocol Monitoring Protocol (BMP) message, where the BMP message includes a Border Gateway Protocol Outbound Routing Filter (BGP ORF) message exchanged between the first communication device and the second communication device.

[0344] S702: Send the BMP message to the control management device.

[0345] The BMP message in method 700 may correspond to the BMP message 3 in method 100 ; the second communication device in method 700 may correspond to the communication device 5 in method 100 .

[0346] In a possible implementation, before obtaining the BMP message, the method further includes:

[0347] Receive a BGP route refresh message sent by the second communication device, wherein the subtype field of the BGP route refresh indicates that the BGP refresh message includes the BGP ORF message; or send a BGP route refresh message to the second communication device, wherein the subtype field of the BGP route refresh indicates that the BGP refresh message includes the BGP ORF message.

[0348] See also Figure 7 , which is a schematic diagram of the structure of a control management device provided in an embodiment of the present application, Figure 7 The control management device 700 shown can be used to execute the information processing method performed by the control management device provided in the above method embodiment.

[0349] In an example, the control management device 700 includes: an acquisition unit 701 and a processing unit 702 .

[0350] The acquisition unit 701 is used to acquire at least one first source address verification SAV table entry used by the first communication device to perform source address verification;

[0351] The processing unit 702 is configured to save the at least one first SAV table entry.

[0352] In one possible implementation, the acquisition unit 701 is used to: receive a first Border Gateway Protocol Monitoring Protocol BMP message sent by the first communication device, the first BMP message including a first Source Path Discovery SPD message, the first SPD message including a second SPD message received by the first communication device and interface information of the first communication device receiving the second SPD message; and generate at least one first SAV table entry according to the first SPD message.

[0353] In a possible implementation, the message type field in the common header of the first BMP message indicates that the first BMP message includes a first BGP route refresh message, the first BGP route refresh message includes first indication information, and the first indication information indicates that the first BGP route refresh message is the first SPD message.

[0354] In a possible implementation manner, the first indication information is a subtype field of the first BGP route refresh message.

[0355] In a possible implementation, the first SPD message further includes first verification mode information, where the first verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the at least one first SAV table entry.

[0356] In a possible implementation, the acquisition unit 701 is further used to: acquire at least one second SAV table entry generated by the first communication device based on the second SPD message; the processing unit 702 is further used to verify the consistency of the at least one first SAV table entry and the at least one second SAV table entry.

[0357] In one possible implementation, the device also includes: a receiving unit, used to receive a second BMP message sent by a second communication device, the second BMP message including a basic BGP route refresh message exchanged between the second communication device and a third communication device, and the basic BGP route refresh message is used to exchange routing update requests between the second communication device and the third communication device.

[0358] In one possible implementation, the message type field in the common header of the second BMP message indicates that the second BMP message includes a second BGP route refresh message, the second BGP route refresh message includes second indication information, and the second indication information indicates that the second BGP route refresh message is the basicBGP route refresh message.

[0359] In a possible implementation, the device includes a receiving unit further configured to: receive a third BMP message sent by a fourth communication device, wherein the third BMP message includes an egress routing filter ORF message exchanged between the fourth communication device and a fifth communication device.

[0360] In one possible implementation, the message type field in the common header of the third BMP message indicates that the third BMP message includes a third BGP route refresh message, the third BGP route refresh message includes third indication information, and the third indication information indicates that the third BGP route refresh message is the ORF message.

[0361] In a possible implementation, the processing unit 702 is further configured to locate, according to the ORF message, a reason why the number of routing prefixes sent by the fourth communication apparatus and the number of routing prefixes received by the fifth communication apparatus are inconsistent.

[0362] In a possible implementation manner, the acquiring unit 701 is configured to: receive a BGP link state LS message from the first communication device, where the BGP LS message includes the at least one first SAV table entry.

[0363] In one possible implementation, the BGP LS message includes network layer reachability information NLRI, the NLRI includes prefix type length value TLVs corresponding to each entry in the at least one first SAV table entry, and each prefix TLV is used to carry the source prefix in the entry corresponding to the prefix TLV.

[0364] In a possible implementation manner, the prefix TLV further includes second verification mode information, where the second verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the table entry corresponding to the prefix TLV.

[0365] In a possible implementation manner, the type field of the prefix TLV indicates the entry type of the entry corresponding to the prefix TLV.

[0366] In a possible implementation manner, the BGP LS message further includes an interface TLV, where the interface TLV is used to carry the inbound interface information in the at least one first SAV table entry.

[0367] In a possible implementation manner, the interface TLV is carried by the NLRI or BGP path attribute.

[0368] In a possible implementation, the processing unit 702 is further configured to:

[0369] In the case that the at least one first SAV entry includes entries of multiple types, it is verified whether there is a conflict between entries of different types.

[0370] See also Figure 8 , which is a schematic diagram of the structure of a communication device provided in an embodiment of the present application, Figure 8 The communication device 800 shown may be used to execute the information processing method 300, 400, 500, 600 or 700 provided by the above method embodiments and performed by the first communication device.

[0371] In an example, the communication device 800 includes: a processing unit 801 and a sending unit 802 .

[0372] In a specific example, when the communication device 800 is used to execute the above method 300:

[0373] The processing unit 801 is used to obtain a Border Gateway Protocol Monitoring Protocol (BMP) message, where the BMP message includes a BGP route refresh message exchanged between the first communication device and the second communication device;

[0374] The sending unit 802 is used to send the BMP message to the control management device.

[0375] In a possible implementation, the BGP route refresh message is a first source path discovery SPD message, and the first SPD message includes a second SPD message received by the first communication device and interface information of the first communication device receiving the second SPD message.

[0376] In a possible implementation, the message type field in the common header of the BMP message indicates that the BMP message includes the BGP route refresh message, and the BGP route refresh message includes first indication information, and the first indication information indicates that the BGP route refresh message is the first SPD message.

[0377] In a possible implementation manner, the first indication information is a subtype field of the first BGP route refresh message.

[0378] In a possible implementation, the first SPD message further includes first verification mode information, where the first verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the at least one first SAV table entry.

[0379] In a possible implementation manner, the BGP route refresh message is a basic BGP route refresh message, and the basic BGP route refresh message is used to exchange route update requests between the first communication device and the second communication device.

[0380] In a possible implementation, the message type field in the common header of the BMP message indicates that the BMP message includes the BGP route refresh message, the BGP route refresh message includes second indication information, and the second indication information indicates that the BGP route refresh message is the basic BGP route refresh message.

[0381] In a possible implementation manner, the BGP route refresh message is an egress route filtering ORF message.

[0382] In a possible implementation, the message type field in the common header of the BMP message indicates that the BMP message includes the BGP route refresh message, the BGP route refresh message includes third indication information, and the third indication information indicates that the BGP route refresh message is the ORF message.

[0383] In yet another specific example, when the communication device 800 is used to execute the above method 400:

[0384] The processing unit 801 is configured to obtain a BGP link state LS message, wherein the BGP LS message includes at least one source address verification SAV table entry used by the first communication device to perform source address verification;

[0385] The sending unit 802 is used to send the BGP LS message to the control management device.

[0386] In a possible implementation, the BGP LS message includes network layer reachability information NLRI, the NLRI includes prefix type length value TLVs corresponding to each entry in the at least one SAV table entry, each prefix TLV is used to carry the source prefix in the entry corresponding to the prefix TLV.

[0387] In a possible implementation manner, the prefix TLV further includes verification mode information, where the verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the table entry corresponding to the prefix TLV.

[0388] In a possible implementation manner, the type field of the prefix TLV indicates the entry type of the entry corresponding to the prefix TLV.

[0389] In a possible implementation manner, the BGP LS message further includes an interface TLV, where the interface TLV is used to carry the inbound interface information in the at least one SAV table entry.

[0390] In a possible implementation, the interface TLV is carried by the NLRI or BGP path attribute. In another specific example, when the communication device 800 is used to execute the above method 500:

[0391] The processing unit 801 is used to obtain a Border Gateway Protocol Monitoring Protocol BMP message, wherein the BMP message includes: a first source path discovery SPD message received by the first communication device and interface information of the first communication device receiving the first SPD message;

[0392] The sending unit 802 is used to send the BMP message to the control management device.

[0393] In a possible implementation, the BMP message includes a BGP route refresh message, the BGP route refresh message is a second SPD message, and the second SPD message includes the first SPD message received by the first communication device and interface information of the first communication device receiving the first SPD message.

[0394] In yet another specific example, when the communication device 800 is used to execute the above method 600:

[0395] The processing unit 801 is used to obtain a Border Gateway Protocol Monitoring Protocol BMP message, wherein the BMP message includes a basic Border Gateway Protocol route refresh basic BGPProute refresh message exchanged between the first communication device and the second communication device, and the basicBGP route refresh message is used to exchange a route update request between the first communication device and the second communication device;

[0396] The sending unit 802 is used to send the BMP message to the control management device.

[0397] In another specific example, when the communication device 800 is used to execute the above method 700:

[0398] The processing unit 801 is used to obtain a Border Gateway Protocol Monitoring Protocol BMP message, wherein the BMP message includes a Border Gateway Protocol Outbound Routing Filtering BGP ORF message exchanged between the first communication device and the second communication device;

[0399] The sending unit 802 is used to send the BMP message to the control management device.

[0400] In a possible implementation manner, the device further includes:

[0401] The receiving unit is used to receive a BGP route refresh message sent by the second communication device before acquiring the BMP message, and the subtype field of the BGP route refresh indicates that the BGP refresh message includes the BGP ORF message.

[0402] In a possible implementation, the sending unit 802 is further configured to send a BGP route refresh message to the second communication device before acquiring the BMP message, and the subtype field of the BGP route refresh indicates that the BGP refresh message includes the BGP ORF message.

[0403] In addition, the present application embodiment also provides a communication device 900, see Fig. 9 As shown, Fig. 9 A schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 900 includes a communication interface 901 and a processor 902 connected to the communication interface 901. The communication device 900 can be used to execute the method 100 or the method 200 or the method 300 or the method 400 or the method 600 or the method 700 in the above embodiments.

[0404] When the communication device 900 is used to execute the above method 100, the communication device 900 is equivalent to the control management device in the method 100, and the communication interface 901 is used to execute the sending and receiving operations executed by the control management device in the method 100. The processor 902 is used to execute operations other than the sending and receiving operations executed by the control management device in the method 100. For example: the communication interface 901 is used to receive at least one SAV table entry 1 used by the communication device 1 for source address verification; the processor 902 is used to save the at least one SAV table entry 1.

[0405] When the communication device 900 is used to execute the above method 200, the communication device 900 is equivalent to the control management device in the method 200, and the communication interface 901 is used to execute the sending and receiving operations executed by the control management device in the method 200. The processor 902 is used to execute operations other than the sending and receiving operations executed by the control management device in the method 200. For example: the communication interface 901 is used to receive at least one first source address verification SAV table item used by the first communication device for source address verification; the processor 902 is used to save the at least one first SAV table item.

[0406] When the communication device 900 is used to execute the above method 300, the communication device 900 is equivalent to the first communication device in the method 300, and the communication interface 901 is used to execute the sending and receiving operations executed by the first communication device in the method 300. The processor 902 is used to execute operations other than the sending and receiving operations executed by the first communication device in the method 300. For example: the processor 902 is used to obtain a Border Gateway Protocol Monitoring Protocol BMP message, and the BMP message includes a BGP route refresh route refresh message exchanged between the first communication device and the second communication device; the communication interface 901 is used to send the BMP message to the control management device.

[0407] When the communication device 900 is used to execute the above method 400, the communication device 900 is equivalent to the first communication device in the method 400, and the communication interface 901 is used to execute the sending and receiving operations executed by the first communication device in the method 400. The processor 902 is used to execute operations other than the sending and receiving operations executed by the first communication device in the method 400. For example: the processor 902 is used to obtain a BGP link state LS message, and the BGP LS message includes at least one source address verification SAV table item used by the first communication device to perform source address verification; the communication interface 901 is used to send the BGP LS message to the control management device.

[0408] When the communication device 900 is used to execute the above method 500, the communication device 900 is equivalent to the first communication device in the method 500, and the communication interface 901 is used to execute the sending and receiving operations executed by the first communication device in the method 500. The processor 902 is used to execute operations other than the sending and receiving operations executed by the first communication device in the method 500. For example: the processor 902 is used to obtain a Border Gateway Protocol Monitoring Protocol BMP message, and the BMP message includes: a first source path discovery SPD message received by the first communication device and interface information of the first communication device receiving the first SPD message; the communication interface 901 is used to send the BMP message to the control management device.

[0409] When the communication device 900 is used to execute the above method 600, the communication device 900 is equivalent to the first communication device in the method 600, and the communication interface 901 is used to execute the sending and receiving operations executed by the first communication device in the method 600. The processor 902 is used to execute operations other than the sending and receiving operations executed by the first communication device in the method 600. For example: the processor 902 is used to obtain a Border Gateway Protocol Monitoring Protocol BMP message, and the BMP message includes a basic Border Gateway Protocol route refresh basic BGP route refresh message exchanged between the first communication device and the second communication device, and the basic BGPProute refresh message is used to exchange route update requests between the first communication device and the second communication device; the communication interface 901 is used to send the BMP message to the control and management device.

[0410] When the communication device 900 is used to execute the above method 700, the communication device 900 is equivalent to the first communication device in the method 700, and the communication interface 901 is used to execute the sending and receiving operations executed by the first communication device in the method 700. The processor 902 is used to execute operations other than the sending and receiving operations executed by the first communication device in the method 700. For example: the processor 902 is used to obtain a Border Gateway Protocol Monitoring Protocol BMP message, and the BMP message includes a Border Gateway Protocol Export Routing Filtering BGP ORF message exchanged between the first communication device and the second communication device; the communication interface 901 is used to send the BMP message to the control management device.

[0411] In addition, the present application embodiment also provides a communication device 1000, see Fig.10 As shown, Fig.10 The communication device 1000 can be used to execute the method 100, 200, 300, 400, 500, 600, or 700 in the above embodiments.

[0412] like Fig.10As shown, the communication device 1000 may include a processor 1010, a memory 1020 coupled to the processor 1010, and a transceiver 1030. The transceiver 1030 may be, for example, a communication interface, an optical module, etc. The processor 1010 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and a NP. The processor may also be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. The processor 1010 may refer to one processor or may include multiple processors. The memory 1020 may include a volatile memory (English: volatile memory), such as a random access memory (English: random-access memory, abbreviated: RAM); the memory may also include a non-volatile memory (English: non-volatile memory), such as a read-only memory (English: read-only memory, abbreviated: ROM), a flash memory (English: flash memory), a hard disk drive (English: hard disk drive, abbreviated: HDD) or a solid-state drive (English: solid-state drive, abbreviated: SSD); the memory 1020 may also include a combination of the above-mentioned types of memories. The memory 1020 may refer to a memory or may include multiple memories. In one embodiment, the memory 1020 stores computer-readable instructions, and the computer-readable instructions include multiple software modules, such as a sending module 1021, a processing module 1022 and a receiving module 1023. After executing each software module, the processor 1010 may perform corresponding operations according to the instructions of each software module. In this embodiment, the operation performed by a software module actually refers to the operation performed by the processor 1010 according to the instructions of the software module.

[0413] When the communication device 1000 is used to execute the above method 100, the communication device 1000 is equivalent to the control management device in the method 100, and the transceiver 1030 is used to execute the transceiver operation executed by the control management device in the method 100. The processor 1010 is used to execute operations other than the transceiver operation executed by the control management device in the method 100. For example: the transceiver 1030 is used to receive at least one SAV table entry 1 used by the communication device 1 for source address verification; the processor 1010 is used to save the at least one SAV table entry 1.

[0414] When the communication device 1000 is used to execute the above method 200, the communication device 1000 is equivalent to the control management device in the method 200, and the transceiver 1030 is used to execute the transceiver operation executed by the control management device in the method 200. The processor 1010 is used to execute operations other than the transceiver operation executed by the control management device in the method 200. For example: the transceiver 1030 is used to receive at least one first source address verification SAV table entry used by the first communication device for source address verification; the processor 1010 is used to save the at least one first SAV table entry.

[0415] When the communication device 1000 is used to execute the above method 300, the communication device 1000 is equivalent to the first communication device in the method 300, and the transceiver 1030 is used to execute the transceiver operation executed by the first communication device in the method 300. The processor 1010 is used to execute operations other than the transceiver operation executed by the first communication device in the method 300. For example: the processor 1010 is used to obtain a Border Gateway Protocol Monitoring Protocol BMP message, and the BMP message includes a BGP route refresh route refresh message exchanged between the first communication device and the second communication device; the transceiver 1030 is used to send the BMP message to the control management device.

[0416] When the communication device 1000 is used to execute the above method 400, the communication device 1000 is equivalent to the first communication device in the method 400, and the transceiver 1030 is used to execute the transceiver operation executed by the first communication device in the method 400. The processor 1010 is used to execute operations other than the transceiver operation executed by the first communication device in the method 400. For example: the processor 1010 is used to obtain a BGP link state LS message, and the BGP LS message includes at least one source address verification SAV table item used by the first communication device to perform source address verification; the transceiver 1030 is used to send the BGP LS message to the control management device.

[0417] When the communication device 1000 is used to execute the above method 500, the communication device 1000 is equivalent to the first communication device in the method 500, and the transceiver 1030 is used to execute the transceiver operation executed by the first communication device in the method 500. The processor 1010 is used to execute operations other than the transceiver operation executed by the first communication device in the method 500. For example: the processor 1010 is used to obtain a Border Gateway Protocol Monitoring Protocol BMP message, and the BMP message includes: a first source path discovery SPD message received by the first communication device and interface information of the first communication device receiving the first SPD message; the transceiver 1030 is used to send the BMP message to the control management device.

[0418] When the communication device 1000 is used to execute the above method 600, the communication device 1000 is equivalent to the first communication device in the method 600, and the transceiver 1030 is used to execute the transceiver operation executed by the first communication device in the method 600. The processor 1010 is used to execute operations other than the transceiver operation executed by the first communication device in the method 600. For example: the processor 1010 is used to obtain a Border Gateway Protocol Monitoring Protocol BMP message, and the BMP message includes a basic Border Gateway Protocol route refresh basic BGP route refresh message exchanged between the first communication device and the second communication device, and the basic BGPProute refresh message is used to exchange route update requests between the first communication device and the second communication device; the transceiver 1030 is used to send the BMP message to the control and management device.

[0419] When the communication device 1000 is used to execute the above method 700, the communication device 1000 is equivalent to the first communication device in the method 700, and the transceiver 1030 is used to execute the transceiver operation executed by the first communication device in the method 700. The processor 1010 is used to execute operations other than the transceiver operation executed by the first communication device in the method 700. For example: the processor 1010 is used to obtain a Border Gateway Protocol Monitoring Protocol BMP message, and the BMP message includes a Border Gateway Protocol Export Routing Filter BGP ORF message exchanged between the first communication device and the second communication device; the transceiver 1030 is used to send the BMP message to the control management device.

[0420] The present application also provides a computer-readable storage medium, in which instructions or computer programs are stored. When the instruction computer program runs on a processor, it can implement any one or more operations of the methods described in the aforementioned embodiments (for example, method 100 or method 200 or method 300 or method 400 or method 500 or method 600 or method 700).

[0421] The present application also provides a computer program product, including a computer program, which, when executed on a processor, can implement any one or more operations of the methods described in the foregoing embodiments (e.g., method 100 or method 200 or method 300 or method 400 or method 500 or method 600 or method 700).

[0422] An embodiment of the present application also provides a communication system for executing the information processing method provided in the above method embodiment.

[0423] In one example, the communication system includes: the control management device in method 100 and the communication apparatus 1 .

[0424] In yet another example, the communication system includes: the control management device in method 100 and the communication apparatus 2 .

[0425] In yet another example, the communication system includes: the control management device in method 100 and the communication apparatus 4 .

[0426] In another example, a control management device that executes the above method 200 and a first communication device that executes any one of the above methods 300 to 700.

[0427] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0428] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0429] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical business division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0430] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0431] In addition, each business unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software business units.

[0432] If the integrated unit is implemented in the form of a software business unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a communication device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0433] Those skilled in the art will appreciate that in one or more of the above examples, the services described in the present invention may be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, the services may be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. Storage media may be any available media that can be accessed by a general-purpose or special-purpose computer.

[0434] The above specific implementation modes further describe the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific implementation modes of the present invention.

[0435] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. An information processing method, characterized in that: Applied to control management equipment, the method comprises: Acquire at least one first source address verification SAV table entry used by the first communication device to perform source address verification; The at least one first SAV table entry is saved.

2. The method according to claim 1, characterized in that The obtaining of at least one first source address verification SAV table entry used by the first communication device for performing source address verification includes: Receive a first Border Gateway Protocol Monitoring Protocol (BMP) message sent by the first communication device, the first BMP message including a first Source Path Discovery (SPD) message, the first SPD message including a second SPD message received by the first communication device and interface information for the first communication device to receive the second SPD message; The at least one first SAV table entry is generated according to the first SPD message.

3. The method according to claim 2, characterized in that The message type field in the common header of the first BMP message indicates that the first BMP message includes a first BGP route refresh message, the first BGP route refresh message includes first indication information, and the first indication information indicates that the first BGP route refresh message is the first SPD message.

4. The method according to claim 3, characterized in that The first indication information is the subtype field of the first BGP routerefresh message.

5. The method according to any one of claims 2 to 4, characterized in that: The first SPD message also includes first verification mode information, where the first verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the at least one first SAV table entry.

6. The method according to any one of claims 2 to 5, characterized in that: The method further comprises: Acquire at least one second SAV table entry generated by the first communication device based on the second SPD message; A consistency verification is performed on the at least one first SAV table entry and the at least one second SAV table entry.

7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: A second BMP message sent by a second communication device is received, wherein the second BMP message includes a basic BGP route refresh message exchanged between the second communication device and a third communication device, wherein the basic BGP route refresh message is used to exchange route update requests between the second communication device and the third communication device.

8. The method according to claim 7, characterized in that The message type field in the common header of the second BMP message indicates that the second BMP message includes a second BGP route refresh message, the second BGP route refresh message includes second indication information, and the second indication information indicates that the second BGP route refresh message is the basic BGP route refresh message.

9. The method according to any one of claims 1 to 8, characterized in that: The method further comprises: A third BMP message sent by a fourth communication device is received, wherein the third BMP message includes an egress routing filter ORF message exchanged between the fourth communication device and a fifth communication device.

10. The method according to claim 9, characterized in that The message type field in the common header of the third BMP message indicates that the third BMP message includes a third BGP route refresh message, the third BGP route refresh message includes third indication information, and the third indication information indicates that the third BGP route refresh message is the ORF message.

11. The method according to claim 9 or 10, characterized in that: The method further comprises: According to the ORF message, the reason why the number of routing prefixes sent by the fourth communication device and the number of routing prefixes received by the fifth communication device are inconsistent is located.

12. The method according to claim 1, characterized in that The obtaining of at least one first source address verification SAV table entry used by the first communication device for performing source address verification includes: A BGP link state LS message is received from the first communication device, wherein the BGP LS message includes the at least one first SAV table entry.

13. The method according to claim 12, characterized in that The BGP LS message includes network layer reachability information NLRI, and the NLRI includes prefix type length value TLVs corresponding to each entry in the at least one first SAV entry, and each prefix TLV is used to carry a source prefix in the entry corresponding to the prefix TLV.

14. The method according to claim 13, characterized in that The prefix TLV also includes second verification mode information, where the second verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the table entry corresponding to the prefix TLV.

15. The method according to claim 13 or 14, characterized in that The type field of the prefix TLV indicates the entry type of the entry corresponding to the prefix TLV.

16. The method according to any one of claims 13 to 15, characterized in that: The BGP LS message also includes an interface TLV, where the interface TLV is used to carry the inbound interface information in the at least one first SAV table entry.

17. The method according to claim 16, characterized in that The interface TLV is carried by the NLRI or BGP path attribute.

18. The method according to any one of claims 13 to 17, characterized in that: The method further comprises: In the case that the at least one first SAV entry includes entries of multiple types, it is verified whether there is a conflict between entries of different types.

19. An information processing method, characterized in that: Applied to a first communication device, the method comprises: Acquire a Border Gateway Protocol Monitoring Protocol (BMP) message, wherein the BMP message includes a BGP route refresh message exchanged between the first communication device and the second communication device; The BMP message is sent to a control management device.

20. The method according to claim 19, characterized in that The BGP route refresh message is a first source path discovery SPD message, and the first SPD message includes a second SPD message received by the first communication device and interface information of the first communication device receiving the second SPD message.

21. The method according to claim 20, characterized in that The message type field in the common header of the BMP message indicates that the BMP message includes the BGP route refresh message, and the BGP route refresh message includes first indication information, and the first indication information indicates that the BGP route refresh message is the first SPD message.

22. The method according to claim 21, characterized in that The first indication information is the subtype field of the first BGProute refresh message.

23. The method according to any one of claims 20 to 22, characterized in that: The first SPD message also includes first verification mode information, where the first verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the at least one first SAV table entry.

24. The method according to claim 19, characterized in that The BGP route refresh message is a basic BGP route refresh message, and the basic BGP route refresh message is used to exchange route update requests between the first communication device and the second communication device.

25. The method according to claim 24, characterized in that The message type field in the common header of the BMP message indicates that the BMP message includes the BGP route refresh message, the BGP route refresh message includes second indication information, and the second indication information indicates that the BGP route refresh message is the basic BGProute refresh message.

26. The method according to claim 19, characterized in that The BGP route refresh message is an egress route filtering ORF message.

27. The method according to claim 26, characterized in that The message type field in the common header of the BMP message indicates that the BMP message includes the BGP route refresh message, the BGP route refresh message includes third indication information, and the third indication information indicates that the BGP route refresh message is the ORF message.

28. An information processing method, characterized in that: Applied to a first communication device, the method comprises: Obtaining a BGP link state LS message, wherein the BGP LS message includes at least one source address verification SAV table entry used by the first communication device to perform source address verification; Send the BGP LS message to the control and management device.

29. The method according to claim 28, characterized in that The BGP LS message includes network layer reachability information NLRI, and the NLRI includes prefix type length value TLVs corresponding to each entry in the at least one SAV entry, and each prefix TLV is used to carry a source prefix in the entry corresponding to the prefix TLV.

30. The method according to claim 29, characterized in that The prefix TLV also includes verification mode information, where the verification mode information indicates a verification mode adopted by the first communication device to verify the source address based on the table entry corresponding to the prefix TLV.

31. The method according to claim 29 or 30, characterized in that The type field of the prefix TLV indicates the entry type of the entry corresponding to the prefix TLV.

32. The method according to any one of claims 29 to 31, characterized in that: The BGP LS message also includes an interface TLV, and the interface TLV is used to carry the inbound interface information in the at least one SAV table entry.

33. The method according to claim 32, characterized in that The interface TLV is carried by the NLRI or BGP path attribute.

34. An information processing device, characterized in that: The device comprises: Transceiver unit and processing unit; The transceiver unit is used to perform the receiving and / or sending operations performed by the control management device as described in any one of claims 1 to 18; the processing unit is used to perform operations other than the receiving and / or sending operations performed by the control management device as described in any one of claims 1 to 18; or, The transceiver unit is used to perform the receiving and / or sending operations performed by the first communication device as described in any one of claims 19-27; the processing unit is used to perform operations other than the receiving and / or sending operations performed by the first communication device as described in any one of claims 19-27; or, The transceiver unit is used to perform the receiving and / or sending operations performed by the first communication device as described in any one of claims 28-33; the processing unit is used to perform operations other than the receiving and / or sending operations performed by the first communication device as described in any one of claims 28-33.

35. An information processing device, characterized in that: include: Processor and memory; The memory is used to store instructions; The processor is used to execute the instructions so that the communication device executes the method described in any one of claims 1-33.

36. A communication system, characterized in that: The system comprises: A control management device for executing the method described in any one of claims 1 to 18 above, and a first communication device for executing the method described in any one of claims 19 to 27 above; or, A control management device for executing the method described in any one of claims 1 to 18, and a first communication device for executing the method described in any one of claims 28 to 33.

37. A computer-readable storage medium, characterized in that: The method comprises instructions or computer programs, which, when executed on a processor, implement the method according to any one of claims 1 to 33.

Images