Secure Digital Model Splicing Through Unified API Endpoints
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing digital engineering tools are siloed, requiring massive teams and expensive subject matter experts for integration and collaboration, leading to redundant physical tests and high costs due to intellectual property concerns, with a lack of unified platforms for multidisciplinary model integration and human-readable documentation.
Innovation Solution
A non-transitory physical storage medium and computer-implemented method for generating sharable model splices of digital engineering models, enabling access to selective digital artifacts through API or SDK endpoints, allowing third-party applications to interact without direct engagement with native tools, and providing a unified programming interface for diverse model types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If digital engineering models from disparate tools are integrated through direct engagement with native tools, then model integration capability is improved, but system complexity and cost increase due to requiring massive teams and expensive subject matter experts
Solution Approach 1:
The patent introduces an intermediary layer (unified programming interface/API gateway) between third-party applications and native digital engineering tools. This intermediary translates requests from various tools into a standardized interface, eliminating the need for direct engagement with multiple complex native tools and reducing system complexity while maintaining integration capability
Solution Approach 2:
The patent creates a universal programming interface that can handle multiple types of digital engineering models from different tools through a single standardized interface. This multi-functional interface replaces the need for tool-specific integration approaches, reducing both system complexity and the expertise required
2Reliability
If intellectual property protection measures are implemented for digital models, then data security is improved, but collaboration efficiency deteriorates due to redundant physical tests and high costs
Solution Approach 1:
The patent extracts only the necessary portions of digital models (selective digital artifacts) and makes them accessible through controlled API endpoints. This allows collaboration on specific model components without exposing the entire model, maintaining IP protection while enabling efficient collaboration and eliminating redundant testing
Solution Approach 2:
The patent creates controlled copies of digital model artifacts that can be shared and accessed by third-party applications through secure APIs. These copies enable collaboration and testing without requiring access to the original protected models, thus maintaining security while improving collaboration efficiency
3Ease of operation
If unified programming interface is implemented for diverse model types, then ease of operation is improved, but implementation complexity increases due to need for secure and scalable architecture
Solution Approach 1:
The patent segments the system into distinct layers: native digital engineering tools, model splicing layer, unified programming interface, and third-party applications. This segmentation allows each layer to handle specific complexity independently, making the overall system easier to operate while distributing implementation complexity across manageable components
Solution Approach 2:
The unified programming interface acts as an intermediary layer that abstracts the complexity of diverse model types and secure access requirements. This intermediary handles the implementation complexity internally while presenting a simple, consistent interface to users, thus improving ease of operation without hiding the underlying implementation complexity
Data Source
AI summary
Methods and systems for generating sharable digital model splices of digital models are provided. The method comprises receiving an input digital model having a digital model type; and generating a default model splice based on the digital model type. The default model splice comprises access to a first splice function script that engages a digital tool associated with the digital model type, that enables external access to a digital artifact derived from the input digital model, and that provides an addressable endpoint to the digital artifact without access to an entirety of the input digital model. The method further comprises receiving an input; generating a second splice function script based on the input; generating a sharable digital model splice from the default model splice and comprising access to the second splice function script; and storing the second splice function script for the digital model type.