Cloud Connector for Unified Communication System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional telecommunications systems face challenges with mobile endpoint devices, including shortened battery life, application shutdowns, connectivity issues, and difficulty in transitioning between cloud-based and on-premises devices, leading to disrupted real-time communications.
Innovation Solution
A locus-based cloud service system that monitors and manages real-time communications across cloud and on-premises devices, using a cloud connector to facilitate seamless communication between client devices and on-premises systems, enabling notifications, media streaming, and seamless reconnection even when devices lose signal.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional call agents maintain long-term signal connections with mobile endpoint devices, then the call agent can monitor device availability, but the mobile device battery life is shortened
Solution Approach 1:
The system transitions from continuous long-term signal connections to periodic connection attempts. The cloud service stores device identifiers and initiates periodic connection attempts to mobile devices, allowing the device to remain in a low-power state while still enabling availability monitoring through intermittent signaling.
Solution Approach 2:
A cloud-based service acts as an intermediary between the call agent and mobile endpoint devices. The cloud service maintains the signaling connection with the call agent while communicating with mobile devices only when needed, decoupling the continuous monitoring requirement from the mobile device's power consumption.
2Loss of energy
If mobile operating systems shut down background applications, then device resources are conserved, but real-time communication sessions are disrupted
Solution Approach 1:
The cloud service acts as a persistent intermediary that maintains communication session state independently of mobile device application states. When a mobile device reconnects after being shut down, the cloud service restores the communication session using stored session information, ensuring continuity without requiring background applications to remain active.
Solution Approach 2:
The system performs preliminary actions by storing device identifiers, communication session state, and configuration information in the cloud before the mobile device needs to reconnect. This pre-stored information enables rapid session restoration without requiring the application to remain running in the background.
3Adaptability or versatility
If mobile endpoint devices experience connectivity loss in degraded signal areas, then mobile devices can operate independently, but real-time communication sessions are dropped and difficult to re-establish
Solution Approach 1:
The cloud service serves as a persistent intermediary that maintains communication session state even when mobile devices are disconnected. When a device reconnects after signal loss, the cloud service uses stored session information to automatically restore the communication, eliminating the need for manual reconnection procedures.
Solution Approach 2:
The system prepares for potential disconnections by storing device identifiers, session state, and communication parameters in the cloud beforehand. This pre-stored information acts as a cushion that enables automatic session restoration when devices reconnect after experiencing signal degradation or loss.
4Device complexity
If conventional telecommunication systems are used for device transitions, then system simplicity is maintained, but transitioning between cloud-based and on-premises devices is difficult
Solution Approach 1:
The cloud service implements a universal device identifier system and unified communication interface that works across both cloud-based and on-premises devices. This allows seamless transitions between device types and locations without requiring complex system reconfiguration, as the same cloud service manages communications for all device types.
Solution Approach 2:
The cloud service acts as an intermediary layer between users and diverse endpoint devices (both cloud-based and on-premises). This intermediary abstracts the complexity of device transitions by providing a unified interface for initiating and managing communications, regardless of the specific device type or location involved.
Data Source
AI summary
Techniques are described herein for facilitating a connection between a cloud networking platform and a unified communication system, where the cloud networking platform hosts communication services including real-time communications for client devices, and the unified communication system hosts communication services including real-time communications for on-prem devices that are associated with the unified communication system. Events associated with the cloud networking platform are monitored at the unified communication system, via a cloud connector device of the unified communication system, where events are associated with users who are registered with client devices and on-prem devices, and the events include real-time communications. A notification is provided to one or more client devices registered to a first user in response to an on-prem device also registered to the first user receiving a real-time communication request from a device of another user.