Packaged Complication Data Management for Wearable Displays

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Computerized watches face challenges in efficiently displaying data due to small screen size and power constraints, limiting their ability to maintain data connections and updates without reducing battery life.

Innovation Solution

A method where a computing device requests and receives a single package of data from a data provider containing multiple updates and timing information for a complication, allowing it to display updates without frequent communication, thereby reducing power consumption and extending battery life.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If the computing device maintains a data connection to receive frequent updates, then the data freshness and update frequency are improved, but the power consumption increases and battery life decreases

Engineering Contradiction:
Improvedata freshnessVSAvoidpower consumption
Core Design Contradiction:
Loss of informationVSUse of energy by moving object

Solution Approach 1:

The server performs preliminary actions by generating multiple complication data updates in advance and packaging them together with timing data before transmission. This allows the computing device to receive a batch of pre-prepared updates in a single communication event, ensuring data freshness without needing to maintain continuous connections or frequently pollute the server.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The computing device transitions from continuous or frequent periodic connections to less frequent periodic connections. By receiving packaged updates that contain multiple updates with timing data, the device can enter lower-power states between package receptions, reducing overall power consumption while still maintaining acceptable data freshness through the pre-packaged updates.

Inventive Principle:
Principle #19Periodic action

2Loss of information

If the computing device requests updates frequently to ensure current information, then the data currency is improved, but the communication overhead and network usage increase

Engineering Contradiction:
Improvedata currencyVSAvoidcommunication overhead
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

Multiple separate update requests and responses are merged into a single packaged complication data transmission. The server combines multiple complication data updates and their associated timing data into one package, reducing the number of communication events between the computing device and the server, thereby reducing communication overhead and network usage.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The server performs the action of preparing and packaging multiple updates in advance before the computing device receives them. This preliminary packaging eliminates the need for multiple separate request-response cycles, reducing communication overhead while ensuring the device receives current information through the pre-packaged updates.

Inventive Principle:
Principle #10Preliminary action

3Duration of action of moving object

If the device displays multiple updates from a single data package, then the battery life is extended by reducing communications, but the device must manage and schedule updates internally

Engineering Contradiction:
Improvebattery lifeVSAvoidupdate management complexity
Core Design Contradiction:
Duration of action of moving objectVSDevice complexity

Solution Approach 1:

The computing device performs self-service by internally managing the scheduling and display of received complication data updates using the timing data included in the package. Instead of requiring continuous server guidance or frequent communication, the device autonomously determines when to display each update based on the embedded timing information, extending battery life while handling its own update management.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The timing data embedded in the packaged complication data acts as an intermediary that carries scheduling instructions from the server to the computing device. This intermediary information enables the device to autonomously manage update timing and display scheduling without requiring complex external coordination, balancing battery extension with manageable device complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP3545410B1Application program interface for managing complication data
Publication Date: 2023.03.08 GOOGLE LLC
  • EP3545410B1 patent drawingFigure 1
  • EP3545410B1 patent drawingFigure 2
  • EP3545410B1 patent drawingFigure 3

AI summary

A computing device is described that requests, at a first time and from a data provider, packaged complication data associated with a complication that comprises a graphical notification element on a display device. The computing device receives the packaged complication data that includes a plurality of complication data updates and timing data that defines a respective length of time that each complication data update is to be displayed. The computing device, responsive to receiving the packaged complication data, outputs, for display, a graphical user interface including current time information and the complication including a graphical indication of a first complication data update. The computing device determines a second time at which to output a graphical indication of a second complication data update for display. The computing device replaces, at the second time, the graphical indication of the first complication data update with that of the second complication data update.