EP3908040B1 - Apparatuses and methods for resource unit (ru) allocation signaling to support trigger-based physical layer protocol data unit (tb ppdu) with multi-ru - Google Patents
Apparatuses and methods for resource unit (ru) allocation signaling to support trigger-based physical layer protocol data unit (tb ppdu) with multi-ru Download PDFInfo
- Publication number
- EP3908040B1 EP3908040B1 EP21170846.6A EP21170846A EP3908040B1 EP 3908040 B1 EP3908040 B1 EP 3908040B1 EP 21170846 A EP21170846 A EP 21170846A EP 3908040 B1 EP3908040 B1 EP 3908040B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- subfield
- ppdu
- allocation subfield
- allocation
- rus
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims description 29
- 230000011664 signaling Effects 0.000 title description 15
- 238000004891 communication Methods 0.000 claims description 23
- 230000005540 biological transmission Effects 0.000 claims description 20
- 230000004044 response Effects 0.000 claims description 12
- 238000012545 processing Methods 0.000 description 18
- 238000010586 diagram Methods 0.000 description 14
- 238000005516 engineering process Methods 0.000 description 10
- 238000006243 chemical reaction Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 230000001960 triggered effect Effects 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000013515 script Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000008094 contradictory effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000012938 design process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 239000013598 vector Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W28/18—Negotiating wireless communication parameters
- H04W28/20—Negotiating bandwidth
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0091—Signaling for the administration of the divided path
- H04L5/0094—Indication of how sub-channels of the path are allocated
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0446—Resources in time domain, e.g. slots or frames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/02—Selection of wireless resources by user or terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
Definitions
- the application generally relates to wireless communications, and more particularly, to apparatuses and methods for Resource Unit (RU) allocation signaling to support Trigger-Based Physical layer Protocol Data Unit (TB PPDU) with multi-RU.
- RU Resource Unit
- TB PPDU Trigger-Based Physical layer Protocol Data Unit
- Wi-Fi Wireless-Fidelity
- WLAN Wireless Local Area Network
- IEEE 802.11 has commercialized or developed various technological standards since an initial WLAN technology is supported using frequencies of 2.4 GHz.
- IEEE 802.11ac supports Multi-User (MU) transmission using spatial degrees of freedom via a MU-Multiple Input-Multiple-Output (MU-MIMO) scheme in a downlink (DL) direction from an Access Point (AP) to Stations (STAs).
- MU-MIMO MU-Multiple Input-Multiple-Output
- DL downlink
- AP Access Point
- STAs Stations
- IEEE 802.11ax uses both Orthogonal Frequency Division Multiple Access (OFDMA) and/or MU-MIMO in both DL and uplink (UL) directions. That is, in addition to supporting frequency and spatial multiplexing from an AP to multiple STAs, transmissions from multiple STAs to the AP are also supported in IEEE 802.11ax.
- OFDMA Orthogonal Frequency Division Multiple Access
- UL uplink
- a Resource Unit refers to a group of 78.125 KHz bandwidth subcarriers (tones) used in both DL and UL transmissions for a single STA, and a MU PPDU may carry multiple RUs, allowing multiple users to access an AP simultaneously and efficiently.
- IEEE 802.11be it has been agreed among IEEE members that multiple RUs may be allocated to a single STA in both DL and UL transmissions.
- the current IEEE 802.11ax specification only defines the usage scenario of RU allocation signaling for an EHT Physical layer Protocol Data Unit (PPDU) sent to multiple STAs (i.e., DL transmission), and does not define the usage scenario of RU allocation signaling for EHT Trigger-Based (TB) PPDU with multiple RUs (i.e., UL transmission).
- PPDU Physical layer Protocol Data Unit
- TB EHT Trigger-Based
- a technique to support 320 MHz operating bandwidth indicates operations by extremely high throughput (EHT) devices on an operating bandwidth, including devices in a basic service set (BSS) supporting the use of a 320 MHz channel.
- the supported functionality may include extensions to flexibility and support rules, structures, and signaling using legacy fields, frames, and features.
- the supported functionality may include channel sensing and reporting, such as per-channel network allocation vectors (NAVs) for the sub-channels of the operating bandwidth.
- a device may identify an operating mode for an operating bandwidth and determine a value for a bandwidth query report (BQR) or a target wake time (TWT) element. The device may check multiple NAVs for sub-channels of the operating bandwidth.
- the operating bandwidth may span concurrent operations on traditional Wi-Fi frequency bands including the 2.4 and 5 GHz bands as well as the 6 GHz band.
- a wireless communication terminal operating as a Station comprises a wireless transceiver and a controller.
- the wireless transceiver is configured to perform wireless transmission and reception to and from an Access Point (AP).
- AP Access Point
- the controller is coupled to the wireless transceiver, and configured to receive a trigger frame comprising a first Resource Unit (RU) Allocation subfield which has one bit to indicate support of 320 MHz bandwidth from the AP via the wireless transceiver, determine a combination of RUs to be used in a Trigger-Based Physical layer Protocol Data Unit (TB PPDU) according to the first RU Allocation subfield, and send the TB PPDU for Uplink (UL) data transmission to the AP via the wireless transceiver in response to the trigger frame, wherein the trigger frame further comprises a subfield for indicating a number of the RUs to be used in the TB PPDU, and a second RU Allocation subfield with the same format as the first RU Allocation subfield; and each of the first RU Allocation subfield and the second RU Allocation subfield indicates a respective one of the RUs to be used in the TB PPDU.
- RU Resource Unit
- a method executed by a wireless communication terminal operating as an STA comprises the following steps: receiving a trigger frame comprising a first RU Allocation subfield which has one bit to indicate support of 320 MHz bandwidth from an AP; determining a combination of RUs to be used in a TB PPDU according to the first RU Allocation subfield; and sending the TB PPDU for UL data transmission to the AP in response to the trigger frame, wherein the trigger frame further comprises a subfield for indicating a number of the RUs to be used in the TB PPDU, and a second RU Allocation subfield with the same format as the first RU Allocation subfield; and each of the first RU Allocation subfield and the second RU Allocation subfield indicates a respective one of the RUs to be used in the TB PPDU.
- a wireless communication terminal operating as an Access Point comprises a wireless transceiver and a controller.
- the wireless transceiver is configured to perform wireless transmission and reception to and from a Station (STA).
- STA Station
- the controller is coupled to the wireless transceiver, and configured to send a trigger frame comprising a first RU Allocation subfield which has one bit to indicate support of 320 MHz bandwidth to an STA, and receive a TB PPDU from the STA in response to the trigger frame; wherein the TB PPDU comprises a combination of RUs as indicated by the first RU Allocation subfield, wherein the trigger frame further comprises a subfield for indicating a number of the RUs to be used in the TB PPDU, and a second RU Allocation subfield with the same format as the first RU Allocation subfield; and each of the first RU Allocation subfield and the second RU Allocation subfield indicates a respective one of the RUs to be used in the TB PPDU.
- a method executed by a wireless communication device operating as an AP comprises the following steps: sending a trigger frame comprising a first RU Allocation subfield which has one bit to indicate support of 320 MHz bandwidth to an STA; and receiving a TB PPDU from the STA in response to the trigger frame; wherein the TB PPDU comprises a combination of RUs as indicated by the first RU Allocation subfield, wherein the trigger frame further comprises a subfield for indicating a number of the RUs to be used in the TB PPDU, and a second RU Allocation subfield with the same format as the first RU Allocation subfield; and each of the first RU Allocation subfield and the second RU Allocation subfield indicates a respective one of the RUs to be used in the TB PPDU.
- the trigger frame is an Extremely-High Throughput (EHT) trigger frame and the TB PPDU is an EHT TB PPDU in compliance with Institute of Electrical and Electronics Engineers (IEEE) 802.11be standard.
- EHT Extremely-High Throughput
- IEEE Institute of Electrical and Electronics Engineers
- the first RU Allocation subfield is 9 bits long, and the bit to indicate support of 320 MHz bandwidth is introduced as the first bit of the first RU Allocation subfield.
- the third to ninth bits of the first RU Allocation subfield represent a value greater than 68 to indicate the combination of the RUs for EHT.
- the trigger frame further comprises a Subtype subfield and a Trigger Type subfield, and one of the Subtype subfield and the Trigger Type subfield is set to a value for EHT identification.
- Fig. 1 is a block diagram of a wireless communication system.
- the wireless communication system 100 includes an Access Point (AP) 110 and a plurality of stations (STAs) 120-140.
- the AP 110 is a wireless communication device compatible with IEEE 802.11 standards to provide and manage the access to the wireless medium for the STAs 120-140.
- the AP 110 has a coverage area 1100 such that STAs 120-140 within that area are within range of the AP 110.
- the STAs 120-140 scatter throughout the coverage area 1100.
- Each of the STAs 120-140 may be stationary, mobile, or a combination thereof.
- the AP 110 may be an Extremely-High Throughput (EHT) AP or an EHT STA operating in the AP mode, which is compatible with the IEEE 802.11be standard.
- EHT Extremely-High Throughput
- the AP 110 may be an AP or an AP-mode STA which is compatible with any IEEE 802.11 standard later than 802.11be.
- Each of the STAs 120-140 may be a mobile phone (e.g., feature phone or smartphone), a panel Personal Computer (PC), a laptop computer, a desktop computer, a smart TV, or any wireless communication terminal, as long as it is compatible with the same IEEE 802.11 standard as the AP 110.
- Each of the STAs 120-140 may operate in the non-AP mode to associate and communicate with the AP 110 for transmitting or receiving data in uplink (UL) or downlink (DL) PPDUs with multi-RU.
- UL uplink
- DL downlink
- each of the STAs 120-140 is triggered by the AP 110 to send uplink data in a Trigger-Based Physical layer Protocol Data Unit (TB PPDU) in which multiple RUs are allocated to a single STA.
- TB PPDU Trigger-Based Physical layer Protocol Data Unit
- the AP 110 sends a trigger frame to the STAs 120-140, and the trigger frame includes an RU Allocation subfield in which an additional bit is newly introduced to indicate support of 320 MHz bandwidth (i.e., the RU allocation applies to EHT).
- the STA 120/130/140 determines the combination of RUs to be used in a TB PPDU according to the RU Allocation subfield, and send the TB PPDU for UL data transmission to the AP 110, wherein the trigger frame further comprises a subfield for indicating a number of the RUs to be used in the TB PPDU, and a second RU Allocation subfield with the same format as the first RU Allocation subfield; and each of the first RU Allocation subfield and the second RU Allocation subfield indicates a respective one of the RUs to be used in the TB PPDU.
- an additional value for EHT identification may be redefined for the Subtype subfield and/or the Trigger Type subfield of the trigger frame.
- Fig. 2 is a block diagram illustrating the STA 120/130/140 and the AP 110.
- the STA 120/130/140 may include a wireless transceiver 10, a controller 20, a storage device 30, a display device 40, and an Input/Output (I/O) device 50.
- a wireless transceiver 10 the STA 120/130/140 may include a wireless transceiver 10, a controller 20, a storage device 30, a display device 40, and an Input/Output (I/O) device 50.
- I/O Input/Output
- the wireless transceiver 10 is configured to perform wireless transmission and reception to and from the AP 110 or an AP mode STA.
- the wireless transceiver 10 may be a Wi-Fi chip.
- the wireless transceiver 10 may include a baseband processing device 11, a Radio Frequency (RF) device 12, and antenna 13, wherein the antenna 13 may include an antenna array for UL/DL Multi-User Multiple Input-Multiple-Output (MU-MIMO).
- RF Radio Frequency
- the baseband processing device 11 is configured to perform baseband signal processing, such as Analog-to-Digital Conversion (ADC)/Digital-to-Analog Conversion (DAC), gain adjusting, modulation/demodulation, encoding/decoding, and so on.
- the baseband processing device 11 may contain multiple hardware components, such as a baseband processor, to perform the baseband signal processing.
- the RF device 12 may receive RF wireless signals via the antenna 13, convert the received RF wireless signals to baseband signals, which are processed by the baseband processing device 11, or receive baseband signals from the baseband processing device 11 and convert the received baseband signals to RF wireless signals, which are later transmitted via the antenna 13.
- the RF device 12 may also contain multiple hardware devices to perform radio frequency conversion.
- the RF device 12 may include a mixer to multiply the baseband signals with a carrier oscillated in the radio frequency of the supported cellular technologies, wherein the radio frequency may be 2.4GHz, 5GHz, or 60GHz utilized in the Wi-Fi technology, or any radio frequency utilized in the future evolution of the Wi-Fi technology.
- the controller 20 may be a general-purpose processor, a Micro Control Unit (MCU), an application processor, a Digital Signal Processor (DSP), or the like, which includes various circuits for providing the functions of data processing and computing, controlling the wireless transceiver 10 for wireless communications with the AP 110, storing and retrieving data (e.g., program code) to and from the storage device 30, sending a series of frame data (e.g. representing text messages, graphics, images, etc.) to the display device 40, and receiving user inputs or outputting signals via the I/O device 50.
- data e.g., program code
- frame data e.g. representing text messages, graphics, images, etc.
- the controller 20 coordinates the aforementioned operations of the wireless transceiver 10, the storage device 30, the display device 40, and the I/O device 50 for performing the method of the present application.
- the controller 20 may be incorporated into the baseband processing device 11, to serve as a baseband processor.
- the storage device 30 may be a non-transitory machine-readable storage medium, including a memory, such as a FLASH memory or a Non-Volatile Random Access Memory (NVRAM), or a magnetic storage device, such as a hard disk or a magnetic tape, or an optical disc, or any combination thereof for storing data, instructions, and/or program code of applications, the Wi-Fi protocol (of the IEEE 802.11be or another protocol version), and/or the method of the present application.
- NVRAM Non-Volatile Random Access Memory
- the display device 40 may be a Liquid-Crystal Display (LCD), a Light-Emitting Diode (LED) display, an Organic LED (OLED) display, or an Electronic Paper Display (EPD), etc., for providing a display function.
- the display device 40 may further include one or more touch sensors for sensing touches, contacts, or approximations of objects, such as fingers or styluses.
- the I/O device 50 may include one or more buttons, a keyboard, a mouse, a touch pad, a video camera, a microphone, and/or a speaker, etc., to serve as the Man-Machine Interface (MMI) for interaction with users.
- MMI Man-Machine Interface
- the AP 110 may include a wireless transceiver 60, a controller 70, a storage device 80, and an I/O device 90.
- the wireless transceiver 60 is configured to perform wireless transmission and reception to and from the STAs 120-140.
- the wireless transceiver 60 may be a Wi-Fi chip.
- the wireless transceiver 60 may include a baseband processing device 61, an RF device 62, and antenna 63, wherein the antenna 63 may include an antenna array for UL/DL MU-MIMO.
- the baseband processing device 61 is configured to perform baseband signal processing, such as ADC/DAC, gain adjusting, modulation/demodulation, encoding/decoding, and so on.
- the baseband processing device 61 may contain multiple hardware components, such as a baseband processor, to perform the baseband signal processing.
- the RF device 62 may receive RF wireless signals via the antenna 63, convert the received RF wireless signals to baseband signals, which are processed by the baseband processing device 61, or receive baseband signals from the baseband processing device 61 and convert the received baseband signals to RF wireless signals, which are later transmitted via the antenna 63.
- the RF device 62 may also contain multiple hardware devices to perform radio frequency conversion.
- the RF device 62 may include a mixer to multiply the baseband signals with a carrier oscillated in the radio frequency of the supported cellular technologies, wherein the radio frequency may be 2.4GHz, 5GHz, or 60GHz utilized in the Wi-Fi technology, or any radio frequency utilized in the future evolution of the Wi-Fi technology.
- the controller 70 may be a general-purpose processor, an MCU, an application processor, a DSP, or the like, which includes various circuits for providing the functions of data processing and computing, controlling the wireless transceiver 60 for wireless communications with the STAs 120-140, storing and retrieving data (e.g., program code) to and from the storage device 80, and receiving user inputs or outputting signals via the I/O device 90.
- data e.g., program code
- the controller 70 coordinates the aforementioned operations of the wireless transceiver 60, the storage device 80, and the I/O device 90 for performing the method of the present application.
- the controller 70 may be incorporated into the baseband processing device 61, to serve as a baseband processor.
- the circuits of the controllers 20 and 70 may include transistors that are configured in such a way as to control the operation of the circuits in accordance with the functions and operations described herein.
- the specific structure or interconnections of the transistors may be determined by a compiler, such as a Register Transfer Language (RTL) compiler.
- RTL compilers may be operated by a processor upon scripts that closely resemble assembly language code, to compile the script into a form that is used for the layout or fabrication of the ultimate circuitry. Indeed, RTL is well known for its role and use in the facilitation of the design process of electronic and digital systems.
- the storage device 80 may be a non-transitory machine-readable storage medium, including a memory, such as a FLASH memory or a NVRAM, or a magnetic storage device, such as a hard disk or a magnetic tape, or an optical disc, or any combination thereof for storing data, instructions, and/or program code of applications, Wi-Fi protocol (of the IEEE 802.11be or another protocol version), and/or the method of the present application.
- a memory such as a FLASH memory or a NVRAM
- a magnetic storage device such as a hard disk or a magnetic tape, or an optical disc, or any combination thereof for storing data, instructions, and/or program code of applications, Wi-Fi protocol (of the IEEE 802.11be or another protocol version), and/or the method of the present application.
- the I/O device 90 may include one or more buttons, a keyboard, a touch pad, a display device (e.g., LCD, LED, OLED, or EPD, etc.), a light emitting device, a microphone, and/or a speaker, etc., to serve as the MMI for interaction with users.
- a display device e.g., LCD, LED, OLED, or EPD, etc.
- a light emitting device e.g., a microphone, and/or a speaker, etc.
- the components described in Fig. 2 are for illustrative purposes only and are not intended to limit the scope of the application.
- the AP 110 or the STA 120/130/140 may include more components, such as another wireless transceiver for providing telecommunication services, a Global Positioning System (GPS) device for use of some location-based services or applications, and/or a battery for powering the other components, etc.
- the AP 110 or the STA 120/130/140 may include fewer components.
- the STA 120/130/140 may not include the display device 40 and/or the I/O device 50.
- Fig. 3 is a schematic diagram illustrating the format of an EHT trigger frame.
- a trigger frame is used by an AP (or an AP mode STA) to allocate resources for and solicit one or more EHT TB PPDU transmissions.
- the trigger frame includes the information required by the responding STA to send an EHT TB PPDU.
- an EHT trigger frame may include a Media Access Control (MAC) header, a Common Info field, a list of User Info fields, padding bit(s), and a Frame Check Sequence (FCS) field.
- MAC Media Access Control
- Common Info field a list of User Info fields
- FCS Frame Check Sequence
- the MAC header is consisted of a Frame Control field, a Duration field, a Receiver Address (RA) field, and a TA field.
- the Frame Control field may include control information required for frame transmission/reception.
- the Duration field may be set to a time for transmitting the corresponding frame.
- the RA field may indicate the address(es) of the receiver STA(s). For example, the RA field may be set to a broadcast group address.
- the TA field may indicate the address of the AP/STA transmitting the EHT trigger frame.
- the Common Info field may include the common information for all the triggered STAs, while each User Info field may include the information dedicated for a respective triggered STA.
- the trigger frame described herein may apply to EHT by defining a new value for EHT identification in the Subtype subfield of the Frame Control field or in the Trigger Type subfield of the Common Info field.
- the valid Control Type value and Subtype value combinations may be defined as follows in Table 1, and the Trigger Type subfield encoding may be defined as follows in Table 2.
- Table. 1 Control Type value Control Type description Subtype value Subtype description 01 Control 0000-0001 Reserved 01 Control 0010 Trigger 01 Control 0101 VHT/HE NDP Announcement 01 Control 1010 EHT identification Table 2.
- Trigger Type value Trigger name variant 0 Basic 1 Beamforming Report Poll (BFRP) 2 MLT-BAR 3 MU-RTS 4 Buffer Status Report Poll (BSRP) 5 GCR MU-BAR 6 Bandwidth Query Report Poll (BQRP) 7 NDP Feedback Report Poll (NFRP) 8 EHT identification 9-15 Reserved
- the EHT trigger frame described herein is enhanced for RU allocation signaling to support EHT TB PPDU with multi-RU, by modifying the RU Allocation subfield format of the User Info field. Details of such improvement will be described later in the following figures.
- Fig. 4 is a schematic diagram illustrating the format of the User Info field of an EHT trigger frame.
- the RU Allocation subfield of the User Info field is 9 bits long, in contrast to the 8-bit long RU Allocation subfield of the User Info field in a conventional trigger frame (e.g., an HE trigger frame).
- a conventional trigger frame e.g., an HE trigger frame
- one additional bit is newly introduced as the first bit (i.e., B0) in the RU Allocation subfield to indicate support of 320 MHz bandwidth in EHT.
- B0 of the RU Allocation subfield is set to 0 to indicate that the RU allocation applies to the primary 160 MHz channel of the 320 MHz bandwidth, and is set to 1 to indicate that the RU allocation applies to the secondary 160 MHz channel of the 320 MHz bandwidth.
- the second bit (i.e., B1) of the RU Allocation subfield indicates whether the RU allocation applies to the primary 80 MHz channel of the 320 MHz bandwidth.
- B1 of the RU Allocation subfield is set to 0 to indicate that the RU allocation applies to the primary 80 MHz channel, and is set to 1 to indicate that the RU allocation applies to the secondary 80 MHz channel.
- Fig. 5 is a schematic diagram illustrating the channel arrangement of a 320 MHz bandwidth.
- the 320 MHz bandwidth is divided into four continuous 80 MHz channels.
- the 160 MHz channel consisting of the first two 80 MHz channels may be configured as the primary 160 MHz channel for EHT, and the 160 MHz channel consisting of the last two 80 MHz channels may be configured as the secondary 160 MHz channel for EHT.
- first 80 MHz channel in the first primary 160 MHz channel may be configured as the primary 80 MHz channel, while the other 80 MHz channels may be configured as the secondary 80 MHz channels.
- the channel arrangement described in Fig 5 is for illustrative purposes only and is not intended to limit the scope of the application.
- the 160 MHz channel consisting of the last two 80 MHz channels may be configured as the primary 160 MHz channel for EHT
- the 160 MHz channel consisting of the first two 80 MHz channels may be configured as the secondary 160 MHz channel for EHT.
- any 80 MHz channel other than the first 80 MHz channel may be configured as the primary 80 MHz channel.
- the third to ninth bits (i.e., B2 to B8) of the RU Allocation subfield represent a value which may be set to be greater than 68 to indicate the combination of the RUs for EHT.
- the values 0-68 have been defined for legacy protocol versions in the IEEE 802.11ax standard. Due to the bandwidth increase from 160 MHz to 320 MHz in IEEE 802.11be, new values are proposed herein for EHT as follows in Tables 3 and 4. Table.
- brackets in Table 3 refer to the RUs in the exemplary RU allocation for EHT as shown in Fig. 6
- the numbers in the brackets in Table 4 refer to the RUs in the exemplary RU allocation for EHT as shown in Fig. 7 .
- 7 bits (i.e., B2 to B8) of the RU Allocation subfield can represent a total number of 128 combinations of RUs, in which 69 combinations of RUs are defined for legacy protocol versions, and thus, there are only 59 combinations of RUs left to be defined for adapting to EHT. In case there may be more than 59 combinations of RUs for adapting to EHT in the future, only one RU Allocation subfield may not be enough to represent the complete combinations of RUs in EHT. In response to such consideration, the present application proposes another solution as follows.
- Fig. 8 is a schematic diagram illustrating the format of the User Info field of an EHT trigger frame according to an embodiment of the application.
- the User Info field is extended to include additional subfields, such as a Num of RUs subfield, and one or more RU Allocation subfields.
- the Num of RUs subfield indicates the number of RUs to be used in a TB PPDU, and correspondingly, there are the same number of RU Allocation subfields in the User Info field.
- the Num of RUs subfield may be 3 bits long, and indicate one RU if it's set to "000" (in binary notation), or indicate two RUs if it's set to "001".
- Each RU Allocation subfield of the User Info field is 9 bits long, in contrast to the 8-bit long RU Allocation subfield of the User Info field in a conventional trigger frame (e.g., an HE trigger frame). Similar to the embodiment of Fig. 4 , one additional bit is newly introduced as the first bit (i.e., B0) in the RU Allocation subfield to indicate support of 320 MHz bandwidth in EHT.
- the Num of RUs subfield is set to "001" to indicate two RUs to be used in a TB PPDU
- the first RU Allocation subfield is set to "000001000” (from B8 to B0 in binary notation)
- the second RU Allocation subfield is set to "010011000”
- the combination of RUs denoted with dark background in Fig. 9 may be determined.
- Fig. 10 is a flow chart illustrating the method for RU allocation signaling to support TB PPDU with multi-RU by an STA according to an embodiment of the application.
- the method for RU allocation signaling to support TB PPDU with multi-RU may be applied to and executed by an STA (e.g., the STA 120/130/140) supporting use of 320 MHz bandwidth.
- an STA e.g., the STA 120/130/140
- the STA receives a trigger frame including a first RU Allocation subfield which has one bit to indicate support of 320 MHz bandwidth from an AP (step S1010).
- the STA determines a combination of RUs to be used in a TB PPDU according to the first RU Allocation subfield (step S 1020).
- the STA sends the TB PPDU for UL data transmission to the AP in response to the trigger frame (step S1030).
- the trigger frame may be an EHT trigger frame and the TB PPDU is an EHT TB PPDU in compliance with IEEE 802.11be standard or any future evolution of the IEEE 802.11be.
- the trigger frame may further include a Subtype subfield and a Trigger Type subfield, and one or both of the Subtype subfield and the Trigger Type subfield may be set to a value for EHT identification.
- the first RU Allocation subfield may be 9 bits long, and the bit to indicate support of 320 MHz bandwidth may be introduced as the first bit of the first RU Allocation subfield, while the third to ninth bits of the first RU Allocation subfield represent a value greater than 68 to indicate the combination of the RUs for EHT.
- only one RU Allocation subfield may be used in the User Info field of the trigger frame to indicate the combination of the RUs to be used in the TB PPDU, if the third to ninth bits of the first RU Allocation subfield are enough to represent the complete combinations of RUs for EHT.
- two or more RU Allocation subfields may be used in the User Info field of the trigger frame to indicate the combination of the RUs to be used in the TB PPDU, if the third to ninth bits of only one RU Allocation subfield are not enough to represent the complete combinations of RUs for EHT.
- the trigger frame further includes a Num of RUs subfield for indicating the number of the RUs to be used in the TB PPDU, and a second RU Allocation subfield with the same format as the first RU Allocation subfield, wherein each of the first RU Allocation subfield and the second RU Allocation subfield indicates a respective one of the RUs to be used in the TB PPDU.
- Fig. 11 is a flow chart illustrating the method for RU allocation signaling to support TB PPDU with multi-RU by an AP according to an embodiment of the application.
- the method for RU allocation signaling to support TB PPDU with multi-RU may be applied to and executed by an AP (e.g., the AP 110 or an AP mode STA) supporting use of 320 MHz bandwidth.
- an AP e.g., the AP 110 or an AP mode STA
- the AP sends a trigger frame including a first RU Allocation subfield which has one bit to indicate support of 320 MHz bandwidth to an STA (step S1110).
- the AP receives a TB PPDU from the STA in response to the trigger frame, wherein the TB PPDU includes a combination of RUs as indicated by the first RU Allocation subfield (step S1120).
- the present application realizes RU allocation signaling to support EHT TB PPDU with multi-RU, by introducing an additional bit in the RU Allocation subfield of a trigger frame to indicate support of 320 MHz bandwidth and defining a new value for EHT identification in the Subtype subfield and/or the Trigger Type subfield of the trigger frame.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Quality & Reliability (AREA)
- Mobile Radio Communication Systems (AREA)
- Developing Agents For Electrophotography (AREA)
Description
- This Application claims priority of
U.S. Provisional Application No. 63/020,582, filed on May 6, 2020 - The application generally relates to wireless communications, and more particularly, to apparatuses and methods for Resource Unit (RU) allocation signaling to support Trigger-Based Physical layer Protocol Data Unit (TB PPDU) with multi-RU.
- With growing demand for ubiquitous computing and networking, various wireless technologies have been developed, including Wireless-Fidelity (Wi-Fi) which is a Wireless Local Area Network (WLAN) technology allowing mobile devices, such as a smartphone, a smart pad, a laptop computer, a portable multimedia player, an embedded apparatus, or the like, to obtain wireless services in a frequency band of 2.4 GHz, 5 GHz or 60 GHz.
- The Institute of Electrical and Electronics Engineers (IEEE) 802.11 has commercialized or developed various technological standards since an initial WLAN technology is supported using frequencies of 2.4 GHz. For example, IEEE 802.11ac supports Multi-User (MU) transmission using spatial degrees of freedom via a MU-Multiple Input-Multiple-Output (MU-MIMO) scheme in a downlink (DL) direction from an Access Point (AP) to Stations (STAs). To improve the performance experienced by users of the aforementioned mobile devices, who demand high-capacity and high-rate services, IEEE 802.11ax has been proposed, which uses both Orthogonal Frequency Division Multiple Access (OFDMA) and/or MU-MIMO in both DL and uplink (UL) directions. That is, in addition to supporting frequency and spatial multiplexing from an AP to multiple STAs, transmissions from multiple STAs to the AP are also supported in IEEE 802.11ax.
- In IEEE 802.11ax, a Resource Unit (RU) refers to a group of 78.125 KHz bandwidth subcarriers (tones) used in both DL and UL transmissions for a single STA, and a MU PPDU may carry multiple RUs, allowing multiple users to access an AP simultaneously and efficiently. In IEEE 802.11be, it has been agreed among IEEE members that multiple RUs may be allocated to a single STA in both DL and UL transmissions. However, the current IEEE 802.11ax specification only defines the usage scenario of RU allocation signaling for an EHT Physical layer Protocol Data Unit (PPDU) sent to multiple STAs (i.e., DL transmission), and does not define the usage scenario of RU allocation signaling for EHT Trigger-Based (TB) PPDU with multiple RUs (i.e., UL transmission).
- In a relevant prior art, US Patent Application
US 2020/0015219 A1, published on January 9, 2020 , a technique to support 320 MHz operating bandwidth is provided. The technique indicates operations by extremely high throughput (EHT) devices on an operating bandwidth, including devices in a basic service set (BSS) supporting the use of a 320 MHz channel. The supported functionality may include extensions to flexibility and support rules, structures, and signaling using legacy fields, frames, and features. In addition, the supported functionality may include channel sensing and reporting, such as per-channel network allocation vectors (NAVs) for the sub-channels of the operating bandwidth. A device may identify an operating mode for an operating bandwidth and determine a value for a bandwidth query report (BQR) or a target wake time (TWT) element. The device may check multiple NAVs for sub-channels of the operating bandwidth. The operating bandwidth may span concurrent operations on traditional Wi-Fi frequency bands including the 2.4 and 5 GHz bands as well as the 6 GHz band. - Therefore, it is desirable to have a robust and feasible way of RU allocation signaling to support EHT TB PPDU with multi-RU.
- Wireless communication terminals and methods according to the invention are defined in the independent claims. The dependent claims define preferred embodiments thereof.
- In a first aspect of the application, a wireless communication terminal operating as a Station (STA) is provided. The wireless communication terminal comprises a wireless transceiver and a controller. The wireless transceiver is configured to perform wireless transmission and reception to and from an Access Point (AP). The controller is coupled to the wireless transceiver, and configured to receive a trigger frame comprising a first Resource Unit (RU) Allocation subfield which has one bit to indicate support of 320 MHz bandwidth from the AP via the wireless transceiver, determine a combination of RUs to be used in a Trigger-Based Physical layer Protocol Data Unit (TB PPDU) according to the first RU Allocation subfield, and send the TB PPDU for Uplink (UL) data transmission to the AP via the wireless transceiver in response to the trigger frame, wherein the trigger frame further comprises a subfield for indicating a number of the RUs to be used in the TB PPDU, and a second RU Allocation subfield with the same format as the first RU Allocation subfield; and each of the first RU Allocation subfield and the second RU Allocation subfield indicates a respective one of the RUs to be used in the TB PPDU.
- In a second aspect of the application, a method executed by a wireless communication terminal operating as an STA is provided. The method comprises the following steps: receiving a trigger frame comprising a first RU Allocation subfield which has one bit to indicate support of 320 MHz bandwidth from an AP; determining a combination of RUs to be used in a TB PPDU according to the first RU Allocation subfield; and sending the TB PPDU for UL data transmission to the AP in response to the trigger frame, wherein the trigger frame further comprises a subfield for indicating a number of the RUs to be used in the TB PPDU, and a second RU Allocation subfield with the same format as the first RU Allocation subfield; and each of the first RU Allocation subfield and the second RU Allocation subfield indicates a respective one of the RUs to be used in the TB PPDU.
- In a third aspect of the application, a wireless communication terminal operating as an Access Point (AP) is provided. The wireless communication terminal comprises a wireless transceiver and a controller. The wireless transceiver is configured to perform wireless transmission and reception to and from a Station (STA). The controller is coupled to the wireless transceiver, and configured to send a trigger frame comprising a first RU Allocation subfield which has one bit to indicate support of 320 MHz bandwidth to an STA, and receive a TB PPDU from the STA in response to the trigger frame; wherein the TB PPDU comprises a combination of RUs as indicated by the first RU Allocation subfield, wherein the trigger frame further comprises a subfield for indicating a number of the RUs to be used in the TB PPDU, and a second RU Allocation subfield with the same format as the first RU Allocation subfield; and each of the first RU Allocation subfield and the second RU Allocation subfield indicates a respective one of the RUs to be used in the TB PPDU.
- In a fourth aspect of the application, a method executed by a wireless communication device operating as an AP is provided. The method comprises the following steps: sending a trigger frame comprising a first RU Allocation subfield which has one bit to indicate support of 320 MHz bandwidth to an STA; and receiving a TB PPDU from the STA in response to the trigger frame; wherein the TB PPDU comprises a combination of RUs as indicated by the first RU Allocation subfield, wherein the trigger frame further comprises a subfield for indicating a number of the RUs to be used in the TB PPDU, and a second RU Allocation subfield with the same format as the first RU Allocation subfield; and each of the first RU Allocation subfield and the second RU Allocation subfield indicates a respective one of the RUs to be used in the TB PPDU.
- In a first implementation form of any one of the described aspects of the application, the trigger frame is an Extremely-High Throughput (EHT) trigger frame and the TB PPDU is an EHT TB PPDU in compliance with Institute of Electrical and Electronics Engineers (IEEE) 802.11be standard.
- In a second implementation form of any one of the described aspects of the application in combination with the first implementation form, the first RU Allocation subfield is 9 bits long, and the bit to indicate support of 320 MHz bandwidth is introduced as the first bit of the first RU Allocation subfield.
- In a third implementation form of any one of the described aspects of the application in combination with the second implementation form, the third to ninth bits of the first RU Allocation subfield represent a value greater than 68 to indicate the combination of the RUs for EHT.
- In a fourth implementation form of any one of the described aspects of the application in combination with the first implementation form, the trigger frame further comprises a Subtype subfield and a Trigger Type subfield, and one of the Subtype subfield and the Trigger Type subfield is set to a value for EHT identification.
- Other aspects and features of the present application will become apparent to those with ordinary skill in the art upon review of the following descriptions of specific embodiments of the apparatuses and methods for RU allocation signaling to support TB PPDU with multi-RU. Further to the combinations explicitly indicated above, the first to fourth implementation forms of any one of the described aspects of the application might also be combined in any other not contradicting way.
- The application can be more fully understood by reading the subsequent detailed description and examples with references made to the accompanying drawings, wherein:
-
Fig. 1 is a block diagram of a wireless communication system; -
Fig. 2 is a block diagram illustrating theSTA 120/130/140 and the AP 110; -
Fig. 3 is a schematic diagram illustrating the format of an EHT trigger frame; -
Fig. 4 is a schematic diagram illustrating the format of the User Info field of an EHT trigger frame; -
Fig. 5 is a schematic diagram illustrating the channel arrangement of a 320 MHz bandwidth; -
Figs. 6 and7 show schematic diagrams illustrating exemplary RU allocations for EHT; -
Fig. 8 is a schematic diagram illustrating the format of the User Info field of an EHT trigger frame according to an embodiment of the application; -
Fig. 9 is a schematic diagrams illustrating an exemplary RU allocation for EHT; -
Fig. 10 is a flow chart illustrating the method for RU allocation signaling to support TB PPDU with multi-RU by an STA according to an embodiment of the application; and -
Fig. 11 is a flow chart illustrating the method for RU allocation signaling to support TB PPDU with multi-RU by an AP according to an embodiment of the application. - The following description is made for the purpose of illustrating the general principles of the application and should not be taken in a limiting sense. It should be understood that the embodiments may be realized in software, hardware, firmware, or any combination thereof. The terms "comprises," "comprising," "includes" and/or "including," when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
-
Fig. 1 is a block diagram of a wireless communication system. - As shown in
Fig. 1 , thewireless communication system 100 includes an Access Point (AP) 110 and a plurality of stations (STAs) 120-140. The AP 110 is a wireless communication device compatible with IEEE 802.11 standards to provide and manage the access to the wireless medium for the STAs 120-140. The AP 110 has acoverage area 1100 such that STAs 120-140 within that area are within range of the AP 110. The STAs 120-140 scatter throughout thecoverage area 1100. Each of the STAs 120-140 may be stationary, mobile, or a combination thereof. - In one embodiment, not falling within the claims, the AP 110 may be an Extremely-High Throughput (EHT) AP or an EHT STA operating in the AP mode, which is compatible with the IEEE 802.11be standard.
- In another embodiment, not falling within the claims, the
AP 110 may be an AP or an AP-mode STA which is compatible with any IEEE 802.11 standard later than 802.11be. - Each of the STAs 120-140 may be a mobile phone (e.g., feature phone or smartphone), a panel Personal Computer (PC), a laptop computer, a desktop computer, a smart TV, or any wireless communication terminal, as long as it is compatible with the same IEEE 802.11 standard as the
AP 110. Each of the STAs 120-140 may operate in the non-AP mode to associate and communicate with theAP 110 for transmitting or receiving data in uplink (UL) or downlink (DL) PPDUs with multi-RU. - In accordance with one novel aspect, each of the STAs 120-140 is triggered by the
AP 110 to send uplink data in a Trigger-Based Physical layer Protocol Data Unit (TB PPDU) in which multiple RUs are allocated to a single STA. Specifically, theAP 110 sends a trigger frame to the STAs 120-140, and the trigger frame includes an RU Allocation subfield in which an additional bit is newly introduced to indicate support of 320 MHz bandwidth (i.e., the RU allocation applies to EHT). In response to the trigger frame, theSTA 120/130/140 determines the combination of RUs to be used in a TB PPDU according to the RU Allocation subfield, and send the TB PPDU for UL data transmission to theAP 110, wherein the trigger frame further comprises a subfield for indicating a number of the RUs to be used in the TB PPDU, and a second RU Allocation subfield with the same format as the first RU Allocation subfield; and each of the first RU Allocation subfield and the second RU Allocation subfield indicates a respective one of the RUs to be used in the TB PPDU. - In accordance with another novel aspect, an additional value for EHT identification may be redefined for the Subtype subfield and/or the Trigger Type subfield of the trigger frame.
-
Fig. 2 is a block diagram illustrating theSTA 120/130/140 and theAP 110. - As shown in
Fig. 2 , theSTA 120/130/140 may include awireless transceiver 10, acontroller 20, astorage device 30, adisplay device 40, and an Input/Output (I/O)device 50. - The
wireless transceiver 10 is configured to perform wireless transmission and reception to and from theAP 110 or an AP mode STA. For example, thewireless transceiver 10 may be a Wi-Fi chip. - Specifically, the
wireless transceiver 10 may include abaseband processing device 11, a Radio Frequency (RF)device 12, andantenna 13, wherein theantenna 13 may include an antenna array for UL/DL Multi-User Multiple Input-Multiple-Output (MU-MIMO). - The
baseband processing device 11 is configured to perform baseband signal processing, such as Analog-to-Digital Conversion (ADC)/Digital-to-Analog Conversion (DAC), gain adjusting, modulation/demodulation, encoding/decoding, and so on. Thebaseband processing device 11 may contain multiple hardware components, such as a baseband processor, to perform the baseband signal processing. - The
RF device 12 may receive RF wireless signals via theantenna 13, convert the received RF wireless signals to baseband signals, which are processed by thebaseband processing device 11, or receive baseband signals from thebaseband processing device 11 and convert the received baseband signals to RF wireless signals, which are later transmitted via theantenna 13. TheRF device 12 may also contain multiple hardware devices to perform radio frequency conversion. For example, theRF device 12 may include a mixer to multiply the baseband signals with a carrier oscillated in the radio frequency of the supported cellular technologies, wherein the radio frequency may be 2.4GHz, 5GHz, or 60GHz utilized in the Wi-Fi technology, or any radio frequency utilized in the future evolution of the Wi-Fi technology. - The
controller 20 may be a general-purpose processor, a Micro Control Unit (MCU), an application processor, a Digital Signal Processor (DSP), or the like, which includes various circuits for providing the functions of data processing and computing, controlling thewireless transceiver 10 for wireless communications with theAP 110, storing and retrieving data (e.g., program code) to and from thestorage device 30, sending a series of frame data (e.g. representing text messages, graphics, images, etc.) to thedisplay device 40, and receiving user inputs or outputting signals via the I/O device 50. - In particular, the
controller 20 coordinates the aforementioned operations of thewireless transceiver 10, thestorage device 30, thedisplay device 40, and the I/O device 50 for performing the method of the present application. - In another embodiment, not falling within the claims, the
controller 20 may be incorporated into thebaseband processing device 11, to serve as a baseband processor. - The
storage device 30 may be a non-transitory machine-readable storage medium, including a memory, such as a FLASH memory or a Non-Volatile Random Access Memory (NVRAM), or a magnetic storage device, such as a hard disk or a magnetic tape, or an optical disc, or any combination thereof for storing data, instructions, and/or program code of applications, the Wi-Fi protocol (of the IEEE 802.11be or another protocol version), and/or the method of the present application. - The
display device 40 may be a Liquid-Crystal Display (LCD), a Light-Emitting Diode (LED) display, an Organic LED (OLED) display, or an Electronic Paper Display (EPD), etc., for providing a display function. Alternatively, thedisplay device 40 may further include one or more touch sensors for sensing touches, contacts, or approximations of objects, such as fingers or styluses. - The I/
O device 50 may include one or more buttons, a keyboard, a mouse, a touch pad, a video camera, a microphone, and/or a speaker, etc., to serve as the Man-Machine Interface (MMI) for interaction with users. - Similarly, the
AP 110 may include awireless transceiver 60, acontroller 70, astorage device 80, and an I/O device 90. - The
wireless transceiver 60 is configured to perform wireless transmission and reception to and from the STAs 120-140. For example, thewireless transceiver 60 may be a Wi-Fi chip. - Specifically, the
wireless transceiver 60 may include abaseband processing device 61, anRF device 62, andantenna 63, wherein theantenna 63 may include an antenna array for UL/DL MU-MIMO. - The
baseband processing device 61 is configured to perform baseband signal processing, such as ADC/DAC, gain adjusting, modulation/demodulation, encoding/decoding, and so on. Thebaseband processing device 61 may contain multiple hardware components, such as a baseband processor, to perform the baseband signal processing. - The
RF device 62 may receive RF wireless signals via theantenna 63, convert the received RF wireless signals to baseband signals, which are processed by thebaseband processing device 61, or receive baseband signals from thebaseband processing device 61 and convert the received baseband signals to RF wireless signals, which are later transmitted via theantenna 63. TheRF device 62 may also contain multiple hardware devices to perform radio frequency conversion. For example, theRF device 62 may include a mixer to multiply the baseband signals with a carrier oscillated in the radio frequency of the supported cellular technologies, wherein the radio frequency may be 2.4GHz, 5GHz, or 60GHz utilized in the Wi-Fi technology, or any radio frequency utilized in the future evolution of the Wi-Fi technology. - The
controller 70 may be a general-purpose processor, an MCU, an application processor, a DSP, or the like, which includes various circuits for providing the functions of data processing and computing, controlling thewireless transceiver 60 for wireless communications with the STAs 120-140, storing and retrieving data (e.g., program code) to and from thestorage device 80, and receiving user inputs or outputting signals via the I/O device 90. - In particular, the
controller 70 coordinates the aforementioned operations of thewireless transceiver 60, thestorage device 80, and the I/O device 90 for performing the method of the present application. - In another embodiment, not falling within the claims, the
controller 70 may be incorporated into thebaseband processing device 61, to serve as a baseband processor. - As will be appreciated by persons skilled in the art, the circuits of the
controllers - The
storage device 80 may be a non-transitory machine-readable storage medium, including a memory, such as a FLASH memory or a NVRAM, or a magnetic storage device, such as a hard disk or a magnetic tape, or an optical disc, or any combination thereof for storing data, instructions, and/or program code of applications, Wi-Fi protocol (of the IEEE 802.11be or another protocol version), and/or the method of the present application. - The I/
O device 90 may include one or more buttons, a keyboard, a touch pad, a display device (e.g., LCD, LED, OLED, or EPD, etc.), a light emitting device, a microphone, and/or a speaker, etc., to serve as the MMI for interaction with users. - It should be understood that the components described in
Fig. 2 are for illustrative purposes only and are not intended to limit the scope of the application. For example, theAP 110 or theSTA 120/130/140 may include more components, such as another wireless transceiver for providing telecommunication services, a Global Positioning System (GPS) device for use of some location-based services or applications, and/or a battery for powering the other components, etc. Alternatively, theAP 110 or theSTA 120/130/140 may include fewer components. For example, theSTA 120/130/140 may not include thedisplay device 40 and/or the I/O device 50. -
Fig. 3 is a schematic diagram illustrating the format of an EHT trigger frame. - A trigger frame is used by an AP (or an AP mode STA) to allocate resources for and solicit one or more EHT TB PPDU transmissions. Generally, the trigger frame includes the information required by the responding STA to send an EHT TB PPDU.
- Specifically, as shown in
Fig. 3 , an EHT trigger frame may include a Media Access Control (MAC) header, a Common Info field, a list of User Info fields, padding bit(s), and a Frame Check Sequence (FCS) field. - The MAC header is consisted of a Frame Control field, a Duration field, a Receiver Address (RA) field, and a TA field. The Frame Control field may include control information required for frame transmission/reception. The Duration field may be set to a time for transmitting the corresponding frame. The RA field may indicate the address(es) of the receiver STA(s). For example, the RA field may be set to a broadcast group address. The TA field may indicate the address of the AP/STA transmitting the EHT trigger frame.
- The Common Info field may include the common information for all the triggered STAs, while each User Info field may include the information dedicated for a respective triggered STA.
- It should be noted that, unlike conventional trigger frames (e.g., an HE trigger frame), the trigger frame described herein may apply to EHT by defining a new value for EHT identification in the Subtype subfield of the Frame Control field or in the Trigger Type subfield of the Common Info field. For example, the valid Control Type value and Subtype value combinations may be defined as follows in Table 1, and the Trigger Type subfield encoding may be defined as follows in Table 2.
Table. 1 Control Type value Control Type description Subtype value Subtype description 01 Control 0000-0001 Reserved 01 Control 0010 Trigger 01 Control 0101 VHT/HE NDP Announcement 01 Control 1010 EHT identification Table 2. Trigger Type value Trigger name variant 0 Basic 1 Beamforming Report Poll (BFRP) 2 MLT- BAR 3 MU- RTS 4 Buffer Status Report Poll (BSRP) 5 GCR MU- BAR 6 Bandwidth Query Report Poll (BQRP) 7 NDP Feedback Report Poll (NFRP) 8 EHT identification 9-15 Reserved - Moreover, unlike conventional trigger frames (e.g., an HE trigger frame), the EHT trigger frame described herein is enhanced for RU allocation signaling to support EHT TB PPDU with multi-RU, by modifying the RU Allocation subfield format of the User Info field. Details of such improvement will be described later in the following figures.
-
Fig. 4 is a schematic diagram illustrating the format of the User Info field of an EHT trigger frame. - As shown in
Fig. 4 , the RU Allocation subfield of the User Info field is 9 bits long, in contrast to the 8-bit long RU Allocation subfield of the User Info field in a conventional trigger frame (e.g., an HE trigger frame). - Specifically, one additional bit is newly introduced as the first bit (i.e., B0) in the RU Allocation subfield to indicate support of 320 MHz bandwidth in EHT. For example, B0 of the RU Allocation subfield is set to 0 to indicate that the RU allocation applies to the primary 160 MHz channel of the 320 MHz bandwidth, and is set to 1 to indicate that the RU allocation applies to the secondary 160 MHz channel of the 320 MHz bandwidth.
- In addition, the second bit (i.e., B1) of the RU Allocation subfield indicates whether the RU allocation applies to the primary 80 MHz channel of the 320 MHz bandwidth. For example, B1 of the RU Allocation subfield is set to 0 to indicate that the RU allocation applies to the primary 80 MHz channel, and is set to 1 to indicate that the RU allocation applies to the secondary 80 MHz channel.
-
Fig. 5 is a schematic diagram illustrating the channel arrangement of a 320 MHz bandwidth. - As shown in
Fig. 5 , the 320 MHz bandwidth is divided into four continuous 80 MHz channels. The 160 MHz channel consisting of the first two 80 MHz channels may be configured as the primary 160 MHz channel for EHT, and the 160 MHz channel consisting of the last two 80 MHz channels may be configured as the secondary 160 MHz channel for EHT. - Furthermore, the first 80 MHz channel in the first primary 160 MHz channel may be configured as the primary 80 MHz channel, while the other 80 MHz channels may be configured as the secondary 80 MHz channels.
- Please note that the channel arrangement described in
Fig 5 is for illustrative purposes only and is not intended to limit the scope of the application. For example, the 160 MHz channel consisting of the last two 80 MHz channels may be configured as the primary 160 MHz channel for EHT, while the 160 MHz channel consisting of the first two 80 MHz channels may be configured as the secondary 160 MHz channel for EHT. Similarly, any 80 MHz channel other than the first 80 MHz channel may be configured as the primary 80 MHz channel. - Referring back to
Fig. 4 , the third to ninth bits (i.e., B2 to B8) of the RU Allocation subfield represent a value which may be set to be greater than 68 to indicate the combination of the RUs for EHT. - Specifically, the values 0-68 have been defined for legacy protocol versions in the IEEE 802.11ax standard. Due to the bandwidth increase from 160 MHz to 320 MHz in IEEE 802.11be, new values are proposed herein for EHT as follows in Tables 3 and 4.
Table. 3 B8 to B2 of the RE Allocation subfield combination of RUs used for UL BW 69 52 tones (2) + 26 tones (2) 70 52 tones (3) + 26 tones (8) 71 52 tones (6) + 26 tones (11) 72 52 tones (7) + 26 tones (17) 73 52 tones (11) + 26 tones (27) 74 52 tones (14) + 26 tones (30) 75 106 tones (1) + 26 tones (5) 76 106 tones (2) + 26 tones (5) 77 106 tones (3) + 26 tones (14) 78 106 tones (4) + 26 tones (14) 79 106 tones (5) + 26 tones (24) 80 106 tones (8) + 26 tones (33) Table. 4 B8 to B2 of the RU Allocation subfield combination of RUs used tor UL BW 81 484 tones (1) + 996 tones (2) 82 484 tones (2) + 996 tones (2) 83 484 tones (3) + 996 tones (1) 84 484 tones (4) + 996 tones (1) 85 242 tones (1) + 484 tones (2) 86 242 tones (2) + 484 tones (2) 87 242 tones (3) + 484 tones (1) 88 242 tones (4) + 484 tones (1) 89 484 tones (2) + 242 tones (2) + 996 tones (2) 90 484 tones (2) + 242 tones (1) + 996 tones (2) ⋮ ⋮ 117 996 tones (1, 2, 3) 118-127 Reserved - Note that the numbers in the brackets in Table 3 refer to the RUs in the exemplary RU allocation for EHT as shown in
Fig. 6 , and the numbers in the brackets in Table 4 refer to the RUs in the exemplary RU allocation for EHT as shown inFig. 7 . - It should be understood that 7 bits (i.e., B2 to B8) of the RU Allocation subfield can represent a total number of 128 combinations of RUs, in which 69 combinations of RUs are defined for legacy protocol versions, and thus, there are only 59 combinations of RUs left to be defined for adapting to EHT. In case there may be more than 59 combinations of RUs for adapting to EHT in the future, only one RU Allocation subfield may not be enough to represent the complete combinations of RUs in EHT. In response to such consideration, the present application proposes another solution as follows.
-
Fig. 8 is a schematic diagram illustrating the format of the User Info field of an EHT trigger frame according to an embodiment of the application. - As shown in
Fig. 8 , the User Info field is extended to include additional subfields, such as a Num of RUs subfield, and one or more RU Allocation subfields. The Num of RUs subfield indicates the number of RUs to be used in a TB PPDU, and correspondingly, there are the same number of RU Allocation subfields in the User Info field. For example, the Num of RUs subfield may be 3 bits long, and indicate one RU if it's set to "000" (in binary notation), or indicate two RUs if it's set to "001". - Each RU Allocation subfield of the User Info field is 9 bits long, in contrast to the 8-bit long RU Allocation subfield of the User Info field in a conventional trigger frame (e.g., an HE trigger frame). Similar to the embodiment of
Fig. 4 , one additional bit is newly introduced as the first bit (i.e., B0) in the RU Allocation subfield to indicate support of 320 MHz bandwidth in EHT. - For example, if the Num of RUs subfield is set to "001" to indicate two RUs to be used in a TB PPDU, the first RU Allocation subfield is set to "000001000" (from B8 to B0 in binary notation), and the second RU Allocation subfield is set to "010011000", then the combination of RUs denoted with dark background in
Fig. 9 may be determined. -
Fig. 10 is a flow chart illustrating the method for RU allocation signaling to support TB PPDU with multi-RU by an STA according to an embodiment of the application. - In this embodiment, the method for RU allocation signaling to support TB PPDU with multi-RU may be applied to and executed by an STA (e.g., the
STA 120/130/140) supporting use of 320 MHz bandwidth. - To begin with, the STA receives a trigger frame including a first RU Allocation subfield which has one bit to indicate support of 320 MHz bandwidth from an AP (step S1010).
- Next, the STA determines a combination of RUs to be used in a TB PPDU according to the first RU Allocation subfield (step S 1020).
- After that, the STA sends the TB PPDU for UL data transmission to the AP in response to the trigger frame (step S1030).
- The trigger frame may be an EHT trigger frame and the TB PPDU is an EHT TB PPDU in compliance with IEEE 802.11be standard or any future evolution of the IEEE 802.11be.
- In addition to the first RU Allocation subfield, the trigger frame may further include a Subtype subfield and a Trigger Type subfield, and one or both of the Subtype subfield and the Trigger Type subfield may be set to a value for EHT identification.
- Specifically, the first RU Allocation subfield may be 9 bits long, and the bit to indicate support of 320 MHz bandwidth may be introduced as the first bit of the first RU Allocation subfield, while the third to ninth bits of the first RU Allocation subfield represent a value greater than 68 to indicate the combination of the RUs for EHT.
- In one embodiment, not falling within the claims, only one RU Allocation subfield (i.e., the first RU Allocation subfield) may be used in the User Info field of the trigger frame to indicate the combination of the RUs to be used in the TB PPDU, if the third to ninth bits of the first RU Allocation subfield are enough to represent the complete combinations of RUs for EHT.
- In another embodiment, not falling within the claims, two or more RU Allocation subfields may be used in the User Info field of the trigger frame to indicate the combination of the RUs to be used in the TB PPDU, if the third to ninth bits of only one RU Allocation subfield are not enough to represent the complete combinations of RUs for EHT. In an embodiment falling within the claims, the trigger frame further includes a Num of RUs subfield for indicating the number of the RUs to be used in the TB PPDU, and a second RU Allocation subfield with the same format as the first RU Allocation subfield, wherein each of the first RU Allocation subfield and the second RU Allocation subfield indicates a respective one of the RUs to be used in the TB PPDU.
-
Fig. 11 is a flow chart illustrating the method for RU allocation signaling to support TB PPDU with multi-RU by an AP according to an embodiment of the application. - In this embodiment, the method for RU allocation signaling to support TB PPDU with multi-RU may be applied to and executed by an AP (e.g., the
AP 110 or an AP mode STA) supporting use of 320 MHz bandwidth. - To begin with, the AP sends a trigger frame including a first RU Allocation subfield which has one bit to indicate support of 320 MHz bandwidth to an STA (step S1110).
- Next, the AP receives a TB PPDU from the STA in response to the trigger frame, wherein the TB PPDU includes a combination of RUs as indicated by the first RU Allocation subfield (step S1120).
- In view of the forgoing embodiments, it will be appreciated that the present application realizes RU allocation signaling to support EHT TB PPDU with multi-RU, by introducing an additional bit in the RU Allocation subfield of a trigger frame to indicate support of 320 MHz bandwidth and defining a new value for EHT identification in the Subtype subfield and/or the Trigger Type subfield of the trigger frame.
- While the application has been described by way of example and in terms of preferred embodiment, it should be understood that the application is not limited thereto. Those who are skilled in this technology can still make various alterations and modifications without departing from the scope of this application. Therefore, the scope of the present application shall be defined and protected by the following claims.
- Use of ordinal terms such as "first", "second", etc., in the claims to modify a claim element does not by itself connote any priority, precedence, or order of one claim element over another or the temporal order in which acts of a method are performed, but are used merely as labels to distinguish one claim element having a certain name from another element having the same name (but for use of the ordinal term) to distinguish the claim elements.
Claims (12)
- A wireless communication terminal, operating as a Station, in the following also referred to as STA, (120, 130, 140), comprising:a wireless transceiver (10), configured to perform wireless transmission and reception to and from an Access Point, in the following also referred to as AP, (110); anda controller (20), coupled to the wireless transceiver (10), and configured to receive a trigger frame comprising a first Resource Unit, in the following also referred to as RU, Allocation subfield which has one bit to indicate support of 320 MHz bandwidth from the AP (110) via the wireless transceiver (10), determine a combination of RUs to be used in a Trigger-Based Physical layer Protocol Data Unit, in the following also referred to as TB PPDU, according to the first RU Allocation subfield, and send the TB PPDU for Uplink, in the following also referred to as UL, data transmission to the AP (110) via the wireless transceiver (10) in response to the trigger frame;characterized in that the trigger frame further comprises a subfield for indicating a number of the RUs to be used in the TB PPDU, and a second RU Allocation subfield with the same format as the first RU Allocation subfield; and each of the first RU Allocation subfield and the second RU Allocation subfield indicates a respective one of the RUs to be used in the TB PPDU.
- A method, executed by a wireless communication terminal operating as a Station, in the following also referred to as STA, the method comprising:receiving a trigger frame comprising a first Resource Unit, in the following also referred to as RU, Allocation subfield which has one bit to indicate support of 320 MHz bandwidth from an Access Point, in the following also referred to as AP, (S1010);determining a combination of RUs to be used in a Trigger-Based Physical layer Protocol Data Unit, in the following also referred to as TB PPDU, according to the first RU Allocation subfield (S1020); andsending the TB PPDU for Uplink, in the following also referred to as UL, data transmission to the AP in response to the trigger frame (S1030);characterized in that the trigger frame further comprises a subfield for indicating a number of the RUs to be used in the TB PPDU, and a second RU Allocation subfield with the same format as the first RU Allocation subfield; and each of the first RU Allocation subfield and the second RU Allocation subfield indicates a respective one of the RUs to be used in the TB PPDU.
- A wireless communication terminal, operating as an Access Point, in the following also referred to as AP, (110), comprising:a wireless transceiver (60), configured to perform wireless transmission and reception to and from a Station, in the following also referred to as STA, (120, 130, 140); anda controller (70), coupled to the wireless transceiver (60), and configured to send a trigger frame comprising a first Resource Unit, in the following also referred to as RU, Allocation subfield which has one bit to indicate support of 320 MHz bandwidth to the STA (120, 130, 140), and receive a Trigger-Based Physical layer Protocol Data Unit, in the following also referred to as TB PPDU, from the STA (120, 130, 140) in response to the trigger frame; wherein the TB PPDU comprises a combination of RUs as indicated by the first RU Allocation subfield;characterized in that the trigger frame further comprises a subfield for indicating a number of the RUs to be used in the TB PPDU, and a second RU Allocation subfield with the same format as the first RU Allocation subfield; and each of the first RU Allocation subfield and the second RU Allocation subfield indicates a respective one of the RUs to be used in the TB PPDU.
- A method, executed by a wireless communication device operating as an Access Point, in the following also referred to as AP, the method comprising:sending a trigger frame comprising a first Resource Unit, in the following also referred to as RU, Allocation subfield which has one bit to indicate support of 320 MHz bandwidth to a Station, in the following also referred to as STA, (S1110); andreceiving a Trigger-Based Physical layer Protocol Data Unit, in the following also referred to as TB PPDU, from the STA in response to the trigger frame (S1020);wherein the TB PPDU comprises a combination of RUs as indicated by the first RU Allocation subfield;characterized in that the trigger frame further comprises a subfield for indicating a number of the RUs to be used in the TB PPDU, and a second RU Allocation subfield with the same format as the first RU Allocation subfield; and each of the first RU Allocation subfield and the second RU Allocation subfield indicates a respective one of the RUs to be used in the TB PPDU.
- The wireless communication terminal as claimed in claim 1 or 3, wherein the trigger frame is an Extremely-High Throughput, in the following also referred to as EHT, trigger frame and the TB PPDU is an EHT TB PPDU in compliance with Institute of Electrical and Electronics Engineers, in the following also referred to as IEEE, 802.11be standard.
- The wireless communication terminal as claimed in claim 5, wherein the first RU Allocation subfield is 9 bits long, and the bit to indicate support of 320 MHz bandwidth is introduced as the first bit of the first RU Allocation subfield.
- The wireless communication terminal as claimed in claim 6, wherein the third to ninth bits of the first RU Allocation subfield represent a value greater than 68 to indicate the combination of the RUs for EHT.
- The wireless communication terminal as claimed in any one of claims 5 to 7, wherein the trigger frame further comprises a Subtype subfield and a Trigger Type subfield, and one of the Subtype subfield and the Trigger Type subfield is set to a value for EHT identification.
- The method as claimed in claims 2 or 4, wherein the trigger frame is an EHT trigger frame and the TB PPDU is an EHT TB PPDU in compliance with IEEE 802.11be standard.
- The method as claimed in claim 9, wherein the first RU Allocation subfield is 9 bits long, and the bit to indicate support of 320 MHz bandwidth is introduced as the first bit of the first RU Allocation subfield.
- The method as claimed in claim 10, wherein the third to ninth bits of the first RU Allocation subfield represent a value greater than 68 to indicate the combination of the RUs for EHT.
- The method as claimed in any one of claims 9 to 11, wherein the trigger frame further comprises a Subtype subfield and a Trigger Type subfield, and one of the Subtype subfield and the Trigger Type subfield is set to a value for EHT identification.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US202063020582P | 2020-05-06 | 2020-05-06 | |
US17/142,333 US11582007B2 (en) | 2020-05-06 | 2021-01-06 | Apparatuses and methods for resource unit (RU) allocation signaling to support trigger-based physical layer protocol data unit (TB PPDU) with multi-RU |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3908040A1 EP3908040A1 (en) | 2021-11-10 |
EP3908040B1 true EP3908040B1 (en) | 2023-11-29 |
Family
ID=75728654
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP21170846.6A Active EP3908040B1 (en) | 2020-05-06 | 2021-04-28 | Apparatuses and methods for resource unit (ru) allocation signaling to support trigger-based physical layer protocol data unit (tb ppdu) with multi-ru |
Country Status (4)
Country | Link |
---|---|
US (1) | US11582007B2 (en) |
EP (1) | EP3908040B1 (en) |
CN (1) | CN113692049B (en) |
TW (1) | TWI772004B (en) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11224058B2 (en) * | 2019-12-17 | 2022-01-11 | Mediatek Inc. | Device and method for generating a physical layer convergence procedure (PLCP) using aggregation operation |
US11985080B2 (en) * | 2020-05-08 | 2024-05-14 | Intel Corporation | Apparatus, system, and method of communicating an extremely high throughput (EHT) physical layer (PHY) protocol data unit (PPDU) |
US20220132371A1 (en) * | 2020-10-26 | 2022-04-28 | Apple Inc. | Configuring a Preamble for Trigger-Based Protocol Data Unit |
CA3208644A1 (en) * | 2022-08-05 | 2024-02-05 | Comcast Cable Communications, Llc | Trigger frame for uplink resource allocation |
WO2024108451A1 (en) * | 2022-11-23 | 2024-05-30 | 北京小米移动软件有限公司 | Communication method, electronic device, and storage medium |
Family Cites Families (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20220157520A (en) * | 2015-02-17 | 2022-11-29 | 주식회사 윌러스표준기술연구소 | Signaling method for multi-user transmission, and wireless communication termianl and wireless communication method using same |
US10116361B2 (en) * | 2015-06-02 | 2018-10-30 | Newracom, Inc. | Methods for uplink multiuser signaling and transmission |
US10219271B1 (en) * | 2015-07-01 | 2019-02-26 | Newracom, Inc. | Bandwidth allocation signalling |
WO2017030342A1 (en) * | 2015-08-19 | 2017-02-23 | 엘지전자(주) | Method for transmitting trigger frame in wireless communication system, and device for same |
WO2017043713A1 (en) * | 2015-09-08 | 2017-03-16 | 엘지전자(주) | Method for transmitting data in wireless communication system and apparatus therefor |
KR20220122776A (en) * | 2016-04-02 | 2022-09-02 | 주식회사 윌러스표준기술연구소 | Wireless communication method and wireless communication terminal for spatial reuse of overlapped basic service set |
US10764877B2 (en) * | 2016-05-06 | 2020-09-01 | Qualcomm Incorporated | Trigger frame in wireless local area network |
SG11201810184QA (en) * | 2016-07-22 | 2018-12-28 | Panasonic Ip Corp America | Transmission appratus and transmission method |
US10848233B2 (en) * | 2017-10-13 | 2020-11-24 | Qualcomm Incorporated | Managing high volumes of space-time-streams in next generation extremely high throughput (EHT) Wi-Fi systems |
US10785706B2 (en) | 2017-10-16 | 2020-09-22 | Qualcomm Incorporated | Bandwidth signaling for a basic service set (BSS) supporting 320 MHZ operating bandwidth |
US11109278B2 (en) | 2017-10-20 | 2021-08-31 | Qualcomm Incorporated | Multiplexing clients of different generations in trigger-based transmissions |
US11160084B2 (en) | 2018-07-05 | 2021-10-26 | Qualcomm Incorporated | Supporting 320 MHz operating BW |
CN116405161B (en) * | 2018-07-17 | 2024-01-16 | 华为技术有限公司 | Communication method and device |
CN116614213A (en) * | 2018-07-25 | 2023-08-18 | 华为技术有限公司 | Resource unit indication method, device and storage medium |
US11082983B2 (en) * | 2018-09-10 | 2021-08-03 | Intel Corporation | Tone plans and preambles for extremely high throughput |
US10813061B2 (en) * | 2018-09-18 | 2020-10-20 | Intel Corporation | Power reduction in a wireless network |
US11128505B2 (en) * | 2019-02-06 | 2021-09-21 | Intel Corporation And Intel Ip Corporation | Channel width, spatial streams, and short packet signaling |
US11588603B2 (en) * | 2019-03-21 | 2023-02-21 | Marvell Asia Pte Ltd | Allocating resource units for uplink multi-user transmissions in wide bandwidths |
US11387937B2 (en) * | 2019-08-07 | 2022-07-12 | Huawei Technologies Co., Ltd. | Preamble with detectable WLAN version identification |
US11539458B2 (en) * | 2020-02-07 | 2022-12-27 | Newracom, Inc. | Multiple resource unit signaling in a wireless local area network |
US11792834B2 (en) * | 2020-03-02 | 2023-10-17 | Avago Technologies International Sales Pte. Limited | Signaling and decoding of punctured subbands in trigger-based PPDU |
-
2021
- 2021-01-06 US US17/142,333 patent/US11582007B2/en active Active
- 2021-04-28 TW TW110115258A patent/TWI772004B/en active
- 2021-04-28 EP EP21170846.6A patent/EP3908040B1/en active Active
- 2021-04-29 CN CN202110472852.0A patent/CN113692049B/en active Active
Also Published As
Publication number | Publication date |
---|---|
US20210351894A1 (en) | 2021-11-11 |
EP3908040A1 (en) | 2021-11-10 |
TW202143686A (en) | 2021-11-16 |
CN113692049B (en) | 2024-06-07 |
CN113692049A (en) | 2021-11-23 |
TWI772004B (en) | 2022-07-21 |
US11582007B2 (en) | 2023-02-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3908040B1 (en) | Apparatuses and methods for resource unit (ru) allocation signaling to support trigger-based physical layer protocol data unit (tb ppdu) with multi-ru | |
US9615397B2 (en) | Efficient group ID management for wireless local area networks (WLANs) | |
US20210345320A1 (en) | Apparatuses and methods for acquiring and reporting resource needs of shared access points (aps) for multi-ap coordination | |
US10757723B2 (en) | Transmitting apparatus and receiving apparatus | |
US20210250919A1 (en) | Apparatuses and methods for user equipment (ue)-coordination based resource allocation for sidelink communication | |
EP4142404A1 (en) | Indication method for multiple resource units for transmission, and related device | |
US20240097842A1 (en) | Ppdu transmission method and related apparatus | |
US20230309088A1 (en) | Transmitting apparatus and receiving apparatus | |
US11937251B2 (en) | Apparatuses and methods for flexible Resource Unit (RU) allocation | |
US11552727B2 (en) | Apparatuses and methods for fast switching from trigger mode to contention mode uplink (UL) transmission | |
CN113630789B (en) | Apparatus and method for wireless communication | |
US20210314951A1 (en) | Apparatuses and methods for uplink transmission using a multi-user physical layer protocol data unit (mu ppdu) with a single resource unit (ru) | |
US20240244687A1 (en) | Data transmission method and apparatus thereof | |
US20240224358A1 (en) | Multi-link operation method, and apparatus thereof | |
US20230354277A1 (en) | Apparatuses and methods for flexible resource unit (ru) allocation | |
US20240204909A1 (en) | Data transmission method and apparatus thereof | |
US20240163932A1 (en) | Multi-link operation (mlo) transmission method and apparatus thereof | |
US20240080138A1 (en) | Duplicated packet transmission method and apparatus thereof | |
US20240163947A1 (en) | Method and apparatus for multi-link operation | |
US20240163768A1 (en) | Packet transmission method and apparatus thereof | |
WO2023160331A1 (en) | Antenna mode switching method and related apparatus | |
CN117377096A (en) | Wireless communication method and related station and access point |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
B565 | Issuance of search results under rule 164(2) epc |
Effective date: 20211013 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20220505 |
|
RBV | Designated contracting states (corrected) |
Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 72/51 20230101ALN20230530BHEP Ipc: H04W 72/02 20090101ALN20230530BHEP Ipc: H04W 84/12 20090101ALN20230530BHEP Ipc: H04W 72/23 20230101ALI20230530BHEP Ipc: H04L 5/00 20060101ALI20230530BHEP Ipc: H04W 28/20 20090101AFI20230530BHEP |
|
INTG | Intention to grant announced |
Effective date: 20230616 |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230607 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602021007181 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG9D |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20231129 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20240301 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20240329 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20240329 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20240301 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20240229 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1637372 Country of ref document: AT Kind code of ref document: T Effective date: 20231129 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20240229 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20240315 Year of fee payment: 4 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20240425 Year of fee payment: 4 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20231129 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20240401 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20240401 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602021007181 Country of ref document: DE |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |