A method and system for optimizing routing in an optical communication network

Abstract

The present invention discloses an optical communication network routing optimization method and system, specifically relating to the technical field of multi-domain optical network collaborative networking, and is used to solve the problem of path selection deviation caused by topological abstraction and simplification in existing multi-domain optical networks; by obtaining the inter-domain topological abstraction information of the cross-domain optical network, reverse generating intra-domain topological compensation parameters representing the potential path resource consumption within the sub-domain, and dynamically monitoring the implicit link competition relationship of cross-domain optical path sharing in combination with real-time link resource data to generate a competition intensity index; evaluating the port resource consumption weight based on the compensation parameter and the competition intensity index, fusing the load status to generate the optimal port selection weight, and finally screening the global path through the weight priority and triggering the optical switching node instruction to establish a cross-domain optical path; realizing the dynamic collaborative optimization of resource consumption and competition conflict in the multi-domain optical network, effectively improving the accuracy of cross-domain path selection and the global utilization rate of network resources, and reducing the risks of redundant jumps and local link congestion.

Description

Technical Field

[0001] The present invention relates to the technical field of multi-domain optical network collaborative networking, and more specifically, the present invention relates to an optical communication network routing optimization method and system. Background Art

[0002] In the modern optical communication network architecture, the multi-domain collaborative networking mode is an important direction for realizing wide-area service interconnection. To balance the efficiency of cross-domain resource management and the requirements of sub-domain autonomy, the prior art usually adopts a topology abstraction method to simplify the internal network structure of the sub-domain into the summary information of boundary nodes and link resources for interaction. Although it reduces the complexity of cross-domain collaboration, it causes the key topological details required for global routing decision-making to be implicitized, making it difficult to accurately guide the selection of nodes and links in the process of establishing cross-domain optical paths.

[0003] In the prior art, due to the excessive simplification of the internal structure of the sub-domain by the topology abstraction mechanism, the cross-domain optical network routing optimization has the defect that the inter-domain path selection does not match the actual resource distribution within the domain. Specifically, it is unable to effectively evaluate the optimality of the internal port nodes of the sub-domain when establishing an optical path across domains, resulting in the accumulation of redundant hops and local link resource overload in the actual transmission of the selected path, significantly reducing the global utilization rate of network resources and exacerbating the uncertainty of service transmission delay, especially prominent in the multi-domain collaborative scenario. Summary of the Invention

[0004] In order to overcome the above-mentioned defects of the prior art, the embodiments of the present invention provide an optical communication network routing optimization method and system to solve the problems proposed in the above background art.

[0005] To achieve the above object, the present invention provides the following technical solutions:

[0006] An optical communication network routing optimization method, comprising the following steps:

[0007] S1. Obtain the inter-domain topology abstraction information of the cross-domain optical network, where the inter-domain topology abstraction information includes the boundary node identifiers of each sub-domain and the link resource data between the boundary nodes;

[0008] S2. Generate the intra-domain topology compensation parameters of each sub-domain based on the boundary node identifiers, where the intra-domain topology compensation parameters are used to characterize the potential path resource consumption between the internal boundary nodes of the sub-domain;

[0009] S3. Dynamically monitor the implicit link competition relationship shared by the cross-domain optical paths within each sub-domain according to the intra-domain topology compensation parameters and the link resource data, and generate a competition intensity index;

[0010] S4. Evaluate the port resource consumption weights of the boundary nodes of each sub-domain based on the intra-domain topology compensation parameters and the competition intensity index;

[0011] S5. Generate the optimal port selection weight for the candidate cross - domain optical path by combining the port resource consumption weight and the link resource data;

[0012] S6. Screen the global routing path according to the optimal port selection weight and trigger the port selection instruction of the optical switching node to establish the cross - domain optical path.

[0013] In a preferred embodiment, obtain the inter - domain topological abstraction information of the cross - domain optical network, including:

[0014] Obtain the boundary node identifiers of each sub - domain through the network management system of the multi - domain optical network. The boundary node identifier includes the mapping relationship between the physical port number and the logical address of the boundary node;

[0015] Collect the link resource data between boundary nodes based on the software - defined network controller. The link resource data includes the available bandwidth value and the current load ratio of each link;

[0016] Associate and store the boundary node identifier and the link resource data as the inter - domain topological abstraction information, and dynamically refresh the associated storage result according to the update period of the link resource data.

[0017] In a preferred embodiment, generate the intra - domain topological compensation parameters for each sub - domain based on the boundary node identifier, including:

[0018] Extract the position distribution characteristics of adjacent boundary nodes in the boundary node set of each sub - domain based on the boundary node identifier. The position distribution characteristics include the distance and connection density between adjacent boundary nodes;

[0019] Calculate the hop count and path length of the potential paths between internal boundary nodes of each sub - domain according to the position distribution characteristics. The hop count and path length are generated through a preset path derivation rule;

[0020] Map the hop count and path length to the intra - domain topological compensation parameters, and associate and store the intra - domain topological compensation parameters with the boundary node identifier of the corresponding sub - domain.

[0021] In a preferred embodiment, dynamically monitor the implicit link competition relationship shared by the cross - domain optical paths within each sub - domain according to the intra - domain topological compensation parameters and the link resource data, and generate a competition intensity index, including:

[0022] Locate the shared physical links within each sub - domain that are shared by multiple cross - domain optical paths according to the path length and hop count in the intra - domain topological compensation parameters;

[0023] Based on the current load ratio in the link resource data, count the number of real - time cross - domain optical paths of the shared physical link, and calculate the dynamic resource fluctuation threshold of the shared physical link in combination with the path length in the intra - domain topological compensation parameters;

[0024] Generate a first competition factor based on the difference ratio between the number of real-time cross-domain optical paths and the dynamic resource fluctuation threshold, and generate a second competition factor based on the ratio of path length to the number of hops;

[0025] If the first competition factor exceeds the preset warning threshold, directly use the first competition factor as the competition intensity index; if not, generate the competition intensity index according to the mapping relationship between the second competition factor and the sub-domain type, and associate the competition intensity index with the boundary node identifier of the corresponding physical link.

[0026] In a preferred embodiment, the shared physical link is determined by reverse derivation through the logical address mapping relationship in the boundary node identifier.

[0027] In a preferred embodiment, evaluate the port resource consumption weights of the boundary nodes of each sub-domain based on the intra-domain topology compensation parameter and the competition intensity index, including:

[0028] Generate the initial resource consumption weights of each boundary node based on the path length and the number of hops in the intra-domain topology compensation parameter. The initial resource consumption weight is a linear combination of the path length and the number of hops;

[0029] Adjust the initial resource consumption weight according to the type of the competition intensity index. If the competition intensity index is the first competition factor, adjust it according to the difference ratio increase; if it is the second competition factor, adjust it according to the preset coefficient of the sub-domain type;

[0030] Normalize the adjusted initial resource consumption weight into the port resource consumption weight, and bind and store it with the logical address mapping relationship in the boundary node identifier.

[0031] In a preferred embodiment, generate the optimal port selection weight of the candidate cross-domain optical path by combining the port resource consumption weight and the link resource data, including:

[0032] Divide the links of the candidate cross-domain optical path according to the available bandwidth value in the link resource data, and set an initial port selection weight coefficient for each type of link;

[0033] Calculate the initial port selection weight of the candidate cross-domain optical path based on the port resource consumption weight and the current load ratio in the link resource data;

[0034] Dynamically adjust the initial port selection weight according to the initial port selection weight coefficient corresponding to the link type to generate the optimal port selection weight, and associate the optimal port selection weight with the logical address mapping relationship of the candidate cross-domain optical path.

[0035] In a preferred embodiment, the links of the candidate cross-domain optical path are divided into high-bandwidth links, medium-bandwidth links and low-bandwidth links; the initial port selection weight is the product of the port resource consumption weight and the reciprocal of the current load ratio.

[0036] In a preferred embodiment, screening the global routing path according to the optimal port selection weight and triggering the port selection instruction of the optical switching node to establish a cross-domain optical path includes:

[0037] Group the global routing paths according to the priority of the optimal port selection weight. The priority grouping rule is to divide the paths with the optimal port selection weight higher than the preset load fluctuation threshold into the high-priority group, and the rest into the low-priority group;

[0038] Dynamically adjust the path ratio between the high-priority group and the low-priority group based on the current load ratio in the link resource data. If the current load ratio exceeds the preset load fluctuation threshold, reduce the number of paths in the high-priority group;

[0039] Trigger the port selection instruction of the optical switching node according to the adjusted path grouping result. The port selection instruction includes the logical address mapping relationship and port number of the paths in the high-priority group to establish a cross-domain optical path.

[0040] On the other hand, the present invention provides an optical communication network routing optimization system, including:

[0041] Topology data acquisition module: Obtain the inter-domain topology abstraction information of the cross-domain optical network. The inter-domain topology abstraction information includes the boundary node identifiers of each sub-domain and the link resource data between the boundary nodes;

[0042] Compensation parameter generation module: Generate the intra-domain topology compensation parameters of each sub-domain based on the boundary node identifiers. The intra-domain topology compensation parameters are used to characterize the potential path resource consumption between the internal boundary nodes of the sub-domain;

[0043] Implicit competition monitoring module: Dynamically monitor the implicit link competition relationship shared by the cross-domain optical paths within each sub-domain according to the intra-domain topology compensation parameters and the link resource data, and generate a competition intensity index;

[0044] Port weight evaluation module: Evaluate the port resource consumption weight of the boundary nodes of each sub-domain based on the intra-domain topology compensation parameters and the competition intensity index;

[0045] Optimal weight generation module: Combine the port resource consumption weight and the link resource data to generate the optimal port selection weight of the candidate cross-domain optical path;

[0046] Optical path trigger execution module: Screen the global routing path according to the optimal port selection weight and trigger the port selection instruction of the optical switching node to establish a cross-domain optical path.

[0047] Compared with the prior art, the present invention has the following beneficial effects:

[0048] 1. By reversely generating intra-domain topology compensation parameters based on boundary node identifiers, the unknown path resource consumption inside the sub-domain is transformed into a quantifiable dynamic index. Combining real-time link load data and competition intensity evaluation, it provides a multi-dimensional resource evaluation basis for cross-domain optical path establishment. It can not only accurately identify the implicit competition conflicts of cross-domain optical paths sharing physical links inside the sub-domain, but also avoid the selection of redundant jump paths through the dynamic integration of compensation parameters and weight evaluation, significantly improving the stability of end-to-end service transmission and the balance of global network resource allocation. Especially in high-dynamic load scenarios, it can more sensitively respond to resource fluctuations inside the sub-domain and reduce the risk of local link congestion;

[0049] 2. With the topology compensation parameters and competition intensity indicators as the core drivers, through the hierarchical calculation and dynamic adjustment of resource evaluation weights, the collaborative optimization of static resource consumption and dynamic competition status in the cross-domain path selection process is realized. In the path screening stage, priority grouping is carried out according to the optimal port weights, and the path ratio is dynamically adjusted in combination with the real-time network load, improving the utilization rate of high-capacity links while reducing the optical path establishment delay. It can adapt to the dynamic changes of resources inside the sub-domain and solve the problems of global resource waste and service delay jitter caused by incomplete topological abstraction information from the bottom layer, and has practicality and adaptability in multi-domain networking environments. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 It is a flowchart of a routing optimization method for an optical communication network according to the present invention;

[0051] Figure 2 It is a schematic structural diagram of a routing optimization system for an optical communication network according to the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0052] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0053] Embodiment 1: Figure 1 A routing optimization method for an optical communication network according to the present invention is given, which includes the following steps:

[0054] S1. Obtain the inter-domain topology abstraction information of the cross-domain optical network, where the inter-domain topology abstraction information includes the boundary node identifiers of each sub-domain and the link resource data between the boundary nodes;

[0055] S2. Generate intra-domain topology compensation parameters for each sub-domain based on the boundary node identifiers, where the intra-domain topology compensation parameters are used to characterize the potential path resource consumption between the boundary nodes inside the sub-domain;

[0056] S3. Dynamically monitor the implicit link competition relationships of cross-domain optical paths shared within each sub-domain according to the in-domain topology compensation parameters and link resource data, and generate competition intensity indicators.

[0057] S4. Evaluate the port resource consumption weights of the boundary nodes of each sub-domain based on the in-domain topology compensation parameters and competition intensity indicators.

[0058] S5. Generate the optimal port selection weights of candidate cross-domain optical paths by combining the port resource consumption weights and link resource data.

[0059] S6. Screen the global routing paths according to the optimal port selection weights and trigger the port selection instructions of the optical switching nodes to establish cross-domain optical paths.

[0060] S1. Obtain the inter-domain topology abstraction information of the cross-domain optical network. The inter-domain topology abstraction information includes the boundary node identifiers of each sub-domain and the link resource data between the boundary nodes, including:

[0061] Obtain the boundary node identifiers of each sub-domain through the network management system of the multi-domain optical network. The boundary node identifiers include the mapping relationship between the physical port numbers and logical addresses of the boundary nodes.

[0062] Collect the link resource data between the boundary nodes based on the software-defined network controller. The link resource data includes the available bandwidth value and the current load ratio of each link.

[0063] Associate and store the boundary node identifiers and link resource data as inter-domain topology abstraction information, and dynamically refresh the associated storage result according to the update period of the link resource data.

[0064] Read the boundary node identifiers of each sub-domain through the network management system of the multi-domain optical network using a preset protocol interface. The process of obtaining the boundary node identifiers includes: extracting the physical port numbers of the boundary nodes from the optical network management database of each sub-domain. The physical port number is the unique number of the physical port actually connected to the optical switch; at the same time, synchronously obtain the logical address mapping relationship of the boundary nodes from the routing control unit of the sub-domain. The logical address mapping relationship is the logical routing identifier of the boundary node in the cross-domain optical network, which is bound to the physical port number one by one. For example, the physical port number of a boundary node in a certain sub-domain is OXC-1-Port-3, and its logical address mapping relationship is 192.168.1.3:1001, indicating the addressing identifier of this port in the cross-domain logical topology.

[0065] The binding relationship between the above physical port number and logical address mapping relationship is automatically synchronized by the network management system through a standard network management protocol (such as SNMP or NETCONF) and stored in the local database.

[0066] Periodically collect link resource data between boundary nodes based on the southbound interface communication between the software-defined network controller and each sub-domain boundary node. The process of collecting link resource data includes: sending a link status query instruction to the boundary node through the southbound interface of the software-defined network controller to obtain the available bandwidth value of each link. The available bandwidth value is the total link bandwidth minus the bandwidth occupied by the currently allocated services; at the same time, collect the current load ratio of the link. The current load ratio is the ratio of the real-time transmission traffic of the link to the available bandwidth value. For example, if the total bandwidth of a link between two boundary nodes is 100 Gbps and the bandwidth occupied by the allocated services is 40 Gbps, the available bandwidth value is 60 Gbps; if the current real-time transmission traffic is 30 Gbps, the current load ratio is 50%.

[0067] The above link resource data is summarized to the central control node through the northbound interface of the software-defined network controller and cached in the temporary storage area in the format marked with a timestamp.

[0068] Match and store the boundary node identifier and the link resource data according to the preset association rules to generate the inter-domain topology abstraction information. The process of matching and storing includes: using the logical address mapping relationship of the boundary node as the primary key, associating the physical port number, the available bandwidth value of the link, and the current load ratio corresponding to the same logical address mapping relationship into a topology record; at the same time, dynamically refresh the associated storage result according to the update period of the link resource data. The update period is adaptively adjusted by the software-defined network controller according to the network state change frequency. For example, when it is detected that the current load ratio of a certain link fluctuates by more than 10% in three consecutive collection periods, shorten the update period of this link to 1 / 2 of the original period to ensure the real-time nature of the topology abstraction information.

[0069] During the dynamic refresh process, if it is detected that the available bandwidth value of a certain link is lower than the preset threshold (such as 10% of the total bandwidth), send a warning signal to the network management system to trigger manual intervention for verification.

[0070] S2. Generate the intra-domain topology compensation parameters for each sub-domain based on the boundary node identifier. The intra-domain topology compensation parameters are used to characterize the potential path resource consumption between the boundary nodes within the sub-domain, including:

[0071] Extract the position distribution characteristics of adjacent boundary nodes in the set of boundary nodes of each sub-domain based on the boundary node identifier. The position distribution characteristics include the distance and connection density between adjacent boundary nodes;

[0072] Calculate the number of hops and the path length of the potential paths between the boundary nodes within each sub-domain according to the position distribution characteristics. The number of hops and the path length are generated through the preset path derivation rules;

[0073] Map the hop count and path length to the intra-domain topology compensation parameter, and store the intra-domain topology compensation parameter associatively to the boundary node identifier of the corresponding sub-domain.

[0074] Based on the boundary node identifiers obtained in step S1, extract the position distribution characteristics of adjacent boundary nodes in each sub-domain boundary node set. The extraction process of the position distribution characteristics of adjacent boundary nodes includes: First, calculate the physical distance between adjacent boundary nodes according to the optical switch physical location information corresponding to the physical port numbers of the boundary nodes. The physical distance is the actual length of the optical cable between the two nodes. Second, count the connection density between adjacent boundary nodes. The connection density is the number of fiber optic links shared between the same pair of adjacent boundary nodes. For example, if the physical distance between boundary node X and boundary node Y in sub-domain A is 50 kilometers and they are connected by two independent fiber optic links, then the connection density is 2.

[0075] The physical distance and connection density data are read from the optical cable resource database of the network management system, and their accuracy is verified in real time through the southbound interface of the software-defined network controller.

[0076] Calculate the hop count and path length of the potential paths between the internal boundary nodes of each sub-domain according to the extracted position distribution characteristics. The calculation process of the hop count and path length includes: Based on the preset path derivation rule, under the constraint that the intra-domain topology is invisible, assume that the shortest path between adjacent boundary nodes is the default path, and deduce the hop count of the potential path according to the physical distance and connection density. The hop count is the number of intermediate nodes passed by the shortest path between adjacent boundary nodes plus 1; the path length is the product of the physical distance between adjacent boundary nodes and the hop count. For example, if the physical distance between boundary node X and Y is 50 kilometers and it is deduced that the shortest path needs to pass through 3 intermediate nodes, then the hop count is 4 and the path length is 50 kilometers × 4 = 200 kilometers.

[0077] The preset path derivation rule adopts the shortest path principle, specifically to preferentially select the link with a high connection density between adjacent boundary nodes as the basis for path derivation to reduce the risk of path interruption.

[0078] Map the hop count and path length to the intra-domain topology compensation parameter, and store this parameter associatively to the boundary node identifier of the corresponding sub-domain. The mapping process includes: Set weight coefficients for the hop count and path length respectively. For example, the hop count weight coefficient is set to 0.6 and the path length weight coefficient is set to 0.4. Weighted sum the hop count and path length according to the weight coefficients to obtain the intra-domain topology compensation parameter. For example, if the hop count of a pair of boundary nodes is 4 and the path length is 200 kilometers, then the intra-domain topology compensation parameter is 4 × 0.6 + 200 × 0.4 = 82.4.

[0079] The setting basis of the weight coefficient is the statistical result of historical transmission data, in which the influence of the number of hops on resource consumption accounts for 60%, and the path length accounts for 40%. The associated storage process binds the logical address mapping relationship between the intra-domain topology compensation parameter and the boundary node identifier and stores it in the topology database of the network management system. The storage format is a relational data table in which the logical address mapping relationship and the compensation parameter correspond one by one.

[0080] S3. Dynamically monitor the implicit link competition relationship of cross-domain optical path sharing within each sub-domain according to the intra-domain topology compensation parameter and the link resource data, and generate a competition intensity index, including:

[0081] Locate the shared physical links within each sub-domain that are shared by multiple cross-domain optical paths according to the path length and the number of hops in the intra-domain topology compensation parameter. The shared physical links are determined by reverse derivation based on the logical address mapping relationship in the boundary node identifier;

[0082] Based on the current load ratio in the link resource data, count the number of real-time cross-domain optical paths of the shared physical link, and calculate the dynamic resource fluctuation threshold of the shared physical link in combination with the path length in the intra-domain topology compensation parameter;

[0083] Generate a first competition factor according to the difference ratio between the number of real-time cross-domain optical paths and the dynamic resource fluctuation threshold, and generate a second competition factor according to the ratio of the path length to the number of hops;

[0084] If the first competition factor exceeds the preset alarm threshold, directly use the first competition factor as the competition intensity index; if not, generate the competition intensity index according to the mapping relationship between the second competition factor and the sub-domain type, and associate the competition intensity index with the boundary node identifier of the corresponding physical link.

[0085] Locate the shared physical links within each sub-domain that are shared by multiple cross-domain optical paths according to the path length and the number of hops in the intra-domain topology compensation parameter. The positioning process of the shared physical link includes: based on the logical address mapping relationship in the boundary node identifier, reverse query the physical port number corresponding to the logical address mapping relationship, and deduce the physical link within the sub-domain that may be shared by multiple cross-domain optical paths in combination with the path length and the number of hops. For example, the logical address mapping relationship of boundary node X is 192.168.1.3:1001, and the corresponding physical port number is OXC-1-Port-3. If the path length associated with this port is 200 kilometers and the number of hops is 4, it is inferred that there is a physical link within the sub-domain starting from OXC-1-Port-3, passing through 3 intermediate nodes, and with a length of 200 kilometers. This link may be shared by multiple cross-domain optical paths. The above derivation process is implemented by querying the optical cable connection topology table of the network management system, and the optical cable connection topology table stores the connection relationship between physical ports and the optical cable length data.

[0086] Based on the current load ratio in the link resource data, count the real-time cross-domain optical path quantity of the shared physical link, and calculate the dynamic resource fluctuation threshold of the shared physical link in combination with the path length in the intra-domain topology compensation parameter. The calculation process of the dynamic resource fluctuation threshold includes: setting a basic fluctuation threshold according to the path length, the longer the path length, the lower the basic fluctuation threshold; then adjusting the basic fluctuation threshold according to the current load ratio to generate the dynamic resource fluctuation threshold. For example, for a shared physical link with a path length of 200 kilometers, the basic fluctuation threshold is set to 5 cross-domain optical paths; if the current load ratio is 60%, then the dynamic resource fluctuation threshold is adjusted to 5×(1 - 60%) = 2. The adjustment formula is reflected as the dynamic resource fluctuation threshold = basic fluctuation threshold × (1 - current load ratio).

[0087] Generate a first competition factor according to the difference ratio between the real-time cross-domain optical path quantity and the dynamic resource fluctuation threshold. The calculation process of the difference ratio includes: when the real-time cross-domain optical path quantity is greater than the dynamic resource fluctuation threshold, the difference ratio is (real-time quantity - threshold) / threshold; when the real-time quantity is less than or equal to the threshold, the difference ratio is 0. For example, for a shared physical link with a dynamic resource fluctuation threshold of 2 and a real-time cross-domain optical path quantity of 3, the difference ratio is (3 - 2) / 2 = 50%.

[0088] At the same time, generate a second competition factor according to the ratio of the path length to the number of hops in the intra-domain topology compensation parameter. The ratio of the path length to the number of hops reflects the average path consumption per hop, and the higher the ratio, the lower the resource consumption efficiency. For example, for a path length of 200 kilometers and 4 hops, the ratio is 50 kilometers / hop. If another link has a path length of 150 kilometers and 5 hops, the ratio is 30 kilometers / hop. The former has a lower resource consumption efficiency and a higher second competition factor.

[0089] If the first competition factor exceeds the preset alarm threshold, directly use the first competition factor as the competition intensity index. The preset alarm threshold is set according to the statistics of historical network congestion events. For example, when the difference ratio exceeds 30%, it is determined as a high competition risk, and the alarm threshold is set to 30%. If the first competition factor does not exceed the alarm threshold, generate the competition intensity index according to the mapping relationship between the second competition factor and the sub-domain type. The mapping relationship of the sub-domain type is defined in the network planning stage. For example, the core sub-domain is more sensitive to the resource consumption efficiency. When the second competition factor is greater than or equal to 40 kilometers / hop, the competition intensity index = second competition factor × 2; the edge sub-domain is less sensitive, and the competition intensity index = second competition factor × 1.

[0090] The generated competition intensity index is associated with the boundary node identifier of the corresponding physical link through the logical address mapping relationship and stored in the competition monitoring database of the network management system for subsequent call in the evaluation of the port resource consumption weight.

[0091] S4. Evaluate the port resource consumption weights of the boundary nodes of each sub-domain based on the intra-domain topology compensation parameters and the competition intensity index, including:

[0092] Generate the initial resource consumption weights of each boundary node based on the path length and hop count in the intra-domain topology compensation parameters. The initial resource consumption weight is a linear combination of the path length and hop count.

[0093] Adjust the initial resource consumption weights according to the type of the competition intensity index. If the competition intensity index is the first competition factor, adjust it by increasing the amplitude according to the difference ratio. If it is the second competition factor, adjust it according to the preset coefficient of the sub-domain type.

[0094] Normalize the adjusted initial resource consumption weights into port resource consumption weights and bind and store them with the logical address mapping relationship in the boundary node identifier.

[0095] When evaluating the port resource consumption weights of the boundary nodes of each sub-domain based on the intra-domain topology compensation parameters and the competition intensity index, the specific operation process is as follows: Generate the initial resource consumption weights of each boundary node based on the path length and hop count in the intra-domain topology compensation parameters. The generation process of the initial resource consumption weight includes: Set the weight coefficients for the path length and hop count respectively. The weight coefficient of the path length is 0.7, and the weight coefficient of the hop count is 0.3. Calculate the initial resource consumption weight by linearly combining the path length and hop count according to the weight coefficients. For example, if the path length of a boundary node is 200 kilometers and the hop count is 4, the initial resource consumption weight is 200×0.7 + 4×0.3 = 140 + 1.2 = 141.2.

[0096] The setting basis of the weight coefficients is the analysis result of historical transmission data. For example, the influence proportion of the path length on resource consumption is 70%, and the hop count is 30%.

[0097] Adjust the initial resource consumption weights according to the type of the competition intensity index. If the competition intensity index is the first competition factor (difference ratio), the adjustment process includes: Adjust the initial resource consumption weight by increasing the amplitude according to the difference ratio, and the increase ratio is 50% of the difference ratio. For example, if the initial weight is 141.2 and the difference ratio is 30%, the adjusted weight is 141.2×(1 + 30%×50%) = 141.2×1.15 = 162.38. If the competition intensity index is the second competition factor (ratio of path length to hop count), the adjustment process includes: Adjust the initial weight according to the preset coefficient of the sub-domain type. The preset coefficient is defined in the network planning stage. For example, the adjustment coefficient of the core sub-domain is 1.5, and that of the edge sub-domain is 1.2. For example, if the second competition factor of an edge sub-domain is 30 kilometers / hop and the initial weight is 141.2, the adjusted weight is 141.2×1.2 = 169.44.

[0098] Normalize the adjusted initial resource consumption weights into port resource consumption weights and bind them to the logical address mapping relationship in the border node identification for storage. The normalization process includes: calculating the maximum and minimum values of the adjusted weights of all border nodes, and mapping each weight to the 0-1 interval according to the formula (weight - minimum value) / (maximum value - minimum value). For example, if the adjusted weight range of a batch of border nodes is 100-200, the normalized result corresponding to the weight of 150 is (150 - 100) / (200 - 100) = 0.5. The normalized port resource consumption weights are bound to the corresponding border nodes through the logical address mapping relationship and stored in the resource weight database of the network management system in the form of key-value pairs of the logical address mapping relationship and the normalized weights. The above database interacts with the software-defined network controller through a standard interface to support real-time invocation for subsequent optimal port selection weight calculation.

[0099] S5. Generate the optimal port selection weight for the candidate cross-domain optical path by combining the port resource consumption weight and the link resource data, including:

[0100] Divide the links of the candidate cross-domain optical path into high-bandwidth links, medium-bandwidth links, and low-bandwidth links according to the available bandwidth values in the link resource data, and set initial port selection weight coefficients for each type of link;

[0101] Calculate the initial port selection weight of the candidate cross-domain optical path based on the port resource consumption weight and the current load ratio in the link resource data. The initial port selection weight is the product of the port resource consumption weight and the reciprocal of the current load ratio;

[0102] Dynamically adjust the initial port selection weight according to the initial port selection weight coefficient corresponding to the link type to generate the optimal port selection weight, and associate the optimal port selection weight with the logical address mapping relationship of the candidate cross-domain optical path.

[0103] When generating the optimal port selection weight for the candidate cross-domain optical path by combining the port resource consumption weight and the link resource data, it specifically includes the following operation process: Divide the links of the candidate cross-domain optical path into high-bandwidth links, medium-bandwidth links, and low-bandwidth links according to the available bandwidth values in the link resource data.

[0104] The link division rules are as follows: If the available bandwidth value is greater than or equal to the preset high bandwidth threshold (e.g., 100 Gbps), it is marked as a high bandwidth link; if the available bandwidth value is between the preset medium bandwidth threshold (e.g., 50 Gbps) and the high bandwidth threshold, it is marked as a medium bandwidth link; if the available bandwidth value is lower than the medium bandwidth threshold, it is marked as a low bandwidth link. The preset thresholds are set according to the statistical data of historical transmission during the network planning phase. For example, the high bandwidth threshold is set to 80% of the historical peak bandwidth. An initial port selection weight coefficient is set for each type of link. The initial port selection weight coefficient for high bandwidth links is 1.5, for medium bandwidth links is 1.2, and for low bandwidth links is 1.0.

[0105] When calculating the initial port selection weight of a candidate cross-domain optical path based on the port resource consumption weight and the current load ratio in the link resource data, the calculation process of the initial port selection weight includes: multiplying the port resource consumption weight by the reciprocal of the current load ratio. The reciprocal of the current load ratio reflects the degree of light loading of the link. For example, if the port resource consumption weight of a candidate cross-domain optical path is 0.8 (normalized value) and the current load ratio is 20%, then the reciprocal of the current load ratio is 5 (1 / 20%), and the initial port selection weight is 0.8 × 5 = 4.0. If the current load ratio is 50%, the reciprocal is 2, and the initial port selection weight is 0.8 × 2 = 1.6.

[0106] When dynamically adjusting the initial port selection weight according to the initial port selection weight coefficient corresponding to the link type to generate the optimal port selection weight, the dynamic adjustment process includes: multiplying the initial port selection weight by the initial port selection weight coefficient corresponding to the link type. For example, if the initial port selection weight of a high bandwidth link is 4.0, multiplying it by the coefficient 1.5 gives the optimal port selection weight of 6.0; the initial weight of a medium bandwidth link is 1.6, multiplying it by the coefficient 1.2 gives 1.92; the initial weight of a low bandwidth link is 1.0, and multiplying it by the coefficient 1.0 keeps it at 1.0.

[0107] The generated optimal port selection weight is bound to the candidate cross-domain optical path through the logical address mapping relationship and stored in the path priority database of the network management system. The storage format is a key-value pair of the logical address mapping relationship and the optimal port selection weight. The above database interacts with the control unit of the optical switching node through a standard interface to support subsequent path screening and real-time invocation of port instructions.

[0108] S6. Screening the global routing path according to the optimal port selection weight and triggering the port selection instruction of the optical switching node to establish a cross-domain optical path, including:

[0109] Group the global routing paths according to the priority of the optimal port selection weight. The priority grouping rule is to divide the paths with the optimal port selection weight higher than the preset load fluctuation threshold into the high priority group, and the rest into the low priority group;

[0110] Dynamically adjust the path ratio between the high-priority group and the low-priority group based on the current load ratio in the link resource data. If the current load ratio exceeds the preset load fluctuation threshold, reduce the number of paths in the high-priority group.

[0111] Trigger the port selection instruction of the optical switching node according to the adjusted path grouping result. The port selection instruction includes the logical address mapping relationship and port number of the high-priority group path to establish a cross-domain optical path.

[0112] Perform priority grouping on the global routing paths according to the optimal port selection weight. The priority grouping rule is to divide the paths with an optimal port selection weight higher than the preset load fluctuation threshold into the high-priority group, and the remaining paths into the low-priority group. The preset load fluctuation threshold is set according to the statistical data of historical network load. For example, take 1.2 times the average value of the optimal port selection weights of all candidate paths as the threshold. If the optimal port selection weight of a certain path is 6.0 and the average value is 5.0, the threshold is set to 6.0, and this path is divided into the high-priority group; if the weight of another path is 4.0, it is classified into the low-priority group.

[0113] Dynamically adjust the path ratio between the high-priority group and the low-priority group based on the current load ratio in the link resource data. If the current load ratio exceeds the preset load fluctuation threshold (e.g., 60%), reduce the number of paths in the high-priority group. The adjustment ratio is that the number of paths in the high-priority group is reduced by 20%, and at the same time, the number of paths in the low-priority group is increased by 20%. For example, if the original high-priority group contains 10 paths and the low-priority group contains 5 paths, after adjustment, the high-priority group retains 8 paths and the low-priority group increases to 7 paths. If the current load ratio does not exceed the threshold, maintain the original grouping ratio.

[0114] The preset load fluctuation threshold is set by the network administrator according to the network capacity planning experience. For example, the load threshold for the core sub-domain is set to 60%, and the edge sub-domain is set to 50%.

[0115] Trigger the port selection instruction of the optical switching node according to the adjusted path grouping result. The generation process of the port selection instruction includes: extracting the logical address mapping relationship and port number of the high-priority group path, and encapsulating the logical address mapping relationship and port number into a control signaling according to the preset instruction format.

[0116] For example, if the logical address mapping relationship of the high-priority group path is 192.168.1.3:1001, and the corresponding physical port number is OXC-1-Port-3, then the generated instruction format is {"logical address": "192.168.1.3:1001", "port number": "OXC-1-Port-3", "operation": "establish"}.

[0117] The above instructions are sent to the optical switching node through the southbound interface (such as the OpenFlow protocol) of the software-defined network controller, driving the optical switch to perform port cross-connection operations to establish a cross-domain optical path. The status of the established cross-domain optical path is synchronized to the topology database of the network management system through the northbound interface for real-time call in subsequent routing optimization.

[0118] Embodiment 2: Figure 2 A schematic structural diagram of an optical communication network routing optimization system according to the present invention is given. An optical communication network routing optimization system includes:

[0119] Topology data acquisition module: Obtain the inter-domain topology abstraction information of the cross-domain optical network. The inter-domain topology abstraction information includes the boundary node identifiers of each sub-domain and the link resource data between the boundary nodes;

[0120] Compensation parameter generation module: Generate the intra-domain topology compensation parameters of each sub-domain based on the boundary node identifiers. The intra-domain topology compensation parameters are used to characterize the potential path resource consumption between the internal boundary nodes of the sub-domain;

[0121] Implicit competition monitoring module: Dynamically monitor the implicit link competition relationship shared by the cross-domain optical paths within each sub-domain according to the intra-domain topology compensation parameters and the link resource data, and generate a competition intensity index;

[0122] Port weight evaluation module: Evaluate the port resource consumption weights of the boundary nodes of each sub-domain based on the intra-domain topology compensation parameters and the competition intensity index;

[0123] Optimal weight generation module: Combine the port resource consumption weights and the link resource data to generate the optimal port selection weights of the candidate cross-domain optical paths;

[0124] Optical path trigger execution module: Screen the global routing path according to the optimal port selection weights and trigger the port selection instructions of the optical switching node to establish a cross-domain optical path.

[0125] The above embodiments can be implemented in whole or in part by software, hardware, firmware, or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product.

[0126] Those of ordinary skill in the art can realize that the modules and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application of the technical solution and the invention constraints. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0127] In addition, in each embodiment of the present application, each functional module may be integrated into a processing module, may exist separately as individual physical modules, or two or more modules may be integrated into one module.

[0128] As mentioned above, the above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

[0129] Finally: The above are only the preferred embodiments of the present invention and are not used to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the present invention should all be included within the protection scope of the present invention.

Claims

1. A method for optimizing routing in an optical communication network, characterized in that: The steps include: S1. Obtaining inter-domain topology abstract information of the cross-domain optical network, where the inter-domain topology abstract information includes boundary node identifiers of each sub-domain and link resource data between boundary nodes; S2. Generate intra-domain topology compensation parameters for each sub-domain based on the boundary node identifier, where the intra-domain topology compensation parameters are used to characterize the potential path resource consumption between boundary nodes within the sub-domain; Generate intra-domain topology compensation parameters for each subdomain based on the boundary node identifier, including: Extracting the position distribution features of adjacent boundary nodes in each subdomain boundary node set based on boundary node identifiers, the position distribution features include the distance and connection density of adjacent boundary nodes; The number of hops and path length of potential paths between boundary nodes within each subdomain are calculated according to the location distribution characteristics. The number of hops and path length are generated by a preset path derivation rule, which adopts the shortest path principle. Mapping the number of hops and the path length into intra-domain topology compensation parameters, and associating and storing the intra-domain topology compensation parameters with the boundary node identifiers of the corresponding sub-domains; S3. Dynamically monitor the implicit link competition relationship of cross-domain optical path sharing within each subdomain based on the intra-domain topology compensation parameters and link resource data, and generate competition intensity indicators, including: Locate the shared physical links in each subdomain that are shared by multiple cross-domain optical paths based on the path length and hop count in the intra-domain topology compensation parameters; Based on the current load ratio in the link resource data, the number of real-time cross-domain optical paths of the shared physical link is counted, and the dynamic resource fluctuation threshold of the shared physical link is calculated in combination with the path length in the intra-domain topology compensation parameter. The dynamic resource fluctuation threshold = basic fluctuation threshold × (1-current load ratio); the basic fluctuation threshold is the number of cross-domain optical paths; A first competition factor is generated according to a difference ratio between the number of real-time cross-domain optical paths and a dynamic resource fluctuation threshold, wherein the difference ratio calculation process includes: (real-time number - threshold) / threshold, and a second competition factor is generated according to a ratio of a path length to a hop number; If the first competition factor exceeds the preset alarm threshold, the first competition factor is directly used as the competition intensity index; if it does not exceed, the competition intensity index is generated according to the mapping relationship between the second competition factor and the subdomain type, and the competition intensity index is associated with the boundary node identifier of the corresponding physical link; S4, evaluating the port resource consumption weight of each sub-domain boundary node based on the intra-domain topology compensation parameter and the competition intensity index; S5, combining the port resource consumption weight and the link resource data to generate the optimal port selection weight of the candidate cross-domain optical path; S6. Filter the global routing path according to the optimal port selection weight and trigger the port selection instruction of the optical switching node to establish a cross-domain optical path.

2. The optical communication network routing optimization method according to claim 1, characterized in that: Obtain inter-domain topology abstract information of cross-domain optical networks, including: Obtaining a boundary node identifier of each subdomain through a network management system of the multi-domain optical network, wherein the boundary node identifier includes a mapping relationship between a physical port number and a logical address of the boundary node; The link resource data between the boundary nodes is collected based on the software-defined network controller. The link resource data includes the available bandwidth value and current load ratio of each link. The boundary node identifier and the link resource data are associated and stored as inter-domain topology abstract information, and the associated storage result is dynamically refreshed according to the update cycle of the link resource data.

3. The optical communication network route optimization method according to claim 1, characterized in that: The shared physical link is determined by reverse deduction of the logical address mapping relationship in the boundary node identifier.

4. The optical communication network route optimization method according to claim 1, characterized in that: The port resource consumption weight of each subdomain boundary node is evaluated based on the intra-domain topology compensation parameters and competition intensity index, including: The initial resource consumption weight of each boundary node is generated based on the path length and hop count in the domain topology compensation parameters. The initial resource consumption weight is a linear combination of the path length and the hop count. The initial resource consumption weight is adjusted according to the type of competition intensity indicator. If the competition intensity indicator is the first competition factor, it is adjusted according to the difference ratio increase; if it is the second competition factor, it is adjusted according to the preset coefficient of the subdomain type; The adjusted initial resource consumption weight is normalized into the port resource consumption weight, and is bound and stored with the logical address mapping relationship in the boundary node identifier.

5. The optical communication network route optimization method according to claim 1, characterized in that: The optimal port selection weights of candidate cross-domain optical paths are generated by combining the port resource consumption weights with the link resource data, including: Divide the links of the candidate cross-domain optical paths according to the available bandwidth values ​​in the link resource data, and set the initial port selection weight coefficient for each type of link; Calculate the initial port selection weight of the candidate cross-domain optical path based on the port resource consumption weight and the current load proportion in the link resource data; The initial port selection weight is dynamically adjusted according to the initial port selection weight coefficient corresponding to the link type to generate the optimal port selection weight, and the optimal port selection weight is associated with the logical address mapping relationship of the candidate cross-domain optical path.

6. The optical communication network route optimization method according to claim 5, characterized in that: The links of candidate cross-domain optical paths are divided into high-bandwidth links, medium-bandwidth links and low-bandwidth links; the initial port selection weight is the inverse product of the port resource consumption weight and the current load ratio.

7. The optical communication network route optimization method according to claim 1, characterized in that: The global routing path is screened according to the optimal port selection weight and the port selection instruction of the optical switching node is triggered to establish a cross-domain optical path, including: The global routing paths are prioritized and grouped according to the optimal port selection weight. The priority grouping rule is to group the paths whose optimal port selection weight is higher than the preset load fluctuation threshold into a high priority group, and the rest into a low priority group. Dynamically adjust the path ratio of the high priority group and the low priority group based on the current load ratio in the link resource data. If the current load ratio exceeds the preset load fluctuation threshold, reduce the number of paths in the high priority group. The port selection instruction of the optical switching node is triggered according to the adjusted path grouping result, and the port selection instruction includes the logical address mapping relationship and the port number of the high priority group path to establish a cross-domain optical path.

8. An optical communication network route optimization system, used to implement an optical communication network route optimization method according to any one of claims 1 to 7, characterized in that: include: Topology data acquisition module: obtains inter-domain topology abstract information of the cross-domain optical network, which includes the boundary node identifiers of each sub-domain and the link resource data between the boundary nodes; Compensation parameter generation module: Generates intra-domain topology compensation parameters for each sub-domain based on boundary node identifiers. The intra-domain topology compensation parameters are used to characterize the potential path resource consumption between boundary nodes within the sub-domain. Implicit competition monitoring module: dynamically monitors the implicit link competition relationship of cross-domain optical path sharing within each subdomain based on the intra-domain topology compensation parameters and link resource data, and generates competition intensity indicators; Port weight evaluation module: evaluates the port resource consumption weight of each sub-domain boundary node based on the intra-domain topology compensation parameter and competition intensity index; Optimal weight generation module: combines the port resource consumption weight and link resource data to generate the optimal port selection weight of the candidate cross-domain optical path; Lightpath trigger execution module: Filters the global routing path according to the optimal port selection weight and triggers the port selection instruction of the optical switching node to establish a cross-domain lightpath.

Images