In a conventional media player appliance, various applications are displayed on a display screen. Given the boom in digital video, music, and other content a large number of applications may be displayed. However, the user may only use a limited number of applications most of the time. This may be problematic if there are a large number of applications. In such a case, the user may be unable to easily locate and start a desired application.
The features and advantages of the present embodiments will become more apparent from the detailed description set forth below when taken in conjunction with the drawings, wherein:
In an embodiment, a media player appliance 102 comprises, for example, a streaming media player, a cable box, a network access storage (“NAS”) device, a direct access storage (“DAS”) device, or other electronic device which may store and run an application. The media player appliance 102 can be connected, for example, to a display unit 104 such as a television, a monitor, or other device which may display the application run by the media player appliance 102. Furthermore, the application may be stored locally in the media player appliance 102, or remotely, on a remote storage site. In an embodiment, the media player appliance may run the application from the remote storage site. In an embodiment, when the media player appliance 102 comprises the streaming media player, the streaming media player is configured to stream media from an external source and to display the streamed media on the display unit 104. In an embodiment, the media player appliance 102 is configured to be an application specific media player appliance 102. For example, the media player appliance 102 can be configured to automatically start an application during startup of the media player appliance 102. In an embodiment, the media player appliance 102 may also utilize other applications in addition to the application which is automatically started when the media player appliance 102 starts up.
In an embodiment, the media player appliance 102 can receive inputs from the remote control device 110. Furthermore, in an embodiment, the remote control device 110 may be wirelessly connected to the media player appliance 102. However, in an embodiment, the remote control device 110 may also be connected to the media player appliance 102 through a cable. In an embodiment, the media player appliance 102 comprises the remote control device 110.
In an embodiment, the remote control device 110 comprises a limited-input control device. For example, the remote control device 110 may not comprise a separate button for each of the letters of the alphabet and may require for example one or more depressions of a button within a predetermined period of time to provide an input for a letter of the alphabet. In an embodiment, the limited-input control device lacks a QWERTY keyboard. In an embodiment, the remote control device 110 comprises a mobile device comprising an application installed on the mobile device, which allows the mobile device to provide inputs to the media player appliance 102.
In some embodiments, the remote control device 110 is shown in
In an embodiment, the transmitter 802 is configured to transmit signals from the remote control device 110 to the media player appliance 102. In an embodiment, the transmitter 802 comprises an infrared transmitter. In an embodiment, the power button 804 is configured to indicate to the media player appliance 102 to start up or shut down. In an embodiment, the home button 806 is configured to indicate to the media player appliance 102 that a home screen in a user interface should be displayed on the display unit 104. In an embodiment, the navigation buttons 808 is configured to indicate to the media player appliance 102 how to navigate through various items or options presented by the media player appliance 102. In an embodiment, the enter button 810 is configured to indicate to the media player appliance 102 that an item or option is selected.
In an embodiment, the media buttons 812 are configured to indicated to the media player appliance 102 how to play a media. In an embodiment, the back button 814 is configured to indicate to the media player appliance 102 that the media player appliance 102 should go back to a previous option or screen. In an embodiment, the option button 816 is configured to indicate to the media player appliance 102 that available options should be displayed on the display unit 104. In an embodiment, the search button 818 is configured to indicate to the media player appliance 102 that a search mode should be displayed on the display unit 104. In an embodiment, the eject button 820 is configured to indicate to the media player appliance 102 that the media player appliance 102 should be configured for safe removal of an attached storage device.
In an embodiment shown in
In an embodiment, the next page button 822a is configured to indicate to the media player appliance 102 that a next page should be displayed. In an embodiment, the previous page button 822b is configured to indicate to the media player appliance 102 that a previous page should be displayed. In an embodiment, the mute button 824 is configured to indicate to the media player appliance 102 to switch between muting and unmuting the sounds. In an embodiment, the setup button 826 is configured to indicate to the media player appliance 102 that a setup screen should be displayed.
In an embodiment, the assignable buttons 828 are configured to be assigned by the user to indicate to the media player appliance 102 that a function should be utilized or an application should be started. In an embodiment, the number buttons 830 are configured to indicate to the media player appliance 102 numerical values. However, in an embodiment, the number buttons 830 are also configured to indicate to the media player alphanumerical values. In an embodiment, the number buttons 830 may indicate to the media player 102 alphabetical values by depressing the number buttons 830 one or more times to achieve a desired alphabetical value.
Referring back to
In addition, the communications interface 112 can communicate with the application provider 108a indirectly, such as when the application provider 108a is connected to a network 106. The network 106 can comprise, for example, a local area network (“LAN”), a wide area network (“WAN”), wireless networks, cellular networks, the Internet, a cable network, or other types of networks which can provide access to the application providers 108. In such a case, the communications interface 112 can connect to the network 106 to communicate with the application provider 108a.
In an embodiment, the communications interface 112 allows for the media player appliance 102 to access the one or more application providers 108. In an embodiment, the communications interface 112 is also configured to receive input from the remote control device 110. In an embodiment, the communications interface 112 comprises a network interface controller, Wi-Fi interface, a universal serial bus (“USB”) port, a coaxial cable port, or other ports which may allow the media player appliance 102 to access the one or more application providers 108. In an embodiment, the communications interface 112 also allows the media player appliance 102 to access one or more content providers which can provide content for the media player appliance.
In an embodiment, the video output 118 is configured to connect to the display unit 104 and provide images or video to the display unit 104 so that the video or images can be displayed on the display unit 104. In an embodiment, the display unit 104 comprises a television, a monitor, or other device which may display the applications stored and run by the media player appliance 102. In an embodiment, the display unit 104 may also display content stored and played by the media player appliance 102.
In an embodiment, the memory 116 comprises at least one of a solid state memory or a magnetic rotating disk. Furthermore, the memory 116 comprises a volatile or a non-volatile memory. In an embodiment, the memory 116 is configured to store data on the media player appliance 102.
While the description herein refers to solid state memory generally, it is understood that solid state memory may comprise one or more of various types of solid state non-volatile memory devices such as flash integrated circuits, Chalcogenide RAM (C-RAM), Phase Change Memory (PC-RAM or PRAM), Programmable Metallization Cell RAM (PMC-RAM or PMCm), Ovonic Unified Memory (OUM), Resistance RAM (RRAM), NAND memory (e.g., single-level cell (SLC) memory, multi-level cell (MLC) memory, or any combination thereof), NOR memory, EEPROM, Ferroelectric Memory (FeRAM), Magnetoresistive RAM (MRAM), other discrete NVM (non-volatile memory) chips, or any combination thereof.
In the embodiment shown in
In the embodiment shown in
In an embodiment, the memory 116 also stores a user interface definition 216. The user interface definition 216 comprises information for displaying a user interface 302 as shown in the embodiment in
In an embodiment, the memory optionally stores shortcut definitions 218. The shortcut definitions 218 correspond to shortcuts which may be displayed on the user interface 302. In an embodiment, the shortcuts correspond to applications or content. When a shortcut is clicked on by a user, such as through the remote control device 110, the media player appliance 102 can start the application or play the content corresponding to the shortcut.
For example, to select an application to start, a user can move around a cursor in the user interface 302 by utilizing for example, the navigation buttons 808 (
In an embodiment, the memory 116 can also store a configuration file 220. In an embodiment, the configuration file 220 need not be stored in the memory 116, but instead, can be stored remotely such as on a server or other memory location which is accessible by the controller 114. In an embodiment, the configuration file 220 designates which application should be automatically started when the media player appliance 102 is starting up. In an embodiment, the configuration file comprises a startup file which can be automatically loaded when the media player appliance 102 starts up. In an embodiment the startup file comprises a database, script, or any combination thereof.
In an embodiment, to designate the application to automatically start, a user can activate a button such as the option button 816 (
In an embodiment, an application can be automatically started based on a process shown in
In an embodiment, the confirmation can include a graphical indication on an application icon that the selected application is set to auto run in the configuration file. In the embodiment shown in
Optionally, the controller 114 can also perform a process shown in
In block S1008, the controller 114 receives an indication from the remote control device 110 that the selected application is not designated to automatically start when the media player appliance 102 is starting up. For example, to designate the application to not automatically start, a user can activate a button such as the option button 816 (
In an embodiment the user can select the option 308, such as through the navigation buttons 808 and the enter button 810 in the remote control device 110 (
In block S1010, the controller 114 updates the configuration file 220 to remove the selected application from the configuration file 220.
In an embodiment, an application can be started based on a process disclosed in
In an embodiment, the configuration file 220 corresponds to user account information for a user account. Thus, different user accounts may have different configuration files 220. The user accounts may comprise a variety of user account information such as the identity of the user account, authentication information, or other types of information. Therefore, when the media player appliance 102 is started, it may request that the user log into the media player appliance 102 with user account information. In an embodiment, logging into the media player appliance with the user account information may require that the user authenticate the user account through a username, password, biometrics, other means of identification, or any combination thereof. In an embodiment, the biometrics comprises fingerprint information, facial recognition information, retina information, or other types of biological information.
In an embodiment, when the user has logged into the media player appliance 102 with the user account information, the controller can retrieve the configuration file 220 corresponding to the user account information and automatically start the application designated in the configuration file 220 which corresponds to the user account information. In an embodiment, user account information may be stored in the memory 116 in the media player appliance 102 or in a remote memory that is accessible by the media player appliance 102.
In an embodiment, the user account information may also comprise information for a user interface configuration. In an embodiment, the user interface configuration may be part of the user interface definition 216 (
For example, the user interface configuration may indicate the order in which applications are displayed. Thus, more popular or desirable applications may be displayed before less popular or less desirable applications. In an embodiment, the user interface configuration may indicate that certain applications should always be displayed on a first page of the user interface 302. For example, certain applications may be pinned to the first page of the user interface 302.
Those of ordinary skill would appreciate that the various illustrative logical blocks, modules, and algorithm parts described in connection with the examples disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. Furthermore, the embodiments can also be embodied on a non-transitory machine readable medium causing a processor or computer to perform or execute certain functions.
To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and process parts have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed apparatus and methods.
The parts of a method or algorithm described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The parts of the method or algorithm may also be performed in an alternate order from those provided in the examples. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, an optical disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuit (ASIC).
The previous description of the disclosed examples is provided to enable any person of ordinary skill in the art to make or use the disclosed methods and apparatus. Various modifications to these examples will be readily apparent to those skilled in the art, and the principles defined herein may be applied to other examples without departing from the spirit or scope of the disclosed method and apparatus. The described embodiments are to be considered in all respects only as illustrative and not restrictive and the scope of the disclosure is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
This application claims the benefit of U.S. Provisional Application No. 61/859,747, filed on Jul. 29, 2013, entitled “AUTO RUN OF APPLICATIONS AT START UP FOR MEDIA PLAYER,” which is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
6675300 | Jung | Jan 2004 | B1 |
7005966 | Leman | Feb 2006 | B1 |
7409569 | Illowsky et al. | Aug 2008 | B2 |
7454542 | Illowsky et al. | Nov 2008 | B2 |
7571346 | Illowsky et al. | Aug 2009 | B2 |
7596227 | Illowsky et al. | Sep 2009 | B2 |
7600252 | Illowsky et al. | Oct 2009 | B2 |
7613881 | Illowsky et al. | Nov 2009 | B2 |
7703073 | Illowsky et al. | Apr 2010 | B2 |
7712111 | Illowsky et al. | May 2010 | B2 |
7730482 | Illowsky et al. | Jun 2010 | B2 |
7747980 | Illowsky et al. | Jun 2010 | B2 |
7761863 | Illowsky et al. | Jul 2010 | B2 |
7788663 | Illowsky et al. | Aug 2010 | B2 |
7831752 | Illowsky et al. | Nov 2010 | B2 |
8327286 | Deutsch | Dec 2012 | B2 |
8516383 | Bryant | Aug 2013 | B2 |
20030140120 | Hartman | Jul 2003 | A1 |
20040260956 | Pagan | Dec 2004 | A1 |
20050026700 | Blanco | Feb 2005 | A1 |
20050251806 | Auslander et al. | Nov 2005 | A1 |
20050289264 | Illowsky et al. | Dec 2005 | A1 |
20050289265 | Illowsky et al. | Dec 2005 | A1 |
20050289266 | Illowsky et al. | Dec 2005 | A1 |
20050289383 | Illowsky et al. | Dec 2005 | A1 |
20050289508 | Illowsky et al. | Dec 2005 | A1 |
20050289509 | Illowsky et al. | Dec 2005 | A1 |
20050289510 | Illowsky et al. | Dec 2005 | A1 |
20050289527 | Illowsky et al. | Dec 2005 | A1 |
20050289531 | Illowsky et al. | Dec 2005 | A1 |
20050289558 | Illowsky et al. | Dec 2005 | A1 |
20050289559 | Illowsky et al. | Dec 2005 | A1 |
20060005193 | Illowsky et al. | Jan 2006 | A1 |
20060005205 | Illowsky et al. | Jan 2006 | A1 |
20060010453 | Illowsky et al. | Jan 2006 | A1 |
20060015665 | Illowsky et al. | Jan 2006 | A1 |
20060015936 | Illowsky et al. | Jan 2006 | A1 |
20060015937 | Illowsky et al. | Jan 2006 | A1 |
20060020912 | Illowsky et al. | Jan 2006 | A1 |
20060026305 | Illowsky et al. | Feb 2006 | A1 |
20060026588 | Illowsky et al. | Feb 2006 | A1 |
20060149955 | Velhal et al. | Jul 2006 | A1 |
20060206882 | Illowsky et al. | Sep 2006 | A1 |
20070143768 | Inami et al. | Jun 2007 | A1 |
20070186188 | Harris | Aug 2007 | A1 |
20080113789 | Canessa et al. | May 2008 | A1 |
20080171600 | Ostergren | Jul 2008 | A1 |
20090031037 | Mendell et al. | Jan 2009 | A1 |
20090063837 | Shayer et al. | Mar 2009 | A1 |
20090113088 | Illowsky et al. | Apr 2009 | A1 |
20090178126 | Du et al. | Jul 2009 | A1 |
20090276618 | Madjlessi | Nov 2009 | A1 |
20100157989 | Krzyzanowski et al. | Jun 2010 | A1 |
20100157990 | Krzyzanowski et al. | Jun 2010 | A1 |
20100159898 | Krzyzanowski et al. | Jun 2010 | A1 |
20100205559 | Rose | Aug 2010 | A1 |
20100293365 | Tandon | Nov 2010 | A1 |
20110004749 | Bennetts et al. | Jan 2011 | A1 |
20110047288 | Sakano | Feb 2011 | A1 |
20110105182 | Sant et al. | May 2011 | A1 |
20110302531 | Takushima | Dec 2011 | A1 |
20110305435 | Tanaka et al. | Dec 2011 | A1 |
20120032945 | Dare et al. | Feb 2012 | A1 |
20120036220 | Dare et al. | Feb 2012 | A1 |
20120036245 | Dare et al. | Feb 2012 | A1 |
20120036440 | Dare et al. | Feb 2012 | A1 |
20120036442 | Dare et al. | Feb 2012 | A1 |
20120036552 | Dare et al. | Feb 2012 | A1 |
20120137282 | Illowsky et al. | May 2012 | A1 |
20120284673 | Lamb | Nov 2012 | A1 |
20130311762 | Bank | Nov 2013 | A1 |
20140215248 | Cheng et al. | Jul 2014 | A1 |
Entry |
---|
Faaborg, “User Experience Design at Mozilla”, May 11, 2009, pp. 1-7, https://blog.mozilla.org/faaborg/2009/05/11/critical-warning/. |
Number | Date | Country | |
---|---|---|---|
61859747 | Jul 2013 | US |