JP7107158B2 - Network management device, method and program - Google Patents

Description

The embodiments of the present invention relate to a network management device, method and program.

Register one or more pieces of specification information including NW characteristics in the specification database from the data that defines the characteristics of the NW (communication network) to be managed in data model format, and associate them with the characteristics included in the specification information. There is a technique for generating an information object representing NW management information based on an information object generation instruction including information for and a value specified for each of one or more items related to this information. The information object includes a value specified for each item included in the information object generation instruction when it matches the format of the corresponding characteristic of the specification information in the specification database (see, for example, Patent Document 1).

In addition, there is a technique of displaying in a common manner without depending on the change of network device type and protocol when holding and displaying the configuration of the physical and logical layers of the network realized by multiple network devices (for example, non-patent See Reference 1).

JP 2018-78523 A

Kimihiko Fukami, Masataka Sato, Kenichi Tayama, Shingo Horiuchi, "A Study on Visualization Method for Multiple Network Configurations", IEICE Technical Report ICM2017-80 (2018-03)

However, with the technology described in Non-Patent Document 1, when a failure occurs in the NW, for example, a device failure, it is difficult to identify which location in the NW configuration (physical or logical layer) the failure location in the NW affects. can't For this reason, it is impossible to display the scope of influence of the failure as a NW configuration, and it is also impossible to acquire the information of customers affected by the failure.

SUMMARY OF THE INVENTION The present invention has been made in view of the above circumstances, and its object is to provide a network management apparatus, method, and program capable of identifying the influence of failures occurring in a communication network. It is in.

To achieve the above object, a first aspect of a network management device of the present invention provides an information object relating to a fault occurrence location in a physical layer of a network configuration, an information object relating to the physical layer of the network configuration and information relating to a logical layer. Acquisition means for acquiring from a storage device in which information indicating a correspondence relationship with an object is stored ; and the location of the failure, which is acquired by the acquisition means among the information objects related to the logical layer stored in the storage device . and an output means for outputting information indicating the failure impact range specified by the specifying means, wherein the information object relating to the logical layer includes an information object relating to a higher hierarchical logical layer and an information object relating to a lower hierarchical logical layer, and the storage device stores the information object relating to the physical layer and the lower hierarchical layer higher than the physical layer. and information indicating a correspondence relationship between an information object relating to the logical layer of the lower hierarchy and an information object relating to the logical layer of the upper hierarchy, wherein the specifying means is , an information object relating to the logical layer of the lower hierarchy, which is associated with the information object relating to the fault occurrence location acquired by the acquiring means, among the information objects relating to the logical layer of each layer stored in the storage device; , and an information object related to the logical layer of the upper hierarchical level, which is associated with the information object related to the logical layer of the lower hierarchical level, is specified as the range of influence of failure .

According to a second aspect of the network management device of the present invention, in the first aspect, the storage device further stores information on subscribers to the service according to the network configuration in association with the information object on the logical layer. and the identifying means identifies the information about the subscriber associated with the information object about the location of the failure acquired by the acquiring means as the information of the subscriber affected by the failure, and the output means is adapted to output the information of the subscribers affected by the failure specified by the specifying means.

A third aspect of the network management device of the present invention is, in the first aspect, the information object relating to the physical layer includes a port object indicating a communication port attached to a communication device, and the information object relating to the logical layer includes a communication and a line or surface object including the point objects, and the correspondence relationship between the physical layer-related information object and the logical layer-related information object is defined by the port object and the It is designed to include correspondence with point objects.

According to a fourth aspect of the network management apparatus of the present invention, in the third aspect, when the information object related to the failure occurrence location acquired by the acquisition means is the port object, the identification means determines the port object. A port object is specified as the failure impact range in the physical layer, and a point object associated with the specified port object and a line or surface object including the point object are specified as the failure impact range in the logical layer. It is designed to

A fifth aspect of the network management device of the present invention is the third aspect, wherein the information object related to the physical layer includes a device object indicating a communication device having the communication port, and the identifying means obtains When the obtained information object related to the location of the failure is the device object, the communication device indicated by the device object and the port object indicating the communication port of the communication device are treated as the fault impact in the physical layer. A point object associated with the identified port object and a line or surface object including the point object are identified as the failure influence area in the logical layer.

A sixth aspect of the network management device of the present invention is the third aspect, wherein the information object related to the physical layer includes a medium object indicating a communication cable connectable to the communication port, and the identifying means includes the obtaining When the information object related to the location of the failure acquired by means is the media object, the communication cable indicated by the media object and the port object indicating the communication port connectable to the communication cable are transferred to the physical device. A point object associated with the identified port object and a line or surface object including the point object are specified as the failure impact range in the logical layer. be.

According to one aspect of the network management method performed by the network management device of the present invention, an information object relating to a failure occurrence location in a physical layer of a network configuration is acquired by an acquisition means of the network management device. and logical layer-related information objects from a storage device that stores information indicating the correspondence relationship between the logical layer-related information objects and the logical layer-related information objects stored in the storage device , specifying the acquired information object associated with the information object related to the failure occurrence location as a failure impact range, and outputting information indicating the specified failure impact range by output means of the network management device and outputting , wherein the information object about the logical layer includes an information object about the logical layer of the upper hierarchy and an information object about the logical layer of the lower hierarchy, and the information about the physical layer is stored in the storage device. Correspondence relationship between objects and information objects relating to the logical layer of the lower hierarchy that is higher than the physical layer, and information objects relating to the logical layer of the lower hierarchy and information objects relating to the logical layer of the higher hierarchy and the specifying means to associate the obtained information object with respect to the location of occurrence of the failure, out of the information objects with respect to the logical layer of each layer stored in the storage device. and an information object related to the logical layer of the upper hierarchy associated with the information object related to the logical layer of the lower hierarchy, and the information object related to the logical layer of the upper hierarchy, which is associated with the information object related to the logical layer of the lower hierarchy. It is intended to include

One aspect of the network management processing program according to one embodiment of the present invention is to cause the processor to function as each means of the network management device in any one of the first to sixth aspects.

According to the first aspect of the network management device according to one embodiment of the present invention, the information object on the logical layer associated with the information object on the failure occurrence location on the physical layer of the network configuration is specified as the failure impact range. Therefore, when a failure occurs in the physical layer, the failure influence range in the logical layer can be appropriately specified.

According to the second aspect of the network management device according to one embodiment of the present invention, the information about the subscriber associated with the information object about the location of the failure is identified as the information about the subscriber affected by the failure. Therefore, communication service subscribers affected by failures can be appropriately identified.

According to the third aspect of the network management device according to one embodiment of the present invention, the correspondence between the physical layer and the logical layer is defined by the correspondence between the port object in the physical layer and the point object in the logical layer. , it is possible to appropriately specify the range of impact due to the occurrence of a failure.

According to the fourth aspect of the network management device according to the embodiment of the present invention, when the location of failure is a communication port, the port object is identified as the failure impact range in the physical layer, and the port object and Since the associated point object and the line or surface object including the point object are identified as the failure impact range in the logical layer, the failure impact range is appropriately specified when the failure occurs at the communication port. can be done.

According to the fifth aspect of the network management device according to one embodiment of the present invention, when a fault occurs in a communication device, the communication device indicated by the device object and the communication port of the communication device are The indicated port object is specified as the fault impact range in the physical layer, and the point object associated with this port object and the line or surface object including the point object are specified as the fault impact range in the logical layer. It is possible to appropriately specify the failure influence range when the location of occurrence is a device.

According to the sixth aspect of the network management device according to one embodiment of the present invention, when a fault occurs in a communication medium, the communication cable indicated by the medium object and the communication connectable to the communication cable A port object indicating a port is identified as a failure area of influence in the physical layer, and a point object associated with this port object and a line or surface object including the point object are identified as a failure area of influence in the logical layer. It is possible to appropriately specify the failure influence range when the location of the failure is the communication medium.

In other words, according to each aspect of the present invention, it is possible to identify the impact of a fault that has occurred in a communication network.

FIG. 4 is a diagram showing an example of network configuration modeling applied to the network management apparatus according to the first embodiment of the present invention in tabular form; FIG. 4 is a diagram showing an application example of a physical entity applied to the network management device according to the first embodiment of the present invention; FIG. 4 is a diagram showing an application example of logical entities applied to the network management device according to the first embodiment of the present invention; FIG. 4 is a diagram showing, in tabular form, an example of a physical layer PS Entity definition applied to the network management device according to the first embodiment of the present invention; FIG. 4 is a diagram showing, in tabular form, an example of a PD Entity definition of the physical layer applied to the network management device according to the first embodiment of the present invention; FIG. 4 is a diagram showing, in tabular form, an example of the definition of a PP Entity in the physical layer applied to the network management device according to the first embodiment of the present invention; FIG. 4 is a diagram showing, in tabular form, an example of a physical layer AS Entity definition applied to the network management device according to the first embodiment of the present invention; FIG. 4 is a diagram showing, in tabular form, an example of PL Entity definitions in the physical layer applied to the network management device according to the first embodiment of the present invention; FIG. 4 is a diagram showing, in tabular form, an example of a physical layer PC Entity definition applied to the network management device according to the first embodiment of the present invention; FIG. 4 is a table showing an example of definitions of LC Entity, XC Entity, TL Entity, and NFD Entity in the logical layer applied to the network management device according to the first embodiment of the present invention; FIG. 4 is a diagram showing, in tabular form, an example of definitions of TPE Entities in the logical layer applied to the network management device according to the first embodiment of the present invention; FIG. 4 is a diagram showing, in tabular form, an example of definitions of NC entities in a logical layer applied to the network management device according to the first embodiment of the present invention; FIG. 4 is a diagram for explaining an example of creation of an Entity by the network management device according to the first embodiment of the present invention; FIG. 11 is a diagram for explaining an example of designation of occurrence of a port failure in an Entity to be managed by the network management device according to the second embodiment of the present invention; FIG. 10 is a diagram illustrating an example of the range of influence of the physical layer on entities managed by the network management device according to the second embodiment of the present invention; FIG. 11 is a diagram illustrating an example of an influence range of a Logical Device layer in an entity to be managed by the network management device according to the second embodiment of the present invention; FIG. 11 is a diagram illustrating an example of an influence range of an OTN layer in an Entity managed by a network management device according to the second embodiment of the present invention; FIG. 11 is a diagram illustrating an example of the influence range of the ETH layer in entities managed by the network management device according to the second embodiment of the present invention; FIG. 9 is a diagram illustrating an example of the influence range of the IP layer in the entities managed by the network management device according to the second embodiment of the present invention; FIG. 11 is a diagram for explaining an example of designation of occurrence of a port failure in an entity to be managed by a network management device according to the third embodiment of the present invention; FIG. 11 is a diagram illustrating an example of the range of influence of the physical layer on entities managed by the network management device according to the third embodiment of the present invention; FIG. 11 is a diagram illustrating an example of the influence range of the Logical Device layer in the Entity to be managed by the network management device according to the third embodiment of the present invention; FIG. 11 is a diagram illustrating an example of the range of influence of the OTN layer on entities managed by the network management device according to the third embodiment of the present invention; FIG. 11 is a diagram illustrating an example of the influence range of the ETH layer in entities managed by the network management device according to the third embodiment of the present invention; FIG. 11 is a diagram illustrating an example of an influence range of an IP layer in an Entity to be managed by the network management device according to the third embodiment of the present invention; FIG. 11 is a diagram for explaining an example of designation of occurrence of a medium failure in an Entity to be managed by a network management device according to the fourth embodiment of the present invention; FIG. 12 is a diagram illustrating an example of the range of influence of the physical layer on entities managed by the network management device according to the fourth embodiment of the present invention; FIG. 12 is a diagram illustrating an example of the influence range of the Logical Device layer in the Entity to be managed by the network management device according to the fourth embodiment of the present invention; FIG. 12 is a diagram illustrating an example of the influence range of the OTN layer in the entities managed by the network management device according to the fourth embodiment of the present invention; FIG. 11 is a diagram illustrating an example of the influence range of the ETH layer in entities managed by the network management device according to the fourth embodiment of the present invention; FIG. 11 is a diagram illustrating an example of the influence range of the IP layer in entities managed by the network management device according to the fourth embodiment of the present invention; The figure explaining an example of the functional outline of the failure influence grasping system which concerns on the 5th Embodiment of this invention. The figure which shows the functional structural example of the failure influence grasping system which concerns on the 5th Embodiment of this invention. FIG. 11 is a sequence diagram showing an example of a procedure for registering facility information by the system for grasping the effects of failure according to the sixth embodiment of the present invention; The figure which shows an example of Spec (physical layer) of the installation information hold|maintained by the failure influence grasping system which concerns on the 6th Embodiment of this invention in a tabular form. The figure which shows an example of the spec (logical layer) of the installation information hold|maintained by the failure influence grasping system which concerns on the 6th Embodiment of this invention in a tabular form. FIG. 11 is a diagram showing an example of the use of Spec and Entity classes by the failure impact assessment system according to the sixth embodiment of the present invention; FIG. 12 is a diagram showing in tabular form an example of a schema of a specificity table of equipment information defined by the failure impact grasping system according to the sixth embodiment of the present invention; FIG. 12 is a diagram showing an example of a schema of an Entity table of equipment information defined by the failure impact grasping system according to the sixth embodiment of the present invention in tabular form; FIG. 12 is a diagram showing an example of a configuration functioning by inputting a failure location in a failure influence grasping system according to a seventh embodiment of the present invention; FIG. 21 is a diagram showing an example of a configuration functioning to display the extent of influence in the failure influence grasping system according to the eighth embodiment of the present invention; FIG. 21 is a sequence diagram showing an example of a processing procedure for displaying an influence range by the failure influence grasping system according to the eighth embodiment of the present invention; FIG. 12 is a flow chart showing an example of a processing procedure by the NW influence range calculation unit of the failure influence grasping system according to the eighth embodiment of the present invention; FIG. FIG. 12 is a flow chart showing an example of a procedure for displaying a configuration of a physical layer by a NW configuration display unit of the system for grasping the effects of failure according to the eighth embodiment of the present invention; FIG. FIG. 14 is a flow chart showing an example of a procedure for displaying layer-specific information by the NW configuration display unit of the failure influence grasping system according to the eighth embodiment of the present invention; FIG. 14 is a flow chart showing an example of a procedure for displaying the configuration of the logical layer by the NW configuration display unit of the failure influence grasping system according to the eighth embodiment of the present invention; FIG. 12 is a flow chart showing an example of a procedure for displaying items other than TPE by the NW configuration display unit of the failure influence grasping system according to the eighth embodiment of the present invention; FIG. FIG. 12 is a flow chart showing an example of a procedure for displaying items other than TPE by the NW configuration display unit of the failure influence grasping system according to the eighth embodiment of the present invention; FIG.

An embodiment according to the present invention will be described below with reference to the drawings.
A network management device according to an embodiment of the present invention models each component of a physical layer and a logical layer of a communication network with a unified information object (hereinafter simply referred to as an object), and uses the connection between each object. to identify the range affected by the failure, and to identify the communication service users affected by the failure from the user information associated with the object.
As a result, the affected service users and the extent of the impact of failures that occur in a network composed of multiple layers with different protocols and media types can be identified.

Next, an overview of the network management device according to one embodiment of the present invention will be described. First, regarding the modeling of the NW configuration, the following 1-1. ~ 1-7. will explain.
1-1. A NW device in the physical layer is held as a device object, a communication port in the physical layer is held as a port object, and a communication medium in the physical layer is held as a medium object.

1-2. A point object at which communication originates or terminates in the logical layer is held, and a communication between these point objects and a communicable range thereof are held as line or plane objects, respectively.

1-3. The logical layer also holds communication objects. This communication object has a point object array that stores all point objects between the start point and the end point on the logical layer, information about service subscribers, and state, respectively.
1-4. Device objects and port objects have states and coordinates, respectively, and media objects have states.

1-5. A point object has a lower object (a point object corresponding to the lower layer), a state and coordinates, respectively, and a line or plane object has a state and a point object array respectively. This point object array holds the point object names that make up the line or plane object. A point object can hold not only lower objects but also upper objects (point objects corresponding to upper layers).

1-6. Maintains relationships between physical layer objects and logical layer objects. Specifically, subordinate objects of point objects hold corresponding physical layer port objects.

1-7. Maintain object relationships between logical layers. Specifically, the lower object of the point object holds the point object where the type of the lower layer changes.

Secondly, regarding the identification and display of the extent of influence (failure due to port failure), see 2-1 below. ~2-7. will explain. 2-1. ~2-4. corresponds to specifying the scope of influence; 2-5. ~2-7. corresponds to the indication of the extent of influence.

2-1. If the fault location is a port, the port object corresponding to that port is set to NG, which indicates that a fault has occurred.
2-2. Set the state of the point object on the logical layer corresponding to the port object to NG.

2-3. Identify the area of influence of a point object. Specifically, the state of the point object array, which includes the above point objects and constitutes the communication objects of the upper layer with respect to the physical layer, is set to NG.

2-4. Repeatedly search for points, lines (or planes), and communication objects in one layer higher layer corresponding to the point object array that corresponds to the location of the failure and that constitutes the above communication object, and repeats the above 2- 3. process.

2-5. Display the communication objects, points and line (or plane) objects that make up all the logical layers, respectively. At the same time, if the status of this object is set to NG, the corresponding object will be displayed in red.
2-6. 2-4. The point object indicated by , and its subordinate objects are retrieved and displayed by connecting them with a dotted line.

2-7. Drawing objects, which are graphics representing physical layer devices, ports, and medium objects, are displayed, and when the port object status is set to NG, the corresponding port object is displayed in red.
Thirdly, regarding the identification and display of the affected range (equipment failure), the following 3-1. ~3-7. will explain. 3-1. ~3-4. corresponds to specifying the scope of influence; 3-5. ~3-7. corresponds to the indication of the extent of influence.

3-1. If the location of the failure is a device, NG is set to the status of the device object corresponding to the device and the port object of the device. Equipment failure occurs when a building is submerged, power depleted, or collapsed, or when a failure occurs in the equipment itself.
3-2. NG is set to the state of the point or line (or plane) object on the logical layer corresponding to the device object.

3-3. Identify the range of influence of line (or plane) objects. Specifically, 3-2. Search for communication, point and line (or plane) objects in the upper layer that contain any of the elements of the point object array that composes the line (or plane) object explained in , and set the state of the corresponding object to NG. do.
3-4. 3-3. Objects in one layer higher layer including any of the communication, point, and line (or plane) objects described in 1) are searched, and this search is repeated up to the highest layer.

3-5. Display the communication objects, points and line (or plane) objects that make up all the logical layers, respectively. In addition, if the status of the above object is set to NG, the corresponding object will be displayed in red.
3-6. 3-5. The point object and its subordinate objects are retrieved and displayed by connecting them with a dotted line.

3-7. Drawing objects representing the device, port, and medium objects of the physical layer are displayed, and if the state of the device object is set to NG, the corresponding device object is displayed in red.
Fourthly, regarding the identification and display of the affected range (in the case of media failure), see 4-1 below. ~ 4-6. will explain. 4-1. ~ 4-3. corresponds to specifying the scope of influence; 4-4. ~ 4-6. corresponds to the indication of the extent of influence.

4-1. If the location of the failure is a media object, set the status of the communication medium (including the connector for connecting the communication medium, if any) to NG, and also set the port object (communication (corresponding to the communication port that can be connected to the media connector) and set the status of this port object to NG. Media objects can fail when cables are cut, corroded, and so on.
4-2. Let the state of the point object on the logical layer of each layer corresponding to the retrieved port object be NG.
4-3. 4-2. The state of upper layer communication and line (or plane) objects to the physical layer, including all point objects, is NG.

4-4. Display the communication objects, points and line (or plane) objects that make up all the logical layers. In addition, if the status of the above object is NG, this object is displayed in red. The upper layer object retrieval method is implemented by retrieving upper layer objects, including point and line (or plane) objects.

4-5. 4-4. , and their subordinate objects are retrieved and displayed by connecting them with dotted lines.
4-6. Physical layer device, medium, and port objects are displayed, and when the status of each object is set to NG, the corresponding object is displayed in red.

(First embodiment)
Next, a first embodiment will be described. First, the method of modeling the NW configuration (physical and logical layers) will be explained.
FIG. 1 is a diagram showing, in tabular form, an example of network configuration modeling applied to the network management apparatus according to the first embodiment of the present invention.

As shown in Figure 1, the configuration of the physical layer consists of PS (Physical Structure), PD (Physical Device), PP (Physical Port), AS (Aggregate Section), PL (Physical Link), and PC (Physical Connector). Entity (information object) is applied, and the logical layer configuration is TL (Topological Link), NFD (Network Forwarding Domain), TPE (Termination Point Encapsulation), NC (Network Connection), LC (Link Connect), XC (Cross ( X) Apply the Entity that becomes Connect). Such adaptation allows the configuration of the physical and logical layers to be kept in a uniform format.

As shown in FIG. 1, Entity names in the physical layer are classified into PS, PD, PP, AS, PL, and PC. The "Entity name: Meaning: Correspondence relationship" for each Entity name is as follows.
・PS (Physical Structure): facilities such as accommodation buildings and manholes: equipment objects ・PD (Physical Device): equipment: equipment objects ・PP (Physical Port): communication ports possessed by equipment: port objects ・AS (Aggregate Section): Cable: Media object PL (Physical Link): Cable core: Media object PC (Physical Connector): Cable connection connector: Media object

As shown in FIG. 1, Entity names in the logical layer are classified into TL, NFD, TPE, NC, LC, and XC. The "Entity name: Meaning: Correspondence relationship" for each Entity name is as follows.
・TL (Topological Link): Connectivity between devices (within Logical Device layer (sometimes called LD layer)): Line object ・NFD (Network Forwarding Domain): Transferable range within device (within Logical Device layer) ): Line or plane object ・TPE (Termination Point Encapsulation): Communication termination point: Point object ・NC (Network Connection): End-End connectivity formed by LC and XC (described later) (in communication layer): Communication object ・LC (Link Connect): Connectivity between devices (in communication layer): Line or plane object ・XC (Cross(X) Connect): Connectivity in device (in communication layer): Line or plane object

Next, an application example of physical Entity will be explained. FIG. 2 is a diagram showing an application example of physical entities applied to the network management device according to the first embodiment of the present invention.
As shown in FIG. 2, Physical Resources are divided into an equipment layer and a building layer.

In the example shown in FIG. 2, the physical resource device layer is PD (NW device), PD (CTF (Cable termination Frame: optical fiber termination device), PL (core line), PC (connector), PP (port) PD (NW device) and PD (CTF) are provided with PP (port), and PC (connector) is attached to both ends of PL (core wire).

The PP (port) on the PD (NW device) side is connected to the PC (connector) at one end of the PL (core wire), and the PP (port) on the PD (CTF) side is connected to the PC (port) at the other end of the PL (core wire). connector), the PD (NW device) and the PD (CTF) are communicably connected. The same applies to the connection between PDs (CTFs).

In the example shown in FIG. 2, the physical resource building layer has PS (station building), PD (NW device), PD (CTF), and Aggregate Section (cable).
Aggregate Section is an object that has multiple PLs (Core Lines).

A PD (NW device) and a PD (CTF) are provided in the PS (station building) and are communicably connected. In the example shown in Figure 2, the PD (CTF) in the first PS (station building) and the PD (CTF) in the second PS (station building) communicate via the Aggregate Section (cable). Connected as possible.

Next, application examples of logical entities will be explained. FIG. 3 is a diagram showing an application example of logical entities applied to the network management device according to the first embodiment of the present invention.
In FIG. 3, Physical Resource has a device layer, and Logical Resource has a communication layer and a Logical Device layer. The Logical Device layer corresponds to a subordinate object to the Communication layer, and the Device layer corresponds to a subordinate object to the Logical Device layer. In the example shown in FIG. 3, in the device layer, the PPs of the Physical Device are connected to the PCs at one end and the other end of the PL.
Corresponding communication layers have TPE, XC, LC, and Logical Device layers have TPE, NFD, TL.

In the example shown in FIG. 3, the Physical Device in the device layer corresponds to XC in the communication layer and NFD in the Logical Device layer, respectively.
The Physical Device PP corresponds to the communication layer TPE and the Logical Device layer TPE, respectively. The same is true for the PC attached to the PL.
The PL of the device layer corresponds to the LC of the communication layer and the TL of the Logical Device layer, respectively. Also, one NC is formed by XC and LC of the communication layer.

Next, the Entity definition of the physical layer will be explained. FIG. 4 is a diagram showing, in tabular form, an example of the definition of the PS Entity of the physical layer applied to the network management device according to the first embodiment of the present invention.
As shown in FIG. 4, PS Entity has state, coordinates, and device object array as attribute names. The "attribute name: type" in each attribute name is as follows.
・State: String (submerged, power exhausted, collapsed)
• Coordinates: Integer array with two-dimensional coordinates • Device object array: Array for storing device objects (PD) The setting of the number of dimensions in the coordinates will be described later.

FIG. 5 is a diagram showing, in tabular form, an example of the definition of the PD Entity of the physical layer applied to the network management device according to the first embodiment of the present invention.
As shown in FIG. 5, PD Entity has state, coordinates, and port objects as attribute names. The "attribute name: type" in each attribute name is as follows.
・State: Boolean
・Coordinates: Integer array with two-dimensional coordinates ・Port objects: Arrays that store port objects (PP)

FIG. 6 is a diagram showing, in tabular form, an example of the definition of the PP Entity of the physical layer applied to the network management device according to the first embodiment of the present invention.
As shown in FIG. 6, PP Entity has state and coordinates as attribute names. The "attribute name: type" in each attribute name is as follows.
・State: Boolean
・Coordinates: Integer array with 2D coordinates

FIG. 7 is a diagram showing, in tabular form, an example of AS Entity definitions in the physical layer applied to the network management apparatus according to the first embodiment of the present invention.
As shown in FIG. 7, AS Entity has state and media object array as attribute names. The "attribute name: type" in each attribute name is as follows.
・State: String (connected, disconnected, corroded)
・Media object array: An array that stores media objects (PL)

FIG. 8 is a diagram showing, in tabular form, an example of PL Entity definitions in the physical layer applied to the network management apparatus according to the first embodiment of the present invention.
As shown in FIG. 8, the PL Entity has state and connector object array as attribute names. The "attribute name: type" in each attribute name is as follows.
・Status: Boolean (connection, disconnection)
・Connector object array: An array that stores connector objects (PC)

FIG. 9 is a diagram showing, in tabular form, an example of a physical layer PC Entity definition applied to the network management apparatus according to the first embodiment of the present invention.
As shown in FIG. 9, PL Entity has state and port objects as attribute names. The "attribute name: type" in each attribute name is as follows.
・Status: Boolean (connected, disconnected)
・Port object: An array that stores port objects (PP)

Next, the Entity definition of the logical layer will be explained. FIG. 10 is a table showing an example of definitions of LC Entity, XC Entity, TL Entity, and NFD Entity in the logical layer applied to the network management device according to the first embodiment of the present invention.
As shown in FIG. 10, LC Entity, XC Entity, TL Entity, and NFD Entity have point connector object array and state as attribute names. The "attribute name: type" in each attribute name is as follows.
・Point object array: TPE (point object) array that configures LC, XC, TL, NFD ・Status: Boolean

FIG. 11 is a diagram showing, in tabular form, an example of the definition of the TPE Entity of the logical layer applied to the network management device according to the first embodiment of the present invention.
As shown in FIG. 11, TPE Entity has lower object, port object array, coordinates, and status as attribute names. The "attribute name: type" in each attribute name is as follows.
・Lower object: Point object (TPE) corresponding to the lower layer
・Port object array: Array that stores port objects (PP) ・Coordinates: Integer array with two-dimensional coordinates ・Status: Boolean

FIG. 12 is a diagram showing, in tabular form, an example of the definition of NC entities in the logical layer applied to the network management device according to the first embodiment of the present invention.
As shown in FIG. 12, NC Entity has point object array, status, and service subscriber information as attribute names. The "attribute name: type" in each attribute name is as follows.
・Point object array: All TPE (point object) arrays between the communication start point and end point ・Status: Boolean
・Service subscriber information: String array or URL
The service subscriber information may be information acquired from OpS (operation system) data for each NC, or may be information specified by the URL of the OpS subscriber information acquisition IF.

Next, Entity creation is explained. FIG. 13 is a diagram illustrating an example of creating an Entity by the network management device according to the first embodiment of the present invention.
FIG. 13 describes the creation of points, lines or planes and communication objects.

In the example shown in FIG. 13, the logical layer has an IP (Internet Protocol) layer, an ETH (Ethernet (registered trademark)) layer, an OTN (Optical Transport Network) layer, and a Logical Device layer. has a Physical layer. Dotted lines between layers in FIG. 13 indicate the correspondence between objects in each layer.

(IP layer)
The IP layer has TPE (CP (Connection Point)) (1_IP, 2_IP), LC (3_IP), NC (4_IP).
(ETH layer)
The ETH layer has TPE(CP)(1-12_Eth), LC(13, 16, 18, 20, 23_Eth), XC(14, 15, 17, 19, 21, 22_Eth), NC(24_Eth).
1 to 12_Eth are provided in numerical order from the 1_IP side to the 2_IP side. 13 to 23_Eth are the same. For example, 13_Eth is provided between 1 and 2_Eth, and 23_Eth is provided between 11 and 12_Eth.
1, 12_Eth corresponds to 1, 2_IP of the IP layer on a one-to-one basis.

(OTN layer)
The OTN layer has TPE(CP)(1-4_OT), XC(5, 7_OT), LC(6_OT), NC(8_OT).
1_OT to 4_OT are provided in numerical order from the 1_IP side to the 2_IP side. 5_OT to 7_OT are the same. For example, 5_OT is provided between 1 and 2_OT, 6_OT is provided between 2 and 3_OT, and 7_OT is provided between 3 and 4_OT.
1, 4_OT correspond one-to-one to 6, 7_Eth of the ETH layer. Also, 5 to 8_OT correspond to 18_Eth of the ETH layer.

(Logical Device layer)
The Logical Device layer has TPE (CP) (1-14_LD), TL (15-19_LD), NFD (20-27_LD).
1 to 14_LD are provided in numerical order from the 1_IP side to the 2_IP side. The same applies to 15-19_LD and 20-27_LD. For example, 15_LD is provided between 1 and 2_LD, and 19_LD is provided between 13 and 14_LD.
20_LD for NFD between 2 and 3_LD, 21_LD for NFD between 3 and 4_LD, 22_LD for NFD between 5 and 6_LD, 23_LD for NFD between 6 and 7_LD, 24_LD for NFD between 8 and 9_LD, 25_LD corresponds to NFD between 9 and 10_LD, 26_LD corresponds to NFD between 11 and 12_LD, and 27_LD corresponds to NFD between 12 and 13_LD.

1 to 14_LD correspond one-to-one to 1 to 6_Eth, 2, 3_OT, and 7 to 12_Eth of the ETH and OTN layers.
15 to 19_LD correspond to 12, 15, 18, 20, 22_Eth of the ETH layer on a one-to-one basis. 17_LD also corresponds to 6_OT in the OTN layer.
5 to 7_LD also correspond to OTN layer 1, 2, 5, 8_OT.

(Physical layer)
Physical layer is Router (1st (1_IP side)), L2SW (L2 switch) (1st (1_IP side)), OTN (1st (1_IP side)), OTN (2nd (2_IP side) ), L2SW (second (2_IP side)), Router (second (2_IP side)) are connected in series from 1_IP side to 2_IP side so as to be able to communicate in series, and PPs are provided in numerical order from 1_IP side to 2_IP side ( 1, 3, 5, 7, 9, 11, 13, 15, 17, 19_PH), PC (2, 4, 6, 8, 10, 12, 14, 16, 18, 20_PH), PL (21～25_PH) , with PD (26-29_PH).

21_PH between Router (1st) and L2SW (1st) is 15_LD of Logical Device layer, 22_PH between L2SW (1st) and OTN (1st) is 16_LD, OTN (1st) , 23_PH between OTN (2nd) to 17_LD, 24_PH between OTN (2nd) and L2SW (2nd) to 18_LD, 25_PH between L2SW (2nd) and Router (2nd) correspond to 19_LD respectively.
7, 9, 27_PH correspond to 5 to 7_LD.

26_PH to 29_PH correspond one-to-one to L2SW (first), OTN (first), OTN (second), and L2SW (second). 26_PH corresponds to 20 and 21_LD, 27_PH to 22 and 23_LD, 28_PH to 24 and 25_LD, and 29_PH to 26 and 27_LD, respectively.

1, 3_PH to PP between Router (1st) and L2SW (1st), 5, 7_PH to PP between L2SW (1st) and OTN (1st), 9, 11_PH to OTN ( 1st), PP between OTN (2nd), 13, 15_PH is PP between OTN (2nd), L2SW (2nd), 17, 19_PH is L2SW (2nd), Router (Second) correspond to each PP between.

2, 4_PH to PC between Router (1st) and L2SW (1st), 6, 8_PH to PC between L2SW (1st) and OTN (1st), 10, 12_PH to OTN ( 1st), PC between OTN (2nd), 14, 16_PH to PC between OTN (2nd), L2SW (2nd), 18, 20_PH to L2SW (2nd), Router (Second) corresponds to each PC between.

Also, 1, 2_PH to 1_LD, 3, 4_PH to 2_LD, 5, 6_PH to 4_LD, 7, 8_PH to 5_LD, 9, 10_PH to 7_LD, 11, 12_PH to 8_LD, 13, 14_PH to 10_LD , 15, 16_PH correspond to 11_LD, 17, 18_PH to 13_LD, and 19, 20_PH to 14_LD, respectively.

(Second embodiment)
Next, a second embodiment will be described. In this second embodiment, the identification and display of the affected range associated with the occurrence of a port error in a managed entity will be described.
First, the identification and display of the affected area (when a port failure occurs) will be explained. 14A and 14B are diagrams illustrating an example of designation of occurrence of a port failure in an Entity to be managed by the network management device according to the second embodiment of the present invention.
In the example shown in FIG. 14, the user designates that a failure has occurred in the PP (port) on the OTN (second) side of the OTN (first).

Next, a method for specifying the range of influence of the physical layer will be described. FIG. 15 is a diagram illustrating an example of the range of influence of the physical layer in the Entity managed by the network management device according to the second embodiment of the present invention.
In the example shown in FIG. 15, only PP(9_PH), which is a port object corresponding to the port of the specified physical layer fault location, is identified as the affected range.

Next, a method for specifying the influence range of the Logical Device layer will be described. FIG. 16 is a diagram illustrating an example of the influence range of the Logical Device layer in the Entity managed by the network management apparatus according to the second embodiment of the present invention.
In the example shown in FIG. 16, TPE (7_LD) in the Logical Device layer corresponding to PP (9_PH), which is the port of the failure location in the Physical layer, is identified as the affected range.

Next, a method for specifying the influence range of the OTN layer will be described. FIG. 17 is a diagram illustrating an example of the influence range of the OTN layer in the entities managed by the network management device according to the second embodiment of the present invention.
In the example shown in FIG. 17, the TPE (2_OT) of the OTN layer corresponding to the TPE (7_LD) of the Logical Device layer and the NC (8_OT) related to the TPE are specified as the influence range.

Next, a method for identifying the affected area of the ETH layer will be explained. FIG. 18 is a diagram illustrating an example of the influence range of the ETH layer in entities managed by the network management device according to the second embodiment of the present invention.
In the example shown in FIG. 18, LC, NC (18, 24_Eth) of the ETH layer corresponding to NC (8_OT) of the OTN layer is specified as the influence range.

Next, a method for specifying the influence range of the IP layer will be explained. FIG. 19 is a diagram illustrating an example of the influence range of the IP layer in entities managed by the network management device according to the second embodiment of the present invention.
In the example shown in FIG. 19, LC, NC (3, 4_IP) on the IP layer corresponding to NC (24_Eth) on the ETH layer is specified as the influence range.

(Third embodiment)
Next, a third embodiment will be described. In the third embodiment, identification and display of the affected range due to the occurrence of a device failure in a managed Entity will be described.
First, identification and display of the affected range (in the case of device failure) will be described. FIG. 20 is a diagram for explaining an example of port failure designation in a managed entity by the network management device according to the third embodiment of the present invention.
In the example shown in FIG. 20, the user designates that a failure has occurred in the OTN (first).

Next, a method for specifying the range of influence of the physical layer will be described. FIG. 21 is a diagram illustrating an example of the influence range of the physical layer in the Entity managed by the network management device according to the third embodiment of the present invention.
In the example shown in FIG. 21, the OTN device (first), which is the PP (failure location), which is the device at the failure location in the specified physical layer, the device object (27_PH) of the main body, the OTN device (first ) are identified in the order of port objects (7, 9_PH) of both ports.

Next, a method for specifying the influence range of the Logical Device layer will be described. FIG. 22 is a diagram illustrating an example of the influence range of the Logical Device layer in the Entity managed by the network management apparatus according to the third embodiment of the present invention.
In the example shown in FIG. 22, TPE (5 to 7_LD) and NFD (22, 23_LD) of the Logical Device layer corresponding to the range of influence of the failure of the device at the failure location of the Physical layer are specified as the range of influence.

Next, a method for specifying the influence range of the OTN layer will be explained. FIG. 23 is a diagram illustrating an example of the influence range of the OTN layer in the entities managed by the network management device according to the third embodiment of the present invention.
In the example shown in FIG. 23, TPE (1, 2_OT), XC of the OTN layer corresponding to NFD (22, 23_LD) of the Logical Device layer, that is, including all the elements of the point object array of NFD (22, 23_LD) (5_OT), NC(8_OT), and TPE(5,6_Eth), XC(17_Eth), NC(24_Eth) of the ETH layer are identified as the influence range.

Next, a method for identifying the affected area of the ETH layer will be explained. FIG. 24 is a diagram illustrating an example of the influence range of the ETH layer in the Entity managed by the network management device according to the third embodiment of the present invention.
In the example shown in FIG. 24, LC(18_Eth) of the ETH layer corresponding to TPE(1,2_OT) and NC(8_OT) of the OTN layer is specified as the influence range.

Next, a method for specifying the influence range of the IP layer will be explained. FIG. 25 is a diagram illustrating an example of the influence range of the IP layer in entities managed by the network management device according to the third embodiment of the present invention.
In the example shown in FIG. 25, LC(3_IP) and NC(4_IP) on the IP layer corresponding to NC(24_Eth) on the ETH layer are specified as the influence range.

(Fourth embodiment)
Next, a fourth embodiment will be described. In this fourth embodiment, the identification and display of the affected range due to the occurrence of a media failure in a managed Entity will be described.
First, the identification and display of the affected range (when a media failure occurs) will be described. FIG. 26 is a diagram illustrating an example of specification of occurrence of a medium failure in an Entity to be managed by the network management device according to the fourth embodiment of the present invention.
In the example shown in FIG. 26, the user specifies that a failure has occurred in the medium between the OTN (first) and OTN (second).

Next, a method for specifying the range of influence of the physical layer will be described. FIG. 27 is a diagram illustrating an example of the influence range of the physical layer in the Entity managed by the network management device according to the fourth embodiment of the present invention.
In the example shown in FIG. 27, PL (communication cable at failure location) (23_PH) between OTN (first) and OTN (second) of the specified Physical layer (23_PH), PC (communication cable Both connectors) (10, 12_PH) and the PP (9, 11_PH) of the OTN device (1st and 2nd) are identified in this order. This PP corresponds to a communication port of each OTN device that can be connected to both connectors of the faulty communication cable.

Next, a method for specifying the influence range of the Logical Device layer will be described. FIG. 28 is a diagram illustrating an example of the influence range of the Logical Device layer in the Entity managed by the network management apparatus according to the fourth embodiment of the present invention.
In the example shown in FIG. 28, TPE(7, 8_LD) and TL(17_LD) of the Logical Device layer corresponding to the influence range of the medium of the failure location of the Physical layer are specified as the influence range.

Next, a method for specifying the influence range of the OTN layer will be explained. FIG. 29 is a diagram illustrating an example of the influence range of the OTN layer in the Entity managed by the network management device according to the fourth embodiment of the present invention.
In the example shown in FIG. 29, TPE (2, 3_OT), LC (6_OT), and NC (8_OT) of the OTN layer corresponding to TPE (7, 8_LD) and TL (17_LD) of the Logical Device layer are the influence range. Each is specified.

Next, a method for identifying the affected area of the ETH layer will be explained. FIG. 30 is a diagram illustrating an example of the influence range of the ETH layer in entities managed by the network management device according to the fourth embodiment of the present invention.
In the example shown in FIG. 30, LC(18_Eth) and NC(24_Eth) of the ETH layer corresponding to NC(8_OT) of the OTN layer are specified as the influence range.

Next, a method for specifying the influence range of the IP layer will be explained. FIG. 31 is a diagram illustrating an example of the influence range of the IP layer in the entities managed by the network management device according to the fourth embodiment of the present invention.
In the example shown in FIG. 31, LC(3_IP) and NC(4_IP) of the IP layer corresponding to NC(24_Eth) of the ETH layer are specified as the influence range.

(Fifth embodiment)
Next, a fifth embodiment will be described. In this fifth embodiment, an overview of the functions of a failure impact grasping system that implements a network management device will be described.
FIG. 32 is a diagram illustrating an example of a functional overview of the failure impact grasping system according to the fifth embodiment of the present invention.

In the failure impact assessment system shown in FIG. 32, equipment information (Spec (network characteristics), Entity (information object)) is registered, and when information on the location of failure is entered, this location of failure is included in the NW configuration (physical/logical layer ) can be displayed on the display device, and the number of disabled users can also be displayed on the display device.
Disabled user display can be realized by displaying attribute values of communication objects (NC) on a display device.

Next, a system configuration diagram of the failure influence grasping system will be described.
FIG. 33 is a diagram showing a functional configuration example of a failure influence grasping system according to the fifth embodiment of the present invention.
In the example shown in FIG. 33 , the failure impact assessment system can be configured as a computer having a central processing unit (CPU), a program memory, an arithmetic memory, etc. As shown in FIG. As functions necessary for carrying out this embodiment, it has a facility information registration unit 11, a Spec DB (database) 12, an Entity DB 13, a failure location entity acquisition unit 14, a NW influence range calculation unit 15, and a NW configuration display unit 16. . These processes will be described later.

The equipment information registration unit 11, the failure location entity acquisition unit 14, the NW influence range calculation unit 15, and the NW configuration display unit 16 can be realized by causing the CPU to execute the programs stored in the program memory. The Spec DB 12 and Entity DB 13 can be realized by a storage device such as a nonvolatile memory, and the NW configuration display section 16 can be realized by including a liquid crystal display or the like. The failure impact assessment system can also be configured with hardware, but a program having the procedures shown in the flow charts described later is installed in a well-known computer via a medium or communication line, and this computer and Spec DB 12 , Entity DB 13, or a computer having Spec DB 12, Entity DB 13, or the like.

(Sixth embodiment)
Next, a sixth embodiment will be described. In this sixth embodiment, the details of the failure influence grasping system will be described.
First, the registration of equipment information (Spec (Specification), Entity (entity)) will be explained. FIG. 34 is a sequence diagram showing an example of a procedure for registering equipment information by the system for grasping the effects of failure according to the sixth embodiment of the present invention.
First, when the operator registers the equipment information (Spec) on the management screen, this equipment information (Spec) is registered in the Spec DB 12, the registration result code is returned to the management screen, and the registration result is displayed on the operator's display screen. returned.

Next, Spec (physical layer) of equipment information will be described. FIG. 35 is a diagram showing an example of Spec (physical layer) of equipment information held by the failure impact grasping system according to the sixth embodiment of the present invention in tabular form.
In the physical layer, attributes that are unique information such as device names or cable types are held in the Spec DB 12 as information obtained by instantiating a Spec (Specification) class (defining attributes indicating characteristics). Specifically, the following Spec classes are defined.
These Specs are mainly used to display the NW configuration.

"Spec name: meaning" in the physical layer is as follows.
・PS Spec (Physical Structure Specification): Defines unique attributes for each PS ・PD Spec (Physical Device Specification): Defines unique attributes for each PD ・PP Spec (Physical Port Specification): Defines unique attributes for each PP Definition AS Spec (Aggregate Section Specification): Defines unique attributes for each AS PL Spec (Physical Link Specification): Defines unique attributes for each PL PC Spec (Physical Connector Specification): Unique attributes for each PC define

Next, Spec (logical layer) of equipment information will be described. FIG. 36 is a diagram showing an example of spec (logical layer) of facility information held by the failure impact grasping system according to the sixth embodiment of the present invention in tabular form.
In the logical layer, attributes unique to each layer (VLANID, IP address, wavelength number, etc.) are held in the Spec DB 12 as information obtained by instantiating each Spec class. Specifically, the following Spec classes are defined.

"Spec name: meaning" in the logical layer is as follows.
・TL Spec (Topological Link Specification): Defines unique attributes for each TL ・NFD Spec (Network Forwarding Domain Specification): Defines unique attributes for each NFD ・TPE Spec (Termination Point Encapsulation Specification): Defines unique attributes for each TPE Define attributes ・NC Spec (Network Connection Specification): Define attributes unique to each NC ・LC Spec (Link Connect Specification): Define attributes unique to each LC ・XC Spec (Cross(X) Connect Specification): XC Define unique attributes for each

Next, we will explain how to use the Spec class and Entity class (classes that define attribute values). FIG. 37 is a diagram showing an example of how the Spec and Entity classes are used by the failure impact grasping system according to the sixth embodiment of the present invention.
As shown in FIG. 37, attributes common to layers and their values are held in the Entity DB 13 as information obtained by instantiating the Entity class (see FIGS. 4 to 12, for example). One Specification class of the Spec class is associated with n SpecCharacteristic classes and n Entity classes. The SpecCharacteristic class contains name, valueFrom, valueTo, and Type described below. Entity class contains "status: String", "position(int, int)". One Entity class corresponds to n CharacteristicValue classes (an external class of the Entity class, a class that stores a concrete characteristic that actualizes one of the characteristics specified in the SpecCharacteristic class). Attached. The CharacteristicValue class includes CharacteristicName and Value, which will be described later.

The layer-specific attribute name is held in the Spec DB 12 as information obtained by instantiating the SpecCharacteristic class (external class of the Specification class) (see FIGS. 35 and 36, for example).

A layer-specific attribute value is held in the Spec DB 12 as information obtained by instantiating the CharacteristicValue class. Attribute names are defined in the SpecCharacteristic class.

Next, the schemas of Spec DB and Entity DB are explained. FIG. 38 is a diagram showing, in tabular form, an example of a schema of a Specification table of equipment information defined by the failure impact grasping system according to the sixth embodiment of the present invention.
The schema (column name: type) of the Specification table held in the Spec DB 12 is as follows (see SpecCharacteristic in FIG. 37).
・Name: String
・ValueFrom: int
・ValueTo: int
・Type: String

FIG. 39 is a diagram showing, in tabular form, an example of a schema of an Entity table of facility information defined by the failure impact assessment system according to the sixth embodiment of the present invention.
The schema (column name: type) of the Entity table held in the Entity DB 13 is as follows (see CharacteristicValue in FIG. 37). CharacteristicName is the name of the corresponding SpecCharacteristic class.
・Characteristic Name: String
・Value (concrete value): String

Next, how to register the Spec will be explained.
(1) The equipment information Spec shown in FIGS. 35 and 36 is created as a table in the Spec DB 12 in the form of the Specification and SpecCharacteristic shown in FIG. For example, in the PS Spec shown in FIG. 35, the SpecCharacteristic table shown in FIG. 37 is managed as a plurality of tables with foreign keys. This SpecCharacteristic table has 4 attributes (Fig. 37).

(2) Attributes required to store a value unique to the logical layer in the Spec DB 12 are set in the name attribute of SpecCharacteristic (see FIG. 37).
(3) The type for which this name attribute is set is set to the type attribute of SpecCharacteristic (see FIG. 37).

(4) If the logic layer requires a precondition for setting a value in the attribute required to store a unique value in the Spec DB 12, this condition is specified in the valueFrom, valueTo attributes of SpecCharacteristic (see FIG. 37). set.

Next, how to register Entity will be explained.
(1) Entity attributes shown in FIGS. 4 to 12 are created in the Entity DB 13 as tables. For example, for PD, PP, and PS entities (see FIGS. 4 to 6), a table is created with a schema consisting of two attributes, state and coordinates.
(2) Values common to the logical layer are stored in corresponding table records in the Entity DB 13 .

(3) Attributes required to store unique values in the logical layer are the attribute name set in the name attribute of SpecCharacteristic of the corresponding Spec, set in the CharacteristicName attribute of CharacteristicValue, and its value in the value attribute of CharacteristicValue It is set (see FIG. 37).

(Seventh embodiment)
Next, a seventh embodiment will be described. In this seventh embodiment, the input of the location of failure and the like will be described.
First, a description will be given of the input of the failure location (correspondence between use cases and functional units. FIG. 40 is a diagram showing an example of a configuration that functions with the input of the failure location in the failure impact grasping system according to the seventh embodiment of the present invention. is.
As shown in FIG. 40, the facility information registration unit 11 and the entity DB 13 function in inputting the location of failure (see FIG. 32).

Next, the processing of the failure location Entity acquisition unit 14 will be described.
(1) The failure location entity acquisition unit 14 can specify the failure location, for example, according to the user's operation of an input device such as a keyboard or mouse from the display screen of the network configuration.
(2) A drawing object corresponding to the location of the failure is specified among the drawing objects of the building, cable, or device on the display screen.
(3) The failure location entity acquisition unit 14 acquires the name of the entity from the drawing object at the specified failure location.
(4) The failure location entity acquisition unit 14 accesses the entity DB 13 with the name of the acquired entity and acquires the entity that is the failure location.

(Eighth embodiment)
Next, an eighth embodiment will be described. In this eighth embodiment, display of the range of influence will be described.
First, the method of displaying the scope of influence (correspondence between use cases and functional units) will be described. FIG. 41 is a diagram showing an example of a configuration that functions to display the extent of influence in the failure influence grasping system according to the eighth embodiment of the present invention.
As shown in FIG. 41, the Spec DB (database) 12, Entity DB 13, NW influence range calculation unit 15, and NW configuration display unit 16 function in displaying the influence range (NW configuration) (see FIG. 32).

Next, a sequence for displaying the range of influence will be described. FIG. 42 is a sequence diagram showing an example of the processing procedure for displaying the extent of influence by the failure influence grasping system according to the eighth embodiment of the present invention.
First, when the operator designates a failure location on the NW configuration display screen, the NW configuration display unit 16 searches the Entity DB 13 via the failure location entity acquisition unit 14 for the Entity ID corresponding to the failure location. This Entity ID is returned to the NW configuration display unit 16 as a fault location Entity ID.

The NW configuration display unit 16 instructs the NW impact range calculation unit 15 to acquire the impact range Entity ID indicating the range of impact of the failure indicated by the failure location Entity ID. Then, the NW influence scope calculation unit 15 searches the influence scope Entity ID from the Entity DB 13 . An array of the searched influence range Entity IDs is returned to the NW configuration display unit 16 .

Next, the NW configuration display unit 16 acquires all Entities from the Entity DB 13 . The NW configuration display unit 16 acquires the Entity including the acquired influence range Entity ID from the Entity DB 13 as an influence range Entity file. The NW configuration display unit 16 acquires Spec information corresponding to all Entities from the Spec DB 12 as a Spec array. Each result obtained by the NW configuration display unit 16 is displayed on the NW influence display screen and is grasped by the operator.

Next, processing by the NW influence range calculation unit 15 will be described. FIG. 43 is a flow chart showing an example of a processing procedure by the NW influence range calculator 15 of the failure influence grasping system according to the eighth embodiment of the present invention.
First, the NW influence range calculation unit 15 acquires the failure location Entity ID from the Entity DB 13 (S11), and acquires the physical layer Entity from the Entity DB 13 (S12).

The NW impact range calculation unit 15 recognizes the failure location indicated by the failure location Entity ID (S13). When this fault location is a location indicating building collapse or total power depletion in the building (total power depletion), the NW influence range calculation unit 15 sets the states of PD and PP in the building to NG (failure). (S14), the states of NFD and TPE of the Logical Device layer corresponding to PD are set to NG (S15).

Further, when the failure location is a location indicating cable cut or corrosion, the NW influence range calculation unit 15 sets the state of the PL to NG (S16), and sets the state of the PC included in the PL to NG ( S17), the state of the PP connected to the PC is set to NG (S18), and the states of TPE and TL of the Logical Device layer corresponding to the PP are set to NG (S19).

Further, when the failure location indicates a device failure, the NW influence range calculation unit 15 sets the states of the PD and PP to NG (S20), and the NFD and TPE of the Logical Device layer corresponding to the PD. The state is set to NG (S21).

After S15, 19 or 21, the NW influence range calculation unit 15 sets the initial value of N to 1, and under the condition that this N is less than the number of upper layers of the Logical Device layer, All Entities of a layer N+1 are acquired from the Entity DB 13 (S22), and the state of TPE, LC, XC, or NC of the upper layer N+1 corresponding to Layer N is set to NG (S23). After this setting, the NW influence range calculation unit 15 updates N by adding 1, and S22 and S23 are looped until N becomes equal to or greater than the number of upper layers of the Logical Device layer.

Next, the display of the influence range in the NW configuration will be explained. FIG. 44 is a flow chart showing an example of the procedure for displaying the configuration of the physical layer by the NW configuration display unit 16 of the failure impact grasping system according to the eighth embodiment of the present invention.
First, the NW configuration display unit 16 sets the initial value of i to 1, and recognizes the physical layer Entity type under the condition that i is less than the total number of Entities (S31).

When the Entity type is PD Entity, the NW configuration display unit 16 acquires the coordinates defined by the PD Entity (see FIG. 5) from the Entity DB 13 (S32), and draws the device at the position corresponding to these coordinates. Display the object (S33).

When the Entity type is PL Entity, the NW configuration display unit 16 acquires the coordinates of the PCs at both ends of the corresponding PL (corresponding to the coordinates of the PP defined by the PP Entity (see FIG. 6)) from the Entity DB 13. (S34), and a line drawing object is displayed between these coordinates (S35).

When the Entity type is PP Entity, the NW configuration display unit 16 acquires the coordinates defined by the PP Entity (see FIG. 6) from the Entity DB 13 (S36), and draws the port at the position corresponding to these coordinates. Display the object (S37).

After S33, 35 or S37, the NW configuration display unit 16 performs display processing of information unique to the layer (S38). Details of S38 will be described later. After the process of S38, the NW configuration display unit 16 updates i by adding 1, and S31 to S38 are looped until this i becomes the number of all entities. Drawing based on object coordinate information is also described in Non-Patent Document 1 or Japanese Patent Application No. 2018-034981.

Next, display of layer-specific information will be described. FIG. 45 is a flow chart showing an example of a procedure for displaying layer-specific information by the NW configuration display unit 16 of the failure influence grasping system according to the eighth embodiment of the present invention.
First, the NW configuration display unit 16 stores the Entity type of CharacteristicValue in variable t, stores the CharacteristicName attribute of CharacteristicValue in variable n, and stores the value attribute of CharacteristicValue in variable v (S38a).

The NW configuration display unit 16 acquires the instance (sc) of the SpecCharacteristic table corresponding to t from the Spec DB 12 (S38b).
The NW configuration display unit 16 takes out one record from sc and stores it in the variable r (S38c).

The NW configuration display unit 16 starts a loop of r!=NULL and displays "n (attribute name): value (v)" as a character string on the display screen (S38d). The NW configuration display unit 16 takes out one record from sc, stores it in the variable r, and returns to the top of the loop.

Next, display of the configuration of the logical layers will be described. FIG. 46 is a flow chart showing an example of the procedure for displaying the configuration of the logical layer by the NW configuration display unit 16 of the failure impact grasping system according to the eighth embodiment of the present invention.
First, the NW configuration display unit 16 sets the initial value of i to 1, and recognizes the type of entity in the logical layer under the condition that i is less than the number of all entities (S41).

When the Entity type is TPE Entity, the NW configuration display unit 16 acquires the coordinates defined by the TPE Entity (see FIG. 11) from the Entity DB 13 (S42), and recognizes the state defined by this TPE Entity. (S43).

When this state is set to NG by the NW influence range calculation unit 15, the NW configuration display unit 16 displays the point corresponding to the acquired coordinates in red (S44). , the NW configuration display unit 16 displays the points corresponding to the acquired coordinates in black (S45).

When the Entity type is other than TPE Entity, the NW configuration display unit 16 acquires all TPEs from the point object array defined in the Entity DB 13 (S46), and determines whether or not this TPE has a CharacteristicValue attribute. is recognized (S47).
When this attribute is present, the NW configuration display unit 16 performs the layer-specific information display process (see FIG. 45) (S48).

After S48, or when there is no attribute of CharacteristicValue, the NW configuration display unit 16 performs display processing other than TPE Entity (S49). Display processing other than TPE Entity will be described later.

Next, display other than TPE will be described. FIGS. 47A and 47B are flowcharts showing an example of procedures for displaying other than TPE by the NW configuration display unit 16 of the system for grasping the effects of failure according to the eighth embodiment of the present invention.
First, the NW configuration display unit 16 starts a loop of "execute until the element of the point object array becomes empty" and acquires the coordinates of two points (TPE1, TPE2) from the point object array defined by the entity DB 13. (S49a), and a line drawing object is added between the obtained TPE1 and TPE2 (S49b).

The NW configuration display unit 16 recognizes the type of Entity between TPE1 and TPE2 obtained above from the Entity DB 13 (S49c).
When the type of Entity is TL or LC, the NW configuration display unit 16 recognizes the state defined by this Entity (S49d).
When this state is set to not NG by the NW influence range calculation unit 15, the NW configuration display unit 16 adds a non-red line, for example, a black line drawing object between the points of TPE1 and TPE2 ( S49e), when it is set to NG, the NW configuration display unit 16 adds a drawing object with a red line between the points TPE1 and TPE2 (S49f).

When the type of Entity is XC, the NW configuration display unit 16 recognizes the state defined by this Entity (S49g).
When this state is set to not NG by the NW influence range calculation unit 15, the NW configuration display unit 16 draws a non-red double line, for example, a black double line between the points TPE1 and TPE2. Add an object (S49h), and when it is set to NG, the NW configuration display unit 16 adds a drawing object with a red double line between the points TPE1 and TPE2 (S49i).

When the type of Entity is NFD, the NW configuration display unit 16 recognizes the state defined by this Entity (S49j).
When this state is set to not NG by the NW influence range calculation unit 15, the NW configuration display unit 16 adds a non-red ellipse, for example, a black ellipse drawing object between the points of TPE1 and TPE2. (S49k) When it is set to NG, the NW configuration display unit 16 adds a red elliptical drawing object between the points TPE1 and TPE2 (S49l).

When the Entity type is NC, the NW configuration display unit 16 recognizes the state defined by this Entity (S49m).
When this state is set to not NG by the NW influence range calculation unit 15, the NW configuration display unit 16 adds a non-red line, for example, a black line drawing object between the points of TPE1 and TPE2 ( S49n), when it is set to NG, the NW configuration display unit 16 adds a drawing object with a red line between the points TPE1 and TPE2 (S49o).
After S49n or S49o, the NW configuration display unit 16 acquires the service subscriber information attribute value from the Entity DB 13 and displays it as a character string (S49p).

Next, I will explain supplementary information about the display coordinates of Entity.
The display coordinates of the Entity object were explained as a 2D coordinate system, but it is not limited to this, it is also possible to design the coordinate axes with Spec for each layer, and it is also possible to design a 3D coordinate system.

When designing coordinate axes in Spec for each layer, it can be achieved by adding unique coordinate attributes in the SpecCharacteristic class of the Spec class and adding attribute names in the CharacteristicValue class of the Entity.

Next, effects produced by one embodiment of the present invention will be described.
In one embodiment of the present invention, devices and media in the physical layer are managed as device and medium objects, communication end points in the logical layer are managed as point objects, and communications connecting between point objects are managed as line or plane objects. , manages the entire communication between logical layers as a communication object.

Point objects have attributes that refer to corresponding physical layer device and media objects. In addition, point objects have attributes that refer to point objects in layers below that logical layer.
The setting of the location of failure is realized by setting a value indicating a failure in the attribute of the physical layer device and medium object.

The search for the range of influence of failure is realized by searching for objects in the logical layer corresponding to the object set at the failure location, and by searching for line objects, plane objects, and communication objects that include the object.
A communication object in which a failure has occurred stores service user information that uses the communication of that logical layer.
As described above, in one embodiment of the present invention, it is possible to specify the influence range of the logical layer used by the communication service, and to grasp the information of the affected service users.

It should be noted that the present invention is not limited to the above-described embodiments, and can be variously modified in the implementation stage without departing from the gist of the present invention. Further, each embodiment may be implemented in combination as appropriate, in which case the combined effect can be obtained. Furthermore, various inventions are included in the above embodiments, and various inventions can be extracted by combinations selected from a plurality of disclosed constituent elements. For example, even if some constituent elements are deleted from all the constituent elements shown in the embodiments, if the problem can be solved and effects can be obtained, the configuration in which these constituent elements are deleted can be extracted as an invention.

Further, the method described in each embodiment can be executed by a computer (computer) as a program (software means), such as a magnetic disk (floppy (registered trademark) disk, hard disk, etc.), an optical disk (CD-ROM, DVD, MO, etc.), semiconductor memory (ROM, RAM, flash memory, etc.), or the like, or can be transmitted and distributed via a communication medium. The programs stored on the medium also include a setting program for configuring software means (including not only execution programs but also tables and data structures) to be executed by the computer. A computer that realizes this device reads a program recorded on a recording medium, and optionally constructs software means by a setting program, and executes the above-described processing by controlling the operation by this software means. The term "recording medium" as used herein is not limited to those for distribution, and includes storage media such as magnetic disks, semiconductor memories, etc. provided in computers or devices connected via a network.

11...equipment information registration unit, 12...Spec DB (database), 13...Entity DB, 14...failure location entity acquisition unit, 15...NW influence range calculation unit, 16...NW configuration display unit.

Claims (8)

an acquisition means for acquiring an information object relating to a failure occurrence location in a physical layer of a network configuration from a storage device storing information indicating a correspondence relationship between an information object relating to the physical layer of the network configuration and an information object relating to the logical layer ;
a specifying means for specifying, as a failure impact range, an information object associated with the information object relating to the fault occurrence location acquired by the acquiring means, from among the information objects relating to the logical layer stored in the storage device ;
an output means for outputting information indicating the failure affected range identified by the identification means;
with
The information object about the logical layer includes an information object about the logical layer of the upper hierarchy and an information object about the logical layer of the lower hierarchy,
The storage device includes
Correspondence relationship between an information object related to the physical layer and an information object related to the logical layer of the lower layer which is a layer higher than the physical layer, and an information object related to the logical layer of the lower layer and the logic of the higher layer Information indicating the correspondence with the information object about the layer is stored,
The specifying means is
an information object related to the logical layer of the lower hierarchy, which is associated with the information object related to the fault occurrence location acquired by the acquisition means, among the information objects related to the logical layer of each layer stored in the storage device; and identifying an information object related to the logical layer of the upper hierarchy, which is associated with the information object related to the logical layer of the lower hierarchy, as the fault impact range;
Network management device. The storage device includes
further storing information about subscribers to services according to the network configuration in association with the information object about the logical layer;
The specifying means is
identifying information about the subscriber associated with the information object about the location of the failure acquired by the acquiring means as information of the subscriber affected by the failure;
The output means is
outputting information of subscribers affected by the failure identified by the identifying means;
The network management device according to claim 1. the physical layer information object includes a port object indicating a communication port attached to a communication device;
The information object related to the logical layer includes a plurality of point objects indicating the origin or termination of communication, and a line or plane object including the point objects,
the correspondence relationship between the physical layer-related information object and the logical layer-related information object includes the correspondence relationship between the port object and the point object;
The network management device according to claim 1. The specifying means is
when the information object related to the failure occurrence location acquired by the acquisition means is the port object, specifying the port object as the failure impact range in the physical layer;
Identifying a point object associated with the identified port object and a line or surface object including the point object as a failure area of influence in the logical layer;
4. The network management device according to claim 3. the physical layer-related information object includes a device object indicating a communication device having the communication port;
The specifying means is
When the information object related to the location of the failure acquired by the acquiring means is the device object, the communication device indicated by the device object and the port object indicating the communication port of the communication device are acquired by the physical device. identified as a fault impact area at the layer,
Identifying a point object associated with the identified port object and a line or surface object including the point object as a failure area of influence in the logical layer;
4. The network management device according to claim 3. the physical layer information object includes a media object indicating a communication cable connectable to the communication port;
The specifying means is
when the information object related to the failure location acquired by the acquiring means is the medium object, a communication cable indicated by the medium object and a port object indicating a communication port connectable to the communication cable, Identify as a failure impact range in the physical layer,
Identifying a point object associated with the identified port object and a line or surface object including the point object as the failure area of influence in the logical layer;
4. The network management device according to claim 3. A network management method performed by a network management device,
By the acquisition means of the network management device, An information object about the location of faults in the physical layer of the network configuration,A storage device storing information indicating a correspondence relationship between an information object relating to the physical layer and an information object relating to the logical layer of the network configurationobtained fromto do and,
By the identification means of the network management device, SaidStorage deviceAmong the information objects related to the logical layer stored in the , an information object associated with the acquired information object related to the failure occurrence location is specified as the failure impact range.to do and,
By the output means of the network management device, outputting information indicating the identified fault impact range;things and,
with
The information object about the logical layer includes an information object about the logical layer of the upper hierarchy and an information object about the logical layer of the lower hierarchy,
The storage device includes
Correspondence relationship between an information object related to the physical layer and an information object related to the logical layer of the lower layer that is a layer higher than the physical layer, and an information object related to the logical layer of the lower layer and the logic of the higher layer Information indicating the correspondence with the information object about the layer is stored,
The identifying
an information object relating to the logical layer of the lower hierarchy, which is associated with the acquired information object relating to the fault occurrence location, among the information objects relating to the logical layer of each layer stored in the storage device, and the lower hierarchy; identifying an information object related to the logical layer of the higher hierarchy, which is associated with the information object related to the logical layer of the hierarchy, as the fault impact range;
Network management method. A network management processing program that causes a processor to function as each means of the network management device according to any one of claims 1 to 6.

Images