Optical cable main branch intelligent operation and maintenance management method based on map node port cooperative linkage

Abstract

The application relates to the field of communication network resource management, and discloses an optical cable main-branch intelligent operation and maintenance management method based on map node port cooperative linkage, which comprises the following steps: acquiring node information to perform differential attribute calculation, establishing an association model, and outputting a standardized object set; performing path identification and hierarchical division to construct an associated topology model and output topology data; then performing access capability verification and fiber core mapping to output to-be-verified routing data; performing fiber core capacity margin constraint and port capacity verification to output verified routing data; identifying a machine room node and performing indoor equipment binding to output path node data; analyzing spatial distance to calculate line length and output main-branch optical cable storage data; performing port matching and binding based on storage and node data type identification to output service data; responding to a modification request to identify change classification processing and output update data; acquiring a target cable core identifier to construct a path chain associated port context and output trace information, and realizing integrated linkage management.

Description

Technical Field

[0001] This invention relates to the field of communication network resource management technology, and more specifically to an intelligent operation and maintenance management method for optical cable main branches based on map node port collaborative linkage. Background Technology

[0002] In the operation and maintenance management of optical communication networks, optical cable paths are typically spatially located using node coordinates in a geographic information system (GIS). Simultaneously, a resource ledger system maintains indoor equipment objects such as ODFs, cabinets, and switches, along with their port occupancy status. These two systems operate independently. In actual operation and maintenance, operators need to sequentially select nodes such as manholes, turning points, optical distribution boxes, connector packages, and equipment rooms on a map to construct the main line. Branch cables are then configured at the optical distribution box or connector package nodes, allocating core counts to each branch cable and designating a first node, forming a tree-like hierarchical structure of main and branch optical cables. When a node in the equipment room connects, the target device must be selected from the available ODF devices in that equipment room and bound. After the path is saved, the system automatically calculates the line length, generates cable core codes, performs port resource matching, and updates the device status. When the path is modified, the change type must be identified, and data consistency must be maintained. Operation and maintenance personnel also need to trace specific cable cores, querying the complete sequence of nodes they pass through and the port binding relationships at each node. The above process involves the collaborative management of map nodes, optical cable main and branch structures, cable core numbering system, and port resources such as optical distribution boxes, connector packages, equipment room ODF, and switches.

[0003] However, during the aforementioned operation and maintenance process, map nodes and resource ledgers operate independently, lacking a node-resource association model based on differentiated attribute calculations. This results in a lack of unified association between spatial coordinates and port resources, requiring manual verification. The hierarchical structure and core allocation of main and sub-optical cables rely on manual configuration, lacking mechanisms for constructing main-branch association topology models, verifying routing node access capabilities, mapping branch fiber cores, and verifying fiber core capacity margins and port capacities, which easily leads to over-provisioning of sub-cable cores. When accessing data center nodes, the system typically cannot automatically identify data center type nodes and perform indoor access device resource binding. After path modification, there is a lack of identification and classification mechanisms for structural change types, resulting in distortion of basic data. When tracing cable cores, it is difficult to construct cable core path chains and associate them with port binding contexts, making it impossible to form a complete path view. Summary of the Invention

[0004] In order to overcome the above-mentioned defects of the prior art, the present invention provides an intelligent operation and maintenance management method for optical cable main branches based on map node port collaborative linkage, so as to solve the problems existing in the background art.

[0005] This invention provides the following technical solution: an intelligent operation and maintenance management method for optical cable main branches based on map node port collaborative linkage, comprising:

[0006] S1: Obtain optical communication network node information, perform differentiated attribute calculations, obtain the path constraint weights and port availability coefficients of each node, establish a node-resource association model, and output a standardized set of node objects.

[0007] S2: Construct a fiber optic cable main branch association topology model based on a standardized set of node objects, and output fiber optic cable topology data;

[0008] S3: Verify the access capabilities of routing nodes and branch fiber core mapping based on optical cable topology data, and output the routing data to be verified;

[0009] S4: Constrain fiber core capacity margin and verify port capacity based on optical cable topology data and routing data to be verified, and output verified routing data;

[0010] S5: Identify data center type nodes based on verified routing data and bind access device resources, then output path node data;

[0011] S6: Based on the verified routing data, parse the spatial distance between nodes and calculate the line length, and output the main and branch optical cable storage data;

[0012] S7: Identify node types and bind port resources based on the main and branch optical cable storage data and path node data, and output resource service data;

[0013] S8: Respond to path modification requests, identify and classify structural change types based on resource business data, and output updated resource business data;

[0014] S9: Obtain the target cable core identifier, construct the cable core path chain based on the main and branch optical cable storage data and updated resource service data, associate it with the port binding context, and output the cable core level traceability information.

[0015] Preferably, step S1 involves acquiring optical communication network node information, calculating differentiated attributes to obtain the path constraint weights and port availability coefficients for each node, establishing a node-resource association model, and outputting a standardized set of node objects. Specifically, this includes:

[0016] S11: Acquire node source data and perform data cleaning and parsing. Collect raw discrete data from geographic information systems and resource management systems through interface calls. Perform format verification and outlier removal on the raw discrete data. Output a standardized basic data stream containing spatial coordinates, associated optical cable characteristic attributes, and node attribute fields.

[0017] S12: Map the physical entity points in the optical cable path to unified node objects according to predefined topology rules, and construct the attribute structure of the node objects. The attribute structure includes a basic attribute set and an extended attribute set. The basic attribute set encapsulates the node number, node type, latitude and longitude, address information, connection relationship between nodes, associated optical cable layer type, associated optical cable fiber core specification and equipment resource identifier. The extended attribute set is reserved for storing the binding resource identifier and port status information.

[0018] S13: Perform differential attribute calculations based on the node type field in the standardized basic data stream, and write the corresponding calculation results into the extended attribute set, specifically including:

[0019] When the node type field is a well or a bend, resource retrieval is skipped. The sequence position weight is calculated based on the ratio of the node's position number in the optical cable path to the total number of nodes in the path. The local link span is calculated based on the spatial coordinates of the node and its adjacent upstream and downstream nodes. The spatial span weight is calculated based on the ratio of the local link span to the total span of the optical cable path. The sequence position weight and the spatial span weight are weighted and fused to obtain the path mandatory constraint weight. This path mandatory constraint weight is written into the extended attribute set.

[0020] When the node type field is "data center", the node number in the basic attribute set is used as the search key. The corresponding data center resource type, ODF identifier, switch identifier, cabinet identifier, resource name and cabinet name are extracted from the resource management system and written into the extended attribute set. At the same time, the total number of ODF ports, the total number of used ports and the number of shared ports that support multiple services among the used ports are retrieved. Based on the total number of ODF ports, the total number of used ports, the number of shared ports and the preset multiplexing conversion factor, the port availability coefficient of the data center node is calculated. When the port availability coefficient is lower than the preset availability threshold, a port overload identifier is generated; otherwise, a port availability identifier is generated. The total number of physical ports, the number of occupied ports, the port availability coefficient and the generated identifier of the data center node are written into the extended attribute set, and a bidirectional index mapping relationship between the node number and the physical resource identifier is generated.

[0021] When the node type field is optical distribution box or connector package, based on the device identification data in the basic attribute set, the total number of physical ports, the number of occupied ports, and the number of shared ports supporting multiple service reuse among the occupied ports are retrieved from the port resource table. Based on the total number of physical ports, the number of occupied ports, the number of shared ports, and the preset multiplexing conversion factor, the port availability coefficient of the optical distribution box or connector package node is calculated. When the port availability coefficient is lower than the preset availability threshold, an access restricted identifier is generated; otherwise, an access unimpeded identifier is generated. The total number of physical ports, the number of occupied ports, the port availability coefficient, and the generated identifier are written into the extended attribute set.

[0022] S14: Summarize and serialize the node objects that have completed the writing of the extended attribute set, establish a node-resource association model, and output a standardized set of node objects.

[0023] Preferably, step S2 constructs a fiber optic cable main-branch association topology model based on a standardized set of node objects and outputs fiber optic cable topology data, specifically including:

[0024] Extract the node connection relationship data of the basic attribute set in the standardized node object set, and map the node sequence with continuous connection relationship to single optical cable path data; based on the topological features of the optical cable path and the associated optical cable level type in the node basic attribute set, identify whether the optical cable path is a main optical cable or a sub-optical cable and assign the corresponding level identifier, generate a parent optical cable identifier for the identified sub-optical cable, and establish its association relationship with the upper-level optical cable based on the parent optical cable identifier to construct a multi-level tree topology structure;

[0025] For the main optical cable, read the associated optical cable core specification data from the basic attribute set of its node and generate complete core sequence data with a unique serial number; for the sub-optical cable, obtain the starting core serial number and ending core serial number of its planned configuration, and logically segment the core sequence data from the corresponding parent optical cable or top-level main optical cable based on the serial number range to generate the core mapping range data of the sub-optical cable.

[0026] The generated fiber core mapping range data is subjected to inheritance conflict detection. The fiber core mapping range of the same level sub-optical cable is compared to see if there is an overlapping range. The cable core inheritance conflict index is calculated based on the ratio of the number of fiber cores in the overlapping range to the total number of fiber cores to be allocated. The cable core inheritance conflict index is compared with the preset conflict threshold. When the cable core inheritance conflict index exceeds the preset conflict threshold, a conflict alarm sign is generated; otherwise, a valid inheritance sign is generated.

[0027] Traverse the optical cable path data that has completed hierarchical division and fiber core mapping, associate and bind the node number and node type with the optical cable identifier, update and write it into the node association table, and integrate the multi-level tree topology structure, fiber core mapping range data and collision detection identifier to output the optical cable topology structure data.

[0028] Preferably, step S3 verifies the access capability of routing nodes and branch fiber core mapping based on optical cable topology data, and outputs the routing data to be verified, specifically including:

[0029] Based on the standardized set of node objects and optical cable topology data, the selected main line node sequence is extracted, and the main line path data is constructed according to the connection relationship between nodes in the basic attribute set.

[0030] When the node type of the main line tail node or the tail node of the already constructed branch cable is an optical distribution box or connector package, the branch cable branching logic is triggered; the branch cable configuration parameters are obtained, including the number of branch cables, the number of cores in each branch cable, and the first node number;

[0031] Access capability verification is performed by extracting the identifier data from the extended attribute set of the corresponding node object based on the first node number. Specifically, when the first node is an optical distribution box or connector package, the access smoothness identifier in its extended attribute set is identified. If the identifier exists, the first node is determined to have access capability. When the first node is a computer room, the port availability identifier in its extended attribute set is identified. If the identifier exists, the first node is determined to have access capability.

[0032] For each sub-cable that passes verification, logical segmentation is performed based on its core count parameter and the core sequence data of the upper-level optical cable in the optical cable topology data to generate fiber core mapping range data for each sub-cable. The generated fiber core mapping range data is compared with the existing mapping ranges in the same-level sub-cable and optical cable topology data, and core inheritance conflict detection is performed to generate corresponding conflict detection identifiers. Based on the conflict detection identifiers, parent identifiers are assigned to each sub-cable and a sub-cable tree structure is constructed.

[0033] Finally, the main line path data, branch cable relationships, fiber core mapping range data, and conflict detection identifiers are integrated to output the route data to be verified, which includes node connection relationships, branch attributes, and branch cable configuration information. The branch attributes are specifically the branch cable tree structure.

[0034] Preferably, step S4 constrains fiber core capacity margin and verifies port capacity based on optical cable topology data and routing data to be verified, and outputs verified routing data, specifically including:

[0035] Based on the cable tree structure in the routing data to be verified and the hierarchical inheritance relationship in the optical cable topology data, the fiber core mapping range data of each level of cable is extracted from top to bottom to calculate the allocated fiber core quantity. Combined with the fiber core specification data of the associated optical cable of the node to which the parent optical cable belongs in the standardized node object set, the remaining allocable fiber core quantity is calculated. When the core number parameter of the cable to be verified is greater than the remaining allocable fiber core quantity of its parent optical cable, a fiber core capacity over-limit flag is generated.

[0036] Simultaneously, based on the routing data to be verified, the target nodes traversed by the main line and branch cables are extracted. Based on the number of cores in each branch cable in the branch cable configuration information and the preset fiber core port mapping rules, the new port demand of each target node is calculated. Combined with the number of occupied ports in the corresponding node extended attribute set in the standardized node object set, the total port demand is calculated. The total port demand is compared with the total number of physical ports of the corresponding node. When the total port demand is greater than the total number of physical ports, a port capacity conflict identifier is generated and the corresponding node number is associated with it and output.

[0037] When no fiber core capacity over-limit flag or port capacity conflict flag is generated, the routing data to be verified is marked as valid for verification, and a pre-occupancy lock operation is performed on the new port requirements involved in the verification, and the verified routing data is output; otherwise, verification abnormal data containing the corresponding conflict flag is output.

[0038] Preferably, step S5 identifies data center type nodes based on verified routing data and binds them to access device resources, outputting path node data, specifically including:

[0039] Traverse the node sequence in the verified routing data. When the node type is identified as a data center, extract the identification data from the extended attribute set of the node object to determine the access status: if there is a port overload indicator, generate a resource shortage alarm indicator; if there is a port available indicator, trigger the resource binding logic.

[0040] Based on the ODF identifier and bidirectional index mapping relationship recorded in the extended attribute set of the data center node, the corresponding available ODF device data is retrieved; the selected target ODF identifier is obtained, the resource name and data center resource type corresponding to the target ODF are extracted, and the target ODF identifier, resource name and data center resource type are updated and written into the extended attribute set of the data center node object to complete the mapping and binding from the geographic coordinate node to the physical access resource.

[0041] The node data that has been bound to the resource is integrated with the verified route data to output the path node data.

[0042] Preferably, step S6 parses the spatial distance between nodes based on the verified routing data and calculates the line length, outputting the main and branch optical cable storage data, specifically including:

[0043] Extract the node sequence based on the verified routing data, and read the latitude and longitude or spatial coordinates from the basic attribute set of the standardized node object set. Calculate the geographical distance between adjacent nodes and accumulate them to obtain the physical length of the line. Update the verified routing data with the physical length of the line as the standard length data.

[0044] Perform the main and branch optical cable saving operation, generate the main optical cable code and cable core code for the main optical cable, and write the main optical cable code and cable core code into the node association table according to the node order; for the sub-optical cable, extract the parent identifier of the sub-cable tree structure and the fiber core mapping range data from the verified routing data, generate the sub-optical cable exclusive cable core code based on the cable core code and fiber core mapping range of the parent optical cable, and bind the fiber core mapping range data to the sub-optical cable path;

[0045] Finally, the main optical cable code, cable core code, node sequence, line physical length and fiber core mapping range data are integrated to output the main and branch optical cable storage data.

[0046] Preferably, step S7 identifies node types and binds port resources based on the main and branch optical cable storage data and path node data, and outputs resource service data, specifically including:

[0047] Based on the node order in the main optical cable storage data, the corresponding nodes are extracted, and the node type is matched, located, and identified in the standardized node object set.

[0048] When the node type is an optical distribution box or connector package, the total number of physical ports, the number of occupied ports, and the number of shared ports in the node's extended attribute set are extracted to perform port allocation: priority is given to allocating shared ports that support multiple service reuse from the occupied ports, and any shortfall is made up from the remaining available physical ports in sequence; based on the allocation result, the corresponding cable core code is bound to the port identifier to generate a service resource binding record, the number of occupied ports in the node's extended attribute set is increased and updated; when the remaining available physical ports cannot meet the demand, a port resource shortage alarm is generated;

[0049] When the node type is a data center, extract the target ODF identifier that has been bound in the extended attribute set of the node and allocate the ODF port to the corresponding cable core code. At the same time, based on the switch identifier and cabinet identifier in the extended attribute set, establish the mapping relationship from the cable core code to the switch port via the ODF port and generate a service resource binding record that includes the mapping of equipment in the data center.

[0050] When the node type is a well or a turning point, extract the path constraint weights from the node's extended attribute set and write them into the business resource binding record as routing scheduling parameters.

[0051] Finally, the business resource binding records of all nodes are integrated, and the main optical cable code, cable core code, node order, line physical length and fiber core mapping range data in the main and branch optical cable storage data are combined to output resource business data.

[0052] Preferably, the S8 response path modification request identifies and classifies the structural change type based on resource business data, and outputs updated resource business data, specifically including:

[0053] By comparing the changed data in the path modification request with the resource business data and the standardized node object set item by item, three types of structural changes were identified:

[0054] When only the latitude, longitude, or address information in the basic attribute set of the standardized node object set changes, and the cable branching relationship in the resource business data remains unchanged, it is determined to be a basic attribute level change; the corresponding fields in the basic attribute set are updated, and the physical length of the line is recalculated based on the updated latitude and longitude to update the resource business data;

[0055] When a non-critical access node is added or deleted, or the order of path nodes changes, but the set of critical node identifiers at the beginning and end points is not added or deleted, and the ODF port mapping relationship and switch port mapping relationship in the resource service data remain unchanged, it is determined to be a path node-level change. The physical length of the line is recalculated based on the updated node order and the spatial coordinates in the basic attribute set of the standardized node object set and updated to the resource service data. At the same time, the path must-pass constraint weights in the extended attribute set of the associated nodes under this path are recalculated and updated. The path node relationship and routing scheduling parameters in the resource service data are incrementally synchronized.

[0056] When the branch cable relationship, ODF port mapping relationship, or switch port mapping relationship in the resource service data changes, it is determined to be a change at the main branch structure level. First, release all port binding relationships under the main optical cable tree according to the resource service data, and reduce and update the number of occupied ports in the corresponding node extended attribute set. Then, recursively delete the association records and old binding data of all sub-optical cables under the main optical cable tree according to the node association table. Then, re-execute steps S4 to S7 according to the modified path to generate new resource service data, and finally output the updated resource service data.

[0057] Preferably, step S9 acquires the target cable core identifier, constructs a cable core path chain based on the main and branch optical cable storage data and updated resource service data, associates it with the port binding context, and outputs cable core-level traceability information, specifically including:

[0058] Based on the target cable core identifier and the fiber core mapping range data and sub-cable tree structure in the main branch optical cable storage data, the cable core path chain is constructed from the top main optical cable to the top main optical cable identifier by tracing back along the parent identifier in the sub-cable tree structure through each level of sub-optical cable to the target cable core.

[0059] Extract the node sequence of each level of optical cable record on the cable core path chain, trim and remove duplicate node sequences where the first node of the branch is the same in two adjacent optical cables, and merge them in topological order to generate the complete node sequence of the target cable core.

[0060] Based on the node identifiers in the complete sequence of nodes, extract the service resource binding records of the corresponding nodes from the updated resource service data; for optical distribution box or connector packet nodes, extract the binding relationship between cable core codes and port identifiers; for equipment room nodes, extract the mapping relationship between cable core codes via ODF ports to switch ports; and form the port binding context of the target cable core by concatenating the nodes in sequence.

[0061] Simultaneously, the target ODF identifier, resource name, data center resource type, switch identifier, and cabinet identifier are attached to the data center nodes in the complete traversed node sequence as extended attributes. Finally, the target cable core identifier, the complete traversed node sequence, port binding context, and additional device identifier information are integrated to output cable core-level traceability information.

[0062] The technical effects and advantages of this invention are as follows:

[0063] (1) Obtain node information through S1 to perform differential attribute calculation, obtain the path must-pass constraint weight and port availability coefficient, establish a node-resource association model, and directly read the status and information from the node object when matching and binding port resources through S7. At the same time, S4 performs port capacity verification to automatically compare the required number of cores and the number of available ports, which is beneficial for operators to complete port verification and binding simultaneously when drawing paths on the map without switching pages, thus improving efficiency and reducing error rate.

[0064] (2) The optical cable main branch association topology model is constructed through S2, the access capability verification of routing nodes and the branch fiber core mapping are performed in combination with S3, and the fiber core capacity margin constraint verification is performed through S4. The remaining allocable core number is calculated from top to bottom. When the total number of cores of the branch cable exceeds the remaining core number of the parent, the submission is prohibited. This solves the problems of the main branch hierarchical structure and core number allocation relying on manual configuration, lack of main branch association topology construction, access verification, branch mapping and capacity verification mechanism, and easy generation of branch cable core number over-allocation. It is conducive to preventing core number over-allocation in real time during the path drawing process and ensuring the accuracy of main branch structure data.

[0065] (3) By identifying the type of data center node through S5 and performing indoor access device resource binding, the data center resource linkage selection mechanism is triggered and the target ODF identifier and other information are written into the node object. This solves the problem that the system cannot automatically identify the type of data center node and perform indoor access device resource binding when the data center node is accessed, and cannot complete the port occupation and cable core association linkage update when saving the path. This is conducive to the automatic establishment of continuous links between outdoor optical cable path and indoor access resources.

[0066] (4) By responding to the path modification request through S8, the structural change type is identified and classified, which solves the problem that the lack of identification and classification mechanism for structural change type after path modification leads to inconsistencies in optical cable length, node status, port binding relationship and sub-cable level, and distortion of basic data. This is conducive to ensuring data consistency before and after modification, and ensuring that the basic data on which inspection, fault location and resource scheduling depend are always accurate.

[0067] (5) By obtaining the target cable core identifier through S9, constructing the cable core path chain and associating it with the port binding context, the problem of difficulty in constructing the cable core path chain and associating it with the port binding context when tracing the cable core is solved, and the problem of not being able to form a complete path view along the main cable, sub-cable, node, and port to the equipment room resources is solved. This is conducive to the operation and maintenance personnel to directly locate each node and port resource that the cable core passes through, and to support fault location and resource verification.

[0068] (6) By using S4 to simultaneously perform fiber core capacity margin constraint verification and port capacity verification, the dual constraints are executed in parallel and conflict alarms are output. This is beneficial to complete the full verification of the number of cores and ports at one time before saving the path, avoid the risk of omission caused by step-by-step verification, and improve verification efficiency and reliability. Attached Figure Description

[0069] Figure 1 This is a diagram illustrating the method steps of the present invention. Detailed Implementation

[0070] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. In addition, the forms of the various structures described in the following embodiments are merely illustrative. The intelligent operation and maintenance management method for optical cable main branches based on map node port collaborative linkage involved in the present invention is not limited to the structures described in the following embodiments. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0071] like Figure 1 The embodiment shown provides an intelligent operation and maintenance management method for optical cable main branches based on map node port collaborative linkage, including:

[0072] S1: Obtain information about optical communication network nodes, perform differentiated attribute calculations, obtain the path constraint weights and port availability coefficients of each node, establish a node-resource association model, and output a standardized set of node objects.

[0073] In this embodiment, S1 acquires optical communication network node information, performs differentiated attribute calculations, obtains the path constraint weights and port availability coefficients of each node, establishes a node-resource association model, and outputs a standardized set of node objects. Specifically, this includes:

[0074] S11: Acquire node source data and perform data cleaning and parsing. Collect raw discrete data from geographic information systems and resource management systems through interface calls. Perform format verification and outlier removal on the raw discrete data. Output a standardized basic data stream containing spatial coordinates, associated optical cable characteristic attributes, and node attribute fields.

[0075] S12: Map the physical entity points in the optical cable path to unified node objects according to predefined topology rules, and construct the attribute structure of the node objects. The attribute structure includes a basic attribute set and an extended attribute set. The basic attribute set encapsulates the node number, node type, latitude and longitude, address information, connection relationship between nodes, associated optical cable layer type, associated optical cable fiber core specification and equipment resource identifier. The extended attribute set is reserved for storing the binding resource identifier and port status information.

[0076] S13: Perform differential attribute calculations based on the node type field in the standardized basic data stream, and write the corresponding calculation results into the extended attribute set, specifically including:

[0077] When the node type field is a well or a bend, resource retrieval is skipped. The sequence position weight is calculated based on the ratio of the node's position number in the optical cable path to the total number of nodes in the path. The local link span is calculated based on the spatial coordinates of the node and its adjacent upstream and downstream nodes. The spatial span weight is calculated based on the ratio of the local link span to the total span of the optical cable path. The sequence position weight and the spatial span weight are weighted and fused to obtain the path mandatory constraint weight. This path mandatory constraint weight is written into the extended attribute set.

[0078] When the node type field is "data center", the node number in the basic attribute set is used as the search key. The corresponding data center resource type, ODF identifier, switch identifier, cabinet identifier, resource name and cabinet name are extracted from the resource management system and written into the extended attribute set. At the same time, the total number of ODF ports, the total number of used ports and the number of shared ports that support multiple services among the used ports are retrieved. Based on the total number of ODF ports, the total number of used ports, the number of shared ports and the preset multiplexing conversion factor, the port availability coefficient of the data center node is calculated. When the port availability coefficient is lower than the preset availability threshold, a port overload identifier is generated; otherwise, a port availability identifier is generated. The total number of physical ports, the number of occupied ports, the port availability coefficient and the generated identifier of the data center node are written into the extended attribute set, and a bidirectional index mapping relationship between the node number and the physical resource identifier is generated.

[0079] When the node type field is optical distribution box or connector package, based on the device identification data in the basic attribute set, the total number of physical ports, the number of occupied ports, and the number of shared ports supporting multiple service reuse among the occupied ports are retrieved from the port resource table. Based on the total number of physical ports, the number of occupied ports, the number of shared ports, and the preset multiplexing conversion factor, the port availability coefficient of the optical distribution box or connector package node is calculated. When the port availability coefficient is lower than the preset availability threshold, an access restricted identifier is generated; otherwise, an access unimpeded identifier is generated. The total number of physical ports, the number of occupied ports, the port availability coefficient, and the generated identifier are written into the extended attribute set.

[0080] S14: Summarize and serialize the node objects that have completed the writing of the extended attribute set, establish a node-resource association model, and output a standardized set of node objects.

[0081] It should be noted that the specific process of obtaining optical communication network node information and establishing a unified node-resource association model is as follows:

[0082] First, step S11 is executed, which calls the Geographic Information System (GIS) and Resource Management System (RMS) through RESTful interfaces to obtain raw discrete data. The data returned by the GIS includes the latitude and longitude coordinates, address descriptions, and administrative region information of each node. The data returned by the RMS includes the ODF equipment list, cabinet list, switch list, and port resource list of each optical distribution box and connector package for each computer room. The above raw discrete data is then subjected to format validation, specifically: checking whether the latitude and longitude fields are valid WGS84 coordinate coefficient values, whether the node number conforms to the preset encoding rules (such as the format "region code-equipment type code-serial number"), and whether the port quantity field is a non-negative integer. Data records that do not conform to the above rules are marked as abnormal records and removed. After removal, a standardized basic data stream containing spatial coordinates and attribute fields is output.

[0083] Then, step S12 is executed, mapping the physical entity points (i.e., actual manholes, bends, optical distribution boxes, equipment rooms, and connector packages) in the optical cable path according to predefined topology rules. These topology rules are: for two physical entity points with consecutive serial numbers in the node association table within the same optical cable path, if there is an optical cable physical connection between them, an adjacency relationship is established in the node object; if the serial numbers in the node association table are not consecutive, or if the serial numbers are consecutive but there is no optical cable physical connection between them, an adjacency relationship is not established. After mapping, the attributes of the node objects are constructed. The structure consists of two layers: a basic attribute set and an extended attribute set. The basic attribute set contains fields common to all node objects, encapsulating the node number (unique identifier), node type (enumerated values: manhole, bend point, optical distribution box, equipment room, connector package), latitude and longitude (WGS84 coordinate system), address information (province-city-district-detailed address), and equipment resource identifier (the identifier of the optical cable currently bound to the node; if not bound, it is empty). The extended attribute set contains fields that differentiate each node object, used to store resource attributes and port status information unique to each type of node.

[0084] Next, step S13 is executed, which involves performing differential correlation analysis and calculation based on the node type field in the standardized basic data stream, and then executing state assessment and access control logic, specifically in three cases:

[0085] In the first scenario, when the node type field is a manhole or bend point, the search of the resource management system is skipped, and the path constraint weight is calculated based on the node's position and spatial characteristics in the optical cable path topology. The specific calculation method is as follows: First, the sequence position weight is calculated based on the ratio of the node's position number in the optical cable path to the total number of nodes in the path. The formula is: Sequence position weight = Position number / Total number of nodes in the path. This weight reflects the relative importance of the node's position in the path topology. Second, the local link span is calculated based on the spatial coordinates of the node and its adjacent upstream and downstream nodes. Adjacent upstream and downstream nodes refer to the node directly topologically adjacent to the current node (i.e., the upstream predecessor node) and the next node (i.e., the downstream successor node) in the node sequence of the optical cable path, determined by the connection relationship between nodes. If the node is the starting point of the path and has no upstream nodes, its own coordinates are considered upstream coordinates; if the node is the ending point of the path and has no upstream nodes, its own coordinates are considered upstream coordinates. Downstream nodes are treated as having their own coordinates as downstream coordinates. The formula for calculating the local link span is: Local link span = [Dist(this node, upstream node) + Dist(this node, downstream node)] / 2, where Dist is the geographical distance calculated based on spatial coordinates. The spatial span weight is calculated based on the ratio of the local link span to the total span of the optical cable path (the sum of the geographical distances of all adjacent nodes along the entire path), using the formula: Spatial span weight = Local link span / Total optical cable path span. This weight reflects the proportion of the physical span of the segment where the node is located. Finally, the sequence position weight and the spatial span weight are weighted and fused to obtain the path mandatory constraint weight, using the formula: Path mandatory constraint weight = Sequence position weight + Spatial span weight, where The preset weight adjustment coefficient (with a value range of 0.5 to 0.8, which can be set according to the engineering experience of network topology regarding location sensitivity and span sensitivity, for example, the default value is 0.6, which indicates a slight emphasis on the positional constraint of the node in the path sequence) is used to determine whether the node is an unavoidable necessary node during subsequent S4 path verification. The higher the weight value, the stronger the constraint of the node in the path. The necessary constraint weight of the path is written into the extended attribute set as a prerequisite parameter for subsequent path verification and route planning.

[0086] In the second scenario, when the node type field is "data center," the system uses the node number in the basic attribute set as the search key to query and extract the corresponding data center resource type (e.g., core data center, access data center, edge data center), ODF identifier (unique identifier for ODF devices), switch identifier (unique identifier for switch devices), rack identifier (unique identifier for racks), resource name (e.g., "ODF-01, 1st Floor, Building A"), and rack name (e.g., "Rack No. 01, 1st Floor, Building A") from the resource management system and writes them into the extended attribute set. Simultaneously, it retrieves the total number of ODF ports, the total number of used ports, and the number of shared ports supporting multi-service reuse among the used ports. Based on the above retrieved data and the preset reuse conversion factor, the port availability coefficient of the data center node is calculated. The formula for calculating the port availability coefficient is: Port Availability Coefficient = (Total ODF Ports - Total Used Ports + Shared Ports) The multiplexing conversion factor is calculated as follows: (multiplexing conversion factor) / total number of ODF ports. The multiplexing conversion factor is a value greater than 0 and less than 1 (preferably set to 0.5). It is set based on the equivalent carrying capacity of optical communication equipment ports when they support multiple service multiplexing (such as wavelength division multiplexing or time slot multiplexing). It is used to convert a shared port into the equivalent proportion of available physical ports, thereby more accurately reflecting the actual remaining carrying capacity. When the calculated port availability factor is lower than the preset availability threshold, a port overload flag is generated; otherwise, a port availability flag is generated. The availability threshold is set to 0.2 (i.e., the remaining equivalent availability is considered overloaded if it is less than 20%). This threshold is set to ensure the safety redundancy of the core access nodes in the data center and to avoid the risk of service interruption due to port exhaustion. Subsequently, the total number of ODF ports of the data center node is used as the total number of physical ports, and the total number of used ports is used as the number of occupied ports. These, along with the port availability coefficient and the generated identifier, are written into the extended attribute set. In addition, a bidirectional index mapping relationship between node number and physical resource identifier is generated. The bidirectional index mapping relationship means that a forward index (all corresponding physical resource identifiers can be found through the node number) and a reverse index (the corresponding node number can be found through any physical resource identifier) ​​are established, thereby supporting bidirectional retrieval from node to resource and from resource to node when tracing the S9 cable core.

[0087] In the third scenario, when the node type field is an optical distribution box or connector packet, based on the device identification data in the basic attribute set, the total number of physical ports, the number of occupied ports, and the number of shared ports supporting multi-service multiplexing among the occupied ports are retrieved from the port resource table. Based on the total number of physical ports, the number of occupied ports, the number of shared ports, and the preset multiplexing conversion factor, the port availability coefficient of the optical distribution box or connector packet node is calculated. The formula for calculating the port availability coefficient is: Port Availability Coefficient = (Total Number of Physical Ports - Number of Occupied Ports + Number of Shared Ports) The port availability coefficient is calculated as (multiplexing conversion factor) / total number of physical ports, where the multiplexing conversion factor is set based on the same criteria as the data center node (preferably 0.5), aiming to objectively assess the true remaining capacity of outdoor access equipment. When the port availability coefficient is lower than a preset availability threshold, an access-restricted flag is generated; otherwise, an access-complete flag is generated. The availability threshold is set to 0.2, designed to prevent the depletion of outdoor node access resources from affecting cable branching capabilities. The total number of physical ports, the number of occupied ports, the port availability coefficient, and the generated flag are written into the extended attribute set. By introducing a shared port quantity supporting multi-service multiplexing and a multiplexing conversion factor to calculate the port availability coefficient, the actual available carrying capacity of node ports can be more accurately reflected, avoiding misjudgments of availability caused by simply calculating physical port occupancy.

[0088] Finally, step S14, which constructs the node-resource association model and outputs a standardized set of node objects, is executed as follows: The system extracts all node objects that have completed the writing of the extended attribute set into memory. Based on the node connection relationship field in the node's basic attribute set, directed reference pointers are established between node objects, thereby constructing a graph data structure in memory with nodes as vertices and optical cable physical connections as edges, which is the node-resource association model. Subsequently, the nodes are sorted according to their numbers, and JSON serialization technology is used to transform the graph data structure into a standardized data stream that can be persistently stored and transmitted over the network. A standardized JSON array format containing "node number - basic attribute key-value pairs - extended attribute key-value pairs" is defined, thereby outputting a standardized set of node objects. Since the geospatial coordinates, topological adjacency relationships, fiber core specifications, and real-time port status have been integrated and encapsulated during the model construction phase, this set can be directly called by each step from S2 to S9 using the node number or resource identifier as the primary key, without needing to repeatedly query discrete data across systems in subsequent processes.

[0089] S2: Construct a fiber optic cable main branch association topology model based on a standardized set of node objects, and output fiber optic cable topology data.

[0090] In this embodiment, S2 constructs a fiber optic cable main-branch association topology model based on a standardized set of node objects and outputs fiber optic cable topology data, specifically including:

[0091] Extract the node connection relationship data of the basic attribute set in the standardized node object set, and map the node sequence with continuous connection relationship to single optical cable path data; based on the topological features of the optical cable path and the associated optical cable level type in the node basic attribute set, identify whether the optical cable path is a main optical cable or a sub-optical cable and assign the corresponding level identifier, generate a parent optical cable identifier for the identified sub-optical cable, and establish its association relationship with the upper-level optical cable based on the parent optical cable identifier to construct a multi-level tree topology structure;

[0092] For the main optical cable, read the associated optical cable core specification data from the basic attribute set of its node and generate complete core sequence data with a unique serial number; for the sub-optical cable, obtain the starting core serial number and ending core serial number of its planned configuration, and logically segment the core sequence data from the corresponding parent optical cable or top-level main optical cable based on the serial number range to generate the core mapping range data of the sub-optical cable.

[0093] The generated fiber core mapping range data is subjected to inheritance conflict detection. The fiber core mapping range of the same level sub-optical cable is compared to see if there is an overlapping range. The cable core inheritance conflict index is calculated based on the ratio of the number of fiber cores in the overlapping range to the total number of fiber cores to be allocated. The cable core inheritance conflict index is compared with the preset conflict threshold. When the cable core inheritance conflict index exceeds the preset conflict threshold, a conflict alarm sign is generated; otherwise, a valid inheritance sign is generated.

[0094] Traverse the optical cable path data that has completed hierarchical division and fiber core mapping, associate and bind the node number and node type with the optical cable identifier, update and write it into the node association table, and integrate the multi-level tree topology structure, fiber core mapping range data and collision detection identifier to output the optical cable topology structure data.

[0095] It should be specifically explained that the specific process of identifying optical cable paths and dividing main and branch hierarchies based on a standardized set of node objects, and constructing an optical cable main and branch association topology model is as follows:

[0096] First, the connection relationship data between nodes in the basic attribute set of the standardized node object set is extracted. The term "having a continuous connection relationship" means that on the physical optical cable route, two nodes are directly physically connected as the beginning and end of the same optical cable segment, and are adjacent to each other without any other nodes in the network logical topology sequence. The node sequence with continuous connection relationship is mapped to single optical cable path data. Based on the topological characteristics of the optical cable path and the associated optical cable level type in the node basic attribute set, the optical cable path is identified as either a main optical cable or a sub-optical cable and assigned a corresponding level identifier. "Main optical cable" refers to the backbone optical cable that directly connects to the core equipment room or aggregation node, and "sub-optical cable" refers to the lower-level access optical cable that branches off from the main optical cable or the upper-level optical cable. At the same time, a parent optical cable identifier is generated for the identified sub-optical cable, and the association relationship between it and the upper-level optical cable is established based on the parent optical cable identifier, constructing a multi-level tree topology structure. "Parent optical cable identifier" refers to the unique number of the upper-level optical cable to which the sub-optical cable directly branches.

[0097] Secondly, for the main optical cable, the associated optical cable core specification data (such as 48 cores, 96 cores, etc.) in the basic attribute set of its node are read to generate complete core sequence data with unique serial numbers. That is, with the total number of cores N of the main optical cable as the upper limit, a continuous integer sequence from 1 to N is generated, and the unique serial number of each core is this integer. This core sequence serves as the only data source for the sub-optical cable cores to inherit. Sub-optical cables are not allowed to generate new serial numbers outside the range of this sequence, thereby ensuring the uniqueness and traceability of the core numbers across the entire network. For the sub-optical cable, the starting core serial number S and the ending core serial number E of its planned configuration are obtained. Based on the serial number range, logical segmentation is performed from the core sequence of the corresponding parent optical cable or the top-level main optical cable. "Logical segmentation" means that instead of physical disconnection, all cores with serial numbers within the closed interval [S, E] in the core sequence of the parent optical cable are extracted and assigned to the sub-optical cable to generate the core mapping range data of the sub-optical cable.

[0098] Next, inheritance conflict detection is performed on the generated fiber core mapping range data. The calculation method for "cable core inheritance conflict detection" and "cable core inheritance conflict index" is as follows: compare the fiber core mapping ranges of sub-cables of the same level allocated from the same parent optical cable to see if there are overlapping intervals (for example, if sub-cable A is allocated 1-12 cores and sub-cable B is allocated 10-20 cores, then 10-12 cores are an overlapping interval, meaning that the same physical fiber core has been repeatedly allocated); calculate the cable core inheritance conflict index based on the ratio of the number of fiber cores in the overlapping interval to the total number of fiber cores to be allocated (i.e., the total number of fiber cores N of the parent optical cable). The calculation formula is: cable core inheritance conflict index = number of fiber cores in the overlapping interval / total number of fiber cores of the parent optical cable. The cable core inheritance conflict index is not a simple proportional calculation, but is used to quantify the degree of resource contention and configuration discrepancies generated when manually configuring the starting and ending fiber core numbers. The engineering indicators for the level of definition; in actual optical cable distribution and wiring projects, ambiguity in the boundary number configuration often occurs when manually planning the fiber core range of sub-optical cables (e.g., one 12-core cable is configured as 1-12, another 12-core cable is configured as 12-23, and the 12th core overlaps). Such slight overlaps are configuration boundary overlaps rather than large-area resource contention, so it is necessary to perform graded error tolerance processing by comparing the conflict index with the threshold; the preset conflict threshold is set at 5%, which is based on the following: in the optical cable distribution construction specifications, when the number of overlapping fiber cores accounts for less than 5% of the total capacity of the parent optical cable (e.g., less than 4 overlapping cores in a 96-core main optical cable), it is usually due to the overlap of the sequence boundary during manual planning or a minor manual error. Such conflicts can be repaired by automatic truncation and redistribution by the system; if it exceeds 5%, it means that there is a serious physical contention conflict of fiber cores, which cannot be solved by simple correction.

[0099] Based on the above indices and thresholds, the tiered processing logic is executed:

[0100] When the core inheritance conflict index is 0, it means that the core number range of the same level sub-optical cable has no overlap. A valid inheritance identifier is directly generated, and the core number range is bound to the sub-optical cable identifier.

[0101] When the core inheritance conflict index is greater than 0 and less than or equal to 5%, it indicates that there is a slight boundary overlap in the core number range. A valid inheritance identifier is generated, but an automatic correction logic is triggered. That is, the system automatically assigns the cores in the overlapping interval to the sub-optical cable with the earlier sequence number, and removes the overlapping interval from the core mapping range of the sub-optical cable with the later sequence number. The binding is performed according to the actual range after removal. At the same time, a correction log is generated. The format of the correction log is: [timestamp, sub-optical cable identifier, original start sequence number S, original end sequence number E, corrected start sequence number, corrected end sequence number, operation type: automatic correction];

[0102] When the core inheritance conflict index exceeds 5%, it indicates that there is a serious overshoot or large-area overlap in the core number range. A conflict alarm is generated, the core configuration of the sub-optical cable is refused to be saved and the current operation is blocked. The output format of the inheritance conflict alarm is: [alarm time, sub-optical cable identifier, conflict index value, alarm level: severe, alarm content: the core inheritance range overlap exceeds the standard, and there is a serious physical preemption conflict].

[0103] S3: Verify the access capabilities of routing nodes and the mapping of branch fiber cores based on the optical cable topology data, and output the routing data to be verified.

[0104] In this embodiment, S3 verifies the access capability of routing nodes and branch fiber core mapping based on optical cable topology data, and outputs the routing data to be verified, specifically including:

[0105] Based on the standardized set of node objects and optical cable topology data, the selected main line node sequence is extracted, and the main line path data is constructed according to the connection relationship between nodes in the basic attribute set.

[0106] When the node type of the main line tail node or the tail node of the already constructed branch cable is an optical distribution box or connector package, the branch cable branching logic is triggered; the branch cable configuration parameters are obtained, including the number of branch cables, the number of cores in each branch cable, and the first node number;

[0107] Access capability verification is performed by extracting the identifier data from the extended attribute set of the corresponding node object based on the first node number. Specifically, when the first node is an optical distribution box or connector package, the access smoothness identifier in its extended attribute set is identified. If the identifier exists, the first node is determined to have access capability. When the first node is a computer room, the port availability identifier in its extended attribute set is identified. If the identifier exists, the first node is determined to have access capability.

[0108] For each sub-cable that passes verification, logical segmentation is performed based on its core count parameter and the core sequence data of the upper-level optical cable in the optical cable topology data to generate fiber core mapping range data for each sub-cable. The generated fiber core mapping range data is compared with the existing mapping ranges in the same-level sub-cable and optical cable topology data, and core inheritance conflict detection is performed to generate corresponding conflict detection identifiers. Based on the conflict detection identifiers, parent identifiers are assigned to each sub-cable and a sub-cable tree structure is constructed.

[0109] Finally, the main line path data, branch cable relationships, fiber core mapping range data, and conflict detection identifiers are integrated to output the route data to be verified, which includes node connection relationships, branch attributes, and branch cable configuration information. The branch attributes are specifically the branch cable tree structure.

[0110] It should be noted that the specific process of verifying the access capability of routing nodes and mapping branch fiber cores based on the standardized set of node objects and optical cable topology data is as follows:

[0111] "Based on a standardized set of node objects and a hierarchical model of optical cable main branches, combined with the geographic information system (GIS) interface receiving the set of main line nodes selected by the operator and constructing the main line path" refers to the operator selecting several nodes on the GIS interface by clicking or selecting with a box, and connecting the selected nodes in sequence according to the adjacency relationship in the node association table to form a continuous node sequence, which is the main line path; "When the node type of the main line tail node or the tail node of the constructed branch cable is an optical distribution box or a connector package, the branch cable branching logic is triggered" refers to the real-time detection of the last node of the current main line path or a certain constructed branch cable. The last node of the branching path reads the node type field from the basic attribute set of the node object. When the value of the node type field is optical distribution box or splice package, it is determined that the node has branching capability. Optical distribution box refers to an outdoor optical cable distribution box, and splice package refers to a closed package used for optical cable splicing. Both are branch nodes in optical communication networks that allow physical access of lower-level optical cables. "Reading the entered number of branching cables, the number of cores in each branching cable, and the first node information in the branching configuration interface" means that the system automatically pops up the branching configuration interface after triggering the branching logic. The operator enters the number of branching cables K generated by this branching and the number of cores in each branching cable (K) in the interface. The system assigns a unique identifier to each branch cable and the first node identifier. The first node refers to the starting node from which the branch cable physically branches off from the main line or an upstream branch cable. "Firstly, perform a uniqueness check on the number of first node identifiers" means that the system counts the total number of first node identifiers entered. The check passes only if each branch cable corresponds to exactly one first node identifier, i.e., the total number of first node identifiers equals the number of branch cables K. If a branch cable does not specify a first node or specifies multiple first nodes, the check fails and the operator is prompted to correct it. "After the check passes, call the identifier data in the extended attribute set of the first node object for a secondary check of access capability" means using the first node identifier as the search key to locate the first node object from the constructed set of node objects and read the access capability status field stored in its extended attribute set. Specifically, this includes: when the first node is an optical... When delivering a junction box or connector, identify the access availability identifier in its extended attribute set. The access availability identifier is generated in S1 when the port availability coefficient of the node is not lower than the threshold. If the identifier exists, the first node is determined to have access capability. When the first node is a data center, identify the port availability identifier in its extended attribute set. The port availability identifier is generated in S1 when the port availability coefficient of the data center node is not lower than the threshold. If the identifier exists, the first node is determined to have access capability. If no corresponding identifier exists, the port resources of the first node are determined to be close to saturation or overloaded, and branch cable access is prohibited and an access alarm identifier is output. "For each branch cable that passes the verification, logically split it from the cable core sequence of the main line or the upper-level branch cable according to its core count parameter" means that for the k-th branch cable, logically split it according to its core count parameter. To segment the length, continuous segments are extracted from the core sequence of the parent optical cable (i.e., the main line or the upper-level branch cable), using the position of the branch cable's first node within the parent optical cable path as the starting offset. The core serial numbers form the core count range for this sub-cable. , ],in This is the starting fiber core number. To terminate the fiber core sequence number; logical segmentation records the fiber core affiliation at the data level without changing the actual connection status of the physical fiber core; "performing cable core inheritance conflict detection, calculating the cable core inheritance conflict index and determining the conflict ratio" refers to comparing the fiber core mapping ranges of sub-cables allocated from the same parent optical cable to see if there are overlapping intervals (for example, if sub-optical cable A is allocated 1-12 cores and sub-optical cable B is allocated 10-20 cores, then 10-12 cores are an overlapping interval, meaning that the same physical fiber core has been repeatedly allocated to two sub-optical cables); based on the number of fiber cores in the overlapping interval and the number to be allocated. The core inheritance conflict index is calculated as the ratio of the total number of fiber cores (i.e., the total number of fiber cores N in the parent optical cable). The calculation formula is: Core inheritance conflict index = Number of fiber cores in the overlapping area / Total number of fiber cores in the parent optical cable; "Processing according to the preset conflict ratio threshold" means performing three levels of processing based on the conflict ratio threshold of 5% set in S2: When the core inheritance conflict index is 0, it indicates no overlap, and the core number range is directly bound to the sub-cable identifier; when the core inheritance conflict index is greater than 0 and less than or equal to 5%, it indicates that there is slight boundary overlap in the core number range (belonging to the edge when manually configuring the sequence number). When the fiber cores in the overlapping area overlap, an automatic correction logic is triggered. This means the system automatically prioritizes assigning the overlapping fiber cores to the sub-cable with the earlier sequence number and removes the overlapping area from the fiber core mapping range of the sub-cable with the later sequence number. The overlapping area is then bound according to the actual range after removal, and a correction log is generated. When the fiber core inheritance conflict index exceeds 5%, it indicates a serious large-area overlap in the number of cores. The sub-cable configuration is refused to be saved, and an inheritance conflict alarm is output. "Assigning parent identifiers to each sub-cable and constructing a sub-cable tree structure" refers to recording the parent optical cable identifier (i.e., the main line identifier or upper-level identifier) ​​for each sub-cable after the grading process is completed. The sub-cable identifier is recorded, and the top-level main optical cable identifier is also recorded, thus forming a multi-level tree topology structure, i.e., the sub-cable tree structure, with the main line as the root node and each sub-cable as a child node. The sub-cable tree structure is a directed acyclic graph data structure, in which nodes store optical cable identifiers and edges store hierarchical relationships and fiber core mapping ranges; "integrating the main line path, sub-cable branch relationships, core number mapping range, and access capability status of each node" means that the system integrates the node sequence of the main line path, the parent-child branch relationships between each sub-cable and the main line or upper-level sub-cable, and the fiber core mapping range of each sub-cable, i.e., the corrected core number interval. , The data is summarized and encapsulated, including the access capability status of each node, i.e., the access smoothness indicator or the port availability indicator. "Outputting verification route data containing node connection relationships, branch attributes and sub-cable configuration information" means that the final output verification route data is a structured data object. This data object contains the following fields: main line node connection sequence, sub-cable branch hierarchy relationship table, fiber core mapping range of each sub-cable, parent identifier and top-level main optical cable identifier of each sub-cable, and access capability status field of the first node of each sub-cable. This verification route data will be used as input for the subsequent S4 route verification steps to verify whether the physical connectivity and resource availability of the entire optical cable path are simultaneously satisfied.

[0112] S4: Based on the optical cable topology data and the routing data to be verified, constrain the fiber core capacity margin and verify the port capacity, and output the verified routing data.

[0113] In this embodiment, step S4 constrains the fiber core capacity margin and verifies the port capacity based on the optical cable topology data and the routing data to be verified, and outputs the verified routing data, specifically including:

[0114] Based on the cable tree structure in the routing data to be verified and the hierarchical inheritance relationship in the optical cable topology data, the fiber core mapping range data of each level of cable is extracted from top to bottom to calculate the allocated fiber core quantity. Combined with the fiber core specification data of the associated optical cable of the node to which the parent optical cable belongs in the standardized node object set, the remaining allocable fiber core quantity is calculated. When the core number parameter of the cable to be verified is greater than the remaining allocable fiber core quantity of its parent optical cable, a fiber core capacity over-limit flag is generated.

[0115] Simultaneously, based on the routing data to be verified, the target nodes traversed by the main line and branch cables are extracted. Based on the number of cores in each branch cable in the branch cable configuration information and the preset fiber core port mapping rules, the new port demand of each target node is calculated. Combined with the number of occupied ports in the corresponding node extended attribute set in the standardized node object set, the total port demand is calculated. The total port demand is compared with the total number of physical ports of the corresponding node. When the total port demand is greater than the total number of physical ports, a port capacity conflict identifier is generated and the corresponding node number is associated with it and output.

[0116] When no fiber core capacity over-limit flag or port capacity conflict flag is generated, the routing data to be verified is marked as valid for verification, and a pre-occupancy lock operation is performed on the new port requirements involved in the verification, and the verified routing data is output; otherwise, verification abnormal data containing the corresponding conflict flag is output.

[0117] It should be noted that the specific process of performing fiber core capacity margin constraints and port capacity verification based on optical cable topology data and routing data to be verified is as follows:

[0118] First, the cable tree structure in the routing data to be verified is read. The cable tree structure refers to the multi-level tree data structure constructed in S3 after assigning parent identifiers to each cable. It records the parent identifier, core count parameters, and the core count interval formed by the starting and ending fiber core numbers for each cable. Simultaneously, the hierarchical inheritance relationship in the optical cable topology data is read. The hierarchical inheritance relationship refers to the multi-level parent-child relationship between the main optical cable and child optical cables contained in the optical cable topology data output by S2. The system traverses the cable tree structure layer by layer from top to bottom, starting from the top-level main optical cable and traversing its direct child optical cables, then traversing the child optical cables' child optical cables, ensuring that the capacity verification of the upper-level optical cable takes precedence over the lower-level optical cable. For each parent optical cable, the core count intervals of all its child cables are summed to obtain the total allocated core count of that parent optical cable. The total allocated core count refers to the sum of the number of fiber cores occupied by all existing child cables under that parent optical cable, expressed by the formula: Total allocated core count = Where m is the number of child cables already connected to the parent optical cable. Let be the termination fiber core number of the i-th sub-cable. The starting fiber core number of the i-th sub-cable is used; then, the remaining allocable cores of the parent optical cable are calculated. The remaining allocable cores are the difference between the total number of fiber cores of the parent optical cable and the sum of the allocated cores, expressed by the formula: Remaining allocable cores = Total number of fiber cores of the parent optical cable - Sum of the allocated cores. The total number of fiber cores of the parent optical cable comes from the associated optical cable fiber core specification data (such as 48 cores, 96 cores, etc.) in the basic attribute set of the node to which the parent optical cable belongs in the standardized node object set, representing the maximum fiber core capacity limit of the physical laying of the optical cable; when the total number of cores of the sub-cable to be verified, that is, the number of fiber cores obtained by subtracting the starting fiber core number plus 1 from the ending fiber core number of the sub-cable, is greater than the remaining allocable cores of its parent optical cable, it is judged as a fiber core capacity over-limit (i.e., cable core inheritance conflict), a fiber core capacity over-limit flag is generated and submission is prohibited; at the same time, the target nodes traversed by the main line and the sub-cable branches are extracted based on the route data to be verified. Target nodes refer to physical access nodes along the optical cable path whose node type is optical distribution box, splice package, or equipment room. Wells and bends do not involve port termination and are therefore not considered target nodes for port capacity verification. The new port demand for each target node is calculated based on the number of cores in the branch cable configuration information and the preset fiber core port mapping rules. The preset fiber core port mapping rules state that, in the optical communication physical connection specification, a single fiber core accessing a node must be terminated at an independent physical port (adapter or flange). Therefore, the fiber core to port follows a one-to-one mapping principle, meaning a single core demand is mapped to a single port demand. The new port demand is numerically equal to the number of branch cable cores accessing that node. The total port demand is calculated by combining the number of occupied ports in the corresponding node extended attribute set in the standardized node object set, expressed by the formula: Total port demand = Number of occupied ports in the node's extended attribute set. The system adds port requirements; it compares the total port requirement with the total number of physical ports of the corresponding node. When the total port requirement exceeds the total number of physical ports, a port capacity conflict flag is generated and associated with the corresponding node number. This determines whether the remaining available ports of the node (the difference between the total number of physical ports and the number of occupied ports) are sufficient to support the current cable splitting access. When no fiber core capacity over-limit flag or port capacity conflict flag is generated, the route data to be verified is marked as valid, and a pre-occupancy locking operation is performed on the added port requirements involved in the verification. The pre-occupancy locking operation means temporarily increasing the number of occupied ports recorded in the extended attribute set of each target node in memory or cache by the added port requirements, and marking these ports as "pre-occupied". This prevents other concurrent operations from repeatedly allocating these ports to other optical cable paths before the current path is officially saved into the database, thereby ensuring data consistency and transaction isolation. The system outputs the verified route data; otherwise, it outputs verification exception data containing the corresponding conflict flag.

[0119] S5: Identify data center type nodes based on verified routing data and bind access device resources, then output path node data.

[0120] In this embodiment, step S5 identifies data center type nodes based on verified routing data and binds access device resources, then outputs path node data, specifically including:

[0121] Traverse the node sequence in the verified routing data. When the node type is identified as a data center, extract the identification data from the extended attribute set of the node object to determine the access status: if there is a port overload indicator, generate a resource shortage alarm indicator; if there is a port available indicator, trigger the resource binding logic.

[0122] Based on the ODF identifier and bidirectional index mapping relationship recorded in the extended attribute set of the data center node, the corresponding available ODF device data is retrieved; the selected target ODF identifier is obtained, the resource name and data center resource type corresponding to the target ODF are extracted, and the target ODF identifier, resource name and data center resource type are updated and written into the extended attribute set of the data center node object to complete the mapping and binding from the geographic coordinate node to the physical access resource.

[0123] The node data that has been bound to the resource is integrated with the verified route data to output the path node data.

[0124] It should be noted that the selection of data center resources is performed based on the standardized set of node objects output by S1. The specific process is as follows:

[0125] The system iterates through the path nodes in the verified routing data saved after S4 verification, and performs type matching based on the node type field in the node object's basic attribute set. When the node type field is identified as "data center," it means that the node is a data center node in S1 for which the data center resource type, ODF identifier, switch identifier, rack identifier, resource name, and rack name have been written into the extended attribute set and the port availability coefficient has been calculated. First, the system extracts the identifier data from the node object's extended attribute set to determine the access status: if there is a port overload identifier in the extended attribute set, it indicates that the port availability coefficient calculated for this data center node in S1 is lower than the preset availability threshold, and the remaining available ports are... If the system cannot support new fiber optic cable access, it generates a resource shortage alarm and prohibits access. If a port availability identifier exists in the extended attribute set, it indicates that the port availability coefficient of the data center node is not lower than the preset availability threshold, and it currently has access capability, triggering resource binding logic. Based on the ODF identifiers and bidirectional index mapping relationships recorded in the extended attribute set of the data center node, the system retrieves the corresponding available ODF device data. The bidirectional index mapping relationship refers to the forward and reverse indexes between the node number and the physical resource identifier established in S1. Specifically, the system uses the forward index, with the node number of the data center node as the search key, to locate the set of all ODF device identifiers attached to the data center node. Subsequently, the data center resource query interface is invoked to retrieve real-time port status data of these ODF devices from the resource management system. Available ODF device data refers to: based on the comparison between the current port occupancy of each ODF device in the resource management system and a preset occupancy threshold (e.g., 80%), ODF devices whose current port occupancy does not exceed the preset threshold, i.e., those in a non-resource-scarce state, are selected and aggregated to form a set of available ODF devices. Obtaining the selected target ODF identifier means that the operator selects one of the available ODF devices from the list of available ODF devices displayed in the geographic information system interface as the path for that optical cable. Indoor access physical entry point; extract the resource name and data center resource type corresponding to the target ODF, update the target ODF identifier, resource name, and data center resource type into the bound resource identifier field of the extended attribute set of the data center node object, and complete the mapping and binding from the geographic coordinate node to the physical access resource. The mapping and binding upgrades the data center spatial node in the map, which originally only represents latitude and longitude coordinates, into a complete resource node containing the selected indoor access resource entry point, realizing the linkage and association between outdoor optical cable routing and indoor physical equipment; integrate the node data with the verified routing data to output path node data containing the binding relationship between node spatial coordinates and indoor access resources.

[0126] S6: Based on the verified routing data, parse the spatial distance between nodes and calculate the line length, then output the main and branch optical cable storage data.

[0127] In this embodiment, step S6 parses the spatial distance between nodes based on the verified routing data and calculates the line length, then outputs the main and branch optical cable storage data, specifically including:

[0128] Extract the node sequence based on the verified routing data, and read the latitude and longitude or spatial coordinates from the basic attribute set of the standardized node object set. Calculate the geographical distance between adjacent nodes and accumulate them to obtain the physical length of the line. Update the verified routing data with the physical length of the line as the standard length data.

[0129] Perform the main and branch optical cable saving operation, generate the main optical cable code and cable core code for the main optical cable, and write the main optical cable code and cable core code into the node association table according to the node order; for the sub-optical cable, extract the parent identifier of the sub-cable tree structure and the fiber core mapping range data from the verified routing data, generate the sub-optical cable exclusive cable core code based on the cable core code and fiber core mapping range of the parent optical cable, and bind the fiber core mapping range data to the sub-optical cable path;

[0130] Finally, the main optical cable code, cable core code, node sequence, line physical length and fiber core mapping range data are integrated to output the main and branch optical cable storage data.

[0131] It should be noted that S6 performs line length calculation and main / branch optical cable storage based on the verified routing data after S4 verification and the standardized node object set output by S1. The specific process is as follows:

[0132] First, the optical cable node sequence in the verified routing data is sequentially arranged. This sequential arrangement refers to arranging the nodes on the path in the topological order from the starting point to the end point, based on the main route path and branch cable tree structure constructed in S3. This ensures that the cumulative direction of subsequent geographical distance calculations is consistent with the actual physical laying direction of the optical cable. Then, based on the latitude and longitude coordinates in the node object's basic attribute set, the geographical distance between adjacent nodes is calculated using either the spherical distance formula (suitable for long-distance cross-regional calculations) or the planar projection distance formula (suitable for short-distance calculations within the park), depending on the span between nodes. Finally, the geographical distances between all adjacent nodes are summed to obtain the physical length of the line. Since the displayed length input at the front end is manually entered by the operator, it may deviate from the actual spatial distance of the node. To ensure the accuracy of the line length in the resource ledger, the calculated result of the physical length of the line will be used to cover the displayed length input at the front end. Then, the main optical cable saving operation is performed. When saving the main optical cable, a unique main optical cable code and the cable core code of each cable core under the main optical cable are automatically generated. The main optical cable code is used to uniquely identify the number of the main optical cable. Its generation rule can adopt the combination of "regional code + optical cable specification + serial number" to ensure global uniqueness. The cable core code is based on the uniqueness of each cable core in the complete cable core sequence generated for the main optical cable in S2. The serial number is generated in association with the main optical cable code, specifically in the format "main optical cable code - fiber core serial number" (e.g., Cable01-1 to Cable01-48), thus achieving fine-grained identification at the single fiber core level. The main optical cable code, fiber core code, and node serial number are written into the S2 node association table in node order. The writing operation establishes a many-to-many mapping relationship between the optical cable identifier, fiber core identifier, and the identifiers of each node traversed by the path in the node association table, recording the topological position of each node in the optical cable path. When saving sub-optical cables, the parent allocation rules recorded in the sub-cable tree structure constructed in S3 are used. The parent allocation rules refer to the sub-optical cables defined in S2 that are assigned to the parent optical cable. Alternatively, the core sequence of the top-level main optical cable is logically divided according to the starting and ending fiber core numbers. The resulting core subset, i.e., the core range corresponding to the starting and ending fiber core numbers, is bound to the path node of the sub-optical cable and written into the node association table. At the same time, a sub-optical cable core code is generated based on the core code and fiber core mapping range of the parent optical cable. The generation rule of the sub-optical cable core code is to inherit the parent optical cable code and add a branch identifier, such as "parent optical cable code - branch number", and record the parent fiber core number range it occupies. This indicates that the sub-optical cable core is not generated independently, but is a logical occupation and inheritance of the physical core of the parent optical cable.Finally, the main optical cable code, core code, node sequence, line physical length, and fiber core mapping range data are integrated to output the main branch optical cable storage data. This constructs the main branch optical cable storage data, which includes the main optical cable code, core code, node sequence, and main branch core number allocation chain. The main branch core number allocation chain refers to the complete record chain of the core inheritance relationship from the top-level main optical cable to each level of sub-optical cable. Its data structure is a tree structure. The root node records the complete fiber core sequence of the top-level main optical cable, and each child node records the fiber core mapping range and exclusive core code of the corresponding sub-optical cable cut from the parent node. This allocation chain completely maps the fiber core splitting topology of the physical optical cable from the trunk to the branches, supporting the subsequent S9 step of tracing the complete physical ownership of a single core along the link.

[0133] S7: Identify node types and bind port resources based on the main and branch optical cable storage data and path node data, and output resource service data.

[0134] In this embodiment, step S7 identifies node types and binds port resources based on the main and branch optical cable storage data and path node data, and outputs resource service data, specifically including:

[0135] Based on the node order in the main optical cable storage data, the corresponding nodes are extracted, and the node type is matched, located, and identified in the standardized node object set.

[0136] When the node type is an optical distribution box or connector package, the total number of physical ports, the number of occupied ports, and the number of shared ports in the node's extended attribute set are extracted to perform port allocation: priority is given to allocating shared ports that support multiple service reuse from the occupied ports, and any shortfall is made up from the remaining available physical ports in sequence; based on the allocation result, the corresponding cable core code is bound to the port identifier to generate a service resource binding record, the number of occupied ports in the node's extended attribute set is increased and updated; when the remaining available physical ports cannot meet the demand, a port resource shortage alarm is generated;

[0137] When the node type is a data center, extract the target ODF identifier that has been bound in the extended attribute set of the node and allocate the ODF port to the corresponding cable core code. At the same time, based on the switch identifier and cabinet identifier in the extended attribute set, establish the mapping relationship from the cable core code to the switch port via the ODF port and generate a service resource binding record that includes the mapping of equipment in the data center.

[0138] When the node type is a well or a turning point, extract the path constraint weights from the node's extended attribute set and write them into the business resource binding record as routing scheduling parameters.

[0139] Finally, the business resource binding records of all nodes are integrated, and the main optical cable code, cable core code, node order, line physical length and fiber core mapping range data in the main and branch optical cable storage data are combined to output resource business data.

[0140] It needs to be specifically explained that the port resource matching and binding process based on the main branch optical cable storage data output by S6 and the path node data output by S5 is as follows: The main branch optical cable storage data is a data set constructed by S6 that includes the main optical cable code, cable core code, node order, and main branch core number allocation chain. The path node data is a data set output by S5 that includes the binding relationship between node spatial coordinates and indoor access resources. The node order refers to the list of node numbers arranged sequentially from the start to the end of the optical cable path in S6. The node order recorded in the main branch optical cable storage data is traversed, and each node is matched and located according to the node identifier in the path node data, i.e., the node number in the basic attribute set, and the node type is identified according to the node type field. When the node type is an optical distribution box or connector package, the total number of physical ports and the number of occupied ports written in the extended attribute set of the path node data are extracted. The occupied ports refer to the physical ports of the node that are currently used by other optical cable path terminations. The port reuse logic is executed: first, allocation is performed from the ports that are occupied by the node and have the conditions for sharing. The sharing condition is to support multiple service reuse and the remaining available cores meet the current allocation requirements. Specifically, supporting multiple service reuse means that the physical port can carry multiple optical path services with different wavelengths or time slots at the same time through wavelength division multiplexing or time division multiplexing technology. The sharing condition means that the port is in the same route direction as this optical cable and there is an idle time slot. That is, the port must meet the following conditions at the same time: (1) The port is not marked as "exclusive binding"; (2) The remaining available cores of the port are ≥ the cores required for the cable splitting; (3) The priority of the service currently carried by the port is lower than the priority of the service to be allocated; the insufficient part is supplemented from the available ports in ascending order of port number until the core number requirement is met. The status field of the used port is set to occupied and a service resource binding record of core number to port is established. The service resource binding record is a one-to-one correspondence data pair between each cable core code and the specific physical port number. When the total number of available ports and occupied ports with sharing conditions is still insufficient to meet the core number requirement, a port resource shortage alarm is generated and the subsequent port allocation operation of the node is stopped.When the node type is a data center, the target ODF identifier, data center resource type, and resource name bound to S5 are extracted from the path node data. Based on the target ODF identifier bound to S5, a specific ODF port number is assigned to the corresponding cable core code (i.e., the unique serial number automatically generated by S6 for each cable core) from the ODF device. Furthermore, the switch port identifier, rack identifier, and data center switching equipment information written into the extended attribute set of this node are extracted in conjunction with the data center extended attribute set. The data center switching equipment information refers to the name, port number, and VLAN configuration of the switch equipment connected to this ODF port through internal jumper fiber. Information is used to establish a complete port-level mapping relationship from the cable core code via the ODF port to the switch port. This complete port-level mapping relationship is a three-level binding link where one cable core corresponds to one ODF port and then to one switch port. This link records the complete physical jumper path from the optical port of the optical distribution frame (ODF) to the electrical port of the switch after the outdoor optical cable signal enters the equipment room, thus forming a service resource binding record that includes the mapping of equipment within the equipment room. When the node type is a manhole or a bend, the path constraint weights written in the extended attribute set of the path node data are extracted. These path constraint weights are based on the node... The weight value converted from the position number in the optical cable path topology represents the constraint of the node in the topology. The higher the weight, the stronger the constraint and the less bypassable it is. This constraint weight is written into the service resource binding record as a routing scheduling parameter. The routing scheduling parameter is the numerical basis used to evaluate path cost and calculate the optimal path weight in subsequent network topology calculation and service routing scheduling. After all nodes are bound, the port records (i.e., the occupancy status of each port in the port resource table), the cable core records (i.e., the binding status of each cable core in the cable core sequence), the node status (i.e., the resource shortage or normal resource marking in the extended attribute set), and the equipment status (i.e., the occupancy level of the equipment room port and the occupancy level of the optical distribution box port) are updated synchronously. Finally, the service resource binding records of all nodes and the physical length of the line and the node order calculated by S6 are integrated to output resource service data containing optical cable code, cable core code, node identifier, node order, physical length of line, ODF port mapping relationship, switch port mapping relationship, port occupancy status, and routing scheduling parameters. The resource service data refers to a complete resource binding dataset that can directly support service activation and resource scheduling, which establishes a closed-loop association between the outdoor geographical topology path and the physical status of indoor equipment ports.

[0141] S8: Respond to path modification requests, identify and classify structural change types based on resource business data, and output updated resource business data.

[0142] In this embodiment, the S8 response path modification request identifies and classifies the structural change type based on resource service data, and outputs updated resource service data, specifically including:

[0143] By comparing the changed data in the path modification request with the resource business data and the standardized node object set item by item, three types of structural changes were identified:

[0144] When only the latitude, longitude, or address information in the basic attribute set of the standardized node object set changes, and the cable branching relationship in the resource business data remains unchanged, it is determined to be a basic attribute level change; the corresponding fields in the basic attribute set are updated, and the physical length of the line is recalculated based on the updated latitude and longitude to update the resource business data;

[0145] When a non-critical access node is added or deleted, or the order of path nodes changes, but the set of critical node identifiers at the beginning and end points is not added or deleted, and the ODF port mapping relationship and switch port mapping relationship in the resource service data remain unchanged, it is determined to be a path node-level change. The physical length of the line is recalculated based on the updated node order and the spatial coordinates in the basic attribute set of the standardized node object set and updated to the resource service data. At the same time, the path must-pass constraint weights in the extended attribute set of the associated nodes under this path are recalculated and updated. The path node relationship and routing scheduling parameters in the resource service data are incrementally synchronized.

[0146] When the branch cable relationship, ODF port mapping relationship, or switch port mapping relationship in the resource service data changes, it is determined to be a change at the main branch structure level. First, release all port binding relationships under the main optical cable tree according to the resource service data, and reduce and update the number of occupied ports in the corresponding node extended attribute set. Then, recursively delete the association records and old binding data of all sub-optical cables under the main optical cable tree according to the node association table. Then, re-execute steps S4 to S7 according to the modified path to generate new resource service data, and finally output the updated resource service data.

[0147] It should be noted that the structural change identification and classification process is performed based on the resource business data output by S7 and the received path modification requests. The specific process is as follows:

[0148] Resource service data is a set of data output by S7 that includes fiber optic cable codes, cable core codes, node identifiers, node order, line physical length, ODF port mapping relationships, switch port mapping relationships, port occupancy status, and routing scheduling parameters. Path modification requests are commands initiated by operators through the geographic information system (GIS) interface to edit attributes, add or delete nodes, or adjust branches of a saved fiber optic cable path. The system compares the fields involved in the modification request with the resource service data and the standardized node object set item by item. This item-by-item comparison means using the current value of each field in the resource service data and node object set as a benchmark, and performing an equal-value comparison with the target value of the corresponding field in the modification request to identify the specific location and scope of the change, thus identifying three types of structural changes:

[0149] When only the latitude, longitude, or address information in the basic attribute set of the standardized node object set changes, and the cable branching relationship in the resource service data remains unchanged, it is determined to be a basic attribute-level change. A basic attribute-level change refers to a change in the spatial location description, where the logical topology and physical resource occupancy status of the optical cable remain unchanged. In this case, the corresponding changed field values ​​in the basic attribute set are updated, and the physical length of the line is recalculated based on the updated latitude and longitude to update the physical length of the line in the resource service data. When the addition or deletion of non-critical access nodes or the order of path nodes changes, but the set of key node identifiers at the beginning and end points does not change, and the ODF port mapping relationship and switch port mapping relationship in the resource service data remain unchanged, it is determined to be a change at the basic attribute level. For path node-level changes, non-critical access nodes refer to physical routing nodes such as manholes or bends that do not involve port resource termination and binding; the set of critical node identifiers at the beginning and end of the optical cable path refers to the set of core access nodes at the start and end points of the optical cable path, with node types such as equipment rooms, optical distribution boxes, or connector packages that involve port resource occupation; path node-level changes refer to modifications where the intermediate routes traversed by the optical cable are adjusted, but the starting and ending resource entry points and the overall branch structure remain unchanged; in this case, the geographical distance between adjacent nodes is recalculated based on the updated node order and the spatial coordinates in the basic attribute set of the standardized node object set, and the new line physical length is obtained by summing them, thereby updating the line physical length in the resource service data; at the same time, due to the change in node position sequence, the path is recalculated. The path constraint weights of the associated nodes in the extended attribute set are updated, and incremental synchronization is performed on the path node relationships and routing scheduling parameters in the resource service data. Incremental synchronization means that only the parameters associated with nodes whose positions have changed are partially replaced and updated, while the unchanged port mapping and other resource binding data remain unchanged. When the branch cable relationship, ODF port mapping relationship, or switch port mapping relationship in the resource service data changes, it is determined to be a main branch structure-level change. A main branch structure-level change refers to the splitting and merging of the main branch layer topology of the optical cable, or a deep modification involving a substantial transfer of the port occupancy status of key nodes such as equipment rooms and optical distribution boxes. At this time, all port binding relationships under the main optical cable tree are released first according to the resource service data. The process of releasing port binding relationships involves removing the correspondence between cable core codes and port identifiers established in S7, restoring the status of the physical ports involved from occupied to idle, and updating the number of occupied ports in the corresponding node's extended attribute set. This update involves subtracting the number of ports released from the number of occupied ports to restore the node's actual remaining available capacity. Then, based on the node association table, the process recursively deletes the association records and old binding data of all sub-optical cables under the main optical cable tree. This recursive deletion involves deleting the node association records and binding data level by level from the last-level sub-optical cable along the tree topology hierarchy from the main optical cable to the sub-optical cable, until all optical cable records at all levels under the main optical cable tree have been cleared to avoid leaving isolated data.Then, based on the modified path, steps S4 to S7 are re-executed to generate new resource service data, and finally, the updated resource service data is output.

[0150] S9: Obtain the target cable core identifier, construct the cable core path chain based on the main and branch optical cable storage data and updated resource service data, associate it with the port binding context, and output the cable core level traceability information.

[0151] In this embodiment, step S9 obtains the target cable core identifier, constructs a cable core path chain based on the main and branch optical cable storage data and updated resource service data, associates it with the port binding context, and outputs cable core-level traceability information, specifically including:

[0152] Based on the target cable core identifier and the fiber core mapping range data and sub-cable tree structure in the main branch optical cable storage data, the cable core path chain is constructed from the top main optical cable to the top main optical cable identifier by tracing back along the parent identifier in the sub-cable tree structure through each level of sub-optical cable to the target cable core.

[0153] Extract the node sequence of each level of optical cable record on the cable core path chain, trim and remove duplicate node sequences where the first node of the branch is the same in two adjacent optical cables, and merge them in topological order to generate the complete node sequence of the target cable core.

[0154] Based on the node identifiers in the complete sequence of nodes, extract the service resource binding records of the corresponding nodes from the updated resource service data; for optical distribution box or connector packet nodes, extract the binding relationship between cable core codes and port identifiers; for equipment room nodes, extract the mapping relationship between cable core codes via ODF ports to switch ports; and form the port binding context of the target cable core by concatenating the nodes in sequence.

[0155] Simultaneously, the target ODF identifier, resource name, data center resource type, switch identifier, and cabinet identifier are attached to the data center nodes in the complete traversed node sequence as extended attributes. Finally, the target cable core identifier, the complete traversed node sequence, port binding context, and additional device identifier information are integrated to output cable core-level traceability information.

[0156] It should be noted that the process of obtaining the target cable core identifier, constructing the cable core path chain based on the main and branch optical cable storage data and the updated resource service data, as well as associating it with the port binding context, and outputting cable core-level traceability information is as follows:

[0157] The target cable core identifier is a query condition input by the operator through the geographic information system interface or automatically generated by the system. Essentially, it is the cable core code automatically generated when the main optical cable is stored in S6 of the main branch optical cable storage data; this is the unique serial number assigned to each cable core. After receiving the target cable core identifier, the system first traces back level by level to the top-level main optical cable identifier based on the fiber core mapping range data and the sub-cable tree structure in the main branch optical cable storage data. The specific process of tracing back level by level is as follows: First, the starting and ending fiber core serial numbers corresponding to the cable core code are read from the fiber core mapping range data of the main branch optical cable storage data. The sub-optical cable identifier to which this core range belongs is determined as the directly belonging sub-optical cable of this cable core. Then, the sub-optical cable identifier is used as the query... The query key is used to read the parent identifier in the sub-cable tree structure. This parent identifier is then used as the new query key to continue reading the next higher-level parent identifier. This process is repeated until the root node without a parent identifier, i.e., the top-level main optical cable identifier, is reached. This constructs a cable core path chain from the top-level main optical cable through each level of sub-optical cables to the target cable core. The cable core path chain is a sequence of optical cable identifiers linked in a hierarchical manner, recording the order of the physical carriers of the optical cable that the cable core traverses from the top-level trunk to the terminal branch. Subsequently, the node order recorded in the main branch optical cable storage data for each level of optical cable in the cable core path chain is extracted, i.e., a list of node numbers arranged according to the path direction for each optical cable. Node sequences with overlapping branch first nodes in adjacent levels of optical cables are pruned to remove duplicates. Overlapping branch first nodes refer to... Because the sub-optical cable branches off from a physical node of the parent optical cable, this branching node, as the tail node of the parent optical cable, is physically the same node as the head node of the sub-optical cable. Deduplication refers to retaining the shared starting node only once when merging node sequences, removing duplicate nodes caused by hierarchical records, and merging them according to topological order to generate a complete sequence of nodes traversed by the target cable core. Topological order refers to the physical connection direction from the head node of the top-level main optical cable to the tail node of the target sub-optical cable. The complete sequence of nodes traversed refers to a non-repeating list of all physical nodes traversed by the cable core from its starting point to its end point, arranged in chronological order. Based on the node identifiers in this complete sequence of nodes traversed, the corresponding service resource binding records are extracted from the updated resource service data. This process is applied to optical distribution boxes or... For connector packet nodes, the binding relationship between cable core codes and port identifiers is extracted. This binding relationship is a one-to-one correspondence between each cable core and a specific physical port number on the optical distribution box or connector packet. For equipment room nodes, the mapping relationship between cable core codes and switch ports via ODF ports is extracted. This mapping relationship is a three-level binding link where one cable core first corresponds to one ODF port number, and then via an internal patch cord in the equipment room, it corresponds to one switch port number. This link completely describes the physical path of the optical signal from the outdoor optical cable into the equipment room, through the optical distribution frame, and finally to the switch equipment. The port binding context of the target cable core is formed by connecting the nodes sequentially. The port binding context refers to the ordered set formed by connecting the resource occupancy of the cable core at each node according to its physical direction.Simultaneously, the system adds the target ODF identifier, resource name, data center resource type, switch identifier, and cabinet identifier already bound to the data center nodes in the complete traversal node sequence. Finally, it integrates the target cable core identifier, the complete traversal node sequence, port binding context, and additional device identifier information to output cable core-level traceability information. This cable core-level traceability information is a complete data record that directly supports maintenance personnel in locating the physical path and resource occupancy of the cable core, achieving end-to-end visual traceability from geographical topology to physical device ports.

[0158] Example 1:

[0159] In a campus optical cable management system, master data is pre-maintained, including data center nodes, optical distribution box nodes, connector packet nodes, ODF devices, cabinets, and switches, and the latitude, longitude, address, and region of each node are recorded. The system establishes a unified node model containing basic attribute sets and extended attribute sets for different node types. Basic attributes encapsulate node number, node type, latitude and longitude, etc., while extended attributes are used to store bound resource identifiers and port status information.

[0160] During implementation, the system acquires information about optical communication network nodes and performs differentiated attribute calculations. For equipment rooms A and E, the system retrieves their total number of ODF ports and total number of used ports, calculates the port availability coefficient, generates a port availability identifier, and writes it into the extended attribute set. Simultaneously, it generates a bidirectional index mapping relationship between node numbers and physical resource identifiers. For optical distribution boxes C and G, connector packets D and F, the system retrieves their total number of physical ports and number of occupied ports, calculates the port availability coefficient, generates an access connectivity identifier, and writes it into the extended attribute set. For manhole B, the system calculates the sequence position weight and spatial span weight based on its position in the path, fuses them to obtain the path necessity constraint weight, and writes it into the extended attribute set, thereby outputting a standardized set of node objects.

[0161] Subsequently, the maintenance personnel added a new 48-core main optical cable, selecting equipment room A, conduit B, optical distribution box C, connector package D, and equipment room E as the main line nodes on the map. The system identified this path as the main optical cable and generated complete cable core sequence data. When the main line reached optical distribution box C, the maintenance personnel triggered the branching logic, configuring two branch cables with this node as the starting point: the first branch cable was allocated 12 cores, with connector package F as the first node; the second branch cable was allocated 8 cores, with optical distribution box G as the first node. The system extracted the access connectivity identifier of the corresponding node based on the first node number, determined that it had access capability, and then logically segmented the cable based on the core number parameter and the main optical cable core sequence, generating fiber core mapping range data for each branch cable and constructing a branch cable tree structure, outputting the route data to be verified.

[0162] Next, fiber core capacity margin constraints and port capacity verification are performed based on the routing data to be verified. The system calculates the remaining allocable fiber cores of the parent optical cable from top to bottom, verifying that 12+8 does not exceed 48; at the same time, it calculates the new port demand and total port demand of each target node based on the number of cores in the sub-cable, compares it with the total number of physical ports, and after confirming that there are no fiber core capacity over-limit indicators or port capacity conflict indicators, the routing data to be verified is marked as valid for verification and a pre-occupancy locking operation is performed, and the verified routing data is output.

[0163] After successful verification, the system iterates through the verified routing data, identifies data center A and data center E as data center type nodes with available ports, and triggers resource binding logic. The system retrieves the corresponding available ODF device data based on a bidirectional index mapping relationship. The operations and maintenance personnel select the target ODF, and the system updates the target ODF identifier, resource name, and data center resource type into the extended attribute set of the data center node object, completing the mapping and binding from the geographic coordinate node to the physical access resource, and outputting the path node data.

[0164] Subsequently, based on the verified routing data, the node sequence is extracted, the latitude and longitude are read to calculate the geographical distance between adjacent nodes, and the sum is used to obtain the physical length of the line, covering the display length input from the front end. The main and branch optical cables are saved, generating a main optical cable code and 48 cable core codes for the main optical cable, and writing them into the node association table. For the sub-optical cables, a unique cable core code for the sub-optical cable is generated based on the cable core code and fiber core mapping range of the parent optical cable. The fiber core mapping range data is bound to the sub-optical cable path, and the main and branch optical cable storage data is output.

[0165] Furthermore, based on the main and branch optical cable storage data and path node data, the system identifies node types and performs port resource matching and binding. For optical distribution box C and connector package F and optical distribution box G, the system prioritizes allocating shared ports that support multiple services from the occupied ports. If insufficient, it sequentially supplements the remaining available physical ports, establishes a service resource binding record between cable core codes and port identifiers, and increases the number of occupied ports. For equipment rooms A and E, the system allocates ODF ports to the corresponding cable core codes based on the bound target ODF identifiers, and extracts switch port identifiers and cabinet identifiers in conjunction with the system to establish a mapping relationship from cable core codes to switch ports via ODF ports. For manhole B, the system extracts its path constraint weights as routing scheduling parameters and writes them into the service resource binding record, and finally integrates and outputs resource service data.

[0166] During subsequent operation and maintenance, if it is necessary to view the specific path of the 5th core, after receiving the target cable core identifier of the 5th core, the system traces back to the top-level main cable identifier level by level along the parent identifier based on the fiber core mapping range data and the branch cable tree structure in the main branch optical cable storage data, constructing a cable core path chain. The system extracts the node sequence of each level of optical cable record on this path chain, trims and removes duplicate node sequences with overlapping branch first nodes in adjacent optical cables, and merges them according to the topological order to generate a complete sequence of traversed nodes, namely "equipment room A - conduit B - optical distribution box C - connector package F - subsequent nodes". Based on this sequence, the system extracts the binding records of the corresponding nodes from the resource service data, extracts the binding relationship between cable core codes and port identifiers for optical distribution boxes and connector packages, and extracts the mapping relationship from cable core codes through ODF ports to switch ports for equipment rooms, concatenates them according to the node sequence to form a port binding context, and adds the target ODF identifier, switch identifier, and cabinet identifier to the equipment room nodes, outputting cable core-level traceability information.

[0167] When a path modification is required, the path modification request is compared with the resource service data to identify the type of structural change and classify it accordingly. When only latitude and longitude or address information changes and the branching relationship of the cable remains unchanged, it is determined to be a basic attribute-level change. Only the corresponding fields are updated and the physical length of the line is recalculated. When non-critical access nodes are added or deleted, or the order of path nodes changes, but the set of key node identifiers at the beginning and end ends does not change, and the mapping relationship between ODF and switch ports remains unchanged, it is determined to be a path node-level change. The physical length of the line and the weight of the path's mandatory constraints are recalculated, and the path node relationship and routing scheduling parameters are incrementally synchronized. When the branching relationship of the cable or the port mapping relationship changes, it is determined to be a main branch structure-level change. First, all port binding relationships under the main optical cable tree are released and the number of occupied ports is reduced. Then, all associated records and old binding data of the sub-optical cables are recursively deleted. Then, steps S4 to S7 are re-executed according to the modified path to generate new resource service data, thereby ensuring the consistency of the modified data.

[0168] In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

[0169] The above description is merely a specific embodiment 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 intelligent operation and maintenance management of optical cable main branches based on map node port collaborative linkage, characterized in that: include: S1: Obtain optical communication network node information, perform differentiated attribute calculations, obtain the path constraint weights and port availability coefficients of each node, establish a node-resource association model, and output a standardized set of node objects. S1 acquires optical communication network node information and performs differentiated attribute calculations to obtain the path constraint weights and port availability coefficients of each node, specifically including: S11: Acquire node source data and perform data cleaning and parsing. Collect raw discrete data from geographic information systems and resource management systems through interface calls. Perform format verification and outlier removal on the raw discrete data. Output a standardized basic data stream containing spatial coordinates, associated optical cable characteristic attributes, and node attribute fields. S12: Map the physical entity points in the optical cable path to unified node objects according to predefined topology rules, and construct the attribute structure of the node objects. The attribute structure includes a basic attribute set and an extended attribute set. The basic attribute set encapsulates the node number, node type, latitude and longitude, address information, connection relationship between nodes, associated optical cable layer type, associated optical cable fiber core specification and equipment resource identifier. The extended attribute set is reserved for storing the binding resource identifier and port status information. S13: Perform differential attribute calculations based on the node type field in the standardized basic data stream, and write the corresponding calculation results into the extended attribute set, specifically including: When the node type field is a well or a bend, resource retrieval is skipped. The sequence position weight is calculated based on the ratio of the node's position number in the optical cable path to the total number of nodes in the path. The local link span is calculated based on the spatial coordinates of the node and its adjacent upstream and downstream nodes. The spatial span weight is calculated based on the ratio of the local link span to the total span of the optical cable path. The sequence position weight and the spatial span weight are weighted and fused to obtain the path mandatory constraint weight. This path mandatory constraint weight is written into the extended attribute set. When the node type field is "data center", the node number in the basic attribute set is used as the search key. The corresponding data center resource type, ODF identifier, switch identifier, cabinet identifier, resource name and cabinet name are extracted from the resource management system and written into the extended attribute set. At the same time, the total number of ODF ports, the total number of used ports and the number of shared ports that support multiple services among the used ports are retrieved. Based on the total number of ODF ports, the total number of used ports, the number of shared ports and the preset multiplexing conversion factor, the port availability coefficient of the data center node is calculated. When the port availability coefficient is lower than the preset availability threshold, a port overload identifier is generated; otherwise, a port availability identifier is generated. The total number of physical ports, the number of occupied ports, the port availability coefficient and the generated identifier of the data center node are written into the extended attribute set, and a bidirectional index mapping relationship between the node number and the physical resource identifier is generated. When the node type field is optical distribution box or connector package, based on the device identification data in the basic attribute set, the total number of physical ports, the number of occupied ports, and the number of shared ports supporting multiple service reuse among the occupied ports are retrieved from the port resource table. Based on the total number of physical ports, the number of occupied ports, the number of shared ports, and the preset multiplexing conversion factor, the port availability coefficient of the optical distribution box or connector package node is calculated. When the port availability coefficient is lower than the preset availability threshold, an access restricted identifier is generated; otherwise, an access unimpeded identifier is generated. The total number of physical ports, the number of occupied ports, the port availability coefficient, and the generated identifier are written into the extended attribute set. S2: Construct a fiber optic cable main branch association topology model based on a standardized set of node objects, and output fiber optic cable topology data; S3: Verify the access capabilities of routing nodes and branch fiber core mapping based on optical cable topology data, and output the routing data to be verified; S4: Constrain fiber core capacity margin and verify port capacity based on optical cable topology data and routing data to be verified, and output verified routing data; S5: Identify data center type nodes based on verified routing data and bind access device resources, then output path node data; S6: Based on the verified routing data, parse the spatial distance between nodes and calculate the line length, and output the main and branch optical cable storage data; S7: Identify node types and bind port resources based on the main and branch optical cable storage data and path node data, and output resource service data; S8: Respond to path modification requests, identify and classify structural change types based on resource business data, and output updated resource business data; S9: Obtain the target cable core identifier, construct the cable core path chain based on the main and branch optical cable storage data and updated resource service data, associate it with the port binding context, and output the cable core level traceability information.

2. The intelligent operation and maintenance management method for optical cable main branches based on map node port collaborative linkage according to claim 1, characterized in that, The S1 step establishes a node-resource association model and outputs a standardized set of node objects, specifically including: The node objects that have completed the writing of the extended attribute set are aggregated and serialized to establish a node-resource association model, thereby outputting a standardized set of node objects.

3. The intelligent operation and maintenance management method for optical cable main branches based on map node port collaborative linkage according to claims 1 and 2, characterized in that, S2 constructs a fiber optic cable main-branch association topology model based on a standardized set of node objects, and outputs fiber optic cable topology data, specifically including: Extract the node connection relationship data of the basic attribute set in the standardized node object set, and map the node sequence with continuous connection relationship to single optical cable path data; based on the topological features of the optical cable path and the associated optical cable level type in the node basic attribute set, identify whether the optical cable path is a main optical cable or a sub-optical cable and assign the corresponding level identifier, generate a parent optical cable identifier for the identified sub-optical cable, and establish its association relationship with the upper-level optical cable based on the parent optical cable identifier to construct a multi-level tree topology structure; For the main optical cable, read the associated optical cable core specification data from the basic attribute set of its node and generate complete core sequence data with a unique serial number; for the sub-optical cable, obtain the starting core serial number and ending core serial number of its planned configuration, and logically segment the core sequence data from the corresponding parent optical cable or top-level main optical cable based on the serial number range to generate the core mapping range data of the sub-optical cable. The generated fiber core mapping range data is subjected to inheritance conflict detection. The fiber core mapping range of the same level sub-optical cable is compared to see if there is an overlapping range. The cable core inheritance conflict index is calculated based on the ratio of the number of fiber cores in the overlapping range to the total number of fiber cores to be allocated. The cable core inheritance conflict index is compared with the preset conflict threshold. When the cable core inheritance conflict index exceeds the preset conflict threshold, a conflict alarm sign is generated; otherwise, a valid inheritance sign is generated. Traverse the optical cable path data that has completed hierarchical division and fiber core mapping, associate and bind the node number and node type with the optical cable identifier, update and write it into the node association table, and integrate the multi-level tree topology structure, fiber core mapping range data and collision detection identifier to output the optical cable topology structure data.

4. The intelligent operation and maintenance management method for optical cable main branches based on map node port collaborative linkage according to claim 3, characterized in that, The S3 verifies the access capabilities of routing nodes and the mapping of branch fiber cores based on the optical cable topology data, and outputs the routing data to be verified, specifically including: Based on the standardized set of node objects and optical cable topology data, the selected main line node sequence is extracted, and the main line path data is constructed according to the connection relationship between nodes in the basic attribute set. When the node type of the main line tail node or the tail node of the already constructed branch cable is an optical distribution box or connector package, the branch cable branching logic is triggered; the branch cable configuration parameters are obtained, including the number of branch cables, the number of cores in each branch cable, and the first node number; Access capability verification is performed by extracting the identifier data from the extended attribute set of the corresponding node object based on the first node number. Specifically, when the first node is an optical distribution box or connector package, the access smoothness identifier in its extended attribute set is identified. If the identifier exists, the first node is determined to have access capability. When the first node is a computer room, the port availability identifier in its extended attribute set is identified. If the identifier exists, the first node is determined to have access capability. For each sub-cable that passes verification, logical segmentation is performed based on its core count parameter and the core sequence data of the upper-level optical cable in the optical cable topology data to generate fiber core mapping range data for each sub-cable. The generated fiber core mapping range data is compared with the existing mapping ranges in the same-level sub-cable and optical cable topology data, and core inheritance conflict detection is performed to generate corresponding conflict detection identifiers. Based on the conflict detection identifiers, parent identifiers are assigned to each sub-cable and a sub-cable tree structure is constructed. Finally, the main line path data, branch cable relationships, fiber core mapping range data, and conflict detection identifiers are integrated to output the route data to be verified, which includes node connection relationships, branch attributes, and branch cable configuration information. The branch attributes are specifically the branch cable tree structure.

5. The intelligent operation and maintenance management method for optical cable main branches based on map node port collaborative linkage according to claim 4, characterized in that, S4 constrains fiber core capacity margin and verifies port capacity based on optical cable topology data and routing data to be verified, and outputs verified routing data, specifically including: Based on the cable tree structure in the routing data to be verified and the hierarchical inheritance relationship in the optical cable topology data, the fiber core mapping range data of each level of cable is extracted from top to bottom to calculate the allocated fiber core quantity. Combined with the fiber core specification data of the associated optical cable of the node to which the parent optical cable belongs in the standardized node object set, the remaining allocable fiber core quantity is calculated. When the core number parameter of the cable to be verified is greater than the remaining allocable fiber core quantity of its parent optical cable, a fiber core capacity over-limit flag is generated. Simultaneously, based on the routing data to be verified, the target nodes traversed by the main line and branch cables are extracted. Based on the number of cores in each branch cable in the branch cable configuration information and the preset fiber core port mapping rules, the new port demand of each target node is calculated. Combined with the number of occupied ports in the corresponding node extended attribute set in the standardized node object set, the total port demand is calculated. The total port demand is compared with the total number of physical ports of the corresponding node. When the total port demand is greater than the total number of physical ports, a port capacity conflict identifier is generated and the corresponding node number is associated with it and output. When no fiber core capacity over-limit flag or port capacity conflict flag is generated, the routing data to be verified is marked as valid for verification, and a pre-occupancy lock operation is performed on the new port requirements involved in the verification, and the verified routing data is output; otherwise, verification abnormal data containing the corresponding conflict flag is output.

6. The intelligent operation and maintenance management method for optical cable main branches based on map node port collaborative linkage according to claim 5, characterized in that, The S5 identifies data center type nodes based on verified routing data and binds them to access device resources, outputting path node data, specifically including: Traverse the node sequence in the verified routing data. When the node type is identified as a data center, extract the identifier data from the extended attribute set of the node object to determine the access status: if there is a port overload identifier, generate a resource shortage alarm identifier; if there is a port available identifier, trigger the resource binding logic. Based on the ODF identifier and bidirectional index mapping relationship recorded in the extended attribute set of the data center node, the corresponding available ODF device data is retrieved; the selected target ODF identifier is obtained, the resource name and data center resource type corresponding to the target ODF are extracted, and the target ODF identifier, resource name and data center resource type are updated and written into the extended attribute set of the data center node object to complete the mapping and binding from the geographic coordinate node to the physical access resource. The node data that has been bound to the resource is integrated with the verified route data to output the path node data.

7. The intelligent operation and maintenance management method for optical cable main branches based on map node port collaborative linkage according to claim 6, characterized in that, S6 parses the spatial distance between nodes based on the verified routing data and calculates the line length, outputting the main and branch optical cable storage data, specifically including: Extract the node sequence based on the verified routing data, and read the latitude and longitude or spatial coordinates from the basic attribute set of the standardized node object set. Calculate the geographical distance between adjacent nodes and accumulate them to obtain the physical length of the line. Update the verified routing data with the physical length of the line as the standard length data. Perform the main and branch optical cable saving operation, generate the main optical cable code and cable core code for the main optical cable, and write the main optical cable code and cable core code into the node association table according to the node order; for the sub-optical cable, extract the parent identifier of the sub-cable tree structure and the fiber core mapping range data from the verified routing data, generate the sub-optical cable exclusive cable core code based on the cable core code and fiber core mapping range of the parent optical cable, and bind the fiber core mapping range data to the sub-optical cable path; Finally, the main optical cable code, cable core code, node sequence, line physical length and fiber core mapping range data are integrated to output the main and branch optical cable storage data.

8. The intelligent operation and maintenance management method for optical cable main branches based on map node port collaborative linkage according to claim 7, characterized in that, The S7 identifies node types and binds port resources based on the main and branch optical cable storage data and path node data, and outputs resource service data, specifically including: Based on the node order in the main optical cable storage data, the corresponding nodes are extracted, and the node type is matched, located, and identified in the standardized node object set. When the node type is an optical distribution box or connector package, the total number of physical ports, the number of occupied ports, and the number of shared ports in the node's extended attribute set are extracted to perform port allocation: priority is given to allocating shared ports that support multiple service reuse from the occupied ports, and any shortfall is made up from the remaining available physical ports in sequence; based on the allocation result, the corresponding cable core code is bound to the port identifier to generate a service resource binding record, the number of occupied ports in the node's extended attribute set is increased and updated; when the remaining available physical ports cannot meet the demand, a port resource shortage alarm is generated; When the node type is a data center, extract the target ODF identifier that has been bound in the extended attribute set of the node and allocate the ODF port to the corresponding cable core code. At the same time, based on the switch identifier and cabinet identifier in the extended attribute set, establish the mapping relationship from the cable core code to the switch port via the ODF port and generate a service resource binding record that includes the mapping of equipment in the data center. When the node type is a well or a turning point, extract the path constraint weights from the node's extended attribute set and write them into the business resource binding record as routing scheduling parameters. Finally, the business resource binding records of all nodes are integrated, and the main optical cable code, cable core code, node order, line physical length and fiber core mapping range data in the main and branch optical cable storage data are combined to output resource business data.

9. The intelligent operation and maintenance management method for optical cable main branches based on map node port collaborative linkage according to claim 8, characterized in that, The S8 response path modification request identifies and classifies the structural change type based on resource business data, and outputs updated resource business data, specifically including: By comparing the changed data in the path modification request with the resource business data and the standardized node object set item by item, three types of structural changes were identified: When only the latitude, longitude, or address information in the basic attribute set of the standardized node object set changes, and the cable branching relationship in the resource business data remains unchanged, it is determined to be a basic attribute level change; the corresponding fields in the basic attribute set are updated, and the physical length of the line is recalculated based on the updated latitude and longitude to update the resource business data; When a non-critical access node is added or deleted, or the order of path nodes changes, but the set of critical node identifiers at the beginning and end points is not added or deleted, and the ODF port mapping relationship and switch port mapping relationship in the resource service data remain unchanged, it is determined to be a path node-level change. The physical length of the line is recalculated based on the updated node order and the spatial coordinates in the basic attribute set of the standardized node object set and updated to the resource service data. At the same time, the path must-pass constraint weights in the extended attribute set of the associated nodes under this path are recalculated and updated. The path node relationship and routing scheduling parameters in the resource service data are incrementally synchronized. When the branch cable relationship, ODF port mapping relationship, or switch port mapping relationship in the resource service data changes, it is determined to be a change at the main branch structure level. First, release all port binding relationships under the main optical cable tree according to the resource service data, and reduce and update the number of occupied ports in the corresponding node extended attribute set. Then, recursively delete the association records and old binding data of all sub-optical cables under the main optical cable tree according to the node association table. Then, re-execute steps S4 to S7 according to the modified path to generate new resource service data, and finally output the updated resource service data.

10. The intelligent operation and maintenance management method for optical cable main branches based on map node port collaborative linkage according to claim 9, characterized in that, S9 acquires the target cable core identifier, constructs a cable core path chain based on the main and branch optical cable storage data and updated resource service data, associates it with the port binding context, and outputs cable core-level traceability information, specifically including: Based on the target cable core identifier and the fiber core mapping range data and sub-cable tree structure in the main branch optical cable storage data, the cable core path chain is constructed from the top main optical cable to the top main optical cable identifier by tracing back along the parent identifier in the sub-cable tree structure through each level of sub-optical cable to the target cable core. Extract the node sequence of each level of optical cable record on the cable core path chain, trim and remove duplicate node sequences where the first node of the branch is the same in two adjacent optical cables, and merge them in topological order to generate the complete node sequence of the target cable core. Based on the node identifiers in the complete sequence of nodes, extract the service resource binding records of the corresponding nodes from the updated resource service data; for optical distribution box or connector packet nodes, extract the binding relationship between cable core codes and port identifiers; for equipment room nodes, extract the mapping relationship between cable core codes via ODF ports to switch ports; and form the port binding context of the target cable core by concatenating the nodes in sequence. Simultaneously, the target ODF identifier, resource name, data center resource type, switch identifier, and cabinet identifier are attached to the data center nodes in the complete traversed node sequence as extended attributes. Finally, the target cable core identifier, the complete traversed node sequence, port binding context, and additional device identifier information are integrated to output cable core-level traceability information.

Images