Wearable Device Cloud Recipe Synchronization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Wearable devices lack an efficient method for third-party services to provide real-time features and content without requiring application or software development, limiting the ability to offer dynamic and user-specific functionality.

Innovation Solution

A system where third-party services can provide recipes via a cloud API, defining triggering events and display templates, allowing wearable devices to synchronize and execute content and actions based on user inputs and sensor data, enabling real-time feature integration without development efforts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If third-party services want to provide real-time features to wearable devices, then functionality and user experience are improved, but software development complexity and device complexity increase

Engineering Contradiction:

Improvethird-party service integrationVSAvoidsoftware development complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a cloud-based recipe management system as an intermediary between third-party services and wearable devices. The cloud server receives recipes from third-party services, processes them, and transmits them to wearable devices via communication networks. This intermediary layer eliminates the need for third-party services to directly integrate with device software, reducing development complexity while enabling real-time feature provision.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments functionality into separate components: the wearable device handles local execution of recipes, the cloud server manages recipe processing and communication, and third-party services provide content. This segmentation allows each component to operate independently, simplifying the integration process for third-party services while maintaining real-time capability through the cloud-based architecture.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If wearable devices receive and execute real-time recipes with triggering events, then adaptability and real-time functionality are improved, but device processing requirements and complexity increase

Engineering Contradiction:

Improvereal-time feature provisionVSAvoidprocessing requirements

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary processing of recipes on the cloud server before transmission to wearable devices. The cloud server validates, processes, and prepares recipes in advance, so that when recipes are received by the wearable device, they are already in an executable format. This preliminary action reduces the processing burden on the wearable device while enabling real-time functionality.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The wearable device is designed to autonomously receive recipes, detect triggering events, and execute corresponding actions without requiring complex processing or external intervention. The device self-manages the recipe execution lifecycle, from receiving the recipe via communication to detecting events and performing actions, thereby minimizing processing requirements while maintaining adaptability.

Inventive Principle:

Principle #25Self-service

3Ease of operation

If the system uses recipes with triggering events for content delivery, then user experience and context-awareness are improved, but system complexity and implementation difficulty increase

Engineering Contradiction:

Improveuser experienceVSAvoidsystem implementation

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The cloud server acts as an intermediary that handles the complexity of recipe management, triggering event detection, and content delivery. It receives triggering event definitions from third-party services, processes them, and manages the overall system logic. This intermediary approach simplifies implementation for wearable devices while enabling sophisticated user experiences through context-aware content delivery.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The recipe format serves as a universal interface that can accommodate various types of triggering events and content elements from different third-party services. The system uses a standardized recipe structure that can be processed by the wearable device regardless of the specific service or event type, thereby simplifying implementation while enabling diverse and engaging user experiences.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS11797248B2Provision of content and/or functional features to wearable devices

Publication Date: 2023.10.24 SUUNTO OY

AI summary

There is provided a wearable device, comprising: at least one processing core; at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processing core, cause the wearable device to: receive one or more recipes being indicative of input elements for the computer program code, the input elements comprising at least one or more triggering events; one or more display templates; one or more content elements; receive user input for selection of a recipe of the one or more recipes; detect a triggering event corresponding to the one or more triggering events; in response to detecting the triggering event, provide the one or more content elements corresponding to the triggering event for display on a display of the wearable device according to a display template corresponding to the triggering event.