Patent Grant
12100258
The instant invention relates to, for example, jukebox systems and, more particularly, to digital downloading jukebox systems of the type which typically include a central server and remote jukebox devices that communicate with the central server for royalty accounting and/or content updates and, still more particularly, to jukebox systems that provide user-tailored music management, communications, and other tools for recognized users using the jukebox system. Exemplary embodiments of the instant invention improve such systems by providing a local server for each jukebox device in the jukebox system network. The local server provides a second and more expansive source of content (e.g., audio and/or visual data) that can be selected by a user of the jukebox device for reproduction on the jukebox device. The local servers may provide a mirror of or subset of the central server, thereby enabling the entire library of audio and/or visual data, or at least the most requested content, to be conveniently available to each jukebox device without the need to download requested content, that is not available on the mass storage device of the jukebox device itself, from the central server. The collective group of local servers may also act as a network of distributed content servers that can be controlled by the central server through each jukebox device to provide services to other devices, such as, for example, other jukebox devices. In addition, the jukebox device and local server can, under control of the central server, operate as a “central hub” or management device for various downloadable fee-based devices present in a location with the jukebox device.
Exemplary embodiments additionally can provide other mechanisms to enhance individual recognized users' experiences, such as, for example, by allowing users to create and manage playlists that can be retrieved on one or more jukeboxes, create and manage buddy lists that can send messages to individuals or broadcast to large groups of individuals, etc. In other words, in one embodiment, the jukebox includes features which enable the jukebox to recognize specific jukebox users, through prior registration or the like, and to provide user-specific services to the user. For example, the jukebox may allow the recognized user to create, edit and/or store custom playlists on the jukebox that can be selected by the user or other registered users designated by the creator of the playlist for play on the jukebox. The jukebox may also allow registered users to communicate with other registered users through the jukebox. Registered users may also be provided with credit on the jukebox so that cash is not necessary for using the jukebox services. The jukebox may also be used to provide background music services in addition to conventional jukebox services in a unique and advantageous manner as described herein. The jukebox may additionally increase a sense of ownership by interacting with a interactive application accessible at a location remote from the jukebox, such as, for example, via the Internet. The remote application may connect individuals to an online community through which users can, for example, communicate with other users, build playlists, share playlists, suggest music to others, participate in promotions, link to targeted advertisements, etc. Additionally, the jukebox and/or remote application may allow users to download information to a portable device, such as, for example, a cell phone, a personal digital assistant, an MP3 player, etc. In certain exemplary embodiments, users' actions on jukeboxes and/or via remote interfaces may be represented by avatars specific to and/or customizable by the user.
Jukeboxes have been around for decades and provide users with the ability to select desired music for reproduction in a convenient and advantageous manner. Jukeboxes have conventionally been provided in commercial establishments, such as restaurants and bars, in order to provide desired music on demand for patrons thereof for a fee. Over the last several years, a new generation of jukebox devices have become available that provide significant improvements in the operation thereof for all parties involved. More specifically, the conventional standalone phonorecord and CD jukeboxes are being replaced by digital downloading jukeboxes that are controlled by and communicate with a central server. An example of this new generation jukebox system is shown in U.S. Pat. No. 6,308,204, the entire disclosure of which is incorporated herein by reference. A leading provider of this new generation of jukebox systems is TouchTunes Music Corporation.
The jukebox devices 16 (sometimes referred to as simply “jukeboxes” herein) are operable to communicate with the central server 12 through a communications network 14, such as, for example, the Internet. The jukeboxes 16 periodically communicate with the server 12 in order to provide information to the server 12 regarding the specific songs that have been played on the jukebox. The central server then uses this information in order to determine the appropriate royalties and/or other payments that are owed for songs played on each jukebox. Thus, one significant advantage of this new generation of jukeboxes is that the sound reproduction and/or other applicable music rights can be adhered to in a more accurate and reliable manner, thereby assuring the proper royalties are paid to the artists or music owners. The central server 12 can also provide new songs to the jukebox 16 in order to assure that the appropriate or most popular songs are maintained on the jukebox based on the specific customers at that location. Thus, the songs available on each jukebox can be customized through communication with the central server in order to provide the songs and/or types of music that customers generally request at each jukebox location. As described in the above-referenced U.S. Pat. No. 6,308,204, the central server can also advantageously be used to update the operating software on the jukeboxes in order to, for example, change the operation of the jukebox, such as to provide new or improved features. Thus, another significant advantage of this new generation of jukeboxes is that the songs (or other audio and/or visual content), and the operation of the jukebox itself can be remotely changed as desired without the need to have someone (such as a routeman) personally service the jukebox. Instead, such updates can be done using the central server 12.
As indicated above, the jukebox devices 16 each include a mass storage device, such as a hard drive, which stores the songs and associated video/graphics data (if any), as well as any other desired graphical information for reproduction on the jukebox. The mass storage device of the jukebox typically has limited storage capacity relative to the storage device of the central server 12. As a result, only a fraction of the songs stored on the central server are typically stored on the mass storage device of the jukebox at any one time. There may be other reasons as well, such as for security of the data or limited room in the jukebox itself, for having limited storage capacity on the jukebox and/or limiting the number of songs stored thereon. For example, physical space may be limited on wall-mount jukeboxes or the like, which are designed to be small in size as compared to free-standing models. As explained above, the songs on the jukebox can be changed through communication with the central server, but typically any one jukebox only stores a relatively small subset of the complete library of songs maintained by the central server at any one time.
In order to maximize the revenue that a jukebox generates, it is important to make the most desired songs available on the jukebox over time. If customers cannot find songs they like on the jukebox, usage of the jukebox (and the revenue generated thereby) will dramatically decrease. On the other hand, it is impossible to predict in advance exactly what a customer at any particular location will desire to play on the jukebox. In fact, there are likely many instances where a customer would have selected a song that exists on the central server but is not currently present on the jukebox. As a result, the jukebox may not be enjoyed and used to its fullest extent. In order to address this problem and increase revenue, jukebox systems have in the past provided a feature which enables the user to search for songs on the central server from the jukebox and request an immediate download of a desired song from the central server to the jukebox for an additional fee. This feature enables the user to play any song in the master library of songs maintained by the central server using the jukebox, regardless of whether or not the specific song is presently stored in the mass storage of the jukebox itself. Thus, the user can first look for desired songs on the local storage of the jukebox and then, if desired, search further on the central server for desired songs. The jukebox device typically charges an additional fee (such as five credits instead on one credit) for an immediate download and play of a song from the central server as opposed to a standard play directly from the jukebox's local storage.
One problem, however, with the immediate downloading feature is that it is desirable to have an immediate and high speed connection with the central server to implement. In addition, the central server and network must be prepared for and capable of handling such requests in a reliable and efficient manner for the feature to properly operate. These requirements cannot always be met and, as a result, implementation of this feature has been limited. For example, many locations that have jukeboxes do not have high speed connections (such as DSL) and instead use dial-up modem connections. Jukeboxes which rely on dial-up connections generally are only designed to communicate with the server periodically and do not allow the user to immediately download a song. They have, however, enabled a user to vote for a song to be downloaded at a later time when the dial-up connection is made. This, of course, is not as satisfying to the user as being able to immediately download a song. Other problems can arise in connection with this download feature if the network or server is not currently available for the download, due to traffic, malfunctions or the like.
For most users, a relationship with a jukebox extends only as far as a choice of songs to play. Casual users may find it difficult to make selections rapidly and/or to locate specific songs. Regular users, however, frequently choose the same songs, and they may become frustrated with always having to make the same selections. Both problems may result in a loss of revenue from intimidation, frustration, etc.
Thus, it is a feature of the exemplary embodiments to create a relationship between the jukebox and the patrons, in view of the further feature of creating a relationship with a whole community of jukebox users. Such a system can establish a trust relationship between the jukebox and the patrons, while also creating a sense of ownership for the patrons by allowing them to customize their services and communicate with their friends. Such a relationship and feeling of ownership can greatly increase the convenience of using a jukebox and its related services while also decreasing intimidation, frustration, etc.
In certain exemplary embodiments described herein, the jukebox can be made the centerpiece for music services as well as other services that enhance the experience of users as well as the revenues of location managers. For example, a jukebox can become a contact point at a given location through which users can reach out to their friends. For instance, users may call a get together using the jukebox, share music through the jukebox system, or meet up at a jukebox if they become separated at a crowded club. Similarly, a jukebox can become, for example, a contact point at a given location through which the manager of the location can reach out to customers. For instance, a manager can advertise specials, notify regulars of special events, etc. Such communications can be initiated by users, by location managers, or by the jukebox itself.
When jukebox users leave a location, their connection to the music, and, more particularly, the jukebox itself, typically ends. Users provide massive amounts of data to the jukeboxes, such as, for example, which users like certain types of music or certain songs, when they listen to music, how frequently they listen to it, etc. With conventional jukeboxes, this information is not leveraged to provide additional features and/or services to interested users. Thus, collected information typically is wasted, and users experience only a fleeting sense of ownership. Users cannot, for example, recreate the experience of a particular night out.
Proprietors also lose out, because their connection to jukebox users disappears when users leave their establishments. Thus, proprietors lose customers until they return and are forced to rely on traditional, often ignored, methods of bulk advertisement. This form of advertising typically lacks specificity and does not reflect a personalized sense of belonging for users. Additionally, proprietors also cannot recreate specific events at which, for example, they had a particularly profitable nights.
Online communities typically, for example, on the Internet, have sprung-up to try to connect disparate users in a virtual space. These communities provide potentially continuous access to a broad range of features and users alike. However, conventional online communities are virtual only—when a user steps away from a computer, the connection, quite literally, is broken. Thus, while users may access this broad host of features and customize their experiences and even build an online persona complete with, for example, buying and viewing habits, the experience is fleeting.
By connecting jukebox users through an online community, however, the information provided to the jukebox can be used to provide a variety of features and services to the users. And, because jukeboxes are present at thousands of meeting points, connections exist at thousands of physical locations apart from the online virtual community. Thus, by leveraging the data collected by jukeboxes and tying users to an online community, a mixed real-and-virtual community may be established, for example, creating a lasting sense of ownership, personalizing services for potentially all users, drawing users together, establishing a vibrant socially active community of users connected by music, etc. Proprietors may similarly benefit by, for example, achieving a pipeline to additional business by connecting with customers while they are away from their locations, thus drawing them to their locations, etc.
In essence, a jukebox with an associated remote application can, for example, change users' perceptions of jukeboxes. Jukeboxes need not be stand-alone devices accessible only at bars. Rather, the instant invention allows users to consider jukeboxes as, for example, media centers, meeting points, portals to online communities, etc.
Moreover, with the advent of web-enabled portable devices (such as, for example, cell phones, personal digital assistants, etc.), users even can take the virtual community with them wherever they go. Users potentially may use portable devices to directly download music at any time, such as, for example, when they hear a song at home, in the car, at a bar, etc.
In certain exemplary embodiments, users' actions on jukeboxes and/or via remote interfaces may be represented by avatars specific to and/or customizable by the user. Jukeboxes may include avatar action programmed logic circuitry (e.g., any appropriate combination of hardware, software, or the like) to take actions on behalf of and/or represent the actions of the user. Such actions may include introducing songs with audio and/or video, singing and/or dancing along with music, marking online transactions (e.g., messages, postings, file transfers, etc.), etc. As such, user avatars may yet further increase senses of ownership and/or belonging, drawing users to jukeboxes. Moreover, avatars may further increase the enjoyment of the individual user, regular patrons, and/or newcomers to an area
There is a need for an improved jukebox system that addresses various needs of users, location owners, and operators. The instant invention is designed to address these and other issues and to provide enhanced functionality for such jukebox systems.
These and other features, objects and advantages of the instant invention will be further understood by review of the following detailed description of the exemplary embodiments when read in conjunction with the appended drawings, in which:
Referring now to the drawings,
The songs (and/or other data) are preferably digitized, compressed and encrypted by the central server 12 prior to sending songs to the jukeboxes for security and bandwidth purposes using known techniques. The songs are then decompressed and decrypted by the jukeboxes for storage and reproduction thereon. Thus, each of the jukeboxes maintains in a database a library of digitized songs for play on the jukebox, wherein the library can be changed or updated through communication by the central server. The jukeboxes preferably also receive and store data constituting images (e.g., still and/or moving video and/or graphical images) that can be displayed on the display 18 of the jukebox device 16. In one exemplary embodiment of the invention, the jukebox devices have similar structure and operation described in U.S. Pat. No. 6,308,204 referenced above. Thus, the jukebox devices 16 each preferably include one or more microprocessors, such as a main CPU and an audio DSP, a memory, such as a hard drive, for storing songs and/or other content, a display of displaying visual items, an audio arrangement 20 for providing audio, a communication system for enabling the jukebox to communicate with the central server 12 through the communications network 14, and operating software, preferably including a multitasking operating system, that controls the operation of the jukebox. The operating software is also preferably updateable through communication with the central server 12 as described, for example, in U.S. Pat. No. 6,308,204 referenced above. The jukeboxes 16 further include one or more payment devices, such as coin, bill and/or credit card input devices, for enabling a customer to pay for usage of the jukebox device in a convenient manner. The screen 18 is preferably a touch screen that enables the user to input selections by touching the screen.
Each jukebox device has, in one embodiment, a local server 22 that can be accessed by the jukebox device. The local servers are respectively connected to the jukebox devices using Ethernet or other type of local connection. In another embodiment, the local server may simply be a logical extension (e.g. partition, directory, or area) of the jukebox's hard drive, rather than a separate hardware device. The local servers 22 each preferably include a mirror copy of the master library of musical recordings maintained by the central server 12. The local server 22 can be loaded with the master library by the entity that owns and/or controls the jukebox network prior to shipping the local server and jukebox device to the jukebox distributor or operator. Of course, over time, the local sever will no longer correspond identically to the central server, due to the fact that the central server is preferably continually updated with additional or new songs. Thus, the local servers 22 are also preferably updated periodically to maintain a correspondence with the library on the central server 12. This updating can be done, for example, by the central server 12 through communication with the jukebox devices connected with the local servers 22 using, for example, either dial-up or broadband modems. Alternatively, the updating can be done personally with an update tool that can be connected by a routeman or other person directly to the jukebox or local server for the purpose of updating the contents of the local server. The portable tool could include a removable storage medium, such as a hard drive, that could be returned to and reused by the owner of the jukebox system for future updates. The tool itself could be kept by the operator or other person in charge of maintaining specific jukeboxes for use upon receipt of the updated removable storage medium from the owner of the jukebox system.
For security reasons, the local server 22 preferably does not include all of the digital data that constitutes any one song that is stored on the local server 22. In addition, the part of the song that is on the local server is encrypted. The jukebox device 16 contains the missing part of each of the songs on the local server, thereby enabling the jukebox to assemble the complete song based on the contents of the local server and the memory on the jukebox device. The missing data located on the jukebox is needed in order to decrypt the songs. For example, a single block (or other small fraction) of data for each song may be missing on the local server but present on the jukebox device, and the encryption may be based on the missing block and may proceed on a block by block basis. Thus, none of the blocks can be decrypted without obtaining and/or decrypting a preceding block. This feature provides significant security and prevents or deters theft or other type of unauthorized use or copying of the songs on the local server. Thus, in this embodiment, each local server must be specifically assigned to a specific jukebox device so that the decryption described above can be properly performed.
In accordance with a preferred exemplary embodiment, the local servers may also each be individually registered with and identified to the central server 12, so that the central server can individually manage and monitor each local server. The same is true for the jukebox device itself, i.e., it may also preferably be registered with the central server so that it too can be individually monitored and managed by the central server. As will be understood from the foregoing description, the local servers become an important and advantageous part of the jukebox system by allowing the contents thereof to be accessed by the jukebox device to provide additional services (such as providing additional songs) not available on the jukebox device itself. As will be explained below, the song library of the central server and/or the storage capacity itself can be advantageously used to provide services to other jukeboxes, such as fee-based residential and commercial jukeboxes and/or other fee-based equipment. One preferred use of the local servers may be to provide an immediate song downloading feature for the jukebox device will now be described below in detail with reference to the exemplary screen shots of
If the user does not see an album of interest in the display of album covers or desires for any reason to search for available songs that are not present on the jukebox device, the user may select the “Tune Central” button 39. When the “Tune Central” button is pressed, the display on the jukebox is changed from that of
Genres may comprise, for example, “pop,” “rock,” “country,” “rap,” “R&B,” “Blues,” etc. Themes may comprise, for example, “Christmas,” “Irish,” “Birthday,” etc. In some exemplary embodiments, these lists can be retrieved from the server, while in other exemplary embodiments the lists may be built dynamically, based on, for example, certain parameters. In still other embodiments, the server may select which lists to enable or send to the jukebox based on criteria, such as, for example, location, music type, etc. A system might only display genres and/or themes for which music is downloaded. However, a system might display all genres and/or themes and enable download of other songs not available to the local jukebox. It also will be appreciated that although
Similar to the genres and themes search, a user may, for example, search for a song using a Personal Music Assistant, an exemplary process for which is shown in
Furthermore, instead of entering identifiers, as shown in
Additionally, a Personal Music Assistant recognizing, for example, a preferred customer or a customer with a large number of credits might morph the jukebox into a jukebox more enjoyable to that specific user. In a related feature, certain patrons may “rent” a jukebox for, for example, a special occasion. Accordingly, a patron could pay a certain amount of money to morph the jukebox into a particular type of jukebox. For example, a patron having a party (e.g. a birthday party) at a particular location could rent a jukebox and morph it into a jukebox that allows only that patron's favorite songs. In another related feature, a patron could exclusively rent a jukebox and prevent others from selecting songs by, for example, programming a playlist through another device (e.g. the web or other communications network operably connected to the jukebox system) or by restricting access to the jukebox through a password or the like. Credits could be, for example, purchased by the user; or given to the user as a reward, for example, for purchasing drinks or souvenirs at an establishment, or for being a regular repeat customer. Thus, a Personal Music Assistant could be implemented in a manner that makes selecting songs a more enjoyable, dynamic, and responsive process while removing the immediate pressure placed on the user to know which song to choose.
When a search is initiated from screen 40, the screen changes to that shown in
Also providing an enjoyable experience for the user is the central servers' capability to identify “hot hits,” preferably in real-time. Preferably, new songs could be made available in a master catalog—that is, they need not reside on local servers or expanded media storage. Then, songs played frequently in a given area (ranging from, for example, a single site or group of sites, to a state or country, to a global connection) could be identified as popular. These songs, or “hot hits,” preferably could be downloaded by, or sent to, individual jukeboxes. Individual jukeboxes preferably would maintain lists of “hot hits” in real-time, allowing users to search through the most popular songs at any given time. Alternatively, a jukebox might maintain a list of “hot hits” without downloading the popular songs, thereby potentially saving download time and resources. As a result, the jukebox could provide an enjoyable experience for the user by providing easy access to the most popular songs. Thus, a jukebox may have access to a “hot list” of “hot hits” generated by a jukebox, jukeboxes, designated by an operator, created automatically and/or especially for enabled jukeboxes, etc. This “hot list” may work as an alternative to themes and/or genres, and/or it may function with themes and/or genres to provide the most popular (“hot”) songs within a given theme and/or genre. Similarly, a user also may select a song from a list of recently played songs. Such a list may be maintained (e.g., stored and updated) on an individual jukebox, or it may be maintained at a central location so as to be accessible and/or updatable by any suitably configured jukebox device.
As also shown in
As can be seen from
In still other exemplary embodiments, a location might provide a “Virtual DJ.” According to one such system, a prepared playlist would be provided to the jukeboxes of a location. Preferably, the playlist can be tailored to the details of the location and/or the event to take place, such as, for example, locale, theme, target audience, etc. Furthermore, some illustrative playlists could be created by famous DJs to attract patrons. DJs could attach their names to playlists and associate themselves with various locations, even though they are not present. A playlist might extend for several songs or for several hours, depending on the needs of the location. It is to be appreciated that coinage need not be collected during such a Virtual DJ event, as a special fee can be associated with the service of using a special playlist. It also is to be appreciated that DJs may prepare special playlists for one-time use, or they may make available repeatable special playlists. These repeatable playlists may, for example, be downloaded by jukeboxes or provided to the jukebox in any suitable manner. Thus, making third part playlists available for use on the jukebox for a fee provides a whole new revenue source for the jukebox operators, location owners and playlist generators, such as well-known DJs or the like. When a playlist is made active, the normal functions of the jukebox are preferably stopped during play of the songs on the playlist.
As will be appreciated from the description of the invention above, the addition of the local server significantly enhances the operation of the jukebox devices that are part of a jukebox system. However, the local servers also provide other benefits and features that will now be described.
A collection of local servers 22 may be used as a network of distributed servers that can be controlled by the central server 12 through its associated jukebox device 16 to provide music services to other devices. For example, the local servers and associated jukebox can be used to deliver requested songs to a dedicated residential or commercial jukebox device (or other suitable jukebox device) in addition to providing song services to the specific jukebox to which it is connected and assigned. Thus, the network of distributed servers can provide a support network for implementing residential and commercial jukeboxes of the type which allow a user to download songs for reproduction and/or storage at a residential or commercial location for an appropriate fee. As a result, the jukebox system operator can provide and control commercial jukeboxes and well as residential jukeboxes through the jukebox system. In this embodiment, the jukebox device and/or local server are connected to the Internet (or other suitable network) using a broadband modem and is provided with software that can selectively deliver song files to any dedicated residential jukebox device (also connectable to the Internet) under control of the central server. The central server receives requests from a residential jukebox and, by analyzing traffic on the network, provides instructions to a selected jukebox device to download the requested song file (either from its memory or from the local server) to the residential jukebox for a fee or under a subscription plan for the residential jukebox. In certain exemplary embodiments, requested songs may be streamed to a jukebox. It will be appreciated that streamed media may originate at a dedicated server, a network of streaming servers, from a jukebox or jukeboxes (such as peer-to-peer or multipeer downloading), etc.
In accordance with another exemplary aspect of the invention, the local server and jukebox device are used, under control of the central server, to provide management services for other types of coin operated or payment triggered equipment, such as gaming devices, installed in the same location as (or in close proximity to) the jukebox. In other words, the jukebox system is preferably used to update the functionality of and/or manage other downloading devices present in the same location. As a result, the jukebox becomes a “central hub” for all downloading equipment in a location. This feature is achieved, in one embodiment, by networking all of the downloading devices in a single location together with the jukebox and local file server. The central server can then download information to the local server together with instructions to the jukebox as to which devices should updated with what data and/or software. The jukebox device and central server can also be used to collect information from the other downloading devices to which it is managing and upload that information to the central server for reporting/accounting purposes. Thus, the owner/operator of the jukebox system can act as a third party service provider to other coin-op companies for the purpose of managing and/or updating their equipment.
The large amounts of memory provided by the local servers and the fact that they are provided and accessible at thousands of locations over a well controlled network, turns the jukebox system into a powerful tool that can be used to perform a variety of functions in the coin-op industry. More and more coin-op manufacturers are going towards games that are software upgradeable through their internal hard drives. These updates are done periodically, but as these devices increase there will be an ever increasing need for a system that can reliably and efficiently perform the updates from a remote location. The jukebox system described herein satisfies this need by enabling all suitable electronic coin-op devices at a jukebox location to be managed by the central server using the jukebox and local server at the location. The central server can download software or data updates, store them on the local server and then dispatch the updates to the intended units of equipment in the establishment. Thus, the jukebox system can act as a third party service provider to other companies in the coin-op business, thereby significantly enhancing the functionality of the jukebox system.
As an example, there are currently about 140,000 Merit coin-operated countertop devices in the USA, each of which enables users to play games and the like for a fee. Many of these devices operate with a hard drive that can be upgraded with new software. Merit does this by shipping CD-ROMs to operators who then need to drive to each location and manually update each machine. In accordance with the instant invention, however, all suitable coin-op equipment at a location are connected (directly or indirectly) with the local jukebox and local server assigned thereto. This enables the central server to receive the intended software update for any device, together with information that identifies what devices are to be upgraded with what software. The upgrade services are preferably fee based and provide an additional revenue stream for the jukebox system. The central server then downloads the software to the local servers with the upgrade instructions to further download the upgrades to the appropriate device(s).
As explained above, the local server enables songs to be downloaded to a commercial jukebox to which it is assigned or to residential jukeboxes under control of the central server. In addition, the local servers can be used for an on-premise networked application which manages other coin-op devices. These various features of the instant invention are illustrated in
Alternatively, the user may elect to have a song played in more than one of the zones 121, 123, 125 simultaneously, or in more than one of the zones at different times. The user may have to pay additional credits to implement either of these features. A preferred embodiment of a multi-zone system could play music at a high quality in the different zones using the system described in application Ser. No. 11/023,390, filed Dec. 29, 2004, entitled “Wireless Digital Transmission System for Loudspeakers,” which is a continuation in part of Ser. No. 09/161,584, filed on Sep. 28, 1998. The entire contents of both applications is incorporated herein by reference. Using this system, for example, a jukebox could compress and transmit audio data through AC power lines to an addressable location, where it could be received, decompressed, converted, and played. In fact, any of the jukebox components herein could be implemented in a manner that uses AC power lines as a communication network for operation.
It is to be appreciated that Wireless Digital Transmission System can be used for other purposes in other embodiments where data needs to be sent between two or more devices. For example, this system could be used to configure dummy terminals. In such an embodiment, the Wireless Digital Transmission System could be used to send information such as, for example, whether to morph, what songs are appropriate given a particular morphing of the jukebox, the zones in which selected music should be played, maximum volume levels, etc, in addition to sending music to the speaker systems.
The operator may also restrict what kind of music is available in a given zone, based on the type of activity in the zone, the time of day, or any other suitable selection criteria. For example, in
In the embodiment of
Additionally, the graphical interface of the terminals 137, 139 may change in accordance with available selections, themes of the bar, themes of the room in which each terminal is located, or any other suitable criteria.
In certain exemplary embodiments, the songs in a queue also may be reordered for other reasons. For example, the songs may be reordered to smooth transitions between songs, thus providing better (e.g., more aurally pleasing, less abrupt, more smooth, etc.) end-to-beginning playback of the songs. Thus, in certain exemplary embodiments, a method for altering the order of playback songs is provided. In such a process, the “color” of the song may be determined for two or more songs in the playlist. The color of a song relates to characteristics of the song, such as, for example, the volume, rhythm, beat, tempo, etc. of the song. After the color determination, the colors may be compared, and the songs may be reordered to group like (or dislike) songs. Optionally, the color of the song(s) may be determined and also may be used to control lighting, displays, etc. to provide a more interactive experience.
Once the songs on the drive have been appropriately categorized (i.e. the basic playable list has been defined), the jukebox begins operation 189. As long as a new basic playable list is not desired 191, the jukebox continues to operate 189 with the currently selected basic playable list. If a new basic playable list is desired 191, the jukebox morphs 193 into a “new” jukebox, selecting a different playable subset of songs for basic selection 185, and preferably changing additional characteristics (e.g., graphics, ads, look and feel, etc.) of the jukebox as dictated by the morph. The ability to morph jukeboxes thus enables owners and/or operators to maintain a single jukebox with a plurality of triggerable personalities which can be switched between automatically, at pre-defined events/times, manually, etc.
Pressing Dynamic Master button 164 is one exemplary, non-limiting way of providing increased user control over the morph.
When a user presses Clone a Location button 166 (e.g., from
Still further, a user can morph a location based on a location's data, specific to, for example, a given date or the latest data known. This allows users to morph a jukebox based on, for example, the popularity of a given morph—e.g., users may choose to revert to a successful morph to try to recreate the entertainment of that evening. This feature also enables users to recover from hard drive crashes and/or other jukebox failures. For example, if a hard drive has been replaced after an old one crashes, a user may morph (or clone) an existing location at a given date and/or time before the crash to restore the songs that were available before the crash because, preferably, the server maintains information sufficient for this functionality. Thus, using the morphing function gives users increased control while also providing backup and restoration features.
If the song is not available on the local hard drive, the jukebox checks to see if a high-speed connection to the central server is available 239. If there is no high-speed connection, the jukebox informs the user that the song is temporarily unavailable 241 and orders the song for download 243. The jukebox may or may not charge an additional amount for ordering the song. If, however, there is an available high-speed connection to the central server, the jukebox orders the song immediately and uses the high-speed connection to download the song right away, queuing it up for playing 245. The jukebox then charges the customer the price of a non-standard selection 247. In certain exemplary embodiments, a jukebox may retrieve songs offline, either after a location closes or before it opens. In certain exemplary embodiments, a jukebox may immediately download a song over a dedicated line with a dial-up connection. In certain other exemplary embodiments, a song may be downloaded from another jukebox (or other jukeboxes) rather than from a central or limited database to reduce network strain. In certain exemplary embodiments, the jukebox may download songs via a distributed media service in which portions of a given song may be downloaded from a plurality of sources and reassembled for the target jukebox. It is to be appreciated that such a peer-to-peer (or jukebox-to-jukebox) or multipeer (several jukeboxes to jukebox) digital downloading network will need to track song licensing information. In certain exemplary embodiments, if a song is not available on a jukebox but other versions or covers are available, the jukebox may recommend to these other songs to the searching user. For example, a user searching for an unavailable Trisha Yearwood version of “How Do I Live” may be recommended available versions by Dolly Parton and/or LeAnn Rimes. Preferably, recommendations will be smart enough to ignore similarly named songs that are completely different, such as, for example, the Everly Brothers' “Oh, Pretty Woman” and the Motley Crue's “Pretty Woman.”
The factory drive explained above, combined with the morphing capabilities, eliminates the need for the local server explained above, as the factory drive can prove the same services as the local server, without the need for a separate hardware device. In other words, the factory drive embodiment herein enables a jukebox to be shipped with a single mass storage device of any technology (or multiple technologies and/or multiple devices acting as a single mass storage device), while still enabling a basic playable list to be defined, an expanded playable list to be defined, morphing capabilities, local server services to be provided, as well as all other features described herein. The content of the factory drive, as shipped, is preferably defined using historical, statistical information on customer preferences.
Alternatively, in another exemplary aspect of the illustrative embodiments, a user can bid on the right to have a song played before other songs previously selected for priority play are played. In a preferred embodiment, the user is shown the top price paid for a priority play, and can pay more than that price to obtain the highest priority available.
Another exemplary aspect of the illustrative embodiments does not allow a user to be shown how much anyone else has paid for priority. The user can pay however much the user desires to spend to obtain a priority ranking, and then receive a ranking of priority based on the amount paid.
In accordance with a further exemplary aspect of the illustrative embodiments, a user can pay however much the user desires to spend to obtain a priority ranking in accordance with the previous exemplary aspect, and then be shown the priority spot which has been obtained based on the paid amount. If this spot is not satisfactory to the user, the user can pay additional money to move the song up in priority ranking, and be shown the new priority ranking obtained based on the additional money paid. The user can repeat this process until the desired priority ranking has been obtained. The user can also pay additional money to make it harder for other users to pre-empt the selected priority spot on the list in a bidding-type situation. Any other suitable method of increased-pay-for-increased-priority may also be implemented.
In accordance with an additional exemplary aspect of the illustrative embodiments which may provide a “lock in” feature, a user can “lock in” a priority ranking with a payment of a pre-selected amount. For example, if a user pays 15 credits to obtain a ranking of 3rd in priority, and wishes to guarantee the third ranking, the user may pay, for example, 4 more credits to “lock in” the ranking. Since locking in the ranking may require the “lock in” of all the rankings above the user as well, the user may be required to pay a certain amount to “lock in” all songs above the user's selection. In one such situation, the user can either choose to pay the price quoted for the “lock in” or pay the same or a varying amount of credits in an attempt to prevent future over-bidding or to move the user's song up further in the priority list.
In accordance with another exemplary aspect of the illustrative embodiments, any of the aforementioned bidding strategies may be implemented, and the user may be shown how much everyone has paid for their particular rankings. This allows the user to know exactly how much he will have to pay to obtain a certain priority position. If the “lock in” feature is implemented, this will also let a user know if it is cheaper to pay the price to “lock in” the song or to pay to move up on the priority list. All of these options result in increased revenue for the operator.
It should be noted that although the embodiments above describe a system for distributing media to non-movable jukeboxes, alternative embodiments using similar systems could distribute media to portable jukebox devices and are contemplated by, and within the scope and spirit of, this invention. A portable jukebox may be, for example, a PDA, a cell phone, or any other movable device capable of receiving and playing music. Furthermore, media may be distributed to portable jukeboxes using the above described methods (e.g. through a broadband connection, wireless connection, etc.), or any other appropriate method, more suited to the particular portable device, such as, for example, using Bluetooth technology. Additionally, the jukeboxes described above typically are for commercial purposes. However, jukeboxes for other purposes such as, for example, playing residential media, also are contemplated by, and within the scope and spirit of, this invention.
In other exemplary embodiments, an employee of a location with a jukebox can be rewarded based on the number of plays customers pay for on the jukebox. In one such exemplary embodiment, the system keeps count of how many plays have been paid for by customers. Every time a certain number of plays have been paid for, the bar employee receives one free play. In some embodiments, a separate counter will be maintained, while in others embodiments only one counter may be necessary to calculate the number of free plays available. Thus, certain exemplary embodiments encourage employees to promote the jukeboxes by compensating the employee with free plays. This also can help reduce the similarity of song-selection throughout the day, preserve free plays for employees of different shifts, etc.
Similarly, jukebox users may vote for particular instances of media to alter their priority in playlists. In this way, jukebox users can, for example, “battle” for control over the music to be played in a particular zone or particular zones within or among locations. It will be appreciated that this voting/battle mode may be implemented by using, for example, a dynamic queue, a priority queue, multiple queues, etc. It also will be appreciated that a jukebox could put into a voting mode automatically (e.g. at a particular time of day and/or on a particular day of the week), or it could be triggered manually.
As users see the coming songs, they will be tempted to push up the songs they like so the songs and/or push down the songs they do not like. In general, the more users who vote, the greater the ambiance of good songs. Thus, after step S1908, or in the case that the song is not over, the jukebox receives users' votes for particular songs in step S1910. Voting can be based on credits (as users buy credits), or tied to a user's account. In certain example embodiments, users must login to place a vote, and in certain example embodiments, users can vote a limited number of times. Preferably, users may vote from at least two distinct places within a location. The queue is updated based on this voting in step S1912, and the process returns to step S1902, where the displayed list is refreshed.
In certain example embodiments, the queue may be based on the total number of votes for particular songs. In certain other example embodiments, users may vote for and/or against certain songs and the “net” information may be displayed, indicating the number for and against, or merely the net result. If there are more votes against a song than for, the system can perform one or more of the following functions. For example, the jukebox simply may keep the song in the queue with a negative number of votes. Alternatively, the jukebox may keep the song in the queue with a zero or negative number of votes, but, for example, always wait until the net vote reaches at least 1 before playing the song. Still alternatively, the jukebox may drop any song that reaches zero or a negative number of votes.
An alternate application includes a voting-mechanism where multiple locations (e.g. bars, restaurants, venues, etc.) are networked together through, for example, the Internet. Those linked locations allow more patrons to “battle” against each other. In this embodiment, the networked jukeboxes would be playing the same song and collectively all users from all locations would decide on the playing order through the voting mechanism or the like. Thus,
An alternate application of this voting features relates to enhancing the “pause” mode of a jukebox. A jukebox, while in pause mode, typically prevents users from selecting music from the jukebox. For example, bartenders may use a pause mode when a special event (e.g. a football game) is presented at the location and when the audio system of the location is playing the match or event. The voting feature can be used to select which songs will be played after the special event is over. It has been widely observed that patrons watching a game very often leave the location once a match is over. This alternate method of selecting songs to be played is likely to motivate patrons to stay in a location and/or continue using the jukebox, etc.
If the user is recognized in step S2002, the MyTouchTunes main menu is displayed for the user in step S2006. From the MyTouchTunes main menu, users using a system according to this exemplary embodiment may, for example, edit account/profile information in step S2010, manage music in step S2020, manage buddies in step S2030, communicate with others in step S2040, and/or access various value-added content that may be provided by the system in step S2050. These and other features will be described in more detail below with reference to
A user would first input personal data in step 2012. Such personal data may include, for example, an e-mail address for the user, a telephone (preferably mobile phone) number, and/or a name. The system also may prompt the user to create a unique username and password so that the system can identify the user at later times and from other locations. Alternatively, the system may use the user's e-mail address as a username and only require a corresponding password. Still alternatively, in the case of residential jukeboxes, for example, an exemplary system may not require a password at all. Based on the personal data, the exemplary system may gather enough information to recognize the user at logins (e.g., online access, preferred location, other locations within a given area, etc.) as well as send e-mail and text messages to the user. These exemplary features will be discussed in greater detail below.
In step S2014, users may specify various locations they frequent. This feature may enable user-tracking by various establishments, advertisers, etc. Establishments may, for example, provide special offers to regulars or others in a particular area to entice them to come visit. Advertisers may monitor the personal information, location information, and playlists to provide, for example, concert tickets, special offers on CDs, t-shirts, and/or other merchandise that may seem to be appealing based on the user's preferences. Still further, if such account/profile information is stored locally on various terminals, the system may communicate with those other terminals to provide the playlists in preparation for a user's visit. In step S2016, a user may add credits and/or specify payment information. Users may, for example, use their credit cards to increase the number of credits they have before entering an establishment, or while at an establishment. Alternatively, users may become “certified” by, for example, providing credit card information and allowing jukeboxes to automatically bill their credit cards for future credits purchased, etc. It is to be appreciated that step S2016 can be used to purchase credits for oneself or for someone else, such as, for example, one's buddies, an employee of the establishment, etc. It also is to be appreciated that a user may transfer money from an account, such as, for example, a Pay-Pal account, to a jukebox-specific account, or a user might use such an account to purchase music and/or services directly.
In certain exemplary embodiments, a user may register by creating an account at a jukebox and providing a verifying contact mechanism, such as, for example, a mobile phone number and/or email address. After a user creates an account and inputs verifying contact mechanism, a message may be sent to that location. For example, a user may receive a text message. Once that message is received, the user may be prompted to input a code to the jukebox, send a return email or text message, etc., to become fully registered and/or to take advantage of certain other advanced features, such as, for example, one or more of the features disclosed herein.
In addition or in the alternative, further playlists may be imported from external sources. For example, software and/or hardware devices often store user-defined and/or custom-generated (e.g., most frequently played, recently added, etc.) playlists. By way of example and without limitation, playlists may be extracted from iPods, portable MP3 players, and/or other hardware devices. This may be done at the jukebox using an appropriate hardware connector provided to the jukebox and/or at a device remote from the jukebox (e.g., on a home computer) where it is more likely that an appropriate hardware connector will already be located (e.g., a proprietary docking port, a USB connection, etc.). In either or both cases, the playlists may be uploaded to a central audiovisual distribution server after the playlist is imported to the local device. Similarly, by way of example and without limitation, playlists may be extracted from iTunes, Windows Media Player, and/or other software applications. In many cases, such devices and/or software applications store playlists in an unencrypted and/or unencoded manner such that the playlists may be read in a manner similar to a flat text file. In this and/or other ways, the imported playlists may be made available to one or more jukeboxes connected to the audiovisual distribution network. Of course, in certain other cases, it may be necessary to decrypt, unencode, and/or perform other processing on the playlists of other hardware devices and/or software applications, prior to processing to make the now-readable playlists suitable for use, for example, on a jukebox or in connection with a jukebox-related service.
This feature may be advantageous to users in that the need to create and subsequently recreate existing playlists may be reduced, at least insofar as a single playlist may be defined on a device and subsequently used on a jukebox at a later time without a significant amount of reentering, reselection, and/or regrouping of the same information. Such techniques also provide yet a further means of interacting with and customizing the jukebox to the user's preferences, e.g., by enabling the customization of playlists through devices and/or software applications with which the user may be more comfortable and/or have more experience, have different interfaces, etc.
Thus, systems and/or methods of distributing a playlist to one or more digital jukeboxes connected to an audiovisual distribution network is provided in certain example embodiments. A peripheral device having a peripheral playlist stored in a computer-readable storage medium thereon is connected to a digital jukebox via a connector. The peripheral playlist is retrieved for the digital jukebox. This may be accomplished by programmed logic circuitry (e.g., any suitable combination of hardware, software, firmware and/or the like) provided to the jukebox. The peripheral playlist is converted to a jukebox playlist. The jukebox playlist is published at least on the jukebox. Similarly, a software application running on a computer device (e.g., a PC, a laptop, PDA, or other similar portable computing device) may be read by a computer and published to a server on the audiovisual distribution network. The peripheral device may be, for example, at least one of a portable music player, a computer, and/or a mobile phone.
The peripheral playlist may be at least temporarily stored to a computer-readable storage medium of the digital jukebox. It may be determined whether the jukebox playlist is to be designated a public jukebox playlist or a private jukebox playlist. Based on the determination, the jukebox playlist may be made publicly available or kept private to the particular registered user importing the playlist.
The jukebox playlist may be sent to a server of the audiovisual distribution network, and the jukebox playlist may be made available to jukeboxes connected to the audiovisual distribution network and/or remote devices connected to the audiovisual distribution network. The person importing the playlist may have to log into the jukebox or a portal to the jukebox before being allowed to import the playlist.
A jukebox device to accomplish the same and/or similar functionality may also be provided, wherein at least some of the functionality is enabled through the use of a processor provided to the jukebox.
In certain exemplary embodiments, it may be advantageous to prevent users from creating playlists directly at the jukeboxes using the jukebox interfaces themselves. For example, this may reduce the amount of crowding around a jukebox, monopolization of the jukebox by a single or a few users, etc. In addition or in the alternative, users may have a reduced ability to create playlists directly at a jukebox. For example, a user may be able to create a playlist from a predetermined set of songs. That predetermined set of songs may include only those songs played by the user on that particular night, at the jukebox(es) at that particular location, at any jukebox(es) connected to the audiovisual distribution network, etc. In this way, it may be possible to enable the user to benefit from the customization of playlists techniques described herein directly at the jukebox while also reducing the time required to do so. In addition, the users may be prompted to create playlists in which songs that have been played, and thus may be likely to be played again, are added.
Thus, in certain exemplary embodiments, systems and/or methods for playing instances of media on a digital downloading jukebox are provided. A user is required to log into the jukebox. A plurality of selectable instances of media are provided for play on the jukebox. User selection of an instance of media from the plurality of selectable instances of media is enabled via a user interface to the jukebox. For each user selection, the instance of media is added to a playlist stored in a computer-readable storage medium of the jukebox. The instances of media in the playlist are played in order. The plurality of selectable instances of media is selected from a master group of instances of media in dependence on a previous play of an instance of media by the user.
In certain exemplary embodiments, the plurality of selectable instances of media is formed from instances of media previously played by the user within a predetermined time period and/or from instances of media previously played by the user at a predetermined location. In certain exemplary embodiments, the plurality of selectable instances of media is formed from instances of media stored in a list of recently played instances of media associated with the user.
Once songs are added to a playlist, a playlist may be played in whole or in part. For example, if a user has enough credits, the entire playlist may be played. However, if the user does not have enough credits, the user may either enter additional payment to purchase a sufficient number of credits to play the entire playlist or may play only a portion of the song. In the latter case, the user may be prompted to select a subset of songs for play from the playlist. Alternatively, the songs from the playlist may be played in order until the credits are exhausted. Optionally, a prompt for the user to enter additional payment to play the whole playlist may be presented when appropriate, and it may removed from a display once sufficient payment has been inserted.
Also with respect to the amount users may be charged for plays, it will be appreciated that in certain exemplary embodiments, registered and/or verified users may be given “price breaks” on plays. For example, users normally may be charged a premium for selecting a song that is not currently available on the jukebox (e.g., requires a download, e.g., from the audiovisual distribution network or other source). In certain exemplary embodiments, certain preferred users may only be charged a reduced or the minimal amount of credits (e.g., only 1 credit), no matter what the source of the song. In certain other exemplary embodiments, preferred users may only be charged the minimal amount of credits if the song was recently played by the particular user. In still other exemplary embodiments, preferred users may only be charged a reduced or the minimal amount of credits if the song exists in a playlist associated with the user (e.g., a playlist the user created, a playlist created by another that the user played in whole or in part, etc.). Thus, it may be possible in certain exemplary embodiments to reward verified users by reducing the number of credits charged for certain instances of media associated with the playlists of those users.
As such, systems and/or methods of playing an instance of media on a digital downloading jukebox are provided in certain exemplary embodiments. A plurality of instances of media on the jukebox is provided. An interface is provided to a user of the jukebox to allow the user to search for a particular instance of media for play on the jukebox. It is determined whether the instance of media is available for immediate play on the jukebox free from additional processing by the jukebox (e.g., without the need for further downloading or retrieval of the instance of media beyond that which is standard for plays, without the need for non-standard searches, etc.). When the instance of media is available for immediate play, the user is charged a predetermined first number of credits and the instance of media is queued up for play. When the instance of media is not available for immediate play, it is determined whether the user is a verified user. When the user is a verified user, a second predetermined number of credits is charged if the instance of media exists in a playlist associated with the user, but otherwise a third predetermined number of credits is charged. The instance of media is queued up 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 predetermined credits.
With respect to the charges, then, in certain exemplary embodiments, the price for a normal play may be the same as the price for a premium song requiring download when the user is a registered user. In certain exemplary embodiments, the playlist associated with the user is a playlist previously created by the user, a playlist including songs recently played by the user, and/or a playlist created by another user but recently played at least in part by the user.
The determination of whether the instance of media is available for immediate play on the jukebox free from additional processing by the jukebox may include determining whether the instance of media resides on a storage area separate from a dedicated storage area of the jukebox comprising immediately playable instances of media. The separate storage area may be a remote server, a partition of the dedicated storage area of the jukebox, a separate storage area within the jukebox, etc. The determination of whether the instance of media is available for immediate play on the jukebox free from additional processing by the jukebox may include, in addition or in the alternative, determining the user's search methodology provided by the interface. For example, a premium may be charged for a “super-search” as compared to a title or artist search. Of course, these examples are provided by way of example and without limitation, and other search methodologies described herein may be provided, and the pricing may be distinguished on the basis thereof, alone and/or in combination with the type of user and/or the existence of the instance of media in a playlist associated with the user.
Here, as elsewhere, any suitable combination of programmed logic circuitry (e.g., hardware, software, firmware, and/or any suitable combination thereof) may enable such functionality. Additionally, instructions for carrying out the same may be stored on any suitable computer-readable storage medium.
Users also may browse their buddies' music collections, playlists, PickLists, etc., as shown in step S2034. Users then could develop their own playlists and/or PickLists based on what they perceive as popular amongst their friends. Users also may copy music from their buddies or send music to their buddies, preferably for a fee, as shown in step S2036. In a step not shown, users also may designate particular songs to play when their friends log in to the jukebox, again, preferably for a fee. Other features pertaining to communication between buddies will be described below with reference to
Similarly, certain exemplary embodiments provide systems and/or methods for establishing and managing a registered user's connections. A registered user may seek to establish a connection with another user or prospective contact at a jukebox or remote from a jukebox. In either case, a user may be prompted to log in. After logging in, the user is prompted to enter information about the prospective connection. This may include, for example, an email address, a mobile phone number, a physical address, a jukebox-specific messaging service, and/or the like.
Once the information is entered, a confirmation message may be sent (e.g., via the audiovisual distribution network) to the prospective contact. The confirmation message may identify the registered user (e.g., by name, login name, with a picture or avatar, etc.) and/or provide contact information for the registered user (e.g., a phone number, email address, jukebox login name, etc.). The prospective contact may determine whether a connection between the two should be established, e.g., by verifying that the prospective contact really knows who the registered user is.
In a case where the prospective contact is not already a registered user of the jukebox services, the prospective contact may be requested, and in some cases required, to become a registered user of the jukebox services itself.
After receiving a confirmation message, the prospective contact may choose whether to accept the registered user as a connection. This may be done, for example, by sending a message including an acceptance code or logging into a particular website or jukebox. For example, an email message, text message, or the like may be sent from the prospective contact as a confirmation. The acceptance code may be a particular alphanumeric code uniquely identifying the registered user and the prospective contact, or it simply may be the email address or mobile phone number of the prospective contact (e.g., sending an SMS, email, telephone call, and/or other message with a blank message, a “YES” message, an alphanumeric acceptance code, etc.). Alternatively or in addition, the acceptance code may be embedded in a hyperlink accessible by the prospective contact and/or may be accessible via a computer-based interface (e.g., a website) or jukebox interface. In still other exemplary embodiments, the prospective contact may have to log into a website or jukebox without the use of a preformed hyperlink having an acceptance code embedded therein.
Once the acceptance code is sent from the prospective contact, it may be validated, e.g., by a server in the audiovisual distribution network. The validation process may include determining whether the registered user is valid, whether the prospective contact is valid, etc. If this is successful, a connection between the registered user and the prospective contact may be established.
Once a connection is established between two people, they may communicate with each other via the jukebox and/or jukebox-related services. For example, they may send messages as described above, share credits, etc.
Each user may determine how and/when communications may be received. For example, a user may use an interface provided on a jukebox or remote to the jukebox to limit messages to a single communications medium. For example, a user may wish to only receive messages on a particular email address (even though another user has provided an alternate email address), in which case messages may be forwarded to the specified email address. In another example, a user may with to never or only be contacted by SMS messages. Still further, a user may limit the times at which messages may be received, e.g., to prevent messages from being sent too late in the evening or too early in the day (for example, which might otherwise disturb the user). In such cases, the messages may be queued at a jukebox or at a server for later delivery. Users additionally may specify that they will not accept any incoming connections unless specified in an access control list. Thus, it will be appreciated that communications among connections may be managed and/or filtered, for example, to specify when, to where, and from whom they may be received, etc. A registered user can then use the connections list to communicate with the parties in the list using the jukebox or remote device that can access the jukebox network, such as by logging on to the network using a personal computer or the like.
It is to be appreciated that although the above-described exemplary MyTouchTunes system has been described in terms of a broad concept for making accounts available on any compatible system, other exemplary embodiments are contemplated where accounts may be made available to smaller subsets of jukeboxes, including, for example, a single jukebox terminal acting in isolation. Furthermore, a large group may act as if it were one system in isolation, or, alternatively, it could have complete knowledge of all user accounts/profiles, locations, etc.
Preferably, a successful log-on displays a main menu for users.
Users can manage a buddy list by adding a buddy by pressing add buddy button 2314. Alternatively, they can remove a buddy by pressing remove buddy button 2316. Users also can communicate by sending messages to their buddies by pressing send message button 2318. This feature can, in certain embodiments, for example, send SMS messages to mobile devices, send e-mails, send messages to appear when the recipient user next logs-in, etc. In still other embodiments, users can, for example, use this feature to send songs, donate credits, etc. Indicator area 2320 shows that the current user has received one message, and it identifies the sender. In other embodiments, however, other information may be displayed, a more complete inbox (e.g., with folders, forwarding, etc.) may be provided, etc. Credit indicator area 2322 provides account status. In this embodiment, it indicates that the user has previously purchased 20 plays online, and has entered enough money in a local jukebox terminal for 5 additional plays, for a grand-total of 25 potential plays.
Another aspect of the instant invention relating to improvements in background music will now be described. The local server and Tune Central feature described herein, open up a whole new world for background music on a jukebox. Currently, when no paid for music is queued, jukeboxes may play background (ambiance) music with the help of an auxiliary system connected to the jukebox, such as DMX or satellite radio. Alternatively, if they play background music with their own music, they are limited to the songs available for play on the jukebox, typically about 2000 songs. These songs are also available for selection by jukebox patrons. Conventional digital jukeboxes are typically connected to a remote network through the internet for accessing extended music. These applications are therefore not well suited for providing background music services other than the music locally available as this would require constant download or streaming from the remote servers for the background music.
However, jukeboxes equipped with an external server or large music partition (such as Tune Central described herein) can select background music to play from that large pool of songs, even if the song is not available for play through the standard interface. This permits a vast musical variety for background music using jukeboxes. The background music selection can be made automatically by the jukebox randomly or with an advanced algorithm that selects music based on genres, themes, era or other criteria. Also, background music lists can be preprogrammed by a disk jockey or the like (background playlists) and sent from a central server to jukeboxes. Since music rights can differ for songs available in pay-per-play mode and background music, there is, in an embodiment of the invention, an indicator for each song or song aggregations (e.g., all songs from ABC record label) allowing the jukebox to distinguish between songs that can be played as background music (as opposed to normal jukebox play) based on the availability of the proper music rights, thereby enabling proper royalty accounting as well. In an embodiment of the invention, the jukebox offers advanced options for allowing an operator to configure how background music will be performed, based on genre, themes, indicators (flags), such as billboard hit, Christmas music, playlists (e.g., DJ John—summer 2005), etc. In another embodiment of the invention, the operator configures the jukebox to allow the bartender to further configure the background music mode through, for example, a remote control; much like the bartender would select a radio station in prior background music systems. This mode offers genres or theme based music or playlists for enhancing background music functionality. The operator can, for example, configure which genre, theme or playlists is available to the bartender. In addition, a remote control with programmable keys combined with suitable software can be provided to allow the bartender (or other person) to select (e.g., for a particular zone) a certain background music play list or TV audio input for special event like, for instance, a football game in a bar zone, thereby providing convenient and effective background music services and other services through the jukebox device.
Thus, similar to the background music services, “channels” of music may be provided. A proprietor of a location may select a channel to play. A list of channels may be defined by the location and/or defined by the content provider (e.g., the jukebox provider). In certain exemplary embodiments, channels may correspond to the themes or genres of music already provided to the jukebox (e.g., rap, rock, country, etc.). In addition or in the alternative, the proprietor of the location may group songs together to form custom channels for or at a particular location or group of locations, and/or shareable between many potentially unrelated or unassociated jukeboxes (e.g., as a sort of public channel). The thousands of songs provided to the jukebox may be played in a coherent grouping as background music, for example, through this channel feature. For example, a predetermined amount of time after no money has been inserted into the jukebox and/or after all songs in the queue have been played, a channel of music (e.g., selected by a proprietor, manager, etc.) may play. The channel may be activated in this illustrative case substantially free from direct user input, for example, so that the switching from normal jukebox operation to background mode is substantially transparent to the normal patrons and/or authorized users (e.g., managers, proprietors, etc.) of the jukebox. Of course, it will be appreciated that authorized users of the jukebox may also cause the jukebox to change from normal operation mode to a channel mode and vice versa, control the switching of channels, choose between channels, etc.
Numerous advantages are provided by this feature. For example, no auxiliary source of media is required to play instances of media provided to the jukebox, thereby reducing the need for, for example, satellite radio, broadcast radio, CD players, and/or other equipment (e.g., in addition to or in place of the jukebox), some of which may require additional costs in terms of hardware and in terms of monthly subscription fees. Rather, a jukebox channel may provide hundreds or even thousands of instances of media playable directly from the jukebox. In this way, numerous different channels of background music can be provided on the jukebox using the music stored in the jukebox or available on the network. The available channels can then be selected by an authorized person using, for example, the remote control provided with the jukebox. The various channels could also be displayed on the jukebox on request, so that a channel can be selected from the list.
Furthermore, unlike traditional broadcast and enhanced satellite radio channels, a jukebox patron may exercise control over the content of a particular channel by more than simply tuning to a new channel. For example, an authorized user (e.g., a proprietor, manager, etc.) may use a jukebox remote control to skip songs, replay songs, remove songs from the channel, add songs to the channel, etc. Currently, this functionality is not possible in connection with broadcast or satellite radio channels. The jukebox channel optionally may learn from this control behavior and, similar to a ratings system, may adapt the channel to more frequently play popular songs, less frequently play skipped songs, etc.
Still further, jukebox channels are not subject to the same kinds of physical problems associated with traditional broadcast and satellite radios. For example, whereas a satellite radio may be inoperable during bad weather conditions, a jukebox channel may function substantially independent of the outside conditions. Similarly, a jukebox channel is not subject to the same kinds of geographical restrictions associated with the antennas of traditional broadcast channels, in that, for example, a jukebox channel may be played wherever there is a jukebox. Indeed, a jukebox channel does not even require the presence of a persistent or establishable internet connection, although it will be appreciated the same may be advantageously used in connection with certain exemplary embodiments where it is desirable to having streaming media, updatable channels, etc.
Thus, certain exemplary embodiments provide systems and/or methods of operating a digital downloading jukebox. A plurality of channels is defined, with each said channel having a plurality of instances of media associated therewith. A channel is selected from the plurality of channels on the part of an authorized user. One or more patron uses of the jukebox is responded to in a first mode, with at least some of said uses including adding instances of media to a queue for play on the jukebox and playing said queued instances of media. When the jukebox is not responding to a patron request and/or playing a queued instance of media, the instances of media in the channel are played in a second mode. The first mode is different from the second mode, and the second mode is not directly controllable by a patron of the jukebox. In certain exemplary embodiment, the second mode may be a background music mode (e.g., such that the music is played at a lower volume, etc.).
In certain exemplary embodiments, the instances of media may be associated with channels by an authorized user and, in addition or in the alternative, the instances of media may be associated with channels according to a theme and/or genre (e.g., rap, rock, country, etc.) associated with each said instance of media.
A frequency an instance of media in a channel is played may be changed in dependence on one or more control codes received from the authorized user. The control codes may correspond to at least one of: skipping an instance of media being played by the channel, replaying an instance of media being or having just been played by the channel, and removing an instance of media from the channel.
Here, as elsewhere, any suitable combination of programmed logic circuitry (e.g., hardware, software, firmware, and/or any suitable combination thereof) may enable such functionality. Additionally, instructions for carrying out the same may be stored on any suitable computer-readable storage medium.
Step S2404 determines whether the user is recognized by the system as an existing user. Users not recognized by the system preferably will be prompted to create an account, as in step S2408. Users may be required to supply, for example, their names, ages, e-mail addresses, etc. Preferably, users will be able to create profiles including, for example, a name and/or nickname, their age, their location, and an associated image. These profiles may be viewable by other users of the system. In some exemplary embodiments, users may be required to register and/or create profiles before participating in some features of the system, for example. Alternatively, in other exemplary embodiments, users may specify that they want their information, or portions thereof, to remain private. A non-limiting exemplary screen shot for editing account information is provided in
If users are recognized in step S2404, they may chose a feature and/or service in step S2406, described in more detail in relation to
In step S2502, a user may search for music. Preferably, a user may specify search fields, alone or in combination, such as, for example, artist, song, album, genre, etc. An exemplary screen shot showing the results of a search is provided in
In step S2504, a user may manage the user's playlists. An exemplary screen shot showing how a user might manage playlists is provided in
A user may purchase music in step S2506. In one exemplary embodiment, a user may order a single song, a plurality of songs, an entire album, or multiple albums. In some exemplary embodiments, a user may have his order shipped, while in other exemplary embodiments licensed digital copies may be made available. In still other exemplary embodiments, it may be possible to purchase music and download it directly to a media playback device (e.g. an appropriately configured PDA, cell phone, or the like).
Preferably, a user could communicate with others via e-mail and/or text messages in step S2508. Step S2508 preferably also will allow users to participate in online forums and live chat rooms. Messages sent through this step may be delivered to conventional e-mail inboxes, cell phones, etc. Additionally, messages may be displayed on jukeboxes, for example, when recipient users initially log-in, when messages are sent and/or received, etc. It will be appreciated that online forums and chat rooms may use protocols, such as, for example, newsgroups, Network News Transfer Protocol (NNTP), Usenet, Internet Relay Chat (IRC), etc., or they may use custom protocols.
From time-to-time, proprietors or the managers of the system may sponsor contests, promotions, or giveaways. Users may participate in such activities through step S2510. For example, a proprietor might allow anyone who prints a coupon to avoid a cover charge. As another example, there might be a competition for the best playlist. It will be appreciated that these example promotions are for illustrative purposes only, and that other contests, promotions, giveaways, or the like may be possible.
In step S2512, a user may edit that user's profile. The discussions of step S2408 from
The Find a juke button preferably enables a user to search for a location with a jukebox. Users may, for example, search for locations near a certain address, in a particular city to which the user may be traveling, locations that offer special features (e.g. drink specials, guest DJs, etc.), locations likely to play music the user likes (e.g. a bar with line dancing might be appropriate for a country music fan, etc.), etc. Social networks also may be built based on postal codes, schools (e.g. high schools, colleges, universities, etc), etc. In a preferred embodiment, when a user finds a specific location, the user may have custom information, for example, directions, custom maps, hours of operation, parking information, etc. displayed. It will be appreciated that because jukeboxes located at many locations preferably are connected to the system and that users' playlists preferably are accessible by the system, users may receive recommendations likely to fit their tastes. For example, the system might suggest a specific bar to users of a certain age in the same town who are known to like a specific type of music. In certain example embodiments, the jukebox can recommend that users form certain connections. These suggested connections between patrons (and thus potential “buddies”) preferably may be based on information known to the jukebox though not necessarily known to other users. Such information can include, for example, venues frequented, musical tastes, ages, etc. In certain example embodiments, therefore, users may be connected based on where they go, not necessarily where they are from.
Similarly, a jukebox locator service may be provided, and it may exist on a jukebox, via a webpage, through the MyTouchTunes web and/or jukebox interface(s), etc. The jukebox locator service may receive user input and search accordingly. For example, a user may specify an address or portion thereof (e.g., city, state, and/or zip code), may search by name or keyword, or may search for specially enabled jukeboxes. A map may be displayed, with each matching location being highlighted. Additional information may be displayed for a given location. Such additional information may include, for example, the name and address of the location and/or any other details about the location. For example, the songs most frequently played may be displayed, as may be certain promotional offerings, DJs being present, etc.
Additional search criteria may be entered initially or to refine a search. Such additional search criteria may include the user's age, musical tastes, preferred theme (e.g., Irish bar, country line dancing, etc.), etc. Alternatively, the jukebox locator service may conduct a basic search using only the criteria entered by the user and may then highlight recommended locations based on, for example, information already known about the user, such as, for example, the above-mentioned additional search criteria.
Users may enter search terms in search field 2610. Additionally, users may further limit their searches by searching only in one of the categories listed in search parameters list 2612. It will be appreciated that the fields of search parameters 2612 are for illustrative purposes only—other fields may be present in addition to, or in place of, those listed, such as, for example, year, popularity, etc. A user may conduct the search by pressing search button 2614. Users may alternatively search by filling in search field 2616 and selecting a search parameter from the list of search parameters in search parameters dropdown list 2618. The results of a search may be displayed according to
A non-limiting exemplary list of genres is given in genre list 2620. It will be appreciated that other genres may be present in genre list 2620, and it also will be appreciated that, in this exemplary embodiment, additional genres may be accessed by clicking the “More . . . ” button in genre list 2620. A user pressing a specific genre may receive content tailored to that genre. For example, pressing the “Alternative” genre may, for example, present a list of the most popular alternative albums, a list of forums dedicated to the discussion of alternative music, etc.
Most popular albums list 2622 contains information related to the most popular albums and preferably displays the album cover, the artist name, and the name of the album. Most popular album list 2622 may be generated in any number of ways. For example, Most popular album list 2622 may be based on preferences of users of the system, commercial data regarding album sales, album sales within a particular geographic segment, etc. Preferably, most popular album list 2622 may be changed depending on the genre selected from genre list 2620.
Users may access community-specific content by selecting a specific communications method from communications methods 2624. In this exemplary embodiment, users may communicate in groups and/or forums. It will be appreciated that participation in groups and/or forums may require registration, and that groups and/or forums may be designated public or private. Preferably, groups will comprise users, for example, with similar interests, in near locations, etc. For example, there may be a group for so-called “Dead Heads” to allow them to plan meet-up points, transportation, etc. for upcoming tours of the Grateful Dead. Forums may function similarly, though they preferably will be more static, allowing threaded messages between users.
Breadcrumbs trail 2626 provides a convenient way for navigating through the system. Specifically, breadcrumbs trail 2626 traces the path a user takes in accessing a certain page. Pressing a specific part of breadcrumb from breadcrumbs trail 2626 preferably takes the user to a corresponding location.
Information area 2628 and information area 2630 may be customized to provide additional information to the users. In this exemplary embodiment, information area 2628 suggests reasons for using specific features (here, creating custom playlists), and information area 2630 provides useful tips (here, relating to how to create a custom playlist). It will be appreciated that information areas 2628 and 2630 may change depending on, for example, the user, the time of access, the number of times a user has accessed a given page, etc. Furthermore, it will be appreciated that information areas 2628 and 2630 may contain different information not related to use of the system, such as, for example, advertisements, promotions, etc.
User playlists 2640 displays the playlists the user has created and/or imported. It will be appreciated that user playlists 2640 will be empty if a user has not created or imported any playlists. Preferably, the exemplary embodiment will display the unique name specified by the user for each of the playlists. Users may expand one or more specific playlists from user playlists 2640 to show the songs associated with the playlist. In the example shown in
Preferably, the system will display at least one recommendation 2644. The recommendation preferably will include an album cover, a song name, artist information, and keywords associated therewith. The recommendation preferably will be generated automatically, and may be based on a variety of data. The data for generating a recommendation may include, for example, user demographic data (e.g. age, gender, race, etc.), the number and types of songs in the user's playlists, songs the user has purchased through the system, popular songs, etc. Preferably, the system will allow the user to quickly add the recommended song to a playlist by pressing add button 2646.
The username selected in the initial account setup is displayed as username field 2670. Preferably, a user will not be able to change username field 2670 after initial setup, and, preferably, each username will be unique. The user may enter an e-mail address in e-mail address field 2652. In a preferred embodiment, the system will send important e-mails (e.g. terms and conditions information, notices of giveaways, bills, etc.) to this e-mail address. A real name may be specified in name field 2654. Although this exemplary embodiment shows name field 2654 as a single field, it will be appreciated that multiple fields may instead capture the same information (e.g. fields for first and last names; first, middle, and last names; etc.). A user may choose a gender from gender options 2656.
A location may be specified in location field 2658. Although this exemplary embodiment shows location field 2658 as a single field, it will be appreciated that multiple fields may instead capture the same or additional information (e.g. fields for city and state; city, state, and zip code; city, province, and country; etc.). A date of birth may be specified in date of birth field 2660. Although this exemplary embodiment shows date of birth field 2660 as three fields, it will be appreciated that a single field or multiple fields in a different order may instead capture the same or additional information (e.g. one field for month, date, and year; month and year only; month, date, and year; etc.).
A user may enter personal or other information in free-form biography field 2662. Additionally, a user may specify a signature line or tag line in forum signature field 2662. Preferably, the system would automatically append the contents of forum signature field 2662 to users' posts to groups and/or forums. A user may upload a picture or icon by entering a file location in picture field 2666. Preferably, this picture would be displayed on login and/or when a user posts a message to a group or forum.
In a preferred embodiment, required fields may be, for example, marked with an asterisk (*), highlighted, or otherwise designated. In other embodiments, a user may additionally store purchase information, such as, for example, credit card information, billing and shipping addresses, etc. This information could be used, for example, if users decide to order or download songs, albums, or other merchandise, to automatically debit an account so that users could “play now and pay later” while using jukeboxes in bars and/or clubs, etc.
Playlist manager button 2668 provides quick access to the playlist manager form, discussed in more detail below in connection with
A user may create a new playlist by pressing create new playlist button 2678. Preferably, the user will be prompted to enter a unique name for the new playlist. Then the user may edit the playlist in the above-described manner. Users also may share playlists by pressing sharing button 2680. Sharing button 2680 allows users to designate their playlists as public to allow other users to retrieve their contents, preferably allowing users to drag and drop selected playlists into categories, such as, for example, public, private, etc. Correspondingly, users may search for playlists created by other users, prepared by DJs, etc. and then copy and/or import the playlist. Users may delete playlists by pressing delete playlist button 2682 to display list of playlists 2684 and then selecting the playlist to delete from the list of playlists 2684.
Although not reflected in
Users may be billed according to billing information they inputted. For example, a stored credit card may be charged whenever a song is downloaded via the jukebox interface. As another example, a user may setup a special jukebox-specific account, linked to, for example, a Pay-Pal account. In a related aspect, users may use their cell phones (or other suitable portable devices) to purchase media, register with the jukebox, etc. by exchanging codes (e.g. via SMS messages) with the jukebox. For example, a user may first identify himself or herself with the jukebox (e.g. may login on the jukebox or remotely through a mobile device). Depending on whether the user's cell phone number (or e-mail address, etc., depending on the implementation), the user may have to enter the appropriate information. An SMS (or appropriately similar) authorization message and/or code may be sent to the user. The user may then enter that code on the jukebox to begin purchasing music, creating personalized content, accessing features available to recognized users, etc. This method of communication also may in some example embodiments enable users to pre-verify and/or pre-pay for music purchases remotely.
Using a mobile device, the user logs into the jukebox system in step S2806 and selects the song to purchase in step S2808. The use of a mobile device allows for quick and convenient “impulse” purchases. In some embodiments, the choice of what song to purchase might be automated, for example, by selecting the song currently playing at a given location, the song currently playing on a certain radio station, the song just played at a given location, etc. The user may specify purchase parameters in step S2810, such as, for example, how to pay for the song, the device to which it should be downloaded, etc. In step S2812, the song is delivered to the user via the jukebox interface. It will be appreciated that the song may be delivered to other devices, such as, for example, a particular jukebox, a portable media device, a laptop, a home computer, etc.
Mobile devices 26a-26d may communicate through an external network to communicate with jukebox 16 having communicator 25. It will be appreciated that mobile devices 26a-26d may communicate over a LAN, wireless Internet, Bluetooth, or any other suitable communications network.
Preferably a central database of recognized user information is maintained and accessible by each of the jukebox devices 16, 16a-f and remote devices 26a-d. However, in some exemplary embodiments, local databases of recognized user information may be maintained on devices. Preferably, the devices will communicate with each other through a communications network, such as, for example, the Internet. However, it will be appreciated that other communications methods are possible, such as, for example, through wired communications over a LAN, wireless communications, etc.
Remote devices 26a-c allow users to login to jukebox 16 remotely, without having to access jukebox 16 and user interface 24 directly. Thus, a user can, for example, play songs, edit playlists, and perform other jukebox-related activities without using user interface 24 directly. It will be appreciated that remote devices 27a-c may have their own user interfaces, which may be the same as or different from user interface 24. User profile information may be stored locally on jukebox 16, on a remote server (not pictured), or on a remote device 27. Preferably, a change made by a remote device (e.g. to user profile information, playlist contents, purchased media, etc.) would be mirrored on jukebox 16, any other associated remote devices, and/or on other jukeboxes, etc.
After a registered user receives a notification regarding a get-together, the registered user may participate in that event, as in step S3006. This step might involve attending a bar, event, social event, or the like. In step S3008, the registered user becomes a verified user. This step might require the user to log onto a jukebox during the get-together. Alternatively, registered users might receive vouchers, codes, or the like to later enter into a jukebox (locally or remotely) to change their status to verified. In certain other embodiments, registered users may drop their business cards, sign lists, or otherwise indicate their presence to have their status changed for them. Thus, In step S3010, a user may have privileges granted, access rights changed, etc. based on verified status. For example, a verified user may be gain access to certain groups/discussion forums for verified users only. Verified users also may, in certain exemplary embodiments, make un-moderated postings. In certain other exemplary embodiments, verified users may be able to access special promotions not available to other users.
One such special promotion may include the ability to send messages (e.g., SMS messages, email messages, picture messages, etc.) to registered users' mobile phones. In certain exemplary embodiments, the coupons for one or more free credits may be sent to registered users. The coupon itself may come in many forms. For example, a simple message may be provided to show to an authorized person at a location (e.g., a bar manager, proprietor, etc.). The coupon may also include a special validation code, for example, to help reduce the chances of free credits being given away erroneously. The validation code could be shown to an authorized person or could be entered directly into a jukebox. The code could be validated against a database of codes located on the jukebox or remote from the jukebox. The database could be updated (e.g., the validity of the coupon may be revoked so as to prevent further use(s) of the same coupon, etc.) after a coupon is read. Alternatively or in addition, the code may be created according to a self-checkable format such that a database does not need to be consulted (e.g., the code itself may be encoded with the number of credits and/or additional information according to a predefined format which may or may not be readily determinable by a casual observer).
The validation code may also include a location code that indicates that the coupon is only good for a particular location or group of locations. As an example, a coupon may be provided for plays on all jukeboxes at all locations owned by a single person. Similarly, the validation code may also include a time expiry code, such as, for example, a number of days or an absolute date and/or time in which the recipient of the coupon must redeem the coupon. For example, the code may be good for use within 1 week, only on certain days, etc.
Separate from or in addition to a simple message and/or validation code, the coupon may be provided in the form of a barcode scannable by the manager and/or at the jukebox using appropriate hardware. The coupons may be delivered, for example, as text messages, through the regular mail, through email, etc. In certain exemplary cases, whether the coupon includes a barcode or in another format, it may be necessary to print out a coupon for redemption at a location, whereas in certain other exemplary cases it may be possible to merely bring the mobile device that has received the coupon.
Thus, certain exemplary embodiments provide systems and/or methods of delivering a coupon to a user of a digital downloading jukebox. A validation code is created. Associating with the validation code is a number of free credits for the user. Note that no specific number necessarily need be included in the validation code—for example, the existence of the coupon itself may be good for a predetermined number of credits (e.g., 1 credit, 5 credits, 10 credits, etc.). The validation code is included with the coupon. The validation code is transmitted to the user.
Included in the validation code may be at least one location where the user can redeem the coupon and/or a restriction on the time when the user can redeem the coupon. The validation code may include an encoded alphanumeric sequence and/or a barcode. The coupon feature could also be used for coupons that provide discounts on food, drink and/or other products/services offered by a jukebox establishment.
In certain exemplary embodiments, the validation code may be obtained from the coupon. It may then be determined whether the validation code is valid. When the validation code is valid, a number of credits is/are provided to the user in accordance with the number of free credits associated with the validation code. The validation code may be obtained by the jukebox via a barcode scanner, and/or a user may have to input the validation code into the jukebox via a user interface provided to the jukebox. Alternatively or in addition, an authorized user of a jukebox (e.g., a manager, proprietor, etc.) may provide the free credits to the patron.
Here, as elsewhere, any suitable combination of programmed logic circuitry (e.g., hardware, software, firmware, and/or any suitable combination thereof) may enable such functionality. Additionally, instructions for carrying out the same may be stored on any suitable computer-readable storage medium.
In step 3206, jukebox users may access public playlists and songs as part of their normal jukebox activities. The jukebox monitors user activity, especially with respect to the songs and playlists accessed. In certain exemplary embodiments, the jukebox will maintain counts, percentages, and the like related to the songs and playlists accessed. The jukebox will reward users based on the accessions of other users in step S3210. For example, users may be rewarded if their playlist(s) is/are accessed the most of any playlist, is/are accessed above a certain threshold number of times, is/are selected more than other playlists in a predefined category, etc. In certain exemplary embodiments, users may be rewarded based on the contents of their playlists. For example, users may be rewarded based on whether their playlists contain a predefined number and/or proportion of the most popular songs, as determined by the jukebox. It will be appreciated that users may be rewarded in any number of ways. For example, one obvious way users may be rewarded is by giving them credits for additional plays on the jukebox. Users also may be rewarded by being entered in certain promotions, giveaways, or the like. More generally, a recognized user may earn reward points for conducting arbitrary jukebox-related activities (e.g., on an actual jukebox, via a web interface, etc.). For example, a recognized user may earn points every time the user logs on, sends a message, shares a playlist, etc. Reward points may be redeemed, for example, to purchase plays on a jukebox. Alternatively, points may be redeemed for special merchandise to promote the further use of the jukebox by the recognized user.
Optionally, a user may choose an avatar to represent the user on a jukebox and/or in any other jukebox-mediated environment. A user's avatar may be depicted graphically, for example, as a picture, as a moving animation, as a character, or in any other way suitable for identifying the user. The avatar may or may not bear a physical likeness to the registered user.
In one example, when a person operating a jukebox selects the local playlists option from a jukebox, the playlists for each registered user on the jukebox may be made available. This example is depicted in
If the playlist, or a portion thereof, is selected for play by the user, a now playing screen may be displayed, as shown in
These and/or similar features may be provided by allowing the registered user to upload content (e.g., video and/or audio content) to the jukebox and/or jukebox distribution network. For example, pictures, audio files, movies, and the like may be captured by and/or stored to a single jukebox and associated with a registered user on that jukebox, or may be stored to a central location so as to be available to multiple jukeboxes.
It will be appreciated that these and/or similar features may be provided in a networked jukebox environment so that registered users may have access to their avatars from anywhere. This may be useful when traveling, for example, back to a hometown, university, and/or other place that the user may visit later, for example. In this way, the avatar may be familiar to other patrons who once knew the registered user. It also may be helpful to registered users on the go, who wish to be creative (e.g., to make new friends) or to introduce themselves (e.g., through introductory audio and/or video clips), while also having access to the user's own library of music, etc.
Avatars and media presented by avatars may be forced to comply with local filters applied to the jukebox. For example, playlists may be filtered if a location does not permit rap, pre-recorded messages may be edited for explicit language, inappropriate pictures may be altered, etc.
As described above with reference to the MyTouchTunes services, suitably configured jukeboxes may facilitate users' connections with various virtual communities, including, for example, communities of interest (e.g., organized around a specific subject), communities of fantasies (e.g., around gaming, creative environments, or the like), and/or communities of relationships (e.g., online meeting spaces). Accordingly, the jukeboxes may provide—either directly or through an online portal—one or more of electronic mailing lists; online chat rooms; bulletin boards, message boards, discussion groups, Internet forums, or the like; blogs; instant messaging services; podcasts; text messaging services; file sharing (e.g., P2P file sharing); multi-user dungeons (MUDs); etc. By connecting with and establishing new jukebox-centered virtual communities, it may be possible to attract new patrons and develop further interest of existing patrons. Indeed, it may be possible to realize increased returns in and through the virtual community by gathering information about members (and targeting advertising and transaction offerings appropriately), drawing vendors to the community to attract members and promote spending, drawing members to the community and generating member-based content, and/or promoting user-to-user interactions to build user loyalty to the community.
The above-described avatars may be used connection with a jukebox-mediated virtual community. For example, avatars may be associated with all actions a user takes within the community (e.g., writing a blog, posting on a bulletin board, sending a message, etc.). As a further, avatars may become more interesting as users begin to create and share their own media. A user may upload music (e.g., pursuant to a standard license agreement), with the avatar being virtually “attached” to or associated with the media. The jukebox-mediated network could track the distribution of the music to websites, P2P file sharing engines, and/or jukeboxes. Royalties may be tracked and returned to the user through its avatar. Additionally, based on the type of user, different fees/royalty structures may be provided. For example, for independent artists, a large fee and small royalty may not be appropriate, whereas an artist associated with a major record label may be more able to bear such direct and indirect costs. To facilitate control, music may be checked for copyright compliance, and this authorization process may be performed automatically (e.g., a comparison to banks of known music, checking for the presence of a digital watermark, etc.) or manually (e.g., by an authorized user, patron, operator, employee of the central distribution network, etc.). When content is posted and/or agreements are ratified, an avatar may be an acceptable form of digital signature attached to a copyright and/or license agreement. An avatar also may be displayed as album art, during the actual playing of a tagged song, etc.
In addition to the above-described toolkit usable by operators, operators, authorized users, and/or proprietors also may make use of a configuration dashboard to administer, manage, update, and/or otherwise control jukeboxes. Indeed, operators managing one or more jukeboxes may save time and/or money by remotely accessing diagnostic and/or management features provided to the jukebox. In certain exemplary embodiments, an operator may be able to access a management and/or diagnostics module of the dashboard using, for example, a computer, handheld device, or other suitable device to receive notifications and/or to inquire into the status of a jukebox through a proprietary (e.g., web-based) interface. Communications may be bidirectional, thus allowing operators to directly instruct and/or query jukeboxes of interest regarding management features and/or alerts and/or notifications. The features described below may be used alone or in various combinations to allow operators, authorized users, and/or proprietors to focus on particular jukeboxes in need of attention, thus saving time and money, while also increasing the up-time, reliability, and overall appeal of jukeboxes.
With respect to such features, each jukebox may gather and/or monitor information in which an operator would be interested, potentially proactively sending this information to the operator. A notification mechanism may send messages (e.g., via email, SMS, or other suitable format) to the operator automatically when predetermined thresholds are exceeded. These predetermined thresholds may be set by the operator, may be preconfigured, etc.
Diagnostics and/alerts may include, for example, the bill rejection rate (e.g., in terms of percentage and/or number), number of bills in the stack, number of reboots, temperature (e.g., hard drive, CPU, system, enclosure, etc.), and the like. Additionally, such alerts/notifications may be set to be sent at a predetermined time. For example, notifications may be sent when the CPU temperature exceeds a threshold for a specified amount of time, when the number of reboots exceeds a threshold within a specified amount of time, etc.
It will be appreciated that such diagnostic techniques may be made available to operators located remote from a jukebox, as well as directly at a jukebox. Furthermore, in certain exemplary embodiments, the diagnostic module of a first jukebox may be used to remotely check the diagnostic module of a second jukebox, the second jukebox being located remote from the first jukebox.
An enhanced scheduling module also may be provided to the jukebox. This module may allow operators and/or other authorized jukebox users to schedule single and/or recurring events. For example, a bar owner may schedule morphs, music filters, and/or background music. The event recurrences may be weekly, monthly, yearly, etc. For example, background music may be played during bunch, music filters may be applied during the afternoon and early evening, and an unrestricted playlist may be made available at night. As another example, the jukebox may morph nightly to accommodate an 80s music night, hip-hop night, country line dancing night, disco night, etc. Such advance setup ultimately may save time and improve convenience. The events scheduler may include monthly and/or daily views, with the daily view being broken down, for example, by hours. After a new event is added, the appropriate views may be updated.
The “schedule this setting” button 3808 may bring up the calendar scheduling component, just as in any other event scheduling.
Operators also may setup sub-user accounts, with such sub-users having restricted location access.
Other functions may include enhanced location setup features.
The present disclosure has used certain terms that should not be interpreted as limiting the invention to a particular embodiment, hardware components and configurations, software configurations, etc. For example, many features and examples have been described in relation to their existence within a bar, pub, or other environment. However, it will be appreciated that the features present in the exemplary embodiments of the present invention are adaptable for use in any location where a jukebox (or multiple jukeboxes) may be located. Similarly, while certain features and functions are described with reference to usage by “users,” “owners,” “operators,” “patrons,” etc., it will be appreciated that these terms are generic and may, in most cases, be used interchangeably depending on the embodiment chosen and the feature employed. For example, while it may be advantageous to limit the initial song selection to owners and/or operators, in certain exemplary embodiments, patrons may play a role in the initial song selection.
Still further, particular hardware combinations and configurations are disclosed which represent only one way which the embodiments may be constructed. Central servers may, in some exemplary embodiments, be comprised of one or more servers acting together or separately to coherently provide the full range of services necessary to enable a functioning jukebox. For example, a cluster of servers may comprise a virtual central server, with one server providing media, another tracking membership, still another processing licensing, etc.
Similarly, the local servers described herein may be incorporated into the jukeboxes. For example, the local servers may appear to function independently, even though they exist as part (e.g. partition) of an integrated mass storage device within the jukebox. Indeed, as hard disks become larger and less expensive, they may preferably serve the functions of local servers. One presently preferred embodiment comprises a 120 GB hard drive containing 25,000 songs as the factory drive. However, flash media or any storage media now known or later developed (or combinations thereof) may be used as the factory drive, expanded media storage or local server, depending on the desires of a system designer for a particular jukebox application. In other words, the invention is not limited to any particular storage technology or configuration, but instead can be implemented using any suitable storage technology.
Also, although the term “song” has been used sometimes in the above-description, this term is not intended to be limiting to the scope of the invention, and any instance or instances of media (e.g., song, video, song/video combination, data, information etc.) can be used in any embodiment herein and still fall within the intended scope of the invention.
Lastly, it will be appreciated that the screen shots and software arrangements presented herein are only one preferred method for organizing and displaying the features disclosed herein. Other configurations are possible and are therefore contemplated herein.
While the preferred aspects of the invention have been illustrated and described herein, it will be apparent to one of ordinary skill in the art that various changes and/or modifications can be made. Thus, the specific description herein is meant to be exemplary only and is not intended to limit the invention beyond the terms of appended claims.
This application is a continuation of application Ser. No. 11/902,658 filed Sep. 24, 2007, which is a continuation-in-part of application Ser. No. 11/727,391 filed Mar. 26, 2007, now U.S. Pat. No. 7,822,687 issued Oct. 26, 2010, which is a continuation-in-part of application Ser. No. 11/358,721 filed Feb. 22, 2006, now U.S. Pat. No. 8,332,895 issued Dec. 11, 2012, which is a continuation-in-part of application Ser. No. 11/222,036 filed Sep. 9, 2005, now U.S. Pat. No. 8,151,304 issued Apr. 3, 2012, which is a continuation-in-part of application Ser. No. 11/185,974 filed Jul. 21, 2005, now U.S. Pat. No. 8,103,589 issued Jan. 24, 2012, which is a continuation-in-part of application Ser. No. 10/661,811 filed Sep. 15, 2003, now U.S. Pat. No. 9,646,339 issued May 9, 2017, which claims priority on provisional patent Application No. 60/410,832, filed Sep. 16, 2002, entitled “Digital Downloading Jukebox System With Central And Local Music Servers,” the entire disclosures of which are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3710137 | Stephens, Jr. | Jan 1973 | A |
| 3807541 | Kortenhaus | Apr 1974 | A |
| 3982620 | Kotenhaus | Sep 1976 | A |
| 4008369 | Theurer et al. | Feb 1977 | A |
| 4064362 | Williams | Dec 1977 | A |
| 4186438 | Benson | Jan 1980 | A |
| 4232295 | McConnell | Nov 1980 | A |
| 4335809 | Wain | Jun 1982 | A |
| 4335908 | Burge | Jun 1982 | A |
| 4336935 | Goldfarb | Jun 1982 | A |
| 4356509 | Skerlos et al. | Oct 1982 | A |
| 4369442 | Werth et al. | Jan 1983 | A |
| 4375287 | Smith | Mar 1983 | A |
| 4412292 | Sedam | Oct 1983 | A |
| 4413260 | Siegel et al. | Nov 1983 | A |
| 4521014 | Sitrick | Jun 1985 | A |
| 4528643 | Freeny | Jul 1985 | A |
| 4558413 | Schmidt | Dec 1985 | A |
| 4572509 | Sitrick | Feb 1986 | A |
| 4577333 | Lewis et al. | Mar 1986 | A |
| 4582324 | Koza | Apr 1986 | A |
| 4588187 | Dell | May 1986 | A |
| 4593904 | Graves | Jun 1986 | A |
| 4597058 | Izumi | Jun 1986 | A |
| 4636951 | Harlick | Jan 1987 | A |
| 4652998 | Koza | Mar 1987 | A |
| 4654799 | Ogaki | Mar 1987 | A |
| 4658093 | Hellman | Apr 1987 | A |
| 4667802 | Verduin et al. | May 1987 | A |
| 4674055 | Ogaki et al. | Jun 1987 | A |
| 4675538 | Epstein | Jun 1987 | A |
| 4677311 | Morita | Jun 1987 | A |
| 4677565 | Ogaki | Jun 1987 | A |
| 4696527 | Ding et al. | Sep 1987 | A |
| 4703465 | Parker | Oct 1987 | A |
| 4704725 | Harvey et al. | Nov 1987 | A |
| 4707804 | Leal | Nov 1987 | A |
| 4722053 | Dubno | Jan 1988 | A |
| 4761684 | Clark | Aug 1988 | A |
| 4766581 | Korn et al. | Aug 1988 | A |
| 4787050 | Suzuki | Nov 1988 | A |
| 4792849 | McCalley | Dec 1988 | A |
| 4807052 | Amano | Feb 1989 | A |
| 4811325 | Sharples | Mar 1989 | A |
| 4814972 | Winter et al. | Mar 1989 | A |
| 4815868 | Speicher | Mar 1989 | A |
| 4825054 | Rust | Apr 1989 | A |
| 4829570 | Schotz | May 1989 | A |
| 4852154 | Lewis et al. | Jul 1989 | A |
| 4857714 | Sunyich | Aug 1989 | A |
| 4868832 | Marrington | Sep 1989 | A |
| 4885694 | Pray et al. | Dec 1989 | A |
| 4905279 | Nishio | Feb 1990 | A |
| 4920432 | Eggers | Apr 1990 | A |
| 4922420 | Nakagawa | May 1990 | A |
| 4924378 | Hershey | May 1990 | A |
| 4926485 | Yamashita | May 1990 | A |
| 4937807 | Weitz | Jun 1990 | A |
| 4949187 | Cohen | Aug 1990 | A |
| 4953159 | Hayden et al. | Aug 1990 | A |
| 4956768 | Sidi | Sep 1990 | A |
| 4958835 | Tashiro | Sep 1990 | A |
| 4965675 | Masashi et al. | Oct 1990 | A |
| 4977593 | Ballance | Dec 1990 | A |
| 4999806 | Chernow | Mar 1991 | A |
| 5008814 | Mathur | Apr 1991 | A |
| 5012121 | Hammond | Apr 1991 | A |
| 5027426 | Chiocca | Jun 1991 | A |
| 5041921 | Scheffler | Aug 1991 | A |
| 5046093 | Wachob | Sep 1991 | A |
| 5053758 | Cornett et al. | Oct 1991 | A |
| 5058089 | Yoshimara | Oct 1991 | A |
| 5077607 | Johnson et al. | Dec 1991 | A |
| 5081534 | Geiger et al. | Jan 1992 | A |
| 5101451 | Ash et al. | Mar 1992 | A |
| 5101499 | Streck et al. | Mar 1992 | A |
| 5106097 | Levine | Apr 1992 | A |
| 5117407 | Vogel | May 1992 | A |
| D327687 | Arbitor | Jul 1992 | S |
| 5128862 | Mueller | Jul 1992 | A |
| 5138712 | Corbin | Aug 1992 | A |
| 5148159 | Clark et al. | Sep 1992 | A |
| 5155847 | Kirouac | Oct 1992 | A |
| 5159678 | Wengelski et al. | Oct 1992 | A |
| 5163131 | Row | Nov 1992 | A |
| 5166886 | Molnar | Nov 1992 | A |
| D332096 | Wolff et al. | Dec 1992 | S |
| 5172413 | Bradley et al. | Dec 1992 | A |
| 5180309 | Egnor | Jan 1993 | A |
| 5189630 | Barstow et al. | Feb 1993 | A |
| 5191573 | Hair | Mar 1993 | A |
| 5191611 | Lang | Mar 1993 | A |
| 5192999 | Graczyk | Mar 1993 | A |
| 5197094 | Tillery | Mar 1993 | A |
| 5203028 | Shiraishi | Apr 1993 | A |
| 5210854 | Beaverton et al. | May 1993 | A |
| 5214761 | Barrett et al. | May 1993 | A |
| 5222134 | Waite et al. | Jun 1993 | A |
| 5228015 | Arbiter et al. | Jul 1993 | A |
| 5231157 | Herzig et al. | Jul 1993 | A |
| 5237157 | Kaplan | Aug 1993 | A |
| 5239480 | Huegel | Aug 1993 | A |
| 5250747 | Tsumura | Oct 1993 | A |
| 5252775 | Urano | Oct 1993 | A |
| 5260999 | Wyman | Nov 1993 | A |
| 5261104 | Bertram et al. | Nov 1993 | A |
| 5262875 | Mincer et al. | Nov 1993 | A |
| 5276866 | Paolini | Jan 1994 | A |
| 5278904 | Servi | Jan 1994 | A |
| 5282028 | Johnson et al. | Jan 1994 | A |
| 5289476 | Johnson et al. | Feb 1994 | A |
| 5289546 | Hetherington | Feb 1994 | A |
| 5315161 | Robinson | May 1994 | A |
| 5315711 | Barone et al. | May 1994 | A |
| 5319455 | Hoarty et al. | Jun 1994 | A |
| 5321846 | Yokota et al. | Jun 1994 | A |
| 5339413 | Koval | Jun 1994 | A |
| 5327230 | Dockery | Jul 1994 | A |
| 5335313 | Douglas | Aug 1994 | A |
| 5339095 | Redford | Aug 1994 | A |
| 5341350 | Frank | Aug 1994 | A |
| 5355302 | Martin et al. | Oct 1994 | A |
| 5357276 | Banker | Oct 1994 | A |
| 5369778 | SanSoucie | Nov 1994 | A |
| 5375206 | Hunter | Dec 1994 | A |
| 5386251 | Movshovich | Jan 1995 | A |
| 5389950 | Bouton | Feb 1995 | A |
| 5404505 | Levinson | Apr 1995 | A |
| 5406634 | Anderson et al. | Apr 1995 | A |
| 5408417 | Wilder | Apr 1995 | A |
| 5410326 | Goldstein | Apr 1995 | A |
| 5410703 | Nilsson et al. | Apr 1995 | A |
| 5418713 | Allen | May 1995 | A |
| 5420923 | Beyers | May 1995 | A |
| 5428252 | Walker | Jun 1995 | A |
| 5428606 | Moskowitz | Jun 1995 | A |
| 5431492 | Rothschild | Jul 1995 | A |
| 5440632 | Bacon et al. | Aug 1995 | A |
| 5444499 | Saitoh | Aug 1995 | A |
| 5445295 | Brown | Aug 1995 | A |
| 5455619 | Truckenmiller et al. | Oct 1995 | A |
| 5455926 | Keele | Oct 1995 | A |
| 5457305 | Akel | Oct 1995 | A |
| 5465213 | Ross | Nov 1995 | A |
| 5465329 | Whistler | Nov 1995 | A |
| 5467326 | Miyashita et al. | Nov 1995 | A |
| 5469370 | Ostrover et al. | Nov 1995 | A |
| 5469573 | McGill et al. | Nov 1995 | A |
| 5471576 | Yee | Nov 1995 | A |
| 5473746 | Pritt et al. | Dec 1995 | A |
| 5475835 | Hickey | Dec 1995 | A |
| 5481509 | Knowles | Jan 1996 | A |
| 5487167 | Dinallo et al. | Jan 1996 | A |
| 5489103 | Okamoto | Feb 1996 | A |
| 5495610 | Shing | Feb 1996 | A |
| 5496178 | Back | Mar 1996 | A |
| 5499921 | Sone | Mar 1996 | A |
| 5511000 | Kaloi | Apr 1996 | A |
| 5513117 | Small | Apr 1996 | A |
| 5515173 | Mankovitz et al. | May 1996 | A |
| 5519435 | Anderson | May 1996 | A |
| 5519457 | Nishigaki et al. | May 1996 | A |
| 5521631 | Budow et al. | May 1996 | A |
| 5521918 | Kim | May 1996 | A |
| 5521922 | Fujinami et al. | May 1996 | A |
| 5523781 | Brusaw | Jun 1996 | A |
| 5528732 | Klotz | Jun 1996 | A |
| 5532734 | Goertz | Jul 1996 | A |
| 5532991 | Sasaki | Jul 1996 | A |
| 5546039 | Hewitt et al. | Aug 1996 | A |
| 5548729 | Akiyoshi | Aug 1996 | A |
| 5550577 | Verbiest | Aug 1996 | A |
| 5554968 | Lee | Sep 1996 | A |
| 5555244 | Gupta | Sep 1996 | A |
| 5557515 | Abbruzzese et al. | Sep 1996 | A |
| 5557541 | Schulhof | Sep 1996 | A |
| 5557724 | Sampat et al. | Sep 1996 | A |
| 5559505 | McNair | Sep 1996 | A |
| 5559549 | Hendricks | Sep 1996 | A |
| 5559714 | Banks et al. | Sep 1996 | A |
| 5561709 | Remillard | Oct 1996 | A |
| 5565908 | Ahmad | Oct 1996 | A |
| 5566237 | Dobbs | Oct 1996 | A |
| 5570363 | Holm | Oct 1996 | A |
| 5578999 | Matsuzawa et al. | Nov 1996 | A |
| 5579404 | Fielder et al. | Nov 1996 | A |
| 5583561 | Baker et al. | Dec 1996 | A |
| 5583937 | Ullrich et al. | Dec 1996 | A |
| 5583994 | Rangan | Dec 1996 | A |
| 5583995 | Gardner et al. | Dec 1996 | A |
| 5590318 | Zbikowski et al. | Dec 1996 | A |
| 5592482 | Abraham | Jan 1997 | A |
| 5592551 | Lett | Jan 1997 | A |
| 5592611 | Midgely et al. | Jan 1997 | A |
| 5594509 | Florin | Jan 1997 | A |
| 5596702 | Stucka et al. | Jan 1997 | A |
| 5607099 | Yeh et al. | Mar 1997 | A |
| 5612581 | Kageyama | Mar 1997 | A |
| 5613909 | Stelovsky | Mar 1997 | A |
| 5616876 | Cluts | Apr 1997 | A |
| 5617565 | Augenbraun et al. | Apr 1997 | A |
| 5619247 | Russo | Apr 1997 | A |
| 5619249 | Billock et al. | Apr 1997 | A |
| 5619250 | McClellan et al. | Apr 1997 | A |
| 5619698 | Lillich | Apr 1997 | A |
| 5623666 | Pike | Apr 1997 | A |
| 5631693 | Wunderlich et al. | May 1997 | A |
| 5636276 | Brugger | Jun 1997 | A |
| 5638426 | Lewis | Jun 1997 | A |
| 5642337 | Oskay | Jun 1997 | A |
| 5643831 | Ochiai et al. | Jul 1997 | A |
| 5644714 | Kikinis | Jul 1997 | A |
| 5644766 | Coy | Jul 1997 | A |
| 5654714 | Takahashi et al. | Aug 1997 | A |
| 5659466 | Norris et al. | Aug 1997 | A |
| 5661517 | Budow et al. | Aug 1997 | A |
| 5661802 | Nilssen | Aug 1997 | A |
| 5663756 | Blahut et al. | Sep 1997 | A |
| 5668592 | Spaulding | Sep 1997 | A |
| 5668778 | Quazi | Sep 1997 | A |
| 5675734 | Hair | Oct 1997 | A |
| 5680533 | Yamato et al. | Oct 1997 | A |
| 5684716 | Freeman | Nov 1997 | A |
| 5689641 | Ludwig et al. | Nov 1997 | A |
| 5691778 | Song | Nov 1997 | A |
| 5691964 | Niederlein et al. | Nov 1997 | A |
| 5696914 | Nahaboo et al. | Dec 1997 | A |
| 5697844 | Von Kohorn | Dec 1997 | A |
| 5703795 | Mankowitz | Dec 1997 | A |
| 5704146 | Herring et al. | Jan 1998 | A |
| 5708811 | Arendt | Jan 1998 | A |
| 5712976 | Falcon | Jan 1998 | A |
| 5713024 | Halladay | Jan 1998 | A |
| 5715416 | Baker | Feb 1998 | A |
| 5717452 | Janin et al. | Feb 1998 | A |
| 5721583 | Harada et al. | Feb 1998 | A |
| 5721815 | Ottesen et al. | Feb 1998 | A |
| 5721827 | Logan et al. | Feb 1998 | A |
| 5721829 | Dunn et al. | Feb 1998 | A |
| 5724525 | Beyers et al. | Mar 1998 | A |
| 5726909 | Krikorian | Mar 1998 | A |
| 5734719 | Tsevdos | Mar 1998 | A |
| 5734961 | Castille | Mar 1998 | A |
| 5739451 | Winksy et al. | Apr 1998 | A |
| 5743745 | Reintjes | Apr 1998 | A |
| 5745391 | Topor | Apr 1998 | A |
| 5748254 | Harrison et al. | May 1998 | A |
| 5748468 | Notenboom et al. | May 1998 | A |
| 5748954 | Mauldin | May 1998 | A |
| 5751336 | Aggarwal et al. | May 1998 | A |
| 5752232 | Basore et al. | May 1998 | A |
| 5757936 | Lee | May 1998 | A |
| 5758340 | Nail | May 1998 | A |
| 5761655 | Hoffman | Jun 1998 | A |
| 5762552 | Vuong | Jun 1998 | A |
| 5774527 | Handelman et al. | Jun 1998 | A |
| 5774668 | Choqiuer | Jun 1998 | A |
| 5778395 | Whiting | Jul 1998 | A |
| 5781889 | Martin et al. | Jul 1998 | A |
| 5786784 | Gaudichon | Jul 1998 | A |
| 5790172 | Imanaka | Aug 1998 | A |
| 5790671 | Cooper | Aug 1998 | A |
| 5790856 | Lillich | Aug 1998 | A |
| 5790935 | Payton | Aug 1998 | A |
| 5793364 | Bolanos et al. | Aug 1998 | A |
| 5793980 | Glaser | Aug 1998 | A |
| 5798785 | Hendricks | Aug 1998 | A |
| 5802283 | Grady et al. | Sep 1998 | A |
| 5802558 | Pierce | Sep 1998 | A |
| 5805804 | Laursen et al. | Sep 1998 | A |
| 5808224 | Kato | Sep 1998 | A |
| 5809246 | Goldman | Sep 1998 | A |
| 5812643 | Schelberg et al. | Sep 1998 | A |
| 5815146 | Youden et al. | Sep 1998 | A |
| 5825884 | Zdepski et al. | Oct 1998 | A |
| 5828343 | MacDonald et al. | Oct 1998 | A |
| 5831555 | Yu et al. | Nov 1998 | A |
| 5831663 | Waterhouse et al. | Nov 1998 | A |
| 5832024 | Schotz et al. | Nov 1998 | A |
| 5832287 | Atalla | Nov 1998 | A |
| 5835843 | Haddad | Nov 1998 | A |
| 5842869 | McGregor et al. | Dec 1998 | A |
| 5845104 | Rao | Dec 1998 | A |
| 5845256 | Pescitelli et al. | Dec 1998 | A |
| 5848398 | Martin | Dec 1998 | A |
| 5851149 | Xidos et al. | Dec 1998 | A |
| 5854887 | Kindell | Dec 1998 | A |
| 5857020 | Peterson | Jan 1999 | A |
| 5857707 | Devlin | Jan 1999 | A |
| 5862324 | Collins | Jan 1999 | A |
| 5864811 | Tran et al. | Jan 1999 | A |
| 5864868 | Contois | Jan 1999 | A |
| 5864870 | Guck | Jan 1999 | A |
| 5867714 | Todd | Feb 1999 | A |
| 5870721 | Norris | Feb 1999 | A |
| 5880386 | Wachi et al. | Mar 1999 | A |
| 5880769 | Nemirofsky et al. | Mar 1999 | A |
| 5884028 | Kindell | Mar 1999 | A |
| 5884298 | Smith | Mar 1999 | A |
| 5887139 | Madison, Jr. et al. | Mar 1999 | A |
| 5887193 | Takahashi | Mar 1999 | A |
| 5893162 | Lau et al. | Apr 1999 | A |
| 5895455 | Bellinger et al. | Apr 1999 | A |
| 5896094 | Narisada et al. | Apr 1999 | A |
| 5903266 | Berstis et al. | May 1999 | A |
| 5913040 | Rakavy | Jun 1999 | A |
| 5914712 | Sartain et al. | Jun 1999 | A |
| 5915094 | Kouloheris | Jun 1999 | A |
| 5915238 | Tjaden | Jun 1999 | A |
| 5917537 | Lightfoot | Jun 1999 | A |
| 5917835 | Barrett | Jun 1999 | A |
| 5918213 | Bernard et al. | Jun 1999 | A |
| 5920700 | Gordon et al. | Jul 1999 | A |
| 5920702 | Johnson | Jul 1999 | A |
| 5923885 | Johnson | Jul 1999 | A |
| 5926531 | Petite | Jul 1999 | A |
| 5926624 | Katz et al. | Jul 1999 | A |
| 5930765 | Martin | Jul 1999 | A |
| 5931908 | Gerba | Aug 1999 | A |
| 5933090 | Christenson | Aug 1999 | A |
| 5940504 | Griswold | Aug 1999 | A |
| 5949411 | Doerr et al. | Sep 1999 | A |
| 5949688 | Montoya | Sep 1999 | A |
| 5953005 | Liu | Sep 1999 | A |
| 5953429 | Wakai et al. | Sep 1999 | A |
| 5956716 | Kenner et al. | Sep 1999 | A |
| 5959869 | Miller | Sep 1999 | A |
| 5959945 | Kleiman | Sep 1999 | A |
| 5960167 | Roberts et al. | Sep 1999 | A |
| 5963916 | Kaplan | Oct 1999 | A |
| 5966495 | Takahashi | Oct 1999 | A |
| 5970467 | Alavi | Oct 1999 | A |
| 5978855 | Metz | Nov 1999 | A |
| 5978912 | Rakavy et al. | Nov 1999 | A |
| 5980261 | Mino et al. | Nov 1999 | A |
| 5999499 | Pines et al. | Dec 1999 | A |
| 5999624 | Hopkins | Dec 1999 | A |
| 6002720 | Yurt | Dec 1999 | A |
| 6005599 | Asai et al. | Dec 1999 | A |
| 6008735 | Chiloyan et al. | Dec 1999 | A |
| 6009274 | Fletcher | Dec 1999 | A |
| 6011758 | Dockes et al. | Jan 2000 | A |
| 6018337 | Peters | Jan 2000 | A |
| 6018726 | Tsumura | Jan 2000 | A |
| 6021386 | Davis | Feb 2000 | A |
| 6023705 | Bellinger et al. | Feb 2000 | A |
| 6025868 | Russo | Feb 2000 | A |
| 6026168 | Li et al. | Feb 2000 | A |
| 6034925 | Wehmeyer | Mar 2000 | A |
| 6038591 | Wolfe et al. | Mar 2000 | A |
| 6040829 | Croy et al. | Mar 2000 | A |
| 6041354 | Biliris et al. | Mar 2000 | A |
| 6049891 | Inamoto | Apr 2000 | A |
| 6054987 | Richardson | Apr 2000 | A |
| 6055573 | Gardenswartz et al. | Apr 2000 | A |
| 6057874 | Michaud | May 2000 | A |
| 6067564 | Urakoshi et al. | May 2000 | A |
| 6069672 | Claassen | May 2000 | A |
| 6072982 | Haddad | Jun 2000 | A |
| 6107937 | Hamada | Aug 2000 | A |
| 6118450 | Proehl et al. | Sep 2000 | A |
| 6124804 | Kitao et al. | Sep 2000 | A |
| 6131088 | Hill | Oct 2000 | A |
| 6131121 | Mattaway et al. | Oct 2000 | A |
| 6134547 | Huxley et al. | Oct 2000 | A |
| 6138150 | Nichols et al. | Oct 2000 | A |
| 6146210 | Cha et al. | Nov 2000 | A |
| 6148142 | Anderson | Nov 2000 | A |
| 6151077 | Vogel et al. | Nov 2000 | A |
| 6151634 | Glaser | Nov 2000 | A |
| 6154207 | Farris et al. | Nov 2000 | A |
| 6157935 | Tran et al. | Dec 2000 | A |
| 6161059 | Tedesco et al. | Dec 2000 | A |
| 6167358 | Othmer et al. | Dec 2000 | A |
| 6170060 | Mott et al. | Jan 2001 | B1 |
| 6173172 | Masuda et al. | Jan 2001 | B1 |
| 6175861 | Williams, Jr. et al. | Jan 2001 | B1 |
| 6182126 | Nathan et al. | Jan 2001 | B1 |
| 6185184 | Mattaway et al. | Feb 2001 | B1 |
| 6185619 | Joffe et al. | Feb 2001 | B1 |
| 6191780 | Martin et al. | Feb 2001 | B1 |
| 6192340 | Abecassis | Feb 2001 | B1 |
| 6195732 | Adams et al. | Feb 2001 | B1 |
| 6198408 | Cohen | Mar 2001 | B1 |
| 6202060 | Tran | Mar 2001 | B1 |
| 6209060 | Machida | Mar 2001 | B1 |
| 6212138 | Kalis et al. | Apr 2001 | B1 |
| 6216175 | Sliger et al. | Apr 2001 | B1 |
| 6216227 | Goldstein et al. | Apr 2001 | B1 |
| 6219692 | Stiles | Apr 2001 | B1 |
| 6223209 | Watson | Apr 2001 | B1 |
| 6226412 | Schwab | May 2001 | B1 |
| 6226715 | Van Der Wolf et al. | May 2001 | B1 |
| 6240550 | Nathan et al. | May 2001 | B1 |
| 6243725 | Hempleman et al. | Jun 2001 | B1 |
| 6247022 | Yankowski | Jun 2001 | B1 |
| 6256773 | Bowman-Amuah | Jul 2001 | B1 |
| 6262569 | Carr et al. | Jul 2001 | B1 |
| 6280327 | Leifer et al. | Aug 2001 | B1 |
| 6282709 | Reha et al. | Aug 2001 | B1 |
| 6288688 | Hughes et al. | Sep 2001 | B1 |
| 6288991 | Kajiyama et al. | Sep 2001 | B1 |
| 6289382 | Bowman-Amuah | Sep 2001 | B1 |
| 6292443 | Awazu et al. | Sep 2001 | B1 |
| 6298373 | Burns et al. | Oct 2001 | B1 |
| 6301710 | Fujiwara | Oct 2001 | B1 |
| 6302793 | Fertitta et al. | Oct 2001 | B1 |
| 6308204 | Nathan et al. | Oct 2001 | B1 |
| 6311214 | Rhoads | Oct 2001 | B1 |
| 6315572 | Glaser | Nov 2001 | B1 |
| 6323911 | Schein et al. | Nov 2001 | B1 |
| 6332025 | Takahashi et al. | Dec 2001 | B2 |
| 6336219 | Nathan | Jan 2002 | B1 |
| 6341166 | Basel | Jan 2002 | B1 |
| 6344862 | Williams et al. | Feb 2002 | B1 |
| 6346951 | Mastronardi | Feb 2002 | B1 |
| 6353820 | Edwards et al. | Mar 2002 | B1 |
| 6356971 | Katz | Mar 2002 | B1 |
| 6359616 | Ogura et al. | Mar 2002 | B1 |
| 6359661 | Nickum | Mar 2002 | B1 |
| 6370580 | Kriegsman | Apr 2002 | B2 |
| 6379187 | Nishimatsu | Apr 2002 | B2 |
| 6381575 | Martin et al. | Apr 2002 | B1 |
| 6384737 | Hsu et al. | May 2002 | B1 |
| 6393584 | McLaren et al. | May 2002 | B1 |
| 6396480 | Schindler et al. | May 2002 | B1 |
| 6397189 | Martin et al. | May 2002 | B1 |
| 6407987 | Abraham | Jun 2002 | B1 |
| 6408435 | Sato | Jun 2002 | B1 |
| 6408437 | Hendricks et al. | Jun 2002 | B1 |
| 6421651 | Tedesco et al. | Jul 2002 | B1 |
| 6425125 | Fries et al. | Jul 2002 | B1 |
| 6430537 | Tedesco et al. | Aug 2002 | B1 |
| 6430738 | Gross et al. | Aug 2002 | B1 |
| 6434678 | Menzel | Aug 2002 | B1 |
| 6438450 | DiLorenzo | Aug 2002 | B1 |
| 6442549 | Schneider | Aug 2002 | B1 |
| 6446080 | Van Ryzin et al. | Sep 2002 | B1 |
| 6446130 | Grapes | Sep 2002 | B1 |
| 6449688 | Peters et al. | Sep 2002 | B1 |
| 6470496 | Kato et al. | Oct 2002 | B1 |
| 6473794 | Guheen et al. | Oct 2002 | B1 |
| 6488508 | Okamoto | Dec 2002 | B2 |
| 6490570 | Numaoka | Dec 2002 | B1 |
| 6493871 | McGuire et al. | Dec 2002 | B1 |
| 6496927 | McGrane et al. | Dec 2002 | B1 |
| 6498855 | Kokkosoulis et al. | Dec 2002 | B1 |
| 6522707 | Brandstetter et al. | Feb 2003 | B1 |
| 6535911 | Miller et al. | Mar 2003 | B1 |
| 6538558 | Sakazume et al. | Mar 2003 | B2 |
| 6543052 | Ogasawara | Apr 2003 | B1 |
| 6544122 | Araki et al. | Apr 2003 | B2 |
| 6549719 | Mankovitz | Apr 2003 | B2 |
| D475029 | Nathan et al. | May 2003 | S |
| 6560651 | Katz et al. | May 2003 | B2 |
| 6570507 | Lee et al. | May 2003 | B1 |
| 6571282 | Bowman-Amuah | May 2003 | B1 |
| 6577735 | Bharat | Jun 2003 | B1 |
| 6578051 | Mastronardi et al. | Jun 2003 | B1 |
| 6587403 | Keller et al. | Jul 2003 | B1 |
| 6590838 | Gerlings et al. | Jul 2003 | B1 |
| 6598230 | Ballhorn | Jul 2003 | B1 |
| 6622307 | Ho | Sep 2003 | B1 |
| 6628939 | Paulsen | Sep 2003 | B2 |
| 6629318 | Radha et al. | Sep 2003 | B1 |
| 6643620 | Contolini et al. | Nov 2003 | B1 |
| 6643690 | Duursma et al. | Nov 2003 | B2 |
| 6654801 | Mann et al. | Nov 2003 | B2 |
| 6658090 | Harjunen et al. | Dec 2003 | B1 |
| 6662231 | Drosset et al. | Dec 2003 | B1 |
| 6702585 | Okamoto | Mar 2004 | B2 |
| 6724974 | Naruto et al. | Apr 2004 | B2 |
| 6728824 | Chen | Apr 2004 | B1 |
| 6728956 | Ono | Apr 2004 | B2 |
| 6728966 | Arsenault et al. | Apr 2004 | B1 |
| 6744882 | Gupta et al. | Jun 2004 | B1 |
| 6751794 | McCaleb et al. | Jun 2004 | B1 |
| 6755744 | Nathan et al. | Jun 2004 | B1 |
| 6762585 | Liao | Jul 2004 | B2 |
| D495755 | Wurz et al. | Sep 2004 | S |
| 6789215 | Rupp et al. | Sep 2004 | B1 |
| 6816578 | Kredo et al. | Nov 2004 | B1 |
| 6850252 | Hoffberg | Feb 2005 | B1 |
| 6882793 | Fu | Apr 2005 | B1 |
| 6898161 | Nathan | May 2005 | B1 |
| 6904592 | Johnson | Jun 2005 | B1 |
| 6920614 | Schindler et al. | Jul 2005 | B1 |
| 6928653 | Ellis et al. | Aug 2005 | B1 |
| 6934700 | Ijdens et al. | Aug 2005 | B1 |
| 6942574 | LeMay et al. | Sep 2005 | B1 |
| 6974076 | Siegel | Dec 2005 | B1 |
| 7024485 | Dunning et al. | Apr 2006 | B2 |
| 7073172 | Chamberlain | Jul 2006 | B2 |
| 7103583 | Baum et al. | Sep 2006 | B1 |
| 7107109 | Nathan et al. | Sep 2006 | B1 |
| 7111129 | Percival | Sep 2006 | B2 |
| 7114013 | Bakke et al. | Sep 2006 | B2 |
| 7124194 | Nathan et al. | Oct 2006 | B2 |
| 7160132 | Phillips et al. | Jan 2007 | B2 |
| 7181458 | Higashi | Feb 2007 | B1 |
| 7188352 | Nathan et al. | Mar 2007 | B2 |
| 7195157 | Swartz et al. | Mar 2007 | B2 |
| 7198571 | LeMay et al. | Apr 2007 | B2 |
| 7205471 | Looney et al. | Apr 2007 | B2 |
| 7206417 | Nathan | Apr 2007 | B2 |
| 7210141 | Nathan et al. | Apr 2007 | B1 |
| 7231656 | Nathan | Jun 2007 | B1 |
| 7237198 | Chaney | Jun 2007 | B1 |
| 7281652 | Foss | Oct 2007 | B2 |
| 7293277 | Nathan | Nov 2007 | B1 |
| D560651 | Berkheimer et al. | Jan 2008 | S |
| 7347723 | Daily | Mar 2008 | B1 |
| D566195 | Ichimura et al. | Apr 2008 | S |
| 7356831 | Nathan | Apr 2008 | B2 |
| 7406529 | Reed | Jul 2008 | B2 |
| 7415707 | Taguchi et al. | Aug 2008 | B2 |
| 7418474 | Schwab | Aug 2008 | B2 |
| 7424731 | Nathan et al. | Sep 2008 | B1 |
| 7430736 | Nguyen et al. | Sep 2008 | B2 |
| 7433832 | Bezos et al. | Oct 2008 | B1 |
| 7448057 | Nathan | Nov 2008 | B1 |
| 7483958 | Elabbady et al. | Jan 2009 | B1 |
| 7500192 | Mastronardi | Mar 2009 | B2 |
| 7512632 | Mastronardi et al. | Mar 2009 | B2 |
| 7519442 | Nathan et al. | Apr 2009 | B2 |
| 7522631 | Brown et al. | Apr 2009 | B1 |
| 7533182 | Wurtzel et al. | May 2009 | B2 |
| 7548851 | Lau | Jun 2009 | B1 |
| 7549919 | Nathan et al. | Jun 2009 | B1 |
| 7574727 | Nathan et al. | Aug 2009 | B2 |
| 7634228 | White et al. | Dec 2009 | B2 |
| 7647613 | Drakoulis et al. | Jan 2010 | B2 |
| 7657910 | McAulay et al. | Feb 2010 | B1 |
| D616414 | Nathan et al. | May 2010 | S |
| 7749083 | Nathan et al. | Jul 2010 | B2 |
| 7757264 | Nathan | Jul 2010 | B2 |
| 7761538 | Lin et al. | Jul 2010 | B2 |
| 7770165 | Olson et al. | Aug 2010 | B2 |
| 7778879 | Nathan et al. | Aug 2010 | B2 |
| 7783593 | Espino | Aug 2010 | B2 |
| 7783774 | Nathan et al. | Aug 2010 | B2 |
| 7793331 | Nathan et al. | Sep 2010 | B2 |
| 7819734 | Nathan et al. | Oct 2010 | B2 |
| 7822687 | Brillon et al. | Oct 2010 | B2 |
| D629382 | Nathan et al. | Dec 2010 | S |
| 7922178 | Nathan et al. | Apr 2011 | B2 |
| 7937724 | Clark et al. | May 2011 | B2 |
| D642553 | Nathan et al. | Aug 2011 | S |
| 7992178 | Nathan et al. | Aug 2011 | B1 |
| 7996873 | Nathan et al. | Aug 2011 | B1 |
| 8015200 | Seiflien et al. | Sep 2011 | B2 |
| 8028318 | Nathan | Sep 2011 | B2 |
| 8032879 | Nathan et al. | Oct 2011 | B2 |
| 8037412 | Nathan et al. | Oct 2011 | B2 |
| 8052512 | Nathan et al. | Nov 2011 | B2 |
| 8103589 | Nathan et al. | Jan 2012 | B2 |
| 8151304 | Nathan et al. | Apr 2012 | B2 |
| 8165318 | Nathan et al. | Apr 2012 | B2 |
| 8214874 | Nathan | Jul 2012 | B2 |
| D665375 | Garneau et al. | Aug 2012 | S |
| 8292712 | Nathan et al. | Oct 2012 | B2 |
| 8325571 | Cappello et al. | Dec 2012 | B2 |
| 8332895 | Nathan et al. | Dec 2012 | B2 |
| 8429530 | Neuman et al. | Apr 2013 | B2 |
| 20010016815 | Takahashi et al. | Aug 2001 | A1 |
| 20010023403 | Martin et al. | Sep 2001 | A1 |
| 20010030660 | Zainoulline | Oct 2001 | A1 |
| 20010030912 | Kalis et al. | Oct 2001 | A1 |
| 20010037367 | Iyer | Nov 2001 | A1 |
| 20010044725 | Matsuda et al. | Nov 2001 | A1 |
| 20020002079 | Martin et al. | Jan 2002 | A1 |
| 20020002483 | Siegel et al. | Jan 2002 | A1 |
| 20020018074 | Buil et al. | Feb 2002 | A1 |
| 20020032603 | Yeiser | Mar 2002 | A1 |
| 20020040371 | Burgess | Apr 2002 | A1 |
| 20020113824 | Myers | Aug 2002 | A1 |
| 20020116476 | Eyal et al. | Aug 2002 | A1 |
| 20020118949 | Jones et al. | Aug 2002 | A1 |
| 20020120925 | Logan | Aug 2002 | A1 |
| 20020123331 | Lehaff et al. | Sep 2002 | A1 |
| 20020126141 | Mastronardi | Sep 2002 | A1 |
| 20020129036 | Ho Yuen Lok et al. | Sep 2002 | A1 |
| 20020129371 | Emura et al. | Sep 2002 | A1 |
| 20020162104 | Raike et al. | Oct 2002 | A1 |
| 20030004833 | Pollak et al. | Jan 2003 | A1 |
| 20030005099 | Sven et al. | Jan 2003 | A1 |
| 20030006911 | Smith et al. | Jan 2003 | A1 |
| 20030008703 | Gauselmann | Jan 2003 | A1 |
| 20030014272 | Goulet et al. | Jan 2003 | A1 |
| 20030018740 | Sonoda et al. | Jan 2003 | A1 |
| 20030027120 | Jean | Feb 2003 | A1 |
| 20030031096 | Nathan et al. | Feb 2003 | A1 |
| 20030037010 | Schmelzer | Feb 2003 | A1 |
| 20030041093 | Yamane et al. | Feb 2003 | A1 |
| 20030050058 | Walsh et al. | Mar 2003 | A1 |
| 20030064805 | Wells | Apr 2003 | A1 |
| 20030065639 | Fiennes et al. | Apr 2003 | A1 |
| 20030076380 | Yusef et al. | Apr 2003 | A1 |
| 20030088538 | Ballard | May 2003 | A1 |
| 20030093790 | Logan et al. | May 2003 | A1 |
| 20030101450 | Davidsson et al. | May 2003 | A1 |
| 20030104865 | Itkis et al. | Jun 2003 | A1 |
| 20030108164 | Laurin et al. | Jun 2003 | A1 |
| 20030135424 | Davis et al. | Jul 2003 | A1 |
| 20030144910 | Flaherty et al. | Jul 2003 | A1 |
| 20030163388 | Beane | Aug 2003 | A1 |
| 20030176218 | LeMay et al. | Sep 2003 | A1 |
| 20030191753 | Hoch | Oct 2003 | A1 |
| 20030208586 | Mastronardi et al. | Nov 2003 | A1 |
| 20030225834 | Lee et al. | Dec 2003 | A1 |
| 20030233469 | Knowlson | Dec 2003 | A1 |
| 20040010800 | Goci | Jan 2004 | A1 |
| 20040025185 | Goci et al. | Feb 2004 | A1 |
| 20040085334 | Reaney | May 2004 | A1 |
| 20040103150 | Ogdon et al. | May 2004 | A1 |
| 20040145477 | Easter | Jul 2004 | A1 |
| 20040158555 | Seedman et al. | Aug 2004 | A1 |
| 20040204220 | Fried et al. | Oct 2004 | A1 |
| 20040205171 | Nathan et al. | Oct 2004 | A1 |
| 20040220926 | Lamkin et al. | Nov 2004 | A1 |
| 20040243482 | Laut | Dec 2004 | A1 |
| 20050034084 | Ohtsuki | Feb 2005 | A1 |
| 20050048816 | Higgins | Mar 2005 | A1 |
| 20050060405 | Nathan et al. | Mar 2005 | A1 |
| 20050073782 | Nathan | Apr 2005 | A1 |
| 20050086172 | Stefik | Apr 2005 | A1 |
| 20050111671 | Nathan | May 2005 | A1 |
| 20050125833 | Nathan et al. | Jun 2005 | A1 |
| 20050201254 | Looney et al. | Sep 2005 | A1 |
| 20050240661 | Heller et al. | Oct 2005 | A1 |
| 20050267819 | Kaplan | Dec 2005 | A1 |
| 20060018208 | Nathan et al. | Jan 2006 | A1 |
| 20060031896 | Pulitzer | Feb 2006 | A1 |
| 20060035707 | Nguyen et al. | Feb 2006 | A1 |
| 20060062094 | Nathan et al. | Mar 2006 | A1 |
| 20060143236 | Wu | Jun 2006 | A1 |
| 20060143575 | Sauermann | Jun 2006 | A1 |
| 20060227673 | Yamashita et al. | Oct 2006 | A1 |
| 20060239131 | Nathan et al. | Oct 2006 | A1 |
| 20060293773 | Nathan et al. | Dec 2006 | A1 |
| 20070025701 | Kawasaki et al. | Feb 2007 | A1 |
| 20070047198 | Crooijmans et al. | Mar 2007 | A1 |
| 20070086280 | Cappello et al. | Apr 2007 | A1 |
| 20070121430 | Nathan | May 2007 | A1 |
| 20070139410 | Abe et al. | Jun 2007 | A1 |
| 20070142022 | Madonna et al. | Jun 2007 | A1 |
| 20070160224 | Nathan | Jul 2007 | A1 |
| 20070204263 | Nathan et al. | Aug 2007 | A1 |
| 20070209053 | Nathan | Sep 2007 | A1 |
| 20070220052 | Kudo et al. | Sep 2007 | A1 |
| 20070247979 | Brillon et al. | Oct 2007 | A1 |
| 20080003881 | Wu | Jan 2008 | A1 |
| 20080005179 | Friedman | Jan 2008 | A1 |
| 20080005698 | Koskinen | Jan 2008 | A1 |
| 20080065925 | Oliverio et al. | Mar 2008 | A1 |
| 20080066016 | Dowdy et al. | Mar 2008 | A1 |
| 20080069545 | Nathan et al. | Mar 2008 | A1 |
| 20080077962 | Nathan | Mar 2008 | A1 |
| 20080086379 | Dion et al. | Apr 2008 | A1 |
| 20080096659 | Kreloff et al. | Apr 2008 | A1 |
| 20080137849 | Nathan | Jun 2008 | A1 |
| 20080155588 | Roberts et al. | Jun 2008 | A1 |
| 20080168807 | Dion et al. | Jul 2008 | A1 |
| 20080171594 | Fedesna et al. | Jul 2008 | A1 |
| 20080195443 | Nathan et al. | Aug 2008 | A1 |
| 20080198271 | Malki | Aug 2008 | A1 |
| 20080222199 | Tiu et al. | Sep 2008 | A1 |
| 20080222546 | Mudd | Sep 2008 | A1 |
| 20080239887 | Tooker et al. | Oct 2008 | A1 |
| 20080275771 | Levine | Nov 2008 | A1 |
| 20080305738 | Khedouri et al. | Dec 2008 | A1 |
| 20090006993 | Tuli et al. | Jan 2009 | A1 |
| 20090030802 | Plotnick et al. | Jan 2009 | A1 |
| 20090037969 | Nathan et al. | Feb 2009 | A1 |
| 20090042632 | Guenster et al. | Feb 2009 | A1 |
| 20090063976 | Bull et al. | Mar 2009 | A1 |
| 20090070341 | Mastronardi et al. | Mar 2009 | A1 |
| 20090091087 | Wasmund | Apr 2009 | A1 |
| 20090100092 | Seiflein et al. | Apr 2009 | A1 |
| 20090109224 | Sakurai | Apr 2009 | A1 |
| 20090128631 | Ortiz | May 2009 | A1 |
| 20090138111 | Mastronardi | May 2009 | A1 |
| 20090158203 | Kerr et al. | Jun 2009 | A1 |
| 20090168901 | Yarmolich et al. | Jul 2009 | A1 |
| 20090172565 | Jackson et al. | Jul 2009 | A1 |
| 20090177301 | Hayes | Jul 2009 | A1 |
| 20090234914 | Mikkelsen et al. | Sep 2009 | A1 |
| 20090240355 | Buil | Sep 2009 | A1 |
| 20090240721 | Giacalone | Sep 2009 | A1 |
| 20090241061 | Asai et al. | Sep 2009 | A1 |
| 20090265734 | Dion et al. | Oct 2009 | A1 |
| 20090282491 | Nathan | Nov 2009 | A1 |
| 20090287696 | Galuten | Nov 2009 | A1 |
| 20090298577 | Gagner et al. | Dec 2009 | A1 |
| 20090307314 | Smith et al. | Dec 2009 | A1 |
| 20090328095 | Vinokurov et al. | Dec 2009 | A1 |
| 20100042505 | Straus | Feb 2010 | A1 |
| 20100111489 | Presler | May 2010 | A1 |
| 20100131558 | Logan et al. | May 2010 | A1 |
| 20100211818 | Nathan et al. | Aug 2010 | A1 |
| 20100211872 | Rolston | Aug 2010 | A1 |
| 20100241259 | Nathan | Sep 2010 | A1 |
| 20100247081 | Victoria Pons | Sep 2010 | A1 |
| 20100269066 | Nathan | Oct 2010 | A1 |
| 20100299232 | Nathan et al. | Nov 2010 | A1 |
| 20100306179 | Lim | Dec 2010 | A1 |
| 20110055019 | Coleman | Mar 2011 | A1 |
| 20110066943 | Brillon et al. | Mar 2011 | A1 |
| 20110173521 | Horton et al. | Jul 2011 | A1 |
| 20110246517 | Nathan et al. | Oct 2011 | A1 |
| 20110270894 | Mastronardi et al. | Nov 2011 | A1 |
| 20110283236 | Beaumier et al. | Nov 2011 | A1 |
| 20110298938 | Nathan et al. | Dec 2011 | A1 |
| 20110304685 | Khedouri et al. | Dec 2011 | A1 |
| 20110321026 | Nathan et al. | Dec 2011 | A1 |
| 20120009985 | Nathan et al. | Jan 2012 | A1 |
| 20120053713 | Nathan | Mar 2012 | A1 |
| 20120105464 | Franceus | May 2012 | A1 |
| 20120143732 | Nathan et al. | Jun 2012 | A1 |
| 20120150614 | Dion et al. | Jun 2012 | A1 |
| 20120158531 | Dion et al. | Jun 2012 | A1 |
| 20120166965 | Nathan et al. | Jun 2012 | A1 |
| 20120240140 | Nathan | Sep 2012 | A1 |
| 20120321098 | Myers | Dec 2012 | A1 |
| 20120323652 | Mastronardi et al. | Dec 2012 | A1 |
| 20130021281 | Tse et al. | Jan 2013 | A1 |
| 20130040715 | Nathan et al. | Feb 2013 | A1 |
| 20130044995 | Cappello et al. | Feb 2013 | A1 |
| 20130070093 | Rivera et al. | Mar 2013 | A1 |
| 20130091054 | Nathan et al. | Apr 2013 | A1 |
| 20140026154 | Nathan | Jan 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 199954012 | Apr 2000 | AU |
| 2119184 | Sep 1994 | CA |
| 1340939 | Mar 2002 | CN |
| 3406058 | Aug 1985 | DE |
| 3723737 | Jan 1988 | DE |
| 3820835 | Jan 1989 | DE |
| A 3820835 | Jan 1989 | DE |
| 3815071 | Nov 1989 | DE |
| 4244198 | Jun 1994 | DE |
| 19539172 | Sep 1996 | DE |
| 19610739 | Sep 1997 | DE |
| 19904007 | Aug 2000 | DE |
| EU A0082077 | Jun 1983 | EP |
| 0140593 | May 1985 | EP |
| O 0256921 | Feb 1988 | EP |
| EU A 0283350 | Sep 1988 | EP |
| O 0283304 | Sep 1988 | EP |
| 0309298 | Mar 1989 | EP |
| EU 0309298 | Mar 1989 | EP |
| 0313359 | Apr 1989 | EP |
| EU A 0313359 | Apr 1989 | EP |
| O 0340787 | Nov 1989 | EP |
| O 0363186 | Apr 1990 | EP |
| O 0 425 168 | May 1991 | EP |
| 0464562 | Jan 1992 | EP |
| O 0480558 | Apr 1992 | EP |
| 0498130 | Aug 1992 | EP |
| 0498130 | Aug 1992 | EP |
| 0 507 110 | Oct 1992 | EP |
| 0529834 | Mar 1993 | EP |
| 0538319 | Apr 1993 | EP |
| EU A 0631283 | Dec 1994 | EP |
| 0632371 | Jan 1995 | EP |
| 0711076 | May 1996 | EP |
| 0786122 | Jul 1997 | EP |
| 0817103 | Jan 1998 | EP |
| 0841616 | May 1998 | EP |
| 0919964 | Jun 1999 | EP |
| 0959570 | Nov 1999 | EP |
| 0 974896 | Jan 2000 | EP |
| 0974941 | Jan 2000 | EP |
| 0982695 | Mar 2000 | EP |
| 1001391 | May 2000 | EP |
| 1170951 | Jan 2002 | EP |
| 1288802 | Mar 2003 | EP |
| 1408427 | Apr 2004 | EP |
| 1549919 | Apr 2004 | EP |
| 1962251 | Aug 2008 | EP |
| 2602352 | Feb 1988 | FR |
| 2808906 | Nov 2001 | FR |
| 2122799 | Jan 1984 | GB |
| A 2122799 | Jan 1984 | GB |
| 2166328 | Apr 1986 | GB |
| 2170943 | Aug 1986 | GB |
| 2193420 | Feb 1988 | GB |
| 2 238680 | Jun 1991 | GB |
| 2254469 | Oct 1992 | GB |
| 2259398 | Mar 1993 | GB |
| 2262170 | Jun 1993 | GB |
| 2380377 | Apr 2003 | GB |
| 2505584 | Aug 2014 | GB |
| 57-173207 | Oct 1982 | JP |
| 58-179892 | Oct 1983 | JP |
| 60-253082 | Dec 1985 | JP |
| 61084143 | Apr 1986 | JP |
| 62-192849 | Aug 1987 | JP |
| 62-284496 | Dec 1987 | JP |
| 63-60634 | Mar 1988 | JP |
| 2-153665 | Jun 1990 | JP |
| 5-74078 | Mar 1993 | JP |
| 5122282 | May 1993 | JP |
| 06-127885 | May 1994 | JP |
| 07281682 | Oct 1995 | JP |
| 07-311587 | Nov 1995 | JP |
| 08-037701 | Feb 1996 | JP |
| 08-279235 | Oct 1996 | JP |
| 8274812 | Oct 1996 | JP |
| 3034555 | Nov 1996 | JP |
| 08289976 | Nov 1996 | JP |
| 928918 | Feb 1997 | JP |
| 9114470 | May 1997 | JP |
| 9127964 | May 1997 | JP |
| 09-244900 | Sep 1997 | JP |
| 10-098344 | Apr 1998 | JP |
| 10-222537 | Aug 1998 | JP |
| 11-003088 | Jan 1999 | JP |
| 11-024686 | Jan 1999 | JP |
| 11-095768 | Apr 1999 | JP |
| 2000-270314 | Sep 2000 | JP |
| 2002-83640 | Mar 2002 | JP |
| 2002-537584 | Nov 2002 | JP |
| 2003-076380 | Mar 2003 | JP |
| 2003-084903 | Mar 2003 | JP |
| 2003-099072 | Apr 2003 | JP |
| 2004-29459 | Jan 2004 | JP |
| 2004-030469 | Jan 2004 | JP |
| 2004-054435 | Feb 2004 | JP |
| 2005-018438 | Jan 2005 | JP |
| 2005-107267 | Apr 2005 | JP |
| 2005-184237 | Jul 2005 | JP |
| 2005-215209 | Aug 2005 | JP |
| 2006-39704 | Feb 2006 | JP |
| 2006-048076 | Feb 2006 | JP |
| 2007-034253 | Feb 2007 | JP |
| 2007-041722 | Feb 2007 | JP |
| 2007505410 | Mar 2007 | JP |
| 07504517 | Mar 2007 | JP |
| 2007-102982 | Apr 2007 | JP |
| 2007-104072 | Apr 2007 | JP |
| 2007-128609 | May 2007 | JP |
| 2007-164078 | Jun 2007 | JP |
| 2007-164298 | Jun 2007 | JP |
| 2007179333 | Jul 2007 | JP |
| 2007-199775 | Aug 2007 | JP |
| 2007-241748 | Sep 2007 | JP |
| 2008-058656 | Mar 2008 | JP |
| 2009-017529 | Jan 2009 | JP |
| 2009-075540 | Apr 2009 | JP |
| 2009-288702 | Dec 2009 | JP |
| 514511 | Dec 2002 | TW |
| M274284 | Sep 2005 | TW |
| M290206 | May 2006 | TW |
| WO 86 01326 | Feb 1986 | WO |
| WO 9000429 | Jan 1990 | WO |
| WO A 90 07843 | Jul 1990 | WO |
| WO 9108542 | Jun 1991 | WO |
| WO 9120082 | Dec 1991 | WO |
| WO 9316557 | Aug 1993 | WO |
| WO 9318465 | Sep 1993 | WO |
| WO93021732 | Oct 1993 | WO |
| WO A 94 03894 | Feb 1994 | WO |
| WO 9414273 | Jun 1994 | WO |
| WO 9415306 | Jul 1994 | WO |
| WO 94 15416 | Jul 1994 | WO |
| WO 95 03609 | Feb 1995 | WO |
| WO 9529537 | Nov 1995 | WO |
| WO 9612255 | Apr 1996 | WO |
| WO 9612256 | Apr 1996 | WO |
| WO 9612257 | Apr 1996 | WO |
| WO 96 12258 | Apr 1996 | WO |
| WO 98 07940 | Feb 1998 | WO |
| WO 9811487 | Mar 1998 | WO |
| WO 9845835 | Oct 1998 | WO |
| WO 9935753 | Jul 1999 | WO |
| WO 0100290 | Jan 2001 | WO |
| WO 0108148 | Feb 2001 | WO |
| WO 0171608 | Sep 2001 | WO |
| WO 02060546 | Aug 2002 | WO |
| WO 02095752 | Nov 2002 | WO |
| WO 01084353 | Jan 2003 | WO |
| WO 2003005743 | Jan 2003 | WO |
| WO 03069613 | Aug 2003 | WO |
| WO 2004029775 | Apr 2004 | WO |
| WO 2005026916 | Mar 2005 | WO |
| WO 2005052751 | Jun 2005 | WO |
| WO 2006014739 | Feb 2006 | WO |
| WO 2006056933 | Jun 2006 | WO |
| WO 2006106631 | Oct 2006 | WO |
| WO 2006138064 | Dec 2006 | WO |
| WO 2007069143 | Jun 2007 | WO |
| WO 2007092542 | Aug 2007 | WO |
| WO 2008-033853 | Mar 2008 | WO |
| WO 2009004531 | Jan 2009 | WO |
| WO 2011094330 | Aug 2011 | WO |
| WO 2013040603 | Mar 2013 | WO |
| Entry |
|---|
| “About Ecast”, date unknown, leaflet. |
| Ahanger et al.; A Digital On-Demand Video Service Supporting Content-Based Queries; 1993; 9 pages. |
| Austin Cyber Limits: Name That Tune [online], [retrieved Jul. 23, 2001]. Retrieved from the Internet: <http://www.pbs.ork/klru/austin/games/namethattune.html>. |
| Back to the Tunes [online], [retrieved Jul. 23, 2001]. Retrieved from the Internet: <http://citc5.hispeed.com/rules.html>. |
| Bonczek et al, “The DSS Development System”, 1983 National Computer Conference, Anaheim, California, May 16-19, 1983, pp. 441-455. |
| Chan et al., “Distributed servers architectures for networked video services”, IEEE Trans on Networking, vol. 9, No. 2, pp. 125-136, 2001. |
| Chen et al., “Optimization of the grouped sweeping scheduling (GSS) with heterogeneous multimedia streams”, ACM Multimedia, pp. 1-7, 1993. |
| Crutcher et al., “The networked video Jukebox”, IEEE, Trans. on circuits and systems for video technology, vol. 4, No. 2, pp. 105-120, 1994. |
| Derfler et al., “How Networks Work”, Millennium Ed., Que Corporation, Jan. 2000. |
| Drews, C.; Pestoni, F.; “Virtual jukebox: reviving a classic,” Proceedings of the 35th Annual Hawaii International Conference System Sciences, pp. 887-893, Jan. 7-10, 2002. |
| “Ecast Forges Landmark International Technology Partnership”, Business Wire at www.findarticles.com/cf_0/m0EIN/2000_July_25/63663604/print.html, 2 pages, Jul. 25, 2000. |
| “Ecast Selects Viant to Build Siren Entertainment System (TM)”, ScreamingMedia, PR Newswire San Francisco, industry.java.sum.com/javanews/stories/story2/0,1072,17618,00.html, 3 pages, Aug. 3, 1999. |
| Fachbuch, “Unterhaltungselektronic von A-Z” gfu 1, VDE-Verlag GmbH, pp. 12-13, 1983-1984. |
| “Foobar 2000 Evaluation Updated,” MonkeyBiz, Aug. 3, 2008, 4 pages (with partial English translation). http://monkeybizinfo.blogspot.jp/2008/08/foobar2000.html. |
| Gallardo et al., “Tangible Jukebox: back to palpable music”, ACM TEI, pp. 199-202, 2010. |
| Gralla, “How the Internet Works”, Millennium Ed., Que Corporation, Aug. 1999. |
| Hewlett-Packard Development Co; HP Open View Storage Data Protector Admin's Guideline Manual Edition; May 2003; Copyright 2003, 60 pages http://h20000.www2.hp.com/bc/docs/support/SupportManual/c006637931/c00663793.pdf. |
| Hicks et al., “Dynamic software updating”, ACM PLDI, pp. 13-23, 2001. |
| IBM Technical Disclosure Bulletin, vol. 30, No. 5, Oct. 1987, “Method for Automated Assembly of Software Versions”, pp. 353-355. |
| IBM Technical Disclosure Bulletin, vol. 32, No. 9A, Feb. 1990, “Robotic Wafer Handling System for Class 10 Environments” pp. 141-143. |
| IBM Technical Disclosure Bulletin, vol. 41, No. 1, Jan. 1998, “Safe Mechanism for Installing Operating System Updates with Applications,” pp. 557-559. |
| ITouch 8 Plus brochure, JVL Corporation, 2005, 2 pages. |
| ITouch 27 New Games brochure, JVL Corporation, 2005, 2 pages. |
| Johnny Rockets Name That Tune [online], [retrieved Mar. 7, 2002]. Retrieved from the Internet: <http://www.johnnyrockets.com/docs/funstuff.html>. |
| Kozierok, The PC Guide, Site Version 2.2.0, http://www.pcguide.com, Apr. 17, 2001. |
| Kraiss et al., “Integrated document caching and prefetching in storage hierarchies based on Markov chain predictions”, The VLDB Journal, vol. 7, issue 3, pp. 141-162, 1998. |
| Liang et al., “Dynamic class loading in the Java virtual machine”, ACM OOPSLA, pp. 36-44, 1998. |
| Look and iTouch brochure, JVL Corporation, 2004, 2 pages. |
| Ludescher et al., “File Storage Management for TFTF physics data”, IEEE, pp. 856-859, 1992. |
| Megatouch Champ brochure, Merit Industries, Inc., 2005, 2 pages. |
| Melnik et al., “A mediation infrastructure for digital library services”, ACM DL, pp. 123-132, 2000. |
| Merriam Webster's Collegiate Dictionary, Tenth Edition, Merriam-Webster, Inc., p. 361 (definition of dynamically). |
| Merriam Webster's Collegiate Dictionary, Ninth Edition, Merriam Webster, Inc., p. 1148, 1986 (definition of “Stand”). |
| Mickey B's Jukebox Revue—Name That Tune! [online], [retrieved Jul. 23, 2001]. Retrieved from the Internet: <http://mickeyb.com/tune/>. |
| Mod Box Internet brochure, Merit Entertainment, 2006, 2 pages. |
| Newsome et al., “Proxy compilation of dynamically loaded java classes with MoJo”, ACM LCTES, pp. 204-212, Jun. 2002. |
| Patent Abstract of Japan vol. 95, No. 010 & JP 07 281682 A (Naguo Yuasa), Oct. 27 1 JP 07 281682, figure 1-6 abrége. |
| Peter Pawlowski, “Basic Player Whose Appearance and Functions can be Customized Freely ‘Foobar 2000’ v1.0 is Unveiled,”Windows Forest, Japan, Jan. 12, 2010, 3 pages (with partial English translation). http://forest.impress.co.jp/docs/news/20100112_ 341870.html. |
| Pohlmann, “Principles of Digital Audio”, Third Edition, 1995. |
| PR Newswire, Press Release, “MusicMatch Announces Commerical Availability of Meta Trust Certified MusicMatch jukebox”, New York; Nov. 15, 1999, extracted from Internet, http://proquest.umi.com on Sep. 17, 2002. |
| Rollins et al., “Pixie: A jukebox architecture to support efficient peer content exchange”, ACM Multimedia, pp. 179-188, 2002. |
| Schneier, “Applied Cryptography”, Second Edition, John Wiley & Sons, Inc. New York, 1996. |
| Sprague et al., “Music selection using the partyvote democratic Jukebox”, ACM AVI, pp. 433-436, 2008. |
| Stewart, “Ecast Deploys Marimba's Castanet to Power an Internet-Based, Entertainment Management System for the Out-of-Home Market”, Marimba, Press Release, 3 pages, www.marimba.com/news/releases/ecast.dec13.html, Dec. 13, 1999. |
| Strauss et al., “Information Jukebox a semi public device for presenting multimedia information content”, Pers. Ubiquit Comput, 7, pp. 217-220, 2003. |
| Tom & Liz's Name That Tune [online], [retrieved Jul. 23, 2001]. Retrieved from the Internet: <http://home.att.net/˜tomnliz/Music.html>. |
| Vortex Brochure, JVL Corporation, 2005, 2 pages. |
| Waingrow, “Unix Hints & Hacks”, Que Corporation, Indianapolis, IN, 1999. |
| White, “How Computers Work”, Millennium Ed., Que Corporation, Indianapolis, IN, Sep. 1999 (Sep. 22, 1999). |
| “Robotic Wafer Handling System for Class 10 Environments” IBM Technical Disclosure Bulletin, vol. 32, No. 9A, Feb. 1990, pp. 141-143. |
| “High-speed Opens and Shorts Substrate Tester”, IBM Technical Disclosure Bulletin, vol. 33, No. 12, May 1991, pp. 251-259. |
| “Darts Revolution Again”, Replay Magazine, Mar. 1991, pp. 146-148. |
| Galen A. Grimes, “Chapter 18, Taking Advantage or Web-based Audio.” |
| Petri Koskelainem “Report on Streamworks™”. |
| W. Richard Stevens, “TCP/IP Illustrated: vol. 1, the Protocols”. |
| Nowell Outlaw “Virtual Servers Offer Performance benefits for Networks Imaging”. |
| Notification of Re-Examination in Chinese Appln. No. 200610005134.8 Nov. 6, 2015. |
| Examiner's Report in related Canadian Application No. 2,881,503 dated Mar. 17, 2016. |
| European Examination Report dated Aug. 17, 2016 in European Appln No. 12 075 107.8. |
| Japanese Office Action in JP Appln. No. 2015-165266 mailed Oct. 18, 2016. |
| Canadian Office Action Application No. 2, 881,533 mailed Aug. 30, 2016. |
| Yuki Murata, iTunes no ‘Kankyo Settei’ Catalog & Tips 10 Sen, Mac People, ASCII Corporation, Oct. 1, 2007. |
| Number | Date | Country | |
|---|---|---|---|
| 20190318567 A1 | Oct 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60410832 | Sep 2002 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11902658 | Sep 2007 | US |
| Child | 16452088 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11727391 | Mar 2007 | US |
| Child | 11902658 | US | |
| Parent | 11358721 | Feb 2006 | US |
| Child | 11727391 | US | |
| Parent | 11222036 | Sep 2005 | US |
| Child | 11358721 | US | |
| Parent | 11185974 | Jul 2005 | US |
| Child | 11222036 | US | |
| Parent | 10661811 | Sep 2003 | US |
| Child | 11185974 | US |
