WO2023037530A1 - データ管理システム - Google Patents

データ管理システム Download PDF

Info

Publication number
WO2023037530A1
WO2023037530A1 PCT/JP2021/033437 JP2021033437W WO2023037530A1 WO 2023037530 A1 WO2023037530 A1 WO 2023037530A1 JP 2021033437 W JP2021033437 W JP 2021033437W WO 2023037530 A1 WO2023037530 A1 WO 2023037530A1
Authority
WO
WIPO (PCT)
Prior art keywords
electronic signature
data management
request message
transmits
attached
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2021/033437
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
圭太 高松
広治 房
佑 日下部
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Gve Ltd
Original Assignee
Gve Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Gve Ltd filed Critical Gve Ltd
Priority to JP2021573617A priority Critical patent/JP7085097B1/ja
Priority to MX2024003078A priority patent/MX2024003078A/es
Priority to CN202180101740.2A priority patent/CN117837125A/zh
Priority to EP21956827.6A priority patent/EP4404503A4/en
Priority to PCT/JP2021/033437 priority patent/WO2023037530A1/ja
Priority to JP2022078665A priority patent/JP2023041601A/ja
Publication of WO2023037530A1 publication Critical patent/WO2023037530A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

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/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
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/606—Protecting data by securing the transmission between two devices or processes
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/64—Protecting data integrity, e.g. using checksums, certificates or signatures
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/18—Legal services
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/26—Government or public services
    • 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/3247—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 digital signatures
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q2220/00—Business processing using cryptography

Definitions

  • the present invention relates to data management.
  • Patent Document 1 A system has been proposed for attaching and verifying electronic signatures using the public key method (see Patent Document 1).
  • An object of one embodiment of the present invention is to provide a data management system that adds and verifies electronic signatures using a private key method.
  • the present invention includes the following embodiment.
  • a data management system comprising a client device, a first electronic signature device, a data management device, a second electronic signature device, a data storage device, and a third electronic signature device, wherein the first electronic signature At least one electronic signature device out of the device, the second electronic signature device, and the third electronic signature stores an encryption key and authority in association with each other, and during processing using the encryption key, the authority
  • a data management system that is an electronic signature device that can only execute processing according to
  • FIG. 1 is a diagram showing a configuration example of a data management system according to Embodiment 1;
  • FIG. 4 is a diagram showing an operation example of the data management system according to the first embodiment;
  • FIG. 4 is a diagram showing a storage example of keys and authorities in the first electronic signature device;
  • FIG. 10 is a diagram showing a storage example of keys and authorities in the second electronic signature device;
  • FIG. 11 is a diagram showing an example of storing keys and authorities in the third electronic signature device;
  • FIG. 10 is a diagram showing a configuration example of a data management system according to Embodiment 2;
  • FIG. 1 is a diagram showing a configuration example of a data management system according to the first embodiment.
  • the data management system according to the first embodiment includes a client device, a first electronic signature device, a data management device, a second electronic signature device, a data storage device, and a third electronic signature device. and a data management system. Each device will be described below.
  • a client device is a device that transmits various request messages. Examples of client devices include laptop computers, smart phones, tablet computers, and the like.
  • An example of the request message includes various data such as packets and signals.
  • a first request message and a second request message which will be described later, are examples of request messages.
  • the first request message is a message requesting the data storage device to perform a predetermined process
  • the second request message is a message requesting the data management device to perform a predetermined process.
  • the client device executes predetermined processing based on the first response message and/or the second response message.
  • An example of predetermined processing based on the first response message includes display of acquired data, display of data registration results, and processing of confirming them.
  • Examples of predetermined processing based on the second response message include processing to display the reasons for refusal of the processing of the first request and the second request, processing to confirm this (only when the processing is rejected by the data management device or data storage device), message Includes sending and receiving histories.
  • the data management device is a device that executes a predetermined process based on the second request message received from the client device and transmits the second response message to the client device. Examples of predetermined processing executed by the data management device include data registration and data acquisition.
  • An example of a data management device includes a server computer and the like.
  • An example of the second response message includes a data registration response and a data acquisition response.
  • the data storage device is a device that executes a predetermined process based on a first request message received from the client device via the data management device and transmits a second response message to the client device via the data management device.
  • Examples of predetermined processing executed by the data storage device include data encryption distributed write and distributed data decryption read.
  • An example of a data storage device includes a distributed storage server (DSS).
  • An example of the first response message includes a data encryption distributed write response and a distributed data decryption read response.
  • the first electronic signature device, the second electronic signature device, and the third electronic signature device are devices that attach electronic signatures to messages such as request messages and response messages, and verify the electronic signatures attached to these messages.
  • an HSM hardware security module
  • the first electronic signature device is an electronic signature device used in the client device.
  • the second electronic signature device is an electronic signature device used in the data management device.
  • the third electronic signature device is an electronic signature device used in the data storage device.
  • the first electronic signature device may be connected to the client device via the network, connected to the client device without the network, or built into the client device. In this embodiment, it is assumed that the first electronic signature device is connected to the client device via the network.
  • the second electronic signature device may be connected to the data management device via the network, connected to the data management device without the network, or built into the data management device. . In this embodiment, it is assumed that the second electronic signature device is connected to the data management device without going through a network.
  • the third electronic signature device may be connected to the data storage device via the network, may be connected to the data storage device without the network, or may be built in the data storage device. . In this embodiment, it is assumed that the third electronic signature device is connected to the data storage device without going through the network.
  • FIG. 3A is a diagram showing a storage example of keys and authorities in the first electronic signature device.
  • FIG. 3B is a diagram showing a storage example of keys and authorities in the second electronic signature device.
  • FIG. 3C is a diagram showing a storage example of keys and authorities in the third electronic signature device.
  • at least one electronic signature device out of a first electronic signature device, a second electronic signature device, and a third electronic signature device is an electronic signature device that stores encryption keys and authorities in association with each other, and that can execute only the processes that correspond to the authorities among the processes that use the encryption keys.
  • an electronic signature device one that creates and verifies electronic signatures based on the public key method is known.
  • the public key method there is a public key and a private key, and the public key is very long (eg 2048 bits).
  • the secret key method encryption and verification are performed with a secret key (eg, 256 bits). For this reason, in the case of the private key system, a long public key need not be used, so the time required for creating/applying and verifying electronic signatures can be shortened.
  • a secret key system is adopted, a cryptographic key (secret key) must be shared among multiple electronic signature devices. Therefore, even an electronic signature device that only verifies an electronic signature created with a certain encryption key can create an electronic signature using that encryption key, which poses a security problem.
  • the first electronic signature device possesses not only the encryption key of the client device but also the encryption keys of the data management device and the data storage device.
  • the encryption key of the data management device or data storage device is only used for verifying the electronic signature. Nevertheless, the first electronic signature device can create an electronic signature using the encryption key of the data management device or data storage device. In other words, the client device can use the first electronic signature device to impersonate the data management device or the data storage device.
  • the first electronic signature device, the second electronic signature device, and the third electronic signature device adopt a secret key system, and the encryption key (private key) is shared among these electronic signature devices.
  • the encryption key private key
  • the third electronic signature device can use each of the plurality of encryption keys (private keys) only for processing according to its authority. In this way, it is possible to shorten the time required for creating/applying and verifying electronic signatures while ensuring security. For example, as shown in FIG.
  • the first electronic signature device has not only the encryption key of the client device but also the encryption key of the data management device and the data storage device. However, it is assumed that the encryption key of the client device is authorized to be assigned and verified, and that the encryption keys of other devices are authorized only to be verified. In this way, the first electronic signature device can both apply and verify the electronic signature using the encryption key of the client device, but cannot apply the electronic signature using the encryption key of another device. Validation can only be performed.
  • each of the first electronic signature device, the second electronic signature device, and the third electronic signature device stores the encryption key and authority in association with each other, and the encryption key It is assumed that the electronic signature device is capable of executing only the processing according to the authority among the processing using .
  • the number of bits of the encryption key is, for example, 128 or 256.
  • a cryptographic key is used both for applying and verifying an electronic signature.
  • the AES method or other methods can be used for attaching and verifying the electronic signature.
  • Examples of authority include “can attach and verify electronic signatures” and “can only verify electronic signatures”. “Electronic signature can be verified only in prescribed cases”, “Electronic signature can be verified at any time, but electronic signature can be attached only in prescribed cases” It includes 'can'.
  • FIG. 2 is a diagram illustrating an operation example of the data management system according to the first embodiment; An operation example of the data management system according to the first embodiment will be described below with reference to FIG. In this specification, "applying" an electronic signature is sometimes referred to as “applying" an electronic signature.
  • Step 1 First, the client device creates a first request message.
  • Step 2 the client device transmits the first request message to the first electronic signature device.
  • the first electronic signature device attaches an electronic signature to the first request message using the encryption key of the client device, and transmits the first request message with the electronic signature to the client device.
  • Step 4 the client device creates a second request message including the first request message to which the electronic signature is attached.
  • Step 5 the client device transmits a second request message to the first electronic signature device.
  • the first electronic signature device attaches an electronic signature to the second request message using the encryption key of the client device, and transmits the second request message with the electronic signature to the client device.
  • Step 7 the client device transmits a second request message with an electronic signature to the data management device.
  • Step 8 the data management device transmits the second request message with the electronic signature to the second electronic signature device.
  • Step 9 the second electronic signature device verifies the electronic signature attached to the second request message using the encryption key of the client device, and transmits the verification result to the data management device.
  • Step 10 the data management device transmits the first request message with the electronic signature to the data storage device based on the result of the verification by the second electronic signature device.
  • Step 11 the data storage device transmits the first request message to which the electronic signature is attached to the third electronic signature device.
  • Step 12 the third electronic signature device verifies the electronic signature attached to the first request message using the encryption key of the client device, and transmits the verification result to the data storage device.
  • Step 13 the data storage device executes processing according to the first request message based on the result of verification by the third electronic signature device.
  • Step 14 the data storage device creates a first response message.
  • Step 15 the data storage device transmits the first response message to the third electronic signature device.
  • the third electronic signature device attaches an electronic signature to the first response message using the encryption key of the data storage device, and transmits the electronically signed first response message to the data storage device. .
  • Step 17 the data storage device transmits a first response message with an electronic signature to the data management device.
  • Step 18 the data management device executes processing according to the second request message.
  • Step 19 the data management device creates a second response message including the electronically signed first response message.
  • Step 20 the data management device transmits a second response message to the second electronic signature device.
  • the second electronic signature device attaches an electronic signature to the second response message using the encryption key of the data management device, and transmits the electronically signed second response message to the data management device.
  • Step 22 the data management device transmits a second response message with an electronic signature to the client device.
  • Step 23 the client device transmits a second response telegram with an electronic signature to the first electronic signature device.
  • the first electronic signature device verifies the electronic signature attached to the second response message using the encryption key of the data management device, and transmits the verification result to the client device.
  • Step 25 the client device transmits the first response message to which the electronic signature is attached to the first electronic signature device.
  • the first electronic signature device verifies the electronic signature attached to the first response message using the encryption key of the data storage device, and transmits the verification result to the client device.
  • Step 27 the client device executes predetermined processing based on the verification result.
  • a data management system that adds and verifies electronic signatures using a private key system (a system in which an encryption key is shared among a plurality of electronic signature devices).
  • a private key system a system in which an encryption key is shared among a plurality of electronic signature devices.
  • one device eg client device
  • another device eg data management device or data storage device
  • a highly secure data management system can be provided.
  • the client device, data management device, and data storage device can use only the attachment and verification of electronic signatures permitted on the data management system.
  • it is a secret key system (a system in which an encryption key is shared among a plurality of electronic signature devices), it is possible to operate strictly controlled electronic signatures.
  • FIG. 4 is a diagram illustrating a configuration example of a data management system according to the second embodiment.
  • the data management system according to the second embodiment differs from the first embodiment in that the key management device is connected to the first electronic signature device, the second electronic signature device, and the third electronic signature device. It is different from the data management system related to As described above, the first electronic signature device, the second electronic signature device, and the third electronic signature device share the encryption keys of the client device, the data management device, and the data storage device.
  • the key management device is a device that associates these shared encryption keys with different authorities and sets them for each electronic signature device.
  • the key management device may be connected to the first electronic signature device, the second electronic signature device, and the third electronic signature device via the network, or may be connected to the first electronic signature device and the second electronic signature device without the network. It may be connected to a signature device and a third electronic signature device. In this embodiment, it is assumed that the key management device is connected to the first electronic signature device, the second electronic signature device, and the third electronic signature device without going through a network.
  • Embodiments 1 and 2 An example of a data management system using Embodiments 1 and 2 will be described below.
  • the data management system according to Embodiments 1 and 2 can be used, for example, to manage vaccination certificates (eg, vaccine passports).
  • client devices include devices used by hospitals, vaccinated persons, airport customs, amusement parks, restaurants, and the like.
  • the hospital stores vaccination certificates in a data storage device using hospital-controlled equipment.
  • vaccinated persons, airport customs, amusement parks, restaurants, etc. use devices managed by each person to display the vaccination certificate stored in the data storage device on the screen of the client device. Can be viewed or printed.
  • the data management system according to Embodiments 1 and 2 can be used, for example, for real estate registration.
  • client devices include devices used by registry offices, corporations, individuals, financial institutions, and the like.
  • the Registrar uses its own equipment to store data relating to property registration in a data storage device.
  • corporations, individuals, financial institutions, etc. can display or print data related to real estate registration stored in the data storage device on the screen of the client device using devices managed by each person.
  • the data management system according to Embodiments 1 and 2 can be used, for example, for company registration.
  • the client device is used by registry offices, corporations, individuals, financial institutions, and the like.
  • a registry office uses a client device to store data relating to company registration in a data storage device.
  • a corporation, an individual, a financial institution, etc. can use a client device to display or print data related to company registration stored in the data storage device on the screen of the client device.
  • the data storage systems according to the first and second embodiments can be used to store various other types of data.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Human Resources & Organizations (AREA)
  • Tourism & Hospitality (AREA)
  • Bioethics (AREA)
  • Economics (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Marketing (AREA)
  • Computer Hardware Design (AREA)
  • General Business, Economics & Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Primary Health Care (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Educational Administration (AREA)
  • Data Mining & Analysis (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Medical Informatics (AREA)
  • Databases & Information Systems (AREA)
  • Technology Law (AREA)
  • Development Economics (AREA)
  • Storage Device Security (AREA)
PCT/JP2021/033437 2021-09-13 2021-09-13 データ管理システム Ceased WO2023037530A1 (ja)

Priority Applications (6)

Application Number Priority Date Filing Date Title
JP2021573617A JP7085097B1 (ja) 2021-09-13 2021-09-13 データ管理システム
MX2024003078A MX2024003078A (es) 2021-09-13 2021-09-13 Sistema de manejo de datos.
CN202180101740.2A CN117837125A (zh) 2021-09-13 2021-09-13 数据管理系统
EP21956827.6A EP4404503A4 (en) 2021-09-13 2021-09-13 DATA MANAGEMENT SYSTEM
PCT/JP2021/033437 WO2023037530A1 (ja) 2021-09-13 2021-09-13 データ管理システム
JP2022078665A JP2023041601A (ja) 2021-09-13 2022-05-12 データ管理システム

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2021/033437 WO2023037530A1 (ja) 2021-09-13 2021-09-13 データ管理システム

Publications (1)

Publication Number Publication Date
WO2023037530A1 true WO2023037530A1 (ja) 2023-03-16

Family

ID=82020786

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/033437 Ceased WO2023037530A1 (ja) 2021-09-13 2021-09-13 データ管理システム

Country Status (5)

Country Link
EP (1) EP4404503A4 (https=)
JP (2) JP7085097B1 (https=)
CN (1) CN117837125A (https=)
MX (1) MX2024003078A (https=)
WO (1) WO2023037530A1 (https=)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TW202439517A (zh) 2023-03-16 2024-10-01 日商東京威力科創股份有限公司 維護作業支援系統、控制方法及控制程式

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002247031A (ja) * 2001-02-16 2002-08-30 Fujitsu Ltd 電子署名方法
JP2008140298A (ja) 2006-12-05 2008-06-19 Verifirm Co Ltd 電子領収認証サーバ、電子領収発行サーバ、電子領収システム及び電子領収認証プログラム
JP2019500799A (ja) * 2015-12-23 2019-01-10 ソニー株式会社 許可アクセスのためのクライアント装置、サーバー装置及びアクセス制御システム

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3688830B2 (ja) * 1995-11-30 2005-08-31 株式会社東芝 パケット転送方法及びパケット処理装置
JP2004110693A (ja) * 2002-09-20 2004-04-08 Toshiba Solutions Corp 電子文書管理システム、電子文書管理方法およびプログラム
JP5874823B2 (ja) * 2012-05-24 2016-03-02 富士通株式会社 ネットワークシステム、ノード、および通信方法。
JP6039364B2 (ja) * 2012-10-26 2016-12-07 キヤノン株式会社 画像形成装置、サーバー装置、情報処理方法及びプログラム
JP6875576B2 (ja) * 2014-05-08 2021-05-26 パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカＰａｎａｓｏｎｉｃ Ｉｎｔｅｌｌｅｃｔｕａｌ Ｐｒｏｐｅｒｔｙ Ｃｏｒｐｏｒａｔｉｏｎ ｏｆ Ａｍｅｒｉｃａ 不正対処方法
CN105637803B (zh) * 2014-05-08 2019-10-22 松下电器（美国）知识产权公司 车载网络系统、不正常检测电子控制单元以及不正常应对方法
JP7058930B2 (ja) * 2015-11-28 2022-04-25 キヤノン株式会社 情報処理装置、情報処理装置の制御方法、プログラム、及び記憶媒体
KR102473100B1 (ko) * 2016-09-23 2022-12-01 애플 인크. 네트워크 트래픽의 보안 통신
JP6174229B1 (ja) * 2016-12-09 2017-08-02 Kddi株式会社 配信システム、データ保安装置、配信方法、及びコンピュータプログラム
JP6590906B2 (ja) * 2017-12-26 2019-10-16 キヤノン株式会社 情報処理装置、および情報処理装置の制御方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002247031A (ja) * 2001-02-16 2002-08-30 Fujitsu Ltd 電子署名方法
JP2008140298A (ja) 2006-12-05 2008-06-19 Verifirm Co Ltd 電子領収認証サーバ、電子領収発行サーバ、電子領収システム及び電子領収認証プログラム
JP2019500799A (ja) * 2015-12-23 2019-01-10 ソニー株式会社 許可アクセスのためのクライアント装置、サーバー装置及びアクセス制御システム

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4404503A4

Also Published As

Publication number Publication date
JP7085097B1 (ja) 2022-06-16
MX2024003078A (es) 2024-04-16
EP4404503A1 (en) 2024-07-24
EP4404503A4 (en) 2025-07-02
JPWO2023037530A1 (https=) 2023-03-16
JP2023041601A (ja) 2023-03-24
CN117837125A (zh) 2024-04-05

Similar Documents

Publication Publication Date Title
JP7602539B2 (ja) 量子安全ネットワーキング
US10673632B2 (en) Method for managing a trusted identity
CA2545015C (en) Portable security transaction protocol
JP2022058803A (ja) コンピュータに実装される方法、ホストコンピュータ、コンピュータ読み取り可能な媒体
JP4744785B2 (ja) セッションキー・セキュリティプロトコル
CN104798083B (zh) 用于验证访问请求的方法和系统
US20150172260A1 (en) Cloud-based key management
SE502424C2 (sv) Metod och anordning vid certifikathanteringssystem
JP2015154491A (ja) リモートアクセス、リモートデジタル署名のためのシステムおよび方法
US9356926B1 (en) Security system
US20220393882A1 (en) Secured private credential certificate
AU2020100734A4 (en) Systems and methods for secure digital file sharing and authenticating
JP5602165B2 (ja) ネットワーク通信を保護する方法および装置
JP2011082662A (ja) 通信装置及び情報処理方法及びプログラム
US20240054204A1 (en) Digital id storage and federation service model
CN106533693B (zh) 轨道车辆监控检修系统的接入方法和装置
JP6712707B2 (ja) 複数のサービスシステムを制御するサーバシステム及び方法
CN107409043B (zh) 基于中央加密的存储数据对产品的分布式处理
JP2023041601A (ja) データ管理システム
JP6760631B1 (ja) 認証リクエストシステム及び認証リクエスト方法
JP2004140636A (ja) 電子文書の署名委任システム、署名委任サーバ及び署名委任プログラム
JP2011145754A (ja) シングルサインオンシステムと方法、認証サーバ、ユーザ端末、サービスサーバ、プログラム
JP2006129143A (ja) 秘密情報送受信システム及び方法、サーバー装置及びプログラム、並びに鍵情報保持装置
JP7230293B2 (ja) 管理サーバ、管理システム、管理方法、及びプログラム
HK40102282A (zh) 数据管理系统

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2021573617

Country of ref document: JP

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21956827

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180101740.2

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 18686141

Country of ref document: US

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112024003920

Country of ref document: BR

WWE Wipo information: entry into national phase

Ref document number: 202447028139

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2021956827

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021956827

Country of ref document: EP

Effective date: 20240415

ENP Entry into the national phase

Ref document number: 112024003920

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20240228