File management using a virtual registry

Abstract

This file management device has one or more processors. The one or more processors execute processing including: managing management information for associating a plurality of nodes belonging to a communication network with a file held in each of the plurality of nodes; receiving a file request; specifying nodes holding a file corresponding to the file request by referring to the management information; and instructing at least one of the specified nodes to transmit the file corresponding to the file request to a designated destination.

Description

Technical Field

[0001] The present disclosure relates to file management using a virtual registry.

Background Art

[0002] In recent years, in wireless communication systems such as 5G, for example, network functions may be virtualized, and virtualized network functions are also referred to as VNFs (Virtual Network Functions). VNFs can be deployed at various locations in the network, enabling flexible network configurations. For example, when it is desired to reduce the latency of a network service, instead of deploying the VNF that provides the service to the end user in a large-scale facility such as a CDC (Central Data Center) built in the center of the network, it is being deployed in medium-scale or small-scale facilities such as RDCs (Regional Data Centers) or GCs (Group Centers) that are closer to the end user.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0004] Incidentally, medium-sized or small facilities, especially GCs, often cannot install large-scale storage capable of storing large amounts of data. Therefore, when VNFs are deployed to medium-sized or small facilities such as RDCs and GCs, the files necessary for deployment are sent from large facilities such as CDCs to the medium-sized or small facilities. In other words, CDCs have large-capacity registries, and files stored in the registry are sent to RDCs and GCs as needed.

[0005] However, when files for VNF deployment are sent from a large facility to a medium or small facility, there is a problem of increased network load. Specifically, for example, when many files are sent simultaneously from a CDC to a GC, the concentration of communication increases the traffic volume, especially on network lines close to the CDC, which can cause a decrease in communication speed at other facilities using that network line.

[0006] This disclosure is made in view of the above and aims to provide file management using a virtual registry that can distribute communications and reduce the load on the network. [Means for solving the problem]

[0007] According to one aspect of the present disclosure, a file management device has one or more processors, and the one or more processors perform processing including managing management information that associates a plurality of nodes belonging to a communication network with files held in each of the plurality of nodes; receiving file requests; referring to the management information to identify a node that holds a file corresponding to the file request; and instructing at least one of the identified nodes to send the file corresponding to the file request to a specified destination.

[0008] Furthermore, according to another aspect of the present disclosure, a file retrieval method includes managing management information that associates a plurality of nodes belonging to a communication network with files held in each of the plurality of nodes; receiving a file request; identifying a node that holds a file corresponding to the file request by referring to the management information; and retrieving a file corresponding to the file request from at least one of the identified nodes. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 shows an example of a communication system according to Embodiment 1. [Figure 2] Figure 2 is a block diagram showing the configuration of the file management system according to Embodiment 1. [Figure 3] Figure 3 shows an example of file information. [Figure 4] Figure 4 shows an example of virtual registry information. [Figure 5] Figure 5 is a sequence diagram showing the file acquisition method according to Embodiment 1. [Figure 6] Figure 6 is a block diagram showing the configuration of the file management system according to Embodiment 2. [Figure 7] Figure 7 shows an example of layer information. [Figure 8] Figure 8 is a sequence diagram showing the file acquisition method according to Embodiment 2. [Figure 9] Figure 9 is a block diagram showing an example hardware configuration for a CDC node. [Figure 10] Figure 10 is a block diagram showing an example of a node's hardware configuration. [Modes for carrying out the invention]

[0010] The embodiments of this disclosure will be described below with reference to the attached drawings. The embodiments described below are illustrative and should not be interpreted as limiting.

[0011] (Embodiment 1) Figure 1 shows an example of a communication system according to Embodiment 1. The communication system shown in Figure 1 includes a CDC node 100 housed in a large-scale facility called a CDC, a node 200 housed in a medium- or small-scale facility called an RDC or GC, and a base station 300 connected to the node 200.

[0012] The CDC node 100 is located in the CDC, which is situated in the center of the network constituting the communication system, and stores files for deploying VNFs to the RDC or GC nodes 200. The CDC node 100 then sends files to the RDC or GC nodes 200 as needed. The CDC node 100 also stores information about the files held by each node 200.

[0013] Furthermore, the CDC node 100 manages the topology that shows the connectivity relationships of all nodes 200 in the network. That is, the CDC node 100 stores the connectivity relationships of each node 200 and the distances between nodes 200.

[0014] Multiple nodes 200 are connected in a ring-like manner, forming a hierarchically connected L-ring 10, M-ring 20, and GC-ring 30. Specifically, the L-ring 10 is a higher-level ring formed by nodes 200 close to the CDC node 100, and aggregates the M-ring 20 on an area basis, for example. The nodes 200 forming the L-ring 10 are located, for example, in the RDC. The M-ring 20 is a middle-level ring formed by nodes 200 somewhat farther from the CDC node 100, and aggregates the GC-ring 30 on a prefecture basis, for example. The nodes 200 forming the M-ring 20 are located, for example, in the RDC or GC. The GC-ring 30 is a lower-level ring formed by nodes 200 directly connected to the base station 300. The nodes 200 forming the GC-ring 30 are located, for example, in the GC.

[0015] In the present embodiment, it is assumed that the communication system is a ring network. However, the technology according to the present disclosure can be applied not only to a ring network but also to networks of various topologies.

[0016] When newly deploying a VNF, the node 200 acquires necessary files from a virtualized registry (hereinafter referred to as "virtual registry"). That is, the node 200 constructs a virtual registry including other nodes 200 and the CDC node 100 other than its own node 200, and acquires necessary files from the virtual registry. The virtual registry may include not only the ring to which the node 200 belongs but also other nodes 200 of the upper ring of the ring and adjacent rings connected via the upper ring. The node 200 acquires topology information from the CDC node 100 and constructs a virtual registry based on the topology information.

[0017] The base station 300 is connected to the node 200 belonging to the GC ring 30 and performs wireless communication with a terminal device (not shown). That is, the base station 300 wirelessly transmits the data received from the node 200 to the terminal device or transfers the data wirelessly received from the terminal device to the node 200.

[0018] FIG. 2 is a block diagram showing the configuration of a file management system according to Embodiment 1. This file management system includes a CDC node 100 and a node 200 connected to the CDC node 100 via one or more rings.

[0019] The CDC node 100 includes a topology management unit 110, a file storage unit 120, and a communication interface unit (hereinafter abbreviated as "communication I / F unit") 130.

[0020] The topology management unit 110 manages the topology of the entire network. Specifically, the topology management unit 110 stores the connection relationships of the nodes 200 that form the L-ring 10, M-ring 20, and GC-ring 30, respectively. The topology management unit 110 also stores an index value related to file transmission between each node 200. This index value is calculated using a predetermined formula based on predetermined elements of the network. These predetermined elements may be determined as appropriate, and specific examples of elements include distance, throughput, or traffic volume in the communication path between nodes 200.

[0021] The index value should be such that, for example, when sending a file from one node 200 to another node 200, a smaller value is calculated as the network load decreases. In this case, it is preferable that file transmissions occur between nodes 200 with smaller index values. Furthermore, the index value may be calculated considering not only the network but also the load on each node 200 or the priority assigned to each node 200 in advance. That is, the load on each node 200 or the priority assigned to each node 200 in advance may be included as elements in the calculation formula for the index value.

[0022] Furthermore, the topology management unit 110 stores information about the files held by each node 200. That is, the topology management unit 110 stores information that identifies the files held by each node 200, for example, as shown in Figure 3. In the example shown in Figure 3, it is shown that each node 200 holds the files marked with a circle. For example, it is shown that "Node #1" holds "File #2" and "Node #2" holds both "File #1" and "File #2".

[0023] The topology management unit 110 provides topology information, including information on index values ​​in the communication path from node 200 to other nodes 200, and information on files held by each of the other nodes 200, in accordance with a request from node 200.

[0024] The file storage unit 120 stores the files used to deploy the VNF to node 200. When requested by node 200, the file storage unit 120 distributes the files to the requesting node 200.

[0025] The communication interface unit 130 sends and receives various data with node 200. The communication interface unit 130 receives requests for topology information or files from node 200 and sends topology information or files to node 200 in response to requests.

[0026] Node 200 includes a communication interface unit 210, a topology information acquisition unit 220, a virtual registry management unit 230, a file request unit 240, and a file acquisition unit 250.

[0027] The communication interface unit 210 sends and receives various data between the CDC node 100 and other nodes 200. The communication interface unit 210 sends requests for topology information or files to the CDC node 100 or node 200, and receives topology information or files in response to the requests from the CDC node 100 or node 200.

[0028] The topology information acquisition unit 220 requests from the CDC node 100 information about the index values ​​in the communication path to the other nodes 200 that constitute the virtual registry, and information about the files held by each of the other nodes 200, in order to build a virtual registry for its own node 200. The topology information acquisition unit 220 then acquires topology information from the CDC node 100 that includes the index value information in the communication path to the other nodes 200 and information about the files held by each of the other nodes 200.

[0029] The virtual registry management unit 230 constructs and manages the virtual registry of its own node 200 and controls the retrieval of files from the virtual registry. Specifically, the virtual registry management unit 230 uses topology information to create information that associates files with the nodes 200 that hold those files. Hereafter, this information will also be referred to as virtual registry information or management information. As shown in Figure 4, for example, the virtual registry management unit 230 creates virtual registry information that indicates which other nodes 200 hold each file, the index value in the communication path to those other nodes 200, and whether each file is held by the optimal other node 200.

[0030] In the virtual registry information shown in Figure 4, distance is used as the indicator value for the communication path. For example, "File #1" is held at "Node #2", which is "5" away from the local node 200 on the network, indicating that "Node #2" is not the optimal other node 200. On the other hand, "File #2" is held at "Node #1", which is "1" away from the local node 200 on the network, indicating that "Node #1" is the optimal other node 200. Here, whether or not another node 200 is the optimal depends on whether or not its distance from the local node 200 is the shortest possible. By creating such virtual registry information, it is possible to manage the indicator values ​​for the communication path from the local node 200 to the other nodes 200 that make up the virtual registry, and to determine the optimal file transmission path.

[0031] When the virtual registry management unit 230 receives a file request from the file request unit 240, it refers to the virtual registry information and identifies the node 200 that holds the requested file from among the nodes 200 that constitute the virtual registry. The virtual registry management unit 230 then sends the file request to the identified node 200 via the communication interface unit 210. If the node 200 that holds the file requested by the file request unit 240 is not included in the virtual registry information, the virtual registry management unit 230 may send the file request to the CDC node 100 via the communication interface unit 210.

[0032] The file request unit 240 requests that the virtual registry retrieve the files necessary for its own node 200. For example, when deploying a VNF to the local node 200, the file request unit 240 corresponds to the VNF management unit and requests the files used for the VNF deployment. The file request unit 240 also notifies the virtual registry management unit 230 of the identification information of the requested files.

[0033] The file acquisition unit 250 acquires files transmitted from the CDC node 100 and other nodes 200 that constitute the virtual registry and received by the communication interface unit 210. For example, when deploying a VNF on the local node 200, the file acquisition unit 250 corresponds to the control unit of the VNF.

[0034] The virtual registry management unit 230 may also instruct the node 200 that is the recipient of the file request to send the file to a specified destination. In this case, the destination may be the file acquisition unit 250, or the virtual registry management unit 230 or the file request unit 240 that is the source of the file request. If the destination is the virtual registry management unit 230 or the file request unit 240, the virtual registry management unit 230 or the file request unit 240 should pass the received file to the file acquisition unit 250. Furthermore, if the local node 200 constitutes the virtual registry of another node 200, the virtual registry management unit 230 may instruct the other node 200 to send the file according to the request from the other node 200, or the local node 200 may acquire the file and transfer it to the other node 200.

[0035] Next, the method for retrieving files in the file management system configured as described above will be explained with reference to the sequence diagram shown in Figure 5. In the following, we will describe the case where one node 200 retrieves files from a virtual registry that includes multiple other nodes 200 in order to deploy a VNF. The node 200 that retrieves the files will be referred to as "node #x", and the virtual registry will include the other nodes 200, "node #1" and "node #2".

[0036] When a new VNF is to be deployed to node #x, the file request unit 240 requests the files necessary for the VNF deployment (step S101). The file request from the file request unit 240 is received by the virtual registry management unit 230, which then references the virtual registry information (step S102). Specifically, by referencing the virtual registry information, the node 200 that holds the requested files among the nodes 200 that make up the virtual registry is identified. Here, we will continue the explanation assuming that the requested files are held by node #2.

[0037] Furthermore, when the virtual registry information is referenced and node #2, which holds the file, is identified, if node #2 is not the optimal node 200, the virtual registry management unit 230 may send a command to optimize node 200 for holding the file. That is, a command may be sent to the identified node #2 instructing it to copy the file to another node 200 with the smallest possible index value in the communication path from node #x. By doing so, the topology information managed by the CDC node 100 is updated, and consequently, the virtual registry information managed by node #x is updated. As a result, it becomes possible to retrieve the file from another node 200 with a small index value in the communication path, enabling efficient network utilization that takes into account the load on the network and node 200.

[0038] When the virtual registry management unit 230 identifies node #2, a file request to node #2 is sent from the communication interface unit 210 (step S103). Upon receiving the file request, node #2 sends the file to node #x according to the request (step S104). The file received by node #x is retrieved by the file retrieval unit 250, and the VNF deployment is performed using the file.

[0039] Thus, since node #x retrieves files from node #2, which constitutes the virtual registry, it does not need to retrieve files from CDC node 100. This avoids the concentration of communication on network lines close to CDC node 100, for example, and allows for more efficient use of the network. In other words, it is possible to distribute communication and reduce the load on the network.

[0040] As described above, according to this embodiment, RDC or GC nodes each construct a virtual registry that includes nodes other than CDC nodes based on the network topology, and retrieve files from the virtual registry. Therefore, not all nodes retrieve files from CDC nodes, and communication for sending and receiving files does not concentrate on a specific point on the network line. As a result, communication can be distributed, and the load on the network can be reduced.

[0041] (Embodiment 2) By the way, in Embodiment 1 described above, the file acquired by node 200 may consist of multiple layers. Therefore, Embodiment 2 will describe the case in which node 200 acquires the layers that make up the file from a virtual registry.

[0042] The configuration of the communication system according to Embodiment 2 is the same as that of Embodiment 1 (Figure 1), so its description will be omitted.

[0043] Figure 6 is a block diagram showing the configuration of a file management system according to Embodiment 2. In Figure 6, the same reference numerals are used for the same parts as in Figure 2, and their descriptions are omitted. In the file management system shown in Figure 6, node 200 has a virtual registry management unit 260, a layer acquisition unit 270, and a file restoration unit 280 instead of the virtual registry management unit 230 and the file acquisition unit 250.

[0044] The virtual registry management unit 260 constructs and manages the virtual registry of its own node 200 and controls the acquisition of layers from the virtual registry. Specifically, the virtual registry management unit 260 uses topology information to create virtual registry information that associates the layers constituting a file with the node 200 that holds the layer. That is, as shown in Figure 7, for example, the virtual registry management unit 260 creates virtual registry information that indicates the other node 200 that holds each layer and the index value in the communication path to that other node 200.

[0045] In the virtual registry information shown in Figure 7, distance is used as the indicator value for the communication path. For example, "Layer #1" is shown to be held by "Node #2", which is "1" away from Node 200 on the network. Similarly, "Layer #4" is shown to be held by "Node #5", which is "7" away from Node 200 on the network. Furthermore, "Layer #5" is shown to be held by no other Node 200.

[0046] When the virtual registry management unit 260 receives a file request from the file request unit 240, it refers to the virtual registry information to identify the node 200 that holds the layers constituting the requested file. The virtual registry management unit 260 then sends a layer request to the identified node 200 via the communication interface unit 210. If the node 200 holding the desired layer is not included in the virtual registry information, the virtual registry management unit 260 may send a layer request to the CDC node 100 via the communication interface unit 210.

[0047] The layer acquisition unit 270 acquires layers transmitted from the CDC node 100 and other nodes 200 that constitute the virtual registry and received by the communication I / F unit 210. The layer acquisition unit 270 may acquire multiple layers that constitute a single file from different CDC nodes 100 and other nodes 200.

[0048] The file restoration unit 280 restores the file using multiple layers acquired by the layer acquisition unit 270. The file restored by the file restoration unit 280 is held on the local node 200 and used for VNF deployment. Furthermore, if the local node 200 constitutes a virtual registry for another node 200, the layers constituting the held file may be sent to the other node 200 in accordance with a request from that other node 200.

[0049] Next, the method for retrieving files in the file management system configured as described above will be explained with reference to the sequence diagram shown in Figure 8. In Figure 8, the same reference numerals are used for the same parts as in Figure 5. In the following, we will explain the case in which one node 200 retrieves the layers that make up a file from a virtual registry that includes multiple other nodes 200. The node 200 that retrieves the layers will be referred to as "node #x", and the virtual registry will include the other nodes 200, "node #1" and "node #2".

[0050] When a new VNF is to be deployed to node #x, the file request unit 240 requests the files necessary for the VNF deployment (step S101). The file request from the file request unit 240 is received by the virtual registry management unit 260, which then references the virtual registry information (step S201). Specifically, by referencing the virtual registry information, the node 200 that holds the layer constituting the requested file among the nodes 200 that make up the virtual registry is identified. Here, we will continue the explanation assuming that the layer constituting the requested file is held by nodes #1 and #2.

[0051] When the virtual registry management unit 260 identifies nodes #1 and #2, a layer request is sent from the communication interface unit 210 to nodes #1 and #2 (step S202). Nodes #1 and #2, upon receiving the layer request, send the layer to node #x according to the request (step S203). The layer received by node #x is acquired by the layer acquisition unit 270, and the file is restored from the acquired layer by the file restoration unit 280 (step S204). Then, the VNF deployment is performed using the restored file.

[0052] Thus, node #x obtains the layers that make up the file from nodes #1 and #2, which constitute the virtual registry. Therefore, it does not need to obtain layers from CDC node 100, thus avoiding a concentration of communication on network lines close to CDC node 100. In other words, communication can be distributed, reducing the load on the network. Furthermore, because node #x obtains the requested file from the virtual registry layer by layer, it can obtain layers from other nodes 200 that hold files containing layers common to the requested file, and restore the file. That is, node #x can obtain the layers necessary to restore the file even from other nodes 200 that do not hold the same file as the file it requests.

[0053] As described above, according to this embodiment, RDC or GC nodes each construct a virtual registry including nodes other than CDC nodes based on the network topology, and obtain the layers that make up the file from the virtual registry. Therefore, not all nodes obtain layers from CDC nodes, and communication for sending and receiving layers does not concentrate at a specific point on the network line. As a result, communication can be distributed and the load on the network can be reduced. In addition, since the layers that make up the file are obtained on a layer-by-layer basis, the necessary layers can be efficiently obtained from multiple nodes that make up the virtual registry.

[0054] In the embodiments described above, it was assumed that node 200 has a topology information acquisition unit 220 and virtual registry management units 230 and 260. However, the topology information acquisition unit 220 and virtual registry management units 230 and 260 do not necessarily have to be provided on node 200. That is, the topology information acquisition unit 220 and virtual registry management units 230 and 260 may be provided on a file management device separate from node 200, which is housed in the RDC or GC, and node 200 may request files from this file management device. In this case, the file management device acquires files from the virtual registry in accordance with the request from node 200 and transfers the files to node 200.

[0055] The CDC node 100 according to each of the above embodiments can be configured using a processor and memory. Figure 9 is a block diagram showing an example of the hardware configuration of the CDC node 100 according to each embodiment. As shown in Figure 9, the CDC node 100 has a processor 101, memory 102, storage 103 and a communication unit 104.

[0056] The processor 101 includes, for example, a CPU (Central Processing Unit), an FPGA (Field Programmable Gate Array), or a DSP (Digital Signal Processor), and provides overall control of the CDC node 100, as well as performing various information processing tasks.

[0057] Memory 102 includes, for example, RAM (Random Access Memory) or ROM (Read Only Memory) and stores information used for information processing performed by processor 101.

[0058] The storage device 103 has, for example, an HDD (Hard Disk Drive) or an SSD (Solid State Drive) and stores various types of data.

[0059] The communication unit 104 has an interface for performing wired or wireless communication and communicates with the node 200.

[0060] The CDC node 100 may also have other components not shown, such as a display or operating switches.

[0061] Similarly, the node 200 according to each of the above embodiments can be configured using a processor and memory. Figure 10 is a block diagram showing an example of the hardware configuration of the node 200 according to each embodiment. As shown in Figure 10, the node 200 has a processor 201, memory 202, storage 203 and a communication unit 204.

[0062] The processor 201 includes, for example, a CPU, FPGA, or DSP, and provides overall control of the node 200, as well as performing various information processing tasks.

[0063] Memory 202, for example, includes RAM or ROM, and stores information used for information processing performed by processor 201.

[0064] Storage 203 has, for example, an HDD or SSD, and stores various types of data.

[0065] The communication unit 204 has an interface for performing wired or wireless communication and communicates with the CDC node 100 and other nodes 200.

[0066] Note that node 200 may have other components not shown, such as a display or operating switches.

[0067] The processing performed by CDC node 100 and node 200 as described in each of the above embodiments can also be written as programs that can be executed by a computer. In this case, these programs can be stored in a computer-readable and non-transitory recording medium and installed on the computer. Examples of such recording media include portable recording media such as CD-ROMs, DVD discs, and USB memory, as well as semiconductor memory such as flash memory.

[0068] This disclosure is not limited to the embodiments described above, but also includes various modifications in which components are added, removed, or replaced from the above-described configuration.

[0069] Furthermore, the term "connection" as used in this disclosure means a logical connection for communication. For example, "B connected to A" means that A and B are logically connected in a way that enables communication. Therefore, A and B do not need to be directly connected by physical cables or the like, and multiple devices or wireless communications may be interposed between A and B.

[0070] The disclosure described above includes the following [1] through [9].

[0071] [1] Having one or more processors, The one or more processors described above are: Managing management information that associates multiple nodes belonging to a communication network with files held on each of those multiple nodes, Accepting file requests, By referring to the aforementioned management information, identify the node that holds the file corresponding to the file request, Instructing at least one of the identified nodes to send the file corresponding to the file request to the specified destination, A file management device that performs processing including the above.

[0072] [2] The process described above is: Based on the index value for sending the file corresponding to the file request, the node that will send the file corresponding to the file request to the specified destination is determined from among the identified nodes. The file management device described above [1] further includes the following:

[0073] [3] The index value is calculated based on the distance, throughput, or traffic volume of the communication path through which the file corresponding to the file request passes. The file management device described in [2] above.

[0074] [4] The above-mentioned management is The management information is created based on information regarding the connection relationships of the multiple nodes and information regarding the files held by the multiple nodes. The file management device described in [1] above, including the above.

[0075] [5] The above-mentioned management is Obtaining information regarding the connection relationships of the multiple nodes and information regarding the files held by the multiple nodes from a node located in the center of the communication network. The file management device described above [4], including the above.

[0076] [6] The above-mentioned management is This includes managing management information that associates multiple layers that make up a file with the nodes that hold those layers, The aforementioned determination means that This includes referring to the management information to identify the node that holds the layers constituting a predetermined file, The above instructions are, This includes instructing at least one of the identified nodes to send the layers that constitute the file corresponding to the file request. The file management device described in [1] above.

[0077] [7] The process described above is: To restore the file corresponding to the file request using the layer transmitted in response to the instructions. The file management device described above [6] further includes the following:

[0078] [8] Having one or more processors, The one or more processors described above are: Managing management information that associates multiple nodes belonging to a communication network with files held on each of those multiple nodes, Accepting file requests, By referring to the aforementioned management information, identify the node that holds the file corresponding to the file request, Sending the file corresponding to the file request from at least one of the identified nodes to the source of the file request, A virtual registry system that performs processes including those mentioned above.

[0079] [9] Managing management information that associates multiple nodes belonging to a communication network with files held on each of the multiple nodes, Accepting file requests, By referring to the aforementioned management information, identify the node that holds the file corresponding to the file request, Retrieving the file corresponding to the file request from at least one of the identified nodes, A method for obtaining a file containing [a certain characteristic]. [Explanation of Symbols]

[0080] 100 CDC nodes 101, 201 processors 102, 202 memory 103, 203 storage 104, 204 Communications Department 110 Topology Management Department 120 File Storage Unit 130, 210 Communication I / F section 200 nodes 220 Topology Information Acquisition Unit 230, 260 Virtual Registry Management Department 240 File Request Section 250 File Acquisition Unit 270 Layer Acquisition Unit 280 File Recovery Unit 300 base stations

Claims

1. Having one or more processors, The one or more processors described above are: From a first node located in the first layer of the communication network topology, information regarding the connection relationships of multiple second nodes located in layers lower than the first layer, and information regarding files held by the multiple second nodes, Based on information regarding the connection relationships of the plurality of second nodes and information regarding the files held by the plurality of second nodes, management information is created that associates the plurality of second nodes with the files held by each of the plurality of second nodes. Accepting file requests, By referring to the management information, identify the second node that holds the file corresponding to the file request, Instructing at least one of the identified second nodes to send the file corresponding to the file request to the specified destination, A file management device that performs processing including the above.

2. The aforementioned process is, Based on the index value for sending the file corresponding to the file request, a second node is determined from among the identified second nodes to send the file corresponding to the file request to the designated destination. The file management device according to claim 1, further comprising:

3. The aforementioned index value is calculated based on the distance, throughput, or traffic volume of the communication path through which the file corresponding to the file request passes. The file management device according to claim 2.

4. Creating the above means This includes creating management information that associates multiple layers that make up a file with a second node that holds the layers, The aforementioned determination means that This includes identifying a second node that holds the layers constituting a predetermined file by referring to the management information, The above instructions are, This includes instructing at least one of the identified second nodes to send the layers that constitute the file corresponding to the file request. The file management device according to claim 1.

5. The aforementioned process is, To restore the file corresponding to the file request using the layer transmitted in response to the instructions. The file management device according to claim 4, further comprising:

6. Having one or more processors, The one or more processors described above are: From a first node located in the first layer of the communication network topology, information regarding the connection relationships of multiple second nodes located in layers lower than the first layer, and information regarding files held by the multiple second nodes, Based on information regarding the connection relationships of the plurality of second nodes and information regarding the files held by the plurality of second nodes, management information is created that associates the plurality of second nodes with the files held by each of the plurality of second nodes. Accepting file requests, By referring to the management information, identify the second node that holds the file corresponding to the file request, Sending the file corresponding to the file request from at least one of the identified second nodes to the source of the file request, A virtual registry system that performs processes including those mentioned above.

7. A computer, From a first node located in the first layer of the communication network topology, information regarding the connection relationships of multiple second nodes located in layers lower than the first layer, and information regarding files held by the multiple second nodes, Based on information regarding the connection relationships of the plurality of second nodes and information regarding the files held by the plurality of second nodes, management information is created that associates the plurality of second nodes with the files held by each of the plurality of second nodes. Accepting file requests, By referring to the management information, identify the second node that holds the file corresponding to the file request, Obtain the file corresponding to the file request from at least one of the identified second nodes, How to obtain the file to execute.

Images