VOIP Platform Process Segmentation for Resource Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developing VOIP applications for mobile devices with limited resources poses challenges in maintaining high quality user experience across both low-end and high-end hardware, particularly due to resource sharing and switching between different types of calls, which are not encountered in personal computers or tablets.
Innovation Solution
A VOIP platform is developed that partitions processes into UI and agent host processes to conserve resources, using existing push client services for notifications and keep-alive functions to manage battery life and resource allocation, ensuring seamless operation and quality across varying hardware capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If VOIP applications run on mobile devices with limited resources, then device accessibility is improved, but call quality deteriorates
Solution Approach 1:
The VOIP application is divided into two separate processes: a UI host process that handles user interface functions and runs only when needed, and an agent host process that handles call processing functionality and runs in the background. This segmentation allows the application to maintain call quality through dedicated processing while reducing overall resource consumption on limited devices.
Solution Approach 2:
The application dynamically adjusts its resource consumption by launching the UI host process only when the user interface is needed and keeping the agent host process running in the background for continuous call processing. This dynamic behavior enables the application to adapt to varying hardware resources while maintaining call quality.
2Adaptability or versatility
If hardware resources are allocated to multiple applications, then application versatility is improved, but VOIP call quality deteriorates
Solution Approach 1:
By separating the VOIP application into UI and agent host processes, the system can allocate resources more efficiently. The agent host process maintains dedicated resources for call processing even when other applications are running, ensuring VOIP call quality is not compromised by resource sharing.
Solution Approach 2:
The agent host process acts as an intermediary that ensures VOIP call processing receives prioritized resource allocation independent of other applications. This intermediary layer protects call quality from resource contention while still allowing multi-application versatility.
3Speed
If all VOIP application code runs in the foreground process, then processing speed is improved, but battery life deteriorates
Solution Approach 1:
The application code is segmented into UI-related functions that run in the foreground process and call processing functions that run in the background agent host process. This segmentation allows the system to maintain fast UI response when needed while reducing overall power consumption by keeping critical call processing in a dedicated background process.
Solution Approach 2:
The agent host process runs periodically in the background to maintain call processing functionality without requiring continuous foreground execution. This periodic operation reduces energy consumption while ensuring call quality is maintained through background processing.
Data Source
AI summary
A computer-implemented system is provided that facilitates implementation of a voice over IP (VOIP) application. The system includes a host system and a user interface (UI) host process residing on the host system. The system also includes an agent host process residing on the host system which is being configured to process a VOIP call received by one or more VOIP applications executable on the host system. The agent host process running as a foreground or background process for the duration of the VOIP call to (i) communicate with a VOIP server associated with the VOIP application, (ii) capture content from at least one input device associated with the host system and (iii) render content on an output device associated with the host system when an instance of the UI host process operates in the foreground.