Patent Application
20230308976
The disclosure herein relates generally to components, systems, and methods for seamlessly switching communications between various Bluetooth-enabled devices.
Bluetooth-enabled devices, including for example headphones, wireless speakers, and other accessories, have grown in popularity over the years. At the same time, numerous devices, such as cars, televisions, radios, computers, mobile phones, and/or smartphones are also Bluetooth-enabled and are capable of connecting to Bluetooth devices, including accessory devices. In order for a Bluetooth-enabled device to communicate with another Bluetooth-enabled device, the two devices typically must first follow a Bluetooth pairing process, in which the devices exchange identification information and other parameters in a handshaking procedure. In order to connect the Bluetooth-enabled device to a different Bluetooth-enabled device, the Bluetooth-enabled accessory may need to disconnect from the first device and then connect with the second device. This process can be lengthy, time consuming, and frustrating for users that wish to quickly switch Bluetooth communications between multiple devices.
Throughout the drawings, like reference numbers are used to depict the same or similar elements, features, and structures. The drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating aspects of the disclosure. In the following description, some aspects of the disclosure are described with reference to the following drawings, in which:
The following detailed description refers to the accompanying drawings that show, by way of illustration, specific details and aspects in which the disclosure may be practiced. One or more aspects are described in sufficient detail to enable those skilled in the art to practice the disclosure. Other aspects may be utilized and structural, logical, and electrical changes may be made without departing from the scope of the disclosure. The various aspects described herein are not necessarily mutually exclusive, as some aspects can be combined with one or more other aspects to form new aspects. Various aspects are described in connection with methods and various aspects are described in connection with devices and vice versa. However, it may be understood that aspects described in connection with methods may similarly apply to the devices, and vice versa. Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures.
As discussed in more detail below, the present disclosure provides for a system that allows a Bluetooth-enabled device (e.g., an accessory device) to seamlessly switch its Bluetooth communications between various Bluetooth-enabled devices (e.g., host devices) without having to re-pair to the newly-selected device. This solution improves speed and continuity when switching, for example, a Bluetooth accessory device's connection from one host device to another host device.
Prerequisite to Bluetooth communication of user data in the application layer, Bluetooth devices must follow a handshaking process called “pairing.” The pairing process involves the exchange and verification of information between two Bluetooth-enabled devices. During pairing of two devices, the two devices establish a relationship by creating a shared secret key known as a “link key.” After both devices store the same link key, they are “paired,” and they may use the link key for the exchange of user data over the now-established Bluetooth communication interface. This pairing and communication mode may also be known as “Bluetooth classic” mode.
This type of pairing process often involves some level of user interaction so that the user can confirm that the correct device has been selected for pairing and that the two devices should commence with Bluetooth communications. For small accessory devices (such as Bluetooth-enabled headphones) without a display, the pairing process can be particularly cumbersome because without a display, the user may not know which host device the accessory is pairing with or which host device the accessory is connecting to. This can be problematic when there are many host devices with which the accessory may connect. As a result, the user must usually follow the pairing process each time the accessory device changes its Bluetooth connection from one host to another.
In operation, for example, headphones 110 may pair with television 120 to enable data communications between the two devices using Bluetooth communication protocols. Once the devices are paired, a Bluetooth communication interface 140b is established, and the television 120 may provide a stream of audio data to the headphones 110 using Bluetooth communication over Bluetooth communication interface 140b, which the headphones 110 interprets and then outputs as audio to its speakers 114. Alternatively, as another example, headphones 110 may pair with CD player 130 to enable data communications between the two devices using Bluetooth communication protocols. Once the devices are paired, a Bluetooth communication interface 140c is established, and the CD player 130 may provide a stream of audio data to the headphones 110 using Bluetooth communication over Bluetooth interface 140c, which the headphones 110 interprets and then outputs audio to its speakers 114. In these exemplary scenarios, the television 120 and CD player 130 may be referred to as host devices and the headphones 110 may be referred to as an accessory device. Typically, an accessory device, such as headphones 110, may be connected with one host device at a time. This means, for example, that headphones 110 may need to disconnect with television 120 in order to connect with and communicate with CD player 130. As explained earlier, the devices must first be paired in order for the devices to use the correct link key established for Bluetooth communications between the two connected devices.
In some cases, a Bluetooth-enabled device may communicate with another Bluetooth-enabled device using what is called Bluetooth low energy mode (also known as “Bluetooth LE” or “BLE”). In this mode, two devices may have limited communication capabilities as compared to pairing in Bluetooth classic mode described above. While a Bluetooth-enabled device may generally only be paired in Bluetooth classic mode with one other device, it may be paired with a second device if one of the pairings is in BLE mode. Referring to
Bluetooth devices, such as headphones 110, may contain a memory for storing information about paired devices and/or previously paired devices. The information may include, for example, an identifier that uniquely identifies the device such as a media access control address (“MAC address”) of a paired device, the link key established with the paired device, the name of the paired device, other information about the paired device, or other information about the communications interface established between the two devices. This type of information may be stored as a collection of information/identifiers in memory using commonly-understood database techniques, by storing, for example, each known device and its associated information/identifiers in fields and records of a database. By storing this information, the headphones 110 may, in a sense, remain “paired” with more than one Bluetooth device because by retaining pairing information for Bluetooth devices with which the headphones 110 have previously paired, the headphones 110 may easily switch Bluetooth communications from one Bluetooth device to another Bluetooth device without having to negotiate new pairing information in a re-repairing process.
Turning to
APP 104 may use the information received from headphones 110 to display certain information to a user of the APP 104 of smartphone 110. For example, APP 104 may display a list of known devices that was generated from the information received from headphones 110. In the example shown in
APP 104 may report the selected device to headphones 110 using, for example, the Bluetooth communication interface established between the two devices. The APP 104 may transmit the selected device to headphones 110, for example, at regular time intervals, when the selection indicator 108 is moved to a newly-selected device, when requested by the headphones 110, when a refresh is requested by the user, or in any other manner.
Headphones 110 may receive information from the APP 104, indicating which device is the selected device. Based on the received information, headphones 110 may, for example, switch its Bluetooth communications to the selected device. Using
Importantly, the headphones 110 need not re-pair with the newly-selected device in order to communicate with it using Bluetooth communications. Although the headphones 110 would normally need to re-pair with the selected device before switching its Bluetooth communications from one device (e.g., television 120) to a different device (e.g., CD player 130), no re-pairing is required. Having previously paired with each Bluetooth-enabled device and stored information about each pairing in its memory, headphones 110 are able to seamlessly switch from communicating with the television 120 as the selected device for Bluetooth communications to communicating with CD player 130 as the newly-selected device for Bluetooth communications, without being disrupted by the pairing process. If Bluetooth communications with the newly-selected device are unsuccessful (perhaps, for example, the newly-selected device is no longer within Bluetooth communication range of the headphones 110), then the headphones 110 may inform the APP 104 that the Bluetooth communication with the newly-selected device was unsuccessful. The headphones 110 may wait a certain amount of time (e.g., a number of seconds) and/or retry a certain number of times before informing the APP 104 of the unsuccessful connection. In the case of unsuccessful Bluetooth communications with the newly-selected device, the headphones 110 may revert Bluetooth communications to be with the previously selected device.
The benefits of this seamless method means the user can quickly and easily switch among using different Bluetooth devices without the cumbersome interruption of the pairing process. For example, a user of smartphone 100 may select CD player 130 as the selected device in order to listen to a music audio stream that is generated by the CD player 130, transmitted to the headphones 110 using Bluetooth communications, and output on speakers 114 of headphones 110. While enjoying the music, the user may see something of interest on the television 120, and would like to listen to the audio stream from the television 120 on speakers 114 of headphones 110. To make the switch easily and quickly without having to re-pair the television 120 to the headphones 110, the user may select TV icon 106 in the APP 104, as shown in
The following examples pertain to various exemplary embodiments.
Example 1 is a method for seamless handover of communications. The method includes receiving at an accessory a first host identifier that uniquely identifies a first host for communications. The method also includes receiving at the accessory a second host identifier that uniquely identifies a second host for communications. The method also includes storing in the accessory the first host identifier and the second host identifier as identifier information. The method also includes receiving at a mobile device at least a portion of the identifier information. The method also includes displaying at the mobile device a list of hosts based on the at least a portion of the identifier information. The method also includes selecting from among the list of hosts the first host as a selected host. The method also includes instructing the accessory to communicate with the selected host without re-pairing with the selected host. The method also includes selecting from among the list of hosts the second host as a newly-selected host. The method also includes instructing the accessory to switch communications from the selected host to the newly-selected host without re-pairing with the newly-selected host.
In example 2, the subject matter of example 1 may optionally include that the communications are Bluetooth communications.
In example 3, the subject matter of any one of examples 1 to 2 may optionally include that instructing the accessory to communicate with the selected host without re-pairing with the selected host includes instructing the accessory to communicate using Bluetooth communications without re-pairing with the selected host.
In example 4, the subject matter of any one of examples 1 to 3 may optionally include that receiving at the accessory the first host identifier includes pairing the first host with the accessory.
In example 5, the subject matter of any one of examples 1 to 4 may optionally include that the first host identifier includes a MAC address of the first host.
In example 6, the subject matter of any one of examples 1 to 5 may optionally include that the first host identifier includes a name of the first host.
In example 7, the subject matter of any one of examples 1 to 6 may optionally include that the identifier information includes a collection of host identifiers, wherein each host identifier in the collection of host identifiers corresponds to a different host.
In example 8, the subject matter of any one of examples 1 to 7 may optionally include that instructing the accessory to communicate with the selected host includes transmitting identifier information corresponding to the selected host to the accessory.
In example 9, the subject matter of any one of examples 1 to 8 may optionally include instructing the accessory to disconnect from the selected host when the accessory switches communications from the selected host to the newly-selected host.
In example 10, the subject matter of any one of examples 1 to 9 may optionally include that the mobile device receives the at least a portion of the identifier information using Bluetooth low energy communication mode with the accessory.
In example 11, the subject matter of any one of examples 1 to 10 may optionally include that instructing the accessory to communicate via communication with the selected host includes instructing the accessory to communicate using Bluetooth classic mode communication with the host.
In example 12, the subject matter of any one of examples 1 to 11 may optionally include that receiving at the mobile device the at least a portion of the identifier information includes receiving the at least a portion of the identifier information from the accessory using Bluetooth low energy mode communication.
In example 13 is a mobile device that includes a communication module configured to pair with and receive identifier information from an accessory. The identifier information comprises a first host identifier and a second host identifier. The first host identifier uniquely identifies a first host and the second host identifier uniquely identifies a second host. The mobile device also includes a user interface configured to allow selection of a selected host from a list of hosts derived from the identifier information. The communication module is also configured to send an instruction to the accessory indicating that the accessory is to communicate with the selected host without re-pairing with the selected host.
In example 14, the subject matter of example 13 may optionally include that the communication module is further configured to use Bluetooth low energy mode communication to send the instruction to the accessory.
In example 15, the subject matter of any one of examples 13 to 14 may optionally include that the first host and the second host were previously paired with the accessory.
In example 16, the subject matter of any one of examples 13 to 15 may optionally include that the first host identifier includes a MAC address of the first host.
In example 17, the subject matter of any one of examples 13 to 16 may optionally include that the first host identifier includes a name of the first host.
In example 18, the subject matter of any one of examples 13 to 17 may optionally include that the instruction includes identifier information corresponding to the selected host.
In example 19, the subject matter of any one of examples 13 to 18 may optionally include that the first host includes a Bluetooth-enabled television and the accessory comprises Bluetooth-enabled headphones.
Example 20 is an accessory that includes a communication module configured to receive during a first pairing process a first host identifier. The communication module is further configured to receive during a second pairing process a second host identifier. The first host identifier uniquely identifies the first host for communications and the second host identifier uniquely identifies the second host for communications. The accessory also includes an identification database that is configured to store the first host identifier and second host identifier as identifier information. The communication module is also configured to send at least a portion of the identifier information from the identification database to a mobile device. The communication module is also configured to receive from the mobile device a first message indicating the first host is a selected host. The first message also indicates that the accessory is to communicate with the selected host without repeating the first pairing process. The communication module is also configured to receive from the mobile device a second message indicating the second host is a newly-selected host. The second messages also indicates that the accessory is to communicate with the newly-selected host without repeating the second pairing process.
It can be understood that the described system can be implemented by means of hardware (e.g. a hard-wired circuit) and/or software (e.g. code segments or an entire application). For example, an application (also referred to as a “program”) may be or be provided which has corresponding code segments (e.g. program code). The code segments may be executed on a processor and/or by means of a circuit which has the processor or multiple processors, and any, all, or portions thereof may execute one or more portions of the code segments.
The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any example or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other examples or designs.
The words “plurality” and “multiple” in the description or the claims expressly refer to a quantity greater than one. The terms “group (of)”, “set [of]”, “collection (of)”, “series (of)”, “sequence (of)”, “grouping (of)”, etc., and the like in the description or in the claims refer to a quantity equal to or greater than one, i.e. one or more. Any term expressed in plural form that does not expressly state “plurality” or “multiple” likewise refers to a quantity equal to or greater than one.
The term “processor” as, for example, used herein may be understood as any kind of entity that allows handling of data, signals, etc. These may be handled according to one or more specific functions executed by the processor.
A processor may thus be or include an analog circuit, digital circuit, mixed-signal circuit, logic circuit, processor, microprocessor, Central Processing Unit (CPU), Graphics Processing Unit (GPU), Digital Signal Processor (DSP), Field Programmable Gate Array (FPGA), integrated circuit, Application Specific Integrated Circuit (ASIC), as examples, or any combination thereof. Any other kind of implementation of the respective functions, which will be described below in further detail, may also be understood as a processor or logic circuit. It is understood that any two (or more) of the processors or logic circuits detailed herein may be realized as a single entity with equivalent functionality, and conversely that any single processor or logic circuit detailed herein may be realized as two (or more) separate entities with equivalent functionality. It is understood that one or more of the systems detailed herein may be performed (e.g., realized) by a processor, may by one or more specific functions executed by the processor.
The term “system” detailed herein may be understood as a set of interacting elements, the elements may be, by way of example and not of limitation, one or more physical components (e.g., processors, transmitters and/or receivers) and/or one or more digital components (e.g., code segments, instructions, protocols). Generally, the system may include one or more functions to be operated (also referred to as “operating functions”) of which each may be controlled for operating the whole system.
A processor may be configured, e.g., by the code segments (e.g., software), to control the operation of a system (e.g., its operating sequence or the like) and may optionally include a memory to, for example, store code segments that represent the functions or processing that the controller performs. Additionally or alternatively, the memory may store one or more models, criterion, rules, and algorithms, as examples, as detailed herein. It is understood that any two (or more) of the controllers detailed herein may be realized as a single controller with substantially equivalent functionality, and conversely that any single controller detailed herein may be realized as two (or more) separate controller with substantially equivalent functionality. Additionally, references to a “controller” may refer to two or more controllers that collectively form a single controller.
The term “software” refers to any type of executable instruction, including firmware.
Various aspects of this disclosure may utilize or be related to wireless communication technologies. While some examples may refer to specific wireless communication technologies, the examples provided herein may be similarly applied to various other wireless communication technologies, both existing and not yet formulated, particularly in cases where such wireless communication technologies share similar features as disclosed regarding the following examples.
While the above descriptions and connected figures may depict electronic device components as separate elements, skilled persons will appreciate the various possibilities to combine or integrate discrete elements into a single element. Such may include combining two or more circuits from a single circuit, mounting two or more circuits onto a common chip or chassis to form an integrated element, executing discrete software components on a common processor core, etc. Conversely, skilled persons will recognize the possibility to separate a single element into two or more discrete elements, such as splitting a single circuit into two or more separate circuits, separating a chip or chassis into discrete elements originally provided thereon, separating a software component into two or more sections and executing each on a separate processor core, etc. Also, it is appreciated that particular implementations of hardware and/or software components are merely illustrative, and other combinations of hardware and/or software that perform the methods described herein are within the scope of the disclosure.
It is appreciated that implementations of methods detailed herein are exemplary in nature, and are thus understood as capable of being implemented in a corresponding device. Likewise, it is appreciated that implementations of devices detailed herein are understood as capable of being implemented as a corresponding method. It is thus understood that a device corresponding to a method detailed herein may include one or more components configured to perform each aspect of the related method.
All acronyms defined in the above description additionally hold in all claims included herein.
While the invention has been particularly shown and described with reference to specific embodiments, it should be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. The scope of the invention is thus indicated by the appended claims and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/SG2021/050301 | 5/31/2021 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 63078273 | Sep 2020 | US |
