Routing method and device for multi-layer multi-domain optical transport network

Abstract

The application discloses a routing method and device of a multi-layer multi-domain optical transport network. The method comprises the following steps: receiving a service request initiated by a starting Ethernet NEP in a source control domain network; determining a plurality of intermediate NEPs between the source control domain network and a destination control domain network in the service request; constructing a topology matrix according to the plurality of intermediate NEPs, and determining a target transmission link with the lowest link cost and meeting a preset constraint condition according to the topology matrix; and routing the service request from the starting Ethernet NEP to a terminal Ethernet NEP in the destination control domain network according to the target transmission link. The application solves the technical problem of poor accuracy and low efficiency of a determined routing link when a fixed routing strategy or a random routing strategy is used to route cross-domain services.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of network communication, in particular to a routing method and device of a multi-layer multi-domain optical transport network. BACKGROUND

[0002] With the increase of traffic and the expansion of the region, cross-domain service has become a regular service requirement. When establishing a multi-domain end-to-end service, the segmentation of the domain is generally based on different operators, different geographical locations of the same operator network, or different switching technologies. Therefore, the transmission network of multiple domains often uses multi-vendor equipment, and each domain adopts a privacy protection strategy and is relatively closed. In order to ensure the reachability of the end-to-end service, the problem of multi-domain routing needs to be considered.

[0003] The traditional processing method is to fix the inter-domain routing forwarding strategy between two domains or randomly select the inter-domain routing method. However, due to the limited inter-domain resources, this processing method is easy to cause the rise of link blocking rate. Therefore, at present, there is an urgent need for a routing strategy technology that can quickly provide an end-to-end transmission link and ensure the success rate of efficient establishment of the service in a multi-layer multi-domain environment.

[0004] In view of the above problems, no effective solution has been proposed so far. SUMMARY

[0005] The embodiments of the present application provide a routing method and device of a multi-layer multi-domain optical transport network, so as to at least solve the technical problems of poor accuracy and low efficiency of the determined routing link when the cross-domain service is routed by using a fixed routing strategy or a random routing strategy.

[0006] According to an aspect of the embodiments of the present application, a routing method of a multi-layer multi-domain optical transport network is provided, which comprises: receiving a service request initiated by a starting Ethernet NEP in a source control domain network, wherein the service request at least carries first node information of a terminating Ethernet NEP in a destination control domain network; determining a plurality of intermediate NEPs between the source control domain network and the destination control domain network in the service request, wherein the plurality of intermediate NEPs comprise: a non-starting Ethernet NEP and a first ODU_NEP in the source control domain network, a second ODU_NEP in an intermediate control domain network between the source control domain network and the destination control domain network, and a non-terminating Ethernet NEP and a third ODU_NEP in the destination control domain network; constructing a topology matrix at least according to the plurality of intermediate NEPs, and determining a target transmission link that meets a preset constraint condition and has the lowest link cost according to the topology matrix; and routing the service request from the starting Ethernet NEP to the terminating Ethernet NEP in the destination control domain network according to the target transmission link.

[0007] Optionally, the topology matrix is constructed according to at least the plurality of intermediate NEPs, and the target transmission link satisfying the preset constraint condition and having the lowest link cost is determined according to the topology matrix, including: taking the start Ethernet NEP, the plurality of intermediate NEPs and the end Ethernet NEP as rows and columns, and taking the link cost of the sub-link between the NEPs corresponding to each row and each column as a matrix element to construct a first topology matrix; performing analysis on the first topology matrix by using the Dijkstra algorithm to obtain a first transmission link satisfying the constraint condition and having the lowest link cost, and taking the first transmission link as the target transmission link.

[0008] Optionally, the topology matrix is constructed according to at least the plurality of intermediate NEPs, and the target transmission link satisfying the preset constraint condition and having the lowest link cost is determined according to the topology matrix, including: taking a non-start Ethernet NEP or a first ODU_NEP in the source control domain network as a start NEP in the source control domain network, and taking a non-end Ethernet NEP or a third ODU_NEP in the destination control domain network as an end NEP in the destination control domain network, wherein the link cost of the sub-link between the start NEP and the start Ethernet NEP and the link cost of the sub-link between the end NEP and the end Ethernet NEP are both less than a preset threshold value; taking the start NEP, the end NEP, the intermediate NEPs between the start NEP and the end NEP as rows and columns, and taking the link cost of the sub-link between the NEPs corresponding to each row and each column as a matrix element to construct a second topology matrix; performing analysis on the second topology matrix by using the Dijkstra algorithm to obtain a second transmission link satisfying the constraint condition and having the lowest link cost; determining a third transmission link between the start Ethernet NEP and the start NEP and a fourth transmission link between the end NEP and the end Ethernet NEP, and taking the third transmission link, the second transmission link and the fourth transmission link to form the target transmission link.

[0009] Optionally, the link cost is a weighted average sum of values of the sub-link in preset link evaluation dimensions, and the link evaluation dimensions include at least one of the following: link distance, link resource usage, hop count and link state.

[0010] Optionally, the constraint condition includes at least one of the following: a sum of link distances of each sub-link is less than a preset first threshold value, a sum of link resource usages of each sub-link is less than a preset second threshold value, a sum of hop counts of each sub-link is less than a preset third threshold value, and link states of each sub-link are all normal states.

[0011] Optionally, the routing the service request from the start Ethernet NEP to the end Ethernet NEP in the target transmission link comprises: determining the control domain network to which each NEP on the target transmission link belongs, obtaining the transmission sub-link in each control domain network, wherein the type of the control domain network comprises: a source control domain network, a target control domain network, and an intermediate control domain network; adjusting the service request according to the type of the control domain network, and routing the adjusted service request to the end Ethernet NEP in the target control domain network according to the transmission sub-link in each control domain network.

[0012] Optionally, the adjusting the to-be-routed service request according to the type of the control domain network comprises: for the transmission sub-link in the source control domain network, adding second node information of the start Ethernet NEP and third node information of the non-start Ethernet NEP in the service request in the process of routing the service request from the start Ethernet NEP to the non-start Ethernet NEP; for the transmission sub-link in the source control domain network, adding the third node information of the non-start Ethernet NEP, fourth node information of the current first ODU_NEP, and fifth node information of the next first ODU_NEP in the service request in the process of routing the service request from the current first ODU_NEP to the next first ODU_NEP in the source control domain network; for the transmission sub-link in the intermediate control domain network, adding sixth node information of the current second ODU_NEP and seventh node information of the next second ODU_NEP in the service request in the process of routing the service request from the current second ODU_NEP to the next second ODU_NEP in the intermediate control domain network; for the transmission sub-link in the target control domain network, adding eighth node information of the current third ODU_NEP and ninth node information of the next third ODU_NEP in the service request in the process of routing the service request from the current third ODU_NEP to the next third ODU_NEP in the target control domain network; and for the transmission sub-link from the non-end Ethernet NEP to the end Ethernet NEP, adding first node information of the end Ethernet NEP and tenth node information of the non-end Ethernet NEP in the service request.

[0013] According to a further aspect of the embodiments of the present application, a routing device of a multi-layer multi-domain optical transport network is also provided, comprising: a receiving module configured to receive a service request initiated by a starting Ethernet NEP in a source control domain network, wherein the service request carries at least first node information of a terminating Ethernet NEP in a destination control domain network; a first determining module configured to determine a plurality of intermediate NEPs between the source control domain network and the destination control domain network in the service request, wherein the intermediate NEPs comprise at least one of the following: a non-starting Ethernet NEP and a first ODU NEP in the source control domain network, a second ODU NEP in an intermediate control domain network between the source control domain network and the destination control domain network, a non-terminating Ethernet NEP and a third ODU NEP in the destination control domain network; a second determining module configured to construct a topology matrix according to the starting Ethernet NEP, the plurality of intermediate NEPs and the terminating Ethernet NEP, and determine a target transmission link satisfying a preset constraint condition and having a lowest link cost according to the topology matrix; and a routing module configured to route the service request from the starting Ethernet NEP to the terminating Ethernet NEP in the destination control domain network according to the target transmission link.

[0014] According to a further aspect of the embodiments of the present application, a computer program product is also provided, which comprises a stored computer program, wherein the computer program is executed by a processor to implement the above-mentioned routing method of a multi-layer multi-domain optical transport network.

[0015] According to a further aspect of the embodiments of the present application, an electronic device is also provided, which comprises a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the above-mentioned routing method of a multi-layer multi-domain optical transport network by the computer program.

[0016] In the embodiments of the present application, the cooperative controller initiates a service request by first receiving a starting Ethernet NEP in a source control domain network, wherein the service request carries at least first node information of a terminating Ethernet NEP in a destination control domain network; then determines a plurality of intermediate NEPs between the source control domain network and the destination control domain network in the service request, wherein the plurality of intermediate NEPs include: a non-starting Ethernet NEP and a first ODU_NEP in the source control domain network, a second ODU_NEP in an intermediate control domain network between the source control domain network and the destination control domain network, a non-terminating Ethernet NEP and a third ODU_NEP in the destination control domain network; then constructs a topology matrix according to at least the plurality of intermediate NEPs, and determines a target transmission link that meets a preset constraint condition and has a lowest link cost according to the topology matrix, effectively avoiding excessive concentration of resources in part of the link, achieving balanced allocation of network resources, and maximizing the overall throughput and service establishment success rate of the network; finally, routes the service request from the starting Ethernet NEP to the terminating Ethernet NEP in the destination control domain network according to the target transmission link, ensuring that the service request can cross multiple networks and multiple control domains, and realizing end-to-end service transmission. Thus, the technical problem of poor accuracy and low efficiency of the determined routing link when routing cross-domain services by using a fixed routing strategy or a random routing strategy is solved. BRIEF DESCRIPTION OF DRAWINGS

[0017] The accompanying drawings, which are included to provide a further understanding of the present application and are incorporated in and constitute a part of this application, illustrate embodiments of the present application and serve to explain the present application, and do not constitute improper limitations on the present application. In the drawings:

[0018] Figure 1 is a hardware structure block diagram of a computer terminal (or mobile device) according to an optional routing method for implementing a multi-layer multi-domain optical transport network according to an embodiment of the present application;

[0019] Figure 2 is a flowchart of an optional routing method for a multi-layer multi-domain optical transport network according to an embodiment of the present application;

[0020] Figure 3 is an architecture diagram of an optional packet OTN network according to related technologies;

[0021] Figure 4 is a topology diagram of an optional multi-domain optical transport network according to an embodiment of the present application;

[0022] Figure 5 is a diagram of an optional multi-layer multi-domain optical transport network model according to an embodiment of the present application;

[0023] Figure 6is a schematic diagram of a principle of an optional global optimal algorithm according to an embodiment of the present application;

[0024] Figure 7 is a schematic diagram of a principle of an optional global optimal algorithm according to an embodiment of the present application;

[0025] Figure 8 is a schematic diagram of a principle of an optional global optimal algorithm according to an embodiment of the present application;

[0026] Figure 9 is a schematic diagram of a principle of an optional global optimal algorithm according to an embodiment of the present application;

[0027] Figure 10 is a schematic diagram of a principle of an optional global optimal algorithm according to an embodiment of the present application; DETAILED DESCRIPTION

[0028] In order to make the personnel in the technical field better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by the personnel in the field without creative labor should belong to the scope of protection of the present application.

[0029] It should be noted that the terms "first", "second", and the like in the specification and claims of the present application and the above-described drawings are used to distinguish similar objects, and do not have to be used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device including a series of steps or units does not have to be limited to those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to the process, method, product or device.

[0030] In addition, the related information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for display, analyzed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties. For example, an interface is provided between the system and the related user or institution. Before obtaining the related information, the interface needs to send a request for obtaining to the aforementioned user or institution, and after receiving the consent information fed back by the aforementioned user or institution, the related information is obtained.

[0031] In order to better understand the embodiments of the present application, the technical terms involved in the embodiments of the present application are explained as follows:

[0032] OTN (Optical Transport Network): It is a kind of transmission network based on optical fiber technology, which is used to realize the transmission and exchange of optical signals. It adopts optical transmission mode to convert digital signals into optical signals for transmission, so as to realize high-speed, high-capacity and flexible data transmission. That is, the ONT transmits optical signals from one point to another point by using optical transmission equipment and optical transmission protocol, and realizes long-distance data communication.

[0033] NE (Network Element) is composed of one or more disks or frames, and can independently complete certain transmission functions. In simple terms, a 5G network is composed of multiple network elements, each of which has its own function. The network elements in the 5G network include: access and mobility management function AMF network element, session management function SMF network element, user plane function UPF network element, unified data management function UDM network element, policy control function PCF network element, authentication server function AUSF network element, network slice selection NSSF network element.

[0034] Ethernet (Ethernet) is a computer local area network technology, which specifies the content of the connection, electronic signal and medium access layer protocol including the physical layer.

[0035] ODUk (Optical channel Data Unit) is a signal-independent connection communication, which plays a connection protection and monitoring function, so its layer is also called data channel layer. In ODUk, ODU can be translated as optical data unit (professionally known as optical channel data unit), and k is the level of ODU, which can be 1, 2 and 3.

[0036] Embodiment 1

[0037] According to the embodiments of the present application, an embodiment of a routing method of a multi-layer multi-domain network is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0038] The method embodiment provided by the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 A hardware structure block diagram of a computer terminal (or mobile device) for implementing a routing method of a multi-layer multi-domain optical transport network is shown. As shown in Figure 1 As shown, the computer terminal 10 (or mobile device 10) can include one or more processors 102 (the processor 102 can include, but not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it can also include a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which can be included as one of the ports in the BUS bus), a network interface, a power supply and / or a camera. Those skilled in the art can understand that Figure 1 The structure shown is only schematic, which does not limit the structure of the above-mentioned electronic device. For example, the computer terminal 10 can also include more or fewer components than those shown in the figure, or have a different configuration than that shown in the figure. Figure 1 The structure shown is only schematic, which does not limit the structure of the above-mentioned electronic device. For example, the computer terminal 10 can also include more or fewer components than those shown in the figure, or have a different configuration than that shown in the figure. Figure 1 The structure shown is only schematic, which does not limit the structure of the above-mentioned electronic device. For example, the computer terminal 10 can also include more or fewer components than those shown in the figure, or have a different configuration than that shown in the figure.

[0039] It should be noted that the one or more processors 102 and / or other data processing circuits described above can be referred to herein generally as "data processing circuits". The data processing circuits can be embodied in whole or in part as software, hardware, firmware, or any combination thereof. In addition, the data processing circuits can be a single independent processing module, or any one of the other elements incorporated into the computer terminal 10 (or mobile device) in whole or in part. As referred to in the embodiments of the present application, the data processing circuit is a processor control (for example, selection of a variable resistance terminal path connected to an interface).

[0040] The memory 104 can be used to store software programs and modules of application software, such as program instructions / data storage devices corresponding to the routing method of the multi-layer multi-domain optical transport network in the embodiments of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implements the routing method of the multi-layer multi-domain optical transport network of the application program described above. The memory 104 can include a high-speed random access memory, and can also include a non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 can further include a memory remotely disposed with respect to the processor 102, which can be connected to the computer terminal 10 through a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0041] The transmission device 106 is configured to receive or send data via a network. The network can include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network interface controller (NIC) that can be connected to other network devices through a base station to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module that is configured to communicate with the Internet through a wireless manner.

[0042] The display can be a liquid crystal display (LCD) that is touch screen type, for example, which can enable a user to interact with a user interface of the computer terminal 10 (or mobile device).

[0043] In the above operating environment, Figure 2 is a flowchart of an optional routing method of a multi-layer multi-domain optical transport network according to an embodiment of the present application, as shown in Figure 2 The method includes steps S202-S208, wherein:

[0044] In step S202, a service request initiated by a starting Ethernet node (NEP) in a source control domain network is received.

[0045] In the technical solution provided in step S202, when the cooperative controller performs routing on the multi-layer multi-domain optical transport network (OTN), it can first receive a service request initiated by a starting Ethernet NEP (i.e., the starting point of the service flow) in a source control domain network, wherein the starting Ethernet NEP (Network Element Point) can be a physical or virtual interface on a network device in the Ethernet network in the source control domain network that can initiate, receive or process data, such as a switch port, an Ethernet interface of a router, a network adapter of a server or other Ethernet ports on a network device that can initiate or receive data transmission. The service request carries at least first node information of a terminating Ethernet NEP (i.e., the end point of the service flow) in a destination control domain network, wherein the terminating Ethernet NEP (Network Element Point) can also be a physical or virtual interface on a network device in the Ethernet network in the destination control domain network that can initiate, receive or process data, such as a switch port, an Ethernet interface of a router, a network adapter of a server or other Ethernet ports on a network device that can initiate or receive data transmission, and the first node information is used to indicate the destination of the transmission request, so that the service request can be accurately identified and processed by the network controller. Therefore, the form of the first node information includes but is not limited to a MAC (Media Access Control) address, an IP (Internet Protocol) address, a port number, a device name or ID, a VLAN ID (Virtual LAN Identifier), etc.

[0046] In step S204, a plurality of intermediate NEPs between the source control domain network and the destination control domain network in the service request are determined.

[0047] Specifically, the packet OTN network serves as a service bearing platform, which can provide a transmission channel for Ethernet in cross-layer services according to a two-layer network structure as shown in the figure. Figure 3 The two-layer network structure includes an Ethernet (ETH) layer network and an ODUk (Optical channel Data Unit) layer network. In addition, the multi-domain optical transport network is composed of multiple control domain networks to form different control domains, which are independent of each other and connected and communicated with each other through inter-domain links. The network devices in a single domain are provided by different manufacturers and integrated with control, as shown in the figure. Figure 4 Each control domain corresponding to each manufacturer contains four network elements (NEs). For ease of understanding, a two-layer network structure can be formed based on the above principle Figure 5 The multi-layer multi-domain resource abstraction model is shown, in which one control domain network or several physical nodes are abstracted as a virtual node (Node) which can be recursively contained, virtual nodes (Node) can be connected through virtual links (Link), and the virtual link (Link) is abstracted from a physical link, and each virtual link can also be an abstraction of several physical links.

[0048] In the technical solution provided in step S204, the source control domain network, the destination control domain network, and the network topology of the intermediate control domain network between the source control domain network and the destination control domain network can be regarded as a large node by the abstraction modeling of the cooperative controller, and each large node includes a plurality of network elements, each network element includes a plurality of ETH_NEP and a plurality of ODU_NEP, and the ETH_NEP and the ODU_NEP are connected through a Transitional Link (interlayer link). Therefore, the plurality of intermediate NEPs between the starting Ethernet NEP and the terminating Ethernet NEP include: a non-starting Ethernet NEP and a first ODU_NEP in the source control domain network, a second ODU_NEP in the intermediate control domain network, and a non-terminating Ethernet NEP and a third ODU_NEP in the destination control domain network.

[0049] It should be noted that, since the devices are provided by different manufacturers, the mapping scheme from the ODU_NEP to the ETH_NEP can be one-to-one or one-to-many.

[0050] In step S206, a topology matrix is constructed according to the plurality of intermediate NEPs, and a target transmission link that meets a preset constraint condition and has the lowest link cost is determined according to the topology matrix.

[0051] In the technical solution provided in step S206, there are two implementation manners of domain controller self-allocation and cooperative controller when performing service routing. The domain controller self-allocation refers to that the domain controller with the autonomous selection right can select to be associated to the ODU_NEP according to the device resource condition, so as to achieve the optimal allocation of resources to the greatest extent. The cooperative controller specifies that the ODU_NEP corresponding to the ETH_NEP is specified by the cooperative controller when establishing the service, and the premise is that the two NEPs specified must be located on the same Transitional Link, at this time, the cooperative controller has the initiative and can establish the service transmission link as needed. The embodiment of the present application mainly introduces the cooperative controller to establish the service transmission link as needed.

[0052] Specifically, the collaborative controller can construct a topology matrix based on at least multiple intermediate NEPs, where the topology matrix is ​​used to reflect the connection status of the links between each NEP; then, by analyzing the topology matrix, the optimal intermediate NEP between the source control domain network and the destination control domain network that meets the preset constraints and has the lowest link cost is selected to establish an inter-layer link (i.e., the target transmission link), thereby forming an inter-layer channel and realizing cross-layer routing.

[0053] Step S208: Routing the service request from the starting Ethernet NEP to the terminating Ethernet NEP in the destination control domain network according to the target transmission link.

[0054] In the technical solution provided in step S208, the collaborative controller routes the service request from the starting Ethernet NEP to the terminating Ethernet NEP in the destination domain network according to the determined optimal transmission link, ensuring that the service request can cross multiple layers of networks and multiple control domains to achieve end-to-end service transmission.

[0055] The above method of this embodiment is further introduced below.

[0056] As an optional implementation, in the technical solution provided in step S206 above, the collaborative controller can use a global optimization algorithm to determine the target transmission link. Global optimization involves calculating the optimal transmission path between the starting Ethernet NEP and the terminating Ethernet NEP across the entire network. This can be achieved by the following steps:

[0057] Step S11 : constructing a first topology matrix with a starting Ethernet NEP, multiple intermediate NEPs, and a terminating Ethernet NEP as rows and columns, and link costs of sub-links between NEPs corresponding to each row and column as matrix elements.

[0058] In the technical solution provided in step S11 above, the first topology matrix is ​​recorded as M(m×m), where m represents the total number of NEPs. ij It should be noted that the link costs of the sub-links between the NEPs in the same network element (NE) are all zero. ij = 0, and if there is no sub-link between the NEP corresponding to the i-th row and the NEP corresponding to the j-th column, then M ij =∞.

[0059] Step S12: Analyze the first topology matrix using the Dijkstra algorithm to obtain a first transmission link that satisfies the constraint conditions and has the lowest link cost, and use the first transmission link as the target transmission link.

[0060] The technical solution provided in the step S12 can be understood as follows: the first topological matrix is preprocessed by using each constraint condition to filter out the NEP satisfying each constraint condition, and the first topological matrix is reconstructed, and the Dijkstra algorithm is used to analyze the reconstructed first topological matrix, and multiple factors are considered in the link determination process to find the first transmission link with the lowest link cost, and the first transmission link is taken as the target transmission link to be determined, thereby reducing the service pressure of the link to some extent and realizing balanced link load.

[0061] For example, Figure 6 is a schematic diagram of an optional global optimal algorithm according to an embodiment of the present application, as shown in Figure 6 For ease of understanding, the routing shown in Figure 6 can be converted into a network topology structure diagram as shown in Figure 7 , which can be represented as G(V, E, w), where V represents a set of domains, E represents a set of each NEP in the domain, and w represents the link cost between each NEP, that is, {d distance, res residual resource, ratio resource occupancy rate}. Then, the calculation of the route between the end-to-end domains can be converted into the calculation of the optimal path between two nodes in the topology graph. The Dijkstra algorithm can be used to obtain the shortest link between node A in domain A and node C in domain C.

[0062] The constraint conditions include at least one of the following: the sum of the link distances of each sub-link is less than a preset first threshold, the sum of the link resource usage rates of each sub-link is less than a preset second threshold, the sum of the hop counts of each sub-link is less than a preset third threshold, and the link states of each sub-link are all normal. The link cost is the weighted average sum of the values of the sub-link in the preset link evaluation dimension, and the link evaluation dimension includes but is not limited to: link distance (i.e. physical distance between two NEPs), link resource usage rate (i.e. ratio of used resource amount to total resource amount of the link), hop count (i.e. number of sub-paths spanning between two NEPs), link state, etc.

[0063] As another optional implementation, in the technical solution provided in the step S206, the local optimal algorithm can also be used by the cooperative controller to determine the target transmission link, wherein the local optimal algorithm only needs to determine the link on the basis of the inter-domain link. The local optimal algorithm can be implemented by the following steps:

[0064] In step S21, a non-starting Ethernet NEP or a first ODU NEP in the source control domain network is taken as a starting NEP in the source control domain network, and a non-terminating Ethernet NEP or a third ODU NEP in the destination control domain network is taken as a terminating NEP in the source control domain network.

[0065] The technical solution provided by the step S21 can be understood as follows: a virtual node is abstracted at the center of the source control domain network and the destination control domain network respectively as the start point (start NEP) and the end point (end NEP) of the target link to be solved, and the selection criteria are that the link cost of the sub-link between the start NEP and the start Ethernet NEP and the link cost of the sub-link between the end NEP and the end Ethernet NEP are both less than a preset threshold value, such as a minimum value ε (ε>0). Therefore, the start point of the target link to be solved can be a non-start Ethernet NEP or a first ODU_NEP in the source control domain network, and the end point of the target link to be solved can be a non-end Ethernet NEP or a third ODU_NEP in the destination control domain network, thereby avoiding the problem of how to select the start point and the end point from the boundary nodes of the domain.

[0066] In step S22, a second topology matrix is constructed with the start NEP, the end NEP, and the intermediate NEPs between the start NEP and the end NEP as rows and columns, and the link cost of the sub-link between the NEPs corresponding to each row and each column as the matrix elements.

[0067] In the technical solution provided by the step S22, the second topology matrix is denoted as N (n×n), where n represents the total number of NEPs between the start point and the end point of the target link to be solved, and then N ij represents the link cost of the sub-link between the NEP corresponding to the ith row and the NEP corresponding to the jth column. It should be noted that the link cost of the sub-link between the NEPs within the same network element (NE) is zero, and M ij =0.

[0068] In step S23, the Dijkstra algorithm is used to analyze the second topology matrix to obtain the second transmission link that meets the constraint condition and has the lowest link cost.

[0069] The technical solution provided by the step S23 can be understood as follows: the second topology matrix is preprocessed using the above-mentioned various constraint conditions to filter out the NEPs that meet the above-mentioned various constraint conditions, the second topology matrix is reconstructed, and the Dijkstra algorithm is used to analyze the reconstructed second topology matrix, and various factors are considered in the path determination process to find the second transmission link with the lowest link cost, thereby reducing the business pressure of the link to a certain extent and achieving balanced link load.

[0070] In step S24, the third transmission link between the start Ethernet NEP and the start NEP and the fourth transmission link between the end NEP and the end Ethernet NEP are determined, and the target transmission link is composed of the third transmission link, the second transmission link, and the fourth transmission link.

[0071] For example, Figure 8 is a schematic diagram of an optional multi-layer multi-domain local optimal routing according to an embodiment of the present application, such as Figure 8 As shown. Since A and Z are the source node and destination node of the actual path calculation, for the sake of convenience, we can directly let A ′ =A, Z ′ = Z, then when constructing the second topology matrix, the collection of NEPs is divided into the following two steps: (1) obtaining all NEPs at both ends of all inter-domain links (i.e., multiple intermediate NEPs); (2) adding source node A and sink node Z, so that the path calculation result is the actual transmission link that needs to be determined. Similarly, Figure 8 The route shown is converted to the form Figure 7 The network topology diagram shown is for the convenience of subsequent analysis using the Dijkstra algorithm to quickly find the shortest link between node A in domain A and node C in domain C.

[0072] In addition, in the above steps S11-S12 and steps S22-S24, the above link cost is the weighted average sum of the values ​​of the sub-links in the preset link evaluation dimensions, and the link evaluation dimensions include at least one of the following: link distance, link resource utilization, number of hops, and link status.

[0073] For example, using link evaluation dimensions including link distance (dist) and link resource utilization (rsrc) (used resources / total resources), the link cost of each sub-link can be expressed as: cost = α*dist + β*rsrc, where α and β represent scaling factors for link distance (dist) and link resource utilization (rsrc), respectively, such that α + β = 1. Compared to considering only a single dimension, this approach can significantly avoid excessive traffic concentration on a single path, significantly improving the success rate of service establishment even in high-volume scenarios.

[0074] It should be noted that when using the values ​​of the sub-link in multiple link evaluation dimensions to determine the link cost, it is necessary to approximate the values ​​of the sub-link in each link evaluation dimension so that the two values ​​are in the same order of magnitude to avoid the value difference being too large and causing one side to have no effect.

[0075] As an optional implementation, in the technical solution provided in step S208 above, the collaborative controller may construct a topology matrix and route service requests by the following method, including:

[0076] Step S2081: Determine the control domain network to which each NEP on the target transmission link belongs, and obtain the transmission sub-links in each control domain network.

[0077] That is, each NEP on the target transmission link is divided into respective control domain networks to form transmission sub-links in each control domain network. The control domain networks include a source control domain network, a destination control domain network, and an intermediate control domain network.

[0078] For example, for the target transmission link shown in FIG. 6, each node on the target transmission link can be divided into the corresponding control domains A, B, and C to obtain transmission sub-links in the control domain networks A, B, and C: {A, a1, a2}, {b1, b2}, and {c, Z}. Figure 6 For example, for the target transmission link shown in FIG. 6, each node on the target transmission link can be divided into the corresponding control domains A, B, and C to obtain transmission sub-links in the control domain networks A, B, and C: {A, a1, a2}, {b1, b2}, and {c, Z}.

[0079] Figure 8 For example, for the target transmission link shown in FIG. 6, each node on the target transmission link can be divided into the corresponding control domains A, B, and C to obtain transmission sub-links in the control domain networks A, B, and C: {A, a1, a2}, {b1, b2}, and {c, Z}.

[0080] In step S2082, the service request is adjusted according to the type of the control domain network, and the adjusted service request is routed to the terminating Ethernet NEP in the destination control domain network according to the transmission sub-link in each control domain network.

[0081] In the multi-layer multi-domain service scenario, the service flows in from the ETH layer, is transported by the ODU layer, and finally flows out from the ETH layer. Therefore, the source control domain network and the destination control domain network need to carry the ETH service, and thus a two-layer connection request needs to be issued in the source control domain network and the destination control domain network.

[0082] Therefore, when the collaborative controller routes the service request across the domains, in order to enable the collaborative controller to obtain all the network element information (i.e., how to route from the starting Ethernet NEP to the terminating Ethernet NEP) and obtain full control, the service request can be adjusted as follows:

[0083] For the transmission sub-link in the source control domain network, in the process of routing the service request from the starting Ethernet NEP to the non-starting Ethernet NEP, the second node information of the starting Ethernet NEP and the third node information of the non-starting Ethernet NEP are added in the service request; in the process of routing the service request from the current first ODU_NEP to the next first ODU_NEP in the source control domain network, the third node information of the non-starting Ethernet NEP, the fourth node information of the current first ODU_NEP, and the fifth node information of the next first ODU_NEP are added in the service request.

[0084] ​For the transmission sub-link in the intermediate control domain network, in the process of routing the service request from the current second ODU_NEP to the next second ODU_NEP, the sixth node information of the current second ODU_NEP and the seventh node information of the next second ODU_NEP are added in the service request;

[0085] For the transmission sub-link in the destination control domain network, in the process of routing the service request from the current third ODU_NEP to the next third ODU_NEP in the destination control domain network, the eighth node information of the current third ODU_NEP and the ninth node information of the next third ODU_NEP are added in the service request; in the process of routing the service request from the non-terminating Ethernet NEP to the terminating Ethernet NEP, the first node information of the terminating Ethernet NEP and the tenth node information of the non-terminating Ethernet NEP are added in the service request.

[0086] For the transmission sub-link in the destination control domain network, in the process of routing the service request from the current third ODU_NEP to the next third ODU_NEP in the destination control domain network, the eighth node information of the current third ODU_NEP and the ninth node information of the next third ODU_NEP are added in the service request; in the process of routing the service request from the non-terminating Ethernet NEP to the terminating Ethernet NEP, the first node information of the terminating Ethernet NEP and the tenth node information of the non-terminating Ethernet NEP are added in the service request. Figure 9 Taking the multi-layer multi-domain optical transport network shown in the figure as an example, the ETH_NEP1 in the network element NE1 in the large node responsible by the vendor A is taken as the starting Ethernet NEP in the source control domain network, and the ETH_NEP1 in the network element NE4 in the large node responsible by the vendor C is taken as the terminating Ethernet NEP in the destination control domain network.

[0087] Then when the network element NE1 in the large node responsible by the vendor A carries the ETH service, and the service request is sent from the starting Ethernet NEP—ETH_NEP1 in the source control domain network to the starting Ethernet NEP—ETH_NEP2, the identification information of {NEA1.ETH_NEP1, NEA1.ETH_NEP2} needs to be added in the request message, where ETH_NEP2 represents the identification information of the ETH_NEP. When the service request is sent from the first ODU_NEP—ODU_NEP1 in the source control domain network to the next first ODU_NEP—ODU_NEP2, the identification information of {NEA1.ETH_NEP2, NEA1.ODU_NEP1, NEA4.ODU_NEP1} needs to be added in the request message. When the service request is sent from the ODU_NEP2 of the network element NE4 in the large node responsible by the vendor A to the ODU_NEP1 of the network element NE1 in the large node responsible by the vendor B, the identification information of {NEA4.ODU_NEP2, NEB1.ODU_NEP1} needs to be added in the request message.

[0088] Based on the scheme defined in steps S202 to S208, in the embodiment, the cooperative controller can construct a topology matrix according to a plurality of intermediate NEPs between the start Ethernet NEP in the source control domain network and the end Ethernet NEP in the destination control domain network, and obtain a target transmission link with optimal performance in a plurality of link evaluation dimensions (i.e., the lowest link cost) according to a preset constraint condition (i.e., meeting a preset link requirement and a routing condition) by using a global optimal algorithm or a local optimal algorithm, thereby improving resource utilization, reducing link congestion, greatly improving network carrying capacity and service establishment success rate. Efficient and balanced management and transmission of cross-domain services in a complex network environment are realized, and the utilization efficiency of network resources and service quality are significantly improved, providing more stable and high-speed network experience for operators and users.

[0089] Embodiment 2

[0090] Based on the embodiment 1 of the present application, an embodiment of a routing device of a multi-layer multi-domain optical transport network is further provided, which executes the routing method of the multi-layer multi-domain optical transport network of the above-mentioned embodiment when running. Wherein, Figure 10 is a structural schematic diagram of an optional routing device of a multi-layer multi-domain optical transport network according to the embodiment of the present application, as Figure 10 shown, the routing device of the multi-layer multi-domain optical transport network at least includes: a receiving module 102, a first determining module 104, a second determining module 106 and a routing module 108, wherein:

[0091] The receiving module 102 is configured to receive a service request initiated by a start Ethernet NEP in a source control domain network, wherein the service request at least carries first node information of an end Ethernet NEP in a destination control domain network;

[0092] The first determining module 104 is configured to determine a plurality of intermediate NEPs between the source control domain network and the destination control domain network in the service request, wherein the intermediate NEPs include at least one of the following: a non-start Ethernet NEP and a first ODU NEP in the source control domain network, a second ODU NEP in an intermediate control domain network between the source control domain network and the destination control domain network, a non-end Ethernet NEP and a third ODU NEP in the destination control domain network;

[0093] The second determining module 106 is configured to construct a topology matrix according to the start Ethernet NEP, the plurality of intermediate NEPs and the end Ethernet NEP, and determine a target transmission link that meets a preset constraint condition and has the lowest link cost according to the topology matrix;

[0094] The routing module 108 is configured to route the service request from the start Ethernet NEP to the end Ethernet NEP in the target transmission link in the destination control domain network.

[0095] It should be noted that each module in the routing device of the multi-layer multi-domain optical transport network can be a program module (for example, a program instruction set for implementing a certain specific function) or a hardware module. For the hardware module, it can be in the following forms, but is not limited thereto: each module is a processor, or the functions of each module are implemented by a processor.

[0096] Embodiment 3

[0097] According to the embodiments of the present application, a non-volatile storage medium is also provided, which stores a program. When the program is executed, the device in which the non-volatile storage medium is located performs the routing method of the multi-layer multi-domain optical transport network in the embodiment 1.

[0098] Optionally, the device in which the non-volatile storage medium is located performs the following steps by executing the program: receiving a service request initiated by a start Ethernet NEP in a source control domain network, wherein the service request carries at least first node information of an end Ethernet NEP in a destination control domain network; determining a plurality of intermediate NEPs between the source control domain network and the destination control domain network in the service request, wherein the plurality of intermediate NEPs include: a non-start Ethernet NEP and a first ODU_NEP in the source control domain network, a second ODU_NEP in an intermediate control domain network between the source control domain network and the destination control domain network, a non-end Ethernet NEP and a third ODU_NEP in the destination control domain network; constructing a topology matrix according to at least the plurality of intermediate NEPs, and determining a target transmission link that meets a preset constraint condition and has a lowest link cost according to the topology matrix; and routing the service request from the start Ethernet NEP to the end Ethernet NEP in the target transmission link in the destination control domain network.

[0099] According to the embodiments of the present application, a computer program product is also provided, which includes a stored computer program. When the computer program is executed by a processor, the routing method of the multi-layer multi-domain optical transport network in the embodiment 1 is implemented.

[0100] Optionally, the computer program performs the following steps: receiving a service request initiated by a start Ethernet NEP in a source control domain network, wherein the service request carries at least first node information of a terminal Ethernet NEP in a destination control domain network; determining a plurality of intermediate NEPs between the source control domain network and the destination control domain network in the service request, wherein the plurality of intermediate NEPs comprise: a non-start Ethernet NEP and a first ODU_NEP in the source control domain network, a second ODU_NEP in an intermediate control domain network between the source control domain network and the destination control domain, a non-terminal Ethernet NEP and a third ODU_NEP in the destination control domain network; constructing a topology matrix according to at least the plurality of intermediate NEPs, and determining a target transmission link satisfying a preset constraint condition and having a lowest link cost according to the topology matrix; and routing the service request from the start Ethernet NEP to the terminal Ethernet NEP in the destination control domain network according to the target transmission link.

[0101] According to an embodiment of the present application, a processor is further provided, which is configured to execute a program. The program is configured to perform the routing method of the multi-layer multi-domain optical transport network in the above embodiment 1 when the program is executed.

[0102] Optionally, the computer program performs the following steps: receiving a service request initiated by a start Ethernet NEP in a source control domain network, wherein the service request carries at least first node information of a terminal Ethernet NEP in a destination control domain network; determining a plurality of intermediate NEPs between the source control domain network and the destination control domain network in the service request, wherein the plurality of intermediate NEPs comprise: a non-start Ethernet NEP and a first ODU_NEP in the source control domain network, a second ODU_NEP in an intermediate control domain network between the source control domain network and the destination control domain, a non-terminal Ethernet NEP and a third ODU_NEP in the destination control domain network; constructing a topology matrix according to at least the plurality of intermediate NEPs, and determining a target transmission link satisfying a preset constraint condition and having a lowest link cost according to the topology matrix; and routing the service request from the start Ethernet NEP to the terminal Ethernet NEP in the destination control domain network according to the target transmission link.

[0103] According to an embodiment of the present application, an electronic device is further provided, which comprises one or more processors; and a memory configured to store one or more programs. The one or more programs, when executed by the one or more processors, cause the one or more processors to implement a program configured to perform the routing method of the multi-layer multi-domain optical transport network in the above embodiment 1.

[0104] Optionally, the processor is configured to implement the following steps by computer program execution: receiving a service request initiated by a starting Ethernet NEP in a source control domain network, wherein the service request carries at least first node information of a terminating Ethernet NEP in a destination control domain network; determining a plurality of intermediate NEPs between the source control domain network and the destination control domain network in the service request, wherein the plurality of intermediate NEPs comprise: a non-starting Ethernet NEP and a first ODU_NEP in the source control domain network, a second ODU_NEP in an intermediate control domain network between the source control domain network and the destination control domain network, a non-terminating Ethernet NEP and a third ODU_NEP in the destination control domain network; constructing a topology matrix according to at least the plurality of intermediate NEPs, and determining a target transmission link satisfying a preset constraint condition and having a lowest link cost according to the topology matrix; and routing the service request from the starting Ethernet NEP to the terminating Ethernet NEP in the destination control domain network according to the target transmission link.

[0105] The above-mentioned sequence numbers of the embodiments of the present application are only for description, and do not represent advantages or disadvantages of the embodiments.

[0106] In the above-mentioned embodiments of the present application, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the relevant description of other embodiments.

[0107] In the several embodiments of the present application, it should be understood that the disclosed technology can be implemented in other ways. Of course, the embodiment described above is only illustrative, and for example, the division of units can be a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, units or modules, and can be electrical or other forms.

[0108] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on multiple units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0109] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The above integrated unit can be realized in the form of hardware or in the form of software functional unit.

[0110] The integrated unit, if implemented in the form of a software function unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application or the part that essentially contributes to the related art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the embodiments of the present application. The aforementioned storage medium includes a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store program codes.

[0111] The above is only the preferred embodiment of the present application. It should be noted that, for those skilled in the art, without departing from the principles of the present application, a number of improvements and refinements can be made, which should also be considered as the protection scope of the present application.

Claims

1. A routing method for a multi-layer multi-domain optical transport network, characterized in that: include: Receiving a service request initiated by a starting Ethernet network element node NEP in a source control domain network, wherein the service request carries at least first node information of a terminating Ethernet NEP in a destination control domain network; Determine a plurality of intermediate NEPs between the source control domain network and the destination control domain network in the service request, wherein the plurality of intermediate NEPs include: a non-initial Ethernet NEP and a first optical path data unit (ODU_NEP) in the source control domain network, a second ODU_NEP in an intermediate control domain network between the source control domain network and the destination control domain, and a non-terminating Ethernet NEP and a third ODU_NEP in the destination control domain network; constructing a topology matrix at least based on the plurality of intermediate NEPs, and determining a target transmission link that satisfies preset constraints and minimizes link cost based on the topology matrix; The service request is routed from the starting Ethernet NEP to a terminating Ethernet NEP in the destination control domain network according to the target transmission link.

2. The method according to claim 1, characterized in that Constructing a topology matrix at least based on the plurality of intermediate NEPs, and determining a target transmission link that satisfies preset constraints and minimizes link cost based on the topology matrix, including: Constructing a first topology matrix using the starting Ethernet NEP, the multiple intermediate NEPs, and the terminating Ethernet NEP as rows and columns, and using link costs of sub-links between NEPs corresponding to each row and each column as matrix elements; The first topology matrix is ​​analyzed using the Dijkstra algorithm to obtain a first transmission link that satisfies the constraint condition and minimizes the link cost, and the first transmission link is used as the target transmission link.

3. The method according to claim 1, characterized in that Constructing a topology matrix at least based on the plurality of intermediate NEPs, and determining a target transmission link that satisfies preset constraints and minimizes link cost based on the topology matrix, including: A non-initial Ethernet NEP or a first ODU_NEP in the source control domain network is used as the initial NEP in the source control domain network, and a non-termination Ethernet NEP or a third ODU_NEP in the destination control domain network is used as the termination NEP in the source control domain network, wherein a link cost of a sublink between the initial NEP and the initial Ethernet NEP and a link cost of a sublink between the termination NEP and the termination Ethernet NEP are both less than a preset threshold value; Constructing a second topology matrix using the starting NEP, the ending NEP, and intermediate NEPs between the starting NEP and the ending NEP as rows and columns, and using link costs of sub-links between NEPs corresponding to each row and each column as matrix elements; Analyzing the second topology matrix using a Dijkstra algorithm to obtain a second transmission link that satisfies the constraint condition and minimizes the link cost; A third transmission link between the starting Ethernet NEP and the starting NEP and a fourth transmission link between the terminating NEP and the terminating Ethernet NEP are determined, and the target transmission link is composed of the third transmission link, the second transmission link, and the fourth transmission link.

4. The method according to any one of claims 2 or 3, characterized in that The link cost is a weighted average sum of the values ​​of the sub-links in preset link evaluation dimensions, and the link evaluation dimensions include at least one of the following: link distance, link resource utilization, number of hops, and link status.

5. The method according to any one of claims 2 or 3, characterized in that The constraint conditions include at least one of the following: the sum of the link distances of each of the sub-links is less than a preset first threshold, the sum of the link resource utilization rates of each of the sub-links is less than a preset second threshold, the sum of the hop counts of each of the sub-links is less than a preset third threshold, and the link status of each of the sub-links is normal.

6. The method according to claim 1, characterized in that Routing the service request from the starting Ethernet NEP to a terminating Ethernet NEP in the destination control domain network according to the target transmission link includes: Determine the control domain network to which each NEP on the target transmission link belongs, and obtain transmission sub-links within each of the control domain networks, wherein the types of the control domain networks include: the source control domain network, the destination control domain network, and the intermediate control domain network; The service request is adjusted according to the type of the control domain network, and the adjusted service request is routed to a terminating Ethernet NEP in the destination control domain network according to the transmission sub-links in each of the control domain networks.

7. The method according to claim 6, characterized in that Adjusting the service request to be routed according to the type of the control domain network includes: For the transmission sub-link within the source control domain network, in the process of routing the service request from the starting Ethernet NEP to the non-starting Ethernet NEP, the second node information of the starting Ethernet NEP and the third node information of the non-starting Ethernet NEP are added to the service request; in the process of routing the service request from the current first ODU_NEP within the source control domain network to the next first ODU_NEP, the third node information of the non-starting Ethernet NEP, the fourth node information of the current first ODU_NEP, and the fifth node information of the next first ODU_NEP are added to the service request; For the transmission sub-link in the intermediate control domain network, in the process of routing the service request from the current second ODU_NEP in the intermediate control domain network to the next second ODU_NEP, adding the sixth node information of the current second ODU_NEP and the seventh node information of the next second ODU_NEP to the service request; For the transmission sub-link within the destination control domain network, in the process of routing the service request from the current third ODU_NEP within the destination control domain network to the next third ODU_NEP, the eighth node information of the current third ODU_NEP and the ninth node information of the next third ODU_NEP are added to the service request; in the process of routing the service request from the non-terminating Ethernet NEP to the terminating Ethernet NEP, the first node information of the terminating Ethernet NEP and the tenth node information of the non-terminating Ethernet NEP are added to the service request.

8. A routing device for a multi-layer, multi-domain optical transport network, characterized in that: include: A receiving module, configured to receive a service request initiated by an initiating Ethernet NEP in a source control domain network, wherein the service request carries at least first node information of a terminating Ethernet NEP in a destination control domain network; a first determining module, configured to determine a plurality of intermediate NEPs between the source control domain network and the destination control domain network in the service request, wherein the plurality of intermediate NEPs include: a non-initial Ethernet NEP and a first ODU NEP in the source control domain network, a second ODU NEP in an intermediate control domain network between the source control domain network and the destination control domain, and a non-terminating Ethernet NEP and a third ODU NEP in the destination control domain network; A second determining module is configured to construct a topology matrix based on the starting Ethernet NEP, the plurality of intermediate NEPs, and the terminating Ethernet NEP, and determine, based on the topology matrix, a target transmission link that satisfies preset constraints and has the lowest link cost; A routing module is configured to route the service request from the starting Ethernet NEP to a terminating Ethernet NEP in the destination control domain network according to the target transmission link.

9. A computer program product, characterized in that include: A computer program, wherein when the computer program is executed by a processor, the routing method of the multi-layer multi-domain optical transport network according to any one of claims 1 to 7 is implemented.

10. An electronic device, characterized in that: include: A memory and a processor, wherein the processor is configured to run a program stored in the memory, wherein the program, when running, executes the routing method for a multi-layer and multi-domain optical transport network according to any one of claims 1 to 7.

Images