BLE link cluster discovery, establishment and termination

Abstract

In an example, a method includes broadcasting an advertisement packet from a broadcaster Bluetooth device (1102), where the advertisement packet includes one or more connection parameters (1112) for one or more links (1110) in a link cluster (1106). The method also includes receiving, at the broadcaster Bluetooth device (1102), a link cluster coordination request from a scanner Bluetooth device (1104), wherein the link cluster coordination request includes one or more connection parameters (1112) for a link (1110) in the link cluster (1106).

Description

Background Art

[0001] Bluetooth Low Energy (BLE) is a wireless communication technology that can be used in various applications and devices, such as in healthcare, fitness, security, home entertainment, and communication devices. BLE communication technology provides lower power consumption of communication devices compared to Bluetooth or other wireless communication technologies, while also maintaining similar wireless communication range and coverage. Compared to other wireless communication technologies, reduced power consumption of communication devices can be provided through simpler modulation schemes. BLE communication technology is based on the BLE communication standard supported by various operating systems (OS), including ANDROID, IOS, WINDOWS, MACOS, LINUX, and other OS to operate communication devices. Summary of the invention

[0002] In at least one example described, a method includes broadcasting an advertisement packet from a broadcaster Bluetooth device, wherein the advertisement packet includes one or more connection parameters for one or more links in a link cluster. The method also includes receiving, at the broadcaster Bluetooth device, a link cluster coordination request from a scanner Bluetooth device, wherein the link cluster coordination request includes one or more connection parameters for the links in the link cluster.

[0003] In at least one example described, a system includes a scanner Bluetooth device configured to scan for advertisement packets from a broadcaster Bluetooth device, wherein the advertisement packets include one or more connection parameters for one or more links in a link cluster. The scanner Bluetooth device is further configured to transmit a link cluster coordination request from the scanner Bluetooth device to the broadcaster Bluetooth device in response to receiving the advertisement packets, wherein the link cluster coordination request includes the one or more connection parameters for the links in the link cluster.

[0004] In at least one example described, a method includes receiving a Generic Access Protocol (GAP) connection request at a broadcaster Bluetooth device. The method also includes transmitting a GAP connection response from the broadcaster Bluetooth device to a scanner Bluetooth device. The method includes receiving an enable message from a scanner Bluetooth device at the broadcaster Bluetooth device to enable Generic Attribute (GATT) notifications. The method also includes, in response to receiving the enable message, transmitting GATT notifications about connection parameters of one or more links in a link cluster from the broadcaster Bluetooth device to the scanner Bluetooth device. The method includes receiving a disable message from a scanner Bluetooth device at the broadcaster Bluetooth device to disable GATT notifications. The method also includes, in response to receiving the disable message, disabling transmission of GATT notifications about one or more links in the link cluster from the broadcaster Bluetooth device to the scanner Bluetooth device. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 is a block diagram of processing and communication systems in various embodiments.

[0006] Figure 2 A Bluetooth device (eg, a BLE device) that is communicatively coupled to one or more other devices in various examples.

[0007] Figure 3 is a block diagram of a BLE network in various examples.

[0008] Figure 4A is a diagram of a network with a link cluster between two Bluetooth devices in various examples.

[0009] Figure 4B is a diagram of a network with link clustering between three Bluetooth devices in various examples.

[0010] Figure 4C is a diagram of a network with link clustering between three Bluetooth devices in various examples.

[0011] Figure 5 is a block diagram of a state machine of a BLE device in various examples.

[0012] Fig. 6A The discovery phase process for link clustering in various examples.

[0013] Figure 6B and 6C Timing diagram for link cluster discovery signaling in various examples.

[0014] Figure 7 Flow for the connection and termination phases of a link cluster in various examples.

[0015] Figure 8 Configure file flows for common properties used for link clusters in various instances.

[0016] Fig. 9 Flowchart of a method for establishing a link cluster in various examples.

[0017] Fig.10 Flowcharts of methods for controlling a link cluster having a common attribute profile in various examples.

[0018] Fig.11 Program flow for link cluster coordination in various instances.

[0019] Fig.12 Program flow for link cluster control and management in various instances.

[0020] Fig.13 Flowchart of a method for managing link cluster connection parameters in various examples.

[0021] Fig.14Flowchart of a method for power management in a link cluster in various examples.

[0022] The same reference numbers or other reference designators are used in the drawings to designate the same or similar features (functionally and / or structurally). DETAILED DESCRIPTION

[0023] The Bluetooth (BT) Low Energy (BLE) standard defines a standard hierarchy of components. The hierarchy includes a BLE controller and a BLE host. Some examples may include a BLE PHY (physical) layer and a radio frequency (RF) front end. A BLE application resides on top of the BLE controller and the BLE host. The BLE controller handles all tasks required to keep the connection active. A unicast BLE connection consists of two devices. BLE devices communicate on a channel called a BLE data channel group at constant intervals (i.e., connection events). During a connection event, a device called a central handles one or more connection events by transmitting one or more packets to a device called a peripheral and receiving the packets. According to the BLE communication standard in Bluetooth Core Specification Verification 5.3, which is incorporated herein by reference, data transmission can be carried via a link or data channel group, which is a connection established between communication devices in the form of messages or packets to exchange data. Each data channel within a channel group has a unique frequency band between 2.4 gigahertz (GHz) and 2.4835 GHz, and therefore each of those channels has unique characteristics. A link between two devices is a superset of a connection event, where a connection event is every instance of communication between the two devices.

[0024] Current Bluetooth standards can support multiple central devices and multiple peripheral devices operating simultaneously. In one case, a central device can connect to multiple peripheral devices without connection event overlap. In another case, a peripheral device can connect to multiple central devices simultaneously without connection event overlap. A connection is established based on peripheral advertising and central scanning. If a connection is established, the peripheral advertisement is updated to enable the peripheral device to establish an additional connection with another central device.

[0025] The current BLE standard limits the central device to establish more than one link with a single peripheral device. In the example herein, a link cluster is described, which is a collection of two or more links between two BLE devices. A link cluster includes two or more links with dependencies or coordination between the links. A link cluster may include a collection of links between any number of devices. Link cluster discovery, establishment, and termination procedures are described herein. These procedures may be based on air signal exchange or host controller interface (HCI) signal exchange. In other examples herein, link cluster management and control procedures are described. Coordination procedures may be used to set or update connection parameters of a specific link or several coupled links within a link cluster. Link cluster signaling exchanges may be performed via a link in a link cluster. In one example, link cluster signaling may support link cluster power management, wherein the per-channel power level within a channel group may be limited. In some examples, link clusters allow BLE systems as described herein to optimize the power consumption of link cluster devices, reduce latency, and increase system-level throughput.

[0026] Figure 1 is a block diagram of a processing and communication system 100 that can be used to process and exchange data in various examples herein. The processing and communication system 100 can be a BLE device capable of establishing a connection to transmit and receive messages or packets consistent with the BLE communication standard. For example, the processing and communication system 100 can be a central device, such as a router or BLE hub, a computer device, or a smart phone, or can be a peripheral device, such as an Internet of Things (IoT) device, a sensor, or other BLE device capable of establishing a connection with a second BLE device or a network such as the Internet. In some examples, the processing and communication system 100 can be a system on a chip (SoC), an electronic circuit board, or a computer card of a BLE device.

[0027] The processing and communication system 100 includes hardware components for establishing a connection and transmitting and receiving data consistent with the BLE communication standard. Figure 1 As shown, the processing and communication system 100 may include one or more processors 101 and one or more memories 102. The processing and communication system 100 may also include one or more transceivers 103 and one or more antennas 104 for establishing wireless connections. These components may be coupled via a bus 105 or in any other suitable manner. Figure 1 , an example is shown in which components are coupled via a bus 105.

[0028] The processor 101 is configured to read and execute computer-readable instructions. For example, the processor 101 is configured to call and execute instructions in a program stored in the memory 102, including the instruction 106. In response to the processor 101 transmitting data, the processor 101 drives or controls the transceiver 103 to perform transmission. The processor 101 also drives or controls the transceiver 103 to perform reception in response to the processor 101 receiving data. Therefore, the processor 101 can be regarded as a control central device for performing transmission or reception of data, and the transceiver 103 is an executor for performing transmission and reception operations.

[0029] In some examples, memory 102 is coupled to processor 101 via bus 105. In other examples, memory 102 is integrated with processor 101. Memory 102 is configured to store various software programs and / or multiple instruction groups, including instruction 106. Memory 102 may include one or more storage devices. For example, memory 102 includes high-speed random access memory and / or may include non-volatile memory, such as one or more disk storage devices, flash memory, another non-volatile solid-state storage device or pseudo-static random access memory (PSRAM). Memory 102 may store an OS such as ANDROID, IOS, WINDOWS or LINUX. Memory 102 may further store a network communication program. The network communication program is used to perform communication with one or more attached devices, one or more user devices or one or more network devices. Memory 102 may further store a user interface program. The user interface program displays the content of the application through a graphical interface and receives data or operations performed by the user on the application via input controls (such as menus, dialog boxes or physical input devices (not shown)). The memory 102 is configured to store instructions 106 for implementing the various methods and processes provided in the various examples of this specification.

[0030] The transceiver 103 includes a transmitter and a receiver. The transceiver 103 is configured to transmit one or more signals provided by the processor 101. The transceiver 103 is also configured to receive one or more signals from other devices or equipment. In this example, the transceiver 103 can be regarded as a wireless transceiver. The antenna 104 can be configured to implement the exchange of wireless communication signals between the transceiver 103 and a network or another system or device.

[0031] The processing and communication system 100 may also include another communication component, such as a global positioning system (GPS) module, a cellular module, a Bluetooth or BLE module, a Zigbee module, a long-term evolution (LTE), a LTE-machine type communication (LTE-M), a narrowband LTE (NB-LTE), a sub-gigahertz, (Sub-Gigahertz) communication (sub1G), Wi-SUN, IEEE 802.15.4 or a wireless fidelity (WI-FI) module. The processing and communication system 100 may also support another wireless communication signal, such as a satellite signal or a shortwave signal. The processing and communication system 100 may also be provided with a wired network interface or a local area network (LAN) interface to support wired communication.

[0032] In various examples, the processing and communication system 100 may also include an input / output interface (not shown) for implementing communication between the processing and communication system 100 and one or more input / output devices (not shown). Examples of input / output devices include audio input / output devices, key input devices, displays, and the like. The input / output devices are configured to implement interaction between the processing and communication system 100 and a user or an external environment. The input / output devices may also include cameras, touch screens, sensors, and the like. The input / output devices communicate with the processor 101 through a user interface.

[0033] Figure 1 The processing and communication system 100 shown in FIG. 1 is an example of a processing and communication system or device. During actual application, the processing and communication system 100 may include more or fewer components. The processing and communication system 100 may be part of a BLE device connected to other BLE devices.

[0034] Figure 2 An example of a Bluetooth device 200 (e.g., a BLE device) communicatively coupled to one or more other devices 202 via a communication connection 220 is depicted in various examples herein. The communication connection 220 can be a channel as described herein. The one or more other devices 202 include any device configured to communicate with the Bluetooth device 200. The communication connection 220 can be any connection medium, link, link cluster one or more channel groups, one or more channels, or one or more connection events, such as a wireless communication connection. In some examples, the communication connection 220 is a link cluster including two or more links.

[0035] The Bluetooth device 200 includes a Bluetooth application 206, a Bluetooth host 208, a Bluetooth host controller interface 210, two Bluetooth controllers 212A and 212B, two Bluetooth PHY layers 214A and 214B, and two RF front ends 216A and 216B. The Bluetooth device 200 may include two or more separate PHY layers that are connected to a single logical link control layer and a single media access control layer by a single interface. The Bluetooth PHY layer 214A and the RF front end 216A may be configured to form a first link with another device, and the Bluetooth PHY layer 214B and the RF front end 216B may be configured to form a second link with another device, wherein the first and second links are separate links. In some examples, each of the RF front ends 216A and 216B may include one or more antennas and other transceiver circuit systems to communicate with another device. Other examples may include a single controller 212 with multiple Bluetooth PHY layers 214 , a single controller 212 with a single Bluetooth PHY layer 214 and multiple RF front ends 216 , or a single controller 212 with a single Bluetooth PHY layer 214 and a single RF front end 216 .

[0036] In some instances, Figure 2 The Bluetooth device 200 corresponds to the above reference Figure 1 The components described in the communication system 100 include the components described above and as described in reference Figure 1 Therefore, the communication system 100 described herein is configured as described in Figure 2 The Bluetooth device 200 can be regarded as Figure 1 In some examples, one or more other devices 202 may correspond to the above referenced communication system 100. Figure 1 The components described in the communication system 100 of the present invention include the components described above and as described in the reference Figure 1 In some examples, one or more other devices 202 may include components similar to those of Bluetooth device 200.

[0037] The Bluetooth device 200 is configured to provide a Bluetooth controller 212 with link cluster channel operating parameters 224. Data 226 may include any data related to communication between devices, such as performance indicators related to channels within the channel group (e.g., power consumption, average and peak throughput, modem characteristics, modulation and coding scheme (MCS), packet level restrictions, responsiveness, etc.). Example details of selecting and changing channels can be found in commonly assigned U.S. patent application serial number 17 / 828,225 filed on May 31, 2022, entitled "Frequency Changes During Connection Events," which is incorporated herein by reference in its entirety.

[0038] In some examples, the Bluetooth device 200 may use an advertising program to share connection parameters for a link within a link cluster and coordinate connection events between two or more devices. The connection parameters may include limitations or capabilities of the Bluetooth device 200. In the examples herein, the device of the advertisement may be referred to as a broadcaster. Other devices 202 (e.g., a second Bluetooth device 202 and / or a third Bluetooth device 202) may receive these advertisements and negotiate a communication connection with the Bluetooth device 200. The device receiving the advertisement may be referred to as a scanner herein. The communication connection may be one or more links within a link cluster. After the link is established, the broadcaster may be referred to as a peripheral device, and the scanner may be referred to as a central device. In some examples, other devices 202 may accept the advertised connection parameters for the link within the link cluster, or may change the connection parameters and then negotiate a communication connection with the Bluetooth device 200. By using the advertising program, the communication connection may be made faster or with lower power usage than other programs.

[0039] In the examples herein, the Bluetooth device 200 may participate in the discovery, establishment, management and termination of the links within the link cluster. The connection parameters of one or more links within the link cluster may be selected, negotiated and updated as described herein. In some examples, one or more of the links within the link cluster may be terminated. The operation settings (channel settings, modem characteristics, power management, power level, duration, anchor point, etc.) of one or more links within the link cluster may be modified as described herein. In some examples, the signaling operation may set or update the parameters of the link or multiple links in the link cluster, such as PHY (physical) parameters, channel maps and channel selection, encryption parameters, modem characteristics, MCS, packet level restrictions, connection event restrictions and power management restrictions (e.g., transmission power restrictions). The links within the link cluster have a level of awareness or coordination with each other to form a link cluster. Each device may manage and coordinate its own links to effectively manage these links as part of a link cluster.

[0040] Figure 3 300 in various examples herein. BLE network 300 includes devices 302, 304, 306, 308, 310, 312, 314, and 316. In this example, devices 304, 306, and 312 are central devices, while devices 302, 308, 310, 314, and 316 are peripheral devices. BLE network 300 also includes subnetworks 320A, 320B, and 320C. Subnetwork 320A includes devices 302, 304, and 306. Subnetwork 320B includes devices 306, 308, and 310. Subnetwork 320C includes devices 308, 310, 312, 314, and 316.

[0041] In one example, BLE network 300 is a multi-peripheral multi-central network. In multi-central mode, more than one central device can be connected to a single peripheral device. As an example, peripheral device 308 is connected to both central device 306 and central device 312. In multi-peripheral mode, more than one peripheral device can be connected to multi-central devices. As an example, peripheral devices 308 and 310 are connected to central device 306. In BLE network 300, any device can connect to any other device using a link cluster of two or more links. In other words, Figure 3 Any connection shown may be a multi-link connection (ie, a cluster of links) between two devices.

[0042] Figure 4A 4 is a diagram of a network 400 with a link cluster between two Bluetooth devices in various examples herein. Network 400 includes device 402 and device 404. In one example, device 402 may be a central device and device 404 may be a peripheral device. Device 402 is connected to device 404 via links 406A and 406B. In this example, links 406A and 406B form a link cluster 408. In other examples, link cluster 408 may include more than two links. Links 406A and 406B in link cluster 408 have awareness and coordination levels to form a link cluster. Devices 402 and 404 can communicate via multiple links 406A and 406B by canceling communication in frequency and / or time. For example, device 402 can send a first packet via link 406A by encoding a first packet in a first frequency channel, and device 402 can send a second packet via link 406B by encoding a second packet in a second frequency channel. The device 402 may be configured to transmit the first and second packets at the same time, at partially overlapping times, or at completely offset times.

[0043] Network 400 can use any suitable technology to transmit data between device 402 and device 404. One technology is synchronous replication mode, in which the same data is transmitted on link 406A and link 406B. In replication mode, the transmitter sends a copy of each frame via multiple links. In other examples, more than two links can connect device 402 and device 404. In replication mode, the receiver can obtain a frame on a first link and then discard the copy of the frame received on a subsequent link. Replication mode increases the robustness of the network. Another technology is joint mode. In joint mode, a transmission frame is sent via multiple available links, but a copy of the frame is not sent. Joint mode reduces transmission delay. The examples described herein can use either mode or both modes.

[0044] Figure 4B430 is a network 430 having a link cluster between three Bluetooth devices in various examples herein. Network 430 includes devices 432, 434, and 436. In various examples, each of devices 432, 434, or 436 may be a central device or a peripheral device. In this example, device 432 is connected to device 434 via link 438. Device 432 is connected to device 436 via link 440. Device 434 is connected to device 436 via links 442A and 442B. Network 430 also includes link cluster 444. Devices 432, 434, and 436 may coordinate links 438, 440, 442A, and 442B to generate link cluster 444. Each device may coordinate its own link to effectively manage these links as part of link cluster 444. In the examples herein, additional links may be added between any two devices. Network 430 is an example of a link cluster with more than two Bluetooth devices.

[0045] Figure 4C 460 with a link cluster between three Bluetooth devices in various examples herein. Network 460 includes devices 462, 464, and 466. In various examples, each of devices 462, 464, or 466 may be a central device or a peripheral device. In this example, device 462 is connected to device 464 via links 468A and 468B. Device 462 is connected to device 466 via links 470A and 470B. Device 464 is connected to device 466 via links 472A and 472B. Network 460 also includes link cluster 474. Devices 462, 464, and 466 may coordinate links 468A, 468B, 470A, 470B, 472A, and 472B to generate link cluster 474. Each device may coordinate its own links to effectively manage these links as part of link cluster 474. In the examples herein, additional links may be added between any two devices. In other examples, a link cluster may include any subset of links 468A, 468B, 470A, 470B, 472A, and 472B.

[0046] The examples herein provide systems and methods for link cluster discovery, establishment, and termination. The examples herein may include link cluster detection, discovery, establishment, and termination procedures that coordinate or utilize link cluster coupling operations. In some examples, the procedure is divided into three phases: discovery, establishment, and termination. First, the device discovers the relevant link or link cluster in the discovery phase. In the second phase, the device establishes a connection via the link. In the third phase, the device terminates the link or link cluster. The methods described herein may be based on air packet exchanges supported by HCI and the Generic Attribute Profile (GATT). The methods described herein may also include some procedures for notifying, selecting, and negotiating connection parameters for any link within a link cluster.

[0047] Figure 5 5 is a block diagram of a state machine 500 of a BLE device in various examples herein. Although the state machine 500 is described as a BLE device, a Bluetooth device or any other communication device may be configured to implement the state machine 500. The state machine 500 shows an idle side 502 and a connected side 504. In this example, the BLE device may operate as a link cluster peripheral device or a link cluster central device depending on the action of the BLE device. The BLE device may start in a standby state 510. The BLE device may move to an advertisement (ADV) state 512 by broadcasting an advertisement signal. ADV may include advertisements for connection parameters of a link within a link cluster. After the ADV state 512, the BLE device may establish a connection 514 and move to a link cluster peripheral state 506 on the connected side 504. In the link cluster peripheral state, the BLE device may advertise again in state 516 or scan in state 518. The BLE device may advertise again in state 516 to connect to another device by generating another link within the link cluster. In another example, the BLE device may scan for advertisements from another device in state 518. The BLE device may also terminate the link via termination 519 and return to the standby state 510 .

[0048] In another example, the BLE device may move from the standby state 510 to the scanning state 520 and initiate a scan. If the scan successfully captures an ADV signal from another device, the BLE device may initialize (INIT) the connection 522 to the link cluster initialization state 524. The BLE device in the initialization state 524 may initialize the link cluster central 508 on the connected side 504. The BLE device then operates as a central device. In this state, the BLE device may advertise in state 526, scan in state 528, or initialize another link cluster via connection 532 at 530. The BLE device may also terminate the connection via termination 534 and return to the standby state 510.

[0049] In some instances, Figure 5 Shows how a BLE device can advertise or scan for a link or link cluster connection. A BLE device can also act as a central or peripheral device depending on the state of the BLE device. In other examples, other states or processes between states can be performed.

[0050] Fig. 6A6 is a discovery phase flow 600 for link clustering in various examples herein. In the discovery phase flow 600, a peripheral device 602 (e.g., a broadcaster device) and a central device 604 (e.g., a scanner device) are shown as one example. In the discovery phase flow 600, the devices exchange packets to discover link functionality, configurations, proposed or preferred bonding methods, etc. for the link cluster. Device functionality may include features supported by the various devices. Features may include connection parameters described herein. In some examples, configurations may include default or preferred configurations of connection parameters.

[0051] The peripheral device 602 (eg, a broadcaster) may enter an advertising duration 606, which includes an advertising interval 608. Figure 5 Describes the advertising state. During the advertising interval 608, the peripheral device 602 may broadcast advertising packets 610, 612, and 614 for the links within the link cluster to the central device 604 (or other device). In some examples, the peripheral device 602 may wake up to send the advertising packet and then enter a sleep state before waking up to send another advertising packet. The advertising packet may include any information about the link or link cluster, including the channel group, connection event start point (anchor point), connection duration, power level, MCS, or any other connection parameters. The connection parameters may include capabilities, limitations, and / or preferences of devices or links within the link cluster.

[0052] The central device 604 (e.g., a scanner) may be in a scanning state with a scan duration 616. The scan duration 616 has a scan interval 618, which includes a scan window 620. During the scan duration 616, the central device 604 may receive advertisement packets 610, 612, and / or 614 for links within a link cluster from the peripheral device 602. In response to receiving the advertisement packets 610, 612, or 614, the central device 604 may send a link cluster join or coordination (e.g., scan) request 622 to the peripheral device 602. With the link cluster join request, the central device 604 may request to establish a link with the peripheral device 602 using the parameters in one or more advertisement packets. With the link cluster coordination request, the central device 604 may transmit or propose changes to one or more connection parameters in the one or more advertisement packets. The peripheral device 602 may then send a link cluster join or coordination (e.g., scan) response 624 to the central device 604. The link cluster join or coordination response 624 may establish a link in a link cluster or negotiate a link in a link cluster between the peripheral device 602 and the central device 604 using the negotiated connection parameters. The negotiation and coordination process may include any number of steps or transmissions between the devices. The peripheral device 602 may then continue advertising by broadcasting another one or more advertisement packets 626 including any connection parameters for the links within the link cluster. In some examples, the peripheral device 602 may also connect to other central devices. In some examples, the broadcaster device may provide a selection of connection parameters for the scanner device to select from. As described above, the devices may coordinate channel groups, start and stop times for connection events, and connection parameters for connection events, such as power and MCS.

[0053] Although Figure 6 is described with respect to joining or coordinating a link, other types of communication performed by the scanner are possible. For example, the scanner may respond to a broadcast by requesting to join a new link with the broadcaster. As another example, the scanner may also coordinate an active or existing link or request to suspend an active or existing link. The request to suspend may indicate the timing of the suspension, or the request may indicate that the suspension occurs immediately. The request to suspend may include a suspension expiration time, or may include a request to suspend one or more links without an expiration time. In some examples, the request to suspend may include one or more suspension criteria. As another example, the scanner may send a request to the broadcaster to request to terminate an existing link. The request to terminate may indicate the timing of the termination, or the request may indicate that the termination occurs immediately. In some examples, the request to terminate may include one or more termination criteria. Another example is that the scanner may send a request to the broadcaster to request to resume the suspended link.

[0054] Figure 6B and 6C There are two examples of link cluster discovery signaling in various examples herein. Figure 6BIs the classic option with primary and secondary channels. Figure 6C A duplicate secondary option with one primary and two secondary channels. Figure 6B and 6C Shown are channels during an example advertising procedure between a broadcaster device and a scanner device as described above.

[0055] Figure 6B Two timing diagrams 630 are included. The first timing diagram represents a primary channel 632, and the second timing diagram represents a secondary channel 634. On the primary channel 632, an advertisement event occurs that includes advertisement packets 636A, 636B, 636C, 638A, 638B, and 638C. Any number of advertisement packets may be included in the advertisement event. The advertisement event may include information such as connection parameters for links within the link cluster. The advertisement event may be described above with respect to Fig. 6A The described broadcaster means broadcasts.

[0056] After the advertising event, a packet may be transmitted on the secondary channel 634. Packet 640 on the secondary channel 634 is an auxiliary advertising indication with link cluster information. Packet 642 on the secondary channel may be a scan (join / coordinate / terminate) request with link cluster information. Packet 642 may be transmitted from the scanner device to the broadcaster device. Packet 644 on the secondary channel 634 is a scan response with link cluster information, which may be a join or coordinate response. Packet 644 may be transmitted from the broadcaster device to the scanner device.

[0057] On primary channel 632, another advertising event may occur including advertising packets 638A, 638B, and 638C. After this advertising event, packets such as packets 640, 642, and 644 may again be transmitted on secondary channel 634.

[0058] Figure 6C Three timing diagrams 660 are included. The first timing diagram represents a primary channel 662, the second timing diagram represents a secondary channel 664A, and the third timing diagram represents a duplicate secondary channel 664B. On the primary channel 662, an advertisement event occurs that includes advertisement packets 666A, 666B, 666C, 668A, 668B, and 668C. Any number of advertisement packets may be included in the advertisement event. The advertisement event may include information such as connection parameters for links within the link cluster. The advertisement event may be displayed as described above with respect to Fig. 6A The described broadcaster means broadcasts.

[0059] After the advertising event, duplicate packets may be transmitted on both secondary channels 664A and 664B. Duplicate packet 670 on secondary channel 664A and packet 676 on secondary channel 664B are auxiliary advertising indications with link cluster information. Duplicate packet 672 on secondary channel 664A and packet 678 on secondary channel 664B are scan requests with link cluster information, which may be join or coordination requests, or any other possible scanner responses, as described above with respect to Fig. 6A Duplicate packets 672 and 678 may be transmitted from the scanner device to the broadcaster device. Duplicate packet 674 on secondary channel 664A and packet 680 on secondary channel 664B are scan responses with link cluster information, which may be join or coordination responses. Packets 674 and 680 may be transmitted from the broadcaster device to the scanner device.

[0060] On primary channel 662, another advertising event may occur including advertising packets 668A, 668B, and 668C. Following this advertising event, the scanner may transmit packets on secondary channels 664A and 664B similar to packets 670, 672, 674, 676, 678, and 680 previously transmitted on these channels.

[0061] Figure 7 700 for links in a link cluster in various examples herein. In the connect and terminate phase flow 700, a peripheral device 602 (e.g., a broadcaster device) and a central device 604 (e.g., a scanner device) are shown as one example. In the connect and terminate phase flow 700, the devices may set up a coordinated cluster of individual links between each other for communication. The devices may connect via multiple links with one advertisement and indication process. In addition, the devices may terminate one or more of the links within the link cluster.

[0062] Flow 700 may include a link cluster advertisement packet 610 from a peripheral device 602 (e.g., a broadcaster) to a central device 604 (e.g., a scanner). In response to receiving one or more link cluster advertisement packets 601, the central device 604 may transmit a link cluster connection indication 702 to establish one or more links within a link cluster. The link cluster may include link 1 704, link 2 706, and link N 708 between the peripheral device 602 and the central device 604. The peripheral device 602 and the central device 604 may enter a connection state 710, in which the devices communicate with each other using the links within the link cluster. Any link in the link cluster may also be terminated individually or collectively. As described herein, the links 704, 706, and 708 may each have a different channel group and other different connection parameters. Communications on the links 704, 706, and 708 may overlap in time due to frequency separation.

[0063] In the example herein, the BLE message between the devices may include coupling coordination parameters. The coupling coordination parameters are used to notify, select and negotiate the connection parameters of a specific link or several coupled links within the link cluster. The BLE message can be extended to include this information. The procedure for coordinating the coupling parameters includes advertising connection parameters, such as the number of supported links, the frequency or bandwidth of the link, the physical (PHY) parameters of one or more links (e.g., rate, power, etc.), channel map and channel selection, encryption parameters, modem characteristics, packet level restrictions, packet duration restrictions, connection event restrictions, power management restrictions MCS, duration, connection event start point, etc. The procedure also includes establishing connection parameters. The procedure may include channel map advertising. For example, only certain channels, not all advertising channels, may be enabled for advertising. Channel map advertising can be used to coordinate frequency, power, duration of connection intervals, etc. The procedure may also include encryption establishment. Each link in the link cluster may have a unique key for encryption. Credentials for connecting devices may also be established. Supported features may also be advertised. In addition, the coupling coordination parameters may include termination conditions.

[0064] In some examples, packet exchange is supported via the HCI interface and based on GATT level signaling. The host can manage link clusters. Coordinated discovery, establishment, and termination procedures are defined for controlling coupled links within a link cluster between a GATT client and a GATT server. The Generic Access Profile (GAP) controls connections and advertisements in Bluetooth and determines how two devices can interact with each other. GAP defines the central and peripheral roles of a device. GAP describes the advertising and scan response processes, as described above with reference to Fig. 6A GATT defines a method for BLE devices to transfer data back and forth. GATT uses a common data protocol called the Attribute Protocol (ATT), which stores services, characteristics, and other related data in a lookup table using a 16-bit ID. GATT is used after a connection is established between two devices using GAP.

[0065] GATT uses a server / client relationship. A GATT server holds ATT lookup data and service and characteristic definitions, and GATT clients send requests to this server. All transactions are initiated by a primary device, a GATT client, which receives responses from a secondary device, a GATT server. In one example, a peripheral device is a GATT server, and a central device is a GATT client. In other examples, a peripheral device may be a GATT client, and a central device may be a GATT server, depending on the direction in which data is being transferred between the devices.

[0066] In the examples herein, GATT can be used to control links within a link cluster between a GATT client and a GATT server. The process flow described herein supports link cluster service discovery, GATT link cluster client requests and server responses, GATT indications or notifications from the client to the server, and data transfer between devices. In one example, the process traverses all available link cluster services in the GATT database and generates events for each link cluster service discovered. In some examples, a server-initiated link cluster update can be sent from a GATT server to a client without the client requesting an update. The notification may include an identifier of a link cluster characteristic, a link cluster value, and / or connection parameters. In some examples, GATT messaging can be performed at the application layer or at the link layer via HCI.

[0067] Figure 8 8 is a GATT process 800 for one or more links in a link cluster in various examples herein. The GATT process 800 includes a peripheral device 602 communicating with a central device 604. The central device 604 sends a GAP connection request 802, and the peripheral device 602 sends a connected response 804. The peripheral device 602 and the central device 604 make a GAP connection after the GAP connected response 804.

[0068] The central device 604 sends an enable notification message 806 to the peripheral device 602. Message 806 implements GATT notifications between the two devices. The peripheral device 602 may send GATT notifications 808A to 808N, where any number N of GATT notifications may be sent. The GATT notifications may include link cluster information. These GATT notifications 808A to 808N may be sent without the client (e.g., the central device 604) requesting the notifications. Figure 8 As shown, the GATT throughput may also be calculated by the peripheral device 602 .

[0069] The central device 604 may send a deactivation notification message 810 to the peripheral device 602. In response to receiving the message 810, the peripheral device 602 stops notification and throughput calculation. In some examples, the central device 604 may then send a GAP disconnect request 812 to the peripheral device 602. In response to receiving the GAP disconnect request, the peripheral device 602 disconnects and may begin advertising to other devices. The peripheral device 602 may also send a gap disconnect response 814 to the central device 604, completing the GAP disconnect process.

[0070] Fig. 9 900 is a flowchart of a method 900 for establishing a link cluster in various examples herein. The steps of method 900 may be performed in any suitable order. In some examples, the above description of Figures 1 to 4CThe described hardware components may perform method 900 .

[0071] Method 900 begins at 910, where a broadcaster Bluetooth device broadcasts an advertising packet, and where the advertising packet includes one or more connection parameters for one or more links in a link cluster. Figures 5 to 7 Describes the broadcast of an advertising packet.

[0072] Method 900 continues at 920, where the broadcaster Bluetooth device receives a link cluster coordination request from the scanner Bluetooth device. The link cluster coordination request includes one or more connection parameters for the links in the link cluster. The connection parameters may include a channel group, a connection event start point (anchor point), a connection duration, a power level, an MCS, a connection interval anchor time, or any other connection parameters. In some examples, the scanner Bluetooth device may accept the connection parameters for the link, or may propose other connection parameters. In other examples, the scanner Bluetooth device may send a join request that accepts the connection parameters.

[0073] Method 900 continues at 930, where in response to receiving the link cluster coordination request, the broadcaster Bluetooth device transmits the link cluster coordination response from the broadcaster Bluetooth device to the scanner Bluetooth device. The link cluster coordination response may be an optional step that is not performed in each instance. Therefore, method 900 may end at 920 with the received link cluster coordination request. In an example, at this time, the device may be connected via a link in the link cluster. As described herein, the device may then communicate with each other using one or more links in the link cluster. In other examples, after transmitting the coordination response, the broadcaster Bluetooth device may be configured to send another broadcast to attempt to form a link with another scanner. In other examples, after transmitting the coordination response, the broadcaster Bluetooth device may be configured to communicate with other devices in the link cluster. In other examples, after receiving the coordination response, the scanner Bluetooth device may be configured to scan the broadcast from another broadcaster. In other examples, after receiving the coordination response, the scanner Bluetooth device may be configured to communicate with other devices in the link cluster.

[0074] Fig.10 1 is a flow chart of a method 1000 for controlling a link cluster with GATT in various examples herein. The steps of method 1000 may be performed in any suitable order. In some examples, the above description of Figures 1 to 4C The described hardware components may perform method 1000 .

[0075] Method 1000 begins at 1010, where a broadcaster Bluetooth device receives a GAP connection request. Figure 8 An example of such a request is shown. A broadcaster Bluetooth device may receive a GAP connection request from a scanner Bluetooth device.

[0076] The method 1000 continues at 1020 where the broadcaster Bluetooth device transmits a GAP connection response from the broadcaster Bluetooth device to the scanner Bluetooth device.

[0077] The method 1000 continues at 1030 where the broadcaster Bluetooth device receives an enable message from the scanner Bluetooth device to enable GATT notifications.

[0078] The method 1000 continues at 1040, where in response to receiving the enable message, the broadcaster Bluetooth device transmits a GATT notification regarding connection parameters of one or more links in the link cluster from the broadcaster Bluetooth device to the scanner Bluetooth device. The broadcaster Bluetooth device and the scanner Bluetooth device can be configured to communicate via the one or more links based on the connection parameters indicated in the GATT notification.

[0079] The method 1000 continues at 1050 where the broadcaster Bluetooth device receives a deactivate message from the scanner Bluetooth device to deactivate GATT notifications.

[0080] The method 1000 continues at 1060, where in response to receiving the deactivation message, the broadcaster Bluetooth device deactivates transmitting GATT notifications about one or more links in the link cluster from the broadcaster Bluetooth device to the scanner Bluetooth device. After 1060, the broadcaster Bluetooth device may begin advertising to the scanner Bluetooth device again as described herein.

[0081] Examples herein also provide link cluster control and management. In one example, a link cluster can perform unicast data exchange. This link cluster control and management for unicast data exchange can support unicast link cluster operation profile modification and / or unicast link cluster feedback and reporting of one or more links within a link cluster.

[0082] The BLE link cluster control and management procedures for data exchange described in this article can be issued between the link layers of devices based on over-the-air signal exchanges (when the link cluster splitting / aggregation point is at the BLE PHY / modem level) or via an HCI single exchange process (when the splitting / aggregation point is at the BLE controller level) or a combination of both.

[0083] The BLE link cluster control and management procedures extend on standalone unaware BLE signaling to support link cluster functionality applied to one or more coupled links within a link cluster. In some examples, this signaling is extended by adding additional link cluster signaling entities (e.g., multi-link elements or fields). In some examples, to reduce overhead and connection time and response, one or more of the devices may be configured to perform the link cluster signaling process only for a preferred single link.

[0084] In some examples herein, the BLE link cluster link layer defines a coordination program for controlling the coupled links within the link cluster. These coordination programs are used to set or update the dependency parameters of a specific link or several coupled links within the link cluster. A plurality of coordination programs are described herein. The coordination program may include a device for executing a link connection parameter modification request program. In order to execute this program, one of the devices may request one or more specific links within the link cluster for modifying or setting connection parameters. The coordination program may include a link connection parameter update program to update the link cluster parameters or execute an update program. The coordination program may include a link PHY parameter modification request program to request modification or setting of the PHY parameters of the link. The coordination program may include a link PHY parameter modification update program to update the PHY parameters of the link or link cluster to execute an update program. The coordination program may include a synchronous link cluster channel map update program to update the link cluster channel map and participate in the frequency hopping link cluster synchronous channel selection. The coordination program may also include a link cluster encryption parameter modification program to update the link cluster encryption control. The coordination program may include a feature modification program to activate or deactivate the supported features of the link cluster. Any device in the link cluster may be configured to execute these programs.

[0085] The coordination procedure may include a link cluster status reporter to report the status of one or more links within the link cluster. As an example, the multi-link signaling entity may exchange status information about the number of supported links, PHY characteristics of the link (rate, power, etc.), transmission operation mode (asynchronous, synchronous, synchronous replication, etc.), or other per-link information. One or more of the devices in the link cluster may be configured to execute a status reporter to report the status of any link in the link cluster. For example, any device in the link cluster may be configured to exchange information about the number of supported links, the rate or power of any link, the operating characteristics of any link, multi-link transmission operation (e.g., asynchronous or synchronous operation), or any other link information. A first device in the link cluster may send a request to a second device in the link cluster to request status information, and the second device may respond to the request with the requested status information. Additionally or alternatively, the second device may be configured to report status information to the first device at regular intervals or based on a schedule.

[0086] Fig.11 1100 is a process flow for link cluster coordination in various examples described herein. Fig.11A program flow 1100 is shown for a link cluster device 1102 and a link cluster device 1104 connected by a link cluster 1106. In one example, the link cluster device 1102 may be a server and the link cluster device 1104 may be a client. The link cluster device 1102 may store data 1108A. The data 1108A may include data about link A 1110A, link B 1110B, ..., link N 1110N (collectively referred to as links 1110). In one example, the link 1110 may be included in the link cluster 1106. Each link 1110 may have a set of one or more link parameters (e.g., connection parameters). As an example, the program flow 1100 shows link parameter 11112A, link parameter 2 1112B, ..., link parameter N 1112N (collectively referred to as link parameters 1112). Link B 1110B and other links 1110 may have their own set of link parameters 1112, but Fig.11 Only one set of link parameters 1112 is shown.

[0087] In the program flow 1100, the link cluster device 1102 may send a notification 1114 to the link cluster device 1104 to notify the link cluster device 1104 of the link parameters 1112 for one or more links 1110. The link cluster device 1104 may use the link parameters 1112 to reconstruct the data 1108A stored at the link cluster device 1102 and create data 1108B stored at the link cluster device 1104, which may include the link parameters 1112 for the various links 1110. Thus, the link cluster device 1104 may utilize the program flow 1100 to notify changes to the link parameters 1112.

[0088] In the examples described herein, devices in a link cluster may perform the link cluster signaling exchanges described herein via at least one link in the link cluster. Link cluster signaling changes may modify operational settings of one (or more) coupled links within a link cluster (e.g., link air access operational characteristics, link modem and media access control (MAC) characteristics, link power management, etc. at packet and connection interval levels). Link cluster signaling may enable devices to change transmission modes, such as synchronous mode, synchronous replication mode, or joint asynchronous mode as described above. Synchronous mode transmits synchronous packets on separate links. Synchronous replication mode transmits replicated packets on separate links in a synchronous manner. Joint asynchronous mode transmits packets via multiple available links, but does not send copies of the packets.

[0089] One example power management coordination procedure supported by link cluster signaling is a power saving state. A device as described herein can operate in two modes: an active mode and a power saving mode. In the active mode, the device is always awake and can transmit and receive frames during the shadowed connection interval. In the power saving mode, the device can suspend one or more of the links from time to time. If a link is suspended, the device can temporarily connect via a single link within the link cluster. The single link can be an anchor link, which in some instances is a link that controls other links within the link cluster and keeps the network operational. The device can then utilize the anchor link to restore the other links via link cluster signaling to enter active mode again.

[0090] Depending on traffic conditions, channel conditions, and interference on different links and at different frequencies, the power management coordinator may use link cluster signaling for parameter modification of one or more links within a link cluster, or temporarily suspend links within a link cluster that will not be used for data transmission. In some examples, the power management coordinator may thereby reduce power consumption.

[0091] Fig.12 1200 is a process flow for link cluster control and management in various examples herein. Fig.12 A program flow 1200 is shown that includes device A 1202, device B 1204, device C 1206, and device D 1208. At 1210, device A 1202 is in a link cluster connection with device B 1204, device C 1206, and device D 1208. Link A, B 1212 connects device A 1202 to device B 1204. Link A, C 1214 connects device A 1202 to device C 1206. Link A, D 1216 connects device A 1202 to device D 1208. At 1218, device B 1204 wishes to change one or more link cluster connection parameters between device B 1204 and device A 1202. Device B 1204 may send a request 1220 to device A 1202. The request 1220 may relate to any characteristics, such as operation settings, MAC characteristics, power management, operation mode, links within a link cluster, transmission rate, transmission power, connection duration, MCS restrictions, anchor points, frequency of connection events, etc. The devices described herein may also share feedback about any of the characteristics described above. The feedback may be used by any device to manage the operation of one or more links within a link cluster. In one example, the request 1220 may also request a change from a replication mode to a joint mode or vice versa.

[0092] In response to request 1220, device A 1202 may update link connection parameters between device A 1202 and device B 1204 at 1222. Device A 1202 may also update link connection parameters for device C 1206 at 1224 and / or link connection parameters for device D 1208 at 1226.

[0093] Fig.13 1 is a flow chart of a method 1300 for managing link cluster connection parameters in various examples herein. The steps of method 1300 may be performed in any suitable order. In some examples, the above description of Figures 1 to 4C The described hardware components may perform method 1300 .

[0094] Method 1300 begins at 1310, where a first Bluetooth device is connected to a second Bluetooth device via one or more links within a link cluster. The devices may be connected using the procedures described herein. In other examples, more than two Bluetooth devices may be connected.

[0095] The method 1300 continues at 1320 where the first Bluetooth device receives a request from the second Bluetooth device to change one or more link connection parameters of a link within the link cluster. Fig.12 Contains an instance of the request.

[0096] The method 1300 continues at 1330, where in response to receiving the request, the first Bluetooth device changes the link connection parameters of the links within the link cluster. The link connection parameters can be any connection parameters described in the various examples herein. In other examples, other Bluetooth devices can also update the link cluster connection parameters for one or more links within their respective link clusters.

[0097] Fig.14 1 is a flow chart of a method 1400 for power management in a link cluster in various examples herein. The steps of method 1400 may be performed in any suitable order. In some examples, the above description of Figures 1 to 4C The described hardware components may perform method 1400 .

[0098] Method 1400 begins at 1410, where a first Bluetooth device is connected to a second Bluetooth device via one or more links within a link cluster. The devices may be connected to each other via the processes described herein, such as in Figures 6A to 6C and 7.

[0099] Method 1400 continues at 1420, where the first Bluetooth device enters a power saving mode. In the power saving mode, the first Bluetooth device suspends one or more of the links within the link cluster. The link may be suspended to save power or for other reasons. As an example, if the link will not be used for data transmission, the link may be suspended. In some examples, all links except one are suspended, and a single non-suspended link is used to keep the network running.

[0100] Method 1400 continues at 1430, where the first Bluetooth device modifies the link connection parameters of the links within the link cluster via the active link in the link cluster. In one example, the first Bluetooth device may send a request to another device to modify the connection parameters, or may modify the link connection parameters and notify other Bluetooth devices.

[0101] Method 1400 continues at 1440, where the first Bluetooth device exits the power saving mode and enters the active mode, where the first Bluetooth device uses the active link within the link cluster to wake up one or more paused links within the link cluster. For example, the first Bluetooth device can be configured to send a message to the second Bluetooth device via the active link to wake up the paused link. The paused link can be a link between the first Bluetooth device and the second Bluetooth device, or the paused link can be a link between the second Bluetooth device and the third Bluetooth device. After entering the active mode, the paused link can be made active.

[0102] In the examples herein, link clustering allows BLE systems to optimize power consumption, reduce latency, and increase system-level throughput. Over-the-air signal exchanges or signal exchanges via HCI can be used to discover link cluster device functionality, understand the preferred or default configuration of the device, and transmit proposed or preferred link cluster joining methods. In some instances, the same technology can be used to establish and / or terminate links. In some instances, signaling can be performed on a single link in a link cluster. The coordination procedure for links within a link cluster may include parameter advertising, parameter establishment, channel map advertising, encryption establishment, common feature advertising, and termination. Link clusters can coordinate and utilize link cluster operations. In some instances, link clusters can synchronize the connection parameters of the link. In some instances, a single link layer can control the link cluster.

[0103] The term "coupled" is used throughout this specification. The term may encompass connections, communications, or signal paths that achieve a functional relationship consistent with this specification. For example, if device A generates a signal to control device B to perform an action, then: in a first instance, device A is coupled to device B; or in a second instance, device A is coupled to device B through an intermediate component C, provided that the intermediate component C does not substantially change the functional relationship between device A and device B, so that device B is controlled by device A via the control signal generated by device A.

[0104] In this specification, a device "configured to" perform a task or function may be configured (e.g., programmed and / or hardwired) to perform the function when manufactured by a manufacturer, and / or may be configured (or reconfigured) by a user after manufacture to perform the function and / or other additional or alternative functions. Configuration may be performed through firmware and / or software programming of the device, through the construction and / or layout of the hardware components and interconnections of the device, or a combination thereof.

[0105] Unless otherwise stated, "about," "approximately," or "substantially" preceding a value means + / - 10 percent of the stated value. Modifications may be made in the described examples, and other examples may be made within the scope of the claims.

Claims

1. A method comprising: broadcasting an advertising packet from a broadcaster Bluetooth device, wherein the advertising packet includes one or more connection parameters for one or more links in a link cluster; and A link cluster coordination request is received at the broadcaster Bluetooth device from a scanner Bluetooth device, wherein the link cluster coordination request includes one or more connection parameters for links in the link cluster.

2. The method according to claim 1, further comprising: In response to receiving the link cluster coordination request, a link cluster coordination response is transmitted from the broadcaster Bluetooth device to the scanner Bluetooth device.

3. The method of claim 2, wherein the broadcaster Bluetooth device broadcasts an additional advertising packet after transmitting the link cluster coordination response. 4 . The method of claim 1 , wherein the link cluster coordination request comprises a change to one or more connection parameters for the links in the link cluster.

5. The method of claim 1, wherein the one or more connection parameters in the advertisement packet include physical (PHY) parameters for the links in the link cluster.

6. The method of claim 1, wherein the one or more connection parameters in the advertisement packet include a channel map for the links in the link cluster.

7. The method of claim 1, wherein the one or more connection parameters in the advertising packet include media access control (MAC) characteristics for the links in the link cluster.

8. The method of claim 1, wherein the one or more connection parameters in the advertisement packet include power management for the links in the link cluster.

9. A system comprising: A scanner Bluetooth device configured to: scanning for advertising packets from a broadcaster Bluetooth device, wherein the advertising packets include one or more connection parameters for one or more links in a link cluster; and In response to receiving an advertising packet, a link cluster coordination request is transmitted from the scanner Bluetooth device to the broadcaster Bluetooth device, wherein the link cluster coordination request includes one or more connection parameters for links in the link cluster.

10. The system of claim 9, wherein the link cluster coordination request includes a change to one or more connection parameters for the links in the link cluster.

11. The system of claim 9, wherein the one or more connection parameters in the advertisement packet include physical (PHY) parameters for the links in the link cluster.

12. The system of claim 9, wherein the one or more connection parameters in the advertising packet include a transmit power limit.

13. The system of claim 9, wherein the one or more connection parameters in the advertisement packet include modulation coding scheme restrictions.

14. The system of claim 9, wherein the link is a first link, and wherein the one or more connection parameters in the advertisement packet include a channel map for a second link in the link cluster.

15. A method comprising: receiving a Generic Access Protocol (GAP) connection request at a broadcaster Bluetooth device; transmitting a GAP connection response from the broadcaster Bluetooth device to the scanner Bluetooth device; receiving, at the broadcaster Bluetooth device, an enable message from the scanner Bluetooth device to enable generic attribute (GATT) notifications; in response to receiving the enable message, transmitting a GATT notification regarding connection parameters of one or more links in a link cluster from the broadcaster Bluetooth device to the scanner Bluetooth device; receiving, at the broadcaster Bluetooth device, a deactivate message from the scanner Bluetooth device to deactivate GATT notifications; and In response to receiving the deactivation message, transmitting GATT notifications from the broadcaster Bluetooth device to the scanner Bluetooth device regarding one or more links in the link cluster is disabled.

16. The method according to claim 15, further comprising: receiving, at the broadcaster Bluetooth device, a GAP disconnect request from the scanner Bluetooth device; and In response to receiving the GAP disconnect request, a GAP disconnect response is transmitted from the broadcaster Bluetooth device to the scanner Bluetooth device.

17. The method according to claim 16, further comprising: In response to receiving the GAP disconnect request, an advertising packet is broadcast from the broadcaster Bluetooth device, wherein the advertising packet includes one or more connection parameters for one or more links in a link cluster.

18. The method of claim 15, wherein the GATT notification is transmitted via a host controller interface (HCI).

19. The method of claim 15, wherein the scanner Bluetooth device is a GATT client and the broadcaster Bluetooth device is a GATT server.

20. The method of claim 15, wherein the GATT notification indicates a change in a link connection parameter of a link in the link cluster.

Images