RCS Origination Forking for Multi-Device Message Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Rich Communication Services (RCS) systems do not effectively manage message origination across multiple devices associated with a single user ID, leading to inconsistencies in displaying outgoing and incoming messages, as messages sent from one device may be received on another, causing confusion in conversation threads.

Innovation Solution

Implementing origination forking in RCS systems, where the RCS server forwards messages to all associated devices with the same user ID, and uses headers to classify messages as incoming or outgoing, ensuring correct display in conversation threads, and devices register their support for origination forking during network registration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If RCS systems support multiple devices with a single user ID, then device versatility and user convenience are improved, but message origin tracking and conversation thread consistency deteriorate

Engineering Contradiction:
Improvemulti-device supportVSAvoidmessage origin tracking
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent introduces an intermediary mechanism (the message forwarding process with origin device identification) that mediates between multiple endpoint devices and the RCS server. The system identifies the original sending device and forwards messages from other devices as if they originated from the identified device, preserving message origin tracking while enabling multi-device support

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a copying mechanism where the RCS server forwards messages to additional devices associated with the same user ID. The message content is copied and delivered to multiple devices while maintaining the original message origin information through the identification mechanism

Inventive Principle:
Principle #26Copying

2Stability of the object's composition

If messages are forwarded to all associated devices, then message synchronization across devices is improved, but device complexity and network traffic increase

Engineering Contradiction:
Improvemessage synchronizationVSAvoidmessage handling complexity
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The patent implements a universal message handling approach where the RCS server performs multiple functions: identifying the origin device, determining associated devices, forwarding messages appropriately, and managing conversation thread consistency. This multi-functional approach simplifies the overall system architecture while achieving message synchronization across devices

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

3Adaptability or versatility

If outgoing messages from one device are displayed on another device, then multi-device accessibility is improved, but conversation thread accuracy deteriorates

Engineering Contradiction:
Improvemulti-device accessibilityVSAvoidconversation thread accuracy
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The RCS server acts as an intermediary that preserves conversation thread accuracy by identifying the original sending device and forwarding messages with appropriate origin information. This allows messages to be accessible on multiple devices while maintaining accurate conversation threads that reflect the actual message flow

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10237212B2RCS origination forking
Publication Date: 2019.03.19 T MOBILE US INC
  • US10237212B2 patent drawing
  • US10237212B2 patent drawing
  • US10237212B2 patent drawing

AI summary

In an IMS (IP multimedia system) and/or RCS (rich communication services) environment, devices that support origination forking of various message types are configured to register with an IMS network and to provide an indication that they support origination forking. The IMS network is configured to record this information for its subscribing devices. When the IMS network receives a message request from an origination device, the message request is forwarded to termination devices as well as to other supporting devices that are associated with the user of the origination device.