A communication network twinning method and apparatus

Abstract

The application relates to a communication network twinning method and device, and belongs to the field of data twinning. The method comprises the following steps: respectively initializing configuration rules between a CN2 bearer network and a PON network and a metropolitan area network; classifying data in the configuration rules into template data; obtaining a to-be-twinning communication network task of a target user; calling circuit topology data of a province side and backbone side of the to-be-twinning communication network task in the form of the template data; performing front-end splicing verification on the circuit topology data of the province side and the backbone side according to the configuration rules; if the verification is passed, the method proceeds to step S7, otherwise, the method proceeds to step S6; outputting a splicing abnormity prompt and terminating splicing; splicing the circuit topology data of the province side and the backbone side to obtain twinned topology data of the to-be-twinning communication network task; and lowering the twinned topology data to the target user. The method improves the twinning efficiency and accuracy of the communication network.

Description

Technical Field

[0001] This invention belongs to the field of data twins, and particularly relates to a method and apparatus for creating a communication network twin. Background Technology

[0002] A communication network is a system in which multiple communication devices are interconnected through physical media or wireless signals to transmit and exchange information. Communication networks can be divided into multiple layers, including access networks, metropolitan area networks, and backbone networks, supporting various types of communication needs such as voice, data, and video. Common communication networks include the Internet, mobile communication networks, and dedicated communication networks.

[0003] Digital twin modeling of communication networks creates a virtual copy of the network that reflects its operational status and structure in real time. This is crucial for monitoring network health, optimizing resource allocation, timely detection of potential faults, and improving maintenance efficiency. Through the twin model, complex network topologies can be understood more intuitively, and rapid diagnosis and prediction of problems can be supported, reducing downtime and thus improving the reliability and performance of the entire network.

[0004] However, existing communication network twins often only focus on the connection relationships between individual node data and do not form a complete system. As the number of communication network nodes increases, it is difficult to accurately twinnize the real-time communication network, resulting in many errors in the reproduction effect, which cannot meet the growing demand for accurate network reproduction. Summary of the Invention

[0005] In view of the shortcomings of the prior art, the purpose of the invention is to provide a communication network twin method and device, which can improve the topology efficiency and accuracy of communication networks, effectively cope with the rapid growth of communication network nodes, greatly improve the standardization and accuracy of communication network topology, enhance the satisfaction of target users, and increase enterprise competitiveness.

[0006] In a first aspect, the present invention provides a method for twinning communication networks, the method comprising:

[0007] S1, initialize the configuration rules between CN2 bearer network and PON network and metropolitan area network respectively;

[0008] S2 categorizes the data in the configuration rules into template data, which includes node data, relationship data, and link data;

[0009] S3, Obtain the target user's twin communication network task;

[0010] S4, retrieve the provincial-side circuit topology data and backbone-side circuit topology data of the twin communication network task in the form of template data;

[0011] S5. Perform a pre-assembly verification on the provincial circuit topology data and the backbone circuit topology data according to the configuration rules. If the verification passes, proceed to step S7; otherwise, proceed to step S6.

[0012] S6 outputs a splicing error alert and terminates the splicing process;

[0013] S7, stitch together the provincial side circuit topology data and the backbone side circuit topology data to obtain the twin topology data of the twin communication network task to be twinned;

[0014] S8 distributes twin topology data to target users.

[0015] Furthermore, the configuration rules include boundary name, boundary type, starting device of boundary type, ending device of boundary type, backbone network access status, and link node label. The boundary name includes PON-MAN and MAN-CN2. The boundary type for PON-MAN is "Boundary," while the boundary type for MAN-CN2 is "Device." The starting devices for the boundary include OLT devices, MAN ASBR devices, MAN SW devices, and devices. The starting devices for the device include MAN ASBR devices, MAN SW devices, and devices. The ending devices for the boundary include MAN SW devices, MSE devices, MAN ASBR devices, MAN BAS devices, PE and CN2 SW devices. The ending devices for the device include PE and CN2 SW devices. The backbone network access status for PON-MAN is "No," while the backbone network access status for MAN-CN2 is "Yes." The link node label for PON-MAN includes Ethernet link combined with hard hop label and single Ethernet link label, while the link node label for MAN-CN2 is a single Ethernet link label.

[0016] Furthermore, node data corresponds to the nodes data in the configuration rules, relationship data corresponds to the relations data in the configuration rules, and link data corresponds to the links data in the configuration rules.

[0017] Node data includes nodeLabels, which define a list of labels for each object;

[0018] The relational data includes linkType corresponding to the link specification name, gid corresponding to the Gid, name corresponding to the name, code corresponding to the encoding, spec_id corresponding to the specification ID, a_port_id corresponding to the port ID of the A-end, a_device_id corresponding to the physical device ID and logical device ID of the A-end, z_port_id corresponding to the port ID of the Z-end, z_device_id corresponding to the physical device ID and logical device ID of the Z-end, using_state_id corresponding to the service status, nextPage corresponding to the next page status, and extended attributes;

[0019] The relation data includes relationType corresponding to the relation specification metadata, gid corresponding to Gid, a_entity_id corresponding to the start node gid, z_entity_id corresponding to the end node gid, a_nodelables corresponding to the entity label of the A-side, and z_nodelables corresponding to the entity label of the Z-side.

[0020] Furthermore, based on the configuration rules, a pre-assembly verification is performed on the provincial-side circuit topology data and the backbone-side circuit topology data, specifically including:

[0021] S501, locate the starting device according to the query rules;

[0022] S502, based on the serial routing of the starting device, find the termination device corresponding to the starting device;

[0023] S503 defines the termination equipment that is the same as the group boundary station in the station to which each termination equipment belongs as the boundary equipment.

[0024] S504 determines whether the boundary device conforms to the local device connection rules. If it does, the verification passes; otherwise, the verification fails.

[0025] Furthermore, the query rules specifically include a first query rule, a second query rule, and a third query rule;

[0026] The first query rule is to determine the starting device based on the geographical location and the local branch office of each device.

[0027] The second query rule is to determine the starting device based on the coverage area of ​​each device.

[0028] The third query rule is to determine the originating device based on the start and end points of the hat link to which the device belongs.

[0029] Furthermore, S502 specifically refers to:

[0030] Determine the serial route of the starting device;

[0031] The traversal route of the starting device is determined based on the serial route, and the last traversal route is determined as the terminating device, wherein there is at least one terminating device.

[0032] A second aspect of the present invention provides a communication network twinning apparatus for implementing the communication network twinning method of any of the first aspects, the apparatus comprising:

[0033] The initialization module is used to initialize the configuration rules between the CN2 bearer network and the PON network and the metropolitan area network, respectively.

[0034] The classification module is used to classify the data in the configuration rules into template data, which includes node data, relationship data, and link data.

[0035] The acquisition module is used to acquire the twin communication network tasks of the target user;

[0036] The retrieval module is used to retrieve the provincial-side circuit topology data and backbone-side circuit topology data of the twin communication network task in the form of template data.

[0037] The verification module is used to perform pre-assembly verification of the provincial-side circuit topology data and the backbone-side circuit topology data according to the configuration rules. If the verification passes, the assembly module is called; otherwise, the output module is called.

[0038] The output module is used to output splicing error alerts and terminate splicing.

[0039] The splicing module is used to splice the provincial-side circuit topology data and the backbone-side circuit topology data to obtain the twin topology data of the twin communication network task to be twinned.

[0040] The distribution module is used to distribute twin topology data to target users.

[0041] Furthermore, the configuration rules include boundary name, boundary type, starting device of boundary type, ending device of boundary type, backbone network access status, and link node label. The boundary name includes PON-MAN and MAN-CN2. The boundary type for PON-MAN is "Boundary," while the boundary type for MAN-CN2 is "Device." The starting devices for the boundary include OLT devices, MAN ASBR devices, MAN SW devices, and devices. The starting devices for the device include MAN ASBR devices, MAN SW devices, and devices. The ending devices for the boundary include MAN SW devices, MSE devices, MAN ASBR devices, MAN BAS devices, PE and CN2 SW devices. The ending devices for the device include PE and CN2 SW devices. The backbone network access status for PON-MAN is "No," while the backbone network access status for MAN-CN2 is "Yes." The link node label for PON-MAN includes Ethernet link combined with hard hop label and single Ethernet link label, while the link node label for MAN-CN2 is a single Ethernet link label.

[0042] Furthermore, node data corresponds to the nodes data in the configuration rules, relationship data corresponds to the relations data in the configuration rules, and link data corresponds to the links data in the configuration rules.

[0043] Node data includes nodeLabels, which define a list of labels for each object;

[0044] The relational data includes linkType corresponding to the link specification name, gid corresponding to the Gid, name corresponding to the name, code corresponding to the encoding, spec_id corresponding to the specification ID, a_port_id corresponding to the port ID of the A-end, a_device_id corresponding to the physical device ID and logical device ID of the A-end, z_port_id corresponding to the port ID of the Z-end, z_device_id corresponding to the physical device ID and logical device ID of the Z-end, using_state_id corresponding to the service status, nextPage corresponding to the next page status, and extended attributes;

[0045] The relation data includes relationType corresponding to the relation specification metadata, gid corresponding to Gid, a_entity_id corresponding to the start node gid, z_entity_id corresponding to the end node gid, a_nodelables corresponding to the entity label of the A-side, and z_nodelables corresponding to the entity label of the Z-side.

[0046] Furthermore, based on the configuration rules, a pre-assembly verification is performed on the provincial-side circuit topology data and the backbone-side circuit topology data, specifically including:

[0047] Find the starting device according to the query rules;

[0048] Based on the serial routing of the starting device, find the corresponding termination device.

[0049] The termination equipment that is the same as the boundary station of the group among the stations to which each termination equipment belongs is identified as the boundary equipment.

[0050] Determine whether the boundary device conforms to the local device connection rules. If it does, the verification passes; otherwise, the verification fails.

[0051] Furthermore, the query rules specifically include a first query rule, a second query rule, and a third query rule;

[0052] The first query rule is to determine the starting device based on the geographical location and the local branch office of each device.

[0053] The second query rule is to determine the starting device based on the coverage area of ​​each device.

[0054] The third query rule is to determine the originating device based on the start and end points of the hat link to which the device belongs.

[0055] Furthermore, based on the serial routing of the starting device, the corresponding ending device is found, specifically as follows:

[0056] Determine the serial route of the starting device;

[0057] The traversal route of the starting device is determined based on the serial route, and the last traversal route is determined as the terminating device, wherein there is at least one terminating device.

[0058] The beneficial effects of this invention are as follows:

[0059] In this embodiment of the invention, the configuration rules between the CN2 bearer network, PON network, and metropolitan area network are first initialized. Then, the data appearing in the configuration rules are uniformly classified as template data, providing a data foundation for the automated completion of communication network twinning. Subsequently, data is extracted from the communication network to be twinned based on the template data, and the extracted data is automatically twinned based on the configuration rules. During the twinning process, the configuration rules are used for pre-assembly verification. Only devices that pass the verification are assembled. Device assembly can be automated and templated in a self-supervised manner, which can effectively reduce manual intervention, improve the efficiency and accuracy of communication network twinning, effectively cope with the rapid growth of communication network nodes, greatly improve the standardization and accuracy of communication network topology, enhance the satisfaction of target users, and increase enterprise competitiveness. Attached Figure Description

[0060] The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Throughout the drawings, the same reference numerals denote the same parts. It is obvious that the drawings described below are merely some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings.

[0061] Figure 1 This is a flowchart illustrating a communication network twinning method provided in an embodiment of the present invention;

[0062] Figure 2 This is a schematic diagram of the structure of a communication network twin device provided in an embodiment of the present invention. Detailed Implementation

[0063] To enable those skilled in the art to better understand the technical solutions in the embodiments of the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. It should be understood that these descriptions are merely exemplary and are not intended to limit the scope of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0064] Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts disclosed in this invention.

[0065] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicating orientation or positional relationships based on the orientation or positional relationships shown in the accompanying drawings, are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance. The terms "installed," "connected," and "linked" should be interpreted broadly; for example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal communication of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0066] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of methods and systems consistent with some aspects of the invention as detailed in the appended claims.

[0067] This invention proposes a communication network twinning method and apparatus to address the problems that existing communication network twinning methods often only focus on the connection relationships between individual node data and do not form a complete system. As the number of communication network nodes increases, it is difficult to accurately twinnize the real-time communication network, resulting in many errors in the reproduction effect and failing to meet the growing demand for accurate network reproduction.

[0068] Method Implementation Examples

[0069] Reference Figure 1 The diagram shows a flowchart of a communication network twin method provided by an embodiment of the present invention.

[0070] This invention provides a communication network twinning method, the method comprising:

[0071] Specifically, the method includes steps S1 to S8.

[0072] S1 initializes the configuration rules between the CN2 bearer network and the PON network and the metropolitan area network, respectively.

[0073] CN2 (China Net Next Carrying Network) is a multi-service carrier network that can support the convergence of data, voice, and video services. The first phase of China Telecom's CN2 network consists of a backbone network and a premium service network. In particular, the carrier network's ability to support new services is an important link between China Telecom's backbone network and its commercial customers, and will directly determine the quality and flexibility provided by China Telecom.

[0074] PON (Passive Optical Network) is a single-fiber bidirectional optical access network with a point-to-multipoint (P2MP) structure, mainly composed of an optical line terminal (OLT) at the central office, an optical distribution network (ODN), and optical network units (ONUs) at the user side. This network structure avoids electromagnetic interference and lightning strikes from external equipment, reduces the failure rate of lines and external equipment, improves system reliability, and saves maintenance costs.

[0075] A Metropolitan Area Network (MAN) is a computer communication network established within a city. It is a type of broadband local area network. Due to the use of LAN technology with active switching elements, transmission latency is relatively low. Its transmission medium is primarily fiber optic cable, and transmission rates exceed 100 megabits per second.

[0076] It should be noted that by initializing the configuration rules for the CN2 bearer network, PON network, and metropolitan area network separately, a foundation is laid for unified management between different networks, ensuring the flexibility and compatibility of network configuration and improving the efficiency and accuracy of subsequent twin operations.

[0077] In one possible implementation, the configuration rules include the boundary name, boundary type, starting device of the boundary type, ending device of the boundary type, backbone network access status, and link node label.

[0078] The boundary names include PON-MAN and MAN-CN2. The boundary type of PON-MAN is "Boundary," while the boundary type of MAN-CN2 is "Device." The starting devices of the boundary include OLT devices, MAN ASBR devices, MAN SW devices, and devices. The starting devices of the device include MAN ASBR devices, MAN SW devices, and devices. The ending devices of the boundary include MAN SW devices, MSE devices, MAN ASBR devices, MAN BAS devices, PE and CN2 SW devices. The ending devices of the device include PE and CN2 SW devices. The backbone network access status of PON-MAN is "No," while the backbone network access status of MAN-CN2 is "Yes." The link node labels of PON-MAN include Ethernet link combined with hard hop labels and single Ethernet link labels, while the link node labels of MAN-CN2 are single Ethernet link labels.

[0079] It should be noted that the configuration rules also include determining the long-term boundary type of network data before splicing. The long-term boundary refers to the boundary between the local network segment (provincial / municipal) and the backbone segment (group). In splicing processes involving two levels of network data (provincial / municipal network data or group network data), the target circuits are mainly cross-domain circuits (first-tier and second-tier backbone circuits). The local segment of these cross-domain circuits is managed by the provincial side, and the backbone segment by the group. Resource data is stored separately. To form a complete network topology, the two levels of data need to be audited and spliced, and the splicing process must follow certain rules. Specifically, the long-term boundary refers to the boundary between the provincial and group circuits. "Long" refers to the long-distance (backbone segment), and "local" refers to the local (segment). This is an internal telecommunications terminology. Boundaries are divided into two types: long-term boundaries and ordinary network boundaries. Ordinary network boundaries do not require boundary splicing because they do not involve two levels of data storage. Whether it is a long-term boundary and whether it crosses the backbone refers to whether this boundary is a provincial or group data boundary. For example, PON-MAN does not belong to the long-term boundary and is not part of the backbone segment. In this case, the rules and policies used are spliced ​​according to the boundary. For another example, MAN-CN2 is the long-term boundary and belongs to the backbone network. In this case, the rules and policies are spliced ​​according to the device (Z end).

[0080]

[0081]

[0082] Table 1

[0083] Referring to Table 1, a rule table showing the detailed rule data storage is presented.

[0084] An ASBR (Autonomous System Border Router) is a router that connects different autonomous systems and is used to pass routing information between them. When a router connects to different autonomous systems, it becomes an ASBR. It needs to maintain the topology information and routing table of each autonomous system and perform information transmission and route exchange between different autonomous systems.

[0085] A switch (SW) is a network device that expands a network by providing additional ports. The function of a switch is to enable a network to connect more computer devices, thereby enhancing network performance and reliability.

[0086] MSE (Multi-Service Edge) is a new type of device located at the edge of an IP / MPLS network, specifically designed to aggregate Layer 2 and Layer 3 data services.

[0087] A BAS (Basic Assembler Program) is a user access service device set up in the network aggregation layer. It can intelligently realize user aggregation, authentication, billing and other services, and can also conveniently provide a variety of IP value-added services according to user needs.

[0088] CE (Customer Edge) devices are used to interface with edge devices in the PTN network.

[0089] PE (Provider Edge, network-side edge device) is required to have encapsulation and decapsulation capabilities.

[0090] Specifically, boundary names refer to the boundary identifiers of different areas or layers within a network. Boundary type indicates the nature of the boundary. Start device refers to the device at the beginning of the boundary or link. End device refers to the device at the end of the link. Backbone network accessibility status indicates whether the network belongs to the backbone network layer and has WAN data transmission capabilities; "yes" means it can pass through the backbone network, and "no" means it cannot. Link node labels are used to identify node information in a link; for example, Ethernet links combined with hard hop labels indicate the specific link attributes and hop count.

[0091] In practical applications, the purpose of setting these configuration rules is to ensure that connections and transmissions between different layers in the network have clear boundaries and are standardized. By defining boundary names, starting devices, ending devices, etc., the responsibilities and functions of different network areas (such as PON, metropolitan area networks, and CN2) can be effectively delineated, preventing data conflicts or errors during transmission. Configuration rules also enhance the automation of network operation and maintenance, facilitating rapid identification of problem points. In addition, link node labels help administrators clearly understand the hop count, bandwidth, and other attributes of each link, achieving efficient network management. Overall, these rules improve the standardization, scalability, and management efficiency of the network architecture, ensuring the reliability of cross-network data transmission.

[0092] S2 categorizes the data in the configuration rules into template data, which includes node data, relationship data, and link data.

[0093] Template data is a standardized and structured abstract collection of network information from configuration rules, facilitating subsequent operations and processing. Templates allow for unified management and operation of different types of network data, ensuring consistency. Node data refers to the specific information of each device or entity in the network, such as the attributes and status of devices like routers and switches. It describes the basic information of each node in the network topology, such as location and function. Relationship data describes the connections and dependencies between different nodes in the network, defining the interactions between network devices, such as two routers connected by a link, or the hierarchical structure between devices. Link data refers to detailed information about the transmission channels between different nodes, including the link's bandwidth, type, hop count, and whether it is a physical or virtual link.

[0094] It should be noted that classifying configuration rule data into template data can standardize and structure network information, making data processing for different network types (such as CN2, PON, and metropolitan area networks) more unified and efficient. This approach reduces complexity, facilitates the generation and management of automated twin models, and improves the accuracy and speed of analysis of communication network topology through this templated data. At the same time, it reduces the risk of errors in manual configuration and operation, making the network twin process more flexible and scalable.

[0095] In one possible implementation, node data corresponds to nodes data in the configuration rule, relation data corresponds to relations data in the configuration rule, and link data corresponds to links data in the configuration rule.

[0096] Node data includes nodeLabels, which are used to define a list of labels for each object.

[0097] The relational data includes linkType corresponding to the link specification name, gid corresponding to the Gid, name corresponding to the name, code corresponding to the encoding, spec_id corresponding to the specification ID, a_port_id corresponding to the port ID of the A-end, a_device_id corresponding to the physical device ID and logical device ID of the A-end, z_port_id corresponding to the port ID of the Z-end, z_device_id corresponding to the physical device ID and logical device ID of the Z-end, using_state_id corresponding to the service status, nextPage corresponding to the next page status, and extended attributes.

[0098] The relation data includes relationType corresponding to the relation specification metadata, gid corresponding to Gid, a_entity_id corresponding to the start node gid, z_entity_id corresponding to the end node gid, a_nodelables corresponding to the entity label of the A-side, and z_nodelables corresponding to the entity label of the Z-side.

[0099] It should be noted that by mapping node data, relationship data, and link data to specific data structures in the configuration rules, such as nodes, relations, and links, accurate network topology modeling is achieved. Each node defines a detailed list of tags, and each relationship contains detailed link information, such as device ID, port ID, and specification ID. This approach helps standardize the processing of complex network information, ensures data consistency and traceability, effectively reduces errors, improves the efficiency and accuracy of network data management, and provides a reliable foundation for subsequent network topology stitching.

[0100] S3, Obtain the target user's twin communication network task.

[0101] Among them, the task of creating a digital twin communication network refers to the specific task submitted by the user that requires digital twin modeling of their communication network. A digital twin is a virtual copy of a physical network. Therefore, the goal of this task is to perform comprehensive virtualization modeling of the user's communication network so that the network can be simulated, monitored, optimized, or troubleshooted in a virtual environment, thereby maintaining synchronization with the actual network and reflecting the network's status and operation in real time.

[0102] S4 retrieves the provincial-side circuit topology data and backbone-side circuit topology data of the twin communication network task in the form of template data.

[0103] Among them, provincial-level circuit topology data refers to the network topology structure of the communication network located within a provincial area, including network nodes, device connections and link information within the region. It is usually responsible for data transmission and processing within the province or region, covering local network devices, links and their interrelationships.

[0104] Backbone-side circuit topology data refers to the topology of the backbone network at the national or inter-provincial level. This data includes large, long-distance data transmission lines, backbone routers, switches, and other equipment. The backbone network is responsible for large-scale data transmission across regions, connecting various provincial networks and providing higher bandwidth and wider coverage.

[0105] It should be noted that retrieving circuit topology data from the provincial and backbone sides in the form of template data enables standardized processing of multi-level network structures. This not only simplifies the integration process of different network levels but also ensures the consistency and integrity of network data. Through this method, the twin modeling of network topology is more accurate, facilitating unified management and maintenance, and helping to fully understand and optimize the network structure.

[0106] S5. Perform a pre-assembly verification on the provincial-side circuit topology data and the backbone-side circuit topology data according to the configuration rules. If the verification passes, proceed to step S7; otherwise, proceed to step S6.

[0107] It should be noted that by configuring rules to perform pre-assembly verification of the circuit topology data on the provincial side and the backbone side, the accuracy, integrity and consistency of the data are ensured. Verification before assembly can detect data errors or mismatches in advance, avoid assembly errors in subsequent operations, thereby reducing debugging time and system failures, improving the reliability of the overall network twin modeling, ensuring that the generated topology data is more accurate, and reducing the need for manual intervention.

[0108] In one possible implementation, pre-assembly verification is performed on the provincial-side circuit topology data and the backbone-side circuit topology data according to configuration rules, specifically including:

[0109] S501, find the starting device according to the query rules.

[0110] In one possible implementation, the query rules specifically include a first query rule, a second query rule, and a third query rule.

[0111] The first query rule is to determine the starting device based on the geographical location and the local exchange location of each device.

[0112] The second query rule is to determine the starting device based on the coverage area of ​​each device.

[0113] The third query rule is to determine the originating device based on the start and end points of the hat link to which the device belongs.

[0114] It should be noted that by locating the starting device through multiple dimensions such as geographical location, coverage area, and link endpoints, the flexibility and accuracy of device lookup are ensured. This allows it to adapt to the needs of different network environments and topologies, improving the accuracy and efficiency of device identification and reducing lookup errors.

[0115] S502, based on the serial routing of the starting device, find the termination device corresponding to the starting device.

[0116] In one possible implementation, S502 specifically includes:

[0117] Determine the serial route for the starting device.

[0118] The traversal route of the starting device is determined based on the serial route, and the last traversal route is determined as the terminating device, wherein there is at least one terminating device.

[0119] It should be noted that by determining the serial and traversal routes of the starting device, the data transmission path can be effectively traced, ensuring accurate location of the terminating device. This method can handle multi-level connections in complex networks, supports the identification of multiple terminating devices, improves the accuracy and efficiency of network topology analysis, and ensures the integrity and visualization of the network structure.

[0120] S503 defines the termination equipment that is the same as the group boundary station among the stations to which each termination equipment belongs as the boundary equipment.

[0121] Specifically, by comparing the local station to which each terminating device belongs with the group boundary station, those devices that are identical to the group boundary station are identified as boundary devices. Boundary devices are key nodes connecting different network regions (such as the provincial side and the backbone side), marking the boundary points between different network layers. Identifying boundary devices further ensures that connections between devices conform to connection rules, thereby guaranteeing correct data transmission and network stability.

[0122] S504 determines whether the boundary device conforms to the local device connection rules. If it does, the verification passes; otherwise, the verification fails.

[0123] It should be noted that by querying the starting device, tracing the serial route, and the ending device from multiple dimensions, and comparing the ending device with the boundary station, it is ensured that the device connection and boundary conform to the connection rules. This method improves the accuracy of device identification, enhances the accuracy and completeness of network topology analysis, ensures reliable connection of cross-domain networks and stability of data transmission, reduces potential errors, and greatly improves network management efficiency.

[0124] S6 outputs a splicing error alert and terminates the splicing process.

[0125] S7, the provincial-side circuit topology data and the backbone-side circuit topology data are spliced ​​together to obtain the twin topology data of the twin communication network task to be twinned.

[0126] S8 distributes twin topology data to target users.

[0127] In practical application, this network twin method generates a complete network twin model by initializing network configuration rules, extracting provincial and backbone topology data, performing data verification, and stitching together. The entire process relies on standardized template data, automated query rules, and verification mechanisms to ensure the accuracy, completeness, and consistency of network data. This method reduces manual intervention, improves the efficiency and reliability of network topology modeling, facilitates network monitoring, optimization, and troubleshooting, and enables comprehensive management and automated operation and maintenance across network layers.

[0128] The beneficial effects of this invention are as follows:

[0129] In this embodiment of the invention, the configuration rules between the CN2 bearer network, PON network, and metropolitan area network are first initialized. Then, the data appearing in the configuration rules are uniformly classified as template data, providing a data foundation for the automated completion of communication network twinning. Subsequently, data is extracted from the communication network to be twinned based on the template data, and the extracted data is automatically twinned based on the configuration rules. During the twinning process, the configuration rules are used for pre-assembly verification. Only devices that pass the verification are assembled. Device assembly can be automated and templated in a self-supervised manner, which can effectively reduce manual intervention, improve the efficiency and accuracy of communication network twinning, effectively cope with the rapid growth of communication network nodes, greatly improve the standardization and accuracy of communication network topology, enhance the satisfaction of target users, and increase enterprise competitiveness.

[0130] Device Examples

[0131] Reference manual attached Figure 2 The diagram shows a schematic representation of a communication network twin device provided in an embodiment of the present invention.

[0132] Another specific embodiment of the present invention discloses a communication network twin device for implementing the communication network twin method of any one of the method embodiments. The communication network twin device 20 includes:

[0133] Initialization module 201 is used to initialize the configuration rules between CN2 bearer network and PON network and metropolitan area network respectively.

[0134] The classification module 202 is used to classify the data in the configuration rules into template data, wherein the template data includes node data, relationship data and link data.

[0135] The acquisition module 203 is used to acquire the twin communication network task of the target user.

[0136] The retrieval module 204 is used to retrieve the provincial-side circuit topology data and backbone-side circuit topology data of the twin communication network task in the form of template data.

[0137] The verification module 205 is used to perform pre-assembly verification on the provincial side circuit topology data and the backbone side circuit topology data according to the configuration rules. If the verification passes, the splicing module is called; otherwise, the output module is called.

[0138] Output module 206 is used to output splicing error reminders and terminate splicing.

[0139] The splicing module 207 is used to splice the provincial-side circuit topology data and the backbone-side circuit topology data to obtain the twin topology data of the twin communication network task to be twinned.

[0140] The delivery module 208 is used to deliver twin topology data to the target user.

[0141] In one possible implementation, the configuration rules include boundary name, boundary type, starting device of boundary type, ending device of boundary type, backbone network access status, and link node label. The boundary name includes PON-MAN and MAN-CN2. The boundary type of PON-MAN is "Boundary," and the boundary type of MAN-CN2 is "Device." The starting devices of the boundary include OLT devices, MAN ASBR devices, MAN SW devices, and devices. The starting devices of the devices include MAN ASBR devices, MAN SW devices, and devices. The ending devices of the boundary include MAN SW devices, MSE devices, MAN ASBR devices, MAN BAS devices, PE and CN2 SW devices. The ending devices of the devices include PE and CN2 SW devices. The backbone network access status of PON-MAN is "No," while the backbone network access status of MAN-CN2 is "Yes." The link node label of PON-MAN includes Ethernet link combined with hard hop label and single Ethernet link label, while the link node label of MAN-CN2 is a single Ethernet link label.

[0142] In one possible implementation, node data corresponds to nodes data in the configuration rule, relation data corresponds to relations data in the configuration rule, and link data corresponds to links data in the configuration rule.

[0143] Node data includes nodeLabels, which are used to define a list of labels for each object.

[0144] The relational data includes linkType corresponding to the link specification name, gid corresponding to the Gid, name corresponding to the name, code corresponding to the encoding, spec_id corresponding to the specification ID, a_port_id corresponding to the port ID of the A-end, a_device_id corresponding to the physical device ID and logical device ID of the A-end, z_port_id corresponding to the port ID of the Z-end, z_device_id corresponding to the physical device ID and logical device ID of the Z-end, using_state_id corresponding to the service status, nextPage corresponding to the next page status, and extended attributes.

[0145] The relation data includes relationType corresponding to the relation specification metadata, gid corresponding to Gid, a_entity_id corresponding to the start node gid, z_entity_id corresponding to the end node gid, a_nodelables corresponding to the entity label of the A-side, and z_nodelables corresponding to the entity label of the Z-side.

[0146] In one possible implementation, pre-assembly verification is performed on the provincial-side circuit topology data and the backbone-side circuit topology data according to configuration rules, specifically including:

[0147] Find the starting device according to the query rules.

[0148] The serial routing based on the starting device finds the corresponding ending device.

[0149] Termination devices that are identical to those at the group's boundary stations among the stations to which each termination device belongs are designated as boundary devices.

[0150] Determine whether the boundary device conforms to the local device connection rules. If it does, the verification passes; otherwise, the verification fails.

[0151] In one possible implementation, the query rules specifically include a first query rule, a second query rule, and a third query rule.

[0152] The first query rule is to determine the starting device based on the geographical location and the local exchange location of each device.

[0153] The second query rule is to determine the starting device based on the coverage area of ​​each device.

[0154] The third query rule is to determine the originating device based on the start and end points of the hat link to which the device belongs.

[0155] In one possible implementation, the termination device corresponding to the starting device is found based on the serial routing of the starting device, specifically as follows:

[0156] Determine the serial route for the starting device.

[0157] The traversal route of the starting device is determined based on the serial route, and the last traversal route is determined as the terminating device, wherein there is at least one terminating device.

[0158] The apparatus provided in this invention can implement the various processes and steps in the above method embodiments and can obtain the same or similar technical effects. To avoid repetition, this invention will not elaborate further.

[0159] The beneficial effects of this invention are as follows:

[0160] In this embodiment of the invention, the configuration rules between the CN2 bearer network, PON network, and metropolitan area network are first initialized. Then, the data appearing in the configuration rules are uniformly classified as template data, providing a data foundation for the automated completion of communication network twinning. Subsequently, data is extracted from the communication network to be twinned based on the template data, and the extracted data is automatically twinned based on the configuration rules. During the twinning process, the configuration rules are used for pre-assembly verification. Only devices that pass the verification are assembled. Device assembly can be automated and templated in a self-supervised manner, which can effectively reduce manual intervention, improve the efficiency and accuracy of communication network twinning, effectively cope with the rapid growth of communication network nodes, greatly improve the standardization and accuracy of communication network topology, enhance the satisfaction of target users, and increase enterprise competitiveness.

[0161] The applicant of this invention has provided a detailed description of the embodiments of the invention in conjunction with the accompanying drawings. However, those skilled in the art should understand that the above embodiments are merely preferred embodiments of the invention. The detailed description is only intended to help readers better understand the spirit of the invention and is not intended to limit the scope of protection of the invention. On the contrary, any improvements or modifications made based on the inventive spirit of the invention should fall within the scope of protection of the invention.

[0162] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the embodiments of the present invention, and are not intended to limit them. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the protection scope of the present invention.

Claims

1. A communication network twin method, characterized in that, The communication network twinning method comprises: S1, respectively initializing configuration rules between CN2 bearer network, PON network and metropolitan area network; S2, classifying data in the configuration rules as template data, wherein the template data comprises node data, relationship data and link data; S3, obtaining a target user's to-be-twinning communication network task; S4, calling provincial side circuit topology data and backbone side circuit topology data of the to-be-twinning communication network task in the form of the template data; S5, performing pre-splicing verification on the provincial side circuit topology data and the backbone side circuit topology data according to the configuration rules, if the verification is passed, entering step S7, otherwise, entering step S6; S6, outputting splicing abnormity reminding and terminating splicing; S7, splicing the provincial side circuit topology data and the backbone side circuit topology data to obtain twinned topology data of the to-be-twinning communication network task; S8, downlinking the twinned topology data to the target user.

2. The communication network twinning method of claim 1, wherein, The configuration rules comprise boundary name, boundary type, start device of boundary type, end device of boundary type, backbone network passing state and link node label, wherein the boundary name comprises PON-metropolitan area network and metropolitan area network-CN2, the boundary type of the PON-metropolitan area network is boundary, the boundary type of the metropolitan area network-CN2 is device, the start device of the boundary comprises OLT device, metropolitan area network ASBR device and metropolitan area network SW device, the start device of the boundary type of device comprises metropolitan area network ASBR device and metropolitan area network SW device, the end device of the boundary comprises metropolitan area network SW device, MSE device, metropolitan area network ASBR device, metropolitan area network BAS device, PE and CN2 SW device, the end device of the boundary type of device comprises PE and CN2 SW device, the backbone network passing state of the PON-metropolitan area network is no, the backbone network passing state of the metropolitan area network-CN2 is yes, the link node label of the PON-metropolitan area network comprises Ethernet link combination hard jump label and single Ethernet link label, and the link node label of the metropolitan area network-CN2 is single Ethernet link label. 3.The communication network twinning method of claim 1, wherein, The node data corresponds to nodes data in the configuration rules, the relationship data corresponds to relations data in the configuration rules, and the link data corresponds to links data in the configuration rules; The node data comprises nodeLabels used for defining a label list for each object. The relationship data includes linkType corresponding to a link specification name, gid corresponding to Gid, name corresponding to a name, code corresponding to an encoding, spec_id corresponding to a specification id, a_port_id corresponding to an A-end port ID, a_device_id corresponding to an A-end physical device ID and an A-end logical device ID, z_port_id corresponding to a Z-end port ID, z_device_id corresponding to a Z-end physical device ID and a Z-end logical device ID, using_state_id corresponding to a service state, nextPage corresponding to a next page state, and an extended attribute; The relationship data includes relationType corresponding to relationship specification metadata, gid corresponding to Gid, a_entity_id corresponding to a start node gid, z_entity_id corresponding to an end node gid, a_nodelables corresponding to an A-end entity label, and z_nodelables corresponding to a Z-end entity label.

4. The communication network twinning method of claim 1, wherein, The pre-splicing verification of the provincial side circuit topology data and the backbone side circuit topology data according to the configuration rule specifically includes: S501, querying a starting device according to a query rule; S502, finding a terminal device corresponding to the starting device based on a concatenation route of the starting device; S503, determining a boundary device as a terminal device belonging to the same group boundary station as a group boundary station among stations to which each terminal device belongs; S504, judging whether the boundary device meets a local device connection rule, and if so, the verification is passed, otherwise, the verification fails.

5. The communication network twinning method of claim 4, wherein, The query rule specifically includes a first query rule, a second query rule, and a third query rule; The first query rule is to determine the starting device according to a geographical position and a home station point of each device; The second query rule is to determine the starting device according to a coverage area of each device; The third query rule is to determine the starting device according to a starting end and a terminal end of a hat link to which the device belongs.

6. The communication network twinning method of claim 4, wherein, The S502 specifically includes: Determining a concatenation route of the starting device; Determining a pass-through route of the starting device according to the concatenation route, and determining a last pass-through route as the terminal device, wherein the terminal device is at least one.

7. A communication network twin device, characterized in that The communication network twinning device includes: An initialization module configured to initialize configuration rules between a CN2 bearer network, a PON network, and a metropolitan area network respectively; A classification module configured to classify data in the configuration rules as template data, wherein the template data includes node data, relationship data, and link data; An acquisition module configured to acquire a to-be-twinning communication network task of a target user; A calling module configured to call provincial side circuit topology data and backbone side circuit topology data of the to-be-twinning communication network task in the form of the template data; The checking module is configured to perform pre-splicing checking on the provincial side circuit topology data and the backbone side circuit topology data according to the configuration rule, and if the checking is passed, the splicing module is called, otherwise, the output module is called; The output module is configured to output a splicing exception prompt and terminate splicing; The splicing module is configured to splice the provincial side circuit topology data and the backbone side circuit topology data to obtain the twin topology data of the to-be-twin communication network task; The decentralization module is configured to decentralize the twin topology data to the target user.

8. The communication network twin apparatus according to claim 7, characterized in that, The configuration rule includes a boundary name, a boundary type, a start device of the boundary type, an end device of the boundary type, a backbone network pass state, and a link node label, wherein the boundary name includes PON-metropolitan area network and metropolitan area network-CN2, the boundary type of the PON-metropolitan area network is a boundary, the boundary type of the metropolitan area network-CN2 is a device, the start device of the boundary includes an OLT device, a metropolitan area network ASBR device, and a metropolitan area network SW device, the start device of the boundary type includes a metropolitan area network ASBR device and a metropolitan area network SW device, the end device of the boundary includes a metropolitan area network SW device, an MSE device, a metropolitan area network ASBR device, a metropolitan area network BAS device, a PE, and a SW device of CN2, the end device of the boundary type includes a PE and a SW device of CN2, the backbone network pass state of the PON-metropolitan area network is no, the backbone network pass state of the metropolitan area network-CN2 is yes, the link node label of the PON-metropolitan area network includes an Ethernet link combined hard jump label and a single Ethernet link label, and the link node label of the metropolitan area network-CN2 is a single Ethernet link label.

9. The communication network twin apparatus according to claim 7, wherein, The node data corresponds to the nodes data in the configuration rule, the relationship data corresponds to the relations data in the configuration rule, and the link data corresponds to the links data in the configuration rule; The node data includes nodeLabels for defining a label list for each object; The relationship data includes linkType corresponding to a link specification name, gid corresponding to a Gid, name corresponding to a name, code corresponding to a code, spec_id corresponding to a specification id, a_port_id corresponding to an A-end port ID, a_device_id corresponding to an A-end physical device ID and an A-end logical device ID, z_port_id corresponding to a Z-end port ID, z_device_id corresponding to a Z-end physical device ID and a Z-end logical device ID, using_state_id corresponding to a service state, nextPage corresponding to a next page state, and an extension attribute. The relationship data includes relationType corresponding to relationship specification metadata, gid corresponding to Gid, a_entity_id corresponding to start node gid, z_entity_id corresponding to end node gid, a_nodelables corresponding to A end entity label and z_nodelables corresponding to Z end entity label.

10. The communication network twin apparatus according to claim 7, wherein, The pre-splicing verification of the provincial side circuit topology data and the backbone side circuit topology data according to the configuration rule specifically includes: Finding a starting device according to a query rule; Finding a terminal device corresponding to the starting device based on a concatenation route of the starting device; Determining a boundary device as a terminal device in a same station of a group boundary station among terminal devices belonging to the station; Judging whether the boundary device meets a local device connection rule, and if yes, the verification is passed, otherwise, the verification fails.

Images