Field of the Invention
The present invention relates to electronic transmission of media content and, more particularly, to electronic submission of media content for purposes of media purchase or distribution.
Description of the Related Art
Traditionally, music and movies has been purchased at music stores or video stores, or at music or video departments of larger stores. A consumer will visit the music or video store (or music or video) department and manually browse for music or movies, or similar media content of interest, on albums or compact discs (CDs) or digital video discs (DVDs) or high definition video discs. After the consumer selects the media content of interest, the consumer proceeds to a check-out register to pay for the music or movies being purchased.
In recent years, media delivery or distribution over the Internet has become popular. Today, various online media hosting sites permit virtual visitors to purchase and download albums or songs via the Internet (e.g., World Wide Web). However, in order for music or movies to be offered for purchase and download, the electronic content for the music or movies must first be provided to the media hosting sites.
Conventionally, a music label or movie studio desirous of selling their productions online produce a tape or disc, and then physically mail the tape or disc to a representative for the media hosting site. More recently, music labels and movie studios have electronically transmitted their productions to the media hosting site, via the Internet. While the Internet may provide many conveniences, such as sending e-mails with file attachments, conventional e-mails with attachments of very large files may be inefficient, may be ineffective, or may fail in transmitting the very large files.
Unfortunately, very large files are typically associated with the productions of music labels and movie studios. For example: data may total approximately seven hundred megabytes for a very large file (or collection of files) associated with an eighty minute music album; data may total approximately eight gigabytes for a very large file (or collection of files) associated with a DVD resolution feature length film, or a large collection of music videos or concert performances. Furthermore, a file or collection of files associated with high definition video can be even larger. For example, feature length movies encoded in ProRes 422 (HQ) may be as large as approximately six-hundred gigabytes or more. Accordingly, it should be understood that attendant difficulties may be encountered by music studios or movie studios when they attempt to electronically transmitted such very large files of their productions to the media hosting site, via the Internet.
Various different network transport methods may help to overcome such difficulties. Naturally, transport speed and efficiency are always at issue, in choosing suitable transport methods, since the media content files are so large. However, choice of transport methods is greatly complicated by additional competing, cross-cutting concerns such as security, cost, load balancing, reliability, convenience, ease of use, and current availability.
For example, while a studio's network firewalls may provide them with added network security, depending on how such firewalls are configured, the fastest transport methods may or may not be available currently, for use in transporting large (voluminous) digital media content. Eliminating diversity by forcing attempts using only the fastest transport methods, when such transport methods are not currently available, may result in media submission failure. As another example, while eliminating diversity by forcing use of only a “lowest common denominator” transport method may help with availability and ease of use, such transport method may provide only very poor transport speed and performance.
From the foregoing, it should be understood that such failure in media content submission or very poor transport speed may cause significant frustration and dissatisfaction on the part of content providers, such as the music or movie studios. Thus, there is a need for improved approaches to manage submission of media to an online media hosting site, where such cross-cutting concerns in transporting voluminous digital media content can be balanced.
Broadly speaking, the invention relates to an improved system and method for submission of voluminous media content data. Automated transport mechanism selection may help to ease difficulties in balancing cross-cutting concerns in transporting the voluminous media. The cross-cutting concerns may relate to one or more aspects such as transport speed, security, cost, load balancing, user classification, reliability, convenience, ease of use, and current availability.
The invention can be implemented in numerous ways, including as a method, system, device, apparatus (including computer readable medium and graphical user interface). Several embodiments of the invention are discussed below.
One embodiment pertains to a method and/or system for transporting media content data over a network to a media submission system. A client media submission program may be provided that supports media submission to the media submission system using a plurality of transport mechanisms. One of the transport mechanisms to be utilized for the media submission may be determined based at least in part on configuration criteria. The media content data may be submitted over the network to the media submission system using the determined one of the transport mechanisms.
Another embodiment pertains to a computer readable medium including at least computer program code stored thereon for transporting media content data over a network to a media submission system. The computer program code can, for example, include at least: computer program code for client media submission to the media submission system using a plurality of transport mechanisms; computer program code for determining one of the transport mechanisms to be utilized for the media submission based at least in part on configuration criteria; and computer program code for submitting the media submission over the network to the media submission system using the determined one of the transport mechanisms.
Another embodiment pertains to an apparatus for transporting media content data over a Wide Area Network (WAN). The apparatus can, for example, include at least validation test logic and transport control logic. The validation test logic can be configured to determine a validation ranking of a plurality of transport mappings. Upon validating a selected transport mapping from among the plurality of transport mappings of the validation ranking, the validation test logic can be configured to designate the selected transport mapping as a validated transport mapping. The transport control logic can be configured to attempt delivery of the media content data over the WAN according to the validated transport mapping.
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.
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:
Embodiments of certain embodiments of the invention are discussed below with reference to
In accordance with one embodiment, an encoding manager 106 encodes media items from metadata and data files containing media content. Encoding manager 106 can encode the media items as they are purchased or prior to purchase by a consumer.
In accordance with another embodiment, a medium store 108 stores or has access to media content that has been submitted to media content submission and distribution system 100. Media store 108 can provide mass storage for media content that is available for purchase via media content submission and distribution system 100. Thus, media store 108 may store media items that have been generated as well as store media content that have been submitted for distribution by media content and distribution system 100.
Media storage servers 110 represents one or more remote storage servers that couple to the data network 104. In media content and distribution system 100 shown in
Media content submission and distribution system 100 is accessible to one or more media content providers 112. A media content provider 112 may be, for example, a movie studio, television network, or record company providing media content that can be distributed via one or more digital media service providers (e.g., via a media distribution system). Each media content provider 112 may submit media content 114. As an example, media content can be submitted in association with a feature film or television episode. Generally, media content includes metadata and identifies a plurality of data files.
Submitted media content is typically very large. As mentioned previously, feature length movies encoded in ProRes 422 (HQ) may be as large as approximately six-hundred gigabytes or more. A Transporter may be embodied as an application or service directed to submission of voluminous media content data. Automation may help to ease difficulties in balancing cross-cutting concerns in transporting the voluminous media. Such cross-cutting concerns may relate to aspects such as transport speed, security, cost, load balancing, user classification, reliability, convenience, ease of use, and current availability.
The Transporter may be embodied as a centralized application or service, or as a distributed application or service. For example, as shown in
Similarly, initiation of some other selected portions of Transporter functionality may be advantageously distributed to the Transporter server program 116B, while further implementation for such other selected portions of Transporter functionality in response to such initiation may be advantageously distributed to the Transporter client program 116A. For example, initiating load balancing of current server load through control messaging may be advantageously distributed to respective Transporter server programs 116B of each of the Media Storage Servers 110. Further implementing load balancing in response to server control messaging, through the Transporter client's selection of suitable transport mechanisms, may be advantageously distributed to the Transporter server program 116B.
Moreover, initiating overall balancing of cross-cutting concerns in transporting the voluminous media, relating to aspects such as transport speed, security, cost, load balancing, customer classification, reliability, convenience, and ease of use, may be advantageously distributed to the Transporter server program 116B. The Transporter server program 116B can provide and/or update configuration criteria to the Transporter client program 116A (and/or through providing and/or updating a preferred ranking related to the server's prioritized preferences with respect to different transport mechanisms, and/or through transmitting to the Transporter client program 116A validation (or invalidation, or undesignation) control messages related to server directives relative to the different transport mechanisms.)
Further implementing overall balancing of cross-cutting concerns, through the Transporter client's selection of suitable transport mechanisms in response to the server's configuration criteria (and/or to the server's preferred ranking, and/or to the server's validation (or invalidation, or undesignation) control messages), may be advantageously distributed to the Transporter client program 116A.
Priority of a plurality of transport mechanisms may be determined 204. For example, the plurality of transport mechanisms may be prioritized based on configuration criteria. The configuration criteria may be provided to the client media submission program by the media submission system.
One of the transport mechanisms to be utilized for the media submission may be determined 206. Such determination may be based, at least in part, on the configuration criteria. The determination of the one of the transport mechanisms to be utilized for the media submission may comprise checking its current availability. For example, in
However, in case the determined one of the transport mechanisms is not currently available, the method may return to block 206 so that another transport mechanism can be determined. For example, if the determined one of the transport mechanisms employs a User Datagram Protocol (UDP), and if the afore-mentioned UDP diagnostic indicates that UDP is not currently available for connection to a desired one of the media storage servers of the media submission system (and hence the determined one of the transport mechanisms is unavailable), then the method may return to block 206. Accordingly, the method 200 may determine another one of the transport mechanisms to be utilized for the media submission, and so on, if the checking indicates that the determined one of the transport mechanisms is not currently available. For example, if the other one of the transport mechanisms does not employ UDP, and instead employs the Transport Control Protocol (TCP), and if the afore-mentioned TCP diagnostic indicates that TCP is currently available for connection to the desired media storage server of the media submission system, then decision block 208 finds affirmatively for the availability of the other one of the transport mechanisms.
Accordingly, with respect to the determined transport mechanism, such transport mechanism may be adapted for transporting the media submission from the client to one or more of the media storage servers of the media submission system using a determined one of a plurality of network protocols. Hence, the submitting may comprise the client submitting the media submission over the network to the media storage server using the determined one of the plurality of network protocols.
Additionally, the submitting may comprise the client submitting the media submission over the network to the media storage server of the media submission system using a determined one a plurality of non-real time Wide Area Network (WAN) protocols. Transport speed and efficiency may be compelling concerns, in choosing suitable transport protocols, since the media content files are so large. Such use of the non-real time WAN protocols may provide particular advantages, and may provide for the particular purpose of satisfying the concern over transport speed and efficiency.
Further with respect to the determined transport mechanism, each of the plurality of transport mechanisms may be identified using a respective one of a plurality of transport mappings. For example, for transport mechanisms adapted for transporting the media submission from the client to one or more of the media storage servers of the media submission system using determined ones of the plurality of network protocols, each transport mapping may comprise a respective protocol set identifier and a respective media storage server identifier. The media storage server identifiers may employ, for example, an Internet Protocol (IP) address. While the form of the identifier may vary, each identifier may uniquely identify a respective one of the media storage servers.
At least one of the transport mappings may be identified as a validated transport mapping. For example, when availability of the determined transport mechanism is validated, the transport mapping corresponding to the validated transport mechanism may be identified as a validated transport mapping. Determining the one of the transport mechanisms to be utilized for the media submission may be based, at least in part, on the validated transport mapping.
Similarly, at least one of the transport mappings may be identified as an invalidated transport mapping. For example, when availability of the determined transport mechanism is invalidated, the transport mapping corresponding to the invalidated transport mechanism may be identified as an invalidated transport mapping. Determining the one of the transport mechanisms to be utilized for the media submission may be based, at least in part, on the validated transport mapping. The one of the transport mechanisms identified by the invalidated transport mapping may be excluded from being utilized for the media submission.
In the following discussions of additional figures, it should be understood that “Logic”, includes but is not limited to hardware, firmware, software and/or combinations of each to perform a function(s) or an action(s), and/or to cause a function or action from another logic, method, and/or system. For example, based on a desired application or needs, logic may include a software controlled microprocessor, discrete logic like an application specific integrated circuit (ASIC), a programmed logic device, a memory device containing instructions, or the like. Logic may include one or more gates, combinations of gates, or other circuit components. Logic may also be fully embodied as software. Where multiple logical logics are described, it may be possible to incorporate the multiple logical logics into one physical logic. Similarly, where a single logical logic is described, it may be possible to distribute that single logical logic between multiple physical logics.
As a general matter, Wide Area Networks (WANs) may have high latency. However, use of the Wide Area Network (WAN) may still be preferred for a particular purpose of convenience, particularly when the content provider(s) and the transporter program 302A may be substantially remote from the media submission system. High latency of WANs may make selection of suitable transport mechanisms more difficult or complex. Automated transport mechanism selection may help to ease difficulties in balancing cross-cutting concerns in transporting the voluminous media over high latency WANs.
As shown in
The media submission system 306 may initiate overall balancing of cross-cutting concerns in transporting the media content data 304, relating to aspects such as transport speed, security, cost, load balancing, customer classification, reliability, convenience, and ease of use. In particular, the media submission system 306 may provide and/or update configuration criteria to the client 302A. The client 302A may implement overall balancing of cross-cutting concerns based on the configuration criteria. Namely, the client's selection of suitable transport mechanisms can be based on the configuration criteria provided by the media submission system 306.
For example, the media submission system 306 may provide and/or update the client with a preferred validation ranking 320 of transport mappings, related to the media submission system's prioritized preferences with respect to different transport mechanisms. Also, through transport mapping validation control messaging 322, the media submission system 306 may invalidate 324 and/or validate 326 transport mappings that affect the client's validation test logic 310.
In particular, the media submission system may initiate load balancing 328 or failover 330 messages (and/or corresponding transport mapping validation/invalidation/undesignation control messages). In response thereto, the client's validation test logic 310 may be configured to determine the validation ranking 312 of the plurality of transport mappings.
Furthermore, in balancing the cross-cutting concerns, various different transport mechanism prioritizations are suited to various different kinds of media content. The larger an amount of data of the media content, the more important the transport speed, at the expense of server load and transport cost. With respect to type of audio-visual media, music files are typically smaller, so transport speed may be less important, relative to importance of transport cost savings. With respect to different media encoding types, some result in more compact files sizes than others. Accordingly, as shown in
The validation test logic 410 may be configured to accommodate one or more validation test modules 418. The validation ranking 412 may be used for prioritizing selection of a transport mapping for validation test. Upon favorable validation test determination by the validation test module 418 of availability of a selected transport mechanism identified by the selected transport mapping, the selected transport mapping may be designated by the validation test logic 412 as the validated transport mapping 414. Upon any invalidation of any member or members of the plurality of transport mappings due to unfavorable validation test 418 determination, the validation test logic 410 may be configured to determine iteratively the validation ranking 412 of the plurality of transport mappings 413.
Various diagnostics and/or tests may be employed. As an example illustrating both a particular diagnostic and an unfavorable test determination, if the UDP diagnostic 420 indicates that a selected transport mechanism requiring UDP is not currently available for connection to a desired one of the media storage servers of the media submission system, then the validation test logic 410 may invalidate the selected transport mapping identifying the selected transport mechanism.
As an example illustrating both another diagnostic and a favorable test determination, if the TCP diagnostic 422 indicates that a selected transport mechanism requiring only TCP (and not UDP) is currently available for connection to a desired one of the media storage servers of the media submission system, then the validation test logic 410 may validate the selected transport mapping identifying the selected transport mechanism, and delivery of the media content data over the WAN according to the validated transport mapping 414 may be attempted.
The validation test module 418 of the validation test logic 410 may be configured to determine transport status 424, indicating a success or a failure of transport of the media content data over the WAN in accordance with the validated transport mapping. The validation test logic 410 may invalidate the validated transport mapping based upon the transport status 424 indicating the failure of transport of the media content data over the WAN in accordance with the validated transport mapping. Upon any invalidation of the validated transport mapping due to the transport status 424 indicating the failure of transport of the media content data over the WAN in accordance with the validated transport mapping, the validation test logic may be configured to determine the validation ranking of the plurality of transport mappings.
As discussed, testing may be performed, and validation/invalidation decisions may be made locally. Alternatively, they may be done remotely. The validation test module 418 may further comprise transport mapping validation control messaging 426 for receiving control messages from the content submission system, and/or from one or more storage servers of the content submission system. As discussed previously herein, in response to receiving such transport mapping validation control messages, the validation control logic 410 may invalidate one or more transport mappings; or may validate one or more transport mappings; or may undesignate one or more transport mappings. In particular, a transport mapping already designated as a validated transport mapping may be undesignated as such; and a transport mapping already designated as an invalid transport mapping may be undesignated as such.
At least one WAN protocol set 426 comprises a pair of multilayer WAN protocols, wherein a first member of the pair has a stateless transport layer protocol 428 for transporting the media content data, and the other member of the pair has a stateful transport layer 430 for transporting flow rate feedback data, which can be used in controlling flow rate of the media content data of the first member.
The transport mechanism illustrated in
A transport mechanism employing the IRSNYC protocol as illustrated in
At decision block 604, in an affirmative case, a transport mapping having a top priority in the validation ranking may be selected. Validation may be performed 606 on the selected transport mapping.
At decision block 608 the selected transport mechanism identified by the selected transport mapping may not pass validation, for example, if the selected transport mechanism is unavailable. In such negative case, the selected transport mapping may be invalidated 609, and the validation ranking may again be determined 602, now taking into account the transport mapping invalidation.
At decision block 608, in an affirmative case the selected transport mechanism identified by the selected transport mapping may pass validation. Upon validating the selected transport mapping, the selected transport mapping may be designated as a validated transport mapping. The delivery of the media content data over the WAN according to the validated transport mapping may then be attempted 610.
At decision block 612, the attempted delivery over the WAN according to the validated transport mapping may be unsuccessful. In such negative case, the validated transport mapping may be invalidated 609. At decision block 612, in an affirmative case the attempted deliver is successful, the status is so updated 614, and the method 600 can end.
The invention can be implemented by software, 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, DVDs, magnetic tape, and optical data storage devices. 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 various aspects, features, embodiments or implementations of the invention described above can be used alone or in various combinations. Embodiments of the invention can, for example, be implemented by software, hardware, or a combination of hardware and software. Embodiments of 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 generally include read-only memory and random-access memory. More specific examples of computer readable medium are tangible and include Flash memory, EEPROM memory, memory card, CD-ROM, DVD, hard drive, magnetic tape, and optical data storage device. 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 advantages of the invention are numerous. The many features and advantages of the present invention are apparent from the written description. 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.
Number | Name | Date | Kind |
---|---|---|---|
4750119 | Cohen et al. | Jun 1988 | A |
5253165 | Leiseca et al. | Oct 1993 | A |
5410598 | Shear | Apr 1995 | A |
5535383 | Gower | Jul 1996 | A |
5627973 | Armstrong et al. | May 1997 | A |
5752128 | Yamashita | May 1998 | A |
5765152 | Erickson | Jun 1998 | A |
5884280 | Yoshioka et al. | Mar 1999 | A |
5943422 | Van | Aug 1999 | A |
6067531 | Hoyt et al. | May 2000 | A |
6085253 | Blackwell et al. | Jul 2000 | A |
6151643 | Cheng | Nov 2000 | A |
6226618 | Downs et al. | May 2001 | B1 |
6233682 | Fritsch | May 2001 | B1 |
6236313 | Milsted et al. | May 2001 | B1 |
6263313 | Milsted | Jul 2001 | B1 |
6275954 | Herman et al. | Aug 2001 | B1 |
6330670 | England et al. | Dec 2001 | B1 |
6338044 | Cook et al. | Jan 2002 | B1 |
6341353 | Herman et al. | Jan 2002 | B1 |
6345256 | Milsted et al. | Feb 2002 | B1 |
6363486 | Knapton | Mar 2002 | B1 |
6363488 | Ginter et al. | Mar 2002 | B1 |
6385596 | Wiser et al. | May 2002 | B1 |
6389592 | Ayres et al. | May 2002 | B1 |
6546555 | Hjelsvold et al. | Apr 2003 | B1 |
6549922 | Srivastava et al. | Apr 2003 | B1 |
6587837 | Spagna et al. | Jul 2003 | B1 |
6591420 | McPherson et al. | Jul 2003 | B1 |
6658476 | Van | Dec 2003 | B1 |
6691149 | Yokota et al. | Feb 2004 | B1 |
6731312 | Robbin | May 2004 | B2 |
6754895 | Bartel et al. | Jun 2004 | B1 |
6873992 | Thomas | Mar 2005 | B1 |
6874003 | Morohashi | Mar 2005 | B2 |
6910049 | Fenton et al. | Jun 2005 | B2 |
6937168 | Iverson et al. | Aug 2005 | B2 |
6938005 | Iverson et al. | Aug 2005 | B2 |
7073193 | Marsh | Jul 2006 | B2 |
7076445 | Cartwright | Jul 2006 | B1 |
7209892 | Galuten et al. | Apr 2007 | B1 |
7275243 | Gibbons et al. | Sep 2007 | B2 |
7292980 | August et al. | Nov 2007 | B1 |
7308413 | Tota et al. | Dec 2007 | B1 |
7383233 | Singh et al. | Jun 2008 | B1 |
7624046 | Galuten et al. | Nov 2009 | B2 |
7685512 | Hanson et al. | Mar 2010 | B2 |
7729946 | Chu | Jun 2010 | B2 |
7739256 | Powell | Jun 2010 | B2 |
7756920 | Muller et al. | Jul 2010 | B2 |
7827162 | Suitts et al. | Nov 2010 | B2 |
7844548 | Robbin et al. | Nov 2010 | B2 |
7860830 | Mirrashidi et al. | Dec 2010 | B2 |
7962634 | Cortos et al. | Jun 2011 | B2 |
8015237 | Muller et al. | Sep 2011 | B2 |
20010021926 | Schneck et al. | Sep 2001 | A1 |
20010037207 | Dejaeger | Nov 2001 | A1 |
20010044786 | Ishibashi | Nov 2001 | A1 |
20010054046 | Mikhailov et al. | Dec 2001 | A1 |
20020002541 | Williams | Jan 2002 | A1 |
20020004824 | Cuan et al. | Jan 2002 | A1 |
20020032658 | Oki et al. | Mar 2002 | A1 |
20020047899 | Son et al. | Apr 2002 | A1 |
20020049844 | Nishikawa | Apr 2002 | A1 |
20020073177 | Clark et al. | Jun 2002 | A1 |
20020077986 | Kobata et al. | Jun 2002 | A1 |
20020078211 | Natarajan et al. | Jun 2002 | A1 |
20020082857 | Skordin et al. | Jun 2002 | A1 |
20020087440 | Blair et al. | Jul 2002 | A1 |
20020091584 | Clark et al. | Jul 2002 | A1 |
20020099661 | Kii et al. | Jul 2002 | A1 |
20020099696 | Prince | Jul 2002 | A1 |
20020099801 | Ishii | Jul 2002 | A1 |
20020107803 | Lisanke et al. | Aug 2002 | A1 |
20020112171 | Ginter et al. | Aug 2002 | A1 |
20020116293 | Lao et al. | Aug 2002 | A1 |
20020124182 | Bacso et al. | Sep 2002 | A1 |
20020143612 | Barik et al. | Oct 2002 | A1 |
20020143782 | Headings et al. | Oct 2002 | A1 |
20020152267 | Lennon | Oct 2002 | A1 |
20020152278 | Pontenzone et al. | Oct 2002 | A1 |
20020165811 | Ishii et al. | Nov 2002 | A1 |
20020186844 | Levy et al. | Dec 2002 | A1 |
20020198843 | Wang et al. | Dec 2002 | A1 |
20030005173 | Shah et al. | Jan 2003 | A1 |
20030021283 | See et al. | Jan 2003 | A1 |
20030033162 | Houssiaux et al. | Feb 2003 | A1 |
20030037242 | Yasuna et al. | Feb 2003 | A1 |
20030065717 | Saito et al. | Apr 2003 | A1 |
20030074465 | Tang et al. | Apr 2003 | A1 |
20030115144 | Stefik et al. | Jun 2003 | A1 |
20030120593 | Bansai et al. | Jun 2003 | A1 |
20030120928 | Cato et al. | Jun 2003 | A1 |
20030135424 | Davis et al. | Jul 2003 | A1 |
20030149742 | Bollerud | Aug 2003 | A1 |
20030182188 | Duchow | Sep 2003 | A1 |
20030208473 | Lennon et al. | Nov 2003 | A1 |
20030226150 | Berberet et al. | Dec 2003 | A1 |
20030236886 | Oren et al. | Dec 2003 | A1 |
20040012618 | Finney | Jan 2004 | A1 |
20040015427 | Camelio | Jan 2004 | A1 |
20040015445 | Heaven | Jan 2004 | A1 |
20040034601 | Kreuzer | Feb 2004 | A1 |
20040039754 | Harple | Feb 2004 | A1 |
20040044949 | Rowe | Mar 2004 | A1 |
20040059929 | Rodgers et al. | Mar 2004 | A1 |
20040133605 | Chang et al. | Jul 2004 | A1 |
20040136698 | Mock et al. | Jul 2004 | A1 |
20040143760 | Alkove et al. | Jul 2004 | A1 |
20040148598 | Kita et al. | Jul 2004 | A1 |
20040153968 | Ching et al. | Aug 2004 | A1 |
20040167858 | Erickson | Aug 2004 | A1 |
20040181459 | Wright | Sep 2004 | A1 |
20040205028 | Verosub et al. | Oct 2004 | A1 |
20040210481 | Quinlan et al. | Oct 2004 | A1 |
20040215733 | Gondhalekar et al. | Oct 2004 | A1 |
20040254883 | Kondrk et al. | Dec 2004 | A1 |
20040254949 | Amirthalingam | Dec 2004 | A1 |
20040267552 | Gilliam et al. | Dec 2004 | A1 |
20040267608 | Mansfield, Jr. | Dec 2004 | A1 |
20040268451 | Robbin et al. | Dec 2004 | A1 |
20050015765 | Covell et al. | Jan 2005 | A1 |
20050021478 | Gautier et al. | Jan 2005 | A1 |
20050034164 | Sano et al. | Feb 2005 | A1 |
20050038813 | Apparao et al. | Feb 2005 | A1 |
20050044524 | Murray et al. | Feb 2005 | A1 |
20050050218 | Sheldon et al. | Mar 2005 | A1 |
20050050345 | Dowdy et al. | Mar 2005 | A1 |
20050071418 | Kjellberg et al. | Mar 2005 | A1 |
20050080743 | Ostrover et al. | Apr 2005 | A1 |
20050080788 | Murata | Apr 2005 | A1 |
20050144635 | Boortz | Jun 2005 | A1 |
20050165656 | Frederick et al. | Jul 2005 | A1 |
20050182792 | Israel et al. | Aug 2005 | A1 |
20050197946 | Williams et al. | Sep 2005 | A1 |
20050216472 | Leon et al. | Sep 2005 | A1 |
20050232227 | Jorgenson et al. | Oct 2005 | A1 |
20050240529 | Thomas | Oct 2005 | A1 |
20050246193 | Roever et al. | Nov 2005 | A1 |
20050267894 | Camahan | Dec 2005 | A1 |
20050278375 | Mitchko et al. | Dec 2005 | A1 |
20050283394 | McGloin et al. | Dec 2005 | A1 |
20060008256 | Khedouri et al. | Jan 2006 | A1 |
20060015489 | Probst et al. | Jan 2006 | A1 |
20060041748 | Lockhart et al. | Feb 2006 | A1 |
20060048132 | Chen et al. | Mar 2006 | A1 |
20060062426 | Levy et al. | Mar 2006 | A1 |
20060074754 | Toyohara et al. | Apr 2006 | A1 |
20060107046 | Raley et al. | May 2006 | A1 |
20060112101 | Young | May 2006 | A1 |
20060143264 | Payne | Jun 2006 | A1 |
20060161604 | Lobo | Jul 2006 | A1 |
20060167751 | Maruyama | Jul 2006 | A1 |
20060167816 | Wang et al. | Jul 2006 | A1 |
20060212722 | Ginter et al. | Sep 2006 | A1 |
20060229929 | Hughes | Oct 2006 | A1 |
20060242640 | Pauly | Oct 2006 | A1 |
20060272026 | Niwano et al. | Nov 2006 | A1 |
20060277096 | Levitus | Dec 2006 | A1 |
20060287966 | Srinivasaraghavan et al. | Dec 2006 | A1 |
20070011156 | Maron | Jan 2007 | A1 |
20070011178 | Dumitru et al. | Jan 2007 | A1 |
20070011709 | Katz et al. | Jan 2007 | A1 |
20070028269 | Nezu et al. | Feb 2007 | A1 |
20070033531 | Marsh | Feb 2007 | A1 |
20070050467 | Borrett et al. | Mar 2007 | A1 |
20070073694 | Picault et al. | Mar 2007 | A1 |
20070083471 | Robbin et al. | Apr 2007 | A1 |
20070106522 | Collins | May 2007 | A1 |
20070108274 | Boardman et al. | May 2007 | A1 |
20070192352 | Levy | Aug 2007 | A1 |
20070208670 | Quoc | Sep 2007 | A1 |
20070220051 | Brentano et al. | Sep 2007 | A1 |
20070261088 | Phillips et al. | Nov 2007 | A1 |
20070265969 | Horwat et al. | Nov 2007 | A1 |
20070266028 | Muller et al. | Nov 2007 | A1 |
20070266047 | Cortes et al. | Nov 2007 | A1 |
20080040379 | Suitts et al. | Feb 2008 | A1 |
20080071614 | Mebruer | Mar 2008 | A1 |
20080120199 | Pirnack et al. | May 2008 | A1 |
20080133594 | Fotinatos et al. | Jun 2008 | A1 |
20080140493 | DeAngelis | Jun 2008 | A1 |
20080140537 | Powell | Jun 2008 | A1 |
20080147530 | Kwan et al. | Jun 2008 | A1 |
20080147558 | Kraus | Jun 2008 | A1 |
20080155552 | Kim | Jun 2008 | A1 |
20080195651 | Rachmiel et al. | Aug 2008 | A1 |
20080249946 | Candelore | Oct 2008 | A1 |
20080288405 | John | Nov 2008 | A1 |
20080301058 | Campbell et al. | Dec 2008 | A1 |
20090037287 | Baitalmal et al. | Feb 2009 | A1 |
20090063543 | Martin et al. | Mar 2009 | A1 |
20090138117 | Bagwell et al. | May 2009 | A1 |
20090198830 | Zhang et al. | Aug 2009 | A1 |
20090240552 | Yang | Sep 2009 | A1 |
20090259502 | Erlewine et al. | Oct 2009 | A1 |
20090260060 | Smith et al. | Oct 2009 | A1 |
20090276332 | Gharabally et al. | Nov 2009 | A1 |
20090276333 | Cortes et al. | Nov 2009 | A1 |
20090276433 | Fosback et al. | Nov 2009 | A1 |
20090307201 | Dunning et al. | Dec 2009 | A1 |
20090307682 | Gharabally | Dec 2009 | A1 |
20090307683 | Gharabally | Dec 2009 | A1 |
20100114739 | Johnston | May 2010 | A1 |
20100115443 | Richstein | May 2010 | A1 |
20100205274 | Gharabally et al. | Aug 2010 | A1 |
20100235254 | Chu et al. | Sep 2010 | A1 |
20100235889 | Chu et al. | Sep 2010 | A1 |
20100251099 | Makower et al. | Sep 2010 | A1 |
20100299219 | Cortes et al. | Nov 2010 | A1 |
20110023001 | Giffel | Jan 2011 | A1 |
20110035579 | Miura et al. | Feb 2011 | A1 |
20110060776 | Suitts et al. | Mar 2011 | A1 |
20110197285 | Ginter et al. | Aug 2011 | A1 |
20120023015 | Mathai et al. | Jan 2012 | A1 |
20120110317 | Scheer et al. | May 2012 | A1 |
Number | Date | Country |
---|---|---|
1 684 223 | Jul 2006 | EP |
1684223 | Jul 2006 | EP |
2 230 620 | Sep 2010 | EP |
2002-328852 | Jan 1900 | JP |
A 2002-041482 | Feb 2002 | JP |
2006-519637 | Aug 2006 | JP |
A 2006-272000 | Oct 2006 | JP |
A 2007-220062 | Aug 2007 | JP |
A 2008-142548 | Jun 2008 | JP |
A 2009-048340 | Mar 2009 | JP |
WO 9704410 | Feb 1997 | WO |
WO 9849644 | Nov 1998 | WO |
WO 0008909 | Feb 2000 | WO |
WO 0248920 | Jun 2002 | WO |
WO 2004019182 | Mar 2004 | WO |
Entry |
---|
“Liquifier Pro 4.0 for Windows™ User's Guide,” 1998, Liquid Audio, Inc. |
Radified Guide to Ripping & Encoding CD Audio, http://mp3.radified.com, downloaded Oct. 7, 2003, pp. 1-5. |
“Music Collector Features,” Collectorz.cona music collector features, http://www.collectorz.com/music/features.php, downloaded Oct. 7, 2003, pp. 1-2. |
“Gracenote CDDB,” Gracenote, product webpage, http://www.gracenote.com/gn—products/cddb.html, downloaded Oct. 7, 2003, pp. 1-2. |
“Gracenote MusicID,” Gracenote, product webpage, http://www.gracenote.com/gn—products/music—id.html, downloaded Oct. 7, 2003, pp. 1-2. |
“AVCataloger Overview,” NC Software, Inc. http://www.avcataloger.com/Products.aspx, downloaded Oct. 6, 2003, pp. 1-4. |
Jyri Huopaniemi, “Music Encoding and Transmission,” CUIDAD meeting, ICMC 2000 Berlin, Aug. 28, 2000. |
“Media Encoding FAQ,” Loudeye Corp., http://www.loudeye.com/digitalmedia/solutions/mediaenchost/encodingfaq.asp, downloaded Oct. 9, 2003, pp. 1-3. |
“Media encoding datasheet,” Loudeye Corp., http://www.loudeye.com/digitalmedia/solutions/mediaenchost/encoding.asp, downloaded Oct. 9, 2003, pp. 1-4. |
“Media hosting datasheet,” Loudeye Corp. http://www.loudeye.com/digitalmedia/solutions/mediaenchost/hosting.asp, downloaded Oct. 9, 2003, pp. 1-2. |
“Preview and Convera Announce Availability of Digital Media Commerce Platform for Secure Digital Audio Devices,” Convera Press release, Las Vegas, NV, Consumer Electronics Show, Jan. 8, 2001, pp. 1-3. |
Sonopress Global Network User Manual, Client Tools, Upload Data/Graphics Files to Sonopress, Sonopress, date unknown. |
MPEG-7 Multimedia Description Schemes XM (Version 2.0), ISO/IEC, Mar. 2000, pp. 1-138. |
“Digital Audio Best Practices Version 2.1”, by Digital Audio Working Group, Oct. 2006, http:/www.mndigital.org.digitizing/standards/audio.pdf. |
Vartiainen et al. “Auto-updated”, Proceedings of the 4th International Conference on Mible Technology, Applications, and Systems and the 1st International Symposium on Computer Human Interactionin Mobile Technology, Mobility '07, Jan. 1 2007, p. 683. |
Number | Date | Country | |
---|---|---|---|
20110035508 A1 | Feb 2011 | US |