Edge Cache Server for Shared Device Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The speed of content download from a network server to a client device is limited by bandwidth, and network servers may be unavailable, leading to delays in accessing digital content, especially in shared device environments where multiple users require rapid access to personalized data.

Innovation Solution

Implementing edge cache servers that establish server affinity with client devices on a local area network, allowing for localized storage and rapid data transfer, even when the primary server is unavailable, by caching user data and directing future transactions to the edge cache server rather than cloud storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If data is transferred from a network server to a client device, then the client device can access digital content, but the download speed is limited by network server bandwidth and may be delayed when the server is unavailable

Engineering Contradiction:
Improvedata access speedVSAvoidserver availability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The edge cache server performs preliminary actions by caching digital content locally before it is requested by client devices. This allows the cached content to be immediately available when requested, eliminating the need to wait for server response and improving both speed and reliability of data access.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The edge cache server acts as an intermediary between the network server and client devices. It receives content from the server, stores it locally, and serves it to client devices, thereby mediating the data transfer process and reducing direct dependency on server availability and bandwidth constraints.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If an edge cache server caches digital content locally to speed up access, then data retrieval is faster, but network bandwidth consumption increases due to repeated downloads

Engineering Contradiction:
Improvecontent access speedVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

The edge cache server performs preliminary caching of digital content that is likely to be requested by client devices. By having this content pre-loaded and stored locally, the system eliminates the need for repeated downloads, thereby reducing network bandwidth consumption while maintaining fast access speeds.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If multiple users share a client device and require rapid access to personalized data, then device utilization is improved, but access speed decreases due to cloud storage dependencies

Engineering Contradiction:
Improveshared device personalizationVSAvoiddata access speed
Core Design Contradiction:
Adaptability or versatilityVSSpeed

Solution Approach 1:

The edge cache server performs preliminary caching of personalized data for multiple users who share a client device. By pre-loading user-specific content and maintaining it in local cache, the system enables rapid access to personalized data without requiring repeated connections to cloud storage, thereby improving both adaptability and access speed.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11412060B2Edge caching shared devices
Publication Date: 2022.08.09 APPLE INC
  • US11412060B2 patent drawing
  • US11412060B2 patent drawing
  • US11412060B2 patent drawing

AI summary

Disclosed are systems, methods, devices and non-transitory, computer-readable storage media for edge caching shared devices. In some implementations, a method comprises: receiving, by an edge cache server on a local area network (LAN) from a client device, a locate server request; determining, by the edge cache server, that the edge cache server has established server affinity with a user of the client device; sending, by the edge cache server to the client device, affinity data corresponding to the user; receiving, by the edge cache server from the client device, a request to transfer user data corresponding to the user; determining, by the edge cache server, that a new version of the user data is available; downloading, by the edge cache server, the new version of the user data; and sending, by the edge cache server to the client device, the new version of the user data.