IP Library › Granted Patent US 12,242,656
Granted Patent B2
US 12,242,656 · App. 17/676,731 · Granted Mar 4, 2025

Seal management method and seal management apparatus

Inventors: Toshiyuki Uehara (Chiba, JP); Yoshiaki Takahashi (Tokyo, JP)
Assignee: GFS Corporation
G06F21/64G06F16/27G06F21/31G06F21/6218
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,242,656
App. No.
17/676,731
Granted
Mar 4, 2025
Kind
B2
Abstract

A seal management apparatus for managing an electronic sealing service performs the steps of receiving seal-required data to be used for the sealing service from a user terminal of a user of the sealing service, generating (a) a seal secret key for sealing the seal-required data and (b) a seal public key used for verifying the seal, in a working memory, when the seal-required data is received, registering the seal public key in a blockchain, acquiring a seal identifier that is an identifier for acquiring the seal public key registered in the blockchain from the blockchain, generating a sealed file by affixing a signature of the seal secret key to a file containing the seal-required data and the seal identifier, deleting the seal secret key from the working memory, and transmitting the seal identifier to the user terminal.

Claims (82)

1. A seal management method, wherein

a seal management apparatus for managing an electronic sealing service performs the steps of:

receiving seal-required data to be used for the sealing service from a user terminal of a user of the sealing service;

generating (a) a seal secret key for sealing the seal-required data and (b) a seal public key used for verifying the seal, in a working memory, in response to the seal-required data being received;

registering the seal public key in a blockchain;

acquiring a seal identifier that is an identifier for acquiring the seal public key registered in the blockchain from the blockchain;

generating a sealed file by affixing a signature of the seal secret key to a file containing the seal-required data and the seal identifier;

deleting the seal secret key from the working memory;

transmitting the seal identifier to the user terminal;

receiving a request for registering the sealing service from the user terminal;

generating (a) a service secret key for affixing a signature to the sealed data that has been sealed using the sealing service and (b) a service public key used for verifying the signature, in response to the request for registration being received;

registering the service public key in the blockchain;

acquiring a service identifier that is an identifier for acquiring the service public key registered in the blockchain, from the blockchain;

storing the service secret key and the service identifier in a storage;

generating a sealed file with a signature by affixing a signature to data containing the sealed file and the service identifier, using the service secret key; and

storing the sealed file with a signature in the storage in association with the seal identifier.

2. The seal management method according to claim 1 , wherein

the seal management apparatus further performs the steps of:

receiving the seal identifier from the user terminal;

acquiring the sealed file with a signature from the storage using the seal identifier; and

transmitting the sealed file with a signature to the user terminal.

3. The seal management method according to claim 2 , wherein

the seal management apparatus further performs the steps of:

receiving the seal identifier from an inspector terminal used by an inspector who inspects the sealing service;

acquiring the seal public key from the blockchain using the seal identifier;

acquiring the sealed file with a signature from the storage using the seal identifier;

verifying the signature of the seal secret key contained in the sealed file with a signature using the seal public key;

generating a report indicating a result of the verification;

acquiring the service secret key from the storage using the service identifier contained in the acquired sealed file with a signature;

generating a signed inspection report to having a signature using the service secret key; and

transmitting the signed inspection report to the inspector terminal.

4. The seal management method according to claim 3 , wherein

the seal management apparatus further performs the steps of:

receiving the seal identifier from the inspector terminal;

acquiring the sealed file with a signature from the storage using the seal identifier;

acquiring the service public key from the blockchain using the service identifier contained in the sealed file with a signature; and

transmitting the acquired service public key to the inspector terminal, wherein the inspector terminal further performs the steps of:

receiving the service public key from the seal management apparatus; and

verifying legitimacy of the signature affixed to the signed inspection report using the received service public key.

5. The seal management method according to claim 1 , wherein

the seal management apparatus further performs the step of:

generating encrypted data by encrypting another piece of data different from the seal-required data using the service secret key, wherein

the generating the sealed file with a signature generates data, obtained by affixing a signature to a file containing the sealed file, the encrypted data, and the service identifier using the service secret key, as the sealed file with a signature.

6. The seal management method according to claim 1 , wherein

the seal management apparatus further performs the step of:

generating a log file indicating that the seal secret key and the seal public key have been deleted from the working memory.

7. The seal management method according to claim 1 , wherein

the blockchain is a consortium blockchain.

8. An information processing method, wherein

a user terminal of a user of an electronic sealing service performs the steps of:

generating a hash value of seal-required data to be used for the sealing service;

generating (a) a user seal secret key for affixing a signature to a verification information containing the hash value and (b) a user public key corresponding to the user seal secret key, in a working memory;

generating signed verification information having a signature using the user seal secret key;

transmitting the signed verification information and the user public key to a seal management apparatus that manages the sealing service; and

deleting the user seal secret key from the working memory; wherein

the seal management apparatus performs the steps of:

receiving the signed verification information and the user public key from the user terminal of the user of the sealing service;

generating (a) a seal secret key for sealing the signed verification information and (b) a seal public key used for verifying the seal, in a working memory;

storing the seal public key and the user public key in association with an seal identifier in a storage;

generating sealed verification information by affixing a signature of the seal secret key to the signed verification information;

transmitting the sealed verification information and the seal identifier to the user terminal; and

deleting the seal secret key from the working memory;

receiving the seal identifier, the sealed verification information, and a hash value of the seal-required data to be verified, from the user terminal;

acquiring the seal public key and the user public key from the storage using the seal identifier;

a first verification step of verifying a signature of the seal secret key contained in the sealed verification information, using the seal public key;

a second verification step of verifying a signature of the user seal secret key contained in the sealed verification information, using the user public key;

a third verification step of verifying that a hash value of the seal-required data contained in the sealed verification information matches a hash value of seal-required data to be verified; and

transmitting the user public key to the user terminal on condition that the verification in each of the first verification step, the second verification step, and the third verification step succeeds.

9. The information processing method according to claim 8 , wherein

the user terminal performs the steps of:

generating a first common key for encrypting a file for storage to be archived, in the working memory;

generating data obtained by encrypting the file for storage with the first common key as the seal-required data;

encrypting the first common key using the user seal secret key to generate an encrypted first common key; and

deleting the first common key from the working memory.

10. The information processing method according to claim 9 , wherein

the seal management apparatus performs the steps of:

generating a second common key different from the first common key in the working memory;

encrypting information containing the sealed verification information with the second common key; and

encrypting the second common key using the seal secret key to generate an encrypted second common key, wherein

the transmitting to the user terminal transmits information including the encrypted sealed verification information, the encrypted second common key, and the seal identifier to the user terminal, wherein

the seal management apparatus further performs the step of:

deleting the second common key from the working memory.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 23, 2022
From: UEHARA, TOSHIYUKI; TAKAHASHI, YOSHIAKI
To: GFS CORPORATION
Reel/Frame 059083/0639 →
Priority Claims (1)
JP 2020-169177 · Oct 6, 2020 · national
Continuity (2)
Continuation PCTJP2021026656 · Jul 15, 2021
Related Publication 20220179999A1 · Jun 9, 2022
References Cited (12)
US 10554407B1 · Greco · 2020 [cited by examiner]
US 20170272245A1 · Norton · 2017 [cited by examiner]
US 20190253260A1 · Uehara et al. · 2019 [cited by applicant]
US 20190287105A1 · Fedorov · 2019 [cited by examiner]
US 20200127826A1 · Ebrahimi · 2020 [cited by examiner]
US 20210397678A1 · Ohashi et al. · 2021 [cited by applicant]
US 20230134095A1 · Mitch · 2023 [cited by examiner]
JP 2002116696A · 2002 [cited by applicant]
JP 2018182487A · 2018 [cited by applicant]
JP 2019164683A · 2019 [cited by applicant]
JP 2020135690A · 2020 [cited by applicant]
WO 2020085378A1 · 2020 [cited by applicant]