Smart battery wear leveling for audio devices

BACKGROUND

0001Mobile and wireless technologies have seen explosive growth over the past several years. This growth has been fueled by better communications, hardware, and more reliable protocols. Wireless service providers are now able to offer their customers an ever-expanding array of features and services, and provide users with unprecedented levels of access to information, resources, and communications. To keep pace with these enhancements, mobile electronic devices (e.g., cellular phones, watches, headphones, remote controls, etc.) have become smaller, more powerful and more feature-rich than ever. Many of these devices now have impressive processing capabilities, large memories, and radios/circuitry for wirelessly sending and receiving information.

0002Wireless communication technologies have also improved over the past several years. Wireless local area networks are now replacing wired networks in many homes and offices. Short-range wireless technologies, such as Bluetooth® and WiFi, enable high speed communications between mobile electronic devices (e.g., cellular phones, watches, headphones, remote controls, etc.) that are within a relatively short distance of one another (e.g., 100 meters or less).

SUMMARY

0003The various embodiments include systems, methods, and devices configured to balance power consumption among wireless devices operating in a master-slave configuration by exchanging master and slave roles in a manner that is less noticeable to a user.

0004Various embodiments include methods of balancing power consumption among wireless nodes by establishing a first communication link between a first wireless node and a second wireless node, establishing a second communication link between the first wireless node and a source wireless device, receiving data transmissions from the source wireless device on the first wireless node over the second communication link, relaying at least a portion of the data transmissions from the first wireless node to the second wireless node over the first communication link, determining whether to exchange master-slave roles between the first wireless node and the second wireless node, exchanging master-slave roles between the first wireless node and the second wireless node in response to determining that it is time to exchange master-slave roles, and receiving the data transmissions from the source wireless device on the second wireless node over the second communication link. In an embodiment, the method may include monitoring the data transmissions to identify periods of low data transmission or pauses, and exchanging the master-slave roles between the first wireless node and the second wireless node during an identified period of low data transmission or pauses. In a further embodiment, monitoring for a period of low data transmission may include monitoring for a break between songs in a stream of music.

0005In an embodiment, the method may include monitoring battery states of the first and second wireless nodes, in which determining whether to exchange master-slave roles between the first wireless node and the second wireless node may include determining whether to exchange master-slave roles based on a battery state of one or both of the first and second wireless nodes. In a further embodiment, exchanging master-slave roles between the first wireless node and the second wireless node may include terminating the first communication link between the first wireless node and the second wireless node, terminating the second communication link between the source wireless device and the first wireless node, and establishing a third communication link between the second wireless node and the source wireless device immediately after terminating the second communication link. In a further embodiment, exchanging master-slave roles between the first wireless node and the second wireless node may include swapping addresses in link key fields associated with the first and second wireless nodes. In a further embodiment, the first wireless node, second wireless node, and source wireless device may be nodes in a piconet.

0006In a further embodiment, exchanging master-slave roles between the first wireless node and the second wireless node in response to determining that it is time to exchange master-slave roles may include controlling a media source on the source wireless device so that master-slave roles are exchanged without disruption of data transmissions from the source wireless device. In an embodiment, the method may include determining whether an audio signal is currently a monaural sound directed to a particular ear, and directing the audio signal to the one of the first wireless node and second wireless node that is positioned in the particular ear after exchanging master-slave roles between the first wireless node and the second wireless node. In an embodiment, the method may include determining whether the source wireless device is currently able to receive a pause request, and transmitting the pause request to the source wireless device in response to determining that master-slave roles should be exchanged and determining that the source wireless device is currently able to receive the pause request, in which exchanging master-slave roles between the first wireless node and the second wireless node is accomplished in response to the source wireless device pausing data transmissions.

0007Further embodiments include a computing device having a transceiver, a memory, and a processor coupled to the transceiver and the memory, in which the processor is configured with processor-executable instructions to perform operations including establishing a first communication link with a second computing device, establishing a second communication link with a source wireless device, receiving data transmissions from the source wireless device over the second communication link, relaying at least a portion of the data transmissions to the second computing device over the first communication link, determining whether to exchange master-slave roles with the second computing device, and exchanging master-slave roles with the second computing device in response to determining that it is time to exchange master-slave roles. In further embodiments, the computing device processor may be configured with processor-executable instructions to perform other operations of the embodiment methods discussed above.

0008Further embodiments include a system that may include a first wireless device including a first transceiver, a first memory and a first processor coupled to the first transceiver and the first memory, a second wireless device including a second transceiver, a second memory and a second processor coupled to the second transceiver and the second memory, and a source wireless device including a source transceiver, a source memory and a source processor coupled to the source transceiver and the source memory in which the in which the first, second and/or source processors are configured with processor-executable instructions to perform operations corresponding to the method or processor operations discussed above. In further embodiments, the processors of the system devices may be configured with processor-executable instructions to perform other operations of the embodiment methods discussed above.

0009Further embodiments include a system having various means for performing functions corresponding to the method or processor operations discussed above.

0010Further embodiments include a computing device having various means for performing functions corresponding to the method or processor operations discussed above.

0011Further embodiments include a non-transitory processor-readable storage medium having stored thereon processor-executable instructions configured to cause a processor of a wireless computing device to perform various operations of the embodiment methods discussed above.

BRIEF DESCRIPTION OF THE DRAWINGS

0012The accompanying drawings, which are incorporated herein and constitute part of this specification, illustrate exemplary embodiments of the invention, and together with the general description given above and the detailed description given below, serve to explain the features of the invention. <ul id="ul0001" list-style="none"><li><figref idref="f0001">FIG. 1</figref> is a component block diagram illustrating example components and communication links in a composite electronic device suitable for implementing the various embodiments.</li><li><figref idref="f0002">FIG. 2</figref> is a component block diagram illustrating example pairings and components in a configuration suitable for implementing the various embodiments.</li><li><figref idref="f0003 f0004">FIGs. 3A-3B</figref> are process flow diagrams of embodiment methods for dynamically swapping master and slave roles to balance power consumption among wireless nodes.</li><li><figref idref="f0005 f0006 f0007">FIGs. 4A-4C</figref> are process flow diagrams of embodiment methods for dynamically swapping master and slave roles so that the role changes have reduced impact on the user experience.</li><li><figref idref="f0008">FIG. 5</figref> is an illustration of a wireless wrist watch-type computing device suitable for use with the various embodiments.</li><li><figref idref="f0009">FIG. 6</figref> is an illustration of a wireless earpiece suitable for use with the various embodiments.</li><li><figref idref="f0010">FIG. 7</figref> is an illustration of an example mobile device suitable for use with the various embodiments.</li><li><figref idref="f0011">FIG. 8</figref> is an illustration of an example laptop computer suitable for use with the various embodiments.</li></ul>

DETAILED DESCRIPTION

0013The various embodiments will be described in detail with reference to the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. References made to particular examples and implementations are for illustrative purposes, and are not intended to limit the scope of the invention or the claims.

0014The term "computing device" is used generically herein to refer to any one or all of servers, personal computers, laptop computers, tablet computers, mobile devices, cellular telephones, smartbooks, ultrabooks, palm-top computers, personal data assistants (PDA's), wireless electronic mail receivers, multimedia Internet-enabled cellular telephones, Global Positioning System (GPS) receivers, wireless gaming controllers, and other similar electronic devices that include a programmable processor and circuitry for wirelessly sending or receiving information.

0015The terms "mobile device," "wireless node" and "receiver device" are used interchangeably herein to refer to any one or all of cellular telephones, smartphones, personal or mobile multi-media players, watches, wrist displays, medical devices, headsets, headphones, speakers, microphones, and/or any electronic device that includes circuitry for wirelessly sending and/or receiving information.

0016The term "Bluetooth®-enabled device" is used herein to refer to any electronic device that includes a radio frequency (RF) radio and a processor or circuitry for implementing the Bluetooth® protocol stack/interface. Bluetooth® is an open standard for short-range radio frequency (RF) communications. Details of the Bluetooth® standards, interfaces, and technology are set forth in Bluetooth® Special Interest Group (SIG) Specification of the Bluetooth® System Version 4.0 June 30, 2010, which is herein incorporated by reference in its entirety.

0017As mobile device and wireless technologies continue to improve and grow in popularity, short-range wireless technologies are expected to supplant or replace the need for connecting devices together using cables or wires. As part of this evolution, composite electronic devices made up of multiple independent wireless-enabled devices are beginning to emerge, and it is becoming more common for individual electronic components to require wireless communications with multiple components/devices. Such communications may have a disproportionate impact on the battery life of each constituent component in a composite electronic device, and distributing the energy consumption costs amongst constituent components of a composite electronic device may become an important and challenging design criterion.

0018Any electronic device that includes a radio frequency (RF) radio and/or circuitry implementing a short wave wireless protocol/interface is a wireless-enabled device capable of communicating using short wave wireless technology. Such RF radios and circuitry are now being embedded in small electronic devices (e.g., headphone speakers), allowing these devices to communicate using wireless technology and replacing the need for wires or wire based communications. As a result, composite electronic devices made up of multiple independent wireless-enabled devices (e.g., two headphone speakers and a wrist display) are beginning to emerge for which all communications between the constituent components are achieved using wireless technology (e.g., Bluetooth®, WiFi, etc.). However, such extensive use of RF radios may quickly deplete the component's battery and cause the entire composite electronic device to become unusable. This is particularly problematic for smaller components (e.g., headphone speakers) that have size or weight limits that prevent them from including larger and more powerful batteries.

0019The various embodiments provide wear-leveling methods that enable the wireless communications to be performed so that the battery levels of the devices are depleted at approximately the same rate. Various embodiments intelligently and dynamically swap master/slave roles among two or more wireless receiver devices (e.g., speakers) coupled to a data source device (e.g., phone) to optimize battery life in both devices. The various embodiments provide methods for swapping the master and slave roles so that there is reduced impact on the user experience. The various embodiments may be implemented using Bluetooth®, WiFi, or other similar short wave wireless communication technologies.

0020Swapping master/slave roles typically requires that the communication link between the existing master device (e.g., a first earpiece) and the source device (e.g., media player) be terminated and a new communication link be established between a new master device (e.g., second earpiece) and the source device (e.g., media player). The process of terminating a first link and establishing a second link may take some time (e.g., one or two seconds), during which the audio playback may be interrupted. The various embodiments swap master and slave roles so that there is reduced disruption to the audio/data stream (e.g., during a media break). Various embodiments initiate a master/slave swap at points in the communication stream at which a swap is most likely to have a reduced impact on the user experience, such as during periods of silence in between songs.

0021In various embodiments, the wear-leveling operations may be performed such that the user does not perceive any changes in the operations of the devices. For example, if a composite device is configured such that monaural sound is produced by a first wireless earpiece but not by a second wireless earpiece, as may be the case when a telephone call is underway and the user prefers to receive audio from phone calls in a particular ear, the master and slave roles of outputting the monaural audio of the first and second earpieces may be swapped so that the monaural sound continues to be produced by the first wireless earpiece (e.g., the user's preferred ear for phone calls), irrespective of the changes in master/slave roles. This may be achieved, for example, by the new master (e.g., second earpiece) streaming the monaural audio to the new slave (e.g., first earpiece). This may also be achieved by, for example, by delaying or suspending the role swap operations until it is determined that the information transmitted from the source device (e.g., media player) is such that the master and slave roles may be swapped without impacting the user experience. For example, the master/slave swap may be delayed until a phone call ends.

0022In an embodiment, the master and slave roles may be swapped in response to determining that information transmitted from the source device (e.g., media player) is to be received on a specific device having a specific role. For example, if the information transmitted from the source device (e.g., media player) requires that a monaural sound be produced by the first wireless earpiece acting in a master role, the system may be configured to place the first wireless earpiece into the master role upon detecting the presence of such information. In this manner, the wear-leveling operations may be performed so that the user does not perceive any changes to device operations.

0023In another embodiment, the master device may be configured to determine when the audio stream from source device is controllable, such as a media player playing stored music versus receiving a broadcast stream, and when that is the case, issue a command or request to the source device that enables the audio stream to be temporarily halted, such as by executing a pause, to enable the master/slave swap to occur without losing any of the media. This option may be particularly useful when the audio is primarily speech (e.g., a podcast or audio book).

0024While the various embodiments are particularly useful in mobile devices (e.g., cellular telephones, headsets, watches, wrist displays, etc.), the embodiments are generally useful in any computing device that sends or receives information over a short-range wireless communication link.

0025Various embodiments are described herein using Bluetooth® and Bluetooth®-related terminology as a convenient example of a communications technology for wirelessly connecting electronic devices located within a relatively short distance of one another (e.g., 100 meters). However, examples referring to Bluetooth®, and other references to the Bluetooth® herein, are for illustration purposes only and are not intended to limit the descriptions or the claims to that particular standard. Therefore, the scope of the claims should not be construed as requiring Bluetooth® technology unless specifically recited as such in the claims.

0026Bluetooth® technology provides a secure way to connect and exchange information between electronic devices (e.g., headphones, cellular phones, watches, laptops, remote controls, etc.). Because many of the services offered over Bluetooth® can expose private data and/or allow the connecting party to control the connected device, Bluetooth® requires that devices first establish a "trust relationship" before they are allowed to connect to one another. This trust relationship may be established using a process called "pairing" in which a bond formed between the two devices. This bond enables the devices to communicate with each other in the future without further authentication.

0027The pairing process may be triggered by a specific request to create a bond (e.g., user explicitly requests to "add a Bluetooth® device"), or may be triggered automatically (e.g., when connecting to a service). For example, a Bluetooth® device may automatically initiate the performance of the pairing operations each time the device is powered or moved within a certain distance of another Bluetooth® device. Pairing information relating to current and previously established pairings may be stored in a paired device list (PDL) in the memory of the Bluetooth® device. This pairing information may include a name field, an address field, a link key field, and other similar fields (e.g., profile type, etc.) useful for authenticating the device and/or establishing a Bluetooth® communication link.

0028Bluetooth® communications may require establishing wireless personal area networks (also referred to as "ad hoc" or "peer-to-peer" networks). These ad hoc networks are commonly called "piconets." Each device may belong to multiple piconets. Multiple interconnected piconets may be called scatternets. A scatternet may be formed when a member of a first piconet elects to participate in a second piconet.

0029A Bluetooth® profile describes general behaviors through which Bluetooth® -enabled devices communicate with other Bluetooth® devices. For example, the hands free profile (HFP) describes how a Bluetooth® device (e.g., phone) may place and receive calls for another Bluetooth® device, and the Advanced Audio Distribution Profile (A2DP) describes how stereo-quality audio may be streamed from a first Bluetooth® device (e.g., phone) to another Bluetooth® device (e.g., headphones). Likewise, the Audio/Video Remote Control Profile (AVRCP) provides an interface that enables a single remote control (or other device) to control all of the devices (e.g., televisions, stereos, etc.) to which a user has access.

0030Bluetooth® devices may connect to two devices at a time using different Bluetooth profiles. For example, a Bluetooth® receiver device (e.g., headphones) may connect to a first Bluetooth® source devices (e.g., a phone and a media player) at the same time using the A2DP and HFP profiles. This allows the user to listen to music streamed from the first source device (e.g., media player) using A2DP while allowing the second source device to automatically interrupt the play of music to stream speech using HFP (e.g., an incoming telephone call), and then automatically return to streaming music from the media player using A2DP (e.g., upon completion of the call).

0031Bluetooth® implements a master-slave structure in which a single master Bluetooth® device (referred to herein simply as the "master device") may communicate with up to seven active slave Bluetooth® devices (herein simply "slave devices") in a piconet. A master device may only communicate with the slave devices that are within the same piconet as the master. Slave devices may only communicate with the master device, and thus, communications between two or more slave devices are typically facilitated by the master device.

0032Master and slave devices may have asymmetrical roles. For example, within each piconet, data may only be transferred over a single connection at a time, and the connection may only be established between the master device and one slave device. Therefore, the master may be responsible for identifying and selecting slave devices with which to communicate, which may require rapidly switching the connection from one slave device to another in a round-robin fashion to avoid starving or neglecting slave devices requesting to send or receive information. In addition, since communications between two slave devices must be facilitated by the master device, the master device may also be responsible for receiving information from a sending slave device, identifying a target slave device, and retransmitting the information to the identified target device. Slave devices, on the other hand, may only be responsible for monitoring or polling a port to receive information from the master device. These asymmetrical roles may result in the master device performing operations that consume a different amount of energy than the operations performed by the slave devices, causing one device to deplete its battery faster than the others.

0033<figref idref="f0001">FIG. 1</figref> is a component block diagram illustrating an example composite electronic device 100 suitable for use with the various embodiments. The composite electronic device 100 may include a first earpiece 102, a second earpiece 104, and a wrist display 106, each of which may be independently Bluetooth®-enabled. Each component 102, 104, 106 may be individually paired to each of the other components via wireless communication links/pairings 116. These links/pairings 116 may be established at the factory so that the user perceives the composite electronic device 100 as a single component. In some embodiments, the first earpiece 102 may be a left earpiece, and the second earpiece 104 may be a right earpiece. In some embodiments, the first earpiece 102 may be a right earpiece, and the second earpiece 104 may be a left earpiece.

0034Each earpiece 102, 104 may include a speaker for generating sounds based on audio signals received from the wrist display 106, another earpiece 104, 102, or a third-party device (e.g., phone). The wrist display 106 may include a media player that transmits wireless audio and/or control streams to the earpieces 102, 104. In an embodiment, the wrist display 106 may be configured to transmit an audio data stream and a control stream to each of the earpieces 102, 104. In these embodiments, the control stream may be transmitted via a separate out-of-band channel.

0035In some embodiments, the wrist display 106 may transmit the audio and/or control streams to the first earpiece 102, which may receive the wireless transmission and transmit a stream to the second earpiece 104. In these embodiments, the first earpiece 102, by operating as the master device, may both send and receive information in such streams.

0036In an embodiment, two or more of the components 102, 104, 106 may be coupled together in an advanced audio distribution profile (A2DP) configuration. In an embodiment, two or more components 102, 104, 106 may be coupled together using a proprietary protocol that allows for communications in addition to, or independent of, the Bluetooth® communications.

0037<figref idref="f0002">FIG. 2</figref> is a block diagram illustrating example wireless links and components in a configuration 200 suitable for implementing the various embodiments. In the illustrated example of <figref idref="f0002">FIG. 2</figref>, a composite electronic device 202 may include multiple independently Bluetooth®-enabled components that may include a wrist display 210, a first earpiece 206 and a second earpiece 208. The composite device 202 may communicate with a Bluetooth®-enabled phone 204 via a wireless communication link 212. The phone 204 may be paired to some or all of the wrist display 210, the first earpiece 206, and the second earpiece 208. If desired, the wrist display 210 may facilitate pairing the phone 204 with one or both of the earpieces 206, 208 by negotiating a pairing with the phone 204 on behalf of the earpieces 206, 208, for example, as disclosed in Applicant's co-pending application, entitled "SMART PAIRING USING BLUETOOTH® TECHNOLOGY" (Attorney Docket No. 113422), filed concurrently with this application and incorporated by reference herein in its entirety. In some embodiments, the first earpiece 206 may be a left earpiece, and the second earpiece 208 may be a right earpiece. In some embodiments, the first earpiece 206 may be a right earpiece, and the second earpiece 208 may be a left earpiece.

0038Two or more components (e.g., the earpieces 206, 208) may be coupled together in an advanced audio distribution profile (AADP). In some embodiments, the phone 204 or wrist display 210 may configured to transmit the audio and/or control streams to the first earpiece 206, which may receive the wireless transmission and transmit a second stream to the second earpiece 208. In such embodiments, the first earpiece 206, by operating as the master device, may both send and receive information in such streams, which may cause the first earpiece 206 to deplete its battery faster than the slave devices (e.g., second earpiece 208).

0039The various embodiments may provide wear-leveling methods that enable the Bluetooth® communications to be performed so that the battery levels of the devices are depleted at approximately the same rate. For example, the earpieces 206, 208 may cooperate to dynamically swap master and slave roles in a manner that balances the load on each earpiece's battery. The earpieces 206, 208 may swap the master/slave roles based on, for example, the amount of battery life remaining on each earpiece (e.g., the earpiece having the most charge operates as the master) and/or other factors.

0040Swapping master/slave roles may include terminating the communication link between a first master device (e.g., first earpiece 206) and a source device (e.g., phone 204 or wrist display 210) and establishing a new communication link between a new master device (e.g., second earpiece 208) and the source device. The process of terminating a first link and establishing a second link may take some time (e.g., one or two seconds), during which the audio playback in the earpieces may be interrupted. The various embodiments may swap master and slave roles at times or points in the communication stream at which one of the device processors determines that there will be less disruption to data being sent in the audio/data stream (e.g., during a media break), and thus reduced impact on the user experience.

0041In an embodiment, the MAC address in the link keys associated with the earpieces 206, 208 may be swapped when swapping master/slave roles so that the source device (e.g., phone 204 or wrist display 210) is unaware of the role change. In another embodiment, the MAC address in the link key associated with the new master earpiece may be changed to the MAC address in the link key that was associated with the previous master earpiece (i.e., the new slave earpiece), and the MAC address in the link key associated with the new slave earpiece may be changed to any desired MAC address. These embodiments may allow the earpiece master/slave roles to be swapped without terminating the link to the source device.

0042Various embodiments may identify one or more points in the communication stream in which a role-swap is likely to have reduced impact on the user experience, and perform the role-swap operations at the identified points. These points may be identified based on an in-band audio signal, silence detection algorithms, media breaks, and/or an out-band communication link signal. For example, data being communicated to the earpiece 206 and/or the earpiece 208 from a source device (e.g., the phone 204 or wrist display 210) may be monitored by a processor in the earpiece currently performing the master role to identify pauses (e.g., silence between songs in a radio or MP3 data stream) or periods of low data traffic, and when such a pause or period is identified, initiate the master/slave role swap. In various embodiments, such pauses or periods may include media breaks that may be detected by subscription Bluetooth® events in an Audio/Video Remote Control Profile (AVRCP) profile (e.g., AVRCP > 1.3), by trapping an application programming interface (API) from the source device's media player, and/or by using track meta data (e.g., track length, current track position, etc.).

0043As discussed above, the wear-leveling operations may be performed such that the user does not perceive any changes in the operations of the devices. In an embodiment, the first and second earpieces 206, 208 may be configured to swap master and slave roles in response to determining that information transmitted from the source device (e.g., phone 204 or wrist display 210) is to be received on a specific device (e.g., first earpiece 206) having a specific role (e.g., master role) and that the specific device (e.g., first earpiece 206) is not currently acting in the specific role (e.g., master role). In an embodiment, it may be determined that information transmitted from the source device (e.g., phone 204 or wrist display 210) is to be received on a specific device having a specific role (e.g., first earpiece 206 serving as the master) by detecting that the transmitted information is monaural sound information.

0044In an embodiment, the first and second earpieces 206, 208 may be configured to delay or suspend role swap operations until it is determined that the information transmitted from the source device (e.g., phone 204 or wrist display 210) is such that the master and slave roles may be swapped without impacting the user experience. This may be achieved, for example, by detecting that the information transmitted by the source device is monaural sound information.

0045<figref idref="f0003">FIG. 3A</figref> illustrates an embodiment method 300 for dynamically swapping master and slave roles to balance the load on each wireless node device's battery. The operations in method 300 and also methods 350, 400A, 400B, 400C, which are described below, may be accomplished by processors within wireless nodes or devices (e.g., left earpiece, right earpiece, wrist display, phone or combination thereof) configured with processor-executable instructions implementing the method, so references to each wireless node or device encompass the processor within the node or device. In block 302, a first wireless node (e.g., left earpiece) may establish a communication link (e.g., Bluetooth® link) with a second wireless node (e.g., right earpiece), which may include, for example, the first wireless node negotiating one or more communication parameters with the second wireless node. As part of block 302, the first wireless node may assume a role as a master node and the second wireless node may assume a role as a slave node. In block 304, the first wireless node may establish a communication link (e.g., Bluetooth® link) with a wireless source device (e.g., wrist display, phone). In block 306, the first wireless node may begin receiving one or more content streams (e.g., audio and/or data streams) via a signal from the wireless source device. In block 308, the first wireless node may begin relaying all or a portion of one or more of the received content streams via a signal to the second wireless node. If desired, the first wireless node may also generate and/or transmit-to the second wireless node-one or more controls related to processing the relayed content streams via the signal. In optional block 310, the first wireless node, the second wireless node, and/or the wireless source device may monitor the battery consumption of the first and second wireless nodes.

0046In determination block 312, the first wireless node, the second wireless node, and/or the wireless source device may determine whether it is time to swap roles. This determination may be based on various factors, such as battery usage, periods of inactivity or silence, a time value, measured energy consumption, processor instructions performed, current battery level, differences in battery states between the first and second wireless nodes, etc. For example, the first wireless node, the second wireless node, and/or the wireless source device may consider the amount of time that the first wireless node has performed the master role, the amount of battery consumed by the master node and/or the slave node, the amount of battery remaining on the master node and/or the slave node, the types or volume of the communications being transmitted, the number of master-specific operations required to process the communications, and other similar factors. In response to the first wireless node, the second wireless node, and/or the wireless source device determining that it is not time to swap roles (i.e., determination block 312 = "No"), the first and second wireless nodes may continue to receive content over the established communication links in block 306. In response to the first wireless node, the second wireless node, and/or the wireless source device determining that it is time to swap roles (i.e., determination block 312 = "Yes"), the first and second wireless nodes may swap roles in block 314, for instance, by establishing a new master-slave communication link. In an embodiment, swapping roles in block 314 may further include swapping MAC addresses in the link keys associated with the first and second wireless nodes. In another embodiment, in block 314, the MAC address in the link key associated with the new master node (e.g., the second wireless node) may be changed to the MAC address in the link key that was associated with the previous master node (e.g., the first wireless node), and the MAC address in the link key associated with the new slave node (e.g., the first wireless node) may be changed to any desired MAC address.

0047<figref idref="f0004">FIG. 3B</figref> illustrates an embodiment method 350 for dynamically swapping master and slave roles. Method 350 may form part of block 314 of method 300 in <figref idref="f0003">FIG. 3A</figref>. In block 352 of method 350, the communication link between the master node (e.g., first wireless node) and the wireless source device may be terminated, for instance, by unpairing the master node from the wireless source device and/or otherwise terminating the link between the master node and the wireless source node. In block 354, the communication link between the master node (e.g., first wireless node) and the slave node (e.g., second wireless node) may be terminated, for instance, by unpairing the master node from the slave node and/or otherwise terminating the link between the master node and the slave node. In block 356, the first wireless node may assume the slave role, the second wireless node may assume the master role, and the first and second wireless nodes may establish a new communication link between the second wireless node (as the new master node) and the first wireless node (as the new slave node). This may be accomplished by the new master node initiating the handshaking communications necessary to establish the new communication link while the new slave node cooperates in the handshaking communications. In block 358, the new master node (e.g., second wireless node) may establish a communication link with the wireless source device.

0048<figref idref="f0005">FIG. 4A</figref> illustrates an embodiment method 400A for dynamically swapping master and slave roles so that there is reduced impact on the user experience. In block 402, a first wireless node (e.g., left earpiece) may establish a communication link (e.g., Bluetooth® link) with a second wireless node (e.g., right earpiece). As part of block 402, the first wireless node may assume the role as a master wireless node and the second wireless node may assume the role as a slave wireless node. In block 404, the first wireless node may establish a communication link (e.g., Bluetooth® link) with a wireless source node (e.g., wrist display, phone). In block 406, the first wireless node may begin receiving one or more content streams (e.g., audio and/or data streams) via a signal from the wireless source device and relaying all or a portion of one or more of the received content streams via a signal to the second wireless node. If desired, the first wireless node may also generate and/or transmit to the second wireless node one or more controls related to processing the relayed content streams via the signal. In determination block 407, the first wireless node, the second wireless node, and/or the wireless source device may determine whether it is time to swap roles. This determination may be based on various factors, such as battery usage, periods of inactivity or silence, a time value, measured energy consumption, processor instructions performed, current battery level, differences in battery states between the first and second wireless nodes, etc. For example, the first wireless node, the second wireless node, and/or the wireless source device may consider the amount of time that the first wireless node has performed the master role, the amount of battery consumed by the master node and/or the slave node, the amount of battery remaining on the master node and/or the slave node, the types or volume of the communications being transmitted, the number of master-specific operations required to process the communications, and other similar factors. In response to the first wireless node, the second wireless node, and/or the wireless source device determining that it is not time to swap roles (i.e., determination block 407 = "No"), the first and second wireless nodes may continue to receive content over the established communication links in block 406. In response to the first wireless node, the second wireless node, and/or the wireless source device determining that it is time to swap roles (i.e., determination block 407 = "Yes"), in block 408, the first wireless node (or another component in the system) may monitor a signal to, as discussed above, identify one or more points in the communication stream in which a role-swap is likely to have a reduced impact on the user experience. In some embodiments, to identify such points in block 408, the first wireless node, the second wireless node, and/or the wireless source device may monitor the signal from the wireless source device to the first wireless node, the signal from the first wireless node to the second wireless node, or both. In block 410, the first and second wireless nodes may swap master-slave roles, for instance, as described above with reference to block 314 in <figref idref="f0003">FIG. 3A</figref> and/or method 350 in <figref idref="f0004">FIG. 3B</figref>. In block 412, the second wireless node (new master node) may begin receiving one or more content streams (e.g., audio and/or data streams) via a signal from the wireless source device, relaying all or a portion of one or more of the received content streams via a signal to the first wireless node (new slave node) and, if desired, generating and/or transmitting-to the first wireless node-one or more controls related to processing the relayed content streams via the signal, essentially returning to block 406 to continue the process described above.

0049<figref idref="f0006">FIG. 4B</figref> illustrates an embodiment method 400B for dynamically swapping master and slave roles that accommodates situations in which monaural sound is being transmitted and the user has a preferred ear for receiving monaural sound (e.g., an ear preferred for telephone calls). Method 400B is substantially similar to method 400A described above with reference to <figref idref="f0005">FIG. 4A</figref>, with the addition of block 413 in which the new master node determines the appropriate ear for playing monaural sound, and either begins generating that monaural sound if the new master node determines that the new master node is in the user's preferred ear, or transmitting monaural sound to the new slave node if the new master node determines that the new slave node is in the user's preferred ear.

0050<figref idref="f0007">FIG. 4C</figref> illustrates an embodiment method 400C for dynamically swapping master and slave roles that accommodates source devices which are receptive to control signals from the master node, such as a pause request. Method 400C is similar to method 400A described above with reference to <figref idref="f0005">FIG. 4A</figref>, with the addition of determination block 414 and blocks 416 and 418. In response to the first wireless node, the second wireless node, and/or the wireless source device determining that it is time to swap the master and slave roles (i.e., determination block 407 = "Yes"), the first wireless node, the second wireless node, and/or the wireless source device may determine whether the wireless source device is currently controllable in determination block 414. The determination in block 414 may be based upon the type of wireless source device with which the master node is communicating, such as whether the wireless source device is capable of receiving commands or pause request. In an embodiment, the determination in block 414 may also be based upon the type of media being played, such as whether the media is a broadcast stream which cannot be interrupted, or a recorded media (e.g., an MP3 file). In a further embodiment, the determination in block 414 may also be based upon the type of content being played in a recorded media, such as whether the recorded media is primarily speech, which can easily be caused without impacting the user experience without the need for waiting for a gap between content segments. This embodiment may be particularly useful when the media being played is a podcast, lecture, or audio book.

0051In response to the first wireless node, the second wireless node, and/or the wireless source device determining that the wireless source device is currently not controllable (i.e., determination block 414 = "No"), the processor may continue to execute the operations in blocks 408 through 412 as described above in method 400A with reference to <figref idref="f0005">FIG. 4A</figref>. In response to the first wireless node, the second wireless node, and/or the wireless source device determining that the source device is currently controllable (i.e., determination block 414 = "Yes"), the first wireless node and/or the second wireless node may, in block 416, send a signal to the wireless source device requesting that the wireless source device execute a pause. The signal may be any type of control signal that is receivable by the wireless source device, and thus may be defined by the particular make and model of wireless source device. In block 418, when the source device executes the requested pause, the first and second wireless nodes may swap master-slave roles, for instance, as described above with reference to block 314 in <figref idref="f0003">FIG. 3A</figref> and/or method 350 in <figref idref="f0004">FIG. 3B</figref>. In this operation, the first and second wireless nodes may wait for a signal from the source device indicating that it is paused or monitor the data stream to detect when the pause has been implemented. After the master/slave role swap is completed in either block 410 or block 418, the second wireless node (new master node) may begin receiving one or more content streams (e.g., audio and/or data streams) via a signal from the wireless source device, relaying all or a portion of one or more of the received content streams via a signal the first wireless node (new slave node) and, if desired, generating and/or transmitting-to the first wireless node-one or more controls related to processing the relayed content streams via the signal, essentially returning to block 406 to continue the process described above.

0052As discussed above, various communication links may be established between the first wireless node and the wireless source device and between the second wireless node and the wireless source device. In some embodiments, an intermediary wireless device (e.g., wrist display 210) may help establish these communication links, for example, by facilitating pairing the first or second wireless node (e.g., earpiece 206 or earpiece 208) with the wireless source device (e.g., phone 204). For instance, the intermediary wireless device may negotiate a pairing with the wireless source device on behalf of the first or second wireless node, for example, as disclosed in Applicant's co-pending application, entitled "SMART PAIRING USING BLUETOOTH® TECHNOLOGY" (Attorney Docket No. 113422), filed concurrently with this application and incorporated by reference herein in its entirety.

0053The various embodiments described above may be implemented using a variety of wireless-enabled mobile computing devices, such as a wrist watch-type computing device ("wrist display") 500 illustrated in <figref idref="f0008">FIG. 5</figref>. A wrist watch computing device 500 may include a processor 502 coupled to a volatile and/or non-volatile internal memory 504, which may be secure and/or encrypted memories, unsecure and/or unencrypted memories, or any combination thereof. The processor 502 may also be coupled to an electronic display screen 506, which may be a touch screen display (e.g., resistive-sensing touch screen, capacitive-sensing touch screen infrared sensing touch screen, etc.). The wrist display 500 may have one or more radios (e.g., RF radio) and/or antennas 508 for sending and receiving electromagnetic radiation that may be connected to a wireless data link and coupled to the processor 502. The radios/antennas 508 may be used with the above-mentioned circuitry to implement the Bluetooth® protocol stack/interface (i.e., the wrist display 500 may be Bluetooth®-enabled).

0054The wrist display 500 may also include a slide sensor 510 and physical buttons 512 for receiving user inputs. The wrist display 500 may include a battery 516 coupled to an inductive charging circuit 518, and a coil antenna 520 which may be an inductive coil adapted to enable inductive charging of the battery 516. The battery 516 and inductive charging circuit 518 may be coupled to the processor 502 to enable the wrist display 500 to control inductive charging and generate messages via the coil antenna 520. The wrist display 500 may further include a vibratory motor 522, and various sensors, such as a temperature sensor 524 and accelerometer 526, all of which may be coupled to the processor 502.

0055Other examples of wireless-enabled mobile computing devices that may be used to implement the various embodiments described above include wireless earpieces, such as wireless earpiece 600 as illustrated in <figref idref="f0009">FIG. 6</figref>. A wireless earpiece 600 may include a processor 602 coupled to volatile or non-volatile internal memories 604 and 606. The wireless earpiece 600 may include one or more radios/antennas 608 for sending and receiving electromagnetic radiation that may be connected to a wireless data link and coupled to the processor 602. The radios/antennas 608 may be used with the above-mentioned circuitry to implement the Bluetooth® protocol stack/interface (i.e., the wireless earpiece 600 may be Bluetooth®-enabled).

0056The wireless earpiece 600 may also include one or more physical buttons 610 for receiving user inputs, a speaker 612 configured to generate an audio output, and a microphone 614 to receive audio input, all of which may be coupled to the processor 602. The wireless earpiece 600 may further include a battery 616 coupled to an inductive charging circuit 618, and a coil antenna 620 which may be an inductive coil adapted to enable inductive charging of the battery 616.

0057The various embodiments may also be implemented using any commercial computing devices having an RF radio, examples of which are illustrated in <figref idref="f0010">FIGs. 7</figref> and <figref idref="f0011">8</figref>. Typical mobile computing devices 700 will have in common the components illustrated in <figref idref="f0010">FIG. 7</figref>. For example, mobile computing devices 700 may include a processor 702 coupled to an internal memory 704 and a touch surface input device/display 706, such as a resistive sensing touchscreen, capacitive sensing touchscreen, infrared sensing touchscreen, acoustic/piezoelectric sensing touchscreen, or the like. The computing device 700 may have a radio/antenna 710 for sending and receiving electromagnetic radiation that is connected to a wireless data link and/or cellular telephone transceiver 708 coupled to the processor 702. Computing devices 700 may also include physical buttons 712 for receiving user inputs.

0058Other forms of computing devices, including personal computers and laptop computers, may be used to implementing the various embodiments. Such computing devices typically include the components illustrated in <figref idref="f0011">FIG. 8</figref> which illustrates an example personal laptop computer 800. Such a personal computer 800 generally includes a processor 802 coupled to volatile memory 804 and a large capacity nonvolatile memory, such as a disk drive 806. The computer 800 may also include a compact disc (CD) and/or DVD drive 808 coupled to the processor 802. The computer device 800 may also include a number of connector ports coupled to the processor 802 for establishing data connections or receiving external memory devices, such as a network connection circuit for coupling the processor 802 to a network. The computing device 800 may have a radio/antenna 810 for sending and receiving electromagnetic radiation that is connected to a wireless data link coupled to the processor 802. The computer 800 may further be coupled to a keyboard 816, a pointing device such as a mouse 814, and a display 812 as is well known in the computer arts.

0059The processors 502, 602, 702, 802 may be any programmable microprocessor, microcomputer or multiple processor chip or chips that may be configured by software instructions (applications) to perform a variety of functions, including the functions of the various embodiments described herein. Multiple processors may be provided, such as one processor dedicated to wireless communication functions and one processor dedicated to running other applications. Typically, software applications may be stored in the internal memory before they are accessed and loaded into the processor 502, 602, 702, 802. In some devices, the processor 502, 602, 702, 802 may include internal memory sufficient to store the application software instructions. In some mobile devices, the secure memory may be in a separate memory chip coupled to the processor 502, 602, 702, 802. The internal memory may be a volatile or nonvolatile memory, such as flash memory, or a mixture of both. For the purposes of this description, a general reference to memory refers to all memory accessible by the processor, including internal memory, removable memory plugged into the device, and memory within the processor 502, 602, 702, 802 itself.

0060The foregoing method descriptions and the process flow diagrams are provided merely as illustrative examples and are not intended to require or imply that the blocks of the various embodiments must be performed in the order presented. As will be appreciated by one of skill in the art the order of blocks in the foregoing embodiments may be performed in any order. Words such as "thereafter," "then," "next," etc. are not intended to limit the order of the blocks; these words are simply used to guide the reader through the description of the methods. Further, any reference to claim elements in the singular, for example, using the articles "a," "an" or "the" is not to be construed as limiting the element to the singular.

0061The various illustrative logical blocks, modules, circuits, and algorithm blocks described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

0062The hardware used to implement the various illustrative logics, logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Alternatively, some steps or methods may be performed by circuitry that is specific to a given function.

0063In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a non-transitory computer-readable or processor-readable storage medium. The steps of a method or algorithm disclosed herein may be embodied in a processor-executable software module which may reside on a non-transitory processor-readable or computer-readable storage medium. Non-transitory processor-readable and computer-readable media may be any available storage media that may be accessed by a computer or a processor of a computing device. By way of example, and not limitation, such non-transitory processor-readable or computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to carry or store desired program code in the form of instructions or data structures and that may be accessed by a computer or processor of a computing device. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of non-transitory computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a non-transitory processor- readable medium and/or non-transitory computer-readable medium, which may be incorporated into a computer program product.

0064The preceding description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the following claims and the principles and novel features disclosed herein.