KR102367857B1 - Apparatus and server for providing no-hdd service - Google Patents

Abstract

A cache engine device installed in an access switch to provide a NO-HDD service includes a receiver that receives a plurality of Operating System (OS) images and main data from a No-Hard storage server, and a cache OS that stores a plurality of OS images. An image storage area, a main data storage area for storing main data, and at least one diskless PC included in a group connected to an access switch provide one of a plurality of OS images, and at least one diskless PC stores main data It may include a no-hard service provider that provides a no-hard service that allows access to a part of the area.

Description

Device and server providing NO-HDD service {APPARATUS AND SERVER FOR PROVIDING NO-HDD SERVICE}

The present invention relates to an apparatus and a server for providing a no-hard service.

In places where a network environment is established, such as a PC room, a company, or a school, multiple PCs are used exclusively or in common. And there were many difficulties in maintaining and managing these multiple PCs. In particular, when a PC is used in common, the performance of the PC deteriorates rapidly, and there is a problem in that it is vulnerable to viruses and malicious codes. Therefore, there is a problem that a lot of money and time is required in maintaining an aging PC.

Recently, as a method to solve this problem, a NO-HDD service has been introduced. The no-hard service refers to a service in which an operating system (OS) and a hard disk are not installed, and a client terminal is provided with an operating system and a hard disk from a server to operate.

On the other hand, according to the existing no-hard service in which the server directly provides the no-hard service to a plurality of client terminals, traffic is concentrated due to frequent communication between a number of client terminals and the server, especially between the aggregation switch and the access switch. There was a problem in that the bottleneck of the network occurred. As a method to solve this problem, a method of increasing the network line capacity or duplicating the line may be considered, but other solutions are required due to the high cost. Prior art Korean Patent No. 10-1569945 discloses a configuration in which a plurality of server nodes receive a deployment package of images (operating system image and application image) from a central service and store the image on a physical disk without installing the deployment package. has been disclosed.

To provide an OS image to at least one diskless PC included in a group connected to the access switch through the cache engine device installed in the access switch, and to allow the at least one diskless PC to access a part of the storage area of the cache engine device We want to provide a NO-HDD service. However, the technical problems to be achieved by the present embodiment are not limited to the technical problems described above, and other technical problems may exist.

As a technical means for achieving the above-described technical problem, a cache engine device installed in an access switch according to the first aspect of the present invention to provide a no-hard (NO-HDD) service is provided by a plurality of operating systems (OS) from a no-hard storage server. System) a receiver for receiving an image and main data; a cache OS image storage area for storing the plurality of OS images; a main data storage area for storing the main data; and providing one of the plurality of OS images to at least one diskless PC included in a group connected to the access switch, and allowing the at least one diskless PC to access a part of the main data storage area It may include a no-hard service provider that provides a hard service.

A no-hard service providing server for providing a no-hard (NO-HDD) service according to a second aspect of the present invention includes an additional data storage area for storing additional data; an OS image allocator for allocating a plurality of OS images to the cache engine device; a transmission unit for transmitting main data to the cache engine device; and a no-hard service providing unit providing the no-hard service by allowing at least one diskless PC to access a part of the additional data storage area, wherein the cache engine device is installed in an access switch and connected to the access switch An OS image may be provided to at least one diskless PC included in the group to be used, and the at least one diskless PC may access a storage area of the cache engine device.

A card-type cache engine device for providing a no-hard (NO-HDD) service according to a third aspect of the present invention is inserted into one of a plurality of slots of an access switch that connects a no-hard storage server and at least one diskless PC. board; a memory including a cache OS image storage area for storing a plurality of OS images and a main data storage area for storing main data; and providing one of the plurality of OS images to at least one diskless PC included in a group connected to the access switch, and allowing the at least one diskless PC to access a part of the main data storage area It may include a processor that provides a hard service.

The above-described problem solving means are merely exemplary, and should not be construed as limiting the present invention. In addition to the exemplary embodiments described above, there may be additional embodiments described in the drawings and detailed description.

According to any one of the above-described problem solving means of the present invention, a network generated between an access switch and an aggregation switch as a no-hard service is provided through a cache engine device installed in each of a plurality of access switches as well as a no-hard storage server The problem of concentrating traffic due to a bottleneck can be eliminated.

In addition, the diskless PC provides an OS image to at least one diskless PC included in the group connected to the access switch through the cache engine device installed in the access switch, and at least one diskless PC can access the main data. It can improve the booting speed of the PC and provide stable no-hard service to diskless PCs.

1 is a block diagram of a system for providing a no-hard (NO-HDD) service according to an embodiment of the present invention.
2 is a block diagram of the cache engine device shown in FIG. 1 according to an embodiment of the present invention.
3 is a block diagram of the no-hard storage server shown in FIG. 1 according to an embodiment of the present invention.
4 is an operation flowchart illustrating a method for providing a no-hard service according to an embodiment of the present invention.
5 is an operation flowchart illustrating a method of sharing shared data through a cache engine device according to an embodiment of the present invention.
6 is a hardware configuration diagram of the card-type cache engine device shown in FIG. 1 according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those of ordinary skill in the art can easily implement them. However, the present invention may be embodied in several different forms and is not limited to the embodiments described herein. And in order to clearly explain the present invention in the drawings, parts irrelevant to the description are omitted, and similar reference numerals are attached to similar parts throughout the specification.

Throughout the specification, when a part is "connected" with another part, this includes not only the case of being "directly connected" but also the case of being "electrically connected" with another element interposed therebetween. . Also, when a part "includes" a certain component, it means that other components may be further included, rather than excluding other components, unless otherwise stated.

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

Some of the operations or functions described as being performed by the terminal or device in this specification may be instead performed by a server connected to the terminal or device. Similarly, some of the operations or functions described as being performed by the server may also be performed in a terminal or device connected to the server.

Hereinafter, detailed contents for carrying out the present invention will be described with reference to the accompanying configuration diagram or process flow diagram.

1 is a block diagram of a system for providing a no-hard (NO-HDD) service according to an embodiment of the present invention.

Referring to FIG. 1 , the no-hard service providing system includes a cache engine device 110 installed in an access switch 100 , a no-hard storage server 120 , and at least one disk included in a group connected to the access switch 100 . It may include a lease PC 130 . However, since the no-hard service providing system of FIG. 1 is only an embodiment of the present invention, the present invention is not limitedly interpreted through FIG. 1 , and may be configured differently from FIG. 1 according to various embodiments of the present invention. there is.

In general, each component of the no-hard service providing system of FIG. 1 is connected through a network. A network refers to a connection structure in which information can be exchanged between each node, such as terminals and servers, and includes a local area network (LAN), a wide area network (WAN), and the Internet (WWW: World). Wide Web), wired and wireless data communication networks, telephone networks, wired and wireless television networks, and the like. Examples of wireless data communication networks include 3G, 4G, 5G, 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE), World Interoperability for Microwave Access (WIMAX), Wi-Fi, Bluetooth communication, infrared communication, ultrasound Communication, Visible Light Communication (VLC), LiFi, and the like are included, but are not limited thereto.

The access switch 100 mediates the communication line between the no-hard storage server 120 and the at least one diskless PC 130 and controls the connection between the network network and the at least one diskless PC 130 and the network network. Perform access control.

The access switch 100 may be, for example, an access network device that provides a bandwidth of 300 Mbps or more to at least one diskless PC 130 . Also, the access switch 100 may be, for example, an L2 switch.

The aggregation switch 140 is an aggregation network device and may include, for example, an optical line terminal (OLT) and an L3/L2 switch.

The cache engine device 110 is installed in the access switch 100 to provide a no-hard service, and provides at least one diskless PC 130 to at least one diskless PC 130 connected to the access switch 100 . ) may provide an operating system (hereinafter referred to as OS) for booting and main data (eg, including data frequently used in the plurality of diskless PCs 130 ).

Also, the cache engine device 110 may allow at least one diskless PC 130 connected to the access switch 100 to access a plurality of storage areas. Through this, at least one diskless PC 130 of the group connected to the access switch 100 can receive stable Nohas service without being affected by network conditions (eg, speed, delay, bottleneck, etc.) . For example, at least one diskless PC 130 may be provided with an environment in which data previously stored in some of the storage areas can be shared at high speed or collaborated. In addition, the at least one diskless PC 130 may directly access web cache data pre-stored in a partial area of the storage area, and may generate or access personal work data in a partial area of the storage area.

The cache engine device 110 may be configured in the form of a card inserted into one of a plurality of slots of the access switch 100 , for example. Alternatively, the cache engine device 110 may include, for example, a connector inserted into one of a plurality of slots of the access switch 100 to connect the access switch 100 and the cache engine device 110 . In this case, the form of the cache engine device 110 is not limited to the form of a card. A plurality of cache engine devices 110 may be inserted into the access switch 100 .

The no-hard storage server 120 may allocate a plurality of OS images to the cache engine device 110 and transmit main data. In addition, the no-hard storage server 120 may allow at least one diskless PC 130 to access a part of the storage area of the cache engine device 110 . For example, the no-hard storage server 120 allows the at least one diskless PC 130 to access the additional data storage area in which additional data (eg, including data with low frequency of use in a plurality of diskless PCs) is stored. can make it

At least one diskless PC 130 is a PC on which an OS and a hard disk are not mounted, and may receive an OS image for driving the PC from the cache engine device 110 or the no-hard storage server 120 . In addition, at least one diskless PC 130 may receive a no-hard service that allows access to a plurality of storage areas including a storage area of main data from the cache engine device 110 . In addition, at least one diskless PC 130 may receive a no-hard service that allows access to the storage area of additional data from the no-hard storage server 120 .

The present invention may provide a hybrid cloud storage service in addition to the no-hard service. For example, the at least one diskless PC 130 stores data in each storage area according to the use of the accessible storage area as a no-hard service provided from the no-hard storage server 120 and the cache engine device 110 or You can access the data stored in each storage area.

As described above, main data (including main work data) including data frequently used by the plurality of diskless PCs 130 is transmitted to at least one disk through the main data storage area of the cache engine device 110 . It may be provided as a lease PC 130 . On the other hand, additional data (including additional work data) including data with a low frequency of use of the plurality of diskless PCs 130 is at least one diskless PC through the additional data storage area of the no-hard storage server 120 . 130 may be provided.

Due to this, the access traffic from the at least one diskless PC 130 to the no-hard storage server 120 can be further reduced, and the network bottleneck occurring between the access switch 100 and the aggregation switch 140 can be reduced. can be effectively prevented.

Hereinafter, the operation of each component of the no-hard service providing system of FIG. 1 will be described in more detail.

2 is a block diagram of the cache engine device 110 shown in FIG. 1 according to an embodiment of the present invention.

Referring to FIG. 2 , the cache engine device 110 includes a receiver 200 , a cache OS image storage area 210 , a main data storage area 220 , a shared data storage area 230 , and a web cache data storage area 240 . ), a no-hard service providing unit 250 and a communication unit 260 may be included. However, the cache engine device 110 illustrated in FIG. 2 is only one implementation example of the present invention, and various modifications are possible based on the components illustrated in FIG. 2 .

The receiver 200 may receive a plurality of operating system (OS) images from the no-hard storage server 120 . In this case, the plurality of OS images received from the no-hard storage server 120 may be stored in the cache OS image storage area 210 .

Here, the plurality of OS images may be composed of at least one image corresponding to at least one OS that provides an environment for driving various application programs in the diskless PC 130 in which a separate disk does not exist.

Such a plurality of OS images includes the main work data to be stored in the main data storage area 220 of the cache engine device 110 among the work data of the at least one diskless PC 130 and the no-hard service providing server 120 . It may include information of the work data list for the additional work data to be stored in the additional data storage area. For example, based on the information of the work data list included in the OS image, additional work data, for example, work data such as game content, document work program, 3D tool, etc. is additional data of the no-hard service providing server 120 It may be stored in the storage area, and main work data, for example, work data such as photos, music, VOD, etc., may be stored in the main data storage area 220 of the cache engine device 110 .

The receiver 200 may receive main data from the no-hard storage server 120 . In this case, the main data received from the no-hard storage server 120 may be stored in the main data storage area 220 . The main data may be data including data frequently used by the plurality of diskless PCs 130 .

When the no-hard service providing unit 250 receives a request to provide the no-hard service from at least one diskless PC 130 included in the group connected to the access switch 100, the corresponding at least one diskless PC ( 130 ) may be provided with one OS image among a plurality of OS images, and at least one diskless PC 130 may access a part of the main data storage area 220 . Here, at least one diskless PC 130 provides an OS image from the cache engine device 110 installed in the access switch 100 based on location information on the OS image provided by the no-hard service providing server 120 . can receive Here, the location information may include at least one of a location of a plurality of cache engine devices 110 installed in the access switch 100 and a location of one of a plurality of OS images stored in the cache engine device 110 .

At least one diskless PC 130 may access main data through the main data storage area 220 . In addition, the at least one diskless PC 130 may generate main work data through the main data storage area 220 , and the generated main work data is the main work data based on the information of the work data list included in the OS image. It may be automatically stored in the data storage area 220 .

The receiver 200 may receive data shared between at least one diskless PC 130 included in a group connected to the access switch 100 from the at least one diskless PC 130 . In this case, data shared between at least one diskless PC 130 may be stored in the shared data storage area 230 .

The no-hard service provider 250 may allow at least one diskless PC 130 to access the shared data storage area 230 . At this time, at least one diskless PC 130 belonging to the same group may store shared data collaborated with other diskless PCs 130 in the shared data storage area 230 , and the shared data storage area 230 . It is also possible to access and use the stored shared data through

The no-hard service provider 250 may periodically back up the shared data stored in the shared data storage area 230 to the shared data backup area of the no-hard storage server 120 . For example, the no-hard service providing unit 250 may communicate with the no-hard storage server 120 to perform synchronization of shared data based on preset schedule information.

The communication unit 260 may store web cache data used by at least one diskless PC 130 included in the group by accessing a web server (not shown) in the web cache data storage area 240 . For example, the communication unit 260 receives web cache data used by at least one diskless PC 130 from a web server (not shown) or a storage area (main data) allocated to the at least one diskless PC 130 . The web cache data may be extracted from web visit history data stored in the storage area or the additional data storage area).

At this time, the communication unit 260 may extract the web cache data used by at least one diskless PC 130 of the plurality of web cache data more than a preset number of times, and store it in the web cache data storage area 240 . For example, the cache engine device 110 stores the web cache data of the application protocol (eg, HTTP, FTP, CIFS, RTSP/RTP, etc.) with the usage record of the diskless PC 130 in the web cache data storage area 240 . ) can be cached.

The no-hard service provider 250 may allow at least one diskless PC 130 to access a portion of the web cache data storage area 240 . For example, when receiving the request for the first web data from the diskless PC 130 , the no-hard service provider 250 determines whether the first web data is cached in the web cache data storage area 240 . can judge When the first web data is cached in the web cache data storage region 240 , the service providing unit 250 provides the first web data to the diskless PC 130 through the web cache data storage region 240 at high speed. can do. If the web data requested by the diskless PC 130 is not cached in the web cache data storage area 240 , the diskless PC 130 may receive the corresponding web data through a web server (not shown). there is.

In this way, by making the diskless PC 130 accessible to the web cache data storage area 240 in which the requested web data is stored, traffic acceleration for the transmission of web data to the diskless PC 130 in a short distance can be guaranteed, It can contribute to the stabilization of the entire network and can improve the perceived speed of data transmission.

The communication unit 260 may be inserted into one of a plurality of slots of the access switch 100 to communicate with the access switch 100 . For example, the communication unit 260 may perform network quality management, traffic management, and the like through the access switch 100 . For example, the communication unit 260 may monitor the number of at least one diskless PC 130 connected to the access switch 100 , and as a result of the monitoring, the number of the at least one diskless PC 130 is unknown. When the number is greater than or equal to the set number (when excessive traffic is generated), it is possible to control the connection of the diskless PC 130 to the access switch 100 .

Meanwhile, for those skilled in the art, the receiver 200 , the cache OS image storage area 210 , the main data storage area 220 , the shared data storage area 230 , the web cache data storage area 240 , and the no-hard service provider 250 . ) and the communication unit 260 may be implemented separately, or it will be fully understood that one or more of them may be integrated and implemented.

3 is a block diagram of the no-hard storage server 120 shown in FIG. 1 according to an embodiment of the present invention.

Referring to FIG. 3 , the no-hard storage server 120 includes a main OS image storage area 300 , an additional data storage area 310 , a shared data backup area 320 , an OS image allocator 330 , and an OS image request. It may include a receiving unit 340 , an OS image location information providing unit 350 , an OS image updating unit 360 , a transmitting unit 370 , and a no-hard service providing unit 380 . However, the cache engine device 110 shown in FIG. 3 is only one implementation example of the present invention, and various modifications are possible based on the components shown in FIG. 3 .

The main OS image storage area 300 may store a plurality of main OS images. For example, the main OS image providing a driving environment of an application program may be stored in the main OS image storage area 300 .

Additional data may be stored in the additional data storage area 310 . Additional work data worked on at least one diskless PC 130 may be stored in some area of the additional data storage area 310 .

In the shared data backup area 320 , shared data between at least one diskless PC 130 included in a group stored in the cache engine device 110 may be backed up through synchronization with the cache engine device 110 .

The OS image allocator 330 may allocate a plurality of OS images to the cache engine device 110 . Here, the plurality of OS images may be images from which a plurality of main OS images are copied. The plurality of OS images are the main work data to be stored in the storage area of the cache engine device 110 among the work data of the at least one diskless PC 130 and the additional data storage area 310 of the no-hard storage server 120 . It may include information of the work data list for the additional work data to be stored.

The OS image request receiving unit 340 may receive a request for an OS image from at least one diskless PC 130 .

The OS image location information providing unit 350 may provide location information of one of a plurality of OS images allocated to the cache engine device 110 to the at least one diskless PC 130 . Here, the location information may include at least one of a location of a plurality of cache engine devices 110 installed in the access switch 100 and a location of one of a plurality of OS images stored in the cache engine device 110 .

In this case, the at least one diskless PC 130 may receive the no-hard service through the OS image corresponding to the location information. Specifically, at least one diskless PC 130 may receive a no-hard service through the cache engine device 110 corresponding to the location information.

The OS image update unit 360 may update the main OS image stored in the main OS image storage area 300 .

The OS image update unit 360 may update information of the work data list based on the work history of the at least one diskless PC 130 . Specifically, the OS image update unit 360 provides the main work data to be stored in the main data storage area 220 of the cache engine device 110 and the no-hard service based on the work history of the at least one diskless PC 130 . Information of the job data list for the additional job data to be stored in the additional data storage area of the providing server 120 may be updated periodically.

The OS image allocator 330 may reassign a plurality of OS images corresponding to each of the plurality of updated main OS images to the cache engine device 110 .

The transmission unit 370 may transmit main data to the cache engine device 110 . Here, the main data may include, for example, a basic program (eg, a web search, etc.) and an application program (eg, a document processing program, a VOD playback program, etc.).

The no-hard service providing unit 380 may allow at least one diskless PC 130 to access a part of the additional data storage area 310 . In this case, the at least one diskless PC 130 may access the additional data through the additional data storage area 310 . At least one diskless PC 130 may generate additional work data generated during the operation using the additional data through the additional data storage area 310 , and the generated additional work data is stored in the additional data storage area 310 . It may be stored in some areas. In addition, at least one diskless PC 130 may access additional work data through the additional data storage area 310 .

The no-hard service providing unit 380 provides at least one diskless PC 130 with one of a plurality of OS images stored in the main OS image storage area 300 when the cache engine device 110 is defective. Hard service can be provided.

The no-hard service providing unit 380 may receive an access request for shared data from an external terminal (not shown) and provide the shared data backup area 320 to the external terminal. Here, the external terminal is an authenticated terminal, for example, a terminal interworking with at least one diskless PC 130 connected to the access switch 100 or at least one diskless connected to the access switch 100 . It may be another terminal of the user using the PC 130 .

Meanwhile, for those skilled in the art, the main OS image storage area 300 , the additional data storage area 310 , the shared data backup area 320 , the OS image allocator 330 , the OS image request receiver 340 , the OS image location information It will be fully understood that each of the providing unit 350 , the OS image updating unit 360 , the transmitting unit 370 , and the no-hard service providing unit 380 may be implemented separately, or one or more of these may be integrated and implemented. .

4 is an operation flowchart illustrating a method for providing a no-hard service according to an embodiment of the present invention.

The no-hard service providing method according to the embodiment shown in FIG. 4 includes the access switch 100 , the cache engine device 110 , the no-hard storage server 120 and the access switch according to the embodiment shown in FIGS. 1 to 3 . It includes steps of being processed time-series by at least one diskless PC 130 included in the group connected to 100 . Therefore, even if omitted below, at least one selected from the group connected to the access switch 100 , the cache engine device 110 , the no-hard storage server 120 , and the access switch 100 of FIGS. 1 to 3 . The contents described with respect to the diskless PC 130 may also be applied to the no-hard service providing method according to the embodiment shown in FIG. 4 .

Referring to FIG. 4 , in step S401 , the no-hard storage server 120 may transmit a plurality of OS images and main data to the cache engine device 110 installed in the access switch 100 .

In step S403 , the cache engine device 110 may store a plurality of OS images in the cache OS image storage area 210 .

In step S405 , the cache engine device 110 may store main data in the main data storage area 220 .

In step S407 , the diskless PC 130 may transmit a request for an OS image to the no-hard storage server 120 .

In step S409, the no-hard storage server 120 determines whether the cache engine device 110 is defective, and as a result of the determination, if the cache engine device 110 operates normally, the cache engine device 110 is cached to the diskless PC 130 in step S411. Location information of one of a plurality of OS images allocated to the engine device 110 may be provided. Here, the location information may include location information of one of the plurality of cache engine devices 110 installed in the access switch 100 .

In step S413 , the diskless PC 130 may access the cache engine device 110 based on the location information, and may receive an OS image from the cache engine device 110 in step S415 .

In step S417 , the cache engine device 110 may allow the diskless PC 130 to access a part of the main data storage area 220 . The diskless PC 130 may generate and store main work data through the main data storage area 220 , and access the main work data worked by the diskless PC 130 through the main data storage area 220 . may be

In step S419 , the no-hard storage server 120 may allow the diskless PC 130 to access a portion of the additional data storage area 310 . The diskless PC 130 may generate or access additional work data through the additional data storage area 310 .

In step S421, when the no-hard storage server 120 determines that the cache engine device 110 is defective in step S409, one of a plurality of OS images stored in the main OS image storage area 300 is transferred to the diskless PC 130. can provide a know-how service.

In the above description, steps S401 to S421 may be further divided into additional steps or combined into fewer steps, according to an embodiment of the present invention. In addition, some steps may be omitted if necessary, and the order between steps may be changed.

5 is an operation flowchart illustrating a method of sharing shared data through the cache engine device 110 according to an embodiment of the present invention.

The shared data sharing method according to the embodiment shown in FIG. 5 is an access switch 100, a cache engine device 110, a no-hard storage server 120 and an access switch ( 100) including steps that are time-sequentially processed by at least one diskless PC 130 included in the group connected thereto. Therefore, even if omitted below, at least one selected from the group connected to the access switch 100 , the cache engine device 110 , the no-hard storage server 120 , and the access switch 100 of FIGS. 1 to 4 . The contents described with respect to the diskless PC 130 may also be applied to the shared data sharing method according to the embodiment shown in FIG. 5 .

Referring to FIG. 5 , in step S501 , the no-hard storage server 120 receives shared data between at least one diskless PC 130 included in the group stored in the cache engine device 110 from the cache engine device 110 . can do.

In step S503, the no-hard storage server 120 may back up the shared data received from the cache engine device 110 to the shared data backup area 320 .

In step S505 , the cache engine device 110 stores shared data storing shared data between at least one diskless PC 130 included in a group in which at least one diskless PC 130 is connected to the access switch 100 . The area 230 may be made accessible.

At least one diskless PC 130 included in the group in step S507 may create or share shared data through the shared data storage area 230 . As another example, the no-hard storage server 120 may receive an access request for shared data from an external terminal (not shown) and provide the shared data backup area 320 to the external terminal. Here, the external terminal is an authenticated terminal, for example, a terminal interworking with at least one diskless PC 130 connected to the access switch 100 or at least one diskless connected to the access switch 100 . It may be another terminal of the user using the PC 130 .

In the above description, steps S501 to S507 may be further divided into additional steps or combined into fewer steps, according to an embodiment of the present invention. In addition, some steps may be omitted if necessary, and the order between steps may be changed.

6 is a hardware configuration diagram of the card-type cache engine device 110 shown in FIG. 1 according to an embodiment of the present invention.

Referring to FIG. 6 , the card-type cache engine device 110 may include a board 600 , a memory 610 , and a processor 620 . Specifically, the card-type cache engine device 110 includes a board 600 inserted into one of a plurality of slots of the access switch 100 , a memory 610 implemented on the board 600 , and a processor 620 . can

The memory 610 of the card-type cache engine device 110 may include a cache OS image storage area 612 for storing a plurality of OS images and a main data storage area 614 for storing main data.

The memory 610 of the card-type cache engine device 110 includes a shared data storage area (not shown) for storing shared data between at least one diskless PC 130 and a web cache of at least one diskless PC 130 . It may further include a web cache data storage area (not shown) for storing data.

The processor 620 of the card-type cache engine device 110 provides one of a plurality of OS images to the at least one diskless PC 130 , and the at least one diskless PC 130 provides the main data storage area 614 . ) can be made accessible to some of them. Here, the at least one diskless PC 130 may access main data through the main data storage area 614 , and may generate and access main work data.

The processor 620 of the card-type cache engine device 110 allows the at least one diskless PC 130 to access the shared data storage area (not shown), thereby sharing data between the at least one diskless PC 130 . can share

The processor 620 of the card-type cache engine device 110 allows the at least one diskless PC 130 to access the web cache data storage area (not shown) so that the at least one diskless PC 130 is at least once It is possible to access the web cache data that has been used above at high speed.

An embodiment of the present invention may be implemented in the form of a recording medium including instructions executable by a computer, such as a program module executed by a computer. Computer-readable media can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. Also, computer-readable media may include all computer storage media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data.

The description of the present invention described above is for illustration, and those of ordinary skill in the art to which the present invention pertains can understand that it can be easily modified into other specific forms without changing the technical spirit or essential features of the present invention. will be. Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive. For example, each component described as a single type may be implemented in a dispersed form, and likewise components described as distributed may also be implemented in a combined form.

The scope of the present invention is indicated by the following claims rather than the detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalent concepts should be construed as being included in the scope of the present invention. .

100: access switch
110: cache engine unit
120: no-hard storage server
130: at least one diskless PC
140: aggregation switch
600: board
610: memory
612: cache OS image storage area
614: main data storage area
620: processor

Claims (19)

In the cache engine device installed in the access switch to provide a no-hard (NO-HDD) service,
a receiving unit for receiving a plurality of operating system (OS) images and main data from a no-hard storage server;
a cache OS image storage area for storing the plurality of OS images;
a main data storage area for storing the main data; and
No-hard for providing one of the plurality of OS images to at least one diskless PC included in a group connected to the access switch, and allowing the at least one diskless PC to access a part of the main data storage area No-hard service provider that provides services
including,
Based on the frequency of use of the data of the plurality of diskless PCs included in the group, the data is stored in the at least one diskless PC through either the main data storage area or the additional data storage area of the no-hard storage server. provided as
The plurality of OS images includes information of a work data list for main work data to be stored in the main data storage area and additional work data to be stored in the additional data storage area among the work data of the at least one diskless PC. Thing is, the cache engine device.
The method of claim 1,
A shared data storage area for storing shared data between at least one diskless PC included in the group
further comprising,
The no-hard service providing unit will allow the at least one diskless PC to access the shared data storage area, the cache engine device.
The method of claim 1,
A web cache data storage area for storing web cache data of at least one diskless PC included in the group
further comprising,
The no-hard service providing unit will allow the at least one diskless PC to access a part of the web cache data storage area, the cache engine device.
3. The method of claim 2,
The no-hard storage server includes a main OS image storage area for storing a plurality of main OS images;
the additional data storage area for storing additional data; and
Shared data backup area to back up the shared data
A cache engine device comprising a.
5. The method of claim 4,
The no-hard service providing unit periodically backs up the shared data stored in the shared data storage area to the shared data backup area, the cache engine device.
delete 5. The method of claim 4,
The at least one diskless PC may access the main data through the main data storage area and access the additional data through the additional data storage area.
The method of claim 1,
The at least one diskless PC is capable of generating and accessing the main work data through the main data storage area, and generating and accessing the additional work data through the additional data storage area.
The method of claim 1,
The cache engine device is configured in the form of a card inserted into one of a plurality of slots of the access switch, the cache engine device.
The method of claim 1,
A communication unit inserted into one of a plurality of slots of the access switch to communicate with the access switch
Which will further include, the cache engine device.
In the no-hard service providing server that provides a no-hard (NO-HDD) service,
an additional data storage area for storing additional data;
an OS image allocator for allocating a plurality of OS images to the cache engine device;
a transmission unit for transmitting main data to the cache engine device; and
A no-hard service providing unit that provides the no-hard service by allowing at least one diskless PC to access a part of the additional data storage area
including,
The cache engine device is installed in an access switch and provides an OS image to at least one diskless PC included in a group connected to the access switch, and the at least one diskless PC accesses a storage area of the cache engine device. make it possible, but
Based on the frequency of use of the data of the plurality of diskless PCs included in the group, the data is stored in the at least one diskless PC through either the main data storage area or the additional data storage area of the no-hard storage server. provided as
The plurality of OS images includes information of a work data list for main work data to be stored in the main data storage area and additional work data to be stored in the additional data storage area among the work data of the at least one diskless PC. That is, a server that provides a no-hard service.
12. The method of claim 11,
an OS image request receiving unit for receiving a request for the OS image from the at least one diskless PC;
OS image location information providing unit for providing location information of one of a plurality of OS images allocated to the cache engine device to the at least one diskless PC
further comprising,
The at least one diskless PC receives the no-hard service through the cache engine device corresponding to the location information, the no-hard service providing server.
13. The method of claim 12,
a main OS (Operating System) image storage area for storing a plurality of main OS images; and
A shared data backup area for backing up shared data between at least one diskless PC included in the group stored in the cache engine device
Which will further include, no-hard service providing server.
14. The method of claim 13,
The no-hard service providing unit provides the no-hard service by providing one of a plurality of OS images stored in the main OS image storage area to the at least one diskless PC when the cache engine device fails. A hard service provider server.
delete 14. The method of claim 13,
OS image update unit for updating the OS image
further comprising,
The OS image update unit will update the information of the work data list based on the work history of the at least one diskless PC, a no-hard service providing server.
12. The method of claim 11,
The at least one diskless PC may access the main data through a storage area of the cache engine device and access the additional data through the additional data storage area, a no-hard service providing server.
14. The method of claim 13,
The at least one diskless PC is capable of generating and accessing the main work data through the storage area of the cache engine device, and generating and accessing the additional work data through the additional data storage area, no-hard service serving server.
In the card-type cache engine device that provides a no-hard (NO-HDD) service,
a board inserted into one of a plurality of slots of an access switch connecting the no-hard storage server and at least one diskless PC;
a memory including a cache OS image storage area for storing a plurality of OS images and a main data storage area for storing main data; and
No-hard for providing one of the plurality of OS images to at least one diskless PC included in a group connected to the access switch, and allowing the at least one diskless PC to access a part of the main data storage area processor providing the service
including,
Based on the frequency of use of the data of the plurality of diskless PCs included in the group, the data is stored in the at least one diskless PC through either the main data storage area or the additional data storage area of the no-hard storage server. provided as
The plurality of OS images includes information of a work data list for main work data to be stored in the main data storage area and additional work data to be stored in the additional data storage area among the work data of the at least one diskless PC. Thing, a card-type cash engine device.

Images