Method and device for publishing information and method and device for acquiring forwarding information

By publishing and receiving Flex-Algo information and BFR IDs within the BIER domain, dynamically determining forwarding information is solved, the problem of inflexible configuration of BIER equipment is realized, the flexible configuration and business differentiation needs of BIERv6 are realized, and the business quality assurance is improved.

CN119071218APending Publication Date: 2024-12-03HUAWEI TECH CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202310627229.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-30
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

After BIER devices configure the BIER subdomain, the existing methods have problems with inflexible configuration, which is difficult to meet the differentiated needs of different services and the separation of forwarding planes.

Method used

By obtaining and sending flexible algorithms Flex-Algo information, bit forwarding router identification BFR ID and address prefix in nodes within the BIER domain, information is published and received using ISIS or OSPFv3 messages, forwarding information is dynamically determined, forwarding plane distinction is realized, and BIERv6 is supported in Run individual planes and provide different plane configurations for different services.

Benefits of technology

It improves the flexibility of BIER configuration, reduces the implementation complexity, supports differentiated needs of different businesses, and ensures business quality assurance and flexible configuration.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119071218A_ABST
    Figure CN119071218A_ABST
Patent Text Reader

Abstract

The invention provides a method and device for publishing information and a method and device for obtaining forwarding information, and belongs to the technical field of communication. The information publishing method comprises the following steps: acquiring a first address prefix, Flex-Algo information, a bit forwarding router identifier (BFR) ID of a first node and an address of the first node based on the first node in a bit indexed explicit replication (BIER) domain; and the first node sends the first address prefix, the Flex-Algo information, the BFR ID of the first node and the address of the first node.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method and device for publishing information, and a method and device for obtaining forwarding information. Background Art

[0002] Bit indexed explicit replication (BIER) technology is a technology used to implement multicast message forwarding. After configuring the BIER subdomain, the device that supports BIER forwarding (referred to as BIER device) specifies the address prefix (prefix) of the BIER device based on the loopback interface. After completing the above manual configuration, the BIER device sends the address prefix of the BIER device to other BIER devices in the network, so that each BIER device can determine the bit index routing table (BIRT) based on the address prefixes received from other BIER devices. The above method has the problem of insufficient configuration flexibility. Summary of the invention

[0003] The present application provides a method and device for publishing information, and a method and device for obtaining forwarding information, which can improve the flexibility of configuration. The technical solution is as follows.

[0004] In a first aspect, a method for publishing information is provided, the method comprising: a first node within a BIER domain obtains a first address prefix, flexible algorithm Flex-Algo information, a bit forwarding router identifier BFR ID of the first node, and an address of the first node; the first node sends the first address prefix, Flex-Algo information, the BFR ID of the first node, and the address of the first node, so that other nodes within the BIER domain can receive this information and determine forwarding information based on this information.

[0005] Exemplarily, the first node is an intermediate BFR or a bit forwarding egress router BFER.

[0006] In this implementation, the intermediate node or egress node in the BIER domain publishes the prefix address, BFR ID, Flex-Algo information and node address, and the intermediate node or ingress node in the BIER domain receives the above information and then determines the forwarding information based on the above information. When determining the forwarding information, the intermediate node or ingress node in the BIER domain can determine the next hop corresponding to the Flex-Algo information, so that the forwarding information can distinguish the forwarding plane, so that BIERv6 can run on a separate plane, and different planes can be used for BIER forwarding for different services, which is beneficial to service quality assurance and flexible configuration.

[0007] In some possible implementations, the first address prefix is ​​an address prefix of a loopback interface of the first node.

[0008] In some other possible implementations, the first address prefix is ​​an address prefix corresponding to an Internet Protocol IPv6-based segment routing SRv6 location identifier locator of the first node, that is, the SRv6 locator serves as a BFR prefix.

[0009] In this implementation, since the SRv6 locator is reused as the BFR prefix, there is no need to separately allocate a loopback interface and configure an address prefix for each BIER device, which reduces the implementation complexity.

[0010] Exemplarily, the first node sends the first address prefix, Flex-Algo information, the BFR ID of the first node, and the address of the first node, including:

[0011] The first node sends an Intermediate System to Intermediate System (ISIS) message or an Open Shortest Path First (OSPFv3) message, where the ISIS message or the OSPFv3 message includes the first address prefix, Flex-Algo information, the BFR ID of the first node, and the address of the first node.

[0012] Optionally, the ISIS message or OSPFv3 message includes an SRv6 location identifier type length value TLV, where the SRv6 location identifier TLV includes the first address prefix, Flex-Algo information, a BFR ID of the first node, and an address of the first node; or,

[0013] The ISIS message or the OSPFv3 message includes Internet Protocol version 6 IPv6 TLV, and the IPv6 TLV includes the first address prefix, Flex-Algo information, the BFR ID of the first node, and the address of the first node.

[0014] In the above implementation, ISIS or OSPFv3 is used to publish the information of the first node, and no additional configuration of control plane messages is required, which facilitates the implementation of the solution.

[0015] Optionally, the first node sends the first address prefix, Flex-Algo information, the BFR ID of the first node, and the address of the first node, including:

[0016] The first node sends a first correspondence and a second correspondence, where the first correspondence includes a first address prefix, the BFR ID of the first node and the address of the first node, and the second correspondence includes a second address prefix and Flex-Algo information, where the second address prefix includes the first address prefix or the address of the first node.

[0017] In this implementation, the information of the above-mentioned first node is published through two corresponding relationships, wherein the second corresponding relationship limits the correspondence between the address prefix and the Flex-Algo information. In this way, after receiving the second node, it can determine the next hop corresponding to the address prefix based on the Flex-Algo information, thereby realizing the distinction of the forwarding plane.

[0018] In a second aspect, a method for obtaining forwarding information is provided, the method comprising: a second node within a BIER domain obtains information about a first node, the information about the first node including a first address prefix, flexible algorithm Flex-Algo information, a bit forwarding router identifier BFR ID of the first node, and the address of the first node; the second node obtains forwarding information based on the information of the first node, the forwarding information including a next hop and the BFR ID of the first node, the next hop being the next hop corresponding to the Flex-Algo information.

[0019] Exemplarily, the second node is an intermediate BFR or a bit forwarding ingress router BFIR; the first node is an intermediate BFR or a bit forwarding egress router BFER.

[0020] In this implementation, the intermediate node or entry node within the BIER domain receives the prefix address, BFR ID, Flex-Algo information and node address published by other nodes, and then determines the forwarding information based on the above information. When determining the forwarding information, the intermediate node or entry node within the BIER domain can determine the next hop corresponding to the Flex-Algo information, so that the forwarding information can distinguish the forwarding plane, so that BIERv6 can run on a separate plane, and different planes can be used for BIER forwarding for different services, which is conducive to service quality assurance and flexible configuration.

[0021] In some possible implementations, the first address prefix is ​​an address prefix of a loopback interface of the first node.

[0022] In some other possible implementations, the first address prefix is ​​an address prefix corresponding to an Internet Protocol IPv6-based segment routing SRv6 location identifier locator of the first node, that is, the SRv6 locator serves as a BFR prefix.

[0023] In this implementation, since the SRv6 locator is reused as the BFR prefix, there is no need to separately allocate a loopback interface and configure an address prefix for each BIER device, which reduces the implementation complexity.

[0024] Exemplarily, the second node obtains the information of the first node, including:

[0025] The second node receives an ISIS message or an OSPFv3 message, where the ISIS message or the OSPFv3 message includes the first address prefix, Flex-Algo information, the BFR ID of the first node, and the address of the first node.

[0026] Optionally, the ISIS message or OSPFv3 message includes an SRv6 location identifier type length value TLV, where the SRv6 location identifier TLV includes the first address prefix, Flex-Algo information, a BFR ID of the first node, and an address of the first node; or,

[0027] The ISIS message or the OSPFv3 message includes Internet Protocol version 6 IPv6 TLV, and the IPv6 TLV includes the first address prefix, Flex-Algo information, the BFR ID of the first node, and the address of the first node.

[0028] In the above implementation, ISIS or OSPFv3 is used to publish the information of the first node, and no additional configuration of control plane messages is required, which facilitates the implementation of the solution.

[0029] Exemplarily, the second node acquires forwarding information based on information of the first node, including:

[0030] The second node obtains a second address prefix, where the second address prefix includes the first address prefix or the address of the first node;

[0031] The second node obtains a next hop based on the second address prefix and the Flex-Algo information, where the next hop is a next hop that matches the Flex-Algo information among the next hops that reach the second address prefix;

[0032] The second node obtains forwarding information based on the next hop and the BFR ID of the first node.

[0033] In this implementation, the second node determines the next hop corresponding to the address prefix based on the Flex-Algo information, thereby achieving differentiation of the forwarding plane.

[0034] In a third aspect, a device for publishing information is provided, the device comprising:

[0035] An acquisition unit, used to acquire a first address prefix, flexible algorithm Flex-Algo information, a bit forwarding router identifier BFR ID of a first node in a BIER domain explicitly copied based on a bit index, and an address of the first node;

[0036] The sending unit is used to send the first address prefix, Flex-Algo information, the BFR ID of the first node and the address of the first node.

[0037] Optionally, the first address prefix is ​​an address prefix of a loopback interface of the first node; or,

[0038] The first address prefix is ​​an address prefix corresponding to the segment routing SRv6 location identifier based on the Internet Protocol IPv6 of the first node.

[0039] Optionally, the sending unit is used to send an intermediate system to intermediate system ISIS message or an open shortest path first OSPFv3 message, where the ISIS message or the OSPFv3 message includes the first address prefix, Flex-Algo information, the BFRID of the first node and the address of the first node.

[0040] Optionally, the ISIS message or OSPFv3 message includes an SRv6 location identifier type length value TLV, where the SRv6 location identifier TLV includes the first address prefix, Flex-Algo information, a BFR ID of the first node, and an address of the first node; or,

[0041] The ISIS message or the OSPFv3 message includes Internet Protocol version 6 IPv6 TLV, and the IPv6 TLV includes the first address prefix, Flex-Algo information, the BFR ID of the first node, and the address of the first node.

[0042] Optionally, the sending unit is used to send a first correspondence relationship and a second correspondence relationship, the first correspondence relationship includes a first address prefix, a BFR ID of the first node and the address of the first node, the second correspondence relationship includes a second address prefix and Flex-Algo information, and the second address prefix includes the first address prefix or the address of the first node.

[0043] Optionally, the first node is an intermediate BFR or a bit forwarding egress router BFER.

[0044] In a fourth aspect, a device for obtaining forwarding information is provided, the device comprising:

[0045] A first acquisition unit is used to acquire information of a first node in a BIER domain explicitly replicated based on a bit index, the information of the first node including a first address prefix, flexible algorithm Flex-Algo information, a bit forwarding router identifier BFR ID of the first node, and an address of the first node;

[0046] The second acquisition unit is used to acquire forwarding information based on the information of the first node, where the forwarding information includes a next hop and a BFR ID of the first node, and the next hop is a next hop corresponding to the Flex-Algo information.

[0047] Optionally, the first address prefix is ​​an address prefix of a loopback interface of the first node; or,

[0048] The first address prefix is ​​an address prefix corresponding to the segment routing SRv6 location identifier based on the Internet Protocol IPv6 of the first node.

[0049] Optionally, the first acquisition unit is used to receive an ISIS message or an OSPFv3 message, where the ISIS message or the OSPFv3 message includes the first address prefix, Flex-Algo information, a BFR ID of the first node, and the address of the first node.

[0050] Optionally, a second acquisition unit is used to obtain a second address prefix, where the second address prefix includes the first address prefix or the address of the first node; based on the second address prefix and the Flex-Algo information, obtain the next hop, where the next hop is the next hop that matches the Flex-Algo information in the next hop to reach the second address prefix; based on the next hop and the BFR ID of the first node, obtain forwarding information.

[0051] Optionally, the device is an intermediate BFR or a bit forwarding ingress router BFIR;

[0052] The first node is an intermediate BFR or a bit forwarding egress router BFER.

[0053] In a fifth aspect, a network device is provided, which includes a processor and a memory, wherein the memory is used to store a software program, and the processor runs or executes the software program stored in the memory so that the network device implements the method in the first aspect or any optional manner of the first aspect, or implements the method in the second aspect or any optional manner of the second aspect.

[0054] In a sixth aspect, an information transmission system is provided, which includes a BIER device, and the BIER device executes the method in the above-mentioned first aspect or any optional manner of the first aspect, or executes the method in the above-mentioned second aspect or any optional manner of the second aspect.

[0055] In the seventh aspect, a computer-readable storage medium is provided, which stores at least one instruction. When the instruction is executed on a computer, the computer executes the method provided by the first aspect or any optional embodiment of the first aspect, or executes the method in the second aspect or any optional embodiment of the second aspect.

[0056] In an eighth aspect, a computer program product is provided, which includes one or more computer program instructions. When the computer program instructions are loaded and executed by a computer, the computer executes the method provided by the first aspect or any optional embodiment of the first aspect, or executes the method in the second aspect or any optional embodiment of the second aspect.

[0057] In the ninth aspect, a chip is provided, comprising a memory and a processor, the memory being used to store computer instructions, and the processor being used to call and run the computer instructions from the memory to execute the method in the above-mentioned first aspect and any possible implementation of the first aspect, or to execute the method in the above-mentioned second aspect or any optional implementation of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Figure 1 This is a format diagram of a BIERv6 message provided in an embodiment of the present application;

[0059] Figure 2 It is a schematic diagram of a network deployment scenario provided by an embodiment of the present application;

[0060] Figure 3 is a flow chart of a method for publishing information provided by an embodiment of the present application;

[0061] Figure 4 is a flow chart of a method for obtaining forwarding information provided by an embodiment of the present application;

[0062] Figure 5 is a flow chart of a method for publishing information provided by an embodiment of the present application;

[0063] Figure 6 This is a schematic diagram of the structure of a TLV provided in an embodiment of the present application;

[0064] Figure 7 This is a schematic diagram of the structure of a TLV provided in an embodiment of the present application;

[0065] Figure 8 This is a schematic diagram of the structure of a TLV provided in an embodiment of the present application;

[0066] Fig. 9 This is a schematic diagram of the structure of a TLV provided in an embodiment of the present application;

[0067] Fig.10 It is a structural diagram of a device for publishing information provided in an embodiment of the present application;

[0068] Fig.11 It is a structural diagram of a device for obtaining forwarding information provided by an embodiment of the present application;

[0069] Fig.12 It is a structural diagram of a network device provided in an embodiment of the present application;

[0070] Fig.13 It is a structural diagram of a network device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0071] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the drawings.

[0072] The following is an explanation of some terminology concepts involved in the embodiments of the present application.

[0073] (1) Bit-based Indexed Explicit Replication (BIER)

[0074] BIER technology is a kind of multicast technology. In BIER technology, a bit forwarding router identifier (BFR ID) is assigned to the edge nodes of the BIER domain, for example, a value between 1 and 256. The edge node floods its configured BIER information in the BIER domain through the interior gateway protocol (IGP), so that other nodes in the BIER domain obtain the parameters required to implement BIER forwarding. For example, if the value of the node's BFR ID is non-0, then the node is an edge node. If the node's BFR ID is 0, then the node is an intermediate node, that is, a non-edge node.

[0075] (2) BIERv6

[0076] BIERv6 is BIER technology encapsulated by Internet Protocol version 6 (IPv6). Figure 1 This is a schematic diagram of the format of a BIERv6 message provided in an embodiment of the present application. Figure 1, the BIERv6 message includes a BIERv6 message header and a multicast data message (that is, the IPv6 Multicast Payload in the figure). The BIERv6 message header includes an IPv6 basic message header and an option extension message header (destination options header, DOH). Among them, the IPv6 basic message header includes version (Version), traffic class (Traffic Class), flow label (Flow Label), payload length (Pload Length), next message header (Next Header), hop limit (Hop Limit), source address (SourceAddress) and destination address (Destination Address). DOH includes the next header (Next Header), the extension header length (Ext Hdr Len), the option type (Option Type), the optional field length (Opt Data Len), the bit indexed forwarding table identifier (BIFT-ID), the traffic class (TC), the S bit, the time to live (TTL), the differentiator (Nibble), the version (Ver), the bit string length (bitslength, BSL), the entropy value (Entropy), the detection (OAM), the reservation (Rsv), the differentiated services field codepoints (differentiated services field codepoints, DSCP), the protocol (Proto), the bit forwarding ingress router (bit forwarding ingress router, BFIR) identifier (identifier, ID) and the bit string (BitString). Each bit in the BitString corresponds to the bit forwarding egress router (bit forwarding egress router, BFER), for example, the low bit (rightmost) of the BitString is used to identify the BFER with a BFR ID of 1. The second bit from right to left in the BitString is used to identify the BFER with BFR ID 2. The BFIR, intermediate BFR or BFER in the BIER domain can forward the BIER message based on the BIER forwarding table entry and the BitString included in the BIER message.

[0077] (3)End.BIER

[0078] End.BIER is a new type of SID defined in the BIERv6 network. It serves as the IPv6 destination address to indicate the BIERv6 extension header in the message processed by the forwarding plane of the device. When each node receives and processes the BIERv6 message, it encapsulates the End.BIER of the next-hop node as the outer IPv6 destination address of the BIERv6 message so that the next-hop node can forward the message according to the BIERv6 process. End.BIER can be divided into two parts: location identifier (Locator) and other bits. Locator represents a BIERv6 forwarding node. Locator has a positioning function. After the node is configured with Locator, the system will generate a Locator network segment route and spread it in the segment routing (segment routing over IPv6, SRv6) domain based on IPv6 through the interior gateway protocol (IGP). Other nodes in the network can locate this node through the Locator network segment route. End.BIER can guide the message to the designated BFR. BFR recognizes that the destination address of the message is the local End.BIER, determines the virtual routing and forwarding (VRF) table according to the Locator, determines the corresponding BIER forwarding table based on the VRF table, and forwards the message based on the End.BIER according to the BIFT-id <sub-domain (sub-domain, SD) / bit string length (BitString length, BSL) / set identifier (setidentifier, SI)> in the corresponding forwarding table entry.

[0079] (4)SRv6 Locator

[0080] According to the SRv6 architecture standards RFC8986 and RFC8754, an IPv6 address block is planned in the network, and an SRv6 Locator is configured for each device in the operator network in the address block. For example, the above address block is 2001:db8:ffff:: / 48. Based on this address block, the SRv6 Locator of the Kth node is identified by 2001:db8:ffff:k:: / 64. For example, PE1 / PE2 / PE3 / P1 are the 1st / 2nd / 3rd / 10th nodes respectively, and the corresponding SRv6 Locators are 2001:db8:ffff:1:: / 64, 2001:db8:ffff:2:: / 64, 2001:db8:ffff:3:: / 64, and 2001:db8:ffff:A:: / 64. End.BIER can be the address under the SRv6 Locator. For example, the Locator of the provider edge (PE) node is 2001:DB8:100:: / 64, and the End.BIER is 2001:DB8:100:1 (128 bit); for another example, the Locator of the PE node is 2001:DB8:200:: / 64, and the End.BIER is 2001:DB8:200:1 (128 bit).

[0081] (5) Flexible algorithm (Flex-Algo)

[0082] Flex-Algo provides a simple solution for separating routing planes, constraining traffic engineering (TE) paths, and low-latency routing, meeting the differentiated needs of various services in the 5G era. In other words, Flex-Algo allows IGP to calculate constraint-based network paths, and use different constraints for path calculation for different applications or services to achieve forwarding plane separation for different applications or services. The Flex-Algo algorithm definition includes three elements: calculation type, metric type, and constraint conditions. Flex-Algo algorithms defined by different elements can be configured with different identifiers. Usually, the Flex-Algo algorithm identifier is defined as Flex-Algo (128) to Flex-Algo (255).

[0083] (6)BFR prefix

[0084] The node announces the BFR prefix in the subdomain, so that each node in the subdomain can determine the BFR neighbor (BFR-NBR) based on the BFR prefix of other BFR nodes, and then generate BIRT, and generate BIFT based on BIRT.

[0085] Figure 2 Schematic diagram of a network deployment scenario provided by an embodiment of the present application. Figure 2 As shown, the scenario includes nodes A~G, and the above nodes A~G belong to the same BIERv6 subdomain (sub domain), such as sub domain 0. Among them, nodes D, E, F, and G are edge nodes, and are configured with BFR IDs: D's BFR ID is 1, E's BFR ID is 2, F's BFR ID is 3, and G's BFR ID is 4. Figure 3 It is a flowchart of a method for publishing information provided in an embodiment of the present application. Figure 3 The method shown includes the following steps S201 to S202. Figure 3 The method shown can be performed by a first node in a BIER domain (e.g., a BIERv6 subdomain), the first node being an intermediate BFR or BFER, for example, Figure 2 Any of the nodes B to G in the scene shown is executed.

[0086] S201. The first node obtains a first address prefix, Flex-Algo information, a BFRID of the first node, and an address of the first node.

[0087] The address prefix of the first node may refer to the BFR prefix of the first node. The Flex-Algo information may refer to the Flex-Algo ID. The address of the first node may refer to the End.BIER of the first node.

[0088] S202: The first node sends a first address prefix, Flex-Algo information, a BFR ID of the first node, and an address of the first node.

[0089] In one example, the first node sending the above information may mean flooding the above information in the BIER domain through IGP so that other nodes in the BIER domain obtain the above information and determine forwarding information based on the above information, such as determining BIFT.

[0090] In an embodiment of the present application, the intermediate node or the egress node within the BIER domain publishes the prefix address, BFRID, Flex-Algo information and the node address, and the intermediate node or the ingress node within the BIER domain receives the above information and then determines the forwarding information based on the above information. When determining the forwarding information, the intermediate node or the ingress node within the BIER domain can determine the next hop corresponding to the Flex-Algo information, so that the forwarding information can distinguish the forwarding plane, so that BIERv6 can run on a separate plane, and different planes can be used for BIER forwarding for different services, which is beneficial to service quality assurance and flexible configuration.

[0091] Figure 4 It is a flowchart of a method for obtaining forwarding information provided in an embodiment of the present application. Figure 4 The method shown includes the following steps S301 to S302. Figure 4 The method shown can be performed by a second node within the BIER domain (e.g., a BIERv6 subdomain), the second node being an intermediate BFR or BFIR, for example, Figure 2 Any of the nodes A to C in the scenario shown is executed.

[0092] S301. The second node obtains a first address prefix, Flex-Algo information, a BFR ID of the first node, and an address of the first node.

[0093] Among them, the address prefix of the first node may refer to the BFR prefix of the first node. The Flex-Algo information may refer to the Flex-Algo ID. The address of the first node may refer to the End.BIER of the first node. In one example, the second node obtaining the above information may refer to receiving the above information flooded by other nodes in the BIER domain through IGP.

[0094] S302: The second node obtains forwarding information based on the information of the first node, where the forwarding information includes a next hop and a BFR ID of the first node, and the next hop is a next hop corresponding to the Flex-Algo information.

[0095] In an embodiment of the present application, an intermediate node or an entry node within the BIER domain receives the prefix address, BFR ID, Flex-Algo information, and node address published by other nodes, and then determines the forwarding information based on the above information. When determining the forwarding information, the intermediate node or the entry node within the BIER domain can determine the next hop corresponding to the Flex-Algo information, so that the forwarding information can distinguish the forwarding plane, so that BIERv6 can run on a separate plane, and different planes can be used for BIER forwarding for different services, which is beneficial to service quality assurance and flexible configuration.

[0096] Figure 5 It is a flowchart of a method for obtaining forwarding information provided in an embodiment of the present application. Figure 5 The method shown includes the following steps S401 to S404. Figure 5 The method shown can be performed by a first node and a second node in the BIER domain, wherein the first node is an intermediate BFR or BFER and the second node is an intermediate BFR or BFIR, for example Figure 2 Any node among the B-G nodes and any node among the A-C nodes in the illustrated scenario are executed together.

[0097] S401. The first node configures SRv6 and BIER based on user input instructions.

[0098] In a possible implementation, the first node receives an SRv6 configuration instruction input by a user, and configures SRv6 based on the SRv6 configuration instruction; the first node receives a BIER configuration instruction input by a user, and configures BIER based on the BIER configuration instruction. The SRv6 configuration instruction includes configuration information of the SRv6 locator.

[0099] For example, for Figure 2 The SRv6 configuration instructions for node D in can be expressed as:

[0100] segment-routing ipv6

[0101] locator PE1 ipv6-prefix 2001:DB8:100:: / 64static 32

[0102] In the above configuration, the SRv6 locator configured for node D, namely PE1, is 2001:DB8:100:: / 64.

[0103] Optionally, the SRv6 configuration instructions also include Flex-Algo configuration. Figure 2 The SRv6 configuration instructions for node D in can be expressed as:

[0104] segment-routing ipv6

[0105] locator PE1 ipv6-prefix 2001:DB8:100:: / 64static 32flex-algo 128

[0106] In the above configuration, node D, also known as PE1, configures the SRv6 locator as 2001:DB8:100:: / 64 and the flex-algo algorithm identifier as 128.

[0107] Among them, BIER configuration instructions include BIER subdomain identifier, BFR ID, BFR prefix, BIER publishing protocol, END.BIER, BSL and maximum set identifier (MAX-SI).

[0108] For example, for Figure 2 The BIER configuration instruction for node D in can be expressed as:

[0109] Bier

[0110] sub-domain 0ipv6

[0111] BFR ID 1

[0112] bfr-prefix srv6-locator PE1

[0113] protocol isis srv6-locator

[0114] end-bier locator PE1 sid 2001:DB8:100:1

[0115] encap ipv6 bsl 256max-si 0

[0116] In this example, the subdomain identifier of node D, also known as PE1, is 0, the BFR ID is 1, the BFR prefix reuses the SRv6 locator, and the intermediate system to intermediate system (intermediate system-to-intermediate system, ISIS) is used as the BIER publishing protocol. END.BIER is 2001:DB8:100:1 (belonging to the network segment to which the SRv6 locator belongs), the BSL is 256, and the MAX-SI is 0.

[0117] In the above configuration, since the SRv6 locator is reused as the BFR prefix, there is no need to separately allocate a loopback interface and configure an address prefix for each BIER device, which reduces the implementation complexity.

[0118] In other examples, the BFR prefix can also use the prefix address configured by the loopback port of node D. In this case, you need to configure Loopback0 first and configure the address prefix for Loopback0. The BIER configuration instruction can be expressed as:

[0119] Bier

[0120] sub-domain 0ipv6

[0121] bfr-id 1

[0122] bfr-prefix interface Loopback0

[0123] protocol isis

[0124] end-bier locator PE1 sid 2001:DB8:100:1

[0125] encap ipv6 bsl 256max-si 0

[0126] That is, the first address prefix of the first node is the address prefix of the loopback interface of the first node; or, the first address prefix of the first node is the address prefix corresponding to the SRv6 locator of the first node.

[0127] In addition to ISIS, the BIER release protocol can also use the Open Shortest Path First (OSPF) protocol. For example, the configuration instructions of the OSPFv3 protocol can be expressed as:

[0128] protocol ospfv3 srv6-locator or protocol ospfv3

[0129] In another possible implementation, the first node receives a user instruction and automatically performs SRv6 and BIER configuration using the strategy indicated by the user instruction. The strategy may include an SRv6 locator allocation pool and allocation method, the strategy also indicates the reuse of the SRv6 locator as a BFR prefix, and the strategy also indicates the default values ​​or configuration schemes of other parameters, etc., thereby implementing the SRv6 and BIER configuration of the device.

[0130] S402: The first node obtains information about the first node, where the information about the first node includes a first address prefix, Flex-Algo information, a BFR ID of the first node, and an address of the first node.

[0131] Obtain the first address prefix, Flex-Algo information, the BFR ID of the first node, and the address of the first node configured in step S301. Figure 2 For node D, obtain the SRv6 locator address in the SRv6 configuration, and obtain the first address prefix of 2001:DB8:100:: / 64; obtain the Flex-Algo associated with the SRv6 locator address in the SRv6 configuration, and obtain the Flex-Algo information as lex-algo algorithm identifier 128; obtain the BFR ID in the BIER configuration, and obtain the BFRID of the first node as 1; obtain the end-bier address in the BIER configuration, and obtain the address of the first node as 2001:DB8:100:1.

[0132] S403: Information sent by the first node and received by the second node.

[0133] In BIERv6, nodes can flood BIER information through the extended IGP protocol. Therefore, step S403 may include: the first node sends an IGP message, and the IGP message includes the first address prefix, Flex-Algo information, the BFR ID of the first node, and the address of the first node. Among them, the IGP message can be an intermediate system to intermediate system (intermediate system-to-intermediate system, ISIS) message or an open shortest path first (Open Shortest PathFirst, OSPF) message.

[0134] Optionally, the ISIS message or the OSPFv3 message includes an SRv6 locator type length value (TLV), the SRv6 locator TLV includes the first address prefix, Flex-Algo information, the BFR ID of the first node, and the address of the first node; or, the ISIS message or the OSPFv3 message includes an IPv6 TLV, the IPv6 TLV includes the first address prefix, Flex-Algo information, the BFR ID of the first node, and the address of the first node.

[0135] In one example, the first node sends a first address prefix, Flex-Algo information, a BFR ID of the first node, and an address of the first node in the following manner: the first node sends a first correspondence and a second correspondence, the first correspondence includes the first address prefix, the BFR ID of the first node, and the address of the first node, the second correspondence includes the second address prefix and the Flex-Algo information, and the second address prefix includes the first address prefix or the address of the first node. For example, when the first address prefix is ​​the address prefix corresponding to the SRv6 locator of the first node, the second address prefix is ​​SRv6locator, the second address prefix includes the first address prefix, and the second address prefix includes the address of the first node. For another example, when the first address prefix is ​​the address prefix of the loopback interface of the first node, the second address prefix is ​​SRv6 locator, and the second address prefix includes the address of the first node. The above correspondence can be published through the type length value (TLV) of the ISIS or OSFP message.

[0136] In step S403, whether the first node uses ISIS or OSPF to publish is determined by the BIER publishing protocol in step S401. That is, the first node obtains the configured BIER publishing protocol and uses the BIER publishing protocol to publish the above information. For example, if the configured publishing protocol is isis srv6-locator, isis srv6-locator TLV is used for publishing; if the configured publishing protocol is isis, isis ipv6 TLV is used for publishing; if the configured publishing protocol is ospfv3 srv6-locator, ospfv3 srv6-locator TLV is used for publishing; if the configured publishing protocol is ospfv3, ospfv3ipv6 TLV is used for publishing.

[0137] The following describes the TLV formats when using these publishing protocols:

[0138] When the first address prefix is ​​an address prefix corresponding to the SRv6 locator of the first node, the publishing protocol is isissrv6-locator or ospfv3 srv6-locator.

[0139] Figure 6 1 is a schematic diagram of the structure of an isis srv6-locator TLV provided in an embodiment of the present application. Figure 6 :isis srv6-locator TLV includes Flex-Algo information (Algorithm) and BIER information sub-TLV (BIER infosub TLV). The BIER information sub-TLV includes the BFR ID of the first node and the END BIER information sub-TLV (END.BIER info sub TLV). The END BIER information sub-TLV includes the address of the first node (End.BIER IPv6 Address). The address of the first node consists of two parts: SRv6 locator and Fuction. The first prefix address reuses the SRv6 locator, and the second prefix address includes the address of the first node or the first prefix address. Therefore, the TLV includes the correspondence between the first address prefix, the BFR ID of the first node and the address of the first node, and also includes the correspondence between the second address prefix and the Flex-Algo information.

[0140] In addition to using the Algorithm field in the message to identify the Flex-Algo information, you can also use a custom field in the isis srv6-locator TLV or other TLVs to identify the Flex-Algo information.

[0141] Figure 7 Schematic diagram of the structure of an ospfv3 srv6-locator provided in an embodiment of the present application. Figure 7 :

[0142] ospfv3 srv6-locator includes Flex-Algo information (Algorithm), the first address prefix (Locator) and BIER information sub-TLV (BIER info sub TLV), the BIER information sub-TLV includes the BFR ID of the first node and ENDBIER information sub-TLV (END.BIER information sub TLV), and the END BIER information sub-TLV includes the address of the first node (End.BIER IPv6 Address). The first prefix address reuses the SRv6 locator, and the second prefix address includes the address of the first node or the first prefix address. Therefore, the TLV includes the correspondence between the first address prefix, the BFR ID of the first node and the address of the first node, and also includes the correspondence between the second address prefix and the Flex-Algo information.

[0143] When the first address prefix is ​​the address prefix of the loopback interface of the first node, the publishing protocol is isis or ospfv3.

[0144] Figure 8 This is a schematic diagram of the structure of an isis ipv6 TLV provided in an embodiment of the present application. Figure 8 :

[0145] The isis ipv6 TLV can be an IS-IS IPv6 AlgorithmPrefix Reachabilty TLV. The isis ipv6 TLV includes Flex-Algo information (Algorithm), a first address prefix (Prefix) and extended sub-TLVs. The extended sub-TLV includes the BFR ID of the first node and the address of the first node (End.BIER IPv6 Address). The address of the first node consists of two parts: SRv6 locator and Fuction. The second prefix address includes the address of the first node. Therefore, the TLV includes the correspondence between the first address prefix, the BFR ID of the first node and the address of the first node, and also includes the correspondence between the second address prefix and the Flex-Algo information.

[0146] Fig. 9 This is a schematic diagram of the structure of an ospfv3 ipv6 TLV provided in an embodiment of the present application. Fig. 9 :

[0147] The ospfv3 ipv6 TLV can be an intra-area-prefix TLV / inter-area-prefix TLV, or an external-prefix TLV. The ospfv3 ipv6 TLV includes the first address prefix (Address Prefix), the OSPFv3 IPv6 algorithm prefix reachability sub-TLV (OSPFv3 IPv6Algorithm Prefix Reachabilty Sub-TLV) and the extended sub-TLV (Sub-TLVs). The OSPFv3 IPv6 algorithm prefix reachability sub-TLV includes Flex-Algo information (Algorithm), and the extended sub-TLV includes the BFR ID of the first node and the address of the first node (End.BIER IPv6 Address). The address of the first node consists of two parts: SRv6 locator and Fuction, and the second prefix address includes the address of the first node. Therefore, the TLV includes the correspondence between the first address prefix, the BFR ID of the first node and the address of the first node, and also includes the correspondence between the second address prefix and the Flex-Algo information.

[0148] In step 403, there may be multiple first nodes, for example, nodes B to G are all first nodes, and these first nodes all publish their own information in the domain. The second node receives the information published by these first nodes and determines the forwarding information based on the information. For intermediate nodes such as B or C, the BFR ID they publish is 0.

[0149] S404: The second node obtains forwarding information based on the information of the first node, where the forwarding information includes a next hop and a BFR ID of the first node, and the next hop is a next hop corresponding to the Flex-Algo information.

[0150] In this step, the second node determines BIRT based on the information of the first node; then determines BIFT based on BIRT. When determining BIRT based on the information of the first node, the second node obtains the second address prefix, and the second address prefix includes the first address prefix or the address of the first node; the second node obtains the next hop based on the second address prefix and the Flex-Algo information, and the next hop is the next hop that matches the Flex-Algo information in the next hop to the second address prefix. Among them, the second address prefix can be obtained from the address of the first node, and the Locator of the address of the first node is determined by the Locator length. Alternatively, the Locator included in the information of the first node is directly obtained. For example, the address of the first node is 2001:DB8:100:1, and the second address prefix obtained therefrom is 2001:DB8:100:: / 64. Among them, after obtaining the second address prefix, the second node determines the next hop corresponding to the second address prefix according to the correspondence between the second address prefix and the Flex-Algo information. For example, when there are multiple paths to the first prefix address, one that complies with the Flex-Algo information is selected; when there is only one path to the first prefix address, the path is the one corresponding to the Flex-Algo information.

[0151] by Figure 2 For example, based on the received information of nodes D to E, the corresponding BIRT under the two planes of Flex-Algo 128 and Flex-Algo 128 is calculated. Figure 2 Type a path in Flex-Algo 128 is preferred. Figure 2 The path indicated by the medium bold line is excluded by Flex-Algo 129 Figure 2 Type a path in the Flex-Algo 129 algorithm is preferred to exclude Figure 2 The path represented by the bold line is Figure 2 The thin line in the figure represents the type b path. Affinity refers to the path that is preferred when selecting a path, and exclusion refers to the path that is excluded when selecting a path.

[0152] In the Flex-Algo 128 plane, the next hop to D is E, the next hop to E is E, the next hop to F is F, and the next hop to G is G. BIRT is shown in Table 1 below:

[0153] Table 1 BIRT

[0154] BFR ID BFR prefix of the destination BFER BFR-NBR 1 D E 2 E E 3 F F 4 G G

[0155] Among them, BFR-NBR is also the next hop node to the destination BFER.

[0156] In the Flex-Algo 129 plane, the next hop to D is D, the next hop to E is B, the next hop to F is B, and the next hop to G is B. BIRT is shown in Table 2 below:

[0157] Table 2 BIRT

[0158] BFR ID BFR prefix of the destination BFER BFR-NBR 1 D D 2 E B 3 F B 4 G B

[0159] After determining the BIRT, determine the BIFT as follows: convert the BFR ID into the corresponding bitstring; perform an OR operation on the bitstrings corresponding to the BFR IDs with the same BFR-NBR entry in the BIRT to obtain a forwarding bitmask (F-BM); obtain the BIFT based on the F-BM and the BFR-NBR. Taking the BIRT shown in Table 1 as an example, convert the BFRID into the corresponding bitstring, the bitstring corresponding to BFR ID=1 is 0001, the bitstring corresponding to BFR ID=2 is 0010, the bitstring corresponding to BFR ID=3 is 0100, and the bitstring corresponding to BFR ID=4 is 1000; perform an operation on the bitstrings 0001 and 0010 corresponding to the two items with BFR-NBR of E in Table 1 to obtain an F-BM of 0011.

[0160] Through the above calculations, the BIFT is obtained as shown in Table 3 below:

[0161] Table 3 BIFT

[0162] F-BM BFR-NBR 0011 E 0100 F 1000 G

[0163] In an embodiment of the present application, since the prefix address is associated with Flex-Algo, the BIRT determined by BIERv6 is also associated with Flex-Algo, so that BIRT can distinguish the forwarding planes, so that different services can use different forwarding planes under BIERv6.

[0164] Fig.10It is a block diagram of a device for publishing information provided by an embodiment of the present application. The device for publishing information can be implemented as all or part of the first node through software, hardware, or a combination of both. The device 400 for publishing information may include: an acquisition unit 401 and a sending unit 402. Among them, the acquisition unit 401 is used to acquire the first address prefix, the flexible algorithm Flex-Algo information, the bit forwarding router identifier BFR ID of the first node in the BIER domain explicitly replicated based on the bit index, and the address of the first node; the sending unit 402 is used to send the first address prefix, Flex-Algo information, the BFR ID of the first node and the address of the first node.

[0165] Optionally, the first address prefix is ​​an address prefix of a loopback interface of the first node; or the first address prefix is ​​an address prefix corresponding to a segment routing SRv6 location identifier based on Internet Protocol IPv6 of the first node.

[0166] Optionally, the sending unit 402 is used to send an intermediate system to intermediate system ISIS message or an open shortest path first OSPFv3 message, where the ISIS message or OSPFv3 message includes the first address prefix, Flex-Algo information, the BFR ID of the first node and the address of the first node.

[0167] Optionally, the ISIS message or OSPFv3 message includes an SRv6 locator TLV, the SRv6 locator TLV includes the first address prefix, Flex-Algo information, the BFR ID of the first node and the address of the first node; or the ISIS message or OSPFv3 message includes an IPv6 TLV, the IPv6 TLV includes the first address prefix, Flex-Algo information, the BFRID of the first node and the address of the first node.

[0168] Optionally, the sending unit 402 is used to send a first correspondence relationship and a second correspondence relationship, the first correspondence relationship includes a first address prefix, a BFR ID of the first node and the address of the first node, the second correspondence relationship includes a second address prefix and Flex-Algo information, and the second address prefix includes the first address prefix or the address of the first node.

[0169] Optionally, the first node is an intermediate BFR or a bit forwarding egress router BFER.

[0170] The information publishing device provided in the above embodiment is only illustrated by the division of the above functional units. In practical applications, the above functions can be assigned to different functional units as needed, that is, the internal structure of the device is divided into different functional units to complete all or part of the functions described above. In addition, the information publishing device provided in the above embodiment and the information publishing method embodiment belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0171] Fig.11 It is a block diagram of a device for obtaining forwarding information provided by an embodiment of the present application. The device for obtaining forwarding information can be implemented as all or part of the second node through software, hardware, or a combination of both. The device 500 for obtaining forwarding information may include: a first acquisition unit 501 and a second acquisition unit 502. Among them, the first acquisition unit 501 is used to obtain information of the first node in the BIER domain based on bit index explicit replication, and the information of the first node includes the first address prefix, the flexible algorithm Flex-Algo information, the bit forwarding router identifier BFR ID of the first node and the address of the first node; the second acquisition unit 502 is used to obtain forwarding information based on the information of the first node, and the forwarding information includes the next hop and the BFR ID of the first node, and the next hop is the next hop corresponding to the Flex-Algo information.

[0172] Optionally, the first address prefix is ​​an address prefix of a loopback interface of the first node; or the first address prefix is ​​an address prefix corresponding to a segment routing SRv6 location identifier based on Internet Protocol IPv6 of the first node.

[0173] Optionally, the first acquiring unit 501 is used to receive an ISIS message or an OSPFv3 message, where the ISIS message or the OSPFv3 message includes the first address prefix, Flex-Algo information, a BFR ID of the first node, and the address of the first node.

[0174] Optionally, the second acquisition unit 502 is used to obtain a second address prefix, which includes the first address prefix or the address of the first node; based on the second address prefix and the Flex-Algo information, obtain the next hop, which is the next hop that matches the Flex-Algo information in the next hop to reach the second address prefix; based on the next hop and the BFR ID of the first node, obtain forwarding information.

[0175] Optionally, the device is an intermediate BFR or a bit forwarding ingress router BFIR; the first node is an intermediate BFR or a bit forwarding egress router BFER.

[0176] The device for obtaining forwarding information provided in the above embodiment is only illustrated by the division of the above functional units. In actual applications, the above functions can be assigned to different functional units as needed, that is, the internal structure of the device is divided into different functional units to complete all or part of the functions described above. In addition, the device for obtaining forwarding information provided in the above embodiment and the method embodiment for obtaining forwarding information belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0177] Fig.12 1 is a schematic diagram of a network device 1000 provided in an embodiment of the present application. The network device 1000 may be the aforementioned first node, and the network device 1000 includes at least one processor 1001 , a memory 1002 , and at least one network interface 1003 .

[0178] Optionally, combined Figure 2 From the network deployment scenario shown in the figure, Fig.12 The network device 1000 shown is Figure 2 Any node in .

[0179] Optionally, combined Figure 3 According to the method flow shown, Fig.12 The network device 1000 is used to perform Figure 3 In the method shown, the processor 1001 is used to support the network device to execute S201, and the network interface 1003 is used to support the network device to execute S202.

[0180] Optionally, combined Figure 4 According to the method flow shown, Fig.12 The network device 1000 is used to perform Figure 4 In the method shown, the network interface 1003 is used to support the network device to execute S301, and the processor 1001 is used to support the network device to execute S302.

[0181] The processor 1001 is, for example, a general-purpose central processing unit (CPU), a network processor (NP), a graphics processing unit (GPU), a neural-network processing unit (NPU), a data processing unit (DPU), a microprocessor, or one or more integrated circuits for implementing the solution of the present application. For example, the processor 1001 includes an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD is, for example, a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0182] The memory 1002 is, for example, a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. Optionally, the memory 1002 exists independently and is connected to the processor 1001 through the internal connection 1004. Alternatively, the memory 1002 and the processor 1001 are optionally integrated together.

[0183] The network interface 1003 uses any transceiver-like device for communicating with other devices or communication networks. The network interface 1003 includes, for example, at least one of a wired network interface or a wireless network interface. The wired network interface is, for example, an Ethernet interface. The Ethernet interface is, for example, an optical interface, an electrical interface, or a combination thereof. The wireless network interface is, for example, a cellular network interface, or a combination thereof.

[0184] In some embodiments, the processor 1001 includes one or more CPUs, such as Fig.12 CPU0 and CPU1 are shown in the figure.

[0185] In some embodiments, the network device 1000 may optionally include multiple processors, such as Fig.12 1001 and 1005 are shown in FIG. Each of these processors is, for example, a single-CPU, or a multi-CPU. The processor herein optionally refers to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).

[0186] In some embodiments, the network device 1000 further includes an internal connection 1004. The processor 1001, the memory 1002, and the at least one network interface 1003 are connected via the internal connection 1004. The internal connection 1004 includes a path to transmit information between the above components. Optionally, the internal connection 1004 is a single board or a bus. Optionally, the internal connection 1004 is divided into an address bus, a data bus, a control bus, etc.

[0187] In some embodiments, the network device 1000 further includes an input / output interface 1006. The input / output interface 1006 is connected to the internal connection 1004.

[0188] In some embodiments, the input-output interface 1006 is used to connect to an input device to receive commands or data involved in the above-mentioned method embodiments input by a user through the input device, such as setting commands, setting expected results of commands, setting regular expressions corresponding to commands, address information corresponding to the forensic server, setting strings, etc.

[0189] Optionally, the processor 1001 implements the method in the above embodiment by reading the program code 1010 stored in the memory 1002, or the processor 1001 implements the method in the above embodiment by the program code stored internally. In the case where the processor 1001 implements the method in the above embodiment by reading the program code 1010 stored in the memory 1002, the memory 1002 stores the program code for implementing the method provided in the embodiment of the present application.

[0190] For more details on how the processor 1001 implements the above functions, please refer to the descriptions in the previous method embodiments, which will not be repeated here.

[0191] Fig.13 A schematic diagram of the hardware structure of another network device 1200 provided in an embodiment of the present application. Fig.13 The network device 1200 shown can execute the corresponding steps executed by the first node or the second node in the method of the above embodiment.

[0192] like Fig.13 The network device 1200 includes: a main control board 1210, an interface board 1230, a switching board 1220 and an interface board 1240. The main control board 1210, the interface boards 1230 and 1240, and the switching board 1220 are connected to the system backplane through a system bus to achieve intercommunication. Among them, the main control board 1210 is used to complete functions such as system management, equipment maintenance, and protocol processing. The switching board 1220 is used to complete data exchange between various interface boards (interface boards are also called line cards or service boards). The interface boards 1230 and 1240 are used to provide various service interfaces (for example, POS interfaces, GE interfaces, ATM interfaces, etc.) and realize the forwarding of data packets.

[0193] The interface board 1230 may include a central processor 1231, a forwarding table entry memory 1234, a physical interface card 1233, and a network processor 1232. The central processor 1231 is used to control and manage the interface board and communicate with the central processor on the main control board. The forwarding table entry memory 1234 is used to store forwarding table entries. The physical interface card 1233 is used to complete the reception and transmission of traffic. The network memory 1232 is used to control the physical interface card 1233 to receive and send traffic according to the forwarding table entries.

[0194] Specifically, the central processor 1211 is used to obtain the information of the first node. The physical interface card 1233 is used to send the information of the first node.

[0195] Alternatively, the physical interface card 1233 is used to obtain the information of the first node. The central processor 1211 is used to obtain the forwarding information based on the information of the first node.

[0196] It should be understood that the operation on the interface board 1240 in the embodiment of the present invention is consistent with the operation of the interface board 1230, and for the sake of brevity, it will not be repeated. It should be understood that the network device 1200 of this embodiment can correspond to the functions and / or various steps implemented in the above method embodiment, and it will not be repeated here.

[0197] In addition, there may be one or more main control boards, and when there are multiple boards, they may include a primary main control board and a standby main control board. There may be one or more interface boards. The stronger the data processing capability of the network device, the more interface boards are provided. There may also be one or more physical interface cards on the interface board. There may be no switching network board, or there may be one or more switching network boards. When there are multiple switching network boards, they can jointly realize load sharing and redundant backup. In a centralized forwarding architecture, the network device may not need a switching network board, and the interface board is responsible for the processing function of the service data of the entire system. In a distributed forwarding architecture, the network device may have at least one switching network board, and the switching network board is used to realize data exchange between multiple interface boards, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of the network device with a distributed architecture are greater than those of the device with a centralized architecture. Which architecture to adopt depends on the specific networking deployment scenario, and no limitation is made here.

[0198] In some embodiments, a computer program product is also provided, which includes one or more computer program instructions. When the computer program instructions are loaded and executed by a computer, the computer executes the method provided by the above method embodiment.

[0199] In some embodiments, a chip is also provided, including a memory and a processor, wherein the memory is used to store computer instructions, and the processor is used to call and run the computer instructions from the memory to execute the method provided by the above method embodiment.

[0200] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. A refers to B, which means that A is the same as B or A is a simple deformation of B. The terms "first" and "second" in the description and claims of the embodiments of the present application are used to distinguish different objects, rather than to describe the specific order of objects, and cannot be understood as indicating or implying relative importance. For example, the first node and the second node are used to distinguish different nodes, rather than to describe the specific order of nodes, and cannot be understood as the first node is more important than the second node. In the embodiments of the present application, unless otherwise specified, the meaning of "at least one" refers to one or more, and the meaning of "multiple" refers to two or more.

[0201] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in accordance with the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk SolidState Disk (SSD)), etc.

[0202] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for publishing information, characterized in that: The method comprises: Based on the bit index, explicitly copy the first node in the BIER domain to obtain the first address prefix, the flexible algorithm Flex-Algo information, the bit forwarding router identifier BFRID of the first node and the address of the first node; The first node sends the first address prefix, the Flex-Algo information, the BFR ID of the first node, and the address of the first node.

2. The method according to claim 1, characterized in that The first address prefix is ​​an address prefix of a loopback interface of the first node; or, The first address prefix is ​​an address prefix corresponding to the Internet Protocol IPv6-based segment routing SRv6 location identifier of the first node.

3. The method according to claim 1 or 2, characterized in that: The first node sends the first address prefix, the Flex-Algo information, the BFRID of the first node, and the address of the first node, including: The first node sends an Intermediate System to Intermediate System (ISIS) message or an Open Shortest Path First (OSPFv3) message, where the ISIS message or the OSPFv3 message includes the first address prefix, the Flex-Algo information, the BFR ID of the first node, and the address of the first node.

4. The method according to claim 3, characterized in that The ISIS message or the OSPFv3 message includes an SRv6 location identifier type length value TLV, where the SRv6 location identifier TLV includes the first address prefix, the Flex-Algo information, the BFRID of the first node, and the address of the first node; or, The ISIS message or the OSPFv3 message includes an Internet Protocol version 6 IPv6 TLV, and the IPv6 TLV includes the first address prefix, the Flex-Algo information, the BFR ID of the first node, and the address of the first node.

5. The method according to any one of claims 1 to 4, characterized in that: The first node sends the first address prefix, the Flex-Algo information, the BFRID of the first node, and the address of the first node, including: The first node sends a first correspondence and a second correspondence, the first correspondence includes the first address prefix, the BFR ID of the first node and the address of the first node, the second correspondence includes the second address prefix and the Flex-Algo information, and the second address prefix includes the first address prefix or the address of the first node.

6. The method according to any one of claims 1 to 5, characterized in that: The first node is an intermediate BFR or a bit forwarding egress router BFER.

7. A method for obtaining forwarding information, characterized in that: The method comprises: Obtain information of the first node by explicitly copying the second node in the BIER domain based on the bit index, where the information of the first node includes the first address prefix, the flexible algorithm Flex-Algo information, the bit forwarding router identifier BFR ID of the first node and the address of the first node; The second node obtains forwarding information based on the information of the first node, where the forwarding information includes a next hop and a BFRID of the first node, and the next hop is a next hop corresponding to the Flex-Algo information.

8. The method according to claim 7, characterized in that The first address prefix is ​​an address prefix of a loopback interface of the first node; or, The first address prefix is ​​an address prefix corresponding to the Internet Protocol IPv6-based segment routing SRv6 location identifier of the first node.

9. The method according to claim 7 or 8, characterized in that: The second node obtains the information of the first node, including: The second node receives an ISIS message or an OSPFv3 message, where the ISIS message or the OSPFv3 message includes the first address prefix, the Flex-Algo information, the BFR ID of the first node, and the address of the first node.

10. The method according to any one of claims 7 to 9, characterized in that: The second node acquires forwarding information based on the information of the first node, including: The second node acquires a second address prefix, where the second address prefix includes the first address prefix or the address of the first node; The second node acquires the next hop based on the second address prefix and the Flex-Algo information, where the next hop is a next hop matching the Flex-Algo information among the next hops reaching the second address prefix; The second node obtains the forwarding information based on the next hop and the BFR ID of the first node.

11. The method according to any one of claims 7 to 10, characterized in that: The second node is an intermediate BFR or a bit forwarding ingress router BFIR; The first node is an intermediate BFR or a bit forwarding egress router BFER.

12. A device for publishing information, characterized in that: The device comprises: An acquisition unit, used to acquire a first address prefix, flexible algorithm Flex-Algo information, a bit forwarding router identifier BFRID of a first node in a BIER domain explicitly copied based on a bit index, and the address of the first node; A sending unit is used to send the first address prefix, the Flex-Algo information, the BFR ID of the first node and the address of the first node.

13. The device according to claim 12, characterized in that The first address prefix is ​​an address prefix of a loopback interface of the first node; or, The first address prefix is ​​an address prefix corresponding to the Internet Protocol IPv6-based segment routing SRv6 location identifier of the first node.

14. The device according to claim 12 or 13, characterized in that The sending unit is used to send an intermediate system to intermediate system ISIS message or an open shortest path first OSPFv3 message, wherein the ISIS message or the OSPFv3 message includes the first address prefix, the Flex-Algo information, the BFR ID of the first node and the address of the first node.

15. The device according to claim 14, characterized in that The ISIS message or the OSPFv3 message includes an SRv6 location identifier type length value TLV, where the SRv6 location identifier TLV includes the first address prefix, the Flex-Algo information, the BFRID of the first node, and the address of the first node; or, The ISIS message or the OSPFv3 message includes an Internet Protocol version 6 IPv6 TLV, and the IPv6 TLV includes the first address prefix, the Flex-Algo information, the BFR ID of the first node, and the address of the first node.

16. The device according to any one of claims 12 to 15, characterized in that The sending unit is used to send a first correspondence relationship and a second correspondence relationship, wherein the first correspondence relationship includes the first address prefix, the BFR ID of the first node and the address of the first node, and the second correspondence relationship includes the second address prefix and the Flex-Algo information, and the second address prefix includes the first address prefix or the address of the first node.

17. The device according to any one of claims 12 to 16, characterized in that The first node is an intermediate BFR or a bit forwarding egress router BFER.

18. A device for obtaining forwarding information, characterized in that: The device comprises: A first acquisition unit is used to acquire information of a first node in a BIER domain explicitly replicated based on a bit index, the information of the first node including a first address prefix, flexible algorithm Flex-Algo information, a bit forwarding router identifier BFRID of the first node, and an address of the first node; The second acquisition unit is used to acquire forwarding information based on the information of the first node, where the forwarding information includes a next hop and a BFRID of the first node, and the next hop is a next hop corresponding to the Flex-Algo information.

19. The device according to claim 18, characterized in that The first address prefix is ​​an address prefix of a loopback interface of the first node; or, The first address prefix is ​​an address prefix corresponding to the Internet Protocol IPv6-based segment routing SRv6 location identifier of the first node.

20. The device according to claim 18 or 19, characterized in that The first acquisition unit is used to receive an ISIS message or an OSPFv3 message, where the ISIS message or the OSPFv3 message includes the first address prefix, the Flex-Algo information, the BFR ID of the first node, and the address of the first node.

21. The device according to any one of claims 18 to 20, characterized in that The second acquiring unit is configured to acquire a second address prefix, where the second address prefix includes the first address prefix or the address of the first node; Based on the second address prefix and the Flex-Algo information, acquiring the next hop, where the next hop is a next hop that matches the Flex-Algo information among the next hops to reach the second address prefix; The forwarding information is obtained based on the next hop and the BFRID of the first node.

22. The device according to any one of claims 18 to 21, characterized in that The device is an intermediate BFR or a bit forwarding ingress router BFIR; The first node is an intermediate BFR or a bit forwarding egress router BFER.

23. A network device, characterized in that: The network device comprises a processor and a memory, wherein the memory is used to store a software program, and the processor runs or executes the software program stored in the memory so that the network device implements the method according to any one of claims 1 to 11.

24. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store program codes executed by a processor, wherein the program codes include instructions for implementing the method according to any one of claims 1 to 11.

25. A computer program product, characterized in that The computer program product comprises program codes, and when a computer runs the computer program product, the computer executes the method according to any one of claims 1 to 11.

Citation Information

Cited By

  • Communication method, electronic device, and apparatus

    WO2026050892A1