Route configuration method and device, network equipment, and storage medium

Abstract

The present disclosure relates to the technical field of optical transport network management, in particular to a routing configuration method and device, a network device, and a storage medium. The method comprises: determining an optical data unit (ODU) service associated with a fault link; determining routing recovery signal level information corresponding to the ODU service and a customer layer service carried by the ODU service based on a service bearer relationship corresponding to the ODU service; and performing service routing planning based on the routing recovery signal level information. The present scheme can replace only the failed route locally, thereby improving the recovery speed of service protection capability.

Description

Technical Field

[0001] This disclosure relates to the field of optical transmission network management technology, specifically to a routing configuration method, a routing configuration device, a network device, and a storage medium. Background Technology

[0002] In the network architecture of OTN (Optical Transport Network), a single OCH (Optical Channel layer) / OTU (Optical Channel Transport Unit) optical channel can carry multiple ODU (Optical Data Unit) pipelines. By overlaying SDH (Synchronous Digital Hierarchy), OSU (Optical Service Unit), or PKT (Packet Switching) technologies on the ODU transmission technology, the ODU pipeline can be split into smaller bearer units to carry services with bandwidth less than 1Gbps, such as government and enterprise services.

[0003] In OTN networks, segmented protection technology is typically used to ensure service reliability. Segmented protection can withstand a single network failure, but the failure of the working or protection entity will result in the loss of protection capability. For fiber optic interruptions caused by network topology adjustments, line faults, etc., it is difficult to repair in a short time. In this case, a secondary fault within the protected segment will cause service interruption.

[0004] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0005] The purpose of this disclosure is to provide a routing configuration method, a routing configuration device, a network device, and a storage medium that can perform partial route replacement in the event of a network failure.

[0006] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.

[0007] According to a first aspect of this disclosure, a routing configuration method is provided, the method comprising:

[0008] Identify the optical data unit (ODU) services associated with the faulty link; based on the service bearer relationship corresponding to the ODU services, determine the routing recovery signal hierarchy information corresponding to the ODU services and the customer layer services carried by the ODU services;

[0009] Based on the route recovery signal hierarchy information, service route planning is performed.

[0010] In an exemplary embodiment of this disclosure, determining the routing recovery signal hierarchy information corresponding to the ODU service and the customer-layer service carried by the ODU service based on the service bearer relationship corresponding to the ODU service includes:

[0011] Obtain the current layer service information of the ODU service, determine whether a protection service exists; and if a protection service exists, configure the layer information of the protection service or the layer information of the corresponding associated configuration layer as the routing recovery signal layer information; or,

[0012] When it is determined that there is no protected service based on the service information of this layer, the service bearer relationship corresponding to the ODU service is traversed layer by layer to determine the routing recovery signal layer information.

[0013] In one exemplary embodiment of this disclosure, the method further includes:

[0014] Obtain the bandwidth utilization information corresponding to the service bearer relationship of the ODU service. If the bandwidth utilization information is greater than or equal to a preset passthrough threshold, then determine that the restored signal layer information is the ODU service layer; or,

[0015] If the bandwidth utilization information is less than the preset passthrough threshold, then the local layer service information of the ODU service is obtained.

[0016] In one exemplary embodiment of this disclosure, the step of performing service routing planning based on the routing recovery signal hierarchy information includes:

[0017] Based on the route recovery signal hierarchy information, the faulty link is avoided, and service routing is planned for the route recovery signal hierarchy;

[0018] Obtain the service layer path reuse information corresponding to the service route. If all service layer paths reuse existing paths, then perform path changes according to the service route planned after restoring the signal hierarchy based on the route; or,

[0019] If the service layer path does not fully reuse existing paths, then the faulty link is avoided and business routing is planned for the service layer.

[0020] In one exemplary embodiment of this disclosure, the method further includes:

[0021] When planning service layer service routes, if intermediate network elements exist, the service layer service terminates and splits at the intermediate network element; the route recovery signal layer service crosses and continues at the intermediate network element; or...

[0022] If no intermediate network element exists, the service layer services will plan their routes using a pipe-through method.

[0023] In one exemplary embodiment of this disclosure, the method further includes:

[0024] Configure the corresponding route recovery signal level based on the protection type of each protection level in the service bearer relationship.

[0025] In one exemplary embodiment of this disclosure, the method further includes:

[0026] Listen for network topology change notifications and collect the corresponding network topology information;

[0027] Based on the network topology change notification, a service routing change event is triggered to perform service routing planning.

[0028] According to a second aspect of this disclosure, a routing configuration apparatus is provided, comprising:

[0029] The bearer relationship analysis module is used to determine the optical data unit (ODU) services associated with the faulty link; based on the service bearer relationship corresponding to the ODU service, it determines the routing recovery signal hierarchy information corresponding to the ODU service and the customer layer services carried by the ODU service.

[0030] The routing planning module is used to plan service routes based on the routing recovery signal hierarchy information.

[0031] According to a third aspect of this disclosure, a network device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform a routing configuration method as described in any of the above embodiments by executing the executable instructions.

[0032] According to a fourth aspect of this disclosure, a storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the routing configuration method as described in any of the above embodiments.

[0033] In one embodiment of the routing configuration method disclosed herein, service bearer relationship analysis is performed on ODU services affected by a faulty link to determine the corresponding route recovery signal hierarchy information, and service routing is planned based on this information. This allows for partial replacement of only the failed routes when network failures cause routing failures, thereby improving the recovery speed of service protection capabilities. Furthermore, determining the corresponding route recovery signal hierarchy information based on service bearer relationships and planning routes accordingly effectively reduces the complexity of configuration changes. This avoids service protection capability degradation and improves service reliability.

[0034] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0035] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0036] Figure 1 This illustration schematically depicts a service bearer route in an exemplary embodiment of the present disclosure;

[0037] Figure 2 This schematic diagram illustrates a segmentation diagram of an ODU transparent transmission service leased line protection in an exemplary embodiment of the present disclosure.

[0038] Figure 3 The diagram illustrates a routing configuration method according to an exemplary embodiment of the present disclosure.

[0039] Figure 4 This illustration schematically depicts a method for analyzing route recovery signal layers based on service bearer relationships in an exemplary embodiment of this disclosure.

[0040] Figure 5 This illustration schematically depicts a routing planning method based on service bearer relationships in an exemplary embodiment of this disclosure;

[0041] Figure 6 This diagram illustrates a service layer service routing planning result without intermediate network elements in an exemplary embodiment of the present disclosure.

[0042] Figure 7 This diagram illustrates a service layer service routing planning result with intermediate network elements in an exemplary embodiment of the present disclosure.

[0043] Figure 8 This illustration schematically depicts a routing plan in a network expansion scenario according to an exemplary embodiment of this disclosure;

[0044] Figure 9 This illustration schematically depicts a routing plan under a network failure scenario in an exemplary embodiment of the present disclosure.

[0045] Figure 10 This schematic diagram illustrates a routing configuration apparatus according to an exemplary embodiment of the present disclosure;

[0046] Figure 11This schematic diagram illustrates a routing configuration apparatus according to an exemplary embodiment of the present disclosure;

[0047] Figure 12 This schematic diagram illustrates a network device according to an exemplary embodiment of the present disclosure;

[0048] Figure 13 The schematic diagram illustrates a storage medium according to an exemplary embodiment of the present disclosure. Detailed Implementation

[0049] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that this disclosure will be more comprehensive and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0050] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0051] In relevant existing technologies, taking government and enterprise OTN transmission networks as an example, refer to Figure 1 The diagram illustrates a multiplexing bearer route in an OTN transmission network. One OCH / OTU optical channel can carry multiple ODU (Optical Data Unit) pipelines. By overlaying SDH (Synchronous Digital Hierarchy), OSU (Optical Service Unit), or PKT (Packet Switching) technologies on the ODU transmission, the ODU pipeline can be split into smaller bandwidth bearer units to carry enterprise services with speeds less than 1Gbps. The minimum bandwidth of an ODU pipeline is 1250Mbps, while the common bandwidth for enterprise services is approximately 2-1000Mbps. Therefore, in an enterprise OTN transmission network, an ODU pipeline can typically carry hundreds of low-speed enterprise services. In OTN networks, to ensure service reliability, refer to... Figure 2As shown, segmented protection is typically employed. Each segment is configured with a working route and a protection route, with the working route serving as the primary route and the protection route as the backup. While protection technologies can withstand a single network failure, the failure of either the working or protection route entity will result in the loss of routing protection capabilities within the segment. Furthermore, fiber optic interruptions caused by network topology adjustments or line faults are difficult to repair quickly, and secondary faults within the protected segment can lead to service interruptions. Therefore, a rapid protection route recovery method is needed to promptly replace the failed route entity when a network failure causes the working or protection route to fail, thereby restoring service protection capabilities.

[0052] In this example implementation, to address the technical deficiencies in the prior art, a routing configuration method is first provided. (See reference...) Figure 3 As shown, it may specifically include:

[0053] Step S11: Determine the optical data unit (ODU) service associated with the faulty link; based on the service bearer relationship corresponding to the ODU service, determine the routing recovery signal hierarchy information corresponding to the ODU service and the customer layer service carried by the ODU service.

[0054] Step S12: Based on the route recovery signal hierarchy information, perform service route planning.

[0055] The routing configuration method provided in this example implementation, on the one hand, analyzes the service bearer relationship of ODU services affected by faulty links to determine the corresponding route recovery signal hierarchy information, and plans service routes based on this information. This allows for partial replacement of only the failed routes when network failures cause route failures, thereby improving the recovery speed of service protection capabilities. On the other hand, determining the corresponding route recovery signal hierarchy information based on service bearer relationships and planning routes accordingly effectively reduces the complexity of configuration changes. This avoids service protection capability degradation and improves service reliability.

[0056] The following will describe in more detail each step of the routing configuration method in this example embodiment, with reference to the accompanying drawings and embodiments.

[0057] In this example implementation, the method described above may include:

[0058] Step S101: Listen for network topology change notifications and collect the corresponding network topology information;

[0059] Step S102: Based on the network topology change notification, trigger a service routing change event to perform service routing planning.

[0060] In this example implementation, the method described above can be applied to a network device or a server. For instance, taking a network device as an example, the network device described above can be as follows: Figure 2 The network architecture shown illustrates a gateway device. Specifically, a topology management module can be provided on the network device for network element and link management. This module can also monitor physical network topology changes and abstract the collected raw network topology data into a unified model. It maintains network element, port, and link data, and synchronizes information such as topology changes, port alarms, and signal defects in real time. For example, when it detects network topology change notifications corresponding to physical facility changes such as physical port alarms, link faults, and optical fiber adjustment information, it can collect the corresponding network topology information in real time, trigger a service routing change event, execute the event, identify the faulty link and the ODU services affected by the faulty link, and perform service routing planning.

[0061] In step S11, the optical data unit (ODU) service associated with the faulty link is determined; based on the service bearer relationship corresponding to the ODU service, the routing recovery signal hierarchy information corresponding to the ODU service and the customer layer service carried by the ODU service is determined.

[0062] In this example implementation, the ODU services affected by the faulty fiber optic link can be identified first. Then, the ODU services are traversed, and a service bearer relationship analysis is performed for each ODU service to determine the corresponding service bearer tree. Here, the service bearer tree refers to the set of services obtained by following the bearer relationship with a specific ODU service as the root. The aforementioned route recovery signal layer can refer to the layer in the service bearer tree that maintains the same start and end points and the same number of services in its customer layer. After a network failure, the services at this layer update their routes promptly for the failed entities in the protection group, thus restoring protection capabilities.

[0063] In this example implementation, when determining the routing recovery signal layer information corresponding to the ODU service and the customer layer service carried by the ODU service, the above method may further include:

[0064] Step S201: Obtain the bandwidth utilization information corresponding to the service bearer relationship of the ODU service. If the bandwidth utilization information is greater than or equal to a preset passthrough threshold, then determine that the restored signal layer information is the ODU service layer; or,

[0065] Step S202: If the bandwidth utilization information is less than a preset passthrough threshold, then obtain the local layer service information of the ODU service.

[0066] In this example embodiment, step S11 above may specifically include:

[0067] Step S21: Obtain the current layer service information of the ODU service, determine whether a protection service exists; and if a protection service exists, configure the layer information of the protection service or the layer information of the corresponding associated configuration layer as the routing recovery signal layer information; or,

[0068] Step S22: When it is determined that there is no protection service based on the service information of this layer, the service bearer relationship corresponding to the ODU service is traversed layer by layer to determine the routing recovery signal layer information.

[0069] For example, you can pre-configure default thresholds and modification interfaces for business pipelines. For instance, you can configure a preset default value of 60%, and changes to this preset value will only affect subsequent operations.

[0070] Specifically, after a service routing change event is triggered, routing calculations can be initiated on a per-service bearer tree basis for the ODU service, and the recovery signal level must first be determined. Specifically, for the currently analyzed ODU service, the bandwidth utilization rate of the ODU service can be determined first. When the bandwidth utilization rate reaches a preset passthrough threshold, it indicates that it no longer has reuse value, and pipeline passthrough can be performed to avoid network fault segments; then the routing recovery signal level of the service bearer tree can be determined as the ODU.

[0071] Alternatively, if the bandwidth utilization of the ODU service does not reach the preset pass-through threshold, the corresponding service bearer tree can be searched to obtain the current layer service information of the ODU service. Based on the protection layer settings of the services on the service bearer tree, the routing recovery signal layer of that service bearer tree can be analyzed. For details, refer to... Figure 4 As shown, when it is determined that the bandwidth utilization of the ODU service has not reached the preset pass-through threshold, for the initial layer of the ODU, the service information of this layer of the ODU service can be obtained first, and it can be determined whether there is a protection service, i.e., protection service routing; for example... Figure 2 The protection service routes shown in the middle protection segment. If a protection service route exists, the recovery signal level can be determined as the level with the protection service route in the service bearer tree or its associated configuration layer. The associated configuration layer refers to a configurable layer that has a 1:1 relationship with a service layer when that service layer does not have independent configuration capabilities. For example, MS and RS usually coexist with ODU services, and if the MS layer does not have independent configuration capabilities, then the ODU layer is its associated configuration layer.

[0072] For example, the corresponding route recovery signal level can be configured based on the protection type of each protection level in the service bearer relationship. Figure 1 Taking the bearer route shown as an example, the correspondence between protection level, protection type and route recovery signal level is shown in Table 1 below.

[0073] Table 1

[0074] ODU ODU-SNCP ODU MS LMSP ODU VC4 Advanced VC-SNCP VC VC12, VC3 low-order VC-SNCP VC OSU OSU-SNCP OSU

[0075] Alternatively, if it is determined that no protected service route exists for the service information at this layer, then the process moves along the service bearer tree towards the customer layer. (Reference) Figure 2 The structure shown moves one layer towards the customer layer each time, determining whether protection can be configured on that layer. If it can, the service information for that layer is obtained, and the recovery signal layer is determined to be that layer or its associated configuration layer. Otherwise, it continues to determine whether the layer still has customer layer carrying capacity. If it does, it moves along the service carrying tree towards the customer layer again for further determination, thereby determining the routing recovery signal layer information.

[0076] In step S12, service routing is planned based on the routing recovery signal hierarchy information.

[0077] In this example embodiment, step S12 described above may include:

[0078] Step S31: Based on the route recovery signal hierarchy information, avoid the faulty link and perform service route planning on the route recovery signal hierarchy;

[0079] Step S32: Obtain service layer path reuse information corresponding to the service route. If all service layer paths reuse existing paths, then perform path changes according to the service routes planned after restoring the signal hierarchy based on the route; or...

[0080] Step S33: If the service layer path does not fully reuse the existing path, then avoid the faulty link and perform service routing planning for the service layer.

[0081] Specifically, refer to Figure 5 As shown, service routing planning is based on the ODU service bearer tree, starting at the bearer tree routing recovery signal layer. Avoiding network fault segments, all service routes at this layer are planned. Routes are calculated according to locally optimal paths, replacing parts of the paths of failed protection group entities. If all service layer paths of a service route reuse existing paths, then after the service path at the routing recovery signal layer is changed, the client-layer services it carries do not require any operation. Alternatively, if not all service layer paths are reused, service layer service routes are planned, avoiding network fault segments. For service layer service routing planning, this is equivalent to iteratively calling the routing planning method at the service layer level.

[0082] In this example implementation, the above method may further include: when planning the service layer service route, if there is an intermediate network element, the service layer service is terminated and split at the intermediate network element; the route recovery signal layer service is cross-continuing at the intermediate network element; or, if there is no intermediate network element, the service layer service is planned to be routed in a pipeline-through manner.

[0083] Specifically, when the new route planned for a service layer service does not have intermediate network elements, the service is routed through the service layer pipeline. For example, the service layer service routing planning result is as follows: Figure 6 As shown, if the path to avoid the network fault segment does not pass through intermediate network elements, the service layer service provides available routes in a pipeline manner.

[0084] Alternatively, when a new route planned for a service layer service exists in an intermediate network element, the service layer service terminates and splits at the intermediate network element; the service in the current layer continues and crosses over at the intermediate network element. For example, the service layer service routing plan result is as follows: Figure 7 As shown, the path to avoid network fault segments passes through one or more intermediate network elements. To improve network bandwidth utilization, service layer services can be terminated and divided into multiple services at intermediate network elements; the current layer service continues the end-to-end route in an interleaved manner at the intermediate network elements.

[0085] Specifically, the rules for replacing routes to failed entities within a protection segment can include: (1) when the bandwidth utilization of a pipeline reaches a threshold and it no longer has reuse value, the pipeline can bypass the network fault segment; (2) when service signals within a protection segment cannot be terminated, the protection setting layer and its associated configuration layer of the network fault segment in the service bearer tree are equivalent to the route recovery signal layer of the bearer tree; (3) when the service layer service of the route recovery signal layer in the service bearer tree needs to be terminated and segmented at intermediate stations on the new path to provide reuse capability; (4) when the service of the route recovery signal layer in the service bearer tree passes through intermediate stations on the new path to ensure signal continuity and protection capability effectiveness; (5) when the customer layer service of the route recovery signal layer in the service bearer tree remains unchanged, only the physical routing information of the service needs to be updated. Based on the above rules, the local optimal path replacement method that avoids the network fault segment can make full use of the existing network configuration, reduce the complexity of network configuration, and can be applied to the segmented protection scenario of government and enterprise OTN services; each protection segment of the service is independent of each other, and route replacement within the protection segment can reduce the complexity of route calculation.

[0086] For example, in the application scenario of expanding government and enterprise OTN networks, there is a need for site expansion in the engineering of government and enterprise OTN networks, such as... Figure 8As shown, in the scenario where the physical network link Link:NE1.a-NE2.b is damaged, NE3 is added between NE1 and NE2, along with Link:NE1.a-NE3.c and Link:NE2.b-NE3.d. In this scenario, the original and target paths for the local optimal path replacement are affected by the cutover plan. It is expected that NE3 can achieve aggregation access and routing forwarding. Simply using a pipe to pass through the lowest layer will reduce the bandwidth utilization of the newly added network segment, creating potential problems for future network operation. In this scenario, the service cutover system can proactively call the aforementioned routing configuration method to obtain topology changes through parameter input or automatic topology awareness, analyze the impact on existing network services, and analyze that the deletion of "Link:NE1.a-NE2.b" is a physical layer fiber adjustment, which will affect a large number of government and enterprise services, thereby triggering the bearer tree routing planning process, including: traversing the ODU services affected by the faulty fiber, analyzing the service bearer tree routing recovery signal hierarchy rooted at the ODU service; among which, it can be according to... Figure 4 The method shown is a hierarchical analysis method for restoring the signal hierarchy of the bearer tree route, which determines... Figure 8 The ODU service routing recovery signal level is VC. Then, based on the ODU service bearer tree routing recovery signal level, service routes on the bearer tree are planned; where, when planning service routes, such as... Figure 8 As shown, the routes and resources of NE1 and NE2 are reused. For the service layer ODU, the service is terminated and divided into two services with NE3 as the boundary: "-NE1-NE3" and "NE3-NE2-". The time slot resources occupied by NE3.c and NE1.a, and NE3.d and NE2.b must be consistent. However, in the route recovery signal layer VC, the resource occupancy of NE3 is determined by the up and down hops of this layer (not necessarily located in NE1 or NE2).

[0087] Based on the above routing results, analyze the business configuration data:

[0088] (1) Configure port mapping to form CTP:c1;

[0089] (2) Configure port mapping to form CTP:d1;

[0090] (3) Binding configuration between VC layer FTP and service layer CTP: FTP:c2 and CTP:c1, FTP:d2 and CTP:d1;

[0091] (4) Routing recovery signal layer CTP configuration: CTP:c3, CTP:d3;

[0092] (5) Cross-configuration between signal layer CTP:c3 and CTP:d3 for route recovery;

[0093] After the configuration interaction module 4023 successfully sends the configuration to the physical network, the service control module 4022 generates RS and MS layer data, adjusts VC layer service customer service relationships, etc., and completes the network expansion and stabilization. Figure 8 As shown, based on the expanded network, new services starting and ending at NE3 can reuse the service layer paths generated during the expansion process, thus improving network bandwidth utilization.

[0094] In this example implementation, in the scenario of OTN network fault service protection and recovery, taking government and enterprise OTN as an example, refer to... Figure 2 The network architecture shown employs segmented protection to ensure reliability. However, each protection group can only withstand a single fiber break within its protected segment; a secondary failure within the protected segment will result in service interruption. (Reference) Figure 9 As shown, when a physical network link (Link:NE1.e-NE2.f) fails and is interrupted, the network device sends a change notification based on a unified model after sensing the link change. Based on this notification, the change is analyzed as a physical layer link interruption, affecting a large number of enterprise services, triggering the bearer tree routing planning process. First, the routing recovery signal level is analyzed, and routing calculations are performed. Finally, service configuration data analysis is completed and distributed to the physical network. Specifically, the service bearer tree routing recovery signal level is analyzed as OSU; the locally optimal path is calculated, with ODU services terminating and splitting at NE3; OSU services continuing end-to-end at NE3; routing configuration changes are analyzed, including: ODU mapping configuration: CTP:a1, c1, d1; virtual port binding configuration: FTP:c2-CTP:c1, FTP:d2-CTP:d1, modifying FTP:a2-CTP:a1; VC layer CTP configuration: CTP:c3, d3; VC layer cross-connect configuration: CTP:c3-CTP:d3. Specifically, as shown... Figure 9 In the routing results shown, besides the intermediate site NE3 having service configurations, NE1 and NE2 also have port replacements. For example, CTP:e1 in NE1.e needs to be replaced with the same-rate CTP:a1 in NE1.a. In network failure scenarios, performing route replacements on failed work or protection entities within the protection segment can quickly restore service protection capabilities. Determining the route recovery signal level through existing network services can avoid the network resource waste caused by lower-level pipeline crossings, and also avoid the problems of large computational load and complex configuration caused by top-level service recovery.

[0095] The routing configuration method provided in this disclosure, when a network failure causes the working or protection route to fail, determines the routing recovery signal layer of the service bearer tree by analyzing the bandwidth utilization of the existing ODU pipeline and the protection mode of the service bearer tree. It replaces the faulty service route at the recovery signal layer with a locally optimal path, only partially replacing the failed working or protection route, thus improving the speed of service protection capability recovery. For ODU service bearer trees with low bandwidth utilization, simple bottom-level pipeline traversal is avoided when restoring protection capabilities, improving network bandwidth utilization. The routing recovery signal layer of the service bearer tree is equivalent to the protection setting layer and its associated configuration layer on the bearer tree, and routes are planned accordingly, reducing the complexity of configuration changes. This technical solution can avoid service protection capability degradation and improve service reliability. This method can utilize existing network configurations, has low configuration complexity, and provides fast service protection capability recovery; it can also avoid large pipeline traversal, allowing for flexible reuse and improving bandwidth utilization; it avoids low-speed service recovery, reducing routing calculation and routing change configuration complexity.

[0096] It should be noted that the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of the present invention, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Furthermore, it is readily understood that these processes may, for example, be executed synchronously or asynchronously in multiple modules.

[0097] Further reference Figure 9 As shown, this example embodiment also provides a routing configuration device 90, including: a bearer relationship analysis module 901 and a routing planning module 902; wherein,

[0098] The bearer relationship analysis module 901 can be used to determine the optical data unit (ODU) service associated with the faulty link; based on the service bearer relationship corresponding to the ODU service, it can determine the routing recovery signal hierarchy information corresponding to the ODU service and the customer layer service carried by the ODU service.

[0099] The routing planning module 902 shown can be used to perform service routing planning based on the routing recovery signal hierarchy information.

[0100] In some exemplary embodiments, the apparatus further includes a topology management module 93.

[0101] The topology management module 93 can be used to monitor changes in the physical network topology, collect network topology data, maintain network element, port, and link data, and synchronize topology changes to other modules in real time. Specifically, the topology management module 93 may include a network element management module 931 and a link management module 932, which are used for network element management and link management, monitoring changes in the physical network topology, abstracting the collected raw network topology data into a unified model, maintaining network element, port, and link data, and synchronizing information such as topology changes, port alarms, and signal defects to the service management module and the routing calculation module in real time.

[0102] In some exemplary embodiments, the apparatus further includes a service management module 92, which may include a bearer impact analysis module 921, a service control module 922, and a configuration interaction module 923. The bearer impact analysis module can be used to receive topology change notifications sent by the topology management module and analyze their impact on existing network services. For infrastructure changes such as link changes and physical port failures that affect a large number of government and enterprise services, the module calls the service bearer tree routing calculation interface provided by the routing calculation module, taking the ODU service bearer tree as a unit, to obtain the routing results, and then calls the service control module. The service control module can be used to analyze service routes and generate service configuration data. When routes change, it updates customer service relationships and maintains service physical routing information. The configuration interaction module can be used to execute service configuration commands issued by the service control module and update the physical network configuration.

[0103] In some exemplary embodiments, the apparatus may further include a routing calculation module 91, which may specifically include a resource maintenance module 903, a bearer relationship analysis module 901, and a routing planning module 902. The resource maintenance module is responsible for real-time synchronization and maintenance of topology data, and provides port resource allocation services to the routing planning module. The bearer relationship analysis module is responsible for maintaining the pipe penetration threshold and analyzing the routing recovery signal hierarchy of the ODU service bearer tree. The routing planning module is responsible for calculating the routes of all services on the bearer tree according to the routing recovery signal hierarchy.

[0104] For example, the bearer tree analysis module provides a default value and modification interface for the service pipeline penetration threshold, assuming a default value of 60%. Modification of the default value only applies to subsequent operations. After the topology management module detects a topology change, it sends a change notification; the resource maintenance module maintains consistency between resource data and the topology management module; and triggers the bearer impact analysis module to analyze the impact of the change. The bearer impact analysis module analyzes physical facility changes such as physical port alarms, link failures, and fiber optic adjustments, identifying a large number of affected enterprise services, triggering route calculations based on the ODU service bearer tree. The bearer tree analysis module analyzes the service bearer tree route recovery signal level according to system preset attributes. The route planning module uses the analyzed bearer tree route recovery signal level as input to plan paths for all services on the service bearer tree. During this process, the resource maintenance module is responsible for providing port resource allocation services and maintaining resource occupancy information. The bearer impact analysis module calls the service control module to analyze service configuration data, including but not limited to mapping configuration, cross-connect configuration, virtual port binding configuration, and protection group modification configuration; thus realizing service configuration data analysis. The service control module completes the distribution of physical network configurations through the configuration interaction module, while simultaneously updating the service's customer service relationship and physical routing information.

[0105] The specific details of each module in the above-mentioned routing configuration device have been described in detail in the corresponding routing configuration methods, so they will not be repeated here.

[0106] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0107] Furthermore, this example embodiment provides a network device 400 capable of implementing the above method. Figure 12 The network device 400 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0108] like Figure 12 As shown, the components of the network device 400 may include, but are not limited to: at least one processing unit 410, at least one storage unit 420, and a bus 430 connecting different system components (including storage unit 420 and processing unit 410).

[0109] The storage unit stores program code that can be executed by the processing unit 410, causing the processing unit 410 to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of the present invention. For example, the processing unit 410 can perform actions such as... Figure 3 The steps are shown in the figure.

[0110] Storage unit 420 may include a readable medium in the form of a volatile storage unit, such as random access memory (RAM) 4201 and / or cache memory 4202, and may further include a read-only memory (ROM) 4203.

[0111] Storage unit 420 may also include a program / utility 4204 having a set (at least one) program module 4205, such program module 4205 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0112] Bus 430 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0113] Computer system 400 can also communicate with one or more external devices 50 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with computer system 400, and / or with any device that enables computer system 400 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 450. Furthermore, computer system 400 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 460. As shown, network adapter 460 communicates with other modules of computer system 400 via bus 430. Processing unit 410 is connected to display unit 440 via bus 430. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with computer system 400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0114] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0115] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the methods described above is stored. In some possible embodiments, various aspects of the invention may also be implemented as a program product comprising program code that, when the program product is run on a terminal device, causes the terminal device to perform the steps of the various exemplary embodiments of the invention described in the "Exemplary Methods" section of this specification.

[0116] refer to Figure 13 As shown, a program product 130 for implementing the above-described method according to an embodiment of the present invention is described. It may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, the readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0117] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0118] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0119] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0120] Program code for performing the operations of this invention can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0121] Furthermore, the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of the present invention, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0122] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and embodiments are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.

[0123] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A routing configuration method, characterized in that, The method includes: Identify the optical data unit (ODU) services associated with the faulty link; Obtain the local layer service information of the ODU service to determine whether there is a protection service; When it is determined that a protection service exists, the hierarchical information of the protection service or the hierarchical information of the corresponding associated configuration layer is configured as the hierarchical information of the route recovery signal. When it is determined that there is no protected service based on the service information of this layer, the service bearer relationship corresponding to the ODU service is traversed layer by layer, and the route recovery signal layer is configured based on the protection type of each protection layer in the service bearer relationship to determine the route recovery signal layer information; the route recovery signal layer refers to the layer in the service bearer tree that maintains the beginning and end and the number of services of this layer and its customer layer unchanged. Based on the aforementioned route recovery signal hierarchy information, service route planning is performed; The process of planning service routes based on the route recovery signal hierarchy information includes: Based on the route recovery signal hierarchy information, the faulty link is avoided, and service routing is planned for the route recovery signal hierarchy; Obtain the service layer path reuse information corresponding to the service route. If all service layer paths reuse existing paths, then perform path changes according to the service route after the signal hierarchy is restored based on the route; or If the service layer path does not fully reuse existing paths, then the faulty link is avoided and business routing is planned for the service layer. When planning service layer service routes, if intermediate network elements exist, the service layer service terminates and splits at the intermediate network element; the route recovery signal layer service crosses and continues at the intermediate network element; or... If no intermediate network element exists, the service layer services will plan their routes using a pipe-through method.

2. The routing configuration method according to claim 1, characterized in that, The method further includes: Obtain the bandwidth utilization information corresponding to the service bearer relationship of the ODU service. If the bandwidth utilization information is greater than or equal to a preset passthrough threshold, then determine that the restored signal layer information is the ODU service layer; or, If the bandwidth utilization information is less than the preset passthrough threshold, then the local layer service information of the ODU service is obtained.

3. The routing configuration method according to claim 1, characterized in that, The method further includes: Listen for network topology change notifications and collect the corresponding network topology information; Based on the network topology change notification, a service routing change event is triggered to perform service routing planning.

4. A routing configuration device, characterized in that, The device includes: The bearer relationship analysis module is used to determine the optical data unit (ODU) services associated with the faulty link; obtain the current layer service information of the ODU service, and determine whether there is a protection service; when it is determined that there is a protection service, configure the layer information of the protection service or the layer information of the corresponding associated configuration layer as the route recovery signal layer information; when it is determined that there is no protection service based on the current layer service information, traverse the service bearer relationship corresponding to the ODU service layer by layer, and configure the route recovery signal layer based on the protection type of each protection layer in the service bearer relationship to determine the route recovery signal layer information; the route recovery signal layer refers to the layer in the service bearer tree that maintains the beginning and end and the number of services of that layer and its customer layer unchanged. The routing planning module is used to perform service routing planning based on the routing recovery signal hierarchy information. The process of planning service routes based on the route recovery signal hierarchy information includes: Based on the route recovery signal hierarchy information, the faulty link is avoided, and service routing is planned for the route recovery signal hierarchy; Obtain the service layer path reuse information corresponding to the service route. If all service layer paths reuse existing paths, then perform path changes according to the service route after the signal hierarchy is restored based on the route; or If the service layer path does not fully reuse existing paths, then the faulty link is avoided and business routing is planned for the service layer. When planning service layer service routes, if intermediate network elements exist, the service layer service terminates and splits at the intermediate network element; the route recovery signal layer service crosses and continues at the intermediate network element; or... If no intermediate network element exists, the service layer services will plan their routes using a pipe-through method.

5. A network device, characterized in that, include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to execute the routing configuration method of any one of claims 1 to 3 by executing the executable instructions.

6. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the routing configuration method as described in any one of claims 1 to 3.

Images