Quoted Text Tokenization for Mobile Message Threads

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Message threads in electronic communications often contain redundant quoted text, leading to increased network bandwidth and storage usage on mobile devices, which can impact battery life and storage capacity.

Innovation Solution

A method where a server system identifies quoted text in incoming messages and replaces it with a token, reducing data transmission and storage by sending only the token to the client device, which can then expand the message upon user request to display the original text.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If quoted text is included in each message to maintain conversation context, then message completeness is improved, but network bandwidth and device storage usage increase

Engineering Contradiction:
Improvemessage completenessVSAvoiddata transmission volume
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The patent extracts only the necessary quoted text from previous messages and attaches it as metadata to each message, rather than including the full quoted text in every message body. This allows the system to maintain conversation context while significantly reducing the amount of data transmitted and stored on mobile devices.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary mechanism where the server manages quoted text storage and retrieval. The server stores quoted text centrally and provides it to clients only when needed, acting as a mediator between the full conversation history and the mobile client's storage constraints.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If quoted text is stored on mobile device for each message, then local accessibility is improved, but device storage space is reduced

Engineering Contradiction:
Improvelocal accessibilityVSAvoiddevice storage space
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent makes the quoted text serve multiple functions: it is stored once on the server, referenced by multiple messages, and made accessible to multiple clients. This universal storage approach eliminates the need for each mobile device to store complete copies of quoted text for every message, preserving device storage space while maintaining accessibility.

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

Solution Approach 2:

Instead of storing the actual quoted text content on each mobile device, the system creates references or pointers to the quoted text stored on the server. This copying approach allows mobile devices to access quoted text without duplicating the actual data, thereby preserving device storage space.

Inventive Principle:
Principle #26Copying

3Loss of information

If complete message threads are transmitted to mobile client, then conversation context is improved, but network bandwidth consumption increases

Engineering Contradiction:
Improveconversation contextVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The patent segments the message transmission into two parts: the current message content is transmitted fully, while quoted text from previous messages is transmitted only as metadata references. This segmentation allows the system to maintain conversation context through proper message ordering and references while significantly reducing the total network bandwidth consumed compared to transmitting complete message threads.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9426102B1Efficient conversation transmission to mobile clients
Publication Date: 2016.08.23 GOOGLE LLC
  • US9426102B1 patent drawing
  • US9426102B1 patent drawing
  • US9426102B1 patent drawing

AI summary

A first method includes, at a server, receiving a new message in a message thread, identifying quoted text (e.g., text from a previous message in the message thread) in the new message, replacing the quoted text with a token that includes information uniquely associated with the previous message to produce a modified incoming message, and sending the modified incoming message to a client. Optionally, the token includes information identifying the previous message in the message thread. Optionally, the token identifies a range of text in the previous message, and the text replaced by the token corresponds to the range of text in the previous message identified by the token. Optionally, the token comprises a tag having text to be displayed by the client. In some embodiments, the method includes sending to the client all messages in the message thread, including the modified incoming message.