KR102469283B1 - Portable uv-led curing apparatus - Google Patents

Abstract

The present invention relates to a portable UV-LED curing device, in which an UV-LED irradiator that irradiates ultraviolet rays is provided in the form of a handgun, so as to make an ultraviolet curing operation easier. The portable UV-LED curing device according to the present invention comprises: an UV-LED irradiator which irradiates ultraviolet rays; and a power supply device which is connected to the UV-LED irradiator via a cable and supplies power to the UV-LED irradiator. The UV-LED irradiator includes: a head part including an UV-LED module which irradiates ultraviolet rays toward an open front; and a handle part coupled to a lower portion of the head part and allowing a user to grip the UV-LED irradiator like a handgun.

Description

Portable UV-LED curing device {PORTABLE UV-LED CURING APPARATUS}

The present invention relates to a portable UV-LED curing device, and more particularly, to a portable UV-LED curing device in which a UV-LED irradiator for irradiating ultraviolet rays is formed in a handgun type so that ultraviolet curing work is easier.

Ultraviolet paint is an ultraviolet (ultraviolet: UV) curable material, which causes a photochemical reaction by ultraviolet energy (100 ~ 400nm) to form a coating film from a liquid phase and cures it into a solid phase.

UV paints are widely used due to their excellent environmental friendliness, economy and workability, and together with this, UV curing devices for rapidly curing UV paints are also widely used.

Existing UV curing devices are mostly large and expensive devices used in industries, but in recent years, compact and portable UV curing devices that are easy to use have been developed.

This compact portable UV curing device includes a small UV-LED irradiator and a power supply supplying power to the UV-LED irradiator. On the other hand, most of the developed small UV-LED irradiators have a hexahedral shape with a handle, and have a problem in that the operator must hold the handle of the UV-LED irradiator before performing the work.

Republic of Korea Patent Registration No. 10-1649931 (Announced on August 23, 2016) Republic of Korea Patent Registration No. 10-2215802 (notice on February 15, 2021)

An object of the present invention for solving the above problems is to provide a portable UV-LED curing device including a handgun type UV-LED irradiator.

In order to achieve the above object, a portable UV-LED curing device according to an embodiment of the present invention is connected to a UV-LED irradiator and the UV-LED irradiator through a cable to irradiate ultraviolet rays to the UV-LED irradiator It includes a power supply unit for supplying power, and the UV-LED irradiator is coupled to a head portion including a UV-LED module for irradiating ultraviolet rays toward an open front and a lower portion of the head portion, and the user can use the hand It includes a handle that can be gripped in a gun type.

The UV-LED module includes a substrate on which a UV-LED chip emitting ultraviolet rays is mounted, and the substrate includes a plurality of substrates emitting ultraviolet rays of different wavelengths to cure a coating film from the inside to the surface. It includes a first substrate and a second substrate on which UV-LED chips are mounted, and a plurality of UV-LED chips emitting ultraviolet rays of 390 to 405 nm wavelength are mounted on the first substrate, and the second substrate , a plurality of UV-LED chips emitting ultraviolet rays of 360 to 370 nm wavelength are mounted.

The head unit is installed in front of the substrate, transmits ultraviolet light emitted from the UV-LED chip, and absorbs heat generated from the UV-LED module and the light emitting plate that protects the substrate and the UV-LED chip. It includes a heat sink that circulates air to dissipate the heat absorbed by the heat sink to the rear, and side openings for intake of air discharged by the heat sink.

The handle portion applies power supplied from the power supply device to the UV-LED module and the heat dissipation cooling fan by a user's pressurization, and includes an elastic body therein to release the application of the power when the pressurization is released; and A push button that maintains a state in which power supplied from the power supply device is applied to the UV-LED module and the heat dissipation cooling fan by a user's pressurization, and releases the application of the power by a user's pressurization again; In front of the head unit, when the UV-LED irradiator is mounted on the floor, a plurality of support members are provided to contact the ground and prevent damage to the head unit.

The power supply unit receives power from an external power source and supplies power to the UV-LED irradiator, a timer unit for receiving operation time information of the UV-LED module, and receiving the operation time information from the timer unit, , A control unit for controlling power supply to the UV-LED irradiator based on the operation time information.

According to the portable UV-LED curing device of the present invention, the UV-LED irradiator is formed in a handgun type, so that the operator can hold it with one hand and then cure the paint.

According to the portable UV-LED curing device of the present invention, including UV-LED chips of different wavelengths, there is an effect of suppressing the oxygen barrier effect as much as possible and completely curing from the inside to the surface of the coating film.

According to the portable UV-LED curing device of the present invention, there is an effect of discontinuously and continuously controlling the operation of the UV-LED, including a trigger for discontinuous operation and a push button for continuous operation.

According to the portable UV-LED curing device of the present invention, after the operating time set through the timer setting, the operation of the UV-LED can be controlled to be off.

According to the portable UV-LED curing device of the present invention, when the UV-LED irradiator is mounted on the floor, there is an effect of preventing damage to the head part by including a plurality of support members in contact with the ground.

1 is a view showing each configuration of a portable UV-LED curing device according to the present invention.
2 is a perspective view of a UV-LED irradiator according to the present invention.
3 is a view showing a substrate of a UV-LED module according to the present invention.
4 is a view showing the head part according to the present invention in detail.
5 is a rear view of a UV-LED irradiator according to the present invention.
6 is a block diagram showing each configuration of the power supply device according to the present invention.
7 is a perspective view of a UV-LED irradiator according to an embodiment of the present invention.
8 is a block diagram showing each configuration of a power supply, a server, and a user terminal according to an embodiment of the present invention.
9 is a diagram showing each module of the server according to the present invention.
10 is a diagram showing each configuration of a data integration management module according to the present invention.
11 is a diagram showing each configuration of a network drive module according to the present invention.
12 is a diagram showing each configuration of a backup module according to the present invention.
13 is a diagram showing each configuration of a backup agent unit according to the present invention.
14 is a diagram showing an embodiment of a server load diagram according to the present invention.
15 is a diagram showing another embodiment of a server load diagram according to the present invention.
16 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 exemplary drawings. In adding reference numerals to components of each drawing, it should be noted that the same components have the same numerals as much as possible, even if they are displayed on different drawings.

And, in describing the embodiments of the present invention, if it is determined that a detailed description of a related known configuration or function hinders understanding of the embodiments of the present invention, the detailed description will be omitted.

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

In this specification, the singular form also includes the plural form unless otherwise specified in the phrase. The terms "comprising" and/or "comprising" used in the specification do not exclude the presence or addition of one or more other components other than the recited components.

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

1 is a view showing each configuration of a portable UV-LED curing device 1000 according to the present invention, and FIG. 2 is a perspective view of a UV-LED irradiator 100 according to the present invention.

Referring to FIG. 1, a portable UV-LED curing device (1000, hereinafter referred to as a 'curing device') according to the present invention includes a UV-LED irradiator 100 and a UV-LED irradiator 100 for irradiating ultraviolet rays. A power supply 200 connected through a cable 201 to supply power to the UV-LED irradiator 100 is included. The curing device 1000 according to the present invention enables the UV-LED irradiator 100 to irradiate ultraviolet rays by transmitting power generated through the power supply device 200 to the UV-LED irradiator 100. The power supply 200 may have a handle for a separate power supply for movement on one side.

Referring to FIG. 2 , the UV-LED irradiator 100 according to the present invention includes a head part 110 and a handle part 120. The head part 110 includes a UV-LED module 111 for irradiating ultraviolet rays toward an open front 115 (front opening). Meanwhile, in the present specification, the direction in which the UV-LED module 111 is located in the head part 110, that is, the direction in which the irradiated object is located based on the head part 110 is referred to as the front, and in the head part 110, The direction in which the heat dissipating cooling fan 119 is located, which will be described later, is referred to as rear. The UV-LED module 111 radiates ultraviolet rays to an object to be irradiated. The head part 110 includes an accommodation space in which various electronic components such as the UV-LED module 111 can be accommodated. A front opening 115 is formed in front of the head unit 110, and ultraviolet rays emitted from the UV-LED module 111 included in the accommodation space pass through the front opening 115 and are disposed in front of the head unit 110. irradiated objects are investigated.

The head part 110 further includes a plurality of support members 101 protruding forward. The support member 101 comes into contact with the ground to prevent damage to the head 110 when a worker places the UV-LED irradiator 100 on the floor when the operator does not use the UV-LED irradiator 100 . The support member 101 may be made of a material having elasticity such as rubber.

3 is a view showing the substrate 112 of the UV-LED module 111 according to the present invention.

The UV-LED module 111 includes a substrate 112 on which a UV-LED chip emitting ultraviolet rays is mounted. The substrate 112 according to the present invention may be a printed circuit board having circuits printed on its surface.

On the other hand, referring to FIG. 3, the substrate 112 according to the present invention includes a plurality of UV-LED chips 1131 and 1141 emitting ultraviolet rays of different wavelengths to cure the coating film from the inside to the surface. Each includes a mounted first substrate 113 and a second substrate 114, and a plurality of UV-LED chips 1131 emitting ultraviolet rays having a wavelength of 390 to 405 nm are mounted on the first substrate 113. And, a plurality of UV-LED chips 1141 emitting ultraviolet rays of 360 to 370 nm wavelength are mounted on the second substrate 114 . On the other hand, for the uniformity of the ultraviolet light flux emitted from the UV-LED module 111, the plurality of UV-LED chips 1131 and 1141 may be spaced apart from each other at a uniform distance and mounted on the substrate 112.

In the photopolymerization-type radical reaction, oxygen in the air acts as a radical reaction inhibitor and hinders the curing of the surface of the coating film, which is called the oxygen barrier effect. By adding a UV-LED chip (1141) with a wavelength of 370 nm, the oxygen barrier effect is suppressed as much as possible, and the coating film is completely cured from the inside to the surface.

That is, the UV-LED module 111 according to the present invention includes a first substrate 113 and a second substrate on which UV-LED chips 1131 and 1141 having different wavelengths are grouped and mounted in the UV-LED module 111. (114). In this case, power is applied to the first substrate 113 and/or the second substrate 114 so that the UV-LED chips 1131 and 1141 having different wavelengths are turned on for each wavelength, so that conversion for each wavelength is possible, In addition, LEDs having different wavelengths are simultaneously turned on so that complete curing can be achieved from the inside to the surface of the coating film as described above.

4 is a view showing the head part 110 according to the present invention in detail, and FIG. 5 is a rear view of the UV-LED irradiator 100 according to the present invention.

Referring to FIG. 4 , the head unit 110 according to the present invention further includes a light emitting plate 116 installed in front of the UV-LED module 111 described above. The light emitting plate 116 transmits ultraviolet rays emitted by the UV-LED chip and protects the substrate 112 and the UV-LED chips 1131 and 1141 mounted on the substrate 112 . The light emitting plate 116 includes quartz glass made of a transparent quartz material. The light emitting plate 116 is installed in the front opening 115 formed in front of the head unit 110 .

That is, the UV-LED module 111 according to the present invention is installed inside the head part 110 so as to be adjacent to the light emitting plate 116, and emits ultraviolet rays toward the light emitting plate 116. In addition, a plurality of UV-LED chips 1131 and 1141 mounted on the substrate 112 are provided so as to correspond to the area of the front opening 115, and can emit ultraviolet rays to the entire front opening 115.

The head part 110 according to the present invention has a heat sink 117 that absorbs heat generated from the UV-LED module 111 therein, and circulates air to dissipate the heat absorbed by the heat sink 117. A heat dissipation cooling fan 119 (fan) discharging to the rear and a side opening 118 for intake of air discharged by the heat dissipation cooling fan 119 are further included.

The heat sink 117 includes a plurality of heat sinks, one end of each heat sink is in contact with the substrate 112 of the UV-LED module 111, and the other end of the heat sink extends toward the heat dissipation cooling fan 119. Air is introduced through the side openings 118 by the operation of the heat dissipating cooling fan 119, and the introduced air absorbs heat in the space between each heat dissipation plate of the heat sink 117, and the receiving space in the head part 110 5, the heat is discharged to the rear of the head unit 110 through the cooling fan 119.

The heat dissipation cooling fan 119 is installed on the rear side of the head unit 110 and sucks external air into the head unit 110 through the side opening 118 when driven, and mixes the introduced air with the heated head unit ( 110) The heated internal components of the head unit 110, particularly the heated UV-LED module 111, are cooled by exhausting the air heated by the heat exchange of the internal components to the outside.

Referring again to FIG. 2 , the handle part 120 according to the present invention is coupled to the lower part of the head part 110 so that the operator can grip it in a handgun type. A trigger 121 is formed on the front of the handle 120 and a push button 123 is formed on the side.

The trigger 121 is located in front of the handle part 120 so as to be pressed by the operator's index or stop. The trigger 121 moves to the inside of the handle part 120 by the operator's pressurization, and the power supplied from the power supply unit 200 is transferred to each component of the head part 110, that is, the UV-LED module 111 and heat dissipation cooling. This is a switch that generates a signal applied to the fan 119. The trigger 121 moves to the inside of the handle part 120 by the operator's pressurization, and then moves to the outside of the handle part 120 again when the operator's pressurization is released, and the UV-LED module 111 and heat dissipation cooling As the generation of the signal applied to the fan 119 is stopped, the application of the power supplied from the power supply device 200 is released. The trigger 121 may include an elastic body (not shown) therein so that the trigger 121 moves to the outside of the handle 120 again and returns to its original position when the operator's pressure is released. The trigger 121 includes each component of the known trigger 121 switch.

The push button 123 is located on the side, preferably the right side, of the handle 120 so as to be pressed by the operator's thumb. The push button 123 moves to the inside of the handle part 120 by the operator's pressurization and transmits a signal for applying the power supplied from the power supply 200 to the UV-LED module 111 and the heat dissipation cooling fan 119. switch that creates Meanwhile, the operation of the push button 123 is roughly distinguished from the trigger 121 . The push button 123 moves to the inside of the handle part 120 by the operator's pressurization, and even if the operator's pressurization is released, the power supplied from the power supply device 200 is applied to the UV-LED module 111 and the heat dissipation cooling fan. (119) continues to be applied. The push button 123 cancels the application of power when the operator presses it again.

The push button 123, for example, moves to the inside of the handle part 120 by the operator's pressurization and then does not move to the outside of the handle part 120 again even if the operator's pressurization is released. That is, the push button 123 does not return to its original position even when the pressurization of the operator is released. The push button 123 is moved to the outside of the handle part 120 by the operator's pressure again, and releases the application of power as it returns to its original position. The push button 123 may include a locking jaw (not shown) and a hook (not shown) therein so that the push button 123 does not return to its original position even when the push button 123 is moved to the inside of the handle part 120 by a worker's pressurization and the pressurization is released. The push button 123 includes each component of a known push button 123.

Alternatively, the push button 123 may generate a signal for applying power supplied from the power supply device 200 to the board 112 by moving downward by a worker's pressurization. At this time, the operator presses the push button 123 downward by moving the thumb downward after gripping the protruding push button 123 so that the thumb touches it. The push button 123 moved downward by the operator's pressurization indicates the state in which the power supplied from the power supply 200 is applied to the UV-LED module 111 and the heat dissipation cooling fan 119 even when the operator's pressurization is released. Do not move up again to maintain The push button 123, which has moved downward, releases the application of power as it moves upward and returns to its original position when the operator presses the push button 123 upward again. The push button 123 may include a known configuration capable of moving upward and downward from the outside of the handle portion 120 by a worker's pressure and generating an upward and downward movement signal.

In summary, the trigger 121 enables the operation of each component of the discontinuous head unit 110, that is, the UV-LED module 111 and / or the heat dissipation cooling fan 119, by the operator's manipulation, and the push button ( 123) enables the operation of each component of the continuous head part 110, that is, the UV-LED module 111 and/or the heat dissipation cooling fan 119, by the operator's manipulation. On the other hand, when the power of the power supply device 200 is applied to each component of the head unit 110 by the push button 123, operating time information set by the timer unit 220 of the power supply device 200 to be described later. Power can be released accordingly.

On the other hand, as another embodiment of the trigger 121 and the push button 123 according to the present invention, the push button 123 allows only the application of power to each component of the head unit 110, and the trigger 121 It may be configured to release the power by an operation by. For example, the operator presses the push button 123 to apply the power supplied from the power supply 200 to the UV-LED module 111 and the cooling fan 119. Then, the operator releases the application of power by pressing the trigger 121 .

6 is a block diagram showing each configuration of the power supply 200 according to the present invention.

Referring to FIGS. 1 and 6, the power supply device 200 according to the present invention receives power from an external power source through a cable 203 and supplies power to the UV-LED irradiator 100 through a cable 201. It includes a power supply unit 210 to.

The power supply unit 210 may be a high voltage transformer, and may have, for example, 220V/380V and 50/60Hz. In addition, the power supply 200 may include a power control switch 211 for supplying and cutting off power on one side. The power control switch 211 may include a pair of power control switches 211 for respectively applying power to the UV-LED module 111 and the heat dissipation cooling fan 119, but is not limited thereto, and a single power supply Power may be applied to both the UV-LED module 111 and the cooling fan 119 by operating the operation switch 211 .

On the other hand, even if the power control switch 211 included in the power supply 200 operates and power is applied to the UV-LED irradiator 100, the trigger 121 or the push button of the UV-LED irradiator 100 ( When there is no operation by 123, power is not applied to each component of the head unit 110, particularly to the UV-LED module 111. Therefore, the operator applies the power of the power supply 200 to the UV-LED irradiator 100 by operating the power control switch 211 of the power supply 200, and then the trigger 121 of the UV-LED irradiator 100 Alternatively, the push button 123 is operated to operate each component in the head unit 110, particularly the UV-LED module 111. Therefore, after the operator operates the power control switch 211 of the power supply 200, the operation of the UV-LED irradiator 100 while holding the UV-LED irradiator 100 without going through the power supply 200 can be manipulated to enable rapid restart.

The power supply 200 receives the operation time information from the timer unit 220 and the timer unit 220 receiving the operation time information of the UV-LED module 111, and based on the operation time information, the UV-LED module 111 A control unit 230 for controlling power supply to the LED irradiator 100 is further included.

The timer unit 220 includes a timer operation switch 223 and a timer display device 221 installed on one side of the power supply 200 .

The timer unit 220 is embedded in the power supply 200 and provides operation time information of the UV-LED module 111 input from the operator through the timer operation switch 223 to the control unit 230. Accordingly, the control unit 230 receives operating time information of the UV-LED module 111 from the timer unit 220 so that the operating time of the UV-LED module 111 exceeds the set time (eg, 3 minutes). If so, the operation of the UV-LED module 111 can be turned off. The set operation time information can be confirmed by the operator through the timer display device 221.

7 is a perspective view of a UV-LED irradiator 100 according to an embodiment of the present invention.

Referring to FIG. 7 , the UV-LED irradiator 100 according to an embodiment of the present invention may further include a distance sensor 103.

The distance sensor 103 is installed on the front or both sides of the head unit 110 to measure the distance to an irradiated object located in front of the head unit 110 . The distance sensor 103 generates data obtained by measuring the distance between the irradiated object and the head unit 110 . The distance sensor 103 may use a variety of well-known sensors that can be purchased on the market, such as an ultrasonic sensor. The distance sensor 103 may further include a display device (not shown) displaying the measured distance and a speaker device (not shown) sounding an alarm when the measured distance is out of a preset allowable range. Therefore, the operator can maintain a constant distance between the UV-LED irradiator 100 and the irradiated object while monitoring the data generated by the distance sensor 103, that is, the measured distance, and thus maintain a constant amount of ultraviolet light. can

In addition, although not shown in the drawing, the UV-LED irradiator 100 according to an embodiment of the present invention may further include a speed sensor (not shown) integrally with or separated from the distance sensor 103. The speed sensor measures the speed at which the UV-LED irradiator 100 moves. The speed sensor generates data including information about the measured speed. This is because the amount of ultraviolet light is not only affected by the distance between the UV-LED irradiator 100 and the irradiated object, but also affected by the moving speed of the UV-LED irradiator 100. As the speed sensor, known sensors available on the market may be used. In addition, it is preferable that the speed sensor includes a display device and a speaker device like the distance sensor 103 . The operator can monitor the data generated by the measurement of the speed sensor, that is, the measured moving speed of the UV-LED irradiator 100, and by this configuration, by maintaining the moving speed of the UV-LED irradiator 100 constant, The amount of ultraviolet light can be kept more constant.

On the other hand, the UV-LED irradiator 100 according to an embodiment of the present invention is a motion sensor (not shown) installed on the rear or both sides of the head unit 110 to detect a worker located at the rear of the head unit 110. may further include. The motion sensor detects that an operator is located behind the UV-LED irradiator 100 and generates operator detection data. Like the speed sensor and the distance sensor 103, the motion sensor may include a display device and a speaker device. The motion sensor detects a worker at the rear of the UV-LED irradiator 100, and if power is applied to the UV-LED irradiator 100 by the push button 123 or the timer unit 220, the motion sensor When the operator detection data is not generated, the control unit 230 may release power applied to the UV-LED irradiator 100 .

To this end, the power supply 200 may further include a sensor unit 240 that controls and communicates with the motion sensor included in the UV-LED irradiator 100 . The sensor unit 240 is connected to the motion sensor of the UV-LED irradiator 100 by a cable 201 to receive operator sensing data generated by the motion sensor and transmits the received operator sensing data to the control unit 230. .

In addition, the sensor unit 240 receives the distance data between the irradiated object and the head unit 110 and the moving speed data of the UV-LED irradiator 100 from the distance sensor 103 and the speed sensor through the cable 201, respectively. and can be transmitted to the control unit 230.

Meanwhile, referring again to FIG. 6, the power supply device 200 according to the present invention is a communication unit for transmitting data received from the motion sensor, the distance sensor 103, and the speed sensor by the sensor unit 240 to the server 300. (250) may be further included.

8 is a diagram showing each configuration of a power supply 200, a server 300, and a user terminal 10 according to an embodiment of the present invention.

Referring to FIG. 8 , the communication unit 250 transmits data generated by each sensor (motion sensor, distance sensor 103 and speed sensor) to the server 300 . The server 300 may provide the received data to the user terminal 10, and the user terminal 10 accesses the server 300 to access the data stored in the server 300, and the hardening device according to the present invention ( 1000) can be monitored.

Meanwhile, a user holding the user terminal 10 may be a manager who monitors the operation of the hardening device 1000 according to the present invention. That is, in this specification, the operator holds the UV-LED irradiator 100 to perform the curing work, and the manager monitors the operation of the curing device 1000 through the user terminal 10 to operate and use the curing device 1000. can manage and supervise

A plurality of user terminals 10 according to the present invention may be provided, and each user terminal 10 may access data stored in the server 300 by accessing the server 300 . The server 300 receives data received by the sensor unit 240 from each sensor through the communication unit 250 and stores the data in a local storage within the server 300 .

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

Meanwhile, the server 300 according to the present invention may be a centralized storage system including one or more individual servers 3110, 3120, 3130, and 3140 (see FIG. 10). Each of the individual servers 3110, 3120, 3130, and 3140 included in the server 300 writes or reads data by accessing a storage system connected through a communication network. At this time, when a failure occurs in any one of the individual servers 3110, 3120, 3130, and 3140 connected to each other, data in the failed individual server 3110, 3120, 3130, and 3140 cannot be used, causing great inconvenience. Therefore, in the present specification, the same data is redundantly stored in other individual servers (3110, 3120, 3130, and 3140), so that even if any individual server (3110, 3120, 3130, or 3140) fails, the server 300 that can access data Initiate.

9 is a diagram showing each module of the server 300 according to the present invention.

Referring to FIG. 9 , the 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, 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, the data integration management module 310 is a backup module ( 330) can be connected.

10 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 redundancy in which high availability (HA) is guaranteed based on virtualization technology. Referring to FIG. 10, the data integration management module 310 includes a plurality of individual servers 3110, 3120, 3130, and 3140 and local storages 3111 and 3121 included in each individual server 3110, 3120, 3130, and 3140. , 3131, 3141). Each of the individual servers 3110, 3120, 3130, and 3140 included in the data integration management module 310 are connected to each other to form a physical network. The data integration management module 310 groups (3101, 3102) the local storages 3111, 3121, 3131, and 3141 of each individual server 3110, 3120, 3130, and 3140 and manages them, and manages 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 performs integrated management. The data integration management module 310 redundantly stores the same 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 another individual server to the user terminal 10 when a failure occurs in at least one individual server.

In the data integration management module 310, for example, the first local storage 3111 of the first server 3110 and the second local storage 3121 of the second server 3120 are configured as a first server group 3101. In one case, each data of the first local storage 3111 and the second local storage 3121 is crossed and stored redundantly. That is, the data integration management module 310, when data a is stored in the first local storage 3111 and data b is stored in the second local storage 3121, the first local storage 3111 Data a is copied and stored in the second local storage 3121, and data b in 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 redundantly. The data integration management module 310 stores any one local storage 3111, 3121 of each local storage 3111, 3121 of the first server group 3101 in which the same data is redundantly stored when an inspection or failure of any one server occurs. 3121), that is, data redundantly stored in the local storage of another server in the same group can be provided to the user terminal 10, so that the stability of data use can be guaranteed. A more detailed description of the data integration management module 310 will be described later.

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

Referring to FIG. 11 , the network drive module 320 according to the present invention is a drive agent unit 3211 that provides a network drive to the user terminal 10 and a data integrated management module through which the user terminal 10 uses the network drive. 310 includes a shared storage unit 3213 that enables access to local storages 3111, 3121, 3131, and 3141 of each individual server 3110, 3120, 3130, and 3140 included. Meanwhile, at this time, the shared storage unit 3213 may be each of the local storages 3111, 3121, 3131, and 3141 of each individual server 3110, 3120, 3130, and 3140 included in the data integration management module 310 described above. There is, or may be a separate storage to which the data of each of the local storage (3111, 3121, 3131, 3141) is copied. When data stored in the shared storage unit 3213 is changed, data in each local storage 3111, 3121, 3131, and 3141 of each individual server 3110, 3120, 3130, and 3140 is also changed.

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

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

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

Referring to FIG. 12, the backup module 330 according to the present invention stores local storages 3111, 3121, 3131, and 3141 in individual servers 3110, 3120, 3130, and 3140 managed by the data integration management module 310. The data of 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 units 3113, 3123, 3133, and 3143 grant access rights to data in the local storage units 3111, 3121, 3131, and 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 storages 3111, 3121, 3131, and 3141 according to a preset schedule. (3113, 3123, 3133, 3143) is accessed to back up the data of the local storage (3111, 3121, 3131, 3141) to the backup storage unit (3317).

On the other hand, in server redundancy, as data in each local storage (3111, 3121, 3131, 3141) is redundantly stored with each other in real time, there is a problem that data reflected by mistake or files infected with viruses can be duplicated. As the backup module 330 backs up data according to a predetermined schedule, that is, with a time difference, data reflected by mistake or a file infected with a virus can be restored. A more detailed description of the backup module 330 will be described later.

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

The integrated data management module 310 according to the present invention is composed of a plurality of individual servers 3110, 3120, 3130, and 3140 and physical switches (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 or more servers.

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

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

As an embodiment, the plurality of individual servers 3110, 3120, 3130, and 3140 integrate and manage the local storages 3111, 3121, 3131, and 3141 respectively included in the individual servers 3110, 3120, 3130, and 3140. includes a virtual machine that Hereinafter, a virtual machine that integrates and manages the local storage (3111, 3121, 3131, 3141) of a plurality of 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's called a 'virtual machine'.

The management virtual machine is located in 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), management virtual machine (not shown), local storage (3111, 3121, 3131, 3141), physical port (not shown) and backup units 3113, 3123, 3133, and 3143. The management virtual machine is located in any one of a plurality of servers constituting the data integration management module 310 .

The local storages 3111, 3121, 3131, and 3141 are storage media such as hard disk drives (HDDs) and solid state drives (SSDs) located in the individual servers 3110, 3120, 3130, and 3140. The local storages 3111, 3121, 3131, and 3141 may include one or more HDDs or one or more SSDs.

Data of the general virtual machine and management virtual machine are stored in local storages 3111, 3121, 3131, and 3141.

Since the data of the general virtual machine is stored in the local storage (3111, 3121, 3131, 3141), when an individual server (3110, 3120, 3130, 3140) is inspected or fails, the individual server (3110, 3120, 3130, 3140) ), there is a problem that the operation of my virtual machine is paused. In order to solve this problem, the present embodiment groups at least two or more servers into server groups 3101 and 3102 to quickly perform virtual machine migration and provide seamless virtual machine services, and then server groups 3101 and 3102 ) stores my data redundantly.

If there are multiple virtual machines in individual servers (3110, 3120, 3130, 3140), a bottleneck may occur in data reading/writing of each virtual machine, or a bottleneck may occur in data transmission/reception with virtual machines in external servers. have. Alternatively, the management virtual machine needs to quickly process control commands or data for managing the local storages 3111, 3121, 3131, and 3141 of the plurality of individual servers 3110, 3120, 3130, and 3140 without a bottleneck. For rapid data transmission and reception, this embodiment includes a plurality of physical ports.

The physical ports of the 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 storages 3111, 3121, 3131, and 3141 of the plurality of individual servers 3110, 3120, 3130, and 3140 through a physical port. .

A physical port is connected to a virtual switch and can transmit/receive data for virtual machine migration. For example, when a first virtual machine located on the first server 3110 migrates to the second server 3120, a virtual machine is configured through a physical port of the first server 3110 and a 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 to transmit/receive data to/from the local storage (3111, 3121, 3131, 3141). For example, data of general virtual machines in the individual servers 3110, 3120, 3130, and 3140 are transferred to and stored in the local storages 3111, 3121, 3131, and 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, at the request of the backup agent unit 3311, the individual servers 3110, 3120, 3130, Authorization to access data in the local storage (3111, 3121, 3131, 3141) is 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 units 3113, 3123, 3133, and 3143 may back up all data of the local storages 3111, 3121, 3131, and 3141 every time, or extract and back up only changed data from the previous backup point to the current point in time. A detailed description of the backup units 3113, 3123, 3133, and 3143 and the backup server 3310 will be described later.

In this embodiment, the general virtual machine and the management virtual machine form a virtual network through a virtual switch. For example, a private Internet Protocol (IP) address used in a virtual network is assigned to the general virtual machine and the management virtual machine, 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, a plurality of pluralities present in the first server 3110 and the second server 3120. The general virtual machine and the management virtual machine 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, or 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. ) It is composed of a second server group 3102 including.

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

The management virtual machine integrates and manages a plurality of server local storages 3111, 3121, 3131, and 3141 according to grouping information of a server group. For example, after identifying the resource information of the local storages 3111, 3121, 3131, and 3141 of the first to fourth individual servers 3110, 3120, 3130, and 3140, the management virtual machine identifies them as one integrated storage (3111, 3111, 3140). 3121, 3131, 3141).

As an embodiment, the management virtual machine redundantly stores data of the general virtual machine in the local storages 3111 , 3121 , 3131 , and 3141 in the server groups 3101 and 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 data corresponding to the data write request of the first virtual machine to the first server group 3101. In addition to being stored in the first local storage 3111 of the first server 3110 where the virtual machine is located, the second local storage ( 3121) is stored redundantly.

As another embodiment, the management virtual machine may redundantly store the metadata of the general virtual machine and the management virtual machine in the server groups 3101 and 3102 . For example, the 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. duplicate storage. For example, when a virtual machine is created in 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 may be redundantly stored in each of the local storages 3111, 3121, 3131, and 3141.

Since general data and metadata of each virtual machine in the server groups 3101 and 3102 are redundantly stored, virtual machine migration in the server groups 3101 and 3102 can be quickly performed.

As an embodiment, the integrated storage (3111, 3121, 3131, 3141) integrating the local storage (3111, 3121, 3131, 3141) of the 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 by virtual machine services, and metadata refers to various data defining virtual machines such as virtual machine identifiers, virtual machine IP addresses, and operating systems. General data and metadata are redundantly stored in at least two server local storages 3111, 3121, 3131, and 3141 for each server group 3101 and 3102.

As an embodiment, the data integration management module 310 includes one server group 3101, and the corresponding 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 can occur in case of server maintenance or failure. For example, the management virtual machine can periodically transmit a PING signal to each server to determine which server has a failure.

As an example, when there is a request for inspection of 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 . In addition, 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 redundantly stored in the local storages 3111 and 3121 of the first server 3110 and the second server 3120, migration can be completed quickly without separate data transmission and reception, enabling seamless provision of virtual machine services. do.

When the inspection of the first server 3110 is completed or the failure is resolved, the general virtual machine may be migrated to the first server 3110 again. At this time, since the data of the general virtual machine exists in the first server 3110 as it is, only data newly stored by the general virtual machine in the second server 3120 may be transmitted to the first server 3110 .

As an embodiment, the first server group 3101 includes a first server 3110 and a second server 3120, and the second server group 3102 includes a third server 3130 and a fourth server 3140. ), and when the first server group 3101 is inspected or fails, the management virtual machine and the general virtual machine existing in the first server group 3101 are transferred to each server 3130, 3140) and stored in the local storages 3111 and 3121 of the first server group 3101 are stored in the local storages 3131 and 3141 of the second server group 3102.

When the inspection of the first server group 3101 is completed or the failure is resolved, the general virtual machine can be migrated to the first server group 3101 again. At this time, since the data of the general virtual machine exists in the first server group 3101 as it is, 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 may be connected to a plurality of user terminals 10 through a wired or wireless communication network. In addition, the network drive server 3210 may be connected to each individual server 3110 , 3120 , 3130 , and 3140 of the integrated data management module 310 .

A user requests a connection to the network drive server 3210 using the user terminal 10, and the user terminal 10 receives 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 as a network drive and used. .

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, and the storage space at this time includes each individual server 3110, 3120, It may be the local storage (3111, 3121, 3131, 3141) of the 3130, 3140. Hereinafter, it is assumed that data stored in the local storages 3111, 3121, 3131, and 3141 are stored in the shared storage unit 3213, but the shared storage unit 3213 itself is included in the aforementioned data integration management module 310. It may be interpreted as meaning each of the local storages 3111, 3121, 3131, and 3141.

The user terminal 10 according to the present invention is a common computing terminal such as a PC, notebook, netbook, tablet PC, PDA, mobile phone, or smart phone used by a user. The user terminal 10 includes a terminal 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 .

A local operating system (OS) for a terminal provides a data explorer for searching for data such as data stored in a local storage medium for the terminal. The data explorer is a graphical user interface (GUI)-type explorer in the form of a window (window), and displays a directory structure in a folder-type hierarchical structure. In addition, the local operating system (OS) for the terminal mounts the storage medium as a drive and searches for data in a directory structure.

That is, in addition to a local storage medium for a terminal, an external storage medium or a storage space on a network can be mounted as a drive. In general, when a storage medium of another computer terminal connected to a network is connected as a drive, this is called a network drive.

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

The network drive server 3210 allows multiple users to share one piece of data to perform a collaborative task. That is, when one user checks out the corresponding data in order to use the data, the corresponding data is set in a locked state to prevent other users from modifying the data. In addition, when the user checks in after using the data, the data is unlocked so that other users can 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.

On the other hand, data stored in or connected to the shared storage unit 3213 are managed and accessed through the network drive server 3210, or each local storage 3111, 3121, As 3131 and 3141 are approached, it will be described that data is stored and managed in the network drive server 3210 without mentioning the shared storage unit 3213 below.

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

In particular, the drive agent unit 3211 allows the user terminal 10 to access the shared storage unit 3213 in the form of a network drive. To this end, the drive agent unit 3211 converts data stored in the shared storage unit 3213 into a data system of the operating system (or local operating system for the terminal) of the user terminal 10 . The drive agent unit 3211 mounts and provides the converted data system as a network drive of a local operating system for a terminal. That is, 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 a 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 of 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. A unique identifier (or data ID) of each data is assigned to the list of received 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 local operating system for the terminal 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 other computer terminals with the same interface as the data searcher of the own computer terminal. That is, when the user terminal 10 mounts the shared storage unit 3213 as a drive through a data sharing protocol, data can be managed through the same interface as if a local storage medium for the terminal was mounted. As an embodiment, when the local operating system for the terminal is Microsoft's Windows, the data sharing protocol is the SMB protocol.

The drive agent unit 3211 provides a data sharing server function according to a data sharing protocol, requests the user terminal 10 to the drive agent unit 3211 to mount the shared storage unit 3213, 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 a shell of a data explorer of a local operating system for the terminal. The interface unit 11 processes the unique function of the network drive server 3210 in addition to the data system function of the local operating system for the terminal. That is, the data collaboration function of the network drive server 3210 described above is processed.

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

The interface unit 11 expands the shell of the data explorer, receives data sharing information (hereinafter, shared information) from the drive agent unit 3211, and displays it as a context menu. In addition, the extended shell by the interface unit 11 displays a locked state as a context menu when data is being edited by another user, or simply displays all version information of the data.

In addition, the extended shell displays a unique function of the network drive server 3210 as a context menu, and transmits a command to the drive agent unit 3211 when a corresponding menu is selected from the context menu. 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 through a data sharing protocol. When the local operating system for a terminal is Microsoft's Windows, shared information is transmitted by an NTFS stream, which is a kind 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 described above, the data sharing protocol is a protocol for handling data stored in other computer terminals with the same interface as the data explorer of one's own computer terminal. Mounting a storage medium connected to a network as a drive creates a local storage medium for the terminal. Data can be managed with the same interface as the mounted one. 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 functions as a data sharing server according to a data sharing protocol. In the case of Windows, the drive agent unit 3211 performs a function of a SMB server, mounts data of the network drive server 3210 in the form of a network drive, and shares them 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 data sharing information (hereinafter, sharing information) to the interface unit 11, and receives a data sharing command (hereinafter, 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, the data sharing function among the unique functions of data management will be described. Functions for sharing data refer to functions such as check-in/check-out and data locking.

When data is modified, the network drive server 3210 stores it for each version. The interface unit 11 displays information for each version of 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 sends it to the user terminal 10. send.

Data can be shared by multiple users and modified by each user. In this case, if several users modify and store data at the same time, only the last user's data may be saved, and other user's data may not be saved. Therefore, only one user should be able to modify the data at any given time. This is for check-in/check-out.

The drive agent unit 3211, through the interface unit 11, sets the data to a locked state in which modification cannot be made when a check-out sharing command is selected among the sharing information of data, and locks it when the check-in sharing command is selected. ) to release the state. That is, if data is set in a locked state, subsequent users cannot access the data, and when a user issues a checkout command to specific data, the data is locked. Therefore, other users cannot view specific data. When the modification of data is completed, the user saves the data.

On the other hand, as described above, when an inspection or failure occurs in any individual server (3110, 3120, 3130, 3140) included in the data integration management module 310 including the data desired by the user, that is, for example, , Data a that the user wants to access is located in the first local storage 3111 of the first server 3110, and the interface unit 11 of the user terminal 10 transfers the drive agent unit 3211 to the first server 3110. ) and transmits a data reception request signal, when an inspection or failure occurs in the first server 3110, the drive agent unit 3211 connects to the shared storage unit 3213. Data a included in the second local storage 3121 of the second server 3120, which is the same server group 3101 as the first server 3110, rather than the first server 3110, can be provided to the user terminal 10. have. Therefore, the 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, as described above, includes a backup agent unit 3311 and a backup storage unit 3317.

The backup agent unit 3311 includes a backup program, and backup targets within the local storages 3111, 3121, 3131, and 3141 of the individual servers 3110, 3120, 3130, and 3140 according to a preset schedule when the backup program is executed. Data is designated, and backup data is formed 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 to the user terminal 10 and executed or may be automatically executed by the backup units 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 may designate a backup schedule through the backup program. Meanwhile, the backup program is provided to a manager terminal (not shown) possessed by a separate server manager, and a backup schedule may be designated by the manager terminal. In addition, when a backup program is executed by the backup units 3113, 3123, 3133, and 3143, a backup schedule may be automatically designated by the backup units 3113, 3123, 3133, and 3143. Backup schedule designation of the backup units 3113, 3123, 3133, and 3143 will be described later.

Backup target data is data created, deleted, and modified by the user terminal 10 or individual servers 3110, 3120, 3130, and 3140, and is stored in the user terminal 10 or individual servers 3110, 3120, 3130, and 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.

In storing backup data, the backup storage unit 3317 prepares for a case where the original backup data cannot be used due to damage or the like by forming a copy of the backup data and storing it separately from the original.

The backup server 3310 performs backup according to a predetermined schedule, detects whether or not the set capacity is exceeded among the accumulated backup data, compares the creation date of the backup data, and deletes the excess capacity portion of the first created data to make a spare. By designing to continuously secure the disk space of the server 300, after operating the server 300, it automatically backs up and secures disk space by self-determining whether or not the set capacity is exceeded when the disk space is insufficient due to accumulated data.

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

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

Referring to FIG. 13 , 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.

The backup memory unit 3312 stores backup programs provided to the user terminal 10, the manager terminal or the backup units 3113, 3123, 3133, and 3143, and is received from the user terminal 10 or the manager terminal or backed up. Settings such as the backup schedule automatically set by (3113, 3123, 3133, 3143), a plurality of backup data folders, a pre-backup process, a post-backup process, and termination after completion of the backup are stored.

The backup input unit 3313 receives a backup program execution command from the user terminal 10 or the backup units 3113, 3123, 3133, and 3143, a backup time, a process or service to be terminated before driving the backup program, and driving of the backup program. A process or service to be executed after termination, a predetermined number of folders for storing backup data, and whether or not the backup agent unit 3311 is automatically terminated after backup are received.

The backup control unit 3314, the backup input unit 3313 reads the backup program execution command and the backup schedule received from the user terminal 10, the manager terminal or the backup unit 3113, 3123, 3133, 3143 and returns to the read schedule. Accordingly, data to be backed up in the individual servers 3110, 3120, 3130, and 3140 is designated, and the backup data formed by forming the designated backup target data as backup data is transferred to the backup storage unit 3317.

As an embodiment, the backup control unit 3314 may not only form the original backup data as backup data in forming the designated backup target data as backup data, but also compress the backup target data to form backup data. The storage space of the backup storage unit 3317 can be used more efficiently by reducing the capacity of the backup data and transferring the data to the backup storage unit 3317. 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 formed backup data needs to be permanently stored, it is stored in the permanent memory space.

As an embodiment, the backup control unit 3314 deletes only the backup data stored in the general memory space and deletes only the backup data stored in the general memory space when the backup data accumulated and stored in the backup storage unit 3317 exceeds the set capacity and deletes the excess part. By not deleting the backup data separately stored in , it is possible to prevent data that the user should keep from being deleted.

The backup display unit 3315 displays the operating state of the backup program driven by the backup control unit 3314 on the display device of the user terminal 10 or manager terminal.

As an embodiment, the backup display unit 3315 displays the operating state of the backup program on the task bar (for example, the task bar at the bottom of the screen in the case of a Windows PC) on the user terminal 10 or the manager terminal. can be displayed

As an embodiment, the backup display unit 3315 displays a setting window for inputting a backup program's settings (eg, a backup time or a process or service to be terminated before driving the backup program) to the user terminal (10). ) can be displayed on the display device.

As an embodiment, the backup display unit 3315 provides the user with a backup program by means of a pop-up window (ie, a new window suddenly created to display certain contents of a specific website) after the backup program starts or ends. Not only can the driving state be informed by visual means, but also through sound reproduction means (eg, external speaker or built-in speaker) provided in the user terminal 10 or the manager terminal, auditory means Also, the running state of the backup program can 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 reference capacity for deleting backup data previously stored in the backup storage unit 3317, 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 backup data stored in the backup storage unit 3317. The backup control unit 3314, as a result of the comparison, when the capacity of the backup data stored in the backup storage unit 3317 exceeds the reference capacity, the backup data stored in the backup storage unit 3317 exceeds the set capacity of the first created backup data. Only one part can be deleted.

As an embodiment, the backup control unit 3314 determines that the capacity of the backup data stored in the backup storage unit 3317 is a predetermined ratio of the available storage capacity of the backup storage unit 3317 (eg, of the backup storage unit 3317). 80% of the available storage capacity) is exceeded, the backup storage unit 3317 compares the date of creation among the backup data stored in the backup storage unit 3317 and deletes the portion that exceeds the capacity among the data created first. You can make available storage space for newly incoming backup data.

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

As an embodiment, the backup control unit 3314 may be used when data other than backup data (eg, video data or image data stored by a user or administrator's needs) is stored in the backup storage unit 3317. , By reading the reference capacity based on the sum of data other than the backup data and the backup data, it is possible to prevent a case in which available storage space for newly incoming backup data becomes insufficient.

The backup control unit 3314 sets the input backup time in the backup memory unit 3312 according to the backup time reservation request when receiving a backup time input from the backup input unit 3313 and receiving a backup time reservation request.

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

The backup control unit 3314 receives a designated folder name for storing backup data in a predetermined folder from the backup input unit 3313 and receives a designated backup setting request, the designated folder name input according to the designated backup setting request. It is set in the backup memory section 3312.

The backup control unit 3314 may store separate backup data for each designated folder in performing designated backup, and may also perform backup at different times for each folder.

The backup control unit 3314 prevents the same folder name during daily cumulative backup by adding and storing the date and time to the set value of the folder name in which the backup data is stored after performing the backup operation of the designated data folder, and When restoring backed up data, you can selectively restore by distinguishing the date and time the backup was created.

The backup control unit 3314 receives a plurality of folder names for storing a predetermined number of backup data in a predetermined folder, respectively, from the backup input unit 3313 and receives a multi-backup setup request, according to the multi-backup setup request. A plurality of input folder names can be set in the backup memory unit 3312.

Meanwhile, the backup units 3113, 3123, 3133, and 3143 according to the present invention analyze the load of each individual server 3110, 3120, 3130, and 3140 according to the server 300 according to the present invention, and the server 300 ) to the backup input unit 3313 to designate a backup schedule.

At this time, server load analysis of the backup units 3113, 3123, 3133, and 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 transmitted from the interface unit 11 of the user terminal 10 to the drive agent unit 3211 may be analyzed by integrating them. At this time, the number of connected user terminals 10 and the number of data request messages may be derived by analyzing logs in the server 300 .

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

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

Referring to FIG. 14, the backup control unit 3314 arranges 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, and displays the server load. create a diagram At this time, the cell may have a form in which a plurality of rectangles are continuous. The server load generated by the backup control unit 3314 may be displayed on the user terminal 10 or the manager terminal by the backup display unit 3315 and provided to the user or manager.

The backup control unit 3314 may display the plurality of cells differently according to the degree of server load. For example, the backup display is performed by coloring the cells darkly when the server load is low and by coloring the cells lightly when the server load is high. The unit 3315 can be displayed on the user terminal 10. Meanwhile, the coloring of the 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 the day and time of the plurality of weeks. Alternatively, the server load diagram according to an embodiment may represent the degree of server load in the form of a rectangular pillar having the above-described 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 may display on the user terminal 10 a server load having a rectangular columnar cell.

Meanwhile, in FIG. 14, the horizontal length of each cell is shown to mean 1 hour as an example, and for convenience of illustration, only the hours from 0:00 am to 12:00 am and from midnight to noon are shown, but within the server load diagram The shape of each cell can be changed at any time depending on the embodiment. Meanwhile, the backup units 3113, 3123, 3133, and 3143 may track and analyze time required for backup as well as analysis of past server loads.

The backup control unit 3314 may generate a straight line connecting the centers of the cells according to the time zone with the lowest load for each day in the server load diagram arranged in the form of a plurality of cells, and calculate the length of the generated straight line. .

If the time required to back up data in the server 300 according to the present invention ends within one hour, such as the horizontal length of a cell shown in FIG. , it is determined that the past backup time did not take long.

If it is determined that the backup time does not take long, the backup control unit 3314 selects the day and time zone having the shortest length among the lengths of a straight line connecting the center of the cell corresponding to the low load time zone, and selects the day and time zone. Backup can be executed by automatically designating a backup schedule by inputting it into the backup input unit 3313.

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

The backup control unit 3314, when the past backup time does not take a long time, obtains the length of a line segment connecting consecutive low-load time zones, and selects the one having the shortest length. This is because it is possible to guarantee accuracy that the load in that time period is small if the same time period with a short distance is consecutive.

Meanwhile, the backup input unit 3313 may receive a backup time period from the user terminal 10 or the manager terminal, and the backup time period input from the user terminal 10 or the manager terminal is the same according to the operation of the backup control unit 3314. When a line segment of the length is derived, a time zone closest to the input backup time zone may be designated as a backup schedule. That is, when the backup time zone input from the user terminal 10 or the manager terminal is 2:00 am, backup of 5:00 am on Tuesday and Wednesday and 4:00 am on Thursday and Friday, when the length of the line segment is equal to 1, as shown in FIG. The controller 3314 may designate a backup schedule by designating 4 am on Thursday and Friday as the backup time zone. In this way, when a backup time zone is input from the user terminal 10 or the manager terminal and one of the days and time zones having the same length of the line segment is selected, the backup schedule is specified to proceed with backup at the specified time zone, that is, 4:00 am on other days. can

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

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

In this way, when it is determined that the past backup time has taken a long time, the backup control unit 3314, referring to FIG. 15 , obtains the distance of the line segments connecting the centers of the cells of the low-load time zone consecutively. This is because the load of each individual server 3110 , 3120 , 3130 , 3140 within the server 300 according to the backup may be reduced as the length of the line segment obtained by the backup control unit 3314 is longer.

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

As described above, when the backup time takes a long time, the appearance of connecting the center of each cell derived by the backup control unit 3314 is as shown in FIG. 15 . At this time, the backup control unit 3314 derives how much backup time it took in the past, and compares the derived backup time with the length of a line segment connecting the center of each cell. If the derived backup time is 2 to 3 hours, in order to minimize the load on each individual server (3110, 3120, 3130, 3140) in the server 300 according to the backup, on Wednesday and Friday in FIG. Excluded. This is determined to be excluded because the length of the line segment connecting the center of each cell of Wednesday and Friday in FIG. 15 is 2. In addition, 2:00 am to 6:00 am on Monday, 2:00 am to 5:00 am on Tuesday, 3:00 am to 6:00 am on Thursday, and 9:00 am to Saturday, including all 2 to 3 hours of the derived backup time. The backup control unit 3314 designates a backup schedule so that backups are performed at 12:00 am and between 5:00 am and 11:00 am on Sunday.

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

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

Meanwhile, the horizontal length of a cell in the server load diagram may change according to the time zone input from the user terminal 10 or the manager terminal. That is, 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 manager terminal. For example, when the time zone input by the user terminal 10 or the administrator terminal is 5:00 am, the horizontal length corresponding to 5:00 am in the server load diagram may be transformed to twice the horizontal length. In this way, when the horizontal length is modified, 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. 16, as the horizontal length of the cell corresponding to 5:00 AM doubles, the length of the line segment connected to the center of 5:00 AM also increases, and the backup control unit 3314 increases the length. The calculation as described above is performed based on the line segment. Therefore, a backup schedule may be designated in consideration of the time zone input from the user terminal 10 or the manager terminal. In the case of Friday, in FIG. Likewise, as the horizontal length of the cell corresponding to 5:00 am increases, the length of the line segment on Friday becomes 3, so the backup schedule can be changed so that backup is performed on Friday as well.

On the other hand, the time zone input from the user terminal 10 or the manager terminal may receive a plurality of time zones having priority, and each time zone has a horizontal length of 5 times, 4 times, 3 times, 2 times, etc. according to the priority. After lengthening, a backup schedule may be designated according to the length of the line segment connecting the center of each cell.

When the backup program is executed, the backup control unit 3314 checks whether the backup program stored in the backup memory unit 3312 is genuine, and stops execution of the backup program if the backup program is not genuine.

When the backup program is executed, the backup control unit 3314 reads the 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. In this case, by displaying an error message and stopping the execution of the backup program, illegal copying of the backup program can be prevented and the rights of the program developer can be protected.

The backup control unit 3314 having the configuration described above stores the characteristic key value of the hard disk to determine whether the program is genuine, and determines whether to execute the program to protect copyright.

The user terminal 10 or manager terminal according to the present invention is a terminal such as a desktop PC, notebook PC, tablet PC, smart phone, etc. having an input means such as a keyboard, mouse, touch pad, or touch screen, and a display screen. It is not limited, and it is possible to access the server 300 and/or the network drive server 3210 of the network drive module 320 through a communication network, enter search information and selection information, and display search result information. Any configuration capable of processing digital information capable of installing an application program may be included. The user terminal 10 or manager terminal according to the present invention is a component that transmits and receives information by accessing the server 300 or the network drive server 3210 through a communication network, for example, a smartphone, a tablet PC ( tablet personal computer, mobile phone, video phone, desktop personal computer, laptop personal computer, netbook computer, personal digital assistant (PDA), portable multimedia player (PMP), It may include at least one of a wearable device (eg, smart glasses, a head-mounted-device (HMD), etc.), a kiosk, or a smart watch.

The user terminal 10, the manager terminal, the UV-LED irradiator 100, the power supply 200, the network drive module 320 of the server 300, the integrated data management module 310, and the backup module according to the present invention ( 330) may communicate through communication units and communication networks each provided. A communication network refers to a connection structure capable of exchanging information between nodes such as terminals and servers. Examples of such a communication network include a 3rd Generation Partnership Project (3GPP) network, a Long Term Evolution (LTE) network, and 5G Network, WIMAX (World Interoperability for Microwave Access) network, Internet (Internet), LAN (Local Area Network), Wireless LAN (Wireless Local Area Network), WAN (Wide Area Network), PAN (Personal Area Network), wifi network, A Bluetooth network, a satellite broadcasting network, an analog broadcasting network, a Digital Multimedia Broadcasting (DMB) network, etc. are included, but are not limited thereto. User terminal 10, manager terminal, UV-LED irradiator 100, power supply 200, network drive module 320 of server 300, data integration management module 310, and backup module 330, respectively The provided communication unit may include electronic components provided for the communication network to perform wired/wireless data communication through the communication network described above.

In this specification, the server 300 and each component thereof may be processors that execute successive processes stored in memory. Or, it can operate as software modules driven and controlled by a processor. Further, a processor may be a hardware device.

The first to fourth local storages 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 (DBMS). A 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 can access specific data according to the input of a specific command.

In this specification, a "unit" includes a unit realized by hardware, a unit realized by software, and a unit realized using both. Further, one unit may be realized using two or more hardware, and two or more units may be realized by one hardware.

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

10: user terminal 11: interface unit
100: UV-LED irradiator 101: support member
103: distance sensor 110: head unit
111: UV-LED module 112: substrate
113: first substrate 1131: UV-LED chip
114: second substrate 1141: UV-LED chip
115: front opening 116: light emitting plate
117: heat sink 118: side opening
119: heat dissipation cooling fan 120: handle
121: trigger 123: push button
200: power supply 201: cable
203: cable 210: power unit
211: power control switch 220: timer unit
221: timer display device 223: timer operation switch
230: control unit 240: sensor unit
250: communication unit 300: server
310: data integration management module 3101: first server group
3102: second 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: 4th server 3141: 4th 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: Portable UV-LED curing device

Claims (5)

UV-LED irradiator for irradiating ultraviolet rays; and
a power supply connected to the UV-LED irradiator through a cable to supply power to the UV-LED irradiator;
Including,
The UV-LED irradiator,
A head portion including a UV-LED module for irradiating ultraviolet rays toward the front of the opening; and
a handle portion coupled to the lower portion of the head portion and allowing the user to grip the handgun type;
Including,
In front of the head unit, a plurality of support members made of elastic rubber material are included to prevent damage to the head unit by coming into contact with the ground when the UV-LED irradiator is placed on the floor,
The UV-LED irradiator,
a distance sensor installed on the front or both sides of the head unit to measure a distance to an irradiated object located in front of the head unit and to generate the measured data;
a speed sensor installed integrally with or separated from the distance sensor and measuring the speed at which the UV-LED irradiator moves and generating the measured data; and
a motion sensor installed on the rear or both sides of the head unit and detecting a worker positioned at the rear of the head unit and generating detected data;
Including more,
The power supply,
a sensor unit receiving data measured by the distance sensor, the speed sensor, and the motion sensor; and
a communication unit for transmitting the data received by the sensor unit to a server;
Including, characterized in that the server provides the data to the user terminal so that the operation of the UV-LED irradiator can be monitored, a portable UV-LED curing device. The method of claim 1,
The UV-LED module,
Including a substrate on which a UV-LED chip emitting ultraviolet rays is mounted,
the substrate,
Including a first substrate and a second substrate on which a plurality of UV-LED chips emitting ultraviolet rays of different wavelengths are respectively mounted to cure the coating from the inside to the surface;
On the first substrate,
A plurality of UV-LED chips emitting ultraviolet rays of 390 to 405 nm wavelength are mounted,
On the second substrate,
Characterized in that a plurality of UV-LED chips emitting ultraviolet rays of 360 to 370 nm wavelength are mounted, a portable UV-LED curing device. The method of claim 2,
the head part,
a light emitting plate installed in front of the substrate, transmitting ultraviolet rays emitted from the UV-LED chip, and protecting the substrate and the UV-LED chip;
a heat sink absorbing heat generated from the UV-LED module;
a heat dissipation cooling fan for discharging heat absorbed by the heat sink to the rear by circulating air; and
a side opening for intake of air discharged by the heat dissipating cooling fan;
Characterized in that it comprises a portable UV-LED curing device. The method of claim 3,
The handle part,
a trigger that applies power supplied from the power supply device to the UV-LED module and the heat dissipation cooling fan by a user's pressurization, and releases the application of the power when the pressurization is released due to an elastic body included therein; and
a push button that maintains a state in which the power supplied from the power supply device is applied to the UV-LED module and the cooling fan by a user's pressurization, and cancels the application of the power by a user's pressurization again;
Characterized in that it comprises a portable UV-LED curing device. The method of claim 1,
The power supply,
a power supply unit receiving power from an external power source and supplying power to the UV-LED irradiator;
a timer unit receiving operation time information of the UV-LED module; and
a controller for receiving the operation time information from the timer unit and controlling power supply to the UV-LED irradiator based on the operation time information;
Characterized in that it further comprises a portable UV-LED curing device.

Images