WO2021213517A1

WO2021213517A1 - Routing domain identifier configuration method and device

Info

Publication number: WO2021213517A1
Application number: PCT/CN2021/089451
Authority: WO
Inventors: 魏含宇; 刘毅松; 于斌; 沈利; 胡寅亮
Original assignee: 华为技术有限公司
Priority date: 2020-04-24
Filing date: 2021-04-23
Publication date: 2021-10-28
Also published as: CN113556796A

Abstract

The present application provides a routing domain identifier configuration method and a device. The method comprises: a first node obtains a routing domain identifier of a first port of the first node, and sends, by means of the first port, to a second node a first message carrying a first routing domain identifier, the first routing domain identifier being the routing domain identifier of the first port, and the first message being used for instructing the second node to configure the routing domain identifier of a second port of the second node as the first routing domain identifier. Upon the reception of the first message by means of the second port, the second node configures the routing domain identifier of the second port as the first routing domain identifier. According to the technical solution provided by the present application, nodes can learn routing domain identifiers from each other, and when nodes in a network agree upon negotiation, the purpose of automatically dividing routing domains is achieved, thereby improving efficiency of nodes in routing domain identifier configuration.

Description

Method and equipment for configuring routing domain identification

This application claims the priority of the Chinese patent application filed with the Chinese Patent Office on April 24, 2020, the application number is 202010335099.6, and the application name is "Method and Equipment for Configuring Routing Domain Identification", the entire content of which is incorporated into this application by reference middle.

Technical field

This application relates to the field of network technology, and in particular to a method and device for configuring a routing domain identifier.

Background technique

Generally, network devices can automatically perform topology discovery, networking, routing calculation, and synchronization through a network routing protocol, so as to achieve the effect that nodes in the network can be connected based on Internet protocol (IP). For example, a node in the network obtains the topology of the network through a certain mechanism (such as neighbor discovery and synchronization of neighbor information, etc.); then the node calculates the relevant routes to other nodes according to the topology of the network. When one or some nodes or links fail, the failure can be synchronized to all nodes through a certain mechanism; then each node recalculates the topology according to the latest topology. Based on the above-mentioned automatic routing networking, when the network (such as the number of nodes or the number of interconnected links) increases to a certain scale, the time delay of topology discovery, route synchronization, and the processing load of interactive messages will become bottlenecks. For example, it is difficult for routers or switches to support large-scale single-area routing network networking calculations and message synchronization loads.

In view of this, it is usually necessary to divide the network into different areas, and perform topology discovery and synchronization in each area. The above-mentioned divided areas can also be called routing domains. The general method of dividing routing domains is for example, manually or outside the network management and control equipment (such as network controller, network management or server, etc.) to issue related configuration node by node. As shown in Figure 1, the management and control device can configure the running routing protocol for each node in the network. Further, the management and control device can set the routing domain to which each node belongs for each node in the network, as shown in Figure 1. Area 0 (area 0), area 1 (area1) and area 2 (area2).

However, the efficiency of setting the routing domain identifier manually or through a management and control device is inefficient.

Summary of the invention

The present application provides a method and device for configuring a routing domain identifier, which effectively improves the efficiency of configuring the routing domain identifier and improves the efficiency of dividing the routing domain.

In a first aspect, the present application provides a method for configuring a routing domain identifier, the method comprising: a first node obtains the routing domain identifier of a first port of the first node, and sends a first message to the second node through the first port ; The first message carries a first routing domain identifier, the first routing domain identifier is the routing domain identifier of the first port, and the first message is used to instruct the second node to configure the routing domain identifier of the second port of the second node Is the first routing domain identifier, and the second port is the port through which the second node receives the first message.

In the embodiment of the present application, the first routing domain identifier may be generated by the first node; or, it may also be obtained by the first node from other nodes.

In the technical solution provided by this application, the second node can learn the first routing domain identifier obtained by the first node through the exchange of messages between the first node and the second node, so as to configure the routing domain identifier of the second port as the first node. A routing domain identifier. Compared with the method in which each node divides the routing domain through the management and control device, and sends the routing domain identifier after dividing the routing domain to configure the routing domain identifier, the method avoids the node waiting for the manual or the management and control device to issue the routing domain identifier. Nodes can learn routing domain identifiers from each other. When the nodes in the network agree upon negotiation, the purpose of automatically dividing routing domains is realized, and the efficiency of node configuration of routing domain identifiers is improved.

In a possible implementation manner, the method further includes: configuring the routing domain identifier of the first port by the first node as the first routing domain identifier.

In the embodiment of the present application, the sequence in which the first node sends the first message and the routing domain identifier configuring the first port is the first routing domain identifier is not limited in the embodiment of the present application. And the order in which the first node obtains the routing domain identifier of the first port of the first node and the routing domain identifier configuring the first port as the first routing domain identifier is not limited.

In a possible implementation manner, after the first node configures the routing domain identifier of the first port as the first routing domain identifier, the method further includes: the first node exchanges routing information with the second node according to the first routing domain identifier .

In the embodiment of the present application, the routing domain identifier may be used to determine the routing mode; or, to determine the range of the routing domain (or the boundary of the routing domain, etc.) for nodes to exchange routing information. Exemplarily, the first routing domain identifier may be used to indicate a routing domain range in which the first node and the second node exchange routing information. The first node exchanges routing information with the second node according to the first routing domain identifier, which can also be understood as the first node to exchange routing information with the second node through the first routing domain identifier.

In a possible implementation manner, before the first node obtains the routing domain identifier of the first port of the first node, the method further includes: the first node determines that the role information of the first node relative to the second node is a domain Generate roles.

Optionally, after obtaining the node type of the first node and the node type of the second node, the first node may obtain the routing domain identifier of the first port according to the node type of the first node and the node type of the second node. Optionally, the first node may also obtain the routing domain identifier of the first port when determining that its role information relative to the second node is a domain generation role.

It can be understood that when the first routing domain identifier is generated by the first node, the first node may also determine that its role information relative to the second node is the domain generation role before acquiring the routing domain identifier of the first port. When the first routing domain identifier is obtained by the first node from other nodes, the first node may determine that its role information relative to the second node is the domain generation role before sending the first message.

In a possible implementation manner, the first node is an edge node, and the first node configures the routing domain identifiers of all ports of the first node as the first routing domain identifiers.

In the embodiment of the present application, when the first node has a domain generation role relative to the second node, and the first node is an edge node, the first node may configure the routing domain identifiers of all its ports as the first routing domain identifier.

In a possible implementation manner, the first node is an edge node, and the first routing domain identifier is different from the routing domain identifier obtained by other edge nodes in the network.

In the embodiment of the present application, the network includes multiple edge nodes, and the multiple edge nodes all have a domain generating role, then the routing domain identifiers of the multiple edge nodes are different. However, the network includes multiple (such as three or more) edge nodes, but two (or more) of the multiple edge nodes are not in the domain generation role (such as the connection between the edge node and the root node). Case), the routing domain identities of the two edge nodes may be the same, but the routing domain identities of the two edge nodes may be different from the routing domain identities of other edge nodes.

In a possible implementation, the first node determines that the role information of the first node relative to the second node is the domain generation role, including: the first node obtains the node type of the first node in the network, and the second node is in the The node type in the network; the first node determines that the role information of the first node relative to the second node is the domain generation role according to the node type of the first node and the node type of the second node.

In the embodiment of the present application, the node type may include one or more of a root node, an edge node, a secondary external node, or a common node. Among them, the root node can be a core node or a central location of the network. The edge node is not on the shortest path from other nodes to the root node, and the other nodes are nodes other than the edge node and the root node in the network. The secondary external node is on the shortest path from the edge node to the root node, and the secondary external node is connected to the edge node; ordinary nodes are nodes other than the root node, edge nodes, and secondary external nodes in the network.

It is understandable that there may be one node type of a node; or, there may be more node types of a node. Exemplarily, the node type of a certain node in the network may be a secondary external node or a normal node.

In a possible implementation, the first node obtains the node type of the first node in the network and the node type of the second node in the network, including: the first node obtains the node type of the first node; and receiving from A second message of the second node, where the second message carries the node type of the second node.

In the embodiment of the present application, the first node may obtain its node type according to the network topology.

In a possible implementation manner, the first node acquiring the node type of the first node in the network and the node type of the second node in the network includes: the first node receives the fifth message from the root node, and the first node Five messages carry the node type of the first node; and a second message received from the second node, the second message carrying the node type of the second node.

In a possible implementation manner, the node type of the first node is a root node; or, the node type of the first node is an edge node. In this case, the first routing domain identifier may be generated by the first node.

In a possible implementation manner, the node type of the first node is a normal node, and the node type of the second node is a secondary node or a normal node. In this case, the first routing domain identifier may be generated by another node (such as a root node or an edge node), that is, the first routing domain identifier may be obtained by the first node from other nodes.

In a possible implementation manner, the node types include first-level nodes and second-level nodes. Or, the node type also includes a third-level node. It can be understood that the first-level node, the second-level node, and the third-level node may also include other names, etc., which are not limited in the embodiment of the present application.

In a possible implementation manner, the first node sending the first message to the second node through the first port includes: when the network topology changes, the first node sends the first message to the second node through the first port The first message; where the first node and/or the second node are nodes whose node types have changed; or, the first node and/or the second node are newly-added nodes.

In the embodiment of the present application, when the topology of the network changes, the routing domain identifier of one or more ports of the node whose node type has changed is reconfigured. Exemplarily, if the node type of the first node relative to the second node changes, the routing domain identifier of the first port and/or the second port may be reconfigured. However, if the node type of the first node relative to the fourth node does not change, the routing domain identifier of the port where the first node communicates with the fourth node may not be reconfigured.

The technical solution provided in this application avoids the re-division of routing domains in the entire network, and by adjusting the routing domain identifiers of a small number of nodes, it is possible to re-deploy the routing domain of the network, improve the efficiency of redeployment, and improve the dynamic adaptability of the network .

In a second aspect, the present application provides a method for configuring a routing domain identifier. The method includes: a second node receives a first message from a first node through a second port, the first message carries the first routing domain identifier, and the The first message is used to instruct the second node to configure the routing domain identification of the second port of the second node as the first routing domain identification, the routing domain identification of the first port of the first node is the first routing domain identification, and the first port is The port through which the first node sends the first message; the second node configures the routing domain identifier of the second port as the first routing domain identifier.

In a possible implementation manner, after the second node configures the routing domain identifier of the second port as the first routing domain identifier, the method further includes: the second node exchanges routing information with the first node according to the first routing domain identifier .

In a possible implementation manner, before the second node configures the routing domain identifier of the second port as the first routing domain identifier, the method further includes: the second node determines that the role information of the second node relative to the first node is Domain learning role.

In a possible implementation, the second node determines that the role information of the second node relative to the first node is a domain learning role, including: the second node obtains the node type of the second node in the network, and the first node is in the The node type in the network; and then the second node determines the role information of the second node relative to the first node as the domain learning role according to the node type of the second node and the node type of the first node.

In a possible implementation, the second node obtains the node type of the second node in the network and the node type of the first node in the network, including: the second node obtains the node type of the second node; and receiving data from The fourth message of the first node, the fourth message carries the node type of the first node.

In a possible implementation manner, the second node acquiring the node type of the second node in the network and the node type of the first node in the network includes: the second node receives the seventh message from the root node, and the seventh node The message carries the node type of the second node; and a fourth message is received from the first node, and the fourth message carries the node type of the first node.

In a possible implementation manner, the node type includes one or more of the root node, edge node, sub-external node, or ordinary node; wherein, the edge node is not on the shortest path from other nodes to the root node, and other nodes are Nodes in the network other than the edge node and the root node; the secondary external node is on the shortest path from the edge node to the root node, and the secondary external node is connected to the edge node; the ordinary node is one of the root node, edge node, and secondary external node in the network Outside the node.

In a possible implementation manner, the node types include first-level nodes and second-level nodes. Or, the node type also includes a third-level node.

In a possible implementation manner, the node type of the first node is a root node; or, the node type of the first node is an edge node; or, the node type of the first node is a normal node, and the node type of the second node is Sub-external node or ordinary node.

In a possible implementation manner, the method further includes: the second node sends an eighth message to the third node through the third port, the eighth message carries the first routing domain identifier, and the eighth message is used to indicate to the third node Configure the routing domain ID of the fourth port of the third node as the first routing domain ID, and the routing domain ID of the third port as the first routing domain ID; the second node configures the routing domain ID of the third port as the first routing domain ID .

Exemplarily, as shown in Figure 5a, the first node may include node 1 (root node), the second node may include node 3 (secondary extra/normal node) or node 4 (secondary extra/normal node), and the third node Can include node 7 (secondary extra node). As shown in FIG. 5c, the first node may include node 20 (root node), the second node may include node 22 (ordinary node), and the third node may include node 24 (secondary node).

In a possible implementation manner, the second node receives the first message from the first node through the second port, including:

When the topology of the network changes, the second node receives the first message from the first node through the second port; wherein the first node and/or the second node are nodes whose node types have changed; or, the first node The first node and/or the second node are newly added nodes.

In the third aspect, this application provides a network device for executing the first aspect or any possible implementation of the first aspect. The network device includes a corresponding unit that executes the method in the first aspect or any possible implementation of the first aspect.

For example, the network device may include a transceiver unit and a processing unit. The network device may be the first node in the foregoing first aspect.

In a fourth aspect, this application provides a network device for executing the second aspect or the method in any possible implementation manner of the second aspect. The network device includes a corresponding unit that executes the second aspect or the method in any possible implementation of the second aspect.

For example, the network device may include a transceiver unit and a processing unit. The network device may be the second node in the above second aspect.

In a fifth aspect, the present application provides a network device that includes a processor, configured to execute a program stored in a memory, and when the program is executed, the network device is caused to execute the above-mentioned first aspect or the first aspect. Any possible implementation of the method shown.

In a possible implementation manner, the memory is located outside the aforementioned network device.

In a possible implementation manner, the memory is located in the aforementioned network device.

In a possible implementation manner, the network device further includes a transceiver, and the transceiver is used to receive a signal or send a signal. Exemplarily, the transceiver may be used to send the first message. For another example, the transceiver can also be used to receive the second message or the fifth message.

In the embodiment of the present application, the network device may be the first node in the foregoing first aspect.

In a sixth aspect, the present application provides a network device that includes a processor, configured to execute a program stored in a memory, and when the program is executed, the network device is caused to execute the second aspect or the second aspect described above. Any possible implementation of the method shown.

In a possible implementation manner, the network device further includes a transceiver, and the transceiver is used to receive a signal or send a signal. Exemplarily, the transceiver may be used to receive the first message. For another example, the transceiver can also be used to receive the fourth message or the seventh message.

In the embodiment of the present application, the network device may be the second node in the second aspect described above.

In a seventh aspect, the present application provides a network device, the network device includes a processing circuit and an interface circuit, the processing circuit is used to obtain the routing domain identifier of the first port; the interface circuit is used to output the first port through the first port A message; the processing circuit is also used to configure the routing domain identifier of the first port.

Exemplarily, the processing circuit is further configured to determine that the role information of the network device relative to the second node is a domain generation role.

Exemplarily, the interface circuit is also used to obtain the node type of the network device in the network and the node type of the second node in the network; and the processing circuit is also used to obtain the node type of the network device and the value of the second node. The node type determines that the role information of the network device relative to the second node is the domain generation role. Alternatively, the processing circuit is also used to obtain the node type of the network device in the network, the interface circuit is also used to obtain the node type of the second node in the network; and the processing circuit is also used to obtain the node type of the network device and The node type of the second node determines that the role information of the network device relative to the second node is the domain generation role.

Exemplarily, the interface circuit may also be used to obtain the second message or the fifth message.

The network device may be the first node in the foregoing first aspect. It can be understood that, for the description of the first message, the second message, or the fifth message, reference may be made to the first aspect, which will not be described in detail here.

In an eighth aspect, the present application provides a network device, the network device includes a processing circuit and an interface circuit, the interface circuit is used to obtain a first message; the processing circuit is used to configure the routing domain identifier of the second port.

Exemplarily, the processing circuit is also used to determine that the role information of the network device relative to the first node is a domain learning role.

Exemplarily, the interface circuit is also used to obtain the node type of the network device in the network and the node type of the first node in the network; the processing circuit is also used to obtain the node type of the network device and the node of the first node The type determines that the role information of the network device relative to the first node is the domain learning role. Alternatively, the processing circuit is also used to obtain the node type of the network device in the network; the interface circuit is also used to obtain the node type of the first node in the network; the processing circuit is also used to obtain the node type and the node type of the network device The node type of the first node determines that the role information of the network device relative to the first node is a domain learning role.

Exemplarily, the interface circuit may also be used to obtain the fourth message or the seventh message, etc.

Exemplarily, the interface circuit may also output an eighth message and so on.

The network device may be the second node in the above second aspect. It can be understood that, for the description of the first message, the fourth message, the seventh message, or the eighth message, reference may be made to the second aspect, which will not be described in detail here.

In a ninth aspect, the present application provides a role determination device, which is used to obtain the node type of the local node according to the network topology. The role determination device includes a processing circuit and an interface circuit, the interface circuit can be used to obtain the network topology, and the processing circuit can be used to determine the node type of the local node according to the network topology.

Exemplarily, the local node may include a first node or a second node.

Or, the role determining device is used to obtain the node type of each node in the network according to the network topology. The role determination device includes a processing circuit and an interface circuit, the interface circuit can be used to obtain the network topology, and the processing circuit can be used to determine the node type of each node according to the network topology.

In a tenth aspect, this application provides a computer-readable storage medium, which is used to store a computer program. When it runs on a computer, the first aspect or any possible implementation of the first aspect The method shown is executed.

In an eleventh aspect, the present application provides a computer-readable storage medium for storing a computer program. When it runs on a computer, it enables any possible implementation of the above-mentioned second aspect or the second aspect The method shown in the method is executed.

In a twelfth aspect, this application provides a computer program product, the computer program product includes a computer program or computer code, when it runs on a computer, the first aspect or any possible implementation of the first aspect is shown in The method is executed.

In a thirteenth aspect, this application provides a computer program product, which includes a computer program or computer code, which when it runs on a computer, makes the above-mentioned second aspect or any possible implementation of the second aspect as shown in The method is executed.

In a fourteenth aspect, the present application provides a computer program. When the computer program runs on a computer, the method shown in the first aspect or any possible implementation of the first aspect is executed.

In a fifteenth aspect, the present application provides a computer program. When the computer program runs on a computer, the method shown in the second aspect or any possible implementation of the second aspect is executed.

In a sixteenth aspect, the present application provides a routing autonomous system. The routing autonomous system includes a first node and a second node. The first node is used to execute the foregoing first aspect or any possible implementation manner of the first aspect. The second node is used to execute the method shown in the foregoing second aspect or any possible implementation manner of the second aspect.

In a possible implementation manner, the routing autonomous system further includes a third node, the third node is configured to receive the eighth message sent by the second node, and configure the routing domain identifier of the fourth port of the third node as The first routing domain identifier.

Description of the drawings

FIG. 1 is a schematic diagram of a scenario for dividing routing domains according to an embodiment of the present application;

FIG. 2 is a schematic flowchart of a method for configuring a routing domain identifier provided by an embodiment of the present application;

Figure 3a is a schematic structural diagram of a network provided by an embodiment of the present application;

Figure 3b is a schematic structural diagram of a network provided by an embodiment of the present application;

Figure 3c is a schematic structural diagram of a network provided by an embodiment of the present application;

Fig. 4a is a schematic flowchart of a method for configuring a routing domain identifier provided by an embodiment of the present application;

FIG. 4b is a schematic flowchart of a method for configuring a routing domain identifier according to an embodiment of the present application;

FIG. 4c is a schematic flowchart of a method for configuring a routing domain identifier according to an embodiment of the present application;

FIG. 5a is a schematic diagram of a scenario for dividing routing domains corresponding to FIG. 3a provided by an embodiment of the present application;

FIG. 5b is a schematic diagram of a scenario for dividing routing domains corresponding to FIG. 3b according to an embodiment of the present application;

FIG. 5c is a schematic diagram of a scenario for dividing routing domains corresponding to FIG. 3c according to an embodiment of the present application;

FIG. 5d is a schematic diagram of a scenario for dividing routing domains according to an embodiment of the present application;

FIG. 6 is a schematic flowchart of a method for configuring a routing domain identifier provided by an embodiment of the present application;

Figure 7a is a schematic diagram of a scenario for dividing routing domains provided by an embodiment of the present application;

Figure 7b is a schematic diagram of a scenario for dividing routing domains provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a network device provided by an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a network device provided by an embodiment of the present application;

FIG. 10 is a schematic structural diagram of a network device provided by an embodiment of the present application;

Fig. 11 is a schematic diagram of a routing autonomous system provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions, and advantages of the present application clearer, the present application will be further described with reference to the accompanying drawings.

The terms "first" and "second" in the specification, claims, and drawings of this application are only used to distinguish different objects, rather than to describe a specific sequence. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optional The ground also includes other steps or units inherent to these processes, methods, products, or equipment.

The “embodiment” mentioned herein means that a specific feature, structure or characteristic described in conjunction with the embodiment may be included in at least one embodiment of the present application. The appearance of the phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art can explicitly and implicitly understand that the embodiments described herein can be combined with other embodiments.

In this application, "at least one (item)" refers to one or more, "multiple" refers to two or more than two, and "at least two (item)" refers to two or three and three Above, "and/or" is used to describe the association relationship of associated objects, which means that there can be three kinds of relationships. For example, "A and/or B" can mean: there is only A, only B, and both A and B. In this case, A and B can be singular or plural. The character "/" generally indicates that the associated objects before and after are in an "or" relationship. "The following at least one item (a)" or similar expressions refers to any combination of these items. For example, at least one of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c" ".

The following describes the terms involved in this application in detail.

Autonomous routing system (AS): In the network, a routing autonomous system is a small unit that has the power to independently decide which routing protocol to use in the routing autonomous system. In other words, all routers in a routing autonomous system can run the same routing protocol, etc., and the routing protocols run by different routing autonomous systems can be the same or different. A routing autonomous system includes one or more routing domains. It can be understood that the network shown in the embodiments of the present application can be understood as a routing autonomous system.

Routing domain identification (area identification, area ID): used to identify routing domains; alternatively, different routing domains can be distinguished through the routing domain identification. Exemplarily, different nodes in a routing domain can exchange routing information according to the routing domain identifier of the routing domain. Exemplarily, when routing information is exchanged between nodes of two routing domains, routing information may be exchanged according to the boundary nodes of the two routing domains.

It can be understood that the routing domain identifiers shown in this application may also be referred to as routing domain numbers, routing domain identifiers, domain numbers, or domain identifiers.

Routing information: can be stored in routing table (routing table) or routing information base (routing information base, FIB), etc. The routing information can be used to instruct the network device to perform routing query or path selection on the message. For example, the routing information can be used to indicate how to select a path from the source to the destination when the message is forwarded in the network.

Domain learning role: used to learn the routing domain ID sent by other nodes, so as to configure the learned routing domain ID for the port (port between other nodes).

Domain generation role: used to generate routing domain identification. In some implementation manners, the domain generation role can send the generated routing domain identification to other nodes; in other implementation manners, the domain generation role can diffuse the learned routing domain identification to other nodes.

It is understandable that in some implementations, a certain node in the network can be a domain generation role; in other implementations, the certain node can also be a domain learning role; in still other implementations, the certain node It can also be both a domain generation role and a domain learning role.

The first message: a node receives the first message sent by another node, then the one node can learn the routing domain identifier carried in the first message to configure the routing domain of the port (that is, the port that receives the first message) The identifier is the routing domain identifier carried in the first message. In other words, the function of the first message may be to instruct the node receiving the first message to learn the routing domain identifier carried in the first message.

Generally, nodes in the network need to configure routing domain identifiers according to the routing domain identifiers uniformly issued by the management and control device, so as to achieve the purpose of dividing routing domains. Furthermore, when the network increases to a certain size, the management and control equipment not only needs to consider the topology of each node, but also needs to consider the interface type, traffic distribution and direction, etc., resulting in low efficiency of the management and control equipment in issuing routing domain identifications. , The node configuration routing domain identification is inefficient. Especially when the topology of the network changes or the network is expanded or reduced, the management and control equipment needs to re-plan the routing domain identification.

In view of this, the present application provides a method for configuring routing domain identification, which avoids the management and control equipment from sending routing domain identifications one by one, configuring domain attribution information, improving the communication efficiency of the control plane or the management plane, and reducing the control plane or the management plane. load. Further, the nodes in the network can learn routing domain identifiers from each other, thereby realizing the purpose of automatically dividing routing domains and improving the efficiency of node configuration of routing domain identifiers.

The method provided in this application can be applied to enterprise networking scenarios, and also applicable to campus networks, campus networks, data centers, and other networking scenarios. In the above networking scenario, the network generally exists in layers. Exemplarily, similar to the network shown in FIG. 1, as shown in FIG. 1, the core layer may be regarded as the uppermost node, the access layer may be regarded as the lowermost node, and the lowermost node may be closer to the terminal device. At the same time, in order to support large-scale terminal equipment access, the closer to the level of terminal equipment, the greater the number of fan-out links of the node. At the same time, considering the situation of network expansion, as well as the above-mentioned networking mode or physical deployment constraints, the general direction of network expansion is to increase the convergence layer or access layer vertically to expand the scale.

It can be understood that the enterprise networking, campus network, campus network, or data center shown above can be understood as the routing autonomous system introduced above. Exemplarily, the network shown in Figure 1 can be understood as a routing autonomous system. The areas 0, area1, and area2 divided in Figure 1 can be understood as three routing domains, and 0, 1, 2 can be understood as routing domain identifiers. .

In the above networking scenario, the network needs to be divided into routing domains, so that nodes in a routing domain can exchange routing information. Further, the method provided in this application can be applied to routing protocols, which include open shortest path first (OSPF) routing protocol, intermediate system-to-intermediate system (intermediate system-to-intermediate system, IS- IS) routing protocol, interior gateway routing protocol (interior gateway routing protocol, IGRP), etc.

The method for configuring the routing domain identifier provided in this application can be applied to the first node and the second node in the network. The first node and the second node may be network equipment, and the network equipment may include a switch, a router, or a wireless access device. Point (access point, AP), etc. The embodiment of the present application does not limit the specific types of the first node and the second node.

Refer to FIG. 2, which is a schematic flowchart of a method for configuring a routing domain identifier according to an embodiment of the present application. As shown in Figure 2, the method includes:

201. The first node obtains the routing domain identifier of the first port of the first node.

Exemplarily, the routing domain identification of the first port may be the first routing domain identification, that is, the first node may obtain the first routing domain identification. The first routing domain ID is used to distinguish other routing domain IDs in the network. As long as the routing domain IDs in the network do not overlap (or are different from each other), the embodiment of the present application does not limit the generation algorithm of the first routing domain ID. Exemplarily, for example, the first routing domain identifier may be the device number of the node, the physical address or IP address of the node, and so on. For another example, the first routing domain identifier can be generated according to the provisions of the routing protocol.

In some implementations, the first routing domain identifier may be generated by the first node. The first routing domain identifier may be the device number, physical address, or IP address of the first node; or, the first routing domain identifier may also be the device number, physical address of the peer node connected to the first node Or IP address, etc. Optionally, before the first node generates the first routing domain identifier, the first node may also determine that the role information of the first node relative to the second node is the domain generation role, thereby generating the first routing domain identifier. Alternatively, the first node may also obtain its node type and the node type of the second node, and generate the first routing domain identifier according to the node type of the first node and the node type of the second node.

In other implementation manners, the first routing domain identifier may be generated by another node, and sent to the first node through the other node. The other nodes are nodes other than the first node and the second node in the network. Optionally, before the first node sends the first message to the second node, the first node may also determine that the role information of the first node with respect to the second node is the domain generation role, so as to send the first message to the second node. information. Alternatively, the first node may also obtain its node type and the node type of the second node, and send the first message to the second node according to the node type of the first node and the node type of the second node.

In other words, acquiring the first routing domain identifier by the first node includes: the first node generates the first routing domain identifier; or, the first node receives the first routing domain identifier sent by other nodes. The method for generating the first routing domain identifier by the other node may refer to the method for generating the first routing domain identifier by the first node, which will not be described in detail here. For a detailed description of generating a routing domain identifier or receiving a routing domain identifier sent by other nodes, refer to FIG. 6, which will not be described in detail here.

For the method for the first node to determine that the role information of the first node relative to the second node is a domain generation role, and for the first node to obtain its node type and the node type of the second node, please refer to Figure 4a and Figure 4b, where I won't go into details.

202. The first node sends a first message to the second node through the first port, the first message carries the first routing domain identifier, and the first message is used to instruct the second node to configure the routing domain of the second port of the second node The identifier is the first routing domain identifier, and the second port is the port through which the second node receives the first message. Correspondingly, the second node receives the first message through the second port.

Generally speaking, a node may include one or more ports. For example, a node may be connected to multiple nodes, and then the one node may exchange messages with the multiple nodes through multiple ports.

The foregoing first port and second port are only a pair of ports when messages are exchanged between the illustrated nodes, and there may be other ports between the first node and other nodes, which are not limited in the embodiment of the present application. The other nodes are nodes other than the first node and the second node in the network.

It can be understood that in the case where there are multiple ports between the first node and the second node, the first node and the second node are also applicable to the method provided in the embodiment of the present application. Exemplarily, the multiple ports may be understood as one logical port; or, the first node may be connected to the second node through one of the paths, etc., which is not limited in the embodiment of the present application.

In the embodiment of the present application, the first message is used to instruct the second node to configure the routing domain identifier of the second port as the first routing domain identifier. That is, after the second node receives the first message, the second node can learn the routing domain identifier of the first port, so as to set the routing domain identifier of the second port as the first routing domain identifier.

In some implementation manners, after receiving the first message, the second node may directly learn the first routing domain identifier (as in step 204).

In other implementation manners, the second node may also determine whether to learn the first routing domain identifier according to some conditions. Exemplarily, when the second node determines that the role information of the second node relative to the first node is a domain learning role, the second node learns the first routing domain identifier. Exemplarily, the second node may also determine whether to learn the first routing domain identifier according to its node type and the node type of the first node (for example, whether to configure the routing domain identifier of the second port as the first routing domain identifier). For the method for the second node to determine its role information and the method for the second node to obtain its node type and the node type of the first node, please refer to FIG. 4a and FIG. 4c, which will not be described in detail here.

In some implementation manners, the first node may send the first message to the second node at a preset time interval; or, the first node may also send the first message to the second node at a preset frequency. The specific value of the preset time interval or preset frequency is not limited in this embodiment of the application. For example, the preset time interval or preset frequency may be set by the first node, other nodes, or manually. The other node may be a node other than the first node in the network.

In other implementation manners, the first node may also send the first message to the second node when the topology of the network changes. In this case, the first node and/or the second node may be newly added nodes; or, the first node and/or the second node may be nodes whose topological structure has changed (such as nodes whose node types have changed, etc.), etc. . In other words, in the case of network capacity expansion or reduction, the first node can send the first message to the second node through the first port. Alternatively, in the case of a network power failure or the like, the first node may also send the first message to the second node through the first port.

It can be understood that the embodiment of the present application does not limit when the first node sends the first message.

203. The first node configures the routing domain identifier of the first port as the first routing domain identifier.

It can be understood that the embodiment of the present application does not limit the sequence of step 202 and step 203.

It can be understood that the embodiment of the present application does not limit the sequence of step 201 and step 203.

204. The second node configures the routing domain identifier of the second port as the first routing domain identifier.

In a possible implementation manner, the method shown in FIG. 2 may further include:

205. The first node exchanges routing information with the second node according to the first routing domain identifier. Correspondingly, the second node exchanges routing information with the first node according to the first routing domain identifier.

In some implementation manners, the first node and the second node may be two adjacent nodes in the network. In this case, the first node may send the first message to the adjacent node (such as the second node). Optionally, the first node may send the first message to a node adjacent to the uplink; or, the first node may also send the first message to a node adjacent to the uplink.

In other implementations, the first node and the second node may not be adjacent. In this case, for example, the first node may send the first message to multiple nodes, as to whether the multiple nodes learn the first route The domain identifier can be determined according to the conditions shown in the embodiments of the present application. Exemplarily, the multiple nodes may determine whether to learn the first routing domain identifier according to respective node types, neighboring nodes, or node types of the first node.

In the embodiment of the present application, through the exchange of messages between the first node and the second node, the second node can learn the first routing domain identifier (that is, the routing domain identifier of the first port) obtained by the first node, thereby configuring The routing domain identifier of the second port is the first routing domain identifier. Compared with the method of configuring the routing domain identification by each node through the management and control device issuing the routing domain identification, it is avoided that the node waits for the manual or the management and control device to issue the routing domain identification. Nodes can learn routing domain identifiers from each other. When the nodes in the network agree upon negotiation, the purpose of automatically dividing routing domains is realized, and the efficiency of node configuration of routing domain identifiers is improved.

The following will first introduce the types of nodes involved in this application, then introduce the method for nodes to determine role information, and finally introduce the method of configuring the routing domain identifier shown in this application in combination with specific scenarios.

In some implementations, the node types may include first-level nodes and second-level nodes. In this case, the node type of each node in the network may be determined by the root node; or, determined by other nodes, etc., which are nodes other than the root node in the network. Alternatively, the node type of each node in the network may also be determined by related equipment, etc. The embodiment of the present application does not limit how to determine the node type of the node.

Exemplarily, the node type of the first node may be a first-level node, and the node type of the second node may be a second-level node, so that the second node can learn the first routing domain sent by the first node through the first message ID, so that the routing domain ID of the second port is configured as the first routing domain ID.

Optionally, the node type may also include a third-level node. In this case, after the first-level node generates the routing domain identifier, such as the second routing domain identifier, it sends a message carrying the second routing domain identifier to the third-level node. Then the routing domain identifier of the third-level node configuration port (the port that receives the second routing domain identifier) is the second routing domain identifier, and at the same time, the third-level node can also diffuse the second-level node it learns to the second-level node. Routing domain ID. After the second-level node receives the second routing domain identifier, the routing domain identifier of the configuration port (the port that receives the second routing domain identifier) is the second routing domain identifier.

In this case, after the node knows its node type and the node type of neighboring nodes, it can generate a routing domain identifier; or learn a routing domain identifier, etc.

It can be understood that the first-level nodes, second-level nodes, and third-level nodes shown above are only examples, and the embodiments of the present application do not limit their names. For example, the first-level node may also be called a type A node, the second-level node may also be called a type B node, and the third-level node may also be called a type C node.

In other implementations, the node types may include root nodes, edge nodes, secondary external nodes, and ordinary nodes. Hereinafter, the method provided by the present application will be illustrated by taking node types including root nodes, edge nodes, secondary external nodes, and ordinary nodes as examples.

1) The root node can be a core node in the network; or, it can be a central location in the network. For example, when most nodes in the network visit each other, the most nodes need to pass through the root node. For another example, the mean square error of the shortest path from the root node to other nodes is the smallest. In other words, the root node is the point with the smallest mean square error of the shortest path from other nodes in the network. Exemplarily, the root node may be manually configured; or, the root node may also be designated by other equipment or devices, etc.; or, the root node may also be determined through related negotiation and competition, etc. The embodiment of the present application determines the root node The method is not limited. The other nodes are nodes other than the root node in the network. Optionally, one or more root nodes may be included in the network. The network includes multiple root nodes, that is, the shortest path from other nodes in the network to the multiple root nodes has the smallest mean square error. In this case, the multiple root nodes may have a short distance from each other. Therefore, in a possible implementation manner, the multiple root nodes may be a root node cluster relative to other types of nodes in the network. In other words, when other types of nodes send a message to one of the multiple root nodes, the message is sent to the root node cluster. As to whether the message is specifically sent to a certain root node, the embodiment of the present application does not limit it.

2) Edge nodes are not on the shortest path from other nodes to the root node. The edge node may be connected to the terminal device; or, the edge node may be the most edge node in the network, that is, the downlink of the edge node may not be connected to other devices. Optionally, the downlink of the edge node may also be connected to other nodes, etc. The embodiment of the present application does not limit whether the downlink of the edge node is connected to a terminal device or other nodes.

Exemplarily, the method for determining an edge node may include: for node i in the network, calculating the shortest path from node i to the root node, when node i is not on the shortest path from other nodes to the root node, then node i is Edge node. Other nodes are nodes in the network except node i and the root node.

Optionally, when there is one and only one node i in the network, the node i can be either a root node or an edge node.

3) The secondary external node is located on the shortest path from the root node to the edge node. The secondary foreign node is usually connected to the edge node. For example, the secondary foreign node may be located on the uplink of the edge node.

Exemplarily, the method for determining the secondary external node may include: for a node i in the network, when there is at least one edge node j in the network, and the node i is located on at least one shortest path from the node j to the root node, then the node i It is a secondary external node. Further, there is at least one direct link between the node i and the node j.

4) Ordinary nodes, which can be nodes other than the above-mentioned root nodes, edge nodes, and secondary nodes in the network. Ordinary nodes can play the role of connecting the root node, other ordinary nodes or sub-external nodes in the network.

Exemplarily, the method for determining a common node may include: for a node i in the network, when the node i is not a root node, is not an edge node, and is not a secondary external node, the node i is a common node. For another example, node i is not a root node, not an edge node, and there is a node j as a secondary external node, and node i is located on the shortest path from node j to the root node, then node i is a normal node.

It can be understood that, in some implementation manners, the aforementioned node i is any one of a root node, an edge node, a secondary external node, and a common node. In another implementation manner, the aforementioned node i may have multiple node types. For example, relative to the edge node, the node i can be a secondary external node; relative to the secondary external node, the node i can also be a normal node.

In order to understand the foregoing node types more vividly, refer to FIG. 3a, which is a schematic diagram of a network architecture provided by an embodiment of the present application.

In Figure 3a, node 8 is not on the shortest path from other nodes to the root node (ie, node 1), so this node 8 is an edge node. Similarly, node 2, node 5, and node 6 are all edge nodes.

The node 7 is located on the shortest path from the node 8 to the root node, and the node 7 is connected to the edge node (node 8), so the node 7 is a secondary external node. Among them, the shortest path from node 8 to the root node can be node 8->node 7->node 4->root node; or node 8->node 7->node 3->root node.

For node 5 or node 6, node 3 is located on the shortest path from node 5 or node 6 to the root node, so node 3 is a secondary external node. For the node 7, the node 3 is located on the shortest path from the second outer node (ie, the node 7) to the root node, and the node 3 is not the root node, so the node 3 is a normal node. Similarly, for node 5 or node 6, node 4 is a secondary external node. For node 7, node 4 is a normal node.

At the same time, the uplink of node 2 (edge node) is connected to the root node, and the downlink is connected to terminal equipment. The uplink of the node 8 is connected to the secondary external node, and the downlink may not be connected to the terminal device. In this case, the node 8 can be called the most edge node in the network. The uplink of node 5 or node 6 connects node 3 and node 4, and the downlink connects terminal equipment. The uplink of node 7 connects node 3 and node 4, and the downlink connects edge node (ie, node 8).

It can be understood that the uplink or downlink shown in this application is relative to the direction of the shortest path from other nodes to the root node. For example, the node 7 is located on the shortest path from the node 8 to the root node, so the node to which the uplink connection of the node 8 is connected is the node 7. For another example, the node 3 is located on the shortest path from the node 3 to the root node, so the node connected to the uplink of the node 3 is the root node; correspondingly, the node connected to the downlink of the node 3 is the node 6 or the node 5. It can be understood that the embodiment of the present application does not limit the definition of the uplink or the downlink.

Referring to FIG. 3b, FIG. 3b is a schematic diagram of a network architecture provided by an embodiment of the present application. In Figure 3b, the network includes a two-layer node networking. In this case, the nodes in the network may include root nodes and edge nodes. As shown in FIG. 3b, the root node 10 may be connected to the edge node 11, the edge node 12, the edge node 13, or the edge node 14.

Referring to FIG. 3c, FIG. 3c is a schematic diagram of a network architecture provided by an embodiment of the present application. The method of determining the node type includes: 1) Determining the node 20 as the root node.

2) Based on the root node, the shortest paths from the root node to other nodes v are: node 20->node 21, node 20->node 21->node 23, node 20->node 22, node 20->node 22 ->node 24, node 20->node 22->node 24->node 25.

3) Determine the node type of other nodes in the network except the root node. When the judgment condition of a certain node is insufficient, the node type of other nodes can be determined first.

For example, for node 21, according to the above shortest path, the node 21 is directly connected to the root node, and node 21 is located on the shortest path from node 23 to the root node (node 20 -> node 21 -> node 23), then the node 21 is not an edge node, it may be a normal node or a secondary external node. Because the node 21 is located on the shortest path from the node 23 to the root node, the node type of the node 21 depends on the node type of the node 23. Therefore, the node type of the node 23 can be determined first. Since the node 23 is not on the shortest path from other nodes to the root node, the node type of the node 23 is an edge node, and the node type of the node 21 can be determined as a secondary external node.

Similarly, node 25 is not on the shortest path from other nodes to the root node, so node 25 is an edge node. The node 24 is located on the shortest path from the node 25 to the root node (node 20 -> node 22 -> node 24 -> node 25), and is connected to the node 25, so the node type of the node 24 is the second outer node. The node 22 is located between the secondary outer node and the root node, and the node 22 is not connected to an edge node, so the node 22 is a normal node.

The above method of determining the node type of a node in the network is only an example. In a specific implementation, the method for determining the node type of each node in the network can be executed by the root node and/or other nodes, etc., which is not limited in the embodiment of the present application. For the method of determining the node type, reference may be made to the methods shown in FIGS. 4a to 4c.

The method for determining the node type is shown above, and the method for determining the role information when different nodes are connected is described in detail below.

When the root node is connected to other nodes, the role information of the root node is the domain generation role, and the other nodes need to learn the routing domain identifier obtained from the root node. The other nodes include edge nodes, secondary external nodes, or ordinary nodes. Optionally, the root node may send the generated routing domain identifier to an adjacent node; or, the root node may also send the generated routing domain identifier to the last external node or common node on the downlink. As shown in Figure 3a, node 1 has a role for domain generation relative to node 2, node 3, and node 4. The node 1 may send the generated routing domain identifier to the node 2, the node 3, and the node 4; or, the node 1 may also send the generated routing domain identifier to the node 7. In this case, the node 7 can determine the routing domain identifier of the port connected to the node 4 according to the node type of the uplink node 4 and the node type of the downlink node 8. At the same time, the node 7 can also determine the routing domain identifier of the port connected to the node 3 according to the node type of the uplink node 3 and the node type of the downlink node 8.

It can be understood that, in some implementation manners, the routing domain identifiers of all nodes connected to the root node may be routing domain identifiers generated by the root node. Exemplarily, if the routing protocol specifies that the routing domain where the root node is located is a zero domain, then the routing domain identifier of at least one port of all nodes connected to the root node is zero. As shown in Figure 5a, the routing domain identifiers of port 4 of node 2, port 5 of node 3, port 13 and port 14 of node 4 are all 0. In other implementations, when the root node is directly connected to the edge node, the routing domain where the root node is located may be determined by the number of edge nodes. As shown in Figure 5b, the routing domain where the root node is located includes four. Or, when the root node is directly connected to the edge node, the routing domain of the edge node can be the same. For example, in Figure 5b, node 11, node 12, node 13, node 14 and node 10 can be in the same routing domain, such as The routing domain is identified as area0.

When the edge node is connected to other nodes, the role information of the edge node is the domain generation role, and the other nodes need to learn the routing domain identifier obtained from the edge node. The other nodes include ordinary nodes or sub-external nodes. In other words, the edge node may generate a routing domain identifier. In this case, the routing domain identifiers of all ports of the edge node may be the routing domain identifiers generated by the edge node. However, the routing domain identifiers of different edge nodes are not the same. As shown in Fig. 3a, node 8 has a domain generation role relative to node 7; node 5 or node 6 has a domain generation role relative to node 3 and node 4. Exemplarily, as shown in Figure 5a, the routing domain ID generated by node 8 is ID 3 (area3), the routing domain ID generated by node 5 is ID 4 (area4), and the routing domain ID generated by node 6 is ID 5 (area5). ), the routing domain identifiers of all ports of the node 8 are identifier 3, the routing domain identifiers of all ports of node 5 are identifier 4, and the routing domain identifiers of all ports of node 6 are identifier 5.

The dotted line in FIG. 3a indicates that the node 5 and the node 6 can also be connected, but in the embodiment of the present application, the node 5 and the node 6 are in different routing domains, so the node 5 and the node 6 cannot directly exchange routing information through the routing domain. The dotted line between node 7 and node 6 in Figure 3a indicates that node 6 and node 7 can also be connected, but node 7 is not on the shortest path from node 6 to the root node, so node 6 and node 7 are not in the same routing domain. Exemplarily, when node 6 and node 7 exchange routing information, node 3 or node 4 can exchange routing information.

In Figure 5b, node 11, node 12, node 13, and node 14 belong to different routing domains. Although node 12, node 13 and node 14 can be connected, node 12, node 13 and node 14 are not connected to each other in Figure 5b. The routing information can be directly exchanged through the routing domain.

However, when the edge node is connected to the root node, the role information of the root node may be a domain generating role; or, the role information of the edge node may be a domain generating role. The embodiment of the application does not limit the role information of a network similar to FIG. 3b. Optionally, if the routing protocol stipulates that the routing domain must have a zero domain, the root node in Figure 3b can act as a domain generation role. In this case, the root node can determine different routing domain IDs, one of which can be 0. If the edge node is used as the domain generation role, since it may not be possible to determine which edge node generates the 0 domain between each other, the root node can be used as the domain generation role.

It can be understood that when there are multiple edge nodes connected to the root node in the network, and the root node is also connected to other types of nodes, the multiple edge nodes can be a domain learning role. In this case, the routing domain identifiers where the multiple edge nodes are located may be determined by the root node. In other words, in this case, the routing domain identifiers where the multiple edge nodes are located may be the same. However, when there are other edge nodes that are not connected to the root node in the network, the edge nodes that are not connected to the root node can generate a routing domain identifier. As shown in Fig. 5d, based on the network shown in Fig. 3a, a node 9 is added to the network, and the node 9 is connected to the root node. In this case, the routing domain identifier where the node 9 is located is also area0. Since the node 9 and the node 2 have a domain learning role relative to the root node, the routing domain where the node 9 and the node 2 are located is identified as area0 (that is, the same). However, node 5, node 6 and node 8 are domain generation roles, so the routing domain identifiers of node 5, node 6 and node 8 are not the same. It is understandable that the port identification of each node and the routing domain identification other than area0 are not shown in FIG. 5d, but they should not be understood as a limitation to the embodiment of the present application. It is understandable that the port identifier in the embodiment of the present application may also be referred to as a port number, a port number, etc., and the embodiment of the present application does not limit its name.

For this description, this application is equally applicable to other embodiments. For ease of description, when the root node is connected to the edge node, the following will take the root node as the domain generation role as an example to illustrate the method provided in this application.

Ordinary nodes can learn the routing domain ID obtained from the root node, and can also send the routing domain ID learned from the root node to other adjacent non-root nodes. As shown in Figure 3a, node 4 (ordinary node) can send the routing domain identifier learned from the root node to node 7 (secondary foreign node). In other words, the node 7 not only needs to learn the routing domain ID obtained from the node 4, but also needs to learn the routing domain ID obtained from the node 8.

As shown in Fig. 3b, the node 11, the node 12, the node 13, and the node 14 can respectively learn the routing domain identifier obtained from the root node.

Optionally, the common node may also be connected to the common node. In this case, the routing domain identifiers to which the two common nodes belong may be determined by the root node. Exemplarily, when a common node is connected to a common node, the common node that first learns the routing domain identifier can spread the learned routing domain identifier to another common node. Exemplarily, when a common node is connected to a common node, when the routing domain identifiers learned by two common nodes are different, any one of the routing domain identifiers can be used as the routing domain identifier of the connection port between the two common nodes.

It can be understood that, in addition to ordinary nodes, other nodes in the network may be directly connected to terminal devices. Exemplarily, when a root node is connected to a terminal device, the routing domain identifiers of all ports of the root node may be generated by the root node. If an edge node is connected to a terminal device, the routing domain identifier of the port connected to the terminal device may be the same as the routing domain identifier of the edge node, etc., which is not limited in the embodiment of the present application. If the secondary foreign node is connected to a terminal device, the routing domain ID of the port connected to the terminal device can be the same as the routing domain ID of the edge node; or, it can be the same as the routing domain ID of the root node or ordinary node, etc., this application The embodiment does not limit this.

The above shows the method for determining the node type of each node in the network, and the method for configuring the routing domain identifier provided by the embodiment of the present application will be described below in conjunction with the node type.

Referring to FIG. 4a, FIG. 4a is a schematic flowchart of a method for configuring a routing domain identifier according to an embodiment of the present application. This method can be applied to the first node, as shown in Figure 4a, the method includes:

In a possible implementation manner, the method shown in FIG. 4a includes step 411 and step 412.

411. The first node obtains the node type of the first node in the network and the node type of the second node in the network.

For step 411, the three methods shown in FIG. 4b can be referred to, which are respectively shown below.

method one,

The first node receives a fifth message from the root node, where the fifth message carries the node type of the first node;

The first node receives a second message from the second node, and the second message carries the node type of the second node.

Exemplarily, the node type of the first node may be an edge node, and the node type of the second node is a secondary node or a normal node except the edge node and the root node. In this case, the first routing domain identifier may be generated by the first node, so that the first node sends the first message to the second node.

Exemplarily, the node type of the first node may be a normal node, and the node type of the second node is a secondary node or a normal node. In this case, the first routing domain identifier may be obtained by the first node from other nodes. Exemplarily, for example, the first routing domain identifier may be obtained by the first node from the root node; alternatively, it may be obtained from other ordinary nodes. Thereby the first node can send the first message to the second node.

Optionally, the fifth message may also carry the port identifier of the uplink from the first node to the root node. The second message may also carry the uplink port identifier, such as the second port. It can be understood that the embodiment of the present application does not limit whether the fifth message or the second message carries the port identifier.

In the embodiment of the present application, the root node obtains the node type of other nodes according to the topology of the network, and sends the node type of the other node to the other node. The root node determines or calculates the node type uniformly, which is simple and feasible, and improves other nodes. Get the efficiency of the node type.

Method Two,

The first node obtains the node type of the first node;

In some implementation manners, the first node may obtain the node type of the first node in the network according to the network topology. The first node may obtain the node type of the first node according to the methods shown in FIG. 3a to FIG. 3c. At the same time, the second node can also obtain the node type of the second node in the network according to the network topology, so that the second node can send a node type notification message (ie, the second message) to the first node. In other implementation manners, the first node may also obtain the node type of the first node according to the connection relationship between the first node and the adjacent node, and the second node may also obtain the node type according to the connection relationship between the second node and the adjacent node Get the node type of the second node. The embodiment of the present application does not limit how the first node obtains the node type of the first node. It can be understood that the embodiment of the present application does not limit the method for how the second node learns its node type. In addition to the methods described above, the second node can obtain the node type of the second node from the root node.

Exemplarily, the node type of the first node may be a root node, and the node type of the second node is an edge node, a secondary node, or a common node other than the root node. Alternatively, the node type of the first node is an edge node, and the node type of the second node is a secondary node or a normal node except the edge node and the root node. In this case, the first routing domain identifier may be generated by the first node, so that the first node sends the first message to the second node.

Exemplarily, the node type of the first node is a normal node, and the node type of the second node is a secondary node or a normal node. In this case, the first routing domain identifier may be obtained by the first node from other nodes. Exemplarily, for example, the first routing domain identifier may be obtained by the first node from the root node; alternatively, it may be obtained from other ordinary nodes. Thus, the first node can send the first message to the second node.

Method three

The first node receives a third message from the root node, and the third message carries the node type of the first node and the node type of the second node.

In the third method, the root node may deliver the third message in the form of broadcast, that is, the third message may carry the node type of each node in the network. In this case, the root node can obtain the node type of each node in the network according to the network topology. The root node can obtain the node type of each node according to the method shown in FIG. 3a to FIG. 3c.

Exemplarily, the node type of the first node may be an edge node, and the node type of the second node is a secondary node or a normal node except the edge node and the root node. Or, the node type of the first node is a normal node, and the node type of the second node is a secondary node or a normal node. For the specific implementation of Method 3, please refer to Method 1 or Method 2, which will not be detailed here.

Optionally, the third message may carry the identification information of the first node and the node type of the first node, as well as the identification information of the second node and the node type of the second node. Therefore, after each node receives the third message, it can learn its own node type according to the identification information.

Optionally, the third message may also carry the port identifier of the first node and the port identifier of the second node. In other words, the third message may carry the node type of each node in the network and the port identifier of each node. By including the port identifier of each node in the third message, each node can learn the port identifier connected to other nodes, so that each node can configure the routing domain identifier according to the port identifier and the received routing domain identifier. Exemplarily, after the first node receives the third message, the first node can learn the port identification of the first port, so that the first node generates the first routing domain identification, and then the routing domain identification of the first port Configure as the first routing domain identifier. At the same time, the first node sends the first message to the second node, and after receiving the first message, the second node can configure the routing domain identifier of the second port as the first routing domain identifier. It can be understood that the foregoing is only an example, and the embodiment of the present application does not limit whether the third message carries the port identifier.

412. The first node determines, according to the node type of the first node and the node type of the second node, that the role information of the first node relative to the second node is a domain generation role.

For how the first node determines that its role information is the domain generation role, reference may be made to the specific description of step 411, which will not be described in detail here.

In some implementation manners, the first node may perform step 411, and then obtain the first routing domain identifier (that is, the routing domain identifier of the first port);

In other implementation manners, the first node may also perform step 411 and step 412, and then obtain the first routing domain identifier.

413. The first node obtains the routing domain identifier of the first port of the first node.

Exemplarily, the routing domain identifier of the first port may be the first routing domain identifier. When the first node is a root node or an edge node, the first node may generate a first routing domain identifier; or, when the first node is a normal node, the first node may receive a sixth message from the root node, the sixth message Carry the first routing domain identifier generated by the root node.

414. The first node sends a first message to the second node through the first port, where the first message carries the first routing domain identifier, and the first message is used to instruct the second node to configure the routing domain of the second port of the second node The identifier is the first routing domain identifier, and the second port is the port through which the second node receives the first message. Correspondingly, the second node receives the first message through the second port.

Optionally, the first message may also carry the node type of the first node; or, the first message may also carry indication information, and the indication information is used to indicate that the role information of the first node relative to the second node is Domain generation role. In this case, after receiving the first message, the second node may determine whether to perform step 418 according to the node type or indication information of the first node. Alternatively, the second node may also determine whether to perform step 418 and so on according to step 416 and step 417.

415. The first node configures the routing domain identifier of the first port as the first routing domain identifier.

In a possible implementation manner, the method shown in FIG. 4a may further include step 416 and step 417.

416. The second node obtains the node type of the second node in the network and the node type of the first node in the network.

With reference to the above step 411, the three methods shown in FIG. 4c can be referred to for step 416, which are respectively shown below.

method one,

The second node receives a seventh message from the root node, where the seventh message carries the node type of the second node;

The second node receives a fourth message from the first node, where the fourth message carries the node type of the first node.

It can be understood that the description of the seventh message can refer to the introduction of the fifth message, and the description of the fourth message can refer to the introduction of the second message, which will not be described in detail here.

Method Two,

The second node obtains the node type of the second node;

And the second node receives a fourth message from the first node, where the fourth message carries the node type of the first node.

For how the second node obtains the node type of the second node, please refer to the method for obtaining the node type of the first node, which will not be described in detail here.

Method three

The second node receives a third message from the root node, and the third message carries the node type of the first node and the node type of the second node.

It can be understood that, for the specific implementation of step 416, reference may be made to step 411, which will not be described in detail here.

417. The second node determines, according to the node type of the second node and the node type of the first node, that the role information of the second node relative to the first node is a domain learning role.

In an implementation manner, the method shown in FIG. 4a may include step 411 and step 412.

In another implementation manner, the method shown in FIG. 4a may include step 416 and step 417. In this case, the second node may perform step 416, and then configure the routing domain identifier of the second port as the first routing domain identifier. Alternatively, the second node may also perform step 416 and step 417, and then configure the routing domain identifier of the second port as the first routing domain identifier.

In another implementation manner, the method shown in FIG. 4a may further include step 411, step 412, step 416, and step 417. In this case, both the first node and the second node can determine the role information of the local end relative to the opposite end, double confirm the role information, and ensure the reliability of the routing domain identification configuration.

418. The second node configures the routing domain identifier of the second port as the first routing domain identifier.

419. The first node exchanges routing information with the second node according to the first routing domain identifier. Correspondingly, the second node exchanges routing information with the first node according to the first routing domain identifier.

In order to understand the methods shown in FIGS. 4a to 4c more vividly, routing domains will be divided into the networks shown in FIGS. 3a to 3c in the following. Referring to Fig. 5a, Fig. 5a is a schematic diagram of a scenario for dividing routing domains corresponding to Fig. 3a provided by an embodiment of the present application.

As shown in Figure 5a, node 1 is the root node. For example, node 1 can generate zero fields such as area0, node 1 sends a message carrying area0 to node 4 through port 3, and node 4 receives the message carrying area0 through port 13. Similarly, node 1 sends a message carrying area 0 to node 2 through port 1, and node 2 receives a message carrying area 0 through port 4. Node 1 sends a message carrying area 0 to node 3 through port 2, and node 3 receives the message carrying area 0 through port 5. Node 1 is configured with the routing domain identifier of port 1, port 2, and port 3 as area0. Node 2 is configured with the routing domain ID of port 4 as area0, node 3 is configured with the routing domain ID of port 5 as area0, and node 4 is configured with the routing domain ID of port 13 as area0.

Node 4 is connected to node 7 (secondary foreign node), and node 7 is a secondary foreign node. Therefore, node 4 sends a message carrying area0 to node 7 through port 14, and node 7 receives message carrying area0 sent by node 4 through port 10. . Node 4 configures the routing domain identifier of port 14 as area0, and node 7 configures the routing domain identifier of port 10 as area0.

It can be understood that since node 3 is connected to node 7, refer to the introduction of node 4 and node 7, so node 3 also needs to configure the routing domain identifier of port 18 as area0, and node 7 also needs to configure the routing domain identifier of port 19 as area0.

Since the node 5 and the node 6 are edge nodes, and the node 3 is connected to the node 5 and the node 6 respectively, the node 3 also needs to learn the routing domain identifiers generated by the node 5 and the node 6. Node 5 generates a routing domain identifier such as area4, and sends a message carrying area4 to node 3 through port 8. After node 3 receives the message carrying area4 through port 6, it configures the routing domain identifier of port 6 as area4. At the same time, because node 4 is also on the shortest path from node 5 to the root node, node 5 also needs to send a message carrying area 4 to node 4 through port 17. After node 4 receives the message carrying area 4 through port 15, it configures the port The routing domain of 15 is identified as area4. Similarly, for the generation or diffusion method of the routing domain identifiers of node 6, node 3, and node 4, such as area 5, refer to the method of node 5, node 3, and node 4, which will not be described in detail here. Similarly, node 7 also needs to learn the routing domain identifier generated by node 8. For example, node 8 sends a message carrying area3 to node 7 through port 12, and node 7 receives the message carrying area3 through port 11. Node 8 configures the routing domain identifier of port 12 as area3, and node 7 configures the routing domain identifier of port 11 as area3.

In other words, the routing domain identification of port 8, port 6, port 17, and port 15 is area4. The routing domain identification of port 9, port 7, port 20, and port 16 is area5. The routing domain where port 12 and port 11 are located is identified as area3. The routing domain identification of port 1, port 4, port 2, port 5, port 18, port 19, port 3, port 13, port 14, and port 10 is area0.

According to the method provided by the embodiment of the present application, the network shown in FIG. 3b can be as shown in FIG. 5b after the routing domain identifier is configured. After the network shown in Figure 3c is configured with a routing domain identifier, it can be as shown in Figure 5c. In FIG. 5c, although the node 23 and the node 24 can be connected, the node 24 is not on the shortest path from the node 23 to the root node, so the node 23 may not send the generated routing domain identifier such as area2 to the node 24.

In the embodiment of the present application, after the first node and the second node determine their respective role information through the node type, for example, the role information of the first node relative to the second node is a domain-generated role, so that the first node can report to the second node The node sends the first message. By determining the role information and then configuring the routing domain identification, on the one hand, the process of mutual message exchange and continuous confirmation of role information or routing domain identification is avoided, and the efficiency of mutual negotiation between nodes is improved. On the other hand, nodes can learn routing domain identifications from each other, which realizes the purpose of automatically dividing routing domains and improves the efficiency of node configuration of routing domain identifications.

Refer to FIG. 6, which is a schematic flowchart of a method for configuring a routing domain identifier according to an embodiment of the present application. This method is shown by taking the node type of each node delivered by the root node as an example, but it should not be construed as a limitation to the embodiment of the present application. Exemplarily, as shown in Fig. 7a, Fig. 7a shows the distribution of nodes in a network, and the nodes in the network include a root node, a node S1, a node S2, a node S3, and a node S4. Taking the network shown in Figure 7a as an example, the method shown in Figure 6 includes:

601. The root node sends a configuration message to each node.

For example, the root node may send a configuration message (such as the above fifth message) to node S1, and the configuration message carries the node type of node S1. In another example, the root node sends a configuration message (such as the seventh message described above) to node S2, and the configuration message carries the node type of node S2. In another example, the root node sends a configuration message to node S3, and the configuration message carries the node type of node S3. In another example, the root node sends a configuration message to node S4, and the configuration message carries the node type of node S4. Correspondingly, the node S1, the node S2, the node S3, and the node S4 respectively receive the configuration message.

In order to avoid that one or more of the configuration messages sent by the root node are not received; or to enable each node to know the node type of the neighboring node, the method shown in FIG. 6 may further include step 602. By sending role notification messages between neighboring nodes, the nodes in the network can further confirm their node types. And the neighboring node can also determine the role information of the local end relative to the opposite end through the role notification message.

602. The neighboring nodes send role notification messages to each other.

For example, the root node may send a role notification message to node S1 through port 1, where the role notification message carries identification information of the root node and the node type of the root node. Optionally, the role notification message may also carry identification information of the node S1 (empty by default) and the node type of the node S1 (empty by default). Correspondingly, the node S1 receives the role notification message sent by the root node. Exemplarily, when the root node does not know the node type and identification information of the node S1, the two pieces of information carried in the role notification message may be empty by default. If the node S1 has sent a role notification message to the root node, that is, the root node has learned the identification information and node type of the node S1, the identification information and node type of the node S1 carried in the role notification message. By carrying the identification information and node type of the opposite end, the opposite end can confirm whether the network topology has changed or updated according to the role notification message. And the opposite end can further confirm whether its role information is correct according to the role notification message. It is understandable that the description of the identification information and node type of the peer carried in the role notification message is also applicable to the following.

For another example, the node S1 may send a role notification message to the root node through the port 2, and the role notification message carries the identification information of the node S1 and the node type (normal node) of the node S1. Optionally, the role notification message may also carry the identification information and node type of the root node. Correspondingly, the root node receives the role notification message sent by the node S1.

For another example, the node S1 may also send the role notification message to the node S2 through the port 3. The role notification message may carry the identification information of the node S1, the node type of the node S1, the identification information of the node S2, and the node type of the node S2. Correspondingly, the node S2 can receive the role notification message sent by the node S1.

For another example, the node S2 may also send a role notification message to the node S1 through the port 4. The node S2 may also send a role notification message to the node S3 through the port 5, and send a role notification message to the node S4 through the port 6. For another example, node S3 may send a role notification message to node S2 through port 8, and node S4 may send a role notification message to node S2 through port 7. It can be understood that for the specific description of the role notification message, reference may be made to the description of the root node or node S1, etc., which will not be described in detail here.

Exemplarily, node S1 and node S2 use interactive role notification messages to enable node S1 to learn the node type of node S2, and node S2 to learn the node type of node S1, so that node S1 can determine the relationship between node S1 and node S2. The role information and the node S2 can also determine the role information of the node S2 relative to the node S1. In other words, through the interaction of role notification messages between neighboring nodes, the local node can learn its role information relative to the peer node, so that the node can independently generate routing domain identification or learn routing domain identification, thereby improving configuration routing The efficiency of domain identification.

It can be understood that the embodiment of the present application does not limit the sequence in which each node sends the role notification message. Exemplarily, if the node S1 receives the configuration message sent by the root node, the node S1 can send the role notification message to the root node and send the role notification message to the node S2. At the same time, if the node S2 also receives the configuration message sent by the root node, the node S2 can send a role notification message to the node S1 and the node S3.

It can be understood that the second message or the fourth message shown above can be understood as the role notification message in step 602.

603. Each node determines whether its role information is a domain learning role or a domain generation role.

Exemplarily, the root node may determine that its role information is a domain generation role. The node S3 can determine that its role information is a domain generation role, and the node connected through port 8 is a secondary foreign node. The node S4 can determine that its role information is a domain generation role, and the node connected through port 7 is a secondary foreign node. Node S1 can determine that the node connected through port 2 is the root node, and the role information is the domain learning role; and the node connected through port 3 is the secondary external node, and the role information is the domain generation role (that is, it diffuses to node S2 and learns from the root node To the routing domain identifier). The node S2 can determine that its role information is a domain learning role. On the one hand, it learns the routing domain ID learned from the node S1, and on the other hand, it learns the routing domain ID learned from the node S3 and the node S4. In other words, port 4, port 5, and port 6 of the node S2 belong to different routing domains.

It can be understood that the embodiment of the present application does not limit the order in which each node determines its role information. Exemplarily, if the node S2 receives the role notification messages of the node S1 and the node S3, the node S2 can determine its role information. If the node S3 receives the role notification messages of the node S2 and the node S4, the node S3 can determine its role information.

604. The domain generation role generates a routing domain identification, and the domain learning role learns the routing domain identification.

Exemplarily, the root node generates a routing domain identifier such as area0, and configures the routing domain identifier of port 1 as area0; and sends a first message to node S1 through port 1, and node S1 receives the first message through port 2, and configures port 2. The routing domain is identified as area0. The first message may carry a routing domain identifier such as area0. Optionally, the first message may also carry identification information of the root node, identification information of the node S1, and so on. Thus, the node S1 can confirm whether the connection relationship and role information of the current neighboring nodes are correct according to the first message. If it is correct, the node S1 can learn area0; if it is not correct, the node S1 can send a role notification to the root node again Messages, etc. to confirm the role information of the root node and node S1.

The node S1 diffuses the learned routing domain identifier such as area0 to the node S2 through port 3, and the node S2 receives the first message through port 4, and the first message carries the routing domain identifier such as area0. Optionally, the first message may also carry identification information of the node S1, identification information of the node S2, and so on. The node S1 is configured with the routing domain ID of port 3 as area0, and the node S2 is configured with the routing domain ID of port 4 as area0.

Exemplarily, the node S3 generates a routing domain identifier such as area3, and sends the first message to the node S2 through the port 8; the node S2 receives the first message through the port 5. The first message carries a routing domain identifier such as area3. Optionally, the first message may also carry identification information of node S3, identification information of node S2, and so on. Node S3 configures the routing domain identifier of port 8 as area3, and node S2 configures the routing domain identifier of port 5 as area3.

Exemplarily, the node S4 generates a routing domain identifier such as area4, and sends the first message to the node S2 through the port 7; the node S2 receives the first message through the port 6. The first message carries a routing domain identifier such as area4. Optionally, the first message may also carry identification information of node S4, identification information of node S2, and so on. Node S4 configures the routing domain identifier of port 7 as area4, and node S2 configures the routing domain identifier of port 6 as area4.

It is understandable that the first message is shown as an example in FIG. 6, but the messages sent by different nodes may also have different message names (such as the first message or the sixth message, etc.), which is not limited in the embodiment of the present application.

It can be seen from Fig. 7a that the routing domain identifiers of node S3 (edge node) and node S4 (edge node) are different. And the node S3 and the node S4 both have global domain identifiers, that is, the routing domain identifiers of all the ports of the node S3 are the same, such as area3, and the routing domain identifiers of all the ports of the node S4 are the same, such as area4.

It can also be seen from Figure 7a that the node S2 (secondary external node) can learn routing domain identification from multiple adjacent nodes, and the routing domain identification of each port is different. In this case, the node S2 does not have a global domain identification. Therefore, in a specific implementation, the secondary foreign node may also configure the routing domain identifier of the port connected to the edge node as the routing domain identifier generated by the edge node. And the secondary external node can also join the routing domain where the routing domain identifier learned from the ordinary node or the root node is located.

It can also be seen from FIG. 7a that the routing domain identifiers of all ports of the node S1 are the routing domain identifiers learned from the root node. In this case, the node S1 has a global domain identifier. It can be understood that the node type of the node S1 in FIG. 7a is only a normal node. However, as shown in FIG. 5a, the node types of nodes 3 and 4 can be either secondary external nodes or ordinary nodes. In this case, there is no global domain identifier for ordinary nodes.

It can be understood that the embodiment of the present application does not limit the sequence in which the root node, the node S3, and the node S4 generate the routing domain identifier and send the first message to the opposite node.

In some implementation manners, step 602 may be executed at a certain time interval; or, executed at a fixed frequency, etc., which is not limited in the embodiment of the present application. It can be understood that the certain time interval may be the same as or different from the preset time interval shown in FIG. 2. And the fixed frequency can also be the same as or different from the preset frequency shown in FIG. 2.

In other implementation manners, when the topology of the network changes, step 602 is executed. In this case, the nodes can mutually confirm whether the role information of the local end relative to the opposite end has changed. Further, it can also be determined whether the routing domain identifier where the node is located needs to be updated. Exemplarily, as shown in FIG. 7b, the network is expanded, such as a node S5 is added. In this case, the node S3 can learn that its node type has changed through the role notification message of the node S5. That is, the node type of node S3 changes from an edge node to a secondary external node. At the same time, the node type of node S2 relative to node S3 has also changed, that is, the node type of node S2 has changed from a secondary node to a normal node.

Further, the node S2, the node S3, and the node S5 may execute the methods shown in step 603 and step 604. Exemplarily, the node S2 may send the routing domain identification area0 to the node S3, and the node S3 updates the routing domain identification of the port 8 as area0. Node S3 learns the routing domain identifier obtained from node S5, such as area5, and configures the routing domain identifier of port 9 as area5. Since the node types of the node S4 and the node S2 have not changed, the routing domain identifiers of the node S4 and the node S2 may not be updated.

In other words, when the topology of the network changes, the entire network is prevented from re-dividing the routing domain. By adjusting the routing domain identifiers of a small number of nodes, it is possible to re-deploy the routing domain of the network and improve the efficiency of redeployment. , Improve the dynamic adaptability of the network.

605. Exchange routing information.

Exemplarily, the root node, node S1, and node S2 can exchange routing information with each other. The node S3 and the node S2 can also exchange routing information, and the node S4 and the node S2 can also exchange routing information (not shown in FIG. 7a). Generally, in a routing domain, routing information can be directly exchanged between nodes. When routing information is exchanged between nodes in different routing domains, it is necessary to pass through the border nodes of the routing domain. For example, in Figure 7a, the node S1 needs to send routing information to the node S4. In this case, the node S1 can send the routing information to the node S2, and the node S2 sends the routing information to the node S4. For another example, in Figure 7b, the root node needs to send routing information to node S5, then the root node can send the routing information to node S3, and node S3 can send the routing information to node S5.

In other words, the routing domain identifier shown in the embodiment of the present application can be used to determine the routing mode of the node; or, it can be used to determine the routing domain range (or boundary, etc.) of the node to exchange routing information.

Through the method provided in the embodiments of the present application, each node can construct a routing domain through a routing protocol, thereby learning or generating related routes, and completing the construction of the entire network route.

In the embodiment of the present application, by introducing a node type, the role information is determined according to the node type. The nodes negotiate by themselves (according to certain rules), automatically generate or learn routing identifiers, etc. according to the role information, which improves the adaptability to the networking topology. Further, when the topology structure changes, the node types of the changed nodes can be adjusted, that is, the changed nodes re-negotiate and self-generate the routing domain, which avoids the risk of network disconnection caused by re-planning or even redeployment of the entire network.

It can be understood that each embodiment shown above has its own focus, and for an implementation manner not described in detail in one of the embodiments, reference may be made to other embodiments, which will not be repeated here.

The following will introduce the equipment provided by the embodiment of the present application.

First, the role determination device provided by the embodiment of the present application is introduced. The role determination device can be used to determine the node type according to the network topology. The role determination device may include a processing circuit and an interface circuit. For example, the interface circuit can be used to obtain the topology of the network. It is understandable that the embodiment of the present application does not limit the method for obtaining the topology of the network. For another example, the processing circuit may be used to determine the node type of the node according to the acquired network topology.

Exemplarily, the root node may include the role determining device, so that the root node may obtain the node type of each node in the network. For example, the root node sends the node type of the first node to the first node, and sends the node type of the second node to the second node, and so on.

The processing circuit may be a chip, a logic circuit, an integrated circuit, or a system on chip (system on chip, SoC) chip, etc., and the interface circuit may be a communication interface, an input/output interface, and the like.

Exemplarily, each node in the network may include the role determination device, so that each node may determine the node type of its local node. For example, the first node in the network can obtain its node type according to the network topology; the second node in the network can also obtain its node type according to the network topology.

The functions performed by the role determination device shown in this application can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above-mentioned functions. For example, the role determination device may be a general-purpose computer or a network element device, or the role determination device may also be implemented by software.

Secondly, the network equipment provided in the embodiment of the present application is introduced.

FIG. 8 is a schematic structural diagram of a network device provided by an embodiment of the present application, and the network device may be used to perform operations performed by the first node in the foregoing method embodiments. Exemplarily, the network device may be a switch or router. The switch may also include an access switch, an aggregation switch, or a core switch. Alternatively, the network device may also be other devices with the same function as the switch or router. Alternatively, the network device may also be a general-purpose computer or a network element device, etc., and the network device may be a wired device or a wireless device. For example, the network device can be used to execute the method shown in FIG. 2, FIG. 4a, FIG. 4b, or FIG. 6. As shown in FIG. 8, the network device includes a processing unit 801 and a transceiver unit 802. in,

The processing unit 801 is configured to obtain the routing domain identifier of the first port of the network device; the transceiver unit 802 is configured to send a first message to the second node through the first port, the first message carrying the first routing domain identifier, and the first route The domain ID is the routing domain ID of the first port, the first message is used to instruct the second node to configure the routing domain ID of the second port of the second node as the first routing domain ID, and the second port is the second node receiving the first message Port.

In this embodiment of the present application, the processing unit 801 may be configured to generate the first routing domain identifier; or, the processing unit 801 may also receive the first routing domain identifier sent by other nodes through the transceiver unit 802.

In a possible implementation manner, the processing unit 801 is further configured to configure the routing domain identifier of the first port as the first routing domain identifier.

In the embodiment of the present application, for the specific implementation of the processing unit and the transceiver unit, reference may be made to the method shown in FIG. 2, which will not be described in detail here.

In a possible implementation manner, the transceiver unit 802 is further configured to exchange routing information with the second node according to the first routing domain identifier.

In a possible implementation manner, the network device is an edge node, and the processing unit 801 is further configured to configure the routing domain identifiers of all ports of the network device as the first routing domain identifier.

In a possible implementation manner, the network device is an edge node, and the first routing domain identifier is different from the routing domain identifier obtained by other edge nodes in the network.

In a possible implementation manner, the processing unit 801 is further configured to determine that the role information of the network device relative to the second node is a domain generation role.

In a possible implementation, the processing unit 801 is also used to obtain the node type of the network device in the network and the node type of the second node in the network; and according to the node type of the network device and the node of the second node The type determines the role information of the network device relative to the second node as the domain generation role.

In a possible implementation manner, the processing unit 801 is further configured to obtain the node type of the network device; and receive a second message from the second node through the transceiver unit 802, the second message carrying the node type of the second node .

In a possible implementation manner, the processing unit 801 is configured to receive a fifth message from the root node through the transceiver unit 802, the fifth message carrying the node type of the network device; and the second message from the second node, the first The second message carries the node type of the second node.

In the embodiment of the present application, for the specific implementation of the processing unit 801 and the transceiver unit 802, reference may be made to the methods shown in FIG. 4a and FIG. 4b, which will not be described in detail here. Exemplarily, for the specific description of the second message and the fifth message, reference may also be made to the methods shown in FIG. 4a and FIG. 4b.

In a possible implementation, the transceiver unit 802 is specifically configured to send the first message to the second node through the first port when the topology of the network changes; wherein, the network device and/or the second node It is a node whose node type has changed; or, the network device and/or the second node is a newly-added node.

It can be understood that, for the specific implementation of the transceiver unit 802 in the embodiment of the present application, reference may be made to the related method shown in FIG. 7b, which will not be described in detail here.

In the embodiment of the present application, for the description of the node type, please refer to the above method embodiment, which will not be described in detail here. Exemplarily, for example, the node type may include first-level nodes and second-level nodes; for example, the node type may include first-level nodes, second-level nodes, and third-level nodes; for example, the node type may also include root nodes, Edge nodes, secondary external nodes and ordinary nodes, etc.

Exemplarily, the node type of the network device may be a first-level node or a third-level node, for example. For another example, the node type of the network device may also be a root node or an edge node. For another example, the node type of the network device may also be a normal node, and the node type of the second node is a secondary foreign node or a normal node.

Exemplarily, for the method for determining the node type, reference may be made to the related descriptions in FIGS. 3a to 3c. For the method of how to learn routing domain identifiers between nodes, refer to the related descriptions in Figs. 5a to 5d.

Exemplarily, referring to Fig. 6, Fig. 7a or Fig. 7b, the network device may be the root node in Fig. 6, and the second node is node S1. For another example, the network device may also be node S1, and the second node may be node S2. For another example, the network device may also be node S3 or node S4, and the second node is node S2.

It should be understood that when the network device shown in FIG. 8 is a network device or a component in the network device that implements the above-mentioned functions, the processing unit 801 may be one or more processors, and the transceiver unit 802 may be a transceiver or a transceiver unit. The 802 may also be a sending unit and a receiving unit. The sending unit may be a transmitter, and the receiving unit may be a receiver. The sending unit and the receiving unit are integrated into one device, such as a transceiver.

When the above-mentioned network device is a circuit system such as a chip, the processing unit 801 may be one or more processors, and the transceiver unit 802 may be an input/output interface, also called a communication interface, or an interface circuit, or an interface. Or the transceiver unit 802 may also be a sending unit and a receiving unit, the sending unit may be an output interface, and the receiving unit may be an input interface, and the sending unit and the receiving unit are integrated into one unit, such as an input/output interface.

The network device of the embodiment of the present application can perform any function performed by the first node in the above method embodiment. For the specific executable steps and/or functions, please refer to the detailed description in the above method embodiment, which is only briefly summarized here. No longer.

In a possible implementation manner, the network device shown in FIG. 8 may be the first node in each of the foregoing method embodiments or a component that implements the foregoing functions in the first node. In this case, the above-mentioned transceiving unit 802 may be realized by a transceiver, and the above-mentioned processing unit 801 may be realized by a processor. As shown in FIG. 9, the network device 90 includes one or more processors 920 and a transceiver 910. The processor and the transceiver may be used to execute the function or operation performed by the first node. Alternatively, the processor and transceiver may also be used to perform functions or operations performed by the above-mentioned root node or edge node. Alternatively, the processor and transceiver may also be used to perform functions or operations performed by the above-mentioned first-level nodes.

Exemplarily, the processor may be used to obtain the routing domain identifier of the first port, where the routing domain identifier of the first port is the first routing domain identifier; the transceiver may be used to send the first message to the second node through the first port; processing The device can also be used to configure the routing domain identifier of the first port as the first routing domain identifier.

It can be understood that, for the specific method of the processor and the transceiver, reference may be made to the method shown in FIG. 2.

Exemplarily, the transceiver may also be used to exchange routing information with the second node according to the first routing domain identifier.

Exemplarily, the processor may also be used to determine that the role information of the network device relative to the second node is a domain generation role.

Exemplarily, the processor may also be used to obtain the node type of the network device and the node type of the second node in the network; and determine that the network device is relative to the second node according to the node type of the network device and the node type of the second node The role information of generates roles for the domain.

Exemplarily, the processor may be used to obtain the node type of the network device, and receive the second message sent by the second node through the transceiver.

Exemplarily, the processor may also be used to receive the fifth message from the root node and the second message from the second node through the transceiver.

Exemplarily, the transceiver may also be used to send the first message to the second node through the first port when the topology of the network changes.

For the specific implementation of the transceiver and the processor, reference may be made to the methods shown in FIG. 2, FIG. 4a, FIG. 4b or FIG. 6, which will not be described in detail here. For the method for determining the node type, please refer to the related descriptions in Figs. 3a to 3c. For the method of how to learn routing domain identifiers between nodes, refer to the related descriptions in Figs. 5a to 5d.

In the various implementations of the network device shown in FIG. 9, the transceiver may include a receiver and a transmitter. The receiver is used to perform the function (or operation) of receiving, and the transmitter is used to perform the function (or operation) of transmitting. ). And the transceiver is used to communicate with other devices/devices through the transmission medium. The processor 920 uses the transceiver 910 to send and receive data and/or signaling, and is used to implement the corresponding method described in FIG. 2, FIG. 4a, FIG. 4b, or FIG. 6 in the foregoing method embodiment.

Optionally, the network device 90 may further include one or more memories 930 for storing program instructions and/or data. The memory 930 and the processor 920 are coupled. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. The processor 920 may cooperate with the memory 930 to operate. The processor 920 may execute program instructions stored in the memory 930. Optionally, at least one of the foregoing one or more memories may be included in the processor.

The specific connection medium between the foregoing transceiver 910, the processor 920, and the memory 930 is not limited in the embodiment of the present application. In the embodiment of the present application, the memory 930, the processor 920, and the transceiver 910 are connected by a bus 940 in FIG. 9. The bus is represented by a thick line in FIG. , Is not limited. The bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.

In the embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc., which can be implemented Or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly embodied as execution and completion by a hardware processor, or execution and completion by a combination of hardware and software modules in the processor, and so on.

It can be understood that when the network device shown in FIG. 9 is a network device, the network device may also have more components and the like than that in FIG. 9, which is not limited in the embodiment of the present application.

It can be understood that the methods executed by the processor and the transceiver shown above are only examples, and for the specific steps executed by the processor and the transceiver, reference may be made to the methods introduced above.

In another possible implementation manner, the network device shown in FIG. 8 may be a circuit system in the first node. In this case, the above-mentioned processing unit 801 may be realized by a processing circuit, and the transceiver unit 802 may be realized by an interface circuit. As shown in FIG. 10, the network device may include a processing circuit 1001 and an interface circuit 1002. The processing circuit 1001 may be a chip, a logic circuit, an integrated circuit or a system on chip (SoC) chip, etc., and the interface circuit 1002 may be a communication interface, an input/output interface, and the like. Exemplarily, the network device may be the circuit system of the first node in the foregoing method embodiment. Exemplarily, the network device may also be the circuit system of the root node or the circuit system of the edge node in the foregoing method embodiment. Exemplarily, the network device may also be a circuit system in the first-level node in the foregoing method embodiment.

For example, the processing circuit can be used to obtain the routing domain identification of the first port, the routing domain identification of the first port is the first routing domain identification; the interface circuit can be used to output the first message; the processing circuit can also be used to configure the first port The routing domain identifier is the first routing domain identifier.

It can be understood that, in other implementation manners, the interface circuit may also be used to obtain the routing domain identifier of the first port.

For another example, when the network device is an edge node, the processing circuit may also be used to configure the routing domain identifiers of all ports of the network device as the first routing domain identifier.

For another example, the processing circuit may also be used to determine that the role information of the network device relative to the second node is the domain generation role.

For another example, the processing circuit may also be used to obtain the node type of the network device and the node type of the second node; and determine its role information relative to the second node according to the node type of the network device and the node type of the second node for domain generation Role.

For another example, in some implementation manners, the processing circuit may also be used to obtain the node type of the network device; and the interface circuit may be used to obtain the second message. In other implementation manners, the interface circuit may also be used to obtain the fifth message and the second message.

It can be understood that the above detailed description of each message and node type may refer to the above method embodiment, which will not be described in detail here. For the method for determining the node type, please refer to the related descriptions in Figs. 3a to 3c. For the method of how to learn routing domain identifiers between nodes, refer to the related descriptions in Figs. 5a to 5d.

In the embodiments of the present application, the processing circuit may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc., which can be implemented Or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application.

It can be understood that the methods performed by the interface circuit and the processing circuit shown above are only examples, and the specific steps performed by the interface circuit and the processing circuit can refer to the methods introduced above.

Figure 8 is reused. Figure 8 is a schematic structural diagram of a network device provided by an embodiment of the present application. The network device can be used to perform operations performed by the second node in the foregoing method embodiments. Exemplarily, the network device may be a switch or router. Alternatively, the network device may also be other devices with the same function as the switch or router. For example, the network device can be used to execute the method shown in FIG. 2, FIG. 4a, FIG. 4b, or FIG. 6. As shown in FIG. 8, the network device includes a processing unit 801 and a transceiver unit 802. in,

The transceiver unit 802 is configured to receive a first message from a first node through a second port, the first message carries a first routing domain identifier, and the first message is used to instruct the network device to configure the routing domain identifier of the second port of the network device Is the first routing domain identifier, the routing domain identifier of the first port of the first node is the first routing domain identifier, and the first port is the port through which the first node sends the first message; the processing unit 801 is configured to configure the second port The routing domain identifier is the first routing domain identifier.

In a possible implementation manner, the transceiver unit 802 is further configured to exchange routing information with the first node according to the first routing domain identifier.

In a possible implementation manner, the processing unit 801 is further configured to determine that the role information of the network device relative to the first node is a domain learning role.

In a possible implementation manner, the processing unit 801 is specifically configured to obtain the node type of the network device in the network and the node type of the first node in the network; and according to the node type of the network device and the node of the first node The type determines that the role information of the network device relative to the first node is the domain learning role.

In a possible implementation manner, the processing unit 801 is specifically configured to obtain the node type of the network device; and receive a fourth message from the first node through the transceiver unit 802, the fourth message carrying the node type of the first node.

In a possible implementation, the processing unit 801 may be configured to receive the seventh message from the root node through the transceiver unit 802, the seventh message carrying the node type of the network device; and the fourth message from the first node, The fourth message carries the node type of the first node.

In the embodiment of the present application, for the specific implementation of the processing unit 801 and the transceiving unit 802, reference may be made to the methods shown in FIG. 4a and FIG. 4c, which will not be described in detail here. For the specific description of the fourth message and the seventh message, reference may also be made to the methods shown in FIG. 4a and FIG. 4c.

In a possible implementation, the transceiver unit 802 is further configured to send an eighth message to the third node through the third port, the eighth message carries the first routing domain identifier, and the eighth message is used to instruct the third node to configure the third node. The routing domain identification of the fourth port of the three nodes is the first routing domain identification, and the routing domain identification of the third port is the first routing domain identification; the processing unit 801 is further configured to configure the routing domain identification of the third port as the first route Domain ID.

In this embodiment, referring to FIG. 6, FIG. 7a or FIG. 7b, the first node may be the root node, the network device may be the node S1, and the third node may be the node S2.

In a possible implementation, the transceiver unit 802 is specifically configured to receive the first message from the first node through the second port when the network topology changes, where the first node and/ Or the network device is a node whose node type has changed; or, the first node and/or the network device is a newly-added node.

Exemplarily, the node type of the network device may be a second-level node. For another example, the node type of the network device may also be a secondary node or a normal node.

Exemplarily, referring to FIG. 6, FIG. 7a or FIG. 7b, the first node may also be the root node in FIG. 6, and the network device may be node S1. In another example, the first node may also be node S1, and the network device may be node S2. In another example, the first node may also be node S3 or node S4, and the network device may be node S2.

It can be understood that for the specific introduction of the processing unit and the transceiving unit, reference may also be made to the description of FIG. 8 when the network device is the first node above, which will not be described in detail here.

The network device of the embodiment of the present application can perform any function performed by the second node in the above method embodiment. For the specific executable steps and/or functions, please refer to the detailed description in the above method embodiment, which is only briefly summarized here. No longer.

In a possible implementation manner, the foregoing network device may be a second node or a component in the second node that implements the foregoing functions. In this case, the above-mentioned transceiving unit may be realized by a transceiver, and the processing unit may be realized by a processor. For the specific implementation of the transceiver and the processor, please refer to the processing unit and the transceiver unit, which will not be described in detail here. It can be understood that, for the specific description of the processor and the transceiver, reference may also be made to the description of the foregoing network device as the first node, which will not be described in detail here. For example, when the network device serves as the second node, the network device may also include a memory and the like.

In another possible implementation manner, the foregoing network device may also be a circuit system in the second node. In this case, the above-mentioned transceiver unit may be realized by an interface circuit, and the processing unit may be realized by a processing circuit. Reusing FIG. 10, the processing circuit 1001 may be a chip, a logic circuit, an integrated circuit, a processing circuit, or a system on chip (SoC) chip, etc., and the interface circuit 1002 may be a communication interface, an input/output interface, etc.

For example, the interface circuit may be used to obtain the first message, and the processing circuit may be used to configure the routing domain identifier of the second port as the first routing domain identifier.

For another example, the processing circuit may also be used to determine that the role information of the network device relative to the first node is a domain learning role.

For another example, the processing circuit can also be used to obtain the node type of the network device in the network, and the node type of the first node in the network; and determine the network device relative to the first node according to the node type of the network device and the node type of the first node. The role information of the node is the domain learning role.

For another example, the processing circuit may be used to obtain the node type of the network device; the interface circuit may be used to obtain the fourth message.

For another example, the interface circuit may be used to obtain the fourth message, the seventh message, and so on.

For another example, the interface circuit can also be used to output the eighth message, and the processing circuit can also be used to configure the routing domain identifier of the third port as the first routing domain identifier.

It can be understood that the introduction about the fourth message, the seventh message, or the eighth message, and the introduction about the node type or routing domain identifier, etc. can refer to the description of the method embodiment, which will not be described in detail here.

It can be understood that for the specific introduction of the interface circuit and the processing circuit, reference may be made to the related description when the network device shown in FIG. 10 is the circuit system in the first node, which will not be described in detail here.

FIG. 11 is a schematic diagram of a routing autonomous system provided by an embodiment of the present application. As shown in FIG. 11, the routing autonomous system may include a first node and a second node. The first node can be used to execute the method executed by the first node in Figure 2, Figure 4a, or Figure 4b. Correspondingly, the second node can be used to execute the method executed by the second node in Figure 2, Figure 4a, or Figure 4b. method. Alternatively, the first node may also be used to execute the method executed by the root node in FIG. 6, and the second node may also be used to execute the method executed by the node S1 in FIG. 6. Alternatively, the first node may also be used to execute the method executed by the node S1 in FIG. 6, and the second node may also be used to execute the method executed by the node S2 in FIG. 6. The first node may also be used to execute the method executed by the node S3 or the node S4 in FIG. 6, and the second node may also be used to execute the method executed by the node S2.

Optionally, the routing autonomous system may further include a third node. Exemplarily, the first node may be used to execute the method executed by the root node in FIG. 6, the second node may be used to execute the method executed by the node S1, and the third node may be used to execute the method executed by the node S2. Or, as shown in Figure 7b, the first node can be used to execute the method executed by the root node in Figure 7b, the second node can be used to execute the method executed by node S1 in Figure 7b, and the third node can be used to execute the method executed by the node S1 in Figure 7b. The method executed by node S2. Alternatively, the first node may be used to execute the method executed by node S1 in FIG. 7b, the second node may be used to execute the method executed by node S2 in FIG. 7b, and the third node may be used to execute the method executed by node S3 in FIG. 7b.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the technical effects of the solutions provided by the embodiments of the present application.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of this application is essentially or the part that contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a readable The storage medium includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned readable storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disks or optical disks, etc., which can store program codes. Medium.

In addition, the present application also provides a computer program, which is used to implement the operations and/or processing performed by the first node in the method for configuring a routing domain identifier provided by the present application.

The present application also provides a computer program, which is used to implement the operations and/or processing performed by the second node in the method for configuring the routing domain identifier provided in the present application.

This application also provides a computer-readable storage medium, which stores computer code. When the computer code runs on a computer, the computer executes the method for configuring routing domain identification provided by this application. Operations and/or processing performed by the node.

This application also provides a computer-readable storage medium that stores computer code. When the computer code runs on a computer, the computer executes the method for configuring routing domain identification provided by this application. Operations and/or processing performed by the node.

This application also provides a computer program product. The computer program product includes computer code or computer program. When the computer code or computer program runs on a computer, the first node in the method for configuring routing domain identification provided by this application is The executed operation and/or processing is executed.

This application also provides a computer program product. The computer program product includes computer code or computer program. When the computer code or computer program runs on a computer, the second node in the method for configuring routing domain identification provided by this application is The executed operation and/or processing is executed.

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A method for configuring a routing domain identifier, characterized in that the method includes:

The first node obtains the routing domain identifier of the first port of the first node;

Sending, by the first node, a first message to the second node through the first port, the first message carrying a first routing domain identifier, and the first routing domain identifier is the routing domain identifier of the first port, The first message is used to instruct the second node to configure the routing domain identifier of the second port of the second node as the first routing domain identifier, and the second port is for the second node to receive the The port of the first message.
The method according to claim 1, wherein after the first node sends the first message to the second node through the first port, the method further comprises:

The first node exchanges routing information with the second node according to the first routing domain identifier.
The method according to claim 1 or 2, wherein the first node is an edge node, and the first node configures the routing domain identifiers of all ports of the first node as the first routing domain identifiers .
The method according to any one of claims 1 to 3, wherein the first node is an edge node, and the first routing domain identifier is different from the routing domain identifier obtained by other edge nodes in the network.
The method according to any one of claims 1 to 4, wherein before the first node obtains the routing domain identifier of the first port of the first node, the method further comprises:

The first node determines that the role information of the first node relative to the second node is a domain generation role.
The method according to claim 5, wherein the determining, by the first node, that the role information of the first node relative to the second node is a domain generation role, comprises:

Acquiring, by the first node, the node type of the first node in the network, and the node type of the second node in the network;

The first node determines, according to the node type of the first node and the node type of the second node, that the role information of the first node relative to the second node is the domain generation role.
The method according to claim 6, wherein the first node acquiring the node type of the first node in the network and the node type of the second node in the network comprises:

The first node receives a fifth message from the root node, where the fifth message carries the node type of the first node;

The first node receives a second message from the second node, and the second message carries the node type of the second node.
A method for configuring a routing domain identifier, characterized in that the method includes:

The second node receives a first message from the first node through a second port, the first message carries a first routing domain identifier, and the first message is used to instruct the second node to configure all of the second node The routing domain identifier of the second port is the first routing domain identifier, the routing domain identifier of the first port of the first node is the first routing domain identifier, and the first port is the first node The port for sending the first message;

The second node configures the routing domain identifier of the second port as the first routing domain identifier.
The method according to claim 8, wherein after the second node configures the routing domain identifier of the second port as the first routing domain identifier, the method further comprises:

The second node exchanges routing information with the first node according to the first routing domain identifier.
The method according to claim 8 or 9, wherein before the second node configures the routing domain identifier of the second port as the first routing domain identifier, the method further comprises:

The second node determines that the role information of the second node relative to the first node is a domain learning role.
The method according to claim 10, wherein the determining, by the second node, that the role information of the second node relative to the first node is a domain learning role, comprises:

Acquiring, by the second node, the node type of the second node in the network and the node type of the first node in the network;

The second node determines that the role information of the second node relative to the first node is the domain learning role according to the node type of the second node and the node type of the first node.
The method according to claim 11, wherein the acquiring, by the second node, the node type of the second node in the network and the node type of the first node in the network comprises:

The second node receives a seventh message from the root node, where the seventh message carries the node type of the second node;

The second node receives a fourth message from the first node, where the fourth message carries the node type of the first node.
The method according to any one of claims 1-12, wherein the node type includes one or more of a root node, an edge node, a secondary external node, or a common node; wherein,

The edge node is not on the shortest path from other nodes to the root node, and the other nodes are nodes in the network other than the edge node and the root node;

The secondary foreign node is on the shortest path from the edge node to the root node, and the secondary foreign node is connected to the edge node;

The ordinary node is a node other than the root node, the edge node, and the secondary extra node in the network.
The method of claim 13, wherein:

The node type of the first node is the root node; or,

The node type of the first node is the edge node; or,

The node type of the first node is the normal node, and the node type of the second node is the second foreign node or the normal node.
A network device, characterized in that the network device includes:

A processor, configured to obtain the routing domain identifier of the first port of the network device;

A transceiver, configured to send a first message to a second node through the first port, the first message carrying a first routing domain identifier, the first routing domain identifier being the routing domain identifier of the first port, The first message is used to instruct the second node to configure the routing domain identifier of the second port of the second node as the first routing domain identifier, and the second port is for the second node to receive the The port of the first message.
The network device according to claim 15, wherein:

The transceiver is also configured to exchange routing information with the second node according to the first routing domain identifier.
The network device according to claim 15 or 16, wherein the network device is an edge node, and the processor is further configured to configure the routing domain identifiers of all ports of the network device as the first route Domain ID.
The network device according to any one of claims 15-17, wherein the network device is an edge node, and the first routing domain identifier is different from the routing domain identifier obtained by other edge nodes in the network.
The network device according to any one of claims 15-18, wherein:

The processor is further configured to determine that the role information of the network device relative to the second node is a domain generation role.
The network device according to claim 19, wherein:

The processor is specifically configured to obtain the node type of the network device in the network and the node type of the second node in the network; and according to the node type of the network device and the second node To determine the role information of the network device relative to the second node to generate the role for the domain.
The network device according to claim 20, wherein:

The processor is configured to receive a fifth message from a root node through the transceiver, the fifth message carrying the node type of the network device; and receiving a second message from the second node, the The second message carries the node type of the second node.
A network device, characterized in that the network device includes:

The transceiver is configured to receive a first message from a first node through a second port, the first message carries a first routing domain identifier, and the first message is used to instruct the network device to configure all the network devices The routing domain identifier of the second port is the first routing domain identifier, the routing domain identifier of the first port of the first node is the first routing domain identifier, and the first port is the first node The port for sending the first message;

The processor is configured to configure the routing domain identifier of the second port as the first routing domain identifier.
The network device according to claim 22, wherein:

The transceiver is further configured to exchange routing information with the first node according to the first routing domain identifier.
The network device according to claim 22 or 23, wherein:

The processor is further configured to determine that the role information of the network device relative to the first node is a domain learning role.
The network device according to claim 24, wherein:

The processor is specifically configured to obtain the node type of the network device in the network and the node type of the first node in the network; and according to the node type of the network device and the first node The node type determines that the role information of the network device relative to the first node is the domain learning role.
The network device according to claim 25, wherein:

The processor is specifically configured to receive a seventh message from a root node through the transceiver, where the seventh message carries the node type of the network device; and receive a fourth message from the first node, the first The fourth message carries the node type of the first node.
The network device according to any one of claims 15-26, wherein the node type includes one or more of a root node, an edge node, a secondary node, or a common node; wherein,

The edge node is not on the shortest path from other nodes to the root node, and the other nodes are nodes in the network other than the edge node and the root node;

The secondary foreign node is on the shortest path from the edge node to the root node, and the secondary foreign node is connected to the edge node;

The ordinary node is a node other than the root node, the edge node, and the secondary extra node in the network.
The network device according to claim 27, wherein:

The node type of the first node is the root node; or,

The node type of the first node is the edge node; or,

The node type of the first node is the normal node, and the node type of the network device is the second foreign node or the normal node.
A computer-readable storage medium, characterized by comprising a computer program, when the computer program is run on a computer, the method according to any one of claims 1-7 is executed; or, as claimed in claim 8- The method described in any one of 14 is executed.
A computer program product, characterized in that, when the computer program product runs on a computer, the method according to any one of claims 1-7 is executed; or, when the computer program product is executed, the method according to any one of claims 8-14 is executed. The method described in the item is executed.