Batch Digital Signature Verification for Cloud Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional cryptographic schemes suffer from inefficiencies due to lengthy signatures, leading to increased compute overhead, latency, and network bandwidth consumption, which are exacerbated by the complexity of machine learning models and the need for secure cloud computing.

Innovation Solution

Implement a one-time digital signature scheme across multiple leaf nodes, distributing data requests and creating signed copies using instances of the scheme to reduce signature size and ensure consistent length, thereby reducing compute overhead and latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional cryptographic schemes are used with lengthy signatures, then data security is provided, but compute overhead and latency increase significantly

Engineering Contradiction:
Improvedata securityVSAvoidlatency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the digital signature verification process into batch operations. Instead of verifying each signature individually, multiple signatures are collected and verified together in a single batch operation. This segmentation of the verification process reduces the total computational overhead and latency, as the system performs one verification operation for multiple signatures rather than repeating the full verification process for each signature separately

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent merges multiple signature verification operations into a single batch verification process. By combining the verification of multiple signatures into one operation, the system reduces redundant computations and achieves lower overall latency while maintaining the same security level. The batch verification allows the system to process multiple signatures simultaneously rather than sequentially

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If conventional cryptographic schemes with lengthy signatures are implemented, then data authentication is ensured, but network bandwidth is significantly consumed

Engineering Contradiction:
Improvedata authenticationVSAvoidnetwork bandwidth
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments the signature data into batch groups that are transmitted and processed together. By organizing signatures into batches, the system reduces the overhead associated with individual signature transmissions and enables more efficient network utilization through consolidated data transfer operations

Inventive Principle:
Principle #1Segmentation

3Reliability

If individual signature verification is performed for each data portion, then data integrity is verified, but processing speed decreases

Engineering Contradiction:
Improvedata integrityVSAvoidprocessing speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent merges multiple individual signature verification operations into a single batch verification process. By combining the verification of multiple signatures into one operation, the system maintains data integrity verification for each signature while achieving significantly higher processing speeds through reduced computational overhead and more efficient resource utilization

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20260019273A1Digital signature batch verification
Publication Date: 2026.01.15 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US20260019273A1 patent drawing
  • US20260019273A1 patent drawing
  • US20260019273A1 patent drawing

AI summary

A computer-implemented method, according to one approach, includes: initializing a one-time digital signature scheme across two or more leaf nodes by: creating and sending instances of the one-time digital signature scheme to the respective leaf nodes. In response to receiving a request for data from a source, where portions of the requested data being stored across the leaf nodes, portions of the data request are distributed to the corresponding leaf nodes. Signed copies of the requested portions of data are further received from the leaf nodes. The received signed copies are formed using the instances sent to the respective leaf nodes. Moreover, the signed copies are sent to the source.