Secure Content Engine with Segmented Cloud UI and On-Premises Repository
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise content management systems face challenges in sharing and syncing content while maintaining control over enterprise content, as traditional methods require downtime for updates and cloud-based systems compromise content ownership and security.
Innovation Solution
A system and method for secure content sharing and synchronization using a content engine that communicates with client devices across multiple platforms, allowing independent management and updates of user experience, application logic, and content distribution systems without direct communication, ensuring content is stored behind a firewall with full audit trails and access controls.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional enterprise content management systems are used, then content security and ownership control are maintained, but system updates require downtime and clients cannot access content during updates
Solution Approach 1:
The system separates the ECM system into two independent components: the content repository (server-side) and the user interface (client-side). The UI can be updated independently and deployed to the cloud without affecting the content repository, allowing continuous content access while enabling frequent UI updates without downtime.
Solution Approach 2:
The cloud-based UI acts as an intermediary layer between users and the content repository. This mediator can be updated and improved continuously in the cloud while the content repository remains stable and secure, allowing UI enhancements without requiring system downtime or compromising content security.
2Adaptability or versatility
If cloud-based systems are used, then user interface updates can be rolled out incrementally without downtime, but enterprise content ownership and security control are compromised
Solution Approach 1:
The system divides functionality into two segments: the content repository remains on-premises under enterprise control for security, while the UI layer is deployed to the cloud for flexible updates. This segmentation allows cloud-based UI adaptability without compromising on-premises content security.
Solution Approach 2:
The cloud-based UI serves as a secure intermediary that interacts with the on-premises content repository through controlled interfaces. This architecture enables frequent UI updates in the cloud while maintaining enterprise control and security over the content repository through authentication and authorization mechanisms.
3Ease of operation
If clients are integrally tied to the ECM repository, then direct access is simplified, but independent updates of UI and content system are impossible
Solution Approach 1:
The system separates the client application into a cloud-based UI layer and a server-based content repository. The UI can be updated independently and deployed to the cloud without modifying the content repository, enabling independent updates while maintaining simple access through the cloud UI.
Solution Approach 2:
The cloud-based UI acts as an intermediary that simplifies client access to content while enabling independent updates. The UI layer can be enhanced and updated without affecting the content repository, and clients access content through this updated UI without needing direct repository connections.
Data Source
AI summary
A flexible content sharing system may comprise a network based application built on a client device using information from dissociated user experience component (UXC), application logic and execution layer (ALEL), and content distribution system (CDS) payloads. An ALEL engine may communicate a request from the network based application to a CDS module. The CDS module may interface the ALEL engine and a CDS server. The ALEL engine can act as a gate keeper and securely communicates requests from client devices to the CDS server. The CDS server is configured to manage and alert the ALEL of any enterprise policies that may be applicable to the client devices connected to the ALEL engine which, in turn, notifies the client devices to comply with the enterprise policies. The CDS server may synchronize any change made to the content by any of the client devices running network based applications.


