Key-Based DLL Service for Local Data Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional dynamic linked library (DLL) applications face issues with increased network traffic and security breaches due to the transmission of user data over networks while accessing web services, which complicates system management and security.

Innovation Solution

The system employs a key-based authentication mechanism using shared memory spaces to maintain user data locally, transmitting only a byte string that includes a functionality key for authentication, thereby reducing network traffic and enhancing security by keeping user data encrypted or in clear text, allowing for dynamic updates to DLL services without altering the API definition.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If user data is transmitted over the network to access web services, then web service functionality is accessible, but network traffic increases and security breaches become more likely

Engineering Contradiction:
Improveweb service accessibilityVSAvoidsecurity breaches
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts user data from network transmission by implementing a DLL service that processes and manages user data locally on the client device. The service exposes functionality through a neutralized API that operates on local data, eliminating the need to transmit user data over the network while maintaining web service accessibility.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a DLL service as an intermediary layer between the user application and web services. This service neutralizes the API by implementing local data processing capabilities, acting as a mediator that prevents direct network transmission of user data while still enabling web service functionality through local operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If user data is transmitted over the network, then web service functionality is accessible, but network traffic increases

Engineering Contradiction:
Improveweb service accessibilityVSAvoidnetwork traffic
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent extracts user data from network transmission by implementing a DLL service that processes and manages user data locally on the client device. The service exposes functionality through a neutralized API that operates on local data, eliminating the need to transmit user data over the network while maintaining web service accessibility.

Inventive Principle:
Principle #2Taking out (Extraction)

3Ease of operation

If traditional DLL applications transmit user data over the network, then web services can be accessed, but system security is compromised

Engineering Contradiction:
Improveweb service accessVSAvoidsystem security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces a DLL service as an intermediary layer between the user application and web services. This service neutralizes the API by implementing local data processing capabilities, acting as a mediator that prevents direct network transmission of user data while still enabling web service functionality through local operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11546315B2Authentication key-based DLL service
Publication Date: 2023.01.03 HEWLETT PACKARD ENTERPRISE DEV LP
  • US11546315B2 patent drawing
  • US11546315B2 patent drawing
  • US11546315B2 patent drawing

AI summary

Systems and methods are provided for implementing an authentication key-based DLL service. For example, the system can expose a list of functionalities and request format, and a byte string denotes a functionality corresponding to the API. Output is received by the user after loading a DLL library maintained by a DLL provider. The system can generate a key corresponding to the functionality and transmit the key to the user. The invocation of the functionality can be performed using the keys. The shared memory space may be used for inputs from the user and outputs of the DLL. The system can perform an action based on the authentication of the keys. During any functionality advancement, the system can notify the user to unload and reload the new DLL in order to make use of the advancements.