A multi-vendor OTN device interworking method

Abstract

The application discloses a multi-vendor OTN equipment intercommunication method, and the method comprises the following steps: 1) network deployment; 2) network configuration; 3) network debugging; 4) service opening; 5) service recovery; and 6) service deletion. The method can realize interconnection and intercommunication of cross-domain network services and dynamic recovery without changing the actual deployment of a physical network, and can improve resource utilization of the network, reduce operation and maintenance complexity of the network and improve the anti-destroying performance of the network.

Description

Technical Field

[0001] This invention relates to optical communication technology, and more particularly to OTN interconnection technology for multi-vendor optical transport networks. The OTN interconnection technology is used to provide an end-to-end service interconnection solution for application scenarios of mixed networking of multi-vendor optical transport network equipment, specifically a method for interoperating multi-vendor OTN equipment. Background Technology

[0002] Driven by the demands of applications such as high-definition video, live streaming, large-scale online games, and big data collaboration, high-capacity OTN equipment has become the mainstream for backbone optical communication networks. However, the communications market is highly competitive, with equipment manufacturers such as Huawei, ZTE, Alcatel-Lucent, Nokia Siemens Networks (NSN), Ciena, and Fiberhome all launching their own mature OTN equipment. Consequently, the OTN networks built in different regions of the existing network vary, resulting in the coexistence of multiple equipment providers within the same type of network. While adhering to OIF specifications, equipment manufacturers use different control protocols and signaling formats during development, making interoperability of the same type of services between different vendors extremely difficult. End-to-end service activation often requires lengthy testing and commissioning by specialized technicians, and cross-vendor service management is challenging, making maintenance and management exceptionally cumbersome and unable to meet the needs for rapid activation, scheduling, and dynamic recovery of cross-domain services. Therefore, there is a strong demand for rapid activation and comprehensive management of cross-domain services in multi-vendor OTN networks. Summary of the Invention

[0003] The purpose of this invention is to address the shortcomings of existing technologies by providing a method for interoperability between multi-vendor OTN devices. This method enables cross-domain network service interconnection and dynamic recovery without altering the actual physical network deployment, thereby improving network resource utilization, reducing network operation and maintenance complexity, and enhancing network resilience.

[0004] The technical solution to achieve the objective of this invention is:

[0005] A method for interoperability of multi-vendor OTN devices is disclosed. This method is applicable to networks established by interconnecting OTN adaptation units and integrated network management units from various vendor domains. Each vendor domain OTN adaptation unit comprises sequentially connected integrated network management information transceiver unit, information conversion unit, information filtering unit, and vendor equipment information transceiver unit. The integrated network management information transceiver unit is connected to the integrated network management unit, and the vendor equipment information transceiver unit is connected to the vendor equipment. The integrated network management unit comprises user management unit, domain configuration unit, information communication unit, service configuration unit, path calculation unit, traffic engineering unit, link management unit, power-down configuration saving unit, alarm and performance management unit, and topology management unit. The method includes the following steps:

[0006] 1) Network Deployment: Without changing the physical network deployment of OTN, connect the OTN adapter units of each vendor to their respective domains, and connect the OTN adapter units of each vendor's domain to the integrated network management unit. Due to the closed nature of each domain, each has its own independent network segment and IP. Even if the domains are physically connected, the networks are not interconnected. Therefore, it is necessary to change the corresponding network segment and IP information of the OTN adapter units of each vendor's domain according to the network plan, and add the corresponding communication IP and network segment to the integrated network management unit to ensure that the integrated network management unit, the OTN adapter units of each vendor's domain, and the vendor's equipment are on the same network segment, so as to realize the physical connection and information exchange between the integrated network management unit and the OTN domains of each vendor.

[0007] 2) Network Configuration: In a multi-domain network composed of OTN equipment from different manufacturers, the connectivity of fiber optic links within a domain can be viewed and verified through the network management systems of each manufacturer. However, for inter-domain links, due to differences in communication protocols and signaling formats between different manufacturers, no connectivity verification mechanism can be provided. Therefore, before actual use, it is necessary to manually verify and ensure the connectivity of inter-domain links. The integrated network management unit should be configured according to the actual network situation, and the network management front-end configuration file should be modified according to the network connection situation. The front-end configuration file includes the domain configuration file, inter-domain link configuration file, link list configuration file, node list configuration file, and topology basic information configuration file.

[0008] 3) Network Debugging: After network deployment and configuration, network debugging tests should be performed to ensure that the network is correctly configured according to the actual network plan. First, ping each vendor's domain OTN adapter unit and vendor network element through the network management host. If connectivity is normal, proceed to the next step; otherwise, check whether the physical connection and IP configuration are correct. Second, check whether the inter-domain link configuration and physical connection are consistent, and check the link connectivity and loss. If no errors are found, proceed to the next step. Then, view the network topology information of each domain on the integrated network management unit. If the network topology information is incomplete or inconsistent with the actual network topology information displayed on the integrated network management unit, the network management front end needs to be reviewed. Configure the network and check the network management systems of each manufacturer's equipment to determine the cause of the problem. Manually check the missing nodes and links according to the manufacturer's network management system prompts to ensure that the integrated network management topology is consistent with the physical network. Finally, restart the integrated network management unit and check whether the network topology and inter-domain links are consistent with the current network plan. If they are consistent, disconnect the optical port laser at the link end on the manufacturer's network management system and check whether the integrated network management unit receives an alarm and whether the link status shows as disconnected. If both are received, restart the laser and check whether the link alarm is resolved and whether the link status returns to normal connection. If all the above operations are normal, the network debugging is complete. Otherwise, continue to check and repeat the above operations until the debugging results are consistent with expectations.

[0009] 4) Service Activation: Once network deployment, configuration, and commissioning are normal, service activation can proceed. Services can be activated through the integrated network management unit (IMU). This includes cross-domain service activation and activation of services within a single vendor's domain. It is recommended that intra-domain service activation be performed on the vendor's network management interface, while cross-domain service activation should be performed on the IMU for easier network maintenance. During service activation, first access the service configuration interface of the IMU. Based on the planned service activation, select the corresponding port, wavelength, and rate parameters. If a port is unavailable, it indicates that the port resource is unavailable. Check the interfaces of the corresponding vendor's network elements to see if services are already available and adjust the corresponding plans accordingly. If everything is normal, the service configuration is issued. The IMU backend will then send the configuration commands to the path calculation function unit for path calculation. The functional unit first updates and queries the traffic engineering database, calculates the service path based on the latest resource information of the entire network, and sends the specific service configuration information to the information communication functional unit. The information communication functional unit then distributes the configuration information to the OTN adaptation units of each vendor domain involved. Each vendor domain OTN adaptation unit parses the information and converts it into information that can be recognized by the vendor network elements, and then forwards it to the vendor network management and device network elements, waits for the network element response, and forwards the response information to the integrated network management unit through each vendor domain OTN adaptation unit. After receiving the information, the integrated network management unit updates the service information and traffic engineering database, and informs that the service has been successfully established. Once the service is successfully established, a loopback is performed on one end port of the service, and a network tester is connected to the other end port for inspection and verification.

[0010] 5) Service Recovery: After cross-domain services are activated, signal degradation, link failures, laser malfunctions, etc., can cause service failures, resulting in bit errors or even complete outages. In such cases, it is urgent to restore cross-domain services. Traditional cross-domain services are mostly established in point-to-point segments, and each domain can only maintain intra-domain links and cannot maintain inter-domain links. Therefore, fault location is difficult and rapid recovery of cross-domain services cannot be achieved. When a cross-domain service fails, the integrated network management unit immediately pops up an alarm prompt based on the received fault information, displays the faulty service as interrupted on the integrated network management unit, and triggers the service recovery mechanism. To efficiently utilize network resources, the faulty service is first deleted and the resources occupied by the service are released during service recovery. Then, the path calculation algorithm is called to calculate a path that is completely unrelated to the faulty service, and then the path recovery is completed. Since the recovered path is completely unrelated to the initial path, the reliability and fault tolerance of the service can be effectively improved. The dynamic recovery feature also greatly improves the network resource utilization rate.

[0011] 6) Service Deletion: When cross-domain services are canceled or adjusted, the services should be deleted promptly to release limited network resources. When deleting a service, first enter the service configuration interface of the integrated network management unit, select the service to be deleted, click the delete option, and click confirm in the pop-up deletion warning box to complete the deletion operation. After the service deletion command is issued, the integrated network management unit will send the command to the information and communication function unit. The information and communication function unit will then send the deletion command to the OTN adaptation units of each vendor domain involved. Each vendor domain OTN adaptation unit will parse the command information and convert it into information that can be recognized by the vendor network elements. Then, it will forward it to the vendor network management and equipment network elements and wait for the network elements to respond and reply. The response information will be forwarded to the integrated network management unit through each vendor domain OTN adaptation unit. After receiving the information, the integrated network management unit will update the service information and traffic engineering database and indicate that the service has been successfully deleted.

[0012] The OTN adaptation units for each vendor are primarily used to convert the control information, management information, and signaling formats of OTN devices from various vendors into a unified information format that can be recognized and processed by the integrated network management unit (IMU). They also convert the control information, management information, and signaling formats issued by the IMU into information formats that can be recognized and processed by the OTN devices from various vendors, thereby achieving unified and interoperable signaling information across the entire network. Specifically:

[0013] The integrated network management information transceiver unit realizes the reception and transmission of information such as route establishment, route disconnection, query, synchronization, alarm, link status, and topology of the integrated network management, and sends the response information of the manufacturer's equipment to the integrated network management unit;

[0014] The information conversion function unit enables bidirectional conversion between information from the integrated network management unit and information from manufacturer equipment, ensuring information exchange and communication.

[0015] The information filtering function unit filters a large amount of manufacturer equipment information to ensure that the necessary instruction information is converted, reducing unnecessary information transmission and processing, and improving the efficiency of dynamic allocation of network resources of the entire system.

[0016] The manufacturer's information transmission and reception function unit sends the information issued by the integrated network management unit to the device and sends the device's response information back to the integrated network management unit.

[0017] The integrated network management unit (IMU) enables rapid deployment of OTN cross-domain services through unified maintenance of the entire network topology, resources, and signaling. The IMU interacts with equipment from various vendors through the information and communication function unit to understand available network resources, dynamically update the topology and traffic engineering database, and maintain synchronization with vendor equipment resource databases. This achieves comprehensive network topology presentation and management. The traffic engineering database maintains port, link, and wavelength information for each vendor's equipment domain across the network and updates it in real time based on network conditions. This provides accurate resource information to the path calculation function unit, improving routing success rates and maintaining resource synchronization between the integrated network management traffic database and the network management information of each vendor's equipment. Specifically:

[0018] The business configuration function unit is responsible for establishing and deleting business connections across vendor domains, providing operators with a convenient and clear operating method;

[0019] The path calculation function unit calculates the required cross-domain path based on the resource data in the traffic engineering database according to the business configuration requirements. On the other hand, when a cross-domain link fails and causes a business interruption, it quickly triggers the recovery mechanism to recalculate a path that is completely unrelated to the failed business based on the traffic engineering database, ensuring the rapid recovery of cross-domain business.

[0020] The link management function unit mainly realizes the maintenance and updating of network topology links and the management of cross-domain paths, and monitors and reports link alarms and service connectivity status in real time.

[0021] The power-off configuration saving function unit mainly realizes the saving of network service configuration information when the integrated network management system is shut down or restarted, so as to prevent the situation where historical configurations cannot be known when the network management system is shut down or restarted, which would cause difficulties in the maintenance and management of historical services and waste of resources.

[0022] The alarm and performance management function unit monitors the status information of links, ports, services, and device nodes, ensuring that network maintenance personnel can keep abreast of the network situation and guarantee stable network operation.

[0023] The beneficial effects of this technical solution are as follows:

[0024] 1) This technical solution can achieve interconnection and interoperability of OTN network services from different manufacturers without changing the actual physical network deployment;

[0025] 2) This technical solution, through the effective collaboration of OTN adaptation units and integrated network management units of various vendors, enables the establishment of cross-domain services to be quickly activated simply by selecting the source and destination ports on the integrated network management system, effectively reducing the operational complexity of establishing cross-domain services under normal circumstances.

[0026] 3) The technical solution can realize complex mesh networking of OTN devices from multiple vendors. Based on comprehensive management and control of the entire network, it can not only realize the rapid activation of cross-domain services across the entire network, but also realize the management, maintenance and dynamic recovery of cross-domain services. It can effectively improve the reliability and fault tolerance of the network, and also greatly improve the resource utilization of the network and reduce the complexity of network operation and maintenance.

[0027] 4) The technical solution can achieve comprehensive control of OTN domain resource information from multiple vendors. In the event of natural disasters or military attacks, it can maximize the use of network resources and achieve dynamic recovery of cross-domain services, which can effectively improve the network's resilience.

[0028] This method enables cross-domain network service interconnection and dynamic recovery without changing the actual physical network deployment, improving network resource utilization, reducing network operation and maintenance complexity, and enhancing network resilience. Attached Figure Description

[0029] Figure 1 This is a schematic diagram illustrating a typical application of a multi-vendor OTN network in the embodiments;

[0030] Figure 2 This is a schematic diagram of the OTN adaptation units of each vendor domain in the embodiment;

[0031] Figure 3 This is a schematic diagram of the integrated network management unit in the embodiment. Implementation

[0032] The present invention will be further described below with reference to the accompanying drawings and embodiments, but this is not intended to limit the scope of the invention. Example

[0033] A method for interoperability of multi-vendor OTN devices, applicable to networks established by interconnecting OTN adaptation units and integrated network management units from various vendors, such as... Figure 1 As shown, the OTN adapter units of each manufacturer's domain are as follows: Figure 2 The diagram shows a series of interconnected functional units: an integrated network management information transceiver unit, an information conversion unit, an information filtering unit, and a manufacturer's equipment information transceiver unit. The integrated network management information transceiver unit is connected to the integrated network management unit, and the manufacturer's equipment information transceiver unit is connected to the manufacturer's equipment. The integrated network management unit is as follows: Figure 3 The system includes user management, domain configuration, information communication, service configuration, path calculation, traffic engineering, link management, power-down configuration saving, alarm and performance management, and topology management units. The method comprises the following steps:

[0034] 1) Network Deployment: Without changing the physical network deployment of OTN, connect the OTN adapter units of each vendor to their respective domains, and connect the OTN adapter units of each vendor's domain to the integrated network management unit. Due to the closed nature of each domain, each has its own independent network segment and IP. Even if the domains are physically connected, the networks are not interconnected. Therefore, it is necessary to change the corresponding network segment and IP information of the OTN adapter units of each vendor's domain according to the network plan, and add the corresponding communication IP and network segment to the integrated network management unit to ensure that the integrated network management unit, the OTN adapter units of each vendor's domain, and the vendor's equipment are on the same network segment, so as to realize the physical connection and information exchange between the integrated network management unit and the OTN domains of each vendor.

[0035] 2) Network Configuration: In a multi-domain network composed of OTN equipment from different manufacturers, the connectivity of fiber optic links within a domain can be viewed and verified through the network management systems of each manufacturer. However, for inter-domain links, due to differences in communication protocols and signaling formats between different manufacturers, no connectivity verification mechanism can be provided. Therefore, before actual use, it is necessary to manually verify and ensure the connectivity of inter-domain links. The integrated network management unit should be configured according to the actual network situation, and the network management front-end configuration file should be modified according to the network connection situation. The front-end configuration file includes the domain configuration file, inter-domain link configuration file, link list configuration file, node list configuration file, and topology basic information configuration file.

[0036] 3) Network Debugging: After network deployment and configuration, network debugging tests should be performed to ensure that the network is correctly configured according to the actual network plan. First, ping each vendor's domain OTN adapter unit and vendor network element through the network management host. If connectivity is normal, proceed to the next step; otherwise, check whether the physical connection and IP configuration are correct. Second, check whether the inter-domain link configuration and physical connection are consistent, and check the link connectivity and loss. If no errors are found, proceed to the next step. Then, view the network topology information of each domain on the integrated network management unit. If the network topology information is incomplete or inconsistent with the actual network topology information displayed on the integrated network management unit, the network management front end needs to be reviewed. Configure the network and check the network management systems of each manufacturer's equipment to determine the cause of the problem. Manually check the missing nodes and links according to the manufacturer's network management system prompts to ensure that the integrated network management topology is consistent with the physical network. Finally, restart the integrated network management unit and check whether the network topology and inter-domain links are consistent with the current network plan. If they are consistent, disconnect the optical port laser at the link end on the manufacturer's network management system and check whether the integrated network management unit receives an alarm and whether the link status shows as disconnected. If both are received, restart the laser and check whether the link alarm is resolved and whether the link status returns to normal connection. If all the above operations are normal, the network debugging is complete. Otherwise, continue to check and repeat the above operations until the debugging results are consistent with expectations.

[0037] 4) Service Activation: Once network deployment, configuration, and commissioning are normal, service activation can proceed. Services can be activated through the integrated network management unit (IMU). This includes cross-domain service activation and activation of services within a single vendor's domain. It is recommended that intra-domain service activation be performed on the vendor's network management interface, while cross-domain service activation should be performed on the IMU for easier network maintenance. During service activation, first access the service configuration interface of the IMU. Based on the planned service activation, select the corresponding port, wavelength, and rate parameters. If a port is unavailable, it indicates that the port resource is unavailable. Check the interfaces of the corresponding vendor's network elements to see if services are already available and adjust the corresponding plans accordingly. If everything is normal, the service configuration is issued. The IMU backend will then send the configuration commands to the path calculation function unit for path calculation. The functional unit first updates and queries the traffic engineering database, calculates the service path based on the latest resource information of the entire network, and sends the specific service configuration information to the information communication functional unit. The information communication functional unit then distributes the configuration information to the OTN adaptation units of each vendor domain involved. Each vendor domain OTN adaptation unit parses the information and converts it into information that can be recognized by the vendor network elements, and then forwards it to the vendor network management and device network elements, waits for the network element response, and forwards the response information to the integrated network management unit through each vendor domain OTN adaptation unit. After receiving the information, the integrated network management unit updates the service information and traffic engineering database, and informs that the service has been successfully established. Once the service is successfully established, a loopback can be performed on one end port of the service, and a network tester can be connected to the other end port for inspection and verification.

[0038] 5) Service Recovery: After cross-domain services are activated, signal degradation, link failures, laser malfunctions, etc., can cause service failures, resulting in bit errors or even complete outages. In such cases, it is urgent to restore cross-domain services. Traditional cross-domain services are mostly established in point-to-point segments, and each domain can only maintain intra-domain links and cannot maintain inter-domain links. Therefore, fault location is difficult and rapid recovery of cross-domain services cannot be achieved. When a cross-domain service fails, the integrated network management unit immediately pops up an alarm prompt based on the received fault information, displays the faulty service as interrupted on the integrated network management unit, and triggers the service recovery mechanism. To efficiently utilize network resources, the faulty service is first deleted and the resources occupied by the service are released during service recovery. Then, the path calculation algorithm is called to calculate a path that is completely unrelated to the faulty service, and then the path recovery is completed. Since the recovered path is completely unrelated to the initial path, the reliability and fault tolerance of the service can be effectively improved. The dynamic recovery feature also greatly improves the network resource utilization rate.

[0039] 6) Service Deletion: When cross-domain services are canceled or adjusted, the services should be deleted promptly to release limited network resources. When deleting a service, first enter the service configuration interface of the integrated network management unit, select the service to be deleted, click the delete option, and click confirm in the pop-up deletion warning box to complete the deletion operation. After the service deletion command is issued, the integrated network management unit will send the command to the information and communication function unit. The information and communication function unit will then send the deletion command to the OTN adaptation units of each vendor domain involved. Each vendor domain OTN adaptation unit will parse the command information and convert it into information that can be recognized by the vendor network elements. Then, it will forward it to the vendor network management and equipment network elements and wait for the network elements to respond and reply. The response information will be forwarded to the integrated network management unit through each vendor domain OTN adaptation unit. After receiving the information, the integrated network management unit will update the service information and traffic engineering database and indicate that the service has been successfully deleted.

[0040] The OTN adaptation units for each vendor are primarily used to convert the control information, management information, and signaling formats of OTN devices from various vendors into a unified information format that can be recognized and processed by the integrated network management unit (IMU). They also convert the control information, management information, and signaling formats issued by the IMU into information formats that can be recognized and processed by the OTN devices from various vendors, thereby achieving unified and interoperable signaling information across the entire network. Specifically:

[0041] The integrated network management information transceiver unit realizes the reception and transmission of information such as route establishment, route disconnection, query, synchronization, alarm, link status, and topology of the integrated network management, and sends the response information of the manufacturer's equipment to the integrated network management unit;

[0042] The information conversion function unit enables bidirectional conversion between information from the integrated network management unit and information from manufacturer equipment, ensuring information exchange and communication.

[0043] The information filtering function unit filters a large amount of manufacturer equipment information to ensure that the necessary instruction information is converted, reducing unnecessary information transmission and processing, and improving the efficiency of dynamic allocation of network resources of the entire system.

[0044] The manufacturer's information transmission and reception function unit sends the information issued by the integrated network management unit to the device and sends the device's response information back to the integrated network management unit.

[0045] The integrated network management unit (IMU) enables rapid deployment of OTN cross-domain services through unified maintenance of the entire network topology, resources, and signaling. The IMU interacts with equipment from various vendors through the information and communication function unit to understand available network resources, dynamically update the topology and traffic engineering database, and maintain synchronization with vendor equipment resource databases. This achieves comprehensive network topology presentation and management. The traffic engineering database maintains port, link, and wavelength information for each vendor's equipment domain across the network and updates it in real time based on network conditions. This provides accurate resource information to the path calculation function unit, improving routing success rates and maintaining resource synchronization between the integrated network management traffic database and the network management information of each vendor's equipment. Specifically:

[0046] The business configuration function unit is responsible for establishing and deleting business connections across vendor domains, providing operators with a convenient and clear operating method;

[0047] The path calculation function unit calculates the required cross-domain path based on the resource data in the traffic engineering database according to the business configuration requirements. On the other hand, when a cross-domain link fails and causes a business interruption, it quickly triggers the recovery mechanism to recalculate a path that is completely unrelated to the failed business based on the traffic engineering database, ensuring the rapid recovery of cross-domain business.

[0048] The link management function unit mainly realizes the maintenance and updating of network topology links and the management of cross-domain paths, and monitors and reports link alarms and service connectivity status in real time.

[0049] The power-off configuration saving function unit mainly realizes the saving of network service configuration information when the integrated network management system is shut down or restarted, so as to prevent the situation where historical configurations cannot be known when the network management system is shut down or restarted, which would cause difficulties in the maintenance and management of historical services and waste of resources.

[0050] The alarm and performance management function unit monitors the status information of links, ports, services, and device nodes, ensuring that network maintenance personnel can keep abreast of the network situation and guarantee stable network operation.

Claims

1. A method for interoperability of multi-vendor OTN devices, the method being applicable to networks established by interconnecting OTN adaptation units and integrated network management units from various vendors, wherein, Each vendor domain OTN adaptation unit is equipped with sequentially connected integrated network management information transceiver unit, information conversion unit, information filtering unit, and vendor equipment information transceiver unit. The integrated network management information transceiver unit is connected to the integrated network management unit, and the vendor equipment information transceiver unit is connected to the vendor equipment. The integrated network management unit includes user management unit, domain configuration unit, information communication unit, service configuration unit, path calculation unit, traffic engineering unit, link management unit, power-down configuration saving unit, alarm and performance management unit, and topology management unit. The method is characterized by the following steps: 1) Network Deployment: Without changing the physical network deployment of OTN, connect the OTN adapter units of each vendor to the corresponding domain, and connect the OTN adapter units of each vendor domain to the integrated network management unit. According to the network plan, change the corresponding network segment and IP information of the OTN adapter units of each vendor domain, and add the corresponding communication IP and network segment to the integrated network management unit. The integrated network management unit, the OTN adapter units of each vendor domain, and the vendor equipment are on the same network segment. 2) Network configuration: Manually verify and ensure the connectivity of inter-domain links, make corresponding configurations in the integrated network management unit according to the actual network situation, and modify the network management front-end configuration file according to the network connection situation. The front-end configuration file includes the domain configuration file, inter-domain link configuration file, link list configuration file, node list configuration file, and topology basic information configuration file. 3) Network Debugging: Following the actual network plan and correct configuration, first, ping each vendor's domain OTN adapter unit and vendor's network element via the network management host. If connectivity is normal, proceed to the next step; otherwise, check the physical connections and IP configurations for correctness. Next, check if the inter-domain link configurations and physical connections are consistent, and check link connectivity and loss. If everything is correct, proceed to the next step. Then, view the network topology information for each domain on the integrated network management unit. If the network topology information is incomplete, or if the network topology information displayed on the integrated network management unit is inconsistent with the actual topology, review the network management front-end configuration file and check the settings of each vendor. Prepare the network management unit and manually check any missing nodes or links according to the manufacturer's network management prompts to ensure that the integrated network management topology is consistent with the physical network. Finally, restart the integrated network management unit and check whether the network topology and inter-domain links are consistent with the current network plan. If they are consistent, disconnect the optical port laser at the link end on the manufacturer's network management unit and check whether the integrated network management unit receives an alarm and whether the link status shows as disconnected. If both are received, restart the laser and check whether the link alarm is restored and whether the link status returns to normal connection. If all the above operations are normal, the network debugging is complete. Otherwise, continue to check and repeat the above operations until the debugging results are consistent with expectations. 4) Service Activation: Services are activated through the integrated network management unit (IMU). This includes cross-domain services and services within a single vendor's domain. Activation of intra-domain services is performed on the vendor's network management interface, while cross-domain services are activated on the IMU. During service activation, first access the IMU's service configuration interface. Based on the planned service activation, select the corresponding port, wavelength, and rate parameters. If a port is unavailable, it indicates that the port resource is unavailable. Check the interface of the corresponding vendor's network element to see if it already has services and adjust the plan accordingly. If everything is normal, the service configuration is issued. The IMU's backend sends the configuration command to the path calculation function unit, which first updates and queries the traffic engineering data. The database calculates the service path based on the latest resource information across the entire network and distributes the specific service configuration information to the information communication function unit. The information communication function unit then distributes the configuration information to the OTN adaptation units of each vendor domain involved. Each vendor domain OTN adaptation unit parses the information and converts it into information that can be recognized by the vendor network elements, and then forwards it to the vendor network management and device network elements, waits for the network element's response, and forwards the response information to the integrated network management unit through each vendor domain OTN adaptation unit. After receiving the information, the integrated network management unit updates the service information and traffic engineering database and informs that the service has been successfully established. Once the service is successfully established, a loopback is established on one end port of the service, and a network tester is connected to the other end port for inspection and verification. 5) Service recovery: When a cross-domain service fails, the integrated network management unit will immediately pop up an alarm prompt based on the received fault information, display the faulty service as interrupted on the integrated network management unit, and trigger the service recovery mechanism. When the service is restored, the faulty service is first deleted and the resources occupied by the service are released. Then, the path calculation algorithm is called to calculate a path that is completely unrelated to the faulty service, and then the path is restored. 6) Service Deletion: When deleting a service, first enter the service configuration interface of the integrated network management unit, select the service to be deleted, click the delete option, and click confirm in the pop-up deletion warning box to complete the deletion operation. After the service deletion command is issued, the integrated network management unit will send the command to the information and communication function unit. The information and communication function unit will then send the deletion command to the relevant vendor domain OTN adaptation units. Each vendor domain OTN adaptation unit will parse the command information and convert it into information that can be recognized by the vendor network elements. Then, it will forward it to the vendor network management and equipment network elements and wait for the network elements to respond and reply. The response information will be forwarded to the integrated network management unit through each vendor domain OTN adaptation unit. After receiving the information, the integrated network management unit will update the service information and traffic engineering database and indicate that the service has been successfully deleted.

Images