Current systems and methods that perform synchronization of content items between computers and portable storage or playback devices have certain disadvantages. For example, one difficulty is the length of the synchronization procedure. Synchronization procedures may be delayed, e.g., by bandwidth limitations for the input/output process as determined by the USB or other connection protocol. A similar limitation pertains to the processor speed. For example, if a file requires conversion before being transferred from a computer to a portable player, the conversion slows and/or delays the synchronization process considerably. A related limitation concerns when a file requires download to a local personal computer prior to synchronization on a device, which is often the case with digital music listed in a local catalog but actually stored on an internet web store for download on-demand. The download requires completion before the file can be transferred.
Another type of limitation is seen when a user's media content library exceeds the storage capacity of the portable player. Current systems for choosing which items to synchronize, and which to avoid, including smart playlists (i.e., rule-based selection mechanisms like “All songs in my library where genre does not equal ‘Christmas’”), are generally complicated and confusing to many users.
A further type of limitation relates to the cumbersome nature of current synchronization procedures, i.e., a user must indicate or build a list of desired changes, e.g., items to synchronize, and then must start the procedure. As such procedures only commence upon user command, synchronization procedures are limited to occurring only at user-specified times or at the time of initial device connection. Some systems have allowed for a degree of spontaneous synchronization—synchronization may begin for some content types as soon as new content requiring synchronization is detected. In these systems, however, any currently-running synchronization must be completed or aborted before initiating a new synchronization, resulting in a less-than-optimum method.
Yet another type of limitation relates to the synchronization process itself: users generally need to have content items to be synchronized stored on their computer in some local location. Thus, content items generally occupy valuable storage space on a user system.
The arrangement improves the efficiency of the synchronization process. The same ensures that synchronizations of large quantities of content can be completed with a minimum of delay. This is accomplished in various ways. One way is to prioritize the various tasks that are to be performed prior to synchronization. Another way is to initiate dependent tasks. Yet another way is to allow other content to synchronize in the meantime, increasing the efficiency of the limited transmission bandwidth.
In another example, a method is provided which allows a user to select content items for synchronization in simple and intuitive ways, using natural organizational units of given types of media, here termed “containers”.
In another example, a method is provided which performs automatic or “live” synchronization, in which a user's library is continually monitored for changes to the set of content the user has indicated should be synchronized, e.g., containers. Synchronization with the portable device then occurs immediately, and continuously, until the synchronization engine determines that there are no items left to be synchronized. If a synchronization is already in-process, any new synchronization tasks may be added to, or removed from, the currently-synchronizing work flow, obviating the need for a separate synchronization process to commence.
In another example, a method is provided that allows content to be placed on a portable player without the intermediate step of having to place content (and occupy storage space within) a user media content library, such as on a user's personal computer. For example, using this arrangement, a user may place a CD of music onto a portable player without having to store the “ripped” music on the user's computer, which saves memory or hard disk space.
This Summary is provided to introduce a selection of concepts in a simplified form. The concepts are further described in the Detailed Description section. Elements or steps other than those described in this Summary are possible, and no element or step is necessarily required. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended for use as an aid in determining the scope of the claimed subject matter. The claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.
The following definitions are used in this description.
“Content items” (elements 120, 120′, and 120″ of
A “content playback device” (element 200 of
A “content management device” (element 100 of
“Synchronization” (alternatively elements 600 or 700 of
“Online service” (e.g., element 310 of
A “playlist” is a collection of media files to be played back in a given order as determined by the user.
A “container” (elements 102, 102′, 104, 104′, 106, and 106′ of
Finally, a “container” may be “associated” with a content playback device when the same is the subject of an operation that transfers, copies, or otherwise causes the content items in the container to be placed onto the content playback device. This may be performed by a simple drag-and-drop operation or by any number of other such similar procedures.
Turning to the drawings, where like numerals designate like components or steps,
Using the metadata or other such information, one or more containers 102, 104, 106 (corresponding to containers 1, 2, and 3) may be defined, created, or generated. The containers 102, 104, 106 may be formed by the action of a filter on a content media library 130, and may be formed automatically or in a custom fashion. The containers may generally include content items in a “natural” organization unit. For example, one container may include all songs by a particular artist, or all songs from an album. Another container may include all shows from a television series, or all shows for that series from a given season. Another container may include all podcasts from a chosen publisher. Another container may include all songs of a given genre.
The content management application may automatically create numerous such containers according to a predefined scheme, and the scheme may be updated periodically. For example, containers may be created that correspond to, for music, any and all albums, any and all artists, and any and all genres represented.
Custom containers, which may be formed on the basis of user input, may be created in either a passive or an active sense. In the former, containers may be formed such as “most played”. In the latter, containers may be formed such as “highest rated”. Custom containers may also incorporate complicated filtering schemes, e.g., all alternative music of the 1980s from British bands.
The content management device 100 may be connected to a network 300 via a wired link 114 or a wireless link 108. The content playback device 200 may also be connected to the network 300 via a link; a wireless link 112 is shown, although a wired link is also possible (not shown). An exemplary online service 310 is shown within the network, the same generally includes a set of content items 120″, which the user may purchase and download either immediately or perform a download-on-demand later, at a time of the user's convenience.
First, an initial optional step is shown of creating a media library 130 (step 400). In many cases, a media library will already have been created.
A next step is to create containers (step 450). As noted above, containers may be generated in a number of ways, such as by the action of a filter on the media library 130. In more detail, as shown in
Referring back to
A content playback device or portable media player icon 480 is displayed in
By clicking on the content playback device icon, or via an analogous procedure, the content items on the content playback device may be displayed. Referring to
A number of containers 484-488 are also displayed on the left-hand-side of the interface of
Following the association operation, a synchronization step may occur. The arrangement provide several types of synchronization operations, which may be employed separately or in combination.
In one type of synchronization operation, a live or automatic synchronization of containers may occur (step 600). Referring to
Live synchronization may be accomplished in at least one of three ways, which may also occur in various combinations. In one way, a synchronization operation may simply occur periodically (step 602). In this way, synchronization occurs every few minutes or on any other schedule as determined by the content management device or user. In a second way, a synchronization operation occurs whenever the content management device 100 detects a change in a container 102 (step 604). For example, if a content item 120 is added to a container 102, and the container 102 is associated with the content playback device 200, then a synchronization operation may occur as soon as is feasible, e.g., immediately or soon thereafter, without user initiation. In the same way, if a drag-and-drop operation is performed on a container, again a synchronization operation may occur as soon as is feasible.
In a third way, and referring in addition to
In another type of synchronization operation, and referring to
As tasks are added to a work queue, the synchronization engine reviews them and determines when an action is capable of being immediately performed, where “immediately performed” means, for example, that a transfer can occur without any prerequisite tasks first being performed on the content item. If it is, the action is performed and a pointer moves to the next task. If the action is not capable of being immediately performed, then the synchronization engine queues a new task of higher priority that is necessary before the initial action can be performed, i.e., a prerequisite task. The pointer is reset to, e.g., the beginning of the queue. Once either of the tasks is performed, the pointer moves to the next item and repeats the process. If resources are available to take action on the next task, the next task is performed; otherwise, it moves on to the next item in the queue. In this way, increased efficiency is obtained in use of limited I/O bandwidth and/or CPU capabilities.
In certain versions of the above arrangement, it is noted that the entire work queue may be reviewed or re-evaluated to ensure that the highest priority tasks are performed first, and that the performance of all the tasks is done in a manner to minimize the overall synchronization time.
Referring in particular to the exemplary
In the example of
As the synchronization engine 110 reaches content item A (element 711), the same determines that a conversion is necessary before the transfer of the item 711 can occur. Consequently a conversion task is queued ahead of the transfer of the item 711, and this transfer is marked as dependent on the conversion. In
The transfer of content item B (item 712) may then begin; however, the synchronization engine 110 determines that a download is necessary before the transfer of the item 712 can occur. Consequently a download task is queued ahead of the transfer of the item 712, and this transfer is marked as dependent on the conversion. In
The transfer of content item C (item 713) may then begin; however, the synchronization engine 110 determines that a download is necessary before the transfer of the item 713 can occur. Consequently a download task is queued ahead of the transfer of the item 713, and this transfer is marked as dependent on the conversion. In
The transfer of content item D (item 714) may then begin; in this case, the transfer of the item 714 can begin immediately, as no items are currently being transferred by the transfer module 702 and the item 714 requires no pre-processing.
At this step in the sequence four tasks are happening contemporaneously. When the conversion of content item A, or the download of content item B or C, is completed, their respective transfers are re-attempted. It may be found that yet another task is prerequisite to the transfer, e.g., it may be that content item B or C has to be converted, in which case another prerequisite task is queued ahead of the same's transfer.
If a content item E (not shown) were now introduced to the queue but required conversion, its conversion would be queued ahead of its transfer, but since there are no free conversion slots, the conversion itself would be delayed until a free resource was available. Similarly, if two more downloads were required, the first would start immediately while the second would be delayed until one of the three active downloads completed.
In alternative arrangements, the availability of resources (e.g., for conversion, download, etc.) may be self-adjusting based on past experience, network utilization, etc.
In another aspect of the method and user interface, as may be seen by comparing
In another aspect of the arrangement, content items 120 may be synchronized to the content playback device 200 without adding the content item files to the user's media library 130. In particular, users may desire to place content items 120 directly on a content playback device 200 as part of media library 130′ but without occupying space in their main media library 130. For example, many news items, lectures, podcasts, are only listened to once, and thus permanent storage is unnecessary and may be undesirable. Another example may be a data CD full of music files or the like, which are archived and need not necessarily be stored on the user's hard drive. Moreover, a data CD full of music files is not always available in the same way as a hard drive generally is. This method is further intended to encompass content items stored in an online store and downloaded on demand directly to a content playback device. In this way, users may, e.g., listen to an album prior to downloading the same onto their hard drive.
In this method, the user may copy content from a normally-offline location, e.g., external drive 125, directly onto their content playback device. This allows the content items to be transferred but to not clutter the user's media library 130. In one implementation, metadata associated with the transferred files may still be maintained in the media library 130, allowing other functionality associated with the synchronization engine to apply to those content items, e.g., automatic content management such as ongoing metadata updates if the original files are altered in some way.
Referring to
In any case, and referring back to
Thus, it can be seen that the arrangements described enable a convenient way to synchronize a content management device with a content playback device.
As shown, operating environment 730 includes processor 732, computer-readable media 734, and computer-executable instructions 736. One or more internal buses 740 may be used to carry data, addresses, control signals, and other information within, to, or from operating environment 730 or elements thereof.
Processor 732, which may be a real or a virtual processor, controls functions of the operating environment by executing computer-executable instructions 736. The processor may execute instructions at the assembly, compiled, or machine-level to perform a particular process.
Computer-readable media 734 may represent any number and combination of local or remote devices, in any form, now known or later developed, capable of recording, storing, or transmitting computer-readable data, such as the above-noted computer-executable instructions 736, including user interface functions 738 and synchronization engine 110, and content items 120. In particular, the computer-readable media 734 may be, or may include, a semiconductor memory (such as a read only memory (“ROM”), any type of programmable ROM (“PROM”), a random access memory (“RAM”), or a flash memory, for example); a magnetic storage device (such as a floppy disk drive, a hard disk drive, a magnetic drum, a magnetic tape, or a magneto-optical disk); an optical storage device (such as any type of compact disk or digital versatile disk); a bubble memory; a cache memory; a core memory; a holographic memory; a memory stick; a paper tape; a punch card; or any combination thereof. The computer-readable media may also include transmission media and data associated therewith. Examples of transmission media/data include, but are not limited to, data embodied in any form of wireline or wireless transmission, such as packetized or non-packetized data carried by a modulated carrier signal.
Computer-executable instructions 736 represent any signal processing methods or stored instructions. Generally, computer-executable instructions 736 are implemented as software components according to well-known practices for component-based software development, and encoded in computer-readable media. Computer programs may be combined or distributed in various ways. Computer-executable instructions 736, however, are not limited to implementation by any specific embodiments of computer programs, and in other instances may be implemented by, or executed in, hardware, software, firmware, or any combination thereof.
Input interface(s) 742 are any now known or later developed physical or logical elements that facilitate receipt of input to operating environment 730.
Output interface(s) 744 are any now known or later developed physical or logical elements that facilitate provisioning of output from operating environment 730.
Network interface(s) 746 represent one or more physical or logical elements, such as connectivity devices or computer-executable instructions, which enable communication between operating environment 730 and external devices or services, via one or more protocols or techniques. Such communication may be, but is not necessarily, client-server type communication or peer-to-peer communication. Information received at a given network interface may traverse one or more layers of a communication protocol stack.
Specialized hardware 748 represents any hardware or firmware that implements functions of operating environment 730. Examples of specialized hardware include encoder/decoders decrypters, application-specific integrated circuits, clocks, and the like.
The methods shown and described above may be implemented in one or more general, multi-purpose, or single-purpose processors. Unless specifically stated, the methods described herein are not constrained to a particular order or sequence. In addition, some of the described methods or elements thereof can occur or be performed concurrently.
Functions/components described herein as being computer programs are not limited to implementation by any specific embodiments of computer programs. Rather, such functions/components are processes that convey or transform data, and may generally be implemented by, or executed in, hardware, software, firmware, or any combination thereof.
It will be appreciated that particular configurations of the operating environment may include fewer, more, or different components or functions than those described. In addition, functional components of the operating environment may be implemented by one or more devices, which are co-located or remotely located, in a variety of ways.
Although the subject matter herein has been described in language specific to structural features and/or methodological acts, it is also to be understood that the subject matter defined in the claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
It will further be understood that when one element is indicated as being responsive to another element, the elements may be directly or indirectly coupled. Connections depicted herein may be logical or physical in practice to achieve a coupling or communicative interface between elements. Connections may be implemented, among other ways, as inter-process communications among software processes, or inter-machine communications among networked computers.
The word “exemplary” is used herein to mean serving as an example, instance, or illustration. Any implementation or aspect thereof described herein as “exemplary” is not necessarily to be constructed as preferred or advantageous over other implementations or aspects thereof.
As it is understood that embodiments other than the specific embodiments described above may be devised without departing from the spirit and scope of the appended claims, it is intended that the scope of the subject matter herein will be governed by the following claims.
This application is a continuation of U.S. application Ser. No. 12/031,708, filed Feb. 15, 2008, now U.S. Pat. No. 8,818,941 issued Aug. 26, 2014, entitled “ARRANGEMENT FOR SYNCHRONIZING MEDIA FILES WITH PORTABLE DEVICES” which claims the benefit of U.S. Provisional Patent Application Ser. No. 60/987,079, filed Nov. 11, 2007, entitled “Arrangement For Synchronizing Media Files With Portable Devices,” which are both incorporated herein by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
6248946 | Dwek | Jun 2001 | B1 |
6304891 | Anderson et al. | Oct 2001 | B1 |
6317797 | Clark et al. | Nov 2001 | B2 |
6446080 | Van Ryzine et al. | Sep 2002 | B1 |
6721489 | Benyamin et al. | Apr 2004 | B1 |
6959288 | Medina et al. | Oct 2005 | B1 |
7024214 | Loveland | Apr 2006 | B2 |
7096416 | Smith et al. | Aug 2006 | B1 |
7107296 | Novak et al. | Sep 2006 | B2 |
7136934 | Carter et al. | Nov 2006 | B2 |
7743019 | Shah et al. | Jun 2010 | B2 |
7790974 | Sherwani | Sep 2010 | B2 |
7858867 | Sherwani | Dec 2010 | B2 |
8150937 | Ng et al. | Apr 2012 | B2 |
8631088 | Robbin et al. | Jan 2014 | B2 |
8818941 | Kiilerich et al. | Aug 2014 | B2 |
20010041021 | Boyle et al. | Nov 2001 | A1 |
20020194309 | Carter et al. | Dec 2002 | A1 |
20030167318 | Robbin et al. | Sep 2003 | A1 |
20040125144 | Yoon | Jul 2004 | A1 |
20050114333 | Nagano et al. | May 2005 | A1 |
20050114711 | Hesselink et al. | May 2005 | A1 |
20050147130 | Hurwitz et al. | Jul 2005 | A1 |
20050187976 | Goodman | Aug 2005 | A1 |
20050234999 | Millikan et al. | Oct 2005 | A1 |
20060168351 | Ng et al. | Jul 2006 | A1 |
20060195864 | New et al. | Aug 2006 | A1 |
20060200599 | Manchester et al. | Sep 2006 | A1 |
20060227245 | Poimboeuf | Oct 2006 | A1 |
20060230349 | Novak et al. | Oct 2006 | A1 |
20060270395 | Dhawan | Nov 2006 | A1 |
20070043847 | Carter et al. | Feb 2007 | A1 |
20070050458 | Rotzoll et al. | Mar 2007 | A1 |
20070088727 | Kindig | Apr 2007 | A1 |
20070089057 | Kindig | Apr 2007 | A1 |
20070156779 | Ho et al. | Jul 2007 | A1 |
20070169087 | Fadell | Jul 2007 | A1 |
20070174520 | Moon | Jul 2007 | A1 |
20070282848 | Kiilerich | Dec 2007 | A1 |
20080022208 | Morse | Jan 2008 | A1 |
20080034126 | Baker | Feb 2008 | A1 |
20080086494 | Heller | Apr 2008 | A1 |
20080134051 | Chaney | Jun 2008 | A1 |
20080162665 | Kali | Jul 2008 | A1 |
20080168525 | Heller et al. | Jul 2008 | A1 |
20100151783 | Cohen | Jun 2010 | A1 |
Number | Date | Country |
---|---|---|
1431977 | Jun 2004 | EP |
WO 0179964 | Oct 2001 | WO |
2005119677 | Dec 2005 | WO |
WO 2005116868 | Dec 2005 | WO |
2007039589 | Apr 2007 | WO |
Entry |
---|
Tilley, et al., “Issues in Accessing Web Sites from Mobile Devices”, Proceedings of the 3rd International Workshop on Web Site Evolution. IEEE, 2001. pp. 1-8. (8 pages total). |
Blakowski, “A Media Synchronization Survey: Reference Model, Specification, and Case Studies”, 1996, IEEE. pp. 1-31. (31 pages total). |
Garnett, Jeff, “Drag-and-drop Playlists in iTunes,” The Mac Observer, Oct. 24, 2006, http://www.macobserver.com/tmo/article/Drag-and-drop—Playlists—in—iTunes/ (2 pages total). |
Number | Date | Country | |
---|---|---|---|
20140365608 A1 | Dec 2014 | US |
Number | Date | Country | |
---|---|---|---|
60987079 | Nov 2007 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12031708 | Feb 2008 | US |
Child | 14468142 | US |