ODF resource visualization method and system

Abstract

The invention provides an ODF resource visualization method and system, and the method comprises the steps: obtaining work order and equipment information through a butt joint operation and maintenance work order system and an equipment management system; aiming at the approved cross-machine-room wiring work order, verifying the routing correctness and the equipment input state, automatically pre-distributing an adaptive idle ODF port, synchronously updating the color of the port on a visual interface, and generating full-link routing information after the work order is completed; for the equipment off-shelf work order, whether equipment is ODF routing double-end equipment is judged, a port release work order is automatically generated, and the port state is updated; meanwhile, port states, routing and operation records are stored to support traceability and rollback. According to the method and the device, automatic management and visual presentation of the ODF resources can be realized, the operation and maintenance efficiency of cross-machine-room links is improved, idle resources are reduced, and reliable operation and maintenance of high-bandwidth links can be supported without hardware transformation.

Description

Technical Field

[0001] This application relates to the field of network operation and maintenance technology, and in particular to an ODF resource visualization method and system. Background Technology

[0002] In network operation and maintenance scenarios in data centers or large campuses, optical path connections between equipment in different data centers rely on ODF (Optical Distribution Frame) to achieve port patching. However, traditional ODF resource management often relies on manual ledger records, which has problems such as scattered information and untimely updates. Operation and maintenance personnel need to manually check work orders and port status, which is not only inefficient, but also prone to resource waste such as duplicate port allocation and ports not being released after equipment is taken off the rack. At the same time, cross-data center routing information relies on manual memory or scattered documents, and troubleshooting requires tracing the links one by one, which is time-consuming.

[0003] On the other hand, while existing ODF resource management solutions can achieve status acquisition through hardware modifications (such as adding sensors), the modification costs are high and require interruption of on-network services, making it difficult to promote on a large scale in production environments. On the other hand, purely software systems often lack linkage with operation and maintenance work orders and equipment management systems, and cannot automatically verify the legality of work orders and port compatibility, resulting in a disconnect between resource allocation and actual business needs, making it difficult to support efficient operation and maintenance of high-bandwidth cross-data center links such as 100GE. Summary of the Invention

[0004] In view of this, the embodiments of this application provide an ODF resource visualization method and system, which can realize the automated management and visualization of ODF resources, improve the operation and maintenance efficiency of cross-data center links, reduce resource idleness, and support the reliable operation and maintenance of high-bandwidth links without hardware modification.

[0005] The technical solution of this application embodiment is implemented as follows: In a first aspect, embodiments of this application provide an ODF resource visualization method, comprising the following steps: The system connects to the operation and maintenance work order system and the equipment management system to obtain operation and maintenance work order information and full equipment information. The operation and maintenance work orders include cross-data center cabling type work orders and equipment de-rack type work orders. When an approved cross-data center cabling work order is received, the routing information of the work order is verified to be correct, and the equipment management system is used to check whether the equipment involved in the work order has been entered into the system. If the routing information is correct and the device has been entered into the system, based on the location of the device in the data center in the work order, query the status of the ODF resource ports required for the corresponding data center and cross-data center fiber jumpers, traverse and search for idle ODF physical ports and pre-allocate them; if the verification fails, generate the verification result and return the work order to the operation and maintenance work order system, while indicating the reason for the return. Based on the pre-assigned ODF physical port status, adjust the port display color in the visualization interface, and after the work order is completed and closed, update the port status to "used" and generate the complete device routing information corresponding to the port. When an approved device removal work order is received, it is determined whether the device to be removed is a dual-end device in the ODF routing line. If it is a dual-end device, an ODF port release work order is generated in the associated maintenance work order system, the status of the corresponding ODF port is updated to pending release, and the routing information corresponding to the port is deleted after the release work order is completed. The status information, routing information, and operation records of the ODF port are stored in the database for data tracing and rollback.

[0006] Secondly, embodiments of this application also provide an ODF resource visualization system, including: an operation and maintenance work order system module, an equipment management system module, and an ODF resource system module; The operation and maintenance work order system module is used to receive work order entries, classify work orders by cross-data center cabling type or equipment removal type, and conduct security approval of work orders, and synchronize the approved work order information to the ODF resource system module. The device management system module is used to store the name, location, model and room information of all devices, provide feedback on the device entry status according to the query request of the ODF resource system module, and update the corresponding device information when the device is put on or taken off the shelf. The ODF resource system module includes a processing module, a visualization module, a storage module, and an administrator module; The processing module is used to interface with the operation and maintenance work order system module and the equipment management system module, perform route verification and equipment entry verification for cross-data center cabling work orders, complete the pre-allocation of idle ODF ports, and perform dual-end device judgment for equipment removal work orders to generate ODF port release work orders. The visualization module is used to adjust the port display color according to the port status output by the processing module; and to generate or delete the routing information line diagram corresponding to the port according to the work order completion status, displaying the port number, device information and computer room location. The storage module is used to store the status information, routing information, work order operation records and administrator account authorization information of the ODF port, and supports data traceability and rollback; The administrator module is used to grant administrators operation permissions to the ODF resource system module, allowing administrators to manually adjust the port status and routing information of non-standard work orders.

[0007] Thirdly, embodiments of this application also provide an electronic device, including: a processor, a storage medium, and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the ODF resource visualization method described in any of the first aspects.

[0008] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the ODF resource visualization method described in any one of the first aspects.

[0009] The embodiments of this application have the following beneficial effects: By constructing a system-linked architecture of "Operation and Maintenance Work Orders - Equipment Management - ODF Resources", the system achieves automated verification, pre-allocation, and closed-loop management of ODF resources across data centers. This not only solves the problems of scattered and inefficient traditional manual ledger information, but also avoids the costs of hardware upgrades and the risk of business interruption. At the same time, through port status color coding, full-link routing visualization, and historical record tracing functions, operation and maintenance personnel can intuitively identify port status and quickly locate faulty links. Combined with compatibility verification and timeout reminder mechanisms, the accuracy of port allocation and work order processing efficiency are further improved. Ultimately, this achieves refined and visualized management of ODF resources, effectively reducing resource idle rates and operation and maintenance costs, and ensuring the stable and reliable operation of high-speed optical links across data centers. Attached Figure Description

[0010] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0011] Figure 1 This is a flowchart of ODF route visualization generation provided in an embodiment of this application; Figure 2 This is a flowchart of the physical release process of the ODF port provided in the embodiments of this application; Figure 3 This is a conceptual example diagram of ODF routing information visualization provided in an embodiment of this application; Figure 4 This is an overall system module block diagram provided in the embodiments of this application. Detailed Implementation

[0012] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the accompanying drawings in this application are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of this application. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of this application. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this application, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.

[0013] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0014] Furthermore, the described embodiments are merely some, not all, of the embodiments of this application. The components of the embodiments of this application described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0015] In the following description, the terms "first, second, third" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first, second, third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0016] It should be noted that the term "comprising" will be used in the embodiments of this application to indicate the presence of the features declared thereafter, but does not exclude the addition of other features.

[0017] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application and is not intended to limit this application.

[0018] See Figure 1 and Figure 2 , Figure 1This is a flowchart of the ODF route visualization generation process provided in the embodiments of this application. Figure 2 This is a flowchart of the physical release of the ODF port provided in the embodiments of this application, which will be combined with Figure 1 and Figure 2 The ODF resource visualization method provided in the embodiments of this application will be explained and described.

[0019] This application provides an ODF resource visualization method, including the following steps: The system connects to the operation and maintenance work order system and the equipment management system to obtain operation and maintenance work order information and full equipment information. The operation and maintenance work orders include cross-data center cabling type work orders and equipment de-rack type work orders. When an approved cross-data center cabling work order is received, the routing information of the work order is verified to be correct, and the equipment management system is used to check whether the equipment involved in the work order has been entered into the system. If the routing information is correct and the device has been entered into the system, based on the location of the device in the data center in the work order, query the status of the ODF resource ports required for the corresponding data center and cross-data center fiber jumpers, traverse and search for idle ODF physical ports and pre-allocate them; if the verification fails, generate the verification result and return the work order to the operation and maintenance work order system, while indicating the reason for the return. Based on the pre-assigned ODF physical port status, adjust the port display color in the visualization interface, and after the work order is completed and closed, update the port status to "used" and generate the complete device routing information corresponding to the port. When an approved device removal work order is received, it is determined whether the device to be removed is a dual-end device in the ODF routing line. If it is a dual-end device, an ODF port release work order is generated in the associated maintenance work order system, the status of the corresponding ODF port is updated to pending release, and the routing information corresponding to the port is deleted after the release work order is completed. The status information, routing information, and operation records of the ODF port are stored in the database for data tracing and rollback.

[0020] The above embodiments aim to solve the problems of low efficiency in manual management, inability of image recognition to obtain routes, and high cost of hardware modification that affects business in the prior art, and achieve the core goal of no hardware modification + automated management + visual presentation, as follows: The operation and maintenance work order system is responsible for collecting actual business needs (such as cross-data center cabling and equipment removal). It needs to support clear classification of work order types (cross-data center cabling / equipment removal) to ensure that subsequent processes can be handled in a targeted manner. The equipment management system stores all basic information of all equipment (such as equipment name, data center, model, and network access status) to provide data support for subsequent equipment legality verification. When both systems synchronize information with the ODF resource management module, they need to ensure data real-time performance (it is recommended that the synchronization delay not exceed 10 seconds) to avoid port allocation errors due to information lag.

[0021] To address the unique characteristics of cross-data center cabling work orders (involving multi-data center port linkage and optical path connectivity), a dual verification standard is established: Routing information correctness verification: It is necessary to verify whether the starting computer room-ending computer room-through optical cable filled in the work order matches the actual physical topology (e.g., if a work order fills in 201 computer room → 405 computer room, but there is no direct optical cable in reality and it needs to be transferred through 202 computer room, then the verification will fail), to avoid port allocation failure due to routing errors; Device entry status verification: Check whether the devices involved in the work order (such as access switches and servers) have completed network registration through the device management system. If the device has not been entered into the system, it means that the legality of the device has not been confirmed. At this time, allocating ports may lead to resource waste or illegal device access, so verification is required.

[0022] Intercepting invalid work orders (such as routing errors or illegal devices) in advance can prevent subsequent invalid operations such as port allocation and implementation, thus reducing the waste of manpower and resources.

[0023] The process is divided into two branches: verification passes and verification fails. Verification passed: Idle port pre-allocation: First, based on the equipment room location in the work order, locate the starting and ending equipment rooms (e.g., if equipment A is in equipment room 201 and equipment B is in equipment room 405, then the ODF ports in equipment rooms 201 and 405 need to be matched); then query the real-time status of the ODF ports in the two equipment rooms (obtained through the ODF resource system module), and iterate through and filter the ports in the unallocated (white) state; at the same time, the fiber optic patch adapter compatibility needs to be considered (e.g., if the port interface type is SC / LC, it needs to be matched with the optical cable connector) to ensure that the pre-allocated ports can be physically connected; Verification failed: Work order rollback: Structured verification results (such as routing error: no direct optical cable between room 201 and room 405, equipment not entered: switch HWCE1688 not registered) should be generated, rather than vague prompts, so that the order submitter can quickly correct the error and improve the efficiency of work order processing.

[0024] Unlike traditional manual port allocation based on experience, this system uses an automated logic of data center location → status screening → compatibility verification to ensure the accuracy and rationality of port allocation, while avoiding the resource shortage problem caused by manual allocation based on proximity.

[0025] The port state update and route generation processes are divided into two phases: Pre-allocation phase: Status color adjustment: After pre-allocation, the port status will be updated from unallocated (white) to pre-allocated (yellow) to distinguish it intuitively by color and avoid other work orders from repeatedly allocating the port (the visual interface needs to be refreshed in real time with a delay of no more than 5 seconds). Work order completion stage: Status and route update: When the work order is completed (such as optical cable splicing or patch cord connection) and the work order is closed, the system detects the work order closure signal and automatically updates the port status from pre-allocated (yellow) to used (blue); at the same time, it generates complete device routing information, which must include the starting port (such as ODF1-Port 1 in Room 201) → through optical cable (such as 96-core optical cable from Room 201 to Room 405) → ending port (such as ODF3-Port 6 in Room 405) → connected devices (such as device A and device B), realizing the full link association of port-device-optical path.

[0026] Color coding enables port status to be identified at a glance, solving the inefficiency of traditional manual ledgers that require flipping through records to check status; end-to-end routing information provides data support for subsequent troubleshooting (such as quickly locating the corresponding port and fiber optic cable if a device loses network access).

[0027] When processing a device decommissioning work order, it is necessary to first check whether the decommissioned device belongs to either end of a certain ODF route (i.e., the starting or ending device of the route; for example, if device A is the starting device of the route from room 201 to room 405, then it is a dual-end device; if it is only a splitter device along the route, then it is not a dual-end device). If it is a dual-end device, it means that after the device is decommissioned, the corresponding route becomes invalid and the port needs to be released. Generate an ODF port release work order in the associated maintenance work order system, specifying the port number to be released (e.g., ODF1-port 1 in room 201, ODF3-port 6 in room 405), and assign it to the implementation personnel. At the same time, update the port status from used (blue) to pending release (red) to indicate that the port needs to be handled. After the release work order is completed (e.g., removing the jumper), delete the routing information corresponding to the port to avoid invalid routes occupying system storage.

[0028] This enables an automated closed loop of device removal → route failure → port release, eliminating the need for manual memorization or querying of which ports correspond to the devices and reducing resource idle rate (tests have shown that port idle time can be shortened from the traditional 2-3 days to within 1 hour).

[0029] For data storage and tracing, the information that needs to be stored includes: Status information: Record of each port status change (e.g., 2024-05-01 10:00: Port 1 changes from white to yellow, operator: System Auto; 2024-05-01 16:00: Port 1 changes from yellow to blue, operator: Zhang San). Routing information: Complete route generation and deletion records (such as route ID, origin / end port, connected device, generation time, and deletion time); Operation logs: Work order processing records (such as work order number, verification result, port number allocated / released), system automatic operation records, and administrator manual operation records; The storage medium uses a relational database (such as MySQL) that supports queries by port number, time range, work order number, etc., and also supports data rollback (e.g., if the status of a port is updated incorrectly, it can be rolled back to the correct status through historical records).

[0030] The above method meets the requirements of traceability and auditability in operation and maintenance management. If port allocation conflicts or routing errors occur later, the problem can be located through historical records (such as duplicate allocation of a port, which can be checked to see if it is a loophole in the system's automatic allocation logic or an administrator's misoperation).

[0031] Please see Figure 3 , Figure 3 This is a conceptual example diagram of ODF routing information visualization provided in the embodiments of this application, such as... Figure 3 As shown, the 100GE high-speed link connection between different equipment rooms is achieved through ODF (Optical Distribution Frame) and optical cable. The specific explanation is as follows: The data centers involved include the 202 module data center, the 201A access room, and the 405 module data center. The entire link is an all-optical connection of "switch → ODF → cross-data center optical cable → ODF → switch". Specific nodes and connection methods are as follows: Starting point (Module 202 computer room): Equipment: A06-420U-PICC-SW-HW-CE16808-100GE1 / 0 / X (CE16808 switch, 100GE port) Connection: Connect to port 35 / 36 of A23-ODF5 (ODF rack) in the same equipment room via single-mode fiber.

[0032] Module 202 computer room → Access room 201A: Connection: A23-ODF5 (ports 35 / 36) is connected to ODF01-20 board (ports 35 / 36) in access room 201A via cross-room optical cable.

[0033] 201A Access Room Internal Transfer: The ODF01-20 board (ports 35 / 36) is connected to the ODF03-49 board (ports 1 / 2) in the same access room via single-mode fiber.

[0034] Access Room 201A → Module Room 405: Connection: The ODF03-49 board (port 1 / 2) is connected to A23-ODF1 (port 1 / 2) in the 405 module room via an inter-room optical cable.

[0035] End point (Module 405 Computer Room): Equipment: D07-40U-PICC-SW-HW-CE6855-100GE1 / 0 / X (CE6855 switch, 100GE port) Connection: Access via single-mode fiber to A23-ODF1 (port 1 / 2) in the same equipment room.

[0036] In some embodiments, the correspondence between port display colors and status is as follows: unallocated status is displayed as white, pre-allocated status as yellow, used status as blue, pending release status as red, and faulty port status as black.

[0037] Unassigned (white): This indicates that the port has never been used, the physical interface has no jumper connections, the optical cable is not spliced, and it is in an idle and available state. It is the first choice for pre-assignment of cross-data center cabling work orders. Pre-assignment (yellow): This indicates that the port has been locked by an approved cross-data center cabling work order, but the physical implementation has not yet been completed (e.g., fiber optic cables have not been spliced ​​or fiber jumpers have not been installed). At this time, other work orders cannot assign this port to avoid conflicts. Used (blue): This indicates that the port has been physically implemented, the fiber patch connection is normal, the corresponding router is in use, and it supports normal data transmission of the device. Pending Release (Red): This indicates that the device corresponding to this port has been taken off the shelf and the jumper needs to be removed. It is in a pending state, prompting the implementer to release it as soon as possible to avoid idle resources. Bad port (black): This indicates that the port has a physical fault (such as interface damage or fiber breakage at the fusion splice) and cannot be used normally. Once marked as a bad port, the system will automatically exclude it from the allocation range to avoid service interruption caused by allocating faulty ports.

[0038] Maintenance personnel can quickly determine the port status by the interface color without clicking on the port to view details (e.g., in the data center ODF panel visualization, blue ports are in use and red ports are waiting to be released), improving inspection efficiency; the color standard is unified across the entire system (e.g., avoiding using green to indicate use in one data center and blue to indicate use in another data center), reducing the understanding cost when collaborating across data centers; red (waiting to be released) and black (bad ports) indicate that the port needs to be handled, and the high-contrast colors (red and black are clearly distinguishable from white, yellow, and blue) prompt maintenance personnel to handle them first and avoid omissions.

[0039] Color updates must be strongly linked to the business process; the specific triggering logic is as follows: White → Yellow: Cross-data center cabling work order verification passed, triggered when the system automatically pre-allocates ports; Yellow → Blue: Cross-data center cabling work order completed and closed; triggered when the system detects the closure signal. Blue → Red: The device removal work order verification shows that the device is a dual-end device, which is triggered when a release work order is generated; Red → White: Triggered when the work order is completed and closed, and the system deletes the routing information; Any status → Black: Triggered after maintenance personnel report port failures through the administrator module and the report is approved.

[0040] In some embodiments, the process of traversing and searching for free ODF physical ports and pre-allocating them further includes: matching the corresponding ODF ports in the room according to the patch cord requirements of cross-room cabling, and ensuring that the pre-allocated ports meet the physical connection conditions for cross-room optical path transmission.

[0041] The core of cross-data center cabling is optical path connectivity. Simply allocating idle ports is insufficient to guarantee service availability; it is necessary to match patch cord requirements with the physical characteristics of the ports. Specific adaptation dimensions include: Interface type compatibility: The type of optical cable connector (such as SC, LC, FC) must be consistent with the type of ODF port interface (e.g., if the optical cable is an SC connector, an SC type port must be assigned) to avoid physical conflicts where the connector cannot be inserted into the port; Fiber core number adaptation: If the work order requires a 12-core fiber optic cable connection across equipment rooms, an ODF port that supports 12-core splicing must be allocated (e.g., the ODF splicing tray is 12-core) to avoid insufficient port core count causing some fiber cores to be unusable. Transmission rate adaptation: If the device is 100GE, an ODF port that supports 100GE transmission must be allocated (such as a port using single-mode fiber, rather than a multimode fiber port) to avoid port rate bottlenecks affecting services. Data center topology adaptation: If cross-data center cabling needs to be transferred through an intermediate data center (e.g., 201 data center → 202 data center → 405 data center), then it is necessary to pre-allocate idle ports in 201 data center (starting point), 202 data center (transfer point), and 405 data center (ending point). The three ports must belong to the same optical path topology to avoid the optical path being blocked because the starting point-ending point ports are idle but the transfer port is occupied.

[0042] During the process of traversing and searching for idle ODF physical ports, a new adaptability verification sub-process needs to be added, specifically: Extract the patch cord requirement parameters (interface type, number of cores, speed, topology path) from the cross-data center cabling work order. Query the physical parameters (interface type, number of supported cores, maximum speed, and topology path) of the idle port from the ODF resource system module. Compare the required parameters with the physical parameters to filter out available ports that perfectly match; If the number of matching ports is greater than or equal to 1, select the port closest to the device (e.g., if the device is in Area A of Room 201, prioritize the ODF port in Area A of Room 201 to reduce the length of the jumper); if the number of matching ports is 0, generate a prompt that there is no compatible port, roll back the work order and suggest adjusting the jumper requirements (e.g., change the connector type).

[0043] In some embodiments, the system also includes an administrator operation process: granting administrator-specific operation permissions, allowing administrators to view full information of ODF resource ports in each data center through a visual interface; supporting administrators to manually add, delete, or modify ODF port status and routing information in non-standard work order scenarios, and synchronously storing administrator operation records in the database.

[0044] Administrator privileges must adhere to the principle of least privilege to avoid abuse of permissions. The activation process is as follows: The applicant (such as the person in charge of data center operation and maintenance) submits a permission application to the ODF resource system module, specifying the reason for the application (such as being responsible for handling non-standard work orders in data center 201) and the scope of the required permissions (such as only viewing and modifying ports in data center 201). The system administrator reviews the application (verifying the applicant's identity, responsibilities, and scope of authority). After the review is approved, the administrator module generates a dedicated account, configures the corresponding permissions (such as viewing all data center port information + modifying the status of the 201 data center port + deleting invalid routes in the 201 data center), and records the account opening time and permission scope; Before an account can be activated, security authentication (such as two-factor authentication or dynamic token) is required to ensure account security.

[0045] Administrator operations primarily target non-standard scenarios that cannot be covered by the system's automated processes, specifically including: Emergency troubleshooting: If a port status shows as used due to a system bug, but is actually not used, the administrator needs to manually change the status to unassigned to avoid wasting resources; Work order abnormal adjustment: For example, if a cross-data center cabling work order has been pre-assigned a port (yellow), but needs to be terminated due to service cancellation, the administrator needs to manually change the port status back to unassigned and delete the pre-assigned record; Historical data correction: If the routing information for a certain port is entered incorrectly when migrating manual ledgers to the system, the administrator needs to manually modify the starting / ending device of the route to ensure data accuracy; Administrators must perform these operations through a visual interface. Specific functions include: View: After selecting a data center, the system displays full port information (status, routing, and historical usage records) for all ODF cabinets in that data center. Add: For temporary routes that are not recorded in the system (such as emergency test routes), manually add the association between ports and devices; Modifications include: adjusting port status (e.g., from yellow to white) and correcting routing information (e.g., replacing the endpoint device). Delete: Delete invalid routes (such as routes that have been removed from the device but not automatically deleted by the system) and delete incorrect port status records.

[0046] To ensure the traceability of administrator operations, operation records must be stored synchronously, including the following: Operator account, operation time, operation type (view / add / modify / delete); Operation object (e.g., ODF1-Port1 in Room 201, Router ID: RT-20240501-001); Status / information before and after the operation (e.g., status before modification: yellow → status after modification: white; route before deletion: port 1 of data center 201 → port 6 of data center 405). Reason for operation (administrator needs to fill in manually, such as business cancellation, termination of pre-allocation); Operation records are stored in the administrator operation log table in the database. Only the system administrator can view them. The system supports querying by operator, time range, and operation object. This is used for subsequent auditing (e.g., if a port status is abnormal, it can be checked whether it was due to an administrator's mistake).

[0047] The above methods can solve the rigidity problem of automated system processes and improve the flexibility of the approach (such as emergency fault handling without waiting for work order processes, which can be quickly adjusted); correct system bugs or data errors through manual intervention to avoid the long-term impact of erroneous data on resource management; and ensure that whoever operates is responsible for the operation, avoiding management chaos caused by abuse of permissions.

[0048] In some embodiments, after the work order is completed and closed, the process of updating the port status to "used" and generating complete device routing information corresponding to the port further includes: displaying the complete routing information in the form of a route diagram through a visual interface, with the port number, the name of the connected device, the location of the device in the computer room, and the number of optical fiber cores marked on the route diagram.

[0049] The route map should be presented in the form of a topology diagram with text annotations, and should be displayed intuitively in a visualization interface. The specific layout and annotation content include: Topology layout: Draw according to the physical location of the data center (e.g., data center 201 on the left, data center 202 in the middle, data center 405 on the right), and connect the corresponding ODF ports with lines (e.g., ODF1-port 1 in data center 201 → ODF2-port 3 in data center 202 → ODF3-port 6 in data center 405). The line color should match the port status (e.g., use blue lines for routes that are in use, and red lines for routes that are to be released). Port number labeling: Label each port with the data center name-ODF number-port number (e.g., data center 201-ODF1-port 1) to facilitate quick location of the physical port; Device name labeling: Next to the start and end ports of the route, label the name of the connected device (e.g., start device: HWCE1688 switch, end device: A2-F1 server) to clearly identify the service device corresponding to the route; Data center location labeling: Label each data center area with the data center name (e.g., Data Center 201 (North Center), Data Center 405 (South Center)) to avoid confusion when crossing data centers; Fiber optic cable core count labeling: Mark the number of cores in the fiber optic cable used next to the line (e.g., 96-core fiber optic cable, 12-core fiber optic cable) to facilitate understanding of fiber optic cable resources during subsequent capacity expansion or fault handling.

[0050] To improve usability, the route map needs to support interactive operations, including the following functions: Zoom: Supports mouse wheel zooming, making it easy to view the overall topology (zoom to the full map) or details (zoom in to the ODF port of a specific data center). Drag and drop: Supports dragging and dropping the topology map position, making it easy to view obscured ports or lines; Hover tooltip: When the mouse hovers over a port or line, detailed information is displayed (e.g., hovering over a port shows the status: Used, usage time: 2024-05-01, corresponding work order: WO-20240501-001; hovering over a line shows the fiber optic cable model: GYTA-96B1, laying time: 2023-12-01). Redirect: Clicking on a port or device name will redirect you to the corresponding details page (e.g., clicking on the HWCE1688 switch will redirect you to the device details page in the device management system to view the device model, IP address, etc.).

[0051] The route diagram is automatically generated by the visualization module. The specific process is as follows: Obtain port allocation information (start / end port, equipment room location), device association information (connected device name), and optical cable information (number of cores, model) from the processing module. Call a drawing engine (such as ECharts or D3.js) to draw the topology framework according to the location of the computer room; Draw connection lines according to port allocation information and set the line color (consistent with port status). Add text labels for the port number, device name, equipment room location, and number of optical fiber cores in the corresponding locations; Generate interactive events (zoom, hover tooltip, jump) and store the route map data in the storage module; The route diagram needs to be updated in real time. When the port status or routing information changes (such as a port changing from yellow to blue), the visualization module automatically redraws the route diagram (updating line colors and labeling information) to ensure consistency with the actual status.

[0052] The above method eliminates the need for maintenance personnel to sift through multiple work orders or ledgers. They can quickly understand which devices are connected to a port and which fiber optic cable it runs through by looking at the route map, improving route lookup efficiency (reducing it from the traditional 10-15 minutes to within 1 minute). If a device loses network access, the route map can quickly locate the corresponding port and fiber optic cable to check whether it is a port failure or a fiber optic cable break, reducing troubleshooting time. The route map also provides a visual view of the routing distribution of ports in each data center, providing a planning basis for subsequent expansion (such as allocating ports for new equipment) (e.g., avoiding excessive port occupation on a certain fiber optic cable).

[0053] Please see Figure 4 , Figure 4 This is an overall system module block diagram provided in the embodiments of this application. The embodiments of this application also provide an ODF resource visualization system, including an operation and maintenance work order system module, an equipment management system module, and an ODF resource system module; The operation and maintenance work order system module is used to receive work order entries, classify work orders by cross-data center cabling type or equipment removal type, and conduct security approval of work orders, and synchronize the approved work order information to the ODF resource system module. The device management system module is used to store the name, location, model and room information of all devices, provide feedback on the device entry status according to the query request of the ODF resource system module, and update the corresponding device information when the device is put on or taken off the shelf. The ODF resource system module includes a processing module, a visualization module, a storage module, and an administrator module; The processing module is used to interface with the operation and maintenance work order system module and the equipment management system module, perform route verification and equipment entry verification for cross-data center cabling work orders, complete the pre-allocation of idle ODF ports, and perform dual-end device judgment for equipment removal work orders to generate ODF port release work orders. The visualization module is used to adjust the port display color according to the port status output by the processing module; and to generate or delete the routing information line diagram corresponding to the port according to the work order completion status, displaying the port number, device information and computer room location. The storage module is used to store the status information, routing information, work order operation records and administrator account authorization information of the ODF port, and supports data traceability and rollback; The administrator module is used to grant administrators operation permissions to the ODF resource system module, allowing administrators to manually adjust the port status and routing information of non-standard work orders.

[0054] This embodiment corresponds to the method in the above embodiments, clarifying the functions and collaborative relationships of each module from the perspective of system module architecture, as explained in detail below: The operations and maintenance work order system module serves as the entry point for business requirements, responsible for collecting and initially processing operations and maintenance needs, including: Work order entry: Provide a web or mobile entry interface to support the person submitting the work order to fill in the work order information (work order type: cross-data center cabling / equipment removal; work order content: equipment name, data center location, routing requirements, implementation time). The interface must have a mandatory field validation function (if the work order type is not selected, it cannot be submitted) to avoid missing information. Work order classification: Based on the entered work order type field, work orders are automatically classified into the cross-data center cabling work order pool or the equipment delisting work order pool for easier subsequent targeted processing; manual adjustment of classification is also supported (if the wrong work order type is selected, the administrator can modify it); Security Approval: A multi-level approval process is set up (e.g., team approval → department approval). Approving personnel need to verify the business legality of the work order (e.g., whether cross-data center cabling complies with network planning) and security compliance (e.g., whether power outage is required during implementation and whether there are security protection measures). After approval, the work order information is automatically synchronized to the ODF resource system module (synchronized content includes work order number, type, content, approval result, and implementing personnel). If the approval fails, it is returned with the reason noted. Work order status management: Supports real-time updates of work order status (e.g., pending approval → approved → in progress → closed), and synchronizes status changes with the ODF resource system module (e.g., the closed status is used to trigger port status updates).

[0055] The equipment management system module serves as the foundation for equipment data, providing the ODF resource system module with support for equipment legitimacy and basic information, including: Full equipment information storage: Stores static information (equipment name, model, manufacturer, network access time, department) and dynamic information (location in computer room, operating status, whether it has been decommissioned) of the equipment. It uses a relational database for storage and supports querying by equipment name, computer room location, operating status and other dimensions. Device information query response: When the processing module of the ODF resource system module initiates a device entry status query request (such as querying whether the HWCE1688 switch has been entered), it must return the query result (entered or not entered) within 1 second, along with the device's data center location information. Equipment information update: When a work order for equipment placement is received, the equipment information is added to the database; when a work order for equipment removal is received, the equipment status is updated to "removed" and the removal time is recorded; after the update, the equipment status change needs to be synchronized with the ODF resource system module (such as the "removed" status to determine whether it is a dual-end device).

[0056] The ODF resource system module is the core of the system, integrating processing, visualization, storage, and administrator functions to achieve automated management and visual presentation of ODF resources. The sub-modules are explained below: The processing module is the logic control center, responsible for connecting the maintenance work order system module and the equipment management system module, executing core business logic, and its specific functions include: Work order verification: Receives approved work orders synchronized from the maintenance work order system module. For cross-data center cabling work orders, performs route information correctness verification (calls the topology data from the device management system module to determine if the route exists) and device entry status verification (calls the device information from the device management system module to determine if the device has been entered). For device removal work orders, performs dual-end device judgment (queries whether the device is the starting or ending point device of a certain ODF route). Port pre-allocation: After the cross-data center cabling work order is verified, based on the data center location in the work order, the port status data of the visualization module is queried, and the unallocated (white) ports that are suitable for patch cord requirements are traversed and filtered to generate a pre-allocation plan (including start / end / transfer port number) and synchronized to the visualization module and storage module. Release work order generation: After the device removal work order is determined to be a dual-end device, the corresponding ODF port information (such as port number and data center location) is extracted, and an ODF port release work order (including work order number, port to be released, associated removal device, and implementation requirements) is generated and synchronized to the operation and maintenance work order system module for dispatching; at the same time, the port status change instruction is sent to the visualization module. Work order progress monitoring: Receives work order status (such as in progress, closed, timed out) synchronized from the operation and maintenance work order system module in real time. When a cross-data center cabling work order is detected as closed, the visualization module is triggered to update the port status to "used". When a release work order is detected as closed, the visualization module is triggered to delete the routing information and update the port status to "unassigned".

[0057] The visualization module is an information presentation window responsible for displaying ODF resource status and routing information in a visual format. Specific functions include: Port status color adjustment: Receive status change instructions from the processing module (e.g., pre-allocated → yellow, used → blue), update the color of the corresponding port in the visualization interface (e.g., data center ODF panel diagram, system overview diagram), with an update delay of no more than 5 seconds; Route information line diagram generation / deletion: Receives route generation instructions from the processing module (such as after closing a cross-data center cabling work order), calls the drawing engine to generate a line diagram containing port, device, data center, and fiber optic cable information; receives route deletion instructions from the processing module (such as after closing a release work order), deletes the corresponding line diagram, and cleans up the line diagram data. Visualized interface interaction: Provides multi-dimensional visualized interfaces (such as a data center-level interface displaying the status of all ODF ports in a data center, and a route-level interface displaying the full link information of a route), supporting interactive operations such as zooming, dragging, and hovering prompts, making it easy for operation and maintenance personnel to view details.

[0058] The storage module is responsible for data security, storing various types of data required for system operation. Its specific functions include: Core data storage includes: ODF port status information (port number, data center location, status, status change time), routing information (route ID, origin / end port, connected device, fiber optic cable information, generation / deletion time), and work order operation records (work order number, associated port, processing result, processing time); a partitioned storage architecture is adopted (the business data area stores status and routing information, and the log data area stores operation records) to facilitate data management and querying. Administrator authorization information storage: Stores administrator account, password (encrypted, such as using MD5 encryption), permission scope (such as only 201 computer room operation permission), account status (enabled / disabled), ensuring that only authorized administrators can perform operations; Data traceability and rollback: Supports querying historical data by timestamp, port number, route ID, etc. (e.g., querying the status changes of a port within 30 days); when data is incorrect (e.g., a system bug causes the status to be incorrect), it can roll back to the correct status through historical data (e.g., roll back to the status 24 hours ago).

[0059] The administrator module serves as the entry point for manual intervention, supporting administrators in handling non-standard scenarios. Specific functions include: Permission Activation and Management: System administrators can create administrator accounts for maintenance personnel, configure permission scope (such as view permission, modify permission, delete permission), and disable accounts based on personnel changes; permission configuration must follow the principle of least privilege (e.g., an administrator only responsible for the 201 data center cannot operate the 405 data center port). Manual adjustment function: Provides a manual operation interface, allowing administrators to adjust port status (e.g., yellow → white), modify routing information (e.g., change endpoint device), and delete invalid data (e.g., routes associated with work orders that have not been closed but whose services have been cancelled) in non-standard scenarios (e.g., system bugs, emergency failures); When performing an operation, a reason must be filled in, and the system will automatically record the operation record; The modules collaborate through data interfaces, and the core process is as follows: The operation and maintenance work order system module inputs and approves work orders, and synchronously sends approved work orders to the processing module of the ODF resource system module; The processing module sends a device information query request to the device management system module to obtain the device entry status and the location of the computer room. The processing module executes verification and port allocation / release logic, and sends state change and route generation / deletion commands to the visualization module; The visualization module executes instructions and updates the interface; at the same time, the processing module sends data storage instructions to the storage module, storing the status, routing, and operation records. Administrators can access the storage module's authorization information through the administrator module, perform manual operations, and the operation records are synchronously stored in the storage module.

[0060] In some embodiments, the processing module also has a timeout reminder function: after pre-allocating ports for cross-data center cabling work orders, it monitors the progress of work order implementation in real time. When it detects that the work order is less than the preset threshold before the preset completion time limit, it sends a timeout reminder message to the work order implementer to urge the work order to be completed.

[0061] The timeout reminder function needs to be triggered based on the comparison between the preset completion time limit of the work order and the real-time implementation progress. The specific logic is as follows: Preset completion time limit acquisition: Extract the implementation completion time limit field from the cross-data center cabling work orders synchronized from the operation and maintenance work order system module (e.g., the work order is filled in as "to be completed before 18:00 on 2024-05-01"); if the work order is not filled in, the system sets the time limit by default (e.g., within 24 hours from the pre-allocated port time). Real-time progress monitoring: The processing module receives the work order status (such as in progress, paused, closed) synchronized by the operation and maintenance work order system module in real time. When the work order status is in progress, the timer is started. Timeout threshold judgment: Set a timeout reminder threshold (e.g., 2 hours left until the preset completion time limit). The processing module periodically (e.g., every 30 minutes) calculates the difference between the current time and the preset completion time limit. When the difference is less than or equal to the threshold, it is determined that the timeout is about to occur. Reminder Sending: Trigger the reminder mechanism to send a timeout reminder message to the work order implementer (obtain contact information from the operation and maintenance work order system module, such as mobile phone number or WeChat account). The message content must include the work order number, the task to be completed (such as cross-data center cabling implementation), the remaining time (such as 2 hours), and the pre-allocated port (such as ODF1-Port 1 in data center 201) to avoid confusion among implementers. Repeat reminder: If the work order is not closed within 1 hour after the reminder is sent, the reminder will be sent again; if the work order is not closed after the preset completion time limit is exceeded, an alarm message will be sent to the person in charge of the work order (such as the team leader of the implementer) to prompt intervention.

[0062] In some embodiments, the routing information map generated by the visualization module supports interactive operation: an administrator or authorized user can click on any port in the route map to expand and view the historical usage records of that port, including previously connected devices, usage time periods, and corresponding work order numbers.

[0063] Interactive operations must be user-friendly, supporting mouse click triggering (administrators or authorized users can left-click any port on the route map). After clicking, a history pop-up window should appear next to the port. The pop-up window must have a close button to avoid obscuring other information. The pop-up window should adopt a layered display structure, with basic port information at the top (port number, data center location, current status), a list of historical usage records in the middle (arranged in reverse chronological order), and operation buttons at the bottom (such as export records, close pop-up window). The list should have pagination functionality (such as displaying 10 records per page) to avoid the pop-up window becoming too long due to too many records.

[0064] Historical usage records must comprehensively reflect the port's past usage, and the specific content and data sources include: Previously connected devices: Records the names of the starting / ending devices that this port has previously connected to (e.g., from 2024-03-01 to 2024-04-30, connecting device A and device B). The data comes from the routing information history table of the storage module. Usage period: The time range during which the port is in use (blue) (e.g., from 10:00 on 2024-03-01 to 16:00 on 2024-04-30), the data comes from the port status change records of the storage module; Corresponding work order number: Records the work order number associated with this port (e.g., WO-20240301-005). Clicking the work order number will take you to the work order details page of the operation and maintenance work order system module (to view the work order content, implementers, and approval records). The data comes from the work order operation record table of the storage module. Operator information: Records the operator who performed the port status change or route generation (such as automatically assigned by the system, administrator Zhang San), and the data comes from the operation log table of the storage module; Historical records must include deletion markers (e.g., if a route is deleted due to service cancellation, it must be marked as deleted) to avoid users mistakenly believing it to be a currently used route.

[0065] To ensure data security, access control must be set for interactive operations: Only administrators and authorized maintenance personnel (such as those responsible for the data center) can click on ports to view historical records; ordinary users (such as those who only need to view port status) do not have click permissions, and pop-ups will not appear; if the historical records contain sensitive information (such as the mobile phone number of the implementer), it must be anonymized (e.g., 131****2951) to avoid information leakage; record the user's operation of viewing historical records (e.g., user Li Si, 2024-05-02 09:30, viewing the historical records of ODF1-port 1 in data center 201) and store it in the log data area of ​​the storage module for easy auditing.

[0066] In some embodiments, the storage module adopts a partitioned storage architecture: port status information and routing information are stored in the business data area, and work order operation records and administrator operation records are stored in the log data area. The business data area and the log data area are backed up independently to ensure data security.

[0067] The partitioned storage architecture divides the storage area into a business data area and a log data area based on differences in data types and uses. These two areas are deployed and managed independently. The storage area supports the core business data for the daily operation of the system, including: ODF port status information (port number, data center location, current status, status change time, associated route ID); ODF routing information (route ID, origin / endpoint / transfer port number, connected device name, fiber optic cable core count and model, generation time, deletion time, validity status); administrator authorization information (administrator account, encrypted password, permission scope, account status, activation / deactivation time); and the storage medium used. High-performance relational databases (such as MySQL clusters) support high-concurrency read and write operations (e.g., handling 100+ port status update requests simultaneously) to ensure smooth system operation; indexes are created for frequently queried fields (such as port number, route ID, and administrator account) to improve query efficiency (e.g., reducing the time to query a port status from 1 second to 0.1 seconds); a combination of incremental and full backups is used, with incremental backups performed hourly (backing up business data added / modified within 1 hour) and full backups performed once daily at midnight (backing up all business data), and backup data is stored on a remote server to avoid data loss due to local failures.

[0068] The system stores operation log data, including: work order operation records (work order number, processing module operation content, operation time, operation result, associated port); administrator operation records (administrator account, operation type, operation object, pre- and post-operation information, operation reason, operation time); and system automatic operation records (operation module, operation content, triggering condition, operation time, operation result). The storage medium uses a time-series database (such as InfluxDB), suitable for storing massive amounts of time-series log data, supporting fast queries by time range (e.g., querying administrator operation records for a specific day). Considering the large volume of log data and its decreasing value over time, a data retention period (e.g., 3 months) is set. Log data exceeding the retention period is automatically archived to low-cost storage media (e.g., tape library) to avoid occupying storage resources in the business data area. Daily incremental backups are used, with backup data stored on a local standby server (since log data has lower real-time requirements than business data, off-site backup is unnecessary). Historical logs can be restored from the standby server if needed.

[0069] Business data and log data are stored separately to avoid slowing down business data queries due to large log data volumes (e.g., when querying port status, there's no need to scan massive amounts of log data). Simultaneously, appropriate databases are selected for different data types (relational databases are suitable for business data, while time-series databases are suitable for log data) to further improve query efficiency. The two areas are backed up independently: business data is backed up off-site to ensure core data is not lost; log data is backed up locally, balancing cost and traceability. Furthermore, the access permissions for the business data area are higher than those for the log data area (e.g., ordinary maintenance personnel can view log data but cannot modify business data), reducing the risk of data leakage or tampering. Log data is archived according to retention periods, freeing up storage space. Business data uses high-performance storage, while log data uses low-cost storage, balancing performance and cost. If the log data area fails (e.g., database crash), it will not affect the operation of the business data area (e.g., port status updates and route generation are unaffected), ensuring the normal operation of core system functions. Conversely, if the business data area fails, the log data area can still provide historical operation records for easy troubleshooting.

[0070] In some embodiments, when generating an ODF port release work order, the processing module will also simultaneously send the associated information of the release work order to the operation and maintenance work order system module. The associated information includes the port number to be released, the corresponding delisted device name and routing line identifier, so as to facilitate operation and maintenance personnel to quickly locate the port to be operated.

[0071] The associated information must be accurate and comprehensive to ensure that maintenance personnel can locate the port to be operated without additional queries. Specific information includes: Port numbers to be released: Clearly indicate the numbers of all ports that need to be released, in the format of data center name-ODF number-port number (e.g., 201 data center-ODF1-port 1, 405 data center-ODF3-port 6). If multiple ports are involved, separate them with commas. The corresponding delisted device name: indicate the delisted device associated with this port release (such as HWCE1688 switch), and clearly state the reason for release (routing failure caused by the delisting of this device) to avoid misunderstanding of the release purpose by maintenance personnel; Router identification: Mark the route identification to which the port to be released belongs (e.g., route ID: RT-20240501-001, route description: 201 computer room → 405 computer room), so that maintenance personnel can quickly find the corresponding route and confirm the port location in the visual interface; Current port status: Marks the current status of the port to be released (e.g., used (blue) → to be released (red)), prompting the operation and maintenance personnel to perform the operation (e.g., remove the jumper of the port); Implementation requirements: Specify the requirements for the release operation (e.g., the removal must be completed within 24 hours to avoid affecting other businesses, and the closing order must be confirmed in the system after removal) to ensure that the operation complies with the specifications.

[0072] The associated information is generated by the processing module and synchronized to the operation and maintenance work order system module. The specific process is as follows: After the processing module determines that the device removal work order is for a dual-end device, it extracts the port number to be released, the name of the associated removed device, the routing line identifier, and the current status of the port. The processing module generates associated information according to a preset format (such as JSON format) (Example: {Port number to be released: Room 201-ODF1-Port 1, Room 405-ODF3-Port 6, De-listed device name: HWCE1688 switch, Routing line identifier: RT-20240501-001 (Room 201 → Room 405), Current port status: Used → Pending release, Implementation requirement: Remove and close the order within 24 hours}). The processing module calls the interface of the operation and maintenance work order system module to synchronize the associated information to the ODF port to release the remarks field or attachment area of ​​the work order; After receiving the associated information, the operation and maintenance work order system module highlights it on the work order details page (e.g., using green font to mark the associated ODF information) and synchronizes the associated information to the implementation personnel's message notification when dispatching the work order (e.g., including a summary of the associated information in a WeChat message).

[0073] In summary, the embodiments of this application have the following beneficial effects: By constructing a system-linked architecture of "Operation and Maintenance Work Orders - Equipment Management - ODF Resources", the system achieves automated verification, pre-allocation, and closed-loop management of ODF resources across data centers. This not only solves the problems of scattered and inefficient traditional manual ledger information, but also avoids the costs of hardware upgrades and the risk of business interruption. At the same time, through port status color coding, full-link routing visualization, and historical record tracing functions, operation and maintenance personnel can intuitively identify port status and quickly locate faulty links. Combined with compatibility verification and timeout reminder mechanisms, the accuracy of port allocation and work order processing efficiency are further improved. Ultimately, this achieves refined and visualized management of ODF resources, effectively reducing resource idle rates and operation and maintenance costs, and ensuring the stable and reliable operation of high-speed optical links across data centers.

[0074] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some communication interfaces; the indirect coupling or communication connection of devices or modules can be electrical, mechanical, or other forms.

[0075] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0076] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for visualizing ODF resources, characterized in that, Includes the following steps: The system connects to the operation and maintenance work order system and the equipment management system to obtain operation and maintenance work order information and full equipment information. The operation and maintenance work orders include cross-data center cabling type work orders and equipment de-rack type work orders. When an approved cross-data center cabling work order is received, the routing information of the work order is verified to be correct, and the equipment management system is used to check whether the equipment involved in the work order has been entered into the system. If the routing information is correct and the device has been entered into the system, based on the location of the device in the data center in the work order, query the status of the ODF resource ports required for the corresponding data center and cross-data center fiber jumpers, traverse and search for idle ODF physical ports and pre-allocate them; If the verification fails, the verification result will be generated and the work order will be returned to the operation and maintenance work order system, with the reason for the return noted. Based on the pre-assigned ODF physical port status, adjust the port display color in the visualization interface, and after the work order is completed and closed, update the port status to "used" and generate the complete device routing information corresponding to the port. When an approved work order for removing a device from the rack is received, determine whether the device to be removed is a dual-end device in an ODF routing line. If it is a dual-end device, generate an ODF port release work order in the associated operation and maintenance work order system, update the status of the corresponding ODF port to pending release, and delete the routing information corresponding to the port after the release work order is completed. The status information, routing information, and operation records of the ODF port are stored in the database for data tracing and rollback.

2. The ODF resource visualization method according to claim 1, characterized in that, The specific correspondence between port display colors and status is as follows: unallocated status is displayed in white, pre-allocated status in yellow, used status in blue, pending release status in red, and faulty port status in black.

3. The ODF resource visualization method according to claim 1, characterized in that, The process of traversing and searching for available ODF physical ports and pre-allocating them also includes: matching the corresponding ODF ports in the room according to the patch cord requirements of cross-room cabling, and ensuring that the pre-allocated ports meet the physical connection conditions for cross-room optical path transmission.

4. The ODF resource visualization method according to claim 1, characterized in that, It also includes administrator operation procedures: granting administrators exclusive operation permissions, allowing them to view full information of ODF resource ports in each data center through a visual interface; It supports administrators to manually add, delete, and modify ODF port status and routing information in non-standard work order scenarios, and synchronizes and stores the administrator's operation records to the database.

5. The ODF resource visualization method according to claim 1, characterized in that, After the work order is completed and closed, the process of updating the port status to "used" and generating complete device routing information for the port also includes: displaying the complete routing information in the form of a route diagram through a visual interface, with the port number, the name of the connected device, the location of the device in the computer room, and the number of optical fiber cores marked on the route diagram.

6. An ODF resource visualization system, characterized in that, This includes a maintenance work order system module, an equipment management system module, and an ODF resource system module; The operation and maintenance work order system module is used to receive work order entries, classify work orders by cross-data center cabling type or equipment removal type, and conduct security approval of work orders, and synchronize the approved work order information to the ODF resource system module. The device management system module is used to store the name, location, model and room information of all devices, provide feedback on the device entry status according to the query request of the ODF resource system module, and update the corresponding device information when the device is put on or taken off the shelf. The ODF resource system module includes a processing module, a visualization module, a storage module, and an administrator module; The processing module is used to interface with the operation and maintenance work order system module and the equipment management system module, perform route verification and equipment entry verification for cross-data center cabling work orders, complete the pre-allocation of idle ODF ports, and perform dual-end device judgment for equipment removal work orders to generate ODF port release work orders. The visualization module is used to adjust the port display color according to the port status output by the processing module; and to generate or delete the routing information line diagram corresponding to the port according to the work order completion status, displaying the port number, device information and computer room location. The storage module is used to store the status information, routing information, work order operation records and administrator account authorization information of the ODF port, and supports data traceability and rollback; The administrator module is used to grant administrators operation permissions to the ODF resource system module, allowing administrators to manually adjust the port status and routing information of non-standard work orders.

7. The ODF resource visualization system according to claim 6, characterized in that, The processing module also has a timeout reminder function: after the port is pre-assigned for the cross-data center cabling work order, the progress of the work order is monitored in real time. When it is detected that the work order is less than the preset threshold before the preset completion time limit, a timeout reminder message is sent to the work order implementer to urge the work order to be completed.

8. The ODF resource visualization system according to claim 6, characterized in that, The routing information map generated by the visualization module supports interactive operation: administrators or authorized users can click on any port in the route map to expand and view the historical usage records of that port, including previously connected devices, usage time periods, and corresponding work order numbers.

9. The ODF resource visualization system according to claim 6, characterized in that, The storage module adopts a partitioned storage architecture: port status information and routing information are stored in the business data area, and work order operation records and administrator operation records are stored in the log data area. The business data area and the log data area are backed up independently to ensure data security.

10. The ODF resource visualization system according to claim 6, characterized in that, When generating an ODF port release work order, the processing module will also simultaneously send the associated information of the release work order to the operation and maintenance work order system module. The associated information includes the port number to be released, the name of the corresponding de-listed device, and the routing line identifier, so that operation and maintenance personnel can quickly locate the port to be operated.

Images