Network scheduling method and apparatus
By pre-storing topology feature codes in optical modules, the scheduling device automatically obtains the connection method of optical modules and generates a target topology table. This solves the problem that OCS devices cannot actively perceive the status of optical modules, realizes automatic recognition and dynamic adjustment of network topology, and improves the efficiency and reliability of network scheduling.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- SHANGHAI HODE INFORMATION TECH CO LTD
- Filing Date
- 2026-03-13
- Publication Date
- 2026-06-09
AI Technical Summary
OCS devices cannot actively sense the status of optical modules in optical transmission networks, resulting in the network topology being opaque to OCS devices. This requires manual reconfiguration, which is time-consuming, labor-intensive, and prone to errors.
By pre-storing topology feature codes in optical modules, the scheduling device automatically obtains the connection mode of the optical modules, generates a target topology table, and realizes automatic recognition and dynamic adjustment of network topology.
It improves the transparency of network topology to scheduling equipment and the efficiency of scheduling equipment in recognizing network topology, enhances the utilization rate of optical module storage resources, shortens network adjustment response time, and improves network reliability.
Smart Images

Figure CN121842559B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of network communication technology, and in particular to a network scheduling method, apparatus, computer equipment, computer-readable storage medium, computer program product, and system. Background Technology
[0002] In optical transmission networks, the OCS (Optical Cross-Connect) device, acting as a pure optical cross-connect system, only possesses optical signal switching capabilities and does not carry optical modules. Optical modules are deployed on the network layer devices at both ends to perform photoelectric conversion. When establishing an optical transmission network, the OCS device relies on manually entering the "cross-connect port - optical module port" mapping to build the topology table, and cannot proactively perceive the status of optical modules. This makes the network topology opaque to the OCS device, resulting in low efficiency in topology recognition. When optical modules are plugged in or removed, or ports are changed, the network topology table must be manually reconfigured, which is time-consuming, labor-intensive, and prone to errors.
[0003] It should be noted that the above content is not necessarily prior art, nor is it intended to limit the scope of patent protection of this application. Summary of the Invention
[0004] This application provides a network scheduling method, apparatus, computer device, computer-readable storage medium, and computer program product to solve or alleviate one or more of the technical problems mentioned above.
[0005] One aspect of this application provides a network scheduling method applied to a scheduling device, the scheduling device being used to connect a first optical module and a second optical module, the method comprising:
[0006] Obtain a first topology feature code from the first optical module and a second topology feature code from the second optical module; the first topology feature code includes a field describing the connection method between the scheduling device and the first optical module; the second topology feature code includes a field describing the connection method between the scheduling device and the second optical module.
[0007] Generate a target topology table based on the first topology feature code and the second topology feature code;
[0008] According to the target topology table, connect the first optical module and the second optical module.
[0009] Optionally, the first optical module is deployed on a first network layer device, and the second optical module is deployed on a second network layer device;
[0010] The first topological feature code includes:
[0011] The device identifier of the first network layer device, the port identifier of the first optical module on the first network layer device, the port identifier of the first optical module associated with the scheduling device, and the connection information between the second optical module and the scheduling device;
[0012] The second topological feature code includes:
[0013] The device identifier of the second network layer device, the port identifier of the second optical module on the second network layer device, the port identifier of the second optical module associated with the scheduling device, and the connection information between the first optical module and the scheduling device.
[0014] Optionally, the method further includes:
[0015] Obtain the updated first topological feature code and / or the updated second topological feature code;
[0016] The target topology table is updated based on the updated first topology feature code and / or the updated second topology feature code.
[0017] Optionally, the first optical module and the second optical module are coupled through a first optical path, and the first optical path has a corresponding priority; the first topology feature code includes the optical module status identifier of the first optical module, and the second topology feature code includes the optical module status identifier of the second optical module; updating the target topology table according to the updated first topology feature code and / or the updated second topology feature code includes:
[0018] If the optical module status identifier of the first optical module and / or the optical module status identifier corresponding to the second optical module are abnormal, the second optical path is determined from the target topology table according to the priority corresponding to the first optical path; wherein, the second optical path is used to couple the first backup optical module and the second backup optical module;
[0019] An adjustment command is sent to the first backup optical module and the second backup optical module to connect the first backup optical module and the second backup optical module;
[0020] If the first backup optical module and the second backup optical module are successfully connected, the target topology table is updated.
[0021] Optionally, when an adjustment command is issued to the first backup optical module and the second backup optical module, if the first backup optical module returns a confirmation signal in response to the adjustment command, the first backup optical module sets its own module status flag to be adjusted; if the second backup optical module returns a confirmation signal in response to the adjustment command, the second backup optical module sets its own module status flag to be adjusted.
[0022] When the first backup optical module and the second backup optical module are successfully connected, the first backup optical module sets its module status indicator to normal, and the second backup optical module sets its module status indicator to normal.
[0023] Optionally, the method further includes:
[0024] Receive a service scheduling instruction, the service scheduling instruction being used to connect a first target optical module and a second target optical module;
[0025] Obtain the first target topology feature code from the first target optical module and the second target topology feature code from the second target optical module;
[0026] The target topology table is updated based on the first target topology feature code and the second target topology feature code;
[0027] Once the target topology table is updated, connect the first target optical module and the second target optical module.
[0028] Optionally, the service scheduling instruction includes a port identifier associated with the first target optical module and a port identifier associated with the second target optical module on the scheduling device;
[0029] Connecting the first target optical module and the second target optical module includes:
[0030] A third optical path connection is established between the port corresponding to the port identifier associated with the first target optical module on the scheduling device and the port corresponding to the port identifier associated with the second target optical module on the scheduling device.
[0031] Another aspect of this application provides a network scheduling device applied to a scheduling equipment, the scheduling equipment being connected to a first optical module and a second optical module, the device comprising:
[0032] The acquisition module is used to acquire a first topology feature code in the first optical module and a second topology feature code in the second optical module; the first topology feature code includes a field describing the connection method between the scheduling device and the first optical module; the second topology feature code includes a field describing the connection method between the scheduling device and the second optical module.
[0033] The generation module is used to generate a target topology table based on the first topology feature code and the second topology feature code;
[0034] The scheduling module is used to connect the first optical module and the second optical module according to the target topology table.
[0035] Another aspect of this application provides a computer device, including:
[0036] At least one processor; and
[0037] A memory that is communicatively connected to the at least one processor;
[0038] Wherein: the memory stores instructions that can be executed by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the method as described above.
[0039] Another aspect of this application provides a computer-readable storage medium storing computer instructions that, when executed by a processor, implement the method described above.
[0040] Another aspect of this application provides a computer program product including a computer program that, when executed by a processor, implements the method described above.
[0041] Another aspect of this application provides a network scheduling system, including:
[0042] The control terminal is used to write or update the topology feature code to the writable storage area of the optical module.
[0043] At least two network layer devices, each of which is equipped with an optical module, an information transmission module and a status monitoring module. The information transmission module is used to transmit data between the optical module and the scheduling device, and the status monitoring module is used to monitor the working status of the optical module and update the module status identifier in the topology feature code.
[0044] The scheduling device connects to the optical modules in the at least two network layer devices and to the control terminal;
[0045] The scheduling device includes:
[0046] (1) Topology information interaction module, used to obtain the topology feature code in each optical module and send adjustment instructions to each optical module;
[0047] (2) Topology management module, used to generate target topology table based on the acquired topology feature code, and periodically monitor topology status;
[0048] (3) Adjustment control module, used to adjust optical path connection according to the target topology table when topology anomaly is detected or service scheduling instruction is received, the service scheduling instruction is used to connect the first target optical module and the second target optical module.
[0049] Optionally, the control terminal is also used to issue the service scheduling instruction to the scheduling device.
[0050] The embodiments of this application employing the above technical solution may include the following advantages: the scheduling device obtains the network connection methods from the topology feature codes pre-stored in the optical modules to construct a target topology table, thereby realizing optical path scheduling. By using the topology feature codes pre-stored in the optical modules, the scheduling device automatically recognizes the network topology, improving the transparency of the network topology to the scheduling device and the efficiency of the scheduling device's network topology recognition, as well as improving the utilization rate of storage resources in the optical modules. Simultaneously, the automatically generated target topology table allows the scheduling device to grasp the relationships between optical modules in real time, thereby realizing dynamic network adjustments, improving the response speed of network adjustments (scheduling), and the reliability of the network. Attached Figure Description
[0051] The accompanying drawings exemplify embodiments and form part of the specification, serving together with the textual description to explain exemplary implementations of the embodiments. The illustrated embodiments are for illustrative purposes only and do not limit the scope of the claims. Throughout the drawings, the same reference numerals refer to similar but not necessarily identical elements.
[0052] Figure 1 This diagram schematically illustrates the operating environment of the network scheduling method according to Embodiment 1 of this application;
[0053] Figure 2 A flowchart illustrating a network scheduling method according to Embodiment 1 of this application is shown schematically.
[0054] Figure 3 The diagram illustrates a new addition to the network scheduling method according to Embodiment 1 of this application;
[0055] Figure 4 Schematic illustration Figure 3 Flowchart of the sub-steps in step S302;
[0056] Figure 5 This schematically illustrates another additional flowchart of the network scheduling method according to Embodiment 1 of this application;
[0057] Figure 6 An exemplary application flowchart of the network scheduling method according to Embodiment 1 of this application is illustrated;
[0058] Figure 7 A block diagram of a network scheduling device according to Embodiment 2 of this application is schematically shown; and
[0059] Figure 8 A schematic diagram of the hardware architecture of a computer device according to Embodiment 3 of this application is shown. Detailed Implementation
[0060] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.
[0061] It should be noted that the descriptions involving "first," "second," etc., in the embodiments of this application are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of that feature. Furthermore, the technical solutions of the various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. If the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed in this application.
[0062] It should be noted that, in any stage of this application involving the collection, storage, use, transmission, and processing of data, each stage strictly adheres to the laws, regulations, industry standards, and regulatory requirements of the data source, usage location, and relevant countries and regions to ensure the legality and compliance of data activities. In the collection stage, the purpose, method, and scope of collection are clearly communicated to the data subject in a prominent manner. Collection is conducted only after obtaining the data subject's legal authorization, ensuring that the collection process follows the "minimum necessary" principle and does not exceed the scope of data collection. In the storage stage, storage periods are limited, and data is promptly deleted or anonymized / encrypted after the storage purpose is achieved. In the usage stage, a strict data security protection mechanism is implemented, using field-level desensitization technology and processing the original data according to preset desensitization rules. For different types of data, multiple desensitization strategies, such as data generalization, data anonymization, and data encryption, are employed to effectively mitigate the risk of sensitive information leakage and ensure that all data used is securely processed and desensitized, comprehensively protecting the rights and interests of data subjects and data security. In the transmission and processing stages, the confidentiality and security of data are ensured during transmission and processing.
[0063] In the description of this application, it should be understood that the numerical labels before the steps do not indicate the order of the steps, but are only used to facilitate the description of this application and to distinguish each step, and therefore should not be construed as a limitation of this application.
[0064] First, a definition of the terminology used in this application is provided:
[0065] OCS (Optical Circuit Switch): A pure optical layer switching device that enables direct switching and routing of optical signals between different ports through an optical cross-connect matrix.
[0066] Optical cross-connect matrix: A functional component of an OCS device used to realize physical layer cross-connection and routing scheduling of optical signals between different input and output ports.
[0067] Network layer devices: Hardware carriers for deploying optical modules, including switches, routers, OTN terminals, etc.
[0068] Optical module: An optoelectronic conversion device deployed on network layer equipment to realize the mutual conversion between electrical signals and optical signals.
[0069] EEPROM: Electrically Erasable Programmable Read-Only Memory, a type of non-volatile memory that allows data to be repeatedly erased and written via electrical signals.
[0070] SFP (Small Form-factor Pluggable): A compact, hot-pluggable optical transceiver module used to convert between electrical and optical signals.
[0071] QSFP (Quad Small Form-factor Pluggable): A compact, hot-pluggable optical module packaging standard that supports four channels of high-speed data transmission.
[0072] Topology: The overall structural layout of network devices and their connections, including the connection mapping between the cross-connect ports of the OCS device and the optical module ports on the network layer devices at both ends.
[0073] Optical transmission network: a high-speed communication network that uses optical fiber as the transmission medium and optical signals as the information carrier.
[0074] AES (Advanced Encryption Standard): A symmetric block cipher algorithm that uses 128-bit block lengths and encrypts data through a multi-round substitution-permutation network.
[0075] I2C (Inter-Integrated Circuit): A serial, half-duplex, multi-master, multi-slave short-distance communication interface that enables bidirectional data transmission between devices through two signal lines: SDA (serial data line) and SCL (serial clock line).
[0076] OTN (Optical Transport Network) terminal: A network layer device based on optical transport network technology, used to realize the mutual conversion between electrical signals and optical signals.
[0077] Switch: A network layer device that operates at the data link layer or network layer of the OSI model. It forwards data packets from the source port to the destination port by parsing the MAC address or IP address in the data frame.
[0078] Router: A network layer device used to forward data packets between different networks. It determines the optimal path for data forwarding by querying a routing table, thereby enabling network interconnection and communication.
[0079] CRC (Cyclic Redundancy Check): An error detection technique based on polynomial division. It generates a fixed-length check code by performing modulo-2 division on the data and appends it to the data. The receiver verifies the data using the same algorithm. If the remainder is not zero, it is determined that there is an error in the transmission.
[0080] Secondly, to facilitate understanding of the technical solutions provided in the embodiments of this application by those skilled in the art, the relevant technologies are described below:
[0081] Optical Controllers (OCS) are the core scheduling devices in optical transmission networks, primarily responsible for cross-connection, routing scheduling, and resource allocation of optical paths at the optical layer. The OCS itself only has the capability to switch and combine optical signals and does not carry optical modules. The core component of photoelectric conversion—the optical module—is deployed on network layer devices (such as routers, OTN terminals, or switches) at both ends of the OCS to support the connection of optical links.
[0082] However, due to the physical separation of OCS and optical modules, OCS relies primarily on manual configuration and static synchronization with external network management systems for topology awareness and link adjustment. This leads to frequent manual reconfiguration when port changes, plugging / unplugging, or device migration occur, which is not only time-consuming and labor-intensive but also prone to port correspondence errors or information omissions, resulting in scheduling mistakes. Furthermore, in the event of optical module failure or link interruption, maintenance personnel must manually check the status of both ends before issuing cross-connection commands. This manual intervention mode typically results in response times in the minute range. Moreover, although optical modules have built-in writable storage areas such as EEPROM, they currently only store basic hardware information such as manufacturer and wavelength, not related to the topology management requirements of OCS, preventing the optical modules from providing effective topology awareness support for OCS. Furthermore, because OCS cannot actively obtain the real-time status of the optical modules at both ends (such as failure or offline status), it struggles to identify topology anomalies when optical modules malfunction, easily leading to hidden faults such as "internal cross-connection normal but actual optical path not working."
[0083] Therefore, this application provides a network scheduling technical solution. In this technical solution, (1) the scheduling device automatically recognizes the network topology by using the topology feature code pre-stored in the optical module, which improves the transparency of the network topology to the scheduling device and the efficiency of the scheduling device in recognizing the network topology, and also improves the utilization rate of the storage resources in the optical module; (2) the automatically generated target topology table enables the scheduling device to grasp the relationship between optical modules in real time, thereby realizing the dynamic adjustment of the network, improving the response speed of network adjustment and the reliability of the network; (3) by monitoring the status flag of the optical module in real time and combining the optical path priority to switch the second optical path to update the target topology table, the connection action of the backup optical module and the logical topology record are linked in real time, thereby improving the efficiency of automated processing from anomaly detection to link reconstruction and the consistency of topology status while prioritizing the continuity of high-priority services; (4) the connection of the first target optical module and the second target optical module is realized according to the service scheduling command, which improves the flexibility and automation of network scheduling, shortens the response cycle of network scheduling, and ensures the accuracy and consistency of topology information in network scheduling. See the following text for details.
[0084] Finally, for ease of understanding, an exemplary operating environment is provided below.
[0085] like Figure 1 As shown in the diagram, the operating environment includes: scheduling device 2, network layer devices (4A and 4B), and control terminal 6.
[0086] Dispatching device 2 can connect to network layer devices 4A and 4B via optical links. Dispatching device 2 can be a single optical cross-connect device (such as an OCS device). Dispatching device 2 can provide optical cross-connect services to network layer devices. Dispatching device 2 can provide services via an optical transmission network. The optical transmission network includes various optical network devices, such as optical amplifiers, dispersion compensators, optical add-drop multiplexers (OADMs), optical cross-connectors, optical terminal multiplexers, optical line protection devices, etc. The optical transmission network can include physical optical links, such as single-mode fiber links, multimode fiber links, fiber bundle links, and combinations thereof, or wireless optical links, such as free-space optical communication (FSO) links.
[0087] Network layer devices (4A and 4B) can be configured to interact with scheduling device 2 for optical signal exchange and service data transmission. Network layer devices 4A and 4B may include hardware carriers for deploying optical modules, such as routers, switches, OTN terminals, WDM terminals, etc., and may also include virtualized network function instances. Network layer devices (4A and 4B) include optical modules, which may have built-in writable storage areas (such as EEPROM) for storing topology signatures, etc.
[0088] Control terminal 6 can be a single computer, a network management terminal, a network management server cluster, or a network management cloud platform, etc. Control terminal 6 can communicate with scheduling device 2 and network layer devices (4A and 4B) via the management network. Control terminal 6 can be used to visually display the topology table, optical module status information, and adjustment records of scheduling device 2, issue service scheduling commands, and receive alarm information from scheduling device 2, etc. Control terminal 6 may also include a coding module for writing and updating topology feature codes to the optical modules on network layer devices 4A and 4B, etc.
[0089] It should be noted that the above-mentioned equipment is exemplary, and the number and type of equipment can be adjusted in different scenarios or according to different needs.
[0090] The technical solutions of this application are described below through several embodiments. It should be understood that these embodiments can be implemented in many different forms and should not be construed as being limited to the embodiments set forth herein.
[0091] Example 1
[0092] This method embodiment can be executed in a scheduling device, which is used to connect the first optical module and the second optical module. The scheduling device will be considered the single execution entity in this process below.
[0093] Figure 2 A flowchart illustrating a network scheduling method according to Embodiment 1 of this application is shown.
[0094] like Figure 2 As shown, the network scheduling method may include steps S200~S204, wherein:
[0095] Step S200: Obtain the first topology feature code in the first optical module and the second topology feature code in the second optical module; the first topology feature code includes a field describing the connection method between the scheduling device and the first optical module; the second topology feature code includes a field describing the connection method between the scheduling device and the second optical module.
[0096] Step S202: Generate a target topology table based on the first topology feature code and the second topology feature code.
[0097] Step S204: Connect the first optical module and the second optical module according to the target topology table.
[0098] The network scheduling method provided in this embodiment involves a scheduling device obtaining network connection methods from topology feature codes pre-stored in optical modules to construct a target topology table, thereby achieving optical path scheduling. By using the topology feature codes pre-stored in the optical modules, the scheduling device automatically recognizes the network topology, improving the transparency of the network topology to the scheduling device and the efficiency of the scheduling device's network topology recognition, as well as increasing the utilization rate of storage resources in the optical modules. Simultaneously, the automatically generated target topology table allows the scheduling device to grasp the relationships between optical modules in real time, thereby enabling dynamic network adjustments and improving the response speed and reliability of network adjustments. Furthermore, this embodiment can achieve network scheduling without changing the hardware architecture of the network scheduling system, only expanding the write code content stored in the optical modules, using the topology feature codes in the expanded write code content to achieve network scheduling, improving the versatility of the network scheduling method and reducing application costs.
[0099] The following combination Figure 2 The steps in steps S200 to S204, as well as other optional steps, are described in detail.
[0100] Step S200 The system obtains a first topology feature code from the first optical module and a second topology feature code from the second optical module. The first topology feature code includes a field describing the connection method between the scheduling device and the first optical module. The second topology feature code includes a field describing the connection method between the scheduling device and the second optical module.
[0101] The scheduling device can be an OCS (Optical Server System), and the first and second optical modules can be SFP (Optical Prefix) or QSFP (Optical Standard Prefix) optical modules deployed on network layer devices (such as OTN terminals) at both ends of the OCS. The scheduling device and the optical modules can be connected via integrated I2C and Ethernet communication interfaces. The optical modules can send information such as topology feature codes encrypted using methods such as AES to the scheduling device through these interfaces. In some embodiments, the scheduling device can also automatically trigger the acquisition of topology feature codes (including the first and second topology feature codes) in the optical modules (including the first and second optical modules) when powered on, hot-plugged, or when the network is established. In other embodiments, the scheduling device can also poll and read the topology feature codes in the optical modules at preset time intervals (such as 100 milliseconds, 1 second, etc.). The scheduling device can read the complete topology feature code each time it reads, or it can only read the complete topology feature code when a change in the version number or a specific identifier bit of the topology feature code is detected, and only read the version number or specific identifier bit when no change is detected.
[0102] The topology signature includes data written to and stored in the writable storage area of the optical module, used to characterize the connection method between the optical module and the scheduling device, and / or the connection method between the peer optical module and the scheduling device. In some embodiments, the topology signature can be stored in a reserved extended address segment of the built-in memory (such as EEPROM) of the corresponding optical module. The connection method between the optical module and the scheduling device can be recorded in the topology signature through fields such as the device identifier of the network layer device to which the optical module belongs, the port location of the optical module on the network layer device, the port number connected to the optical module on the scheduling device, and the topology information of the peer optical module. In some embodiments, the topology signature may also include several additional information fields, such as the real-time status identifier of the optical module.
[0103] In this embodiment, by pre-storing topology feature codes containing connection method fields in the optical module, the scheduling device can proactively perceive the topology relationships in the network, improving the accuracy and efficiency of the scheduling device in topology cognition, enhancing the transparency and precision of the scheduling device in topology management, and also improving the utilization rate of storage resources in the optical module.
[0104] As mentioned earlier, topological feature codes can record corresponding connection methods through various field combinations. The following provides an example field combination in a topological feature code.
[0105] In an optional embodiment, the first optical module is deployed on a first network layer device, and the second optical module is deployed on a second network layer device. The first topology feature code includes: the device identifier of the first network layer device, the port identifier of the first optical module on the first network layer device, the port identifier associated with the first optical module on the scheduling device, and connection information between the second optical module and the scheduling device. The second topology feature code includes: the device identifier of the second network layer device, the port identifier of the second optical module on the second network layer device, the port identifier associated with the second optical module on the scheduling device, and connection information between the first optical module and the scheduling device.
[0106] Network layer devices (e.g., first network layer device, second network layer device) can be routers or OTN terminals, and the device identifier of a network layer device can be its serial number (SN). In some embodiments, the connection information between the second optical module and the scheduling device may include the device identifier of the second network layer device, the port identifier of the second optical module on the second network layer device, and the port identifier associated with the second optical module on the scheduling device. Similarly, the connection information between the first optical module and the scheduling device can also be set accordingly. It should be noted that the length of each field in the topology feature code can be adjusted according to actual needs.
[0107] Step S202 Based on the first topological feature code and the second topological feature code, a target topology table is generated.
[0108] The target topology table may include a structured data table generated by the scheduling device based on the topology feature codes of one or more optical modules, used to record the association relationships between network layer devices, optical module ports, and scheduling device ports. The scheduling device can generate the target topology table by extracting the connection methods (including optical module device number, port number, etc.) between the optical modules and the scheduling device from the topology feature codes. In some embodiments, the topology feature codes may also include fields describing the connection methods between the peer optical modules and the scheduling device. Before generating the target topology table, the scheduling device may first compare the consistency of the field information in the optical modules at both ends, and only generate the target topology table if consistency is determined. The generated target topology table may be stored in the local cache of the scheduling device and in a network management or control terminal outside the network. The target topology table stored in the local cache or other locations may also be updated by triggering specific conditions. When stored in a network management or control terminal, the target topology table may also be converted into a visual data form (such as a topology map) for visualization.
[0109] In this embodiment, the distributed topology feature code, which includes a connection method description field, is transformed into a structured target topology table, realizing the automated construction and accurate mapping of network topology relationships. By automatically recognizing and generating a target topology table containing global relationships, the lag and error rate caused by manual configuration are reduced, the transparency and accuracy of the scheduling device's network topology perception are improved, and the efficiency and accuracy of the scheduling device in network scheduling are enhanced.
[0110] Step S204 According to the target topology table, the first optical module and the second optical module are connected.
[0111] When the scheduling device is an OCS switch, the optical signal can be switched from the original cross-connect port to the selected target cross-connect port by controlling the optical cross-connect matrix inside the OCS, thus realizing the physical link connection between the first optical module and the second optical module. When the scheduling device is another type of device, the connection between the first optical module and the second optical module can be realized in a corresponding manner.
[0112] In this embodiment, by performing physical layer network connections according to the automatically generated target topology table, it is ensured that the switching of physical links within the scheduling device is consistent with the actual topology mapping relationship of the optical modules at both ends, thereby reducing port or mapping errors that may be caused by manually configuring scheduling commands and improving the efficiency and accuracy of network scheduling.
[0113] As mentioned earlier, the target topology table can also be updated. The following provides an example update method.
[0114] In optional embodiments, such as Figure 3 As shown, the method further includes:
[0115] S300, obtain the updated first topological feature code and / or the updated second topological feature code.
[0116] S302, Update the target topology table according to the updated first topology feature code and / or the updated second topology feature code.
[0117] In some embodiments, when an optical module undergoes physical insertion / removal, port change, or network layer device migration, the corresponding field in its internal topology feature code will be updated. The scheduling device can poll the topology feature codes of each optical module at preset time intervals and compare the obtained topology feature codes or version numbers each time to perceive the update status of the topology feature codes in real time. In some embodiments, the topology feature codes can also be sent to the scheduling device by the optical module periodically or proactively when an update to the topology feature code is detected. After the target topology table is updated, the scheduling device can also send the updated target topology table to network management or control terminals for synchronization or display. By perceiving and synchronizing changes in the topology feature codes within the optical modules in real time to update the target topology table, the time for network topology information perception and import can be reduced, the operation and maintenance costs of network scheduling can be lowered, and the efficiency and accuracy of network topology information import can be improved.
[0118] In practical applications, the target topology table can be updated in various ways. The following provides an exemplary update method.
[0119] In an optional embodiment, the first optical module and the second optical module are coupled (establish an optical path connection) through a first optical path, the first optical path having a corresponding priority, the first topology feature code including the optical module status identifier of the first optical module, and the second topology feature code including the optical module status identifier of the second optical module. For example... Figure 4 As shown, step S302 may include:
[0120] S400, if the optical module status identifier of the first optical module and / or the optical module status identifier corresponding to the second optical module are abnormal, a second optical path is determined from the target topology table according to the priority corresponding to the first optical path, wherein the second optical path is used to couple the first backup optical module and the second backup optical module.
[0121] S402, an adjustment command is sent to the first backup optical module and the second backup optical module to connect the first backup optical module and the second backup optical module.
[0122] S404, if the first backup optical module and the second backup optical module are successfully connected, update the target topology table.
[0123] Optical module status indicators can include normal, abnormal, pending adjustment, offline, etc. The scheduling device can poll the status indicators of each optical module in real time through pre-established connection channels (such as I2C communication). When an optical module status indicator is found to be abnormal, the scheduling device can also send a reporting signal to relevant devices and mark the first optical path as abnormal in the target topology table. The priority of the second optical path determined by the scheduling device can be higher than or equal to the priority of the first optical path. The topology feature code can also include fields such as a command receiving bit. When an optical module does not receive a command from the scheduling device, the content of the command receiving bit can be "no command". The adjustment command can modify the content of the command receiving bit of the topology feature code in the backup optical modules (including the first backup optical module and the second backup optical module) to "optical path switching adaptation". When other commands are received from the scheduling device, the content of the command receiving bit can also be "power calibration", "port disabled", etc. The adjustment command can also update relevant fields of the topology feature code in the backup optical module, such as the identifier of the port connected to it on the scheduling device, and the peer topology association information. In some embodiments, the backup optical module can send an acknowledgment signal to the scheduling device after receiving an adjustment instruction. The scheduling device only performs internal cross-matrix switching to connect the first backup optical module and the second backup optical module upon receiving the acknowledgment signal. When updating the target topology table, the first optical path can be marked as "unavailable" or "abnormally offline," and a notification signal such as "topology change" can be sent to the network management or control terminal.
[0124] In this embodiment, by monitoring the optical module status identifier in real time and combining it with the optical path priority (an identifier used to characterize the priority order of optical paths during scheduling or switching) to switch the second optical path to update the target topology table, the connection action of the backup optical module and the logical topology record are linked in real time. This ensures the continuity of high-priority services while improving the efficiency of automated processing from anomaly detection to link reconstruction and the consistency of topology status.
[0125] During network scheduling, the backup optical module can also adjust its module status flag in real time. The following provides an exemplary module status flag adjustment process.
[0126] In an optional embodiment, when adjustment instructions are issued to the first backup optical module and the second backup optical module:
[0127] (1) If the first backup optical module returns a confirmation signal in response to the adjustment command, the first backup optical module sets its module status flag to pending adjustment.
[0128] (2) If the second backup optical module returns a confirmation signal in response to the adjustment command, the second backup optical module sets its module status flag to pending adjustment.
[0129] If the first backup optical module and the second backup optical module are successfully connected:
[0130] (1) The first backup optical module sets its module status flag to normal.
[0131] (2) The second backup optical module sets its module status flag to normal.
[0132] In some embodiments, the backup optical module can verify the adjustment command using methods such as CRC cyclic redundancy check or hash check, and return an acknowledgment signal when the verification passes. In other embodiments, the adjustment command is encrypted during transmission. In this case, the backup optical module needs to decrypt the received adjustment command and compare the fields such as the scheduling device identifier in the adjustment command. Only after confirming that the command was sent correctly will it return an acknowledgment signal and adjust its own module status identifier. The scheduling device can start a timer after sending the adjustment command. If it does not receive acknowledgment signals from both ends within a preset threshold (e.g., 20ms), it determines that the second optical path is unavailable, automatically triggers an abnormal rollback, cancels the adjustment command, and re-selects the optical path.
[0133] In this embodiment, by switching the module status identifier between the pending adjustment and normal states, setting the module status identifier to pending adjustment in the initial stage of adjustment can prevent switching to the second optical path before the backup optical module is ready; setting it to normal after successful adjustment completes the final confirmation of the availability of the second optical path, thereby improving the reliability and response speed of network scheduling.
[0134] In addition to the network scheduling that responds to the optical module status as described above, the scheduling device can also proactively perform network scheduling upon receiving corresponding instructions. An exemplary scheduling method is provided below.
[0135] In optional embodiments, such as Figure 5 As shown, the method further includes:
[0136] S500, receive a service scheduling instruction, the service scheduling instruction being used to connect the first target optical module and the second target optical module.
[0137] S502, obtain the first target topology feature code in the first target optical module and the second target topology feature code in the second target optical module.
[0138] S504, Update the target topology table according to the first target topology feature code and the second target topology feature code.
[0139] S506, after the target topology table is updated, connect the first target optical module and the second target optical module.
[0140] Service scheduling instructions can originate from the visual interface of a network management or control terminal, automated scripts, etc. These instructions may include the connection method between the target optical module (including a first target optical module and a second target optical module) and the scheduling device, as well as the priority of the optical path between the first and second target optical modules. In some embodiments, after receiving a service scheduling instruction, the scheduling device can retrieve the occupancy status of the target optical modules in the current target topology table. If the target optical module is already occupied, the priority of the optical path occupied by the current target optical module can be compared with the priority in the service scheduling instruction. If the priority in the service scheduling instruction is higher, the target optical module can be preempted. After the first and second target optical modules are successfully connected, the updated target topology table can be synchronized to the source device or terminal of the service scheduling instruction for visual display.
[0141] In this embodiment, the connection between the first target optical module and the second target optical module is realized in response to the service scheduling command, which improves the flexibility and automation of network scheduling, shortens the response cycle of network scheduling, and ensures the accuracy and consistency of topology information in network scheduling.
[0142] In practical implementation, the connection between the first target optical module and the second target optical module can be achieved in various ways. An exemplary connection method is provided below.
[0143] In an optional embodiment, the service scheduling instruction includes a port identifier associated with the first target optical module and a port identifier associated with the second target optical module on the scheduling device. S506 includes: establishing a third optical path connection between the port corresponding to the port identifier associated with the first target optical module on the scheduling device and the port corresponding to the port identifier associated with the second target optical module on the scheduling device.
[0144] The scheduling device can control its internal optical cross matrix and adjust the tilt angle of the micromirrors to achieve beam deflection and alignment, guiding the optical signal input from the first target optical module to the port output to the second target optical module, thereby establishing a third optical path connection.
[0145] To make this application easier to understand, the following is combined with... Figure 6 An example application is provided. Wherein:
[0146] S1: Set up a scheduling device (OCS-100G-32P) in the metropolitan area network optical transmission system and connect it to the first network layer device (OTN001) and the second network layer device (OTN002) respectively.
[0147] S2: Deploy the first optical module on the 0 / 1 / 0 port of the first network layer device, and deploy the second optical module on the 0 / 1 / 0 port of the second network layer device.
[0148] S3: Write the first topology feature code to the first optical module, which includes the device identifier (OTN001_SN123456), port identifier (0 / 1 / 0), associated port identifier (OCS-P01), and peer connection information (OTN002_SN654321_0 / 1 / 0_OCS-P02); write the second topology feature code to the second optical module, which includes the device identifier (OTN002_SN654321), port identifier (0 / 1 / 0), associated port identifier (OCS-P02), and peer connection information (OTN001_SN123456_0 / 1 / 0_OCS-P01).
[0149] S4: The scheduling device obtains the first topology feature code in the first optical module and the second topology feature code in the second optical module through the Ethernet interface.
[0150] S5: The scheduling device parses the associated fields in the feature code, automatically generates the target topology table, and establishes "OCS-P01". OTN001_0 / 1 / 0 OTN002_0 / 1 / 0 The association of "OCS-P02".
[0151] S6: The scheduling device issues instructions according to the target topology table and physically connects the first optical module and the second optical module through the internal cross matrix.
[0152] S7: The scheduling equipment monitors the optical module status identifier in the first topology feature code in real time and finds that the status of the first optical module is "abnormal" (identified as 1).
[0153] S8: The scheduling device identifies the priority A corresponding to the faulty optical path and selects a backup link with matching priority from the target topology table as the second optical path.
[0154] S9: The scheduling device determines the first and second backup optical modules located at ports 0 / 1 / 2.
[0155] S10: The scheduling equipment sends adjustment instructions to the first backup optical module and the second backup optical module, and writes the "OCS instruction receiving bit" into the "optical path switching adaptation" instruction.
[0156] S11: Both the first backup optical module and the second backup optical module return an acknowledgment signal in response to the command and set their respective module status flags to "to be adjusted" (flag number 2).
[0157] S12: After receiving the confirmation signal, the scheduling equipment controls the cross-matrix to switch the service signal to the port corresponding to the backup optical module (OCS-P03 and OCS-P04).
[0158] S13: After a successful connection, the scheduling device updates the module status flag of the backup optical module to "normal" (flag is 0) and updates the target topology table.
[0159] S14: The scheduling device receives a service scheduling instruction, which requests a new service with priority B (priority B > priority A) to connect the first target optical module (OTN001_0 / 1 / 3) and the second target optical module (OTN002_0 / 1 / 3).
[0160] S15: The scheduling device obtains the target topology feature code pre-written in the first target optical module and the second target optical module.
[0161] S16: The scheduling device parses the associated port identifiers (OCS-P05, OCS-P06) in the target feature code and updates the target topology table accordingly.
[0162] S17: After the target topology table is updated, the scheduling device establishes a third optical path connection between OCS-P05 and OCS-P06 to complete the service deployment.
[0163] Example 2
[0164] Figure 7 A block diagram of a network scheduling device according to Embodiment 2 of this application is schematically shown. This device is applied to a scheduling equipment, which is connected to a first optical module and a second optical module. The device can be divided into one or more program modules. One or more program modules are stored in a storage medium and executed by one or more processors to complete the embodiments of this application. The program module referred to in the embodiments of this application refers to a series of computer program instruction segments capable of performing a specific function. The following description will specifically introduce the functions of each program module in this embodiment. For example... Figure 7 As shown, the device 1000 may include: an acquisition module 1100, a generation module 1200, and a scheduling module 1300, wherein:
[0165] The acquisition module 1100 is used to acquire a first topology feature code in the first optical module and a second topology feature code in the second optical module; the first topology feature code includes a field describing the connection method between the scheduling device and the first optical module; the second topology feature code includes a field describing the connection method between the scheduling device and the second optical module.
[0166] The generation module 1200 is used to generate a target topology table based on the first topology feature code and the second topology feature code;
[0167] The scheduling module 1300 is used to connect the first optical module and the second optical module according to the target topology table.
[0168] As an optional embodiment, the first optical module is deployed on a first network layer device, and the second optical module is deployed on a second network layer device; the first topology feature code includes:
[0169] The device identifier of the first network layer device, the port identifier of the first optical module on the first network layer device, the port identifier of the first optical module associated with the scheduling device, and the connection information between the second optical module and the scheduling device;
[0170] The second topology feature code includes: the device identifier of the second network layer device, the port identifier of the second optical module on the second network layer device, the port identifier of the second optical module associated with the scheduling device, and the connection information between the first optical module and the scheduling device.
[0171] As an optional embodiment, the device 1000 further includes an update module, the update module being used for:
[0172] Obtain the updated first topological feature code and / or the updated second topological feature code;
[0173] The target topology table is updated based on the updated first topology feature code and / or the updated second topology feature code.
[0174] As an optional embodiment, the first optical module and the second optical module are coupled through a first optical path, and the first optical path has a corresponding priority; the first topology feature code includes the optical module status identifier of the first optical module, the second topology feature code includes the optical module status identifier of the second optical module, and the device 1000 further includes an anomaly response module, which is used for:
[0175] If the optical module status identifier of the first optical module and / or the optical module status identifier corresponding to the second optical module are abnormal, the second optical path is determined from the target topology table according to the priority corresponding to the first optical path; wherein, the second optical path is used to couple the first backup optical module and the second backup optical module;
[0176] An adjustment command is sent to the first backup optical module and the second backup optical module to connect the first backup optical module and the second backup optical module;
[0177] If the first backup optical module and the second backup optical module are successfully connected, the target topology table is updated.
[0178] As an optional embodiment, when an adjustment command is issued to the first backup optical module and the second backup optical module, if the first backup optical module returns a confirmation signal in response to the adjustment command, the first backup optical module sets its own module status identifier to be adjusted; if the second backup optical module returns a confirmation signal in response to the adjustment command, the second backup optical module sets its own module status identifier to be adjusted.
[0179] When the first backup optical module and the second backup optical module are successfully connected, the first backup optical module sets its module status indicator to normal, and the second backup optical module sets its module status indicator to normal.
[0180] As an optional embodiment, the device 1000 further includes a service scheduling module, which is used for:
[0181] Receive a service scheduling instruction, the service scheduling instruction being used to connect a first target optical module and a second target optical module;
[0182] Obtain the first target topology feature code from the first target optical module and the second target topology feature code from the second target optical module;
[0183] The target topology table is updated based on the first target topology feature code and the second target topology feature code;
[0184] Once the target topology table is updated, connect the first target optical module and the second target optical module.
[0185] As an optional embodiment, the service scheduling instruction includes a port identifier associated with the first target optical module and a port identifier associated with the second target optical module on the scheduling device, and the apparatus 1000 is further configured to:
[0186] A third optical path connection is established between the port corresponding to the port identifier associated with the first target optical module on the scheduling device and the port corresponding to the port identifier associated with the second target optical module on the scheduling device.
[0187] Example 3
[0188] Figure 8 This illustration schematically depicts a hardware architecture diagram of a computer device 10000 suitable for implementing a network scheduling method according to Embodiment 3 of this application. In some embodiments, the computer device 10000 may be a network device such as an OCS. Figure 8 As shown, the computer device 10000 includes, but is not limited to: a memory 10010, a processor 10020, and a network interface 10030 that can communicate and be linked with each other via a system bus. Wherein:
[0189] The memory 10010 includes at least one type of computer-readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 10010 may be an internal storage module of a computer device 10000, such as the hard disk or memory of the computer device 10000. In other embodiments, the memory 10010 may also be an external storage device of the computer device 10000, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the computer device 10000. Of course, the memory 10010 may also include both the internal storage module and the external storage device of the computer device 10000. In this embodiment, the memory 10010 is typically used to store the operating system and various application software installed on the computer device 10000, such as the program code of the method described in the foregoing embodiment. Furthermore, the memory 10010 can also be used to temporarily store various types of data that have been output or will be output.
[0190] In some embodiments, processor 10020 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other chip. Processor 10020 is typically used to control the overall operation of computer device 10000, such as performing control and processing related to data interaction or communication with computer device 10000. In this embodiment, processor 10020 is used to run program code stored in memory 10010 or process data.
[0191] Network interface 10030 may include a wireless network interface or a wired network interface, which is typically used to establish a communication link between computer device 10000 and other computer devices. For example, network interface 10030 is used to connect computer device 10000 to an external terminal via a network, establishing a data transmission channel and communication link between computer device 10000 and the external terminal. The network may be an intranet, the Internet, Global System for Mobile Communication (GSM), Wideband Code Division Multiple Access (WCDMA), 4G network, 5G network, Bluetooth, Wi-Fi, or other wireless or wired networks.
[0192] It should be pointed out that, Figure 8 Only computer devices with components 10010-10030 are shown; however, it should be understood that it is not required to implement all of the shown components, and more or fewer components may be implemented instead.
[0193] In this embodiment, the network scheduling method stored in memory 10010 can also be divided into one or more program modules and executed by one or more processors (such as processor 10020) to complete the embodiment of this application.
[0194] Example 4
[0195] This application also provides a computer-readable storage medium storing a computer program thereon, wherein the computer program, when executed by a processor, implements the steps of the method described in the foregoing embodiments.
[0196] In this embodiment, the computer-readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the computer-readable storage medium may be an internal storage unit of a computer device, such as the hard disk or memory of the computer device. In other embodiments, the computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the computer device. Of course, the computer-readable storage medium may include both the internal storage unit and the external storage device of the computer device. In this embodiment, the computer-readable storage medium is typically used to store the operating system and various application software installed on the computer device, such as the program code of the method described in the foregoing embodiments. In addition, the computer-readable storage medium can also be used to temporarily store various types of data that have been output or will be output.
[0197] Example 5
[0198] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the methods described in the above embodiments.
[0199] Example 6
[0200] This application also provides a network scheduling system, the implementation of which and its technical details can be found above.
[0201] The network dispatching system includes a control terminal, at least two network layer devices, and dispatching equipment, wherein:
[0202] The control terminal is used to write or update the topology feature code to the writable storage area of the optical module.
[0203] At least two network layer devices are provided, each of which is equipped with an optical module, an information transmission module, and a status monitoring module. The information transmission module is used to transmit data between the optical module and the scheduling device, and the status monitoring module is used to monitor the working status of the optical module and update the module status identifier in the topology feature code.
[0204] The scheduling device connects to the optical modules in the at least two network layer devices and to the control terminal.
[0205] The scheduling device includes a topology information interaction module, a topology management module, and an adjustment control module, wherein:
[0206] The topology information interaction module is used to obtain the topology feature code in each optical module and send adjustment instructions to each optical module.
[0207] The topology management module is used to generate a target topology table based on the acquired topology feature codes and monitor the topology status in real time.
[0208] The adjustment control module is used to adjust the optical path connection according to the target topology table when a topology anomaly is detected or a service scheduling instruction is received. The service scheduling instruction is used to connect the first target optical module and the second target optical module.
[0209] In this embodiment, the scheduling device directly reads the topology feature code built into the optical module through the topology information interaction module, automatically generating the target topology table without manual input. This improves the efficiency of the scheduling device in topology recognition and reduces the error rate of network configuration. By periodically monitoring the status flags of the optical modules, the scheduling device can proactively identify device faults and topology anomalies, improving the information transparency between the scheduling device and the optical modules. The adjustment control module can automatically adjust the optical path connections based on the target topology table, improving the response speed of network scheduling and reducing the operation and maintenance costs and technical barriers of network scheduling.
[0210] As an optional embodiment, the control terminal is also used to issue the service scheduling instruction to the scheduling device.
[0211] Obviously, those skilled in the art should understand that the modules or steps of the embodiments of this application described above can be implemented using general-purpose computer devices. They can be centralized on a single computer device or distributed across a network of multiple computer devices. Optionally, they can be implemented using computer-executable program code, thereby storing them in a storage device for execution by a computer device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the embodiments of this application are not limited to any particular combination of hardware and software.
[0212] It should be noted that the above are merely preferred embodiments of this application and do not limit the scope of patent protection of this application. Any equivalent structural or procedural changes made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of this application.
Claims
1. A network scheduling method, characterized in that, Applied to a scheduling device for connecting a first optical module and a second optical module, the method includes: Obtain a first topology feature code from the first optical module and a second topology feature code from the second optical module; the first topology feature code includes a field describing the connection method between the scheduling device and the first optical module; the second topology feature code includes a field describing the connection method between the scheduling device and the second optical module. Generate a target topology table based on the first topology feature code and the second topology feature code; According to the target topology table, connect the first optical module and the second optical module. The scheduling device is an OCS device, the first optical module is deployed on the first network layer device, and the second optical module is deployed on the second network layer device; The first topological feature code includes: The device identifier of the first network layer device, the port identifier of the first optical module on the first network layer device, the port identifier of the first optical module associated with the scheduling device, and the connection information between the second optical module and the scheduling device; The second topological feature code includes: The device identifier of the second network layer device, the port identifier of the second optical module on the second network layer device, the port identifier of the second optical module associated with the scheduling device, and the connection information between the first optical module and the scheduling device; The method further includes: Obtain the updated first topological feature code and / or the updated second topological feature code; Update the target topology table according to the updated first topology feature code and / or the updated second topology feature code; Wherein, the first optical module and the second optical module are coupled through a first optical path, and the first optical path has a corresponding priority; the first topology feature code includes the optical module status identifier of the first optical module, and the second topology feature code includes the optical module status identifier of the second optical module; updating the target topology table according to the updated first topology feature code and / or the updated second topology feature code includes: If the optical module status identifier of the first optical module and / or the optical module status identifier corresponding to the second optical module are abnormal, the second optical path is determined from the target topology table according to the priority corresponding to the first optical path; wherein, the second optical path is used to couple the first backup optical module and the second backup optical module; An adjustment command is sent to the first backup optical module and the second backup optical module to connect the first backup optical module and the second backup optical module; If the first backup optical module and the second backup optical module are successfully connected, the target topology table is updated.
2. The method according to claim 1, characterized in that, When an adjustment command is issued to the first backup optical module and the second backup optical module, if the first backup optical module returns a confirmation signal in response to the adjustment command, the first backup optical module sets its own module status flag to be adjusted; if the second backup optical module returns a confirmation signal in response to the adjustment command, the second backup optical module sets its own module status flag to be adjusted. When the first backup optical module and the second backup optical module are successfully connected, the first backup optical module sets its module status indicator to normal, and the second backup optical module sets its module status indicator to normal.
3. The method according to claim 1, characterized in that, The method further includes: Receive a service scheduling instruction, the service scheduling instruction being used to connect a first target optical module and a second target optical module; Obtain the first target topology feature code from the first target optical module and the second target topology feature code from the second target optical module; The target topology table is updated based on the first target topology feature code and the second target topology feature code; Once the target topology table is updated, connect the first target optical module and the second target optical module.
4. The method according to claim 3, characterized in that, The service scheduling instruction includes the port identifier associated with the first target optical module and the port identifier associated with the second target optical module on the scheduling device; Connecting the first target optical module and the second target optical module includes: A third optical path connection is established between the port corresponding to the port identifier associated with the first target optical module on the scheduling device and the port corresponding to the port identifier associated with the second target optical module on the scheduling device.
5. A network scheduling device, characterized in that, Applied to a scheduling device, the scheduling device being connected to a first optical module and a second optical module, the device includes: The acquisition module is used to acquire a first topology feature code in the first optical module and a second topology feature code in the second optical module; the first topology feature code includes a field describing the connection method between the scheduling device and the first optical module; the second topology feature code includes a field describing the connection method between the scheduling device and the second optical module. The generation module is used to generate a target topology table based on the first topology feature code and the second topology feature code; The scheduling module is used to connect the first optical module and the second optical module according to the target topology table; The scheduling device is an OCS device, the first optical module is deployed on the first network layer device, and the second optical module is deployed on the second network layer device; The first topological feature code includes: The device identifier of the first network layer device, the port identifier of the first optical module on the first network layer device, the port identifier of the first optical module associated with the scheduling device, and the connection information between the second optical module and the scheduling device; The second topological feature code includes: The device identifier of the second network layer device, the port identifier of the second optical module on the second network layer device, the port identifier of the second optical module associated with the scheduling device, and the connection information between the first optical module and the scheduling device; The device further includes an update module for: Obtain the updated first topological feature code and / or the updated second topological feature code; Update the target topology table according to the updated first topology feature code and / or the updated second topology feature code; Wherein, the first optical module and the second optical module are coupled through a first optical path, and the first optical path has a corresponding priority; the first topology feature code includes the optical module status identifier of the first optical module, and the second topology feature code includes the optical module status identifier of the second optical module; the update module is further configured to: If the optical module status identifier of the first optical module and / or the optical module status identifier corresponding to the second optical module are abnormal, the second optical path is determined from the target topology table according to the priority corresponding to the first optical path; wherein, the second optical path is used to couple the first backup optical module and the second backup optical module; An adjustment command is sent to the first backup optical module and the second backup optical module to connect the first backup optical module and the second backup optical module; If the first backup optical module and the second backup optical module are successfully connected, the target topology table is updated.
6. A computer device, characterized in that, include: At least one processor; and A memory communicatively connected to the at least one processor; wherein: The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 4.
7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, implement the method as described in any one of claims 1 to 4.
8. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 4.
9. A network scheduling system, characterized in that, The network scheduling system is used to implement the steps of the method according to any one of claims 1 to 4.