Auxiliary Session Data Exchange for Reliable Cross-Platform Transfers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cross-platform communication sessions face inefficiencies due to the lack of standardized methods for sharing auxiliary session data, leading to issues like failed screen pop operations and routing loops, as target platforms often re-query user information or lack necessary billing data.

Innovation Solution

An originating platform transfers auxiliary session data to a target platform using a cross-platform channel, accompanied by a token that uniquely identifies both the originating platform and the data record, allowing seamless retrieval and utilization of auxiliary session data during session transfer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If auxiliary session data is not shared between platforms, then each platform maintains data security and independence, but cross-platform session transfers fail due to lack of necessary data

Engineering Contradiction:
Improvesession transfer reliabilityVSAvoidauxiliary session data availability
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

A standardized data exchange interface acts as an intermediary between distinct platforms, enabling auxiliary session data to be shared during cross-platform session transfers. This interface includes standardized message formats and signaling protocols that allow platforms to exchange necessary data (user profile information, billing data, session context) without compromising their internal data security and independence.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If platforms use proprietary data formats for auxiliary session data, then each platform maintains data integrity, but cross-platform compatibility fails due to format incompatibility

Engineering Contradiction:
Improvecross-platform compatibilityVSAvoiddata exchange complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A universal standardized message format is implemented that can carry multiple types of auxiliary session data (user profile information, billing data, session context, routing information) across different platform types. This standardized format includes flexible fields that can accommodate various data structures while maintaining a consistent exchange protocol, enabling one message structure to serve multiple data transmission needs across diverse platforms.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Loss of time

If auxiliary session data is transmitted during session transfer, then target platforms gain immediate access to necessary data, but data transmission time and channel complexity increase

Engineering Contradiction:
Improvedata retrieval timeVSAvoidchannel coordination complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

Auxiliary session data is prepared and attached to session transfer requests in advance, before the actual session transfer occurs. The originating platform gathers necessary data (user profile information, billing data, session context) and includes it in the transfer signaling messages, so that the target platform receives complete data sets immediately upon session transfer initiation, eliminating the need for separate data retrieval operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250338094A1Coordinated exchange of auxiliary session data for multi-platform environments
Publication Date: 2025.10.30 T MOBILE US INC
  • US20250338094A1 patent drawing
  • US20250338094A1 patent drawing
  • US20250338094A1 patent drawing

AI summary

Aspects of the disclosure relate to cross-platform exchange and sharing of auxiliary session data in connection with a transfer of a communication session. For example, with transfer of a voice call from a first platform to a second platform, the first platform shares profile data for a call participant to the second platform. In an example method, a first platform at which a user is connected to a communication session retrieves auxiliary session data. The first platform determines a transfer of the session to a second platform and sends a data record that includes the auxiliary session data to the second platform. The first platform transfers the communication session via a different cross-platform channel with a token that uniquely identifies the first platform and the data record. Accordingly, the token can be used by the second platform to locate the data record for use during the communication session.