Synchronization messages for peripheral devices

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a central device may send a first communication to initiate a first communication event. The central device may transmit a first synchronization message associated with the first peripheral device and a second synchronization message associated with the second peripheral device during a first time resource and a second time resource associated with the first communication event, respectively. The central device may send a second communication to initiate a second communication event. The central device may monitor a first response from the first peripheral during a third time resource during a second communication event, and monitor a second response from the second peripheral during a fourth time resource. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 381,378, filed on October 28, 2022, entitled “SYNCHRONIZATION MESSAGES FOR PERIPHERAL DEVICES,” and U.S. Non-Provisional Patent Application No. 18 / 183,032, filed on March 13, 2023, entitled “SYNCHRONIZATION MESSAGES FOR PERIPHERAL DEVICES,” which are hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatuses related to synchronization messaging for peripheral devices. Background Art

[0004] A Wireless Personal Area Network (WPAN) is a short-range wireless network typically established by a user to interconnect various personal devices, sensors, and / or appliances located within a specific distance or area of the user. (BT) protocol, Low Energy Protocol or A WPAN based on a communication protocol such as the Bluetooth® protocol can provide wireless connectivity to peripheral devices within a specific distance (such as 5 meters, 10 meters, 20 meters, 100 meters, etc.) of a user.

[0005] Bluetooth is a short-range wireless communication protocol that supports a WPAN between a central device (such as a host device) and at least one peripheral device (such as a client device).The power consumption associated with Bluetooth communication may make Bluetooth impractical in certain applications.

[0006] To address the power consumption issues associated with Bluetooth, the Bluetooth Bluetooth Low Energy (BLE) (also referred to herein as WPAN LE). Specifically, BLE takes advantage of infrequent transmission of data by using low duty cycle operation and placing one or both of the central device and the peripheral device in sleep mode between data transmissions, thereby saving power. Example applications using BLE include battery-powered sensors and actuators in various medical, industrial, consumer, and fitness applications. BLE can also be used to connect devices such as smartphones, tablets, and laptops that support BLE. Although traditional Bluetooth and BLE provide certain advantages, there is a need for further improvements to Bluetooth and BLE technology. For example, traditional Bluetooth and BLE have limited range, have limited data capacity throughput, and are susceptible to interference from other devices communicating in the same frequency band (such as Wi-Fi communications). Summary of the Invention

[0007] The following is a brief summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects and is neither intended to identify key or critical elements of all aspects nor to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0008] Some aspects described herein relate to a method for wireless communication performed by a central device. The method may include sending a first communication to initiate a first communication event. The method may include sending a first synchronization message during a first time resource associated with the first communication event, the first time resource being associated with a first peripheral device. The method may include sending a second synchronization message during a second time resource associated with the first communication event, the second time resource being associated with a second peripheral device. The method may include sending a second communication to initiate a second communication event. The method may include monitoring a first response from the first peripheral device during a third time resource associated with the first time resource, the third time resource being associated with the second communication event. The method may include monitoring a second response from the second peripheral device during a fourth time resource associated with the second time resource, the fourth time resource being associated with the second communication event.

[0009] Some aspects described herein relate to a central device for wireless communication. The central device may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a first communication to initiate a first communication event. The one or more processors may be configured to send a first synchronization message during a first time resource associated with the first communication event, the first time resource being associated with a first peripheral device. The one or more processors may be configured to send a second synchronization message during a second time resource associated with the first communication event, the second time resource being associated with a second peripheral device. The one or more processors may be configured to send a second communication to initiate a second communication event. The one or more processors may be configured to monitor a first response from the first peripheral device during a third time resource associated with the first time resource, the third time resource being associated with the second communication event. The one or more processors may be configured to monitor a second response from the second peripheral device during a fourth time resource associated with the second time resource, the fourth time resource being associated with the second communication event.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a central device. When executed by one or more processors of the central device, the instruction set may cause the central device to send a first communication to initiate a first communication event. When executed by the one or more processors of the central device, the instruction set may cause the central device to send a first synchronization message during a first time resource associated with the first communication event, the first time resource being associated with a first peripheral device. When executed by the one or more processors of the central device, the instruction set may cause the central device to send a second synchronization message during a second time resource associated with the first communication event, the second time resource being associated with a second peripheral device. When executed by the one or more processors of the central device, the instruction set may cause the central device to send a second communication to initiate a second communication event. When executed by the one or more processors of the central device, the instruction set may cause the central device to monitor for a first response from the first peripheral device during a third time resource associated with the first time resource, the third time resource being associated with the second communication event. When executed by the one or more processors of the central device, the instruction set may cause the central device to monitor for a second response from the second peripheral device during a fourth time resource associated with the second time resource, the fourth time resource being associated with the second communication event.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for sending a first communication to initiate a first communication event. The apparatus may include components for sending a first synchronization message during a first time resource associated with the first communication event, the first time resource being associated with a first peripheral device. The apparatus may include components for sending a second synchronization message during a second time resource associated with the first communication event, the second time resource being associated with a second peripheral device. The apparatus may include components for sending a second communication to initiate a second communication event. The apparatus may include components for monitoring a first response from the first peripheral device during a third time resource associated with the first time resource, the third time resource being associated with the second communication event. The apparatus may include components for monitoring a second response from the second peripheral device during a fourth time resource associated with the second time resource, the fourth time resource being associated with the second communication event.

[0012] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, wireless communication devices, and / or processing systems as substantially described herein with reference to and as illustrated by the accompanying figures, appendices, and / or specification.

[0013] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the detailed description below may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be readily used as a basis for modifying or designing other structures for carrying out the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0014] Although various aspects are described in this disclosure by illustrating some examples, it will be understood by those skilled in the art that these aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip embodiments or other devices based on non-module components (e.g., vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The devices in combination with the described aspects and features may include additional components and features for the embodiments and practices of the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order that the above-described features of the present disclosure may be understood in detail, a more particular description, briefly summarized above, may be obtained by reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered limiting of its scope, as the description may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0016] Figure 1 is a diagram illustrating an example of a wireless personal area network (WPAN) according to the present disclosure.

[0017] Figure 2 is a diagram illustrating an example of a wireless communication device according to the present disclosure.

[0018] Figure 3 is a diagram illustrating an example of a protocol stack according to the present disclosure.

[0019] Figure 4 is a diagram illustrating an example transmission of data packets from a wireless communication device to a peripheral device in accordance with the present disclosure.

[0020] Figure 5 is a diagram illustrating an example of a wireless communication device according to the present disclosure.

[0021] Figure 6 is a diagram illustrating an example of a wireless communication device in a WPAN connection according to the present disclosure.

[0022] Figure 7 is a diagram illustrating an example of communication via a WPAN connection according to the present disclosure.

[0023] Figure 8-9 is a diagram illustrating an example associated with event-based initiation of more data mode for a WPAN LE connection according to the present disclosure.

[0024] Figure 10 is a diagram illustrating an example process associated with event-based initiation of more data mode for a WPAN LE connection in accordance with the present disclosure.

[0025] Figure 11 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0026] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. For the purpose of providing a thorough understanding of the various concepts, the detailed description includes specific details. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0027] Several aspects of telecommunications systems will now be presented with reference to various apparatuses and methods. These apparatuses and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0028] As an example, an element or any part of an element or any combination of elements can be implemented as a "processing system" including one or more processors. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gating logic, a discrete hardware circuit, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc.

[0029] Accordingly, in one or more example embodiments, the functions described can be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can be stored on a computer-readable medium or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of the aforementioned types of computer-readable media, or any other medium that can be used to store instructions or data structures that can be accessed by a computer.

[0030] Figure 1 1 is a diagram illustrating an example of a wireless personal area network (WPAN) 100 according to some embodiments. Within the WPAN 100, a central device 102 can connect to one or more peripheral devices 104, 106, 108, 110, 112, 114 using the BLE protocol or a modified BLE protocol and establish a BLE communication link 116 therewith. The BLE protocol is part of the BT core specification and implements radio frequency communications operating in the globally accepted 2.4 GHz Industrial, Scientific, and Medical (ISM) band.

[0031] The central device 102 may include suitable logic, circuitry, interfaces, processors, and / or code that may be operable to communicate with one or more peripheral devices 104, 106, 108, 110, 112, or 114 using the BLE protocol or a modified BLE protocol as described herein. The central device 102 may operate as an initiator to request establishment of a link layer (LL) connection with an intended peripheral device 104, 106, 108, 110, 112, or 114. A link manager may be operable to control operations between a WPAN application controller in the central device 102 and a WPAN application controller in each of the intended peripheral devices 104, 106, 108, 110, 112, and / or 114.

[0032] After establishing the requested link layer connection, the central device 102 can become the host device, and the selected or intended peripheral device 104, 106, 108, 110, 112, or 114 can become paired with the central device 102 via the established link layer connection. As a host device, the central device 102 can be capable of supporting multiple link layer connections with various peripheral devices 104, 106, 108, 110, 112, or 114 operating as client devices at one time. Specifically, the central device 102 can manage various aspects of data packet communication in the link layer connection with one or more of the associated peripheral devices 104, 106, 108, 110, 112, or 114. For example, the central device 102 can determine the operation schedule in the link layer connection with one or more peripheral devices 104, 106, 108, 110, 112, or 114. The central device 102 can also initiate a link layer protocol data unit (PDU) exchange sequence over the link layer connection. The link layer connection can be configured to run periodic connection events in a dedicated data channel. The exchange of link layer data PDU transmissions between the central device 102 and one or more of the peripheral devices 104, 106, 108, 110, 112, or 114 can occur within a connection event.

[0033] In some implementations, the central device 102 can be configured to send the first link layer data PDU in each connection event to the intended peripheral device 104, 106, 108, 110, 112, or 114. In other implementations, the central device 102 can utilize a polling scheme to poll the intended peripheral device 104, 106, 108, 110, 112, or 114 for link layer data PDU transmission during a connection event. The intended peripheral device 104, 106, 108, 110, 112, or 114 can send the link layer data PDU upon receiving the packetized link layer data PDU from the central device 102. In some other implementations, the peripheral device 104, 106, 108, 110, 112, or 114 can send the link layer data PDU to the central device 102 without first receiving the link layer data PDU from the central device 102.

[0034] Examples of central device 102 may include a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a mobile station (STA), a laptop, a personal computer (PC), a desktop computer, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet, a smart device, a wearable device (such as a smartwatch, wireless headphones, etc.), a vehicle, an electric meter, a gas pump, a toaster, a thermostat, a hearing aid, a smartphone, an on-body blood glucose unit, an Internet of Things (IoT) device, or any other similarly functional device.

[0035] Examples of one or more peripheral devices 104, 106, 108, 110, 112, or 114 may include a cellular phone, a smartphone, a SIP phone, a STA, a laptop, a PC, a desktop computer, a PDA, a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet, a smart device, a wearable device (such as a smart watch, wireless headphones, etc.), a vehicle, an electric meter, a gas pump, a toaster, a thermostat, a hearing aid, a wearable blood glucose unit, an IoT device, or any other similarly functional device. Although the central device 102 is shown as communicating with six peripheral devices 104, 106, 108, 110, 112, or 114 in the WPAN 100, the central device 102 can communicate with more or fewer than six peripheral devices within the WPAN 100 without departing from the scope of the present disclosure.

[0036] Devices implementing the BT protocol, such as the central device 102, may operate according to one radio mode, such as Basic Rate (BR) / Enhanced Data Rate (EDR), and devices implementing the BLE protocol may operate according to a BLE radio mode. In some aspects, the central device 102 may be configured with dual radio modes and thus be capable of operating according to either a BR / EDR mode or a BLE mode (e.g., based on the type of short-range wireless communication in which the device may engage).

[0037] For example, the central device 102 can operate according to the BR / EDR mode for continuous streaming of data, for broadcast networks, for mesh networks, and / or for some other applications where relatively higher data rates may be more appropriate. However, the device can operate according to the BLE mode for short burst data transmission, such as for some other applications where power conservation may be desirable and / or relatively lower data rates may be acceptable. In other aspects, the central device 102 can operate according to one or more other radio modes, including proprietary radio modes. Examples of other radio modes may include a high-speed radio mode, a low-energy radio mode, a synchronous radio mode, and the like.

[0038] As mentioned above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0039] Figure 2 is a diagram illustrating an example of a wireless communication device 200 according to the present disclosure. In some instances, the wireless communication device 200 may be Figure 1 In other examples, the wireless communication device 200 may be Figure 1 106, 108, 110, 112, or 114. In some aspects, the wireless communication device 200 can be a Bluetooth enabled device (such as a BLE device).

[0040] As shown, the wireless communication device 200 may include a processing element, such as a processor 202, which may execute program instructions for the wireless communication device 200. The wireless communication device 200 may also include a display 242, which may perform graphics processing and present information to a user. The one or more processors 202 may also be coupled to a memory management unit (MMU) 240, which may be configured to receive addresses from the one or more processors 202 and convert the addresses to address locations in a memory (such as memory 206, ROM 208, or flash memory 210) and / or address locations in other circuits or devices (such as display circuitry 204, radio 230, connector interface 220, and / or display 242). The MMU 240 may also be configured to perform memory protection and page table translation or setup. In some aspects, the MMU 240 may be included as part of the processor 202.

[0041] The processor 202 can be coupled to other circuits of the wireless communication device 200. For example, the wireless communication device 200 can include various types of memory, a connector interface 220 through which the wireless communication device 200 can communicate with a computer system, and a wireless communication subsystem that can send and receive data to and from other devices based on one or more wireless communication standards or protocols. For example, in some aspects, the wireless communication subsystem may include (but is not limited to) a wireless local area network (WLAN) subsystem, a Bluetooth subsystem, or a cellular subsystem (such as a long-term evolution (LTE) or fifth-generation (5G) new radio (NR) subsystem). The wireless communication device 200 may include multiple antennas 235a, 235b, 235c, or 235d for performing wireless communications with wireless communication devices in, for example, a WPAN.

[0042] The wireless communication device 200 can be configured to implement part or all of the techniques described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) and / or through hardware or firmware operations. In other embodiments, the techniques described herein can be implemented at least in part by programmable hardware elements (such as FPGAs and / or application-specific integrated circuits (ASICs)).

[0043] In some aspects, the radio 230 may include a separate controller configured to control communications for various corresponding radio access technology (RAT) protocols. Figure 2As shown, the radio 230 may include a WLAN controller 250 for managing WLAN communications, a Bluetooth controller 252 for managing Bluetooth and BLE communications, and a wireless wide area network (WWAN) controller 256 for managing WWAN communications. In certain aspects, the wireless communication device 200 may store and execute a WLAN software driver for controlling WLAN operations performed by the WLAN controller 250, a Bluetooth software driver for controlling Bluetooth operations performed by the Bluetooth controller 252, and / or a WWAN software driver for controlling WWAN operations performed by the WWAN controller 256.

[0044] In some implementations, a first coexistence interface 254 (such as a wired interface) can be used to transmit information between the WLAN controller 250 and the Bluetooth controller 252. In some other implementations, a second coexistence interface 258 can be used to transmit information between the WLAN controller 250 and the WWAN controller 256. In some other implementations, a third coexistence interface 260 can be used to transmit information between the Bluetooth controller 252 and the WWAN controller 256.

[0045] In some aspects, one or more of the WLAN controller 250, the Bluetooth controller 252, and / or the WWAN controller 256 may be implemented as hardware, software, firmware, or some combination thereof.

[0046] In some configurations, WLAN controller 250 can be configured to use the WLAN link using all antennas 235a, 235b, 235c and 235d to communicate with the second equipment in the WPAN. In some other configurations, Bluetooth controller 252 can be configured to use one or more antennas in antenna 235a, 235b, 235c and 235d to communicate with at least one second equipment in the WPAN. In some other configurations, WWAN controller 256 can be configured to use all antennas 235a, 235b, 235c and 235d to communicate with the second equipment in the WPAN. WLAN controller 250, Bluetooth controller 252 and / or WWAN controller 256 can be configured to adjust the wake-up time interval and the off time of equipment.

[0047] A short-range wireless communication protocol (such as BT, BLE and / or BR / EDR) may include and / or may use one or more other communication protocols, for example, for establishing and maintaining a communication link. Figure 1 , the wireless communication device 200 can establish a communication link 116 with one or more peripheral devices (such as the wireless headset 112) according to at least one communication protocol for short-range wireless communication.

[0048] The communication link 116 may include a communication link that complies with a protocol included in and / or used with BT, BLE, BR / EDR, etc. In one aspect, the communication link 116 may include an asynchronous connectionless (ACL) link. When operating as an ACL link, the communication link 116 may allow the central device 102 (e.g., a source device) to connect or "pair" with a peripheral device (such as the headset 112). The connection is asynchronous because the two devices may not need to synchronize data communications with each other in time to allow communication of data packets via the communication link 116.

[0049] The Logical Link Control and Adaptation Protocol (L2CAP) can be used within the BT protocol stack (for simplicity, Figure 2 (not shown). The L2CAP connection may be established after the ACL link has been established. References to L2CAP in this disclosure may further apply to Enhanced L2CAP (EL2CAP), which may be an enhanced version of the L2CAP protocol that enables multiplexing of multiple logical data channels over a single radio connection.

[0050] In one aspect, the communication link 116 may include an Advanced Audio Distribution Profile (A2DP) link. The A2DP link provides a point-to-point link between a source device (such as the central device 102) and a sync device (such as the headset 112). Using the A2DP link, data packets including audio can be sent on an ACL data channel, and other information, such as for controlling the audio flow, can be sent on a separate control channel. The data packets can occur non-periodically.

[0051] In another aspect, the communication link 116 can support a synchronous logical transport mechanism between a source device (e.g., central device 102) and a peripheral device (e.g., headset 112). For example, the communication link 116 can include a synchronous connection-oriented (SCO) link that provides a symmetrical point-to-point link between the source device and the peripheral device using time slots reserved for BT communications. In some aspects, the SCO link may not support retransmission of data packets, which may be unsatisfactory in audio streaming and / or voice use cases where dropped audio or voice packets may degrade the quality of user experience.

[0052] In another aspect, the communication link 116 may include an extended SCO (eSCO) link. The eSCO link may provide a symmetrical or asymmetrical point-to-point link between the source device and the peripheral device using time slots reserved for BT communications, and may also provide a retransmission window after the reserved time slots. Because the retransmission window may be used to facilitate retransmissions, the eSCO link may be suitable for audio streaming and / or voice use cases because dropped audio or voice packets may be retransmitted, thereby increasing the probability of successfully receiving data packets.

[0053] In one aspect, communication link 116 may comprise an isochronous (ISO) link. When operating as an ISO link, communication link 116 may combine some features of both synchronous and asynchronous links. For example, a stream on an ISO link may begin with a start packet and then transmit packets asynchronously. On an ISO link, the number of retransmission attempts by a transmitting device may be limited. Therefore, if a receiving device cannot decode a data packet within a limited number of retransmission attempts, the data packet may be discarded, and the receiving device may continue to receive the stream without the data from the discarded data packet.

[0054] As described in greater detail elsewhere herein, the Bluetooth controller 252 (or WPAN controller) and / or the WWAN controller 256 may establish a WPAN low energy (LE) connection with a receiving device, the WPAN LE connection being associated with a first number of transmission opportunities per transmission interval; identify an event associated with one or more of: a number of communications meeting a quantity threshold, or one or more communications having a latency requirement meeting a latency threshold; and transmit, based at least in part on identifying the event, to the receiving device an indication to communicate using a multiple data (MD) mode, the MD mode being associated with a second number of transmission opportunities per transmission interval, the second number being greater than the first number. Additionally or alternatively, the Bluetooth controller 252 may perform one or more other operations described herein.

[0055] In some aspects, the central device includes: means for sending a first communication to initiate a first communication event; means for sending a first synchronization message during a first time resource associated with the first communication event, the first time resource being associated with the first peripheral device; means for sending a second synchronization message during a second time resource associated with the first communication event, the second time resource being associated with the second peripheral device; means for sending a second communication to initiate a second communication event; means for monitoring a first response from the first peripheral device during a third time resource associated with the first time resource, the third time resource being associated with the second communication event; and / or means for monitoring a second response from the second peripheral device during a fourth time resource associated with the second time resource, the fourth time resource being associated with the second communication event. In some aspects, means for the central device to perform the operations described herein may include, for example, one or more of the following: the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0056] In some aspects, means for the wireless communication device to perform the operations described herein may include one or more of, for example, the Bluetooth controller 252 , the WWAN controller 256 .

[0057] As mentioned above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0058] Figure 3 3 is a diagram illustrating an example 300 of a protocol stack (eg, a WPAN and / or Bluetooth protocol stack) according to the present disclosure. The protocol stack 300 may be implemented in a wireless communication device (eg, Figure 1 102 or one or more peripheral devices among the peripheral devices 104, 106, 108, 110 or 112). For example, the BT protocol stack 300 may be implemented by Figure 2 The BT protocol stack 300 is implemented by one or more of the processor 202, memory 206, flash memory 210, ROM 208, radio 230, and / or Bluetooth controller 252. The BT protocol stack 300 may be organized into three layers, including an application layer 310, a host layer 320, and a control layer 330.

[0059] The application layer 310 may be a user application that interfaces with other blocks and / or layers of the BT protocol stack 300. In some aspects, the application layer 310 may include one or more applications 312 and one or more Bluetooth profiles 314 that allow applications to communicate using Bluetooth and BLE. The host layer 320 may include upper layers of the BT protocol stack 300 and may communicate with controllers in wireless communication devices such as the host controller interface (HCI) 340. Figure 2 In some aspects, the host layer 320 may include a host stack 321 that may be used for application layer interface management to allow applications to access Bluetooth communications.

[0060] The control layer 330 may include the lower layers of the BT protocol stack 300. The control layer 330, which may be used for hardware interface management, link establishment, and link management, is shown as including a link manager (LM) 332, a link layer 334, and a physical (PHY) layer 336. The PHY layer 336 may include, for example, a radio and / or baseband processor. In some aspects, the PHY layer 336 may define a mechanism for sending a bit stream over a physical link or channel connecting a BT device. The bit stream may be grouped into codewords or symbols and converted into data packets transmitted over a wireless transmission medium. The PHY layer 336 may provide an electrical, mechanical, and / or process interface to the wireless transmission medium. The PHY layer 336 may be responsible for modulating and demodulating data into radio frequency (RF) signals for transmission over the air. The PHY layer 336 may describe the physical characteristics of the receiver / transmitter of the wireless communication device. The physical characteristics may include modulation characteristics, radio frequency tolerance, sensitivity level, etc.

[0061] The Link Layer 334 is responsible for low-level communications above the PHY Layer 336. The Link Layer 334 manages the sequence and timing for sending and receiving data packets and communicates connection parameters and data flow control with other devices using the Link Layer (LL) protocol. The Link Layer 334 also provides gatekeeping to limit exposure and data exchange with other devices. If filtering is configured, the Link Layer 334 maintains a list of permitted devices and ignores all requests for data exchange from devices not on the list. The Link Layer 334 can also reduce power consumption. In some aspects, the Link Layer 334 may include a company's proprietary LL, which can be used to discover peer devices and establish secure communication channels with them. In some aspects, the Link Layer 334 may be responsible for transmitting data packets between devices in the WPAN. Each data packet may include an access address that specifies the type of logical transport used to carry the data packet. Logical transports can exist between master and slave devices. In addition, some logical transports can carry multiple logical links.

[0062] The link manager 332 may be responsible for establishing and configuring links and managing power change requests, among other tasks. Each type of logical link (such as an ACL link, an A2DP link, a SCO link, an eSCO link, an ISO link, etc.) may be associated with a specific packet type. For example, a SCO link may provide reserved channel bandwidth for communication between a master device and a slave device, and support regular, periodic exchange of data packets without retransmissions. An eSCO link may provide reserved channel bandwidth for communication between a source device and a peripheral device, and support regular, periodic exchange of data packets with retransmissions. Starting from the establishment of a connection between a source device and a peripheral device, an ACL link may exist between the source device and the peripheral device, and the data packets of the ACL link may include coding information in addition to the payload.

[0063] The link manager 332 can communicate with the host layer 320 using the HCI 340. In some instances, the link manager 332 can convert the HCI 340 commands into controller-level operations, such as baseband-level operations. The HCI 340 can act as a boundary between lower layers (such as between the control layer 330, the host layer 320, and the application layer 310). The BT specification can define a standard HCI to support BT systems implemented across two separate processors. For example, a BT system on a computer can use the BT system's own processor to implement the lower layers of the BT protocol stack 300, such as the PHY layer 336, the link layer 334, and / or the link manager 332. In some aspects, the BT system can use the processor of the BT component to implement other layers of the BT protocol stack 300, such as the host layer 320 and the application layer 310.

[0064] The host layer 320 is shown as including a Generic Access Profile (GAP) 322, a Generic Attribute Protocol (GATT) 324, a Security Manager (SM) 326, an Attribute Protocol (ATT) 328, and an L2CAP layer 329. The GAP 322 can provide an interface for applications 312 to initiate, establish, and manage connections with other BT or BLE devices. The GATT 324 can use the attribute protocol to provide a service framework for discovering services and for reading and writing characteristic values on peer devices. The GATT 324 can interface with the application 312, for example, through a profile that can define a set of attributes and any permissions required to use the attributes in BT or BLE communications.

[0065] The security manager 326 may be responsible for device pairing and key distribution. The security manager protocol implemented by the security manager 326 may define how to communicate with the security manager of the corresponding BLE device. The security manager 326 provides additional cryptographic functionality that can be used by other components of the BT protocol stack 300. The architecture of the security manager 326 used in Bluetooth communications is designed to minimize resource requirements on peripheral devices by offloading work to a hypothetical more powerful central device. BLE uses a pairing mechanism for key distribution. The security manager 326 provides a mechanism for not only encrypting data but also providing data authentication.

[0066] ATT 328 comprises a client / server protocol based on attributes associated with BLE devices configured for specific purposes. Examples may include monitoring heart rate, temperature, broadcasting advertisements, etc. Attributes can be discovered, read, and written by peer devices. The set of operations performed on ATT 328 may include, but are not limited to, error handling, server configuration, looking up information, read operations, write operations, queued writes, etc. ATT 328 can form the basis for data exchange between BT and BLE devices.

[0067] The L2CAP layer 329 can be implemented on top of the HCI 340 and can communicate with the control layer 330 through the HCI 340. The L2CAP layer 329 can be primarily responsible for establishing connections across one or more existing logical links and requesting additional links if no additional links exist. The L2CAP layer 329 can also implement multiplexing between different higher layer protocols, for example, to allow different applications to use a single link, such as a logical link, including an ACL link. In some implementations, the L2CAP layer 329 can encapsulate multiple protocols from the upper layer into a data packet format (and vice versa). The L2CAP layer 329 can also split packets with large data payloads from the upper layer into multiple packets, where the data payload is split into smaller data payloads that fit the maximum payload size (e.g., 27 bytes) on the sending side.

[0068] In some standards and protocols (such as BLE and / or BR / EDR), the central device 102 can detect errors in packets and / or dropped / lost / not received packets by using cyclic redundancy check (CRC) verification and by using message integrity code (MIC) verification. MIC verification can be used when the packet is encrypted. For example, failure of CRC verification can indicate one or more errors in the received packet, and failure of MIC verification can indicate that another packet has not been received (although failure of CRC verification can also indicate that another packet has not been received and / or failure of MIC verification can also indicate one or more errors in the received packet).

[0069] CRC verification and MIC verification can be based on generating a CRC value and a MIC, respectively, based on a received packet and comparing those generated CRC values and MICs with the CRC and MICs, respectively, included in the received packet. Specifically, a receiving device (such as headset 112) receiving a packet can first generate a CRC value or CRC checksum based on the received packet (such as based on the payload and, if applicable, the MIC included in the received packet). The receiving device can compare the generated CRC value with the CRC value included in the received packet. If the generated CRC value matches the CRC value included in the received packet, the CRC of the received packet can be verified. The CRC-verified received packet can then be decrypted. However, if the generated CRC value does not match the CRC value included in the received packet, the receiving device can determine that the CRC verification of the received packet failed. If the receiving device determines that the received packet failed CRC verification, the received packet may contain errors and / or may be damaged. In one configuration, the receiving device can discard the received packet that failed CRC verification; however, in another configuration, the receiving device can attempt to recover the received packet, for example, using one or more error correction techniques.

[0070] If the received packet is encrypted and passes the CRC verification, the receiving device can decrypt the received packet to obtain the decrypted payload and the decrypted MIC. For MIC verification, the receiving device can generate a MIC based on the decrypted payload and compare the generated MIC with the MIC obtained from the decrypted received packet. If the generated MIC matches the decrypted MIC, the receiving device can determine that the received packet was successfully decrypted. When the received packet is successfully decrypted, the decoded and decrypted payload of the received packet can be provided to another layer of the receiving device, such as a codec of the receiving device, which can cause the receiving device to output the payload data of the received packet, for example, as audio through a speaker of the headset 112.

[0071] If the generated MIC does not match the decrypted MIC of the received packet, the receiving device may determine that the received packet was not successfully decrypted. When the received packet was not successfully decrypted, a different packet may have been missed, or the received packet may be erroneous or otherwise corrupted. In one configuration, the receiving device may discard the received packet that failed MIC verification; however, in another configuration, the receiving device may attempt to recover the received packet.

[0072] As mentioned above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0073] Figure 4 An example transmission 400 of data packets from a wireless communication device 410 to a peripheral device 420 over a communication link 430 is depicted in accordance with the present disclosure. In some implementations, the wireless communication device 410 may be Figure 1 Central device 102 or Figure 2 An example of a wireless communication device 200, and the peripheral device 420 may be Figure 1 4. In some embodiments, peripheral device 420 may be an example of one or more of peripheral devices 104, 106, 108, 110, 112, or 114. In some cases, peripheral device 420 may be a pair of earbuds. Communication link 430 may be any suitable Bluetooth connection or link. In some instances, communication link 430 may be one or more of an ACL link, an L2CAP link, an A2DP link, a SCO link, or an ISO link.

[0074] The wireless communication device 410 is shown as including an encoder 412 and a transmit buffer 414. The encoder 412 can be configured to encode data such as audio or video data using a specified bit rate. The transmit buffer 414 can be configured to queue data packets to be sent to the peripheral device 420 via the communication link 430. In some implementations, for example, based on the type of the communication link 430 and / or the channel conditions associated with the communication link 430, the data packets to be sent on the communication link 430 can have a predefined size. In some aspects, the data encoded by the encoder 412 can be packetized into data packets of a predefined size. The wireless communication device 410 can dequeue the data packets from the transmit buffer 414 and send the data packets to the peripheral device 420 via the communication link 430.

[0075] The peripheral device 420 is shown as including a receive buffer 422 and a decoder 424. Data packets received via the communication link 430 may be queued or otherwise stored in the receive buffer 422. The data packets may be output from the receive buffer 422 and forwarded to the decoder 424. In some aspects, the decoder 424 may decode data (such as audio and / or video data) carried in the payload of the queued data packets and forward the decoded data to upper layers of the protocol stack for processing and playback to a user. In some implementations, the encoder 412 may encode a first encoder / decoder (codec) frame using a first bit rate and forward the first codec frame to the transmit buffer 414 for packetization for transmission to the peripheral device 420 via the communication link 430. The peripheral device 420 may queue the received data packets in the receive buffer 422 and may forward a first portion of the first codec frame to the decoder 424 for decoding.

[0076] As mentioned above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0077] Figure 5 FIG2 shows a block diagram of another example wireless communication device 500 according to the present disclosure. In some implementations, the wireless communication device 500 may be Figure 1 Central device 102, Figure 2 The wireless communication device 200 or Figure 4 An example of a wireless communication device 410. Figure 5 In the example of the wireless communication device 500, a Figure 4 The communication link 430 (eg, a Bluetooth communication connection) is established with the peripheral device 420 .

[0078] The wireless communication device 500 may include an application processing subsystem 510, an audio subsystem 520, a Bluetooth subsystem 530, and an HCI 550. Figure 3 The application processing subsystem 510 of at least some parts of the application layer 310 and host layer 320 of the BT protocol stack 300 is shown to include a media player 511, an application layer 512, a Bluetooth stack 513 and an audio interface 514. The media player 511 can be a suitable device or component capable of generating or receiving multimedia content, including, for example, real-time audio streaming, real-time video streaming, real-time game streaming and other delay-sensitive services. The application layer 512 (which can be Figure 3 In one embodiment of the application layer 310 of the present invention, the application layer 512 includes at least one Bluetooth profile that defines a set of properties and associated permissions to be used in Bluetooth or BLE communications. In some aspects, the application layer 512 may include processing resources including (but not limited to) Figure 2 The Bluetooth stack 513 may be Figure 3 An embodiment of the BT protocol stack 300.

[0079] The Bluetooth transmit driver 516 may include a split audio and packetization module (not shown for simplicity) that can packetize data (such as audio and / or video data) into Bluetooth frames that can be transmitted to the peripheral device 420 using the Bluetooth or BLE protocol.

[0080] The Bluetooth transmit driver 516 is connected to the audio subsystem 520 via an audio and control link 560. In some examples, the audio and control link 560 can be used to send encoded audio / video data and control signals between the Bluetooth transmit driver 516 and the audio / video DSP within the audio subsystem 520.

[0081] The Bluetooth transmit driver 516 is connected to a Universal Asynchronous Receiver-Transmitter (UART) controller 518 , which provides control over the transmission of information via the Bluetooth connection.

[0082] The audio subsystem 520 may include an encoder / decoder 522, one or more DSPs 524, and one or more codecs 526. The encoder / decoder 522 may be used to sample audio / video data extracted from one or more packets received from another wireless communication device. The extracted audio / video data may be processed in the application processing subsystem 510 based at least in part on the Bluetooth profile. In some embodiments, the encoder / decoder 522 may divide the sampled audio / video data into payloads, which may be embedded in one or more Bluetooth packets for transmission to the peripheral device 420 via a Bluetooth or BLE connection. In some instances, the DSP 524 and / or the codec 526 may employ one or more encoding or decoding algorithms in conjunction with sampling the audio data.

[0083] The Bluetooth subsystem 530 may include a baseband circuit (CKT) 532 (e.g., a Bluetooth baseband circuit), Bluetooth firmware 534, an Advanced Audio Distribution Profile (A2DP) circuit 536, and a PHY 538. The baseband circuit 532 and the Bluetooth firmware 534 may be used to generate baseband signals for constructing and deconstructing data frames based on the Bluetooth or BLE protocol. The baseband circuit 532 and the Bluetooth firmware 534 may also be used to generate a carrier signal for up-converting baseband signals during data transmission and for down-converting received data signals to baseband. The A2DP circuit 536 may be used to control or manage the A2DP link between the wireless communication device 500 and the peripheral device 420. Specifically, when the Bluetooth subsystem 530 is in receive mode, the PHY 538 may be used to receive, demodulate, and down-convert data packets received via the communication link 430, and forward the data packets to the application processing subsystem 510. When the Bluetooth subsystem 530 is in transmit mode, the PHY 538 may be used to encapsulate data provided from upper layers into one or more Bluetooth frames or packets for transmission to the peripheral device 420 over the communication link 430 .

[0084] As mentioned above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0085] Figure 66 is a diagram illustrating an example 600 of communication via an extended reality (XR) WPAN connection in accordance with the present disclosure. In some examples, the XR WPAN connection can include a BLE connection and / or a modified BLE connection. For example, the XR WPAN connection can be configured to support multiple peripheral devices 604 and 606 associated with a single application at a central device 602. The multiple peripheral devices 604 and 606 can provide movement data (e.g., tactile data) and / or input data (e.g., input received at one or more buttons or joysticks of the multiple peripheral devices 604 or 606). The XR WPAN connection can be configured to modify a display associated with the central device 602 based at least in part on the movement data and / or input data.

[0086] like Figure 6 As shown in FIG, central device 602 and peripheral device 604 can communicate via low-latency link 608. Central device 602 and peripheral device 606 can communicate via low-latency link 610. In some examples, peripheral device 604 and peripheral device 606 can communicate via synchronization link 612.

[0087] In some networks, links 608 - 612 may have strict latency parameters to maintain a user experience in the XR environment. For example, poor latency may result in user dizziness, unrealistic interactions in the XR environment, and / or communication errors based at least in part on out-of-sync data from multiple peripheral devices 604 and 606 .

[0088] As mentioned above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0089] Figure 7 is a diagram illustrating an example 700 of communication via an XR WPAN connection in accordance with the present disclosure. In some examples, the XR WPAN connection may include a BLE connection and / or a modified BLE connection. For example, the XR WPAN connection may be configured to support multiple peripheral devices associated with a single application at a central device. The multiple peripheral devices may provide movement data (e.g., tactile data) and / or input data (e.g., input received at one or more buttons or joysticks of the multiple peripheral devices). The XR WPAN connection may be configured to modify a display associated with the central device based at least in part on the movement data and / or input data.

[0090] In some networks, an XR WPAN connection may be associated with one or more constraints. For example, an XR WPAN connection may communicate at 1000 μs intervals. Additionally or alternatively, a peripheral device (e.g., an XR controller) may communicate with, for example, at least 29 octets per interval. In some networks, one or more constraints may be a 900 μs communication interval and at least 40 octets per interval from each peripheral device.

[0091] Figure 7 The amount of time used to exchange packets between a central device and a peripheral device within a 1000s interval is shown. The timing for central to peripheral packets can include 0 or 10 octets and peripheral to central packets of 30 octets. In addition, the timing of the interframe space (TIFS) and the timing of the minimum sub-event space (TMSS) can be set to a standard value of 150μs. The synchronization channel configuration can have a burst number (BN) = 1 (one packet per ISO interval), a refresh timeout (FT) = 1 (each packet is refreshed at the end of each interval), and a number of sub-events (NSE) = 1 (1 transmission opportunity per connected synchronization stream (CIS) per interval). Additionally or alternatively, to make the sequence feasible, the 150μs after the second peripheral packet can be used to change the frequency.

[0092] like Figure 7 As shown, a central device and a peripheral device can use a synchronous channel (e.g., with equal time intervals between communications), with each peripheral device using a separate CIS. The central device can send a central message (C_msg) 702 during a first time resource at or near the beginning of a communication interval (e.g., an event-based communication interval). The CIS can include an indication of resources allocated for subsequent communications (e.g., a polling message). The first peripheral device can send a first peripheral message (P1 Msg) 704 (e.g., as indicated by C Msg 702) during a second time resource of the communication interval. The central device can send a C_msg 706 during a third time resource, which provides an indication of resources allocated for subsequent communications. The second peripheral device can send a second peripheral message (P2 Msg) 708 (e.g., as indicated by C Msg 706) during a fourth time resource of the communication interval.

[0093] For any number of octets in the C messages, the amount of time exchanged exceeds the 1000 μs limit. For example, if P2Msg 708 ends outside the 1000 μs limit, this may be prohibited and / or may cause the central device and the peripheral device to miss an opportunity to communicate during the next 1000 μs interval. Additionally or alternatively, the central device and the peripheral device may have an end of exchange 710 at a time after P2Msg 708. This may be based at least in part on the communications being synchronous messages configured to be spaced apart (e.g., with equal intervals). Based at least in part on the timing of end of exchange 710 being the first available time for the central device to send another C1Msg after the P2Msg, based at least in part on the synchronous nature of the communications, the communication between the central device and the peripheral device may have a delay until the next communication 712. The next communication may be associated with a subsequent communication event. This may increase the latency of the communication between the central device and the peripheral device.

[0094] Other configurations may be used, such as a single C Msg that polls the P1 Msg and the P2 Msg. However, fitting the timing within the 1000 μs limit may limit the amount of traffic that can be transmitted during a communication interval.

[0095] As mentioned above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0096] In some networks, the central device and the peripheral device may use a communication interval, such as the communication interval shown in example 700. The peripheral device may attempt to synchronize with the central device to allow communication of uplink and / or downlink communications. However, the synchronization process may have similar timing issues, such as Figure 7 As shown. For example, the exchange of synchronization information may exceed the 1000 μs limit and / or may cause the communication device and the peripheral device to delay subsequent communications. Additionally or alternatively, if synchronization is delayed at least in part based on exceeding the 1000 μs limit, and synchronization is unsuccessful, communication of data may be further delayed until successful synchronization occurs. In this manner, the synchronization process may consume twice the number of communication intervals that would have been consumed if the synchronization process had met the 1000 μs limit. This 2x delay for synchronization may increase communication errors, result in increased latency, and / or disrupt the data flow between the central device and the peripheral device.

[0097] In some aspects described herein, resources of a communication interval may be configured to support communication between a central device (e.g., an XR device) and multiple peripheral devices (e.g., XR peripherals) within a communication interval (e.g., with a 1000 μs limit). For example, the central device may send a first communication to initiate a first communication event. During the first communication event, the central device may send a first synchronization message during a first time resource associated with the first peripheral device, and the central device may send a second synchronization message during a second time resource associated with the second peripheral device. After the first communication event, the central device may send a second communication to initiate a second communication event. During the second communication event, the central device may monitor for a first response from the first peripheral device during a third time resource associated with the first time resource, and monitor for a second response from the second peripheral device during a fourth time resource associated with the second time resource.

[0098] Based at least in part on receiving the first response and the second response, the central device can synchronize with the first peripheral device and the second peripheral device.

[0099] Based at least in part on the failure to receive the first response or the second response, the central device may again attempt to synchronize with the first peripheral device and the second peripheral device. For example, based at least in part on the failure to receive the first response, the central device may send a third communication to initiate a third communication event and send the first synchronization message (e.g., a retransmission of the first synchronization message associated with the first peripheral device) during a fifth time resource associated with the third communication event. The central device may also send a fourth communication to initiate a fourth communication event and monitor for a third response from the first peripheral device during a sixth time resource associated with the fifth time resource (e.g., within the fourth communication event).

[0100] In another example, the central device may receive a first response from the first peripheral device during a third time resource and may fail to receive a second response from the second peripheral device during a fourth time resource. The central device may send a third communication to initiate a third communication event based at least in part on the failure to receive the second response. During the third communication event, the central device may send a second synchronization message (e.g., a retransmission of the second synchronization message associated with the second peripheral device) during a fifth time resource associated with the third communication event. The central device may send a fourth communication to initiate a fourth communication event and monitor for a third response from the second peripheral device during a sixth time resource associated with the fifth time resource, where the sixth time resource is associated with the fourth communication event. During a second attempt to synchronize with the second peripheral device, the central device may communicate with the first peripheral device during a seventh time resource associated with the third communication event based at least in part on the receipt of the first response. Additionally or alternatively, the central device may communicate with the first peripheral device during an eighth time resource associated with the fourth communication event. In this manner, the central device may communicate (e.g., exchange data and / or control information) during a communication event that is also used to establish synchronization with the second peripheral device.

[0101] In an example process, a first peripheral device and a second peripheral device are both in an out-of-sync sub-state, and the central device is searching for both peripheral devices. The central device can alternate between events by sending synchronization packets and listening for packets from the peripheral devices. An event with a synchronization packet in two peripheral sub-events (e.g., a first resource associated with communications to or from a first peripheral device and a second resource associated with communications to or from a second peripheral device) can always be followed by an event in which the central device listens for peripheral packets in both peripheral sub-ports.

[0102] In an example where the first peripheral device is in the sync sub-state, the central device can actively receive packets from the first peripheral device and can alternate between sending sync packets in a sub-event associated with the second peripheral device (e.g., the P2 time slot) and listening for packets from the second peripheral device in the P2 time slot.

[0103] In an example where the second peripheral device is in the sync sub-state, the central device can actively receive packets from the second peripheral device and can alternate between sending sync packets in sub-events associated with the first peripheral device (e.g., P1 time slot) and listening for packets from the first peripheral device in the P1 time slot.

[0104] In examples where the first peripheral device and the second peripheral device are in the synchronization substate, the central device can actively receive packets from the first peripheral device and the second peripheral device.

[0105] In a peripheral device's scanning state, the peripheral device can attempt to synchronize on a previously configured central device synchronization packet. For example, the peripheral device can set the scan channels to all channels (e.g., 37 channels). Optionally, the peripheral device can perform a bad channel assessment to identify potential good channels to scan in order to reduce the scan channel set. The peripheral device can listen for packets within the scan channel set with the access address (AASync) of the synchronization packet at each interval (e.g., in milliseconds) of the synchronization window (TSync_Interval) for the duration (e.g., in milliseconds (ms)) of the synchronization window (TSync_Window). Each window can use a different channel within the scan channel set. Once the peripheral device detects a synchronization packet, it can decode the synchronization packet's payload (e.g., the payload of a synchronization message from the central device) to determine the timing and frequency hopping information required to synchronize with the central device to receive the next central device packet. If the peripheral device fails to receive a synchronization packet within TSync_Timeout seconds, it can again listen for packets within the scan channel set. The peripheral device can repeat this process until TSync_Giveup expires.

[0106] As mentioned above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0107] Figure 8 is a diagram of an example 800 associated with synchronization messages for peripheral devices according to the present disclosure. Figure 8 As shown in , a central device (e.g., a mobile computing device, an XR device, and / or a video device) can communicate with a first peripheral device and a second peripheral device (e.g., a first XR controller or other input device and a second XR controller or other input device). In some aspects, the central device, the first peripheral device, and the second peripheral device can be part of a wireless network (e.g., WPAN 100).

[0108] As indicated by reference numeral 805, the central device may send a first communication to initiate a first communication event, and the first peripheral device and / or the second peripheral device may receive the first communication to initiate the first communication event. In some aspects, the first communication may include resource allocation for one or more synchronization messages.

[0109] A communication event may be a collection of one or more communications that occur within a communication interval (eg, a 1000 μs interval). A communication event may be initiated with a communication from a central device (eg, C_MSG 702) and / or may be periodic.

[0110] As shown in reference numeral 810, the central device may send a first synchronization message, and the first peripheral device and / or the second peripheral device may receive the first synchronization message. For example, the central device may send the first synchronization message during a first time resource associated with a first communication event. The first time resource may be associated with the first peripheral device. For example, the first time resource may be allocated for communication between the central device and the first peripheral device. The first time resource may be a recurring time resource within a set time period of a communication interval between the first peripheral device and the central device. In some aspects, the first peripheral device and / or the second peripheral device may receive the first synchronization message.

[0111] As shown in reference numeral 815, the central device may send a second synchronization message, and the first peripheral device and / or the second peripheral device may receive the second synchronization message. For example, the central device may send the second synchronization message during a second time resource associated with the second communication event. The second time resource may be associated with the second peripheral device. For example, the second time resource may be allocated for communication between the central device and the second peripheral device. The second time resource may be a recurring time resource within a set time period of the communication interval between the second peripheral device and the central device. In some aspects, the first peripheral device and / or the second peripheral device may receive the second synchronization message.

[0112] In some aspects, the first synchronization message or the second synchronization message may include an indication of a first offset associated with a time between the start of the first synchronization message and the start of the second communication, a second offset associated with a time between the start of the second communication and a third time resource, and / or a third offset associated with a time between the start of the second communication and a fourth time resource, among other examples. For example, the first synchronization message may include information for the first peripheral device and / or the second peripheral device to obtain timing and / or frequency synchronization with the central device. Based at least in part on obtaining timing and / or frequency synchronization with the central device, the first peripheral device and / or the second peripheral device may send a reply to the central device and / or receive subsequent communications from the central device.

[0113] The transmission of the first communication, the first synchronization message, and the second synchronization message can be part of the first communication event 820 (eg, included within a communication interval associated with the first communication event 820).

[0114] As indicated at reference numeral 825 , the central device may send a first communication to initiate a first communication event, and the first peripheral device and / or the second peripheral device may receive the first communication to initiate the first communication event.

[0115] As shown in reference numeral 830, the central device may monitor for a first response from the first peripheral device. For example, the central device may monitor for the first response from the first peripheral device during a third time resource associated with the first time resource. The third time resource may be associated with a second communication event. In some aspects, the central device may receive the first response from the first peripheral device. Additionally or alternatively, the central device may receive a second response from the second peripheral device during the third time resource.

[0116] In some aspects, the third time resource can be associated with the first time resource based at least in part on being positioned during the same or overlapping time window of the communication event. For example, the first communication resource can be positioned to have an offset from a reference time of the first communication event 820 (e.g., the start or end of the first communication event or the first communication), and the third communication resource can be positioned to have the same offset from a reference time of the second communication event (e.g., the start or end of the second communication event or the second communication).

[0117] As shown in reference numeral 835, the central device may monitor for a second response from the second peripheral device. For example, the central device may monitor for a second response from the second peripheral device during a fourth time resource associated with the second time resource. The fourth time resource may be associated with a second communication event. Additionally or alternatively, the central device may receive a first response from the first peripheral device during the fourth time resource.

[0118] In some aspects, the fourth time resource can be associated with the second time resource based at least in part on being positioned during the same or overlapping time window of the communication event. For example, the second communication resource can be positioned to have an offset from a reference time of the first communication event 820 (e.g., the start or end of the first communication event or the first communication), and the fourth communication resource can be positioned to have the same offset from a reference time of the second communication event (e.g., the start or end of the second communication event or the second communication).

[0119] In some aspects, the first communication, the second communication, the first response, or the second response includes a first portion of a payload including data and a second portion of the payload including control information. In some aspects, the control information can be configured to be repeated if not acknowledged. For example, the control information can be configured to be repeated until acknowledged or until the control information expires.

[0120] In some aspects, the control information includes a sequence number associated with the control information or data, a next expected sequence number associated with the first peripheral device, and / or a next expected sequence number associated with the second peripheral device, among other examples.

[0121] In some aspects, the data may include XR data, positioning information, power state information, gyroscope data, haptic data, and / or received input data, among other examples.

[0122] In some aspects, communications and messages may be configured as isochronous communications, where intervals between subsequent messages and / or time resources associated with subsequent messages are equal.

[0123] In some aspects, the amount of time between the first time resource and the first communication can be the same amount of time as the amount of time between the third time resource and the second communication. In some aspects, the amount of time between the first time resource and the end time of the first communication event can be the same amount of time as the amount of time between the third time resource and the end time of the second communication event.

[0124] In some aspects, the amount of time between the second time resource and the first communication can be the same amount of time as the amount of time between the fourth time resource and the second communication. In some aspects, the amount of time between the second time resource and the end time of the first communication event can be the same amount of time as the amount of time between the third time resource and the end time of the second communication event.

[0125] The transmission of the first communication, the first synchronization message, and the second synchronization message can be part of the first communication event 840 (eg, included within a communication interval associated with the first communication event 840).

[0126] In some aspects, the central device may fail to receive the first response or the second response and may repeat operations 810 and 825 during a subsequent communication interval and / or may repeat operations 815 and 830 during a subsequent communication interval.

[0127] For example, based at least in part on a failure to receive the first response, the central device may send a third communication to initiate a third communication event. The central device may send the first synchronization message during a fifth time resource associated with the third communication event. The fifth time resource may be associated with the first peripheral device. The central device may send a fourth communication to initiate a fourth communication event and monitor for a third response from the first peripheral device during a sixth time resource associated with the fifth time resource. The sixth time resource may be associated with the fourth communication event.

[0128] For example, the central device may receive a first response from the first peripheral device during a third time resource and may fail to receive a second response from the second peripheral device during a fourth time resource. The central device may send a third communication to initiate a third communication event based, at least in part, on the failure to receive the second response. During the third communication event, the central device may send a second synchronization message (e.g., a retransmission of the second synchronization message associated with the second peripheral device) during a fifth time resource associated with the third communication event. The central device may send a fourth communication to initiate a fourth communication event and monitor for a third response from the second peripheral device during a sixth time resource associated with the fifth time resource, where the sixth time resource is associated with the fourth communication event. During a second attempt to synchronize with the second peripheral device, the central device may communicate with the first peripheral device during a seventh time resource associated with the third communication event based, at least in part, on the receipt of the first response. Additionally or alternatively, the central device may communicate with the first peripheral device during an eighth time resource associated with the fourth communication event. In this manner, the central device may communicate (e.g., exchange data and / or control information) during a communication event that is also used to establish synchronization with the second peripheral device.

[0129] In some aspects, the central device can receive a response from the first peripheral device or the second peripheral device and can synchronize with one of the first peripheral device or the second peripheral device. Based at least in part on synchronizing with only one of the peripheral devices, the central device can communicate (e.g., data and / or control information) with the synchronized peripheral device and can again attempt to synchronize with the unsynchronized peripheral device (e.g., both within the same communication interval).

[0130] As indicated at reference numeral 845, the central device can establish synchronization with the first peripheral device.For example, the central device can establish synchronization with the first peripheral device based at least in part on receiving a first response from the first peripheral device during the third time resource.

[0131] The central device can establish synchronization with the second peripheral device, as indicated at reference numeral 850. For example, the central device can establish synchronization with the second peripheral device based at least in part on receiving the second response from the first peripheral device during the fourth time resource.

[0132] In some aspects, based at least in part on receiving the first response and / or synchronizing with the first peripheral device, the central device may communicate with the first peripheral device in a subsequent communication interval (e.g., associated with a subsequent communication event). In some aspects, based at least in part on receiving the second response and / or synchronizing with the second peripheral device, the central device may communicate with the second peripheral device in a subsequent communication interval (e.g., associated with a subsequent communication event).

[0133] Based at least in part on the central device alternating communication intervals and / or communication events between sending synchronization messages and listening for replies within the same set of resources allocated for communication with the first peripheral device or the second peripheral device, the central device can improve the latency of synchronization between the first peripheral device, the second peripheral device, and the central device. In this manner, the central device can conserve network resources that might otherwise have been consumed to extend the synchronization process over additional time resources.

[0134] As mentioned above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 The examples described are different.

[0135] Figure 9 9 is a diagram illustrating an example of communication via an XR WPAN connection according to the present disclosure. In some examples, the XR WPAN connection may include a BLE connection and / or a modified BLE connection. For example, the XR WPAN connection may be configured to support multiple peripheral devices associated with a single application at a central device. The multiple peripheral devices may provide movement data (e.g., tactile data) and / or input data (e.g., input received at one or more buttons or joysticks of the multiple peripheral devices). The XR WPAN connection may be configured to modify a display associated with the central device based at least in part on the movement data and / or input data.

[0136] In some networks, an XR WPAN connection may be associated with one or more constraints. For example, an XR WPAN connection may communicate at 1000 μs intervals. Additionally or alternatively, a peripheral device (e.g., an XR controller) may communicate with, for example, at least 29 octets per interval. In some networks, one or more constraints may be a 900 μs communication interval and at least 40 octets per interval from each peripheral device.

[0137] Figure 9 The amount of time used to exchange packets between a central device and a peripheral device within a 1000 μs interval is shown. The timing for central to peripheral packets may include 0 or 10 octets and peripheral to central packets of 30 octets. Additionally, TIFS and TMSS may be set to a standard value of 150 μs. The synchronization channel configuration may have BN=1 (one packet per ISO interval), FT=1 (each packet is flushed at the end of each interval), and NSE=1 (1 transmission opportunity per ISO interval). Additionally or alternatively, in order for the sequence to be feasible, 150 μs may need to be available for changing frequency after the second peripheral packet.

[0138] like Figure 9As shown, the central device and the peripheral device can use an isochronous channel (e.g., with equal time intervals between communications), with each peripheral device using a separate CIS. The central device can send a C Msg 902 during a first time resource at or near the beginning of a first communication interval (e.g., an event-based communication interval). The C Msg 902 can include an indication of resources allocated for subsequent communications (e.g., a polling message). The central device can send a first peripheral synchronization message (P1 Sync Msg) 904 during a second time resource of the communication interval (e.g., as indicated by C Msg 902). The central device can send a second peripheral synchronization message (P2 Sync Msg) 906 during a third time resource of the first communication interval (e.g., as indicated by C Msg 902).

[0139] In some aspects, C Msg 902 may initiate a first communication event 908 comprising a communication interval during which one or more communications occur. For example, first communication event 908 may include C Msg 902, P1 Sync Msg 904, and P2 Sync Msg 906. First communication event 908 may be initiated using C Msg 902 sent from a central device. In some aspects, a communication event may be a periodic communication interval during which one or more communications occur and / or have time resources allocated for communication (e.g., having a periodic start time and / or end time). For example, first communication event 908 may include a first time window (e.g., a first time resource) allocated for transmitting C Msg 902, a second time window (e.g., a second time resource) allocated for transmitting P1 Sync Msg 904, and a third time window (e.g., a third time resource) allocated for transmitting P2 Sync Msg 906. The time resources may be paired with frequency resources (e.g., a frequency bandwidth) used for each transmission.

[0140] The central device may send a C Msg 910 during a first time resource at or near the beginning of a second communication interval (e.g., an event-based communication interval). C Msg 910 may include an indication of resources allocated for subsequent communication (e.g., a polling message). The central device may listen 912 for a reply (e.g., P1 Sync Msg reply 914) to P1 Sync Msg 904 during a second time resource of the second communication interval (e.g., as indicated by C Msg 910). The second time resource of the second communication interval may correspond to the second time resource of the first communication interval. The central device may listen 916 for a reply (e.g., P2 Sync Msg reply 918) to P2 Sync Msg 906 during a third time resource of the second communication interval (e.g., as indicated by C Msg 910). The third time resource of the second communication interval may correspond to the third time resource of the first communication interval.

[0141] In some aspects, the C Msg 910 may initiate a second communication event 920, which includes a communication interval during which one or more communications occur. For example, the second communication event 920 includes the C Msg 910 and, in some examples, the P1 Sync Msg reply 914 and the P2 Sync Msg reply 918. The second communication event 920 may be initiated using the CMsg 910 sent from the central device. The second communication event 920 includes a first time window (e.g., a first time resource) allocated for transmitting the C Msg 910, a second time window (e.g., a second time resource) allocated for transmitting the P1 Sync Msg reply 914, and a third time window (e.g., a third time resource) allocated for transmitting the P2 Sync Msg reply 918. The time resources may be paired with frequency resources (e.g., frequency bandwidth) used for each transmission.

[0142] The central device may send a C Msg 922 during a first time resource at or near the beginning of a third communication interval (e.g., an event-based communication interval). C Msg 922 may include an indication of resources allocated for subsequent communication (e.g., a polling message). The central device may communicate data 924 with the first peripheral device during a second time resource of the third communication interval (e.g., based at least in part on receiving P1 Sync Msg reply 914). The central device may send a second peripheral synchronization message (P2 Sync Msg) 926 during a third time resource of the third communication interval (e.g., as indicated by C Msg 902).

[0143] In some aspects, C Msg 922 may initiate a third communication event 928, which includes a communication interval during which one or more communications occur. For example, third communication event 928 includes C Msg 922, data 924, and P2 Sync Msg 926. The third communication event may be initiated using C Msg 922 sent from the central device. Third communication event 928 includes a first time window (e.g., a first time resource) allocated for transmitting C Msg 922, a second time window (e.g., a second time resource) allocated for transmitting data 924, and a third time window (e.g., a third time resource) allocated for transmitting P2 Sync Msg 926. The time resources may be paired with frequency resources (e.g., frequency bandwidth) used for each transmission.

[0144] The central device may send a C Msg 930 during a first time resource at or near the beginning of a fourth communication interval (e.g., an event-based communication interval). C Msg 910 may include an indication of resources allocated for subsequent communication (e.g., a polling message). The central device may listen 912 for a reply (e.g., P1 Sync Msg reply 914) to P1 Sync Msg 904 during a second time resource of a second communication interval (e.g., as indicated by C Msg 910). The second time resource of the second communication interval may correspond to the second time resource of the first communication interval. The central device may listen 916 for a reply (e.g., P2 Sync Msg reply 918) to P2 Sync Msg 906 during a third time resource of the second communication interval (e.g., as indicated by C Msg 910). The second time resource of the second communication interval may correspond to the second time resource of the first communication interval and / or the second communication interval.

[0145] In some aspects, C_Msg 930 may initiate a fourth communication event 938, which includes a communication interval during which one or more communications occur. For example, fourth communication event 938 includes C Msg 930, data 932, and may include P2 Sync Msg reply 936. Fourth communication event 938 may be initiated using C_MSG 930 sent from the central device. Fourth communication event 938 includes a first time window (e.g., a first time resource) allocated for transmitting C_msg 930, a second time window (e.g., a second time resource) allocated for transmitting data 932, and a third time window (e.g., a third time resource) allocated for transmitting P2 Sync Msg reply 936. The time resources may be paired with frequency resources (e.g., a frequency bandwidth) used for each transmission.

[0146] As mentioned above, Figure 9 are provided as examples. Other examples can be found in the Figure 9 The examples described are different.

[0147] Figure 10 1 is a diagram illustrating an example process 1000 performed, for example, by a central device according to the present disclosure. Example process 1000 is an example of a central device (e.g., central device 102, wireless communication device 200, and / or wireless communication device 410, among other examples) performing operations associated with synchronization messages to peripheral devices.

[0148] like Figure 10 As shown, in some aspects, process 1000 may include sending a first communication to initiate a first communication event (block 1010). For example, a central device (e.g., using Figure 11 The WPAN controller 252 and / or WWAN controller 256 and / or sending component 1104 and / or communication manager 1108 depicted in FIG may send a first communication to initiate a first communication event, as described above.

[0149] like Figure 10 As further shown in FIG. 1 , in some aspects, process 1000 may include sending a first synchronization message during a first time resource associated with a first communication event, the first time resource being associated with a first peripheral device (block 1020). For example, a central device (e.g., using Figure 11 The WPAN controller 252 and / or WWAN controller 256 and / or sending component 1104 and / or communication manager 1108 depicted in can send a first synchronization message during a first time resource associated with a first communication event, the first time resource being associated with the first peripheral device, as described above.

[0150] like Figure 10 As further shown in FIG. 1 , in some aspects, process 1000 may include sending a second synchronization message during a second time resource associated with the first communication event, the second time resource being associated with the second peripheral device (block 1030). For example, a central device (e.g., using Figure 11 The WPAN controller 252 and / or WWAN controller 256 and / or sending component 1104 and / or communication manager 1108 depicted in FIG may send a second synchronization message during a second time resource associated with the first communication event, the second time resource being associated with the second peripheral device, as described above.

[0151] like Figure 10 As further shown in FIG. 1 , in some aspects, process 1000 may include sending a second communication to initiate a second communication event (block 1040). For example, a central device (e.g., using Figure 11The WPAN controller 252 and / or WWAN controller 256 and / or sending component 1104 and / or communication manager 1108 depicted in FIG may send a second communication to initiate a second communication event, as described above.

[0152] like Figure 10 As further shown in FIG. 1 , in some aspects, process 1000 may include monitoring a first response from a first peripheral device during a third time resource associated with the first time resource, the third time resource being associated with a second communication event (block 1050). For example, a central device (e.g., using Figure 11 The WPAN controller 252 and / or WWAN controller 256 and / or receiving component 1102 and / or communication manager 1108 depicted in can monitor the first response from the first peripheral device during a third time resource associated with the first time resource, the third time resource being associated with the second communication event, as described above.

[0153] like Figure 10 As further shown in FIG. 1 , in some aspects, process 1000 may include monitoring a second response from a second peripheral device during a fourth time resource associated with the second time resource, the fourth time resource being associated with the second communication event (block 1060). For example, a central device (e.g., using Figure 11 The WPAN controller 252 and / or WWAN controller 256 and / or receiving component 1102 and / or communication manager 1108 depicted in can monitor a second response from the second peripheral device during a fourth time resource associated with the second time resource, the fourth time resource being associated with the second communication event, as described above.

[0154] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0155] In a first aspect, process 1000 includes establishing synchronization with a first peripheral device based at least in part on receiving a first response.

[0156] In a second aspect, alone or in combination with the first aspect, process 1000 includes failing to receive a first response, sending a third communication to initiate a third communication event based at least in part on failing to receive the first response, sending a first synchronization message during a fifth time resource associated with the third communication event based at least in part on failing to receive the first response, the fifth time resource being associated with the first peripheral device, sending a fourth communication to initiate a fourth communication event, and monitoring for a third response from the first peripheral device during a sixth time resource associated with the fifth time resource, the sixth time resource being associated with the fourth communication event.

[0157] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1000 includes receiving a first response from a first peripheral device during a third time resource, failing to receive a second response from a second peripheral device during a fourth time resource, sending a third communication to initiate a third communication event based at least in part on the failure to receive the second response, sending a third communication to initiate a third communication event based at least in part on the failure to receive the second response, sending a fourth communication to initiate a fourth communication event, and monitoring a third response from the second peripheral device during a sixth time resource associated with the fifth time resource, the sixth time resource being associated with the fourth communication event.

[0158] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1000 includes communicating with the first peripheral device during a seventh time resource associated with the third communication event based at least in part on receiving the first response, and communicating with the first peripheral device during an eighth time resource associated with the fourth communication event based at least in part on receiving the first response.

[0159] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, one or more of the first synchronization message or the second synchronization message includes an indication of one or more of: a first offset associated with the time between the start of the first synchronization message and the start of the second communication, a second offset associated with the time between the start of the second communication and a third time resource, or a third offset associated with the time between the start of the second communication and a fourth time resource.

[0160] In the sixth aspect, alone or in combination with one or more of the first to fifth aspects, the first communication, the second communication, the first response or the second response comprises a first portion of the payload comprising data and a second portion of the payload comprising control information, the control information being configured to be repeated if not confirmed.

[0161] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, the data is associated with one or more of augmented reality data, positioning information, power state information, data, tactile data, or received input data.

[0162] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, the control information includes one or more of a sequence number associated with the control information or data, a next expected sequence number associated with the first peripheral device, or a next expected sequence number associated with the second peripheral device.

[0163] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the amount of time between the first time resource and the first communication is the same amount of time as the amount of time between the third time resource and the second communication, or wherein the amount of time between the first time resource and the end time of the first communication event is the same amount of time as the amount of time between the third time resource and the end time of the second communication event.

[0164] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the amount of time between the second time resource and the first communication is the same amount of time as the amount of time between the fourth time resource and the second communication, or wherein the amount of time between the second time resource and the end time of the first communication event is the same amount of time as the amount of time between the third time resource and the end time of the second communication event.

[0165] although Figure 10 Example blocks of process 1000 are shown, but in some aspects, process 1000 may include Figure 10 1000. In some embodiments, the process 1000 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1000 may be executed in parallel.

[0166] Figure 11 1 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 can be a central device, or a central device can include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a transmitting component 1104, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 can communicate with another apparatus 1106 (e.g., a peripheral device, an XR controller, or another wireless communication apparatus) using receiving component 1102 and transmitting component 1104. As further shown, apparatus 1100 can include a communication manager 1108. Communication manager 1108 can include WWAN controller 256, Bluetooth controller 252, processor 202, and / or MMU 240.

[0167] In some aspects, the apparatus 1100 may be configured to perform the Figure 8-9 Additionally or alternatively, the device 1100 may be configured to perform one or more of the processes described herein, such as Figure 10 In some aspects, the apparatus 1100 and / or Figure 11 One or more components shown in FIG may include a combination of Figure 2 Additionally or alternatively, Figure 11 One or more components shown in the may be implemented in conjunction with Figure 2 In one or more components described herein. Additionally or alternatively, one or more components in the set of components may be at least partially implemented as software stored in a memory. For example, a component (or portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0168] The receiving component 1102 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1106. The receiving component 1102 may provide the received communications to one or more other components of the apparatus 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communications and may provide the processed signals to one or more other components of the apparatus 1100. In some aspects, the receiving component 1102 may include a processor coupled to a processor. Figure 2 The described central device may include one or more antennas, modems, demodulators, multiple-input multiple-output (MIMO) detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0169] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1106. In some aspects, one or more other components of the apparatus 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the apparatus 1106. In some aspects, the transmitting component 1104 may perform signal processing (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communications and may transmit the processed signals to the apparatus 1106. In some aspects, the transmitting component 1104 may include a processor coupled to a processor. Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described central device. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0170] The sending component 1104 can send a first communication to initiate a first communication event. The sending component 1104 can send a first synchronization message during a first time resource associated with the first communication event, the first time resource being associated with the first peripheral device. The sending component 1104 can send a second synchronization message during a second time resource associated with the first communication event, the second time resource being associated with the second peripheral device. The sending component 1104 can send a second communication to initiate a second communication event. The communication manager 1108 and / or the receiving component 1102 can monitor a first response from the first peripheral device during a third time resource associated with the first time resource, the third time resource being associated with the second communication event. The communication manager 1108 and / or the receiving component 1102 can monitor a second response from the second peripheral device during a fourth time resource associated with the second time resource, the fourth time resource being associated with the second communication event.

[0171] The communication manager 1108 can establish synchronization with the first peripheral device based at least in part on receiving the first response.

[0172] The communications manager 1108 and / or the receiving component 1102 may fail to receive the first response.

[0173] The sending component 1104 can send a third communication to initiate a third communication event based at least in part on the failure to receive the first response.

[0174] The sending component 1104 can send the first synchronization message during a fifth time resource associated with the third communication event based at least in part on a failure to receive the first response, the fifth time resource being associated with the first peripheral device.

[0175] The sending component 1104 can send a fourth communication to initiate a fourth communication event.

[0176] The communication manager 1108 and / or the receiving component 1102 can monitor for a third response from the first peripheral device during a sixth time resource associated with the fifth time resource, the sixth time resource associated with the fourth communication event.

[0177] The receiving component 1102 can receive a first response from the first peripheral device during a third time resource.

[0178] The communication manager 1108 and / or the receiving component 1102 may fail to receive a second response from the second peripheral device during a fourth time resource.

[0179] The sending component 1104 can send a third communication to initiate a third communication event based at least in part on a failure to receive the second response.

[0180] The sending component 1104 can send a second synchronization message during a fifth time resource associated with the third communication event based at least in part on a failure to receive the second response, the fifth time resource being associated with the second peripheral device.

[0181] The sending component 1104 can send a fourth communication to initiate a fourth communication event.

[0182] The communication manager 1108 and / or the receiving component 1102 can monitor for a third response from the second peripheral device during a sixth time resource associated with the fifth time resource, the sixth time resource associated with the fourth communication event.

[0183] The communication manager 1108 , the sending component 1104 , and / or the receiving component 1102 can communicate with the first peripheral device during a seventh time resource associated with the third communication event based at least in part on receiving the first response.

[0184] The communication manager 1108 , the sending component 1104 , and / or the receiving component 1102 can communicate with the first peripheral device during an eighth time resource associated with the fourth communication event based at least in part on receiving the first response.

[0185] Figure 11 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Figure 11 The components shown in FIG may include additional components, fewer components, different components, or differently arranged components. Figure 11 Two or more components shown in may be implemented within a single component, or Figure 11 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Figure 11 A set of (one or more) components shown in the executable is described as being Figure 11 One or more functions performed by another group of components shown in FIG.

[0186] The following provides an overview of some aspects of the disclosure:

[0187] Aspect 1: A method of wireless communication performed by a central device, comprising: sending a first communication to initiate a first communication event; sending a first synchronization message during a first time resource associated with the first communication event, the first time resource being associated with a first peripheral device; sending a second synchronization message during a second time resource associated with the first communication event, the second time resource being associated with a second peripheral device; sending a second communication to initiate a second communication event; monitoring a first response from the first peripheral device during a third time resource associated with the first time resource, the third time resource being associated with the second communication event; and monitoring a second response from the second peripheral device during a fourth time resource associated with the second time resource, the fourth time resource being associated with the second communication event.

[0188] Aspect 2: The method of aspect 1, further comprising: establishing synchronization with the first peripheral device based at least in part on receiving the first response.

[0189] Aspect 3: The method according to any one of Aspects 1-2 further includes: failing to receive a first response; sending a third communication to initiate a third communication event based at least in part on failing to receive the first response; sending the first synchronization message during a fifth time resource associated with the third communication event based at least in part on failing to receive the first response, the fifth time resource being associated with the first peripheral device; sending a fourth communication to initiate a fourth communication event; and monitoring a third response from the first peripheral device during a sixth time resource associated with the fifth time resource, the sixth time resource being associated with the fourth communication event.

[0190] Aspect 4: The method according to any one of Aspects 1-3 further includes: receiving a first response from the first peripheral device during a third time resource; failing to receive a second response from the second peripheral device during a fourth time resource; sending a third communication to initiate a third communication event based at least in part on the failure to receive the second response; sending the second synchronization message during a fifth time resource associated with the third communication event based at least in part on the failure to receive the second response, the fifth time resource being associated with the second peripheral device; sending a fourth communication to initiate a fourth communication event; and monitoring the third response from the second peripheral device during a sixth time resource associated with the fifth time resource, the sixth time resource being associated with the fourth communication event.

[0191] Aspect 5: The method according to Aspect 4 further includes: communicating with the first peripheral device during the seventh time resource associated with the third communication event based at least in part on receiving the first response; and communicating with the first peripheral device during the eighth time resource associated with the fourth communication event based at least in part on receiving the first response.

[0192] Aspect 6: A method according to any one of Aspects 1-5, wherein one or more of the first synchronization message or the second synchronization message includes an indication of one or more of: a first offset associated with the time between the start of the first synchronization message and the start of the second communication, a second offset associated with the time between the start of the second communication and a third time resource, or a third offset associated with the time between the start of the second communication and a fourth time resource.

[0193] Aspect 7: A method according to any one of Aspects 1-6, wherein the first communication, the second communication, the first response or the second response includes: a first portion of the payload including data, and a second portion of the payload including control information, the control information being configured to be repeated if not confirmed.

[0194] Aspect 8: The method of aspect 7, wherein the data is associated with one or more of: extended reality data, positioning information, power state information, gyroscope data, haptic data, or received input data.

[0195] Aspect 9: The method of any of aspects 7-8, wherein the control information comprises one or more of: a sequence number associated with the control information or data, a next expected sequence number associated with the first peripheral device, or a next expected sequence number associated with the second peripheral device.

[0196] Aspect 10: A method according to any one of Aspects 1-9, wherein the amount of time between the first time resource and the first communication is the same amount of time as the amount of time between the third time resource and the second communication, or wherein the amount of time between the first time resource and the end time of the first communication event is the same amount of time as the amount of time between the third time resource and the end time of the second communication event.

[0197] Aspect 11: A method according to any one of Aspects 1-10, wherein the amount of time between the second time resource and the first communication is the same amount of time as the amount of time between the fourth time resource and the second communication, or wherein the amount of time between the second time resource and the end time of the first communication event is the same amount of time as the amount of time between the third time resource and the end time of the second communication event.

[0198] Aspect 12: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of aspects 1-11.

[0199] Aspect 13: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 1-11.

[0200] Aspect 14: An apparatus for wireless communication, comprising at least one component for performing the method according to one or more of aspects 1-11.

[0201] Aspect 15: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1-11.

[0202] Aspect 16: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of aspects 1-11.

[0203] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the various aspects.

[0204] Further disclosure is included in the appendix. The appendix is provided for illustrative purposes only and is considered a part of the specification. Definitions, illustrations, or other descriptions in the appendix do not supersede or override similar information included in the detailed description or the accompanying drawings. Furthermore, definitions, illustrations, or other descriptions in the detailed description or the accompanying drawings do not supersede or override similar information included in the appendix. Furthermore, the appendix is not intended to limit the possible aspects of the disclosure.

[0205] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other terms, "software" should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes and / or functions, and other examples. As used herein, a "processor" is implemented with a combination of hardware and / or hardware and software. It is apparent that the systems and / or methods described herein can be implemented with different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit these aspects. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement the systems and / or methods at least in part based on the description herein.

[0206] As used herein, "satisfying a threshold" may refer to a value greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0207] Even if a specific combination of features is described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of each aspect. Many of these features can be combined in a manner not specifically described in the claims and / or not disclosed in the specification. The disclosure of each aspect includes the combination of each dependent claim and each other claim in the claim set. As used herein, the phrase "at least one" mentioned in the list of items refers to any combination of these items, including single members. As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, as well as any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c). Or any other arrangement of a, b and c).

[0208] Unless explicitly described as such, elements, actions, or instructions used herein should not be construed as critical or essential. Furthermore, as used herein, the articles "a" and "an" are intended to include one or more items and can be used interchangeably with "one or more." Furthermore, as used herein, the article "the" is intended to include one or more items referenced in conjunction with the article "the" and can be used interchangeably with "one or more." Furthermore, as used herein, the terms "set" and "group" are intended to include one or more items and can be used interchangeably with "one or more." Figure 1 In the case of multiple items, the phrase "only one" or similar language is used. Furthermore, as used herein, the terms "has," "have," "having," and the like are intended to be open-ended terms that do not limit the elements they modify (e.g., an element "having" A may also have B). Furthermore, unless expressly stated otherwise, the phrase "based on" is intended to mean "based, at least in part, on." Furthermore, as used herein, the term "or" when used in series is intended to be inclusive and may be used interchangeably with "and / or" unless expressly stated otherwise (e.g., if used in combination with "either" or "only one of").

Claims

1. A central device for wireless communication, comprising: Memory; as well as One or more processors, coupled to the memory, configured to: sending a first communication to initiate a first communication event; sending a first synchronization message during a first time resource associated with the first communication event, the first time resource being associated with a first peripheral device; sending a second synchronization message during a second time resource associated with the first communication event, the second time resource being associated with a second peripheral device; sending a second communication to initiate a second communication event; monitoring a first response from the first peripheral device during a third time resource associated with the first time resource, the third time resource associated with the second communication event; and A second response from the second peripheral device is monitored during a fourth time resource associated with the second time resource, the fourth time resource being associated with the second communication event.

2. The central device according to claim 1, wherein: The one or more processors are further configured to: Synchronization is established with the first peripheral device based at least in part on receiving the first response.

3. The central device according to claim 1, wherein: Based at least in part on a failure to receive the first response, the one or more processors are further configured to: sending a third communication to initiate a third communication event; sending the first synchronization message during a fifth time resource associated with the third communication event, the fifth time resource being associated with the first peripheral device; sending a fourth communication to initiate a fourth communication event; as well as A third response from the first peripheral device is monitored during a sixth time resource associated with the fifth time resource, the sixth time resource being associated with the fourth communication event.

4. The central device according to claim 1, wherein: Based at least in part on a failure to receive the second response, the one or more processors are further configured to: sending a third communication to initiate a third communication event based at least in part on a failure to receive the second response; sending the second synchronization message during a fifth time resource associated with the third communication event based at least in part on a failure to receive the second response, the fifth time resource being associated with the second peripheral device; sending a fourth communication to initiate a fourth communication event; as well as A third response from the second peripheral device is monitored during a sixth time resource associated with the fifth time resource, the sixth time resource being associated with the fourth communication event.

5. The central device according to claim 4, wherein: Based at least in part on receiving the first response, the one or more processors are further configured to: communicating with the first peripheral device during a seventh time resource associated with the third communication event based at least in part on receiving the first response; as well as Based at least in part on receiving the first response, communicating with the first peripheral device during an eighth time resource associated with the fourth communication event.

6. The central device according to claim 1, wherein: One or more of the first synchronization message or the second synchronization message includes an indication of one or more of: a first offset associated with a time between a start of the first synchronization message and a start of the second communication, a second offset associated with a time between the start of the second communication and the third time resource, or A third offset is associated with a time between a start of the second communication and the fourth time resource.

7. The central device according to claim 1, wherein: The first communication, the second communication, the first response, or the second response includes: The first part of the payload includes the data, and A second portion of the payload includes control information, the control information being configured to be repeated if not acknowledged.

8. The central device according to claim 7, wherein: The data is associated with one or more of the following: Extended reality data, Positioning information, Power status information, Gyroscope data, tactile data, or Received input data.

9. The central device according to claim 7, wherein: The control information includes one or more of the following: a sequence number associated with the control information or the data, the next expected serial number associated with the first peripheral device, or A next expected serial number associated with the second peripheral device.

10. The central device according to claim 1, wherein: the amount of time between the first time resource and the first communication is the same amount of time as the amount of time between the third time resource and the second communication, or The amount of time between the first time resource and the end time of the first communication event is the same as the amount of time between the third time resource and the end time of the second communication event.

11. The central device according to claim 1, wherein: the amount of time between the second time resource and the first communication is the same amount of time as the amount of time between the fourth time resource and the second communication, or The amount of time between the second time resource and the end time of the first communication event is the same as the amount of time between the third time resource and the end time of the second communication event.

12. A method of wireless communication performed by a central device, comprising: sending a first communication to initiate a first communication event; sending a first synchronization message during a first time resource associated with the first communication event, the first time resource being associated with a first peripheral device; sending a second synchronization message during a second time resource associated with the first communication event, the second time resource being associated with a second peripheral device; sending a second communication to initiate a second communication event; monitoring a first response from the first peripheral device during a third time resource associated with the first time resource, the third time resource associated with the second communication event; as well as A second response from the second peripheral device is monitored during a fourth time resource associated with the second time resource, the fourth time resource being associated with the second communication event.

13. The method according to claim 12, further comprising: Synchronization is established with the first peripheral device based at least in part on receiving the first response.

14. The method according to claim 12, further comprising: Failure to receive the first response; sending a third communication to initiate a third communication event based at least in part on a failure to receive the first response; sending the first synchronization message during a fifth time resource associated with the third communication event based at least in part on a failure to receive the first response, the fifth time resource being associated with the first peripheral device; sending a fourth communication to initiate a fourth communication event; as well as A third response from the first peripheral device is monitored during a sixth time resource associated with the fifth time resource, the sixth time resource being associated with the fourth communication event.

15. The method according to claim 12, further comprising: receiving the first response from the first peripheral device during the third time resource; failing to receive the second response from the second peripheral device during the fourth time resource; sending a third communication to initiate a third communication event based at least in part on a failure to receive the second response; sending the second synchronization message during a fifth time resource associated with the third communication event based at least in part on a failure to receive the second response, the fifth time resource being associated with the second peripheral device; sending a fourth communication to initiate a fourth communication event; as well as A third response from the second peripheral device is monitored during a sixth time resource associated with the fifth time resource, the sixth time resource being associated with the fourth communication event.

16. The method according to claim 15, further comprising: communicating with the first peripheral device during a seventh time resource associated with the third communication event based at least in part on receiving the first response; as well as Based at least in part on receiving the first response, communicating with the first peripheral device during an eighth time resource associated with the fourth communication event.

17. The method according to claim 12, wherein: One or more of the first synchronization message or the second synchronization message includes an indication of one or more of: a first offset associated with a time between a start of the first synchronization message and a start of the second communication, a second offset associated with a time between the start of the second communication and the third time resource, or A third offset is associated with a time between a start of the second communication and the fourth time resource.

18. The method according to claim 12, wherein: The first communication, the second communication, the first response, or the second response includes: The first part of the payload includes the data, and A second portion of the payload includes control information, the control information being configured to be repeated if not acknowledged.

19. The method according to claim 18, wherein The data is associated with one or more of the following: Extended reality data, Positioning information, Power status information, Gyroscope data, tactile data, or Received input data.

20. The method according to claim 18, wherein The control information includes one or more of the following: a sequence number associated with the control information or the data, the next expected serial number associated with the first peripheral device, or A next expected serial number associated with the second peripheral device.

21. The method according to claim 12, wherein the amount of time between the first time resource and the first communication is the same amount of time as the amount of time between the third time resource and the second communication, or The amount of time between the first time resource and the end time of the first communication event is the same as the amount of time between the third time resource and the end time of the second communication event.

22. The method according to claim 12, wherein the amount of time between the second time resource and the first communication is the same amount of time as the amount of time between the fourth time resource and the second communication, or The amount of time between the second time resource and the end time of the first communication event is the same as the amount of time between the third time resource and the end time of the second communication event.

23. A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising: One or more instructions that, when executed by one or more processors of a central device, cause the central device to: sending a first communication to initiate a first communication event; sending a first synchronization message during a first time resource associated with the first communication event, the first time resource being associated with a first peripheral device; sending a second synchronization message during a second time resource associated with the first communication event, the second time resource being associated with a second peripheral device; sending a second communication to initiate a second communication event; monitoring a first response from the first peripheral device during a third time resource associated with the first time resource, the third time resource associated with the second communication event; as well as A second response from the second peripheral device is monitored during a fourth time resource associated with the second time resource, the fourth time resource being associated with the second communication event.

24. The non-transitory computer readable medium of claim 23, wherein: The one or more instructions further cause the central device to: Synchronization is established with the first peripheral device based at least in part on receiving the first response.

25. The non-transitory computer readable medium of claim 23, wherein: The one or more instructions further cause the central device to: sending a third communication to initiate a third communication event based at least in part on a failure to receive the first response; sending the first synchronization message during a fifth time resource associated with the third communication event based at least in part on a failure to receive the first response, the fifth time resource being associated with the first peripheral device; sending a fourth communication to initiate a fourth communication event; as well as A third response from the first peripheral device is monitored during a sixth time resource associated with the fifth time resource, the sixth time resource being associated with the fourth communication event.

26. The non-transitory computer-readable medium of claim 23, wherein: The one or more instructions further cause the central device to: receiving the first response from the first peripheral device during the third time resource; sending a third communication to initiate a third communication event based at least in part on a failure to receive the second response; sending the second synchronization message during a fifth time resource associated with the third communication event based at least in part on a failure to receive the second response, the fifth time resource being associated with the second peripheral device; sending a fourth communication to initiate a fourth communication event; as well as A third response from the second peripheral device is monitored during a sixth time resource associated with the fifth time resource, the sixth time resource being associated with the fourth communication event.

27. An apparatus for wireless communication, comprising: means for sending a first communication to initiate a first communication event; means for sending a first synchronization message during a first time resource associated with the first communication event, the first time resource being associated with a first peripheral device; means for sending a second synchronization message during a second time resource associated with the first communication event, the second time resource being associated with a second peripheral device; means for sending a second communication to initiate a second communication event; means for monitoring a first response from the first peripheral device during a third time resource associated with the first time resource, the third time resource being associated with the second communication event; as well as Means for monitoring for a second response from the second peripheral device during a fourth time resource associated with the second time resource, the fourth time resource associated with the second communication event.

28. The apparatus according to claim 27, further comprising: Means for establishing synchronization with the first peripheral device based at least in part on receiving the first response.

29. The apparatus according to claim 27, further comprising: means for failing to receive said first response; means for sending a third communication to initiate a third communication event based at least in part on a failure to receive the first response; means for sending the first synchronization message during a fifth time resource associated with the third communication event based at least in part on a failure to receive the first response, the fifth time resource being associated with the first peripheral device; means for sending a fourth communication to initiate a fourth communication event; as well as Means for monitoring a third response from the first peripheral device during a sixth time resource associated with the fifth time resource, the sixth time resource associated with the fourth communication event.

30. The apparatus of claim 27, further comprising: means for receiving said first response from said first peripheral device during said third time resource; means for failing to receive the second response from the second peripheral device during the fourth time resource; means for sending a third communication to initiate a third communication event based at least in part on a failure to receive the second response; means for sending the second synchronization message during a fifth time resource associated with the third communication event based at least in part on a failure to receive the second response, the fifth time resource being associated with the second peripheral device; means for sending a fourth communication to initiate a fourth communication event; as well as Means for monitoring a third response from the second peripheral device during a sixth time resource associated with the fifth time resource, the sixth time resource associated with the fourth communication event.

Images