WO2024032187A1 - 一种路由信息传输方法及装置 - Google Patents

一种路由信息传输方法及装置 Download PDF

Info

Publication number
WO2024032187A1
WO2024032187A1 PCT/CN2023/103082 CN2023103082W WO2024032187A1 WO 2024032187 A1 WO2024032187 A1 WO 2024032187A1 CN 2023103082 W CN2023103082 W CN 2023103082W WO 2024032187 A1 WO2024032187 A1 WO 2024032187A1
Authority
WO
WIPO (PCT)
Prior art keywords
routing
locator
srv6
identifier
message
Prior art date
Application number
PCT/CN2023/103082
Other languages
English (en)
French (fr)
Inventor
赵孟凯
徐国其
蒋宇
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024032187A1 publication Critical patent/WO2024032187A1/zh

Links

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
    • 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/12—Shortest path evaluation
    • 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/18—Loop-free operations
    • 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/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]

Definitions

  • the present application relates to the field of communication technology, and in particular to a routing information transmission method and device.
  • OSPF Interior Gateway Protocols
  • IPv6 Internet protocol version 6
  • IPv6 SRv6 forwarding plane segment routing
  • out-of-area nodes can also be introduced so that in-area nodes can calculate routes to out-of-area nodes.
  • the autonomous system boundary router (ASBR) generates a link-state advertisement (LSA) and floods it into the domain, so that the nodes in the domain Calculate the route to the node outside the domain based on the LSA.
  • LSA link-state advertisement
  • This application provides a routing information transmission method and device to enable network equipment to calculate routes to nodes outside the domain by carrying routing metric types in routing messages.
  • a routing information transmission method includes: a first network device receives a first message from a first network domain, the first message includes SRv6 Locator, and according to the first The message generates a second message.
  • the second message includes the SRv6 Locator and the routing metric identifier.
  • the routing metric identifier is used to indicate the method of calculating the routing cost of the route corresponding to the SRv6 Locator.
  • the first network device sends the second message to the second network device in the second network domain, so that when receiving the second message, the second network device calculates the routing cost of the route corresponding to the SRv6 Locator.
  • the second message also includes the first route metric value in the first network domain of the route corresponding to the first network device arriving at the SRv6 Locator. That is, in this application, when the first network device introduces the SRv6 Locator route of the first network domain to the second network domain, it will add the routing metric identifier to the generated second message, so that the network device in the second network domain will When calculating the routing cost of the route corresponding to the SRv6 Locator, the calculation method can be determined based on the route metric identifier, and then the routing cost can be obtained based on the determined calculation method.
  • the second message may be an OSPFv3 LSA message.
  • the first network device can also calculate the first routing metric value so as to add the first routing metric value to the second message, thereby facilitating the The second network device uses the first route metric value to calculate the route cost to the SRv6 Locator.
  • the route metric identifier may be carried in the second message in the following manner: the second message includes an SRv6 Locator type length value (TLV), and the SRv6 Locator TLV includes the route metric identifier.
  • the route metric identifier can be carried through the flag bit Flag in the SRv6 Locator TLV.
  • Flags include extension bits, through which the route metric identifier is carried.
  • the SRv6 Locator TLV includes a first sub-TLV, and the first sub-TLV carries the route metric identifier, that is, the route metric identifier is carried by extending the sub-TLV of the SRv6 Locator TLV.
  • the second message may also include a routing identifier, which indicates the source of the SRv6 Locator to prevent loops. That is, the routing identifier is used to prevent packets carrying SRv6 Locator from being sent to the first network domain.
  • the routing identifier in the second message may be determined by the first network device according to the first network domain and the configuration policy after receiving the first message, and the routing identifier corresponding to the first network domain.
  • the configuration policy is used to indicate the routing identifiers corresponding to different network domains.
  • the first network domain can be an intermediate system to intermediate system (ISIS) domain
  • the second network domain can be an OSPF domain.
  • the routing identifier can be carried through the SRv6 Locator TLV in the second message. Considering that the routing identifier occupies a large number of bytes, it can be carried by extending the sub-TLV.
  • the SRv6 Locator TLV includes a second sub-TLV that includes the route identifier.
  • a routing information transmission method includes: the second network device receives a message sent from the first network device, the message includes the SRv6 Locator and routing metrics from the first network domain. Identity and first route metric.
  • the first route metric value is the route metric value in the first network domain of the route corresponding to the SRv6 Locator from the first network device, and the second network device is located in the second network domain; the second network device determines to reach the SRv6 Locator based on the route metric identifier.
  • the routing cost of the corresponding route is used to indicate the method of calculating the route cost to the corresponding route to the SRv6 Locator.
  • the second network device can determine the route cost to the SRv6 Locator based on the route metric identifier.
  • the second network device in order to determine the route cost to reach the SRv6 Locator, can first determine the second route metric value of the corresponding route to the SRv6 Locator in the second network domain, and then determine the final route cost to the SRv6 Locator based on the route metric identifier. .
  • the route metric identifier is the first identifier, it indicates that when calculating the routing cost, the routing cost of the route corresponding to the SRv6 Locator arriving from the first network device in the first network domain and the routing cost corresponding to the SRv6 Locator arriving from the second network device need to be considered at the same time. If the second route metric value of the second network domain is determined, the second network device uses the sum of the first route metric value and the second route metric value as the routing cost of the route corresponding to the SRv6 Locator from the second network device.
  • the route metric identifier is the second identifier, it indicates that when calculating the routing cost, only the routing cost in the first network domain of the route corresponding to the SRv6 Locator from the first network device is considered, and the second network device uses the first route metric value as the value from the second network device. The routing cost of the network device reaching the route corresponding to the SRv6 Locator.
  • the route metric identifier is the third identifier, it indicates that when calculating the routing cost, only the routing cost of the route corresponding to the SRv6 Locator from the second network device in the second network domain needs to be considered, and the second network device uses the second route metric value as the value from the second network device. The routing cost of the network device reaching the route corresponding to the SRv6 Locator.
  • the message includes SRv6 Locator TLV, and the SRv6 Locator TLV includes routing metric identifier.
  • the SRv6 Locator TLV includes Flags, which include routing metric identifiers.
  • Flags includes extension bits that carry routing metric identifiers.
  • the SRv6 Locator TLV includes a first sub-TLV that includes a routing metric identifier.
  • a routing information transmission method includes: the network device passes the first The routing protocol receives the route advertisement message used to advertise the SRv6 Locator route.
  • the route advertisement message contains the SRv6 Locator and the routing identifier.
  • the routing identifier indicates the source of the SRv6 Locator.
  • the route advertisement message may include SRv6 Locator TLV, and the SRv6 Locator TLV includes the route identifier. Further, the SRv6 Locator TLV may include a second sub-TLV, and the second sub-TLV includes a routing identifier.
  • a routing information transmission device is provided.
  • the device is applied to a first network device and includes: a receiving unit configured to receive a first message from the first network domain, where the first message includes SRv6 Locator; a generation unit configured to generate a second message based on the first message.
  • the second message includes the SRv6 Locator and the routing metric identifier.
  • the routing metric identifier is used to indicate the method of calculating the routing cost of the route corresponding to the SRv6 Locator;
  • a sending unit configured to send a second message to a second network device in the second network domain, where the second message also includes a first route metric value in the first network domain of a route corresponding to the SRv6 Locator from the first network device.
  • the second message is an OSPFv3 LSA message.
  • the device further includes: a computing unit;
  • the calculation unit is configured to calculate the first routing metric value after receiving the first message.
  • the second message includes an SRv6 Locator TLV
  • the SRv6 Locator TLV includes a routing metric identifier
  • the SRv6 Locator TLV includes Flags, which include routing metric identifiers.
  • Flags includes extension bits, which carry routing metric identifiers.
  • the SRv6 Locator TLV includes a first sub-TLV, and the first sub-TLV includes a routing metric identifier.
  • the second message also includes a routing identifier, which indicates the source of the SRv6 Locator, and the routing identifier is used to prevent loops.
  • the device further includes: a determining unit;
  • the determining unit is configured to determine the routing identifier corresponding to the first network domain according to the first network domain and the configuration policy after receiving the first message.
  • the second message includes an SRv6 Locator TLV
  • the SRv6 Locator TLV includes a routing identifier
  • the SRv6 Locator TLV includes a second sub-TLV, and the second sub-TLV includes a routing identifier.
  • the first network domain is an ISIS domain
  • the second network domain is an OSPF domain
  • a routing information transmission device is provided.
  • the device is applied to a second network device and includes: a receiving unit configured to receive a message sent from the first network device.
  • the message includes a message sent from the first network domain.
  • the SRv6 location identifier Locator the routing metric identifier and the first routing metric value.
  • the first routing metric value is the routing metric value in the first network domain of the route corresponding to the SRv6 Locator from the first network device.
  • the second network device is located in the second Network domain; determination unit, used to determine the routing cost of the route corresponding to the SRv6Locator based on the routing metric identifier.
  • the determining unit is also configured to determine the second route metric value in the second network domain of the route corresponding to the route from the second network device to the SRv6 Locator.
  • the determining unit is specifically configured to: if the routing metric identifier is the first identifier, the third network device uses the sum of the first routing metric value and the second routing metric value as the value arriving from the second network device. The routing cost of the route corresponding to SRv6 Locator.
  • the determining unit is specifically configured to, if the route metric identifier is the second identifier, the second network device use the first route metric value as the routing cost of the route corresponding to the SRv6 Locator from the second network device.
  • the packet includes an SRv6 Locator TLV
  • the SRv6 Locator TLV includes a routing metric identifier
  • the SRv6 Locator TLV includes Flags, which include routing metric identifiers.
  • Flags includes extension bits, which carry routing metric identifiers.
  • the SRv6 Locator TLV includes a first sub-TLV, and the first sub-TLV includes a routing metric identifier.
  • a routing information transmission device includes: a receiving unit configured to receive a route advertisement message for announcing the SRv6 location identifier Locator route through the first routing protocol, where the route advertisement message includes SRv6 Locator and routing identifier, the routing identifier indicates the source of the SRv6 Locator; the processing unit is used to avoid introducing the SRv6 Locator into the second routing protocol when determining that the routing identifier is the identifier of the network device.
  • the route advertisement message includes an SRv6 Locator TLV
  • the SRv6 Locator TLV includes a route identifier
  • the SRv6 Locator TLV includes a second sub-TLV, and the second sub-TLV includes a routing identifier.
  • a communication device including: a processor and a memory;
  • the memory is used to store instructions or computer programs
  • the processor is configured to execute the instructions or computer programs in the memory, so that the communication device executes the method described in the first aspect or any possible implementation of the first aspect, or executes the third aspect.
  • a computer-readable storage medium including instructions that, when run on a computer, cause the computer to perform the steps described in the above first aspect or any of the possible implementations of the first aspect.
  • a computer program product includes a program.
  • the program When the program is run on a processor, the computer or network device performs the first aspect or any possible method of the first aspect.
  • a chip including: an interface circuit and a processor, the interface circuit and the processor
  • the processor is connected to a processor, and the processor is configured to cause the chip to execute the first aspect or a method in any possible design of the first aspect; or to execute the second aspect or a method in any possible design of the second aspect, or Implementing the method of the third aspect or any of the possible designs of the third aspect.
  • the first network device after receiving the first message from the first network domain, the first network device generates a second message based on the first message.
  • the first message includes the SRv6 Locator
  • the second message includes the SRv6 Locator and the route metric identifier.
  • the route metric identifier is used to indicate the method of calculating the routing cost of the route corresponding to the SRv6 Locator.
  • the first network device sends a second message to the second network device in the second network domain.
  • the second message also includes the first route metric value in the first network domain of the route corresponding to the SRv6 Locator from the first network device.
  • the first network device when the first network device introduces the SRv6 Locator route of the first network domain to the second network domain, it will add the route metric identifier to the generated second message, so that the network device in the second network domain calculates the arrival SRv6
  • the calculation method can be determined based on the route metric identifier, and then the route cost can be obtained based on the determined calculation method.
  • Figure 1 is a schematic diagram of a scenario for introducing SRv6 Locator provided by the embodiment of this application;
  • Figure 2 is a flow chart of a routing information transmission method provided by an embodiment of the present application.
  • Figure 3a is a schematic structural diagram of an SRv6 Locator TLV provided by an embodiment of this application;
  • Figure 3b is a schematic structural diagram of Flags provided by an embodiment of the present application.
  • Figure 3c is a schematic structural diagram of carrying routing metric identifiers in Flags provided by an embodiment of the present application.
  • Figure 3d is a schematic structural diagram of carrying a routing metric identifier in the first sub-TLV provided by an embodiment of the present application;
  • Figure 4a is a schematic diagram of a loop formation scenario provided by an embodiment of the present application.
  • Figure 4b is a schematic structural diagram of carrying a routing identifier in the second sub-TLV provided by an embodiment of the present application
  • Figure 5a is a schematic diagram of a scenario when the routing metric identifier provided by the embodiment of the present application is the first identifier
  • Figure 5b is a schematic diagram of a scenario when the route metric identifier provided by the embodiment of the present application is the second identifier;
  • Figure 6 is a flow chart of another routing information transmission method provided by an embodiment of the present application.
  • Figure 7 is a schematic diagram of preventing the formation of a loop provided by an embodiment of the present application.
  • Figures 8-10 are schematic structural diagrams of a routing information transmission device provided by embodiments of the present application.
  • Figure 11 is a schematic structural diagram of a network device provided by an embodiment of the present application.
  • Figure 12 is a schematic structural diagram of another network device provided by an embodiment of the present application.
  • each segment is identified in SRv6 by a segment ID (SID).
  • SID is a special IPv6 address that has both the routing capabilities of ordinary IPv6 addresses and the unique behavioral capabilities of SRv6.
  • Each SRv6 node maintains a SID table (actually part of the routing table), which is composed of many 128-bit SIDs. SIDs include location identifiers (Locator) and (function) Functions. Among them, Locator identifies the locator of the SRv6 node. Each node has a globally unique Locator value, which serves as the shared prefix of the local SID. Other nodes access the SID of this node through Locator routing.
  • node 1 in the ISIS domain is configured with an SRv6 Locator.
  • ASBR will send an LSA of the external type to node 0 in the OSPF domain.
  • the LSA includes the SRv6 Locator of node 1 and the ASBR arriving at node 1.
  • the route metric value (100). After receiving the LSA, Node 0 will determine the route to the SRv6 Locator.
  • the OSPF route types published by ASBR are divided into OE1 extra-area routes and OE2 extra-area routes.
  • OE1 extra-area routes indicate that the route metric value will be accumulated, that is, the OE1 route cost includes the external cost plus each link that the packet passes through.
  • the internal cost of the route for example, the cost from node 0 to node 1 is 110 (100+10);
  • OE2 external route means that the route metric value is not accumulated, that is, the OE2 route cost only includes the external cost, for example, node 0 to node 1
  • the cost is 100.
  • the LSA sent by ASBR to node 0 does not indicate the route type.
  • node 0 cannot determine whether it needs to add its own route metric value (10) to ASBR when determining the route to the SRv6 Locator. As a result, node 0 cannot determine whether it needs to add its own route metric value (10) to ASBR. The routing cost to reach the Locator.
  • the first network device receives the first message from the first network domain, and the first message includes the SRv6 Locator.
  • the first network device generates a second message based on the first message.
  • the second message includes the SRv6 Locator and a route metric identifier.
  • the route metric identifier is used to indicate a method of calculating the routing cost of the route corresponding to the SRv6 Locator. That is, the route metric identifier is used to indicate the route type.
  • the first network device sends the second packet to the second network device from the second network domain, so that the second network device can calculate the routing cost of the route corresponding to the SRv6 Locator based on the route metric identifier in the second packet.
  • the first network device is the ASBR in Figure 1
  • the first network domain is the ISIS domain
  • the second network domain is the OSPF domain
  • the second network device is node 0 in the OSPF domain.
  • the SRv6 Locator included in the first message indicates Node 1 in the ISIS domain.
  • ASBR will generate a second message including SRv6 Locator and routing metric identifier, and send the second message to node 0, so that node 0 can pass the second message according to the second message.
  • the route metric identifier in determines the way to calculate the route cost to the route corresponding to the SRv6 Locator, and then calculates the route cost to the route corresponding to the SRv6 Locator.
  • Figure 2 is a flow chart of a routing information transmission method provided by an embodiment of the present application. As shown in Figure 2, the method includes:
  • the network device of the first network domain generates the first message, and the first message includes the SRv6 Locator.
  • the network device located in the first network domain can actively flood its own SRv6 Locator into the domain through the first message, so that the nodes in the domain can determine the route to the SRv6 Locator.
  • the first network domain It can be the ISIS domain in Figure 1, and the network device of the first network domain is node 1 in Figure 1; or the first network domain can be the OSPF domain in Figure 1, and the network device of the first network domain is the node 1 in Figure 1. node 0. ,
  • the first message may also include a routing algorithm, and the routing algorithm may instruct the network device to calculate a constraint-based network route.
  • the routing algorithm may include a flexible algorithm (Flex-Algo) identifier so that the network device determines the route based on Flex-Algo.
  • Flex-Algo the range of algorithms that can be customized is Flex-Algo(128) ⁇ Flex-Algo(255).
  • Flex-Algo algorithm can be represented by Flex-Algo(k).
  • the Flex-Algo(k) only participates in this has local meaning in the logical topology of the algorithm.
  • S202 The network device of the first network domain sends the first message to the first network device.
  • the first network device is a network device spanning multiple network domains, and the multiple network domains include a first network domain and a second network domain.
  • the first network device is the ASBR in Figure 1
  • the first network domain is the ISIS domain
  • the second network domain is the OSPF domain.
  • the first network device generates a second message based on the first message.
  • the second message includes the SRv6 Locator and a route metric identifier.
  • the route metric identifier is used to indicate the method of calculating the routing cost of the route corresponding to the SRv6 Locator.
  • the first network device can determine the routing metric identifier according to the preconfigured routing policy, and generate the second message based on the first message and the routing metric identifier.
  • the routing metric identifier may be a first identifier (OE1) or a second identifier (OE2).
  • the first identifier is used to indicate that the network device needs to accumulate routing metric (Metric) values when calculating the routing cost
  • the second identifier is used to Instructs the network device to include only external route metric (Metric) values when calculating routing costs.
  • the first network device may determine that the second message needs to be processed based on the network domain where the network device that sent the first message is located and the correspondence between the preconfigured network domain and the routing metric identifier.
  • the routing metric identifier to be added to the packet For example, ASBR spans the ISIS1 domain, ISIS2 domain and OSPF domain respectively.
  • the pre-configured correspondence is that the ISIS1 domain corresponds to OE1 and the ISIS2 domain corresponds to OE2.
  • the determined The route metric identifier is OE1; when the ASBR receives the first message sent from the network device in the ISIS2 domain, the determined route metric identifier is OE2.
  • the second message may also include a first route metric value, which is a route metric value in the first network domain of the first network device arriving at the route corresponding to the SRv6 Locator.
  • a first route metric value is a route metric value in the first network domain of the first network device arriving at the route corresponding to the SRv6 Locator.
  • the first network device is the ASBR in Figure 1
  • the SRv6 Locator corresponds to node 1 in Figure 1
  • the first route metric value is 100.
  • the first route metric value may be pre-calculated by the first network device, or the first network device may calculate the route metric value for the route to the SRv6 Locator after the first network device receives the first message.
  • the second message when the second network domain spanned by the first network device is an OSPFv3 domain, the second message may be an OSPFv3 LSA message, and since the first network device enters the OSPFv3 domain from other network domains, the second message It is an external type OSPFv3 LSA message.
  • external type OSPFv3 LSA packets can include Autonomous system external LSA (Autonomous system external LSA), also called Type 5 LSA; and Non-So-Stubby Area (NSSA) external LSA, also called Type 7 LSA.
  • Type 5 LSA describes the network route to outside the OSPF autonomous system. It is sent by the ASBR and spread to the entire autonomous system.
  • Type 7 LSA and Type 5 LSA are the same, except that Type 5 LSA is flooded throughout the entire OSPF autonomous system, while Type 7 LSA is only within the non-pure stub area where the NSSA external LSA advertisement originates. carry out flooding.
  • the second message may include a segment routing location identifier length type value (SRv6 Locator TLV) based on Internet Protocol version 6, where the SRv6 Locator TLV includes a routing metric identifier.
  • SRv6 Locator TLV includes a type (Type) field, a length (Length) field, a route type (Route Type) field, an algorithm (Algorithm) field, and a location identifier length ( Locator Length field, Flags field, Metric field, Locator field and sub-TLV.
  • the routing metric identifier can be carried through the reserved bits in the existing fields in the SRv6 Locator TLV, for example, the routing metric identifier can be carried through flags (Flags).
  • the flags (Flags) format is shown in Figure 3b, including N bits (1bit), A bits (1bit) and reserved bits.
  • N bit When the SRv6 Locator uniquely identifies a node in the network, the N bit should be set, otherwise it is deleted.
  • the SRv6 Locator is configured for anycast, the A bit should be set.
  • the route metric identifier can be carried by extending a bit from the reserved bit.
  • the route metric identifier is carried by extending the E bit (1 bit).
  • the E bit When the E bit is 0, it indicates that the routing cost is calculated according to OE1; when the E bit is 1, it indicates that the routing cost is calculated according to OE2.
  • the routing metric identifier can also be carried by extending the sub-TLV corresponding to the SRv6 Locator TLV.
  • the SRv6 Locator LTV includes a first sub-LTV, and the first sub-LTV carries the routing metric identifier.
  • the SRv6 Locator LTV includes the first sub-TLV.
  • a loop phenomenon may occur when the SRv6 Locator route of the ISIS domain is introduced into the OSPF domain through ASBR.
  • the SRv6 Locator of FlexAlgo 128 is configured in the ISIS domain and is flooded in the domain.
  • ASBR1 will The SRv6 Locator is introduced into the OSPF1 domain, ASBR2 introduces the SRv6 Locator into the OSPF2 domain, and ASBR3 introduces the SRv6 Locator back into the ISIS domain, eventually forming a loop.
  • the first network device when it generates the second packet, it will add a routing identifier to the second packet, and use the routing identifier to indicate the source of the SRv6 Locator, thereby preventing loops.
  • the first network device is ASBR1 in Figure 4a, and the SRv6 Locator indicates a node in the ISIS domain, and the routing identifier indicates that the SRv6 Locator comes from the ISIS domain.
  • the first network device may determine the routing identifier corresponding to the first network domain according to the first network domain and the configuration policy.
  • the configuration policy is used to indicate the routing identifiers corresponding to different network domains.
  • the routing identifier is carried by the SRv6 Locator TLV.
  • the routing identifier occupies a large number of bytes, it can be carried by extending the sub-TLV.
  • the SRv6 Locator TLV includes a second sub-TLV that includes a routing identifier.
  • Figure 4b shows another structure of the SRv6 Locator TLV.
  • the SRv6 Locator TLV includes a second sub-TLV, and the second sub-TLV carries the routing identifier.
  • S204 The first network device sends the second message to the second network device in the second network domain.
  • the first network device after generating the second message, the first network device will flood the second message to the second network domain, so that each network device located in the second network domain can determine the arrival of SRv6 based on the second message.
  • Locator routing For example, the second network device can be node 0 in Figure 1, and the next hop of the route to the SRv6 Locator is the ASBR.
  • the second network device receives the second message, and determines the routing cost of the route corresponding to the SRv6 Locator based on the route metric identifier in the second message.
  • the second network device can obtain the routing metric identifier by parsing the second message, and then determine the routing cost to the SRv6 Locator based on the routing metric identifier.
  • the second route metric value may be pre-calculated by the second network device, or may be calculated by the second network device after receiving the second message sent by the first network device. This embodiment is for the second The calculation timing of route metric values is not limited.
  • node 1 in the ISIS domain is configured with the SRv6 Locator
  • node 1 can advertise the route to the SRv6 Locator to other nodes in the domain.
  • the ASBR the border router located in the ISIS domain and OSPFv3 domain
  • ASBR the next hop node to the SRv6 Locator
  • ASBR advertises a route to node 0 it will add a route metric identifier to the packet advertising the route.
  • the route metric identifier indicates how node 0 calculates the routing cost of the route corresponding to the SRv6 Locator. After receiving the route pass message sent by the ASBR, node 0 obtains the route metric identifier by parsing the route advertisement message, and determines the route cost to the SRv6 Locator based on the route metric identifier.
  • the route metric identifier can indicate different calculation methods, which will be explained separately below.
  • the second network device uses the sum of the first route metric value and the second route metric value as the route cost to the second network device.
  • the first route metric value is the route metric value from the first network device to the second network device
  • the second route metric value is the route metric value from the second network device to the first network device.
  • node 1 in the ISIS domain is configured with an SRv6 Locator with the routing algorithm: Flex-Algo (128).
  • node 0 calculates the second route metric value 10 to reach ASBR, determines that the next hop to node 0 is ASBR, and determines the route to node 0 based on the route metric indication E(0).
  • the overhead is 110.
  • the second network device uses the first route metric value as the routing cost for the route corresponding to the SRv6 Locator. That is, when the route metric identifier is the second identifier, the second network device only considers the out-of-area route metric value, that is, the first route metric value, when determining the routing cost of the route corresponding to the SRv6 Locator.
  • node 1 in the ISIS domain is configured with a Locator with the routing algorithm: Flex-Algo (128), and is flooded in the domain; when the ASBR is configured to introduce the Locator route to the ISIS domain, the routing metric is The second identifier (E(1)), after receiving the SRv6 Locator information flooded by node 1, generates an OSPFv3 Locator LSA message and floods it into the OSPFv3 domain. After receiving the AS External type LSA message, node 0 determines the route to the SRv6 Locator: the next hop is ASBR and the route cost is 100.
  • the first network device After receiving the first message from the first network domain, the first network device generates the second message according to the first message.
  • the first message includes the SRv6 Locator
  • the second message includes the SRv6 Locator and the route metric identifier.
  • the route metric identifier is used to indicate the method of calculating the routing cost of the route corresponding to the SRv6 Locator.
  • First network equipment The device sends a second message to the second network device in the second network domain, where the second message further includes a first route metric value in the first network domain of a route corresponding to the route from the first network device to the SRv6 Locator.
  • the first network device when the first network device introduces the SRv6 Locator route of the first network domain to the second network domain, it will add the route metric identifier to the generated second message, so that the network device in the second network domain calculates the arrival SRv6
  • the calculation method can be determined based on the route metric identifier, and then the route cost can be obtained based on the determined calculation method.
  • the second message includes the routing identifier.
  • the routing identifier For network equipment with the import function, when introducing the Locator of one network domain to another network domain, it also needs to verify the routing identifier to verify the location according to the routing identifier. The verification result determines whether to introduce it to another network domain.
  • FIG 6 is another routing information transmission method provided by an embodiment of the present application. As shown in Figure 6, the method includes:
  • the network device receives the route advertisement message used to advertise the SRv6 Locator route through the first routing protocol.
  • the network device is ASBR2 or ASBR3 in Figure 4a.
  • both the first routing protocol and the second routing protocol are OSPF.
  • the network device is ASBR3, the network device can run the first routing protocol OSPF. and the second routing protocol ISIS.
  • the route advertisement message received by the network device through the first routing protocol includes an SRv6 Locator and a routing identifier, and the routing identifier indicates the source of the SRv6 Locator.
  • the route identification is determined by the border routing device of the network domain where the target node is configured with SRv6 Locator.
  • the target node After receiving the route advertisement message sent by the target node, it determines the route identification corresponding to the network domain where the target node is located through the configuration policy, and then uses the The routing identifier is added to the route advertisement message to send the route advertisement message to the node in another network domain where it is located.
  • the target node is located in the ISIS domain in Figure 4a
  • the border routing device is ASBR1
  • the other network domain is OSPF1.
  • the network device After receiving the route advertisement message through the first network protocol, the network device first determines whether the route identifier in the route advertisement message is network before forwarding the route pass message to the network domain running the second network protocol. The identifier of the device, if yes, indicates that the SRv6 Locator in the route advertisement message comes from the second routing protocol. In order to prevent loop formation, the SRv6 Locator in the route advertisement message will no longer be introduced into the second routing protocol. If not, it means that the SRv6 Locator in the route advertisement message does not come from the second routing protocol, and you can continue to introduce the SRv6 Locator into the second routing protocol.
  • the SRv6 Locator of Flex Algo 128 is configured in the ISIS domain.
  • the SRv6 Locator is introduced into OSPF2
  • ASBR3 receives the route advertisement message forwarded by the node in the OSPF2 domain.
  • the SRv6 Locator is introduced into the ISIS domain
  • the network device can determine whether to forward or discard the received route advertisement message according to the route identifier in the route advertisement message, thereby avoiding the formation of a loop.
  • the device 800 can realize the function of the first network device in Figure 2 above, or the device 800 can Realize the functions of ASBR in Figure 1, Figure 5a, and Figure 5b, and ASBR1 in Figure 4a or Figure 7.
  • the device 800 may include a receiving unit 801 , a generating unit 802 and a sending unit 803 . These units can perform corresponding functions of the first network device in the above method examples.
  • the receiving unit 801 is used to support the device 800 to receive the first message in S203 in Figure 2; the generating unit 802 is used to support the device 800 to generate the second message in S203 in Figure 2; the sending unit 803 is used to support the device 800 performs S204 in Figure 2; and/or other processes performed by the first network device in the technology described herein.
  • the specific execution process please refer to the detailed description of the corresponding steps in the embodiment shown in Figure 2, and will not be repeated here.
  • the device 800 may also include: a computing unit;
  • the calculation unit is configured to calculate the first routing metric value after receiving the first message.
  • the device 800 may also include: a determining unit;
  • the determining unit is configured to, after receiving the first message, determine the routing identifier corresponding to the first network domain according to the first network domain and the configuration policy.
  • each functional unit in the embodiment of the present application can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the processing unit and the sending unit may be the same unit or different units.
  • the above integrated units can be implemented in the form of hardware or software functional units.
  • this figure is a structural diagram of another routing information transmission device provided by an embodiment of the present application.
  • the device 900 can implement the function of the second network device in Figure 2, or the device 900 can implement The function of node 0 in Figure 1, Figure 5a, Figure 5b, Figure 4a or ASBR2 in Figure 7.
  • the device 900 may include a receiving unit 901 and a determining unit 902 . These units can perform corresponding functions of the second network device in the above method examples.
  • the receiving unit 901 is used to support the device 900 in receiving the second message in S205 in Figure 2; the determining unit 902 is used to support the device 900 in performing S205 in Figure 2 to determine the route according to the route metric identifier in the second message. Overhead; and/or other processes performed by the second network device in the technology described herein. For the specific execution process, please refer to the detailed description of the corresponding steps in the embodiment shown in Figure 2, and will not be repeated here.
  • the determining unit 902 is also used to determine the second route metric value in the second network domain of the route corresponding to the route from the second network device to the SRv6 Locator.
  • the determining unit 902 is specifically configured to: if the route metric identifier is the first identifier, the third network The network device uses the sum of the first route metric value and the second route metric value as the route cost from the second network device to the route corresponding to the SRv6 Locator.
  • the determining unit 902 is specifically configured to, if the routing metric identifier is a second identifier, the second network device use the first routing metric value as the path from the second network device to the SRv6 The routing cost of the route corresponding to the Locator.
  • each functional unit in the embodiment of the present application can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the processing unit and the sending unit may be the same unit or different units.
  • the above integrated units can be implemented in the form of hardware or software functional units.
  • this figure is a structural diagram of another routing information transmission device provided by an embodiment of the present application.
  • the device 1000 can implement the functions of the network equipment in Figure 6, or the device 1000 can implement the functions of the network equipment in Figure 4a Or the functions of ASBR2 and ASBR3 in Figure 7.
  • the device 1000 may include a receiving unit 1001 and a processing unit 1002. These units can perform corresponding functions of the network device in the method example described in Figure 6 above.
  • the receiving unit 1001 is used to support the device 1000 to perform S601 in Figure 6; the processing unit 1002 is used to support the device 1000 to perform S602 in Figure 6; and/or other processes performed by network devices in the technology described herein.
  • the receiving unit 1001 is used to execute the network device in the above method embodiment to receive the route advertisement message used to advertise the SRv6 Locator route through the first routing protocol; the processing unit 1002 is used to execute the network device in the above method embodiment.
  • the processing unit 1002 is configured to avoid introducing the SRv6 Locator into the second routing protocol when determining that the routing identifier is the identifier of the network device.
  • the specific execution process please refer to the detailed description of the corresponding steps in the embodiment shown in Figure 6 above, and will not be repeated here.
  • each functional unit in the embodiment of the present application can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the processing unit and the sending unit may be the same unit or different units.
  • the above integrated units can be implemented in the form of hardware or software functional units.
  • Figure 11 is a schematic structural diagram of a network device provided by an embodiment of the present application.
  • the network device can be, for example, the first network device and the second network device in the above method embodiment, or it can also be the one in the embodiment shown in Figure 8
  • the device 800, the device 900 in the embodiment shown in FIG. 9 or the device 1000 in the embodiment shown in FIG. 10 is implemented by equipment.
  • the network device 1100 includes: a processor 1110, a communication interface 1120, and a memory 1130.
  • the number of processors 1110 in the communication device 1100 may be one or more. In FIG. 11 , one processor is taken as an example. In this embodiment of the present application, the processor 1110, the communication interface 1120 and the memory 1130 may be connected through a bus system or other means. In FIG. 11, the connection through the bus system 1140 is taken as an example.
  • Processor 1110 may be a CPU, NP, or a combination of CPU and NP.
  • the processor 1110 may further include hardware chips.
  • the above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • the above-mentioned PLD can be a complex programmable logic device (CPLD), a field programmable logic gate array (field-programmable gate array, FPGA), general array logic (generic array logic, GAL) or any combination thereof.
  • the memory 1130 may include volatile memory (volatile memory), such as random-access memory (RAM); the memory 1130 may also include non-volatile memory (non-volatile memory), such as flash memory (flash). memory), hard disk drive (hard disk drive, HDD) or solid-state drive (SSD); the memory 1130 may also include a combination of the above types of memory.
  • volatile memory volatile memory
  • non-volatile memory non-volatile memory
  • flash flash memory
  • HDD hard disk drive
  • SSD solid-state drive
  • the memory 1130 may, for example, store the aforementioned segment routing SR policy and the like.
  • the memory 1130 stores an operating system and programs, executable modules or data structures, or a subset thereof, or an extended set thereof, where the program may include various operating instructions for implementing various operations.
  • the operating system may include various system programs that are used to implement various basic services and handle hardware-based tasks.
  • the processor 1110 can read the program in the memory 1130 to implement the segment routing policy processing method provided by the embodiment of the present application.
  • the memory 1130 may be a storage device in the communication device 1100 , or may be a storage device independent of the communication device 1100 .
  • the bus system 1140 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus system 1140 can be divided into an address bus, a data bus, a control bus, etc. For ease of presentation, only one thick line is used in Figure 11, but it does not mean that there is only one bus or one type of bus.
  • Figure 12 is a schematic structural diagram of a network device 1200 provided by an embodiment of the present application.
  • the network device can be, for example, the first network device or the second network device in the above method embodiment, or it can also be the embodiment shown in Figure 8
  • the device 800 in the embodiment shown in FIG. 9, the device 900 in the embodiment shown in FIG. 9, or the device 1000 in the embodiment shown in FIG. 10 is implemented by equipment.
  • the network device 1200 includes: a main control board 1210 and an interface board 1230.
  • the main control board 1210 is also called the main processing unit (MPU) or the route processor card.
  • the main control board 1210 controls and manages each component in the network device 1200, including route calculation, device management, Equipment maintenance and protocol processing functions.
  • the main control board 1210 includes: a central processing unit 1211 and a memory 1212.
  • the interface board 1230 is also called a line processing unit (LPU), line card or service board.
  • the interface board 1230 is used to provide various service interfaces and implement data packet forwarding.
  • Business interfaces include but are not limited to Ethernet interfaces, POS (Packet over SONET/SDH) interfaces, etc.
  • Ethernet interfaces are, for example, Flexible Ethernet Clients (FlexE Clients).
  • the interface board 1230 includes: a central processor 1231, a network processor 1232, a forwarding entry memory 1234, and a physical interface card (physical interface card, PIC) 1233.
  • the central processor 1231 on the interface board 1230 is used to control and manage the interface board 1230 and communicate with the central processor 1211 on the main control board 1210 .
  • the network processor 1232 is used to implement packet forwarding processing.
  • the network processor 1232 may be in the form of a forwarding chip.
  • the processing of uplink packets includes: processing of packet incoming interfaces, forwarding table search; processing of downlink packets includes forwarding table search, etc.
  • the physical interface card 1233 is used to implement the docking function of the physical layer. The original traffic enters the interface board 1230 through this, and the processed packets are sent out from the physical interface card 1233.
  • the physical interface card 1233 includes at least one physical interface.
  • the management interface is also called the physical interface.
  • the physical interface card 1233 is also called a daughter card and can be installed on the interface board 1230. It is responsible for converting photoelectric signals into messages and checking the validity of the messages before forwarding them to the network processor 1232 for processing.
  • the central processor 1231 of the interface board 1203 can also perform the functions of the network processor 1232, such as implementing software forwarding based on a general-purpose CPU, so that the network processor 1232 is not required in the physical interface card 1233.
  • the network device 1200 includes multiple interface boards.
  • the network device 1200 also includes an interface board 1240.
  • the interface board 1240 includes: a central processor 1241, a network processor 1242, a forwarding entry memory 1244, and a physical interface card 1243.
  • the network device 1200 also includes a switching network board 1220.
  • the switching fabric unit 1220 may also be called a switching fabric unit (switch fabric unit, SFU).
  • SFU switching fabric unit
  • the switching network board 1220 is used to complete data exchange between the interface boards.
  • the interface board 1230 and the interface board 1240 can communicate through the switching network board 1220.
  • the main control board 1210 and the interface board 1230 are coupled.
  • the main control board 1210, the interface board 1230, the interface board 1240, and the switching network board 1220 are connected to the system backplane through a system bus to achieve intercommunication.
  • an inter-process communication protocol (IPC) channel is established between the main control board 1210 and the interface board 1230, and the main control board 1210 and the interface board 1230 communicate through the IPC channel.
  • IPC inter-process communication protocol
  • network device 1200 includes a control plane and a forwarding plane.
  • the control plane includes a main control board 1210 and a central processor 1231.
  • the forwarding plane includes various components that perform forwarding, such as forwarding entry memory 1234, physical interface card 1233, and network processing.
  • the control plane executes functions such as router, generates forwarding tables, processes signaling and protocol messages, configures and maintains device status.
  • the control plane sends the generated forwarding tables to the forwarding plane.
  • the network processor 1232 is based on the control plane.
  • the delivered forwarding table looks up the table and forwards the packets received by the physical interface card 1233.
  • the forwarding table delivered by the control plane may be stored in the forwarding table item storage 1234. In some embodiments, the control plane and forwarding plane may be completely separate and not on the same device.
  • the operations on the interface board 1240 in the embodiment of the present application are consistent with the operations on the interface board 1230, and will not be described again for the sake of simplicity.
  • the network device 1200 in this embodiment may correspond to the first network device in the above method embodiments, and the main control board 1210, the interface board 1230 and/or the interface board 1240 in the network device 1200 may implement the above methods.
  • the various steps in the embodiment will not be described again here.
  • main control boards there may be one or more main control boards, and when there are multiple main control boards, they may include a main main control board and a backup main control board.
  • network equipment can have at least one switching network board, which enables data exchange between multiple interface boards through the switching network board, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of network equipment with a distributed architecture are greater than those with a centralized architecture.
  • the network device can also be in the form of only one board, that is, there is no switching network board. The functions of the interface board and the main control board are integrated on this board. In this case, the central processor and main control board on the interface board The central processor on the board can be combined into one central processor on this board to perform the superimposed functions of the two.
  • This form of equipment has low data exchange and processing capabilities (for example, low-end switches or routers and other networks equipment). The specific architecture used depends on the specific Individual networking deployment scenarios.
  • the above network device can be implemented as a virtualization device.
  • the virtualization device may be a virtual machine (VM) running a program for sending packets, and the virtual machine is deployed on a hardware device (for example, a physical server).
  • a virtual machine refers to a complete computer system with complete hardware system functions simulated by software and running in a completely isolated environment.
  • Virtual machines can be configured as network devices.
  • network devices can be implemented based on general-purpose physical servers combined with network functions virtualization (NFV) technology.
  • NFV network functions virtualization
  • Network devices are virtual hosts, virtual routers, or virtual switches. By reading this application, those skilled in the art can combine NFV technology to virtualize a network device with the above functions on a general physical server, which will not be described again here.
  • the embodiment of the present application also provides a chip, including a processor and an interface circuit.
  • the interface circuit is used to receive instructions and transmit them to the processor; the processor, for example, can be a specific implementation form of the device 800 shown in Figure 8 , can be used to perform the above method.
  • the processor is coupled to a memory, and the memory is used to store programs or instructions.
  • the chip system implements the method in any of the above method embodiments.
  • processors in the chip system there may be one or more processors in the chip system.
  • the processor can be implemented in hardware or software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor implemented by reading software code stored in memory.
  • the memory may be integrated with the processor or may be provided separately from the processor, which is not limited by this application.
  • the memory can be a non-transient processor, such as a read-only memory ROM, which can be integrated on the same chip as the processor, or can be separately provided on different chips.
  • This application describes the type of memory, and the relationship between the memory and the processor. There is no specific limitation on how the processor is configured.
  • the chip system can be a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or a system on chip (SoC) , it can also be a central processor unit (CPU), a network processor (NP), a digital signal processing circuit (digital signal processor, DSP), or a microcontroller ( micro controller unit (MCU)), it can also be a programmable logic device (PLD) or other integrated chip.
  • FPGA field programmable gate array
  • ASIC application-specific integrated circuit
  • SoC system on chip
  • CPU central processor unit
  • NP network processor
  • DSP digital signal processing circuit
  • MCU microcontroller
  • PLD programmable logic device
  • Embodiments of the present application also provide a computer-readable storage medium, which includes instructions or computer programs that, when run on a computer, cause the computer to execute the routing information transmission method provided in the above embodiments.
  • Embodiments of the present application also provide a computer program product containing instructions or computer programs, which, when run on a computer, cause the computer to execute the routing information transmission method provided in the above embodiments.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of units is only a logical service division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • a unit described as a separate component may or may not be physically separate.
  • a component shown as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each business unit in various embodiments of this application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above integrated units can be implemented in the form of hardware or software business units.
  • Integrated units may be stored in a computer-readable storage medium when implemented in the form of software business units and sold or used as independent products.
  • the technical solution of the present application is essentially or contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program code. .
  • Computer-readable media includes computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • Storage media can be any available media that can be accessed by a general purpose or special purpose computer.

Abstract

本申请公开了一种路由信息传输方法及装置，方法包括：第一网络设备在接收到来自第一网络域的第一报文后，根据第一报文生成第二报文。其中，第一报文包括SRv6 Locator，第二报文包括SRv6 Locator以及路由度量标识，该路由度量标识指示计算到达SRv6 Locator对应路由的路由开销的方式。第一网络设备向第二网络域的第二网络设备发送第二报文，该第二报文还包括从第一网络设备到达SRv6 Locator对应的路由在第一网络域内的第一路由度量值。即，第一网络设备在向第二网络域引入第一网络域的SRv6 Locator路由时，将向生成的第二报文中添加路由度量标识，以使得第二网络域中网络设备在计算到达SRv6 Locator对应路由的路由开销时，可以根据路由度量标识确定计算方式，进而根据确定的计算方式获得路由开销。

Description

一种路由信息传输方法及装置
本申请要求于2022年08月09日提交的申请号为202210953219.8、申请名称为“一种路由信息传输方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种路由信息传输方法及装置。
背景技术
目前运营商网络最常用的内部网关协议(interior Gateway Protocols，IGP)协议是开放式最短路径优先(open shortest path first，OSPF)，通过扩展OSPFv3协议携带基于第六版因特网协议(internet protocol version 6，IPv6)转发平面的段路由(segment routing IPv6，SRv6)信息，以实现SRv6控制平面的功能。
在OSPFv3 SRv6场景下，还可以引入域外节点，以使得域内节点可以计算到达域外节点的路由。具体地，自治系统边界路由器(autonomous system boundary router，ASBR)在引入域外节点的位置标识(locator)后，生成链路状态通告(link-state advertisement，LSA)并向域内泛洪，以使得域内节点根据LSA计算到达域外节点的路由。然而，由于受限于当前LSA固有结构，导致无法在LSA中携带有与Locator相关的信息，影响路由计算。
发明内容
本申请提供了一种路由信息传输方法及装置，以通过在路由报文中携带路由度量类型，使得网络设备能够计算到达域外节点的路由。
在本申请第一方面，提供了一种路由信息传输方法，该方法包括：第一网络设备接收来自第一网络域的第一报文，该第一报文包括SRv6 Locator，并根据该第一报文生成第二报文，该第二报文包括SRv6 Locator以及路由度量标识，该路由度量标识用于指示计算到达SRv6 Locator对应路由的路由开销的方式。第一网络设备向第二网络域的第二网络设备发送第二报文，以使得第二网络设备在接收到第二报文时，计算到达SRv6 Locator对应路由的路由开销。其中，第二报文还包括第一网络设备到达SRv6 Locator对应的路由在第一网络域内的第一路由度量值。即，本申请中第一网络设备在向第二网络域引入第一网络域的SRv6 Locator路由时，将向生成的第二报文中添加路由度量标识，以使得第二网络域中网络设备在计算到达SRv6 Locator对应路由的路由开销时，可以根据路由度量标识确定计算方式，进而根据确定的计算方式获得路由开销。
其中，当第一网络设备通过OSPFv3协议通告自身的路由状态时，第二报文可以为OSPFv3 LSA报文。
在一种可能的实现方式中，第一网络设备在接收到第一报文之后，还可以计算得到第一路由度量值，以便在第二报文中添加该第一路由度量值，进而便于第二网络设备利用第一路由度量值计算到达SRv6 Locator的路由开销。
其中，路由度量标识可以通过以下方式携带在第二报文中：第二报文包括SRv6 Locator长度类型值(type length value，TLV)，该SRv6 Locator TLV包括路由度量标识。其中，在通过SRv6 Locator TLV携带路由度量标识时，可以通过该SRv6 Locator TLV中的标志位Flag来携带路由度量标识。进一步地，Flags包括扩展位，通过该扩展位携带路由度量标识。 或者，SRv6 Locator TLV包括第一子TLV，通过该第一子TLV携带路由度量标识，即通过扩展SRv6 Locator TLV的子TLV的方式来携带路由度量标识。
在一种可能的实现方式中，第二报文还可以包括路由标识，该路由标识指示SRv6 Locator的来源，用于防止环路。即，通过路由标识防止携带SRv6 Locator的报文发送至第一网络域。
其中，第二报文中的路由标识可以由第一网络设备在接收到第一报文后，由第一网络设备根据第一网络域以及配置策略确定与第一网络域对应的路由标识。其中，配置策略用于指示不同网络域对应的路由标识，第一网络域可以为中间系统到中间系统(intermediate system to intermediate system，ISIS)域，第二网络域为OSPF域。
具体地，路由标识可以通过第二报文中的SRv6 Locator TLV来携带。考虑到路由标识所占用的字节数较多，则可以通过扩展子TLV的方式携带。例如，SRv6 Locator TLV包括第二子TLV，该第二子TLV包括该路由标识。
在本申请第二方面，提供了一种路由信息传输方法，该方法包括：第二网络设备接收来自第一网络设备发送的报文，该报文包括来自第一网络域的SRv6 Locator、路由度量标识和第一路由度量值。其中，第一路由度量值为从第一网络设备到达SRv6 Locator对应的路由在第一网络域内的路由度量值，第二网络设备位于第二网络域；第二网络设备根据路由度量标识确定达到SRv6Locator对应路由的路由开销。其中，路由度量标识用于指示计算到达SRv6 Locator对应路由的路由开销的方式，第二网络设备在接收到包括路由度量标识的报文后，可以根据路由度量标识确定到达SRv6 Locator的路由开销。
其中，第二网络设备为确定到达SRv6 Locator的路由开销，可以先确定其到达SRv6 Locator对应路由在第二网络域内的第二路由度量值，进而在根据路由度量标识确定到达SRv6 Locator的最终路由开销。
具体地，若路由度量标识为第一标识，表明在计算路由开销时需要同时考虑第一网络设备到达SRv6 Locator对应路由在第一网络域的路由开销，以及第二网络设备到达SRv6对应路由在第二网络域的第二路由度量值，则第二网络设备将第一路由度量值和第二路由度量值的和值作为从第二网络设备到达SRv6 Locator对应路由的路由开销。
若路由度量标识为第二标识，表明在计算路由开销时仅需考虑第一网络设备到达SRv6 Locator对应路由在第一网络域的路由开销，第二网络设备将第一路由度量值作为从第二网络设备到达SRv6 Locator对应路由的路由开销。
若路由度量标识为第三标识，表明在计算路由开销时仅需考虑第二网络设备到达SRv6 Locator对应路由在第二网络域的路由开销，第二网络设备将第二路由度量值作为从第二网络设备到达SRv6 Locator对应路由的路由开销。
其中，报文包括SRv6 Locator TLV，该SRv6 Locator TLV包括路由度量标识。或者，SRv6 Locator TLV包括标志位Flags，该Flags包括路由度量标识。或者，Flags包括扩展位，该扩展位携带路由度量标识。或者，SRv6 Locator TLV包括第一子TLV，该第一子TLV包括路由度量标识。
在本申请第三方面，提供了一种路由信息传输方法，该方法包括：网络设备通过第一 路由协议接收用于通告SRv6 Locator路由的路由通告报文，该路由通告报文包含SRv6 Locator和路由标识，该路由标识指示SRv6 Locator的来源。当网络设备确定该路由标识为自身所对应的标识时，不对该报文进行转发，从而避免将SRv6 Locator引入到第二路由协议中。
其中，路由通告报文可以包括SRv6 Locator TLV，该SRv6 Locator TLV包括路由标识。进一步地，该SRv6 Locator TLV可以包括第二子TLV，该第二子TLV包括路由标识。
在本申请第四方面，提供了一种路由信息传输装置，该装置应用于第一网络设备，包括：接收单元，用于接收来自第一网络域的第一报文，第一报文包括SRv6 Locator；生成单元，用于根据第一报文生成第二报文，该第二报文包括SRv6 Locator以及路由度量标识，该路由度量标识用于指示计算到达SRv6 Locator对应路由的路由开销的方式；发送单元，用于向第二网络域的第二网络设备发送第二报文，第二报文还包括从第一网络设备到达SRv6 Locator对应的路由在第一网络域内的第一路由度量值。
在一种可能的实现方式中，第二报文为OSPFv3 LSA报文。
在一种可能的实现方式中，装置还包括：计算单元；
计算单元，用于在接收到第一报文之后，计算得到第一路由度量值。
在一种可能的实现方式中，第二报文包括SRv6 Locator TLV，该SRv6 Locator TLV包括路由度量标识。
在一种可能的实现方式中，SRv6 Locator TLV包括标志位Flags，该Flags包括路由度量标识。
在一种可能的实现方式中，Flags包括扩展位，该扩展位携带路由度量标识。
在一种可能的实现方式中，SRv6 Locator TLV包括第一子TLV，该第一子TLV包括路由度量标识。
在一种可能的实现方式中，第二报文还包括路由标识，该路由标识指示SRv6 Locator的来源，路由标识用于防止环路。
在一种可能的实现方式中，装置还包括：确定单元；
确定单元，用于在接收到第一报文后，根据第一网络域以及配置策略确定与第一网络域对应的路由标识。
在一种可能的实现方式中，第二报文包括SRv6 Locator TLV，该SRv6 Locator TLV包括路由标识。
在一种可能的实现方式中，SRv6 Locator TLV包括第二子TLV，该第二子TLV包括路由标识。
在一种可能的实现方式中，第一网络域为ISIS域，第二网络域为OSPF域。
在本申请第五方面，提供了一种路由信息传输装置，装置应用于第二网络设备，包括：接收单元，用于接收来自第一网络设备发送的报文，报文包括来自第一网络域的SRv6位置标识Locator、路由度量标识和第一路由度量值，第一路由度量值为从第一网络设备到达SRv6 Locator对应的路由在第一网络域内的路由度量值，第二网络设备位于第二网络域；确定单元，用于根据路由度量标识确定达到SRv6Locator对应路由的路由开销。
在一种可能的实现方式中，确定单元，还用于确定从第二网络设备到达SRv6 Locator对应的路由在第二网络域内的第二路由度量值。
在一种可能的实现方式中，确定单元，具体用于若路由度量标识为第一标识，第三网络设备将第一路由度量值和第二路由度量值的和值作为从第二网络设备到达SRv6 Locator对应路由的路由开销。
在一种可能的实现方式中，确定单元，具体用于若路由度量标识为第二标识，第二网络设备将第一路由度量值作为从第二网络设备到达SRv6 Locator对应路由的路由开销。
在一种可能的实现方式中，报文包括SRv6 Locator TLV，该SRv6 Locator TLV包括路由度量标识。
在一种可能的实现方式中，SRv6 Locator TLV包括标志位Flags，该Flags包括路由度量标识。
在一种可能的实现方式中，Flags包括扩展位，该扩展位携带路由度量标识。
在一种可能的实现方式中，SRv6 Locator TLV包括第一子TLV，该第一子TLV包括路由度量标识。
在本申请第六方面，提供了一种路由信息传输装置，装置包括：接收单元，用于通过第一路由协议接收用于通告SRv6位置标识Locator路由的路由通告报文，路由通告报文包含SRv6 Locator和路由标识，该路由标识指示SRv6 Locator的来源；处理单元，用于确定路由标识为网络设备的标识时，避免将SRv6 Locator引入到第二路由协议中。
在一种可能的实现方式中，路由通告报文包括SRv6 Locator TLV，该SRv6 Locator TLV包括路由标识。
在一种可能的实现方式中，SRv6 Locator TLV包括第二子TLV，该第二子TLV包括路由标识。
在本申请第七方面，提供了一种通信设备，所述设备包括：处理器和存储器；
所述存储器，用于存储指令或计算机程序；
所述处理器，用于执行所述存储器中的所述指令或计算机程序，以使得所述通信设备执行第一方面或第一方面中任一种可能实现方式中所述的方法，或者执行第二方面或第二方面中任一种可能实现方式中所述的方法，或者第三方面或第三方面中任一种可能实现方式中所述的方法。
在本申请第八方面，提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行以上第一方面或第一方面中任一种可能实现方式中所述的方法，或者执行第二方面或第二方面中任一种可能实现方式中所述的方法，或者执行第三方面或第三方面中任一种可能实现方式中所述的方法。
在本申请第九方面，提供了一种计算机程序产品，该计算机程序产品包含程序，当程序在处理器上运行时，使得计算机或网络设备执行第一方面或第一方面的任意一种可能的设计中的方法，或者执行第二方面或第二方面的任意一种可能的设计中的方法，或者执行第三方面或第三方面中任意一种可能的设计中的方法。
在本申请第十方面，提供了一种芯片，包括：接口电路和处理器，该接口电路和处理 器相连接，该处理器用于使得芯片执行第一方面或第一方面的任意一种可能的设计中的方法；或者执行第二方面或第二方面的任意一种可能的设计中的方法，或者执行第三方面或第三方面中任意一种可能的设计中的方法。
通过本申请实施例提供的技术方案，第一网络设备在接收到来自第一网络域的第一报文后，根据第一报文生成第二报文。其中，第一报文包括SRv6 Locator，第二报文包括SRv6 Locator以及路由度量标识，该路由度量标识用于指示计算到达SRv6 Locator对应路由的路由开销的方式。第一网络设备向第二网络域的第二网络设备发送第二报文，该第二报文还包括从第一网络设备到达SRv6 Locator对应的路由在第一网络域内的第一路由度量值。即，第一网络设备在向第二网络域引入第一网络域的SRv6 Locator路由时，将向生成的第二报文中添加路由度量标识，以使得第二网络域中网络设备在计算到达SRv6 Locator对应路由的路由开销时，可以根据路由度量标识确定计算方式，进而根据确定的计算方式获得路由开销。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例提供的一种引入SRv6 Locator场景示意图；
图2为本申请实施例提供的一种路由信息传输方法流程图；
图3a为本申请实施例提供的一种SRv6 Locator TLV结构示意图；
图3b为本申请实施例提供的一种标识Flags结构示意图；
图3c为本申请实施例提供的一种在Flags中携带路由度量标识结构示意图；
图3d为本申请实施例提供的一种在第一子TLV中携带路由度量标识结构示意图；
图4a为本申请实施例提供的一种形成环路场景示意图；
图4b为本申请实施例提供的一种在第二子TLV中携带路由标识结构示意图；
图5a为本申请实施例提供的一种路由度量标识为第一标识时的场景示意图；
图5b为本申请实施例提供的一种路由度量标识为第二标识时的场景示意图；
图6为本申请实施例提供的另一种路由信息传输方法流程图；
图7为本申请实施例提供的一种防止形成环路示意图；
图8-10为本申请实施例提供的一种路由信息传输装置结构示意图；
图11为本申请实施例提供的一种网络设备结构示意图；
图12为本申请实施例提供的另一种网络设备结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本申请中的方案，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅是本申请一部分实施例，而不是全部的实施例。
为便于理解本申请实施例提供的技术方案，下面将先对本申请所涉及的技术进行说明。
在OSPFv3支持SRv6场景下，ASBR可以从ISIS域向OSPF域引入SRv6 Locator路由。通常情况下，SRv6中通过段标识(Segment ID，SID)标识每个段(Segment)，SID是一种特殊的IPv6地址，既有普通IPv6地址的路由能力，又有SRv6特有的行为能力。每个SRv6节点都会维护一张SID表(实际上是路由表的一部分)，由许多128bit的SID组成，SID包括位置标识(Locator)和(功能)Function。其中，Locator标识SRv6节点的定位器，每个节点有一个全局唯一的Locator值，作为本地SID的共享前缀，其他节点通过Locator路由访问本节点SID。
如图1所示，ISIS域内的节点1配置了SRv6 Locator，ASBR将向OSPF域内的节点0发送报文类型为外部(External)类型的LSA，该LSA包括节点1的SRv6 Locator以及ASBR到达节点1的路由度量值(100)。节点0在接收到LSA后，将确定到达SRv6 Locator的路由。
其中，由ASBR发布的OSPF路由类型分为OE1域外路由和OE2域外路由，OE1域外路由表示将累加路由度量(Metric)值，即OE1路由开销包括在外部开销基础上加上分组经过的每条链路的内部开销，例如节点0到节点1的开销为110(100+10)；OE2域外路由表示不累加路由度量(Metric)值，即OE2路由开销只包含外部开销，例如，节点0到节点1的开销为100。而目前ASBR向节点0所发送的LSA并未指示路由类型，导致节点0在确定到达SRv6 Locator的路由时无法确定是否需要加上自身到达ASBR的路由度量值(10)，从而导致节点0无法确定到达Locator的路由开销。
基于此，本申请实施例提供了一种路由信息传输方法，具体为，在第一网络设备接收到来自第一网络域的第一报文，该第一报文包括SRv6 Locator。第一网络设备根据第一报文生成第二报文，该第二报文包括SRv6Locator以及路由度量标识，该路由度量标识用于指示计算到达SRv6 Locator对应路由的路由开销的方式。即，路由度量标识用来指示路由类型。第一网络设备将第二报文发送给来自第二网络域的第二网络设备，以使得第二网络设备可以根据第二报文中的路由度量标识计算到达SRv6 Locator对应路由的路由开销。
具体地，第一网络设备如为图1中的ASBR，第一网络域为ISIS域、第二网络域为OSPF域、第二网络设备为OSPF域中的节点0。第一报文中所包括的SRv6 Locator指示ISIS域中的节点1。ASBR在接收到节点1发送的第一报文后，将生成包括SRv6 Locator以及路由度量标识的第二报文，并将该第二报文发送给节点0，以使得节点0根据第二报文中的路由度量标识确定计算到达SRv6 Locator对应路由的路由开销的方式，进而计算到达SRv6 Locator对应路由的路由开销。
为便于理解本申请实施例提供的技术方案，下面将结合附图进行说明。
参见图2，该图为本申请实施例提供的一种路由信息传输方法流程图，如图2所示，所述方法包括：
S201：第一网络域的网络设备生成第一报文，该第一报文包括SRv6 Locator。
本实施例中，位于第一网络域的网络设备可以通过第一报文主动向域内泛洪自身的SRv6 Locator，以使得域内的节点可以确定到达该SRv6 Locator的路由。例如，第一网络域 可以为图1中的ISIS域，第一网络域的网络设备为图1中的节点1；或者，第一网络域可以为图1中的OSPF域，第一网络域的网络设备为图1中的节点0。，
其中，第一报文还可以包括路由算法，该路由算法可以指示网络设备计算基于约束的网络路由。具体地，该路由算法可以包括灵活算法(Flex-Algo)标识，以便网络设备根据Flex-Algo确定路由。其中，可以自定义的算法范围是Flex-Algo(128)～Flex-Algo(255)，每一个Flex-Algo算法可以使用Flex-Algo(k)表示，该Flex-Algo(k)只在参与这个算法的逻辑拓扑中具有本地意义。
S202：第一网络域的网络设备向第一网络设备发送第一报文。
其中，第一网络设备为跨多个网络域的网络设备，该多个网络域包括第一网络域和第二网络域。例如，第一网络设备为图1中的ASBR，第一网络域为ISIS域、第二网络域为OSPF域。
S203：第一网络设备根据第一报文生成第二报文，该第二报文包括SRv6 Locator和路由度量标识，该路由度量标识用于指示计算到达SRv6 Locator对应路由的路由开销的方式。
本实施例中，第一网络设备在接收到第二网络设备发送的第一报文后，可以根据预先配置的路由策略确定路由度量标识，以根据第一报文和路由度量标识生成第二报文。具体地，路由度量标识可以为第一标识(OE1)或第二标识(OE2)，第一标识用于指示网络设备在计算路由开销时，需要累加路由度量(Metric)值，第二标识用于指示网络设备在计算路由开销时仅包含外部路由度量(Metric)值。
其中，第一网络设备在接收到第一报文后，可以根据发送第一报文的网络设备所在的网络域以及预先配置的网络域与路由度量标识之间的对应关系，确定需要在第二报文所要添加的路由度量标识。例如，ASBR分别跨ISIS1域、ISIS2域以及OSPF域，预先配置的对应关系为，ISIS1域对应OE1、ISIS2域对应OE2，当ASBR接收来自ISIS1域中网络设备发送的第一报文后，所确定的路由度量标识为OE1；当ASBR接收来自ISIS2域中网络设备发送的第一报文后，所确定的路由度量标识为OE2。
其中，第二报文还可以包括第一路由度量值，该第一路由度量值为第一网络设备到达SRv6 Locator对应路由在第一网络域内的路由度量值。例如，第一网络设备为图1中的ASBR、SRv6 Locator对应图1中的节点1，第一路由度量值为100。其中，第一路由度量值可以是第一网络设备预先计算的，也可以是第一网络设备在接收到第一报文之后，第一网络设备计算到达SRv6 Locator路由的路由度量值。
其中，当第一网络设备所跨的第二网络域为OSPFv3域时，第二报文可以为OSPFv3LSA报文，且由于第一网络设备从其他网络域向OSPFv3域进入，因此该第二报文为外部类型OSPFv3 LSA报文。其中，外部类型OSPFv3 LSA报可以包括自治系统外部LSA(Autonomous system external LSA)，也称第5类LSA；和非纯末梢区域(Not-So-Stubby Area，NSSA)外部LSA，也称第7类LSA。其中，第5类LSA描述了前往OSPF自治系统外的网络路由，它由ASBR发送并被扩散到整个自治系统中。第7类LSA和第5类LSA是相同的，只是第5类LSA是在整个OSPF自治系统内进行泛洪扩散，而第7类LSA仅仅在始发这个NSSA外部LSA通告的非纯末梢区域内部进行泛洪扩散。
可选地，第二报文可以包括基于第6版本因特网协议的段路由位置标识长度类型值(SRv6 Locator TLV)，在该SRv6 Locator TLV包括路由度量标识。其中，参见图3a所示的SRv6 Locator TLV的结构图，该SRv6 Locator TLV包括类型(Type)字段、长度(Length)字段、路由类型(Route Type)字段、算法(Algorithm)字段、位置标识长度(Locator Length)字段、标志(Flags)字段、度量(Metric)字段、位置标识(Locator)字段以及子TLV。
其中，可以通过SRv6 Locator TLV中已有字段中的保留位来携带路由度量标识，例如，通过标志(Flags)来携带路由度量标识。其中，标志(Flags)格式如图3b所示，包括N位(1bit)、A位(1bit)和保留(Reserved)位。当SRv6 Locator唯一地标识网络中的一个节点时，应当设置N位，否则删除。当SRv6 Locator配置为任播(anycast)时，应该设置A位。在具体实现时，可以通过从保留位中扩展一个bit来携带路由度量标识。例如图3c所示，通过扩展E位(1bit)携带路由度量标识。当E位为0时，指示按照OE1计算路由开销；当E位为1时，指示按照OE2计算路由开销。
可选地，还可以通过扩展SRv6 Locator TLV对应的子TLV的方式携带路由度量标识，例如，SRv6 Locator LTV包括第一子LTV，该第一子LTV携带路由度量标识。参见图3d所示的SRv6 Locator LTV结构图，在该SRv6 Locator LTV中包括第一子TLV。
在一些场景下，在通过ASBR向OSPF域内引入ISIS域的SRv6 Locator路由时，可能出现环路现象，如图4a所示，ISIS域内配置了FlexAlgo 128的SRv6 Locator，并在域内泛洪，ASBR1将该SRv6 Locator引入到OSPF1域，ASBR2将该SRv6 Locator引入到OSPF2域，ASBR3将该SRv6 Locator引入回ISIS域，最终形成了环路。为避免环路的形成，第一网络设备在生成第二报文时，将在该第二报文中添加路由标识，通过该路由标识指示SRv6 Locator的来源，从而防止环路。例如第一网络设备为图4a中的ASBR1，SRv6 Locator指示ISIS域内的节点，则路由标识指示SRv6 Locator来自ISIS域。
其中，第一网络设备在接收到第一网络域的网络设备发送的第一报文后，可以根据第一网络域以及配置策略确定与第一网络域对应的路由标识。其中，配置策略用于指示不同网络域对应的路由标识。例如配置策略为当SRv6 Locator来自ISIS1域时，其对应的路由标识＝100；当SRv6 Locator来自ISIS2域时，其对应的路由标识＝200，第一网络设备在接收到来自ISIS1域中网络设备发送的第一报文后，确定该第一报文中的SRv6 Locator来自ISIS1域，则对应的路由标识＝100，则第二报文中包括该路由标识＝100。
可选地，当第二报文包括SRv6 Locator TLV，则通过该SRv6 Locator TLV携带路由标识。考虑到路由标识所占用的字节数较多，则可以通过扩展子TLV的方式来携带。具体地，SRv6 Locator TLV包括第二子TLV，该第二子TLV包括路由标识。例如图4b所示的SRv6 Locator TLV的另一种结构，该SRv6 Locator TLV中包括第二子TLV，通过该第二子TLV携带路由标识。
S204：第一网络设备向第二网络域的第二网络设备发送第二报文。
本实施例中，第一网络设备在生成第二报文后，将向第二网络域泛洪第二报文，以使得位于第二网络域的各网络设备可以根据第二报文确定到达SRv6 Locator的路由。例如，第二网络设备可以为图1中节点0，到达SRv6 Locator的路由的下一跳为ASBR。
S205：第二网络设备接收第二报文，并根据第二报文中的路由度量标识确定到达SRv6 Locator对应路由的路由开销。
本实施例中，第二网络设备接收到第二报文后，通过解析第二报文可以获得路由度量标识，进而根据该路由度量标识确定到达SRv6 Locator的路由开销。
其中，第二路由度量值可以是第二网络设备预先计算完成的，也可以是第二网络设备在接收到第一网络设备发送的第二报文后，计算获得的，本实施例对于第二路由度量值的计算时机不做限定。
为便于理解，参见图1所示的应用场景图，当ISIS域内的节点1配置了SRv6 Locator，节点1可以向域内的其他节点通告到达SRv6 Locator的路由。位于ISIS域和OSPFv3域的边界路由器ASBR在接收到节点1所通告的路由后，将向OSPFv3域内的节点0通告到达SRv6 Locator的路由，即到达SRv6 Locator的下一跳节点为ASBR。其中，ASBR在向节点0通告路由时，将向通告路由的报文中添加路由度量标识，该路由度量标识指示节点0计算到达SRv6 Locator对应路由的路由开销的方式。节点0在接收到ASBR发送的路由通过报文后，通过解析该路由通告报文获取路由度量标识，以根据该路由度量标识确定到达SRv6 Locator的路由开销。
其中，路由度量标识可以指示不同的计算方式，下面将分别进行说明。
若路由度量标识为第一标识，第二网络设备将第一路由度量值和第二路由度量值的和值作为达到第二网络设备的路由开销。其中，第一路由度量值为第一网络设备到达第二网络设备的路由度量值，第二路由度量值为第二网络设备到达第一网络设备的路由度量值。例如，图5a所示，ISIS域中的节点1配置了路由算法为：Flex-Algo(128)的SRv6 Locator，节点1向ASBR发送的第一报文中包括：路由算法-Flex-Algo(128)、路由度量Metric＝0、Locator＝1128：：/64；ASBR在接收到第一报文后，计算到达节点1的第一路由度量值为100，则生成的OSPFv3 Locator LSA报文中包括Metric＝100且增加路由类型Route Typre＝AS External、以及路由度量标识为第一标识＝E(0)。节点0在接收到ASBR发送的第二报文后，计算到达ASBR的第二路由度量值10、确定到达节点0的下一跳为ASBR以及根据路由度量指示E(0)确定到达节点0的路由开销为110。
若路由度量标识为第二标识，第二网络设备将第一路由度量值作为达到SRv6 Locator对应路由的路由开销。即，当路由度量标识为第二标识时，第二网络设备在确定到达SRv6 Locator对应路由的路由开销时，仅考虑域外路由度量值，即第一路由度量值。例如，图5b所示，ISIS域中的节点1配置了路由算法为：Flex-Algo(128)的Locator，并在域内泛洪；ASBR上配置在引入ISIS域的Locator路由时，路由度量标识为第二标识(E(1))，其在接收到节点1泛洪的SRv6 Locator信息后，生成OSPFv3 Locator LSA报文，并向OSPFv3域内泛洪。节点0在接收到AS External类型的LSA报文后，确定到达SRv6 Locator路由：下一跳为ASBR、路由开销为100。
可见，第一网络设备在接收到来自第一网络域的第一报文后，根据第一报文生成第二报文。其中，第一报文包括SRv6 Locator，第二报文包括SRv6 Locator以及路由度量标识，该路由度量标识用于指示计算到达SRv6 Locator对应路由的路由开销的方式。第一网络设 备向第二网络域的第二网络设备发送第二报文，该第二报文还包括从第一网络设备到达SRv6 Locator对应的路由在第一网络域内的第一路由度量值。即，第一网络设备在向第二网络域引入第一网络域的SRv6 Locator路由时，将向生成的第二报文中添加路由度量标识，以使得第二网络域中网络设备在计算到达SRv6 Locator对应路由的路由开销时，可以根据路由度量标识确定计算方式，进而根据确定的计算方式获得路由开销。
为防止形成环路，第二报文中包括路由标识，对于具有引入功能的网络设备，其在将一个网路域的Locator引入另一个网络域时，还需要通过路由标识进行校验，以根据校验结果确定是否向另一个网络域引入。
参见图6，该图为本申请实施例提供的另一种路由信息传输方法，如图6所示，该方法包括：
S601：网络设备通过第一路由协议接收用于通告SRv6 Locator路由的路由通告报文。
本实施例中，对于跨多个网络域的网络设备，其可以运行多个路由协议，以通过不同的路由协议进行路由通告。例如，网络设备为图4a中的ASBR2或ASBR3，当网络设备为ASBR2时，第一路由协议和第二路由协议均为OSPF，当网络设备为ASBR3时，该网络设备可以运行第一路由协议OSPF和第二路由协议ISIS。其中，网络设备通过第一路由协议所接收的路由通告报文包括SRv6 Locator和路由标识，该路由标识指示SRv6 Locator的来源。其中，路由标识由配置了SRv6 Locator的目标节点所在网络域的边界路由设备在接收到目标节点发送的路由通告报文后，通过配置策略确定目标节点所在的网络域对应的路由标识，进而将该路由标识添加到路由通告报文中，以向其所在的另一网络域的节点发送路由通告报文。例如，目标节点位于图4a中的ISIS域，边界路由设备为ASBR1，另一网络域为OSPF1。
S602：网络设备确定路由标识为网络设备的标识时，避免将SRv6 Locator引入到第二路由协议中。
网络设备在通过第一网络协议接收到路由通告报文后，在其向运行第二网络协议的网络域中转发该路由通过报文之前，首先确定该路由通告报文中的路由标识是否为网络设备的标识，如果是，表明该路由通告报文中的SRv6 Locator来自第二路由协议，则为防止环路形成，则不再将路由通告报文中的SRv6 Locator引入到第二路由协议中。如果否，表明该路由通告报文中的SRv6 Locator不是来自第二路由协议，则可以继续向第二路由协议中引入SRv6 Locator。
例如，图7所示，ISIS域内配置了Flex Algo 128的SRv6 Locator，配置了SRv6 Locator的节点在域内泛洪到达SRv6 Locator的路由通告报文；ASBR1在接收到路由通告报文时，根据配置策略确定ISIS域对应的路由标识Tag＝100，在向OSPF1域引入该SRv6 Locator时，打上路由标识Admin Tag＝100；ASBR2在接收到OSPF1域内节点转发的路由通告报文，且向OSPF2域引入SRv6 Locator时，该路由通告报文携带Admin Tag＝100，经检测该路由标识非ASBR2所在的OSPF2对应的路由标识，则向OSPF2中引入该SRv6 Locator；ASBR3在接收到OSPF2域内节点转发的路由通告报文，且在向ISIS域引入该SRv6 Locator 时，通过配置的引入路由策略，校验Admin Tag＝100为ISIS域对应的路由标识，则不向ISIS中引入SRv6 Locator，防止环路。
即，网络设备可以根据路由通告报文中的路由标识确定是否对所接收的路由通告报文进行转发或丢弃，从而避免形成环路。
基于上述方法实施例，本申请实施例提供了一种路由信息传输装置，下面将结合附图进行说明。
参见图8，该图为本申请实施例提供的一种路由信息传输装置结构图，如图8所示，该装置800能够实现上图2中第一网络设备的功能，或者，该装置800可以实现图1、图5a、图5b中ASBR、图4a或图7中ASBR1的功能。参见图8，该装置800可以包括接收单元801、生成单元802和发送单元803。这些单元可以执行上述方法示例中第一网络设备的相应功能。
接收单元801，用于支持装置800执行图2中S203中接收第一报文；生成单元802，用于支持装置800执行图2中S203中生成第二报文；发送单元803，用于支持装置800执行图2中的S204；；和/或本文所描述的技术中第一网络设备执行的其它过程。具体执行过程请参考上述图2所示实施例中相应步骤的详细描述，这里不再一一赘述。
可选地，所述装置800还可以包括：计算单元；
所述计算单元，用于在接收到第一报文之后，计算得到第一路由度量值。
可选地，所述装置800还可以包括：确定单元；
所述确定单元，用于在接收到第一报文后，根据第一网络域以及配置策略确定与第一网络域对应的路由标识。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。本申请实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。例如，上述实施例中，处理单元和发送单元可以是同一个单元，也可以是不同的单元。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
参见图9，该图为本申请实施例提供的另一种路由信息传输装置结构图，如图9所示，该装置900可以实现图2中第二网络设备的功能，或者该装置900可以实现图1、图5a、图5b中节点0、图4a或图7中ASBR2的功能。参见图9，该装置900可以包括接收单元901、确定单元902。这些单元可以执行上述方法示例中第二网络设备的相应功能。
接收单元901，用于支持装置900执行图2中S205中的接收第二报文；确定单元902，用于支持装置900执行图2中S205中的根据第二报文中的路由度量标识确定路由开销；和/或本文所描述的技术中第二网络设备执行的其它过程。具体执行过程请参考上述图2所示实施例中相应步骤的详细描述，这里不再一一赘述。
可选地，所述确定单元902，还用于确定从第二网络设备到达SRv6 Locator对应的路由在第二网络域内的第二路由度量值。
可选地，所述确定单元902，具体用于若所述路由度量标识为第一标识，所述第三网 络设备将第一路由度量值和第二路由度量值的和值作为从所述第二网络设备到达所述SRv6 Locator对应路由的路由开销。
可选地，所述确定单元902，具体用于若所述路由度量标识为第二标识，所述第二网络设备将所述第一路由度量值作为从所述第二网络设备到达所述SRv6 Locator对应路由的路由开销。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。本申请实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。例如，上述实施例中，处理单元和发送单元可以是同一个单元，也可以是不同的单元。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
参见图10，该图为本申请实施例提供的又一种路由信息传输装置结构图，如图10所示，该装置1000能够实现图6中网络设备的功能，或者该装置1000可以实现图4a或图7中ASBR2、ASBR3的功能。参见图10，该装置1000可以包括接收单元1001、处理单元1002。这些单元可以执行上述图6所述方法示例中网络设备的相应功能。
接收单元1001，用于支持装置1000执行图6中S601；处理单元1002，用于支持装置1000执行图6中S602；和/或本文所描述的技术中网络设备执行的其它过程。例如，接收单元1001，用于执行上述方法实施例中网络设备通过第一路由协议接收用于通告SRv6 Locator路由的路由通告报文；处理单元1002，用于执行上述方法实施例中网络设备执行的各种处理操作。举例来说，处理单元1002，用于确定所述路由标识为所述网络设备的标识时，避免将所述SRv6 Locator引入到第二路由协议中。具体执行过程请参考上述图6所示实施例中相应步骤的详细描述，这里不再一一赘述。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。本申请实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。例如，上述实施例中，处理单元和发送单元可以是同一个单元，也可以是不同的单元。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
图11为本申请实施例提供的一种网络设备的结构示意图，该网络设备例如可以是上述方法实施例中的第一网络设备、第二网络设备，或者也可以是图8所示实施例中装置800、图9所示实施例中装置900或图10所示实施例中装置1000的设备实现。
该网络设备1100包括：处理器1110、通信接口1120和存储器1130。其中通信设备1100中的处理器1110的数量可以一个或多个，图11中以一个处理器为例。本申请实施例中，处理器1110、通信接口1120和存储器1130可通过总线系统或其它方式连接，其中，图11中以通过总线系统1140连接为例。
处理器1110可以是CPU、NP、或者CPU和NP的组合。处理器1110还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列 (field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
存储器1130可以包括易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器1130也可以包括非易失性存储器(non-volatile memory)，例如快闪存储器(flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；存储器1130还可以包括上述种类的存储器的组合。存储器1130例如可以存储前文提及的分段路由SR策略等。
可选地，存储器1130存储有操作系统和程序、可执行模块或者数据结构，或者它们的子集，或者它们的扩展集，其中，程序可包括各种操作指令，用于实现各种操作。操作系统可包括各种系统程序，用于实现各种基础业务以及处理基于硬件的任务。处理器1110可以读取存储器1130中的程序，实现本申请实施例提供的段路由策略处理方法。
其中，存储器1130可以为通信设备1100中的存储器件，也可以为独立于通信设备1100的存储装置。
总线系统1140可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。总线系统1140可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
图12是本申请实施例提供的一种网络设备1200的结构示意图，该网络设备例如可以是上述方法实施例中的第一网络设备、第二网络设备，或者也可以是图8所示实施例中装置800、图9所示实施例中装置900或图10所示实施例中装置1000的设备实现。
网络设备1200包括：主控板1210和接口板1230。
主控板1210也称为主处理单元(main processing unit，MPU)或路由处理卡(route processor card)，主控板1210对网络设备1200中各个组件的控制和管理，包括路由计算、设备管理、设备维护、协议处理功能。主控板1210包括：中央处理器1211和存储器1212。
接口板1230也称为线路接口单元卡(line processing unit，LPU)、线卡(line card)或业务板。接口板1230用于提供各种业务接口并实现数据包的转发。业务接口包括而不限于以太网接口、POS(Packet over SONET/SDH)接口等，以太网接口例如是灵活以太网业务接口(Flexible Ethernet Clients，FlexE Clients)。接口板1230包括：中央处理器1231、网络处理器1232、转发表项存储器1234和物理接口卡(physical interface card，PIC)1233。
接口板1230上的中央处理器1231用于对接口板1230进行控制管理并与主控板1210上的中央处理器1211进行通信。
网络处理器1232用于实现报文的转发处理。网络处理器1232的形态可以是转发芯片。具体而言，上行报文的处理包括：报文入接口的处理，转发表查找；下行报文的处理包括转发表查找等等。
物理接口卡1233用于实现物理层的对接功能，原始的流量由此进入接口板1230，以及处理后的报文从该物理接口卡1233发出。物理接口卡1233包括至少一个物理接口，物 理接口也称物理口。物理接口卡1233也称为子卡，可安装在接口板1230上，负责将光电信号转换为报文并对报文进行合法性检查后转发给网络处理器1232处理。在一些实施例中，接口板1203的中央处理器1231也可执行网络处理器1232的功能，比如基于通用CPU实现软件转发，从而物理接口卡1233中不需要网络处理器1232。
可选地，网络设备1200包括多个接口板，例如网络设备1200还包括接口板1240，接口板1240包括：中央处理器1241、网络处理器1242、转发表项存储器1244和物理接口卡1243。
可选地，网络设备1200还包括交换网板1220。交换网板1220也可以称为交换网板单元(switch fabric unit，SFU)。在网络设备有多个接口板1230的情况下，交换网板1220用于完成各接口板之间的数据交换。例如，接口板1230和接口板1240之间可以通过交换网板1220通信。
主控板1210和接口板1230耦合。例如。主控板1210、接口板1230和接口板1240，以及交换网板1220之间通过系统总线与系统背板相连实现互通。在一种可能的实现方式中，主控板1210和接口板1230之间建立进程间通信协议(inter-process communication，IPC)通道，主控板1210和接口板1230之间通过IPC通道进行通信。
在逻辑上，网络设备1200包括控制面和转发面，控制面包括主控板1210和中央处理器1231，转发面包括执行转发的各个组件，比如转发表项存储器1234、物理接口卡1233和网络处理器1232。控制面执行路由器、生成转发表、处理信令和协议报文、配置与维护设备的状态等功能，控制面将生成的转发表下发给转发面，在转发面，网络处理器1232基于控制面下发的转发表对物理接口卡1233收到的报文查表转发。控制面下发的转发表可以保存在转发表项存储器1234中。在一些实施例中，控制面和转发面可以完全分离，不在同一设备上。
应理解，本申请实施例中接口板1240上的操作与接口板1230的操作一致，为了简洁，不再赘述。应理解，本实施例的网络设备1200可对应于上述各个方法实施例中的第一网络设备，该网络设备1200中的主控板1210、接口板1230和/或接口板1240可以实现上述各个方法实施例中的各种步骤，为了简洁，在此不再赘述。
应理解，主控板可能有一块或多块，有多块的时候可以包括主用主控板和备用主控板。接口板可能有一块或多块，网络设备的数据处理能力越强，提供的接口板越多。接口板上的物理接口卡也可以有一块或多块。交换网板可能没有，也可能有一块或多块，有多块的时候可以共同实现负荷分担冗余备份。在集中式转发架构下，网络设备可以不需要交换网板，接口板承担整个系统的业务数据的处理功能。在分布式转发架构下，网络设备可以有至少一块交换网板，通过交换网板实现多块接口板之间的数据交换，提供大容量的数据交换和处理能力。所以，分布式架构的网络设备的数据接入和处理能力要大于集中式架构的设备。可选地，网络设备的形态也可以是只有一块板卡，即没有交换网板，接口板和主控板的功能集成在该一块板卡上，此时接口板上的中央处理器和主控板上的中央处理器在该一块板卡上可以合并为一个中央处理器，执行两者叠加后的功能，这种形态设备的数据交换和处理能力较低(例如，低端交换机或路由器等网络设备)。具体采用哪种架构，取决于具 体的组网部署场景。
在一些可能的实施例中，上述网络设备可以实现为虚拟化设备。例如，虚拟化设备可以是运行有用于发送报文功能的程序的虚拟机(virtual machine，VM)，虚拟机部署在硬件设备上(例如，物理服务器)。虚拟机指通过软件模拟的具有完整硬件系统功能的、运行在一个完全隔离环境中的完整计算机系统。可以将虚拟机配置为网络设备。例如，可以基于通用的物理服务器结合网络功能虚拟化(network functions virtualization，NFV)技术来实现网络设备。网络设备为虚拟主机、虚拟路由器或虚拟交换机。本领域技术人员通过阅读本申请即可结合NFV技术在通用物理服务器上虚拟出具有上述功能的网络设备，此处不再赘述。
应理解，上述各种产品形态的网络设备，具有上述方法实施例中第一网络设备的任意功能，此处不再赘述。
本申请实施例还提供了一种芯片，包括处理器和接口电路，接口电路，用于接收指令并传输至处理器；处理器，例如可以是图8示出的装置800的一种具体实现形式，可以用于执行上述方法。其中，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得该芯片系统实现上述任一方法实施例中的方法。
可选地，该芯片系统中的处理器可以为一个或多个。该处理器可以通过硬件实现也可以通过软件实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等。当通过软件实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。
可选地，该芯片系统中的存储器也可以为一个或多个。该存储器可以与处理器集成在一起，也可以和处理器分离设置，本申请并不限定。示例性的，存储器可以是非瞬时性处理器，例如只读存储器ROM，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请对存储器的类型，以及存储器与处理器的设置方式不作具体限定。
示例性的，该芯片系统可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application-specific integrated circuit，ASIC)，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
本申请实施例还提供了一种计算机可读存储介质，包括指令或计算机程序，当其在计算机上运行时，使得计算机执行以上实施例提供的路由信息传输方法。
本申请实施例还提供了一种包含指令或计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行以上实施例提供的路由信息传输方法。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过 程、方法、产品或设备固有的其它步骤或单元。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑业务划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各业务单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件业务单元的形式实现。
集成的单元如果以软件业务单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的业务可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些业务存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上仅为本申请的具体实施方式而已。
以上，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (50)

  1. 一种路由信息传输方法，其特征在于，所述方法包括：
    第一网络设备接收来自第一网络域的第一报文，所述第一报文包括基于第6版因特网协议的段路由SRv6位置标识Locator；
    所述第一网络设备根据所述第一报文生成第二报文，所述第二报文包括所述SRv6Locator以及路由度量标识，所述路由度量标识用于指示计算到达所述SRv6 Locator对应路由的路由开销的方式；
    所述第一网络设备向第二网络域的第二网络设备发送所述第二报文，所述第二报文还包括从所述第一网络设备到达所述SRv6 Locator对应的路由在所述第一网络域内的第一路由度量值。
  2. 根据权利要求1所述的方法，其特征在于，所述第二报文为第3版开放式最短路径优先链路状态通告OSPFv3 LSA报文。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一网络设备在接收到所述第一报文之后，所述方法还包括：
    所述第一网络设备计算得到所述第一路由度量值。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述第二报文包括基于第6版因特网协议的段路由位置标识长度类型值SRv6 Locator TLV，所述SRv6 Locator TLV包括所述路由度量标识。
  5. 根据权利要求4所述的方法，其特征在于，所述SRv6 Locator TLV包括标志位Flags，所述Flags包括所述路由度量标识。
  6. 根据权利要求5所述的方法，其特征在于，所述Flags包括扩展位，所述扩展位携带所述路由度量标识。
  7. 根据权利要求4所述的方法，其特征在于，所述SRv6 Locator TLV包括第一子类型长度值TLV，所述第一子TLV包括所述路由度量标识。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，所述第二报文还包括路由标识，所述路由标识指示所述SRv6 Locator的来源，所述路由标识用于防止环路。
  9. 根据权利要求8所述的方法，其特征在于，所述第一网络设备在接收到所述第一报文后，所述方法还包括：
    所述第一网络设备根据所述第一网络域以及配置策略确定与所述第一网络域对应的路由标识。
  10. 根据权利要求8或9所述的方法，其特征在于，所述第二报文包括SRv6 Locator TLV，所述SRv6 Locator TLV包括所述路由标识。
  11. 根据权利要求10所述的方法，其特征在于，所述SRv6 Locator TLV包括第二子TLV，所述第二子TLV包括所述路由标识。
  12. 根据权利要求1-11任一项所述的方法，其特征在，所述第一网络域为中间系统到中间系统ISIS，所述第二网络域为开放式最短路径优先OSPF。
  13. 一种路由信息传输方法，其特征在于，所述方法包括：
    第二网络设备接收来自第一网络设备发送的报文，所述报文包括来自第一网络域的SRv6位置标识Locator、路由度量标识和第一路由度量值，所述第一路由度量值为从所述第一网络设备到达所述SRv6 Locator对应的路由在所述第一网络域内的路由度量值，所述第二网络设备位于第二网络域；
    所述第二网络设备根据所述路由度量标识确定达到所述SRv6Locator对应路由的路由开销。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备确定从所述第二网络设备到达所述SRv6 Locator对应的路由在所述第二网络域内的第二路由度量值。
  15. 根据权利要求14所述的方法，其特征在于，所述第二网络设备根据所述路由度量标识确定达到所述SRv6 Locator的路由开销包括：
    若所述路由度量标识为第一标识，所述第二网络设备将第一路由度量值和第二路由度量值的和值作为从所述第二网络设备到达所述SRv6 Locator对应路由的路由开销。
  16. 根据权利要求13-15任一所述的方法，其特征在于，所述第二网络设备根据所述路由度量标识确定达到所述SRv6 Locator的路由开销包括：
    若所述路由度量标识为第二标识，所述第二网络设备将所述第一路由度量值作为从所述第二网络设备到达所述SRv6 Locator对应路由的路由开销。
  17. 根据权利要求13-16任一项所述的方法，其特征在于，所述报文包括SRv6 Locator TLV，所述SRv6 Locator TLV包括所述路由度量标识。
  18. 根据权利要求17所述的方法，其特征在于，所述SRv6 Locator TLV包括标志位Flags，所述Flags包括所述路由度量标识。
  19. 根据权利要求18所述的方法，其特征在于，所述Flags包括扩展位，所述扩展位携带所述路由度量标识。
  20. 根据权利要求17所述的方法，其特征在于，所述SRv6 Locator TLV包括第一子类型长度值TLV，所述第一子TLV包括所述路由度量标识。
  21. 一种路由信息传输方法，其特征在于，所述方法包括：
    网络设备通过第一路由协议接收用于通告SRv6位置标识Locator路由的路由通告报文，所述路由通告报文包含所述SRv6 Locator和路由标识，所述路由标识指示所述SRv6 Locator的来源；
    所述网络设备确定所述路由标识为所述网络设备的标识时，避免将所述SRv6 Locator引入到第二路由协议中。
  22. 根据权利要求21所述的方法，其特征在于，所述路由通告报文包括SRv6 Locator TLV，所述SRv6 Locator TLV包括所述路由标识。
  23. 根据权利要求22所述的方法，其特征在于，所述SRv6 Locator TLV包括第二子TLV，所述第二子TLV包括所述路由标识。
  24. 一种路由信息传输装置，其特征在于，所述装置应用于第一网络设备，包括：
    接收单元，用于接收来自第一网络域的第一报文，所述第一报文包括基于第6版因特 网协议的段路由SRv6位置标识Locator；
    生成单元，用于根据所述第一报文生成第二报文，所述第二报文包括所述SRv6 Locator以及路由度量标识，所述路由度量标识用于指示计算到达所述SRv6 Locator对应路由的路由开销的方式；
    发送单元，用于向第二网络域的第二网络设备发送所述第二报文，所述第二报文还包括从所述第一网络设备到达所述SRv6 Locator对应的路由在所述第一网络域内的第一路由度量值。
  25. 根据权利要求24所述的装置，其特征在于，所述第二报文为第3版开放式最短路径优先链路状态通告OSPFv3 LSA报文。
  26. 根据权利要求24或25所述的装置，其特征在于，所述装置还包括：计算单元；
    所述计算单元，用于在接收到所述第一报文之后，计算得到所述第一路由度量值。
  27. 根据权利要求24-26任一项所述的装置，其特征在于，所述第二报文包括基于第6版因特网协议的段路由位置标识长度类型值SRv6 Locator TLV，所述SRv6 Locator TLV包括所述路由度量标识。
  28. 根据权利要求27所述的装置，其特征在于，所述SRv6 Locator TLV包括标志位Flags，所述Flags包括所述路由度量标识。
  29. 根据权利要求28所述的装置，其特征在于，所述Flags包括扩展位，所述扩展位携带所述路由度量标识。
  30. 据权利要求27所述的装置，其特征在于，所述SRv6 Locator TLV包括第一子类型长度值TLV，所述第一子TLV包括所述路由度量标识。
  31. 根据权利要求24-30任一项所述的装置，其特征在于，所述第二报文还包括路由标识，所述路由标识指示所述SRv6 Locator的来源，所述路由标识用于防止环路。
  32. 根据权利要求31所述的装置，其特征在于，所述装置还包括：确定单元；
    所述确定单元，用于在接收到所述第一报文后，根据所述第一网络域以及配置策略确定与所述第一网络域对应的路由标识。
  33. 根据权利要求31或32所述的装置，其特征在于，所述第二报文包括SRv6 Locator TLV，所述SRv6 Locator TLV包括所述路由标识。
  34. 根据权利要求33所述的装置，其特征在于，所述SRv6 Locator TLV包括第二子TLV，所述第二子TLV包括所述路由标识。
  35. 根据权利要求24-34任一项所述的装置，其特征在，所述第一网络域为中间系统到中间系统ISIS，所述第二网络域为开放式最短路径优先OSPF。
  36. 一种路由信息传输装置，其特征在于，所述装置应用于第二网络设备，包括：
    接收单元，用于接收来自第一网络设备发送的报文，所述报文包括来自第一网络域的SRv6位置标识Locator、路由度量标识和第一路由度量值，所述第一路由度量值为从所述第一网络设备到达所述SRv6 Locator对应的路由在所述第一网络域内的路由度量值，所述第二网络设备位于第二网络域；
    确定单元，用于根据所述路由度量标识确定达到所述SRv6Locator对应路由的路由开 销。
  37. 根据权利要求36所述的装置，其特征在于，所述确定单元，还用于确定从第二网络设备到达所述SRv6 Locator对应的路由在所述第二网络域内的第二路由度量值。
  38. 根据权利要求37所述的装置，其特征在于，所述确定单元，具体用于若所述路由度量标识为第一标识，将第一路由度量值和第二路由度量值的和值作为从所述第二网络设备到达所述SRv6 Locator对应路由的路由开销。
  39. 根据权利要求36-38任一所述的装置，其特征在于，所述确定单元，具体用于若所述路由度量标识为第二标识，将所述第一路由度量值作为从所述第二网络设备到达所述SRv6 Locator对应路由的路由开销。
  40. 根据权利要求36-39任一项所述的装置，其特征在于，所述报文包括SRv6 Locator TLV，所述SRv6 Locator TLV包括所述路由度量标识。
  41. 根据权利要求40所述的装置，其特征在于，所述SRv6 Locator TLV包括标志位Flags，所述Flags包括所述路由度量标识。
  42. 根据权利要求41所述的装置，其特征在于，所述Flags包括扩展位，所述扩展位携带所述路由度量标识。
  43. 根据权利要求40所述的方法，其特征在于，所述SRv6 Locator TLV包括第一子类型长度值TLV，所述第一子TLV包括所述路由度量标识。
  44. 一种路由信息传输装置，其特征在于，所述装置包括：
    接收单元，用于通过第一路由协议接收用于通告SRv6位置标识Locator路由的路由通告报文，所述路由通告报文包含所述SRv6 Locator和路由标识，所述路由标识指示所述SRv6Locator的来源；
    处理单元，用于确定所述路由标识为所述网络设备的标识时，避免将所述SRv6 Locator引入到第二路由协议中。
  45. 根据权利要求44所述的装置，其特征在于，所述路由通告报文包括SRv6 Locator TLV，所述SRv6 Locator TLV包括所述路由标识。
  46. 根据权利要求45所述的装置，其特征在于，所述SRv6 Locator TLV包括第二子TLV，所述第二子TLV包括所述路由标识。
  47. 一种通信设备，其特征在于，所述设备包括：处理器和存储器；
    所述存储器，用于存储指令或计算机程序；
    所述处理器，用于执行所述存储器中的所述指令或计算机程序，以使得所述通信设备执行权利要求1-12任意一项所述的方法，或者执行权利要求13-20任一项所述的方法，或者执行权利要求21-23任一项所述的方法。
  48. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行以上权利要求1-12任意一项所述的方法，或者执行权利要求13-20任一项所述的方法，或者执行权利要求21-23任一项所述的方法。
  49. 一种计算机程序产品，其特征在于，所述计算机程序产品包含程序，当所述程序在处理器上运行时，使得计算机或网络设备执行以上权利要求1-12任意一项所述的方法，或 者执行权利要求13-20任一项所述的方法，或者执行权利要求21-23任一项所述的方法。
  50. 一种芯片，其特征在于，包括：接口电路和处理器，所述接口电路和所述处理器相连接，所述处理器用于使得所述芯片执行以上权利要求1-12任意一项所述的方法，或者执行权利要求13-20任一项所述的方法，或者执行权利要求21-23任一项所述的方法。
PCT/CN2023/103082 2022-08-09 2023-06-28 一种路由信息传输方法及装置 WO2024032187A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210953219.8 2022-08-09
CN202210953219.8A CN117640484A (zh) 2022-08-09 2022-08-09 一种路由信息传输方法及装置

Publications (1)

Publication Number Publication Date
WO2024032187A1 true WO2024032187A1 (zh) 2024-02-15

Family

ID=89850622

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/103082 WO2024032187A1 (zh) 2022-08-09 2023-06-28 一种路由信息传输方法及装置

Country Status (2)

Country Link
CN (1) CN117640484A (zh)
WO (1) WO2024032187A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190058657A1 (en) * 2016-02-15 2019-02-21 Telefonaktiebolaget Lm Ericsson (Publ) Ospf extensions for flexible path stitchng and selection for traffic transiting segment routing and mpls networks
CN112511428A (zh) * 2020-03-10 2021-03-16 中兴通讯股份有限公司 报文封装方法、报文转发方法、通告方法、电子设备、和存储介质
CN113300951A (zh) * 2020-02-21 2021-08-24 华为技术有限公司 一种发送报文的方法、设备及系统
CN113411258A (zh) * 2021-06-07 2021-09-17 新华三技术有限公司 报文处理方法及装置
CN114866470A (zh) * 2021-02-03 2022-08-05 华为技术有限公司 发送报文的方法、装置、系统及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190058657A1 (en) * 2016-02-15 2019-02-21 Telefonaktiebolaget Lm Ericsson (Publ) Ospf extensions for flexible path stitchng and selection for traffic transiting segment routing and mpls networks
CN113300951A (zh) * 2020-02-21 2021-08-24 华为技术有限公司 一种发送报文的方法、设备及系统
CN112511428A (zh) * 2020-03-10 2021-03-16 中兴通讯股份有限公司 报文封装方法、报文转发方法、通告方法、电子设备、和存储介质
CN114866470A (zh) * 2021-02-03 2022-08-05 华为技术有限公司 发送报文的方法、装置、系统及存储介质
CN113411258A (zh) * 2021-06-07 2021-09-17 新华三技术有限公司 报文处理方法及装置

Also Published As

Publication number Publication date
CN117640484A (zh) 2024-03-01

Similar Documents

Publication Publication Date Title
CN110784411B (zh) 建立bier转发表项的方法、装置和系统
US10333836B2 (en) Convergence for EVPN multi-homed networks
US9860150B2 (en) Fast convergence of EVPN networks for multi homing topologies
US9781032B1 (en) MPLS label usage in ethernet virtual private networks
US9832097B2 (en) Method and apparatus for MPLS label allocation for a BGP MAC-VPN
EP3148127A1 (en) Egress protection for bum traffic with link failures in evpn
US9019814B1 (en) Fast failover in multi-homed ethernet virtual private networks
RU2704714C1 (ru) Технологии для предоставления максимальной глубины идентификатора сегмента узла и/или линии связи, использующие ospf
US9509609B2 (en) Forwarding packets and PE devices in VPLS
WO2020135395A1 (zh) 一种跨内部网关协议的前缀标识通告方法和装置
EP3799354B1 (en) Synchronizing multicast router capability towards ethernet virtual private network (evpn) multi homed protocol independent multicast (pim) device
CN112702266A (zh) 生成标签转发表的方法、报文发送方法、装置及设备
WO2021164249A1 (zh) 一种发送报文的方法、设备及系统
WO2018103099A1 (zh) 发送和接收消息的方法、设备和系统
CN112868214B (zh) 分组内的协调负载转移oam记录
CN112202669A (zh) 使用分段路由的弹性多协议标签交换（mpls）环
EP3820089A1 (en) Controller provided protection paths
AU2020371074A1 (en) Communication method and device
US20230412503A1 (en) Determining unicast addresses of gateway network devices associated with an anycast address in vxlan-evpn dci environments
CN108768845B (zh) 一种多归属主机路由同步方法及装置
WO2024032187A1 (zh) 一种路由信息传输方法及装置
EP3151486A1 (en) Fast convergence of evpn networks for multi homing topologies
WO2023016550A1 (zh) 一种路由发送方法及设备
WO2022001274A1 (zh) 一种路由生成方法、路由处理方法及装置
WO2022133646A1 (zh) 一种路由传输方法及装置

Legal Events

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

Ref document number: 23851414

Country of ref document: EP

Kind code of ref document: A1