On-device Journey Execution for Resource Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing customer journey execution systems require communication of events and conditions over a network, leading to inefficient use of computing and network resources, especially when devices are disconnected from the internet.

Innovation Solution

Implementing on-device journey execution, where customer journeys are stored and executed directly on the customer's device based on local events or conditions, without the need for network communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If customer journeys are executed on a server requiring network communication, then centralized control and management are improved, but network resource utilization and computing resource utilization deteriorate due to continuous data communication requirements

Engineering Contradiction:
Improvecentralized controlVSAvoidnetwork resource utilization
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments the journey execution system by dividing it into two parts: journey definition and management on the server, and journey execution on the customer device. This segmentation allows centralized control to be maintained for journey configuration while execution occurs locally, eliminating the need for continuous network communication during journey execution and reducing network resource utilization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts the journey execution functionality from the server and places it directly on the customer device. By taking out the execution component from the centralized server, the system maintains centralized control for management purposes while eliminating continuous network communication requirements during execution, thus reducing network resource utilization.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If customer journeys are executed on a server requiring network communication, then centralized control and management are improved, but computing resource utilization deteriorates

Engineering Contradiction:
Improvecentralized controlVSAvoidcomputing resource utilization
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent segments the system architecture to separate journey management (server-side) from journey execution (device-side). This segmentation shifts computing resources required for execution from the server to the customer device, reducing server computing resource utilization while maintaining centralized control over journey definitions and updates.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The execution engine is extracted from the server and deployed to the customer device. This extraction moves the computational burden of journey execution from the server to the device, thereby reducing server computing resource utilization while preserving centralized control capabilities for journey management.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If journeys are executed only when device communicates with server, then centralized control is maintained, but productivity deteriorates due to delayed action execution

Engineering Contradiction:
Improvecentralized controlVSAvoidaction execution speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements preliminary action by downloading and storing journey definitions and execution logic on the customer device before journeys need to be executed. This preliminary preparation enables immediate local execution of journeys without waiting for server communication, thereby improving productivity while centralized control maintains authority over journey definitions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The customer device is empowered with self-service capabilities by providing it with a local execution engine that can autonomously execute journeys without continuous server intervention. This self-service approach allows journeys to be executed immediately when conditions are met, improving productivity while centralized control remains intact for journey management and updates.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250199929A1On-device journey execution
Publication Date: 2025.06.19 ADOBE INC
  • US20250199929A1 patent drawing
  • US20250199929A1 patent drawing
  • US20250199929A1 patent drawing

AI summary

Methods and systems are provided for on-device journey execution. In embodiments described herein, a selection to publish a journey on a device is received. A representation of the journey is communicated from a server to the device over a network to store the journey locally on the device. At least a portion of the journey is executed on the device using the journey stored locally on the device.