Patent Publication Number: US-9430797-B2

Title: Digital downloading jukebox system with user-tailored music management, communications, and other tools

Description:
CROSS-REFERENCES TO RELATED APPLICATIONS 
     This application is a continuation of application Ser. No. 14/048,641 filed Oct. 8, 2013, which is a continuation of application Ser. No. 13/308,898 filed Dec. 1, 2011, which is a continuation of application Ser. No. 11/222,036 filed Sep. 9, 2005, which is a continuation in part of application Ser. No. 11/185,974 filed Jul. 21, 2005, which is a continuation in part of application Ser. No. 10/661,811 filed Sep. 15, 2003, which claims the benefit of Provisional Patent Application No. 60/410,832 filed Sep. 16, 2002, the entire contents of each of which are hereby incorporated by reference in this application. 
    
    
     FIELD 
     The instant invention relates to, for example, jukebox systems and, more particularly, to digital downloading jukebox systems of the type which typically include a central server and remote jukebox devices that communicate with the central server for royalty accounting and/or content updates and, still more particularly, to jukebox systems that provide user-tailored music management, communications, and other tools for recognized users using the jukebox system. Exemplary embodiments of the instant invention improve such systems by providing a local server for each jukebox device in the jukebox system network. The local server provides a second and more expansive source of content (e.g., audio and/or visual data) that can be selected by a user of the jukebox device for reproduction on the jukebox device. The local servers may provide a mirror of or subset of the central server, thereby enabling the entire library of audio and/or visual data, or at least the most requested content, to be conveniently available to each jukebox device without the need to download requested content, that is not available on the mass storage device of the jukebox device itself, from the central server. The collective group of local servers may also act as a network of distributed content servers that can be controlled by the central server through each jukebox device to provide services to other devices, such as, for example, other jukebox devices. In addition, the jukebox device and local server can, under control of the central server, operate as a “central hub” or management device for various downloadable fee-based devices present in a location with the jukebox device. Exemplary embodiments additionally can provide other mechanisms to enhance individual recognized users&#39; experiences, such as, for example, by allowing users to create and manage playlists that can be retrieved on one or more jukeboxes, create and manage buddy lists that can send messages to individuals or broadcast to large groups of individuals, etc. In other words, in one embodiment, the jukebox includes features which enable the jukebox to recognize specific jukebox users, through prior registration or the like, and to provide user-specific services to the user. For example, the jukebox may allow the recognized user to create, edit and/or store custom playlists on the jukebox that can be selected by the user or other registered users designated by the creator of the playlist for play on the jukebox. The jukebox may also allow registered users to communicate with other registered users through the jukebox. Registered users may also be provided with credit on the jukebox so that cash is not necessary for using the jukebox services. The jukebox may also be used to provide background music services in addition to convention jukebox services in a unique and advantageous manner as described herein. 
     BACKGROUND AND SUMMARY 
     Jukeboxes have been around for decades and provide users with the ability to select desired music for reproduction in a convenient and advantageous manner. Jukeboxes have conventionally been provided in commercial establishments, such as restaurants and bars, in order to provide desired music on demand for patrons thereof for a fee. Over the last several years, a new generation of jukebox devices have become available that provide significant improvements in the operation thereof for all parties involved. More specifically, the conventional standalone phonorecord and CD jukeboxes are being replaced by digital downloading jukeboxes that are controlled by and communicate with a central server. An example of this new generation jukebox system is shown in U.S. Pat. No. 6,308,204, the entire disclosure of which is incorporated herein by reference. A leading provider of this new generation of jukebox systems is TouchTunes Music Corporation. 
       FIG. 1  shows an overview of an exemplary embodiment of a digital downloading jukebox system  10  (hereinafter referred to simply as a “jukebox system”). As shown in FIG.  1 , the jukebox system  10  includes a central server  12  that contains a master library of audio content (typically music), as well as or alternatively audiovisual content (typically music and associated video or graphics), that can be downloaded therefrom. The jukebox system also includes a series of remote jukebox devices  16 ,  16   a - 16   f . Each of these jukebox devices are generally located in a bar, restaurant, club or other desired location, and are operable to play music in response to receiving a payment from a user, such as coins, bills, credit/debit card, etc., and having one or more songs selected by the user for play. In an alternative embodiment, a music service is paid for on a subscription basis by the location, and the selected music is free for the end-user. The jukebox device  16  typically includes a screen  18  that presents information to the user and allows the user to select songs therefrom, as well as an audio system  20  that plays the selected songs. The screen  18  may also be used for displaying song-related video or graphics. The screen  18  may also be used to display advertisements for the jukebox itself in order to attract customers thereto, to display other types of advertisements, and/or to display any other desired information. 
     The jukebox devices  16  (sometimes referred to as simply “jukeboxes” herein) are operable to communicate with the central server  12  through a communications network  14 , such as, for example, the Internet. The jukeboxes  16  periodically communicate with the server  12  in order to provide information to the server  12  regarding the specific songs that have been played on the jukebox. The central server then uses this information in order to determine the appropriate royalties and/or other payments that are owed for songs played on each jukebox. Thus, one significant advantage of this new generation of jukeboxes is that the sound reproduction and/or other applicable music rights can be adhered to in a more accurate and reliable manner, thereby assuring the proper royalties are paid to the artists or music owners. The central server  12  can also provide new songs to the jukebox  16  in order to assure that the appropriate or most popular songs are maintained on the jukebox based on the specific customers at that location. Thus, the songs available on each jukebox can be customized through communication with the central server in order to provide the songs and/or types of music that customers generally request at each jukebox location. As described in the above-referenced U.S. Pat. No. 6,308,204, the central server can also advantageously be used to update the operating software on the jukeboxes in order to, for example, change the operation of the jukebox, such as to provide new or improved features. Thus, another significant advantage of this new generation of jukeboxes is that the songs (or other audio and/or visual content), and the operation of the jukebox itself can be remotely changed as desired without the need to have someone (such as a routeman) personally service the jukebox. Instead, such updates can be done using the central server  12 . 
     As indicated above, the jukebox devices  16  each include a mass storage device, such as a hard drive, which stores the songs and associated video/graphics data (if any), as well as any other desired graphical information for reproduction on the jukebox. The mass storage device of the jukebox typically has limited storage capacity relative to the storage device of the central server  12 . As a result, only a fraction of the songs stored on the central server are actually stored on the mass storage device of the jukebox at any one time. There may be other reasons as well, such as for security of the data or limited room in the jukebox itself, for having limited storage capacity on the jukebox and/or limiting the number of songs stored thereon. For example, physical space may be limited on wall-mount jukeboxes or the like, which are designed to be small in size as compared to free-standing models. As explained above, the songs on the jukebox can be changed through communication with the central server, but any one jukebox only stores a small subset of the complete library of songs maintained by the central server at any one time. 
     In order to maximize the revenue that a jukebox generates it is important to make the most desired songs available on the jukebox over time. If customers cannot find songs they like on the jukebox, usage of the jukebox (and the revenue generated thereby) will dramatically decrease. On the other hand, it is impossible to predict in advance exactly what a customer at any particular location will desire to play on the jukebox. In fact, there are likely many instances where a customer would have selected a song that exists on the central server but is not currently present on the jukebox. As a result, the jukebox may not be enjoyed and used to its fullest extent. In order to address this problem and increase revenue, jukebox systems have in the past provided a feature which enables the user to search for songs on the central server from the jukebox and request an immediate download of a desired song from the central server to the jukebox for an additional fee. This feature enables the user to play any song in the master library of songs maintained by the central server using the jukebox, regardless of whether or not the specific song is presently stored in the mass storage of the jukebox itself. Thus, the user can first look for desired songs on the local storage of the jukebox and then, if desired, search further on the central server for desired songs. The jukebox device typically charges an additional fee (such as five credits instead on one credit) for an immediate download and play of a song from the central server as opposed to a standard play directly from the jukebox&#39;s local storage. 
     One problem, however, with the immediate downloading feature is that it is desirable to have an immediate and high speed connection with the central server to implement. In addition, the central server and network must be prepared for and capable of handling such requests in a reliable and efficient manner for the feature to properly operate. These requirements cannot always be met and, as a result, implementation of this feature has been limited. For example, many locations that have jukeboxes do not have high speed connections (such as DSL) and instead use dial-up modem connections. Jukeboxes which rely on dial-up connections generally are only designed to communicate with the server periodically and do not allow the user to immediately download a song. They have, however, enabled a user to vote for a song to be downloaded at a later time when the dial-up connection is made. This, of course, is not as satisfying to the user as being able to immediately download a song. Other problems can arise in connection with this download feature if the network or server is not currently available for the download, due to traffic, malfunctions or the like. 
     For most users, a relationship with a jukebox extends only as far as a choice of songs to play. Casual users may find it difficult to make selections rapidly and/or to locate specific songs. Regular users, however, frequently choose the same songs, and they may become frustrated with always having to make the same selections. Both problems may result in a loss of revenue from intimidation, frustration, etc. 
     Thus, it is a feature of the exemplary embodiments to create a relationship between the jukebox and the patrons, in view of the further feature of creating a relationship with a whole community of jukebox users. Such a system can establish a trust relationship between the jukebox and the patrons, while also creating a sense of ownership for the patrons by allowing them to customize their services and communicate with their friends. Such a relationship and feeling of ownership can greatly increase the convenience of using a jukebox and its related services while also decreasing intimidation, frustration, etc. 
     In certain exemplary embodiments described herein, the jukebox can be made the centerpiece for music services as well as other services that enhance the experience of users as well as the revenues of location managers. For example, a jukebox can become a contact point at a given location through which users can reach out to their friends. For instance, users may call a get together using the jukebox, share music through the jukebox system, or meet up at a jukebox if they become separated at a crowded club. Similarly, a jukebox can become, for example, a contact point at a given location through which the manager of the location can reach out to customers. For instance, a manager can advertise specials, notify regulars of special events, etc. Such communications can be initiated by users, by location managers, or by the jukebox itself. 
     There is a need for an improved jukebox system that addresses various needs of users, location owners and operators. The instant invention is designed to address these and other issues and to provide enhanced functionality for such jukebox systems. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       These and other features, objects and advantages of the instant invention will be further understood by review of the following detailed description of the exemplary embodiments when read in conjunction with the appended drawings, in which: 
         FIG. 1  is a block diagram of a conventional downloading digital jukebox system; 
         FIG. 2  is a block diagram of the improved downloading digital jukebox system in accordance with a preferred embodiment; 
         FIG. 3  is an exemplary screen shot showing an initial selection screen in accordance with a preferred embodiment of the jukebox system; 
         FIG. 4  is another screen shot showing an exemplary search screen for use in searching for songs on the local server in accordance with a preferred embodiment; 
         FIG. 4A  shows an exemplary process for using a Personal Music Assistant to search for songs that might be appropriate for a user-specified profile; 
         FIG. 4B  shows an exemplary process for using a Personal Music Assistant to search for songs that might be appropriate for a recognized user&#39;s profile; 
         FIG. 4C  is an exemplary screen shot showing a non-limiting list of genres and themes available to a user in accordance with one illustrative embodiment; 
         FIG. 5  is another exemplary screen shot showing the results of a search on the local server and providing the user an option of downloading a desired song to the jukebox device for a fee, in accordance with a preferred embodiment; 
         FIG. 5A  shows an exemplary process for searching through a list of popular songs; 
         FIG. 6  is another exemplary screen shot showing an alternative method of allowing access to the downloading feature; 
         FIG. 7  shows a block diagram of a preferred embodiment of the local sever; 
         FIG. 8  shows a block diagram of an exemplary overall network including commercial jukeboxes and residential jukeboxes, as well as other downloading devices and associated connections that are managed by the jukebox system; 
         FIG. 9  shows an overhead view of an exemplary establishment layout for a multi-zone jukebox system; 
         FIG. 10  shows an overhead view of an exemplary establishment layout for a multi-zone jukebox system with selection terminals in each zone; 
         FIG. 11  is a flowchart showing an exemplary implementation of a zone selection process for a multi-zone jukebox system; 
         FIG. 12  is a flowchart showing an exemplary implementation of a priority play by zone selection process for a multi-zone jukebox system; 
         FIG. 13  shows an exemplary implementation of a multi-zone set of priority and non-priority queues, with a subset of queues for each zone; 
         FIG. 14  is a flowchart showing an exemplary distribution and initialization scheme for a jukebox with morph capability; 
         FIG. 15  is a flowchart showing an exemplary implementation of an automatic jukebox morph initiation process based on a triggering event; 
         FIG. 16  is a flowchart showing an exemplary implementation of a jukebox morphing process; 
         FIG. 16A  is an exemplary screen shot showing how a morph of a jukebox can be initiated in one preferred embodiment; 
         FIG. 16B  is another exemplary screen shot showing how a user can specify various criteria before a morph of a jukebox in one preferred embodiment; 
         FIG. 17  shows the relationship between a jukebox with expanded media storage and a central server; 
         FIG. 18  is a flowchart showing an exemplary process for a song selection process when a song is not in the “standard” available playable song list; 
         FIG. 19  is a flowchart showing an exemplary process for a priority play queue with prioritization-based-on-bidding capability; 
         FIG. 20  is a flowchart showing an illustrative process for using a user-tailored system for managing music, communications, etc. in accordance with one exemplary embodiment; 
         FIG. 21A  shows non-limiting, illustrative options available for editing account/profile information in one exemplary embodiment; 
         FIG. 21B  shows non-limiting, illustrative options available for managing music in one exemplary embodiment; 
         FIG. 21C  shows non-limiting, illustrative options available for managing buddy lists in one exemplary embodiment; 
         FIG. 21D  shows non-limiting, illustrative options available for communicating with others in one exemplary embodiment; 
         FIG. 21E  shows non-limiting, illustrative options available for accessing value-added content in one exemplary embodiment; 
         FIG. 22  is an exemplary screen shot of a login page in accordance with one exemplary embodiment; and, 
         FIG. 23  is an exemplary screen shot showing the features available after a recognized user has logged in, in accordance with one exemplary embodiment. 
     
    
    
     DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS 
     Referring now to the drawings,  FIG. 2  shows a block diagram of an exemplary preferred embodiment of an improved jukebox system  10 ′. The jukebox system  10 ′ includes similar elements as shown in  FIG. 1  and described above, including a central server  12 , communications network  14 , and remote jukebox devices  16 ,  16   a - 16   f . However, the jukebox system  10 ′ further includes local servers  22 ,  22   a - 22   f  respectively connected to each of the jukebox devices  16 ,  16   a - 16   f . The central server  12  includes a master library of songs (and/or other content). Each of the jukebox devices includes a subset of the master library on a local storage device of the jukebox. The central server may be used to individually manage the contents of the jukebox device, by monitoring usage of and updating the subset of songs on each of the jukebox devices with the intent of maximizing the usage thereof. The central server  12  periodically receives data from each of the jukeboxes for the purpose of royalty accounting and payment for songs played. The jukebox devices may connect to the network in any suitable manner, such as dial-up modem or broadband modem (e.g., DSL, cable, wireless broadband, or satellite). The communications network  14  may be any suitable network capable of distributing data (e.g., audiovisual data) from the central server  12  to the jukeboxes  16  and enabling data to be uploaded from the jukeboxes  16  to the central server  12 . 
     The songs (and/or other data) are preferably digitized, compressed and encrypted by the central server  12  prior to sending songs to the jukeboxes for security and bandwidth purposes using known techniques. The songs are then decompressed and decrypted by the jukeboxes for storage and reproduction thereon. Thus, each of the jukeboxes maintains in a database a library of digitized songs for play on the jukebox, wherein the library can be changed or updated through communication by the central server. The jukeboxes preferably also receive and store data constituting images (e.g., still and/or moving video and/or graphical images) that can be displayed on the display  18  of the jukebox device  16 . In one exemplary embodiment of the invention, the jukebox devices have similar structure and operation described in U.S. Pat. No. 6,308,204 referenced above. Thus, the jukebox devices  16  each preferably include one or more microprocessors, such as a main CPU and an audio DSP, a memory, such as a hard drive, for storing songs and/or other content, a display of displaying visual items, an audio arrangement  20  for providing audio, a communication system for enabling the jukebox to communicate with the central server  12  through the communications network  14 , and operating software, preferably including a multitasking operating system, that controls the operation of the jukebox. The operating software is also preferably updateable through communication with the central server  12  as described, for example, in U.S. Pat. No. 6,308,204 referenced above. The jukeboxes  16  further include one or more payment devices, such as coin, bill and/or credit card input devices, for enabling a customer to pay for usage of the jukebox device in a convenient manner. The screen  18  is preferably a touch screen that enables the user to input selections by touching the screen. 
     Each jukebox device has, in one embodiment, a local server  22  that can be accessed by the jukebox device. The local servers are respectively connected to the jukebox devices using Ethernet or other type of local connection. The local servers  22  each preferably include a mirror copy of the master library of musical recordings maintained by the central server  12 . The local server  22  can be loaded with the master library by the entity that owns and/or controls the jukebox network prior to shipping the local server and jukebox device to the jukebox distributor or operator. Of course, over time, the local sever will no longer correspond identically to the central server, due to the fact that the central server is preferably continually updated with additional or new songs. Thus, the local servers  22  are also preferably updated periodically to maintain a correspondence with the library on the central server  12 . This updating can be done, for example, by the central server  12  through communication with the jukebox devices connected with the local servers  22  using, for example, either dial-up or broadband modems. Alternatively, the updating can be done personally with an update tool that can be connected by a routeman or other person directly to the jukebox or local server for the purpose of updating the contents of the local server. The portable tool could include a removable storage medium, such as a hard drive, that could be returned to and reused by the owner of the jukebox system for future updates. The tool itself could be kept by the operator or other person in charge of maintaining specific jukeboxes for use upon receipt of the updated removable storage medium from the owner of the jukebox system. 
     For security reasons, the local server  22  preferably does not include all of the digital data that constitutes any one song that is stored on the local server  22 . In addition, the part of the song that is on the local server is encrypted. The jukebox device  16  contains the missing part of each of the songs on the local server, thereby enabling the jukebox to assemble the complete song based on the contents of the local server and the memory on the jukebox device. The missing data located on the jukebox is needed in order to decrypt the songs. For example, a single block (or other small fraction) of data for each song may be missing on the local server but present on the jukebox device, and the encryption may be based on the missing block and may proceed on a block by block basis. Thus, none of the blocks can be decrypted without obtaining and/or decrypting a preceding block. This feature provides significant security and prevents or deters theft or other type of unauthorized use or copying of the songs on the local server. Thus, in this embodiment, each local server must be specifically assigned to a specific jukebox device so that the decryption described above can be properly performed. 
     In accordance with a preferred exemplary embodiment, the local servers may also each be individually registered with and identified to the central server  12 , so that the central server can individually manage and monitor each local server. The same is true for the jukebox device itself, i.e., it may also preferably be registered with the central server so that it too can be individually monitored and managed by the central server. As will be understood from the foregoing description, the local servers become an important and advantageous part of the jukebox system by allowing the contents thereof to be accessed by the jukebox device to provide additional services (such as providing additional songs) not available on the jukebox device itself. As will be explained below, the song library of the central server and/or the storage capacity itself can be advantageously used to provide services to other jukeboxes, such as fee-based residential and commercial jukeboxes and/or other fee-based equipment. One preferred use of the local servers may be to provide an immediate song downloading feature for the jukebox device will now be described below in detail with reference to the exemplary screen shots of  FIGS. 3-6 . 
       FIG. 3  shows an exemplary screen shot for a music selection screen  30  as displayed on the touch display of the jukebox device. As can be seen in  FIG. 3 , this selection screen, which is preferably the initial selection screen displayed to a customer, includes graphical representations  32  of the various album covers for songs that are stored in the memory of the jukebox device. The albums covers are shown in alphabetical order and the virtual slide bar  33  can be used to scroll through the available albums. Up and down arrows ( 34  and  35 ) are also provided for stepping through the available albums. A “Now Playing” button  36  is also provided for showing information on the song currently playing on the jukebox (if any). A “Top Ten” button  38  is also provided for showing a list of the ten most popular songs on the jukebox. A “Tune Central” (TM of TouchTunes Music Corporation) button  39  is also provided, the function of which will now be described in detail with reference to  FIG. 4 . 
     If the user does not see an album of interest in the display of album covers or desires for any reason to search for available songs that are not present on the jukebox device, the user may select the “Tune Central” button  39 . When the “Tune Central” button is pressed, the display on the jukebox is changed from that of  FIG. 3  to that of  FIG. 4 . The exemplary screen shot of  FIG. 4  shows a search screen  40  which enables a search to be performed on the local server  22  connected to the jukebox device. This screen  40  provides a virtual keyboard  42  for use in entering a search request. The search can be done by album, artist, song, or genres or themes (i.e. categorized lists of songs, preferably based on popularity, that help a user find a particular song), based on the associated buttons  47 . Once a search is typed, the user touches the “Search” button  44  and a search of the contents of the local server is initiated. Input from the virtual keyboard can be cleared using the “Clear” button  46 . 
     Genres may comprise, for example, “pop,” “rock,” “country,” “rap,” “R&amp;B,” “Blues,” etc. Themes may comprise, for example, “Christmas,” “Irish,” “Birthday,” etc. In some exemplary embodiments, these lists can be retrieved from the server, while in other exemplary embodiments the lists may be built dynamically, based on, for example, certain parameters. In still other embodiments, the server may select which lists to enable or send to the jukebox based on criteria, such as, for example, location, music type, etc. A system might only display genres and/or themes for which music is downloaded. However, a system might display all genres and/or themes and enable download of other songs not available to the local jukebox. It also will be appreciated that although  FIG. 4C , discussed in detail below, shows the genres and themes on the same screen, other embodiments may present them separately. 
       FIG. 4C  is an exemplary screen shot showing a non-limiting list of genres and themes available to a user in accordance with one illustrative embodiment. Buttons  450  arranged on the left side of the screen correspond to themes available to a user, while buttons  460  arranged on the right side of the screen correspond to genres available to a user. Button  470  exits this selection mechanism. It will be appreciated that other arrangements of the buttons are available, and that the list of themes and genres provided is for non-limiting, illustrative purposes only. 
     Similar to the genres and themes search, a user may, for example, search for a song using a Personal Music Assistant, an exemplary process for which is shown in  FIG. 4A . Preferably, after pressing a Personal Assistant button (step  402 ), the jukebox would ask certain information to identify the user if the user is not already identified (step  404 ). Such information could include, for example, age (or date of birth), preferred style, background, place of birth, or other information that could be used to generate a profile of the user. The jukebox then preferably could compare the profile information to selections made by other users with similar profiles (step  406 ) from, for example, the specific jukebox, the particular establishment, or a national database and recommend songs (step  408 ). For example, the jukebox might suggest a song by “The Doors” to a male user from California who was born in 1960. The user could then choose a song from that list or initiate a new search (step  410 ). 
     Furthermore, instead of entering identifiers, as shown in  FIG. 4B , the Personal Music Assistant could recognize a user in other ways (step  422 ), such as, for example, after a credit card or a pre-programmed site-specific identification card is swiped by the jukebox. Preferably, the Personal Music Assistant would maintain a list of selections made by the user. The user&#39;s list of selections could be maintained, for example, on a local jukebox terminal, on a site&#39;s central jukebox server, on a remote server, or on an identification card, etc. After the Personal Music Assistant recognizes the user, it could then recommend songs based on, for example, songs by the artists the particular user enjoys (step  426 ), songs played frequently by the user ( 428 ), songs not heard recently by the user ( 430 ), etc. 
     Additionally, a Personal Music Assistant recognizing, for example, a preferred customer or a customer with a large number of credits might morph the jukebox into a jukebox more enjoyable to that specific user. Credits could be, for example, purchased by the user; or given to the user as a reward, for example, for purchasing drinks or souvenirs at an establishment, or for being a regular repeat customer. Thus, a Personal Music Assistant could be implemented in a manner that makes selecting songs a more enjoyable, dynamic, and responsive process while removing the immediate pressure placed on the user to know which song to choose. 
     When a search is initiated from screen  40 , the screen changes to that shown in  FIG. 5  to display the results of the search. As shown in  FIG. 5 , the results of the search are listed. More particularly, in this example, a list of songs that satisfy the search request are listed. The list could also be by album if the search was album based. The user can scroll through the search results using slide bar  53 . The user is also shown a display  55  of the number of current credits and a display  56  of the number of credits that are required to download a song from the local server to the jukebox device. The user can go back to the previous screen by touching the “Back” button  57 . If the user selects a song from the search list and then touches the “Get It Now” button  54 , the jukebox is operable to immediately download the selected song from the local server to the jukebox for play on the jukebox. The downloaded song can be queued up with any other selected but unplayed songs (if any) for play on the Jukebox. In this example, the download costs five credits instead of one credit like a normal selection from the storage of the jukebox itself. Once the downloaded song is played, it is preferably deleted from the jukebox device (together with any graphical data, such as the album cover graphic) that was also downloaded from the local server in connection with the song download). In this way, the user has the option, through use of the “Tune Central” button, to temporarily obtain on the jukebox any song from the master library of recordings without the need to contact the central server  12 . As a result, the jukebox provides a more enjoyable experience for the user, while also increasing revenue generated thereby. 
     Also providing an enjoyable experience for the user is the central servers&#39; capability to identify “hot hits,” preferably in real-time. Preferably, new songs could be made available in a master catalog—that is, they need not reside on local servers or expanded media storage. Then, songs played frequently in a given area (ranging from, for example, a single site or group of sites, to a state or country, to a global connection) could be identified as popular. These songs, or “hot hits,” preferably could be downloaded by, or sent to, individual jukeboxes. Individual jukeboxes preferably would maintain lists of “hot hits” in real-time, allowing users to search through the most popular songs at any given time. Alternatively, a jukebox might maintain a list of “hot hits” without downloading the popular songs, thereby potentially saving download time and resources. As a result, the jukebox could provide an enjoyable experience for the user by providing easy access to the most popular songs. 
       FIG. 5A  shows an exemplary process for maintaining a “hot list” on a jukebox with a broadband connection. It should be noted that the same process could apply for a system with a different type of connection, though more time and resources may be used to download a song over a slower connection. In step  502 , songs from a master catalog are received by a site&#39;s central server. Of course, it should be noted that songs could be stored to a local jukebox&#39;s storage media. In step  504 , a user using a jukebox terminal would select a “Hot List” button. After the “Hot List” is displayed (step  506 ), the user could select a particular song or initiate a new search ( 508 ). 
       FIG. 6  shows another exemplary screen shot of a song selection screen  60  that is displayed when a user touches an album cover graphic from the screen  30  of  FIG. 3 . Thus, this screen shows an alternative (or typical) method of selecting a song, wherein the song is selected directly from the subset of songs that are directly available from the storage device of the jukebox itself (rather than the local server). In this example, Joe Cocker&#39;s Greatest Hits was selected from the screen of  FIG. 3 . As shown in  FIG. 6 , the resulting screen display  60  shows the selected album graphic  61  and a list of the songs  62  that are available on the jukebox for that album. The jukebox may or may not include all of the songs for a particular album. The available songs can be scrolled through if necessary using scroll bars  63   a  and  63   b . The user has the option, through the “Play” button  65 , to select a song from the list for play on the jukebox. A “Play Now” button  66  is also provided for enabling the user to select a priority play of the song, thereby giving the song a higher priority than songs selected using the “Play” button  65 . This priority feature preferably requires more play credits than the normal play. A display  67  shows the number of credits available for the user. Button  64  shows other albums for the same artist being shown at  61 , thereby enabling a user to easily search through the albums for a particular artist for a desired song. 
     As also shown in  FIG. 6 , a “Tune Central” button  68  is displayed that enables the user to search for songs by this same artist on the local server as explained in connection with  FIG. 4 . In other words, button  68  takes the user to the search screen  40  of  FIG. 4  for searching the local server. The user can then proceed to search the local server and select songs therefrom, if desired, as described above in connection with  FIGS. 4 and 5 . Thus, as explained above, the user can access the local server at various screens in a convenience and efficient manner, depending on the desires of the user when interacting with the jukebox screen. 
     As can be seen from  FIGS. 3-6 , the user is provided with the option of playing songs that are resident on the jukebox device itself or, alternatively, selecting songs from the local server for download and play in an efficient and reliable manner, thereby significantly improving the operation of jukebox systems, particularly those that cannot quickly, easily or reliably receive downloads of music on demand from a central server. It is noted that the screen shots of  FIGS. 3-6  are only exemplary and any suitable screen configurations can be used to provide the functionality described herein. In addition, the jukebox operator is provided with the ability through operator screens (not shown) to set filters per genre or style of music in order to limit access to the end user and avoid undesirable music being played at a specific location. 
     In still other exemplary embodiments, a location might provide a “Virtual DJ.” According to one such system, a prepared playlist would be provided to the jukeboxes of a location. Preferably, the playlist can be tailored to the details of the location and/or the event to take place, such as, for example, locale, theme, target audience, etc. Furthermore, some illustrative playlists could be created by famous DJs to attract patrons. DJs could attach their names to playlists and associate themselves with various locations, even though they are not present. A playlist might extend for several songs or for several hours, depending on the needs of the location. It is to be appreciated that coinage need not be collected during such a Virtual DJ event, as a special fee can be associated with the service of using a special playlist. It also is to be appreciated that DJs may prepare special playlists for one-time use, or they may make available repeatable special playlists. These repeatable playlists may, for example, be downloaded by jukeboxes or provided to the jukebox in any suitable manner. Thus, making third part playlists available for use on the jukebox for a fee provides a whole new revenue source for the jukebox operators, location owners and playlist generators, such as well-known DJs or the like. When a playlist is made active, the normal functions of the jukebox are preferably stopped during play of the songs on the playlist. 
       FIG. 7  shows a block diagram of the electronic elements that define the local server  22  in accordance with an exemplary embodiment. As shown in  FIG. 7 , the local server  22  includes a CPU  72  (e.g., AMD Elan 100 MHz), a flash memory (e.g., 8 MB) containing the BIOS and OS, a pair of master/slave hard drives ( 82 ,  84  and  86 ,  88 , respectively), a pair of IDE controllers  78  and  80  for the hard drive pairs respectively, a RAM  76  (e.g., 32 MB), an Ethernet controller for controlling communication with the jukebox device  16 , and the appropriate buses interconnecting the various elements. Of course, other configurations or arrangements for the local server  22  may be used. A unique identifier may be provided in the local server for enabling the local server to be uniquely identified and registered by the jukebox and/or central server. The identifier may, for example, be located in the flash memory  74 . 
     As will be appreciated from the description of the invention above, the addition of the local server significantly enhances the operation of the jukebox devices that are part of a jukebox system. However, the local servers also provide other benefits and features that will now be described. 
     A collection of local servers  22  may be used as a network of distributed servers that can be controller by the central server  12  through its associated jukebox device  16  to provide music services to other devices. For example, the local servers and associated jukebox can be used to deliver requested songs to a dedicated residential or commercial jukebox device (or other suitable jukebox device) in addition to providing song services to the specific jukebox to which it is connected and assigned. Thus, the network of distributed servers can provide a support network for implementing residential and commercial jukeboxes of the type which allow a user to download songs for reproduction and/or storage at a residential or commercial location for an appropriate fee. As a result, the jukebox system operator can provide and control commercial jukeboxes and well as residential jukeboxes through the jukebox system. In this embodiment, the jukebox device and/or local server are connected to the Internet (or other suitable network) using a broadband modem and is provided with software that can selectively deliver song files to any dedicated residential jukebox device (also connectable to the Internet) under control of the central server. The central server receives requests from a residential jukebox and, by analyzing traffic on the network, provides instructions to a selected jukebox device to download the requested song file (either from its memory or from the local server) to the residential jukebox for a fee or under a subscription plan for the residential jukebox. 
     In accordance with another exemplary aspect of the invention, the local server and jukebox device are used, under control of the central server, to provide management services for other types of coin operated or payment triggered equipment, such as gaming devices, installed in the same location as (or in close proximity to) the jukebox. In other words, the jukebox system is preferably used to update the functionality of and/or manage other downloading devices present in the same location. As a result, the jukebox becomes a “central hub” for all downloading equipment in a location. This feature is achieved, in one embodiment, by networking all of the downloading devices in a single location together with the jukebox and local file server. The central server can then download information to the local server together with instructions to the jukebox as to which devices should updated with what data and/or software. The jukebox device and central server can also be used to collect information from the other downloading devices to which it is managing and upload that information to the central server for reporting/accounting purposes. Thus, the owner/operator of the jukebox system can act as a third party service provider to other coin-op companies for the purpose of managing and/or updating their equipment. 
     The large amounts of memory provided by the local servers and the fact that they are provided and accessible at thousands of locations over a well controlled network, turns the jukebox system into a powerful tool that can be used to perform a variety of functions in the coin-op industry. More and more coin-op manufacturers are going towards games that are software upgradeable through their internal hard drives. These updates are done periodically, but as these devices increase there will be an ever increasing need for a system that can reliably and efficiently perform the updates from a remote location. The jukebox system described herein satisfies this need by enabling all suitable electronic coin-op devices at a jukebox location to be managed by the central server using the jukebox and local server at the location. The central server can download software or data updates, store them on the local server and then dispatch the updates to the intended units of equipment in the establishment. Thus, the jukebox system can act as a third party service provider to other companies in the coin-op business, thereby significantly enhancing the functionality of the jukebox system. 
     As an example, there are currently about 140,000 Merit coin-operated countertop devices in the USA, each of which enables users to play games and the like for a fee. Many of these devices operate with a hard drive that can be upgraded with new software. Merit does this by shipping CD-ROMs to operators who then need to drive to each location and manually update each machine. In accordance with the instant invention, however, all suitable coin-op equipment at a location are connected (directly or indirectly) with the local jukebox and local server assigned thereto. This enables the central server to receive the intended software update for any device, together with information that identifies what devices are to be upgraded with what software. The upgrade services are preferably fee based and provide an additional revenue stream for the jukebox system. The central server then downloads the software to the local servers with the upgrade instructions to further download the upgrades to the appropriate device(s). 
     As explained above, the local server enables songs to be downloaded to a commercial jukebox to which it is assigned or to residential jukeboxes under control of the central server. In addition, the local servers can be used for an on-premise networked application which manages other coin-op devices. These various features of the instant invention are illustrated in  FIG. 8 . 
       FIG. 8  shows a block diagram of a complete jukebox system network as contemplated by an exemplary embodiment. As explained above, the system includes a central server  12  connected to a communications network  14 , a series of commercial jukeboxes  16   a ,  16   b  and  16   c  with associated local music file servers  22   a ,  22   b  and  22   c , a series of residential jukeboxes  100   a ,  100   b  and  100   c  connected to the network via broadband devices  102   a ,  102   b  and  102   c , and an on-premise network shown on the right hand side of  FIG. 8 . This on-premise network includes a jukebox device  16   d  connected via a router or network hub  110  to a local file server  22   d , a number of additional coin-op equipment, such as a dart game  104 , a golf game  106  and a countertop videogame  108 , and a broadband modem  112  connecting this local network to the communications network  14 . With this exemplary configuration as shown in  FIG. 8  all of the functionality described herein can be implemented through the jukebox system of the instant invention. 
       FIG. 9  shows an overhead view of an exemplary establishment layout for a multi-zone jukebox system, in accordance with one embodiment of the invention. In accordance with an exemplary embodiment, the establishment has three zones  121 ,  123 ,  125 . Each zone is equipped with its own set of speakers  127 ,  129 ,  131 , which are operably connected to the jukebox  133 . Different music may be played simultaneously in all three zones  121 ,  123 ,  125  and all the music may be played from a single jukebox  133 . The jukebox  133  may be provided with additional hardware, as needed, to allow this implementation. 
     Alternatively, the user may elect to have a song played in more than one of the zones  121 ,  123 ,  125  simultaneously, or in more than one of the zones at different times. The user may have to pay additional credits to implement either of these features. A preferred embodiment of a multi-zone system could play music at a high quality in the different zones using the system described in application Ser. No. 11/023,390, filed Dec. 29, 2004, entitled “Wireless Digital Transmission System for Loudspeakers,” which is a continuation in part of Ser. No. 09/161,584, filed on Sep. 28, 1998. The entire contents of both applications is incorporated herein by reference. Using this system, for example, a jukebox could compress and transmit audio data through AC power lines to an addressable location, where it could be received, decompressed, converted, and played. In fact, any of the jukebox components herein could be implemented in a manner that uses AC power lines as a communication network for operation. 
     It is to be appreciated that Wireless Digital Transmission System can be used for other purposes in other embodiments where data needs to be sent between two or more devices. For example, this system could be used to configure dummy terminals. In such an embodiment, the Wireless Digital Transmission System could be used to send information such as, for example, whether to morph, what songs are appropriate given a particular morphing of the jukebox, the zones in which selected music should be played, maximum volume levels, etc, in addition to sending music to the speaker systems. 
     The operator may also restrict what kind of music is available in a given zone, based on the type of activity in the zone, the time of day, or any other suitable selection criteria. For example, in  FIG. 9 , zone three  125  is a restaurant. Restaurant patrons may not wish to listen to the same type of music as someone in zone one  121 , which is a bar room in  FIG. 9 , or in zone two  123 , which is a pool room. The operator may recognize this and restrict the type of music that can be played in zone three  125 . Alternatively, the operator may restrict the volume of the music in any given zone. For example, patrons of a pool room  123  or a restaurant section  125  may not want the music as loud as it is desired to be in the bar room  121 . And maybe the restaurant section  121  is to be kept quieter even than the pool room  123 . The owner can adjust and control all suitable settings to provide the most versatile, patron friendly environment in each of the zones, based on any suitable criteria. 
       FIG. 10  shows an overhead view of an exemplary establishment layout for a multi-zone jukebox system with selection terminals in each zone. In accordance with an exemplary embodiment, the bar has three zones  121 ,  123 ,  125 . Each zone is equipped with its own set of speakers  127 ,  129 ,  131 , which are operably connected to the jukebox  133 . Different music may be played simultaneously in all three zones  121 ,  123 ,  125  and all the music may be played from a single jukebox  133 . The jukebox  133  may be provided with additional hardware to allow this implementation. 
     In the embodiment of  FIG. 10  there are also one or more “dummy” terminals  137 ,  139  located throughout the establishment. An exemplary illustrative dummy terminal could use X-server technology. These terminals  137 ,  139 , which may be stand alone devices or may be provided as part of the interface on a gaming machine or other suitable device with a digital display, allow selection of songs from the jukebox  133  for the zone in which they are located (or possibly other zones). These terminals  137 ,  139  duplicate the zone restrictions imposed on the main jukebox interface and selection criteria. The terminals  137 ,  139  may be restricted to only allowing selection of music for play in the zone where each respective terminal is located, or they may allow selection for play in one or more different zones. 
     Additionally, the graphical interface of the terminals  137 ,  139  may change in accordance with available selections, themes of the bar, themes of the room in which each terminal is located, or any other suitable criteria. 
       FIG. 11  is a flowchart showing an exemplary implementation of a zone selection process for a multi-zone jukebox system. In accordance with an exemplary embodiment, the jukebox first begins the transaction  141  with the user. The user is instructed to select a song  143 , and select one or more zones  145  in which the song is to be played. The jukebox then determines the price based on the number of zones selected  147 . The jukebox accepts payment from the user  149  and queues the song for play in the selected zone or zones  151 . Next, the jukebox checks to see if the user would like to select another song  153 . If the user wants another song, the process returns to the select song step  143  and repeats from there. If the user is finished making selections, the process ends  155 . 
       FIG. 12  is a flowchart showing an exemplary implementation of a priority play by zone selection process for a multi-zone jukebox system. In accordance with an exemplary embodiment, certain jukebox systems may be provided with one or more priority queues corresponding to one or more zones. If priority play is provided for a zone or zones, the jukebox first checks to see if the user would like to select priority play for the selected song  161 . If priority play is selected, the jukebox then provides an option for the user to choose a zone or zones in which priority play should occur  163 . Based on the number of zones selected for priority play, the jukebox determines a price  165 , and accepts payment of that price  167  from the user. The jukebox then places the song in a priority play queue for each selected zone  169 . 
       FIG. 13  shows an exemplary implementation of a multi-zone set of priority and non-priority queues, with a subset of queues for each zone. In accordance with an exemplary embodiment, each of N zones  171  may be provided with its own set of queues, comprising a priority queue  175  and a non-priority queue  173 . A list of songs selected for play is maintained within each queue  173 ,  175 . Each song in each queue may be provided with an identifier  177 ,  179 , which identifies the song, and/or the position of the song in the queue, and/or any other suitable factors. 
       FIG. 14  is a flowchart showing an exemplary distribution and initialization scheme for a jukebox with morph capability. In accordance with an exemplary embodiment, the contents of a factory drive are defined at the point of manufacture  181 . This same drive (or expanded media storage) may be shipped out with all jukeboxes  183 , and may only contain a subset of the total number of songs available on the central server. Once the jukebox containing the drive has reached its destination, the operator may select a subset of songs on the drive as the basic playable list  185 . This selection can be made based on the type of establishment, the type of music the establishment&#39;s patrons typically prefer, or any other suitable criteria. The operator may also allow the central server to recommend a basic playable list. The drive may also allow selection of songs not on the basic list for an additional fee  187 . This list of “alternate” songs might not include all songs however, as the operator might desire to restrict access to songs that don&#39;t meet the theme of the establishment. For example, a country bar owner might not ever want to allow selection of rap or hip-hop songs on the jukebox. 
     Once the songs on the drive have been appropriately categorized, the jukebox begins operation  189 . As long as a new basic playable list is not desired  191 , the jukebox continues to operate  189  with the currently selected basic playable list. If a new basic playable list is desired  191 , the jukebox morphs  193  into a “new” jukebox, selecting a different playable subset of songs for basic selection  185 , and changing additional characteristics as dictated by the morph. 
       FIG. 15  is a flowchart showing an exemplary implementation of an automatic jukebox morph initiation process based on a triggering event. In accordance with an exemplary embodiment, the user may define an event  201 , for example a themed night or a time of day, as a triggering event which triggers a jukebox morph. The jukebox then operates as normal  203 , checking periodically to see if the triggering event occurs  205 . If the triggering event has not occurred, the jukebox simply continues to operate  203 , but if the triggering event occurs, the jukebox is morphed into a “new” jukebox. The triggering events may be one time events, or they may be scheduled to occur weekly, daily, monthly or scheduled based on any other suitable criteria. It should be noted that in a multi-zone configuration, different zones may be morphed while others do not change. This feature of the illustrative embodiments allows, for example, a given zone or zones to be dedicated to a certain kind of music while the other(s) may vary based on any variety of factors, such as the time of day, an owner&#39;s desire to change the music, or a user&#39;s request. 
       FIG. 16  is a flowchart showing an exemplary implementation of a jukebox morphing process. In accordance with an exemplary embodiment, when the jukebox begins morphing  211 , it selects a new subset of songs to be the basic playable list  213 . The jukebox then allows some or all of the remaining songs on the jukebox to be selected for an enhanced fee  215 . Some of the remaining songs may be restricted based on what triggered the morph. Other characteristics of the jukebox may also change  217 , for example, the user interface may be changed, and different advertising may be displayed which corresponds with the predicted tastes of the crowd for which the jukebox has been morphed. Other suitable changes may also be made. In one example of a preferred embodiment, a club owner has a hip-hop night on Wednesdays, beginning at 9:00 pm and ending at 4:00 am. At 9:00 pm on Wednesdays, the jukebox morphs into a hip-hop jukebox, with a basic selection of appropriate music. In accordance with the morph, the jukebox blocks all access to genres of music such as country music, classic rock, jazz, blues and oldies, and the jukebox limits the available selection of hard rock additional songs to “hip-hop-esque” hard rock songs. The graphics on the jukebox convert to edgy, urban graphics, and the advertising changes accordingly, displaying products such as apparel, drinks, and goods which should appeal to the hip-hop crowd. At 4:00 am, the jukebox morphs back into the “standard” jukebox for that club, or into any other suitable jukebox. Alternatively, the jukebox may remain set in hip-hop mode until the next triggering event occurs. Again, it should be noted that in a multi-zone configuration, different zones may be morphed while others do not change. In the above exemplary non-limiting embodiments, the system might morph into hip-hop in one zone for the night, while the “standard” music for the club remains playing in another area. 
       FIG. 16A  is an exemplary screen shot showing how a morph of a jukebox can be initiated in one preferred embodiment. Area  160  is blank to indicate that no selections have been made. A user will select a morphing option by choosing, in this exemplary embodiment, for example, either TouchTunes Master button  162 , Dynamic Master button  164 , or Clone a Location button  166 . It is to be appreciated that other embodiments may provide further morphing options in place of or in addition to the aforementioned buttons. In this embodiment, pressing the TouchTunes Master button  162  will populate area  160  with a list of master selections pre-selected by the TouchTunes music department. These master selections may include, for example, collections of specific songs (e.g., all songs by British bands, all songs by a particular artist, etc.), ratios of particular themes or genres (e.g., a mix of 75 percent Hip-Hop and 10 percent Pop, 10 percent Rock, and 5 percent techno for a particular dance club feel, etc.), etc. A user may peruse the list using slider bar  170 . Once the user is satisfied, pressing Morph It button  168  will morph the jukebox. It is to be appreciated that pressing the Morph It button  168  may trigger an immediate morph, or it may save the morph and instead initiate it at a predefined trigger time. It also is to be appreciated that morphing data may be stored for morphing the jukebox on which the selection was made or any number of connected jukebox terminals. 
     Pressing Dynamic Master button  164  is one exemplary, non-limiting way of providing increased user control over the morph.  FIG. 16B  is another exemplary screen shot showing how a user can specify various criteria before a morph of a jukebox in one preferred embodiment. A discussion of the buttons with identical numbers in  FIG. 16A  and  FIG. 16B  is omitted. Designations for the genres and/or themes of music are provided, such as, for example, Rap label  172 . To specify a given percentage of music to be played, a user may press increase button  174  or decrease button  176 . The amount of music selected for that particular genre or theme will appear in a theme music amount area  178 , while details about the total amount of music selected will appear in total music amount area  180 . In a preferred embodiment, a user may specify percentages of a genre and/or theme to play. For example, a user may select only 100 percent Country music for a country night. Alternatively, as another non-limiting example, a user may select a mix of World and Latin music for an international feel. It is to be appreciated that although a preferred embodiment uses percentages, other embodiments may use different measures for specifying how many of which type of music should play, such as, for example, the number of songs in a given category, the amount of playtime in a given theme and/or genre, etc. It also is to be appreciated that in other embodiments, a user need not use the buttons to increase or decrease the amount of music; that is, in other embodiments, a user may directly input the amount of music via an input mechanism. 
     When a user presses Clone a Location button  166  (e.g., from  FIG. 16A  or  FIG. 16B ), the jukebox displays a list of the jukebox devices, preferably including a unique identifier for each jukebox device. In other embodiments, however, the list may include, for example, other locations owned by the same owner of the present location, etc. After selecting the jukebox terminal, the present jukebox could morph into that jukebox. Alternatively, the jukebox selected could morph into the present jukebox, thus providing, for example, remote morphing. Still alternatively, the list might include information about non-digital jukeboxes that exist in addition to the digital jukeboxes preferred by the exemplary embodiments. This morphing feature can allow users to replace existing jukeboxes quickly and easily by allowing the new jukebox to morph into an older jukebox that is being replaced, such as a convention record, CD or digital jukebox. 
     Still further, a user can morph a location based on a location&#39;s data, specific to, for example, a given date. This allows users to morph a jukebox based on, for example, the popularity of a given morph—e.g., users may choose to revert to a successful morph to try to recreate the entertainment of that evening. This feature also enables users to recover from hard drive crashes. For example, if a hard drive has been replaced after an old one crashes, a user may morph (or clone) an existing location at a given date and/or time before the crash to restore the songs that were available before the crash because, preferably, the server maintains information sufficient for this functionality. Thus, using the morphing function gives users increased control while also providing backup and restoration features. 
       FIG. 17  shows the relationship between a jukebox with expanded media storage and a central server. In accordance with an exemplary embodiment, the central server  221  contains a master library of songs, such library comprising all songs that are currently available to be downloaded and all songs currently installed on jukebox hard drives. The central server may communicate  222  with the remote jukebox  225  containing a local hard drive  223 . The hard drive  223  on the jukebox may have several sections, including available space for downloads  227 , space occupied by preloaded songs  228 , and space for software and an operating system  229 . Additional suitable sections may be added, for example, a section containing different pictures for altering the GUI. The jukebox  225  may communicate with the central server  221  to download songs, upload usage information, update software, and perform any other suitable functions. 
       FIG. 18  is a flowchart showing an exemplary process for a song selection process when a song is not in the “standard” available playable song list. In accordance with an exemplary embodiment, the user first selects a song  231 . The jukebox checks to see if the song is available on the local hard drive as a “non-standard” selection  233 . If the song is available on the local hard drive, the jukebox charges the customer the price set for obtaining and playing a non-standard song  235  and plays the song  237  (or adds it to a playlist, when appropriate). 
     If the song is not available on the local hard drive, the jukebox checks to see if a high-speed connection to the central server is available  239 . If there is no high-speed connection, the jukebox informs the user that the song is temporarily unavailable  241  and orders the song for download  243 . The jukebox may or may not charge an additional amount for ordering the song. If, however, there is an available high-speed connection to the central server, the jukebox orders the song immediately and uses the high-speed connection to download the song right away, queuing it up for playing  245 . The jukebox then charges the customer the price of a non-standard selection  247 . 
       FIG. 19  is a flowchart showing an exemplary process for a priority play queue with prioritization-based-on-bidding capability. According to an exemplary embodiment, the user first indicates that he would like priority play  251 . The jukebox then displays the current status of the priority play queue  253 . This display may include information such as how many songs are in the queue, what the top bid is, how much has been bid on each song, which songs are “locked in,” and any other suitable information about the priority queue. The jukebox then allows the user to select how much additional money the user would like to pay to place his song in a particular spot on the priority list and accepts payment in the selected amount  255 . After accepting the payment  255 , the jukebox places the song in a position on the priority list corresponding to the additional amount received from the user  257 . 
     Alternatively, in another exemplary aspect of the illustrative embodiments, a user can bid on the right to have a song played before other songs previously selected for priority play are played. In a preferred embodiment, the user is shown the top price paid for a priority play, and can pay more than that price to obtain the highest priority available. 
     Another exemplary aspect of the illustrative embodiments does not allow a user to be shown how much anyone else has paid for priority. The user can pay however much the user desires to spend to obtain a priority ranking, and then receive a ranking of priority based on the amount paid. 
     In accordance with a further exemplary aspect of the illustrative embodiments, a user can pay however much the user desires to spend to obtain a priority ranking in accordance with the previous exemplary aspect, and then be shown the priority spot which has been obtained based on the paid amount. If this spot is not satisfactory to the user, the user can pay additional money to move the song up in priority ranking, and be shown the new priority ranking obtained based on the additional money paid. The user can repeat this process until the desired priority ranking has been obtained. The user can also pay additional money to make it harder for other users to pre-empt the selected priority spot on the list in a bidding-type situation. Any other suitable method of increased-pay-for-increased-priority may also be implemented. 
     In accordance with an additional exemplary aspect of the illustrative embodiments which may provide a “lock in” feature, a user can “lock in” a priority ranking with a payment of a pre-selected amount. For example, if a user pays 15 credits to obtain a ranking of 3 rd  in priority, and wishes to guarantee the third ranking, the user may pay, for example, 4 more credits to “lock in” the ranking Since locking in the ranking may require the “lock in” of all the rankings above the user as well, the user may be required to pay a certain amount to “lock in” all songs above the user&#39;s selection. In one such situation, the user can either choose to pay the price quoted for the “lock in” or pay the same or a varying amount of credits in an attempt to prevent future over-bidding or to move the user&#39;s song up further in the priority list. 
     In accordance with another exemplary aspect of the illustrative embodiments, any of the aforementioned bidding strategies may be implemented, and the user may be shown how much everyone has paid for their particular rankings. This allows the user to know exactly how much he will have to pay to obtain a certain priority position. If the “lock in” feature is implemented, this will also let a user know if it is cheaper to pay the price to “lock in” the song or to pay to move up on the priority list. All of these options result in increased revenue for the operator. 
     It should be noted that although the embodiments above describe a system for distributing media to non-movable jukeboxes, alternative embodiments using similar systems could distribute media to portable jukebox devices and are contemplated by, and within the scope and spirit of, this invention. A portable jukebox may be, for example, a PDA, a cell phone, or any other movable device capable of receiving and playing music. Furthermore, media may be distributed to portable jukeboxes using the above described methods (e.g. through a broadband connection, wireless connection, etc.), or any other appropriate method, more suited to the particular portable device, such as, for example, using Bluetooth technology. Additionally, the jukeboxes described above typically are for commercial purposes. However, jukeboxes for other purposes such as, for example, playing residential media, also are contemplated by, and within the scope and spirit of, this invention. 
     In other exemplary embodiments, an employee of a location with a jukebox can be rewarded based on the number of plays customers pay for on the jukebox. In one such exemplary embodiment, the system keeps count of how many plays have been paid for by customers. Every time a certain number of plays have been paid for, the bar employee receives one free play. In some embodiments, a separate counter will be maintained, while in others embodiments only one counter may be necessary to calculate the number of free plays available. Thus, certain exemplary embodiments encourage employees to promote the jukeboxes by compensating the employee with free plays. This also can help reduce the similarity of song-selection throughout the day, preserve free plays for employees of different shifts, etc. 
       FIG. 20  is a flowchart showing an illustrative process for using a user-tailored system for managing music, communications, etc. in accordance with one exemplary embodiment. In step S 2000 , a user accesses the user-tailored system, dubbed MyTouchTunes in this case. It is to be appreciated that a user may access the system at a number of locations, such as, for example, via an Internet front-end, at a jukebox terminal, etc. It further is to be appreciated that the user may access the system in any number of ways, such as, for example, by inputting a username and password combination into the Internet front-end or jukebox terminal, by swiping a credit card at a jukebox terminal, by scanning a site-specific “smart-card” or flash card, etc. The system determines whether it recognizes the user in step S 2002 . If the user is not recognized, the user can be prompted to create account/profile information, as in step S 2004 . The account/profile information will be described in more detail below with reference to  FIG. 21A . 
     If the user is recognized in step S 2002 , the MyTouchTunes main menu is displayed for the user in step S 2006 . From the MyTouchTunes main menu, users using a system according to this exemplary embodiment may, for example, edit account/profile information in step S 2010 , manage music in step S 2020 , manage buddies in step S 2030 , communicate with others in step S 2040 , and/or access various value-added content that may be provided by the system in step S 2050 . These and other features will be described in more detail below with reference to  FIGS. 21A through 21B . 
       FIG. 21A  shows illustrative options available for editing account/profile information in one exemplary embodiment. As noted above, it is to be appreciated that the exemplary steps illustrated in  FIG. 21A  may correspond to the steps required for initial account/profile setup. In such an initial setup case, however, an exemplary system might require the user to complete all of the required information at one time before allowing the user to access the main menu (step S 2006  in  FIG. 20 ). It also is to be appreciated that such account/profile information could be stored in various locations as necessary to a given implementation, such as, for example, in a central location or database, on a particular establishment&#39;s server, on specific jukebox terminals, and/or on a removable card that would identify the user and the user&#39;s information when inserted into a jukebox. 
     A user would first input personal data in step  2012 . Such personal data may include, for example, an e-mail address for the user, a telephone (preferably mobile phone) number, and/or a name. The system also may prompt the user to create a unique username and password so that the system can identify the user at later times and from other locations. Alternatively, the system may use the user&#39;s e-mail address as a username and only require a corresponding password. Still alternatively, in the case of residential jukeboxes, for example, an exemplary system may not require a password at all. Based on the personal data, the exemplary system may gather enough information to recognize the user at logins (e.g., online access, preferred location, other locations within a given area, etc.) as well as send e-mail and text messages to the user. These exemplary features will be discussed in greater detail below. 
     In step S 2014 , users may specify various locations they frequent. This feature may enable user-tracking by various establishments, advertisers, etc. Establishments may, for example, provide special offers to regulars or others in a particular area to entice them to come visit. Advertisers may monitor the personal information, location information, and playlists to provide, for example, concert tickets, special offers on CDs, t-shirts, and/or other merchandise that may seem to be appealing based on the user&#39;s preferences. Still further, if such account/profile information is stored locally on various terminals, the system may communicate with those other terminals to provide the playlists in preparation for a user&#39;s visit. In step S 2016 , a user may add credits and/or specify payment information. Users may, for example, use their credit cards to increase the number of credits they have before entering an establishment, or while at an establishment. Alternatively, users may become “certified” by, for example, providing credit card information and allowing jukeboxes to automatically bill their credit cards for future credits purchased, etc. It is to be appreciated that step S 2016  can be used to purchase credits for oneself or for someone else, such as, for example, one&#39;s buddies, an employee of the establishment, etc. 
       FIG. 21B  shows illustrative options available for managing music in one exemplary embodiment. In step S 2022 , a user may create or edit already existing playlists. Users preferably can search through songs using the above-described methods and/or use system-generated suggestions to build their playlists. Preferably, users also may give their playlists descriptive titles, such as, for example, “Favorite Jams,” “&#39;80s Night,” “Smooth Love Songs,” etc. Users may further designate their playlists as “public” or “private” to allow or restrict other users from perusing their playlists. Users may, in step S 2024 , rate their songs and/or playlists through the PickList feature. The PickList also may generate a custom playlist comprising the songs the user has rated the highest at a given time. Alternatively, a PickList may comprise a list based on the HotHits list described above. In step S 2026 , a user may play music on a jukebox using, for example, any of the above described methods with or without using these playlists. Normally, selecting a playlist for play on a jukebox will add those songs to the regular queue. However, as described above, users may pay an additional fee and/or use the bidding mechanism described above to play their music immediately. Furthermore, selecting a playlist (or playlists) for play on a jukebox normally will play all songs in that particular playlist (or in those particular playlists). However, users may unselect certain songs to prevent them for being played. This enables users to further customize playlists dynamically when they are playing their music. 
       FIG. 21C  shows illustrative options available for managing buddy lists in one exemplary embodiment. Users may keep track of buddies (e.g., friends, regulars at a bar, etc.). The system may use any instant messaging standard, such as, for example, AOL Instant Messenger, MSN Messenger, Yahoo! Messenger, ICQ, a custom jukebox-specific protocol, etc. to send and receive messages. Preferably, the system would alert the user of the buddies&#39; statuses (e.g., online, inactive, busy, etc.). In step S 2032 , a user may create or edit an already existing buddy list. Users may search for buddies by, for example, inputting their names, e-mail addresses, etc. Additionally, users may invite friends to join by issuing invitations, preferably by e-mail or SMS (Short Message Service) text message to a mobile phone, in step S 2038 . 
     Users also may browse their buddies&#39; music collections, playlists, PickLists, etc., as shown in step S 2034 . Users then could develop their own playlists and/or PickLists based on what they perceive as popular amongst their friends. Users also may copy music from their buddies or send music to their buddies, preferably for a fee, as shown in step S 2036 . In a step not shown, users also may designate particular songs to play when their friends log in to the jukebox, again, preferably for a fee. Other features pertaining to communication between buddies will be described below with reference to  FIG. 21D . 
       FIG. 21D  shows illustrative options available for communicating with others in one exemplary embodiment. Preferably, the system can send e-mails and SMS messages to mobile phones. It is to be appreciated that the system should be able to communicate using any variety of communications protocols, such as, for example, via e-mail and/or e-mail-like messages accessible only by the MyTouchTunes system. It also is to be appreciated that bar managers may also send messages (e.g., via e-mail, SMS, etc.) to alert others of events, specials, etc. In step S 2042 , users may check their inbox. Users may receive messages from, for example, their friends (or buddies), proprietors, and/or advertisers, etc. Buddies may suggest, for example, songs or places to gather. In some exemplary embodiment, buddies may receive instant messages on their mobile phones alerting them of a get-together, a particular user&#39;s location in a bar, etc. Furthermore, users may leave messages for others to appear on someone else&#39;s next log-in. Proprietors may send messages to their regulars or others they wish to target to alert them, for example, of drink specials, upcoming special events, etc. Advertisers may, based on demographic information provided by users, extend special offers. In step S 2044 , users may send messages to others&#39; e-mail address, MyTouchTunes inbox, mobile phones, etc. Alternatively or in addition to step S 2044 , in step S 2046 , users may broadcast messages to buddies or groups of others, to, for example, alert a particular group of upcoming parties, etc. Thus, exemplary systems can learn about networks of friends through the messages that users send. In addition, the jukebox may directly provide an interface for the features described above, or it may provide for wireless access to the features, for those users that may bring a wireless device with them to the location (or within range) of the jukebox. Some or all of the features can also be provided to the users remotely by, for example, enabling users to access the jukebox services through the internet or other suitable communications network, using for example, the user&#39;s home computer. 
       FIG. 21E  shows illustrative options available for accessing value-added content in one exemplary embodiment. Users could access external websites (preferably of partners) as shown in step S 2052  for any number of reasons. For example, advertisers may place banner ads pertaining to the particular song or album selected to allow users to place orders for related merchandise. Advertisers may use profile information to target ads, e-mails, text, etc., potentially anywhere (e.g., online, on a jukebox, etc.). For example, jukebox use can be used as a “qualifier” for targeting certain products (either conspicuously or non-conspicuously) to individuals who spend more than a certain amount on jukeboxes yearly. Users also may access external websites to link to a particular band&#39;s website, to order sheet music or guitar or bass “tabs,” to view lyrics, etc. Also, in step S 2054 , users may follow a link to download/purchase songs and/or albums from a third-party provider such as iTunes or Amazon.com. In some exemplary embodiments, this step may also be linked to from the “Manage Music” screen (step S 2020 ), etc. Additionally, in step S 2056 , users may order custom CDs and have them shipped, preferably for a fee. Users could base these orders on their playlists, their PickLists, their buddies&#39; playlists, the HotHits list described above, etc. 
     It is to be appreciated that although the above-described exemplary MyTouchTunes system has been described in terms of a broad concept for making accounts available on any compatible system, other exemplary embodiments are contemplated where accounts may be made available to smaller subsets of jukeboxes, including, for example, a single jukebox terminal acting in isolation. Furthermore, a large group may act as if it were one system in isolation, or, alternatively, it could have complete knowledge of all user accounts/profiles, locations, etc. 
       FIG. 22  is an exemplary screen shot of a login page in accordance with one exemplary embodiment. A user may enter an e-mail address in username area  2200  and a password in password area  2202 . As a shortcut, a user may select a common e-mail domain from domain list  2204 . It is to be appreciated that although this embodiment requires an e-mail address and a password, other embodiments may require a username that need not be an e-mail address. Similarly, it is to be appreciated that a username and password may not be required, for example, on a home jukebox system, and that in yet further embodiments, only a username may be required. A user can use keyboard  2206  to enter the required information, though it is to be appreciated that other input devices, such as a keyboard attached to a home computer, may be used. It also is to be appreciated that the login screen shown in  FIG. 22  may appear on an actual jukebox device, on a computer (e.g., through a web-interface, custom software, etc.), on a mobile device, etc. 
     Preferably, a successful log-on displays a main menu for users.  FIG. 23  is an exemplary screen shot showing the features available after a recognized user has logged in, in accordance with one exemplary embodiment. A customized greeting (e.g., the user&#39;s name) is displayed in area  2300 . Playlists  2302 ,  2304 , and  2306  are displayed with descriptive names along with the number of credits required to play a full playlist. For example, to play playlist  2302  costs 7 plays. Preferably, playlists are presumed to be public, which allows other users to view them. Playlists may be designated private, however, as is, for example, playlist  2306 . Users can create additional playlists by pressing playlist creator button  2308 , and they can edit already existing playlists by pressing playlist manager button  2310 . The playlist manager may allow users to, for example, change existing playlists by adding and/or removing songs, deleting playlists completely, etc. 
     Users can manage a buddy list by adding a buddy by pressing add buddy button  2314 . Alternatively, they can remove a buddy by pressing remove buddy button  2316 . Users also can communicate by sending messages to their buddies by pressing send message button  2318 . This feature can, in certain embodiments, for example, send SMS messages to mobile devices, send e-mails, send messages to appear when the recipient user next logs-in, etc. In still other embodiments, users can, for example, use this feature to send songs, donate credits, etc. Indicator area  2320  shows that the current user has received one message, and it identifies the sender. In other embodiments, however, other information may be displayed, a more complete inbox (e.g., with folders, forwarding, etc.) may be provided, etc. Credit indicator area  2322  provides account status. In this embodiment, it indicates that the user has previously purchased 20 plays online, and has entered enough money in a local jukebox terminal for 5 additional plays, for a grand-total of 25 potential plays. 
     Another aspect of the instant invention relating to improvements in background music will now be described. The local server and Tune Central feature described herein, open up a whole new world for background music on a jukebox. Currently, when no paid for music is queued, jukeboxes may play background (ambiance) music with the help of an auxiliary system connected to the jukebox, such as DMX or satellite radio. Alternatively, if they play background music with their own music, they are limited to the songs available for play on the jukebox, typically about 2000 songs. These songs are also available for selection by jukebox patrons. Conventional digital jukeboxes are typically connected to a remote network through the internet for accessing extended music. These applications are therefore not well suited for providing background music services other than the music locally available as this would require constant download or streaming from the remote servers for the background music. 
     However, jukeboxes equipped with an external server or large music partition (such as Tune Central described herein) can select background music to play from that large pool of songs, even if the song is not available for play through the standard interface. This permits a vast musical variety for background music using jukeboxes. The background music selection can be made automatically by the jukebox randomly or with an advanced algorithm that selects music based on genres, themes, era or other criteria. Also, background music lists can be preprogrammed by a disk jockey or the like (background playlists) and sent from a central server to jukeboxes. Since music rights can differ for songs available in pay-per-play mode and background music, there is, in an embodiment of the invention, an indicator for each song or song aggregations (e.g., all songs from ABC record label) allowing the jukebox to distinguish between songs that can be played as background music (as opposed to normal jukebox play) based on the availability of the proper music rights, thereby enabling proper royalty accounting as well. In an embodiment of the invention, the jukebox offers advanced options for allowing an operator to configure how background music will be performed, based on genre, themes, indicators (flags), such as billboard hit, Christmas music, playlists (e.g., DJ John—summer 2005), etc. In another embodiment of the invention, the operator configures the jukebox to allow the bartender to further configure the background music mode through, for example, a remote control; much like the bartender would select a radio station in prior background music systems. This mode offers genres or theme based music or playlists for enhancing background music functionality. The operator can, for example, configure which genre, theme or playlists is available to the bartender. In addition, a remote control with programmable keys combined with suitable software can be provided to allow the bartender (or other person) to select (e.g., for a particular zone) a certain background music play list or TV audio input for special event like, for instance, a football game in a bar zone, thereby providing convenient and effective background music services and other services through the jukebox device. 
     While the preferred aspects of the invention have been illustrated and described herein, it will be apparent to one of ordinary skill in the art that various changes and/or modifications can be made. Thus, the specific description herein is meant to be exemplary only and is not intended to limit the invention beyond the terms of appended claims.