Accessory Device Application Stub for Companion Computing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Accessory devices with limited resources, such as wearable computers, face challenges in installing applications and providing features comparable to mobile devices due to their restricted computing power and storage capacity.

Innovation Solution

An accessory device application is developed that includes an accessory device stub application and an interface definition, installed on the accessory device, which leverages the data processing and computational power of a companion device to enhance user experience by generating and displaying updated values.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If accessory devices use their own local processing resources to run applications, then application functionality can be executed directly on the device, but the device's limited computing power and storage capacity restrict the complexity and variety of available applications

Engineering Contradiction:
Improveapplication functionalityVSAvoidcomputing power
Core Design Contradiction:
Adaptability or versatilityVSPower

Solution Approach 1:

The patent introduces a companion device as an intermediary that hosts the full application functionality remotely. The accessory device communicates with the companion device over a wireless network, allowing complex applications to run on the companion device while the accessory device provides a simplified interface. This mediator approach enables the accessory device to access advanced features without requiring local processing power.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If accessory devices install full applications locally, then complete application features are available on the device, but the storage capacity is quickly exhausted

Engineering Contradiction:
Improveapplication featuresVSAvoidstorage capacity
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

Instead of storing complete applications locally on the accessory device, the system creates a simplified copy or interface layer that communicates with the full application running on the companion device. The accessory device installs only essential stub applications that serve as proxies, accessing the complete application functionality remotely through wireless communication. This copying approach preserves storage space while maintaining full feature access.

Inventive Principle:
Principle #26Copying

3Use of energy by moving object

If accessory devices run simplified interface only, then resource consumption is reduced, but the user experience lacks depth and engagement

Engineering Contradiction:
Improveenergy consumptionVSAvoiduser experience
Core Design Contradiction:
Use of energy by moving objectVSEase of operation

Solution Approach 1:

The patent adds a network communication dimension to the system architecture. The accessory device operates in two dimensions: locally processing simple interface interactions and remotely accessing complex application logic through wireless network communication. This dimensional expansion allows the device to maintain low local resource consumption while providing rich user experience by leveraging the companion device's processing power over the network dimension.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentEP4145279A1Accessory device operation with user mobile device
Publication Date: 2023.03.08 APPLE INC
  • EP4145279A1 patent drawingFigure 1
  • EP4145279A1 patent drawingFigure 2
  • EP4145279A1 patent drawingFigure 3

AI summary

An accessory device application executes on an accessory device of limited resources. The accessory device application includes an accessory device stub application and an interface definition. When a user interacts with the accessory device application, display changes are generated in response, in accordance with the interface definition, and are sent to a companion extension at an associated companion device. The companion extension receives the changes, and generates updated display values for the accessory device display. The updated display values are sent from the companion device daemon to the daemon of the accessory device, which displays the updated display values at the accessory device display. The functionality and operation of the accessory device application permit an accessory device of limited resources to leverage data processing and computational power of the companion device, to provide a more involving user experience at the accessory device.