Role-Based Application Shell Dynamic Content Delivery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems that store all programming and application versions locally on users' computers consume bandwidth, occupy storage space, and are prone to security breaches, as they often provide unnecessary features and code.
Innovation Solution
A system that identifies user roles and provides only role-specific code and data upon login, updating and modifying the application shell dynamically based on user roles, login events, and training stages, while streaming content and eliminating unnecessary code storage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all programming and application versions are stored locally on users' computers, then complete functionality is available, but bandwidth consumption increases, storage space is occupied, and security risks increase
Solution Approach 1:
The patent segments the application into a shell component and dynamic content components. The shell is stored locally on the user's computer, while the dynamic content is stored remotely on the server. This segmentation allows the system to avoid downloading complete application versions while maintaining functionality, thereby reducing bandwidth consumption and storage requirements.
Solution Approach 2:
The patent extracts the dynamic content from the complete application and stores it separately on the server. Only the essential shell remains on the user's computer, while role-specific code, data, and features are extracted and delivered on-demand based on user login events and identified roles, reducing local storage needs and bandwidth usage.
2Reliability
If all programming and application versions are stored locally on users' computers, then complete functionality is available, but storage space on users' computers is occupied
Solution Approach 1:
The application is divided into a lightweight shell stored locally and role-specific dynamic content stored remotely. This segmentation dramatically reduces the storage space required on users' computers while preserving complete functionality through on-demand content delivery.
Solution Approach 2:
The patent extracts role-specific code, data, and features from the complete application and stores them on the server. Only the essential shell remains on the user's computer, freeing up storage space while maintaining functionality through selective content delivery based on user roles.
3Ease of operation
If all programming and application versions are stored locally on users' computers, then offline access is possible, but security breaches become more likely due to unnecessary code and data
Solution Approach 1:
The patent extracts and removes unnecessary code, data, and features that are not required for the user's specific role. By delivering only role-specific content, the system minimizes the attack surface and reduces security risks associated with storing and processing unnecessary information on users' computers.
Solution Approach 2:
The patent implements local quality by customizing the application content for each user's specific role. The shell is enhanced with only the code and data relevant to that user's job functions, eliminating extraneous elements that could pose security risks while maintaining the necessary functionality for offline access.
4Loss of energy
If role-specific code and data are delivered dynamically upon login, then bandwidth consumption and storage requirements are reduced, but system complexity increases
Solution Approach 1:
The patent introduces a deployment service as an intermediary between the server and the user's computer. This mediator automatically identifies the user's role based on login events, selects the appropriate role-specific content, and integrates it into the application shell. This intermediary manages the complexity of dynamic content delivery, shielding users from the underlying system complexity while achieving bandwidth and storage efficiency.
Data Source
AI summary
Embodiments for updating roles based system access to a user include systems for identifying an application login event and a role associated with the login event. Further the embodiments include selecting an application shell comprising data for an application, the data being associated with the identified role and where the application is a first version of the application, selecting a second version of the application that is different from the first version, modifying the data of the application shell in response to selecting the second version of the application, and providing the modified data to the application associated with a computing device of a user in response to the login event. In specific embodiments, data unrelated to the identified role is not provided to the application or stored in the computing device.