Speculative Database Authentication Protocol

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional database authentication processes are inefficient due to delays caused by multiple back-and-forth messaging, which hinders the expedited processing of subsequent transactions.

Innovation Solution

Speculative authentication is implemented by transmitting a series of simultaneous messages, including a handshake and authentication acknowledgement, followed by immediate acknowledgement without substantial processing, allowing for expedited authentication and subsequent database transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional database authentication processes are used with multiple back-and-forth messaging, then authentication security is maintained, but processing time increases and efficiency decreases

Engineering Contradiction:
Improveauthentication processing efficiencyVSAvoidauthentication messaging exchange time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by transmitting authentication messages in advance before actual database transactions occur. The system sends a series of simultaneous messages including handshake messages and authentication acknowledgments proactively, so that when transactions need to be processed, the authentication is already complete or in progress, eliminating delays between authentication and transaction processing.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent merges multiple authentication messaging steps into a single simultaneous transmission. Instead of sending authentication messages sequentially one after another, the system combines handshake messages, authentication acknowledgments, and database messages into one bundled transmission, significantly reducing the total time spent on authentication exchanges.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If multiple back-and-forth authentication messages are exchanged, then authentication verification is thorough, but subsequent transaction processing is delayed

Engineering Contradiction:
Improveauthentication verificationVSAvoidtransaction processing speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The system performs authentication verification in advance by transmitting all necessary authentication messages before transactions are processed. The authentication acknowledgment messages are sent proactively, ensuring that when transactions arrive, the verification is already complete, allowing transactions to proceed immediately without waiting for authentication to finish.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent ensures continuous useful action by making authentication messages transmitted simultaneously and continuously rather than intermittently. The system maintains authentication verification as an ongoing process that completes in advance, creating a seamless transition from authentication to transaction processing without any idle time or delays.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS8903951B2Speculative database authentication
Publication Date: 2014.12.02 META PLATFORMS INC
  • US8903951B2 patent drawing
  • US8903951B2 patent drawing
  • US8903951B2 patent drawing

AI summary

Speculative processing of authentication messages may include transmitting a first series of simultaneous messages to a database client, the first series of simultaneous messages including a handshake message and a first authentication acknowledgement message, receiving a second series of simultaneous messages from the database client, the second series of simultaneous messages including an authentication message and a database message, and transmitting a database acknowledgment message to the database client. In some implementations, the second series of simultaneous messages is received from the database client substantially without delay after the transmission of the first series of simultaneous messages.