Audio visual device and method to be performed by audio visual device

The integration of jukeboxes with central and local servers and social networking features addresses storage and connectivity limitations, enhancing user experience and revenue through instant song access and community building.

JP2024156760AActive Publication Date: 2024-11-06TOUCHTUNES MUSIC CORP
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2024120882
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2009-03-18
Filing Date
2024-07-26
Publication Date
2024-11-06
Estimated Expiration
2030-03-17

AI Technical Summary

Technical Problem

Traditional jukeboxes face challenges in maintaining a diverse song library due to limited storage capacity and reliance on dial-up connections, leading to user frustration and reduced revenue, while lacking features to enhance customer engagement and community building.

Method used

An entertainment system integrating jukeboxes with a central server and local servers, enabling instant song downloads from local servers, social networking interfaces, and user authentication, allowing for personalized experiences and community interaction through avatars and online platforms.

Benefits of technology

Enhances user engagement by providing instant access to songs, fosters a sense of community, and increases revenue through personalized services and advertising opportunities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024156760000001_ABST
    Figure 2024156760000001_ABST
Patent Text Reader

Abstract

To provide an audio visual device and method for providing social networking and / or other services by interacting with users.SOLUTION: An audio visual device (entertainment server 4002) located in a shop 4000 is connected to an entertainment system network 4010 and sends an information feed to one or more external social networking systems 4018 via an S.N. I / F 4016. The information feed includes data indicating a plurality of selected medium instances to be reproduced by the audio visual device and / or a message to be sent to users of the social networking systems. Further, an MYTT I / F 4014 connects a plurality of end user computers 4020 and / or client devices 4022 that are located outside the shop to the audio visual device.SELECTED DRAWING: Figure 40A
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] Certain exemplary embodiments of the present invention relate to entertainment systems. In particular, certain exemplary embodiments of the present invention relate to entertainment systems that provide social networking and / or other services by interacting with users. For example, in certain exemplary embodiments, an off-site store entertainment system is configured to provide jukebox-related services that are accessible from within and outside the store, while integrating social networking services between customers inside and outside the store and providing advertising opportunities. In certain exemplary embodiments, the in-store entertainment system may function as a jukebox and / or may be connected to a jukebox. Furthermore, in certain exemplary embodiments, the in-store entertainment system may be connected to one or more client devices, one or more displays, one or more bar-top or handheld gaming devices, etc. The entertainment system-mediated, jukebox-related services described above enhance the customer experience and create a sense of ownership and / or belonging to a cohesive community among users of the entertainment system. [Background technology]

[0002] Jukeboxes have been around for about several decades, allowing users to select desired music to play in a convenient and convenient manner. Traditionally, jukeboxes have been installed in commercial establishments, such as restaurants and bars, to provide customers with music of their choice for a fee. In recent years, a new generation of jukebox devices has become available. The new generation of jukebox devices offers significant operational improvements for all participants. More specifically, traditional standalone vinyl and CD jukeboxes have been replaced with digital download jukeboxes that communicate with and are controlled by a central server. An example of this new generation of jukebox system is shown in U.S. Patent No. 6,399,933, the entire disclosure of which is incorporated herein by reference. A leading provider of this new generation of jukebox systems is TouchTunes Music Corporation.

[0003] FIG. 1 shows an overview of an exemplary embodiment of a digital download jukebox system 10 (hereinafter simply referred to as a "jukebox system"). As shown in FIG. 1, the jukebox system 10 includes a central server 12. The central server 12 includes a master library of audio content (typically "music") and / or audiovisual content (typically "music and associated video or graphics") that is available for download from the central server 12. The jukebox system further includes a series of remote jukebox devices 16, 16a-16f. Each of these jukebox devices is typically installed in a bar, restaurant, club, or other desired establishment. Each jukebox device is operative to receive payment from a user, such as coins, bills, credit / debit cards, and to play music in response to the user selecting one or more songs to play. In another embodiment, the establishment pays for the music service on a subscription basis, and the selected music is provided free of charge to the end user. The remote jukebox device 16 includes a screen 18 and an audio system 20. The screen 18 presents information to the user and allows the user to select music. The audio system 20 plays the selected music. The screen 18 may also be used to display advertising for the jukebox itself, as well as other types of advertising and / or other desired information to attract customers.

[0004] The jukebox devices 16 (sometimes simply referred to herein as "jukeboxes") are operable to communicate with a central server 12 over a communications network 14, such as the Internet. The jukebox devices 16 communicate periodically with the server 12 to provide the server 12 with information about the specific songs played on the jukeboxes. The central server uses this information to determine the appropriate royalties and / or other fees to be paid for songs played on each jukebox. In this manner, this new generation of jukeboxes has the advantage that music playback and / or other applicable music rights are protected in a more accurate and reliable manner, thereby ensuring that appropriate royalties are paid to artists and song owners. The central server 12 also provides new songs to the jukeboxes so that the appropriate or most popular songs for the particular customers in the store are maintained in the jukebox. In this manner, the songs available on each jukebox can be customized through communication with the central server so that each jukebox in the store can provide songs and / or a variety of music that are commonly requested by customers. As described in the above-mentioned US Patent No. 5,999,563, the central server can also be preferably used to update the software running on the jukebox, for example to provide new or improved functionality to the jukebox. Thus, this new generation of jukeboxes has the added advantage that the songs (or other audio, visual or audiovisual content) and the operation of the jukebox itself can be remotely modified as desired, without requiring a dealer or other person to personally service the jukebox. Instead, the central server 12 can be used to perform such updates.

[0005] As mentioned above, each jukebox device 16 includes a mass storage device, such as a hard drive, on which music pieces and associated video / graphic data (if any) as well as any desired graphical information to be played by the jukebox are stored. The jukebox's mass storage device typically has a limited storage capacity compared to the storage device of the central server 12. As such, the jukebox's mass storage device typically contains only a portion of the music pieces stored on the central server 12 at any one time. There are further reasons for limiting the storage capacity of the jukebox and / or the number of music pieces stored on the jukebox, such as data security and limited space availability within the jukebox itself. For example, a wall-mounted jukebox, which should be designed to be small in size, may have limited physical space compared to a freestanding model. As explained above, the music on the jukebox can be changed through communication with the central server, but typically, any jukebox stores only a relatively small subset of the complete library of music held by the central server at any one time. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] US Patent No. 6,308,204 Summary of the Invention [Problem to be solved by the invention]

[0007] In order to maximize the revenue generated by a jukebox, it is important to keep the most desired songs available on the jukebox for a long period of time. If customers cannot find their favorite songs on the jukebox, the utilization rate of the jukebox (and thus the profits generated) will drop significantly. On the other hand, it is impossible to accurately predict in advance which songs customers will want to play on the jukebox in a particular store. In fact, there are many instances where customers select songs that are not currently on the jukebox but are on the central server. Thus, the jukebox may not be fully enjoyed and used. To address this problem and increase the revenue of the jukebox, conventional jukeboxes have been equipped with a feature that allows users to search for songs on the central server from the jukebox and to request that desired songs be downloaded immediately from the central server to the jukebox for an additional fee. This feature allows users to play any song on the jukebox that is included in the master library of songs maintained by the central server, regardless of whether the song is stored in the mass storage of the jukebox itself. Thus, a user first searches for the desired song in the jukebox's local storage and, if desired, further searches for the desired song in the central server. Typically, jukeboxes charge an additional fee (e.g., 5 credits instead of 1 credit) for instant download and playback of a song from the central server, as opposed to normal playback directly from the jukebox's local storage.

[0008] However, a problem with the instant download feature is that it requires that a high-speed connection be established immediately with a central server. Moreover, for such a feature to work properly, the central server and the network must be prepared and capable of handling the requests in a reliable and efficient manner. These requirements cannot always be met, and as a result, the adoption of this feature is limited. For example, many stores that have jukeboxes do not have high-speed connections (such as DSL) and instead use dial-up modem connections. Typically, jukeboxes that rely on dial-up connections are designed to only communicate periodically with the server, and do not allow users to download songs immediately. The jukeboxes do allow users to vote for songs to be downloaded later when a dial-up connection is established, but this is, of course, not as satisfying to users as allowing songs to be downloaded immediately. Other problems with the download feature can arise when the network or server is unavailable for downloading due to traffic, failures, etc.

[0009] For many users, their interaction with a jukebox is limited to selecting a song to play. Casual users may find it difficult to quickly locate and / or search for a particular song, while frequent users often select the same songs and may become frustrated by having to make the same selection each time. Both problems resulting from intimidation and frustration result in lost revenue.

[0010] In this regard, it is a feature of the exemplary embodiment to create a relationship between the jukebox and customers with consideration for creating a relationship with the entire community of jukebox users. Such a system allows the jukebox to build trust with customers while creating a sense of ownership for customers by allowing them to customize their own services and communicate with friends. Such a relationship and sense of ownership significantly increases the convenience of using the jukebox and related services while reducing intimidation, frustration, and the like.

[0011] In certain exemplary embodiments described herein, the jukebox can be the centerpiece of music services as well as other services that enhance the user experience and the store manager's revenue. For example, the jukebox can be a touchpoint in the store where users can reach out to their friends. For example, users may use the jukebox to call meetings, share songs through the jukebox system, or meet up at the jukebox if they get separated in a crowded club. Similarly, the jukebox can be a touchpoint in the store where store managers can reach out to customers. For example, the manager can advertise specials or notify patrons of special events. Such communications can be initiated by users, the store manager, or the jukebox itself.

[0012] When a jukebox user leaves the store, they generally lose their connection to the songs and, in particular, to the jukebox itself. Users provide the jukebox with a great deal of data, such as which users like certain types of music or songs, when they listen to music, how often they listen to music, etc. In conventional jukeboxes, this information is not used to provide additional features and / or services to interested users. Thus, the data collected is typically wasted and users experience only a fleeting sense of ownership. For example, users cannot recreate the experience of a special night out.

[0013] Operators also lose because the relationship with the jukebox user is lost when the user leaves the establishment. Thus, operators lose customers until they return, and are forced to rely on traditional, and often ignored, methods of bulk advertising. This form of advertising generally lacks specificity and does not reflect the user's personalized sense of belonging. Furthermore, operators cannot replicate, for example, a special event from a particularly profitable night.

[0014] For example, on the Internet, online communities have typically been created to connect various users in a virtual space. These communities potentially offer a wide range of functionality and ongoing access to a wide range of users. However, traditional online communities exist only on the network; that is, the relationship literally ends when the user leaves the computer. Thus, while users have access to this wide host of functionality, customize their experience, and build an online persona, complete with, for example, purchasing and browsing habits, the experience is fleeting.

[0015] However, by connecting jukebox users through online communities, the information provided to the jukebox can be used to provide various functions and services to the users. And because jukeboxes exist in many meeting places, connections exist in many physical locations apart from the online virtual community. Thus, by using the information data collected by the jukebox to connect users to online communities, a combined real and virtual community is formed. Such a community can, for example, create a sense of ongoing ownership, potentially personalize the service for every user, and connect users to each other, forming a vibrant, socially active community of users connected by music. Store owners can benefit as well. For example, they can connect with customers while they are away from the store, thus creating a pipeline for additional business, which can attract customers to the store.

[0016] In short, a jukebox with associated remote applications, for example, can change a user's perception of the jukebox. A jukebox does not have to be a standalone device accessible only at a bar. Rather, the present invention allows users to perceive the jukebox as a media center, a meeting place, a portal to an online community, etc.

[0017] Moreover, with the advent of web-enabled mobile devices (e.g., cell phones, PDAs (personal digital assistants), etc.), users can even carry their virtual communities with them wherever they go. Users can potentially use their mobile devices to directly download music at any time (e.g., when listening to music at home, in the car, at a bar, etc.).

[0018] In certain exemplary embodiments, a user's actions at the jukebox and / or through the remote interface may be represented by an avatar designated and / or customized by the user. The jukebox may include logic (e.g., hardware, software, or any combination thereof) programmed with avatar behaviors that act on behalf of and / or represent the user's actions. Such behaviors may include audio and / or visual song introductions, singing and / or dancing along with the music, online interactions (announcements, postings, file transfers, etc.), etc. Thus, the user's avatar may increase a sense of ownership and / or belonging, attracting users to the jukebox. Additionally, the avatar may further increase the enjoyment of each user, regular patrons, and / or newcomers to the area.

[0019] The above and / or other aspects, features, and exemplary embodiments are advantageous and represent improvements over existing jukebox-related offerings. It is desirable to integrate and extend the disparate elements of a broader, more integrated entertainment system. For example, with a currently unconnected but widespread collection of jukeboxes, jukebox-specific services, ad servers, independently operated social networking services, and independently controlled client devices, to provide an experience that allows for greater interconnection and integration of seemingly disparate systems. Advantageously providing such a system would enable entertainment system customers to more fully and deeply connect with other customers and non-customers, which sometimes motivates the former group to use the entertainment system components more and the latter group to begin using the entertainment system components. However, it is desirable to further enhance the customer experience to create a sense of ownership and / or belonging to a community in which entertainment system users are connected.

[0020] Jukebox systems need to be improved to meet the various needs of users, store owners, and operators, all of which enhance a customer's sense of ownership and / or belonging. Jukebox systems extend with technology to provide modern social networking opportunities. The present invention is designed to address these and other issues and to enhance the capabilities of such jukebox systems. [Means for solving the problem]

[0021] In certain exemplary embodiments of the present invention, an audiovisual entertainment system is provided, the entertainment system network including a database in which a plurality of media instances are tangibly stored, and a social networking interface configured to mediate communication between the entertainment system and an external social networking system that is not part of the entertainment system, one or more jukeboxes are provided in an off-site store, the one or more jukeboxes are connected to the entertainment system network and configured to play a plurality of media instances that are either locally stored on the jukebox or downloaded from the entertainment system network for a fee, the one or more jukeboxes and the social networking system are configured to share data over the entertainment system network.

[0022] In certain exemplary embodiments, the entertainment system network may further include a jukebox social networking interface to a social networking site associated with the jukebox.

[0023] In certain exemplary embodiments, a plurality of off-site, non-store based computers may be configured to interface with the jukebox via the jukebox social networking interface and / or a non-off-site, non-store based non-jukebox device may be configured to remotely interface with the one or more jukeboxes to select media instances for play on the one or more jukeboxes and transfer credits to the jukebox device, which may be a smart phone, a countertop gaming device, a handheld gaming device, or a computer.

[0024] In certain exemplary embodiments, a first feed may be provided from the one or more jukeboxes to the social networking system via the social networking interface of the entertainment system network, the first feed providing data indicative of a plurality of selected media instances being played or to be played on the one or more jukeboxes. In certain exemplary embodiments, the one or more jukeboxes may include a user authentication unit configured to authenticate pre-registered users logging into the jukebox via the off-site store jukebox or a non-jukebox device. The first feed may further include data indicative of a registered user, if any, who selected each of the plurality of selected media instances being played or to be played on the one or more jukeboxes. The first feed may further include data indicative of a message sent from an authenticated user to the social networking site using the off-site store non-jukebox device. The first feed may further include data indicative of messages sent from an authenticated user to the social networking site using the one or more jukeboxes located at the off-site establishment.

[0025] In certain exemplary embodiments, the display may further include a display external to the one or more jukeboxes and within the off-site establishment. The display may be configured to list the selected media instances being played on the one or more jukeboxes, to list authenticated users, if any, who selected each of the selected media instances being played, to list messages sent by authenticated users to the social networking site directly or indirectly using the one or more jukeboxes in the off-site establishment, to list trivia about the media instance being played, to list a message from an artist or a label, etc., about the media instance being played. In certain exemplary embodiments, the display may be controlled, for example, using a display controller included in the jukebox. In certain exemplary embodiments, the display may be controlled by one or more processors in the entertainment system network. Trivia and / or other messages may be provided from one of the processors and / or from other sources (which may also include an association database mapping messages to media instances).

[0026] In certain exemplary embodiments, a second feed may be provided from the social networking system to the one or more jukeboxes via the social networking interface of the entertainment system network, the second feed including data indicative of messages sent from the social networking site to the off-site in-store authenticated users and / or the one or more jukeboxes, and the display may be configured to list messages from the social networking site using the second feed.

[0027] In certain exemplary embodiments of the present invention, methods of making and / or using an audiovisual entertainment system in accordance with exemplary embodiments disclosed herein are provided. [Brief description of the drawings]

[0028] The above and other features, aspects and advantages of the present invention will be further understood by reference to the following detailed description when read in conjunction with the accompanying drawings. [Figure 1] FIG. 1 is a block diagram of a conventional download digital jukebox. [Diagram 2] FIG. 2 is a block diagram of an improved download digital jukebox in accordance with an exemplary embodiment of the present invention. [Diagram 3] FIG. 3 is an exemplary screenshot showing an initial selection screen according to an exemplary embodiment of the present invention. [Figure 4] FIG. 4 is another screenshot illustrating an exemplary search screen used in searching for songs on a local server in accordance with an exemplary embodiment of the present invention. [Figure 4A] FIG. 4A illustrates a typical process for using the Personal Music Assistant to search for music that may suit a user-specified profile. [Figure 4B] FIG. 4B illustrates an exemplary process for using the Personal Music Assistant to search for music that may be suitable for a recognized user profile. [Figure 4C] 1 is an exemplary screenshot showing a non-limiting list of genres and themes available to a user according to one illustrative embodiment. [Diagram 5]FIG. 5 is another exemplary screenshot showing search results on a local server and presenting the user with the option to download the desired songs to a jukebox for a fee, in accordance with an exemplary embodiment of the present invention. [Figure 5A] FIG. 5A illustrates a typical process for searching through a list of popular songs. [Figure 6] FIG. 6 is another exemplary screenshot illustrating another method of granting access to the download feature. [Figure 7] FIG. 7 is a block diagram illustrating a local server according to an exemplary embodiment. [Figure 8] FIG. 8 shows a block diagram of a typical overall network including commercial and home jukeboxes as well as other download devices and associated communications managed by the jukebox system. [Figure 9] FIG. 9 shows an overhead view of a typical installation layout for a multi-zone jukebox system. [Figure 10] FIG. 10 shows an overhead view of a typical installation layout for a multi-zone jukebox system with a selection terminal in each zone. [Figure 11] FIG. 11 is a flow chart illustrating an exemplary implementation of the zone selection process for a multi-zone jukebox system. [Figure 12] FIG. 12 is a flow chart illustrating an exemplary implementation of a play order for a multi-zone jukebox system. [Figure 13] 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. [Figure 14] FIG. 14 is a flow chart illustrating a typical distribution and initiation scheme for a jukebox with configuration change capabilities. [Figure 15] FIG. 15 is a flow chart illustrating an exemplary implementation of a process for initiating automatic jukebox configuration changes in response to a triggering event. [Figure 16] FIG. 16 is a flow chart illustrating an exemplary implementation of a jukebox configuration change process. [Figure 16A] FIG. 16A is an exemplary screenshot showing how a jukebox reconfiguration can be initiated in an exemplary embodiment. [Figure 16B] FIG. 16B is another exemplary screenshot illustrating how a user can specify various criteria before reconfiguring a jukebox in an exemplary embodiment. [Figure 17] FIG. 17 illustrates the relationship of a jukebox with extended media storage to a central server. [Figure 18] FIG. 18 is a flow chart illustrating an exemplary process for selecting a song when the song is not included in the "standard" available song play list. [Figure 19] FIG. 19 is a flow chart illustrating an exemplary operation of a priority play queue with prioritization-based-on-bidding. [Figure 19A] FIG. 19A is a flow chart illustrating an exemplary implementation of the voting process for a jukebox. [Figure 19B(1)] FIG. 19B(1) is an exemplary screenshot showing the display of the voting queue. [Figure 19B(2)] FIG. 19B(2) is another exemplary screenshot showing a display of the voting queue. [Figure 19C] FIG. 19C is an exemplary block diagram illustrating the voting mechanism within a given store. [Figure 19D] FIG. 19D is another exemplary block diagram illustrating a voting mechanism within a given store. [Figure 19E] FIG. 19E is an exemplary block diagram illustrating a voting mechanism used in multiple stores. [Figure 19F] FIG. 19F is another exemplary block diagram illustrating a voting mechanism for use in multiple stores. [Figure 20] FIG. 20 is a flow chart illustrating an exemplary process for using a user-tailored system for managing music, communications, etc., according to an exemplary embodiment. [Figure 21A] FIG. 21A illustrates non-limiting example options available for editing account / profile information in an exemplary embodiment. [Figure 21B] FIG. 21B illustrates non-limiting example options available for managing songs in an exemplary embodiment. [Figure 21C] FIG. 21C illustrates non-limiting example options available for managing your friends list in an exemplary embodiment. [Figure 21D] FIG. 21D illustrates non-limiting example options available for communicating with others in an exemplary embodiment. [Figure 21E] FIG. 21E illustrates non-limiting example options available for accessing value-added content in an exemplary embodiment. [Figure 22] FIG. 22 is an exemplary screenshot of a login page according to an exemplary embodiment. [Diagram 23] FIG. 23 is an exemplary screenshot illustrating the functionality available to an authenticated user after logging in according to an exemplary embodiment. [Figure 24] FIG. 24 is a flow diagram illustrating an exemplary process for remotely accessing a system according to an exemplary embodiment. [Diagram 25] FIG. 25 is a flow diagram illustrating an exemplary process for selecting one or more of a non-limiting list of services and / or features within a system according to an exemplary embodiment. [Figure 26A] FIG. 26A is an exemplary screenshot illustrating the functionality available to a user before they log into the system according to an exemplary embodiment. [Figure 26B] FIG. 26B is an exemplary screenshot illustrating the functionality available to a user after logging into the system according to an exemplary embodiment. [Figure 26C] FIG. 26C is an exemplary screenshot showing how a user can update their account information. [Figure 26D] FIG. 26D is an exemplary screenshot showing how a user can manage playlists. [Figure 26E] FIG. 26E is an exemplary screenshot showing the results of an exemplary selection of songs. [Figure 26F] FIG. 26F is an exemplary screenshot showing search results from a jukebox search service. [Figure 27] FIG. 27 illustrates an exemplary system for downloading music to a portable device. [Figure 28] FIG. 28 is a flow chart illustrating an exemplary process for searching for music. [Figure 29] FIG. 29 is a block diagram of an improved download digital jukebox system that includes a remote device for accessing the jukebox from within a particular store. [Figure 29A] FIG. 29A is a block diagram of an improved download digital jukebox system that includes a remote device for accessing the jukebox from within a particular store. [Figure 29B] FIG. 29B is a block diagram of an improved download digital jukebox system that includes a remote device for accessing the digital jukebox system outside of a particular store. [Figure 29C] FIG. 29C is another block diagram of an improved download digital jukebox system that includes a remote device for accessing the digital jukebox system outside of a particular store. [Figure 29D]FIG. 29D is a block diagram of an improved download digital jukebox system that includes another digital jukebox system outside of a particular store that accesses the first digital jukebox system. [Figure 29E] FIG. 29E is another block diagram of an improved download digital jukebox system that includes another digital jukebox system outside of a particular store that accesses the first digital jukebox system. [Diagram 30] FIG. 30 is an exemplary flow chart showing how a user can change his / her status by becoming an "authenticated user." [Diagram 31] FIG. 31 is an exemplary flow chart illustrating a method by which a registered user may receive credits for referring potential users. [Diagram 32] FIG. 32 is an exemplary flow chart illustrating how a registered user may receive credits for creating public playlists. [Diagram 33] FIG. 33 shows an exemplary screenshot of the "Local Playlist" screen, where registered users are represented by avatars. [Diagram 34] Figure 34 is a typical screenshot of the Now Playing screen. [Diagram 35] FIG. 35 is an exemplary screenshot for setting alert preferences. [Diagram 36] FIG. 36 is an exemplary screenshot for setting the alert thresholds. [Figure 37] Figure 37 is a typical screenshot showing the status of the various tests. [Figure 38] FIG. 38 is an exemplary screenshot of the configuration change functionality associated with the enhanced scheduling module. [Figure 39] Figure 39 is a typical screenshot of a scheduling calendar. [Figure 40A]FIG. 40A illustrates the major components within an entertainment system according to an exemplary embodiment. [Figure 40B] FIG. 40B illustrates the physical architecture of an entertainment system according to an exemplary embodiment. [Figure 40C] FIG. 40C illustrates the logical architecture of an entertainment system according to an exemplary embodiment. [Figure 41A] FIG. 41A is an exemplary screenshot of a client device logging into an entertainment system according to an exemplary embodiment. [Figure 41B] FIG. 41B is an exemplary screenshot of a client device logging into an entertainment system according to an exemplary embodiment. [Figure 41C] FIG. 41C is an exemplary screenshot of a client device logging into an entertainment system according to an exemplary embodiment. [Figure 41D] FIG. 41D is an exemplary screenshot of a client device logging into an entertainment system according to an exemplary embodiment. [Figure 42A] FIG. 42A is an exemplary screenshot illustrating how a user may log into a wireless network. [Figure 42B] FIG. 42B is an exemplary screenshot illustrating how a user may log into a wireless network. [Figure 43A] FIG. 43A is a flow chart illustrating an exemplary process for receiving payment from a user according to an exemplary embodiment. [Figure 43B] FIG. 43B is a flow chart illustrating an exemplary process for receiving payment from a user according to an exemplary embodiment. [Figure 43C] FIG. 43C is a flow chart illustrating an exemplary process for receiving payment from a user according to an exemplary embodiment. [Fig. 43D] FIG. 43D is a flow chart illustrating an exemplary process for receiving payment from a user according to an exemplary embodiment. [Figure 44A] FIG. 44A is an exemplary screenshot illustrating searching, selecting and playing music on a jukebox using an interface provided on a client device according to an exemplary embodiment. [Figure 44B] FIG. 44B is an exemplary screenshot illustrating searching, selecting and playing music on a jukebox using an interface provided on a client device according to an exemplary embodiment. [Figure 44C] FIG. 44C is an exemplary screenshot illustrating searching, selecting and playing music on a jukebox using an interface provided on a client device according to an exemplary embodiment. [Fig.44D] FIG. 44D is an exemplary screenshot illustrating searching, selecting and playing music on a jukebox using an interface provided on a client device according to an exemplary embodiment. [Figure 44E] FIG. 44E is an exemplary screenshot illustrating searching, selecting and playing music on a jukebox using an interface provided on a client device in accordance with an exemplary embodiment. [Fig.44F] FIG. 44F is an exemplary screenshot illustrating searching, selecting and playing music on a jukebox using an interface provided on a client device in accordance with an exemplary embodiment. [Diagram 45] FIG. 45 is an example display including a "feed" for a virtual store according to an exemplary embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0029] Referring to the drawings, FIG. 2 is a block diagram of an exemplary embodiment of an improved jukebox system 10'. The jukebox system 10' includes similar components to those shown in FIG. 1. The jukebox system 10' includes the central server 12, the communication network 14, and the remote jukebox devices 16, 16a-16f as described above, but also includes local servers 22, 22a-22f. The local servers 22, 22a-22f are connected to the remote jukebox devices 16, 16a-16f, respectively. The central server 12 includes a master library of songs (and / or other content). Each jukebox device includes a portion of the master library on its local storage device. The central server may be used to individually manage the jukebox content by monitoring the usage of songs on each jukebox device and updating the portion of songs to maximize song usage. The central server 12 periodically receives data from each jukebox device for calculation and payment of royalties for played songs. The jukebox devices may be connected to the network in any suitable manner, such as by 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 delivering data (e.g., audiovisual data) from the central server 12 to the jukeboxes 16, and capable of uploading data from the jukeboxes 16 to the central server 12.

[0030] The songs (and / or data) are digitized, compressed and encrypted using known techniques by the central server 12 for security and bandwidth reasons before being sent to the jukebox. The songs are then decompressed and decrypted for storage and playback at the jukebox. In this manner, each jukebox maintains a library of digitized songs in a database for playback on the jukebox, which library may be changed or updated through communications from the central server. The jukebox may receive and store data constituting images (e.g. still and / or moving and / or graphic images) that may be displayed on the display 18 of the jukebox 16. A jukebox apparatus according to an exemplary embodiment of the present invention has a structure similar to that described in the above-referenced U.S. Pat. No. 6,308,204 and operates in a manner similar to that described in the '204 patent. Thus, each jukebox device 16 may include one or more microprocessors, such as a main CPU and / or audio DSP, storage for storing music and / or other content, such as a hard disk, a display for displaying visual items, an audio device 20 for providing sound, a communications system that allows the jukebox to communicate with the central server 12 over the communications network 14, and operating software that controls the operation of the jukebox, including a multitasking operating system. The operating software may be updatable through communications with the central server 12, for example, as described in the above-referenced U.S. Pat. No. 6,308,204. Additionally, the jukebox 16 may include one or more payment devices, such as, for example, coin, bill, and / or credit card deposit devices, that allow customers to conveniently pay for use of the jukebox. The screen 18 may be a touch screen that allows a user to select inputs by touching them.

[0031] In one embodiment, each jukebox may include a local server 22 accessible to the jukebox device. Each local server is connected to the jukebox device using an Ethernet or other type of local connection. In another embodiment, the local server may simply be a logical extension (e.g., a partition, directory, or area) of the jukebox hard drive rather than a separate hardware device. Each local server 22 includes a mirror copy of the master library of music records held by the central server 12. Before the local server and jukebox device are shipped to a jukebox distributor or operator, the local server 22 may be loaded with the master library by an entity that owns and / or controls the network of jukeboxes. Of course, due to the fact that the central server is continually updated with additional or new songs, over time the local server will no longer be perfectly consistent with the central server. Thus, the local servers 22 may also be periodically updated to continually match the library with the central server 12. For example, the central server 12 may perform the updates through communication with the jukebox devices connected to the local server 22, for example, using a dial-up or broadband modem. Alternatively, the updates may be performed directly using an update tool that a vendor or other person can connect directly to the jukebox or local server for the purpose of updating the content of the local server. The portable tool may include a removable storage medium, such as a hard drive, that can be returned to and reused by the owner of the jukebox system for future updates. The tool itself may be managed by an operator or other person responsible for maintaining the particular jukebox being used upon receiving the updated removable storage medium from the jukebox system owner.

[0032] For security reasons, the local server 22 does not contain all the digital data that constitutes any song stored on the local server 22. Furthermore, some of the songs on the local server are encrypted. The jukebox device 16 is provided with the missing portions of each song on the local server, which allows the jukebox to complete the song based on the contents of the local server and the contents of the storage device of the jukebox device. The missing data on the jukebox is necessary to decrypt the song. For example, a single block (or other small portion) of data for each song may not be present on the local server but is present on the jukebox device, and the encryption may proceed block by block based on the missing blocks. Thus, no block can be decrypted without obtaining and / or decrypting the previous block. This feature provides a great deal of security and prevents and deters theft and other types of unauthorized use or copying of songs on the local server. Thus, in this embodiment, each local server must be dedicated to a particular jukebox device so that the decryption described above can be performed properly.

[0033] According to an exemplary embodiment, each local server may be individually registered and identified to the central server 12 so that the central server can manage and monitor each local server individually. The same applies to the jukebox devices themselves, i.e., the jukebox devices may be registered to the central server so that the central server can manage and monitor each jukebox individually. As can be seen from the above, the local server is an important and useful part of the jukebox system by allowing the jukebox to access the content of the local server to provide further services not available on the jukebox itself (such as providing additional songs). As will be explained below, the song library and / or storage capacity of the central server itself can be advantageously used to provide services to other jukeboxes, such as pay-per-use home and commercial jukeboxes, and / or other pay-per-use devices. One use of the local server may be to provide instant song downloading functionality to the jukebox devices, which will be explained in more detail below with reference to exemplary screenshots of Figures 3 to 6.

[0034] FIG. 3 shows a typical screenshot of a music selection screen that may be displayed on the touch display of the jukebox device. As can be seen in FIG. 3, this selection screen, i.e., the initial selection screen presented to the customer, includes a graphical representation 32 of various album covers of songs stored in the storage device of the jukebox device. The album covers are displayed in alphabetical order, and a virtual slide bar 32 may be used to scroll through the available albums. Up and down arrows (34 and 35) are also used to step through the available albums. A "Now Playing" button 36 is also provided to display information about the song (if any) currently playing on the jukebox. A "Top Ten" button 38 is also provided to display a list of the ten most popular songs on the jukebox. A "Tune Central" (Touch Tune) button 39 is also provided to display information about the song (if any) currently playing on the jukebox. A "Top Ten" button 40 is also provided to display information about the song (if any) currently playing on the jukebox. A "Tune Central" (Touch Tune) button 41 is also provided to display information about the song (if any) currently playing on the jukebox. A "Tune Central" (Touch Tune) button 42 is also provided to display information about the song (if any) currently playing on the jukebox. A "Tune Central" (Touch Tune) button 43 is also provided to display information about the song (if any) currently playing on the jukebox. A "Tune Central" (Touch Tune) button 44 is also provided to display information about the song (if any) currently playing on the jukebox. A "Tune Central" (Touch Tune) button 45 is also provided to display information about the song (if any) currently playing on the jukebox. A "Tune Central" (Touch Tune) button 46 is also provided to display information about the song (if any) currently playing on the jukebox. A "Tune Central" (Touch Tune) button 46 is also provided to display information about the song (if any) A (registered trademark of Music Corporation) button 39 is provided, the function of which will be described in detail with reference to FIG.

[0035] If the user does not find an album of interest during the display of the album covers and for any reason wishes 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 of the jukebox changes from that of FIG. 3 to that of FIG. 4. The exemplary screenshot of FIG. 4 shows a search screen 40 that allows a search on the local server 22 connected to the jukebox device. This screen 40 is provided with a virtual keyboard 42 that is used to enter a search request. Based on the associated buttons 47, searches can be made by album, artist, song, or genre or theme (i.e., a list of songs categorized according to popularity that makes it easy for the user to locate a particular song). Once the search is entered, the user touches the "Search" button 44, which initiates a search of the contents of the local server. The input from the virtual keyboard can be cleared using the "Clear" button 46.

[0036] Genres may include, for example, "Pop," "Rock," "Country," "Rap," "R&B," "Blues," etc. Themes may include, for example, "Christmas," "Irish," "Birthday," etc. In some exemplary embodiments, these lists may be retrieved from a server, while in other exemplary embodiments, the lists may be dynamically created 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 store or type of music. The system may only display the genres and / or themes of music to be downloaded, or may display all genres and / or themes and allow other songs that are not available to be downloaded to the local jukebox. It will be appreciated that while FIG. 4C, described in more detail below, shows genres and themes on the same screen, in other embodiments, they may be displayed separately.

[0037] 4C is an exemplary screenshot showing a non-limiting list of genres and themes to a user according to one exemplary embodiment. Buttons 450 located on the left side of the screen correspond to themes available to the user, and buttons 460 located on the right side of the screen correspond to genres available to the user. Button 470 ends the selection process. It will be understood that the arrangement of buttons may vary and that the list of themes and genres is non-limiting and presented for illustrative purposes only.

[0038] Similar to searching by genre and theme, a user may search for songs using, for example, a Personal Music Assistant. A typical process is shown in FIG. 4A. After pressing the Personal Assistant button (step 402), if the user is not authenticated, the jukebox asks for specific information to identify the user (step 404). Such information may include, for example, age (or date of birth), preferred style, background, birthplace, or other information that can be used to generate a user profile. The jukebox then compares the profile information with selections made by other users with similar profiles, for example in a database for a particular jukebox, a particular store, or a country (step 406), and recommends songs. For example, the jukebox would suggest songs by "The Doors" to a male user from California born in 1960. The user can select a song from the list or start a new search (step 410).

[0039] Additionally, instead of entering an identifier, the personal music assistant can authenticate the user in other ways (e.g., after a credit card or preprogrammed site-specific identification card is swiped at the jukebox) as shown in FIG. 4B (step 422). The personal music assistant maintains the user-selected list. The user-selected list may be maintained, for example, locally at the jukebox terminal, at the site's central jukebox server, at a remote server, on the identification card, etc. After the personal music assistant has authenticated the user, it may recommend songs based, for example, on songs by artists that the particular user enjoys, songs that are frequently played by the user (428), songs that the user has not listened to recently (430), etc.

[0040] Furthermore, the personal music assistant, having authenticated, for example, a customer who is a good customer or has a lot of credits, may perform a configuration change process on the jukebox to make it more enjoyable for the particular user. In a related embodiment, a particular customer may rent a jukebox, for example, for a particular event. Thus, the customer may pay a certain fee to change the configuration of the jukebox to a specialized jukebox. For example, a customer having a party (e.g., a birthday party) at a particular establishment may rent a jukebox to allow only the customer's favorite songs. In another related embodiment, the customer may rent the jukebox exclusively and prevent others from selecting songs, for example, by creating a playlist through another device (e.g., the web or other communication network operably connected to the jukebox) or by restricting access to the jukebox with a password or the like. Credits may be purchased, for example, by the user or may be given to the user as a reward, for example, for purchasing beverages or souvenirs at the establishment or for being a frequent repeat customer. In this way, the personal music assistant can be implemented in a way that makes song selection a more fun, lively, and thoughtful process, while removing the immediate pressure on the user to know which song to choose.

[0041] When a search is initiated from screen 40, the screen changes to a screen showing the search results as shown in FIG. 5. As shown in FIG. 5, the search results are listed. More specifically, in this example, a set of songs that satisfy the search request are listed. If the search is album-based, they may be listed by album. The user can scroll through the search results using slide bar 53. The user is also shown an indication of the current number of credits 55 and an indication of the number of credits required to download the song from the local server to the jukebox device 56. The user can return to the previous screen by touching "Back" button 57. When the user selects a song from the selection list and further touches "Get It Now" button 54, the jukebox is operative to immediately download the selected song from the local server to the jukebox for playback on the jukebox. The downloaded song is placed in the jukebox's play queue along with other songs that have been selected but not yet played (if any). In this example, the download costs 5 credits instead of the standard 1 credit for a selection that is directed to the jukebox's own storage. Once a downloaded song has been played, it is deleted from the jukebox (along with any graphic data, such as an album cover image, downloaded from a local server in association with the song download). However, the song is preferably kept in a "smart cache" to determine if and / or when the song should be deleted. For example, the song may be cached for a predetermined period of time (e.g., one day, one week, two weeks, etc.), while the jukebox monitors the playing of the song. If the number of plays within the predetermined period exceeds a predetermined threshold, the song may be kept. If the number of plays falls below the threshold, the song may be deleted. Depending on the embodiment of the invention, the song may or may not be added to a master list of immediately available songs. For example, a song in the "smart cache" may appear to be unavailable to the user immediately, even though it is actually stored in, e.g., a protected area of ​​the jukebox.In this way, the user can “Tune. Through the use of the "Central" button, users have the option to temporarily retrieve any song from the master library of recordings on the jukebox without contacting the central server 12. As a result, the jukebox increases its revenue while providing a more enjoyable experience to its users.

[0042] Also providing a more enjoyable experience for users is the ability of the central server to identify HOT HITs, preferably in real-time. New songs are preferably made available in the master catalog, i.e., new songs do not need to be present on the local server or extended media storage. Songs that are played frequently in a particular geography (e.g., various geographies ranging from a single site or group of sites to a state, country, or global) may be considered popular. These songs, or HOT HITs, are preferably downloaded by and transmitted to each jukebox. Each jukebox preferably maintains a list of HOT HITs in real-time, allowing users to search for the most popular songs at any given time. Alternatively, the jukebox may maintain a list of HOT HITs without downloading a set of popular songs, potentially saving download time and resources. As a result, the jukebox may provide a more enjoyable experience for users by facilitating access to the most popular songs. In this manner, the jukebox may access a hot list of HOT HITs generated by one or more jukeboxes designated by the operator, automatically and / or specifically tailored for the available jukebox. This hot list may act as a proxy for theme and / or genre and / or work in conjunction with theme and / or genre to provide the most popular and hot songs within a given theme and / or genre. Similarly, a user may select songs from a list of recently played songs. Such lists may be maintained (e.g., stored and updated) at each jukebox. Alternatively, such lists may be maintained at a central store so that they can be accessed and / or updated from any appropriately configured jukebox device.

[0043] Figure 5A shows a typical process for maintaining a hot list on a jukebox with a broadband connection. Note that a similar process can be applied to systems with different types of connections, although downloading songs over a slower connection takes more time and resources. At step 502, a central server on the site receives songs from a master catalog. Of course, the songs can be stored on the local jukebox storage media. At step 504, a user at the jukebox terminal selects the "Hot List" button. After the "Hot List" is displayed (step 506), the user can select a particular song or initiate a new search (508).

[0044] FIG. 6 shows another exemplary screenshot of a song selection screen 60 that appears upon touching an album cover image on screen 30 of FIG. 3. This screen illustrates an alternative (or common) way of selecting songs. Songs are selected directly from a subset of songs available directly from the jukebox's own storage device (rather than a local server). In this example, "Joe Cokcer's Greatest Hits" is selected from the screen of FIG. 3. As shown in FIG. 6, the resulting screen display 60 displays the selected album image 61 and a list of songs 62 from that album available on the jukebox. The jukebox may or may not include all songs from a particular album. The available songs can be scrolled through using scroll bars 63a and 63b, if necessary. The user has the option to select a song from the list to be played on the jukebox via a "Play" button 65. A "Play Now" button is also provided to allow the user to select a song to be played in priority, with the song being given a higher priority than the song selected using the "Play" button. This priority feature preferably requires more play credits than normal play. Display 67 indicates the number of credits available to the user. Buttons 64 show other albums by the same artist shown in 61, allowing the user to easily find a desired song from a collection of albums by a particular artist.

[0045] As also shown in Figure 6, a "Tune Central" button 68 is displayed to allow a search for songs by the same artist on the local server as described in relation to Figure 4. That is, button 68 takes the user to search screen 40 of Figure 4 for searching the local server. The user can then, if desired, proceed to search the local server and select songs from the local server as described in relation to Figures 4 and 5. In this manner, as described above, the user can access the local server in a convenient and efficient manner at various screens as the user desires while interacting with the jukebox screens.

[0046] As can be seen from Figures 3-6, a user is given the option to play songs present on the jukebox device itself or, alternatively, to select songs to download from a local server and play in an efficient and reliable manner. This significantly improves the operation of jukebox systems, especially those that do not allow for quick, easy or reliable download of music on demand from a central server. It should be noted that the screenshots in Figures 3-6 are merely representative and any suitable screen configuration that provides the functionality described herein may be used. Additionally, the jukebox operator is given the ability to set filters by genre or type of music through an operational screen (not shown), thereby limiting access to end users and avoiding undesirable music being played in a particular store. For example, these features are preferably available during a schedule established by the jukebox operator and / or store manager, such that, for example, a store manager can prevent hard rock or heavy metal music from being played before 11:00 a.m. For example, the operator or store manager may use the same functionality to set playlists and / or select music available for a particular date and / or time. For example, an operator or store manager may wish to limit the music selection to Irish music on St. Patrick's Day, to love songs on Valentine's Day, to Frank Sinatra music at dinnertime, etc.

[0047] In yet another exemplary embodiment, a store may provide a virtual DJ. In such a system, pre-prepared playlists would be provided to the store's jukebox. The playlists can preferably be tailored to the specifics of the store and / or the event being performed (e.g., language, theme, target audience, etc.). Furthermore, some exemplary playlists may be created by famous DJs who attract customers. The DJs can put their name on the playlists and associate with various stores even when they are not present at the store. The playlists may be several songs or several hours long, depending on the store's needs. It will be appreciated that there is a special fee attached to the service of using the special playlists, so that there is no need to collect coins during such a virtual DJ event. It will also be appreciated that the DJ may prepare a special playlist for a one-time use or may create a reusable special playlist. The reusable special playlists may be downloaded by the jukebox, for example, or provided to the jukebox in any suitable manner. In this way, making third party playlists available on a jukebox for a fee provides an entirely new revenue stream for the playlist creator, such as an operator, venue owner, celebrity DJ, etc. When a playlist is active, it is desirable for the normal functionality of the jukebox to cease while songs from that playlist are being played.

[0048] 7 shows a block diagram of the electronic elements that define local server 22 according to an exemplary embodiment. As shown in FIG. 7, local server 22 includes a CPU 72 (e.g., AMD Elan 800 MHz), a flash memory (e.g., 8 MB) containing the BIOS and OS, a pair of master / slave hard drives (82, 84, 86 and 88, respectively), and a hard drive The local server 22 typically comprises a pair of IDE controllers 78 and 80 for each drive, RAM 76 (e.g., 32 MB), an Ethernet controller for controlling communications with the jukebox device 16, and appropriate buses for interconnecting the various elements. Of course, other configurations or arrangements can be used for the local server 22. The local server may be given a unique identifier so that it may be uniquely identified and registered by the jukebox and / or central server. The identifier may be located, for example, in flash memory 74.

[0049] As can be seen from the above description of the invention, the addition of a local server significantly enhances the operation of the jukebox devices that are part of a jukebox system, but the local server also provides other advantages and capabilities which will now be described.

[0050] A group of local servers 22 may be used as a network of distributed servers that the central server 12 can control through associated jukebox devices 16 that provide music services to other devices. For example, the local servers and associated jukeboxes can be used to provide music services to specific jukeboxes that are connected and assigned to them, as well as to send requested music to dedicated home or commercial jukebox devices (or other suitable jukebox devices). In this manner, the network of distributed servers can provide a support network for implementing such home and commercial jukeboxes that allow users to download music to be played and / or stored at home or in a store for a reasonable fee. As a result, a jukebox system operator can provide and control commercial and home jukeboxes through the jukebox system. In this embodiment, the jukebox devices and / or local servers are connected to the Internet (or other suitable network) using broadband modems and are provided with software that allows them to selectively send music files to any dedicated (also Internet-connectable) home jukebox under the control of the central server. The central server receives requests from home jukeboxes and instructs selected jukebox devices, by analyzing network traffic, to download the requested music files to the home jukebox (either from their own storage or a local server), taking into account the payment amount or subscription plan of the home jukebox. In certain exemplary embodiments, the requested music may be streamed to the jukebox. It will be appreciated that the streamed media may originate from a dedicated server, a network of streaming servers, one or more jukeboxes (such as peer-to-peer or multi-peer download), etc.

[0051] According to another exemplary aspect of the present invention, the local server and jukebox devices are used under the control of a central server to provide management services for other types of coin-operated or payment-triggered devices (e.g., gaming machines located in the same (or nearby) store as the jukebox). That is, the jukebox is preferably used to update and / or manage other download devices in the same store. As a result, the jukebox becomes the central hub for all download devices in the store. In one embodiment, this functionality is achieved by networking all download devices in a single store together with the jukebox and a local file server. The central server can download information to the local server along with instructions for the jukebox as to which devices should be updated with what data and / or software. The jukebox devices and central server can also be used to collect information from other download devices that it manages and upload information to the central server for reporting / accounting purposes. In this manner, the owner / operator of the jukebox system can act as a third-party service provider to manage and / or update devices of other coin-operated gaming companies.

[0052] The mass storage provided by the local server, and the fact that the local server is provided in many stores and accessible through a well-controlled network, makes the jukebox system a powerful tool that can be used to perform a variety of functions in the coin-operated gaming industry. Coin-operated game manufacturers are increasingly focusing on games that allow software updates using an internal hard drive. Updates are performed periodically, and as the number of such devices increases, the need for a system that allows reliable and efficient updates remotely will be greatly increased. The jukebox system described herein meets this need by allowing all suitable electronic gaming machines in a jukebox store to be managed by a central server using the store's jukebox and local servers. The central server downloads and stores software or data updates on the local server and transmits the updates to the desired equipment units within the establishment. In this way, the jukebox system acts as a third party to other companies in the coin-operated gaming business, which greatly increases its functionality.

[0053] As an example, there are currently approximately 140,000 coin-operated counter top devices in the United States, each of which allows users to play games etc. for a fee. Many of these devices run on hard drives that can be upgraded with new software. This is advantageous because it would require shipping CD-ROMs to operators who would have to drive to each store and manually update each machine. However, in the present invention, all suitable coin-operated machines in the store are connected (directly or indirectly) to a local jukebox and an assigned local server. This allows the central server to receive software updates for any device along with information identifying which devices should be upgraded with which software. The update service is preferably on a fee-based basis, providing an additional revenue stream for the jukebox system. The central server downloads the software along with upgrade instructions to the local servers, which then download the upgrade to the appropriate device(s).

[0054] As mentioned above, the local server allows songs to be downloaded to commercial or home jukeboxes to which it is assigned under the control of a central server. Additionally, the local server can be used for commercial networked applications to manage other coin-operated devices. These various features of the present invention are illustrated in FIG. 8.

[0055] Figure 8 shows a block diagram of a complete jukebox system network as contemplated in an exemplary embodiment. As mentioned above, the system includes a central server 12 connected to a communications network 14, a series of commercial jukeboxes 16a, 16b and 16c with corresponding music file servers 22a, 22b and 22c, a series of home jukeboxes 100a, 100b and 100c connected to the network via broadband devices 102a, 102b and 102c, and a commercial network as shown on the right side of Figure 8. The commercial network includes a jukebox device 16d connected to a local file server 22d via a router or network hub 110, a number of additional coin-operated gaming devices such as a dart game 104, a golf game 106 and a countertop video game 108, and a broadband modem 112 connecting the local network to the communications network 14. The exemplary embodiment shown in Figure 8 allows all of the functionality described herein to be implemented through the jukebox system of the present invention.

[0056] 9 shows an overhead view of a typical venue layout for a multi-zone jukebox system according to one embodiment of the present invention. In this embodiment, the venue includes three zones 121, 123 and 125. Each zone is equipped with its own speakers 127, 129 and 131 and operably connected to a jukebox 133. Different music may be played in all three zones simultaneously, or all music may be played from a single jukebox 133. The jukebox 133 may be provided with additional hardware to enable such implementation, if desired.

[0057] Alternatively, the user may choose to play music in one or more of the three zones simultaneously or at different times, or the user may have to pay additional credits to achieve any of these features. One embodiment of the multi-zone system can play high quality music in various zones using the system described in application Ser. No. 11 / 023390, filed Dec. 29, 2004, entitled "Wireless Digital Transmission System for Loudspeakers," and is a continuation-in-part of application Ser. No. 09 / 161,584, filed Sep. 28, 1998, the entire contents of both applications being incorporated herein by reference. For example, using the system, the jukebox can compress and transmit audio data over AC power lines m to an addressable store, where the audio data is then received, decompressed, converted, and played. In fact, any of the elements of the jukebox described herein can be implemented in a manner that uses the AC power lines as a communications network for operation.

[0058] It should be understood that the wireless digital transmission system can be used in other embodiments for other purposes where data needs to be transmitted between two or more devices. For example, the system can be used to set up dummy terminals. In such embodiments, in addition to transmitting songs to the speaker system, the wireless digital transmission system can be used to transmit information such as whether a configuration change should be made, which songs are appropriate for a given configuration change of the jukebox, the zone in which the selected music should be played, the maximum volume level, etc.

[0059] The operator may limit the type of music available in a given zone based on the type of activity in that zone, the time of day, or other suitable selection criteria. For example, in FIG. 9, Zone 3 (125) is a restaurant. Customers of the restaurant may not like to listen to the same type of music as customers of Zone 1 (121), which is a bar room, or Zone 2 (123), which is a billiard room in FIG. 9. The operator may recognize this and limit the type of music that can be played in Zone 3 (125). Alternatively, the operator may limit the volume of music in a particular zone. For example, customers of the billiard room 123 or restaurant section 125 may not want music that is as low-pitched as is desired in the bar room 121. And the restaurant section 125 should be kept much quieter than the billiard room 123. The owner can adjust and control all the settings as appropriate to provide each zone with the most diverse customer-friendly environment based on the appropriate criteria.

[0060] 10 shows an overhead view of a typical venue layout for a multi-zone jukebox system with selection terminals in each zone. In a typical embodiment, the bar has three zones 121, 123, 125. Each zone is equipped with its own speakers 127, 129, 131 and operably connected to a jukebox 133. Different music may be played in all three zones simultaneously, or all music may be played from a single jukebox 133. The jukebox 133 may be provided with additional hardware to enable such an implementation.

[0061] In the embodiment of FIG. 10, one or more dummy terminals 137, 139 are present throughout the facility. Exemplary and exemplary dummy terminals may use X-server technology. These terminals 137, 139 may be standalone devices or may be part of the interface of a gaming device or other suitable device with a digital display. These terminals 137, 139 allow for the selection of music from the jukebox 133 in the zone in which they are located (or in other zones). These terminals 137, 139 replicate the zone restrictions and selection criteria imposed on the main jukebox interface. The terminals 137, 139 may allow for the selection of music to be played only in the zone in which they are located, or may allow for the selection of music to be played in one or more different zones.

[0062] Additionally, the graphic interfaces of the terminals 137, 139 may be altered depending on available selections such as the theme of the bar or the theme of the room in which each terminal is located, or any other suitable criteria.

[0063] FIG. 11 is a flow chart illustrating an exemplary implementation of a zone selection process in a multi-zone jukebox system. In a typical embodiment, the jukebox first initiates a transaction (141) with a user. The user is prompted to select a song (143) and select one or more zones (145) in which the song should be played. The jukebox then determines a fee (147) based on the number of zones selected. The jukebox receives payment (149) from the user and queues (151) the song for playing in the selected zone or zones 151. The jukebox then checks (153) whether the user wants to select another song 153. If the user does want another song, the process repeats, returning to the song selection step 153. Once the user has completed their selection, the process ends (155).

[0064] FIG. 12 is a flow chart illustrating an exemplary implementation of priority play by zone selection processing in a multi-zone jukebox system. In an exemplary embodiment, a particular jukebox system is provided with one or more priority queues corresponding to one or more zones. When priority play is prepared for one or more zones, the jukebox checks (161) whether the user wishes to select priority play for the selected song. If priority play is selected, the jukebox provides (163) an option for the user to select one or more zones in which priority play should occur. Based on the number of zones for which priority play is selected, the jukebox determines (165) a fee and accepts (167) payment from the user. The jukebox then places (169) the song in the priority play queue for each selected zone.

[0065] 13 illustrates an exemplary implementation of a multi-zone set of priority and non-priority queues with a subset of queues for each zone. In an exemplary embodiment, each of N zones 171 may have its own queue set including a priority queue 175 and a non-priority queue 173. A list of songs selected for playback is maintained in each queue 173, 175. The songs in each queue may be provided with an identifier 177, 179 that identifies the song and / or the song's position in the queue and / or other suitable factors.

[0066] In certain exemplary embodiments, songs in a queue may be reordered for other reasons, such as to smooth transitions between songs and to provide better end-to-beginning playback (e.g., more audibly pleasing, less abrupt, or smoother). Thus, in certain exemplary embodiments, a method is provided for reordering songs for playback. In such a process, a song "tone" may be determined for two or more songs in a playlist. A song's tone may relate to song characteristics such as, for example, the song's volume, rhythm, beat, tempo, etc. After tone determination, the tones may be compared and the songs may be reordered to group songs that are liked (or disliked). Alternatively, the tone of the songs may be determined and used to control lighting, displays, etc., for example, to provide a more interactive experience.

[0067] Figure 14 is a flow chart illustrating a typical distribution and start-up scheme for a jukebox with reconfiguration capabilities. In a typical embodiment, the contents of a factory drive are defined at the time of manufacture (181). This same drive (or one with enhanced storage capacity) may be shipped with every jukebox (183), e.g. For example, the drive may contain only a portion of all songs available on the central server. This feature simplifies the manufacturing process by allowing identical drives to be shipped with all jukeboxes. When the jukeboxes with drives arrive at their destination, the operator may select a portion of the songs on the drive as a base playlist (185). This selection may be based on the type of establishment, the type of music that the customers of the establishment generally like, or other suitable criteria. The operator may allow the central server to recommend the base playlist. The drive may allow the selection of songs that are not on the base list but are on the factory drive for an additional fee (187). However, the list of "alternate" songs may not include all songs, as the operator may wish to limit access to songs that do not fit the theme of the establishment. For example, the owner of a country bar may not want to allow rap or hip hop music to be selected on the jukebox. In certain exemplary embodiments, the jukeboxes are shipped with a large number of songs (e.g., 25,000 songs) stored on very large storage media such as hard drives, flash media, etc. A jukebox according to this embodiment would have no "personality" until the operator and / or owner selects a portion of the songs in the collection to make available to customers. In this manner, the operator and / or owner can define the "personality" of the jukebox through the definition of a basic playlist.

[0068] Once the songs in the drive have been properly categorized (i.e., a basic playlist has been defined), the jukebox begins operation (189). The jukebox continues to operate with the currently selected basic playlist (189) unless a new basic playlist is desired (191), in which case the jukebox selects another portion of the playable songs as basic selections and preferably also transforms its configuration into a new jukebox (193) by modifying additional characteristics of the jukebox (e.g., graphics, advertising, rock and feel, etc.) as instructed by the configuration change. The ability to change the configuration of a jukebox allows an owner and / or operator to maintain a single jukebox with multiple triggerable personalities that can be switched automatically, when certain events occur / at certain times, manually, or otherwise.

[0069] FIG. 15 is a flow chart illustrating an exemplary implementation of a process for initiating automatic jukebox configuration changes based on a trigger event. In an exemplary embodiment, a user can define an event, such as a night-themed event, time of day, etc., as a trigger event that will cause the jukebox to change configuration (201). The jukebox then performs normal operation while periodically checking for the occurrence of the trigger event (203). If the trigger event has not occurred, the jukebox simply continues to operate (203), but if the trigger event occurs (205), the jukebox changes its configuration to the new jukebox. The trigger event may be a one-time event or may be scheduled to occur weekly, daily, monthly, or on any other suitable basis. It is noted that in a multi-zone configuration, various zones may change configuration while the remaining zones do not. This feature in an exemplary embodiment may, for example, dedicate one or more given zones to a particular type of music while the remaining zones may vary depending on various factors such as time of day, the owner's desire to change music, user requests, etc.

[0070] FIG. 16 is a flow chart illustrating an exemplary implementation of a jukebox configuration change process. In an exemplary embodiment, when the jukebox initiates a configuration change (211), it selects (213) a new subset of songs to become the basic playlist. The jukebox then makes all or a portion of the remaining songs in the jukebox available for selection for an additional fee (215). Some of the remaining songs may be restricted depending on what triggered the configuration change. Other characteristics of the jukebox may also be changed (217). For example, the user interface may be changed to correspond to the predicted crowd interest that triggered the jukebox configuration change, and different advertisements may be displayed. Other suitable changes may also be made. In an exemplary embodiment, a club owner hosts a hip hop night on Wednesday night from 9:00 PM to 4:00 AM. At 9:00 PM on Wednesday, the jukebox changes its configuration to a hip hop jukebox with the appropriate music as a basic selection. Following the configuration change, the jukebox blocks all access to music in the genres of country music, classic rock, and blues oldies, and only allows the selection of hip-hop-inspired hard rock songs as supplements to hard rock. The jukebox graphics change to edgy, urban graphics, and advertising changes accordingly to display products such as apparel, beverages, and merchandise that appeal to the hip-hop crowd. At 4:00 AM, the jukebox configuration changes back to the club's standard jukebox, or to another suitable jukebox. Alternatively, the jukebox may remain in the hip-hop mode setting until the next trigger event occurs. Again, in a multi-zone configuration, various zones may be configured to change while the remaining zones remain unchanged. In the exemplary, non-limiting embodiment described above, the system may change the configuration of one zone to hip-hop for the night, while other areas continue to play the club's standard music.

[0071] 16A is an exemplary screenshot showing how jukebox reconfiguration may be initiated in one embodiment. Area 160 is blank, indicating that nothing has been selected. In this exemplary embodiment, a user selects a reconfiguration option by, for example, selecting one of the "TouchTunes Master" button 162, the "Dynamic Master" button 164, and the "Clone a Location" button 166. It should be understood that in other embodiments, other reconfiguration options may be provided in place of or in addition to the above-mentioned buttons. In this embodiment, upon pressing the "TouchTunes Master" button 162, area 160 displays a master selection list that has been preselected by the TouchTunes music division. The master selection list may, for example, be For example, a particular collection of songs (all songs by a British band, all songs by a particular artist, etc.), a particular theme or genre ratio (e.g., 75 percent hip hop, 10 percent pop, 10 percent rock, 5 percent a particular dance club style techno, etc.) may be included. The user may use slide bar 170 to peruse the list. When the user is satisfied, he or she presses the "Morph It" button 168, which causes the jukebox to change configuration. It should be understood that pressing the "Morph It" button 168 may initiate a morphology change immediately, or may not be instantaneous and may initiate a morphology change at a predefined trigger time. It should also be understood that morphology change data may be stored to morph the selected jukebox or any number of connected jukebox terminals.

[0072] Pressing the "Dynamic Master" button 164 is an exemplary, non-limiting way to enhance user control of the configuration change. FIG. 16B is another exemplary screenshot showing how a user can specify various criteria before the jukebox configuration change in an exemplary embodiment. Buttons with the same number in FIG. 16A and FIG. 16B are not described. A music genre and / or theme is specified, such as a rap label 172. The user can specify the percentage of music to be played by pressing an "increase" button 174 or a "decrease" button 176. The number of songs selected for a particular genre or theme appears in a theme music number area 178, while the total number of songs selected appears in a total music number area 180. In one embodiment, the user may specify the percentage of genre and / or theme to be played. For example, the user may select 100 percent country music for a country night. Or, as another non-limiting example, a mix of world music and Latin music may be selected to create an international feel. It should be appreciated that while the exemplary embodiment uses a percentage, other embodiments may use other criteria to specify how many pieces of what type of music should be played, such as, for example, the number of songs in a particular category or the duration of a particular genre and / or theme. It should be appreciated that in other embodiments, the user need not use buttons to increase or decrease the number of pieces of music; that is, in other embodiments, the user may directly input the number of pieces of music via an input mechanism. In this manner, it should be appreciated that a remote device operably connected to the jukebox may define and / or initiate the configuration change.

[0073] When a user presses the "Clone a Location" button 166 (e.g., from FIG. 16A or 16B), the jukebox displays a list of jukebox devices, preferably including an identifier for each jukebox. However, in other embodiments, the list may include, for example, other stores owned by a store owner. After selection of a jukebox terminal, the jukebox may be reconfigured to that jukebox. Alternatively, the selected jukebox may be reconfigured to the jukebox, allowing, for example, remote reconfiguration. Also, or alternatively, the list may include information about non-digital jukeboxes that exist along with the jukebox of the exemplary embodiment. This reconfiguration feature allows a user to quickly and easily replace an existing jukebox by changing the configuration of the new jukebox to the old jukebox that is to be replaced (e.g., a traditional record jukebox, a CD jukebox, or a digital jukebox). Additionally, operators maintaining large numbers of jukeboxes may apply route-based cloning and / or reconfiguration processes, for example, to provide customized or canned song sets.

[0074] Additionally, a user may change the store configuration based on, for example, the store's data on a particular day, or the most recent data known. This allows a user to change the jukebox configuration based on, for example, the popularity of a particular configuration change. For example, a user may choose to revert to a successful configuration change in an attempt to recreate the fun of that evening. This feature also allows a user to recover from hard drive crashes and / or other jukebox failures. For example, if a hard drive has been replaced after a previous crash, a user may reconfigure (or replicate) an existing store at a particular date and / or time before the crash to recover songs that were available before the crash. This is because the server preferably maintains sufficient information regarding this feature. In this manner, the use of the configuration change feature provides increased control for the user while providing backup and recovery capabilities.

[0075] FIG. 17 illustrates the relationship between a jukebox with expanded media storage and a central server. In a typical embodiment, the central server 221 includes a master library (e.g., a library containing all songs currently available for download and all songs currently located on the jukebox's hard drive). The central server may communicate 222 with a remote jukebox 225 that includes a local hard drive 223. The jukebox's hard drive 223 may include multiple sections including space available for downloads 227, space occupied by preloaded songs, and space for software and operating system 229. Further appropriate sections may be added (e.g., a section containing various images for changing the GUI). The jukebox 225 may communicate with the central server 221 to download songs, upload usage information, update software, and perform other appropriate functions.

[0076] 18 is a flow chart illustrating an exemplary process for selecting a song when the song is not included in the "standard" available song list for play. In a typical embodiment, the user first selects a song (231). The jukebox checks (233) whether the song is available on the local hard drive as a "non-standard" selection. If the song is available on the local hard drive, the jukebox charges the customer (235) a set amount for acquiring and playing the non-standard song. The jukebox then plays (237) the song or adds the song to a playlist, if appropriate.

[0077] If the song is not available on the local hard drive, the jukebox checks (239) to see if a high-speed connection to a central server is available. If a high-speed connection is not available, the jukebox notifies 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 fee for ordering the song. On the other hand, if a high-speed connection to a central server is available, the jukebox immediately orders the song, uses the high-speed connection to download the song immediately, and queues the song for play (245). The jukebox then charges the customer the fee for the non-standard selection (247). In certain exemplary embodiments, the jukebox may search for songs offline after the store closes or before the store opens. In certain exemplary embodiments, the jukebox may immediately download the song over a dedicated line over a dial-up connection. In certain exemplary embodiments, songs may be downloaded from another jukebox (or other jukeboxes) rather than from a central or restricted database to reduce network load. In certain exemplary embodiments, a jukebox may download songs via a distributed media service where portions of a particular song are downloaded from multiple sources and reassembled at a target jukebox. In such peer-to-peer (jukebox-to-jukebox) or multi-peer (jukebox-to-jukebox) digital download networks, song license information needs to be tracked. In certain exemplary embodiments, if a song is not available on a jukebox, but other versions or covers of the song are available, the jukebox may recommend these other songs to a user searching for them. For example, a user searching for an unavailable Trisha Yearwood version of "How Do I Live" may be recommended the available Dolly Parton and / or LeAnn Rimes versions.The recommendations are hopefully clever enough to ignore songs with similar but completely different titles, such as "Oh Pretty Woman" by the Everly Brothers and "Pretty Woman" by Motley Crue.

[0078] The factory drive described above, combined with the reconfiguration functionality, reduces the need for the local server described above, since the factory drive can demonstrate the same services as the local server without the need for a separate hardware device. That is, the factory drive of this embodiment allows a jukebox to be shipped with a single mass storage device of any technology (or a single mass storage device of multiple technologies and / or multiple devices acting as a single mass storage device), while providing basic playlist definition, extended playlists to be defined, reconfiguration functionality, provision of local server services, and all other functionality described herein. The contents of the factory drive as shipped are preferably determined using historical and statistical information regarding customer preferences.

[0079] FIG. 19 is a flow chart illustrating an exemplary operation of a priority play queue with prioritization-based-on-bidding. In an exemplary embodiment, a user first indicates (251) that they would like to perform priority play. The jukebox displays (253) the current state of the priority play queue. This display may include the number of songs in the queue, the top bid, the bid amount for each song, songs that are locked in, and other suitable information related to priority play. The jukebox then allows the user to select how much extra money they are willing to pay to place the song in a special spot in the priority list, and accepts (255) payment of the selected amount. After receiving (255) payment, the jukebox then places (257) the song in the priority list according to the extra amount accepted from the user.

[0080] Alternatively, in an exemplary aspect of another exemplary embodiment, a user may bid for the right to play a song before other songs that have previously been selected for priority play are played. In one embodiment, the highest amount paid for priority play is shown to the user, and the user may pay more than that amount to obtain the highest priority.

[0081] Another exemplary aspect of the exemplary embodiment is that the user is not shown how many other people have paid for priority play, the user can pay whatever amount they want to get priority and get the priority according to the amount paid.

[0082] In yet another exemplary aspect of the exemplary embodiment, a user can pay whatever amount they want to pay to get priority according to the previous exemplary aspect, and the user is shown the priority spot that they have obtained according to the amount they paid. If the spot is not satisfactory to the user, the user can pay an additional amount to increase the priority of the song, and the user is shown the new priority that they have obtained according to the additional amount they paid. The user can repeat this process until they obtain the desired priority. The user can also pay an additional amount to make it difficult for other users to preempt the selected priority spot in the list by bidding. Any other suitable method of increasing the priority with an increased payment can also be implemented.

[0083] In a further exemplary aspect of an exemplary embodiment providing a confirmation feature, a user may confirm a priority by paying a preselected amount. For example, if a user pays 15 credits to obtain a third priority and wishes to have the third place compensated, the user may pay, for example, an additional 4 credits to confirm the position.

[0084] Since a lock-in requires that all songs above the user be locked in, the user must pay a certain amount to lock in all songs above the selected song. In such a situation, the user may choose to either pay a "lock-in" limit or pay the same or a different number of credits to avoid future high bids or to move the user's song further up the priority list.

[0085] In a typical aspect of an exemplary embodiment, any of the above mentioned trading strategies may be implemented and the user may be shown how much everyone has paid for a particular ranking, so that the user knows exactly how much they will have to pay to get a particular priority. If a "set" feature is implemented, it may also let the user know whether it is cheaper to pay to set a song or pay to increase the priority. All of these options result in increased revenue for the operator.

[0086] It should be noted that while the above embodiment describes a system for distributing media to a non-transportable jukebox, another embodiment using a similar system may distribute media to a portable jukebox. Such a system is contemplated by the present invention and does not depart from the scope and spirit of the present invention. The portable jukebox may be, for example, a PDA, a cell phone, or any other mobile device capable of receiving and playing music. Furthermore, media may be distributed to the portable jukebox using the methods described above (e.g., via a broadband connection, wireless connection, etc.) or using other methods appropriate and more suited to the particular portable device (e.g., using Bluetooth technology). Furthermore, while the above-described jukeboxes are typically used for commercial purposes, the present invention contemplates jukeboxes for other uses (e.g., for playing media for home use) and does not depart from the scope and spirit of the present invention.

[0087] In other exemplary embodiments, employees of a jukebox establishment may be compensated for the number of paid plays that customers make on the jukebox. In such exemplary embodiments, a system keeps track of the number of paid plays made by customers. Each time a certain number of paid plays are made, the bar employee receives one free play. In some embodiments, separate counters may be maintained, and in other embodiments, only one counter may be needed to calculate the number of free plays available. Thus, certain exemplary embodiments may motivate employees to promote the jukebox by compensating them with free plays. This also reduces the number of similar song selections throughout the day and maintains free plays for employees on different shifts.

[0088] Similarly, jukebox users may vote for a particular media instance to change its priority in the playlist. In this manner, jukebox users may, for example, "compete" for control of music played in a zone or multiple zones within or across a store. It should be appreciated that this voting / competition mode may be implemented using, for example, dynamic queues, priority queues, multiple queues, etc. Also, the jukebox may enter voting mode automatically (e.g., at a particular time and / or on a particular day of the week) or may be manually entered. FIG. 19A is a flow chart illustrating an exemplary implementation of a jukebox voting process. Unlike a traditional jukebox or jukebox bidding mode, in step S1902, a list of songs in the jukebox queue is presented to the user. This list may be generated automatically or may be created by the operator, bartender, bar patrons, etc. This list may be displayed, for example, on the jukebox, but is preferably displayed on one or more standalone monitors. Additionally, in certain exemplary embodiments, this list may be viewable on multiple mobile devices and / or handheld terminals. The displayed information preferably includes at least the artist and song titles of the upcoming songs, as well as a number corresponding to the priority of those songs. The list should be sorted by this number so that the song with the most votes is displayed as the song to be played "next", followed by the song with the next most votes. At step S1904, it is determined whether the currently playing song has finished. If so, at step S1906, the song is removed from the queue and the next song is played at step S1908. In another embodiment, the user can decide to stop or skip the currently playing song (or media instance), for example by voting to exceed the number of votes the song had before the jukebox started playing.

[0089] As users browse through the songs, they will be tempted to push up songs they like and / or push down songs they don't like. In general, the more users who vote, the better the mood of a good song. Thus, after step S1908, or if the song is not over, the jukebox accepts user votes for the particular song in step S1910. Voting may be credit-based (as users purchase credits) or in association with a user account. In certain example embodiments, a user may only vote a limited number of times. Users preferably vote from at least two different locations within a store. The columns are updated based on this vote in step S1912, and the process returns to step S1902, where the display list is updated.

[0090] In certain example embodiments, the queue may be based on the total number of votes for a particular song. In certain other example embodiments, users may vote for and / or against a given song and a "full" information may be displayed indicating the number of votes for and against, or simply the result. If the number of votes against exceeds the number of votes for, the system performs one or more of the following functions. For example, the jukebox may simply continue with songs in the queue that have a negative number of votes. The jukebox may also continue with songs in the queue that have zero votes or a negative number of votes, but always wait, for example, until the total number of votes reaches at least 1 before playing the song. The jukebox may also stop any songs that have zero votes or a negative number of votes.

[0091] FIG. 19B(1) is an exemplary screenshot showing a display of a column of vote counts. Display 1900a shows a currently playing song 1902 and its progress 1904. The progress 1904 of the currently playing song 1902 may be displayed in any manner, such as, for example, a number representing the time remaining, a slide bar, etc. A list of artists and songs 1906 is preferably displayed in vote count area 1908a based on the number of votes for each. Alternatively, user area 1910 may display information about the users voting for the song, such as, for example, the user who has the song listed, the user who last voted for the song, the names of groups "battling" to play the song, etc.

[0092] Figure 19B(2) is another exemplary screenshot showing a display of a column of vote counts. Figure 19B(2) is similar to Figure 19B(1), except that the vote count area 1908b reflects the user's "total" votes. This is similar to, for example, Figure 19B(1), where the display shows not only the total votes, but also the number of votes for and against a particular song.

[0093] FIG 19C is an exemplary block diagram showing any in-store voting mechanism. Display 1900a corresponds to FIG 19B(1) but could alternatively be a display corresponding to FIG 19B(2) or other display showing the same or similar information. The list is preferably updated by the jukebox 16. Users vote by the jukebox 16 to update the list (e.g., by voting for and / or against songs) or by any device optionally connected to the jukebox 16, such as, for example, another jukebox 1912a, a remote terminal 1912b, a laptop 1912c, a PDA 1912d, a cell phone 1912e, another mobile device 1912f, etc.

[0094] Figure 19D is another exemplary block diagram showing an arbitrary in-store voting mechanism, which differs from Figure 19C in that it does not involve a jukebox 16, but rather allows users voting from any connected device 1912a-f to directly influence the voting list.

[0095] Other applications include voting mechanisms where multiple establishments (e.g., bars, restaurants, venues, etc.) are networked together, for example, by the Internet. These linked establishments allow more patrons to "play" against each other. In this embodiment, the networked jukeboxes play the same songs, and optionally all users from all establishments decide the order of play using a voting system or the like. Thus, FIG. 19E is an exemplary block diagram illustrating a voting mechanism for use with multiple establishments. A first jukebox 16(1) in a first establishment, with and communicating with a first plurality of portable devices 1912a(1)-f(1), and a second jukebox 16(2) in a second establishment, with and communicating with a second plurality of portable devices 1912a(2)-f(2), influence the playlists accessible by the jukeboxes 16(1) and 16(2).

[0096] Another application of this voting feature is to enhance the "stop" mode of a jukebox. In stop mode, the jukebox typically does not allow the user to select music from the jukebox. For example, a bartender may use the stop mode when there is a special event (e.g., a football game) in the establishment and the establishment's audio system is broadcasting the game or event. This voting feature may be used to select which song will be played after the special event is over. It is a common sight to see patrons who are watching a game closely leave the establishment when the game is over. This other way of selecting the music to play may encourage patrons to linger in the establishment and / or continue using the jukebox, etc.

[0097] According to one exemplary embodiment, FIG. 20 is a flowchart illustratively illustrating a process for using a user-adaptive system for music management, communication, etc. It is understood that a Personal Music Assistant may function as a complementary system, component, etc. of the system according to this exemplary embodiment. In step S2000, a user accesses the user-adaptive system, in this case recording MyTouchTunes. It is understood that the user accesses the system, for example, at a number of stores, via an Internet front end, a jukebox terminal, etc. It is further understood that the user accesses the system in any manner, for example, by entering a username and password combination into the Internet front end or a jukebox terminal, by swiping a credit card at a jukebox terminal, by scanning a site-specific "smart card" or flash card, etc. In certain exemplary embodiments, the user is recognized through biometric data, such as a fingerprint, a retina scan, etc. Of course, biometric authentication may function independently or in conjunction with more traditional forms of user identification such as, for example, a username / password combination, smart card, etc. The system determines whether it recognizes the user in step S2002. If the user is not recognized, the user may be prompted to create account / profile information, as in step S2004. Account / profile information is described in more detail below with reference to FIG. 21A.

[0098] If the user is recognized in step S2002, the MyTouchTunes main menu is displayed to the user in step S2006. A user using the system according to this exemplary embodiment may, for example, edit account / profile information from the MyTouchTunes main menu in step S2010, manage music in step S2020, manage friends in step S2030, communicate with others in step S2040, and access a variety of valuable content provided by the system in step S2050. These and other features are described in more detail below with reference to Figures 21A and 21B.

[0099] FIG. 21A illustratively illustrates the options available for editing account / profile information in one exemplary embodiment. As discussed above, it will be appreciated that the exemplary steps illustrated in FIG. 21A correspond to the steps required for initial account / profile setup. However, during such initial setup, the exemplary system will require the user to register the required information all at once (step S2006 in FIG. 20) before allowing the user access to the main menu. It will be appreciated that such account / profile information may be stored in a variety of locations as required for any implementation, such as, for example, in a central location or database, on a server for a particular store, on a given jukebox terminal, and / or on a removable card that identifies the user and user information when inserted into the jukebox.

[0100] The user first inputs personal data in step S2012. Such personal data may include, for example, the user's email address, phone (preferably mobile) number, and / or name. The system prompts the user to create a unique username and password so that the system can identify the user in the future and from other stores. Alternatively, the system may use the user's email address as the username and only require a password. Alternatively, for example, in the case of a residential jukebox, a typical system may not require a password at all. Based on the personal data, a typical system may send emails and text messages to the user as well as gather enough information to authenticate the user upon login (e.g., online access, preferred store, other stores in any area, etc.). These typical functions are described in more detail below.

[0101] In step S2014, the user identifies various stores that he or she frequents. This function may allow tracking of the user by various stores, advertisers, etc. The establishment may, for example, provide special offers to patrons or others in a particular area to entice them to visit. Advertisers may monitor personal information, store information, playlists, for example, to provide concert tickets, special offers in CD envelopes, t-shirts, and / or other attractive merchandise based on the user's preferences. If such account / profile information is stored locally at various terminals, the system may also communicate with these other terminals to provide playlists in preparation for the user's visit. In step S2016, the user adds credits and / or specifies payment information. For example, the user may increase the number of credits owned by the user by using the user's credit card before entering or while at the store. The user may also be "authenticated," for example, by providing credit card information and then having the jukebox automatically charge the credit card when purchasing credits later. It will be appreciated that step S2016 may be used to purchase credits for the user himself or herself, or for someone else, such as, for example, the user's friends, store dwellers, etc. It will be appreciated that the user may transfer money from an account, such as, for example, a Pay-Pal account, to an account specific to the jukebox, or the user may use such an account to purchase music and / or other services directly.

[0102] In certain exemplary embodiments, a user may register by creating an account on the jukebox and providing a verifying contact mechanism, such as, for example, a mobile phone number and / or email address. After the user creates the account and enters the verifying contact mechanism, a message may be sent to the store. For example, the user may receive a text message. Once the message is received, the user may be prompted to enter a code into the jukebox, send a return email or text message, etc., to be fully registered and / or to use certain other advanced features, such as, for example, one or more of the features disclosed herein.

[0103] FIG. 21B illustrates illustrative options available for managing music in one exemplary embodiment. In step S2022, the user may create or edit an existing playlist. Preferably, the user may search for songs using the methods described above and / or may use system ideas to build the playlist. Preferably, the user may give the playlist a descriptive title, such as, for example, "Favorite Plays," "80s Nights," "Feel-Good Love Songs," etc. In addition, the user may call the playlist "public" or "private" to allow or restrict other users from viewing the playlist. In step S2024, the user may rate the songs and / or playlists through the picklist function. The pick list may also create a custom playlist that includes the songs that the user has rated highest to date. The pick list may also include a list based on the hot hit list described above. In step S2026, the user may have the jukebox play music using, for example, any of the methods described above, with or without the use of a playlist. Typically, by selecting a playlist for the jukebox to play, the user adds those songs to the normal queue. However, as described above, the user may pay an additional fee and / or use the bidding mechanism described above to have music played immediately. Furthermore, selecting a playlist for the jukebox to play typically plays all the songs in that (or those) particular playlist. However, the user may not select certain songs so that they are not played. This allows the user to dramatically further customize the playlists when listening to music.

[0104] Additionally or alternatively, other playlists may be imported from external sources. For example, software and / or hardware devices often store user-defined and / or customer-created (e.g., frequently played, recently added, etc.) playlists. By way of example and without limitation, playlists may be pulled from an iPod, portable MP3 player, and / or other hard device. This may be done at the jukebox using an appropriate hardware connector provided with the jukebox, and / or at a device remote from the jukebox (e.g., at a home computer) where an appropriate hardware connector (e.g., a dedicated docking port, USB connection, etc.) is already in place. In either or both cases, the playlist may be imported from a local device, after which the playlist may be uploaded to a central audiovisual distribution server. Similarly, by way of example and without limitation, playlists may be pulled from iTunes, Windows Media Player, and / or other software applications. In many cases, such devices and / or software applications store the playlist in an unencrypted and / or unencoded manner so that the playlist can be read in a manner similar to a flat text file. In this and / or other manners, the imported playlist may be made available to one or more jukeboxes connected to an audiovisual distribution network. Of course, in certain other cases, it may be necessary to decrypt, unencode, and / or perform other processing on the playlist of other hardware devices and / or software applications prior to processing the now readable playlist to make it suitable for use in, for example, a jukebox or in connection with a jukebox-related service.

[0105] This functionality is beneficial to the user in that it reduces the need to create and subsequently re-create existing playlists, at least to the extent that a single playlist may be defined on the device and then subsequently used on the jukebox without extensive re-entry, re-selection, and / or re-grouping of similar information. Such techniques also provide other means for interacting with the jukebox and customizing the jukebox to the user's tastes, for example, by enabling customization of playlists using devices and / or software applications with which the user may be more comfortable, have more experience, or have a different interface.

[0106] Thus, there is provided in certain example embodiments a system and / or method for distributing playlists to one or more digital jukeboxes connected to an audiovisual distribution network. A peripheral device, having a playlist for the peripheral device stored in a computer readable storage medium of the peripheral device, is connected to the digital jukebox via a connector. The playlist for the peripheral device is retrieved for the jukebox. This may be accomplished by programmed logic circuitry (e.g., any suitable combination of hardware, software, firmware, and / or the like) provided in the jukebox. The playlist for the peripheral device is converted into a jukebox playlist. The jukebox playlist is published at least on the jukebox. Similarly, a software application running on a computing device (e.g., a computer, a laptop, a PDA or other similar portable computing device) may be read by the computer and published to a server on the audiovisual distribution network.

[0107] The playlist for the peripheral may be stored, at least temporarily, in a computer readable storage medium of the digital jukebox. A determination is made as to whether the jukebox playlist is to be referred to as a public jukebox playlist or a private jukebox playlist. Based on the determination, the jukebox playlist may be made shareable or may remain private to the particular registered user importing the playlist.

[0108] Jukebox playlists may be transmitted to a server of the audiovisual distribution network, and jukebox playlists may be made available to jukeboxes connected to the audiovisual distribution network and / or remote devices connected to the audiovisual distribution network. A user importing a playlist must log into the jukebox or jukebox portal before being allowed to import the playlist.

[0109] A jukebox device is also provided for implementing the same and / or similar functionality, where at least some of the functionality is possible using a processor provided in the jukebox.

[0110] In certain exemplary embodiments, it is beneficial for users to refrain from creating playlists directly at the jukebox by using the jukebox interface itself. For example, this reduces crowds around the jukebox, monopolization by a single user or users, etc. Also, or in addition, the functionality for users to create playlists directly at the jukebox is reduced. For example, a user may create a playlist from a predefined combination of songs, which may include only songs played by the user on that particular night on the jukebox in that particular store, on any jukebox connected to an audiovisual distribution network, etc. In this manner, users may benefit from the techniques described herein for customizing playlists directly at the jukebox, and may reduce the time required for customization. Additionally, users may be prompted to create playlists of songs that have been played and songs that are likely to be played again.

[0111] Thus, in certain exemplary embodiments, a system and / or method is provided for playing media on a digital download jukebox. A user is required to log into the jukebox. A plurality of selectable media is provided for playing on the jukebox. User selections of media instances from the plurality of selectable media are made available to the jukebox via a user interface. For each user selection, the media is added to a playlist stored in a computer readable storage medium of the jukebox. The media in the playlist are played in order. The plurality of selectable media is selected by the user from a master group of media instances dependent on the playing of previous media.

[0112] In certain exemplary embodiments, the plurality of selectable media is formed from media most recently played by the user during a predetermined period of time and / or from media most recently played by the user at a predetermined store, hi certain exemplary embodiments, the plurality of selectable media is formed from media stored in a recently played media list associated with the user.

[0113] Once songs are added to a playlist, the playlist may be played in its entirety or in part. For example, if the user has many credits, the playlist may be played in its entirety. However, if the user does not have many credits, the user may pay additional fees to purchase a sufficient number of credits to play the playlist in its entirety, or the songs may be played in part. In the latter case, the user may be prompted to select a subset of songs from the playlist to play, and songs from the playlist may be played in order until credits are used up. Alternatively, a prompt may be displayed at the appropriate time to prompt the user to insert additional fees to play the entire playlist, and the prompt may be removed from the display once sufficient fees have been inserted.

[0114] With respect to the fees charged to users for playback, in certain exemplary embodiments, registered and / or authenticated users may be offered "low-cost" playback. For example, users may be charged a fee for selecting songs that are not normally available on the jukebox (e.g., requiring download from an AV distribution network or other source). In certain exemplary embodiments, only certain preferred users are charged a reduced or minimum number of credits (e.g., only one credit), whatever the source of the song. In certain other exemplary embodiments, only preferred users are charged a minimum number of credits if the song was recently played by a particular user. Also, in other exemplary embodiments, only preferred users are charged a reduced or minimum number of credits if the song is present in a playlist associated with the user (e.g., a playlist created by the user, a playlist created by another user that the user has played in whole or in part, etc.). In this manner, in certain exemplary embodiments, it may be possible to reward authenticated users by reducing the number of credits charged for certain media associated with the user's playlist.

[0115] In certain exemplary embodiments, a system and / or method for playing media on a digital download jukebox is thus provided. A plurality of media is provided to the jukebox. An interface is provided to a user of the jukebox to allow the user to search for specific media to play on the jukebox. It is determined whether the media is immediately playable on the jukebox without any additional processing by the jukebox (e.g., without the need to further download or search for the media beyond what is typically done for playback or to perform a non-standard search). If the media is immediately playable, the user is charged a first predetermined number of credits and the media is added to a queue for play. If the media is not immediately playable, it is determined whether the user is an authenticated user. If the user is an authenticated user, a second predetermined number of credits is charged if the media is in a playlist associated with the user. Otherwise, a third predetermined number of credits is charged. The media is added to a queue for play. The second predetermined number of credits is less than the third predetermined number of credits and the third predetermined number of credits is greater than the first number of credits.

[0116] Subsequently, with regard to billing in certain exemplary embodiments, if the user is a registered user, the price for normal play may be the same as the price for premium songs that require download. In certain exemplary embodiments, playlists associated with a user are playlists previously created by the user, playlists containing songs recently played by the user, and / or playlists created by other users but partially played by the user.

[0117] Determining whether media is immediately playable on the jukebox without additional processing by the jukebox may include determining whether media is present in a storage area separate from the dedicated storage area of ​​the jukebox that contains the immediately playable media. The separate storage area may be a remote server, a portion of the dedicated storage area of ​​the jukebox, a separate storage area within the jukebox, etc. Determining whether media is immediately playable on the jukebox without additional processing by the jukebox may also, or in addition, include determining a user's search technique provided by the interface. For example, a premium may be charged for an "advanced search," such as a title search or an artist search. Of course, these examples are provided by way of example and not of limitation, and other search techniques described herein may be provided, with pricing differentiated based on each of user type and / or the presence of media in playlists associated with the user, and / or combinations thereof.

[0118] And, as described herein, such functionality may be enabled by any suitable combination of programmed logic elements (e.g., hardware, software, firmware, and / or any suitable combination thereof), and those execution instructions may be stored on any suitable computer-readable storage medium.

[0119] FIG. 21C illustratively illustrates available options for managing the buddy list in one exemplary embodiment. The user may keep track of buddies (e.g., friends, bar patrons, etc.). The system may utilize instant messaging standards such as, for example, AOL Instant Messenger, MSN Messenger, Yahoo! Messenger, ICQ, custom jukebox specific protocols, etc., to send and receive messages. The system preferably informs the user of buddy status (e.g., online, on break, busy, etc.). In step S2032, the user may create or edit an existing buddy list. The user may search for buddies, for example, by entering a buddy's name, email address, etc. Additionally, in step S2038, friends may be invited to join by issuing an invitation, preferably by email or SMS (Short Message Service) text message to a mobile phone.

[0120] Users may also view peers' music collections, playlists, picklists, etc., as shown in step S2034. Users may then enrich their own playlists and / or picklists based on what is popular among their friends. Users may also copy music from peers or send music to peers, preferably for a fee, as shown in step S2036. In a step not shown, users may also specify a particular song to play when a friend logs back into the jukebox, preferably for a fee. Other features suitable for communication between peers are described below with reference to FIG. 21D.

[0121] FIG. 21D illustrates illustrative options available for communicating with others in one exemplary embodiment. The system may preferably send email and SMS messages to cell phones. Of course, the system may communicate by using various communication protocols, such as, for example, using email and / or email-like messages accessible only by the MyTouchTunes system. Of course, the bar manager may also send messages (e.g., using email, SMS, etc.) to announce events, special events, etc. to others. In step S2042, the user may check their inbox. The user may receive messages, for example, from their friends (or associates), proprietors, and / or advertisers, etc. For example, associates may suggest songs or places to meet. In some exemplary embodiments, associates may receive instant messages to their cell phones announcing social gatherings, the location of a particular user in the bar, etc. Additionally, the user may leave others a message that appears the next time someone logs in. Proprietors may send messages to their patrons or others they wish to target to announce, for example, drink specials, upcoming special events, etc. Advertisers may provide special offers based on demographic information provided by the user. In step S2044, the user may send messages to others' email addresses, MyTouchTunes inboxes, cell phones, etc. Alternatively or in addition to step S2044, in step S2046, the user may disseminate messages to peers or groups of others, for example to announce an upcoming party for a particular group. This allows the exemplary system to learn about a network of friends using messages sent by the user. Additionally, the jukebox may have a direct interface to the above functionality, or the jukebox may have a wireless connection to the functionality for users who bring their wireless devices to the location (or within range) of the jukebox.Some or all of the functionality may be provided to a user remotely, for example by allowing the user to access the jukebox service via the Internet or other suitable communications network, for example, using a computer at the user's home. In certain exemplary embodiments, communications may be made to an individual user, to predefined groups of users (e.g., family, co-workers, teammates, friends, etc.), and custom messages may be created or more standard messages may be selected (e.g., "Meet us at Bar X," "What are you doing tonight?", etc.). Group and / or canned messages may be implemented and used regardless of whether the messages are sent via email, SMS, IM, etc.

[0122] Similarly, in accordance with certain exemplary embodiments, systems and methods are provided for establishing and managing connections of registered users. Registered users may seek to establish connections with other users or prospective contacts at the jukebox or remotely from the jukebox. In either case, the user may be prompted to log in. After logging in, the user may be prompted to enter information about the prospect. This may include, for example, an email address, a mobile phone number, an address, a jukebox-specific messaging service, and / or the like.

[0123] Once the information has been entered, a confirmation message may be sent (e.g., via an AV distribution network) to the prospective contact. The confirmation message may verify the registered user (e.g., by name, login name, picture, avatar, etc.) and / or provide the registered user with information about the prospective contact (e.g., phone number, email address, jukebox login name, etc.). The prospective contact may determine whether a connection between the two parties should be established, for example, by verifying that the prospective contact actually knows who the registered user is.

[0124] If a potential contact is not already a registered user of the jukebox service, the potential contact may request, and in some cases may be required, to become a registered user of the jukebox service itself.

[0125] After receiving the confirmation message, the prospective contact may choose whether or not to approve the registered user's connection. This may be done, for example, by sending a message containing an authorization code or by logging into a particular website or jukebox. For example, an email message, text message, or the like may be sent by the prospective contact as confirmation. The authorization code may be a specific alphanumeric code that uniquely identifies the registered user to the prospective contact, or may simply be the prospective contact's email address or mobile phone number (e.g., sending an SMS, email, phone, and / or other message with a blank, a "Yes" message, an alphanumeric authorization code, etc.). Additionally or additionally, the authorization code may be embedded in a hyperlink accessible by the prospective contact and / or may be accessible via a computer-based interface (e.g., website) or jukebox interface. In other exemplary embodiments, the prospective contact must log into the website or jukebox without using a pre-created hyperlink with an embedded authorization code.

[0126] Once the authorization code is sent by the prospective contact, the authorization code may be authenticated, for example, by a server on the AV distribution network. The authentication process may include determining whether the registered user is valid, determining whether the prospective contact is valid, etc. If authentication is successful, a connection may be established between the registered user and the prospective contact.

[0127] Once a connection between the two parties is established, they may communicate with each other via the jukebox and / or services associated with the jukebox, for example, they may send messages as described above, share credits, etc.

[0128] Each user may determine how and when communications are received. For example, a user may use an interface provided at the jukebox or remotely from the jukebox to restrict messages to a single communication medium. For example, a user may wish to receive messages only to a specific email address (even if other users have provided alternative email addresses). In such a case, messages may be forwarded to the specified email address. In other embodiments, a user may wish to not interact by SMS messages or to interact only by SMS messages. Additionally, a user may limit the number of times messages are received, for example, to avoid messages being received late at night or early in the morning (e.g., messages that may annoy other users). In such cases, messages may be queued at the jukebox or server for later transmission. A user may additionally specify that no connection is to be received unless specified in the access control list. Communications between connections may then be managed and / or routed to specify, for example, when, where, and from whom they are to be received. Registered users may then use the communications listings to communicate with their listed entities using a jukebox or a remote device that can access the jukebox network, for example by logging into the network using a personal computer or the like.

[0129] FIG. 21E illustrates exemplary options through which value-added content can be accessed in one exemplary embodiment. As shown in step S2052, a user may access an external website (e.g., a peer's) for many reasons. For example, an advertiser may place a banner ad related to a particular song or album selected to get the user to order related merchandise. An advertiser may use potentially ubiquitous (e.g., online, on the jukebox, etc.) profile information to send ads, emails, texts, etc. For example, a jukebox may be used as a "selector" to target (visibly or unvisibly) certain merchandise to individuals who spend more than a certain amount on the jukebox per year. A user may also access an external website to link to a particular band's website, to order a music, guitar, or bass "tabloid," to view lyrics, etc. Also, in step S2054, a user may follow a link to download / purchase the song and / or album from a third party provider such as iTunes or Amazon.com. In some exemplary embodiments, this step may also be linked from a "Manage Music" screen (step S2020), etc. Additionally, in step S2056, the user may order a custom CD, and preferably pay a fee to have a custom CD delivered. The user may base these orders on their playlists, picklists, buddy playlists, hot hits, etc., as described above.

[0130] While the exemplary MyTouchTunes system described above has been described with a broad concept of creating accounts available to compatible systems, other exemplary embodiments contemplate where accounts are created available to a smaller subset of jukeboxes, including, for example, a single jukebox operating in isolation. Additionally, a larger group may operate as if it were a single system in isolation, or alternatively may possess complete information on all user accounts / profiles, stores, etc.

[0131] FIG. 22 shows an exemplary screenshot of a login page according to one exemplary embodiment. A user may enter an email address in username area 2200 and password area 2202. For convenience, the user may select a common email domain from domain list 2204. In this embodiment, a potential email address and password are required, but in other embodiments, a username may be required, which need not be an email address. Similarly, a username and password may not be required, for example, in a home jukebox, and in further embodiments, only a username may be required. The user may use keyboard 2206 to enter the requested information. This may be accomplished using other input devices, such as, for example, a keyboard attached to a home computer. The login screen shown in FIG. 22 may be presented on an actual jukebox, a computer (e.g., via a web interface, custom software, etc.), a mobile device, etc.

[0132] Upon successful login, the user is preferably presented with a main menu. FIG. 23 is an exemplary screenshot illustrating the functionality available to an authorized user after login, according to one exemplary embodiment. A customized greeting (e.g., username) is displayed in area 2300. Playlists 2302, 2304, and 2306 are displayed by playlist name along with the number of credits required to play the entire playlist. For example, playlist 2302 requires 7 credits to play. Playlists are preferably public playlists that can be viewed by other users. However, playlists may be designated private playlists, such as playlist 2306. The user may create additional playlists by pressing playlist create button 2308 and may edit existing playlists by pressing playlist manage button 2310. The playlist manage function may allow the user to modify existing playlists, for example, by adding and / or deleting songs, deleting the playlist entirely, etc.

[0133] A user may manage buddies by adding buddies by pressing an add buddy button 2314. A user may also remove buddies by pressing a remove buddy button 2316. A user may also communicate by sending messages to buddies by pressing a send message button 2318. In some embodiments, this feature may send an SMS message, email, or message to a mobile device that appears the next time the recipient user logs in, etc. In other embodiments, a user may use this feature to, for example, send songs, donate credits, etc. Display area 2320 shows that the current user has received one message and that the sender has been confirmed. However, in other embodiments, other information may be displayed, a more complex inbox (e.g., with folders, forwarding, etc.) may be provided, etc. Credits display area 2322 displays the current status. In this embodiment, credits display area 2322 shows that the user has purchased 20 songs online and has enough money in the local jukebox terminal to play 5 more songs, for a total of 25 songs available for play.

[0134] Another aspect of the invention is described that relates to background music enhancement. The local server and TuneCentral features described herein open up a new world of background music on a jukebox. In fact, if there is information in the queue that the music is not paid for, the jukebox may play background music (ambient music) with the help of an auxiliary system (e.g., DMX or satellite radio) connected to the jukebox. Also, if the jukebox plays background music using its own music, the background music is limited to the songs playable on the jukebox, which is typically around 2000 songs. These songs are also available for selection by the jukebox patron. Conventional digital jukeboxes are typically connected to a remote network via the Internet to access a wide range of music. Therefore, these applications are not well suited to provide background music services other than the locally available music, since they require continuous downloading or streaming from a remote server for the background music.

[0135] However, an external server or a jukebox with a large music partition (such as TuneCentral described herein) may select background music to play from its large pool of songs, even if the background music to play is not playable through the standard interface. This allows for a huge range of music for background music using the jukebox. Background music selections may be created automatically by the jukebox, randomly, or using detailed algorithms that select music based on genre, theme, era, or other criteria. Background music lists may also be sent to the jukebox from a central server, programmed by a DJ or the like (background playlist). Since music copyrights may differ for songs available in single play mode and background music, in one embodiment of the invention, there is an indication of each song or group of songs (e.g., all from the ABC Records label) that allows the jukebox to differentiate between songs that may be played as background music (as opposed to playing on a regular jukebox) based on proper music copyright usage, which also allows for proper royalty accounting. In one embodiment of the invention, the jukebox provides detailed options to let the operator configure how the background music is played based on genres, themes, indicators (flags), such as Billboard Hits, Christmas music, playlists (e.g., DJ John - Summer 2005), etc. In another embodiment of the invention, similar to the bartender selecting a radio station prior to the background music, the operator configures the jukebox to let the bartender further configure a background music mode, for example, using a remote control device. This mode provides genre or theme based music or playlists to enhance the background music functionality. The operator may configure, for example, which genres, themes, or playlists are available to the bartender.Additionally, a remote control with programmable keys associated with appropriate software may be provided to allow the bartender (or others) to select (e.g., for a special area) a predefined background music playlist or TV audio input for special events, such as a football game in that area of ​​the bar, thereby allowing efficient occasional background music and other services to be provided with the jukebox.

[0136] Subsequently, "channels" for music may be provided, similar to background music services. Store management may select which channels to play. The channel list may be determined by the store and / or the content provider (e.g., jukebox provider). In certain exemplary embodiments, the channels may correspond to themes or genres of music offered by the jukebox (e.g., rap, rock, country, etc.). Additionally or alternatively, store management may group songs to create custom channels for a particular store or group of stores, and / or custom channels that can be shared among many potentially unrelated or unrelated jukeboxes (e.g., as a type of shared channel). For example, using this channel feature, thousands of songs offered on a jukebox may be played as play music in a coherently grouping. For example, a music channel (e.g., selected by an owner, manager, etc.) may be played for a predetermined time after the jukebox is no longer charged and / or after all songs in the queue have been played. The channel may be driven in this exemplary case substantially without direct user input, such that, for example, the switch from normal jukebox operation to background mode is substantially transparent to patrons and / or authorized users of the jukebox (e.g., manager, proprietor, etc.). Of course, an authorized user may switch the jukebox from normal operating mode to channel mode, switch the jukebox from channel mode to normal operating mode, control channel switching, select channels, etc.

[0137] This functionality provides a number of benefits. For example, no media royalty source is required to play the media provided to the jukebox. This reduces the need for, for example, satellite radio, broadcast radio, CD players, and / or other devices (e.g., in addition to or instead of the jukebox), some of which may require additional costs in terms of hardware and monthly fees. Rather, a jukebox channel may provide hundreds or thousands of media that are playable directly from the jukebox. In this manner, many different channels of background music may be provided to the jukebox using music stored on the jukebox and music available on the network. The available channels are selected by an authorized person, for example, using a remote control device provided by the jukebox. The various channels may be displayed on the jukebox upon request so that a channel may be selected from a list.

[0138] Furthermore, unlike traditional broadcast radio channels and enhanced satellite radio channels, jukebox customers may exercise control over the content of a particular channel by simply selecting a new channel. For example, an authorized user (e.g., an executive, manager, etc.) may use the jukebox remote control device to skip songs, play songs, remove songs from a channel, add songs to a channel, etc. Currently, this functionality is not possible in connection to broadcast or satellite radio channels. Similar to a rating system, the jukebox channel may selectively learn from this control action and adapt the channel, such as playing popular songs more frequently, skipping unpopular songs, etc.

[0139] Furthermore, jukebox channels do not have the same kind of physical problems associated with traditional broadcast and satellite radio. For example, satellite radio may be inoperable during inclement weather, whereas jukebox channels may function substantially independent of outside conditions. Similarly, jukebox channels do not have the same kind of geographic limitations associated with broadcast channel antennas, in that, for example, jukebox channels may be played wherever a jukebox is present. In fact, jukebox channels do not even require a persistent or stable Internet connection, although for certain exemplary embodiments where it is preferable to have streaming media, updateable channels, and the like, a persistent or stable Internet connection may be advantageously used.

[0140] Subsequently, certain exemplary embodiments provide a system and / or method for operating a digital download jukebox. A plurality of channels are defined, each of the channels having a plurality of media associated with the channel. A channel is selected from the plurality of channels at authorized users. One or more customers using the jukebox respond in a first mode, with at least some of the customers engaging in a use that includes adding media to a queue for play on the jukebox and playing the media in the queue. If the jukebox does not respond to the customer's request and / or if the jukebox does not play the media in the queue, the media in the channel is played in a second mode. The first mode is distinct from the second mode, which is not directly controlled by the customer of the jukebox. In certain exemplary embodiments, the second mode may be a background music mode (e.g., such that music is played at a lower volume).

[0141] In certain exemplary embodiments, media may be associated with channels by a user and / or according to a theme and / or genre (e.g., rap, rock, country, etc.) associated with each of the media.

[0142] The frequency of playback of media in a channel may be changed depending on one or more control codes from an authorized user, the control codes corresponding to at least one of the following events: Skip the media being played by a channel. · Replay the media being played by the channel or that has just been played by the channel. Remove media from a channel.

[0143] As described herein, any suitable combination of programmed logic circuitry (e.g., hardware, software, firmware, and / or combinations thereof) may be capable of performing such functions. Moreover, instructions for carrying out the same may be stored on any suitable computer-readable storage medium.

[0144] FIG. 24 is a flow chart showing an exemplary process for remotely accessing the system according to one exemplary embodiment. In step S2402, a user logs into the jukebox system from a device other than the jukebox installed locally at the store and / or bar. In an embodiment, the user accesses the system via a web browser to access an Internet portal. However, other mechanisms for accessing the system are possible, such as, for example, via a portable device (e.g., cell phone, PDA, etc.), a standalone application on a remote computer, a suitably configured jukebox, etc. Furthermore, the functionality and / or services provided by the system may depend on the mechanism and / or device by which the system is accessed. For example, some functionality may be available to an exemplary embodiment using a web browser on a personal computer that is not available on a cell phone, and vice versa. Keeping in line with this embodiment, but for non-limiting purposes only, an exemplary embodiment using a web browser on a personal computer may have access to any combination of functionality and / or services (e.g., downloading music, participating in forums, chat rooms, etc.), whereas an exemplary embodiment using a cell phone may only be able to download music and receive text messages. Of course, as various devices become more interconnected and more powerful, such distinctions may no longer hold.

[0145] In step S2404, the system determines whether the user is an existing user. Users not recognized by the system are preferably prompted to create an account, as described in step S2408. The user may be required to provide, for example, the user's name, age, email address, etc. The user may preferably be able to create a profile that includes, for example, the name and / or nickname, the user's age, the user's location, and an image associated with the user. These profiles may be viewable by other users of the system. In some exemplary embodiments, for example, the user may be required to register and / or create a profile before utilizing some features of the system. In other exemplary embodiments, the user may set the user's information, or portions thereof, to remain private. A non-limiting exemplary screenshot for editing account information is provided in FIG. 26C and an accompanying description thereof is provided below. After the user creates an account, in step S2410, a central account database is updated. In other exemplary embodiments, a central account database need not be maintained and the account information may be stored anywhere, such as, for example, on the jukebox, on the user's own personal computer, etc.

[0146] If the user is authenticated in step S2404, the user may select functions and / or services in step S2406, which are described in more detail in Figures 25 and 26A. In some exemplary embodiments, the user may access the system restricted by the services to which the user is a member. For example, in some exemplary embodiments, the user may have free and unlimited access to the online system from a personal computer, but must pay a fee to access the services via a PDA. Thus, in a step not shown, even if the user is authenticated as an existing user, if the user attempts to access the system in an unauthorized manner, the user will not be granted access to the system. In some exemplary embodiments, this function may deny unauthorized access by registered or unregistered users attempting to inappropriately access the system and / or the underlying code, music, etc. of the system.

[0147] FIG. 25 is a flow chart showing an illustrative process for selecting one or more of a non-limiting list of services and / or features in a system according to one exemplary embodiment. Other features and / or services added to and incorporated into the features and / or services described below are possible and contemplated herein. FIG. 25 begins with step S2406 described in FIG. 24. In one embodiment, the steps described below need not be selected in any particular order. For example, a user does not need to search for music before communicating with other users. In some exemplary embodiments, the steps described below may be performed alone or in combination. For example, a user may wish to search for music before communicating with other users.

[0148] In step S2502, the user may search for music. The user may specify search terms, such as, for example, artist, song, album, genre, etc., alone or in combination. An exemplary screenshot showing the search results is provided in FIG. 26E and described below. After searching for music, the user may, for example, add the located song to a playlist, purchase the song, or recommend the song to others. For example, a user may remember hearing a catchy song in a bar, but only remember that it was a reggae song somehow related to "Zion" from Damian Marley's latest album. Additionally, in step S2502, the user may search using the following parameters: Artist: Damian Marley Song: "Zion" Genre: Reggae After a search is performed, the user can select "Road to Zion" from the results list. After finding the song, the user can add the song to a playlist for convenience the next time they visit the bar, or recommend the song to a friend. The user can purchase the single and / or download a digital copy. Particularly daring users can order the entire album "Welcome to Jamrock."

[0149] In step S2504, a user may manage his / her playlists. An exemplary screenshot showing how a user manages playlists is provided in FIG. 26D and described below. Briefly, a user may, for example, create a new playlist, delete an existing playlist, and / or edit an existing playlist. In one embodiment, a user may share a playlist with, for example, friends or the general public, and a user may search for playlists available for sharing. A playlist preferably has a unique name (e.g., "Joe's Top Favorites," "Ghetto Groove," "Best Chillout Songs," etc.) and preferably has many songs associated with that name. A playlist may contain only one song. Additionally, in some embodiments, a user, a professional DJ, or others may create and sell playlists, and users may pay for and download such playlists through the system.

[0150] In step S2506, the user may purchase music. In one exemplary embodiment, the user may order a single song, multiple songs, an album, or multiple albums. In some exemplary embodiments, the user may have the order shipped, while in other exemplary embodiments, an authorized digital copy may be created. In other exemplary embodiments, music may be purchased and downloaded directly to a media playback device (e.g., a suitably configured PDA, cell phone, or the like).

[0151] In step S2508, the user may communicate with others via email and / or text messages. In step S2508, the user also preferably participates in online forums and chat rooms. Messages sent through this step may be delivered to a traditional inbox, a cell phone, and the like. Additionally, messages may appear in a jukebox, for example, when the receiving user first logs in, as messages are sent and / or received, etc. Online forums and chat rooms may use protocols such as, for example, newsgroups, Network News Transfer Protocol (NNTP), Usenet, Internet Relay Chat (IRC), and the like, or may use custom protocols.

[0152] From time to time, the proprietor or manager of the system may sponsor content, promotions, or giveaways. Users may participate in such activities through step S2510. For example, the proprietor may approve anyone who prints coupons to avoid paying a cover charge. In another example, a competition may be held to select the best playlist. These promotional examples are for illustration only, and other content, promotions, giveaways, or the like may be possible.

[0153] In step S2512, the user may edit a user profile. Step S2408 of FIG. 24 above and the description in FIG. 26 below provide additional details of the types of information preferably associated with a user profile. In step S2514, the user may log out of the system. In some exemplary embodiments, the user may be automatically logged out of the system after a predetermined period of inactivity.

[0154] 26A-26E, which provide example screenshots, are used for illustrative and descriptive purposes only. The particular fields, buttons, images, etc., and their locations are not limiting. To the contrary, FIGS. 26A-26E depict only one embodiment of the present invention. Other variations and combinations are possible, and these variations and combinations are contemplated herein. A user may navigate between the screens described below in numerous ways, and only one such implementation is indicated by the use of the term "press." For example, a user may navigate between screens using a mouse, keyboard, touch screen, stylus, etc. The user interface is preferably a sleek and simple user interface with a limited amount of advertising or other non-core material. Additionally, if advertisements, surveys, and the like are accessible via the user interface, they are preferably linked to jukebox functionality and / or the links are related to rewards. For example, an advertiser may reward a user who clicks on one of their advertisements with credits, free plays, participation in a contest, etc. Similar rewards may be offered to users for participating in surveys.

[0155] FIG. 26A is an exemplary screenshot showing the functionality before a user logs into the system according to one exemplary embodiment. A user logs into the system by entering a username and password in the username field 2600 and password field 2602, respectively, followed by pressing a login button 2604. A non-registered user may also create an account by pressing a register button 2606. Navigation buttons 2608 help the user quickly navigate the system. In this exemplary embodiment, the navigation buttons 2608 include a "home" button, an "about" button, a "FAQ" button, and a "jukebox search" button. The "home button" returns the user to an introductory screen. The "about" button preferably displays information about the system, including, for example, help documentation, terms and conditions, etc. The "FAQ" button is preferably customized to provide supplemental information to that provided by the "about" button and to provide information regarding the most frequently asked questions about the system and its associated services and features.

[0156] A "jukebox search" button preferably allows a user to search for stores using a jukebox. A user may search, for example, for stores near a given address in a particular city that the user may travel to, stores that offer special features (e.g., drink specials, guest DJs, etc.), stores that play the user's favorite music (a country music fan would be well served by a bar that allows line dancing, etc.), etc. A social network may be built based on zip codes, schools (e.g., high schools, colleges, universities, etc.), etc. In one embodiment, when a user searches for a particular store, the user may have custom information displayed (e.g., directions, custom maps, hours of operation, parking information, etc.). Since jukeboxes installed in many stores are preferably connected to the system, and since a user's playlist is preferably accessible by the system, the user may receive recommendations that match the user's tastes. For example, the system may suggest a particular bar to a user of a given age who lives in the same city and who likes a particular type of music. In certain exemplary embodiments, the jukebox may recommend it to users from a given connection. These suggested connections between customers (and, for example, potential "buddies") are preferably based on information that is known to the jukebox, but need not be known to other users. Such information may include, for example, frequent venues, musical tastes, age, etc. Thus, in certain exemplary embodiments, users may be connected based on where they are going, and not so much on where they are coming from.

[0157] Similarly, a jukebox location service may be provided, which may be present on the jukebox, via a web page, in the MyTouchTunesWeb and / or jukebox interface, etc. The jukebox location service may receive user input and search accordingly. For example, the user may specify an address or part thereof (e.g., city, state, and / or zip code), may search by name or keyword, or may inspect specially available jukeboxes. Matching stores may be prominently displayed. Additional information may be displayed for any store. Such additional information may include, for example, the store name and store address and / or any other details for the store. For example, the most frequently played songs may be displayed, but also certain promotional offers, current DJs, etc.

[0158] Additional search criteria may be entered initially or to reframe the search. Such additional search criteria may include the user's age, musical tastes, favorite themes (e.g., Irish bars, country line dancing, etc.), etc. The jukebox location service may also perform a basic search using only the criteria entered by the user and then highlight recommended businesses based on known information about the user, such as the additional search criteria described above.

[0159] FIG. 26F is an exemplary screenshot showing search results using the jukebox location service. In FIG. 26F, a search term may be entered in a search block 2601. The search may be limited to use exemplary search terms 2603a-d. An area map 2605 may be displayed with flagged or otherwise identified matching stores 2607. A user may select a flag. In this embodiment, if flag 2607' is selected, an information block 2609 containing information related to the selected store is displayed. As discussed above, the information block 2609 may show the above information related to the store or other information related to the store.

[0160] A user may enter search terms in search field 2610. A user may further limit a search by searching in only one of the categories listed in search parameters list 2612. The fields in search parameters 2612 are used for illustrative purposes only, and other fields may be present in addition to or instead of the listing, such as year, trend, etc. A user may search by pressing search button 2614. A user may search by filling in search field 2616 and selecting search parameters from the search parameters list in search parameters drop-down list 2618. Search results are displayed according to FIG. 26E and are described below.

[0161] An example, non-limiting list of genres is shown in genre list 2620. Genre list 2620 preferably includes other genres. In this embodiment, additional genres can be accessed by clicking a "More..." button in genre list 2620. By clicking on a genre, a user can receive content appropriate for that genre. For example, clicking on the "Alternative" genre can display, for example, a list of the most popular alternative albums and a list of forums where discussions of alternative music are heated.

[0162] The most popular albums list 2622 contains information about the most popular albums, displaying the album cover, the artist's name, and the name of the album. The most popular albums list 2622 can be generated by any means. For example, the most popular albums list 2622 can be based on system user settings, commercial data regarding album sales, album sales in a geographic segment, etc. The most popular albums list 2622 changes depending on the genre selected from the genre list 2620.

[0163] By selecting a communication means from communication means 2624, users can access content specific to their region. In this embodiment, users can communicate in groups and / or forums. The groups and / or forums may require registration to join and may be public or private. Groups may consist of users with common interests, nearby users, etc. For example, there may be a group for a so-called "roses dream of death" where users can decide on a meeting place, transportation method, etc. for an upcoming euthanasia tour. Forums work similarly, but are preferably more static and allow threaded messaging between users.

[0164] Breadcrumbs trail 2626 provides a convenient means of navigating throughout the system. Specifically, breadcrumbs trail 2626 allows a user to track the path of a page as it is accessed. Pressing on a particular portion of a breadcrumb in breadcrumb 2626 presents the user with a corresponding location.

[0165] Information area 2628 and information area 2630 may be customized to provide additional information to the user. In this embodiment, information area 2628 provides justification for using the feature (here, creating a custom playlist) and information area 2630 provides useful tips (here, on how to create a custom playlist). Information areas 2628 and 2630 vary depending on, for example, the user, the time of access, the number of times the user has accessed the page, etc. Note that information areas 2628 and 2630 may contain different information that is not related to the use of the system, such as advertisements, promotions, etc.

[0166] FIG. 26B is an example screenshot showing the functionality available to a user after logging into the system according to one embodiment. User information 2632 and user icon 2634 are displayed based on the user's profile information. In this embodiment, user information 2632 includes the user's name and location, and user icon 2634 is a solid rectangle. Additional and / or alternative information may be displayed, or only information provided by the user may be displayed. A user may edit their profile, including user information 2632 and user icon 2634, by pressing an edit profile button 2636. A user may log out of the system by pressing a log out button. In this embodiment, the user is automatically logged out after a period of inactivity.

[0167] The user playlists 2640 display playlists that the user has created and / or imported. If the user has not created or imported any playlists, the user playlists 2640 are empty. In this embodiment, each playlist is displayed with a unique name specified by the user. The user can expand one or more playlists in the user playlists 2640 to display songs associated with that playlist. In the example shown in FIG. 26B, the "Alternative" playlist is expanded, and four songs 2642 are displayed as being associated with the "Alternative" playlist. The user can expand multiple playlists and / or delete the lists after they are expanded.

[0168] The system displays at least one recommendation 2644, which may include album covers, song names, artist information, and associated keywords. The recommendations are preferably generated automatically and based on a variety of data, including, for example, the user's demographic data (e.g., age, gender, race, etc.), the number and type of songs in the user's playlist, songs the user has purchased through the system, popular songs, etc. The system preferably allows the user to quickly add the recommended songs to a playlist by pressing an add button 2646.

[0169] 26C is an example screenshot showing how a user can update their account information. A statistics box 2648 displays basic information that is publicly viewable. In this embodiment, this includes username, real name, gender, location, and age. However, other embodiments may require additional and / or alternative information. The user may also choose some information (e.g., real name, age, etc.) to remain private.

[0170] The username selected during initial account setup is displayed in username field 2670. After initial setup, it is preferred that the user not be able to change username field 2670 and that each username is unique. The user may enter an email address in email address field 2652. In one embodiment, the system will send important emails (e.g., time and status information, giveaway announcements, invoices, etc.) to this email address. A real name is specified in name field 2654. In this embodiment, name field 2654 is shown as a single field, however, multiple fields may accept the same information (e.g., first and last name fields, first name, middle name, last name fields, etc.). The user may select their gender from gender option 2656.

[0171] The store is specified in store field 2658. In this embodiment, store field 2658 is shown as a single field, but multiple fields may accept the same information (e.g., town and state fields; town, state, and zip code fields; town, prefecture, and country fields, etc.). The date of birth is specified in birth date field 2660. In this embodiment, birth date field 2660 is shown as three fields, but multiple fields in different orders may accept the same information or additional information (e.g., one field for month, day, and year; fields for just month and year; fields for month, day, and year, etc.).

[0172] The user may enter personal or other information in a free-form bio field 2662. The user may also specify a signature or tag line in a forum signature field 2662. The system automatically adds the contents of the forum signature field 2662 to the user's postings to the group and / or forum. The user may upload a photo or icon by entering the file location in photo field 2666. This photo is preferably displayed upon login and / or when the user posts a message to the group or forum.

[0173] In one embodiment, required fields may be indicated, for example, with an asterisk (*), highlighted, or otherwise designed. In another embodiment, the user may store additional purchase information, such as, for example, credit card information, billing and delivery addresses, etc. This information may be used, for example, to automatically debit the user when the user places an order or downloads a song, album, or other item. This allows the user to "play now and pay later" while using a jukebox at a bar and / or club, etc.

[0174] A playlist manager button 2668 allows quick access to a playlist manager form, which is described below in connection with FIGURE 26D. Delete and expand buttons 2670 allow the user to quickly modify the playlist information, which in this embodiment is displayed at the left-most edge of the display. Recommendations 2672 are preferably generated in the manner described above, and by clicking on the recommendations one or more times, the user can quickly and easily associate them with his or her playlists.

[0175] FIG. 26D is an example screenshot showing how a user can manage playlists. In this embodiment, the user's custom playlists are displayed horizontally (as playlist labels 2674) with each content displayed under the appropriate heading (as playlist contents 2676). Of course, other arrangements are possible. Each playlist has a unique description associated with it, and each entry in the playlist preferably displays the number of songs in the playlist, the names of the songs, and the artist. The user can edit the playlist by "dragging" and "dropping" songs in and / or out of the playlist. The user can use the search function to add songs. In some embodiments, when all songs are removed from a given playlist, the user is informed that the playlist is empty and asked if the playlist should be deleted.

[0176] A user can create a new playlist by pressing a create new playlist button 2678. The system preferably waits for the user to enter a unique name for the new playlist. The user can edit the playlist as described above. A user can share a playlist by pressing a share button 2680. The share button 2680 allows the user to designate the playlist as public so that other users can make their content available. The user can also drag and drop the selected playlist into categories, such as public, private, etc. Correspondingly, the user can search for playlists created by other users (such as playlists prepared by a DJ) and copy and / or import the playlist. The user can also delete a playlist by pressing a delete playlist button 2682 and selecting the playlist for deletion from the list of playlists 2684.

[0177] FIG. 26E is an example screenshot showing the results of a music search. In this embodiment, a potential user searches for "portis*," where the asterisk (*) represents a wildcard. Search results are grouped by artist (artist list 2686), track / song (track / song list 2688), and / or album (album list 2690). Grouped results have a rank 2692 associated with them, which may be based on, for example, the number of users of the artist / track / album included in a playlist, billboard (or other) chart, all-time sales, etc. Also, in one embodiment, the user may sort the results alphabetically by category or by rank for ease of result location. Due to limited user attention spans and limited display space, it is desirable to limit the search result output to a few results (at least five, but no more than ten), while a more button 2694 allows the user to browse an expanded list.

[0178] FIG. 27 illustrates an example of a system for downloading music to a mobile device. A user indicates an interest in downloading a song after logging into a jukebox 2703 via a mobile device 2702. Many types of mobile devices 2702 can communicate with the jukebox 2703 over many different communication networks. For example, a properly configured mobile phone can communicate over the data channels of a cellular network, a PDA can communicate over standard TCP / IP, and so on. The jukebox 2703 can communicate over a network 2706 with an interface to a music repository 2706. The music repository 2706 preferably contains a wide range of potential downloads. Some requests may require confirmation of the download, for example when multiple versions of a song exist (e.g., Van Morrison and Jimmy Buffett both have versions of "Brown Eyed Girl" and so on) or for verification purposes. After the music repository 2706 receives the request, it selects the appropriate song (or songs) and transmits them back to the portable device 2702 over the network 2704 .

[0179] Although not shown in FIG. 27, in other embodiments, the appropriate songs can be sent to other designated devices. For example, a user at a bar may hear a song and want it sent to a computer at home. A user in a car may want the song to be available the next time they visit a bar. The song is then downloaded to a remote jukebox, for example. In some embodiments, the appropriate songs 2708 are sent over different communication networks as needed. The user is charged according to billing information that the user has entered. For example, a designated credit card is charged each time a song is downloaded via the jukebox interface. In another example, the user can set up an account dedicated to a particular jukebox, for example, linked to a Pay-Pal account. In a related aspect, the user may use their mobile phone (or other suitable mobile device) to purchase media, and can register the jukebox by exchanging a code with the jukebox (e.g., via an SMS message). For example, the user first authenticates themselves with the jukebox (e.g., the user logs into the jukebox or logs in remotely via a mobile device). The user is prompted to enter the appropriate information, such as the user's mobile phone number (or email address, depending on the embodiment). An SMS (or similar, as appropriate) authorization message and / or code is sent to the user. The user enters the code at the jukebox to begin purchasing music, creating personal content, accessing features available to authorized users, etc. This means of communication in some embodiments allows the user to pre-authorize and / or pre-pay to purchase music remotely.

[0180] 28 is a flow chart showing an example of a process for acquiring music. In step S2802, a user listens to a song being played on the radio, for example at a bar or club. After listening to it, in step S2804, the user decides to purchase the song. However, the user may choose to download the song without listening to it, for example because a friend of the user recommended it, or because the user has downloaded all the songs of an artist.

[0181] In step S2806, a user logs into the jukebox system using a portable device, and in step S2808, the user selects a song to purchase. The use of a portable device allows for quick, convenient, and "impulse" purchasing. In some embodiments, the selection of a song to purchase can be automated, for example, by selecting a song currently playing at a given store, a song currently playing on a radio station, a song playing at a given store, etc. In step S2810, the user can specify purchase parameters, such as a payment method and a device to which the song will be downloaded. In step S2812, the song is delivered to the user via the jukebox interface. The song may be delivered to other devices, such as a jukebox, a portable media device, a laptop, a home computer, etc.

[0182] FIG. 29 is a block diagram of an improved downloading digital jukebox system with remote devices for accessing the jukebox from a venue. The jukebox 16 is installed in a venue, bar, etc. A user accesses the jukebox 16 via a user interface 24. However, the user may also access the jukebox 16 remotely. Accordingly, a number of portable devices 26a-26d are shown located in a venue. The portable devices 26a-26d may be laptops, PDAs, cell phones, and other personal devices, but may also be other suitably configured devices. Each of the portable devices 26a-26d includes a wireless transmitter 27a-27d, respectively. The portable devices 26a-26d effectively allow registered users to log into the jukebox system and access specific content, such as customized playlists, personalized screens, and messages from other authorized users. Any changes made through one of the portable devices 26a-26d (e.g., user settings, playlist settings, etc.) are preferably reflected on all of the portable devices 26a-26d. For example, if a user creates a new playlist on the jukebox, edits an existing playlist, changes a password, etc., through the user interface 24, the change is reflected on the user interfaces 24a-24f.

[0183] The portable devices 26a-26d can communicate over an external network to communicate with the jukebox 16 equipped with a communicator 25. The portable devices 26a-26d can communicate over a local area network (LAN), wireless Internet, Bluetooth®, or any other suitable communication network.

[0184] A centralized database of recognized user information is maintained and accessible by each jukebox device 16, 16a-f and remote devices 26a-d, although in some embodiments a local database of recognized user information is maintained at each device. The devices may communicate with each other over a communications network, such as the Internet, although other communications means are possible, such as wired communications relayed over a LAN or wireless communications.

[0185] 29A-29E illustrate additional non-limiting example configurations for remotely accessing a jukebox. Other variations and combinations of these example configurations are possible and are contemplated herein.

[0186] FIG. 29A is a block diagram of an improved downloading digital jukebox system with remote devices for accessing the jukebox from a store. In this embodiment, the jukebox 16 and a number of remote devices are installed in a store. The jukebox 16 includes an interface 24 through which a user of the jukebox can, for example, make selections, create a profile, edit a playlist, etc. The jukebox 16 also includes a wireless communication device 25. The remote devices 26a-26b can communicate with the jukebox 16 via respective wireless communication devices 27a-c. In this embodiment, the remote devices 27a-c are a laptop, a PDA, and a cell phone, respectively. Other remote devices can communicate with the jukebox 16. The remote devices in this system can communicate with the jukebox 16 from outside the store, the range of which depends on the hardware of the jukebox 16 and the remote devices 27a-c, and the protocol used for communication. Thus, by wireless communication, for example via an 802.11g connection, users may access the jukebox 16 from within the store, outside the store as defined in the table, and other areas immediately surrounding that area.

[0187] Remote devices 26a-c allow a user to remotely log into jukebox 16 without having to directly access jukebox 16 and user interface 24. Thus, a user can, for example, play songs, edit playlists, and perform other jukebox-related operations without directly using user interface 24. Remote devices 27a-c each have a user interface that may be the same as or different from user interface 24. User profile information may be stored locally on jukebox 16 or on a remote server (not shown) or remote device 27. Changes made by a remote device (e.g., to user profile information, playlist content, purchased media, etc.) are mirrored to jukebox 16, other associated remote devices, and / or other jukeboxes, etc.

[0188] FIG. 29B is a block diagram of an improved downloading digital jukebox system with remote devices for accessing the digital jukebox system from outside a store. In this embodiment, a jukebox 16 with a local server 22 and a user interface 24 is connected to a network 14. Unlike the remote devices 26a-26c in FIG. 29A that are directly connected to the jukebox 16, these remote devices 26a-26c are connected to the network 14. Thus, users can potentially log into the jukebox 16 over a wide range. For example, the remote devices 26a-26c can be connected to the jukebox 16 via a LAN, a wide area network (WAN), an Internet connection, etc. User profile information may be stored on the local server 22. Changes made by the remote devices (e.g., to user profile information, playlist content, purchased media, etc.) are reflected in the jukebox 16, other associated remote devices, and / or other jukeboxes, etc.

[0189] FIG. 29C is another block diagram of an improved downloading digital jukebox system with remote devices for accessing the digital jukebox system from outside a store. FIG. 29C is similar to FIG. 29B in that multiple remote devices 26a-26c are connected to the jukebox 16 via the network 14. However, FIG. 29C includes a database 29 connected to the network 14. The database 29 holds, for example, user profile information, definitions of user playlists, etc. This configuration is advantageous in some embodiments because multiple jukeboxes connected to the network 14 can all access the centralized database 29 without having to connect to each jukebox or each remote device, which may not always be in communication.

[0190] FIG. 29D is another block diagram of an improved downloading digital jukebox system including another downloading digital jukebox system accessing a first digital jukebox system from outside an establishment. In this embodiment, a jukebox 16a with a local server 22a and a user interface 24a is installed in a first establishment, and a jukebox 16b with a local server 22b and a user interface 24b is installed in a second establishment. The establishments may be different rooms in a bar or two separate buildings. Both jukeboxes 16a and 16b are connected via a network 14. User profile information is stored in one or both of the local servers 22a and 22b. In some embodiments, if the user profile information is stored in only one local server, a user logged into one jukebox can access information stored in the other local server. In other embodiments, if the user profile information is stored in both local servers, any changes made in one jukebox are reflected in the other. In other embodiments, the user's profile information is obtained from a first jukebox and stored in a second jukebox when the user accesses the second jukebox. These configurations have the advantage that the user's information is not distributed to areas where the user does not have access to the information. For example, a user traveling from Washington to Los Angeles can log into a jukebox in Los Angeles and access the user's information created in Washington. However, since the potential user does not log into a jukebox in Montreal, the jukebox will not necessarily have the user's information stored locally.

[0191] FIG. 29E is another block diagram of an improved downloading digital jukebox system including another downloading digital jukebox system accessing the first digital jukebox system from outside a store. FIG. 29E is similar to FIG. 29D in that jukebox 16a is connected to jukebox 16b via network 14. However, in FIG. 29E, a database 29 is included that is connected to network 14. Database 29 holds, for example, user profile information and user playlist definitions. This configuration is advantageous in some embodiments because multiple jukeboxes connected to network 14 can all access centralized database 29 without connecting to each jukebox or each remote device that may not always be in communication. Multiple jukeboxes are connected via network 14.

[0192] FIG. 30 is an example flow chart showing one way in which a user can change their status by becoming a "verified user." In step S3002, a potential user creates a jukebox account to become a registered user. As described above, a potential user may A registered user creates an account from the jukebox at the jukebox or by accessing the jukebox remotely, for example, using a personal computer, laptop, mobile device, etc. A potential user who inadvertently or unwittingly joins the verified users' pool may immediately want to become a verified user and create an account with little or no prior consideration. In step S3004, the registered user receives notifications of social gatherings, special events, etc. Such notifications may be sent via email or SMS text message, or may be by a message that is displayed when the registered user logs into the jukebox. In one embodiment, a registered user is notified of social gatherings only if they meet certain eligibility criteria. For example, all registered users who reside in Barrow, New York, will receive notifications of social gatherings in Manhattan, but registered users in Des Moines will not. As another example, a user determined to like spiritual music will not receive notifications of Go-Go get-togethers.

[0193] After the registered user receives notification about the social event, in step S3006, the registered user can attend the event. This step includes attending a bar, event, social event, etc. In step S3008, the registered user becomes a verified user. Alternatively, the registered user receives vouchers, codes, etc. after entering the jukebox (locally or remotely) to change his / her status to verified. In other embodiments, the registered user drops a business card, a sign-up list, or indicates that he / she has a changed status. Thus, in step S3010, the user has privileges granted, changed access rights, etc. For example, a verified user can access a group / discussion forum that is only for verified users. In one embodiment, a verified user can make unlimited posts. In another embodiment, a verified user can access special promotions that are not available to other users.

[0194] One such special promotion includes the ability to send a message (e.g., SMS message, email message, picture message, etc.) to a registered user's mobile phone. In one embodiment, a coupon for one or more free credits is sent to the registered user. The coupon may be sent in a variety of forms. For example, a simple message may be provided for presentation to an authority figure (e.g., bar manager or proprietor) at a given establishment. The coupon may include a special verification code, for example to mitigate the risk of the free credits being awarded in error. The verification code may be presented to the authority figure, but may also be entered directly into the jukebox. The code may be verified against a database of codes that may be on the jukebox or remote from the jukebox. The database may be updated after the coupon is read (e.g., to invalidate the validity of the coupon to prevent the same coupon from being used again). Alternatively, or in addition, the code may be generated according to a self-checking format, thereby avoiding the need to query a database (e.g., the code may encode the number of credits and / or additional information according to a predetermined format that may or may not be immediately discernible by a casual observer).

[0195] The verification code may include a store code indicating that the coupon is valid at a particular store or group of stores. One example is a coupon offered for play on all jukeboxes in all stores owned by one person. Similarly, the verification code may include a code indicating an expiration date, such as a number of days or an absolute date and / or time that the recipient of the coupon may use the coupon. For example, the code may only be valid within a week or only on certain days.

[0196] Alternatively or in addition to a simple message and / or verification code, the coupon may be provided in bar code readable format by the manager and / or at the jukebox using appropriate hardware. The coupon may be distributed as a text message, for example by regular mail or email. In some cases, depending on whether the coupon contains a bar code or other format, it may be necessary to print the coupon for collection at a store. In other cases, it may be necessary to simply bring the mobile device on which the coupon was received.

[0197] Thus, in one embodiment, a system and / or means is provided for distributing coupons to users of digital download jukeboxes. A verification code is generated. Associated with the verification code is a number of free credits for the user. Note that a particular number does not necessarily need to be included in the verification code. For example, the presence of the coupon itself may be valid for a predetermined number of credits (e.g., 1 credit, 5 credits, 10 credits, etc.). The verification code is included with the coupon. And, the verification code is transmitted to the user.

[0198] The verification code includes at least one store where the user may use the coupon and / or a time restriction during which the user may use the coupon. The verification code includes an encoded alphanumeric sequence and / or a bar code. The coupon function may be used as a coupon to provide discounts on food, beverages, and / or other products / services offered by the jukebox.

[0199] In one embodiment, a verification code is obtained from the coupon and the validity of the verification code is determined. If the verification code is valid, the user is provided with a number of credits according to the number of free credits associated with the verification code. The verification code is obtained by the jukebox via a barcode scanner, and / or the user must enter the verification code into the jukebox via a user interface provided on the jukebox. Alternatively or in addition, an authorized user of the jukebox (e.g., a manager, owner, etc.) may provide free credits to customers.

[0200] Here, a suitable combination of programmable circuitry (e.g., hardware, software, firmware, and / or any suitable combination thereof) enables these functions, and instructions for performing the same may be stored on any suitable computer-readable storage medium.

[0201] FIG. 31 is an example flow chart showing one way in which a registered user receives credits for referring potential users. In step S3102, the user logs into the jukebox (locally or remotely). In step S3104, the user specifies some contact information for the potential future user. Step S3104 is performed when a user creates a new account, when a registered user accesses a form, etc. The contact information is used to send, for example, email, text message, traditional mail, etc., as needed. In step S3106, the jukebox sends an invitation to the potential future user using the provided contact information. Finally, in step S3108, the referring user receives credits. In one embodiment, credits are awarded based on the number of referring users. In one embodiment, credits are awarded based on a set formula (e.g., 1 credit for every 5 users referred and / or registered), including bonuses (e.g., bonuses when 10, 25, and / or 50 referred users become registered users).

[0202] FIG. 32 is an example flow chart illustrating one method by which a registered user may receive credits for creating public playlists. In step S3202, a user logs into the jukebox, either locally or remotely. In step S3204, the user creates a public playlist. As described above, the user associates an instance of media with a playlist. It is desirable to provide a descriptive name for the overall playlist. The user may create a playlist using any of the methods described above. This may include, for example, drag and drop functionality, search functionality, etc. In some embodiments, a playlist may be required to be designated public.

[0203] In step 3206, as part of normal jukebox operation, users of the jukebox have access to public playlists and songs. The jukebox specifically monitors user interaction with accessed songs and playlists. In one embodiment, the jukebox maintains counts, percentages, or the like related to accessed songs and playlists. In step S3210, the jukebox rewards users based on other users' accesses. For example, the user may be rewarded if the user's playlist is accessed a majority of any playlist, if it is accessed more than a certain threshold number of times, if it is selected more than other playlists in a certain category, etc. In one embodiment, the user is rewarded based on the content of the playlist. For example, the user may be rewarded based on whether the user's playlist contains a certain number and / or percentage of the most popular songs, as determined by the jukebox. Users may also be rewarded in a variety of ways. For example, one obvious way to reward a user is to provide credits for additional plays on the jukebox. The user may be rewarded with promotions, giveaways, and the like. More generally, an authenticated user earns reward points that enable any activity related to the jukebox (e.g., on the actual jukebox, via a web interface). For example, an authenticated user may earn points each time a user logs in, sends a message, shares a playlist, and the like. The reward points may be redeemable, for example, for purchase plays on the jukebox. Alternatively, the points may be redeemed by the authenticated user for special merchandise to encourage further use of the jukebox.

[0204] Additionally, users may select an avatar to represent themselves on the jukebox and / or in any other jukebox-mediated environment. A user's avatar may be depicted graphically, for example, by photograph, video, text, or any other method that adequately identifies the user. The avatar may or may not physically resemble a registered user.

[0205] In one example, when a person operating a jukebox selects the local playlist option from the jukebox, the playlists of each registered user on the jukebox are made available. An example of this is shown in FIG. 33, which is an example of a screenshot of a "Local Playlist" screen where registered users are represented by avatars. Next to the registered user's name, nickname, or other identifying mark 3302a-e is the user's avatar 3304a-e. This allows the jukebox to further customization and personalization, for example by representing bar patrons that many customers know or recognize, and encourages less-frequented jukebox customers to become more active, such as by creating custom playlists. When a user selects a group of local playlists represented by an avatar associated with a registered user, the user's playlists are displayed. That is, the user operating the jukebox selects the personal playlist associated with the user represented by the avatar. Once selected, the contents of the playlist (eg, one or more songs) are displayed along with the user's avatar, the name of the playlist, and the number of plays required to play it.

[0206] When a playlist or a portion thereof is selected by the user for playback, a "now playing" screen is displayed, as shown in FIG. 34, which is an example of a screenshot of the "now playing" screen. The screen displays the avatar 3304a, the registered user's name 3402, the name of the playlist 3404, etc. Additionally, registered user activity, audio and / or video intros are played to introduce the songs and transitions between ending songs and / or playlists. For example, the avatars may themselves be animated. If the avatars are photographs, a slideshow may make the images appear to move. Or, by overlaying various images, the avatar's mouth may be opened to make it appear as if the avatar is speaking or singing. If the avatars are animated characters, the same or similar functionality may be achieved. For example, an avatar may sing and / or dance to music (e.g., an avatar may bob its head to heavy metal music or line dance to country music with other real or simulated avatars, either as programmed by a registered user or as automatically generated by the jukebox), using, for example, custom animation and inverse kinematics techniques. Other functionality may be achieved by optional avatar movements programmed into logic (e.g., a remote jukebox interface, which may comprise any suitable combination of processors, hardware, software, etc. accessible to the jukebox). In general, the avatar movements programmed into the logic may allow the avatar to react before, during, and after an instance of media is played.

[0207] Similar functionality is provided by allowing registered users to upload content (e.g., video and / or audio content) to the jukebox and / or the network the jukebox distributes, such as photos, audio files, videos, etc., which can be captured and stored at one jukebox and associated with the registered user at that jukebox, or stored centrally for availability at multiple jukeboxes.

[0208] A similar feature is provided in a networked jukebox environment so that registered users can access their avatars from anywhere. For example, this feature is useful when traveling, visiting home, at college, and / or other stores the user visits later. In this way, the avatars are intimate with other customers who once knew the registered user. It also helps registered users who want to be creative (e.g., make new friends) and still have access to the user's music library.

[0209] The avatars and the media presented by them are subject to local filters applied to the jukebox: if a store doesn't allow rap, for example, the playlist is filtered so that pre-recorded messages are edited for explicit language, inappropriate photos are replaced, and so on.

[0210] As discussed above with reference to the MyTouchTunes service, a properly configured jukebox encourages users to connect to a variety of virtual communities, including, for example, interest communities (e.g., those organized around a particular subject), fantasy communities (e.g., games, creative environments, etc.), and / or relationship communities (e.g., online meeting spaces). Thus, either directly or through an online portal, the jukebox may provide one or more electronic mailing lists, online chat rooms, bulletin boards, message boards, discussion groups, Internet forums, and the like, blogs, instant messaging services, podcasts, text messaging services, file sharing (e.g., P2P file sharing), multi-user dungeons (MUDs), etc. Connecting to or establishing new jukebox virtual communities can attract new customers and further increase the interest of existing customers. Increased profits can be realized in virtual communities by collecting information about members (and targeting advertisements and appropriate offers), inviting vendors to the community to attract members and encourage spending, attracting members to the community to collect member-based content, and / or facilitating user-to-user interactions that build user attachment to the community.

[0211] The avatars described above are used in connection with the virtual community via the jukebox. For example, the avatar is associated with every action the user takes in the community (e.g., writing a blog, posting to a bulletin board, sending a message, etc.). Furthermore, as users begin to create or share their own media, the avatars become more interesting. Users upload music (e.g., conforming to standard license agreements) with the avatar virtually "attached" to them or with the avatar associated with the media. The jukebox network can track music distribution to websites, P2P file sharing engines, and / or jukeboxes. Royalty is tracked and passed on to the user through the avatar. Furthermore, different fee / royalty structures are offered based on the type of user. For example, for independent artists, large fees and small royalties are not appropriate. Also, artists associated with major record labels can reduce such direct and indirect costs. It promotes control and the music is checked to ensure copyright is adhered to. This authentication process may be performed automatically (e.g., comparing a bank of known music, checking for the presence of digital watermarks, etc.) or manually (e.g., by an authorized user, customer, operator, employee of a centralized distribution network). When content is submitted and / or approval is granted, the avatar is an acceptable form of digital signature affixed to copyright and / or license agreements. The avatar may be displayed as album art, such as during actual playback of the tagged song.

[0212] In addition to the above-mentioned toolkits available to the operator, a configuration dashboard is also available to the operator, authorized user, and / or proprietor to administer, manage, update, and / or otherwise control the jukebox. An operator managing one or more jukeboxes can save time and / or money by remotely accessing diagnostic and / or management functions provided for the jukebox. In one embodiment, the operator can access the management and / or diagnostic modules of the dashboard using, for example, a computer, handheld device, or other suitable device capable of receiving notifications and / or checking the status of the jukebox through an owner's interface (e.g., web-based). Communication can be two-way, so that the operator can directly command and / or query the jukebox regarding management functions and / or alerts and / or notifications. The features described below may be used alone or in various combinations. This allows the operator, authorized user, and / or proprietor to focus on the jukeboxes that require their attention, thereby saving time and money, while also increasing the uptime, reliability, and overall appeal of the jukebox.

[0213] With respect to such functionality, each jukebox collects and / or monitors information that may be of interest to an operator, and potentially proactively transmits such information to the operator. Notification mechanisms automatically send messages (e.g., via email, SMS, or other suitable format) to the operator when certain thresholds are exceeded. These certain thresholds may be set by the operator, pre-defined, etc.

[0214] Diagnostics and / or alerts include, for example, bill rejection rates (e.g., using percentages and / or numbers), number of bills stacked, number of reboots, temperature (e.g., hard drive, CPU, system, enclosure, etc.), etc. Such alerts / notifications may also be set to be sent at predefined times. For example, a notification may be sent if the CPU temperature is above a threshold for a certain period of time, if the number of reboots during a certain period of time is above a threshold, etc.

[0215] These diagnostic techniques are available to operators located remotely from the jukebox as well as directly at the jukebox, and in one embodiment, a diagnostic module on a first jukebox is used to remotely check a diagnostic module on a second jukebox, where the second jukebox is located remotely from the first jukebox.

[0216] 35-37 are example screenshots showing how to configure diagnostic alerts. In particular, FIG. 35 is an example screenshot for configuring alert settings. In FIG. 35, the email address to which the alerts are sent is specified in block 3502. Weekly reports are specified by selecting a day from drop down box 3504, and daily reports are similarly specified by selecting a time from drop down box 3506. The bottom part of the example screen lists various tests and how often the emails are sent. For example, from drop down box 3508 one can specify whether a hard disk temperature alert is not sent, sent immediately, sent daily or weekly. Other alerts are sent at the same or different intervals, for example by setting drop down boxes 3510, 3512 (which are partially blocked by expanded drop down box 3508). Of course, other intervals could be specified, other tests could be monitored, and other addresses or notification methods (e.g. SMS message, instant message, etc.) could be used.

[0217] Figure 36 is an example screenshot for setting warning thresholds. The left side of Figure 36 shows the statistic to be monitored (e.g., building rejection rate, building stack fill rate, number of restarts, etc.) and the right side specifies the threshold. Thresholds are set using absolute numbers and / or percentages as appropriate. Other tests may be monitored and any appropriate thresholds may be specified. Also, not setting a threshold will avoid generating a warning for that test.

[0218] FIG. 37 is an example screenshot showing the status of various tests. In FIG. 37, the left side of the screen lists a test and the right side of the screen shows its status. Each test is conveniently categorized (e.g., temperature, bill collection, software operation, etc.). As shown in FIG. 37, the status may be indicated by color (e.g., green indicates no abnormalities or acceptable operation, yellow indicates some concern, red indicates a problem or imminent). Of course, other indications may be used in place of the color indication (e.g., a number or percentage system, etc.).

[0219] An improved scheduling module is also provided for the jukebox. This module allows the operator and / or other authorized users of the jukebox to schedule one-time and / or recurring events. For example, a bar owner can schedule morphs, music filters, and / or background music. The recurrence frequency of the events may be weekly, monthly, yearly, etc. For example, background music may be played during the meeting, music filters may be applied in the afternoon and early morning, and an unlimited playlist may be available in the evening. As another example, the jukebox may gradually change to accommodate the night, such as 80's music night, hip hop night, country line dancing night, disco night, etc. These advanced settings ultimately save time and improve convenience. The event scheduler includes monthly and / or daily appearances. The daily appearances are divided, for example, by hours. After a new event is added, the appearance is updated appropriately.

[0220] FIG. 38 is an example screenshot of a morphing function in conjunction with an improved scheduling module. In the morphing function, a jukebox changes from a predefined master jukebox (e.g., via input area 3802) to a jukebox (e.g., a jukebox previously defined by the proprietor, operator, etc., via input area 3804), or to a new custom list of music (e.g., via input area 3806). Notably, a snapshot is taken for each change of the jukebox, thereby preserving the relevant data (e.g., date, time, playlist). This expedites the process of changes and allows proprietors to "undo" changes (e.g., if they are unpopular or unsuccessful). The user can schedule the changes like any other event by selecting the "Schedule this setting" button 3808.

[0221] A "Schedule this setting" button 3808 can bring up a calendar scheduling component, like other event scheduling. Figure 39 is an example screenshot of a scheduling calendar. The scheduling calendar has a month view 3902 and a day view 3904. The day view 3904 is divided into 30 minute, hourly, etc. views showing other event schedules for each day.

[0222] Operators can set up sub-user accounts, which can have access to restricted storefronts.

[0223] Other features include improved store setup functionality.

[0224] As indicated above, it is desirable to further enhance the customer experience, for example, to create a sense of ownership and / or belonging to the community in which the entertainment system users participate. Thus, since the above and / or other configurations, features, and embodiments certainly have advantages and are a marked improvement over existing jukebox offerings, it is desirable to integrate and extend disparate configurations as a broader, holistic entertainment system. For example, it is desirable to utilize a widespread, but currently unconnected, jukebox, jukebox-specific services, advertising services, independent social networking services, and a collection of independently controlled client devices to provide an experience that allows seemingly disparate systems to be interconnected and deeply integrated with one another, thereby enabling a more complete and deep connection between entertainment system customers and other people and non-customers. This encourages the former group to use the entertainment system configuration and further encourages the latter group to start using the entertainment system configuration.

[0225] To this end, some embodiments relate to an entertainment system (which may be provided off-site) that provides an entertainment system relay service associated with a jukebox that is accessible from and / or off-site, and also provides advertising opportunities and engages social networking services among customers off-site. In some embodiments, an entertainment system at a store acts as and / or is connected to a jukebox. Additionally, in some embodiments, the entertainment system at a store is connected to one or more client devices, one or more displays, one or more bar-top or handheld gaming devices, etc.

[0226] Accordingly, certain embodiments relate to systems and / or techniques for integrating and enhancing portable entertainment systems, jukebox music systems, video systems, and client devices via an entertainment server. According to certain embodiments, the entertainment server develops and integrates with jukeboxes, game devices, and client devices to provide various entertainment, social, and sales services (e.g., outside the home). As described in more detail below, the entertainment server at a store can be controlled from a portable device to enjoy music, games, and / or videos on a jukebox, display, or other device at the store or on the device itself. The entertainment server at the store can be controlled from a portable device to realize these and / or other functions on a jukebox, display, or other device at one or more different stores. The entertainment server at a store is also used by customers. This allows messages sent to the social community to be relayed to the entertainment server, allowing customers to interact with other customers, or non-customers, on actual premises. Additionally, an entertainment server at a given store may be utilized by customers to interact with users at that store by sending messages that are displayed on displays, walls, screens, etc.

[0227] In addition to the control and messaging functions outlined above, as detailed below, an entertainment server at a store is utilized as part of an advertising platform. This constitutes a network of local devices and a back-end system, enabling advertising (e.g., local, national, or even highly contextual advertising) on ​​the jukebox and / or any secondary screens connected to the entertainment server. Additionally, products and / or services are purchased through the entertainment server (either as a result of the advertising or independent of it). For example, products and / or services are purchased from a customer's mobile device, with purchases relayed to local equipment. Commercial equipment connected to the entertainment server and part of a wider entertainment system is used to transmit content directly or indirectly to the mobile device for purchase. In-location servers, such as web servers, provide services directly or indirectly to the mobile devices. While some products and / or services are offered on a pay-per-play or one-time fee basis, commercial equipment that is connected to the entertainment server and is part of a broader entertainment system may provide free, promotional, advertising, solicitation, non-solicitation, and / or other content directly or indirectly to the mobile device.

[0228] FIG. 40A illustrates the major components of an entertainment system according to one embodiment. An entertainment server 4002 is located in a store 4000. The entertainment server 4002 in FIG. 40A is shown "with" a jukebox. In some embodiments, the entertainment server 4002 is provided within the jukebox housing. In some embodiments, the entertainment server 4002 runs on the same computer as the jukebox or on a different computer. Although a stylized jukebox is shown in FIG. 40A, the entertainment server 4002 may be provided in conjunction with jukebox music systems, such as a stand-alone jukebox, a wall-mount jukebox, a remote terminal, etc. Rather than as shown in FIG. 40A, one or more of the jukebox music systems described above may be provided in addition to the entertainment server 4002.

[0229] A wide variety of peripheral devices are connected to the entertainment server 4002. For example, any number of displays 4004 may be connected. Such displays 4004 may include video systems such as overhead displays, plasma or LCD televisions, LEDs, advertising displays, leader boards, IP TVs, network addressable displays, and the like. Countertops and / or mobile devices 4006 belonging to a store may also be connected to the entertainment server 4002. A wide variety of client devices 4008 may also be connected to the entertainment server 4002. Each client device may include any combination of WiFi, 3G, Bluetooth, and the like, such as, for example, mobile phones (iPhone, Blackberries, and the like), PDAs, laptops, and / or the like. Each of these configurations may be connected to the entertainment server 4002 by wired or wireless connections.

[0230] As in the above-described embodiment, the entertainment server with jukebox 4002 is connected to an entertainment system network 4010. As detailed above, the connection between the entertainment server with jukebox 4002 and the entertainment system network 4010 is convenient for use in media distribution, royalty and / or revenue accounting, equipment updates, collecting demographic data, advertising distribution, and the like. The entertainment system network 4010 includes a media database 4012 that contains media instances for playback on the jukebox, display 4004, countertop or handheld device 4006, and / or client equipment 4008. Such media instances may be pay-per-play songs, advertising content, downloadable or network games, and the like.

[0231] The entertainment system network 4010 includes interfaces to MyTouchTunes jukebox-related services and / or external social networking systems. That is, the entertainment system network 4010 includes a MyTouchTunes interface 4014 that allows a user to perform some or all of the functions described above and / or other functions, such as creating, managing, updating, and / or deleting playlists, contacting friends, and logging into the jukebox they manage, optionally with a customizable avatar. The entertainment system network 4010 also includes a social networking system interface 4016 that links with one or more external social networking systems 4018. For example, the social networking system interface 4016 links with Facebook®, Twitter®, MySpace®, and / or other social networking sites. More details about this connection and the functionality it enables are provided below.

[0232] As above, end user computers 4020 and / or client devices 4022 external to a store connect to the entertainment system network 4010 via the MyTouchTunes interface 4014. End user computers 4020 and / or client devices 4022 external to a store also connect to the social networking system 4018. Client devices 4008 at the store 4000 connect to the entertainment system network 4014 through the entertainment server 4002 or more directly through the MyTouchTunes interface 4014. Similarly, client devices 4008 at the store 4000 connect to the social networking system 4018 through the entertainment server 4002 or more directly through a connection of the social networking system 4018 itself.

[0233] As alluded to above, MyTouchTunes related services are made available to users via social networking sites. That is, the social networking system 4018 cannot directly communicate with the MyTouchTunes related services and / or the entertainment system network 4010, but as noted above, a social networking system interface 4016 is provided to the entertainment system network 4010. The social networking system 4018 itself is configured in connection with this social networking system interface 4016. Similarly, the social networking system interface 4016 is configured to "translate" or mediate data communications between the MyTouchTunes related services and the social networking system 4018. With such a link provided, users of the entertainment server 4002 can seamlessly connect to the social networking site and vice versa. This can promote a more integrated and cohesive product.

[0234] FIG. 40B illustrates a physical structure of an entertainment system according to one embodiment. As shown in FIG. 40B, the store 4100 includes a local content server 4102. The local content server includes a server with a network connection, a display for monitoring the server, a storage location, and wired computer equipment. The wired computer equipment is provided for controlling the local content server, management of the storage location, the store's network, and / or external connections, management of store-based services (e.g., advertising and / or other services), and / or the like. A wireless router 4104 is connected to the local content server 4102. The wireless router 4104 connects each of the set-top boxes 4112a-c to the displays 4110a-c through the store's network using WiFi devices (e.g., laptops, handhelds, iPods Touches, PDAs, Sony PSPs, Nintendo DS, some mobile devices, etc.). The wireless router 4104 also provides a connection to the Internet 4114. A wireless phone 4106 (e.g., a smart phone, Web-enabled phone and / or the like) is present in the store or can be connected to the network using a wireless router 4104 via 3G, Bluetooth, or other suitable connections if properly configured. The Internet 4114 is connected to a social network 4118 (e.g., Facebook, Twitter, MySpace, etc.) along with a media server 4116 associated with the jukebox, the latter also providing services related to MyTouchTunes.

[0235] Figure 40C shows the logical structure of an entertainment system according to one embodiment. The local server includes a web server, which is connected to an application server. Both the web server and the application server are connected to content (e.g., audio, video, web pages, and / or the like). The web server is connected to a content metadata server along with an IP TV server.

[0236] The local server 4200 is connected to other components in the system, for example, by a TCP / IP connection. For example, the local server 4200 is connected to the Internet 4202. In turn, the Internet 4202 provides a connection to a social network server 4204. The Internet 4202 also provides a connection to a 3G network 4210, for example, via a 3G packet switched server 4206 and a 3G wireless network server 4208.

[0237] Wireless and / or wired devices 4212 (including web browsers) are connected to the local server 4200 via TCP / IP connections. Similarly, digital signage set-top boxes 4216 (including web browsers, flash players, video / audio players, 2D / 3D display applications, etc.) are connected to the local server 4200 via TCP / IP connections. Web-enabled phones and / or other devices 4214 (including web browsers) are connected to the local server 4200 via WiFi or other wireless connections (e.g., 3G, Bluetooth, etc.).

[0238] Social networking sites offer a wide variety of popular features to a wide range of users. Linking a jukebox to these sites and systems is desirable for the jukebox owner / operator because of the potential increase in exposure of services and advertisements, as well as the potential increase in overall network usage. In other words, advertisements are exposed to social networking users, and media and / or other products and services are sold through an additional sales channel, namely the social networking system. Linking a social networking site to a jukebox is also desirable for the operator or moderator of the social networking site for the same reasons. In fact, usage and advertising exposure increases as more and different types of devices are used to access the site from more and different outlets (e.g., if the jukebox acts as a connectivity "hotspot" as described below).

[0239] An example of the functionality of the MyTouchTunes service has been provided above and will not be repeated in detail, but it is worth mentioning that some or all of the following MyTouchTunes services or features may be available via a social networking site that utilizes the overall entertainment system architecture of an embodiment: (1) Adding Media to a Library: A user can download media to a "personal" library on a device. Alternatively or in addition, a user can "download" media to a centrally accessible storage location, where such "downloading" includes copying or simply providing access to multiple outlets from the centralized media database 4012. Alternatively or in addition, a user can "upload" media to a centrally accessible storage location, such as the media database 4012. Such uploaded media can be made available to other users or can remain private.

[0240] (2) Share Media with Friends: A user can share media with friends in the same manner as described above, i.e., the user uploads the media to a "personal" library on some device. Alternatively or in addition, the user "uploads" the media to a centrally accessible storage location, such as the media database 4012. Uploaded media can be made available to all other users, to a restricted set of users, or can remain private.

[0241] (3) Update / Manage Playlists: Users can update and / or manage personal or shared playlists. Alternatively or in addition, users can update and / or manage playlists that they have collaborated on with friends.

[0242] (4) Search by artist, album, song, theme, genre, playlist, or other: A user may search the centralized media database 4012 or a private collection using some or all of the above and / or other search criteria.

[0243] (5) Listen to a song or song sample: A user may listen to a song or song sample from the centralized media database 4012 or from a private collection.

[0244] (6) Track Stores Visited: Users may receive information pertaining to stores they visit, including, for example, the name of the store, the store's address, directions from the store, directions to the store, promotions associated with the store, information about the store, statistics about the visit (e.g., how many times a user visited, how long they stayed, what songs they played, friends they made, etc.), and / or the like.

[0245] (7) Messages with / around friends: Users can send messages to friends. Such messages are shared in some or all of the following channels: social networking sites, jukeboxes, overhead displays in a store, email, SMS messages, picture messages, etc. Thus, messages may be private or public, and they may be sent to one or more recipients. Messages may be sent immediately, with a delay, or following the occurrence of a particular event (e.g., a birthday, a special event, the selection of a particular song, etc.).

[0246] (8) Manage your overall account and services for social networking sites and / or MyTouchTunes features, including updating your personal information and / or log-in information, billing information, contact information, etc.

[0247] (9) Programming Events: Users can send event invitations, reply confirmations for such events, control changes to jukeboxes or other appropriately configured playback devices at the event location, and the like.

[0248] (10) Link a Playlist to an Event: Similar to above, the user can specify a playlist for an event.

[0249] As seen, some features are accessed and / or replicated through social networking sites. An advantage is that users can use either or both their social networking contacts and / or MyTouchTunes contacts in conjunction with these and / or other features, thus reaching a broad potential audience even when the user is only present in one but not both. And the user reaches this broad potential audience using a comfortable and familiar system that includes all of the above. This capability allows other users who do not use the MyTouchTunes interface, which employs a non-jukebox-related interface, to have a real impact on the integrated entertainment system.

[0250] Other features in other embodiments include the entertainment server 4002 acting as a gateway for the client devices 4008. That is, in one embodiment, the entertainment server 4002 allows the client devices 4008 to access the entertainment system network 4010, the social networking system 4018, and / or other networks (e.g., the Internet). Thus, the entertainment server 4002 provides the client devices 4008 with access to websites by operating as a "hotspot" for WiFi devices, Bluetooth devices, 3G devices, etc., at or near a store. For example, a restricted or unrestricted WiFi network is provided by the entertainment server 4002, with the jukebox acting as a hotspot or web server for the WiFi-enabled devices. The service may be offered as paid, free, free for restricted users, free for users who accept advertisements, free for users who purchase some songs, etc. In one example of a 3G cellular network, a unique ID (i.e., a jukebox ID) allows the user to identify which jukebox they are interacting with.

[0251] In general, this approach allows content selection and purchasing or selection via a mobile device. In contrast to existing applications where music is played on a playback device (e.g., iPhone®, iPod® Touch, laptop, etc.), the web selection technique of one embodiment also allows pay-per-play on a different device (e.g., commercial installation). This makes the playback device essentially a remote control for the jukebox. In other words, in one embodiment, the device the user controls (often the playback device itself) becomes the entry point for the entire entertainment system, as well as potentially a separate social networking system.

[0252] 41A-41D show exemplary screens for a client device to log into an entertainment server in one embodiment. The login techniques shown and described with reference to FIGS. 41A-41D can be used for WiFi login and / or login to other systems. FIG. 41A shows a screen that is displayed to a user when the user opens a mobile web browser on the client device and / or navigates to the appropriate page. In one embodiment, the user can use a "Super Search" feature to search for songs by pressing button 4101 without logging in. Alternatively, the user may not be able to actually play songs without logging in. In any case, pressing login button 4103 in FIG. 41A transitions the user to a login screen, as shown by way of example in FIG. 41B. In FIG. 41B, a username field 4105 and a password field 4107 are shown. As shown in FIG. 41C, the user enters a username and password and presses login button 4109 to log in. Note that for protection, the password is hidden. As shown in Figure 41D, once a user logs in, a welcome message 4111 is displayed that identifies the user by username. The welcome message 4111 is followed by a MyTouchTunes menu. The user can search for songs using buttons 4113 and / or access playlists 4115. The number of credits is presented to the user in an available credits area 4117. The user can log out at any time by pressing the log out button.

[0253] These features operate in the same way as they would if they were displayed on an actual jukebox. Any or all of the above and / or other features available on the jukebox, the MyTouchTunes portal, and / or the connected social networking sites are made accessible via the client device. Note that the interfaces of the features may vary depending, for example, on the device being used to access them. What may be appropriate for a home computer with a large display may not be appropriate for a mobile phone with a very small display. Similarly, what may be appropriate for a bar may not be appropriate for all home users. To illustrate some of the differences, example screens of some of the features for the client device are shown below for illustration. The example screens for the client device are contrasted with the example screens shown above for use on a home computer and / or for use on a jukebox. It should be understood that all example screens are shown for illustration purposes and are not intended to be limiting.

[0254] 42A-42B are example screenshots showing how a user can log into a wireless network. When the user is in wireless range, it appears in the list of networks detected by the local network 4201 (simply put). By selecting this option, the user can connect to the network. A password may be required, may be provided by the store, may be tied to the user's account, etc. In some embodiments, it may be mandatory that either a username or password is not provided, in which case the entertainment server is configured to authenticate the user with a unique string possessed by the client device used to log in. For example, the entertainment server may be configured to authenticate the user with a mobile device's phone number, a pre-stored cookie, or data carried in a packet, etc.

[0255] In one embodiment, the credits are transmitted to a client device. Use cases for such transmissions are detailed below. In general, however, the payment is received by a first payment receiving means (e.g., a coin or bill collector, a credit card verification form), such as a jukebox, a handheld game machine, location staff, a point of sale system, or a web service. The first payment receiving means receives the payment and holds the payment on trust. As a second step, the payment is transmitted to the user. This is done by transmitting an indication as a number of credits directly to one or more of (1) a portable device, such as a mobile phone, smartphone, media player, handheld game console (PSP, Nintendo DS), or other portable computer, or PDA, or web-enabled appliance, (2) a user account, such as a MyTouchTunes login, or other unique identifier, that uniquely identifies the customer, and (3) a commercial device for immediate consumption. The representation of the payment is encrypted and / or otherwise protected to reduce the risk of unverified tampering with the amount. More specifically, some or all of the payment methods may be made available to users to facilitate the collection of payments by merchants. (1) Payments are accepted from business equipment and transmitted to a user account or mobile device.

[0256] (2) Payments are accepted through the website and transmitted to a user account or mobile device.

[0257] (3) Payments are accepted from the SMS payment service and transmitted to a user account or mobile device.

[0258] (4) Payment is accepted from the coupon and transferred to a user account or mobile device.

[0259] (5) A payment is previously accepted from a user account or mobile device and transmitted to a second user account or second mobile device.

[0260] (6) Payments are accepted by store staff members and transmitted directly to a user account, mobile device, or business equipment; and / or (7) The payment is assigned to a customer invoice, such as through point of sale integration, or is otherwise further processed and transmitted directly to a user account, mobile device, or business device.

[0261] In some embodiments, the above-mentioned examples of techniques may be implemented in various combinations and sub-combinations as appropriate for receiving a payment. For example, in a first embodiment, a user goes to a jukebox, inserts a payment, selects a transmit button on the mobile device and / or jukebox, and enters a verification code on the jukebox and / or the device to transmit credits. In a second embodiment, a user authorizes automatic deductions from a registered account, for example, using a pre-authorized credit, debit card, or other payment instrument. In a third embodiment, credits are purchased or redeemed on the mobile device by entering a coupon code that was previously purchased or awarded, for example, at a store, on the web or a social networking site, as a promotion, etc. With regard to this last example, promotional credits or monetary value may be transferred to a user account or mobile device by allowing a coupon ID to be entered into the entertainment system at one access point, or by automatically allocating promotional credits or monetary value at a qualified event.

[0262] Qualifying events may include, for example, detecting a new mobile device at the store, a new user subscription or sign-up for the MyTouchTunes service and / or a social networking site, a specially designed event (e.g., Get 2 Free Plays on St. Patrick's Day, Get 5 Free Plays on a Regular Night Out, etc.), a customer becoming a frequent user of the jukebox or other related systems (e.g., playing more than a predetermined number of songs during a certain time interval or total time, purchasing a certain amount of drinks or other goods and services, etc.), and / or other circumstances. Flowcharts illustrating these and / or other example techniques are provided below.

[0263] 43A-43D are explanatory flow charts showing an example of a process for accepting a payment from a user in one embodiment. The flow charts include screen examples on the client device and / or the jukebox as necessary. It should be understood that both the process and the screen examples are shown for illustrative purposes and not limiting. In any case, FIG. 43A shows a first credit transfer flow according to an embodiment. In step S4302, from the user's personal device or mobile device, the user presses an "add credits" button. The number of credits is displayed in the user's reference on the device. In step S4304, a prompting message is displayed on the device. The prompting message briefly indicates the steps the user will take or must take to transfer credits to the device. The number of credits is redisplayed in the user's reference on the device. In step S4306, the user makes a payment to a network device equipped with an appropriate payment acceptance means, such as a jukebox. In step S4308, the network device displays a message confirming that the payment has been accepted, or sends the message to another display or the device (e.g., a display connected to it, or the device itself). In step S4310, the user presses a button on the initializing device to initiate the payment confirmation and verification process. In step S4312, the network device for which the payment is being escrowed (in this case the jukebox) displays a message containing an activation code. The activation code may be a simple alphanumeric code. The alphanumeric code is randomly generated (created) according to predefined rules. Alternatively, the code may be an error checking code built into the device, or the like. After the message is displayed, in step S4314, the user types the activation code into the appropriate entry field on the initializing device. If the device does not display a transfer code, the user indicates the same on the device.That is, store staff may assist the user, re-insert money, instructions may be sent to the appropriate device to re-display the activation code, or other action may be taken. In any case, once the code is entered, the transfer credits button is pressed in step S4316. In step S4318, the code is verified. If the code is valid, credits are transferred from the payment device to the initializing device. If the code is invalid, the user is notified of the invalidity. The number of credits transferred and the updated number of credits are displayed to the user.

[0264] FIG. 43B is an example of a payment device initiating a credit transfer according to one embodiment. In step S4320, a user deposits money into a jukebox or other network payment device. In step S4322, a message is displayed on the jukebox or other network payment device, prompting the user to select whether to transfer credit to the device and / or to use credit on the jukebox or other network payment device. In step S4324, the user presses a button to initiate a credit transfer communication, which in the example of FIG. 43B includes transferring funds to a portable device. In step S4326, instructions are displayed on the jukebox or other network payment device, which in the example of FIG. 43B instruct the user to press an add credit button on the portable device. In step S4328, the user does so and in step S4330 enters the provided code on the portable device. In step S4332, the transfer credit button is pressed. In step S4334, the code is verified as described above. If the code is valid, the credits are transferred from the payment device to the initialization device. If the code is invalid, the user is notified of the invalidity. The number of credits transferred and the updated number of credits are displayed to the user.

[0265] FIG. 43C is an example of another credit transfer according to an embodiment. In step S4336, the user presses a button from the payment device and / or jukebox or other network device to initiate a payment communication. In step S4338, the user is prompted to insert money and / or a credit card and enter a capture code. In the example of FIG. 43C, in step S4340, the user makes a payment to the jukebox or other network device. In step S4342, instructions are displayed on the jukebox or other network payment device. In the example of FIG. 43C, the instructions tell the user to press an add credit button on the portable device. In step S4344, the user does so and in step S4346 enters the provided code on the portable device. In step S4348, a transfer credit button is pressed. The code is verified in step S4350 as described above. If the code is valid, credit is transferred from the payment device to the initialization device. If the code is invalid, the user is notified of the invalidity. The number of credits transferred and the updated number of credits are displayed to the user.

[0266] FIG. 43D is yet another example of credit transfer according to an embodiment. In the example of FIG. 43D, credit is transferred when a coupon is acquired on a mobile device. In step S4352, from a personal or mobile device, the user presses a "redeem coupon" button. In step S4354, the user enters an acquisition code and / or a coupon code and / or enters or scans a barcode value. In step S4356, the user presses a "redeem code" button. In step S4360, the validity of the code and / or its associated value units and / or the amount of the code is verified, for example, by a database of accepted codes. If the code is determined to be valid, an acknowledgement is sent to the mobile device and the associated code is flagged as used or unavailable and / or deleted from the coupon validation database. In step S4362, upon receiving approval from the verification data, credits and / or equivalent value units and / or amounts are made available to the device.

[0267] In some embodiments, in the context of transferring credits, the user may also specify the number of credits to be used on the portable device and the number of credits to be used on the jukebox or network appliance. Additionally, in some embodiments, in the context of transferring credits, the user may also authorize a credit card, debit card, or other account or payment instrument that will be automatically charged (e.g., on every play) when the user has used all of the available credits.

[0268] As indicated above, the client device is used to control the entire entertainment system and / or access features such as the MyTouchTunes service and social networking sites. FIGS. 44A-44F are example screenshots illustrating searching, selecting, and playing music using an interface provided on a client device according to one embodiment. FIG. 44A is an example of a "main page" where a user controls and / or otherwise interacts with the entertainment system, the MyTouchTunes service, and / or the social networking site. This allows a user to initiate a search using "SuperSearch" button 4402, edit playlists using "myPlaylists" button 4404, or add credits using button 4406. Area 4408 may inform the user of the number of credits available.

[0269] When a user initiates a search, the user selects a search method. The screen of FIG. 44B allows the user to search by artist name by pressing button 4410, by album name by pressing button 4412, or by song title by pressing button 4414. Once the user selects a search method, a search screen similar to the screen shown in FIG. 44C is displayed. In the example of FIG. 44C, the user is using virtual keyboard 4420 to enter the name of a song in entry field 4416. When searching, an "auto-complete" feature displays possible search results while the user types into the search criteria. The results of the search are displayed in results area 4418. The list is updated as the user types or after the user indicates completion of the text entry.

[0270] FIG. 44D shows results for a search for the song "Hotel." The song title, artist name, album name, album art, and / or other information are displayed in the expanded results area 4418. When the user makes a selection from one of the search results shown in the expanded results area 4418, details of the song are displayed in a screen similar to the example of FIG. 44E. Details of the selected song, such as the above and / or other details, are displayed in the information area 4420. For the user's convenience when deciding whether to play the song, the number of credits is displayed. A play button 4422 allows the user to add the song to the queue, or, for premium, a play now button 4424 allows the user to move the song to the top of the queue. The queue details have been described above and will not be repeated here. When the play button 4422 or the play now button 4424 is pressed, the song is placed in the play queue, if necessary, assuming the user has sufficient credits. The user is returned to the "main screen." However, a confirmation message may be displayed in status area 4426 (in this case, a message indicating that the queue was successful).

[0271] Other features of the MyTouchTunes service, jukebox related services, and / or social networking services may desirably be accessible in these and / or similar ways. Depending on the device used to access and / or control the system, a simplified and / or "lite" interface may be provided. Such a lite interface may be used to augment ordering of products and / or services at or related to a store, content, etc. For example, some embodiments may be used to purchase or rent content (e.g., songs or other media), change the state of the system, e.g., by changing the order of the play queue (by paying a premium fee to play songs out of order), vote for the music to be played next, vote for the best staff, etc., purchase merchandise (specific to that store, songs played by that artist, etc.), order food and drinks, purchase products and services at that store, order a taxi ride, or purchase other products and services, etc.

[0272] In some situations, it is desirable to record events that have taken place at a store. This information, along with other content, may be of interest to customers who are in the store, customers passing by or considering visiting the store, friends who cannot make it to the store, etc. Thus, one embodiment manages a database of events and / or other information related to exactly what is going on at the store. This information may be managed in a database at the store, a centralized entertainment system network, a social networking server, etc. In other words, a feed of information is maintained locally or remotely from the store and distributed to interested subscribers, readers, or customers. In one embodiment, the information is managed and aggregated to provide a "feed" of information to the store and / or an existing social networking infrastructure. That is, in one embodiment, the feed of information is transmitted to a "wall" of a social networking site and / or displays at the store.

[0273] Information feeds are distributed by pulling data from or pushing data to the appropriate stores. More specifically, in some embodiments, the feeds are enabled by reading from a web service, receiving Resource Description Framework (RDF) Site Summary (RSS) streams, and / or displaying publicly viewable "messages" on one or both of (1) one or more displays in a given store and / or (2) external screens. Connections are provided directly from a processing server in a given store or through a centralized entertainment system network. Various network technologies, such as, for example, IP TV, Connec-TT®, and / or other push, pull, broadcast, subscription, and / or other technologies, may be used alone or in various combinations to accomplish these and / or other objectives.

[0274] A wide variety of information is delivered to the store's displays and / or social networking site walls, including, for example, information about the songs sung at the store, including information about the song (e.g., title, artist, duration, etc.), the name and / or avatar of the person who sang the song (e.g., at an event where the customer who sang the song was a registered user), the playlist in which the song was played (e.g., creator, playlist length, playlist position, etc.), and / or other similar information.

[0275] Messages exchanged through the system are distributed on the store's displays and / or on the walls of social networking sites. For example, user-to-user messages may be displayed, distributed to everyone in the store (e.g., not to one person in particular), etc. Thus, a back and forth dialogue is displayed, along with additional content attached, e.g., pictures, videos, music, etc. Messages designated "private" or that have not been made "public" will not, of course, be displayed in this way.

[0276] The displayed information and / or events occurring at the store automatically trigger an authorized user activation, a special event. For example, keywords included in the song selection and / or message are removed. Based on appropriate detection, data is delivered spontaneously in the delivery of real-time dynamic information to the customer. This customer generated information can be content from the artist, the label, or other people. For example, based on detection of a song or keywords related to the song, one or more factoids about the song selection are presented. The facts are displayed and / or a trivia game is played (e.g., via the client device, countertop, or handheld gaming device). In another example, an artist can issue a special message, such as "Thank you for listening to my song at XYZ Bar." The special message is included in the feed and / or played for the user at the store. In yet another example, information about new CD releases, upcoming appearances, concerts, etc. is provided as part of the feed.

[0277] Advertisers also benefit from the automated delivery of the feed, for example, by interest in the song being played and / or keywords. In general, based on receipt of the message, the advertiser can contextually expose specific ads to the customer on the main screen or any external screen based on the keyword search, the song being played, the artist of the song being played, or the mood entered. Advertisements may be displayed based on content suggested and / or paid for by the advertiser. For example, an advertiser may determine that the question "Joe, do you want a beer?" contains the word "beer" and, in response, show an advertisement for a certain alcoholic beverage and / or a drink special at the bar. Similarly, an advertiser may detect that a certain song being played is being used as a "jingle" and decide to place an advertisement.

[0278] Typically, an advertisement database is maintained at the store level and / or at the centralized entertainment system network level. The advertisement database provides a mapping between specific advertisements that are placed when keywords are detected, songs are played, etc. When there are conflicting or overlapping entries, priority rules are applied. In one example, priority is given to advertisers who have paid more. In another, advertisements are rotated. In yet another, the number of times an advertisement appears is proportional to the amount spent by competing advertisers. Of course, other priority rules for resolving the conflicts may be implemented.

[0279] Backend revenue sharing is agreed upon for displaying the advertisements. See, for example, U.S. patent application Ser. No. 12 / 222,785, the entire contents of which are incorporated herein by reference. Ad servers and video servers are disclosed, for example, in U.S. patent application Ser. Nos. 12 / 076,761 and 12 / 318,864, the entire contents of which are incorporated herein by reference.

[0280] Customers can also program the system to automatically leave messages in response to the occurrence of certain events. For example, the customer's mood or state can be used as a trigger, such that a message appears when the customer's mood or state changes. In one example, when a first customer's mood or state changes to "partying", a second customer can program a message to appear, such as "You go home and do your homework!". Other special messages can be left by or for customers, such as when a song is playing (e.g., "This is my favorite song" or "I hate this song"), when a user logs in (e.g., "I didn't know you were out tonight" or "I can't believe I saw you here"), etc.

[0281] FIG. 45 is an example display 4500 including a "feed" related to a virtual storefront, according to one embodiment. A remote device can display the same or similar information, for example, through a social networking site, directly on the device, etc. The example display 4500 includes a main content area 4502 and an advertising area 4504, which in this example is displayed around the main content area 4502. It should be understood that the layout can be modified. For example, other shapes (e.g., a wide bottom, top, and / or sidebars) may be provided in place of the corner-shaped advertising area 4504.

[0282] The first feed 4506a includes information about the song being played, with associated illustration 4506b displayed adjacent to the information. In this example, the song "Hotel California" by the Eagles is being played. Playing the song automatically triggers a contextual factoid to appear in the second feed 4508a, with associated illustration 4508b displayed adjacent to it. Here, the factoid is that a version of the song "Help Freeze Over" is played with a total of eight guitars. User comments are displayed as a third feed 4510a, with personal images and / or avatars 4510b displayed adjacent to the third feed 4510a. Note that the username of the person sending the message is also displayed in the third feed 4510a. Customized messages from artists and labels are displayed as a fourth feed 4512a, along with an image of the Eagles themselves 4512b. Advertisements for upcoming concerts are shown as a fifth feed 4514a. When a user receives the feed on a personal device, the link provided for the fifth feed 4514a is a "live" link that, when selected, may take the user directly to a web page from which they can purchase concert tickets.

[0283] User messages are shown as the fifth feed 4516a. Keywords and contextual awareness are used to trigger events. In other words, posts are scanned for keywords and / or context and are provided for special promotional events. In this example, advertising space 4504 is updated in response to this detection. Thus, an advertisement for "Bud" is displayed in response to detecting the word "beer." In general, area 4504 is used as an advertising space or an illustration space that is contextually aware and is triggered and modified by certain events and / or the detection of keywords and / or other stimuli.

[0284] A timestamp may also be associated with each feed. New feeds are added to the top or bottom of the display. If too many feeds are displayed, the oldest feeds are removed and the feeds are "scrolled" up or down as necessary. The layout shown in Figure 45 is an example. In different embodiments of the invention, for example, the number of messages, illustrations, and / or other elements currently displayed may be swapped.

[0285] Due to the inappropriateness of messages (e.g., they are obscene, offensive, libelous, and / or otherwise inappropriate), store-specific and / or store-related technology may be provided for "cleaning" undesirable messages. For example, such technology may provide to an external system a complete "erasure" from display in the store and / or feed. A menu may also be provided that allows only a portion of the sentences, feeds, and / or messages to be deleted. A record of deleted items may be maintained, in case such a need arises in response to, for example, a customer complaint, police investigation, etc. Such records may be located in a separate storage location, or the database may simply have a "do not display" or "redacted" field associated with each entry, interpreted by programmed logic circuitry to provide the appropriate display control.

[0286] Also, in some embodiments, suspicious feeds are automatically flagged, removed, and / or edited. For example, the system can scan for inappropriate language or content (e.g., age-appropriate and / or other content filters are in place). Rather than simply deleting offensive content, it may be partially edited (e.g., replacing foul language with asterisks, etc.). Users can also flag a feed for review by appropriate authorities who will ultimately decide that the content should be left alone, changed, or removed.

[0287] An embodiment relates to an entertainment center, comprising a network-enabled computer, further connected to at least one display, standard analog, digital or network addressable, the computer operable to communicate with a remote device connected to one of the networks that interacts with the computer, the remote device operable to receive a code and transmit the code to the computer, the computer operable to verify the validity of the code against a database or against an algorithm, and upon positive validation, the computer configured to assign a monetary or credit value to the remote device. The remote device operable to view content contained in the computer, the remote device further operable to select the content and pay for the content with the monetary or credit value, the computer operable to reduce the monetary or credit value based on the selection by the remote device. The code is alternatively or additionally transmitted to the remote device and entered into the computer.

[0288] One embodiment relates to an out-of-home entertainment center in conjunction with at least one Internet-based messaging system and in conjunction with at least one remote device, the remote device being connected to the out-of-home entertainment center by a wired or wireless local area network or via the Internet, the entertainment center sending the messages to the at least one Internet-based messaging system by using some of the entertainment center's services from the remote device, the connection to the system via the Internet requiring the user to enter a code into the remote device that uniquely identifies the entertainment center.

[0289] Some of the portable devices referenced herein may be described, for example, in application Ser. No. 11 / 902,790, the entire contents of which are incorporated herein by reference.

[0290] Although this disclosure has used specific terminology, this is not to be construed as limiting the invention to a particular embodiment, hardware components and configurations, software configurations, etc. For example, although many of the features and examples have been described in connection with being present in a bar, pub, or other environment, the functionality present in one embodiment of the invention is applicable to use in any establishment where a jukebox (or multiple jukeboxes) is located. Similarly, while certain features and functions have been described with reference to the use of "user," "owner," "operator," "customer," etc., these terms are generic and, in most cases, are used interchangeably depending on the embodiment selected and the functionality used. For example, while it may be advantageous for the owner and / or operator to limit the initial song selection, in some embodiments the customer plays a role in the selection of the initial song. The term "display" includes, for example, a monitor connected directly or remotely to a computer, or an embedded IC such as IP·TV technology. The display may be network addressable. Also, standard digital signs (LED based) may be considered displays and / or provided as network addressable displays.

[0291] Furthermore, specific hardware combinations and configurations are disclosed that represent only one way in which an embodiment may be configured. In one embodiment, a centralized server is comprised of one or more servers operating simultaneously or separately to consistently provide the full range of services essential to enabling a functioning jukebox. For example, a cluster of servers may constitute a virtual centralized server, with one server providing media, another tracking membership, yet another license processing, etc.

[0292] Similarly, the local server described herein may be incorporated into a jukebox. For example, the local server may appear to function independently or through its presence as part of (e.g., separate from) the integrated mass storage in the jukebox. As hard disk capacities become larger and cheaper, it is desirable for them to function as local servers. One embodiment configures a 120 GB hard disk drive containing 25,000 songs as a factory drive. However, it is contemplated that a local server may be used in conjunction with currently known hard disk drives, as required by system designers for jukebox applications. Or flash media or any storage media developed later (or a combination thereof) may be used as factory drives, extended media storage, or local servers. In other words, the present invention is not limited to any storage technology or configuration, but may be implemented using any suitable storage technology.

[0293] Additionally, although the term "music" has been used frequently in the above description, this term is not intended to limit the scope of the present invention, and any instance or instances of media (e.g., music, video, music / video combinations, data, information, etc.) may be used in any embodiment and are within the scope of the present invention.

[0294] Finally, the screenshots and software configurations depicted herein are merely one way to organize and display the functionality disclosed herein. Other configurations are possible and, therefore, contemplated herein.

[0295] While a preferred form of the invention has been shown and described herein, it will be apparent to one skilled in the art that various changes and / or modifications may be made therein. Accordingly, the specific description herein is meant to be illustrative only and is not intended to limit the invention beyond the terms of the appended claims.

[0296] Certain exemplary embodiments relate to an entertainment system that provides social networking and / or other services for user interaction. In certain exemplary embodiments, the entertainment system is configured to provide jukebox-related and other services that are mediated by the entertainment system and accessible both inside and outside the store, thereby integrating social networking services for customers inside and outside the store and providing advertising opportunities. In certain exemplary embodiments, the in-store entertainment system serves as and / or is connected to the jukebox. In certain exemplary embodiments, the in-store entertainment system may be connected to one or more devices, one or more displays, one or more bar-top gaming devices, one or more handheld gaming devices, etc. Entertainment system-mediated jukebox-related services provide a way to enhance the customer experience and create a sense of ownership and belonging to a community of connected entertainment system users.

[0297] [Cross-references to related literature] This application claims priority to U.S. Patent Application No. 61 / 202,617, the entire contents of which are incorporated herein by reference, and the entire contents of U.S. Patent Application Nos. 11 / 902,658, 11 / 902,790, 12 / 076,761, 61 / 129,637, 12 / 222,785, and 12 / 318,864, each of which is co-pending and co-owned by the same applicant.

[0298] [Configuration 1] A jukebox installed in an outside store, the jukebox is connected to an entertainment system network and configured to play a plurality of media instances that are either stored locally on the jukebox or downloaded from the entertainment system network for a fee; The jukebox and a social networking system are configured to share data via a social networking interface, the social networking system being external to and not part of the entertainment system network.

[0299] [Configuration 2] 2. The jukebox of embodiment 1, wherein the social networking interface is part of the entertainment system network.

[0300] [Configuration 3] 3. The jukebox of any one of the preceding claims, wherein the social networking interface is external to the jukebox.

[0301] [Configuration 4] A jukebox as described in any one of configurations 1 to 3, wherein the entertainment system network further includes a jukebox social networking interface to a social networking site associated with the jukebox, the social networking site associated with the jukebox being unrelated to the social networking system.

[0302] [Configuration 5] The jukebox of any one of configurations 1 to 4, wherein the social networking interface is configured to connect a plurality of computers provided outside a store outside the home to the jukebox.

[0303] [Configuration 6] A jukebox as described in any one of configurations 1 to 5, wherein a non-jukebox device located outside the store and remotely connected to the jukebox is capable of controlling at least the selection of multiple media instances to be played on the jukebox and, in addition, the permission to share credits.

[0304] [Configuration 7] The jukebox of any one of configurations 1 to 6, wherein the social networking interface is further configured to receive a feed from the jukebox and provide a feed to the social networking system, the feed providing data indicative of a plurality of selected media instances that are being played or will be played on the jukebox.

[0305] [Configuration 8] The jukebox described in any one of configurations 1 to 7, further comprising a user authentication unit configured to authenticate a pre-registered user who logs in to the jukebox via a jukebox or a device other than a jukebox in a store outside the home.

[0306] [Configuration 9] 8. The jukebox of claim 7, wherein the feed further includes data indicating an authenticated user who selected each of the plurality of media instances that are being played or will be played on the jukebox.

[0307] [Configuration 10] The jukebox of configuration 7, wherein the feed further includes data indicating messages sent from an authenticated user via the social networking system to a user of another social networking system using an electronic device located at a store outside the home.

[0308] [Configuration 11] 11. The jukebox according to any one of configurations 1 to 10, including output to an external display.

[0309] [Configuration 12] 12. The jukebox of claim 11, which is controllable to output to the external display a list of selected media instances that are being played or will be played on the jukebox.

[0310] [Configuration 13] A jukebox as described in configuration 12, which is controllable to provide an authenticated user as output to an external display if the user who selected multiple media instances that are being played or will be played on the jukebox is authenticated.

[0311] [Configuration 14] A jukebox as described in any one of configurations 11 to 13, capable of controlling messages sent to a user of a social networking system from a user authenticated by the jukebox who sent the message via the social networking interface as output to an external display.

[0312] [Configuration 15] 15. The jukebox according to any one of configurations 11 to 14, wherein a message sent from a user of the social networking system to an authenticated user in a store outside the home can be controlled as output to an external display.

[0313] [Configuration 16] A jukebox as described in any one of configurations 11 to 15, which is capable of controlling trivia about a plurality of media instances that are being played or will be played on the jukebox as output to an external display.

[0314] [Configuration 17] A jukebox as described in any one of configurations 11 to 16, which is capable of controlling messages from artists or labels relating to multiple media instances being or to be played on the jukebox as output to an external display.

[0315] [Configuration 18] A method for operating a jukebox installed in an outside store, comprising: The jukebox is connected to an entertainment system network; receiving and responding to user requests to play a plurality of media instances that are either stored locally on the jukebox and / or downloaded from the entertainment system network for a fee; and sharing data via a social networking interface; A method of operating a jukebox, wherein the social networking system is external to, and not part of, the entertainment system network.

[0316] [Configuration 19] 20. The method of claim 18, wherein the social networking interface is part of the entertainment system network.

[0317] [Configuration 20] 20. The method of operating a jukebox of any one of configurations 18 to 19, wherein the social networking interface is external to the jukebox.

[0318] [Configuration 21] A method of operating a jukebox as described in any one of configurations 18 to 20, wherein the entertainment system network further includes a jukebox social networking interface to a social networking site related to the jukebox, the social networking site related to the jukebox being unrelated to the social networking system.

[0319] [Configuration 22] 22. A method of operating a jukebox as described in any one of configurations 18 to 21, further comprising the step of selectively controlling the jukebox in response to user requests received via the social networking interface from a plurality of computers located outside the off-site store, and from non-jukebox devices located in the off-site store remotely connected to the jukebox.

[0320] [Structure 23] providing a feed from said jukebox to a social networking system; 23. The method of operating a jukebox of any one of claims 18 to 22, wherein the feed includes data indicative of a plurality of selected media instances that are being or will be played on the jukebox, and messages to be sent to authenticated users who selected each of the plurality of media instances that are being or will be played on the jukebox, or to users of a social networking site.

[0321] [Structure 24] 24. A method of operating a jukebox as recited in any one of claims 18 to 23, comprising the step of providing output to an external display device.

[0322] [Configuration 25] The output to the external display device is data indicative of selected media instances being or to be played on the jukebox; data indicative of an authenticated user who has selected multiple instances of media that are being played or will be played on the jukebox; Data indicative of a message sent from a user of the social networking system to an authenticated user at an off-site store; data indicative of trivia about a plurality of media instances being or to be played on the jukebox; Alternatively, the method of operating a jukebox as recited in configuration 24 includes data indicating a message from an artist or label regarding a plurality of media instances being or to be played on the jukebox.

Claims

1. 1. An audiovisual device located outside a store and connected to an entertainment system network, the audiovisual device including at least one processor, the audiovisual device sharing data with a social networking system via a social networking interface; said social networking system is external to, and not part of, said entertainment system network; the social networking interface is configured to mediate communication between the entertainment system network and the social networking system; the audiovisual device transmitting a feed to the social networking system via the social networking interface; the feed providing at least one of data indicative of a plurality of selected instances of media being played or to be played on the audiovisual device and messages to be sent to users of the social networking system; The social networking interface is further configured to connect a plurality of computers located outside the off-site store to the audiovisual device.

2. The audiovisual device of claim 1 , wherein the social networking interface is part of the entertainment system network.

3. An audiovisual device according to any one of claims 1 to 2, wherein the social networking interface is external to the audiovisual device.

4. a jukebox social networking interface to a social networking system associated with the jukebox; 4. An audiovisual device according to any one of claims 1 to 3, wherein a social networking system associated with the jukebox is not associated with the social networking system.

5. An audiovisual device as described in any one of claims 1 to 4, further comprising a user authentication unit configured to authenticate a pre-registered user who logs into the audiovisual device via an audiovisual device or other electronic device located in a store outside the home.

6. 6. The audiovisual device of claim 5, wherein the feed further includes data indicative of messages sent from an authenticated user via the social networking system to another user of the social networking system using an electronic device located at the off-site store.

7. An audiovisual device according to any preceding claim, including an output to an external display.

8. 8. An audiovisual device as claimed in claim 7, controllable to output to the external display a listing of selected media instances that are being played or will be played on the audiovisual device.

9. 10. The audiovisual device of claim 8, wherein if a user who has selected multiple media instances that are being played or to be played on the audiovisual device has been authenticated, the audiovisual device is controllable to provide the authenticated user as output to the external display.

10. 10. An audiovisual device as claimed in any one of claims 7 to 9, which is controllable to output to the external display messages sent to users of the social networking system by authenticated users of the audiovisual device who sent messages via the social networking interface.

11. An audiovisual device as claimed in any one of claims 7 to 10, which is controllable to output to the external display a message sent from a user of the social networking system to an authenticated user in a store outside the home.

12. 12. An audiovisual device as claimed in any one of claims 7 to 11, controllable to output to the external display factoids relating to a plurality of media instances being or to be played on the audiovisual device.

13. 13. An audiovisual device as claimed in any one of claims 7 to 12, controllable to output to the external display messages from artists and / or labels relating to media instances being or to be played on the audiovisual device.

14. 14. The audiovisual device of claim 1, configured to remotely connect with other electronic devices via the social networking system to enable the other electronic devices to select multiple media instances to play on the audiovisual device and to transfer credits to the audiovisual device.

15. 1. A method performed by an audiovisual device located in an off-site store, comprising: said audiovisual device being connected to an entertainment system network; sharing the data with a social networking system via a social networking interface; transmitting a feed to the social networking system via the social networking interface; the social networking interface is configured to mediate communication between the audiovisual device and the social networking system; said social networking system is not part of, but external to, said entertainment system network; the feed providing at least one of data indicative of a plurality of selected instances of media being played or to be played on the audiovisual device and messages to be sent to users of the social networking system; The method, wherein the social networking interface is further configured to connect a plurality of computers located outside the off-site business with the audiovisual device.

16. The method of claim 15 , wherein the social networking interface is part of the entertainment system network and is external to the audiovisual device.

17. the entertainment system network further comprising a jukebox social networking interface to a social networking system associated with the jukebox; 17. The method of claim 15 or 16, wherein a social networking system associated with the jukebox is not associated with the social networking system.

18. 18. The method of claim 15, further comprising the step of selectively controlling the audiovisual equipment in response to further user requests, receivable via the social networking interface from a plurality of computers located outside the off-site store.

19. The method of any one of claims 15 to 18, further comprising the step of providing an output to an external display device.

20. The output to the external display device is data indicative of a plurality of selected instances of media being or to be played on said audiovisual device; data indicative of an authenticated user that has selected a number of instances of media that are being played or will be played on the audiovisual device; data indicative of a message to be sent from a user of the social networking system to an authenticated user at the off-site store; data indicative of factoids regarding a plurality of media instances being or to be played on the audiovisual device; and 20. The method of claim 19, further comprising: data indicative of a message from an artist and / or label regarding a media instance being or to be played on the audiovisual device.

Citation Information

Patent Citations

  • Karaoke remote control system

    JP2004004271A

  • Media content sharing experience

    JP2007501557A

  • Information processing equipment, service provision server, and remote operation apparatus

    JP2008129860A

  • Musical piece distribution system

    JP2008250694A

  • Jukebox with associated video server

    JP2009017529A