Base station device, terminal device, and communication method

Abstract

The present invention comprises a reception unit that receives an MU-RTS trigger frame which includes a first field. The first field indicates whether a CTS frame is to be transmitted on a primary 20 MHz channel, a primary 40 MHz channel, a primary 80 MHz channel, a 160 MHz channel, an 80+80 MHz channel, 320 MHz, or an NPCA primary channel. In the first field, a first value is set to indicate the NPCA primary channel.　

Description

Base Station Device, Terminal Device, and Communication Method

[0001] The present invention relates to a base station device, a terminal device, and a communication method. This application claims priority to Japanese Patent Application No. 2024-187362 filed in Japan on October 24, 2024, the content of which is incorporated herein by reference.

[0002] The IEEE (The Institute of Electrical and Electronics Engineers Inc.) is considering accelerating wireless LAN (Local Area Network) communication and improving frequency utilization efficiency. Currently, the standardization of IEEE802.11bn has been started as a successor standard to IEEE802.11be.

[0003] IEEE802.11-23 / 2005r0, Intel Corp, “Non-primary channel access (NPCA)”, November 2023.

[0004] One aspect of the present invention provides a terminal device, a base station device, and a communication method capable of efficient communication.

[0005] (1) A first aspect of the present invention is a terminal device including a receiving unit that receives a MU-RTS Trigger frame including a first field, wherein the first field indicates whether a CTS frame is transmitted on any of a primary 20MHz channel, a primary 40MHz channel, a primary 80MHz channel, a 160MHz channel, an 80+80MHz channel, a 320MHz, an NPCA primary channel, and the first field has a first value set to indicate the NPCA primary channel.

[0006] (2) A second aspect of the present invention is a base station device comprising a transmitting unit that transmits a MU-RTS Trigger frame including a first field, wherein the first field indicates whether the CTS frame is transmitted on a primary 20MHz channel, a primary 40MHz channel, a primary 80MHz channel, a 160MHz channel, an 80+80MHz channel, a 320MHz channel, or an NPCA primary channel, and the first field is set to a first value to indicate the NPCA primary channel.

[0007] (3) A third aspect of the present invention is a communication method for use in a terminal device, comprising the step of receiving a MU-RTS Trigger frame including a first field, wherein the first field indicates whether the CTS frame is transmitted on a primary 20MHz channel, a primary 40MHz channel, a primary 80MHz channel, a 160MHz channel, an 80+80MHz channel, a 320MHz channel, or an NPCA primary channel, and the first field is set to a first value to indicate the NPCA primary channel.

[0008] This enables the realization of an efficient wireless communication system.

[0009] This figure shows an example of a wireless LAN system according to one embodiment of this embodiment. This figure shows an example of an OBSS according to one embodiment of this embodiment. This figure shows an example of the configuration of an STA according to one embodiment of this embodiment. This figure shows an example of the configuration of an AP according to one embodiment of this embodiment. This figure shows an example of a MAC frame format according to one embodiment of this embodiment. This figure shows an example of an A-MSDU according to one embodiment of this embodiment. This figure shows an example of an A-MPDU according to one embodiment of this embodiment. This figure shows an example of Fragmentation according to one embodiment of this embodiment. This figure shows an example of a PPDU according to one embodiment of this embodiment. This figure shows an example of a backoff procedure according to one embodiment of this embodiment. This figure shows an example of a NAV according to one embodiment of this embodiment. This figure shows an example of channel bonding according to one embodiment of this embodiment. This figure shows an example of a backoff procedure on the NPCA primary channel of an STA according to one embodiment of this embodiment. This figure shows an example of the size and placement of RUs by RU Allocation subfield and UL BW subfield according to one embodiment of this embodiment. This figure shows an example of a table defining the mapping between RU index and RU when the UL BW subfield indicates 20MHz according to one embodiment of this embodiment. This figure shows an example of B7-B1 of the UL BW subfield and RU Allocation subfield of a MU-RTS Trigger frame according to one embodiment of this embodiment. This figure shows an example of the B7-B1 RU Allocation subfield of MU-RTS Trigger frames of various bandwidths according to one aspect of this embodiment. This figure shows an example of the exchange of MU-RTS and simultaneous CTS response according to one aspect of this embodiment. This figure shows an example of the exchange of MU-RTS Trigger frame and simultaneous CTS frame response in a 40MHz channel according to one aspect of this embodiment. This figure shows an example of the channel for CTS transmission in NPCA according to one aspect of this embodiment.This figure shows an example of the process for determining the channel to which a CTS is transmitted according to one aspect of this embodiment. This figure shows an example of the process for indicating the channel to which a response CTS to MU-RTS is transmitted according to one aspect of this embodiment.

[0010] Embodiments of the present invention will be described below.

[0011] "A, and / or B" may be a term that includes "A", "B", or "A and B".

[0012] The wireless LAN system in this embodiment comprises access points (APs) and stations (STAs). The network consisting of access points and stations is referred to as a BSS (Basic Service Set). The wireless LAN system may consist of one or more stations. If the wireless LAN system consists of two or more STAs, the wireless LAN system may also be referred to as a BSS.

[0013] An access point (AP) may also be called a base station device. A station (STA) may also be called a terminal device.

[0014] Figure 1 shows an example of a wireless LAN system according to one embodiment of this model. In Figure 1, the wireless LAN system comprises STA 103, STA 104, and AP 102. 101 may be referred to as BSS.

[0015] An STA may be a logical entity. This logical entity may be a logical entity that is a single addressable instance of the Medium Access Control (MAC) and physical layer interface to the Wireless Medium (WM). An STA may be a communication device over the Wireless Medium. An STA may also include an Access Point (AP) with base station functionality and / or a non-AP STA with terminal functionality. In other words, an STA may be an AP. An STA may also be a non-AP STA. An STA may also be both an AP and a non-AP STA. An STA may also be referred to as a terminal device.

[0016] The wireless medium may be the medium used to implement the transfer of Protocol Data Units (PDUs) between peer physical layer entities of a Wireless LAN. The wireless medium may be referred to as the medium. The medium may be referred to as Medium.

[0017] A channel may be an instance of a wireless medium used to transmit PPDU between two or more STAs.

[0018] For example, the channel may be 20 MHz. For example, the channel may be 1 MHz. The channel may have a frequency bandwidth other than those mentioned above. For example, a 20 MHz channel may be replaced with a 1 MHz channel. For example, each 20 MHz channel may be replaced with a 1 MHz channel. It may be replaced with a bandwidth other than 1 MHz.

[0019] An AP may include one STA and be an entity that provides access to distribution system services (DSS) via a wireless medium to associated STA(s). An AP may include an STA and a distribution system access function (DSAF). An AP may be referred to as an STA. In other words, an AP may be an STA.

[0020] A non-AP STA (non-access point station) may be an STA that is not included within an AP. For example, a non-AP STA may be an HT STA, a VHT STA, a HE STA, an EHT STA, or a UHR STA. A non-AP STA may be any STA other than those mentioned above. A non-AP STA may simply be referred to as an STA.

[0021] Distribution system services may be a set of services provided by the distribution system (DS). The distribution system access function may be a function within the AP that uses MAC services and distribution system services to provide access between the distribution system and the wireless medium. The distribution system may also be a system used to interconnect a set of BSSs and an integrated LAN to create an Extended Service Set (ESS).

[0022] A BSS may consist of a set of STAs that have successfully synchronized using JOIN service primitives and a set of STAs that uses a START primitive. For example, MLME-JOIN.confirm may be used as the JOIN service primitive. MLME-JOIN.confirm may be a primitive for confirming synchronization with the BSS. MLME-JOIN.request may be used as the JOIN service primitive. MLME-JOIN.request may be a primitive for requesting synchronization with the BSS. For example, MLME-START.request may be used as the START primitive. MLME-START.request may be a primitive for requesting a MAC entity to start a new BSS. A primitive may be an internal signal in an STA or AP. An internal signal here may be an internal signal used for information exchange between entities at different layers or different protocols, such as between an SME and an MLME, between an SME and a PLME, or between an MLME and a PLME.

[0023] An ESS is a set of one or more interconnected BSSs, which may appear as a single BSS in the Logical Link Control (LLC) layer of an STA associated with any of these BSSs. An ESS (Extended Service Set) may have a connection path via a WM between one of the APs that are members of the ESS and a non-AP STA. An ESS may have overlapping communication areas (coverages) composed of multiple BSSs. The distances between the multiple BSSs in an ESS may be large, and the coverage covered by multiple BSSs may be arranged as a wider coverage. In other words, the communication area of ​​an ESS may be the same as or larger than the communication area of ​​a single BSS. The communication area composed of an ESS may be referred to as an ESA (Extended Service Area).

[0024] An OBSS (Overlapping Basic Service Set) may be a BSS that operates on the same channel as the STA's BSS, and within (partially or entirely) its BSA (Basic Service Area).

[0025] Figure 2 shows an example of OBSS according to one aspect of this embodiment. In Figure 2, 202 may be AP#1. 203 may be STA#1. 204 may be STA#2. 201 may be BSS#1 composed of 202, 203, and 204. 203 may be synchronized with 202. 204 may be synchronized with 202. 206 may be AP#2. 207 may be STA#3. 208 may be STA#4. 205 may be BSS#2 composed of 206, 207, and 208. 207 may be synchronized with 206. 208 may be synchronized with 206. 202 may not be synchronized with 207. 202 may not be synchronized with 208. 206 may not be synchronized with 203. 206 may not be synchronized with 204. 201 and 205 may be BSS operating on the same channel. 205 may be considered an OBSS to 201. 201 may be considered an OBSS to 205. For example, 202 may receive a frame transmitted by 207. 204 may receive a frame transmitted by 207. 207 may receive a frame transmitted by 202. 207 may receive a frame transmitted by 204. For example, 202 may determine that the channel is busy while 207 is transmitting. 204 may determine that the channel is busy while 207 is transmitting. 207 may determine that the channel is busy while 202 is transmitting. 207 may determine that the channel is busy while 204 is transmitting.

[0026] A BSA may be a region that includes members of a BSS. A BSA may also include members of other BSSs. For example, in Figure 2, 201 may be a BSA that includes 203, 204, and 207, where 207 may be a member of another BSS.

[0027] IBSS (Independent Basic Service Set) is a BSS that forms a self-contained network, and access to the DS is not available.

[0028] An addressable unit may be a station (STA). Physical and operational characteristics may be defined by modifiers placed before the term STA. For example, in the case of location or mobility, an addressable unit may be a fixed STA, a mobile STA, and a mobility STA. An STA is an addressable destination, but it does not (generally) have to be a fixed location. An STA may have several different characteristics, each of which may constitute its function. For example, a single addressable unit may simultaneously have the characteristics of a portable STA, a QoS STA, a dependent STA, and a hidden STA.

[0029] The architecture may consist of several components that interact to provide a WLAN that transparently supports the movement of STAs to higher layers. The BSS may be a fundamental component of the LAN. The range over which member STAs of the BSS can communicate may be considered the coverage area. The range of all possible directional transmissions by member STAs may be referred to as the BSA.

[0030] Physical limitations may determine the direct distance between STAs. An infrastructure BSS may be part of a network composed of multiple BSSs. The architectural component for interconnecting infrastructure BSSs may be a DS for non-General Link (non-GLK) operations. The DS and Extended Service Set (ESS) may be mechanisms for extending connectivity for non-GLK operations. GLK operations may involve using bridges to form an extended network. The radio medium and the DSM (Distribution System Medium) may be logically separated. Each logical medium may be used for different purposes by different components of the architecture. Recognizing that multiple media are logically different is important for understanding the flexibility of the architecture. The LAN architecture is specified independently of the physical characteristics of a particular implementation. The DS may enable support for mobile devices by providing logical services necessary for address-to-destination mapping and seamless integration of multiple BSSs. An AP is an entity with STA functionality and a DSAF (Distribution System Access Function), which may enable access to the DS via the radio medium for the associated STA. Data between the BSS and DS may travel via the DSAF within the AP. An AP may include an STA, and its STA address may be addressable on the radio medium. The address that the AP uses to communicate with the radio medium and the DSM does not necessarily have to be the same. Data sent from one of the STAs associated with the AP to the AP's STA address may always be received on an uncontrolled port and processed by a port access entity. If a controlled port is authorized, the frame may conceptually pass through the DS.

[0031] Wireless networks of any size and complexity may be constructed using DS and infrastructure BSS. This network may be referred to as an ESS (Extended Service Set). An ESS is a collection of infrastructure BSSs connected by the same SSID, which may be connected by DS. An ESS does not necessarily contain a DS. To the LLC layer, an ESS may look the same as an IBSS. STAs within an ESS can communicate, and mobile STA(s) may move transparently between BSSs to the LLC (within the same ESS). In an ESS, BSSs may partially overlap. This may be commonly used to position coverage within a physical range. In an ESS, BSSs may be physically separated. In an ESS, there may be no logical limit on the distance between BSSs. In an ESS, BSSs may be located in the same physical location. This may be done to provide redundancy. In an ESS, one or more IBSS(s) or ESS(s) may physically reside in the same location as one or more ESS(s).

[0032] Figure 3 shows an example of the device configuration of an STA according to one embodiment of this model. The STA may include an antenna unit SU1, an RF (Radio Frequency) unit SU2, a physical layer processing unit (PHY layer processing unit) SU3, a MAC layer processing unit SU4, and an upper layer packet processing unit SU5. The STA may also include a wireless transceiver unit SU6 and a frame processing unit SU7. The wireless transceiver unit SU6 may be configured to include the antenna unit SU1 and the RF unit SU2. The frame processing unit SU7 may be configured to include the physical layer processing unit SU3 and the MAC layer processing unit SU4. The RF unit SU2 receives wireless signals via the antenna unit SU1.

[0033] The signal received by the RF unit SU2 is converted into a baseband signal and sent to the physical layer processing unit SU3. The physical layer processing unit SU3 performs processing related to the physical layer function (PHY function) on the converted baseband signal. The signal that has undergone processing at the physical layer in the physical layer processing unit SU3 is sent to the MAC layer processing unit SU4. The MAC layer processing unit SU4 performs processing related to the MAC layer function (MAC function) on the baseband signal. The signal that has undergone processing at the MAC layer in the MAC layer processing unit SU4 is sent as an upper layer packet to the upper layer packet processing unit SU5. The upper layer packet processing unit SU5 performs processing related to the upper layer function on the upper layer packet extracted from the received signal.

[0034] The upper layer packet processing unit SU5 performs processing related to the functions of the upper layer when transmitting upper layer packets. The upper layer packet to be transmitted is sent from the upper layer packet processing unit SU5 to the MAC layer processing unit SU4. The MAC layer processing unit SU4 performs processing related to the functions of the MAC layer on the upper layer packet. The frame that has undergone MAC layer processing in the MAC layer processing unit SU4 (a frame generated by processing the upper layer packet) is sent to the physical layer processing unit SU3. The physical layer processing unit SU3 performs processing related to the functions of the physical layer on the frame that has undergone MAC layer processing. The frame sent from the physical layer processing unit SU3 to the RF unit SU2 is converted into an RF signal and transmitted as a wireless signal via the antenna unit SU1.

[0035] The processing of the physical layer processing unit SU3 may be controlled by a PLME (Physical Layer Management Entity), which is an entity that controls the physical layer. The processing of the MAC processing unit SU4 may be controlled by an MLME (MAC Layer Management Entity), which is an entity that controls the MAC layer. PLME and MLME provide their respective layer management service interfaces. PLME and MLME may also be controlled by an SME (Station Management Entity), which is an entity independent of the layer. PLME, MLME, and SME may be included in the frame processing unit SU7.

[0036] Figure 4 shows an example of the device configuration of an AP according to one aspect of this embodiment. The AP may have an antenna unit AU1, an RF unit AU2, a physical layer processing unit AU3, a MAC layer processing unit AU4, and a DSAF unit AU5. The DSAF unit AU5 may have a higher layer packet processing function. The AP may also have a wireless transceiver unit AU6 and a frame processing unit AU7. The wireless transceiver unit AU6 may be configured to include the antenna unit AU1 and the RF unit AU2. The frame processing unit AU7 may be configured to include the physical layer processing unit AU3 and the MAC layer processing unit AU4.

[0037] The signal received by the RF unit AU2 is converted into a baseband signal and sent to the physical layer processing unit AU3. The physical layer processing unit AU3 performs processing related to the physical layer functions on the converted baseband signal. The signal that has undergone processing at the physical layer in the physical layer processing unit AU3 is sent to the MAC layer processing unit AU4. The MAC layer processing unit AU4 performs processing related to the MAC layer functions on the baseband signal. The signal that has undergone processing at the MAC layer in the MAC layer processing unit AU4 is sent to the DSAF unit AU5 as an upper layer packet. The DSAF unit AU5 performs processing related to the upper layer functions on the upper layer packet extracted from the received signal. The DSAF unit AU5 may also provide the upper layer packet to the DS.

[0038] The DSAF unit AU5 may acquire upper-layer packets from the DS. When transmitting upper-layer packets, the DSAF unit AU5 performs processing related to the functions of the upper layer. The upper-layer packets to be transmitted from the DSAF unit AU5 are sent to the MAC layer processing unit AU4. The MAC layer processing unit AU4 performs processing related to the functions of the MAC layer on the upper-layer packets. The frame that has undergone MAC layer processing in the MAC layer processing unit AU4 (a frame generated by processing the upper-layer packets) is sent to the physical layer processing unit AU3. The physical layer processing unit AU3 performs processing related to the functions of the physical layer on the frame that has undergone MAC layer processing. The frame sent from the physical layer processing unit AU3 to the RF unit AU2 is converted into an RF signal and transmitted as a radio signal via the antenna unit AU1.

[0039] The processing of the physical layer processing unit AU3 may be controlled by PLME. The processing of the MAC processing unit AU4 may be controlled by MLME. Furthermore, PLME and MLME may be controlled by SME, which is an entity independent of the layer. PLME, MLME, and SME may be included in the frame processing unit AU7.

[0040] An HT STA (High-Throughput STA) may provide PHY and MAC capabilities capable of supporting throughput of 100 Mb / s or more as measured at a MAC Data Services Access Point (SAP). An HT STA may also be a QoS STA. HT features may be utilized in an HT STA associated with an HT AP (High-Throughput AP). A subset of HT features may be used between two HT STAs that are members of the same IBSS. Some PHY features that distinguish an HT STA from a non-HT STA may be multiple-input multiple-output (MIMO) operation, spatial multiplexing (SM), spatial mapping (including transmit beamforming), spacetime block coding (STBC), low-density parity checking (LDPC) coding, and antenna selection (ASEL). The PPDU formats permitted in an HT STA may be non-HT format, HT-mixed format, and HT-greenfield format. In an HT STA, the PPDU may be transmitted with a 20 MHz bandwidth. In an HT STA, the PPDU may be transmitted with a 40 MHz bandwidth. The HT STA may have MAC functionality, including frame aggregation, several block ack features, low-power multipole (PSMP) operation, reverse direction (RD), and protection mechanisms to support coexistence with non-HT STAs.

[0041] A VHT STA (Very High-Throughput STA) may be an HT STA that supports VHT functions in addition to the functions supported by an HT STA. The main PHY functions of a VHT STA may support 40MHz and 80MHz channel widths. VHT single-user (SU) PPDUs may be supported as a main PHY function of a VHT STA. 160MHz and 80+80MHz channel widths may be supported as a main PHY function of a VHT STA. VHT multi-user (MU) PPDUs may be supported as a main PHY function of a VHT STA. The main PHY functions of a VHT STA do not necessarily have to be present in an HT STA. A-MPDU padding of VHT PPDUs may be supported as a main MAC function of a VHT STA. S-MPDU may be supported as a main MAC function of a VHT STA. Bandwidth indication response may be supported as a main MAC function of a VHT STA. The main MAC functions of a VHT STA do not necessarily have to be present in an HT STA. The VHT functionality may be used in VHT STAs associated with a VHT AP (Very High-Throughput AP). A subset of the VHT functionality may be used between two VHT STAs that are members of the same IBSS.

[0042] The operating channel width may be the channel width that the STA can currently receive. The operating channel width may also be the channel width that the STA can currently transmit. The operating channel width may also be referred to as the BSS bandwidth. For example, the operating channel may be the channel through which beacons are transmitted.

[0043] A High Efficiency (HE) STA may also be a VHT STA if operating in the 5GHz band. A 20MHz-only HE STA may not support 40MHz and 80MHz channel widths. Support for a 20MHz operating channel width may be mandatory for HE STAs. A 20MHz-only non-AP HE STA may be required to support 40MHz and 80MHz operating channel widths. Support for 160MHz and 80+80MHz operating channel widths may be optional for HE STAs. A HE STA may also be an HT STA. The main PHY features of an HE STA that are not present in HT STAs or VHT STAs may include support for DL ​​and UL OFDMA (Up Link Orthogonal Frequency Division Multiple Access). The main PHY features of an HE STA that are not present in HT STAs or VHT STAs may include support for DL ​​MU-MIMO (Down Link Multi User Multiple Input Multiple Output) with an HE AP supporting four or more spatial streams when MU-MIMO (Multi User Multiple Input Multiple Output) is performed across the entire PPDU bandwidth. The main PHY function of HE STA that is not present in HT STA or VHT STA may be support for DL ​​MU-MIMO reception in non-AP HE STA. The main MAC function of HE STA that is not present in HT STA or VHT STA may be support for the AP's OMI (Operating Mode Indication) responder and OMI initiator. The main MAC function of HE STA that is not present in HT STA or VHT STA may be support for the AP's individual TWT (Target Wake Time).The main MAC functions of HE STAs that do not exist in HT STAs or VHT STAs may also support the two NAV operations of non-AP STAs.

[0044] An EHT (Extreme High Throughput) STA may operate in a band between 1 GHz and 7.250 GHz. For example, an EHT STA may be a HE STA at 5 GHz and 6 GHz. For example, an EHT STA may be a HE STA at 2.4 GHz. An EHT STA may use operation elements for HT and / or VHT and / or HE STAs.

[0045] A UHR (Ultra High Reliability) STA may operate in a band between 1 GHz and 7.250 GHz. For example, a UHR STA may be an EHT STA at 5 GHz and 6 GHz. For example, a UHR STA may be a HE STA at 5 GHz and 6 GHz. For example, a UHR STA may be a VHT STA at 5 GHz and 6 GHz. For example, a UHR STA may be a HE STA at 2.4 GHz. For example, a UHR STA may be an HT STA at 2.4 GHz. A UHR STA may support Non Primary Channel Access. A UHR STA may use operation elements for HT, and / or VHT, and / or HE STAs, and / or UHR STAs. That is, a UHR STA may be controlled by an HT operation element, and / or a VHT operation element, and / or a HE operation element, and / or an EHT operation element, and / or a UHR operation element.

[0046] The APs and STAs within the BSS may perform transmission based on CSMA / CA (Carrier Sense Multiple Access with Collision Avoidance). The CSMA / CA protocol may be a protocol designed to reduce the collision probability at the time when collisions are most likely to occur among multiple STAs accessing the medium.

[0047] The HT BSS may be a BSS in which the Beacon frame transmitted by the HT STA includes the HT Capabilities element. The VHT BSS may be a BSS in which the Beacon frame transmitted by the VHT STA includes the VHT Operation element. The HE BSS may be a BSS in which the Beacon frame transmitted by the HE STA includes the HE Operation element. The EHT BSS may be a BSS in which the Beacon frame transmitted by the HE STA includes the EHT Operation element. For example, the HT BSS may be composed of STAs that support the capabilities of the HT STA. For example, the VHT BSS may be composed of STAs that support the capabilities of the VHT STA. For example, the HE BSS may be composed of STAs that support the capabilities of the HE. For example, the EHT BSS may be composed of STAs that support the capabilities of the EHT.

[0048] In this embodiment, the STA may be, for example, an HT STA, a VHT STA, a HE STA, an EHT STA, or a UHR STA. The STA may also be an STA other than the aforementioned STAs.

[0049] The APs and STAs may transmit frames of multiple frame types having a common frame format. The frames may be defined respectively at the physical layer, the MAC layer, and the logical link control (LLC) layer.

[0050] A MAC frame may be a unit of data exchanged between MAC entities. A synonym for MAC frame may be MPDU. An MPDU (MAC Protocol Data Unit) may be a unit of data exchanged between two peer MAC entities using physical layer (PHY) data services. A synonym for MPDU may be MAC frame. An MSDU (MAC Service Data Unit) may be information delivered as a single unit between MAC service access points (SAPs). In an STA, a MAC frame may be processed by the MAC layer processing unit SU4. In an STA, a MAC frame may be processed by the frame processing unit SU7. In an AP, a MAC frame may be processed by the MAC layer processing unit AU4. In an AP, a MAC frame may be processed by the frame processing unit AU7.

[0051] A PHY frame may be a unit of data exchanged between PHY entities. A synonym for PHY frame may be PPDU. A PPDU (PHY Protocol Data Unit) may be a unit of data exchanged between two peer PHY entities using physical layer (PHY) data services. A synonym for PPDU may be PHY frame. In the STA, a PHY frame may be processed by the physical layer processing unit SU4. In the STA, a PHY frame may be processed by the frame processing unit SU7. In the AP, a PHY frame may be processed by the physical layer processing unit AU4. In the AP, a PHY frame may be processed by the frame processing unit AU7.

[0052] The MAC frame format may consist of a MAC header, a frame body, and an FCS. The MAC frame format may also consist of a set of fields that occur in a fixed order in all frames.

[0053] The MAC header may consist of a Frame Control field, a Duration / ID field, an Address 1 field, an Address 2 field, an Address 3 field, a Sequence Control field, an Address 4 field, a QoS Control field, an HT Control field, etc. The MAC header may consist of all of the aforementioned fields. The MAC header may consist of some of the aforementioned fields.

[0054] Figure 5 shows an example of a MAC frame format according to one aspect of this embodiment. In Figure 5, the MAC frame format may consist of a MAC header, a Frame Body, and an FCS. In Figure 5, the MAC header may consist of a Frame Control field, a Duration field, an Address 1 field, an Address 2 field, an Address 3 field, a Sequence Control field, an Address 4 field, and a QoS Control field. The MAC frame format may also be an MPDU.

[0055] The MAC header's Frame Control field may consist of subfields such as Protocol Version, Type, Subtype, To DS, From DS, More Fragments, Retry, Power Management, More data, Protected Frame, +HTC, Control Frame Extension, Compressed SSID Present, ANO Present, BSS BW, Security, AP PM, etc. The MAC header's Frame Control field may consist of some of the aforementioned subfields. The MAC header's Frame Control field may consist of all of the aforementioned subfields. The MAC header's Frame Control field may consist of a specific combination of subfields depending on the frame type.

[0056] The frame type may be indicated in the Type subfield contained in the Frame Control field of the MAC header. Control frame, Management frame, and Data frame may be defined as frame types. The Type subfield may indicate any of these three. For example, the Type subfield may be a two-bit subfield. If the Type subfield is set to 00, the frame type may be a Management frame. If the Type subfield is set to 01, the frame type may be a Control frame. If the Type subfield is set to 10, the frame type may be a Data frame.

[0057] A Management frame may be a frame for managing the connection status between devices. A Control frame may be a frame for managing the communication status between devices. A Data frame may be a frame containing the actual data to be transmitted.

[0058] The Subtype subfield in the Frame Control field of the MAC header may indicate the frame's subtype. Possible subtypes of the frame include Association Request, Association Response, Reassociation Request, Reassociation Response, Probe Request, Probe Response, Beacon, ATIM, Disassociation, Authentication, Deauthentication, Action, Block Ack Request, Block Ack, PS-Poll, RTS, CTS, Ack, CF-End, Data, QoS Data, etc. Other subtypes may also be defined.

[0059] The frame subtype may be determined from the Type subfield and Subtype subfield contained in the Frame Control field of the MAC header. The Subtype subfield may be a 4-bit subfield. If the Type subfield is set to 00, the Type subfield may indicate a Management frame. If the Type subfield is set to 01, the Type subfield may indicate a Control frame. If the Type subfield is set to 10, the Type subfield may indicate a Data frame.

[0060] For example, if the Type subfield indicates Management frame and the Subtype subfield is set to 0000, the subtype may be Association Request. If the Type subfield indicates Management frame and the Subtype subfield is set to 0001, the subtype may be Association Response. If the Type subfield indicates Management frame and the Subtype subfield is set to 0010, the subtype may be Reassociation Request. If the Type subfield indicates Management frame and the Subtype subfield is set to 0011, the subtype may be Reassociation Response. If the Type subfield indicates Management frame and the Subtype subfield is set to 0100, the subtype may be Probe Request. If the Type subfield indicates Management frame and the Subtype subfield is set to 0101, the subtype may be Probe Response. If the Type subfield indicates Management frame and the Subtype subfield is set to 1000, the subtype may be Beacon.

[0061] A Beacon frame may contain information such as the Beacon's period and SSID. A Beacon frame may be a frame that is periodically sent to the STA in the BSS. An Association Response frame may contain information such as the Status code. An Association Response frame may be a frame sent in response to a received Association Request frame. A Reassociation Response frame may contain information such as the Status code. A Reassociation Response frame may be a frame sent in response to a received Reassociation Request frame. A Probe Response frame may contain information such as the Beacon's period and SSID. A Probe Response frame may be a frame sent in response to a received Probe Request frame.

[0062] For example, if the Type subfield indicates Control frame and the Subtype subfield is set to 1011, the subtype may be RTS. If the Type subfield indicates Control frame and the Subtype subfield is set to 1100, the subtype may be CTS. If the Type subfield indicates Control frame and the Subtype subfield is set to 1101, the subtype may be Ack.

[0063] For example, if the Type subfield indicates Data frame and the Subtype subfield is set to 0000, then subtype may be Data. If the Type subfield indicates Data frame and the Subtype subfield is set to 1000, then subtype may be QoS Data.

[0064] The Frame body field of a MAC frame format may consist of fields and elements defined for each subtype of management frame. Fields and elements are displayed in a specified relative order, and non-existent fields or elements may be skipped. If the STA encounters an element ID that it does not recognize in the frame body of a received management frame, it ignores that element and continues to parse the rest of the management frame body (if any) in search of additional elements with recognizable element IDs. In other words, the frame body of a management frame may contain one or more elements.

[0065] The element format of each element included in the Frame body may be defined in the Element ID field, Length field, Element ID Extension field, information field, etc. The Information field may contain information specific to the element. For example, if Element ID is 61, it may indicate an element for HT Operation. For example, if Element ID is 191, it may indicate an element for VHT Capabilities. For example, if Element ID is 192, it may indicate an element for VHT Operation. For example, if Element ID is 255, it may indicate an element for HE Capabilities. For example, if Element ID is 255, it may indicate an element for HE Operation.

[0066] An Operation element may be information for controlling the operation of STA within BSS. An Operation element may consist of multiple fields.

[0067] An HT Operation element may be defined by the Element ID field, Length field, Primary Channel field, HT Operation information field, and Basic HT-MCS Set field. The Primary Channel field may indicate the channel number of the primary channel. As described above, the channel position may be indicated by the channel number. The HT Operation information field may consist of the Secondary Channel Offset field, STA Channel Width field, etc. The Secondary Channel Offset field may indicate the offset of the secondary channel relative to the primary channel. If the Secondary Channel Offset field is set to 1, the secondary channel may be located above the primary channel. If the Secondary Channel Offset field is set to 3, the secondary channel may be located below the primary channel. If the Secondary Channel Offset field is set to 0, the secondary channel may not exist. The STA Channel Width field may define the channel width that the STA can use for transmission. The STA Channel Width field may be set to 0 for 20MHz. The STA Channel Width field may be set to 1 if it allows the use of any channel within the supported channel width set. The operation of HT STA(s) within the BSS may be controlled by an HT Operation element. In other words, the HT Operation element may be an operation element that controls the operation of HT STA within the BSS.

[0068] An HT operation element may be sent in a Management frame. An HT operation element may be sent in a Control frame. An HT operation element may be sent in a Data frame. For example, an HT operation element may be sent in a Beacon frame. For example, an HT operation element may be sent in an Association Response frame. For example, an HT operation element may be sent in a Reassociation Response frame. For example, an HT operation element may be sent in a Probe Response frame.

[0069] A VHT Operation element may be defined by an Element ID field, a Length field, a VHT Operation Information field, and a Basic VHT-MCS And NSS Set field. The VHT Operation Information field may consist of a Channel Width field, a Channel Center Frequency Segment 0 field, and a Channel Center Frequency Segment 1 field. The operation of VHT STA(s) within the BSS may be controlled by an HT Operation element and a VHT Operation element. In other words, a VHT Operation element may be an operation element that controls the operation of VHT STA within the BSS.

[0070] A VHT operation element may be sent in a Management frame. A VHT operation element may be sent in a Control frame. A VHT operation element may be sent in a Data frame. For example, a VHT operation element may be sent in a Beacon frame. For example, a VHT operation element may be sent in an Association Response frame. For example, a VHT operation element may be sent in a Reassociation Response frame. For example, a VHT operation element may be sent in a Probe Response frame.

[0071] The Channel Width field in the VHT Operation information field, along with the STA channel width field in the HT operation element, may define the BSS bandwidth. The Channel Width field may be set to 0 for a 20MHz or 40MHz BSS bandwidth. The Channel Width field may be set to 1 for an 80MHz, 160MHz, or 80+80MHz BSS bandwidth. The Channel Width field may be set to 2 for a 160MHz BSS bandwidth. The Channel Width field may be set to 3 for an 80+80MHz BSS bandwidth. Values ​​in the Channel Width field ranging from 4 to 255 may be reserved.

[0072] The Channel Center Frequency Segment 0 field within the VHT Operation information field may define the channelcenter frequency for VHT BSS of 20MHz, 40MHz, 80MHz, 160MHz, or 80+80MHz. For BSS bandwidths of 20MHz, 40MHz, or 80MHz, the Channel Center Frequency Segment 0 field may indicate the channel center frequency index for the 20MHz, 40MHz, or 80MHz channel on which the VHT BSS operates. For a 160MHz BSS bandwidth and a Channel Width subfield of 1, the Channel Center Frequency Segment 0 field may indicate the channel center frequency index for the 80MHz channel segment containing the primary channel. For a 160MHz BSS bandwidth and a Channel Width subfield of 2, the Channel Center Frequency Segment 0 field may indicate the channel center frequency index for the 160MHz channel on which the VHT BSS operates. The Channel Center Frequency Segment0 field may indicate the channel center frequency index of the primary 80MHz channel of the VHT BSS when the BSS bandwidth is 80 + 80MHz and the Channel Width subfield is 1 or 3.

[0073] The Channel Center Frequency Segment 1 field in the VHT Operation information field may define the channel center frequency for a 160MHz or 80+80MHz VHT BSS. The Channel Center Frequency Segment 1 field may be set to 0 for a BSS bandwidth of 20MHz, 40MHz, or 80MHz. The Channel Center Frequency Segment 1 field may indicate the channel center frequency index of the 160MHz channel on which the VHTBSS operates when the BSS bandwidth is 160MHz and the Channel Width subfield is 1. The Channel Center Frequency Segment 1 field may be set to 0 when the BSS bandwidth is 160MHz and the Channel Width subfield is 2. The Channel Center Frequency Segment 1 field may indicate the channel center frequency index of the Secondary 80MHz channel of the VHT BSS when the BSS bandwidth is 80+80MHz and the Channel Width subfield is 1 or 3.

[0074] The HE Operation element format may consist of fields such as Element ID, Length, ElementID Extension, HE Operation Parameter, BSS Color Information, Basic HE-MCS And NSS Set, VHT Operation Information, Max Co-Hosted BSSID Indicator, and 6GHz Operation Information. When operating in the 2.4GHz band, the HE STA in the HE BSS may be controlled by the HT Operation element and the HE Operation element. When operating in the 5GHz band, the HE STA in the HE BSS may be controlled by the HT Operation element, the VHT Operation element (if present), and the HE Operation element. When operating in the 6GHz band, the HE STA in the HE BSS may be controlled by the HE Operation element. In other words, the HE Operation element may be an operation element that controls the operation of the HE STA in the BSS.

[0075] HE operation elements may be sent in a Management frame. HE operation elements may be sent in a Control frame. HE operation elements may be sent in a Data frame. For example, HE operation elements may be sent in a Beacon frame. For example, HE operation elements may be sent in an Association Response frame. For example, HE operation elements may be sent in a Reassociation Response frame. For example, HE operation elements may be sent in a Probe Response frame.

[0076] The HE Operation Parameter field format of the HE Operation element format may consist of the Default PE Duration subfield, TWT Required subfield, TXOP Duration RTS Threshold subfield, VHT Operation Information Present subfield, Co-Hosted BSS subfield, ER SU Disabled subfield, 6GHz Operation Information Present subfield, Reserved subfield, etc. The VHT Operation Information Present subfield may be set to 1 to indicate that the VHT Operation Information field exists in the HE Operation element, and to 0 otherwise. The 6GHz Operation Information Present field may be set to 1 to indicate that the 6GHz Operation Information field exists, and to 0 otherwise.

[0077] The BSS Color Information field format of the HE Operation element format may consist of a BSS Color subfield, a Partial BSS Color subfield, a BSS Color Disabled subfield, and so on.

[0078] The 6GHz Operation Information field in the HE Operation element format may provide channel and bandwidth information related to 6GHz operation. The 6GHz Operation Information field format may consist of a Primary channel field, a Control field, a Channel Center Frequency Segment 0 field, a Channel Center Frequency Segment 1 field, a Minimum Rate field, etc. The Primary Channel field may indicate the channel number of the primary channel at 6GHz. The Channel Center Frequency Segment 0 field may indicate the channel center frequency index of a 20MHz, 40MHz, 80MHz, 160MHz, or 80+80MHz channel of the BSS operating at 6GHz. The Channel Center Frequency Segment 0 field may indicate the channel center frequency index of the primary 80MHz channel if the BSS channel width is 160MHz or 80+80MHz. The Channel Center Frequency Segment 1 field may indicate the channel center frequency index of a 160MHz channel of the BSS operating at 6GHz. The Channel Center Frequency Segment 1 field may indicate the channel center frequency index of the secondary 80MHz channel when the channel width is 80+80MHz. The Control field format within the 6GHz Operation Information field format may consist of the Channel Width field, Duplicate Beacon subfield, Regulatory Info subfield, Reserved subfield, etc.The Channel Width field indicates the BSS channel width and may be set to 0 for 20MHz, 1 for 40MHz, 2 for 80MHz, or 3 for 80+80MHz or 160MHz.

[0079] The EHT Operation element format may also be an Operation element for controlling an EHT STA operating in an EHT BSS. When operating in the 2.4GHz band, an EHT STA in an EHT BSS may be controlled by an HT Operation element, an HE Operation element, and an EHT Operation element. When operating in the 5GHz band, an EHT STA in an EHT BSS may be controlled by an HT Operation element, a VHT Operation element (if present), an HE Operation element, and an EHT Operation element. When operating in the 6GHz band, an EHT STA in an EHT BSS may be controlled by an HE Operation element and an EHT Operation element.

[0080] The EHT Operation element format may consist of the Element ID, Length, Element ID Extension, EHT Operation Parameter, Basic EHT-MCS And Nss Set, and EHT Operation Information fields. The EHT Operation Information field may consist of the Control subfield, CCFS0 subfield, CCFS1 subfield, and Disabled Subchannel Bitmap subfield. The Control subfield may include a Channel Width subfield. The Channel Width subfield may be a subfield for defining the EHT BSS bandwidth. The Channel Width subfield may define 0 for a 20MHz EHT BSS bandwidth. The Channel Width subfield may define 1 for a 40MHz EHT BSS bandwidth. The Channel Width subfield may define 2 for an 80MHz EHT BSS bandwidth. The Channel Width subfield may define 3 for a 160MHz EHT BSS bandwidth. The Channel Width subfield may define 4 for a 320MHz EHT BSS bandwidth. The CCFS0 subfield may define the center frequency of the primary 80MHz channel for 20MHz EHT BSS, 40MHz EHT BSS, 80MHz EHT BSS, 160MHz EHT BSS, or the primary 160MHz channel for 320MHz EHT BSS. The CCFS0 subfield may also indicate the channel center frequency index of the 20MHz channel, 40MHz channel, or 80MHz channel on which the EHT BSS operates, for a 20MHz BSS bandwidth, 40MHz BSS bandwidth, or 80MHz BSS bandwidth.The CCFS0 subfield may indicate the channel center frequency index of the primary 80MHz channel for a 160MHz BSS bandwidth. The CCFS0 subfield may indicate the channel center frequency index of the primary 160MHz channel for a 320MHz BSS bandwidth. The CCFS1 subfield may define the center frequency of a 160MHz EHT BSS or a 320MHz EHT BSS. The CCFS1 subfield may be set to 0 for a 20MHz BSS bandwidth, a 40MHz BSS bandwidth, or an 80MHz BSS bandwidth. The CCFS1 subfield may index the center frequency of a 160MHz channel for a 160MHz BSS bandwidth. The CCFS1 subfield may index the center frequency of a 320MHz channel for a 320MHz BSS bandwidth.

[0081] An A-MSDU (Aggregate MSDU) may be a sequence of A-MSDU subframes. Each A-MSDU subframe may consist of an A-MSDU subframe header, followed by the MSDU and padding of 0 to 3. In an A-MSDU subframe, the A-MSDU subframe header may include a DA field, an SA field, and a Length field. The DA and SA fields may contain values ​​passed in MA-UNITDATA.request and MAUNITDATA.indication primitives. The Length field may contain the length of the MSDU in octets (i.e., 8 bits).

[0082] Figure 6 shows an example of an A-MSDU according to one aspect of this embodiment. In Figure 6, the MAC frame format may consist of a MAC header, a Frame Body, and an FCS. Here, the MAC header may consist of a Frame Control field, a Duration field, an Address 1 field, an Address 2 field, an Address 3 field, a Sequence Control field, an Address 4 field, and a QoS Control field. The MAC frame format may also be an MPDU. The Frame Body may consist of n A-MSDU subframes. Each A-MSDU may consist of an A-MSDU subframe header, an MSDU, and Padding. The A-MSDU subframe header may consist of a DA field, an SA field, and a Length field.

[0083] An A-MPDU (Aggregate MPDU) may consist of a sequence of one or more A-MPDU subframes and a variable amount of EOFPadding. Each A-MPDU subframe may optionally consist of an MPDU followed by an MPDU delimiter. Each nonfinal A-MPDU subframe within an A-MPDU may have padding octets added to make the subframe length a multiple of four octets. The EOF Padding field may consist of an EOF Padding subframe field and an EOF Padding Octets field. The A-MPDU pre-EOF padding may refer to the contents of the A-MPDU without including the EOF Padding field. The MPDU delimiter may consist of an EOF field, a Reserved field, an MPDULength field, a CRC field, and a Delimiter Signature field.

[0084] Figure 7 shows an example of an A-MPDU according to one embodiment of this model. In Figure 7, the A-MPDU may consist of n A-MPDU subframe fields and an EOF Padding field. The n A-MPDU subframe fields may be referred to as A-MPDU pre-EOF padding. Each A-MPDU subframe field may consist of an MPDU delimiter field, an MPDU field, and a padding field. The MPDU delimiter field may consist of an EOF field, a Reserved field, an MPDU Length field, a CRC field, and a Delimiter Signature field. The EOF Padding field may consist of an EOF Padding subframe field and an EOF Padding Octets field.

[0085] The process of dividing an MSDU or MMPDU (MAC Management Protocol Data Unit) into smaller MAC-level frames, or MPDUs, may be called fragmentation. A MAC may fragment and reassemble an MSDU or MMPDU that is carried in individually addressed MPDUs.

[0086] Figure 8 shows an example of Fragmentation according to one aspect of this embodiment. In Figure 8, the MSDU may be fragmented into n parts. The MSDU is divided into n Frame Bodies, and each Frame Body may be assigned a MAC HDR (header) and a CRC (Cyclic Redundancy Check).

[0087] A PPDU may consist of a PHY preamble, a PHY header, a PSDU (PHY Service Data Unit), etc. A PPDU may be assigned L-STF, L-LTF, and L-SIG. A PPDU may be assigned HT-STF, HT-LTF, and HT-SIG. A PPDU may be assigned VHT-STF, VHT-LTF, VHT-SIG-A, and VHT-SIG-B. A PPDU may be assigned HE-STF, HE-LTF, HE-SIG-A, and HE-SIG-B. A PPDU may be assigned HT-STF, HT-LTF, and HT-SIG in addition to L-STF, L-LTF, and L-SIG. A PPDU may be assigned VHT-STF, VHT-LTF, VHT-SIG-A, and VHT-SIG-B in addition to L-STF, L-LTF, and L-SIG. In addition to L-STF, L-LTF, and L-SIG, PPDU may also be assigned HE-STF, HE-LTF, HE-SIG-A, and HE-SIG-B.

[0088] Figure 9 shows an example of a PPDU according to one aspect of this embodiment. In Figure 9, L-STF and L-LTF may be added to the PPDU in the PHY layer. In Figure 9, the PPDU may consist of PSDU, PHYpreamble, PHY header, Tail, and Padding. Here, the PSDU may be an A-MPDU in the MAC sublayer. The A-MPDU may consist of multiple MAC frame formats. Here, one MAC frame format may consist of a MAC header field, an A-MSDU field, and an FCS field.

[0089] The time interval between frames may be referred to as IFS (Inter-Frame Space). The STA may use carrier sensing functionality at a specified time interval to determine if the medium is idle. In other words, the STA may perform carrier sensing over the IFS period to determine whether the medium is idle or not.

[0090] Multiple types of IFS may be defined. For example, IFS may include RIFS (Reduced Inter Frame Space), SIFS (Short Inter Frame Space), PIFS (Priority Inter Frame Space), DIFS (DCF Inter Frame Space), AIFS (Arbitration Inter Frame Space), EIFS (Extended Inter Frame Space), SBIFS (Short Beamforming Inter Frame Space), BRPIFS (Beam Refinement Inter Frame Space), MBIFS (Medium Beamforming Inter Frame Space), and LBIFS (Long Beamforming Inter Frame Space).

[0091] The time interval may differ depending on the type of IFS. For example, PIFS may have a longer time interval than SIFS. DIFS may also have a longer time interval than PIFS. The type of IFS may provide a priority level for access to the wireless medium. In other words, an IFS with a shorter time interval may be an IFS with a higher priority level for access to the wireless medium.

[0092] SIFS (Short Inter Frame Space) may be the time from the end of the last symbol or signal extension (if any) of the previous frame until the first symbol of the preamble of the next frame is seen on the radio medium.

[0093] Priority Inter Frame Space (PIFS) may be used to control access to media in order to obtain priority access. PIFS may also be used to perform Clear Channel Assessment (CCA) on secondary 20MHz, secondary 40MHz, and secondary 80MHz channels before transmission at 40MHz, 80MHz, and 160MHz.

[0094] Clear Channel Assessment (CCA) may determine the current usage status of a wireless medium. CCA may be a function at the physical layer for determining the current usage status of a wireless medium. CCA may also be referred to as the CCA function.

[0095] DIFS (DCF Inter Frame Space) may be used by an STA operating with DCF to transmit data frames (MPDUs) and management frames (MMPDUs). An STA using DCF may transmit after successfully receiving a frame, if the CS (Carrier Sense) mechanism determines that the medium is idle at a TxDIFS slot boundary, and the value of the STA's backoff counter is zero.

[0096] For example, carrier sense may include backoff and / or EDCA and / or channel access and / or CCA.

[0097] AIFS (Arbitration Inter Frame Space) may be used for QoS STAs that access media using EDCAF.

[0098] EIFS (Extended Inter Frame Space) may be used in DCF when the medium is immediately determined to be idle after receiving a frame with an incorrect FCS value.

[0099] The basic method of accessing MACs used by STAs may be DFC (Distributed Coordination Function). DCF may be a class of coordination function where the same coordination logic is always active in each STA within the BSS when the network is operational. DCF may be a type of CSMA / CA. DCF may be a function that needs to be implemented in all STAs.

[0100] To initiate a transmission, the STA detects the medium and determines whether another STA is currently transmitting. If the medium is not busy, the STA may proceed with the transmission. If the medium is determined to be busy, the STA postpones transmission until the current transmission is complete.

[0101] In the CSMA / CA distributed algorithm, there is a specified time gap between frame exchange sequences. This specified time gap between frame exchange sequences may be referred to as the IFS (Interval Free Time). Before attempting to transmit, the transmitting STA (Signal Agent) ensures that the medium is idle for a required period. This required period may be the specified time gap between frame exchange sequences. This required period may be referred to as the IFS.

[0102] The STA may initialize the backoff counter to a random backoff counter before attempting to transmit again after a delay or immediately after a successful transmission. The STA may decrement the backoff counter once per aSlotTime period while the medium is idle. aSlotTime may be the duration of the slot. The duration of the slot may be the duration of the slot that the MAC uses to define the IFS. Alternatively, aSlotTime may be a predetermined duration (e.g., a fixed duration in microseconds).

[0103] The basic media access protocol may be DCF. DCF enables automatic sharing of media between compatible PHYs through the use of CSMA / CA and a random backoff counter after the media becomes busy. All individually addressed traffic uses an immediate positive acknowledgment (Ack frame), and if an Ack frame is not received, the sender schedules a retransmission. Multiple STAs may be waiting for the media to become available, and collisions are most likely when the media goes from busy to idle. Therefore, a random backoff procedure is necessary to resolve media contention. An STA transmission may interfere with (collision with) another STA transmission even if the carrier sense function (CS function) indicates that the media is not busy. Interference may be identified when the expected response frame is not received.

[0104] An STA that wants to initiate the transfer of data frames or management frames using DCF may use a carrier sense mechanism to determine the busy / idle state of the medium. If the medium is busy, the STA waits without interruption for an IFS until the medium is determined to be idle. Here, the type of IFS may be EIFS if the transition to the last idle state was due to the detection of a frame that was not properly received on the medium. Otherwise, the type of IFS may be DIFS. After the medium is idle in DIFS or EIFS, the STA may generate a random backoff count for additional delay time before transmission. However, if the backoff counter already contains a non-zero value, the selection of a random number is not required. The backoff counter may be a pseudo-random integer obtained by subtracting a uniform variance between [0, CW]. CW may be an integer within the range of aCWmin and aCWmax values, which are characteristics of the PHY. CW may be greater than or equal to aCWmin and less than or equal to aCWmax. CW may be referred to as the Contention Window.

[0105] The contention window parameter may take the initial value of aCWmin. The contention window takes a series of values ​​each time an MPDU transmission attempt fails and any STA retry increases until the contention window reaches the value of aCWmax. Once the contention window reaches aCWmax, it maintains the value of aCWmax until the contention window is reset. If a data frame or management frame is successfully transmitted, the contention window may be reset to aCWmin. If the SSRC reaches dot11ShortRetryLimit, the contention window may be reset to aCWmin. The set of contention window values ​​may be in ascending order as integers obtained by powers of 2 minus 1, starting from the PHY-specific aCWmin value and continuing up to the PHY-specific aCWmax. For example, if aCWmin is 7 and aCWmax is 255, the set of contention window values ​​may be a set containing 7, 15, 31, 63, 127, and 255.

[0106] For example, in OFDM PHY characteristics, with a 20MHz channel spacing, aSlotTime may be 9μs. In OFDM PHY characteristics, with a 20MHz channel spacing, aCWmin may be 15. In OFDM PHY characteristics, with a 20MHz channel spacing, aCWmax may be 1023.

[0107] A QoS facility may include an additional coordinating function called HCF (Hybrid Coordination Function), which is only available in a QoS network configuration. HCF may be implemented in all QoS STAs. HCF is a coordinating function that combines aspects of competition-based and competition-free access methods to provide prioritized, parameterized QoS access to the radio medium for QoS STAs, and may continue to support non-QoS STAs for best-effort forwarding. HCF may include functionality provided by both EDCA (Enhanced Distributed Channel Access) and HCCA (HCF controlled channel access). HCF may use a competition-based channel access method called the EDCA mechanism for competition-based forwarding. HCF may use a controlled channel access method called the HCCA mechanism for competition-free forwarding.

[0108] HCCA (HCF Controlled Channel Access) may be a channel access mechanism used by a Hybrid Coordinator (HC) to coordinate the use of a non-contradiction-free medium by a QoS STA for individually addressed downlink, uplink, and direct-link transmissions.

[0109] The EDCA mechanism may use eight different User Priorities (UPs) to provide STAs with differentiated, distributed access to the wireless medium. UPs are values ​​associated with MAC Service Data Units (MSDUs) and may indicate how the MSDU should be handled. UPs may be assigned to MSDUs at higher layers of the MAC. UPs may take any value from 0 to 7. The EDCA mechanism may define four Access Categories (ACs) to support the delivery of traffic using STAs' UPs. ACs may be labels for a common set of EDCA parameters that QoS STAs use to compete for channels and transmit MSDUs with specific priorities. ACs may take any value from AC_BE, AC_BK, AC_VI, and AC_VO. AC_BE, AC_BK, AC_VI, and AC_VO may indicate access categories corresponding to best-effort, background, video, and voice, respectively.

[0110] A Quality of Service (QoS) facility may include extensions, channel access rules, frame formats, frame exchange sequences, and managed objects used to provide parameterized and prioritized QoS. A QoS STA may be an STA that implements the QoS function. A QoS AP may be an AP that supports the QoS function. A QoS BSS may be a BSS that provides the QoS function. An Infrastructure QoS BSS may include a QoS AP.

[0111] An Enhanced Distributed Channel Access Function (EDCA) is a logical function within a QoS STA that uses the EDCA to determine when a frame in a transmit queue with an associated AC is permitted to be transmitted over the radio medium. There may be one EDCFA per AC. The DCF and HCF may be defined to operate within the same BSS.

[0112] Each EDCAF may maintain a backoff counter measured in the backoff slot. When the backoff procedure is called, the backoff counter may be set to a randomly selected integer value in a uniform distribution from 0 to CW. AIFS may be defined as AIFSN × aSlotTime + aSIFSTime. For example, in OFDM PHY characteristics, for a 20MHz channel spacing, aSlotTime may be 9μs and aSIFTTime may be 16μs. AIFSN may differ for each AC. For example, if AC is AC_BK, AIFSN may be 7. If AC is AC_BE, AIFSN may be 3. If AC is AC_VI, AIFSN may be 2. If AC is AC_VO, AIFSN may be 2. CW may be in ascending order as a power of 2 minus 1 integer, starting from a PHY-specific CWmin value and continuing to a PHY-specific CWmax. CWmin and CWmax may differ for each AC. For example, if AC is AC_BK, CWmin may be aCWmin and CWmax may be aCWmax. If AC is AC_BE, CWmin may be aCWmin and CWmax may be aCWmax. If AC is AC_VI, CWmin may be {(aCWmin+1) / 2}-1 and CWmax may be aCWmin. If AC is AC_VO, CWmin may be {(aCWmin+1) / 4}-1 and CWmax may be {(aCWmin+1) / 2}-1. In OFDM PHY characteristics, with a 20MHz channel spacing, aCWmin may be 15. In OFDM PHY characteristics, with a 20MHz channel spacing, aCWmax may be 1023. The STA may decrement its backoff counter once for every aSlotTime period while the medium is idle. It takes a series of the following values ​​each time an MPDU transmission attempt fails and any STA's retry increases.

[0113] In HCF, the basic unit of assigning transmission rights to a radio medium may be a TXOP. A TXOP (Transmission Opportunity) may be a time interval in which a particular QoS STA has the right to initiate a frame exchange sequence on the radio medium. A TXOP may be defined by its start time and maximum duration. A TXOP may be acquired through EDCA. That is, an STA may acquire a TXOP if it performs an EDCA.

[0114] Figure 10 is a diagram showing an example of a backoff procedure according to one aspect of this embodiment. In Figure 10, the horizontal axis may represent time. 1001 may be a transmission by STA#1. 1002 may be an IFS. 1003 may be a backoff counter. 1003 may also be called a contention window. 1004 may be a transmission by STA#2. In Figure 10, STA#2 may detect 1001 on the channel. While STA#2 is detecting 1001, it may determine that the channel is busy. In other words, 1001 may be the period during which the channel is determined to be busy. STA#2 may perform carrier sense and determine whether the channel is busy or not. When the period of 1001 has ended and STA#2 determines that the channel is idle, it may perform carrier sense during the period of 1002. For example, 1002 may be a DIFS. 1002 may also be an AIFS. STA#2 may start 1003 if it is idle during the period 1002. 1003 decrements the backoff counter while the channel is idle. For example, six backoff counters may be generated in 1003. The backoff counter is decremented while the channel is idle, and when the backoff counter reaches 0, STA#2 may transmit (1004). Here, the backoff counter may be determined between 0 and CW. CW may be a value selected from a range of values ​​between aCWmin and aCWmax. The channel may be referred to as the radio medium.

[0115] The carrier sense mechanism may be a mechanism that combines the Network Allocation Vector (NAV) status and the physical carrier sense of the STA transmitter to determine whether the medium is busy or idle. The NAV may be maintained by each STA and may be an indicator of the period during which transmission to the wireless medium is not initiated by the STA, regardless of whether the STA's Clear Channel Assessment (CCA) function senses that the medium is busy.

[0116] The carrier sense mechanism in STA may be performed in the physical layer processing unit SU3 and / or the MAC layer processing unit SU3. The carrier sense mechanism in AP may be performed in the physical layer processing unit AU3 and / or the MAC layer processing unit AU3.

[0117] The NAV may be a counter that counts down to zero at a constant rate. The STA may indicate that the virtual carrier sense is idle if the NAV counter is zero. The STA may indicate that the virtual carrier sense is busy if the NAV counter is not zero. Physical and virtual carrier sense functions may be used to determine the state of the medium. If either the physical or virtual carrier sense function indicates busy, the medium may be considered busy. If both the physical and virtual carrier sense functions indicate idle, the medium may be considered idle. The virtual carrier sense may be referred to as the NAV. The NAV may be provided by all MACs. The NAV counter may be referred to as the NAV timer.

[0118] The physical carrier sense function in the STA may be controlled by the physical layer processing unit SU3. The virtual carrier sense function in the STA may be controlled by the MAC layer processing unit SU4. The physical carrier sense function in the AP may be controlled by the physical layer processing unit AU3. The virtual carrier sense function in the AP may be controlled by the MAC layer processing unit AU4. The NAV in the STA may be controlled by the MAC layer processing unit SU4. The NAV in the AP may be controlled by the MAC layer processing unit AU4.

[0119] The STA may set the NAV if the address field of a received frame is not its own address. The STA may update the NAV using the information from any valid Duration field in the PSDU when it receives at least one valid frame in the PSDU. The STA may update the NAV if the value indicated by the Duration field of a received frame is greater than the current NAV value. The STA does not update the NAV if the RA (address) of a received frame is equal to the STA's own MAC address.

[0120] An STA may maintain two NAVs. An AP may maintain two NAVs. The two NAVs may be an intra-BSS NAV and a basic NAV. The intra-BSS NAV may be updated by an intra-BSS PPDU. The basic NAV may be updated by an inter-BSS PPDU. The basic NAV may be updated by a PPDU that cannot be classified as either an intra-BSS PPDU or an inter-BSS PPDU. An STA maintaining two NAVs may indicate that the medium is idle if the timers for both NAVs are 0. In other words, an STA maintaining two NAVs may indicate that the medium is idle if the timers for both the intra-BSS NAV and the basic NAV are 0. If at least one of the two NAV timers is not 0, the virtual CS indication may indicate that the medium is busy. In other words, if an STA or AP maintaining two NAVs has a timer that is not zero for at least one Intra-BSS NAV or basic NAV, the virtual CS indication may indicate that the medium is busy.

[0121] NAV may also be basic NAV. NAV may also be intra-BSS NAV. Basic NAV may also be NAV. Intra-BSS NAV may also be NAV. NAV may be called basic NAV. NAV may also be called intra-BSS NAV. Basic NAV may also be called NAV. Intra-BSS NAV may also be called NAV.

[0122] RTS (Request To send) may also be referred to as an RTS frame. CTS (Clear To send) may also be referred to as a CTS frame.

[0123] Carrier sense (CS) may be performed through both physical and virtual mechanisms. Carrier sense may also be referred to as a carrier sense function. Carrier sense may also be referred to as a carrier sense mechanism. A virtual carrier sense mechanism is implemented by distributing reservation information that notifies of the advance use of a medium. Exchanging RTS and CTS frames before the actual data frame may be one means of distributing medium reservation information. RTS and CTS frames may include a Duration field that defines the period during which the medium is reserved for transmitting the actual data frame and Ack frame. An STA that receives an RTS frame (sent by the originating STA) or a CTS frame (sent by the destination STA) processes the medium reservation. An STA can know that it is planning to transmit a data frame using the medium even if it does not receive from the originating STA. Medium reservation information may be distributed in the Duration / ID field of an individually addressed frame. The Duration / ID field may indicate the time (period) during which the medium is reserved. The Duration / ID field may indicate the time during which the medium is reserved, ending in the following Ack frame. In the case of fragment sequences, the Duration / ID field may indicate the time the medium is reserved until the end of the Ack frame following the next fragment. The RTS / CTS mechanism may also function when multiple BSSs using the same channel overlap. The medium reservation mechanism may also function across BSS boundaries.

[0124] The RTS (Request To Send) frame format may include a Frame Control field, a Duration field, an RA field, a TA field, and an FCS field. The Duration field of the RTS frame format may indicate the time (in microseconds) required to send the pending data or management frame, one CTS frame, one Ack frame, and three SIFS frames. The RA field of the RTS frame may be the address of the STA that is the intended direct recipient of the pending individually addressed frame. The TA field may be the address of the STA sending the RTS frame or the bandwidth signal TA of the STA sending the RTS frame.

[0125] The CTS (Clear To Send) frame format may include a Frame Control field, a Duration field, an RA field, and an FCS field. The Duration field of a CTS frame format sent in response to an RTS frame may be the Duration field of the immediately preceding RTS frame minus the time required to send the CTS frame and its corresponding SIFS. In other words, it may be the time required to send the pending data or management frame, one Ack frame, and two SIFS. If the CTS frame is the first frame in the exchange and the pending data or management frame requires an acknowledgment, the Duration field may be the time (in microseconds) required to send the pending data or management frame, two SIFS, and one Ack frame. If the CTS frame is the first frame in the exchange and the pending data or management frame does not require an immediate acknowledgment, the Duration field may be the time required to send the pending data or management frame and one SIFS. If the CTS frame is a response to an RTS frame, the RA field of the CTS frame may contain the address from the TA field of the RTS frame, and the individual / group bits may be set to 0. If the CTS frame is the first frame in a frame exchange, the RA field may contain the source MAC address.

[0126] Figure 11 shows an example of NAV according to one aspect of this embodiment. In Figure 11, the horizontal axis may represent time. For example, 1101 may be the timeline of AP#1's operation. 1102 may be the timeline of STA#1's operation. 1103 may be the timeline of AP#2's operation. 1104 may be the timeline of STA#2's operation. 1101, 1102, 1103, and 1104 may be timelines on the same channel. 1105 may be an RTS frame. 1106 may be the NAV period of AP#1. 1107 may be a CTS frame. 1108 may be the NAV period of STA#2. 1109 may be a Data frame. 1110 may be an AcK frame. 1111 may be an IFS. 1112 may be a contention window (backoff counter, backoff procedure). STA#1 may send 1105 to AP#2. Upon receiving 1105, AP#1 may set 1106 for the period indicated in the RTS Duration field. Upon receiving 1105, AP#2 may send 1107 to STA#1. Upon receiving 1107, STA#2 may set 1108 for the period indicated in the CTS Duration field. Upon receiving 1107, STA#1 may send 1109. Upon receiving 1109, AP#2 may send 1110 to STA#1. After 1106 is completed, AP#1 may start 1112 with 1111 if the channel is idle. After 1108 is completed, STA#2 may start 1112 with 1111 if the channel is idle. The period between 1105 and 1107 may be IFS. AP#2 may transmit 1107 if the channel is idle during the IFS period before transmitting 1107. There may be an IFS period between 1107 and 1109. STA#1 may transmit 1109 if the channel is idle during the IFS period before transmitting 1109. There may be an IFS period between 1109 and 1110. AP#2 may transmit 1110 if the channel is idle during the IFS period before transmitting 1110.Here, for example, AP#1 may be 202 in Figure 2. For example, STA#1 may be 207 in Figure 2. For example, AP#2 may be 206 in Figure 2. For example, STA#2 may be 2088 in Figure 2. 1101 may be a timeline of the operation of AP or STA. 1102 may be a timeline of the operation of AP or STA. 1103 may be a timeline of the operation of AP or STA. 1104 may be a timeline of the operation of AP or STA.

[0127] An STA or AP may perform a frame exchange. For example, a frame exchange may occur when an STA or AP sends an RTS and an STA or AP sends a CTS to the RTS. For example, a frame exchange may occur when an STA or AP sends a Trigger frame and an STA or AP sends a CTS to the Trigger frame. For example, a frame exchange may occur when an STA or AP sends an MU-RTS (MU-RTS Trigger frame) and an STA or AP sends a CTS to the MU-RTS. For example, a Trigger frame may be used by an AP to allocate a Resource Unit (RU) to an STA. A Trigger frame may be a frame containing at least a Common Info field and / or a User Info List field. The Common Info field may be a field for notifying multiple STAs of information common to all. The User Info List field may contain zero or more User Info fields. The User Info field may be a field for allocating RUs to each STA. For example, the User Info field may contain an RU allocation subfield. MU-RTS may be referred to as a MU-RTS Trigger frame.

[0128] The trigger frame may be sent in PPDU format. For example, the trigger frame may be sent in MU PPDU format. For example, the trigger frame may be sent in non-HT PPDU format. For example, the trigger frame may be sent in non-HT duplicate PPDU format.

[0129] Channel bonding may transmit using one or more 20MHz channels. Alternatively, channel bonding may transmit using multiple 20MHz channels. Channel bonding may transmit using multiple adjacent 20MHz channels. Channel bonding may also be called channel aggregation. Because channel bonding uses multiple channels simultaneously to transmit data, it provides broad bandwidth and improves data transmission speed. The multiple channels used for BSS members may include a primary channel and one or more secondary channels, and channel bonding may be performed using multiple of these channels.

[0130] The primary channel may be a channel common to all STAs that are members of the BSS. The primary 20MHz channel may be a 20MHz channel on which a 20MHz PPDU is transmitted in a 40MHz, 80MHz, 160MHz, or 80+80MHz BSS. The primary 40 channel may be a 40MHz channel on which a 40MHz PPDU is transmitted in an 80MHz, 160MHz, or 80+80MHz BSS. The primary 80 channel may be an 80MHz channel on which an 80MHz PPDU is transmitted in a 160MHz or 80+80MHz BSS. The primary 160MHz channel may be a 160MHz channel that includes the primary 20MHz channel in a 320MHz BSS. For example, the primary channel in a 20MHz, 40MHz, 80MHz, 160MHz, 80+80MHz, or 320MHz BSS may be referred to as the primary 20MHz channel. The primary channel may also be the channel on which the backoff procedure is performed. The primary channel may also be called the primary 20MHz channel. The primary 20MHz channel may also be called the primary channel. The primary channel may be the primary 20MHz channel. The primary 20MHz channel may also be the primary channel.

[0131] A secondary channel is a channel associated with a primary channel and may be a channel used to create a wider channel than the primary channel. For example, a secondary channel in a 40MHz, 80MHz, 160MHz, or 80+80MHz BSS may be referred to as a secondary 20MHz channel. In a 40MHz BSS, the secondary 20MHz channel may be a 20MHz channel adjacent to the primary 20MHz channel. In a 40MHz BSS, the secondary 20MHz channel may combine with the primary 20MHz channel to form a 40MHz channel. In an 80MHz BSS, the secondary 20MHz channel may be a 20MHz channel adjacent to the primary 20MHz channel. In an 80MHz BSS, the secondary 20MHz channel may combine with the primary 20MHz channel to form a primary 40MHz channel. In a 160MHz or 80+80MHz BSS, the secondary 20MHz channel may be a 20MHz channel adjacent to the primary 20MHz channel. The secondary 20MHz channel may be a channel that combines with the primary 20MHz channel to form a primary 40MHz channel in a 160MHz or 80+80MHz BSS. The secondary 40MHz channel may be a 40MHz channel adjacent to the primary 40MHz channel to form an 80MHz channel in an 80MHz BSS. The secondary 40MHz channel may be a 40MHz channel adjacent to the primary 40MHz channel to form a primary 80MHz channel in a 160MHz or 80+80MHz BSS.The secondary 80MHz channel may be an 80MHz channel that does not include the primary 20MHz channel in a 160MHz or 80+80MHz BSS. The secondary 80MHz channel may be combined with the primary 80MHz channel to form a 160MHz or 80+80MHz channel. In a 320MHz BSS, the secondary 160MHz channel may, together with the primary 160MHz channel, form a 320MHz channel in a 320MHz EHT BSS, and may be a 160MHz channel that does not include the primary 20MHz channel.

[0132] The non-primary channel may be any 20MHz channel other than the primary 20MHz channel in the 40MHz channel, 80MHz channel, 160MHz channel, 80+80MHz channel, and 320MHz channel.

[0133] Figure 12 shows an example of channel bonding according to one aspect of this embodiment. In Figure 12, 1201, 1202, 1203, 1204, 1205, 1206, 1207, and 1208 may each be 20 MHz channels. The horizontal axis of Figure 12 may represent frequency. Figure 12 may also represent a channel configuration of a BSS operating with a 160 MHz channel width. 1201 may be a primary 20 MHz channel. 1201 may also be referred to as the primary channel. 1202 may be a secondary 20 MHz channel. A secondary 40 MHz channel may be formed from 1203 and 1204. A secondary 80 MHz channel may be formed from 1205, 1206, 1207, and 1208. 1202, 1203, 1204, 1205, 1206, 1207, and 1208 may also be referred to as secondary channels.

[0134] When performing channel bonding, the STA may perform a backoff procedure on the primary 20MHz channel and channel sensing using PIFS immediately before transmission on the secondary channel. For example, in Figure 12, in order to transmit with a 160MHz channel width, the STA may perform a backoff procedure at 1201 and channel sensing during the PIFS period immediately before transmission at 1202, 1203, 1204, 1205, 1206, 1207, and 1208.

[0135] The Operating class may indicate an index to a set of values ​​for radio operation in a regulated domain. The Operating class value may indicate the frequency for a channel number, the center frequency of an available channel, and the maximum channel width that can be used. The Operating class value may also indicate the Channel starting frequency, Channel Spacing, Channelset, etc. The Channel set may be a list of valid integer channel numbers for the regulated domain and class. The Channel Spacing may be the frequency difference between non-overlapping adjacent channel center frequencies when using the maximum bandwidth of a single frequency segment permitted by the Operating class. The Operating class value may be transmitted in a frame. For example, the Operating class value may be transmitted in a Beacon frame. The Operating class value may be transmitted in a Probe Response frame. The Operating class value may also be an Operating class index.

[0136] The center frequency of the primary 20MHz channel may be determined by Channel starting frequency + 5 × dot11CurrentPrimaryChannel. dot11CurrentPrimaryChannel may be the channel number of the primary channel. The STA may determine dot11CurrentPrimaryChannel from the Operation element included in the frame received from the AP. The STA may determine dot11CurrentPrimaryChannel from the information in the Primary Channel field included in the HT Operation element. The STA may determine dot11CurrentPrimaryChannel from the Primary Channel field included in the HT Operation element. The STA may determine dot11CurrentPrimaryChannel from the information in the Primary channel field in the 6GHz Operation Information field included in the HE Operation element. For example, an STA that receives a Beacon frame from an AP may determine the primary channel from the Primary Channel field of the HT operation element included in the Beacon frame. The Channel starting frequency may be defined as dot11ChannelStartingFactor × 500kHz. dot11ChannelStartingFactor may be indicated in the Operating Class field.

[0137] The AP may include information related to the primary channel in the operation element and transmit it in the frame. The information related to the primary channel may be the channel number of the primary channel. The AP may include the channel number of the primary channel in the operation element and transmit it in the frame. For example, the AP may indicate the channel number of the primary channel in the Primary channel field of the HT operation element. For example, the AP may indicate the channel number of the primary channel in the Primary channel field within the 6GHz Operation Information field included in the HE operation element.

[0138] In channel bonding, the STA may perform a backoff procedure on the primary channel, sense the duration of the PIFS on the secondary channels, and then transmit. The STA may acquire an EDCA TXOP based on the activity of the primary channel. The transmission bandwidth may be determined by the CCA status of the nonprimary channels during the PIFS before transmission.

[0139] A PHY-CCA.indication primitive may be a primitive that indicates the current state of a medium from the PHY to the MAC entity. A PHY-CCA.indication primitive may include a STATE parameter. A PHY-CCA.indication primitive may include a channel-list parameter. The STATE parameter of a PHY-CCA.indication primitive may have one of two values: BUSY or IDLE. A PHY-CCA.indication primitive may include at least a STATE parameter. A PHY-CCA.indication primitive may include at least a channel-list parameter. A PHY-CCA.indication primitive may include at least a STATE and channel-list parameter. The STATE parameter value of a PHY-CCA.indication primitive may be BUSY if the PHY's evaluation of the channel indicates that the channel is unavailable. Otherwise, the STATE parameter value of a PHY-CCA.indication primitive may be IDLE. If STA is in the IDLE state, the channel-list parameter does not exist. If the CCA is determined by a single channel depending on the type of PHY being operated, the channel-list parameter does not exist. Otherwise, the channel-list parameter may contain a set of busy channels. That is, if the CCA is determined by multiple channels and they are BUSY, the channel-list parameter may exist. For example, the channel-list parameter entry may indicate primary, secondary, secondary40, and secondary80.The STATE parameter may also be called the STATUS parameter. The STATUS parameter may also be called the STATE parameter.

[0140] The PHY-CCA.indication primitive may contain a channel-list parameter. The channel-list parameter may contain one entry. One entry may be one of a set of entries. A set of entries may be defined. A set of entries may be called channel-list parameter entries. For example, a set of entries may include primary, secondary, secondary40, secondary80, primary1, primary2, secondary2, secondary4, and secondary8.

[0141] For example, if the channel-list parameter entry for PHY-CCA.indication primitive is set to primary, it may indicate that the primary channel is busy. For example, if the channel-list parameter entry for PHY-CCA.indication primitive is set to secondary, it may indicate that the secondary channel (secondary 20MHz channel) is busy. For example, if the channel-list parameter entry for PHY-CCA.indication primitive is set to secondary40, it may indicate that the secondary40 channel is busy. For example, if the channel-list parameter entry for PHY-CCA.indication primitive is set to secondary80, it may indicate that the secondary80 channel is busy.

[0142] The PHY-CCA.indication primitive may be generated (issued) when the channel state changes from idle to busy, or when the channel state changes from busy to idle, or when the entry in the channel-list parameter is changed. "Issuing a primitive" may be synonymous with "generating a primitive". "Generating a primitive" may be synonymous with "Issuing a primitive".

[0143] When MAC receives a PHY-CCA.indication with a channel-list parameter, it may determine which channels are idle. If the channel-list parameter entry in PHY-CCA.indication is primary, it may determine that there are no idle channels. If the channel-list parameter entry in PHY-CCA.indication is secondary, it may determine that the primary channel is idle. If the channel-list parameter entry in PHY-CCA.indication is secondary40, it may determine that the primary channel and the secondary 20MHz channel are idle. If the channel-list parameter entry in PHY-CCA.indication is secondary80, it may determine that the primary channel, the secondary 20MHz channel, and the secondary 40MHz channel are idle.

[0144] For example, in Figure 12, 1201 may be the primary channel. 1202 may be the secondary channel (secondary 20MHz channel). 1203 and 1204 may form a secondary 40MHz channel. 1205, 1206, 1207, and 1208 may form a secondary 80MHz channel. In other words, in Figure 12 with a bandwidth of 160MHz, the primary channel is 1201, the secondary channel (secondary 20MHz channel) is 1201, the secondary 40MHz channel is composed of 1203 and 1204, and the secondary 80MHz channel may be composed of 1205, 1206, 1207, and 1208. For example, STA may issue a primitive (PHY-CCA.indication(BUSY,{primary})) indicating that the primary channel is busy when the channel state changes from idle to busy on the primary channel (1201). STA may also issue a primitive (PHY-CCA.indication(IDLE,{primary})) indicating that the primary channel is idle when the channel state changes from busy to idle on the primary channel. If a primitive (PHY-CCA.indication(BUSY,{primary}))) indicating that the primary channel is idle is issued on the primary channel, it may be determined that there are no idle channels. STA may also issue primitives related to the secondary channel (1202) when the primary channel is idle.The STA may issue a primitive (PHY-CCA.indication(IDLE,{secondary})) indicating that the secondary channel (secondary 20MHz channel) is idle if it is idle. The STA may issue a primitive (PHY-CCA.indication(BUSY,{secondary})) indicating that the secondary channel (secondary 20MHz channel) is busy if it is busy. PHY-CCA.indication(IDLE,{secondary}) may indicate that both the primary channel and the secondary channel are idle. PHY-CCA.indication(BUSY,{secondary}) may indicate that the primary channel is idle and the secondary channel is busy. The STA may issue primitives related to the secondary 40MHz channel (composed of 1202 and 1204) if both the primary channel and the secondary 20MHz channel are idle. The STA may issue a primitive (PHY-CCA.indication(IDLE,{secondary40})) indicating that the secondary 40MHz channel is idle if it is idle. The STA may also issue a primitive (PHY-CCA.indication(BUSY,{secondary40})) indicating that the secondary 40MHz channel is busy if it is busy. PHY-CCA.indication(IDLE,{secondary40}) may indicate that the primary channel, secondary channel, and secondary 40MHz channel are idle.PHY-CCA.indication(IDLE,{secondary 40}) may indicate that the primary channel and secondary channel are idle and the secondary 40MHz channel is busy. The STA may issue primitives related to the secondary 80MHz channel (composed of 1205-1208) if the primary channel, secondary 20MHz channel, and secondary 40MHz channel are idle. The STA may issue primitives (PHY-CCA.indication(IDLE,{secondary80})) indicating that the secondary 80MHz channel is idle if the secondary 80MHz channel is idle. The STA may issue primitives (PHY-CCA.indication(BUSY,{secondary80})) indicating that the secondary 80MHz channel is busy if the secondary 80MHz channel is busy. PHY-CCA.indication(IDLE,{secondary 80}) may indicate that the primary channel, secondary channel, secondary 40MHz channel, and secondary 80MHz channel are idle. PHY-CCA.indication(IDLE,{secondary 80}) may also indicate that the primary channel, secondary channel, and secondary 40MHz channel are idle, and the secondary 80MHz channel is busy.

[0145] The STA may determine the PHY-CCA.indication primitive in the physical layer processing unit SU3. The STA may indicate the PHY-CCA.indication primitive determined in the physical layer processing unit SU3 to the MAC layer processing unit SU4. The AP may issue the PHY-CCA.indication primitive in the physical layer processing unit AU3. The AP may indicate the PHY-CCA.indication primitive determined in the physical layer processing unit AU3 to the MAC layer processing unit AU4.

[0146] An STA with an operation channel width of W MHz may detect the start of a PPDU occupying at least the primary 20 MHz channel with a probability of a predetermined percentage or higher (e.g., 90% or higher) and if the power of the preamble or PPDU measured within the primary 20 MHz channel is above a predetermined value (e.g., -82 dBm or higher), it may issue a PHY-CCA.indication(BUSY, {primary}) primitive within the aCCATime period. In other words, an STA may issue a PHY-CCA.indication(BUSY, {primary}) primitive when it receives a non-HT duplicate or PPDU exceeding -82 dBm on the primary 20 MHz channel. -82 dBm may be a threshold for determining whether the channel is idle or busy.

[0147] The receiver issues a PHY-CCA.indication(BUSY, {primary}) primitive for any signal that exceeds a predetermined threshold (-62dBm) that is a certain value (e.g., 20 dB) higher than the sensitivity of the minimum modulation and coding rate on the primary 20 MHz channel, within a period of aCCATime after the signal arrives at the receiver's antenna. Thereafter, as long as the threshold remains exceeded, the receiver does not issue a PHY-CCA.indication(BUSY,{secondary}), PHY-CCA.indication(BUSY,{secondary40}), PHY CCA.indication(BUSY,{secondary80}), or PHY-CCA.indication(IDLE) primitive. In other words, the receiver may issue a PHY-CCA.indication(BUSY, {primary}) primitive when it receives any signal that exceeds -62dBm on the primary 20 MHz channel. -62dBm may be a threshold used to determine whether the channel is idle or busy.

[0148] The PHY issues the PHY-CCA.indication(BUSY, {secondary}) primitive if there are no conditions to issue the PHY-CCA.indication(BUSY, {primary}) primitive, and any signal in the secondary 20 MHz channel exceeds a threshold of -62 dBm or more within aCCATime after reaching the receiver antenna, in idle operating channel widths of 40 MHz, 80 MHz, 160 MHz, and 80+80 MHz. In this case, the PHY does not issue the PHY-CCA.indication(BUSY, {secondary40}), PHY-CCA.indication(BUSY, {secondary80}), or PHY-CCA.indication(IDLE) primitive. The PHY issues the PHY-CCA.indication(BUSY, {secondary}) primitive if there are no conditions to issue the PHY-CCA.indication(BUSY, {primary}) primitive, and in idle operating channel widths of 40MHz, 80MHz, 160MHz, and 80+80MHz, a 20MHz preamble or PPDU of -72dBm or higher is detected on the secondary 20MHz channel with a probability of 90% or higher within the aCCAMidTime period. -72dBm may be a threshold used to determine whether a channel is idle or busy.

[0149] The PHY issues the PHY-CCA.indication(BUSY, {secondary}) primitive if there are no conditions to issue the PHY-CCA.indication(BUSY, {secondary}) or PHY-CCA.indication(BUSY, {secondary}) primitive, and any signal in the secondary 40 MHz channel exceeds a threshold of -59 dBm or more within aCCATime after reaching the receiver antenna, in an idle operating channel width of 80 MHz, 160 MHz, or 80+80 MHz. In this case, the PHY does not issue the PHY-CCA.indication(BUSY, {secondary80}) primitive or the PHY-CCA.indication(IDLE) primitive. The PHY issues the PHY-CCA.indication(BUSY, {secondary}) primitive if there are no conditions to issue the PHY-CCA.indication(BUSY, {secondary}) primitive, and in an idle operating channel width of 80MHz, 160MHz, or 80+80MHz, a 40MHz preamble or PPDU of -72dBm or higher is detected on the secondary 40MHz channel with a probability of 90% or higher within the aCCAMidTime period.The PHY issues the PHY-CCA.indication(BUSY, {secondary}) primitive if there are no conditions to issue the PHY-CCA.indication(BUSY, {secondary}) and PHY-CCA.indication(BUSY, {secondary}) primitives, and in an idle 80MHz, 160MHz, or 80+80MHz operating channel width, a 20MHz preamble or PPDU of -72dBm or higher is detected with a probability of 90% or higher within the aCCAMidTime period in any 20MHz subchannel of the secondary 40MHz channel. -72dBm may be a threshold for determining whether a channel is idle or busy.

[0150] The PHY issues the PHY-CCA.indication(BUSY, {secondary}) primitive if there are no conditions for issuing the PHY-CCA.indication(BUSY, {secondary}), PHY-CCA.indication(BUSY, {secondary40}) primitive, and if any signal greater than -56 dBm exists within the secondary80 MHz channel in an idle 160 MHz or 80+80 MHz operating channel width. The PHY issues the PHY-CCA.indication(BUSY, {secondary80}) primitive if there are no conditions for issuing the PHY-CCA.indication(BUSY, {primary}), PHY-CCA.indication(BUSY, {secondary40}), or PHY-CCA.Indication(BUSY, {secondary40}) primitive, and in an idle 160MHz or 80+80MHz operating channel width, an 80 MHz preamble or PPDU of -69 dBm or higher is detected in the secondary 80 MHz channel with a probability of 90% or higher within the aCCAMidTime period. The PHY issues the PHY-CCA.indication(BUSY, {secondary}) primitive if there are no conditions for issuing the PHY-CCA.indication(BUSY, {secondary}), PHY-CCA.indication(BUSY, {secondary40}) primitive, and if, in an idle operating channel width of 160MHz or 80+80MHz, a 40MHz preamble or PPDU of -72 dBm or higher is detected with a probability of 90% or more within the aCCAMidTime period in any 40MHz subchannel of the secondary 80MHz channel.The PHY issues the PHY-CCA.indication(BUSY, {secondary80}) primitive if there are no conditions for issuing the PHY-CCA.indication(BUSY, {primary}), PHY-CCA.indication(BUSY, {secondary40}), or PHY-CCA.Indication(BUSY, {secondary40}) primitive, and in an idle 160MHz or 80+80MHz operating channel width, a 20MHz preamble or PPDU is detected at -72dBm or higher with a probability of more than 90% within the aCCAMidTime period in any 20MHz subchannel of the secondary 80MHz channel. Here, -56dBm, -69dBm, and -72dBm may be thresholds for determining whether a channel is idle or busy.

[0151] The threshold may be compared with the signal level of the receiving antenna. In STA, the signal level compared with the threshold may be the signal level received by the antenna unit SU1. In AP, the signal level compared with the threshold may be the signal level received by the antenna unit AU1.

[0152] An STA with an operation channel width of W MHz may detect the start of a PPDU occupying at least the primary 20 MHz channel with a probability of a predetermined percentage or higher (e.g., 90% or higher) and if the power of the preamble or PPDU measured within the primary 20 MHz channel is above a predetermined value (e.g., -82 dBm or higher), it may issue a PHY-CCA.indication with the STATUS parameter set to BUSY within the aCCATime period. In other words, an STA may issue a PHY-CCA.indication(BUSY) primitive when it receives a preamble or PPDU exceeding -82 dBm on the primary 20 MHz channel. A receiver may issue a PHY-CCA.indication with the STATUS parameter set to BUSY for any signal exceeding a threshold (-62 dBm) that is a predetermined value (e.g., 20 dB) higher than the sensitivity of the minimum modulation and coding rate on the primary 20 MHz channel within the aCCATime period after the signal arrives at the receiver's antenna. If the operation channel width is 20 MHz or greater, the channel-list parameter may exist and be set to {primary}. While the threshold remains exceeded following the indication, the receiver will not issue a PHY-CCA.indication primitive with the STATUS parameter set to IDLE or a PHY-CCA.indication with the channel-list parameter modified.

[0153] If there are no conditions for issuing a PHY-CCA.indication primitive with the STATUS parameter set to BUSY, and any signal in the secondary 20 MHz channel exceeds a threshold of -62 dBm or more within aCCATime after reaching the receiver antenna in idle operating channel widths of 40 MHz, 80 MHz, 160 MHz, and 80+80 MHz, the PHY will issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}. If there are no conditions for issuing a PHY-CCA.indication primitive with the STATUS parameter set to BUSY, and a 20MHz preamble or PPDU of -72dBm or higher is detected with a probability of 90% or more within the aCCAMidTime period in the idle operating channel widths of 40MHz, 80MHz, 160MHz, and 80+80MHz, the PHY will issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}. As long as the threshold continues to be exceeded following the indication, the receiver will not issue a PHY-CCA.indication primitive with the STATUS parameter set to IDLE, or a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40} or {secondary 80}.

[0154] If there are no conditions for issuing a PHY-CCA.indication primitive with the STATUS parameter set to BUSY, and there is no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, then in idle operating channel widths of 80MHz, 160MHz, and 80+80MHz, if any signal in the secondary 40 MHz channel exceeds a threshold of -59dBm or more within aCCATime after reaching the receiver antenna, PHY will issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}. If there are no conditions for issuing a PHY-CCA.indication primitive with the STATUS parameter set to BUSY, and there is no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, then in idle operating channel widths of 80MHz, 160MHz, and 80+80MHz, if a 40MHz preamble or PPDU of -72dBm or higher is detected with a probability of 90% or more within the aCCAMidTime period, PHY will issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}.If there are no conditions for issuing a PHY-CCA.indication primitive with the STATUS parameter set to BUSY, and there is no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, then in idle operating channel widths of 80MHz, 160MHz, and 80+80MHz, if a 20MHz preamble or PPDU of -72dBm or higher is detected with a probability of 90% or more within the aCCAMidTime period in any 20MHz subchannel of the secondary 40MHz channel, PHY will issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}. As long as the threshold remains exceeded following the indication, the receiver will not issue a PHY-CCA.indication primitive with the STATUS parameter set to IDLE, or a PHY-CCA.indicationprimitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 80}.

[0155] If the conditions for issuing a PHY-CCA.indication primitive with the STATUS parameter set to BUSY are not met, and if there is no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, and no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}, and if there is any signal of -56dBm or greater in the secondary 80 MHz channel in an idle operating channel width of 160MHz or 80+80MHz, then the PHY will issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 80}. If the conditions for issuing a PHY-CCA.indication primitive with the STATUS parameter set to BUSY are not met, and if there is no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, and no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}, and if, in an idle operating channel width of 160MHz or 80+80MHz, an 80 MHz preamble or PPDU of -69 dBm or higher is detected in the secondary 80 MHz channel with a probability of 90% or higher within the aCCAMidTime period, the PHY will issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 80}.If the conditions for issuing a PHY-CCA.indication primitive with the STATUS parameter set to BUSY are not met, and if there is no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, and no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}, and if, in an idle operating channel width of 160MHz or 80+80MHz, a 40MHz preamble or PPDU of -72 dBm or higher is detected with a probability of 90% or more within the aCCAMidTime period in any 40MHz subchannel of the secondary 80MHz channel, then PHY will issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 80}.If the conditions for issuing a PHY-CCA.indication primitive with the STATUS parameter set to BUSY are not met, and if there is no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, and no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}, and if a 20MHz preamble or PPDU is detected at -72dBm or higher with a probability of more than 90% within the aCCAMidTime period in any 20MHz subchannel of the secondary 80MHz channel in an idle operating channel width of 160MHz or 80+80MHz, then the PHY will issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 80}.

[0156] An STA with an operation channel width of W MHz may detect the start of a PPDU occupying at least the primary 20 MHz channel with a probability of a predetermined percentage or higher (e.g., 90% or higher) and if the power of the preamble or PPDU measured within the primary 20 MHz channel is above a predetermined value (e.g., -82 dBm or higher), it may issue a PHY-CCA.indication with the STATUS parameter set to BUSY within the aCCATime period. In other words, an STA may issue a PHY-CCA.indication(BUSY) primitive when it receives a preamble or PPDU exceeding -82 dBm on the primary 20 MHz channel. If the operating channel width is greater than 20 MHz, the Channel-list parameter exists and may be set to {primary}. The receiver may issue a PHY-CCA.indication with the STATUS parameter set to BUSY for any signal exceeding the -62dBm threshold on the primary 20 MHz channel within a period of aCCATime after the signal arrives at the receiver's antenna.

[0157] An NPCA (Non-Primary Channel Access) primary channel may be defined. An NPCA primary channel may be a channel on which access is performed while the primary channel is busy. An NPCA primary channel may be a channel on which access is performed while the primary channel is busy due to OBSS traffic. An NPCA primary channel may be referred to by something other than NPCA primary channel. For example, an NPCA primary channel may be referred to as a Secondary primary channel, etc. Access may be a CCA. Access may be a backoff procedure. Access may be an EDCA. Access may be a carrier sense. Access may be a virtual carrier sense and a physical carrier sense. For example, "while the primary channel is busy" may be the period during which NAV is set (maintained) on the primary channel. For example, "while the primary channel is busy" may be the period during which no backoff procedure is performed on the primary channel. For example, "while the primary channel is busy" may be the period indicated by the received PPDU. "While the primary channel is busy" may be referred to as "when the primary channel is busy". "While the primary channel is busy" can be rephrased as "when the primary channel is busy." The NPCA primary channel may also be the NPCA primary 20MHz channel. The NPCA primary channel may also be referred to as the NPCA primary 20MHz channel. For example, the NPCA primary 20MHz channel may also be referred to as the 20MHz channel that includes the NPCA primary channel. The NPCA primary 20MHz channel may also be the NPCA primary channel.The NPCA primary 20MHz channel may also be referred to as the NPCA primary channel.

[0158] APs and / or STAs may perform NPCA (Non-Primary Channel Access). NPCA may be an operation to access other channels while the primary channel is busy due to OBSS traffic (i.e., occupied by OBSS traffic). In other words, it may be a mechanism for transferring operation from the primary channel to the NPCA primary channel. For example, OBSS traffic may be PPDUs received from OBSS. OBSS traffic may be inter-BSS PPDUs. OBSS traffic may be configured with NAV. OBSS traffic may be configured with basic NAV. OBSS traffic may be OBSS frame exchange. APs and / or STAs may perform backoff procedures on other channels while the primary channel is busy due to OBSS traffic. For example, a channel on which a backoff procedure is performed while the primary channel is busy due to OBSS traffic may be called an NPCA primary channel, a secondary primary channel, etc. The name of the channel on which a backoff procedure is performed while the primary channel is busy may be a name other than those mentioned above. In other words, the AP and / or STA may perform a backoff procedure on the NPCA primary channel when the primary channel becomes busy due to OBSS traffic. The AP and / or STA may perform a backoff procedure on the NPCA primary channel for the duration that NAV is configured on the primary channel by the OBSS PPDU. Once the backoff procedure on the NPCA primary channel is complete, the AP and / or STA may transmit on one or more channels that include the NPCA primary channel but do not include the primary channel.The AP and / or STA may switch to the primary channel before the NAV period ends. The AP may transmit information related to NPCA primary channel access in a frame. The STA may determine the action related to NPCA primary channel access based on the frame received from the AP.

[0159] In other words, the NPCA primary channel may be a channel for channel access while the primary channel is busy. The NPCA primary channel may be a channel for channel access while the NAV is set on the primary channel. The NPCA primary channel may be a channel for channel access while the basic NAV is set on the primary channel. The NPCA primary channel may be a channel for channel access while the primary channel is busy by the OBSS PPDU. The NPCA primary channel may be a channel for channel access while the NAV is set on the primary channel by the OBSS PPDU. While the NAV is set may be referred to as while the NAV is maintained. Channel access may be a backoff procedure. Channel access may be an EDCA. Channel access may be an EDCAF. Channel access may be a CCA.

[0160] An AP may send a frame containing an information element that includes information related to Non Primary Channel Access. An AP may send a frame containing an information element that includes information related to Non Primary Channel Access when performing Non Primary Channel Access. An AP may send a frame containing an information element that includes information related to Non Primary Channel Access to indicate to the STA in the BSS whether Non Primary Channel Access is enabled or disabled. If an AP does not perform Non Primary Channel Access in its BSS, it does not need to include an information element that includes information related to Non Primary Channel Access in the frame it sends. For example, an information element that includes information related to Non Primary Channel Access may be called an NPCA operation element. For example, an information element that includes information related to Non Primary Channel Access may be called a UHR operation element. An information element that includes information related to Non Primary Channel Access may be referred to in ways other than those mentioned above. An Element ID may be set for the NPCA operation element. An Element ID may be set for the UHR operation element. For example, an NPCA operation element may indicate information for Non Primary Channel Access. An NPCA operation element may consist of one or more fields. The NPCA operation element may include a field indicating the Element ID.The NPCA operation element may include a field indicating whether Non Primary Channel Access is enabled or disabled. The NPCA operation element may include a field indicating the location of the NPCA primary channel for Non Primary Channel Access. The NPCA operation element may include a field indicating the channel width for Non Primary Channel Access. Fields other than those mentioned above may be included in the NPCA operation element. For example, if an STA receives a frame containing an NPCA operation element from an AP, it may perform Non Primary Channel Access. If an STA receives a frame containing an NPCA operation element from an AP, it may perform Non Primary Channel Access using the information indicated in the fields of the NPCA operation element. If an STA receives a frame containing an NPCA operation element from an AP and it indicates that Non Primary Channel Access is enabled, it may perform Non Primary Channel Access. If an STA does not receive a frame containing an NPCA operation element from an AP, it will not perform Non Primary Channel Access. If an STA receives a frame containing an NPCA operation element from an AP and it indicates that Non Primary Channel Access is disabled, it will not perform Non Primary Channel Access. For example, the UHR operation element may display information for controlling the UHR STA. For example, the UHR operation element may display information for Non-Primary Channel Access. The UHR operation element may consist of one or more fields.A UHR operation element may include a field indicating the Element ID. A UHR operation element may include a field indicating whether information related to Non Primary Channel Access is included in the UHR operation element. A UHR operation element may include a field indicating whether Non Primary Channel Access is enabled or disabled. A UHR operation element may include a field indicating the location of the NPCA primary channel for Non Primary Channel Access. If a UHR operation element indicates that information related to Non Primary Channel Access is included in the UHR operation element, it may include a field indicating the location of the NPCA primary channel for Non Primary Channel Access. A UHR operation element may include a field indicating the channel width for Non Primary Channel Access. If a UHR operation element indicates that information related to Non Primary Channel Access is included in the UHR operation element, it may include a field indicating the channel width for Non Primary Channel Access. Fields other than those mentioned above may be included in the UHR operation element. A field indicating the center frequency of the channel width for Non Primary Channel Access may be included. For example, if an STA receives a frame containing a UHR operation element from an AP, it may perform Non Primary Channel Access.If the STA receives a frame from the AP containing a UHR operation element, it may perform Non Primary Channel Access using the information indicated in the fields of the UHR operation element. If the STA receives a frame from the AP containing a UHR operation element and the UHR operation element indicates that Non Primary Channel Access is enabled, it may perform Non Primary Channel Access. If the STA does not receive a frame from the AP containing a UHR operation element, it will not perform Non Primary Channel Access. If the STA receives a frame from the AP containing a UHR operation element and it indicates that Non Primary Channel Access is disabled, it will not perform Non Primary Channel Access. If the received UHR operation element indicates that the UHR operation element contains information related to Non Primary Channel Access, the STA may perform Non Primary Channel Access. If the received UHR operation element indicates that the UHR operation element does not contain information related to Non Primary Channel Access, the STA will not perform Non Primary Channel Access.

[0161] The channel width for Non-Primary Channel Access may be the bandwidth of a channel that includes the NPCA primary channel but does not include the primary channel. The channel width for Non-Primary Channel Access may also be referred to as the NPCA channel width. The channel width for Non-Primary Channel Access of an AP may also be referred to as the NPCA BSS operating channel width. The channel width for Non-Primary Channel Access of an AP may also be referred to as the NPCA BSS bandwidth. The NPCA operating channel may be the channel on which the STA and / or AP transmit and / or receive, including the NPCA primary channel but not the primary channel. The STA may notify the AP of the capability of the NPCA operating channel widths it supports.

[0162] For example, the PHY of STA and / or AP may perform NPCA if the PHY-CONFIG_VECOTR parameter included in the PHY-CONFIG.request primitive indicated by MAC contains information about the NPCA_flag. For example, the PHY of STA and / or AP may perform NPCA if the PHY-CONFIG_VECOTR parameter included in the PHY-CONFIG.request primitive indicated by MAC contains the NPCA_flag. For example, the PHY of STA and / or AP may perform NPCA if the PHY-CONFIG_VECOTR parameter included in the PHY-CONFIG.request primitive indicated by MAC indicates that NPCA should be performed. The PHY-CONFIG_VECOTR parameter included in the PHY-CONFIG.request primitive may contain information about the NPCA primary channel. The PHY-CONFIG_VECOTR parameter included in the PHY-CONFIG.request primitive may contain information about the primary channel.

[0163] Information related to Non Primary Channel Access may include information indicating the location of at least the NPCA primary channel. Information related to Non Primary Channel Access may also include information indicating the location of the NPCA primary channel and / or the NPCA secondary 20MHz channel and / or the NPCA secondary 40MHz channel and / or the NPCA secondary 80MHz channel. An AP may transmit a frame containing information related to Non Primary Channel Access if the operating channel width includes at least the NPCA primary channel. An STA may determine that at least the NPCA primary channel exists in the operating channel width if the frame received from the AP contains information related to Non Primary Channel Access. In other words, if the frame received from the AP contains information related to Non Primary Channel Access, the STA may perform Non Primary Channel Access. If the frame received from the AP does not contain information related to Non Primary Channel Access, the STA may determine that the NPCA primary channel does not exist in the operating channel width. In other words, if the frame received from the AP does not contain information related to Non Primary Channel Access, the STA may decide not to perform Non Primary Channel Access.

[0164] If the primary channel is idle, the STA or AP may transmit on one or more channels including the primary channel. If the primary channel is busy, the STA or AP may perform sensing on the NPCA primary channel, and if the NPCA primary channel is idle, it may transmit on one or more channels including the NPCA primary channel but not the primary channel. If the primary channel is busy due to OBSS traffic, the STA or AP may perform sensing on the NPCA primary channel, and if the NPCA primary channel is idle, it may transmit on one or more channels including the NPCA primary channel but not the primary channel. For example, OBSS traffic may be OBSS PPDU. The STA or AP may transmit on one or more channels including the NPCA primary channel but not the primary channel. Note that "may transmit" can also be expressed as "have the right to transmit". The STA or AP may receive on one or more channels including the primary channel. The STA or AP may receive on one or more channels that do not include the primary channel but include at least the NPCA primary channel.

[0165] An STA or AP may transmit using multiple channels in NPCA. When an STA or AP transmits using multiple channels in NPCA, it may perform a backoff procedure on the NPCA primary channel, perform sensing for a predetermined period on the NPCA secondary channel immediately before transmission, and then transmit. The NPCA secondary channel may be a channel other than the NPCA primary channel used for transmitting using multiple channels in NPCA. NPCA secondary channels may be defined as an NPCA secondary 20MHz channel, an NPCA secondary 40MHz channel, and an NPCA secondary 80MHz channel. The NPCA secondary 20MHz channel may be a 20MHz channel related to the NPCA primary channel. For example, when an STA or AP transmits with a bandwidth of 40MHz in NPCA, it may transmit using the NPCA primary channel and the NPCA secondary 20MHz channel. The NPCA secondary 40MHz channel may be a 40MHz channel related to the NPCA primary channel. For example, if an STA or AP transmits with an 80MHz bandwidth in NPCA, it may use the NPCA primary channel, the NPCA secondary 20MHz channel, and the NPCA secondary 40MHz channel for transmission. The NPCA secondary 40MHz channel may consist of two 20MHz channels. The NPCA secondary 80MHz channel may be an 80MHz channel associated with the NPCA primary channel.For example, when an STA or AP transmits with a bandwidth of 160 MHz in NPCA, it may transmit using the NPCA primary channel, NPCA secondary 20 MHz channel, NPCA secondary 40 MHz channel, and NPCA secondary 80 MHz channel. The NPCA secondary 80 MHz channel may consist of four 20 MHz channels. The NPCA secondary channel may be referred to in ways other than NPCA secondary channel. For example, the NPCA secondary channel may be referred to as a secondary secondary channel. The NPCA secondary 20 MHz channel may be referred to in ways other than NPCA secondary 20 MHz channel. For example, the NPCA secondary 20 MHz channel may be referred to as a secondary secondary 20 MHz channel. The NPCA secondary 40 MHz channel may be referred to in ways other than NPCA secondary 40 MHz channel. For example, the NPCA secondary 40 MHz channel may be referred to as a secondary secondary 40 MHz channel. The NPCA secondary 80 MHz channel may be referred to in ways other than NPCA secondary 80 MHz channel. For example, an NPCA secondary 80MHz channel may also be referred to as a secondary secondary 80MHz channel. In NPCA, channel access may also be performed on the NPCA primary channel.

[0166] STA and / or AP may transmit using one or more channels that include the NPCA primary channel but do not include the primary channel. STA and / or AP may receive PPDU transmitted on one or more channels that include the NPCA primary channel but do not include the primary channel. A channel used for transmission on a 40MHz channel that includes the NPCA primary channel but does not include the primary channel may be referred to as the NPCA primary 40MHz channel. It may be referred to in ways other than NPCA primary 40MHz channel. For example, NPCA primary 40MHz channel may be referred to as 40MHz channel including the NPCA primary channel. A channel used for transmission on an 80MHz channel that includes the NPCA primary channel but does not include the primary channel may be referred to as the NPCA primary 80MHz channel. It may be referred to in ways other than NPCA primary 80MHz channel. For example, NPCA primary 80MHz channel may be referred to as 80MHz channel including the NPCA primary channel. NPCA primary 40MHz channel may consist of an NPCA primary channel and an NPCA secondary 20MHz channel. The NPCA primary 80MHz channel may consist of the NPCA primary channel, the NPCA secondary 20MHz channel, and the NPCA primary 40MHz channel. The NPCA primary 80MHz channel may also consist of the NPCA primary 40MHz channel and the NPCA secondary 40MHz channel.The NPCA primary channel is the channel on which carrier sensing is performed when the primary channel is busy, and may be a channel of a different frequency than the primary channel. The NPCA primary channel may be a 20MHz channel used to transmit PPDUs with a 20MHz bandwidth when the primary channel is busy. The NPCA primary 40MHz channel may be a 40MHz channel used to transmit PPDUs with a 40MHz bandwidth that include the NPCA primary channel but do not include the primary channel when the primary channel is busy. The NPCA primary 80MHz channel may be an 80MHz channel used to transmit PPDUs with an 80MHz bandwidth that include the NPCA primary channel but do not include the primary channel when the primary channel is busy. There may be PPDUs transmitted using one or more channels, including the primary channel. There may be frames transmitted using one or more channels, including the primary channel. There may be PPDUs transmitted using one or more channels, including the NPCA primary channel but not including the primary channel. There may be frames transmitted using one or more channels, including the NPCA primary channel but not including the primary channel. In other words, there may be PPDUs or frames that are transmitted or received only when NPCA is being performed. There may be PPDUs or frames that are transmitted or received only when NPCA is not being performed. There may be PPDUs or frames that are transmitted or received both when NPCA is being performed and when NPCA is not being performed. For example, a given frame or PPDU may not be transmitted when NPCA is being performed. A given frame or PPDU may be transmitted when NPCA is not being performed.A given frame or PPDU may be transmitted both when NPCA is being performed and when NPCA is not being performed. There may be frames or PPDUs that are transmitted only on the Operating channel. There may be frames or PPDUs that are transmitted only on the NCPA Operating channel. There may be frames or PPDUs that are transmitted on both the Operating channel and the NCPA Operating channel. For example, a Beacon may be transmitted on the Operating channel. For example, a Beacon may not be transmitted on the NPCA Operating channel. The NPCA operating channel may be a channel within the operating channel.

[0167] The NPCA operating channel may be the channel on which the STA and / or AP transmit and / or receive and / or carrier sense in the NPCA. The NPCA operating channel bandwidth may be the bandwidth of the channel on which the STA and / or AP transmit and / or receive and / or carrier sense in the NPCA. For example, in Figure 13, the NPCA operating channels may be 1305, 1306, 1307, and 1308. In Figure 13, the NPCA operating channel bandwidth may be 80 MHz. The NPCA primary channel may be a channel within the NPCA operating channel. The NPCA primary channel is a channel within the NPCA operating channel and may be a different channel from the primary channel. The NPCA primary 40 MHz channel is a channel within the NPCA operating channel and may be a 40 MHz channel that includes the NPCA primary channel but does not include the primary channel. For example, in Figure 13, the NPCA primary 40 MHz channel may be composed of 1305 and 1306. The NPCA primary 80MHz channel is a channel within the NPCA operating channel and may be a 40MHz channel that includes the NPCA primary channel but does not include the primary channel. The NPCA operating channel width may have a smaller bandwidth than the operating channel width.

[0168] Figure 13 shows an example of a backoff procedure on the NPCA primary channel according to one aspect of this embodiment. 1301, 1302, 1303, 1304, 1305, 1306, 1307, and 1308 may each be 20 MHz channels. Figure 13 may also be a diagram of an STA or AP operating with a 160 MHz channel width. 1301 may be the primary channel. 1306 may be the NPCA primary channel. 1309 may be a frame transmitted by another STA or AP received by the STA or AP. 1309 may be a frame transmitted by an STA or AP belonging to the OBSS received by the STA or AP. For example, 1309 may be an RTS frame. 1309 may be a CTS frame. 1309 may be a Data frame. 1309 may be a PPDU. 1309 may be a PPDU received from an STA or AP belonging to the OBSS. 1310 may be while the primary channel is busy. 1310 may be the period during which the NAV is set (maintained). 1311 may be carrier sense (backoff counter, contention window, DCF, EDCA). 1312 may be the transmission of a PPDU. For example, when an STA or AP receives 1309 on 1301, it may set 1310 on 1301 for the period indicated in the Duration field of 1309. Once 1310 is set on 1301, the STA may move to 1306, that is, it may switch from the primary channel to the NPCA primary channel. Once the STA moves to 1306, it may start 1311 on 1306. The STA may perform 1312 when 1311 is complete. Here, for example, if the STA performs the operation in Figure 13, the STA is 204 in Figure 2, and 1309 may be the frame transmitted by 207 in Figure 2. Figure 13 may be a diagram of an AP operating at 160MHz. For example, if the AP performs the operation shown in Figure 13, the AP performs the operation of 202 in Figure 2, and 1309 may be a frame transmitted by 207.1312 may be transmitted using multiple channels. For example, 1312 may be a transmission with a channel width of 80 MHz transmitted using 1308, 1307, 1306, and 1305. Here, 1308, 1307, and 1305 may each be NPCA secondary channels. The 80 MHz transmission may also be a transmission using the NPCA primary channel of 1306, the NPCA secondary 20 MHz channel of 1305, and the NPCA secondary 40 MHz channel composed of 1307 and 1308. In other words, when a backoff procedure is performed at 1301, 1305, 1306, 1307, and 1308 may be channels that constitute a secondary 80 MHz channel. In Non Primary Channel Access, when a backoff procedure is performed at 1306, 1305 may be an NPCA secondary 20 MHz channel, and 1307 and 1308 may be channels that constitute an NPCA secondary 40 MHz channel. The AP may determine that 1305 within the operating channel width is the NPCA secondary 20MHz channel, 1305 is the NPCA primary channel, and 1307 and 1308 are channels that constitute the NPCA secondary 40MHz channel, and notify the STA of this in a frame. The AP may also notify the STA of 80MHz as the NPCA operating channel width. The AP may also notify the STA of 80MHz, composed of 1305, 1306, 1307, and 1308, as the NPCA operating channel width. The AP may notify the STA of the location of the NPCA primary channel (1305). The AP may also notify the STA of the center frequency of the NPCA operating channel.The STA may determine from the frame received from the AP that channel 1305 in the Operating channel width is the NPCA secondary 20MHz channel, channel 1305 is the NPCA primary channel, and channels 1307 and 1308 constitute the NPCA secondary 40MHz channel.

[0169] STA may generate a PHY-CCA.indication primitive in the physical layer processing unit SU3. STA may present the PHY-CCA.indication primitive generated in the physical layer processing unit SU3 to the MAC layer processing unit SU4. AP may generate a PHY-CCA.indication primitive in the physical layer processing unit AU3. AP may present the PHY-CCA.indication primitive generated in the physical layer processing unit AU3 to the MAC layer processing unit AU4. The PHY-CCA.indication primitive may include a channel-list parameter. The channel-list parameter may include one entry. One entry may be one of a set of entries. A set of entries may be defined. A set of entries may be called channel-list parameter entries. For example, channel-list parameter entries may include an entry indicating that the NPCA primary channel is busy. In other words, the PHY-CCA.indication primitive includes a channel-list parameter, the channel-list parameter includes one entry, the one entry is one of a set of entries, the set of entries includes at least a first entry, and the first entry may indicate that the NPCA primary channel is busy.

[0170] For example, the set of entries may include NPCA primary and / or NPCA secondary and / or NPCA secondary 20 and / or NPCA secondary 40 and / or NPCA secondary 80. That is, channel-list parameter entries may be defined that include NPCA primary and / or NPCA secondary and / or NPCA secondary 20 and / or NPCA secondary 40 and / or NPCA secondary 80. NPCA primary may be the value of an entry. NPCA primary may be an entry indicating the channel state of the NPCA primary channel. NPCA primary may be an entry indicating that the NPCA primary channel is busy. NPCA primary may further indicate that the primary channel is busy. NPCA secondary may be the value of an entry. NPCA secondary may be an entry indicating the channel state of the NPCA secondary channel. NPCA secondary may be an entry indicating that the NPCA secondary channel is busy. NPCA secondary may further indicate that the primary channel is busy. NPCA secondary may indicate that the NPCA primary channel is idle. secondary20 may be the value of entry. NPCA secondary20 may be an entry indicating the channel state of the NPCA secondary 20MHz channel. NPCA secondary20 may be an entry indicating that the NPCA secondary 20MHz channel is busy. NPCA secondary20 may also indicate that the primary channel is busy.NPCA secondary20 may indicate that the NPCA primary channel is idle. secondary40 may be an entry value. NPCA secondary40 may be an entry indicating the channel state of the NPCA secondary 40MHz channel. NPCA secondary40 may be an entry indicating that the NPCA secondary 40MHz channel is busy. NPCA secondary40 may further indicate that the primary channel is busy. NPCA secondary40 may indicate that both the NPCA primary channel and the NPCA secondary 20MHz channel are idle. secondary80 may be an entry value. NPCA secondary80 may be an entry indicating the channel state of the NPCA secondary 80MHz channel. NPCA secondary80 may be an entry indicating that the NPCA secondary 80MHz channel is busy. NPCA secondary80 may further indicate that the primary channel is busy. NPCA secondary80 may indicate that the NPCA primary channel, NPCA secondary 20MHz channel, and NPCA secondary 40MHz channel are idle. For example, the set of entries may include primary, secondary, secondary40, secondary80, primary1, primary2, secondary2, secondary4, secondary8, and / or NPCA primary and / or NPCA secondary and / or NPCA secondary 20 and / or NPCA secondary40 and / or NPCA secondary80.In other words, channel-list parameter entries may be defined that include primary, secondary, secondary40, secondary80, primary1, primary2, secondary2, secondary4, secondary8, and / or NPCA primary and / or NPCA secondary and / or NPCA secondary 20 and / or NPCA secondary40 and / or NPCA secondary80. The value of an entry, NPCA primary, may be called secondary primary. The value of an entry, NPCA primary, may be called anchor primary. The value of an entry, NPCA primary, may be referred to in ways other than those mentioned above. The value of an entry, NPCA secondary, may be called secondary secondary. The value of an entry, NPCA secondary, may be called anchor secondary. The value of an entry, NPCA secondary, may be referred to in ways other than those mentioned above. The value of an entry, NPCA secondary20, may be called secondary secondary20. The value of an entry, NPCA secondary20, may be called anchor secondary20. The value of an entry, NPCA secondary20, may be referred to in ways other than those mentioned above. The entry value NPCA secondary40 may also be called secondary secondary40. The entry value NPCA secondary40 may also be called anchor secondary40. The entry value NPCA secondary40 may be referred to in ways other than those mentioned above. The entry value NPCA secondary80 may also be called secondary secondary80. The entry value NPCA secondary80 may also be called anchor secondary80.The entry value, NPCA secondary80, may be referred to in ways other than those mentioned above.

[0171] The STA or AP may issue a PHY-CCA.indication primitive associated with the NPCA primary channel. The PHY (Physical Layer) may issue a PHY-CCA.indication primitive associated with the NPCA primary channel to indicate to the MAC that the NPCA primary channel is idle or busy. {NPCA primary} may be the channel-list parameter for the NPCA primary channel. For example, if the NPCA primary channel is idle, the physical layer of the STA or AP may issue a PHY-CCA.indication primitive indicating that STATUS is IDLE and the channel-list parameter is {NPCA primary}. That is, the PHY-CCA.indication(IDLE, {NPCAprimary}) primitive may be issued. For example, if the NPCA primary channel is busy, the physical layer of the STA or AP may issue a PHY-CCA.indication primitive indicating that STATUS is BUSY and the channel-list parameter is {NPCA primary}. That is, the PHY-CCA.indication(BUSY, {NPCA primary}) primitive may be issued. The PHY-CCA.indication primitive associated with the NPCA primary channel may only be issued when NPCA is performed. The MAC layer that receives a PHY-CCA.indication primitive with STATUS IDLE and channel-list parameter {NPCA primary} may determine that the NPCA primary channel is idle.A MAC layer that receives a PHY-CCA.indication primitive with STATUS IDLE and channel-list parameter {NPCA primary} may determine that the NPCA primary channel is idle and the primary channel is busy. A MAC layer that receives a PHY-CCA.indication primitive with STATUS BUSY and channel-list parameter {NPCA primary} may determine that the NPCA primary channel is busy. A MAC layer that receives a PHY-CCA.indication primitive with STATUS BUSY and channel-list parameter {NPCA primary} may determine that both the NPCA primary channel and the primary channel are busy. The channel-list parameter {NPCA primary} may also be called {secondary primary}. A MAC layer may determine that the NPCA primary channel is busy if the channel-list parameter is set to NPCA primary. A MAC layer may determine that both the NPCA primary channel and the primary channel are busy if the channel-list parameter is set to NPCA primary.

[0172] The STA or AP may issue a PHY-CCA.indication primitive associated with an NPCA secondary channel. The PHY-CCA.indication primitive associated with an NPCA secondary channel may be issued to indicate to the MAC (Physical Layer) that the NPCA secondary channel is idle or busy. {NPCA secondary} may be a channel-list parameter for the NPCA secondary channel. For example, if the NPCA secondary channel is idle, the physical layer of the STA or AP may issue a PHY-CCA.indication primitive indicating STATUS is IDLE and the channel-list parameter is {NPCA secondary}. That is, the PHY-CCA.indication(IDLE, {NPCA secondary}) primitive may be issued. For example, if the NPCA secondary channel is busy, the physical layer of the STA or AP may issue a PHY-CCA.indication primitive indicating STATUS is BUSY and the channel-list parameter is {NPCA secondary}. That is, the PHY-CCA.indication(BUSY, {NPCA secondary}) primitive may be issued. The PHY-CCA.indication primitive associated with the NPCA secondary channel may be issued when NPCA is performed. The PHY-CCA.indication primitive associated with the NPCA secondary channel may be issued when the NPCA primary channel is idle. The PHY-CCA.indication primitive associated with the NPCA secondary channel may be issued when the NPCA primary channel is not busy.A MAC layer that receives a PHY-CCA.indication primitive with STATUS = IDLE and channel-list parameter = {NPCA secondary} may determine that the NPCA secondary channel is idle. A MAC layer that receives a PHY-CCA.indication primitive with STATUS = IDLE and channel-list parameter = {NPCA secondary} may determine that both the NPCA primary channel and NPCA secondary channel are idle. A MAC layer that receives a PHY-CCA.indication primitive with STATUS = IDLE and channel-list parameter = {NPCA secondary} may determine that both the NPCA primary channel and NPCA secondary channel are idle and the primary channel is busy. A MAC layer that receives a PHY-CCA.indication primitive with STATUS = BUSY and channel-list parameter = {NPCA secondary} may determine that the NPCA secondary channel is busy. A MAC layer that receives a PHY-CCA.indication primitive with STATUS BUSY and channel-list parameter {NPCA secondary} may determine that the NPCA primary channel is idle and the NPCA secondary channel is busy.The MAC layer may determine that the NPCA secondary channel is busy if the channel-list parameter is set to NPCA secondary. The MAC layer may also determine that both the NPCA secondary channel and the primary channel are busy if the channel-list parameter is set to NPCA secondary. For example, the channel-list parameter {NPCA secondary} may be called {secondary secondary}. The channel-list parameter {NPCA secondary} may be referred to in ways other than those mentioned above.

[0173] A table may be defined to define the meaning of the channel-list parameter entries in PHY-CCA.indication. For example, the meaning of Channel-list parameter entry{NPCA primary} may indicate that STA is busy on the NPCA primary channel. For example, the meaning of Channel-list parameter entry{NPCA secondary} may indicate that STA is busy on the NPCA secondary channel. For example, the meaning of channel-list parameter entry{NPCA secondary} may indicate that STA is busy on both the NPCA secondary channel and the primary channel. For example, the meaning of channel-list parameter entry{NPCA secondary20} may indicate that STA is busy on the NPCA secondary 20MHz channel. For example, the meaning of channel-list parameter entry{NPCA secondary20} may indicate that STA is busy on both the NPCA secondary 20MHz channel and the primary channel. For example, the meaning of channel-list parameter entry{NPCA secondary40} may indicate that STA is busy on the NPCA secondary 40MHz channel. For example, the meaning of the channel-list parameter entry{NPCA secondary40} may indicate that STA is busy with the NPCA secondary 40MHz channel and the primary channel. For example, the meaning of the channel-list parameter entry{NPCA secondary80} may indicate that STA is busy with the NPCA secondary 80MHz channel.For example, the meaning of the channel-list parameter entry{NPCA secondary80} may indicate that STA is busy with the NPCA secondary 80MHz channel and the primary channel.

[0174] The STA may issue (generate) a PHY-RXSTART.indication primitive. The AP may issue (generate) a PHY-RXSTART.indication primitive. The PHY-RXSTART.indication primitive may indicate to the local MAC entity that the PHY (Physical Layer) has received a valid start of a PPDU containing a valid PHY header. The PHY-RXSTART.indication primitive may not be generated until the PHY determines the PPDU format (e.g., a VHT PPDU beginning with an HT PHY header).

[0175] STA may generate PHY-RXSTART.indication primitive in the physical layer processing unit SU3. STA may also show the PHY-RXSTART.indication primitive generated in the physical layer processing unit SU3 to the MAC layer processing unit SU4. AP may generate PHY-RXSTART.indication primitive in the physical layer processing unit AU3. AP may also show the PHY-RXSTART.indication primitive generated in the physical layer processing unit AU3 to the MAC layer processing unit AU4.

[0176] The PHY-RXSTART.indication primitive may provide an RXVECTOR. The RXVECTOR may represent a list of parameters that the PHY provides to the local MAC entity upon receiving a valid PHY header. The RXVECTOR may include at least the DATARATE parameter and / or the LENGTH parameter.

[0177] The PHY may provide an interface to the MAC. The MAC may provide an interface to the PHY. This interface may include a TXVECTOR and an RXVECTOR. The MAC may use the TXVECTOR to supply transmission parameters for each PPDU to the PHY. The PHY may use the RXVECTOR to notify the MAC of the parameters of the received PPDU. The TXVECTOR may include one or more parameters.

[0178] The syntax of "a frame, MPDU, or A-MPDU is transmitted with a certain TXVECTOR parameter, or received with a certain RXVECTOR parameter" may be understood to refer to the TXVECTOR parameter or RXVECTOR parameter corresponding to the PSDU containing the frame, MPDU, or A-MPDU, respectively. The syntax of "a PPDU is transmitted with a certain TXVECTOR parameter, or received with a certain RXVECTOR parameter" may be understood to refer to the TXVECTOR or RXVECTOR parameter corresponding to the PSDU contained within the PPDU, respectively.

[0179] The TXVECTOR and / or RXVECTOR of the HT PHY may include additional parameters related to the operating mode of the HT PHY. In certain operating modes, the DATARATE parameter may be replaced by MCS, CH_BANDWIDTH, or GI_TYPE values. Additional parameters related to the operating mode of the HT PHY may include FORMAT parameter, NON_HT_MODULATION parameter, L_LENGTH parameter, L_DATARATE parameter, LSIGVALID parameter, RSSI parameter, MSC parameter, CH_BANDWIDTH parameter, LENGTH parameter, GI_TYPE parameter, SNR parameter, etc.

[0180] The TXVECTOR and / or RXVECTOR of the VHT PHY may include additional parameters related to the operating mode of the VHT PHY. In certain operating modes, the DATARATE parameter may be replaced by MCS, CH_BANDWIDTH, NUM_STS, STBC, and GI_TYPE values. Additional parameters related to the operating mode of the VHT PHY may include FORMAT parameter, NON_HT_MODULATION parameter, DELTA_SNR parameter, SNR parameter, STBC parameter, GI_TYPE parameter, RSSI parameter, MSC parameter, CH_BANDWIDTH parameter, GI_TYPE parameter, NUM_STS parameter, etc.

[0181] The TXVECTOR and / or RXVECTOR of the HE PHY may include additional parameters related to the HE PHY's operating mode. In certain operating modes, the DATARATE parameter may be replaced by MCS, CH_BANDWIDTH, RU_ALLOCATION, NUM_STS, STBC, GI_TYPE, and DCM values. Additional parameters related to the HE PHY's operating mode may include FORMAT parameter, SNR parameter, CQI parameter, STBC parameter, GI_TYPE parameter, RSSI parameter, RSSI_LEGACY parameter, MSC parameter, DCM parameter, CH_BANDWIDTH parameter, TXOP_DURATION parameter, SPATIAL_REUSE parameter, RU_ALLOCATION parameter, etc.

[0182] The FORMAT parameter may be a parameter (value) that determines the format of the PPDU. The NON_HT_MODULATION parameter may be a parameter (value) that determines the Enumerated type. The NON_HT_MODULATION parameter may be a parameter (value) that indicates the estimated format type of the received non-HT PPDU. The L_LENGTH parameter may be a parameter (value) that indicates the length of the PSDU. The L_DATARATE parameter may be a parameter (value) that indicates the rate used to transmit the PDSU. The LSIGVALID parameter may be a parameter (value) that indicates true if L-SIG Parity is enabled, and false if L-SIG Parity is not enabled. The RSSI parameter may be a parameter (value) that indicates the PHY measurement of power observed at the antenna connector that received the current PPDU. The MCS parameter may be a parameter (value) that selects the modulation scheme and coding rate used for packet transmission. The CH_BANDWIDTH parameter may indicate the channel width through which the packet was transmitted. The LENGTH parameter may be a parameter (value) that indicates the length of the HT PSDU. The GI_TYPE parameter may be a parameter (value) indicating whether to use a short guard interval for packet transmission. The SNR parameter may be a measure of the received SNR per chain. The SNR parameter may be a measure of the received SNR per stream. The STBC parameter may be a parameter (value) indicating the difference between the number of space-time streams and the number of spatial streams. The DELTA_SNR parameter may be a parameter (value) containing an array of delta SNR values ​​based on channels measured with the training symbols of the received VHT NDP. The NUM_STS parameter may be a parameter (value) indicating the number of space-time streams.The SNR parameter may be a parameter (value) containing an array of received SNR measurements for each spatial stream. The STBC parameter may be a parameter (value) indicating whether STBC is being used. The CH_BANDWIDTH parameter may be a parameter (value) indicating the channel width of the PPDU. The DCM parameter may be a parameter (value) indicating whether DCM is being used for the Date field. The TXOP_DURATION parameter may be a parameter (value) indicating the TXOP duration. The SPATIAL_REUSE parameter may be a parameter (value) indicating the spatial reuse parameter value. The RU_ALLOCATION parameter may be a parameter (value) indicating the RU (Resource Unit) allocated within the bandwidth.

[0183] The TXVECTOR and / or RXVECTOR of the UHR PHY may include additional parameters related to the operating mode of the UHR PHY. For example, additional parameters related to the operating mode of the UHR PHY may include FORMAT parameters.

[0184] The PHY-RXSTART.indication primitive may be generated by the local PHY entity to the MAC sublayer when the PHY successfully validates the PHY header at the start of a new PPDU. After generating the PHY-RXSTART.indication primitive, the PHY may maintain a physical medium busy status for the duration required for the PHY to forward frames of the indicated length at the indicated data rate. The physical medium busy status may also be maintained if the PHY generates a PHY-RXEND.indication(CarrierLost) primitive or a PHY-RXEND.indication(FormatViolation) primitive before the end of the period. When the MAC entity receives the PHY-RXSTART.indication primitive, the MAC may prepare a new receive flow.

[0185] PHY-RXEND.indication may be a primitive that the PHY uses to indicate to the local MAC entity that the currently received PPDU has completed. The PHY-RXEND.indication primitive may include an RXERROR parameter. The RXERROR parameter may convey one or more values ​​indicating NoError or an error state. The RXERROR parameter may indicate NoError, FormatViolation, CarrierLost, UnsupportedRate, or Filtered. NoError may be used to indicate that no errors occurred during the PHY's receiving process. FormatViolation may be used to indicate that the format of the received PPDU was incorrect. CarrierLost may be used to indicate that the carrier was lost during the reception of the received PSDU and the PSDU cannot be processed any further. UnsupportedRate may be used to indicate that an unsupported data rate was detected during the reception of the received PPDU. Filtered may be used to indicate that the PPDU was filtered during the reception of the PPDU due to conditions set in PHYCONFIG_VECTOR.

[0186] An STA or AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the primary channel. The STA's PHY or the AP's PHY may issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the primary channel. An STA or AP does not have to issue a PHY-RXSTART.indication primitive for PPDUs that do not overlap with the primary channel. An STA's PHY or the AP's PHY does not have to issue a PHY-RXSTART.indication primitive for PPDUs that do not overlap with the primary channel. A PPDU that overlaps with the primary channel may be a PPDU that includes at least the primary channel. A PPDU that overlaps with the primary channel may be a PPDU that is transmitted using at least the primary channel. A PPDU that overlaps with the primary channel may be a PPDU whose transmission frequency overlaps with the primary channel frequency.

[0187] In Figure 12, for example, STA or AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with 1201. For example, STA or AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU transmitted using 1201. For example, STA or AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU transmitted using both 1201 and 1202. For example, STA or AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU transmitted using both 1201, 1202, 1203, and 1204. In other words, STA or AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU transmitted using 1201. For example, STA or AP does not need to issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with 1201. For example, an STA or AP does not need to issue a PHY-RXSTART.indication primitive when it receives a PPDU transmitted using only 1202. For example, an STA or AP does not need to issue a PHY-RXSTART.indication primitive when it receives a PPDU transmitted using both 1203 and 1204. In other words, an STA or AP does not need to issue a PHY-RXSTART.indication primitive when it receives a PPDU transmitted without using 1201.

[0188] Unless the AP's PHY receives a TB PPDU requested by the AP, the PHY does not need to issue a PHY-RXSTART.indication primitive for PPDUs that do not overlap with the primary channel. For TB PPDUs requested by the AP, the PHY may issue a PHY-RXSTART.indication primitive for PPDUs received on the primary channel, or on the secondary 20MHz channel, secondary 40MHz channel, or secondary 80MHz channel.

[0189] An AP may request one or more STAs to send a Trigger Based (TB) PPDU. An AP may request one or more STAs to send a TB PPDU using a Trigger frame. A Trigger frame may be used to request one or more TB PPDU transmissions and to allocate resources for one or more TB PPDU transmissions. When an STA receives a Trigger frame from an AP, it may send a TB PPDU based on the information contained in the received Trigger frame. A Trigger frame may be used by an AP to enable Multi-User (UL MU) transmission. A Trigger frame may be used for OFDMA transmission. A TB PPDU may be a PPDU. A TB PPDU may be referred to as a PPDU.

[0190] In Figure 12, for example, AP does not need to issue a PHY-RXSTART.indication primitive for PPDUs that do not overlap with 1201 unless it receives a TB PPDU that AP requested. For example, AP may issue a PHY-RXSTART.indication primitive for PPDUs that do not overlap with 1201 after receiving a TB PPDU that AP requested. For example, AP may assign TB PPDU 1202 to STA, and when AP receives a PPDU from STA using 1202, it may issue a PHY-RXSTART.indication primitive. For example, AP may assign TB PPDUs 1203 and 1204 to STA, and when AP receives PPDUs from STA using 1203 and 1204, it may issue a PHY-RXSTART.indication primitive. For example, AP may assign TB PPDUs to 1205, 1206, 1207, and 1208 to STA, and when AP receives PPDUs from STA using 1205, 1206, 1207, and 1208, it may issue a PHY-RXSTART.indication primitive. The PPDUs sent by STA may also be TB PPDUs.

[0191] Unless the AP's PHY receives a requested TB PPDU from the AP, the PHY does not need to issue PHY-RXEARLYSIG.indication primitive and PHY-RXSTART.indication primitive for PPDUs that do not overlap with the primary channel. The PHY may issue both PHY-RXEARLYSIG.indication primitive and PHY-RXSTART.indication primitive for a requested TB PPDU from the AP. PHY-RXEARLYSIG.indication primitive may be a primitive that is advertised from the PHY to the MAC. PHY-RXEARLYSIG.indication primitive may be issued after PHY-CCA.indication primitive. PHY-RXEARLYSIG.indication primitive may be issued before PHY-RXSTART.indication. For example, PHY-RXEARLYSIG.indication primitive may be issued after L-SIG decoding (reception). For example, the PHY-RXEARLYSIG.indication primitive may be issued after decoding (receiving) the L-SIG and / or RL-SIG. For example, the PHY-RXEARLYSIG.indication primitive may be issued before decoding (receiving) the U-SIG. For example, the PHY-RXEARLYSIG.indication primitive may be issued before decoding (receiving) U-SIG-1 and / or U-SIG-2. A PHY may issue the PHY-RXSTART.indication primitive. The STA's PHY may issue the PHY-RXSTART.indication primitive. The AP's PHY may issue the PHY-RXSTART.indication primitive.

[0192] STA or AP does not have to issue a PHY-RXSTART.indication primitive for PPDUs that do not overlap with the primary channel and / or the NPCA primary channel. STA or AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the NPCA primary channel. In NPCA, STA may issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the primary channel but overlaps with the NPCA primary channel. In NPCA, AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the primary channel but overlaps with the NPCA primary channel. In NPCA, STA does not have to issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the NPCA primary channel. In NPCA, AP does not have to issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the NPCA primary channel. The primary channel and the NPCA primary channel may be different channels. PHY may issue a PHY-RXSTART.indication primitive. The STA's PHY may issue a PHY-RXSTART.indication primitive. The AP's PHY may also issue a PHY-RXSTART.indication primitive.

[0193] When an AP receives a PPDU requested by an AP on the NPCA primary channel, the AP may issue a PHY-RXSTART.indication primitive. The AP may also issue a PHY-RXSTART.indication primitive for PPDUs that do not overlap with the primary channel. The AP is not required to issue a PHY-RXSTART.indication primitive for PPDUs that do not overlap with the primary channel or the NPCA primary channel. When an AP receives a PPDU requested by an AP on the NPCA primary channel, NPCA secondary 20MHz channel, NPCA secondary 40MHz channel, or NPCA secondary 80MHz channel, the AP may issue a PHY-RXSTART.indication primitive. The AP may assign a PPDU to an STA, and when it receives the assigned PPDU on the NPCA primary channel, NPCA secondary 20MHz channel, NPCA secondary 40MHz channel, or NPCA secondary 80MHz channel, it may issue a PHY-RXSTART.indication primitive. In NPCA, when an AP receives a PPDU requested by an AP on the NPCA primary channel, NPCA secondary 20MHz channel, NPCA secondary 40MHz channel, or NPCA secondary 80MHz channel, it may issue a PHY-RXSTART.indication primitive.In other words, in NPCA, an AP may issue a PHY-RXSTART.indication primitive when it assigns a PPDU to an STA and receives the assigned PPDU on the NPCA primary channel, NPCA secondary 20MHz channel, NPCA secondary 40MHz channel, or NPCA secondary 80MHz channel. In NPCA, an AP may issue a PHY-RXSTART.indication primitive for PPDUs that do not overlap with the primary channel. In NPCA, an AP does not have to issue a PHY-RXSTART.indication primitive for PPDUs that do not overlap with the primary channel or the NPCA primary channel. In NPCA, if the PPDU is requested by the AP, an AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the NPCA primary channel. In NPCA, if the PPDU is not requested by the AP, an AP does not have to issue a PHY-RXSTART.indication primitive for PPDUs that do not overlap with the NPCA primary channel. The primary channel and the NPCA primary channel may be different channels. A PHY may issue a PHY-RXSTART.indication primitive. A STA's PHY may issue a PHY-RXSTART.indication primitive. An AP's PHY may issue a PHY-RXSTART.indication primitive.

[0194] PPDU may be non-HT PPDU. Non-HT PPDU may be called PPDU. PPDU may be HT PPDU. HT PPDU may be called PPDU. PPDU may be VHT PPDU. VHT PPDU may be called PPDU. PPDU may be HE PPDU. HE PPDU may be called PPDU. PPDU may be EHT PPDU. EHT PPDU may be called PPDU. PPDU may be UHR PPDU. UHR PPDU may be called PPDU.

[0195] The non-HT PPDU format may consist of a PHY Preamble, a PHY Header, and an MDPU. The PHY Preamble may consist of a SYNC field and an SFD field. The PHY Header may consist of a SIGNAL field, a SERVICE field, a LENGTH field, and a CRC field. The non-HT PPDU format may consist of a PHY Preamble, a PHY Header, and a PSDU. The non-HT PPDU format may consist of a PHY Preamble, a SIGNAL field, and a DATA field. The DATA field may consist of a SERVICE field, a PSDU field, a Tail field, and Pad Bits. The SIGNAL field may consist of a RATE field, a Reserved field, a LENGTH field, a Parity field, and a Tail field. The PHY Header may consist of a RATE field, a Reserved field, a LENGTH field, a Parity field, a Tail field, and a SERVICE field. The non-HT PPDU format may consist of an L-STF field, a L-LTF field, a L-SIG field, and a Data field. The Data field may consist of the SERVICE field, Scrambled PSDU field, Tail bits field, and Pad bits field. The HT PPDU format may consist of the L-STF field, L-LTF field, L-SIG field, HT-SIG field, HT-STF field, HT-LTF field, and Data field. The HT PPDU format may consist of the HT GF STF field, HT LTF1 field, HT-SIG field, HT-STF field, HT-LTF field, and Data field. The VHT PPDU format may consist of the L-STF field, L-LTF field, L-SIG field, VHT-SIG-A field, VHT-STF field, VHT-LTF field, VHT-SIG-B field, and Data field.

[0196] At 20MHz, the number of tones in the L-STF field may be 12, the number of tones in the L-LTF field may be 52, and the number of tones in the L-SIG field may be 52. At 40MHz, the number of tones in the L-STF field may be 24, the number of tones in the L-LTF field may be 104, the number of tones in the L-SIG field may be 104, the number of tones in NON_HT_DUP_OFDM-Date may be 104, and the number of tones in Non-HT Duplicate field may be 104. At 80MHz, the number of tones in the L-STF field may be 48, the number of tones in the L-LTF field may be 208, the number of tones in the L-SIG field may be 208, and the number of tones in NON_HT_DUP_OFDM-Date may be 208. At 160MHz, the number of tones in the L-STF field may be 96, the number of tones in the L-LTF field may be 416, the number of tones in the L-SIG field may be 416, and the number of tones in NON_HT_DUP_OFDM-Date may be 416.

[0197] HE PPDU may also be HE TB PPDU. HE TB PPDU may be called HE PPDU. HEPPDU may also be HE SU PPDU. HE SU PPDU may be called HE PPDU. HE PPDU may also be HE ER SU PPDU. HE SU ER PPDU may be called HE PPDU. HE PPDU may also be HE MU PPDU. HE MU PPDU may be called HE PPDU. The HE SU PPDU format may consist of an L-STF field, an L-LTF field, an L-SIG field, an RL-SIG field, an HE-SIG-A field, an HE-STF field, an HE-LTF field, a Data field, and a PE field. The HE MU PPDU format may consist of an L-STF field, an L-LTF field, an L-SIG field, an RL-SIG field, an HE-SIG-A field, an HE-SIG-B field, an HE-STF field, an HE-LTF field, a Data field, and a PE field. The HE ER SU PPDU format may consist of an L-STF field, an L-LTF field, an L-SIG field, an RL-SIG field, an HE-SIG-A field, an HE-STF field, an HE-LTF field, a Data field, and a PE field. The HE TB PPDU format may consist of an L-STF field, an L-LTF field, an L-SIG field, an RL-SIG field, an HE-SIG-A field, an HE-STF field, an HE-LTF field, a Data field, and a PE field. A HE ER SU PPDU (High-Efficiency Extended Range Single User PPDU) is a PPDU transmitted in the HEER SU PPDU format and may be a PPDU that transmits a single PSDU. A HE SU PPDU (High-Efficiency Single User PPDU) is a PPDU transmitted in the HE SU PPDU format, and may be a PPDU that transmits a single PSDU.A HE TB PPDU (High-Efficiency Trigger Based PPDU) is a PPDU transmitted in HE TB PPDU format and may be a PPDU that transmits a single PSDU. A HE MU PPDU (High-Efficiency Multi-User PPDU) may be a PPDU transmitted in HE MU PPDU format.

[0198] EHT PPDU may also be EHT TB PPDU. EHT TB PPDU may be referred to as EHT PPDU. EHT PPDU may also be EHT MU PPDU. EHT MU PPDU may be referred to as EHT PPDU. EHT MU PPDU may be an EHT PPDU format used for transmissions that are not responses to a trigger frame. EHT MU PPDU may transmit one or more PSDUs. EHT TB PPDU may be an EHT PPDU format used for transmitting responses to a trigger frame. EHT TB PPDU may transmit one PSDU. The EHT MU PPDU format may consist of an L-STF field, an L-LTF field, an L-SIG field, an RL-SIG field, a U-SIG field, an EHT-SIG field, an EHT-STF field, an EHT-LTF field, a Data field, and a PE field. The EHT TB PPDU format may consist of an L-STF field, an L-LTF field, an L-SIG field, an RL-SIG field, a U-SIG field, an EHT-STF field, an EHT-LTF field, a Data field, and a PE field.

[0199] A UHR PPDU may also be a UHR TB PPDU. A UHR TB PPDU may be referred to as a UHR PPDU. A UHR PPDU may also be a UHR MU PPDU. A UHR MU PPDU may be referred to as a UHR PPDU. A UHR PPDU may also be a UHR SU PPDU. A UHR SU PPDU may be referred to as a UHR PPDU. A UHR MU PPDU may be a PPDU used for transmissions that are not responses to a trigger frame using the UHR PPDU format. A UHR MU PPDU may transmit one or more PSDUs. A UHR TB PPDU may be a PPDU used for transmitting responses to a trigger frame using the UHR PPDU format. A UHR TB PPDU may transmit one PSDU. A UHR TB PPDU may transmit multiple PSDUs. For example, the UHR MU PPDU format may consist of L-STF fields, L-LTF fields, L-SIG fields, RL-SIG fields, U-SIG fields, UHR-SIG fields, UHR-STF fields, UHR-LTF fields, Data fields, PE fields, etc. The UHR MU PPDU format may consist of fields other than those mentioned above. For example, the UHR TB PPDU format may consist of L-STF fields, L-LTF fields, L-SIG fields, RL-SIG fields, U-SIG fields, UHR-STF fields, UHR-LTF fields, Data fields, PE fields, etc. The UHR TB PPDU format may consist of fields other than those mentioned above. UHR PPDU may also be called HT PPDU. UHR PPDU may also be HT PPDU. The UHR PPDU format may include the same fields as the HT PPDU format. UHR PPDU may also be called VHT PPDU. A UHR PPDU may also be a VHT PPDU. The UHR PPDU format may contain the same fields as the VHT PPDU format.UHR PPDU may also be called HE PPDU. UHR PPDU may be HE PPDU. The UHR PPDU format may contain the same fields as the HE PPDU format. UHR PPDU may also be called EHT PPDU. UHR PPDU may be EHT PPDU. The UHR PPDU format may contain the same fields as the EHT PPDU format.

[0200] Non-HT (non-High Throughput) may be a modifier meaning that it is not high throughput (HT), very high throughput (VHT), or high efficiency (HE). Non-HT may also be a modifier meaning that it is not HT, VHT, HE, EHT, or UHR. For example, non-HT PPDU may mean that it is not HT PPDU, VHT PPDU, HE PPDU, EHT PPDU, or UHR PPDU. Non-HT duplicate may be a physical layer (PHY) transmission format that duplicates a 20MHz non-HT transmission across two or more 20MHz channels so that an STA on any of the 20MHz channels in a non-HT basic service set (BSS) can receive the transmission. The non-HT duplicate format may be one of the following: 40MHz non-HT duplicate, 80MHz non-HT duplicate, 160MHz non-HT duplicate, 80+80MHz non-HT duplicate, or 320MHz non-HT duplicate. 40MHz non-HT duplicate may be a PHY transmission format that duplicates a 20MHz non-HT transmission on two adjacent 20MHz channels. 80MHz non-HT duplicate may be a PHY transmission format that duplicates a 20MHz non-HT transmission on four adjacent 20MHz channels. 160MHz non-HT duplicate may be a PHY transmission format that duplicates a 20MHz non-HT transmission on eight adjacent 20MHz channels. 80+80MHz non-HT duplicate may be a PHY transmission format that duplicates a 20MHz non-HT transmission on two frequency segments of four adjacent 20MHz channels.320MHz non-HT duplicate may also be a PHY transmission format that duplicates 20MHz non-HT transmission using 16 adjacent 20MHz channels.

[0201] A non-HT duplicate frame may be a frame transmitted as a non-HT duplicate of a physical layer (PHY) protocol date unit (PPDU). A non-HT PPDU (non-high throughput physical layer protocol date unit) is a PPDU transmitted from a PHY whose TXVECOTR FORMAT parameter may be a value other than a predetermined value. For example, a non-HT PPDU may be a PPDU transmitted from a PHY whose TXVECOTR FORMAT parameter is not equal to HT_MF, HT_GF, or VHT. For example, a non-HT PPDU may be a PPDU transmitted from a DSSS PHY, HR / DSSS PHY, OFDM PHY, or ERP PHY whose TXVECOTR FORMAT parameter is not equal to HT_MF, HT_GF, or VHT. A non-HT duplicate PPDU (non-high throughput duplicate physical layer protocol date unit) may be a PPDU sent from a PHY with the TXVECTOR FORMAT parameter set to NON_HT and the CH_BANDWIDTH parameter set to NON_HT_CBW40, CBW40, CBW80, CBW160, or CBW80+80, or CBW320. For example, a non-HT duplicate PPDU may be a PPDU sent from an HT PHY or VHT PHY with the TXVECTOR FORMAT parameter set to NON_HT and the CH_BANDWIDTH parameter set to NON_HT_CBW40, CBW40, CBW80, CBW160, or CBW80+80, or CBW320.

[0202] AP may send a trigger frame. For example, the trigger frame may be a control frame. For example, the trigger frame may be a frame in the MAC header where the Type subfield of the Frame Control field is Control and the subtype subfield is Trigger. For example, the trigger frame may be a frame in the MAC header where the Type subfield of the Frame Control field is 01 and the subtype subfield is 0010. The trigger frame may be a frame other than those described above. STA may send a trigger frame. The trigger frame may be a date frame. The trigger frame may be a management frame.

[0203] A trigger frame may allocate resources and solicit one or more TB PPDU transmissions. A trigger frame may also transmit other information necessary for a responding STA to transmit a TB PPDU. A trigger frame that is not a MU-RTS trigger frame may allocate resources and solicit one or more TB PPDU transmissions. A MU-RTS trigger frame may allocate resources for one or more PPDUs that are not TB PPDUs. A trigger frame may consist of fields such as Frame Control, Duration, RA, TA, Common Info, User Info List, padding, FCS, etc. The Common Info field may be an HE variant Common Info field, an EHT variant Common Info field, or a UHR variant Common Info field. The Common Info field may include subfields such as TriggerType subfield, UL BW subfield, and CS Required subfield.

[0204] In a MU-RTS trigger frame, the Duration / ID field may be set to the estimated time (in microseconds) required to send the pending frame, the time required to send one CTS frame and, if necessary, the requested TBPPDU, the time required to send an acknowledgment for the requested TB PPDU, and the applicable IFS. In a Basic trigger frame, the Duration / ID field may be set to the estimated time required to send the requested TB PPDU, the estimated time required to send an acknowledgment for the requested TB PPDU, and the applicable SIFS.

[0205] The Duration / ID field of a CTS frame sent in response to a MU-RTS Trigger frame may be set to the Duration / ID field of the MU-RTS Trigger frame that triggered the CTS frame, minus the time (in microseconds) from the end of the PPDU containing the MU-RTS Trigger frame to the end of the PPDU containing the CTS frame.

[0206] If the CTS frame is a response to an RTS frame, the RA field of the CTS frame may be set to the address of the TA field of the RTS frame with Individual / Group set to 0. If the CTS frame is the first frame in a frame exchange, the RA field may be set to the source MAC address. If the CTS frame is a response to an MU-RTS Trigger frame, the RA field of the CTS frame may be set to the address of the TA field of the MU-RTS Trigger frame.

[0207] For example, a TB PPDU (Trigger Based PPDU) may be used for transmissions that are responses to a trigger frame. For example, a TB PPDU may transmit a single PSDU (Physical Layer Service Date Unit). For example, a MU PPDU (Multi-User PPDU) may be used for transmitting one or more PSDSs.

[0208] The Trigger Type subfield may identify the Trigger frame variant. If the value of the Trigger Type subfield is 0, the Trigger frame variant may be Basic. That is, if the value of the Trigger Type subfield is 0, the Trigger frame format may be Basic Trigger frame format. If the value of the Trigger Type subfield is 1, the Trigger frame variant may be Beamforming Report Poll (BFRP). That is, if the value of the Trigger Type subfield is 1, the Trigger frame format may be BFRP Trigger frame format. If the value of the Trigger Type subfield is 2, the Trigger frame variant may be MU-BAR. That is, if the value of the Trigger Type subfield is 2, the Trigger frame format may be MU-BAR Trigger frame format. If the value of the Trigger Type subfield is 3, the Trigger frame variant may be MU-RTS. That is, if the value of the Trigger Type subfield is 3, the Trigger frame format may be MU-RTS Trigger frame format. If the value of the Trigger Type subfield is 4, the Trigger frame variant may be BufferStatus Report Poll (BSRP). In other words, if the value of the Trigger Type subfield is 1, the Trigger frame format may be the BSRP Trigger frame format.

[0209] The CS Required subfield in the Common Info field may be set to 1 to indicate that the STA identified in the User Info field should consider the medium state and NAV when deciding whether to respond using the ED to detect medium. The CS Required subfield may be set to 0 to indicate that the STA identified in the User Info field does not need to consider the medium state or NAV when deciding whether to respond.

[0210] The UL BW subfield in the Common Info field may indicate the bandwidth of the TB PPDU. The UL BW subfield in the Common Info field may indicate the bandwidth of the HE-SIG-A field of the HE TB PPDU. HE variant The UL BW subfield in the Common Info field may indicate the bandwidth of the HE-SIG-A field of the HE TB PPDU. For example, if the UL BW subfield value is 0, it may be 20MHz. If the UL BW subfield value is 1, it may be 40MHz. If the UL BW subfield value is 2, it may be 80MHz. If the UL BW subfield value is 3, it may be 80+80MHz or 160MHz. EHT variant The UL BW subfield in the Common Info field may indicate the bandwidth of the U-SIG field of the EHT TB PPDU together with the UL BW Extension subfield in the Special User Info field. For example, when the UL BW subfield is 0 and the UL BW Extension subfield is 0, the bandwidth of the EHT TB PPDU may be 20MHz. When the UL BW subfield is 1 and the UL BW Extension subfield is 0, the bandwidth of the EHT TB PPDU may be 40 MHz. When the UL BW subfield is 2 and the UL BW Extension subfield is 0, the bandwidth of the EHT TB PPDU may be 80 MHz. When the UL BW subfield is 3 and the UL BW Extension subfield is 1, the bandwidth of the EHT TB PPDU may be 160 MHz. When the UL BW subfield is 3 and the UL BW Extension subfield is 2, the bandwidth of the EHT TB PPDU may be 320 MHz.When the UL BW subfield is 3 and the UL BW Extension subfield is 3, the bandwidth of the EHT TB PPDU may be 320 MHz. The UL BW Extension subfield may also be called the UL Bandwidth Extension subfield. The UL Bandwidth Extension subfield, together with the UL BW subfield in the Common Info field, may indicate the bandwidth of the requested TB PPDU.

[0211] The User Info List field may contain zero or more User Info fields. The User Info List field may contain zero or more User Info fields. User Info fields may include AID12 subfield, RU Allocation subfield, UL FEC Coding Type subfield, UL HEMCS subfield, UL DCM subfield, SS Allocation / RA-RU Information subfield, UL Target Receive Power subfield, Trigger Dependent User Info subfield, UL EHT MCS subfield, SS Allocation subfield, PS160 subfield, etc. The User Info field may also be an HE variant User Info field. The User Info field may also be an EHT variant User Info field. The HE variant User Info field may also be a User Info field. The EHT variant User Info field may also be a User Info field. The HE variant User Info field may also be referred to as a User Info field. The EHT variant User Info field may also be referred to as a User Info field.

[0212] For example, if the AID12 subfield is 0, the User Info field may assign one or more consecutive RA-RUs (Random Access Resource Units) to the associated STA(s). For example, if the AID12 subfield is 1 to 2007, the User Info field may be assigned to the associated STA whose AID is equal to the value of the AID12 subfield. For example, if the AID12 subfield is 2008 to 2044, it may be Reserved. For example, if the AID12 subfield is 2045, the User Info field may assign one or more consecutive RA-RUs to an unassociated STA. For example, if the AID12 subfield is 2046, it may be Unallocated RU. For example, if the AID12 subfield is 2047 to 4094, it may be Reserved. For example, if the AID12 subfield is 4095, it may be the start of a Padding field. For example, if the AID12 subfield is 4095, it may be set to Disallowed in the User Info field because it indicates the start of a Padding field.

[0213] The RU Allocation subfield may specify the size and location of the RU together with the UL BW subfield in the Common Info field. If the UL BW subfield indicates a 20MHz, 40MHz, or 80MHz PPDU, B0 in the RU Allocation subfield may be set to 0. If the UL BW subfield indicates an 80+80 MHz or 160 MHz PPDU, B0 in the RU Allocation subfield may be set to 0 to indicate that the RU Allocation applies to the primary 80 MHz channel, and to 1 to indicate that the RU Allocation applies to the secondary 80MHz channel. The B7-B1 mapping of the RU Allocation subfield for trigger frames that are not MU-RTS trigger frames may be defined in a table. If the UL BW subfield indicates 20MHz, the mapping of the RU to the RU index may be defined in a table. If the UL BW subfield indicates 40MHz, the mapping of the RU to the RU index may be defined in a table. If the UL BW subfield indicates 80MHz, 160MHz, or 80+80MHz, the mapping of RUs to the RU index may be defined in a table. Figure 14 may be a table in which the B7-B1 mapping of the RU Allocation subfield for trigger frames that are not MU-RTS trigger frames is defined. Figure 15 may be a table in which the mapping of RUs to the RU index is defined when the UL BW subfield indicates 20MHz.

[0214] Figure 14 shows an example of the size and arrangement of RUs based on an RU Allocation subfield and a UL BW subfield according to one aspect of this embodiment. The RU size and RU index may be determined from a table in which the B7-B1 mapping of the RU Allocation subfield is defined. For example, if B7-B1 of the RU Allocation subfield indicates 0, and the UL BW subfield indicates 20MHz, 40MHz, 80MHz, 80+80MHz, or 160MHz, the RU size may be 26 and the RU index may be RU1. Here, 0 to 8 in B7-B1 of the RU Allocation subfield may correspond to RU1 to RU9 of the RU index, respectively. That is, if B7-B1 of the RU Allocation subfield is 0, it corresponds to RU1; if it is 1, it corresponds to RU2; if it is 2, it corresponds to RU3; if it is 3, it corresponds to RU4; if it is 4, it corresponds to RU5; if it is 5, it corresponds to RU6; if it is 6, it corresponds to RU7; if it is 7, it corresponds to RU8; and if it is 8, it corresponds to RU9.

[0215] Figure 14 shows an example of the size and arrangement of RUs based on an RU Allocation subfield and a UL BW subfield according to one aspect of this embodiment. The RU size and RU index may be determined from a table in which the B7-B1 mapping of the RU Allocation subfield is defined. For example, if B7-B1 of the RU Allocation subfield indicates 0, and the UL BW subfield indicates 20MHz, 40MHz, 80MHz, 80+80MHz, or 160MHz, the RU size may be 26 and the RU index may be RU1. Here, 0 to 8 in B7-B1 of the RU Allocation subfield may correspond to RU1 to RU9 of the RU index, respectively. That is, if B7-B1 of the RU Allocation subfield is 0, it corresponds to RU1; if it is 1, it corresponds to RU2; if it is 2, it corresponds to RU3; if it is 3, it corresponds to RU4; if it is 4, it corresponds to RU5; if it is 5, it corresponds to RU6; if it is 6, it corresponds to RU7; if it is 7, it corresponds to RU8; and if it is 8, it corresponds to RU9.

[0216] Figure 15 shows an example of a table defining the mapping between RU index and RU when the UL BW subfield is 20MHz according to one aspect of this embodiment. For example, if the RU type is 26-tone RU and RU1, 26 tones with subcarrier indices from -121 to -96 may be used for PPDU transmission. The RU type may also be the RU size. RU1 may have an RU index of 1. If the RU type is 242-tone RU and RU1, 242 tones with subcarrier indices from -122 to -2 and from 2 to 122 may be used for PPDU transmission. Subcarrier index 0 may correspond to a DC tone. In Figure 14, if the RU Allocation subfield is 61 and the UL BW subfield is 20MHz, the RU size corresponds to 242 and the RU index corresponds to RU1. In Figure 15, if the RU size is 242 and the RU index is 1, the subcarrier index may correspond to 242 tones from -122 to -2 and from 2 to 122.

[0217] Along with the UL BW subfield in the Common Info field, the RU Allocation subfield in the HE variant User Info field may specify the size and location of the RU. If the UL BW subfield indicates 20MHz, 40MHz, or 80MHz, B0 in the RU Allocation subfield may be set to 0. If the UL BW subfield indicates 80+80MHz or 160MHz, B0 in the RU Allocation subfield may be set to 0 to indicate that the RU Allocation applies to the primary 80MHz channel, and to 1 to indicate that the RU Allocation applies to the secondary 80MHz channel. The mapping of B7-B1 in the RU Allocation subfield for trigger frames that are not MU-RTS trigger frames may be defined in a table. If the UL BW subfield indicates 20MHz, the mapping of RUs to RU indices may be defined in a table. If the UL BW subfield indicates 40MHz, the mapping of RUs to RU indices may be defined in a table. If the UL BW subfield indicates 80MHz, 160MHz, or 80+80MHz, the mapping of RUs to the RU index may be defined in a Table.

[0218] The RUAllocation subfield of the EHT variant User Info field of a trigger frame that is not a MU-RTS trigger frame may identify the size and location of the RU or MRU, along with the UL BW subfield of the Common Info field, the UL BW Extension subfield of the Special User Info field, and the PS160 subfield of the EHT variant User Info field. The B7-B1 mapping of the RU Allocation subfield and the settings of the B0 and PS160 subfields of the RU Allocation subfield of the EHT variant User Info field may be defined in a Table, where the bandwidth may be defined in a Table and obtained from a combination of the UL BW subfield and the UL Bandwidth Extension subfield.

[0219] RU size may be the number of tones. Tone may be a subcarrier. The number of tones may be the number of subcarriers. For example, the subcarrier interval may be 312.5 kHz. For example, the subcarrier interval may be 78.125 kHz. The subcarrier interval may be a value other than those mentioned above. For example, the subcarrier interval of a non-HT PPDU may be 78.125 kHz. For example, the subcarrier interval of an HT PPDU may be 78.125 kHz. For example, the subcarrier interval of a VHT PPDU may be 78.125 kHz. For example, the subcarrier interval of an HE PPDU may be 78.125 kHz. For example, the subcarrier interval of an EHT PPDU may be 78.125 kHz. For example, the subcarrier interval of a UHR PPDU may be 78.125 kHz. For example, the subcarrier interval of a non-HT PPDU may be 312.5 kHz. For example, the subcarrier interval of an HT PPDU may be 312.5 kHz. For example, the subcarrier spacing of a VHT PPDU may be 312.5 kHz. For example, the subcarrier spacing of an HE PPDU may be 312.5 kHz. For example, the subcarrier spacing of an EHT PPDU may be 312.5 kHz. For example, the subcarrier spacing of a UHR PPDU may be 312.5 kHz. Different subcarrier spacings may be used for each PPDU. For example, the subcarrier spacing of non-HT PPDU, HT PPDU, and VHT PPDU may be 78.125 kHz, while the subcarrier spacing of HE PPDU, EHT PPDU, and UHR PPDU may be 312.5 kHz.

[0220] The UL BW subfield in the Common Info field may indicate the bandwidth of the PPDU that transmits the MU-RTS Trigger frame. The UL BW subfield in the Common Info field may indicate the bandwidth of the PPDU that transmits the MU-RTS Trigger frame, together with the UL BW Extension subfield in the Special User Info field (if present).

[0221] The RU Allocation subfield in the User Info field addressed to the STA may indicate whether the CTS frame is transmitted on the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, or 320MHz channel. To indicate the primary 20MHz channel, primary 40MHz channel, or primary 80MHz channel, B0 in the RU Allocation subfield may be set to 0. For 160MHz and 80+80MHz indications, B0 in the RU Allocation subfield may be set to 1. B0 in the RU Allocation subfield may be set to 0 to indicate the primary 20MHz channel, primary 40MHz channel, or primary 80MHz channel. When indicating primary 160MHz, 80+80MHz, or 320MHz, B0 in the RU Allocation subfield may be set to 1. The PS160 subfield in the User Info field may be set to 1 to indicate the 320MHz channel, and may be set to 0 to indicate the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, and primary 160MHz channel.

[0222] For example, the RU Allocation subfield may be an 8-bit subfield. The 8 bits of the RU Allocation subfield may be represented as B0, B1, B2, B3, B4, B5, B6, B7 (B0-B7). For example, the first bit of the RU Allocation subfield (the most significant bit, MSB) may be B0. The second bit of the RU Allocation subfield may be B1. The third bit of the RU Allocation subfield may be B2. The fourth bit of the RU Allocation subfield may be B3. The fifth bit of the RU Allocation subfield may be B4. The sixth bit of the RU Allocation subfield may be B5. The seventh bit of the RU Allocation subfield may be B6. The eighth bit of the RU Allocation subfield (the least significant bit, LSB) may be B7. For example, the first bit of the RU Allocation subfield (the most significant bit, MSB) may be B7. The second bit of the RU Allocation subfield may be B6. The third bit of the RU Allocation subfield may be B5. The fourth bit of the RU Allocation subfield may be B4. The fifth bit of the RU Allocation subfield may be B3. The sixth bit of the RU Allocation subfield may be B2. The seventh bit of the RU Allocation subfield may be B1. The eighth bit of the RU Allocation subfield (the least significant bit, LSB) may be B0. The correspondence between the RU Allocation subfield and bits B0-B7 may be other than those described above.

[0223] B7-B1 of the RU Allocation subfield may be set to indicate the primary 20MHz channel as follows: - If the primary 20MHz channel is the only 20MHz channel, or the lowest frequency 20MHz channel in the primary 40MHz channel or primary 80MHz channel, 61. - If the primary 20MHz channel is the second lowest frequency 20MHz channel in the primary 40MHz channel or primary 80MHz channel, 62. - If the primary 20MHz channel is the third lowest frequency 20MHz channel in the primary 80MHz channel, 63. - If the primary 20MHz channel is the fourth lowest frequency 20MHz channel in the primary 80MHz channel, 64.

[0224] When an AP requests the STA to transmit a CTS in response to MU-RTS, it may indicate 61, 62, 63, or 64 in the RU allocation subfield of MU-RTS to request the STA to transmit a CTS on the primary 20MHz channel. The STA may transmit a CTS on the primary 20MHz channel if the RU allocation subfield of the MU-RTS transmitted from the AP indicates 61, 62, 63, or 64. If the primary 20MHz channel is the only 20MHz channel, the RU allocation subfield may be set to 61. The only 20MHz channel may have an operating channel width of 20MHz. The only 20MHz channel may have a channel width of 20MHz in MU-RTS. If the primary 20MHz channel is the lowest frequency 20MHz channel in the primary 40MHz channel, the RU allocation subfield may be set to 61. If the primary 20MHz channel is the lowest frequency 20MHz channel in the primary 80MHz channel, the RU allocation subfield may be set to 61. If the primary 20MHz channel is the lowest frequency 20MHz channel in the primary 160MHz channel, the RU allocation subfield may be set to 61. If the primary 20MHz channel is the second lowest frequency 20MHz channel in the primary 40MHz channel, the RU allocation subfield may be set to 62. If the primary 20MHz channel is the second lowest frequency 20MHz channel in the primary 80MHz channel, the RU allocation subfield may be set to 62.If the primary 20MHz channel is the second lowest frequency 20MHz channel in the primary 160MHz channel, the RU allocation subfield may be set to 62. If the primary 20MHz channel is the third lowest frequency 20MHz channel in the primary 80MHz channel, the RU allocation subfield may be set to 63. If the primary 20MHz channel is the third lowest frequency 20MHz channel in the primary 160MHz channel, the RU allocation subfield may be set to 63. If the primary 20MHz channel is the fourth lowest frequency 20MHz channel in the primary 80MHz channel, the RU allocation subfield may be set to 64. If the primary 20MHz channel is the fourth lowest frequency 20MHz channel in the primary 160MHz channel, the RU allocation subfield may be set to 64. A value other than those mentioned above may be set in the RU allocation subfield to indicate the primary 20MHz channel.

[0225] B7-B1 of the RU Allocation subfield may be set to indicate the primary 40MHz channel as follows: - If the primary 40MHz channel is the only 40MHz channel or the lowest frequency 40MHz channel in the primary 80MHz channel, 65. - If the primary 40MHz channel is the second lowest frequency in the primary 80MHz channel, 66.

[0226] When an AP requests the STA to transmit a CTS in response to MU-RTS, it may indicate 65 or 66 in the RU allocation subfield of MU-RTS to request the STA to transmit a CTS on the primary 40MHz channel. If the RU allocation subfield of the MU-RTS transmitted from the AP indicates 65 or 66, the STA may transmit a CTS on the primary 40MHz channel. If the primary 40MHz channel is the only 40MHz channel, the RU allocation subfield may be set to 65. If the primary 40MHz channel is the lowest frequency 40MHz channel in the primary 80MHz channel, the RU allocation subfield may be set to 65. If the primary 40MHz channel is the lowest frequency 40MHz channel in the primary 160MHz channel, the RU allocation subfield may be set to 65. If the primary 40MHz channel is the second lowest frequency 40MHz channel in the primary 80MHz channel, the RU allocation subfield may be set to 66. If the primary 40MHz channel is the second lowest frequency 40MHz channel in the primary 160MHz channel, the RU allocation subfield may be set to 66. If the primary 40MHz channel is the third lowest frequency 40MHz channel in the primary 160MHz channel, a predetermined value may be set to the RU allocation subfield. If the primary 40MHz channel is the fourth lowest frequency 40MHz channel in the primary 160MHz channel, a predetermined value may be set to the RU allocation subfield.Other values ​​may be set in the RU allocation subfield to indicate the primary 40MHz channel.

[0227] B7-B1 of the RU Allocation subfield may be set to 67 to indicate the primary 80MHz channel. B7-B1 of the RU Allocation subfield may be set to 68 to indicate the primary and secondary 80MHz channels (primary 80MHz channel and secondary 80MHz channel). B7-B1 of the RU Allocation subfield may be set to 68 to indicate the primary 80MHz channel and secondary 80MHz channel when the bandwidth of the PPDU transmitting the MU-RTS Trigger frame is less than 320MHz, or to indicate the primary 160MHz channel when the bandwidth of the PPDU transmitting the MU-RTS Trigger frame is 320MHz. B7-B1 of the RU Allocation subfield may be set to 68 to indicate the primary 80MHz channel and secondary 80MHz channel when the bandwidth of the PPDU transmitting the MU-RTS Trigger frame is less than 320MHz. The B7-B1 of the RU Allocation subfield may be set to 68 to indicate the primary 160MHz channel when the bandwidth of the PPDU transmitting the MU-RTS Trigger frame is 320MHz. The B7-B1 of the RU Allocation subfield may be set to 69 to indicate the 320MHz channel.

[0228] When AP requests STA to transmit CTS in response to MU-RTS, AP may indicate 67 in the RU allocation subfield of MU-RTS to request STA to transmit CTS on the primary 80MHz channel. If 67 is indicated in the RU allocation subfield of the MU-RTS transmitted from AP, STA may transmit CTS on the primary 80MHz channel. The RU allocation subfield may be set to 67 to indicate the primary 80MHz channel. The RU allocation subfield may be set to 67 if the primary 80MHz channel is the lowest frequency 80MHz channel in the primary 160MHz channel. If the primary 80MHz channel is the second lowest frequency 80MHz channel in the primary 160MHz channel, a predetermined value may be set in the RU allocation subfield.

[0229] When an AP requests an STA to transmit a CTS in response to a MU-RTS, it may indicate 68 in the RU allocation subfield of the MU-RTS to request the STA to transmit a CTS on the primary 160MHz channel. If the STA receives a MU-RTS from the AP and the RU allocation subfield indicates 68, the STA may transmit a CTS on the primary 160MHz channel. When an AP requests an STA to transmit a CTS in response to a MU-RTS, it may indicate 68 in the RU allocation subfield of the MU-RTS to request the STA to transmit a CTS on the primary 80MHz channel and the secondary 80MHz channel. If the STA receives a MU-RTS from the AP and the RU allocation subfield indicates 68, the STA may transmit a CTS on the primary 80MHz channel and the secondary 80MHz channel. The transmission of a CTS on the primary 80MHz channel and the secondary 80MHz channel may also be transmitted on the 80+80MHz channel.

[0230] When AP requests STA to transmit CTS in response to MU-RTS, AP may indicate 69 in the RU allocation subfield of MU-RTS to request STA to transmit CTS on the 320MHz channel. STA may transmit CTS on the 320MHz channel if 69 is indicated in the RU allocation subfield of MU-RTS transmitted from AP.

[0231] Figure 16 shows an example of B7-B1 of the UL BW subfield and RU Allocation subfield of a MU-RTS Trigger frame according to one aspect of this embodiment. Figure 16 may also show the setting of B7-B1 of the RU Allocation subfield. 1601, 1602, 1603, 1604, 1605, 1606, 1607, and 1608 may be 20MHz channels. 1609, 1610, 1611, and 1612 may be the bandwidth of the PPDU carrying the MU-RTS Trigger frame. 1609, 1610, 1611, and 1612 may be the values ​​indicated in the UL BW subfield. 1609 may be 20MHz indicated in the UL BW subfield. 1610 may be 40MHz indicated in the UL BW subfield. 1611 may be 80MHz indicated in the UL BW subfield. 1612 may be indicated as 160MHz or 80+80MHz in the UL BW subfield. 1613 may be indicated as B0 of the RU Allocation subfield being 0. 1614 may be indicated as B0 of the RU Allocation subfield being 1. 1615, 1616, 1617, 1618, 1619, 1620, 1621, and 1622 may be channels on which CTS frames are transmitted. Any of 1615, 1616, 1617, 1618, 1619, 1620, 1621, or 1622 may be indicated in the RU Allocation subfield. 1615, 1616, 1617, and 1618 may be primary 20MHz channels. 1619 and 1620 may be primary 40MHz channels. 1621 may be primary 80MHz channels. 1622 may be 160MHz or 80+80MHz.If a predetermined value (e.g., 61, 62, 63, or 64) is specified in the RU Allocation subfield, the STA may transmit the CTS using the primary 20MHz channel. If a predetermined value (e.g., 65, or 66) is specified in the RU Allocation subfield, the STA may transmit the CTS using the primary 40MHz channel. If a predetermined value (e.g., 67) is specified in the RU Allocation subfield, the STA may transmit the CTS using the primary 80MHz channel. If a predetermined value (e.g., 68) is specified in the RU Allocation subfield, the STA may transmit the CTS using 160MHz or 80+80MHz. If the primary 20MHz channel is the only 20MHz channel, or the lowest frequency 20MHz channel among the primary 40MHz channel or primary 80MHz channel, the predetermined value may be 61. If the primary 20MHz channel is the second lowest frequency in the primary 40MHz channel or primary 80MHz channel, the predetermined value may be 62. If the primary 20MHz channel is the third lowest frequency in the primary 80MHz channel, the predetermined value may be 63. If the primary 20MHz channel is the fourth lowest frequency in the primary 80MHz channel, the predetermined value may be 64. If the primary 40MHz channel is the only 40MHz channel or the lowest frequency 40MHz channel in the primary 80MHz channel, the predetermined value may be 65. If the primary 40MHz channel is the second lowest frequency in the primary 80MHz channel, the predetermined value may be 66.For example, an AP may transmit a MU-RTS Trigger frame with a bandwidth of 1609, 1610, 1611, or 1612, and indicate to each of one or more STAs one of 1615, 1616, 1617, 1618, 1619, 1620, or 1621 in the RU Allocation subfield, and each STA may transmit a CTS on the indicated channel.

[0232] Figure 17 shows an example of B7-B1 of the RU Allocation subfield for MU-RTS Trigger frames of various bandwidths according to one embodiment of this model. Figure 17 may also show the settings for B7-B1 of the RU Allocation subfield. Figure 17 may also show the UL BW subfield and B7-B1 of the RU Allocation subfield for MU-RTS Trigger frames for various bandwidths. 1701, 1702, 1703, 1704, 1705, 1706, 1707, 1708, 1709, 1710, 1711, 1712, 1713, 1714, 1715, 1716 may be 20MHz channels. 1717, 1718, 1719, 1720, 1721 may be the bandwidth of the PPDU carrying the MU-RTS Trigger frame. 1717, 1718, 1719, 1720, and 1721 may be values ​​indicated using the UL BW subfield and UL BW Extension subfield (if present). 1717 may be 20MHz indicated using the UL BW subfield and UL BW Extension subfield (if present). 1718 may be 40MHz indicated using the UL BW subfield and UL BW Extension subfield (if present). 1719 may be 80MHz indicated using the UL BW subfield and UL BW Extension subfield (if present). 1720 may be the primary 160MHz channel or 80+80MHz indicated using the UL BW subfield and UL BW Extension subfield (if present). 1721 may be 320MHz indicated using the UL BW subfield and UL BW Extension subfield (if present). 1722 may be 0 when B0 of the RU Allocation subfield is 0.1723 may be a case where B0 of the RU Allocation subfield is 1. 1724 may be a case where PS160 is 0. 1725 may be a case where PS160 is 0. 1726, 1727, 1728, 1729, 1730, 1731, 1732, 1733, 1734 may be channels on which CTS frames are transmitted. Any of 1726, 1727, 1728, 1729, 1730, 1731, 1732, 1733, 1734 may be indicated by the RU Allocation subfield. 1726, 1727, 1728, 1729 may be primary 20MHz channels. 1730, 1731 may be primary 40MHz channels. 1732 may be primary 80MHz channels. Channel 1733 may be the primary 160MHz channel or 80+80MHz. Channel 1734 may be the primary 160MHz channel or 80+80MHz. If a predetermined value (e.g., 61, 62, 63, or 64) is indicated in the RU Allocation subfield, the STA may transmit the CTS using the primary 20MHz channel. If a predetermined value (e.g., 65, or 66) is indicated in the RU Allocation subfield, the STA may transmit the CTS using the primary 40MHz channel. If a predetermined value (e.g., 67) is indicated in the RU Allocation subfield, the STA may transmit the CTS using the primary 80MHz channel. If a predetermined value (e.g., 68) is indicated in the RU Allocation subfield, the STA may transmit the CTS using the primary 160MHz channel or 80+80MHz. If a predetermined value (e.g., 69) is indicated in the RU Allocation subfield, the STA may transmit the CTS using 320MHz.If the primary 20MHz channel is the only 20MHz channel, or the lowest frequency 20MHz channel among the primary 40MHz channel or primary 80MHz channel, the predetermined value may be 61. If the primary 20MHz channel is the second lowest frequency among the primary 40MHz channel or primary 80MHz channel, the predetermined value may be 62. If the primary 20MHz channel is the third lowest frequency among the primary 80MHz channel, the predetermined value may be 63. If the primary 20MHz channel is the fourth lowest frequency among the primary 80MHz channel, the predetermined value may be 64. If the primary 40MHz channel is the only 40MHz channel, or the lowest frequency 40MHz channel among the primary 80MHz channel, the predetermined value may be 65. If the primary 40MHz channel is the second lowest frequency among the primary 80MHz channel, the predetermined value may be 66. For example, an AP may send a MU-RTS Trigger frame with one of the bandwidths 1717, 1718, 1719, 1720, or 1721, and indicate to each of one or more STAs one of the following in the RU Allocation subfield: 1726, 1727, 1728, 1729, 1730, 1731, 1732, 1733, or 1734, and each STA may send a CTS on the indicated channel.

[0233] The MU-RTS Trigger / CTS frame exchange procedure may allow the AP to initiate TXOP and protect the TXOP frame exchange. The AP may send a MU-RTS Trigger frame to request a CTS frame response simultaneously from one or more STAs.

[0234] Figure 18 shows an example of the exchange of MU-RTS and simultaneous CTS responses according to one aspect of this embodiment. Figure 18 may also be an example of the NAV setting for MU-RTS and / or CTS. 1801 may be an operation of the AP (receive, transmit, etc.). 1802 may be an operation of STA#1 (receive, transmit, etc.). 1803 may be an operation of STA#2 (receive, transmit, etc.). 1804 may be an operation of one or more STAs other than STA#1 and STA#2 (receive, transmit, etc.). 1805 may be a MU-RTS trigger frame that the AP sends to STA#1 and STA#2. 1806 may be a CTS that STA#1 sends to the AP after receiving 1805 from the AP. 1807 may be a CTS that STA#2 sends to the AP after receiving 1805 from the AP. 1808 may be a transmission from the AP to STA#1 and STA#2. For example, 1808 may be a MU PPDU. For example, 1808 may be a PPDU containing a trigger frame. 1809 may be a PPDU that STA#1, which received 1808, sends to the AP. 1810 may be a PPDU that STA#2, which received 1808, sends to the AP. For example, 1809 may be a TB PPDU to the AP. For example, 1810 may be a TB PPDU to the AP. For example, 1809 may be a TB PPDU containing an acknowledgment to the AP. For example, 1810 may be a TB PPDU containing an acknowledgment to the AP. 1811 may be a NAV maintained by an STA other than STA#1 or STA#2, which received 1805. 1812 may be a NAV maintained by an STA other than STA#1 or STA#2, which received 1806 or 1807. For example, 1801 may be the operation (receive, transmit, etc.) of 202 in Figure 2. For example, 1802 may be the operation of 203 in Figure 2 (receiving, transmitting, etc.). For example, 1803 may be the operation of 204 in Figure 2 (receiving, transmitting, etc.). For example, 1803 may be the operation of 207 in Figure 2 (receiving, transmitting, etc.).

[0235] On each 20MHz channel occupied by a PPDU containing a MU-RTS Trigger frame, the sender of the MU-RTS Trigger frame may request at least one STA occupying the 20MHz channel to send a CTS frame response. The sender of the MU-RTS Trigger frame does not need to request a CTS frame response from an STA on a 20MHz channel not occupied by a PPDU containing a MU-RTS Trigger frame. After sending a MU-RTS Trigger frame, the AP may wait for a CTSTimeout interval of aSIFSTime + aSlotTime + aRxPHYStartDelay, which begins when the MAC receives the PHY-TXEND.confirm primitive of the transmitted MU-RTS Trigger frame. If the MAC does not receive the PHY-RXSTART.indication primitive during the CTSTimeout interval, the AP determines that the transmission of the MU-RTS Trigger frame has failed, and if the MU-RTS Trigger frame initiated TXOP, the AP may initiate the backoff procedure. If the MAC receives a PHY-RXSTART.indication primitive during the CTSTimeout interval, the MAC may wait for the corresponding PHY-RXEND.indication primitive to determine whether the MU-RTS Trigger frame transmission was successful. If a CTS frame is received from the STA addressed by the MU-RTS Trigger frame before the PHY-RXEND.indication primitive, the transmission of the MU-RTS Trigger frame may be interpreted as successful, and the continuation of the frame exchange sequence may be permitted. If any other type of frame is received, the transmission of the MU-RTS Trigger frame may be interpreted as a failure.In this case, the AP processes the received frame and, if the MU-RTS Trigger frame initiates a TXOP, may initiate the backoff procedure with the PHY-RXEND.indication primitive. If the AP sends a MU-RTS Trigger frame with an already initiated TXOP and the transmission of the MU-RTS Trigger frame fails, the AP may perform PIFS recovery or the backoff procedure.

[0236] If the STA receives a MU-RTS Trigger frame, the STA may begin sending a CTS frame response at the SIFS time boundary after the end of the received PPDU, provided that all of the following conditions are met: — The MU-RTS Trigger frame has one of the User Info fields addressed to the STA. The User Info field is addressed to the STA if the AID12 subfield is equal to the 12th LSB of the STA's AID, and the MU-RTS Trigger frame is sent by the AP to which the STA is associated, or if the STA is associated with the AP corresponding to a nontransmitted BSSID and the TA field indicates support for receiving Control frames set to a transmitted BSSID by setting the Rx Control Frame To MultiBSS subfield of the HE Capabilities element sent by the STA to 1. — The UL MU CS condition indicates that medium is in an idle state. Otherwise, the STA does not need to send a CTS frame response.

[0237] ED-based CCA and virtual CS functions may be used to determine the medium state if CS is required before responding to an received Trigger frame. UL MU CS condition may also determine the medium state using ED-based CCA and virtual CS functions. Responding regardless of the busy / idle state of the medium may mean that the STA can respond without needing to check for a medium indication from the physical CS and virtual CS (i.e., basic NAV and intra-BSS NAV). The STA does not need to consider the intra-BSS NAV when deciding whether to respond to a Trigger frame sent by the AP to which the STA is associated. The STA may consider the basic NAV when deciding whether to respond to a Trigger frame sent by the AP to which the STA is associated. The STA may consider the NAV when deciding whether to respond to a Trigger frame sent by an AP to which the STA is not associated via the UORA (UL OFDMA-based Radom Access) procedure, unless the NAV is set by a frame originating from the AP that sent the Trigger frame. When an STA decides whether to respond to a Trigger frame sent by another AP that contains an unassociated STA's RU allocation, it may consider the intra-BSS NAV associated with the AP. For an STA requested to transmit by a Trigger frame, if the STA does not consider the NAV, the virtual CS may indicate idle. For an STA requested to transmit by a Trigger frame, if the NAV counters for all NAVs considered by the STA are 0, the virtual CS may indicate idle. Otherwise, the virtual CS may indicate busy.If the CS Required subfield of the Trigger frame is 1, the STA may consider the state of the CCA (using energy detect and virtual carrier sense) during the SIFS between the Trigger frame and the PPDU sent in response to the Trigger frame. In this case, after receiving the PPDU containing the Trigger frame (i.e., during the SIFS), the STA may sense the medium using energy detect and perform energy detect on at least the subchannel containing the STA's UL allocation. The sensed subchannel may consist of one or more 20 MHz channels. The STA may transmit the requested PPDU if the 20 MHz channels containing the RU allocated in the Trigger frame are considered idle. The STA does not have to transmit if it detects that all 20 MHz channels containing the allocated RUs are not idle. If the Trigger frame is a MU-RTS Trigger frame, the requested PPDU may be a non-HT PPDU or a non-TH duplicate PPDU. Otherwise, the requested PPDU may be a TB PPDU. The CS Required subfield for the MU-RTS Trigger frame may be set to 1.

[0238] For example, if an STA receives a MU-RTS Trigger frame, it may send a CTS frame response if several conditions are met. If none of the conditions are met, the STA does not have to send a CTS frame response.

[0239] The RU Allocation subfield in the User Info field addressed to the STA may indicate whether the CTS frame response is transmitted on the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, 160MHz channel, or 80+80MHz channel. A combination of virtual CS and ED-based CCA in the SIFS after the PPDU containing the MU-RTS Trigger frame may be used to determine the Medium state. The CTS frame transmitted in response to the MU-RTS Trigger frame may be transmitted as a non-HT PPDU or a non-HT duplicate PPDU at a rate of 6Mb / s, with the TXVECTOR parameter SCRAMBLER_INITIAL_VALUE set to the same value as the RXVECTOR parameter SCRAMBLER_INITIAL_VALUE of the PPDU transmitting the MU-RTS Trigger frame. The PPDU transmitting the CTS frame may be transmitted on the 20MHz channel(s) indicated in the RU Allocation subfield of the User Info field of the MU-RTS Trigger frame. The bandwidth signaling TA may not be used in the MU-RTS Trigger frame or in the CTS frame response to the MU-RTS Trigger frame. The TXVECTOR parameter CH_BANDWIDTH_IN_NON_HT may not be present when transmitting the MU-RTS Trigger frame or the CTS frame response to the MU-RTS Trigger frame. The Power Management subfield and More Data subfield of the CTS frame transmitted as a response to the MU-RTS Trigger frame may be set to 0.

[0240] CTS may be transmitted in PPDU format. For example, CTS may be transmitted in non-HT PPDU format. For example, CTS may be transmitted in non-HT duplicate PPDU format. CTS may be transmitted in a format other than the aforementioned PPDU formats.

[0241] Figure 19 shows an example of the exchange of a MU-RTS trigger frame and a simultaneous CTS frame response in a 40MHz channel according to one aspect of this embodiment. 1901 may be the operation of the AP (transmit, receive, etc.). 1902 may be the operation of STA#1 (transmit, receive, etc.). 1903 may be the operation of STA#2 (transmit, receive, etc.). 1904 may be a 40MHz channel. AP, STA#1, and STA#2 may operate on the same channel (1904). 1901, 1902, and 1903 may operate on the same channel (1904). 1905 may be a primary 20MHz channel. 1905 may be a channel common to 1901, 1902, and 1903. 1906 may be a MU-RTS trigger frame transmitted to STA#1 and STA#2. 1906 may be a MU-RTS trigger frame transmitted on the primary 40MHz channel with a 40MHz non-HT duplicate PPDU. 1906 may indicate to STA#1 a CTS transmission on the primary 20MHz channel and to STA#2 a CTS transmission on the primary 40MHz channel. 1906 may request STA#1 to transmit a CTS frame on the primary 20MHz channel with a non-HT PPDU and request STA2 to transmit a CTS frame on the primary 40MHz channel with a 40MHz non-HT duplicate PPDU. 1907 may be a CTS transmission from STA#1 to AP. 1907 may be a CTS transmitted on the primary 20MHz channel (1905). 1907 may be a CTS to AP transmitted with a non-HT PPDU as indicated by MU-RTS. 1908 may be a CTS transmission from STA#2 to AP. 1908 may also be a CTS transmitted on the primary 40MHz channel (1904).1908 may be a CTS to an AP transmitted at 40 MHz non-HT duplicate PPDU, as shown in MU-RTS. For example, 1901 may be the operation of 202 in Figure 2 (receive, transmit, etc.). For example, 1902 may be the operation of 203 in Figure 2 (receive, transmit, etc.). For example, 1903 may be the operation of 204 in Figure 2 (receive, transmit, etc.).

[0242] STA and / or AP may transmit CTS on the NPCA primary channel (NPCA primary 20MHz channel). CTS may be transmitted on the NPCA primary channel (NPCA primary 20MHz channel). STA and / or AP may transmit CTS on the NPCA primary 40MHz channel. CTS may be transmitted on the NPCA primary 40MHz channel. STA and / or AP may transmit CTS on the NPCA primary 80MHz channel. CTS may be transmitted on the NPCA primary 80MHz channel. STA and / or AP may transmit CTS on the NPCA primary channel (NPCA primary 20MHz channel), NPCA primary 40MHz channel, or NPCA primary 80MHz channel. CTS may be transmitted on the NPCA primary channel (NPCA primary 20MHz channel), NPCA primary 40MHz channel, or NPCA primary 80MHz channel. The RU Allocation subfield in the User Info field addressed to the STA may indicate whether the CTS frame is transmitted on the NPCA primary channel, the NPCA primary 40MHz channel, or the NPCA primary 80MHz channel.

[0243] STA and / or AP may transmit CTS on the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, 320MHz channel, NPCA primary channel, NPCA primary 40MHz channel, or NPCA primary 80MHz channel. CTS may be transmitted on the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, 320MHz channel, NPCA primary channel, NPCA primary 40MHz channel, or NPCA primary 80MHz channel. The RU Allocation subfield in the User Info field addressed to the STA may indicate whether the CTS frame is transmitted on the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, 320MHz channel, NPCA primary channel, NPCA primary 40MHz channel, or NPCA primary 80MHz channel.

[0244] AP may set or determine the value of the RU Allocation subfield of the Trigger frame in the frame processing unit AU7. AP may set or determine the value of the RU Allocation subfield of the Trigger frame in the MAC layer processing unit AU4. AP may transmit the Trigger frame in the radio transmitter / receiver AU6. AP may transmit a PPDU containing the Trigger frame in the radio transmitter / receiver AU6. AP may transmit a PPDU containing the Trigger frame containing the RU Allocation subfield in the radio transmitter / receiver AU6. AP may receive a CTS in the radio transmitter / receiver AU6. AP may receive a PPDU containing a CTS in the radio transmitter / receiver AU6. AP may receive a CTS on the channel indicated by the RU Allocation of the Trigger frame in the radio transmitter / receiver AU6. AP may receive a PPDU containing a CTS on the channel indicated by the RU Allocation of the Trigger frame in the radio transmitter / receiver AU6. STA may receive a Trigger frame in the radio transmitter / receiver SU6. STA may receive a PPDU containing the Trigger frame in the radio transmitter / receiver SU6. The STA may receive a PPDU containing a Trigger frame containing a RU Allocation subfield in the wireless transmit / receive unit SU6. The STA may determine the RU Allocation subfield of the Trigger frame in the frame processing unit SU7. The STA may determine the RU Allocation subfield of the Trigger frame in the MAC layer processing unit SU4. The STA may determine the channel to transmit the CTS from the RU Allocation subfield of the Trigger frame in the frame processing unit SU7. The STA may determine the channel to transmit the CTS from the RU Allocation subfield of the Trigger frame in the MAC layer processing unit SU4. The STA may transmit a CTS in the wireless transmit / receive unit SU6. The STA may transmit a PPDU containing a CTS in the wireless transmit / receive unit SU6.The STA may transmit a CTS on the channel indicated by the RU Allocation in the Trigger frame using the wireless transmitter / receiver SU6. The STA may also transmit a PPDU containing a CTS on the channel indicated by the RU Allocation in the Trigger frame using the wireless transmitter / receiver SU6.

[0245] The channel may be a primary 20MHz channel, a primary 40MHz channel, a primary 80MHz channel, a primary 160MHz channel, an 80+80MHz channel, a 320MHz channel, an NPCA primary channel, an NPCA primary 40MHz channel, or an NPCA primary 80MHz channel. The channel may be referred to as a primary 20MHz channel, a primary 40MHz channel, a primary 80MHz channel, a primary 160MHz channel, an 80+80MHz channel, a 320MHz channel, an NPCA primary channel, an NPCA primary 40MHz channel, or an NPCA primary 80MHz channel. The channel may be any of the primary 20MHz channel, a primary 40MHz channel, a primary 80MHz channel, a primary 160MHz channel, an 80+80MHz channel, a 320MHz channel, an NPCA primary channel, an NPCA primary 40MHz channel, or an NPCA primary 80MHz channel. The term "channel" may refer to any one of the following: primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, 320MHz channel, NPCA primary channel, NPCA primary 40MHz channel, or NPCA primary 80MHz channel.

[0246] The phrase “indicates whether transmission is transmitted on the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, 320MHz channel, NPCA primary channel, NPCA primary 40MHz channel, or NPCA primary 80MHz channel” could also mean “indicates one channel from among the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, 320MHz channel, NPCA primary channel, NPCA primary 40MHz channel, or NPCA primary 80MHz channel.” In other words, an AP may indicate only one type of channel for a single STA in the RU allocation subfield of the MU-RTS. For example, an AP may be a MU-RTS containing multiple User Info fields, where the primary 20MHz channel is indicated in the RU allocation subfield for STA#1 and the primary 40MHz channel is indicated in the RU allocation subfield for STA#2.

[0247] The B0 subfield of the RU Allocation may be set to 0 to indicate the NPCA primary channel, NPCA primary 40MHz channel, or NPCA primary 80MHz channel. The B0 subfield of the RU Allocation may be set to 1 to indicate the NPCA primary channel, NPCA primary 40MHz channel, or NPCA primary 80MHz channel. The B0 subfield of the RU Allocation may be set to 0 to indicate the NPCA primary 20MHz channel, NPCA primary 40MHz channel, or NPCA primary 80MHz channel. The B0 subfield of the RU Allocation may be set to 1 to indicate the NPCA primary 20MHz channel, NPCA primary 40MHz channel, or NPCA primary 80MHz channel. The PS160 subfield of the User Info field may be set to 0 to indicate the NPCA primary 20MHz channel, NPCA primary 40MHz channel, or NPCA primary 80MHz channel. The PS160 subfield in the User Info field may be set to 1 to indicate the NPCA primary MHz channel, NPCA primary 40MHz channel, and NPCA primary 80MHz channel.

[0248] B7-B1 of the RU Allocation subfield may be set to indicate the NPCA primary channel as follows: - If the NPCA primary channel is the only 20MHz channel, or the lowest frequency 20MHz channel in the NPCA primary 40MHz channel or NPCA primary 80MHz channel, 61. - If the NPCA primary channel is the second lowest frequency in the NPCA primary 40MHz channel or NPCA primary 80MHz channel, 62. - If the NPCA primary channel is the third lowest frequency in the NPCA primary 80MHz channel, 63. - If the NPCA primary channel is the fourth lowest frequency in the NPCA primary 80MHz channel, 64.

[0249] The B7-B1 (B7 to B1) of the RU Allocation subfield may be set to indicate the NPCA primary 40MHz channel as follows: - If the NPCA primary 40MHz channel is the only 40MHz channel, or the lowest frequency 40MHz channel in the NPCA primary 80MHz channel, 65. - If the NPCA primary 40MHz channel is the second lowest frequency in the NPCA primary 80MHz channel, 66.

[0250] B7-B1 of the RU Allocation subfield may be set to 67 to indicate the NPCA primary 80MHz channel. B7-B1 of the RU Allocation subfield may be set to 68 to indicate the NPCA primary and NPCA secondary 80MHz channels (NPCA primary 80MHz channel and NPCA secondary 80MHz channel).

[0251] B7-B1 (B7 to B1) of the RU Allocation subfield may be set to indicate the primary 20MHz channel or NPCA primary channel as follows: - If the primary 20MHz channel is the only 20MHz channel, or the lowest frequency 20MHz channel in the primary 40MHz channel or primary 80MHz channel, or if the NPCA primary channel is the only 20MHz channel, or the lowest frequency 20MHz channel in the NPCA primary 40MHz channel or NPCA primary 80MHz channel,61. - If the primary 20MHz channel is the second lowest frequency in the primary 40MHz channel or primary 80MHz channel, or if the NPCA primary channel is the second lowest frequency in the NPCA primary 40MHz channel or NPCA primary 80MHz channel,62. - If the primary 20MHz channel is the third lowest frequency in the primary 80MHz channel, or if the NPCA primary channel is the third lowest frequency in the NPCA primary 80MHz channel, 63. - If the primary 20MHz channel is the fourth lowest frequency in the primary 80MHz channel, or if the NPCA primary channel is the fourth lowest frequency in the NPCA primary 80MHz channel, 64.

[0252] B7-B1 of the RU Allocation subfield may be set to indicate the NPCA primary 40MHz channel as follows: - If the primary 40MHz channel is the only 40MHz channel or the lowest frequency 40MHz channel in the primary 80MHz channel, or if the NPCA primary 40MHz channel is the only 40MHz channel or the lowest frequency 40MHz channel in the NPCA primary 80MHz channel,65. - If the primary 40MHz channel is the second lowest frequency in the primary 80MHz channel, or if the NPCA primary 40MHz channel is the second lowest frequency in the NPCA primary 80MHz channel,66.

[0253] B7-B1 of the RU Allocation subfield may be set to 67 to indicate a primary 80MHz channel or an NPCA primary 80MHz channel. B7-B1 of the RU Allocation subfield may be set to 68 to indicate primary and secondary 80MHz channels (primary 80MHz channel and secondary 80MHz channel), or NPCA primary and NPCA secondary 80MHz channels (NPCA primary 80MHz channel and NPCA secondary 80MHz channel).

[0254] B7-B1 (B7 to B1) of the RU Allocation subfield may be set to indicate the NPCA primary channel as follows: - A predetermined value if the NPCA primary channel is the only 20MHz channel, or the lowest frequency 20MHz channel in the NPCA primary 40MHz channel or NPCA primary 80MHz channel. - A predetermined value if the NPCA primary channel is the second lowest frequency in the NPCA primary 40MHz channel or NPCA primary 80MHz channel. - A predetermined value if the NPCA primary channel is the third lowest frequency in the NPCA primary 80MHz channel. - A predetermined value if the NPCA primary channel is the fourth lowest frequency in the NPCA primary 80MHz channel.

[0255] B7-B1 of the RU Allocation subfield may be set to indicate the NPCA primary 40MHz channel as follows: - A predetermined value if the NPCA primary 40MHz channel is the only 40MHz channel or the lowest frequency 40MHz channel in the primary 80MHz channel. - A predetermined value if the NPCA primary 40MHz channel is the second lowest frequency in the NPCA primary 80MHz channel.

[0256] B7-B1 of the RU Allocation subfield may be set to a predetermined value to indicate the NPCA primary 80MHz channel. B7-B1 of the RU Allocation subfield may be set to a predetermined value to indicate the NPCA primary and NPCA secondary 80MHz channels (NPCA primary 80MHz channel and NPCA secondary 80MHz channel).

[0257] When an AP requests the STA to transmit a CTS in response to MU-RTS, it may indicate a predetermined value in the RU allocation subfield of MU-RTS to request the STA to transmit the CTS on the NPCA primary channel. If the STA receives a predetermined value in the RU allocation subfield of MU-RTS transmitted from the AP, it may transmit the CTS on the NPCA primary channel. If the NPCA primary channel is the only 20MHz channel, a predetermined value (e.g., 61, or another value) may be set in the RU allocation subfield. The only 20MHz channel may also be the NPCA operating channel width of 20MHz. The only 20MHz channel may also be the MU-RTS channel width of 20MHz. If the NPCA primary channel is the lowest frequency 20MHz channel among the NPCA primary 40MHz channels, a predetermined value (e.g., 61, or another value) may be set in the RU allocation subfield. If the NPCA primary channel is the lowest frequency 20MHz channel among the NPCA primary 80MHz channels, a predetermined value (e.g., 61, or another value) may be set in the RU allocation subfield. If the NPCA primary channel is the lowest frequency 20MHz channel among the NPCA operating channels, a predetermined value (e.g., 61, or another value) may be set in the RU allocation subfield. If the NPCA primary channel is the second lowest frequency 20MHz channel among the NPCA primary 40MHz channels, a predetermined value (e.g., 62, or another value) may be set in the RU allocation subfield.If the NPCA primary channel is the second lowest frequency 20MHz channel among the NPCA primary 80MHz channels, a predetermined value (e.g., 62, or another value) may be set in the RU allocation subfield. If the NPCA primary channel is the second lowest frequency 20MHz channel among the NPCA operating channels, a predetermined value (e.g., 62, or another value) may be set in the RU allocation subfield. If the NPCA primary channel is the third lowest frequency 20MHz channel among the NPCA primary 80MHz channels, a predetermined value (e.g., 63, or another value) may be set in the RU allocation subfield. If the NPCA primary channel is the third lowest frequency 20MHz channel among the NPCA operating channels, a predetermined value (e.g., 63, or another value) may be set in the RU allocation subfield. If the NPCA primary channel is the fourth lowest frequency 20MHz channel among the NPCA primary 80MHz channels, a predetermined value (e.g., 64, or another value) may be set in the RU allocation subfield. If the NPCA primary channel is the 20MHz channel, which is the fourth lowest frequency among the NPCA operating channels, a predetermined value (e.g., 64, or another value) may be set in the RU allocation subfield. The predetermined value may be an integer greater than or equal to 1. The predetermined value may be the same value used to indicate the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, or 320MHz channel.The specified value may be different from the value used to indicate the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, or 320MHz channel.

[0258] When an AP requests the STA to transmit a CTS in response to MU-RTS, it may indicate a predetermined value in the RU allocation subfield of MU-RTS to request the STA to transmit a CTS on the NPCA primary 40MHz channel. If the STA receives a predetermined value in the RU allocation subfield of MU-RTS transmitted from the AP, it may transmit a CTS on the NPCA primary 40MHz channel. If the NPCA primary 40MHz channel is the only 40MHz channel, a predetermined value (e.g., 65, or another value) may be set in the RU allocation subfield. The only 40MHz channel may also be the NPCA operating channel width of 20MHz. The only 40MHz channel may also be the MU-RTS channel width of 40MHz. If the NPCA primary 40MHz channel is the lowest frequency 40MHz channel in the NPCA primary 80MHz channel, a predetermined value (e.g., 65, or another value) may be set in the RU allocation subfield. If the NPCA primary 40MHz channel is the lowest frequency 40MHz channel among the NPCA operating channels, a predetermined value (e.g., 65, or another value) may be set in the RU allocation subfield. If the NPCA primary 40MHz channel is the second lowest frequency 40MHz channel among the NPCA primary 80MHz channels, a predetermined value (e.g., 66, or another value) may be set in the RU allocation subfield.If the NPCA primary 40MHz channel is the second lowest frequency 40MHz channel in the NPCA operating channels, a predetermined value (e.g., 66, or another value) may be set in the RU allocation subfield. The predetermined value may be an integer greater than or equal to 1. The predetermined value may be the same value used to indicate the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, or 320MHz channel. The predetermined value may also be different from the value used to indicate the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, or 320MHz channel.

[0259] When an AP requests the STA to transmit a CTS in response to MU-RTS, it may indicate a predetermined value (e.g., 67, or another value) in the RU allocation subfield of MU-RTS to request the STA to transmit a CTS on the NPCA primary 80MHz channel. If the STA receives a predetermined value (e.g., 67, or another value) in the RU allocation subfield of MU-RTS transmitted from the AP, it may transmit a CTS on the NPCA primary 80MHz channel. The predetermined value may be an integer greater than or equal to 1. The predetermined value may be the same value used to indicate the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, or 320MHz channel. The predetermined value may be different from the value used to indicate the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, or 320MHz channel.

[0260] When an AP requests the STA to transmit a CTS in response to MU-RTS, it may indicate a predetermined value (e.g., 68, or another value) in the RU allocation subfield of MU-RTS to request the STA to transmit a CTS on a 160MHz channel that includes the NPCA primary channel but does not include the primary channel. If the RU allocation subfield of the MU-RTS transmitted by the AP indicates a predetermined value (e.g., 68, or another value), the STA may transmit a CTS on a 160MHz channel that includes the NPCA primary channel but does not include the primary channel. The predetermined value may be an integer greater than or equal to 1. The predetermined value may be the same value used to indicate the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, or 320MHz channel. The specified value may be different from the value used to indicate the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, or 320MHz channel.

[0261] In the MU-RTS RU Allocation subfield, the predetermined value for indicating the NPCA primary channel may be the same value as the predetermined value for indicating the primary 20MHz channel (e.g., 61, 62, 62, or 64). In the MU-RTS RU Allocation subfield, the predetermined value for indicating the NPCA primary channel may be a different value from the predetermined value for indicating the primary 20MHz channel. In the MU-RTS RU Allocation subfield, the predetermined value for indicating the NPCA primary 40MHz channel may be the same value as the predetermined value for indicating the primary 40MHz channel (e.g., 65, or 66). In the MU-RTS RU Allocation subfield, the predetermined value for indicating the NPCA primary 40MHz channel may be a different value from the predetermined value for indicating the primary 40MHz channel. In the RU Allocation subfield of MU-RTS, the predetermined value for indicating an 80MHz channel in NPCA may be the same value as the predetermined value for indicating a primary 80MHz channel (e.g., 67). In the RU Allocation subfield of MU-RTS, the predetermined value for indicating an 80MHz channel in NPCA may be a different value from the predetermined value for indicating a primary 80MHz channel.

[0262] A primitive containing a parameter indicating that NPCA should be performed may be issued. A primitive containing a parameter indicating that NPCA should be performed may be issued in MAC or PHY. For example, primitives containing a parameter indicating that NPCA should be performed may be PHY-CONFIG.request primitive, PHY-CONFIG.confirm primitive, etc. The parameter indicating that NPCA should be performed may be called NPCA_flag. If NPCA_flag does not exist, a primitive containing NPCA_flag may not be issued. If NPCA_flag exists, a primitive containing NPCA_flag may be issued.

[0263] B7-B1 of the RU Allocation subfield may be set to indicate the primary 20MHz channel or NPCA primary channel as follows: - If the primary 20MHz channel is the only 20MHz channel, or the lowest frequency 20MHz channel in the primary 40MHz channel or primary 80MHz channel and does not have an NPCA_flag, or if the NPCA primary channel is the only 20MHz channel, or the lowest frequency 20MHz channel in the NPCA primary 40MHz channel or NPCA primary 80MHz channel and does have an NPCA_flag,61. - If the primary 20MHz channel is the second lowest frequency in the primary 40MHz channel or primary 80MHz channel and does not have an NPCA_flag, or if the NPCA primary channel is the second lowest frequency in the NPCA primary 40MHz channel or NPCA primary 80MHz channel and does have an NPCA_flag,62. - If the primary 20MHz channel is the third lowest frequency in the primary 80MHz channel and NPCA_flag does not exist, or if the NPCA primary channel is the third lowest frequency in the NPCA primary 80MHz channel and NPCA_flag exists, 63. - If the primary 20MHz channel is the fourth lowest frequency in the primary 80MHz channel and NPCA_flag does not exist, or if the NPCA primary channel is the fourth lowest frequency in the NPCA primary 80MHz channel and NPCA_flag exists, 64.

[0264] B7-B1 of the RU Allocation subfield may be set to indicate the NPCA primary 40MHz channel as follows: - If the primary 40MHz channel is the only 40MHz channel, or the lowest frequency 40MHz channel in the primary 80MHz channel and does not have an NPCA_flag, or if the NPCA primary 40MHz channel is the only 40MHz channel, or the lowest frequency 40MHz channel in the primary 80MHz channel and does have an NPCA_flag,65. - If the primary 40MHz channel is the second lowest frequency in the primary 80MHz channel and does not have an NPCA_flag, or if the NPCA primary 40MHz channel is the second lowest frequency in the primary 80MHz channel and does have an NPCA_flag,66.

[0265] B7-B1 of the RU Allocation subfield may be set to 67 to indicate the primary 80MHz channel if NPCA_flag does not exist, or the NPCA primary 80MHz channel if NPCA_flag exists. B7-B1 of the RU Allocation subfield may be set to 68 to indicate the primary 80MHz channel and the secondary 80MHz channel if NPCA_flag does not exist, or to indicate the 160MHz channel if NPCA_flag exists.

[0266] When an AP performs carrier sensing on the NPCA primary channel and transmits MU-RTS, it may indicate that it is transmitting MU-RTS via the NPCA primary channel. The MU-RTS Trigger frame may have a field indicating that it is performing carrier sensing on the NPCA primary channel and transmitting a MU-RTS Trigger frame. For example, the Common Info field of the MU-RTS Trigger frame may have a field indicating that it is performing carrier sensing on the NPCA primary channel and transmitting a MU-RTS Trigger frame. When an AP performs carrier sensing on the NPCA primary channel and transmits MU-RTS on one or more channels, including the NPCA primary channel, it may indicate that it is transmitting MU-RTS via the NPCA primary channel. When an AP transmits MU-RTS when a PHY-CONFIG.request primary containing information about NPCA has been issued, it may indicate that it is transmitting MU-RTS via the NPCA primary channel. "Transmitting MU-RTS via the NPCA primary channel" may be synonymous with "Performing carrier sensing on the NPCA primary channel and transmitting a MU-RTS Trigger frame." "Transmitting MU-RTS via the primary channel" may be synonymous with "Performing carrier sensing on the primary channel and transmitting a MU-RTS trigger frame." For example, if the STA receives MU-RTS and indicates that the MU-RTS was transmitted via the NPCA primary channel, the RU Allocation subfield may be determined to be based on the NPCA primary channel.For example, if an STA receives a MU-RTS and it does not indicate that the MU-RTS was transmitted via the NPCA primary channel, the RU Allocation subfield may be determined to indicate the primary channel. For example, if an AP transmits a MU-RTS via the NPCA primary channel and requests the STA to transmit a CTS on a channel that includes the NPCA primary channel, the MU-RTS may include information about the NPCA. For example, the information about the NPCA may indicate that the MU-RTS was transmitted after carrier sensing on the NPCA primary channel. That is, it may include the NPCA primary channel but not the primary channel. If an STA receives a MU-RTS and it includes information about the NPCA, it may determine that it was transmitted via the NPCA primary channel and transmit a CTS on a channel that includes the NPCA primary channel indicated in the RU Allocation subfield. If an STA receives a MU-RTS and it does not include information about the NPCA, it may determine that it was transmitted via the primary channel and transmit a CTS on a channel that includes the primary channel indicated in the RU Allocation subfield. When an AP transmits MU-RTS after carrier sensing on the primary channel, information regarding NPCA does not need to be indicated. For example, information regarding NPCA may be called NPCA indicate. NPCA indicate may be a field included in MU-RTS. For example, if NPCA indicate is present, the NPCA indicate field may indicate that MU-RTS is being transmitted over the NPCA primary channel. For example, if NPCA indicate is not present, the NPCA indicate field may indicate that MU-RTS is not being transmitted over the NPCA primary channel.For example, the NPCA indicate field may be defined as 1 bit, and if the NPCA indicate field shows 0, it may indicate that the MU-RTS is not transmitting via the NPCA primary channel, and if the NPCA indicate field shows 1, it may indicate that the MU-RTS is transmitting via the NPCA primary channel. For example, if the NPCA indicate field does not exist, it may mean that the MU-RTS does not have an NPCA indicate field.

[0267] B7-B1 of the RU Allocation subfield (B7 to B1) may be set to indicate the primary 20MHz channel or NPCA primary channel as follows: - If the primary 20MHz channel is the only 20MHz channel, or the lowest frequency 20MHz channel in the primary 40MHz channel or primary 80MHz channel and no NPCA indicate exists, or if the NPCA primary channel is the only 20MHz channel, or the lowest frequency 20MHz channel in the NPCA primary 40MHz channel or NPCA primary 80MHz channel and an NPCA indicate exists,61. - If the primary 20MHz channel is the second lowest frequency in the primary 40MHz channel or primary 80MHz channel and no NPCA indicate exists, or if the NPCA primary channel is the second lowest frequency in the NPCA primary 40MHz channel or NPCA primary 80MHz channel and an NPCA indicate exists,62. ― If the primary 20MHz channel is the third lowest frequency in the primary 80MHz channel and there is no NPCA indicate, or if the NPCA primary channel is the third lowest frequency in the NPCA primary 80MHz channel and there is an NPCA indicate, 63.― If the primary 20MHz channel is the fourth lowest frequency in the primary 80MHz channel and there is no NPCA indicate, or if the NPCA primary channel is the fourth lowest frequency in the NPCA primary 80MHz channel and there is an NPCA indicate, 64.

[0268] B7-B1 of the RU Allocation subfield may be set to indicate the NPCA primary 40MHz channel as follows: - If the primary 40MHz channel is the only 40MHz channel, or the lowest frequency 40MHz channel in the primary 80MHz channel and no NPCA indicate exists, or if the NPCA primary 40MHz channel is the only 40MHz channel, or the lowest frequency 40MHz channel in the primary 80MHz channel and an NPCA indicate exists,65. - If the primary 40MHz channel is the second lowest frequency in the primary 80MHz channel and no NPCA indicate exists, or if the NPCA primary 40MHz channel is the second lowest frequency in the NPCA primary 80MHz channel and an NPCA indicate exists,66.

[0269] B7-B1 of the RU Allocation subfield may be set to 67 to indicate the primary 80MHz channel when no NPCA indicator is present, or the NPCA primary 80MHz channel when an NPCA indicator is present. B7-B1 of the RU Allocation subfield may be set to 68 to indicate the primary 80MHz channel and the secondary 80MHz channel when no NPCA indicator is present, or to indicate the 160MHz channel when an NPCA indicator is present.

[0270] There may be a set of candidate channels for which a CTS is transmitted in response to MU-RTS. This set of candidate channels for which a CTS is transmitted in response to MU-RTS may consist of one or more types of channels. The channel indicated in the RU Allocation subfield of MU-RTS may be one of the channels in the set of candidates. The set of candidate channels for which a CTS is transmitted may consist of a primary 20MHz channel and / or a primary 40MHz channel and / or a primary 80MHz channel and / or a primary 160MHz channel and / or an 80+80MHz channel and / or a 320MHz channel and / or an NPCA primary channel and / or an NPCA primary 40MHz channel and / or an NPCA primary 80MHz channel. For example, the set of candidate channels for which a CTS is transmitted may consist of a primary 20MHz channel, a primary 40MHz channel, a primary 80MHz channel, a primary 160MHz channel, an 80+80MHz channel, and a 320MHz channel. For example, the candidate set of channels on which CTS is transmitted may consist of an NPCA primary channel, an NPCA primary 40MHz channel, an NPCA primary 80MHz channel, and a 160MHz channel. For example, the candidate set of channels on which CTS is transmitted may consist of a primary 20MHz channel, a primary 40MHz channel, a primary 80MHz channel, a primary 160MHz channel, an 80+80MHz channel, a 320MHz channel, and an NPCA primary channel.For example, the set of candidate channels on which the CTS is transmitted may consist of a primary 20MHz channel, a primary 40MHz channel, a primary 80MHz channel, a primary 160MHz channel, an 80+80MHz channel, a 320MHz channel, an NPCA primary channel, an NPCA primary 40MHz channel, and an NPCA primary 80MHz channel. The AP may notify one or more STAs of one channel from the set of candidates in the RU allocation subfield of the MU-RTS. The set of candidates may change depending on the value of the Operating channel width. For example, when the Operating channel width is 40MHz, the set of candidates may consist of a primary 20MHz channel and a primary 40MHz channel. For example, when the Operating channel width is 160MHz, the set of candidates may consist of a primary 20MHz channel, a primary 40MHz channel, a primary 80MHz channel, a 160MHz channel, and an 80+80MHz channel. For example, when the operating channel width is 160MHz, the candidate set may consist of a primary 20MHz channel, a primary 40MHz channel, a primary 80MHz channel, a 160MHz channel, an 80+80MHz channel, an NPCA primary channel, and an NPCA primary 40MHz channel.For example, when the Operating channel width is 320MHz, the candidate set may consist of a primary 20MHz channel, a primary 40MHz channel, a primary 80MHz channel, a primary 160MHz channel, an 80+80MHz channel, a 320MHz channel, an NPCA primary channel, an NPCA primary 40MHz channel, and an NPCA primary 80MHz channel. The candidate set may change depending on the value of the NPCA Operating channel width. For example, when the NPCA Operating channel width is 160MHz, the candidate set may consist of an NPCA primary channel, an NPCA primary 40MHz channel, an NPCA primary 80MHz channel, and a 160MHz channel. For example, when the NPCA Operating channel width is 80MHz, the candidate set may consist of an NPCA primary channel, an NPCA primary 40MHz channel, and an 80MHz channel. The candidate sets may be configured by the Operating channel width and the NPCA Operating channel width. In NPCA, the channel to transmit CTS may be indicated from a set of candidates determined by the NPCA Operating channel width or a predefined set. Each set of candidates may be composed of the Operating channel width. The set of candidates may be predefined. The set of candidates may be determined by the Operating channel width and / or NPCA operating channel width. The operating channel width may be the operating channel width of the AP. The operating channel width may be the operating channel width of the STA.The NPCA operating channel width may be the operating channel width of the AP. The NPCA operating channel width may be the operating channel width of the STA. "Indicate whether transmission will be made on one of the following: primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, 320MHz channel, NPCA primary channel, NPCA primary 40MHz channel, or NPCA primary 80MHz channel" may mean that one channel is indicated from the set of candidates.

[0271] For example, in Figure 16, the candidate set may be primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, and 160MHz channel. For example, in Figure 17, the candidate set may be primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, and 320MHz channel.

[0272] Figure 20 shows an example of a channel for CTS transmission in NPCA according to one aspect of this embodiment. Figure 20 may also show the setting of B7-B1 of the RU Allocation subfield. 2001, 2002, 2003, 2004, 2005, 2006, 2007, and 2008 may be 20MHz channels. In Figure 20, the operating channel width may be a 160MHz channel. In Figure 20, the operating channel width of the STA and / or AP may be a 160MHz channel. 2001, 2002, 2003, 2004, 2005, 2006, 2007, and 2008 may be operating channels. 2009, 2010, 2011, and 2012 may be the bandwidth of the PPDU carrying the MU-RTS Trigger frame. 2009, 2010, 2011, and 2012 may be the bandwidth of the PPDU carrying the MU-RTS Trigger frame after carrier sensing on the primary channel. The STA and / or AP may transmit MU-RTS with the bandwidth of 2009, 2010, 2011, or 2012 after carrier sensing on the primary channel. 2009, 2010, 2011, and 2012 may be the values ​​indicated in the UL BW subfield. 2009 may be indicated as 20 MHz in the UL BW subfield. 2010 may be indicated as 40 MHz in the UL BW subfield. 2011 may be indicated as 80 MHz in the UL BW subfield. 2012 may be indicated as 160 MHz or 80+80 MHz in the UL BW subfield. 2013, 2014, 2015, 2016, 2017, 2018, 2019, and 2020 may be channels on which CTS frames are transmitted. Any of 2013, 2014, 2015, 2016, 2017, 2018, 2019, and 2020 may be indicated in the RU Allocation subfield of MU-RTS.2013, 2014, 2015, or 2016 may be the primary 20MHz channel. 2017 or 2018 may be the primary 40MHz channel. 2019 may be the primary 80MHz channel. 2020 may be 160MHz or 80+80MHz. If a predetermined value is indicated in the RU Allocation subfield, the STA may transmit the CTS using the primary 20MHz channel. If a predetermined value is indicated in the RU Allocation subfield, the STA may transmit the CTS using the primary 40MHz channel. If a predetermined value is indicated in the RU Allocation subfield, the STA may transmit the CTS using the primary 80MHz channel. If a predetermined value is indicated in the RU Allocation subfield, the STA may transmit the CTS using an operating channel width of 160MHz. In Figure 20, the NPCA operating channel width may be an 80MHz channel. In Figure 20, the NPCA operating channel width of the STA and / or AP may be an 80MHz channel. 2005, 2006, 2007, and 2008 may be the NPCA operating channel. 2021, 2022, and 2023 may be the bandwidth of the PPDU carrying the MU-RTS trigger frame after carrier sensing on the NPCA primary channel. The STA and / or AP may transmit MU-RTS on the bandwidth of 2021, 2022, or 2023 after carrier sensing on the NPCA primary channel. 2021, 2022, and 2023 may be the values ​​indicated in the UL BW subfield in the NPCA. 2021 may be the value indicated in the UL BW subfield in the NPCA as 20MHz.2022 may be 40MHz in the UL BW subfield in NPCA. 2023 may be 80MHz in the UL BW subfield in NPCA. 2024, 2025, 2026, and 2027 may be channels in NPCA on which CTS frames are transmitted. 2024 or 2025 may be the NPCA primary channel. 2026 may be the NPCA primary 40MHz channel. 2027 may be the 80MHz channel. If a predetermined value is indicated in the RU Allocation subfield, the STA may transmit CTS using the NPCA primary channel. If a predetermined value is indicated in the RU Allocation subfield, the STA may transmit CTS using the NPCA primary 40MHz channel. If a predetermined value is indicated in the RU Allocation subfield, the STA may transmit CTS using the NPCA operating channel at 80MHz. For example, AP may transmit a MU-RTS Trigger frame with a bandwidth of 2009, 2010, 2011, or 2012, and indicate to one or more STAs one of 2013, 2014, 2015, 2016, 2017, 2018, 2019, or 2020 in the RU Allocation subfield, and each STA may transmit a CTS on the indicated channel. In NPCA, AP may transmit a MU-RTS Trigger frame with a bandwidth of 2021, 2022, or 2023, and indicate to one or more STAs one of 2024, 2025, 2026, or 2027 in the RU Allocation subfield, and each STA may transmit a CTS on the indicated channel. For example, if 2001 is the primary channel, then 2013 may be the primary 20MHz channel, 2017 the primary 40MHz channel, and 2019 the primary 80MHz channel.The AP may indicate 2013 in the RU Allocation subfield of MU-RTS to request the STA to transmit CTS on the primary 20MHz channel, 2017 in the RU Allocation subfield of MU-RTS to request the STA to transmit CTS on the primary 40MHz channel, and 2019 in the RU Allocation subfield of MU-RTS to request the STA to transmit CTS on the primary 80MHz channel. For example, if 2008 is the NPCA primary channel, then 2024 may be the NPCA primary channel, 2026 may be the NPCA primary 40MHz channel, and 2027 may be the 80MHz channel. In NPCA, the AP may indicate 2024 in the RU Allocation subfield of MU-RTS to request the STA to transmit CTS on the NPCA primary channel, 2026 in the RU Allocation subfield of MU-RTS to request the STA to transmit CTS on the NPCA primary 40MHz channel, and 2027 in the RU Allocation subfield of MU-RTS to request the STA to transmit CTS on the 80MHz channel.

[0273] For example, in Figure 20, the candidate set may consist of a primary 20MHz channel, a primary 40MHz channel, a primary 80MHz channel, a 160MHz channel, an NPCA primary channel, an NPCA primary 40MHz channel, and an 80MHz channel.

[0274] Figure 21 shows an example of the process for determining the channel on which to transmit a CTS according to one aspect of this embodiment. The STA may receive a MU-RTS (S2101). The STA may indicate the channel for CTS transmission in the RU Allocation subfield of the received MU-RTS (S2102). The RU Allocation subfield may indicate a channel that includes the NPCA primary channel but does not include the primary channel. The CTS may be transmitted on a channel that includes the NPCA primary channel but does not include the primary channel. The MU-RTS may be received on a channel that includes the NPCA primary channel but does not include the primary channel. The MU-RTS may be received on a channel that includes both the NPCA primary channel and the primary channel. After receiving the MU-RTS, the STA may send a response CTS to the MU-RTS.

[0275] Figure 21 is a diagram showing an example of the process of indicating the channel on which a response CTS to MU-RTS is transmitted according to one aspect of this embodiment. The AP may set a value in the RU Allocation subfield of MU-RTS that indicates the channel on which STA transmits the CTS (S2201). The AP may transmit MU-RTS (S2202). The RU Allocation subfield may indicate a channel that includes the NPCA primary channel but does not include the primary channel. The CTS may be transmitted on a channel that includes the NPCA primary channel but does not include the primary channel. The MU-RTS may be transmitted on a channel that includes the NPCA primary channel but does not include the primary channel. The MU-RTS may be transmitted on a channel that includes both the NPCA primary channel and the primary channel. After transmitting MU-RTS, the AP may receive a response CTS to MU-RTS.

[0276] As described above, AP can indicate CTS transmission in MU-RTS on a channel that includes the NPCA primary channel but does not include the primary channel. STA can indicate CTS transmission on a channel that includes the NPCA primary channel but does not include the primary channel. In one aspect of this invention, STA and AP can perform frame exchange between MU-RTS and CTS in NPCA.

[0277] The programs that operate in the base station device and terminal device according to embodiments of the present invention may be programs that control the CPU (Central Processing Unit) and the like (programs that make the computer function) in order to realize the functions of the above embodiments according to embodiments of the present invention. The information handled by these devices is temporarily stored in RAM (Random Access Memory) during processing, and then stored in various ROMs such as Flash ROM (Read Only Memory) or HDD (Hard Disk Drive), and read, modified, and written by the CPU as needed.

[0278] Furthermore, the terminal device and some of the base station devices in the above-described embodiment may be implemented using a computer. In that case, the program for implementing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be loaded into a computer system and executed.

[0279] Furthermore, the term "computer system" as used herein refers to a computer system built into a terminal device or base station device, and includes hardware such as the operating system and peripheral devices. Also, "computer-readable recording media" refers to portable media such as flexible disks, magneto-optical disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into computer systems.

[0280] Furthermore, "computer-readable recording media" may include those that dynamically hold programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or communication lines such as telephone lines, as well as those that hold programs for a certain period of time, such as volatile memory within a computer system that acts as a server or client in such cases. In addition, the above-mentioned program may be for the purpose of realizing some of the functions described above, and may also be a program that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

[0281] The terminal device may consist of at least one processor and at least one memory containing computer program instructions (computer program). The memory and computer program instructions (computer program) may be configured to cause the terminal device to perform the operations and processing described in the above embodiment using the processor. The base station device may consist of at least one processor and at least one memory containing computer program instructions (computer program). The memory and computer program instructions (computer program) may be configured to cause the base station device to perform the operations and processing described in the above embodiment using the processor.

[0282] Furthermore, the base station equipment in the above-described embodiment can also be implemented as an assembly (device group) composed of multiple devices. Each device constituting the device group may have some or all of the functions or functional blocks of the base station equipment related to the above-described embodiment. The device group only needs to have a complete set of functions or functional blocks of the base station equipment. In addition, the terminal equipment related to the above-described embodiment can also communicate with the base station equipment as an assembly.

[0283] Furthermore, some or all of the terminal device and base station device in the above-described embodiments may be implemented as LSIs, which are typically integrated circuits, or as chipsets. Each functional block of the terminal device and base station device may be individually chipped, or some or all of them may be integrated into a single chip. In addition, the method of implementing the integrated circuit is not limited to LSIs; it may also be implemented using dedicated circuits or general-purpose processors. Moreover, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that can replace LSIs, it is also possible to use integrated circuits based on those technologies.

[0284] Furthermore, although the above-described embodiment mentions a terminal device as an example of a communication device, the present invention is not limited to this and can also be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning and washing machines, air conditioning equipment, office equipment, vending machines, and other household appliances, as well as terminal devices or communication devices.

[0285] While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like that do not depart from the gist of this invention are also included. Furthermore, various modifications are possible within the scope of the claims for one aspect of the present invention, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. In addition, configurations in which elements described in each of the above embodiments that produce similar effects are substituted for each other are also included.

[0286] One aspect of the present invention can be used, for example, in communication systems, communication equipment (e.g., mobile phone devices, base station devices, wireless LAN devices, or sensor devices), integrated circuits (e.g., communication chips), or programs.

[0287] SU1, AU1 Antenna section SU2, AU2 RF section SU3, AU3 Physical layer processing section SU4, AU4 MAC layer processing section SU5 Upper layer packet processing section SU6, AU6 Wireless transceiver section SU7, AU7 Frame processing section AU5 DSAF section

Claims

1. A terminal device comprising a receiving unit that receives a MU-RTS Trigger frame including a first field, wherein the first field indicates whether the CTS frame is transmitted on the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, 160MHz channel, 80+80MHz channel, 320MHz, or NPCA primary channel, and the first field is set to a first value to indicate the NPCA primary channel.

2. The terminal device according to claim 1, wherein the NPCA primary channel is a channel to which a user transitions from the primary channel when the primary channel is occupied by OBSS.

3. A base station device comprising a transmitting unit that transmits a MU-RTS Trigger frame including a first field, wherein the first field indicates whether the CTS frame is transmitted on the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, 160MHz channel, 80+80MHz channel, 320MHz, or NPCA primary channel, and the first field is set to a first value to indicate the NPCA primary channel.

4. The base station device according to claim 3, wherein the NPCA primary channel is a channel to which the primary channel is migrated when the primary channel is occupied by OBSS.

5. A communication method for a terminal device, comprising the step of receiving a MU-RTS Trigger frame including a first field, wherein the first field indicates whether the CTS frame is transmitted on a primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, 160MHz channel, 80+80MHz channel, 320MHz, or NPCA primary channel, and the first field is set to a first value to indicate the NPCA primary channel.

Images