JP2012238113A - File management device, file management method, and file management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To realize sound distribution of files.SOLUTION: A file management device registers derivative information of each file, the information including identification information of a user using a user terminal in which a file operation is performed, and attribute information of a file derived from the file operation in a storage part, for each file operation on the user terminal. When receiving a predetermined file operation such as mail transmission, the file management device specifies a derivative source of the file on the basis of the derivative information registered in the storage part. The file management device notifies a user of a permission request for the mail transmission, the user corresponding to the identification information of the derivative source of the specified file. When receiving the permission for the mail transmission from the user terminal used by the user corresponding to the identification information of the derivative source of the file, the file management device performs control processing to permit the mail transmission of the file.

Description

  The present invention relates to a file management apparatus, a file management method, and a file management program.

  Conventionally, for file distribution, for example, an e-mail file attachment function or a file transfer system that can deliver files by uploading to a server may be used. Such a file may be derived at the stage of distribution due to modification of the file contents or change of the file name. For this reason, from the viewpoint of protecting a file by copyright, a user who receives a file may obtain permission to send to the user who created or modified the file when sending the file to a third party. preferable.

  Regarding obtaining permission, recently, when applying for registration of a file to be shared in the company system to the server, the department head who requests approval is identified by tracing back the hierarchical tree structure in which the hierarchy of the department is expressed and specified. There is a technology to obtain permission from the assigned head.

JP 2009-258907 A

  However, the above-described conventional technique has a problem that sound distribution of files cannot be realized. For example, when a file is sent to a third party by a user who receives the file, the user can specify the user who sent the file, but not all users who created or modified the file. Have difficulty. In addition, it is difficult to apply a technique for registering a file shared in an in-company system to a server for distribution of files between users whose vertical relationship by job title or connection by department is not particularly determined. As a result, the conventional technology cannot realize the sound distribution of files.

  Therefore, the present invention has been made in view of the above, and an object of the present invention is to provide a file management apparatus, a file management method, and a file management program capable of realizing sound distribution of files.

  In order to solve the above-described problems and achieve the object, the file management device includes identification information of a user who uses the user terminal that performed the file operation for each file operation by the user terminal, and is derived by the file operation. Derived information registration unit for registering derivation information including attribute information of the file in the storage unit for each file, and derivation information registered in the storage unit by the derivation information registration unit when a request for a predetermined file operation is received And a request for permission to perform the predetermined file operation to a user corresponding to the identification information of the derivation source of the file specified by the derivation source specification unit. From the permission request notifying unit to notify, and the user terminal used by the user corresponding to the identification information of the derivation of the file, When receiving the permission of the constant file operations, and a file operation control unit that controls to allow file operation corresponding file.

  According to one aspect of the file management apparatus, the file management method, and the file management program, there is an effect that sound distribution can be realized.

FIG. 1 is a diagram illustrating a configuration example of a file distribution management system. FIG. 2 is a diagram illustrating an example of functional blocks of the file management apparatus according to the first embodiment. FIG. 3 is a diagram illustrating an example of information stored in the derived information storage unit. FIG. 4 is a diagram illustrating an example of a tree structure related to derivation information. FIG. 5 is a diagram for explaining processing for specifying a file derivation source. FIG. 6 is a flowchart illustrating an example of the flow of the file status management process according to the first embodiment. FIG. 7 is a flowchart illustrating an example of a flow of file transmission processing according to the first embodiment. FIG. 8 is a diagram showing that the processing by the file management program is specifically realized using a computer.

  Hereinafter, embodiments of a file management apparatus, a file management method, and a file management program will be described with reference to the accompanying drawings. In addition, this invention is not limited by the following examples.

[System configuration]
The configuration of the file distribution management system will be described with reference to FIG. FIG. 1 is a diagram illustrating a configuration example of a file distribution management system. In the following, a file distribution management system employing a thin client system will be described as an example. That is, the file is distributed in the file distribution management system.

  For example, as shown in FIG. 1, the file distribution management system includes a file creation system, a mail system, a file status management system, and a center server that operate on the virtual desktop system. Similarly, the file distribution management system includes user terminals such as a user terminal A, a user terminal B, and a user terminal C. The number of user terminals is not limited to the number shown. The file management apparatus disclosed in the present application includes, for example, the file status management system and the center server shown in FIG.

  In the above configuration, each user terminal executes a file operation by using a file creation system or a mail system via a virtual desktop system, for example. Here, the virtual desktop system is a kind of software that extends the desktop environment of a computer as one aspect, and provides a plurality of independent virtual desktop environments, a continuous desktop space wider than the display area, and the like. . Specifically, each user terminal executes file operations such as file creation, modification, name change, deletion, or directory movement using a file creation system. Further, each user terminal executes a file operation for transmitting / receiving a mail with a file attached thereto using a mail system.

  In addition, the file creation system that has executed the file operation, for example, every time a file is created, modified, renamed, deleted, or moved to a directory, the user who uses the time, file name, file hash value, and user terminal that performed the file operation The file status management system is notified of the address corresponding to. Similarly, a mail system that has executed a file operation manages, for example, the time, the file name, the hash value of the file, the address corresponding to the user who uses the user terminal that performed the file operation, etc. Notify the system.

  For example, the file status management system acquires information on the derivation of the processed file based on the processing in the file creation system or the mail system, and registers the acquired information in the center server. Here, the information related to the derivation of the processed file refers to file attribute information that occurs in each process such as file creation, modification, name change, deletion, directory movement, transmission, or reception. Such file attribute information indicates, for example, a time, a file name, a hash value, an address, and the like for each file creation, modification, name change, deletion, directory movement, transmission or reception. Hereinafter, the file attribute information may be described as derivative information.

  More specifically, the file state management system acquires derivative information generated for each process such as file creation, modification, name change, deletion, or directory move based on the process in the file creation system. Then, the file state management system registers the acquired derivative information in the center server. Similarly, the file status management system acquires derivative information generated for each processing such as transmission or reception of a file based on processing in the mail system. Then, the file state management system registers the acquired derivative information in the center server. Note that processing by the file management apparatus and derived information will be described later.

[Configuration of file management device]
Next, functional blocks of the file management apparatus according to the first embodiment will be described with reference to FIG. FIG. 2 is a diagram illustrating an example of functional blocks of the file management apparatus according to the first embodiment. Further, as described above, the file management apparatus includes the file state management system and the center server shown in FIG. For example, as illustrated in FIG. 2, the file management apparatus 100 includes a storage unit 110 and a control unit 120.

  The storage unit 110 stores, for example, data required for various types of processing by the control unit 120 and various types of processing results by the control unit 120, and includes a derivation information storage unit 111. The storage unit 110 is, for example, a semiconductor memory device such as a random access memory (RAM), a read only memory (ROM), and a flash memory, or a storage device such as a hard disk or an optical disk.

  The control unit 120 includes, for example, a control program, a program defining various processing procedures, and an internal memory for storing required data. The control unit 120 includes a derivation information registration unit 121, a derivation source identification unit 122, a permission request notification unit 123, and a file operation control unit 124. The control unit 120 is an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array), or an electronic circuit such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit).

  For example, the derivation information registration unit 121 includes, for each file operation by the user terminal, the identification information including the identification information of the user who uses the user terminal that performed the file operation and the attribute information of the file derived by the file operation. Each is registered in the derivative information storage unit 111. Specifically, the derivation information registration unit 121 detects that a file operation has occurred due to file I / O (Input / Output) or the like in the file creation system, and acquires the derivation information of the corresponding file from the file creation system. Then, the derivation information registration unit 121 registers the acquired derivation information in the derivation information storage unit 111. Here, the derivation information acquired from the file creation system includes, for example, “time”, “file name”, “file name” for each file creation, modification, name change, deletion, or directory move that is the “status” of the file. Hash value ”,“ operator address ”, and the like. The “operator address” included in the derived information is an example of identification information of a user who uses the user terminal that performed the file operation.

  Similarly, the derivation information registration unit 121 detects that a file operation has occurred due to mail transmission / reception or the like in the mail system, and acquires the derivation information of the file from the mail system. Then, the derivation information registration unit 121 registers the acquired derivation information in the derivation information storage unit 111. Here, the derivative information acquired from the mail system is, for example, “time”, “file name”, “hash value”, “operator address”, etc., for each transmission or reception of the file that is the “state” of the file. Is mentioned. When the derivation information registration unit 121 detects that a file operation for mail transmission has occurred in the mail system, the derivation source identification unit 121 indicates that the file operation for mail transmission has occurred, along with the derivation information of the corresponding file. 122 is notified.

  Here, the information stored in the derivative information storage unit 111 will be described with reference to FIG. FIG. 3 is a diagram illustrating an example of information stored in the derived information storage unit 111. For example, the derivation information storage unit 111 stores the derivation information registered by the derivation information registration unit 121 for each file.

  For example, as shown in FIG. 3, the derivation information storage unit 111 includes “time” indicating the date and time when the file operation was performed, “file name” indicating the file name of the file operated file, and the file operated file. A “hash value” indicating a hash value is stored in association with each other. In addition, the derivation information storage unit 111 stores a “status” indicating the status of the file operation and an “operator address” indicating an address corresponding to the user who uses the user terminal that has operated the file.

  For example, the derivation information storage unit 111 includes the item number “1”, the time “2011.1.3.10.10: 23: 44”, the file name “aaa”, the hash value “233458”, the status “Create” and operator address “A” are stored in association with each other. In addition, the derivative information storage unit 111 stores the item number “2”, the time “2011.11.10: 12: 33: 43”, the file name “aaa”, the hash value “133333”, and the state “modified”. And the operator address “A” are stored in association with each other. In addition, the derivation information storage unit 111 includes the item number “3”, the time “2011.3.110: 12: 33: 50”, the file name “aaa1”, the hash value “133333”, and the state “name change”. And the operator address “A” are stored in association with each other.

  In addition, the derivation information storage unit 111 stores the item number “4”, the time “2011.3.110.12:35:00”, the file name “aaa1”, the hash value “133333”, and the state “transmission”. And the operator address “A” are stored in association with each other. In addition, the derivation information storage unit 111 stores the item number “5”, the time “2011.10.15: 20: 00”, the file name “aaa1”, the hash value “133333”, and the state “reception”. And the operator address “B” are stored in association with each other.

  That is, in the example of FIG. 3, in the use of the file distribution management system by the user terminal used by the user having the operator address “A”, a file was created at 10:23:44 on March 10, 2011. I understand. Further, it can be seen that the created file has the file name “aaa” and the hash value “233458”.

  Similarly, in the example of FIG. 3, in the use of the file distribution management system by the user terminal used by the user having the operator address “A”, the file is modified at 12:33:43 on March 10, 2011. You can see that Further, it can be seen that the modified file has a file name “aaa” and a hash value “133333”. Similarly, in the example of FIG. 3, in the use of the file distribution management system by the user terminal used by the user having the operator address “A”, the file name is changed at 12:33:50 on March 10, 2011. You can see that it was done. Further, it can be seen that the renamed file has the file name “aaa1” and the hash value “133333”.

  Similarly, in the example of FIG. 3, in the use of the file distribution management system by the user terminal used by the user having the operator address “A”, the file is transmitted at 12:35:00 on March 10, 2011. You can see that Further, it can be seen that the transmitted file has the file name “aaa1” and the hash value “133333”. Similarly, in the example of FIG. 3, when the file distribution management system is used by the user terminal used by the user having the operator address “B”, the file is received at 15:20:00 on March 10, 2011. You can see that The received file has a file name “aaa1” and a hash value “133333”.

  As shown in FIG. 3, the hash value is changed when the name is changed, but is not changed when the name is changed. That is, when the name is changed, the hash value is not changed because the content of the file itself is not changed.

  In addition, the derivation information registration unit 121, when registering the acquired derivation information in the derivation information storage unit 111, has a tree structure in which a creation source file is used as a vertex node and the derived file is hierarchized as each node over time. You may register by. FIG. 4 is a diagram illustrating an example of a tree structure related to derivation information. For example, as shown in FIG. 4, the tree structure related to the derivation information is hierarchized with the creation source file as a vertex node and the derived file as each node for each operator address with time. In FIG. 4, “file name” and “hash value” are represented in the image of each node.

For example, the example of FIG. 4 indicates that a file having the file name “A ₁ ” and the hash value “344689” is created by the use of the user terminal by the user corresponding to the operator address “B”. The file created by using the user terminal by the user corresponding to the operator address “B” is transmitted to the user having the operator address “A” after being modified twice. A file created by using the user terminal by the user corresponding to the operator address “B” is copied after being modified once, modified, renamed, etc., and the file name “D ₁ ”, hash value is obtained. “557890”.

At this time, after modification or name change, the file having the file name “B ₁ ” and the hash value “11267” is transmitted to the user having the operator address “C”. In addition, when the user corresponding to the operator address “C” uses the user terminal, the name is changed, copied or deleted. In FIG. 4, it can be seen that in “copy”, a file having the same content as the copy source file has been created and the file name has been changed.

  Returning to the description of FIG. 2, when the derivation source specifying unit 122 receives a request for a predetermined file operation, for example, the derivation source specifying unit 122 corresponds to the derivation information registered in the derivation information storage unit 111 by the derivation information registration unit 121. Identify the source of the file. Specifically, the derivation source identification unit 122 accepts that a file operation for mail transmission has occurred by the derivation information registration unit 121. The derivation source identification unit 122 identifies the derivation source of the corresponding file by tracing back from the information stored in the derivation information storage unit 111 from the same information as the operator address, file name, and hash value of the corresponding file. To do.

  Here, the process of specifying the derivation source of the corresponding file will be described with reference to FIG. FIG. 5 is a diagram for explaining processing for specifying a file derivation source. Here, as shown in FIG. 5, the derivation information registration unit 121 registers the nodes (A) to (G) including the derivation information for each operator address corresponding to each user in chronological order. Go.

  That is, in the example of FIG. 5, the file with the file name “aaa” and the hash value “233458” has been created in the use of the file distribution management system by the user terminal used by the user with the operator address “A”. I understand. Similarly, in the example of FIG. 5, in the use of the file distribution management system by the user terminal used by the user having the operator address “A”, the file having the file name “aaa” is modified and the hash value is “233458”. It turns out that it became "133333".

  Similarly, in the example of FIG. 5, in the use of the file distribution management system by the user terminal used by the user having the operator address “A”, the file name “aaa” is renamed, and the file name is changed. It can be seen that “aaa” has changed to “aaa1”. Similarly, in the example of FIG. 5, in the use of the file distribution management system by the user terminal used by the user with the operator address “A”, the file with the file name “aaa1” is the operator address “B”. It turns out that it transmitted to the user terminal.

  Similarly, in the example of FIG. 5, in the use of the file distribution management system by the user terminal used by the user with the operator address “B”, the file with the file name “aaa1” is the operator address “A”. It can be seen that it was received from the user terminal. Similarly, in the example of FIG. 5, in the use of the file distribution management system by the user terminal used by the user having the operator address “B”, the file having the file name “aaa1” is modified and the hash value is “133333”. It turns out that it became "322493".

  Similarly, in the example of FIG. 5, in the use of the file distribution management system by the user terminal used by the user having the operator address “B”, the file name “aaa1” is renamed and the file name is changed. It can be seen that “aaa1” is changed to “aaa2”. Similarly, in the example of FIG. 5, in the use of the file distribution management system by the user terminal used by the user with the operator address “B”, the file with the file name “aaa2” is the operator address “C”. You can see that it was sent to the user.

  Similarly, in the example of FIG. 5, in the use of the file distribution management system by the user terminal used by the user with the operator address “C”, the file with the file name “aaa2” is the operator address “B”. It can be seen that it was received from the user terminal used by the user. In the tree structure related to the derivative information shown in FIG. 5, nodes are registered as time passes, so that “time” does not have to be held in each node.

  Hereinafter, a case where the file having the operator address “C”, the file name “aaa2”, and the hash value “322493” illustrated in FIG. 5G is transmitted to another user terminal will be described as an example.

  For example, when the file corresponding to FIG. 5G is transmitted, the derivation source identification unit 122 sets the hash value “322493” as the hash value after derivation, and whether or not the hash value “322493” matches. Go back through the tree structure while judging. That is, the derivation source identification unit 122 determines that the hash value “322493” after derivation matches the hash value “322493” of the files shown in FIGS. 5 (F) and 5 (E). Subsequently, the derivation source identification unit 122 does not match the hash value “322493” after derivation with the hash value “133333” of the file shown in FIG. In E), it is recognized that the file has been altered. That is, the derivation source identification unit 122 derives the file in FIG. 5D at the operator address “B” as the corresponding file has been modified by the user terminal used by the user corresponding to the operator address “B”. Identify as one of the original.

  Further, the derivation source specifying unit 122 sets the hash value “133333” of the file shown in FIG. 5D as a newly derived hash value, and determines whether or not the hash value “133333” matches. Go back further in structure. That is, the derivation source identification unit 122 determines that the hash value “133333” after derivation matches the hash value “133333” of the files illustrated in FIGS. 5C and 5B. Subsequently, the derivation source identification unit 122 does not match the hash value “133333” after derivation with the hash value “233458” of the file shown in FIG. In B), it is recognized that the file has been altered. That is, the derivation source specifying unit 122 derives the file in FIG. 5A at the operator address “A” as the corresponding file has been modified by the user terminal used by the user corresponding to the operator address “A”. Identify as one of the original.

  In addition, the derivation source identification unit 122 sets the hash value “233458” of the file shown in FIG. 5A as a new derivation hash value and determines whether or not the hash value “233458” matches the tree value. Go back further in structure. At this time, the derivation source specifying unit 122 cannot go back beyond FIG. 5A, and recognizes that the file has been created in FIG. That is, the derivation source identification unit 122 derives the file in FIG. 5A at the operator address “A” as the corresponding file has been created by the user terminal used by the user corresponding to the operator address “A”. It is specified as one of the originals (in detail, the creator).

  By the way, in the above example, an example in which the tree structure is traced using only the hash value has been described, but the derivation source identification unit 122 may trace the tree structure further using the file name. For example, when a file corresponding to FIG. 5G is transmitted, the derivation source identification unit 122 matches the hash value “322493” and the file name “aaa2” as the hash value and file name after derivation. The tree structure is traced while determining whether or not to do so. That is, the derivation source identification unit 122 matches the hash value “322493” and the file name “aaa2” after derivation with the hash value “322493” and the file name “aaa2” of the file shown in FIG. Determine. Subsequently, the derivation source specifying unit 122 does not match the file name “aaa2” after derivation with the file name “aaa1” of the file shown in FIG. In F), it is recognized that the file has been renamed. That is, the derivation source specifying unit 122 assumes that the name of the file has been changed by the user terminal used by the user corresponding to the operator address “B”, and the operator address “B” in FIG. Identify the file as one of the sources.

  Further, the derivation source identification unit 122 sets whether the hash value “322493” and the file name “aaa1” of the file shown in FIG. Go back through the tree structure while judging. That is, the derivation source specifying unit 122 does not match the hash value “322493” after derivation with the hash value “133333” of the file shown in FIG. ) To recognize that the file has been altered. That is, the derivation source identification unit 122 derives the file in FIG. 5D at the operator address “B” as the corresponding file has been modified by the user terminal used by the user corresponding to the operator address “B”. Identify as one of the original.

  Further, the derivation source identification unit 122 sets whether or not the hash value “133333” and the file name “aaa1” of the file shown in FIG. Go back through the tree structure while judging. That is, the derivation source identification unit 122 matches the hash value “133333” and the file name “aaa1” after derivation with the hash value “133333” and the file name “aaa1” of the file shown in FIG. Determine. Subsequently, the derivation source identifying unit 122 does not match the file name “aaa1” after derivation with the file name “aaa” of the file shown in FIG. In C), it is recognized that the file has been renamed. That is, the derivation source specifying unit 122 assumes that the file has been renamed by the user terminal used by the user corresponding to the operator address “A”, and the file in FIG. Specify as one of the derivation sources.

  Further, the derivation source identification unit 122 sets whether or not the hash value “133333” and the file name “aaa” of the file shown in FIG. Go back through the tree structure while judging. That is, the derivation source specifying unit 122 does not match the hash value “133333” after derivation with the hash value “233458” of the file shown in FIG. ) To recognize that the file has been altered. That is, the derivation source specifying unit 122 derives the file in FIG. 5A at the operator address “A” as the corresponding file has been modified by the user terminal used by the user corresponding to the operator address “A”. Identify as one of the original.

  In addition, the derivation source identification unit 122 sets whether the hash value “233458” and the file name “aaa” of the file shown in FIG. Go back through the tree structure while judging. At this time, the derivation source specifying unit 122 cannot go back beyond FIG. 5A, and recognizes that the file has been created in FIG. That is, the derivation source identification unit 122 derives the file in FIG. 5A at the operator address “A” as the corresponding file has been created by the user terminal used by the user corresponding to the operator address “A”. It is specified as one of the originals (in detail, the creator).

  Accordingly, when the file shown in FIG. 5G is transmitted by the user terminal used by the user corresponding to the operator address “C”, the derivation source specifying unit 122 uses the operator as the derivation source of the corresponding file. The file at the address “B” and the operator address “A” is specified. In addition, when the file shown in FIG. 5F is transmitted by the user terminal used by the user corresponding to the operator address “B”, the derivation source specifying unit 122 uses the operator address as the derivation source of the corresponding file. The file in “A” is specified. In addition, when the file shown in FIG. 5C is transmitted by the user terminal used by the user corresponding to the operator address “A”, the derivation source specifying unit 122 uses the operator address as the derivation source of the corresponding file. The file in “A” is specified.

  For example, the permission request notifying unit 123 notifies the user corresponding to the identification information of the derivation source of the file specified by the derivation source specifying unit 122 to a permission request for a predetermined file operation. Specifically, the permission request notification unit 123 transmits a mail transmission permission request for the corresponding file to the operator address corresponding to the derivation source of the file identified by the derivation source identification unit 122 using the mail system. To do. The permission request notifying unit 123 notifies the file operation control unit 124 of all the operator addresses that have transmitted the permission request after transmitting the mail transmission permission request using the mail system.

  That is, when the file shown in FIG. 5G is transmitted, the permission request notification unit 123 sends a transmission permission request for the corresponding file to the operator address “B” and the operator address “A”. Send using. Further, when the file shown in FIG. 5F is transmitted, the permission request notification unit 123 transmits a transmission permission request for the corresponding file to the operator address “A” using the mail system. Further, when the file shown in FIG. 5C is transmitted, the permission request notifying unit 123 matches the operator address “A” for transmitting the file and the derivation source operator address “A”. Therefore, the transmission permission request for the corresponding file is not transmitted. In other words, the permission request notification unit 123 transmits a transmission permission request for the corresponding file to a derivation source operator address that does not match the operator address that transmits the file and the derivation source operator address.

  For example, when the file operation control unit 124 receives permission for a predetermined file operation from a user terminal used by the user corresponding to the identification information of the derivation source of the file, the file operation control unit 124 permits the file operation of the corresponding file. To control. Specifically, after the permission request notification unit 123 notifies the permission request, the file operation control unit 124 is notified from the user terminal used by the user corresponding to the identification information of the file derivation source, that is, the permission request notification unit 123. Information on permission to send mail is received from the user terminal used by the user corresponding to the operator address. Then, when the file operation control unit 124 receives information that permits mail transmission from all the operator addresses notified from the permission request notification unit 123, the file operation control unit 124 controls the mail system to perform mail transmission of the corresponding file. Against. On the other hand, the file operation control unit 124 performs control to stop the mail transmission of the corresponding file when any information that does not permit the mail transmission is received. Further, the file operation control unit 124 transmits the mail of the corresponding file without accepting the permission for mail transmission when the match with the operator address that transmits the corresponding file is only the operator address of the creation source. The mail system is controlled to execute.

[File Status Management Processing According to Embodiment 1]
Next, file state management processing according to the first embodiment will be described with reference to FIG. FIG. 6 is a flowchart illustrating an example of the flow of the file status management process according to the first embodiment. Note that the file status management processing mainly refers to processing by the derived information registration unit 121.

  For example, as shown in FIG. 6, the derivation information registration unit 121 determines whether or not a file operation has occurred due to file I / O or the like in the file creation system (step S101). At this time, when the derivation information registration unit 121 detects that a file operation has occurred (Yes in step S101), the derivation information registration unit 121 acquires the derivation information of the corresponding file from the file creation system, and the derivation information storage unit 111 acquires the acquired derivation information. (Step S102). On the other hand, when the derivation information registration unit 121 does not detect that a file operation has occurred (No in step S101), the derivation information registration unit 121 executes the process of step S103.

  Then, the derivative information registration unit 121 determines whether or not a file operation has occurred due to mail transmission / reception in the mail system (step S103). At this time, when the derivation information registration unit 121 detects that a file operation has occurred (Yes in step S103), the derivation information registration unit 121 acquires the derivation information of the corresponding file from the mail system and stores the acquired derivation information in the derivation information storage unit 111. Registration is performed (step S104). On the other hand, when the derivation information registration unit 121 does not detect that a file operation has occurred (No at Step S103), the derivation information registration unit 121 executes the process at Step S101. The derivative information registration unit 121 repeatedly executes the above process.

[File Transmission Processing According to Embodiment 1]
Next, a file transmission process according to the first embodiment will be described with reference to FIG. FIG. 7 is a flowchart illustrating an example of a flow of file transmission processing according to the first embodiment. The file transmission processing mainly refers to processing by the derivation source identification unit 122, the permission request notification unit 123, and the file operation control unit 124.

  For example, as illustrated in FIG. 7, the derivation source identification unit 122 determines whether a file operation for mail transmission has been received from the derivation information registration unit 121 (step S201). At this time, when the derivation source specifying unit 122 accepts a file operation for mail transmission (Yes in step S201), the derivation source specifying unit 122 traces the derivation information stored in the derivation information storage unit 111 and specifies the derivation source of the corresponding file (step S201). S202). On the other hand, if the derivation source identification unit 122 has not received a file operation for mail transmission (No in step S201), the derivation source identification unit 122 enters a state of waiting for reception of the file operation for mail transmission.

  Then, the permission request notification unit 123 determines whether or not the derivation source operator address that matches the operator address corresponding to the file is only the operator address corresponding to the creation source file (step S203). ). At this time, if the permission request notifying unit 123 determines that it is not only the operator address corresponding to the creation source file (No in step S203), the permission request notification unit 123 sends a transmission permission request for the file to each of the derivation source operator addresses. Transmit (step S204). On the other hand, the permission request notifying unit 123 requests the file operation control unit 124 to execute the process of step S206 when it is determined that only the operator address corresponding to the creation source file matches (Yes in step S203). That is, when the file operation control unit 124 is requested to execute the process from the permission request notification unit 123, the file operation control unit 124 controls the mail system to execute mail transmission of the corresponding file (step S206).

  Further, the file operation control unit 124 determines whether or not the information permitting transmission is received from the user terminal used by the user corresponding to the corresponding operator address after the transmission permission request is transmitted by the permission request notifying unit 123. (Step S205). At this time, when the file operation control unit 124 receives information permitting transmission (Yes in step S205), the file operation control unit 124 performs control for executing mail transmission of the file on the mail system (step S206). On the other hand, when the file operation control unit 124 receives information that does not permit transmission (No at Step S205), the file operation control unit 124 requests the derivation source specifying unit 122 to execute the process at Step S201. Note that the derivation source identification unit 122, the permission request notification unit 123, and the file operation control unit 124 repeatedly execute the above processing.

[Effects of Example 1]
As described above, the file management apparatus 100 identifies a file derivation source at the time of file transmission based on the file derivation information registered for each file operation, and grants transmission permission to the user corresponding to the identified derivation source. Send file when notified and approved. As a result, the file management apparatus 100 is more difficult to identify all the users who have modified the file, and it is difficult to apply it to the distribution of files between users. Sound distribution can be realized.

  Further, the file management apparatus 100 expresses the derivation information in a tree structure and specifies the derivation source of the file based on the hash value or file name of the file. Therefore, the file management device 100 preferably specifies the file creation source or the modified user terminal. be able to.

  Although the embodiments of the file management apparatus 100 disclosed in the present application have been described so far, the present invention may be implemented in various different forms other than the embodiments described above. Therefore, (1) transmission permission request setting, (2) derivation source specific conditions, (3) file access, (4) information used for derivation source identification, (5) configuration, (6) program, different implementations An example will be described.

(1) Setting of transmission permission request In the above embodiment, the case where a transmission permission request is transmitted to a user corresponding to the specified derivation source has been described. good. For example, each user using each user terminal sets whether or not transmission permission for the file is required when the file is altered or renamed. Then, the setting information as to whether or not transmission permission is required is notified to the file management apparatus 100 together with the derivative information by the file creation system. At this time, the file management apparatus 100 also registers, in the derivative information storage unit 111, setting information indicating whether transmission permission is required when the derivative information is registered.

  Thereafter, when transmitting a transmission permission request, the file management apparatus 100 refers to setting information as to whether or not transmission permission is required, and transmits a transmission permission request to an operator address that is set to require transmission permission. To do. That is, the user who is the target of transmitting the transmission permission request indicates the user who requests transmission of the transmission permission request. As a result, the file management apparatus 100 does not have to send a request for permission to send a file that does not need to set a copyright, so the processing load can be reduced. Further, the file management apparatus 100 can reduce a complicated process of accepting a transmission permission request for a user who does not want to set a copyright.

  In addition, the transmission permission request may be set not only by each user but also by the system in advance. For example, it is set to send a transmission permission request only to the user corresponding to the file creation source, or to send a transmission permission request to the user corresponding to the file creation source and / or modification source. Sometimes.

(2) Conditions for Deriving Source Specification In the above embodiment, the case where the derivation source is specified on the condition whether or not the hash value and the file name match is described. It may be set in advance whether the condition until the file names match is a condition. In short, it can be determined by setting the file distribution management system whether or not to rename a file until the file is renamed.

(3) File Access In the above-described embodiment, the process related to the transmission permission of file mail transmission in the thin client system has been described. However, the process related to file access may be executed. For example, when the file management apparatus 100 detects a file operation for file access, the file management apparatus 100 identifies the derivation source of the corresponding file and notifies an access permission request, and when the permission is obtained, enables the file access to the corresponding file. Control. That is, the file management apparatus 100 executes a process of identifying a file derivation source and obtaining permission for a user corresponding to the identified derivation source when obtaining some permission regarding the file operation.

(4) Information used for specifying the derivation source In the above embodiment, the hash value and the file name have been described as examples of information used for specifying the derivation source of the file. However, the information is stored in the derivation information storage unit 111. “Status” information may be used. For example, when the file management apparatus 100 goes back through the tree structure to identify the derivation source, if there is information of “modification” or “name change”, the file management device 100 identifies the file there as the derivation source, and the corresponding operator A transmission permission request is transmitted to the address.

(5) Configuration In addition, information including processing procedures, control procedures, specific names, various data, parameters, and the like shown in the document and drawings (for example, information stored in the derivative information storage unit 111) Can be arbitrarily changed unless otherwise specified. For example, the information stored in the derivation information storage unit 111 is changed according to information used for derivation source identification. Specifically, the derivation information storage unit 111 may be different between when a hash value or a file name is used for derivation source identification and when a modification or a name change that is a file state is used. The derivative information storage unit 111 may also include setting information for a transmission permission request.

  Each component of the illustrated file management apparatus 100 is functionally conceptual and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to the one shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various burdens or usage conditions. Can be integrated. For example, a “state determination unit” for determining the state of the file operation is provided, and the derivation information registration unit 121, the derivation source identification unit 122, and the file operation control unit 124 are requested to start processing depending on the state of the file operation. Also good.

  Each processing function performed in the file management apparatus 100 is realized entirely or arbitrarily by a CPU (Central Processing Unit) and a program that is analyzed and executed by the CPU, or by wired logic. It can be realized as hardware.

(6) Program FIG. 8 is a diagram showing that the processing by the file management program is specifically realized using a computer. As illustrated in FIG. 8, the computer 1000 includes, for example, a memory 1001, a CPU 1002, a hard disk drive interface 1003, a disk drive interface 1004, a serial port interface 1005, a video adapter 1006, and a network interface 1007. These units are connected by a bus 1008.

  As illustrated in FIG. 8, the memory 1001 includes a ROM (Read Only Memory) 1001a and a RAM (Random Access Memory) 1001b. The ROM 1001a stores a boot program such as BIOS (Basic Input Output System). The hard disk drive interface 1003 is connected to the hard disk drive 1009 as illustrated in FIG. The disk drive interface 1004 is connected to the disk drive 1010 as illustrated in FIG. For example, a removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive 1010. The serial port interface 1005 is connected to, for example, a mouse 1011 and a keyboard 1012 as illustrated in FIG. The video adapter 1006 is connected to a display 1013, for example, as illustrated in FIG.

  Here, as illustrated in FIG. 8, the hard disk drive 1009 stores, for example, an OS (Operating System) 1009a, an application program 1009b, a program module 1009c, and program data 1009d. That is, the file management program is stored in, for example, the hard disk drive 1009 as a program module 1009c in which a command to be executed by the computer 1000 is described. Specifically, a derivation information registration procedure for executing processing similar to that of the derivation information registration unit 121 described in the above embodiment, a derivation source specifying procedure for executing processing similar to that of the derivation source specifying unit 122, and a permission request notification The hard disk drive 1009 stores a program module 1009c in which a permission request notification procedure for executing processing similar to that of the unit 123 and a file operation control procedure for executing processing similar to that of the file operation control unit 124 are described. Further, like data stored in the derivative information storage unit 111 described in the above embodiment, data used for processing by the file management program is stored as, for example, the hard disk drive 1009 as program data 1009d. The CPU 1002 reads the program module 1009c and program data 1009d stored in the hard disk drive 1009 to the RAM 1001b as necessary, and executes a derivation information registration procedure, a derivation source identification procedure, a permission request notification procedure, and a file operation control procedure. .

  Note that the program module 1009c and the program data 1009d related to the file management program are not limited to being stored in the hard disk drive 1009, but are stored in, for example, a removable storage medium and read out by the CPU 1002 via the disk drive 1010 or the like. May be. Alternatively, the program module 1009c and the program data 1009d related to the file management program are stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.), and the network interface 1007 is stored. Via the CPU 1002.

DESCRIPTION OF SYMBOLS 100 File management apparatus 110 Storage part 111 Derived information storage part 120 Control part 121 Derived information registration part 122 Derived origin specific | specification part 123 Permit request notification part 124 File operation control part

Claims (7)

For each file operation by the user terminal, registration information including identification information of a user who uses the user terminal that performed the file operation and including attribute information of the file derived by the file operation is registered in the storage unit for each file. Derived information registration part,
When receiving a request for a predetermined file operation, a derivation source specifying unit that specifies a derivation source of the corresponding file based on the derivation information registered in the storage unit by the derivation information registration unit;
A permission request notifying unit for notifying the permission request for the predetermined file operation to the user corresponding to the identification information of the derivation source of the file specified by the derivation source specifying unit;
A file operation control unit that controls to permit the file operation of the corresponding file when the permission of the predetermined file operation is received from the user terminal used by the user corresponding to the identification information of the derivation source of the file; A file management apparatus comprising: The derivation information registration unit registers information including a hash value of a file in the storage unit as the derivation information,
The derivation source specifying unit specifies a derivation source of the corresponding file according to whether the hash value of the file registered in the storage unit by the derivation information registration unit matches the hash value after derivation of the corresponding file. The file management apparatus according to claim 1. The derivation information registration unit registers information including a file name of a file in the storage unit as the derivation information,
The derivation source specifying unit specifies a derivation source of the corresponding file based on whether the file name of the file registered in the storage unit by the derivation information registration unit matches the file name after derivation of the corresponding file. The file management apparatus according to claim 2. The derivation information registration unit registers the derivation information in a storage unit with a tree structure in which the creation source file is a vertex node and the derived file is hierarchized as each node over time,
The file according to any one of claims 1 to 3, wherein the derivation source specifying unit specifies a derivation source of the corresponding file by tracing back the tree structure from a node corresponding to the corresponding file. Management device.   The permission request notifying unit sends the predetermined request to a user who is set to be notified of the predetermined file operation permission request among the users corresponding to the identification information of the derivation source of the file specified by the derivation source specifying unit. The file management apparatus according to claim 1, wherein a file operation permission request is notified. A file management method executed by a file management device,
For each file operation by the user terminal, registration information including identification information of a user who uses the user terminal that performed the file operation and including attribute information of the file derived by the file operation is registered in the storage unit for each file. Derived information registration process,
When a request for a predetermined file operation is received, a derivation source specifying step for specifying a derivation source of the corresponding file based on the derivation information registered in the storage unit by the derivation information registration step;
A permission request notifying step of notifying the permission request for the predetermined file operation to the user corresponding to the identification information of the derivation source of the file specified by the derivation source specifying step;
A file operation control step of controlling to permit file operation of the corresponding file when the permission of the predetermined file operation is received from a user terminal used by a user corresponding to the identification information of the file derivation source; A file management method characterized by including:   A file management program for causing a computer to function as the file management apparatus according to claim 1.

Images