Autonomous Software Containers Decentralize Data Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Centralized storage of source code and databases in networked environments leads to large system resource requirements and increased security risks due to privileged data being stored at a single location, making it vulnerable to breaches.
Innovation Solution
Autonomous software modules are transmitted to local computers, hosting their own databases and employing a two-way interrogation and verification mechanism for secure communication, along with container-encrypted fingerprints and tokenization to ensure secure operations and protect against security threats.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If source code and databases are stored centrally, then data access and communication are simplified, but system resource requirements increase and security risks increase
Solution Approach 1:
The patent segments the centralized database into distributed databases located at different entities. Each entity maintains its own database locally rather than accessing a central repository, which reduces the resource burden on any single system while maintaining data accessibility through the software container architecture.
Solution Approach 2:
The software container acts as an intermediary that enables data access and communication between entities without requiring a centralized database. The container encapsulates the necessary data and functionality, allowing entities to access information through the container interface rather than directly querying a central system.
2Ease of operation
If source code and databases are stored centrally, then communication between entities is simplified, but security risks increase due to single point of vulnerability
Solution Approach 1:
The patent divides the centralized data storage into multiple distributed databases across different entities. This segmentation eliminates the single point of failure, as each entity's data is isolated in its own database, preventing a breach at one location from compromising the entire system.
Solution Approach 2:
Each entity maintains local databases with data specific to its needs, rather than relying on a central repository. This local quality approach allows each entity to implement its own security measures and access controls, improving overall system security while maintaining communication efficiency through the software container interface.
3Reliability
If autonomous software modules are deployed locally, then security is improved through data decentralization, but system complexity increases
Solution Approach 1:
The software container is designed as a universal component that can be deployed at any entity while providing the same security and data access functionality. This multi-functionality reduces system complexity by using a standardized approach across all entities rather than requiring custom solutions for each location.
Solution Approach 2:
The patent uses copying by deploying identical software container instances across multiple entities. Each container is a copy that encapsulates the necessary data and functionality, allowing secure local deployment without requiring complex custom configurations at each location.
4Reliability
If entities maintain local databases, then security is improved, but communication overhead increases
Solution Approach 1:
The software container serves as an intermediary that optimizes communication between entities with local databases. It provides a standardized interface for data access and transaction processing, reducing communication overhead by handling data exchange efficiently without requiring direct complex interactions between distributed databases.
Data Source
AI summary
An individualized software container is provided. The software container may be created by a remote entity. The software container may be located on a computer of a local entity. The software container may provide an entity separation between the local entity and at least one other entity. The software container may encompass a plurality of containers. The software container may communicate with a plurality of other software containers. The plurality of other software containers may be associated with at least one other entity. The software container may host its own database. The software container may include a plurality of security features associated with the remote entity. The software container may include a container-encrypted fingerprint (“CEF”). The CEF may enable encrypted end-to-end connection between the software container and the remote entity. The CEF may leverage fingerprinting and/or tokenization of the software container.