WO2020107678A1 - 云网传输路由方法和系统 - Google Patents

云网传输路由方法和系统 Download PDF

Info

Publication number
WO2020107678A1
WO2020107678A1 PCT/CN2019/071877 CN2019071877W WO2020107678A1 WO 2020107678 A1 WO2020107678 A1 WO 2020107678A1 CN 2019071877 W CN2019071877 W CN 2019071877W WO 2020107678 A1 WO2020107678 A1 WO 2020107678A1
Authority
WO
WIPO (PCT)
Prior art keywords
data exchange
network
network partition
bgp
bgp routing
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2019/071877
Other languages
English (en)
French (fr)
Inventor
郭志鸿
李庆荣
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Wangsu Science and Technology Co Ltd
Original Assignee
Wangsu Science and Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Wangsu Science and Technology Co Ltd filed Critical Wangsu Science and Technology Co Ltd
Priority to EP19890293.4A priority Critical patent/EP3886376A4/en
Priority to US17/044,641 priority patent/US20210105204A1/en
Publication of WO2020107678A1 publication Critical patent/WO2020107678A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/033—Topology update or discovery by updating distance vector protocols

Definitions

  • the invention relates to the technical field of network transmission, in particular to a cloud network transmission routing method and system.
  • node servers in the network are increasing day by day, and mutual visits between node servers are frequent.
  • data is often transmitted through the public network, which will increase the operating costs of the enterprise.
  • the public network lines are easy to use during peak traffic Line congestion occurs, affecting business operations.
  • each branch route connects multiple node servers.
  • Each node server on the branch route can record its own network segment in the routing table, and announce the routing table table to nearby node servers and the branch routes connected to it.
  • the branch route can send the routing table received from the target node server to the central route, other branch routes connected to it, and other node servers connected to it.
  • the central route forwards the routing table received from the target branch route to other branch routes, and then the other branch routes are forwarded to each connected node server separately.
  • the node server can add the routing table received to the other node server to its own routing table in. In this way, the routing table of each node server in the network records the network segment of other node servers, so that it can be routed from the target node server to any other node server.
  • embodiments of the present invention provide a cloud network transmission routing method and system.
  • the technical solution is as follows:
  • a cloud network transmission routing method is provided.
  • the method is applicable to a BGP network.
  • the BGP network may be divided into multiple network partitions, and each network partition includes a data exchange system and multiple node servers.
  • the data exchange system establishes a BGP session with each of the node servers.
  • the method includes:
  • the data exchange system of the first network partition receives the updated BGP routing item announced by the target node server, where the BGP routing item includes the network segment identifier of the target network segment of the target node server and the corresponding community attribute value;
  • the data exchange system of the first network partition sends the BGP route item to the data exchange system of the second network partition according to the community attribute value included in the BGP route item;
  • the data exchange system of the second network partition forwards the BGP routing item to the node server of the second network partition.
  • the data exchange system of the first network partition receiving the updated BGP routing item announced by the target node server includes:
  • the data exchange system of the first network partition judges whether the community attribute value included in the BGP routing item conforms to a local preset community attribute reception rule in the partition;
  • the data exchange system of the first network partition receives the updated BGP routing item announced by the target node server.
  • the data exchange system of the first network partition sends the BGP route item to the data exchange system of the second network partition according to the community attribute value included in the BGP route item, including:
  • the data exchange system of the first network partition determines, in a locally preset inter-community community attribute transmission rule table, the target inter-community community attribute transmission rule that the community attribute value included in the BGP routing item matches;
  • the data exchange system of the first network partition determines the second network partition pointed by the target community attribute sending rule, and sends the BGP routing item to the data exchange system of the second network partition.
  • the data exchange system of the second network partition forwarding the BGP routing item to the node server of the second network partition includes:
  • the data exchange system of the second network partition judges whether the community attribute value included in the BGP routing item conforms to a local preset community attribute sending rule in the partition;
  • the data exchange system of the second network partition forwards the BGP routing entry to the node server of the second network partition.
  • the data exchange system of the second network partition forwarding the BGP routing item to the node server of the second network partition includes:
  • the data exchange system of the second network partition judges whether the community attribute value included in the BGP routing item conforms to the inter-community community attribute reception rule in the locally preset inter-community community attribute reception rule table;
  • the data exchange system of the second network partition sends the BGP routing item to the node server of the second network partition.
  • the method further includes:
  • the data exchange system of the first network partition judges whether the community attribute value included in the BGP routing item conforms to a local preset community attribute sending rule in the partition;
  • the data exchange system of the first network partition sends the BGP routing entry to the node server of the first network partition.
  • the data exchange system includes at least one regional core switch.
  • the data exchange system further includes at least one regional transit switch, and the regional transit switch establishes a BGP session with each of the node server and the regional core switch.
  • the method further includes:
  • the target node server periodically sends a status detection message to the node server corresponding to the BGP routing item;
  • the target node server If the target node server does not receive the status response message returned by the node server corresponding to the BGP route item, the target node server deletes the BGP route item.
  • a cloud network transmission routing system is provided.
  • the system is applicable to a BGP network.
  • the BGP network can be divided into multiple network partitions, each of which includes a data exchange subsystem and multiple node servers
  • the data exchange subsystem establishes a BGP session with each of the node servers.
  • the system includes:
  • the data exchange subsystem of the first network partition is used to receive the updated BGP routing item announced by the target node server, and send the BGP routing item to the second network partition according to the community attribute value contained in the BGP routing item
  • the core switch, the BGP routing item contains the network segment identifier of the target network segment of the target node server and the corresponding community attribute value;
  • the data exchange subsystem of the second network partition is used to forward the BGP routing item to the node server of the second network partition.
  • data exchange subsystem of the first network partition is specifically used for:
  • data exchange subsystem of the first network partition is specifically used for:
  • data exchange subsystem of the second network partition is specifically used for:
  • the BGP routing entry is forwarded to the node server of the second network partition.
  • data exchange subsystem of the second network partition is specifically used for:
  • the data exchange subsystem of the first network partition is also used to:
  • the BGP routing entry is sent to the node server of the first network partition.
  • the data exchange subsystem includes at least one regional core switch.
  • the data exchange subsystem further includes at least one regional transit switch, and the regional transit switch establishes a BGP session with each of the node server and the regional core switch.
  • node server is also used to:
  • the BGP routing item is deleted.
  • the data exchange system of the first network partition receives the updated BGP routing item announced by the target node server, and the BGP routing item includes the network segment identifier of the target network segment of the target node server and the corresponding community attribute value;
  • the data exchange system of a network partition sends the BGP route item to the data exchange system of the second network partition according to the community attribute value contained in the BGP route item;
  • the data exchange system of the second network partition forwards the BGP route item to the second network partition Node server.
  • the node server that can receive the BGP routing item can be determined by the community attribute value, so that the BGP routing item can only be received by the designated node server, reducing the traffic consumption in the process of transmitting the BGP routing item, and avoiding the BGP routing item from other
  • the node server is obtained to improve security.
  • FIG. 1 is a flowchart of a cloud network transmission routing method provided by an embodiment of the present invention
  • FIG. 2 is a schematic structural diagram of a cloud network transmission routing system according to an embodiment of the present invention.
  • An embodiment of the present invention provides a cloud network transmission routing method, which can be applied to a BGP (Border Gateway Gateway, Border Gateway Protocol) network, which is implemented by a data exchange system and a node server in a BGP network.
  • the data exchange system can be At least one core switch can also be composed of at least one core switch and at least one transit switch.
  • the data exchange system establishes a BGP session with the node server, and the core switch and the transit exchange in the data exchange system also establish BGP. Conversation.
  • the node server can use its own network segment as a BGP routing item and send it to other node servers in the BGP network through the data exchange system, so that the two node servers can perform routing transmission of data packets.
  • the application scenario of this embodiment may be: the administrator sets the target network segment of the node server as the BGP routing item on the target node server of the first network partition, and the BGP routing item contains the network segment identifier of the target network segment and the corresponding The community attribute value, the target node server announces the BGP routing item to the outside.
  • the data switching system of the first network partition After receiving the BGP routing item, sends the BGP routing item to the data switching system of the second network partition according to the community attribute value contained in the BGP routing item.
  • the core data exchange system of the second network partition forwards the BGP routing item to the node server of the second network partition.
  • Step 101 The data exchange system of the first network partition receives the updated BGP routing item announced by the target node server.
  • the BGP routing item includes the network segment identifier of the target network segment of the target node server and the corresponding community attribute value.
  • a BGP session is established between the node server and the data exchange system, and the BGP network is formed by the node server and the data exchange system. More than one network partition can be set in the BGP network. Each network partition contains a data exchange system and multiple node servers. BGP sessions are also established between the data exchange systems of different network partitions. Different network partitions exchange data through each partition BGP session connection between systems.
  • the target node server may announce the updated BGP routing entry to the outside.
  • the BGP routing item contains the network segment identifier of the target network segment of the target node server and the corresponding community attribute value.
  • the updated BGP routing item announced by the target node server may be received by the data exchange system of the first network partition.
  • the update operations of BGP routing items include: adding BGP routing items of new network segments, deleting BGP routing items of existing network segments, adding community attribute values corresponding to network segments in existing BGP routing items, and deleting existing BGP routing items The community attribute value corresponding to the network segment and modifying the community attribute value corresponding to the network segment in the existing BGP routing item. Understandably, the target node server can usually use the update message to announce the updated BGP routing item.
  • the update message has different fields for identifying the corresponding update operation.
  • BGP routing entries on the target node server can form a BGP routing table, as shown in Table 1.
  • the Community attribute value is in the form of AA:NN, where AA represents the source network partition of the node server to which the BGP routing entry belongs, and NN represents the destination network partition to which the BGP routing entry can be sent.
  • AA represents the source network partition of the node server to which the BGP routing entry belongs
  • NN represents the destination network partition to which the BGP routing entry can be sent.
  • 100 represents Hangzhou and 200 represents Shenzhen and 300 represent Beijing. It can be seen from Table 1 that the target node server has two network segments 11.0.0.0/24 and 11.0.1.0/24. According to different network segments, there are two BGP routing entries.
  • BGP routing entry 11 indicates the BGP routing entry.
  • the network segment ID is 11.0.0.0/24, with two community attribute values 100:200, 100:300, the source network partition of the node server to which the BGP routing item 11 belongs is Hangzhou, and can be sent to the node server of the Shenzhen network partition Or the node server of the Beijing network partition;
  • BGP routing item 12 indicates that the network segment identifier of the BGP routing item is 11.0.1.0/24, with three community attribute values of 100:100, 100:200, 100:300, and BGP routing item 12
  • the source network partition of the node server to which it belongs is Hangzhou, which can be sent to other node servers of the Hangzhou network partition, the node servers of the Shenzhen network partition or the node servers of the Beijing network partition.
  • the data exchange system of the first network partition may receive some wrong or unconfigured BGP routing items due to various factors. Therefore, the processing in step 101 may be specifically as follows: The data exchange system of the first network partition judges that the BGP routing items contain Whether the value of the community attribute conforms to the local community attribute reception rule preset in the zone; if it matches, the data exchange system of the first network zone receives the updated BGP routing item announced by the target node server.
  • the target node server of the first network partition may declare an incorrect or unconfigured BGP routing item due to operational errors or other factors. Therefore, on the data exchange system of the first network partition, the community attribute reception rule in the partition can be preset, and only the BGP routing items whose community attribute value matches the community attribute reception rule in the partition can be exchanged by the data in the first network partition The system receives. If the value of the community attribute included in the BGP routing entry does not meet the preset community attribute reception rule on the data exchange system of the first network partition, the data exchange system of the first network partition discards the BGP routing entry.
  • the data exchange system of the first network partition After receiving the BGP routing item, the data exchange system of the first network partition sends it to the data exchange system of the second network partition.
  • the BGP routing items announced by the node server can be filtered by the data exchange system in the same network partition, and only the pre-planned BGP routing items can be used for the data
  • the switching system receives and sends it out to prevent unplanned BGP routing items from being sent and improve security.
  • the data exchange system of Hangzhou network partition only receives BGP routing items whose source network partition is Hangzhou. Refer to Table 1 to know that both BGP routing item 11 and BGP routing item 12 can be received by the data switching system of Hangzhou network partition.
  • the data exchange system of the first network partition is also preset with a community attribute transmission rule in the partition. After receiving the BGP routing item sent by the data exchange system of the other network partition, the data exchange system of the first network partition can further Determine whether the community attribute of the BGP routing item conforms to the community attribute sending rule preset in the data exchange system of the first network partition. If it matches, the data exchange system of the first network partition can forward the BGP route item to all connected to it The node server of the first network partition.
  • the data exchange system of the Hangzhou network partition can only send the BGP routing items of the destination network partition to Hangzhou to the node server of the Hangzhou network partition.
  • the two community attribute values of BGP route item 21 are 200:200 and 200:300, that is, the source network partition is Shenzhen, and the destination network partition is Shenzhen and Beijing; the two community of BGP route item 22
  • the attribute values are 200:200 and 200:100, that is, the source network partition is Shenzhen, and the destination network partition is Shenzhen and Hangzhou, respectively.
  • the data exchange system of the Hangzhou network partition receives the BGP route item 21 and the BGP route item 22, because the value of the community attribute contained in the BGP route item 21 does not match the rules for sending the community attribute in the above partition, the data exchange system of the Hangzhou network partition
  • the BGP routing item 21 cannot be forwarded to all node servers of the Hangzhou network partition connected to the data exchange system of the Hangzhou network partition; and the community attribute value contained in the BGP routing item 22 conforms to the above community attribute sending rules in the partition. Therefore, the Hangzhou network partition
  • the data exchange system can forward the BGP routing item 22 to all the node servers of the Hangzhou network partition connected to the data exchange system of the Hangzhou network partition.
  • the data exchange system can filter and filter the BGP routing items received from other network partitions, and only pre-planned BGP routing items can be sent by the data exchange system to Node servers in the same network partition avoid unplanned BGP routing items being learned by node servers in the same network partition, improving security.
  • Serial number Segment identification Community attribute value Source Network Partition-Destination Network Partition twenty one 21.0.0.0/24 200:200; 200:300 Shenzhen-Shenzhen; Shenzhen-Beijing twenty two 21.0.1.0/24 200:200; 200:100 Shenzhen-Shenzhen; Shenzhen-Hangzhou
  • Step 102 The data exchange system of the first network partition sends the BGP route item to the data exchange system of the second network partition according to the community attribute value contained in the BGP route item.
  • the data switching system of the first network partition after receiving the BGP routing item sent from the node server of the first network partition, adds the received BGP routing item to the local BGP route of the data switching system of the first network partition Table, and then send the BGP routing entry to the data exchange system of the second network partition according to the community attribute value contained in the BGP routing entry.
  • step 102 may be specifically as follows: In the attribute transmission rule table, determine the community attribute transmission rule between the target partitions that the community attribute value included in the BGP routing item matches; The routing item is sent to the data exchange system of the second network partition.
  • the data exchange system of the first network partition is preset with the inter-partition community attribute transmission rule table, and the table records multiple inter-partition community attribute transmission rules, and each inter-partition community attribute transmission rule is applied to the corresponding BGP session (BGP session between the data exchange system of the first network partition and the data exchange system of other network partitions).
  • the data exchange system of the first network partition After receiving the BGP routing entry from the first network node server, the data exchange system of the first network partition updates the local BGP routing table of the data exchange system of the first network partition, and then according to the community attribute value of the BGP routing entry, from The community attribute transmission rule between the target partitions is determined in the community attribute transmission rule table by section.
  • the data exchange system of the first network partition further determines the second network partition pointed to by the BGP session corresponding to the community attribute transmission rule between the target partitions, and then sends the BGP routing item to the data exchange system of the second network partition through the BGP session.
  • the data exchange system of the Hangzhou network partition receives BGP route item 11 and BGP route item 12
  • the community attribute value contained in BGP route item 11 and BGP route item 12 conforms to the above-mentioned application on the Hangzhou-Shenzhen BGP session
  • the community attribute sending rule is divided into sections.
  • the data exchange system of the Hangzhou network partition further determines the Shenzhen network zone pointed to by the Hangzhou-Shenzhen BGP session corresponding to the community attribute sending rule between the partitions, and then transfers the BGP routing items through the Hangzhou-Shenzhen BGP session 11 and BGP routing items 12 are sent to the data exchange system of the Shenzhen network partition.
  • BGP route item 11 and BGP route item 12 Will be discarded directly.
  • the data exchange system can filter and filter the BGP routing items received from the node servers of the same network partition, and only the pre-planned BGP routing items can be used for the data
  • the switching system is sent to the data switching system of the corresponding network partition to prevent unplanned BGP routing items from being sent to the wrong network partition and improve security.
  • Step 103 The data exchange system of the second network partition forwards the BGP routing entries to the node server of the second network partition.
  • the data switching system of the second network partition after receiving the BGP routing entry sent by the data switching system of the first network partition, the data switching system of the second network partition sends the BGP routing entry to the node server of the second network partition.
  • the processing in step 103 may be specifically as follows: The data exchange system of the second network partition judges that the BGP routing items contain Whether the community attribute value meets the inter-partition community attribute reception rule in the local preset inter-community community attribute reception rule table; if it matches, the data exchange system of the second network partition sends the BGP routing item to the node server of the second network partition.
  • the data exchange system of the second network partition can be connected to the data exchange systems of multiple network partitions. Therefore, the data exchange system of the second network partition can receive BGP routes from the data exchange system of different network partitions Among these BGP routing entries, there may be some incorrect or unplanned BGP routing entries caused by human operation errors or other factors. Therefore, it is possible to pre-set the inter-partition community attribute reception rule table on the data exchange system of the second network partition.
  • the table records multiple inter-partition community attribute reception rules, and each inter-partition community attribute reception rule is applied to the corresponding BGP session (BGP session between the data exchange system of the second network partition and the data exchange system of other network partitions). Only when the community attribute value of the BGP routing item received by the data exchange system of the second network partition meets an inter-partition community attribute reception rule in the table, the data exchange system of the second network partition can receive the BGP route item.
  • the data exchange system of the second network partition After receiving the BGP route item sent by the data exchange system of the first network, the data exchange system of the second network partition determines whether the community attribute value contained in the BGP route item conforms to the local preset inter-community community attribute reception rule table The community attribute receiving rule of any one of the partitions, if it is met, the data exchange system of the second network partition receives the BGP routing item through the BGP session corresponding to the community attribute sending rule in the target partition, and sends the BGP routing item to the second The node server of the network partition; if not, the data exchange system of the second network partition discards the BGP routing entry.
  • an inter-community community property reception rule table in the inter-community community property reception rule table on the data exchange system of the Shenzhen network partition: community100:200 that is, the source network partition of the node server to which the BGP routing item belongs is Hangzhou, and the destination network The partition is Shenzhen, and the community attribute reception rule between the partitions is applied to the Hangzhou-Shenzhen BGP session.
  • the data exchange system of the Shenzhen network partition receives BGP route item 11 and BGP route item 12
  • BGP route item 11 and BGP route item 12 come from the Hangzhou-Shenzhen BGP session
  • the routing attribute 12 contains the community attribute value transmission rule that matches the community attribute value.
  • the data exchange system of the Shenzhen network partition receives the BGP route item 11 and the BGP route item 12, and forwards it to the data exchange of the Shenzhen network zone system.
  • the data exchange system of the Shenzhen network partition since these BGP sessions do not have corresponding community property reception rules between the partitions: community100:200, if BGP route item 11 and BGP route item 12 come from these BGP sessions, in If there is no inter-partition community attribute reception rule in the local preset inter-community community attribute reception rule table, BGP route item 11 and BGP route item 12 will be directly discarded.
  • the data exchange system can filter and filter the BGP routing items received from other network partitions, and only pre-planned BGP routing items can be received by the data exchange system. This prevents the data exchange system from sending unplanned BGP routing items to node servers in the same network partition, and improves security.
  • the data exchange system of the second network partition may receive some wrong or unplanned BGP routing entries due to various factors. Therefore, in order to avoid sending these wrong or unplanned BGP routing entries to the node server of the second network partition , Causing the node server of the second network partition to receive the wrong BGP route, the processing of step 103 may be as follows: the data exchange system of the second network partition judges whether the community attribute value included in the BGP route item conforms to the community attribute in the local preset zone Sending rules; if it meets, the data exchange system of the second network partition forwards the BGP routing entries to the node server of the second network partition.
  • the data exchange system of the second network partition is preset with a community attribute transmission rule in the partition. After receiving the BGP routing item sent by the data exchange system of the first network partition, the data exchange of the second network partition The system can further determine whether the community attribute of the BGP routing item conforms to the local preset community attribute sending rule. If it matches, the data exchange system of the second network partition forwards the BGP route item to all second network partitions connected to it Node server.
  • the data exchange system of the Shenzhen network partition can only send BGP routing items whose destination network is Shenzhen to the node server of the Shenzhen network partition.
  • the data exchange system of the Shenzhen network partition receives the BGP route item 11 and the BGP route item 12
  • the community attribute value included in the BGP route item 11 and the BGP route item 12 conforms to the community attribute sending rule in the above-mentioned zone, so
  • the data exchange system of Shenzhen network partition can send BGP routing item 11 and BGP routing item 12 to the node server of Shenzhen network partition.
  • the data exchange system of the first network partition After the data exchange system of the first network partition receives the BGP routing item from the node server of the first network partition, if the destination network partition of the BGP routing item is the first network partition, the data exchange system of the first network partition can directly To process it, the corresponding processing can be as follows: The data exchange system of the first network partition judges whether the value of the community attribute contained in the BGP routing item conforms to the preset local community attribute transmission rule; if it matches, the data of the first network partition The switching system sends the BGP routing items to the node server of the first network partition.
  • the BGP routing items received by the data exchange system of the first network partition may originate from the node server of the first network partition, or may originate from the data exchange system of other network partitions.
  • the processing of the system's BGP routing items has been described above, and will not be repeated here.
  • the processing of the BGP routing items of the node server of the source and the first network partition will be described.
  • the data exchange system of the first network partition is also preset with a community attribute sending rule in the partition.
  • the data of the first network partition After receiving the BGP routing item sent by the node server of the first network partition, the data of the first network partition The switching system can further determine whether the community attribute of the BGP routing item conforms to the community attribute sending rule preset within the data exchange system of the first network partition. If it matches, the data exchange system of the first network partition can use the BGP routing item. Forwarded to all node servers of the first network partition connected to it.
  • the data exchange system of the network partition can send the BGP routing items received from the node server of the Hangzhou network partition to the node server of the Hangzhou network partition.
  • the community attribute value included in the BGP route item 11 does not conform to the community attribute sending rule in the above zone.
  • the Hangzhou network zone The data exchange system cannot send BGP routing item 11 to the node server of the Hangzhou network partition; and the community attribute value contained in the BGP routing item 12 conforms to the above community attribute sending rules in the partition. Therefore, the data exchange system of the Hangzhou network partition can directly send The BGP routing item 12 is forwarded to all the node servers of the Hangzhou network partition connected to the data exchange system of the Hangzhou network partition.
  • the data exchange system can filter and filter the BGP routing items received from the node servers in the same network partition, and only the pre-planned BGP routing items can be exchanged by the data
  • the system sends it to other node servers in the same network partition to prevent unplanned BGP routing items from being learned by other node servers in the same network partition and improve security.
  • the data exchange system of each network partition may be composed of at least one regional core switch.
  • the preset community attribute reception rules, the inter-community community attribute transmission rule table, the inter-zone community attribute reception rule table and the intra-community community attribute transmission rule preset on the data exchange system are all set in the regional core switch of the corresponding network partition on.
  • the data exchange system of each partition may also be composed of at least one regional core switch and at least one regional transit switch.
  • the regional core switch establishes a BGP session with the regional transit switch, and the regional transit switch establishes a BGP session with each node server; between different network partitions, the regional core switch of each network partition is established There is a BGP session.
  • the community attribute receiving rules within the subzone and the community attribute sending rules within the zone are set on the regional transit switch corresponding to the network zone, and the interzone community attribute sending rules table and the interzone community attribute receiving rule table are set on the regional core switch corresponding to the network zone.
  • the transmission process of the BGP routing item in the above method may be: the regional transit switch of the first network partition receives the updated BGP routing item announced by the node server of the first network partition according to the community attribute reception rule preset in the local area, Then send it to the regional core switch of the first network partition; the core switch of the first network partition sends the BGP routing entry to the core switch of the second network partition according to the local preset inter-community community attribute sending rule table; The core switch receives the BGP routing items sent from the regional core switch in the first network partition according to the local preset intercommunity community attribute receiving rule table, and sends it to the regional transit switch in the second network partition; the transit switch in the second network partition The community attribute sending rule preset in the local zone sends the received BGP routing item to the node server of the second network zone.
  • the specific content of the transmission process is similar to the previous text, and will not be repeated here.
  • the target node server In order to avoid the route failure between the nodes, the route still exists, and the route still exists, causing the data to be discarded when it is sent through the route.
  • the corresponding processing can be as follows: the target node server periodically sends to the node server corresponding to the received BGP route item Status detection message; if the target node server does not receive the status response message returned by the node server corresponding to the BGP route item, the target node server deletes the BGP route item.
  • BFD Bidirectional Forwarding Detection
  • BFD Bidirectional Forwarding Detection
  • the target node server can periodically send the received BGP The node server corresponding to the route item sends a BFD control message (status detection message). If the target node server does not receive the BFD control message (status response message) returned by the node server corresponding to the BGP route item within the set time, the target The node server will resend the BFD control message.
  • the target node server deletes the BGP routing entry in the local BGP routing table.
  • the data exchange system of the first network partition receives the updated BGP routing item announced by the target node server, and the BGP routing item includes the network segment identifier of the target network segment of the target node server and the corresponding community attribute value;
  • the data exchange system of a network partition sends the BGP route item to the data exchange system of the second network partition according to the community attribute value contained in the BGP route item;
  • the data exchange system of the second network partition forwards the BGP route item to the second network partition Node server.
  • the node server that can receive the BGP routing item can be determined by the community attribute value, so that the BGP routing item can only be received by the designated node server, reducing the traffic consumption in the process of transmitting the BGP routing item, and avoiding the BGP routing item from other
  • the node server is obtained to improve security.
  • an embodiment of the present invention also provides a cloud network transmission routing system.
  • the system is applicable to a BGP network.
  • the BGP network may be divided into multiple network partitions, each network
  • the partition includes a data exchange subsystem and multiple node servers.
  • the data exchange subsystem establishes a BGP session with each of the node servers.
  • the system includes:
  • the data exchange subsystem of the first network partition is used to receive the updated BGP routing item announced by the target node server, and send the BGP routing item to the second network partition according to the community attribute value contained in the BGP routing item
  • the data exchange subsystem of the BGP routing item includes the network segment identifier of the target network segment of the target node server and the corresponding community attribute value.
  • the data exchange subsystem of the second network partition is used to forward the BGP routing item to the node server of the second network partition.
  • the data exchange subsystem of the first network partition is specifically used for:
  • the data exchange subsystem of the first network partition is specifically used for:
  • the data exchange subsystem of the second network partition is specifically used for:
  • the BGP routing entry is forwarded to the node server of the second network partition.
  • the data exchange subsystem of the second network partition is specifically used for:
  • the data exchange subsystem of the first network partition is also used to:
  • the BGP routing entry is sent to the node server of the first network partition.
  • the data exchange subsystem includes at least one regional core switch.
  • the data exchange subsystem further includes at least one regional transit switch, and the regional transit switch establishes a BGP session with each of the node server and the regional core switch.
  • the node server is also used for:
  • the BGP routing item is deleted.
  • each embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware.
  • the above-mentioned technical solutions can be embodied in the form of software products in essence or to contribute to the existing technology, and the computer software products can be stored in computer-readable storage media, such as ROM/RAM, magnetic Discs, optical discs, etc., include several instructions to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in the various embodiments or some parts of the embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种云网传输路由方法和系统，属于网络传输技术领域。所述方法包括：第一网络分区的数据交换系统接收目标节点服务器宣告的更新后的BGP路由项，BGP路由项包含目标节点服务器的目标网段的网段标识和对应的community属性值；第一网络分区的数据交换系统根据BGP路由项包含的community属性值，将BGP路由项发往第二网络分区的数据交换系统；第二网络分区的数据交换系统将BGP路由项转发给第二网络分区的节点服务器。本发明能够减少BGP路由项传输过程中的流量消耗。

Description

云网传输路由方法和系统 技术领域
本发明涉及网络传输技术领域，尤其涉及一种云网传输路由方法和系统。
背景技术
随着互联网业务的蓬勃发展，网络中的节点服务器日益增多，节点服务器之间互访频繁。节点服务器之间进行互访时，往往通过公网进行数据传输，这样会导致企业运营费用增加，同时，由于公网的网络建设不能满足当前业务的发展，在流量高峰期，公网的线路容易发生线路拥塞，影响业务运行。
为了避免上述情况，还可以采用类似大型企业的网络架构来设置节点服务器和路由，即通过中央路由连接多个分支路由，每个分支路由再连接多个节点服务器。分支路由上的每个节点服务器，都可以将自己的网段记录在路由表中，并将路由表表宣告给附近的节点服务器以及与它相连的分支路由。分支路由可以将从目标节点服务器接收到的路由表发送给中央路由、与其相连的其他分支路由以及与其相连的其他节点服务器。中央路由将从目标分支路由接收到的路由表转发给其他分支路由，然后其他分支路分别转发给相连的每个节点服务器，节点服务器可以将接收到其他节点服务器的路由表添加在自己的路由表中。这样，网络中每个节点服务器的路由表中，都记录有其他节点服务器的网段，从而可以从目标节点服务器路由到任一其他节点服务器。
在实现本发明的过程中，发明人发现现有技术中至少存在以下问题：
在传递路由表的过程中，由于要将目标节点服务器的网段发送给网络中的每个节点服务器，因此，需要花费大量数据流量，同时，由于网络中所有节点服务器的网段都可以从任一节点服务器的路由表中获得，节点服务器间数据传输的安全风险较高。
发明内容
为了解决现有技术的问题，本发明实施例提供了一种云网传输路由方法和 系统。所述技术方案如下：
第一方面，提供了一种云网传输路由方法，所述方法适用于BGP网络，所述BGP网络可以分为多个网络分区，每个网络分区包括数据交换系统和多个节点服务器，所述数据交换系统与每个所述节点服务器建立有BGP会话，所述方法包括：
第一网络分区的数据交换系统接收目标节点服务器宣告的更新后的BGP路由项，所述BGP路由项包含所述目标节点服务器的目标网段的网段标识和对应的community属性值；
所述第一网络分区的数据交换系统根据所述BGP路由项包含的community属性值，将所述BGP路由项发往第二网络分区的数据交换系统；
所述第二网络分区的数据交换系统将所述BGP路由项转发给所述第二网络分区的节点服务器。
进一步的，所述第一网络分区的数据交换系统接收目标节点服务器宣告的更新后的BGP路由项，包括：
所述第一网络分区的数据交换系统判断所述BGP路由项包含的community属性值是否符合本地预设的分区内community属性接收规则；
如果符合，所述第一网络分区的数据交换系统接收所述目标节点服务器宣告的更新后的BGP路由项。
进一步的，所述第一网络分区的数据交换系统根据所述BGP路由项包含的community属性值，将所述BGP路由项发往第二网络分区的数据交换系统，包括：
所述第一网络分区的数据交换系统在本地预设的分区间community属性发送规则表中，确定所述BGP路由项包含的community属性值符合的目标分区间community属性发送规则；
所述第一网络分区的数据交换系统确定所述目标community属性发送规则指向的第二网络分区，将所述BGP路由项发往第二网络分区的数据交换系统。
进一步的，所述第二网络分区的数据交换系统将所述BGP路由项转发给所述第二网络分区的节点服务器，包括：
所述第二网络分区的数据交换系统判断所述BGP路由项包含的community属性值是否符合本地预设的分区内community属性发送规则；
如果符合，所述第二网络分区的数据交换系统则将所述BGP路由项转发给所述第二网络分区的节点服务器。
进一步的，所述第二网络分区的数据交换系统将所述BGP路由项转发给所述第二网络分区的节点服务器，包括：
所述第二网络分区的数据交换系统判断所述BGP路由项包含的community属性值是否符合本地预设的分区间community属性接收规则表中的分区间community属性接收规则；
如果符合，所述第二网络分区的数据交换系统将所述BGP路由项发往所述第二网络分区的节点服务器。
进一步的，所述方法还包括：
所述第一网络分区的数据交换系统判断所述BGP路由项包含的community属性值是否符合本地预设的分区内community属性发送规则；
如果符合，所述第一网络分区的数据交换系统则将所述BGP路由项发送给所述第一网络分区的节点服务器。
进一步的，所述数据交换系统包括至少一个区域核心交换机。
进一步的，所述数据交换系统还包括至少一个区域中转交换机，所述区域中转交换机与每个所述节点服务器及所述区域核心交换机建立有BGP会话。
进一步的，所述方法还包括：
目标节点服务器周期性向BGP路由项对应的节点服务器发送状态检测报文；
如果目标节点服务器没有接收到BGP路由项对应的节点服务器返回的状态响应报文，则所述目标节点服务器删除所述BGP路由项。
第二方面，提供了一种云网传输路由系统，所述系统适用于BGP网络，所述BGP网络可以分为多个网络分区，每个网络分区包括数据交换子系统和多个节点服务器，所述数据交换子系与每个所述节点服务器建立有BGP会话，所述系统包括：
第一网络分区的数据交换子系，用于接收目标节点服务器宣告的更新后的BGP路由项，并根据所述BGP路由项包含的community属性值，将所述BGP路由项发往第二网络分区的核心交换机，所述BGP路由项包含所述目标节点服 务器的目标网段的网段标识和对应的community属性值；
第二网络分区的数据交换子系统，用于将所述BGP路由项转发给所述第二网络分区的节点服务器。
进一步的，所述第一网络分区的数据交换子系统，具体用于：
判断所述BGP路由项包含的community属性值是否符合本地预设的分区内community属性接收规则；
如果符合，则接收所述目标节点服务器宣告的更新后的BGP路由项。
进一步的，所述第一网络分区的数据交换子系统，具体用于：
在本地预设的分区间community属性发送规则表中，确定所述BGP路由项包含的community属性值符合的目标分区间community属性发送规则；
确定所述目标community属性发送规则指向的第二网络分区，将所述BGP路由项发往第二网络分区的数据交换子系统。
进一步的，所述第二网络分区的数据交换子系统，具体用于：
判断所述BGP路由项包含的community属性值是否符合本地预设的分区内community属性发送规则；
如果符合，则将所述BGP路由项转发给所述第二网络分区的节点服务器。
进一步的，所述第二网络分区的数据交换子系统，具体用于：
判断所述BGP路由项包含的community属性值是否符合本地预设的分区间community属性接收规则表中的分区间community属性接收规则；
如果符合，将所述BGP路由项发往所述第二网络分区的节点服务器。
进一步的，所述第一网络分区的数据交换子系统，还用于：
判断所述BGP路由项包含的community属性值是否符合本地预设的分区内community属性发送规则；
如果符合，则将所述BGP路由项发送给所述第一网络分区的节点服务器。
进一步的，所述数据交换子系统包括至少一个区域核心交换机。
进一步的，所述数据交换子系统还包括至少一个区域中转交换机，所述区域中转交换机与每个所述节点服务器及所述区域核心交换机建立有BGP会话。
进一步的，所述节点服务器，还用于：
周期性向BGP路由项对应的节点服务器发送状态检测报文；
如果没有接收到BGP路由项对应的节点服务器返回的状态响应报文，则删 除所述BGP路由项。
本发明实施例提供的技术方案带来的有益效果是：
本发明实施例中，第一网络分区的数据交换系统接收目标节点服务器宣告的更新后的BGP路由项，BGP路由项包含目标节点服务器的目标网段的网段标识和对应的community属性值；第一网络分区的数据交换系统根据BGP路由项包含的community属性值，将BGP路由项发往第二网络分区的数据交换系统；第二网络分区的数据交换系统将BGP路由项转发给第二网络分区的节点服务器。这样，可以通过community属性值确定可以接收BGP路由项的节点服务器，使得BGP路由项只能被指定的节点服务器收到，降低了传输BGP路由项过程中的流量消耗，避免BGP路由项可以从其他节点服务器获得，提高安全性。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明实施例提供的一种云网传输路由方法的流程图；
图2是本发明实施例提供的一种云网传输路由系统的结构示意图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明实施方式作进一步地详细描述。
本发明实施例提供了一种云网传输路由方法，该方法可以适用于BGP(Border Gateway Protocol，边界网关协议)网络，由BGP网络中的数据交换系统和节点服务器共同实现，数据交换系统可以由至少一个核心交换机构成，也可以由至少一个核心交换机和至少一个中转交换机共同构成，在BGP网络中数据交换系统与节点服务器建立有BGP会话，数据交换系统中的核心交换机与中转交换机也建立有BGP会话。节点服务器可以将自己的网段作为BGP路由项，通过数据交换系统发送给BGP网络中的其他节点服务器，使得两个节点服务器 之间可以进行数据报文的路由传输。本实施例的应用场景可以是：管理人员在第一网络分区的目标节点服务器上设置该节点服务器的目标网段作为BGP路由项，BGP路由项中包含有目标网段的网段标识和对应的community属性值，目标节点服务器将该BGP路由项向外宣告。第一网络分区的数据交换系统接收到该BGP路由项后，根据该BGP路由项包含的community属性值，将该BGP路由项发往第二网络分区的数据交换系统。第二网络分区的核心数据交换系统将该BGP路由项转发给第二网络分区的节点服务器。
下面将结合具体实施方式，对图1所示的一种云网路由流程进行详细的说明，内容可以如下：
步骤101：第一网络分区的数据交换系统接收目标节点服务器宣告的更新后的BGP路由项。
其中，BGP路由项包含目标节点服务器的目标网段的网段标识和对应的community属性值。
在实施中，在节点服务器和数据交换系统之间建立BGP会话，通过节点服务器和数据交换系统构成BGP网络。BGP网络中可以设置一个以上的网络分区，每个网络分区包含一个数据交换系统以及多个节点服务器，不同网络分区的数据交换系统之间也建立有BGP会话，不同网络分区通过各分区的数据交换系统之间的BGP会话连接。
管理人员在第一网络分区中的目标节点服务器上对目标节点服务器的BGP路由项进行更新操作后，目标节点服务器可以将更新后的BGP路由项向外宣告。BGP路由项包含目标节点服务器的目标网段的网段标识和对应的community属性值。目标节点服务器宣告的更新后的BGP路由项可以被第一网络分区的数据交换系统接收。BGP路由项的更新操作包括：增加新的网段的BGP路由项、删除现有网段的BGP路由项、增加现有BGP路由项中网段对应的community属性值、删除现有BGP路由项中网段对应的community属性值和修改现有BGP路由项中网段对应的community属性值。可以理解的，目标节点服务器通常可以使用update报文宣告更新后的BGP路由项，update报文中具有不同的字段用于标识相应的更新操作。
目标节点服务器上的多条BGP路由项可以组成BGP路由表，如表1所示。Community属性值为AA:NN形式，其中，AA代表BGP路由项所属节点服务器 的源网络分区、NN代表BGP路由项可以被发送到的目的网络分区，以表1为例，100代表杭州、200代表深圳、300代表北京。根据表1可以看出，目标节点服务器存在11.0.0.0/24和11.0.1.0/24两个网段，根据网段的不同，对应有两个BGP路由项，BGP路由项11表示该BGP路由项的网段标识为11.0.0.0/24，带有两个community属性值100:200、100:300，BGP路由项11所属节点服务器的源网络分区为杭州，可以被发送到深圳网络分区的节点服务器或北京网络分区的节点服务器；BGP路由项12表示该BGP路由项的网段标识为11.0.1.0/24，带有三个community属性值100:100、100:200、100:300，BGP路由项12所属节点服务器的源网络分区为杭州，可以被发送到杭州网络分区的其他节点服务器、深圳网络分区的节点服务器或北京网络分区的节点服务器。
表1 BGP路由表1
Figure PCTCN2019071877-appb-000001
第一网络分区的数据交换系统可能因为多种因素接收到一些错误的或者没有配置的BGP路由项，因此，步骤101的处理具体可以如下：第一网络分区的数据交换系统判断BGP路由项包含的community属性值是否符合本地预设的分区内community属性接收规则；如果符合，第一网络分区的数据交换系统接收目标节点服务器宣告的更新后的BGP路由项。
在实施中，管理人员在第一网络分区的目标节点服务器上设置BGP路由项时，可能因为操作失误，或其他因素，导致第一网络分区的目标节点服务器宣告错误的或者没有配置的BGP路由项，因此，可以在第一网络分区的数据交换系统上，预先设置分区内community属性接收规则，只有community属性值符合该分区内community属性接收规则的BGP路由项，才能被第一网络分区的数据交换系统接收。如果BGP路由项包含的community属性值不符合第一网络分区的数据交换系统上预设的分区内community属性接收规则，第一网络分区的数据交换系统将该BGP路由项丢弃。第一网络分区的数据交换系统接收BGP路由项后，将其发送给第二网络分区的数据交换系统。这样，通过在数据交换系统上设置分区内community属性接收规则，节点服务器宣告的BGP路由项， 就可以被同一网络分区内的数据交换系统进行筛选过滤，只有预先规划的BGP路由项才能被该数据交换系统接收并发送出去，避免非规划的BGP路由项被发送，提高安全性。
例如，可以在杭州网络分区的数据交换系统上设置分区内community属性接收规则为community属性值为100:NN，即BGP路由项所属节点服务器的源网络分区为杭州，目的网络分区可以为任意网络分区，杭州网络分区的数据交换系统只接收源网络分区为杭州的BGP路由项，参考表1可知，BGP路由项11和BGP路由项12都可以被杭州网络分区的数据交换系统接收。
在第一网络分区的数据交换系统上还预先设置有分区内community属性发送规则，在接收到其他网络分区的数据交换系统发来的BGP路由项后，第一网络分区的数据交换系统还可以进一步判断BGP路由项的community属性是否符合第一网络分区的数据交换系统本地预设的分区内community属性发送规则，如果符合，第一网络分区的数据交换系统可以将该BGP路由项转发给所有与其相连的第一网络分区的节点服务器。
例如，可以在杭州网络分区的数据交换系统上设置分区内community属性发送规则为community属性值为AA:100，即BGP路由项所属节点服务器的源网络分区可以为任意网络分区，目的网络分区为杭州，杭州网络分区的数据交换系统只能将目的网络分区为杭州的BGP路由项发送给杭州网络分区的节点服务器。如表2所示，BGP路由项21的两个community属性值分别为200:200和200:300，即源网络分区为深圳，目的网络分区分别为深圳和北京；BGP路由项22的两个community属性值分别为200:200和200:100，即源网络分区为深圳，目的网络分区分别为深圳和杭州。当杭州网络分区的数据交换系统接收到BGP路由项21和BGP路由项22时，由于BGP路由项21包含的community属性值与上述分区内community属性发送规则不符，因此，杭州网络分区的数据交换系统不能将BGP路由项21转发给所有与杭州网络分区的数据交换系统相连的杭州网络分区的节点服务器；而BGP路由项22包含的community属性值符合上述分区内community属性发送规则，因此，杭州网络分区的数据交换系统可以将BGP路由项22转发给所有与杭州网络分区的数据交换系统相连的杭州网络分区的节点服务器。这样，通过在数据交换系统上设置分区内community属性发送规则，数据交换系统可以对从其他网络分区接收到的BGP路由项进行筛 选过滤，只有预先规划的BGP路由项才能被该数据交换系统发送给同一网络分区内的节点服务器，避免非规划的BGP路由项被同一网络分区内的节点服务器学习到，提高安全性。
表2 BGP路由表2
序号 网段标识 Community属性值 源网络分区-目的网络分区
21 21.0.0.0/24 200:200；200:300 深圳-深圳；深圳-北京
22 21.0.1.0/24 200:200；200:100 深圳-深圳；深圳-杭州
步骤102：第一网络分区的数据交换系统根据BGP路由项包含的community属性值，将BGP路由项发往第二网络分区的数据交换系统。
在实施中，第一网络分区的数据交换系统在接收到第一网络分区的节点服务器发来的BGP路由项后，将接收到的BGP路由项添加入第一网络分区的数据交换系统本地BGP路由表，然后根据该BGP路由项包含的community属性值，将该BGP路由项发送给第二网络分区的数据交换系统。
为了避免第一网络分区的数据交换系统将接收到的BGP路由项发送给错误的网络分区，故而，步骤102的处理具体可以如下：第一网络分区的数据交换系统在本地预设的分区间community属性发送规则表中，确定BGP路由项包含的community属性值符合的目标分区间community属性发送规则；第一网络分区的数据交换系统确定目标分区间community属性发送规则指向的第二网络分区，将BGP路由项发往第二网络分区的数据交换系统。
在实施中，第一网络分区的数据交换系统上预先设置有分区间community属性发送规则表，表中记录有多条分区间community属性发送规则，每条分区间community属性发送规则都应用在对应的BGP会话(第一网络分区的数据交换系统与其他网络分区的数据交换系统之间的BGP会话)上。第一网络分区的数据交换系统在接收到第一网络节点服务器发来的BGP路由项后，更新第一网络分区的数据交换系统本地的BGP路由表，然后根据BGP路由项的community属性值，从分区间community属性发送规则表中确定目标分区间community属性发送规则。第一网络分区的数据交换系统再进一步确定目标分区间community属性发送规则对应的BGP会话指向的第二网络分区，然后通过该BGP会话将BGP路由项发往第二网络分区的数据交换系统。
例如，可以在杭州网络分区的数据交换系统上的分区间community属性发 送规则表中设置一条分区间community属性发送规则：community100:200，即BGP路由项所属节点服务器的源网络分区为杭州，目的网络分区为深圳，该分区间community属性发送规则应用在杭州-深圳BGP会话(杭州网络分区的数据交换系统与深圳网络分区的数据交换系统之间的BGP会话)上。参考表1可知，当杭州网络分区的数据交换系统接收到BGP路由项11和BGP路由项12时，BGP路由项11和BGP路由项12包含的community属性值符合杭州-深圳BGP会话上应用的上述分区间community属性发送规则，此时，杭州网络分区的数据交换系统进一步确定上述分区间community属性发送规则对应的杭州-深圳BGP会话指向的深圳网络分区，然后通过杭州-深圳BGP会话将BGP路由项11和BGP路由项12发往深圳网络分区的数据交换系统。而对于杭州网络分区的数据交换系统上的其他BGP会话，由于这些BGP会话没有对应的分区间community属性发送规则：community100:200，因此，在这些BGP会话上，BGP路由项11和BGP路由项12将被直接丢弃。这样，通过在数据交换系统上设置分区间community属性发送规则，数据交换系统就可以对从同一网络分区的节点服务器接收到的BGP路由项进行筛选过滤，只有预先规划的BGP路由项才能被该数据交换系统发送给对应网络分区的数据交换系统，避免非规划的BGP路由项被发送给错误的网络分区，提高安全性。
步骤103：第二网络分区的数据交换系统将BGP路由项转发给第二网络分区的节点服务器。
在实施中，第二网络分区的数据交换系统在接收到第一网络分区的数据交换系统发送来的BGP路由项后将该BGP路由项发送给第二网络分区的节点服务器。
为了避免第二网络分区的数据交换系统将接收到的错误的或者非规划的BGP路由项发送出去，故而，步骤103的处理具体可以如下：第二网络分区的数据交换系统判断BGP路由项包含的community属性值是否符合本地预设的分区间community属性接收规则表中的分区间community属性接收规则；如果符合，第二网络分区的数据交换系统将BGP路由项发往第二网络分区的节点服务器。
在实施中，第二网络分区的数据交换系统可以与多个网络分区的数据交换系统相连，因此，第二网络分区的数据交换系统可以接收到来自不同网络分区 的数据交换系统发来的BGP路由项，这些BGP路由项中，可能存在一些由于人为操作失误或其他因素导致的错误的或非规划的BGP路由项。故而，可以在第二网分区的数据交换系统上预先设置分区间community属性接收规则表，表中记录多条分区间community属性接收规则，每条分区间community属性接收规则都应用在对应的BGP会话(第二网络分区的数据交换系统与其他网络分区的数据交换系统之间的BGP会话)上。只有当第二网络分区的数据交换系统接收到的BGP路由项的community属性值符合表中某条的分区间community属性接收规则时，第二网络分区的数据交换系统才能够接收该BGP路由项。
第二网络分区的数据交换系统在接收到第一网络的数据交换系统发来的BGP路由项后，判断该BGP路由项包含的community属性值是否符合本地预设的分区间community属性接收规则表中的任意一条分区间community属性接收规则，如果符合，第二网络分区的数据交换系统通过该目标分区内community属性发送规则对应的BGP会话接收该BGP路由项，并将该BGP路由项发往第二网络分区的节点服务器；如果不符合，第二网络分区的数据交换系统则将该BGP路由项丢弃。
例如，可以在深圳网络分区的数据交换系统上的分区间community属性接收规则表中设置一条分区间community属性接收规则：community100:200，即BGP路由项所属节点服务器的源网络分区为杭州，目的网络分区为深圳，该分区间community属性接收规则应用在杭州-深圳BGP会话上。参考表1可知，当深圳网络分区的数据交换系统接收到BGP路由项11和BGP路由项12时，如果BGP路由项11和BGP路由项12来自于杭州-深圳BGP会话，BGP路由项11和BGP路由项12包含的community属性值符合的上述分区间community属性发送规则，此时，深圳网络分区的数据交换系统接收BGP路由项11和BGP路由项12，并将其转发给深圳网络分区的数据交换系统。而对于深圳网络分区的数据交换系统上的其他BGP会话，由于这些BGP会话没有对应的分区间community属性接收规则：community100:200，如果BGP路由项11和BGP路由项12来自于这些BGP会话，在本地预设的分区间community属性接收规则表中没有符合的分区间community属性接收规则，BGP路由项11和BGP路由项12将被直接丢弃。这样，通过在数据交换系统上设置分区间community属性接收规则，数据交换系统可以对从其他网络分区接收到的BGP路由项进行筛选 过滤，只有预先规划的BGP路由项才能被该数据交换系统接收，避免该数据交换系统将非规划的BGP路由项接收后发送给同一网络分区内的节点服务器，提高安全性。
第二网络分区的数据交换系统可能因为多种因素接收到一些错误的或非规划的BGP路由项，因此，为了避免将这些错误的或非规划的BGP路由项发送给第二网络分区的节点服务器，导致第二网络分区的节点服务器接收到错误的BGP路由，步骤103的处理可以如下：第二网络分区的数据交换系统判断BGP路由项包含的community属性值是否符合本地预设的分区内community属性发送规则；如果符合，第二网络分区的数据交换系统则将BGP路由项转发给第二网络分区的节点服务器。
在实施中，第二网络分区的数据交换系统上，预先设置有分区内community属性发送规则，在接收到第一网络分区的数据交换系统发来的BGP路由项后，第二网络分区的数据交换系统还可以进一步判断BGP路由项的community属性是否符合本地预设的分区内community属性发送规则，如果符合，第二网络分区的数据交换系统将该BGP路由项转发给所有与其相连的第二网络分区的节点服务器。
例如，可以在深圳网络分区的数据交换系统上设置分区内community属性发送规则为community属性值为AA:200，即BGP路由项所属节点服务器的源网络分区可以为任意网络分区，目的网络分区为深圳，深圳网络分区的数据交换系统只能将目的网络分区为深圳的BGP路由项发送给深圳网络分区的节点服务器。参考表1可知，当深圳网络分区的数据交换系统接收到BGP路由项11和BGP路由项12时，BGP路由项11和BGP路由项12包含的community属性值符合上述分区内community属性发送规则，因此，深圳网络分区的数据交换系统可以将BGP路由项11和BGP路由项12发送给深圳网络分区的节点服务器。
第一网络分区的数据交换系统在接收到第一网络分区的节点服务器发来的BGP路由项后，如果BGP路由项的目的网络分区为第一网络分区，第一网络分区的数据交换系统可以直接对其进行处理，相应的处理可以如下：第一网络分区的数据交换系统判断BGP路由项包含的community属性值是否符合本地预设的分区内community属性发送规则；如果符合，第一网络分区的数据交换系统则将BGP路由项发送给第一网络分区的节点服务器。
在实施中，第一网络分区的数据交换系统接收到的BGP路由项可能来源与第一网络分区的节点服务器，也可能来源于其他网络分区的数据交换系统，对于来源于其他网络分区的数据交换系统的BGP路由项的处理，前文已经进行了说明，在此不再赘述，这里对来源与第一网络分区的节点服务器的BGP路由项的处理，进行说明。如前文所述，在第一网络分区的数据交换系统上还预先设置有分区内community属性发送规则，在接收到第一网络分区的节点服务器发来的BGP路由项后，第一网络分区的数据交换系统还可以进一步判断BGP路由项的community属性是否符合第一网络分区的数据交换系统本地预设的分区内community属性发送规则，如果符合，第一网络分区的数据交换系统可以将该BGP路由项转发给所有与其相连的第一网络分区的节点服务器。
例如，可以在杭州网络分区的数据交换系统上设置分区内community属性发送规则为community属性值为100:100，即BGP路由项所属节点服务器的源网络分区为杭州，目的网络分区也为杭州，杭州网络分区的数据交换系统可以将从杭州网络分区的节点服务器接收到的BGP路由项发送给杭州网络分区的节点服务器。参考表1可知，当杭州网络分区的数据交换系统接收到BGP路由项11和BGP路由项12时，BGP路由项11包含的community属性值不符合上述分区内community属性发送规则，因此，杭州网络分区的数据交换系统不能将BGP路由项11发送给杭州网络分区的节点服务器；而BGP路由项12包含的community属性值符合上述分区内community属性发送规则，因此，杭州网络分区的数据交换系统可以直接将BGP路由项12转发给所有与杭州网络分区的数据交换系统相连的杭州网络分区的节点服务器。这样，通过在数据交换系统上设置分区内community属性发送规则，数据交换系统可以对从同一网络分区的节点服务器接收到的BGP路由项进行筛选过滤，只有预先规划的BGP路由项才能被该数据交换系统发送给同一网络分区内的其他节点服务器，避免非规划的BGP路由项被同一网络分区内的其他节点服务器学习到，提高安全性。
上述方法在实施过程中，每个网络分区的数据交换系统可以由至少一个区域核心交换机构成。上述方法中在数据交换系统上预设的分区内community属性接收规则、分区间community属性发送规则表、分区间community属性接收规则表和分区内community属性发送规则均设置在对应网络分区的区域核心交 换机上。
上述方法在实施过程中，每个分区的数据交换系统也可以由至少一个区域核心交换机和至少一个区域中转交换机组成。在同一个网络分区内，区域核心交换机与区域中转交换机建立有BGP会话，区域中转交换机与每个节点服务器建立有BGP会话；在不同网络分区之间，每个网络分区的区域核心交换机之间建立有BGP会话。分区内community属性接收规则和分区内community属性发送规则设置在对应网络分区的区域中转交换机上，分区间community属性发送规则表和分区间community属性接收规则表设置在对应网络分区的区域核心交换机上。
故而，上述方法中BGP路由项的传输过程可以是：第一网络分区的区域中转交换机根据本地预设的分区内community属性接收规则接收第一网络分区的节点服务器宣告的更新后的BGP路由项，然后发送给第一网络分区的区域核心交换机；第一网络分区的核心交换机根据本地预设的分区间community属性发送规则表将BGP路由项发送给第二网络分区的核心交换机；第二网络分区的核心交换机根据本地预设的分区间community属性接收规则表接收第一网络分区的区域核心交换机发来的BGP路由项，并发送给第二网络分区的区域中转交换机；第二网络分区的中转交换机根据本地预设的分区内community属性发送规则，将接收到的BGP路由项发送给第二网络分区的节点服务器。传输过程的具体内容与前文相似，在此不再赘述。
为了避免节点之间建立路由后，线路发生故障而路由仍然存在，导致数据仍然通过该路由发送时被丢弃，相应的处理可以如下：目标节点服务器周期性向接收到的BGP路由项对应的节点服务器发送状态检测报文；如果目标节点服务器没有接收到BGP路由项对应的节点服务器返回的状态响应报文，则目标节点服务器删除BGP路由项。
在实施中，还可以在BGP网络中使用BFD(Bidirectional Forwarding Detection，双向转发检测)对建立路由关系的节点服务器之间的线路进行检测，检测时，目标节点服务器可以周期性的向接收到的BGP路由项对应的节点服务器发送BFD控制报文(状态检测报文)，在设置时间内如果目标节点服务器没有收到BGP路由项对应的节点服务器返回的BFD控制报文(状态响应报文)，目标节点服务器会重新发送BFD控制报文，如果重复发送几次后仍未收到BGP 路由项对应的节点服务器返回的BFD控制报文，则说明目标节点服务器到该BGP路由项对应的节点服务器的线路出现问题，此时，目标节点服务器在本地的BGP路由表中删除该BGP路由项。
本发明实施例中，第一网络分区的数据交换系统接收目标节点服务器宣告的更新后的BGP路由项，BGP路由项包含目标节点服务器的目标网段的网段标识和对应的community属性值；第一网络分区的数据交换系统根据BGP路由项包含的community属性值，将BGP路由项发往第二网络分区的数据交换系统；第二网络分区的数据交换系统将BGP路由项转发给第二网络分区的节点服务器。这样，可以通过community属性值确定可以接收BGP路由项的节点服务器，使得BGP路由项只能被指定的节点服务器收到，降低了传输BGP路由项过程中的流量消耗，避免BGP路由项可以从其他节点服务器获得，提高安全性。
基于相同的技术构思，本发明实施例还提供了一种云网传输路由系统，如图2所示，所述系统适用于BGP网络，所述BGP网络可以分为多个网络分区，每个网络分区包括数据交换子系统和多个节点服务器，所述数据交换子系统与每个所述节点服务器建立有BGP会话，所述系统包括：
第一网络分区的数据交换子系统，用于接收目标节点服务器宣告的更新后的BGP路由项，并根据所述BGP路由项包含的community属性值，将所述BGP路由项发往第二网络分区的数据交换子系统，所述BGP路由项包含所述目标节点服务器的目标网段的网段标识和对应的community属性值。
第二网络分区的数据交换子系统，用于将所述BGP路由项转发给所述第二网络分区的节点服务器。
可选的，所述第一网络分区的数据交换子系统，具体用于：
判断所述BGP路由项包含的community属性值是否符合本地预设的分区内community属性接收规则；
如果符合，则接收目标节点服务器宣告的更新后的BGP路由项。
可选的，所述第一网络分区的数据交换子系统，具体用于：
在本地预设的分区间community属性发送规则表中，确定所述BGP路由项包含的community属性值符合的目标分区间community属性发送规则；
确定所述目标community属性发送规则指向的第二网络分区，将所述BGP 路由项发往第二网络分区的数据交换子系统。
可选的，所述第二网络分区的数据交换子系统，具体用于：
判断所述BGP路由项包含的community属性值是否符合本地预设的分区内community属性发送规则；
如果符合，则将所述BGP路由项转发给所述第二网络分区的节点服务器。
可选的，所述第二网络分区的数据交换子系统，具体用于：
判断所述BGP路由项包含的community属性值是否符合本地预设的分区间community属性接收规则表中的分区间community属性接收规则；
如果符合，将所述BGP路由项发往所述第二网络分区的节点服务器。
可选的，所述第一网络分区的数据交换子系统，还用于：
判断所述BGP路由项包含的community属性值是否符合本地预设的分区内community属性发送规则；
如果符合，则将所述BGP路由项发送给所述第一网络分区的节点服务器。
可选的，所述数据交换子系统包括至少一个区域核心交换机。
可选的，所述数据交换子系统还包括至少一个区域中转交换机，所述区域中转交换机与每个所述节点服务器及所述区域核心交换机建立有BGP会话。
可选的，所述节点服务器，还用于：
周期性向BGP路由项对应的节点服务器发送状态检测报文；
如果没有接收到BGP路由项对应的节点服务器返回的状态响应报文，则删除所述BGP路由项。
需要说明的是：上述实施例提供的云网传输路由系统与云网传输路由方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到各实施方式可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件。基于这样的理解，上述技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务端，或者网络设备等)执行各个实施例或者实施例 的某些部分所述的方法。
以上所述仅为本发明的较佳实施例，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (18)

  1. 一种云网传输路由方法，其特征在于，所述方法适用于BGP网络，所述BGP网络可以分为多个网络分区，每个网络分区包括数据交换系统和多个节点服务器，所述数据交换系统与每个所述节点服务器建立有BGP会话，所述方法包括：
    第一网络分区的数据交换系统接收目标节点服务器宣告的更新后的BGP路由项，所述BGP路由项包含所述目标节点服务器的目标网段的网段标识和对应的community属性值；
    所述第一网络分区的数据交换系统根据所述BGP路由项包含的community属性值，将所述BGP路由项发往第二网络分区的数据交换系统；
    所述第二网络分区的数据交换系统将所述BGP路由项转发给所述第二网络分区的节点服务器。
  2. 根据权利要求1所述的方法，其特征在于，所述第一网络分区的数据交换系统接收目标节点服务器宣告的更新后的BGP路由项，包括：
    所述第一网络分区的数据交换系统判断所述BGP路由项包含的community属性值是否符合本地预设的分区内community属性接收规则；
    如果符合，所述第一网络分区的数据交换系统接收所述目标节点服务器宣告的更新后的BGP路由项。
  3. 根据权利要求1所述的方法，其特征在于，所述第一网络分区的数据交换系统根据所述BGP路由项包含的community属性值，将所述BGP路由项发往第二网络分区的数据交换系统，包括：
    所述第一网络分区的数据交换系统在本地预设的分区间community属性发送规则表中，确定所述BGP路由项包含的community属性值符合的目标分区间community属性发送规则；
    所述第一网络分区的数据交换系统确定所述目标community属性发送规则指向的第二网络分区，将所述BGP路由项发往第二网络分区的数据交换系统。
  4. 根据权利要求1所述的方法，其特征在于，所述第二网络分区的数据交换系统将所述BGP路由项转发给所述第二网络分区的节点服务器，包括：
    所述第二网络分区的数据交换系统判断所述BGP路由项包含的community属性值是否符合本地预设的分区内community属性发送规则；
    如果符合，所述第二网络分区的数据交换系统则将所述BGP路由项转发给所述第二网络分区的节点服务器。
  5. 根据权利要求1所述的方法，其特征在于，所述第二网络分区的数据交换系统将所述BGP路由项转发给所述第二网络分区的节点服务器，包括：
    所述第二网络分区的数据交换系统判断所述BGP路由项包含的community属性值是否符合本地预设的分区间community属性接收规则表中的分区间community属性接收规则；
    如果符合，所述第二网络分区的数据交换系统将所述BGP路由项发往所述第二网络分区的节点服务器。
  6. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一网络分区的数据交换系统判断所述BGP路由项包含的community属性值是否符合本地预设的分区内community属性发送规则；
    如果符合，所述第一网络分区的数据交换系统则将所述BGP路由项发送给所述第一网络分区的节点服务器。
  7. 根据权利要求1-6任一所述的方法，其特征在于，所述数据交换系统包括至少一个区域核心交换机。
  8. 根据权利要求7所述的方法，其特征在于，所述数据交换系统还包括至少一个区域中转交换机，所述区域中转交换机与每个所述节点服务器及所述区域核心交换机建立有BGP会话。
  9. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    目标节点服务器周期性向BGP路由项对应的节点服务器发送状态检测报 文；
    如果目标节点服务器没有接收到BGP路由项对应的节点服务器返回的状态响应报文，则所述目标节点服务器删除所述BGP路由项。
  10. 一种云网传输路由系统，其特征在于，所述系统适用于BGP网络，所述BGP网络可以分为多个网络分区，每个网络分区包括数据交换子系统和多个节点服务器，所述数据交换子系统与每个所述节点服务器建立有BGP会话，所述系统包括：
    第一网络分区的数据交换子系统，用于接收目标节点服务器宣告的更新后的BGP路由项，并根据所述BGP路由项包含的community属性值，将所述BGP路由项发往第二网络分区的数据交换子系统，所述BGP路由项包含所述目标节点服务器的目标网段的网段标识和对应的community属性值；
    第二网络分区的数据交换子系统，用于将所述BGP路由项转发给所述第二网络分区的节点服务器。
  11. 根据权利要求10所述的系统，其特征在于，所述第一网络分区的数据交换子系统，具体用于：
    判断所述BGP路由项包含的community属性值是否符合本地预设的分区内community属性接收规则；
    如果符合，则接收所述目标节点服务器宣告的更新后的BGP路由项。
  12. 根据权利要求10所述的系统，其特征在于，所述第一网络分区的数据交换子系统，具体用于：
    在本地预设的分区间community属性发送规则表中，确定所述BGP路由项包含的community属性值符合的目标分区间community属性发送规则；
    确定所述目标community属性发送规则指向的第二网络分区，将所述BGP路由项发往第二网络分区的数据交换子系统。
  13. 根据权利要求10所述的系统，其特征在于，所述第二网络分区的数据交换子系统，具体用于：
    判断所述BGP路由项包含的community属性值是否符合本地预设的分区内community属性发送规则；
    如果符合，则将所述BGP路由项转发给所述第二网络分区的节点服务器。
  14. 根据权利要求10所述的系统，其特征在于，所述第二网络分区的数据交换子系统，具体用于：
    判断所述BGP路由项包含的community属性值是否符合本地预设的分区间community属性接收规则表中的分区间community属性接收规则；
    如果符合，将所述BGP路由项发往所述第二网络分区的节点服务器。
  15. 根据权利要求10所述的系统，其特征在于，所述第一网络分区的数据交换子系统，还用于：
    判断所述BGP路由项包含的community属性值是否符合本地预设的分区内community属性发送规则；
    如果符合，则将所述BGP路由项发送给所述第一网络分区的节点服务器。
  16. 根据权利要求10-15任一所述的系统，其特征在于，所述数据交换子系统包括至少一个区域核心交换机。
  17. 根据权利要求16所述的系统，其特征在于，所述数据交换子系统还包括至少一个区域中转交换机，所述区域中转交换机与每个所述节点服务器及所述区域核心交换机建立有BGP会话。
  18. 根据权利要求10所述的系统，其特征在于，所述节点服务器，还用于：
    周期性向BGP路由项对应的节点服务器发送状态检测报文；
    如果没有接收到BGP路由项对应的节点服务器返回的状态响应报文，则删除所述BGP路由项。
PCT/CN2019/071877 2018-11-28 2019-01-16 云网传输路由方法和系统 Ceased WO2020107678A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19890293.4A EP3886376A4 (en) 2018-11-28 2019-01-16 Cloud network transmission routing method and system
US17/044,641 US20210105204A1 (en) 2018-11-28 2019-01-16 Cloud network transmission routing method and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811435777.5 2018-11-28
CN201811435777.5A CN109412942B (zh) 2018-11-28 2018-11-28 云网传输路由方法和系统

Publications (1)

Publication Number Publication Date
WO2020107678A1 true WO2020107678A1 (zh) 2020-06-04

Family

ID=65456056

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/071877 Ceased WO2020107678A1 (zh) 2018-11-28 2019-01-16 云网传输路由方法和系统

Country Status (4)

Country Link
US (1) US20210105204A1 (zh)
EP (1) EP3886376A4 (zh)
CN (1) CN109412942B (zh)
WO (1) WO2020107678A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110430134B (zh) * 2019-06-21 2021-05-07 网宿科技股份有限公司 云网传输路由方法和系统
CN113778995A (zh) * 2021-09-17 2021-12-10 中国建设银行股份有限公司 银行交易明细数据迁移方法及装置
CN114338747B (zh) * 2021-12-31 2023-07-25 四川启睿克科技有限公司 支持设备自定义上报数据报文的云端场景控制系统及方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101636724A (zh) * 2007-01-17 2010-01-27 北方电讯网络有限公司 用于使用了基于802.1ah的隧道的第2层和第3层虚拟专用网络的边界网关协议扩展团体属性
WO2016034226A1 (en) * 2014-09-03 2016-03-10 Telefonaktiebolaget L M Ericsson (Publ) Auto-discovery of packet islands over gmpls-uni
CN107078937A (zh) * 2014-10-26 2017-08-18 微软技术许可有限责任公司 用于计算机网络中的可达性管理的方法
CN108234305A (zh) * 2016-12-22 2018-06-29 上海诺基亚贝尔股份有限公司 一种跨机框链路冗余保护的控制方法及设备
US10135683B1 (en) * 2010-12-30 2018-11-20 Juniper Networks, Inc. Dynamically generating application-layer traffic optimization protocol endpoint attributes

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8385342B2 (en) * 2001-05-31 2013-02-26 Fujitsu Limited System and method of virtual private network route target filtering
US7920572B2 (en) * 2005-09-20 2011-04-05 Cisco Technology, Inc. Modifying operation of peer-to-peer networks based on integrating network routing information
US7865615B2 (en) * 2006-05-08 2011-01-04 Cisco Technology, Inc. Maintaining IGP transparency of VPN routes when BGP is used as a PE-CE protocol
JP4630225B2 (ja) * 2006-05-15 2011-02-09 富士通株式会社 通信制御システム
CN101931583B (zh) * 2009-06-18 2012-09-26 中兴通讯股份有限公司 域路由信息生成方法、装置以及路径计算方法、装置
CN102025599B (zh) * 2009-09-17 2014-10-22 中兴通讯股份有限公司 发起通信、信息/数据报文的转发及路由配置方法/系统
CN102447605A (zh) * 2010-09-30 2012-05-09 华为技术有限公司 一种请求获取路由信息的方法和相应的路由设备
CN102130834B (zh) * 2011-03-15 2014-04-02 杭州华三通信技术有限公司 一种ip路由方法和路由器
US9258210B2 (en) * 2013-10-01 2016-02-09 Juniper Networks, Inc. Dynamic area filtering for link-state routing protocols
CN105991441B (zh) * 2015-03-24 2019-08-06 杭州迪普科技股份有限公司 对bgp路由选择性下发路由转发表的方法和装置
US10135726B2 (en) * 2016-10-27 2018-11-20 Vmware, Inc. Virtualization port layer including physical switch port and logical switch port
CN108123876B (zh) * 2017-12-14 2020-08-11 新华三技术有限公司 边界网关协议bgp路由信息处理方法及装置
CN108616451B (zh) * 2018-04-25 2020-12-29 新华三技术有限公司 一种Flow Spec路由生效方法、装置及网络设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101636724A (zh) * 2007-01-17 2010-01-27 北方电讯网络有限公司 用于使用了基于802.1ah的隧道的第2层和第3层虚拟专用网络的边界网关协议扩展团体属性
US10135683B1 (en) * 2010-12-30 2018-11-20 Juniper Networks, Inc. Dynamically generating application-layer traffic optimization protocol endpoint attributes
WO2016034226A1 (en) * 2014-09-03 2016-03-10 Telefonaktiebolaget L M Ericsson (Publ) Auto-discovery of packet islands over gmpls-uni
CN107078937A (zh) * 2014-10-26 2017-08-18 微软技术许可有限责任公司 用于计算机网络中的可达性管理的方法
CN108234305A (zh) * 2016-12-22 2018-06-29 上海诺基亚贝尔股份有限公司 一种跨机框链路冗余保护的控制方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3886376A4 *

Also Published As

Publication number Publication date
US20210105204A1 (en) 2021-04-08
EP3886376A1 (en) 2021-09-29
CN109412942B (zh) 2020-12-29
CN109412942A (zh) 2019-03-01
EP3886376A4 (en) 2022-01-19

Similar Documents

Publication Publication Date Title
US10476793B2 (en) Multicast flow overlay using registration over a reliable transport
US7859992B2 (en) Router redundancy in data communication networks
EP2157746B1 (en) Routing control system for L3VPN service network
CN112929285B (zh) 区块链网络的通信优化系统
US8817798B2 (en) Constraining topology size and recursively calculating routes in large networks
WO2020001393A1 (zh) 发送网络性能参数、计算网络性能的方法和网络节点
US10263808B2 (en) Deployment of virtual extensible local area network
WO2021007963A1 (zh) 路由分发方法及控制器、信息路由方法及网络节点设备
US7539191B1 (en) System and method for securing route processors against attack
CN110932876B (zh) 一种通信系统、方法及装置
CN101364889B (zh) 一种快速接入组播用户的方法
CN109412942B (zh) 云网传输路由方法和系统
CN115801654A (zh) 路由通告方法、路径建立方法、业务数据的传输方法
CN106302076A (zh) 建立vxlan隧道的方法、系统及sdn控制器
CN104158736B (zh) 一种确定下一跳、发布路由信息的方法和装置
Jingjing et al. The deployment of routing protocols in distributed control plane of SDN
CN107968825B (zh) 一种报文转发控制方法及装置
JP6307031B2 (ja) ルートリフレクタおよびルートリフレクタの経路制御方法
CN106487682B (zh) 一种Diameter信令网路由方法和装置
CN110430134B (zh) 云网传输路由方法和系统
CN106878051B (zh) 一种多机备份实现方法及装置
CN119766647B (zh) 一种租户网关迁移的方法及装置、电子设备、存储介质
CN113765783B (zh) 通信方法及装置
JP4477318B2 (ja) 経路制御方法、そのデータ集約装置および経路制御システム
WO2020215713A1 (zh) 管理mac表的方法、网络设备、存储介质和程序产品

Legal Events

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

Ref document number: 19890293

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019890293

Country of ref document: EP

Effective date: 20210625