KR20200099268A - Satellite data service system for sharing the data - Google Patents

Abstract

The present invention relates to a satellite data service system. According to the present invention, the satellite data service system comprises: a plurality of networked nodes for distributing and storing a satellite data file registered from a node in individual storage and transmitting the stored satellite data file in response to a request for the satellite data file from another node; and a service server storing information on the usage status of the satellite data file input from the plurality of nodes and managing the maintenance or deletion of the satellite data file in the individual storage of the plurality of nodes storing the satellite data file based on the information on the usage status. As described above, since the satellite data service system of the present invention stores and services the satellite data by distributing the data to a plurality of nodes, the system is advantageous for data normalization and is capable of efficient operation of a storage resource of an individual user.

Description

Satellite data service system for data sharing {SATELLITE DATA SERVICE SYSTEM FOR SHARING THE DATA}

The present invention relates to a satellite data service system, and more particularly, to a satellite data service system that stores satellite data for sharing satellite data among multiple users and provides satellite data according to a user's request.

Satellite data observed by artificial satellites are currently being used in various fields such as soil moisture, environment, ocean, geology, resources, and weather/climate, and the scope of use is continuously expanding. However, the data capacity of satellite data is not small, and in particular, when used for time series analysis, it becomes big data, and individual users who use satellite data have difficulty in receiving, storing, and managing the entire data.

For the convenience of storing and managing satellite data for each user, a way to share satellite data between users using a shared URL can be considered, but trust in the storage of the other party's data, including concerns about server failures of the sharing partner, etc. Because it is difficult, in most cases, each user individually stores and manages data. In addition, there is a problem that the burden on satellite data operation is further increased by performing data backup in preparation for data loss due to a server failure of the user.

As described above, the conventional satellite data management method causes inefficient operation of data storage from the perspective of each user. In addition, since each user processes satellite data in their own data format, stores and manages them individually, there is a difficulty in data normalization for compatibility and sharing of satellite data.

Korean Patent Registration No. 15191897 (2015.05.04)

The present invention was conceived to solve the problems of the prior art described above, and an object of the present invention is to provide a satellite data service system that provides a service to a user terminal requesting satellite data by storing satellite data distributed in a plurality of nodes.

The above object is a satellite data service system based on a distributed storage file system according to an aspect of the present invention, in which satellite data files registered from each node are distributed and stored in individual storage, and the satellite data files of other nodes are A plurality of networked nodes for transmitting the stored satellite data file in response to a request; And the satellite data in individual storage of the plurality of nodes for storing information on the usage status of the satellite data files input from the plurality of nodes, and storing the satellite data files based on the information on the usage status. It can be achieved by a satellite data service system comprising a service server that manages the maintenance or deletion of files.

Here, the node may assign an identification code for identification of the satellite data file to the satellite data file registered in the node, and the plurality of nodes may request the satellite data file based on the identification code.

Meanwhile, the service server may include a file information storage unit for storing information on the registered satellite data file; A usage status storage unit for storing information on usage status of the satellite data files input from the plurality of nodes; And a file management unit determining whether to maintain or delete the satellite data files in individual storages of the plurality of nodes based on the information on the usage status.

Here, when it is determined that a node using the satellite data file exists based on the information on the usage status, the file management unit may control to maintain the corresponding satellite data file in at least one of the nodes.

In this case, the file management unit may determine the number of nodes that maintain the satellite data file among the plurality of nodes in proportion to the number of nodes using the satellite data file according to the information on the usage status.

Meanwhile, the service server may further include a price calculation unit for calculating a satellite data service charge according to the use of the satellite data file of each node and a reward amount according to storage of the satellite data file for a plurality of the nodes. .

In addition, the service server further comprises a node for storing the satellite data file and a distributed node information storage unit for storing information on a file storage period in which the storage of the satellite data file is continued in the node, and the amount calculation unit , A storage node for storing the satellite data file based on an overlap period in which the file storage period of the satellite data file and the use period of the satellite data file according to the usage status stored in the usage status storage unit overlap each other, and the The reward amount and the satellite data service charge may be calculated for the node using the satellite data file.

In addition, the distributed storage file system may be an IPFS (Inter Planetary File System).

On the other hand, the satellite data file is a file in a grid format, and the node is input from the grid of the stored satellite data file based on information about the rows and columns of the grid input from the file request node that requested the satellite data file. At least one grid cell corresponding to the row and column according to the information may be extracted and transmitted to the file requesting node in units of grid cells.

In addition, the node stores information on a file format that is allowed to be registered, and when registering the satellite data file, it checks whether the file format conforms to the file format based on the header of the satellite data file to allow registration of the satellite data file. Can be determined.

As described above, according to the present invention, since satellite data is stored and serviced by distributing it to a plurality of nodes, it is possible to efficiently manage storage resources of individual users and is advantageous for data normalization.

In addition, according to the present invention, by providing a data management method according to whether or not each file is actually utilized, and a reward and billing method according to the data service, it is possible to promote equity between service users and to enable efficient operation of the service system.

1 is a block diagram showing the configuration of a satellite data service system according to an embodiment of the present invention;
2 is a data table showing an example of an identification code assigned to a satellite data file registered from a node according to an embodiment of the present invention;
3 is a block diagram showing the configuration of a service server according to an embodiment of the present invention;
4 is an example of a data table stored in a file information storage unit of a service server according to an embodiment of the present invention;
5 is a first embodiment of a data table stored in a usage status storage unit of a service server according to an embodiment of the present invention;
6 is a second embodiment of a data table stored in a usage status storage unit of a service server according to an embodiment of the present invention;
7 is an example of a data table stored in a distributed node information storage unit of a service server according to an embodiment of the present invention; And
8 is a reference diagram for explaining an example of calculating a reward amount and a data service fee according to an amount calculating unit of a service server according to an embodiment of the present invention.

Hereinafter, specific embodiments of the present invention will be described with reference to the drawings.

The satellite data file described in this specification is not only the original of the file received from the satellite, but also the coordinates or vectors for the required area in a file corresponding to the entire spatial area or converting the format, coordinate system, and resolution of the file from the original file. Includes files created through processing or pre-processing by extracting only data corresponding to some regions using vector geometry.

1 is a block diagram showing the configuration of a satellite data service system according to an embodiment of the present invention. Referring to FIG. 1, a satellite data service system 1 according to an embodiment of the present invention includes a plurality of nodes 100_1 to 100_n and a service server 200.

The nodes 100_1 to 100_n are elements constituting the distributed storage file system 1a, and are terminals operated or possessed by a service user using a satellite data service. Here, as the distributed storage file system, various known system types including an Inter-Planetary File System (IPFS) may be applied. Since the IPFS system and the like are already known and used systems, detailed descriptions thereof will be omitted for convenience of description.

Each node 100 includes storage for storing satellite data files, and a plurality of nodes 100 network with each other to transmit a file requested from another node 100 or receive a file requested by the node 100 (Networking) becomes. The node 100 may be a desktop, laptop, or tablet computer used by various subjects such as schools, research institutes, companies, and individuals.

The node 100 receives a satellite data file from a service user and registers it in the distributed storage file system 1a, and the registered satellite data files are distributed and stored in the storage of the plurality of nodes 100. When a satellite data file is registered in each node 100, each node 100 is assigned an identification code for identification of each satellite data file, such as a hash code, and a plurality of nodes 100 A satellite data file may be requested based on the identification code given by the registered node 100. In this way, in order to assign an identification code, a plurality of nodes 100 may distribute and manage a hash table based on a Distributed Hash table (DHT).

FIG. 2 is a data table showing an example of an identification code assigned to a satellite data file registered from each node 100. Referring to FIG. 2, when three files in the tif format are registered by the node 100, You can check the hash code assigned to each file. Regardless of the file name of the identification code, each node 100 may adopt a content-based allocation method in which the same code is assigned if the contents of the file are the same, and different codes are assigned if the contents are different. As described above, since the identification code is assigned to the satellite data file can be implemented based on various known hash algorithms that generate a hash code using a hash function, a detailed description thereof will be omitted for simplicity of explanation. .

Meanwhile, a plurality of nodes 100 store information on a preset file format, and when each node 100 registers a satellite data file with the distributed storage file system 1a, the header of the registered satellite data file It is possible to determine whether to register a satellite data file by checking whether it conforms to the stored file format based on (Header). For example, the node 100 is a lattice raster format, which allows only some formats such as tif, netcdf, and hdf to set the format standard, and when registering a file, whether the corresponding file meets the format standard simply by the file name extension. It is possible to prevent illegal files from being distributed by determining this through the header rather than checking it.

A plurality of nodes 100 are networked with each other to distribute and store satellite data files registered in one node 100, and in response to a file request from another node 100, a node that requests the file stored in its own storage Send to 100. In this way, files registered in a plurality of nodes 100 are distributed and stored, thereby reducing the burden of storing files for each individual node, and is effective in achieving data normalization by sharing one registration file equally among a plurality of nodes. .

On the other hand, when the format of the satellite data file is a grid raster format, the node 100 may perform the request by limiting information on the rows and columns of the grid when the satellite data file is requested, and a plurality of nodes receiving the request The 100 may extract grid cells corresponding to rows and columns input by the file requesting node requesting the file from the file stored in the storage and transmit it to the file requesting node in units of grid cells. According to this, it is possible to selectively receive only portions that are substantially used for analysis, excluding portions corresponding to unnecessary spatial regions, thereby improving data transmission efficiency and saving time required for processing the received data file. In this way, extracting and providing a part of the stored file can be achieved by implementing a new function by wrapping it based on the offset function supported by IPFS.

The service server 200 stores registration information of satellite data files, usage status of satellite data files of a plurality of nodes 100, and information on nodes 100 that distribute and store registered satellite data files, and the like It calculates the service charge or reward amount according to the service use of each node 100, and determines whether to keep/delete whether to continue storing or deleting a specific satellite data file in the individual storage of each node 100. Manage.

3 is a block diagram showing the configuration of a service server 200 according to an embodiment of the present invention. Hereinafter, the configuration of the service server 200 will be described in more detail with reference to FIG. 3. Referring to FIG. 3, the service server 200 includes a file information storage unit 210, a usage status storage unit 220, a distributed node information storage unit 230, a file management unit 240, and an amount calculation unit 250. Includes.

The file information storage unit 210 stores information on satellite data files registered from each node 100. The file information storage unit 210 may store an ID or code assigned to identify the node 100 itself or a user of the node 100 as information about the node 100 that has registered the corresponding satellite data file. The file name of the file, the identification code assigned to the file at the time of registration, the file capacity, the file registration date, and the number of times the file is used by the plurality of nodes 100 may be stored.

4 shows an example of a data table stored in the file information storage unit 210 according to an embodiment of the present invention.

Referring to FIG. 4, one record for each file is stored in the data table stored in the file information storage unit 210, and the data item includes a file registrant (a1), a file name (a2), and a file identification code (a3). , File capacity (a4), file registration date (a5), number of uses (a6), meta data (a7), etc. may be included.

Here, the file registrant (a1) is the identifier of the node 100 that registered the satellite data file, and is an ID or code assigned to each node 100 or user of the node 100, and the file name (a2) is the node 100 ), the file identification code (a3) is the identification code assigned to each file when the file is registered, the file capacity (a4) is the capacity of the registered satellite data file, and the file registration date (a5) is the node 100 ) Means the date the file was registered.

The number of times of use (a6) is the number of times the file was registered and then transmitted to the node 100 that requested the file at the request of each node 100 and serviced, and information on transmission and reception of satellite data files between a plurality of nodes 100 Can be identified by collecting. For example, the service server 200 collects log records regarding data reception or transmission from each node 100 to another node 100, or monitors whether data is received or transmitted between each node 100 in real time and used. The data of the number of times (a6) can be updated. Alternatively, the number of file users who have expressed their intention to use may be counted and updated through the usage status storage unit 220.

Meta data of the registered satellite data file is stored in the meta data (a7) item. As metadata (a7), attributes or additional information about the file, such as the organization that created the file, the satellite that is the source of the file, and the file creation date, are stored. This can be saved in XML format according to standards such as ISO19139. have.

Meanwhile, although not shown in FIG. 4, the file information storage unit 210 may receive and store information on whether or not the registered file can be deleted from the registration node when registering the file. For example, if the node 100 registering the file does not want the file to be deleted from its local storage, information about this may be stored together in the file information storage unit 210.

Next, the usage status storage unit 220 stores information on the usage status of the registered satellite data file. Information on the usage status may be input from a plurality of nodes 100, respectively. Here, the usage status refers to whether or not the node 100 is used for a specific satellite data file, and includes not only a case currently being used but also a case scheduled to be used in the future. For example, when a specific satellite data file'A' is currently being used or is scheduled to be used in the future, each node 100 expresses its intention to use the'A' file according to a preset standard, and In addition, if there is no plan to use the'A' file in the future, it can be expressed that there is no intention to use it.

When each node 100 inputs usage status information for an individual file, a pattern phrase may be allowed in the file name for convenience of input. For example, Global_Precipitation_2019011% by inserting a pattern phrase in the part representing the date in the file name so that information on the usage status can be entered, so that the usage status of files corresponding to the file from January 10, 2019 to January 19, 2019 Can be entered in batches. According to this, the usage status of the time series file can be saved with a single input, which greatly increases the convenience.

5 shows a first embodiment of a data table stored in the usage status storage unit 220 according to an embodiment of the present invention.

5, the data items of the data table stored in the usage status storage unit 220 include a file user (b1), a file name (b2), a registration intent to use (b3), a file evaluation grade (b4), and a file use period. Item (b5) may be included.

The file user (b1) is the identifier of the node 100 that receives and uses the registered satellite data file, and is an ID or code assigned to each node 100, and the file name (b2) is the node 100 among a plurality of registered files. Is the name of the target file that expressed intentions regarding the usage status.

The date of registration of intention to use (b3) refers to the date on which a specific file with a file name according to the file name (b2) is being used or an intention to use is expressed. At this time, when the node 100 expresses its intention to use, the date of expression is entered on the intent to use registration date (b3), and if the node 100 does not specifically express the intention to use it, the use intention registration date (b3) item Can be null. In this way, depending on whether the use intention registration date (b3) is null, it is possible to indirectly identify the use status, but separate from the use intention registration date (b3), data items related to the use status or intention to use may be separately operated. Of course.

The file evaluation grade (b4) is an item in which information on the grade or evaluation score that evaluates the quality or contents of the file having the file name according to the file name (b2) in the node 100 using the registered file is stored, The file use period (b5) stores the use period of the satellite data file according to the file use status of the file user. For example, as the using node uses the registration file from January 21, 2019 to February 22, 2019, the start date of using the registration file and the end date of ending use may be entered. Accordingly, the end date may not be specified. On the other hand, when the node 100 does not use the file, the file use period b5 may be stored as null.

As shown in FIG. 5, the usage status storage unit 220 may store information on the usage status based on the file name input when registering the file, but as another example, the usage status storage unit 220 is used when registering a file. It goes without saying that it is also possible to store information on usage status based on the file identification code assigned to each file.

6 shows a second embodiment of a data table stored in the usage status storage unit 220 according to an embodiment of the present invention.

The data table according to FIG. 5 includes data items related to the file name b2, but referring to FIG. 6, the data items shown in FIG. 5 are the same except that the file identification code c2 is stored instead of the file name.

The usage status storage unit 220 may alternatively operate the above-described file name-based data table and the file identification code-based data table, or both.

The distributed node information storage unit 230 stores information about a file storage period, which is a period during which the storage of the corresponding file is continued, in the node 100 for distributed storage of each file and the storage of the node 100.

7 shows an example of a data table stored in the distributed node information storage unit 230 according to an embodiment of the present invention.

Referring to FIG. 7, data items of a data table stored in the distributed node information storage unit 230 may include a file store (d1), a file identification code (d2), and a file storage period (d3).

Here, the file store (d1) is an ID or identification code assigned to identify each node 100 that distributes and stores a registered file, and the file identification code (d2) is an identification code assigned to each file when registering the file. , The file storage period (d3) refers to the period in which the storage of a specific registered file having a file identification code (d2) in the node 100 according to the file store (d1) has been continued, and the starting point of saving the file And files can be deleted and saved as the end point when saving is finished. In this case, it goes without saying that the end point may not be specified when the file is maintained without being deleted. The file storage period d3 item may be stored by collecting information on whether to store or delete a file from each node 100 in which the corresponding file is distributed and stored.

Next, the file management unit 240 determines whether or not the registered satellite data files are required, and determines whether to store or delete the satellite data files in individual storages of the plurality of nodes 100.

That is, when it is determined that there is a node using a specific satellite data file based on the usage status information stored in the usage status storage unit 220, the file management unit 240 is at least one of the plurality of nodes 100 At 100, it is possible to control the storage of the satellite data file to be maintained. In this case, when there is at least one node using a specific satellite data file, the file management unit 240 may control the storage to be maintained in all nodes 100 that store the above file. Alternatively, the file management unit 240 is the node 100 that maintains the satellite data file among the plurality of nodes 100 in proportion to the number of nodes 100 using the satellite data file according to the information on the usage status. It is also possible to adaptively determine the number of. For example, according to the usage status information stored in the usage status storage unit 220, comparing the cases in which the number of nodes 100 currently using the satellite data file'A' is 10 and 1000 cases, the usage node 100 When the number of) is 1000, it is possible to control so that the storage of the'A' file is maintained in a relatively larger number of nodes 100.

The amount calculation unit 250 calculates a satellite data service charge according to the use of the satellite data file of each node 100 and a reward amount according to storage of the satellite data file for the plurality of nodes 100. That is, a service fee is charged to the node that uses the data by requesting and receiving the satellite data file from the other node 100, and conversely, the registered satellite data file is stored in its own storage and the other node 100 For the storage nodes that contributed to the provision of data to the furnace, rewards are provided.

To this end, the amount calculation unit 250 is a file storage period for each node 100 stored in the distributed node information storage unit 230, and the usage status stored in the usage status storage unit 220 Based on the overlapping period in which the use periods of the satellite data files are overlapped according to each other, the reward amount for the storage node that distributes and stores the satellite data files is calculated, and the data service usage fee is charged to the nodes using the satellite data files. .

8 is a reference diagram for explaining an example of calculating a reward amount and a data service fee according to the amount calculation unit 250 according to an embodiment of the present invention.

Referring to FIG. 8, it is assumed that a storage node A and a storage node B exist, and a use node C and a use node D exist. For reference, the storage node refers to a node that distributes and stores the registered satellite data file, and the use node refers to a node that receives and uses the saved satellite data file from another node.

According to FIG. 8, when the distributed node information storage unit 230, the storage node A stores satellite data files in its local storage from 1/15 to 2/19, and the storage node B stores 2/2 to 2 Shows an example of storing satellite data files in local storage up to /28. On the other hand, by the usage status storage unit 220, the usage node C registered the usage status by using the satellite data files stored in the storage nodes A and B from 1/21 to 2/12, and the usage node D It is used from 2/10 to 2/22 and shows an example of registering the usage status.

In such a case, the amount calculation unit 250 is the storage node A, 1/21 to 2/12 overlapping the file use period of the use node C and 2/10 to 2 overlapping the file use period of the use node D. Reward amount is calculated for files saved up to /19. On the other hand, for storage node B, rewards for storing files from 2/2 to 2/12 overlapping with the file use period of using node C and 2/10 to 2/22 overlapping with the file use period of using node D The amount is calculated.

At this time, the reward amount may be distributed to the storage node A and the storage node B until 2/2 to 2/19, which is a period in which the storage node A and the storage node B simultaneously receive rewards for the same data file. In other words, if the reward received by storage node A is 100 until 1/21 to 2/2, which is the period when the storage node A alone was storing the file, it is saved during the period 2/2 to 2/19, when the reward is received simultaneously with storage node B 50 rewards can be distributed to node A and storage node B. In this way, the price calculation unit 250 may distribute a reward corresponding to the file to N storage nodes that store the same file.

On the other hand, during 2/10~2/12, when the usage periods of the usage node C and the usage node D overlap each other for the same file, the usage node C and the usage node D can share the service usage fee for the file. have. For example, if the service usage fee borne by the using node C is 100 until 1/21~2/10, which is the period when the using node C uses the file alone, the usage period overlaps with each other 2/10~2/ In 12, the usage node D and the service usage fee can be divided by 50. In this way, the amount calculation unit 250 may allow the N number of nodes to equally share the service usage fee. At this time, even if a specific period is registered as a usage period according to the usage status, it is difficult to receive actual data service in a section in which the storage node does not exist during the period, so it is possible to exclude it from pricing.

On the other hand, in the section in which the use node does not exist, e.g., according to FIG. 8, in 1/15 to 1/21 and 2/22 to 2/28, rewards according to file storage are provided even if the storage node is storing the file. It is possible not to. Alternatively, the basic reward for saving the file and the reward for using the file are classified, and both the basic reward and the used reward are provided in the section where the usage node exists, and only the basic reward for saving the file in the section where the usage node does not exist. You might be able to provide it.

Meanwhile, the amount calculation unit 250 may consider the file capacity when calculating the reward amount or service usage fee. In this case, the file capacity may refer to information stored in the file information storage unit 210. For example, when the file size is large, the reward or service usage fee can be calculated in proportion to the file size by setting a relatively large reward or service usage fee.

As described above, according to the satellite data service system 1 according to the present invention, since satellite data is distributed and stored in a plurality of nodes based on a distributed storage file system, the storage resources of individual service users are efficiently It is operable and can easily achieve data normalization.

In addition, fairness among service users can be promoted and efficient operation of the system is possible by providing a data management method according to whether each file is actually used and a reward and billing method according to the data service.

Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or combinations thereof. Implementations include a data processing device, e.g., a programmable processor, a computer, or a computer program product, i.e. an information carrier, e.g., machine-readable storage, for processing by or controlling the operation of multiple computers. It can be implemented as a computer program recorded on an apparatus (computer-readable medium). Computer programs such as the above-described computer program(s) may be recorded in any type of programming language including compiled or interpreted languages, and as a standalone program or in a module, component, subroutine, or computing environment. It can be deployed in any form, including as other units suitable for the use of. A computer program can be deployed to be processed on one computer or multiple computers at one site, or to be distributed across multiple sites and interconnected by a communication network.

Processors suitable for processing a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. In general, the processor will receive instructions and data from read-only memory or random access memory or both. Elements of the computer may include at least one processor that executes instructions and one or more memory devices that store instructions and data. In general, a computer may include one or more mass storage devices, such as magnetic, magnetic-optical disks, or optical disks, to store data, receive data from, transmit data to, or both It may be combined so as to be. Information carriers suitable for embodying computer program instructions and data are, for example, semiconductor memory devices, for example, magnetic media such as hard disks, floppy disks and magnetic tapes, Compact Disk Read Only Memory (CD-ROM). ), Optical Media such as DVD (Digital Video Disk), Magnetic-Optical Media such as Floptical Disk, ROM (Read Only Memory), RAM (RAM) , Random Access Memory), flash memory, EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), and the like. The processor and memory may be supplemented by or included in a special purpose logic circuit structure.

Further, the computer-readable medium may be any available medium that can be accessed by a computer, and may include a computer storage medium.

While this specification includes details of a number of specific implementations, these should not be construed as limiting to the scope of any invention or claim, but rather as a description of features that may be peculiar to a particular embodiment of a particular invention. It must be understood. Certain features described herein in the context of separate embodiments may be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination. Furthermore, although features operate in a particular combination and may be initially described as so claimed, one or more features from a claimed combination may in some cases be excluded from the combination, and the claimed combination may be a subcombination. Or sub-combination variations.

Likewise, although operations are depicted in the drawings in a specific order, it should not be understood that such operations must be performed in that particular order or sequential order shown, or that all illustrated operations must be performed in order to obtain a desired result. In certain cases, multitasking and parallel processing can be advantageous. In addition, the separation of the various device components of the above-described embodiments should not be understood as requiring such separation in all embodiments, and the program components and devices described are generally integrated together into a single software product or packaged in multiple software products. You should understand that you can.

On the other hand, the embodiments of the present invention disclosed in the specification and drawings are only presented specific examples to aid understanding, and are not intended to limit the scope of the present invention. In addition to the embodiments disclosed herein, it is apparent to those of ordinary skill in the art that other modified examples based on the technical idea of the present invention may be implemented.

1: Satellite data service system 1a: Distributed storage file system
100: node 200: service server
210: file information storage unit 220: usage status storage unit
230: distributed node information storage unit 240: file management unit
250: amount settlement department

Claims (10)

In a satellite data service system based on a distributed storage file system,
A plurality of networked nodes for distributing and storing the satellite data files registered from each node in individual storage and transmitting the stored satellite data files in response to a request for the satellite data files from other nodes; And
The satellite data file in individual storage of the plurality of nodes that stores information on the usage status of the satellite data files input from the plurality of nodes, and stores the satellite data file based on the information on the usage status Satellite data service system comprising a service server that manages maintenance or deletion of data.
The method of claim 1,
Wherein the node gives an identification code for identification of the satellite data file to the satellite data file registered at the node, and the plurality of nodes request the satellite data file based on the identification code Data service system.
The method of claim 1,
The service server,
A file information storage unit for storing information on the registered satellite data file;
A usage status storage unit for storing information on usage status of the satellite data files input from the plurality of nodes; And
And a file management unit that determines whether to keep or delete the satellite data files in individual storages of the plurality of nodes based on the information on the usage status.
According to claim 3
When it is determined that a node using the satellite data file exists based on the information on the usage status, the file management unit controls at least one node to maintain a corresponding satellite data file. Data service system.
The method of claim 4,
The file management unit determines the number of nodes that maintain a corresponding satellite data file among the plurality of nodes in proportion to the number of nodes using the satellite data file according to the information on the usage status. Service system.
The method of claim 3,
The service server,
And a cost calculation unit for calculating a satellite data service charge according to the use of the satellite data file by each node and a reward amount according to storage of the satellite data file for the plurality of nodes.
The method of claim 6,
The service server further includes a node for storing the satellite data file and a distributed node information storage unit for storing information on a file storage period in which the storage of the satellite data file is continued in the node,
The amount calculation unit stores the satellite data file based on an overlap period in which the file storage period of the satellite data file and the use period of the satellite data file according to the usage status stored in the usage status storage unit overlap each other. A satellite data service system, wherein the reward amount and the satellite data service charge are respectively calculated for a storage node and a use node using the satellite data file.
The method of claim 1,
The distributed storage file system is a satellite data service system, characterized in that the IPFS (Inter Planetary File System).
The method of claim 1,
The satellite data file is a grid format file,
The node includes at least one grid corresponding to the row and column according to the information input from the grid of the stored satellite data file, based on information on the rows and columns of the grid input from the file requesting node that requested the satellite data file. A satellite data service system comprising extracting cells and transmitting them to the file requesting node in units of grid cells.
The method of claim 1,
The node stores information on the file format allowed for registration, and determines whether to allow registration of the satellite data file by checking whether it conforms to the file format based on the header of the satellite data file when registering the satellite data file. Satellite data service system, characterized in that.

Images