Wrapping Layer for Unified Collaboration in Managed Apps
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current managed applications face challenges in seamlessly integrating collaboration features, such as text chat, video chat, and presence, due to compatibility issues and the need for users to switch between separate applications, leading to a cumbersome and costly process.
Innovation Solution
A method is introduced to automatically render collaboration features within managed applications on client devices by wrapping them with collaboration components, allowing session information sharing and execution across multiple managed applications, using a software development toolkit, API, or standalone collaboration software, and managing feature activation based on stored policies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If collaboration features are added by re-writing native source code after-the-fact, then collaboration functionality is achieved, but the process becomes time-consuming and costly
Solution Approach 1:
The patent applies preliminary action by pre-configuring collaboration features through wrapping mechanisms before the application needs to use them. The wrapping layer is prepared in advance with all necessary collaboration components (chat, video, audio, presence) already integrated, so when an application needs collaboration functionality, it is immediately available without requiring time-consuming source code re-writing.
Solution Approach 2:
The patent uses an intermediary approach by introducing a wrapping layer that sits between the native application and the collaboration features. This wrapping layer acts as a mediator that automatically handles the integration of collaboration functionality, eliminating the need for developers to directly modify application source code and significantly reducing development time and cost.
2Adaptability or versatility
If each application has its own text chat feature, then application-specific chat is available, but compatibility with other applications' chat features is lost and users must switch between applications
Solution Approach 1:
The patent applies universality by creating a unified collaboration layer through wrapping that provides consistent chat, video, audio, and presence features across all managed applications. This wrapping layer enables collaboration features to work universally across different applications without requiring users to switch between separate chat applications, while still maintaining application-specific functionality through the standardized interface.
3Ease of operation
If collaboration features are integrated into managed applications, then seamless collaboration is achieved, but system complexity increases due to wrapping and policy management
Solution Approach 1:
The patent applies segmentation by dividing the system into distinct layers: the native application layer and the collaboration wrapping layer. This segmentation allows collaboration features to be added without modifying the core application code, maintaining a clear separation of concerns. The wrapping layer handles all collaboration functionality independently, which actually reduces overall system complexity by avoiding tangled integrations.
4Ease of manufacture
If wrapping is used to add collaboration features, then integration is simplified, but overhead is introduced in feature activation and policy enforcement
Solution Approach 1:
The patent applies parameter changes by dynamically adjusting feature activation based on policy parameters and runtime conditions. The wrapping layer monitors policy parameters and automatically enables or disables collaboration features as needed, optimizing computational overhead by only activating features when permitted by policies rather than maintaining all features continuously active.
Data Source
AI summary
Methods and systems for an ubiquitous collaboration feature in a managed application environment are described herein. The collaboration service and/or server may store session information and one or more configuration files for use in rendering the collaboration features in combination with managed applications executing on a user's computing device.