Cross-domain network topology generation method and device

Abstract

The invention discloses a cross-domain network topology generation method and a cross-domain network topology generation device, which are used for restoring a cross-domain network topology. The method comprises the following steps: determining an alarm type of each network port according to alarm data of each network port in a plurality of network ports in a plurality of network domains; wherein the plurality of network domains comprise a wavelength division network domain and a digital communication network domain, and the alarm type of each network port is used for representing the property of the alarm generated by each network port; determining at least one group of network port pairs with a cross-domain association relationship among the plurality of network ports according to the alarm types of the plurality of network ports; wherein any group of network port pair comprises two network ports from different network domains, and the alarm types of the two network ports have a causal relationship; and generating a cross-domain network topology according to the at least one group of network port pairs. Therefore, at least one group of network port pairs with the cross-domain association relationship can be determined according to the alarm data, so that the cross-domain network topology can be restored.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method and apparatus for generating cross-domain network topology. Background Technology

[0002] Network topology restoration, also known as network connectivity restoration, refers to the technique of logically connecting network element ports to other network elements according to their physical configuration information, whether it's a subset or all of them. It's essential for viewing transmission links, analyzing service quality, and locating network faults in communication networks. Network topology restoration is widely used in network management systems (NMS) of telecommunications operators, element management systems (EMS) of equipment manufacturers, and operation support systems (OSS) of third-party service providers.

[0003] In existing technologies, network topology reconstruction primarily relies on communication messages exchanged between network elements in an operator's asset management system to determine the inputs and outputs of interconnected network devices and generate the network topology. However, when two or more different network domains are involved, the operator's asset management system cannot obtain the communication messages exchanged between network elements in the two different network domains. Therefore, the aforementioned network topology reconstruction techniques are inadequate for generating cross-domain (including two or more network domains) network topology reconstruction scenarios. Therefore, a cross-domain network topology generation method is urgently needed. Summary of the Invention

[0004] This application provides a method and apparatus for generating cross-domain network topology, used to generate network topology between different network domains.

[0005] In a first aspect, embodiments of this application provide a method for generating cross-domain network topology, which can be executed by an electronic device, and the method includes:

[0006] The electronic device determines the alarm type of each network port based on the alarm data of each network port located in multiple network domains. These multiple network domains include wavelength division multiplexing (WDM) network domains and data communication network domains. The alarm type of each network port is used to characterize the nature of the alarm generated by each network port. The electronic device can also determine at least one pair of network ports with cross-domain relationships among the multiple network ports based on the alarm types. Each pair of network ports contains two network ports from different network domains whose alarm types have a causal relationship. The electronic device can generate a cross-domain network topology based on at least one pair of network ports.

[0007] In this method, electronic devices can perform cross-domain correlation analysis on every two network ports from different network domains based on alarm data of network ports in different network domains, and form network port pairs with alarm types that have a causal relationship. Thus, cross-domain network topology can be generated based on at least one network port pair, without having to determine the cross-domain correlation between network ports through communication messages between network ports, thereby improving the reconstruction rate of cross-domain network topology.

[0008] In one possible design, the following steps are performed on a first network port among multiple network ports: the electronic device can match the alarm type of the first network port with the alarm type of at least one candidate network port among the multiple network ports; when there is at least one target network port among the at least one candidate network port whose alarm type matches the alarm type of the first network port, the electronic device can generate at least one set of first network port pairs based on the first network port and at least one target network port; wherein, the first network port is any network port among the multiple network ports, and the network domain of the at least one candidate network port is different from the network domain of the first network port; any first network port pair includes a first network port and a target network port, and the alarm type of at least one target network port has a causal relationship with the alarm type of the first network port; at least one set of network port pairs contains at least one set of first network port pairs.

[0009] Through this design, the electronic device can match the alarm type of the first network port with the alarm type of at least one candidate network port, and determine at least one target network port from the at least one candidate network port whose alarm type has a causal relationship with the alarm type of the first network port. In this way, at least one pair of first network ports with cross-domain association can be accurately obtained, and then the cross-domain network topology can be restored based on the network port pairs with cross-domain association, ensuring the restoration rate of the cross-domain network topology.

[0010] In one possible design, the time interval between alarm data generation for any target network port that matches the alarm type of the first network port is less than or equal to a time threshold.

[0011] This design allows electronic devices to avoid pairing two network ports that match alarm types but have excessively large alarm data generation intervals. This ensures the accuracy of identifying at least one set of network port pairs from multiple network ports, thereby guaranteeing the accuracy of subsequent cross-domain network topology reconstruction based on at least one set of network port pairs.

[0012] In one possible design, the electronic device can match the alarm type of a first network port with the alarm type of at least one candidate network port from a plurality of network ports according to a preset alarm matching rule; wherein the alarm matching rule is used to indicate multiple sets of alarm types with causal relationship.

[0013] With this design, the electronic device can accurately determine the candidate network port that matches the alarm type of the first network port from at least one candidate network port according to the preset alarm matching rules, thereby improving the accuracy of the obtained at least one pair of first network ports.

[0014] In one possible design, each network port has at least one alarm data point; the electronic device can determine at least one alarm type for each network port based on the at least one alarm data point for each network port; at least one alarm type of any target network port matches at least one alarm type of a first network port; the electronic device can also generate a network port relationship graph based on at least one set of network port pairs; wherein the network port relationship graph contains at least one link, each link being used to connect two network ports contained in a set of network port pairs; the electronic device can determine the confidence rate of each link based on the alarm type matching of the two network ports connected by each link in the network port relationship graph; the electronic device can also generate a cross-domain network topology based on the confidence rate of each link and the network port relationship graph.

[0015] This design allows electronic devices to determine the confidence rate of each link based on the alarm type matching of the two network ports connected by each link in the network port relationship diagram. Based on the confidence rate of each link and the network port relationship diagram, a cross-domain network topology can be generated without manually determining the confidence rate of the link connecting network ports of two different network domains. This reduces manual workload and improves the accuracy of cross-domain network topology reconstruction.

[0016] In one possible design, for a first link in the network port relationship graph, the following steps are performed: the electronic device can use the number of alarm types that match between the second network port and the third network port as a first quantity; wherein, the first link is used to connect the second network port and the third network port, and the first link is any link in the network port relationship graph; the electronic device can also use the number of alarm types that match between the second network port and at least one fourth network port as a second quantity; wherein, the network domain where the second network port is located is a first network domain set among multiple network domains; at least one fourth network port is a network port that matches the alarm type of the second network port; the electronic device can use the ratio of the first quantity to the second quantity as the confidence rate of the first link.

[0017] With this design, the electronic device can use the ratio of the number of alarm types matched between the second network port and the third network port to the number of alarm types matched between the second network port and at least one fourth network port as the confidence rate of the first link connecting the second network port and the third network port, thus ensuring the accuracy of the confidence rate of the first link.

[0018] In one possible design, the electronic device can also determine that the link with the highest current confidence rate in the network port relationship graph is a cross-domain link, and clear the links between the two network ports connected by the cross-domain link in the network port relationship graph; repeat the above steps until all links in the network port relationship graph are cleared; and generate a cross-domain network topology based on at least one cross-domain link determined in the network port relationship graph.

[0019] Through this design, the electronic device can identify the link with the highest confidence rate in the network port relationship graph as a cross-domain link, and clear the links that the two network ports connected by the cross-domain link in the network port relationship graph have, and the cleared links include cross-domain links. By repeating the above operation, the accuracy of the cross-domain network topology restoration generated based on at least one cross-domain link can be guaranteed.

[0020] In one possible design, multiple network ports are located within the same physical area.

[0021] Secondly, embodiments of this application also provide a cross-domain network topology generation apparatus, which includes modules or units for implementing the method described in the first aspect and any possible design of the first aspect.

[0022] Thirdly, embodiments of this application also provide a cross-domain network topology generation apparatus, comprising: a processor and a communication interface. The communication interface is used to receive signals from other devices outside the cross-domain network topology generation apparatus and transmit them to the processor, or to send signals from the processor to other devices outside the cross-domain network topology generation apparatus. The processor executes code instructions through logic circuits to implement the method described in the first aspect and any possible design of the first aspect. Optionally, the cross-domain network topology generation apparatus may further include a memory coupled to the processor, which stores program instructions and data necessary for the apparatus.

[0023] Fourthly, embodiments of this application provide a chip system, including: a processor coupled to a memory, the memory being used to store programs or instructions, which, when executed by the processor, cause the chip system to implement the methods described in the first aspect or any possible design of the first aspect.

[0024] Optionally, the chip system also includes an interface circuit for exchanging code instructions with the processor.

[0025] Optionally, the chip system may include one or more processors, which can be implemented in hardware or software. When implemented in hardware, the processor may be a logic circuit, integrated circuit, etc. When implemented in software, the processor may be a general-purpose processor that reads software code stored in memory.

[0026] Optionally, the chip system may contain one or more memories. These memories may be integrated with the processor or separated from it; this application does not limit this. For example, the memory may be a non-transient processor, such as read-only memory (ROM), which may be integrated with the processor on the same chip or disposed on different chips. This application does not specifically limit the type of memory or the arrangement of the memory and processor.

[0027] Fifthly, embodiments of this application provide a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed, causes a computer to perform the method described in the first aspect or any possible design of the first aspect.

[0028] In a sixth aspect, embodiments of this application provide a computer program product that, when read and executed by a computer, causes the computer to perform the method described in the first aspect or any possible design of the first aspect.

[0029] For details of the beneficial effects of aspects two through six above, please refer to the technical effects that can be achieved by the corresponding design in aspect one above, which will not be repeated here. Attached Figure Description

[0030] Figure 1 This application provides an exemplary schematic diagram illustrating an application scenario suitable for a cross-domain network topology generation method.

[0031] Figure 2 A schematic diagram of a display screen for an electronic device provided in an embodiment of this application;

[0032] Figure 3 A user interface diagram provided for an embodiment of this application;

[0033] Figure 4 Another user interface diagram provided for an embodiment of this application;

[0034] Figure 5This application provides a schematic diagram of a cross-domain network topology restoration process.

[0035] Figure 6A A schematic diagram of a network port relationship provided in an embodiment of this application;

[0036] Figure 6B A schematic diagram of another network port relationship provided in an embodiment of this application;

[0037] Figure 7 A schematic diagram of yet another network port relationship diagram provided for an embodiment of this application;

[0038] Figure 8 This application provides a schematic diagram of a cross-domain network topology.

[0039] Figure 9A A flowchart illustrating a cross-domain network topology generation method provided in this application embodiment;

[0040] Figure 9B A schematic diagram of the interaction process of a cross-domain network topology generation method provided in an embodiment of this application;

[0041] Figure 10 A schematic diagram of a cross-domain network topology generation device provided in an embodiment of this application;

[0042] Figure 11 This is a schematic diagram of another cross-domain network topology generation device provided in an embodiment of this application. Detailed Implementation

[0043] The technical solutions in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0044] First, the concepts related to the embodiments of this application will be explained.

[0045] (1) A site refers to a group of physical servers that are physically located within the same physical area.

[0046] (2) A network element, also known as a network unit, refers to the basic unit that constitutes a communication network and is responsible for completing various communication tasks. A network element can include hardware devices and software running on the hardware devices. It is a device or software entity with specific functions and independent operating capabilities in a communication network. Usually, a network unit has at least one main control board, which is responsible for the management and monitoring of the entire network unit. Among them, a network element contains multiple network ports, and the network element communicates with other network elements through the network ports.

[0047] (3) A network port refers to the communication port of a network or a network device, through which signals can be inserted or extracted. In a communication system, signals can be routed from one network to another through a network port. Network devices include, but are not limited to, routers, switches, firewalls, gateways, network interface cards (NICs), wireless access points (APs), modems, hubs, and fiber optic transceivers.

[0048] (4) Cross-domain linking refers to communication between network elements belonging to different network domains within a single site. In the embodiments of this application, a site may contain multiple network elements, each belonging to a specific network domain (e.g., wavelength division multiplexing network domain, data communication network domain, etc.).

[0049] (5) Alarm data refers to the information generated when network devices or network systems poll and detect faults.

[0050] (6) Network topology restoration, also known as network connectivity restoration, refers to the technology of logically connecting network ports to network ports according to their physical configuration information for some or all network elements in the network. It is an essential part of communication networks for viewing the transmission links of network objects, analyzing service quality, and locating network faults.

[0051] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0052] Furthermore, unless otherwise stated, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the size, content, order, timing, priority, or importance of multiple objects. For example, "second file" and "second file" are only used to distinguish different files and do not indicate that the two files are different in size, content, priority, or importance.

[0053] Currently, network topology reconstruction technology mainly relies on communication messages exchanged between network elements in the operator's asset management system to determine the inputs and outputs of the ports of interconnected network devices and generate the network topology. However, when two or more different network domains are involved, the operator's asset management system cannot obtain the communication messages exchanged between network elements in the two different network domains. Therefore, the above-mentioned network topology reconstruction technology is inadequate for generating cross-domain (including two or more network domains) network topology reconstruction scenarios. Therefore, a cross-domain network topology generation method is urgently needed.

[0054] In view of this, embodiments of this application provide a method and apparatus for generating cross-domain network topology, used to reconstruct cross-domain network topology. The method and apparatus are based on the same technical concept. Since the principles by which the method and apparatus solve the problem are similar, the implementation of the apparatus and method can be referred to mutually, and repeated details will not be repeated. Furthermore, in the various embodiments of this application, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the various embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0055] The solution provided in this application will now be described in conjunction with the accompanying drawings and specific embodiments.

[0056] Figure 1 This diagram illustrates an application scenario for the cross-domain network topology generation method provided in this embodiment of the application. Figure 1 As shown, in this application scenario, it may include an electronic device 100 and a database 200. The electronic device 100 and the database 200 can communicate via a network, and the database 200 is used to store network topology data. The network topology data can be a network topology diagram or a set of links corresponding to the network topology. The electronic device 100 can be a server or a terminal device, and is not limited thereto. In this embodiment, Figure 1 The functions implemented by the electronic device 100 in the application scenario shown can also be implemented by a cross-domain network topology device, and are not limited to this.

[0057] The cross-domain network topology generation method of this application embodiment can be implemented by a topology restoration module in the electronic device 100. This topology restoration module can be an independent device or a... Figure 1 The chip or component in the illustrated electronic device 100 can also be a software module (e.g., an application program). This software module can be deployed on the operating system of the electronic device 100. This application embodiment does not limit the product form or deployment method of the topology restoration module.

[0058] In this embodiment, the topology restoration module may be the cross-domain link analysis platform of the operating system of the electronic device 100.

[0059] The electronic device 100 may include at least one display screen. The topology restoration module may implement the cross-domain network topology generation method of the embodiments of this application, and may also display the cross-domain network topology generation process and the generated cross-domain network topology on any of the at least one display screen to notify the user of the cross-domain network topology generation process.

[0060] In some embodiments, the topology restoration module is a separate device within the electronic device 100. For example... Figure 2 As shown, a first application (APP) can be installed and run on the operating system of the topology restoration module. This first application is used to implement the network topology restoration function. The topology restoration module can display the icon of the installed first application on the display screen of the associated electronic device 100. In addition, while the first application is running, the topology restoration module can display the user interface of the first application on the display screen of the electronic device 100.

[0061] When a user needs to restore the network topology under a business scenario (e.g., a real business scenario), the topology restoration module can respond to the user's activation of the first application icon on the display screen of the electronic device 100, launching and running the first application. The business scenario can be an IP-plus-optical scenario, or other business scenarios involving network elements under multiple network domains. In an IP-plus-optical scenario, the network elements belong to both wavelength division multiplexing (WDM) network domains and data communication network domains. For example, a WDM network domain may include, but is not limited to, an optical transport network (OTN). A data communication network domain may include, but is not limited to, a packet transport network (PTN). In this embodiment, the business scenario for cross-domain network topology restoration includes one or more sites, each of which includes multiple network elements under different network domains, and each network element includes one or more network ports. That is, each site can contain at least one network port from multiple network domains within the same physical range. For example, when the business scenario is an IP-plus-optical scenario, this business scenario includes one site.

[0062] The topology restoration module can obtain network port alarm data for a given business scenario through the first application. Specifically, when the business scenario includes one site, the topology restoration module obtains alarm data for the network ports within that site. When the business scenario includes multiple sites, the topology restoration module obtains alarm data for the network ports across all sites.

[0063] The alarm data for any network port includes, but is not limited to, location information, alarm location information, alarm first occurrence time, network type, alarm type, alarm body, and device type. Location information indicates the site that generated the alarm; alarm location information indicates the network port that generated the alarm; alarm first occurrence time indicates the time when the network port first generated the alarm; and network type indicates the network domain information of the network port that generated the alarm. For example, the alarm type can be REMOTE_FAULT, LOCAL_FAULT, or other alarm types, without limitation. REMOTE_FAULT indicates a problem or fault in the peer link, causing the local device to be unable to establish a link connection normally. LOCAL_FAULT indicates a partial fault or local fault. For example, part of the alarm data obtained by the topology restoration module can be shown in Table 1 below:

[0064] Table 1: Partial Contents of Alarm Data

[0065]

[0066] As an example, the topology restoration module can respond to user input in the user interface of the first application and determine the business scenario requiring network topology restoration. The topology restoration module can retrieve alarm data from the alarm database for this business scenario. The alarm database stores alarm data and allows users to query and download it. In this business scenario, the alarm database can be stored on a local server, a remote server, or cloud storage. Furthermore, the alarm database can be... Figure 1 Database 200 can be any other database. For example, the topology restoration module can identify network elements in a business scenario and retrieve alarm data for those network elements within a set time period from the alarm database. For instance, if the business scenario includes network elements 1, 2, 3, and 4, and the set time period is the past month, the topology restoration module can retrieve alarm data for network elements 1, 2, 3, and 4 from the alarm database for the past month.

[0067] For example, such as Figure 3As shown, when a user wants to restore the cross-domain network topology in an IP plus optical scenario, the topology restoration module can launch a first application and display the user interface 300a of the first application on the display screen of the electronic device 100. The user interface 300a includes at least a "Cross-domain Network Topology Restoration" control 301 and a "Business Scenario" control 302. The "Cross-domain Network Topology Restoration" control 301 prompts the user to restore the cross-domain network topology corresponding to the business scenario, and the "Business Scenario" control 302 prompts the user to input the business scenario for which cross-domain network topology restoration is required. In response to the user's operation on the "Business Scenario" control 302, the topology restoration module displays the user interface 300b. The user interface 300b includes at least a "Business Scenario Type" menu option 303. In response to the user's operation on the "Business Scenario Type" menu option 303, the topology restoration module displays the user interface 300c. The user interface 300c includes at least a "Selectable Business Scenario" menu option 304, which displays Business Scenario 1 and Business Scenario 2. The topology restoration module responds to user actions on the "Optional Business Scenarios" menu option 304. For example, if the user selects business scenario 1 displayed on the "Optional Business Scenarios" menu option 304, the topology restoration module displays the user interface 300d. The user interface 300d includes at least a "Cross-Domain Network Topology Restoration" control 301. Responding to actions on the "Cross-Domain Network Topology Restoration" control 301, the topology restoration module determines that the business scenario requiring cross-domain network topology restoration is business scenario 1. The topology restoration module can identify the network elements under business scenario 1 and retrieve the alarm data of these network elements from the alarm database.

[0068] As another example, the topology restoration module can also receive alarm files uploaded by users. These alarm files contain alarm data for network elements in business scenarios requiring cross-domain network topology restoration. For instance, the topology restoration module can receive alarm files in response to a user's upload operation in the user interface of the first application.

[0069] For example, such as Figure 4As shown, when a user wants to restore the cross-domain network topology in an IP plus optical scenario, the topology restoration module can launch a first application and display the user interface 400a of the first application on the display screen of the electronic device 100. The user interface 400a includes at least a "Cross-domain Network Topology Restoration" control 401 and an "Upload Alarm File" control 402. The "Cross-domain Network Topology Restoration" control 401 prompts the user to restore the cross-domain network topology corresponding to the alarm file, while the "Get Alarm File" control 402 prompts the user to input the alarm file for the business scenario requiring cross-domain network topology restoration. In response to the user's operation on the "Upload Alarm File" control 402, the topology restoration module displays the user interface 400b. The user interface 400b includes at least a "File Source" menu option 403. In response to the user's operation on the "File Source" menu option 403, the topology restoration module displays the user interface 400c. The user interface 400c includes at least a "Optional File" menu option 404, which displays alarm file 1 and alarm file 2. The topology restoration module responds to the user's operation on the "Optional Files" menu option 404. For example, if the user selects alarm file 1 displayed on the "Optional Files" menu option 404, the topology restoration module displays the user interface 400d.

[0070] For example, when a business scenario includes one site, the topology restoration module can obtain the cross-domain link relationships of that site within the business scenario. As another example, when a business scenario includes multiple sites, the topology restoration module can obtain the cross-domain link relationships of each of the multiple sites within the business scenario.

[0071] Since cross-domain network topology refers to the link relationships between network ports in different network domains within a single site, each site corresponds to a separate cross-domain network topology map. In this case, after obtaining alarm data from a business scenario, the topology restoration module needs to parse and segment the alarm data to obtain the alarm data for one or more sites within that scenario. For example, the topology restoration module can segment the alarm data based on its location information to obtain the alarm data for one or more sites. Thus, the topology restoration module can perform cross-domain network topology restoration for each site based on the alarm data of each of the one or more sites, obtaining the cross-domain network topology for each site. For example, as... Figure 5 As shown, the topology restoration module can restore the cross-domain network topology of the first site through the following steps. Here, the first site can be any one of one or more sites.

[0072] S501: The topology restoration module determines the alarm type of each network port based on the alarm data of each network port in multiple network ports located in multiple network domains.

[0073] The network includes multiple network domains, such as wavelength division multiplexing (WDM) network domain and data communication network domain. The alarm type for each network port is used to characterize the nature of the alarm generated by each network port. The first site contains multiple network ports, meaning that multiple network ports are within the same physical range.

[0074] In some embodiments, after obtaining the alarm data of the first site, the topology restoration module can parse the alarm data of the first site to obtain the alarm data of each of the multiple network ports within the first site. The topology restoration module can also determine the alarm type of each network port based on the alarm data of each network port. Each network port has at least one alarm data. For example, the topology restoration module can also determine at least one alarm type of each network port based on at least one alarm data.

[0075] S502: The topology restoration module determines at least one pair of network ports with cross-domain relationships among multiple network ports based on the alarm types of multiple network ports.

[0076] Each network port pair contains two network ports from different network domains whose alarm types are causally related.

[0077] After obtaining the alarm type of each network port from multiple network ports, the topology restoration module can match the alarm types of network ports in different network domains to obtain at least one set of network port pairs. For example, the topology restoration module can match the alarm types of network ports in different network domains according to preset alarm matching rules, preset alarm type mapping relationships, or other methods, which are not limited here. The alarm matching rules are used to indicate multiple sets of alarm types with causal relationships, and the alarm type mapping relationships are used to indicate multiple sets of alarm types with causal relationships.

[0078] In this embodiment, the alarm matching rules can be pre-configured by the user in the topology restoration module, uploaded by the user simultaneously with the alarm file, or set by the user in the user interface of the first application of the topology restoration module. The alarm matching rules can be multiple sets of alarm types constructed by the user based on business processes, representing causal relationships between interconnected network ports belonging to two different network domains.

[0079] For example, when a trunk fiber optic failure occurs in an OTN and PTN service scenario, the OTN line-side network port experiences a loss of receive line-side signal (e.g., receiver line of signal, R_LOS). The corresponding tributary network port on the OTN line side reports a LOCAL_FAULT alarm to the PTN, and the PTN reports a REMOTE_FAULT alarm back. In this case, there is a causal relationship between the REMOTE_FAULT alarm type of the OTN-side network port and the LOCAL_FAULT alarm type of the PTN-side network port. As another example, when a trunk fiber optic failure occurs in an OTN and PTN service scenario, the OTN near-end and far-end tributary sides shut down the lasers and report an alarm type of automatic laser shutdown active (e.g., automatic laser shutdown active, ALS_ACTIVE). At this time, the PTN network port connected to the OTN reports a LOS. In this case, there is a causal relationship between the ALS_ACTIVE alarm type of the OTN-side network port and the Ethernet port connection loss alarm type R_LOS of the PTN-side network port.

[0080] For example, when a fiber optic cable failure occurs in an OTN and PTN service scenario, the network port on the near-end tributary of the OTN reports R_LOS (fiber breakage) or LOCAL_FAULT. The far-end tributary of the OTN reports REM_SF (remote signal failure alarm) and simultaneously inserts LOCAL_FAULT into the PTN, while the PTN inserts REMOTE_FAULT back. In this case, there is a causal relationship between the alarm type REM_SF / REMOTE_FAULT on the OTN side and the alarm type LOCAL_FAULT on the PTN side. As another example, when a fiber optic cable failure occurs in an OTN and PTN service scenario, the near-end and far-end tributaries of the OTN shut down the laser and report an alarm type ALS_ACTIVE. At this time, the network port of the PTN connected to the OTN reports LOS. In this case, there is a causal relationship between the alarm type ALS_ACTIVE on the OTN side and the alarm types ETH_LOS / R_LOS on the PTN side.

[0081] Based on the above, for example, the multiple sets of alarm types with causal relationships included in the alarm matching rules can be shown in Table 2 below:

[0082] Table 2: Alarm Matching Rules

[0083]

[0084] In this model, there is a causal relationship between the OTN tributary alarm types and the PTN alarm types in each row. If there is a cross-domain link between network ports in two different network domains, then both network ports will inevitably experience two corresponding alarm types simultaneously. That is, when there is a cross-domain link between network port A belonging to OTN and network port B belonging to PTN, then when network port B experiences a local network failure (alarm type LOCAL_FAULT), network port A will simultaneously experience a remote network failure (alarm type REMOTE_FAULT). In this way, the topology restoration module can determine at least one pair of network ports with cross-domain associations among multiple network ports according to preset alarm matching rules.

[0085] For example, the topology restoration module can determine at least one set of network port pairs in the following way. The topology restoration module can perform the following steps for the first network port among a plurality of network ports:

[0086] A1: The topology restoration module can match the alarm type of the first network port with the alarm type of at least one candidate network port among multiple network ports.

[0087] The first network port can be any one of multiple network ports, and at least one candidate network port is located in a different network domain than the first network port. For example, the network domain of the first network port is OTN, and the network domain of at least one candidate network port is PTN.

[0088] As an example, the topology restoration module can match the alarm type of the first network port with the alarm type of at least one candidate network port among multiple network ports according to preset alarm matching rules.

[0089] A2: When at least one candidate network port has an alarm type that matches the alarm type of the first network port, the topology restoration module can generate at least one set of first network port pairs based on the first network port and at least one target network port.

[0090] Each first network port pair includes a first network port and a target network port, and the alarm type of at least one target network port is causally related to the alarm type of the first network port; at least one set of network port pairs includes at least one set of first network port pairs. Optionally, the alarm data generation time interval for any target network port matching the alarm type of the first network port is less than or equal to a time threshold. Furthermore, since each network port has at least one alarm type, at least one alarm type of any target network port matches at least one alarm type of the first network port.

[0091] As an example, when the topology restoration module determines that there is at least one candidate network port whose alarm type matches that of the first network port, it can also determine whether the alarm data generation time interval of the candidate network port matching the alarm type of the first network port is less than or equal to a time threshold. When the topology restoration module determines that the generation time interval is less than or equal to the time threshold, the topology restoration module can use the candidate network port as the target network port.

[0092] For example, with a time threshold of 30 seconds, network port A belongs to OTN, and a remote network fault alarm (e.g., REMOTE_FAULT) occurs on network port A at 12:31:08; network port B belongs to PTN, and a local network fault alarm (e.g., LOCAL_FAULT) occurs on network port B at 12:30:57. The topology restoration module can determine, based on preset alarm matching rules, that there is a causal relationship between the alarm types of network port A and network port B, and that the alarm data generation time interval is 9 seconds, which is less than the time threshold of 30 seconds. In this case, the topology restoration module can determine that network port A and network port B form a network port pair.

[0093] S503: The topology restoration module generates a cross-domain network topology based on at least one set of network port pairs.

[0094] In some embodiments, after obtaining at least one set of network port pairs, the topology restoration module can also generate a network port relationship diagram based on the at least one set of network port pairs. The network port relationship diagram contains at least one link, each link connecting two network ports within a set of network port pairs. For example, the topology restoration module can also display the network port relationship diagram in the user interface of the first application. The network port relationship diagram corresponds to the first site.

[0095] For example, such as Figure 6A As shown, after obtaining 9 sets of network port pairs, the topology restoration module generates a network port relationship diagram based on these 9 sets of network port pairs. The 9 sets of network port pairs are: port A and port B, port A and port D, port A and port F, port C and port B, port C and port D, port C and port F, port E and port B, port E and port D, and port E and port F. Ports A, C, and E belong to OTN, while ports B, D, and F belong to PTN.

[0096] The topology restoration module can determine the confidence rate of each link based on the alarm type matching of the two network ports connected to each link in the network port relationship diagram. For example, the topology restoration module can determine the confidence rate of each link in the following way.

[0097] For the first link in the network port relationship graph, the topology restoration module can perform the following steps:

[0098] B1: The topology restoration module can use the number of alarm types that match between the second network port and the third network port as the first quantity.

[0099] The first link is used to connect the second network port and the third network port, and the first link can be any link in the network port relationship diagram.

[0100] B2: The topology restoration module can use the number of alarm types that match between the second network port and at least one fourth network port as the second quantity.

[0101] The network domain of the second network port is the first network domain among multiple network domains. At least one fourth network port is a network port whose alarm type matches that of the second network port, and at least one fourth network port includes a third network port.

[0102] B3: The topology restoration module can use the ratio of the first quantity to the second quantity as the confidence rate of the first link.

[0103] For example, such as Figure 6B As shown, in the network port relationship diagram, the number of matching alarm types between ports A and B is 10, between ports A and D is 5, between ports A and F is 5, between ports C and B is 4, between ports C and D is 12, between ports C and F is 6, between ports E and B is 3, between ports E and D is 4, and between ports E and F is 9. The topology restoration module can determine the confidence rate of each link connecting ports A, C, and E based on the number of matching alarm types between ports in the network port relationship diagram. Additionally, the topology restoration module can also determine the confidence rate of each link connecting ports B, D, and F based on the number of matching alarm types between ports. In some embodiments, the topology restoration module can also display the content shown in Figure 6 in the user interface of the first application to inform the user of the confidence rate of each link in the network port relationship diagram.

[0104] After obtaining the confidence rate of each link in the network relationship graph, the topology restoration module can generate a cross-domain network topology based on the confidence rate of each link and the network port relationship graph. For example, the topology restoration module can determine that the link with the highest current confidence rate in the network port relationship graph is a cross-domain link, and clear the links between the two network ports connected by the cross-domain link in the network port relationship graph; repeating the above steps until all links in the network port relationship graph are cleared. Among the links cleared by the topology restoration module are cross-domain links. The topology restoration module can generate a cross-domain network topology based on at least one cross-domain link determined in the network port relationship graph. This cross-domain network topology is the cross-domain network topology of the first site. In some scenarios, the topology restoration module can also display the process of generating the cross-domain network topology of the first site based on the confidence rate of each link in the network relationship graph in the user interface of the first application.

[0105] For example, such as Figure 7 As shown, the topology restoration module determines that the link with the highest confidence rate in the network port relationship graph is the link connecting ports E and F, and treats this link as a cross-domain link. The topology restoration module can also clear the links connecting ports E and F from the network port relationship graph. The topology restoration module determines that the link with the highest confidence rate in the network port relationship graph is the link connecting ports C and D, and treats this link as a cross-domain link. The topology restoration module can also clear the links connecting ports C and D from the network port relationship graph. At this point, only the link connecting ports A and B remains in the network port relationship graph, and this link is treated as a cross-domain link and cleared. Thus, the topology restoration module can obtain the cross-domain links connecting ports E and F, the cross-domain links connecting ports C and D, and the cross-domain links connecting ports A and B. Figure 8 As shown, after obtaining the three cross-domain links, the topology restoration module can generate the cross-domain network topology of the first site based on the three cross-domain links determined in the network port relationship diagram.

[0106] After obtaining the cross-domain network topology for each site in this business scenario, the topology restoration module can also synchronize one or more cross-domain network topologies in this business scenario to the database used to store network topologies. The topology restoration module can also generate and store a cross-domain link relationship file based on one or more cross-domain network topologies, allowing users to view one or more cross-domain network topologies in this business scenario based on the cross-domain link relationship file.

[0107] Based on the above embodiments, the topology restoration module can perform cross-domain correlation analysis on every two network ports from different network domains based on alarm data of network ports in different network domains, and form network port pairs with alarm types that have a causal relationship. Thus, a cross-domain network topology can be generated based on at least one network port pair, without having to determine the cross-domain correlation between network ports through communication messages between network ports, thereby improving the restoration rate of cross-domain network topology.

[0108] Based on the cross-domain network topology generation method provided in the above embodiments, this application also provides an example of a cross-domain network topology generation method. In this example, multiple network ports are located within the same site. Figure 9A The illustration shows a schematic complete flowchart of a cross-domain network topology generation method provided in an embodiment of this application, including the following steps:

[0109] S901: The topology restoration module determines at least one alarm type for each network port based on at least one alarm data for each network port among multiple network ports located in two network domains.

[0110] Among them, the two network domains are wavelength division multiplexing network domain and data communication network domain. At least one alarm type of each network port is used to characterize the nature of the alarm generated by each network port. Multiple network ports are located in the same physical range.

[0111] S902: The topology restoration module determines at least one pair of network ports with cross-domain relationships among multiple network ports based on the alarm types of multiple network ports.

[0112] Each network port pair contains two network ports from different network domains whose alarm types are causally related.

[0113] The execution process of step S902 is the same as that of step S502 in the above embodiment, and will not be described again here.

[0114] S903: The topology restoration module generates a network port relationship diagram based on at least one set of network port pairs.

[0115] The network port relationship diagram contains at least one link, and each link is used to connect two network ports in a set of network port pairs.

[0116] S904: The topology restoration module determines the confidence rate of each link based on the alarm type matching of the two network ports connected to each link in the network port relationship diagram.

[0117] The execution process of step S904 is the same as the process by which the topology restoration module can determine the confidence rate of each link in the above embodiment, and will not be described again here.

[0118] S905: The topology restoration module determines that the link with the highest confidence rate in the network port relationship graph is a cross-domain link.

[0119] S906: The topology restoration module clears the links between two network ports connected by cross-domain links in the network port relationship diagram.

[0120] S907: The topology restoration module determines whether all links in the network port relationship diagram have been cleared; if yes, proceed to step S908; if no, proceed to step S905.

[0121] S908: The topology restoration module generates a cross-domain network topology based on at least one cross-domain link determined in the network port relationship graph.

[0122] based on Figure 9A As shown, the topology reconstruction module can perform cross-domain correlation analysis on every two network ports from different network domains based on alarm data from network ports in different network domains. It then pairs two network ports from different network domains whose alarm types have a causal relationship, thus obtaining at least one set of network port pairs with cross-domain correlations. In this way, the topology reconstruction module can determine the probability of cross-domain links between network ports based on the confidence rate of each link in the network port relationship graph composed of at least one set of network port pairs. This eliminates the need for manual determination of the probability of cross-domain links between network ports, thereby reducing manual workload and improving the accuracy of cross-domain network topology reconstruction.

[0123] Based on the cross-domain network topology generation method provided in the above embodiments, this application also provides an example of another cross-domain network topology generation method. In this example, multiple network ports are located within the same site. Figure 9B This paper illustrates an interactive flowchart of a cross-domain network topology generation method provided in an embodiment of this application, including the following steps:

[0124] S1001: The user equipment sends the alarm data and alarm matching rules of the first site to the topology restoration module. The topology restoration module receives the alarm data and alarm matching rules of the first site from the user equipment.

[0125] In this context, user equipment refers to equipment used to meet specific user needs. For example, user equipment can be terminal devices such as mobile phones, tablets, and laptops. The first site includes multiple network ports located in two network domains: a wavelength division multiplexing (WDM) network domain and a data communication network domain, with the multiple network ports situated within the same physical area. Alarm matching rules are used to indicate multiple sets of alarm types with causal relationships.

[0126] S1002: The topology restoration module determines the alarm type of each network port based on the alarm data of each network port among multiple network ports.

[0127] The alarm type for each network port is used to characterize the nature of the alarms generated by each network port.

[0128] S1003: The topology restoration module determines at least one pair of network ports with cross-domain relationships among multiple network ports based on the alarm types and alarm matching rules of multiple network ports.

[0129] Each network port pair contains two network ports from different network domains whose alarm types are causally related.

[0130] The execution process of step S1003 is the same as that of step S502 in the above embodiment, and will not be described again here.

[0131] S1004: The topology restoration module generates a cross-domain network topology based on at least one set of network port pairs.

[0132] The execution process of step S1004 is the same as that of step S503 in the above embodiment, and will not be described again here.

[0133] S1005: The topology restoration module sends cross-domain network topology data to the database. The database receives the cross-domain network topology data from the topology restoration module.

[0134] The cross-domain network topology data can be either a cross-domain network topology diagram of the first site or a set of links corresponding to the cross-domain network topology of the first site. The database can be... Figure 1 The database shown is 200.

[0135] After receiving cross-domain network topology data, the database can save the cross-domain network topology of the first site.

[0136] S1006: The topology restoration module sends cross-domain network topology data to the user equipment. The user equipment receives the cross-domain network topology data from the topology restoration module.

[0137] There is no specific order in which steps S1005 and S1006 are executed.

[0138] based on Figure 9B As shown, the user equipment can send the alarm data of the first site for which the user wants to perform topology restoration, along with the alarm matching rules, to the topology restoration module. This allows the topology restoration module to perform cross-domain correlation analysis on every two network ports from different network domains in the first site based on the alarm data and alarm matching rules. It then groups two network ports from different network domains whose alarm types have a causal relationship into network port pairs. This allows the module to generate a cross-domain network topology based on at least one obtained network port pair, without needing to determine the cross-domain correlation between network ports through communication messages between them, thereby improving the cross-domain network topology restoration rate.

[0139] Based on the above content and the same concept, Figure 10 This is a schematic diagram of the structure of a possible cross-domain network topology generation device 1000 provided in this application, as shown below. Figure 10 As shown, the cross-domain network topology generation apparatus 1000 may include a processing unit 1001 and a communication unit 1002. The processing unit 1001 controls and manages the operation of the cross-domain network topology generation apparatus 1000. The communication unit 1002 supports communication between the cross-domain network topology generation apparatus 1000 and other devices. Optionally, the communication unit 1002 may include a receiving unit and / or a sending unit, respectively used to perform receiving and sending operations. Optionally, the cross-domain network topology generation apparatus 1000 may also include a storage unit 1003 for storing the program code and / or data of the cross-domain network topology generation apparatus 1000.

[0140] The processing unit 1001 can support the cross-domain network topology generation device 1000 in executing the actions of the topology restoration module in the method examples above. Alternatively, the processing unit 1001 mainly executes the internal actions of the topology restoration module in the method examples. The communication unit 1002 can support communication between the cross-domain network topology generation device 1000 and other devices.

[0141] For example, the cross-domain network topology generation device 1000 can be the topology restoration module in the above embodiments. This cross-domain network topology generation device 1000 is applied to electronic devices.

[0142] In some embodiments, the cross-domain network topology generation device 1000 can be used to implement the function of the topology restoration module in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0143] Processing unit 1001 is configured to determine the alarm type of each network port based on alarm data of each network port in multiple network ports located in multiple network domains; wherein the multiple network domains include wavelength division multiplexing network domains and data communication network domains, and the alarm type of each network port is used to characterize the nature of the alarm generated by each network port; based on the alarm types of the multiple network ports, determine at least one pair of network ports with cross-domain correlation among the multiple network ports; wherein any pair of network ports contains two network ports from different network domains whose alarm types have a causal relationship; and generate a cross-domain network topology based on the at least one pair of network ports.

[0144] The communication unit 1002 is used to receive and send data.

[0145] In one possible implementation, the processing unit 1001 is specifically used for:

[0146] For the first network port among the plurality of network ports, perform the following steps:

[0147] The alarm type of the first network port is matched with the alarm type of at least one candidate network port among the plurality of network ports; when there is at least one target network port among the at least one candidate network port whose alarm type matches the alarm type of the first network port, at least one first network port pair is generated based on the first network port and the at least one target network port.

[0148] Wherein, the first network port is any one of the plurality of network ports, and the network domain in which the at least one candidate network port is located is different from the network domain in which the first network port is located; any first network port pair includes the first network port and a target network port, and the alarm type of the at least one target network port is causally related to the alarm type of the first network port; the at least one set of network port pairs includes the at least one set of first network port pairs.

[0149] In one possible implementation, the alarm data generation time interval for any target network port that matches the alarm type of the first network port is less than or equal to a time threshold.

[0150] In one possible implementation, the processing unit 1001 is specifically configured to: match the alarm type of the first network port with the alarm type of at least one candidate network port among the plurality of network ports according to a preset alarm matching rule; the alarm matching rule is used to indicate multiple sets of alarm types with causal relationship.

[0151] In one possible implementation, each network port has at least one alarm data; the processing unit 1001 is specifically used for:

[0152] Based on at least one alarm data for each network port, determine at least one alarm type for each network port;

[0153] At least one alarm type of any target network port matches at least one alarm type of the first network port;

[0154] Processing unit 1001 is specifically used for:

[0155] A network port relationship graph is generated based on the at least one set of network port pairs; wherein the network port relationship graph contains at least one link, and each link is used to connect two network ports contained in a set of network port pairs;

[0156] Based on the alarm type matching of the two network ports connected to each link in the network port relationship diagram, the confidence rate of each link is determined.

[0157] The cross-domain network topology is generated based on the confidence rate of each link and the network port relationship graph.

[0158] In one possible implementation, the processing unit 1001 is specifically used for:

[0159] For the first link in the network port relationship graph, perform the following steps:

[0160] The number of alarm types that match between the second network port and the third network port is taken as the first quantity; wherein, the first link is used to connect the second network port and the third network port, and the first link is any link in the network port relationship diagram;

[0161] The number of alarm types that match between the second network port and at least one fourth network port is taken as the second quantity; wherein, the network domain where the second network port is located is the first network domain set among the plurality of network domains; and the at least one fourth network port is a network port that matches the alarm type of the second network port.

[0162] The ratio of the first quantity to the second quantity is used as the confidence rate of the first link.

[0163] In one possible implementation, the processing unit 1001 is specifically used for:

[0164] The link with the highest confidence rate in the network port relationship graph is identified as a cross-domain link, and the links between the two network ports connected by the cross-domain link in the network port relationship graph are cleared. The above steps are repeated until all links in the network port relationship graph are cleared. Based on at least one cross-domain link identified in the network port relationship graph, the cross-domain network topology is generated.

[0165] In one possible implementation, the plurality of network ports are located within the same physical area.

[0166] It should be understood that the division of units in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, all units in the device can be implemented entirely through software calls from processing elements; all units can be implemented entirely in hardware; or some units can be implemented through software calls from processing elements, while others are implemented in hardware. For example, each unit can be a separate processing element, or it can be integrated into a chip within the device. Alternatively, it can be stored as a program in memory, called and executed by a processing element of the device. Moreover, these units can be fully or partially integrated together, or implemented independently. The processing element here can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, the operations or units described above can be implemented through integrated logic circuits in the processor element or through software calls from processing elements.

[0167] In one example, a unit in any of the above devices can be one or more integrated circuits configured to implement the methods described above, such as: one or more application-specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these forms of integrated circuits. As another example, when a unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a processor, such as a general-purpose central processing unit (CPU), or other processor capable of calling programs. Furthermore, these units can be integrated together to implement a system-on-a-chip (SOC).

[0168] The receiving unit described above is an interface circuit of the device, used to receive signals from other devices. For example, when the device is implemented as a chip, the receiving unit is an interface circuit for the chip to receive signals from other chips or devices. The transmitting unit described above is an interface circuit of the device, used to transmit signals to other devices. For example, when the device is implemented as a chip, the transmitting unit is an interface circuit for the chip to transmit signals to other chips or devices.

[0169] Please refer to Figure 11 This is a schematic diagram of a cross-domain network topology generation device provided in an embodiment of this application, used to implement the operation of the topology restoration module in the above embodiments. The cross-domain network topology generation device 1100 includes a processor 1110 and an interface 1130. Optionally, the communication device 1100 also includes a memory 1120. The interface 1130 is used to enable communication with other devices.

[0170] In the above embodiments, the method executed by the topology restoration module of the electronic device can be implemented by the processor 1110 calling a program stored in the memory (which can be the memory 1120 in the topology restoration module of the electronic device or an external memory). That is, the cross-domain network topology generation device 1100 for implementing the function of the topology restoration module of the electronic device may include a processor 1110, which executes the method executed by the topology restoration module of the electronic device in the above method embodiments by calling a program in the memory. The processor here can be an integrated circuit with signal processing capabilities, such as a CPU. The electronic device can be implemented by one or more integrated circuits configured to implement the above method. For example: one or more ASICs, or one or more microprocessors (DSPs), or one or more FPGAs, or a combination of at least two of these integrated circuit forms. Alternatively, the above implementation methods can be combined.

[0171] When the communication device 1100 is used in the above method, the processor 1110 is used to implement the function of the processing unit 1001, and the interface 1130 is used to implement the function of the communication unit 1002.

[0172] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0173] The various illustrative logic units and circuits described in the embodiments of this application can be implemented or operate the described functions using a general-purpose processor, digital signal processor, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor can be a microprocessor; alternatively, it can also be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented using a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration.

[0174] The steps of the methods or algorithms described in the embodiments of this application can be directly embedded in hardware, software units executed by a processor, or a combination of both. The software units can be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from and write information to the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and storage medium can be housed in an ASIC.

[0175] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0176] In one or more exemplary implementations, the functions described in the embodiments of this application can be implemented in hardware, software, firmware, or any combination of these three. If implemented in software, these functions can be stored on a computer-readable medium or transmitted on a computer-readable medium in the form of one or more instructions or code. Computer-readable media include computer storage media and communication media that facilitate the transfer of computer programs from one place to another. Storage media can be any available media that can be accessed by a general-purpose or special-purpose computer. For example, such computer-readable media can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store program code in the form of instructions or data structures and other forms that can be read by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Furthermore, any connection can be suitably defined as a computer-readable medium, for example, if the software is transmitted from a website, server or other remote resource via a coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL) or wirelessly, such as infrared, wireless and microwave, it is also included in the defined computer-readable medium. The disks and discs mentioned include compressed disks, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks typically copy data magnetically, while discs typically copy data optically using lasers. Combinations of these can also be contained in computer-readable media.

[0177] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0178] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the embodiments of this application. It should be understood that the above descriptions are merely specific implementations of the embodiments of this application and are not intended to limit the scope of protection of the embodiments of this application. Any modifications, equivalent substitutions, or improvements made based on the technical solutions of the embodiments of this application should be included within the scope of protection of the embodiments of this application. The above description of this application specification allows any artist in the art to utilize or implement the content of the embodiments of this application. Any modifications based on the disclosed content should be considered obvious in the art. The basic principles described in the embodiments of this application can be applied to other variations without departing from the inventive nature and scope of this application. Therefore, the content disclosed in the embodiments of this application is not limited to the described embodiments and implementations, but can be extended to the maximum scope consistent with the principles of this application and the disclosed new features.

[0179] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of the embodiments of this application. Accordingly, this specification and drawings are merely exemplary illustrations of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Obviously, those skilled in the art can make various alterations and modifications to this application without departing from the scope of this application. Thus, if these modifications and modifications to the embodiments of this application fall within the scope of the claims of this application and their equivalents, the embodiments of this application are also intended to include these modifications and modifications.

Claims

1. A method for generating cross-domain network topology, characterized in that, include: Based on the alarm data of each network port in multiple network ports located in multiple network domains, the alarm type of each network port is determined; wherein, the multiple network domains include wavelength division network domain and data communication network domain, and the alarm type of each network port is used to characterize the nature of the alarm generated by each network port. Based on the alarm types of the plurality of network ports, at least one pair of network ports with cross-domain association is determined from the plurality of network ports; wherein any pair of network ports contains two network ports from different network domains whose alarm types have a causal relationship. A cross-domain network topology is generated based on the at least one set of network port pairs.

2. The method according to claim 1, characterized in that, The step of determining at least one pair of network ports with cross-domain association relationships among the multiple network ports based on the alarm types of the multiple network ports includes: For the first network port among the plurality of network ports, perform the following steps: The alarm type of the first network port is matched with the alarm type of at least one candidate network port among the plurality of network ports; When there is at least one target network port among the at least one candidate network port whose alarm type matches the alarm type of the first network port, at least one set of first network port pairs is generated based on the first network port and the at least one target network port; Wherein, the first network port is any one of the plurality of network ports, and the network domain in which the at least one candidate network port is located is different from the network domain in which the first network port is located; any first network port pair includes the first network port and a target network port, and the alarm type of the at least one target network port is causally related to the alarm type of the first network port; the at least one set of network port pairs includes the at least one set of first network port pairs.

3. The method according to claim 2, characterized in that, The alarm data generation time interval for any target network port that matches the alarm type of the first network port is less than or equal to the time threshold.

4. The method according to claim 2 or 3, characterized in that, The step of matching the alarm type of the first network port with the alarm type of at least one candidate network port among the plurality of network ports includes: According to a preset alarm matching rule, the alarm type of the first network port is matched with the alarm type of the at least one candidate network port; wherein, the alarm matching rule is used to indicate multiple sets of alarm types with causal relationship.

5. The method according to any one of claims 2-4, characterized in that, Each network port has at least one alarm data; the step of determining the alarm type of each network port based on the alarm data of each network port in multiple network domains includes determining at least one alarm type of each network port based on at least one alarm data of each network port. At least one alarm type of any target network port matches at least one alarm type of the first network port; The step of generating a cross-domain network topology based on the at least one set of network port pairs includes: A network port relationship graph is generated based on the at least one set of network port pairs; wherein the network port relationship graph contains at least one link, and each link is used to connect two network ports contained in a set of network port pairs; Based on the alarm type matching of the two network ports connected to each link in the network port relationship diagram, the confidence rate of each link is determined. The cross-domain network topology is generated based on the confidence rate of each link and the network port relationship graph.

6. The method according to claim 5, characterized in that, The step of determining the confidence rate of each link based on the alarm type matching of the two network ports connected to each link in the network port relationship diagram includes: For the first link in the network port relationship graph, perform the following steps: The number of alarm types that match between the second network port and the third network port is taken as the first quantity; wherein, the first link is used to connect the second network port and the third network port, and the first link is any link in the network port relationship diagram; The number of alarm types that match between the second network port and at least one fourth network port is taken as the second quantity; wherein, the network domain where the second network port is located is the first network domain set among the plurality of network domains; and the at least one fourth network port is a network port that matches the alarm type of the second network port. The ratio of the first quantity to the second quantity is used as the confidence rate of the first link.

7. The method according to claim 5 or 6, characterized in that, The step of generating the cross-domain network topology based on the confidence rate of each link and the network port relationship graph includes: The link with the highest confidence rate in the network port relationship graph is identified as a cross-domain link, and the links between the two network ports connected by the cross-domain link in the network port relationship graph are cleared. The above steps are repeated until all links in the network port relationship graph are cleared. Based on at least one cross-domain link identified in the network port relationship graph, the cross-domain network topology is generated.

8. The method according to any one of claims 1-7, characterized in that, The multiple network ports are located within the same physical area.

9. A cross-domain network topology generation device, characterized in that, It includes a memory and one or more processors, the memory being coupled to the one or more processors; The memory is used to store computer programs or instructions that, when executed by the one or more processors, cause the communication device to perform the method as described in any one of claims 1-8.

10. A cross-domain network topology generation device, characterized in that, Includes a communication unit and a processing unit; The communication unit is used to receive and send data; The processing unit is configured to perform the method as described in any one of claims 1-8.

11. A computer-readable storage medium, characterized in that, Includes computer program instructions, which, when executed by a computer, cause the computer to perform the method as described in any one of claims 1-8.

12. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1-8.

13. A chip, characterized in that, The chip is connected to a memory and is used to read and execute program code stored in the memory to implement the method as described in any one of claims 1-8.

Images