Low power activation of accessories in sleep state

Abstract

The present disclosure relates to low-power activation of accessories in a sleep state. A first device is configured to establish a connection with a second device over a short-range communication link. The first device can transition to a sleep state, terminate (i) a paging operation and a paging scan operation associated with a paging protocol and (ii) an announcement scan operation associated with an announcement protocol, and perform an announcement broadcast operation associated with the announcement protocol that generates an announcement to be broadcast at a first interval, where the first interval is greater than a second interval used to perform the announcement broadcast operation in an active state.

Description

[0001] Related application citation

[0002] This application is a divisional application of Chinese national application number 201910682369.8, filed on July 26, 2019, entitled "Low-power activation of accessories in sleep state". Technical Field

[0003] This disclosure relates to low-power activation of accessories during sleep. Background Technology

[0004] Short-range communication protocols enable the exchange of short-range communication between two or more devices. Short-range connections can be established manually or automatically. Manual methods allow for greater control during link establishment and can make connection operations only active when the connection is active. However, manual methods can be time-consuming. Automated methods are more time-efficient and require little or no input, providing an improved user experience. However, automated methods can perform connection operations at predetermined times, potentially utilizing the increased power from limited power supplies. To further improve automated methods, detection protocols can be used based on Bluetooth configurations, including, for example, paging and announcement protocols.

[0005] Once a short-range communication link is established, the first device can exchange data with the second device. For example, the first device can be a source device providing audio data to the second device. The second device can receive the audio data and generate audio output to be played on the audio component of the second device. The short-range communication link can be maintained until the user chooses to discontinue use. For example, when the second device is an audio output component such as an earpiece or headset, the user can remove the second device (e.g., remove it from the ear, take it off the head, etc.). The short-range communication link can then no longer be used for data exchange other than control data exchange. In this way, the second device can be placed in a low-power state, such as a sleep state.

[0006] Sleep mode allows the second device to conserve power by modifying the way it performs certain operations. However, as mentioned above, the automated method can be maintained when continued connection operations are required. For example, to provide an improved user experience, the automated method can continue, allowing the short-range communication link to be re-established at any time the user chooses to resume use of the second device. However, when the automated method is used during sleep mode, the second device will continue to draw power for connection operations, including paging and announcement protocols. Therefore, even if the sleep mode is maintained for a long period, the second device will continue to draw power from a limited power supply to perform operations related to the automated connection method. When the second device remains in sleep mode for a sufficiently long period and based on the remaining power of the limited power supply, the second device may run out of power, requiring the user to recharge the second device before resuming any use, thus adversely affecting the user experience. Summary of the Invention

[0007] In one exemplary embodiment, a method is performed by a first device configured to establish a connection with a second device via a short-range communication link. The method includes putting the first device into a sleep state, terminating (i) paging operations and paging scan operations associated with a paging protocol and (ii) announcement scan operations associated with an announcement protocol; and performing an announcement broadcast operation associated with the announcement protocol, the announcement broadcast operation generating an announcement to be broadcast at a first interval, wherein the first interval is greater than a second interval used for performing the announcement broadcast operation in an active state.

[0008] In another exemplary embodiment, a first device configured to establish a connection with a second device via a short-range communication link is described. The first device has a transceiver and a processor. The transceiver is configured to establish a connection. The processor is configured to put the first device into a sleep state, instructing the transceiver to terminate (i) paging operations and paging scan operations associated with a paging protocol, or (ii) announcement scan operations associated with an announcement protocol, and instructing the transceiver to perform an announcement broadcast operation associated with an announcement protocol, the announcement broadcast operation generating an announcement to be broadcast at a first interval, the first interval being greater than a second interval used to perform the announcement broadcast operation in an active state.

[0009] In another exemplary embodiment, a method is performed by a first device configured to establish a connection with a second device via a short-range communication link. The method includes switching the first device from a sleep state to a non-sleep state, activating a paging scan operation associated with a paging protocol to listen for paging from the second device, and updating a declaration broadcast operation associated with a declaration protocol, the declaration broadcast operation generating a declaration to be broadcast at a first interval, which is smaller than a second interval used to perform the declaration broadcast operation during the sleep state, wherein the paging operation associated with the paging protocol and the declaration scan operation associated with the declaration protocol remain inactive. Attached Figure Description

[0010] Figure 1 Example systems utilizing components of short-range communication links according to various exemplary embodiments described herein are illustrated.

[0011] Figure 2 Example devices for establishing short-range communication links according to various exemplary embodiments described herein are shown.

[0012] Figure 3 Example signal diagrams for disconnecting short-range communication links when entering a sleep state are shown according to various exemplary embodiments described herein.

[0013] Figure 4 Example signal diagrams are shown for establishing short-range communication links upon exiting a sleep state, according to various exemplary embodiments described herein.

[0014] Figure 5 Example methods for disconnecting short-range communication links when entering a sleep state are illustrated according to various exemplary embodiments described herein.

[0015] Figure 6 Example methods for establishing a short-range communication link upon exiting a sleep state are shown according to various exemplary embodiments described herein. Detailed Implementation

[0016] This exemplary embodiment can be further understood with reference to the following description and accompanying drawings, wherein similar elements are labeled using the same reference numerals. The exemplary embodiment describes devices, systems, and methods for reducing or minimizing power consumption when in a sleep state (e.g., when establishing a short-range communication link using an automated method). The exemplary embodiment includes a first aspect when a sleep state is identified, which defines how to perform connection operations using an automated method when the accessory device is in a sleep state. The exemplary embodiment also includes a second aspect when the accessory device transitions from a sleep state to a wake-up or usage state, which triggers further connection operations on the accessory device to automatically establish a short-range communication link with the source device. Thus, the exemplary embodiment provides a mechanism that allows a short-range communication link to be established in a relatively short amount of time when the accessory device is to be used, and saves more power when the accessory device is in a low-power state.

[0017] This document describes an exemplary implementation for establishing a short-range communication link (or connection), wherein the short-range communication link is a Bluetooth link. However, the use of a Bluetooth link is merely exemplary, and a Bluetooth link may represent any short-range communication link (or be replaced by it). Furthermore, the use of a short-range communication link is also merely exemplary, and the exemplary implementation can be used or modified for any type of connection (e.g., mid-range or long-range connection) between two or more devices. The exemplary implementation described herein includes a declaration scheme involving broadcast identifiers (or identifiers) and scanning operations to detect broadcast identifiers / identifiers. However, the use of this type of declaration scheme is merely exemplary, and the exemplary implementation can be used or modified for any lower-power, faster identifier detection scheme. This document describes an exemplary implementation for establishing a Bluetooth link between an accessory device and a source device. However, the use of this accessory and source configuration is merely exemplary, and the exemplary implementation can be used or modified for any two or more devices to establish a connection using the mechanisms described herein. That is, it is not required that one device be subordinate to another. The terms "source device" and "accessory device" are used only for convenience in distinguishing the two devices in this specification. Additionally, this document describes an exemplary implementation for sleep states. However, a sleep state can represent any lower power state in which some or all of the device's functions and / or components are powered down or otherwise configured to consume less power than during normal operation. Furthermore, powered-down components do not require that the components not draw any power, but rather that they draw less power than during normal full operation. Exemplary embodiments are described in relation to when the device might be used. Possible uses may involve when information is evaluated to determine the probability indicating that the device is being used.

[0018] Wireless communication systems and protocols are being developed to further increase the types of uses and the types of devices that can be connected in this way. One wireless communication system may utilize a Personal Area Network (“PAN”), which can be defined as a computer network used to transmit data between multiple devices. For example, a PAN can be used for communication between devices themselves (e.g., interpersonal communication), or for connecting one or more devices to a higher-level network and / or the Internet via an uplink, where a “master” (or primary) device may assume responsibility for performing operations associated with a router. Furthermore, a wireless PAN may be a network that uses short-range wireless technologies such as the Bluetooth protocol to interconnect devices.

[0019] Within a wireless PAN, some applications or operations may be considered to use a relatively large amount of power, while others may be considered to use a relatively low amount of power. Similarly, some applications or operations may be considered to require a relatively large amount of time, while others may be considered to require a relatively small amount of time. For example, regarding Bluetooth connectivity, Bluetooth paging / paging scan operations can utilize more power and more time relatively than Bluetooth advertising schemes. Bluetooth paging / paging scan operations may be based on the Bluetooth protocol, which defines how Bluetooth connectivity operations are performed. Bluetooth advertising schemes may involve protocols in which low-power application profiles send and receive short data segments over low-power links. These profiles provide standards that manufacturers adhere to to allow devices to use specific technologies, such as Bluetooth, in the intended manner. One such advertising scheme has been defined as Bluetooth Low Energy (hereinafter referred to as "BLE") or "Bluetooth Smart," a wireless PAN technology designed and marketed by the Bluetooth SIG for applications in industries such as healthcare, fitness, positioning, beacons, security, and home entertainment. As described above, compared to Classic Bluetooth (or Bluetooth Classic), which includes Bluetooth paging / paging scan operations, BLE aims to provide significantly reduced power consumption and cost while maintaining similar communication range and reducing the time Bluetooth devices spend identifying proximity and establishing Bluetooth connections. However, even when using the BLE protocol in automated methods of establishing Bluetooth links, especially when the device is in a low-power state, Bluetooth paging scan operations and BLE scan operations are maintained to receive any paging or announcements that may be broadcast. As mentioned above, these operations can utilize more time and / or power.

[0020] An exemplary implementation is configured to reduce or minimize the amount of power drawn when the accessory device is in sleep mode. As will be described in further detail below, upon entering sleep mode, the exemplary implementation may terminate Bluetooth paging and paging scan operations as well as BLE scan operations, and maintain only BLE announcement operations to detect the source device in a modified manner using increased intervals. To exit sleep mode when the accessory device may be used, the accessory device may receive a request from the source device or detect the possible use of the accessory device. Upon confirming that the source device is an authorized device, the accessory device may initiate Bluetooth paging and paging scan operations to establish a Bluetooth connection. When the Bluetooth paging and paging scan operations and BLE scan operations are removed and other connection operations are modified when the accessory device enters sleep mode, the radio components on the accessory device can be used significantly less, allowing for improved power performance.

[0021] Figure 1 A system 100 utilizing components of a short-range communication link according to an exemplary embodiment is illustrated. System 100 illustrates a possible network of short-range connections between a source device 105 and a paired audio device 108 or between a source device 105 and an audio device 135, the paired audio device including a primary audio earbud 110 and a secondary audio earbud 115. System 100 illustrates when a short-range connection has been established between the source device 105 and the accessory device (e.g., paired audio device 108 or audio device 135). However, because the exemplary embodiment involves the duration during which a short-range communication link is not established and subsequently established, the illustrated short-range communication link may not be continuously active. The paired audio device 108 may be a system comprising two cordless audio earbuds 110, 115, for example, where there is no wired connection between the audio earbuds 110, 115, but they are designed to operate in conjunction with each other. For example, the first audio earbud 110 may output right channel audio streamed from the source device 105, and the second audio earbud may output left channel audio streamed from the source device 105. As will be described in more detail below, when outputting data received from the source device 105, one of the audio earbuds will assume the primary role of direct wireless connection to the source device 105 (e.g., the main audio earbud 110), while the other audio earbud will assume the secondary role of indirect wireless connection to the source device and direct connection to the main audio earbud (e.g., the auxiliary audio earbud 115).

[0022] A first short-range communication link can be established between the source device 105 and the primary audio earpiece 110 of the paired audio device 108 via a source-to-earbud (S2B) link 120. A second short-range communication link can be established between the primary audio earpiece 110 and the secondary audio earpiece 115 in the paired audio device 108 via an earpiece-to-earbud (B2B) link 125. The secondary audio earpiece 115 can also be configured to perform eavesdropping 130 (e.g., snooping) on ​​communications (e.g., data) being exchanged on the S2B link 120 or being broadcast / transmitted by the source device 105. A third short-range communication link can be established between the source device 105 and the audio device 135 via a source-to-device (S2D) link 140. The S2D link 140 can be substantially similar to the S2B link 120. System 100 may also include additional short-range communication links, such as between the source device 105 and the secondary audio earpiece 115 (not shown). In some examples, the short-range communication link can be a Bluetooth connection.

[0023] In conventional methods (e.g., as defined by the classic Bluetooth protocol), a manual method can be used to establish S2B link 120 and / or S2D link 140, where the user manually selects the device. For example, when both the main audio earbud 110 and audio device 135 can be used by the source device 105 to establish a short-range communication link, the source device 105 can detect these devices and display them in a list that allows the user to select one of these devices for connection. In contrast, an automated method can be used to establish B2B link 125, where the ability to continuously perform proximity detection and / or establish B2B link 125 is performed (e.g., at predetermined intervals). As will be described in detail below, according to an exemplary embodiment, S2B link 120, B2B link 125, and S2D link 140 can each be established using an automated method.

[0024] Source device 105 can be any electronic device capable of establishing S2B link 120 and / or S2D link 140. For example, source device 105 can be a mobile device (e.g., mobile computing device, mobile phone, tablet, personal computer, VoIP phone, personal digital assistant, wearable device, peripheral device, Internet of Things (IoT) device, etc.) or a fixed device (e.g., desktop terminal, server, IoT device, etc.). Paired audio devices 108 (including main audio earbud 110 and auxiliary audio earbud 115) can be any multiple wireless audio output components (e.g., earbuds) used together. Specifically, main audio earbud 110 and auxiliary audio earbud 115 can be wirelessly connected to source device 105 and connected to each other. Audio device 135 can be any integrated wireless audio output component (e.g., wireless headphones, speaker, etc.). Specifically, audio device 135 can be wirelessly connected to source device 105, but can utilize a wired arrangement for multiple audio output sub-components. The use of audio-related devices such as audio earbuds and audio devices is merely exemplary. Exemplary implementations can be used to establish short-range communication links between one or more devices of any type. Therefore, the main audio earpiece 110, the auxiliary audio earpiece 115, and the audio device 135 can represent any one or more electronic devices, including those of the types described above for the source device 105, as well as other types (e.g., accessory devices). For example, the main audio earpiece 110, the auxiliary audio earpiece 115, and the audio device 135 can also be Bluetooth-enabled hands-free headsets, wireless speakers, walkie-talkies, fitness trackers, sensors, car audio systems, etc.

[0025] In system 100, either source device 105 or master audio earphone 110 or audio device 135 may have a master / slave (or master / auxiliary) relationship on S2B link 120 or S2D link 140, respectively. Specifically, source device 105 may be the master component, while master audio earphone 110 or audio device 135 may be the slave component. Similarly, master audio earphone 110 and auxiliary audio earphone 115 may have a master / slave relationship on B2B link 125. Specifically, master audio earphone 110 may be the master component, while auxiliary audio earphone 115 may be the slave component. However, the master / slave relationship is merely exemplary. According to another exemplary embodiment, components connected via a short-range communication link may have a mutual relationship (e.g., peer-to-peer), where neither component has a priority (e.g., sharing equal priority), or neither component has a predetermined operation that must be performed (e.g., they may share predetermined operations or share responsibilities to be performed). In another exemplary embodiment, the master / slave relationship may be dynamically set. For example, if the primary audio earbud 110 is initially set as the primary component and the secondary audio earbud 115 is initially set as the secondary component, but conditions change such that the secondary audio earbud 115 remains connected to the source device 105 or has a better short-range connection to the source device 105, then the secondary audio earbud 115 can become the primary component, and the primary audio earbud 115 can become the secondary component. System 100 may include one or more other devices that may also exist in any S2B link 120, B2B link 125, S2D link 140, or another connection to any device of system 100.

[0026] When establishing a short-range communication link (e.g., S2B link 120, B2B link 125, or S2D link 140), the source device 105, main audio earbud 110, auxiliary audio earbud 115, and audio device 135 may include the necessary hardware, software, and / or firmware to perform routine operations and operations according to the exemplary embodiment. Furthermore, during periods when the main audio earbud 110, auxiliary audio earbud 115, and audio device 135 are in a low-power state, these components may include the necessary hardware, software, and / or firmware for performing routine operations and operations according to the exemplary embodiment.

[0027] Figure 2 A device 200 is shown according to an exemplary embodiment for establishing a short-range communication link and performing operations for use in a low-power state (e.g., Bluetooth paging operation, Bluetooth paging scan operation, BLE announcement operation, and BLE scan operation). Device 200 may represent any of the source device 105, main audio earpiece 110, auxiliary audio earpiece 115, and audio device 135. Specifically, device 200 may represent components that can be included to perform general operations and operations according to the exemplary embodiment.

[0028] Device 200 may include a transceiver 205 connected to antenna 210, baseband processor 215, controller 220, and other components (not shown). Other components may include, for example, memory, application processor, battery, ports for electrically connecting device 200 to other electronic devices, etc. Transceiver 205 may be configured to exchange data via one or more connections. Specifically, transceiver 205 may allow the establishment of short-range communication links using frequencies or channels associated with short-range communication protocols (e.g., channels associated with Bluetooth connections). Controller 220 may control the communication functions of transceiver 205 and baseband processor 215. Additionally, controller 220 may also control non-communication functions associated with other components such as memory, battery, etc. Accordingly, controller 220 may perform operations associated with the application processor.

[0029] The baseband processor 215 may be a chip compatible with wireless communication standards such as Bluetooth. The baseband processor 215 may be configured to perform multiple operations of the device 200. For example, operations may include methods and operations associated with exemplary embodiments, such as tearing down a short-range communication link when the device 200 enters a sleep state (or a lower power / reduced power state), and modified announcement schemes or detection operations, then using the announcement scheme and performing corresponding connection operations to establish a short-range communication link. Additionally, the transceiver 205 may also be configured to perform multiple operations of the device 200. For example, operations may include methods and operations associated with exemplary embodiments.

[0030] For the main audio earbud 110, the auxiliary audio earbud 115, and the audio device 135, these devices may include additional components. As will be described in further detail below, there may be available information indicating when these devices are being used or may be used. Accordingly, these devices may be equipped with additional components that generate or otherwise detect this information. For example, these devices may include sensors that can identify when the device is being used. In a particular example, the sensor may indicate a relative orientation or position (e.g., relative to each other in the case of paired audio devices 108, or relative to the user). When the sensor indicates that the device is, for example, in the user's ear, worn on the user's head, etc., the sensor may generate sensor data that is processed to indicate that the device is being used or may be used. As another example, the sensor may be a motion sensor. When the motion sensor detects the start of movement from a state of inactivity, the motion sensor may generate motion sensor data that is processed to indicate that the user has moved (e.g., picked up) the device and may be using the device.

[0031] For illustrative purposes, exemplary embodiments are described herein in conjunction with audio device 135. However, those skilled in the art will recognize that the description herein also relates to paired audio device 108 including primary audio earbud 110. Appropriate descriptions will also be provided when the mechanisms of the exemplary embodiments include additional operations when the secondary audio earbud 115 is implemented together with paired audio device 108.

[0032] Initially, the audio device 135 can be configured to be in one of several states. For example, the states may include any / all of the following: transport state, hibernation state, standby state, sleep state, idle state, ready state, and active state. These states can typically be categorized, for example, based on their relative power state compared to the components drawing power to establish a connection. As will be described below, the transport and hibernation states may use the lowest power state, the standby state may use an intermediate power state relative to the hibernation state, the sleep state may use a low power state, the idle state may use an intermediate power state relative to the sleep state, and the ready and active states may use a normal (or high / full) power state (e.g., when all connection operations are in use).

[0033] This state can relate to when the audio device 135 will be shipped from the retailer to the user / purchaser of the product. Therefore, the audio device 135, including radio components (such as transceiver 205), can be deactivated to utilize a minimum power state without using connection operations, including Bluetooth paging and paging scan operations as well as BLE announcement and scan operations. For the user and the specific audio device 135, the shipping state is only available when the audio device 135 is delivered to the user, until any type of first use is registered (e.g., charging operation, power-on operation, connection operation, etc.).

[0034] Sleep and standby states can refer to the state when the audio device 135 is in a storage case or otherwise placed in a mode that indicates the device will not be used immediately (if available). Sleep state can be used when the audio device 135 is in the storage case for an extended period. Therefore, the audio device 135 can utilize a minimum power state that is essentially similar to a transport state, as the likelihood of using the audio device 135 is low. In this state, connection operations, including Bluetooth paging and paging scan operations, and BLE announcement and scan operations, are not used. When the audio device 135 is removed from the storage case, the audio device 135 can exit the sleep state and enter another state, such as an idle state (described below). From the user's perspective, placing the audio device 135 in the storage case ensures that the radio components are deactivated.

[0035] Standby mode can be a mode that indicates the device will not be used for a short period of time when the audio device 135 is in the storage compartment or otherwise enters a state that indicates the device will not be used for a short period of time, for example, when the audio device 135 is expected to be used within the next 1 minute, 5 minutes, etc. Thus, the audio device 135 may have recently been placed in the storage compartment. The last used power state can be maintained for a period of time because the audio device 135 may be removed from the storage compartment during that period. For example, the last used power state could be an idle state before being placed in the storage compartment. The last used power state can transition to a short period of standby mode and then to a longer period of sleep mode. Any time period can be used to transition from standby mode (e.g., at least 1 minute, 5 minutes, etc.), but the faster the transition, the greater the power savings.

[0036] The sleep state and idle state may involve the audio device 135 being unused for a predetermined period of time. For example, the audio device 135 may be removed from the user's ear (e.g., in the case of audio earbuds), removed from the user's head (e.g., in the case of headphones), and so on. The audio device 135 may enter the sleep state after a longer period of inactivity compared to the idle state, or it may enter the idle state after a shorter period of time. Therefore, the audio device 135 may utilize a lower power state. In contrast to the lowest power state where no connection operation is performed, the lower power state according to the exemplary embodiment may utilize (or enable) the selection operation of the BLE protocol to allow the audio device 135 to still be detected. As will be described in detail below, when the audio device 135 is in the sleep state, the audio device 135 may perform or otherwise participate in BLE announcement operations, but does not perform Bluetooth paging and paging scan operations or BLE scan operations. In some examples, the audio device 135 may enter the sleep state after detecting little or no movement within a predetermined amount of time (e.g., 30 minutes, 1 hour, 2 hours, etc.). When the audio device 135 determines that it may be used (e.g., receives a request from the source device 105, detects motion, etc.), it can exit the sleep state.

[0037] An idle state can be achieved when the audio device 135 is not used for a short period of time (e.g., 1 minute, 5 minutes, 15 minutes, etc.). Similar to the relationship between hibernation and standby states, the audio device 135 may have been set to an idle state recently after being used. The power state of the last used device can be retained because the audio device 135 may be used again. For example, the audio device 135 can be removed from the position corresponding to the ready state (described below).

[0038] Readiness and activity states can relate to when audio device 135 is being used or may be used. For example, if audio device 135 is placed in a user's ear (e.g., in the case of audio earbuds), above or around the user's head (e.g., in the case of headphones), etc., then audio device 135 may be being used or ready to be used. Similarly, if audio device 135 is nearby or worn in an alternative position (e.g., when headphones are worn around a user's neck, when audio earbuds have detected movement, etc.), then audio device 135 may be used. Considering that audio device 135 is being used or may be used, the connection operation with source device 105 can continue to maintain S2B link 120 or S2D link 140.

[0039] As those skilled in the art will understand, a sleep state can be a low-power state during which the audio device 135 maintains a specific power usage while it is not used for an extended period. The goal of reducing or minimizing radio component activity to a threshold while in a sleep state provides improved power savings. As described above, different states can be categorized in various ways, such as the audio device 135 being in a box (e.g., in transit, hibernation, and standby), not being used (e.g., in sleep and idle), and being used (e.g., ready and active). Those skilled in the art will appreciate that the most commonly used states are those associated with both inactivity and use. Between each use of the audio device 135, the audio device 135 may remain in a sleep state for a considerable period. Accordingly, exemplary embodiments provide a mechanism that defines how connectivity operations associated with an automation method are used when the audio device 135 is in a sleep state.

[0040] For establishing a short-range communication link, the mechanism according to the exemplary embodiment can be used to accomplish the process using operations defined by classic Bluetooth. When audio device 135 is in sleep mode, source device 105 can connect to audio device 135 and cause audio device 135 to exit sleep mode. As described above, the automated method used in classic Bluetooth to allow source device 105 to connect to audio device 135 requires audio device 135 to perform active Bluetooth paging scans while in sleep mode. These Bluetooth paging scans can be performed at predetermined intervals, such as intervals required by Bluetooth. Performing paging scans while audio device 135 is in sleep mode can consume power from the power source. The exemplary embodiment is configured to reduce or minimize the power consumption when audio device 135 is in sleep mode, for example, by using different connection operations. While in sleep mode, audio device 135 can terminate all Bluetooth paging and paging scan operations as well as BLE scan operations, while maintaining only BLE announcement operations that can be used to detect source device 105 (and for source device 105 to detect and / or signal audio device 135). In addition, BLE operations can be modified to determine when to perform these operations to further reduce power consumption.

[0041] Audio device 135 can receive a scan request from source device 105, which can cause it to exit sleep mode. Furthermore, audio device 135 can maintain a whitelist of allowed devices with which it can establish an S2D link 140. Therefore, devices on the whitelist can trigger audio device 135 to exit sleep mode, while devices not on the whitelist do not trigger any action on audio device 135, allowing audio device 135 to remain asleep. Once audio device 135 exits sleep mode, BLE operations (e.g., announcement and / or scan) and Bluetooth operations (paging and / or paging scan) can be performed. By eliminating the need to perform Bluetooth paging and paging scan operations and BLE scan operations, and by further modifying how BLE announcement operations are performed while in sleep mode, the radio components of audio device 135 can be used significantly less, thus achieving improved power performance.

[0042] Exemplary embodiments can be configured to have a fallback mechanism. Those skilled in the art will understand that source device 105 can be configured to utilize classic Bluetooth, including paging and paging scan operations, but not BLE operations utilizing BLE announcement and BLE scan operations. Since the exemplary embodiment utilizes BLE operations while terminating classic Bluetooth connection operations in the automated method when audio device 135 is in sleep mode, audio device 135 may not be configured to establish S2D link 140 if source device 105 is configured in this manner. Therefore, audio device 135 can utilize a fallback mechanism, where audio device 135 can initiate a Bluetooth paging scan operation. In some embodiments, this use of Bluetooth paging scan operations can be configured by user-controlled manual settings. Alternatively, Bluetooth paging scan can be enabled automatically. For example, Bluetooth paging scan operations can also be triggered when an event occurs. Compared to using a scan request received from source device 105 configured to use BLE operations, the fallback mechanism can trigger a Bluetooth paging scan operation when potential use of audio device 135 is detected. For example, the audio device 135 may be equipped with one or more sensors (e.g., motion sensors, optical sensors, etc.) to identify when the audio device 135 may be used.

[0043] Returning to the mechanism according to the exemplary embodiment, a first aspect could be when the audio device 135 enters a sleep state and performs subsequent operations. The audio device 135 may be in an idle state (e.g., entering from a ready or active state). The audio device 135 may detect when it enters an idle state based on various criteria. Exemplary criteria include the S2D link 140 being used only for control data; the audio device 135 no longer being worn by the user; the audio device 135 being placed on a stationary surface, etc. After entering an idle state, a decision may instruct the audio device 135 to remain unused for a predetermined (or threshold) period of time and thus enter a sleep state. The decision to enter a sleep state may be based on the idle state. For example, the audio device 135 may determine that the current state is an idle state and that the idle state has been maintained for at least a predetermined amount of time (e.g., 30 minutes, 1 hour, 2 hours, etc.). In identifying when it enters an idle state, the audio device 135 may determine via sensors that it is not being used or has no intention to be used. For example, a sensor can indicate the position or orientation of the audio device 135 on a user, indicating that the audio device 135 is being used (e.g., around the user's head, around the user's ears, etc.) or may be used (e.g., around the user's neck). As another example, a sensor can indicate the movement of the audio device 135. No movement may indicate that the audio device 135 is not being used, while selected movement may indicate that the audio device 135 may be being used. The audio device 135 may utilize detected movements individually or in combination, for example, to make a use or intention decision.

[0044] Once the audio device 135 determines it needs to enter a sleep state, it may perform one or more operations during the transition. In the first example, while the S2D link 140 is still established, the audio device 135 may disconnect from the source device 105 and dismantle the S2D link 140. For example, the audio device 135 may have been removed from the user's clothing and placed on a nearby surface, but the user remains in a substantially similar position near the audio device 135. Therefore, the S2D link 140 can still be established. In this case, the audio device 135 may dismantle the existing S2D link 140 when entering a sleep state. As another example, the audio device 135 may have been removed from the user's clothing and placed on a nearby surface, but the user has left that position, leaving the source device 105 outside the operating range of the S2D link 140. Therefore, the S2D link 140 may have been disconnected before the time to enter a sleep state. In this case, the link may have been dismantled before it is determined that the audio device should enter a sleep state.

[0045] When entering sleep mode, the S2D link 140 is disconnected from the audio device 135, the short-range communication link is broken, or before the audio device 135 enters sleep mode, the S2D link is disconnected from an unsustainable short-range communication link for any reason, the audio device 135 may be configured to store host connection information associated with the previous S2D link 140 between the audio device 135 and the source device 105 (or another source device to which the audio device 135 is connected). As will be described in detail below, the host connection information of the previous S2D link 140 for which the audio device 135 is a member may provide information on when the audio device 135 wakes from sleep mode based on, for example, sensor data, rather than receiving scan requests from the source device 105.

[0046] In another example of operations performed when entering sleep mode, audio device 135 may terminate Bluetooth paging, Bluetooth paging scan, and BLE scan operations. These connection operations can be performed in an automated method to establish S2D link 140. Due to the increased power consumption of using paging and the two scan operations, the exemplary embodiment is configured to terminate these operations while in sleep mode to further save power and reduce the power usage of audio device 135. Accordingly, a BLE announcement operation is performed in sleep mode so that audio device 135 can still be detected by source device 105. The exemplary embodiment is described in conjunction with the termination of paging and the two scan operations. However, the exemplary embodiment may also utilize different operation options to be maintained or used while in sleep mode. For example, a fallback mechanism may exist if the last connected source device 105 was not configured with an announcement protocol under BLE. Therefore, audio device 135 may still perform Bluetooth paging operations in sleep mode. Alternatively, audio device 135 may choose to terminate Bluetooth paging and paging scan operations and maintain BLE announcement and scan operations. BLE scan operations may consume less power than Bluetooth scan operations. Therefore, even in sleep mode, it can still improve power savings compared to conventional automation methods.

[0047] In another example of an operation performed in sleep mode, audio device 135 may switch a BLE announcement operation from a first interval to a second, longer interval. In addition to selecting which connection operation to perform, the operation being performed can also be modified. For example, the BLE announcement operation may be modified from a standard announcement broadcast interval (e.g., 181.25 ms) used before entering sleep mode (e.g., when in an idle, ready, or active state) to a longer sleep announcement broadcast interval (e.g., twice as long, 362.5 ms). By reducing the number of BLE announcements broadcast, audio device 135 can further save power and reduce power consumption. The sleep announcement broadcast interval can be fixed, dynamic, random, etc., as long as the sleep announcement broadcast interval is longer than the standard announcement broadcast interval. The length of the interval may differ from the example used herein. For example, the BLE announcement broadcast interval may be greater than or less than the standard announcement broadcast interval (e.g., 181.25 ms). The sleep announcement broadcast interval may also be a different multiple relative to the BLE announcement broadcast interval and may be greater than or less than twice the BLE announcement broadcast interval (e.g., 362.5 ms).

[0048] The BLE announcement can also be modified to change a portion of the payload. For example, when audio device 135 enters a sleep state, the BLE announcement operation can generate a BLE announcement with a payload indicating the state of audio device 135. In this case, the payload indicates that audio device 135 is in sleep (or in a low-power state). When a continuous BLE announcement instructing audio device 135 to remain in sleep is broadcast, the device receiving the BLE announcement can infer that audio device 135 is not available to establish S2D link 140. Therefore, the device can terminate transmissions to audio device 135 (e.g., a scan request as described below).

[0049] BLE announcement operations can generate scannable BLE announcements. That is, when correctly configured, source device 105 can receive BLE announcements being broadcast from audio device 135 during a BLE scan operation performed by source device 105. Similarly, if source device 105 is not configured with an announcement protocol under BLE, audio device 135 can revert to a fallback mechanism and utilize a Bluetooth paging scan operation instead of generating and broadcasting a BLE announcement.

[0050] In another example of operations performed in sleep mode, audio device 135 may configure transceiver 205 to receive scan requests from source device 105. That is, audio device 135 may utilize passive receive operations, where scan requests transmitted from source device 105 can be received by audio device 135 in sleep mode. Audio device 135 may also configure transceiver 205 such that only source devices in a whitelist are allowed to trigger the establishment of S2D link 140. The whitelist may be a manually generated list, an automatically generated list, or a combination thereof. As a manually generated list, a user may provide audio device 135 with identification information indicating different source devices to be included in the whitelist. As an automatically generated list, audio device 135 may track source devices with which it has previously established corresponding S2D links 140. Audio device 135 can therefore include these previously connected source devices in the whitelist. For illustrative purposes, it may be assumed that source device 105 is in the whitelist. Operations associated with the whitelist may be performed by, for example, a Bluetooth core controller, application processor, etc.

[0051] Audio device 135 may remain in sleep mode and utilize selected operations in a modified manner until an instruction to exit sleep mode is received or determined. Once audio device 135 determines to exit sleep mode, it may perform one or more operations during the transition. As described above, there are multiple ways for audio device 135 to determine to exit sleep mode. In a first example exit mode, audio device 135 may utilize a passive receiving operation, wherein a scan request from source device 105 may be received, which may trigger exit from sleep mode (e.g., if source device 105 is in a whitelist). In a second example exit mode, audio device 135 may determine, for example, based on sensor data from one or more sensors of audio device 135 to determine possible user use of audio device 135. Each exit mode may require performing a corresponding set of operations.

[0052] In a first example exit mode where audio device 135 receives a scan request from source device 105, audio device 135 can wake up from a sleep state, enter an idle state, and perform several operations. In the first example, audio device 135 can identify source device 105 (e.g., based on its identity included in the scan request) and determine whether source device 105 is a known device or otherwise included in a whitelist. First, source device 105 can be positioned to receive a BLE announcement being broadcast by audio device 135. Based on the BLE announcement, source device 105 can transmit a scan request to audio device 135. If source device 105 from which it transmits the scan request is not in the whitelist, audio device 135 can return to a sleep state and continue the BLE announcement operation at modified intervals. If source device 105 is in the whitelist, audio device 135 can then perform subsequent operations.

[0053] Subsequent operations may involve transitioning from a sleep state to an idle state. In the first example, audio device 135 may respond to a scan request and transmit a scan response. As described above, the BLE announcement operation may generate a BLE announcement with a modified payload indicating the sleep state of audio device 135. To prevent a whitelisted source device 105 from terminating its connection attempt with audio device 135, the scan response may include an indication that audio device 135 has woken up and is no longer in a sleep state (along with other information such as identification information, control information, etc.). In the second example, audio device 135 may update the payload of the BLE announcement. Like the scan response, audio device 135 may now indicate in the BLE announcement that audio device 135 is in a non-sleep state (e.g., an idle state). Using the updated payload of the BLE announcement, the scan response may be selectively used to update the state change of audio device 135 to source device 105. In the third example, audio device 135 may update the interval of broadcasting the BLE announcement. Audio device 135 can resume from, for example, a sleep announcement broadcast interval of 362.5 ms to, for example, a standard announcement broadcast interval of 181.25 ms. In the fourth example, audio device 135 can initiate a Bluetooth paging scan operation. As described above, the mechanism for establishing S2D link 140 can include operations used in classic Bluetooth. Therefore, Bluetooth paging and paging scan operations can be used. Accordingly, a source device 105 that has detected audio device 135 and now realizes that audio device 135 is not in sleep mode can begin paging audio device 135 using Bluetooth paging. Audio device 135 can perform a Bluetooth paging scan to receive Bluetooth paging. In the fifth example, audio device 135 can set the interval for performing the Bluetooth paging scan operation. For example, audio device 135 can use a fast scan rate, in which more Bluetooth paging scans are performed compared to a standard scan. Audio device 135 can use a fast scan rate for a predetermined amount of time or when establishing S2D link 140, and then set the Bluetooth paging scan to the standard scan rate. Audio device 135 can utilize these connection operations for a predetermined amount of time (e.g., 5 seconds, 10 seconds, etc.). If audio device 135 is configured to perform more attempts, the connection operations can be cycled again for more attempts, with an interruption time between each attempt. If audio device 135 fails to establish S2D link 140, audio device 135 can return to sleep and update the connection operations.

[0054] In a second example exit method where audio device 135 determines possible use, audio device 135 can wake from a sleep state and enter an idle state to perform multiple operations based on other operations being performed while in the sleep state. While in the sleep state, sensors of audio device 135 can monitor and register sensor data, such as any / all of position, orientation, movement, etc. For example, if the sensors register audio device 135 as relatively stationary, the probability of audio device 135 being used is relatively low. In contrast, if the sensors register movement of audio device 135 from a stationary state, the probability of audio device 135 being used is higher. As another example, if the sensors register audio device 135 is now in a position corresponding to possible use (e.g., on the user's neck) or actual use (e.g., on the user's head, on the user's ear, etc.), it can be determined that audio device 135 will be used. Therefore, using sensor data, audio device 135 can exit from a sleep state to an idle, ready, or active state.

[0055] Upon waking from a sleep state and entering a subsequent state, the audio device 135 may perform several operations. For example, the audio device 135 may determine whether a previous source device 105 with which the audio device 135 had established a connection supports a fast scan rate. Since a fast scan rate is a feature of the connection operation in the Bluetooth standard, it may not be implemented in all Bluetooth-enabled devices, and when the audio device 135 is configured to have a fast scan rate, the audio device 135 may dynamically set the Bluetooth paging scan operation and the corresponding paging scan interval. Therefore, if the previous source device 105 supports this function, the audio device 135 may set a fast scan rate. Alternatively, if the previous source device 105 does not support this function or the timer using the fast scan rate has expired, the audio device 135 may set a standard scan rate. Further operations may be performed in a manner substantially similar to the first approach described above. Specifically, a BLE announcement may be broadcast at a new interval from the sleep announcement (or low power) broadcast interval (e.g., 362.5 ms) to the standard announcement broadcast interval (e.g., 181.25 ms). BLE claims that the payload can be modified to indicate a new state of the audio device (e.g., non-sleep state).

[0056] Furthermore, in the second example mode, the audio device 135 can perform a Bluetooth paging operation. In this second mode, the audio device 135 exits sleep mode due to sensor data rather than due to an indication from the source device 105. Therefore, compared to the first mode which uses a scan request (which is a fairly clear indication that the source device 105 is in a position to establish an S2D link 140), the second mode which uses sensor data relies on the assumption that the audio device 135 will be used, and also assumes the existence of a source device 105 in a position to establish an S2D link 140, which triggers sensor data to indicate possible use. Therefore, the audio device 135 can also utilize the Bluetooth paging operation to transmit a Bluetooth paging message to the source device 105 that is performing a Bluetooth paging scan operation. The audio device 135 can perform the Bluetooth paging operation for a predetermined amount of time and perform one or more cycles. For example, the audio device 135 can broadcast a Bluetooth paging message for a predetermined amount of time (e.g., 1 second, 5 seconds, greater than 5 seconds, etc.). If the S2D link 140 has been established, the audio device 135 can terminate the Bluetooth paging operation prematurely. After a predetermined time, audio device 135 may wait for a shorter duration (e.g., 5 seconds, 10 seconds, etc.) and perform a Bluetooth paging operation (if configured to do so). For example, audio device 135 may use a predetermined number of Bluetooth paging operation cycles (e.g., 3 attempts, 5 attempts, etc.). If the S2D link 140 has not been established, audio device 135 may enter an unconnected idle state. When audio device 135 wakes from sleep mode for a predetermined reason (e.g., motion is detected), audio device 135 may enter an idle state and a timer may start. The timer may start while in the idle state when sensor data no longer indicates potential use (e.g., audio device 135 returns to a static setting). When the timer expires (e.g., 30 minutes, 1 hour, 2 hours, etc.), audio device 135 may return to sleep mode.

[0057] Alternatively, when a scan request is received but does not result in a connection with source device 105, audio device 135 may reach an unconnected idle state. Although there is generally clear indication that source device 105 is in the proper position to establish S2D link 140, audio device 135 may still fail to establish S2D link 140 with source device 105. For example, a Bluetooth paging from source device 105 may not reach audio device 135 during a Bluetooth paging scan. As described above, if a fast scan rate is used (e.g., source device 105 is correctly configured), audio device 135 may continue using the fast scan rate until a predetermined time associated with using the fast scan rate has expired, at which point the audio device may return to the standard scan rate. Using either scan rate, audio device 135 may continue to receive Bluetooth paging from source device 105. When the Bluetooth paging scan operation is set to the standard scan rate, audio device 135 may activate a sleep timer, in which attempts to receive Bluetooth paging from source device 105 transmitting the scan request are terminated. When the sleep timer expires, the audio device 135 can determine whether a usage indication exists, such as a usage indication corresponding to the second type (e.g., sensor data indicating position, orientation, movement, etc., to identify possible use). If no usage indication is detected, the audio device 135 can return to the sleep state and update the connection operation. However, if a usage indication exists, the audio device 135 can enter an unconnected idle state, and after the timer associated with entering the sleep state from the idle state expires (e.g., 30 minutes, 1 hour, 2 hours, etc.), the audio device can return to the sleep state from the unconnected idle state.

[0058] Audio device 135 can determine potential use based on sensor data in a variety of ways. In a particular manner, which may be implemented according to an exemplary embodiment, the sensor data may include a corresponding threshold. For example, when sensor data indicates motion, the motion may be required to be above a motion threshold. In this way, audio device 135 can exit sleep mode when there is a reasonable possibility of using audio device 135 rather than unexpected motion that audio device 135 may experience.

[0059] Exemplary implementations may also consider other features of the Bluetooth protocol. For example, the Bluetooth protocol may include sniffing connections. Those skilled in the art will understand that one type of connection that can be used in the Bluetooth protocol is a sniffing mode, a power-saving mode in which the audio device 135 is in a less active state. Therefore, a sniffing connection can be substantially similar to a sleep state, but is not actually in a sleep state. Thus, if a sniffing connection is present, the audio device 135 can listen for transmissions at set intervals (e.g., 100ms, 200ms, etc.). Sniffing connections may also include sniffing anchors that can take precedence over other operations. For example, a sniffing anchor may have a higher priority than a BLE declaration for re-establishing a sniffing connection.

[0060] As described above, source device 105 can also establish an S2B link 120 with paired audio device 108. Since paired audio device 108 includes both a primary audio earbud 110 and a secondary audio earbud 115, the above mechanism can include further operations and modifications to combine the secondary audio earbud 115 and the S2B link 125. These further operations and modifications may involve operations performed by the primary audio earbud 110, which, as described above, is substantially similar to audio device 135 relative to source device 105.

[0061] In the first example, the main audio earbud 110 and the auxiliary audio earbud 115 may each be equipped with a sensor. Accordingly, the main audio earbud 110 may generate sensor data in a manner substantially similar to that of the audio device 135. Additionally, the auxiliary audio earbud 115 may generate sensor data detected at the auxiliary audio earbud 115 and may transmit this sensor data to the main audio earbud 110 and / or another device for further processing. In this way, the sensor data detected at the main audio earbud 110 and / or the auxiliary audio earbud 115 may be used independently or in combination to determine whether the paired audio device 108 may be used.

[0062] In the second example, before paired audio device 108 enters sleep mode, but after determining that primary audio earbud 110 is to enter sleep mode (in a manner substantially similar to audio device 135), primary audio earbud 110 may determine whether the secondary connection or B2B link 125 is still established. If B2B link 125 is disconnected, paired audio earbud 108 may enter sleep mode and perform the connection operations as described above. However, if B2B link 125 is still established, primary audio earbud 110 may change B2B link 125 to a sniffing connection with a usage time interval (e.g., 500ms or 4 watts / timeout). Subsequently, primary audio earbud 110 may terminate BLE scanning operations (and Bluetooth paging and paging scanning operations (if not already performed)) to enter coupled sleep mode with secondary audio earbud 115. Primary audio earbud 110 may update the sniffing settings of the sniffing connection and transmit this information to secondary audio earbud 115 for its use. The auxiliary audio earbud 115 can then terminate the BLE scanning operation (as well as the Bluetooth paging and paging scanning operation (if not already performed)) to enter a coupled sleep state with the main audio earbud 110.

[0063] When B2B link 125 goes offline (e.g., due to battery depletion, interference, range, etc.), the secondary audio earpiece 115 can be responsible for rebuilding B2B link 125, for example, using a fast connection procedure. In this scenario, the secondary audio earpiece 115 can enable BLE scanning and BLE announcement operations (e.g., broadcasting an announcement at 181.25 ms). The secondary audio earpiece 115 can receive announcements from the primary audio earpiece 110, and the secondary audio earpiece 115 can transmit a scan request with connection intent along with its current state to the primary audio earpiece. The primary audio earpiece 110 can follow a procedure to exit sleep mode and begin paging scanning and other connection operations. The secondary audio earpiece 115 pagees the primary audio earpiece 110 and establishes a connection. The primary audio earpiece 110 can then switch connection roles, enter sniffing mode, and use the mechanisms described above to put the paired audio device 108 into sleep mode.

[0064] When the paired audio device 108 is in sleep mode, the primary audio earbud 110 can be configured to perform a BLE announcement operation and broadcast a BLE announcement indicating the status of both the primary and secondary audio earbuds 110 and 115. Since the BLE announcement from the primary audio earbud 110 includes information about the secondary audio earbud 115, the secondary audio earbud 115 can use a sniffing connection to update the primary audio earbud 110, for example, using sensor and / or status information (such as motion status, battery level, etc.). Given that the primary audio earbud 110 is responsible for performing the BLE announcement operation, after an extended period in sleep mode, the primary audio earbud 110 can utilize a larger portion of its power supply than the secondary audio earbud 115, thus requiring only the aforementioned information to update the primary audio earbud 110. To maximize efficiency and improve power usage between the primary and secondary audio earbuds 110 and 115 of the paired audio device 108, a coordinated earbud swap can be used, where the secondary audio earbud 115 can become the master device and the primary audio earbud 110 becomes the slave device. Therefore, the secondary audio earbud 115 can take over the responsibility of performing BLE announcement operations, while the primary audio earbud 110 can resume providing updated information to the secondary audio earbud 115. Any subsequent swapping can be performed while the paired audio device 108 remains in sleep mode. Triggers for initiating role swapping can be based on any one or more conditions (e.g., time, battery threshold, power consumption over a period of time, etc.). Furthermore, role swapping can be performed at any time, and the time periods between role swaps do not need to be equal. Swapping can be performed even without a connection to the source device 105.

[0065] For further operations performed when paired audio device 108 exits sleep mode, a set of operations substantially opposite to those described above can be performed when paired audio device 108 enters sleep mode. For example, primary audio earbud 110 and secondary audio earbud 115 can initiate a BLE scan operation to establish a B2B link 125 beyond the sniffing connection. Further details and exemplary timing of when these further operations (for both entering and exiting sleep mode) are performed when paired audio device 108 is used with S2B link 120 and B2B link 125 will be described in further detail below.

[0066] Figure 3Example signal diagram 300 is illustrated for disconnecting a short-range communication link upon entering a sleep state, according to various exemplary embodiments described herein. Specifically, signal diagram 300 illustrates an exemplary sequence of events that occur when audio device 135 enters a sleep state from a non-sleep state (e.g., an active, ready, or idle state) and subsequent connection operations performed by audio device 135 and source device 105. As shown, signal diagram 300 may include source device 105, which includes baseband processor 305 and controller 310, and audio device 135, which includes baseband processor 315 and controller 320. For illustrative purposes, signal diagram 300 also relates to when an S2D link 140 is established and subsequently dismantled upon entering a sleep state.

[0067] In non-sleep mode, baseband processors 305 and 315 can perform connectivity operations, including Bluetooth paging and paging scan operations, as well as BLE announcement and scan operations. For example, baseband processor 305 can broadcast a BLE announcement 322 and perform a BLE scan 324. Baseband processor 315 can broadcast a BLE announcement 326 and perform a BLE scan 328. As another example, baseband processor 305 can perform a Bluetooth paging scan operation (not shown), while baseband processor 315 can also perform a Bluetooth paging scan operation 332. In another example, baseband processor 305 can transmit a Bluetooth paging 330, while baseband processor 315 can also transmit a Bluetooth paging (not shown).

[0068] Connection operations can be performed at predetermined intervals. In a first example, when the baseband processor 305 or 315 enters a paging state, a Bluetooth paging operation can be performed to transmit a Bluetooth paging (e.g., Bluetooth paging 330). In a particular embodiment, when using 32 Bluetooth channels, the Bluetooth paging operation can cycle once every 10 ms. In a second example, the baseband processor 305 or 315 can be configured to utilize a Bluetooth paging scan operation when in a currently non-sleep state. In a particular embodiment, using a standard Bluetooth paging scan operation interval, the processor 305 or 315 can scan the Bluetooth channels for 11.25 ms every 1.28 seconds to look for a Bluetooth paging. In a third example, the baseband processor 305 or 315 can be configured to utilize a BLE announcement operation when in a currently non-sleep state. In a particular embodiment, using a standard BLE announcement operation interval, the baseband processor 305 or 315 can broadcast a BLE announcement once every 181.25 ms. In the fourth example, baseband processor 305 or 315 can be configured to utilize BLE scan operations while in a currently non-sleep state. In a particular implementation, using a standard BLE scan operation interval, processor 305 or 315 can perform a 10ms BLE scan every 100ms.

[0069] The intervals of the above connection operations are shown in signal diagram 300. BLE announcements 322 and 326 may be broadcast once every 181.25 ms. BLE scans 324 and 328 may be performed for 10 ms every 100 ms. BLE scan 328 may not be performed on audio device 135. According to another exemplary embodiment, the baseband processor 315 of audio device 135 may only perform the BLE announcement operation (without performing the BLE scan operation). Accordingly, the baseband processor 305 of source device 105 may perform the BLE scan operation (and may additionally perform the BLE announcement operation). Once the announcement protocol indicates detection between source device 105 and audio device 135, a paging protocol can be used to establish S2D link 140. For example, Bluetooth paging 330 may cycle once every 10 ms, and Bluetooth paging scan 332 may be performed for 11.25 ms every 1.28 seconds. Thus, Bluetooth connection 334 (e.g., S2D link 140) may be established.

[0070] At a subsequent time, controller 320 may determine that audio device 135 may enter sleep state 336. As described above, audio device 135 may include a sensor that generates sensor data indicating when audio device 135 is no longer in use. For example, paired audio device 108 may be removed from a user's ear. Alternatively, audio device 135 may be placed on a surface. When audio device 135 is not in use, controller 320 may initially place audio device 135 (e.g., from an active or ready state) into an idle state. Once in an idle state, a timer may be activated so that it can enter sleep state upon timeout. For example, if audio device 135 remains in an idle state for at least 2 hours (or other predetermined duration), controller 320 may place audio device 135 into sleep state.

[0071] When controller 320 determines that audio device 135 is about to enter sleep state 336, controller 320 may forward sleep state indication 338 to baseband processor 315 to terminate Bluetooth connection 334 (because S2D link 140 is no longer needed). Accordingly, baseband processors 305 and 315 may use standard termination procedures to disconnect Bluetooth connection 334. Signal diagram 300 assumes that Bluetooth connection 334 is still established when sleep state 336 is determined. However, as mentioned above, Bluetooth connection 334 may have already been terminated for any of a variety of other reasons.

[0072] According to a first aspect of the mechanism of the exemplary embodiment, when it is determined that the audio device 135 is to enter sleep state 336, the controller 320 may configure how the baseband processor 315 performs connection operations when the audio device 135 enters sleep state. As described above, in sleep state, the audio device 135 may terminate Bluetooth paging and paging scan operations as well as BLE scan operations, leaving only BLE announcement operations. Therefore, the controller 320 may set 342 for BLE announcement and forward BLE announcement instruction 344. The controller 320 may instruct the baseband processor 315 to terminate other connection operations in a variety of ways. For example, the controller 320 may forward a separate instruction (not shown) or may include the instruction in the BLE announcement instruction 344. Once the baseband processor 315 receives the BLE announcement instruction 344, the baseband processor 315 may begin performing BLE announcement operations by broadcasting a sleep BLE announcement 346 at intervals greater than a standard interval (e.g., 362.5 ms). BLE announcement instruction 344 can also instruct baseband processor 315 to update the BLE announcement payload, thereby indicating the sleep state of audio device 135.

[0073] Figure 4 Example signal diagram 400 for establishing a short-range communication link upon exiting a sleep state, according to various exemplary embodiments described herein. Specifically, signal diagram 400 illustrates an exemplary sequence of events that occur when audio device 135 exits a sleep state and enters a non-sleep state (e.g., an active, ready, or idle state), and subsequent connection operations performed by audio device 135 and source device 105. As shown, signal diagram 400 may include source device 105, which includes baseband processor 405 and controller 410, and audio device 135, which includes baseband processor 415 and controller 420. For illustrative purposes, signal diagram 400 also relates to when audio device 135 exits a sleep state based on a received scan request to establish an S2D link 140.

[0074] In sleep mode, baseband processor 415 can perform BLE announcement operations only at modified intervals. Therefore, a sleep BLE announcement 422 can be broadcast every 362.5 ms, including a payload indicating the sleep state of audio device 135. Subsequently, source device 105 can listen for the announcement, allowing source device 105 and audio device 135 to detect each other. For example, baseband processor 415 can broadcast a sleep BLE announcement 426 received by source device 105 during BLE scan 428. Sleep BLE announcement 426 can be processed, and the sleep state of audio device 135 indicated in the payload can be monitored. The received sleep BLE announcement 426 can trigger baseband processor 405 to forward announcement indication 430 to controller 410. Announcement indication 430 can be processed by controller 410 to trigger connection 432 with audio device 135. Therefore, controller 410 can forward connection indication 434 to baseband processor 405. Meanwhile, baseband processor 415 can continue broadcasting sleep BLE announcement 436. For illustrative purposes, sleep BLE announcements 426 and 436 are shown, and the distance between them is not intended to show the actual sleep broadcast interval. Therefore, announcement indication 430, trigger 432, and connection indication 434 may not all occur during the interval between two sleep BLE announcements.

[0075] When baseband processor 405 receives connection instruction 434, it may transmit scan request 438 to baseband processor 415. As described above, audio device 135 may passively listen for scan requests from source devices attempting to establish S2D link 140. When baseband processor 415 has received scan request 438 from source device 105, it may forward request instruction 440 to controller 420. Controller 420 may wake up audio device 135. In this case, controller 420 may transition audio device 135 from sleep state to idle state. Then, controller 420 may, for example, use a mechanism according to an exemplary embodiment to determine whether source device 105 is included in a whitelist of source devices allowed to establish S2D link 140 with audio device 135. Assuming controller 420 determines that source device 105 is allowed or in the whitelist, controller 420 may forward an allow instruction 446 to baseband processor 415.

[0076] When baseband processor 415 receives the permitted indication 446, it can transmit a scan response 448 back to baseband processor 405. The scan response 448 may include an indication that audio device 135 is no longer in a sleep state but is in a non-sleep state (such as idle, ready, or active). Furthermore, the permitted indication 446 may update the BLE announcement payload, thereby indicating that the state of audio device 135 is now indicated as non-sleep. As described above, audio device 135 may indicate a state change to source device 105 using the scan response 448 or via an updated BLE announcement (e.g., BLE announcement 450). Since audio device 135 is not in a sleep state, a standard BLE announcement interval of 181.25 ms can be used to perform the BLE announcement operation. Using the scan response 448, the BLE announcement can act as a backup indication (e.g., if the scan response 448 does not reach source device 105).

[0077] A scan response 448 (or BLE announcement 450) enables the source device 105 to perform a Bluetooth paging operation, thereby establishing an S2D link 140. The audio device 135, emerging from sleep mode, can also activate the Bluetooth paging scan operation. According to one exemplary embodiment, the audio device 135 can utilize a fast scan rate. For example, a fast scan rate could be one or more scans every 100 ms, each scan lasting 11.25 ms (compared to a standard scan rate of 11.25 ms every 1.28 seconds). Similarly, a fast scan rate can be used for a predetermined amount of time, then reverting to a standard scan rate. Thus, the audio device 135 can perform a fast Bluetooth paging scan 452, during which the source device 105 can broadcast a Bluetooth paging 454. A Bluetooth connection 456 (e.g., S2D link 140) can be established using the standard classic Bluetooth connection procedure.

[0078] Figure 5 An example method 500 for disconnecting a short-range communication link upon entering a sleep state, according to various exemplary embodiments described herein, is illustrated. Method 500 involves determining, based on available information, when an audio device 135 is no longer in use. That is, method 500 involves when the audio device 135 is in an awake state (e.g., an active or ready state), but first transitions to an idle state, and then transitions to a sleep state after a predetermined period of time in the idle state. Method 500 includes operations associated with disconnecting the S2D link 140 with the source device 105, as well as subsequent detection operations. Method 500 will be described from the perspective of the audio device 135 relative to the S2D link 140.

[0079] In step 505, audio device 135 determines a state. As described above, audio device 135 can be in any of a variety of states, including a transport state, a hibernation state, a standby state, a sleep state, an idle state, a ready state, and an active state. For a first aspect of the mechanism according to an exemplary embodiment associated with entering a sleep state, audio device 135 may record idle and sleep states. In step 510, audio device 135 determines whether the state is an idle state where audio device 135 is not currently in use. If audio device 135 is not in an idle state (e.g., in an active or ready state), audio device 135 proceeds to step 515, where it uses a non-sleep state (e.g., an active or ready state). If audio device 135 is in an idle state, audio device 135 proceeds to step 525, where audio device 135 determines whether the amount of time it has been in an idle state is greater than a predetermined threshold (e.g., 30 minutes, 1 hour, 2 hours, etc.). Upon entering an idle state, audio device 135 may activate a timer corresponding to the predetermined threshold. When the timer expires, the audio device 135 can transition from an idle state to a sleep state. If the audio device 135 has been in an idle state for less than a predetermined threshold, the audio device 135 continues to 515, where it uses the idle state (non-sleep state). If the audio device 135 has been in an idle state for at least the predetermined threshold, the audio device 135 continues to 530, which corresponds to the audio device 135 being in a sleep state.

[0080] In step 530, audio device 135 determines whether S2D link 140 is still established. Even though audio device 135 is in sleep mode, source device 105 may still be in a position where S2D link 140 remains established. However, as audio device 135 transitions to sleep mode, S2D link 140 can be terminated. If S2D link 140 is still established, audio device 135 proceeds to step 535 to determine if a sniffing connection exists. A sniffing connection can be a low-power state that is not a sleep state used by a Bluetooth-enabled device such as audio device 135. If a sniffing connection exists, audio device 135 can assume that S2D link 140 will remain established. Therefore, audio device 135 returns to step 515. Accordingly, audio device 135 can use an idle state for S2D link 140.

[0081] If no sniffing connection exists, this may be an indication to dismantle S2D link 140. Therefore, audio device 135 can continue from 535 to 540, where S2D link 140 is dismantled, and audio device 135 continues to 545. Alternatively, returning to 530, source device 105 may no longer be in a position supporting S2D link 140 with audio device 135. For example, the user may remove source device 105 from audio device 135, beyond the operating distance of the short-range communication link. Therefore, S2D link 140 may have been disconnected. Accordingly, audio device 135 can continue to 545.

[0082] In step 545, audio device 135 is in a sleep state, where S2D link 140 has been torn down, and the connection operation to be continued is selected. For example, in some implementations, audio device 135 may terminate Bluetooth paging operations, Bluetooth paging scanning operations, and BLE scanning operations. Therefore, only the BLE announcement operation can be maintained. In step 550, audio device 135 updates the payload of the announcement to be broadcast using the BLE announcement operation. Specifically, the update of the payload may be based on the current state of audio device 135. Therefore, audio device 135 may update the payload of the BLE announcement to indicate to any receiving device that audio device 135 is in a sleep state. In step 555, audio device 135 may update the rate at which the BLE announcement is broadcast using the BLE announcement operation. For example, the rate may be reduced. A BLE announcement may be broadcast every 181.25 ms. However, in sleep mode, a BLE announcement may be broadcast every 362.5 ms. Accordingly, in 560, audio device 135 performs the remaining connection operations, and in 565, audio device 135 enters sleep mode.

[0083] The mechanism for a device to enter a sleep state according to an exemplary embodiment may include further operations when the source device 105 interacts with the paired audio device 108. Method 500 may be used or modified to incorporate these further operations with the paired audio device 108, as well as operations that may be performed to incorporate the B2B link 125 and the secondary audio earbud 115. For the following example, it may be assumed that the primary audio earbud 110 performs the operations of method 500 and is equivalent to the audio device 135 in relation to the source device 105.

[0084] In the first example, method 500 may incorporate further information in execution 510. For example, it may be determined whether audio device 135 is idle. Similar to audio device 135, the primary audio earbud 110 and secondary audio earbud 115 of paired audio device 108 may each include one or more sensors that generate corresponding sensor data regarding their respective use. If the sensor data generated by the primary audio earbud 110 is equivalent to the sensor data generated by audio device 135, then the sensor data generated by the secondary audio earbud 115 may represent further information. Accordingly, the sensor data from both the primary audio earbud 110 and the secondary audio earbud 115 can provide information about whether paired audio device 108 is idle, being used, or likely to be used.

[0085] In the second example, method 500 may incorporate the process of handling B2B link 125 into the main audio earbud 110. Therefore, after 560, it can be determined whether B2B link 125 is still established. If B2B link 125 is not established and has been torn down, the main audio earbud 110 may continue to 565. However, if B2B link 125 is still established, the main audio earbud 110 may change B2B link 125 to a sniffing connection with a usage time interval (e.g., 500ms or 4 watts / timeout). The BLE scan operation associated with the announcement protocol used to establish B2B link 125 can then be terminated. While performing these operations, the main audio earbud 110 may enter a sleep state.

[0086] In the third example, from the perspective of the secondary audio earbud 115, when the B2B link 125 is changed to a sniffing connection, the primary audio earbud 110 can update the sniffing settings (e.g., 500ms or 4 watts / timeout). The secondary audio earbud 115 can then terminate the BLE scan operation associated with the announcement protocol used to establish the B2B link 125. While performing these operations, the secondary audio earbud 115 can also enter a sleep state, causing the paired audio device 108 to sleep as well.

[0087] Figure 6 An example method 600 for establishing a short-range communication link upon exiting a sleep state, according to various exemplary embodiments described herein, is illustrated. Specifically, method 600 involves determining when to use audio device 135 based on received input or information from availability. That is, method 600 involves when audio device 135 wakes from a sleep state and the associated operation for establishing an S2D link 140 with source device 105. Method 600 will be described from the perspective of audio device 135 establishing an S2D link 140.

[0088] In step 602, audio device 135 is in a sleep state. Therefore, in one exemplary embodiment, audio device 135 is performing a BLE announcement operation to generate and broadcast a BLE announcement at a modified 362.5 ms interval. Audio device 135 may also passively listen for scan requests. Audio device 135 can exit the sleep state in several ways to perform subsequent operations, including receiving scan requests and determining possible uses (e.g., based on sensor data).

[0089] In step 604, audio device 135 determines whether a scan request has been received (e.g., from source device 105). In the case where audio device 135 broadcasts a BLE announcement, source device 105 may have already received the BLE announcement during a BLE scan. The BLE announcement may include an indication that audio device 135 is currently in a sleep state. However, source device 105 may transmit a scan request to audio device 135 to attempt to establish an S2D link 140. If a scan request has already been received, audio device 135 may assume that source device 105 is in a position to establish an S2D link 140. Therefore, as described above, audio device 135 may exit a sleep state and enter a non-sleep state (e.g., an idle state), and in step 606, a scan response is transmitted to source device 105 that transmitted the scan request. Before transmitting the scan response, audio device 135 may determine whether source device 105 is an authorized device or whether it is on a whitelist of devices authorized to establish an S2D link 140. Therefore, if the source device 105 transmitting the scan request is permitted and / or is on a whitelist, a scan response can be generated and transmitted back to the source device 105. The scan request may include an indication that the audio device 135 is no longer in a sleep state. When the audio device 135 receives the scan request and the basic assumption that the source device 105 is in the appropriate location, in 608, the audio device 135 may set a fast scan rate (e.g., 11.25 ms scan per 100 ms) to perform a Bluetooth paging scan operation, thereby listening for Bluetooth paging from the source device 105. Additionally, the BLE announcement operation may be updated based on whether the audio device 135 is in a non-sleep state. Therefore, in 610, the audio device 135 updates the BLE announcement payload to indicate the current state as non-sleep, and in 612, the audio device 135 updates the interval for broadcasting the BLE announcement. For example, the interval may be reduced (e.g., from 362.5 ms to 181.25 ms).

[0090] In step 614, audio device 135 determines whether a timer associated with performing a Bluetooth paging scan operation has expired. As described above, the Bluetooth paging scan operation can be performed for a predetermined amount of time. For example, with a faster, more aggressive scan rate, audio device 135 may require additional power to perform the operation. Therefore, the timer ensures that inappropriate power is not used to perform the operation. If the timer has not expired, audio device 135 proceeds to step 616, where audio device 135 determines whether a connection has been established. That is, audio device 135 may have received a Bluetooth paging from source device 105, and using the classic Bluetooth procedure, an S2D link 140 can be established. If a connection is established, audio device 135 proceeds to step 618, where audio device 135 is in both a connected state and an idle state for radio (until use or potential use is detected to transition audio device 135 to an active state or a ready state, respectively). If no connection is established in step 616, audio device 135 returns to step 614 to continue tracking the timer.

[0091] If the timer used for Bluetooth paging scanning operations at a fast scan rate expires, audio device 135 continues from 614 to 620, where it resumes to a standard scan rate (e.g., scanning 11.25 ms every 1.28 seconds). Upon exiting sleep mode, audio device 135 can continue performing Bluetooth paging scanning operations at the standard scan rate. However, it is possible that a scan request has been received, but audio device 135 will not be used, and audio device 135 should (after being woken up from receiving the scan request) be placed back into sleep mode. Therefore, in 622, audio device 135 starts a sleep timer to determine whether it wants to transition back to sleep mode. In 624, audio device 135 determines whether the sleep timer has expired. If the sleep timer has not expired, audio device 135 continues to 626, where it determines whether a connection has been established, for example, by performing a Bluetooth paging scanning operation at a standard scan rate. If a connection has been established, audio device 135 proceeds to 618 to put the radio component into a connected state and to put audio device 135 into an idle state. However, if no connection has been established, audio device 135 returns to 624.

[0092] When the sleep timer expires, audio device 135 continues from 624 to 628, where audio device 135 determines whether a usage instruction has been received. The usage instruction may be based at least in part on sensor data from one or more sensors indicating possible use of audio device 135. As described above, one or more sensors may generate sensor data associated with any / all positions, orientations, movements, etc. When a usage instruction is present, for example, based on sensor data, audio device 135 continues to 630, where audio device 135 remains in an idle state. Specifically, in 630, audio device 135 is in an unconnected idle state. At this time, a timer may be started to determine the length of time audio device 135 remains in the idle state. When the idle state has been maintained for a predetermined amount of time (e.g., 30 minutes, 1 hour, 2 hours, etc.), audio device 135 may transition from the idle state to a sleep state. Therefore, when audio device 135 is in an unconnected idle state, the device may (e.g., by determining a usage instruction) activate the timer.

[0093] If a scan request does not result in a connection using Bluetooth paging scan operations at either a fast or standard scan rate, and no usage indication is received, audio device 135 proceeds from 628 to 632, where it terminates the Bluetooth paging scan operation. At this point, despite having received a scan request, audio device 135 can determine that it is unlikely to be used. Therefore, in 634, audio device 135 increases the interval for generating and transmitting BLE announcements using BLE announcement operations. Furthermore, in 636, audio device 135 can update the payload of the BLE announcement to indicate that it is in a sleep state. Therefore, audio device 135 returns to 602, where it is in a sleep state.

[0094] Upon returning to 604, if audio device 135 does not receive a scan request, it proceeds to 638, where it determines (in a manner substantially similar to that performed in 628) whether a usage instruction exists. If no usage instruction exists, audio device 135 returns to 602, where it remains in sleep mode and connection operations continue while in sleep mode. If a usage instruction exists, audio device 135 transitions to idle mode and proceeds to 608, where it performs a Bluetooth paging scan operation using a fast scan rate.

[0095] The mechanism for a device to enter a sleep state according to an exemplary embodiment may include further operations when the source device 105 interacts with the paired audio device 108. Method 600 may be used or modified to incorporate these further operations with the paired audio device 108, as well as operations that may be performed to incorporate the B2B link 125 and the secondary audio earbud 115. For the following example, it may be assumed that the primary audio earbud 110 performs the operations of method 600 and is equivalent to the audio device 135 in relation to the source device 105.

[0096] In the first example, after step 608, the main audio earpiece 110 can initiate a BLE scan operation to establish a B2B link 125 (assuming the B2B link 125 has not yet been established). That is, the main audio earpiece 110 can utilize a set of operations when it wakes up from sleep due to receiving a scan request. Because the main audio earpiece 110 is in an idle state and not in a sleep state, the main audio earpiece 110 can then update the state of the B2B link 125 and the corresponding sniffing rate of the short-range communication link.

[0097] In the second example, if the awakened primary audio earbud 110 wants to transition back to sleep mode, the reverse set of operations will be performed. Therefore, after 636, the primary audio earbud 110 can terminate the BLE scan operation of the B2B link 125. Subsequently, if the B2B link 125 remains established, the primary audio earbud 110 can change the B2B link 125 to a sniffing connection with corresponding sniffing settings (e.g., 500ms or 4 watts / timeout). The paired audio earbud 108, including the primary audio earbud 110 and the secondary audio earbud 115, can then return to 602 to return to sleep mode.

[0098] Exemplary embodiments provide devices, systems, and methods for placing an accessory device into a low-power state, and subsequent operations performed while in a low-power state. Specifically, when it is determined that an accessory device has entered a low-power state, the accessory device terminates the connection selection operation and maintains other connection operations performed at modified intervals. This allows the accessory device to optimize power usage while in a low-power state. Exemplary embodiments also provide another mechanism for the accessory device to exit a low-power state and subsequent operations performed upon exiting the low-power state. Specifically, when the accessory device exits a low-power state based on receiving a request or determining potential usage, the accessory device updates the connection operation to establish a link with the source device.

[0099] Those skilled in the art will understand that the exemplary embodiments described above can be implemented with any suitable software or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, and mobile devices with operating systems such as iOS, Android, etc. In other examples, exemplary embodiments of the methods described above may be embodied as programs comprising lines of code stored on a non-transitory computer-readable storage medium, which, at compile time, can be executed on a processor or microprocessor.

[0100] It will be apparent to those skilled in the art that various modifications can be made to this disclosure without departing from its spirit or scope. Therefore, this disclosure is intended to cover all modifications and variations thereof, provided that such modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. A method comprising: At a wireless device having a short-range communication link with a source device, wherein the wireless device operates in a first power state when the short-range communication link is connected: Based on input from the sensors of the wireless device, identify the conditions related to the wireless device; Based on the identified situation, the wireless device is placed in a second power state, which is lower than the first power state, and the short-range communication link connection is maintained in the second power state. Based on the identified situation, start the timer; as well as When the timer reaches a predetermined value, the short-range communication link is disconnected and the wireless device is placed in a third power state, which is a lower power state than the second power state.

2. The method of claim 1, wherein the sensor comprises one of a motion sensor, an optical sensor, or an orientation sensor.

3. The method according to claim 1, further comprising: When in the third power state, a low-power declaration is sent at a first rate that is lower than the declaration sent in the first power state or the second power state.

4. The method of claim 3, wherein the low power declaration includes a payload indicating that the wireless device is in the third power state.

5. The method according to claim 3, further comprising: When in the third power state, the scanning and paging activities of the wireless device are suspended.

6. The method of claim 3, wherein the low power declaration includes a Bluetooth Low Energy (BLE) declaration.

7. A processor for a wireless device having a short-range communication link with a source device, wherein when the short-range communication link is connected, the wireless device operates in a first power state, and the processor is configured to perform operations including: Based on input from the sensors of the wireless device, identify the conditions related to the wireless device; Based on the identified situation, the wireless device is placed in a second power state, which is lower than the first power state, and the short-range communication link connection is maintained in the second power state. Based on the identified situation, start the timer; as well as When the timer reaches a predetermined value, the short-range communication link is disconnected and the wireless device is placed in a third power state, which is a lower power state than the second power state.

8. The processor according to claim 7, wherein the operation further comprises: When in the third power state, a low-power declaration is sent at a first rate that is lower than the declaration sent in the first power state or the second power state.

9. The processor of claim 8, wherein the low-power declaration includes a payload indicating that the wireless device is in the third power state.

10. The processor of claim 8, further comprising: When in the third power state, the scanning and paging activities of the wireless device are suspended.

11. The processor of claim 8, wherein the low-power declaration includes a Bluetooth Low Energy (BLE) declaration.

12. A wireless device, comprising: A radio component is configured to communicate with a source device via a short-range communication link, wherein the radio device operates in a first power state when the short-range communication link is connected; as well as The processor is communicatively coupled to the radio component and configured to perform operations including the following: Based on input from the sensors of the wireless device, identify the conditions related to the wireless device; Based on the identified situation, the wireless device is placed in a second power state, which is lower than the first power state, and the short-range communication link connection is maintained in the second power state. Based on the identified situation, start the timer; as well as When the timer reaches a predetermined value, the short-range communication link is disconnected and the wireless device is placed in a third power state, which is a lower power state than the second power state.

13. The wireless device of claim 12, wherein the sensor comprises one of a motion sensor, an optical sensor, or an orientation sensor.

14. The wireless device of claim 12, further comprising: When in the third power state, a low-power declaration is sent at a first rate that is lower than the declaration sent in the first power state or the second power state.

15. The wireless device of claim 14, wherein the low power declaration includes a payload indicating that the wireless device is in the third power state.

16. The wireless device of claim 14, further comprising: When in the third power state, the scanning and paging activities of the wireless device are suspended.

17. The wireless device of claim 14, wherein the low power declaration includes a Bluetooth Low Energy (BLE) declaration.

Images