Network abstraction method, apparatus, and storage medium

Abstract

The application provides a network abstraction method and device and a storage medium, relates to the technical field of communication, and can abstract the physical topology of device content. The method comprises the following steps: acquiring the physical topology of a target network and the physical topology of at least one node in the target network; the physical topology of the target network comprises at least one of the following: a node, a link and a port; the physical topology of the node comprises at least one of the following: a hardware module, a hardware module link and a hardware port; the physical topology of the target network and the physical topology of the at least one node are abstracted, and the abstracted topology of the target network is determined; the abstracted topology of the target network comprises at least one of the following: abstracted information of a node, abstracted information of a link, abstracted information of a port, node abstracted information of a hardware module, abstracted information of a hardware module link and abstracted information of a hardware port. The embodiment of the application is used in a network abstraction process.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a network abstraction method, apparatus and storage medium. Background Technology

[0002] In related technologies, when abstracting and controlling traffic-engineered networks (ACTN) controllers abstract transport networks, they typically only abstract individual nodes, links, and ports within the transport network.

[0003] However, with the development of devices in current transmission networks, a single device may include multiple hardware components (boards) with different functions, and different hardware components within the same device may have different functions. Current abstraction methods cannot represent the information of the device's hardware, the link information between hardware components, and the port information of the hardware. This will prevent the ACTN controller from controlling the hardware of devices in the transmission network. Summary of the Invention

[0004] This application provides a network abstraction method, apparatus, and storage medium capable of abstracting the physical topology of device content.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] Firstly, a network abstraction method is provided, comprising: obtaining the physical topology of a target network and the physical topology of at least one node in the target network; the physical topology of the target network includes at least one of the following: node, link, and port; the physical topology of the node includes at least one of the following: hardware module, hardware module link, and hardware port; abstracting the physical topology of the target network and the physical topology of at least one node to determine the abstract topology of the target network; the abstract topology of the target network includes at least one of the following: abstract information of nodes, abstract information of links, abstract information of ports, abstract information of nodes of hardware modules, abstract information of links of hardware modules, and abstract information of hardware ports.

[0007] In conjunction with the first aspect above, in one possible implementation, the physical topology of a node includes: a first hardware module and a second hardware module; a node is a node in at least one node; abstracting the physical topology of a node includes: abstracting the first hardware module and the second hardware module into first node abstract information; the first node abstract information is used to represent the physical topology of the first hardware module and the second hardware module.

[0008] In conjunction with the first aspect above, in one possible implementation, the physical topology of a node includes: a third hardware module; a node is a node among at least one node; abstracting the physical topology of a node includes: abstracting the third hardware module into second node abstract information and third node abstract information; the second node abstract information and the third node abstract information are used to jointly represent the physical topology of the third hardware module.

[0009] In conjunction with the first aspect above, in one possible implementation, at least one node includes an optical network device; the physical topology of the optical network device includes: boards, links between boards, and ports of boards; the abstract topology of the optical network device includes: node abstract information of boards, abstract information of links between boards, and abstract information of ports of boards.

[0010] In a second aspect, a network abstraction device is provided, comprising: an acquisition unit and a processing unit; the acquisition unit is configured to acquire the physical topology of a target network and the physical topology of at least one node in the target network; the physical topology of the target network includes at least one of the following: node, link, and port; the physical topology of the node includes at least one of the following: hardware module, hardware module link, and hardware port; the processing unit is configured to abstract the physical topology of the target network and the physical topology of at least one node to determine an abstract topology of the target network; the abstract topology of the target network includes at least one of the following: abstract information of nodes, abstract information of links, abstract information of ports, abstract information of nodes of hardware modules, abstract information of links of hardware modules, and abstract information of hardware ports.

[0011] In conjunction with the second aspect above, in one possible implementation, the physical topology of the node includes: a first hardware module and a second hardware module; and a processing unit specifically used to: abstract the first hardware module and the second hardware module into first node abstract information; the first node abstract information is used to represent the physical topology of the first hardware module and the second hardware module.

[0012] In conjunction with the second aspect above, in one possible implementation, the physical topology of the node includes: a third hardware module; and a processing unit, specifically used to: abstract the third hardware module into second node abstract information and third node abstract information; the second node abstract information and the third node abstract information are used to jointly represent the physical topology of the third hardware module.

[0013] In conjunction with the second aspect above, in one possible implementation, at least one node includes an optical network device; the physical topology of the optical network device includes: boards, links between boards, and ports of boards; the abstract topology of the optical network device includes: node abstract information of boards, abstract information of links between boards, and abstract information of ports of boards.

[0014] Thirdly, this application provides a network abstraction device, which includes: a processor and a communication interface; the communication interface and the processor are coupled, and the processor is used to run computer programs or instructions to implement the network abstraction method as described in the first aspect and any possible implementation of the first aspect.

[0015] Fourthly, this application provides a computer-readable storage medium storing instructions that, when executed on a terminal, cause the terminal to perform the network abstraction method as described in the first aspect and any possible implementation thereof.

[0016] In this application, the names of the aforementioned network abstraction devices do not limit the devices or functional modules themselves. In actual implementation, these devices or functional modules may appear under other names. As long as the functions of each device or functional module are similar to those of this invention, they fall within the scope of the claims of this invention and their equivalents.

[0017] These or other aspects of the invention will become more apparent from the following description.

[0018] The technical solution provided in this application offers at least the following advantages: When abstracting a target network, the network abstraction device not only abstracts the physical topology of the target network but also the physical topology of at least one node in the target network. Therefore, the network abstraction device can obtain an abstraction result at the granularity of its internal hardware modules. Based on this abstraction result at the granularity of the internal hardware modules, the ACTN controller can manage the target network at the granularity of its internal hardware modules.

[0019] For example, when performing business planning in the ACTN controller, the performance of the internal hardware modules of the device can be directly determined, and then business planning can be carried out based on the performance of the internal hardware modules of the device, so as to achieve more refined business planning.

[0020] For example, when performing fault location in the ACTN controller, the fault can be located directly in the specific hardware module based on the current state of the internal hardware module of the device, thus achieving more accurate fault location. Attached Figure Description

[0021] Figure 1 A schematic diagram of the ACTN structure provided in this application;

[0022] Figure 2 A system architecture diagram of a communication network provided in this application;

[0023] Figure 3 An abstract topology diagram of a transmission network provided in this application;

[0024] Figure 4 A flowchart of a network abstraction method provided in this application;

[0025] Figure 5 A schematic diagram of the internal hardware structure of an optical network device provided in this application;

[0026] Figure 6 An abstract topology diagram of the internal structure of an optical network device is provided in this application;

[0027] Figure 7 This is a schematic diagram of the structure of a network abstraction device provided in this application. Detailed Implementation

[0028] The network abstraction method and apparatus provided in the embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0029] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0030] The terms "first" and "second," etc., used in the specification and drawings of this application are used to distinguish different objects or to distinguish different treatments of the same object, rather than to describe a specific order of objects.

[0031] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0032] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0033] In order to implement the network abstraction method provided in the embodiments of this application, the embodiments of this application provide a network abstraction device for executing the network abstraction method. The network abstraction device may be the network abstraction device involved in this application, or a module in the network abstraction device; or a chip in the network abstraction device, or other devices for executing the network abstraction method. This application does not limit the scope of the application.

[0034] The following explanations of the terms used in the embodiments of this application are provided to facilitate the reader's understanding:

[0035] 1. ACTN Controller

[0036] The ACTN controller is a hierarchical controller proposed based on the specific scenarios and business needs of operators. The ACTN controller can realize the clustering and virtualization management of the transmission network, shield network differences, and provide users with a single virtual network through a hierarchical abstract model.

[0037] like Figure 1 The diagram shows the system architecture of the ACTN controller system. The ACTN controller system includes at least one customer network controller (CNC), a multi-domain service coordinator (MDSC), and at least one physical network controller (PNC). The PNC is connected to the transport network and is used to monitor the physical topology of the transport network. The MDSC is connected to the PNC and uses a topology abstraction-based method to manage the transport networks connected to each PNC.

[0038] 2. Transmission Network

[0039] Common transport networks include optical transport networks (OTN), packet-enhanced OTN networks, and transport-oriented multi-protocol label switching (MPLS-TP) networks. Transport networks are primarily used as data transmission channels for data transmission.

[0040] 3. Abstraction

[0041] In the ACTN controller, since one MDSC connects to multiple PNCs, the MDSC needs to manage the transport networks connected to these multiple PNCs. This may result in a large load on the MDSC and affect its working performance.

[0042] The PNC abstracts the physical topology of the transport network to obtain an abstract topology. The PNC then sends this abstract topology to the MDSC. The MDSC manages the transport network based on this abstract topology, allowing it to ignore less important nodes and focus on managing crucial ones. This significantly reduces the load on the MDSC.

[0043] 4. White Abstract

[0044] White abstraction is not abstraction. MDSC has full topology information of the transport network. MDSC can complete path calculation and establish an end-to-end path in the transport network based on the full topology information of the transport network.

[0045] 5. Black Abstract

[0046] Black abstraction involves abstracting a transport network as a virtual node. The MDSC needs to send path calculation requirements to the PNC. The PNC is responsible for creating services within the domain (i.e., within the transport network; a transport network is called a domain). The MDSC is responsible for cross-domain coordination.

[0047] 6. Gray Abstraction

[0048] Gray abstraction lies between black and white abstraction, and has two types: the first is the abstracted boundary node of a single domain; the second is the abstracted single-domain boundary node and some internal virtual nodes.

[0049] There are two ways to perform gray abstraction. The first is to automatically generate an abstract topology through configuration information, and the second is to generate a supplementary topology on demand based on path calculation requirements.

[0050] 7. Physical Topology

[0051] The physical topology of a transport network reflects the connections between various network entities and devices. In the physical topology of a transport network, each device is considered a point, and the links between devices are considered lines. This connection relationship between points and lines represents the network structure of the transport network.

[0052] 8. Abstract Topology

[0053] Abstract topology is the topology obtained by abstracting the physical topology of a transmission network according to preset abstraction rules (such as the white abstraction, black abstraction, or gray abstraction mentioned above).

[0054] The terms used in the embodiments of this application have been explained above.

[0055] The embodiments of this application can be applied to, for example... Figure 2 In the communication network 200 shown, such as Figure 2 As shown, the communication network 200 includes: MDSC 201, at least one CNC 202, and at least one PNC 203. The communication network 200 also includes network 1, network 2, and network 3. Figure 2The diagram shows the physical topology of Network 1, Network 2, and Network 3. The interface between CNC202 and MDSC201 is the CNC-MDSC201 interface (CMI), and the interface between MDSC201 and PNC203 is the MDSC-PNC interface (MPI).

[0056] The CNC202 is responsible for managing the resources of the transport network nodes and can also obtain virtual network services provided by the operator from the MDSC201 through the CMI interface. The CNC202 can also obtain resource information of the edge nodes of the transport network by negotiating with the MDSC201.

[0057] PNC203 is responsible for configuring the nodes of the transport network it is connected to. For example, PNC1203 is responsible for configuring the nodes in network 1, which includes nodes A, B, C, D, and E. Similarly, PNC2203 is responsible for configuring the nodes in network 2, which includes nodes I, J, K, L, M, and N. PNC3203 is responsible for configuring the nodes in network 3, which includes nodes F, G, and H. Network 1, network 2, or network 3 can be a packet network, an OTN network, a packet-enhanced OTN network, or an MPLS-TP network, etc., and this application does not limit this. PNC203 can also monitor the physical and virtual topologies of the corresponding networks and can transmit topology information to MDSC201.

[0058] The MDSC201, located between the CNC202 and PNC203, provides functions such as cross-domain coordination, multi-domain coordination, virtualization / abstraction, service mapping / conversion, and virtual service coordination. One MDSC201 can correspond to multiple PNC203s, enabling multi-domain coordination through these PNCs. The MDSC201 separates network control and service control from physical network technology, allowing for the selection of appropriate technologies to create virtual networks that meet business needs. This allows users to focus more on their specific business requirements, improving user experience.

[0059] It should be noted that network 1 includes nodes, links, and ports. (Combined with...) Figure 2 It can be seen that network 1 includes nodes A, B, C, D, and E. Network 1 also includes links AB, BC, AD, DE, BD, and CE. In addition, network 1 includes ports 1 through 12.

[0060] Networks 2 and 3 also include nodes, links, and ports. For details regarding the nodes, links, and ports included in Networks 2 and 3, please refer to [link to relevant documentation]. Figure 2 The nodes, links, and ports shown are not described further here.

[0061] The PNC203 can abstract the physical topology of network 1, network 2 and network 3 respectively to obtain the corresponding abstract topology.

[0062] like Figure 3 As shown, Figure 3 The abstract topologies of network 1, network 2, and network 3 are shown.

[0063] It's important to note that after PNC abstracts the network, it abstracts nodes as nodes and ports as termination points (TPs). For example, for node A in network 1, the abstract topology obtained by PNC after abstracting node A is nodeA'. For port 1 in network 1, the abstract topology obtained by PNC after abstracting port 1 is TP1. In other words, the abstract topology corresponding to node A in network 1 is nodeA', and the abstract topology of port 1 in network 1 is TP1.

[0064] The following, combined with Figure 2 and Figure 3 This document details the process by which the PNC abstracts the physical topology of network 1 to obtain the abstract topology of network 1; the process by which the PNC abstracts the physical topology of network 2 to obtain the abstract topology of network 2; and the process by which the PNC abstracts the physical topology of network 3 to obtain the abstract topology of network 3.

[0065] 1. PNC performs gray abstraction on network 1. The abstract topology of network 1 does not include nodes B and D. In other words, MDSC cannot perceive nodes B and D based on the abstract topology of network 1, nor can MDSC perceive the ports on nodes B and D or the links between nodes B and D.

[0066] Specifically, for nodes in network 1, the PNC abstracts the physical topology of node A, resulting in an abstract topology of A'. The PNC abstracts the physical topology of node C, resulting in an abstract topology of C'. The PNC abstracts the physical topology of node E, resulting in an abstract topology of E'.

[0067] It should be noted that nodes B and D in network 1 do not have corresponding abstract topologies; therefore, MDSC is unable to perceive nodes B and D in network 1.

[0068] For the links in network 1, the PNC abstracts the physical topology of link ABC, resulting in an abstract topology of A'-C'. The PNC abstracts the physical topology of link ADE, resulting in an abstract topology of A'-E'. The PNC abstracts the physical topology of link CE, resulting in an abstract topology of C'-E'.

[0069] It should be noted that links AB, BC, AD, DE, and BD in network 1 do not have corresponding abstract topologies. Therefore, MDSC cannot perceive links AB, BC, AD, DE, and BD in network 1.

[0070] For ports in network 1, the PNC abstracts the physical topology of port 1, resulting in an abstract topology of TP1. The PNC abstracts the physical topology of port 2, resulting in an abstract topology of TP2. The PNC abstracts the physical topology of port 3, resulting in an abstract topology of TP3. The PNC abstracts the physical topology of port 4, resulting in an abstract topology of TP4. The PNC abstracts the physical topology of port 5, resulting in an abstract topology of TP5. The PNC abstracts the physical topology of port 6, resulting in an abstract topology of TP6.

[0071] It should be noted that ports 7, 8, 9, 10, 11 and 12 in network 1 do not have corresponding abstract topologies. Therefore, MDSC cannot be aware of ports 7, 8, 9, 10, 11 and 12 in network 1.

[0072] 2. PNC also performs gray abstraction on network 2. The specific abstraction process of network 2, as well as the correspondence between the abstract topology and the physical topology, is similar to that of transport network 1, and will not be elaborated here.

[0073] 3. PNC performs a white abstraction of network 3. The abstract topology of network 3 includes all physical topology information of network 3. That is to say, MDSC can perceive all nodes, links, and ports in network 3.

[0074] Specifically, for nodes in network 3, the PNC abstracts the physical topology of node F, resulting in an abstract topology of F'. The PNC abstracts the physical topology of node G, resulting in an abstract topology of G'. The PNC abstracts the physical topology of node H, resulting in an abstract topology of H'.

[0075] For the links in network 3, the PNC abstracts the physical topology of link FH, resulting in an abstract topology of F'-H'. The PNC abstracts the physical topology of link GH, resulting in an abstract topology of G'-H'. The PNC abstracts the physical topology of link FG, resulting in an abstract topology of F'-G'.

[0076] For the ports in network 3, the PNC abstracts the physical structure of port 31, resulting in an abstract topology of TP31. The PNC abstracts the physical structure of port 32, resulting in an abstract topology of TP32. The PNC abstracts the physical structure of port 33, resulting in an abstract topology of TP33. The PNC abstracts the physical structure of port 34, resulting in an abstract topology of TP34. The PNC abstracts the physical structure of port 35, resulting in an abstract topology of TP35. The PNC abstracts the physical structure of port 36, resulting in an abstract topology of TP36. The PNC abstracts the physical structure of port 37, resulting in an abstract topology of TP37. The PNC abstracts the physical structure of port 38, resulting in an abstract topology of TP38.

[0077] It should be noted that after the PNC abstracts the physical topology of network 1, the PNC can store the correspondence between the aforementioned nodes, links, and ports. The PNC uses this correspondence as a mapping between the physical topology and the abstract topology of network 1. Thus, the PNC can determine the physical topology of the target object corresponding to the abstract topology of the target object issued by the MDSC based on this mapping; and the PNC can also abstract the obtained physical performance parameters into abstract performance parameters based on this mapping.

[0078] Similarly, PNC can also determine the mapping relationship between the physical topology and abstract topology of network 2, as well as the mapping relationship between the physical topology and abstract topology of network 3.

[0079] Based on the above description of the network abstraction process of the ACTN controller in related technologies, it can be seen that when the ACTN controller abstracts the transmission network, it usually only abstracts the individual nodes, links, and ports in the transmission network.

[0080] However, with the development of devices in current transmission networks, a single device may include multiple hardware components (boards) with different functions, and different hardware components within the same device may have different functions. Current abstraction methods cannot represent the information of the device's hardware, the link information between hardware components, and the port information of the hardware. This will prevent the ACTN controller from controlling the hardware of devices in the transmission network.

[0081] like Figure 4 As shown, this embodiment of the application provides a network abstraction method that can be applied to, for example... Figure 2 In the communication network system shown, such as Figure 4 As shown, the network abstraction method includes the following S401 and S402.

[0082] S401, The network abstraction device obtains the physical topology of the target network and the physical topology of at least one node in the target network.

[0083] The physical topology of the target network includes at least one of the following: nodes, links, and ports; the content topology of the nodes includes at least one of the following: hardware modules, hardware module links, and hardware ports.

[0084] It should be noted that the network abstraction device in the embodiments of this application can be the PNC or MDSC in the ACTN controller, and this application does not limit it.

[0085] In the case of a network abstraction device (PNC), since the PNC is pre-configured with the physical topology of the target network and the physical topology of each node in the target network, the PNC can obtain the physical topology of the target network from within, as well as the physical topology of at least one node in the target network.

[0086] When the network abstraction device is MDSC, MDSC sends a physical topology request to PNC, requesting the physical topology of the target network and the physical topology of each node in the target network configured in PNC. PNC sends the physical topology of the target network and the physical topology of each node in the target network to MDSC. Correspondingly, MDSC receives the physical topology of the target network and the physical topology of each node in the target network from PNC.

[0087] It should be noted that at least one node described in the embodiments of this application may be all nodes in the target network or some nodes in the target network.

[0088] For example, when performing white abstraction on the target network, at least one node can be all nodes in the target network, nodes of a specified type in the target network, or a subset of nodes determined from all nodes in the target network in other ways. This application does not impose any limitations on this.

[0089] For example, when performing gray abstraction on the target network, at least one node is an abstracted node from the target network, or a subset of the abstracted nodes. This application does not impose any limitations on this.

[0090] For example, when performing black abstraction on the target network, at least one node is an abstracted node from the target network.

[0091] S402. The network abstraction device abstracts the physical topology of the target network and the physical topology within each node to determine the abstract topology of the target network.

[0092] The abstract topology of the target network includes at least one of the following: abstract information of nodes, abstract information of links, abstract information of ports, abstract information of hardware modules, abstract information of hardware module links, and abstract information of hardware ports.

[0093] Specifically, the physical topology of the target network characterizes the names (or physical properties) of each node in the target network, the connections between nodes, and the port information between nodes. In this way, the PNC can abstract the abstract topology of the target network based on the physical topology. This allows the MDSC to perform node-level service planning, fault location, and other tasks based on the abstract topology of the target network.

[0094] The physical topology of a node represents the names (or physical performance) of each hardware module within the node, the connections between these modules, and the ports of each module. This allows the PNC to abstract the internal topology of the node based on the physical topology. This, in turn, enables the MDSC to perform granular service planning and fault location within the device based on the node's abstract topology.

[0095] The above scheme offers at least the following benefits: When abstracting a target network, the network abstraction device not only abstracts the physical topology of the target network but also the physical topology of at least one node within the target network. Therefore, the network abstraction device can obtain abstraction results at the granularity of its internal hardware modules. Based on this granular abstraction result, the ACTN controller can manage the target network at the same granularity as the internal hardware modules.

[0096] For example, when performing business planning in the ACTN controller, the performance of the internal hardware modules of the device can be directly determined, and then business planning can be carried out based on the performance of the internal hardware modules of the device, so as to achieve more refined business planning.

[0097] For example, when performing fault location in the ACTN controller, the fault can be located directly in the specific hardware module based on the current state of the internal hardware module of the device, thus achieving more accurate fault location.

[0098] The network abstraction method involved in the embodiments of this application has been described in detail above.

[0099] In one possible implementation, the physical topology of a node includes: a first hardware module and a second hardware module.

[0100] Abstracting the physical topology of the at least one node includes:

[0101] The first hardware module and the second hardware module are abstracted into first node abstract information; the first node abstract information is used to represent the physical topology of the first hardware module and the second hardware module.

[0102] In other words, when abstracting the hardware modules inside a node, the network abstraction device can abstract multiple hardware modules with the same function within the same device into a single node abstraction. This reduces the number of nodes abstracted by the network abstraction device and lowers the load on MDSC.

[0103] In one example, an optical network device includes optical transform units (OTUs) #1 and #2. OTUs #1 and #2 have the same function: converting electrical signals into optical signals and outputting the converted optical signals to a multiplexing board. In this case, the network abstraction device can abstract OTUs #1 and #2 as a single OTU Node.

[0104] In another possible implementation, the physical topology of a node includes: a third hardware module; the node is a node among the at least one node;

[0105] Abstracting the physical topology of a node includes:

[0106] The third hardware module is abstracted into second node abstract information and third node abstract information; the second node abstract information and the third node abstract information are used to jointly represent the physical topology of the third hardware module.

[0107] In other words, when abstracting the hardware modules inside a node, a network abstraction device can abstract a single hardware module with multiple functions within the same device into multiple node abstract information. In this way, the network abstraction device can abstract at the granularity of the hardware module's function, thereby achieving a more refined level of abstraction.

[0108] The following describes the network abstraction method involved in the embodiments of this application, taking the target network as an optical network and the nodes as optical network devices as an example.

[0109] like Figure 5 The diagram shows the internal hardware structure of the optical network device 50. The optical network device 50 includes: an OTU 501, a multiplexer 502, an optical amplifier (OA) 503, an optical fiber line auto switch protection device (OLP) 504, and a demultiplexer 505.

[0110] Among them, OTU501 is used to convert electrical signals into optical signals.

[0111] The multiplexer 502 is used to couple multiple optical signals of different wavelengths into a single optical signal and transmit the coupled signal. The multiplexer is also called a multiplexer (MUX).

[0112] The OA503 is used to amplify optical signals. Figure 5 The diagram shows three OAs, denoted as OA#1, OA#2, and OA#3.

[0113] OLP504 is used to protect at least two optical signals in fiber optic or optical network equipment.

[0114] The wavelength division multiplexer 505 and the multiplexer 502 have opposite functions; the former separates a single optical signal into multiple optical signals and transmits these multiple signals. The wavelength division multiplexer is also called a demultiplexer (DMUX).

[0115] Network abstraction devices for, for example Figure 5 When abstracting the optical network device 50 shown, the hardware in the optical network device 50 is abstracted as Node (e.g., Wson-Node). The links between the various hardware components (e.g., fiber optic cables, panel cables) are abstracted as links. The ports of each hardware component are abstracted as TPs, and each TP corresponds to a different Node.

[0116] One example is a network abstraction device for, for example Figure 5 After abstracting the optical network device 50 shown, the resulting abstract topology is as follows: Figure 6 As shown. Figure 6 As shown, the abstract topology of optical network device 50 includes:

[0117] First, the network abstraction device abstracts the hardware of the optical network device 50, including:

[0118] The network abstraction device abstracts the OTU to obtain an abstract topology: OTU Node.

[0119] The network abstraction device abstracts the multiplexer to obtain an abstract topology: MUX Node.

[0120] The network abstraction device abstracts OA#1 to obtain the abstract topology: OA#1Node.

[0121] The network abstraction device abstracts OA#2 to obtain the abstract topology: OA#2Node.

[0122] Network abstraction devices abstract the OLP to obtain an abstract topology: OLP Node.

[0123] The network abstraction device abstracts the dialer to obtain an abstract topology: MUX Node.

[0124] Second, the network abstraction device abstracts the links between the hardware of the optical network devices 50, including:

[0125] The network abstraction device abstracts the link between the OTU and MUX, resulting in an abstract topology: OTU-MUX link.

[0126] The network abstraction device abstracts the link between MUX and OA#1, resulting in an abstract topology: MUX-OA#1link.

[0127] The network abstraction device abstracts the link between OA#1 and OLP, resulting in an abstract topology: OA#1-OLP link.

[0128] The network abstraction device abstracts the link between OTU and DMUX, resulting in an abstract topology: OTU-DMUX link.

[0129] The network abstraction device abstracts the link between DMUX and OA#2, resulting in an abstract topology: DMUX-OA#2link.

[0130] Third, the network abstraction device abstracts the hardware ports of the optical network device 50, including:

[0131] The network abstraction device abstracts the input ports of the two OTUs respectively, resulting in abstract topologies TP#1 and TP#2; the network abstraction device abstracts the ports in the OTUs that are connected to the MUX, resulting in abstract topology TP#3; the network abstraction device abstracts the ports in the OTUs that are connected to the DMUX, resulting in abstract topology TP#4.

[0132] The network abstraction device abstracts the ports in the MUX that are connected to the OTUs, resulting in the abstract topology TP#5; the network abstraction device abstracts the ports in the MUX that are connected to the OA#1, resulting in the abstract topology TP#6.

[0133] The network abstraction device abstracts the ports connected to the MUX in OA#1 to obtain the abstract topology TP#7; the network abstraction device abstracts the ports connected to the OLP in OA#1 to obtain the abstract topology TP#8.

[0134] The network abstraction device abstracts the port connected to OA#1 in the OLP to obtain the abstract topology TP#9; the network abstraction device abstracts the two output ports of the OLP to obtain the abstract topologies TP#10 and TP#11.

[0135] The network abstraction device abstracts the ports in the DMUX that are connected to the OTU, resulting in the abstract topology TP#12; the network abstraction device abstracts the ports in the DMUX that are connected to the OA#2, resulting in the abstract topology TP#13.

[0136] The network abstraction device abstracts the port connected to DMUX in OA#2 to obtain the abstract topology TP#14; the network abstraction device abstracts the output port of OA#2 to obtain the abstract topology TP#15.

[0137] It should be noted that the network abstraction device abstracts the TP (Transmission Point) that needs to establish an optical layer tunnel as a TTP: Tunnel Termination Point. For example, the ports on the OTU that are connected to the MUX and DMUX are the starting points for establishing an optical layer tunnel. Therefore, the network abstraction device can abstract the ports on the OTU that are connected to the MUX and the ports on the OTU that are connected to the DMUX as TTPs.

[0138] The above, taking an optical network device as an example, provides a detailed explanation of the process by which a network abstraction device abstracts the internal hardware structure of an optical network device.

[0139] As can be seen, the above mainly describes the technical solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, it includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, in conjunction with the modules and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this invention.

[0140] This application embodiment can divide the network abstraction device into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing unit. The integrated modules can be implemented in hardware or as software functional modules. Optionally, the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0141] like Figure 7 The diagram shown is a structural schematic of a network abstraction device provided in an embodiment of this application. The network abstraction device includes an acquisition unit 701 and a processing unit 702.

[0142] The acquisition unit 701 is used to acquire the physical topology of the target network and the physical topology of at least one node in the target network; the physical topology of the target network includes at least one of the following: node, link, and port; the physical topology of the node includes at least one of the following: hardware module, hardware module link, and hardware port; the processing unit 702 is used to abstract the physical topology of the target network and the physical topology of at least one node to determine the abstract topology of the target network; the abstract topology of the target network includes at least one of the following: abstract information of the node, abstract information of the link, abstract information of the port, abstract information of the node of the hardware module, abstract information of the link of the hardware module, and abstract information of the hardware port.

[0143] Optionally, the physical topology of the node includes: a first hardware module and a second hardware module; the processing unit 702 is specifically used to: abstract the first hardware module and the second hardware module into first node abstract information; the first node abstract information is used to represent the physical topology of the first hardware module and the second hardware module.

[0144] Optionally, the physical topology of the node includes: a third hardware module; and a processing unit 702, specifically used to: abstract the third hardware module into second node abstract information and third node abstract information; the second node abstract information and the third node abstract information are used to jointly represent the physical topology of the third hardware module.

[0145] Optionally, at least one node includes an optical network device; the physical topology of the optical network device includes: boards, links between boards, and ports of boards; the abstract topology of the optical network device includes: node abstract information of boards, abstract information of links between boards, and abstract information of ports of boards.

[0146] The processing unit 702 may be a processor or a controller. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination of functions implementing computation, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc. The acquisition unit 701 may be a transceiver circuit or an acquisition interface, etc. The storage unit may be a memory.

[0147] Through the above description of the implementation methods, those skilled in the art will clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the network node can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, modules, and network nodes described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0148] This application also provides a computer-readable storage medium storing instructions. When a computer executes these instructions, the computer performs each step of the method flow shown in the above-described method embodiments.

[0149] Embodiments of this application provide a computer program product containing instructions that, when executed on a computer, cause the computer to perform the software upgrade method described in the above method embodiments.

[0150] The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), registers, hard disks, optical fibers, compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing, or any other form of computer-readable storage medium in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may reside in an application-specific integrated circuit (ASIC). In embodiments of the present invention, a computer-readable storage medium may be any tangible medium that contains or stores a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0151] Since the apparatus, device, computer-readable storage medium, and computer program product in the embodiments of the present invention can be applied to the above methods, the technical effects that can be obtained can also be referred to the above method embodiments. The embodiments of this application will not be repeated here.

[0152] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A network abstraction method, characterized by, The method comprises: obtaining a physical topology of a target network and a physical topology of at least one node in the target network; the physical topology of the target network comprises nodes, links and ports; the physical topology of the node comprises hardware modules, hardware module links and hardware ports; abstracting the physical topology of the target network and the physical topology of the at least one node to determine an abstract topology of the target network; the abstract topology of the target network comprises at least one of the following: abstract information of the node, abstract information of the link, abstract information of the port, node abstract information of the hardware module, abstract information of the hardware module link and abstract information of the hardware port; wherein, when the physical topology of the one node comprises a first hardware module and a second hardware module having the same function, the abstracting of the physical topology of the one node comprises: abstracting the first hardware module and the second hardware module into first node abstract information; the first node abstract information is used to represent the physical topology of the first hardware module and the second hardware module; when the physical topology of the one node comprises a third hardware module having at least two functions, the abstracting of the physical topology of the one node comprises: abstracting the third hardware module into second node abstract information and third node abstract information; the second node abstract information and the third node abstract information are used to jointly represent the physical topology of the third hardware module.

2. The method of claim 1, wherein, The at least one node comprises an optical network device; the physical topology of the optical network device comprises board cards, links between the board cards and ports of the board cards; the abstract topology of the optical network device comprises node abstract information of the board cards, abstract information of the links between the board cards and abstract information of the ports of the board cards.

3. A network abstraction apparatus, characterized by, The method comprises: an obtaining unit and a processing unit; the obtaining unit is configured to obtain a physical topology of a target network and a physical topology of at least one node in the target network; the physical topology of the target network comprises nodes, links and ports; the physical topology of the node comprises hardware modules, hardware module links and hardware ports; the processing unit is configured to abstract the physical topology of the target network and the physical topology of the at least one node to determine an abstract topology of the target network; the abstract topology of the target network comprises at least one of the following: abstract information of the node, abstract information of the link, abstract information of the port, node abstract information of the hardware module, abstract information of the hardware module link and abstract information of the hardware port; wherein, when the physical topology of the node comprises a first hardware module and a second hardware module having the same function, the processing unit is specifically configured to: abstract the first hardware module and the second hardware module into first node abstract information; the first node abstract information is used to represent the physical topology of the first hardware module and the second hardware module; When the physical topology of the node comprises a third hardware module having at least two functions, the processing unit is specifically configured to: abstract the third hardware module into second node abstraction information and third node abstraction information; and the second node abstraction information and the third node abstraction information are used to jointly represent the physical topology of the third hardware module.

4. The network abstraction apparatus of claim 3, wherein, The at least one node comprises an optical network device. The physical topology of the optical network device comprises: board cards, links between the board cards, ports of the board cards; and the abstract topology of the optical network device comprises: node abstraction information of the board cards, abstract information of the links between the board cards, and abstract information of the ports of the board cards.

5. A network abstraction apparatus, characterized by, Comprise: A processor and a communication interface; the communication interface and the processor are coupled, and the processor is used to run a computer program or instructions to realize the network abstraction method as claimed in any one of claims 1-2.

6. A computer-readable storage medium having stored therein instructions, the computer-readable storage medium comprising: When a computer executes the instructions, the computer executes the network abstraction method as claimed in any one of claims 1-2.

Images