WO2022088967A1 - 确定下一跳的方法及装置 - Google Patents

确定下一跳的方法及装置 Download PDF

Info

Publication number
WO2022088967A1
WO2022088967A1 PCT/CN2021/116119 CN2021116119W WO2022088967A1 WO 2022088967 A1 WO2022088967 A1 WO 2022088967A1 CN 2021116119 W CN2021116119 W CN 2021116119W WO 2022088967 A1 WO2022088967 A1 WO 2022088967A1
Authority
WO
WIPO (PCT)
Prior art keywords
bfr
attribute
next hop
identifier
prefix
Prior art date
Application number
PCT/CN2021/116119
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
Priority claimed from CN202110184092.3A external-priority patent/CN114531391A/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2023526335A priority Critical patent/JP2023547485A/ja
Priority to EP21884698.8A priority patent/EP4224817A4/en
Priority to KR1020237017030A priority patent/KR20230088494A/ko
Publication of WO2022088967A1 publication Critical patent/WO2022088967A1/zh
Priority to US18/309,532 priority patent/US20230269165A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • 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/34—Source routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/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/16—Multipoint routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/72—Routing based on the source address

Definitions

  • the present invention relates to the field of communication technologies, and in particular, to a method and apparatus for determining a next hop.
  • the bit forwarding ingress router (BFIR) or the first intermediate bit forwarding router (transit BFR) can receive other data in the BIER domain.
  • BIER information flooded by a BFR (such as a second intermediate BFR or a bit forwarding egress router (BFER)) through an internal gateway protocol (IGP).
  • the BIER information includes: the BFR prefix (prefix) of the BFR sending the BIER information, the bit forwarding router identifier (bit forwarding router identifier, BFR-id) of one or more BFERs, and its BFR prefix.
  • the BFR prefix indicates the address of the BFR in the BIER domain.
  • the BFIR or the first intermediate BFR may obtain a bit index forwarding table (BIFT) according to the BIER information flooded through the IGP.
  • the BIFT entry includes the forwarding bitmask (F-BM) and the BFR neighbor (BFR neighbor, BFR-NBR) as the next hop.
  • the bits set to 1 in the bit string included in the F-BM correspond to the BFER in the received BIER information.
  • the address in the BFR-NBR is the BFR prefix of the BFR included in the BIER information that sends the BIER information.
  • the published BIER information includes the same BFER parameters, such as the BFR-id of the BFER and the BIER prefix of the BFER, and received from the second BFR and the third BFR
  • the BFR of the BIER information published by the BFR such as BFIR or the first BFR, can select the BIER information published by a BFR according to the longest matching strategy or the equal-cost multi-path routing (ECMP) strategy. The method of next hop is not flexible enough.
  • the embodiments of the present application provide a method and apparatus for determining a next hop, which can improve flexibility.
  • a first aspect provides a method for determining a next hop, wherein the method is applied to forwarding and routing BIER domains based on bit indices, including:
  • the third device acquires first BIER information of the first device, attributes of the first device, second BIER information of the second device, and attributes of the second device, where the first BIER information includes edges in the subdomain a bit forwarding router identifier BFR-id of a bit forwarding router BFR, and the second BIER information includes the BFR-id of the edge BFR in the subdomain;
  • the third device determines, according to the first BIER information, the second BIER information, the attribute of the first device, and the attribute of the second device, to reach the lower part of the edge BFR in the subdomain. One hop.
  • the third device can flexibly select the next hop to reach the edge BFR of the subdomain based on the attributes of the first device and the attributes of the second device, and is not limited to the longest matching strategy or the ECMP strategy for selection, which improves the Determines the flexibility of the next hop.
  • the attribute of the first device and the attribute of the second device include a first identifier
  • the first identifier is used to identify the BFR prefix of anycast
  • the method further includes: the first identifier
  • the third device performs the determination to reach the The next hop of the edge BFR.
  • the attribute of the first device or the attribute of the second device includes a first identifier
  • the first identifier is used to identify the BFR prefix of anycast
  • the third device uses the first identifier to identify the BFR prefix of anycast.
  • One BIER information, the second BIER information, the attribute of the first device and the attribute of the second device, and determining the next hop to the edge BFR in the subdomain includes: the third device When the first BIER information and the second BIER information are the same, a device whose attribute includes the first identifier is determined as the next hop.
  • the method further includes: the first BFR information and the second BIER information of the third device are the same, and the attributes of the first device and the attributes of the second device are the same.
  • the first identifiers are included, an alarm is output, and the first identifier is used to identify the BFR prefix of anycast.
  • the attribute of the first device further includes the node identifier of the first device
  • the attribute of the second device includes the node identifier of the second device
  • the third device the first BIER information, the second BIER information, the attributes of the first device and the attributes of the second device, and determining the next hop to the edge BFR in the subdomain includes: the first When the first BIER information is the same as the second BIER information, the third device determines the first device and the second device based on the first policy, the node identifier of the first device, and the node identifier of the second device One of the two devices is used as the next hop, and the first strategy includes using a device with a larger node identification as the next hop or a device with a smaller node identification as the next hop.
  • the attribute of the first device further includes a second identifier
  • the attribute of the second device further includes a third identifier
  • the second identifier is used to identify the priority of the first device
  • the third identifier is used to identify the priority of the second device
  • the attribute of the first device includes the BFR prefix of the first device
  • the attribute of the second device includes the BFR prefix of the second device
  • the BFR prefix of the first device Different from the BFR prefix of the second device, the third device determines, according to the first BIER information, the second BIER information, the attributes of the first device and the attributes of the second device, to reach the destination.
  • the next hop of the edge BFR in the subdomain includes: the third device, when the first BIER information and the second BIER information are the same, according to the third policy, the overhead cost value of the first link and the cost value of the second link, determine one of the first device and the second device as the next hop, and the third strategy includes using the device at the opposite end of the link with a smaller cost value as the next hop hop or use the device on the opposite end of the link with a larger cost value as the next hop, the first link is the link from the third device to the first device, and the second link is the first link The link of the three devices to the second device.
  • the attribute of the first device includes the BFR prefix of the first device
  • the attribute of the second device includes the BFR prefix of the second device
  • the BFR prefix of the first device Different from the BFR prefix of the second device, the third device determines, according to the first BIER information, the second BIER information, the attributes of the first device and the attributes of the second device, to reach the destination.
  • the next hop of the edge BFR in the subdomain includes: when the first BIER information and the second BIER information are the same by the third device, according to the fourth policy, the BFR prefix of the first device and the BFR prefix of the second device, determine one of the first device and the second device as the next hop, and the fourth strategy includes using the device with a smaller BFR prefix as the next hop or using the device with a smaller BFR prefix as the next hop.
  • a device with a larger BFR prefix is used as the next hop.
  • the attribute of the first device includes the BFR prefix of the first device and the node identifier of the first device
  • the attribute of the second device includes the BFR prefix of the second device and the node identifier of the second device
  • the BFR prefix of the first device is different from the BFR prefix of the second device
  • the third device is based on the first BIER information, the second BIER information
  • the The attribute of the first device and the attribute of the second device, and determining the next hop to the edge BFR in the subdomain includes: the third device in the first BIER information and the second When the BIER information is the same, according to the first policy, the node identifier of the first device and the node identifier of the second node, determine one of the first device and the second device as the next hop, and the first policy Including taking the device with the larger node identification as the next hop or taking the device with the smaller node identification as the next hop.
  • the attribute of the first device includes a BFR prefix and a second identifier of the first device
  • the attribute of the second device includes a BFR prefix and a third identifier of the second device
  • the second identifier is used to identify the priority of the first device
  • the third identifier is used to identify the priority of the second device
  • the BFR prefix of the first device is the same as the BFR of the second device.
  • the next hop of the BFR includes: when the first BIER information and the second BIER information are the same, the third device determines the first device according to the second policy, the second identifier and the third identifier and one of the second devices is used as the next hop, and the second strategy includes using a device with a higher priority as the next hop or a device with a lower priority as the next hop.
  • a second aspect provides an apparatus for determining a next hop, the apparatus comprising a unit for implementing the functions of the steps included in the first aspect or any possible design of the first aspect.
  • a system comprising the apparatus for determining the next hop provided by the second aspect or any possible design of the second aspect.
  • a chip in a fourth aspect, includes a memory and a processor, the memory is used to store computer instructions, and the processor is used to call and run the computer instructions from the memory, so as to execute the above-mentioned first The method for determining the next hop provided by the aspect or any possible implementation manner of the first aspect.
  • a fifth aspect provides a computer program product, the computer program product comprising one or more computer program instructions, when the computer program instructions are loaded and executed by a computer, cause the computer to perform the first aspect or the first The method for determining the next hop provided by any possible implementation manner of the aspect.
  • a computer-readable storage medium is provided, where the computer-readable storage medium is used to store instructions, and the instructions include the determination provided by the first aspect or any possible implementation manner of the first aspect.
  • the next set of methods are designed to program.
  • FIG. 1 is a schematic diagram of a network scenario.
  • FIG. 2 is a schematic flowchart of a method for determining a next hop according to Embodiment 1 of the present application.
  • FIG. 3 is a schematic flowchart of a method for determining a next hop according to Embodiment 2 of the present application.
  • FIG. 4 is a message format provided by Embodiment 3 of the present application.
  • FIG. 5 is a message format provided by Embodiment 4 of the present application.
  • FIG. 6 is another message format provided by Embodiment 4 of the present application.
  • FIG. 7 is a message format provided by Embodiment 5 of the present application.
  • FIG. 8 is a schematic structural diagram of an apparatus for determining a next hop according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of another apparatus for determining a next hop provided by an embodiment of the present application.
  • FIG. 1 is a schematic diagram of a network scenario.
  • R1, R2, R3, R4, R5, R11, R12, R13, R21, R22, and R23 represent BFRs in the BIER domain.
  • R1, R2, R3, R4 and R5 are in the same IGP domain, and this area may be called area A1.
  • the value of the BFR-id configured on R1 is 1.
  • the value of the BFR-id configured for R2 is 2.
  • the value of the BFR-id configured on R3 is 3.
  • the value of the BFR-id configured for R4 is 4.
  • the value of the BFR-id configured on R5 is 5.
  • R3, R4 and R5 are edge BFRs.
  • R1 and R2 can act as area border routers (ABRs). When R1 and R2 are not used as BFERs, R1 and R2 do not need to configure BFR-id or the configured BFR-id is invalid.
  • R11, R12, and R13 are in the same IGP domain, which may be referred to as area A10.
  • R11, R12, and R13 are all edge BFRs, such as BFER.
  • the value of the BFR-id assigned to R11 is 11.
  • the value of the BFR-id configured for R12 is 12.
  • the value of the BFR-id configured for R13 is 13.
  • R21, R22 and R23 are in the same IGP domain, which may be referred to as area A20.
  • R21, R22, and R23 are all edge BFRs, such as BFER.
  • the value of the BFR-id configured for R21 is 21.
  • the value of the BFR-id configured for R22 is 22.
  • the value of the BFR-id configured for R23 is 23.
  • R1 and R2 will flood the BIER information of R11, R12, R13, R21, R22, and R23 to BFRs in the A1 domain, such as R3, R4, and R5.
  • R1 and R2 also flood the BIER information of R3, R4, and R5 to BFRs in the A10 domain, such as R11, R12, and R13, and BFRs in the A20 domain, such as R21, R22, and R23.
  • the method of releasing the obtained BIER information to the BFR in the A1 domain by R1 and R2 is the same as the method of releasing the obtained BIER information to the BFR in the A10 domain and the BFR in the A20 domain.
  • the method of BIER information will be described as an example.
  • R1 and R2 can directly or indirectly obtain the BFR-id as the edge BFR from the BFR of the area A10 and the BFR of the area A20, such as the values of 11, 12, 13, 21, 22 and 23.
  • BFR-id The BIER information issued by R1 to the area A1 includes: BFR-ids with values of 11, 12, 13, 21, 22 and 23.
  • the BIER information issued by R2 to the area A1 includes: BFR-ids with values of 11, 12, 13, 21, 22 and 23. Among them, R1 and R2 can issue BFR-ids with values of 11, 12, 13, 21, 22 and 23 through the sub-tlv of the BFR-id range.
  • the sub-tlv of the BFR-id range can be carried by the BIER Proxy Range sub-TLV defined by draft-ietf-bier-prefix-redistribute-00.
  • the sub-TLV represents three BFR-ids whose BFR-id starts from 21, that is, the BFR-id is 21, 22 and 23. numerical value.
  • the device serving as BFER can carry the BFR-id configured by itself in the published BIER information.
  • the BIER information released by R1 to area A1 also includes the valid BFR-id assigned by R1.
  • the BIER information released by R2 to area A1 also includes the valid BFR-id assigned by R2.
  • R1's host prefix may be used when R1 publishes BIER information.
  • R2's host prefix can be used when R2 publishes BIER information.
  • the above-mentioned host prefix is a prefix of a 32-bit mask under the Internet Protocol version 4 (Internet Protocol version 4, IPv4) network, and its information is a complete IPv4 address.
  • the above host prefix is a prefix of a 128-bit mask under the Internet Protocol version 6 (Internet Protocol version 6, IPv6) network, and its information is a complete IPv6 address.
  • R1 can use the non-host routing prefix representing R1 to advertise BIER information to area A1, for example, a 64-masked IPv6 address as Locator to identify R1; or draft-ietf-bier-prefix- redistribute-00 uses an aggregated route or default route to carry the BIER information advertised by R1.
  • R2 can use the non-host routing prefix representing R2 to advertise BIER information to area A1, such as an IPv6 address with a 64 mask as the Locator to identify R2; or draft-ietf-bier-prefix-redistribute-00 can use an aggregated route or default route to carry the BIER information released by R2.
  • R1 in Figure 1 can respectively receive its own BFR-id issued by R11, R12 and R13 in area A10, receive its own BFR-id issued by R21, R22 and R23 in area A20, and also receive BIER issued by R2 information.
  • R11 uses the IP address of R11 as the BFR-prefix and publishes it together with the BFR-id value of 11.
  • the BIER Sub-TLV (Type value 9) defined by RFC8444 is carried in OSPFv2 Extended Prefix TLV.
  • the above sub-TLV can be used to carry the IP address of R11 and the BFR-id with a value of 11.
  • the BFR-id of R11 released by R2 can be carried in the BIER Proxy Range sub-TLV defined by draft-ietf-bier-prefix-redistribute-00, and the TLV can also carry the BFR-prefix whose value is the IP address of R2.
  • R1 preferentially uses the information published by R11 through BIER-info TLV or BIER sub-TLV to establish bit index routing table (BIRT) entries and bit index forwarding table (BIFT) entries to reach R11 .
  • the BIRT entry and BIFT entry established by R1 to reach R11 include the BFR-id value of 11, the next hop is the BFR-prefix of R11, and the outgoing interface is the interface between R1 and R11.
  • the BIRT entry and BIFT entry established by R1 to reach R12 include the BFR-id value of 12, the next hop is the BFR-prefix of R12, and the outgoing interface is the interface between R1 and R12.
  • the method of establishing the BIRT entry and the BIFT entry to R13, R21, R22 and R23 established by R1 is the same as the method of establishing the above-mentioned BIRT entry and BIFT entry, and will not be repeated here.
  • any of the above devices will receive the BIER information released by R1 and the BIER information released by R2.
  • the BIFT entry includes the next hop node information and the forwarding bit mask (Forwarding-Bit-Mask, FBM) to the BFR-id, which can be represented by (BFR-id, NextHop, FBM).
  • FBM forwarding bit mask
  • any one of the above three devices will receive the BIER information released by R1 and the BIER information released by R2.
  • Both the BIER information published by R1 and the BIER information published by R2 include BFR-ids with values of 11, 12, 13, 21, 22, and 23.
  • R3, R4 or R5 can determine the next hop and outgoing port according to the routing and longest matching algorithm of the BFR-id advertised with values of 11, 12, 13, 21, 22 and 23.
  • the publisher of the selected BIER information is not the performance Best equipment, flexibility and forwarding performance to be improved.
  • the method provided by this embodiment of the present application can solve the problem of how one or more of R3, R4, and R5 select the next hop with the best performance in the scenario where R1 and R2 publish the same BFR-id in FIG. 1 . question.
  • both R1 and R2 publish the BFR-id of the device serving as the BFER in the area A10
  • R3 and R4 in the area A1 use the method provided by the embodiment of the present application to select the next hop as an example for description.
  • the method adopted by R5 is the same as the method adopted by R3 or R4, which is not repeated in this embodiment of the present application.
  • the method for selecting the next hop for the edge BFR in area A1 can refer to the method used in the above R3 or R4, which is no longer used in this embodiment of the application. Repeat.
  • FIG. 2 is a schematic flowchart of a method for determining a next hop according to Embodiment 1 of the present application.
  • both R3 and R4 in Figure 1 will receive attributes from R1, attributes of R2, and BIER information sent by R1 and R2.
  • R3 or R4 is based on attributes of R1, attributes of R2, attributes of R1 and R2
  • the next hop is determined in the sent BIER information.
  • the attributes of R1 and R2 are of the same type, but the values can be the same or different.
  • R3 or R4 uses the BIER information sent by the next hop to generate entries for forwarding BIER packets.
  • the entry used to forward the BIER message can be one entry or multiple entries in the BIFT entry and the BIRT entry.
  • Embodiment 1 of the present application is described by taking an example that the BFR-prefixes of R1 and R2 are the same.
  • the method for determining the next hop provided by Embodiment 1 of the present application will be described below with reference to FIG. 1 and FIG. 2 .
  • R1 and R2 can be configured with the same BFR-prefix.
  • the edge BFR of the area A10 shown in FIG. 1 includes R11, R12 and R13.
  • the same BFR-prefix in this embodiment of the present application may be represented by an address prefix, and the BFR-prefix may be an IPv4 address or an IPv6 address disclosed in RFC8401 or RFC8444, or the BFR-prefix may be an IPv6 address block.
  • the IPv6 address block may be a 64-masked address block.
  • the first identifier is a BFR-prefix for identifying as anycast.
  • the BIER information published by R1 may be the first BIER information
  • the BIER information published by R2 may be the second BIER information.
  • the BFR-id included in the first BIER information or the second BIER information can be sent in the manner mentioned in RFC8401 or RFC8444, or carried in the BFR-id range of draft-ietf-bier-prefix-redistribute-00 for sending .
  • the BFR-prefix of R1 and R2 can be carried and sent through the Adv-bfr-prefix field.
  • the first identifiers included in the attributes of R1 and R2 may be carried and sent through the Adv-anycast-flag field.
  • the attribute of R1 may further include one or more of a node identifier of R1 and a second identifier for identifying a priority.
  • the attributes of R2 may also include one or more of the node identification of R2 and a third identification for identifying the priority.
  • the node identifier in the embodiment of the present application is a system identifier (system-id) in an intermediate system to intermediate system (ISIS) protocol, and is a system-id in an Open Shortest Path First (Open Shortest Path First, OSPF) protocol
  • the router-id is carried in the Adv-router-id field for transmission.
  • the above-mentioned second identifier and the above-mentioned third identifier may be carried in the Adv-admin-tag field for transmission.
  • R3 receives attributes from R1, attributes from R2, first BIER information from R1, and second BIER information from R2.
  • the second BIER information from R2 received by R3 may come from one interface or multiple interfaces among the interface through which R3 communicates with R1 and the interface through which R3 communicates with R4.
  • R3 determines based on the first BIER information and the second BIER information that both R1 and R2 can be used as intermediate BFRs reaching the edge BFRs included in the area A10.
  • R3 can determine whether the first identifier exists in the attribute of R1 and the attribute of R2. If neither the attribute of R1 nor the attribute of R2 includes the first identifier, then R3 determines that the configuration is incorrect, and outputs an alarm.
  • the R3 method determines that the configuration is correct, and S203 is executed.
  • the method of outputting the alarm may output the alarm to the network management device or other management device through the Network Configuration Protocol (NETCONF).
  • NETCONF Network Configuration Protocol
  • R3 determines the next hop to the edge BFR included in the area A10.
  • R3 determines the next hop as the device corresponding to the attribute carrying the first identifier, for example, the attribute published by R1 includes the first identifier. ID, and the attribute published by R2 does not include the first ID, then R3 sets the next hop to the edge BFR of the area A10 as R1, then the BIRT entry or BIFT entry corresponding to the edge BFR of the area A10 obtained by R3
  • the next hop included is R1, and the outgoing interface is the interface through which R3 communicates with R1.
  • the attribute advertised by R2 includes the first identifier, but the attribute advertised by R1 does not include the first identifier, then R3 will reach the next hop device R2 of the edge BFR of the area A10, then the BIRT table obtained by R3 corresponding to the edge BFR of the area A10
  • the next hop included in the entry or BIFT entry is R2, and the outgoing interface is the interface on R3 that can communicate with R2.
  • the interfaces on R3 that can communicate with R2 include an interface through which R3 communicates with R1 and an interface through which R3 communicates with R4.
  • R3 determines an interface capable of communicating with R2, it may select an interface capable of communicating with R2 according to a link cost (cost) or a link state.
  • cost cost
  • BIRT entries can be in the following ways:
  • BIFT entries can be in the following ways:
  • R3 can use the following methods to determine the next hop:
  • R3 can according to the first strategy, the node identification of R1 and the node identification of R2. , and determine the device as the next hop from R1 and R2.
  • the first strategy may be that the node identifies the larger device as the next hop, or the node identifies the smaller device as the next hop.
  • the attribute of R1 includes the node identification and the second identification of R1
  • the attribute of R2 includes the node identification and third identification of R2.
  • R3 can be based on the second strategy,
  • the second identifier and the third identifier determine the device as the next hop from R1 and R2.
  • the second policy may be that the device with the higher priority among the second identifier and the third identifier is used as the next hop, or the second policy may be the device with the lower priority among the second identifier and the third identifier as the next hop.
  • the attribute of R1 includes the second identification
  • the attribute of R2 includes the third identification
  • the priority identified by the second identification is different from the priority identified by the third identification
  • R3 can be based on the second policy, the second identification and the third identification.
  • the attribute of R1 includes the node identification and the second identification of R1
  • the attribute of R2 includes the node identification and the third identification of R2, when the priority identified by the second identification and the priority identified by the third identification are the same
  • R3 can determine the device as the next hop from R1 and R2 according to the first policy, the node identifier of R1 and the node identifier of R2.
  • the first strategy may be that the node identifies the larger device as the next hop, or the node identifies the smaller device as the next hop.
  • the attribute of R1 includes the node identification of R1 and the second identification
  • the attribute of R2 includes the node identification of R2 and the third identification, when the node identification of R1 and the node identification of R2 are the same, and the second identification is preferred.
  • R3 can select any device from R1 and R2 as the next hop.
  • R3 may obtain an entry for forwarding the BIER packet.
  • the next hop included in the entry for forwarding the BIER packet is the next hop determined by R3.
  • R4 judges whether to give an alarm according to the received attribute of R1 and the attribute of R2, and if not, execute S205.
  • R4 receives attributes from R1, attributes from R2, first BIER information from R1, and second BIER information from R2.
  • R4 determines based on the first BIER information and the second BIER information that both R1 and R2 can be used as intermediate BFRs reaching the edge BFRs included in the area A10.
  • R4 can determine whether the first identifier exists in the attribute of R1 and the attribute of R2. If neither the attribute of R1 nor the attribute of R2 has the first identifier, then R4 determines that the configuration is incorrect, and outputs an alarm. If at least one of the attribute of R1 and the attribute of R2 includes the first identifier, then R4 determines that the configuration is correct, and executes S205.
  • the method of outputting the alarm please refer to the method adopted by R3.
  • R4 determines the next hop to the edge BFR included in the area A10.
  • R4 determines the next hop as the device corresponding to the attribute carrying the first identifier, for example, the attribute of R1 published by R1 includes The first identifier, and the attribute of R2 published by R2 does not include the first identifier, then R4 sets the next hop to the edge BFR of the area A10 as R1, then the BIRT entry corresponding to the edge BFR of the area A10 obtained by R4 or The next hop included in the BIFT entry is R1, and the outgoing interface is the interface between R4 and R1.
  • the attributes of R2 advertised by R2 include the first identifier, and the attributes of R1 advertised by R1 do not include the first identifier, then R4 will reach the next-hop device R2 of the edge BFR of area A10, then the edge BFR of area A10 obtained by R4 and the edge BFR of area A10 will be reached.
  • the next hop included in the corresponding BIRT entry or BIFT entry is R2, and the outgoing interface is the interface through which R4 communicates with R2.
  • R4 may obtain an entry for forwarding the BIER packet.
  • the next hop included in the entry for forwarding the BIER packet is the next hop determined by R4.
  • R3 or R4 when R3 or R4 sends a BEIR multicast packet to the area A10, it can use the obtained entry for forwarding the BIER packet to send the multicast packet to the next hop.
  • the method for determining the next hop of the edge BFR reaching the area A10 is more flexible, and an alarm can be raised for a configuration error.
  • the priority comparison method the priority of the device with better performance can be set according to the second policy, so that the node with better performance can be determined as the next hop.
  • the node identifier of the device with better performance can be set according to the first strategy, so that the node with better performance can be determined as the next hop. In this way, the method provided by the embodiment of the present application can further meet the performance requirement of the multicast service based on the next hop with better performance and improve the forwarding efficiency.
  • FIG. 3 is a schematic flowchart of a method for determining a next hop according to Embodiment 2 of the present application.
  • both R3 and R4 in Figure 1 will receive attributes from R1, attributes from R2, and BIER information sent by R1 and R2.
  • R3 or R4 determines the next step based on the attributes of R1 and R2.
  • R3 or R4 uses the BIER information sent by the next hop to generate entries for forwarding BIER packets.
  • the entry used to forward the BIER message can be one entry or multiple entries in the BIFT entry and the BIRT entry.
  • the second embodiment of the present application is described by taking an example that the BFR-prefixes of R1 and R2 are different.
  • the method for determining the next hop provided by Embodiment 2 of the present application will be described below with reference to FIG. 1 and FIG. 3 .
  • R1 and R2 may be configured with different BFR-prefixes
  • the BFR-prefix configured with R1 may be the first address
  • the BFR-prefix configured with R2 may be the second address.
  • the meaning of the BFR-prefix in the second embodiment is the same as that in the first embodiment, and details are not repeated here.
  • the edge BFR of the area A10 shown in FIG. 1 includes R11, R12 and R13.
  • the first BIER information issued by R1 to R3 in the area A1 through the IGP includes BFR-ids with values of 11, 12 and 13.
  • the attribute of R1 advertised by R1 to R3 of the area A1 through the IGP includes the first address.
  • the second BIER information issued by R2 to R3 in the area A1 through the IGP includes BFR-ids with values of 11, 12 and 13.
  • the attribute of R2 advertised by R2 to R3 of the area A1 through the IGP includes the second address.
  • the BFR-id included in the first BIER information or the second BIER information can be sent in the manner disclosed in RFC8401 or RFC8444, or carried in the BFR-id range of draft-ietf-bier-prefix-redistribute-00 for sending.
  • the BFR-prefix can be carried and sent through the Adv-bfr-prefix field.
  • the attribute of R1 may further include one or more of a node identifier of R1 and a second identifier for identifying a priority.
  • the attributes of R1 may also include one or more of the node identification of R2 and a third identification for identifying the priority.
  • the node identifier in the second embodiment reference may be made to the corresponding content of the first embodiment, which will not be repeated here.
  • the identifier used to identify the priority in the second embodiment reference may be made to the corresponding content of the first embodiment, which will not be repeated here.
  • the above node identifier may be carried in the Adv-router-id field for transmission.
  • the above-mentioned second identifier and the above-mentioned third identifier may be carried in the Adv-admin-tag field for transmission.
  • R3 determines the next hop according to the received attributes of R1 and R2.
  • R3 receives attributes from R1, attributes from R2, first BIER information from R1, and second BIER information from R2.
  • the second BIER information from R2 received by R3 may come from one interface or multiple interfaces among the interface through which R3 communicates with R1 and the interface through which R3 communicates with R4.
  • R3 determines that intermediate BFRs passed through by the edge BFR included in the arrival area A10 include R1 and R2.
  • R3 may determine the next hop based on the attributes of R1 and the attributes of R2.
  • R3 writes the next hop into the BIRT entry or the BIFT entry corresponding to the edge BFR of the area A10.
  • the method in Embodiment 1 may be used to determine the interface capable of communicating with R2, which will not be repeated here.
  • R3 can use any one of the following methods or a combination of several methods to determine the device as the next hop from R1 and R2, as follows:
  • R3 can according to the first strategy, the node identification of R1 and the node identification of R2. , and determine the device as the next hop from R1 and R2.
  • the first strategy may be that the node identifies the larger device as the next hop, or the node identifies the smaller device as the next hop.
  • the attribute of R1 includes the node identification and the second identification of R1
  • the attribute of R2 includes the node identification and third identification of R2.
  • R3 can be based on the second strategy,
  • the second identifier and the third identifier determine the device as the next hop from R1 and R2.
  • the second policy may be that the device with the higher priority among the second identifier and the third identifier is used as the next hop, or the second policy may be the device with the lower priority among the second identifier and the third identifier as the next hop.
  • the attribute of R1 includes the second identification
  • the attribute of R2 includes the third identification
  • the priority identified by the second identification is different from the priority identified by the third identification
  • R3 can be based on the second policy, the second identification and the third identification.
  • the attribute of R1 includes the node identification and the second identification of R1
  • the attribute of R2 includes the node identification and the third identification of R2, when the priority identified by the second identification and the priority identified by the third identification are the same
  • R3 can determine the device as the next hop from R1 and R2 according to the first policy, the node identifier of R1 and the node identifier of R2.
  • the attribute of R1 includes the node identification of R1 and the second identification
  • the attribute of R2 includes the node identification of R2 and the third identification, when the node identification of R1 and the node identification of R2 are the same, and the second identification is preferred.
  • R3 can determine any device from R1 and R2 as the next hop.
  • the attribute of R1 includes the cost value of R1 reaching R3, the attribute of R2 includes the cost value of R2 reaching R3, and R3 can be based on the fourth strategy, the cost value of R1 reaching R3 and the cost value of R2 reaching R3, from R1 and R2 The device as the next hop is determined. Among them, the cost value of R2 reaching R3 and the cost value of R1 reaching R3.
  • the fourth strategy is to select a device with a smaller cost value as the next hop, or select a device with a larger cost value as the next hop.
  • one or a combination of the above manners 1 to 5 may be used to determine the next hop.
  • the first BIER information may not need to carry the second identifier
  • the second BIER information may not need to carry the third identifier.
  • the attributes of R1 include the BFR-prefix of R1
  • the attributes of R2 include the BFR-prefix of R2
  • the R3 can be determined from R1 and R2 according to the fifth strategy, the BFR-prefix of R1 and the BFR-prefix of R2.
  • the fifth strategy is to select a device with a smaller BFR-prefix as the next hop, or select a device with a larger BFR-prefix as the next hop.
  • the attribute of R1 does not need to carry the second identification, and the attribute of R2 does not need to carry the third identification; even if the attribute of R1 includes the node identification of R1, the attribute of R2 includes the node identification of R2, and the attribute of R3 does not need to carry the node identification of R2. Identify and compare.
  • R3 when R3 cannot determine the next hop by using the sixth method, it can determine the next hop by using the seventh method. Or when R3 cannot determine the next hop by using the sixth method, it can use the first method to determine the next hop. Or when R3 cannot determine the next hop by using the sixth method and the first method, it can use the second method to determine the next hop. Or when R3 cannot determine the next hop by using the sixth, the first and the second mode, it can use the seventh or the fifth mode to determine the next hop. Or when R3 cannot determine the next hop by using the sixth method, it can use the third method to determine the next hop. Or when R3 cannot determine the next hop by using the sixth and third modes, it can determine the next hop by using the fourth mode.
  • R4 determines the next hop according to the received attributes of R1 and R2.
  • R4 receives the first BIER information from R1 and the second BIER information from R2, and R4 also receives the attributes of R1 and the attributes of R2. Based on the first BIER information and the second BIER information, R4 determines that the intermediate BFRs passed through by the edge BFRs included in the arrival area A10 include R1 and R2. R4 may use the same method as that used by R3 to determine the next hop, which will not be repeated here. Optionally, after determining the next hop, R4 writes the next hop into the BIRT entry or the BIFT entry corresponding to the edge BFR of the area A10.
  • the above-obtained entry for forwarding the BIER packet can be used to send the multicast packet to the next hop.
  • the method for determining the next hop of the edge BFR reaching the area A10 is more flexible, and an alarm can be raised for a configuration error.
  • the priority comparison method is adopted, the priority of the device with better performance can be set according to the second policy, so that the node with better performance can be determined as the next hop.
  • the node identifier of the device with better performance can be set according to the first strategy, so that the node with better performance can be determined as the next hop. In this way, the method provided by the embodiment of the present application can further meet the performance requirement of the multicast service based on the next hop with better performance and improve the forwarding efficiency.
  • the third embodiment is to determine the BIRT and BIFT of a certain BFR-id according to the size of the adv-admin-tag in multiple messages after the adv-admin-tag is configured.
  • the following describes the configuration and processing methods of related equipment in conjunction with the scenario shown in Figure 1:
  • R1 publishes the first BIER information with BFR-ids 11, 12, 13, 21, 22, and 23 to the isis 1 process (corresponding to area A1), using the BFR-id Range sub-TLV.
  • R1 will also publish the information that the BFR-id of this node is 1 to the isis 1 process, using the BIER-info sub-TLV defined by RFC8401.
  • the above information published by R1 to the isis 1 process uses the IP address 2001:1:1:1::10 of loopback1 as the BFR-prefix.
  • FIG 4 is an example of an IS-IS message sent by R1 carrying a BFR-id Range sub-TLV, which are all sub-TLVs as ISIS Prefix TLVs (TLV types are one of 135, 235, 236 and 237). exists, where the BFR-id range sub-TLV can be a pair of BIER proxy range sub-TLVs as defined in draft-ietf-bier-prefix-redistribute-00.
  • the packet format shown in Figure 4 may be another example in which the IS-IS message sent by R1 carries a BFR-id Range sub-TLV, where the BFR-id Range sub-TLV is used as an ISIS Prefix TLV (TLV type is 135, 235, 236 and 237) sub-TLVs exist.
  • the BFR-id Range sub-TLV in the message published by router R1 contains BFR-id ranges of 11, 12, 13, 21, 22 and 23; the BFR-id range sub-TLV can be a pair of draft-ietf-bier-prefix Modified from the BIER proxy range sub-TLV defined in -redistribute-00.
  • R1 publishes information with a BFR-id of 3, 4 or 5 to the isis 2 process (corresponding to areas A10 and A20), using the BFR-id Range sub-TLV.
  • the above information published by R1 to the isis 2 process uses the IP address 2001:1:1:1::20 of loopback2 as the BFR-prefix.
  • R2 publishes BFR-ids 11, 12, 13, 21, 22, and 23 to the isis 1 process (corresponding to area A1), using the BFR-id Range sub-TLV.
  • the above information published by R2 to the isis 1 process uses the IP address 2001:2:2:2:10 of loopback1 as the BFR-prefix.
  • R2 publishes information with BFR-ids 3, 4 and 5 to the isis 2 process (corresponding to areas A10 and A20), using the BFR-id Range sub-TLV.
  • the above information published by R2 to the isis 2 process uses the IP address 2001:2:2:2::20 of loopback2 as the BFR-prefix.
  • the packet format used by R2 may be the packet format shown in FIG. 4 , which will not be repeated here.
  • the fourth embodiment describes that the next hop included in the BIRR and BIFT of a certain BFR-id is determined by configuring the adv-admin-tag and according to the size of the adv-admin-tag in multiple messages.
  • the configuration of the fourth embodiment will be described below with reference to the scenario shown in FIG. 1 .
  • R1 publishes BFR-ids 11, 12, 13, 21, 22 and 23 to the isis 1 process (corresponding to area A1), and carries an administrative-tag with a value of 1, using the BFR-id Range sub -TLV.
  • the above information published by R1 to the isis 1 process uses the IP address 2001:1:1:1:10 of loopback1 as the BFR-prefix.
  • Figure 5 is an example of an IS-IS message sent by R1 carrying an administrative-tag and a BFR-id Range sub-TLV.
  • the above parameters are used as ISIS Prefix TLVs (TLV types are 135, 235, 236 and 237) A) sub-TLVs exist.
  • the administrative-tag value is used as the preferred distinction of the BFR-id contained in the BFR-id Range sub-TLV.
  • the BFR-id Range sub-TLV contains the BFR-id of 11, 12, 13, 21, 22 and 23, the Administrative-tag value is 1.
  • the BFR-id range sub-TLV may be a pair of BIER proxy range sub-TLVs as defined in draft-ietf-bier-prefix-redistribute-00.
  • FIG. 5 is another example of an IS-IS message sent by an R1 carrying an administrative-tag and a BFR-id Range sub-TLV.
  • the BFR-id Range sub-TLV exists as a sub-TLV of the ISIS Prefix TLV (TLV type is one of 135, 235, 236 and 237), and the administrative-tag value is defined in the BFR-id Range sub-TLV middle.
  • TLV type is one of 135, 235, 236 and 23
  • the administrative-tag value is defined in the BFR-id Range sub-TLV middle.
  • the BFR-id Range sub-TLV contains BFR-id ranges of 11, 12, 13, 21, 22, and 23, and the Administrative-tag value is 1.
  • One of the ISIS Prefix TLVs contains two BFR-id Range sub-TLVs.
  • Each BFR-id Range sub-TLV contains an administrative Tag and a (BFR-id, BFR-id range) tuple.
  • the BFR-id range sub-TLV can be modified from the BIER proxy range sub-TLV defined in draft-ietf-bier-prefix-redistribute-00.
  • R1 publishes information with a BFR-id of 3, 4 or 5 to the isis 2 process (corresponding to areas A10 and A20) and carries an administrative-tag with a value of 1, using the BFR-id Range sub-TLV.
  • the above information published by R1 to the isis 2 process uses the IP address 2001:1:1:1::20 of loopback2 as the BFR-prefix.
  • R2 is published to the isis 1 process (corresponding to area A1) as 11, 12, 13, 21, 22, and 23, and carries an administrative-tag with a value of 2, using the BFR-id Range sub-TLV.
  • the above information published by R2 to the isis 1 process uses the IP address 2001:2:2:2:10 of loopback1 as the BFR-prefix.
  • R2 publishes information with BFR-ids 3, 4, and 5 to the isis 2 process (corresponding to areas A10 and A20) and carries an administrative-tag with a value of 2, using the BFR-id Range sub-TLV.
  • the above information published by R2 to the isis 2 process uses the IP address 2001:2:2:2::20 of loopback2 as the BFR-prefix.
  • R2 may also use the message format of FIG. 5 or FIG. 6 to publish the second BIER information and the attributes of R2, which will not be repeated here.
  • the routers in the area A0 establish next-hop routing and forwarding information to the BFR-ids 11, 12, 13, 21, 22, and 23. For details, refer to the corresponding content in Embodiment 1 or Embodiment 2, which will not be repeated here.
  • Embodiment 5 By configuring anycast BFR-prefix and configuring the same BIER encapsulation related information, the BIRT and BIFT of a certain BFR-id are determined according to the route to the BFR-prefix. In this embodiment, neither R1 nor R2 is configured with a valid BFR-id value (the BFR-id value filled in the BIER info sub-TLV is an invalid value of 0). The configuration method will be described below with reference to the scenario shown in FIG. 1 .
  • Interface loopback1 2001:1:1:1::AAAA anycast indicates that the configured IPv6 address is an anycast address, which is used as the BFR-prefix for BIER information release.
  • Interface loopback2 2001:1:1:1::BBBB anycast indicates that the configured IPv6 address is an anycast address, which is used as the BFR-prefix for BIER information release.
  • end-bier sid 2001:1:1:1::AB37 anycast indicates that the encapsulation information used to forward BIER packets is an Anycast information.
  • end-bier is a BIER packet used for BIERv6 encapsulation. package information.
  • anycast indicates that the encapsulation information used for forwarding BIER packets is an Anycast information.
  • the bift-id in this example is a BIER packet encapsulation information used for BIERv6/BIER-MPLS encapsulation.
  • the bift-id value is an MPLS label. To support the Anycast method in this solution, it is necessary to manually configure R1 and R2 to use the same MPLS label, that is, configure the same bift-id value.
  • bift-id When used in Non-MPLS encapsulation or BIERv6 encapsulation, bift-id can be a value automatically generated according to BIER's Sub-domain-id, BitStringLength ID(BSL), Set Identifier(SI), R1 and R2 according to The same rule generates the same value, so no additional configuration is required.
  • anycast-flag indicates that the anycast flag is carried when publishing BIER information.
  • Figure 7 is an example of an IS-IS message sent by an R1 carrying an Anycast flag and a BFR-id Range sub-TLV, all of which are used as ISIS Prefix TLVs (TLV types are one of 135, 235, 236 and 237). Sub-TLVs exist, as shown in Figure 7.
  • anycast flag bit (the 4th bit of the flag bit field of the sub-TLV) defined by draft-ietf-lsr-isis-srv6-extensions-11 based on the Prefix Attribute Flags sub-TLV of RFC7794 bit), the flag bit is used in this scheme as a method for publishing BIER information and establishing BIER routing and BIER forwarding information accordingly.
  • R2 publishes BFR-id 11, 12, 13, 21, 22 and 23 to the isis 1 process (corresponding to area A1), and carries the anycast flag, using BFR-id Range sub-TLV; R2 will also send
  • R3, R4 and R5 receive the information released by R1 and R2 above.
  • FIG. 8 is an apparatus for determining a next hop provided by an embodiment of the present application.
  • the device 800 may be disposed on the edge BFR, such as R3 , R4 or R5 , of the region A1 except for R1 and R2 in any one of the first to fifth embodiments above.
  • the first device mentioned in this application as an example may be R1 in any one of the foregoing Embodiments 1 to 5, and the second device may be R2 in any of the foregoing Embodiments 1 to 5.
  • the apparatus 800 is configured to forward and route the BIER domain based on the bit index, and includes: an acquisition unit 801 and a determination unit 802 .
  • the obtaining unit 801 is configured to obtain first BIER information of a first device, attributes of the first device, second BIER information of a second device, and attributes of the second device, where the first BIER information includes The bit-forwarding router identification BFR-id of the edge bit-forwarding router BFR in the sub-domain, and the second BIER information includes the BFR-id of the edge BFR in the sub-domain.
  • the determining unit 802 is configured to determine, according to the first BIER information, the second BIER information, the attribute of the first device and the attribute of the second device, the lower part of the edge BFR that reaches the subdomain. One hop.
  • the attribute of the first device and the attribute of the second device include a first identifier, where the first identifier is used to identify the BFR prefix of anycast
  • the apparatus further includes: an identification unit .
  • the identification unit is configured to perform a determination of the arrival of the subdomain when the first BIER information and the second BIER information are the same, and the attribute of the first device and the attribute of the second device include the first identifier. The next hop of the BFR.
  • the attribute of the first device or the attribute of the second device includes a first identifier
  • the first identifier is used to identify the BFR prefix of anycast
  • the determining unit 802 is specifically configured to When the first BIER information and the second BIER information are the same, a device whose attribute includes the first identifier is determined as the next hop.
  • the apparatus further includes: an output unit.
  • the output unit is configured to output an alarm when the first BFR information and the second BIER information are the same, and neither the attribute of the first device nor the attribute of the second device includes the first identifier.
  • the attribute of the first device further includes a node identifier of the first device
  • the attribute of the second device includes a node identifier of the second device.
  • the determining unit 802 specifically For: when the first BIER information is the same as the second BIER information, based on the first policy, the node identifier of the first device and the node identifier of the second device, determine the first device and the second device. One of the second devices is used as the next hop, and the first strategy includes using a device with a larger node identification as the next hop or a device with a smaller node identification as the next hop.
  • the attribute of the first device further includes a second identifier
  • the attribute of the second device further includes a third identifier
  • the second identifier is used to identify the priority of the first device level
  • the third identifier is used to identify the priority of the second device
  • the determining unit 802 is specifically configured to: when the first BIER information is the same as the second BIER information, based on the second policy, The second identifier and the third identifier determine one of the first device and the second device as the next hop, and the second strategy includes using the device with a higher priority as the next hop Or take the device with lower priority as the next hop.
  • the attribute of the first device includes a BFR prefix of the first device
  • the attribute of the second device includes a BFR prefix of the second device
  • the BFR prefix of the first device The prefix is different from the BFR prefix of the second device
  • the determining unit 802 is specifically configured to: when the first BIER information and the second BIER information are the same, according to the third policy, the overhead cost of the first link value and the cost value of the second link, determine one of the first device and the second device as the next hop
  • the third strategy includes using the device on the opposite end of the link with a smaller cost value as the next hop
  • One hop or the device on the opposite end of the link with a larger cost value is used as the next hop
  • the first link is the link from the third device to the first device
  • the second link is the The link from the third device to the second device.
  • the attribute of the first device includes a BFR prefix of the first device
  • the attribute of the second device includes a BFR prefix of the second device
  • the BFR prefix of the first device The prefix is different from the BFR prefix of the second device
  • the determining unit 802 is specifically configured to: when the first BIER information and the second BIER information are the same, according to the fourth policy, the BFR of the first device prefix and the BFR prefix of the second device, determine one of the first device and the second device as the next hop, and the fourth policy includes using the device with the smaller BFR prefix as the next hop or Use the device with a larger BFR prefix as the next hop.
  • the attribute of the first device includes the BFR prefix of the first device and the node identifier of the first device
  • the attribute of the second device includes the BFR of the second device prefix and the node identifier of the second device
  • the BFR prefix of the first device is different from the BFR prefix of the second device
  • the determining unit 802 is specifically configured to: in the first BIER information and the second device When the two BIER information are the same, according to the first policy, the node identifier of the first device and the node identifier of the second node, determine one of the first device and the second device as the next hop, and the first device and the second device are determined as the next hop.
  • the strategy includes taking the device with the larger node identification as the next hop or the device with the smaller node identification as the next hop.
  • the attribute of the first device includes a BFR prefix and a second identifier of the first device
  • the attribute of the second device includes a BFR prefix and a third identifier of the second device
  • the second identifier is used to identify the priority of the first device
  • the third identifier is used to identify the priority of the second device
  • the BFR prefix of the first device is the same as that of the second device.
  • the determining unit 802 is specifically configured to: when the first BIER information and the second BIER information are the same, determine the first BIER according to the second policy, the second identifier and the third identifier One of the device and the second device is used as the next hop, and the second strategy includes using a device with a higher priority as the next hop or a device with a lower priority as the next hop.
  • FIG. 9 is a schematic structural diagram of an apparatus for determining a next hop according to an embodiment of the present application.
  • the apparatus 900 for determining the next hop provided in the embodiment corresponding to FIG. 10 may be the apparatus 800 for determining the next hop provided in the embodiment corresponding to FIG. 8 .
  • the apparatus 900 for determining the next hop provided by the embodiment corresponding to FIG. 9 is described from the perspective of hardware structure.
  • the apparatus 900 for determining the next hop includes a processor 901 , a memory 902 , a communication bus 904 and a communication interface 903 .
  • the processor 901 , the memory 902 and the communication interface 903 are connected through a communication bus 904 .
  • the memory 902 is used to store programs.
  • the processor 901 executes the above implementation according to the executable instructions included in the program read from the memory 902 The method performed by any one of Embodiments R3 or R4 in Embodiments 1 to 5.
  • An embodiment of the present application provides a system, where the system includes an apparatus 800 for determining a next hop.
  • the apparatus 800 for determining the next hop may be configured to perform the method performed by R3 or R4 mentioned in any one of Embodiments 1 to 5.
  • An embodiment of the present application provides a chip.
  • the chip may include the memory 901 and the processor 901 shown in FIG. 9 .
  • the memory 902 is used to store computer instructions.
  • the processor 901 is configured to call and execute the computer instructions from the memory 902 to execute the method executed by R3 or R4 mentioned in any one of Embodiments 1 to 5.
  • the chip provided by the embodiment of the present application may be disposed on the forwarding hardware, or the forwarding circuit included in the forwarding hardware may be integrated with the chip provided by the embodiment of the present application.
  • At least one item (piece) refers to one or more, and “multiple” refers to two or more.
  • At least one item(s) below” or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
  • at least one item (a) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c may be single or multiple .
  • “A and/or B” is considered to include A alone, B alone, and A+B.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical module division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be acquired according to actual needs to achieve the purpose of the solution in this embodiment.
  • each module unit in each embodiment of the present 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-mentioned integrated unit may be implemented in the form of hardware, or may be implemented in the form of software module units.
  • the integrated unit if implemented in the form of a software module unit and sold or used as a stand-alone product, may be stored in a computer-readable storage medium.
  • the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing 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 described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes .
  • the functions described in the present invention may be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

本申请实施例提供的一种确定下一跳的方法，所述方法应用于基于位索引转发路由 BIER 域，包括: 第三设备获取第一设备的第一 BIER 信息、所述第一设备的属性、第二设备的第二 BIER 信息和所述第二设备的属性，所述第一 BIER 信息包括子域中的边缘位转发路由器BFR的位转发路由器标识BFR-id，所述第二 BIER 信息包括所述子域中的所述边缘 BFR 的所述 BFR-id; 所述第三设备根据所述第一 BIER 信息、所述第二 BIER 信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘 BFR 的下一跳。

Description

确定下一跳的方法及装置
本申请要求于2020年10月30日提交国家知识产权局、申请号为202011193045.7、发明名称为“一种建立转发表的方法及装置”的中国专利申请的优先权，以及要求于2021年2月10日提交国家知识产权局、申请号为202110184092.3、发明名称为“确定下一跳的方法及装置”的中国专利申请的优先权。上述中国专利申请的全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，特别涉及一种确定下一跳的方法及装置。
背景技术
在位索引显式复制(Bit Index Explicit Replication，BIER)域内，位转发入口路由器(bit forwarding ingress router，BFIR)或第一中间位转发路由器(transit bit forwarding router，transit BFR)可接收BIER域内的其它BFR(比如第二中间BFR或位转发出口路由器(bit forwarding egress router，BFER))通过内部网关协议(Internal gateway protocol，IGP)泛洪的BIER信息。该BIER信息包括：发送该BIER信息的BFR的BFR前缀(prefix)、一个或多个BFER的位转发路由器标识(bit forwarding router identifier，BFR-id)和其BFR prefix。其中，BFR prefix表示该BFR在BIER域内的地址。BFIR或第一中间BFR可根据通过IGP泛洪的BIER信息获得位索引转发表(bit index forwarding table，BIFT)。BIFT表项包括转发位串掩码(forwarding bitmask，F-BM)和作为下一跳的BFR邻居(BFR neighbor,BFR-NBR)。F-BM包括的比特串(bit string)中被置1的比特位与接收到的BIER信息中的BFER对应。BFR-NBR中的地址为BIER信息包括的发送该BIER信息的BFR的BFR prefix。当BIER域内存在两个中间BFR，比如第二BFR和第三BFR，发布的BIER信息包括相同的BFER的参数，比如BFER的BFR-id和BFER的BIER prefix，接收到来自第二BFR和第三BFR发布的BIER信息的BFR，比如BFIR或第一BFR，可根据最长匹配策略或等价多路径路由(equal-cost multi-path routing，ECMP)策略选择某个BFR发布的BIER信息，目前确定下一跳的方法不够灵活。
发明内容
本申请实施例提供了一种确定下一跳的方法及装置，能够提高灵活性。
第一方面，提供一种确定下一跳的方法，其特征在于，所述方法应用于基于位索引转发路由BIER域，包括：
第三设备获取第一设备的第一BIER信息、所述第一设备的属性、第二设备的第二BIER信息和所述第二设备的属性，所述第一BIER信息包括子域中的边缘位转发路由器BFR的位转发路由器标识BFR-id，所述第二BIER信息包括所述子域中的所述边缘BFR的所述BFR-id；
所述第三设备根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳。
上述方法中，第三设备可基于第一设备的属性和第二设备的属性，灵活地选择到达子域的边缘BFR的下一跳，不局限于最长匹配策略或ECMP策略进行选择，提高了确定下一跳的 灵活性。
在一种可能的设计中，所述第一设备的属性和所述第二设备的属性包括第一标识，所述第一标识用于标识anycast的BFR前缀，所述方法还包括：所述第三设备在所述第一BIER信息和所述第二BIER信息相同，且所述第一设备的属性和所述第二设备的属性包括第一标识时，执行确定到达所述子域中所述边缘BFR的下一跳。
在一种可能的设计中，所述第一设备的属性或所述第二设备的属性包括第一标识，所述第一标识用于标识anycast的BFR前缀，所述第三设备根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳包括：所述第三设备在所述第一BIER信息和所述第二BIER信息相同时，将属性包括所述第一标识的设备确定为下一跳。
在一种可能的设计中，所述方法还包括：所述第三设备在所述第一BFR信息和所述第二BIER信息相同，所述第一设备的属性和所述第二设备的属性均不包括第一标识时，输出告警，所述第一标识用于标识anycast的BFR前缀。
在一种可能的设计中，所述第一设备的属性还包括所述第一设备的节点标识，所述第二设备的属性包括所述第二设备的节点标识，所述第三设备根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳包括：所述第三设备在所述第一BIER信息与所述第二BIER信息相同时，基于第一策略、所述第一设备的节点标识和所述第二设备的节点标识，确定所述第一设备和第二设备中的一个设备作为下一跳，所述第一策略包括将节点标识较大的设备作为下一跳或者将节点标识较小的设备作为下一跳。
在一种可能的设计中，所述第一设备的属性还包括第二标识，所述第二设备的属性还包括第三标识，所述第二标识用于标识所述第一设备的优先级，所述第三标识用于标识所述第二设备的优先级，所述第三设备根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳包括：所述第三设备在所述第一BIER信息与所述第二BIER信息相同时，基于第二策略、所述第二标识和所述第三标识，确定所述第一设备和所述第二设备中的一个设备作为下一跳，所述第二策略包括将优先级较大的设备作为下一跳或者将优先级较小的设备作为下一跳。
在一种可能的设计中，所述第一设备的属性包括所述第一设备的BFR前缀，所述第二设备的属性包括所述第二设备的BFR前缀，所述第一设备的BFR前缀与所述第二设备的BFR前缀不同，所述第三设备根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳包括：所述第三设备在所述第一BIER信息和所述第二BIER信息相同时，根据第三策略、第一链路的开销cost值和第二链路的cost值，确定所述第一设备和所述第二设备中的一个设备作为下一跳，所述第三策略包括将cost值较小的链路对端的设备作为下一跳或者将cost值较大的链路对端的设备作为下一跳，所述第一链路为所述第三设备到达所述第一设备的链路，所述第二链路为所述第三设备到达所述第二设备的链路。
在一种可能的设计中，所述第一设备的属性包括所述第一设备的BFR前缀，所述第二设备的属性包括所述第二设备的BFR前缀，所述第一设备的BFR前缀与所述第二设备的BFR前缀不同，所述第三设备根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳包括：所述第三设备在所述第一BIER信息和所述第二BIER信息相同时，根据第四策略、所述第一设备的BFR 前缀和所述第二设备的BFR前缀，确定所述第一设备和所述第二设备中的一个设备作为下一跳，所述第四策略包括将BFR前缀较小的设备作为下一跳或者将BFR前缀较大的设备作为下一跳。
在一种可能的设计中，所述第一设备的属性包括所述第一设备的BFR前缀和所述第一设备的节点标识，所述第二设备的属性包括所述第二设备的BFR前缀和所述第二设备的节点标识，所述第一设备的BFR前缀与所述第二设备的BFR前缀不同，所述第三设备根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳包括：所述第三设备在所述第一BIER信息和所述第二BIER信息相同时，根据第一策略、所述第一设备的节点标识和所述第二节点的节点标识，确定第一设备和第二设备中的一个设备作为下一跳，所述第一策略包括将节点标识较大的设备作为下一跳或者将节点标识较小的设备作为下一跳。
在一种可能的设计中，所述第一设备的属性包括所述第一设备的BFR前缀和第二标识，所述第二设备的属性包括所述第二设备的BFR前缀和第三标识，所述第二标识用于标识所述第一设备的优先级，所述第三标识用于标识所述第二设备的优先级，所述第一设备的BFR前缀与所述第二设备的BFR前缀不同，所述第三设备根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳包括：所述第三设备在所述第一BIER信息和所述第二BIER信息相同时，根据第二策略、所述第二标识和所述第三标识，确定第一设备和第二设备中的一个设备作为下一跳，所述第二策略包括将优先级较大的设备作为下一跳或者将优先级较小的设备作为下一跳。
第二方面，提供一种确定下一跳的装置，该装置包括实现第一方面或第一方面任一种可能的设计所包括的步骤的功能的单元。
第三方面，提供一种系统，所述系统包括如上述第二方面或第二方面任一种可能设计提供的确定下一跳的装置。
第四方面，提供一种芯片，所述芯片包括存储器和处理器，所述存储器用于存储计算机指令，所述处理器用于从所述存储器中调用并运行所述计算机指令，以执行上述第一方面或第一方面任一可能的实现方式提供的确定下一跳的方法。
第五方面，提供一种计算机程序产品，所述计算机程序产品包括一个或多个计算机程序指令，当所述计算机程序指令被计算机加载并执行时，使得所述计算机执行上述第一方面或第一方面任一可能的实现方式提供的确定下一跳的方法。
第六方面，提供一种计算机可读存储介质，所述计算机可读存储介质用于存储指令，所述指令中包括用于执行上述第一方面或第一方面任一可能的实现方式提供的确定下一套的方法所设计的程序。
附图说明
图1为一种网络场景示意图。
图2为本申请实施例一提供的确定下一跳的方法的流程示意图。
图3为本申请实施例二提供的确定下一跳的方法的流程示意图。
图4为本申请实施例三提供的一种报文格式。
图5为本申请实施例四提供的一种报文格式。
图6为本申请实施例四提供的另一种报文格式。
图7为本申请实施例五提供的一种报文格式。
图8为本申请实施例提供的一种确定下一跳的装置的结构示意图。
图9为本申请实施例提供的另一种确定下一跳的装置的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述。
图1为一种网络场景示意图。图1所示的网络场景中，R1、R2、R3、R4、R5、R11、R12、R13、R21、R22和R23表示BIER域内的BFR。其中，R1、R2、R3、R4和R5处于同一IGP域内，该区域可以称为区域A1。R1被配置的BFR-id的数值为1。R2被配置的BFR-id的数值为2。R3被配置的BFR-id的数值为3。R4被配置的BFR-id的数值为4。R5被配置的BFR-id的数值为5。R3、R4和R5为边缘BFR。R1和R2可作为区域边界路由器(area border router，ABR)。当R1和R2不作为BFER时，R1和R2不需要配置BFR-id或者被配置的BFR-id属于无效值。R11、R12和R13处于同一IGP域内，该区域可以称为区域A10。R11、R12和R13均为边缘BFR，比如BFER。R11被配置的BFR-id的数值为11。R12被配置的BFR-id的数值为12。R13被配置的BFR-id的数值为13。R21、R22和R23处于同一IGP域内，该区域可以称为区域A20。R21、R22和R23均为边缘BFR，比如BFER。R21被配置的BFR-id的数值为21。R22被配置的BFR-id的数值为22。R23被配置的BFR-id的数值为23。在图1所示的场景中，R1和R2会将R11、R12、R13、R21、R22和R23的BIER信息泛洪给A1域内的BFR，比如R3、R4和R5。R1和R2还会将R3、R4和R5的BIER信息泛洪给A10域内的BFR，比如R11、R12和R13，以及A20域内的BFR，比如R21、R22和R23。R1和R2向A1域内的BFR发布获取的BIER信息的方法，与向A10域内的BFR和A20域内的BFR发布获取的BIER信息的方法相同，下述以R1和R2向A1域内的BFR发布获取的BIER信息的方法为例进行说明。
在图1所示的场景中，R1和R2可直接或间接从区域A10的BFR和区域A20的BFR获取作为边缘BFR的BFR-id，比如数值为11、12、13、21、22和23的BFR-id。R1向区域A1发布的BIER信息包括：数值为11、12、13、21、22和23的BFR-id。R2向区域A1发布的BIER信息包括：数值为11、12、13、21、22和23的BFR-id。其中，R1和R2可通过BFR-id range的sub-tlv发布数值为11、12、13、21、22和23的BFR-id。BFR-id range的sub-tlv可通过draft-ietf-bier-prefix-redistribute-00所定义的BIER Proxy Range sub-TLV来携带。比如：BIER Proxy Range sub-TLV可包括BFR-id＝11和range＝3，该sub-TLV表示BFR-id从11开始的3个BFR-id，即BFR-id为11、12和13这三个数值。BIER Proxy Range sub-TLV还可包括BFR-id＝21和range＝3，该sub-TLV表示BFR-id从21开始的3个BFR-id，即BFR-id为21、22和23这三个数值。当R1和R2中的一个或多个可作为BFER时，作为BFER的设备可将其自身配置的BFR-id携带在发布的BIER信息中。比如，R1可作为BFER时，R1向区域A1发布的BIER信息还包括R1被分配的有效的BFR-id。R2可作为BFER时，R2向区域A1发布的BIER信息还包括R2被分配的有效的BFR-id。在一种可能的实现方式中，R1发布BIER信息时可以使用R1的主机前缀。R2发布BIER信息时可以使用R2的主机前缀。上述主机前缀在第四版互联网协议(Internet Protocol version 4，IPv4)网络下是一个32位掩码的前缀，其信息为一个完整的IPv4地址。或者上述主机前缀在第六版互联网协议(Internet Protocol  version 6，IPv6)网络下是一个128位掩码的前缀，其信息为一个完整的IPv6地址。在另一种可能的实现方式中，R1向区域A1发布BIER信息可以使用代表R1的非主机路由前缀，例如，一个64掩码的IPv6地址作为Locator标识R1；或者draft-ietf-bier-prefix-redistribute-00使用一个聚合的路由或者默认路由来携带R1发布的BIER信息。R2向区域A1发布BIER信息可以使用代表R2的非主机路由前缀，例如一个64掩码的IPv6地址作为Locator标识R2；或者draft-ietf-bier-prefix-redistribute-00使用一个聚合的路由或者默认路由来携带R2发布的BIER信息。
图1中的R1可分别接收区域A10中的R11、R12和R13发布的自身的BFR-id，接收区域A20中的R21、R22和R23发布的自身的BFR-id，还会接收R2发布的BIER信息。以数值为11的BFR-id为例，R11将R11的IP地址作为BFR-prefix，与数值为11的BFR-id一起发布。例如RFC8401所定义的BIER-info sub-TLV(Type值为32)携带在ISIS的Type＝135、235、236和237消息中，或者RFC8444所定义的BIER Sub-TLV(Type值为9)携带在OSPFv2 Extended Prefix TLV中。上述sub-TLV可用于携带R11的IP地址和数值为11的BFR-id。R1发布的信息可表示为(BFR-prefix＝R11的IP地址，BIER-info<Sub-domain＝0，BFR-id＝11>)。R2发布的R11的BFR-id可以采用draft-ietf-bier-prefix-redistribute-00所定义的BIER Proxy Range sub-TLV中携带，该TLV还可携带数值为R2的IP地址的BFR-prefix。R2发布的信息可表示为(BFR-prefix＝2.2.2.2，BIER-info<Sub-domain＝0，BFR-id＝2>，BFR-id-range<BFR-id-range＝11 to 13,21 to 23>)；其中，2.2.2.2是R2的IP地址，BFR-id＝2是R2的有效BFR-id值。R1优先采用R11通过BIER-info TLV或BIER sub-TLV发布的信息建立到达R11的位索引路由表(bit index routing table，BIRT)表项和位索引转发表(bit index forwarding table，BIFT)表项。R1所建立的到达R11的BIRT表项和BIFT表项包括数值为11的BFR-id，下一跳均为R11的BFR-prefix，出接口均为R1连R11的接口。
按照上述方法，R1会对BFR-id＝12优先选择R12所发布的信息，建立到达BFR-id＝12的BIRT表项和BIFT表项。R1所建立的到达R12的BIRT表项和BIFT表项包括数值为12的BFR-id，下一跳均为R12的BFR-prefix，出接口为R1连R12的接口。R1所建立的到达R13、R21、R22和R23的BIRT表项和BIFT表项的方法与建立上述BIRT表项和BIFT表项的方法相同，在此不再赘述。R2建立BIRT表项和BIFT表项的方法与R1所采用的方法相同，在此不再赘述。对于区域A1内的R3、R4和R5而言，上述任一设备均会收到R1所发布的BIER信息和R2所发布的BIER信息，当R1和R2发布的BIER信息还包括R1的BFR-id时，R3、R4和R5均会根据R1发布的BFR-id＝1建立到达R1的BIRT表项和BIFT表项，建立方法与上述R1采用的方法相同，此处不再赘述。当R1和R2发布的BIER信息还包括R2的BFR-id时，R3、R4和R5均会根据R2发布的BFR-id＝2建立到达R2的BIRT表项和BIFT表项，建立方法与上述R1采用的方法相同，此处不再赘述。BIRT表项包括到达BFR-id的下一跳节点信息，可以用(BFR-id，NextHop)表示，例如某一条BIRT表项包括(BFR-id＝11,NextHop＝R1)，该BIRT表项表示到达BFR-id＝11的BFER的下一跳为R1。BIFT表项包括到达BFR-id的下一跳节点信息以及转发位掩码(Forwarding-Bit-Mask，FBM)，可以用(BFR-id,NextHop,FBM)表示，例如某一条BIFT表项包括(BFR-id＝11,NextHop＝R1,FBM＝01110000)，其中FBM中的三个1bit位可以分别对应于BFR-id为11，12和13的BFER。
对于区域A1内的R3、R4和R5而言，上述三台设备中的任一台设备会收到R1发布的BIER信息和R2发布的BIER信息。R1发布的BIER信息和R2发布的BIER信息均包括的数值为11、12、13、21、22和23的BFR-id。R3、R4或R5可根据发布数值为11、12、13、 21、22和23的BFR-id的路由和最长匹配算法来确定下一跳和出端口，所选择BIER信息的发布者并非性能最佳的设备，灵活性和转发性能有待提高。
本申请实施例提供的方法，能够解决图1中R1和R2发布了相同的BFR-id的场景中，R3、R4和R5中的一台或多台如何选择性能最佳的下一跳这一问题。本申请实施例对于R1和R2均发布区域A10内的作为BFER的设备的BFR-id，区域A1中的R3和R4采用本申请实施例提供的方法选择下一跳为例进行说明。区域A1中的其它边缘BFR，比如R5所采用的方法与R3或R4采用的方法相同，本申请实施例对此不再赘述。对于R1和R2均发布区域A20内的作为BFER的设备的BFR-id，区域A1中的边缘BFR选择下一跳的方法可参见上述R3或R4所采用的方法，本申请实施例对此不再赘述。
实施例一
图2为本申请实施例一提供的确定下一跳方法的流程示意图。图2所示的方法中，图1中的R3和R4均会接收来自R1的属性、R2的属性、R1和R2发送的BIER信息，R3或R4基于R1的属性、R2的属性、R1和R2发送的BIER信息中确定下一跳。R1的属性和R2的属性的类型相同，但数值可以相同，也可以不同。R3或R4利用下一跳发送的BIER信息生成用来转发BIER报文的表项。用来转发BIER报文的表项可以是BIFT表项和BIRT表项中的一个表项或多个表项。本申请实施例一是以R1和R2的BFR-prefix相同为例进行说明的。下面结合图1和图2，对本申请实施例一提供的确定下一跳的方法进行说明。
S201，R1和R2使用相同的BFR-prefix来发布区域A10的边缘BFR的BFR-id。
为了避免BIER转发成环，R1和R2中的任一设备均不作为BFER使用，或者任一设备均未配置有效的BFR-id，或者任一设备均未配置非0的BFR-id时，R1和R2可被配置相同的BFR-prefix。图1所示的区域A10的边缘BFR包括R11、R12和R13。本申请实施例中的相同的BFR-prefix可用地址前缀表示，该BFR-prefix可以如RFC8401或RFC8444公开的IPv4地址或IPv6地址，或者该BFR-prefix可以是IPv6地址块。该IPv6地址块可以是64掩码的地址块。R1和R2通过内部网关协议(Interior Gateway Protocol，IGP)向区域A1的R3发布的BIER信息均包括数值为11、12和13的BFR-id。其中，R1和R2还通过IGP向区域A1的R3发布各自的属性。R1的属性和R2的属性包括第一标识。该第一标识是用来标识为任播(anycast)的BFR-prefix。本申请实施例中R1发布的BIER信息可为第一BIER信息，R2发布的BIER信息可为第二BIER信息。其中，第一BIER信息或第二BIER信息包括的BFR-id可采用RFC8401或RFC8444中提及的方式发送，或者携带在draft-ietf-bier-prefix-redistribute-00的BFR-id range中进行发送。R1和R2的BFR-prefix可通过Adv-bfr-prefix字段携带发送。R1和R2的属性包括的第一标识可通过Adv-anycast-flag字段携带发送。在一种可能的实现方式中，R1的属性还可包括R1的节点标识和用于标识优先级的第二标识中的一个或多个。R2的属性还可包括R2的节点标识和用于标识优先级的第三标识中的一个或多个。本申请实施例中的节点标识在中间系统到中间系统(intermediate system to intermediate system，ISIS)协议中是系统标识(system-id)，在开放最短路径优先(Open Shortest Path First，OSPF)协议中是路由标识(router-id)。上述节点标识可携带在Adv-router-id字段中进行发送。上述第二标识和上述第三标识可携带在Adv-admin-tag字段中进行发送。
S202，R3根据接收到的R1的属性和R2的属性，判断是否告警，如果不进行告警，则执行S203。
举例说明，基于图1的场景，R3收到来自R1的属性、来自R2的属性、来自R1的第一BIER信息和来自R2的第二BIER信息。R3收到的来自R2的第二BIER信息可来自于R3与 R1通信的接口和R3与R4通信的接口中的一个接口或多个接口。R3基于第一BIER信息和第二BIER信息确定R1和R2均可作为到达区域A10包括的边缘BFR的中间BFR。R3可判断R1的属性和R2的属性中是否存在第一标识。如果R1的属性和R2的属性均不包括第一标识，则R3确定配置错误，输出告警。如果R1的属性和R2的属性中的至少一个包括第一标识，则R3法确定配置正确，执行S203。其中，输出告警的方式可通过网络配置协议(Network Configuration Protocol，NETCONF)向网管设备或者其他管理设备输出告警。
S203，R3确定到达区域A10包括的边缘BFR的下一跳。
在一种可能的实现方式中，当R1的属性或R2的属性包括第一标识，则R3将下一跳确定为携带有第一标识的属性对应的设备，比如：R1发布的属性包括第一标识，而R2发布的属性不包括第一标识，则R3将到达区域A10的边缘BFR的下一跳设为R1，则R3获取的与区域A10的边缘BFR对应的BIRT表项或BIFT表项所包括的下一跳为R1，出接口为R3与R1通信的接口。R2发布的属性包括第一标识，而R1发布的属性不包括第一标识，则R3将到达区域A10的边缘BFR的下一跳设备R2，则R3获取的与区域A10的边缘BFR对应的BIRT表项或BIFT表项所包括的下一跳为R2，出接口为R3上能够与R2通信的接口。在图1所示的场景中，R3上能够与R2通信的接口包括了R3与R1通信的接口和R3与R4通信的接口，具体可参见S202的内容。R3在确定能够与R2通信的接口时，可根据链路开销(cost)或者链路状态来选择能够与R2通信的接口。其中，BIRT表项和BIFR表项可采用以下示例：
BIRT表项可采用以下方式：
(BFR-id＝11,NextHop＝R4)
(BFR-id＝12,NextHop＝R4)
(BFR-id＝13,NextHop＝R4)
BIFT表项可采用以下方式：
(BFR-id＝11,NextHop＝R4,FBM＝01110000)
(BFR-id＝12,NextHop＝R4,FBM＝01110000)
(BFR-id＝13,NextHop＝R4,FBM＝01110000)
在另一种可能的实现方式中，当R1的属性和R2的属性均包括第一标识，则R3可采用以下几种方式来确定下一跳：
方式一，R1的属性包括R1的节点标识，R2的属性包括R2的节点标识，在R1的节点标识和R2的节点标识不同时，R3可根据第一策略、R1的节点标识和R2的节点标识，从R1和R2中确定出作为下一跳的设备。第一策略可以是节点标识较大的设备作为下一跳，或者节点标识较小的设备作为下一跳。
方式二，R1的属性包括R1的节点标识和第二标识，R2的属性包括R2的节点标识和第三标识，在R1的节点标识和R2的节点标识相同时，则R3可根据第二策略、第二标识和第三标识，从R1和R2中确定出作为下一跳的设备。第二策略可以是第二标识和第三标识中优先级较大的设备作为下一跳，或者第二策略可以是第二标识和第三标识中优先级较小的设备作为下一跳。
方式三，R1的属性包括第二标识，R2的属性包括第三标识，第二标识所标识的优先级与第三标识所标识的优先级不同，R3可根据第二策略、第二标识和第三标识，从R1和R2中确定出作为下一跳的设备。
方式四，R1的属性包括R1的节点标识和第二标识，R2的属性包括R2的节点标识和第三标识，在第二标识所标识的优先级和第三标识所标识的优先级相同时，则R3可根据第一 策略、R1的节点标识和R2的节点标识，从R1和R2中确定出作为下一跳的设备。第一策略可以是节点标识较大的设备作为下一跳，或者节点标识较小的设备作为下一跳。
方式五，R1的属性包括R1的节点标识和第二标识，R2的属性包括R2的节点标识和第三标识，当R1的节点标识和R2的节点标识均相同，且第二标识所标识的优先级和第三标识所标识的优先级相同时，R3可以从R1和R2中选择任一设备作为下一跳。
可选地，R3在确定了下一跳之后，可获取用于转发BIER报文的表项。用于转发BIER报文的表项包括的下一跳为R3所确定的下一跳。
S204,R4根据接收到的R1的属性和R2的属性，判断是否告警，如果不进行告警，则执行S205。
举例说明，基于图1的场景，R4收到来自R1的属性、来自R2的属性、来自R1的第一BIER信息和来自R2的第二BIER信息。R4基于第一BIER信息和第二BIER信息确定R1和R2均可作为到达区域A10包括的边缘BFR的中间BFR。R4可判断R1的属性和R2的属性中是否存在第一标识。如果R1的属性和R2的属性均不存在第一标识，则R4确定配置错误，输出告警。如果R1的属性和R2的属性中的至少一个包括第一标识，则R4确定配置正确，执行S205。其中，输出告警的方式可参见R3所采用的方式。
S205，R4确定到达区域A10包括的边缘BFR的下一跳。
在一种可能的实现方式中，当R1的属性或R2的属性包括第一标识，则R4将下一跳确定为携带有第一标识的属性对应的设备，比如：R1发布的R1的属性包括第一标识，而R2发布的R2的属性不包括第一标识，则R4将到达区域A10的边缘BFR的下一跳设为R1，则R4获取的与区域A10的边缘BFR对应的BIRT表项或BIFT表项所包括的下一跳为R1，出接口为R4与R1通信的接口。R2发布的R2的属性包括第一标识，而R1发布的R1的属性不包括第一标识，则R4将到达区域A10的边缘BFR的下一跳设备R2，则R4获取的与区域A10的边缘BFR对应的BIRT表项或BIFT表项所包括的下一跳为R2，出接口为R4与R2通信的接口。其中，R4确定下一跳的方法可参见S203中R3确定下一跳所采用的方式一至方式五中的任一种方式。
可选地，R4在确定了下一跳之后，可获取用于转发BIER报文的表项。用于转发BIER报文的表项包括的下一跳为R4所确定的下一跳。
本申请实施例提供的方法中，R3或R4在向区域A10发送BEIR组播报文时，可利用上述获取的用于转发BIER报文的表项，将组播报文发送给下一跳。而到达区域A10的边缘BFR的下一跳的确定方法较为灵活，且能够对于配置错误的情况提出告警。当采用优先级比较的方法时，可根据第二策略对性能较佳的设备的优先级进行设置，以便性能较佳的节点能够被确定为下一跳。当采用节点标识比较的方法时，可根据第一策略对性能较佳的设备的节点标识进行设置，以便性能较佳的节点能够被确定为下一跳。这样，本申请实施例提供的方法还能进一步基于性能较佳的下一跳，满足组播业务的性能需求，提高转发效率。
实施例二
图3为本申请实施例二提供的确定下一跳方法的流程示意图。图3所示的方法中，图1中的R3和R4均会接收来自R1的属性、来自R2的属性、R1和R2发送的BIER信息，R3或R4基于R1的属性和R2的属性确定下一跳。R3或R4利用下一跳发送的BIER信息生成用来转发BIER报文的表项。用来转发BIER报文的表项可以是BIFT表项和BIRT表项中的一个表项或多个表项。本申请实施例二是以R1和R2的BFR-prefix不同为例进行说明的。下面结合图1和图3，对本申请实施例二提供的确定下一跳方法进行说明。
S301，R1和R2使用不同的BFR-prefix来发布区域A10的边缘BFR的BFR-id。
举例说明，R1和R2可被配置不同的BFR-prefix，R1被配置的BFR-prefix可为第一地址，R2被配置的BFR-prefix可为第二地址。实施例二的BFR-prefix的含义与实施例一相同，在此不再赘述。图1所示的区域A10的边缘BFR包括R11、R12和R13。R1通过IGP向区域A1的R3发布的第一BIER信息包括数值为11、12和13的BFR-id。R1通过IGP向区域A1的R3发布的R1的属性包括第一地址。R2通过IGP向区域A1的R3发布的第二BIER信息包括数值为11、12和13的BFR-id。R2通过IGP向区域A1的R3发布的R2的属性包括第二地址。其中，第一BIER信息或第二BIER信息包括的BFR-id可采用RFC8401或RFC8444公开的方式发送，或者携带在draft-ietf-bier-prefix-redistribute-00的BFR-id range中进行发送。BFR-prefix可通过Adv-bfr-prefix字段携带发送。
在一种可能的实现方式中，R1的属性还可包括R1的节点标识和用于标识优先级的第二标识中的一个或多个。R1的属性还可包括R2的节点标识和用于标识优先级的第三标识中的一个或多个。实施例二中的节点标识的含义可参见实施例一的相应内容，在此不再赘述。实施二中的用于标识优先级的标识的含义可参见实施例一的相应内容，在此不再赘述。上述节点标识可携带在Adv-router-id字段中进行发送。上述第二标识和上述第三标识可携带在Adv-admin-tag字段中进行发送。
S302，R3根据接收到的R1的属性和R2的属性，确定下一跳。
举例说明，基于图1的场景，R3收到来自R1的属性、来自R2的属性、来自R1的第一BIER信息和来自R2的第二BIER信息。R3收到的来自R2的第二BIER信息可来自于R3与R1通信的接口和R3与R4通信的接口中的一个接口或多个接口。R3基于第一BIER信息和第二BIER信息，确定到达区域A10包括的边缘BFR所经过的中间BFR包括R1和R2。R3可基于R1的属性和R2的属性确定下一跳。可选地，R3在确定下一跳之后，将下一跳写入与区域A10的边缘BFR对应的BIRT表项或BIFT表项中。当R3确定下一跳是R2时，可采用实施例一中的方法确定能够与R2通信的接口，在此不再赘述。
其中，R3可采用下述任一种方式或几种方式的组合，从R1和R2中确定作为下一跳的设备，具体如下：
方式一，R1的属性包括R1的节点标识，R2的属性包括R2的节点标识，在R1的节点标识和R2的节点标识不同时，R3可根据第一策略、R1的节点标识和R2的节点标识，从R1和R2中确定出作为下一跳的设备。第一策略可以是节点标识较大的设备作为下一跳，或者节点标识较小的设备作为下一跳。
方式二，R1的属性包括R1的节点标识和第二标识，R2的属性包括R2的节点标识和第三标识，在R1的节点标识和R2的节点标识相同时，则R3可根据第二策略、第二标识和第三标识，从R1和R2中确定出作为下一跳的设备。第二策略可以是第二标识和第三标识中优先级较大的设备作为下一跳，或者第二策略可以是第二标识和第三标识中优先级较小的设备作为下一跳。
方式三，R1的属性包括第二标识，R2的属性包括第三标识，第二标识所标识的优先级与第三标识所标识的优先级不同，R3可根据第二策略、第二标识和第三标识，从R1和R2中确定出作为下一跳的设备。
方式四，R1的属性包括R1的节点标识和第二标识，R2的属性包括R2的节点标识和第三标识，在第二标识所标识的优先级和第三标识所标识的优先级相同时，则R3可根据第一策略、R1的节点标识和R2的节点标识，从R1和R2中确定出作为下一跳的设备。
方式五，R1的属性包括R1的节点标识和第二标识，R2的属性包括R2的节点标识和第三标识，当R1的节点标识和R2的节点标识均相同，且第二标识所标识的优先级和第三标识所标识的优先级相同时，R3可以从R1和R2中确定任一设备作为下一跳。
方式六，R1的属性包括R1到达R3的cost值，R2的属性包括R2到达R3的cost值，R3可根据第四策略、R1到达R3的cost值和R2到达R3的cost值，从R1和R2中确定出作为下一跳的设备。其中，R2到达R3的cost值和R1到达R3的cost值。第四策略为选择cost值较小的设备作为下一跳，或者选择cost值较大的设备作为下一跳。当R3到达R1的cost值和R3到达R2的cost值相同时，可采用上述方式一至方式五中的一种或几种方式的组合来确定下一跳。对于方式六而言，当R1到达R3的cost值和2到达R3的cost值不同时，第一BIER信息可无需携带第二标识，第二BIER信息可无需携带第三标识。当R1到达R3的cost值和2到达R3的cost值不同时，即便R1的属性包括R1的节点标识，R2的属性包括R2的节点标识，R3可不对节点标识进行识别和比较，能够降低对R3的性能需求和提高表项获取效率。
方式七，R1的属性包括R1的BFR-prefix，R2的属性包括R2的BFR-prefix，R3可根据第五策略、R1的BFR-prefix和R2的BFR-prefix，从R1和R2中确定出作为下一跳的设备。第五策略为选择BFR-prefix较小的设备作为下一跳，或者选择BFR-prefix较大的设备作为下一跳。对于方式七而言，R1的属性可无需携带第二标识，R2的属性可无需携带第三标识；即便R1的属性包括R1的节点标识，R2的属性包括R2的节点标识，R3可不对节点标识进行识别和比较。
举例说明，当R3采用方式六无法确定下一跳时，可采用方式七确定下一跳。或者当R3采用方式六无法确定下一跳时，可采用方式一确定下一跳。或者当R3采用方式六和方式一无法确定下一跳时，可采用方式二确定下一跳。或者当R3采用方式六、方式一和方式二无法确定下一跳时，可采用方式七或方式五确定下一跳。或者当R3采用方式六无法确定下一跳时，可采用方式三确定下一跳。或者当R3采用方式六和方式三无法确定下一跳时，可采用方式四确定下一跳。或者当R3采用方式六、方式三和方式四无法确定下一跳是，可采用方式七或方式五确定下一跳。上述是对上述方式的组合进行举例说明，还可根据上述多种方式进行其它组合，本申请实施例对此不进行限定。
S302，R4根据接收到的R1的属性和R2的属性，确定下一跳。
举例说明，基于图1的场景，R4收到来自R1的第一BIER信息和来自R2的第二BIER信息，R4还接收到R1的属性和R2的属性。R4基于第一BIER信息和第二BIER信息，确定到达区域A10包括的边缘BFR所经过的中间BFR包括R1和R2。R4可采用与R3所采用的方法相同的方法，来确定下一跳，在此不再赘述。可选地，R4在确定下一跳之后，将下一跳写入与区域A10的边缘BFR对应的BIRT表项或BIFT表项中。
本申请实施例提供的方法中，R3或R4在向区域A10发送组播报文时，可利用上述获取的用于转发BIER报文的表项，将组播报文发送给下一跳。而到达区域A10的边缘BFR的下一跳的确定方法较为灵活，且能够对于配置错误的情况提出告警。当采用优先级比较的方法时，可根据第二策略对性能较佳的设备的优先级进行设置，以便性能较佳的节点能够被确定为下一跳。当采用节点标识比较的方法时，可根据第一策略对性能较佳的设备的节点标识进行设置，以便性能较佳的节点能够被确定为下一跳。这样，本申请实施例提供的方法还能进一步基于性能较佳的下一跳，满足组播业务的性能需求，提高转发效率。
实施例三
实施例三是在配置adv-admin-tag后，根据多个消息中adv-admin-tag的大小确定某个BFR-id的BIRT和BIFT。下面结合图1所示的场景，对相关设备的配置及处理方法进行说明：
1、在R1上进行的配置：
#接口1_to_2和1_to_3和1_to_4运行在isis的进程1上；
Isis 1
Interface 1_to_3
Interface 1_to_2
Interface 1_to_4
Interface loopback1 2001:1:1:1::10/128
#接口1_to_11和1_to_21运行在isis的进程2上；
Isis 2
Interface 1_to_11
Interface 1_to_21
Interface loopback2 2001:1:1:1::20/128
#BIER的配置
Bier
--Sub-domain 1
----BFR-id 1
----bfr-prefix interface loopback1[advertise-policy ply_1]
----bfr-prefix interface loopback2[advertise-policy ply_2]
##定义将要发布到isis进程1的BFR-id范围及策略；
advertise-policy ply_1
--import BFR-id-range 11 to 13
--import BFR-id-range 21 to 23
##定义将要发布到isis进程2的BFR-id范围及策略；
advertise-policy ply_2
--import BFR-id-range 3 to 5
举例说明，R1上向isis 1进程(对应区域A1)发布BFR-id为11、12、13、21、22和23的第一BIER信息，使用的是BFR-id Range sub-TLV。R1还会向isis 1进程发布本节点的BFR-id为1的信息，使用的是RFC8401所定义的BIER-info sub-TLV。R1向isis 1进程发布的以上信息使用loopback1的IP地址2001:1:1:1::10作为BFR-prefix。图4是一个R1所发送的IS-IS消息携带一个BFR-id Range sub-TLV的示例，他们都是作为ISIS Prefix TLV(TLV类型为135、235、236和237中的一种)的子TLV存在，其中的BFR-id range sub-TLV可以是对draft-ietf-bier-prefix-redistribute-00中所定义的BIER proxy range sub-TLV。
图4所示的报文格式可以是R1所发送的IS-IS消息携带一个BFR-id Range sub-TLV的另一个示例，其中，BFR-id Range sub-TLV是作为ISIS Prefix TLV(TLV类型为135、235、236和237中的一种)的子TLV存在。路由器R1发布的消息中BFR-id Range sub-TLV包含BFR-id range为11、12、13、21、22和23；其中的BFR-id range sub-TLV可以是对draft-ietf-bier-prefix-redistribute-00中所定义的BIER proxy range sub-TLV修改而来。同理，R1向isis 2进程(对应区域A10和A20)发布BFR-id为3、4或5的信息，使用的是BFR-id Range sub-TLV。R1还会向isis 2进程发布本节点的BFR-id＝1信息，使用的是RFC8401所定义的 BIER-info sub-TLV。R1向isis 2进程发布的以上信息使用loopback2的IP地址2001:1:1:1::20作为BFR-prefix。
2、在R2上做如下配置：
#接口2_to_4和2_to_1运行在isis的进程1上；
Isis 1
Interface 2_to_4
Interface 2_to_1
Interface loopback1 2001:2:2:2::10/128
#接口1_to_13和1_to_23运行在isis的进程2上；
Isis 2
Interface 2_to_13
Interface 2_to_23
Interface loopback2 2001:2:2:2::20/128
#BIER的配置；
Bier
--Sub-domain 1
----BFR-id 1
----bfr-prefix interface loopback1[advertise-policy ply_1]
----bfr-prefix interface loopback2[advertise-policy ply_2]
##定义将要发布到isis进程1的BFR-id范围及策略；
advertise-policy ply_1
--import BFR-id-range 11 to 13
--import BFR-id-range 21 to 23
##定义将要发布到isis进程2的BFR-id范围及策略；
advertise-policy ply_2
--import BFR-id-range 3 to 5
举例说明，R2上向isis 1进程(对应区域A1)发布BFR-id为11、12、13、21、22和23，使用的是BFR-id Range sub-TLV。R2还会向isis 1进程发布本节点的BFR-id＝2信息，使用的是RFC8401所定义的BIER-info sub-TLV。R2向isis 1进程发布的以上信息使用loopback1的IP地址2001:2:2:2::10作为BFR-prefix。同理，R2向isis 2进程(对应区域A10和A20)发布BFR-id为3、4和5的信息，使用的是BFR-id Range sub-TLV。R2还会向isis 2进程发布本节点的BFR-id＝2信息，使用的是RFC8401所定义的BIER-info sub-TLV。R2向isis 2进程发布的以上信息使用loopback2的IP地址2001:2:2:2::20作为BFR-prefix。R2所采用的报文格式可以是图4所示的报文格式，在此不再赘述。
3、区域A0内的路由器建立到BFR-id为11、12、13、21、22和23的下一跳路的方法可参考实施例一或实施例二的方法，在此不再赘述。
实施例四
本实施例四说明通过配置adv-admin-tag的方式并根据多个消息中adv-admin-tag的大小确定某个BFR-id的BIRR和BIFT包括的下一跳。下面结合图1所示的场景对实施例四的配置进行说明。
1、在R1上做如下配置：
#接口1_to_2和1_to_3和1_to_4运行在isis的进程1上；
Isis 1
Interface 1_to_3
Interface 1_to_2
Interface 1_to_4
Interface loopback1 2001:1:1:1::10/128
#接口1_to_11和1_to_21运行在isis的进程2上；
Isis 2
Interface 1_to_11
Interface 1_to_21
Interface loopback2 2001:1:1:1::20/128
#BIER的配置
Bier
--Sub-domain 1
----BFR-id 1
----bfr-prefix interface loopback1[advertise-policy ply_1]
----bfr-prefix interface loopback2[advertise-policy ply_2]
##定义将要发布到isis进程1的BFR-id范围及策略；
advertise-policy ply_1
--apply Administrative-tag 1
--import BFR-id-range 11 to 13
--import BFR-id-range 21 to 23
##定义将要发布到isis进程2的BFR-id范围及策略；
advertise-policy ply_2
--apply administrative-tag 1
--import BFR-id-range 3 to 5
举例说明，R1上向isis 1进程(对应区域A1)发布BFR-id为11、12、13、21、22和23，并携带有值为1的administrative-tag，使用的是BFR-id Range sub-TLV。R1还会向isis 1进程发布本节点的BFR-id＝1信息，使用的是RFC8401所定义的BIER-info sub-TLV。R1向isis 1进程发布的以上信息使用loopback1的IP地址2001:1:1:1::10作为BFR-prefix。图5是一个R1所发送的IS-IS消息携带一个administrative-tag、一个BFR-id Range sub-TLV的示例，上述参数都是作为ISIS Prefix TLV(TLV类型为135、235、236和237中的一种)的子TLV存在。其中的administrative-tag值用来作为BFR-id Range sub-TLV所包含的BFR-id的优选区分，例如R1发布的消息中BFR-id Range sub-TLV包含BFR-id为11、12、13、21、22和23，Administrative-tag值为1。BFR-id range sub-TLV可以是对draft-ietf-bier-prefix-redistribute-00中所定义的BIER proxy range sub-TLV。
图5是一个R1所发送的IS-IS消息携带一个administrative-tag、一个BFR-id Range sub-TLV的另一个示例。其中，BFR-id Range sub-TLV是作为ISIS Prefix TLV(TLV类型为135、235、236和237中的一种)的子TLV存在，而administrative-tag值则定义在BFR-id Range sub-TLV中。R1发布的消息中BFR-id Range sub-TLV包含BFR-id range为11、12、13、21、22和23，Administrative-tag值为1。其中一个ISIS Prefix TLV下包含两个BFR-id Range  sub-TLV。每个BFR-id Range sub-TLV中包含一个administrative Tag及一个(BFR-id,BFR-id range)元组。其中的BFR-id range sub-TLV可以是对draft-ietf-bier-prefix-redistribute-00中所定义的BIER proxy range sub-TLV修改而来。也可以一个ISIS Prefix TLV下可以有一个BFR-id Range sub-TLV、该BFR-id Range sub-TLV中包含一个Administrative Tag及两个(BFR-id,BFR-id range)元组，如图6所示。
同理，R1向isis 2进程(对应区域A10和A20)发布BFR-id为3、4或5的信息并携带有值为1的administrative-tag，使用的是BFR-id Range sub-TLV。R1还会向isis 2进程发布本节点的BFR-id＝1信息，使用的是RFC8401所定义的BIER-info sub-TLV。R1向isis 2进程发布的以上信息使用loopback2的IP地址2001:1:1:1::20作为BFR-prefix。
2、在R2上做如下配置：
#接口2_to_4和2_to_1运行在isis的进程1上；
Isis 1
Interface 2_to_4
Interface 2_to_1
Interface loopback1 2001:2:2:2::10/128
#接口1_to_13和1_to_23运行在isis的进程2上；
Isis 2
Interface 2_to_13
Interface 2_to_23
Interface loopback2 2001:2:2:2::20/128
#BIER的配置；
Bier
--Sub-domain 1
----BFR-id 1
----bfr-prefix interface loopback1[advertise-policy ply_1]
----bfr-prefix interface loopback2[advertise-policy ply_2]
##定义将要发布到isis进程1的BFR-id范围及策略；
advertise-policy ply_1
--apply administrative-tag 2
--import BFR-id-range 11 to 13
--import BFR-id-range 21 to 23
##定义将要发布到isis进程2的BFR-id范围及策略；
advertise-policy ply_2
--apply administrative-tag 2
--import BFR-id-range 3 to 5
举例说明，R2上向isis 1进程(对应区域A1)发布为11、12、13、21、22和23，并携带有值为2的administrative-tag，使用的是BFR-id Range sub-TLV。R2还会向isis 1进程发布本节点的BFR-id＝2信息，使用的是RFC8401所定义的BIER-info sub-TLV。R2向isis 1进程发布的以上信息使用loopback1的IP地址2001:2:2:2::10作为BFR-prefix。同理，R2向isis 2进程(对应区域A10和A20)发布BFR-id为3、4和5的信息并携带有值为2的administrative-tag，使用的是BFR-id Range sub-TLV。R2还会向isis 2进程发布本节点的 BFR-id＝2信息，使用的是RFC8401所定义的BIER-info sub-TLV。R2向isis 2进程发布的以上信息使用loopback2的IP地址2001:2:2:2::20作为BFR-prefix。R2也可采用图5或图6的报文格式来发布第二BIER信息和R2的属性，在此不再赘述。
3、区域A0内的路由器建立到BFR-id为11、12、13、21、22和23的下一跳路由及转发信息。具体可参见实施例一或实施例二中的相应内容，在此不再赘述。
实施例五
实施例五通过配置anycast BFR-prefix并配置相同的BIER封装相关信息的方式，根据到该BFR-prefix的路由来确定某个BFR-id的BIRT和BIFT。在本实施例中，R1和R2都没有配置有效的BFR-id值(在BIER info sub-TLV中填写的BFR-id值是一个无效值0)。下面结合图1所示的场景对配置方法进行说明。
1、在R1上做如下配置：
#接口1_to_2和1_to_3和1_to_4运行在isis的进程1上；
Isis 1
Interface 1_to_3
Interface 1_to_2
Interface 1_to_4
Interface loopback1 2001:1:1:1::AAAA anycast
#接口1_to_11和1_to_21运行在isis的进程2上；
Isis 2
Interface 1_to_11
Interface 1_to_21
Interface loopback2 2001:1:1:1::BBBB anycast
#BIER的配置
Bier
--Sub-domain 1
----end-bier sid 2001:1:1:1::AB37 anycast
----bift-id 200001 anycast
----bfr-prefix interface loopback1[advertise-policy ply_1]
----bfr-prefix interface loopback2[advertise-policy ply_2]
##定义将要发布到isis进程1的BFR-id范围及策略；
advertise-policy ply_1
--apply anycast-flag
--import BFR-id-range 11 to 13
--import BFR-id-range 21 to 23
##定义将要发布到isis进程2的BFR-id范围及策略；
advertise-policy ply_2
--apply anycast-flag
--import BFR-id-range 3 to 5
其中的一些配置含义如下：
Interface loopback1 2001:1:1:1::AAAA anycast表示所配置的Ipv6地址是一个anycast地址，用作BIER信息发布的BFR-prefix。
Interface loopback2 2001:1:1:1::BBBB anycast表示所配置的Ipv6地址是一个anycast地址，用作BIER信息发布的BFR-prefix。
end-bier sid 2001:1:1:1::AB37 anycast表示用于转发BIER报文时的封装信息是一个Anycast的信息，本例中的end-bier是一种用于BIERv6封装时的BIER报文封装信息。
bift-id 200001 anycast表示用于转发BIER报文时的封装信息是一个Anycast的信息，本例中的bift-id是一种用于BIERv6/BIER-MPLS封装时的BIER报文封装信息，当用在BIER-MPLS封装时，该bift-id值是一个MPLS标签，为了支持本方案中的Anycast方法，需要手工配置R1和R2上使用相同的MPLS标签，也就是配置相同的bift-id值。当用在Non-MPLS的封装或BIERv6封装时，bift-id可以是一个根据BIER的Sub-domain-id、BitStringLength ID(BSL)、Set Identifier(SI)而自动生成的值，R1和R2上根据相同的规则生成的值相同，因此可以不需要额外配置。
apply anycast-flag表示发布BIER信息时携带anycast标记。
举例说明，R1上向isis 1进程(对应区域A1)发布BFR-id为11、12、13、21、22和23，并携带有anycast标记，使用的是BFR-id Range sub-TLV；R1还会向isis 1进程发布本节点的BFR-id＝0信息，使用的是RFC8401所定义的BIER-info sub-TLV；R1向isis1进程发布的以上信息使用loopback1的IP地址2001:1:1:1::AAAA作为BFR-prefix。图7是一个R1所发送的IS-IS消息携带Anycast标记、一个BFR-id Range sub-TLV的示例，都是作为ISIS Prefix TLV(TLV类型为135、235、236和237中的一种)的子TLV存在，如图7所示。其中，携带Anycast标记的是使用一个由draft-ietf-lsr-isis-srv6-extensions-11基于RFC7794的Prefix Attribute Flags sub-TLV所定义的Anycast标记位(sub-TLV的标记位字段的第4个bit)，该标记位用在本方案中、作为BIER信息发布及相应建立BIER路由和BIER转发信息的方法。
2、在R2上做如下配置：
#接口1_to_2和1_to_3和1_to_4运行在isis的进程1上；
Isis 1
Interface 2_to_4
Interface 2_to_1
Interface loopback1 2001:1:1:1::AAAA anycast
#接口1_to_11和1_to_21运行在isis的进程2上；
Isis 2
Interface 2_to_13
Interface 2_to_23
Interface loopback2 2001:1:1:1::BBBB anycast
#BIER的配置
Bier
--Sub-domain 1
----end-bier sid 2001:1:1:1::AB37 anycast
----bift-id 200001 anycast
----bfr-prefix interface loopback1[advertise-policy ply_1]
----bfr-prefix interface loopback2[advertise-policy ply_2]
##定义将要发布到isis进程1的BFR-id范围及策略；
advertise-policy ply_1
--apply anycast-flag
--import BFR-id-range 11 to 13
--import BFR-id-range 21 to 23
##定义将要发布到isis进程2的BFR-id范围及策略；
advertise-policy ply_2
--apply anycast-flag
--import BFR-id-range 3 to 5
相关配置的含义和R1类似，不再赘述。
相应的，R2上向isis 1进程(对应区域A1)发布BFR-id11、12、13、21、22和23，并携带有anycast标记，使用的是BFR-id Range sub-TLV；R2还会向isis 1进程发布本节点的BFR-id＝0信息，使用的是RFC8401所定义的BIER-info sub-TLV；R2向isis 1进程发布的以上信息使用loopback1的IP地址2001:1:1:1::AAAA作为BFR-prefix，这个BFR-prefix和R1所使用的BFR-prefix相同。R3、R4和R5收到以上R1和R2发布的信息，对于BFR-id＝11而言，R1和R2使用的是相同的BFR-prefix发布并且携带有anycast标记，那么R3、R4和R5都对BFR-id＝11按如下方式建立转发表：到BFR-prefix＝2001:1:1:1::AAAA的下一跳作为BFR-id＝11的路由表和转发表的下一跳。
图8为本申请实施例提供的一种确定下一跳的装置。装置800可设置于上述实施例一至实施例五中任一实施例的区域A1中除R1和R2的边缘BFR，比如R3、R4或R5。本申请是实例提及的第一设备可以是上述实施例一至实施例五中任一实施例的R1，第二设备可以是上述实施例一至实施例五中任一实施例的R2。装置800设于基于位索引转发路由BIER域，包括：获取单元801和确定单元802。
举例说明，获取单元801用于获取第一设备的第一BIER信息、所述第一设备的属性、第二设备的第二BIER信息和所述第二设备的属性，所述第一BIER信息包括子域中的边缘位转发路由器BFR的位转发路由器标识BFR-id，所述第二BIER信息包括所述子域中的所述边缘BFR的所述BFR-id。确定单元802用于根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳。
在一种可能的实现方式中，所述第一设备的属性和所述第二设备的属性包括第一标识，所述第一标识用于标识anycast的BFR前缀，所述装置还包括：识别单元。识别单元用于在所述第一BIER信息和所述第二BIER信息相同，且所述第一设备的属性和所述第二设备的属性包括第一标识时，执行确定到达所述子域的所述BFR的下一跳。
在一种可能的实现方式中，所述第一设备的属性或所述第二设备的属性包括第一标识，所述第一标识用于标识anycast的BFR前缀，所述确定单元802具体用于在所述第一BIER信息和所述第二BIER信息相同时，将属性包括所述第一标识的设备确定为下一跳。
在一种可能的实现方式中，所述装置还包括：输出单元。输出单元用于确在所述第一BFR信息和所述第二BIER信息相同，所述第一设备的属性和所述第二设备的属性均不包括第一标识时，输出告警。
在一种可能的实现方式中，所述第一设备的属性还包括所述第一设备的节点标识，所述第二设备的属性包括所述第二设备的节点标识，所述确定单元802具体用于：在所述第一BIER信息与所述第二BIER信息相同时，基于第一策略、所述第一设备的节点标识和所述第二设备的节点标识，确定所述第一设备和第二设备中的一个设备作为下一跳，所述第一策略包括 将节点标识较大的设备作为下一跳或者将节点标识较小的设备作为下一跳。
在一种可能的实现方式中，所述第一设备的属性还包括第二标识，所述第二设备的属性还包括第三标识，所述第二标识用于标识所述第一设备的优先级，所述第三标识用于标识所述第二设备的优先级，所述确定单元802具体用于：在所述第一BIER信息与所述第二BIER信息相同时，基于第二策略、所述第二标识和所述第三标识，确定所述第一设备和所述第二设备中的一个设备作为下一跳，所述第二策略包括将优先级较大的设备作为下一跳或者将优先级较小的设备作为下一跳。
在一种可能的实现方式中，所述第一设备的属性包括所述第一设备的BFR前缀，所述第二设备的属性包括所述第二设备的BFR前缀，所述第一设备的BFR前缀与所述第二设备的BFR前缀不同，所述确定单元802具体用于：在所述第一BIER信息和所述第二BIER信息相同时，根据第三策略、第一链路的开销cost值和第二链路的cost值，确定所述第一设备和所述第二设备中的一个设备作为下一跳，所述第三策略包括将cost值较小的链路对端的设备作为下一跳或者将cost值较大的链路对端的设备作为下一跳，所述第一链路为所述第三设备到达所述第一设备的链路，所述第二链路为所述第三设备到达所述第二设备的链路。
在一种可能的实现方式中，所述第一设备的属性包括所述第一设备的BFR前缀，所述第二设备的属性包括所述第二设备的BFR前缀，所述第一设备的BFR前缀与所述第二设备的BFR前缀不同，所述确定单元802具体用于：在所述第一BIER信息和所述第二BIER信息相同时，根据第四策略、所述第一设备的BFR前缀和所述第二设备的BFR前缀，确定所述第一设备和所述第二设备中的一个设备作为下一跳，所述第四策略包括将BFR前缀较小的设备作为下一跳或者将BFR前缀较大的设备作为下一跳。
在一种可能的实现方式中，所述第一设备的属性包括所述第一设备的BFR前缀和所述第一设备的节点标识，所述第二设备的属性包括所述第二设备的BFR前缀和所述第二设备的节点标识，所述第一设备的BFR前缀与所述第二设备的BFR前缀不同，所述确定单元802具体用于：在所述第一BIER信息和所述第二BIER信息相同时，根据第一策略、所述第一设备的节点标识和所述第二节点的节点标识，确定第一设备和第二设备中的一个设备作为下一跳，所述第一策略包括将节点标识较大的设备作为下一跳或者将节点标识较小的设备作为下一跳。
在一种可能的实现方式中，所述第一设备的属性包括所述第一设备的BFR前缀和第二标识，所述第二设备的属性包括所述第二设备的BFR前缀和第三标识，所述第二标识用于标识所述第一设备的优先级，所述第三标识用于标识所述第二设备的优先级，所述第一设备的BFR前缀与所述第二设备的BFR前缀不同，所述确定单元802具体用于：在所述第一BIER信息和所述第二BIER信息相同时，根据第二策略、所述第二标识和所述第三标识，确定第一设备和第二设备中的一个设备作为下一跳，所述第二策略包括将优先级较大的设备作为下一跳或者将优先级较小的设备作为下一跳。
图9为本申请实施例提供的确定下一跳的装置的结构示意图。图10对应的实施例提供的确定下一跳的装置900可以是图8对应的实施例提供的确定下一跳的装置800。图9对应的实施例提供的确定下一跳的装置900是从硬件结构的角度进行的描述。确定下一跳的装置900包括处理器901、存储器902、通信总线904和通信接口903。所述处理器901、所述存储器902和所述通信接口903通过通信总线904连接。所述存储器902用于存储程序。当装置900设置于实施例一至实施例五中任一实施例提及的R3或R4时，所述处理器901根据从所述存储器902中读取的程序所包括的可执行指令，执行上述实施例一至实施例五中任一实施例R3 或R4执行的方法。
本申请实施例提供了一种系统，所述系统包括确定下一跳的装置800。确定下一跳的装置800可用于执行实施例一至实施例五中任一实施例提及的R3或R4所执行的方法。
本申请实施例提供了一种芯片。所述芯片可包括图9所示的存储器901和处理器901。所述存储器902用于存储计算机指令。所述处理器901用于从所述存储器902中调用并运行所述计算机指令，以执行实施例一至实施例五中任一实施例提及的R3或R4所执行的方法。本申请实施例提供的芯片可以设置于转发硬件上或者转发硬件包括的转发电路集成于本申请实施例提供的芯片。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包括，例如，包括了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请中“至少一项(个)”是指一个或者多个，“多个”是指两个或两个以上。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。本申请中认为“A和/或B”包括单独A，单独B，和A+B。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑模块划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要获取其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各模块单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件模块单元的形式实现。
所述集成的单元如果以软件模块单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机 存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已。
以上所述，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (25)

  1. 一种确定下一跳的方法，其特征在于，所述方法应用于基于位索引转发路由BIER域，包括：
    第三设备获取第一设备的第一BIER信息、所述第一设备的属性、第二设备的第二BIER信息和所述第二设备的属性，所述第一BIER信息包括子域中的边缘位转发路由器BFR的位转发路由器标识BFR-id，所述第二BIER信息包括所述子域中的所述边缘BFR的所述BFR-id；
    所述第三设备根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳。
  2. 根据权利要求1所述的方法，其特征在于，所述第一设备的属性和所述第二设备的属性包括第一标识，所述第一标识用于标识anycast的BFR前缀，所述方法还包括：
    所述第三设备在所述第一BIER信息和所述第二BIER信息相同，且所述第一设备的属性和所述第二设备的属性包括第一标识时，执行确定到达所述子域中所述边缘BFR的下一跳。
  3. 根据权利要求1所述的方法，其特征在于，所述第一设备的属性或所述第二设备的属性包括第一标识，所述第一标识用于标识anycast的BFR前缀，所述第三设备根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳包括：
    所述第三设备在所述第一BIER信息和所述第二BIER信息相同时，将属性包括所述第一标识的设备确定为下一跳。
  4. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第三设备在所述第一BFR信息和所述第二BIER信息相同，所述第一设备的属性和所述第二设备的属性均不包括第一标识时，输出告警，所述第一标识用于标识anycast的BFR前缀。
  5. 根据权利要求2所述的方法，其特征在于，所述第一设备的属性还包括所述第一设备的节点标识，所述第二设备的属性包括所述第二设备的节点标识，所述第三设备根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳包括：
    所述第三设备在所述第一BIER信息与所述第二BIER信息相同时，基于第一策略、所述第一设备的节点标识和所述第二设备的节点标识，确定所述第一设备和第二设备中的一个设备作为下一跳，所述第一策略包括将节点标识较大的设备作为下一跳或者将节点标识较小的设备作为下一跳。
  6. 根据权利要求2所述的方法，其特征在于，所述第一设备的属性还包括第二标识，所述第二设备的属性还包括第三标识，所述第二标识用于标识所述第一设备的优先级，所述第三标识用于标识所述第二设备的优先级，所述第三设备根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳包括：
    所述第三设备在所述第一BIER信息与所述第二BIER信息相同时，基于第二策略、所述第二标识和所述第三标识，确定所述第一设备和所述第二设备中的一个设备作为下一跳，所述第二策略包括将优先级较大的设备作为下一跳或者将优先级较小的设备作为下一跳。
  7. 根据权利要求1所述的方法，其特征在于，所述第一设备的属性包括所述第一设备的BFR前缀，所述第二设备的属性包括所述第二设备的BFR前缀，所述第一设备的BFR前缀与所述第二设备的BFR前缀不同，所述第三设备根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳包括：
    所述第三设备在所述第一BIER信息和所述第二BIER信息相同时，根据第三策略、第一链路的开销cost值和第二链路的cost值，确定所述第一设备和所述第二设备中的一个设备作为下一跳，所述第三策略包括将cost值较小的链路对端的设备作为下一跳或者将cost值较大的链路对端的设备作为下一跳，所述第一链路为所述第三设备到达所述第一设备的链路，所述第二链路为所述第三设备到达所述第二设备的链路。
  8. 根据权利要求1所述的方法，其特征在于，所述第一设备的属性包括所述第一设备的BFR前缀，所述第二设备的属性包括所述第二设备的BFR前缀，所述第一设备的BFR前缀与所述第二设备的BFR前缀不同，所述第三设备根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳包括：
    所述第三设备在所述第一BIER信息和所述第二BIER信息相同时，根据第四策略、所述第一设备的BFR前缀和所述第二设备的BFR前缀，确定所述第一设备和所述第二设备中的一个设备作为下一跳，所述第四策略包括将BFR前缀较小的设备作为下一跳或者将BFR前缀较大的设备作为下一跳。
  9. 根据权利要求1所述的方法，其特征在于，所述第一设备的属性包括所述第一设备的BFR前缀和所述第一设备的节点标识，所述第二设备的属性包括所述第二设备的BFR前缀和所述第二设备的节点标识，所述第一设备的BFR前缀与所述第二设备的BFR前缀不同，所述第三设备根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳包括：
    所述第三设备在所述第一BIER信息和所述第二BIER信息相同时，根据第一策略、所述第一设备的节点标识和所述第二节点的节点标识，确定第一设备和第二设备中的一个设备作为下一跳，所述第一策略包括将节点标识较大的设备作为下一跳或者将节点标识较小的设备作为下一跳。
  10. 根据权利要求1所述的方法，其特征在于，所述第一设备的属性包括所述第一设备的BFR前缀和第二标识，所述第二设备的属性包括所述第二设备的BFR前缀和第三标识，所述第二标识用于标识所述第一设备的优先级，所述第三标识用于标识所述第二设备的优先级，所述第一设备的BFR前缀与所述第二设备的BFR前缀不同，所述第三设备根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳包括：
    所述第三设备在所述第一BIER信息和所述第二BIER信息相同时，根据第二策略、所述第二标识和所述第三标识，确定第一设备和第二设备中的一个设备作为下一跳，所述第二策略包括将优先级较大的设备作为下一跳或者将优先级较小的设备作为下一跳。
  11. 一种确定下一跳的装置，其特征在于，所述装置设于基于位索引转发路由BIER域，包括：
    获取单元，用于获取第一设备的第一BIER信息、所述第一设备的属性、第二设备的第二BIER信息和所述第二设备的属性，所述第一BIER信息包括子域中的边缘位转发路由器 BFR的位转发路由器标识BFR-id，所述第二BIER信息包括所述子域中的所述边缘BFR的所述BFR-id；
    确定单元，用于根据所述第一BIER信息、所述第二BIER信息、所述第一设备的属性和所述第二设备的属性，确定到达所述子域中的所述边缘BFR的下一跳。
  12. 根据权利要求11所述的装置，其特征在于，所述第一设备的属性和所述第二设备的属性包括第一标识，所述第一标识用于标识anycast的BFR前缀，所述装置还包括：
    识别单元，用于在所述第一BIER信息和所述第二BIER信息相同，且所述第一设备的属性和所述第二设备的属性包括第一标识时，执行确定到达所述子域的所述BFR的下一跳。
  13. 根据权利要求11所述的装置，其特征在于，所述第一设备的属性或所述第二设备的属性包括第一标识，所述第一标识用于标识anycast的BFR前缀，所述确定单元具体用于：
    在所述第一BIER信息和所述第二BIER信息相同时，将属性包括所述第一标识的设备确定为下一跳。
  14. 根据权利要求11所述的装置，其特征在于，所述装置还包括：
    输出单元，用于确在所述第一BFR信息和所述第二BIER信息相同，所述第一设备的属性和所述第二设备的属性均不包括第一标识时，输出告警。
  15. 根据权利要求12所述的装置，其特征在于，所述第一设备的属性还包括所述第一设备的节点标识，所述第二设备的属性包括所述第二设备的节点标识，所述确定单元具体用于：
    在所述第一BIER信息与所述第二BIER信息相同时，基于第一策略、所述第一设备的节点标识和所述第二设备的节点标识，确定所述第一设备和第二设备中的一个设备作为下一跳，所述第一策略包括将节点标识较大的设备作为下一跳或者将节点标识较小的设备作为下一跳。
  16. 根据权利要求12所述的装置，其特征在于，所述第一设备的属性还包括第二标识，所述第二设备的属性还包括第三标识，所述第二标识用于标识所述第一设备的优先级，所述第三标识用于标识所述第二设备的优先级，所述确定单元具体用于：
    在所述第一BIER信息与所述第二BIER信息相同时，基于第二策略、所述第二标识和所述第三标识，确定所述第一设备和所述第二设备中的一个设备作为下一跳，所述第二策略包括将优先级较大的设备作为下一跳或者将优先级较小的设备作为下一跳。
  17. 根据权利要求11所述的装置，其特征在于，所述第一设备的属性包括所述第一设备的BFR前缀，所述第二设备的属性包括所述第二设备的BFR前缀，所述第一设备的BFR前缀与所述第二设备的BFR前缀不同，所述确定单元具体用于：
    在所述第一BIER信息和所述第二BIER信息相同时，根据第三策略、第一链路的开销cost值和第二链路的cost值，确定所述第一设备和所述第二设备中的一个设备作为下一跳，所述第三策略包括将cost值较小的链路对端的设备作为下一跳或者将cost值较大的链路对端的设备作为下一跳，所述第一链路为所述第三设备到达所述第一设备的链路，所述第二链路为所述第三设备到达所述第二设备的链路。
  18. 根据权利要求11所述的装置，其特征在于，所述第一设备的属性包括所述第一设备的BFR前缀，所述第二设备的属性包括所述第二设备的BFR前缀，所述第一设备的BFR前缀与所述第二设备的BFR前缀不同，所述确定单元具体用于：
    在所述第一BIER信息和所述第二BIER信息相同时，根据第四策略、所述第一设备的BFR前缀和所述第二设备的BFR前缀，确定所述第一设备和所述第二设备中的一个设备作为下一跳，所述第四策略包括将BFR前缀较小的设备作为下一跳或者将BFR前缀较大的设备 作为下一跳。
  19. 根据权利要求11所述的装置，其特征在于，所述第一设备的属性包括所述第一设备的BFR前缀和所述第一设备的节点标识，所述第二设备的属性包括所述第二设备的BFR前缀和所述第二设备的节点标识，所述第一设备的BFR前缀与所述第二设备的BFR前缀不同，所述确定单元具体用于：
    在所述第一BIER信息和所述第二BIER信息相同时，根据第一策略、所述第一设备的节点标识和所述第二节点的节点标识，确定第一设备和第二设备中的一个设备作为下一跳，所述第一策略包括将节点标识较大的设备作为下一跳或者将节点标识较小的设备作为下一跳。
  20. 根据权利要求1所述的方法，其特征在于，所述第一设备的属性包括所述第一设备的BFR前缀和第二标识，所述第二设备的属性包括所述第二设备的BFR前缀和第三标识，所述第二标识用于标识所述第一设备的优先级，所述第三标识用于标识所述第二设备的优先级，所述第一设备的BFR前缀与所述第二设备的BFR前缀不同，所述确定单元具体用于：
    在所述第一BIER信息和所述第二BIER信息相同时，根据第二策略、所述第二标识和所述第三标识，确定第一设备和第二设备中的一个设备作为下一跳，所述第二策略包括将优先级较大的设备作为下一跳或者将优先级较小的设备作为下一跳。
  21. 一种系统，其特征在于，所述系统包括如权利要求11至20任一所述的确定下一跳的装置。
  22. 一种芯片，其特征在于，所述芯片包括存储器和处理器，所述存储器用于存储计算机指令，所述处理器用于从所述存储器中调用并运行所述计算机指令，以执行权利要求1至10任一所述的确定下一跳的方法。
  23. 一种计算机程序产品，其特征在于，所述计算机程序产品包括一个或多个计算机程序指令，当所述计算机程序指令被计算机加载并执行时，使得所述计算机执行权利要求1至10任一所述的确定下一跳的方法。
  24. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质用于存储指令，所述指令中包括用于执行权利要求1至10任一所述的确定下一跳的方法所设计的程序。
  25. 一种确定下一跳的装置，其特征在于，所述发送组播报文的装置包括处理器和存储供所述处理器执行的程序指令的非瞬时性计算机可读存储介质，所述程序指令指示所述处理器执行权利要求1至10任一所述的确定下一跳的方法。
PCT/CN2021/116119 2020-10-30 2021-09-02 确定下一跳的方法及装置 WO2022088967A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2023526335A JP2023547485A (ja) 2020-10-30 2021-09-02 次ホップ決定方法および装置
EP21884698.8A EP4224817A4 (en) 2020-10-30 2021-09-02 METHOD AND DEVICE FOR DETERMINING THE NEXT JUMP
KR1020237017030A KR20230088494A (ko) 2020-10-30 2021-09-02 다음 홉을 결정하기 위한 방법 및 장치
US18/309,532 US20230269165A1 (en) 2020-10-30 2023-04-28 Next Hop Determining Method and Apparatus

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202011193045 2020-10-30
CN202011193045.7 2020-10-30
CN202110184092.3 2021-02-10
CN202110184092.3A CN114531391A (zh) 2020-10-30 2021-02-10 确定下一跳的方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/309,532 Continuation US20230269165A1 (en) 2020-10-30 2023-04-28 Next Hop Determining Method and Apparatus

Publications (1)

Publication Number Publication Date
WO2022088967A1 true WO2022088967A1 (zh) 2022-05-05

Family

ID=81381835

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/116119 WO2022088967A1 (zh) 2020-10-30 2021-09-02 确定下一跳的方法及装置

Country Status (5)

Country Link
US (1) US20230269165A1 (zh)
EP (1) EP4224817A4 (zh)
JP (1) JP2023547485A (zh)
KR (1) KR20230088494A (zh)
WO (1) WO2022088967A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12040978B2 (en) * 2021-04-02 2024-07-16 Microsoft Technology Licensing, Llc Anycast routing technique for a content delivery network

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106209629A (zh) * 2014-11-06 2016-12-07 瞻博网络公司 确定性的且优化的比特索引显式复制（bier）转发
CN106506367A (zh) * 2016-11-30 2017-03-15 杭州华三通信技术有限公司 一种下一跳确定方法及装置
CN106656524A (zh) * 2015-10-30 2017-05-10 中兴通讯股份有限公司 一种bier控制信息的传输方法、装置和系统
CN110784411A (zh) * 2019-09-30 2020-02-11 华为技术有限公司 建立bier转发表项的方法、装置和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106209629A (zh) * 2014-11-06 2016-12-07 瞻博网络公司 确定性的且优化的比特索引显式复制（bier）转发
CN106656524A (zh) * 2015-10-30 2017-05-10 中兴通讯股份有限公司 一种bier控制信息的传输方法、装置和系统
CN106506367A (zh) * 2016-11-30 2017-03-15 杭州华三通信技术有限公司 一种下一跳确定方法及装置
CN110784411A (zh) * 2019-09-30 2020-02-11 华为技术有限公司 建立bier转发表项的方法、装置和系统

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
US20230269165A1 (en) 2023-08-24
EP4224817A4 (en) 2024-04-03
JP2023547485A (ja) 2023-11-10
EP4224817A1 (en) 2023-08-09
KR20230088494A (ko) 2023-06-19

Similar Documents

Publication Publication Date Title
JP7419510B2 (ja) Ｂｉｅｒ転送項目構築方法、装置、およびシステム
EP2869512B1 (en) Dynamic area filtering for link-state routing protocols
US9319312B2 (en) Segment routing mapping server for LDP/SR interoperability
CN106572023B (zh) 一种实现比特位索引显示复制的方法及比特位转发路由器
US10637687B2 (en) EVPN implicit aliasing
US8121032B2 (en) Efficient convergence of grouped VPN prefixes
WO2021189993A1 (zh) 路由方法、路由装置及计算机可读存储介质
JP7479489B2 (ja) パケット送信方法、デバイス、およびシステム
US11671352B2 (en) Message sending method, binding relationship advertising method, apparatus, and storage medium
WO2016198022A1 (zh) 一种实现虚拟化网络叠加的方法与网络虚拟化边缘节点
CN111837368B (zh) 使用内部网关协议通告和编程优选路径路由
US20220286383A1 (en) Method and Apparatus for Processing Forwarding Entry
US20230269165A1 (en) Next Hop Determining Method and Apparatus
WO2018177273A1 (zh) 一种基于bier信息的处理及装置
US12058027B2 (en) Packet transmission method, correspondence obtaining method, apparatus, and system
US7525949B1 (en) Forwarding for network devices
WO2023016550A1 (zh) 一种路由发送方法及设备
JP7273125B2 (ja) ＢＩＥＲｖ６パケットを送信するための方法および第１のネットワークデバイス
Le Faucheur et al. Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop
CN114531391A (zh) 确定下一跳的方法及装置
WO2022188488A1 (zh) 路径建立方法及其装置、节点、计算机可读存储介质
WO2024061184A1 (zh) 对应关系的获取方法、参数通告方法、装置、设备及介质
US12028249B2 (en) Resource aware forwarding in the network with abstract destination address and semantic addressing
WO2024179107A1 (zh) 一种路由通告的方法以及相关装置

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202327029771

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2023526335

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 2021884698

Country of ref document: EP

Effective date: 20230503

ENP Entry into the national phase

Ref document number: 20237017030

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE