Multi-peripheral connectivity service

Abstract

The invention relates to multiple peripheral connectivity services. In an embodiment, a method includes transmitting, by a first device (102), a first message during a first connection event (202); receiving, at the first device (102), a first response to the first message from the second device (104.1) during the first connection event (202); receiving, by the first device (102), a second response to the first message from a third device (104.2) during the first connection event (202); and receiving, by the first device (102), a third response from the second device (104.1) during the first connection event (202).

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 523,269, filed on June 26, 2023, entitled “MULTI-PERIPHERALSCONNECTION SERVICE,” which is incorporated herein by reference.

[0003] This application is related to commonly assigned U.S. patent application Ser. No. 18 / 528,503, filed on December 4, 2023, entitled “SIMULTANEOUS MULTI-FREQUENCY MULTI-PERIPHERAL BLE SERVICE,” which is incorporated herein by reference. Technical Field

[0004] The present disclosure relates generally to wireless communications and, in particular embodiments, to multi-peripheral connection services. Background Art

[0005] Bluetooth Low Energy (BLE) is a wireless communication technology suitable for various applications and devices, such as healthcare, health, security, home entertainment and communication devices. Compared with Bluetooth or other wireless communication technologies, BLE communication technology provides reduced power consumption of communication devices while maintaining similar wireless communication range and coverage. Compared with other wireless communication technologies, simpler modulation schemes can provide reduced power consumption of communication devices. BLE communication technology is based on the BLE communication standard supported by various operating systems (OS) operating communication devices, including ANDROID, IOS, WINDOWS, MACOS, LINUX and other OS. Summary of the invention

[0006] Some embodiments relate to multi-device wireless communications.

[0007] In some embodiments, a first device (e.g., a central device) exchanges data with multiple other devices (e.g., peripheral devices) during a single connection event (referred to herein as a multiple peripheral connection (MPC) event). By exchanging data with multiple devices during an MPC event, some embodiments advantageously improve throughput (e.g., because there is no need to wait for subsequent connection events to exchange data with all other devices).

[0008] In some embodiments, one or more of the other devices may transition to a sleep mode during an MPC event and wake up during the same MPC event to exchange data with the first device. By entering a sleep mode and then waking up during the same MPC event, some embodiments advantageously reduce power consumption without sacrificing data throughput.

[0009] In some embodiments, packets exchanged between the first device and multiple other devices during an MPC event can be performed using respective encryption keys. By using different encryption keys to exchange data during an MPC event, some embodiments advantageously maintain secure communications when the first device exchanges data with multiple other devices.

[0010] In some embodiments, during the same MPC event, a first device may exchange data with a first other device, then exchange data with a second other device, and then exchange data with the first other device again. By exchanging data with the same other device in a non-continuous manner during the same MPC event, some embodiments may advantageously reduce latency (e.g., during a first exchange, a first other device may request data, which may be generated by the first device and transmitted to the first other device during a second exchange, while still providing services to the second other device).

[0011] In some embodiments, all data exchanges during an MPC event may use the same communication channel. By using the same communication channel during all exchanges, some embodiments advantageously allow other devices to use other channels for other communications, and / or allow implementation of other advantageous features, such as using channel hopping for consecutive MPC events.

[0012] In some embodiments, messages exchanged during an MPC event may be in accordance with the BLE protocol. By transmitting messages in accordance with the BLE protocol, some embodiments may be easier to implement, test, and support, and they may at least partially reuse existing hardware and software.

[0013] In some embodiments, a single advertising packet may be used during an MPC event. By using a single advertising packet, some embodiments advantageously allow all peripherals to determine their respective associated allocated times, which in turn may advantageously allow for power reduction (because the device can transition to a sleep mode) and / or efficient communication (e.g., because the device can plan actions based on the determined timing during the MPC event).

[0014] In some embodiments, multiple advertisement packets may be used during an MPC event.By using multiple advertisement packets, some embodiments advantageously allow for flexible allocation of sub-connection events (eg, based on the needs of a particular other device or central device).

[0015] In some embodiments, the duration of the sub-connection events of the MPC event may be different. By using sub-connection events of different durations, some embodiments advantageously allocate transmission bandwidth efficiently among other devices.

[0016] In some embodiments, the number of packets exchanged during a sub-connection event of an MPC event may be different. By exchanging different numbers of packets during different sub-connection events of an MPC, some embodiments advantageously exchange data efficiently without transmitting empty packets (when the device has no more data to send and still has a certain number of packet slots allocated) or having to wait until the next MPC to send additional data (e.g., when the device has more data to send than the number of allocated packet slots).

[0017] In some embodiments, advertisement packets may not be transmitted during MPC events. By avoiding transmission of advertisement packets, some embodiments may advantageously use such bandwidth for data transmission.

[0018] In some embodiments, parameters associated with MPC events can be dynamically renegotiated. By allowing renegotiation of parameters, some embodiments can advantageously exhibit less overhead and higher scalability because the parameters of the MPC events are optimized and adaptively adjusted for the current conditions of the wireless network.

[0019] In some embodiments, the MPC capabilities of a device are discoverable during an MPC event. By allowing discoverability of the MPC capabilities of a device during an MPC event, selected MPC features may be implemented without risking loss of communication with a particular device.

[0020] Some embodiments allow a single connection event (MPC event) to be subdivided into multiple sub-connection events. Specifically, each of these sub-connection events can have a flexible duration and can be assigned to peripheral devices. Within a sub-connection event, the peripheral device can exchange data with the central device. Because each of the multiple sub-connection events is respectively assigned to at least one peripheral device, multiple peripheral devices can exchange data with the central device and / or with each other within a single connection event. This can allow multi-peripheral data exchange within a single connection event, because data exchange is possible in each sub-connection event, which can advantageously improve channel utilization efficiency because there is no need to wait for subsequent connection events to exchange data with all other devices. Therefore, the throughput of communications during at least a single sub-connection event can be advantageously improved.

[0021] According to an embodiment, a method includes: transmitting a first message by a first device during a first connection event; receiving a first response to the first message from a second device at the first device during the first connection event; receiving a second response to the first message by the first device from a third device during the first connection event; and receiving a third response by the first device from the second device during the first connection event. Among other advantages, the method can advantageously improve throughput, for example, by allowing multi-peripheral data exchange.

[0022] According to an embodiment, a method includes: receiving a first message from a second device at a first device during a first connection event; transmitting a second message by the first device during the first connection event; entering a low power mode at the first device after transmitting the second message; exiting the low power mode at the first device; and transmitting a third message by the first device during the first connection event after exiting the low power mode. Among other advantages, the method advantageously reduces power consumption, for example by allowing the device to transition to a low power mode without losing a wireless connection.

[0023] According to an embodiment, an electronic device includes: a transceiver; and a processor, which is configured to: transmit a first advertising packet using the transceiver during a first connection event, wherein the first advertising packet indicates a first time for a second advertising packet; receive a first response from a first device via the transceiver in response to the first advertising packet during the first connection event; transmit a second advertising packet using the transceiver at a first time during the first connection event; and receive a second response in response to the second advertising packet during the first connection event. Among other advantages, the electronic device can advantageously improve throughput, for example by allowing multi-peripheral data exchange.

[0024] According to an embodiment, an electronic device includes: a transceiver; and a processor, which is configured to: during a first connection event, receive a first advertising packet using the transceiver, wherein the first advertising packet indicates a first time for a second advertising packet; determine that the first advertising packet is directed to a different device; in response to the determination, transition to a sleep mode; wake up at a first time; receive a second advertising packet using the transceiver; and transmit a response to the second advertising packet using the transceiver. Among other advantages, the electronic device advantageously reduces power consumption, for example by allowing the device to transition to a low power mode without losing a wireless connection, while advantageously improving throughput by allowing multi-peripheral data exchange.

[0025] According to an embodiment, a method includes transmitting a first broadcast message by a first device during a first connection event; transmitting a first message by the first device to a second device during the first connection event; receiving a first response to the first message at the first device from the second device during the first connection event; transmitting a second message by the first device to a third device during the first connection event; receiving a second response to the second message from the third device during the first connection event; transmitting a third message by the first device to the second device during the first connection event; and receiving a third response to the third message by the first device from the second device during the first connection event. Among other advantages, the method can advantageously improve throughput, for example by allowing multi-peripheral data exchange.

[0026] According to an embodiment, a method includes: receiving a first message from a second device at a first device during a first connection event; transmitting a second message by the first device during the first connection event; entering a low power mode at the first device after transmitting the second message; remaining in the low power mode while the second device provides services to a third device; exiting the low power mode at the first device during the first connection event; receiving a third message from the second device at the first device after exiting the low power mode; and transmitting a fourth message by the first device. Among other advantages, the method can advantageously reduce power consumption, for example by allowing the device to transition to a low power mode without losing a wireless connection, while advantageously improving throughput by allowing multi-peripheral data exchange.

[0027] According to an embodiment, an electronic device includes: a transceiver; and a processor, which is configured to: transmit a first advertising packet using the transceiver during a first connection event, wherein the first advertising packet indicates a first time for a second advertising packet; receive a first response from a first device via the transceiver in response to the first advertising packet during a first sub-connection event of the first connection event; transmit a second advertising packet at a first time using the transceiver during a second sub-connection event of the first connection event; and receive a second response in response to the second advertising packet during the first connection event. Among other advantages, the electronic device can advantageously improve throughput, for example by allowing multi-peripheral data exchange.

[0028] This summary is provided to introduce a selection of concepts in a simplified form, which will be further described below in the detailed description. Some embodiments may implement one or more (or all) of the features described in the summary. Some features described in this section may not be implemented by some embodiments, but still show advantages over the prior art. It is understood that the summary is not intended to identify the key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 is a block diagram of a hardware architecture of a central device and a peripheral device according to various examples.

[0030] Figure 2 is an illustration of a multiple peripheral connection (MPC) system according to various examples.

[0031] Figure 3 is a timeline of MPC connection events according to various examples.

[0032] Figure 4 is a timeline of MPC connection events according to various examples.

[0033] Figure 5 is a timeline of MPC connection events according to various examples.

[0034] Figure 6 is a flow chart of a method for MPC connection events according to various examples.

[0035] Figure 7 is a flow chart of a method for MPC connection events according to various examples.

[0036] Figure 8 is a flow chart of a method for MPC connection events according to various examples.

[0037] Fig. 9 is a flow chart of a method for MPC connection events according to various examples.

[0038] Fig.10 is a flow chart of a method for MPC connection events according to various examples.

[0039] Fig.11 is a flow chart of a method for MPC connection events according to various examples.

[0040] The same reference numerals or other reference numerals are used in the drawings to indicate the same or similar (functionally and / or structurally) features. DETAILED DESCRIPTION

[0041] The following will discuss in detail the creation and use of the disclosed embodiments. The present disclosure provides many applicable concepts that can be embodied in various specific situations. The specific examples discussed are only illustrative of specific ways to create and use embodiments of the present invention and do not limit the scope of the present disclosure.

[0042] To provide a deep understanding of several example implementations according to the following description, the description will illustrate various specific details. An embodiment can be obtained without one or more of the specific details, and the embodiment can also be obtained using other methods, components, materials, etc. In some cases, to avoid ambiguity in different aspects of the embodiment, known structures, materials or operations are not shown or described in detail. The "embodiment" or "example" mentioned in this description indicates that a specific configuration, structure or feature described about the embodiment is included in at least one embodiment. Therefore, phrases such as "in one embodiment" or "in an example" that may appear in different places in this description do not necessarily refer to the same embodiment completely. In addition, in one or more embodiments, specific configurations, structures or features can be combined in any appropriate manner.

[0043] Embodiments of the present disclosure are described in a specific case (eg, using a multi-peripheral connection service of BLE). Some embodiments may be used for other types of communication protocols, such as conventional Bluetooth and non-Bluetooth communication protocols, such as other wireless communication protocols different from Bluetooth.

[0044] According to the BLE communication standard, data transfer can be performed between two communication devices within a periodic and time-synchronized connection event. A connection event is characterized by a negotiated start time, duration, and operating frequency (e.g., frequency set). Communication devices (also referred to as peer devices) can include central devices and peripheral devices.

[0045] In some examples, the peripheral device may have more limited available power than the central device. For example, the peripheral device may be a sensor device or a wearable device, such as a temperature sensor or a wireless headset, that has a smaller battery or a battery with more limited power storage than the central device (which may be a smartphone, tablet, or laptop). In some examples, the peripheral device may be powered by energy harvesting.

[0046] Some central devices may be powered by batteries. In some examples, instead of or in addition to batteries, the central device may have a non-battery power source, such as a gateway or computer device that plugs into an electrical outlet.

[0047] Depending on the network and device configuration, communication protocol or application, the time period of the connection event between the central device and the peripheral device can range from a few milliseconds (e.g., 4ms, 7.5ms, 10ms, etc.) to a few seconds (e.g., 4s, 5s or more). In some communication protocols, the connection event between the central device and the peripheral device can have a different time period, such as less than 4ms (e.g., 1ms or less) or more than 4s, such as 10s, 60s or more.

[0048] For a BLE connection event, the connection interval may be between 7.5 ms and 4 s. During a connection event, multiple data packets may be exchanged between the central device and the peripheral device in either direction. The central device may transmit a first data packet to the peripheral device and receive a second data packet from the peripheral device.

[0049] In the examples herein, connection events between a central device and multiple peripheral devices are described. In the case of multiple peripheral connections (MPC), a central device can provide services for more than one peripheral device under a single BLE connection event. In some embodiments, an MPC connection can occur at a single frequency (e.g., a single channel) within a known frequency set. For example, in some embodiments, a device (central or peripheral) can publish advertisements for a feature set and its capabilities; recipients of the advertisements can send requests to join and / or negotiate service parameters; and peripheral devices can dynamically modify services. A collection of service parameters may be referred to herein as a service mode.

[0050] In some embodiments, channel hopping is used for sequential MPC (eg, according to a (eg, predetermined) hopping sequence).

[0051] In some embodiments, such as described in US Patent Application No. 18 / 528,503, the MPC connection may use multiple frequencies.

[0052] In some embodiments, the examples herein may be used to secure transmissions between devices. Some embodiments described herein may advantageously achieve power savings and optimizations compared to other systems and may be more efficient and less expensive. The processes described herein may advantageously have lower latency compared to other advertising schemes.

[0053] Although the examples provided in the present disclosure are described with reference to the BLE communication standard, the steps and systems in the examples can be extended to other wireless communication standards and technologies, such as Bluetooth, IEEE 802.15.4-based protocols (such as Zigbee and Thread), ultra-wideband (UWB), WI-FI, wireless local area network (WLAN), low-power wireless personal area network (WPAN), narrowband Internet of Things (NB-IoT), long-term evolution machine type communications (LTE-M), proprietary wireless communication protocols, and other suitable wireless communication technologies (which may be standardized or non-standardized).

[0054] Figure 1 is a block diagram 100 of a hardware architecture of a central device and a peripheral device (eg, an endpoint peripheral (EPP) device) according to various examples herein. Figure 1 In various examples, the components in the process and exchange data signals. In some examples, Figure 1The devices in may be referred to as wireless devices or wireless electronic devices.

[0055] In some examples, Figure 1 The devices 102 and 104 in the BLE communication standard may be transmitting or receiving devices that can establish a connection to transmit and receive data or other packets according to the BLE communication standard. For example, each of the devices 102 and 104 may be a computer, a mobile or Internet of Things (IoT) device, or other device capable of establishing a connection with a network (such as the Internet) or other devices to exchange data packets. The hardware architecture includes hardware components that can be part of a processing and communication system.

[0056] Figure 1 1 and 104. A central device 102 (eg, central 102) and a peripheral device 104 (eg, peripheral 104) are shown. In the examples herein, the devices 102 and 104 may be referred to as nodes. Figure 1 As shown, each of the devices (e.g., the center 102 or the peripheral 104) includes one or more processors 108 and one or more memories 110. The memory 110 may include instructions 112. In some examples, the device may also include one or more transceivers 114 and one or more antennas 116 for establishing a wireless connection. These components may be coupled together via a bus 118 or in any other suitable manner. Figure 1 , an example in which components are coupled together via a bus 118 is shown.

[0057] exist Figure 1 In the embodiment, the central device 102 includes a processor 108A, a memory 110A, instructions 112A, a transceiver 114A, an antenna 116A, and a bus 118A. The peripheral device 104 includes a processor 108B, a memory 110B, instructions 112B, a transceiver 114B, an antenna 116B, and a bus 118B.

[0058] The processor 108 (e.g., 108A or 108B) may be configured to read and execute computer-readable instructions. For example, the processor 108 may be configured to call and execute instructions stored in the memory 110, including instructions 112. The processor 108 may support one or more global systems for wireless communications. In response to the processor 108 transmitting a message or data, the processor 108 drives or controls the transceiver 114 to perform transmission. In response to the processor 108 receiving a message or data, the processor 108 also drives or controls the transceiver 114 to perform reception. Therefore, the processor 108 may be regarded as a control center that performs transmission or reception, and the transceiver 114 is an executor that performs transmission and reception operations.

[0059] In some examples, any or all of processors 108 may be implemented as a general or custom processor or controller capable of executing instructions stored in memory. In some examples, any or all of processors 108 may be implemented as an application specific integrated circuit (ASIC). In some examples, any or all of processors 108 may include one or more of a field programmable gate array (FPGA), a central processing unit (CPU), a graphics processor unit (GPU), a digital signal processor (DSP). In some examples, any or all of processors 108 may include a finite state machine (FSM). Other implementations are also possible.

[0060] In some examples, the memory 110 may be coupled to the processor 108 via a bus 118 or an input / output port (not shown). In other examples, the memory 110 may be integrated with the processor 108. The memory 110 may be a non-transitory computer-readable medium configured to store various software programs and / or multiple sets of instructions, including instructions 112. For example, the memory 110 may include a high-speed random access memory and / or may include a non-volatile memory, such as one or more disk storage devices, flash memory, or another non-volatile solid-state storage device. The memory 110 may store an operating system, such as ANDROID, IOS, WINDOWS, or LINUX. The memory 110 may also store a network communication program. For example, the network communication program may be used to communicate with one or more additional devices, one or more user devices, or one or more network devices. The memory 110 may also store a user interface program. The user interface program may display the content of the application through a graphical interface and receive control operations performed by the user on the application via input controls, such as menus, dialog boxes, or physical input devices (not shown). The memory 110 may be configured to store instructions 112 for implementing the various methods and processes provided according to the various examples of the present description. The memory 110 may be implemented in any suitable manner.

[0061] Antenna 116 can be configured to enable the exchange of wireless communication signals between the processing system and a network or another system or device. Antenna 116 can be configured to convert electromagnetic energy into electromagnetic waves in free space, or convert electromagnetic waves in free space into electromagnetic energy in a transmission line. Transceiver 114 can be configured to transmit signals provided by processor 108, or can be configured to receive wireless communication signals received by antenna 116. In this example, transceiver 114 can be considered a wireless transceiver. Antenna 116 can be implemented in any suitable manner.

[0062] In some embodiments, processor 108, memory 110, and transceiver 114 may be implemented in a single integrated circuit (IC), such as within a single package. In some embodiments, part or all of memory 110 and / or transceiver 114 may be implemented outside the package including processor 108.

[0063] In some embodiments, antenna 116 may be external to the device (eg, 102 or 104 ), such as external to a package that includes components of the device (eg, 108 , 110 , and / or 116 ).

[0064] The hardware architecture of each of the devices 102, 104 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, or a WI-FI module. The hardware architecture may also support another wireless communication signal, such as a satellite signal or a shortwave signal. The hardware architecture may also be provided with a wired network interface or a local area network (LAN) interface to support wired communication.

[0065] In various examples, the hardware architecture of the devices 102, 104 may further include input / output devices (not shown), such as audio input / output devices, key input devices, displays, etc. The input / output devices may be configured to implement interaction between the hardware architecture and a user / external environment, and may include audio input / output devices, key input devices, displays, etc. The input / output devices may also include cameras, touch screens, sensors, etc. The input / output devices may communicate with the processor 108 through a user interface.

[0066] Figure 1 The hardware architecture shown is an example of implementation in various examples of the present description. During actual implementation, the hardware architecture may include more or fewer components.

[0067] In the examples herein, an MPC connection event is described, wherein a central device 102 can provide services for more than one peripheral device 104 under a single BLE connection event. In some embodiments, an MPC connection can occur under a single frequency (e.g., a single communication channel). This article describes a method for enabling a peripheral device 104 to join or exit a service. In some embodiments, the peripheral device 104 can also dynamically modify a service profile. In some embodiments, the MPC service is advantageously secure, power efficient, and scalable. In some embodiments, the MPC service can advantageously have less overhead and lower latency than other processes. In some embodiments, the MPC service can achieve power savings and power optimization at both the peripheral device 104 and the central device 102.

[0068] In the examples herein, the MPC service provides discovery, establishment, operation, and modification for a group of peripheral devices 104 that can be serviced in a single connection event. In some embodiments, the peripheral device 104 or the central device 102 can publish advertisements for MPC capabilities. In some embodiments, the central device 102 can publish advertisements for potential or existing MPC services. In some embodiments, the peripheral device 104 can publish requests for specific MPC service modes and advertisements for capabilities.

[0069] In some embodiments, the peripheral device 104 may send a request to join the MPC service, which may include a specific service mode. The peripheral device 104 may receive a response including the relevant MPC service mode from the central device 102, and may renegotiate the service mode.

[0070] In some embodiments, during MPC service, the peripheral device 104 may send an MPC service mode request, which may be acknowledged by the central device 102 or may be renegotiated. In some embodiments, multiple peripheral devices 104 may be serviced during a single connection event. A single connection event may have two or more sub-connection events, and the central device 102 may provide services to the peripheral device 104 during one or more sub-connection events of the connection event. During any sub-connection event, one or more packets may be exchanged. In some examples herein, a sleep mode is described in which the peripheral device 104 may enter a low power mode (e.g., not perform wireless communications) for a portion of a continuous connection event. In some embodiments, as described below, the MPC service may also handle encrypted communications between devices.

[0071] The examples herein describe connection events that use a single frequency to transmit packets.An example of a multi-peripheral multi-frequency system is described in US Patent Application No. 18 / 528,503.

[0072] Figure 2 2 is a schematic diagram of an MPC system 200 according to various examples herein. The MPC system 200 may be a BLE system in one example. The system 200 includes a central device 102 and EPPs 104.1, 104.2, and 104.N (e.g., endpoint peripheral (EPP) devices 104). Communication between the devices may be performed via a main MPC connection event 202 and sub-connection events 204.1, 204.2, and 204.N (sub-connection events 204). Figure 1Some components in system 200 are described, and the same numbers represent the same components. In system 200, there can be any number of peripheral devices 104, but for simplicity, EPPs 104.1, 104.2, and 104.N are shown here (where N is an arbitrary number). There can be any number of sub-connection events 204, and sub-connection events 204.1, 204.2, and 204.N are shown here (where N can be an arbitrary number).

[0073] The system 200 includes a central device 102 that manages MPC services in the system 200. In some embodiments, the central device 102 handles data exchange with other nodes in the system 200 and sets anchor points for peripheral devices 104. In some embodiments, the central device 102 manages MPC connection events in the system 200. Feature exchange and negotiation can be performed between devices and can include setting anchor points for MPC connection events and sub-connection events, setting connection event and sub-connection event durations and service modes, etc. In some examples, the anchor points indicate the time when the MPC connection event 202 or sub-connection event 204 starts and / or ends.

[0074] The main MPC connection event 202 and the sub-connection events 204.1 through 204.N may be used by the system 200. In some embodiments, all communication exchanges during the MPC connection event 202 and the associated sub-connection events 204 occur in the same communication channel (eg, at the same frequency).

[0075] The main MPC connection event 202 starts from a primary anchor point (PAP) and lasts for a set amount of time. During the main MPC connection event 202, the central device 102 communicates with the peripheral devices 104.1 to 104.N in a first communication channel (e.g., at a first frequency F0). The duration of the main MPC connection event 202 can be set by the central device 102. Sub-connection events 204 (e.g., 204.1 to 204.N) occur during the main MPC connection event 202. In some examples, the duration of the sub-connection event 204 is set by the central device 102. In some examples, each sub-connection event 204 starts with a virtual anchor point (VAP) set by the central device 102.

[0076] In the examples herein, any number of sub-connection events 204 may occur within the main MPC connection event 202. In addition, the peripheral device 104 may communicate with the central device 102 during more than one of the sub-connection events 204 in the main MPC connection event 202. For example, the central device 102 and the peripheral device 104.1 may communicate during the sub-connection event 204.1. The central device 102 and the peripheral device 104.2 may communicate during the sub-connection event 204.2. Then, the central device 102 and the peripheral device 104.1 may communicate again during the sub-connection event 204.3, wherein the sub-connection events 204.1, 204.2, and 204.3 occur sequentially in time.

[0077] In some embodiments, the main MPC connection event 202 may have any number of sub-connection events 204, and the central device 102 may communicate with each peripheral device 104 during any number of sub-connection events 204 during the main MPC connection event 202. In some embodiments, all sub-connection events 204 during the main MPC connection event 202 occur sequentially in time, and there is no temporal overlap between each sub-connection event 204. In some embodiments, such as described in U.S. Patent Application No. 18 / 528,503, because a different communication channel may be used for each sub-connection event 204 during the main MPC connection event 202, the sub-connection events 204 may (e.g., partially) overlap in time.

[0078] In some embodiments, the central device 102 may send advertisement packet(s) (e.g., advertisement messages) during the main MPC connection event 202 that are received by the plurality of peripheral devices 104. In some embodiments, each peripheral device 104 receives a separate advertisement packet during its respective child connection event 204 of the main MPC connection event 202. In some embodiments, each peripheral device 104 may receive data packets from the central device 102, but each peripheral device 104 responds to the central device 102 only if the data packets are directed to the particular peripheral device 104.

[0079] Figure 3300 is a timeline of MPC connection events according to various examples herein. The MPC connection event may be the master MPC connection event 202 as described above. The timeline 300 includes the master MPC connection event 202, sub-connection event #1 204.1, sub-connection event #2 204.2, and sub-connection event #3 204.3. The timeline 300 also includes messages 302, 304, 306, 308, 310, 312, 314, 316, 318, 320, 322, 324, and 326. The timeline 300 also includes a primary anchor point (PAP) 328 and virtual anchor points (VAPs) 330, 332, and 334.

[0080] The main MPC connection event 202 starts from PAP 328. Sub-connection event #1 204.1 starts from VAP 330. Sub-connection event #2 204.2 starts from VAP 332. Sub-connection event #3 204.3 starts from VAP 334. In this example, the central device 102 communicates with each of the peripheral devices 104 during the main MPC connection event 202 using a first communication channel (e.g., using a first frequency F0).

[0081] exist Figure 3 In the illustrated message, central device 102 is denoted by C, peripheral device 104.1 is denoted by P1, peripheral device 104.2 is denoted by P2, and peripheral device 104.3 is denoted by P3.

[0082] like Figure 3 As shown, the primary MPC connection event 202 begins with the device 102 sending a message 302 at the PAP 328 .

[0083] like Figure 3 As shown, in some embodiments, the central device 102 initiates the primary MPC connection event 202 at the PAP 328 by transmitting an advertisement packet (ADV) 302 .

[0084] The message 302 in this example is received by all peripheral devices 104 that share the primary MPC connection event 202 (e.g., peripheral devices 104.1, 104.2, and 104.3 are listening to the communication channel in which the message 302 is sent). The message 302 can be a broadcast message or a multicast message. The message 302 can be an advertising packet that includes a proposed service mode for the primary MPC connection event 202. The service mode can include a set of characteristics of the connection event, such as the connection event duration, (one or more) sub-connection event durations, anchor points (e.g., virtual anchor points for one or more of the sub-connection events of the MPC connection event 202), a channel map (e.g., where multiple frequencies are used, such as described in U.S. Patent Application No. 18 / 528,503, an indication of the communication channels to be used in subsequent MPC connection events 202, and / or an indication of the communication channels to be used during the MPC connection event 202), a transmission rate, a bandwidth, a packet size limit, encryption information, and / or any other suitable characteristics.

[0085] The recipients of message 302 (in this case, peripheral devices 104.1, 104.2, and 104.3) may confirm the service mode or propose a modification. In some embodiments, a negotiation may be performed between central device 102 and any peripheral device 104. Such modifications may take effect during the same MPC connection event 202 and / or during subsequent MPC communication events 202.

[0086] In some embodiments, message 302 includes an indication of the timing of VAPs 330, 332, and 334. In some embodiments, such as in embodiments where the timing of one or more of VAPs 330, 332, and 334 has been determined and shared with peripheral devices 104.1, 104.2, and 104.3, such an indication may be omitted from message 302.

[0087] In an example, a device receiving an advertisement (e.g., a responding device) may send an MPC join indication to the advertising device. The join indication may be a join acceptance or a join rejection. A join acceptance response is a request to join the network using the advertised service mode. A join rejection response is an indication to negotiate a service mode and may include features of a proposal for a service mode or connection event that is acceptable to the responding device. Thus, some embodiments described herein advantageously provide MPC service discovery, MPC service establishment, MPC service operation, and / or MPC service modification.

[0088] In this example, the central device 102 communicates with the peripheral device 104.1 during sub-connection event #1 204.1. Sub-connection event #1 204.1 begins from the VAP 330. The central device 102 sends a message 304 to the peripheral device 104.1. The peripheral device 104.1 responds by sending a message 306 to the central device 102. The central device 102 sends a message 308 to the peripheral device 104.1. The peripheral device 104.1 responds by sending a message 310 to the central device 102.

[0089] In this example, four messages (304, 306, 308, and 310) are exchanged between the central device 102 and the peripheral device 104.1 during the sub-connection event #1 204.1. However, in other examples, any number of messages may be transmitted (e.g., by the central device 102 or the peripheral device 104.1) during the sub-connection event #1 204.1.

[0090] Subconnection event #1 204.1 may be of any (e.g., predetermined) duration (e.g., as determined / indicated in message 302 or otherwise known to device 104.1). Central device 102 and peripheral device 104.1 may exchange messages using the service mode advertised by central device 102 or peripheral device 104.1. Central device 102 and peripheral device 104.1 may also negotiate or renegotiate a service mode using any messages transmitted between them.

[0091] During sub-connection event #2 204.2, the central device 102 communicates with the peripheral device 104.2. Sub-connection event #2 204.2 begins with the VAP 332. The central device 102 sends a message 312 to the peripheral device 104.2. The peripheral device 104.2 responds by sending a message 314 to the central device 102. In this example, two messages (312 and 314) are exchanged between the central device 102 and the peripheral device 104.2 during sub-connection event #2 204.2, but in other examples any number of messages may be transmitted (e.g., by the central device 102 or the peripheral device 104.2) during sub-connection event #2 204.2.

[0092] Sub-connection event #2 204.2 may be of any duration, and the central device 102 and the peripheral device 104.2 may exchange messages using any service mode.

[0093] During sub-connection event #3 204.3, the central device 102 communicates with the peripheral device 104.3. Sub-connection event #3 204.3 begins with the VAP 334. The central device 102 sends a message 316 to the peripheral device 104.3. The peripheral device 104.3 responds by sending a message 318 to the central device 102. The central device 102 sends a message 320 to the peripheral device 104.3. The peripheral device 104.3 responds by sending a message 322 to the central device 102. Then, the central device 102 sends a message 324 to the peripheral device 104.3. The peripheral device 104.3 responds by sending a message 326 to the central device 102. In this example, six messages (316, 318, 320, 322, 324, and 326) are exchanged between the central device 102 and the peripheral device 104.3 during sub-connection event #3 204.3, but in other examples, any number of messages may be transmitted (e.g., by the central device 102 or the peripheral device 104.3) during sub-connection event #3 204.3.

[0094] Sub-connection event #3 204.3 may be of any duration, and the central device 102 and the peripheral device 104.3 may exchange messages using any service mode.

[0095] Timeline 300 provides an example of an MPC connection event. A main MPC connection event 202 is subdivided into any number of sub-connection events 204. In some embodiments, the number of sub-connection events 204 during an MPC connection event 202 may be equal to the number of peripheral devices exchanging data during the MPC connection event 202. In some embodiments, the number of sub-connection events 204 during an MPC connection event 202 may be higher than the number of peripheral devices exchanging data during the MPC connection event 202.

[0096] Figure 3 204, but in other examples there may be any number of sub-connection events 204. Furthermore, any number of messages may be transmitted during any sub-connection event 204. In some examples, the central device 102 may communicate with the peripheral device 104 during multiple sub-connection events 204 of a given primary MPC connection event 202. For example, the central device may communicate with the peripheral device 104.1 during sub-connection event #1 204.1 and sub-connection event #3 204.3.

[0097] In some embodiments, the central device 102 may use the same service mode for each sub-connection event 204. For example, in some embodiments, the duration of each sub-connection event 204 within the MPC connection event 202 is the same.

[0098] In some embodiments, the central device 102 may use different service modes for different sub-connection events 204. For example, in some embodiments, the duration of each of the sub-connection events 204 within the MPC connection event 202 may be different.

[0099] In some embodiments, messages transmitted between the central device 102 and the peripheral devices 104 may be encrypted (e.g., using symmetric or asymmetric encryption) in some examples. For example, in some embodiments, each peripheral device 104 may have an associated (e.g., symmetric or asymmetric) encryption key, such as the peripheral device 104.1 having a first encryption key, the peripheral device 104.2 having a second encryption key, and the peripheral device 104.3 having a third encryption key. Messages sent from the central device 102 to the peripheral device 104.1 may be encrypted with the first encryption key. Messages sent from the central device 102 to the peripheral device 104.2 may be encrypted with the second encryption key. Messages sent from the central device 102 to the peripheral device 104.1 may be encrypted with the third encryption key. In embodiments where each peripheral device 104 has a separate encryption key, any device other than the device having the encryption key (such as the central device 102) will not be able to read messages from one peripheral device 104. Likewise, messages sent by the central device 102 to a particular device 104 and encrypted for that particular device 104 cannot be read by any other device 104. Thus, messages from / to one peripheral device 104 can advantageously remain secure even when those messages are received by another peripheral device 104 in the same system.

[0100] In some embodiments, one or more peripheral devices 104 may send an advertisement packet to the central device 102 to advertise its capabilities and request services.

[0101] Figure 4 400 is a timeline of MPC connection events according to various examples herein. The MPC connection event may be the master MPC connection event 202 as described above. The timeline 400 includes the master MPC connection event 202, sub-connection event #1 440.1, sub-connection event #2 440.2, and sub-connection event #3 440.3. The timeline 400 also includes messages 402, 404, 406, 408, 410, 412, 414, 416, 418, 420, 422, 424, 426, 428, and 430. The timeline 400 also includes a primary anchor point (PAP) 432 and virtual anchor points (VAPs) 434, 436, and 438.

[0102] Timeline 400 illustrates an embodiment that operates in a similar manner to the embodiment illustrated by timeline 300. However, in the embodiment illustrated by timeline 400, central device 102 transmits multiple advertisement packets (e.g., 402, 412, 418) during the same MPC connection event 202, as opposed to the embodiment illustrated by timeline 300 where central device 102 transmits a single advertisement packet (e.g., 302).

[0103] The main MPC connection event 202 starts from PAP 432. Sub-connection event #1 440.1 starts from VAP 434. Sub-connection event #2 440.2 starts from VAP 436. Sub-connection event #3 440.3 starts from VAP 438. In this example, the central device 102 communicates with each of the peripheral devices 104 during the main MPC connection event 202 using a first communication channel (e.g., using a first frequency F0).

[0104] exist Figure 4 In the messages shown, the central device 102 is represented by C, the peripheral device 104.1 is represented by P1, the peripheral device 104.2 is represented by P2, and the peripheral device 104.3 is represented by P3. In this example, the main MPC connection event 202 starts from the PAP 432. The central device 102 sends a message 402, which is an advertisement packet (ADV) in this example. The message 402 in this example is received by all peripheral devices 104 (e.g., peripheral devices 104.1, 104.2, and 104.3) that share the main MPC connection event 202. The message 402 can be a broadcast message or a multicast message. The message 402 can be an advertisement packet that includes a proposed service mode for the main MPC connection event 202. The service mode can include a set of features for the connection event, such as the connection event duration, (one or more) sub-connection event durations, anchor points, frequencies, channel maps, transmission rates, bandwidths, packet size limits, encryption information, and any other suitable features. The recipients of the message 402 (in this example, the peripheral devices 104 . 1 , 104 . 2 , and 104 . 3 ) may confirm the service mode or propose a modification. Negotiation may take place between the central device 102 and any of the peripheral devices 104 .

[0105] In some examples, the message 402 may indicate to the peripheral device 104 the duration and starting point (e.g., VAP) of one or more (or all) of the sub-connection events 440, and / or which device is to be addressed in one or more of such sub-connection events 440. For example, in an embodiment, the message 402 provides an indication of the starting point (e.g., VAP 436) of the sub-connection event #2 440.2, and an indication that the sub-connection event 440.1 is assigned to the device 104.1. In response to receiving the message 402, the peripheral devices 104.2 and 104.3 may enter or transition to a sleep mode (e.g., a low power mode) until the sub-connection event #2 440.2 begins. During the sub-connection event #1 440.1, the peripheral devices 104.2 and 104.3 may be in a sleep mode while the central device 102 communicates with the peripheral device 104.1. Therefore, some embodiments may advantageously reduce power consumption compared to other solutions.

[0106] In some embodiments, message 402 includes an indication of the timing of all other advertisement packets to be transmitted (e.g., 412, 418). In some embodiments, message 402 includes an indication of the timing of the next advertisement packet, but does not include an indication of the timing of other advertisement packets. For example, in some embodiments, message 402 includes an indication of the timing of message 412, but does not include an indication of the timing of 418, and message 412 includes an indication of the timing of message 418.

[0107] In some embodiments, each peripheral device 104 is assigned only one sub-connection event 440 during an MPC connection event 202. In some such embodiments, each peripheral device 104 may be awake during the sub-connection event assigned to such peripheral device 104, and may enter a sleep mode at the end of such sub-connection event 440 and during the remainder of the MPC connection event 202. For example, peripheral device 104.1 may enter a sleep mode after the end of sub-connection event #1 440.1 until the end of the MPC connection event 202 (and may not wake up to receive subsequent advertisement packets during the remainder of such MPC connection event 202).

[0108] In some embodiments, peripheral devices 104 may be assigned more than one sub-connection event 440 during MPC connection event 202. In some such embodiments, each peripheral may wake up to receive an advertisement packet (e.g., 412, 418) and may return to sleep mode if such an advertisement packet indicates that the associated sub-connection event is not assigned to such peripheral device 104.

[0109] In some embodiments, an initial advertisement packet (e.g., message 402) of an MPC connection event 202 includes an indication of the timing of all other advertisement packets (e.g., 412, 418) to be transmitted during a particular MPC connection event 202, but includes only an indication of the assignment of devices (e.g., 104.1) to the associated sub-connection event, while subsequent messages (e.g., 412, 418) indicate that devices are assigned to corresponding sub-connection events (e.g., 104.2 and 104.3, respectively).

[0110] As described herein, any peripheral device 104 can enter or exit sleep mode in response to receiving a timing (eg, in an advertising packet after a virtual anchor point) from the central device 102 indicating a sub-connection event 440 corresponding to the peripheral device 104 .

[0111] In this example, peripheral devices 104.2 and 104.3 may receive message 402, and these devices may enter sleep mode until their respective sub-connection events 440 begin. Here, peripheral devices 104.2 and 104.3 may enter sleep mode during sub-connection #1 440.1. During sub-connection #1 440.1, central device 102 sends message 404 to peripheral device 104.1. Peripheral device 104.1 sends message 406 to central device 102. Central device 102 sends message 408 to peripheral device 104.1. Peripheral device 104.1 sends message 410 to central device 102.

[0112] In this example, four messages (404, 406, 408, and 410) are exchanged between the central device 102 and the peripheral device 104.1 during sub-connection event #1 440.1. However, in other examples, any number of messages may be transmitted during sub-connection event #1 440.1. Sub-connection event #1 440.1 may be of any duration. The central device 102 and the peripheral device 104.1 may exchange messages using a service mode advertised by the central device 102 or the peripheral device 104.1. The central device 102 and the peripheral device 104.1 may also negotiate or renegotiate a service mode using any of the messages transmitted between them.

[0113] At the VAP 436, sub-connection event #2 440.2 begins. During sub-connection event #2 440.2, the central device 102 communicates with the peripheral device 104.2. The peripheral device 104.1 may enter sleep mode at the end of sub-connection event #1 440.1. The peripheral device 104.1 may remain in sleep mode until its next sub-connection event 440 begins, which may be during the main MPC connection event 202, or during another MPC connection event. Additionally, the peripheral device 104.3 may be in sleep mode during sub-connection #2 440.2.

[0114] During sub-connection event #2 440.2, peripheral device 104.2 receives message 412. In this example, message 412 may be received by all peripheral devices 104 (e.g., peripheral devices 104.1, 104.2, and 104.3) that share the main MPC connection event 202, provided that these devices are awake and receive messages. Message 412 may be a broadcast message or a multicast message. Message 412 may be an advertisement packet that includes a proposed service mode for sub-connection event #2 440.2. The central device 102 and peripheral device 104.2 may exchange messages using the service mode advertised by the central device 102 or the peripheral device 104.2. The central device 102 and peripheral device 104.2 may also negotiate or renegotiate a service mode using any message transmitted between them.

[0115] During sub-connection #2 440.2, the central device 102 sends a message 414 to the peripheral device 104.2. The peripheral device 104.2 sends a message 416 to the central device 102. In this example, three messages (412, 414, and 416) are exchanged between the central device 102 and the peripheral device 104.2 during sub-connection event #2 440.2. However, in other examples, any number of messages may be transmitted during sub-connection event #2 440.2. Sub-connection event #2 440.2 may be of any duration.

[0116] At the VAP 438, sub-connection event #3 440.3 begins. During sub-connection event #3 440.3, the central device 102 communicates with the peripheral device 104.3. The peripheral device 104.2 may enter sleep mode at the end of sub-connection event #2 440.2. The peripheral device 104.2 may remain in sleep mode until its next sub-connection event 440 begins, which may be during the main MPC connection event 202 or during another MPC connection event. In addition, the peripheral device 104.1 may also be in sleep mode during sub-connection #3 40.3.

[0117] The peripheral device 104.3 exits sleep mode at or before the VAP 438 and is ready to communicate with the central device 102 during the sub-connection #3 440.3. During the sub-connection event #3 440.3, the peripheral device 104.3 receives a message 418. In this example, the message 418 can be received by all peripheral devices 104 (e.g., peripheral devices 104.1, 104.2, and 104.3) that share the main MPC connection event 202, provided that these devices are awake and receive messages. The message 418 can be a broadcast message or a multicast message. The message 418 can be an advertising packet that includes a proposed service mode for the sub-connection event #3 440.3. The central device 102 and the peripheral device 104.3 can exchange messages using the service mode advertised by the central device 102 or the peripheral device 104.3. The central device 102 and the peripheral device 104.3 can also use any message transmitted between them to negotiate or renegotiate the service mode.

[0118] During subconnection #3 440.3, the central device 102 sends a message 420 to the peripheral device 104.3. The peripheral device 104.3 sends a message 422 to the central device 102. The central device 102 sends a message 424 to the peripheral device 104.3. The peripheral device 104.3 sends a message 426 to the central device 102. The central device 102 sends a message 428 to the peripheral device 104.3. The peripheral device 104.3 sends a message 430 to the central device 102.

[0119] In this example, seven messages (418, 420, 422, 424, 426, 428, and 430) are exchanged between the central device 102 and the peripheral device 104.3 during sub-connection event #3 440.3. However, in other examples, any number of messages may be transmitted during sub-connection event #3 440.3. Sub-connection event #3 440.3 may be of any duration.

[0120] In this example, the advertising messages (messages 402, 412, and 418) may be different from each other. The peripheral device 104 may enter a sleep mode at a specific time to reduce power consumption. The peripheral device 104 may exit its corresponding sleep mode (e.g., wake up) at a set time (e.g., a first time, a second time, etc.) to communicate during a specific sub-connection event 440. The peripheral device 104 may also enter or leave a service and rejoin at a later time, which may reduce power consumption. Data may be exchanged with multiple peripheral devices 104 during an MPC connection event, rather than waiting for a later MPC connection event. Service modes and features may be negotiated between devices.

[0121] Figure 55 is a timeline 500 of MPC connection events according to various examples herein. The MPC connection event may be the master MPC connection event 202 as described above. The timeline 500 includes the master MPC connection event 202, sub-connection event #1 532.1, sub-connection event #2 532.2, and sub-connection event #3 532.3. The timeline 500 also includes messages 502, 504, 506, 508, 510, 512, 514, 516, 518, 520, 522, and 524. The timeline 500 also includes a primary anchor point (PAP) 526 and virtual anchor points (VAPs) 528 and 530.

[0122] Timeline 500 illustrates an embodiment that operates in a similar manner to the embodiment illustrated in timeline 300. However, in the embodiment illustrated in timeline 500, central device 102 does not transmit advertisement packets during MPC connection event 202, in contrast to the embodiment illustrated in timeline 300 where central device 102 transmits a single advertisement packet (e.g., 302). Figure 5 In the illustrated embodiment, peripheral devices 104 (e.g., 104.1, 104.2, and 104.3) use an auto-discovery method to determine when a sub-connection event assigned to such device 104 begins (e.g., by each device 104 determining whether a packet is for such device 104, for example based on a device identifier or the ability to decrypt a message).

[0123] like Figure 5 As shown, advertisement messages are not shown in timeline 500. In some embodiments, in this example, a service mode is negotiated before the main MPC connection event 202 begins. The main MPC connection event 202 begins with PAP 526. Sub-connection event #1 532.1 begins with PAP 526. Sub-connection event #2 532.2 begins with VAP 528. Sub-connection event #3 532.3 begins with VAP 530. In this example, central device 102 communicates with each of peripheral devices 104 using a first communication channel (e.g., using a first frequency F0) during the main MPC connection event 202.

[0124] exist Figure 5 In the messages shown, the central device 102 is represented by C, the peripheral device 104.1 is represented by P1, the peripheral device 104.2 is represented by P2, and the peripheral device 104.3 is represented by P3. At the PAP 526, sub-connection event #1 532.1 begins. During sub-connection #1 532.1, the central device 102 sends a message 502 to the peripheral device 104.1. The peripheral device 104.1 sends a message 504 to the central device 102. The central device 102 sends a message 506 to the peripheral device 104.1. The peripheral device 104.1 sends a message 508 to the central device 102.

[0125] In this example, the other peripheral devices 104 may wake up during sub-connection event #1 532.1 and receive messages 502 and 506 from the central device 102. The peripheral devices 104.2 and 104.3 may receive the messages 502 and 506. The peripheral devices 104.2 and 104.3 may respond to the central device 102 only if the messages 502 and 506 are directed to them. The peripheral device 104 may determine whether the message is directed to it by reading the device identifier in the message, where the device identifier identifies the device to which the message is directed.

[0126] In some examples, messages from central device 102 may be encrypted with a key assigned to a particular peripheral device 104. In some such embodiments, peripheral devices 104 may ignore or discard any messages that they are unable to decrypt, and respond to messages that can be successfully decrypted (e.g., as opposed to using an explicit device identifier to determine whether to respond to a message).

[0127] In this example, four messages (502, 504, 506, and 508) are exchanged between the central device 102 and the peripheral device 104.1 during the sub-connection event #1 532.1. However, in other examples, any number of messages may be transmitted during the sub-connection event #1 532.1. The sub-connection event #1 532.1 may be of any duration.

[0128] At the VAP 528, sub-connection event #2 532.2 begins. During sub-connection #2 532.2, the central device 102 sends a message 510 to the peripheral device 104.2. The peripheral device 104.2 sends a message 512 to the central device 102. Similar to sub-connection event #1 532.1, the peripheral devices 104.1 and 104.3 may receive the message 510, but may ignore or discard it because the message 510 is directed to another peripheral device (e.g., the peripheral device 104.1). Two messages (510 and 512) are exchanged between the central device 102 and the peripheral device 104.2 during sub-connection event #2 532.2. In other examples, any number of messages may be transmitted during sub-connection event #2 532.2, and the sub-connection event #2 532.2 may be of any duration.

[0129] At the VAP 530, sub-connection event #3 532.3 begins. During sub-connection #3 532.3, the central device 102 sends a message 514 to the peripheral device 104.3. The peripheral device 104.3 sends a message 516 to the central device 102. The central device 102 sends a message 518 to the peripheral device 104.3. The peripheral device 104.3 sends a message 520 to the central device 102. The central device 102 sends a message 522 to the peripheral device 104.3. The peripheral device 104.3 sends a message 524 to the central device 102. Similar to sub-connection event #1 532.1 and sub-connection event #2 532.2, the peripheral devices 104.1 and 104.2 may receive the messages 514, 518, 522, etc., but may ignore or discard these messages because they are directed to another peripheral device (e.g., the peripheral device 104.3). Six messages are exchanged between the central device 102 and the peripheral device 104.3 during sub-connection event #3 532.3. In other examples, any number of messages may be transmitted during sub-connection event #3 532.3, and sub-connection event #3 532.3 may be of any duration.

[0130] Figure 6 600 is a flow chart of a method 600 for MPC connection events according to various examples herein. The steps of method 600 may be performed in any suitable order. In some examples, the above description of Figure 1 and Figure 2 The hardware components described above can be used to perform the method 600. In some examples, any suitable hardware, software, or digital logic can perform the method 600.

[0131] Method 600 begins at 610, where a first device transmits a first message during a first connection event. For example, central device 102 transmits a message during primary MPC connection event 202. In one example, the first message may be an advertising packet. The first message may be broadcast or multicast to multiple other devices. In some examples, peripheral device 104 transmits the first message.

[0132] The method 600 continues at 620 where the first device receives a first response to the first message from the second device during the first connection event. In one example, the second device may be the first peripheral device 104 .

[0133] The method 600 continues at 630, where the first device receives a second response to the first message from a third device during the first connection event. In one example, the third device may be the second peripheral device 104. In this example, multiple peripheral devices 104 may communicate with the central device 102 during a single connection event.

[0134] The method 600 continues at 640, where the first device receives a third response from the second device during the first connection event. In this example, the first device (such as the central device 102) receives a first response from the first peripheral device 104 (e.g., the second device), then receives a second response from the second peripheral device 104 (e.g., the third device), and then receives a third response from the first peripheral device 104 (e.g., the second device). Therefore, in the examples herein, a more complex connection event 202 is described, which includes two or more sub-connection events 204. A device can communicate with another device during multiple non-contiguous sub-connection events 204 during the connection event 202. During the connection event 202, three or more devices can communicate with each other.

[0135] like Figure 6 (as well as Figure 3-Figure 5 ), in some embodiments, the number of packets exchanged during different sub-connection events of the main MPC connection event may be different.

[0136] Figure 7 700 is a flow chart of a method 700 for MPC connection events according to various examples herein. The steps of method 700 may be performed in any suitable order. In some examples, the above description of Figure 1 and Figure 2 The method 700 may be performed by the hardware components described above. In some examples, the method 700 may be performed by any suitable hardware, software, or digital logic.

[0137] Method 700 begins at 710, where a first device receives a first message from a second device during a first connection event. In one example, the first device may be a peripheral device 104, and the second device may be a central device 102. The first message may be an advertising packet or any other type of message.

[0138] The method 700 continues at 720 where the first device transmits a second message during the first connection event. The second message may be a response to the first message. In one example, the second message may be transmitted by the peripheral device 104.

[0139] Method 700 continues at 730, where after transmitting the second message, the first device enters a low power mode. In one example, the low power mode can be a sleep mode. Figure 4 As described above, the peripheral device 104.1 may enter a sleep mode or a low power mode after the sub-connection event #1 440.1 ends.

[0140] The method 700 continues at 740 where the first device exits the low power mode. In one example, the first device exits the low power mode to prepare to receive one or more messages in another sub-connection event 204 of the main connection event 202.

[0141] The method 700 continues at 750, where after exiting the low power mode, the first device transmits a third message during the first connection event. As shown in this example, the first device can communicate with another device during a first sub-connection event 204, enter a sleep mode for one or more sub-connection events 204, and then wake up for a second sub-connection event 204 and communicate again, all during a single main connection event 202. In these examples, more than two devices can communicate during a single main connection event 202, and the devices can communicate during non-consecutive sub-connection events 204 of the main connection event 202. The devices can also save power by entering or exiting a low power mode at appropriate times during the main connection event 202.

[0142] In some embodiments, such as Figure 7 As shown, the peripheral device 104 may request specific data from the central device 102 during a first connection event 204. The time taken to generate such data may be more than the time for the central device 102 to respond to such a request during the same sub-connection event, but may be less than the total duration of the main MPC event 202. In some such embodiments, the peripheral device 104 may enter a low power mode while the device 102 is generating such data. The device 104 may later wake up and receive such data in a later sub-connection event of the same main MPC event 202. Thus, in some such embodiments, latency is advantageously reduced, in contrast to conventional systems in which a device 104 requesting data must wait until the next connection event to receive such data.

[0143] Figure 8 800 is a flow chart of a method 800 for MPC connection events according to various examples herein. The steps of method 800 may be performed in any suitable order. In some examples, the above description of Figure 1 and Figure 2 The method 800 may be performed by the hardware components described above. In some examples, the method 800 may be performed by any suitable hardware, software, or digital logic.

[0144] The method 800 begins at 810, where an electronic device transmits a first advertising packet during a first connection event, where the first advertising packet indicates a first time for a second advertising packet. In one example, the electronic device is a central device 102. In one example, the first advertising packet can be broadcast or multicast to multiple peripheral devices 104. The first advertising packet can include any information about a service mode or feature set, such as specifically supported features, and can also indicate a time when the second advertising packet will be transmitted.

[0145] The method 800 continues at 820, where the electronic device receives a first response from the first device in response to the first advertisement packet during the first connection event. In one example, the first device can be the peripheral device 104. The first response can be an acceptance of the service mode from the first advertisement packet, or can be a negotiation of the service mode. In one example, the first response can be received during the first sub-connection event 204 of the first connection event 202.

[0146] The method 800 continues at 830 , where the electronic device transmits the second advertisement packet at a first time during the first connection event. In one example, the first time may be during the second sub-connection event 204 of the first connection event 202 .

[0147] The method continues at 840, where the electronic device receives a second response in response to the second advertising packet during the first connection event. The second response can be from the first device or another device. In one example, the second advertising packet indicates a second time for a third advertising packet. In another example, the second time is based on data exchanged after transmitting the first advertising packet.

[0148] Fig. 9 900 is a flow chart of a method 900 for MPC connection events according to various examples herein. The steps of method 900 may be performed in any suitable order. In some examples, the above description of Figure 1 and Figure 2 The method 900 may be performed by the hardware components described above. In some examples, the method 900 may be performed by any suitable hardware, software, or digital logic.

[0149] Method 900 begins at 910 , where an electronic device receives a first advertisement packet during a first connection event, where the first advertisement packet indicates a first time for a second advertisement packet. In one example, the electronic device may be a peripheral device 104 .

[0150] Method 900 continues at 920, where the electronic device determines that the first advertisement packet is directed to a different device. As described herein, the electronic device can determine that the advertisement packet is directed to a different device by reading a device identifier in the advertisement packet. The electronic device can also determine that the advertisement packet is directed to a different device if the electronic device cannot decrypt the advertisement packet.

[0151] Method 900 continues at 930 where, in response to the determination, the electronic device transitions to a sleep mode. The electronic device may transition to a sleep mode to save power until a later time when the electronic device will resume communication with other devices in the system (eg, such as waking up at the time of receiving the next advertising packet).

[0152] The method 900 continues at 940 where the electronic device wakes up at a first time. In one example, the first time may be the start of a specific sub-connection event 204.

[0153] Method 900 continues at 950 where the electronic device receives a second advertisement packet. The second advertisement packet may be sent by the central device 102 in one example or by a different device in another example.

[0154] Method 900 continues at 960, where the electronic device transmits a response to the second advertisement packet. As described herein, the response can be transmitted during the current sub-connection event 204 or a subsequent sub-connection event 204 of the main connection event 202. In some examples, the response can include a negotiation of a feature set or service mode.

[0155] In one example, the second advertisement packet indicates a second time for the third advertisement packet. In another example, the second advertisement packet includes a feature set or service mode for the first connection event.

[0156] Fig.10 is a flow chart of a method 1000 for MPC connection events according to various examples herein. The steps of method 1000 may be performed in any suitable order. In some examples, the above description of Figure 1 and Figure 2 The method 1000 may be performed by the hardware components described above. In some examples, the method 1000 may be performed by any suitable hardware, software, or digital logic.

[0157] Method 1000 begins at 1010, where a first device transmits a first broadcast message during a first connection event. As an example, central device 102 transmits a message during a primary MPC connection event 202. In one example, the first message may be an advertisement packet. In some examples, peripheral device 104 transmits the first message. The first broadcast message may provide an indication that an associated child connection event is assigned to a second device.

[0158] Method 1000 continues at 1020, where the first device transmits a first message to the second device during the first connection event. The first message can be a message directed to the second device. In one example, the first message can be transmitted during the first sub-connection event. In one example, the second device can be the peripheral device 104.

[0159] Method 1000 continues at 1030, where the first device receives a first response to the first message from the second device during the first connection event. In one example, the first device may receive the first response during the first sub-connection event.

[0160] The method 1000 continues at 1040, where the first device transmits a second message to a third device during the first connection event. In one example, the third device may be the peripheral device 104. In one example, the first device may transmit the second message during a second sub-connection event.

[0161] Method 1000 continues at 1050, where the first device receives a second response to the second message from the third device during the first connection event. In one example, the second response may be received by the first device during a second sub-connection event.

[0162] Method 1000 continues at 1060, where the first device transmits a third message to the second device during the first connection event. The third message may be transmitted during the first sub-connection event, the third sub-connection event, or another sub-connection event.

[0163] Method 1000 continues at 1070, where the first device receives a third response to the third message from the second device during the first connection event. In one example, the third response can be received during a third sub-connection event.

[0164] Fig.11 1 is a flow chart of a method 1100 for MPC connection events according to various examples herein. The steps of method 1100 may be performed in any suitable order. In some examples, the above description of Figure 1 and Figure 2 The method 1100 may be performed by the hardware components described above. In some examples, the method 1100 may be performed by any suitable hardware, software, or digital logic.

[0165] The method 1100 begins at 1110, where a first device receives a first message from a second device during a first connection event. In one example, the first device may be a peripheral device 104. In one example, the second device may be a central device 102. The first message may be received during a first sub-connection event of the first connection event.

[0166] The method 1100 continues at 1120 where the first device transmits a second message during the first connection event. In one example, the second message can be transmitted to the first device, such as the central device 102.

[0167] The method 1100 continues at 1130, where after transmitting the second message, the first device enters a low power mode. In one example, the low power mode can be a sleep mode. The first device can remain in the low power mode for any period of time.

[0168] The method 1100 continues at 1140, where the first device remains in a low power mode while the second device provides services to the third device. The third device may be another peripheral device 104 provided services by the central device 102. The second device may provide services to the third device during the first connection event. In one example, the second device may provide services to the third device during a second sub-connection event of the first connection event.

[0169] The method 1100 continues at 1150, where the first device exits the low power mode during the first connection event. The first device may exit the low power mode after a predefined duration has elapsed. The first device may exit the low power mode during any sub-connection event of the first connection event.

[0170] Method 1100 continues at 1160, where the first device receives a third message from the second device after exiting the low power mode. In one example, the second device may send the third message at a predetermined time after the first device exits the low power mode.

[0171] The method 1100 continues at 1170, where the first device transmits a fourth message. In one example, the first device may transmit the fourth message to the second device. In one example, the fourth message may be a response to the third message. The fourth message may be transmitted during any sub-connection event of the first connection event.

[0172] In the examples herein, a connection event between a central device and multiple peripheral devices is described. In some embodiments, in the case of multiple peripheral connections, the central device can provide services for more than one peripheral under a single BLE connection event. Compared with other systems, providing services for more than one peripheral in a single connection event can provide more efficient transmission by reducing overhead. In the examples herein, a device (central or peripheral) can publish advertisements for feature sets and their capabilities. The recipient of the advertisement can send a request to join and / or negotiate a service mode and feature set. Therefore, different peripherals can utilize different feature sets during a single connection event.

[0173] In the examples herein, the peripheral device can dynamically modify the service by renegotiating the feature set with the central device. The transmission between the devices can be secured with encryption using the examples herein. The examples described herein can also achieve power savings by allowing the peripheral device to enter a sleep mode or low power mode during a portion of the main connection event. Since the central device provides services for multiple peripheral devices during a single connection event, the process described herein can have lower latency than other advertising schemes.

[0174] Example embodiments of the present disclosure are summarized herein. Other embodiments may also be understood based on the entirety of this specification and the claims filed herein.

[0175] Example 1. A method comprising: transmitting a first message by a first device during a first connection event; receiving a first response to the first message from a second device at the first device during the first connection event; receiving a second response to the first message by the first device from a third device during the first connection event; and receiving a third response by the first device from the second device during the first connection event.

[0176] Example 2. The method of Example 1, wherein the first device receives the third response after the first response and before the second response.

[0177] Example 3. A method according to one of Examples 1 or 2, wherein the first device receives the third response after the first response and after the second response.

[0178] Example 4. A method according to one of Examples 1 to 3, wherein the first message is a broadcast message.

[0179] Example 5. The method of one of Examples 1 to 4, wherein the first message is a multicast message directed to the second device and the third device.

[0180] Example 6. A method according to one of Examples 1 to 5, further comprising: transmitting a second message by the first device to the second device during the first connection event; and transmitting a third message to the third device during the first connection event, wherein the second message is encrypted with a first encryption key associated with the second device, and wherein the third message is encrypted with a second encryption key associated with the third device.

[0181] Example 7. The method of one of Examples 1 to 6, wherein all packet exchanges between the first device and another device during the first connection event occur on the same channel.

[0182] Example 8. A method according to one of Examples 1 to 7, wherein the first connection event has a first multi-peripheral connection service mode, and the method also includes transmitting a second message by the first device during a second connection event after the first connection event, wherein the second connection event has a second multi-peripheral connection service mode different from the first multi-peripheral connection service mode.

[0183] Example 9. The method of one of Examples 1 to 8, further comprising: transmitting the first message from the first device to a fourth device during the first connection event; and receiving a fourth response from the fourth device at the first device during the first connection event.

[0184] Example 10. A method according to one of Examples 1 to 9, wherein the first message includes a first duration of a first sub-connection event for the second device during the first connection event, and a second duration of a second sub-connection event for the third device during the first connection event.

[0185] Example 11. The method of one of Examples 1 to 10, wherein a number of packets exchanged between the first device and the second device during the first sub-connection event is greater than one.

[0186] Example 12. The method of one of Examples 1 to 11, wherein a number of packets exchanged between the first device and the second device during the first sub-connection event is greater than two.

[0187] Example 13. The method of one of Examples 1 to 12, wherein a number of packets exchanged during the first sub-connectivity event is different than a number of packets exchanged during the second sub-connectivity event.

[0188] Example 14. A method according to one of Examples 1 to 13, wherein the first duration and the second duration are different durations.

[0189] Example 15. The method of one of Examples 1 to 14, wherein the first device receives the first response during the first sub-connection event and receives the second response during the second sub-connection event.

[0190] Example 16. The method of one of Examples 1 to 15, wherein the first device receives the third response during the second sub-connection event.

[0191] Example 17. A method according to one of Examples 1 to 16, wherein the first message includes a third length of a third sub-connection event for the second device during the first connection event, and wherein the first device receives the third response during the third sub-connection event.

[0192] Example 18. The method of one of Examples 1 to 17, wherein the first sub-connection event and the third sub-connection event are not consecutive sub-connection events.

[0193] Example 19. A method according to one of Examples 1 to 18, wherein the first sub-connection event is an initial sub-connection event during the first connection event, and the third sub-connection event is a last sub-connection event during the first connection event.

[0194] Example 20. The method of one of Examples 1 to 19, further comprising transmitting, by the first device, a third message during the third sub-connection event, the third message being responsive to the first response.

[0195] Example 21. The method of one of Examples 1 to 20, wherein the second device transitions to a sleep mode between transmitting the first response and transmitting the third response.

[0196] Example 22. A method according to one of Examples 1 to 21, wherein the first device is a central Bluetooth Low Energy (BLE) device.

[0197] Example 23. The method of one of Examples 1 to 22, wherein the second device is a peripheral BLE device.

[0198] Example 24. The method of one of Examples 1 to 23, wherein the first message is an advertisement packet including a feature set for the first connection event.

[0199] Example 25. The method of one of Examples 1 to 24, wherein the feature set comprises a duration, an anchor point, or a transmission rate of the first connection event.

[0200] Example 26. The method of one of Examples 1 to 25, wherein the first response comprises a request for a multi-peripheral service mode from the second device.

[0201] Example 27. A method comprising: receiving a first message from a second device at a first device during a first connection event; transmitting a second message by the first device during the first connection event; entering a low power mode at the first device after transmitting the second message; exiting the low power mode at the first device; and transmitting a third message by the first device during the first connection event after exiting the low power mode.

[0202] Example 28. The method of Example 27, wherein the first message is a broadcast message or a multicast message.

[0203] Example 29. The method of one of Examples 27 or 28, wherein the first message includes an advertisement packet specifying a first sub-connection event for the first device and a second sub-connection event for a third device.

[0204] Example 30. A method according to one of Examples 27 to 29, wherein the advertising grouping also specifies a third sub-connection event for the first device, wherein the first device transmits the second message during the first connection event and transmits the third message during the third connection event.

[0205] Example 31. The method of one of Examples 27 to 30, wherein the advertising packet indicates a sub-connection event time, wherein the first device exits the low power mode based on the sub-connection event time.

[0206] Example 32. The method of one of Examples 27 to 31, further comprising: receiving the first message from the second device at a third device during the first connection event; determining that the first message is directed to a different device; and discarding the first message.

[0207] Example 33. The method of one of Examples 27 to 32, wherein determining that the first message is directed to a different device comprises reading a device identifier in the first message.

[0208] Example 34. The method of one of Examples 27 to 33, wherein the second message comprises a request to renegotiate one or more characteristics of the first connection event.

[0209] Example 35. A method according to one of Examples 27 to 34, wherein the second message includes one or more capabilities of the first device.

[0210] Example 36. The method of one of Examples 27 to 35, wherein a third device receives the first message from the second device during the first connection event.

[0211] Example 37. An electronic device comprising: a transceiver; and a processor configured to: transmit a first advertising packet using the transceiver during a first connection event, wherein the first advertising packet indicates a first time for a second advertising packet; receive a first response from a first device via the transceiver in response to the first advertising packet during the first connection event; transmit the second advertising packet using the transceiver at the first time during the first connection event; and receive a second response in response to the second advertising packet during the first connection event.

[0212] Example 38. The electronic device of Example 37, wherein receiving the second response comprises receiving the second response from the first device.

[0213] Example 39. The electronic device of one of Examples 37 or 38, wherein receiving the second response comprises receiving the second response from a second device.

[0214] Example 40. An electronic device according to one of Examples 37 to 39, wherein the second advertising packet indicates a second time for a third advertising packet, and wherein the processor is configured to transmit the third advertising packet using the transceiver at the second time during the first connection event.

[0215] Example 41. The electronic device of one of Examples 37 to 40, wherein the second time is based on data exchanged after transmitting the first advertising packet.

[0216] Example 42. The electronic device of one of Examples 37 to 41, wherein a first time period between transmitting the first advertising packet and the second advertising packet is different from a second time period between transmitting the second advertising packet and the third advertising packet.

[0217] Example 43. The electronic device of one of Examples 37 to 42, wherein the first advertisement packet includes a feature set for the first connection event.

[0218] Example 44. The electronic device of one of Examples 37 to 43, wherein the first response comprises a request to renegotiate characteristics of the first connection event.

[0219] Example 45. An electronic device according to one of Examples 37 to 44, wherein the processor is further configured to: receive the first response during a first sub-connection event of the first connection event; and receive the second response during a second sub-connection event of the first connection event.

[0220] Example 46. An electronic device comprising: a transceiver; and a processor configured to: during a first connection event, receive a first advertising packet using the transceiver, wherein the first advertising packet indicates a first time for a second advertising packet; determine that the first advertising packet is directed to a different device; in response to the determination, transition to a sleep mode; wake up at the first time; receive the second advertising packet using the transceiver; and transmit a response to the second advertising packet using the transceiver.

[0221] Example 47. The electronic device of Example 46, wherein the second advertisement packet indicates a second time for a third advertisement packet.

[0222] Example 48. The electronic device of one of Examples 46 or 47, wherein the second advertisement packet includes a feature set for the first connection event.

[0223] Example 49. The electronic device of one of Examples 46 to 48, wherein the response comprises a request to renegotiate characteristics of the first connection event.

[0224] Example 50. An electronic device according to one of Examples 46 to 49, wherein the processor is further configured to: receive the first advertising packet during a first sub-connection event of the first connection event; and receive the second advertising packet during a second sub-connection event of the first connection event.

[0225] Example 51. A method comprising: during a first connection event, transmitting a first broadcast message by a first device; during the first connection event, transmitting a first message by the first device to a second device; during the first connection event, receiving a first response to the first message at the first device from the second device; during the first connection event, transmitting a second message by the first device to a third device; during the first connection event, receiving a second response to the second message by the first device from the third device; during the first connection event, transmitting a third message by the first device to the second device; and during the first connection event, receiving a third response to the third message by the first device from the second device.

[0226] Example 52. The method of Example 51, wherein the first message is an advertising message.

[0227] Example 53. A method according to one of Examples 51 or 52, further comprising: transmitting a fourth message by the first device to the second device during the first connection event; and transmitting a fifth message to the third device during the first connection event, wherein the fourth message is encrypted with a first encryption key associated with the second device, and wherein the fifth message is encrypted with a second encryption key associated with the third device.

[0228] Example 54. A method according to one of Examples 51 to 53, wherein the first connection event has a first multi-peripheral connection service mode, and the method further includes transmitting a fourth message by the first device during a second connection event after the first connection event, wherein the second connection event has a second multi-peripheral connection service mode different from the first multi-peripheral connection service mode.

[0229] Example 55. A method according to one of Examples 51 to 54, further comprising: transmitting a fourth message from the first device to a fourth device during the first connection event; and receiving a fourth response from the fourth device at the first device during the first connection event.

[0230] Example 56. A method according to one of Examples 51 to 55, wherein the first broadcast message includes a first duration of a first sub-connection event for the second device during the first connection event, and a second duration of a second sub-connection event for the third device during the first connection event.

[0231] Example 57. A method according to one of Examples 51 to 56, wherein the first device receives the first response during the first sub-connection event and receives the second response during the second sub-connection event.

[0232] Example 58. A method according to one of Examples 51 to 57, wherein the first message includes a third duration of a third sub-connection event for the second device during the first connection event, and the first device receives the third response during the third sub-connection event.

[0233] Example 59. The method of one of Examples 51 to 58, further comprising transmitting, by the first device during the third sub-connection event, a fourth message, the fourth message being responsive to the first response.

[0234] Example 60. A method comprising: receiving a first message from a second device at a first device during a first connection event; transmitting a second message by the first device during the first connection event; entering a low power mode at the first device after transmitting the second message; remaining in the low power mode while the second device provides services to a third device; exiting the low power mode at the first device during the first connection event; receiving a third message from the second device at the first device after exiting the low power mode; and transmitting a fourth message by the first device.

[0235] Example 61. The method of Example 60, wherein the first message is a broadcast message or a multicast message during the first connection event.

[0236] Example 62. The method of one of Examples 60 or 61, wherein the first message includes an advertisement packet specifying a first sub-connection event for the first device and a second sub-connection event for the third device.

[0237] Example 63. A method according to one of Examples 60 to 62, wherein the advertising group also specifies a third sub-connection event for the first device, wherein the first device transmits the second message during the first sub-connection event and transmits the fourth message during the third sub-connection event.

[0238] Example 64. The method of one of Examples 60 to 63, further comprising: receiving the first message from the second device at the third device during the first connection event; determining that the first message is directed to a different device; and discarding the first message.

[0239] Example 65. The method of one of Examples 60 to 64, wherein the first device remains in the low power mode until a second connection event.

[0240] Example 66. An electronic device comprising: a transceiver; and a processor configured to: transmit a first advertising packet using the transceiver during a first connection event, wherein the first advertising packet indicates a first time for a second advertising packet; receive a first response from a first device via the transceiver in response to the first advertising packet during a first sub-connection event of the first connection event; transmit the second advertising packet using the transceiver at the first time during a second sub-connection event of the first connection event; and receive a second response in response to the second advertising packet during the first connection event.

[0241] Example 67. The electronic device of Example 66, wherein the second advertising packet indicates a second time for a third advertising packet, wherein the processor is configured to transmit the third advertising packet using the transceiver at the second time during the first connection event.

[0242] Example 68. An electronic device according to one of Examples 66 or 67, wherein a first time period between transmitting the first advertising packet and the second advertising packet is different from a second time period between transmitting the second advertising packet and the third advertising packet.

[0243] Example 69. The electronic device of one of Examples 66 to 68, wherein the third advertisement packet is transmitted during a third sub-connection event of the first connection event.

[0244] Although the present disclosure has been described with reference to illustrative embodiments, this description is not intended to be limiting. Various modifications and combinations of the illustrative embodiments, as well as other embodiments, will become apparent to those skilled in the art upon reference to this description.

Claims

1. A method comprising: During the first connection event, transmitting a first message by the first device; receiving, at the first device, a first response to the first message from a second device during the first connection event; receiving, by the first device, a second response to the first message from a third device during the first connection event; as well as During the first connection event, a third response is received by the first device from the second device.

2. The method according to claim 1, wherein: The first device receives the third response after the first response and before the second response.

3. The method according to claim 1, wherein: The first device receives the third response after the first response and after the second response.

4. The method according to claim 1, wherein: The first message is a broadcast message.

5. The method according to claim 1, wherein: The first message is a multicast message directed to the second device and the third device.

6. The method according to claim 1, further comprising: During the first connection event, transmitting a second message by the first device to the second device; as well as During the first connection event, a third message is transmitted to the third device, wherein the second message is encrypted with a first encryption key associated with the second device, and wherein the third message is encrypted with a second encryption key associated with the third device.

7. The method according to claim 1, wherein: All packet exchanges between the first device and another device during the first connection event occur on the same channel.

8. The method according to claim 1, wherein: The first connection event has a first multi-peripheral connection service mode, and the method further includes transmitting a second message by the first device during a second connection event after the first connection event, wherein the second connection event has a second multi-peripheral connection service mode different from the first multi-peripheral connection service mode.

9. The method according to claim 1, further comprising: transmitting, during the first connection event, the first message from the first device to a fourth device; as well as During the first connection event, a fourth response is received at the first device from the fourth device.

10. The method according to claim 1, wherein: The first message includes a first duration of a first sub-connection event for the second device during the first connection event, and a second duration of a second sub-connection event for the third device during the first connection event.

11. The method according to claim 10, wherein: The number of packets exchanged between the first device and the second device during the first sub-connection event is greater than one.

12. The method according to claim 11, wherein: The number of packets exchanged between the first device and the second device during the first sub-connection event is greater than two.

13. The method according to claim 10, wherein: The number of packets exchanged during the first sub-connection event is different from the number of packets exchanged during the second sub-connection event.

14. The method according to claim 10, wherein: The first duration and the second duration are different durations.

15. The method according to claim 10, wherein: The first device receives the first response during the first sub-connection event and receives the second response during the second sub-connection event.

16. The method according to claim 15, wherein: The first device receives the third response during the second sub-connection event.

17. The method according to claim 15, wherein: The first message includes a third length of a third sub-connection event for the second device during the first connection event, and wherein the first device receives the third response during the third sub-connection event.

18. The method according to claim 17, wherein: The first sub-connection event and the third sub-connection event are not consecutive sub-connection events.

19. The method according to claim 17, wherein: The first sub-connection event is an initial sub-connection event during the first connection event, and the third sub-connection event is a last sub-connection event during the first connection event.

20. The method of claim 17, further comprising transmitting, by the first device, a third message during the third sub-connection event, the third message being responsive to the first response.

21. The method according to claim 1, wherein: The second device transitions to a sleep mode between transmitting the first response and transmitting the third response.

22. The method according to claim 1, wherein: The first device is a central Bluetooth Low Energy (BLE) device.

23. The method according to claim 1, wherein: The second device is a peripheral BLE device.

24. The method according to claim 1, wherein: The first message is an advertisement packet including a feature set for the first connection event.

25. The method according to claim 24, wherein: The set of characteristics includes a duration, an anchor point, or a transmission rate of the first connection event.

26. The method of claim 1, wherein: The first response includes a request for a multi-peripheral service mode from the second device.

Images