Third-Party Application Control for UCaaS Client Telephony
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
UCaaS platforms lack integration with third-party applications, requiring users to switch between platforms for phone calls, disrupting workflow and productivity.
Innovation Solution
Implement a shared control mode that enables third-party applications to control UCaaS platform devices, using APIs to integrate functions like click-to-call, call transfer, and volume control directly from the third-party application.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If UCaaS platforms maintain separate integrated telephony services, then service reliability is improved, but ease of operation deteriorates due to requiring users to switch between platforms
Solution Approach 1:
The patent merges third-party application control with UCaaS platform telephony services through a shared control mode. The third-party application interface is combined with the UCaaS client interface, allowing users to control desk phone functions (placing calls, transferring calls, conferencing) directly from the third-party application without switching between separate platforms, thus maintaining service reliability while improving ease of operation
Solution Approach 2:
The patent introduces a shared control mode as an intermediary layer between the third-party application and the UCaaS platform. This mediator enables communication and control between the previously disconnected systems, allowing the third-party application to send control commands to the UCaaS platform's desk phone while maintaining the platform's integrated service architecture
2Productivity
If UCaaS platforms integrate third-party application control, then productivity is improved, but device complexity increases
Solution Approach 1:
The patent segments the control functionality into distinct modules within the shared control mode. Specific desk phone functions (call placement, call transfer, conferencing controls) are divided into separate control commands that can be independently implemented. This segmentation allows the system to integrate third-party application control while maintaining manageability and reducing overall system complexity
3Reliability
If separate communication services are used, then service reliability is maintained, but loss of time increases due to manual information passing
Solution Approach 1:
The patent combines third-party application workflows with UCaaS platform communication services in a unified interface. Users can initiate calls, transfer calls, and manage conferencing directly from the third-party application without manually switching to the UCaaS client or passing information between systems, eliminating time loss while maintaining the reliability of the integrated telephony service
Data Source
AI summary
A third party application is used to control a client over a software platform. The third party application sends a control command to a microservice of the software platform. The microservice generates an event socket command based on the control command. The microservice transmits the event socket command to a private branch exchange (PBX) server of the software platform over a transmission control protocol (TCP) connection. The PBX server transmits the event socket command to the client to perform the function based on a binding status that indicates a binding between the third party application and the client.