Patent Description:
This disclosure relates generally to audio operating systems, and more specifically to audio operating systems for portable electronic accessory systems such as truly wireless stereo (TWS) headphone systems.

Truly wireless stereo (TWS) headphones have become a popular alternative to conventional wired headphones. TWS headphones allow the user to listen to music and podcasts, participate in two-way voice and video communications, and hear audio for videos without the inconveniences associated with wired headphones. TWS headphones are commonly sold with a TWS headphone case that is used to charge and store the TWS headphones.

Document <CIT> B <NUM> discloses a system for audibly outputting a notification to a user, the system comprising: an audio device in network communication with the server, the audio device comprising: a microphone configured to receive audible commands from a user; a loudspeaker configured to output audible notifications to the user; a hardware processor; and a memory storing instructions that, when executed by the hardware processor, configure the hardware processor to: receive, over a network, user-specific notification data associated with the user; determine an indication to output audible notifications associated with the user; output, based at least on the user-specific notification data associated with the user, a top-level audible notification via the loudspeaker, the top-level audible notification identifying a plurality of categories of user-specific audible content, each respective category selectable by the user using a corresponding voice command to explore additional details of the respective category; receive a first voice command from the user in response to the top-level audible notification, the first voice command identifying the user's selection of a first category of the plurality of categories identified by the top-level audible notification to explore additional details of the selected category; in response to the first voice command, output a lower-level audible notification via the loudspeaker, the lower-level audible notification identifying at least a first sub-category of user-specific audible content that is categorized under the first category and selectable in response to the lower-level audible notification; transmit, over the network, an indication of the user's selection of the first category over one or more other categories of the plurality of categories identified by the top-level audible notification; receive, over the network, modified user-specific notification data associated with the user, the modified user-specific notification data being different than the user-specific notification data previously received; subsequent to outputting the lower-level audio notification, determine another indication to output audible notifications associated with the user; and output, using at least the modified user-specific notification data associated with the user, a modified top-level audible notification via the loudspeaker, the modified top-level audible notification (i) identifying at least the first sub-category of user-specific audible content previously identified by the lower-level audible notification, (ii) causing such that the first sub-category to be selectable to cause presentation of multiple user-selectable items associated with the first sub-category in response to the modified top-level audible notification instead of another lower-level audible notification and thereby reducing a delay associated with outputting the multiple user-selectable items associated with the first sub-category based at least on the use of the modified user-specific notification data, and (iii) no longer identifying the first category such that at least one sub-category categorized under the first category is not accessible by selecting the first category in response to the modified top-level audible notification.

Document <CIT> discloses method comprising: receiving a first audio signal corresponding to a first microphone of a device; receiving a second audio signal corresponding to a second microphone of the device; generating, based on at least one of the first audio signal or the second audio signal, a third audio signal corresponding to a voice beam directed to an expected position of a mouth of a user of the device; determining, based on at least one of the first audio signal, the second audio signal, or the third audio signal, whether wind noise is present in at least one of the first, second, or third audio signals; and selecting, based on determining whether wind noise is present, an audio signal from among the second audio signal or the third audio signal, for a determination of whether at least one of the first or second audio signals corresponds to the user.

While this disclosure concludes with claims defining the scope of the invention, various features and advantages of embodiments within the scope of this disclosure may be more readily ascertained from the following description when read in conjunction with the accompanying drawings, in which:.

In the following detailed description, reference is made to the accompanying drawings, which form a part hereof, and in which are shown, by way of illustration, specific examples of embodiments in which the present disclosure may be practiced. These embodiments are described in sufficient detail to enable a person of ordinary skill in the art to practice the present invention as defined by the appended claims.

<FIG> is a block diagram of a portable electronic accessory system <NUM>, according to some embodiments. The portable electronic accessory system <NUM> includes a portable electronic accessory <NUM> and a removable control package <NUM>. The portable electronic accessory <NUM> includes a battery <NUM> configured to provide battery power <NUM> and a control socket <NUM> configured to receive the removable control package <NUM>. The removable control package <NUM> is configured to control operation of the portable electronic accessory <NUM>. The portable electronic accessory <NUM> also includes power circuitry <NUM> configured to deliver at least a portion of the battery power <NUM> to the removable control package <NUM> to power the removable control package <NUM>.

The removable control package <NUM> also includes a power connector <NUM> configured to receive external power <NUM> from an external power source <NUM> and provide the external power <NUM> to the power circuitry <NUM>. By way of non-limiting example, the external power source <NUM> may include an alternating current (AC) to direct current (DC) power converter configured to convert AC power from a plug to the external power <NUM> in the form of DC power. Also by way of non-limiting example, the external power source <NUM> may include a wireless power transmitter and the power connector <NUM> may include a wireless power receiver. The power circuitry <NUM> provides battery power <NUM> to the battery <NUM> responsive to the external power <NUM>. The power circuitry <NUM> may also control charging of the battery <NUM> and distribution of the battery power <NUM> from the battery <NUM> to the removable control package <NUM>.

In some embodiments the portable electronic accessory <NUM> is a truly wireless stereo (TWS) headphone case including headphone receptacles <NUM>. The headphone receptacles <NUM> are configured to receive headphones <NUM> (e.g., TWS headphones) therein to store the headphones <NUM> in the TWS headphone case and charge headphone batteries <NUM> of the headphones <NUM> while the headphones <NUM> are received in the headphone receptacles <NUM>. In some embodiments the headphone receptacles <NUM> include charging pins <NUM> therein. The charging pins <NUM> are configured to deliver charging power to the headphones <NUM> when the headphones <NUM> are received in the headphone receptacles <NUM>. The power circuitry <NUM> may be configured to control delivery of the battery power <NUM> to the charging pins <NUM>. The headphones <NUM> may store the charging power in the headphone batteries <NUM>. The headphone batteries <NUM> are configured to power speakers <NUM> and microphones <NUM>, and circuitry of the headphone <NUM>. Although the portable electronic accessory <NUM> illustrated in <FIG> is a TWS headphone case, the disclosure is not so limited. For example, in some embodiments the portable electronic accessory <NUM> may be a watch (e.g., a smart watch), electronic glasses, or a speaker assembly (e.g., a wireless speaker).

In some embodiments the control socket <NUM> has a form factor of a secure digital (SD) card socket and the removable control package <NUM> has a form factor of an SD card. An SD card form factor may enable easy insertion and removal of the removable control package <NUM> from the control socket <NUM>. The control socket <NUM> and the removable control package <NUM> may take other forms, however. For example, the control socket <NUM> and the removable control package <NUM> may instead reflect a Compact-Flash form factor, a MultiMediaCard form factor, a Memory Stick form factor, or any other form factor. In some embodiments the control socket <NUM> is configured to completely house the removable control package <NUM>. In some embodiments the control socket <NUM> is configured to at least partially house the removable control package <NUM>.

The removable control package <NUM> includes input/output pins (I/O pins <NUM>) configured to interface with control pins <NUM> of the control socket <NUM> of a portable electronic accessory <NUM>. The control socket <NUM> is configured to removably receive the removable control package <NUM>. The I/O pins <NUM> are configured to electrically connect to the control pins <NUM> of the control socket <NUM> when the removable control package <NUM> is received into the control socket <NUM>. The I/O pins <NUM> are configured to receive battery power <NUM> from the battery <NUM> of the portable electronic accessory <NUM>.

The removable control package <NUM> is configured to power circuitry of the removable control package <NUM> using the battery power <NUM> received through the I/O pins <NUM>. For example, the removable control package <NUM> may include one or more communication radio circuits. By way of non-limiting examples, the communication radio circuits may include one or more cellular data radio circuits <NUM> (e.g., a fourth generation (<NUM>) long-term evolution (LTE) radio circuit, a fifth generation (<NUM>) radio circuit, etc.), and one or more PAN radio circuits <NUM> (e.g., a Bluetooth radio circuit, a Zigbee radio circuit, etc.). Also by way of non-limiting example, the cellular data radio circuits <NUM> may include one or more of a narrow-band internet of things (NB-IoT) radio circuit and an enhanced machine type communication (eMTC) long-term evolution (LTE-M) radio circuit.

The one or more communication radio circuits are configured to provide wireless communication capabilities to the portable electronic accessory <NUM>. In embodiments where the cellular data radio circuits <NUM> include an NB-IoT radio circuit the cellular data radio circuits <NUM> may be capable of providing voice and data communications. In embodiments where the cellular data radio circuits <NUM> include an LTE-M radio circuit the cellular data radio circuits <NUM> may be capable of providing full music streaming capabilities to the cellular data radio circuits <NUM>.

In embodiments where the removable control package <NUM> includes one or more cellular data radio circuits <NUM> the removable control package <NUM> may include a Subscriber Identity Module (SIM) card slot (SIM card slot <NUM>) configured to receive a SIM card <NUM>. The cellular data radio circuits <NUM> may use the SIM card slot <NUM> in cellular data operations.

In some embodiments one or more communication radio circuits of the removable control package <NUM> may be configured to communicate with one or more antennas <NUM> of the portable electronic accessory <NUM> through the I/O pins <NUM> and the control pins <NUM>. In some embodiments the one or more antennas <NUM> may include a cellular data antenna (not shown) configured to interface with the one or more cellular data radio circuits <NUM> of the removable control package to enable the cellular data radio circuits <NUM> to communicate by way of a cellular data network (not shown). By way of non-limiting example, the one or more antennas <NUM> may include a <NUM> LTE cellular data antenna. Also by way of non-limiting example, the one or more antennas <NUM> may include a <NUM> cellular data antenna. As another non-limiting example, the one or more antennas may include a narrow-band internet of things (NB-IoT) antenna configured to interface with an NB-IoT radio circuit of the cellular data radio circuits <NUM>. The NB-IoT antenna may be configured to enable the NB-IoT radio circuit to communicate by way an NB-IoT network. As a further non-limiting example, the one or more antennas may include an enhanced machine type communication (eMTC) long-term evolution (LTE-M) antenna configured to interface with an LTE-M radio circuit of the cellular data radio circuits <NUM>. The LTE-M radio circuit is configured to enable the LTE-M radio circuit to communicate by way an NB-IoT network. As an even further non-limiting example, the one or more antennas <NUM> may include a wireless PAN (e.g., Bluetooth, Zigbee, etc.) antenna configured to interface with a wireless PAN radio circuit of the PAN radio circuits <NUM>. The wireless PAN antenna may enable the PAN radio circuits <NUM> to communicate with one or more PAN peripheral devices (e.g., the headphones <NUM>). By way of non-limiting example, the headphones <NUM> may include antennas <NUM> and PAN peripheral circuits <NUM>. The PAN peripheral circuits <NUM> may be configured to communicate with the PAN radio circuits <NUM> through the antennas <NUM> and the one or more antennas <NUM> or one or more antennas <NUM> (discussed in more detail below).

In some embodiments the removable control package <NUM> itself may include one or more antennas <NUM>. The one or more antennas <NUM> may include any one or more of the one or more antennas <NUM> discussed above. As a result, in various embodiments all the antennas may be located in the removable control package <NUM>, all of the antennas may be located in the portable electronic accessory <NUM>, or the antennas may be distributed within both the removable control package <NUM> and the portable electronic accessory <NUM>. Because of limited space on the removable control package <NUM>, however, it may be convenient to provide most or all of the antennas in the one or more antennas <NUM> of the portable electronic accessory <NUM>.

The removable control package <NUM> may further include one or more application processors <NUM> and one or more data storage devices <NUM> (e.g., serial Flash, pseudo-static dynamic random access memory (PSRAM), etc.). The data storage devices <NUM> are configured to store computer-readable instructions for an operating system (e.g., an audio operating system) and software applications (e.g., music software applications). The application processors <NUM> are configured to execute the computer-readable instructions stored by the data storage devices <NUM>. An audio operating system may be used with truly wireless stereo (TWS) headphones <NUM> responsive to insertion of the removable control package <NUM> into the control socket <NUM>. , the portable electronic accessory comprising a TWS headphone case for the TWS headphones. The application processors <NUM> may be configured to execute one or more music software applications to provide music to the headphones <NUM> (e.g., via the PAN radio circuits <NUM>). Although the application processors <NUM> is shown separately from the cellular data radio circuits <NUM> and the PAN radio circuits <NUM>, in some embodiments the application processors <NUM> may be implemented on the cellular data radio circuits <NUM> or the PAN radio circuits <NUM>. As a specific non-limiting example the application processors <NUM> may be implemented on one or more PAN radio circuits <NUM> including a Bluetooth radio circuit such as on an Airoha AB1552A BLUETOOTH® system on chip (SoC). The data storage devices <NUM> may also be configured to store audio data (e.g., music, podcasts, etc.), which may be provided to the headphones <NUM> via the PAN radio circuits <NUM> and the PAN peripheral circuits <NUM>.

In operation, the removable control package <NUM> may be inserted into the control socket <NUM>. As a result, the removable control package <NUM> may be powered by battery power <NUM> delivered to the removable control package <NUM> (e.g., via the control pins <NUM> and the I/O pins <NUM>). If the headphones <NUM> are removed from the headphone receptacle <NUM> (e.g., worn by a user) the PAN radio circuits <NUM> of the removable control package <NUM> may communicate with the PAN peripheral circuits <NUM> of the headphones <NUM> (e.g., through the one or more antennas <NUM> or the one or more antennas <NUM> and the antennas <NUM>). As a result the application processors <NUM> may provide and receive audio elements (e.g., audio commands received through the microphones <NUM>, button or touch inputs received through buttons or touch sensors of the headphones <NUM>, etc.) for an audio operating system to and from the headphones <NUM> via the PAN radio circuits <NUM>, which is in communication with the PAN peripheral circuits <NUM> of the headphone <NUM>. The cellular data radio circuits <NUM> may provide an Internet connection (e.g., via the one or more antennas <NUM> or the one or more antennas <NUM>), which may be utilized by the operating system to provide network resources.

By way of non-limiting example, audio (e.g., music, podcasts, etc.) may be streamed to the speakers <NUM> of the headphone <NUM> using a multi-media software application (e.g., a music software application, a podcast software application, etc.) enabled by the application processors <NUM>. The audio may be provided by a content provider through the Internet. The one or more antennas <NUM> or the one or more antennas <NUM> may receive the audio from the Internet and provide the audio to the cellular data radio circuits <NUM>. The application processors <NUM> may control the PAN radio circuits <NUM> to provide the audio to the PAN peripheral circuits <NUM> of the headphones <NUM> (e.g., by providing the audio to the one or more antennas <NUM>, which may provide the audio to the antennas <NUM> of the headphones <NUM>).

Also by way of non-limiting example, two-way voice communication may be enabled. For example, the microphones <NUM> may capture voice data corresponding to acoustic waves in proximity to the microphones <NUM>, and provide the voice data to the PAN peripheral circuits <NUM>. The PAN peripheral circuits <NUM> may transmit the voice data, using the antennas <NUM>, to the one or more antennas <NUM> or the one or more antennas <NUM>, which may provide the voice data to the PAN radio circuits <NUM>. The cellular data radio circuits <NUM> may then transmit the voice data over the Internet via the one or more antennas <NUM> or the one or more antennas <NUM>. The cellular data radio circuits <NUM> may also receive received voice data transmitted to the cellular data radio circuits <NUM> via the one or more antennas <NUM> or the one or more antennas <NUM> through the Internet. The PAN radio circuits <NUM> may forward the received voice data to the PAN peripheral circuits <NUM> via the one or more antennas <NUM> or the one or more antennas <NUM>, and the PAN peripheral circuit <NUM> may provide the received voice data to the speakers <NUM>, which may convert the received voice data to acoustic waves. In this way, a user may engage in two-way voice communications using the portable electronic accessory system <NUM>.

As a further non-limiting example, the application processors <NUM> may provide an audio user interface via the headphones <NUM>. For example, audio messages corresponding to menu options may be stored in the data storage devices <NUM>, and the audio messages may be provided to the headphones <NUM> for presentation to the user using the speakers <NUM> via the PAN radio circuits <NUM> and the PAN peripheral circuits <NUM>. As another example, audio messages corresponding to menu options may be stored remotely by one or more cloud servers. User selections, other verbal commands, and/or button selections of buttons on the headphones <NUM> and/or on the portable electronic accessory <NUM> may be received at the application processors <NUM> (e.g., through the PAN peripheral circuits <NUM> and the PAN radio circuits <NUM> or via the control pins <NUM> and the I/O pins <NUM>).

Software applications that may be stored by the data storage devices <NUM> and executed by the application processors <NUM> (or stored and/or executed by one or more cloud servers) may include audio software applications configured to operate free from graphical user interface elements based at least in part on audio inputs and audio outputs of the audio user interface. By way of non-limiting examples, audio software applications may include a community engagement on the go software application, a location intelligence software application, a health and workout intelligence software application, a voice interface software application (e.g., a phone software application), online shopping software applications, search engine software applications, web browser software applications, music streaming software applications, cloud connection software applications, a settings software application, a software application store software application, a music sharing software application, an audio-enabled text message software application, other software applications, or combinations thereof.

It is contemplated herein that the control socket <NUM> is configured to receive various different removable control packages. For example, when a user is desirous to upgrade functional features of the removable control package <NUM>, the user may simply remove the removable control package <NUM> and replace the removable control package <NUM> with a different removable control package having upgraded capabilities. In a similar way a faulty removable control package may be removed from the control socket <NUM> and replaced with a functional removable control package to enable replacement of the electronics of the removable control package <NUM> without the need to replace the portable electronic accessory <NUM>. Furthermore, the portable electronic accessory <NUM> may be replaced without the need to replace the removable control package <NUM> because the removable control package <NUM> may be removed from the portable electronic accessory <NUM> and placed into a new portable electronic accessory. Also, a user may use the removable control package <NUM> with various different portable electronic accessories. For example, the user may remove the removable control package <NUM> from the control socket <NUM> of the portable electronic accessory <NUM> and insert the removable control package <NUM> into a different portable electronic accessory (e.g., another TWS headphone case, a smart watch, electronic glasses, etc.). As a result, a single removable control package <NUM> may be used in conjunction with several different portable electronic devices without the need for expensive control circuitry in each of the portable electronic devices.

<FIG> is a block diagram of another portable electronic accessory system <NUM>, according to some embodiments. The portable electronic accessory system <NUM> is similar to the portable electronic accessory system <NUM> of <FIG>. For example, the portable electronic accessory system <NUM> includes the external power source <NUM> and headphones <NUM>, as discussed with reference to <FIG>. The portable electronic accessory system <NUM> also includes a portable electronic accessory <NUM>, which is similar to the portable electronic accessory <NUM> of <FIG> except that instead of the removable control package <NUM> of the portable electronic accessory <NUM> of <FIG>, the portable electronic accessory <NUM> includes control circuitry <NUM>, which is built into (e.g., not removable from) the portable electronic accessory <NUM>.

Similar to the removable control package <NUM>, the control circuitry <NUM> includes the SIM card slot <NUM>, the SIM card <NUM>, the cellular data radio circuits <NUM>, the PAN radio circuits <NUM>, the application processors <NUM>, the one or more antennas <NUM>, and the data storage devices <NUM> discussed above with reference to <FIG>. The control circuitry <NUM>, however, may not include the I/O pins <NUM> and the portable electronic accessory <NUM> may not include the control pins <NUM> discussed above with reference to <FIG>. Rather, since the control circuitry <NUM> is built into the portable electronic accessory <NUM>, the power circuitry <NUM> may deliver the battery power <NUM> to the control circuitry <NUM> without the need for detachable pins.

<FIG> is a block diagram of a cloud-assisted audio system <NUM>, according to some embodiments. The cloud-assisted audio system <NUM> includes a portable electronic accessory system <NUM>, which may include, by way of non-limiting example, the portable electronic accessory system <NUM> of <FIG> or the portable electronic accessory system <NUM> of <FIG>. The cloud-assisted audio system <NUM> also includes a cellular base station <NUM> and cloud servers <NUM>, which are connected to the Internet <NUM>.

The portable electronic accessory system <NUM> includes headphones <NUM> similar to the headphones <NUM> of <FIG> and <FIG>. The portable electronic accessory system <NUM> also includes a portable electronic accessory <NUM> similar to the portable electronic accessory <NUM> of <FIG> and the portable electronic accessory <NUM> of <FIG>. The portable electronic accessory <NUM> includes control circuitry <NUM>, which may include a removable control package such as the removable control package <NUM> of <FIG> or built in control circuitry such as the control circuitry <NUM> of <FIG>.

The control circuitry <NUM> is operably coupled to the headphones <NUM> (e.g., via one or more wireless PAN networks <NUM>). Accordingly, the control circuitry <NUM> is operably coupled to speakers <NUM> and microphones <NUM> (<FIG> and <FIG>) of the headphones <NUM>. The microphones <NUM> of the headphone <NUM> are configured to receive audio inputs. The speakers <NUM> are configured to provide audio outputs. The wireless PAN network <NUM> may deliver the audio inputs and audio outputs (audio I/O <NUM>) between the headphones <NUM> and the control circuitry <NUM>.

The control circuitry <NUM> includes one or more application processors <NUM> and one or more cellular data radio circuits <NUM> operably coupled to the one or more application processors <NUM>. The cellular data radio circuits <NUM> are configured to communicate with the cloud servers <NUM> through a cellular data network <NUM> (e.g., via the cellular base station <NUM> and the Internet <NUM>). The cellular data radio circuits <NUM> are examples of the cellular data radio circuits <NUM> of <FIG> and <FIG>. The cellular data radio circuits <NUM> may enable the control circuitry <NUM> to connect to the cellular base station <NUM> via a cellular data network <NUM>, which is capable of enabling bidirectional communications between the control circuitry <NUM> (e.g., the application processors <NUM>) and the cloud servers <NUM> via a cellular data network <NUM> and the cellular base station <NUM>. By way of non-limiting examples, the cellular data network <NUM> may be provided according to <NUM> LTE protocols or <NUM> protocols.

The application processors <NUM> are configured to execute at least a portion of an audio operating system <NUM>. The audio operating system <NUM> is configured to provide an audio interface that is screen-free. The audio interface may, however, be enhanced by headphone buttons of the headphone <NUM> (headphone buttons not shown) and/or haptic outputs (e.g., provided by a vibration motor of the headphones <NUM>, also not shown). The audio interface may include audio inputs and audio outputs of audio I/O <NUM>. By way of non-limiting examples, the audio outputs may include audio alerts (e.g., alarms, "beeps," verbal statements, or combinations thereof), verbally stated questions, verbally stated lists of menu options, other audio outputs, and combinations thereof. Also by way of non-limiting examples, the audio inputs may include spoken commands (e.g., spoken words and/or phrases linked to specific operations to be performed responsive to the spoken words and/or phrases), spoken questions,.

The audio operating system <NUM> is configured to host audio software applications provided by the cloud servers <NUM>. The audio software applications are configured to operate free from graphical user interface elements based at least in part on the audio inputs and the audio outputs (e.g., the audio I/O <NUM>). The audio software applications may also be configured to operate based on headphone buttons and haptic outputs. In some embodiments the audio operating system <NUM> is configured to enable and disable the audio software applications responsive to the audio inputs of the audio I/O <NUM>. In some embodiments the audio operating system <NUM> is configured to provide audio notifications of new audio functional features that are available to be provided via the application processors <NUM>. By way of non-limiting examples, the audio interface may be configured to provide the audio notifications periodically, responsive to availability of the new audio functional features, and/or responsive to the audio inputs.

The cloud servers <NUM> are configured to support the portable electronic accessory <NUM>. The cloud servers <NUM> include one or more network interfaces <NUM> configured to communicate with the portable electronic accessory <NUM> (e.g., via the Internet <NUM>, the cellular base station <NUM>, and the cellular data network <NUM>), one or more processors <NUM> operably coupled to the network interfaces <NUM>, and one or more data storage devices <NUM> operably coupled to the one or more processors <NUM>. In some embodiments operation of the audio operating system <NUM> may be distributed between the application processors <NUM> and the cloud servers <NUM> (e.g., the operating system support engine code <NUM>). In some embodiments the application processors <NUM> are configured to execute at least a portion of the audio operating system <NUM> as a virtual machine to audio operating system code operated by the cloud servers <NUM>.

The data storage devices <NUM> include computer-readable instructions <NUM> stored thereon. The computer-readable instructions <NUM> include software application code <NUM> for the audio software applications to be hosted by the audio operating system <NUM> of the portable electronic accessory <NUM>.

The computer-readable instructions <NUM> also include operating system support engine code <NUM> that, when executed by the processors <NUM>, is configured to support operation of the audio operating system <NUM>. In some embodiments the operating system support engine code <NUM> is configured to instruct the processors <NUM> to support the operation of the audio operating system <NUM> by executing a cloud audio operating system. By way of non-limiting example, the operating system support engine code <NUM> may include a portion of the audio operating system <NUM> (e.g., a cloud audio operating system) and the application processors <NUM> may operate as a virtual machine.

In some embodiments the operating system support engine code <NUM> is configured to instruct the processors <NUM> to provide spatialized audio capabilities. Spatialized audio may be used to accurately present to the headphones <NUM> location cues and sounds within a three-dimensional audio space that humans understand. For example, sounds may be perceived as coming from ahead, behind, left, or right, from nearby or from far in the distance, and from a certain elevation relative to the hearer. Spatialized audio may be used for sightless navigation to locate a position of sounds within the user's audio space. For example, a navigation prompt to "turn left in <NUM> feet" may be presented to the user as coming from the intended direction, faintly at first, and then growing "closer" as the user closes on the point of the turn, at which point the prompt may indicate strongly to "turn left forty-five degrees now," without limitation. The prompt may be presented as positioned strongly on the left side of the audio space of the user. Geolocation and dead reckoning along with further audio prompts may be used to ensure the user is following navigation instructions.

Spatialized audio may also be used to enable an immersive and accurate health and workout experience by positioning environmental sounds accurately in the three-dimensional space perceived by the user. For example, audio of a virtual coach may be presented to be perceived as "walking around" a user during a coaching session and the coach's voice could be presented as coming from in front of or to the side of the user.

In some embodiments the operating system support engine code <NUM> is configured to instruct the processors <NUM> to provide voice printing and bio-credentials for security capabilities. Voice printing may be used as an augmented biosecurity feature to ensure user and device security. Voice printing may be combined with biometrics data to create an extremely secure bio-password that is truly hands-free. By way of non-limiting example, a user may insert a removable control package (e.g., the removable control package <NUM> of <FIG>) into the portable electronic accessory <NUM>, and be automatically validated through his or her bio-credentials.

The computer-readable instructions <NUM> further include audio software application store code <NUM>. The audio software application store code <NUM> is configured to provide the audio software applications responsive to the audio I/O <NUM> at the portable electronic accessory <NUM>. As previously discussed, the audio interface may be configured to provide audio notifications regarding new audio software applications and services periodically, responsive to availability of the new audio functional features, and/or responsive to the audio inputs. As a specific non-limiting example, the user may receive audio notifications of new audio software applications and/or services he or she may be interested in, and can verbally opt in to these audio software applications and services by speaking to the earphone, rather than interacting with a screen. The user may also verbally request "what's new" and receive audio prompts describing audio software applications and/or services and deemed interesting or relevant to the particular user.

In some embodiments the portable electronic accessory <NUM> may include a TWS headphone case and the headphones <NUM> may be TWS headphones. The control circuitry <NUM> is configured to connect to the headphones <NUM> via the wireless PAN network <NUM> (e.g., Bluetooth) to enable communication of audio I/O <NUM> between the control circuitry <NUM> and the headphones <NUM>. One of the wireless PAN network <NUM> lines shown in <FIG> is illustrated using broken lines because in some embodiments only one of the headphone <NUM> may communicate directly with the control circuitry <NUM>. In such embodiments a wireless PAN network <NUM> between the headphones <NUM> may be used to route the audio I/O <NUM> between the control circuitry <NUM> and the other one of the headphones <NUM> that is not directly connected to the control circuitry <NUM> by the wireless PAN network <NUM>. In some embodiments, however, both of the headphone <NUM> may be directly connected to the control circuitry <NUM> using the wireless PAN network <NUM>.

In some embodiments the audio software applications include a community engagement on the go software application. Using a cloud server-based community voice platform, the portable electronic accessory system <NUM> may power a community "chatroom" experience on the go. A real-time cloud hosted chatroom may be initiated using a simple voice command (e.g., of the audio I/O <NUM>). Firmware of the audio operating system <NUM> may engage service in the cloud (e.g., the cloud servers <NUM>). Such community engagement on the go software applications may enable persons (e.g., coaches, leaders) that direct groups of people (e.g., teams) in disparate locations to chat in real-time while coordinating performance of group tasks (e.g., engagements, missions, adventures) on the go and leverage additional data and analytics in real time. Community engagement may be enabled using a hands-free, voice driven voice over internet protocol (VoIP) service resident on the application processors <NUM>. In addition, community engagement on the go software applications may supports an "always on" mode whereby users may simply listen passively or engage at will simply by speaking naturally, similarly to "hanging out" in a physical space, but virtually.

In some embodiments the audio software applications include location intelligence software applications. Location intelligence software applications may, for example, enable cloud data collection and execution of stored plans for adventures (e.g., stored at the portable electronic accessory <NUM> and/or at the cloud servers <NUM>). Location intelligence software applications may also enable tracking of a user of the portable electronic accessory <NUM> and feedback from the user, which may be automatic, human generated, or both. Location intelligence software applications may also enable leaders (e.g., team leaders) to choreograph movement in advance. By way of non-limiting examples, a choreographed movement may include a patrol over a mountain on a certain path or a mountain hike. As a specific, non-limiting example, a choreographed movement may be initiated by a team leader providing a voice command such as "patrol over the mountain on a certain path.

A geolocater (not shown) of the portable electronic accessory <NUM> (e.g., of the control circuitry <NUM>, of the headphones <NUM>, or both) may enable a defined group to track each other and route along a predefined path. Location data may be provided by a global positioning system (GPS) location, wireless networks (e.g., WiFi networks, Bluetooth networks), augmented or deduced (dead) reckoning (e.g., when GPS is unavailable) or combinations thereof. Augmented or deduced reckoning may use integrated motion sensors units (IMUs) such as accelerometers, gyroscopes, a digital compass, other sensors, or combinations thereof. IMUs, or IMUs in combination with GPS tracking, may enable detection of velocity and direction, attitude, sudden stops, impacts, falls, or combinations thereof.

By way of non-limiting example, a location intelligence software application may enable provision of real-time data to the cloud servers <NUM>, which may alert a leader and/or other user if a user has deviated from a predetermined route. Biometric sensor (e.g., as part of the portable electronic accessory <NUM> and/or the headphones <NUM>) may enable activity tracking and prediction (e.g., is the user walking, running, riding, swimming, etc.). Biometric sensors may be configured to detect environmental temperature, body temperature, pulse oximetry, oxygen saturation, heart rate, environmental sounds, other relevant variables, or combinations thereof. Proximity detection and alerts may be enabled using a combination of GPS tracking, embedded radio frequency (RF) signaling (e.g., received signal strength indicators (RSSIs) related to Bluetooth low energy (BLE) links emitted by the portable electronic accessory <NUM> and/or the headphones <NUM>). Proximity detection may be combined with the user's current location, direction, speed, and attitude to determine proximity to other users and/or obstacles, predict possible collisions, and/or provide relevant alerts.

For location intelligence software applications, haptic devices (not shown) and headphone buttons (not shown) in the headphones <NUM> may enable users to "feel" or signal each other without talking. As specific, non-limiting examples, in instances where users are in the dark or operating in a dense landscape, a haptic device (e.g., a vibration motor) in a right (as opposed to left) headphone <NUM> may be driven to vibrate responsive to proximity of another user within ten meters to the right to signal the presence of the other user. Geolocation devices (not shown) of the portable electronic accessory <NUM> and/or the headphones <NUM> may enable alerts of dangers or obstacles in real time.

By way of non-limiting example, for bike riding applications, alerts may be provided when other riders come into proximity, and a lane assist feature indicating that a vehicle is approaching. Also by way of non-limiting example, a six feet proximity alert may be used during the spread of respiratory disease (e.g., COVID-<NUM>). As a further non-limiting example, a team leader may use a headphone button (e.g., a double tap of the headphone button) trigger a haptic signal in other users' headphones (e.g., the headphone <NUM>) if for whatever reason the team leader cannot or does not desire to speak out loud (e.g., alert if there is enemy in the area, or "alert I see a Bear"). As another non-limiting example, a team leader and/or team members could also use a command (e.g., a verbal command) to create a community chatroom to connect all members on the go. In some embodiments, team members, as designated, may listen to other users' environmental sounds using the microphones on the other users' headphones (e.g., the headphones <NUM>), which may be streamed as real-time audio data to the cloud. For example, the team leader may listen to the audio at a particular user's location for clues to current whereabouts or condition of the particular use, or to eavesdrop.

In some embodiments the audio software applications include health and workout intelligence software applications. Health and workout intelligence software applications may enable collection of physical exertion effort data and collection of biometrics data. Health and workout intelligence software applications may also enable analysis of collected data (e.g., physical exertion effort data, biometrics data), and provide downstream assistance. Biometrics data (e.g., heart rate, blood pressure, pulse-ox, etc.) may be collected through the headphones <NUM>, which are connected to the user's ear. Biometrics data may be passed to the cloud servers <NUM> on the go for data collection. Also workout analytics may be collected in real-time and passed to the cloud servers <NUM> for physical and/or athletic evaluation. Automatic audio feedback may be sent to the user in real time through the headphones <NUM>.

A geolocator of the portable electronic accessory <NUM> and/or the headphone <NUM> may enable tracking of user data, user location, and user speed. Data may be collected and stored in an ecosystem with an at-home workout system. With the above-discussed data passed to a coach, a doctor, and/or a leader in real-time via the cloud servers <NUM>, consultation services and feedback may be provided to the user. Users may extend home workout experience from in-home trainers to an on the go experience with real-time coaching through cloud connected teachers. Voice commands from a user may query and leverage coaching and analytics support while on the go.

<FIG> is a block diagram of a cloud-assisted audio system <NUM>, according to some embodiments. The cloud-assisted audio system <NUM> includes one or more cloud servers <NUM> similar to the one or more cloud servers <NUM> of <FIG>, and portable electronic accessories 404a-404d, each of which is similar to the portable electronic accessory <NUM> of <FIG>, the portable electronic accessory <NUM> of <FIG>, or the portable electronic accessory <NUM> of <FIG>. The portable electronic accessories 404a-404d are configured to communication with the cloud servers <NUM> as discussed above for the portable electronic accessory <NUM> and the cloud servers <NUM> of <FIG> (e.g., via cellular data networks, cellular base stations, and the internet). The cloud-assisted audio system <NUM> also includes satellites <NUM> configured to provide geolocation signals <NUM> to enable geolocation and GPS functionality disclosed herein.

As discussed above, various audio software applications and/or other functions of the cloud-assisted audio system <NUM> of <FIG> may involve coordination of various users of portable electronic accessories such as the portable electronic accessories 404a-404d. <FIG> illustrates an example of a network architecture for a cloud-assisted audio system <NUM> that enables such cooperative functions.

<FIG> is a flowchart illustrating a method <NUM> of operating an audio operating system (e.g., the audio operating system <NUM> of <FIG>) for a portable electronic accessory (e.g., the portable electronic accessory <NUM> of <FIG>, the portable electronic accessory <NUM> of <FIG>, the portable electronic accessory <NUM> of <FIG>), according to some embodiments. At operation <NUM> the method <NUM> includes providing an audio interface at the portable electronic accessory. The audio interface is free of graphical user interface elements, according to embodiments disclosed herein. The audio interface includes audio inputs and audio outputs (e.g., the audio I/O <NUM> of <FIG>).

At operation <NUM> the method <NUM> includes executing software application code for audio software applications hosted by the audio operating system. In some embodiments executing the software application code includes executing the software application code by one or more cloud servers (e.g., the cloud servers <NUM> of <FIG>, the cloud servers <NUM> of <FIG>) remote from the portable electronic accessory. In some embodiments executing the software application code includes executing the software application code by one or more application processors (e.g., the application processors <NUM> of <FIG> and <FIG>, the application processors <NUM> of <FIG>) of the portable electronic accessory. In some embodiments executing the software application code includes coordinating activity of the portable electronic accessory with activities of one or more other portable electronic accessories.

At operation <NUM> the method <NUM> includes providing the software application code for use by the portable electronic accessory responsive to the audio inputs. In some embodiments providing the audio interface at the portable electronic accessory includes providing the audio outputs to one or more speakers (e.g., the speakers <NUM> of <FIG> and <FIG>) of one or more headphones (e.g., the headphones <NUM> of <FIG> and <FIG>, the headphones <NUM> of <FIG>) of the portable electronic accessory. In some embodiments providing the audio interface at the portable electronic accessory includes receiving the audio inputs by one or more microphones (e.g., the microphones <NUM> of <FIG> and <FIG>) of the one or more headphones of the portable electronic accessory.

It will be appreciated by those of ordinary skill in the art that functional elements of embodiments disclosed herein (e.g., functions, operations, acts, processes, and/or methods) may be implemented in any suitable hardware, software, firmware, or combinations thereof. <FIG> illustrates non-limiting examples of implementations of functional elements disclosed herein. In some embodiments, some or all portions of the functional elements disclosed herein may be performed by hardware specially configured for carrying out the functional elements.

<FIG> is a block diagram of circuitry <NUM> that, in some embodiments, may be used to implement various functions, operations, acts, processes, and/or methods disclosed herein. The circuitry <NUM> includes one or more processors <NUM> (sometimes referred to herein as "processors <NUM>") operably coupled to one or more data storage devices (sometimes referred to herein as "storage <NUM>"). The storage <NUM> includes machine executable code <NUM> stored thereon and the processors <NUM> include logic circuitry <NUM>. The machine executable code <NUM> includes information describing functional elements that may be implemented by (e.g., performed by) the logic circuitry <NUM>. The logic circuitry <NUM> is adapted to implement (e.g., perform) the functional elements described by the machine executable code <NUM>. The circuitry <NUM>, when executing the functional elements described by the machine executable code <NUM>, should be considered as special purpose hardware configured for carrying out functional elements disclosed herein. In some embodiments the processors <NUM> may be configured to perform the functional elements described by the machine executable code <NUM> sequentially, concurrently (e.g., on one or more different hardware platforms), or in one or more parallel process streams.

When implemented by logic circuitry <NUM> of the processors <NUM>, the machine executable code <NUM> is configured to adapt the processors <NUM> to perform operations of embodiments disclosed herein. For example, the machine executable code <NUM> may be configured to adapt the processors <NUM> to perform at least a portion of the method <NUM> of <FIG>. As another example, the machine executable code <NUM> may be configured to adapt the processors <NUM> to perform at least a portion or a totality of the operations discussed for the application processors <NUM> of <FIG> and <FIG>, the cellular data radio circuits <NUM> of <FIG> and <FIG>, the PAN radio circuits <NUM> of <FIG> and <FIG>, the PAN peripheral circuits <NUM> of <FIG> and <FIG>, the power circuitry <NUM> of <FIG> and <FIG>, the control circuitry <NUM> of <FIG>, the application processors <NUM> of <FIG>, the cellular data radio circuits <NUM> of <FIG>, and/or the cloud servers <NUM> of <FIG>.

The processors <NUM> may include a general purpose processor, a special purpose processor, a central processing unit (CPU), a microcontroller, a programmable logic controller (PLC), 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, other programmable device, or any combination thereof designed to perform the functions disclosed herein. A general-purpose computer including a processor is considered a special-purpose computer while the general-purpose computer is configured to execute functional elements corresponding to the machine executable code <NUM> (e.g., software code, firmware code, hardware descriptions) related to embodiments of the present disclosure. It is noted that a general-purpose processor (may also be referred to herein as a host processor or simply a host) may be a microprocessor, but in the alternative, the processors <NUM> may include any conventional processor, controller, microcontroller, or state machine. The processors <NUM> may also be implemented as a combination of computing devices, such as 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.

In some embodiments the storage <NUM> includes volatile data storage (e.g., random-access memory (RAM)), non-volatile data storage (e.g., Flash memory, a hard disc drive, a solid state drive, erasable programmable read-only memory (EPROM), etc.). In some embodiments the processors <NUM> and the storage <NUM> may be implemented into a single device (e.g., a semiconductor device product, a system on chip (SOC), etc.). In some embodiments the processors <NUM> and the storage <NUM> may be implemented into separate devices.

In some embodiments the machine executable code <NUM> may include computer-readable instructions (e.g., software code, firmware code). By way of non-limiting example, the computer-readable instructions may be stored by the storage <NUM>, accessed directly by the processors <NUM>, and executed by the processors <NUM> using at least the logic circuitry <NUM>. Also by way of non-limiting example, the computer-readable instructions may be stored on the storage <NUM>, transferred to a memory device (not shown) for execution, and executed by the processors <NUM> using at least the logic circuitry <NUM>. Accordingly, in some embodiments the logic circuitry <NUM> includes electrically configurable logic circuitry <NUM>.

In some embodiments the machine executable code <NUM> may describe hardware (e.g., circuitry) to be implemented in the logic circuitry <NUM> to perform the functional elements. This hardware may be described at any of a variety of levels of abstraction, from low-level transistor layouts to high-level description languages. At a high-level of abstraction, a hardware description language (HDL) such as an IEEE Standard hardware description language (HDL) may be used. By way of non-limiting examples, Verilog™, SystemVerilog™ or very large scale integration (VLSI) hardware description language (VHDL™) may be used.

HDL descriptions may be converted into descriptions at any of numerous other levels of abstraction as desired. As a non-limiting example, a high-level description can be converted to a logic-level description such as a register-transfer language (RTL), a gate-level (GL) description, a layout-level description, or a mask-level description. As a non-limiting example, micro-operations to be performed by hardware logic circuits (e.g., gates, flip-flops, registers, without limitation) of the logic circuitry <NUM> may be described in a RTL and then converted by a synthesis tool into a GL description, and the GL description may be converted by a placement and routing tool into a layout-level description that corresponds to a physical layout of an integrated circuit of a programmable logic device, discrete gate or transistor logic, discrete hardware components, or combinations thereof. Accordingly, in some embodiments the machine executable code <NUM> may include an HDL, an RTL, a GL description, a mask level description, other hardware description, or any combination thereof.

In embodiments where the machine executable code <NUM> includes a hardware description (at any level of abstraction), a system (not shown, but including the storage <NUM>) may be configured to implement the hardware description described by the machine executable code <NUM>. By way of non-limiting example, the processors <NUM> may include a programmable logic device (e.g., an FPGA or a PLC) and the logic circuitry <NUM> may be electrically controlled to implement circuitry corresponding to the hardware description into the logic circuitry <NUM>. Also by way of non-limiting example, the logic circuitry <NUM> may include hard-wired logic manufactured by a manufacturing system (not shown, but including the storage <NUM>) according to the hardware description of the machine executable code <NUM>.

Claim 1:
A portable electronic accessory (<NUM>, <NUM>, <NUM>), comprising:
one or more microphones (<NUM>) configured to receive audio inputs;
one or more speakers (<NUM>) configured to provide audio outputs;
wherein the portable electronic accessory (<NUM>, <NUM>, <NUM>) includes one or more headphones (<NUM>, <NUM>) including the one or more speakers (<NUM>) and the one or more microphones (<NUM>);
wherein the one or more headphones (<NUM>, <NUM>) include truly wireless stereo (TWS) headphones;
control circuitry (<NUM>, <NUM>) operably coupled to the one or more speakers (<NUM>) and the one or more microphones (<NUM>),
wherein the portable electronic accessory (<NUM>, <NUM>, <NUM>) includes a TWS headphone charging case including the control circuitry (<NUM>, <NUM>), the portable electronic accessory being characterised in that the control circuitry (<NUM>, <NUM>) is implemented as a removable control package that is removable from the TWS headphone charging case;
the control circuitry (<NUM>, <NUM>) including:
one or more cellular data radio circuits (<NUM>) configured to communicate with one or more cloud servers (<NUM>, <NUM>) through a cellular data network (<NUM>); and
one or more application processors (<NUM>, <NUM>) configured to execute at least a portion of an audio operating system (<NUM>), the audio operating system (<NUM>) configured to host audio software applications provided by the one or more cloud servers (<NUM>, <NUM>), the audio software applications configured to operate free from graphical user interface elements based at least in part on the audio inputs and the audio outputs.