KR20240040931A - Modular maritime traffic congestion prediction system - Google Patents

Abstract

The present invention relates to a modular maritime traffic congestion prediction system, and more specifically, to one or more congestion levels that calculate maritime traffic congestion based on maritime traffic data including AIS dynamic information and static information received from an intelligent maritime traffic information server. It relates to a modular maritime traffic congestion prediction system that includes a calculation module and one or more congestion prediction modules for predicting maritime traffic congestion. The modular maritime traffic congestion prediction system according to the present invention calculates and predicts maritime traffic congestion, and the modular maritime traffic congestion prediction system receives maritime traffic data from an intelligent maritime traffic information server and calculates the maritime traffic congestion. and a modular maritime traffic congestion prediction server that predicts, wherein the modular maritime traffic congestion prediction server includes an interface unit that receives the maritime traffic data from the intelligent maritime traffic information server, and a maritime traffic congestion prediction server based on the maritime traffic data. It includes a congestion calculation unit that calculates traffic congestion and a congestion prediction unit that predicts future maritime traffic congestion based on the maritime traffic congestion calculated by the congestion calculation unit.

Description

Modular maritime traffic congestion prediction system {MODULAR MARITIME TRAFFIC CONGESTION PREDICTION SYSTEM}

The present invention relates to a modular maritime traffic congestion prediction system, and more specifically, to one or more congestion levels that calculate maritime traffic congestion based on maritime traffic data including AIS dynamic information and static information received from an intelligent maritime traffic information server. It relates to a modular maritime traffic congestion prediction system that includes a calculation module and one or more congestion prediction modules for predicting maritime traffic congestion.

Maritime traffic congestion is an indicator for evaluating whether there is maritime traffic congestion in ports and routes, and it is difficult to define because it must take into account the operation characteristics of ships and the characteristics of the sea areas used by ships. In general, maritime traffic congestion is calculated using a technique to evaluate the marine traffic capacity of a route using the concept of occlusion area of the bumper model, and is based on various assumptions to reflect the operating characteristics of ships and the characteristics of the sea area used by ships. Typically, the ratio for estimating practical traffic capacity, the length of a standard ship, the section according to the length of the ship and the representative length for each section, and the short and long diameters of the blocked area are assumed based on various theories, and accordingly, the same Even if the data is analyzed, different maritime traffic congestion figures are derived.

In addition, the congestion figures derived in this way are used to predict future maritime traffic congestion, but even if the same forecast model is used, there is a large difference in the forecast value, and when a different forecast model is used, the overall trend may be predicted to be different. do. This phenomenon not only causes confusion in understanding the status of maritime traffic, but can also interfere with predicting future maritime traffic conditions and establishing policies related to maritime traffic safety.

Republic of Korea Patent Publication No. 10-2429235 (announced on August 4, 2022)

The purpose of the present invention to solve the above-mentioned problems is to calculate congestion based on various theories according to the congestion calculation module and compare several maritime traffic congestion prediction modules based on this to create a modular module that can predict highly reliable congestion. It provides a maritime traffic congestion prediction system.

In addition, the purpose of the present invention is to predict and visualize future maritime traffic congestion based on maritime traffic data in sea areas where congestion is expected, thereby predicting modular maritime traffic congestion that can help manage maritime traffic in a wide sea area with a small number of people. providing a system.

In order to achieve the above-mentioned purpose, the modular maritime traffic congestion prediction system according to an embodiment of the present invention calculates and predicts maritime traffic congestion, and the modular maritime traffic congestion prediction system is operated from an intelligent maritime traffic information server. It includes a modular maritime traffic congestion prediction server that receives maritime traffic data to calculate and predict the maritime traffic congestion, and the modular maritime traffic congestion prediction server receives the maritime traffic data from the intelligent maritime traffic information server. It includes an interface unit that calculates maritime traffic congestion based on the maritime traffic data, a congestion calculation unit that calculates maritime traffic congestion, and a congestion prediction unit that predicts future maritime traffic congestion based on the maritime traffic congestion calculated by the congestion calculation unit.

The congestion calculation unit includes one or more congestion calculation modules, wherein the congestion calculation module includes an actual maritime traffic calculation module for calculating actual maritime traffic for a specific gate line based on the maritime traffic data, and a basic maritime traffic volume calculation module for calculating actual maritime traffic for a specific gate line based on the maritime traffic data. It includes a practical traffic capacity calculation module that calculates traffic capacity and calculates practical traffic capacity based on the calculated basic traffic capacity, and the congestion calculation module uses the following formula based on the actual maritime traffic volume and the practical traffic capacity. Calculate the maritime traffic congestion as expressed in 1.

<Formula 1>

The actual maritime traffic volume calculation module calculates the actual maritime traffic volume by multiplying the L-squared conversion coefficient and the number of ships.

The practical traffic capacity calculation module calculates the basic traffic capacity by dividing the product of the route width and the average ship speed in the route by the size of the vessel's blockage area, and calculates the basic traffic capacity by multiplying the practical traffic capacity ratio. Calculated based on practical traffic capacity.

The maritime traffic data includes AIS dynamic information and static information.

According to the modular maritime traffic congestion prediction system of the present invention, the appropriate maritime traffic congestion can be calculated by simultaneously calculating and comparing maritime traffic congestion based on various theories, and various future maritime traffic congestion prediction modules are created based on the congestion calculated in this way. By comparison, it has the effect of predicting future maritime traffic congestion with high reliability.

In addition, the present invention can help manage maritime traffic in a wide sea area with a small number of people by predicting and visualizing future maritime traffic congestion based on maritime traffic data in sea areas where congestion is expected.

Figure 1 is a diagram briefly showing each configuration of the modular maritime traffic congestion prediction system according to the present invention.
Figure 2 is a diagram briefly showing each configuration of the modular maritime traffic congestion prediction server according to the present invention.
Figure 3 is a diagram briefly showing each configuration of the congestion calculation unit according to the present invention.
Figure 4 is a diagram showing the corresponding relationship between the congestion calculation module and the congestion prediction module according to the present invention.
Figure 5 is a diagram showing the modular maritime traffic congestion prediction system according to the present invention further including a data management server.
Figure 6 is a diagram showing each module of the data management server according to the present invention.
Figure 7 is a diagram showing each configuration of the data integration management module according to the present invention.
Figure 8 is a diagram showing each configuration of the network drive module according to the present invention.
Figure 9 is a diagram showing each configuration of the backup module according to the present invention.
Figure 10 is a diagram showing each configuration of the backup agent unit according to the present invention.
Figure 11 is a diagram showing an embodiment of a server load diagram according to the present invention.
Figure 12 is a diagram showing another embodiment of a server load diagram according to the present invention.
Figure 13 is a diagram showing another embodiment of a server load diagram according to the present invention.

Hereinafter, some embodiments of the present invention will be described in detail through illustrative drawings. When adding reference signs to components in each drawing, it should be noted that the same components are given the same reference numerals as much as possible even if they are shown in different drawings.

Also, in describing embodiments of the present invention, if detailed descriptions of related known configurations or functions are judged to impede understanding of the embodiments of the present invention, the detailed descriptions will be omitted.

Additionally, when describing the components of an embodiment of the present invention, terms such as first, second, A, B, (a), and (b) may be used. These terms are only used to distinguish the component from other components, and the nature, sequence, or order of the component is not limited by the term.

In this specification, singular forms also include plural forms unless specifically stated in the phrase. As used in the specification, “comprises” and/or “including” does not exclude the presence or addition of one or more other components in addition to the mentioned components.

In this specification, AIS (Automatic Identification System) refers to an automatic tracking system that exchanges data through electronic communication with nearby ships, base stations, satellites, etc. in order to identify ships and determine their location during maritime traffic control.

The modular maritime traffic congestion prediction system 1000 according to the present invention calculates past and present maritime traffic congestion and predicts future maritime traffic congestion.

Hereinafter, the present invention will be described in more detail with reference to the attached drawings.

Figure 1 is a diagram briefly showing each configuration of the modular maritime traffic congestion prediction system 1000 according to the present invention.

Referring to FIG. 1, the modular maritime traffic congestion prediction system 1000 (hereinafter also referred to as 'system') according to the present invention includes a modular maritime traffic congestion prediction server 100 and an intelligent maritime traffic information server 200. Includes.

The modular maritime traffic congestion prediction server 100 according to the present invention receives maritime traffic data including AIS dynamic information and AIS static information from the intelligent maritime traffic information server 200 and calculates and predicts maritime traffic congestion.

The modular maritime traffic congestion prediction server 100 according to the present invention includes an interface unit 110, a congestion calculation unit 120, and a congestion prediction unit 130.

The interface unit 110 receives maritime traffic data including AIS dynamic information and static information from the intelligent maritime traffic information server 200 and provides the received maritime traffic data to the congestion calculation unit 120. Meanwhile, in this specification, the interface unit 110, referred to as the intelligent maritime traffic information server 200, receives AIS dynamic information and static information. As long as it can receive AIS dynamic information and static information, the recipient is an intelligent maritime traffic information server. It is not limited to the traffic information server 200.

FIG. 2 is a diagram briefly showing each configuration of the modular maritime traffic congestion prediction server 100 according to the present invention, and FIG. 3 is a diagram briefly showing each configuration of the congestion calculation unit 120 according to the present invention.

The congestion calculation unit 120 calculates the maritime traffic congestion level based on the maritime traffic data received by the interface unit 110. Referring to FIG. 2, the congestion calculation unit 120 includes one or more congestion calculation modules 121. And, referring to FIG. 3, each congestion calculation module 121 includes an actual maritime traffic volume calculation module 1211 and a practical traffic capacity calculation module 1213. Therefore, as the congestion calculation unit 120 includes one or more congestion calculation modules 121, the system 1000 also includes one or more actual maritime traffic volume calculation modules 1211 and practical traffic capacity calculation modules 1213.

The actual maritime traffic volume calculation module 1211 calculates the actual maritime traffic volume by calculating the traffic volume for a specific gate line based on the received maritime traffic data. And the practical traffic capacity calculation module 1213 calculates the basic traffic capacity for a specific gate line and calculates the practical traffic capacity based on the calculated basic traffic capacity.

The congestion calculation module 121 calculates the maritime traffic congestion based on the actual maritime traffic volume and practical traffic capacity calculated by the actual maritime traffic volume calculation module 1211 and the practical traffic capacity calculation module 1213, respectively. The maritime traffic congestion calculation of the congestion calculation module 121 is as expressed in Equation 1 below.

<Formula 1>

The actual maritime traffic volume calculation module 1211 calculates the actual maritime traffic volume by calculating the traffic volume for a specific gate line based on the AIS dynamic information and static information received from the intelligent maritime traffic information server 200. The traffic volume calculated at this time can be understood to mean the L-squared traffic volume since the area of the sea area required for the safe operation of a ship is usually proportional to the square of the length (L) of the ship.

L-squared traffic volume can be calculated by dividing the vessel into sections and using the representative length of each section, or it can be calculated for each vessel using the length of each vessel. Sections can be divided according to the length of the ship and total tonnage, and if a representative length for each section can be defined, the method is not limited.

The actual maritime traffic volume calculation module 1211 calculates the L-squared conversion traffic volume by multiplying the L-squared conversion coefficient and the number of ships. When calculating for each section, the L square conversion coefficient is calculated as the square of the ratio of the representative length for each section and the standard ship length, and when calculated for each ship, it is calculated as the square of the ratio between the length of the ship and the standard ship length. Table 1 below is an example of calculating sections by gross tonnage of ships and L-squared traffic volume according to the Marine Port Logistics Information System (https://new.portmis.go.kr/).

<Table 1: Example of section and traffic volume calculation by gross tonnage of vessel>

The practical traffic capacity calculation module 1213 calculates the basic traffic capacity for a specific gate line and calculates the practical traffic capacity for this. The basic traffic capacity is calculated by multiplying the route width (length of the gate line) by the average ship speed in the route and dividing it by the size of the vessel's blockage area, which is expressed as Equation 2 below.

<Formula 2>

Practical traffic capacity refers to the number of vessels that can actually travel due to restrictions on vessel operation according to sea/weather conditions, freedom of vessel navigation, and maritime traffic management methods. It is generally assumed to be 20-25% of the basic traffic capacity, and this ratio is called the practical traffic capacity ratio.

Meanwhile, as described above, the system 1000 includes one or more practical traffic capacity calculation modules 1213. At this time, the practical traffic capacity ratio can be set differently depending on each practical traffic capacity calculation module 1213. Additionally, the major diameter and minor diameter of the occlusion area can be set differently depending on each practical traffic capacity calculation module 1213. In addition, as described above, the system 1000 includes one or more actual maritime traffic volume calculation modules 1211, and according to each actual maritime traffic volume calculation module 1211, vessel sections, representative lengths for each section, standard ship length, etc. You can set them all differently, or you can set only some of them differently.

Therefore, as a result, in the system 1000, each module 121 (specifically, 1211 and 1213) can simultaneously calculate maritime traffic congestion based on various theories, and calculate an appropriate maritime traffic congestion by comparing them.

Similarly, referring again to FIG. 2, the congestion prediction unit 130 includes one or more congestion prediction modules 131. The congestion prediction module 131 predicts future maritime traffic congestion based on the maritime traffic congestion calculated by the congestion calculation unit 120 and separately input data received from the user. The prediction of congestion is basically for the next 5 and 10 years, but is not limited to this.

The congestion prediction module 131 can use a future maritime traffic volume estimation method using trends in past maritime traffic volume according to each congestion prediction module 131, and can also use a maritime traffic volume estimation method based on the growth rate of cargo volume. In addition, a maritime traffic volume estimation method that considers the characteristics of each berth according to the port development plan can be used, and in addition to the methods mentioned above, an appropriate method for estimating future maritime traffic volume can also be used.

Figure 4 is a diagram showing the corresponding relationship between the congestion calculation module 121 and the congestion prediction module 131 according to the present invention.

Meanwhile, as shown in FIG. 4, the congestion calculation module 121 of the congestion calculation unit 120 and the congestion prediction module 131 of the congestion prediction unit 130 are 1:1, 1:N, and N:1 with each other. Or, it can have an N:N relationship.

As described above, the interface unit 110 provides the AIS dynamic information and static information received from the intelligent maritime traffic information server 200 to the congestion calculation unit 120, and if it can receive the AIS dynamic information and static information, The receiving destination is not limited to the intelligent maritime traffic information server 200. In addition, gate lines for calculating congestion can be created, modified, and deleted, and the congestion calculation module 121 of the congestion calculation unit 120 can be created, modified, and deleted. In the case of the congestion prediction module 131 of the congestion prediction unit 130, each data can be created, modified, and deleted, but modification may not be possible depending on the prediction module.

Additionally, the system 1000 can only perform congestion calculation using only the congestion calculation unit 120, and can also perform congestion prediction using the congestion calculation unit 120 and the congestion prediction unit 130. At this time, the interface unit 110 can select the congestion calculation module 121 and the congestion prediction module 131 to use.

Figure 5 is a diagram showing the modular maritime traffic congestion prediction system 1000 according to the present invention further including a data management server 300.

Referring to FIG. 5, the modular maritime traffic congestion prediction system 1000 according to the present invention includes a data management server ( 300).

As described above, the interface unit 110 can create, modify, and delete each data necessary for the congestion calculation module 121 and the congestion prediction module 131. In this way, information about data created, modified, or deleted by the interface unit 110 and information with various condition information selected (hereinafter referred to as ‘data’) are transmitted to the data management server 300 and stored. Additionally, data calculated by the congestion calculation unit 120 and the congestion prediction unit 130 (hereinafter referred to as ‘data’) are also transmitted to the data management server 300 and stored.

The data management server 300 can provide the received data to the user terminal 10 (see FIG. 6), and the user terminal 10 connects to the data management server 300 to access the data stored in the data management server 300. You can monitor the operation of the system 1000 according to the present invention by accessing .

Meanwhile, the user holding the user terminal 10 may be an administrator who monitors the operation of the system 1000 according to the present invention or a user who has been given permission by the administrator. That is, an administrator or user can monitor the operation of the system 1000 through the user terminal 10, and manage and supervise its operation and use.

There may be a plurality of user terminals 10 according to the present invention, and each user terminal 10 can access data stored in the data management server 300 by connecting to the data management server 300. The data management server 300 receives data from each configuration of the modular maritime traffic congestion prediction server and stores the received data in local storage (3111, 3121, 3131, 3141, see FIG. 7) within the data management server 300. do.

The user terminal 10 can connect to the data management server 300 and read, modify, or delete data stored in the data management server 300. Data modified or deleted by one user terminal 10 may be reflected in the data management server 300 and provided to a plurality of user terminals 10 again.

Meanwhile, the data management server 300 according to the present invention may be a centralized storage system including at least one individual server (3110, 3120, 3130, 3140, see FIG. 7). Each individual server 3110, 3120, 3130, and 3140 included in the data management server 300 connects to a storage system connected to a communication network to write or read data. At this time, if a failure occurs in any one of the individual servers (3110, 3120, 3130, 3140) connected to each other, the data in the failed individual server (3110, 3120, 3130, 3140) cannot be used, causing great inconvenience. Therefore, in this specification, the same data is stored redundantly in other individual servers (3110, 3120, 3130, 3140) so that data can be accessed even when a failure occurs in any individual server (3110, 3120, 3130, 3140). ) begins.

Figure 6 is a diagram showing each module of the data management server 300 according to the present invention.

Referring to FIG. 6, the data management server 300 according to the present invention includes a network drive module 320, a data integration management module 310, and a backup module 330. Each module 310, 320, and 330 is connected to each other through a wired or wireless communication network. As an embodiment, the user terminal 10 is connected to the network drive module 320, the network drive module 320 is connected to the data integration management module 310, and the data integration management module 310 is a backup module ( 330).

Figure 7 is a diagram showing each configuration of the data integration management module 310 according to the present invention.

The data integration management module 310 according to the present invention manages data through server duplication with guaranteed high availability (HA) based on virtualization technology. Referring to FIG. 7, the data integration management module 310 includes a plurality of individual servers (3110, 3120, 3130, 3140) and local storage (3111, 3121) included in each individual server (3110, 3120, 3130, 3140). , 3131, 3141). Each individual server (3110, 3120, 3130, and 3140) included in the data integration management module 310 is connected to each other to form a physical network. The data integration management module 310 manages the local storage (3111, 3121, 3131, 3141) of each individual server (3110, 3120, 3130, 3140) by grouping (3101, 3102) the local storage (3111) of the same group. , 3121, 3131, 3141) have the same data. That is, the data integration management module 310 groups the local storages 3111, 3121, 3131, and 3141 of each individual server 3110, 3120, 3130, and 3140 through a virtual network and manages them integratedly. The data integration management module 310 redundantly stores identical data in the local storages 3111, 3121, 3131, and 3141 of each group 3101 and 3102 to duplicate servers. The data integration management module 310 immediately provides data stored in other individual servers to the user terminal 10 when a failure occurs in at least one individual server.

For example, the data integration management module 310 may configure the first local storage 3111 of the first server 3110 and the second local storage 3121 of the second server 3120 into the first server group 3101. In one case, each data in the first local storage 3111 and the second local storage 3121 is stored in an alternating manner. That is, when data a is stored in the first local storage 3111 and data b is stored in the second local storage 3121, the data integration management module 310 stores the data a in the first local storage 3111. Data a is copied and stored in the second local storage 3121, and data b from the second local storage 3121 is copied and stored in the first local storage 3111. Accordingly, the first local storage 3111 and the second local storage 3121 of the first server group 3101 store the same data in duplicate. When an inspection or failure of a server occurs, the data integration management module 310 stores the same data in one of the local storages 3111 and 3121 of the first server group 3101, which stores the same data redundantly. 3121), that is, data stored redundantly in the local storage of another server of the same group can be provided to the user terminal 10, so the stability of data use can be guaranteed. A more detailed description of the data integration management module 310 will be provided later.

Figure 8 is a diagram showing each configuration of the network drive module 320 according to the present invention.

Referring to FIG. 8, the network drive module 320 according to the present invention includes a drive agent unit 3211 that provides a network drive to the user terminal 10 and a data integration management module through which the user terminal 10 provides a network drive. It includes a shared storage unit 3213 that allows access to the local storage (3111, 3121, 3131, 3141) of each individual server (3110, 3120, 3130, 3140) included in (310). Meanwhile, at this time, the shared storage unit 3213 may be each local storage (3111, 3121, 3131, 3141) of each individual server (3110, 3120, 3130, 3140) included in the data integration management module 310. Alternatively, it may be a separate storage where the data of each local storage (3111, 3121, 3131, and 3141) is copied. If the data stored in the shared storage unit 3213 is changed, the data in each local storage (3111, 3121, 3131, 3141) of each individual server (3110, 3120, 3130, 3140) is also changed.

That is, the user terminal 10 accesses each local storage (3111, 3121, 3131, 3141) included in the data integration management module 310 through the network drive provided by the drive agent unit 3211 to generate data. When modifications, deletions, etc. are performed, the results are reflected in real time in the data of each local storage (3111, 3121, 3131, 3141) of the shared storage unit (3213) or the data integration management module (310).

Accordingly, a plurality of user terminals 10 can share data in each local storage of the data integration management module 310 through a network drive. A more detailed description of the network drive module 320 will be provided later.

Figure 9 is a diagram showing each configuration of the backup module 330 according to the present invention.

Referring to FIG. 9, the backup module 330 according to the present invention is a local storage (3111, 3121, 3131, 3141) in an individual server (3110, 3120, 3130, 3140) managed by the data integration management module 310. Data is backed up according to a preset schedule. The individual servers 3110, 3120, 3130, and 3140 included in the data integration management module 310 further include backup units 3113, 3123, 3133, and 3143, respectively. The backup unit (3113, 3123, 3133, 3143) grants access to data in the local storage (3111, 3121, 3131, 3141) to the backup agent unit (3311) according to a preset backup schedule. The backup module 330 includes a backup agent unit 3311, and the backup agent unit 3311 backs up data in the local storage (3111, 3121, 3131, 3141) according to a preset schedule. (3113, 3123, 3133, 3143) is accessed to back up the data in the local storage (3111, 3121, 3131, 3141) to the backup storage unit (3317).

On the other hand, in server duplication, there is a problem in that data in each local storage (3111, 3121, 3131, and 3141) is stored redundantly in real time, so accidentally reflected data or virus-infected files can also be copied. The backup module 330 can restore accidentally reflected data or virus-infected files by backing up data according to a preset schedule, that is, at intervals. A more detailed description of the backup module 330 will be provided later.

Below, the data integration management module 310, network drive module 320, and backup module 330 according to the present invention will be described in more detail.

The data integration management module 310 according to the present invention is composed of a plurality of individual servers (3110, 3120, 3130, 3140) and a physical switch (not shown). A plurality of individual servers 3110, 3120, 3130, and 3140 form a physical network through a physical switch (not shown). The data integration management module 310 may be implemented with at least two servers.

Each individual server (3110, 3120, 3130, 3140) may include hardware such as a central processing unit, memory, and interface device, and software such as an operating system and supervisor. Since the general configuration of server hardware and software is widely known, the following will mainly describe the configuration of the server for the data integration management module 310 of this embodiment.

Each individual server 3110, 3120, 3130, and 3140 may or may not include at least one virtual machine. For example, the first to third servers 3110, 3120, and 3130 may each include at least one virtual machine, and the fourth server 3140 may not include a virtual machine.

As an embodiment, a plurality of individual servers (3110, 3120, 3130, and 3140) integrate and manage the local storage (3111, 3121, 3131, and 3141) included in each individual server (3110, 3120, 3130, and 3140). Includes virtual machines that Hereinafter, a virtual machine that integrates and manages the local storage (3111, 3121, 3131, 3141) of multiple individual servers (3110, 3120, 3130, 3140) is referred to as a 'management virtual machine', and other general virtual machines are referred to as 'general'. It is called a ‘virtual machine’.

The management virtual machine is located on at least one of a plurality of individual servers (3110, 3120, 3130, and 3140), and can be migrated between servers as needed.

Each individual server (3110, 3120, 3130, 3140) has at least one general virtual machine (not shown), a management virtual machine (not shown), local storage (3111, 3121, 3131, 3141), and a physical port (not shown). and backup units 3113, 3123, 3133, and 3143. The management virtual machine is located in one of a plurality of servers constituting the data integration management module 310.

Local storage (3111, 3121, 3131, 3141) is a storage medium such as HDD (Hard Disk Drive) or SSD (Solid State Drive) located within individual servers (3110, 3120, 3130, 3140). The local storages 3111, 3121, 3131, and 3141 may include at least one HDD or at least one SSD.

Data of general virtual machines and management virtual machines are stored in local storage (3111, 3121, 3131, 3141).

Since the data of the general virtual machine is stored in the local storage (3111, 3121, 3131, 3141), if an inspection or failure of the individual server (3110, 3120, 3130, 3140) occurs, the data of the individual server (3110, 3120, 3130, 3140) ) There is a problem where the operation of my virtual machine is paused. To solve this problem, in this embodiment, at least two servers are grouped into server groups (3101, 3102) to quickly perform virtual machine migration and provide uninterrupted virtual machine services, and then grouped into server groups (3101, 3102). ) My data is stored redundantly.

If multiple virtual machines exist within an individual server (3110, 3120, 3130, 3140), a bottleneck may occur in reading/writing data for each virtual machine, or a bottleneck may occur in sending and receiving data to and from a virtual machine on an external server. there is. Alternatively, the management virtual machine needs to quickly process control commands or data to manage local storage (3111, 3121, 3131, 3141) of multiple individual servers (3110, 3120, 3130, 3140) without bottlenecks. For rapid data transmission and reception, this embodiment includes a plurality of physical ports.

The physical ports of individual servers (3110, 3120, 3130, and 3140) are connected to the management virtual machine through a virtual switch (not shown). For example, the management virtual machine can transmit and receive control commands or data for managing the local storage (3111, 3121, 3131, 3141) of multiple individual servers (3110, 3120, 3130, 3140) through a physical port. .

The physical port is connected to the virtual switch to enable data transmission and reception for virtual machine migration. For example, when the first virtual machine located on the first server 3110 migrates to the second server 3120, the virtual machine is migrated through the physical port of the first server 3110 and the physical port of the second server 3120. Data for machine migration can be transmitted and received.

The physical port is connected to the virtual switch and can transmit and receive data to local storage (3111, 3121, 3131, 3141). For example, data from general virtual machines within individual servers (3110, 3120, 3130, 3140) are transferred to and stored in local storage (3111, 3121, 3131, 3141) through physical ports.

A physical port is connected to at least one general virtual machine through a virtual switch.

The backup units 3113, 3123, 3133, and 3143 are connected to the backup agent unit 3311 of the backup server 3310, which will be described later, and are connected to the individual servers 3110, 3120, 3130, at the request of the backup agent unit 3311. Access rights to data in the local storage (3111, 3121, 3131, 3141) are granted to the backup agent unit 3311 so that data stored in the local storage (3111, 3121, 3131, 3141) of 3140 can be backed up and stored at regular intervals. . The backup unit (3113, 3123, 3133, 3143) can back up all data in the local storage (3111, 3121, 3131, 3141) each time, or can extract and back up only the data that has changed from the previous backup to the current time. A detailed description of the backup units 3113, 3123, 3133, and 3143 and the backup server 3310 will be provided later.

In this embodiment, the general virtual machine and the management virtual machine form a virtual network through a virtual switch. For example, general virtual machines and management virtual machines are assigned private IP (Internet Protocol) addresses used in virtual networks, and each virtual machine can transmit and receive data using the private IP address.

For example, when the data integration management module 310 is composed of two servers, the first server 3110 and the second server 3120, the plurality of servers present in the first server 3110 and the second server 3120 The regular virtual machines and management virtual machines form a virtual network through at least one virtual switch.

The data integration management module 310 includes at least one server group (3101 or 3102), and each server group (3101 or 3102) may be composed of at least two or more individual servers (3110, 3120, 3130, and 3140). . As an embodiment, the data integration management module 310 includes a first server group 3101 including a first server 3110 and a second server 3120, a third server 3130, and a fourth server 3140. ) and consists of a second server group 3102 including.

As another example, the number of servers included in each server group may be different. For example, the first server group may be composed of two servers, and the second server group may be composed of three servers.

The management virtual machine integrates and manages multiple server local storages (3111, 3121, 3131, and 3141) according to the grouping information of the server group. For example, the management virtual machine determines the resource information of the local storage (3111, 3121, 3131, 3141) of the first to fourth individual servers (3110, 3120, 3130, 3140) and then stores it in one integrated storage (3111, 3121, 3131, 3141).

As an embodiment, the management virtual machine stores the data of the general virtual machine redundantly in the local storage (3111, 3121, 3131, 3141) within the server group (3101, 3102). For example, if there is a data write request from the first virtual machine located in the first server 3110 of the first server group 3101, the management virtual machine sends the data corresponding to the data write request of the first virtual machine to the first server group 3101. Not only is it stored in the first local storage 3111 of the first server 3110 where the virtual machine is located, but also the second local storage of the second server 3120 that exists in the same server group 3101 as the first server 3110 ( 3121).

As another example, the management virtual machine may store the metadata of the general virtual machine and the management virtual machine redundantly within the server groups 3101 and 3102. For example, metadata for the first virtual machine of the first server 3110 is stored in the first local storage 3111 of the first server 3110 and the second local storage 3121 of the second server 3120. It is stored redundantly. For example, when a virtual machine is created on each individual server (3110, 3120, 3130, 3140), each individual server (3110, 3120, 3130, 3140) is within the same server group (3101, 3102) according to server grouping information. Virtual machine meta information can be stored redundantly in each local storage (3111, 3121, 3131, 3141).

Since the general data and metadata of each virtual machine within the server group (3101, 3102) are stored redundantly, migration of the virtual machine within the server group (3101, 3102) can be performed quickly.

As an embodiment, the integrated storage (3111, 3121, 3131, 3141), which integrates the local storage (3111, 3121, 3131, 3141) of a plurality of individual servers (3110, 3120, 3130, 3140), includes a general virtual machine and General data and metadata of the management virtual machine are stored. General data refers to various data generated from virtual machine services, and metadata refers to various data that defines a virtual machine, such as virtual machine identifier, virtual machine IP address, and operating system. General data and metadata are redundantly stored in at least two server local storages (3111, 3121, 3131, and 3141) for each server group (3101, 3102).

As an embodiment, the data integration management module 310 includes one server group 3101, and the server group 3101 includes a first server 3110 and a second server 3120. A management virtual machine and first and second general virtual machines exist in the first server 3110, and third and fourth general virtual machines exist in the second server 3120.

Virtual machine migration may occur in the event of server maintenance or failure. For example, the management virtual machine can periodically send a ping signal to each server to check which server is experiencing a failure.

As an embodiment, when there is an inspection request for the first server 3110 or a failure occurs, the management virtual machine is first migrated from the first server 3110 to the second server 3120. And the first and second general virtual machines of the first server 3110 are migrated from the first server 3110 to the second server 3120. Since data is stored redundantly in the local storages (3111, 3121) of the first server (3110) and the second server (3120), migration can be completed quickly without separate data transmission and reception, enabling uninterrupted provision of virtual machine services. do.

When the inspection of the first server 3110 is completed or the problem is resolved, the general virtual machine can be migrated back to the first server 3110. At this time, since the data of the general virtual machine remains in the first server 3110, only data newly stored by the general virtual machine in the second server 3120 can be transmitted to the first server 3110.

As an embodiment, the first server group 3101 consists of the first server 3110 and the second server 3120, and the second server group 3102 consists of the third server 3130 and the fourth server 3140. ), and when an inspection or failure of the first server group (3101) occurs, the management virtual machine and general virtual machine existing in the first server group (3101) are each server (3130, Data migrated to 3140) and stored in local storages 3111 and 3121 of the first server group 3101 are stored in local storages 3131 and 3141 of the second server group 3102.

When the inspection of the first server group 3101 is completed or the problem is resolved, the general virtual machine can be migrated back to the first server group 3101. At this time, since the data of the general virtual machine remains in the first server group 3101, only data newly stored by the general virtual machine in the second server group 3102 can be transmitted to the first server group 3101.

Next, the network drive module 320 according to the present invention will be described.

The network drive module 320 according to the present invention includes a network drive server 3210, and the network drive server 3210 includes a drive agent unit 3211 and a shared storage unit 3213 as described above. .

Meanwhile, the network drive server 3210 can be connected to a plurality of user terminals 10 through a wired or wireless communication network. Additionally, the network drive server 3210 may be connected to each individual server 3110, 3120, 3130, and 3140 of the data integration management module 310.

The user requests a connection to the network drive server 3210 using the user terminal 10, and the user terminal 10 connects to each storage or shared storage unit of the shared storage unit 3213 included in the network drive server 3210. Data in the local storage (3111, 3121, 3131, 3141) of each individual server (3110, 3120, 3130, 3140) included in the data integration management module (310) connected to (3213) can be provided and used as a network drive. .

The network drive server 3210 includes a drive agent unit 3211 and a shared storage unit 3213.

The drive agent unit 3211 transmits and receives data between the network drive server 3210 and a plurality of user terminals 10. The shared storage unit 3213 includes a storage space provided as a network drive according to the user of the user terminal 10. In this case, the storage space is stored in each individual server 3110, 3120, and 3120 included in the data integration management module 310. It may be a local storage (3111, 3121, 3131, 3141) of 3130, 3140). Hereinafter, the description will be made assuming that the data stored in the local storage (3111, 3121, 3131, 3141) is stored in the shared storage unit 3213, but the shared storage unit 3213 itself is stored in the data integration management module 310 described above. It can also be interpreted to mean each local storage (3111, 3121, 3131, 3141).

The user terminal 10 according to the present invention is a typical computing terminal used by a user, such as a PC, laptop, netbook, tablet PC, PDA, mobile, or smartphone. The user terminal 10 is equipped with a local storage medium (not shown) for storing data, and a local operating system (OS, not shown) for the terminal is installed and operated in the user terminal 10.

The local operating system (OS) for the terminal provides a data explorer to explore data such as data stored in the local storage medium for the terminal. Data Explorer is a window-type GUI (graphical user interface) type explorer that displays the directory structure in a folder-type hierarchy. Additionally, the local operating system (OS) for the terminal mounts the storage medium as a drive and allows data to be searched using a directory structure.

In other words, in addition to the local storage medium for the terminal, external storage media or storage space on the network can be mounted as a drive. In general, when a storage medium of another computer terminal connected on a network is connected as a drive, it is called a network drive.

The network drive server 3210 according to the present invention provides data in local storages 3111, 3121, 3131, and 3141 stored in the shared storage unit 3213 or connected to the shared storage unit 3213 to the user terminal 10. do.

The network drive server 3210 allows multiple users to perform collaborative work by sharing one data. In other words, when one user checks out the data to use it, the data is set to locked to prevent other users from modifying the data. Additionally, when a user finishes using the data and checks in, the lock state of the data is released so that other users can use and modify the data.

The network drive server 3210 stores and manages data in the shared storage unit 3213. The shared storage unit 3213 includes a known database, storage, and/or repository.

Meanwhile, data stored or connected to the shared storage unit 3213 is managed and accessed through the network drive server 3210, or is stored in each local storage unit 3111, 3121, and As 3131 and 3141) are approached, data will be stored and managed in the network drive server 3210 without mention of the shared storage unit 3213.

The network drive server 3210 according to the present invention further includes a drive agent unit 3211 that allows the user terminal 10 to access data managed by the network drive server 3210.

In particular, the drive agent unit 3211 allows the shared storage unit 3213 to be accessed in the form of a network drive from the user terminal 10. To this end, the drive agent unit 3211 converts the data stored in the shared storage unit 3213 to the data system of the operating system of the user terminal 10 (or local operating system for the terminal). The drive agent unit 3211 mounts the converted data system as a network drive of the local operating system for the terminal and provides it. In other words, the drive agent unit 3211 provides a data sharing server function that allows the user terminal 10 to share data through a network drive of the local operating system for the terminal.

The network drive server 3210 converts the data stored in the shared storage unit 3213 to correspond to the data system structure of the local operating system for the terminal provided by the user terminal 10. In detail, the drive agent unit 3211 requests the shared storage unit 3213 for a list of data stored in the shared storage unit 3213 and receives the list of data. The received data list is assigned a unique identifier (or data ID) for each data, and when specific data is selected, the contents of the specific data can be requested and received from the shared storage unit 3213 through the unique identifier of the specific data. .

The terminal local operating system of the user terminal 10 uses a data sharing protocol to share data stored in the shared storage unit 3213 connected to the network. At this time, the data sharing protocol is a protocol for handling data stored in another computer terminal through the same interface as the data explorer of one's computer terminal. That is, when the user terminal 10 mounts the shared storage unit 3213 as a drive through the data sharing protocol, data can be managed through the same interface as if a local storage medium for the terminal was mounted. As an example, when the local operating system for the terminal is Microsoft's Windows, the data sharing protocol is the Samba (SMB) protocol.

The drive agent unit 3211 provides a data sharing server function according to the data sharing protocol, requests mount of the shared storage unit 3213 from the user terminal 10 to the drive agent unit 3211, and drives the drive agent unit 3211. ) mounts a network drive with a data system structure corresponding to the data list.

The user terminal 10 includes an interface unit 11 that extends the shell of the data explorer of the local operating system for the terminal. The interface unit 11 processes the unique functions of the network drive server 3210 in addition to the data system functions of the local operating system for the terminal. In other words, it processes the data collaboration performance function of the network drive server 3210 described above.

The shell of the data explorer of the local operating system for the terminal is an interface program for processing user commands. For example, when you double-click a specific folder in the data explorer using the shell, you move to that folder, or when you select specific data or folder, a context menu related to the selected data is displayed.

The interface unit 11 extends the shell of the data explorer and receives information about data sharing (hereinafter referred to as sharing information) from the drive agent unit 3211 and displays it as a context menu. Additionally, the extended shell provided by the interface unit 11 performs tasks such as displaying the lock status as a context menu when data is being edited by another user, or briefly displaying all version information of the data.

Additionally, the extended shell displays the unique functions of the network drive server 3210 as a context menu, and when the menu is selected from the context menu, the command is transmitted to the drive agent unit 3211. The drive agent unit 3211 interprets the command and transmits necessary data to the user terminal 10 according to the command.

Meanwhile, when shared information is received from the drive agent unit 3211 in the extended shell, the shared information is transmitted and received by the data sharing protocol. If the local operating system for the terminal is Microsoft's Windows, shared information is transmitted by an NTFS stream, a type of alternate data stream (ADS).

The drive agent unit 3211 establishes a data sharing session with the user terminal 10 through a data sharing protocol and shares data in the form of a local data system. That is, the drive agent unit 3211 shares data in the shared storage unit 3213 of the network drive server 3210 in the form of a local data system.

As explained earlier, the data sharing protocol is a protocol for handling data stored in other computer terminals through the same interface as the data explorer of one's own computer terminal. When a storage medium connected to the network is mounted as a drive, it is as if it were a local storage medium for the terminal. You can manage data using the same interface as the mounted one. If the local operating system for the terminal is Microsoft's Windows, the data sharing protocol is the Samba (SMB) protocol.

The drive agent unit 3211 functions as a data sharing server according to the data sharing protocol. In the case of Windows, the drive agent unit 3211 performs the function of a SMB server, mounts the data of the network drive server 3210 in the form of a network drive and shares it as shared data on the network. That is, the drive agent unit 3211 connects the data sharing session to the network drive.

The drive agent unit 3211 transmits information regarding data sharing (hereinafter referred to as sharing information) to the interface unit 11 and receives a command regarding data sharing (hereinafter referred to as sharing command) from the interface unit 11.

The interface unit 11 displays data sharing information as a data context menu. At this time, the sharing information includes a sharing command, and the interface unit 11 transmits the sharing command selected by the context menu to the drive agent unit 3211.

Next, we explain the data sharing function among the unique functions of data management. Functions for sharing data include functions such as check-in/check-out and data locking.

When data is modified, it is stored by version by the network drive server 3210. The interface unit 11 displays version-specific information about data as shared information.

When the interface unit 11 selects a specific version of the data and requests reception, the drive agent unit 3211 retrieves the data of the specific version stored in the network drive server 3210 and transmits it to the user terminal 10.

Data can be shared by multiple users and modified by each user. At this time, if multiple users modify and save data at the same time, only the data of the user who finally saved may be saved, and the data of other users may not be saved. Therefore, only one user should be able to modify data at a specific time. For this purpose, check-in/check-out is provided.

The drive agent unit 3211 sets the data to a locked state where it cannot be modified when the checkout sharing command is selected among the data sharing information through the interface unit 11, and locks the data when the checkin sharing command is selected. ) Release the state. In other words, when data is set to a locked state, subsequent users cannot access the data, and when a user issues a checkout command for specific data, the data is locked. Therefore, other users cannot view specific data. When the user completes modifying the data, he or she saves the data.

Meanwhile, as described above, if an inspection or failure occurs in any of the individual servers (3110, 3120, 3130, 3140) containing the data desired by the user, that is, for example, the data a that the user wishes to access is 1 It is located in the first local storage 3111 of the server 3110, and the interface unit 11 of the user terminal 10 wants to receive data located in the first server 3110 through the drive agent unit 3211, A data reception request signal is transmitted, and at this time, if an inspection or failure occurs in the first server 3110, the drive agent unit 3211 is not the first server 3110 connected to the shared storage unit 3213. Data a contained in the second local storage 3121 of the second server 3120, which is the same server group 3101 as (3110), can be provided to the user terminal 10. Therefore, the data management server 300 according to the present invention can guarantee the stability of data use.

Next, the backup module 330 according to the present invention will be described.

The backup module 330 according to the present invention includes a backup server 3310, and the backup server 3310 includes a backup agent unit 3311 and a backup storage unit 3317, as described above.

The backup agent unit 3311 includes a backup program, and when the backup program is executed, the backup target in the local storage (3111, 3121, 3131, 3141) of the individual server (3110, 3120, 3130, 3140) according to a preset schedule. Data is designated and formed as backup data based on the designated backup target data. The backup agent unit 3311 transmits the formed backup data to the backup storage unit 3317. Meanwhile, the backup program may be provided and executed on the user terminal 10 or may be automatically executed by the backup unit 3113, 3123, 3133, and 3143 of the data integration management module 310. As the backup program is provided to the user terminal 10, the user terminal 10 can specify a backup schedule through the backup program. Meanwhile, the backup program is provided through an administrator terminal (not shown) owned by a separate server administrator, and a backup schedule may be specified by the administrator terminal. Additionally, when the backup program is executed by the backup unit (3113, 3123, 3133, 3143), the backup schedule can be automatically specified by the backup unit (3113, 3123, 3133, 3143). Backup schedule designation for the backup units 3113, 3123, 3133, and 3143 will be described later.

The backup target data is data created, deleted, and modified by the user terminal 10 or individual servers (3110, 3120, 3130, 3140) and is stored within the user terminal 10 or individual servers (3110, 3120, 3130, 3140). It can be a data file that can be processed in .

The backup storage unit 3317 receives and stores backup data from the individual servers 3110, 3120, 3130, and 3140 through the backup agent unit 3311.

When storing backup data, the backup storage unit 3317 creates a copy of the backup data and stores it separately from the original to prepare for the case where the original backup data is damaged or cannot be used.

The backup server 3310 executes backups according to a set schedule, detects whether the set capacity among the accumulated backup data is exceeded, compares the creation date of the backup data, and deletes the excess capacity portion of the data created first to spare. By designing it to continuously secure disk space, it automatically performs backups after the data management server 300 is in operation, and when disk space is insufficient due to accumulated data, disk space is secured by automatically determining whether the set capacity has been exceeded.

The backup server 3310 generates a plurality of backup data and stores them individually so that the original data can be selectively recovered from the accumulated backup data even if the corresponding backup data is damaged.

Figure 10 is a diagram showing each configuration of the backup agent unit 3311 according to the present invention.

Referring to FIG. 10 , the backup agent unit 3311 includes a backup memory unit 3312, a backup input unit 3313, a backup control unit 3314, and a backup display unit 3315.

In the backup memory unit 3312, the backup program provided to the user terminal 10, the administrator terminal, or the backup unit 3113, 3123, 3133, and 3143 is stored, and is received from the user terminal 10 or the administrator terminal or is stored in the backup unit. Settings such as the backup schedule automatically set by (3113, 3123, 3133, 3143), multiple backup data folders, backup pre-task processor, backup post-task processor, and whether to terminate the backup after completion are saved.

The backup input unit 3313 receives the backup program execution command, backup time, process or service to be terminated before running the backup program, and operation of the backup program from the user terminal 10 or the backup unit (3113, 3123, 3133, 3143). It receives a process or service to be executed after termination, a predetermined number of folders for storing backup data, and whether the backup agent unit 3311 will be automatically terminated after backup.

The backup control unit 3314 reads the backup program execution command and backup schedule received by the backup input unit 3313 from the user terminal 10, the administrator terminal, or the backup unit 3113, 3123, 3133, and 3143, and executes the backup schedule according to the read schedule. Accordingly, the backup target data within the individual servers (3110, 3120, 3130, and 3140) is designated, the designated backup target data is formed as backup data, and the formed backup data is delivered to the backup storage unit 3317.

As an embodiment, when forming designated backup target data into backup data, the backup control unit 3314 not only forms the original backup target data into backup data, but also compresses the backup target data to form backup data. By reducing the capacity of the backup data and delivering it to the backup storage unit 3317, the storage space of the backup storage unit 3317 can be utilized more efficiently. The backup control unit 3314 allocates a permanent memory space for permanently storing backup data and a general memory space for storing backup data other than permanent storage to the backup storage unit 3317, and checks whether the formed backup data is permanently stored. And, if the created backup data needs to be stored permanently, it is stored in a permanent memory space.

As an embodiment, the backup control unit 3314 exceeds the set capacity of the backup data accumulated in the backup storage unit 3317, and when deleting the excess portion, only the backup data stored in the general memory space is deleted and the backup data stored in the permanent memory space is deleted. By not deleting backup data separately stored in , it is possible to prevent data that must be retained by the user from being deleted.

The backup display unit 3315 displays the operating status of the backup program run by the backup control unit 3314 on the display device of the user terminal 10 or the administrator terminal.

As an embodiment, the backup display unit 3315 displays the operating status of the backup program on the taskbar on the user terminal 10 or the administrator terminal (for example, in the case of a Windows PC, the taskbar at the bottom of the screen, etc.). It can be displayed.

As an embodiment, the backup display unit 3315 displays a settings window for entering settings for the backup program (for example, backup time or a process or service to be terminated before running the backup program, etc.) on the user terminal (10). ) can be displayed on the display device.

As an embodiment, the backup display unit 3315 displays the backup program to the user through a pop-up window (i.e., a new window that is suddenly created to display certain contents of a specific website) after the backup program starts or ends. Not only can the driving status be informed by visual means, but also by auditory means through sound reproduction means (for example, external speakers or built-in speakers, etc.) provided in the user terminal 10 or the administrator terminal. The running status of the backup program can also be notified to the user.

The backup control unit 3314 transmits backup data to the backup storage unit 3317.

The backup control unit 3314 sets a standard capacity for deleting the backup data previously stored in the backup storage unit 3317 and stores it in the backup memory unit 3312, and stores the backup data stored in the backup storage unit 3317. The capacity is read, and the reference capacity read from the backup memory unit 3312 is compared with the capacity of the backup data stored in the backup storage unit 3317. As a result of the comparison, the backup control unit 3314 determines that when the capacity of the backup data stored in the backup storage unit 3317 exceeds the standard capacity, the backup data created first among the backup data stored in the backup storage unit 3317 exceeds the set capacity. You can delete as much as one part.

As an embodiment, the backup control unit 3314 determines that the capacity of the backup data stored in the backup storage unit 3317 is set to a certain percentage of the available storage capacity of the backup storage unit 3317 (for example, the amount of backup data stored in the backup storage unit 3317 When the available storage capacity (80%) is exceeded, the creation date among the backup data stored in the backup storage unit 3317 is compared and the portion of the data created earlier that exceeds the capacity is deleted, so that the backup storage unit 3317 It can be used to create available storage space for newly incoming backup data.

As an embodiment, when deleting backup data stored in the backup storage unit 3317, the backup control unit 3314 deletes a predetermined capacity (for example, 10% of the available storage capacity of the backup storage unit 3317, etc.) The backup storage unit 3317 can secure available storage space for the newly incoming backup data by deleting or deleting an amount equivalent to the newly incoming backup data capacity.

As an embodiment, the backup control unit 3314 stores data other than backup data in the backup storage unit 3317 (for example, video data or image data stored according to the needs of a user or administrator). , By reading the standard capacity based on the combined capacity of data other than backup data and the backup data, it is possible to prevent the case where available storage space for newly incoming backup data becomes insufficient.

When the backup time is input from the backup input unit 3313 and a backup time reservation request is received, the backup control unit 3314 sets the backup time input according to the backup time reservation request in the backup memory unit 3312.

As an embodiment, the backup control unit 3314 can provide work convenience by allowing the backup program to run at the same time every day when setting the backup time.

When the backup control unit 3314 receives a designated folder name for storing backup data in a pre-designated folder from the backup input unit 3313 and receives a request for designated backup settings, the backup control unit 3314 returns the designated folder name entered according to the designated backup setting request. Set in the backup memory unit 3312.

When performing a designated backup, the backup control unit 3314 can store separate backup data for each designated folder and can also allow each folder to be backed up at a different time.

The backup control unit 3314 performs a backup operation of a designated data folder and then adds the date and time to the set value of the folder name where the backup data is stored and stores it, thereby preventing the same folder name from being used during daily cumulative backup and preventing the user from using the same folder name. When restoring backed up data, you can selectively restore it by distinguishing the date and time the backup was created.

When the backup control unit 3314 receives a plurality of folder names for storing a predetermined number of backup data in a predetermined folder from the backup input unit 3313 and receives a request for setting up multiple backups, the backup control unit 3314 responds to the request for setting up multiple backups. Multiple input folder names can be set in the backup memory unit 3312.

Meanwhile, the backup unit (3113, 3123, 3133, 3143) according to the present invention analyzes the load of each individual server (3110, 3120, 3130, 3140) according to the data management server 300 according to the present invention, and stores the data. A backup schedule can be specified by inputting the day and time of day when the management server 300 has the lowest load into the backup input unit 3313.

At this time, the server load analysis of the backup unit (3113, 3123, 3133, 3143) is, for example, the number of user terminals 10 connected to each server of the data integration management module 310 through the network drive module 320. Alternatively, the number of data request messages sent by the interface unit 11 of the user terminal 10 to the drive agent unit 3211 may be comprehensively analyzed. At this time, the number of connected user terminals 10 and the number of data request messages may be derived by analyzing the log in the data management server 300.

The backup units 3113, 3123, 3133, and 3143 continuously analyze the degree of past server load and transmit the analysis results to the backup control unit 3314.

Figure 11 is a diagram showing an embodiment of a server load diagram according to the present invention.

Referring to FIG. 11, the backup control unit 3314 organizes the degree of server load received from the backup units 3113, 3123, 3133, and 3143 in the form of a plurality of cells divided by day of the week and time zone to determine the server load. Create a diagram. At this time, the cell may be in the form of a plurality of consecutive squares. The server load diagram generated by the backup control unit 3314 may be displayed on the user terminal 10 or the administrator terminal by the backup display unit 3315 and provided to the user or administrator.

The backup control unit 3314 can display a plurality of cells differently depending on the degree of server load. For example, when the server load is low, the cells are colored darkly, and when the server load is large, the cells are colored lightly to display the backup. Unit 3315 can be displayed on the user terminal 10. Meanwhile, the coloring of cells according to each day and time of the server load diagram may have a coloring value according to the degree of server load corresponding to the average value of the degree of server load for days and times of multiple weeks. Alternatively, the server load diagram according to one embodiment may represent the degree of server load in the form of a square pillar with the aforementioned cell as the bottom, and in this case, the degree of server load may be the height of the square pillar. The backup display unit 3315 can display a server load diagram with square column-shaped cells on the user terminal 10.

Meanwhile, in FIG. 11, the horizontal length of each cell is shown to mean 1 hour as an example. For convenience, only the time from 0:00 AM to 12:00 AM and midnight to noon is shown, but the server load is also The shape of each cell can be changed at any time depending on the embodiment. Meanwhile, the backup units 3113, 3123, 3133, and 3143 can track and analyze not only the past server load, but also the time required for backup.

The backup control unit 3314 generates a straight line connecting the centers of cells according to the time zone with the lowest load for each day of the week in the server load chart organized in the form of a plurality of cells, and calculates the length of the generated straight line. .

If the time required to back up data in the data management server 300 according to the present invention ends within the time of a single cell, as an example, within one hour, such as the horizontal length of the cell shown in FIG. 11, the backup control unit ( 3314) determines that past backup times did not take long.

If it is determined that the backup time will not take a long time, the backup control unit 3314 selects the day and time zone with the shortest length among the lengths of the straight line connecting the center of the cell corresponding to the low load time zone, and selects the day and time zone. You can execute a backup by automatically specifying a backup schedule by entering it into the backup input unit 3313.

For example, as shown in Figure 11, the length of the line segment connecting the center of each cell at 5 AM on Tuesday and Wednesday is 1, and the length of the line segment connecting the center of each cell at 4 AM on Thursday and Friday is 1. If is 1, you can specify a backup schedule to perform backups at 5 a.m. on Tuesdays and Wednesdays and at 4 a.m. on Thursdays and Fridays.

If the past backup time does not take a long time, the backup control unit 3314 finds the length of a line segment connecting consecutive low-load times and selects the one with the shortest length. This is because if the same time zone with a short distance is continuous, the accuracy can be guaranteed that the load in that time zone is low.

Meanwhile, the backup input unit 3313 can receive the backup time zone from the user terminal 10 or the administrator terminal, and the backup time zone input from the user terminal 10 or the administrator terminal is the same according to the operation of the backup control unit 3314. When a line segment of length is derived, the time zone closest to the input backup time zone can be designated as the backup schedule. That is, if the backup time input from the user terminal 10 or the administrator terminal is 2:00 AM, backup is performed between 5:00 AM on Tuesday and Wednesday and 4:00 AM on Thursday and Friday when the line segment length is 1, as shown in Figure 11. The control unit 3314 can specify a backup schedule by specifying the backup time zone as 4 AM on Thursday and Friday. In this way, if the backup time zone is input from the user terminal 10 or the administrator terminal and one of the days and time zones with the same line segment length is selected, the backup schedule can be set to perform backup at the specified time zone on other days of the week, that is, at 4 am. You can.

On the other hand, unlike the above, if the time required to back up data in the data management server 300 does not end within the time of a single cell, as an example, within one hour according to the horizontal length of the cell shown in FIG. 11 , the backup control unit 3314 determines that the past backup time took a long time.

Figure 12 is a diagram showing another embodiment of a server load diagram according to the present invention.

In this case, when it is determined that the past backup time took a long time, the backup control unit 3314, referring to FIG. 12, calculates the distance of the line segment connecting the centers of the cells in the continuous low-load time zone. This is because the longer the length of the line segment obtained by the backup control unit 3314, the less load can be placed on each individual server (3110, 3120, 3130, and 3140) within the data management server 300 due to backup.

When the backup control unit 3314 continuously selects cells in the time zone with low load, it first derives the cell in the time zone with the lowest load on each day of the week, and then derives the cell in the time zone with the lowest load after that cell. At this time, when the cell in the lowest load time zone and the cell in the next lowest load time zone are adjacent to each other, the backup control unit 3314 connects the centers of the two adjacent cells. Again, the backup control unit 3314 derives the cell in the next low-load time period and determines whether the derived cell is adjacent to both cells whose centers are connected by a line segment. If the derived cell is adjacent to both cells whose centers are connected by a line segment, the centers are connected again, and if it is not adjacent to both cells, the backup control unit 3314 no longer derives the low-load time for the corresponding day of the week.

As described above, when the backup time takes a long time, the center of each cell derived by the backup control unit 3314 is connected as shown in FIG. 12. At this time, the backup control unit 3314 derives how long the past backup time took, and compares the derived backup time with the length of the line segment connecting the center of each cell. If the derived backup time is 2 to 3 hours, backups are performed on Wednesday and Friday in FIG. excluded from the schedule. This is determined to be excluded because the length of the line segment between the centers of each cell on Wednesday and Friday in FIG. 12 is 2. In addition, 2 AM to 6 AM on Monday, 2 AM to 5 AM on Tuesday, 3 AM to 6 AM on Thursday, and 9 AM to Saturday, including all 2 to 3 hours of the derived backup time. The backup control unit 3314 specifies a backup schedule so that backups are performed at 12:00 AM and between 5:00 AM and 11:00 AM on Sundays, respectively.

Meanwhile, as described above, the backup input unit 3313 can receive a backup time zone from the user terminal 10, and the time zone at which the backup starts can be determined according to the backup time zone input from the user terminal 10. For example, if the backup time input from the user terminal 10 is 2 a.m., backup starts at 2 a.m. on Monday and Tuesday, and on Thursday, backup starts at 3 a.m. closest to the input time zone. Backups can start at 9:00 AM on Saturdays and 5:00 AM on Sundays. On the other hand, if the backup time input from the user terminal 10 is 7 a.m., the backup starts at 3 a.m. on Monday so that the backup can be completed at the time closest to 7 a.m., and on Tuesday the backup starts at 2 a.m. The backup schedule can be set to start at 3:00 AM on Thursday, 9:00 AM on Saturday, and 5:00 AM on Sunday.

Figure 13 is a diagram showing another embodiment of a server load diagram according to the present invention.

Meanwhile, the horizontal length of the cell within the server load may change depending on the time zone input from the user terminal 10 or the administrator terminal. In other words, a weight can be given to the horizontal length of the cell according to the time zone input by the user terminal 10 or the administrator terminal. For example, if the time zone entered by the user terminal 10 or the administrator terminal is 5 a.m., the horizontal length corresponding to 5 a.m. in the server load may be modified to be twice that amount. When the horizontal length is changed like this, the length of the line segment passing through the center of the cell corresponding to 5 AM is also given a weight of 2, which is an increase of 1. For example, as shown in FIG. 13, as the horizontal length of the cell corresponding to 5 a.m. is doubled, the length of the line segment connected to the center of 5 a.m. also increases, and the backup control unit 3314 increases in length. The above-described calculation is performed based on the line segment. Therefore, the backup schedule can be specified in consideration of the time zone input from the user terminal 10 or the administrator terminal. In the case of Friday, because the length of the line segment in FIG. 12 was 2, backup was not performed on Friday, as in FIG. 13. Likewise, as the horizontal length of the cell corresponding to 5 a.m. increases, the line segment length for Friday becomes 3, so the backup schedule can be changed so that backup is performed on Friday as well.

Meanwhile, the time zone input from the user terminal 10 or the administrator terminal can receive multiple time zones with priorities, and each time zone has a horizontal length of 5 times, 4 times, 3 times, 2 times, etc. depending on the priority. After lengthening, a backup schedule can be specified according to the length of the line segment connecting the center of each cell.

The backup control unit 3314 may check whether the backup program stored in the backup memory unit 3312 is genuine when executing the backup program, and may stop execution of the backup program if the backup program is not genuine.

When executing a backup program, the backup control unit 3314 reads a specific key value stored in the backup storage unit 3317 and compares it with the key value of the backup program stored in the backup memory unit 3312. If the two compared values are different, In this case, an error message is displayed and the execution of the backup program is stopped, preventing illegal copying of the backup program and protecting the rights of the program developer.

The backup control unit 3314, which has the above-described configuration, can store the characteristic key value of the hard disk to determine whether the program is genuine and determine whether to execute it to protect copyright.

The user terminal 10 or administrator terminal according to the present invention is a terminal such as a desktop PC, laptop PC, tablet PC, or smartphone equipped with an input means such as a keyboard, mouse, touchpad, or touch screen, and a display screen. It is not limited, and it is possible to connect to the modular maritime traffic congestion prediction server 100, the interface unit 110, the data management server 300, and/or the network drive server 3210 of the network drive module 320 through a communication network. Any configuration capable of processing digital information that can input search information and selection information and install an application program that can display search result information may be included. The user terminal 10 or administrator terminal according to the present invention is a network drive server ( 3210) is a component that transmits and receives information by connecting to a communication network, such as a smartphone, tablet personal computer, mobile phone, video phone, desktop personal computer, and laptop. Laptop personal computer (PC), netbook computer, personal digital assistant (PDA), portable multimedia player (PMP), wearable device (e.g. smart glasses, head-mounted-device) (HMD, etc.), an unmanned terminal (kiosk), or a smart watch).

The user terminal 10, manager terminal, modular maritime traffic congestion prediction server 100, intelligent maritime traffic information server 200, data management server 300 and their respective detailed components according to the present invention include a communication unit each provided. and can communicate through a communication network. A communication network refers to a connection structure that allows information exchange between nodes such as terminals and servers. Examples of such communication networks include the 3rd Generation Partnership Project (3GPP) network, Long Term Evolution (LTE) network, and 5G. Network, WIMAX (World Interoperability for Microwave Access) network, Internet, LAN (Local Area Network), Wireless LAN (Wireless Local Area Network), WAN (Wide Area Network), PAN (Personal Area Network), wifi network, It includes, but is not limited to, a Bluetooth network, a satellite broadcasting network, an analog broadcasting network, and a Digital Multimedia Broadcasting (DMB) network. The communication unit provided with the user terminal 10, the administrator terminal, the modular maritime traffic congestion prediction server 100, the intelligent maritime traffic information server 200, the data management server 300, and their respective detailed components is the aforementioned communication network. It may include electronic components provided for the communication network so as to perform wired and wireless data communication.

In this specification, the modular maritime traffic congestion prediction server 100, the intelligent maritime traffic information server, the data management server 300, and their respective detailed components may be processors that execute sequential execution processes stored in memory. Alternatively, they may operate as software modules driven and controlled by a processor. Furthermore, a processor may be a hardware device.

The first to fourth local storage units 3111, 3121, 3131, and 3141, the shared storage unit 3213, and the backup storage unit 3317 according to the present invention may include a database management system (hereinafter referred to as DBMS). DBMS is a set of software tools that allow multiple users to access data in a database. DBMS includes IMS, CODASYL DB, DB2, ORACLE, INFORMIX, SYBASE, INGRES, MS-SQL, Objectivity, O2, Versanat, Ontos, Gemstone, Unisql, Object Store, Starburst, Postgres, Tibero, MySQL or MS-access. can do. DBMS allows access to specific data depending on the input of a specific command.

In this specification, 'part' includes a unit realized by hardware, a unit realized by software, and a unit realized using both. Additionally, one unit may be realized using two or more pieces of hardware, and two or more units may be realized using one piece of hardware.

The scope of protection of the present invention is not limited to the description and expression of the embodiments explicitly described above. In addition, it is to be added once again that the scope of protection of the present invention may not be limited due to changes or substitutions that are obvious in the technical field to which the present invention pertains.

10: user terminal 11: interface unit
100: Modular maritime traffic congestion prediction server
110: Interface unit 120: Congestion calculation unit
121: Congestion calculation module 1211: Actual maritime traffic calculation module
1213: Practical traffic capacity calculation module 130: Congestion prediction unit
131: Congestion prediction module 200: Intelligent marine traffic information server
300: Data management server 310: Data integration management module
3101: 1st server group 3102: 2nd server group
3110: first server 3111: first local storage
3113: Backup unit 3120: Second server
3121: Second local storage 3123: Backup unit
3130: Third server 3131: Third local storage
3133: Backup unit 3140: Fourth server
3141: Fourth local storage 3143: Backup unit
320: network drive module 3210: network drive server
3211: Drive agent unit 3213: Shared storage unit
330: Backup module 3310: Backup server
3311: Backup agent unit 3312: Backup memory unit
3313: Backup input unit 3314: Backup control unit
3315: Backup display unit 3317: Backup storage unit
1000: Modular maritime traffic congestion prediction system

Claims (5)

In a modular maritime traffic congestion prediction system that calculates and predicts maritime traffic congestion,
The modular maritime traffic congestion prediction system is,
It includes a modular maritime traffic congestion prediction server that receives maritime traffic data from an intelligent maritime traffic information server and calculates and predicts the maritime traffic congestion,
The modular maritime traffic congestion prediction server,
An interface unit that receives the maritime traffic data from the intelligent maritime traffic information server;
A congestion calculation unit that calculates maritime traffic congestion based on the maritime traffic data; and
a congestion prediction unit that predicts future maritime traffic congestion based on the maritime traffic congestion calculated by the congestion calculation unit;
A modular maritime traffic congestion prediction system comprising: In claim 1,
The congestion calculation unit includes one or more congestion calculation modules,
The congestion calculation module is,
An actual maritime traffic volume calculation module that calculates the actual maritime traffic volume for a specific gate line based on the maritime traffic data; and
A practical traffic capacity calculation module that calculates the basic traffic capacity for a specific gate line and calculates the practical traffic capacity based on the calculated basic traffic capacity;
Includes,
The congestion calculation module is,
A modular maritime traffic congestion prediction system, characterized in that the maritime traffic congestion is calculated as expressed in Equation 1 below based on the actual maritime traffic volume and the practical traffic capacity.

<Formula 1> In claim 2,
The actual maritime traffic calculation module is,
A modular maritime traffic congestion prediction system, characterized in that the actual maritime traffic volume is calculated by multiplying the L-squared conversion coefficient and the number of ships. In claim 3,
The practical traffic capacity calculation module calculates the basic traffic capacity by dividing the product of the route width and the average ship speed in the route by the size of the vessel's blockage area, and calculates the basic traffic capacity by multiplying the practical traffic capacity ratio. A modular maritime traffic congestion prediction system characterized by calculation based on practical traffic capacity. In claim 1,
The maritime traffic data is a modular maritime traffic congestion prediction system, characterized in that it includes AIS dynamic information and static information.

Images