Network management device, method and program

The network management device efficiently calculates communication failure impacts and prioritizes buildings for recovery, addressing the challenge of lengthy processing times in existing methods by rapidly identifying recovery targets.

JP7750432B2Active Publication Date: 2025-10-07NIPPON TELEGRAPH & TELEPHONE CORP
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2024562409
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2022-12-05
Publication Date
2025-10-07
Estimated Expiration
2042-12-05

AI Technical Summary

Technical Problem

Existing methods require extensive processing time to evaluate the impact of communication failures across all possible building combinations during a disaster, making it difficult to quickly determine a fuel delivery plan for telecommunications buildings.

Method used

A network management device that calculates the impact of communication failures and prioritizes buildings for recovery by evaluating the ripple effect on the network topology, allowing for rapid identification of target buildings for fuel delivery.

Benefits of technology

Enables quick identification of recovery targets, reducing processing time and eliminating the need for advanced skills in creating deployment plans, thereby minimizing communication outages.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007750432000001
    Figure 0007750432000001
  • Figure 0007750432000002
    Figure 0007750432000002
  • Figure 0007750432000003
    Figure 0007750432000003
Patent Text Reader

Abstract

A network management device according to one embodiment of the present invention comprises: a failure influence calculation unit that calculates, for each of a plurality of buildings accommodating a communication facility and corresponding to an upper layer of a network, influence of a failure in communication which is at the time of application of such a condition that a failure occurs to the communication of one building of the plurality of buildings and which includes influence of the occurred failure and influence of this failure on other buildings corresponding to a lower layer in the network; and a priority calculation unit that uses the influence calculated by the failure influence calculation unit to calculate priority at the time of application of such a condition that the failure has occurred in the communication of a plurality of buildings corresponding to the upper layer, for each combination of the plurality of buildings having the failure, the priority relating to a candidate building which is among the plurality of buildings and the failure of which is to be recovered.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] FIELD Embodiments of the present invention relate to a network management device, method, and program. [Background technology]

[0002] In a building (sometimes called a communications building) that houses communications equipment and provides communications to the outside world, if communications within the building are cut off due to a disaster such as an earthquake or typhoon cutting off the power supply from a power plant, communications can be resumed by restoring power by operating a fuel-powered emergency generator installed within the building.

[0003] If the emergency generators operate for a long period of time and the fuel stored in the building runs out, the operation of the emergency generators will stop, and the power supply will be cut off again, cutting off communications. Therefore, telecommunications carriers deliver and supply fuel to the telecommunications buildings by vehicle or the like.

[0004] Telecommunications operators need to quickly resume providing communications services by delivering fuel to telecommunications buildings before they run out of fuel, or by using fuel delivery vehicles to quickly deliver fuel to telecommunications buildings that have run out of fuel.

[0005] In order to minimize the impact of communication outages under conditions of limited fuel resources, telecommunications operators need to quickly select relief buildings to which fuel will be delivered from among the many telecommunications buildings that have lost power and are running out of fuel.

[0006] The buildings to be rescued must be selected based on various factors, such as the damaged building, the impact on communication network services from the building, location, fuel situation, and traffic conditions, and manual review requires a great deal of time and advanced skills.

[0007] Responding to disasters requires urgency, they occur infrequently, and it is difficult to train skilled personnel. Therefore, there is a need for technology that can select buildings to be rescued based on the situation at the time of a disaster and automatically and quickly determine a fuel delivery plan for these buildings.

[0008] For example, a technology has been disclosed that requires network configuration information and fault impact information, and based on this fault impact information, the buildings that should be prioritized for rescue can be evaluated and the above-mentioned delivery plan can be determined (see, for example, non-patent documents 1 and 2).

[0009] Furthermore, since the ripple effects differ depending on the combination of buildings that experience failures during a disaster, it is possible to evaluate the impact on services and calculate a deployment plan for all possible combinations of buildings, using weights (policies) for each impact item based on information about buildings that have lost power and social information. [Prior art documents] [Non-patent literature]

[0010] [Non-Patent Document 1] Hiroaki Matsubayashi, Masataka Sato, Kenji Murase, Shunsuke Kanai, Kazuaki Akashi, Shohei Nishikawa, Manami Ogawa, and Kenichi Tayama, "A Study on Relief Building Priority Considering the Network Topology," Institute of Electronics, Information and Communication Engineers [Non-patent document 2] Masataka Sato, Shohei Nishikawa, Kimihiko Fukami, Kenji Murase, and Kenichi Tayama, "Service Impact Assessment Technology Using a Unified Management Model Independent of Network Type," NTT Technical Journal, Internet <URL: https: / / journal.ntt.co.jp / wp-content / uploads / 2020 / 07 / JN20200851.pdf> Summary of the Invention [Problem to be solved by the invention]

[0011] As described above, when evaluating the service impact for all possible combinations of buildings where a failure occurs and creating a delivery plan, the processing time required is the time required to calculate the service impact for each combination multiplied by the number of building combinations, and the processing time becomes enormous depending on the number of building combinations.

[0012] This invention has been made in light of the above circumstances, and its purpose is to provide a network management device, method, and program that, when a communication failure occurs in a network configuration, makes it possible to identify the target for recovery from the failure in an appropriate processing time. [Means for solving the problem]

[0013] A network management device according to one embodiment of the present invention comprises a failure impact calculation unit that calculates the impact of a communication failure, including the failure that occurs and the impact of the failure on other buildings corresponding to lower levels of the network, when a condition is applied in which a communication failure occurs in one of a plurality of buildings that accommodates communication equipment and corresponds to a higher level of the network, for each of the buildings corresponding to the higher level; and a priority calculation unit that calculates, based on the impact calculated by the failure impact calculation unit, the priority of a candidate building from which to restore the failure, for each combination of a plurality of buildings in which the failure occurred, when a condition is applied in which a communication failure occurs in the plurality of buildings corresponding to the higher level.

[0014] A network management method according to one embodiment of the present invention is a method performed by a network management device, and includes the steps of: calculating, for each of a plurality of buildings corresponding to a higher hierarchy of a network that accommodates communication equipment, the impact of a communication failure when a condition is applied in which a communication failure occurs in one of the buildings; the impact of the communication failure including the failure that occurs and the impact of the failure on other buildings corresponding to a lower hierarchy of the network; and calculating, based on the calculated impact, the priority of a candidate building from among the plurality of buildings corresponding to the higher hierarchy that can be used to restore the failure when a condition is applied in which a communication failure occurs in the plurality of buildings. [Effects of the Invention]

[0015] According to the present invention, when a communication failure occurs in a network configuration, it is possible to identify a target for recovery from this failure in an appropriate processing time. [Brief explanation of the drawings]

[0016] [Figure 1] FIG. 1 is a diagram showing an application example of a network management device according to an embodiment of the present invention. [Figure 2] FIG. 2 is a flowchart showing an example of a processing procedure performed by a network management device according to an embodiment of the present invention. [Figure 3] FIG. 3 is a diagram showing an example of a general calculation of the service impact for a combination of buildings in which a failure occurs. [Figure 4] FIG. 4 is a diagram illustrating an example of the functions of the priority calculation unit and the deployment plan processing unit. [Figure 5] FIG. 5 is a diagram illustrating an example of calculation of the priority of a single building. [Figure 6] FIG. 6 is a diagram showing an example of calculation of the priority of a single building in the form of a table. [Figure 7]FIG. 7 is a block diagram showing an example of the hardware configuration of a network management device according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0017] An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a diagram showing an application example of a network management device according to an embodiment of the present invention. As shown in FIG. 1, a network management device 100 according to one embodiment of the present invention includes an input unit 10, a single-building priority calculation unit (failure impact calculation unit) 20, a priority calculation unit (combined priority calculation unit) 30, a deployment plan processing unit 40, and a deployment plan output unit 50.

[0018] FIG. 2 is a flowchart showing an example of a processing procedure performed by the network management device according to an embodiment of the present invention. The input unit 10 inputs failure information indicating a communication failure (sometimes simply referred to as a failure) that has occurred in one of multiple buildings that house communication equipment and form a network configuration, for example, a network redundant configuration, the power supply status related to the recovery of the communication failure that has occurred, and vehicle deployment information related to candidates for vehicles (hereinafter sometimes referred to as recovery work vehicles) that will be used for communication recovery work for the building where the communication failure has occurred (S11). The power supply status is, for example, the status of power supply to the emergency power sources (described later) housed in each building, the time elapsed since the occurrence of a communication failure in each building, etc. The vehicle deployment information is, for example, the current locations of candidate recovery vehicles, the number of recovery vehicles that can move to the building, the types of recovery vehicles, and the amount of fuel for the emergency generators that can be transported and supplied by each recovery vehicle, etc.

[0019] For example, the input unit 10 can input, in S11, the failure information, such as the connection relationship of each building in the redundant network configuration to which communications are provided, the type of emergency power supply in each building, the location of each building, and information indicating the impact when a communication failure occurs in a building, through input operations by an operator, etc.

[0020] Providing communications in a building means, for example, communications between communications devices within the building and communications between communications devices within the building and external communications devices. Examples of the communication failure include a communication interruption caused by a power cutoff to communication equipment in a building, or a communication interruption caused by a failure of communication equipment such as a server or damage to a communication cable. In the following description of this embodiment, a communication interruption caused by a power cutoff to communication equipment in a building will be described as an example.

[0021] The types of emergency power sources in each building include emergency generators that run on fuel and emergency power supply devices that run on rechargeable batteries. An example of an emergency generator is a diesel engine. The building may take other forms as long as it is a facility that provides communications.

[0022] The connection relationships between the buildings may include, for example, information indicating a higher hierarchy (sometimes simply referred to as "upper hierarchy") and a lower hierarchy (sometimes simply referred to as "lower hierarchy") in the network topology. Examples of information indicating the impact of a communication failure include the number of communication users (sometimes referred to as "accommodated users") that can be accommodated in the building where the communication failure occurred, the number of communication devices installed in the building, or the amount of data sent and received by the communication devices installed in the building.

[0023] Furthermore, the input unit 10 can input the traffic conditions in the travel area of ​​each vehicle related to the candidate recovery work vehicle as vehicle deployment information by the above-mentioned input operation, etc. Examples of traffic conditions include information indicating the traffic volume in the travel area, and information indicating whether roads are passable due to construction or disaster, etc.

[0024] The vehicle types in the vehicle deployment information include fuel delivery vehicles and power supply vehicles. The fuel delivery vehicle is a vehicle that carries fuel for the emergency generator when the emergency power source in the building is the above-mentioned emergency generator, and has equipment for filling the emergency generator with this fuel. In addition, the power supply vehicle is a vehicle that has charging equipment for the storage battery when the emergency power source in the building is the emergency power supply device, or a vehicle that carries a replacement storage battery, i.e., a new, charged storage battery, when the storage battery is replaceable.

[0025] Based on the failure information input in S11, the individual building priority calculation unit 20 uses the failure impact calculation function of, for example, NOIM (Network Operation Injected Model) disclosed in the above-mentioned non-patent document 2 to calculate for each building the ripple effect of a communication failure, which is the effect of the communication failure on other buildings in the same network configuration, as well as the communication failure that occurs as a result of, for example, the interruption of power supply to communication equipment housed in a single building in the network configuration (S12).

[0026] For example, based on the information input by the input unit 10, the individual building priority calculation unit 20 can identify multiple lower-level buildings in the network topology that will have their communications cut off due to the impact of a communication failure occurring in multiple higher-level buildings in the network topology among the buildings in the network redundant configuration.

[0027] The individual building priority calculation unit 20 utilizes the network topology to calculate the individual building priority (sometimes referred to as the individual building priority score), which is the magnitude of the impact on communication services, including the magnitude of the communication failure in the individual building, based on the ripple effect of the communication failure in the individual building (S13).

[0028] This individual building priority is determined based on the situation of the communication failure and its impact on other buildings under hypothetical conditions, for example, when a failure in the power supply to the communication equipment housed in that individual building, i.e., a communication failure, occurs.

[0029] In this embodiment, the above-mentioned individual building priority can be calculated by taking into account the ripple effects from the individual building in which the above-mentioned failure occurred, such as ``communication not possible,'' ``communication possible,'' and ``intermediate impact state in which some communications are affected.''

[0030] In this embodiment, the priority of the building to be rescued, which is the target for restoring communication functions, is calculated using the calculation results of the individual building priority described above, instead of the ripple effect under the conditions of the combination of buildings where a communication failure has occurred, such as the absolute value of the number of affected users, thereby significantly reducing the time required to calculate the priority of the building to be rescued.

[0031] In this embodiment, the ripple effect is calculated for each individual building by utilizing the network topology, so that the magnitude of the service impact, including buildings related to the building where the communication failure occurred, can be evaluated without calculating for each possible combination of patrol targets. Even if the number of combination patterns increases, it does not affect the processing time, and advance calculations are also possible.

[0032] In this embodiment, the calculated individual building priority can be calculated simply by superimposing the calculated individual building priority, thereby reducing the processing time. In this embodiment, by using the individual building priority, it is possible to simplify the investigation into the ripple effects of a communication failure after extracting a combination of buildings in which a communication failure has occurred. This reduces the processing time for combinations of buildings to be rescued, and combinations of buildings to be rescued can be extracted in descending order of the individual building priority.

[0033] Next, an example of evaluating the impact of a failure using a general method that does not conform to this embodiment will be described. Since the ripple effect of a communication failure, i.e., the number of users affected by the communication failure, differs depending on the combination of buildings in which the communication failure occurs, it is necessary to calculate the service impact on the entire network for each combination of buildings in which a failure occurs. As the number of target buildings increases, the number of combination patterns increases rapidly, and the total processing time required to calculate the service impact becomes longer.

[0034] FIG. 3 is a diagram showing an example of a general calculation of the service impact for a combination of buildings in which a failure occurs. Figure 3 shows an example in which there are multiple buildings located at a lower level in the network than "Building A" and "Building B," which correspond to higher levels, and which can communicate with both "Building A" and "Building B," as well as a building that can communicate with "Building A."In addition, there are multiple buildings located below "Building C" and "Building D," which can communicate with both "Building C" and "Building D."

[0035] In this example, network redundancy is ensured by multiple buildings equipped with communication equipment, such as "Building A" and "Building B" shown in Figure 3, or "Building C" and "Building D" shown in Figure 3. In such a configuration, even if a communication failure occurs in only one of the redundant buildings, as long as there is no communication failure in the other building, there will be no ripple effect on communication (sometimes called a ripple effect) in the lower-level buildings. On the other hand, if a communication failure occurs in both of the multiple buildings having the above-mentioned redundancy, a ripple effect on communication will occur in lower-level buildings depending on the configuration of the network topology.

[0036] Figure 3 shows, as a first example, an example in which a communication failure occurs in "Building A," "Building B," "Building C," and "Building D," and communication functions are restored for only "Building A" and "Building D" out of these buildings, which have experienced a communication failure, and as a second example, an example in which communication functions are restored for only "Building A" and "Building B" out of "Building A," "Building B," "Building C," and "Building D," which have experienced a communication failure.

[0037] As in the first example, when communication functions are restored by targeting "Building A" and "Building D" as the targets of relief, the total number of users (number of users) affected by the communication failure, including any ripple effects, is calculated to be 280, which is the total capacity (number of users) of "Building B," which was not targeted for relief, which is 200 people, plus the capacity of "Building C," which was also not targeted for relief, which is 80 people. In this example, no ripple effect on communication occurs to the buildings below "Building A" and "Building B" and the buildings below "Building C" and "Building D."

[0038] Furthermore, as in the second example, when communication functions are restored with "Building A" and "Building B" as the targets of recovery, the number of users affected by the communication failure, including any ripple effects, is calculated to be 730, which is the total number of people: "Building C," which was not the target of recovery, with a capacity of 80; "Building D," which was also not the target of recovery, with a capacity of 150; and the total capacity of multiple buildings subordinate to "Building C" and "Building D," which can communicate with both "Building C" and "Building D," with a total capacity of 500. In this example, there is no ripple effect on communication to buildings subordinate to "Building A" and "Building B," but there is a ripple effect on communication to buildings subordinate to "Building C" and "Building D."

[0039] In other words, when a failure occurs in "Building A," "Building B," "Building C," and "Building D" shown in Figure 3, the impact of the failure on the entire network will be less when "Building A" and "Building D" are the targets of relief compared to when "Building A" and "Building B" are the targets of relief.

[0040] FIG. 4 is a diagram illustrating an example of the functions of the priority calculation unit and the deployment plan processing unit. The priority calculation unit 30 calculates the priority of recovery from the communication failure for each combination of buildings where the communication failure has occurred, based on the individual building priority of each building where the communication failure has occurred (S14).

[0041] In the example shown in FIG. 4, the buildings in which communication failures have occurred are "Building A," "Building B," "Building C," "Building D," "Building E," and "Building F." Assuming that a communication failure occurs in one of these buildings, the individual building priority, which is the total impact of the failure based on the number of users accommodated in the building where the communication failure occurs and the number of users affected by the communication failure, which is a ripple effect of the communication failure, is calculated by the individual building priority calculation unit 20 as, for example, as shown in Figure 4, "Individual building priority of Building A: 100 people," "Individual building priority of Building B: 80 people," "Individual building priority of Building C: 260 people," "Individual building priority of Building D: 300 people," "Individual building priority of Building E: 205 people," and "Individual building priority of Building F: 275 people."

[0042] The priority calculation unit 30 can then determine the restoration priority for each combination of buildings to be rescued, based on the priority of each individual building. For example, as shown in Fig. 4, the priority calculation unit 30 can determine that the priority for a combination of six buildings, "Building A" through "Building F," is "1220," the priority for a combination of four buildings, "Building C" through "Building F," is "1040," the priority for a combination of five buildings, "Building A" through "Building E," is "945," the priority for a combination of four buildings, "Building A," "Building C," "Building D," and "Building F," is "935," and the priority for a combination of four buildings, "Building A" through "Building D," is "740."

[0043] Among the above combinations, combinations with higher priorities, i.e., combinations with a large number of accommodated users affected by communication failures, are combinations that are highly effective in recovery-related work, and therefore have a high priority for carrying out recovery-related work.

[0044] The deployment plan processing unit 40 determines whether or not to deploy and patrol candidate recovery work vehicles, which are vehicles that will be sent to each building belonging to a building combination pattern related to this priority, in descending order of priority calculated by the priority calculation unit 30, for each pattern of building combinations that form a redundant configuration of the network, based on the location of each building where a communication failure has occurred, the power supply status, and the traffic conditions in the vehicle deployment information, etc., entered in S11, and thereby searches for recovery work vehicles for each building in the pattern according to the priority and a deployment route, which is an appropriate movement route for this vehicle (S15).

[0045] If the result of this determination is that there is a route available for deploying and patrolling a recovery work vehicle (Y in S16), the deployment plan processing unit 40 generates deployment plan information, which is information indicating the recovery work vehicle that will actually be sent to carry out recovery work at the building, as well as the vehicle's travel schedule and travel route. The deployment plan output unit 50 outputs the deployment plan information generated by the deployment plan processing unit 40 by displaying it on a display device (not shown) or the like (S17).

[0046] In this embodiment, an appropriate deployment plan for recovery work vehicles is generated for each combination of buildings that form a redundant network configuration and in which a communication failure has occurred, based on the number of users that can be accommodated when a communication failure occurs in a single building, thereby generating an appropriate deployment plan for recovery work vehicles.

[0047] This makes it possible to automatically and quickly determine a deployment plan that can significantly reduce the time that communication outages occur in a building that is the target of communication restoration, thereby eliminating the need for advanced skills in creating the deployment plan and significantly reducing the time required to create it.

[0048] Next, a specific example of the calculation of the individual building priority will be described. Fig. 5 is a diagram showing an example of the calculation of the individual building priority. Fig. 6 is a diagram showing an example of the calculation of the individual building priority in a table format. Figure 5 shows examples of calculations by the individual building priority calculation unit 20 of the individual building priority when a failure occurs in "Building A," the individual building priority when a failure occurs in "Building B," the individual building priority when a failure occurs in "Building C," and the individual building priority when a failure occurs in "Building D."

[0049] Here, first, when a failure occurs in "Building A," the individual building priority calculation unit 20 calculates "375" as the individual building priority when a failure occurs in "Building A," by adding "200," the number of users accommodated in "Building A," "50," the number of users accommodated in one of the three buildings subordinate to "Building A" that can communicate only with "Building A," i.e., that does not communicate with "Building B," which is redundant with "Building A," and "250," the number of users accommodated in two buildings subordinate to "Building A" and "Building B," which are redundant and can communicate with both "Building A" and "Building B," multiplied by "0.5," a coefficient for converting to the number of users affected by a failure occurring in "Building A," to the sum of these, and the number of users obtained by "125."

[0050] Secondly, when a failure occurs in "Building B," the individual building priority calculation unit 20 calculates "325" as the individual building priority when a failure occurs in "Building B," by adding "200," the number of users accommodated in "Building B," and "250," the number of users accommodated in the two redundant buildings subordinate to "Building A" and "Building B" that can communicate with both "Building A" and "Building B," to "125," which is obtained by multiplying this by "0.5," a coefficient for converting to the number of users affected by a failure occurring in "Building B."

[0051] Third, when a failure occurs in "Building C," the individual building priority calculation unit 20 calculates "330" as the individual building priority when a failure occurs in "Building C," calculated by adding "80," the number of users accommodated in "Building C," and "500," the number of users accommodated in the two buildings subordinate to "Building C" and "Building D" that are redundant and can communicate with both "Building C" and "Building D," to the number of users obtained by multiplying this by "0.5," a coefficient for converting to the number of users affected by a failure occurring in "Building C," to obtain "250."

[0052] Fourth, when a failure occurs in "Building D," the individual building priority calculation unit 20 calculates "400" as the individual building priority when a failure occurs in "Building D," by adding "250," which is the number of users that "Building D" can accommodate ("150"), and "Building C," which is redundant, and "Building D," which is the number of users that "500" can accommodate in two buildings that are subordinate to "Building D" and can communicate with both "Building C" and "Building D," multiplied by "0.5," a coefficient for converting to the number of users that will be affected by a failure that occurs in "Building D."

[0053] As a result of these calculations, the individual building priority for "Building D" is highest, followed by the individual building priority for "Building A," the individual building priority for "Building C," and the individual building priority for "Building B." Therefore, when one building is the subject of relief, the relief priority will be in the following order: "Building D," "Building A," "Building C," and "Building B."

[0054] When multiple buildings, in this case two buildings, are the subject of relief, for example, the priority for the combination of "Building A" and "Building B" is "700", which is the sum of the individual building priority for "Building A" and the individual building priority for "Building B", and the priority for the combination of "Building A" and "Building D" is "775", which is the sum of the individual building priority for "Building A" and the individual building priority for "Building D". Comparing these, it is clear that targeting relief for the combination of "Building A" and "Building D", which has the higher priority, will reduce the impact of the disruption after relief.

[0055] FIG. 7 is a block diagram showing an example of the hardware configuration of a network management device according to an embodiment of the present invention. 7, the network management device 100 according to the above embodiment is configured, for example, by a server computer or a personal computer, and has a hardware processor 111A such as a CPU. 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.

[0056] The communication interface 114 includes, for example, one or more wireless communication interface units, and enables transmission and reception of information to and from the communication network NW. As the wireless interface, for example, an interface that adopts a low-power wireless data communication standard such as a wireless LAN (Local Area Network) is used.

[0057] An input device 200 and an output device 300 that are attached to the network management device 100 and used by users or the like are connected to the input / output interface 113 . The input / output interface 113 can take in operation data input by a user or the like via an input device 200 such as a keyboard, touch panel, touchpad, or mouse, and can also process output data to be displayed on an output device 300 including a display device using a liquid crystal or organic electroluminescence (EL) display. Note that the input device 200 and the output device 300 may be devices built into the network management device 100, or may be input devices and output devices of other information terminals that can communicate with the network management device 100 via the network NW.

[0058] The program memory 111B is a non-transitory tangible storage medium that is a combination of a non-volatile memory that can be written to and read from at any time, such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive), and a non-volatile memory such as a ROM (Read Only Memory), and can store programs required to execute various control processes, etc., according to one embodiment.

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

[0060] A network management device 100 according to an embodiment of the present invention can be configured as a data processing device having the units shown in FIG. 1 as software-based processing function units.

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

[0062] The processing function units in each of the above units can be realized by reading and executing a program stored in the program memory 111B by the hardware processor 111A. Note that some or all of these processing function units may be realized in various other forms, including integrated circuits such as an application specific integrated circuit (ASIC) or a field-programmable gate array (FPGA).

[0063] The methods described in each embodiment may be stored as a program (software means) that can be executed by a computer on a recording medium such as a magnetic disk (e.g., a floppy disk, a hard disk, etc.), an optical disk (e.g., a CD-ROM, a DVD, an MO, etc.), or a semiconductor memory (e.g., a ROM, a RAM, a flash memory, etc.), or may be transmitted and distributed via a communication medium. The program stored on the medium also includes a configuration program that configures the software means (including not only execution programs but also tables and data structures) that the computer executes. The computer that realizes this device reads the program stored on the recording medium and, in some cases, configures the software means using the configuration program, and executes the above-described processing by having the operation controlled by this software means. The term "recording medium" as used herein is not limited to a storage medium for distribution, but also includes a storage medium such as a magnetic disk or semiconductor memory installed inside the computer or in a device connected via a network.

[0064] The methods described in each embodiment may be stored as a program (software means) that can be executed by a computer on a recording medium such as a magnetic disk (e.g., a floppy disk, a hard disk, etc.), an optical disk (e.g., a CD-ROM, a DVD, an MO, etc.), or a semiconductor memory (e.g., a ROM, a RAM, a flash memory, etc.), or may be transmitted and distributed via a communication medium. The program stored on the medium also includes a configuration program that configures the software means (including not only execution programs but also tables and data structures) that the computer executes. The computer that realizes this device reads the program stored on the recording medium and, in some cases, configures the software means using the configuration program, and executes the above-described processing by having the operation controlled by this software means. The term "recording medium" as used herein is not limited to a storage medium for distribution, but also includes a storage medium such as a magnetic disk or semiconductor memory installed inside the computer or in a device connected via a network.

[0065] The present invention is not limited to the above-described embodiments, and various modifications can be made in the implementation stage without departing from the spirit of the invention. Furthermore, the embodiments may be implemented in appropriate combinations, in which case the combined effects can be obtained. Furthermore, the above-described embodiments include various inventions, and various inventions can be extracted by combining selected elements from the disclosed elements. For example, if the problem can be solved and the desired effect can be obtained even if some elements are deleted from all elements shown in the embodiments, the configuration from which these elements are deleted can be extracted as an invention. [Explanation of symbols]

[0066] 100...Network management device 10...Input section 20...Single building priority calculation section 30…Priority calculation unit 40...Deployment planning processing unit 50...Deployment plan output section

Claims

1. a failure impact calculation unit that, when a condition is applied in which a failure occurs in communication in one of a plurality of buildings that accommodate communication facilities and correspond to an upper layer of a network, calculates the impact of the failure on the communication, including the failure that has occurred and the impact of the failure on other buildings that correspond to a lower layer of the network, for each of the buildings that correspond to the upper layer; a priority calculation unit that calculates, based on the impact calculated by the failure impact calculation unit, a priority of a candidate building from which the failure is to be restored among the plurality of buildings corresponding to the upper hierarchy when a condition in which a failure has occurred in communication in the plurality of buildings is applied, for each combination of the plurality of buildings in which the failure has occurred; A network management device comprising:

2. The failure impact calculation unit Calculating the impact of the communication failure, including the impact of the failure on buildings that correspond to the higher hierarchy and are capable of communicating with other buildings that correspond to the higher hierarchy and are capable of communicating with the building in which the failure occurred, for each building that corresponds to the higher hierarchy. The network management device according to claim 1 .

3. The failure impact calculation unit Calculating the impact of the communication failure for each building corresponding to the upper hierarchy, including the failure that has occurred, the impact of the failure on buildings that correspond to the lower hierarchy of the network and do not communicate with the other buildings in the upper hierarchy, and the impact of the failure on buildings that correspond to the lower hierarchy of the network and are able to communicate with the other buildings in the upper hierarchy; The network management device according to claim 2 .

4. a planning processing unit that plans a restoration work for the failure that has occurred based on conditions related to the restoration work for the building that corresponds to the priority calculated by the priority calculation unit; The network management device according to claim 1 .

5. The failure impact calculation unit When a condition that the failure occurs due to a power outage to communication equipment housed in one of the buildings corresponding to the upper level is applied, the impact of the communication failure, including the failure that occurred and the impact of the failure on other buildings corresponding to the lower level, is calculated for each building corresponding to the upper level; The priority calculation unit calculates, for each combination of the plurality of buildings in which the failure has occurred, a priority of a candidate building to which the power supply should be restored, among the plurality of buildings corresponding to the upper hierarchy, when a condition in which the power supply to the communication equipment housed in the plurality of buildings has been stopped is applied, based on the impact calculated by the failure impact calculation unit; The network management device according to claim 1 .

6. The planning processing unit giving priority to buildings with high priorities calculated by the priority calculation unit, and planning information indicating vehicles to be actually deployed to the buildings and travel routes of the vehicles to the buildings based on information related to the failures in the buildings and information related to candidates for vehicles to be deployed for work to restore the buildings from the failures; The network management device according to claim 4.

7. 1. A method performed by a network management device, comprising: When a condition is applied in which a failure occurs in communication in one of a plurality of buildings that accommodate communication facilities and correspond to a higher layer of a network, calculating the impact of the failure on communication, including the failure that has occurred and the impact of the failure on other buildings that correspond to a lower layer of the network, for each of the buildings that correspond to the higher layer; calculating, based on the calculated influence, a priority of a candidate building from which the failure is to be restored among the plurality of buildings corresponding to the upper hierarchy when a condition in which a failure has occurred in communication in the plurality of buildings corresponding to the upper hierarchy is applied, for each combination of the plurality of buildings in which the failure has occurred; A network management method comprising:

8. A network management processing program that causes a processor to function as each of the units of the network management device according to any one of claims 1 to 6.

Citation Information

Patent Citations

  • Network monitoring system and network monitoring method

    JP2013030826A

  • Preferentially-restored facility determination device, preferentially-restored facility determination method, program, and preferentially-restored facility determination system

    JP2014199993A

  • Service recovery system and service recovery method

    JP2020022022A

  • Network management device, method, and program

    WO2022130475A1