Pre-building Meeting Containers to Reduce Startup Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Access to user documents or programs on public computing devices is often slow, leading to user frustration due to the need for containers to be built at the start of a meeting, causing delays in accessing relevant data.
Innovation Solution
Pre-building containers with isolated usage sessions provisioned for meetings, either statically or dynamically, to reduce startup delays by having necessary data and applications already available, and updating containers as needed with new information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If containers are built at the start of a meeting, then secure isolated usage sessions are provided, but access time to documents and programs is slow
Solution Approach 1:
The system pre-builds containers before meetings by receiving meeting indications from calendaring systems and creating isolated usage sessions in advance. This preliminary action ensures that when the meeting starts, the container is already prepared with necessary applications and documents, eliminating startup delays while maintaining security isolation.
Solution Approach 2:
The system creates container copies from templates that contain pre-configured applications and documents. Instead of building containers from scratch at meeting start, the system copies pre-prepared container configurations, significantly reducing access time while maintaining the secure isolated environment through containerization.
2Speed
If containers are pre-built with all necessary data and applications, then access speed is improved, but device complexity increases
Solution Approach 1:
The system implements self-service mechanisms where the container management system automatically receives meeting indications, selects appropriate templates, and builds or retrieves containers without manual intervention. This automation reduces the perceived complexity for users while maintaining the necessary infrastructure for fast container access.
Solution Approach 2:
The system uses universal container templates that can serve multiple meeting types and purposes. By creating multi-functional templates that contain commonly used applications and documents, the system reduces the need for numerous specialized containers, thereby managing complexity while maintaining fast access speeds through reusable configurations.
Data Source
AI summary
A container for one or more scheduled meeting is pre-built for the meeting prior to the meeting occurring. The container can be built in a variety of manners, including using both static and dynamic techniques. Dynamic techniques for building a container allows a pre-build system to include more pertinent data in the container whereas static techniques reduce computing workload and allow for pre-building containers for unscheduled meetings. A combination of static and dynamic building techniques can be applied using a layer repository. Alternately, a static base layer can be used and customized for scheduled meetings.