Information processing method and device
By integrating multiple business relationships and path information, the accuracy of BGP routing verification is enhanced, addressing the limitations of current methods in detecting path hijacking and leakage attacks.
Patent Information
- Application Number
- CN202310666203.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-06-06
- Publication Date
- 2024-12-06
AI Technical Summary
Current methods for security verification of Border Gateway Protocol (BGP) routing information by network devices lack accuracy, particularly in identifying path hijacking and path leakage attacks.
Enhance security verification by incorporating additional business relationships such as customer to provider (C2P), peer to peer (P2P), sibling, partial, and hybrid relationships, along with topological and routing transmission path information, to improve the accuracy of BGP routing verification.
Improves the accuracy of BGP routing verification by enabling network devices to utilize a broader range of relationships and path information, effectively identifying and mitigating path hijacking and leakage attacks.
Smart Images

Figure CN119094144A_ABST
Abstract
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] With the development of network technology, there are more and more attack methods against the network. Border Gateway Protocol (BGP) routing attack is a common attack method used by attackers. Among them, path hijacking attack and path leakage attack are two common BGP routing attack methods.
[0003] In order to reduce BGP routing attacks, network devices can perform security checks on BGP routing information to determine whether there is a BGP routing attack, and when it is determined that there is a BGP routing attack, execute corresponding processing measures to ensure network security.
[0004] However, the current method of performing security verification on BGP routing information by network devices cannot obtain accurate verification results. Therefore, a solution is urgently needed to solve the above problem. Summary of the invention
[0005] The embodiment of the present application provides an information processing method, which can improve the accuracy of the verification results obtained by the network device when performing security verification on BGP routing information.
[0006] In the first aspect, an embodiment of the present application provides an information processing method, which can be applied to a network device. In a specific example, a network device can receive security verification information sent by a server, the security verification information is used to perform security verification on BGP routing information, and the security verification information includes a first business relationship corresponding to a first network domain and a second business relationship corresponding to the first network domain, and the first business relationship is customer to provider (customer toprovider, C2P). After receiving the security verification information, the network device can store the security verification information so as to facilitate subsequent security verification of the BGP routing information based on the security verification information. Since the security verification information includes not only the first business relationship corresponding to the first network domain, but also the second business relationship corresponding to the first network domain, when the network device performs security verification on the BGP routing information, in addition to performing security verification based on the first business relationship corresponding to the first network domain as in the traditional technology, it can also perform security verification based on the second business relationship corresponding to the first network domain, that is, the network device uses more business relationships for security verification of the BGP routing information, and accordingly, the accuracy of the obtained verification result is also improved. Therefore, by utilizing the solution of the embodiments of the present application, the accuracy of the verification results obtained by the network device performing security verification on BGP routing information can be improved.
[0007] In a possible implementation, the network device can also obtain the first BGP routing information. For example, the network device can receive the first BGP routing information from other network devices. And perform security verification on the first BGP routing information according to the security verification information. Since the security verification information includes not only the first business relationship corresponding to the first network domain, but also the second business relationship corresponding to the first network domain, when the network device performs security verification on the first BGP routing information, in addition to performing security verification based on the first business relationship corresponding to the first network domain as in the traditional technology, it can also perform security verification based on the second business relationship corresponding to the first network domain. In other words, the network device uses more business relationships to perform security verification on the first BGP routing information, and accordingly, the accuracy of the verification result obtained is also improved.
[0008] In a possible implementation, considering that when verifying BGP routing information, especially when determining whether path hijacking exists, if the topological relationship of the network domain can be known, the possibility of identifying path hijacking can be effectively improved. Therefore, in one example, the security verification information may also include the topological relationship of the first network domain.
[0009] In a possible implementation, considering the neighbor relationship between network domains, the possibility of identifying path hijacking can be effectively improved. Therefore, the topological relationship of the first network domain can be at least one second network domain that has a neighbor relationship with the first network domain.
[0010] In one possible implementation, in order to further improve the accuracy of security verification of BGP routes, the security verification information may also include a routing transmission path that supports transmission through the first network domain. In this way, when performing security verification on BGP routing information, security verification can be performed in combination with the routing transmission path that supports transmission through the first network domain.
[0011] In a possible implementation, although BGP routing transmission as a whole needs to comply with routing transmission constraints, in some special scenarios, BGP routing information is allowed to be transmitted through paths that violate routing transmission constraints. In order to avoid BGP routing information that is transmitted through legal "violation of routing transmission constraints" failing security verification, in one example, the routing transmission path supported for transmission through the first network domain may be a routing transmission path that does not comply with routing transmission constraints. Among them, a routing transmission path that does not comply with routing transmission constraints may also be referred to as a "valley path," and the two may be used interchangeably.
[0012] In a possible implementation, the second business relationship includes one or more of provider to customer (P2C), peer to peer (P2P), sibling, partial, and hybrid. In this case, when the network device performs security verification on the BGP routing information based on the security verification information, it can not only determine which network domains are the providers of the first network domain, but also determine the customers of the first network domain, or determine which network domains have a P2P business relationship with the first network domain, or determine which network domains have a partial business relationship with the first network domain, or determine which network domains have a hybrid business relationship with the first network domain, thereby improving the accuracy of security verification of BGP routing information.
[0013] In a possible implementation, the network device may actively request the security verification information from a server (e.g., a first server). In a specific example, the network device may send a request message to the server, the request message being used to request information for security verification of BGP routing information. Accordingly, after receiving the request message, the server may return the security verification information to the network device based on the request message.
[0014] In a possible implementation, the network device may request the information it needs from the server on demand. In this case, the request message may include an information type, which indicates the type of information required by the network device for security verification of BGP routing information. In other words, the information type is used to indicate that the server returns information of the information type for security verification of BGP routing information to the network device. For example, if the network device needs business relationship information, the information type may include business relationship; for another example, if the network device needs topology information, the information type may include topology relationship; for another example, if the network device needs valley path information, the information type may include valley path. Accordingly, after receiving the request message, the first server may parse the request message to obtain the information type. Further, the first server may obtain information of the information type for security verification of BGP routing information, and send the obtained security verification information to the network device.
[0015] In a possible implementation, the network device receives the security verification information sent by the server. For example, in a specific implementation, the network device can receive a first protocol data unit (PDU) sent by the server, and the first PDU includes the security verification information. In this way, the first server can send the security verification information to the network device through a PDU, and correspondingly, the network device can obtain the security verification information through a PDU.
[0016] In a possible implementation, the first PDU may include at least one first type length value (TLV) field, and the at least one first TLV field is used to carry the security verification information, wherein one first TLV field is used to carry a type of information in the security verification information. In this case, the network device may parse the at least one first TLV to obtain the security verification information.
[0017] In a possible implementation, the network device receives the security verification information sent by the server, for example, in a specific implementation, the second PDU and the third PDU sent by the server may be received, wherein the second PDU includes the first business relationship, and the third PDU includes other information in the security verification information except the first business relationship. In this case, the format of the second PDU may follow the format of the PDU of the first business relationship sent by the server to the network device in the traditional technology. In this way, there is no need to expand the format of the PDU of the first business relationship sent by the server to the network device.
[0018] In a possible implementation, the third PDU may include at least one second TLV, and the at least one second TLV is used to carry the other information, wherein one second TLV carries a type of information in the other information. In this case, the network device may parse the at least one second TLV to obtain the other information in the security verification information.
[0019] In a second aspect, an embodiment of the present application provides an information processing method, which can be applied to a first server. In a specific example, the first server can obtain security verification information, and the security verification information is used to perform security verification on BGP routing information, and the security verification information includes a first business relationship corresponding to a first network domain and a second business relationship corresponding to the first network domain, and the first business relationship is C2P. After the first server obtains the security verification information, it can send the security verification information to a network device, so that the network device can perform security verification on the BGP routing information based on the security verification information. Since the security verification information includes not only the first business relationship corresponding to the first network domain, but also the second business relationship corresponding to the first network domain, when the network device performs security verification on the BGP routing information, in addition to performing security verification based on the first business relationship corresponding to the first network domain as in the traditional technology, it can also perform security verification based on the second business relationship corresponding to the first network domain, that is, the network device uses more business relationships for security verification of the BGP routing information, and accordingly, the accuracy of the verification result obtained is also improved. Therefore, by using the solution of the embodiment of the present application, the accuracy of the verification result obtained by the network device performing security verification on the BGP routing information can be improved.
[0020] In a possible implementation manner, the security verification information further includes: a topological relationship of the first network domain, and / or a routing transmission path that supports transmission through the first network domain.
[0021] In a possible implementation manner, the topological relationship includes: at least one second network domain having a neighbor relationship with the first network domain.
[0022] In a possible implementation manner, the supporting the routing transmission path transmitted through the first network domain includes: supporting the routing transmission path transmitted through the first network domain and not meeting the routing transmission constraint condition.
[0023] In a possible implementation manner, the second business relationship includes one or more of the following: provider to customer P2C, peer to peer P2P, provider sibling, partial, and hybrid.
[0024] In a possible implementation, the first server may obtain the pre-stored security verification information. In a specific example, the first server may obtain the security verification information through a simplified local internet number resource management (SLURM) file and store the security verification information.
[0025] In a possible implementation, it is considered that there are many servers that can be used to register information for security verification of BGP routing information. In order to synchronize the information registered on each server, the first server can obtain the SLURM file from the second server. In a specific example, the first server can send an information synchronization message to the second server, and the information synchronization message is used to request synchronization of information used for security verification of BGP routing information. After receiving the information synchronization message, the second server can obtain the locally stored SLURM file and send the SLURM file to the first server.
[0026] In a possible implementation, the SLURM file may include a first object, and the first object may be used to carry all the information in the security verification information. In this case, the network device may parse the first object to obtain the security verification information.
[0027] In a possible implementation, the SLURM file may include a second object and a third object, wherein the second object and the third object are used together to carry the security verification information. In other words, the second object and the third object may respectively carry part of the information in the security verification information. In a specific example, the second object may be used to carry the first business relationship, and the third object may be used to carry other information in the security verification information except the first business relationship. In this case, the second object may use the object used to carry the first business relationship in traditional technology. In this way, there is no need to expand and modify the object used to carry the first business relationship in traditional technology.
[0028] In a possible implementation, the method also includes: receiving a request message sent by the network device, the request message being used to request information for performing security verification on BGP routing information; and sending the security verification information to the network device includes: sending the security verification information to the network device according to the request information.
[0029] In one possible implementation, the request message includes an information type, and the information type is used to indicate that the first server returns information of the information type to the network device for security verification of BGP routing information, and accordingly, the security verification information includes information of the information type.
[0030] In a possible implementation manner, sending the security verification information to the network device includes: sending a first protocol data unit PDU to the network device, where the first PDU includes the security verification information.
[0031] In a possible implementation, the first PDU includes at least one first type length value TLV field, and the at least one first TLV field is used to carry the security verification information, wherein one of the first TLV fields is used to carry a type of information in the security verification information.
[0032] In one possible implementation, sending the security verification information to the network device includes: sending a second PDU and a third PDU to the network device, the second PDU including the first business relationship, and the third PDU including other information in the security verification information except the first business relationship.
[0033] In a possible implementation manner, the third PDU includes at least one second TLV, and the at least one second TLV is used to carry the other information, wherein one second TLV carries a type of information in the other information.
[0034] In a third aspect, an embodiment of the present application provides an information processing device, which is applied to a network device, and the device includes: a receiving unit, which is used to receive security verification information sent by a server, and the security verification information is used to perform security verification on Border Gateway Protocol BGP routing information, and the security verification information includes a first business relationship corresponding to a first network domain and a second business relationship corresponding to the first network domain, and the first business relationship is customer to provider C2P; a processing unit, which is used to store the security verification information.
[0035] In a possible implementation, the processing unit is further used to: obtain first BGP routing information; and perform security verification on the first BGP routing information according to the security verification information.
[0036] In a possible implementation manner, the security verification information further includes: a topological relationship of the first network domain, and / or a routing transmission path that supports transmission through the first network domain.
[0037] In a possible implementation manner, the topological relationship of the first network domain includes: at least one second network domain having a neighbor relationship with the first network domain.
[0038] In a possible implementation manner, the supporting the routing transmission path transmitted through the first network domain includes: supporting the routing transmission path transmitted through the first network domain and not meeting the routing transmission constraint condition.
[0039] In a possible implementation manner, the second business relationship includes one or more of the following: provider to customer P2C, peer to peer P2P, provider sibling, partial, and hybrid.
[0040] In one possible implementation, the device also includes: a sending unit, used to send a request message to the server, wherein the request message is used to request information for performing security verification on BGP routing information; and a receiving unit, used to receive the security verification information returned by the server in response to the request message.
[0041] In one possible implementation, the request message includes an information type, and the information type is used to instruct the server to return information of the information type to the network device for security verification of BGP routing information. Accordingly, the security verification information includes information of the information type.
[0042] In a possible implementation manner, the receiving unit is used to: receive a first protocol data unit PDU sent by the server, where the first PDU includes the security verification information.
[0043] In a possible implementation, the first PDU includes at least one first type length value TLV field, and the at least one first TLV field is used to carry the security verification information, wherein one of the first TLV fields is used to carry a type of information in the security verification information.
[0044] In a possible implementation, the receiving unit is used to: receive a second PDU and a third PDU sent by the server, the second PDU includes the first business relationship, and the third PDU includes other information in the security verification information except the first business relationship.
[0045] In a possible implementation manner, the third PDU includes at least one second TLV, and the at least one second TLV is used to carry the other information, wherein one second TLV carries a type of information in the other information.
[0046] In a fourth aspect, an embodiment of the present application provides an information processing device, which is applied to a first server, and the device includes: a processing unit, which is used to obtain security verification information, and the security verification information is used to perform security verification on Border Gateway Protocol BGP routing information, and the security verification information includes a first business relationship corresponding to a first network domain and a second business relationship corresponding to the first network domain, and the first business relationship is customer to provider C2P; a sending unit, which is used to send the security verification information to a network device.
[0047] In a possible implementation manner, the security verification information further includes: a topological relationship of the first network domain, and / or a routing transmission path that supports transmission through the first network domain.
[0048] In a possible implementation manner, the topological relationship includes: at least one second network domain having a neighbor relationship with the first network domain.
[0049] In a possible implementation manner, the supporting the routing transmission path transmitted through the first network domain includes: supporting the routing transmission path transmitted through the first network domain and not meeting the routing transmission constraint condition.
[0050] In a possible implementation manner, the second business relationship includes one or more of the following: provider to customer P2C, peer to peer P2P, provider sibling, partial, and hybrid.
[0051] In a possible implementation, the device also includes: a receiving unit, used to obtain a simplified local Internet number resource management SLURM file corresponding to the first network domain, the SLURM file including the security verification information; the processing unit, further used to store the security verification information.
[0052] In a possible implementation manner, the SLURM file includes a first object, and the first object carries the security verification information.
[0053] In a possible implementation manner, the SLURM file includes a second object and a third object, and the second object and the third object jointly carry the security verification information.
[0054] In a possible implementation manner, the second object carries the first business relationship, and the third object carries other information in the security verification information except the first business relationship.
[0055] In a possible implementation, the sending unit is further used to: send an information synchronization message to the second server, wherein the information synchronization message is used to request synchronization of information used to perform security verification on BGP routing information; and the receiving unit is used to: receive a SLURM file corresponding to the first network domain sent by the second server.
[0056] In a possible implementation, the receiving unit included in the apparatus is further used to: receive a request message sent by the network device, the request message being used to request information for performing security verification on BGP routing information; and the sending unit is used to: send the security verification information to the network device based on the request information.
[0057] In one possible implementation, the request message includes an information type, and the information type is used to indicate that the first server returns information of the information type to the network device for security verification of BGP routing information, and accordingly, the security verification information includes information of the information type.
[0058] In a possible implementation manner, the sending unit is used to: send a first protocol data unit PDU to the network device, where the first PDU includes the security verification information.
[0059] In a possible implementation, the first PDU includes at least one first type length value TLV field, and the at least one first TLV field is used to carry the security verification information, wherein one of the first TLV fields is used to carry a type of information in the security verification information.
[0060] In a possible implementation, the sending unit is used to send a second PDU and a third PDU to the network device, wherein the second PDU includes the first business relationship, and the third PDU includes other information in the security verification information except the first business relationship.
[0061] In a possible implementation manner, the third PDU includes at least one second TLV, and the at least one second TLV is used to carry the other information, wherein one second TLV carries a type of information in the other information.
[0062] In a fifth aspect, an embodiment of the present application provides a device. The device includes a processor and a memory. The memory is used to store instructions or computer programs. The processor is used to execute the instructions or computer programs in the memory, execute any one of the methods described in the first aspect above, or execute any one of the methods described in the second aspect above.
[0063] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, including instructions or a computer program, which, when executed on a computer, enables the computer to execute any of the methods described in the first aspect above, or execute any of the methods described in the second aspect above.
[0064] In the seventh aspect, an embodiment of the present application provides a computer program product comprising instructions or a computer program, which, when executed on a computer, enables the computer to execute any method described in the first aspect above, or execute any method described in the second aspect above.
[0065] In an eighth aspect, an embodiment of the present application provides a communication system, comprising: a network device for executing the method described in any one of the first aspect above, and a controller for executing the method described in any one of the second aspect above. BRIEF DESCRIPTION OF THE DRAWINGS
[0066] 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 ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0067] Figure 1a A schematic diagram of an exemplary network architecture provided for an embodiment of the present application;
[0068] Figure 1b A schematic diagram of the structure of a PDU provided in an embodiment of the present application;
[0069] Figure 2a A schematic diagram of an exemplary application scenario provided for an embodiment of the present application;
[0070] Figure 2b A schematic diagram of another exemplary application scenario provided for an embodiment of the present application;
[0071] Figure 2c A schematic diagram of another exemplary application scenario provided for an embodiment of the present application;
[0072] Figure 2d A schematic diagram of another exemplary application scenario provided for an embodiment of the present application;
[0073] Figure 2e A schematic diagram of another exemplary application scenario provided for an embodiment of the present application;
[0074] Figure 2f A schematic diagram of another exemplary application scenario provided for an embodiment of the present application;
[0075] Figure 3 A signaling interaction diagram of an information processing method provided in an embodiment of the present application;
[0076] Figure 4a A schematic diagram of the structure of a first PDU provided in an embodiment of the present application;
[0077] Figure 4b A schematic diagram of the structure of a third PDU provided in an embodiment of the present application;
[0078] Figure 5 A schematic diagram of the structure of an information processing device provided in an embodiment of the present application;
[0079] Figure 6 A schematic diagram of the structure of another information processing device provided in an embodiment of the present application;
[0080] Figure 7 A schematic diagram of the structure of a device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0081] The embodiments of the present application provide an information processing method and apparatus, which can improve the accuracy of verification results obtained by a network device performing security verification on BGP routing information.
[0082] BGP routing attack is a common attack method used by attackers. By using BGP routing attack, the attackers can achieve attack effects such as traffic eavesdropping, sending attack messages to maliciously occupy network resources, etc.
[0083] In order to reduce BGP routing attacks, the BGP routing can be security-verified through the autonomous system (AS) path included in the BGP routing information. The AS path is used to indicate the AS path that the BGP routing passes through during transmission. According to the AS path, the ASs that the BGP routing passes through in sequence during transmission can be determined. Specifically, when transmitting, the BGP routing needs to meet the routing transmission constraints. The routing transmission constraints mentioned here can be the Valley-Free principle. The Valley-Free principle stipulates the conditions that the business relationships that the BGP routing passes through during transmission must meet.
[0084] The business relationships mentioned in the embodiments of the present application may include: P2C, P2P, C2P, sibling, partial and hybrid.
[0085] Sibling is a special business relationship. When the business relationship between two network domains is sibling, the two network domains are each other's providers. In an example, when the business relationship between network domain 1 and network domain 2 is sibling, network domain 1 can continue to transmit BGP routing information received through any business relationship to network domain 2.
[0086] Partial is also a special business relationship. The BGP routes received by a network device from a neighbor with which it has a partial business relationship can be passed to the customer or peer of the network device, but cannot be passed to the provider of the network device. The business relationship between network devices refers to the business relationship between the network domains to which the network devices belong. For example, network device 1 belongs to network domain 1, and network device 2 belongs to network domain 2. The business relationship between network devices 1 and 2 refers to the business relationship between network domain 1 and network domain 2.
[0087] Hybrid is also a special business relationship. Two network domains with a hybrid relationship have different business relationships in different geographical locations. For example, in region 1, network domain 1 is the provider of network domain 2, and in region 2, network domain 2 is the provider of network domain 1.
[0088] In the scenario where the routing server participates in BGP routing transmission, C2P can also be from client to routing server, and P2C can be from routing server to client.
[0089] For the various business relationships, please refer to request for comments (RFC) 7908 and RFC9234 and the relevant description parts in "https: / / datatracker.ietf.org / doc / html / draft-shen-sidrops-regionalized-as-relationships-02", which will not be described in detail here.
[0090] As the name implies, the no-valley principle can be understood as the transmission path that BGP routing information experiences during transmission cannot have a "valley". Specifically, when BGP routing information is transmitted along C2P, the transmission path of the BGP routing information includes an upstream path, which can be likened to an uphill slope. When BGP routing information is transmitted along P2C, the transmission path of the BGP routing information includes a downstream path, which can be likened to a downhill slope. When BGP routing is transmitted along P2P, the transmission path of the BGP routing can be likened to transmission on a flat road.
[0091] Therefore, in an example, the no-valley principle may include, for example, the routing transmission principle shown in Table 1 below:
[0092] Table 1
[0093] to customer to peer to provider from customer allow allow allow from peer allow Not allowed Not allowed from provider allow Not allowed Not allowed from sibling allow allow allow from partial allow allow Not allowed
[0094] According to Table 1, the no-valley principle can include the following five constraints:
[0095] 1. The BGP routing information received by the network device from the customer network domain of the network domain to which it belongs can be transmitted to the customer network domain, peer network domain and provider network domain of the network domain to which it belongs. Among them, the BGP routing information received by the network device from the customer network domain of the network domain to which it belongs can also be understood as the BGP routing information received by the network device through the business relationship C2P. In other words, the BGP routing information received by the network device through the business relationship C2P can continue to be transmitted through the business relationships P2C, P2P and C2P.
[0096] 2. The BGP routing information received by the network device from the peer network domain of the network domain to which it belongs can only be transmitted to the customer network domain of the network domain to which it belongs. Among them, the BGP routing information received by the network device from the peer network domain of the network domain to which it belongs can be understood as the BGP routing information received by the network device through the business relationship P2P. In other words, the BGP routing information received by the network device through the business relationship P2P can only be further transmitted through the business relationship P2C.
[0097] 3. The BGP routing information received by the network device from the provider network domain of the network domain to which it belongs can only be transmitted to the customer network domain of the network domain to which it belongs. Among them, the BGP routing information received by the network device from the provider network domain of the network domain to which it belongs can also be understood as the BGP routing information received by the network device through the business relationship C2P. In other words, the BGP routing information received by the network device through the business relationship P2C can only be further transmitted through the business relationship P2C.
[0098] 4. The BGP routing information received by the network device from the sibling network domain of the network domain to which it belongs can be transmitted to the customer network domain, peer network domain and provider network domain of the network domain to which it belongs. Among them, the BGP routing information received by the network device from the sibling network domain of the network domain to which it belongs can also be understood as the BGP routing information received by the network device through the business relationship sibling network domain. In other words, the BGP routing information received by the network device through the business relationship sibling can continue to be transmitted through the business relationship P2C, P2P and C2P.
[0099] 5. The BGP routing information received by the network device from the partial network domain of the network domain to which it belongs can only be transmitted to the customer network domain and peer network domain of the network domain to which it belongs. Among them, the BGP routing information received by the network device from the partial network domain of the network domain to which it belongs can also be understood as the BGP routing information received by the network device partially through the business relationship. In other words, the BGP routing received by the network device partially through the business relationship can continue to be transmitted through the business relationship P2C and P2P.
[0100] At present, when a network device performs security verification on BGP routing information, it can perform security verification in combination with the first business relationship corresponding to the network domain, wherein the first business relationship is C2P. In a specific example, the network device can obtain the first business relationship of the first network domain, that is, determine which provider network domains the first network domain has, and then perform security verification on the AS path in the BGP routing information according to the first business relationship of the first network domain to determine whether the business relationship experienced by the BGP routing information during the transmission process meets the aforementioned no-valley principle, thereby obtaining the verification result of the security verification of the BGP routing information.
[0101] In one example, once the BGP routing information has experienced a business relationship other than C2P during the transmission process, it can be considered that the BGP routing information has flipped. For example, if the business relationship experienced by the BGP routing information changes from C2P to P2C, the BGP routing information has flipped; for another example, if the business relationship experienced by the BGP routing information changes from C2P to P2P, the BGP routing information has flipped; for another example, if the business relationship experienced by the BGP routing information at the beginning of transmission is P2C or P2P, the BGP routing information has flipped. Once the BGP routing information has flipped, the BGP routing information can only continue to be transmitted through P2C, because once it is transmitted along other business relationships, it will cause a "valley" in the transmission path experienced by the BGP routing information during the transmission process, thereby violating the no-valley principle.
[0102] The network domain mentioned in the embodiments of the present application may be an AS.
[0103] In one example, refer to Figure 1a To understand, Figure 1aA schematic diagram of an exemplary network architecture provided for an embodiment of the present application. A first business relationship corresponding to a network domain may be registered to a server 100. After the server 100 obtains the first business relationship corresponding to the network domain, the first business relationship may be stored and sent to a network device 200, so that the network device 200 can verify the BGP routing information based on the first business relationship. In one example, the server 100 may be a relay party (RP) server. In one example, the network device 200 may be a boundary device of a network domain. For example, the network device 200 may be an autonomous system boundary router (ASBR).
[0104] In one example, the first business relationship corresponding to the network domain may be registered to the server 100 via SLURM, where SLURM is a mechanism for operating registration data on the server 100 .
[0105] It should be noted that SLURM can not only be used to register the first business relationship corresponding to the network domain, but can also be used for operations on other data, which will not be explained in detail here.
[0106] Next, the first business relationship of registering a network domain using SLURM is described in conjunction with the format of the SLURM file.
[0107]
[0108] In the above example, the content after the characters " / / " is a comment.
[0109] In an example, the server 100 may send the first business relationship registered in the network domain to the network device 200 by using the Resource Public Key Infrastructure to Router Protocol (RTR) protocol.
[0110] The RTR protocol supports many types of messages. In the embodiment of the present application, the message based on the RTR protocol is called PDU. Each PDU has a corresponding type. The type value corresponding to the PDU used to carry the first business relationship is 11. Figure 1b , the format of the PDU used to carry the aforementioned first business relationship is introduced.
[0111] Figure 1b A schematic diagram of the structure of a PDU provided in an embodiment of the present application.
[0112] like Figure 1bAs shown, the PDU includes: a protocol version field, a PDU Type field, a zero field, a length field, a flags field, an address family identifier (AFI) flags field, a Provider AS count field, a Customer Autonomous System Number field, and a Provider Autonomous System Numbers field. Among them:
[0113] The Protocol Version field is used to carry the protocol version number of the RTR;
[0114] PDU Type is used to carry the PDU type. The value of this field can be 11.
[0115] The Zero field is an all-zero field;
[0116] The Length field is used to carry the PDU length, indicating the byte length of the entire PDU including the Length field itself;
[0117] The Flags field has a total of 8 bits. The least significant bit indicates whether the PDU is an announcement PDU or a withdrawal PDU.
[0118] The AFI Flags field has 8 bits in total. The least significant bit indicates whether the business relationship information is for IPv4 or IPv6. The Provider AS count field is used to carry the number of registered provider ASs.
[0119] Customer Autonomous System Number is used to carry the AS number of the customer AS and is also the AS number of the AS that registers the first business relationship;
[0120] Provider Autonomous System Numbers is used to carry the numbers of all registered provider ASs.
[0121] It should be noted that Figure 1a This is only for the convenience of understanding the present solution and does not constitute a limitation on the embodiments of the present application. Figure 1a Only one server and one network device are shown, but in actual applications, the number of servers that can be used to register the first business relationship is not limited to Figure 1aIn addition, a server may also send the first business relationship to multiple network devices. For example, in addition to sending the first business relationship to network device 200, server 100 may also send it to other network devices.
[0122] In one example, when the AS Path is security verified based on the first business relationship, the verification process may include upstream verification and downstream verification. In a specific example, if the network device receives BGP routing information through the business relationship C2P, upstream verification is performed; if the network device receives BGP routing information through the business relationship P2C, downstream verification is performed. When performing upstream verification, if any transmission path in the AS path is C2P, that is, uphill, the verification is passed; otherwise, the verification is not passed. When performing downstream verification, the transmission path indicated by the AS path may include an uphill section and a downhill section, and the length of the uphill and downhill sections is equal to the length of the transmission path indicated by the entire AS path, the verification is passed; otherwise, the verification is not passed. For details about upstream verification and downstream verification, please refer to the relevant description in "BGP AS_PATH Verification Based on Autonomous System ProviderAuthorization (ASPA) Objects", which will not be repeated here.
[0123] At present, when the network device performs security verification on the AS path based on the first business relationship, the verification result obtained may not be accurate. For example, it is impossible to determine whether the transmission path experienced by the BGP routing information during the transmission process complies with the no-valley principle; for another example, if it is determined that the transmission path experienced by the BGP routing information during the transmission process does not comply with the no-valley principle, it is impossible to distinguish whether it is path hijacking or path leakage. Figure 2a to Figure 2f Provide explanation.
[0124] See also Figure 2a , Figure 2a A schematic diagram of an exemplary application scenario provided for an embodiment of the present application.
[0125] like Figure 2aAs shown, AS X receives BGP routing information from AS 2, and the AS path corresponding to the BGP routing information is [AS1, AS2]. AS X is the provider of AS2, so after receiving the BGP routing information from AS 2, the network device (such as the border device) in AS X can perform upstream verification on the AS path [AS1, AS2], and according to the first business relationship of AS1, it is determined that AS3 and AS4 are the providers of AS1, and AS2 is not the provider of AS1. Therefore, the network device in AS X can determine that the BGP routing information has not passed the security verification. However, the network device in AS X cannot determine whether the BGP routing information has been leaked or hijacked.
[0126] See also Figure 2b , which is a schematic diagram of another exemplary application scenario provided in an embodiment of the present application.
[0127] like Figure 2b As shown in the figure, there is no real link between AS1 and AS2, or in other words, AS1 and AS2 do not have a neighbor relationship. AS X receives BGP routing information from AS 2, and the AS path corresponding to the BGP routing information is [AS1, AS2]. AS 2 is the provider of ASX, so after the network device in AS X (such as the edge device) receives the BGP routing information from AS 2, it can perform downstream verification on the AS path [AS1, AS2].
[0128] When the network device in AS X performs downstream verification, it determines that AS3 and AS4 are the providers of AS1 and AS2 is not the provider of AS1 based on the first business relationship of AS1. However, it cannot determine whether AS1 and AS2 have other business relationships. Therefore, the network device in AS X can determine AS1 as the uphill segment and AS2 as the downhill segment. Since the uphill segment and the downhill segment cover the entire AS path [AS1, AS2], the network device in AS X can determine that the BGP routing information passes the security verification. However, the verification result is actually inaccurate because AS1 and AS2 do not have a neighbor relationship, and the BGP routing information actually undergoes path hijacking.
[0129] See also Figure 2c , which is a schematic diagram of another exemplary application scenario provided in an embodiment of the present application.
[0130] like Figure 2cAs shown, AS X receives BGP routing information from AS 2, and the AS path corresponding to the BGP routing information is [AS1, AS2]. AS 2 is a customer of AS X. Therefore, after receiving the BGP routing information from AS 2, the network device in AS X (such as the border device) can perform upstream verification on the AS path [AS1, AS2]. The network device in AS X does not obtain the first business relationship of AS1. Moreover, according to the first business relationship of AS2, it is determined that AS1 is not the provider of AS2, but it is impossible to determine whether AS1 and AS2 have other business relationships. Therefore, the verification result obtained by the network device in AS X performing upstream verification is "unknown".
[0131] See also Figure 2d , which is a schematic diagram of another exemplary application scenario provided in an embodiment of the present application.
[0132] like Figure 2d As shown, AS X receives BGP routing information from AS 2, and the AS path corresponding to the BGP routing information is [AS1, AS2]. AS 2 is a customer of AS X. Therefore, after receiving the BGP routing information from AS 2, the network device in AS X (such as the border device) can perform upstream verification on the AS path [AS1, AS2]. The network device in AS X determines that AS1 is the provider of AS2 based on the first business relationship of AS2. Therefore, the network device in AS X determines that the BGP routing information is illegal because AS2 receives the BGP routing information through the business relationship P2C, but continues to transmit it to AS X through the business relationship C2P, which violates the no-valley principle.
[0133] However, in some special scenarios, BGP routing information is allowed to be transmitted through valley paths, for example, Figure 2d In the scenario shown, AS2 is allowed to continue to transmit the BGP routing information from AS1 to AS X. However, in this case, using the traditional security verification method will judge the legal transmission path with valleys as an illegal transmission path, thereby determining that the BGP routing information is illegal, and further, causing abnormal service traffic transmission.
[0134] See also Figure 2e , which is a schematic diagram of another exemplary application scenario provided in an embodiment of the present application.
[0135] like Figure 2eAs shown in the figure, AS X is the provider of AS2. AS X receives BGP routing information from AS 2, and the AS path corresponding to the BGP routing information is [AS1, AS2]. The business relationship between AS1 and AS2 is hybrid. For example, in region 1, the business relationship between AS1 and AS2 is C2P, that is, AS2 is the provider of AS1. In region 1, the business relationship between AS1 and AS2 is P2C, that is, AS1 is the provider of AS2. However, current network devices do not support security verification of AS paths based on hybrid business relationships, which means that network devices in AS X cannot obtain accurate verification results when performing security verification on the AS path [AS1, AS2].
[0136] See also Figure 2f , which is a schematic diagram of another exemplary application scenario provided in an embodiment of the present application.
[0137] like Figure 2f As shown, AS1 transmits BGP routing information to AS2, AS2 transmits BGP routing information to AS3, and AS3 further transmits BGP routing information to AS X. AS X receives BGP routing information from AS 3, and the ASpath corresponding to the BGP routing information is [AS1, AS2, AS3]. The business relationship between AS1 and AS2 is partial, and the business relationship between AS2 and AS3 is C2P. Therefore, the BGP routing information is actually illegal, because the BGP routing information received through the partial business relationship cannot be further transmitted through the C2P business relationship. However, the current network equipment does not support security verification of ASpath based on the partial business relationship, which also causes the network equipment in AS X to be unable to obtain accurate verification results when performing security verification on the AS path [AS1, AS2, AS3]. In an example, when performing security verification, the network equipment in AS X determines that AS2 is not the provider of AS1 based on the first business relationship of AS1, but cannot determine whether there are other business relationships between AS1 and AS2. Therefore, the network device in AS X can determine that the verification result of the BGP routing information is unknown. In another example, AS1 registers its business relationship with AS2 as AS2 and registers AS2 as its own provider. In this case, when performing security verification, the network device in AS X determines that AS2 is the provider of AS1 according to the first business relationship of AS1. Therefore, the network device in AS X can determine that the BGP routing information passes the security verification.
[0138] In order to improve the accuracy of the verification results obtained by the network device performing security verification on BGP routing information, the embodiment of the present application provides an information processing method and device. Next, the information processing method and device provided by the embodiment of the present application are introduced in conjunction with the accompanying drawings.
[0139] See also Figure 3 , this figure is a signaling interaction diagram of an information processing method provided in an embodiment of the present application. Figure 3 The method shown may, for example, include the following S101 - S104 .
[0140] Figure 3 The first server in the method shown may correspond to Figure 1a The server 100 shown, Figure 3 The network device in the method shown, for example, may correspond to Figure 1a The network device 200 is shown.
[0141] S101: The first server obtains security verification information, where the security verification information is used to perform security verification on BGP routing information. The security verification information includes a first business relationship corresponding to a first network domain and a second business relationship corresponding to the first network domain, where the first business relationship is C2P.
[0142] In an embodiment of the present application, the security verification information may include, in addition to the first business relationship, a second business relationship different from the first business relationship. The second business relationship may include one or more of P2C, P2P, sibling, partial, and hybrid. In this way, when performing security verification on the BGP routing information based on the security verification information, not only the first business relationship of the first network domain may be combined, but also the second business relationship of the first network domain may be combined, so that the verification result is more accurate. Regarding the business relationships P2C, P2P, sibling, partial, and hybrid, please refer to the relevant description part of the previous text, and no repeated description will be made here.
[0143] In one example, when verifying BGP routing information, especially when determining whether path hijacking exists, if the topological relationship of the network domain can be known, the possibility of identifying path hijacking can be effectively improved. Figure 2bIn the scenario shown, if the topological relationship of AS1 can be obtained, it can be determined that AS1 and AS2 do not have a neighbor relationship, thereby determining that path hijacking has occurred. Therefore, in one example, the security verification information may also include the topological relationship of the first network domain. In an embodiment of the present application, the topological relationship of the first network domain may, for example, include other network domains that can communicate directly or indirectly with the first network domain. In one example, considering the neighbor relationship between network domains, the possibility of identifying path hijacking can be effectively improved. Therefore, the topological relationship of the first network domain may be at least one second network domain that has a neighbor relationship with the first network domain.
[0144] In one example, in order to further improve the accuracy of security verification of BGP routes, the security verification information may also include a routing transmission path that supports transmission through the first network domain. In this way, when performing security verification on BGP routing information, security verification can be performed in combination with the routing transmission path that supports transmission through the first network domain.
[0145] In one example, the routing transmission path supporting transmission through the first network domain may be a partial path in a path that meets the routing transmission constraint condition. For example, for business routing, according to business requirements, a partial path may be designated as a routing transmission path supporting transmission through the first network domain.
[0146] In another example, although BGP routing transmission as a whole needs to comply with routing transmission constraints, in some special scenarios, BGP routing information is allowed to be transmitted via valley paths. In order to avoid BGP routing information transmitted via a legitimate "valley path" failing security verification, in one example, the routing transmission path supported for transmission through the first network domain may be a routing transmission path that does not comply with routing transmission constraints. In other words, the routing transmission path supported for transmission through the first network domain may be a "valley path."
[0147] In an example, the first server may obtain the pre-stored security verification information. The security verification information may be stored locally on the first server or in a storage device external to the first server, which is not specifically limited in the embodiment of the present application.
[0148] In one example, the first server can obtain a file including the security verification information, parse the file to obtain the security verification information, and further store the security verification information. The embodiment of the present application does not specifically limit the format of the file. The format of the file can be a scripting language object notation (JSON), an extensible markup language (XML), or another markup language (YAML). In the embodiment of the present application, the file is a file in JSON format as an example for explanation. In this case, the file can be a SLURM file. In other words, in an example, the first server can obtain the security verification information through a SLURM file and store the security verification information.
[0149] In a specific example, the SLURM file may be uploaded by a user to the first server. In another example, it is considered that there are many servers that can be used to register information for security verification of BGP routing information. In order to synchronize the information registered on each server, the first server may obtain the SLURM file from the second server. In a specific example, the first server may send an information synchronization message to the second server, and the information synchronization message is used to request synchronization of information used for security verification of BGP routing information. After receiving the information synchronization message, the second server may obtain the locally stored SLURM file and send the SLURM file to the first server. In an example, the second server may, for example, send the SLURM file uploaded by the user to the second server within a certain period of time (for example, the last day) to the first server. The embodiment of the present application does not specifically limit the protocol used for interaction between the first server and the second server. In an example, the first server and the second server may communicate using the Hypertext Transfer Protocol Secure (HTTPS) protocol. In other words, the first server may send an information synchronization message to the second server using HTTP, and accordingly, the second server may send the SLURM file to the first server using HTTP.
[0150] In one example, the SLURM file may include a first object, which may be used to carry all the information in the security verification information. In one example, the first object corresponds to the aspaAssertions mentioned above. Among them, "aspaAssertions" is the object name of the first object. Now, taking the example that the security verification information includes a first business relationship, a second business relationship, at least one second network domain that has a neighbor relationship with the first network domain, and a valley path that supports transmission through the first network domain, the first object is explained.
[0151]
[0152]
[0153] In the above description of the first object, the content after the characters “ / / ” is a comment.
[0154] In another example, the SLURM file may include a second object and a third object, wherein the second object and the third object are used together to carry the security verification information. In other words, the second object and the third object may respectively carry part of the information in the security verification information.
[0155] In one example, the second object may be used to carry the business relationship information in the security verification information, the business relationship information including the first business relationship and the second business relationship. The third object may be used to carry information other than the business relationship information in the security verification information.
[0156] In another example, the second object can be used to carry the first business relationship, and the third object can be used to carry other information in the security verification information except the first business relationship. For this case, the second object can use aspaAssertions in traditional technology. In this way, there is no need to expand and modify the object aspaAssertions. Regarding the third object, the third object is now explained by taking the example that the security verification information includes the first business relationship, the second business relationship, at least one second network domain that has a neighbor relationship with the first network domain, and a valley path that supports transmission through the first network domain.
[0157]
[0158]
[0159] S102: The first server sends the security verification information to the network device.
[0160] After the first server obtains the security verification information, it can send the security verification information to the network device. In one example, the first server can actively send the security verification information to the network device. In another example, the first server can send the security verification information to the network device based on a request message sent by the network device, wherein the request message is used to request information for security verification of BGP routing information. In this case, the first server can also receive the request message sent by the network device before executing S102.
[0161] In one example, the network device may request the information it needs from the first server on demand. In this case, the request message may include an information type, which indicates the type of information required by the network device for security verification of BGP routing information. In other words, the information type is used to indicate that the first server returns the information of the information type for security verification of BGP routing information to the network device. For example, if the network device needs business relationship information, the information type may include business relationship; for another example, if the network device needs topology information, the information type may include topology relationship; for another example, if the network device needs valley path information, the information type may include valley path. Accordingly, after receiving the request message, the first server may parse the request message to obtain the information type. Further, the first server may obtain the information of the information type for security verification of BGP routing information, and send the obtained security verification information to the network device.
[0162] In one example, when S102 is implemented, the first server may send a first PDU to the network device, wherein the first PDU includes the security verification information. That is, the first server may send the security verification information to the network device through a PDU.
[0163] In one example, the first PDU may include at least one first TLV field, and the at least one first TLV field is used to carry the security verification information, wherein one first TLV field is used to carry a type of information in the security verification information. Taking the security verification information including: the first business relationship of the first network domain, the second business relationship of the first network domain, the topological relationship of the first network domain, and the valley path supporting transmission through the first network domain as an example, assuming that the second business relationship includes: P2C, P2P, sibling, partial, and hybrid. Then the first PDU may include 8 first TLVs, which are the first TLV corresponding to the first business relationship, the first TLV corresponding to P2C, the first TLV corresponding to P2P, the first TLV corresponding to sibling, the first TLV corresponding to partial, the first TLV corresponding to hybrid, the first TLV corresponding to the topological relationship, and the first TLV corresponding to the valley path.
[0164] In an example, the value field of the first TLV corresponding to P2C is used to carry the customerAS set of the first network domain, the customerAS set includes the number of at least one customerAS, and the length field of the first TLV corresponding to P2C is used to carry the number of customerAS included in the customerAS set.
[0165] In an example, the value field of the first TLV corresponding to sibling is used to carry the sibling AS set of the first network domain, the sibling AS set includes the number of at least one sibling AS, and the length field of the first TLV corresponding to sibling is used to carry the number of sibling ASs included in the sibling AS set.
[0166] In an example, the value field of the first TLV corresponding to partial is used to carry a partial AS set of the first network domain, the partial AS set includes the number of at least one partial AS, and the length field of the first TLV corresponding to partial is used to carry the number of partial ASs included in the partial AS set.
[0167] In one example, the first TLV corresponding to hybrid may include at least one LV field, one LV field being used to carry information about a network domain that has a hybrid business relationship with the first network domain. For example, the business relationship between the third network domain and the first network domain is hybrid, and the business relationship between the fourth network domain and the first network domain is also hybrid. Then, the first TLV corresponding to the hybrid may include two LV fields, one LV field being used to carry the business relationship between the third network domain and the first network domain, and the other LV field being used to carry the business relationship between the fourth network domain and the first network domain.
[0168] In one example, the value field of the first TLV corresponding to the topological relationship is used to carry a neighbor AS set of the first network domain, the neighbor AS set includes the number of at least one neighbor AS, and the length field of the first TLV corresponding to the topological relationship is used to carry the number of neighbor ASs included in the neighbor AS set.
[0169] In an example, the first TLV corresponding to the valley path may include at least one LV field, where one LV field is used for a valley path that is allowed to be transmitted through the first network domain.
[0170] In an example, the structure of the first PDU may be as follows: Figure 4a As shown, Figure 4a A structural diagram of a first PDU provided in an embodiment of the present application. Figure 4a The PDU shown is in Figure 1b A plurality of first TLVs 410 are extended on the basis of the PDU shown, and are used to carry other information in the security verification information except the first business relationship.
[0171] In another example, when S102 is implemented, the first server may send a second PDU and a third PDU to the network device, wherein the second PDU includes the first business relationship, and the third PDU includes other information in the security verification information except the first business relationship. In this case, the format of the second PDU may follow the format of the PDU of the first business relationship sent by the server to the network device in the traditional technology. In one example, the format of the second PDU may refer to Figure 1b shown.
[0172] In one example, the third PDU may include at least one second TLV, and the at least one second TLV is used to carry the other information, wherein one of the second TLVs carries a type of information in the other information. In one example, the format of the third PDU may be as follows: Figure 4b As shown, Figure 4bThis is a schematic diagram of the structure of a third PDU provided in an embodiment of the present application. Figure 4b As shown, the third PDU includes at least one second TLV field 420 for carrying the other information, and each second TLV field can be used to carry a type of information in the other information. For the second TLV, reference can be made to the description of the first TLV field in the previous text, and no repeated description is made here. For other fields in the third TLV except the second TLV field, reference can be made to the description of the first TLV field in the previous text. Figure 1b The description of is not repeated here. It should be noted that Figure 4b The value of the PDU type field of the third PDU shown is different from the value of the PDU type field of the second PDU.
[0173] S103: The network device receives the security verification information sent by the first server.
[0174] S104: The network device stores the security verification information.
[0175] After the first server sends the security verification information to the network device, the network device may receive and store the security verification information sent by the first server, so as to perform security verification on the BGP routing information based on the security verification information later.
[0176] In an example, the network device may store the security verification information locally in the network device.
[0177] In one example, the network device may also obtain the first BGP routing information. For example, the network device may receive the first BGP routing information from other network devices. After the network device obtains the first BGP routing information, it may perform a security verification on the first BGP routing information according to the security verification information. In one example, the first BGP routing information may include a first AS path, and the first AS path is used to indicate the ASs that the first BGP routing information sequentially passes through during the transmission process. In other words, the first AS path is used to indicate the transmission path of the first BGP routing information.
[0178] In an embodiment of the present application, the network device may determine whether the first BGP routing information complies with the routing transmission constraint conditions based on the security verification information. In a specific example, the network device may determine whether the first BGP routing information complies with the routing transmission constraint conditions based on the first business relationship and the second business relationship. In one example, the network device may determine whether the first BGP routing information complies with the routing transmission constraint conditions based on the business relationship corresponding to each transmission path in the first AS path. In another example, the network device may perform upstream verification or downstream verification using the first business relationship and the second business relationship to determine whether the first BGP routing information complies with the routing transmission constraint conditions. Now, examples are given in conjunction with specific scenarios:
[0179] exist Figure 2a In the scenario shown, if the network device in AS X determines that there is no business relationship between AS1 and AS2 based on the second business relationship of AS1, it means that AS1 and AS2 are not neighbors, so the network device in AS X can determine that path hijacking has occurred. If the network device in AS X determines that AS1 is the provider of AS2 based on the second business relationship between AS1 and AS2, the network device in AS X can determine that path leakage has occurred.
[0180] exist Figure 2b In the illustrated scenario, the network device in AS X can determine that there is no business relationship between AS1 and AS2 based on the second business relationship of AS1, that is, AS1 and AS2 are not neighbors, so the network device in AS X can determine that path hijacking has occurred.
[0181] exist Figure 2c In the scenario shown, the network device in AS X can determine that AS1 is a customer of AS2 based on the second business relationship of AS2, so the network device in AS X determines that the verification passes when performing upstream verification.
[0182] exist Figure 2e In the scenario shown, in region 1, the business relationship between AS1 and AS2 is C2P, so the network device in AS X determines that the verification passes when performing upstream verification. In region 2, the business relationship between AS1 and AS2 is C2P, so the network device in AS X determines that the verification fails when performing upstream verification.
[0183] exist Figure 2fIn the scenario shown, since the second business relationship between AS1 and AS2 is partial, the BGP routing information received by AS2 from AS1 cannot be further transmitted through the business relationship C2P, and AS3 is the provider of AS2. Therefore, the network device in AS X can accurately determine that a path leak has occurred.
[0184] In one example, if the security verification information also includes the topological relationship corresponding to the first network domain, the network device can further combine the topological relationship to determine whether the first BGP routing information meets the routing transmission constraint. In a specific example, it can also be further combined with the topological relationship to determine whether the first BGP routing information has path hijacking or path leakage. Now, an example is given in conjunction with a specific scenario:
[0185] exist Figure 2a In the scenario shown, if the network device in AS X determines that there is no business relationship between AS1 and AS2 based on the second business relationship of AS1, and further verifies that there is no neighbor relationship between AS1 and AS2 based on the topological relationship of AS1, the network device in AS X can determine that path hijacking has occurred.
[0186] exist Figure 2b In the scenario shown, the network device in AS X can determine that there is no business relationship between AS1 and AS2 based on the second business relationship of AS1, and further verify that there is no neighbor relationship between AS1 and AS2 based on the topological relationship of AS1, so the network device in AS X can determine that path hijacking has occurred.
[0187] In one example, if the security verification information also includes a routing transmission path that supports transmission through the first network domain, the network device can further combine the routing transmission path to perform a security verification on the first BGP routing information, for example, to determine whether a valley path in the transmission path of the first BGP routing information is a routing transmission path that supports transmission through the first network domain.
[0188] For example, in Figure 2d In the scenario shown, the network device in AS X determines that the transmission path AS1→AS2→ASX is a valley path according to the second business relationship of AS1, and according to the routing transmission path supporting transmission through AS2, the transmission path AS1→AS2→ASX is legal. Therefore, the network device in AS X can determine that the received first BGP routing information passes the security check.
[0189] It can be seen from the above description that, by using the solution of the embodiment of the present application, when the network device performs security verification on the BGP routing information, in addition to using the first business relationship of the network domain for security verification. The BGP routing information can also be security verified in combination with the second business relationship. In addition, in some scenarios, the BGP routing information can also be security verified in combination with the topological relationship of the network domain, and / or the routing transmission path that supports transmission through the network domain. In this solution, compared with traditional technologies, the reference information for security verification of BGP routing information is richer, and accordingly, the verification results obtained are more accurate.
[0190] Based on the information processing method provided by the above method embodiment, the embodiment of the present application also provides a corresponding information processing device. Next, the information processing device provided by the embodiment of the present application is introduced in conjunction with the accompanying drawings.
[0191] See also Figure 5 , which is a structural schematic diagram of an information processing device provided in an embodiment of the present application. Figure 5 The information processing apparatus shown can be applied to a network device to execute the information processing method executed by the network device in the above method embodiment.
[0192] In one example, Figure 5 The information processing device 500 shown may include a receiving unit 501 and a processing unit 502 .
[0193] The receiving unit 501 is used to receive security verification information sent by the server, and the security verification information is used to perform security verification on the Border Gateway Protocol BGP routing information. The security verification information includes a first business relationship corresponding to a first network domain and a second business relationship corresponding to the first network domain. The first business relationship is customer to provider C2P.
[0194] The processing unit 502 is used to store the security verification information.
[0195] The server mentioned here may correspond to the first server in the above method embodiment.
[0196] In a possible implementation, the processing unit 502 is further configured to: obtain first BGP routing information; and perform security verification on the first BGP routing information according to the security verification information.
[0197] In a possible implementation manner, the security verification information further includes: a topological relationship of the first network domain, and / or a routing transmission path that supports transmission through the first network domain.
[0198] In a possible implementation manner, the topological relationship of the first network domain includes: at least one second network domain having a neighbor relationship with the first network domain.
[0199] In a possible implementation manner, the supporting the routing transmission path transmitted through the first network domain includes: supporting the routing transmission path transmitted through the first network domain and not meeting the routing transmission constraint condition.
[0200] In a possible implementation manner, the second business relationship includes one or more of the following: provider to customer P2C, peer to peer P2P, provider sibling, partial, and hybrid.
[0201] In a possible implementation, the device also includes: a sending unit, used to send a request message to the server, the request message is used to request information for security verification of BGP routing information; the receiving unit 501 is used to: receive the security verification information returned by the server in response to the request message.
[0202] In one possible implementation, the request message includes an information type, and the information type is used to instruct the server to return information of the information type to the network device for security verification of BGP routing information. Accordingly, the security verification information includes information of the information type.
[0203] In a possible implementation, the receiving unit 501 is configured to: receive a first protocol data unit PDU sent by the server, where the first PDU includes the security verification information.
[0204] In a possible implementation, the first PDU includes at least one first type length value TLV field, and the at least one first TLV field is used to carry the security verification information, wherein one of the first TLV fields is used to carry a type of information in the security verification information.
[0205] In a possible implementation, the receiving unit 501 is used to: receive a second PDU and a third PDU sent by the server, the second PDU including the first business relationship, and the third PDU including other information in the security verification information except the first business relationship.
[0206] In a possible implementation manner, the third PDU includes at least one second TLV, and the at least one second TLV is used to carry the other information, wherein one second TLV carries a type of information in the other information.
[0207] Since the information processing device 500 and the information processing method executed by the network device in the method embodiment belong to the same concept, the specific implementation of each unit of the information processing device 500 can refer to the relevant description part of the above method embodiment, and no repeated description is made here.
[0208] See also Figure 6 , which is a structural schematic diagram of an information processing device provided in an embodiment of the present application. Figure 6 The information processing device shown can be applied to the first server to execute the information processing method executed by the first server in the above method embodiment.
[0209] In one example, Figure 6 The information processing device 600 shown may include a processing unit 601 and a sending unit 602 .
[0210] Processing unit 601 is used to obtain security verification information, and the security verification information is used to perform security verification on Border Gateway Protocol BGP routing information. The security verification information includes a first business relationship corresponding to a first network domain and a second business relationship corresponding to the first network domain, and the first business relationship is customer to provider C2P.
[0211] The sending unit 602 is used to send the security verification information to the network device.
[0212] In a possible implementation manner, the security verification information further includes: a topological relationship of the first network domain, and / or a routing transmission path that supports transmission through the first network domain.
[0213] In a possible implementation manner, the topological relationship includes: at least one second network domain having a neighbor relationship with the first network domain.
[0214] In a possible implementation manner, the supporting the routing transmission path transmitted through the first network domain includes: supporting the routing transmission path transmitted through the first network domain and not meeting the routing transmission constraint condition.
[0215] In a possible implementation manner, the second business relationship includes one or more of the following: provider to customer P2C, peer to peer P2P, provider sibling, partial, and hybrid.
[0216] In a possible implementation, the device also includes: a receiving unit, used to obtain a simplified local Internet number resource management SLURM file corresponding to the first network domain, the SLURM file including the security verification information; the processing unit 601 is also used to store the security verification information.
[0217] In a possible implementation manner, the SLURM file includes a first object, and the first object carries the security verification information.
[0218] In a possible implementation manner, the SLURM file includes a second object and a third object, and the second object and the third object jointly carry the security verification information.
[0219] In a possible implementation manner, the second object carries the first business relationship, and the third object carries other information in the security verification information except the first business relationship.
[0220] In a possible implementation, the sending unit 602 is further used to: send an information synchronization message to the second server, wherein the information synchronization message is used to request synchronization of information used to perform security verification on BGP routing information; and the receiving unit is used to: receive the SLURM file corresponding to the first network domain sent by the second server.
[0221] In a possible implementation, the receiving unit included in the apparatus is further used to: receive a request message sent by the network device, the request message being used to request information for performing security verification on BGP routing information; the sending unit 602 is used to: send the security verification information to the network device based on the request information.
[0222] In one possible implementation, the request message includes an information type, and the information type is used to indicate that the first server returns information of the information type to the network device for security verification of BGP routing information, and accordingly, the security verification information includes information of the information type.
[0223] In a possible implementation, the sending unit 602 is configured to send a first protocol data unit PDU to the network device, where the first PDU includes the security verification information.
[0224] In a possible implementation, the first PDU includes at least one first type length value TLV field, and the at least one first TLV field is used to carry the security verification information, wherein one of the first TLV fields is used to carry a type of information in the security verification information.
[0225] In a possible implementation, the sending unit 602 is used to: send a second PDU and a third PDU to the network device, the second PDU includes the first business relationship, and the third PDU includes other information in the security verification information except the first business relationship.
[0226] In a possible implementation manner, the third PDU includes at least one second TLV, and the at least one second TLV is used to carry the other information, wherein one second TLV carries a type of information in the other information.
[0227] Since the information processing device 600 and the information processing method executed by the first server in the method embodiment belong to the same concept, the specific implementation of each unit of the information processing device 600 can refer to the relevant description part of the above method embodiment and will not be repeated here.
[0228] It should be noted that the hardware structure of the information processing devices 500 and 600 mentioned above can be as follows: Figure 7 The structure shown, Figure 7 A schematic diagram of the structure of a device provided in an embodiment of the present application.
[0229] See also Figure 7 As shown, the device 700 includes: a processor 710, a communication interface 720 and a memory 730. The number of the processor 710 in the device 700 can be one or more. Figure 7 In the embodiment of the present application, the processor 710, the communication interface 720 and the memory 730 may be connected via a bus system or other means, wherein: Figure 7 The connection via bus system 740 is taken as an example.
[0230] The processor 710 may be a central processing unit (CPU), a network processor (NP) or a combination of a CPU and a NP. The processor 710 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.
[0231] The memory 730 may include a volatile memory (English: volatile memory), such as a random-access memory (RAM); the memory 730 may also include a non-volatile memory (English: non-volatile memory), such as a flash memory (English: flash memory), a hard disk drive (HDD) or a solid-state drive (SSD); the memory 730 may also include a combination of the above-mentioned types of memory. The memory 730 may, for example, store the aforementioned security verification information.
[0232] Optionally, the memory 730 stores an operating system and a program, an executable module or a data structure, or a subset thereof, or an extended set thereof, wherein the program may include various operating instructions for implementing various operations. The operating system may include various system programs for implementing various basic services and processing hardware-based tasks. The processor 710 may read the program in the memory 730 to implement the information processing method provided in the embodiment of the present application.
[0233] The bus system 740 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus system 740 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 7 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.
[0234] The embodiment of the present application also provides a computer-readable storage medium, including instructions or computer programs, which, when executed on a computer, enable the computer to execute the information processing method provided in the above embodiment.
[0235] The embodiments of the present application also provide a computer program product including instructions or a computer program, which, when executed on a computer, enables the computer to execute the information processing method provided in the above embodiments.
[0236] An embodiment of the present application also provides a communication system, which may include a first server and a network device of the information processing method corresponding to the above method embodiment.
[0237] 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.
[0238] 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.
[0239] 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.
[0240] 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.
[0241] 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.
[0242] 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 is essentially 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, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network 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), random access memory (RAM), disk or optical disk and other media that can store program code.
[0243] 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.
[0244] 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.
[0245] 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, a person of ordinary skill in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features thereof 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 a network device, the method comprises: Receiving security verification information sent by a server, the security verification information is used to perform security verification on Border Gateway Protocol (BGP) routing information, the security verification information includes a first business relationship corresponding to a first network domain and a second business relationship corresponding to the first network domain, the first business relationship being a customer-to-provider (C2P) relationship; The security verification information is stored.
2. The method according to claim 1, characterized in that: The method further comprises: Obtain first BGP routing information; Perform a security check on the first BGP routing information according to the security check information.
3. The method according to claim 1 or 2, characterized in that: The security verification information also includes: The topological relationship of the first network domain, and / or, a routing transmission path supporting transmission through the first network domain.
4. The method according to claim 3, characterized in that The topological relationship of the first network domain includes: At least one second network domain having a neighbor relationship with the first network domain.
5. The method according to claim 3 or 4, characterized in that: The routing transmission path supporting transmission through the first network domain includes: A routing transmission path that is transmitted through the first network domain and does not meet the routing transmission constraint condition is supported.
6. The method according to any one of claims 1 to 5, characterized in that: The second business relationship includes one or more of the following: Provider to customer P2C, peer to peer P2P, sibling to each other, partial transmission, and hybrid.
7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: Sending a request message to the server, wherein the request message is used to request information for security verification of BGP routing information; The receiving server sends the security verification information, including: Receive the security verification information returned by the server in response to the request message.
8. The method according to claim 7, characterized in that The request message includes an information type, and the information type is used to instruct the server to return information of the information type to the network device for security verification of BGP routing information. Accordingly, the security verification information includes information of the information type.
9. The method according to any one of claims 1 to 8, characterized in that: The receiving server sends the security verification information, including: A first protocol data unit (PDU) sent by the server is received, where the first PDU includes the security verification information.
10. The method according to claim 9, characterized in that The first PDU includes at least one first type length value TLV field, and the at least one first TLV field is used to carry the security verification information, wherein one first TLV field is used to carry a type of information in the security verification information.
11. The method according to any one of claims 1 to 8, characterized in that: The receiving server sends the security verification information, including: A second PDU and a third PDU sent by the server are received, wherein the second PDU includes the first business relationship, and the third PDU includes other information in the security verification information except the first business relationship.
12. The method according to claim 11, characterized in that The third PDU includes at least one second TLV, and the at least one second TLV is used to carry the other information, wherein one second TLV carries a type of information in the other information.
13. An information processing method, characterized in that: Applied to a first server, the method comprises: Acquire security verification information, where the security verification information is used to perform security verification on Border Gateway Protocol (BGP) routing information, where the security verification information includes a first business relationship corresponding to a first network domain and a second business relationship corresponding to the first network domain, where the first business relationship is a customer-to-provider (C2P) relationship; The security verification information is sent to the network device.
14. The method according to claim 13, characterized in that The security verification information also includes: The topological relationship of the first network domain, and / or, a routing transmission path supporting transmission through the first network domain.
15. The method according to claim 14, characterized in that The topological relationship includes: At least one second network domain having a neighbor relationship with the first network domain.
16. The method according to claim 14 or 15, characterized in that The routing transmission path supporting transmission through the first network domain includes: A routing transmission path that is transmitted through the first network domain and does not meet the routing transmission constraint condition is supported.
17. The method according to claims 13-16, characterized in that The second business relationship includes one or more of the following: Provider to customer P2C, peer to peer P2P, sibling to each other, partial transmission, and hybrid.
18. The method according to any one of claims 13 to 17, characterized in that: The method further comprises: Obtaining a Simplified Local Internet Number Resource Management (SLURM) file corresponding to the first network domain, wherein the SLURM file includes the security verification information; The security verification information is stored.
19. The method according to claim 18, characterized in that The SLURM file includes a first object, and the first object carries the security verification information.
20. The method according to claim 18, characterized in that The SLURM file includes a second object and a third object, and the second object and the third object jointly carry the security verification information.
21. The method according to claim 20, characterized in that The second object carries the first business relationship, and the third object carries other information in the security verification information except the first business relationship.
22. The method according to any one of claims 18 to 21, characterized in that: The method further comprises: Sending an information synchronization message to the second server, wherein the information synchronization message is used to request synchronization of information used to perform security verification on BGP routing information; The obtaining of the SLURM file corresponding to the first network domain includes: Receive a SLURM file corresponding to the first network domain sent by the second server.
23. The method according to any one of claims 13 to 22, characterized in that: The method further comprises: Receiving a request message sent by the network device, wherein the request message is used to request information for performing security verification on BGP routing information; The sending the security verification information to the network device includes: The security verification information is sent to the network device according to the request information.
24. The method according to claim 23, characterized in that The request message includes an information type, and the information type is used to instruct the first server to return information of the information type to the network device for security verification of BGP routing information. Accordingly, the security verification information includes information of the information type.
25. The method according to any one of claims 13 to 24, characterized in that: The sending the security verification information to the network device includes: A first protocol data unit (PDU) is sent to the network device, where the first PDU includes the security verification information.
26. The method according to claim 25, characterized in that The first PDU includes at least one first type length value TLV field, and the at least one first TLV field is used to carry the security verification information, wherein one first TLV field is used to carry a type of information in the security verification information.
27. The method according to any one of claims 13 to 24, characterized in that: The sending the security verification information to the network device includes: A second PDU and a third PDU are sent to the network device, wherein the second PDU includes the first business relationship, and the third PDU includes other information in the security verification information except the first business relationship.
28. The method according to claim 27, characterized in that The third PDU includes at least one second TLV, and the at least one second TLV is used to carry the other information, wherein one second TLV carries a type of information in the other information.
29. An information processing device, characterized in that: Applied to network equipment, the device comprises: a receiving unit, configured to receive security verification information sent by a server, wherein the security verification information is used to perform security verification on Border Gateway Protocol (BGP) routing information, wherein the security verification information includes a first business relationship corresponding to a first network domain and a second business relationship corresponding to the first network domain, wherein the first business relationship is a customer-to-provider (C2P) relationship; A processing unit is used to store the security verification information.
30. An information processing device, characterized in that: Applied to a first server, the device comprises: a processing unit, configured to obtain security verification information, wherein the security verification information is used to perform security verification on Border Gateway Protocol (BGP) routing information, wherein the security verification information includes a first business relationship corresponding to a first network domain and a second business relationship corresponding to the first network domain, wherein the first business relationship is a customer-to-provider (C2P) relationship; A sending unit is used to send the security verification information to the network device.
31. A device, characterized in that include: Processor and memory; The memory is used to store instructions or computer programs; The processor is used to execute the instructions or computer programs to perform the method according to any one of claims 1 to 28.
32. A computer-readable storage medium, characterized in that: The method comprises instructions or a computer program, which, when executed on a computer, causes the computer to execute the method according to any one of claims 1 to 28.
33. A communication system, characterized in that: The system comprises: A network device that executes the method described in any one of claims 1-12 above, and a first server that executes the method described in any one of claims 13-28 above.
Citation Information
Cited By
Information processing method and apparatus
EP4712411A1
Information processing method and apparatus
WO2024251078A1
