Communication network twinning method and device

Abstract

The invention relates to a communication network twinning method and device, and belongs to the field of data twinning. Comprising the following steps: respectively initializing configuration rules between a CN2 bearer network and a metropolitan area network and between a PON network and the metropolitan Classifying data in the configuration rule as template data; obtaining a to-be-twinned communication network task of the target user; calling provincial side circuit topology data and backbone side circuit topology data of a to-be-twinned communication network task in the form of template data; performing pre-splicing verification on the provincial side circuit topology data and the backbone side circuit topology data according to a configuration rule, if verification is passed, entering a step S7, otherwise, entering a step S6; outputting a splicing abnormity prompt, and terminating splicing; splicing the provincial side circuit topology data and the backbone side circuit topology data to obtain twin topology data of the communication network task to be twin; and transferring the twin topology data to the target user. And the twinning efficiency and accuracy of the communication network are improved.

Description

Technical Field

[0001] The present invention belongs to the field of data twins, and in particular, relates to a communication network twin method and device. Background Art

[0002] A communication network refers to a system in which multiple communication devices are connected to each other through physical media or wireless signals to transmit and exchange information. Communication networks can be divided into multiple levels, 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] Twinning (i.e., digital twin modeling) of communication networks can create a virtual copy of the network, reflecting its operating status and structure in real time, which is crucial for monitoring network health, optimizing resource allocation, promptly detecting potential faults, and improving maintenance efficiency. Through the twin model, complex network topology can be understood more intuitively, and it supports rapid diagnosis and prediction of problems, 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 relationship between individual node data and have not formed a complete system. As the number of communication network nodes increases, it is difficult to accurately twin the real-time communication network, and the reproduction effect has many errors, which cannot meet the growing demand for accurate network reproduction. Summary of the invention

[0005] In view of the above-mentioned deficiencies in the prior art, the purpose of the invention is to provide a communication network twin method and device, which can improve the topological efficiency and accuracy of the communication network, effectively cope with the rapid growth of communication network nodes, greatly improve the standardization and accuracy of the communication network topology, improve the satisfaction of target users, and increase corporate competitiveness.

[0006] A first aspect of the present invention provides a communication network twin method, the method comprising:

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

[0008] S2, classifying the data in the configuration rule into template data, wherein the template data includes node data, relationship data and link data;

[0009] S3, obtain the target user’s pending twin communication network tasks;

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

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

[0012] S6, output splicing abnormality reminder and terminate splicing;

[0013] S7, splicing 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;

[0014] S8, delegate the twin topology data to the target user.

[0015] Furthermore, the configuration rules include boundary names, boundary types, starting devices of boundary types, ending devices of boundary types, backbone network traffic status and link node labels, wherein the boundary names include PON-MAN and MAN-CN2, the boundary type of PON-MAN is boundary, 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 SW devices of CN2, the ending devices of the devices include PE and SW devices of CN2, the backbone network traffic status of PON-MAN is no, the backbone network peer status of MAN-CN2 is yes, the link node label of PON-MAN includes Ethernet link combined hard jump label and single Ethernet link label, and the link node label of MAN-CN2 is a single Ethernet link label.

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

[0017] The node data includes nodeLabels which is used to define a list of labels for each object;

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

[0019] The relationship data includes relationType corresponding to the relationship 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 A-end entity label, and z_nodelables corresponding to the Z-end entity label.

[0020] Furthermore, the provincial side circuit topology data and the backbone side circuit topology data are pre-joined and checked according to the configuration rules, specifically including:

[0021] S501, searching for a starting device according to a query rule;

[0022] S502, searching for a terminating device corresponding to the starting device based on the serial route of the starting device;

[0023] S503, determining the terminating device that is the same as the group boundary station in the station to which each terminating device belongs as the boundary device;

[0024] S504, determining whether the edge device complies with the local device connection rule, if yes, the verification passes, otherwise, the verification fails.

[0025] Further, 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 according to the geographical location and the affiliated office of each device;

[0027] The second query rule is to determine the starting device according to the coverage area of ​​each device;

[0028] The third query rule is to determine the starting device according to the starting end and the ending end of the hat link to which the device belongs.

[0029] Further, S502 is specifically:

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

[0031] The passing route of the starting device is determined according to the serial connection route, and the last passing 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 twin device for implementing any one of the communication network twin methods of the first aspect, the device comprising:

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

[0034] A classification module, used to classify the data in the configuration rule into template data, wherein the template data includes node data, relationship data and link data;

[0035] An acquisition module is used to obtain the target user's pending twin communication network tasks;

[0036] A calling module, used to call the provincial side circuit topology data and the 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-splicing 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;

[0038] Output module, used to output splicing abnormality reminder and terminate splicing;

[0039] A 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;

[0040] The decentralization module is used to decentralize the twin topology data to the target users.

[0041] Furthermore, the configuration rules include boundary names, boundary types, starting devices of boundary types, ending devices of boundary types, backbone network traffic status and link node labels, wherein the boundary names include PON-MAN and MAN-CN2, the boundary type of PON-MAN is boundary, 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 SW devices of CN2, the ending devices of the devices include PE and SW devices of CN2, the backbone network traffic status of PON-MAN is no, the backbone network peer status of MAN-CN2 is yes, the link node label of PON-MAN includes Ethernet link combined hard jump label and single Ethernet link label, and the link node label of MAN-CN2 is a single Ethernet link label.

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

[0043] The node data includes nodeLabels which is used to define a list of labels for each object;

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

[0045] The relationship data includes relationType corresponding to the relationship 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 A-end entity label, and z_nodelables corresponding to the Z-end entity label.

[0046] Furthermore, the provincial side circuit topology data and the backbone side circuit topology data are pre-joined and checked according to the configuration rules, specifically including:

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

[0048] Finding a terminating device corresponding to the starting device based on the serial route of the starting device;

[0049] The terminating equipment in the bureaus and stations to which each terminating equipment belongs that is the same as the group's boundary bureau and station is determined as the boundary equipment;

[0050] Determine whether the boundary device complies with the local device connection rules. If yes, the verification passes; otherwise, the verification fails.

[0051] Further, 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 according to the geographical location and the affiliated office of each device;

[0053] The second query rule is to determine the starting device according to the coverage area of ​​each device;

[0054] The third query rule is to determine the starting device according to the starting end and the ending end of the hat link to which the device belongs.

[0055] Further, based on the serial route of the starting device, the terminating device corresponding to the starting device is searched, specifically:

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

[0057] The passing route of the starting device is determined according to the serial connection route, and the last passing route is determined as the terminating device, wherein there is at least one terminating device.

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

[0059] In an embodiment of the present invention, the configuration rules between the CN2 bearer network and the PON network and the metropolitan area network are first initialized, and then the data appearing in the configuration rules are uniformly classified as template data to provide a data basis for the automatic completion of the communication network twin. After that, data is extracted for the twin communication network task in combination with the template data, and the extracted data is automatically twinned in combination with the configuration rules. In the twinning process, the configuration rules are used for pre-splicing verification, and only the equipment that passes the verification is spliced. The equipment splicing can be automatically performed in a templated manner in a self-supervising manner, which can effectively reduce manual intervention, improve the efficiency and accuracy of the communication network twin, and can effectively cope with the rapid growth of communication network nodes, greatly improve the standardization and accuracy of the communication network topology, improve the satisfaction of target users, and increase corporate competitiveness. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] The accompanying drawings are only used to illustrate specific embodiments and are not considered to limit the present invention. In the entire drawings, the same reference symbols represent the same components. Obviously, the drawings described below are only some embodiments recorded in the embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings.

[0061] Figure 1 It is a flow chart of a communication network twin method provided by an embodiment of the present invention;

[0062] Figure 2 It is a structural diagram of a communication network twin device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0063] In order 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 in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all of the embodiments. It should be understood that these descriptions are only 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 ordinary technicians in the field without making creative work should fall within the scope of protection of the present invention.

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

[0065] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the orientation or position relationship indicated by the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inside", "outside", etc. is based on the orientation or position relationship shown in the drawings, which is only for the convenience of describing the present invention and simplifying the description, and does not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation of the present invention. In addition, the terms "first", "second", and "third" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. The terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be a connection between the two elements. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

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

[0067] The present invention proposes a communication network twin method and device to solve the problems that the existing communication network twins often only focus on the connection relationship between individual node data and have not formed a complete system. As the number of communication network nodes increases, it is difficult to accurately twin the real-time communication network, and the reproduction effect has many errors, which cannot meet the growing demand for accurate network reproduction.

[0068] Method Embodiment

[0069] Reference Figure 1 , showing a flow chart of a communication network twin method provided in an embodiment of the present invention.

[0070] An embodiment of the present invention provides a communication network twin method, the method comprising:

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

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

[0073] Among them, CN2 (China Net Next Carrying Network) is a multi-service bearer network that can support the application of multiple business integration of data, voice and video. The first phase of China Telecom's CN2 network project consists of a backbone network and a boutique business network. In particular, the bearer network's ability to support new businesses 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 an optical network unit (ONU) at the user side. This network structure avoids electromagnetic interference and lightning effects from external devices, reduces the failure rate of lines and external devices, improves system reliability, and saves maintenance costs.

[0075] A metropolitan area network (MAN) is a computer communication network established within a city, referred to as MAN. It is a broadband local area network. Because it uses local area network technology with active switching components, the transmission delay in the network is small. Its transmission medium mainly uses optical cables, and the transmission rate is above 100 megabits per second.

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

[0077] In a possible implementation, the configuration rule includes a boundary name, a boundary type, a starting device of the boundary type, an ending device of the boundary type, a backbone network traffic status, and a link node label.

[0078] Among them, the boundary names include PON-MAN and MAN-CN2, the boundary type of PON-MAN is boundary, 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 SW devices of CN2, the ending devices of the devices include PE and SW devices of CN2, the backbone network access status of PON-MAN is no, the backbone network peer status of MAN-CN2 is yes, the link node label of PON-MAN includes Ethernet link combined hard jump label and single Ethernet link label, and the link node label of MAN-CN2 is single Ethernet link label.

[0079] It should be noted that the configuration rules also include judging the long-term boundary type of network data before splicing, where the long-term boundary refers to the network connection boundary between the local segment (provincial side / prefectural city) and the backbone segment (group side). In the splicing process involving two-level network data (provincial (prefectural city) network data or group network data), the target circuit of splicing is mainly cross-domain circuit (one-trunk and two-trunk circuit). The local segment of the cross-domain circuit is managed by the provincial side, and the backbone segment is managed by the group. The resource data is also stored separately. To form a complete network topology, it is necessary to audit and splice the two-level data. The splicing process needs to be carried out according to certain rules. Specifically, the long-term boundary refers to the boundary of the provincial side and the group side circuit. The long refers to the long distance (backbone segment) and the local refers to the local (segment). It is a telecom internal name for the boundary. There are two types of boundaries. One is the long-term boundary and the other is not the long-term boundary. It belongs to the ordinary network boundary. The ordinary network boundary does not need to be spliced ​​because it does not involve two-level data storage. Whether it is a long-term boundary and whether it passes through the backbone refers to whether this boundary is the provincial and group data boundary. For example, PON-MAN does not belong to the long-term boundary, nor does it belong to the backbone segment. At this time, the rule strategy adopted is spliced ​​according to the boundary. For another example, MAN-CN2 is the long-term boundary and belongs to the backbone network. At this time, the rule strategy is spliced ​​according to the device (Z end).

[0080]

[0081]

[0082] Table 1

[0083] Referring to Table 1, a rule table for storing detailed rule data is shown.

[0084] Among them, ASBR (Autonomous System Border Router) is a router connecting different autonomous systems and is used to transmit routing information between different autonomous systems. When a router is connected to different autonomous systems, it becomes an ASBR. It needs to maintain the topology information and routing table of each autonomous system, and transmit information and exchange routes 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 the performance and reliability of the network.

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

[0087] BAS (Basic Assembler Program, broadband access server) is a user access service device set up at the network aggregation layer. It can intelligently implement 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) equipment is used to connect to the edge equipment of the PTN network.

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

[0090] Specifically, the boundary name refers to the boundary identifier of different areas or layers in the network. The boundary type indicates the nature of the boundary. The start device refers to the starting point device of the boundary or link. The end device refers to the end point device of the link. The backbone network access status refers to whether the network belongs to the backbone network level and has the wide area network data transmission capability. "Yes" means it can pass through the backbone network, and "No" means it cannot pass through the backbone network. The link node label is used to identify the node information in the link, such as the Ethernet link combined with the hard jump label, indicating the attributes and hop count of the specific link.

[0091] In actual application, the purpose of setting these configuration rules is to ensure that the connection and transmission between different levels in the network have clear boundaries and standardization. By defining boundary names, starting devices, ending devices, etc., the responsibilities and functions of different network areas (such as PON, metropolitan area network, and CN2) can be effectively divided to prevent conflicts or errors in data transmission. Configuration rules can also enhance the automation of network operation and maintenance, making it easier to quickly identify problem points. In addition, link node labels can help administrators clearly understand the attributes of each link, such as the number of hops and bandwidth, to achieve efficient network management. Overall, these rules improve the standardization, scalability, and management efficiency of the network architecture, and ensure the reliability of cross-network data transmission.

[0092] S2, classifying the data in the configuration rule into template data, wherein the template data includes node data, relationship data and link data.

[0093] Among them, template data is an abstract collection that standardizes and structures the network information in the configuration rules to facilitate subsequent operations and processing. Templating can uniformly manage and operate different types of network data to ensure consistency. Node data refers to the specific information of each device or entity in the network, such as the attributes and status of routers, switches and other devices. It describes the basic information of each node in the network topology, such as location, function, etc. Relationship data describes the connection and dependency between different nodes in the network and defines the interaction between network devices, such as two routers connected by a link, or the hierarchical structure between devices. Link data refers to the detailed information of the transmission channel between different nodes, including the bandwidth, type, number of hops, and whether it is a physical or virtual link.

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

[0095] In a possible implementation, the node data corresponds to the nodes data in the configuration rules, the relationship data corresponds to the relations data in the configuration rules, and the link data corresponds to the links data in the configuration rules.

[0096] The node data includes nodeLabels which is used to define a list of labels for each object.

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

[0098] The relationship data includes relationType corresponding to the relationship 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 A-end entity label, and z_nodelables corresponding to the Z-end entity label.

[0099] It should be noted that accurate modeling of network topology is achieved by mapping node data, relationship data, and link data to specific data structures in the configuration rules, such as nodes, relations, and links. Each node defines a detailed list of labels, and each relationship contains detailed information about the link, such as device ID, port ID, specification ID, etc. This approach helps to 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 splicing.

[0100] S3, obtain the target user’s pending twin communication network tasks.

[0101] The communication network task to be twinned refers to a specific task submitted by the user that requires digital twin modeling of its communication network. The digital twin is a virtual copy of the physical network. Therefore, the goal of this task is to conduct a comprehensive virtual modeling of the user's communication network so as to simulate, monitor, optimize or troubleshoot the network in a virtual environment, thereby keeping in sync with the actual network and being able to reflect the network status and operation in real time.

[0102] 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.

[0103] Among them, provincial circuit topology data refers to the network topology structure within the provincial scope in the communication network, including network nodes, equipment connections and link information within the area. It is usually responsible for data transmission and processing within the province or region, covering the local network's equipment, links and their relationships.

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

[0105] It should be noted that by retrieving the circuit topology data on the provincial side and the backbone side in the form of template data, standardized processing of multi-level network structures can be achieved, which not only simplifies the integration process of networks at different levels, but also ensures the consistency and integrity of network data. Through this method, the twin modeling of network topology is more accurate, convenient for unified management and maintenance, and helps to fully understand the network structure and optimize it.

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

[0107] It should be noted that by configuring rules, the circuit topology data on the provincial side and the backbone side are pre-splicing checked to ensure the accuracy, completeness and consistency of the data. Verification before splicing can detect data errors or mismatches in advance and avoid splicing 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 a possible implementation, pre-joining verification is performed on provincial-side circuit topology data and backbone-side circuit topology data according to configuration rules, specifically including:

[0109] S501, searching for a starting device according to a query rule.

[0110] In a possible implementation manner, the query rule specifically includes a first query rule, a second query rule, and a third query rule.

[0111] The first query rule is to determine the starting device according to the geographical location and the affiliated office of each device.

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

[0113] The third query rule is to determine the starting device according to the starting end and the ending end of the hat link to which the device belongs.

[0114] It should be noted that the starting device is located in multiple dimensions through geographical location, coverage area and link endpoints to ensure the flexibility and accuracy of device query. It can adapt to the needs of different network environments and topological structures, improve the accuracy and efficiency of device identification, and reduce search errors.

[0115] S502: Find a terminating device corresponding to the starting device based on the serial route of the starting device.

[0116] In a possible implementation manner, S502 specifically includes:

[0117] Determine the serial routing of the starting device.

[0118] The passing route of the starting device is determined according to the serial connection route, and the last passing 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 route and the pass route of the starting device, the data transmission path can be effectively tracked to ensure the precise positioning of the terminating device. This method can handle multi-level connections in complex networks, support the identification of multiple terminating devices, improve the accuracy and efficiency of network topology analysis, and ensure the integrity and visualization of the network structure.

[0120] S503: Determine the terminating device that is the same as the group boundary station among the stations to which each terminating device belongs as the boundary station.

[0121] Specifically, by comparing the station to which each terminating device belongs with the group's border station, those devices whose terminating devices are the same as the group's border station are identified as border devices. Border devices are key nodes that connect different network areas (such as the provincial side and the backbone side), marking the dividing point between different levels of the network. After determining the border devices, it is possible to further ensure that the connection between devices complies with the connection rules, thereby ensuring the correct transmission of data and the stability of the network.

[0122] S504, determining whether the edge device complies with the local device connection rule, if yes, the verification passes, otherwise, the verification fails.

[0123] It should be noted that by querying the starting device in multiple dimensions, tracking the serial route and the terminating device, and comparing the terminating device with the border station, it is ensured that the connection and boundary of the device meet 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, output splicing abnormality reminder, terminate splicing.

[0125] S7, splicing 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.

[0126] S8, delegate the twin topology data to the target user.

[0127] In actual use, the communication network twin method generates a complete network twin model by initializing network configuration rules, extracting provincial and backbone topology data, and performing data verification and splicing. 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 realizes comprehensive management and automated operation and maintenance of cross-level networks.

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

[0129] In an embodiment of the present invention, the configuration rules between the CN2 bearer network and the PON network and the metropolitan area network are first initialized, and then the data appearing in the configuration rules are uniformly classified as template data to provide a data basis for the automatic completion of the communication network twin. After that, data is extracted for the twin communication network task in combination with the template data, and the extracted data is automatically twinned in combination with the configuration rules. In the twinning process, the configuration rules are used for pre-splicing verification, and only the equipment that passes the verification is spliced. The equipment splicing can be automatically performed in a templated manner in a self-supervising manner, which can effectively reduce manual intervention, improve the efficiency and accuracy of the communication network twin, and can effectively cope with the rapid growth of communication network nodes, greatly improve the standardization and accuracy of the communication network topology, improve the satisfaction of target users, and increase corporate competitiveness.

[0130] Device Embodiment

[0131] Reference Manual Attached Figure 2 , showing a schematic diagram of the structure 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, which is used to implement any one of the communication network twin methods in the method embodiments. The communication network twin device 20 includes:

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

[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 obtain the target user's pending twin communication network tasks.

[0136] The retrieving module 204 is used to retrieve the provincial side circuit topology data and the 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 a 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 passes, the splicing module is called, otherwise, the output module is called.

[0138] The output module 206 is used to output a splicing abnormality reminder and terminate the 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.

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

[0141] In a possible implementation, the configuration rules include a boundary name, a boundary type, a starting device of the boundary type, an ending device of the boundary type, a backbone network traffic status, and a link node label, wherein the boundary name includes PON-metropolitan area network and metropolitan area network-CN2, the boundary type of PON-metropolitan area network is boundary, the boundary type of metropolitan area network-CN2 is device, the starting device of the boundary includes OLT device, metropolitan area network ASBR device, metropolitan area network SW device and device, the starting device of the device includes metropolitan area network ASBR device, metropolitan area network SW device and device, the ending device of the boundary includes metropolitan area network SW device, MSE device, metropolitan area network ASBR device, metropolitan area network BAS device, PE and CN2 SW device, the ending device of the device includes PE and CN2 SW device, the backbone network traffic status of PON-metropolitan area network is no, the backbone network peer status of metropolitan area network-CN2 is yes, the link node label of PON-metropolitan area network includes Ethernet link combined hard jump label and single Ethernet link label, and the link node label of metropolitan area network-CN2 is a single Ethernet link label.

[0142] In a possible implementation, the node data corresponds to the nodes data in the configuration rules, the relationship data corresponds to the relations data in the configuration rules, and the link data corresponds to the links data in the configuration rules.

[0143] The node data includes nodeLabels which is used to define a list of labels for each object.

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

[0145] The relationship data includes relationType corresponding to the relationship 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 A-end entity label, and z_nodelables corresponding to the Z-end entity label.

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

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

[0148] The terminating device corresponding to the starting device is found based on the serial route of the starting device.

[0149] The termination devices in the stations to which each termination device belongs that are identical to the group's boundary stations are determined as boundary devices.

[0150] Determine whether the boundary device complies with the local device connection rules. If yes, the verification passes; otherwise, the verification fails.

[0151] In a possible implementation manner, the query rule specifically includes a first query rule, a second query rule, and a third query rule.

[0152] The first query rule is to determine the starting device according to the geographical location and the affiliated office of each device.

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

[0154] The third query rule is to determine the starting device according to the starting end and the ending end of the hat link to which the device belongs.

[0155] In a possible implementation, searching for a terminating device corresponding to the starting device based on the serial route of the starting device is specifically as follows:

[0156] Determine the serial routing of the starting device.

[0157] The passing route of the starting device is determined according to the serial connection route, and the last passing route is determined as the terminating device, wherein there is at least one terminating device.

[0158] The device provided in the embodiment of the present invention can implement each process and step in the above method embodiment, and can obtain the same or similar technical effects. To avoid repetition, the present invention will not go into details.

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

[0160] In an embodiment of the present invention, the configuration rules between the CN2 bearer network and the PON network and the metropolitan area network are first initialized, and then the data appearing in the configuration rules are uniformly classified as template data to provide a data basis for the automatic completion of the communication network twin. After that, data is extracted for the twin communication network task in combination with the template data, and the extracted data is automatically twinned in combination with the configuration rules. In the twinning process, the configuration rules are used for pre-splicing verification, and only the equipment that passes the verification is spliced. The equipment splicing can be automatically performed in a templated manner in a self-supervising manner, which can effectively reduce manual intervention, improve the efficiency and accuracy of the communication network twin, and can effectively cope with the rapid growth of communication network nodes, greatly improve the standardization and accuracy of the communication network topology, improve the satisfaction of target users, and increase corporate competitiveness.

[0161] The applicant of the present invention has made a detailed explanation and description of the implementation examples of the present invention in conjunction with the drawings in the specification. However, those skilled in the art should understand that the above implementation examples are only preferred implementation schemes of the present invention, and the detailed description is only to help readers better understand the spirit of the present invention, but not to limit the scope of protection of the present invention. On the contrary, any improvements or modifications based on the inventive spirit of the present invention should fall within the scope of protection of the present 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, rather than to limit them. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions recorded in the above embodiments, or replace some of the technical features therein by equivalents; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention. Any changes or replacements that can be easily thought of by those skilled in the art within the technical scope disclosed in the present invention should be covered within the protection scope of the present invention.

Claims

1. A communication network twin method, characterized in that: The communication network twin method comprises: S1, respectively initialize the configuration rules between the CN2 bearer network and the PON network and the metropolitan area network; S2, classifying the data in the configuration rule as template data, wherein the template data includes node data, relationship data and link data; S3, obtain the target user’s pending twin communication network tasks; S4, retrieving the provincial side circuit topology data and the backbone side circuit topology data of the twin communication network task in the form of the template data; S5, performing a pre-splicing check on the provincial-side circuit topology data and the backbone-side circuit topology data according to the configuration rule, if the check passes, proceeding to step S7, otherwise, proceeding to step S6; S6, output splicing abnormality reminder and terminate splicing; S7, splicing 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; S8, transferring the twin topology data to the target user.

2. The communication network twin method according to claim 1, characterized in that: The configuration rules include a boundary name, a boundary type, a starting device of the boundary type, an ending device of the boundary type, a backbone network traffic status, 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 boundary, the boundary type of the metropolitan area network-CN2 is device, the starting device of the boundary includes OLT device, metropolitan area network ASBR device, metropolitan area network SW device and device, the starting device of the device includes metropolitan area network ASBR device, metropolitan area network SW device and device, The end devices of the boundary include metropolitan area network SW devices, MSE devices, metropolitan area network ASBR devices, metropolitan area network BAS devices, PE and CN2 SW devices, the end devices of the devices include PE and CN2 SW devices, the backbone network access status of the PON-metropolitan area network is no, the backbone network peer status of the metropolitan area network-CN2 is yes, the link node label of the PON-metropolitan area network includes an Ethernet link combined with a 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.

3. The communication network twin method according to claim 1, characterized in that: 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 the link specification name, gid corresponding to Gid, name corresponding to the name, code corresponding to the code, spec_id corresponding to the specification id, a_port_id corresponding to the A-end port ID, a_device_id corresponding to the A-end physical device ID and the A-end logical device ID, z_port_id corresponding to the Z-end port ID, z_device_id corresponding to the Z-end physical device ID and the Z-end logical device ID, using_state_id corresponding to the service state, nextPage corresponding to the next page state, and extended attributes; 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.

4. The communication network twin method according to claim 1, characterized in that: The performing a pre-splicing check on the provincial-side circuit topology data and the backbone-side circuit topology data according to the configuration rule specifically includes: S501, searching for a starting device according to a query rule; S502, searching for a terminating device corresponding to the initiating device based on the serial route of the initiating device; S503, determining the terminating device that is the same as the group boundary station in the station to which each terminating device belongs as the boundary device; S504, determining whether the edge device complies with the local device connection rule, if yes, the verification passes, otherwise, the verification fails.

5. The communication network twin method according to claim 4, characterized in that: The query rules specifically include 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 the geographical location and the affiliated office of each device; The second query rule is to determine the starting device according to the coverage area of ​​each device; The third query rule is to determine the starting device according to the starting end and the ending end of the hat link to which the device belongs.

6. The communication network twin method according to claim 4, characterized in that: The S502 is specifically as follows: Determining a serial connection route of the starting device; The passing route of the starting device is determined according to the serial route, and the last passing route is determined as the terminating device, wherein the number of the terminating device is at least one.

7. A communication network twin device, characterized in that: The communication network twin device comprises: An initialization module, used to respectively initialize the configuration rules between the CN2 bearer network and the PON network and the metropolitan area network; A classification module, used to classify the data in the configuration rule into template data, wherein the template data includes node data, relationship data and link data; An acquisition module is used to obtain the target user's pending twin communication network tasks; A calling module, used to call the provincial side circuit topology data and the backbone side circuit topology data of the twin communication network task in the form of the template data; A verification module, used for performing a pre-splicing verification on the provincial-side circuit topology data and the backbone-side circuit topology data according to the configuration rule, and if the verification passes, calling the splicing module, otherwise, calling the output module; Output module, used to output splicing abnormality reminder and terminate splicing; A splicing module, used for splicing 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; A decentralization module is used to decentralize the twin topology data to the target user.

8. The communication network twin device according to claim 7, characterized in that: The configuration rules include a boundary name, a boundary type, a starting device of the boundary type, an ending device of the boundary type, a backbone network traffic status, 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 boundary, the boundary type of the metropolitan area network-CN2 is device, the starting device of the boundary includes OLT device, metropolitan area network ASBR device, metropolitan area network SW device and device, the starting device of the device includes metropolitan area network ASBR device, metropolitan area network SW device and device, The end devices of the boundary include metropolitan area network SW devices, MSE devices, metropolitan area network ASBR devices, metropolitan area network BAS devices, PE and CN2 SW devices, the end devices of the devices include PE and CN2 SW devices, the backbone network access status of the PON-metropolitan area network is no, the backbone network peer status of the metropolitan area network-CN2 is yes, the link node label of the PON-metropolitan area network includes an Ethernet link combined with a 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 device according to claim 7, characterized in that: 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 the link specification name, gid corresponding to Gid, name corresponding to the name, code corresponding to the code, spec_id corresponding to the specification id, a_port_id corresponding to the A-end port ID, a_device_id corresponding to the A-end physical device ID and the A-end logical device ID, z_port_id corresponding to the Z-end port ID, z_device_id corresponding to the Z-end physical device ID and the Z-end logical device ID, using_state_id corresponding to the service state, nextPage corresponding to the next page state, and extended attributes; 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 device according to claim 7, characterized in that: The performing a pre-splicing check on the provincial-side circuit topology data and the backbone-side circuit topology data according to the configuration rule specifically includes: Find the starting device according to the query rules; Finding a terminating device corresponding to the starting device based on the serial route of the starting device; The terminating equipment in the bureaus and stations to which each terminating equipment belongs that is the same as the group's boundary bureau and station is determined as the boundary equipment; It is determined whether the edge device complies with the local device connection rule. If so, the verification passes; otherwise, the verification fails.

Images