WO2020177540A1 - 基于rift协议的网络逻辑分层方法、装置、网络设备及存储介质 - Google Patents

基于rift协议的网络逻辑分层方法、装置、网络设备及存储介质 Download PDF

Info

Publication number
WO2020177540A1
WO2020177540A1 PCT/CN2020/075952 CN2020075952W WO2020177540A1 WO 2020177540 A1 WO2020177540 A1 WO 2020177540A1 CN 2020075952 W CN2020075952 W CN 2020075952W WO 2020177540 A1 WO2020177540 A1 WO 2020177540A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
topology
tie
lie
network
Prior art date
Application number
PCT/CN2020/075952
Other languages
English (en)
French (fr)
Inventor
徐本崇
王会来
彭少富
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP20766989.6A priority Critical patent/EP3920486A4/en
Priority to US17/434,752 priority patent/US20220166710A1/en
Publication of WO2020177540A1 publication Critical patent/WO2020177540A1/zh

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/48—Routing tree calculation
    • 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
    • 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/64—Routing or path finding of packets in data switching networks using an overlay routing layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/15—Interconnection of switching modules
    • H04L49/1553—Interconnection of ATM switching modules, e.g. ATM switching fabrics
    • H04L49/1569—Clos switching fabrics

Definitions

  • the present disclosure relates to the field of communications, for example, to a network logic layering method, device, network device and storage medium based on the RIFT protocol.
  • RIFT Ribonuclear In Fat Tree
  • the fat tree topology is widely used in data center networks, and can also be used in areas such as metropolitan area networks and bearer networks.
  • the RIFT protocol has the following advantages: natural loop prevention, support for ZTP (Zero Touch Provisioning, zero-touch service provisioning), easy deployment, support for network self-checks, and can greatly reduce the number of routing tables of underlying devices, and support Very high level of ECMP (Equal-Cost Multipath Routing) etc.
  • the RIFT protocol does not support multi-topology or multi-instance to logically layer the network. Therefore, it is urgent to provide a solution to logically layer the network under the RIFT protocol.
  • the RIFT protocol-based network logic layering method, device, network equipment, and computer-readable storage medium are provided in the embodiments of the present invention to solve: how to implement network logic layering based on multiple topologies under the RIFT protocol; how to implement the network logic layering under the RIFT protocol Realize the layering of network logic based on multiple instances.
  • the embodiment of the present invention provides a network logic layering method based on the RIFT protocol, including:
  • the LIE message can indicate the topology ID of at least one topology supported by the source device that sends the message.
  • the TIE message contains neighbor information carrying the target topology ID and Metric (metric) information carrying the target topology ID.
  • the target topology ID is The topology ID indicated by the LIE message corresponding to the TIE message;
  • the network logic is layered.
  • the embodiment of the present invention also provides a network logic layering method based on the RIFT protocol, including:
  • both LIE messages and TIE messages include the instance ID option, and the instance ID option carries There is an instance ID of at least one instance supported by the source device that sends the message;
  • the network is logically layered based on the LIE message and TIE message received by the device.
  • the embodiment of the present invention also provides a network logic layering device, including:
  • the first message transceiver module is used to send LIE messages and TIE messages to other devices in the network, and to receive LIE messages and TIE messages sent by other devices in the network;
  • LIE messages can indicate the sending of the message
  • the TIE message contains neighbor information carrying the target topology ID and Metric information carrying the target topology ID.
  • the target topology ID is indicated by the LIE message corresponding to the TIE message Topology ID;
  • the first layered processing module is used to perform network logical layering based on the LIE message and TIE message received by the device.
  • the embodiment of the present invention also provides a network logic layering device, including:
  • the second message transceiver module is used to send LIE messages and TIE messages to other devices in the network, and receive LIE messages and TIE messages sent by other devices in the network; both LIE messages and TIE messages include Instance ID option, the instance ID option carries the instance ID of at least one instance supported by the source device sending the message;
  • the second layering processing module is used to logically layer the network based on the LIE message and the TIE message received by the device.
  • the embodiment of the present invention also provides a network device, which includes a processor, a memory, and a communication bus;
  • the communication bus is used to realize the connection and communication between the processor and the memory
  • the processor is used to execute the first network logic layered program stored in the memory to implement the steps of the first network logic layering method based on the RIFT protocol; and/or the processor is used to execute the second network logic layer stored in the memory Layer procedures to implement the steps of the second layered method of network logic based on the RIFT protocol.
  • the embodiment of the present invention also provides a computer storage medium, the computer-readable storage medium stores at least one of a first network logic layered program and a second network logic layered program, the first network logic layered program can be Or executed by multiple processors to implement the steps of the first RIFT-based network logic layering method; the second network logic layering program can be executed by one or more processors to implement the second RIFT-based The steps of the protocol's network logic layered approach.
  • the network device sends LIE messages and TIE messages to other devices in the network, and Receive LIE messages and TIE messages sent by other devices in the network, and then determine the topology route corresponding to the topology supported by the device based on the LIE messages and TIE messages received by the device to achieve network logical layering.
  • the LIE message can indicate the topology ID of at least one topology supported by the source device that sends the message
  • the TIE message contains neighbor information carrying the target topology ID and Metric information carrying the target topology ID
  • the target topology ID is and The topology ID carried in the LIE packet corresponding to the TIE packet
  • the network device can exchange LIE packets and TIE packets with other devices in the network to allow other devices in the network to understand the topology supported by the device, and The neighbor information and metric information of this device in this topology, this device can also understand the topology supported by other devices in the network and the neighbor information and metric information of other devices in the corresponding topology, so that the device can calculate what the device supports
  • the topological routing corresponding to the topological topology can also allow other devices to calculate the topological routing of the supported topology.
  • a topology ID is introduced in the LIE message and the TIE message.
  • the topology ID can be used to distinguish, thereby realizing a multi-topology network
  • the logical layering is conducive to the optimization of the configuration of communication resources and the improvement of the utilization of communication resources.
  • the LIE messages and TIE messages that the network device interacts with other devices on the network both include the instance ID option, and the instance ID option carries at least one instance of the instance supported by the source device that sent the message. ID, that is, the instances supported by each device in the network can be inconsistent.
  • the network device can determine the instances supported by other devices. Since the devices of different instances do not report messages, based on the different instances, each device in the network can determine at least two routing tables based on the received LIE message and TIE message, so as to realize the network connection based on the different instances.
  • the logical layering improves the optimal configuration level of the network.
  • FIG. 1 is a flowchart of a network logic layering method based on the RIFT protocol provided in Embodiment 1 of the present invention
  • FIG. 2 is a schematic diagram of a networking architecture provided in Embodiment 1 of the present invention.
  • FIG. 3 is a schematic structural diagram of a topology ID option provided in Embodiment 1 of the present invention.
  • FIG. 4 is a schematic structural diagram of a neighbor option carrying a target topology ID provided in Embodiment 1 of the present invention.
  • FIG. 5 is a schematic structural diagram of a metric option provided in Embodiment 1 of the present invention.
  • FIG. 6 is a flow chart of a method for network logic layering based on the RIFT protocol provided in the second embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of an instance ID option provided in Embodiment 2 of the present invention.
  • FIG. 8 is a flow chart of the network device provided in the second embodiment of the present invention determining a topology route based on the received LIE message and the TIE message;
  • FIG. 9 is a schematic structural diagram of a network logic layering device provided in Embodiment 4 of the present invention.
  • FIG. 10 is a schematic structural diagram of a network logic layering device provided in Embodiment 4 of the present invention.
  • FIG. 11 is a schematic diagram of a hardware structure of a network device provided in Embodiment 5 of the present invention.
  • FIG. 12 is a schematic diagram of an architecture of RIFT networking provided in Embodiment 6 of the present invention.
  • multiple topologies are often used. For example, only some devices in the network have the multicast function deployed, and some devices do not support the multicast function. Therefore, use multi-topology to logically layer the network and create a multicast topology for devices that support the multicast function. Functions can be used in these devices; for another example, not all nodes in the network are deployed with IPv6 (Internet Protocol Version 6, Internet Protocol Version 6) functions. In order to allow these devices with IPv6 functions to communicate based on IPv6, you can Use multiple topologies to create an IPv6 topology.
  • IPv6 Internet Protocol Version 6, Internet Protocol Version 6
  • Multi-topology can logically layer the network, allowing different communication data to be routed and transmitted in different topologies, thereby improving the optimal configuration and utilization of communication resources.
  • the RIFT protocol does not support the implementation of multiple topologies in the same instance, so this reduces the utilization of communication resources, is not conducive to the optimal configuration of communication resources, and is not conducive to the application of the RIFT protocol.
  • this embodiment provides a network logic layering method based on the RIFT protocol. Please refer to the flowchart of the network logic layering method based on the RIFT protocol shown in FIG. 1.
  • S102 Send LIE messages and TIE messages to other devices in the network, and receive LIE messages and TIE messages sent by other devices in the network.
  • a network device can send LIE messages and TIE messages to other devices in the network, and can also receive LIE messages and TIE messages sent by other devices in the network.
  • the timing of the two processes of sending LIE messages and TIE messages and receiving LIE messages and TIE messages sent by other devices is not Fixed: In some scenarios, the network device can first send LIE messages and TIE messages to other devices, and then receive LIE messages and TIE messages sent by other devices; in other scenarios, it can also The message is received first, and then the message is sent. The process of sending the LIE message and the TIE message and the process of receiving the LIE message and the TIE message may also be performed simultaneously.
  • the LIE message can indicate the topology ID of at least one topology supported by the source device that sends the message. It is understandable that the so-called source device refers to the network device that generates and sends the LIE message. Please refer to Figure 2 below. Schematic diagram:
  • network device A generates and sends an LIE message to network device B. Subsequently, network device B may forward the LIE message from network device A and send it to the network device C, but even though network device B sends the LIE message, network device B is not the source device of the LIE message.
  • the source device of the LIE message should be the network device A that generates and sends the LIE message.
  • the LIE message may include the topology ID of at least one topology supported by the source device.
  • the source device supports other topologies in addition to the default topology, so the source device
  • the sent LIE message may also carry the topology ID of at least one other topology supported by the source device.
  • a network device supports two topologies with topology identifiers "0" and "1" respectively.
  • the topology with the topology ID "0" is the topology supported by each device in the network by default, while the topology with the topology ID "1" is only the topology supported by some devices in the network.
  • the LIE message sent by the network device can only include the topology ID "1", because even if the topology ID "0" is not carried in the LIE message, other devices in the network can also know that the network device is It supports the topology with the topology ID "0".
  • the LIE message may include the topology ID of each topology supported by the source device.
  • the topology identifier of the topology supported by a network device includes “0", “1", and “3”.
  • the LIE message sent by the network device as the source device can also include the topology identifier, including "0", "1", and "3".
  • the LIE message carries a topology ID option, and the LIE message indicates the topology supported by the source device through the topology ID option.
  • Figure 3 shows a schematic structural diagram of a topology ID option provided by this embodiment:
  • the topology ID option 30 includes a flag (Flags) field 31 and a topology ID (Topology ID) field 32, where the Flags field 31 can indicate that the content carried in the following fields is the topology ID.
  • the Flags field 31 has a length of one byte (BYTE), and some bits may be reserved for subsequent function expansion.
  • the length of the topology ID field 32 can be configured as two BYTEs, which carry the topology ID of the topology supported by the source device.
  • the LIE message sent by a network device does not carry the topology ID option, it means that the network device only supports the default topology.
  • the TIE message includes neighbor information and metric (Metric) information.
  • the neighbor information and metric information in the TIE message both carry the target topology ID, and the target topology ID mentioned here is the corresponding LIE message.
  • the LIE message and the TIE message sent by a network device as the source device are related to each other. In this embodiment, the two are said to correspond to each other.
  • the neighbor information in the TIE message and the topology ID carried in the metric information are both the topology ID indicated in the corresponding LIE message.
  • the TIE message includes a Node TIE message and a Prefix TIE message, where the Node TIE message includes neighbor information carrying the target topology ID, a Node TIE message and a Prefix TIE message
  • the text includes Metric information carrying the target topology ID.
  • the neighbor information in the TIE message can be carried by neighbor options.
  • Figure 4 shows a neighbor option that carries the target topology ID.
  • the neighbor option 40 includes the Flags field 41 and the topology ID field 42, and the neighbor option 40 also includes the neighbor structure 43 of the structure.
  • the neighbor option 40 shown in FIG. 4 carries information about M neighbors.
  • the Flags field 41 and the topology ID field 42 in the neighbor option 40 are similar to the corresponding content in FIG. 3, and will not be repeated here.
  • the Metric information in the TIE message can be carried by the Metric option.
  • FIG. 5 shows a schematic diagram of the structure of a Metric option: the Metric option 50 includes the Flags field 51 and the topology ID field 52, and the Flags field 51 in the metric option 50 and The topology ID field 52 is similar to the corresponding content in FIG. 3 and FIG. 4, and will not be repeated here.
  • the Metric option 50 also includes a Metric field 53, and the Metric field 53 carries Metric information.
  • the network device in order for a network device to send the LIE message and TIE message described above to other devices in the network, the network device can establish a mapping relationship between its own interface and the topology that it only supports. That is to bind the interface with the topology supported by itself.
  • a network device supports two topologies with topology IDs "1" and "2".
  • the network device can bind the topology with the topology ID "1" to its own interface a, and the topology with the topology ID "2"
  • the topology is bound to interface b. It can be understood that, in some other examples of this embodiment, when the network device performs interface and topology binding, one interface can be bound to two or more topologies.
  • the LIE message sent from the interface will carry the topology ID of the topology corresponding to the interface, and the TIE message sent through the interface includes the neighbor information and the neighbor information carrying the corresponding topology ID. Metric information.
  • S104 Perform network logic layering based on the LIE message and the TIE message received by the device.
  • this device After receiving LIE messages and TIE messages sent by other devices in the network, this device can determine devices that are the same or partially the same as the topology supported by this device based on the received LIE messages and TIE messages, and then based The obtained neighbor information carrying the target topology ID and the metric information carrying the target topology ID are calculated to determine the topology route corresponding to the target topology ID.
  • a network device when routing is determined, the network device needs to determine topological routes for these multiple topologies separately, and determine the topological routes belonging to each topology, for example, suppose The network device supports two topologies with topology IDs "1" and "2".
  • the network device determines routing based on LIE messages and TIE messages received from other devices, it needs to set the topology ID to The topology of "1" calculates a topology route, and the topology of topology ID "2" calculates a topology route.
  • the network device After the network device determines the topology route corresponding to each topology supported by the device, if there is data that needs to be transmitted by the network device through a certain topology, the network device can query the forwarding path based on the corresponding topology route determined before. Realize data transmission.
  • the network logic layering method based on the RIFT protocol provided in this embodiment can be executed by network devices in the network. It is understandable that each network device in the network can execute the RIFT protocol-based network logic layering method, so as to determine the topology route corresponding to the topology supported by itself.
  • the network device in the network adds a topology ID that can indicate the topology supported by itself in the LIE message, and is included in the neighbor information and the metric information of the TIE message Carry the topology ID of the topology supported by itself, so that other devices in the network can understand the topology supported by the device, and understand the neighbor information and metric information of the device under the topology; at the same time, the device can also send through other devices
  • the LIE message and TIE message understand the topology supported by other devices, as well as the neighbor information and metric information of other devices in the corresponding topology, so that each device in the network can determine the topology route of its supported topology based on this information.
  • Multi-topology realizes the logical layering of the network to optimize the configuration of network communication resources.
  • the RIFT protocol only supports different UDP (User Datagram Protocol, User Datagram Protocol) port numbers to distinguish different instances, that is, first specify a specific UDP port number for an instance, and then distinguish instances based on the UDP port number.
  • UDP User Datagram Protocol
  • the UDP port number is a public resource. It is easy for users to specify the UDP port number of an instance to cause conflicts between the port number commanded for the instance and the well-known port number, and the well-known port number will continue to change with the development of the protocol, so use UDP port number to distinguish between instances is not conducive to RIFT protocol compatibility.
  • this embodiment provides a solution to realize the distinction of instances through the RIFT protocol. Please refer to the flowchart of the network logic layering method based on the RIFT protocol shown in FIG. 6:
  • S602 Send a LIE message and a TIE message to other devices in the network, and receive a LIE message and a TIE message sent by other devices in the network.
  • the instances supported by each network device may be the same. In this case, it is only possible to logically layer the network based on multiple topologies according to the introduction of the first embodiment. However, in some other instances of this embodiment, in a network, the instances supported by each network device may not be exactly the same. For example, some of the devices support instance 1, while other devices support instance 2. In this case, The logical layering of the network can also be realized based on multiple instances.
  • new configurations can be performed on the LIE message and TIE message sent by each network device:
  • FIG. 7 shows a schematic diagram of the structure of the instance ID option:
  • the instance ID option 70 includes an instance ID (Instance ID) field 71 and a logical topology field 72.
  • the instance ID field 71 includes the instance ID of at least one instance supported by the source device, and the logical topology field 72 may include the source device At least one topology ID option in this example, so the logical topology field 72 may include at least one topology ID option as shown in FIG. 3.
  • the logical topology field 72 may not carry any topology ID option. In this case, the characterizing source device only supports the default topology.
  • the network device in order to send LIE messages and TIE messages carrying the instance ID option to other devices in the network, the network device can first configure the mapping relationship between its own interface and the instance, bind the interface to the instance, and then The LIE message and TIE message are sent out through the interface bound to the corresponding instance, so that the sent LIE message and TIE message will carry the corresponding instance ID option.
  • S604 Logically layer the network based on the LIE message and the TIE message received by the device.
  • the network device After receiving the LIE message and TIE message sent by other devices in the network, the network device can determine the same devices in the network as the instance supported by this device based on these LIE messages and TIE messages, and the network devices in their Topology supported under the supported instance. Subsequently, the network device can determine the topology route of each topology supported by itself under the instance it supports based on the acquired information.
  • a network device can support more than one instance at the same time. For example, a network device supports both instance 1 and instance 2. In this case, although, instance 1 Both the packets of instance 2 and instance 2 can be received by the network device, but the network device does not need the LIE packets and TIE packets from instance 2 when determining the topology route under instance 1. Similarly, when determining the instance During the topology routing under 2, there is no need to care about the LIE message and TIE message sent by the network device in Example 1. Therefore, for supporting a certain instance, the LIE message and TIE message received by the network device are not both useful. Therefore, the following describes a scheme for determining topological routing in conjunction with Figure 8:
  • S802 Filter the received LIE messages and TIE messages, and retain the target LIE messages and target TIE messages.
  • the target LIE message refers to the LIE message that carries the same instance ID as the instance ID bound to the interface that receives the message
  • the target TIE message refers to the carried instance ID and the received instance ID.
  • a certain network device only supports instance 1, and the network device binds instance 1 to its own interface a. Then, the network device receives two packets from interface a, one of which contains the LIE message
  • the instance ID in the instance ID option carried in the TIE message and the instance ID option are both instance 1, but the instance ID in the LIE message and the instance ID option carried in the TIE message of the other message is "2", in this case
  • the network device only regards the LIE message in the first message as the target LIE message corresponding to example 1, and the TIE message in the first message as the target TIE message corresponding to example 1.
  • the network device can directly discard the message, that is, discard the second message. LIE message and TIE message in one message.
  • the network device when the network device filters the target TIE message, it not only requires that the instance ID carried in the target TIE message be consistent with the instance ID of the instance bound to the interface on which the network device receives the message, but also, It is also required that the message is sent by a neighbor of the network device. That is, in some cases, even if the instance ID carried in a TIE message meets the requirements, it is likely that the source device of the TIE message is not a neighbor of the network device, and therefore will be discarded by the network device.
  • S804 Logically layer the network based on the target LIE message and the target TIE message.
  • the network device can determine the topology route of each topology under the instance supported by the device based on the target LIE message and the target TIE message. For example, a certain network device only supports instance 1. In instance 1, the network device supports topology 1 and topology 2. Therefore, the topology route that the network device needs to determine ultimately includes the topology route of topology 1 under instance 1, and the topology route under instance 1. Topology routing for topology 2.
  • each network device in the network carries the instance ID option in the LIE message and TIE message sent by itself, and indicates this to other devices in the network through the instance ID option.
  • Each network device exchanges LIE messages and TIE messages to learn about the instances and topologies supported by other devices, and then realizes the logical division of the network on the basis of multiple instances.
  • the first embodiment provides a solution to achieve network logic layering based on multiple topologies
  • the second embodiment provides a solution to achieve network logic layering based on multiple instances. It can be understood that the logic of the network is When layering, you can combine the solutions of Embodiment 1 and Embodiment 2, and realize network layering based on multiple instances and multiple topologies at the same time:
  • each network device in the network will also exchange LIE messages and TIE messages.
  • the LIE message sent by the network device can not only indicate the source
  • the topology ID of at least one topology supported by the device and also includes an instance ID option.
  • the LIE message includes the topology ID option. Therefore, other devices are notified of the topology information supported by their own interface through the LIE message.
  • the TIE message not only includes neighbor information carrying the target topology ID and Metric information carrying the target topology ID, but also includes an instance ID option.
  • the Node TIE message supports the neighbor option that carries the topology ID and announces the remote's own neighbor information in a certain topology.
  • the Node TIE message and Prefix TIE message include the metric information that carries the topology ID, thereby notifying other devices in the network that they are Corresponding to the Metric information in the topology.
  • the network device in order to send LIE messages and TIE messages that comply with the above introduction to other devices, can first bind a certain instance it supports and a certain topology under that instance to one of its own interfaces.
  • the LIE message sent through the interface can naturally carry the corresponding topology ID option and the instance ID option
  • the TIE message sent through the interface naturally includes neighbor information and metric information carrying the target topology ID, and The corresponding instance ID.
  • the network device can also first filter the received messages according to the introduction in the second embodiment to determine the corresponding target LIE message and The target TIE message is then based on the information in the target LIE message and the target TIE message retained by the screening to determine the topology routing of each topology under the instance supported by the device.
  • the network logic layering method based on the RIFT protocol allows the receiver of the message to determine whether the instance ID in the message and the instance ID of the instance supported by the message is carried by the instance ID option in the LIE message If they are consistent, they are discarded if they are inconsistent, and the neighbor relationship is not established; at the same time, the TIE message carries the instance ID option, so that the message receiver can judge whether the message is sent by the neighbor of the instance it supports, and discard it if it is not.
  • Using different messages between instances when there are two or more instances in the network, let each instance determine the topology route separately.
  • topology ID that can indicate the topology supported by the source device in the LIE message
  • other devices in the network can be made Understand the topology supported by the device, and understand the neighbor information and metric information of the device under the topology, and then realize the logical layering of the network based on the multi-topology to optimize the configuration of network communication resources.
  • This embodiment provides a network logic layering device. Please refer to a schematic structural diagram of the network logic layering device 90 shown in FIG. 9:
  • the network logic layering device 90 includes a first message transceiving module 902 and a first layered processing module 904.
  • the first message transceiving module 902 is used to send LIE messages and TIE messages to other devices in the network, and Receive LIE messages and TIE messages sent by other devices in the network; LIE messages can indicate the topology ID of at least one topology supported by the source device that sent the message.
  • the TIE message contains neighbor information and the neighbor information that carries the target topology ID. Metric information carrying the target topology ID, the target topology ID is the topology ID indicated by the LIE message corresponding to the TIE message.
  • the first layering processing module 904 is configured to perform network logic layering based on the LIE message and the TIE message received by the device.
  • the network logic layered device 90 can be deployed on a network device, where the function of the first message transceiving module 902 can be realized by the communication unit and the processor of the network device, and the function of the first layered processing module 904 can be Realized by the processor of the network device.
  • the network logic layering device 90 can implement the RIFT protocol-based network logic layering method introduced in the first embodiment and the third embodiment. For the specific implementation process of the RIFT protocol-based network logic layering method, please refer to the introduction of the foregoing embodiment. I won't repeat it here.
  • This embodiment also provides another network logic layering device. Please refer to the schematic structural diagram shown in FIG. 10:
  • the network logic layered device 10 includes a second message transceiving module 102 and a second layered processing module 104, where the second message transceiving module 102 is used to send LIE messages and TIE messages to other devices in the network, and Receive LIE messages and TIE messages sent by other devices on the network; both LIE messages and TIE messages include an instance ID option, and the instance ID option carries at least one instance of an instance supported by the source device that sent the message ID and the topology ID of at least one topology under the instance.
  • the second layered processing module 104 is used to logically layer the network based on the LIE message and TIE message received by the device.
  • the network logic layered device 10 can also be deployed on a network device, where the function of the second message transceiving module 102 can be realized by the communication unit and the processor of the network device, and the function of the second layered processing module 104 is It can be implemented by the processor of the network device.
  • the network logic layering device 10 can implement the RIFT protocol-based network logic layering method introduced in the second embodiment and the third embodiment. For the specific implementation process of the RIFT protocol-based network logic layering method, please refer to the introduction of the foregoing embodiment. I won't repeat it here.
  • the network logic layering device provided in this embodiment expands the LIE message and the TIE message, so that the logical layering of the network can be realized based on multi-topology and/or multi-instance, which is conducive to improving the network through self-topology.
  • the utilization rate of communication resources and the optimal allocation of resources are optimized.
  • the computer-readable storage medium can store one or more computer programs that can be read, compiled, and executed by one or more processors.
  • the computer-readable storage medium may store one of a first network logic layered program and a second network logic layered program, wherein the first network logic layered program can be executed by one or more processors to implement the foregoing embodiments
  • the second network logic layering program can be executed by one or more processors to implement the flow of any one of the RIFT protocol-based network logic layering methods introduced in the second and third embodiments.
  • the network device 110 includes a processor 111, a memory 112, and a communication bus 113 for connecting the processor 111 and the memory 112, where the memory 112 may be the aforementioned storage
  • the processor 111 can read the first network logic layering program, compile and execute the process of implementing the network logic layering method based on the RIFT protocol introduced in the first embodiment and the third embodiment:
  • the processor 111 sends LIE messages and TIE messages to other devices in the network, and receives LIE messages and TIE messages sent by other devices in the network. Then, based on the LIE message and TIE message received by the device, the topology route corresponding to the topology supported by the device is determined, and the logical layering of the network is realized based on the topology.
  • the LIE message can indicate the topology ID of at least one topology supported by the source device that sends the message.
  • the TIE message contains neighbor information carrying the target topology ID and metric information carrying the target topology ID.
  • the target topology ID is The topology ID indicated by the LIE message corresponding to the TIE message.
  • the processor 111 may bind the topology supported by the network device 110 with the interface of the device, and send LIE messages and TIE messages to other devices in the network through the interface.
  • the TIE message sent by the processor 111 includes a Node TIE message and a Prefix TIE message; wherein, the Node TIE message includes neighbor information carrying the target topology ID, and the Node TIE message and the Prefix TIE message include Include Metric information carrying the target topology ID.
  • the processor 111 may also read the second network logic layering program, compile and execute the process of implementing the network logic layering method based on the RIFT protocol introduced in the second embodiment and the third embodiment:
  • the processor 111 sends LIE messages and TIE messages to other devices in the network, and receives LIE messages and TIE messages sent by other devices in the network. Both the LIE message and the TIE message include an instance ID option. The instance ID option carries the instance ID of at least one instance supported by the active device. After receiving the LIE message and the TIE message sent by other devices, the processor 111 performs network logical layering based on the LIE message and TIE message received by the device.
  • the processor 111 may bind the instance supported by the device with the interface of the device, and send the LIE message and the TIE message to other devices in the network through the interface.
  • the processor 111 determines the topology route corresponding to each topology in the instance supported by the device based on the LIE message and TIE message received by the device, it can filter the received LIE message and TIE message , Reserve the target LIE message and the target TIE message, the target LIE message is the LIE message that carries the same instance ID as the instance ID bound to the interface that receives the message, and the target TIE message is the carried instance ID A TIE packet that is the same as the instance ID bound to the interface that received the packet and sent by the neighboring device of the device under the instance ID. After screening, the network logic is layered based on the target LIE message and the target TIE message.
  • the processor 111 of the network device 110 executes at least one of the first network logic layering program and the second network logic layering program to implement the network logic layering method based on the RIFT protocol.
  • the processor 111 of the network device 110 executes at least one of the first network logic layering program and the second network logic layering program to implement the network logic layering method based on the RIFT protocol.
  • Embodiment 6 is a diagrammatic representation of Embodiment 6
  • this embodiment will continue to perform the routing determination solution in the foregoing embodiment in combination with specific examples and the RIFT networking architecture shown in FIG. 12 Introduction:
  • Example 1- Realize the logical layering of the network based on multiple topologies.
  • the topology ID option is added to the LIE message, and the structure of the topology ID option is shown in Figure 3.
  • the LIE message sent by a certain network device does not carry the topology ID option, it means that the network device only supports the default topology.
  • the neighbor information that carries the topology ID can be added, for example, through the neighbor option shown in FIG. 4.
  • “Neighbor structure” is the neighbor structure specified by the RIFT protocol, which is used to characterize neighbors. It is understandable that a TIE message can carry multiple neighbor options.
  • the Metric information carrying the topology ID can be added to the TIE message, for example, carried by the Metric option shown in FIG. 5.
  • a TIE message can carry multiple Metric options.
  • the network device can bind an interface of the device to a specific topology through configuration commands or other methods.
  • Node111, Node122, and Spine22 do not support multicast functions (for example, IPv4 multicast functions), and the topology ID of the multicast topology is "1".
  • all nodes in Figure 12 support topology 0 by default.
  • Leaf011 node For the Leaf011 node, it will bind itself to topology 1 except for the interface connected to Node111; for the Leaf012 node, it will bind itself to topology 1 except for the interface connected to Node111. Medium; for the Leaf021 node, it will bind itself to topology 1 except for the interface connected to Node122; for the Leaf022 node, it will bind itself to all other interfaces except the interface connected to Node122 Topology 1.
  • Node112 node For the Node112 node, it will bind itself to topology 1 except for the interface connected to Spine22; for the Node121 node, it will bind itself to topology 1 except for the interface connected to Spine22 in.
  • the LIE messages sent by these interfaces will carry the topology ID option, and the topology ID in the topology ID option is "1".
  • the Node TIE messages sent by these interfaces contain the neighbor option carrying the topology ID "1”
  • the Node TIE messages and Prefix TIE messages contain the metric option carrying the topology ID "1".
  • each node supports the default topology of topology 0. At the same time, some nodes support topology 1. Therefore, nodes that support topology 1 will calculate the topology route separately for topology 1. The route of topology 1 is used for multicast selection. The interface that is not bound to topology 1 does not participate in the topology routing calculation.
  • the instance ID option is added to the LIE message.
  • the structure of the instance ID option is shown in Figure 7. In this embodiment, if the LIE message sent by a certain network device does not carry the instance ID option, the network device only supports the default instance (instance 0) by default.
  • the instance ID option shown in Figure 7 is also added to the TIE message.
  • the network device can bind an interface of the device to a specific instance through configuration commands or other methods.
  • Leaf011, Node111, Spine21, Node121, and Leaf021 support the topology 1 of instance 1, these nodes can connect themselves to any of the four nodes.
  • the interface is bound to topology 1 of instance 1.
  • LIE messages and TIE messages sent by these interfaces will both carry an instance ID option.
  • the instance ID carried in the instance ID option is "1" and the topology ID is "1".
  • the packet is discarded.
  • the network device determines whether the instance ID carried in the message is consistent with the instance ID bound to the interface that receives the TIE message, and when it is determined that they are consistent, it determines whether the device belongs to the instance. If the result of the judgment is no, the packet will be discarded. If it is determined that the instance ID carried in the TIE message is consistent with the instance ID bound to the interface that receives the TIE message, and it is determined that it was sent by the neighbor of the device, the TIE is sent to the neighbor of the same instance according to the TIE flooding rules Message.
  • the network device After the network device receives the LIE message and the TIE message sent by other devices, it can calculate the topology route for each instance and each topology that it supports.
  • the network device can bind a certain interface of the device to the specific topology of a specific instance through configuration commands or other methods.
  • Leaf011 binds all its interfaces to topology 1 and topology 2 under instance 1.
  • the interface binding relationship of Leaf011 is recorded as "1.1+1.2";
  • Leaf012 binds all its interfaces to Topology 1 and Topology 2 under instance 2.
  • the interface binding relationship of Leaf012 is recorded as "2.1+2.2";
  • Node111 binds all its interfaces to Topology 1 and Topology 2 under instance 1.
  • the interface binding relationship of Node111 is recorded as "1.1+1.2";
  • Node 112 binds all its interfaces to instance 2 topology 2.
  • the interface binding relationship of Node 111 is recorded as "2.2".
  • each node uses the corresponding interface to send the LIE message and the TIE message, so that the sent LIE message carries the corresponding topology ID option and the instance ID option, so that the sent TIE message contains the corresponding topology ID.
  • the neighbor option and the Metric option of, carry the corresponding instance ID option at the same time.
  • each network device After each network device receives the LIE message and the TIE message from other network devices, it will filter and forward it according to the introduction in Example 2. For the specific process, please refer to the introduction of the foregoing example, and will not be repeated here.
  • Leaf012 and Node112 are the same, neighbor relationships can be established normally and TIE messages can be exchanged. At the same time, because these two nodes support topology 2, the route of topology 2 can be calculated normally, but because Node 112 does not support topology 1, the route of topology 1 cannot be calculated.
  • the functional modules/units in the system, and the device can be implemented as software (which can be implemented by program code executable by a computing device) , Firmware, hardware and their appropriate combination.
  • the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may consist of several physical components. The components are executed cooperatively.
  • Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit .
  • the computer-readable medium may include computer storage Medium (or non-transitory medium) and communication medium (or temporary medium).
  • computer storage medium includes volatile and non-volatile data implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data).
  • flexible, removable and non-removable media are examples of computer storage Medium.
  • Computer storage media include but are not limited to Random Access Memory (RAM), Read-Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash memory Or other memory technologies, compact Disc Read Only Memory (CD-ROM), Digital Video Disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage
  • RAM Random Access Memory
  • ROM Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • CD-ROM Compact Disc Read Only Memory
  • DVD Digital Video Disk
  • communication media usually contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery media . Therefore, the present disclosure is not limited to any specific hardware and software combination.

Landscapes

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

Abstract

本发明实施例提供一种基于RIFT协议的网络逻辑分层方法、装置、网络设备及存储介质，网络设备通过与其他设备交换链路信息元素LIE报文和拓扑信息元素TIE报文，能够让网络中其他设备了解本设备所支持的拓扑，以及本设备在该拓扑下的邻居信息与度量Metric信息，本设备也能了解网络中其他设备所支持的拓扑以及其他设备在对应拓扑下的邻居信息与Metric信息，进而让本设备计算出本设备所支持的拓扑所对应的拓扑路由。

Description

基于RIFT协议的网络逻辑分层方法、装置、网络设备及存储介质
本申请要求在2019年03月01日提交中国专利局、申请号为201910157607.3的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本公开涉及通信领域，例如涉及一种基于RIFT协议的网络逻辑分层方法、装置、网络设备及存储介质。
背景技术
RIFT(Routing In Fat Tree，胖树路由)作为为胖树(Fat Tree)拓扑设计的一种路由协议，正在兴起阶段。胖树拓扑广泛用于数据中心网络中，并且也可以在城域网、承载网等领域使用。和传统路由协议相比，RIFT协议具有以下优势：天然防环、支持ZTP(Zero Touch Provisioning，零接触服务开通)、部署方便、支持网络自检、可以极大减少底层设备的路由表数量、支持很高程度的ECMP(Equal-Cost Multi path Routing，等价路由)等。
RIFT协议不支持多拓扑或多实例对网络的逻辑分层，所以，亟需提供一种解决方案，用以在RIFT协议下对网络进行逻辑分层。
发明内容
本发明实施例提供的基于RIFT协议的网络逻辑分层方法、装置、网络设备及计算机可读存储介质，以解决：如何在RIFT协议下基于多拓扑实现对网络逻辑分层；如何在RIFT协议下基于多实例实现对网络逻辑分层。
本发明实施例提供一种基于RIFT协议的网络逻辑分层方法，包括：
向网络中的其他设备发送LIE(Link Information Element，链路信息元素)报文和TIE(Topology Information Element，拓扑信息元素)报文，并接收网络中其他设备发送的LIE报文和TIE报文；LIE报文能够指示发送该报文的源设备所支持的至少一个拓扑的拓扑ID，TIE报文中包含携带目标拓扑ID的邻居信息与携带目标拓扑ID的Metric(度量)信息，目标拓扑ID为与该TIE报文对应的LIE报文所指示的拓扑ID；
基于本设备所接收到的LIE报文和TIE报文进行网络逻辑分层。
本发明实施例还提供一种基于RIFT协议的网络逻辑分层方法，包括：
向网络中的其他设备发送LIE报文和TIE报文，并接收网络中其他设备发送的LIE报文和TIE报文；LIE报文和TIE报文中均包括实例ID选项，实例ID选项中携带有发送该报文的源设备所支持的至少一个实例的实例ID；
基于本设备所接收到的LIE报文和TIE报文对网络进行逻辑分层。
本发明实施例还提供一种网络逻辑分层装置，包括：
第一报文收发模块，用于向网络中的其他设备发送LIE报文和TIE报文，并接收网络中其他设备发送的LIE报文和TIE报文；LIE报文能够指示发送该报文的源设备所支持的至少一个拓扑的拓扑ID，TIE报文中包含携带目标拓扑ID的邻居信息与携带目标拓扑ID的Metric信息，目标拓扑ID为与该TIE报文对应的LIE报文所指示的拓扑ID；
第一分层处理模块，用于基于本设备所接收到的LIE报文和TIE报文进行网络逻辑分层。
本发明实施例还提供一种网络逻辑分层装置，包括：
第二报文收发模块，用于向网络中的其他设备发送LIE报文和TIE报文，并接收网络中其他设备发送的LIE报文和TIE报文；LIE报文和TIE报文中均包括实例ID选项，实例ID选项中携带有发送该报文的源设备所支持的至少一个实例的实例ID；
第二分层处理模块，用于基于本设备所接收到的LIE报文和TIE报文对网络进行逻辑分层。
本发明实施例还提供一种网络设备，该网络设备包括处理器、存储器及通信总线；
通信总线用于实现处理器和存储器之间的连接通信；
处理器用于执行存储器中存储的第一网络逻辑分层程序，以实现上述第一种基于RIFT协议的网络逻辑分层方法的步骤；和/或处理器用于执行存储器中存储的第二网络逻辑分层程序，以实现上述第二种基于RIFT协议的网络逻辑分层方法的步骤。
本发明实施例还提供一种计算机存储介质，该计算机可读存储介质存储有第一网络逻辑分层程序和第二网络逻辑分层程序中的至少一个，第一网络逻辑分层程序可被一个或者多个处理器执行，以实现上述第一种基于RIFT协议的网络逻辑分层方法的步骤；第二网络逻辑分层程序可被一个或者多个处理器执行，以实现上述第二种基于RIFT协议的网络逻辑分层方法的步骤。
根据本发明实施例提供的基于RIFT协议的网络逻辑分层方法、装置、网络 设备及计算机可读存储介质，一方面，网络设备通过向网络中的其他设备发送LIE报文和TIE报文，并接收网络中其他设备发送的LIE报文和TIE报文，然后基于本设备所接收到的LIE报文和TIE报文确定本设备所支持的拓扑对应的拓扑路由，实现网络逻辑分层。由于LIE报文能够指示发送该报文的源设备所支持的至少一个拓扑的拓扑ID，而TIE报文中包含携带目标拓扑ID的邻居信息与携带目标拓扑ID的Metric信息，目标拓扑ID为与该TIE报文对应的LIE报文中所携带的拓扑ID，所以，网络设备通过与网络中其他设备交换LIE报文和TIE报文，能够让网络中其他设备了解本设备所支持的拓扑，以及本设备在该拓扑下的邻居信息与Metric信息，本设备也能了解网络中其他设备所支持的拓扑以及其他设备在对应拓扑下的邻居信息与Metric信息，进而让本设备计算出本设备所支持的拓扑所对应的拓扑路由，同时也能让其他设备计算出其所支持的拓扑的拓扑路由。本发明实施例提供的网络逻辑分层方案中，在LIE报文和TIE报文中引入了拓扑ID，在网络设备支持的拓扑不只一个时，可以通过拓扑ID进行区分，从而实现多拓扑的网络逻辑分层，有利于实现通信资源的优化配置，提升通信资源的利用率。
另一方面，网络设备同网络中其他设备所交互的LIE报文和TIE报文中均包括实例ID选项，该实例ID选项中携带有发送该报文的源设备所支持的至少一个实例的实例ID，也就是说，网络中各设备所支持的实例可以不一致。一个网络接收到其他设备发送的LIE报文和TIE报文之后，网络设备可以确定其他设备所支持的实例。由于不同实例的设备之间不通报文，因此基于实例的不同，网络中各设备基于接收到的LIE报文和TIE报文可以确定出至少两种路由表，从而基于实例的不同实现对网络的逻辑分层，提升了网络的优化配置水平。
附图说明
图1为本发明实施例一中提供的基于RIFT协议的网络逻辑分层方法的一种流程图；
图2为本发明实施例一中提供的一种组网架构示意图；
图3为本发明实施例一中提供的拓扑ID选项的一种结构示意图；
图4为本发明实施例一中提供的携带目标拓扑ID的邻居选项的一种结构示意图；
图5为本发明实施例一中提供的Metric选项的一种结构示意图；
图6为本发明实施例二中提供的基于RIFT协议的网络逻辑分层方法的一种 流程图；
图7为本发明实施例二中提供的实例ID选项的一种结构示意图；
图8为本发明实施例二中提供的网络设备基于接收到的LIE报文和TIE报文确定拓扑路由的一种流程图；
图9为本发明实施例四中提供的网络逻辑分层装置的一种结构示意图；
图10为本发明实施例四中提供的网络逻辑分层装置的一种结构示意图；
图11为本发明实施例五中提供的网络设备的一种硬件结构示意图；
图12为本发明实施例六中提供的RIFT组网的一种架构示意图。
具体实施方式
下面通过具体实施方式结合附图对本发明实施例作进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本公开，并不用于限定本公开。
实施例一：
现实中一些场景，经常需要用到多拓扑。例如，网络中只有部分设备部署了组播功能，另外一些设备并不支持组播功能，所以，使用多拓扑对网络进行逻辑分层，为支持组播功能的设备创建一个组播拓扑，这样，在这些设备中就可以使用功能；又如，网络中不是所有节点都部署了IPv6(Internet Protocol Version 6，互联网协议第6版)功能，为了让这些部署了IPv6功能设备可以基于IPv6进行通信，可以使用多拓扑创建一个IPv6拓扑。
多拓扑可以从逻辑上对网络进行分层，从而让不同的通信数据在不同的拓扑路由传输，从而提升通信资源的优化配置与利用率。不过，RIFT协议并不支持同一个实例多拓扑实现，所以，这降低了通信资源的利用率，不利于通信资源的优化配置，也不利于RIFT协议的应用。为了解决该问题，本实施例提供一种基于RIFT协议的网络逻辑分层方法，请参见图1示出的基于RIFT协议的网络逻辑分层方法的流程图：
S102：向网络中的其他设备发送LIE报文和TIE报文，并接收网络中其他设备发送的LIE报文和TIE报文。
在本实施例中，一个网络设备可以向网络中其他设备发送LIE报文和TIE报文，也可以接收网络中其他设备发送的LIE报文和TIE报文。毫无疑义的是，在本实施例中，对于一个网络设备而言，其发送LIE报文、TIE报文和接收其他设备所发送的LIE报文、TIE报文这两个过程的时序并不是固定的：在一些情景 中，该网络设备可以先向其他设备发送LIE报文和TIE报文，然后才会接收到其他设备发送的LIE报文和TIE报文；在另外一些情景中，也可以是先进行报文接收，然后才进行报文的发送。发送LIE报文和TIE报文的过程与接收LIE报文和TIE报文的过程也可以是同时进行的。
下面对本实施例中，网络设备之间交换的LIE报文和TIE报文进行介绍：
LIE报文中能够指示发送该报文的源设备所支持的至少一个拓扑的拓扑ID，可以理解的是，所谓源设备是指生成并发送该LIE报文的网络设备，请结合图2示出的示意图：
在图2示出的网络中，网络设备A生成并向网络设备B发送了LIE报文，随后，网络设备B可能会对这个来源于网络设备A的LIE报文进行转发，从而发送给网络设备C，但即便网络设备B发送了该LIE报文，但网络设备B并非是该LIE报文的源设备。该LIE报文的源设备应当是生成并发送该LIE报文的网络设备A。
可以理解的是，网络中存在的拓扑不只一个，即可以基于多拓扑实现对网络的逻辑分层。在本实施例的一些示例中，LIE报文中可以包括源设备所支持的至少一个拓扑的拓扑ID，例如，在一个示例当中，源设备除支持默认拓扑以外，还支持其他拓扑，所以源设备所发送的LIE报文中携带的也可以是源设备所支持的其他至少一个拓扑的拓扑ID。如，一个网络设备支持拓扑标识分别为“0”、“1”的两个拓扑。其中，拓扑ID为“0”的拓扑是网络中各设备默认支持的拓扑，而拓扑ID为“1”的拓扑却只是该网络中部分设备支持的拓扑。在该示例当中，该网络设备发送的LIE报文中可以仅包括拓扑ID“1”，因为即便是在LIE报文中不携带拓扑ID“0”，网络中其他设备也能够了解该网络设备是支持拓扑ID为“0”的拓扑的。
在本实施例的另外一些示例中，LIE报文中可以包括该源设备所支持各个拓扑的拓扑ID，例如，一个网络设备支持的拓扑的拓扑标识包括“0”、“1”、“3”，则在该网络设备作为源设备所发送的LIE报文中可以同时包括拓扑标识，包括“0”、“1”、“3”。
LIE报文中携带有拓扑ID选项，LIE报文通过该拓扑ID选项来指示源设备所支持的拓扑。图3示出了本实施例提供的一种拓扑ID选项的结构示意图：
在拓扑ID选项30当中包括标志(Flags)字段31以及拓扑ID(Topology ID)字段32，其中，Flags字段31可以表征后面的字段中所携带的内容是拓扑ID。在本实施例中，Flags字段31长度为一个字节(BYTE)，可以预留部分位以便后续进行功能扩展。拓扑ID字段32的长度可以被配置为两个BYTE，其中携带 源设备所支持的拓扑的拓扑ID。
根据前述介绍可知，如果一个网络设备所发送的LIE报文中不携带拓扑ID选项，则说明该网络设备仅支持默认拓扑。
TIE报文中包括邻居信息和度量(Metric)信息，在本实施例中，TIE报文中邻居信息和Metric信息均是携带有目标拓扑ID，这里所说的目标拓扑ID即是对应的LIE报文所指示的拓扑ID。因为LIE报文可以向网络中其他设备指示源设备所支持的拓扑的拓扑ID，而TIE报文可以向网络中的其他设备指示源设备在该拓扑ID之下的邻居信息与Metric信息，因此，一个网络设备作为源设备所发送的LIE报文和TIE报文是有相互关联的，在本实施例中，称二者相互对应。
所以，TIE报文中的邻居信息与Metric信息所携带的拓扑ID都是对应的LIE报文中所指示的拓扑ID。在本实施例中，TIE报文包括Node(节点)TIE报文与Prefix(前缀)TIE报文，其中，Node TIE报文中包括携带目标拓扑ID的邻居信息，Node TIE报文和Prefix TIE报文中则包括携带目标拓扑ID的Metric信息。
TIE报文中的邻居信息可以通过邻居选项携带，图4示出了一种携带目标拓扑ID的邻居选项。邻居选项40包括Flags字段41以及拓扑ID字段42，同时邻居选项40中还包括结构体的邻居信息(Neighbor structure)43，在图4示出的邻居选项40中携带有M个邻居的信息。在本实施例中，邻居选项40中的Flags字段41以及拓扑ID字段42与图3中相应的内容类似，这里不再赘述。
TIE报文中的Metric信息可以通过Metric选项携带，图5示出的是一种Metric选项的结构示意图：Metric选项50包括Flags字段51以及拓扑ID字段52，且Metric选项50中的Flags字段51以及拓扑ID字段52与图3、图4中相应的内容类似，这里不再赘述。同时，Metric选项50中还包括Metric字段53，该Metric字段53中携带有Metric信息。
在本实施例的一种示例当中，网络设备为了向网络中其他设备发送上面介绍的LIE报文和TIE报文，网络设备可以建立自己接口同自己所只支持的拓扑之间的映射关系，也即将接口与自己所支持的拓扑进行绑定。例如，一个网络设备支持拓扑ID为“1”和“2”的两个拓扑，该网络设备可以将拓扑ID为“1”的拓扑同自己的接口a绑定，将拓扑ID为“2”的拓扑同接口b绑定。可以理解的是，在本实施例的其他一些示例当中，网络设备进行接口与拓扑绑定的时候，可以将一个接口同两个甚至两个以上的拓扑绑定。
通过绑定接口与拓扑，可以使得从该接口发送出的LIE报文中将携带上该 接口对应的拓扑的拓扑ID，通过该接口发送出去的TIE报文中包括携带对应拓扑ID的邻居信息与Metric信息。
S104：基于本设备所接收到的LIE报文和TIE报文进行网络逻辑分层。
在接收到网络中其他设备发送的LIE报文和TIE报文后，本设备可以基于接收到的这些LIE报文和TIE报文确定出与本设备所支持拓扑相同或部分相同的设备，然后基于获取到的携带目标拓扑ID的邻居信息与携带目标拓扑ID的Metric信息计算确定出该目标拓扑ID对应的拓扑路由。
毫无疑义的是，如果一个网络设备支持多个拓扑，则在进行路由确定的时候，该网络设备需要分别为这多个拓扑确定拓扑路由，确定出分别属于各个拓扑的拓扑路由，例如，假定网络设备支持拓扑ID为“1”和“2”的两个拓扑，则该网络设备在基于从其他设备处接收到的LIE报文和TIE报文进行路由确定的时候，需要分别为拓扑ID为“1”的拓扑计算一个拓扑路由，为拓扑ID为“2”的拓扑计算一个拓扑路由。
网络设备确定出本设备所支持的各拓扑对应的拓扑路由之后，如果有数据需要由该网络设备通过某一个拓扑进行传输，则该网络设备可以基于之前确定出的对应的拓扑路由查询转发路径，实现数据传输。
本实施例提供的基于RIFT协议的网络逻辑分层方法可以由网络中的网络设备执行。可以理解的是，网络中的各网络设备均可以执行该基于RIFT协议的网络逻辑分层方法，从而确定出自身所支持的拓扑对应的拓扑路由。
本发明实施例提供的基于RIFT协议的网络逻辑分层方法，网络中的网络设备通过在LIE报文中增设能够指示自己所支持拓扑的拓扑ID，并在TIE报文的邻居信息与Metric信息中携带自身所支持的拓扑的拓扑ID，从而使得网络中其他设备了解本设备所支持的拓扑，并了解本设备在该拓扑下的邻居信息与Metric信息；同时，本设备也能通过其他设备所发送的LIE报文与TIE报文了解其他设备所支持的拓扑，以及其他设备在对应拓扑下的邻居信息与Metric信息，进而使得网络中各设备基于这些信息确定出自己所支持拓扑的拓扑路由，基于多拓扑实现对网络的逻辑分层，以优化网络通信资源的配置。
实施例二：
RIFT协议仅支持通过不同的UDP(User Datagram Protocol，用户数据报协议)端口号来区分不同实例，即先为某个实例指定特定的UDP端口号，随后基于UDP端口号来区分实例。
不过，UDP端口号作为一种公共资源，让用户指定某实例的UDP端口号容 易导致为实例指令的端口号同知名端口号产生冲突，且知名端口号会随着协议发展不断变化，所以，使用UDP端口号进行实例区分也不利于RIFT协议兼容性。对此，本实施例提供一种解决方案，以便通过RIFT协议实现实例的区分，请参见图6示出的基于RIFT协议的网络逻辑分层方法的流程图：
S602：向网络中的其他设备发送LIE报文和TIE报文，并接收网络中其他设备发送的LIE报文和TIE报文。
在本实施例中，一个网络中，各网络设备所支持的实例可以相同，在这种情况下，就只能按照实施例一的介绍，基于多拓扑对网络进行逻辑分层。不过在本实施例的其他一些实例当中，一个网络中，各网络设备所支持的实例可以不完全相同，例如其中一部分设备支持实例1，而另外一部分设备则支持实例2，在这种情况下，基于多实例也可以实现网络的逻辑分层。
为了让网络中各网络设备能够基于多实例实现对网络的逻辑分层，可以对各网络设备发送的LIE报文和TIE报文进行新的配置：
在本实施例中，在网络设备发送的LIE报文和TIE报文均携带有实例ID选项，所以，各网络设备从其他设备处接收到的LIE报文与TIE报文中也应当携带有实例ID选项。图7示出实例ID选项的一种结构示意图：
实例ID选项70中包括实例ID(Instance ID)字段71与逻辑拓扑字段72，其中实例ID字段71中包括源设备所支持的至少一个实例的实例ID，而逻辑拓扑字段72中可以包含源设备在该实例下的至少一个拓扑ID选项，所以在逻辑拓扑字段72中可以包括至少一个如图3示出的拓扑ID选项。例如，在图7示出的实例ID选项70当中，就包括N个拓扑ID选项。不过，在本实施例的一些示例当中，逻辑拓扑字段72中也可以不携带任何一个拓扑ID选项，在这种情况下表征源设备仅支持默认拓扑。
在本实施例中，为了向网络中其他设备发送携带实例ID选项的LIE报文和TIE报文，网络设备可以先配置自己接口同实例之间的映射关系，将接口与实例绑定，随后再通过绑定了对应实例的接口外发LIE报文和TIE报文，这样，发送的LIE报文和TIE报文中就都会携带对应的实例ID选项。
S604：基于本设备所接收到的LIE报文和TIE报文对网络进行逻辑分层。
在接收到网络中其他设备发送的LIE报文和TIE报文后，网络设备可以基于这些LIE报文和TIE报文确定出网络中与本设备所支持实例相同的设备，以及这些网络设备在其所支持的实例下所支持的拓扑。随后，网络设备便可以基于获取到的这些信息确定出自己所支持的实例下自己所支持的各拓扑的拓扑路由。
可以理解的是，一个网络中存在至少两个实例时，就可以基于实例对网络进行逻辑分层。实例与实例之间是不通报文的，不过，有时候，一个网络设备可以同时支持不只一个实例，例如，某一网络设备同时支持实例1与实例2，在这种情况下，尽管，实例1和实例2的报文都能够被该网络设备接收到，但该网络设备在确定实例1下的拓扑路由时，不会需要来自实例2的LIE报文和TIE报文；同样地，在确定实例2下的拓扑路由时，也不必关心实例1中网络设备所发送的LIE报文和TIE报文。因此，对于支持某一实例而言，网络设备所接收到的LIE报文和TIE报文也并不都有用，所以，下面结合图8介绍一种确定拓扑路由的方案：
S802：对接收到的LIE报文和TIE报文进行筛选，保留目标LIE报文和目标TIE报文。
在本实施例中，目标LIE报文是指所携带实例ID与接收到该报文的接口所绑定实例ID相同的LIE报文，而目标TIE报文则是指所携带的实例ID与接收到该报文的接口所绑定实例ID相同且由本设备在实例ID下的邻居设备发送的TIE报文。
例如，某一网络设备仅支持实例1，并且该网络设备将实例1同自己的接口a绑定，随后，网络设备从接口a中接收两份报文，其中一份报文中的LIE报文与TIE报文所携带实例ID选项中的实例ID均为实例1，但是另一份报文的LIE报文与TIE报文所携带实例ID选项中的实例ID为“2”，在这种情况下，该网络设备仅会将第一份报文中的LIE报文作为实例1对应的目标LIE报文，将第一份报文中的TIE报文作为实例1对应的目标TIE报文。并且，在确定第二份报文中所携带的实例ID与接收到该份报文的接口a所绑定的实例ID不一致的时候，网络设备可以直接丢弃这份报文，也即丢弃第二份报文中的LIE报文与TIE报文。
另外，在本示例中，网络设备在筛选目标TIE报文时，不仅要求目标TIE报文所携带的实例ID与网络设备接收到该报文的接口所绑定的实例的实例ID一致，同时，还要求该报文是由该网络设备的邻居发送的。也即在一些情况下，即便一个TIE报文中所携带的实例ID符合要求，但很可能因为该TIE报文的源设备不是网络设备的邻居，因此，也会被网络设备所丢弃。
S804：基于目标LIE报文和目标TIE报文对网络进行逻辑分层。
筛选出目标LIE报文和目标TIE报文之后，网络设备可以基于这些目标LIE报文与目标TIE报文来确定本设备所支持实例下的各拓扑的拓扑路由。例如某一网络设备仅支持实例1，在实例1下，该网络设备支持拓扑1和拓扑2，因此，该网络设备最终需要确定的拓扑路由包括实例1下拓扑1的拓扑路由，以及实 例1下拓扑2的拓扑路由。
本实施例提供的基于RIFT协议的网络逻辑分层方法，网络中各网络设备通过在各自发送的LIE报文和TIE报文中，携带实例ID选项，通过实例ID选项向网络中其他设备指示本设备所支持的实例，以及本设备在该实例下所支持的拓扑。各网络设备通过交换LIE报文和TIE报文，从而了解其他设备所支持的实例以及拓扑，进而在多实例的基础上实现对网络进行逻辑划分。
实施例三：
实施例一中提供了一种基于多拓扑实现网络逻辑分层的方案，而实施例二中则提供了一种基于多实例实现网络逻辑分层的方案，可以理解的是，在对网络进行逻辑分层的时候，可以结合实施例一与实施例二的方案进行，及同时基于多实例与多拓扑实现网络的分层：
在本实施例中，网络中的各网络设备同样会交换LIE报文与TIE报文，为了同时基于多实例与多拓扑的网络逻辑划分，网络设备向外发送的LIE报文中不仅能够指示源设备所支持的至少一个拓扑的拓扑ID，同时还包括实例ID选项。LIE报文中包括拓扑ID选项，因此，通过该LIE报文告知其他设备自己接口所支持的拓扑信息。
而TIE报文中，则不仅包括携带目标拓扑ID的邻居信息以及携带目标拓扑ID的Metric信息，同时还包括实例ID选项。Node TIE报文中支持携带拓扑ID的邻居选项，通告远端自己在某拓扑的邻居信息；Node TIE报文和Prefix TIE报文中包括携带拓扑ID的Metric信息，从而通告网络中其他设备自己在对应拓扑中的Metric信息。
在一种示例当中，为了向其他设备发送出符合上述介绍的LIE报文与TIE报文，网络设备可以先将自己支持的某一实例以及该实例下的某一拓扑同自己的一个接口绑定，这样，通过该接口发送出的LIE报文就自然可以携带对应的拓扑ID选项以及实例ID选项，而通过该接口发送的TIE报文就自然包括携带目标拓扑ID的邻居信息与Metric信息，以及对应的实例ID。
在接收到网络中其他设备发送的LIE报文与TIE报文后，网络设备也可以先按照实施例二中的介绍，先对接收到的报文进行筛选，确定出对应的目标LIE报文与目标TIE报文，然后才基于筛选保留下的目标LIE报文与目标TIE报文中的信息确定本设备所支持实例下各拓扑的拓扑路由。
本实施例中所提供的基于RIFT协议的网络逻辑分层方法，通过在LIE报文携带实例ID选项，从而让报文接收者判断报文中的实例ID和自己所支持的实 例的实例ID是否一致，不一致则丢弃，不建立邻居关系；同时，通过在TIE报文携带实例ID选项，从而让报文接收者判断报文是否是自己所支持实例的邻居发送的，不是则丢弃。利用实例之间的不同报文，在网络中存在两个甚至更多实例的时候，让各实例单独确定拓扑路由。
更进一步地，通过在LIE报文中增设能够指示源设备所支持拓扑的拓扑ID，并在TIE报文的邻居信息与Metric信息中携带自身所支持的拓扑的拓扑ID，从而使得网络中其他设备了解本设备所支持的拓扑，并了解本设备在该拓扑下的邻居信息与Metric信息，进而基于多拓扑实现对网络的逻辑分层，以优化网络通信资源的配置。
实施例四：
本实施例提供一种网络逻辑分层装置，请参见图9示出的网络逻辑分层装置90的一种结构示意图：
网络逻辑分层装置90包括第一报文收发模块902以及第一分层处理模块904，其中，第一报文收发模块902用于向网络中的其他设备发送LIE报文和TIE报文，并接收网络中其他设备发送的LIE报文和TIE报文；LIE报文能够指示发送该报文的源设备所支持的至少一个拓扑的拓扑ID，TIE报文中包含携带目标拓扑ID的邻居信息与携带目标拓扑ID的Metric信息，目标拓扑ID为与该TIE报文对应的LIE报文所指示的拓扑ID。第一分层处理模块904用于基于本设备所接收到的LIE报文和TIE报文进行网络逻辑分层。
该网络逻辑分层装置90可以被部署在网络设备上，其中第一报文收发模块902的功能可以通过网络设备的通信单元和处理器共同实现，而第一分层处理模块904的功能则可以通过网络设备的处理器实现。该网络逻辑分层装置90可以实现实施例一以及实施例三中介绍的基于RIFT协议的网络逻辑分层方法，基于RIFT协议的网络逻辑分层方法的具体实现过程请参见前述实施例的介绍，这里不再赘述。
本实施例还提供另外一种网络逻辑分层装置，请参见图10示出的结构示意图：
网络逻辑分层装置10包括第二报文收发模块102以及第二分层处理模块104，其中，第二报文收发模块102用于向网络中的其他设备发送LIE报文和TIE报文，并接收网络中其他设备发送的LIE报文和TIE报文；LIE报文和TIE报文中均包括实例ID选项，实例ID选项中携带有发送该报文的源设备所支持的至少一个实例的实例ID与该实例下的至少一个拓扑的拓扑ID。第二分层处理模 块104用于基于本设备所接收到的LIE报文和TIE报文对网络进行逻辑分层。
网络逻辑分层装置10同样也可以被部署在网络设备上，其中第二报文收发模块102的功能可以通过网络设备的通信单元和处理器共同实现，而第二分层处理模块104的功能则可以通过网络设备的处理器实现。该网络逻辑分层装置10可以实现实施例二以及实施例三中介绍的基于RIFT协议的网络逻辑分层方法，基于RIFT协议的网络逻辑分层方法的具体实现过程请参见前述实施例的介绍，这里不再赘述。
本实施例中提供的网络逻辑分层装置，通过对LIE报文以及TIE报文进行扩展，从而可以基于多拓扑和/或多实例实现对网络的逻辑分层，有利于通过自拓扑提升网络中通信资源的利用率，优化资源的优化配置。
实施例五：
本实施例提供一种计算机可读存储介质，该计算机可读存储介质中可以存储有一个或多个可供一个或多个处理器读取、编译并执行的计算机程序，在本实施例中，该计算机可读存储介质可以存储有第一网络逻辑分层程序和第二网络逻辑分层程序中的一个，其中，第一网络逻辑分层程序可供一个或多个处理器执行实现前述实施例一以及实施例三中介绍的任意一种基于RIFT协议的网络逻辑分层方法的流程。第二网络逻辑分层程序可供一个或多个处理器执行实现前述实施例二和实施例三中介绍的任意一种基于RIFT协议的网络逻辑分层方法的流程。
本实施例中还提供一种网络设备，如图11所示：网络设备110包括处理器111、存储器112以及用于连接处理器111与存储器112的通信总线113，其中存储器112可以为前述存储有第一网络逻辑分层程序和/或第二网络逻辑分层程序的计算机可读存储介质。处理器111可以读取第一网络逻辑分层程序，进行编译并执行实现前述实施例一以及实施例三中介绍的基于RIFT协议的网络逻辑分层方法的流程：
处理器111向网络中的其他设备发送LIE报文和TIE报文，并接收网络中其他设备发送的LIE报文和TIE报文。然后，基于本设备所接收到的LIE报文和TIE报文确定本设备所支持的拓扑对应的拓扑路由，基于拓扑实现对网络的逻辑分层。
其中，LIE报文能够指示发送该报文的源设备所支持的至少一个拓扑的拓扑ID，TIE报文中包含携带目标拓扑ID的邻居信息与携带目标拓扑ID的度量Metric信息，目标拓扑ID为与该TIE报文对应的LIE报文所指示的拓扑ID。
处理器111可以将本网络设备110所支持的拓扑同本设备的接口绑定，通过 接口向网络中的其他设备发送LIE报文和TIE报文。
可选地，处理器111发送的TIE报文包括Node TIE报文与Prefix TIE报文；其中，Node TIE报文中包括携带目标拓扑ID的邻居信息，且Node TIE报文和Prefix TIE报文中包括携带目标拓扑ID的Metric信息。
处理器111也可以读取第二网络逻辑分层程序，进行编译并执行实现前述实施例二以及实施例三中介绍的基于RIFT协议的网络逻辑分层方法的流程：
处理器111向网络中的其他设备发送LIE报文和TIE报文，并接收网络中其他设备发送的LIE报文和TIE报文。该LIE报文和TIE报文中均包括实例ID选项，实例ID选项中携带有源设备所支持的至少一个实例的实例ID，接收到其他设备发送的LIE报文和TIE报文后，处理器111基于本设备所接收到的LIE报文和TIE报文进行网络逻辑分层。
可选地，处理器111可以将本设备所支持的实例同本设备的接口绑定，并通过接口向网络中的其他设备发送LIE报文和TIE报文。
另外，在处理器111基于本设备所接收到的LIE报文和TIE报文确定本设备所支持实例下各拓扑对应的拓扑路由时，其可以对接收到的LIE报文和TIE报文进行筛选，保留目标LIE报文和目标TIE报文，目标LIE报文为所携带实例ID与接收到该报文的接口所绑定实例ID相同的LIE报文，目标TIE报文为所携带的实例ID与接收到该报文的接口所绑定实例ID相同且由本设备在实例ID下的邻居设备发送的TIE报文。筛选之后，再基于目标LIE报文和目标TIE报文进行网络逻辑分层。
该网络设备110的处理器111执行第一网络逻辑分层程序和第二网络逻辑分层程序中至少一个以实现基于RIFT协议的网络逻辑分层方法，其他细节请参见前述实施例的介绍，这里不再赘述。
实施例六：
为了使本领域技术人员更清楚前述实施例中所提供路由确定方案的优点与细节，本实施例将结合具体示例以及图12示出的RIFT组网架构继续对前述实施例中的路由确定方案进行介绍：
示例1——基于多拓扑实现网络的逻辑分层。
●RIFT协议报文扩展的说明：
针对LIE报文：
在LIE报文中新增拓扑ID选项，拓扑ID选项的结构如图3所示。在本实 施例中，如果某一网络设备所发送的LIE报文中不携带该拓扑ID选项，则说明该网络设备仅支持默认拓扑。
针对TIE报文：
可以新增携带拓扑ID的邻居信息，例如通过图4示出的邻居选项携带。在图4当中，“Neighbor structure”为RIFT协议规定的邻居结构，用于表征邻居。可以理解的是，一个TIE报文中可以携带多个邻居选项。
同时，可以在TIE报文中新增携带拓扑ID的Metric信息，例如通过图5示出的Metric选项携带。同样地，一个TIE报文中可以携带多个Metric选项。
●报文发送的说明：
网络设备可以通过配置命令或其他方法，把本设备的某个接口绑定到特定的拓扑中。
例如，在图12所示的网络中，假设Node111、Node122、Spine22不支持组播功能(例如IPv4组播功能)，且组播拓扑的拓扑ID为“1”。同时图12中所有节点都默认支持拓扑0。
对于Leaf011节点，其会将自身除了同Node111连接的接口以外的其他接口都绑定到拓扑1中；对于Leaf012节点，其会将自身除了同Node111连接的接口以外的其他接口都绑定到拓扑1中；对于Leaf021节点，其会将自身除了同Node122连接的接口以外的其他接口都绑定到拓扑1中；对于Leaf022节点，其会将自身除了同Node122连接的接口以外的其他接口都绑定到拓扑1中。
对于Node112节点，其会将自身除了同Spine22连接的接口以外的其他接口都绑定到拓扑1中；对于Node121节点，其会将自身除了同Spine22连接的接口以外的其他接口都绑定到拓扑1中。
对于Spine21节点，其会将自身除了同Node111、Node122连接的接口以外的其他接口都绑定到拓扑1中。
在网络中各节点进行了接口与拓扑1的绑定之后，这些接口发送的LIE报文都会携带拓扑ID选项，且拓扑ID选项中的拓扑ID为“1”。这些接口发送的Node TIE报文里包含携带拓扑ID“1”的邻居选项，Node TIE报文以及Prefix TIE报文里包含携带拓扑ID“1”的Metric选项。
●路由确定说明：
在本示例中，各节点均支持拓扑0这一默认拓扑，同时，部分节点支持拓扑1，所以，支持拓扑1的节点会为拓扑1单独计算拓扑路由，该拓扑1的路由用于组播选路转发，没有绑定拓扑1的接口则不参与拓扑路由计算。
示例2——基于多实例实现网络的逻辑分层。
●RIFT协议报文扩展的说明：
针对LIE报文：
在LIE报文中新增实例ID选项，实例ID选项的结构如图7所示。在本实施例中，如果某一网络设备所发送的LIE报文中不携带该实例ID选项，则默认该网络设备仅支持默认实例(实例0)。
针对TIE报文：
在TIE报文中也同样新增图7所示的实例ID选项。
●报文发送的说明：
网络设备可以通过配置命令或其他方法，把本设备的某个接口绑定到特定的实例中。
例如，在图12所示的网络中，假如Leaf011、Node111、Spine21、Node121、Leaf021这5个节点支持实例1拓扑1，因此，这几个节点可将自身同其与四个节点中任意一个相连的接口绑定到实例1拓扑1中。随后，这些接口发送的LIE报文与TIE报文将均会携带实例ID选项，该实例ID选项中所携带的实例ID为“1”，拓扑ID为“1”。
●报文接收的说明：
网络设备接收到LIE报文后，如果确定该LIE报文携带的实例ID和接收该LIE报文的接口绑定的实例ID不一致，则将该报文丢掉。
对于接收到的TIE报文，网络设备确定该报文所携带的实例ID和接收该TIE报文的接口绑定的实例ID是否一致，并在确定一致时确定其是否是由本设备在该实例下的邻居发送的，如果判断结果为否，则将该报文丢弃。若确定该TIE报文携带的实例ID和接收该TIE报文的接口绑定的实例ID一致，且确定其是由本设备的邻居发送的，则按照TIE泛洪规则向同一实例的邻居发送该TIE报文。
●路由确定说明：
网络设备接收到其他设备发送的LIE报文和TIE报文后，可以为自己所支持的各实例、各拓扑计算拓扑路由。
示例3——基于多拓扑多实例实现网络的逻辑分层。
●RIFT协议报文扩展的说明：
本示例中对于协议的扩展，结合了示例1与示例2的做法，所以，这里可以参见前述示例的介绍，这里不再赘述。
●报文发送的说明：
网络设备可以通过配置命令或其他方法，把本设备的某个接口绑定到特定的实例特定的拓扑中。
例如，在图12所示的网络中，假定Leaf011将自身的所有接口均绑定到实例1下的拓扑1以及拓扑2，这里将Leaf011的接口绑定关系记为“1.1+1.2”；
Leaf012将自身的所有接口绑定实例2下的拓扑1以及拓扑2，这里将Leaf012的接口绑定关系记为“2.1+2.2”；
Node111将自身的所有接口绑定实例1下的拓扑1以及拓扑2，这里将Node111的接口绑定关系记为“1.1+1.2”；
Node112将自身所有接口均绑定实例2拓扑2，这里将Node111的接口绑定关系记为“2.2”。
随后，各节点采用对应的接口进行LIE报文以及TIE报文的发送，从而使得发送的LIE报文中携带对应的拓扑ID选项以及实例ID选项，使得发送的TIE报文中包含携带对应拓扑ID的邻居选项与Metric选项，同时携带对应的实例ID选项。
●报文接收的说明：
各网络设备从其他网络设备处接收到LIE报文与TIE报文后，会按照示例2中的介绍进行筛选与转发，具体过程请参见前述示例的介绍，这里不再赘述。
●路由确定说明：
在本示例中，由于Leaf011和Node111之间实例和拓扑完全相同，可以正常建立邻居关系，正常交换TIE报文，计算出实例1的拓扑1和拓扑2两个拓扑的路由。
由于Leaf011和Node112之间实例不同，因此无法建立邻居关系。
同样地，因为Leaf012和Node111之间实例不同，所以，也无法建立邻居关系。
由于Leaf012和Node112之间实例相同，可以正常建立邻居关系，并交换TIE报文。同时，因为这两个节点都支持拓扑2，所以，可以正常计算拓扑2的路由，但是因为Node112不支持拓扑1，所以无法计算拓扑1的路由。
本申请中，各个实施例中的技术特征，在不冲突的情况下，可以组合在一个实施例中使用。
显然，本领域的技术人员应该明白，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件(可以用计算装置可执行的程序代码来实现)、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于随机存取存储器(Random Access Memory，RAM),只读存储器(Read-Only Memory，ROM),电可擦只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、闪存或其他存储器技术、便携式紧凑磁盘只读存储器(Compact Disc Read Only Memory，CD-ROM)，数字多功能盘(Digital Video Disk，DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。所以，本公开不限制于任何特定的硬件和软件结合。

Claims (17)

  1. 一种基于胖树路由RIFT协议的网络逻辑分层方法，包括：
    向网络中的其他设备发送链路信息元素LIE报文和拓扑信息元素TIE报文，并接收所述网络中的所述其他设备发送的LIE报文和TIE报文；其中，所述LIE报文指示发送所述LIE报文的源设备所支持的至少一个拓扑的拓扑标识ID，所述TIE报文中包含携带目标拓扑ID的邻居信息与携带所述目标拓扑ID的度量Metric信息，所述目标拓扑ID为与所述TIE报文对应的LIE报文所指示的拓扑ID；
    基于本设备所接收到的LIE报文和TIE报文进行网络逻辑分层；
    其中，所述其他设备为除所述本设备之外的设备。
  2. 如权利要求1所述的方法，其中，所述向网络中的其他设备发送LIE报文和TIE报文，包括：
    将所述本设备所支持的拓扑同所述本设备的接口绑定；
    通过所述接口向所述网络中的所述其他设备发送携带所述本设备所支持的至少一个拓扑的拓扑ID的LIE报文，并通过所述接口向所述网络中的所述其他设备发送TIE报文，所述TIE报文中包含携带目标拓扑ID的邻居信息与携带所述目标拓扑ID的Metric信息。
  3. 如权利要求1所述的方法，其中，在所述源设备除支持默认拓扑以外，还支持其他拓扑的情况下，所述LIE报文中携带所述源设备所支持的其他至少一个拓扑的拓扑ID。
  4. 如权利要求1所述的方法，其中，所述TIE报文包括节点Node TIE报文与前缀Prefix TIE报文；所述Node TIE报文中包括携带所述目标拓扑ID的邻居信息，且所述Node TIE报文和所述Prefix TIE报文中包括携带所述目标拓扑ID的Metric信息。
  5. 如权利要求1-4任一项所述的方法，其中，所述LIE报文和所述TIE报文中均还包括实例ID选项，所述实例ID选项中携带有所述源设备所支持的至少一个实例的实例ID与所述实例下的至少一个拓扑的拓扑ID。
  6. 如权利要求5所述的方法，其中，所述向网络中的其他设备发送LIE报文和TIE报文，包括：
    将所述本设备所支持的实例同所述本设备的接口绑定；
    通过所述接口向所述网络中的所述其他设备发送LIE报文和TIE报文。
  7. 如权利要求5所述的方法，其中，所述基于本设备所接收到的LIE报文和TIE报文进行网络逻辑分层，包括：
    对接收到的LIE报文和TIE报文进行筛选，保留目标LIE报文和目标TIE报文，所述目标LIE报文为所携带的实例ID与接收到所述LIE报文的接口所绑定的实例ID相同的LIE报文，所述目标TIE报文为所携带的实例ID与接收到所述TIE报文的接口所绑定的实例ID相同且由所述本设备在所述实例ID下的邻居设备发送的TIE报文；
    基于所述目标LIE报文和所述目标TIE报文进行网络逻辑分层。
  8. 一种基于胖树路由RIFT协议的网络逻辑分层方法，包括：
    向网络中的其他设备发送链路信息元素LIE报文和拓扑信息元素TIE报文，并接收所述网络中的所述其他设备发送的LIE报文和TIE报文；其中，所述LIE报文和所述TIE报文中均包括实例标识ID选项，所述实例ID选项中携带有发送所述LIE报文和所述TIE报文的源设备所支持的至少一个实例的实例ID；
    基于本设备所接收到的LIE报文和TIE报文对网络进行逻辑分层；
    其中，所述其他设备为除所述本设备之外的设备。
  9. 如权利要求8所述的方法，其中，所述向网络中的其他设备发送LIE报文和TIE报文，包括：
    将所述本设备所支持的实例同所述本设备的接口绑定；
    通过所述接口向所述网络中的所述其他设备发送携带所述本设备所支持的至少一个拓扑的拓扑ID的LIE报文，并通过所述接口向所述网络中的所述其他设备发送TIE报文，所述TIE报文中包含携带目标拓扑ID的邻居信息与携带所述目标拓扑ID的度量Metric信息。
  10. 如权利要求8所述的方法，其中，所述基于本设备所接收到的LIE报文和TIE报文对网络进行逻辑分层，包括：
    对接收到的LIE报文和TIE报文进行筛选，保留目标LIE报文和目标TIE报文，所述目标LIE报文为所携带的实例ID与接收到所述LIE报文的接口所绑定的实例ID相同的LIE报文，所述目标TIE报文为所携带的实例ID与接收到所述TIE报文的接口所绑定实例的ID相同且由所述本设备在所述实例ID下的邻居设备发送的TIE报文；
    基于所述目标LIE报文和所述目标TIE报文对网络进行逻辑分层。
  11. 如权利要求8-10任一项所述的方法，其中，所述网络中存在至少两个拓扑；所述LIE报文中还包括发送所述LIE报文的源设备所支持的至少一个拓扑的拓扑ID，所述TIE报文中包含携带目标拓扑ID的邻居信息与携带所述目标拓扑ID的Metric信息，所述目标拓扑ID为与所述TIE报文对应的LIE报文中 所指定的拓扑ID。
  12. 如权利要求11所述的方法，其中，所述向网络中的其他设备发送LIE报文和TIE报文，包括：
    将所述本设备所支持的拓扑同所述本设备的接口绑定；
    通过所述接口向所述网络中的所述其他设备发送携带本设备的实例ID选项的LIE报文和携带本设备的实例ID选项的TIE报文。
  13. 如权利要求11所述的方法，其中，所述TIE报文包括节点Node TIE报文与前缀Prefix TIE报文；所述Node TIE报文中包括携带所述目标拓扑ID的邻居信息，且所述Node TIE报文和所述Prefix TIE报文中包括携带所述目标拓扑ID的Metric信息。
  14. 一种网络逻辑分层装置，包括：
    第一报文收发模块，设置为向网络中的其他设备发送链路信息元素LIE报文和拓扑信息元素TIE报文，并接收所述网络中的所述其他设备发送的LIE报文和TIE报文；其中，所述LIE报文指示发送所述LIE报文的源设备所支持的至少一个拓扑的拓扑标识ID，所述TIE报文中包含携带目标拓扑ID的邻居信息与携带所述目标拓扑ID的度量Metric信息，所述目标拓扑ID为与所述TIE报文对应的LIE报文所指示的拓扑ID；
    第一分层处理模块，设置为基于本设备所接收到的LIE报文和TIE报文进行网络逻辑分层；
    其中，所述其他设备为除所述本设备之外的设备。
  15. 一种网络逻辑分层装置，包括：
    第二报文收发模块，设置为向网络中的其他设备发送链路信息元素LIE报文和拓扑信息元素TIE报文，并接收所述网络中的所述其他设备发送的LIE报文和TIE报文；其中，所述LIE报文和所述TIE报文中均包括实例标识ID选项，所述实例ID选项中携带有发送所述LIE报文和所述TIE报文的源设备所支持的至少一个实例的实例ID；
    第二分层处理模块，设置为基于本设备所接收到的LIE报文和TIE报文对网络进行逻辑分层；
    其中，所述其他设备为除所述本设备之外的设备。
  16. 一种网络设备，所述网络设备包括处理器、存储器及通信总线；
    所述通信总线设置为实现处理器和存储器之间的连接通信；
    所述处理器设置为执行所述存储器中存储的第一网络逻辑分层程序，以实现如权利要求1至7中任一项所述的基于胖树路由RIFT协议的网络逻辑分层方法；和/或所述处理器用于执行存储器中存储的第一网络逻辑分层程序，以实现如权利要求8至13中任一项所述的基于RIFT协议的网络逻辑分层方法。
  17. 一种计算机可读存储介质，所述计算机可读存储介质存储有第一网络逻辑分层程序和第二网络逻辑分层程序中的至少一个，所述第一网络逻辑分层程序可被一个或者多个处理器执行，以实现如权利要求1至7中任一项所述的基于胖树路由RIFT协议的网络逻辑分层方法；所述第二网络逻辑分层程序可被一个或者多个处理器执行，以实现如权利要求8至13中任一项所述的基于RIFT协议的网络逻辑分层方法。
PCT/CN2020/075952 2019-03-01 2020-02-20 基于rift协议的网络逻辑分层方法、装置、网络设备及存储介质 WO2020177540A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20766989.6A EP3920486A4 (en) 2019-03-01 2020-02-20 METHOD FOR LAYERING NETWORK LOGIC BASED ON RIFT PROTOCOL, DEVICE, NETWORK DEVICE, AND MEDIA
US17/434,752 US20220166710A1 (en) 2019-03-01 2020-02-20 Rift protocol-based network logical layering method and device, network device and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910157607.3 2019-03-01
CN201910157607.3A CN111641560A (zh) 2019-03-01 2019-03-01 网络逻辑分层方法、装置、网络设备及存储介质

Publications (1)

Publication Number Publication Date
WO2020177540A1 true WO2020177540A1 (zh) 2020-09-10

Family

ID=72330914

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/075952 WO2020177540A1 (zh) 2019-03-01 2020-02-20 基于rift协议的网络逻辑分层方法、装置、网络设备及存储介质

Country Status (4)

Country Link
US (1) US20220166710A1 (zh)
EP (1) EP3920486A4 (zh)
CN (1) CN111641560A (zh)
WO (1) WO2020177540A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102164081A (zh) * 2011-03-31 2011-08-24 华为技术有限公司 一种胖树拓扑的路由计算方法、节点设备和通信系统
CN103078798A (zh) * 2012-12-28 2013-05-01 华为技术有限公司 一种建立路由表的方法和设备
CN105591932A (zh) * 2015-07-13 2016-05-18 杭州华三通信技术有限公司 邻居的识别方法及装置
WO2018145761A1 (en) * 2017-02-10 2018-08-16 Huawei Technologies Co., Ltd. Structured id-based and topology adaptive control plane for 5g

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8223669B2 (en) * 2008-04-07 2012-07-17 Futurewei Technologies, Inc. Multi-protocol label switching multi-topology support
CN103825827B (zh) * 2014-03-04 2017-06-23 新华三技术有限公司 一种路由通告方法及设备
CN107689915A (zh) * 2016-08-04 2018-02-13 中兴通讯股份有限公司 报文转发方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102164081A (zh) * 2011-03-31 2011-08-24 华为技术有限公司 一种胖树拓扑的路由计算方法、节点设备和通信系统
CN103078798A (zh) * 2012-12-28 2013-05-01 华为技术有限公司 一种建立路由表的方法和设备
CN105591932A (zh) * 2015-07-13 2016-05-18 杭州华三通信技术有限公司 邻居的识别方法及装置
WO2018145761A1 (en) * 2017-02-10 2018-08-16 Huawei Technologies Co., Ltd. Structured id-based and topology adaptive control plane for 5g

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
CN111641560A (zh) 2020-09-08
EP3920486A1 (en) 2021-12-08
EP3920486A4 (en) 2022-11-09
US20220166710A1 (en) 2022-05-26

Similar Documents

Publication Publication Date Title
EP2962431B1 (en) Spanning tree in fabric switches
JP7292427B2 (ja) Ｔｓｎ内のコントローラ間の通信のための方法、装置、およびシステム
US9665530B2 (en) Method and system for implementing elastic network interface and interconnection
CA3148150A1 (en) Connection establishment method,device,integrated access backhaul node and storage medium
CN102318287B (zh) 路由器邻居建立方法和设备
US10404571B2 (en) Communication among network controllers
CN113037527B (zh) 网络切片创建方法、报文转发方法及其装置
CN111711941B (zh) 数据传输方法以及相关设备、装置
WO2021227561A1 (zh) 通信方法和装置
WO2020078043A1 (zh) 一种确定组播流的df的方法、设备及系统
CN104301226A (zh) 一种指定路由桥选举方法、设备和系统
WO2015196923A1 (zh) 一种发送信息的方法和网络装置
WO2013013642A1 (zh) 处理跨环业务的方法和相交节点
CN104038427A (zh) 路由更新方法和路由更新装置
CN110177021B (zh) 基于软件定义的无线自组网节点及数据传输方法
CN109039916B (zh) 报文转发方法、装置及存储介质
US11343153B2 (en) BGP logical topology generation method, and device
JP2024504466A (ja) パケット転送方法、パケット処理方法、およびデバイス
WO2020177540A1 (zh) 基于rift协议的网络逻辑分层方法、装置、网络设备及存储介质
WO2015032260A1 (zh) 路由更新方法和路由设备
CN102857415A (zh) 介质访问控制地址学习控制方法、装置和路由桥
US8352637B2 (en) Techniques for resolving network connectivity
CN110830295B (zh) 一种设备管理方法及系统
CN113260072A (zh) Mesh组网流量调度方法、网关设备和存储介质
WO2019128651A1 (zh) 一种anima网络的信息处理方法、设备及系统

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: 20766989

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: 2020766989

Country of ref document: EP

Effective date: 20210901