KR102434716B1 - Underwater network management system - Google Patents

Abstract

Underwater network management system according to an aspect according to the technical idea of the present disclosure, a management station corresponding to the manager, a gateway connected to the management station and corresponding to the proxy agent, each master agent or the master connected to the proxy agent Including a plurality of underwater devices corresponding to a sub-agent connected to the agent, wherein each of the manager and the agents includes a plurality of management objects for the management of the plurality of underwater networks and the plurality of underwater devices. a management information base, wherein the manager and each of the agents' underwater management information base are updated based on the movement of a first underwater device among the plurality of underwater devices, and at least some of the plurality of underwater networks are It is reconstructed based on the movement of the first underwater device.

Description

UNDERWATER NETWORK MANAGEMENT SYSTEM

The technical idea of the present disclosure (disclosure) relates to an underwater network management system.

Water covers about 70% of the Earth's surface. Recently, new technologies related to monitoring of underwater ecosystem survey, resource exploration, measurement of pollutants and pollution levels, and meteorological observation and underwater data collection are emerging.

In an underwater network management system for managing an underwater network and devices existing in the water, systematic management of various information such as the underwater data may be required. However, the underwater environment has different characteristics from the terrestrial environment, and the resource availability of a device used in the water may be significantly different from the resource availability of a device used on the ground. In addition, since the management information base (MIB) of the terrestrial network has many managed objects (MOs), it is difficult to apply it to the underwater network as it is.

On the other hand, as the underwater network is actively being developed for networking using an underwater vehicle such as an autonomous underwater vehicle (AUV), a remotely operated vehicle (ROV), etc., the implementation of an underwater management information base for nodes with such mobility this may be necessary

1. Republic of Korea Patent Publication No. 10-2010-0077707 (published on Jul. 8, 2010)

One problem to be solved by the present invention is to provide an underwater network management system in which an underwater management information base (underwater-MIB (u-MIB)) is implemented for the management of an underwater network and underwater devices.

One problem to be solved by the present invention is to provide an underwater network management system in consideration of the mobility of nodes (agents) constituting the underwater network.

In order to achieve the above object, an underwater network management system according to an aspect according to the technical idea of the present disclosure, a management station corresponding to a manager, a gateway connected to the management station and corresponding to a proxy agent, each a plurality of underwater devices corresponding to a master agent connected to the proxy agent or a sub-agent connected to the master agent, wherein each of the manager and the agents includes: An underwater management information base comprising a plurality of management objects for management, wherein each of the manager and the agent, the underwater management information base is updated based on the movement of a first underwater device among the plurality of underwater devices and at least some of the plurality of underwater networks are reconfigured based on the movement of the first underwater device.

According to an embodiment, the first underwater device is included in a first underwater network of the plurality of underwater networks, and when it is detected that the first underwater device moves from the first underwater network to a second underwater network, The first underwater network and the second underwater network may be reconfigured.

According to an embodiment, the first underwater device is a first sub-agent connected to a first master agent of the first underwater network, and the first sub-agent is the second from a space corresponding to the first underwater network. As it moves to a space corresponding to the underwater network, a message for connection with another master agent may be output, and the message may include at least one management object indicating information of the first sub-agent.

According to an embodiment, the second master agent of the second underwater network receives the message output from the first sub-agent, and in response to the received message, it is added to the list of agents included in the second underwater network. adding the first sub-agent, registering the first sub-agent with the second underwater network through connection with the first sub-agent, and notifying that the first sub-agent is registered with the second underwater network A message may be sent to the proxy agent.

According to an embodiment, the proxy agent receives a message transmitted from the second master agent, updates a list including information on agents connected to the proxy agent in response to the received message, and the first sub-agent transmits a message for notifying that is registered in the second underwater network to the manager, and the manager may update a list including information of agents connected to the manager in response to the received message.

According to an embodiment, when the information of the first sub-agent is present in the list, the proxy agent updates that the first sub-agent is registered in the second underwater network, and the information of the first sub-agent If is not present, the first sub-agent may be added to the list.

According to an embodiment, the master agent of the first underwater network may delete the first sub-agent from the list of agents included in the first underwater network based on the movement of the first sub-agent.

According to an embodiment, the first underwater device is a first master agent of the first underwater network, and the first master agent is from a space corresponding to the first underwater network to a space corresponding to the second underwater network. As it moves, it outputs a message for registration as a sub-agent in the second underwater network, and the second master agent of the second underwater network sends the first master agent to the second underwater network in response to the received message. It can be registered as a sub-agent.

According to an embodiment, in response to the movement of the first master agent, any one of a plurality of sub-agents included in the first underwater network may be selected as the master agent, whereby the first underwater network may be reconfigured.

According to an embodiment, the selected master agent transmits a message for notifying that the first underwater network is reconfigured to the proxy agent, and the proxy agent receives the message transmitted from the selected master agent, In response to the message, the list including information of agents connected to the proxy agent may be updated.

According to an embodiment, the proxy agent transmits a message for notifying that the first underwater network is reconfigured to the manager, and the manager updates a list including information of agents connected to the manager in response to the received message can do.

According to an embodiment, the proxy agent may transmit control information of the first underwater network to the selected master agent.

According to an embodiment, the selected master agent transmits a request message for acquiring information on sub-agents included in the first underwater network to the sub-agents, and receives at least one management target from each of the sub-agents. Receive a response message including an object, based on the management object included in the received response message, it is possible to update the underwater management information base of the selected master agent.

The underwater network management system according to the technical idea of the present disclosure can more systematically manage information required for managing the underwater network by using an underwater management information base that is optimized and lightweight for an underwater network.

In addition, the underwater management information base implemented in the underwater network management system includes an information item (management object) to reflect the mobility of the nodes (agents) constituting the underwater network, thereby effectively reconfiguring the underwater network when the node moves. To maintain a smooth communication state.

Effects according to the technical spirit of the present disclosure are not limited to the above-mentioned effects, and other effects not mentioned may be clearly understood by those of ordinary skill in the art to which the present invention belongs from the description below. There will be.

In order to more fully understand the drawings cited in this disclosure, a brief description of each drawing is provided.
1 is an exemplary conceptual diagram of an underwater communication system to which the underwater network management system of the present disclosure is applied.
2 is a diagram schematically showing the configuration of an underwater network management system according to an exemplary embodiment of the present disclosure.
Figure 3 is a view showing the underwater network management system shown in Figure 2 in more detail.
4 to 8 are diagrams showing a detailed configuration of an underwater management information base according to embodiments of the present disclosure.
9 is a conceptual diagram of an operation in which the underwater network management system acquires and manages information of underwater devices according to an exemplary embodiment of the present disclosure.
10 is a diagram illustrating examples of managed objects implemented for management of information related to the mobility of an agent.
11 to 12 are diagrams for explaining an underwater network management operation as an underwater device corresponding to a sub-agent moves from a space corresponding to a first underwater network to a space corresponding to a second underwater network.
13 to 15 are diagrams for explaining an underwater network management operation as the underwater device corresponding to the master agent moves from the space corresponding to the first underwater network to the space corresponding to the second underwater network.

Exemplary embodiments according to the technical spirit of the present disclosure are provided to more completely explain the technical spirit of the present disclosure to those of ordinary skill in the art, and the following embodiments are modified in various other forms may be, and the scope of the technical spirit of the present disclosure is not limited to the following embodiments. Rather, these embodiments are provided to more fully and complete the present disclosure, and to fully convey the technical spirit of the present invention to those skilled in the art.

Although the terms first, second, etc. are used in this disclosure to describe various members, regions, layers, regions, and/or components, these members, parts, regions, layers, regions, and/or components refer to these terms. It is obvious that it should not be limited by These terms do not imply a specific order, upper and lower, or superiority, and are used only to distinguish one member, region, region, or component from another member, region, region, or component. Accordingly, a first member, region, region, or component to be described below may refer to a second member, region, region, or component without departing from the teachings of the present disclosure. For example, without departing from the scope of the present disclosure, a first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component.

Unless defined otherwise, all terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the concepts of this disclosure belong, including technical and scientific terms. In addition, commonly used terms as defined in the dictionary should be construed as having a meaning consistent with their meaning in the context of the relevant technology, and unless explicitly defined herein, in an overly formal sense. shall not be interpreted.

In the case where certain embodiments can be implemented differently, the order of specific processes may be performed differently from the described order. For example, two processes described in succession may be performed substantially simultaneously, or may be performed in an order opposite to the described order.

As used herein, the term 'and/or' includes each and every combination of one or more of the recited elements.

Hereinafter, embodiments according to the technical spirit of the present disclosure will be described in detail with reference to the accompanying drawings.

1 is an exemplary conceptual diagram of an underwater communication system to which the underwater network management system of the present disclosure is applied.

Referring to Figure 1, the underwater communication system is a management station (or server) 1 on the ground, a plurality of wireless communication devices (or nodes) present in the water (11a, 11b, 12a, 12b, 13, 14a, 14b; Hereinafter, collectively denoted as '10'), and a sleep gateway (20a, 20b; hereinafter collectively denoted as '20') existing between the management station 1 and the wireless communication device 10. have.

The management station 1 may be connected to the gateways 20a and 20b and the underwater wireless communication device 10 through a terrestrial base station antenna or satellite. The management station 1 may perform overall operations related to the management of data, resources, and devices 10 and 20 of the underwater communication system. For example, the management station 1 may store or process various types of data provided from the underwater wireless communication devices 10 to provide information for use in various fields. Also, the management station 1 may perform an operation such as checking and managing the states of the devices 10 and 20 included in the underwater communication system. For example, the management station 1 may be implemented as a server, but is not limited thereto.

The gateway 20 is connected between the management station 1 and the wireless communication devices 10 to enable data exchange between the management station 1 and the wireless communication devices 10 . To this end, the gateway 20 may support various known wireless communication methods for wireless communication with the management station 1 (eg, mobile communication methods such as LTE and 5G, satellite communication methods, etc.), and a wireless communication device ( 10) for underwater wireless communication with an underwater wireless communication method (eg, sound wave communication, visible light communication, infrared communication, low frequency communication, magnetic field communication, etc.) can be supported. According to an embodiment, the gateway 20 may be implemented as a communication device provided in the ships 30a and 30b.

The wireless communication devices 10 include a variety of devices that are disposed in or used in the water, and each of the devices may support an underwater wireless communication method. For example, the wireless communication devices 10 include a plurality of sensor nodes 11a and 11b for sensing data for measuring and monitoring an underwater environment, an underwater vehicle 12a, 12b, and an autonomous underwater vehicle (AUV) 13 ), and/or communication devices 14a, 14b mounted on or carried by the diver. These wireless communication devices 10 may form a network by being directly or indirectly connected using an underwater wireless communication method.

The wireless communication devices 10 may transmit various data acquired according to the operation of the device, such as data related to the underwater environment, to the management station 1 through the gateway 20 . Hereinafter, the wireless communication device 10 is referred to as an underwater device 10 for convenience of description, but this is not limited to that the wireless communication device 10 is a device used only in water.

Meanwhile, a network management system (NMS) for managing a communication network and devices constituting the communication network may be implemented in the communication system. Even in the case of the underwater communication system shown in Figure 1, an underwater network management system (underwater NMS (U-NMS)) for the management of the underwater network and devices 10, 20 may be implemented. The underwater network management system may be implemented in hardware, software, or a combination thereof.

However, the underwater environment is different from the terrestrial environment in which a general communication system is provided, and the resource availability (power supply, etc.) of the underwater device 10 may be significantly different from the resource availability of the communication device used on the ground. In addition, the management information base (MIB) of the terrestrial network holds a number of managed objects (MOs). Therefore, it may be inefficient to apply the network management system and management information base of the conventional general communication system as it is to the underwater communication system.

According to embodiments of the present disclosure, an underwater network management system can more systematically manage information for operation of an underwater network using an underwater management information base (underwater-MIB (u-MIB)) optimized for an underwater network. have. Hereinafter, various embodiments related to the underwater network management system and the underwater management information base of the present disclosure will be described with reference to FIGS. 2 to 8 .

2 is a diagram schematically showing the configuration of an underwater network management system according to an exemplary embodiment of the present disclosure. Figure 3 is a view showing the underwater network management system shown in Figure 2 in more detail.

Referring to FIG. 2 , the underwater network management system 100 may include a manager 110 and an agent 120 . Each of the manager 110 and the agent 120 may be implemented in hardware, software, or a combination thereof, but is not limited thereto.

For example, the manager 110 may manage the devices 10 and 20 included in the underwater network and/or control overall functions of the underwater network. The manager 110 may be implemented as the management station 1 or a device included in the management station 1 , or may include a program (such as a management application 310 ) installed in the management station 1 . The manager 110 may monitor or control the status of the underwater network or the devices 10 and 20 based on various management information provided from the agent 120 .

The agent 120 may be included in the underwater device 10 and the gateway 20 described above. For example, the underwater device 10 and the gateway 20 may include a device 320 having a processor (CPU, etc.), memory, an operating system (OS), an agent, and other configurations. The agent 120 may provide various information generated or obtained from the underwater device 10 and/or the gateway 20 to the manager 110 .

Each of the manager 110 and the agent 120 may include an underwater management information base (u-MIB) 130 and 140 . The underwater management information base (130, 140) may correspond to a database designed for management of the components included in the underwater network management system. The underwater management information bases 130 and 140 may correspond to a set of managed objects (MOs) using the structured format 150 to define names and entities suitable for the underwater network management system 100 . Each of the managed objects (MOs) may include various types of management information related to the underwater network and/or the devices 10 and 20 included in the underwater network.

As described above, the conventional management information base of a general terrestrial network maintains an excessive number of managed objects (MOs), and may not be suitable for application to an underwater network. Accordingly, the underwater management information base (130, 140) according to an embodiment of the present disclosure is a lightweight database including only the minimum management object (MOs) necessary for the management of the underwater network and devices (10, 20). By being implemented, it enables efficient management of an underwater network. The implementation example of the underwater management information base (130, 140) will be described in more detail later with reference to FIGS. 4 to 8.

2 to 3 , the manager 110 and the agent 120 may transmit and receive messages and/or information according to the packet exchange form defined by the management protocol 160 . For example, the manager 110 may receive and manage managed objects (MOs) from the agent 120 using a request message (Get Request or Set Request). The agent 120 may transmit a response message (Get Response or Set Response) including managed objects (MOs) to the manager 110 in response to the request message. According to an embodiment, when an important event occurs in the corresponding devices 10 and 20, the agent 120 sends a trap message (Trap) including the managed objects (MOs) related to the event to the manager 110 . ) can be transmitted. For example, the important event may include an increase in temperature, insufficient remaining battery power, insufficient memory space, and the like.

Hereinafter, various embodiments related to the underwater management information bases 130 and 140 and the management target objects (MOs) included therein will be described with reference to FIGS. 4 to 8 .

4 to 8 are diagrams showing a detailed configuration of an underwater management information base according to embodiments of the present disclosure.

4, the underwater management information base (130, 140) is a set of management object (MOs) hierarchically structured underwater network management information, using an object identifier (object identifier (OID)) underwater It can be organized into networks and underwater devices.

The underwater network section ( u_networks ) may be understood as underwater network information including a plurality of managed objects (MOs) for managing network connections between devices 10 and 20 (eg, checking connectivity between devices, etc.). .

The underwater device section ( u_devices ) is a plurality of managed objects (MOs) (eg, battery status of underwater devices, etc.) for management of devices (eg, proxy agent, master agent, sub-agent, etc.) constituting the underwater network. It can be understood as underwater device information that includes.

5 shows an example of the general structure of the underwater management information base (130, 140). Referring to FIG. 5 , the underwater management information base 130 , 140 includes a plurality of management objects (MOs), and each of the plurality of management objects (MOs) is an underwater network section ( u_networks ) or an underwater device section. ( u_devices ) can be included.

For example, the managed object (MO) is an object name (OBJECT-NAME), data type (DATA-TYPE), access authority (RIGHT-TO-ACCESS), status indicator (STATUS-INDICATOR), and object description (OBJECT-DESCRIPTION) ) can be defined as The object name indicates the name of the object, such as a device name or management information base version, and the data type indicates the type of data (eg, integer, string, time, etc.) corresponding to the object name. The access right indicates the right to search for an object (read-write, read-only, etc.), the status indicator indicates whether the object is mandatory or optional, and the object description indicates the description of the object. (text) can be displayed.

The interface description language may be used to define managed objects (MOs), and a structured format may be used to define the object names and the like.

6 shows an example of a management object included in the underwater network section ( u_networks ) of the underwater management information base (130, 140).

Referring to FIG. 6 , information related to network connectivity, packets transmitted/received through the network, and notification according to an event occurring in the network may be required for management of an underwater network. Managed objects (MOs) included in the underwater network section may be classified into the connectivity, packet, and notification categories.

Each of Tables 1 to 3 below shows an example of the configuration and category classification of managed objects included in the underwater network section ( u_networks ).

According to the embodiments of Tables 1 to 3, the connectivity category may include information on the type of network, signal strength, connection quality, network activation time, network disconnection time, and the number of devices connected to the network. The packet category may include information such as the total amount of packets received and transmitted through the network, the number of processed requests or responses, and the number of managed objects retrieved or changed according to the requests or responses. The notification category may include information included in a trap message when an event occurs, such as a communication connection failure with a specific device or authentication failure of a specific device.

The underwater network management system 100 acquires various information for management of the underwater network through the managed objects (MOs) of the aforementioned underwater network section ( u_networks ), and connects or maintains the underwater network based on the obtained information management operations, etc. may be performed.

7 shows an example of a management target object included in the underwater device section ( u_devices ) of the underwater management information bases 130 and 140 .

Referring to FIG. 7 , in order to manage the underwater devices constituting the underwater network, it may be necessary to grasp information or status of the device, battery, memory, temperature, location, connectivity, message (packet), notification, and the like. Based on this, the managed objects (MOs) included in the underwater device section ( u_devices ) are device information, device state, battery information, battery state, memory information, memory state, temperature state, location information, connection information, and message information. , notification information, and notification status.

Each of Tables 4 to 6 below shows examples of the configuration of managed objects included in the underwater device section ( u_devices ) and classification by category.

Group MO name Data type right to access Description u_devices_general_info u_devices_ID STRING read-only It indicates the identification number of underwater devices. u_devices_name STRING read-only It indicates the manufacturer's name of underwater devices. u_devices_firmware STRING read-only/write-only It indicates the current firmware version of underwater devices. u_devices_type STRING read-only It indicates the type of underwater devices such as UUVs, UWA-GW, UWA-CH, UWA-SNode, etc. u_devices_status u_devices_location INTEGER read-only It reports the existing location of underwater devices. u_devices_activeTime TIME read-only It reports the active connection time of a unique underwater device. u_devices_suspendedTime TIME read-only It reports the connection suspended time of a unique underwater device. u_devices_start BOOLEAN read-only It starts to collect the device management resources such as battery level, memory level, etc. u_devices_stop BOOLEAN read-only It stops to collect the management resources from underwater devices. u_devices_time TIME read-only/write-only It reports the current time of underwater devices, by increasing the time value in seconds. u_devices_battery_info u_devices_battery_total INTEGER read-only It indicates the total power of the individual battery in underwater devices (in mAh). u_devices_battery_used INTEGER read-only It indicates the used power of the individual battery in underwater devices (in mAh). u_devices_battery_available INTEGER read-only It indicates the remaining power of individual battery IN underwater devices (in mAh). u_devices_battery_status u_devices_battery_normal INTEGER read-only It reports the battery has no problem. '1' is the code for the "battery working normally" in underwater devices. u_devices_battery_damaged INTEGER read-only It reports if some physical damages (some problems are in the battery). '2' is the code for the "battery damages" in underwater devices. u_devices_battery_low INTEGER read-only It reports the battery charge is low. So, battery replacement or battery recharging is important in this situation. '3' is the code for the "low battery" in underwater devices. u_devices_battery_not_installed INTEGER read-only It reports the battery charge was not installed. '4' is the code for the "battery not installed" in underwater devices. u_devices_memory_info u_devices_memory_total INTEGER read-only It indicates the total memory space in underwater devices (in MB/GB). u_devices_memory_used INTEGER read-only It indicates the used memory space in underwater devices (in MB/GB). u_devices_memory_total INTEGER read-only It indicates the available memory space in underwater devices (in MB/GB).

Group MO name Data type right to access Description u_devices_memory_status u_devices_memory_damaged INTEGER read-only It reports the memory may be broken (some problem in memory). '1' is the code for the "memory damages" in underwater devices. u_devices_memory_low INTEGER read-only It reports the memory level is low. So, formatting is important in this situation. '2' is the code for the "low memory" in underwater devices. u_devices_memory_not_installed INTEGER read-only It reports the memory was not installed. '3' is the code for the "memory not installed" in underwater devices. u_devices_temperature_status u_devices_curr_temp_level INTEGER read-only It indicates the current temperature of underwater devices. u_devices_notify_temp_limit INTEGER read-only It indicates the limit value of temperature. It is useful when the temperature crosses its threshold in underwater devices. u_devices_location_info u_devices_address INTEGER read-only It indicates the address to track the location of underwater devices. u_devices_depth INTEGER read-only It indicates the distance from UWA-CH/UUV/UWA-SNode to UWA-GW to find the exact location. u_devices_received_time TIME read-only It indicates the received time or the reflected time of the acoustic signal in seconds to find the exact distance between the underwater devices. u_devices_speed INTEGER read-only It indicates the speed of the transmitted signal. u_devices_connectivity_info u_devices_network_Type STRING read-only It indicates the type of network connection with underwater devices such as acoustic-based network or RF-based network. u_devices_signal_strength INTEGER read-only It indicates the average received signal strength (RSS) of acoustic-based network or RF-based networks in decibels (dB). u_devices_signal_link_quality INTEGER read-only It indicates the link quality between the devices in the acoustic-based network or RF-based network. u_devices_message_info u_devices_sent_msgnum INTEGER read-only It reports the total number of messages to send by the devices through the network. u_devices_rcvd_msgnum INTEGER read-only It reports the total number of messages received from the devices through the network. u_devices_send_bits INTEGER read-only It reports the size of the data sends from the devices in bits. u_devices_rcvd_bits INTEGER read-only It reports the size of the data received from the devices in bits. u_devices_max_size INTEGER read-only It reports the maximum size of the data collected by the devices in bits. u_devices_notification_info u_devices_event_code INTEGER read-only It indicates the unique code of each event in underwater devices. u_devices_event_name INTEGER read-only It indicates the device event name such as memory problem, battery problem, etc. u_devices_event_description INTEGER read-only It indicates the detailed description of the error event occurring in underwater devices. u_devices_event_sendTime INTEGER read-only It indicates the last time the event generated in underwater devices. u_devices_notificationTable INTEGER read-only It updates and stores all the entries inside u_devices_notification_info .

Group MO name data type right to access Description u_devices_notification_status u_devices_no_error INTEGER read-only It reports no error in underwater devices. '1' is the code for reporting "No errors". u_devices_battery_trap INTEGER read-only It reports a low battery level in underwater devices. '2' is the code for reporting "low battery". u_devices_memory_trap INTEGER read-only It reports out of memory space problems in underwater devices. '3' is the code for reporting "low memory". u_devices_temp_trap INTEGER read-only It reports if the temperature is increased and extends its threshold value. This increase in temperature may cause the failure of devices. '4' is the code for reporting "increasing temperature" in underwater devices. u_devices_link_failure_trap INTEGER read-only It reports the connectivity problem between underwater devices. '5' is the code for reporting "connection failure". u_devices_low_signal_trap INTEGER read-only It reports if the devices receive low RSS value. '6' is the code for reporting "Low signal strength".

The underwater network management system 100 acquires various information for management of underwater devices through the management target objects (MOs) of the aforementioned underwater device section ( u_devices ), and monitors the status of the underwater devices based on the obtained information And, based on the monitored state, it is possible to perform a control and management operation for the underwater device.

8 shows an example of managed objects (MOs) for providing information about an event occurring in an underwater network or an underwater device to the manager 110 .

Referring to FIG. 8 , when an important event (such as a network or device error) occurs in an underwater network or an underwater device, the agent 120 includes a trap message including managed objects (MOs) indicating information about the event. (or packet) may be transmitted to the manager 110 . Managed objects (MOs) representing information about the event may be included in each of an underwater network section ( u_networks ) and an underwater device section ( u_devices ). For example, the managed objects (MOs) may indicate serial numbers of devices in which an event has occurred, a name of a device that transmits a trap message, and information about an event occurrence time, cause, and the like. The manager 110 recognizes an event occurring in the underwater network or underwater device based on the managed objects (MOs) included in the trap message received from the agent 120 , and controls the underwater network or underwater device according to the recognition result and management.

According to the embodiment of Figures 4 to 8, the underwater network management system 10 through the underwater information management base (u-MIB) implemented in a form optimized for the characteristics of the underwater network, efficient management of the underwater network and underwater devices can be performed.

9 is a conceptual diagram of an operation in which the underwater network management system acquires and manages information of underwater devices according to an exemplary embodiment of the present disclosure.

Referring to the embodiment of FIG. 9 , the underwater network management system 100 includes a manager 110 and a plurality of agents 120 , and the plurality of agents 120 is a proxy agent according to a connection relationship between underwater devices. agent) 900 , a master agent 910 , and a sub agent 920 . The manager 110 may correspond to the management station 1 , and the proxy agent 900 may correspond to the gateway 20 . The sub-agent 920 may correspond to an underwater device connected to an end of the underwater network, and the master agent 910 may correspond to an underwater device connected between the proxy agent 900 and the sub-agent 920 .

The manager 110 acquires information (management object) included in the underwater management information base of the master agent 910 or the sub-agent 920 through the proxy agent 900, and based on the obtained information, the master agent ( The state of the underwater device corresponding to the 910) or the underwater device corresponding to the sub-agent 920 may be monitored.

As an example, the manager 110 may transmit a request message for information on the connection state of the underwater devices to the proxy agent 900 . In response to the received request message, the proxy agent 900 may transmit a request message for connection state information to each of the lower connected agents (the master agent 910 and/or the sub-agent 920 ). Master agent 910 and / or sub-agent 920 in response to the received request message, each of the management objects (MOs) included in the underwater management information base 140, related to the connection state of the underwater device A response message including managed objects may be transmitted to the proxy agent 900 . For example, the management object related to the connection state includes information for identification of each underwater device (device name, etc.), state-related information (operation state, battery state, etc.), and/or information on the connection state (connection or not). , network type, connection quality, etc.) may be managed objects.

The manager 110 may receive a response message including managed objects from the proxy agent 900 , and monitor the connection status of the underwater devices based on the received response message. Also, the manager 110 may update the underwater management information base 130 of the manager 110 based on the management objects included in the received response message. Meanwhile, the proxy agent 900 may also update the underwater management information base based on the management objects received from the master agent 910 and/or the sub agent 920 .

The underwater network management system 100 may include at least one underwater network. For example, each of the at least one underwater network may be divided into a predetermined space unit, and agents (master agent and/or sub-agent) existing in the same unit space may form one underwater network.

Meanwhile, some of the agents (eg, UUV, AUV, etc.) have mobility, and may move from a specific unit space to another unit space as needed. Alternatively, some agents may be moved from a specific unit space to another unit space under the influence of birds or the like. In this case, the agent moved to another unit space must be registered in the underwater network formed in the other unit space to smoothly perform communication. An embodiment of an underwater management information base reflecting the mobility of such an agent (node) and an embodiment of a network management operation using the same will be described below with reference to FIGS. 10 to 15 .

10 is a diagram illustrating examples of managed objects implemented for management of information related to mobility of an agent.

Referring to FIG. 10 , a managed object (MO) related to mobility may be provided differently depending on the type or attribute of the agent. For example, a managed object (MO) related to mobility may be implemented differently for each of a sub-agent, a fixed master agent, a master agent with mobility, a proxy agent, and a manager.

Meanwhile, a managed object (MO) related to mobility may be included in the underwater device section ( u_devices ), and the contents of each managed object are shown in Tables 7 to 11 below.

MOs considering mobility for sub agent group name MOs Description u_devices_mobility_action_info u_devices_mobility_action_start It indicates the sub agent started moving from its old position. u_devices_mobility_action_moving It indicates the sub agent is currently moving. u_devices_mobility_action_stop It indicates the sub agent stop moving. u_devices_mobility_action_distance_moved It indicates the distance between the old position and the new position of sub agent. u_devices_mobility_location_info u_devices_mobility_SA_old_location It indicates the old position of sub agent in U-NMS. u_devices_mobility_SA_new_location It indicates the new position of a sub agent in the U-NMS. u_devices_mobility_auto_configuration u_devices_mobility_change_identified It indicates the changes in sub agent such as start moving, still moving, and stop moving. u_devices_mobility_change_auto_update It automatically updates and fixes the new position of sub agent in sub agent. u_devices_mobility_change_notify Sub agent notifies the changes in position to master agent 1 and master agent 2.Notify the changes in position from position 1 to position 2 to master agent 1 and master agent 2. u_devices_sub_agent_mobility_error (critical events of sub agent) u_devices_mobility_SA_battery_low The sub agent sends the trap message to the master agent, that shows the reason for mobility error (battery low is the reason for mobility problem in sub agent). u_devices_mobility_SA_hardware_fault It indicates the hardware fault in sub agent to the master agent. So, the sub agent is not moving. u_devices_mobility_SA_connectivity_fault It indicates the connectivity problem of sub agent to the master agent. u_devices_mobility_SA_memory_fault It indicates the memory problem of sub agent to the master agent. So, the sub agent cannot be updated due to a memory error.

Referring to the embodiment of Table 7, the managed objects implemented in the subagent in relation to mobility include information related to whether to move (movement start, moving, stop, moving distance, etc.), location information (previous location, latest location, etc.) ), and event information related to movement (movement impossible due to low battery or hardware error, network connection failure, etc.) can be managed.

MOs considering mobility for stable Master agent group name MOs Description u_devices_stable_MA_configuration u_devices_mobility_total_connected It indicates the total number of sub agents connected under master agent 1 and master agent 2. u_devices_mobility_change_detection Master agent identifies the changes in the position of sub agent from network 1 to network 2.
It identifies the new sub agent is discovered by master agent 1 or master agent 2 under network 1 or network 2. u_devices_mobility_change_addition It adds the new sub agent to master agent 1 or master agent 2 which is discovered under network 1 or network 2. u_devices_mobility_change_update It updates the addition of new sub agent to master agent 1 and master agent 2. u_devices_mobility_change_notify Master agent 1 and master agent 2 notifies the changes to the proxy agent. u_devices_MA_critical_trap u_devices_mobility_MA_battery_low The master agent sends the critical trap message to the proxy agent. The error is due to a low battery problem in the master agent. u_devices_mobility_MA_hardware_fault It indicates the hardware fault in master agent to the proxy agent. So, the master agent cannot function more. u_devices_mobility_MA_connectivity_fault It indicates the connectivity problem between the master agent and proxy agent. u_devices_mobility_MA_memory_fault It indicates the memory problem of the master agent to proxy agent. Therefore, the master agent updating process is stopped.

Referring to the embodiment of Table 8, the managed objects implemented in the fixed master agent include information related to the connected sub-agent (the number of connected sub-agents, movement detection, additional detection, etc.), event information (low battery, hardware failure, You can manage information such as connection failure with a proxy agent).

MOs considering mobility for mobile Master agent group name MOs Description u_devices_mobility_MA_auto_configuration u_devices_mobility_MA_change_identified It indicates the changes in master agent such as start moving, still moving, and stop moving. u_devices_mobility_MA_change_addition It indicates that the new master agent is moved under another master agent. That means master agent 1 moved from network 1 to network 2. u_devices_mobility_MA_change_auto_update It automatically updates and fixes the new position of master agent in master agent. u_devices_mobility_SA_convertion It converts the newly added master agent to sub agent. u_devices_mobility_MA_convertion It converts the existing sub agent to master agent based on battery availability. u_devices_mobility_SA_change_notify Master agent notifies the conversion of the master agent to sub agent to proxy agent 1 and proxy agent 2. u_devices_mobility_SA_update_objects The proxy agent and master agent will update the MOs of the newly formed sub agent. u_devices_mobility_MA_change_notify Master agent notifies the conversion of the sub agent to master agent to proxy agent 1 and proxy agent 2. u_devices_mobility_MA_update_objects The proxy agent will update the MOs of the newly formed master agent. u_devices_mobility_MA_auto_confirmation u_devices_mobility_MA_send_request The newly formed master agent will send the request to all sub agent for confirmation. u_devices_mobility_SA_send_response The sub agent will send the ack message. This message will make the connection between the newly formed master agent and sub agents. u_devices_MA_critical_trap u_devices_mobility_MA_battery_low The master agent sends the critical trap message to the proxy agent. The error is due to a low battery problem in the master agent. u_devices_mobility_MA_hardware_fault It indicates the hardware fault in master agent to the proxy agent. So, the master agent cannot function more. u_devices_mobility_MA_connectivity_fault It indicates the connectivity problem between the master agent and proxy agent. u_devices_mobility_MA_memory_fault It indicates the memory problem of the master agent to proxy agent. Therefore, the master agent updating process is stopped. u_devices_MA_mobile_trap u_devices_mobility_MA_action_start It indicates the master agent started moving from its old position. u_devices_mobility_MA_action_moving It indicates the master agent is currently moving. u_devices_mobility_MA_action_stop It indicates the master agent stop moving. u_devices_mobility_MA_action_disctance_moved It indicates the distance between the old position and the new position of the master agent. u_devices_mobility_MA_location_info u_devices_mobility_MA_old_location It indicates the old position of master agent in U-NMS. u_devices_mobility_MA_new_location It indicates the new position of a master agent in the U-NMS.

Referring to the embodiment of Table 9, the managed objects implemented in the movable master agent include information related to the movement of the master agent, information for network configuration according to the movement of the master agent, event information related to movement, etc. You can manage a variety of information.

MOs considering mobility for proxy agent (Gateway) group name MOs Description u_devices_mobility_PA_configuration u_devices_mobility_MA_connected It indicates the master agent is connected with proxy agent 1 or proxy agent 2. u_devices_mobility_change_MA_received It receives the changes reported by the master agent. u_devices_mobility_change_MA_update It updates the changes reported by mater agent 1 or master agent 2 to the proxy agent 1 and proxy agent 2. u_devices_mobility_change_MA_notify proxy agent 1 or proxy agent 2 notifies the changes to the manager.Also, the updated information is shared between the proxy agent 1 and proxy agent 2. u_devices_mobility_change_MA_auto_correction It will try to automatically update and correct the software faults that occur in the proxy agent.

Referring to the embodiment of Table 10, managed objects implemented in the proxy agent may manage various information for reconfiguring the underwater network according to the movement of the master agent and/or sub-agent.

MOs considering mobility for Manager group name MOs Description u_devices_mobility_location_info u_devices_mobility_location_old_position It indicates the old position of node in U-NMS. u_devices_mobility_location_new_position It indicates the new position of the node in the U-NMS. u_devices_mobility_location_location_update It updates the location information in the manager base on the information sent by the proxy agent 1 or proxy agent 2. u_devices_mobility_network_info u_devices_mobility_network_device_connected It indicates the total number of devices connected in U-NMS such as proxy agent, the master agent, and sub agent. u_devices_mobility_network_receive_notification It receives the notification from the proxy agent. u_devices_mobility_network_auto_update It automatically updates the information in manager u-MIB based on the changes received from proxy agent. u_devices_mobility_network_adaptation
u_devices_mobility_network_scalability It is used to automatically adapt the changes that appear in network 1 or network 2. For example, sub agent was moved from network 1 to network 2.

Referring to the embodiment of Table 11, managed objects implemented in the manager may manage location information of agents, information related to an underwater network reconfigured according to movement of the master agent and/or sub-agent, and the like.

11 to 12 are diagrams for explaining an underwater network management operation as an underwater device corresponding to a sub-agent moves from a space corresponding to a first underwater network to a space corresponding to a second underwater network.

Referring to FIG. 11 , the underwater network management system 100 may include a manager 110 and agents corresponding to the management station 1 . Agents include at least one proxy agent (900a, 900b), a master agent (MA1, MA2) connected to the proxy agents (900a, 900b), and sub-agents (SA1 to SA5) connected to the master agent (MA1, MA2). may include For example, the proxy agents 900a and 900b may correspond to the gateway 20, and each of the master agents MA1 and MA2 and the sub-agents SA1 to SA5 may correspond to an underwater device. Although one master agent MA1 and MA2 is illustrated in FIG. 11 as being connected to each of the proxy agents 900a and 900b, a plurality of master agents may be connected to the proxy agents 900a and 900b according to an embodiment.

On the other hand, each of the master agents (MA1, MA2) may configure the underwater network (NW1, NW2) together with the connected sub-agent. For example, the first underwater network (NW1) may be configured to include a first master agent (MA1), and sub-agents (SA1, SA2, SA3) connected to the first master agent (MA1). The second underwater network (NW2) may be configured to include a second master agent (MA2), and sub-agents (SA4, SA5) connected to the second master agent (MA2).

The space corresponding to the underwater network may be defined by the manager 110 or the proxy agent 900 . In this case, any one of the underwater devices located in the same space may be set as the master agent, and other devices may be set as the sub-agent. According to an embodiment, the space corresponding to the underwater network may correspond to a communicationable distance with the master agent of the corresponding underwater network (or a distance at which communication performance maintains more than the reference performance).

Meanwhile, among underwater devices, AUV, UUV, ROV, etc. may have mobility. For example, an underwater device corresponding to a sub-agent (third sub-agent SA3) among underwater devices having such mobility corresponds to a second underwater network NW2 from a position in the space corresponding to the first underwater network NW1. You can move to a location in space. As it moves to the space corresponding to the second underwater network (NW2), the sub-agent (SA3) may not be able to perform normal communication with the first master agent (MA1). In this case, the sub-agent SA3 may be blocked from transmitting and receiving information with the outside (manager, etc.), and the manager 110 or the like does not receive the status information of the sub-agent SA3, etc., so may not be able to perform normal management of Alternatively, the sub agent (SA3) may be able to communicate itself with the first master agent (MA1) in a space corresponding to the second underwater network (NW2). However, to perform communication in connection with the second master agent (MA2) of the second underwater network (NW2) may be effective, such as communication quality or power consumption.

According to an embodiment of the present disclosure, the underwater network management system 100 can prevent the above-described problem by actively reconfiguring the underwater network when the movement of the sub-agent is detected.

12 illustrates an embodiment of an underwater network management operation upon detecting the movement of a sub-agent. Referring to FIG. 12 , the sub-agent (eg, the third sub-agent SA3) may detect a movement from a location in the space corresponding to the first underwater network NW1 to another location (S200).

The underwater device (eg, AUV, etc.) corresponding to the sub-agent SA3 may move according to the driving of the driving unit such as a motor (not shown). Based on the driving of the driving unit, the sub-agent SA3 may detect a movement to another location, and based on whether or not the movement is moving, the moving distance, etc., the managed objects (MOs) of the underwater management information base (u-MIB). In FIG. 10 , management objects related to mobility may be updated.

The sub-agent SA3 is based on the sensed movement distance, the sensed location, or whether communication with an existing connected master agent (eg, the first master agent MA1) is possible, etc., from the space corresponding to the first underwater network NW1. deviation can be detected.

On the other hand, as the movement of the sub-agent SA3 is detected, the master agent MA1 may delete the moved sub-agent SA3 from the list of sub-agents included in the first underwater network NW1 (S210).

The master agent MA1 may detect the movement of the sub agent SA3 through a communication means or a sensor. Alternatively, the master agent MA1 may receive a managed object indicating mobility-related information from the sub-agent SA3, and detect the movement of the sub-agent SA3 based on information included in the received managed object. have. For example, when the master agent MA1 detects that the position of the sub-agent SA3 on the move is out of the space corresponding to the first underwater network NW1, or communication with the sub-agent SA3 becomes impossible (or communication performance) If it is lower than this reference performance), the sub-agent SA3 may be deleted from the list of sub-agents (SA1, SA2, etc.) constituting the first underwater network (NW1). As the sub-agent SA3 is deleted, the first underwater network NW1 may be reconfigured into a first master agent MA1, a first sub-agent SA1, and a second sub-agent SA2.

Although not shown, according to an embodiment, the master agent (MA1) is based on the reconfiguration result of the first underwater network (NW1), management related to mobility among the managed objects included in the underwater management information base of the master agent (MA1) You can update the target object. For example, the master agent MA1 may update a managed object indicating information on “the number of connected sub-agents” among the managed objects. Thereafter, the master agent MA1 transmits the updated managed object according to the request of the proxy agent 900a or the manager 110, or transmits a trap message including the updated managed object to the proxy agent 900a. can also be transmitted.

The sub-agent SA3 may perform an operation for registration in the underwater network corresponding to another master agent by detecting a departure from the space corresponding to the first underwater network NW1. For example, when communication with the first master agent MA1 is not normally performed for more than a predetermined time after the sub-agent SA3 moves a predetermined distance, an operation for registration in the underwater network corresponding to the other master agent can be performed. have.

The sub agent SA3 may transmit (output) a trap message for connection with another master agent (S220).

For example, the sub-agent SA3 may not recognize information about the location of another master agent. Accordingly, the sub-agent SA3 may broadcast the trap message using the underwater communication methods (sonic wave, visible light, infrared light, magnetic field, low frequency, etc.) implemented in the underwater device. The trap message may include information (serial number, device name, etc.) of the sub agent SA3.

According to an embodiment, when the sub-agent SA3 includes information on the space of the second underwater network NW2, and/or the information on the master agent MA2 located in the second underwater network NW2, The sub-agent SA3 may recognize that the current sub-agent SA3 corresponds to the space of the second underwater network NW2 based on the moved location. According to the recognition result, the sub-agent SA3 may transmit a trap message for connection with the second master agent MA2 of the second underwater network NW2.

As the sub-agent SA3 outputs a trap message at a location in the space corresponding to the second underwater network NW2, the second master agent MA2 of the second underwater network NW2 can receive the trap message. have. The second master agent MA2 may register the sub-agent SA3 to the second underwater network NW2 by adding the sub-agent SA3 to the list in response to the received trap message (S230).

The second master agent MA2 may identify the sub-agent SA3 in response to the received trap message, and add the identified sub-agent SA3 to the list. Accordingly, the list corresponding to the second master agent MA2 may include the pre-registered sub-agents SA4 and SA5 and the added sub-agent SA3. In addition, the second master agent (MA2) is connected to the sub-agent (SA3), it is possible to add the sub-agent (SA3) to the second underwater network (NW2).

Although not shown, the second master agent MA2 may transmit a message including at least some of the managed objects included in its underwater management information base to the sub-agent SA3. The sub-agent SA3 may communicate with the second master agent MA2 by updating the underwater management information base based on the received message.

The second master agent (MA2) may transmit a trap message for informing the proxy agent (900b) that the sub-agent (SA3) is registered in the second underwater network (NW2) (S240).

For example, the trap message may be generated including at least a part of information of the trap message received from the sub-agent SA3. According to an embodiment, the second master agent MA2 may forward the trap message received from the sub-agent SA3 to the proxy agent 900b.

The proxy agent 900b may update the list corresponding to the proxy agent 900b in response to the received trap message (S250).

The list may include information on at least one master agent connected to the proxy agent 900b and sub-agents connected to the at least one master agent.

11 , information on the sub-agent SA3 added to the second underwater network NW2 may not exist in the list of the proxy agent 900b. In this case, the proxy agent 900b may add information about the sub-agent SA3 to the list in response to the received trap message.

According to an embodiment, when the first master agent (MA1) and the second master agent (MA2) are connected to the same proxy agent (eg 900b), unlike in FIG. 11 , the list of the proxy agent 900b includes the first underwater network (NW1). ), there may be information on the sub-agent SA3 registered as included in the . In this case, the proxy agent 900b may update the list to indicate that the sub-agent SA3 is included in the second underwater network NW2.

Similar to step S240, the proxy agent 900b may transmit a trap message for informing the manager 110 that the sub-agent SA3 is registered in the second underwater network NW2 (S260). The manager 110 may update the list corresponding to the manager 110 in response to the received trap message (S270).

The list of the manager 110 may include information on the sub-agent SA3 registered to be included in the first underwater network NW1. The manager 110 may update the list to indicate that the sub-agent SA3 is included in the second underwater network NW2 in response to the received trap message.

Accordingly, the sub-agent SA3, which has moved to the space corresponding to the second underwater network NW2, is registered in the second underwater network NW2 to continue smooth communication with other underwater devices and the management station 1 on the ground, etc. can be done

13 to 15 are diagrams for explaining an underwater network management operation as the underwater device corresponding to the master agent moves from the space corresponding to the first underwater network to the space corresponding to the second underwater network.

13 to 14 , the configuration of the underwater network management system 100 may be similar to that of FIG. 11 . The first underwater network (NW1) may be configured to include a first master agent (MA1), and sub-agents (SA1, SA2, SA3) connected to the first master agent (MA1). The second underwater network (NW2) may be configured to include a second master agent (MA2), and sub-agents (SA4, SA5) connected to the second master agent (MA2).

On the other hand, the underwater device corresponding to the master agent may be maintained in a fixed state at a predetermined position or freely movable according to the type or characteristic of the device. The underwater management information base of the master agent maintaining a fixed state may include the managed objects of Table 8, and the underwater management information base of the movable master agent may include the managed objects of Table 9.

For example, the first master agent MA1 may correspond to the above-described UUV, AUV, ROV, etc. as a movable master agent. The first master agent (MA1) may move from the space corresponding to the first underwater network (NW1) to the space corresponding to the second underwater network (NW2) during operation. In this case, normal communication between the sub-agents SA1 , SA2 , SA3 and the first master agent MA1 existing in the first underwater network NW1 may not be performed, or communication performance and power efficiency may be reduced.

According to an embodiment of the present disclosure, the underwater network management system 100 can prevent the above-described problem by actively reconfiguring the underwater network when the movement of the master agent is detected.

As an example, the first master agent (MA1) moved to the second underwater network (NW2) as shown in Figure 14 is registered in the second underwater network (NW2) as a sub-agent (SA6), the second master agent ( MA2) can be connected. On the other hand, the underwater network management system 100 reconfigures the first underwater network (NW1) by re-selecting the master agent of the first underwater network (NW1) (eg, selecting the sub agent (SA2) as the master agent (MA1')) can do.

In this regard, FIG. 15 shows a specific embodiment of an underwater network management operation when the movement of the master agent is detected. Referring to FIG. 15 , the master agent (eg, the first master agent MA1) may detect a movement from a location in the space corresponding to the first underwater network NW1 to another location (S300).

The underwater device corresponding to the first master agent MA1 may move according to the driving of the driving unit. Based on the driving of the driving unit, the first master agent (MA1) can detect a movement to another location, and based on whether the movement is moving, the moving distance, etc., among the management objects of the underwater management information base, as described above in FIG. Managed objects related to mobility can be updated.

The first master agent (MA1) is a space corresponding to the first underwater network (NW1) based on the detected movement distance, the detected location, or whether communication with the existing connected sub-agents (SA1, SA2, SA3) is possible, etc. deviations can be detected.

For example, when the first master agent MA1 moves to the second underwater network NW2, the first master agent MA1 can be registered as a sub-agent SA6 in the moved second underwater network NW2 ( S305), thus the second underwater network (NW2) may be reconfigured. The operation of registering to the second underwater network NW2 as the sub-agent SA6 is the same as or similar to steps S220 to S270 of FIG. 12, and a description thereof will be omitted.

Although not shown, the first master agent (MA1) may include a list of sub-agents included in the first underwater network (NW1), but as it is registered as a sub-agent (SA6) in the second underwater network (NW2) You can also delete the list.

On the other hand, the sub-agents SA1, SA2, SA3 existing in the first underwater network (NW1) detect that the moved first master agent (MA1) does not exist in the space corresponding to the first underwater network (NW1) It can be done (S310).

For example, the sub-agents SA1, SA2, and SA3 may detect the movement of the first master agent MA1 through communication means or the like. Alternatively, the sub-agents (SA1, SA2, SA3) are the first master agent (MA1) when the connection is released as the registration in the second underwater network (NW2), the first master agent (MA1) is the first underwater network It may be detected that it does not exist in the space corresponding to (NW1).

The underwater network management system 100 may reselect any one of the sub-agents SA1, SA2, SA3 existing in the first underwater network NW1 as the master agent (S315).

The reselection operation may be performed according to various known protocols or algorithms. For example, the master agent may be randomly selected based on a low-energy adaptive clustering hierarchy (LEACH) protocol. Alternatively, a sub-agent having the highest power level among the sub-agents SA1, SA2, and SA3 may be selected as the master agent. According to an embodiment, the master agent may be selected based on a protocol such as LEACH-C or PEGASIS (power-efficient gathering in sensor information system).

According to the example shown in FIG. 14 , the second sub-agent SA2 may be selected as the master agent MA1 ′, and accordingly, the first underwater network NW1 may be reconfigured. According to an embodiment, the reselected master agent (MA1') may create a list having information of the sub-agents (SA1, SA3) included in the first underwater network (NW1).

The reselected master agent MA1' transmits a trap message including information related to the reconfiguration of the first underwater network NW1 to the proxy agent 900a (S320), and the proxy agent 900a receives the trap message In response, the list may be updated (S325).

The reselected master agent MA1 ′ may transmit a trap message including information related to the reconfigured first underwater network NW1 to the proxy agent 900a. For example, the trap message may include information about the master agent and sub-agents of the reconfigured first underwater network (NW1).

The proxy agent 900a may recognize that the first underwater network NW1 is reconfigured based on the received trap message, and update the list according to the recognition result. For example, the proxy agent 900a may delete the master agent MA1 previously registered in the list and change the second sub-agent SA2 as the master agent MA1'.

On the other hand, although not shown, the proxy agent 900a by using the information of the reselected master agent (MA1') to copy and customize the underwater management information base of the existing master agent (MA1), the reconfigured first underwater network Based on (NW1), the underwater management information base can be updated.

Similar to steps S260 to S270 of FIG. 12 , the proxy agent 900a may transmit a trap message for informing the manager 110 of information related to the reconfiguration of the first underwater network (NW1) (S330), the manager ( The 110 may update the list corresponding to the manager 110 in response to the received trap message (S340).

In the list of the manager 110, the master agent of the first underwater network (NW1) is registered as an existing master agent (MA1), and the reselected master agent (MA1') is a sub-agent of the first underwater network (NW1) It may be in a state of being registered as (SA2). The manager 110 may change the reselected master agent MA1' as the master agent of the first underwater network NW1 by updating the list in response to the received trap message, and the existing master agent MA1 It can be changed as a sub-agent SA6 of the second underwater network NW2.

Meanwhile, the proxy agent 900a may transmit control information that the existing master agent MA1 has to the reselected master agent MA1' (S340). The control information may correspond to information for controlling sub-agents included in the first underwater network NW1. The reselected master agent MA1' may control the sub agents SA1 and SA3 based on the received control information.

The reselected master agent (MA1') may request all information of the connected sub-agents (SA1, SA3) in order to update the underwater management information base (u-MIB) (S345). For example, the master agent MA1' may request transmission of information by transmitting a Get all request message to the sub agents SA1 and SA3.

Each of the sub-agents SA1 and SA3 may transmit the managed objects (MOs) included in the underwater management information base to the master agent MA1' in response to the request (S350). For example, each of the sub-agents SA1 and SA3 may transmit a Get all response message including the managed objects to the master agent MA1'.

The master agent MA1' may update the underwater management information base of the master agent MA1' based on the received managed objects (S355). After that, when the master agent MA1 ' receives a request message (Get/Set request, etc.) from the proxy agent 900a, a response message (Get/Set response, etc.) including the managed object of the updated underwater management information base. etc.) to the proxy agent 900a.

10 to 15 , the underwater network management system 100 may actively reconfigure the underwater network when the underwater device 10 (or node) corresponding to the master agent or sub-agent moves. Accordingly, smooth underwater communication of the underwater devices 10 can be effectively maintained, and problems such as a decrease in communication efficiency or an increase in power consumption of the underwater devices can be minimized according to the reconfiguration of the underwater network.

Since the descriptions of the above embodiments are merely those exemplified with reference to the drawings for a more thorough understanding of the present disclosure, they should not be construed as limiting the technical spirit of the present disclosure.

Meanwhile, the present invention described above can be implemented as computer-readable codes on a recording medium in which a program is recorded. The computer-readable recording medium includes all types of recording devices in which data readable by a computer system is stored. Examples of computer-readable media include Hard Disk Drive (HDD), Solid State Disk (SSD), Silicon Disk Drive (SDD), ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, etc. includes Accordingly, the above detailed description should not be construed as restrictive in all respects but as exemplary. In addition, it will be apparent to those of ordinary skill in the art to which the present disclosure pertains that various changes and modifications can be made without departing from the basic principles of the present disclosure.

Claims (13)

In the underwater network management system for managing a plurality of underwater networks formed in the water,
a management station corresponding to a manager of the underwater network management system;
a gateway connected to the management station and corresponding to a proxy agent;
A plurality of underwater devices, each corresponding to a master agent connected to the proxy agent or a sub agent connected to the master agent,
Each of the manager and the agents,
an underwater management information base (u-MIB) comprising a plurality of managed objects for the management of the plurality of underwater networks and the plurality of underwater devices;
The manager and the respective underwater management information base of the agents are updated based on the movement of the first underwater device among the plurality of underwater devices,
At least some of the plurality of underwater networks are reconfigured based on the movement of the first underwater device,
The first underwater device is included in a first underwater network of the plurality of underwater networks,
When it is detected that the first underwater device moves from the first underwater network to the second underwater network, the first underwater network and the second underwater network are reconfigured;
When the first underwater device is the first master agent of the first underwater network,
The first master agent is registered as a sub-agent in the second underwater network as it moves from the first underwater network to the second underwater network,
According to the movement of the first master agent, any one of the plurality of sub-agents included in the first underwater network is selected as the master agent, whereby the first underwater network is reconfigured,
Underwater network management system. delete According to claim 1,
When the first underwater device is a first sub-agent connected to the first master agent of the first underwater network,
As the first sub-agent moves from the space corresponding to the first underwater network to the space corresponding to the second underwater network, it outputs a message for connection with another master agent,
The message includes at least one managed object indicating information of the first sub-agent,
Underwater network management system. 4. The method of claim 3,
The second master agent of the second underwater network,
receiving the message output from the first sub-agent,
In response to the received message, the first sub-agent is added to the list of agents included in the second underwater network, and the first sub-agent is connected to the second underwater network through a connection with the first sub-agent. register,
Transmitting a message to the proxy agent informing that the first sub-agent is registered in the second underwater network,
Underwater network management system. 5. The method of claim 4,
The proxy agent is
receiving a message transmitted from the second master agent, and updating a list including information of agents connected to the proxy agent in response to the received message;
sending a message to the manager notifying that the first sub-agent is registered in the second underwater network,
The manager updates the list including information of agents connected to the manager in response to the received message,
Underwater network management system. 6. The method of claim 5,
When the information of the first sub-agent is present in the list, the proxy agent updates that the first sub-agent is registered in the second underwater network, and when the information of the first sub-agent does not exist, adding a first sub-agent to the list;
Underwater network management system. 4. The method of claim 3,
The master agent of the first underwater network, based on the movement of the first sub-agent, deletes the first sub-agent from the list of agents included in the first underwater network,
Underwater network management system. According to claim 1,
As the first master agent moves from the space corresponding to the first underwater network to the space corresponding to the second underwater network, it outputs a message for registering as a sub-agent in the second underwater network,
the second master agent of the second underwater network registers the first master agent as a sub-agent in the second underwater network in response to the received message;
Underwater network management system. delete According to claim 1,
The selected master agent transmits a message to the proxy agent informing that the first underwater network is reconfigured,
The proxy agent is
receiving a message transmitted from the selected master agent, and updating a list including information of agents connected to the proxy agent in response to the received message,
Underwater network management system. 11. The method of claim 10,
The proxy agent is
Sending a message to the manager to inform that the first underwater network is reconfigured,
The manager updates the list including information of agents connected to the manager in response to the received message,
Underwater network management system. 11. The method of claim 10,
The proxy agent is
Transmitting the control information of the first underwater network to the selected master agent,
Underwater network management system. According to claim 1,
The selected master agent is
Transmitting a request message for obtaining information on sub-agents included in the first underwater network to the sub-agents,
Receiving a response message including at least one managed object from each of the sub-agents,
Based on the management object included in the received response message, updating the underwater management information base of the selected master agent,
Underwater network management system.

Images