Remote Media Interface Protocol for Database State Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing remote user interface protocols for portable media devices do not allow for seamless transitions between the device's interface and a remote interface, as they do not maintain the database navigation state or enable on-the-fly playlist creation and modification.
Innovation Solution
A protocol that allows accessories to cache information from portable media devices, maintain database synchronization status, and enable remote playlist management, including creation, modification, and deletion, while initializing the remote interface to match the device's state.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the accessory re-requests all database information upon each connection to the portable media device, then the information displayed in the remote user interface is always up-to-date, but the communication burden and data transmission time increase significantly
Solution Approach 1:
The accessory performs preliminary actions by caching database information during the first connection and checking for updates before full re-requests. This preliminary caching action reduces the need for complete data re-transmission during subsequent connections, thereby reducing initialization time while maintaining information accuracy through selective update checks.
Solution Approach 2:
The system implements a feedback mechanism where the accessory checks whether the database has been updated since the last connection. Based on this feedback information, the accessory intelligently decides whether to request full database information or use cached data, optimizing the balance between information accuracy and communication efficiency.
2Ease of operation
If the accessory requests complete database navigation state information upon connection, then the remote interface can restore the exact user position in the database hierarchy, but the data transmission volume and processing overhead increase
Solution Approach 1:
The invention extracts only the essential navigation state information needed to restore the user interface position, rather than transmitting the entire database structure. By taking out only the critical path information (current folder, selected item, navigation history), the system achieves interface continuity with minimal data transmission volume.
Solution Approach 2:
The system applies partial action by requesting only the necessary portion of database state information required to restore the remote interface to the correct navigation position. Instead of requesting complete database contents, it requests minimal sufficient information about the user's current location and navigation path, reducing data overhead while maintaining operational continuity.
3Ease of operation
If the remote user interface does not maintain database navigation state across connections, then the protocol complexity remains simple, but the user experience becomes discontinuous and requires re-navigation
Solution Approach 1:
The system performs preliminary action by maintaining and storing database navigation state information during the connection period. This pre-maintained state information enables seamless continuity when the user reconnects, eliminating the need for re-navigation while adding moderate protocol complexity for state management and persistence.
Data Source
AI summary
Remote user interfaces for portable media devices provided improved access by accessories to media assets and metadata stored in a database of a portable media device, enhancing a user's ability to control operation of the portable media device using a remote user interface provided by the accessory. In one example, an accessory can determine whether the database of the portable media device was updated while the portable media device was disconnected from the accessory. In a second example, an accessory can create and manage a playlist for the portable media device and can incorporate into the playlist tracks already queued for playback when the accessory connects to the portable media device. In a third example, an accessory can obtain database navigation history and initialize a database navigation interface to match the database navigation history.