Local Service Node Proactive Data Migration for Vehicle Connectivity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile communication devices experience poor user experience and connectivity issues when running distributed applications over unreliable communication links, particularly in scenarios like vehicle travel where connectivity degrades predictably.

Innovation Solution

A central node proactively migrates data and application modules from a remote service node to a local service node on the vehicle, leveraging a-priori known circumstances to ensure timely migration before connectivity degradation, using cloud computing resources and short-range links for reliable access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If data and application modules are accessed remotely over unreliable communication links, then device complexity is reduced, but connectivity reliability deteriorates

Engineering Contradiction:
Improvedevice complexityVSAvoidconnectivity reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system proactively migrates data and application modules from remote service nodes to local service nodes before connectivity degradation occurs. The central node predicts communication link reliability and initiates migration when reliability falls below a threshold, ensuring services remain accessible locally even when remote connectivity is lost.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A local service node is introduced as an intermediary between the mobile communication device and the remote service node. This local node caches data and application modules locally, allowing the device to access services through the local node when remote connectivity is unavailable, thus mediating the connection and improving reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If data and application modules are migrated to local service nodes, then connectivity reliability is improved, but device complexity increases

Engineering Contradiction:
Improveconnectivity reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The local service node autonomously manages data and application module caching, migration, and synchronization without requiring complex device-side logic. The node self-determines when to migrate content based on predicted connectivity and automatically synchronizes with remote nodes when connectivity is available, reducing the complexity burden on the mobile device.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The local service node is designed as a multi-functional component that can cache data, host application modules, manage synchronization, and predict connectivity patterns. This universal node handles multiple responsibilities that would otherwise require complex coordination between device and network, consolidating functionality and simplifying the overall system architecture.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Stability of the object's composition

If proactive migration is performed before connectivity degradation, then service continuity is improved, but loss of time increases

Engineering Contradiction:
Improveservice continuityVSAvoidmigration time
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

The system migrates only the necessary data and application modules to the local service node rather than all content. The central node determines which specific modules and data are required based on service requirements and predicted connectivity patterns, performing partial migration to minimize time consumption while ensuring service continuity for critical functions.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system dynamically adjusts migration parameters such as the threshold for initiating migration, the selection of which modules to migrate, and the timing of synchronization operations. By changing these parameters based on predicted connectivity patterns and service priorities, the system optimizes the balance between service continuity and migration time consumption.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP3395044B1Local service node improving the user experience
Publication Date: 2021.08.25 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP3395044B1 patent drawingFigure 1
  • EP3395044B1 patent drawingFigure 2
  • EP3395044B1 patent drawingFigure 3

AI summary

A method in a central node, for migration of data and/or application modules from a remote service node to a local service node residing in a vehicle, the method comprising determining that a first condition is met that indicates a request to migrate data and/or application modules from a remote service node to a local service node and initiating a first migration of data and/or application modules based on whether the first condition is met.