User-Aware Cloud Messaging for Battery Conservation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional push notification systems lack efficiency in managing message delivery to mobile devices with multiple user profiles, as they typically require immediate transmission, which drains battery power by activating inactive user profiles and do not account for the different states of user profiles, leading to unnecessary resource usage.

Innovation Solution

A messaging system that identifies and differentiates between active and inactive user profiles, temporarily holding messages for inactive profiles until an active profile is detected, allowing for batched transmission and reducing the need for continuous radio activation, thereby conserving battery power.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If messages are transmitted immediately upon receipt, then message delivery speed is improved, but battery power is drained unnecessarily by activating inactive user profiles

Engineering Contradiction:
Improvemessage delivery speedVSAvoidbattery power consumption
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The system performs preliminary classification of user profiles into active and inactive states before message transmission. Messages are queued and held in a buffer until an active user profile becomes available, preventing unnecessary activation of inactive profiles and conserving battery power while maintaining timely delivery when users are actually available.

Inventive Principle:
Principle #10Preliminary action

2Use of energy by moving object

If the system monitors and differentiates between active and inactive user profiles, then power management is improved, but system complexity increases

Engineering Contradiction:
Improvepower management efficiencyVSAvoidmessage management system complexity
Core Design Contradiction:
Use of energy by moving objectVSDevice complexity

Solution Approach 1:

The system segments user profiles into distinct categories (active and inactive) and implements separate handling pathways for messages destined for each category. This segmentation allows the system to apply different transmission strategies - immediate delivery for active profiles and queued delivery for inactive profiles - thereby improving power management without requiring overly complex unified logic.

Inventive Principle:
Principle #1Segmentation

3Use of energy by moving object

If messages are held in queue for later transmission, then battery power is conserved, but message delivery time is extended

Engineering Contradiction:
Improvebattery power conservationVSAvoidmessage delivery delay
Core Design Contradiction:
Use of energy by moving objectVSLoss of time

Solution Approach 1:

The message transmission system dynamically adjusts its behavior based on the real-time state of user profiles. Rather than using a static immediate-transmission or fixed-delay approach, the system continuously monitors profile availability and transmits messages as soon as an active profile becomes available, minimizing delay while conserving power by avoiding transmissions to inactive profiles.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP2974232B1User- aware cloud to device messaging systems and methods
Publication Date: 2018.01.17 GOOGLE LLC
  • EP2974232B1 patent drawingFigure 1
  • EP2974232B1 patent drawingFigure 2
  • EP2974232B1 patent drawingFigure 3

AI summary

The disclosed technology covers messaging systems and methods, and computer program products embodying such systems and methods. An example computer-implemented method may include receiving, at a message server, a plurality of messages directed toward a plurality of computing devices, the plurality of messages including a first message directed toward a first user profile. A first computing device may be identified as being associated with the first user profile. It may be determined, by a computer processor, that the first user profile is inactive on the first computing device and that a second user profile is active on the first computing device. In that case, the first message may be held at the message server due to the first user profile being inactive. Other implementations of the messaging systems and methods are also disclosed herein.