Workspace Databases for Digital Twin Session Customization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing techniques for providing reference data to customize application sessions in digital twin software lack efficient organization, version control, adaptability, fine-grained access permissions, direct cloud access, and efficient update procedures.
Innovation Solution
The implementation of workspace databases, both file-based and cloud-based, using in-memory cloud container objects and local caching, with access managed by tokens, allows for efficient organization, versioning, and fine-grained access permissions, enabling direct access and fast updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If reference data is stored as separate files in a local file system, then direct access is possible, but organization efficiency deteriorates and version control is lost
Solution Approach 1:
The patent merges multiple separate reference data files into a unified workspace database structure. Related files (e.g., specifications, patterns, catalog information) are consolidated into a single database entity with a unique identifier, enabling efficient organization while maintaining direct access capabilities through the database interface.
Solution Approach 2:
The patent creates a virtual copy of the file system structure within the workspace database. The database stores references to actual files while providing database-level organization and control, allowing direct file access when needed while benefiting from structured database management.
2Ease of operation
If all reference data is downloaded locally for offline use, then direct access is enabled, but access speed deteriorates due to lengthy pre-downloads
Solution Approach 1:
The system performs preliminary actions by establishing a virtual connection to the cloud storage container before actual data access. The workspace database is initialized with metadata and structure in advance, allowing immediate access to reference data without requiring complete pre-download of all files. Data is cached locally as needed during the session.
Solution Approach 2:
The patent introduces a cloud storage container as an intermediary between the local application and remote reference data. This intermediary enables direct access to cloud-stored files through a standardized interface, eliminating the need for complete local downloads while maintaining offline-capable access patterns through selective caching.
3Stability of the object's composition
If reference data is stored in a centralized location, then version control is improved, but adaptability between projects deteriorates
Solution Approach 1:
The patent segments the centralized reference data into project-specific subsets while maintaining version control at the parent level. Each workspace database can selectively reference specific versions or subsets of the centralized data, allowing different projects to use different versions or configurations of the same reference data while maintaining stability through the centralized version control mechanism.
4Reliability
If fine-grained access permissions are implemented, then security is improved, but system complexity deteriorates
Solution Approach 1:
The patent implements a universal permission system that handles multiple access control requirements through a single mechanism. The workspace database uses a standardized permission framework that can enforce fine-grained access control for different user roles, file types, and operations without requiring separate complex permission management systems for each scenario.
Data Source
AI summary
In example embodiments, techniques are described for using workspace databases to provide workspace resources to customize sessions of applications. File-based workspace databases are maintained in workspace files in a local file system. Cloud-based workspace databases are maintained in a cloud-based blob storage container of a storage account of a cloud storage system. Each cloud-based blob storage container may hold multiple cloud-based workspace databases, including multiple versions of the same database. To use a cloud-based workspace database, a backend module of an application may create an in-memory cloud container object that represents a connection to the cloud-based blob storage container. It may be attached to an in-memory object configured to manage a local cache of blocks of workspace databases. Access to the cloud-based blob storage container may be managed by access tokens provided by a container authority. Modifications to existing workspace databases or addition of new workspace databases may be performed using a workspace editor.