WO2021215867A1

WO2021215867A1 - Usb-based cloud disk and disk segment management system

Info

Publication number: WO2021215867A1
Application number: PCT/KR2021/005145
Authority: WO
Inventors: 김종호
Original assignee: Kim Chong Ho
Priority date: 2020-04-23
Filing date: 2021-04-23
Publication date: 2021-10-28
Also published as: KR20210131256A; KR102650146B1

Abstract

Disclosed is a USB-based cloud disk according to an embodiment, wherein when the USB-based cloud disk is connected to a computer and has received a write command for a sector from the computer, the USB-based cloud disk transmits data for the sector and a data path for the sector data to a remote storage.

Description

USB-based cloud disk and disk segment management system

The present invention relates to a USB-based cloud disk and disk segment management system.

As network technology develops, data stored in the user's device (eg, desktop, laptop, portable device, etc.) You can use the data stored in the sudden cloud storage.

As an example, Korean Patent Application Laid-Open No. 10-2015-0067643 (published on June 18, 2015) discloses a method and an apparatus for sharing a file in a cloud storage service.

According to an embodiment of the present invention, the security of data stored in the remote storage is enhanced, and the USB storage device can manage (store, delete, read, modify) data in the remote storage simply by connecting the USB storage device to the USB host. A cloud-based disk is provided.

According to another embodiment of the present invention, there is provided a cloud disk in the form of a program installed on a computer to store and manage data in a remote storage.

According to another embodiment of the present invention, the security of data stored in the remote storage is enhanced, and data can be managed (stored, deleted, read, modified) in the remote storage simply by connecting the USB-based cloud disk to the USB host. A data management system and method are provided.

In the USB-based cloud disk according to one or more embodiments of the present invention,

computer processor; a storage unit operatively coupled to the computer processor;

a storage space configuration management unit for managing remote space configuration information; block data connection; and

and a communication unit operatively connected to the computer processor;

The storage space configuration management unit and the block data connection unit may be loaded and operated in the storage unit under the control of the computer processor,

The remote space configuration information includes a sector ID, a remote storage in which sector data is to be stored, and a data path of the sector data, wherein the sector ID, the remote storage, and the data path are associated with each other;

The data path indicates a location where the sector data is stored in the remote storage, and from a computer connected to the USB-based cloud disk, the USB-based cloud disk may receive a write command;

The write command includes sector data (data 1) and an ID (S1) of a sector to store sector data (data 1),

When the USB-based cloud disk receives the write command, the storage space configuration management unit generates configuration information of the sector S1,

The configuration information of the sector S1 includes a remote storage to transmit the sector data data 1 and a data path to store the sector data data 1,

The block data connection unit transmits the sector data (data 1) and the data path of the sector data (data 1) to the remote storage included in the configuration information of the sector (S1) through the communication unit. of cloud disk is disclosed.

In the above-described embodiment, the storage space configuration management unit checks whether the configuration information of the sector S1 is present in the remote space configuration information before generating the configuration information of the sector S1, and if there is no configuration information An update operation of generating the configuration information of the sector S1 and adding the generated configuration information of the sector S1 to the remote space configuration information may be performed.

In the above-described embodiment, the data path of the sector data (data 1) and the sector data (data 1) transmitted by the block data connection unit to the remote storage is determined from the remote space configuration information updated by the block data connection unit. may have been obtained

In the above embodiment, the data path to store the sector data (data 1) includes a place to store the sector data (data 1) and a remote space block ID for the sector data (data 1), and the write The sector ID (S1) included in the command may be a virtual space block ID, and the virtual space block ID and the remote space block ID may be mapped to each other.

In the above-described embodiment, the USB-based cloud disk may receive a read command from a computer connected to the USB-based cloud disk,

The read command includes the ID (S3) of the sector to be read,

When the read command is received after the update operation is completed, the storage space configuration management unit checks whether the configuration information of the sector S3 exists in the updated remote space configuration information,

When the configuration information of the sector S3 exists, the block data connection unit transmits the data path of the sector S3 to the remote storage included in the configuration information of the sector S3 to the remote storage through the communication unit, , receive data stored in the data path of the sector S3 from the remote storage through the communication unit,

The USB-based cloud disk may transmit the data received through the communication unit to the computer that has transmitted the read command.

The read command includes an ID (S0) of a sector to be read, and when the read command is received before the update operation is completed, the storage space configuration management unit adds the sector to the remote space configuration information before being updated. Check whether the configuration information of (S0) exists,

If the configuration information of the sector S0 does not exist, the storage space configuration management unit generates the configuration information of the sector S0 and performs an update operation to add it to the remote space configuration information before being updated,

The configuration information of the sector S0 may include a remote storage for transmitting sector data data 0 to be stored in the sector S0 and a data path for storing the sector data data 0 .

According to one or more embodiments of the present invention, since the data stored in the remote storage can be stored in the remote storage by dividing the data in sector units, even if the data stored in the remote storage is hacked, it is difficult to decrypt the data.

In accordance with one or more embodiments of the present invention, data stored in the remote storage can be stored and data stored in the remote storage can be read without installing a drive of the remote storage on the USB host.

1 to 4 are diagrams for explaining a data management system using a USB-based cloud disk according to an embodiment of the present invention.

5 is a diagram for explaining a USB-based virtual cloud disk according to an embodiment of the present invention.

6 is a diagram for explaining RSC information and F/S information.

7 is a diagram for explaining an operation of formatting the VCD 200 according to an embodiment of the present invention.

8 is a diagram for explaining an operation of writing data to the VCD 200 according to an embodiment of the present invention.

9 is a diagram for explaining an operation of reading data from the VCD 200 according to an embodiment of the present invention.

10 is a diagram for explaining a cloud disk in the form of a program.

[Explanation of code]

USB Host: 100 Explorer: 101

File system: 103 Disc layer: 105

Communication department: 109 USB storage device: 200

Cloud disk in program form: 2200

Remote Storage: 300 Wireless Terminal: 400

The above objects, other objects, features and advantages of the present invention will be easily understood through the following preferred embodiments in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments described herein and may be embodied in other forms. Rather, the embodiments introduced herein are provided so that the disclosed subject matter may be thorough and complete, and that the spirit of the present invention may be sufficiently conveyed to those skilled in the art.

In various embodiments of the present specification, terms such as first, second, etc. are used to describe various components, but these components should not be limited by these terms. These terms are only used to distinguish one component from another. The embodiments described and illustrated herein also include complementary embodiments thereof.

The terminology used herein is for the purpose of describing the embodiments and is not intended to limit the present invention. As used herein, the singular also includes the plural unless specifically stated otherwise in the phrase. As used herein, the terms 'comprises' and/or 'comprising' do not exclude the presence or addition of one or more other components.

용어의 정의Definition of Terms

As used herein, the term 'software' refers to a technology that moves hardware in a computer, and the term 'hardware' refers to a tangible device or device (CPU, memory, input device, output device, peripheral device, etc.) constituting the computer. The term 'step' refers to a series of processing or operations connected in time series to achieve a predetermined goal, the term 'program' refers to a set of instructions combined for processing by a computer, and the term 'recording medium' refers to It means a computer-readable recording medium on which a program used for installing, executing, or distributing a program is recorded.

In the present specification, the term 'execution' means that a program is loaded into a storage unit and operated under the control of a computer processor, even if not explicitly mentioned.

As used herein, the term 'file system' means 'a system that stores or organizes files or data so that they can be easily found and accessed on a computer' or 'a program that stores or organizes files or data so that they can be easily found and accessed on a computer' ' means For example, 'file system' is configured to include several layers such as 'storage device, input/output control, basic file system, file organization module, virtual file system', where the virtual file system is the computer's operating system (OS). ), may or may not be included in the file system (eg, an OS such as Linux) or not (eg, an OS such as Windows). Hereinafter, for the purpose of description, in the present specification, a 'file system' will be used to mean any one of a file system not including a virtual file system, a file system including a virtual file system, and a virtual file system.

In this specification, the term 'USB' (Universal Serial Bus) is used to mean a serial bus standard for connecting peripheral devices to information devices such as computers or to mean 'USB storage device'.

In this specification, the term 'USB storage device' refers to a portable storage device having a function of transmitting and receiving data according to the USB standard. Unlike ROM, which cannot be deleted or modified when data is saved, or RAM, which can be deleted or modified but loses all data when the power is turned off, a 'USB storage device' can store or delete data freely. It has a function to preserve data as it is even when the power is turned off. Meanwhile, the 'USB storage device' may be, for example, a 'USB flash drive or a 'USB memory'.

As used herein, the term 'storage unit' refers to a computer-readable component that can temporarily or permanently set data. The 'storage unit' may refer to, for example, at least one of a volatile memory, a volatile memory, a hard disk, and a solid state disk.

As used herein, the term 'data management system' means a system for managing data, where the term 'management' refers to 'receiving', 'sending', 'storing', 'modification', and 'deletion' of data. It is meant to include, and the term 'unit' means a program for performing a certain function.

In this specification, the term 'disk segment management system' is used to collectively refer to the storage space management unit and the block data connection unit.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

Referring to FIG. 5 , a USB-based Virtual Cloud Disk (VCD) 200 according to an embodiment of the present invention is operatively connected to a USB port (not shown) provided in the computer 100 . . In this specification, the USB-based virtual cloud disk according to an embodiment of the present invention is often referred to as 'VCD' or 'USB storage device'.

The computer 100 includes an explorer 101, a file system 103, a disk layer 105, a storage unit (not shown), an operating system (not shown), and hardware and programs (not shown) for the operation of these components. city) may be included.

The operating system (not shown) includes a file system 103 and a disk layer 105 , and the disk layer 105 may recognize a storage device such as a hard disk.

The disk layer 105 may also receive a read command and a write command for a sector, which is a structural unit of the hard disk, from the file system 103 and transmit it to the hard disk. The disk layer 105 may also transfer sector data received from the hard disk to the file system 103 . In the embodiment described with reference to FIGS. 5 to 9 and the embodiment described with reference to FIGS. 1 to 4 , even if there is no explicit reference to the disc layer 105 , the file system 103 and the VCD 200 ), data and commands transmitted and received between them pass through the disk layer 105 .

The VCD 200 includes a communication unit (not shown) capable of communicating with the remote storage 300 via the Internet, a computer processor (not shown), and a storage unit (eg, operatively connected to the computer processor (not shown)). , including volatile memory and non-volatile memory) (not shown), a disk segment management system, hardware for performing various operations, and a program (not shown). These components are operatively connected to each other.

The disk segment management system includes a storage space configuration management unit (not shown) (hereinafter, 'SCM') (hereinafter, 'SCM') capable of managing remote space configuration information and a block data connection unit (not shown) (hereinafter, 'BDC').

The storage unit (not shown) may temporarily or permanently store programs and data. For example, the SCM (not shown) and the BDC (not shown) may be loaded into a storage unit (not shown) to operate. In addition, basic data and RSC information may also be temporarily or permanently stored in a storage unit (not shown) and used by the SCM (not shown) and the BDC (not shown).

The SCM (not shown) is loaded into a storage unit (not shown) under the control of a computer processor (not shown) when the VCD 200 is connected to the computer 100 and includes basic data (meaning virtual space configuration information) and Executes an operation to manage remote space configuration information. In the present specification, the remote space configuration information will be abbreviated as 'RSC information'.

For more specific examples of SCM (not shown), BDC (not shown), virtual space configuration information, and remote space configuration information, refer to the embodiments described with reference to FIGS. 1 to 4 .

The BDC (not shown) is loaded into a storage unit (not shown) under the control of a computer processor (not shown) when the VCD 200 is connected to the computer 100 and receives a read command and a write command from the computer 100 . A receiving operation may be performed.

The BDC (not shown) may also request sector data from the remote storage 300 or perform an operation to store sector data.

When the VCD 200 is connected to a USB port provided in the computer 100 , the computer 100 recognizes the VCD 200 as a storage device such as a hard disk or a USB memory.

In the following description, the expression that the VCD 200 is connected to the computer 100 means that the VCD 200 is connected to the USB port.

When a user wants to store a file stored in the computer 100 (or a file stored in an arbitrary storage location) (hereinafter, also referred to as a 'target file') in the VCD 200 , the user transfers the VCD 200 to the computer 100 . ) and give a command to save the target file to the VCD (200).

Upon receiving the storage command, the computer 100 divides the target file into one or more data, allocates them to sectors, and sequentially transmits the data allocated to the sectors (hereinafter, 'sector data') to the VCD 200 .

The file system 103 may know how many sector data to divide the target file into by referring to the basic data provided by the VCD 200 . The file system 103 can also know which sectors to allocate by referring to the F/S information for the VCD 200 .

The VCD 200 may sequentially transmit sector data received from the computer 100 to the remote storage 300 . The actual location where sector data is stored is remote storage 300 , but computer 100 understands and treats sector data as stored by VCD 200 .

The VCD 200 stores and manages basic data and RSC information. For example, the SCM (not shown) manages basic data and RSC information.

The basic data may include a type of remote storage (hereinafter also referred to as a 'store server'), a storage capacity of the VCD 200 , and a format type. The VCD 200 may also generate configuration information for a sector using basic data and add it to the RSC information.

The format type may be, for example, File Allocation Table (FAT), File Allocation Table 32 (FAT32), New Technology File system (NTFS), or Extended FAT (exFAT), but the present invention is limited thereto it's not going to be

The RSC information includes a sector ID, a remote storage to store sector data, and a data path. Here, the data path indicates a path to store sector data in the remote storage, and the sector ID, the remote storage to store the sector data, and the data path are related to each other.

RSC information and basic data may be stored and managed in a storage unit (not shown) provided in the VCD 200 or a remote storage 300 (not shown) other than the remote storage 300 .

6 is a diagram for explaining RSC information and F/S information.

Referring to FIG. 6 , Table 2 is shown as an example of RSC information, and Table 1 is shown as an example of F/S information.

Referring to FIG. 6 , Table 2 includes configuration information for each sector.

As a specific example, the sector configuration information includes a sector ID, a store type, and a data path, and the sector ID, the store type, and the data path are related to each other.

Referring to Table 2, the data path of the sector whose sector ID is S0 is ' https://drive.google.com/disk1/sector0 '. Here, 'sector0' may be a remote space block ID of S0 data. In addition, the data path of the sector whose sector ID is S3 is 'disk1, sector3', where 'sector3' may be a remote space block ID.

The sector ID included in the sector configuration information is given by the file system 103 and may correspond to a 'virtual space block ID' in the embodiments of FIGS. 1 to 4 .

On the other hand, the data path includes the remote space block ID, for example, 'sector0' and 'sector3' may correspond to the remote space block ID. For a more detailed description of the virtual space block ID and the remote space block ID, refer to the embodiments of FIGS. 1 to 4 .

Store type defines a remote store that can store sector data. For example, the store type may be cloud storage, database, or NAS (Network Attached Storage). Examples of commercial products of cloud storage, such as Google Drive (trade name), OneDrive (trade name), Dropbox (trade name), MYBOX (trade name), Baidu Cloud (trade name), Examples of commercial products may be MySQL (trade name) or Oracle (trade name).

The store type defines a type of remote storage 300 such as cloud storage, database, or network attached storage (NAS).

The format of the data path is different for each store type. Therefore, when generating sector configuration information, the SCM (not shown) first determines a store type and creates a data path of a format supported by the determined store type.

The data path may include information indicating a place where sector data is to be stored and a remote space block ID. For example, when S4 data is to be stored in the remote storage 300 , the VCD 200 transmits the data path of S4 and the S4 data to the cloud storage which is the remote storage 300 .

The data path of S4 and the cloud storage that has received the S4 data stores the S4 data in the data path of S4.

For another example, when the VCD 200 requests S10 data stored in the database that is the remote storage 300 , the VCD 200 requests the data of S10 while transmitting the data path of S10 to the database. Cloud storage searches for S10 data using “disk1, sector10” included in the data path of S10 as a keyword and transmits it to the VCD 200 .

Referring to FIG. 6 , F/S information includes a file and a sector ID, and one or more sector IDs are mapped (ie, mapped) to the file. The sector ID included in the F/S information is a virtual space block ID.

Now, the format, sector data write, and sector data read operations will be sequentially described with reference mainly to FIGS. 7 to 9 . In the present specification, the form of RSC information, F/S information, or instruction is merely an exemplary representation for the description of the present invention, and the present invention is not limited only to such representations.

포맷format

Referring to FIG. 7 , when the VCD 200 is connected to the computer 100 , the VCD 200 provides basic data to the computer 100 . The VCD 200 reads RSC information (eg, Table 2-1) and stores it in a storage unit (not shown) provided in the VCD 200 (eg, a non-volatile memory such as RAM).

Basic data and RSC information are stored in a storage unit (not shown) provided in the VCD 200 or any remote storage 300 (not shown) other than the remote storage 300 as described above, and are stored in the VCD 200 ) can be managed by

The basic data is provided to the file system 103 . The disk layer 105 recognizes that the VCD 200 is connected to a USB port, and performs sector data transfer, read, and write operations between the VCD 200 and the file system 103 .

The file system 103 may know the sector in which the F/S information is stored by referring to the format type included in the basic data. This is because the sector in which the F/S information is stored is predetermined according to the format type. In this embodiment, it is assumed that F/S information is stored in sector 0 (hereinafter, 'S0').

The file system 103 transmits a read command (READ (S0)) for reading sector data stored in S0 to the VCD 200 in order to know the F/S information of the VCD 200 . Here, 'S0' is a sector ID.

When the VCD 200 receives the read command (READ (S0)), the SCM (not shown) refers to the RSC information (Table 2-1), and whether there is the configuration information of S0 in the RSC information (Table 2-1). check

Since this VCD 200 is not yet formatted, there is no configuration information of S0 in the RSC information (Table 2-1). If the configuration information of S0 does not exist, the SCM (not shown) generates the configuration information of S0 and performs an update operation of adding the generated configuration information of the SO to Table 2-1. 7 , the updated Table 2-2 is exemplarily displayed.

The SCM (not shown) updates Table 2-1 to Table 2-2 and temporarily creates S0 data. Temporarily generated S0 data (hereinafter, 'temporary S0 data') may be, for example, data composed of only '0' or only '1'.

The VCD 200 transmits the temporary SO data to the file system 103 . The file system 103 checks whether F/S information exists in the temporary SO data. In this case, since there is no F/S information in the temporary SO data, the file system 103 generates the F/S information. The file system 103 transmits a write command (Write (data 0, S0)) to store the generated F/S information in S0 to the VCD 200 . Here, data 0 is data constituting F/S information.

Since configuration information of S0 exists in Table 2-2, the VCD 200 transmits data 0 and data paths of S0 to the remote storage 300 using the configuration information of SO. For example, in Table 2-2, since the data path for S0 is 'https://drive.google.com/disk1/sector0', the BDC (not shown) transmits data O to Google Drive with 'https: //drive.google.com/disk1/sector0' Google Drive stores data 0 as 'sector0' in the location indicated by https://drive.google.com/disk1 according to the above request.

Some of the operations in the format operation described above with reference to FIG. 7 are operations that are repeated even in the read operation and the write operation. Repeated operations will be referred to as basic operations in this specification. The basic operation is performed whenever the VCD 200 is connected to the USB port of the computer 100 . Referring to FIG. 7 , the basic operation starts with an operation in which the VCD 200 transmits basic data to the file system 103 , and the file system 103 receives S0 data from the VCD 200 to receive F/S information. It includes a series of operations up to the operation to check whether or not is included.

데이터 쓰기write data

In FIG. 8 , the VCD 200 has completed the format operation described with reference to FIG. 7 . Therefore, it is assumed that the RSC information is Table 2-2 and the F/S information is Table 1-1 in FIG. 7 , and an operation of writing the file jwk.jpg to the VCD 200 will be described.

When the VCD 200 is connected to the computer 100 , the above-described basic operation is performed between the VCD 200 and the computer 100 . For example, the SCM (not shown) provides basic data to the computer 100, reads Table 2-2, and stores it in a storage unit (not shown) provided in the VCD 200 . The file system 103 finds the sector allocated to the F/S information with reference to the basic data.

In the present embodiment, since the sector allocated to the F/S information is S0 , the file system 103 transmits a read command READ (S0) to the VCD 200 . When the SCM (not shown) receives the read command (READ (S0)), it refers to Table 2-2 stored in the storage unit (not shown). In this example, since configuration information of S0 exists in Table 2-2, the VCD 200 provides the remote storage 300 with the data path of S0 (eg, https://drive.google.com/disk1/sector0). ) to request data.

The remote storage 300 searches for data stored in the data path of S0 and transmits it to the VCD 200 , and the VCD 200 provides the data to the computer 100 . The computer 100 may check F/O information from the S0 data. F/O information includes node information (folders and files). The explorer 101 receives such node information from the file system 103 , and provides information on a virtual disk (eg, D) corresponding to the VCD 200 and folders and files located under the virtual disk. can be displayed so that the user can visually see it.

When the computer 100 receives a command from the user to copy the target file (eg, jwk.jpg) to the VCD 200, the computer 100 converts one or more data of jwk.jpg. partitioned and allocated to each sector. For example, assuming that the capacity of jwk.jpg is 6 KB and the sector capacity is 4 KB, two sectors to be allocated to jwk.jpg are required. That is, the file system 103 divides jwk.jpg into two pieces of data, and allocates the two pieces of data to, for example, a sector S3 (hereinafter, 'S3') and a sector S10 (hereinafter, 'S10'), respectively. do. For convenience, the data allocated to S3 is called data 3, and the data allocated to S10 is called data 10.

The file system 103 transmits the command WRITE(data 3, S3) to the VCD 200 . When the VCD 200 receives the command WRITE (data 3, S3), the SCM (not shown) checks whether there is configuration information of S3 with reference to Table 2-2. Since the configuration information of S3 is not included in Table 2-2, the SCM (not shown) creates the configuration information of S3 and adds it to Table 2-2. In FIG. 8, Table 2-3 is shown in which configuration information for S3 is added.

In Table 2-3, the data path of S3 is 'disk1, sector3'. Here, sector 3 is a remote space block ID for data of S3.

In this embodiment, when the VCD 200 creates the data path of data 3, S3 which is the sector ID (ie, 'virtual space block ID') given by the file system 103, and 'sector' which is the remote space block ID It can be seen that it has been converted to 3'.

Alternatively, the virtual space block ID and the remote space block ID may be used identically, and when the VCD 200 in this case creates a data path, the sector ID received from the file system 103 is remotely It will be used as it is as a space block ID. The same is the case with the PCD 2200, which will be described later.

Table 2-3 is an updated version of Table 2-2, and the SCM (not shown) always refers to the most recently updated remote configuration information.

Data 10 allocated to sector S10 (hereinafter, 'S10') is also performed in the same manner as described above. That is, when the VCD 200 receives WRITE ((data 10, S10), the SCM (not shown) first checks whether there is configuration information of S10 in Table 2-3. If there is no configuration information of S10, The configuration information is created and added to Table 2-3 Table 2-4 is the updated Table 2-3, and the configuration information of S10 is added The VCD 200 uses the configuration information of S10 to store the remote storage Data 10 is stored in (300).

Referring to Table 2-3, the remote storage 300 in which S3 data is stored is a database. The data path of S3 is 'disk1, sector 3'. The database type remote storage 300 can find S3 data stored in a specific column of a specific record of a specific table by using the keyword 'disk1, sector 3'.

데이터 읽기read data

In FIG. 9 , the VCD 200 is the VCD 200 in the state described with reference to FIG. 8 . Therefore, the RSC information is Table 2-4, and the F/S information corresponds to a file and S0, S3, and S10.

Hereinafter, the operation of reading jwk.jpg will be described.

When the VCD 200 is connected to the computer 100 , the above-described basic operation is performed between the VCD 200 and the computer 100 . That is, the SCM (not shown) provides basic data to the computer 100, reads Table 2-4, and stores it in a storage unit (not shown) provided in the VCD 200 . The file system 103 of the computer 100 refers to the basic data to find the sector allocated to the F/S information.

In the present embodiment, since the sector allocated to the F/S information is S0, the computer 100 transmits a read command (READ (S0)) to the VCD 200 . When the VCD 200 receives the read command READ (S0), the SCM (not shown) refers to Table 2-4 stored in the storage unit (not shown).

The BDC (not shown) transmits the data path of S0 (eg, https://drive.google.com/disk1/sector0 ) to the remote storage 300 using the configuration information of S0 in Table 2-4. while requesting data.

The remote storage 300 searches for data stored in the data path of S0 (ie, S0 data) and transmits it to the VCD 200 , and the VCD 200 provides the S0 data to the computer 100 .

The computer 100 may check F/O information from the S0 data. The F/O information includes node information (folders and files), and the explorer 101 receives such node information from the file system 103, and a virtual disk corresponding to the VCD 200 (eg, D ) and information about the folders and files located under the virtual disk can be displayed so that the user can visually see them.

Now, when the user selects to read jwk.jpg, the computer 100 can know the sectors allocated to jwk.jpg by referring to the F/S information.

The computer 100 sequentially transmits read commands for S3 and S10 to the VCD 200 . For example, when the computer 100 transmits a read command (READ (S3)) to the VCD 200, the SCM (not shown) checks whether there is configuration information of S3 with reference to Table 2-4.

If there is configuration information of S3, the BDC (not shown) requests S3 data while transmitting the data path included in the configuration information of S3 to the remote storage 300 . In this example, the database, remote storage 300 , receives the above request. The remote storage 300 searches for data stored in the location indicated by the data path of S3 and transmits it to the VCD 200 , and the VCD 200 provides the data to the computer 100 . S10 data can also be read in the same way as S3.

In the above, various embodiments of the USB-based cloud disk according to the present invention have been described with reference to FIGS. 5 to 9 . Meanwhile, the present invention can also be implemented as a cloud disk (hereinafter, referred to as a 'program-type cloud disk') composed of a computer 100 program. That is, according to the present invention, the USB-based cloud disk described above can be configured as a computer program rather than a device.

10 is a diagram for explaining a cloud disk in the form of a program.

Referring to FIG. 10 , the cloud disk 2200 in the form of a program according to an embodiment of the present invention may be installed and executed in the computer 100 . The cloud disk 2200 in the form of a program is operatively connected to the file system 103 and the remote storage 300 . In FIGS. 5 and 10 , the same reference numerals are assigned to components having the same or similar operations.

Referring to FIG. 10 , the computer 100 includes a communication unit 109 , and a cloud disk (hereinafter, 'PCD') 2200 in the form of a program according to an embodiment of the present invention is provided through the communication unit 100 . , request the remote storage 300 to store sector data, or request the remote storage 300 to store sector data.

The PCD 2200 includes a storage space configuration management unit (not shown) and a block data connection unit (not shown), and the operations of the storage space configuration management unit (not shown) and the block data connection unit (not shown) are shown in FIGS. 5 to 9 . Please refer to the description of the embodiments described with reference to and the embodiments described with reference to FIGS. 1 to 4 .

Hereinafter, the operation of the PCD 2200 will be described in detail, but differences from the VCD 200 will be mainly described. The PCD 2200 is operatively connected to the file system 103 rather than the disk layer 105 . When the PCD 2200 is executed by the user in the computer 100 , the file system 103 recognizes that a physical USB storage device is connected to a USB port provided in the computer 100 . When the PCD 2200 is executed by the user, the PCD 2200 generates a virtual signal indicating that it is connected to the USB port provided in the computer 100 (hereinafter, 'virtual connection signal') and sends it to the file system 103 . send The file system 103 receiving the virtual connection signal recognizes that the PCD 2200 is connected to a USB port provided in the computer.

The PCD 2200 transmits basic data to the file system 103 .

Referring to FIG. 10 , when the user of the computer 100 wants to save the target file to the PCD 2200 , the user gives a command to save the target file to the PCD 2200 . Upon receiving the save command, the computer 100 divides the target file into one or more data, allocates them to sectors, and transmits the data allocated to the sectors (hereinafter, 'sector data') to the PCD 2200 .

The PCD 2200 sequentially transmits sector data received from the computer 100 to the remote storage 300 . The location where the target file is actually stored is the remote storage 300 , but the computer 100 understands and treats the target file as being stored by the PCD 2200 .

The PCD 2200 stores and manages basic data and RSC information in the same manner as the VCD 200 described with reference to FIGS. 5 to 9 . For example, the PCD 2200 may generate sector configuration information using basic data.

RSC information and basic data may be stored and managed in a storage unit (not shown) provided in the computer 100 or a remote storage 300 (not shown) other than the remote storage 300 .

A format operation, a write operation, and a read operation of the PCD 2200 are the same as or similar to those of the VCD 200 .

An operation of formatting in the PCD 2200 according to an embodiment of the present invention will be described with reference to FIG. 10, but a part of the description will be referred to with FIGS. 5 to 9 as well.

When the PCD 2200 is executed in the computer 100 , the PCD 2200 provides a virtual connection signal to the file system 103 , and also provides basic data to the file system 103 . Thereafter, the PCD 2200 reads the RSC information (eg, Table 2-1 of FIG. 7 ) and temporarily stores it in a storage unit (not shown) provided in the computer 100 .

The file system 103 may know the sector in which the F/S information is to be stored by referring to the format type included in the basic data. The file system 103 transmits a read command READ (S0) to the PCD 2200 in order to know F/S information.

Upon receiving the read command (READ (S0)), the PCD 2200 refers to the RSC information (Table 2-1) and checks whether the configuration information of S0 is included in the RSC information (Table 2-1). Since the configuration information of S0 does not yet exist in the RSC information (Table 2-1), the PCD 2200 generates the configuration information of S0 and performs an update operation to add it to Table 2-1. 7, Table 2-2 is an updated version of Table 2-1.

The PCD 2200 updates Table 2-1 to Table 2-2 and generates S0 temporary data.

The PCD 2200 provides temporary SO data to the file system 103 . Since there is no F/S information in the temporary SO data, the file system 103 generates F/S information. The file system 103 also converts the generated F/S information into data to be stored in S0 (hereinafter, 'data 0') and transmits a write command (Write (data 0, S0)) to the PCD 2200 . .

When the PCD 2200 receives the write command (Write(data 0, S0)), it refers to Table 2-2, which is remote configuration information. Since configuration information of S0 exists in Table 2-2, the PCD 2200 transmits data 0, which is S0 data, to the remote storage 300 using the configuration information. The remote storage 300 stores data 0 according to the above request.

A write operation in the PCD 2200 according to an embodiment of the present invention will be described with reference to FIG. 10 , but FIGS. 5 to 9 and a part of the description will be referred to together.

It is assumed that the PCD 2200 is in a state in which the format operation is completed as described above, therefore, it is assumed that the RSC information is Table 2-2 and the F/S information is Table 1-1 of FIG. 7 , and in this assumption, the PCD ( 2200), the operation of writing the file jwk.jpg will be described.

When the PCD 2200 is executed in the computer 100 , the PCD 2200 provides a virtual connection signal to the file system 103 , and also provides basic data to the file system 103 . Thereafter, the PCD 2200 reads the RSC information (eg, Table 2-2 of FIG. 7 ) and temporarily stores it in a storage unit (not shown) provided in the computer 100 .

The file system 103 may know the sector in which the F/S information is stored by referring to the format type included in the basic data. The file system 103 transmits a read command READ (S0) to the PCD 2200 in order to know F/S information. When the PCD 2200 receives the read command READ (S0), it refers to Table 2-2 stored in the storage unit (not shown). The PCD 2200 requests data while sending the data path of S0 to the remote storage 300 using the configuration information of S0 present in Table 2-2.

The remote storage 300 searches for data stored in the data path of S0 and transmits it to the PCD 2200 , and the PCD 2200 provides the data to the file system 103 .

Now, assuming that the user copies the target file jwk.jpg to the PCD 2200, the file system 103 divides jwk.jpg into two pieces of data and assigns them to S3 and S10, respectively.

The file system 103 transmits the command WRITE(data 3, S3) to the PCD 2200 . The PCD 2200 checks whether there is configuration information of S3 with reference to Table 2-2. Since the configuration information of S3 is not included in Table 2-2, the PCD 2200 generates the configuration information of S3 and adds it to Table 2-2. In FIG. 8 , it is exemplarily shown as Table 2-3 to which configuration information for S3 is added.

Data 10 allocated to S10 is also performed in the same manner as described above. That is, upon receiving the WRITE ((data 10, S10), the PCD 2200 first checks whether there is configuration information for S10 with reference to Table 2-3. If there is no configuration information for S10, the configuration for S10 Information is created and added to Table 2-3 Table 2-4 is an updated Table 2-3, and configuration information of S10 is added PCD 2200 uses the configuration information of S10 to store remote storage Data 10 is stored in (300).

A read operation in the PCD 2200 according to an embodiment of the present invention will be described with reference to FIG. 10, but a portion of the description will be referred to with FIGS. 5 to 9 as well.

It is assumed that the format of the PCD 2200 in FIG. 10 is completed, and jwk.jpg is stored in the PCD 2200 as described above. Meanwhile, it is assumed that RSC information is Table 2-4 (refer to FIG. 9), and F/S information includes file information allocated to S0, S3, and S10.

When the PCD 2200 is executed in the computer 100 , the PCD 2200 provides a virtual connection signal to the file system 103 , and also provides basic data to the file system 103 . Thereafter, the PCD 2200 reads the RSC information (Table 2-4) and temporarily stores it in a storage unit (not shown) (eg, RAM) provided in the computer 100 .

The PCD 2200 provides basic data to the file system 103 . The file system 103 may know the sector in which the F/S information is to be stored by referring to the format type included in the basic data. The file system 103 transmits a read command (READ (S0)) for reading data stored in S0 to the PCD 2200 in order to know F/S information. When the PCD 2200 receives the read command READ (S0), it refers to Table 2-4 stored in the storage unit (not shown). The PCD 2200 requests S0 data from the remote storage 300 using the configuration information of S0 present in Table 2-4.

Now, when the user selects to read the target file jwk.jpg in the computer 100, the file system 103 refers to the F/S information to find out the sectors allocated to jwk.jpg.

The file system 103 sequentially transmits read commands for S3 and S10 to the PCD 2200 . For example, when the computer 100 transmits a read command (READ (S3)) to the PCD 2200, the PCD 2200 checks whether there is configuration information of S3 with reference to Table 2-4. The PCD 2200 requests S3 data from the remote storage 300 indicated by the data path of S3. The remote storage 300 searches for S3 data stored in the location indicated by the data path of S3 and transmits it to the PCD 2200 , and the PCD 2200 provides the S3 data received from the remote storage 300 to the file system 103 . . The computer 100 may also receive S10 data from the PCD 2200 in the same manner as S3.

In the VCD 200 and PCD 2200 described with reference to FIGS. 5 to 10 , the sector number (ie, virtual space block ID) managed in the F/S information and the sector transmitted to the remote storage 300 are This is an embodiment in which numbers (ie, remote space block IDs) are implemented differently. Therefore, the VCD 200 and the PCD 2200 convert the virtual space block ID into the remote space block ID when creating a data path to be transmitted to the remote storage 300 . Meanwhile, alternatively, if the virtual space block ID and the remote space block ID are implemented identically to each other, the VCD 200 and the PCD 2200 generate a data path to be transmitted to the remote storage 300 , You will be able to use the spatial block ID as it is.

Hereinafter, even in the USB storage device 200 to be described with reference to FIGS. 1 to 4 , an operation of converting the virtual space block ID into the remote space block ID is performed when a data path is created. Meanwhile, alternatively, if the virtual space block ID and the remote space block ID are implemented identically to each other, the USB storage device 200 creates a data path to be transmitted to the remote storage 300 , the virtual space block You will be able to use the ID as it is.

1 to 4 are diagrams for explaining a data management system using a USB-based cloud disk according to an embodiment of the present invention. Meanwhile, the same reference numerals are assigned to the components shown in FIGS. 1 to 4 and the components shown in FIGS. 5 to 10 that have the same or similar operations.

A data management system (hereinafter, 'data management system') using a USB-based cloud disk according to an embodiment of the present invention includes a USB host 100, a USB storage device 200, and a remote device according to an embodiment of the present invention. It may include a storage 300 , and a wireless communication terminal 400 . Here, the USB storage device 200 may be the VCD 200 described with reference to FIGS. 5 to 9 .

The USB host 100 includes a computer processor (not shown), a storage unit (eg, a device capable of temporarily and/or permanently storing data, such as memory or HDD, RAM, or ROM) (not shown), an operating system ( It is a computer equipped with resources (hardware and programs), such as a file system 103, a peripheral device (not shown), and a peripheral device (not shown). The USB host 100 may communicate with the USB storage device 200 according to the USB standard.

A computer processor (not shown), a storage unit (not shown), an operating system (not shown), a peripheral device (not shown), and a file system 103 provided in the USB host 100 are operatively connected to each other. have.

The operation of the file system 103 may be the same as or similar to the operation of the file system 103 described with reference to FIGS. 5 to 10 .

The USB host 100 may transmit/receive data and/or a request (command) to and from the USB storage device 200 through the USB connector 210 .

The USB storage device 200 includes at least one computer processor 204 , a storage unit (eg, RAM 206 , ROM 208 , memory 202 ), a USB connector 210 , and a communication unit 212 . may include. The USB storage device 200 also includes a storage space configuration management unit ('SCM') 214 , a block data connection unit ('BDC') 218 , a USB driver 220 , and attribute/block information 216 . may include

The storage unit (not shown) of the USB storage device 200 may temporarily or permanently store programs and data. For example, the SCM 214 and the BDC 218 may be stored and operated in a storage unit (not shown) of the USB storage device 200 . Also, the storage unit (not shown) of the USB storage device 200 may temporarily or permanently store basic data and RSC information.

Programs such as the SCM 214 , the BDC 218 , and the USB driver 220 are stored in the memory 202 , and are loaded into the RAM 206 under the control of the processor 204 for their operation. can be executed

The computer processor 204 and the memory 202 of the USB storage device 200 are operatively connected and also operatively connected to the communication unit 212 .

The attribute/block information 216 may include virtual space configuration information and RSC information.

The attribute/block information 216 may be managed (created, deleted, changed) by the SCM 214 .

The virtual space configuration information may be stored in the memory 202 , and the RSC information may be stored in the memory 202 or any remote storage (remote storage other than the remote storage 300 ). When the RSC information is stored in any remote storage, the RSC information may be moved or copied to the USB storage device 200 whenever the USB storage device 200 is connected to the computer 100 . RSC information moved or copied to the USB storage device 200 may be loaded into the RAM 206 and used.

The virtual space configuration information includes an address (eg, URL) of the remote storage 300 , a type of the remote storage 300 , information (user ID, password, token) that can log in to the remote storage 300 , and a format may include the type of , and the total size of the virtual space (storage capacity provided by the USB storage device 200 ). Meanwhile, the virtual space configuration information may further include a storage capacity of a block and the number of blocks. Here, the 'block' corresponds to the 'sector' described with reference to FIGS. 5 to 10 .

The virtual space configuration information may correspond to 'basic data' described with reference to FIGS. 5 to 10 .

The F/S information includes 'file-virtual space block mapping data'. 'File-virtual space block mapping data' is a correspondence between files and sectors. Specifically, the 'file-virtual space block mapping data' may correspond to a file and one or more virtual space block IDs. When the capacity of the file is larger than the size of the virtual space block, the file is divided into two or more pieces of data, and virtual space block IDs correspond to the divided data, respectively.

The RSC information includes configuration information of a block (ie, a sector). In the block configuration information, the type of remote storage (ie, store type) and data path are defined for each block. For example, the virtual block ID, the type of remote storage, and the data face correspond to each other.

The virtual space configuration information may further include 'virtual space block-remote space block mapping data'. The 'virtual space block-remote space block mapping data' is data in which a virtual space block ID and a remote space block ID are mapped to each other.

A data path included in the RSC information includes a place to store block data and a remote space block ID. That is, when the SCM 214 generates a data path for a certain block, referring to 'virtual space block-remote space block mapping data', the SCM 214 finds out the remote space block ID corresponding to the virtual space block ID, included in the data path of

Since the RSC information and the F/S information have been described in detail with reference to FIGS. 5 to 10, they will be omitted here.

The communication unit 212 supports communication with the remote storage 300 . For example, the communication unit 212 may be hardware supporting wireless communication such as Wi-Fi or Bluetooth communication, and a program for this may be stored in the storage unit or in the form of firmware in the communication unit.

Here, 'Wireless Fidelity' is a technology that enables electronic devices to connect to a wireless LAN (WLAN). short-distance communication technology capable of In the IEEE 802.11 standard, standards for Wi-Fi communication are defined and managed.

In addition, 'Bluetooth' is a personal short-range wireless communication industry standard for digital communication devices. It is a short-distance data communication technology between electronic devices using short-wave UHF radio waves of 2.4-2.485 GHz included in the ISM band, and is used for personal computers. It is a technology employed for the purpose of exchanging digital information through wireless communication at a relatively low speed for text information and voice information from mobile phones, smartphones, tablets, speakers, etc., as well as mice and keyboards. Bluetooth is registered as IEEE 802.15.1 in the IEEE, and is a technology managed through the Bluetooth Special Interest Group (SIG).

The SCM 214 may generate RSC information for the block. For example, the SCM 214 may generate a data path for block data to be transmitted to the remote storage 300 . When generating a data path, the SCM 214 converts the virtual space block ID given by the file system 103 into a remote space block ID, and the converted remote space block ID is included in the data path.

The SCM 214 may update the RSC information. When the USB storage device 200 receives the WRITE (S4, data 4), the SCM 214 checks whether the configuration information of S4 is included in the RSC information. add to

The SCM 214 may generate the configuration information of S4 with reference to the virtual space configuration information. For example, the SCM 214 selects an available 'remote storage' included in the virtual space configuration information, allocates a remote space block ID to correspond to the virtual space block ID, and selects a data path to store the block data of S4. create

On the other hand, when the USB storage device 200 receives the READ (S3), the SCM 214 checks whether the configuration information of S3 is present in the RSC information, and if present, provides the configuration information of S3 to the BDC 218 . The BDC 218 requests block data from the remote storage 300 using the configuration information of S3.

In this embodiment, the virtual storage space managed by the SCM 214 is not a space physically present in the USB storage device 200 , and the actual physical storage space corresponding to the virtual storage space is located in the remote storage 300 . exist.

The total size (capacity) of the virtual storage space managed by the USB storage device 200 may be set or fixed by a user. Meanwhile, the size of the virtual space block may also be determined by the user. The SCM 214 may set and manage the size of the virtual space block.

The user can set the virtual storage space capacity and virtual space block size through an app or browser installed on the USB host 100, and the SCM 214 is operatively connected to the app or browser, and the SCM 214 ) is managed by including the capacity of the virtual storage space set by the user and the size of the virtual space block in the attribute/block information 216 .

When the BDC 218 receives a read command for a block (eg, S4) from the file system 103, it sends the block data to the remote storage 300 using the RSC information for the block S4. Request and receive from remote storage 300 .

In addition, when receiving a write command to store data in a certain block S5 from the file system 103, the SCM 214 generates RSC information for the block S5, and the BDC 218 generates the generated data in the block S5. The RSC information may be used to request the remote storage 300 to store block data.

The BDC 218 provides an interface capable of transmitting and receiving information such as data, request, and various IDs to and from the USB driver 220 and an interface capable of transmitting and receiving information such as data, request, and various IDs to and from the remote storage 300 do.

The wireless communication terminal 400 performs a function as an access point (AP), receives data from the USB storage device 200 and transmits it to the remote storage 300 , and receives data from the remote storage 300 and stores the USB. to the device 200 .

The wireless communication terminal 400 has a function for short-distance communication with the USB storage device 200 and may include, for example, a communication function such as Wi-Fi or Bluetooth.

The wireless communication terminal 400 may be a device having a data communication function, such as a smart phone or a personal digital assistant (PDA).

The remote storage 300 is a storage device that can be connected through a communication network such as the Internet. It may be a storage device.

The remote storage 300 stores block data received from the USB storage device 200 in a location indicated by a data path. Meanwhile, the remote storage 300 may use the 'remote space block ID' included in the data path as the ID of the block data. For example, when the remote storage 300 receives a data path of 'https://drive.google.com/disk1/sector2', 'sector2' may be used as an ID of block data.

Alternatively, the remote storage 300 may use the ID of the block data other than the remote space block ID included in the data path. In this case, the remote storage 300 will manage the data in which the remote space block ID and the ID of the block data used by the remote storage 300 correspond to each other.

According to an embodiment of the present data management system, data storage may be performed as follows.

When the USB host 100 transmits block data to be stored in a block (eg, S7) to the USB storage device 200 , the USB storage device 200 generates RSC information to store the block data. The USB storage device 200 transmits block data and a data path to the remote storage 300 through the wireless communication terminal 400 . The remote storage 300 stores data received from the USB storage device 200 in a location indicated by a data path.

According to an embodiment of the present data management system, data reading may be performed as follows.

When the USB host 100 requests the USB storage device 200 to read data stored in a block (eg, S8), the USB storage device 200 refers to the space configuration information of the block S8. . Thereafter, the USB storage device 200 requests the data stored in the block S8 while transmitting the data path included in the space configuration information of the block S8 to the remote storage 300 . The remote storage 300 reads data stored in the data path and transmits it to the USB storage device 200 . The USB storage device 200 transmits data received from the remote storage 300 to the file system 103 of the computer 100 .

According to an embodiment of the present invention, there is provided a data management method (hereinafter, 'data management method') using a USB-based cloud disk, wherein the data management method includes a USB storage device, a host of the USB storage device, a sector receiving a write request of data (eg, data 13) to (eg, S13); generating RSC information for the sector (S13) in response to a write request; transmitting the data path of the sector (S13) and the data (data 13) included in the RSC information to a remote storage; and storing, by the remote storage, the data (data 13) in a location indicated by the Data path.

In addition, a data management method according to an embodiment of the present invention includes: receiving, by a USB storage device, a read request of data stored in a sector (eg, S14) from a host of the USB storage device; referring to RSC information for the sector (S14) in response to a read request; transmitting the data path of the sector (S14) included in the RSC information to a remote storage; and finding, by the remote storage, data stored in the location indicated by the data path and providing the data to the USB storage device.

In the above-described methods, for a description of the RSC information, refer to the description of FIGS. 1 to 10 .

The above-described data management method can be implemented by the above-described data management system. Hereinafter, an example in which the present data management method is applied to the above-described data management system will be described.

In the memory included in the USB storage device 200 , a program for causing the processor of the USB storage device 200 to perform the present data management method is stored. A program for performing the present data management method includes the SCM 214 and the BDC 218 .

A data management method according to an embodiment of the present invention is provided, in which a disk segment management system stores data (eg, data 13) in a sector (eg, S13) from a host of a USB storage device. ) receiving a write request; generating, by the disk segment management system, RSC information for the sector (S13) in response to a write request; transmitting, by a disk segment management system, a data path of the sector (S13) included in the RSC information and the data (data 13) to a remote storage; and storing, by the remote storage, the data (data 13) in a location indicated by the Data path.

In addition, the data management method according to an embodiment of the present invention comprises: receiving, by a disk segment management system, a read request for data stored in a sector (eg, S14) from a host of a USB storage device; transmitting, by the disk segment management system, the data path of the sector (S14) included in the RSC information to a remote storage in response to a read request; and finding, by the remote storage, data stored in the location indicated by the data path and providing the data to the USB storage device.

As such, the present invention is not limited to the described embodiments, and it is apparent to those skilled in the art that various modifications and variations can be made without departing from the spirit and scope of the present invention. Therefore, it should be said that such modifications or variations belong to the claims of the present invention.

Claims

In the USB-based cloud disk,

computer processor;

a storage unit operatively coupled to the computer processor;

a storage space configuration management unit for managing remote space configuration information;

block data connection; and

and a communication unit operatively connected to the computer processor;

The storage space configuration management unit and the block data connection unit may be loaded and operated in the storage unit under the control of the computer processor,

The remote space configuration information includes a sector ID, a remote storage in which sector data is to be stored, and a data path of the sector data, wherein the sector ID, the remote storage, and the data path are associated with each other;

The Data path indicates a location where the sector data is stored in the remote storage,

From a computer connected to the USB-based cloud disk, the USB-based cloud disk may receive a write command,

The write command includes sector data (data 1) and an ID (S1) of a sector to store sector data (data 1),

When the USB-based cloud disk receives the write command, the storage space configuration management unit generates configuration information of the sector S1,

The configuration information of the sector S1 includes a remote storage to transmit the sector data data 1 and a data path to store the sector data data 1,

The block data connection unit transmits the sector data (data 1) and the data path of the sector data (data 1) to the remote storage included in the configuration information of the sector (S1) through the communication unit. of cloud disk.
According to claim 1,

The storage space configuration management unit, prior to generating the configuration information of the sector S1, checks whether the configuration information of the sector S1 is present in the remote space configuration information, and if there is no configuration information of the sector S1, A USB-based cloud disk that generates configuration information and performs an update operation of adding the generated configuration information of the sector S1 to the remote space configuration information.
3. The method of claim 2,

The data path of the sector data (data 1) and the sector data (data 1) transmitted by the block data connection unit to the remote storage is obtained from the updated remote space configuration information by the block data connection unit. of cloud disk.
According to claim 1,

The data path to store the sector data (data 1) includes a place to store the sector data (data 1) and a remote space block ID for the sector data (data 1),

The sector ID (S1) included in the write command is a virtual space block ID,

The virtual space block ID and the remote space block ID are mapped to each other, USB-based cloud disk.
3. The method of claim 2,

From a computer connected to the USB-based cloud disk, the USB-based cloud disk may receive a read command,

The read command includes the ID (S3) of the sector to be read,

When the read command is received after the update operation is completed, the storage space configuration management unit checks whether the configuration information of the sector S3 exists in the updated remote space configuration information,

When the configuration information of the sector S3 exists, the block data connection unit transmits the data path of the sector S3 to the remote storage included in the configuration information of the sector S3 to the remote storage through the communication unit, , receive data stored in the data path of the sector S3 from the remote storage through the communication unit,

The USB-based cloud disk transmits the data received through the communication unit to the computer that has transmitted the read command, the USB-based cloud disk
3. The method of claim 2,

From a computer connected to the USB-based cloud disk, the USB-based cloud disk may receive a read command,

The read command includes the ID (S0) of the sector to be read,

If the read command is received before the update operation is completed, the storage space configuration management unit checks whether the configuration information of the sector S0 exists in the remote space configuration information before being updated,

If the configuration information of the sector S0 does not exist, the storage space configuration management unit generates the configuration information of the sector S0 and performs an update operation to add it to the remote space configuration information before being updated,

The configuration information of the sector S0 includes a remote storage to transmit sector data (data 0) to be stored in the sector (S0) and a data path to store the sector data (data 0), a USB-based cloud disk.