Network topology generation method, apparatus, device, medium, and program product

Abstract

Embodiments of the application disclose a network topology generation method, device, equipment, medium and program product. The method comprises: obtaining first topology data of an OLT device; determining at least one uplink device matched with an uplink port of the OLT device according to the first topology data; obtaining second topology data of the uplink device, the second topology data comprising physical topology data corresponding to an Ethernet interface of the uplink device and logical link data; in the case that the uplink device comprises a metropolitan area network switch, determining at least one metropolitan area network router matched with the uplink port of the metropolitan area network switch according to the physical topology data and the logical link data corresponding to the uplink port in the Ethernet interface of the metropolitan area network switch; obtaining third topology data of the metropolitan area network router; and generating a network topology from the OLT device to the metropolitan area network router according to the first topology data, the second topology data and the third topology data. The embodiments of the application can generate a network topology covering a PON access network to a data metropolitan area network, thereby supporting end-to-end automatic opening of a PON private line.

Description

Technical Field

[0001] This application belongs to the field of computer network technology, and in particular relates to a network topology generation method, apparatus, device, computer storage medium, and computer program product. Background Technology

[0002] Passive Optical Network (PON) leased line services are a core business for telecom operators. However, due to limitations in internal resource coordination efficiency and personnel expertise, current leased line activation efficiency is low, and manual activation cannot meet users' comprehensive and flexible service needs. Therefore, automatic activation of PON leased lines is a primary requirement for operators to improve efficiency and customer satisfaction.

[0003] Accurate network topology data is fundamental for achieving end-to-end automatic activation of leased lines. PON leased line activation involves both PON access networks and data metropolitan area networks (MANs), requiring accurate network topology data to send automatic activation configurations to network devices along the activation path. However, due to limitations in the functionality of the Operations & Maintenance Center (OMC) network management system and the domain-specific management of different networks, there is currently a lack of effective methods and systems to generate network topology data covering both access networks and data MANs. Currently, the data is manually entered into the resource management system using manual record forms from device network access. However, the accuracy and completeness of manually entered network topology data are insufficient to support end-to-end automatic activation of PON leased lines. Summary of the Invention

[0004] This application provides a network topology generation method, apparatus, device, computer storage medium, and computer program product, which can generate a network topology covering PON access network and data metropolitan area network to support end-to-end automatic commissioning of PON leased lines.

[0005] In a first aspect, embodiments of this application provide a network topology generation method, including:

[0006] Obtain the first topology data of the OLT device. The first topology data includes physical topology data and logical link data corresponding to the uplink port of the OLT device.

[0007] Based on the first topology data, at least one uplink device is identified that matches the uplink port of the OLT device. The uplink device includes a metropolitan area network router or a metropolitan area network switch.

[0008] Obtain the second topology data of the uplink device. The second topology data includes physical topology data and logical link data corresponding to the Ethernet interface of the uplink device.

[0009] When the uplink device includes a metropolitan area network (MAN) switch, at least one MAN router that matches the uplink port of the MAN switch is determined based on the physical topology data and logical link data corresponding to the uplink port in the Ethernet interface of the MAN switch.

[0010] Obtain the third topology data of the metropolitan area network (MAN) router. The third topology data includes the physical topology data and logical link data corresponding to the Ethernet interface of the MAN router.

[0011] Based on the first topology data, the second topology data, and the third topology data, a network topology from the OLT device to the metropolitan area network router is generated.

[0012] In one optional implementation, the OLT device includes multiple uplink ports to acquire first topology data of the OLT device, including:

[0013] Collect physical topology data and logical link data corresponding to each uplink port of the OLT device;

[0014] Based on the physical topology data and logical link data corresponding to each uplink port of the OLT device, a topology data dictionary for the OLT device is generated. The topology data dictionary for the OLT device includes the identification information of the OLT device, the identification information of each uplink port of the OLT device, and the physical topology data and logical link data corresponding to each uplink port of the OLT device respectively.

[0015] The physical topology data corresponding to each uplink port of the OLT device is judged to determine the type of the peer device of the uplink port of the OLT device;

[0016] When the uplink port of the OLT device is a metropolitan area network switch or metropolitan area network router, obtain the physical topology data and logical link data corresponding to the uplink port of the OLT device.

[0017] In one optional implementation, physical topology data and logical link data corresponding to each uplink port of the OLT device are collected, including:

[0018] The Link Layer Discovery Protocol (LLDP) is used to collect physical topology data for each uplink port of the OLT device.

[0019] Collect logical link data corresponding to each uplink port of the OLT device.

[0020] In one optional implementation, the physical topology data and logical link data corresponding to each uplink port of the OLT device are collected respectively, and the method further includes:

[0021] If the OLT device does not support LLDP, obtain the MAC address information of the OLT device;

[0022] Collect physical topology data corresponding to each uplink port of the OLT device by using MAC address information;

[0023] Collect logical link data corresponding to each uplink port of the OLT device.

[0024] In one optional implementation, acquiring the second topology data of the uplink device includes:

[0025] The physical topology data and logical link data corresponding to each Ethernet interface of the uplink device are collected using LLDP.

[0026] Based on the physical topology data and logical link data corresponding to each Ethernet interface of the uplink device, a topology data dictionary for the uplink device is generated. The topology data dictionary for the uplink device includes the identification information of the uplink device, the identification information of each Ethernet interface of the uplink device, and the physical topology data and logical link data corresponding to each Ethernet interface of the uplink device respectively.

[0027] The physical topology data corresponding to each Ethernet interface of the uplink device is judged to determine the peer device type of the Ethernet interface of the uplink device;

[0028] When the peer device of the Ethernet interface of the uplink device is a metropolitan area network (MAN) device or an OLT device, obtain the physical topology data and logical link data corresponding to the Ethernet interface of the uplink device. MAN devices include MAN switches and MAN routers.

[0029] In one optional implementation, obtaining third topology data of the metropolitan area network router includes:

[0030] The physical topology data and logical link data corresponding to each Ethernet interface of the metropolitan area network router are collected using LLDP.

[0031] Based on the physical topology data and logical link data corresponding to each Ethernet interface of the metropolitan area network (MAN) router, a topology data dictionary for the MAN router is generated. The topology data dictionary for the MAN router includes the identification information of the MAN router, the identification information of each Ethernet interface of the MAN router, and the physical topology data and logical link data corresponding to each Ethernet interface of the MAN router.

[0032] The physical topology data corresponding to each Ethernet interface of the metropolitan area network router is judged to determine the peer device type of the Ethernet interface of the metropolitan area network router.

[0033] When the peer device of the Ethernet interface of the metropolitan area network (MAN) router is a MAN switch or a MAN router, obtain the physical topology data and logical link data corresponding to the Ethernet interface of the MAN router.

[0034] Secondly, embodiments of this application provide a network topology generation apparatus, comprising:

[0035] The acquisition module is used to acquire the first topology data of the OLT device. The first topology data includes physical topology data and logical link data corresponding to the uplink port of the OLT device.

[0036] The determination module is used to determine, based on the first topology data, at least one uplink device that matches the uplink port of the OLT device, including a metropolitan area network router or a metropolitan area network switch.

[0037] The acquisition module is also used to acquire the second topology data of the uplink device, which includes physical topology data and logical link data corresponding to the Ethernet interface of the uplink device.

[0038] The determination module is also used to determine, in the case where the uplink device includes a metropolitan area network (MAN) switch, at least one MAN router that matches the uplink port of the MAN switch based on the physical topology data and logical link data corresponding to the uplink port in the Ethernet interface of the MAN switch.

[0039] The acquisition module is also used to acquire the third topology data of the metropolitan area network router, which includes physical topology data and logical link data corresponding to the Ethernet interface of the metropolitan area network router.

[0040] The generation module is used to generate a network topology from the OLT device to the metropolitan area network router based on the first topology data, the second topology data, and the third topology data.

[0041] Thirdly, embodiments of this application provide an electronic device, the device including: a processor and a memory storing computer program instructions;

[0042] When the processor executes computer program instructions, it implements a network topology generation method as described in any optional embodiment of the first aspect of this application.

[0043] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer program instructions, which, when executed by a processor, implement the network topology generation method as described in any optional embodiment of the first aspect of this application.

[0044] Fifthly, embodiments of this application provide a computer program product in which instructions, when executed by a processor of an electronic device, cause the electronic device to perform a network topology generation method as described in any optional embodiment of the first aspect of this application.

[0045] The network topology generation method, apparatus, device, computer storage medium, and computer program product of this application embodiment can determine the uplink device matching the uplink port of the OLT device through the physical topology data and logical link data corresponding to the uplink port of the OLT device, and obtain the physical topology data and logical link data corresponding to the Ethernet interface of the uplink device. This allows for accurate and complete acquisition of network topology data from the OLT device to the metropolitan area network (MAN) switch network segment, and from the OLT device directly connected to the MAN router network segment. This application embodiment also determines the MAN router matching the uplink port of the MAN switch through the physical topology data and logical link data corresponding to the uplink port of the MAN switch, and obtains the physical topology data and logical link data corresponding to the Ethernet interface of the MAN router. This allows for accurate and complete acquisition of network topology data from the MAN switch to the MAN router network segment. Thus, the accuracy and completeness of the network topology data from the OLT device connected to the MAN router network segment via the MAN switch are guaranteed. This application embodiment generates a network topology based on the first topology data, the second topology data, and the third topology data. This network topology can cover the PON access network to the data metropolitan area network, thereby supporting end-to-end automatic activation of PON leased lines. Attached Figure Description

[0046] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0047] Figure 1 This is a schematic diagram of a PON leased line architecture provided in one embodiment of this application;

[0048] Figure 2 This is a flowchart illustrating a network topology generation method provided in another embodiment of this application;

[0049] Figure 3 This is a schematic diagram of the structure of a PON leased line end-to-end network topology generation system provided in another embodiment of this application;

[0050] Figure 4 This is a schematic diagram of the structure of the PON access network OLT topology information acquisition module in the PON leased line end-to-end network topology generation system provided in another embodiment of this application;

[0051] Figure 5 This is a schematic diagram of the structure of the metropolitan area network switch topology information acquisition module in the PON leased line end-to-end network topology generation system provided in another embodiment of this application;

[0052] Figure 6 This is a schematic diagram of the structure of the metropolitan area network router topology information collection module in the PON leased line end-to-end network topology generation system provided in another embodiment of this application;

[0053] Figure 7 This is a flowchart illustrating a network topology generation method provided in another embodiment of this application;

[0054] Figure 8 This is a network topology diagram of an OLT device to a metropolitan area network router provided in another embodiment of this application;

[0055] Figure 9 This is a schematic diagram of the network topology generation apparatus provided in another embodiment of this application;

[0056] Figure 10 This is a schematic diagram of the network topology generation device provided in another embodiment of this application. Detailed Implementation

[0057] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0058] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0059] As described in the background section, providing accurate network topology data to support end-to-end automatic activation of PON leased lines is of great significance for improving operators' business processing efficiency and customer satisfaction.

[0060] Figure 1 This is a schematic diagram of a PON leased line architecture provided in one embodiment of this application. Figure 1 As shown, a PON leased line can include a PON access network and a data metropolitan area network (MAN). The data MAN includes the network segment from the Optical Line Terminal (OLT) equipment to the MAN switch, and the network segment from the MAN switch to the MAN router. Ensuring the accuracy and integrity of the network topology data of each network segment in the data MAN is crucial for supporting the end-to-end automatic commissioning of the PON leased line.

[0061] Currently, network topology data in related technologies is mostly manually entered into resource management systems using manual record forms when devices are connected to the network. However, the accuracy and completeness of manually entered network topology data are insufficient to support end-to-end automatic commissioning of PON leased lines.

[0062] Related technologies also involve receiving Link Layer Discovery Protocol (LLDP) information periodically sent by routers in multiple network segments, preprocessing the LLDP information, and generating an information list. A network segment topology generation algorithm is then used to process the information in the information list and generate a network physical topology map. However, because some older OLT devices do not support LLDP, the network physical topology map for these OLT devices cannot be obtained, making it difficult to guarantee the integrity of the network physical topology map. Furthermore, automatic commissioning of PON leased lines requires not only physical topology data but also logical link information such as Ethernet link aggregation (Eth-trunk) and Link Aggregation Control Protocol (LACP) protection groups. For example, Virtual Local Area Networks (VLANs) need to be configured in the Eth-trunk. Therefore, the aforementioned network physical topology map still cannot support end-to-end automatic commissioning of PON leased lines.

[0063] To support end-to-end automatic commissioning of PON leased lines, the inventors, through in-depth consideration, ingeniously proposed a network topology generation method, apparatus, device, computer storage medium, and computer program product. This network topology generation method generates a network topology covering the PON access network to the data metropolitan area network, enabling end-to-end automatic commissioning of PON leased lines.

[0064] The network topology generation method provided in this application will be described below with reference to the accompanying drawings and specific embodiments and application scenarios. The network topology generation method provided in this application can be executed by a network topology generation device, or a portion of the network topology generation device used to execute the network topology generation method. This application uses the execution of the network topology generation method by a network topology generation device as an example to describe in detail the network topology generation method provided in this application.

[0065] Figure 2 A schematic flowchart of a network topology generation method according to an embodiment of this application is shown. Figure 2 As shown, the network topology generation method may specifically include the following steps S110 to S160.

[0066] S110, Obtain the first topology data of the OLT device. The first topology data includes physical topology data and logical link data corresponding to the uplink port of the OLT device.

[0067] In step S110, the uplink port of the OLT device may include the port on the OLT device used to connect to an upper-layer metropolitan area network switch or metropolitan area network router. The physical topology data corresponding to the uplink port of the OLT device may include, but is not limited to: the name of the peer device of the uplink port and the port number of the peer device of the uplink port. The logical link data corresponding to the uplink port of the OLT device may include, but is not limited to: the protection group to which the uplink port belongs and the protection group type (e.g., Link Aggregation Control Protocol (LACP) aggregation group, UPS protection group, SmartLink protection group, etc.).

[0068] S120, based on the first topology data, determine at least one uplink device that matches the uplink port of the OLT device, the uplink device including a metropolitan area network router or a metropolitan area network switch.

[0069] In step S120, determining at least one metropolitan area network (MAN) switch matching the uplink port of the OLT device based on the first topology data may include: determining the name of the peer device of the uplink port based on the physical topology data corresponding to the uplink port in the first topology data; and determining that the peer device is an uplink device matching the uplink port of the OLT device if the name of the peer device conforms to the naming rules of MAN switches or MAN routers. In one embodiment, the name of the peer device of the uplink port may include the name format information, device version information, and device type information of the peer device of the uplink port. If the name of the peer device on the uplink port conforms to the naming rules of a metropolitan area network (MAN) switch or MAN router, determining that the peer device is an uplink device matching the uplink port of the OLT device may include: determining whether the name of the peer device on the uplink port conforms to the naming rules of a MAN switch or MAN router based on at least one of the following: the name format information, the device version information, and the device type information; and if the name of the peer device on the uplink port conforms to the naming rules of a MAN switch or MAN router, determining that the peer device is an uplink device matching the uplink port of the OLT device.

[0070] S130, Obtain the second topology data of the uplink device. The second topology data includes physical topology data and logical link data corresponding to the Ethernet interface of the uplink device.

[0071] In step S130, when the uplink device is a metropolitan area network (MAN) switch, the Ethernet interface of the uplink device may include the downlink port, crossover port, and uplink port of the uplink device. The downlink port of the uplink device may include a port in the MAN switch used for connecting to a lower-level OLT device; the crossover port of the uplink device may include a port in the MAN switch used for connecting to a MAN switch at the same level; the uplink port of the uplink device may include a port in the MAN switch used for connecting to an upper-level MAN router. When the uplink device is a MAN router, the Ethernet interface of the uplink device may include the downlink port and crossover port of the uplink device. The downlink port of the uplink device may include a port in the MAN router used for connecting to a lower-level OLT device or MAN switch; the crossover port of the uplink device may include a port in the MAN router used for connecting to a MAN router at the same level. The physical topology data corresponding to the Ethernet interface of the uplink device may include, but is not limited to: the name of the peer device of the Ethernet interface, the role of the Ethernet interface, and the port number of the peer device of the Ethernet interface. The logical link data corresponding to the Ethernet interface of the uplink device may include, but is not limited to, the Eth-trunk group where the Ethernet interface of the uplink device is located.

[0072] S140, when the uplink device includes a metropolitan area network (MAN) switch, determine at least one MAN router that matches the uplink port of the MAN switch based on the physical topology data and logical link data corresponding to the uplink port in the Ethernet interface of the MAN switch.

[0073] In step S140, based on the physical topology data and logical link data corresponding to the uplink port of the Ethernet interface of the metropolitan area network (MAN) switch, determining at least one MAN switch that matches the uplink port of the MAN switch may include: determining the name of the peer device of the uplink port based on the physical topology data of the uplink port of the MAN switch; and determining that the peer device is a MAN router that matches the uplink port of the MAN switch if the name of the peer device conforms to the naming rules of MAN routers. The name of the peer device of the uplink port of the MAN switch has a similar meaning to the name of the peer device of the uplink port of the OLT device, and will not be described in detail here. If the name of the peer device on the uplink port conforms to the naming rules of a metropolitan area network (MAN) switch, determining that the peer device is a MAN router matching the uplink port of the MAN switch may include: determining whether the name of the peer device on the uplink port conforms to the naming rules of a MAN router based on at least one of the following: the name format information, the device version information, and the device type information of the peer device on the uplink port; and if the name of the peer device on the uplink port conforms to the naming rules of a MAN router, determining that the peer device is a MAN router matching the uplink port of the MAN switch.

[0074] S150, obtain the third topology data of the metropolitan area network router. The third topology data includes the physical topology data and logical link data corresponding to the Ethernet interface of the metropolitan area network router.

[0075] In step S150, the Ethernet interface of the metropolitan area network (MAN) router may include its downlink port and crosslink port. The downlink port may include a port on the MAN router used for connecting to a lower-level MAN switch or OLT device; the crosslink port may include a port on the MAN router used for connecting to a MAN router at the same level. The physical topology data corresponding to the Ethernet interface of the MAN router may include, but is not limited to: the name of the peer device of the Ethernet interface, the role of the Ethernet interface, and the port number of the peer device. The logical link data corresponding to the Ethernet interface of the MAN router may include, but is not limited to: the Eth-trunk group to which the Ethernet interface of the MAN router belongs.

[0076] S160: Based on the first topology data, the second topology data, and the third topology data, generate the network topology from the OLT device to the metropolitan area network router.

[0077] In one embodiment, step S160 may include: based on the first topology data, the second topology data, and the third topology data, performing topology assembly hop-by-hop on the first topology data, the second topology data, and the third topology data, starting from the access network OLT device and ending at the metropolitan area network router, or starting from the access network OLT device, using the metropolitan area network switch as an intermediate node, and ending at the metropolitan area network router, thereby generating a network topology from the OLT device to the metropolitan area network router.

[0078] The network topology generation method of this application can determine the metropolitan area network (MAN) switch matching the uplink port of the OLT device using the physical topology data and logical link data corresponding to the uplink port of the OLT device, and obtain the physical topology data and logical link data corresponding to the Ethernet interface of the MAN switch. This allows for accurate and complete acquisition of network topology data from the OLT device to the MAN switch network segment, and from the OLT device directly connected to the MAN router network segment. This application also determines the MAN router matching the uplink port of the MAN switch using the physical topology data and logical link data corresponding to the uplink port of the MAN switch, and obtains the physical topology data and logical link data corresponding to the Ethernet interface of the MAN router. This allows for accurate and complete acquisition of network topology data from the MAN switch to the MAN router network segment. Thus, the accuracy and completeness of the network topology data from the OLT device connected to the MAN router network segment via the MAN switch are guaranteed. This application embodiment generates a network topology based on the first topology data, the second topology data, and the third topology data. This network topology can cover the PON access network to the data metropolitan area network, thereby supporting end-to-end automatic activation of PON leased lines.

[0079] In one embodiment, the OLT device includes multiple uplink ports to obtain the first topology data of the OLT device, which may specifically include:

[0080] Collect physical topology data and logical link data corresponding to each uplink port of the OLT device.

[0081] Based on the physical topology data and logical link data corresponding to each uplink port of the OLT device, a topology data dictionary for the OLT device is generated. The topology data dictionary for the OLT device includes the identification information of the OLT device, the identification information of each uplink port of the OLT device, and the physical topology data and logical link data corresponding to each uplink port of the OLT device.

[0082] The physical topology data corresponding to each uplink port of the OLT device is judged to determine the type of the peer device of the uplink port of the OLT device.

[0083] When the uplink port of the OLT device is a metropolitan area network switch or metropolitan area network router, obtain the physical topology data and logical link data corresponding to the uplink port of the OLT device.

[0084] The uplink port of an OLT device can include the port on the OLT device used to connect to a metropolitan area network (MAN) switch or MAN router. For end-to-end automatic commissioning of PON leased lines, there are cases where the OLT device is directly connected to the MAN router, and cases where the OLT device is connected to the MAN router via a MAN switch. In this embodiment, when the peer device of the OLT device's uplink port is a MAN switch or MAN router, obtaining the physical topology data and logical link data corresponding to the OLT device's uplink port can filter out useless topology data, preventing the relevant configurations from being sent to the wrong device or port during automatic commissioning of the PON leased line. This reduces the risk of forming network path loops or incorrect network paths. Therefore, the efficiency and accuracy of obtaining the first topology data can be improved, thus ensuring end-to-end automatic commissioning of the PON leased line.

[0085] In one embodiment, the physical topology data and logical link data corresponding to each uplink port of the OLT device are collected respectively, which may specifically include:

[0086] The Link Layer Discovery Protocol (LLDP) is used to collect the physical topology data corresponding to each uplink port of the OLT device.

[0087] Collect logical link data corresponding to each uplink port of the OLT device.

[0088] In this embodiment, by collecting the physical topology data corresponding to the uplink port of the OLT device through LLDP, the efficient collection of physical topology data can be achieved, thereby improving the efficiency of network topology generation and thus improving the end-to-end automatic commissioning efficiency of PON leased lines.

[0089] In one embodiment, collecting physical topology data and logical link data corresponding to each uplink port of the OLT device may further include:

[0090] Obtain the MAC address information of the OLT device when the OLT device does not support LLDP.

[0091] The physical topology data corresponding to each uplink port of the OLT device is collected by using MAC address information.

[0092] Collect logical link data corresponding to each uplink port of the OLT device.

[0093] This embodiment can collect physical topology data corresponding to each uplink port of the OLT device using the OLT device's MAC address information, even when the OLT device does not support LLDP. This ensures the integrity of the network topology data, thereby guaranteeing the automatic end-to-end activation of the PON leased line. Furthermore, the network topology generation method according to this application embodiment can be applied to more types or versions of OLT devices, thus improving the applicability of the network topology generation method.

[0094] In one embodiment, obtaining the second topology data of the uplink device may specifically include:

[0095] The physical topology data and logical link data corresponding to each Ethernet interface of the uplink device are collected using LLDP.

[0096] Based on the physical topology data and logical link data corresponding to each Ethernet interface of the uplink device, a topology data dictionary for the uplink device is generated. The topology data dictionary for the uplink device includes the identification information of the uplink device, the identification information of each Ethernet interface of the uplink device, and the physical topology data and logical link data corresponding to each Ethernet interface of the uplink device.

[0097] The physical topology data corresponding to each Ethernet interface of the uplink device is judged to determine the peer device type of the Ethernet interface of the uplink device.

[0098] When the peer device of the Ethernet interface of the uplink device is a metropolitan area network (MAN) device or an OLT device, obtain the physical topology data and logical link data corresponding to the Ethernet interface of the uplink device. MAN devices include MAN switches and MAN routers.

[0099] In this embodiment, when the peer device of the Ethernet interface of the uplink device is a metropolitan area network (MAN) device or an OLT device, obtaining the physical topology data and logical link data corresponding to the Ethernet interface of the uplink device can filter out invalid LLDP information such as non-MAN devices connected to the OLT device, thereby avoiding the acquisition of useless topology data. This improves the efficiency and accuracy of acquiring the second topology data, thus ensuring the end-to-end automatic commissioning of the PON leased line.

[0100] In one embodiment, obtaining third topology data of a metropolitan area network router may specifically include:

[0101] The physical topology data and logical link data corresponding to each Ethernet interface of the metropolitan area network router are collected using LLDP.

[0102] Based on the physical topology data and logical link data corresponding to each Ethernet interface of the metropolitan area network (MAN) router, a topology data dictionary for the MAN router is generated. The topology data dictionary for the MAN router includes the identification information of the MAN router, the identification information of each Ethernet interface of the MAN router, and the physical topology data and logical link data corresponding to each Ethernet interface of the MAN router.

[0103] The physical topology data corresponding to each Ethernet interface of the metropolitan area network (MAN) router is analyzed to determine the peer device type of the Ethernet interface of the MAN router.

[0104] When the peer device of the Ethernet interface of the metropolitan area network (MAN) router is a MAN switch or a MAN router, obtain the physical topology data and logical link data corresponding to the Ethernet interface of the MAN router.

[0105] In this embodiment, when the peer device of the Ethernet interface of the metropolitan area network (MAN) router is a MAN switch or a MAN router, the physical topology data and logical link data corresponding to the Ethernet interface of the MAN router are then obtained. This allows for the filtering of invalid LLDP information, such as that from non-MAN devices connected to the MAN router, thus avoiding the acquisition of useless topology data. This improves the efficiency and accuracy of acquiring third-party topology data, thereby ensuring end-to-end automatic commissioning of the PON leased line.

[0106] To better describe the entire solution, based on the various implementation methods described above, the following is in conjunction with the appendix. Figures 3 to 8 Let's illustrate this with a concrete example. In this example, the network topology generation method can be achieved through methods such as... Figure 3 The PON leased line end-to-end network topology generation system shown is executed.

[0107] like Figure 3 As shown, the PON leased line end-to-end network topology generation system may include a PON access network OLT topology information acquisition module, a metropolitan area network switch topology information acquisition module, a metropolitan area network router topology information acquisition module, and a PON leased line end-to-end network topology generation module. Specifically, the PON access network OLT topology information acquisition module can be used to collect first topology data; the metropolitan area network switch topology information acquisition module can be used to collect second topology data corresponding to the metropolitan area network switch; the metropolitan area network router topology information acquisition module can be used to collect second and third topology data corresponding to the metropolitan area network router; and the PON leased line end-to-end network topology generation module can be used to generate the network topology.

[0108] In a PON leased line end-to-end network topology generation system, such as Figure 4As shown, the PON access network OLT topology information acquisition module may include an OLT system name acquisition module, an LLDP global enable module, an OLT uplink port acquisition module, an uplink port LLDP function enable module, an uplink port LLDP acquisition module, a topology information filtering module, an uplink port MAC address acquisition module, a protection group / aggregation group acquisition module, and an OLT topology data dictionary generation module.

[0109] The OLT system name acquisition module can be used to collect the standard system name (olt_system_name) of OLT devices; the LLDP global enable module can be used to perform LLDP enabling operations in OLT devices, resolving the problem of topology data acquisition failure caused by LLDP not being enabled; the OLT uplink port acquisition module can be used to analyze all active ports of OLT devices to determine the connection port (up_link_port) with the uplink MAN switch / router; the uplink port LLDP function enable module can be used to enable LLDP in the uplink port to support the acquisition of physical topology data of the uplink port through LLDP information, preventing topology data loss; the uplink port LLDP acquisition module can be used to collect uplink port LLDP peer device information, mainly including the peer device name (remote_device) and peer port number (remote_port); the topology information filtering module can be used for topology pruning, filtering useless topology data, preventing... The automatic configuration activation is prevented from being sent to the wrong device or port. The uplink MAC address acquisition module can be used to collect relevant MAC address information of the uplink port when the OLT device does not support LLDP, and generate a MAC address information table (port_mac_table_list) for matching the remote device membrane (remote_device) and remote port number (remote_port) using the MAC address. The protection group / aggregation group acquisition module can be used to collect the protection group (protect_group_id) and protection mode (protect-group) of the OLT device's uplink port. The OLT topology data dictionary generation module can be used to generate an OLT topology dictionary (topo_olt_dic) according to the data model definition based on the information obtained by the OLT system name acquisition module, the uplink LLDP acquisition module, the uplink MAC address acquisition module, and the protection group / aggregation group acquisition module.

[0110] Specifically, the OLT topology dictionary (topo_olt_dic) can be a nested dictionary. The key of the OLT topology dictionary can be olt_system_name, and the value can be a nested topology data dictionary. In the topology data dictionary, the key can be the port number of all uplink ports of the OLT device, and the value can be a list of topology information corresponding to the uplink ports. The topology information list can contain topology information fields. These topology information fields can contain information related to physical topology data, such as remote_device and remote_port, and information related to logical link data, such as protect_group_id and protect-group. In one embodiment, the topology information fields can also include port_mac_table_list. Through port_mac_table_list, information related to physical topology data, such as remote_device and remote_port, can be indirectly obtained. Based on the topology information fields, the first topology data of the OLT device's uplink ports can be obtained.

[0111] In a PON leased line end-to-end network topology generation system, such as Figure 5 As shown, the metropolitan area network switch topology information acquisition module may include a switch system name acquisition module, an ETH port acquisition module, a port MAC address acquisition module, a port role analysis module, a port LLDP acquisition module, a topology information filtering module, an aggregation group acquisition module, and a topology data dictionary generation module.

[0112] The switch system name acquisition module can be used to collect the standard system name (switch_system_name) of a metropolitan area network (MAN) switch; the ETH port acquisition module can be used to collect all active Ethernet interfaces (eth_port) of a MAN switch; the port MAC address acquisition module can be used to collect the relevant MAC address information of active ports of the switch and generate a MAC address information table (port_mac_table_list); the port role analysis module can be used to analyze the port role (port_role) based on the information of the device connected to the port peer; ports connected to MAN routers are called uplink ports, ports connected to OLT devices are called downlink ports, and ports connected to MAN switches are called cross-connect ports; the port LLDP acquisition module can be used to collect the MAC address information of the MAN switch peers. The end device information mainly includes the peer device name (remote_device) and peer port number (remote_port); the topology information filtering module can be used for topology pruning, filtering out useless topology data such as non-metropolitan area network devices connected to Ethernet interfaces; the aggregation group acquisition module can be used to collect the Eth-trunk group (eth_trunk_id) where the Ethernet interface is located; the topology data dictionary generation module can be used to generate a metropolitan area network switch topology dictionary (topo_switch_dic) according to the data model definition based on the information obtained by the switch system name acquisition module, ETH port acquisition module, port MAC address acquisition module, port role analysis module, port LLDP acquisition module, aggregation group acquisition module, etc.

[0113] Specifically, the metropolitan area network (MAN) switch topology dictionary (topo_switch_dic) can be a nested dictionary. The key of the MAN switch topology dictionary can be `switch_system_name`, and the value can be a nested topology data dictionary. In the topology data dictionary, the key can be the port numbers of all downlink, crosslink, and uplink ports of the MAN switch, and the value can be a list of topology information corresponding to the port. This topology information list can contain topology information fields. These topology information fields can include information related to physical topology data, such as `remote_device`, `remote_port`, and `port_role`, as well as information related to logical link data, such as `eth_trunk_id`. In one embodiment, the topology information fields can also include `port_mac_table_list`, through which information related to physical topology data, such as `remote_device`, `remote_port`, and `port_role`, can be indirectly obtained. Based on the topology information fields, second topology data corresponding to the MAN switch can be obtained.

[0114] In a PON leased line end-to-end network topology generation system, such as Figure 6As shown, the metropolitan area network router topology information acquisition module may include a router system name acquisition module, an ETH port acquisition module, a port role analysis module, a port LLDP acquisition module, a topology information filtering module, an aggregation group acquisition module, and a topology data dictionary generation module.

[0115] The router system name acquisition module can be used to collect the standard system name (router_system_name) of metropolitan area network (MAN) routers; the ETH port acquisition module can be used to collect all in-use Ethernet interfaces (eth_port) of MAN routers; the port role analysis module can be used to analyze the port role (port_role) based on the peer device information, where the port connected to the MAN router is the cross-connect port, and the port connected to the MAN switch or OLT device is the downstream port; the port LLDP acquisition module can be used to collect peer device information, mainly including the peer device name (remote_device) and peer port number (remote_port); the topology information filtering module can be used for topology pruning, filtering out useless topology data such as non-MAN devices; the aggregation group acquisition module can be used to collect the Eth-trunk group (eth_trunk_id) to which the Ethernet interface belongs; the topology data dictionary generation module can be used to generate a MAN router topology dictionary (topo_router_dic) according to the data model definition based on the information obtained by the router system name acquisition module, ETH port acquisition module, port role analysis module, port LLDP acquisition module, aggregation group acquisition module, etc.

[0116] Specifically, the metropolitan area network (MAN) router topology dictionary (topo_router_dic) can be a nested dictionary. The key of the MAN router topology dictionary can be `router_system_name`, and the value can be a nested topology data dictionary. In the topology data dictionary, the key can be the port numbers of all downlink and crosslink ports of the MAN router, and the value can be a list of topology information corresponding to each port. This topology information list can contain topology information fields. These fields can include information related to physical topology data, such as `remote_device`, `remote_port`, and `port_role`, as well as information related to logical link data, such as `eth_trunk_id`. Based on these topology information fields, the second and third topology data corresponding to the MAN router can be obtained.

[0117] The following is in conjunction with the appendix Figure 7Taking the end-to-end network topology generation of a PON leased line using an OLT device (system standard name: CQJB-ZiShuiZhongXue-OLT001-XX-XXXX) as an example, this application illustrates the network topology generation method. It should be noted that the following examples are merely for illustrative purposes and not for limiting the scope of this application.

[0118] like Figure 7 As shown, the network topology generation method may include steps S210 to S260.

[0119] S210, based on the system standard name of the OLT device, queries the OLT topology dictionary corresponding to the OLT device to obtain the first topology data of the OLT device.

[0120] Specifically, the topology data dictionary corresponding to the OLT device can be obtained using "CQJB-ZiShuiZhongXue-OLT001-XX-XXXX" as the key. The topology data dictionary is then queried to obtain the two uplink ports xge0 / 19 / 0 and xge0 / 20 / 0 corresponding to the OLT device. Then, using "xge0 / 19 / 0" and "xge0 / 20 / 0" as keys, the information such as protect_group_id, protect_type, remote_device, and remote_port in the corresponding topology information list is retrieved. The topology information is then filtered based on remote_device to remove useless topology data such as the peer OLT device or serial links, thus obtaining the first topology data of the OLT device. In one embodiment, when the OLT device does not support LLDP, the remote_device and remote_port information can be obtained by searching the port_mac_table_lis in the topology information list. In this way, the first topology data of the OLT device as shown in Table 1 can be obtained.

[0121] Table 1

[0122]

[0123] S220, Based on the first topology data, determine the system standard name of at least one uplink device that matches the uplink port of the OLT device.

[0124] Specifically, based on the first topology data shown in Table 1 above, the system standard name of the metropolitan area network switch that matches the uplink port xge0 / 19 / 0 of the OLT device is determined to be CQXPF-MC-CMNET-XX01-XXXX, and the system standard name of the metropolitan area network switch that matches the uplink port xge0 / 20 / 0 of the OLT device is CQXPF-MC-CMNET-XX02-XXXX.

[0125] Step S230: Based on the system standard name of the uplink device, query the uplink device topology dictionary corresponding to the uplink device to obtain the second topology data of the uplink device.

[0126] Specifically, in this example, the topology data dictionary corresponding to the metropolitan area network (MAN) switch can be obtained using "CQXPF-MC-CMNET-XX01-XXXX" as the key. Querying the topology data dictionary yields the four Ethernet interfaces corresponding to the MAN switch: xge1 / 1 / 3, xge1 / 2 / 1, xge1 / 1 / 4, and xg1 / 2 / 4. Then, using "xge1 / 1 / 3", "xge1 / 2 / 1", "xge1 / 1 / 4", and "xge1 / 2 / 4" as keys, the port_role, eth_trunk_id, remote_device, and remote_port information in the corresponding topology information list are queried. The topology information is then filtered based on remote_device to remove useless topology data such as non-MAN devices, thus obtaining the second topology data of the MAN switch. In this way, the second topology data of the MAN switch CQXPF-MC-CMNET-XX01-XXXX, as shown in Table 2, can be obtained.

[0127] Table 2

[0128]

[0129] Similarly, using "CQXPF-MC-CMNET-XX02-XXXX" as the key, the second topology data of the MAN switch CQXPF-MC-CMNET-XX02-XXXX, as shown in Table 3, can be obtained. In this example, the uplink devices matched with the uplink ports of the OLT device are all MAN switches; therefore, the second topology data only includes the second topology data corresponding to the MAN switches. It is easy to understand that in some embodiments, if the uplink devices matched with the uplink ports of the OLT device also include MAN routers, the second topology data may also include the second topology data corresponding to the MAN routers.

[0130] Table 3

[0131]

[0132] S240, when the uplink device includes a metropolitan area network (MAN) switch, determine the system standard name of at least one MAN router that matches the uplink port of the MAN switch based on the physical topology data and logical link data corresponding to the uplink port in the Ethernet interface of the MAN switch.

[0133] Specifically, based on the second topology data shown in Table 2 above, the system standard name of the metropolitan area network router that matches the uplink ports xge1 / 1 / 4 and xge1 / 2 / 4 of the metropolitan area network switch CQXPF-MC-CMNET-XX01-XXXX can be determined as CQXPF-PA-CMNET-BAS01-XX-XXXX, and the system standard name of the metropolitan area network router that matches the uplink ports xge1 / 1 / 4 and xge1 / 2 / 4 of the metropolitan area network switch CQXPF-MC-CMNET-XX02-XXXX can be determined as CQXPF-PA-CMNET-BAS02-XX-XXXX.

[0134] S250 queries the metropolitan area network (MAN) router topology dictionary corresponding to the MAN router based on the system standard name of the MAN router to obtain the third topology data of the MAN router.

[0135] Specifically, the topology data dictionary corresponding to the metropolitan area network router can be obtained using "CQXPF-PA-CMNET-BAS01-XX-XXXX" as the key. The topology data dictionary is then queried to obtain the three Ethernet interfaces xge1 / 3 / 1, xge1 / 12 / 1, and xge1 / 12 / 4 corresponding to the metropolitan area network switch. Then, using "xge1 / 3 / 1", "xge1 / 12 / 1", and "xge1 / 12 / 4" as keys, the port_role, eth_trunk_id, remote_device, and remote_port information in the corresponding topology information list are queried. The topology information is then filtered based on remote_device to remove useless topology data such as non-metropolitan area network devices, thus obtaining the third topology data of the metropolitan area network router CQXPF-PA-CMNET-BAS01-XX-XXXX. Similarly, using "CQXPF-PA-CMNET-BAS02-XX-XXXX" as the key, the third topology data of the metropolitan area network router CQXPF-PA-CMNET-BAS02-XX-XXXX can be obtained. Thus, the third topology data of the metropolitan area network router as shown in Table 4 can be obtained.

[0136] Table 4

[0137]

[0138] S260 generates a network topology from the OLT device to the metropolitan area network router based on the first topology data, the second topology data, and the third topology data.

[0139] Specifically, the network topology from the OLT device to the metropolitan area network router can be as follows: Figure 8 As shown.

[0140] Based on the same inventive concept, embodiments of this application also provide a network topology generation device.

[0141] like Figure 9 As shown, the network topology generation device 300 may include an acquisition module 301, a determination module 302, and a generation module 303.

[0142] The acquisition module 301 is used to acquire the first topology data of the OLT device. The first topology data includes physical topology data and logical link data corresponding to the uplink port of the OLT device.

[0143] The determination module 302 is used to determine, based on the first topology data, at least one uplink device that matches the uplink port of the OLT device, including a metropolitan area network router or a metropolitan area network switch.

[0144] The acquisition module 301 is also used to acquire the second topology data of the uplink device, which includes physical topology data and logical link data corresponding to the Ethernet interface of the uplink device.

[0145] The determining module 302 is further configured to, when the uplink device includes a metropolitan area network (MAN) switch, determine at least one MAN router that matches the uplink port of the MAN switch based on the physical topology data and logical link data corresponding to the uplink port in the Ethernet interface of the MAN switch.

[0146] The acquisition module 301 is also used to acquire the third topology data of the metropolitan area network router, which includes physical topology data and logical link data corresponding to the Ethernet interface of the metropolitan area network router.

[0147] The generation module 303 is used to generate a network topology from the OLT device to the metropolitan area network router based on the first topology data, the second topology data, and the third topology data.

[0148] The network topology generation device in this application embodiment can determine the uplink device matching the uplink port of the OLT device using the physical topology data and logical link data corresponding to the uplink port of the OLT device, and obtain the physical topology data and logical link data corresponding to the Ethernet interface of the uplink device. This allows for accurate and complete acquisition of network topology data from the OLT device to the metropolitan area network (MAN) switch network segment, and from the OLT device directly connected to the MAN router network segment. This application embodiment also determines the MAN router matching the uplink port of the MAN switch using the physical topology data and logical link data corresponding to the uplink port of the MAN switch, and obtains the physical topology data and logical link data corresponding to the Ethernet interface of the MAN router. This allows for accurate and complete acquisition of network topology data from the MAN switch to the MAN router network segment. Thus, the accuracy and completeness of the network topology data from the OLT device connected to the MAN router network segment via the MAN switch are guaranteed. This application embodiment generates a network topology based on the first topology data, the second topology data, and the third topology data. This network topology can cover the PON access network to the data metropolitan area network, thereby supporting end-to-end automatic activation of PON leased lines.

[0149] In one embodiment, the OLT device includes multiple uplink ports, and the network topology generation device may further include a data acquisition module and a judgment module.

[0150] The acquisition module is used to acquire the first topology data of the OLT device, which may specifically include:

[0151] The acquisition module is used to collect physical topology data and logical link data corresponding to each uplink port of the OLT device.

[0152] The generation module is used to generate a topology data dictionary for the OLT device based on the physical topology data and logical link data corresponding to each uplink port of the OLT device. The topology data dictionary of the OLT device includes the identification information of the OLT device, the identification information of each uplink port of the OLT device, and the physical topology data and logical link data corresponding to each uplink port of the OLT device.

[0153] The judgment module is used to judge the physical topology data corresponding to each uplink port of the OLT device to determine the peer device type of the uplink port of the OLT device.

[0154] The acquisition module is used to acquire the physical topology data and logical link data corresponding to the uplink port of the OLT device when the peer device of the uplink port is a metropolitan area network switch or metropolitan area network router.

[0155] In one embodiment, the acquisition module is used to acquire physical topology data and logical link data corresponding to each uplink port of the OLT device, which may specifically include:

[0156] The acquisition module is used to collect physical topology data corresponding to each uplink port of the OLT device through the Link Layer Discovery Protocol (LLDP).

[0157] The acquisition module is used to acquire logical link data corresponding to each uplink port of the OLT device.

[0158] In one embodiment, the acquisition module is used to acquire physical topology data and logical link data corresponding to each uplink port of the OLT device, and may further include:

[0159] The acquisition module is used to obtain the MAC address information of the OLT device when the OLT device does not support LLDP.

[0160] The acquisition module is used to collect physical topology data corresponding to each uplink port of the OLT device through MAC address information.

[0161] The acquisition module is used to acquire logical link data corresponding to each uplink port of the OLT device.

[0162] In one embodiment, the acquisition module is used to acquire the second topology data of the uplink device, which may specifically include:

[0163] The acquisition module is used to acquire physical topology data and logical link data corresponding to each Ethernet interface of the uplink device via LLDP.

[0164] The generation module is used to generate a topology data dictionary for the uplink device based on the physical topology data and logical link data corresponding to each Ethernet interface of the uplink device. The topology data dictionary for the uplink device includes the identification information of the uplink device, the identification information of each Ethernet interface of the uplink device, and the physical topology data and logical link data corresponding to each Ethernet interface of the uplink device.

[0165] The judgment module is used to judge the physical topology data corresponding to each Ethernet interface of the uplink device to determine the peer device type of the Ethernet interface of the uplink device.

[0166] The acquisition module is used to acquire the physical topology data and logical link data corresponding to the Ethernet interface of the uplink device when the peer device of the uplink device is a metropolitan area network device or an OLT device. The metropolitan area network device includes metropolitan area network switches and metropolitan area network routers.

[0167] In one embodiment, the acquisition module is used to acquire third topology data of the metropolitan area network router, which may specifically include:

[0168] The acquisition module is used to collect physical topology data and logical link data corresponding to each Ethernet interface of the metropolitan area network router via LLDP.

[0169] The generation module is used to generate a topology data dictionary for the metropolitan area network (MAN) router based on the physical topology data and logical link data corresponding to each Ethernet interface of the MAN router. The topology data dictionary of the MAN router includes the identification information of the MAN router, the identification information of each Ethernet interface of the MAN router, and the physical topology data and logical link data corresponding to each Ethernet interface of the MAN router.

[0170] The judgment module is used to judge the physical topology data corresponding to each Ethernet interface of the metropolitan area network router to determine the peer device type of the Ethernet interface of the metropolitan area network router.

[0171] The acquisition module is used to acquire the physical topology data and logical link data corresponding to the Ethernet interface of the metropolitan area network (MAN) router when the peer device of the Ethernet interface of the MAN router is a MAN switch or a MAN router.

[0172] The network topology generation device provided in this application embodiment can achieve... Figure 2 The various processes implemented in the method implementation examples will not be described again here to avoid repetition.

[0173] Figure 10 A schematic diagram of the hardware structure of the network topology generation device provided in an embodiment of this application is shown.

[0174] The network topology generation device may include a processor 401 and a memory 402 storing computer program instructions.

[0175] Specifically, the processor 401 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0176] Memory 402 may include mass storage for data or instructions. For example, and not limitingly, memory 402 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 402 may include removable or non-removable (or fixed) media. Where appropriate, memory 402 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 402 is non-volatile solid-state memory.

[0177] Memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the methods according to one aspect of this disclosure.

[0178] The processor 401 reads and executes computer program instructions stored in the memory 402 to implement any of the network topology generation methods in the above embodiments.

[0179] As an example, the network topology generation device may also include a communication interface 403 and a bus 410. Wherein, such as Figure 10 As shown, the processor 401, memory 402, and communication interface 403 are connected through bus 410 and complete communication with each other.

[0180] The communication interface 403 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0181] Bus 410 includes hardware, software, or both, that couples components of an online data traffic metering device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 410 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, this application contemplates any suitable bus or interconnect.

[0182] The property planning equipment can execute the property planning method in the embodiments of this application, thereby achieving a combination Figure 2 and Figure 9 The network topology generation method and apparatus are described.

[0183] Furthermore, in conjunction with the network topology generation methods described in the above embodiments, this application embodiment can provide a computer storage medium for implementation. This computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the network topology generation methods described in the above embodiments.

[0184] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0185] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0186] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0187] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0188] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A method for generating network topology, characterized in that, include: Acquiring first topology data of an optical line terminal (OLT) device, the first topology data includes physical topology data and logical link data corresponding to the uplink ports of the OLT device. The OLT device includes multiple uplink ports. The acquisition of the first topology data of the optical line terminal (OLT) device includes: Physical topology data and logical link data corresponding to each uplink port of the OLT device are collected respectively. Based on the physical topology data and logical link data corresponding to each uplink port of the OLT device, a topology data dictionary of the OLT device is generated. The topology data dictionary of the OLT device includes the identification information of the OLT device, the identification information of each uplink port of the OLT device, and the physical topology data and logical link data corresponding to each uplink port of the OLT device respectively. The physical topology data corresponding to each uplink port of the OLT device is judged to determine the peer device type of the uplink port of the OLT device. If the peer device type of the uplink port of the OLT device is a metropolitan area network switch or a metropolitan area network router, the physical topology data and logical link data corresponding to the uplink port of the OLT device are obtained. Based on the first topology data, at least one uplink device matching the uplink port of the OLT device is determined, and the uplink device includes a metropolitan area network router or a metropolitan area network switch. Obtain the second topology data of the uplink device, the second topology data including physical topology data and logical link data corresponding to the Ethernet interface of the uplink device; When the uplink device includes a metropolitan area network (MAN) switch, at least one MAN router that matches the uplink port of the MAN switch is determined based on the physical topology data and logical link data corresponding to the uplink port in the Ethernet interface of the MAN switch. Obtain the third topology data of the metropolitan area network router, the third topology data including physical topology data and logical link data corresponding to the Ethernet interface of the metropolitan area network router; Based on the first topology data, the second topology data, and the third topology data, a network topology from the OLT device to the metropolitan area network router is generated.

2. The method according to claim 1, characterized in that, The process of collecting physical topology data and logical link data corresponding to each uplink port of the OLT device includes: The Link Layer Discovery Protocol (LLDP) is used to collect the physical topology data corresponding to each uplink port of the OLT device. Collect logical link data corresponding to each uplink port of the OLT device.

3. The method according to claim 2, characterized in that, The process of collecting physical topology data and logical link data corresponding to each uplink port of the OLT device also includes: If the OLT device does not support LLDP, obtain the MAC address information of the OLT device; The physical topology data corresponding to each uplink port of the OLT device is collected using the MAC address information; Collect logical link data corresponding to each uplink port of the OLT device.

4. The method according to claim 1, characterized in that, The step of obtaining the second topology data of the uplink device includes: The physical topology data and logical link data corresponding to each Ethernet interface of the uplink device are collected using LLDP. Based on the physical topology data corresponding to each Ethernet interface of the uplink device and the logical link data, a topology data dictionary for the uplink device is generated. The topology data dictionary for the uplink device includes the identification information of the uplink device, the identification information of each Ethernet interface of the uplink device, and the physical topology data and logical link data corresponding to each Ethernet interface of the uplink device, respectively. The physical topology data corresponding to each Ethernet interface of the uplink device is judged to determine the peer device type of the Ethernet interface of the uplink device; When the peer device type of the Ethernet interface of the uplink device is a metropolitan area network (MAN) device or an OLT device, the physical topology data and logical link data corresponding to the Ethernet interface of the uplink device are obtained. The MAN device includes MAN switches and MAN routers.

5. The method according to claim 1, characterized in that, The acquisition of the third topology data of the metropolitan area network router includes: The physical topology data and logical link data corresponding to each Ethernet interface of the metropolitan area network router are collected using LLDP. Based on the physical topology data corresponding to each Ethernet interface of the metropolitan area network router and the logical link data, a topology data dictionary of the metropolitan area network router is generated. The topology data dictionary of the metropolitan area network router includes the identification information of the metropolitan area network router, the identification information of each Ethernet interface of the metropolitan area network router, and the physical topology data and logical link data corresponding to each Ethernet interface of the metropolitan area network router respectively. The physical topology data corresponding to each Ethernet interface of the metropolitan area network router is judged to determine the peer device type of the Ethernet interface of the metropolitan area network router. When the peer device type of the Ethernet interface of the metropolitan area network router is a metropolitan area network switch or a metropolitan area network router, obtain the physical topology data and logical link data corresponding to the Ethernet interface of the metropolitan area network router.

6. A network topology generation device, characterized in that, include: The acquisition module is used to acquire first topology data of the OLT device. The first topology data includes physical topology data and logical link data corresponding to the uplink ports of the OLT device. The OLT device includes multiple uplink ports. The acquisition module is used to: Physical topology data and logical link data corresponding to each uplink port of the OLT device are collected respectively. Based on the physical topology data and logical link data corresponding to each uplink port of the OLT device, a topology data dictionary of the OLT device is generated. The topology data dictionary of the OLT device includes the identification information of the OLT device, the identification information of each uplink port of the OLT device, and the physical topology data and logical link data corresponding to each uplink port of the OLT device respectively. The physical topology data corresponding to each uplink port of the OLT device is judged to determine the peer device type of the uplink port of the OLT device. If the peer device type of the uplink port of the OLT device is a metropolitan area network switch or a metropolitan area network router, the physical topology data and logical link data corresponding to the uplink port of the OLT device are obtained. The determination module is used to determine, based on the first topology data, at least one uplink device that matches the uplink port of the OLT device, wherein the uplink device includes a metropolitan area network router or a metropolitan area network switch. The acquisition module is further configured to acquire the second topology data of the uplink device, the second topology data including physical topology data and logical link data corresponding to the Ethernet interface of the uplink device; The determining module is further configured to, when the uplink device includes a metropolitan area network (MAN) switch, determine at least one MAN router that matches the uplink port of the MAN switch based on the physical topology data and logical link data corresponding to the uplink port in the Ethernet interface of the MAN switch. The acquisition module is further configured to acquire third topology data of the metropolitan area network router, the third topology data including physical topology data and logical link data corresponding to the Ethernet interface of the metropolitan area network router; The generation module is used to generate a network topology from the OLT device to the metropolitan area network router based on the first topology data, the second topology data, and the third topology data.

7. An electronic device, characterized in that, The device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the network topology generation method as described in any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the network topology generation method as described in any one of claims 1-5.

9. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device performs the network topology generation method as described in any one of claims 1-5.

Images