Mobile Web Conversation Update Mechanism

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Updating conversations on mobile devices is inefficient due to the transfer of entire conversations, which consumes bandwidth, battery life, and time, especially over wireless networks, and requires multiple update requests for each conversation.

Innovation Solution

A method and system that send a request from a mobile device to a server with a conversation identifier, first message identifier, last message identifier, and conversation metric, allowing the server to send only new messages to update the conversation, reducing data transfer and using a single request to update multiple conversations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If entire conversations are transferred to the mobile device, then the conversation is fully updated, but bandwidth consumption increases and transfer time increases

Engineering Contradiction:
Improveconversation update completenessVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts only the essential update information (new message identifiers and conversation metrics) from the server and transfers minimal data to the mobile device. Instead of transferring entire conversations, the system sends only the differential changes needed to update the local cache, thereby reducing bandwidth consumption while maintaining update completeness.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The conversation update process is segmented into two parts: (1) transferring minimal metadata (message identifiers and metrics) to identify what needs updating, and (2) selectively retrieving only the specific new messages needed. This segmentation allows the system to update conversations efficiently without transferring unnecessary data.

Inventive Principle:
Principle #1Segmentation

2Reliability

If entire conversations are transferred to the mobile device, then the conversation is fully updated, but transfer time increases

Engineering Contradiction:
Improveconversation update completenessVSAvoidupdate transfer time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the essential update information (new message identifiers and conversation metrics) from the server and transfers minimal data to the mobile device. Instead of transferring entire conversations, the system sends only the differential changes needed to update the local cache, thereby reducing transfer time while maintaining update completeness.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The mobile device maintains a local cache of existing conversation data and message identifiers beforehand. When an update is needed, the device compares the cached data with server data to determine what needs updating, then retrieves only those specific new messages. This preliminary caching action significantly reduces update transfer time.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If separate update requests are sent for each conversation, then each conversation can be updated individually, but battery power consumption increases

Engineering Contradiction:
Improveindividual conversation update controlVSAvoidbattery power consumption
Core Design Contradiction:
Ease of operationVSUse of energy by moving object

Solution Approach 1:

The patent merges multiple conversation update operations into a single batched update request. The mobile device can request updates for multiple conversations simultaneously, and the server processes them in one operation, thereby reducing the number of separate network transactions and lowering battery power consumption while still allowing individual conversation tracking.

Inventive Principle:
Principle #5Merging (Combining)

4Ease of operation

If separate update requests are sent for each conversation, then each conversation can be updated individually, but bandwidth usage increases

Engineering Contradiction:
Improveindividual conversation update controlVSAvoidbandwidth usage
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The patent merges multiple conversation update operations into a single batched update request. The mobile device can request updates for multiple conversations simultaneously, and the server processes them in one operation, thereby reducing the number of separate network transactions and lowering bandwidth usage while still allowing individual conversation tracking.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8868644B2Mechanism for message prefetching in an intermittently connected offline-capable mobile web application
Publication Date: 2014.10.21 GOOGLE LLC
  • US8868644B2 patent drawing
  • US8868644B2 patent drawing
  • US8868644B2 patent drawing

AI summary

A request to update a list of conversations is sent to a server. At least a portion of each conversation in the list of conversations is stored on the client. A plurality of updates is received form the server. The plurality of updates includes messages corresponding to respective conversations in the list of conversations.