SYSTEM AND CONSTITUENT MEDIA DEVICE COMPONENTS AND MEDIA DEVICE-BASED ECOSYSTEM

Embodiments of the present application relate generally to electrical and electronic hardware, computer software, wired and wireless network communications, wearable, hand held, and portable computing devices for facilitating communication of information and presentation of media. An ecosystem of wireless media devices may be in wireless communication with one another and with at least one wireless user device (e.g., smartphone, tablet or pad). The wireless media devices are configured to detect proximity and/or presence of wireless user devices, objects, or users in proximity of one or more of the wireless media devices and to capture and take over content handling from the at least one wireless user device. In some examples, the wireless media devices are powered by a rechargeable power source, such as a rechargeable battery or the like. Wireless media devices may vary in size such as personal, pocketable, portable, ultra-portable, head worn, shared household, table top, etc.

DETAILED DESCRIPTION

Various embodiments or examples may be implemented in numerous ways, including as a system, a process, an apparatus, a user interface, or a series of program instructions on a non-transitory computer readable medium such as a computer readable storage medium or a computer network where the program instructions are sent over optical, electronic, or wireless communication links. In general, operations of disclosed processes may be performed in an arbitrary order, unless otherwise provided in the claims.

Prior to describing an ecosystem of wireless media devices, attention is directed toFIG. 1, where a block diagram will be used to illustrate one example of architecture for a wireless media device. The architecture depicted is a non-limiting example and the components (e.g., the various blocks depicted inFIG. 1) of the architecture may be the same or different among wireless media devices in an ecosystem. The ecosystem may include just a single wireless media device or a plurality of wireless media devices. The ecosystem may be dynamic and at any given time may vary in the number of wireless media devices present in the ecosystem. Further, dynamics of the ecosystem may include variations in the number of user devices (e.g., wireless user devices) and users that are present in the ecosystem at any given time. Dynamics of the ecosystem may include at any given time the addition of or removal of a selected one or more of media devices, wireless user devices, or users. One or more systems in one or more media devices may be configured to detect (e.g., wirelessly) one or more of presence, motion, or relative position of other media devices, wireless user devices, users, or other objects (e.g., pets) in the ecosystem.

FIG. 1depicts a block diagram of one embodiment of a wireless media device100(media device100hereinafter) having systems including but not limited to a controller101, a data storage (DS) system103, a input/output (I/O) system105, a radio frequency (RF) system107, an audio/video (NV) system109, a power system111, and a proximity sensing (PROX) system113. A bus110enables electrical communication between the controller101, DS system103, I/O system105, RF system107, AV system109, power system111, and PROX system113. Power bus112supplies electrical power from power system111to the controller101, DS system103, I/O system105, RF system107, AV system109, and PROX system113.

Power system111may include a power source internal to the media device100such as a battery (e.g., AAA or AA batteries) or a rechargeable battery (e.g., such as a lithium ion or nickel metal hydride type battery, etc.) denoted as BAT135. Power system111may be electrically coupled with a port114for connecting an external power source (not shown) such as a power supply that connects with an external AC or DC power source. Examples include but are not limited to a wall wart type of power supply that converts AC power to DC power or AC power to AC power at a different voltage level. In other examples, port114may be a connector (e.g., an IEC connector) for a power cord that plugs into an AC outlet or other type of connecter, such as a universal serial bus (USB) connector. Power system111provides DC power for the various systems of media device100. Power system111may convert AC or DC power into a form usable by the various systems of media device100. Power system111may provide the same or different voltages to the various systems of media device100. In applications where a rechargeable battery is used for BAT135, the external power source may be used to power the power system111, recharge BAT135, or both. Further, power system111on its own or under control or controller101may be configured for power management to reduce power consumption of media device100, by for example, reducing or disconnecting power from one or more of the systems in media device100when those systems are not in use or are placed in a standby or idle mode. Power system111may also be configured to monitor power usage of the various systems in media device100and to report that usage to other systems in media device100and/or to other devices (e.g., including other media devices100) using one or more of the I/O system105, RF system107, and AV system109, for example. Operation and control of the various functions of power system111may be externally controlled by other devices (e.g., including other media devices100).

Controller101controls operation of media device100and may include a non-transitory computer readable medium, such as executable program code to enable control and operation of the various systems of media device100. DS103may be used to store executable code used by controller101in one or more data storage mediums such as ROM, RAM, SRAM, RAM, SSD, Flash, etc., for example. Controller101may include but is not limited to one or more of a microprocessor (μP), a microcontroller (μP), a digital signal processor (DSP), a baseband processor, an application specific integrated circuit (ASIC), just to name a few. Processors used for controller101may include a single core or multiple cores (e.g., dual core, quad core, etc.). Port116may be used to electrically couple controller101to an external device (not shown).

DS system103may include but is not limited to non-volatile memory (e.g., Flash memory), SRAM, DRAM, ROM, SSD, just to name a few. In that the media device100in some applications is designed to be compact, portable, or to have a small size footprint, memory in DS103will typically be solid state memory (e.g., no moving or rotating components); however, in some application a hard disk drive (HDD) or hybrid HDD may be used for all or some of the memory in DS103. In some examples, DS103may be electrically coupled with a port128for connecting an external memory source (e.g., USB Flash drive, SD, SDHC, SDXC, microSD, Memory Stick, CF, SSD, etc.). Port128may be a USB or mini USB port for a Flash drive or a card slot for a Flash memory card. In some examples as will be explained in greater detail below, DS103includes data storage for configuration data, denoted as CFG125, used by controller101to control operation of media device100and its various systems. DS103may include memory designate for use by other systems in media device100(e.g., MAC addresses for WiFi130, network passwords, data for settings and parameters for NV109, and other data for operation and/or control of media device100, etc.). DS103may also store data used as an operating system denoted as OS1 for controller101, or other controllers and/or processors. If controller101includes a DSP, then DS103may store data, algorithms, program code, an OS, etc. for use by the DSP, for example. In some examples, one or more systems in media device100may include their own data storage systems. OS1 may be an operating system that is proprietary to the media device100.

I/O system105may be used to control input and output operations between the various systems of media device100via bus110and between systems external to media device100via port118. Port118may be a connector (e.g., USB, HDMI, Ethernet, fiber optic, Toslink, Firewire, IEEE 1394, or other) or a hard wired (e.g., captive) connection that facilitates coupling I/O system105with external systems. In some examples port118may include one or more switches, buttons, or the like, used to control functions of the media device100such as a power switch, a standby power mode switch, a button for wireless pairing, an audio muting button, an audio volume control, an audio mute button, a button for connecting/disconnecting from a WiFi network, an infrared (IR) transceiver, just to name a few. I/O system105may also control indicator lights, audible signals, or the like (not shown) that give status information about the media device100, such as a light to indicate the media device100is powered up, a light to indicate the media device100is in wireless communication (e.g., WiFi, Bluetooth®, WiMAX, cellular, etc.), a light to indicate the media device100is Bluetooth® paired, in Bluetooth® pairing mode, Bluetooth® communication is enabled, a light to indicate the audio and/or microphone is muted, just to name a few. Audible signals may be generated by the I/O system105or via the AV system107to indicate status, etc. of the media device100. Audible signals may be used to announce Bluetooth® status, powering up or down the media device100, muting the audio or microphone, an incoming phone call, a new message such as a text, email, or SMS, just to name a few. In some examples, I/O system105may use optical technology to wirelessly communicate with other media devices100or other devices. Examples include but are not limited to infrared (IR) transmitters, receivers, transceivers, an IR LED, and an IR detector, just to name a few. I/O system105may include an optical transceiver OPT185that includes an optical transmitter185t(e.g., an IR LED) and an optical receiver185r(e.g., a photo diode). OPT185may include the circuitry necessary to drive the optical transmitter185twith encoded signals and to receive and decode signals received by the optical receiver185r. Bus110may be used to communicate signals to and from OPT185. OPT185may be used to transmit and receive IR commands consistent with those used by infrared remote controls used to control AV equipment, televisions, computers, and other types of systems and consumer electronics devices. The IR commands may be used to control and configure the media device100, or the media device100may use the IR commands to configure/re-configure and control other media devices or other user devices, for example.

RF system107includes at least one RF antenna124that is electrically coupled with a plurality of radios (e.g., RF transceivers) including but not limited to a Bluetooth® (BT) transceiver120, a WiFi transceiver130(e.g., for wireless communications over a wireless and/or WiMAX network), and a proprietary Ad Hoc (AH) transceiver140pre-configured (e.g., at the factory) to wirelessly communicate with a proprietary Ad Hoc wireless network (AH-WiFi) (not shown). AH140and AH-WiFi are configured to allow wireless communications between similarly configured media devices (e.g., an ecosystem comprised of a plurality of similarly configured media devices) as will be explained in greater detail below. RF system107may include more or fewer radios than depicted inFIG. 1and the number and type of radios will be application dependent. Furthermore, radios in RF system107need not be transceivers, RF system107may include radios that transmit only or receive only, for example. Optionally, RF system107may include a radio150configured for RF communications using a proprietary format, frequency band, or other existent now or to be implemented in the future. Radio150may be used for cellular communications (e.g., 3G, 4G, or other), for example. Antenna124may be configured to be a de-tunable antenna such that it may be de-tuned129over a wide range of RF frequencies including but not limited to licensed bands, unlicensed bands, WiFi, WiMAX, cellular bands, Bluetooth®, from about 2.0 GHz to about 6.0 GHz range, and broadband, just to name a few. As will be discussed below, PROX system113may use the de-tuning129capabilities of antenna124to sense proximity of the user, other people, the relative locations of other media devices100, just to name a few. Radio150(e.g., a transceiver) or other transceiver in RF107, may be used in conjunction with the de-tuning capabilities of antenna124to sense proximity, to detect and or spatially locate other RF sources such as those from other media devices100, devices of a user, just to name a few. RF system107may include a port123configured to connect the RF system107with an external component or system, such as an external RF antenna, for example. The transceivers depicted inFIG. 1are non-limiting examples of the type of transceivers that may be included in RF system107. RF system107may include a first transceiver configured to wirelessly communicate using a first protocol, a second transceiver configured to wirelessly communicate using a second protocol, a third transceiver configured to wirelessly communicate using a third protocol, and so on. One of the transceivers in RF system107may be configured for short range RF communications, such as within a range from about 1 meter to about 15 meters, or less, for example. Another one of the transceivers in RF system107may be configured for long range RF communications, such any range up to about 50 meters or more, for example. Short range RF may include Bluetooth®; whereas, long range RF may include WiFi, WiMAX, cellular, and Ad Hoc wireless, for example.

AV system109includes at least one audio transducer, such as a loud speaker160, a microphone170, or both. AV system109further includes circuitry such as amplifiers, preamplifiers, or the like as necessary to drive or process signals to/from the audio transducers. Optionally, AV system109may include a display (DISP)180, a video device (VID)190(e.g., an image captured device or a web CAM, etc.), or both. DISP180may be a display and/or touch screen (e.g., a LCD, OLED, LED, flat panel display, micro or pico-projector) for displaying content, video media, images, information relating to operation of media device100, content available to or operated on by the media device100, playlists for media, date and/or time of day, alpha-numeric text and characters, caller ID, file/directory information, a GUI, just to name a few. DISP180may comprise more than one display device such as a touch screen for displaying data and a GUI for a user to interact with and a separate image projection device for projecting images, video, content, and the like on a surface, such as a micro-projector or pico-projector, for example. A port122may be used to electrically couple AV system109with an external device and/or external signals. Port122may be a USB, HDMI, Firewire/IEEE-1394, 3.5 mm audio jack, or other. For example, port122may be a 3.5 mm audio jack for connecting an external speaker, headphones, earphones, etc. for listening to audio content being processed by media device100. As another example, port122may be a 3.5 mm audio jack for connecting an external microphone or the audio output from an external device. In some examples, SPK160may include but is not limited to one or more active or passive audio transducers such as woofers, concentric drivers, tweeters, super tweeters, midrange drivers, sub-woofers, passive radiators, just to name a few. MIC170may include one or more microphones and the one or more microphones may have any polar pattern suitable for the intended application including but not limited to omni-directional, directional, bi-directional, uni-directional, bi-polar, uni-polar, any variety of cardioid pattern, and shotgun, for example. MIC170may be configured for mono, stereo, or other. MIC170may be configured to be responsive (e.g., generate an electrical signal in response to sound) to any frequency range including but not limited to ultrasonic, infrasonic, from about 20 Hz to about 20 kHz, and any range within or outside of human hearing. In some applications, the audio transducer of AV system109may serve dual roles as both a speaker and a microphone.

Circuitry in AV system109may include but is not limited to a digital-to-analog converter (DAC) and algorithms for decoding and playback of media files such as MP3, FLAG, AIFF, ALAC, WAV, MPEG, QuickTime, AVI, compressed media files, uncompressed media files, and lossless media files, just to name a few, for example. A DAC may be used by AV system109to decode wireless data from a user device or from any of the radios in RF system107. AV system109may also include an analog-to-digital converter (ADC) for converting analog signals, from MIC170for example, into digital signals for processing by one or more system in media device100.

Media device100may be used for a variety of applications including but not limited to wirelessly communicating with other wireless devices, other media devices100, wireless networks, and the like for playback of media (e.g., streaming content), such as audio, for example. The actual source for the media need not be located on a user's device (e.g., smart phone, MP3 player, iPod, iPhone, iPad, Android, laptop, PC, etc.). For example, media files to be played back on media device100may be located on the Internet, a web site, or in the Cloud, and media device100may access (e.g., over a WiFi network via WiFi130) the files, process data in the files, and initiate playback of the media files. Media device100may access or store in its memory a playlist or favorites list and playback content listed in those lists. In some applications, media device100will store content (e.g., files) to be played back on the media device100or on another media device100.

In other examples, housing199may be configured as speaker, a subwoofer, a conference call speaker, an intercom, a media playback device, just to name a few. If configured as a speaker, then the housing199may be configured as a variety of speaker types including but not limited to a left channel speaker, a right channel speaker, a center channel speaker, a left rear channel speaker, a right rear channel speaker, a subwoofer, a left channel surround speaker, a right channel surround speaker, a left channel height speaker, a right channel height speaker, any speaker in a 3.1, 5.1, 7.1, 9.1 or other surround sound format including those having two or more subwoofers or having two or more center channels, for example. In other examples, housing199may be configured to include a display (e.g., DISP180) for viewing video, serving as a touch screen interface for a user, providing an interface for a GUI, for example.

PROX system113may include one or more sensors denoted as SEN195that are configured to sense197an environment198external to the housing199of media device100. Using SEN195and/or other systems in media device100(e.g., antenna124, SPK160, MIC170, etc.), PROX system113senses197an environment198that is external to the media device100(e.g., external to housing199). PROX system113may be used to sense one or more of proximity of the user or other persons to the media device100or other media devices100. PROX system113may use a variety of sensor technologies for SEN195including but not limited to ultrasound, infrared (IR), passive infrared (PIR), optical, acoustic, vibration, light, ambient light sensor (ALS), IR proximity sensors, LED emitters and detectors, RGB LED's, RF, temperature, capacitive, capacitive touch, inductive, just to name a few. PROX system113may be configured to sense location of users or other persons, user devices, and other media devices100, without limitation. Output signals from PROX system113may be used to configure media device100or other media devices100, to re-configure and/or re-purpose media device100or other media devices100(e.g., change a role the media device100plays for the user, based on a user profile or configuration data), just to name a few. A plurality of media devices100in an eco-system of media devices100may collectively use their respective PROX system113and/or other systems (e.g., RF107, de-tunable antenna124, AV109, etc.) to accomplish tasks including but not limited to changing configuration, re-configuring one or more media devices, implement user specified configurations and/or profiles, insertion and/or removal of one or more media devices in an eco-system, just to name a few.

In other examples, PROX113may include one or more proximity detection islands PSEN196as will be discussed in greater detail inFIGS. 3-6. PSEN196may be positioned at one or more locations on chassis199and configured to sense an approach of a user or other person towards the media device100or to sense motion or gestures of a user or other person by a portion of the body such as a hand for example. PSEN196may be used in conjunction with or in place of one or more of SEN195, OPT185, SPK160, MIC170, RF107and/or de-tunable129antenna124to sense proximity and/or presence in an environment surrounding the media device100, for example. PSEN196may be configured to take or cause an action to occur upon detection of an event (e.g., an approach or gesture by user201or other) such as emitting light (e.g., via an LED), generating a sound or announcement (e.g., via SPK160), causing a vibration (e.g., via SPK160or a vibration motor), display information (e.g., via DISP180), trigger haptic feedback, for example. In some examples, PSEN196may be included in I/O105instead of PROX113or be shared between one or more systems of media device100. In other examples, components, circuitry, and functionality of PSEN196may vary among a plurality of PSEN196sensors in media device100such that all PSEN196are not identical. PSEN196may be referred to below as proximity detection islands (I1-I4).

FIG. 2depicts an exemplary computer system200suitable for use in the systems, methods, and apparatus described herein. In some examples, computer system200may be used to implement computer programs, applications (e.g., APP's), configurations (e.g., CFG's), methods, processes, or other software to perform the above-described techniques. Computer system200includes a bus202or other communication mechanism for communicating information, which interconnects subsystems and devices, such as one or more processors204, system memory206(e.g., RAM, SRAM, DRAM, Flash), storage device208(e.g., Flash, ROM), disk drive210(e.g., magnetic, optical, solid state), communication interface212(e.g., modem, Ethernet, WiFi), display214(e.g., CRT, LCD, touch screen), input device216(e.g., keyboard, stylus), and cursor control218(e.g., mouse, trackball, stylus). Some of the elements depicted in computer system200may be optional, such as elements214-218, for example and computer system200need not include all of the elements depicted.

According to some examples, computer system200performs specific operations by processor204executing one or more sequences of one or more instructions stored in system memory206. Such instructions may be read into system memory206from another non-transitory computer readable medium, such as storage device208or disk drive210(e.g., a HD or SSD). In some examples, circuitry may be used in place of or in combination with software instructions for implementation. The term “non-transitory computer readable medium” refers to any tangible medium that participates in providing instructions to processor204for execution. Such a medium may take many forms, including but not limited to, non-volatile media and volatile media. Non-volatile media includes, for example, optical, magnetic, or solid state disks, such as disk drive210. Volatile media includes dynamic memory, such as system memory206. Common forms of non-transitory computer readable media includes, for example, floppy disk, flexible disk, hard disk, SSD, magnetic tape, any other magnetic medium, CD-ROM, DVD-ROM, Blu-Ray ROM, USB thumb drive, SD Card, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, RAM, PROM, EPROM, FLASH-EPROM, any other memory chip or cartridge, or any other medium from which a computer may read.

Instructions may further be transmitted or received using a transmission medium. The term “transmission medium” may include any tangible or intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible medium to facilitate communication of such instructions. Transmission media includes coaxial cables, copper wire, and fiber optics, including wires that comprise bus202for transmitting a computer data signal. In some examples, execution of the sequences of instructions may be performed by a single computer system200. According to some examples, two or more computer systems200coupled by communication link220(e.g., LAN, Ethernet, PSTN, or wireless network) may perform the sequence of instructions in coordination with one another. Computer system200may transmit and receive messages, data, and instructions, including programs, (i.e., application code), through communication link220and communication interface212. Received program code may be executed by processor204as it is received, and/or stored in disk drive210, or other non-volatile storage for later execution. Computer system200may optionally include a wireless transceiver213in communication with the communication interface212and coupled215with an antenna217for receiving and generating RF signals221, such as from a WiFi network, BT radio, or other wireless network and/or wireless devices, for example. Examples of wireless devices include but are not limited to: a data capable strap band, wristband, wristwatch, digital watch, or wireless activity monitoring and reporting device; a smartphone; cellular phone; tablet; tablet computer; pad device (e.g., an iPad); touch screen device; touch screen computer; laptop computer; personal computer; server; personal digital assistant (PDA); portable gaming device; a mobile electronic device; and a wireless media device, just to name a few. Computer system200in part or whole may be used to implement one or more components of media devices100of FIGS.1and3-4. For example, processor175, wireless module177, display110, and optical sensor120may be implemented using one or more elements of computer system200. Computer system200in part or whole may be used to implement a remote server or other compute engine in communication with media devices100of FIGS.1and3-4.

Turning now toFIG. 3, one example of an ecosystem300includes one or more media devices. Here, ecosystem300is depicted as including a media device100although the ecosystem300may include additional media devices as denoted by100n. Media device100may be in wireless communication126with other media devices (not shown) and with one or more wireless user devices. Media devices100may detect presence and/or proximity of one or more wireless user devices, one or more users301or one or more objects. InFIG. 3, ecosystem300is depicted as including a plurality of wireless user devices denoted as310,312,314,316,318,320, and322. However, there may more of fewer wireless user devices than depicted, and in some scenarios, there may be no (zero) wireless user devices. The number and variety of wireless user devices depicted are presented to illustrate the number and diversity of wireless user devices the ecosystem300of media device100may recognize, wirelessly communicate with, and interact with to serve the needs of one or more users301. Moreover, the number and variety of wireless user devices depicted also illustrate the ability of the media devices100to recognize, wirelessly communicate with, and interact with wireless user devices from a variety of different manufactures. That is, the media devices100are configured to seamlessly work with wireless user devices from manufactures other than a manufacture of the media device100. Ecosystem300may also interact with a user301; however, there may be no users (zero), or there may be more than one user301as denoted by301n. Interaction with a user301or other object may include detecting presence and/or proximity of the user301or object and one or more of the media devices100taking some action or actions based on the detecting.

Wireless user devices310,312,314,316,318,320, and322may be in wireless communications with media device100using one or more wireless protocols as denoted by311,313,315,317,319,321, and323. Furthermore, the media device100and/or one or more of the wireless user devices may be in wireless communications (351) with one or more of backend services350. The media device100and/or wireless user devices may communicate (381,391) with backend service350via wireless network380,390or both. Although not depicted, communication with backend service350may be wired352(e.g., LAN, Ethernet, fiber optic), wireless, or both. Wireless networks380or390may also include a wired connection denoted as382and392respectively. In some applications there may be no distinction between backend service350and the instrumentalities used to access the backend service350, such as wireless networks380or390. Therefore, in some examples a backend service may include the wired or wireless communications networks that enable communication with the backend service. Backend service350may include one or more compute engines such as server353and may include one or more data storage devices such as data store357. Data store357may take on many forms such as RAID, HDD, SSD, Flash memory, just to name a few. Server353may comprise a server farm or many servers in racks, for example. In other examples, backend service may comprise one or more Cloud based resources or one or more locations/addresses/URL's on the Internet or an intranet.

Media devices100may include a variety of features and may have functionalities that differ among the media devices in ecosystem300. Features and functionalities in the example media device100depicted inFIG. 3may include but are not limited to: one or more speakers SPK160; one or more microphones MIC170; one or more proximity detection islands I1-I4 (e.g., PSEN196); a display180; a plurality of controls denoted as399, such as play, pause, fast forward, fast reverse, volume up “+”, volume down “−”, volume mute and/or BT pairing “0”, and one or more function buttons/keys f1-f6; and an RF antenna124for use by the various RF transceivers in RF107.

Some of the wireless user devices may not have the RF communications hardware necessary to access backend service350and/or wireless networks380and390. For example, wireless user device312may comprise a data capable strap band, wristband, wristwatch, digital watch, or wireless activity monitoring and reporting device. Wireless user device312may wirelessly communicate313using a Bluetooth protocol with one or more of the media devices100; however, wireless user device312may not be able to directly wirelessly communicate (351,381,391) with backend service350or wireless networks380and/or390. One of the media devices100may establish a wireless communications link with device312using its respective BT radio120and may, concurrently or subsequently, use another one of its RF transceivers to wirelessly communicate126with another resource such as backend service350or a wireless network (380,390). For example, if wireless user device312includes data about user301(e.g., dietary, calories burned, calorie intake, heart rate, sleep patterns, etc.) that the user301wants to upload to the user's page on a social network, the device312and media device100may negotiate the transfer of that data using the BT link and then the media device100may wirelessly link with backend service350to transmit/upload the user data to the user's page on the social network. Similarly, data may be pushed from the backend service350to the device312using the media device100as an intermediary communications portal. As one example, data for an alarm to be set on the device312may be stored on backend service350and transmitted to the media device100(e.g., using WiFi130), which in turns transmits the alarm data to the wireless user device312(e.g., using BT120). Other types of data, such as software or software updates may be downloaded to device312from backend service350using the media device100as a wireless communications link between312and350.

Media devices100in ecosystem300need not be physically positioned in the same room or location, so long as a communications link (wireless or wired) is maintained between media devices in the ecosystem300. In the above examples for wireless user device316, one or more of the media devices100may be positioned at different locations or rooms, in a house or office, for example. If user301is in room 1 and the audio content is being handled by a media device100in room 1, then the user301may subsequently move from room 1 to room 2 were another media device100is present. The media device100in room 1 may handoff the handling of the audio content to the media device100in room 2. The handoff may occur once user301and/or device316are in proximity detection range of the media device100in room 2. Alternatively, once the user301and/or device316move out of proximity detection range of the media device100in room 1, that media device may handoff the audio content back to device316and the media device100in room 2 takes over handling the audio content when the user301and/or device316are in proximity detection range of the media device100in room 2.

User device316may be a wireless headset that is configured to wirelessly communicate using BT. Some or all of the media devices100in ecosystem300may recognize device316when it is in RF proximity of the media devices and may arbitrate among the media devices100as to which media devices100will establish a wireless communications link with device316and interact with device316. As one example, user301may be presently in a phone conversation on user device320for which the audio portions of the conversation are being handled by headset316. Sometime after the conversation has commenced the user devices316and320enter in proximity of one or more of the media devices100in ecosystem300. Media devices100may be configured (e.g., via CFG125) based on user preferences or other criteria, to wirelessly link with device316(e.g., using BT) and to transfer the audio content of the conversation to one or more of the media devices100, such that those media devices100serve as a speaker phone or conference call phone. As another example, as the conversation proceeds with the audio being handled by the media devices100, one or more of the media devices may detect presence and/or proximity of another user/object or user device.

Media devices100may be configured (e.g., via CFG125) based on user preferences or other criteria, to switch the audio content back to device316because the user301may have set a preference (e.g., via CFG125) to have private conversations when there are other persons present. Here, any of the various systems of the media devices100may have detected presence and/or proximity using one or more of PROX113, RF107, or NV109to determine that someone other than user301is in proximity of the user301and may hear his/her conversation. One or more media devices100other than the one handling the audio content may be the media device(s) that detects the presence and/or proximity and may wirelessly communicate to the media device100that is handling the audio content that presence and/or proximity has been detected, causing the media device100that is handling the audio content to switch the audio handling back to wireless user device316. In some examples, detections of presence and/or proximity may be by the RF signature of another wireless user device that enters within RF detection range of one or more media devices100in ecosystem300. In other examples, one or more proximity detection islands on one or more of the media devices100detects presence and/or proximity and wirelessly communicates the detected event to other media devices100in the ecosystem300.

Wireless user devices may be configured to implement control of some functions of a media device100. For example, user device316may transfer handling of a phone call to media device100where SPK160and MIC170allow the media device to function as a speaker phone of conference call phone. If the subject matter of the conversation suddenly requires discretion, user301may actuate318a button, switch, or other control element on device316. Upon actuation, device316wirelessly signals317media device100to surrender handling of the conversation back to device316where the conversation is now conducted over the headset. If the user301actuates318the button again, the conversation may be switched back to the media device100. In other examples, actuation318of the button may “Mute” the phone conversation being handled on the media device100and a subsequent actuation318of the button “Un-mutes” the conversation. CFG125on media device100and/or an APP225installed on user device316may be used to orchestrate which device handles content at any given time.

As another example, wireless user device312may include one or more accelerometers, gyroscopes, or other sensors that enable the device312to sense motion of user301when the device is worn or handled by the user301. Those sensors may sense motion, acceleration, vibrations, rotation, etc., about one or more axes, such as X-Y-Z axes370. One or more signals generated by those sensors may be processed and may be wirelessly transmitted313to media device100to effectuate some action on media device100. For example, user301may actuate319a button, switch, or other control element on device312that wirelessly transmits313data (e.g., diametric and activity data collected from user301) to media device100to media device100. Media device100may parse the data and display information regarding the data on display180and/or using sound via SPK160. The data may comprise: 1) calories burned; 2) calories consumed; 3) heart rate; 4) user's weight; 5) miles ran; and 6) sleep activity. Items 1)-6) may be displayed as icons on display180and by moving or otherwise articulating his/her wrist or body, the X-Y-Z motions may be converted to signals that are wirelessly transmitted313to media device100and operative to cause one of the items 1)-6) be highlighted or otherwise selected on display180. User301may actuate319the button to cause media device100to download the selected item (e.g., user's weight) to a web page the user301maintains on backend service350. More than one of the items 1)-6) may be selected for download.

As another example, display180may present information such as the availability of a software update, an alarm, a new set of health/wellness goals, etc. and the user301may articulate the device312to select one or more items of the displayed information to be uploaded into device312. Here, even though user device312does not have direct wireless access to backend service350, the Internet, or wireless networks (380,390), access is nevertheless essentially provided by using the media device100as a surrogate or intermediary connection to those wireless resources. If an alarm that has already been set has been handed over to the media device100to execute, then upon execution of the alarm (e.g., a wake-up alarm) by media device100, the user301may actuate319the button one time to put the alarm in “Snooze” mode or may actuate319the button two times to “Cancel” the alarm.

The functionality described above for devices312and316may apply to the other wireless user devices depicted as examples inFIG. 3, such as devices311,320,322,314, and318. A phone call of conference call on devices320and/or314may be transferred to media device100for handling, a VoIP call with audio and/or video content may be presently being handled by devices311and/or318and may be subsequently transferred over to media device100. The video portion of the content may remain on display of devices (311,318) and the audio portion may be transferred over to media device100such that the MIC170and SPK160are used to handle the audio portions of the VoIP call.

Wireless user device322may be handling content related to a video game and the audio and/or video content of that game may be transferred to media device100for handling. The game may have a surround sound or multi-dimensional (e.g., 3D) sound track. If ecosystem300includes a plurality of media devices100, then those devices may wirelessly126communicate with one another and arbitrate which media device100will handle which channels of the sound track. For example, if the game includes a 5.1 surround sound track and there are six media devices100in ecosystem300, then a first media device100will handle the left channel, a second media device100will handle the right channel, a third media device100will handle the center channel, a fourth media device100will handle the left rear channel, a fifth media device100will handle the right rear channel, and a sixth media device100will handle the low frequency channel (e.g., subwoofer channel). If there are only three media devices100in ecosystem300, then a first media device100will handle the left channel, a second media device100will handle the right channel, a third media device100will handle the center channel. Those three media devices100may act in concert to user their respective A/V systems109and processors/controllers to synthesize the left and right rear channels.

Wireless user devices (e.g.,310,314,320,322,318) that are handling a broad variety of content may, when in proximity (e.g., physical or RF) of ecosystem300have that content and optionally the wireless bandwidth associated with the content, transferred over to one or more media devices in ecosystem300. Furthermore, information or data associated with the content (e.g., playlists, bookmarks, favorites, locations for content, etc.) may be transferred over to one or more media devices in ecosystem300. The one or more media devices100may wirelessly access whatever backend services350as necessary to execute handling of the content being transferred. As one example, user301may be listening to music from a library of tunes based on a playlist resident on user device310. The actual data (e.g., content files, MP3, FLAG, AIFF, etc.) are not resident in memory of device310, but rather are located in a remote external location, such as backend service350. Upon establishing a wireless communications link with device310, a media device100may wirelessly receive a copy of the playlist from device310as well as a location and access information (e.g., username/email address and password) from user device310and then wirelessly access backend service350or other resource to take over playback of the content on media device100. Track and timestamp information associated with the current item of content being played back on device310may also be transferred so that media device100can resume playback at exactly or approximately the same point in time so that there is no or minimal delay or interruption in playback from the standpoint of user301. Media device100may use its own internal data storage system (e.g., DS103) to store the playlist and/or buffer or store content on the playlist. In some examples, the playlist may reside external to the media device100(e.g., on backend service350). An application (e.g., APP225) in user device310and/or a configuration (e.g., CFG125) in media device100may be used to determine the transfer of content to/from devices310and100. The plurality of controls399, display180(e.g., using a GUI), voice commands received by MIC170, a display of device310(e.g., using a GUI), or other controls on device310may be used to control playback of the content being handled by media device100. For example, a GUI on device310may show which track of content is currently being handled by media device100and user301may touch and icon or the like to cause a variety of functions associated with content playback to occur such as advancing to the next track in the playlist to be played, changing the volume of playback, pausing playback, muting volume, viewing metadata, viewing liner notes, displaying CD/album artwork, just to name a few. Control functions on the media device100and user device310may be simultaneously active so that user301may use either device to control content and/or playback on media device100.

If more than one wireless user device (e.g.,318and310or320,314, and322) is detected in proximity of the media devices100in ecosystem300, then those media devices100may arbitrate which user device is to have its content serviced by which media devices100. For example, CFG125in those media devices100may recognize (e.g., via RF signature, MAC address, etc.) that user device318is designated as a master device that has preference over other devices that are present in the ecosystem300. To that end, content from device318is serviced by the media devices and other devices that are present in the ecosystem300may be placed in a service queue based on the order in which they were detected or in some other queuing order. User301may prefer (e.g., via APP225and/or CFG125) that user devices from guests be serviced at a priority that is higher than the user's301own wireless devices (e.g., device314). To that end when device314is present and guest device321is also present, then media devices100will service the content on device321and/or allow services provided by the media devices100to be accessed by device321. For example, services provided by media devices100may include content and playlists of user301that are made available to a user of device321to access for playback, etc., or user of device321may be granted access to NAS, network printers, or the Internet via a wireless network (e.g.,390) that the media devices100use for wireless communication126between each other (e.g., WiFi130) and with external sources (e.g., backend service350).

FIG. 4depicts another example of an ecosystem400. Ecosystem400includes five media devices100denoted as100i-100v; however, ecosystem400may include fewer or more media devices than depicted as denoted by100n. Each media device100i-100vis in wireless communication (126,411and451) with the other media devices, with user devices410, and backend service450. User devices410may include at least one user device413but may also represent more user devices as denoted by410n. Backend service450may represent one or more resources that may be accessed (wirelessly, wired, or both) directly or indirectly by media devices100i-100vand optionally user devices410. Backend service450may include but is not limited to data storage systems, compute engines, wireless communications networks, wired communications networks, the Cloud, the Internet, an intranet, NAS, RAID, servers, a data center, a server farm, content sites, a social network, a professional network, content streaming sites, Internet radio, a data base, a web site or web page, Big Data, and the like, just to name a few. Essentially, backend service450may represent an entire world of data that is available for access using electronic means such as wireless and/or wired communications networks and their equivalents.

Each media device100i-100vmay include systems for detecting presence and/or proximity as described above. Those systems may collectively create a proximity detection range for each media device100i-100vdenoted as197i-197vand may generally represent a maximum range at which a media device (100i-100v) may detect presence and/or proximity using its respective systems. Proximity detection ranges197i-197vmay not be the same for each media device and the ranges may overlap for some or all of the media devices100i-100vin ecosystem400. For purposes of explanation, proximity detection ranges197i-197vmay be visualized as an approximate radius of detection RDfrom some reference point P on each media device, where if a user, object, or RF signature is within RD, then that media device will detect presence and/or proximity using its respective systems. The systems for detecting proximity may each have different ranges and approximate radius of detection RDmay represent a radius of detection for the system that has the greatest detection range. For example, the RF system107may have a greater detection range than the proximity detection system113or the A/V system109. Therefore, a user403carrying a wireless user device413that is emitting RF signals (e.g.,411) may be detected earlier and at a greater distance from a media device by RF system107than detection of the user403's body by proximity detection islands (I1-I4) in PROX system113, for example.

InFIG. 5, a block diagram500depicts one example of an ecosystem of wireless media devices operative as bridge between wireless user device and a backend service. Dashed lines598and599symbolically demarcate different universes of devices that may be part of a system that interacts with an ecosystem of the wireless media devices. Above dashed line598there may be a universe510of wireless user devices520-526and/or users503-503nwho may or may not be associated with one or more of the wireless user device. In some examples, universe510may not include any (i.e., zero) users. Universe510may include a broad variety of wireless user devices and is not limited to those depicted inFIG. 5and there may be more or fewer wireless user devices than depicted. In some examples, universe510may not include any (i.e., zero) wireless user devices. Some of the wireless user devices may be associated with one another (e.g., via BT pairing, NFC, etc.), for example, data capable band520may be associated with smart phone522(e.g., via BT pairing or other protocol). Each of the wireless user devices may be in wireless communications511with other wirelessly enabled devices in block diagram500.

Below dashed line599a backend service550represents a universe of resources available to the universe510of wireless user devices520-526and/or users503-503nand to the wireless media devices100i-100n. Essentially all of the world's data that may be accessed electronically (e.g., wired, wirelessly, or both) may be embodied by backend service550. Access includes but is not limited to free access, un-restricted access, un-limited access, paid access, restricted access, access by permission, access by account, limited access, and access by login (e.g., user-name/email address and password).

Backend service may electronically communicate with the wireless media devices100i-100nand/or universe510of wireless user devices520-526using a variety of means including but not limited to wireless communications551,581, and591, wired communications553(e.g., using a router560or the like). Wireless resources such as a WiFi router590or broadband/cellular580may be used by or be components of backend service550.

Information and/or components of backend service550may include but are not limited to: Cloud565; Internet563, intranet564; one or more databases556; one or more data storage systems557; RAID562; NAS558(e.g., HDD or SSD); one or more data centers569; Content554; Data555; Big Data561; WWW570(e.g., Web page or Web site, etc.); Providers567; Media559; CFG's125(e.g., for wireless media devices); APP's225(e.g., for wireless user devices); Routers/Switches560; Wireless networks590; and Broadband/Cellular networks580.

Cloud554may comprise any information, service, site, storage, data, hardware, software, or instrumentality available for access in Cloud554. Internet563may comprise any location and its associated content that may be accessed on the Internet563. In some examples, Cloud565and Internet563may be interchangeable or may overlap in terms of what may be accessed from either one. The intranet563may comprise any location and its associated content that may be accessed over an intranet, such as one located behind a firewall or other security screen for the intended purposes of its operator. Content554broadly includes any content regardless of form, file type, data type, or structure that may be accessed from backend service550for use by wireless media devices and/or wireless user devices. Media559broadly includes any media that may be consumed, operated on, displayed, played back, viewed, read, heard, rendered, manipulated, processed, or otherwise of use to wireless media devices and/or wireless user devices. Media559and Content554may not be mutually exclusive in some examples and the definition of what comprises Media559and Content554may overlap or be duplicative. Providers567broadly includes any service, web site, web page, social or professional network, content provider, streaming media service, Internet radio, Blog, Business, e-Business, retailer, wholesaler, SMS, email, or other entity on the Internet563and/or Cloud565that may be accessed by wireless media devices and/or wireless user devices. Database DB556broadly may be any type or form of database, regardless of content that may be accessed by wireless media devices and/or wireless user devices. Data555may broadly be any data that may be accessed by wireless media devices and/or wireless user devices, including but not limited to playlists, shared playlists, family playlists, group playlists, health and/or wellness data, contacts data, calendar data, just to name a few. Big data561broadly includes any collection of large data sets that may be accessed and optionally processed or operated on by wireless media devices and/or wireless user devices or compute engine in backend service550. CFG125may include but is not limited to any configuration file used internally by one or more of the wireless media devices as described herein for various purposes including but not limited to communication and control with one or more of the wireless user devices. APP225may include but is not limited to any application file used internally by one or more of the wireless user devices for various purposes including but not limited to communication and control with one or more of the wireless media devices.

Referring back toFIG. 5, bridging the universes between users and wireless user devices and backend service550are one or more wireless media devices100i-100n. Users503-503n, if any, and one or more wireless user devices520-526, if any, when within proximity (RF or other) range RDof the one or more wireless media devices100i-100nmay access resources available in backend service550using systems included in one or more of the media devices100i-100n. For example, if user503of user device524is viewing a newspaper article from Media559and user503and/or user device524enter proximity of wireless media device100iii, then wireless media device100iiimay establish a wireless communications link between100iiiand524and the content comprising the newspaper article and any link information (e.g., a URL for the source of the newspaper article and/or login data) may be wirelessly communicated between100iiiand524such that handling of the content is now transferred from524to100iii. Wireless media device100iii, or another wireless media device, may establish a communications link with backend service550to access media559and the newspaper article may be presented on display180of media device100iiior on some other display connected with media device100iiior on one of the other media devices. For example, wireless media device100imay include an HDMI output that is connected with a HD display (e.g., a HDTV or HD monitor) and image data comprising the newspaper article may be wirelessly transmitted126from media device100iiito media device100iand outputted by media device100ion its HDMI output for display on the HD display.

Here a data payload and/or wireless bandwidth payload (e.g., 3G or 4G Cellular) associated with handling the content of the newspaper article on wireless user device524is offloaded to one of the wireless media devices100i-100n(e.g., to media device100iii) and those media devices may use any one of their respective RF transceivers (e.g., WiFi130) to wirelessly access resources on the backend service550(e.g., Media559). In cases where the content comprises larger data payloads and wireless bandwidth payloads, such as in streaming video, movies or high resolution audio, having the wireless media device(s) offload one or both of those payloads from a user device may be of great advantage to a user. As one example, if user device522is viewing an audio/video stream of a feature length movie and is using up some of the allotted monthly data usage for device522, then when device522comes into proximity of media device100n, media device100nmay wirelessly link with device522and take over the data and bandwidth payload from device522by using its available wireless resources and wireless connections, such as WiFi or broadband, for example. Further, as media device100nhandles the transferred content, the user device522is freed up to perform other tasks for its user, such as phone calls, texting, browsing, etc.

InFIG. 5, the content, data, media, files, playlists, preferences, favorites, photos, videos, images, and other forms of information follow the user devices of a user into and out of the ecosystem of wireless media devices100i-100n. When a user device transitions (e.g., is carried or moved) from proximity of a media device, whatever services the media device was performing may be transferred back to the user device. After transferring content, control, etc. back to the wireless user device, that device may then make whatever communication links, if any, as necessary to continue handling the content, control, etc. going forward. For example, if a playlist is resident on the user device, then when control of the content is transferred back to the user device the track and time index information for the track being played back on the media device may be wirelessly transmitted to the user device so that the user device may resume playback at the same time index for the same track, thereby making the content transfer as seamless as possible with minimum time delay between the transfer and playback resuming on the user device. As another example, the content may reside on the user device and at the time the media device took control of handling the content, the media device may wirelessly accessed an external version of the content from backend service550, thereby preventing the user device from having to wirelessly transmit the content to the media device. When the media device hands control of the content back to the user device, the user device may access its resident version of the content and continue playback from that resident version.

The wireless media devices as described herein may have a variety of different shapes, sizes, capabilities, functionalities, aesthetic elements, form factors, utility, just to name a few. InFIG. 6an ecosystem600includes a plurality of different wireless media devices denoted as100a-100m. There may be more of fewer wireless media devices than depicted inFIG. 6as denoted by100N. The wireless media devices may vary in configuration such that wireless media device100ais designed to be pocketable, that is, it is sized to be small, transportable, and to fit in typical locations in a user603's clothing, such as a pocket of a jacket, shirt, sweat top, vest, sweater, back pack, laptop case, shorts, or pair of pants, for example. A pocketable media device100amay be easily carried in one hand of user603.

In other examples, media device100ais designed to be ultra-portable and may be configured to be worn or otherwise connected with a body of user603, such as a headset, head band, data capable strap band, wristband, wristwatch, digital watch, or wireless activity monitoring and reporting device. Although the ultra-portable size may allow media device100ato fit in a pocket or the like due to its smaller size, the ultra-portable form factor for100ais configured to facilitate wearing or otherwise coupling or connecting the media device100awith user's603body. For example, an ultra-portable wireless media device may be configured and may be sized to be head worn (e.g., as an earpiece).

Wireless media device100bis designed to be portable by user603such that it is sized to be easily carried and transported from place-to-place by user603, but its size is not intended to make it easily fit in a pocket or the like or to be worn by user603(e.g., it's not ultra-portable), but100bmay be stowed in an armrest or glove compartment of an automobile, carried in a back pack or purse, set on a surface such as a picnic bench, desk, or table, etc. Therefore, wireless media device100bis larger than pocketable or ultra-portable wireless media device100a.

Wireless media devices100c-100lare designed to a personal size that may vary based on market needs, functionally, features, speaker sizes, enclosure volume need for the speakers, and end use scenarios, for example. Typically, media devices100c-100lare larger than media device100band much larger than media device100a. Wireless media devices100c-100lare usually for use in less mobile scenarios such as in a room of a house, business, or some other interior structure. Example locations include but are not limited to an office, place of business, lobby, break room, cafeteria, lunch room, study, library, lounge, conference room, workout room, gym, studio, meeting room, family room, loft, balcony, landing, hotel/motel room, bedroom, bathroom, locker room, patio, deck, home theater, music room, recording studio, terrace, kitchen, breakfast nook, great room, guest room, sound room, just to name a few. Although dimensions and weight may be application dependent, an example range of approximate sizes for media devices100c-100linclude but are not limited to: Length from about 130 mm to about 300 mm; Width from about 30 mm to about 130 mm; and Height from about 40 mm to about 150 mm. An example range of approximate weight includes but is not limited to: from about 0.3 kg to about 4 kg. Some personal wireless media devices may be even larger in size and weigh more than the examples above. As one example, wireless media device100mmay be configured as a subwoofer (e.g., for use in a surround sound or other audio system) and may have an enclosure (e.g., chassis199) configured to support the low frequency driver size (e.g., SPK160) and enclosure volume to produce the desired low frequency range of sounds typical of a subwoofer, such as from about 20 Hz to about 100 Hz. Personal sized wireless media devices may be configured to be placed on a surface such as a table, desk, counter, audio rack, speaker stand, pedestal, tripod, bench, or other similar structure. Furthermore, personal sized wireless media devices may be configured to be mounted to a structure such as a wall, beam, pillar, post, ceiling, or the like.

InFIG. 6, the ecosystem600may comprise a variety of different wireless media devices that may be positioned in different physical locations. Dashed line610represents movement by user603and/or one or more user devices612and614between different zones621-661in which different types and numbers of wireless media devices are positioned. Dashed lines620,630,640,650, and660are provided to illustrate a demarcation between the different zones621-661. Zones621-661may represent different rooms or spaces in a structure such as a house, apartment, office, business, dorm, etc. Some of the zones621-661may be separated by open spaces, a structure such as a wall or the like, and the zones621-661need not be physically adjacent to one another. Wireless media devices100a-100mmay be in wireless communications126with one another, with wireless user devices612and614(e.g.,613and615), and with a backend resource690. A WiFi router or other wireless node may be used to allow the wireless media devices100a-100mto wirelessly communicate with one another over distances that may vary based on RF capabilities, RF signal strength, structures that may interfere with RF, just to name a few.

Wireless media devices100a-100mmay be in wireless communications126with one another using one or more of their respective internal RF systems107, including AH140. In some examples, one or more of the wireless media devices100a-100mmay communicate with other of the wireless media devices100a-100musing an external wireless network (e.g., a WiFi router, WiMAX network, cellular network, or broadband network). For example, media device110bmay wirelessly communicate126with media devices100h-100musing their respective WiFi130transceivers with a WiFi network serving as a communications link between the two media devices. As another example, media device100amay wirelessly communicate with media device100eby using its BT140to communicate with media device100band media device100buses its AH140to communicate with AH140of media device100esuch that any information exchange between media devices100aand100eare passed through media device100bas an intermediary or hub.

While in zone621, user603may be accessing content from one or both wireless user devices614and/or612using media device100a, which for purposes of explanation will be assumed to be a BT enabled headset worn on an ear of user603. Further, user603is listening to content that comprises music streaming on device614using a BT link between device614and media device100a. Lastly, assume that media device100aonly includes a BT transceiver140in its RF system. As user603moves from zone621to zone631, media device100bdetects one or more of three RF signatures (126,613, and615) and/or presence/proximity of user603. Media device100bestablishes a wireless link with user device614, determines that100ais handling content from614, and takes over the content handling for device614. Here, media devices100aand/or100bmay be configured (e.g., via CFG125) to recognize one each other, determine which device is to dominate content handling in a given scenario, and to take action to switch content handling to the dominate media device. In this example, media device100bis of larger size and has larger speakers that are able to playback the music being streamed at a higher fidelity and higher volume. User603may have pre-set a preference (e.g., via APP225on device614and/or CFG125on media device100band/or100a) that controls which media device in ecosystem600is best suited to handling content from the user's wireless devices. Media devices100band100amay or may not establish a BT wireless link between each other to facilitate switching content handling from media device100ato media device100b. Zone621may have been a car the user603was in prior to moving610to zone631in a room of the user603's house, for example. Furthermore, while in zone631, audio content on phone calls on user device614will be handled by media device100b, and optionally by media device100aif the user603take some action (e.g., pushes a button or presses an icon) to make the conversation private.

As another example, user603leaves device614on a table in zone631and moves610to zone641, which is in another room in user603's house. The music content is still being handled by media device100b; however, media device100bno longer detects presence/proximity of user603in zone631, but media devices100cand100ddetect presence/proximity of user603in zone641. Media device100cand/or100dwirelessly communicate with media device100aand negotiate transferring content handling from media device100bto media devices100cand100d. Here, ecosystem600provides two larger media devices100cand100dto playback the music content. User603may have pre-set a preference to hear playback in stereo (e.g., using two media devices instead of one) or with a larger sound field that may be produced with two media devices that have larger speakers. User603's media followed the user603even though the user's wireless device614remained in zone631. In an alternate example, the user603moves from zone631to zone641with the user device614in tow. The result may be the same, with media devices100cand/or100ddetecting presence/proximity of user603and/or device614and transferring content handling from media device100b.

In another example scenario, wireless user device614is playing back a multi-channel audio track. Initially, user603is in zone631and media device100bwirelessly communicates with device614to transfer content handling to media device100bas described above. Subsequently, user603moves610from: zone631to zone641; zone641to zone651; and zone651to zone661. As the user603moves610between zones, media devices in those zones detect the user device614, the user603, or both while in their respective zones and take over content handling. While in zone641, both media devices100cand100dplayback the multi-channel content using their respective A/V systems109to provide at least stereo playback (e.g., left channel and right channel) or synthesized multi-channel playback (e.g., using algorithms and/or processors to synthesize more than two audio channels). For example, a center channel may be synthesized from the multi-channel content. While in zone651all three media devices100e-100gprovide at least three channels (e.g., left, right, and center channel) or synthesized multi-channel playback (e.g., left rear and right rear channels are synthesized). While in zone661all five media devices100h-100lprovide at least six channels of playback (e.g., 5.1 surround sound) and may synthesize additional channels (e.g., left height and right height channels). Therefore, as the user603and/or user devices (614,612) move between various areas of ecosystem600(e.g., zones621-661) the user's media content follows the user603and/or the user's wireless user devices.

In the above scenario, the user device614may remain stationary in one of the zones621-661and movement of the user603between the zones causes the content to follow the user603(e.g., from zone641to zone661) as the user603is detected by the media devices in a particular zone. The user experience of the content may be upgraded or enhanced in some zones based on the capabilities of media devices in those zones. For example, the user603experiences 3 channel playback in zone651and that experience is upgraded or improved to a 5.1 experience in zone661due to two additional media devices100kand100land subwoofer media device100m. In the above scenario the user's movement between the zones need not be in the order depicted and the zones may be traversed by the user603in a different order. The zones depicted are not necessarily arranged as shown and the user603may move from one zone to any zone without passing through other zones, such as moving from zone621directly to zone661without passing through zones631,641, and651, for example.

Content, data, or other information for user devices612and614and media devices100a-100lmay be resident in those devices, may be distributed among a plurality of those devices and may reside in whole or in part in backend service690as was described above in reference toFIG. 5. In some examples, duplicate copies of content, data, or other information may reside in one or more of backend service690, media devices100a-100l, or user devices612and614. Content being handled by one or more media devices need not be resident (e.g., in DS103) in the media device(s) handling the content. In some examples, a full or partial copy of content, data, or other information may be copied to one or more media devices assigned to handle the content. For example, a wireless user device upon negotiating with one or more media devices that will take over handling of content from the wireless user device may transfer a full or partial copy of the content, data, or other information to one or more of the media devices. The content, data, or other information transferred may include a playlist, the content (e.g., MP3 files), or both. A display (e.g., touch screen), controls, or other instrumentalities on the media devices and/or wireless user device may be used to control content handling, playback, and other functions of media devices that are currently handling content.

Wireless user device612may include a RF system that only allows wireless communication using a single protocol, such as BT for example. One or more of media devices100a-100lmay wirelessly link with device612upon detecting it and uses its respective RF system to wirelessly transmit data to/from device612or to interface device with backend service690. As one example, alarms and data in device612may be handled by media device100bwhile device612is in zone631; however, the handling of those alarms and data may be transferred to other media devices in other zones as the user603and/or device612moves into and out of those other zones. As another example, as device612move from zone631to zone651, one or more of media devise100e-100gmay establish a wireless link with612and take over handling of content (e.g., alarms, data, etc.). Data to be downloaded to device612from a source such as backend service690or other (e.g., NAS) and may be wirelessly transmitted from that source (e.g., using WiFi) to one of the media devices linked to device612and then the media device may use the link to wirelessly transmit (e.g., using BT) the data to device612.

The examples depicted inFIG. 6are non-limiting and ecosystem600may include more or fewer users and/or objects, may include more or fewer wireless user devices and different types of wireless user devices. Content handling and functionality of the wireless media devices100a-100lin ecosystem600may dynamically change and be re-tasked based on changes in the ecosystem. Examples include but are not limited to: media devices being added to or removed from the ecosystem600; media devices moving into and/or out of the zones such that the number of media devices in a zone goes up or down; adding a new media device (e.g., out-of-the-box) to the ecosystem600for the very first time; changes in configuration files (e.g., CFG125) for one or more of the media devices in ecosystem600; an increase or decrease in the number of users and/or objects in ecosystem600; an increase or decrease in the number of wireless user devices in ecosystem600; introduction of a wireless media device into ecosystem600for the very first time; and a change in an application (e.g., APP225) on one or more wireless user devices that have already been recognized (e.g., in CFG125) by one or more media devices in ecosystem600. One or more of the wireless media devices100a-100ldepicted inFIG. 6may be configured to operate as a satellite of one or more of other wireless media devices. For example, functions to be performed in connection with handling content may be distributed among a plurality of the wireless media devices100a-100l.

A satellite media device need not be in the same zone as the media device(s) it is acting as a satellite for. For example, media device100iin zone661may handle stereo audio content and may use the A/V systems of media devices100hand100jto implement the left and right channels of stereo playback. As another example, media device100ein zone651may handle stereo audio content and may use the A/V systems of media devices100cand100din zone641to implement the left and right channels of stereo playback (e.g., user603has moved610from zone651to zone641and the music content follows user603).

The systems, ecosystems, wireless media devices, apparatus and methods of the foregoing examples may be embodied and/or implemented at least in part as a machine configured to receive a non-transitory computer-readable medium storing computer-readable instructions. The instructions may be executed by computer-executable components preferably integrated with the application, server, network, website, web browser, hardware/firmware/software elements of a user computer or electronic device, or any suitable combination thereof. Other systems and methods of the embodiment may be embodied and/or implemented at least in part as a machine configured to receive a non-transitory computer-readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components preferably integrated by computer-executable components preferably integrated with apparatuses and networks of the type described above. The non-transitory computer-readable medium may be stored on any suitable computer readable media such as RAMs, ROMs, Flash memory, EEPROMs, optical devices (CD, DVD or Blu-Ray), hard drives (HD), solid state drives (SSD), floppy drives, or any suitable device. The computer-executable component may preferably be a processor but any suitable dedicated hardware device may (alternatively or additionally) execute the instructions.

As a person skilled in the art will recognize from the previous detailed description and from the drawing FIGS. and claims set forth below, modifications and changes may be made to the embodiments of the present application without departing from the scope of this present application as defined in the following claims.

Although the foregoing examples have been described in some detail for purposes of clarity of understanding, the above-described inventive techniques are not limited to the details provided. There are many alternative ways of implementing the above-described techniques or the present application. The disclosed examples are illustrative and not restrictive.