Electronic Transfer Directory Service for Secure File Distribution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for electronic transfers require sending voluminous repository data, leading to reduced computation efficiency, increased memory allocation, and security concerns due to the transmission of sensitive information.
Innovation Solution
A system and method that utilize non-transitory computer readable media to execute operations for verifying entities and facilitating electronic transfers by generating internal and external profiles, access tokens, and storing them in a directory, allowing for secure and efficient transfers without transmitting voluminous data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional methods transmit voluminous repository data to verify entity ownership, then entity verification can be performed, but computation efficiency is reduced and memory allocation increases
Solution Approach 1:
The patent extracts only the essential verification attributes from the voluminous repository data and encapsulates them in a compact digital signature. Instead of transmitting the entire repository dataset, the system extracts and transmits only the cryptographic signature that proves entity ownership, dramatically reducing data volume while maintaining verification reliability
Solution Approach 2:
The patent introduces a digital signature as an intermediary element between the repository data and the verification process. The digital signature acts as a mediator that proves entity ownership without requiring direct transmission or storage of the actual repository data, solving both the verification reliability and computation efficiency requirements
2Reliability
If conventional methods transmit voluminous repository data for entity verification, then entity ownership can be confirmed, but security concerns arise due to transmission of sensitive information
Solution Approach 1:
The patent extracts only the cryptographic proof of ownership from the sensitive repository data. By transmitting only the digital signature rather than the actual repository contents, the system confirms entity ownership while eliminating the security risk of exposing sensitive information during transmission
Solution Approach 2:
The patent creates and transmits a cryptographic copy (digital signature) that proves ownership without copying or transmitting the actual sensitive repository data. This cryptographic copy contains all necessary verification information while being safe to transmit across networks
3Ease of operation
If conventional systems store entity repository information in memory for processing, then electronic transfers can be performed, but memory allocation becomes inefficient
Solution Approach 1:
The patent extracts only the essential verification information into a compact digital signature format. This extracted representation requires minimal memory allocation while still enabling complete electronic transfer processing, eliminating the need to store large amounts of repository data in memory
4Ease of operation
If conventional methods transmit entity repository data between entities, then electronic transfers can be initiated, but data transmission volume increases
Solution Approach 1:
The patent extracts only the necessary verification proof from the repository data and transmits it as a digital signature. This extracted signature enables electronic transfer initiation while reducing data transmission volume from voluminous repository data to a compact cryptographic proof
Data Source
AI summary
A method for verifying entities and provide an electronic transfer between entities comprising: retrieving a first reference number and a first transmit number associated with a first entity repository; generating a first internal profile associated with the first entity; generating a first access token; generating a first external profile associated with the first entity; storing the profiles in a directory; retrieving a second identification of a second access token; identifying a second entity associated with the second external profile using the second identification; identifying a second internal profile from the plurality of internal profiles associated with the second entity; using a second reference number and a second transmit number associated with the second internal profile, identifying a current status and a history of a second entity repository associated with the second internal profile; and initiating the electronic transfer from the first entity repository to the second entity repository.


