KR20100067976A - Method for synchronizing contents files stored separately - Google Patents

Abstract

PURPOSE: A method for synchronizing a content file which are dispersedly stored is provided to synchronize dispersed contents file through other different systems on the internet effectively and easily. CONSTITUTION: It is detected whether or not the content files which are the dispersion target are changed(300). The file synchronization server requests the metadata of the contents file if the change of the contents file is detected(302). The meta data received from the file synchronization server are compared with the meta data managed by the contents producer terminal(304). If the file synchronization is necessary(306), the alter file information on the contents file is transmitted to the synchronization server and requests(308).

Description

How to synchronize distributed stored content files {METHOD FOR SYNCHRONIZING CONTENTS FILES STORED SEPARATELY}

The present invention relates to a method for synchronizing distributed and stored content files, and more particularly, when the same content file is distributed and managed in a plurality of systems (user terminal, service server, etc.), the change in the content file in any one system is limited. If so, it relates to a method for synchronizing distributed and stored content files that can be quickly reflected and matched in other systems.

In the conventional Internet, the file transfer protocol (FTP) for file transfer simply performs a function of transmitting or receiving a file by a user's command. In this case, the file is duplicated into two different files, one is stored on the transmitting side, and the other is transmitted and stored on the receiving side.

After copying, these two files have the same shape, but are not really physically related. Therefore, even if one of the two files is changed, the other file is not automatically changed. However, since the average person tends to think of the two files as the same data, there is a need to synchronize them.

Current synchronization techniques include a method of synchronizing a plurality of files (data) that are physically separated from each other, rather than being copied (replicated) as described above. In this regard, data that guarantees interoperability between heterogeneous systems Synchronization Markup Language (SyncML), a synchronization standard, is a typical example. This synchronization solution is focused on synchronization, such as data collision, and the application process using synchronization must be implemented separately.

Such conventional methods do not have a problem in performing a single function, respectively, but there is a problem in that a content producer may cause a mistake and inconvenience in handling a large number of content files.

In addition, when uploading / downloading a large file to a service server through the Internet, the speed is slowed down due to overload. Therefore, it is difficult for a content producer to add / modify a content file, and to modify a content file. In the case of / addition, if the version management is not properly performed, there may be a situation in which a plurality of identical content files are registered or original loss / damage may occur.

It is an object of the present invention to provide a method for synchronizing distributed and stored content files, which can solve the problems of the related art as described above, and can quickly and easily synchronize content files distributed and managed through different systems on the Internet.

The objects of the present invention are not limited to the above-mentioned objects, and other objects and advantages of the present invention which are not mentioned can be understood by the following description, and will be more clearly understood by the embodiments of the present invention. Also, it will be readily appreciated that the objects and advantages of the present invention may be realized by the means and combinations thereof indicated in the claims.

In order to solve the above object, the present invention provides a content file synchronization method applied to a content producer terminal, comprising: a change detection step of detecting whether a file synchronization server and a content file to be distributed management target are changed; A metadata request step of requesting metadata of the content file from the file synchronization server when a change of the content file is detected; And comparing the metadata received from the file synchronization server with metadata managed by the content producer terminal to synchronize the file, and requesting synchronization while transmitting file change information about the content file to the synchronization server. Steps.

In addition, the present invention, in the content file synchronization method applied to the file synchronization server for performing the synchronization of the content file through the linkage with the content producer terminal,

Providing metadata about a content file requested from the content producer terminal; A first synchronization step of reflecting the file change information received from the content producer terminal in the content file; And a second synchronization step of receiving a content file change received from the content producer terminal at a predetermined synchronization time point and reflecting the change in the content file.

As described above, when the same content file is distributed and stored / managed by the producer terminal and a content server on the web through the Internet, the distributed content file can be quickly and easily synchronized.

In addition, the present invention has the effect that the content producer can register (upload) the high-definition / large-capacity multimedia content file to a content server (service server) on the Internet, and then effectively and systematically perform post management.

In addition, the present invention has the effect of reducing the waiting time of the manufacturer by processing the large sized files as immediately uploaded / downloaded using a background file transfer system developed based on the data distribution synchronization technology.

In addition, the present invention has the effect of reducing the transmission time and cost by reading and transmitting only the changed part even when the content file is changed many times by the content producer.

In addition, the present invention, by managing the file version in the content producer terminal, it is possible to systematically manage important files such as the latest file, the original file, etc. This can also prevent the mistakes or duplication of work of the producer .

In addition, the present invention can be used when transmitting a large amount of data through the Internet, can be used for uploading content files for Internet services, can be used in a system for storing and managing a large number of large personal data on the server In addition, there is an effect that can be utilized when registering and using files in a P2P system.

In addition, the present invention has an effect that can be utilized even when an individual or a business operator publishes for an Internet service after producing a high-quality large-capacity multimedia content file on the Internet.

The present invention facilitates the management of the content file of the producer through the version management based on the synchronization technology in registering and managing a large number of content files produced by the content creator on the Internet.

The foregoing and other objects, features and advantages of the present invention will become more apparent from the following detailed description of the present invention when taken in conjunction with the accompanying drawings, in which: There will be. In addition, in describing the present invention, when it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. Hereinafter, a preferred embodiment of the present invention will be described in detail with reference to the accompanying drawings.

1 is a configuration diagram of an embodiment of a content file synchronization system according to the present invention.

As shown in FIG. 1, the content file synchronization system according to the present invention includes a content producer terminal 10 and a file synchronization server 12.

The content file synchronization system synchronizes a content file in a synchronization directory of an operating system file system in the content producer terminal 10 with a corresponding content file in a producer-specific synchronization directory in a file synchronization server 12 located at a remote location. Do this.

That is, in the case where the same content file is distributed and stored in the content producer terminal 10 and the file synchronization server 12, the content file synchronization system reflects the change in the remaining files regardless of which file change occurs. A synchronization process is performed so that metadata and actual file contents of a plurality of managed files are the same.

Figure 2 is a detailed configuration diagram of one embodiment of the file synchronization device (client) of Figure 1 according to the present invention. Hereinafter, the synchronization method performed by the file synchronization server and the file synchronization device (client) will be described together.

As shown in FIG. 2, the file synchronization device (client) 210 includes a file manager 211, a file state manager 212, a file version manager 213, a metadata generator 214, and a file. It includes a synchronization unit 215, a background file transmission unit 216.

The producer file manager 211 provides a function of managing information such as registration, change, deletion, upload / download, and file version of a content file.

The file state manager 212 detects and notifies whether or not the content file in the synchronization directory 200 is changed.

The file version management unit 213 bundles the content file designated by the user with various other changed files and manages the version file such as a modification date and a modified version.

The metadata generating unit 214 stores metadata about the actual file (for example, file name, file size, creation date, date of use, storage location, etc.), file distribution information, and synchronization information. Create / Change

The file synchronizer 215 exchanges and compares metadata by communicating with a file synchronization server 12 located at a remote location to perform a synchronization process.

The background file transmission unit 216 transmits a file in the background according to metadata at a time when a user (content producer) does not use his terminal 10 or at the user's request.

When the producer puts a content file to be transmitted through the producer file management unit 211 into the directory 200 for synchronization of the file system of the computer operating system, the file state management unit 212 automatically indicates that the file is "added". Recognizes and checks the file version management unit 213 whether it is a new file or an existing file.

If the file is a new file, the metadata generator 214 generates metadata about the content file. Here, the metadata includes file information metadata, synchronization information metadata, and usage information metadata.

The content file in which the metadata is generated is registered in the synchronization queue by the file synchronization unit 215 and records the synchronization state in the synchronization information metadata. Thereafter, synchronization is sequentially performed at a time point at which synchronization is possible. Here, the synchronization period is a synchronization period set by the producer file management unit 211, the synchronization is made by this synchronization period.

In more detail, the synchronization period is subdivided into a default synchronization period, an entire synchronization period, and a file-by-file synchronization period. The timing of synchronization is determined according to the type of synchronization setup time interval, the type of non-use of the computer and the type of user manual operation, which is set in advance.

The timer inside the background file transmitter 216 operates by the set synchronization period to transmit a file (newly added file) based on the synchronization information in the synchronization queue. That is, the background file transfer unit 216 operates according to a synchronization cycle to transmit additional files (newly added files) in the synchronization queue in the file synchronizer 215.

On the other hand, when the producer changes the existing file stored / managed in the synchronization directory 200 (when a version upgraded file is added to the synchronization directory 200), the file state management unit 212 automatically changes the file. If the file version manager 213 is recognized and notified to the file version manager 213, the file version manager 213 queries the metadata of the corresponding file and then passes the file information metadata to the file synchronizer 215.

Then, the file synchronization unit 215 requests and receives the metadata for the same file from the file synchronization server 12, and receives two metadata (file information metadata received from the file version management unit and metadata received from the file synchronization server). Compare to see if the file has changed.

Here, in the file change checking process, the file contents including the information and attributes of the file are checked in byte units and the changes are recorded. The file content checking method generates a hash value in a file checking unit (basically 4 KB, but can be changed according to an embodiment), and compares the hash value for each checking unit section.

The smaller the check unit, the larger the hash value array size. The larger the check unit, the smaller the hash value array size. If there are many small files, set the check unit to a small size. If there are many large files, set the check unit to a large size. Depending on the size of the inspection unit, the transmission rate and the comparison rate may be affected, and in general, the transmission rate and the comparison rate are inversely proportional.

When comparing two files, if there is a change in only one of them, the direction of transferring the latest file is determined, and the synchronization status is recorded in the synchronization information metadata. Thereafter, synchronization processing is performed sequentially at the time points at which synchronization is possible. At this time, the changed part information is extracted while comparing the metadata, and only the changed file part is transmitted during the actual transmission. This can dramatically reduce the transfer of large files.

If both are changed, the change is determined according to the change collision determination method. Here, the change collision determination method (method) includes the latest change date first, the designated device first, the user confirmation, and the like, and the determination method may be set by the user (manufacturer) through the file management unit 211 for the producer.

On the other hand, if the producer "delete" a particular file in the synchronization directory 200, the file is also deleted in the file synchronization server 12, the process will be described as follows.

When the creator deletes the file, the file state manager 212 automatically recognizes that the file has changed, and the file version manager 213 inquires the file's metadata and then sends the file information metadata to the file synchronizer 215. Pass it over. Then, the file synchronization unit 215 requests the file synchronization server 12 to delete the file.

In response to the request of the file synchronization unit 215, the file synchronization server 12 performs a process for the deletion request and returns the result. Here, the processing result is deletion completion, deletion not possible, deletion, pending hold, no file, no permission to delete, a cause not possible error, and the like.

On the other hand, a case where a change to the file stored in the file synchronization server 12 occurs will be described as follows.

The file synchronizer 215 of the content producer terminal 10 periodically requests the file synchronization server 12 to confirm the file change. Here, the file change confirmation request period may be set by the producer through the producer file manager 211.

In response to the file change confirmation request, the file synchronization server 12 transmits a change list to the file synchronization unit 215 when there is a change.

The file synchronizer 215 sequentially processes the changes in the change list. Here, the changes may be in the form of file addition, file change, or file deletion.

First, when a file 'addition' is necessary, that is, if there is a specific file in the file synchronization server 12 but not in the content producer terminal 10, the file synchronization unit 215 has a change and the metadata generator 214. ), The metadata generator 214 determines whether the metadata is consistent, such as whether a file name is error, whether the file can be created, or whether the file storage space is sufficient, based on the metadata passed by the file synchronization server 12. Check and generate metadata if there is no problem. In the synchronization information metadata, a "file reception synchronization status" (meaning that a file reception is required for synchronization) is recorded. Thereafter, the file is sequentially received and processed at the time of file transfer.

Second, when a file 'change' is required, the file synchronization unit 215 inquires the metadata of the file version management unit 213, and compares the search result with metadata provided by the file synchronization server 12 to change the file. Check whether or not.

When only one of the file synchronizing device 210 and the file synchronizing server 12 is changed, the processing direction is determined by transmitting the latest file and recorded in the synchronizing information metadata in a synchronizing state (synchronization required). Then, synchronization processing is sequentially performed at a later point in time that can be synchronized. At this time, the changed part information is extracted while comparing the metadata, and only the changed file part is transmitted during the actual transmission. By doing so, it is possible to drastically shorten the receiving capacity and the receiving time of a large file.

If changes are made in both the file synchronization device 210 and the file synchronization server 12, the file synchronization device 210 processes the data according to the change collision determination method (policy), and records the file information in the synchronization information metadata in the file reception synchronization state. Then, synchronization is sequentially performed at a later point in time that can be synchronized.

Third, when the file 'deletion' is necessary, the file synchronization unit 215 requests the file version management unit 213 to query the metadata and the producer file management unit 211 to confirm the existence of the file to delete the file to be deleted. If it exists, delete it. If the producer does not want to delete the local file at the request of the file synchronization server 12, if the producer activates the delete protection function in advance, the deletion is impossible.

3 is a flowchart illustrating a method of synchronizing a content file in a content producer terminal according to the present invention, and more specifically, illustrates a method performed by the file synchronizing apparatus 210.

The file synchronization device 210 of the content producer terminal 10 detects whether or not a change is made to the content file distributed and managed by the file synchronization server 12 (300). For example, when an arbitrary content file F 'is added to the synchronization directory 200, the file synchronization device 210 may store metadata (eg, file ID, By comparing the file name, creation / modification date, file size, etc., it is checked whether the original file for the added content file exists or is a new file. This process detects whether the content file has changed.

 When the file synchronization device 210 detects a file change, that is, detects that there is already a content file F having the same file ID, the file synchronization device 210 informs the file synchronization server 12 about the content file F in which the change is detected. Request metadata (302).

The file synchronization device 210 compares the metadata managed by the metadata with the metadata received from the file synchronization server 12 (304) to determine the necessity of file synchronization.

As a result of determination, when file synchronization is required, for example, when the content file F 'inserted into the synchronization directory 200 is newer than the content file stored in the file synchronization server 12, the first synchronization time point In step 308, the synchronization request is made while transmitting the change information (file change information) of the metadata generated in the metadata comparison process at "304" to the file synchronization server 12.

Then, the file synchronization server 12 changes the metadata for the corresponding content file based on the file change information received from the content producer terminal 10. The entire new metadata for the content file F 'added to the directory 200 for synchronization is transmitted to the file synchronization server 12, or only the information about the changed part of the metadata is transmitted to the file synchronization server 12. Can be. Here, the file change information is used in a broad sense to encompass the change information transmitted in connection with the change of the content file in the above two cases.

Subsequently, the file synchronization device 210 of the content producer terminal 10 at the second synchronization time point, the file synchronization server 12 according to the background file transmission method of the entire or changed portion of the newly added content file (modified file) (310). Then, the file synchronization server 12 reflects the change contents (substantial content change contents) of the corresponding content file to the content file (synchronization target file) previously stored / managed.

On the other hand, the synchronization request step of "308", if the content file added to the directory for synchronization in the file change detection step 300 is a new file, the corresponding metadata is generated and transmitted to the file synchronization server 12 to synchronize Ask.

In addition, the synchronization request step of "308" and "310", if the deletion of the content file is detected in the file change detection step 300, after deleting the corresponding metadata, the file synchronization server 12 to the corresponding content file Request the deletion of.

4 is a flowchart illustrating a method of synchronizing a content file in a file content server according to the present invention, and illustrating a process of synchronizing a content file through interworking with a content producer terminal.

When the file content server 12 receives a request for metadata about a content file from the content producer terminal 10 (400), the file content server 12 transmits the requested metadata to the content producer terminal 10 (402).

When the file content server 12 receives the file change information from the content producer terminal 10, the file content server 12 changes the metadata of the corresponding content file according to the received file change information (first file synchronization) (404).

Subsequently, when the file content server 12 receives the content file change received from the content producer terminal 10 at the time of synchronization, the file content server 12 reflects the change in the content file (second synchronization step) 406.

As another embodiment, when the file content server 12 receives a file change confirmation request from the content producer terminal 10, the file content server 12 confirms whether or not the file synchronization server-side content file to be synchronized is changed, and when the file change is confirmed. In addition, the process of transmitting the corresponding file change information to the content producer terminal 10 may be further performed. In this case, the change of the server-side content file is transmitted to the content producer terminal 10 according to the background transmission method.

As another embodiment, when the file content server 12 receives a specific content file from a third content producer terminal, the file content server 12 first transmits data of the corresponding content file and then background transfers the content of the requested content file at the time of synchronization. According to the method, the third content producer is transmitted to the terminal. Here, the user of the first content producer terminal and the third content producer terminal may be the same or different.

If the file content server 12 changes the content file transmitted to the third content producer terminal, the file change information and the change of the content file are transmitted to the third content producer terminal.

On the other hand, the method of the present invention as described above can be written in a computer program. And the code and code segments constituting the program can be easily inferred by a computer programmer in the art. In addition, the written program is stored in a computer-readable recording medium (information storage medium), and read and executed by a computer to implement the method of the present invention. The recording medium may include any type of recording medium that can be read by a computer.

The present invention described above is capable of various substitutions, modifications, and changes without departing from the technical spirit of the present invention for those skilled in the art to which the present invention pertains. It is not limited by the drawings.

1 is a configuration diagram of an embodiment of a content file synchronization system according to the present invention;

2 is a detailed configuration diagram of an embodiment of a file synchronization terminal (client) of FIG. 1 according to the present invention;

3 is a flowchart illustrating a method of synchronizing a content file in a content producer terminal according to the present invention;

4 is a flowchart illustrating a content file synchronization method in a file content server according to the present invention.

* Explanation of symbols on the main parts of the drawings

10: content producer terminal 12: file synchronization server

200: directory for synchronization 210: file synchronization device (client)

Claims (12)

In the content file synchronization method applied to the content producer terminal, A change detection step of detecting whether a file synchronization server and a content file to be distributed management target are changed; A metadata request step of requesting metadata of the content file from the file synchronization server when a change of the content file is detected; And If a file synchronization is required by comparing the metadata received from the file synchronization server and metadata managed by the content producer terminal, a synchronization request step of requesting synchronization while transmitting file change information about the content file to the synchronization server. Content file synchronization method comprising a. The method of claim 1, The synchronization request step, And transmitting file change information to the file synchronization server at a first predetermined synchronization time point. The method according to claim 1 or 2, Transmitting a change of the content file to a file synchronization server according to a background transfer method at a predetermined second synchronization time point; Content file synchronization method further comprising. The method of claim 3, wherein The change detection step, When an arbitrary content file is added to the synchronization directory, the metadata for the added content file is generated, and then compared with the metadata of the previously stored content files, the content file synchronization method of detecting a content file to be changed. . The method of claim 4, wherein The synchronization request step, If the content file added to the synchronization directory in the change detection step is a new file, the content file synchronization method for generating a request for synchronization while transmitting the metadata to the file synchronization server. The method of claim 4, wherein The synchronization request step, If the deletion of the content file is detected in the change detection step, after deleting the corresponding metadata, and requests the file synchronization server to delete the content file. In the content file synchronization method applied to a file synchronization server for synchronizing the content file by interworking with the content producer terminal, Providing metadata about a content file requested from the content producer terminal; A first synchronization step of reflecting the file change information received from the content producer terminal in the content file; And  A second synchronization step of receiving a content file change received from the content producer terminal at a predetermined synchronization time point and reflecting the change in the content file; Content file synchronization method comprising a. The method of claim 7, wherein Receiving a file change confirmation request from the content producer terminal; Checking whether the file synchronization server-side content file to be synchronized is changed; If the file change is confirmed, transmitting the file change information to the content producer terminal. Content file synchronization method further comprising. The method of claim 8, Transmitting a change of a server-side content file to the content producer terminal according to a background transmission method; Content file synchronization method further comprising. The method according to any one of claims 7 to 9, When a specific content file is requested from a third content producer terminal, data of the corresponding content file is first transmitted, and at the time of synchronization, the content of the requested content file is transmitted to the third content producer terminal according to a background transmission method. Content file synchronization method further comprising. The method of claim 10, And when a change occurs in the content file transmitted to the third content producer terminal, transmitting the file change information and the change of the content file to the third content producer terminal. The method of claim 11, And the user of the first content producer terminal and the third content producer terminal are the same.

Images