Security Token Sharing for Stored Database Query Results

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for sharing query results in database systems are inefficient and insecure, as they often require re-running queries or downloading large, unsecured local copies of data.

Innovation Solution

A network-based database system uses security tokens to enable users to share query results directly, managing the lifecycle of access within the system, ensuring security and efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users download local copies of query results to share with others, then data sharing is enabled, but security is compromised and storage space is consumed

Engineering Contradiction:
Improvedata sharing capabilityVSAvoiddata security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces security tokens as intermediaries between query results and users. Instead of directly sharing large data files, users receive tokens that grant controlled access to the query results stored in the database system. The token acts as a mediator that enables data sharing while maintaining security, as it contains encrypted access information rather than the actual data.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the access control mechanism from the data itself by separating authentication credentials (tokens) from the query results. The token contains only the necessary information to access specific query results, excluding the actual large-volume data, thereby enabling secure sharing without transferring sensitive information.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If users re-run queries to share results, then data freshness is maintained, but time and computational resources are wasted

Engineering Contradiction:
Improvedata freshnessVSAvoidquery execution time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-computing query results and storing them in the database system before sharing is needed. When a user wants to share results, the query has already been executed and the results are ready, eliminating the need for re-execution. The system generates tokens that reference these pre-computed results, maintaining data freshness while avoiding redundant computation.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If large query result files are downloaded for sharing, then complete data access is provided, but network bandwidth and storage are consumed

Engineering Contradiction:
Improvedata access completenessVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The patent creates a lightweight copy (the security token) instead of copying the entire query result set. The token is a small data structure containing encrypted access credentials that references the original query results stored in the database. Users receive this minimal copy rather than the full data set, enabling complete data access through the token while consuming negligible network bandwidth and storage resources.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12563025B2Token-based secure database query result sharing
Publication Date: 2026.02.24 SNOWFLAKE INC
  • US12563025B2 patent drawing
  • US12563025B2 patent drawing
  • US12563025B2 patent drawing

AI summary

Techniques for sharing query results in a multi-tenant database system are described. The query results can be shared between users of the same account or organization in the multi-tenant network-based database system using security tokens. A first user executes a query, and the results are stored in the network-based database system. The first user can invoke a function to create a security token to provide access to the stored query results to other users in the same account. The first user can share the security token with the other users, who can directly access the stored results in the network-based database system instead of having to download local copies of the query results.