Playlist Version Conflict Resolution via Superset Logic

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In cloud locker environments, version conflicts arise when a user modifies a playlist on a client device while disconnected from the cloud, leading to inconsistencies that existing distributed computing solutions cannot adequately resolve, as they are based on different assumptions regarding multiple users collaborating on the same document.

Innovation Solution

A heuristic approach is implemented to reconcile version conflicts by monitoring user-initiated changes on the client device, determining if one playlist is a superset or subset of the other, and upon reconnection, saving the superset to both the client and cloud locker while deleting the subset, or creating a new version if no clear superset-subset relationship exists.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If distributed computing solutions are used to handle version conflicts, then conflicts from multiple users collaborating on documents can be resolved, but they fail to address version conflicts arising from single users modifying playlists in cloud locker environments

Engineering Contradiction:

Improveapplicability to different conflict scenariosVSAvoideffectiveness in resolving cloud locker conflicts

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent changes the fundamental parameters of conflict resolution by shifting from user-based assumptions (multiple collaborators) to modification-based assumptions (superset-subset relationships). This allows the same distributed computing framework to handle both multi-user document conflicts and single-user playlist conflicts effectively

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

Instead of assuming conflicts arise from multiple users and applying collaboration-based resolution, the patent inverts the approach by assuming single-user modifications and applying superset-subset logic. This inversion makes the solution adaptable to cloud locker environments while maintaining reliability

Inventive Principle:

Principle #13The other way round (Inversion)

2Ease of operation

If the client device stores a subset of the music catalog and playlists locally, then offline access is enabled, but version conflicts occur when the client reconnects after making modifications

Engineering Contradiction:

Improveoffline access capabilityVSAvoiddata consistency upon reconnection

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary actions by establishing superset-subset relationships and modification tracking before conflicts occur. When the client disconnects, modifications are tracked locally; upon reconnection, the pre-established relationships enable automatic resolution without requiring user intervention, thus maintaining both offline accessibility and data consistency

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where the system continuously monitors and compares playlist versions between cloud locker and client device. Upon reconnection, feedback from the version comparison triggers automatic conflict resolution based on superset-subset relationships, ensuring data consistency while preserving offline operation capabilities

Inventive Principle:

Principle #23Feedback

3Reliability

If the server saves the superset playlist to both client and cloud locker, then data integrity is maintained, but the subset version must be deleted which may lose user-specific customizations

Engineering Contradiction:

Improvedata integrityVSAvoiduser-specific playlist customizations

Core Design Contradiction:

ReliabilityVSLoss of information

Solution Approach 1:

The patent segments playlist modifications into two categories: structural changes (additions/removals of tracks) and user-specific customizations (track ordering, playback settings). The superset-subset logic resolves structural conflicts by saving the superset, while user-specific customizations are preserved as separate metadata, preventing information loss while maintaining data integrity

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The solution nests user-specific customizations within the superset playlist structure. When conflicts are resolved by saving the superset, user customizations are embedded as nested metadata layers that remain intact, allowing the system to maintain data integrity at the playlist level while preserving user-specific information within the nested structure

Inventive Principle:

Principle #7Nested doll (Nesting)

Data Source

PatentUS8983905B2Merging playlists from multiple sources

Publication Date: 2015.03.17 APPLE INC

AI summary

The present technology resolves playlist version conflicts resulting from modifications made to a playlist version, stored on a client device and in a cloud locker, when the client device and the cloud locker are in a disconnected state. The present technology is a heuristic for determining how to resolve such version conflicts. Upon reconnection of the client and cloud locker, the server, associated with cloud locker attempts to reconcile any version discrepancies resulting from user-initiated changes. In one embodiment, when the server determines that one of the playlists on the client or server is a superset of the other, the superset is selected and saved to both the client and cloud locker, while the subset version is deleted.