Information Processing Method, Network Controller, Node and Computer Readable Storage Medium

Abstract

The present invention provides an information processing method, a network controller, a node, and a computer-readable storage medium. Among them, the information processing method includes: obtaining a first BGP-LS message reported by a first edge node in a first network domain, where the first BGP-LS message carries second segment identification information and first segment identification information configured according to the second segment identification information, the first segment identification information corresponds to the first edge node, and the second segment identification information corresponds to a second edge node in the first network domain; determining that there is a reachable path from the first edge node to the second edge node according to the first segment identification information and the second segment identification information; calculating a routing path including the reachable path, and establishing a segment identification list including the first segment identification information during the process of calculating the routing path. In the embodiments of the present invention, even if the network controller has no permission to obtain the topology information within the first network domain, it can still calculate a routing path spanning the first network domain according to the first segment identification information and the second segment identification information.

Description

Technical Field

[0001] The embodiments of the present invention relate to, but are not limited to, the field of communication technology, and in particular, to an information processing method, a network controller, a node, and a computer-readable storage medium. Background Art

[0002] Segment Routing (SR) is a method of routing based on source nodes. This method can force a flow to pass through any path and service chain by maintaining the state of each flow only on the source node. Neither the intermediate nodes nor the tail nodes need to maintain the state of the flow. Segment routing can be applied to the MPLS (Multi-Protocol Label Switching) data plane and the IPv6 data plane, which are called SR-MPLS and SRv6 respectively.

[0003] In the related art, SRv6 and SR-MPLS or traditional MPLS can communicate with each other by announcing public network routes or virtual private network (VPN) private network routes through the Border Gateway Protocol (BGP). However, in the case where the metropolitan area networks at both ends and the backbone network in the middle are in different network domains, and the network controller has no authority to obtain the topology information in the backbone domain, for example, in the case where the metropolitan area networks at both ends are networks that support SRv6 and the backbone network is a traditional MPLS network, and the network controller has no authority to obtain the topology information of the traditional MPLS network in the backbone domain, the network controller cannot calculate the end-to-end routing path across the metropolitan area-backbone-metropolitan area. Summary of the invention

[0004] The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.

[0005] The embodiments of the present invention provide an information processing method, a network controller, a node and a computer-readable storage medium, which can calculate a routing path across a network domain even if the network controller has no authority to obtain topology information within the network domain.

[0006] In a first aspect, an embodiment of the present invention provides an information processing method, which is applied to a network controller. The information processing method includes:

[0007] Obtain a first Border Gateway Protocol Link-State (BGP-LS) message reported by a first edge node of a first network domain. The first BGP-LS message carries second segment identification information and first segment identification information configured according to the second segment identification information. The first segment identification information corresponds to the first edge node, and the second segment identification information corresponds to a second edge node of the first network domain;

[0008] Determine that there is a reachable path from the first edge node to the second edge node according to the first segment identification information and the second segment identification information;

[0009] Calculate a routing path including the reachable path, and establish a segment identification list including the first segment identification information during the process of calculating the routing path.

[0010] In a second aspect, an embodiment of the present invention further provides an information processing method, which is applied to a first edge node of a first network domain. The information processing method includes:

[0011] Construct a first BGP-LS message carrying first segment identification information and second segment identification information. The second segment identification information comes from a second edge node of the first network domain and corresponds to the second edge node. The first segment identification information is configured according to the second segment identification information and corresponds to the first edge node;

[0012] Report the first BGP-LS message to a network controller, so that the network controller determines that there is a reachable path from the first edge node to the second edge node according to the first segment identification information and the second segment identification information in the first BGP-LS message and calculates a routing path including the reachable path, and enables the network controller to establish a segment identification list including the first segment identification information during the process of calculating the routing path.

[0013] In a third aspect, an embodiment of the present invention further provides a network controller, including: a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, it implements the information processing method in the first aspect as described above.

[0014] In a fourth aspect, an embodiment of the present invention further provides a node, including: a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, it implements the information processing method in the second aspect as described above.

[0015] Fifth aspect, an embodiment of the present invention further provides a computer-readable storage medium storing computer-executable instructions for executing the information processing method as described above.

[0016] An embodiment of the present invention includes: obtaining a first BGP-LS message reported by a first edge node in a first network domain, where the first BGP-LS message carries second segment identification information and first segment identification information configured according to the second segment identification information, the first segment identification information corresponds to the first edge node, and the second segment identification information corresponds to a second edge node in the first network domain; determining, according to the first segment identification information and the second segment identification information, that there is a reachable path from the first edge node to the second edge node; calculating a routing path including the reachable path, and establishing a segment identification list including the first segment identification information during the process of calculating the routing path. According to the solution provided by the embodiment of the present invention, after the network controller obtains the first segment identification information and the second segment identification information reported by the first edge node in the first network domain through the first BGP-LS message, since the first segment identification information corresponds to the first edge node, the second segment identification information corresponds to the second edge node in the first network domain, and the first segment identification information is configured according to the second segment identification information, the network controller can determine, according to the first segment identification information and the second segment identification information, that there is a reachable path across the first network domain from the first edge node to the second edge node, so as to be able to calculate a routing path including the reachable path. Therefore, even if the network controller has no permission to obtain the topological information within the first network domain, the network controller can still calculate a routing path across the first network domain.

[0017] Other features and advantages of the present invention will be described in the following specification, and, in part, will be obvious from the specification, or will be understood by implementing the present invention. The objectives and other advantages of the present invention can be realized and obtained by the structures specifically pointed out in the specification, the claims, and the drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings are used to provide a further understanding of the technical solution of the present invention, and constitute a part of the specification. They are used together with the embodiments of the present invention to explain the technical solution of the present invention, and do not constitute a limitation to the technical solution of the present invention.

[0019] Figure 1 is a schematic diagram of a network topology for executing an information processing method provided by an embodiment of the present invention;

[0020] Figure 2 is a schematic diagram of a network topology for executing an information processing method provided by another embodiment of the present invention;

[0021] Figure 3It is a flowchart of an information processing method applied to a network controller provided by an embodiment of the present invention;

[0022] Figure 4 It is a schematic diagram of a sub-TLV structure carrying first segment identification information provided by an embodiment of the present invention;

[0023] Figure 5 It is a schematic diagram of a sub-TLV structure carrying second segment identification information provided by another embodiment of the present invention;

[0024] Figure 6 It is a flowchart of calculating a routing path in an information processing method provided by another embodiment of the present invention;

[0025] Figure 7 It is a flowchart of an information processing method applied to a first edge node provided by another embodiment of the present invention;

[0026] Figure 8 It is a flowchart of an information processing method applied to a first edge node provided by another embodiment of the present invention;

[0027] Figure 9 It is a flowchart of an information processing method applied to a first edge node provided by another embodiment of the present invention;

[0028] Figure 10 It is a flowchart of forwarding a message according to the first segment identification information in a segment identification list in an information processing method provided by another embodiment of the present invention. Detailed implementation manners

[0029] In order to make the objectives, technical solutions and advantages of the present invention clearer and more understandable, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0030] It should be noted that although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order from the module division in the device or the order in the flowchart. Terms such as "first" and "second" in the specification, claims and the above-mentioned drawings are used to distinguish similar objects and do not necessarily need to describe a specific order or sequence.

[0031] The present invention provides an information processing method, a network controller, a node, and a computer-readable storage medium. The network controller obtains first segment identification information and second segment identification information through first BGP-LS messages reported by a first edge node in a first network domain. Since the first segment identification information corresponds to the first edge node, the second segment identification information corresponds to a second edge node in the first network domain, and the first segment identification information is configured based on the second segment identification information, the network controller can determine that there is a reachable path across the first network domain from the first edge node to the second edge node according to the first segment identification information and the second segment identification information, and thus can calculate a routing path including the reachable path. Therefore, even if the network controller has no permission to obtain the topological information within the first network domain, the network controller can still calculate the routing path across the first network domain. In addition, the network controller will establish a segment identification list including the first segment identification information during the process of calculating the routing path. Therefore, after the network controller sends the segment identification list including the first segment identification information to the node, the node can forward messages according to the segment identification list, so that the messages can be forwarded along the routing path across the first network domain.

[0032] The embodiments of the present invention will be further described below with reference to the accompanying drawings.

[0033] As Figure 1 shown, Figure 1 is a schematic diagram of a network topology for implementing an information processing method provided by an embodiment of the present invention. In the example of Figure 1 , the network topology includes a network controller 100, a first node 121, a second node 122, a third node 111, a fourth node 112, a fifth node 113, a sixth node 131, and a seventh node 132. Among them, the first node 121 and the second node 122 belong to the second network domain 120, the third node 111, the fourth node 112, and the fifth node 113 belong to the first network domain 110, the sixth node 131 and the seventh node 132 belong to the third network domain 130, and the first node 121, the second node 122, the third node 111, the fourth node 112, the fifth node 113, the sixth node 131, and the seventh node 132 are connected in sequence. The first node 121, the second node 122, the third node 111, the fourth node 112, the fifth node 113, the sixth node 131, and the seventh node 132 can be network devices such as routers or switches, and can forward messages. The network controller 100 is respectively connected to the first node 121, the second node 122, the third node 111, the fifth node 113, the sixth node 131, and the seventh node 132, can respectively obtain the node information reported by these nodes, and can calculate the end-to-end routing path according to these node information. In addition, the network controller 100 can also control these nodes respectively.

[0034] In one embodiment, both the second network domain 120 and the third network domain 130 belong to the metropolitan area network, while the first network domain 110 belongs to the backbone network. Additionally, referring to Figure 1 , the second network domain 120 and the third network domain 130 can be SRv6 domains, while the first network domain 110 is an MPLS domain; or, referring to Figure 2 , the second network domain 120 and the third network domain 130 can be MPLS domains, while the first network domain 110 is an SRv6 domain.

[0035] It should be noted that both the third node 111 and the fifth node 113 are edge nodes of the first network domain 110 and both have the ability to support SRv6 and can report relevant node information to the network controller 100. The second node 122 and the third node 111 are BGP peers, the fifth node 113 and the sixth node 131 are BGP peers, the second node 122 stores a link segment identifier for representing the adjacency relationship between the second node 122 and the third node 111, and the sixth node 131 stores a link segment identifier for representing the adjacency relationship between the fifth node 113 and the sixth node 131. Both the second node 122 and the sixth node 131 can report the stored link segment identifiers to the network controller 100.

[0036] In addition, each node in the first network domain 110 can obtain the node information of other nodes in the first network domain 110, so as to be able to establish a reachable path in the first network domain 110. For example, in Figure 1 , the third node 111 can establish a reachable path from the fourth node 112 to the fifth node 113. It should be noted that in the case where the network controller has no permission to obtain the topology information within the first network domain 110, the network controller cannot obtain the specific topology information of this reachable path through the third node 111.

[0037] The network topologies and application scenarios described in the embodiments of the present invention are for more clearly illustrating the technical solutions of the embodiments of the present invention and do not constitute a limitation on the technical solutions provided by the embodiments of the present invention. Those skilled in the art can know that with the evolution of the network topology and the emergence of new application scenarios, the technical solutions provided by the embodiments of the present invention are equally applicable to similar technical problems.

[0038] Those skilled in the art can understand that Figure 1 the various nodes and topological structures shown in

[0039] do not constitute a limitation on the embodiments of the present invention and may include more or fewer components than shown in the figure, or combine some components, or have different component arrangements. Figure 1In the network topology shown, the edge nodes of each network domain can separately call the information processing programs stored therein to execute the information processing method; alternatively, the network controller can call the information processing program stored therein and cooperate with each node to execute the information processing method.

[0040] Based on the above network topology, various embodiments of the information processing method of the present invention are proposed.

[0041] As Figure 3 shown, Figure 3 is a flowchart of an information processing method provided by an embodiment of the present invention. The information processing method is applied to a network controller, and the information processing method includes but is not limited to the following steps:

[0042] Step S110, obtain a first BGP-LS message reported by a first edge node of a first network domain. The first BGP-LS message carries second segment identification information and first segment identification information configured according to the second segment identification information. The first segment identification information corresponds to the first edge node, and the second segment identification information corresponds to a second edge node of the first network domain;

[0043] Step S120, determine that there is a reachable path from the first edge node to the second edge node according to the first segment identification information and the second segment identification information;

[0044] Step S130, calculate a routing path including the reachable path, and establish a segment identification list including the first segment identification information during the process of calculating the routing path.

[0045] In one embodiment, the second segment identification information comes from and corresponds to a second edge node of a first network domain. Therefore, when a first edge node of the first network domain obtains the second segment identification information, the first edge node can pre-configure corresponding first segment identification information for the second segment identification information (i.e., there is a mapping relationship between the first segment identification information and the second segment identification information). When the network controller receives the first segment identification information and the second segment identification information carried in the first BGP-LS message, since the first segment identification information corresponds to the first edge node, the second segment identification information corresponds to the second edge node, and the first segment identification information is configured based on the second segment identification information, therefore, in the case where the network controller has no permission to obtain the topology information within the first network domain, the network controller can regard the first network domain as a black box network that can know the ingress node information and the egress node information but cannot know the specific internal topology structure, that is, the network controller can determine, based on the first segment identification information and the second segment identification information, that there is a reachable path across the first network domain from the first edge node to the second edge node. Therefore, the network controller can calculate a routing path including the reachable path. So, even if the network controller has no permission to obtain the topology information within the first network domain, the network controller can still calculate a routing path across the first network domain. In addition, the network controller will establish a segment identification list including the first segment identification information during the process of calculating the routing path. Therefore, when the network controller distributes the segment identification list including the first segment identification information to the nodes in subsequent steps, it can enable the nodes to forward packets according to the segment identification list, so that the packets can be forwarded along the routing path across the first network domain.

[0046] In one embodiment, the first network domain can be an MPLS domain or an SRv6 domain, and this embodiment does not make specific limitations thereto. When the first network domain is an MPLS domain, the first segment identification information is an SRv6 segment identification, and the second segment identification information is an MPLS label; when the first network domain is an SRv6 domain, the first segment identification information is an MPLS label, and the second segment identification information is an SRv6 segment identification.

[0047] In one embodiment, a sub-TLV can be added to the first BGP-LS message so that the first BGP-LS message can carry the first segment identification information and the second segment identification information.

[0048] The following is an illustration with a specific example:

[0049] In one example, when the first network domain is an MPLS domain, an MPLS Cross Connect Incoming SRv6 SID sub-TLV can be added to the existing Local MPLS Cross Connect TLV in the BGP-LS message structure to carry the first segment of identification information (SRv6 segment identifier). Among them, the Local MPLS Cross Connect TLV is extended and carried through the NLRI (Network Layer Reachability Information) field in the BGP-LS message structure, and the second segment of identification information (MPLS label) is carried in the Local MPLS Cross Connect TLV. Refer to Figure 4 , Figure 4 Exemplarily, the structure of the MPLS Cross Connect Incoming SRv6 SID sub-TLV carrying the first segment of identification information is given. In this sub-TLV structure, the explanations of the main fields are as follows:

[0050] Type: Occupies 2 bytes and is used to indicate that this sub-TLV is the MPLS Cross Connect Incoming SRv6 SID sub-TLV;

[0051] Length: Occupies 2 bytes and is used to indicate the length of this sub-TLV excluding the Type field and the Length field;

[0052] Incoming SRv6 SID: Occupies 16 bytes and is used to indicate the specific value of the first segment of identification information. The specific function is as follows: For an IPv6 packet with the Active Segment Identifier (Active SID) being the first segment of identification information represented by this field, it can be guided to be forwarded along the reachable path mapped to the first segment of identification information.

[0053] After the network controller obtains the content of the second segment identification information in the Local MPLS Cross Connect TLV and the Incoming SRv6 SID field in the MPLS Cross Connect Incoming SRv6 SID sub-TLV (i.e., the first segment identification information), the network controller can include the first segment identification information (SRv6 segment identification) represented by the Incoming SRv6 SID field in an end-to-end SRv6 segment identification list spanning the first network domain, so that when the packet forwarded along the SRv6 segment identification list reaches the edge node corresponding to the first segment identification information, the edge node can exchange the first segment identification information into the MPLS label (i.e., the second segment identification information) pre-stored in the edge node, so that the edge node can forward the packet within the first network domain according to the MPLS label.

[0054] In addition, in another example, when the first network domain is an SRv6 domain, an MPLS Cross Connect Outgoing SRv6 SID sub-TLV can be added to the Local MPLS Cross Connect TLV in the existing BGP-LS message structure. Among them, the Local MPLS Cross Connect TLV is extended and carried through the NLRI field in the BGP-LS message structure, and the Incoming Label field in the Local MPLS Cross Connect TLV carries the first segment identification information (MPLS label), while the MPLS Cross Connect Outgoing SRv6 SID sub-TLV carries the second segment identification information (SRv6 segment identification). Refer to Figure 5 , Figure 5 Exemplarily, the structure of the MPLS Cross Connect Outgoing SRv6 SID sub-TLV carrying the second segment identification information is given. In this sub-TLV structure, the explanations of the main fields are as follows:

[0055] Type: Occupies 2 bytes and is used to indicate that this sub-TLV is the MPLS Cross Connect Outgoing SRv6 SID sub-TLV;

[0056] Length: Occupies 2 bytes and is used to indicate the length of this sub-TLV excluding the Type field and the Length field;

[0057] Outgoing SRv6 SID: It occupies 16 bytes and is used to represent the specific value of the second - segment identification information. Its specific function is as follows: For an MPLS label packet with the top - level label being the first - segment identification information, it can be guided to be forwarded along a reachable path with the second - segment identification information represented by this field as the exit address information.

[0058] When the network controller obtains the content of the Incoming Label field in the Local MPLS Cross Connect TLV (i.e., the first - segment identification information) and the content of the Outgoing SRv6 SID field in the MPLS Cross Connect Incoming SRv6 SID sub - TLV (i.e., the second - segment identification information), the network controller can include the first - segment identification information (MPLS label) represented by the Incoming Label field in an end - to - end SR - MPLS segment identification list spanning the first network domain. When a packet forwarded along this SR - MPLS segment identification list reaches the edge node corresponding to the first - segment identification information, this edge node can exchange the first - segment identification information into the SRv6 segment identification (i.e., the second - segment identification information) pre - stored in this edge node, so that this edge node can forward the packet within the first network domain according to this SRv6 segment identification.

[0059] In addition, in an embodiment, the first BGP - LS message also carries Forwarding Equivalence Class (FEC) information, and this FEC information is used to indicate relevant information about the exit node of the reachable path from the first edge node to the second edge node in the first network domain. In this case, step S120 may include but is not limited to the following steps:

[0060] Determine the existence of a reachable path from the first edge node to the second edge node according to the first - segment identification information, the second - segment identification information, and the FEC information.

[0061] In one embodiment, the FEC information may be the loopback routing information of the egress node of an MPLS LSP (MPLS Label Switching Path) or the global IPv6 routing information to which the egress node of the SRv6 domain belongs. The network controller may utilize this FEC information to complete the path puzzle during end-to-end cross-domain path calculation. For example, when the network controller is unable to obtain the topological information within the first network domain and treats the first network domain as a black box network, when the network controller needs to calculate an end-to-end routing path spanning the first network domain, since the network controller has obtained the first BGP-LS message reported by the first edge node of the first network domain, and this first BGP-LS message carries the first segment identification information, the second segment identification information, and the FEC information, the network controller can thus learn, through the first segment identification information, the second segment identification information, and the FEC information, that there is a reachable path (such as an MPLS LSP or an SRv6 forwarding path) within the first network domain from this first edge node to the second edge node, where the specific information of the second edge node is indicated by the FEC information. Therefore, when an end-to-end routing path spanning the first network domain needs to be calculated, the network controller may establish a segment identification list including the first segment identification information and consider that the first segment identification information in this segment identification list corresponds to a one-hop reachable path from the first edge node to the second edge node, so that the packet can be transparently transmitted along this one-hop reachable path within the black box network (i.e., the first network domain) according to this segment identification list. Therefore, even if the network controller has no permission to obtain the topological information within the first network domain, the network controller can still calculate the routing path spanning the first network domain and can establish a segment identification list including the first segment identification information during the calculation of this routing path, so that the packet can be forwarded along this routing path spanning the first network domain according to this segment identification list.

[0062] In addition, in one embodiment, referring to Figure 6 , the calculation of the routing path including the reachable path in step S130 may include, but is not limited to, the following steps:

[0063] Step S131, obtain a second BGP-LS message reported by a network node of the second network domain, where the second BGP-LS message carries third segment identification information corresponding to the network node of the second network domain;

[0064] Step S132, calculate the routing path including the reachable path according to the first segment identification information, the second segment identification information, and the third segment identification information.

[0065] In one embodiment, the network controller may further obtain a second BGP-LS message reported by a network node in a second network domain. Since the second BGP-LS message carries third segment identification information corresponding to the network node in the second network domain, the network controller can calculate a routing path that spans the first network domain from the second network domain and includes the reachable path based on the first segment identification information, the second segment identification information, and the third segment identification information.

[0066] In one embodiment, the first network domain and the second network domain are different from each other. For example, when the first network domain is an SRv6 domain, the second network domain is an MPLS domain; when the first network domain is an MPLS domain, the second network domain is an SRv6 domain. It should be noted that when the second network domain is an MPLS domain, the third segment identification information is an MPLS label; when the second network domain is an SRv6 domain, the third segment identification information is an SRv6 segment identification.

[0067] In one embodiment, the network node in the second network domain may be an intermediate node in the second network domain or an edge node in the second network domain, and this embodiment does not make specific limitations thereto. When the network node in the second network domain is an intermediate node in the second network domain, the third segment identification information carried in the second BGP-LS message may be the segment identification corresponding to the intermediate node; when the network node in the second network domain is an edge node in the second network domain, a BGP adjacency relationship is established between the edge node in the second network domain and the first edge node in the first network domain. Therefore, the third segment identification information carried in the second BGP-LS message may include the segment identification corresponding to the edge node and the link segment identification corresponding to the BGP adjacency relationship, where the link segment identification corresponds to the adjacency link between the edge node in the second network domain and the first edge node in the first network domain.

[0068] In addition, in one embodiment, the information processing method may further include, but is not limited to, the following steps:

[0069] Send a segment identifier list including the first segment identification information to the first edge node, so that the first edge node forwards the message according to the segment identifier list including the first segment identification information.

[0070] In one embodiment, after the network controller establishes a segment identifier list including first segment identifier information during the process of calculating a routing path, the network controller may send the segment identifier list including the first segment identifier information to a first edge node in a first network domain, so that the first edge node can construct a packet including the first segment identifier information according to the segment identifier list. Therefore, when the first edge node forwards a packet according to the segment identifier list including the first segment identifier information, the packet can be forwarded along a routing path spanning the first network domain according to the segment identifier list including the first segment identifier information. Therefore, even if the network controller has no permission to obtain the topology information within the first network domain, the network controller can still establish a segment identifier list that enables packets to be forwarded across the first network domain, thereby meeting the cross-domain service forwarding requirements brought about by the incremental deployment of the SRv6 network in the network.

[0071] In addition, in one embodiment, the information processing method may further include, but is not limited to, the following steps:

[0072] Send the segment identifier list including the first segment identifier information to a network node in a second network domain, so that the network node in the second network domain can forward a packet according to the segment identifier list including the first segment identifier information.

[0073] In one embodiment, after the network controller establishes a segment identifier list including first segment identifier information during the process of calculating a routing path, the network controller may send the segment identifier list including the first segment identifier information to a network node in a second network domain, so that the network node in the second network domain can construct a packet including the first segment identifier information according to the segment identifier list. Therefore, when the network node in the second network domain forwards a packet according to the segment identifier list including the first segment identifier information, the packet can be forwarded along a routing path from the second network domain spanning the first network domain according to the segment identifier list including the first segment identifier information. Therefore, even if the network controller has no permission to obtain the topology information within the first network domain, the network controller can still establish a segment identifier list that enables packets to be forwarded from the second network domain across the first network domain, thereby meeting the cross-domain service forwarding requirements brought about by the incremental deployment of the SRv6 network in the network.

[0074] In addition, another embodiment of the present invention further provides an information processing method, as Figure 7 shown, Figure 7 is a flowchart of the information processing method provided by another embodiment of the present invention. The information processing method is applied to a first edge node in a first network domain. The information processing method includes, but is not limited to, the following steps:

[0075] Step S210: Construct a first BGP-LS message carrying first segment identification information and second segment identification information. The second segment identification information comes from a second edge node of the first network domain and corresponds to the second edge node. The first segment identification information is configured based on the second segment identification information and corresponds to the first edge node.

[0076] Step S220: Report the first BGP-LS message to the network controller, so that the network controller determines that there is a reachable path from the first edge node to the second edge node based on the first segment identification information and the second segment identification information in the first BGP-LS message, calculates a routing path including the reachable path, and causes the network controller to establish a segment identification list including the first segment identification information during the process of calculating the routing path.

[0077] In an embodiment, when the first edge node obtains the second segment identification information from the second edge node of the first network domain and corresponding to the second edge node, the first edge node can first configure corresponding first segment identification information for the second segment identification information (that is, there is a mapping relationship between the first segment identification information and the second segment identification information). Then, the first edge node constructs a first BGP-LS message carrying the first segment identification information and the second segment identification information. Then, the first edge node reports the first BGP-LS message to the network controller. When the network controller obtains the first segment identification information and the second segment identification information according to the first BGP-LS message, due to the mapping relationship between the first segment identification information and the second segment identification information, the network controller can regard the first network domain as a black box network that can know the ingress node information and the egress node information but cannot know the specific internal topology structure, and can determine that there is a reachable path from the first edge node to the second edge node across the first network domain based on the first segment identification information and the second segment identification information. Therefore, the network controller can calculate a routing path including the reachable path. So, even if the network controller has no permission to obtain the topology information within the first network domain, the network controller can still calculate the routing path across the first network domain. In addition, the network controller will establish a segment identification list including the first segment identification information during the process of calculating the routing path. Therefore, when the first edge node receives the segment identification list including the first segment identification information sent by the network controller in the subsequent steps, the first edge node can forward the message according to the segment identification list, so that the message can be forwarded along the routing path across the first network domain.

[0078] In one embodiment, the first network domain may be an MPLS domain or an SRv6 domain, and this embodiment does not make specific limitations thereto. When the first network domain is an MPLS domain, the first segment of identification information is an SRv6 segment identifier, and the second segment of identification information is an MPLS label; when the first network domain is an SRv6 domain, the first segment of identification information is an MPLS label, and the second segment of identification information is an SRv6 segment identifier.

[0079] In one embodiment, the first edge node can make the first BGP-LS message carry the first segment of identification information and the second segment of identification information by adding a sub-TLV to the first BGP-LS message. For example, when the first network domain is an MPLS domain, an MPLS Cross Connect Incoming SRv6 SID sub-TLV can be added to the Local MPLS Cross Connect TLV in the existing BGP-LS message structure to carry the first segment of identification information (SRv6 segment identifier). Among them, the Local MPLS Cross Connect TLV is extended and carried through the NLRI (Network Layer Reachability Information) field in the BGP-LS message structure, and the second segment of identification information (MPLS label) is carried in the Local MPLS Cross Connect TLV. Another example is that when the first network domain is an SRv6 domain, an MPLS Cross Connect Outgoing SRv6 SID sub-TLV can be added to the Local MPLS Cross Connect TLV in the existing BGP-LS message structure. Among them, the Local MPLS Cross Connect TLV is extended and carried through the NLRI field in the BGP-LS message structure, and the Incoming Label field in the Local MPLS Cross Connect TLV carries the first segment of identification information (MPLS label), while the MPLS Cross Connect Outgoing SRv6 SID sub-TLV carries the second segment of identification information (SRv6 segment identifier).

[0080] It should be noted that in this embodiment, when the first network domain is an MPLS domain, the MPLS Cross Connect Incoming SRv6 SID sub-TLV added to the Local MPLS Cross Connect TLV, and Figure 4The MPLS Cross Connect Incoming SRv6 SID sub-TLV in the illustrated embodiment has the same structure and meaning explanation. For the structure and meaning explanation of the MPLS Cross Connect Incoming SRv6 SID sub-TLV in this embodiment, reference can be made to the relevant description of the MPLS Cross Connect Incoming SRv6 SID sub-TLV in the embodiment shown as Figure 4 above. To avoid repetition of content, it will not be elaborated here. In addition, in this embodiment, when the first network domain is an SRv6 domain, the newly added MPLS Cross Connect Outgoing SRv6 SID sub-TLV in the Local MPLS Cross Connect TLV and the Figure 5 MPLS Cross Connect Outgoing SRv6 SID sub-TLV in the embodiment shown as Figure 5 above have the same structure and meaning explanation. For the structure and meaning explanation of the MPLS Cross Connect Outgoing SRv6 SID sub-TLV in this embodiment, reference can be made to the relevant description of the MPLS Cross Connect Outgoing SRv6 SID sub-TLV in the embodiment shown as

[0081] above. To avoid repetition of content, it will not be elaborated here.

[0081] In addition, in an embodiment, the first BGP-LS message further carries FEC information, and the FEC information is used to indicate relevant information of the egress node of the reachable path from the first edge node to the second edge node in the first network domain. In this case, the first BGP-LS message enables the network controller to determine the existence of a reachable path from the first edge node to the second edge node based on the first segment identification information, the second segment identification information, and the FEC information in the first BGP-LS message and calculate a routing path including the reachable path, and enables the network controller to establish a segment identification list including the first segment identification information during the process of calculating the routing path.

[0082] In one embodiment, the FEC information may be the loopback routing information of the egress node of the MPLS LSP or the global IPv6 routing information to which the egress node of the SRv6 domain belongs. The network controller may use this FEC information to complete the path puzzle during end-to-end cross-domain path calculation. For example, when the network controller cannot obtain the topological information within the first network domain and regards the first network domain as a black box network, when the network controller needs to calculate an end-to-end routing path across the first network domain, since the first BGP-LS message reported by the first edge node carries the first segment identification information, the second segment identification information, and the FEC information, the network controller can learn that there is a reachable path (such as an MPLS LSP or an SRv6 forwarding path) from the first edge node to the second edge node within the first network domain through the first segment identification information, the second segment identification information, and the FEC information. Among them, the specific information of the second edge node is indicated by the FEC information. Therefore, when an end-to-end routing path across the first network domain needs to be calculated, the network controller may establish a segment identification list including the first segment identification information and consider that the first segment identification information in the segment identification list corresponds to a one-hop reachable path from the first edge node to the second edge node. Therefore, the message can be transparently transmitted along the one-hop reachable path within the black box network (i.e., the first network domain) according to the segment identification list. Therefore, even if the network controller has no permission to obtain the topological information within the first network domain, the network controller can still calculate the routing path across the first network domain and establish a segment identification list including the first segment identification information during the process of calculating the routing path, so that the message can be forwarded along the routing path across the first network domain according to the segment identification list.

[0083] In addition, in one embodiment, referring to Figure 8 , the information processing method may further include but is not limited to the following steps:

[0084] Step S230, obtaining a message forwarded according to a segment identification list including the first segment identification information;

[0085] Step S240, forwarding the message according to the first segment identification information in the segment identification list.

[0086] In one embodiment, after the network controller establishes a segment identifier list including first segment identifier information during the process of calculating a routing path, the network controller may distribute the segment identifier list including the first segment identifier information to the network nodes in the second network domain, so that the network nodes in the second network domain can construct and forward packets according to the segment identifier list. When the first edge node in the first network domain obtains a packet forwarded by the network nodes in the second network domain according to the segment identifier list, the first edge node will forward the packet according to the first segment identifier information in the segment identifier list, so that the packet can be forwarded along a routing path that spans from the second network domain to the first network domain according to the segment identifier list including the first segment identifier information. Therefore, even if the network controller has no permission to obtain the topology information within the first network domain, the network controller can still establish and distribute a segment identifier list that can enable packets to be forwarded across the first network domain from the second network domain, thereby meeting the cross-domain service forwarding requirements brought about by the incremental deployment of SRv6 networks in the network.

[0087] In addition, in one embodiment, referring to Figure 9 , the information processing method may further include but is not limited to the following steps:

[0088] Step S250: Obtain a segment identifier list including first segment identifier information distributed by the network controller;

[0089] Step S260: Construct a packet according to the segment identifier list including the first segment identifier information;

[0090] Step S270: Forward the packet according to the first segment identifier information in the segment identifier list.

[0091] In one embodiment, after the network controller establishes a segment identifier list including first segment identifier information during the process of calculating a routing path, the network controller may distribute the segment identifier list including the first segment identifier information to the first edge node in the first network domain, so that the first edge node in the first network domain can construct and forward packets according to the segment identifier list, thereby enabling the packets to be forwarded along a routing path that spans the first network domain according to the segment identifier list including the first segment identifier information. Therefore, even if the network controller has no permission to obtain the topology information within the first network domain, the network controller can still establish and distribute a segment identifier list that can enable packets to be forwarded across the first network domain, thereby meeting the cross-domain service forwarding requirements brought about by the incremental deployment of SRv6 networks in the network.

[0092] It should be noted that in the above embodiments as Figure 8 shown, when the first edge node is a node in the MPLS domain, the packet received by the first edge node is an IPv6 packet, and the first segment identifier information is an SRv6 segment identifier; in the above as Figure 9In the illustrated embodiment, when the first edge node is a node in the MPLS domain, the packet constructed and forwarded by the first edge node is an IPv6 packet, and the first segment identifier information is the SRv6 segment identifier. Regardless of whether it is in the embodiment as shown in Figure 8 the illustrated embodiment or in the embodiment as shown in Figure 9 the illustrated embodiment, when the first edge node forwards a packet according to the first segment identifier information in the segment identifier list, the first edge node can exchange the first segment identifier information for the second segment identifier information (MPLS label), and additionally encapsulate the intermediate segment identifier list corresponding to the second segment identifier information outside the packet, so that the packet forms an MPLS label packet, thereby enabling the MPLS label packet to be transparently transmitted along the reachable path within the first network domain. In addition, in the embodiment as shown in Figure 8 the illustrated embodiment, when the first edge node is a node in the SRv6 domain, the packet received by the first edge node is an MPLS label packet, and the first segment identifier information is the MPLS segment identifier; in the embodiment as shown in Figure 9 the illustrated embodiment, when the first edge node is a node in the SRv6 domain, the packet constructed and forwarded by the first edge node is an MPLS label packet, and the first segment identifier information is the MPLS segment identifier. Regardless of whether it is in the embodiment as shown in Figure 8 the illustrated embodiment or in the embodiment as shown in Figure 9 the illustrated embodiment, when the first edge node forwards a packet according to the first segment identifier information in the segment identifier list, the first edge node can exchange the first segment identifier information for the second segment identifier information (SRv6 segment identifier), and additionally encapsulate the intermediate segment identifier list corresponding to the second segment identifier information outside the packet, so that the packet forms an IPv6 packet, thereby enabling the IPv6 packet to be transparently transmitted along the reachable path within the first network domain.

[0093] In addition, in one embodiment, referring to Figure 10 , such as step S240 in the embodiment as shown in Figure 8 or step S270 in the embodiment as shown in Figure 9 the illustrated embodiment may include but is not limited to the following steps:

[0094] Step S281, look up and match the segment identifier information in the segment identifier list to obtain the identifier information entry;

[0095] Step S282, obtain the second segment identifier information from the identifier information entry according to the first segment identifier information;

[0096] Step S283, update the first segment identifier information in the segment identifier list to the second segment identifier information;

[0097] Step S284, construct a new packet header according to the second segment identifier information to form a new packet;

[0098] Step S285, forward the new message.

[0099] In one embodiment, when the first edge node forwards a message according to the first segment identification information in the segment identification list, the first edge node may first look up and match the first segment identification information in the segment identification list to obtain the identification information entry pre-created in the first edge node. This identification information entry represents the mapping relationship between the first segment identification information and the second segment identification information. At this time, the first edge node may obtain the second segment identification information corresponding to the first segment identification information from this identification information entry according to the first segment identification information. Then, the first edge node may replace the first segment identification information in the segment identification list with the second segment identification information. At this time, the first edge node can construct a new message header according to the second segment identification information in the segment identification list to form a new message. Then, the first edge node will forward the new message according to the new message header, so that the new message can be transparently transmitted along the reachable path within the first network domain.

[0100] In one embodiment, when the first edge node configures the corresponding first segment identification information for the obtained second segment identification information, the first edge node will correspondingly create an identification information entry. According to the network domain to which the first edge node belongs, the identification information entry pre-created in the first edge node can have different implementation manners. For example, when the first edge node is a node in the MPLS domain, this identification information entry is a local segment identification table entry, and this local segment identification table entry contains the first segment identification information (SRv6 segment identification) and the second segment identification information (MPLS label) corresponding to the first segment identification information. Another example is that when the first edge node is a node in the SRv6 domain, this identification information entry is an Incoming Label Map (ILM) table entry. The forwarding information contained in this ILM table entry indicates that the first segment identification information (MPLS label) is exchanged for the second segment identification information (SRv6 segment identification) corresponding to the first segment identification information and is forwarded to the second edge node along the shortest path. This ILM table entry reflects a reachable path across the first network domain from the first edge node to the second edge node.

[0101] In one embodiment, according to the network domain to which the first edge node belongs, the first edge node can construct a new packet header based on the second segment identification information in different implementation manners. For example, when the first edge node is a node in the MPLS domain, the new packet header is an MPLS label stack. The first edge node will form an MPLS label stack to the second segment identification information based on the second segment identification information (MPLS label) and the MPLS labels advertised by other nodes in the first network domain. At this time, by encapsulating the MPLS label stack to the outer layer of the packet, a new packet that can be forwarded within the first network domain can be formed. Another example is that when the first edge node is a node in the SRv6 domain, the new packet header is an SRv6 segment identification list formed by an IPv6 address list. The first edge node will form an SRv6 segment identification list to the second segment identification information based on the second segment identification information (SRv6 segment identification) and the SRv6 segment identifications advertised by other nodes in the first network domain. At this time, by encapsulating the SRv6 segment identification list to the outer layer of the packet, a new packet that can be forwarded within the first network domain can be formed.

[0102] For the information processing method provided in the above embodiment, the following will be described in detail with specific examples:

[0103] Example 1:

[0104] As Figure 1 shown, both the second network domain 120 and the third network domain 130 are SRv6 domains, and the first network domain 110 is an MPLS domain. Among them, the second network domain 120 includes a first node 121 and a second node 122 connected in sequence. The first network domain 110 includes a third node 111, a fourth node 112, and a fifth node 113 connected in sequence. The third network domain 130 includes a sixth node 131 and a seventh node 132 connected in sequence. The second node 122 and the third node 111 are BGP peers, and the fifth node 113 and the sixth node 131 are BGP peers. The network controller 100 is respectively connected to the first node 121, the second node 122, the third node 111, the fifth node 113, the sixth node 131, and the seventh node 132.

[0105] The network controller 100 needs to calculate an end-to-end SR-TE (Segment Routing Traffic Engineering) path from the first node 121 to the seventh node 132. This SR-TE path sequentially traverses the second network domain 120, the first network domain 110, and the third network domain 130. Among them, the third node 111 and the fifth node 113 have the ability to support SRv6.

[0106] The second node 122 stores a link segment identifier END.X SID(122-111) for representing the adjacency relationship between the second node 122 and the third node 111. The sixth node 131 stores a link segment identifier END.X SID(113-131) for representing the adjacency relationship between the fifth node 113 and the sixth node 131. The third node 111 creates a BGP LU LSP (BGP Labeled Unicast LSP, BGP label unicast label forwarding channel) to the fifth node 113 within the first network domain 110, and the third node 111 configures a first segment identifier information sid-100 for this BGP LU LSP according to the locally configured policy.

[0107] The third node 111 reports the local MPLS cross-connection information corresponding to this BGP LU LSP to the network controller 100. This local MPLS cross-connection information is denoted as XC(from 111to 113). Moreover, this local MPLS cross-connection information includes the first segment identifier information sid-100, the second segment identifier information label-100 corresponding to the fifth node 113, the outgoing interface, and the FEC information corresponding to the fifth node 113, etc. Therefore, based on this local MPLS cross-connection information, the network controller 100 can perceive that there is a one-hop reachable path from the third node 111 to the fifth node 113 within the first network domain 110. So, the network controller 100 can calculate the end-to-end SR-TE path as <122, 122-111, XC(from111to113), 113-131,132>. Translating this SR-TE path into an SRv6 segment identifier list, the obtained SRv6 segment identifier list is <END SID(122), END.X SID(122-111), sid-100, END.X SID(113-131), END SID(132)>. Then, the network controller 100 distributes this SRv6 segment identifier list to the first node 121 so that the first node 121 forwards the IPv6 packet according to this SRv6 segment identifier list.

[0108] In the first node 121, when the IPv6 packet is forwarded along this SRv6 segment identifier list, the first node 121 encapsulates an IPv6 header and a segment routing header for this IPv6 packet. Among them, the segment routing header contains this SRv6 segment identifier list. The following is the specific forwarding process of the IPv6 packet:

[0109] The first node 121 forwards the IPv6 packet to the second node 122 along the shortest path according to the first segment identifier END SID(122) in the SRv6 segment identifier list;

[0110] The second node 122 forwards the IPv6 packet explicitly along the inter-domain link to the third node 111 according to the second segment identifier END.X SID (122-111) in the SRv6 segment identifier list;

[0111] The third node 111 hits the corresponding local segment identifier entry in the third node 111 according to the third segment identifier sid-100 (i.e., the first segment identifier information) in the SRv6 segment identifier list, exchanges the first segment identifier information sid-100 for the second segment identifier information label-100, and obtains the corresponding MPLS label stack to the fifth node 113 according to the second segment identifier information label-100, and encapsulates the outer MPLS label stack for the IPv6 packet, so that the IPv6 packet forms an MPLS label packet, so that the MPLS label packet is transparently transmitted to the fifth node 113 in the first network domain 110 all the time according to the forwarding method of traditional MPLS;

[0112] In the fifth node 113, the outer MPLS labels of the MPLS label packet will be all popped up, thus revealing the inner IPv6 header. At this time, the MPLS label packet is restored to an IPv6 packet, and the IPv6 packet is explicitly forwarded along the inter-domain link to the sixth node 131 according to the fourth segment identifier END.X SID (113-131) in the SRv6 segment identifier list;

[0113] The sixth node 131 forwards the IPv6 packet to the seventh node 132 along the shortest path according to the fifth segment identifier END SID (132) in the SRv6 segment identifier list.

[0114] Example 2:

[0115] As Figure 2 shown, the second network domain 120 and the third network domain 130 are both SR-MPLS domains, and the first network domain 110 is an SRv6 domain. Among them, the second network domain 120 includes a first node 121 and a second node 122 connected in sequence, the first network domain 110 includes a third node 111, a fourth node 112 and a fifth node 113 connected in sequence, the third network domain 130 includes a sixth node 131 and a seventh node 132 connected in sequence, the second node 122 and the third node 111 are BGP peers with each other, the fifth node 113 and the sixth node 131 are BGP peers with each other, and the network controller 100 is respectively connected to the first node 121, the second node 122, the third node 111, the fifth node 113, the sixth node 131 and the seventh node 132.

[0116] The network controller 100 needs to calculate an end-to-end SR-TE path from the first node 121 to the seventh node 132, which sequentially traverses the second network domain 120, the first network domain 110, and the third network domain 130. Among them, the third node 111 and the fifth node 113 have the ability to support both SR-MPLS and SRv6 simultaneously.

[0117] The second node 122 stores the link segment identifier Adjacency-SID(122-111) representing the adjacency relationship between the second node 122 and the third node 111. The sixth node 131 stores the link segment identifier Adjacency-SID(113-131) representing the adjacency relationship between the fifth node 113 and the sixth node 131. The third node 111 receives the node segment identifier END SID(113) (i.e., the second segment identifier information) of the fifth node 113 advertised by the fifth node 113 through the IGP (Interior Gateway Protocol). The third node 111 configures a first segment identifier information label-200 for the node segment identifier END SID(113) of the fifth node 113 according to the locally configured policy, and creates a corresponding ILM entry. The forwarding information included in the ILM entry indicates that the first segment identifier information label-200 is exchanged for the second segment identifier information END SID(113) and forwarded to the fifth node 113 along the shortest path. It should be noted that the third node 111 can also configure the local policy to directly allocate an additional first segment identifier information (MPLS label) for the node segment identifier of the fifth node 113.

[0118] The third node 111 reports the local MPLS cross-connection information corresponding to this ILM entry to the network controller 100. This local MPLS cross-connection information is denoted as XC(from 111 to 113). Moreover, this local MPLS cross-connection information includes information such as the first segment identification information label-200, the second segment identification information END SID(113), the outgoing interface, and the FEC information corresponding to the fifth node 113. Therefore, based on this local MPLS cross-connection information, the network controller 100 can perceive that there is a one-hop reachable path from the third node 111 to the fifth node 113 within the first network domain 110. Thus, the network controller 100 can calculate the end-to-end SR-TE path as <122, 122-111, XC(from 111 to 113), 113-131, 132>. Translating this SR-TE path into an SR-MPLS segment identification list, the SR-MPLS segment identification list can be obtained as <Node-SID(122), Adjacency-SID(122-111), label-200, Adjacency-SID(113-131), Node-SID(132)>. Then, the network controller 100 distributes this SR-MPLS segment identification list to the first node 121 so that the first node 121 can forward the MPLS label packet according to this SR-MPLS segment identification list.

[0119] In the first node 121, when the MPLS label packet is forwarded along this SR-MPLS segment identification list, the first node 121 encapsulates an outer MPLS label stack for this MPLS label packet. Among them, the MPLS label stack contains this SR-MPLS segment identification list. The following is the specific forwarding process of the MPLS label packet:

[0120] Based on the first segment identification Node-SID(122) in the SR-MPLS segment identification list, the first node 121 forwards the MPLS label packet to the second node 122 along the shortest path;

[0121] Based on the second segment identification Adjacency-SID(122-111) in the SR-MPLS segment identification list, the second node 122 explicitly forwards the MPLS label packet along the inter-domain link to the third node 111;

[0122] The third node 111 hits the corresponding ILM entry in the third node 111 according to the third segment identifier label-200 (i.e., the first segment identifier information) in the SR-MPLS segment identifier list, exchanges the first segment identifier information label-200 into the second segment identifier information END SID(113), obtains the corresponding SRv6 segment identifier list to the fifth node 113 according to the second segment identifier information END SID(113), and encapsulates the outer IPv6 header for the MPLS label packet, so that the MPLS label packet forms an IPv6 packet, so that the IPv6 packet is transparently transmitted to the fifth node 113 in the first network domain 110 all the time according to the forwarding mode of the traditional IPv6 packet;

[0123] In the fifth node 113, the outer IPv6 header of the IPv6 packet will be removed, thus exposing the inner MPLS label packet. At this time, the IPv6 packet is restored to the MPLS label packet, and the MPLS label packet is explicitly forwarded along the inter-domain link to the sixth node 131 according to the fourth segment identifier Adjacency-SID(113-131) in the SR-MPLS segment identifier list;

[0124] The sixth node 131 forwards the MPLS label packet to the seventh node 132 along the shortest path according to the fifth segment identifier Node-SID(132) in the SR-MPLS segment identifier list.

[0125] In addition, an embodiment of the present invention further provides a network controller, which includes: a memory, a processor, and a computer program stored on the memory and executable on the processor.

[0126] The processor and the memory can be connected by a bus or other means.

[0127] The memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. In addition, the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In some embodiments, the memory may optionally include a memory remotely set relative to the processor, and these remote memories may be connected to the processor through a network. Examples of the above networks include, but are not limited to, the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0128] It should be noted that the network controller in this embodiment can be applied to the network controller in the embodiment shown in Figure 1 or Figure 2 The network controller in this embodiment can form Figure 1 or Figure 2A part of the network topology in the illustrated embodiments, all of which belong to the same inventive concept. Therefore, these embodiments have the same implementation principles and technical effects, which will not be elaborated here.

[0129] The non-transitory software programs and instructions required to implement the information processing method of the above embodiments are stored in the memory. When executed by the processor, the information processing method of the above embodiments is executed. For example, the method steps S110 to S130 described above are executed. Figure 3 in Figure 6 and the method steps S131 to S132 in

[0130] In addition, an embodiment of the present invention further provides a node, which includes: a memory, a processor, and a computer program stored on the memory and executable on the processor.

[0131] The processor and the memory can be connected through a bus or other means.

[0132] As a non-transitory computer-readable storage medium, the memory can be used to store non-transitory software programs and non-transitory computer-executable programs. In addition, the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories can be connected to the processor through a network. Examples of the above networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0133] It should be noted that the node in this embodiment can be applied to the first edge node in the embodiments shown in Figure 1 or Figure 2 The node in this embodiment can form a part of the network topology in the embodiments shown in Figure 1 or Figure 2 All of these embodiments belong to the same inventive concept. Therefore, these embodiments have the same implementation principles and technical effects, which will not be elaborated here.

[0134] The non-transitory software programs and instructions required to implement the information processing method of the above embodiments are stored in the memory. When executed by the processor, the information processing method of the above embodiments is executed. For example, the method steps S210 to S220 described above are executed. Figure 7 in Figure 8 and the method steps S230 to S240 in Figure 9 and the method steps S250 to S270 in Figure 10 and the method steps S281 to S285 in

[0135] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0136] In addition, an embodiment of the present invention further provides a computer-readable storage medium storing computer-executable instructions. When the computer-executable instructions are executed by a processor or a controller, for example, executed by a processor in the above network controller embodiment, the processor can be caused to execute the information processing method in the above embodiment. For example, execute the method steps S110 to S130 described above Figure 3 in Figure 6 and the method steps S131 to S132 in Figure 7 ; or when executed by a processor in the above node embodiment, the processor can be caused to execute the information processing method in the above embodiment. For example, execute the method steps S210 to S220 described above Figure 8 in Figure 9 and the method steps S230 to S240 in Figure 10 and the method steps S250 to S270 in

[0137] Those of ordinary skill in the art will understand that all or some of the steps and systems disclosed in the above methods can be implemented as software, firmware, hardware, and their appropriate combinations. Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or can be implemented as hardware, or can be implemented as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include a computer storage medium (or non-transitory medium) and a communication medium (or transitory medium). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those of ordinary skill in the art that a communication medium typically contains computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and can include any information delivery medium.

[0138] The above is a specific description of the preferred embodiments of the present invention, but the present invention is not limited to the above embodiments. Those skilled in the art can make various equivalent deformations or substitutions without departing from the spirit of the present invention, and these equivalent deformations or substitutions are all included within the scope defined by the claims of the present invention.

Claims

1. An information processing method, applied to a network controller, the information processing method comprising: Obtaining a first Border Gateway Protocol Link State (BGP-LS) message reported by a first edge node in a first network domain, the first BGP-LS message carrying second segment identification information and first segment identification information configured according to the second segment identification information, the first segment identification information corresponding to the first edge node, the second segment identification information corresponding to a second edge node in the first network domain, and there being a mapping relationship between the first segment identification information and the second segment identification information; Determining, according to the first segment identification information and the second segment identification information, that there is a reachable path from the first edge node to the second edge node; Calculating a routing path including the reachable path, and establishing a segment identification list including the first segment identification information during the process of calculating the routing path.

2. The information processing method according to claim 1, wherein The first BGP-LS message further carries Forwarding Equivalence Class (FEC) information, and the FEC information is used to indicate information related to an egress node of the reachable path from the first edge node in the first network domain to the second edge node; The determining, according to the first segment identification information and the second segment identification information, that there is a reachable path from the first edge node to the second edge node includes: Determining, according to the first segment identification information, the second segment identification information, and the FEC information, that there is a reachable path from the first edge node to the second edge node.

3. The information processing method according to claim 1 or 2, characterized in that The calculating a routing path including the reachable path includes: Obtaining a second BGP-LS message reported by a network node in a second network domain, the second BGP-LS message carrying third segment identification information corresponding to the network node; Calculating a routing path including the reachable path according to the first segment identification information, the second segment identification information, and the third segment identification information.

4. The information processing method according to claim 1 or 2, characterized in that Further comprising: Sending the segment identification list including the first segment identification information to the first edge node, so that the first edge node forwards a message according to the segment identification list including the first segment identification information.

5. The information processing method according to claim 3, wherein Further comprising: Sending the segment identification list including the first segment identification information to the network node, so that the network node forwards a message according to the segment identification list including the first segment identification information.

6. An information processing method, applied to a first edge node in a first network domain, the information processing method comprising: Constructing a first BGP-LS message carrying first segment identification information and second segment identification information, the second segment identification information coming from a second edge node in the first network domain and corresponding to the second edge node, the first segment identification information being configured according to the second segment identification information and corresponding to the first edge node, and there being a mapping relationship between the first segment identification information and the second segment identification information; Report the first BGP-LS message to the network controller, so that the network controller determines that there is a reachable path from the first edge node to the second edge node based on the first segment identification information and the second segment identification information in the first BGP-LS message, calculates a routing path including the reachable path, and enables the network controller to establish a segment identification list including the first segment identification information during the process of calculating the routing path.

7. The information processing method according to claim 6, wherein The first BGP-LS message also carries FEC information, where the FEC information is used to indicate relevant information of the egress node of the reachable path from the first edge node to the second edge node in the first network domain. The first BGP-LS message enables the network controller to determine that there is a reachable path from the first edge node to the second edge node based on the first segment identification information, the second segment identification information, and the FEC information in the first BGP-LS message, calculates a routing path including the reachable path, and enables the network controller to establish a segment identification list including the first segment identification information during the process of calculating the routing path.

8. The information processing method according to claim 6 or 7, characterized in that It further includes: Obtain the message forwarded according to the segment identification list, and forward the message according to the first segment identification information in the segment identification list; Or, Obtain the segment identification list including the first segment identification information sent by the network controller, construct a message according to the segment identification list including the first segment identification information, and forward the message according to the first segment identification information in the segment identification list.

9. The information processing method according to claim 8, wherein The forwarding the message according to the first segment identification information in the segment identification list includes: Look up and match in a table according to the first segment identification information in the segment identification list to obtain an identification information table entry; Obtain the second segment identification information from the identification information table entry according to the first segment identification information; Update the first segment identification information in the segment identification list to the second segment identification information; Construct a new message header according to the second segment identification information to form a new message; Forward the new message.

10. A network controller, comprising: A memory, a processor, and a computer program stored on the memory and executable on the processor, wherein when the processor executes the computer program, it implements the information processing method according to any one of claims 1 to 5.

11. A node, comprising: A memory, a processor, and a computer program stored on the memory and executable on the processor, wherein when the processor executes the computer program, it implements the information processing method according to any one of claims 6 to 9.

12. A computer-readable storage medium storing computer-executable instructions for executing the information processing method according to any one of claims 1 to 5 or executing the information processing method according to any one of claims 6 to 9.

Images