JP4574287B2 - File management device - Google Patents

Description

  The present invention relates to a file management apparatus connected to a network.

  A so-called file sharing server apparatus that can access a shared file via a conventional network performs access management to the file by user authentication. For example, such a file sharing server device receives user authentication information such as a user name (for example, “user1”) and a password (for example, “abcd1234”) from a client terminal via a network, and performs its own user authentication function or user A user authentication function provided by the authentication server authenticates the user, and determines whether or not connection is possible and the access right of the file or folder.

  However, since user authentication via the network requires a response to user authentication information, the existence of the file sharing server is exposed to the network, and there is a drawback that it is susceptible to attacks from malicious users.

To deal with this problem, the disk device disclosed in Patent Document 1 registers the location information on the network of a computer permitted to issue a processing request, and processes only the processing request from the registered computer. I'm trying to configure and fix the problem.
JP 2000-347808 A

  However, with the configuration as described in Patent Document 1, it is difficult to cope with the current network environment in which position information changes dynamically. Also, in a distributed environment where a large number of server devices and client terminals are arranged on a network, there are many setting items, which increases management costs. Furthermore, since the IP address and port number used as the position information can be set by the user at the client terminal, there is a drawback that “spoofing” is possible.

  Accordingly, an object of the present invention is to provide a file management device that is not easily attacked by a malicious user, can handle a dynamic network configuration, is easy to set, and is difficult to “spoof”. .

  In order to achieve the above object, a file management apparatus according to the present invention is a network that transfers packets between apparatuses based on path information included in packet header information, and includes group identification information included in packet header information. Connected to a network that distributes at least the path information corresponding to the virtual network to a device that is permitted to connect to the virtual network. A first packet processing means for receiving a packet transferred from the network based on the path information and processing first header information used for communication control in the network; Based on the group identification information, the first packet processing means Second packet processing means for processing second header information used for communication control in the virtual network, and association information between the file and / or folder and the group identification information. Files and folders received by the file management means to be managed and data determined to be a file operation request by the second packet processing means, and associated with the group identification information by the association information according to the file operation request File operation processing means for performing the file operation, and drive means for driving the second packet processing means corresponding to each of the group identification information associated with the file and / or folder by the association information by the file management means It is characterized by having.

  As described above, according to the present invention, it is possible to provide a file management device that is difficult to be attacked by a malicious user, can handle a dynamic network configuration, is easy to set, and is difficult to “spoof”. .

  An embodiment of the present invention will be described in detail with reference to FIGS.

<Configuration example of file management system of this embodiment>
FIG. 1 is a diagram illustrating a configuration example of a system including a file sharing server apparatus according to the present embodiment.

  In FIG. 1, 110 is a file sharing server device that provides a file sharing server function, 120 is a network such as a LAN or the Internet, 130-1 to 6 are client terminals such as a personal computer (PC) and a personal digital assistant (PDA), A network management apparatus 140 manages connections from the client terminals 130-1 to 6 and the file sharing server apparatus 110 to the virtual networks 121-1 to 4 that are virtually constructed on the network 120. The network management device 140 determines whether to connect to the virtual networks 121-1 to 4 in accordance with requests from the client terminals 130-1 to 130-6 and the file sharing server device 110, and if connection is possible, the respective virtual networks 121- 1 to 4 distributes route information for communication.

  The file sharing server apparatus 110 includes a network processing unit 111 that performs communication via the network 120, virtual network processing units 112-1 to 112-4 that perform communication via the virtual networks 121-1 to 12, and storage and deletion of files. A file management unit 113 that performs management functions such as migration, copying, a database 115 having file management information, and a service configuration unit 114 that activates the virtual network processing units 112-1 to 112-4 and the file management unit 113. Composed.

  In this embodiment, an example in which four virtual networks are configured is shown, but the number of virtual networks is not limited to four.

<Configuration Example of File Sharing Server Device of the Present Embodiment>
(Hardware configuration example)
FIG. 2 is a diagram illustrating a hardware configuration example of the file sharing server apparatus according to the present embodiment.

  In FIG. 2, a file sharing server device 110 includes a central processing unit (CPU) 110, a memory 212 such as a ROM or a RAM, a hard disk drive (HDD) 213 that is a large-capacity storage device, and a network interface card (NIC). The program stored in the hard disk drive 213 is loaded into the memory 212 and executed by the CPU 211. The program also controls the NIC 214 and communication via the network 120 is realized. Needless to say, the file sharing server apparatus of the present embodiment can be applied to any configuration as long as it is hardware capable of operating a program and communicating with a network.

(Software and data configuration example)
FIG. 3 is a diagram showing a configuration example of software and data in the file sharing server apparatus of the present embodiment.

  In FIG. 3, reference numeral 311 denotes an operating system that is a basic program of the system, 312 denotes a network protocol driver that controls the NIC 214 and processes a protocol necessary for communication via the network 120, and 313 denotes a virtual network 121. -Virtual network protocol driver which is a program for processing a protocol necessary for communication via 1-4, 314 is a database repository which is data managed in a database such as a file, 315 is a database record which is database management data, Reference numeral 316 denotes a database management system which is a program for adding, deleting, changing, and searching records in the database record 315, and 317 is a program for providing a file sharing server function. A file sharing server services, 318 is a file sharing server configuration service is a program used to start such startup and file sharing server service virtual network protocol driver program.

  The virtual network protocol driver has a plurality of drivers according to the type of virtual network. These programs and data are stored in the HDD 213, and each program is loaded into the memory 212 and executed by the CPU 211.

(Database configuration example)
FIG. 4A is a diagram showing an example of a database record (folder record) in the file sharing server device of the present embodiment.

  4A, reference numeral 315-1 denotes a part of the database record 315, and is an example of a folder record that is a record for managing folders. The folder record 315-1 includes fields of a folder ID 411, a folder name 412, a network ID 413 indicating an accessible virtual network, a parent folder ID 414, and a property 415.

  In the folder record 315-1, a record with a folder ID “3” has a folder name “root”, accessible network IDs 3 and 4, a parent folder ID 0, and a property “<dp3> dpv3 </ dpv3”. > ... ".

  Here, the parent folder ID of 0 represents the root folder, “dp3” in the property represents the attribute name, and “dpv3” represents the attribute value.

  FIG. 4B is a diagram showing an example of a database record (file record) in the file sharing server device of the present embodiment.

  In FIG. 4B, reference numeral 315-2 denotes a part of the database record 315, which is an example of a file record that is a record for managing a file. The file record 315-2 includes fields of a file ID 421, a file name 422, a network ID 423 indicating an accessible virtual network, a parent folder ID 424, a property 425, and a repository location 426.

  In the file record 315-2, the file with the file ID "6" has the file name "img123.jpg", the accessible network ID 3 and the parent folder ID 6 (folder name "image"), and the property is “<Fp6> fpv6 </ fp6>...” And the repository location is “repository1 / img123.jpg”.

  Here, the repository location is an actual data storage destination and is represented by a path name in the database repository 314.

  FIG. 4C is a diagram illustrating an example of a hierarchical structure of folders and files according to the present embodiment.

  In FIG. 4C, reference numerals 430-1 to 430-4 are examples in which folder records 315-1 and file records 315-2 are displayed hierarchically for each virtual network. Here, for example, “document / audi222.mp3” is displayed in both the hierarchical structure 430-3 of the virtual network-3 and the hierarchical structure 430-4 of the virtual network-4, and is shared by both virtual networks. ing.

(Data and command format example)
FIG. 5A is a diagram illustrating a configuration example of a packet transmitted and received by the file sharing server apparatus according to the present embodiment.

  In FIG. 5A, reference numeral 510 denotes a PAN packet that is transferred through the network 120 and forms the virtual networks 121-1 to 121-4. The destination PAN member ID 511, the source PAN member ID 512, the type PAN 513 indicating that the packet is a PAN packet, and the network All-route designation label 514 that is route information used for switching in the network, terminal device header 515 including information as to whether or not the file operation request is used for communication control on virtual network 121, on virtual network 121 Type 516 indicating the type of packet used for the communication of, and data 517 which is data to be transferred.

  The destination PAN member ID 511 includes PAN_ID 531 that is group identification information for identifying a virtual network and a PAN device ID 532 that indicates a device type.

  In the present embodiment, the configuration of the PAN packet 510 has been described. However, in the present embodiment, the virtual networks 121-1 to 121-1 are based on path information and group identification information distributed from the network 120, such as a VPN (Virtual Private Network). Various other packet configurations that can configure 4 can be similarly applied, and these are also included in the present invention.

  FIG. 5B is a diagram showing a configuration example of a file operation request in the file sharing server device of the present embodiment. FIG. 5B is an example, and other file operations may be added, or a plurality of file operations may be combined.

  In FIG. 5B, the property acquisition request 610 includes a request name “PROPFIND” 611 and a property acquisition target location 612. Similarly, the folder creation request 620 includes the request name “MKCOL” 621 and the creation location 622, the file storage request 630 includes the request name “PUT” 631, the storage location 632, the storage data 633, and the file read request 640 includes the request name ”. GET "641 and read target file location 642, delete request 650 is request name" DELETE "651 and delete target location 652, file copy request 660 is request name" COPY "661, copy source location 662, and copy destination location 663. The file move request 670 includes a request name “MOVE” 671, a move source location 672, a move destination location 673, and a share setting request 680 includes a request name “PROPPATCH” 681 and a setting target location 682 for changing attribute settings. As ne Composed from the value 684 Metropolitan network ID set to be shared with "Network_ID" 683 for specifying the network ID.

  Here, in addition to the field values of the properties 415 and 425, the property includes a list of folders and files located in the immediately lower hierarchy in the case of a folder. The location is a path name in the hierarchical structure, for example, “audio / audio223.mp3” in 430-2.

<Operation example of the file sharing server apparatus of this embodiment>
(Overall flow)
FIG. 6 is a flowchart showing an outline of the overall operation of the file sharing server apparatus of this embodiment. Details of each process are shown in the flowcharts of FIGS.

  First, step S700 is the processing of the file sharing server configuration service 318 in FIG. 3, and the database 115 on the disk 213 is initialized using the database management system 316 (see FIG. 7). Next, in step S800 as well, the file sharing server is activated (for example, the virtual network protocol driver 313 and the file sharing server service 317 are activated) by the processing of the file sharing server configuration service 318 in FIG. 3 (see FIG. 8).

  Waiting for packet reception in step S100, and if there is another processing request, the process proceeds from step S200 to S300 to perform other processing. If there is packet reception, the process proceeds to step S900, and corresponding processing is performed from the header of the received packet (see FIGS. 9 to 19).

  When the packet processing or other processing ends, it is determined in step S400 that the service of the file sharing server has been stopped. If not stopped, the processing returns to step S100 to perform the next processing.

(Disk initialization process: S700)
FIG. 7 is a flowchart of disk initialization processing in the file sharing server device of this embodiment. The disk initialization process (S700) is executed by the file sharing server configuration service 318 when the apparatus is initialized.

  In the disk initialization process (S700), a list of network IDs that are first allowed to be accessed is received by a keyboard or the like (not shown) (S701), and the database record 315 and the database repository 314 are initialized (S702). Next, the received network ID is read (S703). When the network ID is read (No in S704), a record of the root folder corresponding to the read network ID is created (S705). ), The next network ID is read (S703), and the same processing is repeated. Here, when the network ID is finished (Yes in S704), the process is finished (S710).

  Note that processing for the database record 315 is executed via the database management system 316 unless otherwise specified. The network ID indicates PAN_ID 531.

(File sharing server activation process: S800)
FIG. 8 is a flowchart of the file sharing server activation process in the file sharing server apparatus of this embodiment. The file sharing server activation process (S800) is executed by the file sharing server configuration service 318 when the apparatus after initialization is activated.

  In the file sharing server activation process (S800), all network IDs associated with files and folders are searched from the database record (S801). Next, the network ID is read from the search result (S802). When the network ID is read (No in S803), the virtual network protocol driver 313 corresponding to the network ID is activated (S804), and the virtual network is sequentially set. And repeat from S802. Here, if the network ID is completed (Yes in S803), the file sharing server service 317 for all the activated virtual network protocol drivers 313 is activated (S810), and the process is terminated (S811).

  Note that the effect of the present invention is the same regardless of whether the file sharing server service 317 is activated for all the virtual network protocol drivers 313 or one for each virtual network protocol driver 313, and the present invention is not limited to any one.

(Packet reception processing: S900)
FIG. 9 is a flowchart of packet reception processing in the file sharing server apparatus of this embodiment. The packet reception process (S900) is executed when a packet is received by the network protocol driver 312 via the NIC 214.

  In the packet reception process (S900), the network ID is read from the header information of the received packet (PAN_ID 531 in the example of FIG. 5A) (S901), and the corresponding virtual network protocol driver is activated (Yes in S902), The process proceeds to the virtual network packet reception process (S1000).

  If the corresponding virtual network protocol driver is not activated (No in S902), the packet is discarded (S903), and the process is terminated (S904).

  In this embodiment, an example of discarding packets other than the packet for the virtual network is shown, but it may be used for other services, and is not described in this example in order to avoid complexity.

(Virtual network packet reception processing: S1000)
FIG. 10 is a flowchart of virtual network packet reception processing in the file sharing server device of this embodiment. The virtual network packet reception process (S1000) is executed by the virtual network protocol driver 313.

  In the virtual network packet processing (S1000), it is determined whether or not the received packet is a file operation request based on header information in the virtual network (terminal device header 515 in the PAN packet 510) (S1001). If it is determined (Yes in S1001) and the corresponding file sharing service 317 is activated (Yes in S1010), the process proceeds to the file operation request process (S1100).

  If it is determined that the received packet is not a file operation request (No in S1001), or if the corresponding file sharing service 317 is not activated (No in S1010), the packet is discarded (S1002), and the process ends. (S1003).

  In this embodiment, an example of discarding packets other than those for the file sharing server service is shown. However, it may be used in other services, and is not described in this example in order to avoid complexity.

(File operation request processing: S1100)
FIG. 11 is a flowchart of file operation request processing in the file sharing server apparatus of this embodiment. The file operation request process (S1100) is executed by the file sharing server service 317.

  In the file operation request process (S1100), the contents of the file operation request are determined. If it is determined that the request is the property acquisition request 610 (Yes in S1101), the process proceeds to the property acquisition process (S1200) and is not the property acquisition request 610. (No in S1101), and if it is determined that the request is a folder creation request 620 (Yes in S1102), the process proceeds to the folder creation process (S1300).

  Similarly, when it is determined that the request is not the folder creation request 620 (No in S1102) and is determined to be the file save request 630 (Yes in S1103), the process proceeds to the file save process (S1400) and is not the file save request 630. Is determined (No in S1103), and if it is determined that the request is a file read request 640 (Yes in S1104), the process proceeds to a file read process (S1500), and is determined not to be a file read request 640 (No in S1104). If it is determined that the request is a delete request 650 (Yes in S1105), the process proceeds to the delete process (S1600), and is determined not to be a delete request 650 (No in S1105), and is determined to be a file copy request 660. In the case (Yes in S1106), go to the file copy process (S1700). If it is determined that the request is not the file copy request 660 (No in S1106) and is determined to be the file move request 670 (Yes in S1107), the process moves to the file move process (S1800) and is not the file move request 670. Is determined (No in S1107) and if it is determined that the request is a sharing setting request 680 (Yes in S1108), the process proceeds to the sharing setting process (S1900), and is determined not to be a sharing setting request 680 (S1108). No) returns a file operation request error response (S1109), and ends the processing (S1110).

  The determination of the file operation request is not limited to the order shown in FIG.

<Example of processing procedure for each file operation>
(Property acquisition processing: S1200)
FIG. 12 is a flowchart of property acquisition processing in the file sharing server device of this embodiment. The property acquisition process (S1200) is executed by the file sharing server service 317.

  In the property acquisition process (S1200), the target network ID is read (S1201), the target location 612 is read (S1202), and the ID and property of the file and folder corresponding to the target location and the target network ID are searched in the database record 315 ( S1203). If neither file ID nor folder ID is found (Yes in S1204), there is no corresponding file or folder, so a property acquisition error response is returned (S1205), and the process ends (S1206).

  If either file ID or folder ID is found (No in S1204) and it is not a folder ID (file ID) (No in S1207), response data is constructed based on the target property found in the search (S1220). If it is a folder ID (Yes in S1207), a folder ID and file ID having the target folder ID as the parent folder ID and the target network ID are searched (S1208). Based on the target property and the folder ID and file ID searched in S1208, the file name and the like are appropriately searched to construct response data (S1209). These response data are returned as a property acquisition response (S1210), and the process ends (S1211).

  Here, the target network ID may be notified from the virtual network protocol driver 313 executed in FIG. 10 to the file sharing server service 317 or may be acquired from the virtual network protocol driver 313. .

(Folder creation process: S1300)
FIG. 13 is a flowchart of the folder creation process in the file sharing server device of this embodiment. The folder creation process (S1300) is executed by the file sharing server service 317.

  In the folder creation process (S1300), the target network ID is read (S1301), the target location 622 is read (S1302), and the folder ID corresponding to the target location and the target network ID is searched in the database record 315 (S1303). If the folder ID is found (Yes in S1304), since the same folder already exists, a folder creation error response is returned (S1320), and the process ends (S1321).

  If the folder ID is not found (No in S1304), the new folder name and parent folder location are extracted from the target location 622 (S1305), and the folder ID corresponding to the parent folder location and the target network ID is searched (S1306). . If the parent folder ID is found (Yes in S1307), a new folder record is added with the new folder name, parent folder ID, and target network ID (S1308), a folder creation completion response is returned (S1309), and the process is terminated. (S1310). If the parent folder ID is not found (No in S1307), the target network ID or the target location 622 is incorrect, so a folder creation error is returned (S1330), and the process ends (S1331).

(File saving process: S1400)
FIG. 14 is a flowchart of file storage processing in the file sharing server device of this embodiment. The file saving process (S1400) is executed by the file sharing server service 317.

  In the file storage process (S1400), the target network ID is read (S1401), the target location 632 is read (S1402), the target data 633 is read (S1403), and the file ID corresponding to the target location and the target network ID is stored in the database record 315. (S1404).

  If the file ID is found (Yes in S1405), the repository location is searched from the file ID (S1420), the target data 633 is overwritten in the repository location (S1421), a file save completion response is returned (S1422), and the process is performed. The process ends (S1423).

  If the file ID is not found (No in S1405), the file name and parent folder location are extracted from the target location (S1406), and the folder ID corresponding to the parent folder location and the target network ID is searched (S1407). If the parent folder ID is not found (No in S1408), a file storage error response is returned (S1430) because the target network ID or the target location 632 is incorrect, and the process ends (S1431). If the parent folder ID is found (Yes in S1408), a repository location is generated and the target data is stored (S1409), and a file record is created and added with the file name, parent folder ID, target network ID, and repository location ( S1410), a file storage completion response is returned (S1411), and the process is terminated (S1412).

(File read processing: S1500)
FIG. 15 is a flowchart of file read processing in the file sharing server apparatus of this embodiment. The file reading process (S1500) is executed by the file sharing server service 317.

  In the file reading process (S1500), the target network ID is read (S1501), the target location 642 is read (S1502), and the file ID corresponding to the target location and the target network ID is searched in the database record 315 (S1503).

  If the file ID is not found (No in S1504), a file read error response is returned (S1520) because there is an error in the target network ID or the target location 642, and the process ends (S1521).

  If the file ID is found (Yes in S1504), the repository location is searched from the file ID (S1505), data is read from the repository location (S1506), and a folder read completion response including response data in the read data is returned (S1507). ), The process is terminated (S1508).

(Delete processing: S1600)
FIG. 16 is a flowchart of the deletion process in the file sharing server device of this embodiment. The deletion process (S1600) is executed by the file sharing server service 317.

  In the deletion process (S1600), the target network ID is read (S1601), the target location 652 is read (S1602), and the ID and property of the file and folder corresponding to the target location and the target network ID are searched in the database record 315 (S1603). ).

  If the target file ID is found (Yes in S1604), the repository location corresponding to the file ID is searched (S1620), the file record corresponding to the file ID is deleted (S1621), and the repository location data is deleted ( S1622), a deletion process completion response is returned (S1623), and the process is terminated (S1624).

  If the target file ID does not exist (No in S1604) and the target folder ID exists (Yes in S1605), a child file ID and a child folder ID having the target folder ID as the parent folder ID are searched (S1606). If neither the child file ID nor the child folder ID exists (No in S1607), the folder record corresponding to the folder ID is deleted (S1608), a deletion completion response is returned (S1609), and the process ends (S1610).

  If the target folder ID does not exist (No in S1605), there is an error in the target network ID or the target location 652, or the target folder ID exists (Yes in S1605) and the child file ID or child folder ID exists. If yes (Yes in S1607), in order to prevent unintended deletion of the child file or child folder, a deletion process error response is returned (S1630), and the process ends (S1631).

(File copy processing: S1700)
FIG. 17 is a flowchart of file copy processing in the file sharing server device of this embodiment. The file copy process (S1700) is executed by the file sharing server service 317.

  In the file copy process (S1700), the target network ID is read (S1701), the target location 662 is read (S1702), the copy destination location 663 is read (S1703), and the file ID corresponding to the target location and the target network ID is a database record. A search is made at 315 (S1704).

  If the file ID is found (Yes in S1705), the database record 315 is searched for the file ID corresponding to the copy destination location and the target network ID (S1706). If the copy destination file ID is not found (No in S1707), the parent folder location and the copy destination file name of the copy destination location are extracted (S1708), and the folder ID corresponding to the parent folder location and the target network ID is stored in the database record. A search is made at 315 (S1709). If the parent folder ID of the copy destination is found (Yes in S1710), the copy source repository location for the target file ID is searched (S1711), the copy destination repository location is generated (S1712), and the data of the copy source repository location is obtained. Copy to the copy destination repository location (S1713), create a file record corresponding to the copy destination file name, parent folder ID, target network ID, and copy destination repository location (S1715), and return a file copy completion response (S1715). The process ends (S1716).

  If the target file ID is not found (No in S1705), there is an error in the target network ID or the target location 662, or if the file ID is found (Yes in S1705) and the copy destination file ID is found (Yes in S1707). ) Already exists, or the file ID is found (Yes in S1705), the copy destination file ID is not found (No in S1707), and the copy destination parent folder ID is not found (No in S1710). Since there is an error in the target network ID or the copy destination location 663, a file copy error response is returned (S1720), and the process ends (S1721).

(File move processing: S1800)
FIG. 18 is a flowchart of file movement processing in the file sharing server apparatus of this embodiment. The file movement process (S1800) is executed by the file sharing server service 317.

  In the file migration process (S1800), the target network ID is read (S1801), the target location 672 is read (S1802), the destination location 673 is read (S1803), and the file ID corresponding to the target location and the target network ID is a database record. A search is made at 315 (S1804).

  When the file ID is found (Yes in S1805), the database record 315 is searched for the file ID corresponding to the destination location and the target network ID (S1806). If the destination file ID is not found (No in S1807), the parent folder location and destination file name of the destination location are extracted (S1808), and the folder ID corresponding to the parent folder location and the target network ID is stored in the database record. A search is made at 315 (S1809). If the destination parent folder ID is found (Yes in S1810), the file record for the target file ID is changed to the destination file name and destination parent folder ID (S1811), and the process ends (S1813).

  If the target file ID is not found (No in S1805), there is an error in the target network ID or the target location 672, or if the file ID is found (Yes in S1805) and the destination file ID is found (Yes in S1807). ) Already exists, or the file ID is found (Yes in S1805), the destination file ID is not found (No in S1807), and the destination parent folder ID is not found (No in S1810). Since there is an error in the target network ID and the migration destination location 673, a file migration error response is returned (S1820), and the process is terminated (S1821).

(Share setting process: S1900)
FIG. 19 is a flowchart of the sharing setting process in the file sharing server apparatus of this embodiment. The sharing setting process (S1900) is executed by the file sharing server service 317.

  In the sharing setting process (S1900), the target network ID is read (S1901), the target location 682 is read (S1902), the set network ID 684 is read (S1903), and the folder ID and file ID corresponding to the target location and the target network ID are obtained. The database record 315 is searched (S1904).

  If the file ID is not found (No in S1905), and if the folder ID is not found (No in S1906), a share setting error response is returned (S1907) because there is an error in the target network ID or the target location 682. Is finished (S1908).

  If the file ID is found (Yes in S1905), the target network ID and the setting network ID are set in the file record for the file ID (S1920), a sharing setting completion response is returned (S1921), and the process ends (S1922). . On the other hand, if the folder ID is found (Yes in S1906), the target network ID and the set network ID are set in the folder record for the folder ID (S1930), a sharing setting completion response is returned (S1931), and the process is terminated ( S1932).

  In the present embodiment, the network management apparatus 140 in FIG. 1 assigns a virtual network to the client terminal 130. However, the attribute of information for communicating the virtual network not in units of the client terminal 130, for example, image, document , audio, etc., can be implemented even if the virtual network is assigned to each communication unit more dynamically, and the network ID is returned to the client terminal in response to completion of each file operation. . As described above, the present invention can be applied to any network as long as the virtual network does not change without being notified when accessing the same folder or the same file. It is included in the present invention. Furthermore, in the present embodiment, the network has a virtual network function, and an example in which the function is used has been described. However, the present invention is not limited to the virtual network function, and the network provides without authentication by user authentication information. It can also be realized by managing communication information such as communication path information associated with a folder or file.

  As described above, in this embodiment, only the setting of the identification information of the virtual network to the file or folder is performed, and only the terminal permitted to connect to the virtual network is flexibly adapted to each virtual network. Operates to provide file sharing services.

  Further, as described above, in the present embodiment, the network transfers packets between devices based on the path information included in the packet header information, and is based on the group identification information included in the packet header information. Identifying virtual networks to files and folders in a network that constitutes a virtual network separated into two, and that distributes at least route information corresponding to the virtual network to devices that are permitted to connect to the virtual network Operates to provide a flexible file sharing service according to each virtual network only for terminals that are allowed to connect to the virtual network only by setting information, and opens the file sharing server function on the network. Not from malicious users Because it uses a virtual network function of the network, it can handle dynamic network configurations and can be managed with group identification information, so it is easy to set up and is not restricted by user-configurable information. A file sharing service that is difficult to impersonate becomes possible.

It is a figure which shows the structural example of the system which has the file sharing server apparatus of this embodiment. It is a figure which shows the hardware structural example in the file sharing server apparatus of this embodiment. It is a figure which shows the structural example of the software and data in the file sharing server apparatus of this embodiment. It is a figure which shows an example of the database record (folder record) in the file sharing server apparatus of this embodiment. It is a figure which shows an example of the database record (file record) in the file sharing server apparatus of this embodiment. It is a figure which shows an example of the hierarchical structure of the folder and file of this embodiment. It is a figure which shows the structural example of the packet which the file sharing server apparatus of this embodiment transmits / receives. It is a figure which shows the structural example of the file operation request which the file sharing server apparatus of this embodiment receives. It is a flowchart which shows the whole process outline in the file sharing server apparatus of this embodiment. It is a flowchart of the disk initialization process in the file sharing server apparatus of this embodiment. It is a flowchart of the file sharing server starting process in the file sharing server apparatus of this embodiment. It is a flowchart of the packet reception process in the file sharing server apparatus of this embodiment. It is a flowchart of the virtual network packet reception process in the file sharing server device of the present embodiment. It is a flowchart of the file operation request process in the file sharing server device of the present embodiment. It is a flowchart of the property acquisition process in the file sharing server apparatus of this embodiment. It is a flowchart of the folder creation process in the file sharing server apparatus of this embodiment. It is a flowchart of the file preservation | save process in the file sharing server apparatus of this embodiment. It is a flowchart of the file read-out process in the file sharing server apparatus of this embodiment. It is a flowchart of the deletion process in the file sharing server apparatus of this embodiment. It is a flowchart of the file copy process in the file sharing server apparatus of this embodiment. It is a flowchart of the file movement process in the file sharing server apparatus of this embodiment. It is a flowchart of the share setting process in the file sharing server apparatus of this embodiment.

Claims (7)

It is a network that transfers packets between devices based on path information included in packet header information, and is a network that constitutes a virtual network that is virtually separated based on group identification information included in packet header information, A file management device connected to a network that distributes at least the path information corresponding to the virtual network to a device that is permitted to connect to the virtual network;
First packet processing means for receiving a packet transferred from the network based on the path information and processing first header information used for communication control in the network;
A second packet processing means for receiving a packet processed by the first packet processing means based on the group identification information and processing second header information used for communication control in the virtual network;
File management means for managing association information between files and / or folders and the group identification information;
A file operation that receives data determined to be a file operation request by the second packet processing means, and performs file operations on files and folders associated with the group identification information by the association information in accordance with the file operation request Processing means;
And a drive unit that drives the second packet processing unit corresponding to each of the group identification information associated with the file and / or folder by the file management unit by the association information. . 2. The file management according to claim 1, wherein the second packet processing unit holds the group identification information, and the file operation processing unit acquires the group identification information from the second packet processing unit. apparatus. 2. The file according to claim 1, wherein the second packet processing unit holds the group identification information, and the second packet processing unit notifies the file operation request processing unit of the group identification information. Management device. Said group identification information, in claim 3, wherein the first packet processing unit notifies the second packet processing unit, the second packet processing means and notifying the file management processor means The file management device described. Said file management means includes a database with records that correspond to files and folders, the record is any one of claims 1 to 4, characterized in that with fields corresponding to at least one of the group identification information The file management device according to item. The file operations, reading of the file or the folder, creating, saving, deleting, changing the hierarchical structure, reading attributes to any one of claims 1 to 5, characterized in that either changes The file management device described. A program for causing a computer to realize the function of the file management apparatus according to any one of claims 1 to 6 .

Images