Seamless Service Server for Cross-Device Application Continuity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users face inconvenience when switching between devices as they need to re-execute applications to continue content consumption, lacking seamless service continuity.

Innovation Solution

A method and system that allow seamless service by transmitting history information and seamless service data between devices, enabling continuous execution of applications across devices through a seamless service providing server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a user switches from one device to another device, then the user can use different electronic devices for various purposes, but the user must re-execute applications which interrupts content consumption continuity

Engineering Contradiction:
Improvedevice switching capabilityVSAvoidapplication re-execution time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by storing execution history information (including application state, buffer status, and playback position) before the user switches devices. When the user requests seamless service on a new device, the pre-stored history information is rapidly retrieved and used to restore the application state immediately, eliminating the time loss associated with re-executing applications.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A seamless service providing server acts as an intermediary between multiple user devices. The server receives execution history from one device, processes it to generate seamless service data, and delivers it to the target device. This intermediary mechanism enables state transfer across devices without requiring the user to manually re-execute applications, thus resolving the contradiction between device versatility and time loss.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If application execution history is stored and transferred between devices, then seamless service continuity is achieved, but system complexity increases due to additional data management requirements

Engineering Contradiction:
Improveservice continuityVSAvoiddata management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the complex data management functionality from individual user devices and relocates it to a dedicated seamless service providing server. The server handles the storage, processing, and management of execution history information and seamless service data, while user devices only need to send requests and receive processed data. This extraction reduces device complexity while maintaining service continuity reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The seamless service providing server serves as an intermediary that manages the complexity of data storage and retrieval. Instead of each device managing its own execution history and coordinating with other devices, the central server consolidates these management tasks. It receives execution history from various devices, generates appropriate seamless service data, and delivers it to requesting devices, thereby simplifying the overall system architecture while ensuring reliable service continuity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8977246B2Method and system for providing seamless service
Publication Date: 2015.03.10 KT CORP
  • US8977246B2 patent drawing
  • US8977246B2 patent drawing
  • US8977246B2 patent drawing

AI summary

There is provided a method and a system of providing a seamless service. The method includes receiving seamless service application information from a first device; receiving, from a second device, history information of at least one application executed by the second device; receiving a seamless service request from the first device; generating seamless service data for the first device, in response to the request, based on the received seamless service application information and the received history information; and transmitting the generated seamless service data to the first device, wherein the first device executes at least one seamless service application based on the transmitted seamless service data.