Display Apparatus View History Synchronization via Cloud Server

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Display apparatuses with cloud account functionality cannot synchronize view history across multiple devices, limiting users' ability to access their complete viewing history across different logged-in devices.

Innovation Solution

A display apparatus that generates a view history record including a preset image and cloud account identifier for each video item watched, sends this record to a server, and retrieves and displays a synchronized list of view history records from the server when the user requests their view history, ensuring consistency and completeness of the viewing history across all connected devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If view history is stored locally on each display apparatus, then the device complexity is reduced and operation is simple, but the view history cannot be synchronized across multiple devices logged into the same cloud account

Engineering Contradiction:
Improveview history synchronizationVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

A server is introduced as an intermediary to store and manage view history records for cloud accounts. When a user logs in to a cloud account on a display apparatus, the view history records are synchronized from the server, enabling access to complete viewing history across multiple devices without significantly increasing local device complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

View history records are copied from the central server storage to the local display apparatus for display purposes. This allows the apparatus to show synchronized view history without permanently storing all records locally, maintaining data consistency across devices while managing storage efficiently

Inventive Principle:
Principle #26Copying

2Loss of information

If view history records are stored only locally on the display apparatus, then the loss of information is minimized for local access, but the user cannot access view history from other devices

Engineering Contradiction:
Improveview history completenessVSAvoidcross-device accessibility
Core Design Contradiction:
Loss of informationVSAdaptability or versatility

Solution Approach 1:

The server implements a universal storage system that serves multiple display apparatuses logged into the same cloud account. View history records stored on the server become accessible to all associated devices, enabling cross-device access while maintaining a single source of truth for the complete viewing history

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

Solution Approach 2:

The system implements feedback mechanisms where view history records are continuously synchronized between the server and display apparatuses. When new viewing records are generated on any device, they are automatically uploaded to the server and subsequently distributed to other devices in the cloud account, ensuring all devices have access to the complete and up-to-date view history

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11736752B2Method for displaying view history and display apparatus
Publication Date: 2023.08.22 QINGDAO HISENSE MEDIA NETWORKS CO LTD
  • US11736752B2 patent drawing
  • US11736752B2 patent drawing
  • US11736752B2 patent drawing

AI summary

The disclosure provides a display apparatus including a controller and a method for displaying view history in the display apparatus. The controller is configured to cause the display apparatus to perform: after logging in to a cloud account on the display apparatus, in response to a command for watching a first video item on the display of the display apparatus, generating a first view history record corresponding to the first video item; sending the first view history record to a server; inserting the first view history record into a first place of a second history information list; in response to receiving a command for displaying a view history interface, sending a request for view history to the server; in response to receiving first history information list, displaying preset images of first view history records included in the received first history information list on the view history interface.