Collaboration Handoff Server Session Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional collaboration session handoff technologies disrupt ongoing sessions by requiring users to exit and rejoin, often losing chat history and settings, and may prompt unnecessary security re-entry or notifications, especially when switching between devices.
Innovation Solution
A method for seamlessly transferring collaboration sessions between devices without disrupting the current session, including chat history, video layouts, and settings, by using a collaboration server to manage device lists and handoff requests, allowing users to select a new device without re-entering security credentials or notifying other participants.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional collaboration session handoff technologies are used to transfer sessions between devices, then device switching capability is enabled, but session continuity is disrupted and chat history is lost
Solution Approach 1:
The collaboration server acts as an intermediary that maintains session data independently of client devices. When handoff occurs, the server preserves chat history and session state, transferring only the session identifier to the new device rather than transferring actual session data between devices. This mediator approach prevents information loss during device switching.
Solution Approach 2:
The system performs preliminary actions by pre-establishing session data storage on the server before device switching occurs. The session state, chat history, and configuration are maintained on the server in advance, so when handoff is initiated, the new device simply retrieves this pre-prepared data from the server rather than requiring data transfer or reconstruction.
2Adaptability or versatility
If conventional handoff methods are used, then device transfer is possible, but security re-entry is required
Solution Approach 1:
The collaboration server mediates the authentication process by verifying the user's identity once and maintaining authenticated session state. When transferring to a new device, the server recognizes the authenticated user and grants access without requiring re-entry of security credentials, as the authentication state is maintained on the server rather than being device-specific.
3Adaptability or versatility
If conventional session handoff is implemented, then device switching is enabled, but notifications are sent to other participants
Solution Approach 1:
The collaboration server acts as an intermediary that absorbs the handoff event, preventing it from propagating as a notification to other participants. The server processes the device transfer internally and maintains the session as continuous from the perspective of other participants, thus eliminating the harmful effect of unnecessary notifications while still enabling device switching.
4Ease of operation
If users exit and rejoin sessions to switch devices, then device switching is achieved, but session settings are lost
Solution Approach 1:
The collaboration server maintains session settings, video layouts, and configuration data independently of client devices. When a user switches devices, the server retrieves the preserved settings and transmits them to the new device, eliminating the need for users to manually reconfigure session parameters and preventing settings loss during device transitions.
Data Source
Figure 1a
Figure 1b~1d
Figure 2
AI summary
A collaboration handoff method for seamlessly passing a communication session between devices includes connecting a first device (210) and a second device (216) to enable communication between the first and second devices using an intermediary device (214) to initiate a communication session. A request may be received from one of the first device (210) and a third device (212) to switch to the third device (212) for communication with the second device (216). Communication session data for the first device (210) may be identified at the intermediary device(214). The third device (212) may be connected with the second device (216) within the communication session and the communication session data may be transmitted to the third device (212).