PATENT DOCUMENT

Publication Number: US-8489468-B2
Application Number: US-201113005222-A
Country: US
Kind Code: B2

Title: Online purchase of digital media bundles

Abstract:
Techniques for interacting with an online media store to obtain a media asset bundle, such as a digital boxset, are disclosed. These techniques involve, for instance, browsing for a media asset bundle that includes at least one non-playable media asset, purchasing the media asset bundle, obtaining the media assets contained in the media asset bundle, determining if a presentation request has been made for a media asset in the media asset bundle, and presenting the requested media asset. Further, these techniques involve playing the media assets in a media asset bundle by selecting a media asset in the media asset bundle, determining whether the media asset is playable or non-playable, presenting the media asset using an appropriate media asset viewer if it is playable, not playing (skipping) the media asset if it is non-playable, and selecting/playing other media assets in the media asset bundle until no more media assets are available to be played.

Claims:
What is claimed is: 
     
       1. A computer-implemented method for obtaining a media asset bundle, comprising:
 (a) browsing a commerce server for a media asset bundle, wherein the media asset bundle comprises a plurality of media assets and wherein at least one of the media assets in the media asset bundle is a non-playable media asset; 
 (b) purchasing the media asset bundle; 
 (c) obtaining, at a client device, the media assets contained in the media asset bundle; 
 (d) determining by a media management application operating on the client device, if a request has been made for a media asset in the media asset bundle; 
 (e) determining by the media management application operating on the client device, whether the media asset is a playable media asset or a non-playable media asset; 
 (f) presenting the requested media asset in a playable media asset format by the media management application operating on the client device, if it is determined that the media asset is a playable media asset; and 
 (g) presenting the requested media asset in a non-playable media asset format by the media management application operating on the client device, if it is determined that the media asset is a non-playable media asset. 
 
     
     
       2. The method of  claim 1 , wherein the purchasing (b) of the media asset bundle is done at an online media store. 
     
     
       3. The method of  claim 1 , wherein the presenting (f) and (g) are restricted by digital rights management information. 
     
     
       4. The method of  claim 1 , wherein the non-playable media asset is selected from the group consisting of a portable document format (PDF) file, a graphics file, a multi-media file and a text file. 
     
     
       5. The method of  claim 4 , wherein the non-playable media asset file contains digital rights management information. 
     
     
       6. The method of  claim 4 , wherein the text file comprises embedded graphics. 
     
     
       7. The method of  claim 1 , wherein the playable media assets are selected from the group consisting of audio files and video files. 
     
     
       8. The method of  claim 7 , wherein the audio file comprises media content selected from the group consisting of a song and a spoken-word performance. 
     
     
       9. The method of  claim 6 , wherein the playable media assets are selected from the group consisting of songs, music videos, and audio books. 
     
     
       10. The method of  claim 8 , wherein the text file comprises embedded graphics. 
     
     
       11. The method of  claim 1 , wherein the presenting (g) uses at least one of a PDF viewer, a text editor, a web browser, an e-book reader, or an XML browser. 
     
     
       12. The method of  claim 11 , wherein the presenting (g) causes a media asset viewer to be spawned by the media management application. 
     
     
       13. A method for obtaining a media asset bundle, comprising:
 (a) browsing for a media asset bundle, wherein the media asset bundle comprises a plurality of media assets, wherein the plurality of media assets includes at least one media asset of a first media asset type and at least one media asset of a second media asset type; 
 (b) purchasing the media asset bundle; 
 (c) obtaining, at a client device, the media assets contained in the media asset bundle; 
 (d) determining by a media management application operating on the client device, if a request has been made for a media asset in the media asset bundle; 
 (e) determining by the media management application operating on the client device, whether the media asset is a playable media asset or a non-playable media asset; 
 (f) presenting the requested media asset in a playable media asset format by the media management application operating on the client device, if it is determined that the media asset is a playable media asset; and 
 (g) presenting the requested media asset in a non-playable media asset format by the media management application operating on the client device, if it is determined that the media asset is a non-playable media asset. 
 
     
     
       14. The method of  claim 13  , wherein the purchasing (b) of the media asset bundle is done at an online media store. 
     
     
       15. The method of  claim 13 , wherein the presenting (f) and (g) is restricted by digital rights management information. 
     
     
       16. The method of  claim 13 , wherein the non-playable media asset is selected from the group consisting of a portable document format (PDF) file, a graphics file, a multimedia file and a text file. 
     
     
       17. The method of  claim 13 , wherein the playable media asset is selected from the group consisting of audio files, video files, and graphics files. 
     
     
       18. The method of  claim 17 , wherein audio files comprise media content selected from the group consisting of songs, interviews, and spoken-word performances. 
     
     
       19. The method of  claim 17 , wherein video files comprise media content selected from the group consisting of videos and motion pictures. 
     
     
       20. The method of  claim 17 , wherein graphics files comprise media content selected from the group consisting of pictures, drawings, and text.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is a divisional application of U.S. patent application Ser. No. 11/138,004, filed May 25, 2005 now U.S. Pat. No. 7,899,714, and entitled “ONLINE PURCHASE OF DIGITAL MEDIA BUNDLES,” which is hereby incorporated herein by reference. 
     This application claims priority of U.S. Provisional Patent application No. 60/622,280, filed Oct. 25, 2004, and entitled “ONLINE PURCHASE OF DIGITAL MEDIA BUNDLES”, which is hereby incorporated herein by reference. 
     In addition, this application references the following: (i) U.S. patent application Ser. No. 10/832,812, filed Apr. 26, 2004, and entitled “METHOD AND SYSTEM FOR SECURE NETWORK-BASED DISTRIBUTION OF CONTENT,” (ii) U.S. patent application Ser. No. 10/833,267, filed Apr. 26, 2004, and entitled “METHOD AND SYSTEM FOR NETWORK-BASED PURCHASE AND DISTRIBUTION OF MEDIA,” (iii) U.S. patent application Ser. No. 10/832,812, filed Apr. 26, 2004, and entitled “GRAPHICAL USER INTERFACE FOR BROWSING, SEARCHING AND PRESENTING MEDIA ITEMS,” (iv) U.S. Provisional Patent application No. 60/622,178, filed Oct. 25, 2004, and entitled “RESERVATION OF DIGITAL MEDIA ITEMS,” (v) U.S. Provisional Patent Application No. 60/620,223, filed Oct. 18, 2004, and entitled “NETWORK-BASED PURCHASE AND DISTRIBUTION OF DIGITAL MEDIA ITEMS,” all of which are hereby incorporated herein by reference herein. 
    
    
     BACKGROUND OF THE INVENTION 
     1. Field of the Invention 
     The present invention relates to the purchasing of digital media assets and, more specifically, to the purchase of media asset bundles. 
     2. Description of the Related Art 
     Traditionally, music has been purchased at music stores or music departments of larger stores. A consumer will visit the music store or department and manually browse for albums or compact discs (CDs) of interest. After the consumer selects an album or CD of interest, the consumer proceeds to a checkout register to pay for the album or CD being purchased. 
     In recent years music delivery or distribution over the Internet has become popular. Due to the advances in efficient file formats, such as MP3 and MPEG4, the size of media files has become small enough to make their download via the Internet practical. Also, technological advances have led to higher-speed Internet connections and lower cost of memory. The combination of these advances make downloading media files, such as for music and videos, manageable and not too time consuming. 
     One popular approach to online music distribution is Apple&#39;s iTunes® online music store. Consumers may use the iTunes® online music store to purchase music either as individual music tracks or in albums of songs. Other music stores such as Rhapsody™ and Napster™ have also been employed to purchase music online. 
     However, one limitation common to online music stores (generically referred to as online media stores) is in the limited options a consumer has when purchasing music albums. Currently, a music album available from an online media store contains a group of music files and no other file types. However, there are cases when a distributor of a music album may want to distribute other media file types along with the music files, such as non-playable file types (e.g., text or graphics). It is therefore desirable to enable the online distribution of media bundles that contain disparate media file types. 
     SUMMARY 
     The invention pertains to techniques for purchasing media asset bundles. These techniques can allow a user of a client computer to identify, preview, and purchase media asset bundles. In the context of this application, a media asset bundle is a group of disparate media assets, including at least one non-playable media asset. 
     The invention can be implemented in numerous ways, including as a method, system, device, apparatus, graphical user interface, or computer readable medium. Several embodiments of the invention are discussed below. 
     In one embodiment of the invention, a user browses for a media asset bundle that includes at least one non-playable media asset. Next, the user purchases the media asset bundle and obtains the media assets contained in the media asset bundle. Next, it is determined if a request has been made for a media asset in the media asset bundle and, if so, the requested media asset is presented to the user. In some embodiments of the invention, the presenting of the requested media asset further involves determining whether the requested media asset is a playable or non-playable media asset and presenting the viewing the media asset in an media asset viewer appropriate for that particular media asset (i.e., a non-playable media asset viewer or a playable media asset viewer). Non-playable media assets include portable document format (PDF) files, graphics files, multi-media files, and text files. Playable media assets include audio files and video files. Further, both playable and non-playable media asset files can contain digital rights management (DRM) information in some embodiments. Non-playable media asset viewers include web browser applications, text editors, PDF viewers, and e-book readers. Playable media asset viewers include media management applications and media players. 
     In a second embodiment of the invention, a client (e.g., a personal computer) requests to purchase a media asset bundle. Next, a payment is authorized for the request to purchase the media asset bundle and the media assets in the media asset bundle are obtained and made available to the requesting client. 
     In still another embodiment of the invention, a media asset is selected from the media asset bundle (e.g., by a user or program). Next, a determination is made whether the media asset in the media asset bundle is playable or non-playable. If the media asset is playable, the media asset is played. If the media asset is not playable, then the media asset is not played (i.e., skipped). 
     In another embodiment of the invention, a media asset bundle is presented to a user of a client computer. First, a client request is received to purchase a media asset bundle. Next, a payment is authorized for the media assets. Next, the media assets are obtained and made available to the client computer. Once the media assets have been made available to the requesting client, a media asset in the media asset bundle is selected (e.g., by a user). Upon selection, it is determined whether the selected media asset is playable or non-playable. If the media asset is playable, the media asset is played, or if not playable, not played. 
     Other aspects and advantages of the invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of the invention. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The invention will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like structural elements, and in which: 
         FIG. 1  is a block diagram of a multi-device media purchase system according to one embodiment of the invention. 
         FIG. 2  is a flow diagram of a media asset bundle purchase and presentation process according to one embodiment of the invention. 
         FIG. 3  is an exemplary application window showing an interface for browsing and purchasing of a media asset bundle according to one embodiment of the invention. 
         FIG. 4A  is a block diagram of a media asset bundle according to one embodiment of the invention. 
         FIG. 4B  is a block diagram of a media asset bundle according to one embodiment of the invention. 
         FIG. 5  is a flow diagram of a server-side media asset bundle purchase process according to one embodiment of the invention. 
         FIG. 6  is a block diagram representation of an exemplary relational database containing various data tables and tables of pointers to digital media assets according to one embodiment of the invention. 
         FIG. 7A  is a flow diagram of a client-side media asset bundle purchase and presentation process according to one embodiment of the invention. 
         FIG. 7B  is a flow diagram of a client-side media asset bundle purchase and present process according to a second embodiment of the invention. 
         FIG. 8  is a screen shot of a representative application program window according to one embodiment of the invention. 
         FIG. 9  shows an exemplary computer system suitable for use with the invention. 
     
    
    
     DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION 
     The invention pertains to techniques for purchasing media asset bundles. These techniques can allow a user of a client computer to identify, preview, and purchase media asset bundles. In the context of this invention, a media asset bundle is a group of disparate media assets, including at least one non-playable media asset (e.g., text or graphics). 
     Media assets are digital media items, for example audio, video, text, graphics, or multimedia files. The term media asset includes, but is not limited to, a wide variety of digital media items of various types, including songs or other audio files (e.g., MP3, MPEG4, AAC, WMA), music videos (e.g., QuickTime®, AVI), e-books, graphics (e.g., bitmap, JPEG, TIFF), portable document files (PDFs), digital slide presentations (e.g., Microsoft PowerPoint presentations), or interactive multimedia presentations (e.g., presented using a multimedia application such as QuickTime® or Macromedia Flash®). Further, media assets can be divided into two sub-types: playable media assets and non-playable media assets. Playable media assets include video and audio files, i.e., files that are typically presented or “played” in media players. Examples of playable media assets include, but are not limited to, music, music videos, audio books, promotional films, concert footage, artist interviews, and motion pictures. 
     Non-playable media assets include text and graphic files that are typically presented or “viewed” in browser or viewer applications (e.g., non-playable media asset viewers). As an example, a non-playable media asset could be a PDF file, viewed with a non-playable media asset viewer, in this case Adobe® Acrobat® Reader, which is typically used to view PDF files. Both playable and non-playable media assets may be protected by digital rights management DRM protection (e.g., Apple&#39;s Fair Play DRM) to limit access to the media assets to the purchaser of those media assets (see, for example, U.S. application Ser. No. 10/832,812.) Examples of non-playable media assets include photographs, logos, drawings, pamphlets, and e-books. 
     One example of a media asset bundle is a digital boxset. The digital boxset is a collection of songs available for purchase from an online media store. A digital boxset can be considered an online analogue of box sets traditionally sold in record stores. Traditionally, box sets contain several albums by a single recording artist, often along with bonus songs and liner notes describing the music contained in the box set. According to one embodiment, a digital boxset might include a variety of media assets including several songs, possibly one or more music videos, and a text, graphic or PDF file containing liner notes. 
     Typically, a consumer wishing to buy a media asset bundle online will employ a media management application or media player running on a client computer to make the purchase. Media management applications (MMAs) or media players, in the context of this invention, include software applications that typically incorporate the ability to do one or more of the following: play, browse, organize, purchase, and/or transfer digital media items between devices, including to portable media players (e.g., MP3 or AAC players). An example of a media management application is Apple&#39;s iTunes® application, produced by and available from Apple Inc., of Cupertino, Calif. An example of a portable media player is Apple&#39;s iPod available from Apple Inc. 
     Embodiments of the invention are discussed below with reference to  FIGS. 1-9 . However, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes as the invention extends beyond these limited embodiments. 
       FIG. 1  is a block diagram of a multi-device media purchase system  100  according to one embodiment of the invention. The media purchase system  100  includes a media commerce server  102 . The media commerce server  102  coordinates review and/or purchase of media assets (e.g., digital media items) through on-line transactions. Media assets are categorized as playable media assets  117  and non-playable media assets  115 . On-line transactions to purchase media assets are also referred to as electronic commerce (e-commerce). The media purchase system  100  also includes a client  104 . Typically, the media purchase system  100  would include a plurality of different clients  104 . Each client  104  includes a media player or media management application  108  (hereafter media player  108 ). The media player  108  is an application program (e.g., software application) that operates on the client  104 , which is a computing device. The client  104  is coupled to the media commerce server  102  through a data network  106 . Hence, any of the clients  104  can interact with the media commerce server  102  to review and/or purchase media assets. In one embodiment, the data network  106  includes at least a portion of the Internet. The clients  104  can vary with application but generally are computing devices that have memory storage. Often, the clients  104  are personal computers or other computing devices that are capable of storing and presenting media to their users. 
     The media purchase system  100  also includes a media storage server  110  and a media store  112 . The media storage server  110  represents a remote storage server that couples to the data network  106 . The media store  112  provides mass storage of the numerous playable media assets  117  and non-playable media assets  115  that are available for purchase via the media purchase system  100 . Once purchased, the media assets can be accessed from the media store  112  over the data network  106  by way of the media storage server  110 . 
     More particularly, the media purchase system  100  allows a user of the client  104  to utilize the media player  108  to browse, search or sort through a plurality of media asset bundles (not shown) that can be purchased from the media commerce server  102 . The media player  108  may also allow the user to preview a media clip of the media asset. In the event that the user of the media player  108  desires to purchase a particular media asset bundle (e.g., a media collection or digital boxset), the user (via the media player  108 ) and the media commerce server  102  engage in an on-line commerce transaction in which the user pays for access rights to the media assets in the media asset collection. 
     In the media purchase system  100  shown in  FIG. 1 , the media assets are stored in the media store  112  and retrieved via the media storage server  110 . Hence, the media commerce server  102  need not burden its resources to deliver any of the media assets that may be purchased to the client  104 . Instead, on purchasing a particular media asset bundle, the media commerce server  102  sends download information to the media player  108  on the client  104 . The download information can then be used by the media player  108  (and the client  104 ) to retrieve the media content for the particular media asset bundle by interacting with the media storage server  110  through the data network  106 . In this regard, the media storage server  110  obtains media assets from the media store  112  and downloads such media assets through the data network  106  to the client  104 . The downloaded media assets can then be stored on the client  104 . Thereafter, the media player  108  can present (e.g., play or view) the media assets at the client  104 . 
     The connections through the data network  106  between the media commerce server  102 , the client  104  and the media storage server  110  can be through secure connections, such as Secure Sockets Layer (SSL). Further, the media assets are typically stored at the client  104  in an encrypted manner. 
       FIG. 2  is a flow diagram of a media asset bundle purchase and play process  200  according to one embodiment of the invention. The media asset bundle purchase and present process  200  is, for example, associated with a media player of an online media purchase system. The media player can, for example, be the media player  108  operating on the client  104  illustrated in  FIG. 1 . The media asset bundle purchase and present process  200  typically permits a user to browse  201  available media assets. Typically, as noted above, media assets include audio, video, text and graphics files. Some media assets will be grouped into media asset bundles, which can be purchased in a single transaction. In one embodiment, the media assets in a media asset bundle may also be purchased separately. Generally, a user will see some advantage in purchasing a media asset bundle over buying media assets individually, including: a discounted price per media asset when bought as part of the bundle, the inclusion of media assets that are unavailable except as part of a media asset bundle, or the inclusion of non-playable media items such as liner notes that are unavailable except as part of a media asset bundle. 
     After the user browses  201  the available media assets and media asset bundles, the user purchases  203  a media asset bundle of interest. Upon the completion of the purchase  203 , the media assets of the media asset bundle are obtained  205  (e.g., by download or e-mail attachment). In one embodiment, as disclosed in related U.S. patent application Ser. No. 10/833,267, a client may receive a media access response containing instructions to the media player (or other client application) enabling the retrieval of each media asset in the media asset bundle that was purchased. Once media assets are obtained  205 , a decision  207  determines if a presentation request for a media asset has been made (e.g., by a user selecting the media asset in the media player.) If the presentation request has been made, the media asset is presented  209  (e.g., played or viewed) to the user. 
       FIG. 3  is an exemplary application window  300  showing an interface for browsing and purchasing of a media asset bundle according to one embodiment of the invention. In one embodiment of the invention, the application window  300  is produced by a media management application. 
     The application window  300  includes a media asset display panel  305 , which typically contains information and graphics relating to a particular media asset bundle (or group of media assets) that is referred to as a “digital boxset.” Additionally, the application window  300  contains a media asset listing  307 , having detailed information regarding individual media assets in the media asset bundle. Typically, this detailed information includes such things as publisher information and media asset title. The media asset listing  307  shows media asset information for songs, videos, and liner notes associated with the particular media asset bundle (e.g., digital boxset). In this example, the media asset information includes title, artist name, and album name. Of course other information could be displayed as well, such as year published, playing time, music genre, etc. 
     The media asset listing  307  contains a list of media assets, including both playable media assets  309  and non-playable media assets  311 . In this embodiment, playable media assets  309  include songs and videos, while the non-playable media asset  311  shown is a liner notes file, which typically contains text and/or graphics. The media asset display panel  305  contains artist and album information as well as a graphic  303 , for example an album cover graphic, associated with the media asset bundle. Additionally, the media asset display panel  305  includes a purchase button  301  (labeled “Buy Boxset”, in this embodiment), which enables the user to purchase the media assets listed in the media asset listing  307 . 
       FIG. 4A  is a block diagram of an exemplary media asset bundle  400  according to one embodiment of the invention. The media asset bundle  400  includes a plurality of playable media assets  401  and at least one non-playable media asset  403 . Specifically, in this exemplary media asset bundle  400  the playable media assets  401  are songs  405  (e.g., digital music files) and the non-playable media asset  403  is liner notes  407  (e.g., a document containing text and/or graphics). 
     In another embodiment of the invention, the media asset bundle can include a plurality of playable and/or non-playable media asset types. As noted above, media asset types include, but are not limited to audio files, video files and graphics files. One example of such a media asset bundle could contains one or more songs and one or more music videos. Other combinations are possible as well. 
       FIG. 4B  is a block diagram of an exemplary media asset bundle  410  according to another embodiment of the invention. As in  FIG. 4A , this embodiment contains playable media assets  401  and non-playable media assets  403 . In this embodiment, the media asset bundle  450  further contains an additional playable media asset  409 , namely, a video file (e.g., a music video) and an additional non-playable media asset, namely, a digital graphic  411  (e.g., a photograph or logo). 
       FIG. 5  is a flow diagram of a server-side media asset bundle purchase process  500  according to one embodiment of the invention. This process is, for example, associated with one or more server computers of a media purchase system. The server computers can, for example, be the media storage server  110  and/or the media commerce server  102  illustrated in  FIG. 1 . 
     The server-side media asset bundle purchase process  500  begins with receiving  501  a client request to purchase a media asset bundle, for example, a digital boxset. Next, a payment is authorized  503 . Authorization may proceed according to conventional online payment methods or as described in related U.S. patent application Ser. Nos. 10/833,267 and 10/832,812. Next, decision  505  determines if payment has been authorized. If payment has not been authorized, the purchase is denied and media asset bundle purchase process  500  ends. On the other hand, if decision  505  determines that payment has been authorized, the media assets in the media asset bundle are obtained  507 . For example, the media assets in the media asset bundle can be obtained  507  by looking up media asset locations in a database and gathering the media assets at a server computer. Finally, the media assets are made available  509  to the requesting client. The media assets can be made available  509  by, for example, transmitting the individual media assets to the client, by storing a media interest indicator on a server computer such that a user may download the media assets at a later time, or by sending a media access response (e.g., a document containing download information) to be used by a media management application to download the media assets when practicable (for a discussion of exemplary media access response formats, see related U.S. patent application Ser. No. 10/832,812.) 
       FIG. 6  is a block diagram representation of an exemplary relational database  600  containing various data tables and tables of pointers  650  pertaining to digital media assets according to one embodiment of the invention. Other database types (such as flat file databases) may be used as well. The database  600  may be used, for example, at operation  507  of the server-side media asset bundle purchase process  500  discussed above. It should be understood that there are a wide variety of database organizational structures, and that  FIG. 6  is meant to be exemplary and not as limiting the invention to any particular database structure. 
       FIG. 6  shows three exemplary data sections in the database  600 , which may be distributed across one or more media or database servers. A database table section  601  contains the database, i.e., the relational data tying the database together. As will be understood by those familiar with database organization, database tables may be implemented as tables of pointers pointing to other tables or to files on a server computer. The database table section  601  shown contains collection tables  605  (e.g., C 1 ), album tables  609  (e.g., A 1  and A 2 ), bundle tables  607  (e.g., B 1 ), and media asset tables  611   a - 611   d  (e.g., S 1 , S 2 , V 1 , and LN 1 ). 
     In addition to the database table section  601 , the relational database also includes a metadata section  603 . As can be seen in  FIG. 6 , the metadata section  603  contains metadata information, organized in metadata tables  613  (e.g., MD 1  and MD 2 ). Metadata, in the context of this figure, includes information relating to media assets, for example, songs. Typical metadata information includes media asset title, publication information, artist information, etc. The exemplary metadata tables  613  shown in  FIG. 6  contain song information such as is normally stored in, for example ID 3  tags in typical MP3 files, including such data as song titles, artist names, music genres, song release dates, etc. 
     The relational database further includes a media asset storage section  604 . The media asset storage section  604  is, for example, a file server or a media storage device such as the media store  112  shown in  FIG. 1 . 
     As discussed above, the database  600  contains a variety of tables, stored in database table section  601 . Typical tables include a collection table  605 . The collection table  605  may include pointers  650  to several media asset bundles, including music albums and compilations. In one embodiment, collection table  605  contains pointers  650  to a media asset bundle, logically represented by bundle table  607 , which includes pointers  652  that lead to media asset tables  611   a - 611   d , which contain pointers  654  that lead to media assets  615  (e.g., songs S 1  and S 2 , video V 1 , and liner notes LN 1 ) associated with the media asset bundle. The media asset tables  611   a - 611   d  can further include pointers  656  to metadata for the associated media assets  615 . Alternately, the bundle table  607  may point (not shown) to a plurality of music albums such as the album represented by album table  609 . In one embodiment of the invention, the media asset bundle is a digital boxset. Additionally, the collection table  605  shown can contain pointers  658  to the album table  609 , which contains pointers to media assets  615  (e.g., songs S 1 , S 2 , etc.) in the album. 
     As illustrated in  FIG. 6 , the album table  609  and the bundle table  607  include pointers  652  and  660  to songs, some of which are included in both the album table  609  and the bundle table  607 . Specifically, for song S 1 , a media asset  615 , is shown as having pointers  660  and  652  to it from both the album table (A 1 )  609  and the bundle table (B 1 )  607 . In this case, following the pointers  660  and  652  that lead to the media asset table (S 1 )  611   a  leads to a location (e.g., path) of song S 1 , which is shown as the single media asset  615  that is stored in the media asset storage section  604 . 
     In  FIG. 6 , media asset tables  611   a - 611   d  contain pointers  654  to media assets  615  (e.g., song files, video files, and liner notes) in the media asset storage section  604 . The media asset tables shown in  FIG. 6  include song tables  611   a  and  611   b , which point to song files S 1  and S 2  in the media asset storage section  604 ; a video table  611   c , which points to a video file V 1  in the media asset storage section  604 ; and a liner notes table  611   d , which points to a liner notes file (LN 1 ) in the media asset storage section  604 . Other media asset types, such as graphics, multimedia files, audio books, and/or e-books may be stored in the database in a similar manner. 
     Returning to the media asset bundle table  607  and the album table  609 , which may indicate that songs common to both a media asset bundle and an album are stored only once on a single file server, those familiar with the art will understand that media assets associated with a media asset bundle and media assets associated with an album may be stored in different locations, leading to multiple copies of a single media asset across a plurality of file servers. Thus, in one embodiment, song file S 1  is stored in one media asset storage section for a first media asset bundle and in a separate media asset storage section for an album. 
       FIG. 7A  is a flow diagram of a client-side media asset bundle purchase and present process  700  according to one embodiment of the invention. The media asset bundle purchase and present process  700  is, for example associated with a client computer of a media purchase system. The client computer can, for example, be the client  104  illustrated in  FIG. 1 . 
     The client-side media asset bundle purchase and present process  700  begins with a user browsing  701   a  media store, e.g., Apple&#39;s iTunes® Store, using, for example, a media management application e.g., Apple&#39;s iTunes® client application. Next, the user finds and selects  703  a media asset bundle, for example, a digital boxset that he or she wishes to purchase  705 . The selection  703  and purchase  705  may be accomplished by selecting, for example, a user interface control, such as a purchase button  301  in the application window  300  shown in  FIG. 3 . Next, the media asset bundle is received  707  at the client computer, for example, by downloading individual media assets associated with the media asset bundle. 
     Thereafter, the received media assets can be displayed  709  to the user. Next, a displayed media asset is selected  711  by the user or the client computer. Next, a decision  713  determines if the selected media asset is a playable media asset, such as an audio or video file. As noted above, playable media assets include video and audio files, i.e., files that are typically “played” in media players or media management applications. Examples of playable media assets include but are not limited to, music, music videos and movies. If the media asset is playable, the selected media asset is presented by playing  717  the media asset in a playable media asset reader (e.g., a media management application or media player). If decision  713  determines that the selected media asset is a non-playable media asset (e.g., liner notes contained in a PDF file), then the selected non-playable media asset is viewed  715  in, for example, a non-playable media asset viewer application, such as the Adobe® Acrobat® Reader, which is commonly used to view PDF files. Other non-playable media asset viewers include web browser applications, XML browsers, text editors, and e-book readers. Finally, decision  719  checks to see if the user has selected another media asset. If a media asset has been selected, the client-side media asset bundle purchase and present process  700  returns to block  713  and subsequent blocks. If, on the other hand, no media asset has been selected, then the process  700  ends. 
     In one embodiment of the invention, the non-playable media asset viewer application is integral (i.e., built-in) to the media management application or media player used to view  715  the received media assets. In another embodiment, the media management application or media player used to view  715  the received media assets can spawn an external application to view non-playable media assets. 
       FIG. 7B  is a flow diagram of a client-side media asset bundle purchase and present process  750  according to a second embodiment of the invention. According to this embodiment media assets are automatically played sequentially (or randomly) by a media management application or media player (e.g., when the media management application is playing the media assets in a playlist, album, or digital boxset). 
     Client-side media asset bundle purchase and present process  750  begins with steps  701 - 709  as described above with reference to  FIG. 7B . However, upon the completion of the displaying  709  of media assets in the media asset bundle, the list of media assets is played  751  (e.g., presented by selecting the list and clicking ‘play’ in the media management application.) Next, the first (or next) media asset in the list of media assets is selected  753 , followed by a determination  755  whether the selected media asset is playable. If the selected media asset is playable, then it is played  759  by the media management application or media player. On the other hand, if the selected media asset is not playable then it is skipped  757 . Upon completion of the playing  757  of the currently selected media asset, a decision  761  determines if there are more media assets to present in the list of media assets. If there are, the client-side media asset bundle purchase and present process  750  returns to block  753  and subsequent blocks. On the other hand, if decision  761  determines that no more media assets are available (e.g., the media management application has played through the entire media asset bundle), then the process ends. In this way, for example, a media management application may automatically play one or more media assets in a media asset bundle (e.g., boxset) that includes audio files (e.g., songs) and text/graphics files (e.g., liner notes) and be able to distinguish between audio and text/graphics without user intervention. Similarly, a media management application can play one or more media assets in a media asset bundle that includes audio and video files as well as text/graphics files, playing only the audio files, only the video files, or both, depending on the user&#39;s preference. 
       FIG. 8  is a screenshot of a representative application program window  800  according to one embodiment of the invention. This particular screenshot is of a version of iTunes®, a media management application/media player produced by and available from Apple Inc. of Cupertino, Calif. The application window contains, among other data, a listing  803  of a plurality of media assets  805 , including AAC audio files  807  (songs) and a PDF document  809  (liner notes). As noted above, the PDF document  809  is an example of a non-playable media asset, while the AAC audio files  807  are examples of playable media assets. 
       FIG. 9  shows an exemplary computer system  925  suitable for use as a client according to one embodiment of the invention. The computer system can be, for example, the client  104  as illustrated in  FIG. 1 . The computer system  925  includes a display monitor  928  having single or multi-screen displays  930  (or multiple displays), cabinet  932 , keyboard  934 , and mouse  936 . Cabinet  932  houses a drive  938 , such as a CD-ROM or floppy drive, system memory and a hard drive (not shown) which may be utilized to store and retrieve software programs incorporating computer code that implements the present invention, data for use with the invention, and the like. Although CD-ROM  940  is shown as an exemplary computer readable storage medium, other computer readable storage media including floppy disk, tape, flash memory, system memory, and hard drive may be utilized. Additionally, a data signal embodied in a carrier wave (e.g., in a network including the Internet) may be the computer readable storage medium. In one implementation, an operating system for the computer system  925  is provided in the system memory, the hard drive, the CD-ROM  940  or other computer readable storage medium and serves to incorporate the computer code that implements the invention. 
     The invention is preferably implemented by software, but can also be implemented in hardware or a combination of hardware and software. The invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data, which can thereafter be read by a computer system. Examples of the computer readable medium include read-only memory, random-access memory, CD-ROMs, flash memory cards, DVDs, magnetic tape, optical data storage devices, and carrier waves. The computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion. 
     The many features and advantages of the present invention are apparent from the written description and, thus, it is intended by the appended claims to cover all such features and advantages of the invention. Further, since numerous modifications and changes will readily occur to those skilled in the art, the invention should not be limited to the exact construction and operation as illustrated and described. Hence, all suitable modifications and equivalents may be resorted to as falling within the scope of the invention.

Metadata:
Filing Date: 20110112
Publication Date: 20130716
Grant Date: 20130716
Priority Date: 20050525
Inventors: ROBBIN JEFFREY L.
HELLER DAVID
WIESE MIKE
GAUTIER PATRICE
VEROSUB ELLIS M.
Assignee: APPLE INC
CPC Classifications: [{"code": "G06Q30/0601", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06Q30/0641", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06Q30/00", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06Q30/0641", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06Q30/0601", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06Q30/00", "inventive": true, "first": true, "tree": "[]"}]
Family ID: 43926423