Wireless accessory notification

Abstract

The invention relates to wireless accessory notification. Systems, methods, devices, and non-transitory computer-readable storage media are disclosed for: identifying, by a processor of a wireless device coupled to a charging cartridge, an enable command received from the charging cartridge; and transmitting, by the processor, a notification signal based on the enable command, the notification signal including information related to identification of the wireless device.

Description

[0001] This application is a divisional application of the invention patent application with application date of April 28, 2022, application number 202210469817.8, and invention name “Wireless Accessory Notification”. Technical Field

[0002] The present disclosure generally relates to transmitting advertisements from wireless devices. Background Art

[0003] When the wireless accessory is in active use (e.g., powered on and being used by a user of the wireless accessory and / or the wireless device), the wireless accessory (e.g., wireless earbuds, headphones, headsets, etc.) may periodically transmit status notifications to a paired wireless device (e.g., a personal digital assistant (PDA), mobile phone, tablet computer, etc.). These status notifications may allow the user to locate the wireless accessory, or monitor status such as the battery status of the wireless accessory. Summary of the invention

[0004] Systems, methods, devices, and non-transitory computer-readable storage media for status notifications from a wireless accessory, such as an earbud, are disclosed.

[0005] In some specific implementations, the computer-implemented method includes: identifying, by a processor of a wireless device coupled to a charging box, an enablement command received from a charging box; and transmitting, by the processor, a notification signal based on the enablement command, the notification signal including information related to the identification of the wireless device.

[0006] In some specific implementations, the computer-implemented method includes: a processor of a charging box coupled to one or more wireless devices identifies that an interval timer has expired; the processor identifies a first wireless device from the one or more wireless devices; and the processor transmits an enable command to the first wireless device based on the interval timer, so that the first wireless device transmits a notification signal related to the identification of the first wireless device.

[0007] In some specific implementations, a computer-implemented method includes: identifying, by a processor of a wireless device coupled to a charging case, an enable command received from a charging case, wherein the wireless device belongs to a pair of wireless devices including the wireless device and another wireless device; and transmitting, by the processor in response to identifying the enable command, a notification signal including information related to a status of the wireless device and a status of the other wireless device.

[0008] The foregoing embodiments and other embodiments may each optionally include one or more of the following features, alone or in combination. The method may include determining, by the processor, that the processor has received a connection with a second wireless device; and transmitting, by the processor, at least in part in response to determining that the processor has received a connection with the second wireless device, a wait command to the charging case to cause the charging case to wait for a disable command to be sent to the processor of the wireless device. Determining that the processor has received a connection with the second wireless device may include: determining, by the processor, that the processor has received a connection with the second wireless device while the processor is transmitting a notification signal.

[0009] In some implementations, the notification signal may be a Bluetooth signal. The method may include identifying, by a processor, a power signal received from the charging case, the reception of the power signal occurring substantially simultaneously with the transmission of the notification signal. The enable command may be at a first power level. The power signal may be at a second power level different from the first power level. The enable command may be within a first time period. The power signal may be within a second time period different from the first time period. The first time period may be one second. The second time period may be three seconds.

[0010] In some implementations, the method may include, by the processor, identifying a disable command received from the charging case; and, by the processor, stopping transmission of a notification signal based on the disable command. The method may include, before identifying an enable command, identifying, by the processor, a wake-up command received from the charging case; and, by the processor, entering a wake-up operation state based on the wake-up command, the wake-up operation state causing the processor to monitor for an enable command.

[0011] In some implementations, the method may include, after transmitting the notification signal, recognizing, by the processor, a sleep command received from the charging case; and entering, by the processor, a sleep operating state based on the sleep command, the sleep operating state causing the processor to skip monitoring for an enable command. Entering the sleep operating state may cause the processor to shut down.

[0012] In some implementations, the method may include identifying, by the processor, that a notification duration timer has expired; and, in response, at least in part, to determining that the notification duration timer has expired, transmitting, by the processor, a disable command to the first wireless device to stop transmitting notification signals by the first wireless device. The method may include identifying, by the processor, that a total duration timer has expired; and, in response, at least in part, to identifying that the total duration has expired, stopping, by the processor, an interval timer and a total duration timer.

[0013] In some implementations, the one or more wireless devices may include two or more wireless devices, the two or more wireless devices including a first wireless device and a second wireless device. The method may include determining, by a processor, that the first wireless device and the second wireless device are not coupled; and transmitting, by the processor, at least in part in response to determining that the first wireless device and the second wireless device are not coupled, a second enable command to the second wireless device to cause the second wireless device to transmit a second notification signal associated with a second identification of the second wireless device.

[0014] In some implementations, the method may include, before transmitting the enable command, transmitting, by the processor, a wake-up command to the first wireless device to cause the first wireless device to enter a wake-up operating state. The method may include, after transmitting the notification signal by the first wireless device, transmitting, by the processor, a sleep command to the first wireless device to cause the first wireless device to enter a sleep operating state.

[0015] In some implementations, the one or more wireless devices may include two or more wireless devices. Identifying the first wireless device may include identifying, by the processor, a power level of a corresponding wireless device in the two or more wireless devices. Identifying the first wireless device may include identifying, by the processor, that the first wireless device is coupled to a charging box, while another wireless device in the two or more wireless devices is not coupled to the charging box. Identifying the first wireless device may include identifying, by the processor, which wireless device in the two or more wireless devices transmitted a previous notification signal. The notification signal may include a first portion related to a state of the wireless device and a second portion related to a state of another wireless device.

[0016] In some implementations, the first portion may have a length of one bit. The information related to the state of the wireless device may include information related to whether the wireless device is coupled to another wireless device. The information related to the state of the other wireless device may indicate that when the wireless device is not coupled to the other wireless device, the other wireless device is not in a charging case with the wireless device.

[0017] In some implementations, information related to the state of the wireless device may include information related to whether the wireless device is coupled to a charging case. Information related to the state of another wireless device may include information related to identification of the other wireless device. Identification may indicate whether the other wireless device is coupled to a charging case. Information related to the state of the wireless device or the state of another wireless device may include an indication of whether the wireless device and the other wireless device are wirelessly communicatively coupled to each other.

[0018] Details of the disclosed implementations are shown in the following drawings and detailed description.Other features, objects, and advantages will be apparent from the description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 is an example of a wireless system including a wireless accessory according to various implementations.

[0020] Figure 2 is an exemplary block diagram of a wireless system including a wireless accessory according to various implementations.

[0021] Figure 3 is an example of a process flow for wireless accessory notifications according to various implementations.

[0022] Figure 4 It is implemented according to various Figure 3 Example of the continuation of the processing flow.

[0023] Figure 5 Depicted are examples of power usage of a wireless accessory during notifications according to various implementations.

[0024] Figure 6 Exemplary techniques related to wireless accessory notifications according to various implementations.

[0025] Figure 7 are alternative exemplary techniques related to wireless accessory notifications according to various implementations.

[0026] Figure 8 are alternative exemplary techniques related to wireless accessory notifications according to various implementations.

[0027] Fig. 9 is an exemplary block diagram of a wireless accessory architecture according to various implementations. DETAILED DESCRIPTION

[0028] As previously noted, a wireless accessory (e.g., wireless earbuds, headphones, headsets, etc.) may periodically transmit status notifications to a paired wireless device (e.g., a PDA, mobile phone, tablet computer, etc.) when the wireless accessory is in an active use state (e.g., powered on and being used by a user of the wireless accessory and / or the wireless device). These status notifications may allow a user to locate the wireless accessory, or monitor status such as the battery status of the wireless accessory. For example, if a user has a mobile device that is communicatively coupled to the wireless accessory, the user may be able to use the mobile device to locate, control, or monitor the wireless accessory based on the status notifications by receiving the status notifications by the mobile device, or by receiving the status notifications from a different mobile device that can then forward the received information to the user's mobile device.

[0029] However, in some implementations, the wireless accessory may not be configured to transmit such notifications in certain situations. For example, in the case of earbuds, when the earbuds are in a charging case with a closed lid, sometimes the earbuds may not be configured to transmit status notifications. For example, the earbuds may be in a lower power or sleep mode, in which case they may not transmit status notifications.

[0030] Implementations herein address the above situations. Specifically, implementations herein relate to status notifications that may be provided by one or more wireless accessories, such as earbuds, when the wireless accessory is in a box with a lid closed, such as when the wireless accessory is not in active use. Such techniques may be referred to herein as "notification in box" techniques. Additionally, in some implementations, the status notification may include information related to both earbuds in a pair of earbuds. In some implementations, the information may be different for each earbud.

[0031] In some implementations, if the wireless accessory consists of two physically separate parts, such as two earbuds, each of the earbuds may sometimes be in a different position from the other. In these implementations, it may be desirable for the status notification to include information related to both earbuds. The information for one earbud may be different from the information for the other earbud, for example, because the earbuds are in different physical positions.

[0032] Figure 1 is an example of a wireless system including wireless accessories according to various implementations. System 100 includes wireless device 105; wireless accessory devices 110a and 110b, collectively referred to as wireless accessory devices 110; and case 115 for wireless accessory devices 110.

[0033] The wireless accessory device 110 can be a device configured to communicate with a wireless device such as the wireless device 105 directly or indirectly (e.g., through another device or computer) over a wireless network or a peer-to-peer communication link. Some examples of wireless accessory devices include, but are not limited to, wireless earbuds, headphones, headsets, and other wearable devices, such as smart watches, fitness bands, optical head-mounted displays, game controllers, remote controls, smart phones. In some implementations, the wireless accessory device 110 may be ... in accordance with, for example, a wireless technology standard such as Bluetooth. TM , the wireless accessory device 110 can be "paired" with the wireless device 105. It can be seen that the wireless accessory device 110 can include two separate physical elements, such as 110a and 110b, for example, a left earbud and a right earbud. In some implementations, the wireless accessory device 110 can include more or fewer physical elements. For example, the wireless accessory device can include one physical element or three or more physical elements.

[0034] Some examples of wireless networks include wireless local area networks (WLANs), such as the Internet, and wireless personal area networks (WPANs). Some examples of communication technologies include any suitable IEEE 802.xx technology, including but not limited to Wi-Fi, Ultra Wideband, and Bluetooth. TM .

[0035] The wireless device 105 may be an electronic device capable of communicating with the wireless accessory device 110, such as a device including a wireless transceiver chip. The wireless device 105 includes at least one microphone or other sound transducer; a display or other output device, such as an audio output device, to assist a user in locating the wireless accessory device; or both. Some examples of the wireless device 105 include, but are not limited to, a smart phone, a tablet computer, a notebook computer, a wearable computer such as a smart watch, etc.

[0036] As can be seen, the box 115 may include a box body 115b, a box cover 115a, and a cavity 115c in which the wireless accessory device 110 may be placed. Specifically, the box body 115b may include one or more processors, storage media, user interactive elements (e.g., buttons or user signals such as lights), etc.

[0037] The case body 115b may further include one or more contacts within the cavity 115c. In a specific implementation, the wireless accessory device 110 may be placed within the cavity 115c so that they are physically coupled to the contacts. The contacts may provide power to one or both of the wireless accessory devices 110a and 110b, such as recharging. In some specific implementations, the case body 115b may be configured for some other charging technology, such as inductive charging. In some specific implementations, the case 115 may be configured to not charge the wireless accessory device 110 until the lid 115a of the case 115 is closed and the wireless accessory device 110 is located in the cavity 115c.

[0038] Figure 2 is an exemplary block diagram of a wireless system 200 including a wireless accessory according to various implementations. Figure 2 In other figures of this document, the wireless accessory is depicted and discussed as a wireless earbud 210, which can be similar to one or both of wireless accessories 110a and 110b. However, it should be understood that the concepts of this document can be applied to other specific implementations, where the wireless accessory is a headset, headphones, or some other type of wireless accessory.

[0039] Wireless earbuds 210, such as headphones positioned directly in a user's ears, may include a processor 240, a physical port 235, a user input / output (I / O) 225, a wireless I / O 230 (e.g., such as a Bluetooth TMtransceiver), memory 245, speaker 250, battery 255 and one or more sensors 260.

[0040] The processor 240 may be a processor such as a central processing unit (CPU), a general purpose processing unit (GPU), one or more processor cores, an integrated circuit (IC), an application specific IC (ASIC), or some other type of logic or controller operable to control the operation of the wireless earbud 210.

[0041] The port 235 can be a physical or wired connection that allows physical coupling and exchange of electrical signals between the wireless earbud 210 and a corresponding port 203 in or on the charging case 215 when the wireless earbud 210 is physically coupled to the case 215, for example, when the wireless earbud is positioned in the cavity 115c and the lid 115a is closed. In specific implementations, the port 235 can be used to charge the wireless earbud 210; exchange data with the case 215; or both. For example, some specific implementations of the port 235 can allow data to be exchanged between the processor 240 of the wireless earbud 210 and the processor 218 of the case 215. In some specific implementations, the port 235 can be coupled to the battery 255 of the wireless earbud 210 and configured to receive power from the case 215, which can then be provided to the battery 255. The battery 255 can be, for example, a lithium-ion battery or some other type of battery.

[0042] The wireless I / O 230 (which may also be referred to as a wireless transceiver) may be configured to support or facilitate short-range wireless communications (e.g., Bluetooth®) between the wireless earbuds 210 and a wireless device such as the wireless device 105. TM or some other short-range communication protocol). The wireless I / O or transceiver 230 enables the wireless earbuds 210 to communicate wirelessly with the box 215 once a channel for wireless communication has been established between the two.

[0043] The memory 245 may store firmware for operating the wireless earbuds 210, as well as data for coupling with other wireless earbuds and for pairing the wireless earbuds 210 with wireless mobile devices. The memory 245 may be, for example, non-volatile memory (NVM), flash memory, or some other type or kind of memory.

[0044] In some implementations, the wireless earbuds 210 may further include one or more speakers 250 that may be configured to produce sound. Specifically, the speakers 250 may be configured to play audio, such as music, podcasts, voice communications, or some other type of audio. In some implementations, the earbuds 210 may include a single speaker 250, while in other implementations, the earbuds 210 may include various speakers tuned to different frequencies (e.g., a mid-range speaker, a high-frequency speaker, and a low-frequency range speaker).

[0045] The wireless earbuds 210 may further include a user I / O 225. The user I / O 225 may include one or more elements for user input, such as buttons, switches, knobs, etc. The user I / O 225 may further include one or more user output elements, such as light, tactile feedback, or some other type of output element.

[0046] The wireless earbud 210 may further include one or more sensors 260 , such as an accelerometer or an in-ear sensor, configured to identify the position, orientation, or movement of the wireless earbud 210 .

[0047] The wireless system 200 may further include a box 215, which may be similar to Figure 1 115. In other implementations, the box 215 can be a docking station or some other type of accessory or electronic device. The box 215 can include the port 203, the battery 204, the processor 218, the user I / O 205, and the memory 220, which can be similar to the port 235, the battery 255, the processor 240, the user I / O 225, and the memory 245, respectively.

[0048] Figure 3 315 and earbud 310, which can be similar to case 115 or 215 and wireless accessory 110a or wireless earbud 210, respectively. The communication can be performed by signals passed between, for example, ports 203 and 235. The communication can facilitate in-box notifications from earbud 310.

[0049] When the earbud 310 is placed in the box 315 and recognized by the box 315, the process flow begins at 303. For example, the earbud 310 can be placed in one of the cavities 115c. In some specific implementations, the earbud 310 can be coupled to the box 315 in another way. The box 315 can identify the earbud 310 for the in-box notification technology based on multiple factors. For example, the earbuds 310 can be identified based on the order in which they are placed in the box 315, for example, always selecting the first or last earbud 310 to be placed in the box 315. In some specific implementations, the earbud 310 can be identified based on which earbud in the earbud pair previously participated in the in-box notification technology, for example, if the "left" earbud previously performed the in-box notification, the "right" earbud can be selected, or vice versa. In some specific implementations, the earbud 310 can be identified based on the power level of the two earbuds of a pair of earbuds, respectively, for example, the earbud with the highest power can be selected. Other criteria may exist in other specific implementations.

[0050] Then the sleep timer is started at 305. Specifically, Figure 3 As shown, the sleep timer can be initiated by a processor such as the processor 240 of the wireless earbud 310. Generally speaking, the sleep timer can be a timer that indicates how long the earbud 310 should remain in the case 315 in the awake state of operation before entering the sleep state of operation. The sleep state of operation can be defined by characteristics such as reduced power consumption, extended time between processor activities, reduced signaling, or a combination of these. It should be noted that while the sleep timer initiated at 305 is depicted as an activity of the earbud 310, in some specific implementations, the sleep timer can be additionally or alternatively run, monitored, or maintained by the case 315, for example, a processor such as the processor 218.

[0051] The box 315 may then transmit a notification support query at 306. Specifically, the notification support query may be a message that queries whether the earbud 310 supports the in-box notification technology as described herein. The earbud 310 may respond with a notification support response 309 that includes a bit or some other indicator that the earbud 310 supports the notification technology described herein (e.g., in-box notification technology).

[0052] After the case confirms that the earbud 310 supports the in-box notification technology, the case 315 can start a total duration timer at 312. The total duration timer can be a timer that indicates the total length of time for the in-box notification technology before instructing the earbud 310 not to perform additional notifications. In some implementations, the total duration timer can have a length of between approximately sixteen hours and six months, specifically between sixteen hours and twenty-four hours, and more specifically twenty-four hours.

[0053] The box 315 may then send a time query to the earbud 310 at 316. The time query may be, for example, a query to coordinate the internal clocks of both the box 315 and the earbud 310, such as by comparing the two clocks to Coordinated Universal Time (UTC) or some other time. In some implementations, the time query may include an indication of the internal clock of the box 315. In some implementations, the time query may include a request for the earbud 310 to provide an indication of its internal clock. In response, the earbud 310 provides a time response at 318, which may confirm the information provided by the box 315 and / or include an indication of the internal clock of the earbud 310.

[0054] The lid of the case 315 (e.g., lid 115a) may be closed, which may initiate a power reduction procedure for the earbud 310. The power reduction procedure may be a procedure by which the operation of the state of the earbud 310 is changed to a reduced power operating state. In the reduced power operating state, the earbud 310 may, for example, use less power, recharge the battery of the earbud 310 from the battery of the case, or a combination of these.

[0055] Specifically, when the lid is closed at 321, the case 315 can transmit a radio disable command to the earbud 310 at 324. The radio disable command can be a command to cause the earbud 310 to power down, turn off, or otherwise stop the operation of the earbud's internal radio, such as the wireless I / O 230. The earbud 310 can respond with a radio disable response 327, which can include, for example, acknowledging the radio disable command at 324. The earbud's radio is then disabled at 330.

[0056] The box may then transmit a reboot command to the earbud 310 at 333. The reboot command may be a command that causes the earbud 310 to reboot itself, such as by power cycling, at 336. Such a reboot may, for example, clear various temporary data of the earbud (e.g., some encryption keys), clear the earbud's cache, or both.

[0057] The wireless system may then begin a notification loop at 339. Generally speaking, the notification loop at 339 may be a loop in which the earbud 310 performs in-box notifications.

[0058] The box 315 and / or the earbud 310 may additionally start an interval timer. Generally speaking, it may be desirable for in-box notifications to occur periodically according to a predictable schedule. An interval timer may refer to a timer that indicates how often an in-box notification should occur. In some implementations, the interval timer may be, for example, about one minute, however, it should be understood that in other implementations, the interval timer may be longer or shorter, depending on factors such as battery life, specific usage scenarios, and the like.

[0059] Initially, the notification loop may include sleeping for a specific time at 342. Figure 3 As depicted, the specific time is the difference between the interval timer and the notification duration timer as discussed above. The notification duration timer may refer to a timer that monitors how long a status notification should occur. In some implementations, the notification duration timer may be approximately three seconds long, while in other implementations, the notification duration may be longer or shorter, again depending on factors such as battery life, specific usage scenarios, etc. In some implementations, hibernation may further take into account the time required for the notification enabling procedures described at 345 and 348, the notification disabling procedures described at 357 and 360, or both, described in more detail below.

[0060] At the end of hibernation, the box 315 can send a notification enable command at 345. The notification enable command can be, for example, a one second long power pulse transmitted to the earbud 310. In some implementations, the notification enable command can be a set bit or some other command in a message provided by the box 315 to the earbud 310. The earbud 310 can recognize the notification enable command and send a notification enable response 348, which acknowledges receipt of the command at 345.

[0061] Based on the notification enablement command 354, the earbud 310 may transmit a status notification at 354. The status notification may include information such as the location of the earbud 310, an identifier of the earbud 310, a power level of the earbud 310, some other status indicator of the earbud 310, or a combination of two or more of these.

[0062] In some implementations, when the earbud 310 transmits the status notification at 354, a companion device (e.g., a wireless device such as a smart phone or smart watch) can transmit information about the earbud 310. For example, the companion device can transmit data indicating the location of the earbud 310, some other status indicator of the earbud 310, or both. The companion device can transmit data that is not included in the status notification.

[0063] Substantially simultaneously with the notification at 354, the box 315 may monitor the notification duration timer at 351. As noted above, the notification duration timer at 351 may be approximately three seconds long. It should be understood that in some implementations not shown, the earbud 310 may additionally or alternatively monitor the notification duration timer.

[0064] After the notification duration timer at 351 expires, the box 315 can send a notification disable command at 357, which can include an indication that the earbud 310 is to stop notifications according to a specific power level, a specific bit, or some other indication. Based on the command at 357, the earbud 310 can transmit a notification disable response at 360, which confirms the disable command at 357.

[0065] Process flow then loops back to element 339 at 363 until the sleep timer started at 305 expires. In some implementations, the earbud used to transmit the status notification at 354 may be switched when process flow loops back to 339 at 363, while in other implementations, the same earbud may be used for two or more consecutive cycles.

[0066] After the sleep timer expires, the earbud 310 may enter a sleep state of operation at 366. In the sleep state of operation, one or more processes or elements of the earbud 310 may be further powered down so that they consume less power, e.g., shut down, monitor for signals at longer periodic intervals, or both. The process may then continue to 369. Figure 4 .

[0067] In some implementations, when the earbud 310 is transmitting the notification signal, a wireless device, such as the wireless device 105, can send a signal to the earbud 310. This can occur when the wireless device attempts to determine the location of the earbud 310, send audio content to the earbud 310, or both.

[0068] When the earbud 310 receives a signal from the wireless device, for example, when the earbud 310 is transmitting a notification signal, the earbud 310 may transmit a signal to the charging box 315 indicating that the charging box should wait to send a disable command to the earbud 310. For example, the earbud 310 may monitor for signals from, for example, a connection with a device. This monitoring may occur when the earbud 310 is transmitting a notification signal. In response to determining that the earbud receives a connection with the wireless device, the earbud 310 may send a wait command to the charging box 315 to cause the charging box 315 to wait to send a disable command to the earbud 310.

[0069] When the connection with the wireless device is terminated, the earbud 310 may send a stop waiting command to the charging case 315 after a predetermined period of time or at another appropriate time. Receiving the stop waiting command may cause the charging case 315 to continue its previous operation, for example, continuing any timers that were paused based on receiving the waiting command. This may enable the wireless device to determine the location of the earbud 310, such as an approximate location, in the following situations: when the time required exceeds the time that the charging case 315 would normally allow, for example, when the user of the wireless device needs to find the earbud 310 and the wireless device only provides the user with directional information to determine the location of the earbud 310.

[0070] Figure 4 It is implemented according to various Figure 3 Specifically, Figure 4 Depicts that once the earbud enters the sleep operating state at 366, it may be considered Figure 3The continuation of the processing flow.

[0071] Combination box 415 and earplug 410 depicts Figure 4 , which can be similar to Figure 3 The processing flow may start at 403 with the initiation of a notification loop and then sleep at 406, which may be similar to Figure 3 Elements 339 and 342.

[0072] After the sleep at 406, the box 415 can transmit a wake-up command to the earbud 410 at 409. The wake-up command at 409 can be a command to cause the earbud 410 to exit the sleep operating state and enter the wake-up operating state. The wake-up operating state can be an operating state in which the earbud 410 is configured to transmit, receive, monitor, or a combination of these for one or more wireless signals such as status notifications. The box 415 can then wait for the duration of the earbud 410 wake-up procedure at 412, and the earbud enters the wake-up operating state at 414.

[0073] The processing flow may then include Figure 4 Depicted are elements 416, 418, 421, 424, 427, and 430, which may be similar to elements 345, 348, 351, 354, 357, and 360, respectively, as discussed above. To avoid redundancy in this discussion, these elements will not be described again.

[0074] After the notifications at 427 and 430 are disabled, the box 415 may send a sleep command to the earbud at 410, which is acknowledged in the response at 436. The sleep command may be a command to cause the earbud to enter a sleep state of operation at 439, similar to element 366 as described above.

[0075] Process flow may then return to element 412 until the total duration timer started at element 312 expires at 445. Once the total duration timer expires at 445, the case 415 may likewise enter a sleep state of operation 448 and direct the earbuds to not continue periodic status notifications. In this way, the case 415 and / or the earbuds 410 may not drain their respective batteries or perform unnecessary power cycles due to status notifications.

[0076] It should be understood that Figure 3 and Figure 4 The description is intended as an example, and other implementations may vary. For example, certain elements may occur in a different order than depicted (e.g., in reverse order or simultaneously). In some implementations, an element described as being transmitted or initiated by the box 315 / 415 may be initiated by the earbud 310 / 410 and confirmed by the box, or vice versa.

[0077] In some implementations, the timers, such as interval timers, notification duration timers, total duration timers, sleep timers, etc., may be started at different points than those depicted in the process flow, or may be different from the above timers. For example, the "notification enable command 345" may be as follows in combination with Figure 5 Thus, in this implementation, the sleep at 342 may be the difference between the interval timer and [notification duration timer + one second]. In some implementations, this additional one second time interval may be built into or otherwise be part of the interval timer or notification duration timer. Similarly, the timer may be modified to account for the wake-up command at 409. In general, it should be understood that the exact organization of the process flow may vary in different implementations, and Figure 3 and Figure 4 The examples are intended as high-level examples of the concepts described herein. Other variations are possible in other implementations.

[0078] Figure 5 Depicted are examples of power usage of a wireless accessory (e.g., an earbud such as earbud 310 or 410) during a notification cycle according to various implementations. Specifically, Figure 5 The X-axis depicts time, and the Y-axis depicts power level. It should be understood that Figure 5 It is for discussion purposes only and is not intended to be drawn to scale.

[0079] For the purposes of this discussion, assume that the notification loop cycles once every minute. That is, the interval timer is one minute long. Similarly, assume that the status notification from the earbud is approximately three seconds long. That is, the notification duration timer is three seconds long.

[0080] like Figure 5 As can be seen in FIG. 5 , the earbud may be at relatively low power at 505. For example, the earbud may consume approximately 30 microwatts (μW) of power from the case. This power consumption may be for the purpose of maintaining or recharging the battery of the earbud. Generally speaking, this stage may be consistent with the sleep described at 342 and 406, may last approximately 56 seconds, or both.

[0081] The case may then provide at 510 a notification enable command as described at 345 or 416. Generally, the command may take the form of a relatively high power pulse supplied from the case 315 / 415 to the earbud 310 / 410. In some implementations, the command at 510 may last for about one second, have a power of about 25 milliwatts (mW), or both, but in other implementations, the duration and / or power of the command may be greater or less than the duration and / or power. During the wake-up enable command at 510, earbud charging may be disabled.

[0082] The earbud 310 / 410 may then perform a status notification at 515 as described at 354 or 424. The notification may last for approximately three seconds, for example, the duration of the notification duration timer. In some implementations, the notification may take the form of a single transmission. In some implementations, the notification may take the form of repeated periodic transmissions during predetermined, for example, three second intervals. After the status notification at 515, the process may then loop as described above in connection with element 363 or 445.

[0083] As noted above, in some implementations, status notifications may be transmitted by only a single earbud in one or more, such as a pair of earbuds. However, two earbuds in a group of two or more, such as a pair of earbuds, may have different states from each other. For example, in some implementations, one earbud (e.g., wireless accessory 110a) may be in a box (e.g., box 115), while the other earbud (e.g., wireless accessory 110b) may not be in the box. In some implementations, the earbuds may be communicatively coupled to each other. In some implementations, the earbuds may not be communicatively coupled to each other. In some implementations, the lid of the box (e.g., lid 115a) may be open. In some implementations, the lid may be closed.

[0084] It may be desirable for the status notification to indicate one or more changes in the above situations. Table 1 below describes an example of information that may be included in the status notification. In this example, the status notification may be represented by two bits. In this example, it may be assumed that the status notification is being transmitted by the left earbud. The first bit (bit-0) may include information related to the right earbud. The second bit (bit-1) may include information related to the status of the transmission, for example, the left earbud. Specifically, bit-1 may include information related to whether the transmitting earbud is in the box.

[0085] It should be understood that Table 1 below is intended to illustrate how different bits may be set in different scenarios. However, Table 1 is not intended to illustrate the relative positions of bits in a transmission. In other words, bit-0 may appear before bit-1 in a transmission, or vice versa. In some implementations, the relative positions of bit 0 and bit 1 may be based on factors such as which earbud is transmitting the status notification.

[0086]

[0087]

[0088] Figure 6 The invention is an exemplary technique related to wireless accessory notification according to various specific implementations. Specifically, the technique is a technique that can be performed by a wireless accessory such as a wireless earbud 210 / 310 / 410 (and more specifically, the processor 240 of the wireless earbud 210).

[0089] The technique may include recognizing an enable command received from a charging case, such as case 215, at 605. The enable command may be, for example, a notification enable command discussed in connection with element 345 or 416. The technique also includes transmitting a notification signal based on the enable command at 610, the notification signal including information related to the identification of the earbud. The notification signal may be, for example, a status notification discussed above in connection with element 354 or 424 or Table 1.

[0090] Figure 7 is an alternative exemplary technique related to wireless accessory notifications according to various specific implementations. Specifically, the technique is a technique that can be performed by a box such as box 215 / 315 / 415 (and more specifically, processor 218 of box 215).

[0091] The technique may include identifying that an interval timer has expired at 705. The interval timer may be the one described above in conjunction with, for example, element 342 or 406 or Figure 5 The technique may further include identifying one or more earbuds, for example, in a pair of earbuds at 710. As noted in conjunction with element 303, the identification of the earbuds may be based on one or more factors, such as the respective power levels of the earbuds, which earbud was first placed in the case, which earbud was last used to transmit the status notification, etc. The technique may further include transmitting an enable command to the identified earbuds based on the interval timer at 715. Specifically, the enable command may be a notification enable command as described in conjunction with element 345 or 416, and may be configured to cause the earbud to transmit a notification signal associated with the identification of the earbud.

[0092] In some implementations, a case can receive two earbuds that are not communicatively coupled. Coupled earbuds can be earbuds that are sold as a set, typically play audio together, can communicate directly with each other (e.g., without another device to facilitate communication), or a combination of two or more of these. This can occur when two people who own similar pairs of earbuds accidentally grab one earbud from each of the two pairs.

[0093] In these specific implementations, the technology may further include determining that the first earbud and the second earbud are not coupled. The box may perform this determination when the two earbuds are placed in the box, or at any other appropriate time. At least in part in response to determining that the first earbud and the second earbud are not coupled, the box may transmit a similar enable command to the other earbud. For example, the box may transmit a second enable command to the second earbud to cause the second earbud to transmit a second notification signal associated with a second identification of the second earbud. The second enable command may be the same command as the enable command sent to the first earbud.

[0094] Figure 8is another exemplary technique related to wireless accessory notifications according to various implementations. Specifically, the technique is a technique that can be performed by a wireless accessory such as a wireless earbud 210 / 310 / 410 (and more specifically, the processor 240 of the wireless earbud 210).

[0095] The technique includes recognizing an enable command received from a charging case (e.g., charging case 215, 315, or 415) at 805. The enable command may be, for example, a notification enable command discussed in conjunction with element 345 or 416. The technique also includes transmitting a notification signal based on the enable command at 810, the notification signal including information related to a state of the earbud, a state of another earbud, or both. The notification signal may be, for example, a state notification discussed above in conjunction with element 354 or 424 or Table 1.

[0096] In some implementations, the notification signal can indicate whether the earbud is still coupled to the other earbud. For example, the two earbuds may no longer be coupled when: the other earbud has no power, e.g., the battery of the other earbud is depleted; when the distance between the other earbud and the earbud exceeds a threshold distance; or a combination of these.

[0097] The earbud may determine some or all of the information related to the state of the earbud, the state of the other earbud, or both. For example, when the earbud is not coupled to the other earbud, the earbud may determine whether the earbud is coupled to the other earbud. The earbud may determine information indicating that the other earbud is or is not coupled to the earbud as the state of the other earbud. For example, the earbud may determine information related to the state of the other earbud indicating that the other earbud is not in a charging case with the earbud when the earbud is not coupled to the other earbud.

[0098] It should be understood that Figure 6 , Figure 7 and Figure 8 The exemplary techniques described are intended as advanced exemplary techniques. Other implementations may have more or fewer elements, elements in a different order than depicted, etc. Other variations are possible in other implementations.

[0099] Fig. 9 It is based on the specific implementation of the wireless accessory device architecture. In general, Fig. 9 Can be wireless earbuds and are designed to complement Figure 2 In other words, architecture 900 may be Figure 2 The wireless earbud 210 may be a component thereof.

[0100] The architecture 900 includes a memory interface 901, a processor 902 (which may be similar to the processor 240), a peripheral device interface 903, a memory 904 (which may be similar to the memory 245), one or more inertial sensors 905, an in-ear detector (IED) 906, a wireless communication subsystem 907 (which may be similar to the wireless I / O 230), an audio subsystem 908, one or more speakers 909 (which may be similar to the speaker 250), one or more microphones 910, and an input / output (I / O) subsystem 911 (which may be similar to the user I / O 225). The inertial sensor 905 and the IED 906 may be similar to the sensor 260. The memory also includes instructions 912 and sound files 913. The memory interface 901, the processor 902, and / or the peripheral device interface 903 may be separate components, or may be integrated in one or more integrated circuits. Other accessory devices such as smart watches may include a wrist detector (OWD) (e.g., using an optical or proximity sensor) instead of an IED. One or more communication buses or signal lines may couple the various components.

[0101] Sensors, devices and subsystems may be coupled to the peripheral device interface 903 to facilitate multiple functions. For example, inertial sensors 905 and IED 906 may be coupled to the peripheral device interface 903 to facilitate the orientation and proximity functions of the accessory device. In some specific implementations, inertial sensors 905 (e.g., accelerometers, rate gyroscopes) may be utilized to detect the movement and orientation of the accessory device. For example, if the accessory device is an earplug, a binaural headset or a headset, a multi-axis accelerometer may be used to identify the head posture. In addition, an accelerometer may be configured to detect vibrations (e.g., tapping the accessory device) due to user input to activate or deactivate the accessory device or perform another function. Other sensors may also be connected to the peripheral device interface 903, such as a magnetometer, a temperature sensor, a barometer or a biometric sensor to facilitate related functions. For example, a biometric sensor may be used to verify and / or monitor heart rate and / or other fitness parameters. IED 906 may include an optical sensor, a proximity switch, a biometric sensor or any other suitable sensor for detecting when the accessory device is placed in or near the user's ear.

[0102] The communication functions may be facilitated by the wireless communication subsystem 907. The wireless communication subsystem 907 may include a radio frequency (RF) transceiver for communicating with a wireless communication device such as a wireless communication device. Figures 1 to 8The wireless communication subsystem 907 may facilitate short-range, peer-to-peer communication with the mobile device or another earbud. The specific design and implementation of the wireless communication subsystem 907 may depend on the communication network or medium through which the device is intended to operate. For example, the wireless communication subsystem 907 may facilitate communication over a Global System for Mobile Communications (GSM) network, a GPRS network, an Enhanced Data GSM Environment (EDGE) network, an IEEE 802.xx communication network (e.g., Wi-Fi, Wi-Max, ZigBee TM ), 3G, 4G, 4G LTE, Code Division Multiple Access (CDMA) networks, Near Field Communication (NFC), Wi-Fi Direct, and Bluetooth TM The wireless communication subsystem 907 may include a software stack for implementing wireless communication protocols.

[0103] The audio subsystem 908 may be coupled to one or more speakers 909 and one or more microphones 911 to facilitate voice-enabled functions such as voice recognition, voice replication, digital recording, and telephony functions, and to perform the same functions as described in reference to Figures 1 to 8 The process or enabling feature described.

[0104] The I / O subsystem 911 may include a touch controller and / or another input controller. The touch controller may be coupled to a touch surface. The touch surface and touch controller may, for example, detect contact and movement or its interruption using any of a variety of touch-sensitive technologies, including but not limited to capacitive, resistive, infrared and surface acoustic wave technologies, and other proximity sensor arrays or other elements for determining one or more points of contact with the touch surface. Other input controllers may be coupled to other input / control devices, such as one or more buttons, rocker switches or thumb wheels. One or more buttons may include an increase / decrease button for volume control of a speaker 909 and / or a microphone 911. In some specific implementations, an accessory device may play recorded audio files (e.g., sound files or audio messages), such as MP3, AAC and MPEG video files. In some specific implementations, an accessory device may include the functionality of an audio player (e.g., an MP3 player).

[0105] Memory interface 901 may be coupled to memory 904. Memory 904 may include high-speed random access memory or non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, or flash memory (e.g., NAND, NOR). Memory 904 may store instructions 912 and sound files 913. The instructions may include operating system instructions for handling basic system services and for performing hardware-related tasks. Instructions 912 may facilitate communication with one or more additional devices, one or more computers or servers, including communication with a computer such as a computer system described in reference to FIG. Figures 1 to 8The instructions 912 may facilitate graphical user interface (GUI) processing, inertial sensor processing, and IED processing. The instructions 912 may play a sound file 913 in response to a signal or command from the companion device, wherein the loudness level is increased to a maximum loudness but not exceeding the maximum loudness allowed by government regulations. The memory 904 may include additional instructions or fewer instructions. The various functions of the accessory device may be implemented in hardware and / or software, including in one or more signal processing and / or ASICs.

[0106] The features described may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of these. The features may be implemented in a computer program product tangibly embodied in an information carrier (e.g., in a machine-readable storage device) for execution by a programmable processor; and the method steps may be performed by a programmable processor executing a program of instructions to perform the functions of the embodiment described by operating on input data and generating output.

[0107] The described features may advantageously be implemented in one or more computer programs executable on a programmable system, the programmable system comprising at least one input device, at least one output device, and at least one programmable processor coupled to receive data and instructions from a data storage system and transmit data and instructions to the data storage system. A computer program is a set of instructions that can be used directly or indirectly in a computer to perform some activity or produce some result. A computer program may be written in any form of programming language (e.g., Objective-C, Java), including compiled and interpreted languages, and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0108] For example, suitable processors for executing a program of instructions include both general-purpose microprocessors and special-purpose microprocessors, and one or the only processor of multiple processors or cores of any type of computer. Generally speaking, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memories for storing instructions and data. Generally speaking, a computer can communicate with mass storage devices to store data files. These mass storage devices may include disks, such as internal hard disks and removable disks; magneto-optical disks; and optical disks. Storage devices suitable for tangibly embodying computer program instructions and data include: all forms of non-volatile memory, for example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and memory may be supplemented by an ASIC or incorporated into an ASIC. To provide for interaction with a user, these features may be implemented on a computer having a display device, such as a CRT (cathode ray tube), LED (light emitting diode), or LCD (liquid crystal display) display or monitor, for displaying information to the author, a keyboard, and a pointing device, such as a mouse or trackball, which the author can use to provide input to the computer.

[0109] The term "coupled" and its derivatives may be used herein. "Coupled" may refer to one or more of the following. "Coupled" may refer to two or more elements that are in direct physical or electrical contact. However, "coupled" may also refer to two or more elements that are in indirect contact with each other, but still cooperate or interact with each other, and may mean that one or more other elements are coupled or connected between the elements referred to as being coupled to each other. The term "directly coupled" may refer to two or more elements that are in direct contact.

[0110] Various operations may be described as multiple discrete operations in turn, in a manner that is most helpful in understanding the claimed subject matter. However, the order of description should not be construed as to imply that these operations are necessarily order dependent.

[0111] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the specific implementations to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from the practice of various specific implementations.

[0112] Although the above specific implementations have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

[0113] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

Claims

1. An apparatus comprising a processing circuit and a memory having stored thereon instructions, the instructions being operable when executed by the processing circuit to cause the processing circuit to perform operations comprising: receiving, by means of a wireless device communicatively coupled to the charging case, an enable command including an instruction to enable one or more notification signals; and A notification signal is generated based on receipt of the enable command, wherein the notification signal includes information related to the identification of the wireless device.

2. The device according to claim 1, wherein: When receiving the enable command, the wireless device does not transmit the notification signal; as well as Receipt of the enable command causes the wireless device to change state from not transmitting a notification signal to transmitting a notification signal.

3. The apparatus according to claim 1, wherein the operation further comprises: determining that the apparatus receives a connection with a second wireless device; as well as Responsive at least in part to determining that the apparatus received the connection with the second wireless device, a wait command is generated for transmission to the charging case to cause the charging case to wait for a disable command to be sent to the apparatus of the wireless device.

4. The apparatus of claim 3, wherein determining that the apparatus receives the connection with the second wireless device comprises: It is determined that the wireless device receives the connection with the second wireless device when the notification signal is enabled.

5. The device according to any one of claims 1-4, the operation also includes identifying a power signal from the charging box after generating the notification signal, and the power signal includes a signal to disable one or more notification signals.

6. The apparatus according to any one of claims 1 to 4, wherein the operation further comprises: identifying a disable command received from the charging case; as well as A stop command is generated for a transceiver included in the wireless device based on the disable command, the stop command causing the transceiver to stop transmission of the notification signal.

7. The apparatus according to any one of claims 1 to 4, wherein the operation further comprises: prior to said receiving of said enabling command, identifying a wake-up command received from said charging case; as well as A wake-up operating state is entered based on the wake-up command, wherein the wake-up operating state causes the device to monitor for the enable command.

8. The apparatus according to any one of claims 1 to 4, wherein the operation further comprises: After generating the notification signal, identifying a sleep command received from the charging box; as well as A sleep operational state is entered based on the sleep command, wherein the sleep operational state causes the device to skip monitoring for the enable command.

9. An apparatus comprising a processing circuit and a memory having stored thereon instructions operable when executed by the processing circuit to cause the processing circuit to perform operations comprising: determining, by means of a carrier device communicatively coupled to the one or more wireless devices, that an interval timer has expired; identifying a first wireless device from among the one or more wireless devices; as well as Based on identifying that the interval timer has expired, an enable command is generated for the first wireless device, the enable command including an indication to enable one or more notification signals identifying the first wireless device.

10. The apparatus of claim 9, wherein the operations further comprise: Detecting that the notification duration timer has expired; as well as In response at least in part to detecting that the notification duration timer has expired, a disable command for transmission to the first wireless device is generated to cause the first wireless device to cease transmitting the notification signal.

11. The apparatus of claim 10, wherein the operations further comprise: It is detected that the total duration timer has expired; as well as In response at least in part to detecting that the total duration has expired, the interval timer and the total duration timer are stopped.

12. The device according to any one of claims 9 to 11, wherein: The one or more wireless devices include two or more wireless devices, the two or more wireless devices include the first wireless device and a second wireless device, The operations also include: determining that the first wireless device and the second wireless device are not coupled; and In response at least in part to determining that the first wireless device and the second wireless device are not coupled, a second enable command identifying the second wireless device is generated for transmission to the second wireless device.

13. The device according to any one of claims 9 to 11, wherein: The one or more wireless devices include the first wireless device and a second wireless device; and The operations also include determining that the first wireless device includes identifying a first power level of the first wireless device and a second power level of the second wireless device.

14. The device according to any one of claims 9 to 11, wherein: The one or more wireless devices include the first wireless device and a second wireless device; and The operations also include determining that the first wireless device includes determining that the first wireless device is coupled to the carrier device and the second wireless device is not coupled to the carrier device.

15. The device according to any one of claims 9 to 11, wherein: The one or more wireless devices include the first wireless device and a second wireless device; and The operations also include determining the first wireless device includes determining which of the first wireless device and the second wireless device transmitted a previous notification signal.

16. A method comprising: receiving, by a processor of a first wireless device communicatively coupled to the charging case, an enable command including an indication for enabling one or more notification signals that should be enabled, wherein a pair of wireless devices includes a first wireless device and a second wireless device, each wireless device generating an audio signal; as well as A notification signal is generated by the processor in response to identifying the enable command, wherein the notification signal includes information related to a status of the pair of wireless devices. 17 . The method of claim 16 , wherein the notification signal comprises a first portion related to the status of the first wireless device and a second portion related to the status of the second wireless device.

18. The method of claim 16, wherein the information related to the status of the pair of wireless devices includes information related to whether the first wireless device is communicatively coupled to the second wireless device.

19. The method of claim 16, wherein the information related to the status of the pair of wireless devices includes information related to whether the wireless device is operably coupled to the charging case.

20. The method of claim 16, wherein the information related to the status of the second wireless device comprises information related to an identification of the second wireless device.

Images