JP2014110620A - Network operation system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a network operation system that can facilitate administration and operation of network component devices even if the network is affected by the large disaster.SOLUTION: A network operation device is deployed redundantly and periodically transmits a diagnostic request message requesting to diagnose to a network component device. The network component device that received the diagnostic request message records the time of receipt and transmits a diagnostic response message containing the time of receipt and the diagnostic result to the network operation device. The time of receipt is recorded for each of diagnostic request messages from network operation devices in all of the redundant systems. A network operation device of a standby system detects whether the time of receipt relating to another network operation device is updated, and if not updated, switches a network component device having recorded that time of receipt to be managed thereby.

Description

  The following embodiment relates to a network operation system.

Since the Great East Japan Earthquake, each carrier that provides information and communication services has been actively considering disaster recovery.
However, in the event of a natural disaster such as this time, damage far beyond assumptions will occur. In disaster recovery, it is considered that the network operation centers are distributed (two bases) and redundantly installed EMS (Element Management System) that manages the operation of each device constituting the communication network providing the information communication service. It is done. However, it is conceivable that a network component device stop at the municipal level or a network stop between operation centers occurs. In that case, the operator who operates the network is forced to operate the network based on the situation after grasping the communication state with several hundred devices connected to the EMS for each EMS of each operation center. It will be.

  In addition, as a main function of the redundant EMS, there is management of setting information of network constituent devices connected under the control and failure information notified from the network constituent devices. Of these, the setting information of the former network configuration equipment needs to be centrally managed in the redundant EMS. Conventionally, the status information of the main system and the subordinate system is managed, and the setting information is centrally managed by the main system. Centralized management is realized by copying the data to the secondary system. Here, the network component device is a repeater or a router.

FIG. 1 is a diagram showing a state of centralized management of setting information for network configuration devices using a conventional EMS redundancy configuration.
In FIG. 1, the network includes network constituent devices # 1 to # 4 and EMSs (network operation devices) 10 and 11 that manage and operate them. The EMS 10 is an operation system, system 1 or main system, and the EMS 10 normally manages and operates all the network component devices # 1 to # 4. The EMS 10 is provided in the main network center. The EMS 11 is a device provided as a standby system, a second system, or a slave system with respect to the EMS 10. The EMS 11 manages and operates the network constituent devices instead of the EMS 10 when the EMS 10 cannot manage and operate the network constituent devices due to some situation. The EMS 11 is provided in the sub network center.

  For example, in FIG. 1, it is assumed that the network between the network component device # 4 and the EMS 10 is disconnected. In this case, the EMS 10 cannot manage / operate the network component device # 4. In this case, a network is provided between the EMS 10 and the EMS 11, and the EMS 11 is notified that the EMS 10 can no longer manage and operate the setting process of the network component device # 4. Then, the EMS 11 accesses the network component device # 4 and performs management / operation processing such as setting processing. The database of network configuration devices held by the EMS 10 and the EMS 11 is consistent in real time, and the EMS 11 can perform an operation in place of the EMS 10 at any time.

FIG. 2 is a diagram illustrating a format of data transmitted / received between the EMS and the network configuration device.
The EMS periodically transmits a message for diagnosing the state of the network to the network constituent devices. (1) in FIG. 2 is a format of a message sent from the EMS to the network component device. “Diagnosis request” is set as the data type, and the addresses of the transmission source and transmission destination, the block serial number of the message, and the number of stored data are set. When receiving the message (1) in FIG. 2 from the EMS, the network component device performs a status diagnosis of the device itself and returns the result to the EMS. (2) in FIG. 2 shows a case where there is a temperature abnormality and a memory parity abnormality. In the return message, “diagnosis response” is set as the data type, and the address of the network component device is set as the transmission source. An EMS address is set. Further, as data, abnormality 1 data indicating that there is a temperature abnormality and abnormality 2 data indicating that there is a memory parity abnormality are added to the message. In the data number field, it is set that data indicating two abnormalities is added as the data number. (3) in FIG. 2 is a format of a return message transmitted from the network device to the EMS when there is no abnormality in the network device. “Diagnosis response” is set as the data type, the address of the network component device is set as the transmission source, and the EMS address is set as the transmission destination.

  Even in the case of the configuration shown in FIG. 1, when a large-scale earthquake such as described above occurs, it is possible that the network between EMS suffers and becomes disconnected. In that case, each EMS is used as a main system, and network configuration devices connected in EMS units are set, and data matching individually set for each EMS after restoration from an earthquake is extremely difficult.

  In the prior art, even when the intersystem communication is disconnected, there are those that enable the duplex devices to be mutually monitored, and those that monitor the connection status of the terminal devices.

Japanese Patent Laid-Open No. 10-242889 JP 2000-324121 A

FIG. 3 is a diagram for explaining a conventional problem.
In FIG. 3, due to the disaster, the network constituent devices # 1 and # 4 cannot communicate with the EMS2 system, and the network constituent devices # 3 and # 4 cannot communicate with the EMS1 system.

  In order to adapt to disaster recovery, even if redundant EMSs are distributed and arranged, if various failures occur due to a catastrophic event beyond the assumption, accurate operation is required for each EMS.

  In response to a disaster, a redundant EMS needs to utilize both EMSs. In that case, it is necessary to determine to which EMS the network component device to be set is taken in for each EMS unit. For this purpose, it is necessary to grasp the connection status between the EMS and the network constituent device in each EMS for each network constituent device connected in units of EMS. In order to avoid the double setting, it is necessary to decide which EMS the setting control is to be performed from, but there are several hundreds connected under the EMS while the event exceeding the assumption has occurred. It is extremely difficult to accurately grasp the connection status of network configuration devices.

  Also, it is necessary to store various EMS information performed on the network components in the operational state by both EMSs, and to ensure consistency when the EMS starts communication with each other after the earthquake recovery. .

  In the following embodiments, a network operation system is provided that can easily manage and operate network components even in the event of a major disaster.

  A network operation system according to an aspect of the following embodiment is a network operation system including a network configuration device that configures a network and a plurality of network operation devices that manage and operate the network configuration device. The first network operation device that periodically transmits a diagnosis request message for requesting acquisition of the status of the network component device, and when receiving the diagnosis request message, obtains the reception time and determines the status of the network component device. The network component device that diagnoses and returns a diagnosis response message including the result of the diagnosis and the reception time to the first network operation device, and periodically transmits the diagnosis request message to the network component device Receiving the diagnostic response message and receiving the diagnostic response It is detected whether the reception time at the network component device of the diagnosis request message from the first network operation device included in the message has been updated. If the reception time has not been updated, the network component device is automatically And a second network operation device that is set to be managed by the network operation device.

  According to the following embodiments, it is possible to provide a network operation system that can easily manage and operate network components even in the event of a major disaster.

It is a figure which shows the mode of the unified management of the setting information to the network configuration apparatus by the redundant structure of the conventional EMS. It is the figure which showed the data format transmitted / received between EMS and a network component apparatus. It is a figure explaining the conventional problem. It is the figure (the 1) which shows the relationship between EMS, a management object network, network component apparatus, and the function of EMS. It is the figure (the 2) which shows the relationship between EMS, a management object network, network component apparatus, and the function of EMS. FIG. 6 is a diagram (part 3) illustrating a relationship between an EMS, a management target network, a network configuration device, and an EMS function; FIG. 14 is a diagram (part 4) illustrating a relationship between an EMS, a management target network, a network configuration device, and an EMS function; FIG. 11 is a diagram (part 5) illustrating a relationship between an EMS, a management target network, a network configuration device, and an EMS function; It is a figure which shows the block block diagram of EMS and a network component apparatus. It is a figure which shows the format of the diagnostic message of a network component apparatus. It is a figure which shows the relationship between the diagnostic sequence and the time stored in the diagnostic response message. It is a flowchart which shows the network component apparatus acquisition process at the time of a disaster. It is a figure which shows the diagnosis result condition according to a affliction condition. It is a figure which shows the EMS operational content at the time of a disaster. It is a figure which shows the recording format of network DB. It is a figure which shows DB matching result at the time of a disaster condition recovery. It is a figure which shows the content of the diagnostic result at the time of other system EMS stop. It is a flowchart which shows operation / standby switching processing of the standby EMS. It is a figure which shows the system configuration | structure at the time of triple EMS. It is a figure which shows the mode at the time of a disaster. It is a figure which shows the diagnosis result condition of each EMS at the time of the affliction of FIG. It is a figure which shows the hardware structural example of EMS. It is a figure which shows the hardware constitutions of a network component apparatus.

  In this embodiment, each EMS periodically requests diagnosis from each network component device. Each network component device requested for diagnosis records and updates the time when the diagnosis request message is received from each EMS, and adds the diagnosis status to the diagnosis response message of each EMS and returns it.

Each EMS can grasp the communication status between the other system EMS and the network component device by checking the diagnosis time of the other system in the received diagnosis response information.
That is, when the diagnosis reception time of the other system EMS is updated, it is determined that the communication between the other system EMS and the network constituent device is normal. Conversely, when the diagnosis reception time of the other EMS has not been updated, it is determined that the communication between the other EMS and the network constituent device is abnormal.

  Even when the network is cut off due to the occurrence of a natural disaster and the EMS is disconnected, the EMS can grasp the communication status with other EMS from the network constituent devices that have been diagnosed. When an EMS of a sub-network center (standby network center) is used as an active system at the time of a disaster, the EMS moves a network component device that is not connected to another system under the control of its own EMS. It is possible to inherit the operation smoothly.

  At the time of disaster recovery, it is necessary to achieve consistency in order to unify the database contents by reflecting the setting contents performed individually for each EMS. In that case, it is possible to coordinate the database contents by linking the setting information that was implemented in the state where communication between the other EMS and the network component device was interrupted at the time of the disaster. Become.

  If the network is severed and communication between EMS is disrupted, and both EMS systems are used and network operation is attempted to be inherited, the network connection status of the network configuration equipment with other systems EMS You can know it through the equipment. Therefore, it is possible to automatically determine which network component device is to be transferred to its own EMS.

  Also, the setting information implemented under this situation is recorded in units of EMS, so that it is possible to achieve mutual alignment when communication between EMSs is restored.

4 to 8 are diagrams illustrating the relationship between the EMS, the management target network and the network constituent devices, and the functions of the EMS.
As shown in FIG. 4, the EMS is made redundant (duplex), and the network constituent devices # 1 to # 4 are connected to the EMSs 10 and 11, respectively.

  On the other hand, the systems between the EMSs 10 and 11 are connected to each other, the mutual operation status of the EMS (active system, standby system) is grasped, the database is matched between the EMSs, and the primary failure of the EMS to network component connection route Configure a detour route.

EMS generally has the following functions.
(1) The connection configuration of the network configuration devices that configure the management target network is managed as network information.
As shown in FIG. 5, the EMS is provided with a network database, and network configuration devices included in the network to be managed and connection relationships between them are registered. The network database of the active EMS and the standby EMS holds the same network information. This information is made the same information by ensuring consistency between the network database of the active system and the standby system EMS.

(2) Manage the connection state between the network components and the EMS.
As shown in FIG. 6, each EMS periodically diagnoses the connection state of each network component device, and stores the result in a diagnosis management database.

(3) Implement various settings in accordance with the network information updated for the network component devices.
As shown in FIG. 7, the operator sets which line should be relayed to each network constituent device via the network configuration management unit of the EMS. This setting is synchronized so that the same information is held in the EMS of both the active system and the standby system.

(4) Collect and notify failures of network components.
As shown in FIG. 8, when a network component device detects a failure or the like, an alarm is notified to the EMS. This alarm is notified to an operator who operates the EMS.

FIG. 9 is a block diagram of the EMS and network configuration equipment.
The active EMS 10 and the standby EMS 11 have the same configuration.
The network configuration management unit 21 performs device setting, alarm monitoring, and network configuration device management for managing the operation of the network configuration device 20. Device setting information and alarm monitoring information are centrally managed by a network database (DB) 22.

  The network component communication function 23 implements transmission / reception of each piece of information executed by the network configuration management unit 21 with the network component 20. The inter-EMS communication function 24 is used to bypass communication information of the network component device communication function 23. Moreover, the apparatus state between EMS is diagnosed using the communication function 24 between EMS.

  The network configuration device setting management unit 25 creates setting information of the network configuration device 20 for the device settings performed by the network configuration management unit 21, and sends the setting information to the network configuration device 20 via the network configuration device communication function 23. To do. Also, the setting result received from the network configuration device 20 is managed and transmitted to the network configuration management unit 21.

  The network component device alarm management unit 26 for managing the abnormality related to the service provided by the operator receives the alarm information of the network component device 20 notified from the network component device communication function 23 and understands it to the operator. The data is converted and transferred to the network configuration management unit 21.

  The network configuration device connection management unit 27 for managing the state of the network configuration device performs diagnosis of the network configuration device 20 via the network configuration device communication function 23, stores the diagnosis result in the diagnosis management DB 28, Generate information necessary for operation during disasters.

  The inter-EMS connection management unit 29 for managing the operation state of the other system EMS monitors the operation state of the other system EMS via the inter-EMS communication function 24.

  In order to match the network device setting information between the EMSs, the inter-EMS DB matching unit 30 performs a matching process of taking the difference of the network configuration device setting information via the inter-EMS communication function 24 and matching the difference.

  The network component device 20 performs device setting, alarm notification, and diagnosis notification via the EMS communication function 31.

  The device setting unit 36 performs its own internal setting based on the setting information received via the EMS communication function 31 during device setting, and returns the implementation result to the EMS via the EMS communication function 31.

  The alarm management unit 32 monitors the failure state of the network component itself, stores the alarm contents in the alarm DB 33 at the time of occurrence and recovery of the alarm, and simultaneously notifies the EMS via the EMS communication function 31 autonomously. .

  The EMS diagnosis management unit 34 stores the diagnosis time in the diagnosis DB 35 with respect to the diagnosis request information periodically received via the EMS communication function 31 and returns the latest diagnosis results of both systems EMS to the EMS.

  The network configuration device communication function 23 of both EMS systems periodically diagnoses the network configuration device 20.

  The EMS diagnosis management unit 34 of the network component device 20 records the reception time in the diagnosis DB 35 when receiving a diagnosis request message periodically transmitted from both EMS systems.

  Moreover, the diagnosis reception time of both EMS systems recorded in the diagnosis DB 35 is added to the response information of the diagnosis result, and the response is returned to the EMSs 10 and 11 that have received the diagnosis request.

FIG. 10 is a diagram illustrating a format of a diagnostic message for network configuration devices.
In FIG. 10, the same information as in FIG. 2 is assigned the same label, and the description thereof is omitted.

  The diagnosis request message (1) from the EMS to the network component device is the same as that in FIG. The diagnostic response message (2) when there is an abnormality adds the time when the diagnostic message was received from the EMS1 system and the time when the diagnostic message was received from the EMS2 system to the message as well as that of FIG. . The diagnosis response message (3) when there is no abnormality is the same as in FIG. 2 except that the reception time of the diagnosis request message from the EMS1 system and the reception time of the diagnosis request message from the EMS2 system are added as data. It is.

  Here, the reception time of the diagnosis request message records the time when the diagnosis request message transmitted periodically (for example, every 30 seconds) is received from the EMS, but this time is updated when normal. Will be. On the other hand, when there is an abnormality and the diagnosis request message cannot be received, this time is not updated and only shows the same value. Therefore, whether or not the connection status between the EMS of the other system and the network configuration apparatus is normal can be determined by checking whether or not the diagnosis reception time of the EMS of the other system is updated.

  The diagnosis DB 35 of the network component device 20 stores the reception time of the diagnosis request message from the active (first system) EMS and the reception time of the diagnosis request message from the standby (second system) EMS. When the diagnostic response message is returned to the EMS, these reception times are read from the diagnostic DB 35 and attached to the message as data.

FIG. 11 is a diagram illustrating the relationship between the diagnostic sequence and the time stored in the diagnostic response message.
In FIG. 11, normally, diagnostic request messages from the active EMS and the standby EMS are periodically transmitted to the network component device # 1, respectively. In returning the diagnostic response message, the network component device # 1 records the time when the diagnostic request message is received, adds it as data to the diagnostic response message, and returns it to the EMS. At that time, the reception time of the diagnosis request message of the EMS of both systems is added to the diagnosis response message. In FIG. 11, for convenience, the transmission time of the diagnosis request message from the EMS is the same as the reception time at the network component device # 1, but this is not always the case. The reception time is later than the transmission time.

  Next, it is assumed that the operational EMS has stopped due to the disaster. Then, the diagnosis request message from the active EMS is not transmitted. However, the diagnosis request message is transmitted from the standby EMS as usual. When the network component device # 1 returns a diagnosis response message to the diagnosis request message from the standby EMS, the network component device # 1 also transmits the reception time of the diagnosis request message of the active EMS. In this case, since the active EMS is stopped, the diagnosis request message is not transmitted. Therefore, in the network component device # 1, the reception time is added to the diagnosis response message to the standby EMS while the reception time of the diagnosis request message from the active EMS is not updated, and the standby EMS Will be returned.

  Therefore, the standby EMS detects that the reception time at the network component device # 1 of the diagnosis request message from the active EMS has not been updated, so that the operation EMS and the network component device # 1 It is detected that some kind of failure has occurred in communication. When the active EMS returns from the stop, the active EMS again sends a diagnosis request message to the network constituent device # 1, so that the network constituent device # 1 has a diagnosis from the active EMS. The reception time of the request message is updated.

  The network configuration device connection management unit 27 of the EMS that has received the diagnostic response message of the network configuration device refers to the diagnosis time of the other EMS stored in the diagnosis response result, and Simultaneously grasp the connection information.

  If the network is disrupted at the time of the disaster, or if the disaster occurs in units of offices, the network operation is continued by using EMS as a mutual operation system. At this time, the EMS that transits from the standby system setting to the active system setting indicates that the network component device is not connected to the EMS of the other system (failure has occurred) based on the previous diagnosis result information. , To be managed under own system EMS.

FIG. 12 is a flowchart showing the network configuration device import processing at the time of disaster.
Here, when the EMS takes in the network constituent device or manages it as a subordinate device, it means that the network constituent device is operated according to the setting of the own EMS.

  When the diagnosis status check is started, in step S10, the other EMS determines whether or not it is in operation. This determines whether or not the other EMS is operating normally by checking whether or not the other EMS is operating normally and whether or not the diagnostic reception time of the other EMS of the diagnostic response message has been updated. Is. If the determination in step S10 is yes, the process ends.

  If the determination in step S10 is No, in step S11, if the number of network configuration devices whose diagnosis time is not updated is n and the total number is m, n / m is calculated. This is compared with an appropriately determined threshold value to determine whether the threshold value is exceeded. This threshold is 1/2 or 1/3. This is because it is considered that many network components will fail at the same time in the event of a disaster due to a major earthquake, etc., so it is determined whether or not there is a disaster. The threshold is set appropriately by the system designer. May be set.

  If the determination in step S11 is No, it is determined that there is no damage, and the process ends without performing the process related to the damage. If the determination in step S11 is Yes, in step S12, the self EMS determines whether or not it is a standby system. If the determination in step S12 is No, the self EMS only needs to operate as before, and the process ends. If the determination in step S12 is Yes, in step S13, it is determined that a disaster has occurred, and the network component device acquisition is started.

  First, in step S14, it is determined whether or not the diagnosis time of another system EMS of one network component device has been updated. If the determination in step S14 is yes, the process proceeds to step S16. When the determination in step S14 is No, in step S15, the network configuration device is set to be managed as a device under its own EMS, and the process proceeds to step S16.

  In step S16, it is determined whether or not all network constituent devices have been processed. If No, the process returns to step S14 to repeat the process. If Yes, the process ends.

FIG. 13 is a diagram illustrating the diagnosis result status according to the disaster status.
In FIG. 13, it is assumed that network constituent devices # 1 and # 4 cannot communicate with the EMS2 system due to a disaster, and network constituent devices # 3 and # 4 cannot communicate with the EMS1 system.

  In the EMS1 system, it is detected that there is no response from the network constituent devices # 3 and # 4. On the other hand, the network component device # 1 cannot communicate with the EMS2 system, but can communicate with the EMS1 system. Therefore, as a diagnosis result of the network component device # 1, it is detected that the diagnosis reception time of the EMS1 system is updated and the diagnosis reception time of the EMS2 system is not updated. Since the network device # 2 has normal communication with the EMSs of both systems, it is detected that the diagnostic reception time of the EMSs of both systems has been updated.

  In the EMS2 system, it is detected that there is no response from the network constituent devices # 1 and # 4. On the other hand, the network component device # 3 cannot communicate with the EMS1 system, but can communicate with the EMS2 system. Therefore, the diagnosis result of the network component device # 3 is detected that the EMS2 system diagnosis reception time is updated and the EMS1 system diagnosis reception time is not updated. Since the network device # 2 has normal communication with the EMSs of both systems, it is detected that the diagnostic reception time of the EMSs of both systems has been updated.

FIG. 14 is a diagram showing the EMS operation contents at the time of disaster.
When the disaster status recovers the network configuration equipment and line settings made in units of EMS, the EMS adds the disaster flag to the settings made at the time of the disaster in order to reflect each other in the network DB. to manage. When the affected state recovers, the contents stored in the affected state flag are reflected in the mutual network DB.

  In FIG. 14, due to a disaster, the connection between the network component devices # 1 and # 4 and the standby EMS is disconnected, and the connection between the network component devices # 3 and # 4 and the active EMS is disconnected. Network component device # 2 is not affected. In that case, the active EMS performs switching setting to the network component device # 1, and passes the customer line via the network component device # 2 before the disaster, via the network component device # 2. Switch to things. The active EMS also sets the network component device # 2 to relay the customer line from the network component device # 1. In addition, the standby EMS takes in the network component device # 3, cancels the relay setting from the network component device # 4, and switches and sets the customer line to be relayed only from the network component device # 2. Then, the active and standby EMS records the contents of the above setting process in each network DB with the affected flag added.

FIG. 15 is a diagram showing a recording format of the network DB.
In the operational EMS (EMS1 system), the process of switching the customer line from the network component device # 4 to the network component device # 2 for the network component device # 1, and the network for the customer line in the network component device # 2 A process of relaying from the device # 1 to the network constituent device # 3 is performed. The description of these processes is associated with the execution time and recorded in the network DB.

  In the standby system EMS (EMS2 system), the network component device # 3 performs a process of switching the customer line from the network component device # 4 to the network component device # 2, and records it in the network DB together with the execution time. Yes.

FIG. 16 is a diagram illustrating a DB matching result at the time of recovery from the disaster status.
The same data as shown in FIG. 15 shown in (1) of FIG. 16 is exchanged between the EMSs of both systems, and the data (2) obtained by merging the exchanged data into the network DB of the EMSs of both systems. Store.

  As described above, when performing network operation using EMS at the time of both disasters as an operational system, it is possible for EMS to automatically grasp the devices that EMS automatically captures without checking the connection status of several hundred network components. Is possible.

Hereinafter, an application example using the configuration of the above embodiment will be described.
If the EMS has a redundant configuration of the active / standby system, the standby system determines that the active application has stopped (notification of the active application stop), and a method of transitioning to the active system is adopted. Yes.

However, in the case of a network disconnection between EMSs or a hardware failure of the EMS, the standby system cannot know that the application has stopped and cannot transition to the active system.
Also in this case, if the diagnosis status of the other system EMS is determined, it is possible to determine whether the other system EMS is stopped or the network is disconnected between the EMSs, and the standby system EMS can surely transit to the operation system.

FIG. 17 is a diagram illustrating the contents of the diagnosis result when the other system EMS is stopped.
Since the active EMS (system 1) is stopped, the diagnosis request message is not transmitted. The standby EMS (system 2) receives the diagnosis response message from the network component devices # 1 to # 4 and acquires the diagnosis time. Although the diagnosis time of EMS (2 system) is updated, since EMS (1 system) is stopped, the diagnosis time is not updated.

FIG. 18 is a flowchart showing standby EMS operation / standby switching processing.
In step S20, it is determined whether an application stop notification is received from the active system. If the determination in step S20 is yes, the process proceeds to step S23. If the determination in step S20 is No, in step S21, it is determined whether the other system can monitor the network constituent devices by detecting the operating state of the other system's EMS. If the determination in step S21 is Yes, the process ends. If the determination in step S21 is No, in step S22, it is determined whether or not the diagnosis time of the EMS of the other system of the network constituent device being diagnosed in the own system has been updated. If the determination in step S22 is Yes, the process ends. If the determination in step S22 is No, in step S23, the state of the local EMS is changed to the active system, and the process ends.

Below, the case where EMS is tripled is demonstrated.
FIG. 19 is a diagram showing a system configuration when the EMS is tripled.
In FIG. 19, the configuration of the network configuration equipment is the same as that in FIG. 1, but two standby EMSs, the EMS 2 system and the EMS 3 system, are provided for the operation system EMS (1 system).

The standby system determines in advance a priority order for fetching the network constituent devices in the event of a disaster. In this example, the EMS2 system is positioned as priority 1, and the EMS3 system is positioned as priority 2.
Each of the EMS2 system and the EMS3 system is provided with a line so that it can communicate with the EMS1 system.

FIG. 20 is a diagram illustrating a situation during a disaster.
The network component device # 1 cannot communicate with the EMS 41, the network component device # 2 cannot communicate with the EMS 42, and the network component device # 3 cannot communicate with the EMS 40 and the EMS 42. The component device # 4 is in a state where it is damaged and cannot communicate at all.

FIG. 21 is a diagram showing the diagnosis result status of each EMS in the disaster situation of FIG.
The standby system EMS2 system and EMS3 system determine whether to take in network constituent devices, but the priority 1 EMS2 system transfers devices whose EMS1 system diagnosis has not been updated to its own EMS. In this example, network device # 3 is transferred.

  The EMS 3 system, which is the priority 2, transfers network devices in which the diagnosis of both the EMS 1 system and the 2 system has not been updated (no response) to the EMS. In this example, network device # 4 is transferred.

FIG. 22 is a diagram illustrating a hardware configuration example of the EMS.
A CPU 51, a memory 52, a display / keyboard 53, a hard disk 56, a network component device interface 55, an EMS intersystem interface 54, and a medium driver 59 are connected by a bus 50.

  A program for realizing the processing of the above embodiment is expanded in the memory 52 and executed by the CPU 51 to realize the processing of the embodiment. The program may be stored in a portable recording medium 60 such as a CD, a DVD, an IC memory, a flexible disk, or a Blu-ray. The program is read by the medium driver 59, developed in the memory 52, and executed. Also good.

  The display / keyboard 53 is used by an operator to read information from the EMS and to input information. The hard disk 56 stores a network DB 58 and a diagnosis management DB 57. Alternatively, the above-described program may be stored in the hard disk 56 and expanded into the memory 52 for execution.

  The network component device interface 55 is an interface for performing communication between the EMS of FIG. 22 and the network component device of the target network. The EMS intersystem interface 54 is an interface that performs EMS intercommunication with another EMS.

FIG. 23 is a diagram illustrating a hardware configuration of network configuration equipment.
In FIG. 23, the configuration for relaying, switching, and transferring data flowing through the line of the network constituent devices is omitted.

  The CPU 66, the EMS interface 65, and the memory 67 are connected by a bus 70.

  The inter-EMS interface 65 is an interface for performing communication between the network configuration device of FIG. 23 and the EMS. Based on the diagnosis request message received from the EMS via the EMS interface 65, the CPU 66 diagnoses its own network device and generates a diagnosis response message to be transmitted to the EMS. The memory 67 stores an alarm DB 68 and a diagnostic DB 69.

10, 40 Operational EMS (1 system)
11, 41 Standby system EMS (2 systems)
21 Network configuration management unit 22 Network DB
23 Network configuration device communication function 24 EMS communication function 25 Network configuration device setting management unit 26 Network configuration device alarm management unit 27 Network configuration device connection management unit 28 Diagnostic management DB
29 EMS connection management unit 30 EMS DB matching unit 31 EMS communication function 32 alarm management unit 33 alarm DB
34 EMS Diagnosis Management Unit 35 Diagnosis DB
36 Device setting unit 42 Standby system EMS (3 system)
50 bus 51, 66 CPU
52, 67 Memory 53 Display / Keyboard 54 EMS Intersystem Interface 55 Network Component Interface 56 Hard Disk 57 Diagnosis Management DB
58 Network DB
59 Medium driver 60 Portable recording medium 65 EMS interface 68 Alarm DB
69 Diagnosis DB

Claims (8)

In a network operation system comprising a network configuration device that configures a network and a plurality of network operation devices that manage and operate the network configuration device,
A first network operation device that periodically transmits a diagnosis request message for requesting acquisition of the status of the network component device to the network component device;
When the diagnosis request message is received, the reception time is acquired, the state of the network component device is diagnosed, and the diagnosis response message including the diagnosis result and the reception time is returned to the first network operation device. Component equipment; and
The network of the diagnostic request message from the first network operation device included in the diagnostic response message, which is periodically transmitted to the network component device, receives the diagnostic response message, and is included in the diagnostic response message A second network operation device configured to detect whether or not the reception time in the component device is updated, and to set the network component device to be under the control of the own network operation device if not updated;
A network operation system comprising:   2. The network operation according to claim 1, wherein when the reception time is not updated, it is detected that communication between the first network operation device and the network component device is interrupted. system.   The network operation system according to claim 2, wherein the communication interruption is caused by a disaster.   The first network operation device and the second network operation device are connected by a communication line, and each store setting information performed on the network constituent devices constituting a communication network that provides an information communication service. The network operation system according to claim 2, wherein when communication between the first network operation device and the second network operation device is resumed, the setting information is synchronized with each other.   The network operation system according to claim 1, wherein the plurality of network operation devices include an active network operation device and a standby network operation device.   The network operation system according to claim 5, wherein the standby network operation apparatus includes one or more network operation apparatuses.   2. The network operation system according to claim 1, wherein, among the network configuration devices, the network configuration device that does not respond to the diagnosis request message is not managed by the local network operation device. In a network operation method of a network operation system comprising a network component device that configures a network and a plurality of network operation devices that manage and operate the network component device,
The first network operation device periodically transmits a diagnosis request message for requesting acquisition of the state of the network component device to the network component device,
When the network component device receives the diagnosis request message, the network component device acquires the reception time, diagnoses the state of the network component device, and sends a diagnosis response message including the diagnosis result and the reception time to the first network operation device. Returned to
The second network operation device periodically transmits the diagnosis request message to the network component device, receives the diagnosis response message, and is included in the diagnosis response message from the first network operation device. Detecting whether the reception time of the diagnosis request message in the network component device is updated, and if not, setting the network component device to be under the management of the own network operation device;
A network operation method characterized by the above.