Method, device, equipment and storage medium for information transmission and distribution tree establishment

Abstract

The present application proposes a method, device, equipment and storage medium for information transmission and distribution tree establishment, including: determining the processing capability of the node for the multicast join message join attribute; notifying the processing capability information of the multicast join message join attribute to the network, wherein the processing capability information of the multicast join message join attribute is used to indicate the processing capability of the node for the join attribute carried by the multicast join message. This enables the controller or router in the network to perceive and determine which routers in the local routing area support or do not support processing of the join attribute, thereby automatically building a multicast distribution tree that meets specific requirements.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, apparatus, device and storage medium for information sending and distribution tree establishment. Background Art

[0002] The establishment of a basic multicast distribution tree relies only on unicast routing to the source or aggregation point. However, with the emergence of new application scenarios, the protocol allows the inclusion of a join attribute field in the join message, which will affect the construction of the multicast distribution tree.

[0003] Carrying join attributes in multicast join messages helps build multicast distribution trees with special requirements, but this requires that each router that receives a multicast join message with join attributes has the ability to process the attribute to prevent loops. However, there are still some problems in application. The discovery message of the protocol-independent multicast protocol is a single-hop multicast message. Only routers connected to the same link can discover each other's ability to process join attributes. That is, the controller or router in the network cannot perceive and determine which routers in the local routing area support or do not support processing join attributes. At present, when using join attributes, network administrators need to manually calculate and fill in specific information, so there are problems such as poor flexibility and inability to respond to changes in network topology or router capabilities in a timely manner. Summary of the invention

[0004] The present application provides a method, apparatus, device and storage medium for information transmission and distribution tree establishment, so as to enable a controller or router in a network to perceive and determine which routers in a local routing area support or do not support processing of join attributes, thereby automatically building a multicast distribution tree that meets specific requirements.

[0005] In a first aspect, an embodiment of the present application provides an information sending method, including:

[0006] Determine the processing capability of the node to process the join attributes of multicast join messages;

[0007] The processing capability information of the join attribute of the multicast join message is notified to the network, wherein the processing capability information of the join attribute of the multicast join message is used to indicate the processing capability of the node for the join attribute carried by the multicast join message.

[0008] In a second aspect, an embodiment of the present application provides a distribution tree establishment method, including:

[0009] Receive the processing capability information of the join attribute of the multicast join message of each node;

[0010] A multicast distribution tree is established based on the processing capability information of the multicast join message join attribute of each node.

[0011] In a third aspect, an embodiment of the present application provides an information sending device, including:

[0012] The sending module is configured to determine the processing capability of the node for adding attributes of a multicast adding message; and to notify the processing capability information of the adding attributes of the multicast adding message to the network, wherein the processing capability information of the adding attributes of the multicast adding message is used to indicate the processing capability of the node for the adding attributes carried by the multicast adding message.

[0013] In a fourth aspect, an embodiment of the present application provides a distribution tree establishment device, including:

[0014] A receiving module, configured to receive processing capability information of a join attribute of a multicast join message of each node;

[0015] The establishing module is configured to establish a multicast distribution tree based on the processing capability information of the multicast joining message joining attribute of each node.

[0016] In a fifth aspect, an embodiment of the present application provides a device, including:

[0017] one or more processors;

[0018] A memory for storing one or more programs;

[0019] When the one or more programs are executed by the one or more processors, the one or more processors implement any one of the methods in the embodiments of the present application.

[0020] In a sixth aspect, an embodiment of the present application provides a storage medium, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, any one of the methods in the embodiments of the present application is implemented.

[0021] With regard to the above embodiments and other aspects of the present application and their implementation, further description is provided in the accompanying drawings, detailed description and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 A flowchart of a method for sending information provided by this application;

[0023] Figure 2 A flow chart of a distribution tree establishment method provided in this application;

[0024] Figure 3 This is an information structure diagram provided by the present application for notifying the multicast join message join attribute processing capability in IGP and BGP-LS;

[0025] Figure 4It is a flowchart of a method for notifying multicast join message join attribute processing capability provided by the present application;

[0026] Figure 5 It is a flow chart of a method for dynamically determining a multicast distribution tree based on multicast join message join attribute processing capability information of each node in a network provided by the present application;

[0027] Figure 6 It is a schematic diagram of the original topology of the multicast distribution tree for constructing a dual-active elastic protection backup path;

[0028] Figure 7 It is a schematic diagram of the topological structure of the active-active elastic protection backup path after being trimmed based on the multicast join message join attribute processing capability;

[0029] Figure 8 It is a schematic diagram of the structure of a router provided by the present application for notifying the multicast join message join attribute processing capability and building a multicast distribution tree;

[0030] Fig. 9 A schematic diagram of the structure of an information sending device provided by the present application;

[0031] Fig.10 A schematic diagram of the structure of a distribution tree establishment device provided in this application;

[0032] Fig.11 It is a structural schematic diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to make the purpose, technical solution and advantages of the present application more clear, the embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features in the embodiments of the present application can be combined with each other arbitrarily without conflict.

[0034] The steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions. Also, although a logical sequence is shown in the flowchart, in some cases, the steps shown or described can be performed in a sequence different from that shown here.

[0035] First, the concepts involved in multicast technology are briefly explained.

[0036] Multicast technology provides efficient point-to-multipoint traffic transmission. The current mainstream Protocol Independent Multicast (PIM) protocol builds a multicast distribution tree with a multicast source or aggregation point as the root and traffic receivers as leaves. Traffic flows from the root to the leaves along the multicast distribution tree, and is only replicated at the branch nodes to reach multiple receivers. In a multicast network, the network device connected to the multicast traffic receiver is called the last hop router, the network device connected to the multicast source is called the source router, and the network device where the aggregation point is located is called the aggregation point router. Multicast routers advertise the Layer 3 multicast capability and establish multicast neighbors by exchanging protocol-independent multicast protocol discovery messages on the interface link. In the unicast routing table, the outbound interface and next-hop device to the source or aggregation point are respectively called the reverse path forwarding interface and multicast upstream neighbor for the source or aggregation point. The last-hop router uses the join message to the source or aggregation point in the protocol-independent multicast protocol to build a multicast distribution tree. The last-hop router sends a multicast join message to its multicast upstream neighbor, and the upstream neighbor continues to forward the join message to its upstream neighbor until it finally reaches the designated source router or aggregation point router, completing the multicast distribution tree built from the leaf to the root. Multicast traffic propagates from the root to the leaf on the multicast distribution tree. Any multicast traffic received by a multicast router on a non-reverse path forwarding interface will be discarded to prevent loops and duplicate traffic; the multicast router propagates the traffic received from the reverse path forwarding interface to the downstream outbound interface.

[0037] The basic construction of multicast distribution tree relies only on unicast routing to the source or aggregation point, but with the emergence of new application scenarios, the protocol allows the inclusion of a join attribute field in the join message, which will affect the construction of the multicast distribution tree. For example, within a routing area, the border router connects to the external area, the core router is used to connect to the border router, and the external routing information is directly transmitted between the border routers. That is, the core router only has routing information to each border router and does not need to learn external routing information to reduce the burden on the core router. When the multicast source / aggregation point and the receiver are in the external area connected to different border routers, there will be problems in building a multicast distribution tree across the core area, because the core area router does not have a unicast route to the external multicast source / aggregation point and cannot determine the multicast upstream neighbor. To solve this problem, the protocol defines a reverse path forwarding vector (RPFVector) join attribute, which indicates the address of the border router connected to the multicast source / aggregation point. When the core router receives the join message with the reverse path forwarding vector join attribute, it will no longer calculate the multicast upstream neighbors for the multicast source / aggregation point, but will calculate the multicast upstream neighbors with the border router indicated by the vector as the target, and build a multicast distribution tree with the border gateway router connected to the multicast source / aggregation point as the root and the border gateway router connected to the receiver as the leaf. For example, some multicast applications require active-active elastic protection to ensure high-reliability transmission, that is, the last-hop router receives traffic from two independent multicast distribution trees at the same time. When the transmission network is normal, the last-hop router forwards the traffic received from the primary multicast distribution tree to the receiver and discards the traffic received from the backup multicast distribution tree; when the traffic cannot be received from the primary multicast distribution tree due to a network failure, it starts to forward the traffic received from the backup multicast distribution tree. This requires that the paths of the primary and backup multicast distribution trees be independent of each other and have no intersection points to avoid the failure of the primary and backup multicast distribution trees at the same time due to a single point failure. The protocol defines a new attribute of the explicit reverse path vector (Explicit RPF Vector) to construct the backup multicast distribution tree. This attribute carries the information of each hop from the leaf to the root of the backup multicast distribution tree. When a router receives a multicast join message with the explicit reverse path vector join attribute, it does not need to calculate the multicast upstream neighbors for the multicast source / aggregation point, but directly sends a join message according to the upstream neighbors indicated by the attribute.

[0038] Carrying the join attribute in the multicast join message helps to build a multicast distribution tree with special requirements, but this requires that each router that receives the join message with the join attribute has the ability to process the attribute to prevent loops. If a router that does not have the processing capability receives a join message with the join attribute and ignores the join attribute that originally indicates the multicast upstream neighbor, and calculates the multicast upstream neighbor based on the multicast source / aggregation point, it is possible to send the join message back to the router that has already passed it. For this reason, the discovery message of the protocol-independent multicast protocol will be extended to carry the notification of the ability to process the join attribute. When a router finds that its multicast upstream neighbor does not support processing the join attribute, the multicast join message sent to the upstream neighbor must first remove the join attribute. However, there are still some problems in application. The discovery message of the protocol-independent multicast protocol is a single-hop multicast message. Only routers connected to the same link can discover each other's ability to process the join attribute. That is, the controller or router in the network cannot perceive and determine which routers in the local routing area support or do not support processing the join attribute. Taking the detailed reverse path vector addition attribute that provides active-active elastic protection as an example, the current method is that the network administrator manually calculates a backup multicast distribution tree that does not intersect with the primary multicast distribution tree and that each hop device can support the addition attribute, and then manually fills in the detailed reverse path vector addition attribute information. Obviously, manual participation has poor flexibility and cannot respond to changes in network topology or router capabilities in a timely manner; low scalability, heavy computing burden and easy errors when multiple multicast applications require active-active elastic protection.

[0039] In view of the fact that network controllers and routers cannot obtain the processing capabilities of other routers in the local routing area except for directly connected ones for the multicast join message addition attributes, and that manual participation is required when constructing a multicast distribution tree that is not simply a unicast route for multicast source / aggregation point, resulting in poor flexibility, low scalability, and easy errors, a method is provided in which a unicast link state protocol is used to describe the processing capabilities of routers for the multicast join message addition attributes and the protocol is announced in the routing area, so that each router participating in the link state protocol can grasp the processing capabilities of other routers in the routing area for the multicast join message addition attributes; the description information of the link state protocol for the processing capabilities of the multicast join message addition attributes is encoded and announced to the controller by the Border Gateway Protocol-LinkState (BGP-LS), so that the controller can grasp the capabilities of each router in the network. The router and the controller learn the capabilities of each router in the routing domain, so that the multicast distribution tree path that meets the requirements can be dynamically calculated.

[0040] In one embodiment, the present application provides a method for sending information, such as Figure 1 As shown, the information sending method provided in the embodiment of the present application includes steps S11 and S12.

[0041] S11. Determine the processing capability of the node for multicast join message join attributes.

[0042] S12. Notify the network of the processing capability information of the join attribute of the multicast join message, wherein the processing capability information of the join attribute of the multicast join message is used to indicate the processing capability of the current node for the join attribute carried by the multicast join message.

[0043] In one embodiment, the above information sending method is executed by each node in the routing area.

[0044] In one embodiment, a node refers to all routing devices in a routing area. It should be noted that the nodes, devices and routers in this embodiment are all routing devices in a routing area.

[0045] The processing capability information of the multicast join message join attribute may be understood as information indicating whether the node has the capability of processing the multicast join message join attribute, or may be understood as information indicating whether the node supports the multicast join message join attribute.

[0046] In one embodiment, if the processing capability information of the multicast join message's join attribute carries the processing capability identifier of the multicast join message's join attribute, it indicates that the node has the processing capability for the join attribute carried by the multicast join message. If the processing capability information of the multicast join message's join attribute does not carry the processing capability identifier of the multicast join message's join attribute, it indicates that the node does not have the processing capability for the join attribute carried by the multicast join message.

[0047] Further, in the present embodiment, the processing capability identifier of the join attribute of the multicast join message may be a newly defined Type-Length-Value (TLV) field or a newly defined flag bit in the existing link state protocol router capability object. That is, when the TLV field exists, it indicates that the node has the processing capability of the join attribute carried by the multicast join message, and when the TLV field does not exist, it indicates that the node does not have the processing capability of the join attribute carried by the multicast join message, or when the newly defined flag bit in the link state protocol router capability object is set to 1, it indicates that the node has the processing capability of the join attribute carried by the multicast join message, and when it is set to 0, it indicates that the node does not have the processing capability of the join attribute carried by the multicast join message. It should be noted that in the present embodiment, only the processing capability identifier of the join attribute of the multicast join message is described, but not limited.

[0048] In one embodiment, the processing capability information of the multicast join message join attribute further includes subtypes of the multicast join message join attribute supported by the node.

[0049] In one embodiment, since the join attribute can have multiple subtypes, different subtypes have different functions and require different processing methods, the specific subtypes that can be supported by the carrying device at the moment can be selected under the multicast join message join attribute capability information. If there are subtypes of the join attribute supported by the announcement node under the router capability information, it means that the router can only recognize and process the announced subtypes but cannot process the unannounced subtypes. If there are no subtypes of the join attribute supported by the announcement node under the router capability information, it is assumed by default that the multicast message join attribute can support processing of any subtype.

[0050] In one embodiment, the processing capability information of the multicast join message joining attribute is carried in the router capability information of the link state protocol IGP, or the processing capability information of the multicast join message joining attribute is carried in the group attribute information of the border gateway protocol-link state BGP-LS routing.

[0051] In one embodiment, the method further includes: when the processing capability of the multicast join attribute of the node changes, updating the processing capability information of the join attribute of the multicast join message in the IGP and BGP-LS.

[0052] In one embodiment, the updating of the processing capability information of the join attribute of the multicast join message includes one or more of the following: updating the processing capability identifier of the join attribute of the multicast join message, and updating the subtype of the join attribute supported by the node.

[0053] In one embodiment, updating the processing capability identifier of the multicast join message join attribute includes deleting the processing capability identifier of the multicast join message join attribute, or adding the processing capability identifier of the multicast join message join attribute.

[0054] Update the subtypes of the added attributes supported by the node, including adding the subtypes of the added attributes supported by the new node, or reducing the subtypes of the added attributes supported by the node.

[0055] It should be noted that in this embodiment, the subtypes of the added attributes supported by the node are complete, that is, when the support capability of a subtype of added attributes on the router changes, all the subtypes of added attributes currently supported must be notified at the same time, and incremental notification is not allowed, that is, only the changed subtype is not allowed to be notified.

[0056] In one embodiment, the present application provides a distribution tree establishment method, such as Figure 2 As shown, the distribution tree establishment method provided in the embodiment of the present application includes steps S21 and S22.

[0057] S21, receiving the processing capability information of the multicast join message join attribute of each node;

[0058] S22: Establish a multicast distribution tree based on the processing capability information of the multicast join message join attribute of each node.

[0059] In one embodiment, receiving the processing capability information of the multicast join message join attribute of each node includes: receiving the processing capability information of the multicast join message join attribute advertised by each node in IGP or BGP-LS.

[0060] In one embodiment, the establishment of a multicast distribution tree based on the processing capability information of the joining attributes of the multicast joining message of each node includes: retaining the nodes that meet the preset conditions in the original network topology structure to form a new network topology structure, wherein the preset conditions are determined by the processing capability information of the joining attributes of the multicast joining message; and establishing a multicast distribution tree on the new network topology structure.

[0061] In one embodiment, the nodes that meet the preset conditions include one or more of the following situations: a node that only has a multicast join message join attribute processing capability identifier and does not carry any subtype; a node that has a multicast join message join attribute processing capability identifier and the subtypes it carries include the required specific subtypes.

[0062] In this embodiment, nodes that do not have the ability to process the join attributes of multicast join messages, nodes that announce detailed join attribute subtypes but do not announce the required specific subtypes, and the connections where these nodes are located are deleted from the original network topology, and the backup multicast distribution tree branch paths to the multicast source / aggregation point are calculated based on the remaining network topology information.

[0063] In addition, it should be noted that when the joining attribute capability of a router in the network changes, it may trigger the recalculation of the multicast distribution tree.

[0064] In an applicable embodiment, a link state protocol and a border gateway protocol-link state are provided to notify an information structure of a multicast join message join attribute processing capability. Figure 3 This is an information structure diagram of a notification multicast join message join attribute processing capability provided by this application.

[0065] like Figure 3As shown, the link state protocol adds a multicast join message join attribute processing capability identifier in the router capability information. The Type field indicates that the join attribute is supported. Length indicates the total length of multiple join attribute subtypes carried later. Attribute-Type indicates the specific join attribute subtype; the F bit indicates whether it can be transparently transmitted. This bit is meaningful only when the multicast module of the router processes the specific join attribute of the multicast join message, so the F bit is set to 0 when the link state protocol capability is announced, and it is ignored and treated as 0 when receiving; the E bit in the join attribute indicates that this Attribute-Type is the last join attribute subtype carried by the multicast join message, but there is a Length field in the link state protocol to indicate the total number of Attribute-Type subtypes, so the E bit is set to 0 when the capability is announced and ignored when receiving.

[0066] If the link state protocol does not carry a specific join attribute subtype when announcing the join attribute capability of the multicast join message, the Length field is filled with 0, indicating that the router can process any subtype.

[0067] When the capability of a router changes and it no longer supports some previously announced join attribute subtypes or starts to support new subtypes, the router must re-advertise all currently supported join attribute subtypes in the link state protocol. When receiving the capability information of a router with a changed join attribute subtype in a multicast join message sent by other routers, the capability information of the corresponding router must be updated.

[0068] When generating node type network layer reachability information describing link state protocol node information, the border gateway protocol-link state adds a community attribute for describing the multicast join message join attribute processing capability.

[0069] In one embodiment, the method described in the present application for processing the join attribute capability information of a multicast join message by using a link state protocol and a border gateway protocol-link state notification network device includes the following processes:

[0070] The link state protocol module obtains the join attribute processing capability information of the local multicast function for the multicast join message, and announces the join attribute information in the router capability information of the link state protocol.

[0071] The joining attribute information can be understood as whether the router has the ability to process the joining attribute in the multicast joining message in the link state protocol. The link state protocol includes: Open Shortest Path First (OSPF) and Intermediate System to Intermediate System (IS-IS).

[0072] Since the join attribute of a multicast join message can have multiple subtypes, and different subtypes have different functions and require different processing methods, the supported join attribute subtypes can be carried in more detail under the router capability information. If there is a detailed type of announcement, it means that the router can only identify and process the subtype of the announcement and cannot process the subtype that is not announced; if there is no detailed type of announcement, it is assumed by default that it can support the processing of any subtype of the join attribute.

[0073] The subtypes of the join attribute of the multicast join message announced by the link state protocol are complete. That is, when the processing capability of a join attribute subtype on the router changes, all the join attribute subtypes currently supported must be announced together, and incremental announcements are not allowed.

[0074] When generating network layer reachability information of a node type, the Border Gateway Protocol-Link State adds a community attribute that describes the router's ability to process the attributes of a multicast join message.

[0075] Routers within the range of link state protocol information dissemination and controllers connected by border gateway protocol-link state can accurately understand the processing of the join attribute of the multicast join message by each router in the network. When building a multicast distribution tree that is not purely aimed at multicast source / aggregation point unicast routing, the controller or last hop router uses the ability of network devices to support join attributes as a limiting condition based on application requirements, and only calculates multicast upstream neighbors or complete paths between routers that have explicitly announced support for this sub-join attribute type or default announcement support for all attribute types.

[0076] The ability of the link state protocol and border gateway protocol-link state notification network device to process the join attributes of multicast join messages described in the present application, compared with the existing technology implementation, the controller and the router can accurately grasp the support status of each router in the network for the multicast join message join attribute processing capability, the controller or the last-hop router can perform dynamic calculations when constructing a multicast distribution tree that is not simply a unicast route targeting the multicast source / aggregation point, and actively avoid routers that do not support the join extension feature, without the need for human intervention, and the flexibility and scalability can be improved.

[0077] In an application example, a method for notifying a multicast join message join attribute processing capability is provided. Figure 4 This is a schematic diagram of the notification process provided by this application.

[0078] like Figure 4 As shown, the method for notifying the multicast join message join attribute processing capability mainly includes steps S31, S32, S33, S34, S35, and S36.

[0079] S31. The link state protocol module obtains information about the router's ability to process attributes of a multicast join message from the multicast module.

[0080] S32: If the router does not have the capability to process the join attribute, the join attribute information is not carried in the router capability information.

[0081] S33: If the ability to process the added attribute is available, determine whether it is necessary to notify the detailed added attribute subtype. If it is not necessary to notify the detailed added attribute subtype, directly execute S35. If it is necessary to notify the detailed added attribute subtype, directly execute S34.

[0082] S34. Add all currently supported subtypes in the added attribute information.

[0083] S35. Add attribute information to the router capability information.

[0084] If no subtype information is carried, it means that the router can support any subtype.

[0085] S36: When the processing capability of the router changes or the subtype changes, the process returns to S31 and refreshes the attribute information notification.

[0086] In an application example, a process of dynamically calculating the attribute information of multicast join messages by using each router is provided. Figure 5 As shown, the method for dynamically determining a multicast distribution tree based on joining attribute information mainly includes the steps: S41, S42, S43, S44, S45, and S46.

[0087] S41. The last hop router or controller learns the network topology and the processing status of each router on the joining attribute of the multicast joining message through the link state protocol or the border gateway protocol-link state.

[0088] S42: The last-hop router or controller receives a request from an application to calculate a specific non-basic routing multicast distribution tree.

[0089] S43. The routing calculation component of the last-hop router or controller removes the nodes and their links that do not support the multicast join attribute in the original network topology, and further removes the nodes and their links that clearly do not support the required specific join attribute subtype.

[0090] S44. The last-hop router or controller calculates the multicast upstream neighbor or complete path for the multicast source / aggregation point or other information on the existing node and link topology.

[0091] S45, determine whether the joining attribute information in the link state protocol or border gateway protocol-link state advertisement router capability information has changed, if not, do nothing. If changed, execute S46.

[0092] S46. Determine whether the capability change affects the calculated multicast upstream neighbors or paths. If not, do not perform any operation. If yes, return to execute S43.

[0093] Specifically, active-active resilient protection relies on the detailed reverse path vector attribute, a subtype of the join attribute of the multicast join message, to build a backup path multicast distribution tree. Each router in the routing domain that supports the detailed reverse path vector join attribute subtype announces it in the subtype of the join attribute of the router capability information of the link state protocol. If the router capability information of the link state protocol only announces support for the join attribute without carrying any detailed subtypes, it is assumed by default that all subtypes can be supported; if the router capability information does not announce the join attribute, or the announced join attribute carries other detailed subtypes but does not include the detailed reverse path vector subtype, it means that the router does not support processing multicast join messages with the detailed reverse path vector join attribute. When calculating the backup multicast distribution tree of active-active resilient protection, routers that do not have the ability to process the detailed reverse path vector join attribute subtype should be excluded.

[0094] The last-hop router uses the traditional calculation method when calculating the main multicast distribution tree, that is, it does not need to consider the processing of the join attribute capabilities of each router in the routing domain, and uses the shortest path spanning tree algorithm of the link state protocol to find the multicast upstream neighbors to the multicast source / aggregation point in the entire routing domain.

[0095] When calculating the backup multicast distribution tree that does not intersect with the primary multicast distribution tree, a constrained shortest path spanning tree algorithm is used. The constraints are to first delete the nodes and links that the primary multicast distribution tree passes through from the original network topology, then delete the nodes that do not have the ability to process the join attributes of the multicast join message, the nodes that have announced the detailed join attribute subtype but do not carry the detailed reverse path vector subtype, and all connections of these nodes, and run the shortest path spanning tree algorithm on the remaining network topology information to find the backup multicast distribution tree branch path to the multicast source / aggregation point.

[0096] In one embodiment, each link has the same cost, wherein router R4 does not support the multicast join message join attribute. Routers R0, R1, R2, R3, R5, R6, and R7 all support the multicast join message join attribute such as Figure 6 As shown. Taking the construction of a backup multicast distribution tree with active-active elastic protection as an example, in the original network topology, the last hop router R1 calculates the shortest path to the source router R0 as the main multicast distribution tree, and the calculation result shows that the path from the receiver to the source is R1-R2-R0. When calculating the backup multicast distribution tree, the router R2 and R4 that does not have the ability to join the attribute and its related links that the main multicast distribution tree passes through are deleted, and the pruned network topology structure is obtained as shown in Figure 7 The last hop router R1 calculates the multicast distribution tree on the pruned network topology. The calculation result is R1-R5-R6-R7-R0. R1 fills in the join attribute of the multicast join message sent to R5 in sequence.<R5,R6,R7,R0> information.

[0097] When the join attribute capability of the router in the network changes, for example, the router that originally supported the exhaustive reverse path vector subtype no longer supports this subtype or the router that originally did not support it starts to support it, it will trigger the recalculation of the backup multicast distribution tree. The controller can also learn the capability of each router in the routing domain to process the detailed reverse path vector join attribute subtype of the multicast join message from the border gateway protocol-link state. The process of the controller as a centralized computing unit in the routing domain to calculate the backup multicast distribution tree path for the last hop router is the same as the process of the last hop router autonomously calculating it. This embodiment will not be repeated.

[0098] In an exemplary embodiment, a schematic diagram of a structure of a router for notifying a multicast join message join attribute capability and building a multicast distribution tree is provided.

[0099] like Figure 8 As shown, the command line interface (CLI) can provide a switch for the multicast module (PIM) to process the join attribute capability of the multicast join message. Optionally, a switch for the join attribute subtype is provided.

[0100] The link state protocol module (IGP) obtains the multicast join message join attribute processing capability information from the multicast module and carries it in the router capability information of the link state protocol.

[0101] When Border Gateway Protocol-Link State (BGP-LS) generates node-type network layer reachability information for link state information, it adds a community attribute that describes the router's ability to handle extended attributes of multicast join messages.

[0102] The router announces and receives link state protocol messages and border gateway protocol-link state network layer reachability information with the ability to join multicast join messages through the control plane, generates network topology information with node capabilities, and the calculation module calculates upstream neighbors on the available network topology in response to multicast requirements.

[0103] In one embodiment, the present application provides a distribution tree establishment device, such as Fig. 9 As shown, the distribution tree establishment device provided in the embodiment of the present application includes a sending module 71.

[0104] Among them, the sending module 71 is configured to determine the processing capability of the multicast join message joining attributes of this node; and to notify the processing capability information of the multicast join message joining attributes to the network, wherein the processing capability information of the multicast join message joining attributes is used to indicate the processing capability of this node for the joining attributes carried by the multicast join message.

[0105] In one embodiment, the processing capability information of the multicast join message's join attribute carries a processing capability identifier of the multicast join message's join attribute, indicating that the node has the capability to process the join attribute carried by the multicast join message.

[0106] In one embodiment, the processing capability information of the multicast join message join attribute further includes subtypes of the multicast join message join attribute supported by the node.

[0107] In one embodiment, the processing capability information of the multicast join message joining attribute is carried in the router capability information of the link state protocol IGP, or the processing capability information of the multicast join message joining attribute is carried in the group attribute information of the border gateway protocol-link state BGP-LS routing.

[0108] In one embodiment, the method further includes: when the processing capability of the multicast join attribute of the local node changes, updating the processing capability information of the join attribute of the multicast join message in the IGP and BGP-LS.

[0109] In one embodiment, the updating of the processing capability information of the join attribute of the multicast join message includes one or more of the following: updating the processing capability identifier of the join attribute of the multicast join message, and updating the subtype of the join attribute supported by the node.

[0110] The information sending device provided in this embodiment can execute the information sending method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of executing the method. For technical details not described in detail in this embodiment, please refer to the information sending method provided in any embodiment of the present invention.

[0111] It is worth noting that in the embodiment of the above-mentioned information sending device, the various units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application.

[0112] In one embodiment, the present application provides a distribution tree establishment device, such as Fig.10 As shown, the distribution tree establishing device provided in the embodiment of the present application includes a receiving module 81 and an establishing module 82.

[0113] The receiving module 81 is configured to receive the processing capability information of the joining attribute of the multicast joining message of each node;

[0114] The establishing module 82 is configured to establish a multicast distribution tree based on the processing capability information of the multicast join message join attribute of each node.

[0115] In one embodiment, receiving the processing capability information of the multicast join message join attribute of each node includes: receiving the processing capability information of the multicast join message join attribute advertised by each node in IGP or BGP-LS.

[0116] In one embodiment, the multicast distribution tree is established based on the processing capability information of the multicast join message joining attribute of each node, including: retaining the nodes that meet the preset conditions in the original network topology structure to form a new network topology structure, wherein the preset conditions are determined by the processing capability information of the multicast join message joining attribute; and establishing the multicast distribution tree on the new network topology structure.

[0117] In one embodiment, the nodes that meet the preset conditions include one or more of the following situations: a node that only has a multicast join message join attribute processing capability identifier and does not carry any subtype; a node that has a multicast join message join attribute processing capability identifier and the subtypes it carries include the required specific subtype.

[0118] The distribution tree establishment device provided in this embodiment can execute the distribution tree establishment method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of executing the method. For technical details not described in detail in this embodiment, please refer to the distribution tree establishment method provided in any embodiment of the present invention.

[0119] It is worth noting that in the embodiment of the above-mentioned distribution tree establishment device, the various units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application.

[0120] The present application also provides a device, Fig.11 is a schematic diagram of the structure of a device provided in an embodiment of the present application, such as Fig.11 As shown, the device includes a processor 91, a memory 92, an input device 93, and an output device 94; the number of processors 91 in the device can be one or more. Fig.11 A processor 91 is taken as an example; the processor 91, memory 92, input device 93 and output device 94 in the device can be connected by a bus or other means. Fig.11 The example of connecting through bus is taken in the following.

[0121] The memory 92, as a computer-readable storage medium, can be used to store software programs, computer executable programs and modules, such as the program instructions / modules corresponding to the information sending method in the embodiment of the present application (for example, the sending module 71 in the information sending device), such as the program instructions / modules corresponding to the distribution tree establishment method in the embodiment of the present application (for example, the receiving module 81 and the establishment module 82 in the multicast distribution tree establishment device). The processor 91 executes various functional applications and data processing of the device by running the software programs, instructions and modules stored in the memory 92, that is, implements any method provided in the embodiment of the present application.

[0122] The memory 92 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application required for a function; the data storage area may store data created according to the use of the device, etc. In addition, the memory 92 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 92 may further include a memory remotely arranged relative to the processor 91, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0123] The input device 93 can be used to receive input digital or character information, and generate key signal input related to user settings and function control of the device.

[0124] The embodiment of the present application further provides a storage medium containing computer executable instructions, wherein the computer executable instructions are used to execute an information sending method when executed by a computer processor, including:

[0125] Determine the processing capability of the node to process the join attributes of multicast join messages;

[0126] The processing capability information of the join attribute of the multicast join message is notified to the network, wherein the processing capability information of the join attribute of the multicast join message is used to indicate the processing capability of the node for the join attribute carried by the multicast join message.

[0127] Of course, the storage medium containing computer executable instructions provided in the embodiment of the present application, whose computer executable instructions are not limited to the operations of the information sending method described above, can also execute related operations in the information sending method provided in any embodiment of the present application.

[0128] The embodiment of the present application further provides a storage medium including computer executable instructions, wherein the computer executable instructions are used to execute a method for establishing a multicast distribution tree when executed by a computer processor, including:

[0129] Receive the processing capability information of the join attribute of the multicast join message of each node;

[0130] A multicast distribution tree is established based on the processing capability information of the multicast join message join attribute of each node.

[0131] Of course, the storage medium containing computer executable instructions provided in the embodiment of the present application is not limited to the multicast distribution tree establishment method operation described above, and can also execute the related operations of the distribution tree establishment provided in any embodiment of the present application.

[0132] Through the above description of the implementation method, the technicians in the relevant field can clearly understand that the present application can be implemented with the help of software and necessary general hardware, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application can be essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory (FLASH), hard disk or optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0133] The above description is merely an exemplary embodiment of the present application and is not intended to limit the protection scope of the present application.

[0134] It will be appreciated by those skilled in the art that the term user terminal covers any suitable type of wireless user node, such as a mobile phone, a portable data processing device, a portable web browser or a vehicle-mounted mobile station.

[0135] In general, various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software that can be executed by a controller, microprocessor or other computing device, although the present application is not limited thereto.

[0136] Embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.

[0137] The block diagram of any logic flow in the accompanying drawings of the present application can represent program steps, or can represent interconnected logic circuits, modules and functions, or can represent a combination of program steps and logic circuits, modules and functions. The computer program can be stored on a memory. The memory can have any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read-only memory (ROM), random access memory (RAM), optical memory device and system (digital versatile disc DVD or CD disc), etc. Computer-readable media may include non-transient storage media. The data processor can be any type suitable for the local technical environment, such as but not limited to a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (FGPA) and a processor based on a multi-core processor architecture.

[0138] By way of exemplary and non-limiting examples, a detailed description of exemplary embodiments of the present application has been provided above. However, various modifications and adjustments to the above embodiments will be apparent to those skilled in the art when considered in conjunction with the accompanying drawings and claims, but will not depart from the scope of the present invention. Therefore, the proper scope of the present invention will be determined according to the claims.

Claims

1. A method for sending information, characterized in that: include: Determine the processing capability of the node to process the join attributes of multicast join messages; Notifying the processing capability information of the join attribute of the multicast join message in the network, wherein the processing capability information of the join attribute of the multicast join message is used to indicate the processing capability of the node for the join attribute carried by the multicast join message; The processing capability information of the multicast join message joining attribute is carried in the router capability information of the link state protocol IGP, or the processing capability information of the multicast join message joining attribute is carried in the group attribute information of the border gateway protocol-link state BGP-LS routing.

2. The method according to claim 1, characterized in that The processing capability information of the multicast join message's join attribute carries the processing capability identifier of the multicast join message's join attribute, indicating that the node has the processing capability of the join attribute carried by the multicast join message.

3. The method according to claim 2, characterized in that The processing capability information of the multicast join message join attribute also includes the subtypes of the multicast join message join attribute supported by the node.

4. The method according to claim 1, characterized in that: The method further comprises: When the processing capability of the multicast join attribute of the local node changes, the processing capability information of the join attribute of the multicast join message is updated in the IGP and BGP-LS.

5. The method according to claim 4, characterized in that The processing capability information of updating the multicast join message join attribute includes one or more of the following: The processing capability identifier of the join attribute of the multicast join message is updated, and the subtype of the join attribute supported by the node is updated.

6. A distribution tree establishment method, characterized in that: include: Receive the processing capability information of the join attribute of the multicast join message of each node; Establishing a multicast distribution tree based on the processing capability information of the multicast join message join attribute of each node; The processing capability information of the multicast join message join attribute received from each node includes: Receive the processing capability information of the join attribute of the multicast join message advertised by each node in IGP or BGP-LS.

7. The method according to claim 6, characterized in that The establishing of a multicast distribution tree based on the processing capability information of the multicast join message join attribute of each node includes: Retaining nodes in the original network topology that meet preset conditions to form a new network topology, wherein the preset conditions are determined by the processing capability information of the joining attribute of the multicast joining message; A multicast distribution tree is established on the new network topology.

8. The method according to claim 7, characterized in that The nodes that meet the preset conditions include one or more of the following situations: A node that only has the multicast join message join attribute processing capability flag and does not carry any subtypes; A node having a multicast join message join attribute processing capability identifier and the carried subtype includes a required specific subtype.

9. An information sending device, characterized in that: include: A sending module, configured to determine a processing capability of a node for a multicast join message join attribute; Notifying the processing capability information of the join attribute of the multicast join message in the network, wherein the processing capability information of the join attribute of the multicast join message is used to indicate the processing capability of the node for the join attribute carried by the multicast join message; The processing capability information of the multicast join message joining attribute is carried in the router capability information of the link state protocol IGP, or the processing capability information of the multicast join message joining attribute is carried in the group attribute information of the border gateway protocol-link state BGP-LS routing.

10. A distribution tree establishment device, characterized in that: include: A receiving module, configured to receive processing capability information of a join attribute of a multicast join message of each node; An establishing module configured to establish a multicast distribution tree based on the processing capability information of the multicast join message join attribute of each node; The processing capability information of the multicast join message join attribute received from each node includes: Receive the processing capability information of the join attribute of the multicast join message advertised by each node in IGP or BGP-LS.

11. A device, characterized in that: include: one or more processors; A memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 8.

12. A storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.

Images