Softphone Over DaaS Framework Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Desktop-as-a-Service (DaaS) solutions do not enable portable telephone access, leading to inefficiencies and security concerns, as users must access their full desktop to use a softphone client, which requires multiple logins and lacks centralized management of telephone numbers and usage metrics.
Innovation Solution
The Softphone-over-DaaS (SoDaaS) framework allows users to access telephone services independently by determining and configuring a telephone number on a client device, enabling single sign-on and centralized management of telephone access, reducing server resource usage and improving security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a generic softphone client is installed as a native application within each user's desktop, then users can send and receive phone calls through the telephony service, but the user must request and access their full desktop before using the softphone client, leading to inefficiencies in server resource allocation
Solution Approach 1:
The patent segments the softphone client from the full desktop environment, allowing the softphone to be delivered and executed as a separate, standalone component. This enables users to access telephony functionality without requiring the overhead of a complete desktop session, thereby improving server resource allocation efficiency while maintaining ease of access to the softphone client.
2Adaptability or versatility
If a generic softphone client is used for all users, then the softphone client is universally accessible, but the service provider has no visibility into or control over the mapping of users to telephony accounts, preventing centralized management
Solution Approach 1:
The patent implements feedback mechanisms where the softphone client communicates user identification and telephony account mapping information back to the service provider's server. This enables the service provider to maintain visibility and control over user-to-telephony-account mappings, achieving centralized management while preserving the universal accessibility of the softphone client through dynamic configuration based on received feedback.
3Ease of operation
If the softphone client is delivered as a native desktop application, then the user can use telephony services, but the user must login at least twice (once to DaaS service and again to telephony service), which is burdensome and error-prone
Solution Approach 1:
The patent merges the authentication processes of the DaaS service and the telephony service into a single unified login operation. By integrating the telephony service authentication with the existing DaaS login mechanism, users perform only one login action to gain access to both services, eliminating the time loss and burden associated with multiple separate login operations while maintaining ease of telephony service access.
Data Source
AI summary
Techniques for delivering telephone access are provided. In one embodiment, a server system can determine a telephone number assigned to a user operating a client device. The server system can further retrieve, based on the telephone number, softphone configuration data from a telephony service, where the softphone configuration data enables a softphone associated with the client device to register itself, and the telephone number, with the telephony service. The server system can then transmit the softphone configuration data to the client device.