KR102227113B1 - A file processing apparatus based on a shared file system - Google Patents

Abstract

The present invention relates to a file processing apparatus based on a shared file system, wherein a file metadata processing unit that determines file metadata associated with a file, and checks whether to set the sharing of the file based on a sharing setting tag included in the file metadata. And a shared file processing unit that obtains shared file metadata that is implicitly accessed through the file metadata when the sharing setting of the file is confirmed and controls access to the file according to the permission attribute of each sharer. . Accordingly, the present invention can classify shared files in a file system of a user storage device and efficiently manage shared files between sharers through shared file metadata.

Description

File processing device based on shared file system {A FILE PROCESSING APPARATUS BASED ON A SHARED FILE SYSTEM}

The present invention relates to a file processing technology based on a shared file system, and more particularly, to a file system based on a shared file system that classifies shared files in a file system of a user storage device and manages shared files through shared file metadata. It relates to a file processing device.

A file system may refer to a system that stores or organizes files or data in a computer so that they can be easily found and accessed. File system usually refers to the management of the physical location of a file using a physical data storage device such as a hard disk or CD-ROM, but the data on the file server is transmitted through a client that performs network protocols (NFS, SMB, 9P, etc.). A method of providing access and a method in which only access means exist as a virtual form can also be included in the scope of the file system. In the case of sharing a storage device, the existing file system does not take into account the control and management of shared files for the sharer.

Korean Patent Laid-Open Publication No. 10-2003-0073981 (2003.09.19) discloses the steps of generating a root block having a constant global depth; And when the directory entry is completely filled in the root block, an index value representing the number of bits to be referred to for the root block is obtained from the global depth through a hash function, and the index value is used as a logical and continuous object. It consists of a step of obtaining block numbers of leaf blocks composed of a plurality of fixed-length-based extent blocks, sequentially storing them in the root block, and then dividing the directory entries of the root block into the leaf blocks and storing them. Accordingly, the data of the file system It improves search performance by delaying the cause of frequent changes to the storage structure and flexibly preventing the generation of indirect blocks.

Korean Patent Publication No. 10-2013-0086694 (2013.08.05) provides a file management method using a file system suitable for nonvolatile memory. In this file management method, a file system used to manage files stored in a storage device includes a super block area, an inode block area, a bitmap block area, and a data block area. As a result, file management using a file system suitable for a nonvolatile storage device becomes possible.

Korean Patent Publication No. 10-2003-0073981 (2003.09.19) Korean Patent Publication No. 10-2013-0086694 (2013.08.05)

An embodiment of the present invention is to provide a file processing device based on a shared file system that classifies shared files in a file system of a user storage device and manages shared files through shared file metadata.

An embodiment of the present invention is to provide a file processing apparatus based on a shared file system that records and manages information about a sharer's access to a shared file shared by a user through shared file metadata.

An embodiment of the present invention is to provide a file processing apparatus based on a shared file system that records and manages whether a user has access to a shared file shared or updated by a sharer.

Among embodiments, a file processing apparatus based on a shared file system includes a file metadata processing unit that determines file metadata associated with a file, and checks whether to set the sharing of the file based on a sharing setting tag included in the file metadata. A shared file verification unit and a shared file processing unit that, when the sharing setting of the file is confirmed, obtains the shared file metadata that is implicitly accessed through the file metadata, and controls access to the file according to the permission attribute for each sharer. have.

The shared file processor may detect a sharer badge through the shared file metadata and provide the number of unread file sharers to all file sharers.

The shared file processor may detect that the file is read by a specific file sharer and update the number of unread file sharers in the badge of the corresponding sharer.

The shared file processing unit may obtain a list of access history of a sharer of the file based on the badge of the sharer and provide it to the creator of the file.

The shared file processor may detect a user badge through the shared file metadata to induce a user to access the file.

The shared file processor may dynamically generate the shared file metadata when the sharing setting tag is set.

The shared file processor may update the file metadata to access the shared file metadata with a shared file pointer in the file metadata.

When the sharing setting tag is set, the shared file processing unit may detect access to the file, access implicitly through the shared file metadata, and update a user-specific access history list recording access details for each user of the file. .

When the file is changed through the access of the file, the shared file processor may update the access history list for each user and store the file before the change.

When the sharing setting tag is released, the shared file processing unit may delete the shared file metadata.

The disclosed technology can have the following effects. However, since it does not mean that a specific embodiment should include all of the following effects or only the following effects, it should not be understood that the scope of the rights of the disclosed technology is limited thereby.

The file processing apparatus based on the shared file system according to an embodiment of the present invention may classify a shared file in a file system of a user storage device and manage the shared file through shared file metadata.

The file processing apparatus based on a shared file system according to an embodiment of the present invention may record and manage information about a sharer's access to a shared file shared by a user through shared file metadata.

The file processing apparatus based on a shared file system according to an embodiment of the present invention may record and manage whether a user has access to a shared file shared or updated by a sharer.

1 is a diagram illustrating a file processing system based on a shared file system according to an embodiment of the present invention.
FIG. 2 is a block diagram illustrating a file processing apparatus based on the shared file system of FIG. 1.
3 is a block diagram illustrating a storage device of a file processing apparatus based on a shared file system according to an embodiment of the present invention.
4 is an exemplary view showing a user badge and a sharer badge displayed on a shared file according to an embodiment of the present invention.
5 is a flowchart illustrating a file processing method based on a shared file system according to an embodiment of the present invention.

Since the description of the present invention is merely an embodiment for structural or functional description, the scope of the present invention should not be construed as being limited by the embodiments described in the text. That is, since the embodiments can be variously changed and have various forms, the scope of the present invention should be understood to include equivalents capable of realizing the technical idea. In addition, since the object or effect presented in the present invention does not mean that a specific embodiment should include all or only such effects, the scope of the present invention should not be understood as being limited thereto.

Meanwhile, the meaning of terms described in the present application should be understood as follows.

Terms such as "first" and "second" are used to distinguish one component from other components, and the scope of rights is not limited by these terms. For example, a first component may be referred to as a second component, and similarly, a second component may be referred to as a first component.

When a component is referred to as being "connected" to another component, it should be understood that although it may be directly connected to the other component, another component may exist in the middle. On the other hand, when it is mentioned that a component is "directly connected" to another component, it should be understood that there is no other component in the middle. On the other hand, other expressions describing the relationship between components, that is, "between" and "just between" or "neighboring to" and "directly neighboring to" should be interpreted as well.

Singular expressions are to be understood as including plural expressions unless the context clearly indicates otherwise, and terms such as "comprises" or "have" refer to implemented features, numbers, steps, actions, components, parts, or It is to be understood that it is intended to designate that a combination exists and does not preclude the presence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

In each step, the identification code (e.g., a, b, c, etc.) is used for convenience of explanation, and the identification code does not describe the order of each step, and each step has a specific sequence clearly in the context. Unless otherwise stated, it may occur differently from the stated order. That is, each of the steps may occur in the same order as the specified order, may be performed substantially simultaneously, or may be performed in the reverse order.

The present invention can be implemented as computer-readable code on a computer-readable recording medium, and the computer-readable recording medium includes all types of recording devices storing data that can be read by a computer system. . Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tapes, floppy disks, and optical data storage devices. Further, the computer-readable recording medium is distributed over a computer system connected by a network, so that computer-readable codes can be stored and executed in a distributed manner.

All terms used herein have the same meaning as commonly understood by one of ordinary skill in the field to which the present invention belongs, unless otherwise defined. Terms defined in commonly used dictionaries should be construed as having meanings in the context of related technologies, and cannot be construed as having an ideal or excessively formal meaning unless explicitly defined in the present application.

1 is a diagram illustrating a file processing system based on a shared file system according to an embodiment of the present invention.

Referring to FIG. 1, a file processing system 100 based on a shared file system includes a file processing apparatus 110 and a user terminal 120 based on a shared file system.

The file processing device based on the shared file system (hereinafter, the file processing device 110) may classify and manage a shared file of the storage device as a non-shared file based on a sharing setting tag of file metadata associated with the file. In an embodiment, the file processing device 110 may control and manage access of a sharer by acquiring shared file metadata for a shared file for which the sharing setting is confirmed through the sharing setting tag. More specifically, the file processing device 110 may differentially grant permission for reading and writing to a shared file in the storage device 240 for each sharer, and detect the sharer's access to generate an access history list. In addition, the file processing apparatus 110 may provide a user and a sharer with a record of access to the shared file of the user and the sharer through a user badge and a sharer badge, respectively. That is, the file processing device 110 provides a user badge or a sharer badge to a user or a sharer, respectively, so that the user can know whether the user himself or another sharer has read or not read the shared file. The file processing device 110 enables effective processing of shared files by controlling and managing a file sharer based on a shared file system.

The user terminal 120 corresponds to a computing device connected to the file processing device 110 through a wired or wireless network, and may be implemented as, for example, a desktop, a laptop computer, a tablet PC, or a smartphone. The user may access the shared file through the user terminal 120 and request to read or write the shared file according to the granted permission.

FIG. 2 is a block diagram illustrating a file processing apparatus based on the shared file system of FIG. 1. 3 is a block diagram illustrating a storage device of a file processing apparatus based on a shared file system according to an embodiment of the present invention.

Referring to FIG. 2, the file processing device 110 includes a network input/output unit 210, a control unit 220, a file metadata processing unit 232, a shared file checking unit 234, and sharing in the shared file system 230. It includes a file processing unit 236, and includes a storage device 240 connected to the shared file system. 3, the storage device 240 includes a file metadata 310, a sharer access history list 330, and a user access history list 340 in the system data area, and the file metadata 310 is a file It includes an attribute 20, a sharing setting tag 30, and a shared file metadata 320.

The network input/output unit 210 includes an environment for connecting to at least one user terminal 120 and may include, for example, an adapter for LAN (Local Area Network) communication. In one embodiment, the file processing apparatus 110 may be connected to the hard disk of the user terminal 120 through the network input/output unit 210.

The control unit 220 controls the overall operation of the file processing device 110, and controls the file metadata processing unit 232, the shared file verification unit 234, and the shared file processing unit 236 inside the shared file system 230 And manage file flow.

The shared file system 230 may correspond to a file system structure capable of managing a shared file of the storage device 240 by separating it from a non-shared file. The shared file system 230 may include file metadata in system data and actual file (content) data in user data. More specifically, the shared file system 230 may manage shared files through the file metadata processing unit 232, the shared file checking unit 234, and the shared file processing unit 236.

The storage device 240 is a device that temporarily or permanently stores data in a computer, and may generally mean a nonvolatile memory device. In one embodiment, the storage device 240 is not limited to a hard disk and may correspond to a generic concept including a flash memory, USB memory, and the like. The storage device 240 may effectively process internal file metadata and shared file metadata through the shared file system 230.

The file metadata processing unit 232 may determine file metadata associated with the file. Metadata may basically mean data about data. Metadata may refer to data that is given to content (user data) according to certain rules in order to efficiently find and use the information that is being searched from among a large amount of information. That is, it may correspond to information that is followed after the data in order to analyze and classify structured information about certain data and add additional information. In one embodiment, the file metadata processing unit 232 is generally implemented similarly to an i-node corresponding to metadata of a file system, but characteristically, a sharer history list having a sharing setting tag and a permission attribute for each sharer File metadata 310 that further includes, etc. may be determined. Here, the inode may mean a data structure that is configured one for each file and has all the information for each file. For example, the inode may include information on the size, type, ownership, availability, and recent modification time of the file. More specifically, the file metadata processing unit 232 may determine the file metadata 310 including the file attribute 20 and the sharing setting tag 30 for a specific file.

The shared file checker 234 may check whether to set the sharing of the file based on the sharing setting tag 30 included in the determined file metadata 310. For example, if the file metadata 310 of the file includes the sharing setting tag 30, the shared file check unit 234 determines the file as a shared file, and if it is not included, the file is determined as a non-shared file. I can.

When the sharing setting of the file is confirmed, the shared file processing unit 236 may obtain the shared file metadata 320 that is implicitly accessed through the file metadata 310 and control access to the file according to the permission attribute of each sharer. . In one embodiment, the shared file processing unit 236 is included in the file metadata 310 by itself, or the shared file metadata 320 is used to access the file system in the system data area without a separate user accessing from the outside. Can be obtained. In an embodiment, the shared file processing unit 236 may control access to a file for a sharer according to read and write permissions for the shared file for each sharer.

In an embodiment, the shared file processing unit 236 may detect the sharer badge 322 through the shared file metadata 320 and provide the file sharer with the number of unread file sharers. Here, the sharer badge may mean a specific number displayed on the shared file, indicating the number of sharers who have not read the shared file among all sharers for each shared file. In one embodiment, the shared file processing unit 236 may update the number of unread file sharers in the corresponding sharer badge 322 by detecting that a file is read by a specific file sharer. More specifically, the shared file processing unit 236 gives the sharer badge 322 to the shared file, and updates it in real time whenever an unread sharer reads so that the sharer can check the access status of other sharers to the shared file. do.

In an embodiment, the shared file processing unit 236 may obtain the file sharer access history list 330 based on the sharer badge 322 and provide it to the creator of the file. Here, the sharer access history list 330 may correspond to a list showing a status of a shared file, such as who read or who changed it. In one embodiment, the shared file processing unit 236 may generate a sharer access history list 330 and provide it to other sharers. For example, the shared file processing unit 236 displays the read status for the sharer A who has finally updated the shared file based on the last read time, and does not read the last updated file for the sharer C who created the first file. The sharer access history list 330 may be generated to indicate the unread status of the sharer B that has read the state before the last update. That is, when the shared file is updated, the shared file processing unit 236 may detect the sharer badge 322 based on the last updated file and obtain the sharer access history list 330 based on this.

In one embodiment, the shared file processing unit 236 may detect the user badge 324 through the shared file metadata 320 to induce a user to access the file. Here, the user badge 324 may correspond to a number indicating an unread state of a shared file of a user who is one of the sharers. For example, the user badge 324 may be displayed as 1 when the user has not read the shared file. If the user reads the shared file, nothing may be displayed. In one embodiment, the shared file processing unit 236 may display the update status of the shared file through the user badge 324. More specifically, the shared file processing unit 236 may detect whether or not the shared file is updated and the number of times, and display it on the shared file through the user badge 324. For example, when the shared file is updated once after the shared file is created, the shared file processing unit 236 may display 2 on the shared file. The shared file processing unit 236 may remove the displayed number when the user reads the shared file through the user badge 324. In one embodiment, the shared file processing unit 236 may store the file before being updated when a shared file that has not been read by the user is updated once. When the user finally reads the updated file once, the shared file processing unit 236 provides the stored file before the update to the user, and may change the number displayed on the shared file from 2 to 1. Thereafter, when the user reads the shared file again, the shared file processing unit 236 may provide the updated final file to the user and remove the displayed 1.

In an embodiment, the shared file processing unit 236 may dynamically generate the shared file metadata 320 when a sharing setting tag is set. For example, when a file is created and a sharing setting tag is set to become a shared file, the shared file processing unit 236 dynamically generates the shared file metadata 320 and detects the sharer badge and the user badge for the shared file to Can be provided to. Here, the shared file metadata 320 may include a sharer badge 322, a user badge 324, a user information pointer, a sharer information pointer, and a file pointer. The user information pointer may point to a user-specific access history list, the sharer information pointer may point to a sharer access history list, and the file pointer may point to a file corresponding to user data. In an embodiment, the shared file processing unit 236 may update the file metadata to access the shared file metadata 230 with a shared file pointer in the file metadata. For example, in the process of dynamically generating the shared file metadata 320, the shared file processing unit 236 may update the file metadata 310 to access the shared file metadata 320 with a shared file pointer. .

In one embodiment, the shared file processing unit 236 detects the access of the file when the sharing setting tag is set, is accessed implicitly through the shared file metadata 320, and records the access history for each user of the file. The list 340 can be updated. That is, the shared file processing unit 236 may update a user-specific access history every time a user accesses the shared file. In an embodiment, when a file is changed through access to a file, the shared file processing unit 236 may update the user-specific access history list 340 and store the file before the change. For example, when a file is changed, the shared file processing unit 236 may initialize the user-specific access history list 340 and store the file before the change together with the previous user-specific access history list. In an embodiment, the shared file processing unit 236 may delete the shared file metadata 320 when the sharing setting tag 30 is released. The shared file processing unit 236 may change the shared file to a non-shared file by releasing the sharing setting tag 30 for the shared file according to the user's request, and at the same time delete the shared file metadata 320. In an embodiment, the shared file processing unit 236 may separately generate and store a shared data file (not shown) including the shared file metadata 320 in the process of releasing the sharing setting tag 30. For example, the shared file processing unit 236 allows the user to determine whether to generate the shared data file, and when the creation is determined, may store the shared data file for a predetermined period of time.

4 is an exemplary view showing a user badge and a sharer badge according to an embodiment of the present invention.

In an embodiment, the file processing apparatus 110 may detect a user badge indicating the number of unread files of the user for the shared folder and display the user badge on the shared folder. More specifically, the file processing apparatus 110 may detect user badges for unread files of the user in the shared folder and display them in the folder. For example, the file processing device 110 detects 3 corresponding to the sum of the user badges (unread number) for the a.doc file and the b.doc file that the user in the F3 folder has not yet read, and is next to the F3 folder. Can be marked on.
In another embodiment, the file processing device 110 may detect the number of unread files in the shared folder and display them next to the shared folder. For example, the file processing apparatus 110 may detect 2 representing the number of two files, a.doc and b.doc, which are files that the user has not read in the F3 folder, and display them next to the F3 folder.
In FIG. 4, the file processing apparatus 110 may display a sharer badge at the upper right of the shared file and a user badge at the lower part for the shared files a, b, and c. It is obvious that the display method is not limited to FIG. 4 and that various methods are possible. For example, the a.doc file corresponds to a shared file, has not been updated, the user has not read, and 9 sharers have not read the shared file. Also, in the case of b.doc file, 4 sharers did not read it, and if one update was made, the user did not read all after the update before the update. In the case of the c.doc file, the user can see that it has been read and that 9 sharers have not read it yet.

5 is a flowchart illustrating a file processing method based on a shared file system according to an embodiment of the present invention.

In FIG. 5, the file processing device 110 may determine file metadata associated with a file through the file metadata processing unit (step S510).

The file processing device 110 may check whether to set the sharing of the file based on the sharing setting tag included in the file metadata through the shared file checker (step S520).

When the sharing setting of the file is confirmed through the shared file processing unit, the file processing device 110 may acquire shared file metadata that is implicitly accessed through the file metadata, and control access to the file according to the permission attribute for each sharer ( Step S530).

Although the above has been described with reference to preferred embodiments of the present invention, those skilled in the art will variously modify and change the present invention within the scope not departing from the spirit and scope of the present invention described in the following claims. You will understand that you can do it.

100: file processing system based on shared file system
110: a file processing device based on a shared file system
120: user terminal
210: network input/output unit 220: control unit
230: shared file system 232: file metadata processing unit
234: shared file verification unit 236: shared file processing unit
240: storage device
310: File Metadata 320: Shared File Metadata
322: Sharer Badge 324: User Badge
330: sharer access history list 340: user-specific access history list

Claims (10)

A file metadata processing unit that determines file metadata associated with a file;
A shared file checking unit that checks whether or not the file is set to be shared based on a sharing setting tag included in the file metadata; And
When the sharing setting of the file is confirmed, a shared file processing unit that obtains shared file metadata that is implicitly accessed through the file metadata and controls access to the file according to the permission attribute of each sharer,
The shared file processing unit
When the sharing setting tag is set, the shared file metadata including at least a sharer badge or a user badge is dynamically generated.
The method of claim 1, wherein the shared file processing unit
A file processing apparatus based on a shared file system, characterized in that the number of unread file sharers is provided to all file sharers by detecting a sharer badge through the shared file metadata.
The method of claim 2, wherein the shared file processing unit
A file processing apparatus based on a shared file system, characterized in that by detecting that the file is read by a specific file sharer, the number of unread file sharers in the badge of the corresponding sharer is updated.
The method of claim 3, wherein the shared file processing unit
A file processing apparatus based on a shared file system, characterized in that, based on the sharer badge, a list of access history of a sharer of the file is obtained and provided to a creator of the file.
The method of claim 1, wherein the shared file processing unit
A file processing apparatus based on a shared file system, characterized in that inducing access to the file to a user by detecting a user badge through the shared file metadata.
delete The method of claim 1, wherein the shared file processing unit
And updating the file metadata to access the shared file metadata with a shared file pointer in the file metadata.
The method of claim 1, wherein the shared file processing unit
When the sharing setting tag is set, the access history list for each user is updated by detecting the access of the file, accessing it implicitly through the shared file metadata, and recording the access details for each user of the file. Based file handling unit.
The method of claim 8, wherein the shared file processing unit
When the file is changed through access to the file, the file before the change is stored together with the update of the access history list for each user.
The method of claim 1, wherein the shared file processing unit
When the sharing setting tag is released, the shared file metadata is deleted.

Images