Multiplexing Mobile Messages via Server-Side User Identifiers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional push notification systems in mobile devices support only a single user profile, limiting their ability to manage message delivery efficiently across multiple user profiles over a single network connection, which can lead to battery drain and inefficient message processing.

Innovation Solution

The system employs a message server that receives and manages messages for multiple user profiles by associating each message with a unique user identifier, allowing for multiplexing of a single network connection to deliver messages to independent user profiles on a mobile device, enabling efficient message delivery across multiple user profiles.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If a single network connection is used for message delivery to multiple user profiles, then network resource utilization is improved, but message delivery efficiency deteriorates due to connection sharing overhead

Engineering Contradiction:
Improvenetwork connection utilizationVSAvoidmessage delivery efficiency
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent segments the single network connection into multiple logical channels by introducing connection identifiers that distinguish different user profiles. Each message is tagged with the appropriate connection identifier, allowing the system to multiplex multiple user profile communications over a single physical connection while maintaining logical separation and efficient routing for each profile.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If multiple user profiles are supported on a mobile device, then user versatility is improved, but message processing complexity increases due to independent application instances

Engineering Contradiction:
Improveuser profile supportVSAvoidmessage processing architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a message server as an intermediary between the application server and multiple user profiles on the mobile device. The message server receives messages, determines the appropriate user profile based on connection identifiers, and routes messages accordingly. This intermediary simplifies the architecture by centralizing the complexity of multi-profile message management on the server side rather than requiring complex client-side handling for each user profile.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If continuous message checking is performed on mobile devices, then message delivery reliability is improved, but energy consumption increases

Engineering Contradiction:
Improvemessage delivery assuranceVSAvoidmobile device battery consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent implements push notification technology where the message server proactively pushes messages to mobile devices before the devices need to check for them. This preliminary action of pre-notifying the device eliminates the need for continuous polling or checking, thereby ensuring reliable message delivery while significantly reducing mobile device energy consumption since the device only wakes up when a message is pushed to it.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10237222B2Systems and methods for directing messages to multiple user profiles on a mobile device
Publication Date: 2019.03.19 GOOGLE LLC
  • US10237222B2 patent drawing
  • US10237222B2 patent drawing
  • US10237222B2 patent drawing

AI summary

The disclosed technology covers messaging systems and methods, and computer program products embodying such systems and methods. An example computer-implemented method includes receiving, at a message server, a plurality of messages for a plurality of remote mobile devices; and providing a single network connection between the message server and a first mobile device of the plurality of mobile devices. The first mobile device may have a first user profile and a second user profile, each with its own applications and preferences. The method may include associating the first user profile with a first user identifier, and the second user profile with a second identifier. When a message is received, and directed toward the first user profile, the method may include packaging the first message with the first user identifier, and transmitting the first message, along with the first user identifier, to the first mobile device.