IP Library Granted Patent US 11,638,238
Granted Patent B2
US 11,638,238 · App. 17/139,656 · Granted Apr 25, 2023

Trigger frame based method and device for communications

Inventors: Liwen Chu (San Ramon, CA); Rui Cao (Sunnyvale, CA); Sudhir Srinivasa (Los Gatos, CA); Hongyuan Zhang (Fremont, CA); Young Hoon Kwon (Laguna Niguel, CA); Hui-Ling Lou (Sunnyvale, CA)
Assignee: NXP USA, Inc.
H04W72/0406
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,638,238
App. No.
17/139,656
Granted
Apr 25, 2023
Kind
B2
Abstract

Embodiments of a method and an apparatus for multi-link data transmission are disclosed. In an embodiment, a method for communications involves at a first device, transmitting, to a second device, a trigger frame that solicits at least one Physical layer Protocol Data Unit (PPDU) for uplink transmission, wherein the trigger frame includes a standard-compatible common info field that includes a trigger type field and a standard-compatible user info list field that includes at least one user info field, wherein the trigger frame includes a solicited Trigger-Based (TB) type indicator in a field in the trigger frame other than the trigger type field, and receiving, at the first device, at least one PPDU from the second device in response to the solicited TB type indicator that was transmitted in the trigger frame by the first device.

Claims (48)

1. A method for communications, the method comprising:

at a first device, transmitting, to a second device, a trigger frame that solicits at least one Physical layer Protocol Data Unit (PPDU) for uplink transmission,

wherein the trigger frame includes a standard-compatible common info field that includes a trigger type field and a standard-compatible user info list field that includes at least one user info field,

wherein the trigger frame includes a solicited Trigger-Based (TB) type indicator in a field in the trigger frame other than the trigger type field; and

receiving, at the first device, at least one PPDU from the second device in response to the solicited TB type indicator that was transmitted in the trigger frame by the first device.

2. The method of claim 1 , wherein the trigger frame uses a High-Efficiency (HE) trigger frame format.

3. The method of claim 2 , wherein a reserved field of the standard-compatible common info field indicates that the first device solicits an Extremely High Throughput (EHT) TB PPDU.

4. The method of claim 2 , wherein a specific association identifier (AID) value of an AID subfield of the standard-compatible user info field announces solicited PPDU formats.

5. The method of claim 4 ,

wherein the standard-compatible user info field with the specific AID value of the AID12 subfield is used to carry common information for multiple solicited devices;

wherein, the specific AID value of the AID12 subfield is 2007; and

wherein, an uplink (UL) High Efficiency (HE) Signal-A2 (UL HE-SIG-A2) Reserved subfield is used to carry common information different from a reserved value for multiple solicited devices.

6. The method of claim 5 ,

wherein the standard-compatible user info field with the specific AID value of the AID12 subfield carries an Extremely High Throughput (EHT) signal (SIG) value of the solicited EHT TB PPDU.

7. The method of claim 2 ,

wherein an uplink (UL) High Efficiency (HE) Signal-A2 (UL HE-SIG-A2) Reserved subfield of the standard-compatible common info field announces PPDU formats.

8. The method of claim 1 ,

wherein the standard-compatible user info field comprises a Resource Unit (RU) allocation that uses 9-bits for signaling at least one of a one RU and multiple RUs for the second device(s).

9. The method of claim 8 ,

wherein 1-bit of the 9-bits indicates whether the RU is in at least one of a primary 160 MHz (MegaHertz) channel and a secondary 160 MHz channel if the solicited PPDU is more than 160 MHz.

10. The method of claim 8 ,

wherein 1-bit of the 9-bits indicates whether the RU is in at least one of a primary 80 MHz (MegaHertz) channel and a secondary 80 MHz channel; and

wherein, if the RU is in the secondary 160 MHz channel, a location infrequency of the primary 80 MHz channel and the secondary 80 MHz channel is the same as a location of the primary 80 MHz channel and the secondary 80 MHz channel of the primary 160 MHz channel.

11. The method of claim 8 ,

wherein 1-bit of the 9-bits indicates whether a wider RU is in at least one of the primary 160 MHz (MegaHertz) channel and the secondary 160 MHz channel if multiple RUs for a single device covering at least one of the primary 160 MHz channel and the secondary 160 MHz channel are allocated to the single device.

12. The method of claim 8 ,

wherein 1-bit of the 9-bits indicates whether a wider RU is in at least one of the primary 80 MHz (MegaHertz) channel and the secondary 80 MHz channel if multiple RUs for the single device covering at least one of the primary 80 MHz channel and the secondary 80 MHz channel are allocated to the single device.

13. The method of claim 1 ,

wherein if an HE TB PPDU and a TB PPDU other than the HE TB PPDU are solicited by the trigger frame, the standard-compatible common info field announces common information for the HE TB PPDU and the standard-compatible user info field with a specific association identifier (AID) value of an AID12 subfield announces common information for the TB PPDU other than the HE TB PPDU.

14. The method of claim 1 ,

wherein if multiple TB PPDUs with different TB types are solicited by the Trigger frame, the standard-compatible common info field announces the frequency location if different TB types are present.

15. The method of claim 1 ,

wherein if multiple TB PPDUs with different TB types are solicited by the trigger frame, the standard-compatible user info field with a specific association identifier (AID) value of an AID12 subfield that solicits the TB PPDU from the second device with Extremely High Throughput (EHT) TB type is placed before the standard-compatible user info field with the specific AID12 value that solicits TB PPDU from second devices with next-generation (NG) EHT TB type.

16. A first device, the first device comprising:

a processor configured to:

transmit, to a second device, a trigger frame that solicits at least one Physical layer Protocol Data Unit (PPDU) for uplink transmission,

wherein the trigger frame includes a standard-compatible common info field that includes a trigger type field and a standard-compatible user info list field that includes at least one user info field,

wherein the trigger frame includes a solicited Trigger-Based (TB) type indicator in a field in the trigger frame other than the trigger type field; and

receive at least one PPDU from the second device in response to the solicited TB type indicator that was transmitted in the trigger frame by the first device.

17. A method for multi-link communications, the method comprising:

at a first device, formatting a trigger frame that solicits at least one of a Trigger-Based (TB) Aggregated-Physical layer Protocol Data Unit (PPDU) and a PPDU for uplink transmission,

wherein the trigger frame includes a standard-compatible common info field for a specific TB type and a standard-compatible user info list field for a specific TB type,

wherein the trigger frame includes a solicited Trigger-Based (TB) type indicator in a field in the trigger frame other than the trigger type field;

transmitting, to a second device, the trigger frame that solicits at least one of the TB A-PPDU (Aggregated-PPDU) and the PPDU for uplink transmission; and

receiving, at the first device, at least one PPDU from the second device in response to the solicited TB type indicator that was transmitted in the trigger frame by the first device.

18. The method of claim 17 , wherein formatting the trigger frame includes using an Extremely High Throughput (EHT) trigger frame format.

19. The method of claim 17 , wherein formatting the trigger frame includes reusing a HE trigger frame format.

20. The method of claim 17 , wherein formatting the trigger frame includes using a cascaded trigger frame format.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 22, 2021
From: CHU, LIWEN; CAO, RUI; SRINIVASA, SUDHIR; ZHANG, HONGYUAN; KWON, YOUNG HOON; LOU, HUI-LING
To: NXP USA, INC.
Reel/Frame 056006/0001 →
Continuity (8)
Provisional Application 62957174 · Jan 4, 2020
Provisional Application 62980213 · Feb 22, 2020
Provisional Application 62984562 · Mar 3, 2020
Provisional Application 63033776 · Jun 2, 2020
Provisional Application 63048699 · Jul 7, 2020
Provisional Application 63075364 · Sep 8, 2020
Provisional Application 63023226 · May 11, 2020
Related Publication 20210227529A1 · Jul 22, 2021
Cited By (1)
US 12,206,533