WO2022079831A1 - 登録者端末、保有者端末、方法およびプログラム - Google Patents
登録者端末、保有者端末、方法およびプログラム Download PDFInfo
- Publication number
- WO2022079831A1 WO2022079831A1 PCT/JP2020/038779 JP2020038779W WO2022079831A1 WO 2022079831 A1 WO2022079831 A1 WO 2022079831A1 JP 2020038779 W JP2020038779 W JP 2020038779W WO 2022079831 A1 WO2022079831 A1 WO 2022079831A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- file
- token
- identifier
- distributed ledger
- chunk
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 49
- 230000004044 response Effects 0.000 claims description 18
- 230000005540 biological transmission Effects 0.000 claims description 11
- 125000002015 acyclic group Chemical group 0.000 claims 1
- 230000006870 function Effects 0.000 description 106
- 238000004891 communication Methods 0.000 description 35
- 238000010586 diagram Methods 0.000 description 26
- 238000012795 verification Methods 0.000 description 21
- 238000012545 processing Methods 0.000 description 16
- 230000015654 memory Effects 0.000 description 14
- 238000012423 maintenance Methods 0.000 description 9
- 238000006243 chemical reaction Methods 0.000 description 4
- 239000000470 constituent Substances 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 239000012634 fragment Substances 0.000 description 3
- 230000000717 retained effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000002301 combined effect Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005401 electroluminescence Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3234—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
Definitions
- Embodiments of the present invention relate to registrant terminals, holder terminals, methods and programs.
- blockchain which is a type of decentralized distributed ledger technology, is used. Since blockchain has high robustness against tampering, it is being considered to be used for various purposes such as smart contracts that can execute various contracts or transactions in addition to cryptocurrencies.
- transactions are not grouped in the above blocks, but there is also a distributed ledger that is expressed by the connection of transactions.
- a distributed ledger is not suitable for managing the above files because it has a structure in which transactions for the past are left.
- Non-Patent Document 1 As a method of distributed file management, there is a storage in which a file is managed by using a unique identifier (IDentifier) generated from a content hash or the like (for example,). See Non-Patent Document 1). There is also a method in which a file is registered in the storage and the ID of the file is recorded in the distributed ledger and managed (see, for example, Non-Patent Document 2).
- IDentifier unique identifier
- the file identifier When the file identifier is recorded in the distributed ledger, it is possible to specify the file after referring to the distributed ledger, but it is not possible to specify and refer to the corresponding distributed ledger information from the file.
- the present invention has been made by paying attention to the above circumstances, and an object thereof is a registrant terminal, a holder terminal, a method, and a method in which information managed by a distributed ledger can be referred from a file. To provide a program.
- the registrant terminal is a registrant terminal that can be connected to the distributed ledger network, generates a transaction related to the generation of a token in the distributed ledger network, and transmits the transaction to the distributed ledger network.
- the token generation unit that generates the token in the distributed ledger network and the information in which the access information to the token is set in the file to be processed are generated, the identifier of the file to be processed is generated, and the said.
- It includes a registration unit that generates a transaction related to registration of the identifier in the token and registers the identifier in the token by transmitting this transaction to the distributed ledger network.
- the registrant terminal is a file holder terminal that can be connected to a distributed ledger network in which a token including an identifier of a file to be processed is held, and the file to be processed includes the token.
- the acquisition unit that acquires the file identifier from the token by using the access information to the token described in the file to be processed, the file identifier of the file to be processed, and the file identifier of the file to be processed.
- a determination unit for determining that the file identifier acquired by the acquisition unit matches the file identifier is provided.
- the holder terminal is a file holder terminal capable of connecting to a distributed ledger network in which a token including a user identifier which is a legitimate user identifier of a file stored in a storage device is held.
- a token including a user identifier which is a legitimate user identifier of a file stored in a storage device is held.
- the request is related to the acquisition of the file stored in the storage device, and includes the identifier of the user who requested the request.
- the acquisition unit that acquires the user identifier from the token by using the access information to the token described in the file stored in the storage device, the identifier included in the request, and the acquisition. It includes a transmission unit that transmits a file stored in the storage device to the request source when the user identifier acquired by the unit matches.
- the registration method is a method performed by a registrant terminal that can connect to the distributed ledger network, generates a transaction related to the generation of a token in the distributed ledger network, and transfers the transaction to the distributed ledger.
- the token is generated in the distributed ledger network, the information in which the access information to the token is set in the file to be processed is generated, and the identifier of the file to be processed is generated.
- a transaction relating to the registration of the identifier in the token is generated, and the transaction is transmitted to the distributed ledger network to register the identifier in the token.
- the information managed by the distributed ledger can be referred from the file.
- FIG. 1 is a diagram showing an application example of a management system according to an embodiment of the present invention.
- FIG. 2 is a diagram showing an application example of the management system according to the embodiment of the present invention.
- FIG. 3 is a block diagram showing an example of the functional configuration of the file registrant terminal.
- FIG. 4 is a block diagram showing an example of the functional configuration of the file holder terminal.
- FIG. 5 is a block diagram showing an example of the functional configuration of the user terminal.
- FIG. 6 is a diagram showing an example of information managed by a distributed ledger and information managed by a file used in one embodiment of the present invention.
- FIG. 7 is a diagram showing an example of information managed by a distributed ledger and information managed by a file used in one embodiment of the present invention.
- FIG. 1 is a diagram showing an application example of a management system according to an embodiment of the present invention.
- FIG. 2 is a diagram showing an application example of the management system according to the embodiment of the present invention.
- FIG. 3
- FIG. 8 is a diagram showing a sequence for explaining an example of a file registration process for normal storage.
- FIG. 9 is a diagram showing a sequence illustrating an example of a file registration process for a storage in which a file is converted to a DAG.
- FIG. 10 is a diagram showing a sequence for explaining an example of file association verification processing for normal storage.
- FIG. 11 is a diagram showing a sequence for explaining an example of the file association verification process for the storage in which the file is DAG-ized.
- FIG. 12 is a diagram showing a sequence for explaining an example of the file pre-transmission verification process for the normal storage.
- FIG. 13 is a diagram showing a sequence for explaining an example of the file pre-transmission verification process for the storage in which the file is DAG-ized.
- FIG. 14 is a block diagram showing an example of a hardware configuration of a file registrant terminal according to an embodiment of the present invention.
- FIG. 1 and 2 are diagrams showing an application example of the management system according to the embodiment of the present invention.
- FIG. 1 shows an overall network configuration for a management system according to an embodiment of the present invention.
- the file registrant terminal 1, the file holder terminal 2, and the user terminal 3 can be connected via a network, and each terminal can be connected. It is a system that can communicate with each other.
- FIG. 2 shows a network configuration of an application program of a distributed ledger according to a management system according to an embodiment of the present invention.
- the management system 100 according to the embodiment of the present invention includes a file registrant terminal 1, a file holder terminal 2, and a user terminal 3, and each terminal can communicate with each other. Is.
- the file registrant terminal 1, the file holder terminal 2, and the user terminal 3 have an access function to the distributed ledger network 4, and the private key associated with each account (account) is the user and the file registrant. , And under the control of the file owner.
- the location where the private key is stored is not specified.
- the distributed ledger network 4 is composed of a plurality of terminals.
- the file registrant terminal 1 and the file holder terminal 2 may have a node function for maintaining the distributed ledger network 4 with the user terminal 3. Further, a terminal that substitutes for the node function may be provided between each of the distributed ledger network 4, the file registrant terminal 1, the file holder terminal 2, and the user terminal 3.
- the node function is a function for verifying and approving network transactions, and updating and holding ledger information (block information and state database, etc.).
- the file holder terminal 2 or the user terminal 3 has a conversion function from a DAG (Directed acyclic graph) format file to a normal format file.
- the file registrant terminal 1 and the file holder terminal 2 may be the same terminal.
- a terminal that substitutes for the node function may exist in the distributed ledger network 4. This terminal is called another node.
- another node 5 that maintains the distributed ledger network 4 may exist.
- the file registrant terminal 1, the file holder terminal 2, and the user terminal 3 do not have to include the node function when another node 5 that substitutes for the node function exists.
- a case where the file registrant terminal 1, the file holder terminal 2, and the user terminal 3 also execute the node function will be described.
- FIG. 3 is a block diagram showing an example of the functional configuration of the file registrant terminal.
- the file registrant terminal 1 has a file utilization unit 11, an access function unit 12, a node function unit 13, and a communication unit 14.
- the file utilization unit 11 has a file management DB (database) 11a
- the access function unit 12 has a key management DB 12a
- the node function unit 13 has a network (NW) maintenance / identification information DB 13a.
- NW network maintenance / identification information DB 13a.
- the various databases in this embodiment are also referred to as storage.
- the file usage unit 11 manages files, for example, creates, updates, or uses them, and stores the managed data in the file management DB 11a.
- the file utilization unit 11 also manages the key required for managing the file.
- the access function unit 12 issues transactions to the network and sends / receives files to / from other terminals. Further, the access function unit 12 stores the key information used in the access in the key management DB 12a.
- the node function unit 13 executes the above-mentioned node function and stores information for network maintenance and identification in the process in the network (NW) maintenance / identification information DB 13a.
- the communication unit 14 is responsible for communication with the outside.
- FIG. 4 is a block diagram showing an example of the functional configuration of the file holder terminal.
- the file holder terminal 2 has a file utilization unit 21, an access function unit 22, a node function unit 23, and a communication unit 24.
- the file utilization unit 21 has a file management DB 21a
- the access function unit 22 has a key management DB 22a
- the node function unit 23 has a network (NW) maintenance / identification information DB 23a.
- NW network
- the file utilization unit 21 performs the same processing as the file utilization unit 11 described above, and stores the managed data in the file management DB 21a.
- the access function unit 22 performs the same processing as the access function unit 12 described above, and stores the key information used in the access in the key management DB 22a.
- the node function unit 23 executes the above-mentioned node function, and stores the above-mentioned information for network maintenance and identification in the network (NW) maintenance / identification information DB 23a.
- the communication unit 24 is responsible for communication with the outside.
- FIG. 5 is a block diagram showing an example of the functional configuration of the user terminal.
- the user terminal 3 has a file utilization unit 31, an access function unit 32, a node function unit 33, and a communication unit 34.
- the file utilization unit 31 has a file management DB 31a
- the access function unit 32 has a key management DB 32a
- the node function unit 33 has a network (NW) maintenance / identification information DB 33a.
- NW network
- the file utilization unit 31 performs the same processing as the file utilization unit 11 described above, and stores the managed data in the file management DB 31a.
- the access function unit 32 performs the same processing as the access function unit 12 described above, and stores the key information used in the access in the key management DB 32a.
- the node function unit 33 executes the above-mentioned node function, and stores the above-mentioned information for network maintenance and identification in the network (NW) maintenance / identification information DB 33a.
- the communication unit 34 is responsible for communication with the outside.
- FIG. 6 and 7 are diagrams showing an example of information managed by the distributed ledger and information managed by the file used in one embodiment of the present invention.
- token C A and token C A' are managed, and the file hash F A , which is a file identifier, is managed in each token.
- access information to token CA is embedded in the header of each file.
- ID of the file (identifier created from the hash) is recorded in the token, so that the relationship between the correct token and the file can be confirmed.
- the access information to the token is not limited to the example of being embedded in the header of the file as described above.
- a folder structure is generated in the file, and the access information to the token is incorporated in this folder structure. Then, by performing archiving or compression processing by, for example, a tar method or a zip method, a file containing access information to the token may be generated.
- token C A and token C A ⁇ are managed, and in each token, the chunk identifiers chunk hash FC A_1 , chunk hash FC A_2 , and chunk hash FC are managed. Multiple chunk hashes, including A_3 , are managed.
- access information to token CA is embedded in each chunk, and a DAG format file is formed by the chunks in which the access information is embedded in this way.
- the chunk ID (identifier created from the hash) is recorded in the token, so that the correct relationship between the token and the chunk can be confirmed.
- the storage in which files are converted to DAG is, for example, IPFS (InterPlanetary File System).
- IPFS InterPlanetary File System
- the access information is stored at the beginning of the Data item of each IPFS object separately from the chunk information of the file body.
- This registration process is a process in which the identifier related to the file to be processed is registered in the token on the distributed ledger network.
- the storage used in each terminal is divided into normal storage and storage in which files are converted to DAG.
- Normal storage is storage in which files are not DAG-ized.
- FIG. 8 is a diagram showing a sequence for explaining an example of a file registration process for normal storage.
- the file utilization unit 11 of the file registrant terminal 1 instructs the access function unit 12 to generate a token to the distributed ledger, which is a token related to the file to be processed, which is stored in the file management DB 11a (S11). ).
- the access function unit 12 of the file registrant terminal 1 performs a token generation process for the distributed ledger (S12).
- the access function unit 12 creates a transaction for generating a Token to the distributed ledger without including a file identifier, and broadcasts it to the distributed ledger network 4 via the communication unit 14. (S12-1).
- the access function unit 12 sends a transaction result notification request to the node function unit 13 (S12-2).
- the transaction is verified by the consensus algorithm in the distributed ledger network 4. If this transaction meets a predetermined requirement, this transaction is confirmed (S12-3).
- the node function unit 13 When the node function unit 13 receives the transaction result from the distributed ledger network 4 via the communication unit 14, the node function unit 13 returns this result to the access function unit 12 (S12-4). In response to this result, the access function unit 12 creates "access information to Token" for the file to be processed (S12-5). As a result, the processing of S12 is performed. The access function unit 12 returns the created "access information to the Token" to the file usage unit 11 (S13).
- the file utilization unit 11 records the "access information to Token" returned in S13 in the header (sometimes referred to as a file header) of the file to be processed, which is stored in the file management DB 11a. do.
- a plurality of "access information to Token" may be recorded in the file header.
- the file usage unit 11 generates a file identifier (for example, hash) of a file in which access information to the Token is recorded in the file header (S14).
- a file identifier for example, hash
- the file is transmitted to the file holder terminal 2, and the identifier used for file acquisition may be generated by the file holder terminal 2.
- the file utilization unit 11 records the "access information to the Token" returned in S13 in an access information file different from the file to be processed, and then files.
- a file to be processed and an access information file stored in the management DB 11a may be stored in the same folder, and a file may be created by archiving or compressing this folder to generate a file identifier of the file.
- the file usage unit 11 sends a Token update, here an instruction to register a file identifier to the Token, to the access function unit 12 (S15).
- the access function unit 12 performs a file identifier registration process in the Token related to the above-mentioned "access information to the Token" managed by the distributed ledger (S16).
- the access function unit 12 creates a transaction for registering a file identifier in the Token managed by the distributed ledger network 4 and broadcasts it to the distributed ledger network 4 via the communication unit 14 (S16-1). ).
- the access function unit 12 sends a transaction result notification request to the node function unit 13 (S16-2).
- the transaction is verified by the concession algorithm in the distributed ledger network 4. If this transaction meets a predetermined requirement, this transaction is approved (S16-3).
- the node function unit 13 When the node function unit 13 receives the transaction result from the distributed ledger network 4 via the communication unit 14, the node function unit 13 returns this result to the access function unit 12 (S16-4). As a result, the file identifier is recorded in the Token by S16. In response to this result, the access function unit 12 notifies the file utilization unit 11 of the Token update completion notification (S17).
- FIG. 9 is a diagram showing a sequence illustrating an example of a file registration process for a storage in which a file is converted to a DAG.
- the access function unit 12 is instructed to generate a token in the distributed ledger, as in the file registration process for the normal storage.
- the token generation process for the distributed ledger is performed.
- the created "access information to Token" is returned to the file usage unit 11.
- the file utilization unit 11 records "access information to Token" in the header of the file to be processed (S111). Here, a plurality of "access information to Token” may be recorded. (3) The file utilization unit 11 removes the header of the file and divides the remaining portion into temporary chunks (S112). (4) The file utilization unit 11 updates the temporary chunks by adding the header of the file to each temporary chunk (S113).
- the file utilization unit 11 records the "access information to the Token" returned in S13 in the access information file, and the file to be processed and the access information file stored in the file management DB 11a are the same. Create a file by storing it in a folder and archiving or compressing this folder.
- the file utilization unit 11 restores the archived or compressed file to the original folder, removes the access information file stored in this folder, and divides the remaining portion into temporary chunks.
- the file utilization unit 11 updates the temporary chunks by adding the access information to the Token recorded in the access information file stored in the above folder to each temporary chunk (S113).
- the file utilization unit 11 creates a DAG-ized file based on the temporary chunks, and generates an identifier of each chunk forming the DAG-ized file. (S114).
- the file utilization unit 11 records the "access information to the Token" returned in S13 in the access information file, and for each of the temporary chunks, the temporary chunk and the above access information.
- this folder creates an archived or compressed file, creates a DAG file based on this file, and forms this DAG file for each chunk An identifier may be generated.
- the file usage unit 11 sends a Token update, here an instruction to register a chunk identifier to the Token, to the access function unit 12 (S115).
- the access function unit 12 performs a chunk identifier registration process for the Token related to the above-mentioned "access information to the Token" managed by the distributed ledger (S116).
- the access function unit 12 creates a transaction for registering a chunk identifier in the Token managed by the distributed ledger network 4 and broadcasts it to the distributed ledger network 4 via the communication unit 14 (S116-1). ).
- the access function unit 12 sends a transaction result notification request to the node function unit 13 (S116-2).
- the transaction is verified by the concession algorithm in the distributed ledger network 4. If this transaction meets the predetermined requirements, this transaction is approved (S116-3).
- the node function unit 13 When the node function unit 13 receives the transaction result from the distributed ledger network 4 via the communication unit 14, the node function unit 13 returns this result to the access function unit 12 (S116-4). As a result, the chunk identifier is recorded in the Token by S116. In response to this result, the access function unit 12 notifies the file utilization unit 11 of the Token update completion notification (S117).
- the entire file including the header is divided into chunks, so chunks that do not include header information are generated.
- a header including at least access information to the Token is added to each chunk.
- FIG. 10 is a diagram showing a sequence for explaining an example of file association verification processing for normal storage.
- the file usage unit 21 of the file holder terminal 2 acquires "access information to Token" described in the file header of the updated file to be processed (S41), and uses this access information. Then, the access function unit 22 is instructed to acquire the file identifier in the control information in the token managed by the distributed ledger network 4 (S42).
- the file utilization unit 21 restores the archived or compressed file to the original folder. Then, the access information file stored in this folder is acquired, and the file identifier in the control information in the token managed by the distributed ledger network 4 is used by using the "access information to Token" recorded in this access information file. Is instructed to the access function unit 22 to acquire the file.
- the access function unit 22 instructs the node function unit 23 to acquire the control information from the token (S43).
- the node function unit 23 accesses the distributed ledger network 4 via the communication unit 24 to obtain control information from the token related to the above-mentioned "access information to Token" managed by the distributed ledger.
- the file identifier is acquired from the control information, and this file identifier is returned to the access function unit 22 (S44).
- the access function unit 22 returns this file identifier to the file utilization unit 21 (S45).
- the file identifier of the updated file to be processed is stored and managed in the file management DB 21a.
- the file utilization unit 21 acquires the file identifier of the updated file to be processed from the file management DB 21a, compares this file identifier with the file identifier returned in S45, and confirms that they match. (Verification) (S46).
- the file utilization unit 21 restores the file to be processed to the original folder and then stores the file in this folder.
- the file identifier of the updated file to be processed is acquired from the file management DB 21a, and this file identifier is compared with the file identifier returned in S45, and it is confirmed (verified) that they match.
- FIG. 11 is a diagram showing a sequence for explaining an example of the file association verification process for the storage in which the file is DAG-ized.
- the file usage unit 21 of the file holder terminal 2 acquires "access information to Token" described in the chunk of the file to be processed (S141), and acquires control information using this access information. Is instructed to the access function unit 22 (S142). In response to this instruction, the access function unit 22 instructs the node function unit 23 to acquire the control information from the token (S143).
- the file utilization unit 21 is based on the archived or compressed file. Restore to the folder of, acquire the access information file stored in this folder, and use the "access information to Token" recorded in this access information file to control the tokens managed by the distributed ledger network 4. Instruct the access function unit 22 to acquire the file identifier in the information.
- the node function unit 23 accesses the distributed ledger network 4 via the communication unit 24 to obtain control information from the token related to the above-mentioned "access information to Token" managed by the distributed ledger.
- the chunk identifier is acquired from the control information, and the chunk identifier is returned to the access function unit 22 (S144).
- the access function unit 22 returns the identifier of this chunk to the file utilization unit 21 (S145).
- the chunk identifier of the chunk of the updated file, which is the processing target, is stored and managed in the file management DB 21a.
- the file utilization unit 21 acquires the chunk identifier of the chunk of the updated file to be processed from the file management DB 21a, and uses this chunk identifier and the chunk identifier described in the control information returned in S145. Are compared, and it is confirmed (verified) that they match (S146).
- the file utilization unit 21 restores the file to be processed to the original folder and then processes the file.
- the chunk of the updated file stored in this folder is identified, the chunk identifier of this chunk is obtained from the file management DB 21a, and this chunk identifier is compared with the chunk identifier returned in S145. Confirm (verify) that these match.
- the file header or each chunk contains access information to the Token, so that the Token is set for each file or chunk. It is possible to verify the validity of a file or chunk even if it is disjointed.
- the pre-transmission verification process means that when the user terminal 3 requests the acquisition of a file or chunk held in the storage of the file holder terminal 2, the file corresponding to the user terminal 3 is used in response to the request. This is a process that verifies whether or not transmission is possible.
- the token managed on the distributed ledger network 4 has an identifier such as a file held by the file holder terminal 2 and a use permitted to acquire this file or the like.
- the user identifier which is the identifier of the person, is managed.
- FIG. 12 is a diagram showing a sequence for explaining an example of the file association verification process for the normal storage.
- the access function unit 32 of the user terminal 3 transmits a file acquisition request to the file owner terminal 2 to the file owner terminal 2 via the communication unit 34 according to the operation by the user.
- This request includes at least the file identifier of the file to be requested and the user identifier given to the user of the user terminal 3.
- the file usage unit 21 of the file holder terminal 2 receives a file acquisition request from the user via the communication unit 24 (S51).
- the file utilization unit 21 of the file holder terminal 2 identifies a file specified to be acquired in the request received in S51 from the file stored in the file management DB 21a, and describes the file in the file header of this file.
- the "access information to the Token" is acquired (S52), and the access function unit 22 is instructed to acquire the user identifier using this access information (S53).
- the access function unit 22 instructs the node function unit 23 to acquire the control information from the token (S54).
- the file utilization unit 21 is stored in the file management DB 21a and is archived or compressed. Access function to restore the file to the original folder, acquire the access information file stored in this folder, and use the "access information to Token" recorded in this access information file to acquire the user identifier. Instruct unit 22.
- the node function unit 23 acquires control information from the token managed by the distributed ledger network 4, acquires a user identifier from the control information, and transfers this user identifier to the access function unit 22. Return (S55).
- the access function unit 22 returns this user identifier to the file user unit 21 (S56).
- the control information of the plurality of Tokens is acquired.
- the file user unit 21 compares the user identifier returned in S56 with the user identifier included in the request from the user terminal 3, and these identifiers match, that is, the use included in the request. It is confirmed (verified) that the person identifier is a request from a user who is permitted to acquire the retained file (S57).
- the file user unit 21 transmits the file specified by the request to the user terminal 3 via the communication unit 24.
- the access function unit 32 of the user terminal 3 acquires the transmitted file via the communication unit 34 (S58).
- FIG. 12 is a diagram showing a sequence for explaining an example of the file pre-transmission verification process for the storage in which the file is DAG-ized.
- the access function unit 32 of the user terminal 3 transmits a chunk acquisition request to the file owner terminal 2 to the file owner terminal 2 via the communication unit 34 according to the operation by the user.
- This request includes at least the chunk identifier of the chunk of the file to be requested and the user identifier given to the user of the user terminal 3.
- the file usage unit 21 of the file holder terminal 2 receives a request for chunk acquisition from the user via the communication unit 24 (S151).
- the file utilization unit 21 identifies the chunk specified to be acquired in the request received in S51 from the chunk of the file stored in the file management DB 21a, and the "access information to Token" described in this chunk. (S152), and instructing the access function unit 22 to acquire the user identifier using this access information (S153). In response to this instruction, the access function unit 22 instructs the node function unit 23 to acquire the control information from the token (S154).
- the file utilization unit 21 stores the archive in the file management DB 21a.
- the file management DB 21a identify the chunk specified to be acquired in the request received in S151, and access information stored in the folder together with this chunk.
- the "access information to the Token" recorded in the file is acquired, and the access function unit 22 is instructed to acquire the user identifier using this access information.
- the node function unit 23 acquires control information from the token managed by the distributed ledger network 4, acquires a user identifier from the control information, and transfers this user identifier to the access function unit 22. Return it (S155).
- the access function unit 22 returns this user identifier to the file user unit 21 (S156).
- the control information of the plurality of Tokens is acquired.
- the file user unit 21 compares the user identifier returned in S56 with the user identifier included in the request from the user terminal 3, and these identifiers match, that is, are included in the request. It is confirmed (verified) that the user identifier is a request from a user who is permitted to acquire the retained file (S157).
- the file user unit 21 transmits the chunk specified in the request to the user terminal 3 via the communication unit 24.
- the access function unit 32 of the user terminal 3 acquires the transmitted chunk via the communication unit 34 (S158).
- the access information to the Token is displayed in the file header or each chunk regardless of whether the state of the requested data is a normal file state or a DAG-ized file state. Since it is included, it is possible to control sharing of files or chunks even if the Tokens are different for each file or chunk.
- the file to be processed is a file that includes the access information file and is archived or compressed, in these (2) and (3), from the chunk to the fragment of the file body and the access information file in the file. May be obtained and it may be confirmed that all access information files obtained from all chunks are the same.
- the file to be processed includes the access information to the token on the distributed ledger, and the identifier of the file is included in the token. Therefore, the management system is managed by the distributed ledger. You can refer to the information to be created from the file.
- FIG. 14 is a block diagram showing an example of the hardware configuration of the file registrant terminal according to the embodiment of the present invention.
- the file registrant terminal 1 is configured by, for example, a server computer or a personal computer, and is a hardware processor 111 such as a CPU (Central Processing Unit). Has. Then, the program memory 111B, the data memory 112, the input / output interface 113, and the communication interface 114 are connected to the hardware processor 111 via the bus 120. .. The same applies to the file holder terminal 2 and the user terminal 3.
- a hardware processor 111 such as a CPU (Central Processing Unit).
- the program memory 111B, the data memory 112, the input / output interface 113, and the communication interface 114 are connected to the hardware processor 111 via the bus 120. ..
- the communication interface 114 includes, for example, one or more wireless communication interface units, and enables information to be transmitted / received to / from the communication network NW.
- the wireless interface an interface adopting a low power wireless data communication standard such as a wireless LAN (Local Area Network) can be used.
- An input device (device) 130 and an output device 140 for an operator (operator) attached to the file registrant terminal 1 are connected to the input / output interface 113.
- the input / output interface 113 captures operation data input by an operator through an input device 130 such as a keyboard, touch panel, touchpad, mouse, etc., and outputs data as liquid crystal or organic.
- a process of outputting to an output device 140 including a display device using an EL (organic electro-luminescence) or the like and displaying the device is performed.
- a device built in the file registrant terminal 1 may be used, and another information terminal capable of communicating with the file registrant terminal 1 via the communication network NW. Input and output devices of may be used.
- the program memory 111B is a non-volatile memory such as an HDD (Hard Disk Drive) or SSD (Solid State Drive) that can be written and read at any time as a non-temporary tangible storage medium, and a ROM (Read Only Memory). It is used in combination with non-volatile memory such as, and stores programs necessary for executing various control processes according to one embodiment.
- HDD Hard Disk Drive
- SSD Solid State Drive
- ROM Read Only Memory
- the data memory 112 is used as a tangible storage medium, for example, in combination with the above-mentioned non-volatile memory and a volatile memory such as RAM (RandomAccessMemory), and various processes are performed. It is used to store various data acquired and created in the process.
- RAM RandomAccessMemory
- the file registrant terminal 1 has a file utilization unit 11, an access function unit 12, a node function unit 13, and a communication unit 14 shown in FIG. 3 as processing function units by software. Can be configured as a data processing device with.
- the various databases shown in FIG. 3 can be configured using the data memory 112 shown in FIG.
- the above various databases are not indispensable in the file registrant terminal 1, for example, an external storage medium such as a USB (Universal Serial Bus) memory, or a database server located in the cloud. ) Etc. may be provided in a storage device.
- the processing function units in each of the file utilization unit 11, the access function unit 12, the node function unit 13, and the communication unit 14 shown in FIG. 3 all use the program stored in the program memory 111B as the hardware processor. It can be realized by reading and executing by 111. It should be noted that some or all of these processing functional units may be realized by other various formats including integrated circuits such as integrated circuits (ASICs) for specific applications or FPGAs (Field-Programmable Gate Arrays).
- ASICs integrated circuits
- FPGAs Field-Programmable Gate Arrays
- the method described in each embodiment is, for example, a magnetic disk (floppy disk (registered trademark) disk (Floppy disk), hard disk (hard disk)) as a program (software means) that can be executed by a computer (computer).
- Etc. stored in recording media such as optical discs (CD-ROM, DVD, MO, etc.), semiconductor memory (ROM, RAM, Flash memory, etc.), and transmitted and distributed by communication media.
- the program stored on the medium side also includes a setting program for configuring the software means (including not only the execution program but also the table and the data structure) to be executed by the computer in the computer.
- a computer that realizes this device reads a program recorded on a recording medium, constructs software means by a setting program in some cases, and executes the above-mentioned processing by controlling the operation by the software means.
- the recording medium referred to in the present specification is not limited to distribution, and includes storage media such as magnetic disks and semiconductor memories provided in devices connected inside a computer or via a network.
- the present invention is not limited to the above embodiment, and can be variously modified at the implementation stage without departing from the gist thereof.
- each embodiment may be carried out in combination as appropriate, in which case the combined effect can be obtained.
- the above-described embodiment includes various inventions, and various inventions can be extracted by a combination selected from a plurality of disclosed constituent requirements. For example, even if some constituent elements are deleted from all the constituent elements shown in the embodiment, if the problem can be solved and the effect is obtained, the configuration in which the constituent elements are deleted can be extracted as an invention.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Health & Medical Sciences (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- General Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Computing Systems (AREA)
Abstract
Description
図1および図2は、本発明の一実施形態に係る管理システムの適用例を示す図である。図1では、本発明の一実施形態に係る管理システムに係るネットワーク(network)全体構成が示される。
図1に示されるように、本発明の一実施形態に係る管理システム100では、ファイル登録者端末1、ファイル保有者端末2、および利用者端末3がネットワークを介して接続可能で、各端末が相互に通信可能なシステムである。
図2に示される例では、本発明の一実施形態に係る管理システム100は、ファイル登録者端末1、ファイル保有者端末2、および利用者端末3を含み、各端末が相互に通信可能なシステムである。
ファイル登録者端末1と、ファイル保有者端末2と、利用者端末3は、分散台帳ネットワーク4へのアクセス機能を有し、各アカウント(account)に紐付けられる秘密鍵が利用者、ファイル登録者、およびファイル保有者の管理下にある。秘密鍵が保存される場所は特に指定されない。
図3に示されるように、ファイル登録者端末1は、ファイル利用部11、アクセス機能部12、ノード機能部13、および通信部14を有する。
ファイル利用部11は、ファイル管理DB(データベース)11aを有し、アクセス機能部12は、鍵管理DB12aを有し、ノード機能部13は、ネットワーク(NW)維持・識別用情報DB13aを有する。本実施形態での各種データベースはストレージとも称される。
通信部14は、外部との通信を担う。
図4に示されるように、ファイル保有者端末2は、ファイル利用部21、アクセス機能部22、ノード機能部23、および通信部24を有する。
ファイル利用部21は、ファイル管理DB21aを有し、アクセス機能部22は、鍵管理DB22aを有し、ノード機能部23は、ネットワーク(NW)維持・識別用情報DB23aを有する。
アクセス機能部22は、上記のアクセス機能部12と同様の処理を行ない、アクセスにおいて用いられる鍵の情報を鍵管理DB22aに格納する。
ノード機能部23は、上記のノード機能を実行し、上記のネットワーク維持および識別用の情報をネットワーク(NW)維持・識別用情報DB23aに格納する。
通信部24は、外部との通信を担う。
図5に示されるように、利用者端末3は、ファイル利用部31、アクセス機能部32、ノード機能部33、および通信部34を有する。
ファイル利用部31は、ファイル管理DB31aを有し、アクセス機能部32は、鍵管理DB32aを有し、ノード機能部33は、ネットワーク(NW)維持・識別用情報DB33aを有する。
アクセス機能部32は、上記のアクセス機能部12と同様の処理を行ない、アクセスにおいて用いられる鍵の情報を鍵管理DB32aに格納する。
ノード機能部33は、上記のノード機能を実行し、上記のネットワーク維持および識別用の情報をネットワーク(NW)維持・識別用情報DB33aに格納する。
通信部34は、外部との通信を担う。
図6に示された例では、分散台帳では、トークン(token)CAおよびトークンCA´が管理され、それぞれのトークンにおいてファイル識別子であるファイルハッシュFAが管理される。
本実施形態では、各ファイルのヘッダ(header)にトークンCAへのアクセス情報が埋め込まれる。
本実施形態では、ファイルのID(ハッシュから作られる識別子)がトークンに記録されることで、正しいトークンとファイルとの関係が確認され得る。
本実施形態では、チャンクのID(ハッシュから作られる識別子)がトークンに記録されることで、トークンとチャンクとの正しい関係が確認され得る。
次に、本実施形態に係る管理システムでの、通常ストレージへのファイルの登録処理について説明する。この登録処理は、処理対象のファイルに係る識別子が分散台帳ネットワーク上のトークンに登録される処理である。本実施形態では、各端末で用いられるストレージは、通常のストレージと、ファイルがDAG化されるストレージとに区分される。通常のストレージは、ファイルがDAG化されないストレージである。
(1) ファイル登録者端末1のファイル利用部11は、ファイル管理DB11aに記憶される、処理対象であるファイルに係るトークンである、分散台帳へのToken生成をアクセス機能部12に指示する(S11)。この指示を受けて、ファイル登録者端末1のアクセス機能部12は、分散台帳へのToken生成処理を行なう(S12)。
アクセス機能部12は、この作成された「Tokenへのアクセス情報」をファイル利用部11に返却する(S13)。
この結果を受けて、アクセス機能部12は、Tokenの更新完了通知をファイル利用部11に通知する(S17)。
次に、本実施形態に係る管理システムでの、ファイルがDAG化されるストレージへのファイルの登録処理について説明する。図9は、ファイルがDAG化されるストレージに対するファイルの登録処理の一例を説明するシーケンスを示す図である。
(1) まず、通常ストレージに対するファイルの登録処理と同様に、S11で説明したように、分散台帳へのToken生成がアクセス機能部12に指示される。次に、S12で説明したように、分散台帳へのToken生成処理が行なわれる。
次に、S13で説明したように、作成された「Tokenへのアクセス情報」がファイル利用部11に返却される。
(3) ファイル利用部11は、ファイルのヘッダを取り除き、残りの部分を仮チャンクに分割する(S112)。
(4) ファイル利用部11は、ファイルのヘッダを各仮チャンクに追加することで、仮チャンクをアップデート(update)する(S113)。
(2a) ファイル利用部11は、S13で返却された「Tokenへのアクセス情報」をアクセス情報ファイルに記録し、そして、ファイル管理DB11aに記憶される、処理対象のファイルとアクセス情報ファイルとを同じフォルダに格納し、このフォルダをアーカイブまたは圧縮することでファイルを作成する。
(4a) ファイル利用部11は、上記フォルダに格納されるアクセス情報ファイルに記録された、Tokenへのアクセス情報を各仮チャンクに追加することで、仮チャンクをアップデートする(S113)。
(5) (4)または(4a)の後、ファイル利用部11は、仮チャンクをもとに、DAG化されたファイルを作成し、このDAG化されたファイルを形成する各チャンクの識別子を生成する(S114)。
上記(2)~(5)では、ファイル利用部11は、S13で返却された「Tokenへのアクセス情報」をアクセス情報ファイルに記録し、各仮チャンクの各々について、当該仮チャンクと上記アクセス情報ファイルとを同じフォルダに格納し、このフォルダがアーカイブまたは圧縮されたファイルを生成し、このファイルをもとに、DAG化されたファイルを作成し、このDAG化されたファイルを形成する各チャンクの識別子を生成してもよい。
この結果を受けて、アクセス機能部12は、Tokenの更新完了通知をファイル利用部11に通知する(S117)。
一方で、本実施形態では、上記のように、ファイルがDAG化されたファイルに変換される際のチャンクへの分割において、少なくともTokenへのアクセス情報を含むヘッダが各チャンクに追加される。
次に、本実施形態に係る管理システムでの、通常ストレージに対するファイルの紐付け検証処理について説明する。この紐付け検証処理は、更新されたファイルに係る識別子と、当該ファイルの更新前に作成されて分散台帳ネットワークで管理される、更新前のファイルに係る識別子とが一致するか否かが確認されることにより、分散台帳ネットワーク4で管理されるトークンと、ファイル保有者端末2で管理される、トークンへのアクセス情報を有するファイルとの紐付けが検証される処理である。図10は、通常ストレージに対するファイルの紐付け検証処理の一例を説明するシーケンスを示す図である。
この指示を受けて、ノード機能部23は、通信部24を介して分散台帳ネットワーク4にアクセスすることで、分散台帳で管理される、上記「Tokenへのアクセス情報」に係るトークンから制御情報を取得して、当該制御情報からファイル識別子を取得し、このファイル識別子をアクセス機能部22に返却する(S44)。アクセス機能部22は、このファイル識別子をファイル利用部21に返却する(S45)。
次に、本実施形態に係る管理システムでの、ファイルがDAG化されるストレージに対するファイルの紐付け検証処理について説明する。図11は、ファイルがDAG化されるストレージに対するファイルの紐付け検証処理の一例を説明するシーケンスを示す図である。
次に、本実施形態に係る管理システムでの、通常ストレージに対するファイルの送信前検証処理について説明する。
送信前検証処理とは、ファイル保有者端末2のストレージで保有されるファイルまたはチャンクの取得が利用者端末3からリクエストされた場合に、このリクエストに応じて利用者端末3に該当のファイルなどの送信の可否が検証される処理である。
(1) まず、利用者端末3のアクセス機能部32は、利用者による操作に従って、ファイル保有者端末2へのファイル取得のリクエストを通信部34を介してファイル保有者端末2に送信する。このリクエストには、少なくとも、リクエスト対象のファイルのファイル識別子、および利用者端末3のユーザに付与された利用者識別子を含む。ファイル保有者端末2のファイル利用部21は、利用者からファイル取得のリクエストを通信部24を介して受信する(S51)。
次に、本実施形態に係る管理システムでの、ファイルがDAG化されるストレージに対するファイルの送信前検証処理について説明する。図12は、ファイルがDAG化されるストレージに対するファイルの送信前検証処理の一例を説明するシーケンスを示す図である。
ファイルがDAG化されるストレージから通常のファイルが取得される場合、DAG形式のファイルから通常のファイルへの変換が以下の処理によりなされる。この変換は、利用者端末3での利用前、またはファイル保有者端末2から利用者端末3への送信前になされる。
(2) チャンクからファイル本体の断片とファイルヘッダとが取得される。
(3) 全てのチャンクから取得された全てのファイルヘッダが同じであることが確認される。
(5) また、必要に応じて、上記の<ファイルの紐付け検証:通常ストレージ>の処理が実行される。
2…ファイル保有者端末
3…利用者端末
4…分散台帳ネットワーク
11,21,31…ファイル利用部
12,22,32…アクセス機能部
13,23,33…ノード機能部
14,24,34…通信部
100…管理システム
Claims (8)
- 分散台帳ネットワークに接続可能な登録者端末であって、
前記分散台帳ネットワークへのトークンの生成に関するトランザクションを生成し、前記トランザクションを前記分散台帳ネットワークに送信することで前記分散台帳ネットワークに前記トークンを生成するトークン生成部と、
処理対象のファイルに前記トークンへのアクセス情報が設定された情報を生成し、前記処理対象のファイルの識別子を生成し、
前記トークンへの前記識別子の登録に関するトランザクションを生成し、このトランザクションを前記分散台帳ネットワークに送信することで前記トークンに前記識別子を登録する登録部と、
を備える登録者端末。 - 前記登録部は、
前記処理対象のファイルに前記トークンへのアクセス情報が設定された情報を生成する情報生成部と、
前記処理対象のファイルからファイルヘッダを取り除き、各仮チャンクに分割するファイル分割部と、
前記ファイルヘッダを仮チャンクのそれぞれに追加する追加部と、
各仮チャンクを用いて有向非巡回グラフ化されたファイルを作成し、前記トークンへの、前記作成されたファイルを構成する前記仮チャンクの識別子を作成し、この識別子の登録に関するトランザクションを生成し、このトランザクションを前記分散台帳ネットワークに送信することで前記トークンに前記識別子を登録する識別子登録部と、
を含む、
請求項1に記載の登録者端末。 - 処理対象のファイルの識別子を含むトークンが保持される分散台帳ネットワークに接続可能なファイル保有者端末であって、
前記処理対象のファイルには、前記トークンへのアクセス情報が記載され、
前記処理対象のファイルに記載された、前記トークンへのアクセス情報を用いて、前記トークンからファイル識別子を取得する取得部と、
前記処理対象のファイルのファイル識別子と、前記取得部により取得されたファイル識別子とが一致することを判定する判定部と、
を備える保有者端末。 - 前記取得部は、
前記処理対象のファイルのチャンクに記載された、前記トークンへのアクセス情報を用いて、前記トークンから前記識別子を取得し、
前記判定部は、
前記処理対象のファイルのチャンクの識別子と、前記取得部により取得された識別子とが一致することを判定する、
請求項3に記載の保有者端末。 - 記憶装置に記憶されるファイルの正当な利用者の識別子である利用者識別子を含むトークンが保持される分散台帳ネットワークに接続可能であるファイル保有者端末であって、
前記記憶装置に記憶されるファイルには、前記トークンへのアクセス情報が記載され、
前記記憶装置に記憶されるファイルの取得に関するリクエストであって、リクエスト元の利用者の識別子を含むリクエストに応じて、前記記憶装置に記憶されるファイルに記載される前記トークンへのアクセス情報を用いて、前記トークンから前記利用者識別子を取得する取得部と、
前記リクエストに含まれる識別子と前記取得部により取得された利用者識別子とが一致する場合に、前記記憶装置に記憶されるファイルを前記リクエスト元に送信する送信部と、
を備えるファイル保有者端末。 - 前記記憶装置に記憶されるファイルのチャンクの正当な利用者の識別子である利用者識別子を含むトークンが保持される分散台帳ネットワークに接続可能であり、
前記記憶装置に記憶されるチャンクには、前記トークンへのアクセス情報が記載され、
前記取得部は、
前記記憶装置に記憶されるチャンクの取得に関するリクエストであって、リクエスト元の利用者の識別子を含むリクエストに応じて、前記記憶装置に記憶されるチャンクに記載される前記トークンへのアクセス情報を用いて、前記トークンから前記利用者識別子を取得し、
前記送信部は、
前記リクエストに含まれる識別子と前記取得部により取得された利用者識別子とが一致する場合に、前記記憶装置に記憶されるチャンクを前記リクエスト元に送信する、
請求項5に記載の保有者端末。 - 分散台帳ネットワークに接続可能な登録者端末により行なわれる方法であって、
前記分散台帳ネットワークへのトークンの生成に関するトランザクションを生成し、前記トランザクションを前記分散台帳ネットワークに送信することで前記分散台帳ネットワークに前記トークンを生成することと、
処理対象のファイルに前記トークンへのアクセス情報が設定された情報を生成し、前記処理対象のファイルの識別子を生成し、前記トークンへの前記識別子の登録に関するトランザクションを生成し、このトランザクションを前記分散台帳ネットワークに送信することで前記トークンに前記識別子を登録することと、
を備える登録方法。 - 請求項1もしくは2に記載の登録者端末の前記各部、または請求項3乃至6のいずれか1項に記載に保有者端末の前記各部としてプロセッサを機能させるプログラム。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2020/038779 WO2022079831A1 (ja) | 2020-10-14 | 2020-10-14 | 登録者端末、保有者端末、方法およびプログラム |
JP2022556752A JP7452690B2 (ja) | 2020-10-14 | 2020-10-14 | 登録者端末、保有者端末、方法およびプログラム |
US18/031,520 US20230412385A1 (en) | 2020-10-14 | 2020-10-14 | Registration terminal, holder terminal, method, and program |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2020/038779 WO2022079831A1 (ja) | 2020-10-14 | 2020-10-14 | 登録者端末、保有者端末、方法およびプログラム |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022079831A1 true WO2022079831A1 (ja) | 2022-04-21 |
Family
ID=81208952
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2020/038779 WO2022079831A1 (ja) | 2020-10-14 | 2020-10-14 | 登録者端末、保有者端末、方法およびプログラム |
Country Status (3)
Country | Link |
---|---|
US (1) | US20230412385A1 (ja) |
JP (1) | JP7452690B2 (ja) |
WO (1) | WO2022079831A1 (ja) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11954094B2 (en) * | 2021-08-06 | 2024-04-09 | Salesforce, Inc. | Database system public trust ledger architecture |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019004118A1 (ja) * | 2017-06-28 | 2019-01-03 | 特定非営利活動法人サイバー・キャンパス・コンソーシアムTies | ブロックチェーンにおけるコンテンツコントラクトならびにそれを用いるコンテンツの管理システムおよびコンテンツの提供方法 |
WO2020080537A1 (ja) * | 2018-10-18 | 2020-04-23 | スタートバーン株式会社 | 取扱管理装置 |
JP2020144586A (ja) * | 2019-03-06 | 2020-09-10 | 日本電信電話株式会社 | 管理者端末、参加者端末、権利者端末、利用者端末、コンテンツ利用システム、管理者プログラム、参加者プログラム、権利者プログラム、利用者プログラムおよびステートデータのデータ構造 |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11038672B2 (en) | 2018-06-01 | 2021-06-15 | Duality Technologies, Inc. | Secure and distributed management of a proxy re-encryption key ledger |
-
2020
- 2020-10-14 WO PCT/JP2020/038779 patent/WO2022079831A1/ja active Application Filing
- 2020-10-14 JP JP2022556752A patent/JP7452690B2/ja active Active
- 2020-10-14 US US18/031,520 patent/US20230412385A1/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019004118A1 (ja) * | 2017-06-28 | 2019-01-03 | 特定非営利活動法人サイバー・キャンパス・コンソーシアムTies | ブロックチェーンにおけるコンテンツコントラクトならびにそれを用いるコンテンツの管理システムおよびコンテンツの提供方法 |
WO2020080537A1 (ja) * | 2018-10-18 | 2020-04-23 | スタートバーン株式会社 | 取扱管理装置 |
JP2020144586A (ja) * | 2019-03-06 | 2020-09-10 | 日本電信電話株式会社 | 管理者端末、参加者端末、権利者端末、利用者端末、コンテンツ利用システム、管理者プログラム、参加者プログラム、権利者プログラム、利用者プログラムおよびステートデータのデータ構造 |
Also Published As
Publication number | Publication date |
---|---|
US20230412385A1 (en) | 2023-12-21 |
JPWO2022079831A1 (ja) | 2022-04-21 |
JP7452690B2 (ja) | 2024-03-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3438903B1 (en) | Hierarchical network system, and node and program used in same | |
US20180285839A1 (en) | Providing data provenance, permissioning, compliance, and access control for data storage systems using an immutable ledger overlay network | |
JP2021506004A (ja) | 分散型ストレージ方法及び装置、コンピュータ機器及び記憶媒体 | |
US9075958B2 (en) | Use of fingerprint with an on-line or networked auction | |
WO2018154698A1 (ja) | ファイルストレージ、オブジェクトストレージ、およびストレージシステム | |
JP2017207979A (ja) | 改ざん検知システム、及び改ざん検知方法 | |
US20190372778A1 (en) | Tracking provenance of digital data | |
CN102576371A (zh) | 用于对内容进行可调分发的方法和系统 | |
CN110597885A (zh) | 信息处理方法、装置、区块链网络的节点及存储介质 | |
KR102107438B1 (ko) | 블록체인을 이용한 전자 문서 관리 장치 및 이의 동작 방법 | |
JP7053031B2 (ja) | 情報処理システム、情報処理装置、情報処理方法及び情報処理プログラム | |
WO2022079831A1 (ja) | 登録者端末、保有者端末、方法およびプログラム | |
US20230232222A1 (en) | User terminal, authentication terminal, registration terminal, management system and program | |
JP2014153583A (ja) | 署名文書の管理方法及び署名サーバ | |
JP6931005B2 (ja) | 一貫性を有する散在ストレージ・ネットワークにおけるデータの格納 | |
WO2022079830A1 (ja) | 登録者端末、保有者端末、方法およびプログラム | |
US20210182314A1 (en) | Systems and methods for on-chain / off-chain storage using a cryptographic blockchain | |
EP3357188B1 (en) | Code signing service | |
JP2023078577A (ja) | 情報処理システム、情報処理方法、及びプログラム | |
JP6944317B2 (ja) | ファイル転送システムおよびファイル転送方法 | |
US11626986B1 (en) | Method and system of rescinding access to blockchain data | |
US11880824B1 (en) | Managing digital blockchains via digital tokens, systems, methods, and apparatus | |
JP7424490B2 (ja) | 登録者端末、検証者端末、管理システムおよびプログラム | |
WO2022168192A1 (ja) | データ移行装置、データ移行方法、及び、データ移行プログラム | |
US20220103372A1 (en) | Communication apparatus and communication method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20957660 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2022556752 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18031520 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20957660 Country of ref document: EP Kind code of ref document: A1 |