One-to-many wireless communication method, apparatus, and system

Abstract

The application discloses a one-to-many wireless communication method, device and system. A receiving device communicates with N slave devices on the same physical channel through a radio frequency transceiver in a time division multiplexing superframe, and at least two target slave devices have a human-computer interface input unit and an audio acquisition unit. The receiving device determines the number of audio frame transmissions per superframe for each target slave device according to the audio data generation rate, the single frame audio net payload length and the superframe period of each target slave device, so that the audio net payload transmission rate is not lower than the generation rate; the number of transmissions is less than the time slot capacity of the device, the sum is less than the total capacity of the superframe, and the remaining number of transmissions in the time slot is used for human-computer interface data and audio retransmission. The target slave device configures the radio frequency protocol layer automatic retransmission number to zero, and the unconfirmed audio frame is only retransmitted in the time slot of the subsequent superframe of the device. The receiving device feeds back the confirmation information, identifies and recombines the continuous audio stream of each target slave device according to the transmission sequence mark, and realizes the time slot resource isolation between devices.

Description

Technical Field

[0001] This invention relates to the field of wireless communication technology, and in particular to a one-to-many wireless communication method, a receiving device, a wireless input device, and a wireless communication system. Background Technology

[0002] Wireless mice, wireless keyboards, and other human interface devices (HIDs) typically communicate with the host via a proprietary protocol in the 2.4 GHz band using a dedicated receiver, or connect directly to the host via Bluetooth. With the increasing popularity of applications such as voice interaction, voice chat, and online conferencing, there is a growing demand for integrating microphones and other audio acquisition units into input devices like mice and keyboards, enabling devices to collect and transmit voice data while simultaneously reporting HID data.

[0003] In a common configuration, different wireless peripherals use their own receivers, and audio peripherals and human-machine interface (HMI) peripherals may each occupy a USB port on the host computer. However, thin and light laptops and tablets have a limited number of USB ports available for peripherals, making it difficult to adapt to use cases where host interface resources are limited. Therefore, a one-to-many solution has emerged, connecting a single receiver to multiple wireless peripherals. However, existing one-to-many solutions typically focus on either HMI services or audio services: solutions for multiple HMI devices usually do not involve carrying multiple continuous audio streams; solutions for multiple wireless microphones do not involve low-latency transmission of HMI data.

[0004] When using Bluetooth Low Energy (BLE) to transmit audio and HMI data, audio can be transmitted via the low-power audio isochronous channel, and HMI data can be transmitted via the attribute protocol. The wireless controller manages the connection and transmission event scheduling. In multi-device concurrent scenarios, high refresh rate HMI reports and continuous audio from each device require wireless transmission resources, increasing resource scheduling complexity with the number of devices. BLE typically uses lossy audio encoding, potentially introducing encoding artifacts. Existing 2.4GHz proprietary protocol solutions either reserve extra channel capacity for audio transmission and combine acknowledgment and retransmission mechanisms to improve reliability, or carry audio and HMI data blocks within the same wireless data packet. Some solutions can even be extended to point-to-many communication. However, when multiple slave devices simultaneously generate continuous audio and HMI data, existing solutions struggle to simultaneously meet the following requirements: how to ensure each slave device receives transmission capacity matching its audio generation speed, how to satisfy the overall transmission needs of all slave devices within limited wireless resources, and how to prevent transmission anomalies in individual slave devices from affecting the normal transmission of other slave devices.

[0005] Furthermore, wireless channels are susceptible to interference and packet loss. Retransmitting failed audio data consumes additional wireless resources and time, potentially affecting the normal transmission of other devices in multi-device scenarios. Discarding undelivered audio data directly causes audio interruptions, impacting voice quality. Reliability and the requirement for non-interference between multiple devices are difficult to reconcile.

[0006] Therefore, how to enable multiple wireless peripherals, each with both human-machine interface input and audio acquisition capabilities, to transmit continuous audio concurrently through a single receiver while ensuring low latency of human-machine interface data, and to ensure that the transmission of multiple slave devices does not interfere with each other, is a technical problem that urgently needs to be solved in this field. Summary of the Invention

[0007] In view of this, the present invention provides a one-to-many wireless communication method, a receiving device, a wireless input device, and a wireless communication system, which aim to enable multiple wireless peripherals, each with human-machine interface input and audio acquisition capabilities, to transmit continuous audio concurrently through a single receiver while ensuring low latency of human-machine interface data, and to ensure that the transmission of multiple slave devices does not interfere with each other.

[0008] In a first aspect, the present invention provides a one-to-many wireless communication method, executed by a receiving device and N slave devices, where N ≥ 2. The receiving device includes a radio frequency transceiver circuit, operates on the same physical channel with the N slave devices, and communicates via time-division multiplexing superframes. The superframe contains time slots allocated to the N slave devices respectively. At least two target slave devices among the N slave devices respectively include a human-machine interface input unit and an audio acquisition unit. The method includes: the receiving device determining the number of audio data frame transmissions by each target slave device within each superframe based on the audio data generation rate of each target slave device, the net payload length used to carry audio data in a single audio data frame, and the period of the superframe, such that the corresponding audio payload transmission rate is not lower than the audio data generation rate of the target slave device; wherein, the number of audio data frame transmissions by any target slave device is less than the number of transmissions that the time slot of the target slave device can accommodate, and the remaining transmissions in the time slot are used to carry the retransmission of the human-machine interface data and audio data frames of the target slave device, and the sum of the number of audio data frame transmissions by all target slave devices is less than the total number of transmissions that the superframe can accommodate; the target slave devices will... The automatic retransmission count of the radio frequency protocol layer is configured to zero. Within the time slot of this device, audio data frames carrying transmission sequence identifiers are transmitted according to the determined number of audio data frame transmissions. The device also transmits the human-machine interface data generated by the human-machine interface input unit within the time slot of this device. The receiving device receives the audio data frames and the human-machine interface data and sends acknowledgment information back to the corresponding target slave device. The target slave device adds audio data frames not acknowledged by the acknowledgment information to the retransmission queue and retransmits them using the remaining transmission count in the time slot of the device in subsequent superframes. Based on the transmission sequence identifier, the receiving device deduplicates the first and retransmitted audio data frames and reassembles them into continuous audio streams corresponding to each target slave device.

[0009] In the above scheme, the receiving device configures basic audio transmission resources for each target slave device according to the audio data generation rate of each target slave device, so that each target slave device obtains a transmission capability that matches its audio generation speed. The number of audio data frame transmissions determined for each device is verified by the time slot capacity and the total superframe capacity of the device, ensuring that the configuration of basic audio resources is feasible across all target slave devices. The retransmission of audio data is limited to the time slot of the subsequent superframe of the device and only occupies the remaining transmission count in the time slot of the device. Combined with the setting of zero automatic retransmission count of the radio frequency protocol layer, the retransmission of any target slave device does not occupy the time slot resources of other slave devices, realizing the mutual isolation of transmission resources between devices.

[0010] In one possible implementation, the HMI data is transmitted as an independent data frame, occupying the remaining transmission attempts; alternatively, the HMI data is encapsulated in the payload of the audio data frame, sharing the same transmission attempt with the audio data, and does not occupy the remaining transmission attempts. Thus, the HMI data and continuous audio are multiplexed and transmitted within the same slave device's time slot, and the HMI data does not need to occupy a transmission window separate from the device's time slot, which helps reduce its reporting latency.

[0011] In one possible implementation, the receiving device configures multiple logical receiving channels corresponding to different slave devices on the same physical channel, and determines the slave device that sent the data frame based on the address prefix carried in the received data frame. Thus, the receiving device can distinguish and receive data from multiple slave devices with a single RF transceiver circuit, eliminating the need to set up independent RF transceiver circuits for each slave device.

[0012] In one possible implementation, the number of retransmissions of any audio data frame is limited by a preset upper limit. Audio data frames that have not been acknowledged after reaching the preset upper limit are removed from the retransmission queue. This avoids the continuous retransmission of individual audio data frames occupying the remaining transmission count for an extended period, ensuring the timely transmission of subsequent audio data.

[0013] In one possible implementation, when the waiting time for a queue item in the retransmission queue exceeds a first duration, the target slave device increases the transmission priority of that queue item; when the waiting time exceeds a second duration, the queue item is discarded, where the second duration is longer than the first duration. This achieves a balance between reliable audio data transmission and timeliness: audio data frames that have been waiting for a longer period are prioritized for retransmission, while expired audio data frames are discarded, preventing outdated data from crowding out the transmission opportunities of new data.

[0014] In one possible implementation, the receiving device sends the determined number of audio data frame transmissions to the corresponding target slave device via a pairing response or downlink control frame. Thus, the target slave device can know its resource configuration upon pairing completion or during operation, without independent calculation, ensuring consistency of resource views between the transmitting and receiving ends.

[0015] In one possible implementation, the audio data frame carries un-lossy pulse-code modulation data with a sampling rate of 16kHz, a quantization bit depth of 16bit, and a mono channel. The target slave device is a wireless mouse, wireless keyboard, wireless presenter, or wireless game controller, and the audio acquisition unit is a microphone. The same physical channel is located in the 2.4GHz ISM band. Thus, the voice data is transmitted directly without lossy encoding, avoiding the additional distortion caused by lossy encoding.

[0016] Secondly, the present invention provides a receiving device, including a radio frequency transceiver circuit, a USB interface circuit, a processor, and a memory. When the instructions stored in the memory are executed by the processor, the receiving device performs the steps described in any implementation of the first aspect, and reports the human-machine interface data and continuous audio streams corresponding to each target slave device to the host via the USB interface circuit. Thus, human-machine interface data and audio data from multiple slave devices are reported to the host via a single receiving device and a single USB interface, reducing the number of USB interfaces required on the host.

[0017] Thirdly, the present invention provides a wireless input device, including a human-machine interface input unit, an audio acquisition unit, a radio frequency transceiver circuit, a processor, and a memory. When the instructions stored in the memory are executed by the processor, the wireless input device, as a target slave device, performs the steps executed by the target slave device in any implementation of the method of the first aspect.

[0018] Fourthly, the present invention provides a wireless communication system, including the receiving device described in the second aspect and N slave devices, where N ≥ 2, and at least two of the N slave devices are the wireless input devices described in the third aspect.

[0019] Fifthly, the present invention provides a computer-readable storage medium storing a computer program that, when executed by a processor, causes a receiving device to perform steps of the method performed by the receiving device in any implementation of the first aspect, or causes a wireless input device to perform steps of the method performed by the target slave device as a target slave device.

[0020] The technical solution provided by this invention has at least the following beneficial effects: First, multiple slave devices, each with both human-machine interface input and audio acquisition capabilities, can communicate concurrently through a single receiving device and report data to the host via a single USB interface, reducing the number of USB interfaces occupied by the host. Second, the receiving device configures basic audio transmission resources for each target slave device according to its audio data generation rate, and performs time slot capacity and total superframe capacity verification on the number of audio data frame transmissions. When the capacity conditions are met, each target slave device obtains transmission capacity commensurate with its audio data generation rate, while enabling multiplexing of human-machine interface data within the device's time slot, which helps reduce reporting latency. Third, the automatic retransmission count of the radio frequency protocol layer is zero, and retransmission is only performed within the subsequent superframe time slot of the device, ensuring that audio retransmission by any target slave device does not occupy the time slot resources of other slave devices, achieving isolation of transmission resources between devices. Fourth, the receiving device performs deduplication and reassembly on the first and retransmitted audio data frames according to the transmission sequence identifier, which helps reduce the impact of duplicate frames and out-of-order sequences on audio stream recovery, balancing the reliability of wireless transmission and the real-time performance of audio data. Attached Figure Description

[0021] Figure 1 This is a schematic diagram of the architecture of a one-to-many wireless communication system provided in an embodiment of the present invention;

[0022] Figure 2 This is a schematic diagram of the superframe structure and the allocation of transmission times within a time slot provided in an embodiment of the present invention;

[0023] Figure 3 An interactive flowchart of a one-to-many wireless communication method provided in an embodiment of the present invention;

[0024] Figure 4 A flowchart for determining the number of audio data frame transmissions and verifying capacity provided in an embodiment of the present invention;

[0025] Figure 5 A timing diagram illustrating the retransmission and deduplication of audio data frames provided in an embodiment of the present invention;

[0026] Figure 6 This is a schematic diagram of the receiving device and wireless input device provided in an embodiment of the present invention. Detailed Implementation

[0027] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0028] like Figure 1 As shown, the one-to-many wireless communication system provided in this embodiment of the invention includes a receiving device 100 and N slave devices 200, where N≥2. The receiving device 100 includes a radio frequency transceiver circuit 110, a USB interface circuit 120, a processor 130, and a memory 140, and is connected to a host 300 via a single USB interface. At least two of the N slave devices 200 are target slave devices. Each target slave device includes a human-machine interface input unit 210 (e.g., an optical displacement sensor and key circuit, keyboard scanning matrix), an audio acquisition unit 220 (e.g., a digital microphone), a radio frequency transceiver circuit 230, a processor 240, and a memory 250. Target slave devices may be, for example, wireless mice with integrated microphones, wireless keyboards, wireless presenters, or wireless game controllers. The slave devices other than the target slave devices may be devices with only human-machine interface input units. The receiving device and all slave devices operate on the same physical channel at any given time, which is located in the 2.4GHz ISM band. In one example, the RF transceiver circuit communicates using an RF protocol that supports data frame acknowledgment, a logical receive pipeline, and configurable automatic retransmissions. The physical layer rate is determined by the RF chip used, such as 2 Mbps or 4 Mbps. In this example, the private data pipeline payload of the data frame is used to carry audio data or human-machine interface reports. The receiving device distinguishes the data frame type based on the payload length: data frames carrying audio data have a payload of the length required to reach an audio frame, such as 64 bytes of audio data. In the mode using the acknowledgment mechanism, an additional 2-byte header is added to form a 66-byte payload. The 2-byte header carries control information such as the transmission sequence identifier and is located outside the audio payload; the payload length of the human-machine interface data frame is shorter than the specified length.

[0029] For clarity, the following conventions are used in this document. A single “transmission” refers to a complete radio frequency (RF) interaction initiated by the device, including transmission preparation (e.g., a rapid rise time of approximately 40 μs), data frame over-the-air transmission, transmit / receive conversion, acknowledgment frame reception or acknowledgment waiting timeout (transmissions without an acknowledgment mechanism do not include the acknowledgment-related phase), and the guard interval required between adjacent RF interactions. With the RF protocol layer's automatic retransmission count configured to zero, the maximum occupancy time for a single transmission can be predetermined. “Net payload length used to carry audio data in a single audio data frame” (referred to as audio payload length L) refers to the number of bytes actually used to carry audio sampling data in the payload of a single audio data frame, excluding additional headers, transmission sequence identifiers, check fields, and human-machine interface data multiplexed with the audio data. “Number of transmissions that a time slot can accommodate” (time slot capacity C) refers to the number of transmissions that can be completed within one time slot, calculated based on the physical layer rate and the complete duration of a single transmission. "Remaining transmission counts" refers to the non-negative difference between the time slot capacity allocated to the target slave device and the number of audio data frame transmissions for that device; when the difference is greater than zero, it is used for independent transmission of human-machine interface data and retransmission of audio data frames for the target slave device. "Audio data generation rate" R refers to the bit rate of the pulse code modulation data output by the audio acquisition unit. For example, with a sampling rate of 16kHz, quantization bits of 16bit, and mono, R=256kbps, which means 32 bytes of audio data are generated every millisecond.

[0030] The system supports at least two user-configurable operating modes. In Link Quality Assurance mode, audio data frames are transmitted using an acknowledgment mechanism and carry a transmission sequence identifier. The receiving device sends back acknowledgment information via the acknowledgment frame. Unacknowledged audio data frames are retransmitted in subsequent time slots according to the mechanism described below. In Device Quantity Priority mode, undelivered audio data frames are not retransmitted; instead, they are compensated by zero-value padding by the receiving device or the host side. In this mode, audio data frames may not use an acknowledgment mechanism or include a transmission sequence identifier header, or they may use an acknowledgment mechanism but not add unacknowledged audio data frames to the retransmission queue. This reduces the overhead of retransmissions on wireless resources and the time spent on each transmission, allowing for more slave devices to connect. The following description focuses on Link Quality Assurance mode.

[0031] As examples of single transmission duration, at a 2Mbps physical layer, the over-the-air transmission of a 64-byte payload data frame takes approximately 280 to 288 μs. A complete transmission without acknowledgment takes approximately 321 to 330 μs, with acknowledgment and an empty acknowledgment frame, it takes approximately 380 to 420 μs, and with an acknowledgment frame carrying 8 bytes of data, it takes approximately 410 to 455 μs. At a 4Mbps physical layer, the over-the-air transmission of a 64-byte payload takes approximately 140 to 144 μs. A complete transmission without acknowledgment takes approximately 181 to 186 μs, with acknowledgment and an empty acknowledgment frame, it takes approximately 220 to 250 μs, and with an acknowledgment frame carrying 8 bytes of data, it takes approximately 235 to 270 μs. These values ​​are estimates based on RF chip parameters and conventional optimized configurations. Actual values ​​should be measured on the entire device and can be pre-measured to create a configuration table stored in the receiver's memory.

[0032] like Figure 2 As shown, a superframe includes device time slots allocated to N slave devices, and may also include synchronization, control, or protection periods; in the example where the device time slots are arranged sequentially and no other periods are specified, the superframe period is... This is the sum of the time slot durations for all devices. The duration of each device's time slot is configured based on the device type, physical layer rate, and data volume, and does not need to be equal in length: the target slave device is allocated a time slot long enough to accommodate the basic audio transmission and the remaining transmission; slave devices that only transmit HMI data can be allocated shorter time slots, for example, 250μs at a physical layer rate of 4Mbps. In this case, with two slave devices forming a 500μs superframe, the HMI report rate can reach up to 2kHz. The time slot duration can also include anti-jitter protection intervals. For example, at 2Mbps, an 800μs time slot with 150μs protection intervals before and after the data transmission time can be used, or a 600μs time slot can be used after compressing the protection interval. Figure 2 The enlarged view at the bottom shows a target slave device's time slot: the time slot capacity is C transmissions, of which M are used for the basic transmission of audio data frames, and the remaining CM are the remaining transmission counts. Figure 2 Two multiplexing methods for HMI data are also shown. Method 1: HMI data forms an independent data frame, with the payload being a HMI report, occupying one of the remaining transmission attempts. Method 2: The HMI report is encapsulated in the payload of an audio data frame, sharing the same transmission attempt with the audio data, without occupying any remaining transmission attempts. In this case, the net audio payload length of the audio data frame is correspondingly reduced. The receiving device determines the audio data portion and the HMI data portion of the payload based on the data frame type field, the predetermined payload format, or the preset correspondence between the payload length and the frame format, and processes them separately. HMI data is not retransmitted to ensure its real-time reporting; the audio data frame is retransmitted in link quality assurance mode according to the mechanism described later.

[0033] like Figure 3 As shown, the one-to-many wireless communication method includes: S101, the receiving device generates a rate according to the audio data of each target slave device , the audio payload length and the superframe period , respectively determining the number of audio data frame transmissions per superframe for each target slave device , and issues them to the corresponding target slave device via a pairing response or a downlink control frame; S102, the target slave device configures the number of automatic retransmissions at the radio frequency protocol layer to zero, and follows the rule within its own time slot transmits an audio data frame carrying a transmission sequence identifier, and transmits human-machine interface data within its own time slot; S103, the receiving device receives the audio data frame and the human-machine interface data, and feeds back confirmation information to the corresponding target slave device via a confirmation frame; S104, the target slave device adds the unacknowledged audio data frame to the retransmission queue; S105, the target slave device retransmits the audio data frames in the retransmission queue by occupying the remaining transmission times within its own time slot in subsequent superframes; S106, the receiving device deduplicates the audio data frames transmitted for the first time and retransmitted according to the transmission sequence identifier, reorganizes them into continuous audio streams respectively corresponding to each target slave device, and reports the streams together with the human-machine interface data to the host via the USB interface circuit.

[0034] As Figure 4 shown, the receiving device follows determines the number of audio data frame transmissions, where the unit is bit / s, the unit is s, the unit is byte, represents rounding up. Then perform two levels of verification: First, < , that is, the number of audio data frame transmissions of any target slave device is less than the time slot capacity of the device, ensuring that there are remaining transmission times left in the time slot; Second, sum all K target slave devices (K≤N), Σ <Q, where Q is the sum of the number of transmissions that can be accommodated in the time slots allocated to each target slave device in the superframe, excluding synchronization, downlink control, channel scanning periods, and transmission resources allocated to non-target slave devices. Since Q is not greater than the total number of transmissions that the superframe can accommodate, satisfying Σ <Q satisfies the condition for the total number of transmissions. When any verification fails, the receiving device rejects the configuration, jointly adjusts the device time slot duration, audio payload length, physical layer rate, number of target slave devices or other communication parameters, and then recalculates the number of audio data frame transmissions and the time slot capacity until both are satisfied < and Σ <Q, or adopt the full-load transmission mode described later. The receiving device queries the aforementioned configuration table or determines in real time according to the above calculation formula .

[0035] In one embodiment, the system operates in a link quality assurance mode, the physical layer rate is 4Mbps, and 3 target slave devices each collect 16kHz / 16bit mono audio, =256kbps. The time slot duration of each target slave device is 600μs, and the time slot capacity is determined according to the complete transmission with the acknowledgement mechanism: a complete transmission carrying 66 bytes of payload and including a null acknowledgement frame takes approximately 225 to 255μs, and two such transmissions total approximately 450 to 510μs, which is less than 600μs and leaves a protection margin, the time slot capacity =2. =1.8ms, the audio generation amount per superframe is about 57.6 bytes, and each audio data frame adopts a pure audio payload that does not multiplex the human-machine interface report, =64 bytes, , the audio net payload transmission rate is 64×8 / 1.8ms≈284kbps, which meets the requirement of no less than ; the check =1< =2, Σ =3<Q=6 all pass, and one remaining transmission time is left in the time slot of each target slave device, which is used for independent transmission of human-machine interface data or retransmission of audio data frames, wherein the retransmission of audio data frames also adopts the acknowledgement mechanism.

[0036] The slave device configures the number of automatic retransmissions at the radio frequency protocol layer to zero, so that any transmission will not be automatically retransmitted when no acknowledgement frame is received. For comparison, when the radio frequency protocol layer is configured with multiple automatic retransmissions, a predetermined retransmission interval is set between adjacent transmission attempts; if the number of automatic retransmissions and their duration are not included in the device time slot budget, the cumulative duration of multiple automatic retransmissions may exceed the time slot of the local device, thereby affecting the normal transmission of subsequent slave devices. In one test configuration, the number of automatic retransmissions is 6, and the start interval between adjacent transmission attempts is about 435μs, and its cumulative time is significantly longer than the single device time slot of this embodiment. This is exactly the scenario where automatic retransmissions are not included in the time slot budget as described in the background art.

[0037] As Figure 5 shown, if the slave device does not receive the acknowledgement frame within the acknowledgement receiving window, it determines that the audio data frame is unacknowledged, and adds it to the to-be-retransmitted queue. In one implementation, the to-be-retransmitted queue is a first-in first-out queue with a depth of 4, and each queue entry records the transmission sequence identifier, enqueue time and the number of retransmissions. In the time slot of the local device in the subsequent superframe, the slave device first completes the The audio is sent first, and then the remaining transmission count is used to send queue items in the retransmission queue. In one implementation, when the remaining transmission count is insufficient to simultaneously send the HMI data frame and the audio data frame to be retransmitted, the HMI data is sent first to ensure low latency, followed by the audio data frame to be retransmitted. Queue items with a waiting time exceeding a first duration are given priority over those without. Data that cannot be sent is retained in the local device time slot of a subsequent superframe. Priority enhancement refers to improving the transmission order of a queue item relative to other queue items within the retransmission queue, without changing the transmission order within each superframe. Resource configuration for basic audio transmission. If any audio data frame remains unacknowledged after being retransmitted a preset maximum number of times (e.g., 3 times), the frame is removed from the queue. Queue entries with a waiting time exceeding a first duration (e.g., 20ms) have their transmission priority increased; those exceeding a second duration (e.g., 40ms) are discarded. The second duration is longer than the first. When the queue is full, the earliest enqueued entry is removed to accommodate new entries. A transmission sequence identifier is maintained by each target slave device and carried in the additional header of the audio data frame. New audio data frames increment the transmission sequence identifier, while retransmitted audio data frames retain the original transmission sequence identifier. In one implementation, the transmission sequence identifier is cyclically counted with a fixed bit width, and the receiving device compares the sequence identifiers modulo-based. Figure 5 The timing diagram shows that if device A fails to acknowledge a transmission within its own time slot in superframe k, its retransmission occurs within device A's own time slot in superframe k+1, during which time slots of other devices are unaffected.

[0038] The receiving device maintains an independent reassembly buffer and expected transmission sequence identifier value for each target slave device. It removes duplicate frames and restores the transmission order according to the transmission sequence identifier. Upon receiving a duplicate audio data frame, it discards the duplicate copy and sends back an acknowledgment. For audio data frames that fail to arrive due to reaching the retransmission limit, exceeding the second duration, or queue overflow, the corresponding audio gaps are filled with zero-value sampling (mute) before continuing output, thus maintaining continuous audio stream output from each target slave device: when using USB audio reporting, the receiving device fills the gaps during reassembly; when using private channel reporting, the host-side software fills the gaps. In device quantity priority mode, undelivered audio data frames are also compensated using zero-value filling.

[0039] In another device-priority configuration without audio retransmission, the physical layer rate is 4 Mbps, with 4 target slave devices. Each target slave device has a 500 μs time slot, which can accommodate one transmission of an audio data frame and one transmission of a human-machine interface data frame. Each transmission does not use an acknowledgment mechanism (approximately 185 μs each time), or the audio data frame transmission uses an acknowledgment mechanism (approximately 225 to 255 μs) while the human-machine interface data frame transmission does not. Undelivered audio data frames are compensated by zero-value padding. The concurrent communication capability of 4 devices at a 4 Mbps physical layer with 500 μs time slots per device has been verified in a real-world test.

[0040] In another optional operating mode (full load transmission mode), the number of audio data frames transmitted from the target device is equal to the slot capacity. = In this mode, no remaining transmission attempts are set within the time slot. Human-machine interface (HMI) data is encapsulated in the payload of audio data frames at a reduced report rate. In this mode, the audio payload length of audio data frames carrying HMI reports is shorter than that of audio data frames without HMI reports. The receiving device verifies the audio payload transmission capability within a preset statistical period based on the HMI report cycle and the number of both types of audio data frames. This mode sacrifices retransmission opportunities within the time slot in exchange for supporting more target slave devices at the same physical layer rate. It is typically used in conjunction with the device quantity priority mode. Undelivered audio data frames are compensated by the receiving device or host side using the aforementioned zero-value filling method. The full-load transmission mode is an optional operating mode disclosed in this specification and is not an implementation method using the remaining transmission attempts mechanism. In an example of the full-load transmission mode, the system operates in device quantity priority mode with a physical layer rate of 2 Mbps and 3 target slave devices. A complete transmission of a data frame carrying a 64-byte payload without acknowledgment takes approximately 321 to 330 μs. The device time slot is configured as 600 μs, including guard intervals at time slot boundaries, and the time slot capacity... =1, =1800μs; approximately 57.6 bytes of audio are generated per superframe. =1= The audio payload transmission rate is 64×8 / 1.8ms≈284kbps, meeting the requirement of not less than 256kbps. Human-machine interface data is encapsulated in the audio data frame payload at a report rate of approximately 125Hz (one report every 8ms). Verified according to the statistical period, the total audio payload carried by the audio data frame is not less than the amount of audio data generated within the corresponding statistical period. The concurrent communication capability of three devices under a 2Mbps physical layer and a 600μs timeslot configuration per device has been verified in a real-world test. In another example with a full-load transmission mode, the physical layer rate is 4Mbps, and the timeslot length is 500μs. =2, when the total net audio payload actually carried by the two audio data frames is not less than the amount of audio data generated within the corresponding superframe period, 5 to 7 target slave devices can be configured according to... =2 transmits its own unlossy pulse code modulation audio, with the specific number supported determined by the actual audio payload length and the intra-frame multiplexing overhead reported by the human-machine interface. The remaining transmission count mechanism and the full-load transmission mode can be used for different communication configurations.

[0041] The receiving device is configured with multiple logical receive channels on the same physical channel, each corresponding to a different slave device. Each channel has a different address prefix. In one example, channel 0 is reserved for the pairing process, and channels 1 through 7 correspond to the time slots of each slave device. Data frames sent by slave devices carry their own address prefix, which the receiving device uses to determine the source of the data frames. A single RF transceiver circuit distinguishes and receives data from multiple slave devices. The receiving device reports the HMI data from each target slave device, along with the reconstructed continuous audio stream, to the host via the USB interface circuit. The reporting method includes two forms: First, the audio data is reported via a private report channel of the HMI class, carrying the identifier of the target slave device. This report is then parsed by the host software into an audio stream corresponding to each target slave device. Secondly, the receiving device is enumerated as a USB composite device. The human-machine interface data is reported through the endpoint of the human-machine interface class. The reporting of audio data includes two implementations: In one implementation, the continuous audio stream of each target slave device is mapped to different channels in the multi-channel data stream of the USB audio class, with one target slave device corresponding to one channel. The host distinguishes the audio source according to the channel position. In the other implementation, according to the settings, one target slave device is specified from multiple target slave devices to report its audio stream through the endpoint of the USB audio class, and the audio data of the remaining target slave devices is reported through the private reporting channel of the human-machine interface class.

[0042] like Figure 6 As shown, the memory 140 of the receiving device 100 stores instructions. When the instructions are executed by the processor 130, the receiving device performs the steps in the above method performed by the receiving device, and reports the human-machine interface data and the continuous audio stream corresponding to each target slave device to the host via the USB interface circuit 120. The memory 250 of the wireless input device 200 stores instructions. When the instructions are executed by the processor 240, the wireless input device performs the steps in the above method performed by the target slave device as a target slave device. This embodiment of the invention also provides a computer-readable storage medium, which can be a read-only memory, random access memory, flash memory, or other non-transitory storage medium capable of storing computer programs. When the computer program is executed by the processor, it causes the receiving device to perform the steps in the above method performed by the receiving device, or causes the wireless input device to perform the steps in the above method performed by the target slave device as a target slave device.

[0043] The physical layer rate, time slot duration, payload length, additional header length, audio sampling specification, reporting rate, queue depth, maximum number of retransmissions, first duration and second duration in the above embodiments are all examples, which can be configured according to application requirements. In the embodiment adopting the remaining transmission times mechanism, the following shall still be satisfied after configuration < and Σ <Q. In the optional operation mode adopting the full-load transmission mode, it is allowed = , this mode does not have an independent audio retransmission opportunity within a time slot, and human-machine interface data is transmitted by means of intra-frame multiplexing. Audio data can also be transmitted according to the same time division mechanism after being compressed and encoded under a bandwidth-limited configuration. The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any variation or replacement that can be easily conceived by a person skilled in the art within the technical scope disclosed by the present invention shall be covered within the protection scope of the present invention. The protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A one-to-many wireless communication method, executed by a receiving device and N slave devices, where N≥2, wherein the receiving device includes a radio frequency transceiver circuit, operates on the same physical channel with the N slave devices, and communicates via time-division multiplexing superframes, wherein the superframe contains time slots allocated to the N slave devices respectively, and at least two target slave devices among the N slave devices respectively include a human-machine interface input unit and an audio acquisition unit, characterized in that, The method includes: The receiving device determines the number of audio data frame transmissions by each target slave device within each superframe based on the audio data generation rate of each target slave device, the net payload length for carrying audio data in a single audio data frame, and the period of the superframe, ensuring that the corresponding audio payload transmission rate is not lower than the audio data generation rate of the target slave device. Wherein, the number of audio data frame transmissions by any target slave device is less than the number of transmissions that the target slave device's time slot can accommodate; the remaining transmissions within that time slot are used to carry the retransmission of the target slave device's human-machine interface data and audio data frames, and the sum of the number of audio data frame transmissions by all target slave devices is less than the total number of transmissions that the superframe can accommodate. The target slave device configures the automatic retransmission count of the radio frequency protocol layer to zero, transmits audio data frames carrying transmission sequence identifiers according to the determined number of audio data frame transmissions within the time slot of the device, and transmits the human-machine interface data generated by the human-machine interface input unit within the time slot of the device. The receiving device receives the audio data frame and the human-machine interface data, and sends back confirmation information to the corresponding target device. The target device adds audio data frames that have not been confirmed by the confirmation information to the retransmission queue and retransmits them using the remaining transmission count in the time slot of the device in the subsequent superframe. The receiving device, based on the transmission sequence identifier, deduplicates the first and retransmitted audio data frames and reassembles them into continuous audio streams corresponding to each target slave device.

2. The method according to claim 1, characterized in that, The human-machine interface data is sent as an independent data frame, occupying the remaining transmission count; or, the human-machine interface data is encapsulated in the payload of the audio data frame and shares the same transmission count with the audio data, without occupying the remaining transmission count.

3. The method according to claim 1, characterized in that, The receiving device configures multiple logical receiving channels corresponding to different slave devices on the same physical channel, and determines the slave device that sent the data frame based on the address prefix carried in the received data frame.

4. The method according to claim 1, characterized in that, The number of times any audio data frame can be retransmitted is limited by a preset upper limit. Audio data frames that have not been acknowledged after reaching the preset upper limit are removed from the retransmission queue.

5. The method according to claim 1, characterized in that, When the waiting time of a queue item in the retransmission queue exceeds a first duration, the target slave device increases the transmission priority of that queue item; when the waiting time exceeds a second duration, the queue item is discarded, where the second duration is longer than the first duration.

6. The method according to claim 1, characterized in that, The receiving device sends the determined number of audio data frame transmissions to the corresponding target slave device via a pairing response or downlink control frame.

7. The method according to claim 1, characterized in that, The audio data frame carries audio data that is pulse code modulation data without lossy encoding, with a sampling rate of 16kHz, a quantization bit depth of 16bit, and a mono channel; the target slave device is a wireless mouse, wireless keyboard, wireless presenter, or wireless game controller, and the audio acquisition unit is a microphone; the same physical channel is located in the 2.4GHz ISM band.

8. A receiving device, comprising a radio frequency transceiver circuit, a USB interface circuit, a processor, and a memory, characterized in that, When the instructions stored in the memory are executed by the processor, the receiving device performs the steps of the method according to any one of claims 1 to 7, and reports the human-machine interface data and the continuous audio stream corresponding to each target slave device to the host through the USB interface circuit.

9. A wireless input device, comprising a human-machine interface input unit, an audio acquisition unit, a radio frequency transceiver circuit, a processor, and a memory, characterized in that, When the instructions stored in the memory are executed by the processor, the wireless input device, as a target slave device, performs the steps of the method of any one of claims 1 to 7 executed by the target slave device.

10. A wireless communication system, characterized in that, It includes the receiving device as described in claim 8 and N slave devices, where N ≥ 2, and at least two of the N slave devices are the wireless input devices as described in claim 9.

Images