Network management device and method

Abstract

A network management device according to one embodiment of the present invention comprises: a linking unit which generates information that links first configuration information, in which communication network configuration elements are managed using a first data model, and second configuration information, in which the communication network configuration elements are managed using a second data model different from the first data model, and that is based on configuration elements which are included in the first and second configuration information and are the same between different data models of the communication network; and a conversion unit which, on the basis of the layer configuration of the communication network, converts the information generated by the linking unit into information indicating information objects related to each layer of the communication network and reference relationships of the information objects related to each layer.

Description

Network management apparatus and method

[0001] Embodiments of the present invention relate to a network management apparatus and method.

[0002] Communication carriers provide various communication services by combining communication networks (hereinafter referred to as NWs) of multiple layers or domains. In order to efficiently operate the diversifying communication services, cross-NW information analysis is important rather than analysis for each layer or domain.

[0003] On the other hand, since the configuration information of each NW is managed by individual systems for each layer and domain, in cross-NW information analysis, it is necessary to cross-reference and combine the configuration information of these NWs with different data models for processing.

[0004] Regarding cross-NW information analysis, Patent Document 1 discloses a technique for quickly identifying communication at a higher layer that is affected when a NW at a certain layer fails based on a multi-layer NW configuration. Also, Patent Document 2 discloses a technique for performing path control of the entire network across domains when a failure occurs across multiple domains.

[0005] Japanese Patent No. 7107158, Japanese Patent Application Laid-Open No. 2016-140004

[0006] However, the above-mentioned techniques do not have a function of combining the configuration information of NWs with different data models. Also, as a method of combining the configuration information of NWs, a method of importing the configuration information in each system and implementing individual combination processing for each combination of configuration information can be mentioned. When there are multiple systems that utilize the same NW configuration information, the following problems (1-1) and (1-2) exist.

[0007] (1-1) Since combination and reference processing are implemented in each system for each combination of configuration information, that is, for each combination of layers and domains, the process portability is low. (1-2) When new NW configuration information is added or the NW configuration information is changed, it is necessary to modify all systems that utilize the configuration information.

[0008] This invention was made in view of the above circumstances, and its purpose is to provide a network management device and method that can obtain appropriate information about the relationships between each layer of a communication network.

[0009] A network management device according to one aspect of the present invention includes: a coupling unit that generates information by combining the first and second configuration information, which are based on the same components between different data models of the communication network, and which are included in first configuration information in which the components of the communication network are managed by a first data model and second configuration information in which the components of the communication network are managed by a second data model different from the first data model; and a conversion unit that converts the information generated by the coupling unit into information indicating information objects for each of the layers of the communication network and reference relationships between the information objects for each of the layers, based on the layer configuration of the communication network.

[0010] A network management method according to one aspect of the present invention is a method performed by a network management device, comprising: a coupling unit of the network management device generating information which combines the first and second configuration information, which is based on the same components between different data models of the communication network and is included in first configuration information in which the components of the communication network are managed by a first data model and second configuration information in which the components of the communication network are managed by a second data model different from the first data model; and a conversion unit of the network management device converting the information generated by the coupling unit into information which indicates information objects for each layer of the communication network and the reference relationships of the information objects for each layer, based on the layer configuration of the communication network.

[0011] According to the present invention, appropriate information regarding the relationships between each layer of a communication network can be obtained.

[0012] Figure 1 shows an example of application of a network management device according to one embodiment of the present invention. Figure 2 shows an example of network configuration information. Figure 3 shows an example of network configuration information. Figure 4 shows an example of network configuration information. Figure 5 shows an example of network configuration information. Figure 6 shows an example of the result of extracting components from network configuration information. Figure 7 shows an example of the result of extracting components from network configuration information. Figure 8 shows an example of the result of extracting components from network configuration information. Figure 9 shows an example of the result of extracting components from network configuration information. Figure 10 shows an example of combining network configuration information. Figure 11 shows an example of the result of combining network configuration information. Figure 12 shows an example of the result of combining network configuration information. Figure 13 shows an example of a data model for network configuration information. Figure 14 shows an example of attributes of the data model for network configuration information. Figure 15 shows an example of attributes of the data model for network configuration information. Figure 16 shows an example of the result of converting the result of combining network configuration information to information objects and reference relationship information. Figure 17 shows an example of the target information in network configuration information. Figure 18 shows an example of a conversion rule related to the NW-A layer. Figure 19 shows an example of a conversion rule related to the NW-C layer. Figure 20 shows an example of a conversion rule related to the logic device layer. Figure 21 shows an example of a conversion rule related to physical resources. Figure 22 shows an example of a conversion rule related to updates. Figure 23 shows an example of a conversion rule related to the NW-B layer. Figure 24 shows an example of a conversion rule related to physical resources. Figure 25 shows an example of the conversion result by the NW configuration conversion unit related to the physical layer. Figure 26 shows an example of the conversion result by the NW configuration conversion unit related to the physical layer. Figure 27 shows an example of the conversion result by the NW configuration conversion unit related to the physical layer. Figure 28 shows an example of the conversion result by the NW configuration conversion unit related to the physical layer. Figure 29 shows an example of the conversion result by the NW configuration conversion unit related to the physical layer.Figure 30 is a diagram showing an example of the conversion result by the NW configuration conversion unit relating to the physical layer. Figure 31 is a diagram showing an example of the conversion result by the NW configuration conversion unit relating to the physical layer. Figure 32 is a diagram showing an example of the conversion result by the NW configuration conversion unit relating to the physical layer. Figure 33 is a diagram showing an example of the conversion result by the NW configuration conversion unit relating to the physical layer. Figure 34 is a diagram showing an example of the conversion result by the NW configuration conversion unit relating to the logical layer. Figure 35 is a diagram showing an example of the conversion result by the NW configuration conversion unit relating to the logical layer. Figure 36 is a diagram showing an example of the conversion result by the NW configuration conversion unit relating to the logical layer. Figure 37 is a diagram showing an example of the conversion result by the NW configuration conversion unit relating to the logical layer. Figure 38 is a diagram showing an example of the conversion result by the NW configuration conversion unit relating to the logical layer. Figure 39 is a diagram showing an example of the conversion result by the NW configuration conversion unit relating to the logical layer. Figure 40 is a diagram showing an example of the conversion result by the NW configuration conversion unit relating to the logical layer. Figure 41 is a diagram showing an example of the conversion result by the NW configuration conversion unit relating to the logical layer. Figure 42 is a diagram showing an example of the result of conversion by the NW configuration conversion unit related to the logical layer. Figure 43 is a diagram showing an example of the result of conversion by the NW configuration conversion unit. Figure 44 is a diagram showing an example of the result of conversion by the NW configuration conversion unit. Figure 45 is a diagram showing an example of a duplicate determination method related to the result of conversion by the NW configuration conversion unit. Figure 46 is a diagram showing an example of an information object after merging the result of conversion by the NW configuration conversion unit. Figure 47 is a block diagram showing an example of the hardware configuration of a network management device according to one embodiment of the present invention.

[0013] Embodiments relating to this invention will be described below. Figure 1 is a diagram showing an example of application of a network management device according to one embodiment of the present invention. One embodiment of the present invention is a technology that converts multiple NW configuration information managed by individual data models into a single unified data model and provides it to an external system. NW configuration information is information in which the components of each layer of the NW are managed. As shown in Figure 1, the network management device 100 according to one embodiment of the present invention comprises an NW configuration extraction unit 10, an NW configuration coupling unit 20, an NW configuration conversion unit 30, an NW configuration holding unit 40, and an NW configuration providing unit 50.

[0014] The NW configuration extraction unit 10 takes in the configuration information of each NW, that is, NW configuration information in which the components of the NW are managed by different data models, and extracts the components of each NW from each configuration information based on extraction rules. The NW configuration information in which the components of the NW are managed by different data models is information that is different in layer or domain from one another. The acquisition of NW configuration information can be done, for example, by periodic or ad-hoc linkage with the management system for each NW information, or by manual input.

[0015] The NW configuration merging unit 20 merges the configuration information of each NW based on merging rules. This merging means that the NW configuration information, which is based on the same components and is included in multiple NW configuration information that are in different layers or domains, is merged into a single set of configuration information.

[0016] The NW configuration conversion unit 30 converts the result of the combination performed by the NW configuration combination unit 20 into information objects related to the physical layer, information objects related to the logical layer, and information indicating the layer and domain-independent reference relationships between these objects, based on conversion rules and layer configuration, and stores them in the NW configuration holding unit 40. The NW configuration holding unit 40 is composed of a storage medium, such as an HDD (Hard Disk Drive), SSD (Solid State Drive), or memory.

[0017] The NW configuration provider unit 50 provides all or part of the NW configuration, which has been converted into a unified data model, to an external system. Examples of the forms of provision by the NW configuration provider unit 50 include file linkage, such as FTP (File Transfer Protocol) and SFTP (Secure File Transfer Protocol), API (Application Programming Interface) linkage, such as REST-API (Representational State Transfer API), or direct access to a DB (database).

[0018] The NW configuration merging unit 20, the NW configuration conversion unit 30, and the NW configuration holding unit 40 can absorb additions or changes to NW configuration information. In this embodiment, the NW configuration information of multiple layers and domains is converted into information of a unified data model that includes physical layer and logical layer objects and their reference relationships, based on extraction, merging, and conversion rules. As a result, external systems can process the entire NW configuration based on common reference relationships that are independent of the original layers and domains.

[0019] For example, when new network configuration information is added or when network configuration information is changed, these additions or changes can be absorbed by the network management device 100 according to this embodiment, thus reducing or eliminating the need for modifications to external systems.

[0020] Figures 2 to 5 illustrate examples of network configuration information. Figure 2 shows NW-A information, one of the network configuration information components, in this case, management information for an IP network. In the example shown in Figure 2, the NW-A information includes identifier "A01", path type "transmission", path name "path X", A-end device "A-router 1", A-end port number "0", Z-end device "A-router 2", Z-end port number "0", and other information to which components are associated. Figure 3 shows NW-B information, another type of network configuration information component, in this case, management information for an Ethernet (registered trademark) network. The NW-B information is network configuration information where the layer hierarchy is the same as that of the NW-A information, but the domain is different from that of the NW-A information.

[0021] In the example shown in Figure 3, the NW-B information includes the identifier "B01", the path name "Transmission Path X", the A-end device "B-Switch 1", the A-end port number "0", the Z-end device "B-Switch 2", the Z-end port number "0", and other information to which components are associated.

[0022] Figure 4 shows NW-C information, which is one type of network configuration information, specifically management information for an optical transmission network. NW-C information is network configuration information whose layer is lower than that of NW-A information and NW-B information. In the example shown in Figure 4, the NW-C information includes the path name "Transmission Path X", the starting building "D-Building 1", the ending building "D-Building 2", the starting device "C-Transmission 1", the starting port number "0", the ending device "C-Transmission 2", the ending port number "0", and other information to which components are associated.

[0023] Figure 4 shows NW-D information, which is one type of network configuration information, specifically management information for physical cable information. NW-D information is network configuration information whose layer is lower than the layer related to NW-C. In the example shown in Figure 5, the NW-D information includes information to which the cable name "Cable 1", the upper building "D-Building 1", the lower building "D-Building 2", and other components are associated.

[0024] Next, we will describe an example of a rule for extracting network components from network configuration information. The extraction rule specifies how the NW configuration extraction unit 10 extracts only the information that is subject to the joining process by the NW configuration joining unit 20 and the conversion process by the NW configuration conversion unit 30 from each piece of information. For example, it specifies the name of the attribute to be extracted. Note that the extraction rule is not mandatory, as it is provided to reduce the amount of information and speed up the subsequent joining and conversion processes.

[0025] First, let's explain the NW-A extraction rule. This NW-A extraction rule shows a list of attributes to be extracted from the NW-A information shown in Figure 2. The attributes to be extracted by the NW-A extraction rule are identifier, path type, path name, A-end device, A-end port number, Z-end device, and Z-end port number.

[0026] Next, we will explain the NW-B extraction rules. These NW-B extraction rules show a list of attributes to be extracted from the NW-B information shown in Figure 3. The attributes to be extracted by the NW-B extraction rules are the identifier, path name, A-end device, A-end port number, Z-end device, and Z-end port number.

[0027] Next, we will explain the NW-C extraction rules. These NW-C extraction rules show a list of attributes to be extracted from the NW-C information shown in Figure 4. The attributes to be extracted by the NW-C extraction rules are the path name, starting building, ending building, starting device, starting port number, ending device, and ending port number.

[0028] Next, we will explain the NW-D extraction rules. These NW-D extraction rules show a list of attributes to be extracted from the NW-D information shown in Figure 5. The attributes to be extracted by the NW-D extraction rules are cable name, upstream building, and downstream building.

[0029] Figures 6 to 9 show examples of the results of extracting components from network configuration information. Figure 6 shows intermediate information which is the result of extraction by the NW configuration extraction unit 10 from the NW-A information shown in Figure 2. In the example shown in Figure 6, the intermediate information derived from the NW-A information is associated with an identifier, path type, path name, A-end device, A-end port number, Z-end device, and Z-end port number.

[0030] Figure 7 shows the intermediate information extracted by the NW configuration extraction unit 10 from the NW-B information shown in Figure 3. In the example shown in Figure 7, the intermediate information derived from the NW-B information is associated with an identifier, a path name, an A-terminal device, an A-terminal port number, a Z-terminal device, and a Z-terminal port number.

[0031] Figure 8 shows the intermediate information extracted by the NW configuration extraction unit 10 from the NW-C information shown in Figure 4. In the example shown in Figure 8, the intermediate information derived from the NW-C information is associated with the path name, starting building, ending building, starting device, starting port number, ending device, and ending port number.

[0032] Figure 9 shows the intermediate information extracted by the NW configuration extraction unit 10 from the NW-D information shown in Figure 5. In the example shown in Figure 9, the intermediate information derived from the NW-D information is associated with the cable name, the upper-level building, and the lower-level building.

[0033] Next, we will explain an example of a rule for joining network configuration information. Figure 10 shows an example of joining network configuration information. A joining rule is used when combining different data, for example, when combining configuration information from different layers, each containing the same components between layers, such as configuration information where components of one layer are managed and configuration information where components of different layers are managed, into a single set of configuration information. This rule manages the components of the physical layer of the communication network, which are set for each piece of information to be joined.

[0034] First, let's explain the "NW-A to NW-C joining rule." This rule is used to combine information derived from NW-A information, as shown in Figure 6, and information derived from NW-C information, as shown in Figure 8. For example, it can be expressed as follows: (NW-A to NW-C joining rule) "NW-A information 'path type' + NW-A information 'path name'" and "NW-C information 'path name'" are equal.

[0035] Next, we will explain the "NW-B to NW-C joining rule." This rule is used to join information derived from NW-B information, as shown in Figure 7, and information derived from NW-C information, as shown in Figure 8. For example, it is shown as follows: (NW-B to NW-C joining rule) "NW-B information 'path name'" and "NW-C information 'path name'" are equal.

[0036] Next, we will explain the "NW-C to NW-D joining rule." This rule is used to join information derived from NW-C information, as shown in Figure 8, and information derived from NW-D information, as shown in Figure 9. For example, it can be shown as follows: (NW-C to NW-D joining rule) NW-C information "starting building" and NW-D information "upper building" are equal, AND NW-C information "ending building" and NW-D information "lower building" are equal, OR NW-C information "starting building" and NW-D information "lower building" are equal, AND NW-C information "ending building" and NW-D information "upper building" are equal.

[0037] Figures 11 and 12 show an example of the result of combining network configuration information. Figure 11 shows intermediate information which is the result of combining the extracted information derived from NW-A information shown in Figure 6, the extracted information derived from NW-C information shown in Figure 8, and the extracted information derived from NW-D information shown in Figure 9 by the NW configuration combining unit 20.

[0038] In the example shown in Figure 11, the information derived from NW-A information is associated with identifiers, A-end device, A-end port number, Z-end device, and Z-end port number; the information derived from NW-C information is associated with path names, source device, source port number, destination device, and destination port number; and the information derived from NW-D information is associated with cable names, parent buildings, and subordinate buildings, similar to the example shown in Figure 9. In the examples described below, the parent building corresponding to the cable name "Cable 1" in the information derived from NW-D information is assumed to be "Building A1," and the corresponding subordinate building is assumed to be "Building Z1."

[0039] Figure 12 shows intermediate information, which is the result of combining the extracted information derived from NW-B information shown in Figure 7, the extracted information derived from NW-C information shown in Figure 8, and the extracted information derived from NW-D information shown in Figure 9, by the NW configuration coupling unit 20.

[0040] In the example shown in Figure 12, the information derived from NW-B information is associated with the identifier, A-end device, A-end port number, Z-end device, and Z-end port number; the information derived from NW-C information is associated with the path name, source device, source port number, destination device, and destination port number, similar to the example shown in Figure 11; and the information derived from NW-D information is associated with the cable name, upstream building, and downstream building, similar to the example shown in Figure 11.

[0041] Next, we will describe an example of a data model for network configuration information. Figure 13 shows an example of a data model for network configuration information. In the example shown in Figure 13, the data model consists of a layer type, an information object type, and an overview of the information object type.

[0042] The information object types and descriptions for the "Physical Layer" layer type, as shown in Figure 13, are as follows (2-1) to (2-5): (2-1) (Information object type) PS (Physical Structure), (Description) Structure (e.g., telecommunications building) (2-2) (Information object type) PD (Physical Device), (Description) Device (e.g., router, transmission equipment) (2-3) (Information object type) PP (Physical Port), (Description) Physical port of the device (2-4) (Information object type) PL (Physical Link), (Description) Physical link (e.g., core wire) (2-5) (Information object type) AS (Aggregate Section), (Description) Cable (e.g., conduit) bundling physical links

[0043] The information object types and overviews for the layer type "Logical Layer" shown in Figure 13 are as follows (3-1) to (3-4): (3-1) (Information object type) TPE (Termination Point Encapsulation), (Overview) Communication endpoint (within the communication layer) (3-2) (Information object type) FRE (Forwarding Relationship Encapsulation), (Overview) Connectivity between communication endpoints (within the communication layer) *Types of connectivity -LC (Link Connection): Connectivity between devices -XC (Cross Connection): Connectivity within a device -NC (Network Connection): End-to-end connectivity composed of LC and XC (3-3) (Information object type) NFD (Network Forwarding Domain), (Overview) Connectivity within a device (Logical device layer) (3-4) (Information object type) TL (Topological Link), (Overview) Connectivity between devices (Logical device layer)

[0044] Next, an example of the attributes of the physical layer of the data model of NW configuration information will be described. FIG. 14 is a diagram showing an example of the attributes of the data model of network configuration information. In the example shown in FIG. 14, the information related to the attributes of the data model consists of resource type, information object type, attributes, and an overview of the attributes.

[0045] For the resource type "Physical Resource" and the information object type "PS (Physical Structure)" shown in FIG. 14, the attributes and an overview of the attributes are shown as follows in (4-1). (4-1) (Attribute) objectID, (Overview) ID of the object (Attribute) commonName, (Overview) Name (e.g., building name) (Attribute) _physicalDevices, (Overview) objectID of the installed PD

[0046] For the resource type "Physical Resource" and the information object type "PD (Physical Device)" shown in FIG. 1, the attributes and an overview of the attributes are shown as follows in (4-2). (4-2) (Attribute) objectID, (Overview) ID of the object (Attribute) commonName, (Overview) Name (e.g., device name) (Attribute) _physicalPorts, (Overview) objectID of the equipped PP

[0047] For the resource type "Physical Resource" and the information object type "PP (Physical Port)" shown in FIG. 14, the attributes and an overview of the attributes are shown as follows in (4-3). (4-3) (Attribute) objectID, (Overview) ID of the object (Attribute) commonName, (Overview) Name (e.g., port name)

[0048] The attributes and an overview of the attribute of the information object type "PL (Physical Link)" of the resource type "physical resource" shown in FIG. 14 are shown as follows in (4-4). (4-4) (Attribute) objectID, (Overview) ID of the object (Attribute) commonName, (Overview) Name (e.g., core wire name) (Attribute) _physicalPorts, (Overview) objectID of the connected PP

[0049] The attributes and an overview of the attribute of the information object type "AS (Aggregate Section)" of the resource type "physical resource" shown in FIG. 14 are shown as follows in (4-5). (4-5) (Attribute) objectID, (Overview) Object ID (identifier) (Attribute) commonName, (Overview) Name (e.g., cable name) (Attribute) _physicalLinks, (Overview) objectID of the aggregated PL (Attribute) _physicalStructures, (Overview) objectID of the connected PS

[0050] Next, an example of the attributes of the logical layer of the data model of the NW configuration information will be described. FIG. 15 is a diagram showing an example of the attributes of the data model of the network configuration information. In the example shown in FIG. 15, the information related to the attributes of the data model consists of the resource type, the information object type, the attribute, and an overview of the attribute.

[0051] The attributes and attribute summaries of the information object type "TPE (Termination Point Encapsulation)" of resource type "Logical Resource" shown in Figure 15 are as follows (5-1): (5-1) (Attribute) objectID, (Summary) ID of the object (Attribute) commonName, (Summary) Name (Attribute) layerProtocolName, (Summary) Communication layer name (e.g., NW-A (IP) layer, NW-C (Transmission) layer, Logical device layer) (Attribute) _encapsulatedLtList, (Summary) objectID of the TPE of the lower communication layer (Attribute) _physicalPort, (Summary) objectID of the PP of the lower physical layer

[0052] The attributes and attribute summaries of the information object type "FRE (Forwarding Relationship Encapsulation)" of resource type "Logical Resource" shown in Figure 15 are shown below in (5-2). (5-2) (Attribute) objectID, (Summary) ID of the object (Attribute) commonName, (Summary) Name (e.g., path name) (Attribute) layerProtocolName, (Summary) Communication layer name (Attribute) freType, (Summary) Type of connectivity (LC / XC / NC) (Attribute) _endPointList, (Summary) objectID of the connected TPE

[0053] The attributes and attribute summaries of the information object type "NFD (Network Forwarding Domain)" of resource type "Logical Resource" shown in Figure 15 are shown below in (5-3). (5-3) (Attribute) objectID, (Summary) ID of the object (Attribute) commonName, (Summary) Name (Attribute) _edgeTpeRefList, (Summary) objectID of the connected TPE

[0054] The attributes and attribute summaries of the information object type "TL (Topological Link)" of resource type "Logical Resource" shown in Figure 15 are as follows (5-4): (5-4) (Attribute) objectID, (Summary) ID of the object (Attribute) commonName, (Summary) Name (Attribute) _endTpeRefList, (Summary) objectID of the connected TPE

[0055] Figure 16 shows an example of the result of converting the combined network configuration information into information objects and reference relationship information. In the example shown in Figure 16, the source information, which is the result of combining the extracted information derived from NW-A information, extracted information derived from NW-C information, and extracted information derived from NW-D information shown in Figure 11 by the NW configuration combination unit 20, is converted by the NW configuration conversion unit 30 into information objects for logical resources, information objects for physical resources, and reference relationship information for these information objects. The logical resources include the NW-A (IP) layer, the NW-C (transmission) layer, and the logical device layer. The conversion result includes the type, attributes, and values ​​of the attributes of the destination information objects.

[0056] Figure 17 shows an example of the correspondence of conversion rules in network configuration information. Figure 18 shows an example of conversion rules related to the NW-A layer. The example shown in Figure 18 is a conversion rule related to the generation of TPE and FRE of the NW-A layer of logical resources, based on the source information shown in Figure 16. The numbers "1" to "6" shown in Figure 17 correspond to the identification numbers "1" to "6" of the NW-A layer TPE shown in Figure 18.

[0057] Figure 19 shows an example of a conversion rule related to the NW-C layer. The example shown in Figure 19 is a conversion rule related to the generation of the TPE and FRE of the NW-C layer of a logical resource, based on the source information shown in Figure 16. The numbers "13" to "16" shown in Figure 17 correspond to the identification numbers "13" to "16" of the NW-C layer TPE shown in Figure 19.

[0058] Figure 20 shows an example of a conversion rule related to the logical device layer. The example shown in Figure 20 is a conversion rule related to the generation of the TPE, NFD, and TL of the logical device layer of a logical resource, based on the source information shown in Figure 16. The numbers "21" to "28" shown in Figure 17 correspond to the identification numbers "21" to "28" of the TPE of the logical device layer shown in Figure 20.

[0059] Figure 21 shows an example of a conversion rule related to physical resources. The example shown in Figure 21 is a conversion rule for generating PP, PD, PL, PS, and AS of physical resources based on the source information shown in Figure 16. The numbers "36" to "43" shown in Figure 17 correspond to the identification numbers "36" to "43" of the physical resource PP shown in Figure 21. Figure 22 shows an example of a conversion rule related to updates. The example shown in Figure 22 is a rule that shows the reference relationships related to TPE and PP of each layer.

[0060] Figure 23 shows an example of a conversion rule related to the NW-B layer. The example shown in Figure 23 is a conversion rule for generating the TPE and FRE of the NW-B layer of a logical resource, based on the source information which is the result of combining the extracted information derived from NW-B information, extracted information derived from NW-C information, and extracted information derived from NW-D information shown in Figure 12 by the NW configuration coupling unit 20.

[0061] Figure 24 shows an example of a conversion rule related to physical resources. The example shown in Figure 24 is a conversion rule for generating PP, PD, PL, PS, and AS of physical resources, based on the source information shown in Figure 12.

[0062] Figures 25 to 33 show examples of the results of the conversion by the NW configuration conversion unit related to the physical layer. The attribute names shown in Figures 26 to 33 correspond to the attribute names shown in Figure 14. The attributes and attribute values ​​of the physical resource information object type "PP" (PP02 in Figure 25) shown in Figure 25 are shown as follows (6-1) (see Figure 26). (6-1) (Attribute) objectID, (Value) PP / 02 (Attribute) commonName, (Value) 0

[0063] The attributes and attribute values ​​of the physical resource information object type "PP" (PP03 in Figure 25), as shown in Figure 25, are shown below (6-2) (see Figure 27). (6-2) (Attribute) objectID, (Value) PP / 03 (Attribute) commonName, (Value) -

[0064] The attributes and attribute values ​​of the physical resource information object type "PD" (PD01 in Figure 25), as shown in Figure 25, are shown below (6-3) (see Figure 28). (6-3) (Attribute) objectID, (Value) PD / 01 (Attribute) commonName, (Value) A-Router1 (Attribute) _physicalPorts, (Value) PP / 01, PP / 02

[0065] The attributes and attribute values ​​of the physical resource information object type "PD" (PD02 in Figure 25), as shown in Figure 25, are as follows (6-4) (see Figure 29). (6-4) (Attribute) objectID, (Value) PD / 02 (Attribute) commonName, (Value) C-Transmission1 (Attribute) _physicalPorts, (Value) PP / 03, PP / 04

[0066] The attributes and attribute values ​​of the physical resource information object type "PL" (PL02 in Figure 25), as shown in Figure 25, are as follows (6-5) (see Figure 30). (6-5) (Attribute) objectID, (Value) PL / 02 (Attribute) commonName, (Value) - (Attribute) _physicalPorts, (Value) PP / 04, PP / 05

[0067] The attributes and attribute values ​​of the physical resource information object type "PS" (PS01 in Figure 25), as shown in Figure 25, are as follows (6-6) (see Figure 31). (6-6) (Attribute) objectID, (Value) PS / 01 (Attribute) commonName, (Value) Building A1 (Attribute) _physicalDevices, (Value) PD / 01, PD / 02

[0068] The attributes and attribute values ​​of the physical resource information object type "PS" (PS02 in Figure 25), as shown in Figure 25, are as follows (6-7) (see Figure 32). (6-7) (Attribute) objectID, (Value) PS / 02 (Attribute) commonName, (Value) Building Z1 (Attribute) _physicalDevices, (Value) PD / 03, PD / 04

[0069] The attributes and attribute values ​​of the physical resource information object type "AS" (AS01 in Figure 25), as shown in Figure 25, are shown below (6-8) (see Figure 33). (6-8) (Attribute) objectID, (Value) AS / 01 (Attribute) commonName, (Value) Cable1 (Attribute) _physicalLinks, (Value) PL / 02 (Attribute) _physicalStructures, (Value) ]PS / 01, PS / 02

[0070] Figures 34 to 42 show examples of the results of the conversion by the NW configuration conversion unit relating to the logical layer. The attribute names shown in Figures 35 to 42 correspond to the attribute names shown in Figure 15. The attributes and attribute values ​​of the information object type "TPE" (TPE03 in Figure 34) of the NW-A layer of the logical resource shown in Figure 34 are shown as follows (7-1) (see Figure 35).

[0071] (7-1) (Attribute) objectID, (Value) TPE / 03 (Attribute) commonName, (Value) - (Attribute) layerProtocolName, (Value) NW-A (Attribute) _encapsulatedLtList, (Value) TPE / 07 (Attribute) _physicalPort, (Value) -

[0072] The attributes and attribute values ​​of the information object type "FRE" (FRE01 in Figure 34) of the NW-A layer of the logical resource shown in Figure 34 are shown as follows (7-2) (see Figure 36).

[0073] (7-2) (Attribute) objectID, (Value) FRE / 01 (Attribute) commonName, (Value) A01 (Attribute) layerProtocolName, (Value) NW-A (Attribute) freType, (Value) NC (Attribute) _endPointList, (Value) TPE / 01,TPE / 06

[0074] The attributes and attribute values ​​of the information object type "FRE" (FRE04 in Figure 34) of the NW-A layer of the logical resource shown in Figure 34 are shown as follows (7-3) (see Figure 37).

[0075] (7-3) (Attribute) objectID, (Value) FRE / 04 (Attribute) commonName, (Value) - (Attribute) layerProtocolName, (Value) NW-A (Attribute) freType, (Value) LC (Attribute) _endPointList, (Value) TPE / 03, TPE / 04

[0076] The attributes and attribute values ​​of the information object type "TPE" (TPE07 in Figure 34) of the NW-C layer of the logical resource, as shown in Figure 34, are shown as follows (7-4) (see Figure 38).

[0077] (7-4) (Attribute) objectID, (Value) TPE / 07 (Attribute) commonName, (Value) - (Attribute) layerProtocolName, (Value) NW-C (Attribute) _encapsulatedLtList, (Value) TPE / 13 (Attribute) _physicalPort, (Value) -

[0078] The attributes and attribute values ​​of the information object type "FRE" (FRE07 in Figure 34) of the NW-C layer of the logical resource shown in Figure 34 are shown as follows (7-5) (see Figure 39).

[0079] (7-5) (Attribute) objectID, (Value) FRE / 07 (Attribute) commonName, (Value) Transmission Path X (Attribute) layerProtocolName, (Value) NW-C (Attribute) freType, (Value) NC (Attribute) _endPointList TPE / 01,TPE / 02

[0080] The attributes and attribute values ​​of the information object type "TPE" (TPE13 in Figure 34) of the logical device layer of the logical resource, as shown in Figure 34, are shown as follows (7-6) (see Figure 40).

[0081] (7-6) (Attribute) objectID, (Value) TPE / 13 (Attribute) commonName, (Value) - (Attribute) layerProtocolName, (Value) Logical Unit (Attribute) _encapsulatedLtList, (Value) - (Attribute) _physicalPort, (Value) PP / 03

[0082] The attributes and attribute values ​​of the information object type "NFD" (NFD02 in Figure 34) of the logical device layer of the logical resource, as shown in Figure 34, are shown as follows (7-7) (see Figure 41).

[0083] (7-7) (Attribute) objectID, (Value) NFD / 02 (Attribute) commonName, (Value) - (Attribute) _edgeTpeRefList, (Value) TPE / 13, TPE / 14

[0084] The attributes and attribute values ​​of the information object type "TL" (TL02 in Figure 34) of the logical device layer of the logical resource, as shown in Figure 34, are shown in (7-8) below (see Figure 42).

[0085] (7-8) (Attribute) objectID, (Value) TL / 02 (Attribute) commonName, (Value) - (Attribute) _endTpeRefList, (Value) TPE / 14, TPE / 15

[0086] Figures 43 and 44 show an example of the conversion result by the NW configuration conversion unit. In the example shown in Figure 43, the conversion result by the NW configuration conversion unit 30 is shown from the source information, which is the result of combining the extracted information derived from NW-A information, extracted information derived from NW-C information, and extracted information derived from NW-D information shown in Figure 11 by the NW configuration coupling unit 20, to information objects for logical resources, information objects for physical resources, and information on the reference relationships of these information objects. In this conversion result, the objectIDs of the information objects for physical resources are "PD / 01", "PD / 02", "PD / 03", and "PD / 04".

[0087] Furthermore, in the example shown in Figure 44, the result of the conversion by the NW configuration conversion unit 30 is shown from the source information, which is the result of the NW configuration coupling unit 20 combining the extracted information derived from NW-B information, extracted information derived from NW-C information, and extracted information derived from NW-D information shown in Figure 12, into information objects for logical resources, information objects for physical resources, and information on the reference relationships of these information objects. The objectIDs of the information objects for physical resources in this conversion result are "PD / 05", "PD / 06", "PD / 07", and "PD / 08".

[0088] The NW configuration conversion unit 30 can merge duplicate information objects in the results of these conversions to generate a new conversion result after merging.

[0089] An example of the merging process is to determine if there are duplicate information objects between the conversion results shown in Figure 43 and Figure 44, according to the duplicate detection method described below, and then generate new information by deleting all but one of these duplicate objects. During this merge, among the attributes managed by the conversion results as shown in Figures 25 to 42, the objectIDs of attributes that reference the objectID of the deleted information object as the objectID of other information objects, such as "_physicalDevices", "_physicalStructures", "_encapsulatedLtList", or "_endPointList", are updated according to the merge result.

[0090] Figure 45 shows an example of a duplicate determination method related to the conversion results by the NW configuration conversion unit. In this embodiment, information objects are merged in the order of physical resources to logical resources, that is, from lower layers to upper layers.

[0091] The hierarchical relationships between logical resource layers can be defined by the TPE's reference attributes or by defining information describing the layer configuration, and the relevant information may be referenced. The TPE's reference attributes can be determined from the aforementioned "_encapsulatedLtList" and "_physicalPort".

[0092] The types of information objects subject to duplicate detection and the methods for determining duplicates in the "Physical Layer" layer are shown below in (8-1) to (8-5). (8-1) (Information object type) PS, (Duplicate detection method) commonName is the same (the same building name is considered the same building) (8-2) (Information object type) PD, (Duplicate detection method) commonName is the same (the same device name is considered the same device)

[0093] (8-3) (Information object type) PP, (Duplicate detection method) The PDs referencing the objectID are the same and the commonName is the same (the same port name on the same device is considered the same port) (8-4) (Information object type) PL, (Duplicate detection method) The objectIDs included in _pysicalPorts are the same (determined after PP merging) (8-5) (Information object type) AS, (Duplicate detection method) The commonName is the same (the same cable name is considered the same cable)

[0094] Furthermore, the types of information objects subject to duplicate determination and the duplicate determination method for the layer type "Logical Layer" are shown below in (9-1) to (9-4). (9-1) (Information object type) TPE, (Duplicate determination method) If layerProtocolName is a logical device: The objectID of _physicalPort is the same. Otherwise: The objectID included in _encapsulatedLtList is the same.

[0095] (9-2) (Information object type) FRE, (Method of determining duplicates) For NC: commonName is the same. For LC and XC: objectID included in _endPointList is the same. (Determined after TPE merging is performed)

[0096] (9-3) (Information object type) NFD, (Method of determining duplicates) commonName is the same. (9-4) (Information object type) TL, (Method of determining duplicates) objectID included in _endTpeRefList is the same (determined after TPE merging is performed).

[0097] Figure 46 shows an example of an information object after merging the results of the conversion by the NW configuration conversion unit. In the example shown in Figure 46, it is determined that the PD with objectID "PD / 02" shown in Figure 43 and the PD with objectID "PD / 06" shown in Figure 44 are duplicates, and that the PD with objectID "PD / 03" shown in Figure 43 and the PD with objectID "PD / 07" shown in Figure 44 are duplicates.

[0098] Following this determination, the PD with objectID "PD / 06" and the PD with objectID "PD / 07" shown in Figure 44 are deleted, the connection relationship is changed so that the PD with objectID "PD / 05" is connected to the PD with objectID "PD / 02", and the connection relationship is changed so that the PD with objectID "PD / 08" is connected to the PD with objectID "PD / 03", and this is generated as information relating to the merged information object.

[0099] Figure 47 is a block diagram showing an example of the hardware configuration of a network management device according to one embodiment of the present invention. In the example shown in Figure 47, the network management device 100 according to the above embodiment is composed of, for example, a server computer or a personal computer, and has a hardware processor 111A such as a CPU (Central Processing Unit). A program memory 111B, a data memory 112, an input / output interface 113, and a communication interface 114 are connected to this hardware processor 111A via a bus 115.

[0100] The communication interface 114 includes, for example, one or more wireless communication interface units, enabling the transmission and reception of information with the communication network. As the wireless interface, for example, an interface employing a low-power wireless data communication standard such as a wireless LAN (Local Area Network) is used.

[0101] Input / output interface 113 is connected to input devices 200 and output devices 300, which are attached to the network management device 100 and used by users.

[0102] The input / output interface 113 can capture operation data entered by a user or the like through an input device 200 such as a keyboard, touch panel, or touchpad, and output the output data to an output device 300, including a display device using liquid crystal or organic EL (electroluminescence), for display. The input device 200 and output device 300 may be devices built into the network management device 100, or they may be input and output devices of other information terminals that can communicate with the network management device 100 via the network.

[0103] The program memory 111B is a non-temporary tangible storage medium in which a non-volatile memory that can be written to and read at any time, such as an HDD or SSD, is used in combination with another non-volatile memory such as ROM (Read Only Memory), and can store programs necessary for executing various control processes, etc., according to one embodiment.

[0104] The data memory 112 is a tangible storage medium that, for example, uses a combination of the above-mentioned non-volatile memory and volatile memory such as RAM (Random Access Memory), and can be used to store various data or information acquired and created during the process of various operations.

[0105] One embodiment of the present invention, the network management device 100, can be configured as an information processing device having the parts shown in Figure 1, with a software-based processing function unit.

[0106] The information storage unit used as work memory by each part of the network management device 100 may be configured using a data memory 112. However, these storage areas are not essential to the network management device 100, and may be, for example, areas provided in an external storage medium such as a USB (Universal Serial Bus) memory, or in a storage device such as a database server located in the cloud.

[0107] Each of the processing functions in the above-described section can be implemented by having the hardware processor 111A read and execute a program stored in the program memory 111B. Some or all of these processing functions may be implemented in various other forms, including application-specific integrated circuits (ASICs) or field-programmable gate arrays (FPGAs).

[0108] Furthermore, the methods described in each embodiment can be stored as programs (software means) that can be executed by a computer on recording media such as magnetic disks (floppy disks, hard disks, etc.), optical disks (CD-ROMs, DVDs, MOs, etc.), and semiconductor memories (ROMs, RAMs, flash memories, etc.), and can also be transmitted and distributed via communication media. The programs stored on the media also include configuration programs that configure the computer to run software means (including not only the execution program but also tables or data structures). The computer implementing this device reads the program recorded on the recording media and, if necessary, constructs the software means using the configuration program, and executes the above-described processes by controlling the operation of this software means. Note that the recording media referred to in this specification are not limited to those for distribution, but also include storage media such as magnetic disks or semiconductor memories provided inside the computer or in devices connected via a network.

[0109] It should be noted that the present invention is not limited to the embodiments described above, and can be modified in various ways during implementation without departing from its essence. Furthermore, each embodiment may be combined as appropriate, and in that case, the combined effects can be obtained. Moreover, the above embodiments include various inventions, and various inventions can be extracted by selecting combinations from the multiple constituent elements disclosed. For example, if the problem can be solved and effects obtained even if some constituent elements are deleted from all the constituent elements shown in the embodiment, then the configuration with these deleted constituent elements can be extracted as an invention.

[0110] 100...Network management device 10...Network configuration extraction unit 20...Network configuration joining unit 30...Network configuration conversion unit 40...Network configuration holding unit 50...Network configuration providing unit

Claims

1. A network management device comprising: a coupling unit that generates information by combining the first and second configuration information, which is based on the same components between different data models of the communication network, and which is included in first configuration information in which the components of the communication network are managed by a first data model and second configuration information in which the components of the communication network are managed by a second data model different from the first data model; and a conversion unit that converts the information generated by the coupling unit into information indicating information objects for each layer of the communication network and reference relationships between the information objects for each layer, based on the layer configuration of the communication network.

2. The network management device according to claim 1, further comprising an extraction unit for extracting components related to the object of conversion by the conversion unit from each of the first and second configuration information, wherein the combining unit generates information in which the first and second configuration information are combined, based on the same components between the different data models as shown by the results extracted by the extraction unit.

3. The network management device according to claim 1, wherein the conversion unit deletes overlapping information objects between information objects represented by first information, which is information converted by the conversion unit based on the components of a first communication network, and information objects represented by second information, which is information converted by the conversion unit based on the components of a second communication network, and generates information by merging the first and second information.

4. A network management method performed by a network management device, comprising: a coupling unit of the network management device generating information which combines the first and second configuration information, based on the same components between different data models of the communication network, and which includes first configuration information in which the components of the communication network are managed by a first data model and second configuration information in which the components of the communication network are managed by a second data model different from the first data model; and a conversion unit of the network management device converting the information generated by the coupling unit into information which indicates information objects for each layer of the communication network and reference relationships between the information objects for each layer, based on the layer configuration of the communication network.

Images