Source: http://www.google.com/patents/US20020174269?dq=6,757,682
Timestamp: 2017-01-23 17:15:23
Document Index: 655247973

Matched Legal Cases: ['art” 200', 'art” 220', 'art” 240', 'art” 260', 'art” 280', 'art” 300', 'art” 320', 'art” 330', 'art” 340', 'art” 360', 'art” 380', 'art” 390']

Patent US20020174269 - Proximity synchronizing audio gateway device - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA digital audio gateway device for use in a wireless network of digital audio playback devices. The gateway device is wirelessly linked to one or more digital audio playback devices to provide a gateway to the Internet for the digital audio playback devices. In addition to functioning as a gateway, the...http://www.google.com/patents/US20020174269?utm_source=gb-gplus-sharePatent US20020174269 - Proximity synchronizing audio gateway deviceAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS20020174269 A1Publication typeApplicationApplication numberUS 09/858,810Publication dateNov 21, 2002Filing dateMay 16, 2001Priority dateMay 16, 2001Also published asUS7890661, US20120030361, US20130073737, US20130080582Publication number09858810, 858810, US 2002/0174269 A1, US 2002/174269 A1, US 20020174269 A1, US 20020174269A1, US 2002174269 A1, US 2002174269A1, US-A1-20020174269, US-A1-2002174269, US2002/0174269A1, US2002/174269A1, US20020174269 A1, US20020174269A1, US2002174269 A1, US2002174269A1InventorsJeffrey Spurgat, Stephen Gladwin, Hoyet AndrewsOriginal AssigneeFullaudio CorporationExport CitationBiBTeX, EndNote, RefManPatent Citations (38), Referenced by (163), Classifications (21), Legal Events (17) External Links: USPTO, USPTO Assignment, EspacenetProximity synchronizing audio gateway device
BACKGROUND OF THE INVENTION [0002] 1. Field of the Invention [0003] The present invention relates to an audio gateway device and more particularly to an audio gateway device that is adapted to be used in a network of one or more digital audio playback devices which provides a gateway to the Internet for such digital audio playback devices and provides additional functionality such as synchronizing the digital audio content and playlists between the digital audio playback devices. [0004] 2. Description of the Prior Art [0005] A multitude of different devices for digital audio playback are known. Handheld or portable audio players, mobile as well as fixed audio players are known. Examples of such handheld audio players are compact disc (CD) players and MP3 players. Such mobile audio players include audio players, such as CD players, mounted in vehicles. Such mobile audio players are known to be mounted either in-dash in the vehicle or in the case of conversion vans and recreational vehicles in ceiling of the vehicle. Examples of fixed digital audio playback devices include stand-alone players and rack players that are adapted to connect to a home stereo system and to an AC power source. [0006] Digital audio content from the Internet is known to be downloaded onto storage devices, such as CDs, by way of a personal computer. Such Internet-based digital audio content has also been downloaded onto portable MP3 audio players. Although such systems allow selected digital audio content to be played when desired by the user, such systems only allow rather limited functionality. As such, various functions, such as interaction, communication and synchronizing the digital content on a plurality of digital audio players must be done manually. Thus, there is a need for system for providing increased functionality of various digital audio players. SUMMARY OF THE INVENTION [0007] Briefly, the present invention relates to a digital audio gateway device for use in a wireless network of digital audio playback devices. The gateway device is wirelessly linked to one or more digital audio playback devices to provide a gateway to the Internet for the digital audio playback devices. In addition to functioning as a gateway, the device provides additional functionality and may act as a cache of digital audio data for the various digital audio players connected in the wireless network and may also act to automatically update digital audio content on the audio players, synchronize digital audio content and playlists between the digital audio players and continue automatically or upon user request a particular playlist as the user moves from one digital audio player to another. BRIEF DESCRIPTION OF THE DRAWINGS [0008] These and other advantages of the present invention will be readily understood with reference to the following specification and attached drawings wherein: [0009] [0009]FIG. 1 is a block diagram of a digital audio communication system in accordance with the present invention. [0010] [0010]FIG. 2 is a block diagram of a digital audio gateway in accordance with the present invention. [0011] [0011]FIG. 3 is a block diagram of a wireless communication network which includes various digital audio players in accordance with the present invention. [0012] [0012]FIG. 4 is a block diagram of a system which utilizes a personal computing platform for communicating with a plurality of audio players. [0013] [0013]FIG. 5 is an alternate embodiment of the invention which illustrates the use of a television set top box as a communication link for communicating with a plurality of digital audio players in accordance with an alternate embodiment of the invention. [0014] [0014]FIG. 6 is a block diagram of an alternate embodiment of the invention which illustrates a communication system between a number of digital audio players and stand-alone audio gateway. [0015] [0015]FIG. 7 is a block diagram of a communication network between various digital audio players in accordance with another aspect of the present invention. [0016] [0016]FIG. 8 is a block diagram of the computing platform in accordance with the present invention. [0017] [0017]FIG. 9 is a block diagram of a stand-alone audio gateway in accordance with the present invention. [0018] [0018]FIG. 10 is a block diagram of a mobile digital audio player in accordance with the present invention. [0019] [0019]FIG. 11 is a block diagram of a fixed digital audio player in accordance with the present invention. [0020] [0020]FIG. 12 is a block diagram of a handheld or portable digital audio player in accordance with the present invention. [0021] [0021]FIG. 13 is a block diagram of an automotive digital audio player in accordance with the present invention. [0022] [0022]FIG. 14 is a block diagram of a rack player in accordance with the present invention. [0023] [0023]FIG. 15 is a block diagram of a stand-alone digital audio player in accordance with the present invention. [0024] [0024]FIG. 16 is a flow diagram of the audio gateway message handling in accordance with the present invention. [0025] [0025]FIG. 17 is a flow diagram of the audio gateway discovery in accordance with the present invention. [0026] [0026]FIG. 18 is a flow diagram of the audio gateway drop-out detection in accordance with the present invention. [0027] [0027]FIG. 19 is a flow diagram of the audio gateway content synchronization in accordance with the present invention. [0028] [0028]FIG. 20 is a flow diagram of the audio gateway playlist continuation in accordance with the present invention. [0029] [0029]FIG. 21 is a flow diagram of the player message handling in accordance with the present invention. [0030] [0030]FIGS. 22 and 23 are flow diagrams of the player discovery in accordance with the present invention. [0031] [0031]FIG. 24 is a flow diagram of the player drop-out detection in accordance with the present invention. [0032] [0032]FIG. 25 is a flow diagram of the player content synchronization in accordance with the present invention. [0033] [0033]FIGS. 26 and 27 are flow diagrams of the player playlist continuation feature in accordance with the present invention.
DETAILED DESCRIPTION [0034] The present invention is adapted to provide additional functionality of digital audio players. For example, in one embodiment, as illustrated in FIG. 1, a computing platform 103, for example, a personal computer, is used as a gateway to enable various digital audio players 115 and 116 to be connected to the Internet or other computer network 102. In this embodiment, the computing platform 103 may be configured to access one or more servers 100 on the Internet or other computer network 102 that contain digital audio content and other information 101, such as artists, track names, album names, lyrics, and playlists, among other things. Though the computing platform 103 can act as a digital audio player by itself, in this embodiment of the invention, the computing platform 103 acts as an audio gateway for various digital audio players 115 and 116, and can additionally provide caching of the digital audio content and other information 101 for the digital audio players 115 and 116 from the servers 100 that are connected to the computing platform 103 through the Internet or other computer network 102. Using a wireless network or wireless communication platform 104, the computing platform 103 is adapted to communicate with various digital audio players, such as one or more mobile digital audio players 115 and fixed digital audio players 116 that are within range of the wireless network or wireless communication platform 104 forming a local wireless network as generally illustrated in FIG. 3. [0035] Various devices are contemplated for use as audio gateways, for example, as shown in FIG. 2. In one embodiment, a personal computer 105 coupled to an internal or external wireless communication network or wireless communication platform 104, for example, an access point 106, is used as an audio gateway. Alternatively, a set top box 107 with a wireless network or wireless communication platform 104, coupled to a conventional TV 108, may be used as an audio gateway. A stand alone audio gateway 109 may also be formed from a wireless network or wireless communication platform 104. Other embodiments of an audio gateway are also contemplated. For example, any device with a wireless network or wireless communication platform 104, either public or private, may be used. [0036] In another embodiment of the invention, the computing platform 103 may be configured to automatically synchronize, or upon request, copy, add or remove digital audio content and other information 101, such as playlists, on mobile digital audio players 115 and fixed digital audio players 116. The computing platform 103 may also be used to control mobile digital audio players 115 and fixed digital audio players 116 by changing the current playlist or the currently playing digital audio content, among other things, on the mobile digital audio players 115 or fixed digital audio players 116. [0037] In another embodiment of the invention as illustrated in FIG. 7, the system enables communication between various digital audio players, such as the digital audio players 110-113. This embodiment may be also incorporated with a computing platform 103, for example, acting as a gateway, as discussed above, or alternatively using the computing platform 103 for synchronization among the various digital audio players 110-113 or other functions, such as those discussed above. Audio Gateway [0038] FIGS. 4-6 represent an exemplary network configuration, utilizing different audio gateways for enabling connection of the digital audio players 110-113 to the Internet or other computer network 102. These examples are by no means the only possible configurations that support the invention and do not necessarily cover all aspects of the invention. Personal Computer and Digital Audio Players Configuration [0039] The first exemplary configuration, shown in FIG. 4, uses a personal computer 105 as the audio gateway. The personal computer 105 connects to the Internet or other computer network 102 using a conventional network interface or modem 137. The personal computer 105 is thus able to download digital audio content and other information 101 from the server 100 (FIG. 1) connected to the Internet or other computer network 102. The digital audio content and other information 101, such as artists, track names, album names, lyrics, and playlists, can then be stored in a persistent storage 133 (FIG. 8), such as a hard drive, on the personal computer 105. The user can also create new playlists using the personal computer 105. [0040] In this embodiment, a wireless access point 106 is used to access the wireless network or wireless communication platform 104. The wireless network or wireless communication platform 104 is used by the personal computer 105, acting as the audio gateway, to communicate with mobile digital audio players 115 and fixed digital audio [0041] players 116. The personal computer 105, using the wireless network or wireless communication platform 104, is able to, either automatically or at user request, pass the digital audio content and other information 101, including new playlists, to mobile digital audio players 115 and fixed digital audio players 116. If a fixed digital audio player 116, such as a stand-alone player 112 or a rack player 113 that connects to a stereo 114, happens to be turned off at the time, then the personal computer 105 is able to automatically detect the next time the fixed digital audio player 116 is turned on. When the personal computer 105 detects that a fixed digital audio player 116 has just turned on, then the personal computer 105 can pass the digital audio content and other information 101 to the fixed digital audio player 116 at that time. Mobile digital audio players 115, such as automotive players 110 and handheld players 111, may be out of range of the wireless network or wireless communication platform 104 during normal use. When a mobile digital audio player 115 comes into range of the wireless network or wireless communication platform 104, the personal computer 105, acting as an audio gateway, can automatically detect the mobile digital audio player 115 and pass the digital audio content and other information 101 at that time. [0042] In addition, the personal computer 105 can, either automatically or upon user request, determine the current playlist and current position within the playlist on a particular mobile digital audio player 115 or fixed digital audio player 116. Then the personal computer 105 can propagate this playlist information to any other mobile digital audio players 115 and fixed digital audio players 116 that are on and in range. This allows a user to move from one mobile digital audio player 115 or fixed digital audio player 116 to another mobile digital audio player 115 or fixed digital audio player 116 and automatically be able to continue the same music and playlist in a seamless manner. Set-Top Box and Digital Audio Players Configuration [0043] Another exemplary configuration, shown in FIG. 5, uses a set-top box 107 as the audio gateway. The set-top box 107 can connect to the Internet or other computer network 102 either through the same cable or by way of a satellite connection that provides the analog or digital audio or video 151 (FIG. 8) that is passed to an audio or video playback device, such as a television set 108, or through an internal or external network interface or modem 137. The set-top box 107 can thus download digital audio content and other information 101 from a server 100, connected to the Internet or other computer network 102. The digital audio content and other information 101, such as artists, track names, album names, lyrics, and playlists, can then be stored in persistent storage 133, such as a hard drive or flash memory, on the set-top box 107. [0044] In this embodiment, a wireless network interface or wireless communication interface 141 is used to handle the wireless network or wireless communication platform 104. The set-top box 107, acting as the audio gateway, uses the wireless network or wireless communication platform 104 to communicate with mobile digital audio players 115 and the fixed digital audio players 116. The set-top box 107, using the wireless network or wireless communication platform 104, is able to, either automatically or upon user request, pass the digital audio content and other information 101 to mobile digital audio players 115 and fixed digital audio players 116. [0045] If a fixed digital audio player 116, such as a stand-alone player 112 or a rack player 113 that connects to a stereo 114, happens to be turned off at the time, then the set-top box 107 is able to automatically detect the next time the fixed digital audio player 116 is turned on. When the set-top box 107 detects that a fixed digital audio player 116 has just turned on, then the set-top box 107 can pass the digital audio content and other information 101 to the fixed digital audio player 116 at that time. Mobile digital audio players 115, such as automotive players 110 and handheld players 111, are typically out of range of the wireless network or wireless communication platform 104 during normal use. [0046] When a mobile digital audio player 115 comes into range of the wireless network or wireless communication platform 104, the set-top box 107, acting as an audio gateway, can automatically detect the mobile digital audio player 115 and pass the digital audio content and other information 101 at that time. In addition, the set-top box 107 can determine, either automatically or upon user request, the current playlist and current position within the playlist on a particular mobile digital audio player 115 or fixed digital audio player 116. Then the set-top box 107 can propagate this playlist information to any other mobile digital audio players 115 and fixed digital audio players 116 that are on and in range. This allows a user to move from one mobile digital audio player 115 or fixed digital audio player [0047] [0047]116 to another mobile digital audio player 115 or fixed digital audio player 116 and automatically be able to continue the same music and playlist in a seamless manner. Stand-Alone Gateway and Digital Audio Players Configuration [0048] Another exemplary configuration, shown in FIG. 6, uses a stand-alone audio gateway 109 as the audio gateway. The stand-alone audio gateway 109 connects to the Internet or other computer network 102 using a network interface or modem 137. The stand-alone audio gateway 109 can download digital audio content and other information 101 from a server 100 connected to the Internet or other computer network 102. The digital audio content and other information 101, such as artists, track names, album names, lyrics, and playlists, can then be stored in persistent storage 133, such as a hard drive or flash memory, on the stand-alone audio gateway 109. In this embodiment, a wireless network interface or wireless communication interface 141 (FIG. 8) is used to handle the wireless network or wireless communication platform 104. The wireless network or wireless communication platform 104 is used by the stand-alone audio gateway 109 to communicate with mobile digital audio players 115 and fixed digital audio players 116. The stand-alone audio gateway 109, using the wireless network or wireless communication platform 104, is able to, either automatically or at user request, pass the digital audio content and other information 101 to mobile digital audio players 115 and fixed digital audio players 116. If a fixed digital audio player 116, such as a stand-alone player 112 or a rack player 113 that connects to a stereo 114, happens to be turned off at the time, then the stand-alone audio gateway 109 is able to automatically detect the next time the fixed digital audio player 116 is turned on. When the stand-alone audio gateway 109 detects that a fixed digital audio player 116 has just turned on, then the stand-alone audio gateway 109 can pass the digital audio content and other information 101 to the fixed digital audio player 116 at that time. [0049] Mobile digital audio players 115, such as automotive players 110 and portable or handheld players 111, may be out of range of the wireless network or wireless communication platform 104 during normal use. When a mobile digital audio player 115 comes into range of the wireless network or wireless communication platform 104, the stand-alone audio gateway 109 can automatically detect the mobile digital audio player 115 and pass the digital audio content and other information 101 at that time. [0050] In addition, the stand-alone audio gateway 109 can, either automatically or upon user request, determine the current playlist and current position within the playlist on a particular mobile digital audio player 115 or fixed digital audio player 116. Then the stand-alone audio gateway 109 can propagate this playlist information to any other mobile digital audio players 115 and fixed digital audio players 116 that are on and in range. This allows a user to move from one mobile digital audio player 115 or fixed digital audio player 116 to another mobile digital audio player 115 or fixed digital audio player 116 and automatically be able to continue the same music and playlist in a seamless manner. Local Wireless Network [0051] In another embodiment, shown in FIG. 3, a local wireless network is formed which enables wireless communication between a host, such as a personal computer 105, a stand alone audio gateway 109, a set top box 107, and various digital audio players, such as mobile digital audio players 115, fixed digital audio players 116, a stand alone audio gateway 109 and a set top box 107, for example, configured in a star topography. As shown, various audio gateways are used to establish the network. However, in this embodiment, audio gateways, which contain a wireless network or wireless communication platform 104 as discussed above, are used primarily for establishing network communication and may or may not be connected to a remote server 100. [0052] Wireless communications between the computing platform 103 and mobile digital audio players 115 and fixed digital audio players 116, can be done using industry standard wireless communications and networking technology, such as Bluetooth, HomeRF, and IEEE 802.11. In addition, with respect to this invention, a proprietary wireless communications technology may also be used for wireless communications. Use of the wireless network or wireless communication platform 104 by computing platforms 103, mobile digital audio players 115, and fixed digital audio players 116 may be handled as an internal or external peripheral in the form of a wireless network interface or wireless communication interface 141. The wireless network or wireless communication platform 104 may also require an external wireless access point 106 to handle or facilitate wireless communications and to act as a bridge between the wireless network and wired networking connections, such as may be used by a personal computer 105. Communication Between Digital Audio Players [0053] [0053]FIG. 7 illustrates a wireless network configuration which enables communication directly among various digital audio players without a host. The various digital audio players, such as mobile digital audio players 115 and fixed digital audio players 116, use the same wireless network or wireless communication platform 104 that is used to wirelessly communicate with the computing platform 103, to communicate with each other. The wireless communication between the various digital audio players may be handled by an internal or external wireless network interface or wireless communication interface 141 (FIGS. 10 and 11) in each of the disposed digital audio players. In this embodiment, communication between the various digital audio players include directly passing digital audio content and other information 101, including playlists from, for example, one mobile digital audio player 115 or fixed digital audio player 116 to another. Computing and Player Architectures [0054] [0054]FIGS. 8 and 9 illustrate architectures for the computing platform and standalone audio gateway platforms. FIGS. 10-15 illustrate the architectures for the various digital audio player platforms. As shown, the architecture of the various platforms is similar. Thus, like reference numbers are used for like components for clarity. Computing Platform [0055] [0055]FIG. 8 illustrates the typical system architecture of a computing platform 103, which can encompass anything from general-purpose devices, such as personal computers 105, to open fixed function devices, such as set-top boxes 107 or stand-alone audio gateways 109, among others. In general, the computing platform 103 has a main processor 130, such as an Intel Pentium III, for executing various software components. The various software instructions are typically stored in read only memory, or ROM, or flash memory 136, or local storage 132. The local storage 132 can consist of persistent storage 133, such as hard drives or flash memory, or removable storage 134, such as floppy drives, CD-ROM drives, or DVD drives. The software instructions may be executed by the main processor 130 directly from their storage location or loaded into random access memory or RAM 135 to be executed from RAM 135 by the main processor 130. The local storage 132 can also be used to cache digital audio content and other information 101. [0056] The computing platform 103 uses a network interface or modem 137 to access servers 100 on the Internet or other computer network 102, in order to download digital audio content or other information 101. The network interface or modem 137, for example, a 3COM Etherlink 10/100 PCI network interface card, may be connected internally or externally to the computing platform 103 using a system bus or peripheral bus 131. The system bus and peripheral buses 131 are provided for connecting internal and external devices to the computing platform 103 in a standard manner. Typical system and peripheral buses 131 include Universal Serial Bus, commonly referred to as USB, IEEE 1394 bus, commonly referred to as FireWire, and Peripheral Connect Interface, commonly referred to as PCI. [0057] The computing platform 103 also supports connection through a user input interface 142 to external or integrated user input devices 153, such as keyboards and mice. In order to provide for output to the user, the computing platform 103 may also contain a display controller 138, for example, an NVIDIA Model No. GeForce2, which stores graphical data such as windows, bitmaps and text. The display controller 138 outputs the graphical data in a video output 150 format that is typically displayed to the user on a video monitor, television 108, or LCD panel. In addition to video output 150, the computing platform 103 can provide audio output 152, which is handled by audio playback hardware 140. [0058] For a computing platform 103 that is acting as a set-top box 107, the computing platform 103 will likely also contain an analog or digital audio and video decoder 139, for example, a C-Cube Model No. AViA 600, hereby incorporated by reference. The analog or digital audio and video decoder 139 decodes the analog or digital audio or video 151 from sources such as cable or satellite, and passes the audio output 152 and video output 150 to an audio and video playback device, such as a television set 108. [0059] For wireless communication with other computing platforms 103, and various digital audio players, such as mobile digital audio players 115, and fixed digital audio players 116 on a wireless network or wireless communication platform 104, the computing platform 103 uses an internal or external wireless network interface or wireless communication interface 141. It should be noted that a computing platform 103 is not limited to the capabilities and features listed in this description, but may contain a subset of the described features or may contain additional capabilities or features not listed. Gateway Platform [0060] [0060]FIG. 9 demonstrates some of the unique capabilities of the stand-alone audio gateway 109, though this example is by no means complete or exhaustive in its coverage of the possible options for a stand-alone audio gateway 109. In particular, the stand-alone audio gateway 109 acts as a fixed function device, whose main purpose is to be an audio gateway. The fixed function nature of the stand-alone audio gateway 109 is unlike the personal computer 105, which exists as a general-purpose computing device. The stand-alone audio gateway 109 is able to connect to the Internet or other computer network 102 using an internal or external network interface or modem 137. The stand-alone audio gateway 109 is able to cache digital audio content and other information 101 downloaded from a server 100 connected to the Internet or other computer network 102 into persistent storage 133, such as a hard drive, on the stand-alone audio gateway 109. [0061] [0061]FIG. 9 illustrates a typical system architecture of the stand-alone audio gateway 109. In general, the stand-alone audio gateway 109 has a main processor 130 for executing various software components. The various software components are typically stored in read only memory, or ROM, or flash memory 136, or local storage 132. Local storage 132 can consist of persistent storage 133, such as hard drives or flash memory, or removable storage 134 such as floppy drives, CD-ROM drives, or DVD drives. The software components are executed by the main processor 130 directly from their storage location or are loaded into random access memory or RAM 135, to be executed from RAM 135 by the main processor 130. Local storage 132 can also be used to cache digital audio content and other information 101. The stand-alone audio gateway 109 uses a network interface or modem 137 to access servers 100 on the Internet or other computer network 102, in order to download digital audio content or other information 101. The network interface or modem 137 is connected internally or externally to the stand-alone audio gateway 109 using a system bus or peripheral bus 131. The system bus and peripheral buses 131 are provided for connecting internal and external devices to the stand-alone audio gateway 109 in a standard manner. Typical system and peripheral buses 131 include Universal Serial Bus, commonly referred to as USB, IEEE 1394, commonly referred to as FireWire, and Peripheral Connect Interface, commonly referred to as PCI. The stand-alone audio gateway 109 also supports connection through a user input interface 142 to external or integrated user input devices 153, such as buttons, keyboards and mice. For output to the user, the stand-alone audio gateway 109 may contain a display controller 138, which stores display data such as windows, bitmaps and text. The display controller 138 outputs the display data in a video output 150 format that is typically displayed to the user on a video monitor, television 108, or LCD panel. In addition to video output 150, the stand-alone audio gateway 109 can provide audio output 152, which is handled by audio playback hardware 140. For wireless communication with mobile digital audio players 115, and fixed digital audio players 116 on a wireless network or wireless communication platform 104, the stand-alone audio gateway 109 uses an internal or external wireless network interface or wireless communication interface 141. It should be noted that a stand-alone audio gateway 109 is not limited to the capabilities and features listed in this description, but may contain a subset of the described features or may contain additional capabilities or features not listed. Mobile Player [0062] Many different types of mobile digital audio players 115 are suitable for use with the present invention. FIG. 10 demonstrates the general architecture for a mobile digital audio player 115. In general, a mobile digital audio player 115 has a processor 155 that is responsible for executing various software and firmware components. The various software and firmware components are typically stored in read only memory, or ROM, or flash memory 158 or in player storage 156, such as a hard drive, flash memory, or removable media. The software and firmware components are executed by the processor 155 directly from their storage location or are loaded into random access memory or RAM 157 to be executed from RAM 157 by the processor 155. Player storage 156 can also be used for storing digital audio content and other information 101, such as artists, track names, album names, lyrics, and playlists, for later playback and presentation to the user. Typically, the digital audio content 101 is in some encoded format. The audio decoder 162 decodes the digital audio content 101 and passes it to the audio digital to analog converter 163, or DAC. The audio DAC 163 converts the decoded audio to analog and then provides audio output 166 from the mobile digital audio player 115. The audio output 166 of a mobile digital audio player 115 is typically passed to an amplifier or headphones. Communication using a wireless network or wireless communication platform 104 by the mobile digital audio player 115 with a computer platform 103, other mobile digital audio players 115, and fixed digital audio players 116 is done using an internal or external wireless network interface or wireless communication interface 141. For input from the user, the mobile digital audio player 115 contains user inputs 165, such as buttons or a touch screen. The user input interface 164 handles the actual interface with the user inputs 165, while interpretation of these inputs are typically handled by software and firmware running on the processor 155. For output to the user, the mobile digital audio player 115 may contain a display controller 160, which can provide text and possibly graphical output to the user on an LCD display 161. Tying of the functional components and processor 155 together is typically done using a system bus and peripheral buses 159. Examples of system and peripheral buses 159 include Universal Serial Bus, commonly referred to as USB, IEEE 1394, commonly referred to as FireWire, and Peripheral Connect Interface, commonly referred to as PCI. It should be noted that some of the functional blocks described might encompass multiple physical components. As well, multiple functional blocks may be contained in a single physical component. It should also be noted that a mobile digital audio player 115 is not limited to the capabilities and features listed in this description, but may contain a subset of the described features or may contain additional capabilities or features not listed. Fixed Player [0063] There are many different types of fixed digital audio players 116. FIG. 11 demonstrates the general architecture for a fixed digital audio player 116. In general, a fixed digital audio player 116 has a processor 155 that is responsible for executing various software and firmware components. The various software and firmware components are typically stored in read only memory, or ROM, or flash memory 158 or in player storage 156, such as a hard drive, flash memory, or removable media. The software and firmware components are executed by the processor 155 directly from their storage location or are loaded into random access memory or RAM 157 to be executed from RAM 157 by the processor 155. Player storage 156 can also be used for storing digital audio content and other information 101, such as artists, track names, album names, lyrics, and playlists, for later playback and presentation to the user. Typically, the digital audio content 101 is in some encoded format. The audio decoder 162 decodes the digital audio content 101 and passes it to the audio digital to analog converter 163, or DAC. The audio DAC 163 converts the decoded audio to analog and then provides audio output 167 from the fixed digital audio player 116. The audio output 167 of a fixed digital audio player 116 is typically passed to a stereo, amplifier, speakers or headphones. Communication using a wireless network or wireless communication platform 104 by the fixed digital audio player 116 with a computing platform 103, mobile digital audio players 115, and other fixed digital audio players 116, is done using an internal or external wireless network interface or wireless communication interface 141. For input from the user, the fixed digital audio player 116 contains user inputs 165, such as buttons or a touch screen. The fixed digital audio player 116 may also receive infrared input 168 from a remote control. The user input interface 164 handles the actual interface with the user inputs 165 and the infrared input 168, while interpretation of these inputs are typically handled by software and firmware running on the processor 155. For output to the user, the fixed digital audio player 116 may contain a display controller 160, which can provide text and possibly graphical output to the user on an LCD display 161. Tying of the functional components and processor 155 together is typically done using a system bus and peripheral buses 159. Examples of system and peripheral buses 159 include Universal Serial Bus, commonly referred to as USB, IEEE 1394, commonly referred to as FireWire, and Peripheral Connect Interface, commonly referred to as PCI. It should be noted that some of the functional blocks described might encompass multiple physical components. As well, multiple functional blocks may be contained in a single physical component. It should also be noted that a fixed digital audio player 116 is not limited to the capabilities and features listed in this description, but may contain a subset of the described features or may contain additional capabilities or features not listed. Handheld Player [0064] Many different types of mobile digital audio players 115 are suitable for use with the present invention. For example, FIG. 12 illustrates the general architecture for the handheld player 111. In general, the handheld player 111 includes a processor 155 for executing various software and firmware instructions. The various software and firmware instructions may be stored in read only memory, or ROM, or flash memory 158 or in player storage 156, such as a hard drive, flash memory, or removable media. The software and firmware instructions are executed by the processor 155 directly from their storage location or are loaded into random access memory or RAM 157 to be executed from RAM 157 by the processor 155. Player storage 156 can also be used for storing digital audio content and other information 101, such as artists, track names, album names, lyrics, and playlists, for later playback and presentation to the user. Typically, the digital audio content 101 is in some encoded format. The audio decoder 162, for example, a Texas Instruments digital signal processor, Model No. TMS320VC5416, decodes the digital audio content 101 and passes it to the audio digital to analog converter 163, or DAC. The audio DAC 163, for example, a Texas Instruments Model No. TLC320AD77C converts the decoded audio to analog and then provides audio output 166 from the handheld player 111. The audio output 166 of a handheld player 111 may be used to drive headphones. [0065] Communication using a wireless network or wireless communication platform 104 by the handheld player 111 with the computing platforms 103, other mobile digital audio players 115, and fixed digital audio players 116 is done using an internal or external wireless network interface or wireless communication interface 141. For input from the user, the handheld player 111 contains user inputs 165, such as buttons or a touch screen. The user input interface 164 handles the actual interface with the user inputs 165, while interpretation of these inputs are typically handled by software and firmware running on the processor 155. For output to the user, the handheld player 111 may contain a display controller 160, for example, an embedded display controller in a Motorola MC68EZ328 controller, which can provide text and possibly graphical output to the user on an LCD display 161. Tying of the functional components and processor 155 together is typically done using a system bus and peripheral buses 159. Examples of system and peripheral buses 159 include Universal Serial Bus, commonly referred to as USB, IEEE 1394, commonly referred to as FireWire, and Peripheral Connect Interface, commonly referred to as PCI. It should be noted that some of the functional blocks described might encompass multiple physical components. As well, multiple functional blocks may be contained in a single physical component. It should also be noted that a handheld player 111 is not limited to the capabilities and features listed in this description, but may contain a subset of the described features or may contain additional capabilities or features not listed. Automotive Player [0066] Another type of mobile digital audio player 115 is the automotive player 110, whose general architecture is shown in FIG. 13. In general, the automotive player 110 includes a processor 155 that is responsible for executing various software and firmware instructions. The various software and firmware components are typically stored in read only memory, or ROM, or flash memory 158 or in player storage 156, such as a hard drive, flash memory, or removable media. The software and firmware instructions are executed by the processor 155 directly from their storage location or are loaded into random access memory or RAM 157 to be executed from RAM 157 by the processor 155. Player storage 156 can also be used for storing digital audio content and other information 101, such as artists, track names, album names, lyrics, and playlists, for later playback and presentation to the user. [0067] Typically, the digital audio content 101 is in some encoded format. The audio decoder 162 decodes the digital audio content 101 and passes it to the audio digital to analog converter 163 or DAC. The audio DAC 163 converts the decoded audio to analog and then provides audio output 167 from the automotive player 110. The audio output 167 of an automotive player 110 typically feeds a conventional audio amplifier, which then drives the car speakers. Communication using a wireless network or wireless communication platform 104 by the automotive player 110 with computing platforms 103, other mobile digital audio players 115, and fixed digital audio players 116 is done using an internal or external wireless network interface or wireless communication interface 141. [0068] For input from the user, the automotive player 110 contains user inputs 165, such as buttons or a touch screen. The user input interface 164 handles the actual interface with the user inputs 165, while interpretation of these inputs are typically handled by software and firmware running on the processor 155. In addition, an automotive player 110 may support voice commands for user input. If voice commands are supported, a microphone 174 is used to feed analog audio to the audio analog to digital converter 173, which converts the analog audio to digital. Then, the audio capture hardware 172 and the processor 155 will interpret the voice commands from the user. For output to the user, the automotive player 110 may contain a display controller 160, which can provide text and possibly graphical output to the user on an LCD display 161. Tying of the functional components and processor 155 together may be accomplished by way of a system bus and peripheral buses 159. Examples of suitable system and peripheral buses 159 include Universal Serial Bus, commonly referred to as USB, IEEE 1394, commonly referred to as FireWire, and Peripheral Connect Interface, commonly referred to as PCI. [0069] It should be noted that some of the functional blocks described might encompass multiple physical components. As well, multiple functional blocks may be contained in a single physical component. It should also be noted that an automotive player 110 is not limited to the capabilities and features listed in this description, but may contain a subset of the described features or may contain additional capabilities or features not listed. Rack Player [0070] There are many different types of fixed digital audio players 116. FIG. 14 demonstrates the general architecture for a rack player 113. In general, a rack player 113 includes a processor 155 that is responsible for executing various software and firmware instructions. The various software and firmware instructions may be stored in read only memory, or ROM, or flash memory 158 or in player storage 156, such as a hard drive, flash memory, or removable media. The software and firmware instructions may be executed by the processor 155 directly from their storage location or loaded into random access memory or RAM 157 to be executed from RAM 157 by the processor 155. Player storage 156 can also be used for storing digital audio content and other information 101, such as artists, track names, album names, lyrics, and playlists, for later playback and presentation to the user. Typically, the digital audio content 101 is in some encoded format. The audio decoder 162 decodes the digital audio content 101 and passes it to the audio digital to analog converter 163, or DAC. The audio DAC 163 converts the decoded audio to analog and then provides audio output 167 from the rack player 113. The audio output 167 of a rack player 113 typically is passed to a stereo system 114. Communication using a wireless network or wireless communication platform 104 by the rack player 113 with computing platforms 103, mobile digital audio players 115, and other fixed digital audio players 116 is done using an internal or external wireless network interface or wireless communication interface 141. For input from the user, the rack player 113 contains user inputs 165, such as buttons or a touch screen. The rack player 113 may also receive infrared input 168 from a remote control. The user input interface 164 handles the actual interface with the user inputs 165 and the infrared input 168, while interpretation of these inputs are typically handled by software and firmware running on the processor 155. For output to the user, the rack player 113 may contain a display controller 160, which can provide text and possibly graphical output to the user on an LCD display 161. Tying connection of the functional components and processor 155 together may be accomplished by way of a system bus and peripheral buses 159. Examples of suitable system and peripheral buses 159 include Universal Serial Bus, commonly referred to as USB, IEEE 1394, commonly referred to as FireWire, and Peripheral Connect Interface, commonly referred to as PCI. [0071] It should be noted that some of the functional blocks described might encompass multiple physical components. As well, multiple functional blocks may be contained in a single physical component. It should also be noted that a rack player 113 is not limited to the capabilities and features listed in this description, but may contain a subset of the described features or may contain additional capabilities or features not listed. Stand-alone Player [0072] Another type of fixed digital audio player 116 is the stand-alone player 112, whose general architecture is shown in FIG. 15. In general, a stand-alone player 112 includes a processor 155 that is responsible for executing various software and firmware instructions. The various software and firmware components are typically stored in read only memory, or ROM, or flash memory 158 or in player storage 156, such as a hard drive, flash memory, or removable media. The software and firmware components are executed by the processor 155 directly from their storage location or are loaded into random access memory or RAM 157 to be executed from RAM 157 by the processor 155. Player storage 156 can also be used for storing digital audio content and other information 101, such as artists, track names, album names, lyrics, and playlists, for later playback and presentation to the user. Typically, the digital audio content 101 is in some encoded format. The audio decoder 162 decodes the digital audio content 101 and passes it to the audio digital to analog converter 163, or DAC. The audio DAC 163 converts the decoded audio to analog. The analog audio from a stand-alone player 112 typically directly drives speakers 170 attached to the stand-alone player 112. Communication using a wireless network or wireless communication platform 104 by the stand-alone player 112 with computing platforms 103, mobile digital audio players 115, and other fixed digital audio players 116 is done using an internal or external wireless network interface or wireless communication interface 141. For input from the user, the stand-alone player 112 contains user inputs 165, such as buttons or a touch screen. The stand-alone player 112 may also receive infrared input 168 from a remote control. The user input interface 164 handles the actual interface with the user inputs 165 and the infrared input 168, while interpretation of these inputs are typically handled by software and firmware running on the processor 155. For output to the user, the stand-alone player 112 may contain a display controller 160, which can provide text and possibly graphical output to the user on an LCD display 161. Connection of the functional components and processor 155 together is typically done using a system bus and peripheral buses 159. Examples of suitable system and peripheral buses 159 include Universal Serial Bus, commonly referred to as USB, IEEE 1394, commonly referred to as FireWire, and Peripheral Connect Interface, commonly referred to as PCI. [0073] It should be noted that some of the functional blocks described might encompass multiple physical components. As well, multiple functional blocks may be contained in a single physical component. It should also be noted that a stand-alone player 112 is not limited to the capabilities and features listed in this description, but may contain a subset of the described features or may contain additional capabilities or features not listed. Audio Gateway Software [0074] FIGS. 16 to 20 provide flow diagrams for the audio gateway embodiment of this invention. In these flow diagrams, the software is assumed to be running in a multitasking environment, with each of the flow diagrams representing a particular independently running task or process. However, it should be noted that these flow diagrams represent only one of many different ways to implement the key software functionality for the audio gateway and that many other implementations are possible, including those which do not require a multitasking environment. Audio Gateway Message Handling Flow [0075] [0075]FIG. 16 provides the flow diagram of the message handler for the audio gateway. In general, the message handler takes the messages received from other computing platforms 103, mobile digital audio players 115, and fixed digital audio players 116 on the wireless network or wireless communication platform 104 and queues these messages for use by other processes or handles them itself, depending on the message type. In this embodiment, the message handler is a continuously running process. The step, “Start” 200, represents the beginning of the message handling process. The message handler checks if there is a message received in step 201. [0076] If a message has been received, the message handler then checks to see what type of message it is, among many possible types, as indicated in steps 202-212. After the message handler determines the type of message, an appropriate response is queued and the system returns to step 201 and checks for additional messages. If the message is a broadcast response message from a player 202, then the message handler queues the broadcast response message 203. If the message is a query response message from a player 204, then the message handler queues the query response message in step 205. If the message is a poll response message from a player 206, then the message handler queues the poll response message in step 207. If the message is a playlist response message from a player 208, then the message handler queues the playlist response message in step 209. If the message is a content response message from a player 210, then the message handler queues the content response message in step 211. If the message is a content acknowledge message from a player 212, then the message handler queues the content acknowledge message in step 213. If the message was none of those previously checked for, the message handler handles or queues any other messages as necessary 214. Audio Gateway Discovery Flow [0077] Discovery of mobile digital audio players 115 and fixed digital audio players 116 within range of the audio gateway, on the wireless network or wireless communication platform 104, is an important capability with respect to this invention. FIG. 17 provides the flow diagram for discovery by the audio gateway of mobile digital audio players 115 and fixed digital audio players 116. In this example, the audio gateway discovery handler is a continuously running process. The step “Start” 220, represents the beginning of the discovery handling process. In order to get a message response from the mobile digital audio players 115 and fixed digital audio players 116, the discovery handler sends a broadcast for players message in step 221. The discovery handler then waits, with a timeout, for example, 5 seconds, for a broadcast response message from any players in step 222. The discovery handler then checks if there is a player broadcast response message in the queue in step 223. If there is no response, then the discovery handler broadcasts again for players. If there is a response, then the discovery handler sends a query player message to a responding player in step 224 to get information about the type of player that has responded. The discovery handler then waits, with some timeout, for a player query response message in step 225 from the player that previously responded to the broadcast. The discovery handler then checks if there is a query response message in the queue in step 226. If there is no response, then the discovery handler broadcasts again for players. If there is a response, then the discovery handler checks the information returned in the query response message to see if the player is already known in step 227. If the player is already known, then the discovery handler broadcasts again for players. However, a player is unlikely to respond to a broadcast from an audio gateway when the player and audio gateway already know about each other. If the player is not already known, then the discovery handler adds the player to the list of players in proximity in step 228 of the audio gateway. Finally, the discovery handler flags the new player in proximity for playlist continuation in step 229 and for content synchronization in step 230. This allows the playlist continuation handler in the audio gateway to capture the current playlist and current selection from this new player for possible broadcast to other players. Also, this allows the content synchronization handler in the audio gateway to automatically download digital audio content and other information 101 cached on the audio gateway to the new player. Audio Gateway Dropout Detection Flow [0078] The flow diagram for audio gateway detection of dropout of players is shown in FIG. 18. The dropout detection handler in the audio gateway polls players that are known to be in proximity in order to see if any of the players has possibly gone out of range of the wireless network or wireless communication platform 104 or has been turned off. In this example, the dropout detection handler is a continuously running process. The step, “Start” 240, represents the beginning of the dropout detection handling process. The dropout detection handler checks the list of players in proximity 241 maintained by the audio gateway. If there are players in proximity as determined in step 242, then the dropout detection handler sends a poll message to the next player in proximity in the proximity list in step 243. This allows all the players in the list of players in proximity to be checked in a sequential manner. Then the dropout detection handler waits, with some timeout, for a poll response message from the player in step 244 that was sent the poll message in step 243. If there is no poll response message from the player in the queue in step 245 then the dropout detection handler checks if the player is already flagged as possibly being out of range in step 246 of the wireless network or wireless communication platform 104. If the player is not already flagged as possibly out of range 246, then the dropout detection handler flags that the player is possibly out of range in step 247 and checks the list of players in proximity again. If the player is already flagged as possibly out of range in step 246, then the dropout detection handler removes the player from the list of players in proximity in step 248 and checks the list of players in proximity in step 241 again. If the player poll response message is in the queue in step 245, then the dropout detection handler clears the possibly out of range flag in step 249 for the player in the list of players in proximity. Next, the dropout detection handler checks if the player is requesting content synchronization in step 250, based on information passed in the poll response message from the player. If the player is requesting content synchronization, then the dropout detection handler flags the player for content synchronization in step 251 in the list of players in proximity. The content synchronization handler uses this information when deciding which players to update for digital audio content and other information 101. Once the player is flagged for content synchronization or the player is not requesting content synchronization, then the dropout detection handler checks if the player is requesting playlist continuation in step 252, based on information passed in the poll response message from the player. If the player is requesting playlist continuation, then the dropout detection handler flags the player for playlist continuation in step 253 in the list of players in proximity. The playlist continuation handler uses this information when deciding which players to update the playlist and current selection for. Once the player is flagged for playlist continuation in step 253 or the player is not requesting playlist continuation in step 252, then the dropout detection handler checks the list of players in proximity in step 241 again. Audio Gateway Content Synchronization Flow [0079] The flow diagram for audio gateway content synchronization is shown in FIG. 19, with content synchronization being a key capability of the invention. The content synchronization handler in the audio gateway checks for players that need content synchronization. Content synchronization involves updating or adding digital audio content and other information 101 to a player when the audio gateway has digital audio content and other information 101 that is not contained on the player. This may be handled automatically when the player has recently been discovered as being in proximity by the gateway discovery handler or the player directly requests content synchronization through poll response messages to the gateway. In this example, the content synchronization handler is a continuously running process. The step, “Start” 260, represents the beginning of the content synchronization handling process. The content synchronization handler checks the list of players in proximity in step 261 maintained by the gateway. If there are players in proximity flagged for content synchronization in step 262, then the content synchronization handler sends a query player for content message to the player in step 263 that is flagged for content synchronization. Next, the content synchronization handler waits, with some timeout, for a player content response message in step 264. If there is no content response message in the queue in step 265 from the player that was sent the query player for content message in step 263, then the content synchronization handler clears the content synchronization flag for the player in the proximity list in step 266 and checks the list of players in proximity again. If there is a content response message in the queue in step 265 from the player that was sent the query player for content message, then the gateway compares the digital audio content in the player with the digital audio content in the gateway in step 267. The player′s digital audio content information is contained in the content response message sent to the gateway by the player. Next, the content synchronization handler checks if there is any content in the gateway that is not on the player in step 268. If the player content is properly synchronized with the gateway, then the content synchronization handler clears the content synchronization flag for the player in the proximity list and checks the list of players in proximity in step 261 again. If there is content on the gateway that is not on the player in step 268, then the content synchronization handler checks if there is storage on the player for the new content in step 269. The available storage on the player is provided in the content response message that the player sent to the gateway. If there is not sufficient storage on the player for the new content in step 269, then the content synchronization handler clears the content synchronization flag for the player in the proximity list in step 266 and checks the list of players in proximity in step 261 again. If there is storage on the player for the new content as determined in step 269, then the content synchronization handler sends the content data to the player in step 270. Next, the content synchronization handler waits, with some timeout, for the content acknowledge message from the player in step 271. If there is no content acknowledge message in the queue in step 272, then the content synchronization handler clears the content synchronization flag for the player in the proximity list in step 266 and checks the list of players in proximity in step 261 again. If there is a content acknowledge message in the queue from the player, then the content synchronization handler checks to see, from the compare of content in the player with content in the gateway, if there is more content to send to the player in step 273. If there is more content to send to the player then the content synchronization handler checks again if there is storage on the player for the new content in step 269, and so on until there is no more content to pass from the gateway to the player. If there is no more content to send to the player, then the content synchronization handler clears the content synchronization flag for the player in the proximity list in step 266 and checks the list of players in proximity in step 261 again. Audio Gateway Playlist Continuation Flow [0080] The flow diagram for audio gateway playlist continuation is shown in FIG. 20, with playlist continuation being a key capability of the invention. The playlist continuation handler in the audio gateway checks for propagation of the playlist and current playlist selection from one mobile digital audio player 115 or fixed digital audio player 116 to all other mobile digital audio players 115 and fixed digital audio players 116 in proximity. Playlist continuation involves seamless continuation of playback of digital audio content 101 from a particular playlist as a user moves from one mobile digital audio player 115 or fixed digital audio player 116 to another. This may be handled automatically when the gateway discovery handler discovers a player as being in proximity, where the player is currently playing digital audio content 101. The player itself may also directly request playlist continuation through poll response messages to the gateway. [0081] In this example, the playlist continuation handler is a continuously running process. The step, “Start” 280, represents the beginning of the playlist continuation handling process. The playlist continuation handler checks the list of players in proximity in step 281 maintained by the gateway. If there are players in proximity flagged for playlist continuation in step 282, then the playlist continuation handler sends a query player for playlist message to the player in step 283 that is flagged for playlist continuation. Next, the playlist continuation handler waits, with some timeout, for a player playlist response message in step 284. If there is no playlist response message in the queue in step 285 from the player that was sent the query player for playlist message in step 283, then the playlist continuation handler clears the playlist continuation flag for the player in the proximity list in step 286 and checks the list of players in proximity again. If there is a playlist response message in the queue as determined in step 285 from the player that was sent the query player for playlist message in step 283, then the gateway checks the playlist response message to see if the playlist and current position within the playlist, both of which are contained in the playlist response message, are valid in step 287. If the playlist and current position are not valid, then the playlist continuation handler clears the playlist continuation flag for the player in the proximity list in step 286 and checks the list of players in proximity again. If the playlist and current position in the playlist are valid as determined in step 287, then the playlist continuation handler checks the list of players in proximity in step 288. If there are any other players in proximity as determined in step 289, then the playlist continuation handler sends a broadcast playlist and current position message to all other players in proximity in step 290. After the playlist continuation handler sends a broadcast playlist and current position message to all other players in proximity in step 290 or if there are no other players in proximity, then the playlist continuation handler clears the playlist continuation flag for the player in the proximity list in step 286 and checks the list of players in proximity in step 281 again. Player Software [0082] FIGS. 21-27 provide flow diagrams for the various digital audio players. In these flow diagrams, the software is assumed to be running in a multitasking environment, with each of the flow diagrams representing a particular independently running task or process. However, it should be noted that these flow diagrams represent only one of many different ways to implement the key software functionality for the player and that many other implementations are possible, including those which do not require a multitasking environment. Player Message Handling Flow [0083] [0083]FIG. 21 is a flow diagram of the message handler for a player. In general, the message handler takes the messages received from computing platforms 103 acting as audio gateways and from other mobile digital audio players 115 and fixed digital audio players 116, on a wireless network or wireless communication platform 104, and queues these messages for use by other processes or handles them itself, depending on the message type. In this example, the message handler is a continuously running process. The step, “Start” 300, represents the beginning of the message handling process. The message handler checks if there is a message received in step 301. If there is a message received, the message handler then checks to see what type of message it is, among many possible types. [0084] After the message handler determines the type of message an appropriate response is queued and the system returns to step 301 and checks for additional messages. If the message is a broadcast for players message from a gateway as determined in step 302, then the message handler queues the broadcast for players message in step 303. After the message handler queues the broadcast for players message in step 303, the message handler checks for more messages. If the message is a query player message from a gateway as determined in step 304, then the message handler queues the query player message in step 305. After the message handler queues the query player message in step 305, the message handler checks for more messages. If the message is a poll message from a gateway as determined in 306, then the message handler queues the poll message in step 307. After the message handler queues the poll message in step 307, the message handler checks for more messages. If the message is a query player for content message from a gateway as determined in 308, then the message handler queues the query player for content message in step 309. After the message handler queues the query player for content message in step 309, the message handler checks for more messages. If the message is content data from a gateway in step 310, then the message handler stores the content in local player storage in step 311. The message handler also sends a content acknowledge message to the gateway in step 312. After the message handler sends a content acknowledge message to the gateway in step 312, the message handler checks for more messages. If the message is a query player for playlist message from a gateway as determined in step 313, then the message handler queues the query player for playlist message in step 314. After the message handler queues the query player for playlist message in step 314, the message handler checks for more messages. If the message is a broadcast playlist message from a gateway as determined in step 315, then the message handler queues the broadcast playlist message in step 316. After the message handler queues the broadcast playlist message in step 316, the message handler checks for more messages. Finally, if the message was none of those previously checked for, the message handler handles or queues any other messages as necessary in step 317 and then the message handler checks for more messages. Player Discovery Flow [0085] Discovery by the audio gateway of mobile digital audio players 115 and fixed digital audio players 116 is an important capability with respect to this invention. FIGS. 22 and 23 provide the flow diagrams for discovery responses by the player when the player detects discovery attempts by an audio gateway. In this example, the player discovery broadcast response handler and the player discovery query response handler are continuously running processes. The step, “Start” 320, represents the beginning of the discovery broadcast response handling process. The discovery broadcast response handler first checks for a broadcast for players message in the queue in step 321 from a gateway. If there is a broadcast for players message in the queue as determined in 322, then the discovery broadcast response handler checks if the gateway is already in proximity of the player in step 323. The discovery broadcast response handler is able to get information about the gateway from the broadcast for players message received from the gateway and can compare that information with information saved by the discovery query response handler for any gateway in proximity. If the gateway is not already in proximity as determined in step 323, then the discovery broadcast response handler sends a broadcast acknowledge message to the gateway in step 324. After the discovery broadcast response handler sends the broadcast acknowledge message to the gateway in step 324, or if the gateway is already in proximity as determined in step 323, or if there is no broadcast for players message in the queue as determined in step 322, then the discovery broadcast response handler checks for a broadcast for players message in the queue again. [0086] The step, “Start” 330 (FIG. 23), represents the beginning of the discovery query response handling process. The discovery query response handler first checks for query player messages from a gateway in the queue in step 331. If there is a query player message in the queue as determined in step 332, then the discovery query response handler sends a query response message to the gateway in step 333 that sent the query player message. Then the discovery query response handler saves that the gateway is in proximity in step 334 from information obtained from the query player message from the gateway. After the discovery query response handler saves that the gateway is in proximity as determined in step 334 or if there is no query player message in the queue as determined in step 332, then the discovery query response handler checks for a query player message from a gateway in the queue again. Player Dropout Detection Flow [0087] The flow diagram for player dropout detection of an audio gateway is shown in FIG. 24. The dropout detection handler in the player watches for poll messages from an audio gateway in order to see if the player has gone out of range of the gateway. In this example, the player dropout detection handler is a continuously running process. Step, “Start” 340, represents the beginning of the player dropout detection handling process. The player dropout detection handler checks if the player is in proximity of a gateway in step 341. The player discovery query response handler, shown in FIG. 23, saves information about a gateway that is in proximity. If the player is not in proximity of a gateway as determined in step 341, then the player dropout detection handler just continues to check if the player is in proximity of a gateway. If the player is in proximity of a gateway as determined in step 341, then the player dropout detection handler waits, with some timeout, for a poll response message from the gateway in step 342 that is in proximity. The timeout period is significantly more than the polling period used by the gateway. If there is not a poll message in the queue as determined in step 343 from the gateway that is in proximity, then the player dropout detection handler checks if the gateway is already flagged as possibly out of range in step 344. If the gateway is not already flagged as possibly out of range as determined in step 344, then the player dropout detection handler flags that the gateway is possibly out of range in step 345 and then continues to check if the player is in proximity of a gateway in step 341. If the gateway is already flagged as possibly out of range as determined in step 344, then the player dropout detection handler removes the gateway as being in proximity in step 346 and then continues to check if the player is in proximity of a gateway in step 341. If there is a poll message in the queue as determined in 343 from the gateway that is in proximity, then the player dropout detection handler checks if the user requested content synchronization of the player in step 347. If the user did request content synchronization of the player as determined in step 347, then the player dropout detection handler flags a content synchronization request in the poll response message in step 348 to the gateway in proximity. If the user did not request content synchronization of the player, then the player dropout detection handler skips flagging of content synchronization in the poll response message in step 348. Next, the player dropout detection handler checks if the user requested playlist continuation for the player in step 349. If the user did request playlist continuation for the player as determined in step 349, then the player dropout detection handler flags a playlist continuation request in the poll response message in step 350 to the gateway in proximity. If the user did not request playlist continuation for the player as determined in step 349, then the player dropout detection handler skips flagging of playlist continuation in the poll response message in step 350. Next, the player dropout detection handler sends the poll response message to the gateway in step 351 that is in proximity and sent the poll message. Next, the player dropout detection handler clears the gateway possibly out of range flag in step 352 if it was set for the gateway in proximity. Then the player dropout detection handler continues to check if the player is in proximity of a gateway as determined in step 341. Player Content Synchronization Flow [0088] The flow diagram for player content synchronization response is shown in FIG. 25, with content synchronization being a key capability of the invention. The content synchronization response handler in the player responds to content queries from a gateway. In this example, the content synchronization response handler is a continuously running process. The step, “Start” 360, represents the beginning of the content synchronization response handling process. The content synchronization response handler checks for a query player content message in the queue in step 361 from a gateway. If there is a query player content message in the queue as determined in step 362, then the content synchronization response handler builds a content response message by first getting a list of all the digital audio content on the player in 363. Next, the content synchronization response handler determines the amount of available storage space on the player in step 364 for additional digital audio content. Finally, the content synchronization response handler sends a player content response message in step 365 to the gateway that sent the query player content message. The player content response message contains the list of all the digital audio content on the player as well as the amount of available space on the player. Once the content synchronization response handler sends a player content response message, as determined in step 365, to the gateway that sent the query player content message or there is no query player content message in the queue in step 362, then the content synchronization response handler checks for a query player content message in the queue again. Player Playlist Continuation Flow [0089] [0089]FIGS. 26 and 27 represent flow diagrams for playlist continuation response and playlist continuation updating by the player when the player detects playlist continuation query and updating attempts by an audio gateway. Playlist continuation is a key capability of the invention. In this example, the player playlist response handler and the player playlist update handler are continuously running processes. The step, “Start” 380, represents the beginning of the playlist response handling process. First, the playlist response handler checks for a query player for playlist message in the queue in step 381 from a gateway in proximity. If there is a query player for playlist message in the queue as determined in step 382, then the playlist response handler gets the current playlist and current position within the playlist in step 383 and puts this information in a playlist response message. Next, the playlist response handler sends the playlist response message to the gateway in step 384 that sent the query player for playlist message. After the playlist response handler sends the playlist response message to the gateway as determined 384 or there is not a query player for playlist message in the queue as determined in step 382, then the playlist response handler checks for a query player for playlists message 381 in the queue again. [0090] The step, “Start” 390 (FIG. 27), represents the beginning of the playlist update handling process. First the playlist update handler checks for a broadcast playlist message in step 391 in the queue from a gateway in proximity. If there is not a broadcast playlist message in the queue as determine in step 392, then the playlist update handler just checks for a broadcast playlist message in the queue again. If there is a broadcast playlist message in the queue, as determined in step 392, then the playlist update handler checks if the playlist already exists on the player in step 393. The playlist information is found in the broadcast playlist message. If the playlist already exists on the player, as determined in step 393, then the playlist update handler activates the playlist and sets the current position within the playlist in step 394 on the player. The current position within the playlist is found in the broadcast playlist message. Then the playlist update handler checks for a broadcast playlist message in step 391 in the queue again. If the playlist does not already exist on the player as determined in step 393, then the playlist update handler saves the new playlist on the player in step 395. Next, the playlist update handler checks if the player is currently playing in step 396. If the player is not currently playing, then the playlist update handler sets the new playlist as the current playlist in step 397 and sets the current position within the playlist in step 394. If the player is currently playing, then the playlist update handler notifies the user that a new playlist is available in step 398. This allows the user to decide to play the new playlist or continue with a current playlist. Next, the playlist update handler checks for a broadcast playlist message in step 391 in the queue again. [0091] Obviously, many modifications and variations of the present invention are possible in light of the above teachings. Thus, it is to be understood that, within the scope of the appended claims, the invention may be practiced otherwise than as specifically described above.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5109484 *Apr 9, 1986Apr 28, 1992International Business Machines CorporationSelf configuring terminal which polls loop network and generates list of connected devices for use in selectively downloading control programsUS5421030 *Sep 17, 1991May 30, 1995Com21, Inc.Communications system and method for bi-directional communications between an upstream control facility and downstream user terminalsUS5666530 *Dec 2, 1992Sep 9, 1997Compaq Computer CorporationSystem for automatic synchronization of common file between portable computer and host computer via communication channel selected from a plurality of usable channels there betweenUS5727202 *Oct 18, 1995Mar 10, 1998Palm Computing, Inc.Method and apparatus for synchronizing information on two different computer systemsUS5819160 *Sep 18, 1996Oct 6, 1998At&T CorpProgrammable radio subscription system for receiving selectively defined informationUS5905719 *Sep 19, 1996May 18, 1999Bell Communications Research, Inc.Method and system for wireless internet accessUS5923757 *Apr 10, 1997Jul 13, 1999International Business Machines CorporationDocking method for establishing secure wireless connection between computer devices using a docket portUS5969678 *Nov 4, 1998Oct 19, 1999Wayport, Inc.System for hybrid wired and wireless geographic-based communications serviceUS5974238 *Aug 7, 1996Oct 26, 1999Compaq Computer CorporationAutomatic data synchronization between a handheld and a host computer using pseudo cache including tags and logical data elementsUS5974312 *Jul 10, 1997Oct 26, 1999Ericsson Inc.System and method for updating a memory in an electronic device via wireless data transferUS6035349 *Dec 9, 1997Mar 7, 2000Electrolnics And Telecommunications Research InstituteStructure of portable multimedia data input/output processor and method for driving the sameUS6064379 *Jun 24, 1996May 16, 2000Sun Microsystems, Inc.System and method for synchronizing presentation of media stream playlists with real timeUS6072468 *Apr 10, 1997Jun 6, 2000International Business Machines CorporationDocking system for establishing secure wireless connection between computer devicesUS6295541 *Aug 18, 1998Sep 25, 2001Starfish Software, Inc.System and methods for synchronizing two or more datasetsUS6330618 *May 25, 1999Dec 11, 2001Palm, Inc.Method and apparatus for synchronizing a portable computer system with a desktop computer systemUS6477117 *Jun 30, 2000Nov 5, 2002International Business Machines CorporationAlarm interface for a smart watchUS6522886 *Nov 22, 1999Feb 18, 2003Qwest Communications International Inc.Method and system for simultaneously sharing wireless communications among multiple wireless handsetsUS6678215 *Mar 20, 2000Jan 13, 2004G. Victor TreyzDigital audio devicesUS6697649 *Oct 1, 1998Feb 24, 2004At&T Laboratories Cambridge LimitedPeer-to-peer communication in a radio networkUS6714797 *May 17, 2000Mar 30, 2004Nokia CorporationSystem and method for the transfer of digital data to a mobile deviceUS6754468 *Apr 30, 1999Jun 22, 2004Micronas Intermetall GmbhLocal communications deviceUS6774951 *Feb 22, 2001Aug 10, 2004Sony CorporationDigital broadcast reception system, digital broadcast reception apparatus and digital broadcast printing apparatusUS6874037 *Jun 19, 2000Mar 29, 2005Sony CorporationMethod and apparatus for synchronizing device informationUS6931429 *Apr 27, 2001Aug 16, 2005Left Gate Holdings, Inc.Adaptable wireless proximity networkingUS6931454 *Dec 29, 2000Aug 16, 2005Intel CorporationMethod and apparatus for adaptive synchronization of network devicesUS6938100 *Dec 21, 2000Aug 30, 2005Lg Electronics Inc.Method for synchronizing data between mobile terminal and computerUS7587446 *Nov 10, 2000Sep 8, 2009Fusionone, Inc.Acquisition and synchronization of digital media to a personal information spaceUS20020002039 *Mar 12, 2001Jan 3, 2002Safi QuresheyNetwork-enabled audio deviceUS20020022453 *Mar 30, 2001Feb 21, 2002Horia BalogDynamic protocol selection and routing of content to mobile devicesUS20020087996 *Nov 6, 2001Jul 4, 2002Depeng BiInteractive remote control of audio or video playback and selectionsUS20020099772 *Dec 29, 2000Jul 25, 2002Nikhil DeshpandeMethod and apparatus for adaptive synchronization of network devicesUS20020114350 *Oct 29, 2001Aug 22, 2002Tang Hong DaSystems, devices and methods for use in proximity-based networkingUS20020116533 *Jun 8, 2001Aug 22, 2002Holliman Matthew J.System for providing a multimedia peer-to-peer computing platformUS20020132616 *Mar 19, 2001Sep 19, 2002Ross Lorna R.Communications system with automatic download capabilityUS20020164973 *Oct 19, 2001Nov 7, 2002Janik Craig M.Automotive storage and playback device and method for using the sameUS20020164995 *May 3, 2001Nov 7, 2002International Business Machines CorporationMethod, system, and program for providing user location information for a personal information management system from transmitting devicesUS20030079038 *Oct 21, 2002Apr 24, 2003Apple Computer, Inc.Intelligent interaction between media player and host computerUS20050002039 *Jul 2, 2003Jan 6, 2005Abbink Russell E.Interferometer* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7130251Sep 20, 2000Oct 31, 2006Sony CorporationCommunication system and its method and communication apparatus and its methodUS7166791Oct 28, 2002Jan 23, 2007Apple Computer, Inc.Graphical user interface and methods of use thereof in a multimedia playerUS7502344 *Jun 27, 2005Mar 10, 2009Fujifilm CorporationCommunications terminal, server, playback control method and programUS7521625Dec 7, 2006Apr 21, 2009Apple Inc.Graphical user interface and methods of use thereof in a multimedia playerUS7560637Sep 28, 2005Jul 14, 2009Apple Inc.Graphical user interface and methods of use thereof in a multimedia playerUS7617537Jan 31, 2005Nov 10, 2009Sony CorporationCommunication system and its method and communication apparatus and its methodUS7660929Sep 12, 2008Feb 9, 2010Apple Inc.Connector interface system for a multi-communication deviceUS7667124Nov 29, 2006Feb 23, 2010Apple Inc.Graphical user interface and methods of use thereof in a multimedia playerUS7673083Sep 11, 2006Mar 2, 2010Apple Inc.Method and system for controlling video selection and playback in a portable media playerUS7680849Oct 25, 2004Mar 16, 2010Apple Inc.Multiple media type synchronization between host computer and media deviceUS7688384 *Jul 17, 2007Mar 30, 2010The Directv Group, Inc.Personal multimedia device video format conversion across multiple video formatsUS7702833Sep 12, 2008Apr 20, 2010Apple Inc.Techniques for transferring information between an accessory and a multi-communication deviceUS7720929Jun 9, 2004May 18, 2010Sony CorporationCommunication system and its method and communication apparatus and its methodUS7721337Oct 26, 2001May 18, 2010Ibiquity Digital CorporationSystem and method for providing a push of background dataUS7734248Feb 25, 2009Jun 8, 2010Fujifilm CorporationCommunications terminal, server, playback control method and programUS7757026Aug 3, 2009Jul 13, 2010Apple Inc.Techniques for transferring status information between an accessory and a multi-communication deviceUS7765326 *Oct 21, 2002Jul 27, 2010Apple Inc.Intelligent interaction between media player and host computerUS7769903 *Jun 1, 2007Aug 3, 2010Apple Inc.Intelligent interaction between media player and host computerUS7779185Apr 15, 2009Aug 17, 2010Apple Inc.Communication between a media player and an accessory using a protocol with multiple lingoesUS7797446Jul 16, 2002Sep 14, 2010Apple Inc.Method and system for updating playlistsUS7797456Dec 15, 2000Sep 14, 2010Sony CorporationInformation processing apparatus and associated method of transferring grouped contentUS7797471Jun 27, 2006Sep 14, 2010Apple Inc.Method and system for transferring album artwork between a media player and an accessoryUS7823214Feb 3, 2005Oct 26, 2010Apple Inc.Accessory authentication for electronic devicesUS7826318Jun 26, 2007Nov 2, 2010Apple Inc.Method and system for allowing a media player to transfer digital audio to an accessoryUS7827259Apr 27, 2004Nov 2, 2010Apple Inc.Method and system for configurable automatic media selectionUS7853746Sep 12, 2008Dec 14, 2010Apple Inc.Interface system for enabling data communication between a multi-communication device and other devicesUS7860830Apr 25, 2005Dec 28, 2010Apple Inc.Publishing, browsing and purchasing of groups of media itemsUS7877532Apr 15, 2009Jan 25, 2011Apple Inc.Communication between an accessory and a media player with multiple lingoes and lingo version informationUS7881706Feb 23, 2009Feb 1, 2011Fujifilm CorporationCommunication terminal, server, playback control method and programUS7895378 *Jun 27, 2006Feb 22, 2011Apple Inc.Method and system for allowing a media player to transfer digital audio to an accessoryUS7907563Jan 26, 2009Mar 15, 2011Fujifilm CorporationCommunications terminal, server, playback control method and programUS7949810Sep 11, 2008May 24, 2011Apple Inc.Techniques for transferring data between a media player and an accessory having a tunerUS7956272Dec 5, 2005Jun 7, 2011Apple Inc.Management of files in a personal communication deviceUS7958441Apr 1, 2005Jun 7, 2011Apple Inc.Media management for groups of media itemsUS8006019Nov 2, 2009Aug 23, 2011Apple, Inc.Method and system for transferring stored data between a media player and an accessoryUS8041195Nov 3, 2006Oct 18, 2011Audiovox CorporationVehicle entertainment system for remote sharing and storage of video contentUS8046369Sep 4, 2007Oct 25, 2011Apple Inc.Media asset rating systemUS8047966Sep 26, 2008Nov 1, 2011Apple Inc.Interfacing portable media devices and sports equipmentUS8082376Apr 15, 2009Dec 20, 2011Apple Inc.Communication between an accessory and a media player with multiple protocol versionsUS8095716Jul 21, 2008Jan 10, 2012Apple Inc.Method and system for communicating capability information from an accessory to a media playerUS8099536Apr 15, 2009Jan 17, 2012Apple Inc.Communication between an accessory and a media player with general and accessory lingoesUS8103793Oct 20, 2009Jan 24, 2012Apple Inc.Method and system for updating playlistsUS8108572Jul 13, 2010Jan 31, 2012Sony CorporationCommunication system and its method and communication apparatus and its methodUS8112567Jun 4, 2009Feb 7, 2012Apple, Inc.Method and system for controlling power provided to an accessoryUS8112592Aug 30, 2002Feb 7, 2012Sony CorporationInformation processing apparatus and methodUS8117651Jun 27, 2006Feb 14, 2012Apple Inc.Method and system for authenticating an accessoryUS8122163Feb 20, 2008Feb 21, 2012Sony CorporationCommunication system and its method and communication apparatus and its methodUS8135891Aug 7, 2009Mar 13, 2012Apple Inc.Method and system for transferring button status information between a media player and an accessoryUS8150937Nov 12, 2004Apr 3, 2012Apple Inc.Wireless synchronization between media player and host deviceUS8151063Mar 8, 2005Apr 3, 2012Sony CorporationInformation processing apparatus and methodUS8161567Sep 30, 2010Apr 17, 2012Apple Inc.Accessory authentication for electronic devicesUS8171194Aug 16, 2010May 1, 2012Apple Inc.Accessory communication with a media player using a display remote lingoUS8171195Aug 16, 2010May 1, 2012Apple Inc.Media player communication with an accessory using a display remote lingoUS8188357May 12, 2009May 29, 2012Apple Inc.Graphical user interface and methods of use thereof in a multimedia playerUS8203657Jul 11, 2008Jun 19, 2012Audiovox CorporationInductively powered mobile entertainment systemUS8208853Sep 9, 2009Jun 26, 2012Apple Inc.Accessory device authenticationUS8238291Feb 7, 2011Aug 7, 2012Fujifilm CorporationCommunications terminal, server, playback control method and programUS8238811Jan 7, 2009Aug 7, 2012Apple Inc.Cross-transport authenticationUS8239595Nov 23, 2010Aug 7, 2012Apple Inc.Communication between a media player and an accessory with an extended interface modeUS8261246Sep 7, 2004Sep 4, 2012Apple Inc.Method and system for dynamically populating groups in a developer environmentUS8261309Jun 9, 2009Sep 4, 2012Audiovox CorporationMobile entertainment system with retrieval of audio and video media content from a remote libraryUS8285901Nov 23, 2010Oct 9, 2012Apple Inc.Communication between an accessory and a media player using an extended interface lingoUS8291134Nov 16, 2011Oct 16, 2012Sony CorporationCommunication system and its method and communication apparatus and its methodUS8317658Oct 12, 2011Nov 27, 2012Apple Inc.Interfacing portable media devices and sports equipmentUS8370555Dec 20, 2011Feb 5, 2013Apple Inc.Method and system for allowing a media player to determine if it supports the capabilities of an accessoryUS8386581Feb 4, 2010Feb 26, 2013Sony CorporationCommunication system and its method and communication apparatus and its methodUS8386680Nov 15, 2011Feb 26, 2013Apple Inc.Communication between an accessory and a media player with multiple protocol versions and extended interface lingoUS8402187Feb 3, 2012Mar 19, 2013Apple Inc.Method and system for transferring button status information between a media player and an accessoryUS8417779Jan 12, 2010Apr 9, 2013Apple Inc.Apparatus and method for interacting with handheld carrier hosting media contentUS8443038 *Jul 1, 2011May 14, 2013Apple Inc.Network media deviceUS8443096Mar 25, 2009May 14, 2013Apple Inc.Accessory identification for mobile computing devicesUS8452903Jun 5, 2009May 28, 2013Apple Inc.Mobile computing device capabilities for accessoriesUS8463868Mar 10, 2005Jun 11, 2013Sony CorporationInformation processing apparatus and associated method of content exchangeUS8495246Jan 24, 2012Jul 23, 2013Apple Inc.Method and system for updating playlistsUS8509691May 17, 2012Aug 13, 2013Apple Inc.Accessory device authenticationUS8522150Jul 12, 2010Aug 27, 2013Sony CorporationInformation processing apparatus and associated method of content exchangeUS8554888Apr 26, 2011Oct 8, 2013Sony CorporationContent management system for searching for and transmitting contentUS8570949 *Jul 2, 2012Oct 29, 2013Facebook, Inc.Communications terminal, server, playback control method and programUS8590036Jan 10, 2012Nov 19, 2013Apple Inc.Method and system for authenticating an accessoryUS8601243Jul 13, 2010Dec 3, 2013Sony CorporationCommunication system and its method and communication apparatus and its methodUS8626952Jul 2, 2010Jan 7, 2014Apple Inc.Intelligent interaction between media player and host computerUS8631088Feb 26, 2007Jan 14, 2014Apple Inc.Prioritized data synchronization with host deviceUS8634761Jun 29, 2012Jan 21, 2014Apple Inc.Cross-transport authenticationUS8683009Mar 29, 2012Mar 25, 2014Apple Inc.Wireless synchronization between media player and host deviceUS8706159Sep 1, 2006Apr 22, 2014Apple Inc.Media data transferUS8713126 *Feb 28, 2005Apr 29, 2014Sony CorporationInformation-provision control method, information reproduction system, information-provision apparatus, information reproduction apparatus and information-presentation control programUS8724608Sep 29, 2004May 13, 2014Koninklijke Philips N.V.Radio system with configurable linksUS8762565 *Dec 9, 2013Jun 24, 2014Sony CorporationInformation-provision control method, information reproduction system, information-provision apparatus, information reproduction apparatus and information-presentation control programUS8763079Dec 4, 2008Jun 24, 2014Apple Inc.Accessory authentication for electronic devicesUS8850140Feb 26, 2007Sep 30, 2014Apple Inc.Data backup for mobile deviceUS8909803Mar 16, 2009Dec 9, 2014Apple Inc.Accessory identification for mobile computing devicesUS8929299Sep 25, 2013Jan 6, 2015Facebook, Inc.Communications terminal, server, playback control method and programUS9001813May 2, 2014Apr 7, 2015Koninklijke Philips N.V.Radio system with configurable linksUS9049240 *Apr 9, 2009Jun 2, 2015Thomson LicensingDevice and method for sharing filesUS9087060 *Mar 19, 2012Jul 21, 2015Apple Inc.Partial sort on a hostUS9160541Nov 19, 2013Oct 13, 2015Apple Inc.Method and system for authenticating an accessoryUS9160818Oct 28, 2013Oct 13, 2015Sony CorporationCommunication system and its method and communication apparatus and its methodUS9223958Jun 23, 2014Dec 29, 2015Apple Inc.Accessory authentication for electronic devicesUS9224364Apr 8, 2013Dec 29, 2015Apple Inc.Apparatus and method for interacting with handheld carrier hosting media contentUS9241022Nov 21, 2012Jan 19, 2016Sony CorporationInformation processing apparatus and associated method of content exchangeUS9299329Dec 7, 2006Mar 29, 2016Apple Inc.Graphical user interface and methods of use thereof in a multimedia playerUS9306879Dec 10, 2012Apr 5, 2016Apple Inc.Message-based identification of an electronic deviceUS9380112Mar 28, 2014Jun 28, 2016Sony CorporationCommunication system and its method and communication apparatus and its methodUS9405766Jan 13, 2014Aug 2, 2016Apple Inc.Prioritized data synchronization with host deviceUS9412417Apr 1, 2005Aug 9, 2016Apple Inc.Persistent group of media items for a media deviceUS9448683Apr 24, 2013Sep 20, 2016Apple Inc.Network media deviceUS9467735Jun 13, 2008Oct 11, 2016Apple Inc.Synchronizing digital audio and analog video from a portable media deviceUS9491214May 7, 2014Nov 8, 2016Sony CorporationInformation-provision control method, information reproduction system, information-provision apparatus, information reproduction apparatus and information-presentation control programUS20020159304 *Dec 15, 2000Oct 31, 2002Toshihiro MoritaMethod and apparatus for information processing, and medium for storing programUS20030083977 *Oct 26, 2001May 1, 2003Majid SyedSystem and method for providing electronic bulk buyingUS20030084108 *Oct 26, 2001May 1, 2003Majid SyedSystem and method for providing a push gateway between consumer devices and remote content povider centersUS20030167318 *Apr 5, 2002Sep 4, 2003Apple Computer, Inc.Intelligent synchronization of media player with host computerUS20040027931 *Aug 30, 2002Feb 12, 2004Toshihiro MoritaInformation processing apparatus and methodUS20040055446 *Oct 28, 2002Mar 25, 2004Apple Computer, Inc.Graphical user interface and methods of use thereof in a multimedia playerUS20050141367 *Jan 31, 2005Jun 30, 2005Sony CorporationCommunication system and its method and communication apparatus and its methodUS20050146995 *Mar 8, 2005Jul 7, 2005Toshihiro MoritaInformation processing apparatus and methodUS20050165898 *Mar 10, 2005Jul 28, 2005Sony CorporationInformation processing apparatus and method, and program storage mediumUS20050235334 *Feb 28, 2005Oct 20, 2005Sony CorporationInformation-provision control method, information reproduction system,information-provision apparatus, information reproduction apparatus and information-presentation control programUS20050286463 *Jun 27, 2005Dec 29, 2005Fuji Photo Film Co., Ltd.Communications terminal, server, playback control method and programUS20060212564 *May 16, 2006Sep 21, 2006Sony CorporationContent management system and associated methodologyUS20070026846 *Sep 29, 2004Feb 1, 2007Bird Neil CRadio system with configurable linksUS20070074118 *Nov 29, 2006Mar 29, 2007Robbin Jeffrey LGraphical user interface and methods of use thereof in a multimedia playerUS20070155307 *Sep 1, 2006Jul 5, 2007Apple Computer, Inc.Media data transferUS20070192797 *Jan 19, 2007Aug 16, 2007Samsung Electronics Co., Ltd.Method of and apparatus for managing distributed contentsUS20070233294 *Jun 27, 2006Oct 4, 2007Paul HoldenMethod and system for allowing a media player to transfer digital audio to an accessoryUS20070277221 *Jul 17, 2007Nov 29, 2007Robert DavisPersonal multimedia device video format conversion across multiple video formatsUS20080086494 *Sep 11, 2006Apr 10, 2008Apple Computer, Inc.Transfer and synchronization of media dataUS20080162668 *Dec 29, 2006Jul 3, 2008John David MillerMethod and apparatus for mutually-shared media experiencesUS20080168525 *Feb 26, 2007Jul 10, 2008David HellerBackground Data Transmission between Media Device and Host DeviceUS20080256378 *Jan 26, 2005Oct 16, 2008Koninklijke Philips Electronic, N.V.Audio/Video Content Synchronization Through PlaylistsUS20090060446 *Jun 13, 2008Mar 5, 2009Apple Inc.Synchronizing digital audio and analog video from a portable media deviceUS20090063652 *Sep 4, 2007Mar 5, 2009Yoon Sub HwangLocalized Media Content DeliveryUS20090094348 *Jul 10, 2006Apr 9, 2009Mitsubishi Electric CorporationContent server apparatus, content transfer apparatus and content playback apparatusUS20090100081 *Oct 8, 2008Apr 16, 2009Olympus CorporationInformation processing apparatus, information processing method, and program storage medium storing programUS20090129320 *Jan 26, 2009May 21, 2009Tetsuya MatsumotoCommunications Terminal, Server, Playback Control Method and ProgramUS20090170425 *Feb 25, 2009Jul 2, 2009Fujifilm CorpCommunications terminal, server, playback control method and programUS20090181656 *Feb 23, 2009Jul 16, 2009Fujifilm CorpCommunication terminal, server, playback control method and programUS20090307729 *Jun 9, 2009Dec 10, 2009Vitito Christopher JMobile entertainment system with retrieval of audio and video media content from a remote libraryUS20100135133 *Feb 4, 2010Jun 3, 2010Sony CorporationCommunication system and its method and communication apparatus and its methodUS20100234068 *Mar 25, 2009Sep 16, 2010Apple Inc.Accessory identification for mobile computing devicesUS20100275127 *Jul 12, 2010Oct 28, 2010Sony CorporationInformation processing apparatus and associated method of content exchangeUS20100281140 *Jul 13, 2010Nov 4, 2010Sony CorporationCommunication system and its method and communication apparatus and its methodUS20100281141 *Jul 13, 2010Nov 4, 2010Sony CorporationCommunication system and its method and communication apparatus and its methodUS20110060777 *Apr 9, 2009Mar 10, 2011Dirk Van De PoelDevice and method for sharing filesUS20110169735 *Jan 12, 2010Jul 14, 2011Douglas WeberApparatus and Method for Interacting with Handheld Carrier Hosting Media ContentUS20110264732 *Jul 1, 2011Oct 27, 2011Apple Inc.Network Media DeviceUS20120271917 *Jul 2, 2012Oct 25, 2012Fujifilm CorporationCommunications terminal, server, playback control method and programUS20120311194 *Mar 19, 2012Dec 6, 2012Thomas Matthieu AlsinaPartial sort on a hostUS20150172878 *Dec 12, 2013Jun 18, 2015AliphcomAcoustic environments and awareness user interfaces for media devicesEP1569391A2 *Nov 9, 2004Aug 31, 2005Kabushiki Kaisha ToshibaElectronic device and device discovery method using the sameEP1569391A3 *Nov 9, 2004Nov 2, 2005Kabushiki Kaisha ToshibaElectronic device and device discovery method using the sameEP1571803A1 *Feb 18, 2005Sep 7, 2005Sony CorporationInformation-provision control method, information reproduction system, and information-provision apparatusEP1903445A1 *Jul 10, 2006Mar 26, 2008Mitsubishi Electric CorporationContents server apparatus, contents transferring apparatus and contents reproducing apparatusEP1903445A4 *Jul 10, 2006Jan 20, 2010Mitsubishi Electric CorpContents server apparatus, contents transferring apparatus and contents reproducing apparatusEP2111011A1 *Apr 16, 2008Oct 21, 2009Thomson Telecom BelgiumDevice and method for sharing filesWO2004095767A2 *Apr 16, 2004Nov 4, 2004France TelecomMethod for reading recordings on terminals and method for transmission of data to terminalsWO2004095767A3 *Apr 16, 2004Jul 21, 2005Didier BaronMethod for reading recordings on terminals and method for transmission of data to terminalsWO2005034432A1 *Sep 29, 2004Apr 14, 2005Koninklijke Philips Electronics N.V.Radio system with configurable linksWO2005073856A2 *Jan 26, 2005Aug 11, 2005Koninklijke Philips Electronics, N.V.Audio/video content synchronization through playlistsWO2005073856A3 *Jan 26, 2005Oct 20, 2005Fabien M J GuilloritAudio/video content synchronization through playlistsWO2006072854A1 *Dec 21, 2005Jul 13, 2006Koninklijke Philips Electronics N.V.Method of updating content of a portable deviceWO2009127358A1 *Apr 9, 2009Oct 22, 2009Thomson LicensingDevice and method for sharing filesWO2012020890A1 *Dec 22, 2010Feb 16, 2012Lg Electronics Inc.Car audio system and control method therefor* Cited by examinerClassifications U.S. Classification710/1International ClassificationH04L29/08, H04L12/28, H04L29/06, H04H60/88Cooperative ClassificationH04L65/1036, H04L65/1026, H04L29/06, H04N21/4126, H04H60/88, H04L29/06027, H04L67/289, H04L67/04, H04L67/10European ClassificationH04N21/41P5, H04L29/06, H04L29/08N9, H04L29/08N3, H04H60/88, H04L29/06M2N2M2, H04L29/06M2N2S2Legal EventsDateCodeEventDescriptionMay 16, 2001ASAssignmentOwner name: FULLAUDIO CORPORATION, ILLINOISFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SPURGAT, JEFFREY JONATHAN;GLADWIN, STEPHEN CHRISTOPHER;ANDREWS, HOYET HARRISON, III;REEL/FRAME:011824/0021;SIGNING DATES FROM 20010430 TO 20010516Owner name: FULLAUDIO CORPORATION, ILLINOISFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SPURGAT, JEFFREY JONATHAN;GLADWIN, STEPHEN CHRISTOPHER;ANDREWS, HOYET HARRISON, III;SIGNING DATES FROM 20010430 TO 20010516;REEL/FRAME:011824/0021Sep 25, 2002ASAssignmentOwner name: TRANSAMERICA TECHNOLOGY FINANCE CORPORATION, CONNEFree format text: SECURITY INTEREST;ASSIGNOR:FULLAUDIO CORPORATION;REEL/FRAME:013305/0402Effective date: 20020913Owner name: TRANSAMERICA TECHNOLOGY FINANCE CORPORATION,CONNECFree format text: SECURITY INTEREST;ASSIGNOR:FULLAUDIO CORPORATION;REEL/FRAME:013305/0402Effective date: 20020913Feb 17, 2004ASAssignmentOwner name: SILICON VALLEY BANK, CALIFORNIAFree format text: SECURITY INTEREST;ASSIGNOR:MUSICNOW, INC.;REEL/FRAME:014981/0766Effective date: 20040108Owner name: SILICON VALLEY BANK,CALIFORNIAFree format text: SECURITY INTEREST;ASSIGNOR:MUSICNOW, INC.;REEL/FRAME:014981/0766Effective date: 20040108Mar 30, 2004ASAssignmentOwner name: MUSICNOW, INC., ILLINOISFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FULLAUDIO CORPORATION;REEL/FRAME:015147/0733Effective date: 20031104Owner name: MUSICNOW, INC.,ILLINOISFree format text: CHANGE OF NAME;ASSIGNOR:FULLAUDIO CORPORATION;REEL/FRAME:015147/0733Effective date: 20031104Owner name: MUSICNOW, INC., ILLINOISFree format text: CHANGE OF NAME;ASSIGNOR:FULLAUDIO CORPORATION;REEL/FRAME:015147/0733Effective date: 20031104Apr 23, 2004ASAssignmentOwner name: FULLAUDIO CORPORATION, ILLINOISFree format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:TRANSAMERICA TECHNOLOGY FINANCE CORP.;REEL/FRAME:015246/0764Effective date: 20040205Owner name: FULLAUDIO CORPORATION,ILLINOISFree format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:TRANSAMERICA TECHNOLOGY FINANCE CORP.;REEL/FRAME:015246/0764Effective date: 20040205May 19, 2004ASAssignmentOwner name: MAYLAND, LLC, VIRGINIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MUSICNOW, INC.;REEL/FRAME:015341/0007Effective date: 20040405Owner name: MAYLAND, LLC,VIRGINIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MUSICNOW, INC.;REEL/FRAME:015341/0007Effective date: 20040405Feb 8, 2005ASAssignmentOwner name: MUSICNOW, INC., ILLINOISFree format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:016226/0839Effective date: 20050126Owner name: MUSICNOW, INC.,ILLINOISFree format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:016226/0839Effective date: 20050126Nov 2, 2006ASAssignmentOwner name: MN ACQUISITION LLC, ILLINOISFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FOSS, MICHAEL E.;REEL/FRAME:018471/0388Effective date: 20051031Owner name: MN ACQUISITION LLC,ILLINOISFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FOSS, MICHAEL E.;REEL/FRAME:018471/0388Effective date: 20051031Nov 3, 2006ASAssignmentOwner name: AOL MUSICNOW LLC, ILLINOISFree format text: CHANGE OF NAME;ASSIGNOR:MN ACQUISITION LLC;REEL/FRAME:018480/0021Effective date: 20051101Owner name: MUSICNOW LLC, ILLINOISFree format text: CHANGE OF NAME;ASSIGNOR:MAYLAND, LLC;REEL/FRAME:018471/0996Effective date: 20040317Owner name: MN ACQUISITION LLC, ILLINOISFree format text: CORRECTIVE ASSIGNMENT TO CORRECT THE EFFECTIVE DATE AND THE CONVEYING PARTY DATA PREVIOUSLY RECORDED ON REEL 018471 FRAME 0388;ASSIGNOR:MUSICNOW LLC (F/K/A MAYLAND LLC);REEL/FRAME:018471/0977Effective date: 20051031Owner name: MN ACQUISITION LLC,ILLINOISFree format text: CORRECTIVE ASSIGNMENT TO CORRECT THE EFFECTIVE DATE AND THE CONVEYING PARTY DATA PREVIOUSLY RECORDED ON REEL 018471 FRAME 0388. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:MUSICNOW LLC (F/K/A MAYLAND LLC);REEL/FRAME:018471/0977Effective date: 20051031Owner name: MUSICNOW LLC,ILLINOISFree format text: CHANGE OF NAME;ASSIGNOR:MAYLAND, LLC;REEL/FRAME:018471/0996Effective date: 20040317Owner name: AOL MUSICNOW LLC,ILLINOISFree format text: CHANGE OF NAME;ASSIGNOR:MN ACQUISITION LLC;REEL/FRAME:018480/0021Effective date: 20051101Owner name: MN ACQUISITION LLC, ILLINOISFree format text: CORRECTIVE ASSIGNMENT TO CORRECT THE EFFECTIVE DATE AND THE CONVEYING PARTY DATA PREVIOUSLY RECORDED ON REEL 018471 FRAME 0388. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:MUSICNOW LLC (F/K/A MAYLAND LLC);REEL/FRAME:018471/0977Effective date: 20051031May 27, 2009ASAssignmentOwner name: AOL LLC, VIRGINIAFree format text: MERGER;ASSIGNOR:AOL MUSICNOW LLC;REEL/FRAME:022732/0569Effective date: 20090316Owner name: AOL LLC,VIRGINIAFree format text: MERGER;ASSIGNOR:AOL MUSICNOW LLC;REEL/FRAME:022732/0569Effective date: 20090316Jun 11, 2009ASAssignmentOwner name: MUSICNOW LLC, ILLINOISFree format text: RE-RECORD TO CORRECT A DOCUMENT PREVIOUSLY RECORDED AT REEL 018471, FRAME 0996. (CHANGE OF NAME);ASSIGNOR:MAYLAND, LLC;REEL/FRAME:022818/0256Effective date: 20040413Owner name: MUSICNOW LLC,ILLINOISFree format text: RE-RECORD TO CORRECT A DOCUMENT PREVIOUSLY RECORDED AT REEL 018471, FRAME 0996. (CHANGE OF NAME);ASSIGNOR:MAYLAND, LLC;REEL/FRAME:022818/0256Effective date: 20040413Dec 14, 2009ASAssignmentOwner name: BANK OF AMERICAN, N.A. AS COLLATERAL AGENT,TEXASFree format text: SECURITY AGREEMENT;ASSIGNORS:AOL INC.;AOL ADVERTISING INC.;BEBO, INC.;AND OTHERS;REEL/FRAME:023649/0061Effective date: 20091209Owner name: BANK OF AMERICAN, N.A. AS COLLATERAL AGENT, TEXASFree format text: SECURITY AGREEMENT;ASSIGNORS:AOL INC.;AOL ADVERTISING INC.;BEBO, INC.;AND OTHERS;REEL/FRAME:023649/0061Effective date: 20091209Dec 31, 2009ASAssignmentOwner name: AOL INC.,VIRGINIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AOL LLC;REEL/FRAME:023720/0309Effective date: 20091204Owner name: AOL INC., VIRGINIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AOL LLC;REEL/FRAME:023720/0309Effective date: 20091204Nov 16, 2010ASAssignmentOwner name: SPHERE SOURCE, INC, VIRGINIAFree format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416Effective date: 20100930Owner name: GOING INC, MASSACHUSETTSFree format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416Effective date: 20100930Owner name: MAPQUEST, INC, COLORADOFree format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416Effective date: 20100930Owner name: AOL INC, VIRGINIAFree format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416Effective date: 20100930Owner name: LIGHTNINGCAST LLC, NEW YORKFree format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416Effective date: 20100930Owner name: AOL ADVERTISING INC, NEW YORKFree format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416Effective date: 20100930Owner name: YEDDA, INC, VIRGINIAFree format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416Effective date: 20100930Owner name: NETSCAPE COMMUNICATIONS CORPORATION, VIRGINIAFree format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416Effective date: 20100930Owner name: TACODA LLC, NEW YORKFree format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416Effective date: 20100930Owner name: TRUVEO, INC, CALIFORNIAFree format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416Effective date: 20100930Owner name: QUIGO TECHNOLOGIES LLC, NEW YORKFree format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:BANK OF AMERICA, N A;REEL/FRAME:025323/0416Effective date: 20100930Feb 22, 2012ASAssignmentOwner name: AOL LLC, VIRGINIAFree format text: MERGER;ASSIGNOR:AOL MUSICNOW LLC;REEL/FRAME:027741/0205Effective date: 20090317Owner name: AOL INC., VIRGINIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AOL LLC;REEL/FRAME:027741/0321Effective date: 20091204Owner name: MUSICNOW LLC, VIRGINIAFree format text: CHANGE OF NAME;ASSIGNOR:MAYLAND, LLC;REEL/FRAME:027746/0991Effective date: 20040412Owner name: MUSICNOW, INC., ILLINOISFree format text: CHANGE OF NAME;ASSIGNOR:FULLAUDIO CORPORATION;REEL/FRAME:027746/0988Effective date: 20031105Owner name: AOL MUSICNOW LLC, ILLINOISFree format text: CHANGE OF NAME;ASSIGNOR:MN ACQUISITION LLC;REEL/FRAME:027747/0001Effective date: 20051101Owner name: MAYLAND, LLC, VIRGINIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MUSICNOW, INC.;REEL/FRAME:027741/0074Effective date: 20040405Owner name: MN ACQUISITION LLC, ILLINOISFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MUSICNOW LLC;REEL/FRAME:027741/0116Effective date: 20051031Owner name: FULLAUDIO CORPORATION, ILLINOISFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SPURGAT, JEFFREY JONATHAN;GLADWIN, STEPHEN CHRISTOPHER;ANDREWS, HOYET HARRISON, III;SIGNING DATES FROM 20010430 TO 20010516;REEL/FRAME:027740/0979Jul 3, 2012ASAssignmentOwner name: FACEBOOK, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AOL INC.;REEL/FRAME:028487/0534Effective date: 20120614Jul 16, 2014FPAYFee paymentYear of fee payment: 4RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services