# US 2024/0205018 A1 · Quantum safe digital signature service

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0205018 A1
- Document ID: US20240205018A1
- Status: Published application
- Kind: A1
- Application number: 18/081,225
- Filed: 2022-12-14
- Published: 2024-06-20
- Earliest claimed: 2022-12-14
- Assignees: Sap SE
- Applicants: Sap SE
- Inventors: Anitha Naduvath; Bino Rose Philip; Anselme Tueno; Andrey Hoursanov; Tim Rausch; David Boehm; Ajitha Naduvath; Mohamed Doula
- Web page: https://patentgrep.com/patent/US20240205018A1

## CPC

- H04L 9/3247: {involving digital signatures}
- G06F 16/93: Document management systems
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Mechanisms are disclosed for decoupled integration of quantum-safe digital signatures into software applications. Electronic document content is stored, by a software application, in connection with a document store. An application programming interface (API) request is issued to a quantum-safe digital signature service. The API request comprises an identifier associated with the electronic document content and a request to generate a quantum-safe signature associated with the electronic document content. The request to generate a quantum-safe signature of the electronic document content causes the quantum-safe digital signature service to perform several steps. First, the electronic document content is retrieved from the document store. Next, a quantum-safe digital signature data structure is generated. Next, the quantum-safe digital signature data structure is stored to the document store. A signing status update is transmitted to the software application. The software application reads the signature data structure from the document store.

## Claims

### Claim 1

One or more non-transitory computer-readable media storing computer-executable instructions that, when executed by a processor, perform a method of decoupled integration of quantum-safe digital signatures into a software application, the method comprising:
storing, by the software application, in connection with a document store, electronic document content;
issuing an application programming interface (API) request to a quantum-safe digital signature service,
wherein the API request comprises an identifier associated with the electronic document content and a request to generate a quantum-safe signature associated with the electronic document content, and
wherein the request to generate a quantum-safe signature of the electronic document content causes the quantum-safe digital signature service to:
retrieve the electronic document content from the document store;
generate a quantum-safe digital signature data structure;
store the quantum-safe digital signature data structure to the document store; and
transmit a signing status update to the software application; and
reading, by the software application, the signature data structure from the document store.

### Claim 2 (depends on 1)

The non-transitory computer-readable media of claim 1, wherein the API request is made directly to the quantum-safe digital signature service.

### Claim 3 (depends on 1)

The non-transitory computer-readable media of claim 1, wherein the API request is made indirectly to the quantum-safe digital signature service via the document store by setting an attribute associated with the electronic document content.

### Claim 4 (depends on 1)

The non-transitory computer-readable media of claim 1, wherein the electronic document content comprises an electronic file that is persisted in connection with persistent storage associated with the document store.

### Claim 5 (depends on 1)

The non-transitory computer-readable media of claim 1, wherein the document store is a document management system.

### Claim 6 (depends on 1)

The non-transitory computer-readable media of claim 1, wherein the API request is a REST API request.

### Claim 7 (depends on 1)

The non-transitory computer-readable media of claim 1, wherein the signature data structure comprises an electronic file containing the quantum-safe digital signature.

### Claim 8

A method for decoupled integration of quantum-safe digital signatures into a software application, the method comprising:
storing, by the software application, in connection with a document store, electronic document content;
issuing an application programming interface (API) request to a quantum-safe digital signature service,
wherein the API request comprises an identifier associated with the electronic document content and a request to generate a quantum-safe signature associated with the electronic document content, and
wherein the request to generate a quantum-safe signature of the electronic document content causes the quantum-safe digital signature service to:
retrieve the electronic document content from the document store;
generate a quantum-safe digital signature data structure;
store the quantum-safe digital signature data structure to the document store; and
transmit a signing status update to the software application; and
causing the application to read the signature data structure from the document store.

### Claim 9 (depends on 8)

The method of claim 8, wherein the API request is made directly to the quantum-safe digital signature service.

### Claim 10 (depends on 9)

The method of claim 9, wherein the API request is made indirectly to the quantum-safe digital signature service via the document store by setting an attribute associated with the electronic document content.

### Claim 11 (depends on 10)

The method of claim 10, wherein the API request is made indirectly to the quantum-safe digital signature service via the document store by setting an attribute associated with the electronic document content.

### Claim 12 (depends on 11)

The method of claim 11, wherein the document store is a document management system.

### Claim 13 (depends on 10)

The method of claim 10, wherein the API request is a REST API request.

### Claim 14 (depends on 8)

The method of claim 8, wherein the signature data structure comprises an electronic file containing the quantum-safe digital signature.

### Claim 15

A system for decoupled integration of quantum-safe digital signatures into a software application, the system comprising:
at least one processor;
and at least one non-transitory memory storing computer executable instructions that when executed by the at least one processor cause the system to carry out actions comprising:
storing, by the software application, in connection with a document store, electronic document content;
issuing an application programming interface (API) request to a quantum-safe digital signature service,
wherein the API request comprises an identifier associated with the electronic document content and a request to generate a quantum-safe signature associated with the electronic document content, and
wherein the request to generate a quantum-safe signature of the electronic document content causes the quantum-safe digital signature service to:
retrieve the electronic document content from the document store;
generate a quantum-safe digital signature data structure;
store the quantum-safe digital signature data structure to the document store; and
transmit a signing status update to the software application; and
causing the software application to read the signature data structure from the document store.

### Claim 16 (depends on 15)

The system of claim 15, wherein the API request is made directly to the quantum-safe digital signature service.

### Claim 17 (depends on 15)

The system of claim 15, wherein the API request is made indirectly to the quantum-safe digital signature service via the document store by setting an attribute associated with the electronic document content.

### Claim 18 (depends on 17)

The system of claim 17, wherein the API request is made indirectly to the quantum-safe digital signature service via the document store by setting an attribute associated with the electronic document content.

### Claim 19 (depends on 18)

The system of claim 18, wherein the document store is a document management system.

### Claim 20 (depends on 17)

The system of claim 17, wherein the API request is a REST API request.
