A cross-layer path deployment method and apparatus

Abstract

The application discloses a cross-layer path deployment method and device, and relates to the technical field of communication. The method comprises the following steps: determining intersecting gateway nodes according to a constructed service layer topology and a customer layer topology; and constructing service layer links and customer layer links between the gateway nodes by path searching on the service layer topology and the customer layer topology, so as to simultaneously deploy service layer paths and customer layer paths. The application can simultaneously calculate and deploy service layer paths and customer layer paths through cross-layer path calculation in the case that the service layer paths are not configured in advance.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and more specifically to a method and apparatus for deploying cross-layer paths. Background Technology

[0002] In scenarios utilizing SRv6 paths for network connections, such as SRv6 over SR-TP, MTN FG-Channel, or OTN (Note: SRv6 stands for Segment Routing IPv6, based on the IPv6 forwarding plane; SR-TP stands for Segment Routing Transport Profile, based on MPLS; MTN stands for Metro Transport Network; FG-Channel stands for Fine Granularity Channel; OTN stands for Optical Transport Network), there is a need to deploy end-to-end paths across different network link layers, such as... Figure 1 As shown, gray and black nodes, along with light solid line links, constitute the service layer network (e.g., SR-TP, MTN FG-Channel paths can be established), gray and white nodes, along with dark solid line links, constitute the client layer network (e.g., SRv6Policy paths can be established), and gray nodes are gateway nodes (supporting both service layer and client layer paths). To establish an end-to-end client layer path from node A to node J, existing technologies require the following steps:

[0003] Step 1: Static configuration of the management system or acquisition of the client-layer topology from the device (e.g.) Figure 2 As shown, the client-side topology is an IPv6 topology. The management system is statically configured or collects the service-side topology from the device (e.g., ...). Figure 3 As shown, the service layer topology is an IPv4 topology.

[0004] Step 2: Configure service layer paths for each gateway node in the service layer topology diagram (e.g., ...). Figure 4 As shown, nodes C, D, H, and G are nodes where service layer links and client layer links intersect. SR-TP paths are configured for each pair of these four nodes.

[0005] Step 3: Generate virtual links for the service layer paths configured in Step 2 (e.g., ...). Figure 5 As shown, six virtual links are generated and added to the client layer topology as one of the virtual links in the client layer topology.

[0006] Step 4: Based on the merged customer layer topology, perform customer layer path finding and create customer layer paths.

[0007] Based on the above deployment steps, the existing technology has the following problems:

[0008] 1. Pre-deploying service layer paths between gateway nodes may result in the configuration of some unused service layer paths, leading to resource waste.

[0009] 2. Because the service layer path needs to be deployed in advance at the gateway node, it does not meet the requirement of real-time, on-demand, and rapid deployment of the client layer path.

[0010] 3. When deploying the client layer path, it is not supported to select different service layer topology types as needed according to user requirements. Summary of the Invention

[0011] To address the shortcomings of existing technologies, the first aspect of this invention provides a cross-layer path deployment method that can simultaneously calculate and deploy service layer and client layer paths through cross-layer path calculation when the service layer path is not pre-configured.

[0012] To achieve the above objectives, the technical solution adopted by the present invention is as follows:

[0013] A cross-layer path deployment method, the method comprising the following steps:

[0014] Determine the intersecting gateway nodes based on the constructed service layer topology and client layer topology;

[0015] By tracing the service layer topology and the client layer topology, service layer links and client layer links between the gateway nodes are constructed to deploy service layer paths and client layer paths simultaneously.

[0016] In some embodiments, determining the intersecting gateway nodes based on the constructed service layer topology and client layer topology includes:

[0017] Construct service layer topology and client layer topology, including nodes and links;

[0018] The set of intersecting gateway nodes is determined based on the intersection of the service layer topology and the client layer topology.

[0019] In some embodiments, the step of constructing service layer links and client layer links between the gateway nodes by routing through the service layer topology and client layer topology, so as to simultaneously deploy service layer paths and client layer paths, includes:

[0020] Based on the node set of the customer layer topology, intersecting gateway nodes, and link latency attributes, perform customer layer path finding between the source and destination nodes of the customer layer path to be deployed, and return the service layer link list and the customer layer link list.

[0021] Based on the service layer link list, the source node of the first link with the overlay attribute of overlay_nni and the destination node of the last link with the overlay attribute of overlay_nni are used as the source node and destination node of the service layer path to create a service layer path, and the service layer path is constructed into a virtual link. When the port type at both ends of the link is Network Node Interface (NNI), the overlay attribute of the link is overlay_nni.

[0022] Create customer-layer paths based on the customer-layer link list and the constructed virtual links.

[0023] In some embodiments, the step of performing client-layer path routing between the source and destination nodes of the client-layer path to be deployed, based on the node set of the client-layer topology, intersecting gateway nodes, and link latency attributes, and returning a service-layer link list and a client-layer link list, includes:

[0024] Select the node with the smallest latency attribute value from the set of nodes included in the client layer topology;

[0025] Based on whether the selected node is a gateway node, a relaxation operation is performed on the latency attribute value of each node with an adjacency relationship to the selected node until the set of nodes included in the client layer topology is selected or the node with the smallest latency attribute value is the destination node of the client layer path.

[0026] The process begins by obtaining the list of links and link types of the preceding nodes from the destination node, iterating until the preceding node is empty. The link types include service layer links and client layer links.

[0027] In some embodiments, the relaxation operation of latency attribute values ​​for each adjacent node of the selected node based on whether the selected node is a gateway node includes:

[0028] If the selected node is not a gateway node, then the latency attribute values ​​of the adjacent nodes of the selected node are relaxed.

[0029] If the selected node is a gateway node, then the latency attribute values ​​of the adjacent nodes of the selected node are relaxed, and the relaxation operation is also performed on other gateway nodes in the gateway node set other than the selected node.

[0030] In some embodiments, the relaxation operation on the delay attribute values ​​of the adjacent nodes of the selected node includes:

[0031] If u.totalcost + link(u, v).cost < v.totalcost, then update v.totalcost = u.totalcost + link(u, v).cost, where u.totalcost is the latency attribute value from the source node to the selected node u, link(u, v).cost is the latency attribute value of the link between u and its adjacent node v, and v.totalcost is the latency attribute value from the source node to v;

[0032] And set the link list from v to the previous node to the link between u and v, and set the link type from v to the previous node to the client layer link.

[0033] In some embodiments, the relaxation operation on other gateway nodes in the gateway node set except the selected node includes:

[0034] For each other gateway node v in the gateway node set that is not u ， Call the shortest path algorithm to calculate the shortest path between u and v ， Return the link passed between u and v ， And the latency attribute value link(u, v ， ).cost between u and v ， ).cost;

[0035] If there is a service layer path between u and v ， And u.totalcost + link(u, v ， ).cost < v ， .totalcost, then update v ， .totalcost = u.totalcost + link(u, v ， ).cost, where v ， .totalcost is the latency attribute value from the source node to v ， ;

[0036] And set the link list from v ， to the previous node to the link between u and v ， And set the link type from v ， to the previous node to the service layer link.

[0037] In some embodiments, construct the service layer topology and the client layer topology on the management and control system according to the static configuration node and link information.

[0038] In some embodiments, deploy a distributed protocol on the device for topology discovery, and use the management and control system to collect the discovered topology from the device to construct the service layer topology and the client layer topology.

[0039] A second aspect of the present invention provides a cross-layer path deployment apparatus, which can simultaneously calculate and deploy service layer and client layer paths through cross-layer path calculation when the service layer path is not pre-configured.

[0040] To achieve the above objectives, the technical solution adopted by the present invention is as follows:

[0041] A cross-layer path deployment device, comprising:

[0042] The construction module determines the intersecting gateway nodes based on the constructed service layer topology and client layer topology;

[0043] The deployment module constructs service layer links and customer layer links between the gateway nodes by tracing the service layer topology and customer layer topology, so as to deploy service layer paths and customer layer paths simultaneously.

[0044] Compared with the prior art, the advantages of the present invention are as follows:

[0045] The cross-layer path deployment method in this invention determines intersecting gateway nodes based on the constructed service layer topology and client layer topology. By routing through the service layer and client layer topologies, it constructs service layer links and client layer links between the gateway nodes, thus simultaneously deploying service layer paths and client layer paths. This allows for the simultaneous calculation and deployment of service layer and client layer paths even when service layer paths are not pre-configured. It avoids the waste of service layer path resources caused by pre-deploying service layer paths pairwise in gateway nodes due to uncertain client layer requirements. It also avoids the latency and other issues that pre-deployed service layer paths may not meet the needs of client layer paths. Attached Figure Description

[0046] Figure 1 This is a schematic diagram of a network in which the client layer is carried on the service layer in existing technology;

[0047] Figure 2 This is a schematic diagram of the static configuration of the control system or the acquisition of the customer layer topology from the device in the existing technology;

[0048] Figure 3 This is a schematic diagram of the static configuration of the control system or the service layer topology collected from the device in the existing technology;

[0049] Figure 4 This is a schematic diagram illustrating the configuration of service layer paths between gateway network elements in the service layer in existing technologies.

[0050] Figure 5 This is a schematic diagram of generating a virtual link from a configured service layer path in existing technology, serving as a virtual link in the client layer topology;

[0051] Figure 6 This is a schematic diagram of the service layer path terminating on a network element in an embodiment of the present invention;

[0052] Figure 7 This is a schematic diagram of the service layer path terminating on the port in an embodiment of the present invention;

[0053] Figure 8 This is a flowchart of the cross-layer path deployment method in an embodiment of the present invention;

[0054] Figure 9 This is a schematic diagram of the path link formed according to the attributes of each node after the path calculation is completed in an embodiment of the present invention;

[0055] Figure 10 This is a schematic diagram of the IPv6 link topology, IPv4 link, and MTN Channel link topology in an embodiment of the present invention;

[0056] Figure 11 This is a schematic diagram illustrating the creation of service layer paths and customer layer paths based on the service layer and customer layer links returned by path calculation in an embodiment of the present invention;

[0057] Figure 12 This is a topology diagram of SRv6 Over OTN in an embodiment of the present invention;

[0058] Figure 13 This is a schematic diagram of the Pv6 client layer topology, OTN service layer topology, SRv6 Policy path, and OTN path in an embodiment of the present invention. Detailed Implementation

[0059] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0060] This invention discloses a cross-layer path deployment method, which includes the following steps:

[0061] The intersecting gateway nodes are determined based on the constructed service layer topology and client layer topology.

[0062] By tracing the service layer topology and the client layer topology, service layer links and client layer links between the gateway nodes are constructed to deploy service layer paths and client layer paths simultaneously.

[0063] First, it's worth noting that, to determine the service layer path, this embodiment of the invention defines two overlay types based on the location where the service layer path terminates: overlay_uni and overlay_nni. Each link has an overlay attribute. If the service layer path terminates at a port, the overlay attribute of the link to that port is overlay_uni. If the service layer path terminates at a network element, the overlay attribute of the links traversed by that service layer path is overlay_nni. See also... Figure 6 As shown, the endpoint of the service layer path is on the network element, and the overlay attribute of (link2,link3,link4,link5) is overlay_nni. Figure 7 The endpoint of the middle service layer path is on the port. The overlay attribute of (link2,link5) is overlay_uni, and the overlay attribute of (link3,link4) is overlay_nni.

[0064] See Figure 8 As shown, the specific process of the above steps is described below:

[0065] S1. Construct the topology for service layer path calculation, and label the service layer topology as Gs;

[0066] It is worth noting that the service layer topology consists of nodes and links. Links have latency attributes (represented by cost values). For example, the cost value of the link from node u to v can be represented by link(u,v).cost.

[0067] The links in the service layer topology have the aforementioned overlay attribute. This attribute value can be manually specified or automatically generated based on the port types at both ends of the link. The automatic generation rule is as follows: if both ends of the link have NNI (Network to Network Interface) ports, then the overlay attribute of the link is overlay_nni; if one end of the link has an NNI port and the other end has a UNI (User Network Interface) port, then the overlay attribute of the link is overlay_uni. For example... Figure 5 Since the port types at both ends of (link2, link3, link4, link5) are both NNI, the overlay attribute of (link2, link3, link4, link5) is overlay_nni. For example... Figure 6In the middle, the port type of link2 connected to node C is UNI, and the port type of link5 connected to node B is NNI. The port type of link5 connected to node E is UNI, and the port type of link5 connected to node F is NNI. The port types of both ends of (link3, link4) are NNI. Therefore, the overlay attribute of (link2, link5) is overlay_uni, and the overlay attribute of (link3, link4) is overlay_nni.

[0068] The service layer topology can be constructed in several ways. It can be statically configured by the user on the management system, with node and link information configured on the device. Alternatively, a distributed protocol can be deployed on the device for topology discovery, from which the management system collects the discovered topology.

[0069] In addition, based on the device's support for service layer paths, different types of service layer topologies are constructed and labeled as Gs1, Gs2, ... Gsn.

[0070] S2. Construct the topology for client-layer path calculation and label the topology as Gc;

[0071] The client-layer topology consists of nodes and links, and the links have latency attributes (represented by cost values).

[0072] The client-layer topology can be constructed in several ways. It can be statically configured by the user on the management system, with node and link information configured on the device. Alternatively, a distributed protocol can be deployed on the device for topology discovery, from which the management system collects the discovered topology.

[0073] S3. Calculate the gateway node where the service layer link and the client layer link intersect;

[0074] S31. Obtain the set of nodes included in the client layer topology Gc, labeled as A.

[0075] S32. For each constructed service layer topology Gsk (k = 1, 2, ..., n), obtain its set of nodes, labeled as Bk (k = 1, 2, ..., n).

[0076] S33. Taking the intersection of set A with set Bk respectively, we get GatewaySetk (k = 1, 2, ..., n), which is the set of gateway nodes where the service layer links and the client layer links intersect.

[0077] S4. End-to-end deployment of the client-side path;

[0078] S41. Select the source and destination nodes of the client layer path to be deployed, specify the required bandwidth, specify the service layer type (e.g., hard isolation, soft isolation), etc. Each service layer type can correspond one-to-one with the service layer topology constructed in step S1.

[0079] S42. Select the corresponding service layer topology from the multiple service layer topologies constructed in step S1 according to the service layer type, and mark it as Gsk.

[0080] S43. Based on the service layer topology Gsk selected in S4.2 and the client layer topology Gc constructed in S2, perform client layer pathfinding at the source node and the destination node, and return a list. The objects in the list contain two members: link type (distinguishing between service layer and client layer links) and link list (representing an ordered set of links).

[0081] Specifically, in step S43, the process of simultaneously calculating the client-layer and service-layer paths based on the client-layer topology Gc, the service-layer topology Gsk, and the source and destination nodes is as follows (in the following process, if a node in the client-layer topology is a gateway node, in addition to considering nodes with which it has a client-layer link relationship as neighbors, other gateway nodes are also considered as virtual neighbors. The virtual links between gateway nodes and other gateway nodes are virtually generated after the service-layer path is obtained by calling the service-layer topology routing calculation):

[0082] S431. Based on the value of k in the service layer topology Gsk, find the network element node set GatewaySetk calculated in step S3.

[0083] Each node in S432.Gc defines the following properties:

[0084] totalcost (represents the cost value from the source node to this node);

[0085] prenode (represents the node preceding the source node);

[0086] toprelinklist (represents a list of links to the preceding node);

[0087] linktype (represents the link type to the preceding node, with values ​​for client layer and service layer);

[0088] visited (a marker indicating whether a number has been visited).

[0089] S433. Initialize the total cost of each node in the Gc to infinity, the prenode to empty, and the toprelinklist to empty. Initialize the total cost of the source nodes in the Gc to 0. Initialize the visited value of each node in the Gc to false.

[0090] S434. Select a node with the minimum totalcost value from the set of nodes in Gc whose visited value is false, and mark it as u.

[0091] If u is the destination node, go to S436

[0092] For each adjacent node v of u: perform a relaxation operation on the totalcost value of v:

[0093] (if u.totalcost + link(u, v).cost < v.totalcost: then v.totalcost = u.totalcost + link(u, v).cost), set the toprelinklist of v to the link between (u, v), and set the linktype of v to the client layer.

[0094] If u is a gateway node, call the shortest path algorithm for each other gateway node v' in GatewaySetk (the input topology is the service layer topology Gsk), calculate the shortest path between u and v', and return the passed linklist(u - v') and the cost(u - v') value of (u, v') (equal to the sum of the cost values of each link included in linklist(u - v')). If there is a service layer path between u and v', perform a relaxation operation on the node v': update the totalcost value of the node v', set the toprelinklist of v' to linklist(u - v'), and set the linktype of v' to the service layer.

[0095] Mark the visited of node u as true.

[0096] S435. Repeat S434 until the visited attribute of each node in Gc is true.

[0097] S436. Starting from the destination node, obtain the toprelinklist and linktype of the previous node, and add this pair to the head of the list of path, and iterate until the previous node is empty. Return the path, and the process ends.

[0098] Take Figure 9 as an example to illustrate: Starting from the destination node J, iterate to obtain its previous node until the previous node is empty. The obtained client layer path is [A, B, C, G, J], and the link list is [([link1], C), ([link2], C), ([link3, link4], S), ([link5], C)]. Where S represents the service layer link and C represents the client layer link.

[0099] S44. Based on the service layer link list returned in S43, create a service layer path: where the source node of the service layer path is the source node of the first link in the service layer links whose overlay attribute is overlay_nni, and the destination node of the service layer path is the destination node of the last link in the service layer links whose overlay attribute is overlay_nni. For Figure 5 The service layer link list calculated by S43 pathfinding is (link2, link3, link4, link5). The overlay attribute of these links is overlay_nni. Therefore, the source node of the service layer path is the source node B of link2, and the destination node of the service layer path is the destination node F of link5. For Figure 6 The service layer link list calculated by pathfinding is (link2, link3, link4, link5), where the overlay attribute of link2 and link5 is overlay_uni, and the overlay attribute of link3 and link5 is overlay_nni. Therefore, the source node of the service layer path is the source node C of link3, and the destination node of the service layer path is the destination node E of link4. Simultaneously, the entire service layer link is abstracted into a virtual link, serving as a hop in the client layer path.

[0100] S45. Based on the client-layer link returned in S43 and the virtual link constructed in S44, create a client-layer path.

[0101] The following two specific examples will further illustrate the steps described above:

[0102] One example illustrates this using an SRv6 Policy tunnel over an SR-TP tunnel / MTN FG-Channel tunnel:

[0103] S1. Construct the service layer topology (e.g.) Figure 10 As shown in the figure, in this embodiment, the service layer network element supports IPv4 links and MTNChannel links.

[0104] IPv4 links between network elements can be collected from the device via the BGP-LS protocol or configured statically by hand.

[0105] Based on the generated IPv4 links and nodes, the service layer topology Gs1 can be constructed.

[0106] The MTN Channel links between network elements can be manually and statically configured. Based on the generated MTN Channel links and nodes, the service layer topology Gs2 can be constructed. It is understood that Gs1 and Gs2 may contain the same or different nodes.

[0107] Since both the SR-TP tunnel and the MTN FG-Channel tunnel terminate at network elements, the overlay attribute of the constructed IPv4 link and MTN Channel link is overlay_nni.

[0108] S2. Construct the client-layer network topology (e.g.) Figure 10 As shown in the figure, the client layer link in this example is an IPv6 link.

[0109] IPv6 links between network elements can be generated from equipment data or configured statically by hand.

[0110] Based on the generated IPv6 links and nodes, the client-layer topology Gc can be constructed.

[0111] S3. Calculate the network elements where the service layer link and the client layer link intersect. The specific steps are as follows:

[0112] GatewaySet1 is obtained by taking the intersection of the network element sets of the two topologies Gs1 and Gc.

[0113] GatewaySet2 is obtained by taking the intersection of the network element sets of the two topologies Gs2 and Gc.

[0114] S4. Deploy end-to-end client layer path. In this embodiment, two SRv6 Policy tunnels are deployed, one of which (marked as A) is carried on SR-TP and the other (marked as B) is carried on MTN FG-Channel.

[0115] S41. Select the source and destination nodes for the client layer path to be deployed, and specify the required bandwidth. For tunnel A, specify the service layer type as soft isolation, and for tunnel B, specify the service layer type as hard isolation.

[0116] S42. Select one of the multiple service layer topologies constructed in step S1 based on the service layer type, and label it Gsk. In this example, tunnel A is specified to carry a soft isolation service layer type, so the selected service layer topology is Gs1. In this example, tunnel B is specified to carry a hard isolation service layer type, so the selected service layer topology is Gs2.

[0117] S43. Based on the service layer topology Gsk selected in S42 and the client layer topology Gc constructed in S2, perform pathfinding on the client layer path between the source node and the destination node (see the description of the pathfinding algorithm above), and return a list. The objects in the list contain two members: link type (distinguishing between service layer and client layer links) and link list (representing an ordered set of links).

[0118] S44. Based on the service layer link list returned in S43, create an SR-TP service layer path for SRv6 Policy tunnel A and an MTN FG-Channel service layer path for SRv6 Policy tunnel B. Since the overlay attribute of all returned service layer links is overlay_nni, the source node of the service layer path is the source node of the first link in the service layer link list, and the destination node of the service layer path is the destination node of the last link in the service layer link list (e.g., ...). Figure 11 As shown, the source node of the SR-TP service layer path is C, the destination node is G, and the list of links is [link3, link4]. The entire service layer path is also abstracted into a virtual link (virtuallink1), which serves as a hop in the SRv6 Policy path, and a SID is assigned to this virtual link.

[0119] S45. Based on the client-layer links returned in S43 and the virtual link list constructed in S44, create an SRv6 Policy tunnel (e.g., ...). Figure 10 As shown, the SRv6 Policy tunnel A path is [link1,link2,virtuallink1,link5]).

[0120] Another embodiment takes the SRv6 Policy tunnel over OTN scenario as an example (e.g.) Figure 12 The diagram shown is a topology diagram of this embodiment.

[0121] S1. Construct the service layer topology. In this example, the service layer network elements only support OTN links.

[0122] OTN links between service layer network elements can be manually statically configured or automatically discovered. In this embodiment, the service layer topology is: Gs1 = (Es, Vs), as follows... Figure 13 As shown, where

[0123] Es = {link2,link3,link4,link5,link10,link11,link12,link13,link14}, Vs = {B,C,D,E,F,I,J,K,L}. The overlay attribute of link2,link5,link10, andlink14 is overlay_uni, and the overlay attribute of other links is overlay_nni.

[0124] S2. Construct the client-layer network topology. In this example, the client-layer links are IPv6 links.

[0125] IPv6 links between network elements can be generated from equipment data or configured statically by hand.

[0126] Based on the generated IPv6 links and nodes, the client-layer topology Gc can be constructed. In this embodiment, the service-layer topology is: Gc = (Ec, Vc), as shown below. Figure 10 As shown, where

[0127] Ec={link1, link6, link7, link8, link9, link15, link16}, Vc={A, B, F, G, H, I, L}.

[0128] S3. Calculate the network elements where the service layer link and the client layer link intersect. The specific steps are as follows:

[0129] GatewaySet1 is obtained by taking the intersection of the network element sets of the two topologies Gs1 and Gc. In this embodiment, GatewaySet1 = {B, F, I, L}.

[0130] S4. Deploy end-to-end client layer path. In this embodiment, one SRv6 Policy tunnel is deployed.

[0131] S41. Select the source and destination nodes for the client-layer path to be deployed, specify the required bandwidth, and specify the service layer type as hard isolation. In this embodiment, the source node of the SRv6 Policy is A, and the destination node is G.

[0132] S42. In this example, the service layer type specified for the tunnel is hard isolation, so the selected service layer topology is Gs1.

[0133] S43. Based on the service layer topology Gs1 selected in S42 and the client layer topology Gc constructed in S2, perform pathfinding on the client layer path between the source node and the destination node (see the description of the pathfinding algorithm above), and return a list. The objects in the list contain two members: link type (distinguishing between service layer and client layer links) and link list (representing an ordered set of links).

[0134] After using the above pathfinding algorithm, the list data returned in this embodiment is: [([link1],C),([link2,link11,link12,link14],S),([link16],C)].

[0135] S44. Based on the service layer link list returned in S43, create an OTN service layer path. Since the overlay attribute of link2 and link14 is overlay_uni, the source node of the OTN service layer path to be created is C, the destination node is K, and the path is [link11, link12]. At the same time, virtualize the service layer link list [link2, link11, link12, link14] into a virtual link (virtuallink1) as a hop in the SRv6 Policy path, and assign a SID to this virtual link.

[0136] S45. Based on the client-layer link returned in S43 and the virtual link constructed in S44, create an SRv6 Policy tunnel. In this embodiment, the SRv6 Policy tunnel path is: [link1, virtuallink1, link16].

[0137] In summary, the cross-layer path deployment method of this invention determines intersecting gateway nodes based on the constructed service layer topology and client layer topology; by pathfinding the service layer topology and client layer topology, it constructs service layer links and client layer links between the gateway nodes to simultaneously deploy service layer paths and client layer paths. This allows for the simultaneous calculation and deployment of service layer and client layer paths even when service layer paths are not pre-configured. It avoids the waste of service layer path resources caused by pre-deploying service layer paths pairwise in gateway nodes due to uncertain client layer requirements. It also avoids the problem of latency and other issues with pre-deployed service layer paths failing to meet the requirements of client layer paths.

[0138] Meanwhile, embodiments of the present invention also provide a cross-layer path deployment device, which includes a construction module and a deployment module.

[0139] Among them, the construction module determines the intersecting gateway nodes based on the constructed service layer topology and client layer topology;

[0140] The deployment module constructs service layer links and customer layer links between the gateway nodes by tracing the service layer topology and customer layer topology, so as to deploy service layer paths and customer layer paths simultaneously.

[0141] In some embodiments, the construction module determines intersecting gateway nodes based on the constructed service layer topology and client layer topology, including:

[0142] Construct service layer topology and client layer topology, including nodes and links;

[0143] The set of intersecting gateway nodes is determined based on the intersection of the service layer topology and the client layer topology.

[0144] In some embodiments, the deployment module constructs service layer links and client layer links between the gateway nodes by routing through the service layer topology and the client layer topology, so as to simultaneously deploy service layer paths and client layer paths, including:

[0145] Based on the node set of the customer layer topology, intersecting gateway nodes, and link latency attributes, perform customer layer path finding between the source and destination nodes of the customer layer path to be deployed, and return the service layer link list and the customer layer link list.

[0146] Based on the service layer link list, the source node of the first link with the overlay attribute of overlay_nni and the destination node of the last link with the overlay attribute of overlay_nni are used as the source node and destination node of the service layer path to create a service layer path, and the service layer path is constructed into a virtual link. When the port type at both ends of the link is Network Node Interface (NNI), the overlay attribute of the link is overlay_nni.

[0147] Create customer-layer paths based on the customer-layer link list and the constructed virtual links.

[0148] In some embodiments, the deployment module performs client-layer path routing between the source and destination nodes of the client-layer path to be deployed based on the node set of the client-layer topology, intersecting gateway nodes, and link latency attributes, and returns a service-layer link list and a client-layer link list, including:

[0149] Select the node with the smallest latency attribute value from the set of nodes included in the client layer topology;

[0150] Based on whether the selected node is a gateway node, a relaxation operation is performed on the latency attribute value of each node with an adjacency relationship to the selected node until the set of nodes included in the client layer topology is selected or the node with the smallest latency attribute value is the destination node of the client layer path.

[0151] The process begins by obtaining the list of links and link types of the preceding nodes from the destination node, iterating until the preceding node is empty. The link types include service layer links and client layer links.

[0152] In some embodiments, the deployment module performs a latency attribute relaxation operation on each adjacent node of the selected node based on whether the selected node is a gateway node, including:

[0153] If the selected node is not a gateway node, then the latency attribute values ​​of the adjacent nodes of the selected node are relaxed.

[0154] If the selected node is a gateway node, perform a relaxation operation on the delay attribute values of the adjacent nodes of the selected node, and perform a relaxation operation on the other gateway nodes in the gateway node set except the selected node.

[0155] In some embodiments, the deployment module performs a relaxation operation on the delay attribute values of the adjacent nodes of the selected node, including:

[0156] If u.totalcost + link(u, v).cost < v.totalcost, update v.totalcost = u.totalcost + link(u, v).cost, where u.totalcost is the delay attribute value from the source node to the selected node u, link(u, v).cost is the delay attribute value of the link between u and its adjacent node v, and v.totalcost is the delay attribute value from the source node to v;

[0157] And set the link list from v to the previous node to the link between u and v, and set the link type from v to the previous node to the customer layer link.

[0158] In some embodiments, the deployment module performs a relaxation operation on the other gateway nodes in the gateway node set except the selected node, including:

[0159] For each other gateway node v in the gateway node set that is not u ， Call the shortest path algorithm to calculate the shortest path between u and v ， Return the link passed between u and v ， And the delay attribute value link(u, v ， ).cost between u and v; ， ).cost;

[0160] If there is a service layer path between u and v ， And u.totalcost + link(u, v ， ).cost < v ， .totalcost, then update v ， .totalcost = u.totalcost + link(u, v ， ).cost, where v ， .totalcost is the delay attribute value from the source node to v ， ;

[0161] And set the link list from v ， to the previous node to the link between u and v ， and set the link type from v ， to the previous node to the service layer link.

[0162] In some embodiments, the construction module constructs service layer topology and client layer topology on the management and control system based on statically configured node and link information.

[0163] In some embodiments, the construction module deploys a distributed protocol on the device for topology discovery, and uses a management and control system to collect the discovered topology from the device to construct service layer topology and client layer topology.

[0164] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A cross-layer path deployment method, characterized in that, The method includes the following steps: Determine the intersecting gateway nodes based on the constructed service layer topology and client layer topology; By tracing the service layer topology and the client layer topology, service layer links and client layer links between the gateway nodes are constructed to deploy service layer paths and client layer paths simultaneously.

2. The cross-layer path deployment method according to claim 1, characterized in that, The step of determining the intersecting gateway nodes based on the constructed service layer topology and client layer topology includes: Construct service layer topology and client layer topology, including nodes and links; The set of intersecting gateway nodes is determined based on the intersection of the service layer topology and the client layer topology.

3. The cross-layer path deployment method according to claim 2, characterized in that, The step of constructing service layer links and client layer links between gateway nodes by routing through the service layer topology and client layer topology, so as to simultaneously deploy service layer paths and client layer paths, includes: Based on the node set of the customer layer topology, intersecting gateway nodes, and link latency attributes, perform customer layer path finding between the source and destination nodes of the customer layer path to be deployed, and return the service layer link list and the customer layer link list. Based on the service layer link list, the source node of the first link with the overlay attribute of overlay_nni and the destination node of the last link with the overlay attribute of overlay_nni are used as the source node and destination node of the service layer path to create a service layer path, and the service layer path is constructed into a virtual link. When the port type at both ends of the link is Network Node Interface (NNI), the overlay attribute of the link is overlay_nni. Create customer-layer paths based on the customer-layer link list and the constructed virtual links.

4. The cross-layer path deployment method according to claim 3, characterized in that, The process involves performing client-layer pathfinding between the source and destination nodes of the client-layer path to be deployed, based on the node set of the client-layer topology, intersecting gateway nodes, and link latency attributes, and returning a service-layer link list and a client-layer link list, including: Select the node with the smallest latency attribute value from the set of nodes included in the client layer topology; Based on whether the selected node is a gateway node, a relaxation operation is performed on the latency attribute value of each node with an adjacency relationship to the selected node until the set of nodes included in the client layer topology is selected or the node with the smallest latency attribute value is the destination node of the client layer path. The process begins by obtaining the list of links and link types of the preceding nodes from the destination node, iterating until the preceding node is empty. The link types include service layer links and client layer links.

5. The cross-layer path deployment method according to claim 4, characterized in that, The relaxation operation on the latency attribute value of each adjacent node of the selected node, based on whether the selected node is a gateway node, includes: If the selected node is not a gateway node, then the latency attribute values ​​of the adjacent nodes of the selected node are relaxed. If the selected node is a gateway node, then the latency attribute values ​​of the adjacent nodes of the selected node are relaxed, and the relaxation operation is also performed on other gateway nodes in the gateway node set other than the selected node.

6. The cross-layer path deployment method according to claim 5, characterized in that, The relaxation operation on the delay attribute values ​​of the adjacent nodes of the selected node includes: If u.totalcost + link(u, v).cost < v.totalcost, then update v.totalcost = u.totalcost + link(u, v).cost, where u.totalcost is the delay attribute value from the source node to the selected node u, link(u, v).cost is the delay attribute value of the link between u and its adjacent node v, and v.totalcost is the delay attribute value from the source node to v; And set the link list from v to its previous node to the link between u and v, and set the link type from v to its previous node to the client layer link.

7. A cross-layer path deployment method according to claim 5, characterized in that, The relaxation operation on other gateway nodes in the gateway node set except the selected node includes: For each non-u other gateway node v in the gateway node set ， Call the shortest path algorithm to calculate u and v ， Find the shortest path between u and v, and return the paths traversed. ， The links between them, and u and v ， The time delay attribute value between link(u,v) ， cost; If there is a service layer path between u and v ， , and u.totalcost + link(u, v ， ).cost < v ， .totalcost, then update v ， .totalcost = u.totalcost + link(u, v ， ).cost, where v ， .totalcost is the value of the delay attribute from the source node to v ， . And v ， The link list to the preceding node is set to u and v. ， The link between them will v ， Set the link type to the front-end node to a service layer link.

8. A cross-layer path deployment method according to claim 2, characterized in that: Construct the service layer topology and the client layer topology on the management and control system according to the static configuration node and link information.

9. A cross-layer path deployment method according to claim 2, characterized in that: Deploy a distributed protocol on the device for topology discovery, and use the management and control system to collect the discovered topology from the device to construct the service layer topology and the client layer topology.

10. A cross-layer path deployment device, characterized in that, It includes: A construction module that determines the intersecting gateway nodes according to the constructed service layer topology and client layer topology; A deployment module that constructs the service layer link and the client layer link between the gateway nodes by finding paths in the service layer topology and the client layer topology to simultaneously deploy the service layer path and the client layer path.

Images