Base station equipment, terminal equipment, and communication method

Abstract

Achieve efficient communication with a wireless LAN system. [Solution] The terminal device receives a MU-RTS Trigger frame including an RU allocation subfield. The RU allocation subfield indicates whether the CTS frame is transmitted on a primary 20MHz (40MHz, 80MHz) channel, a 160MHz (80+80MHz, 320MHz) channel, or an NPCA primary channel. A first value is set if the primary 20MHz or NPCA primary channel or NPCA primary channel is the lowest frequency 20MHz channel of the only 20MHz channel, NPCA primary, or 80MHz channel.

Description

Technical Field

[0001] The present invention relates to a base station device, a terminal device, and a communication method.

Background Art

[0002] The Institute of Electrical and Electronics Engineers Inc. (IEEE) is considering ways to increase the speed and frequency utilization efficiency of Wireless Local Area Network (LAN) communication. Currently, the standardization of IEEE 802.11bn has been initiated as a successor standard to IEEE 802.11be.

Prior Art Documents

Non-Patent Documents

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

Summary of the Invention

Problems to be Solved by the Invention

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

Means for Solving the Problems

[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 RU allocation subfield, wherein the RU Allocation subfield is a CTS frame It will be determined which of the following channels will be used for transmission: primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, 160MHz channel, 80+80MHz channel, 320MHz, or NPCA primary channel. A terminal device wherein the RU Allocation subfield indicates a primary 20MHz channel or an NPCA primary channel, and the RU Allocation subfield is set to a first value when the NPCA primary channel is only a 20MHz channel, or the lowest frequency 20MHz channel of an NPCA primary 40MHz channel or an NPCA primary 80MHz channel.

[0006] (2) A second aspect of the present invention is a communication method used in a terminal device, comprising the step of receiving a MU-RTS Trigger frame including an RU allocation subfield, wherein the RU Allocation subfield 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 RU Allocation subfield indicates either a primary 20MHz channel or an NPCA primary channel, and the RU Allocation subfield indicates whether the NPCA primary channel is only a 20MHz channel, or an NPCA primary 40MHz channel or an NPCA primary 80MHz channel If the channel is the lowest frequency 20MHz channel, the first value is set, including communication method. [Effects of the Invention]

[0007] This enables the realization of an efficient wireless communication system. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows an example of a wireless LAN system according to one aspect of this embodiment. [Figure 2] This figure shows an example of OBSS according to one aspect of this embodiment. [Figure 3] This diagram shows an example of the configuration of STA according to one aspect of this embodiment. [Figure 4] This diagram shows an example of the configuration of an AP according to one aspect of this embodiment. [Figure 5] This figure shows an example of a MAC frame format according to one aspect of this embodiment. [Figure 6] This figure shows an example of an A-MSDU according to one aspect of this embodiment. [Figure 7] This figure shows an example of an A-MPDU according to one aspect of this embodiment. [Figure 8] This figure shows an example of Fragmentation according to one embodiment. [Figure 9] This figure shows an example of a PPDU according to one aspect of this embodiment. [Figure 10] This figure shows an example of a backoff procedure according to one aspect of this embodiment. [Figure 11] This figure shows an example of a NAV according to one aspect of this embodiment. [Figure 12] This figure shows an example of channel bonding according to one aspect of this embodiment. [Figure 13] This figure shows an example of the backoff procedure on the NPCA primary channel of the STA according to one aspect of this embodiment. [Figure 14]A diagram showing an example of the size and arrangement of RUs by the RU Allocation subfield and the UL BW subfield according to one aspect of the present embodiment. [Figure 15] A diagram showing an example of a table defining the mapping between the RU index and RUs when the UL BW subfield according to one aspect of the present embodiment indicates 20 MHz. [Figure 16] A diagram showing an example of B7 - B1 of the UL BW subfield and the RU Allocation subfield of the MU - RTS Trigger frame according to one aspect of the present embodiment. [Figure 17] A diagram showing an example of B7 - B1 of the RU Allocation subfield of MU - RTS Trigger frames with various bandwidths according to one aspect of the present embodiment. [Figure 18] A diagram showing an example of the exchange of MU - RTS and simultaneous CTS responses according to one aspect of the present embodiment. [Figure 19] A diagram showing an example of the exchange of a MU - RTS Trigger frame and a simultaneous CTS frame response in a 40 MHz channel according to one aspect of the present embodiment. [Figure 20] A diagram showing an example of the channel for CTS transmission in NPCA according to one aspect of the present embodiment. [Figure 21] A diagram showing an example of the process for determining the channel for transmitting CTS according to one aspect of the present embodiment. [Figure 22] A diagram showing an example of the process for indicating the channel for transmitting a response CTS to MU - RTS according to one aspect of the present embodiment.

Mode for Carrying Out the Invention

[0009] Hereinafter, embodiments of the present invention will be described.

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

[0011] The wireless LAN system in this embodiment includes an access point (AP) and a station It includes (STA). A network consisting of access points and stations is called a BSS (Basic Service Set). A 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 be called a BSS.

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

[0013] Figure 1 shows an example of a wireless LAN system according to one aspect of this embodiment. The wireless LAN system comprises STA103, STA104, and AP102. It may also be called BSS.

[0014] STA may be a logical entity. This logical entity is the Medium Access Control (MAC) and physical layer interface to the wireless medium (WM: Wireless Medium). STA may be a logical entity that is a single addressable instance. It may also be a communication device that uses a wireless medium. Furthermore, STA may include AP (Access Point) having the function of a base station and / or non-AP STA having the function of a terminal. In other words, STA may be an AP. Also, STA may be a non-AP STA. Also, STA may refer to both AP and non-AP STA. STA may also be called a terminal device.

[0015] Wireless media use PDUs (Protocol Data Units) between peer physical layer entities of a Wireless LAN. It may be a medium used to implement the transfer. A wireless medium may be referred to as a medium. A medium may be referred to as a medium.

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

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

[0018] 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 also be referred to as an STA. Good. In other words, AP can also be STA.

[0019] 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 non-AP STA may be a VHT STA. This is also acceptable. Non-AP STA may also be HE STA. Non-AP STA may also be EHT STA. A non-AP STA may also be a UHR STA. A non-AP STA is an STA other than the aforementioned STA. That is also acceptable. Non-AP STA may be referred to as STA.

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

[0021] The BSS may be a set of STAs that successfully synchronized using JOIN service primitives and a set of STAs using START primitive. For example, MLME-JOIN.confirm may be used as the JOIN service primitive. MLME-JOIN.confirm confirms synchronization with the BSS. It may be a primitive for doing so. MLME-JOIN.request may be used as the JOIN service primitive. MLME-JOIN.request is a primitive for requesting synchronization with BSS. This is also acceptable. For example, MLME-START.request may be used as the START primitive. Good. MLME-START.request may be a primitive for a MAC entity to request that a new BSS be started. A primitive is an internal signal in STA or AP. This is also acceptable. The internal signals referred to here may be internal signals 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 two MLMEs and two PLMEs.

[0022] An ESS is a set of one or more interconnected BSSs, which appear as a single BSS in the Logical Link Control (LLC) layer of an STA associated with any of these BSSs. It is also possible. 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 coverage areas (areas) composed of multiple BSSs. An ESS may have multiple BSSs that are far apart, and the coverage covered by multiple BSSs may be considered as a wider coverage. It may be ranged. In other words, the communication area of ​​ESS may be the same as or wider than the communication area of ​​BSS alone. The communication area formed by ESS is called ESA (Extended Service Area). It may also be used.

[0023] 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).

[0024] Figure 2 shows an example of OBSS according to one aspect of this embodiment. In Figure 2, 202 203 may be AP#1. 203 may be STA#1. 204 may be STA#2. 201 may be BSS#1, which consists of 202, 203, and 204. 203 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, which consists of 206, 207, and 208. 207 is 206 may be synchronized with 208. 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.

[0025] 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 is a BSA that includes 203, 204, and 207. This is also acceptable. Here, 207 may be another member of the BSS.

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

[0027] The addressable unit may be a station (STA). Physical and operational Characteristics may also be defined by modifiers placed before the STA term. For example, in the case of location or mobility, the addressable unit is fixed STA. ), mobile STA, and mobility STA may also be used. STA is A While the recipient can specify a dress code, it does not (generally) have to be a fixed location. STA is multiple It may have a number of different characteristics, each of which forms its function. This is also acceptable. For example, a single addressable unit may simultaneously possess the characteristics of a portable STA, a QoS STA, a dependent STA, and a hidden STA. That's fine.

[0028] The architecture provides a WLAN that transparently supports STA migration to the upper layers. It may consist of several interacting components. 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 is the set of all possible directional transmissions by member STAs. It may also be called BSA.

[0029] 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. DS and Extended Service Sets (ESSs) may be mechanisms for extending connectivity for non-GLK operations. GLK operations use bridges. An extended network may be formed using these. The wireless medium and the DSM (Distribution System Medium) may be logically separated. Each logical medium has a different architecture. They may be used for different purposes by different components. Recognizing that multiple media are logically different is important for understanding the flexibility of the architecture. LAN The architecture is specified independently of the physical characteristics of a particular implementation. DS provides the logical services necessary for address-to-destination mapping and the seamless integration of multiple BSSs. This may enable support for mobile devices. The AP uses STA functionality and DSAF. It is an entity with a Distribution System Access Function (BSS) and may enable the associated STA to access the DS via wireless media. The data between the BSS and the DS is handled by the AP. It may travel via the internal DSAF. The AP may include an STA, and its STA address may be addressable on the radio medium. For the AP to communicate with the radio medium and DSM The addresses used do not necessarily have to be the same. Data sent from one of the STAs associated with the AP to the AP's STA address is always received on an uncontrolled port. It may be processed by the access entity. If the controlled port is authorized, the frame may conceptually pass through the DS.

[0030] DS and Infrastructure BSS enable wireless networks of any size and complexity. A network may be constructed. This network may be called an ESS (Extensible Services Set). Good. An ESS is a collection of infrastructure BSSs connected by the same SSID, which may also be connected by DSs. An ESS does not necessarily contain a DS. For the LLC layer, an ESS is an IBSS. It may look the same. STAs within ESS can communicate, and mobile STA(s) are (same Within the ESS, movement between BSSs may be transparent to the LLC. In the ESS, the BSS is partial It may overlap. This may be commonly used to position coverage within a physical range. In ESS, BSS may be physically separated. In ESS, logically There may be no restrictions on the distance between BSSs. In ESS, BSSs are physically located in the same place. 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).

[0031] Figure 3 shows an example of the device configuration of an STA according to one embodiment of this model. The STA may have 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 have a wireless transceiver unit SU6 and a frame processing unit SU7. The wireless transceiver unit SU6 connects the antenna unit SU1 and the RF The frame processing unit SU7 may be configured to include a physical layer processing unit SU3 and a MAC layer processing unit SU4. The RF unit SU2 transmits radio signals via the antenna unit SU1. Received the number.

[0032] 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 on the converted baseband signal related to the physical layer function (PHY function). The signal that has undergone processing in the physical layer processing unit SU3 is sent to the MAC layer processing unit SU4. The MAC layer processing unit SU4 performs processing on the baseband signal related to the MAC layer function (MA function). The MAC layer processing unit SU4 performs processing related to the MAC layer function. The signal, after processing at the MAC layer in the MAC layer processing unit SU4, is sent as a higher layer packet to the higher layer packet processing unit SU5. The higher layer packet processing unit SU5 performs processing related to the higher layer function on the higher layer packet extracted from the received signal.

[0033] The upper layer packet processing unit SU5, when transmitting upper layer packets, processes information related to the functions of the upper layer. Processing is performed. 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 on the upper layer packet related to the MAC layer function. The frame after processing at the MAC layer in the MAC layer processing unit SU4 (the upper layer packet has been processed) The generated frame is sent to the physical layer processing unit SU3. The physical layer processing unit SU3 performs processing related to the physical layer's functions on the frame that has undergone processing at the MAC layer. 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.

[0034] 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. Furthermore, PLME and MLME may 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.

[0035] Figure 4 shows an example of the device configuration of an AP according to one aspect of this embodiment. The AP may include 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 also have a higher layer packet processing function. Furthermore, the AP is capable of wireless transmission and reception. The unit may have a section AU6 and a frame processing section AU7. The wireless transceiver section AU6 may be configured to include an antenna section AU1 and an RF section AU2. The frame processing section AU7 may be configured to include a physical layer processing section AU3 and a MAC layer processing section AU4.

[0036] 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 processes the converted baseband signal to determine the function of the physical layer. Processing is performed. The signal that has undergone processing in the physical layer processing unit AU3 is sent to the MAC layer processing unit AU4. The MAC layer processing unit AU4 processes the baseband signal, performing operations related to the MAC layer's functions. The MAC layer processing in MAC layer processing unit AU4 is sent to DSAF unit AU5 as a higher layer packet. DSAF unit AU5 then processes the higher layer packet extracted from the received signal. It performs processing related to the functions of the higher layer. In addition, the DSAF unit AU5 provides higher layer packets to the DS. That's good too.

[0037] 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 packet is sent to the MAC layer processing unit AU4. The MAC layer processing unit AU4 performs processing related to the MAC layer's functions on the upper layer packet. The frame that has undergone MAC layer processing in the MAC layer processing unit AU4 (a frame generated by processing the upper layer packet) is sent to the physical layer processing unit AU3. The physical layer processing unit AU3 performs processing related to the physical layer's functions on the frame that has undergone processing at the MAC layer. 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 wireless signal via the antenna unit AU1.

[0038] 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 are independent of the layer. It may be controlled by the SME, which is a type. PLME, MLME, and SME are connected to the frame processing unit AU7. It may be included.

[0039] HT STA (High-Throughput STA) is measured at MAC Data Services Access Points (SAPs). The PHY and MAC may provide capabilities to support a specified throughput of 100 Mb / s or higher. The HT STA may also be a QoS STA. The HT feature may be used in an HT STA associated with an HT AP (High-Throughput AP). A subset of the HT feature may be used between two HT STAs that are members of the same IBSS. Some PHY features that distinguish HT STAs from non-HT STAs include multiple input multiple output (MIMO) operation, spatial multiplexing (SM), Spatial mapping (including transmit beamforming), spacetime block coding (STBC), low-density parity check (LDPC) coding, and antenna selection (ASEL) may be used. The permitted PPDU formats for HT STA may be non-HT format, HT-mixed format, and HT-greenfield format. In HT STA, PPDU may be transmitted with a 20 MHz bandwidth. In HT STA, PPDU may be transmitted with a 40 MHz bandwidth. 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 STA. good.

[0040] VHT STA (Very High-Throughput STA) supports the same features as HT STA, in addition to the other features supported by HT STA. The VHT STA may also support VHT functionality. The main PHY functions of the VHT STA may support 40MHz and 80MHz channel widths. The main PHY functions of the VHT STA may also support VHT single-user (SU) PPDUs. The main PHY functions of the VHT STA may also support 160MHz. Channel widths of 80+80MHz may be supported. VHT multi-user (MU)PPDUs may be supported as the main PHY function of VHT STA. The main PHY function of VHT is present in HT STA. It is not required. As a primary MAC function of VHT STA, A-MPDU padding of VHT PPDU may be supported. As a primary MAC function of VHT STA, S-MPDU may be supported. As a primary MAC function of VHT STA, bandwidth indication response may be supported. The MAC function does not need to be present in HT STA. The VHT function is VHT AP (Very High-Throughput). It may be used with VHT STA associated with AP). A subset of VHT functions is available in the same IBSS. It may be used between two VHT STAs that are members of the same group.

[0041] The operating channel width is the channel width that the STA can currently receive. It is also acceptable. The operating channel width is the channel width that STA can currently transmit. The operating channel width may also be called the BSS bandwidth. For example, the operating channel may be the channel on which beacons are transmitted.

[0042] HE (High Efficiency) STA can also be VHT STA when operating in the 5GHz band. i. A 20MHz-only HE STA does not need to support 40MHz and 80MHz channel widths. Support for a 20MHz operating channel width may be mandatory for HE STA. A 20MHz-only non-AP HE STA does not need to support 40MHz and 80MHz operating channel widths. This may be required. HE STA has operating channel widths of 160MHz and 80+80MHz. Support for this may be optional. HE STA may be HT STA. The main PHY features of HE STA that are not present in HT STA or VHT STA may be DL and UL OFDMA (Up Link Orthogonal Frequency Division Multiple Access) support. The main PHY features of HE STA that are not present in HT STA or VHT STA may be HE AP that supports four or more spatial streams when MU-MIMO (Multi User Multiple Input Multiple Output) is performed across the entire PPDU bandwidth. Support for DL ​​MU-MIMO (Down Link Multi User Multiple Input Multiple Output) It may be so. The main PHY function of HE STA that is not present in HT STA or VHT STA is non-AP HE STA It may also support DL MU-MIMO reception. The main HE STA that does not exist in HT STA or VHT STA. The MAC function may also 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 is A Support for individual TWT (Target Wake Time) in P may also be an option. The main MAC function of HE STA, which is not present in HT STA or VHT STA, may be support for two NAV operation in non-AP STA.

[0043] EHT (Extreme High Throughput) STA can operate in a bandwidth between 1 GHz and 7.250 GHz. For example, EHT STA may be HE STA at 5GHz and 6GHz. The STA may be an HE STA at 2.4 GHz. The EHT STA may use an operation element for HT and / or VHT and / or HE STA.

[0044] A UHR (Ultra High Reliability) STA may operate in a bandwidth 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 an 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 an HE STA at 2.4GHz. For example, a UHR STA may be an HT STA at 2.4GHz. A UHR STA supports Non Primary Channel Access. The UHR STA may use HT, and / or VHT, and / or HE STA, and / or operation elements for the UHR STA. In other words, the UHR STA may be controlled by an HT operation element, and / or VHT operation element, and / or HE operation element, and / or EHT operation element, and / or UHR operation element.

[0045] APs and STAs within a BSS may transmit based on CSMA / CA (Carrier Sense Multiple Access with Collision Avoidance). The CSMA / CA protocol is designed to reduce the probability of collisions at the point in time when collisions between multiple STAs accessing the medium are most likely to occur. The protocol used may also be acceptable.

[0046] HT BSS may be a BSS in which the Beacon frame transmitted by HT STA includes an HT Capabilities element. VHT BSS may be a BSS in which the Beacon frame transmitted by VHT STA includes a VHT Operation element. HE BSS may be a BSS in which the Beacon frame transmitted by HE STA includes an HE Operation element. It is also possible that the EHT BSS is a BSS in which the Beacon frame transmitted by the HE STA contains an EHT Operation element. For example, the HT BSS is a BSS that enables the HT STA to perform It may be configured with ported STAs. For example, VHT BSS may use the capability of VHT STA. It may be configured with ported STAs. For example, HE BSS supports HE capability It may be composed of STAs that support the capabilities of EHT. For example, EHT BSS supports the capabilities of EHT. It may be composed of STAs.

[0047] In this embodiment, STA may be, for example, HT STA, VHT STA, HE STA, EHT STA, or UHR STA. STA may also be any STA other than those described above.

[0048] AP and STA are frames of multiple frame types that share a common frame format. A frame may be sent. A frame may be defined at the physical layer, MAC layer, and Logical Link Control (LLC) layer, respectively.

[0049] 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) is a unit exchanged between MAC service access points (SAPs). It may also be information that is distributed in this way. MAC frames in STA are processed by the MAC layer processing unit SU4. It may also be done. MAC frames in STA may be processed by the frame processing unit SU7. The MAC frame may be processed by the MAC layer processing unit AU4. The MAC frame in AP may be processed by the frame processing unit AU7.

[0050] 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 the Physical Layer (PHY) data service. A synonym for PPDU may be PHY frame. In STA, a PHY frame is a unit of data. The PHY frame in STA may be processed by the physical layer processing unit SU4. The PHY frame in AP may be processed by the physical layer processing unit AU4. The PHY frame in AP may be processed by the frame processing unit AU7.

[0051] The MAC frame format may consist of a MAC header, a Frame body, and an FCS. The MAC frame format consists of a set of fields that occur in a fixed order in all frames. It may be configured as follows.

[0052] The MAC header consists of the Frame Control field, Duration / ID field, and Address1 field. The MAC header may consist of fields such as Address2, Address3, Sequence Control, Address4, QoS Control, HT Control, etc. The MAC header may consist of all of the aforementioned fields. The MAC header may consist of some of the aforementioned fields.

[0053] 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 this case, the MAC header may consist of a Frame Control field, a Duration field, an Address1 field, an Address2 field, an Address3 field, a Sequence Control field, an Address4 field, and a QoS Control field. The MAC frame format may be MPDU.

[0054] The MAC header's Frame Control field is a Protocol Version subfield, Type subfield. Field, Subtype subfield, To DS subfield, From DS subfield More Fragments subfield, Retry subfield, Power Management subfield The MAC header may consist of subfields such as: Frame Control, More data subfield, Protected Frame subfield, +HTC subfield, Control Frame Extension subfield, Compressed SSID Present subfield, ANO Present subfield, BSS BW subfield, Security subfield, AP PM subfield, etc. The field may consist of some of the subfields mentioned above. The Frame Control field of the MAC header may consist of all of the subfields mentioned above. The Frame Control field in the MAC header determines the frame type, depending on the subframe. It may also be composed of combinations of Lud.

[0055] The frame type may also be indicated in the Type subfield within the Frame Control field of the MAC header. The frame type may be defined as Control frame, Management frame, or Data frame. It may be shown. For example, the Type subfield may be a 2-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. That's fine. If the Type subfield is set to 10, the frame type may also be a Data frame.

[0056] 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.

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

[0058] The frame subtype may be determined from the Type and Subtype subfields contained in the Frame Control field of the MAC header. The Subtype subfield is 4 bits. It may also be a subfield of . 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 field is set to 10, the Type subfield may indicate a Data frame.

[0059] For example, the Type subfield indicates a Management frame, and the Subtype subfield If 0000 is set, the subtype may be Association Request. The Type subfield indicates Management frame and the Subtype subfield is 0001. If configured, the subtype may be Association Response. In the table, the Management frame is shown, and the Subtype subfield is set to 0010. If present, the subtype may be a Reassociation Request. If the Type subfield indicates a Management frame and the Subtype subfield is set to 0011, the subtype may be a Reassociation Response. If a frame is shown and the Subtype subfield is set to 0100, the subtype may be a Probe Request. If the Type subfield shows a Management frame and the Subtype subfield is set to 0101, the subtype may be a Probe Response. It is also acceptable. The Type subfield indicates the Management frame, and the Subtype subfield If 1000 is set in the configuration, the subtype may be Beacon.

[0060] A Beacon frame may be a frame containing information such as the Beacon 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 be a frame containing information such as the Status code. An Association Response frame may be a frame that is sent as a response to a received Association request frame. An Association Response frame may be a frame containing information such as the Status code. It may also be a frame. A Reassociation Response frame may be a frame sent in response to an received Reassociation Request frame. A Probe Response frame is The frame may also contain information such as the Beacon's period and SSID. The Probe Response frame may be a frame sent as a response to a received Probe Request frame.

[0061] 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.

[0062] For example, the Type subfield indicates a Data frame, and the Subtype subfield is 00 If 00 is set, the subtype may be Data. If the Type subfield indicates a Data frame and the Subtype subfield is set to 1000, then the subtype This may also be QoS Data.

[0063] The Frame body field of the MAC frame format may consist of fields and elements defined for each subtype of management frame. The elements are displayed in the specified relative order, and non-existent fields or elements may be skipped. If the STA encounters an element ID that it cannot recognize in the frame body of the 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.

[0064] The element format of each element contained within the Frame body is determined by the Element ID field and Length field. Defined in fields, Element ID Extension fields, information fields, etc. This is also acceptable. The Information field may contain information specific to the element. For example, if the Element ID is 61, it may indicate the element for HT Operation. For example, Element If the ID is 191, it may indicate an element for VHT Capabilities. For example, if the Element ID is 192, it may indicate an element for VHT Operation. For example, if the Element ID is 255, it may indicate an element for HE Capabilities. For example, if the Element ID is 255, it may indicate an element for HE Operation.

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

[0066] The HT Operation element is 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. The HT Operation information field may indicate the Secondary Channel Offset field. The STA Channel Width field may also be included. 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 positioned 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 allow the use of any channel within the supported channel width set. In total, 1 may be set. The operation of HT STA(s) within the BSS may be controlled by an HT Operation element. That is, an HT Operation element may be an operation element that controls the operation of HT STA within the BSS.

[0067] HT Operation elements may be sent in a Management frame. HT Operation elements may be sent in a Control frame. HT Operation elements 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.

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

[0069] 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, the VHT operation element may be sent in the Association Response frame. For example, a VHT operation element may be sent in a Reassociation Response frame. For example, the VHT operation element may be sent in the Probe Response frame.

[0070] The Channel Width field in the VHT Operation information field is for HT operation The BSS bandwidth may be defined along with the element's STA channel width field. The Channel Width field may be set to 0 for a 20MHz or 40MHz BSS bandwidth. Good. The Channel Width field may be set to 1 for 80MHz, 160MHz, or 80+80MHz BSS bandwidth. The Channel Width field may be set to 2 for 160MHz BSS bandwidth. The Channel Width field may be set to 2 for 80+80MHz BSS bandwidth. 3 may be set. Values ​​in the Channel Width field ranging from 4 to 255 are reserved. That's fine.

[0071] Channel Center Frequency Segment 0 in the VHT Operation information field The channel is for VHT BSS at 20MHz, 40MHz, 80MHz, 160MHz, or 80+80MHz. You may define a center frequency. Channel Center Frequency Segment 0 field For a BSS bandwidth of 20MHz, 40MHz, or 80MHz, this may indicate the channel center frequency index of 20MHz, 40MHz, or 80MHz on which VHT BSS operates. The Channel Center Frequency Segment 0 field is for a BSS bandwidth of 160MHz and the Channel Width subfield is If 1, it may indicate the channel center frequency index of the 80 MHz channel segment containing the primary channel. The Channel Center Frequency Segment 0 field is the 160 MHz BSS. When the bandwidth and Channel Width subfield are 2, VHT BSS operates on a 160MHz channel. The channel center frequency index may also be shown. Channel Center Frequency Segment The 0 field has a BSS bandwidth of 80 + 80 MHz and a Channel Width subfield of 1 or 3. In this case, the channel center frequency index of the primary 80MHz channel of the VHT BSS may be shown.

[0072] Channel Center Frequency Segment 1 in the VHT Operation information field The code defines 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 BSS bandwidths of 20MHz, 40MHz, or 80MHz. The Channel Center Frequency Segment 1 field may be set to 0 for BSS bandwidths of 160MHz and Channel Width subfield is 1. The Channel Center Frequency Segment 1 field may indicate the channel center frequency index of the 160MHz channel on which the BSS operates. If the BSS bandwidth is 160MHz and the Channel Width subfield is 2, this field may be set to 0. If the BSS bandwidth is 80+80MHz and the Channel Width subfield is 1 or 3, the Channel Center Frequency Segment 1 field may indicate the channel center frequency index of the Secondary 80MHz channel of the VHT BSS.

[0073] The HE Operation Element format includes the Element ID field, the Length field, and the Element ID Extension field, HE Operation Parameter field, BSS Color Information field, Basic HE-MCS And NSS Set field, VHT Operation Information field Rudo, Max Co-Hosted BSSID Indicator field, 6GHz Operation Information field It may consist of a rd, etc. When operating in the 2.4GHz band, the HE STA in the HE BSS may be controlled by an HT Operation element and an HE Operation element. When operating in the 5GHz band, the HE STA in the HE BSS may consist of an HT Operation element and an VHT Operation element. If present, and may be controlled by an HE Operation element. When operating in the 6GHz band, the HE STA in the HE BSS may be controlled by an 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.

[0074] 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, an HE operation element may be sent in a Beacon frame. For example, an HE operation element may be sent in an Association Response frame. For example, an HE operation element may be sent in a Reassociation Response frame. For example, an HE operation element may be sent in a Probe Response frame.

[0075] 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.

[0076] 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.

[0077] 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 includes a Primary channel field, a Control field, a Channel Center Frequency Segment 0 field, and a Channel Center Frequency Segment 1 field. It may consist of a Minimum Rate field, etc. The Primary Channel field is The channel number of the primary channel at 6 GHz may also be indicated. The Channel Center Frequency Segment 0 field indicates the 20 MHz, 40 MHz, 80 MHz, 160 MHz of the BSS operating at 6 GHz, and This may indicate the channel center frequency index of the 80+80MHz channel. The Frequency Segment 0 field is used when the BSS channel width is 160MHz or 80+80MHz. The Channel Center Frequency Segment 1 field may indicate the channel center frequency index of the primary 80MHz channel. The Channel Center Frequency Segment 1 field may indicate the channel center frequency index of the 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 if 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, which is 0 for 20MHz and 40MHz. For a combination, 1 may be set; for 80MHz, 2 may be set; and for 80+80MHz or 160MHz, 3 may be set.

[0078] 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. Good. When operating in the 5GHz band, the EHT STA in the EHT BSS may be controlled by the HT Operation element, VHT Operation element (if present), HE Operation element, and EHT Operation element. When operating in the 6GHz band, the EHT STA in the EHT BSS may be controlled by the HE Operation element and EHT Operation element.

[0079] The EHT Operation element format includes Element ID, Length, Element ID Extension, EHT Operation Parameter, Basic EHT-MCS And Nss Set, and EHT Operation Information. It may consist of fields. The EHT Operation Information field may consist of a Control subfield, a CCFS0 subfield, a CCFS1 subfield, and a 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. For a 160MHz EHT BSS bandwidth, 3 may be defined. Channel Width subfeed Rudo may define 4 for a 320MHz EHT BSS bandwidth. CCFS0 subfield The primary 80MHz EHT BSS is available for 20MHz EHT BSS, 40MHz EHT BSS, 80MHz EHT BSS, and 160MHz EHT BSS. The CCFS0 subfield may define the channel, or the center frequency of the primary 160MHz channel of the 320MHz EHT BSS. The CCFS0 subfield may 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, a 40MHz BSS bandwidth, or an 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 the 160MHz EHT BSS or the 320MHz EHT BSS. The field may be set to 0 for the 20MHz BSS bandwidth, 40MHz BSS bandwidth, or 80MHz BSS bandwidth. The CCFS1 subfield may index the center frequency of the 160MHz channel for the 160MHz BSS bandwidth. CCFS1 subfield This may involve indexing the center frequency of a 320MHz channel for a 320MHz BSS bandwidth.

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

[0081] 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 Address1 field, an Address2 field, an Address3 field, a Sequence Control field, an Address4 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, MSDU, and padding. The A-MSDU subframe header is a DA file. It may consist of a field, an SA field, and a Length field.

[0082] A-MPDU (Aggregate MPDU) is a sequence of one or more A-MPDU subframes and a variable amount of EOF. It may consist of padding. Each A-MPDU subframe may optionally be followed by an MPDU delimiter. It may consist of an MPDU. Each nonfinal A-MPDU subframe within an A-MPDU may have padding octets added to make the subframe length a multiple of 4 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 consists of the EOF field, the Reserved field, and the MPDU Even if it consists of a Length field, a CRC field, and a Delimiter Signature field good.

[0083] Figure 7 shows an example of an A-MPDU according to one aspect of this embodiment. 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 and a Reserved field. Fields: MPDU Length field, CRC field, Delimiter Signature field The EOF Padding field may consist of an EOF Padding subframe field and an EOF Padding Octets field.

[0084] MSDU or MMPDU (MAC Management Protocol Data Unit) for smaller MAC-level files The process of splitting into MPDUs may also be called fragmentation. MAC is Fragmenting and reconstructing MSDUs or MMPDUs that are delivered in individually addressed MPDUs It is permissible.

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

[0086] A PPDU consists of components such as the PHY preamble, PHY header, and PSDU (PHY Service Data Unit). PPDU may also be assigned L-STF, L-LTF, and L-SIG. PPDU may also be assigned HT-STF, HT-LTF, and HT-SIG. PPDU may also be assigned VHT-STF, VHT-LTF, VHT-SIG-A, and VHT-SIG-B. The following may be assigned: PPDU may be assigned HE-STF, HE-LTF, HE-SIG-A, HE-SIG-B. PPDU may be assigned HT-STF, HT-LTF, HT-SIG in addition to L-STF, L-LTF, L-SIG. In addition to L-STF, L-LTF, and L-SIG, PPDU also includes VHT-STF, VHT-LTF, VHT-SIG-A, and VHT-SIG-B. The following may be assigned: 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.

[0087] 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 is a PSDU, PHY It may consist of a preamble, 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.

[0088] The time interval between frames may also be called IFS (Inter Frame Space). STA is specified The carrier sense function may be used at the specified time interval to determine if the medium is idle. In other words, the STA may perform carrier sense for the duration of the IFS to determine whether the medium is idle or not.

[0089] 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).

[0090] The time interval may differ depending on the type of IFS. For example, PIFS has a longer time interval than SIFS. An IFS with a longer interval is also acceptable. DIFS may be an IFS with 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 short time interval may be an IFS with a high priority level for access to the wireless medium.

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

[0092] 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.

[0093] CCA (Clear Channel Assessment) is the process of determining the current usage status of a wireless medium. It is acceptable. CCA is a function at the physical layer for determining the current usage state of the wireless medium. It is also acceptable to refer to CCA as CCA function.

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

[0095] For example, career sense may include backoff and / or EDCA and / or channel access and / or CCA. It may also be referred to as EDCA and / or Channel Access and / or CCA.

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

[0097] 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.

[0098] The basic method of accessing MACs used by STAs may be DFC (Distributed Coordination Function). DCF ensures the same coordination across all STAs within the BSS when the network is operational. The functional logic may always be an active class adjustment function. DCF is one of CSMA / CA It may be a species. DCF may be a feature that needs to be implemented in all STAs.

[0099] The STA detects the medium and determines whether another STA is currently transmitting in order to transmit. If the medium is not busy, the STA may transmit. If interrupted, STA will postpone the transmission until the current transmission is complete.

[0100] In the CSMA / CA distributed algorithm, specified between frame exchange sequences. A gap exists in the specified period. The specified gap in the frame exchange sequence may be referred to as the IFS. The transmitting STA ensures that the medium is idle for a certain required period before attempting to transmit. This required period may be the specified gap in the frame exchange sequence. This required period may be referred to as the IFS. .

[0101] STA resets the backoff counter before attempting to transmit again after a delay or immediately after a successful transmission. The backoff counter may be initialized to a random value. The STA may decrement the backoff counter once every aSlotTime while the medium is idle. aSlotTime may be the time length of the slot. The slot time referred to here may be the time of the slot that the MAC uses to define the IFS. aSlotTime may also be a predetermined time length. It may also be a fixed time length (for example, in microseconds).

[0102] The basic media access protocol may be DCF. DCF is a protocol that allows CSMA / CA and media to be accessed via Through the use of a random backoff counter after the G state, media between compatible PHYs Enables automatic sharing. All individually addressed traffic will use an immediate positive acknowledgment (Ack frame), and if an Ack frame is not received, it will not send Resending is scheduled by the person in charge. Multiple STAs are waiting for the medium to become available. There is a possibility of collisions occurring, and the likelihood of collisions is highest when the medium transitions from busy to idle. Therefore, a random backoff procedure is necessary to resolve medium contention. An STA transmission can interfere with (collision with) other STA transmissions even if the carrier sense function (CS function) indicates the medium is not busy. Interference is expected. This may be specified if a response frame is not received.

[0103] STAs that wish 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 will continue without interruption until the medium is determined to be idle during the IFS. It waits. Here, the type of IFS is when the transition to the last idle state is correctly received on the medium. If the detection is based on frames that were not detected, EIFS may be used. Otherwise, IFS The type may be DIFS. After the medium idles in DIFS or EIFS, the STA may generate a random backoff count for an 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 pseudorandom integer obtained by subtracting a uniform variance between [0, CW]. CW is an integer within the range of the values ​​aCWmin and aCWmax, which are characteristics of the PHY. It is also acceptable to have a value of CW greater than or equal to aCWmin and less than or equal to aCWmax. CW may also be called the Contention Window.

[0104] 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. The contention window maintains the value of aCWmax until it is reset when aCWmax is reached. If a data frame or management frame is successfully sent, the contention window may be reset to aCWmin. If SSRC reaches dot11ShortRetryLimit, the contention window may be reset to aCWmin. The set of contention window values ​​starts at the PHY-specific aCWmin value and continues up to the PHY-specific aCWmax. Alternatively, the values ​​can be sorted in ascending order as integers obtained by subtracting 1 from powers of 2. For example, if aCWmin is 7 and aCWmax is 255, the set of contention windows is 7, 15, 31, 63, 127. It may also be a set that includes 255.

[0105] 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.

[0106] 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 combines aspects of contention-based and contention-free access methods to provide prioritized, parameterized QoS access to the QoS STA via the wireless medium. It is a well-functioning system that continues to support non-QoS STA for best-effort transfers. It is also acceptable. HCF stands for EDCA (Enhanced Distributed Channel Access). Both access and HCCA (HCF controlled channel access) Features provided by may be included. HCF uses EDCA mechanisms for competition-based transfers. You may also use a competition-based channel access method called M. HCF is competition-free. A control channel access method called the HCCA mechanism may be used for the transfer.

[0107] HCCA (HCF Controlled Channel Access) is an individually addressed downlink For transmission, uplink transmission, and direct link transmission, QoS STA ensures that contention is handled. This may also be a channel access mechanism used by a Hybrid Coordinator (HC) to coordinate the use of a non-existent medium.

[0108] The EDCA mechanism uses eight different UP (User Priority) values ​​to send wireless media to the STA. It may provide differentiated distributed access. UP uses MSDU (MAC Service Data Unit) This is an associated value and may indicate how MSDU is processed. UP is the higher level of MAC. The MSDU may be assigned at the layer. UP may take any value from 0 to 7. The EDCA mechanism may define four ACs (Access Categories) to support traffic delivery using the STA's UP. ACs are QoS STA channels AC may be a label for a common set of EDCA parameters used to compete for and send MSDUs with a specific priority. AC may take one of the values ​​AC_BE, AC_BK, AC_VI, or AC_VO. AC_BE, AC_BK, AC_VI, and AC_VO may indicate access categories corresponding to best effort, background, video, and voice, respectively.

[0109] QoS (Quality of Service) functions (facilities) are parameterized and prioritized. Extended functions, channel access rules, and frame rates used to provide a QoS are also used. - It may be a mat, frame exchange sequence, or managed object. QoS STA is , or an STA that implements QoS functionality. A QoS AP is an AP that supports QoS functionality. Alternatively, a QoS BSS may also be a BSS that provides QoS functionality. This may include a QoS AP.

[0110] An EDCFA (Enhanced Distributed Channel Access Function) is a logical function within a QoS STA that uses an 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. DCFs and HCFs may be defined to operate within the same BSS.

[0111] Each EDCAF may maintain a backoff counter measured in the backoff slot. When the backoff procedure is called, the backoff counter is raised in a uniform distribution from 0 to CW. It may be set to an integer value selected randomly. AIFS may be defined as AIFSN × aSlotTime + aSIFSTime. For example, in OFDM PHY characteristics, with 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. i. If AC is AC_VO, AIFSN may be 2. CW may be in ascending order as integers obtained by subtracting 1 from a power of 2, starting from the PHY-specific CWmin value and continuing up to the 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, for 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 per aSlotTime period while the medium is idle. Each time an MPDU transmission attempt fails and any STA's retry count increases, it takes a series of the following values.

[0112] In HCF, the basic unit of assigning transmission rights to a wireless medium may be a TXOP. A TXOP (Transmission Opportunity) is a frame exchange opportunity on a wireless medium provided by a specific QoS STA. It may be a time interval during which one has the right to start a match. TXOP may be defined by the start time and maximum duration. TXOP may be obtained by EDCA. That is, STA is EDCA If you do this, you may earn TXOP.

[0113] Figure 10 shows an example of a backoff procedure according to one aspect of this embodiment. In Figure 10, the horizontal axis may represent time. 1001 may represent the transmission of STA#1. 02 may be an IFS. 1003 may be a backoff counter. 100 3 may be called the contention window. 1004 is the transmission of STA#2. Alternatively, in Figure 10, STA#2 may detect 1001 on the channel. STA#2 is 1 While 001 is detected, the channel may be judged as busy. In other words, 1001 may be the period during which the channel is judged as busy. STA#2 implements carrier sense. You may then determine whether the channel is busy or not. STA#2 will complete period 1001. If the channel is determined to be idle, carrier sensing may be performed for a period of 1002. For example, 1002 may be DIFS. 1002 may also be AIFS. STA#2 If the channel is idle for a period of 1002, then 1003 may be started. 1003 decrements the backoff counter while the channel is idle. For example, 6 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 sends Signal (1004) may be performed. Here, the backoff counter may be determined to be between 0 and CW. CW may be a value selected from a range of values ​​between aCWmin and aCWmax. The channel may be called the radio medium.

[0114] The carrier sense mechanism uses NAV (Network Allocation Vector) status and STA transmission. The mechanism may combine the physical carrier sense of the 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 CCA (Clear Channel Assessment) function detects that the medium is busy. stomach.

[0115] 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 Alternatively, this may be done in the MAC layer processing unit AU3.

[0116] 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.

[0117] 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 may be controlled by the physical layer processing unit AU3. The carrier sense function may be controlled by the MAC layer processing unit AU4. NAV in STA is the MAC layer The NAV in the AP may be controlled by the MAC layer processing unit SU4.

[0118] The STA may set NAV if the address field of the received frame is not its own address. When the STA receives at least one valid frame in the PSDU, it sets NAV in the PSDU. The STA may update the NAV using the information from any valid Duration field. The STA may update the NAV if the value indicated by the Duration field of the received frame is greater than the current NAV value. The STA may update the NAV if the RA (address) of the received frame is greater than the STA's own MAC address. If they are equal, the NAV will not be updated.

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

[0120] The NAV may be a basic NAV. The NAV may also be an intra-BSS NAV. basic NAV It may also be called NAV. Intra-BSS NAV may also be called NAV. NAV is called basic NAV. This may be done. NAV may be called intra-BSS NAV. Basic NAV may be called NAV. Intra-BSS NAV may be called NAV.

[0121] RTS (Request To send) may also be called RTS frame. CTS (Clear The "To send" object may also be referred to as a CTS frame.

[0122] 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. Virtual carrier sense... The reservation mechanism is implemented by distributing reservation information that notifies users of the upcoming use of the media. Exchanging RTS frames and CTS frames before the actual data frame may be one of the means of distributing the media reservation information. The RTS frame and CTS frame are the actual data frame The Duration field defines the period during which the medium is reserved for sending an Ack frame. May include: RTS frames (sent by the originating STA) or CTS frames (destination The STA that receives the originating STA processes the media reservation. The STA receives from the originating STA. Even if it's not possible, you can still know that the media is intended to be used to send the data frame. The media reservation information is in the Duration / ID field of the individually addressed frame. It may be distributed via [platform name]. The Duration / ID field indicates the time (period) for which the media is reserved. The Duration / ID field may indicate the time the medium is reserved to end in the following Ack frame. For fragment sequences, the Duration / ID field This is the time the medium is reserved until the end of the Ack frame that follows the next fragment. This may also be shown. The RTS / CTS mechanism may function even when multiple BSSs using the same channel overlap. The media reservation mechanism may function across BSS boundaries.

[0123] The RTS (Request To Send) frame format includes the Frame Control field and the Duration field. The RTS frame format may include the RA field, TA field, and FCS field. The Duration field of the RTS frame format may indicate the time (in microseconds) required to transmit the pending data or management frame, one CTS frame, one Ack frame, and three SIFS frames. The RA field of the RTS frame indicates the intended direct transmission of the pending individual addressable frame. The TA field may be the address of the receiving STA. 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.

[0124] The CTS (Clear To Send) frame format uses the Frame Control field and the Duration field. The RA field and FCS field may be included. The Duration field of the CTS frame format sent in response to an RTS frame may be the Duration field of the previous RTS frame minus the time required to send the CTS frame and the SIFS for it. In other words, it may be the time required to send the pending data or management frame, one Ack frame, and two SIFS. The CTS frame is the first frame of the exchange, and the pending data Alternatively, if the management frame requires an acknowledgment, the Duration field indicates the time required to send the pending data or management frame, two SIFSs, and one Ack frame. (May be in microseconds). The CTS frame is the first frame of the exchange and is held. If the data or management frame inside does not require immediate acknowledgment, the Duration field is the time required for the pending data or management frame and one SIFS transmission. It is also possible. If the CTS frame is a response to the RTS frame, the RA fee of the CTS frame The `rd` bit is set to the address of the TA field of the RTS frame, and the individual / group bits are set to 0. It may be set to if the CTS frame is the first frame in a frame exchange, then the RA frame The field may be set to the MAC address of the sender.

[0125] Figure 11 is a diagram showing an example of a NAV according to one aspect of this embodiment. In Figure 11, horizontal The 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. It could be the production timeline. 1104 could also be the timeline of STA#2's operation. Good. 1101, 1102, 1103, and 1104 may be timelines on the same channel. 1105 may be an RTS frame. 1106 may be the NAV period for AP#1. 1107 may be a CTS frame. 1108 may be the NAV period for STA#2. It can be in between. 1109 can be a Data frame. 1110 is an AcK frame. It may be present. 1111 may be IFS. 1112 is Contention Window It may also be U (backoff counter, backoff procedure). STA#1 is 1105 to AP#2 It may be sent to [address]. AP#1 will receive 1105 and the duration indicated in the RTS Duration field will be [duration]. You can also set it to 1106. When AP#2 receives 1105, it sends 1107 to STA#1. You may send a message. STA#2 may set 1108 for the duration indicated in the CTS Duration field upon receiving 1107. STA#1 may send 1109 upon receiving 1107. AP#2 may send 1110 to STA#1 upon receiving 1109. AP#1 may start 1112 with 1111 if the channel is idle after 1106 has finished. STA#2 If the channel is idle after 1108 has finished, 1112 may be started with 1111. There may be an IFS between 1105 and 1107. AP#2 may send 1107 if the channel is idle during the IFS period before sending 1107. There may be an IFS between 1107 and 1109. STA#1 may send 1109 if the channel is idle during the IFS period before sending 1109. There may be an IFS between 1109 and 1110. AP#2 will send 1110 if the channel is idle during the IFS period before sending 1110. This is also possible. 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. This is also acceptable. For example, STA#2 may be 2088 in Figure 2. 1101 is AP Alternatively, it may be the timeline of the STA's operation. 1102 may be the timeline of the AP or STA's operation. 1103 may be the timeline of the AP or STA's operation. 1104 may be the timeline of AP or STA operation.

[0126] STA or AP may perform a frame exchange. For example, frame exchange The exchange occurs when STA or AP transmits RTS, and STA or AP transmits CTS in response to RTS. This is also possible. For example, frame exchange may occur when the STA or AP sends a Trigger frame, and the STA or AP sends a CTS in response to the Trigger frame. For example, frame exchange may occur when the STA or AP sends a MU-RTS (MU-RTS Trigger frame) and the STA or AP sends a CTS to the MU-RTS. For example, the Trigger frame may be used by the AP to allocate a RU (Resource Unit) to the STA. The Trigger frame is The frame may include 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 each other. The User Info List field may include zero or more User Info fields. Good. The User Info field may also be a field for allocating RUs to each STA. For example, the User Info field may include an RU allocation subfield. MU-RTS may also be referred to as MU-RTS Trigger frame.

[0127] 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 as a non-HT PPDU. For example, the trigger frame may be sent as a non-HT duplicate PPDU.

[0128] 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 referred to as channel aggregation. Good. Channel bonding uses multiple channels simultaneously to transmit data, so This increases bandwidth and improves data transmission speed. Multiple channels used by BSS members This may include a primary channel and one or more secondary channels, and channel bonding may be performed using multiple of these channels.

[0129] The primary channel is a common channel for 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 40MHz channel may be a 40MHz channel on which a 40MHz PPDU is transmitted in an 80MHz, 160MHz, or 80+80MHz BSS. That's fine too. The primary 80 channel transmits an 80MHz PPDU in a 160MHz or 80+80MHz BSS. It may be a trusted 80MHz channel. The primary 160MHz channel is connected to the 320MHz BSS. It may also be a 160MHz channel including a primary 20MHz channel. 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 referred to as the primary 20MHz channel. The primary 20MHz channel may also be referred to as the primary channel. The primary channel may also be the primary 20MHz channel. The primary 20MHz channel may also be the primary channel.

[0130] 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 called 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 be a channel that combines with the primary 20MHz channel to form a 40MHz channel. In an 80MHz BSS, the secondary 20MHz channel may be a channel adjacent to the primary 20MHz channel. A secondary 20MHz channel may be a 20MHz channel adjacent to a 20MHz channel. In an 80MHz BSS, the secondary 20MHz channel may combine with the primary 20MHz channel to form a primary 40MHz channel. A secondary 20MHz channel may be a 20MHz channel adjacent to the primary 20MHz channel in a 160MHz or 80+80MHz BSS. A secondary 20MHz channel may combine with the primary 20MHz channel in a 160MHz or 80+80MHz BSS. The secondary 40MHz channel may be a channel that forms a primary 40MHz channel. The secondary 40MHz channel may be a 40MHz channel adjacent to the primary 40MHz channel in an 80MHz BSS to form an 80MHz channel. The secondary 40MHz channel may be a 40MHz channel adjacent to the primary 40MHz channel in a 160MHz or 80+80MHz BSS to form a primary 80MHz channel. The secondary 80MHz channel may be a channel that forms a primary 40MHz channel in a 160MHz or 80+80MHz BSS. In an 80+80MHz BSS, this is an 80MHz channel that does not include the primary 20MHz channel. This is also fine. The secondary 80MHz channel can be combined with the primary 80MHz channel to produce 160MHz or The 80+80MHz channel may be configured. The secondary 160MHz channel, in a 320MHz BSS, may, together with the primary 160MHz channel, form a 320MHz channel of the 320MHz EHT BSS, and may be a 160MHz channel that does not include the primary 20MHz channel.

[0131] The non-primary channel is any 20MHz channel other than the primary 20MHz channel in the 40MHz channel, 80MHz channel, 160MHz channel, 80+80MHz channel, and 320MHz channel. It is delicious.

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

[0133] When performing channel bonding, the STA performs a backoff procedure on the primary 20MHz channel. Alternatively, channel sensing can be performed using PIFS immediately before transmission on the secondary channel. Example For example, in Figure 12, STA transmits with a 160MHz channel width, so 1201 A backoff procedure may be performed, and for 1202, 1203, 1204, 1205, 1206, 1207, and 1208, channel sensing may be performed for the PIFS period immediately before transmission.

[0134] The Operating class is an index to a set of values ​​for radio operation in a regulated domain. It may be shown. The Operating class value is the frequency for the channel number, the available channels. The center frequency of the channel and the maximum usable channel width may be indicated. Operating class value. Channel starting frequency, Channel Spacing, Channel This may also indicate a set of channels. A channel set is a set of regulatory domains and This may be a list of valid integer channel numbers for the class. Channel Spacing uses the maximum bandwidth of one frequency segment allowed in the Operating class. The Operating class value may also be the frequency difference between the center frequencies of adjacent channels that do not overlap. 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. That's also fine. The Operating class value can also be an Operating class index.

[0135] 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 contained in the frame received from the AP. The STA may determine dot11CurrentPrimaryChannel from the information in the Primary Channel field contained in the HT Operation element. The STA may determine dot11CurrentPrimaryChannel from the Primary Channel field contained in the HT Operation element. The STA may determine dot11CurrentPrimaryChannel from the information in the Primary channel field in the 6GHz Operation Information field contained in the HE Operation element. For example, the STA that received a Beacon frame from the AP Alternatively, the primary channel may be determined 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 by the Operating Class field.

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

[0137] In channel bonding, the STA may perform a backoff procedure on the primary channel, sense the PIFS period on the secondary channels, and then transmit. An EDCA TXOP may be obtained based on the activity. The transmission bandwidth may be determined by the CCA status of nonprimary channels in the PIFS before transmission.

[0138] The PHY-CCA.indication primitive may be a primitive that indicates the current state of the medium from the PHY to the MAC entity. The PHY-CCA.indication primitive includes the STATE parameter. This is also acceptable. The PHY-CCA.indication primitive may include a channel-list parameter. The STATE parameter of the PHY-CCA.indication primitive may be one of two values: BUSY or IDLE. The PHY-CCA.indication primitive may include at least the STATE parameter. The PHY-CCA.indication primitive may include at least the channel-list parameter. The PHY-CCA.indication primitive may include at least the STATE and channel-list parameters. PH The STATE parameter value of Y-CCA.indication primitive may be BUSY if it indicates that the channel is unavailable during the PHY's channel evaluation. Otherwise, the STATE parameter value of PHY-CCA.indication primitive may be IDLE. When STATE is in the IDLE state, the channel-list parameter does not exist. Type of PHY in operation If the CCA is determined by a single channel, the channel-list parameter is: Does not exist. Otherwise, the channel-list parameter may contain a set of channels that are busy. In other words, the CCA may have multiple channels If determined to be BUSY, the channel-list parameter may exist. For example, the entries for the channel-list parameter may be primary, secondary, secondary40, and secondary80. The STATE parameter may be referred to as the STATUS parameter. The STATUS parameter may be referred to as the STATE parameter.

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

[0140] 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.

[0141] 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. "To perform" may be synonymous with "to generate a primitive." "To generate a primitive" may be synonymous with "to issue a primitive."

[0142] When MAC receives a PHY-CCA.indication that has a channel-list parameter, it determines which channel You can determine if a channel is idle. If the channel-list parameter entry in PHY-CCA.indication is primary, you can determine that there are no idle channels. If the channel-list parameter entry in PHY-CCA.indication is secondary, the primary channel is idle. It may be determined that the primary channel and secondary 20MHz channel are idle. If the channel-list parameter entry in PHY-CCA.indication is secondary40, then the primary channel and secondary 20MHz channel are considered idle. This is acceptable if the channel-list parameter entry in PHY-CCA.indication is secondary80. The primary channel, secondary 20MHz channel, and secondary 40MHz channel are It can be considered an idol.

[0143] For example, in Figure 12, 1201 may be the primary channel. 1202 may be the secondary channel (secondary 20MHz channel). 1203 and 1204 Then, a secondary 40MHz channel may be configured. 1205, 1206, 1207, and Alternatively, a secondary 80MHz channel may be configured with 1208. That is, a bandwidth of 160MHz In Figure 12, the primary channel is 1201, the secondary channel (secondary 20MHz channel) is 1201, the secondary 40MHz channel consists of 1203 and 1204, and the secondary 80MHz channel consists of 1205, 1206, 1207, and It may also be configured as 1208. For example, STA indicates that the primary channel (1201) is busy when the channel state changes from idle to busy. The STA may issue a primitive(PHY-CCA.indication(BUSY,{primary})). When the state of a primary channel changes from busy to idle, the STA may issue a primitive(PHY-CCA.indication(IDLE,{primary})) indicating that the primary channel is idle. If the primary channel issues a primitive(PHY-CCA.indication(BUSY,{primary})) indicating that the primary channel is idle, it may be determined that there are no idle channels. STA may issue a primitive associated with the secondary channel (1202) if the primary channel is idle. STA may issue a primitive (PHY-CCA.indication(IDLE,{secondary})) indicating that the secondary channel is idle if the secondary channel (secondary 20MHz channel) is idle. STA may issue a primitive (PHY-CCA.indication(BUSY,{secondary})) indicating that the secondary channel (secondary 20MHz channel) is busy if the secondary channel is busy. PHY-CCA.indication(IDLE,{secondary}) may indicate that both the primary and secondary channels are idle. PHY-CCA.indication(BUSY,{secondary}) indicates that the primary channel is idle and the secondary channel The STA may indicate that the channel is busy. The STA may issue a primitive associated with the secondary 40MHz channel (composed of 1202 and 1204) if the primary channel and secondary 20MHz channel are idle. The STA will indicate that the secondary 40MHz channel is idle In this case, the STA may issue a primitive (PHY-CCA.indication(IDLE,{secondary40})) indicating that the secondary 40MHz channel is idle. If the secondary 40MHz channel is busy, the STA may issue a primitive (PHY-CCA.indication(BUSY,{secondary40})) indicating that the secondary 40MHz channel is busy. PHY-CCA.indication(IDLE,{secondary 40}) The primary channel, secondary channel, and secondary 40MHz channel are idle. It may indicate that the primary channel and secondary channel are idle, and the secondary 40MHz channel is busy. STA indicates the primary channel, the secondary 20MHz channel, and If the secondary 40MHz channel is idle, the STA may issue a primitive associated with the secondary 80MHz channel (composed of 1205-1208). If the secondary 80MHz channel is idle, the STA may issue a primitive (PHY-CCA.indication(IDLE,{secondary80})) indicating that the secondary 80MHz channel is idle. If busy, a primitive(PHY-CCA.indication(BUSY,{secondary80})) may be issued to indicate that 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 indicate that the primary channel, secondary channel, and secondary 40MHz channel are idle, and the secondary 80MHz channel is busy.

[0144] STA may determine the PHY-CCA.indication primitive in the physical layer processing unit SU3. STA Even if the PHY-CCA.indication primitive determined in the physical layer processing unit SU3 is shown to the MAC layer processing unit SU4 Good. The AP may issue the PHY-CCA.indication primitive in the physical layer processing unit AU3. The PHY-CCA.indication primitive determined in the physical layer processing unit AU3 is shown to the MAC layer processing unit AU4. That's good too.

[0145] An STA with an operation channel width of W MHz must initiate a PPDU that occupies at least the primary 20 MHz channel with a W MHz operation channel width at a predetermined rate (e.g., 90% or more). The probability of detection is such that the power of the preamble or PPDU measured within the primary 20MHz channel is If the value is above a predetermined value (for example, -82dBm or higher), the PHY-CCA.indication(BUSY, {primary}) primitive may be issued within the aCCATime period. In other words, the STA may issue the PHY-CCA.indication(BUSY, {primary}) primitive when it receives a non-HT duplicate or PPDU exceeding -82dBm on the primary 20MHz channel. -82dBm may be a threshold for determining whether the channel is idle or busy.

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

[0147] 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 the 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, {primary}) primitive if there are no conditions to issue the PHY-CCA.indication(BUSY, {primary}) primitive, and in the idle operating channel widths of 40 MHz, 80 MHz, 160 MHz, and 80+80 MHz. If a 20MHz preamble or PPDU of -72dBm or higher is detected on the secondary 20 MHz channel with a probability of 90% or higher within the aCCAMidTime period, the PHY-CCA.indication(BUSY, {secondary}) primitive is issued. -72dBm is the threshold for determining whether the channel is idle or busy. It may also be a value.

[0148] The PHY will issue PHY-CCA.indication(BUSY, {primary}) and PHY-CCA.indication(BUSY, {secondary}) primitives when there are no conditions for them to be issued, and in an idle operating channel width of 80MHz, 160MHz, or 80+80MHz, any signal in the secondary 40 MHz channel will be issued. However, if the threshold of -59dBm or higher is exceeded within aCCATime after reaching the receiver antenna, the PHY issues the PHY-CCA.indication(BUSY, {secondary40}) primitive. In this case, the PHY does not issue the PHY-CCA.indication(BUSY, {secondary80}) primitive or the PHY-CCA.indication(IDLE) primitive. The PHY does not issue the PHY-CCA.indication(BUSY, {primary}) or PHY-CCA.indication(BUSY, {secondary}) primitive if there are no conditions for issuing the PHY-CCA.indication(BUSY, {secondary}) primitive and the PHY is idle in an 80MHz, 160MHz, or 80+80MHz operating channel width, and the 40MHz preamble or PPDU of -72dBm or higher occurs for 90% or more of the aCCAMidTime period in the secondary 40MHz channel. If detected with a certain probability, the PHY PHY-CCA.indication(BUSY, {secondary40}) primitive Issue. PHY is PHY-CCA.indication(BUSY, {primary}) and PHY-CCA.indication(BUSY, There are no conditions for issuing the {secondary}) primitive, and the idle state of 80MHz, 160MHz, Alternatively, in an operating channel width of 80+80MHz, any 20MHz subchannel of the secondary 40MHz channel has a 20MHz preamble or PPDU of -72dBm or higher, and aCCAMidTime If detected with a probability of 90% or higher within the specified period, the PHY PHY-CCA.indication(BUSY, {secondary40}) primitive is issued. -72dBm may be a threshold for determining whether the channel is idle or busy.

[0149] PHY is PHY-CCA.indication(BUSY,{primary}), PHY-CCA.indication(BUSY,{secondary} ), there are no conditions for issuing the PHY-CCA. Indication (BUSY, {secondary40}) primitive, and in idle operating channel widths of 160MHz or 80+80MHz, secondary If there is any signal above -56 dBm within the 80 MHz channel, issue the PHY-CCA.indication(BUSY, {secondary80}) primitive. The PHY issues the PHY-CCA.indication(BUSY, {primary}), PHY-CCA.indication(BUSY, {secondary}), and PHY-CCA.indication(BUSY, {secondary40}) primitives without conditions, and within the idle 160 MHz or 80 + 80 MHz operating channel bandwidth, if an 80 MHz preamble or PPDU above -69 dBm is detected with a probability of 90% or more within the aCCAMidTime period in the secondary 80 MHz channel, issue the PHY-CCA.indication(BUSY, {secondary80}) primitive. The PHY issues the PHY-CCA.indication(BUSY, {primary}), PHY-CCA.indication(BUSY, {secondary}), and PHY-CCA.indication(BUSY, {secondary40}) primitives without conditions, and within the idle 160 MHz or 80 + 80 MHz operating channel bandwidth, if a 40 MHz preamble or PPDU above -72 dBm is detected with a probability of 90% or more within the aCCAMidTime period in any 40 MHz subchannel of the secondary 80 MHz channel, issue the PHY-CCA.indication(BUSY, {secondary80}) Issue a primitive. The PHY issues a PHY-CCA.indication(BUSY,{primary}) primitive, a PHY-CCA.indication(BUSY,{secondary}) primitive, and a PHY-CCA.Indication (BUSY, {secondary40}) primitive when there is no such condition, and in an idle 160 MHz or 80 + 80 MHz operating channel width, a 20 MHz preamble or PPDU is detected at -72 dBm or higher with a probability exceeding 90% within the aCCAMidTime period in any 20 MHz subchannel of the secondary 80 MHz channel If so, issue a PHY-CCA.indication(BUSY, {secondary80}) primitive. Here, -56 dBm, -69 dBm, and -72 dBm are thresholds for determining whether the channel is idle or busy It may be.

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

[0151] A STA with a W MHz operation channel width detects the start of a PPDU occupying at least the primary 20 MHz channel with a probability of a predetermined ratio or more (for example, 90% or more) with a W MHz operation channel width, and the power of the preamble or PPDU measured within the primary 20 MHz channel is detected at -72 dBm or higher with a probability exceeding 90% within the aCCAMidTime period in any 20 MHz subchannel of the secondary 80 MHz channel If the signal is above a predetermined value (e.g., -82 dBm or higher), a PHY-CCA.indication with the STATUS parameter set to BUSY may be issued within the aCCATime period. In other words, the 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. The receiver may issue a PHY-CCA.indication with the STATUS parameter set to BUSY for any signal that exceeds a threshold (-62 dBm) on the primary 20 MHz channel by a predetermined value (e.g., 20 dB) higher than the sensitivity of the minimum modulation and coding rate, 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 does not issue a PHY-CCA.indication primitive with the STATUS parameter set to IDLE or a PHY-CCA.indication with a modified channel-list parameter.

[0152] PHY issues a PHY-CCA.indication primitive with the STATUS parameter set to BUSY. In the absence of any conditions and in an idle state, with operating channel widths of 40MHz, 80MHz, 160MHz, and 80+80MHz, any signal within the secondary 20 MHz channel reaches the receiver's antenna. If the threshold of -62dBm or higher is exceeded within aCCATime, the STATUS parameter is set to BUSY and the channel-list parameter is set to {secondary} in the PHY-CCA.indication primitive. It issues a PHY-CCA.indication primitive with the STATUS parameter set to BUSY. There are no conditions for issuing an alert, and the idle 40MHz, 80MHz, 160MHz, and 80+80MHz operations In the g channel width, the secondary 20 MHz channel has a 20 MHz preamble of -72 dBm or higher. Alternatively, if a PPDU is detected with a probability of 90% or more within the aCCAMidTime period, the receiver issues a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}. While the threshold remains exceeded following the indication, the receiver issues a PHY-CCA.indication primitive with the STATUS parameter set to IDLE, or with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40} or {secondary 80}. The set PHY-CCA.indication primitive will not be issued.

[0153] PHY issues a PHY-CCA.indication primitive with the STATUS parameter set to BUSY. If no conditions exist, and no PHY-CCA.indication primitive exists with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, then in the idle operating channel widths of 80MHz, 160MHz, and 80+80MHz, within the secondary 40 MHz channel... Any signal exceeding a threshold of -59 dBm within aCCATime after reaching the receiver's antenna In this case, a PHY-CCA.indication primitive is issued with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}. PHY sets the STATUS parameter to BUSY If there are no conditions to issue the PHY-CCA.indication primitive set to BUSY, and there is no PHY-CCA.indication primitive set to {secondary} with the STATUS parameter set to BUSY, then in the 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, the PHY will issue a PHY-CCA.indication primitive set to BUSY with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}. In the dollar state, with operating channel widths of 80MHz, 160MHz, and 80+80MHz, any 20MHz subchannel of the secondary 40MHz channel has a 20MHz preamble or PPDU of -72dBm or higher. However, if detection occurs with a probability of 90% or more within the aCCAMidTime period, the receiver issues a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}. While the threshold remains exceeded following the indication, the receiver issues 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 80}. No such issue will be issued.

[0154] PHY issues a PHY-CCA.indication primitive with the STATUS parameter set to BUSY. Set the conditions and STATUS parameter to BUSY, set the channel-list parameter to {secondary}, and set the PHY-CCA.indication primitive and STATUS parameter to BUSY. If no PHY-CCA.indication primitive exists with the channel-list parameter set to {secondary 40}, and any signal greater than -56dBm exists within the secondary 80 MHz channel in an idle 160MHz or 80+80MHz operating channel width, the STATUS parameter is set to BUSY and a PHY-CCA.indication primitive with the channel-list parameter set to {secondary 80} is issued. If the PHY does not have a PHY-CCA.indication primitive with the STATUS parameter set to BUSY, or a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, and if there is 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 160MHz or 80+80MHz operating channel width, an 80 MHz preamble or PPDU of -69 dBm or higher is detected with a probability of 90% or more 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}, then the PHY will issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY, or a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 80}. If there is no PHY-CCA.indication primitive with the el-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 in an idle state with an operating channel width of 160MHz or 80+80MHz, any 40MHz sub-channel of the secondary 80MHz channel If a 40MHz preamble or PPDU of -72 dBm or higher is detected in a channel with a probability of 90% or higher within the aCCAMidTime period, the PHY issues a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 80}. The PHY issues a PHY-CCA.indication primitive with the STATUS parameter set to BUSY, and if there are no PHY-CCA.indication primitives with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, or PHY-CCA.indication primitives with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}, then the PHY will issue a PHY-CCA.indication primitive. If, in an idle operating channel width of 160MHz or 80+80MHz, a 20MHz preamble or PPDU is detected at -72dBm or higher with a probability of more than 90% within the aCCAMidTime period on any 20MHz subchannel of the secondary 80MHz channel, then a PHY-CCA.indication primitive is issued with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 80}.

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

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

[0157] AP and / or STA may perform NPCA (Non Primary Channel Access). This allows access to other channels while the primary channel is busy due to OBSS traffic. It may also be an operation. For example, OBSS traffic may be a PPDU received from OBSS. OBSS traffic may also be an inter-BSS PPDU. OBSS traffic may be a NAV configured This may also be the case. OBSS traffic may be used even if basic NAV is configured. . OBSS traffic may also be OBSS frame exchange. APs and / or STAs back up on other channels while the primary channel is busy due to OBSS traffic. You may also perform an off procedure. For example, while the primary channel is busy due to OBSS traffic, The channel on which the backoff procedure is performed may be called the NPCA primary channel, secondary primary channel, etc. The name of the channel on which the backoff procedure is performed while the primary channel is busy may be a name other than those mentioned above. In other words, AP and / or STA may perform the backoff procedure on the NPCA primary channel when the primary channel becomes busy due to OBSS traffic. AP and / or STA will perform the backoff procedure on the primary channel if the NAV is on the primary channel due to the OBSS PPDU. The AP and / or STA may perform a backoff procedure on the NPCA primary channel for the configured period. Once the backoff procedure is complete on the NPCA primary channel, 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 send information related to NPCA primary channel access in a frame. The STA may, based on the frame received from the AP, access to the NPCA primary channel. It may determine related operations.

[0158] That is, the NPCA primary channel may be a channel for accessing the channel while the primary channel is busy. The NPCA primary channel may be a channel for accessing the channel while NAV is set on the primary channel. The NPCA primary channel may be a channel for accessing the channel while basic NAV is set on the primary channel. The NPCA primary channel may be a channel for accessing the channel while the primary channel is busy due to the OBSS PPDU. The NPCA primary channel may be a channel for accessing the channel while NAV is set on the primary channel due to the OBSS PPDU. While NAV is set, it may be referred to as while NAV is maintained. The channel access may be a backoff procedure. The channel access may be EDCA. The channel access may be EDCAF . The channel access may be CCA. The AP may transmit a frame including an information element including information related to Non Primary Channel Access. When performing Non Primary Channel Access, the AP may transmit a frame including an information element including information related to Non Primary Channel Access .

[0159] ​​It is also possible. The AP may include a frame containing an information element that includes information related to Non Primary Channel Access in order to indicate to the STA in the BSS whether Non Primary Channel Access is enabled or disabled. You may send a message. The AP will not perform Non Primary Channel Access in its BSS. If not applicable, the transmitted frame does not need to include an information element containing information related to Non Primary Channel Access. For example, information related to Non Primary Channel Access An information element containing information may be called an NPCA operation element. For example, an information element containing information related to Non Primary Channel Access may be called a UHR operation element. An information element containing 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. This is also acceptable. 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. An NPCA operation element may include a field indicating the Element ID. An NPCA operation element may include a field indicating whether Non Primary Channel Access is enabled or disabled. An NPCA operation element may indicate information for Non Primary Channel Access. A field may be included to indicate the location of the primary channel. NPCA operation The element includes a field to indicate the channel width for Non Primary Channel Access. It may be included. Fields other than those mentioned above may be included in the NPCA operation element. For example, if the STA receives a frame containing an NPCA operation element from the AP, it may perform Non Primary Channel Access. If the STA receives a frame containing an NPCA operation element from the AP, it may perform Non Primary Channel Access using the information indicated in the fields of the NPCA operation element. The STA receives the NPCA operation element from the AP. If a frame containing the element is received and indicates that Non Primary Channel Access is enabled, Non Primary Channel Access may be performed. The STA receives the NPCA operation element from the AP. If a frame containing [this] is not received, Non Primary Channel Access will not be performed. STA is AP If a frame containing an NPCA operation element is received and it indicates that Non Primary Channel Access is disabled, Non Primary Channel Access will not be performed. For example, a UHR operation element may contain information for controlling UHR STA. For example, a UHR operation element may contain information for Non Primary Channel Access. A 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 checks whether information related to Non Primary Channel Access is included in the UHR operation element. The UHR operation element may include fields indicating whether Non Primary Channel Access is enabled or disabled. The UHR operation element may include fields indicating the location of the NPCA primary channel for Non Primary Channel Access. The UHR operation element may include fields indicating the location of the NPCA primary channel for Non Primary Channel Access if it indicates that the UHR operation element contains information related to Non Primary Channel Access. The UHR operation element may include fields indicating the channel width for Non Primary Channel Access. The UHR operation element may include fields indicating the channel width for Non Primary Channel Access if it indicates that the UHR operation element contains information related to Non Primary Channel Access. Fields other than those mentioned above may be included in the UHR operation element. A field indicating the cardiac frequency may be included. For example, if the STA receives a frame from the AP that contains a UHR operation element, it may perform Non Primary Channel Access. If the STA receives a frame from the AP that contains a UHR operation element, it may perform Non Primary Channel Access using the information indicated in the field of the UHR operation element. Good. The STA receives a frame from the AP containing a UHR operation element, and if the UHR operation element indicates that Non Primary Channel Access is enabled, then Non Primary Channel access may be performed. The STA receives a frame containing the UHR operation element from the AP. If it does not receive, Non Primary Channel Access will not be performed. If the STA receives a frame from the AP containing a UHR operation element and it indicates that Non Primary Channel Access is disabled, Non Primary Channel Access will not be performed. The STA will not perform Non Primary Channel Access if it receives a UHR operation The element contains information related to Non Primary Channel Access, and the UHR operation element is included in this element. If it indicates that it is being received, Non Primary Channel Access may be performed. STA is receiving If the UHR operation element indicates that it does not contain information related to Non Primary Channel Access, then Non Primary Channel Access will not be performed.

[0160] The channel width for Non Primary Channel Access includes the primary channel. It may also be the bandwidth of a channel that does not include the channel. The channel width of Non Primary Channel Access may also be called the NPCA channel width. Non Primary Channel Access The channel width may also be called the NPCA operating channel width. AP Non Primary The channel width of Channel Access may also be called the NPCA BSS operating channel width. The channel width of Non-Primary Channel Access of AP is called the NPCA BSS bandwidth. It is also acceptable. The NPCA operating channel is the STA and / or AP's NPCA primary channel. When sending and / or receiving on a channel that does not include the primary channel, It may be present. The STA may notify the AP of its supported NPCA operating channel width capability.

[0161] 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 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 information about 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. NPCA may be performed if it is present. 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 It may include information related to this.

[0162] 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. AP includes at least the NPCA primary channel in its operating channel width. In addition, a frame containing information related to Non Primary Channel Access may be sent. STA If the frame received from the AP contains information related to Non Primary Channel Access, it is determined that at least one NPCA primary channel exists within the operating channel width. It is permissible for the STA to perform Non Primary Channel Access if the frame received from the AP contains information related to 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 there is no NPCA primary channel in the operating channel width. In other words, the STA receives information related to Non Primary Channel Access in the frame received from the AP. If no information is included, you may decide not to perform Non-Primary Channel Access.

[0163] STA or AP is the primary channel, and if idle, it includes one or more primary channels. Transmission may be performed on the 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 that include the NPCA primary channel but do not include the primary channel. The STA or AP may perform sensing on the NPCA primary channel if the primary channel is busy due to OBSS traffic, and transmit on one or more channels that include the NPCA primary channel but do not include the primary channel if the NPCA primary channel is idle. For example, OBSS traffic may be OBSS PPDU. The STA or AP may transmit on one or more channels that include the NPCA primary channel but do not include the primary channel. The STA or AP may receive on one or more channels that include the primary channel. AP does not include a primary channel, but includes at least one NPCA primary channel or Reception may be performed on multiple channels.

[0164] STA or AP may transmit using multiple channels in NPCA. When STA or AP transmits using multiple channels in NPCA, STA or AP performs a backoff procedure on the NPCA primary channel and immediately before transmission on the NPCA secondary channel. Sensing may be performed for a fixed period, followed by transmission. The NPCA secondary channel may be a channel other than the NPCA primary channel used for transmission using multiple channels in NPCA. The NPCA secondary channel may be defined as an NPCA secondary 20MHz channel, an NPCA secondary 40MHz channel, or an NPCA secondary 80MHz channel. Even if the usual 20MHz channel is a 20MHz channel related to the NPCA primary channel That's fine. For example, if an STA or AP transmits with a bandwidth of 40 MHz in NPCA, it may transmit using the NPCA primary channel and the NPCA secondary 20 MHz channel. The NPCA secondary 40 MHz channel may be a 40 MHz channel related to the NPCA primary channel. That's fine. 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 has two 20MHz channels. It may consist of channels. The NPCA secondary 80MHz channel may be an 80MHz channel related to the NPCA primary channel. For example, if an STA or AP transmits with a bandwidth of 160MHz in the NPCA, it may transmit using the NPCA primary channel, the NPCA secondary 20MHz channel, the NPCA secondary 40MHz channel, and the NPCA secondary 80MHz channel. The NPCA secondary 80MHz channel consists of four 20MHz channels. It is also acceptable to refer to the NPCA secondary channel by a different name. For example, the NPCA secondary channel may be called a secondary secondary channel. Good. The NPCA secondary 20MHz channel may be referred to in ways other than "NPCA secondary 20MHz channel". For example, the NPCA secondary 20MHz channel may be referred to as the secondary secondary 20MHz channel. The NPCA secondary 40MHz channel may be referred to in ways other than "NPCA secondary 40MHz channel". For example, the NPCA secondary 40MHz channel may be referred to as the secondary secondary 40MHz channel. The NPCA secondary 80MHz channel is NPCA It may be referred to by a name other than "secondary 80MHz channel." For example, NPCA secondary 80MHz The channel may also be called the secondary secondary 80MHz channel. In NPCA, This may also apply if channel access is being performed via the NPCA primary channel.

[0165] 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. The NPCA primary 40MHz channel may be referred to by a name other than NPCA primary 40MHz channel. The channel used for transmission on the 80MHz channel, which includes the NPCA primary channel but does not include the primary channel, may be referred to as the NPCA primary 80MHz channel. It is also acceptable. The NPCA primary 40MHz channel is the NPCA primary channel and the NPCA secondary It may consist of a 20MHz channel. The NPCA primary 80MHz channel consists of the NPCA primary channel, the NPCA secondary 20MHz channel, and the NPCA primary 40MHz channel. It may be done. The NPCA primary 80MHz channel is the NPCA primary 40MHz channel and the NPCA It may consist of a secondary 40MHz channel. The NPCA primary channel is the channel where carrier sensing is performed when the primary channel is busy, and may be a channel with a different frequency from the primary channel. In the case of G, even if it is a 20MHz channel used for transmitting PPDU with a 20MHz bandwidth Good. The NPCA primary 40MHz channel may be a 40MHz channel used to transmit PPDUs with a bandwidth of 40MHz 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 a bandwidth of 80MHz 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 more than one channel. Primary channel A frame may be transmitted using one or more channels, including the NPCA Primary channel and not including the primary channel. A PPDU may be transmitted using one or more channels, including the NPCA Primary channel and not including the primary channel. No, there may be frames that are sent using one or more channels. There may be PPDU or frames that are sent or received only if NPCA is being performed. . Even if there are PPDU or frames sent or received, only if NPCA is not performed. There may be PPDUs or frames that are sent or received both when NPCA is performed and when NPCA is not performed. For example, a given frame or PPDU may not be sent when NPCA is performed. A given frame or PPDU may not be sent when NPCA is not performed. If not, it may be sent. The specified frame or PPDU is if NPCA is being performed. It may be sent in both cases, and if NPCA is not being performed. Only on the Operation channel. There may be frames or PPDUs that are transmitted. There may be frames or PPDUs that are transmitted only on the NCPA Operating channel. Both the Operating channel and the NCPA Operating channel. There may be frames or PPDUs transmitted on the other side. For example, a Beacon may be transmitted in the Operating channel. For example, a Beacon may not be transmitted in the NPCA Operating channel. The NPCA operating channel may be a channel within the operating channel.

[0166] The NPCA operating channel is used by the STA and / or AP to transmit and / or This may be a channel for receiving and / or carrier sensing. The NPCA operating channel bandwidth is the channel through which the STA and / or AP transmit and / or receive in the NPCA. This may also be the bandwidth of the channel on which carrier sensing is performed. For example, in Figure 13, the NPCA operating channels may be 1305, 1306, 1307, and 1308. In Figure 13, the NPCA operating channel bandwidth is 80 MHz. It is also possible that the NPCA primary channel is 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 40MHz 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. For example, in Figure 13, 1305 and 1306 or A primary 40MHz channel may be configured. The primary 80MHz channel is a channel within the NPCA operating channel and may be a 40MHz channel that includes the primary channel but does not include the primary channel. The NPCA operating channel width may have a smaller bandwidth than the operating channel width.

[0167] Figure 13 shows an example of a backoff procedure on an 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 show 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 the STA or This could be a frame received by the AP or a frame transmitted by another STA or AP. 1309 could also be a frame belonging to an OBSS received by the STA or AP or a frame transmitted by another 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 OBSS. 1310 may be while the primary channel is busy. 1310 may be during the period when NAV is set (maintained). This is also acceptable. 1311 may be carrier sense (backoff counter, contention window, DCF, EDCA). 1312 may be transmission of PPDU. For example, if an STA or AP receives 1309 on 1301, it may set 1310 on 1301 for the period indicated in the Duration field of 1309. The STA will then set 1310 on 1301. Then, it is also possible to migrate to 1306. When STA migrates to 1306, 1311 will be used in 1306. You may start. STA may perform 1312 once 1311 is complete. Here, for example If STA performs the operation shown in Figure 13, then STA is 204 in Figure 2, and 1309 is in Figure 2. It may also be a frame transmitted by 207. Figure 13 is a diagram of an AP operating at 160MHz. This is also possible. For example, if the AP performs the operation shown in Figure 13, the AP is performing 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 transmitted using 1308, 130 7, 1306, and 1305 may be used to transmit a channel width of 80 MHz. Here, 1308, 1307, and 1305 may each be NPCA secondary channels. The 80 MHz transmission is on the NPCA primary channel of 1306, 130 Transmission may also be performed using the NPCA secondary 20MHz channel of 5, and the NPCA secondary 40MHz channel consisting of 1307 and 1308. In other words, if the backoff procedure is performed on 1301, 1305, 1306, 1307 and 1308 may be channels that constitute the secondary 80MHz channel. In Non Primary Channel Access, 13 In step 06, when performing the backoff procedure, 1305 may be the NPCA secondary 20MHz channel, and 1307 and 1308 may be channels constituting the NPCA secondary 40MHz 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 constituting the NPCA secondary 40MHz channel, and notify the STA of this in a frame. The AP may notify the STA of 80MHz as the NPCA operating channel width. The AP may 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 notify the STA of the center frequency of the NPCA operating channel. The STA may determine from the frame received from the AP that 1305 in 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.

[0168] STA may generate the PHY-CCA.indication primitive in the physical layer processing unit SU3. STA Even if the PHY-CCA.indication primitive generated by the physical layer processing unit SU3 is shown to the MAC layer processing unit SU4 Good. AP may generate the PHY-CCA.indication primitive in the physical layer processing unit AU3. AP The PHY-CCA.indication primitive generated by the physical layer processing unit AU3 is shown to the MAC layer processing unit AU4. This is also acceptable. The PHY-CCA.indication primitive may include a channel-list parameter. The channel-list parameter may include one entry. One entry is a set of entries. It may be one of the following. A set of entries may be defined. The 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. Furthermore, the PHY-CCA.indication primitive includes a channel-list parameter, the channel-list parameter includes one entry, and the one entry is one of the set of entries. The set of entries includes at least one entry, the first entry which may indicate that the NPCA primary channel is busy.

[0169] For example, the entry set may include NPCA primary and / or NPCA secondary and / or Or it may include NPCA secondary 20 and / or NPCA secondary 40 and / or NPCA secondary 80. That is, NPCA primary and / or NPCA secondary and / or NPCA secondary 20 and / or NPCA secondary 40 and / or NPCA secondary 80 Channel-list parameter entries containing this may be defined. NPCA primary may be the value of entry. NPCA primary indicates the channel state of the NPCA primary channel. It may also be an entry. NPCA primary is when the NPCA primary channel is busy. This may be an entry to indicate. NPCA primary may further indicate that the primary channel is busy. NPCA secondary may be the value of the entry. NPCA secondary `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 also indicate that the NPCA primary channel is idle. `secondary20` may be the value of the entry. `NPCA secondary20` is the channel state of the NPCA secondary 20MHz channel. This may be an entry to indicate the Nell state. NPCA secondary20 is NPCA secondary 20MH This entry may indicate that the z channel is busy. NPCA secondary20 may further indicate that the primary channel is busy. NPCA secondary20 may also indicate that the NPCA primary channel is idle. secondary40 may be the value of the entry. NPCA secondary40 may be an entry indicating the channel state of the NPCA secondary 40MHz channel. NPCA secondary40 indicates that the NPCA secondary 40MHz channel is busy. NPCA secondary40 may also be an entry to indicate that the primary channel is busy. NPCA secondary40 may also indicate that the NPCA primary channel and the NPCA secondary 20MHz channel are idle. secondary80 may be the value of the entry. NPCA secondary80 may be an entry to indicate the channel state of the NPCA secondary 80MHz channel. NPCA secondary80 may also be an entry to indicate that the NPCA secondary 80MHz channel is busy. NPCA secondary80 may also indicate that the primary channel is busy. NPCA secondary80 may indicate the NPCA primary channel, the NPCA secondary 20MHz channel, and the NPCA secondary 40MHz channel You may also indicate that it is 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 secondary 40 and / or NPCA secondary 80 are included. Good. That is, 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 secondary 40 and / Alternatively, channel-list parameter entries containing NPCA secondary80 may be defined. The value of the entry, NPCA primary, may be called secondary primary. A certain NPCA primary may also be called an anchor primary. The value of the entry is the NPCA primary. It may be referred to in ways other than those mentioned above. The NPCA secondary, which is the value of entry, may also be called a secondary secondary. The NPCA secondary, which is the value of entry, may also be called an anchor secondary. It may be referred to in ways other than those mentioned above. The entry value NPCA secondary may be referred to as secondary secondary20. The entry value NPCA secondary20 may be referred to as anchor secondary20. The entry value NPCA secondary20 may be referred to in ways other than those mentioned above. The entry value NPCA secondary40 may be referred to as secondary secondary40. The entry value NPCA secondary40 may be referred to as anchor secondary40. The entry value NPCA secondary40 may be referred to in ways other than those mentioned above. It may also be referred to as follows. The entry value NPCA secondary80 may also be referred to as secondary secondary80. The entry value NPCA secondary80 may also be referred to as anchor secondary80. It is also acceptable for the entry value, NPCA secondary80, to be referred to in ways other than those mentioned above.

[0170] STA or AP emits PHY-CCA indication primitive associated with the NPCA primary channel. It may be done. The PHY-CCA indication primitive associated with the NPCA primary channel is NPCA The PHY (Physical Layer) may issue a MAC to indicate that the primary channel is idle or busy. {NPCA primary} may be a channel-list parameter for the NPCA primary channel. For example, if the NPCA primary channel is idle, the STA or AP may issue a MAC. The physical layer may issue a PHY-CCA.indication primitive with STATUS IDLE and channel-list parameter {NPCA primary}. That is, PHY-CCA.indication(IDLE, {NPCA A primitive named {NPCA primary} 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 with STATUS being BUSY and channel-list parameter being {NPCA primary}. In other words, a PHY-CCA.indication(BUSY, {NPCA primary}) primitive may be issued. The associated PHY-CCA.indication primitive may only be issued when NPCA is performed. Even if the MAC layer receives a PHY-CCA.indication primitive with STATUS IDLE and channel-list parameter {NPCA primary}, it may still determine that the NPCA primary channel is idle. Good. PHY-CCA.in where STATUS is IDLE and channel-list parameter is {NPCA primary}. A MAC layer that receives an indication primitive 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}. If NPCA primary is set in the channel-list parameter, the MAC layer determines that the NPCA primary channel is busy. It can be concluded that this is the case. The MAC layer has NPCA primary set in the channel-list parameter. If this is the case, then the NPCA primary channel and primary channel are determined to be busy. That's good too.

[0171] STA or AP is related to the PHY-CCA indication primitive of the NPCA secondary channel. The following may be issued. A PHY-CCA.indication primitive associated with an NPCA secondary channel may be issued to indicate to the PHY (physical layer) via MAC 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, a 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, a PHY-CCA.indication(BUSY, {NPCA secondary}) primitive may be issued. A PHY-CCA.indication primitive associated with a secondary channel may be issued when NPCA is performed. A PHY-CCA.indication primitive associated with an NPCA secondary channel may be issued when the NPCA primary channel is idle. A PHY-CCA.indication primitive associated with an NPCA secondary channel may be issued when the NPCA primary channel is not busy. The MAC layer that receives a PHY-CCA.indication primitive with STATUS IDLE and channel-list parameter {NPCA secondary} will determine that the NPCA secondary channel is idle. It may be determined that it is idle. The MAC layer that receives a PHY-CCA.indication primitive with STATUS IDLE and channel-list parameter {NPCA secondary} may determine that the NPCA primary channel and NPCA secondary channel are idle. STATUS IDLE, Furthermore, when the MAC layer receives a PHY-CCA.indication primitive whose channel-list parameter is {NPCA secondary}, the NPCA primary channel and NPCA secondary channel are idle. Furthermore, it may be determined that 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. It may be determined that the MAC layer, upon receiving a PHY-CCA.indication primitive with STATUS BUSY and channel-list parameter {NPCA secondary}, has an NPCA primary channel. It is a dollar, and it is determined that the NPCA secondary channel and primary channel are 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 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.

[0172] Table for defining the meaning of the channel-list parameter entry in PHY-CCA.indication The following may be defined: 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 with the NPCA secondary 20MHz channel and primary channel. For example, the meaning of channel-list parameter entry{NPCA secondary40} may indicate that STA is busy with the NPCA secondary 40MHz channel. For example, the meaning of channel-list parameter entry{NPCA secondary40} may indicate that STA is busy with the NPCA secondary 40MHz channel and primary channel. For example, the meaning of channel-list parameter entry{NPCA secondary80} may indicate that STA is busy with the NPCA secondary 80MHz channel. For example, the meaning of channel-list parameter entry{NPCA secondary80} may indicate that STA is busy with the NPCA secondary 80MHz channel and primary channel.

[0173] 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 indicates that the PHY (Physical Layer) has a valid opening of a PPDU containing a valid PHY header. This may indicate to the local MAC entity that the start has been received. The PHY-RXSTART.indication primitive may not be generated until the PHY determines the PPDU format (e.g., VHT PPDU starting with an HT PHY header).

[0174] STA may generate the PHY-RXSTART.indication primitive in the physical layer processing unit SU3. The PHY-RXSTART.indication primitive generated by the physical layer processing unit SU3 is then sent to the MAC layer processing unit SU4. It may be shown. AP generates PHY-RXSTART.indication primitive in the physical layer processing unit AU3. Alternatively, AP may present the PHY-RXSTART.indication primitive generated by the physical layer processing unit AU3 to the MAC layer processing unit AU4.

[0175] The PHY-RXSTART.indication primitive may provide an RXVECTOR. The RXVECTOR is a list of parameters that the PHY provides to the local MAC entity when a valid PHY header is received. It may also be expressed as follows: RXVECTOR may include at least the DATARATE parameter and / or the LENGTH parameter.

[0176] The PHY may provide an interface to the MAC. The MAC may provide an interface to the PHY. This interface may include TXVECTOR and RXVECTOR. The TXVECTOR may be used 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 be one or It may contain multiple parameters.

[0177] The syntax in which a frame, MPDU, or A-MPDU is sent with a certain TXVECTOR parameter or received with a certain RXVECTOR parameter is a frame, MPDU, or The syntax of a PPDU being sent with a certain TXVECTOR parameter or received with a certain RXVECTOR parameter may be understood as referring to the TXVECTOR or RXVECTOR parameter corresponding to each PSDU contained within the PPDU.

[0178] 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 is MCS, CH_BA NDWIDTH and GI_TYPE values ​​may be substituted. Additional parameters related to the HT PHY operating mode 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.

[0179] 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 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. Anything is fine.

[0180] 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. Good. Additional parameters related to the operating mode of HE PHY 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. stomach.

[0181] The FORMAT parameter may be a parameter (value) that determines the format of the PPDU. The NON_HT_MODULATION parameter is a parameter (value) that determines the Enumerated type. You may do so. The NON_HT_MODULATION parameter is the estimated format of the received non-HT PPDU. The L_LENGTH parameter may indicate the type. The L_DATARATE parameter may indicate the length of the PSDU. The L_DATARATE parameter may indicate the rate used to transmit the PDSU. The LSIGVALID parameter may indicate true if L-SIG Parity is enabled, and false if L-SIG Parity is disabled. The RSSI parameter may indicate the PHY measurement of power observed at the antenna connector receiving the current PPDU. The MCS parameter may select the modulation scheme and coding rate used for packet transmission. The CH_BANDWIDTH parameter may indicate the channel width from which the packet was transmitted. Good. The LENGTH parameter may be a parameter (value) indicating 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 is a measure of the received SNR per chain. It is also possible that the SNR parameter is a measure of the received SNR per stream. The STBC parameter is a parameter (value) that indicates the difference between the number of space-time streams and the number of spatial streams. It is also possible that the DELTA_SNR parameter is a parameter (value) that contains an array of delta SNR values ​​based on the channel measured with the training symbol of the received VHT NDP. The NUM_STS parameter is a parameter (value) that indicates the number of space-time streams. The SNR parameter is a parameter (value) that contains an array of received SNR measurements for each spatial stream. The STBC parameter is a parameter (value) that indicates whether STBC is being used. The CH_BANDWIDTH parameter is a parameter (value) that indicates the channel width of the PPDU. The DCM parameter is a parameter (value) that indicates whether DCM is being used for the Date field. The TXOP_DURATION parameter is a parameter (value) that indicates the TXOP duration. The SPATIAL_REUSE parameter is a parameter (value) that indicates the spatial reuse parameter value. The RU_ALLOCATION parameter is a parameter (value) that indicates the RU (Resource Unit) allocated within the bandwidth.

[0182] 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 It may also have parameters such as FORMAT.

[0183] The PHY-RXSTART.indication primitive may be generated for the MAC sublayer from the local PHY entity 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 transfer frames of the indicated length at the indicated data rate. The physical medium busy status is maintained when the PHY-RXEND.indication(CarrierLost) primitive or PHY-RXEND.indication(FormatViolation) primitive is generated at the end of the period. It may be generated or maintained by the PHY before completion. PHY-RXSTART.indication primitive When a MAC entity receives this, the MAC may prepare a new receive flow.

[0184] The PHY-RXEND.indication primitive may be used by the PHY to indicate to the local MAC entity that the currently received PPDU is complete. The PHY-RXEND.indication primitive may include the 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 is used to indicate that the receiving It may be used to indicate that there was an error in the format of the transmitted PPDU. CarrierLost indicates that the carrier was lost during reception of the received PSDU and the PSDU cannot be processed any further. It may be used to indicate. UnsupportedRate is used when receiving an incoming PPDU, if it is not supported. It may be used to indicate that a data rate that is not being received has been detected. Filtered may be used to indicate that the PPDU was filtered during PPDU reception according to the conditions set in PHYCONFIG_VECTOR.

[0185] The STA or AP may issue a PHY-RXSTART.indication primitive when it receives a duplicate PPDU on the primary channel. The STA's PHY or the AP's PHY may issue a PHY-RXSTART.indication primitive when it receives a duplicate PPDU on the primary channel. Alternatively, the AP does not need to issue a PHY-RXSTART.indication primitive for PPDUs that do not overlap with the primary channel. The STA's PHY or the AP's PHY does not overlap with the primary channel. For PPDUs that do not have a PHY-RXSTART.indication primitive, it is not necessary to issue one. 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.

[0186] 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 and 1202, and both 1203 and 1204. In other words, STA Alternatively, the AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU transmitted using 1201. For example, the 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, the STA or AP does not need to issue a PHY-RXSTART.indication primitive when it receives a PPDU transmitted using only 1202. For example, the STA or AP does not need to issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with 1201. When receiving a PPDU sent using 204, it is not necessary to issue the PHY-RXSTART.indication primitive. In other words, the STA or AP does not need to issue 1201 when receiving a PPDU sent without using 1201. When a signal is received, it is not necessary to issue the PHY-RXSTART.indication primitive.

[0187] Unless the AP's PHY receives a requested TB PPDU from the AP, the PHY does not need to issue a PHY-RXSTART.indication primitive for PPDUs that do not overlap with the primary channel. In response to a requested TB PPDU, 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.

[0188] Even if the AP requests one or more STAs to send a Trigger Based (TB) PPDU, Good. The AP will send a TB PPDU to one or more STAs 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 TB PPDUs based on the information contained in the received trigger frame. The trigger frame enables UL MU (Multi-User) transmission by the AP. It may be used for that purpose. The trigger frame may be used for OFDMA transmission. The TB PPDU may be a PPDU. The TB PPDU may be referred to as a PPDU.

[0189] In Figure 12, for example, AP will not receive 1201 unless it receives the TB PPDU that AP requested. It is not necessary to issue a PHY-RXSTART.indication primitive for non-duplicate PPDUs. For example, an AP may receive a TB PPDU requested by the AP and issue a PHY-RXSTART.indication primitive for any PPDU that does not overlap with 1201. For example, the AP may send a TB PPDU to the STA as 1202. To assign, the AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU from the STA using 1202. For example, the AP assigns the TB PPDU to the STA using 1203 and 1204. In that case, when the AP receives a PPDU from the STA using 1203 and 1204, it may issue the PHY-RXSTART.indication primitive. For example, the AP sends a TB PPDU to the STA using 1205 and Assigned to 1206, 1207, and 1208, AP is from STA to 1205 and 120 When a PPDU using 6, 1207, and 1208 is received, the PHY-RXSTART.indication primitive may be issued. The PPDU transmitted by the STA may also be a TB PPDU.

[0190] 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 primitive 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 This may be issued after decoding (receiving) the L-SIG. For example, the PHY-RXEARLYSIG.indication primitive may be issued after decoding (receiving) the L-SIG and / or the RL-SIG. Yes. 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. The 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.

[0191] The STA or AP does not need to issue the PHY-RXSTART.indication primitive for PPDUs that do not overlap with the primary channel and / or NPCA primary channel. When the STA or AP receives a PPDU that overlaps with the NPCA primary channel, it does not issue the PHY-RXSTART.indication primitive. It may be issued. In NPCA, the 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, the 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. Upon receiving, the PHY-RXSTART.indication primitive may be issued. In NPCA, STA is If a PPDU that does not overlap with the NPCA primary channel is received, the PHY-RXSTART.indication primitive does not need to be issued. In NPCA, the AP does not need to issue the PHY-RXSTART.indication primitive if 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. The 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] In response to a PPDU requested by an AP, the AP may issue a PHY-RXSTART.indication primitive upon receiving the PPDU on the NPCA primary channel. The AP may issue a PHY-RXSTART.indication primitive for the PPDU that does not overlap with the primary channel or NPCA primary channel. The AP does not have to issue a PHY-RXSTART.indication primitive for the PPDU that does not overlap with the primary channel or NPCA primary channel. For PPDUs requested by the AP, the AP The AP may issue a PHY-RXSTART.indication primitive when it receives the PPDU on the NPCA primary channel, NPCA secondary 20MHz channel, NPCA secondary 40MHz channel, or NPCA secondary 80MHz channel. The AP may assign the PPDU to the STA, and when it receives the PPDU assigned to the STA 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, the AP may issue a PHY-RXSTART.indication primitive when it receives the PPDU requested by the AP on the NPCA primary channel, NPCA secondary 20MHz channel, NPCA secondary 40MHz channel, or NPCA secondary 80MHz channel. In other words, in NPCA, the AP assigns the PPDU to the STA. The PPDU assigned to the STA is then received on the NPCA primary channel, NPCA secondary 20MHz channel, NPCA secondary 40MHz channel, or NPCA secondary 80MHz channel. In this case, the PHY-RXSTART.indication primitive may be issued. In NPCA, the AP issues the PHY-RXSTART.indication primitive to the PPDU that does not overlap with the primary channel. In NPCA, AP may overlap with the primary channel or NPCA primary channel. It is not necessary to issue a PHY-RXSTART.indication primitive for a PPDU that does not exist. In NPCA, if the AP receives a PPDU that is requested by the AP and does not overlap with the NPCA primary channel, the AP may issue a PHY-RXSTART.indication primitive. In NPCA, if the AP does not receive a PPDU that is not requested by the AP, the AP does not need to issue a PHY-RXSTART.indication primitive for a PPDU that does 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. The STA's PHY may issue a PHY-RXSTART.indication primitive. The AP's PHY may issue a PHY-RXSTART.indication primitive.

[0193] 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.

[0194] 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. This is also acceptable. 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, and DATA. DATA is, The SERVICE field may consist of PSDU, Tail, and Pad Bits. SIGNAL is RATE. The PHY Header may consist of the following fields: Reserved, LENGTH, Parity, and Tail. The PHY Header may consist of the RATE, Reserved, LENGTH, Parity, Tail, and SERVICE fields. The non-HT PPDU format may consist of the L-STF, L-LTF, L-SIG, and Data fields. The Data field may consist of the SERVICE and Scrambled PSDU fields. It may consist of a field, a Tail bits field, and a Pad bits field. HT PPDU The format may consist of an L-STF field, an L-LTF field, an L-SIG field, an HT-SIG field, an HT-STF field, an HT-LTF field, and a Data field. The HT PPDU format may consist of an HT GF STF field, an HT LTF1 field, an HT-SIG field, an HT-STF field, an HT-LTF field, and a Data field. The VHT PPDU format may consist of an L-STF field, an L-LTF field, an L-SIG field, a VHT-SIG-A field, a VHT-STF field, a VHT-LTF field, a VHT-SIG-B field, and a Data field.

[0195] 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 the Non-HT Duplicate field may be 104. At 80MHz, the number of tones in the L-STF field may be 48, and the number of tones in the L-LTF field may be 52. The number is 208, the number of tones in the L-SIG field is 208, and the number of tones in NON_HT_DUP_OFDM-Date is 20 It may also be 8. At 160MHz, the number of tones in the L-STF field is 96, the number of tones in the L-LTF field is 416, the number of tones in the L-SIG field is 416, and the number of tones in NON_HT_DUP_OFDM-Date is... It may also be 416.

[0196] HE PPDU may also be called HE TB PPDU. HE TB PPDU may also be called HE PPDU. PPDU 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, and a PE field. Lud, L-SIG field, RL-SIG field, HE-SIG-A field, HE-SIG-B field It may consist of 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, and an L-SIG field. The HE TB PPDU format may consist of L-STF field, L-LTF field, L-SIG field, RL-SIG-A field, HE-STF field, HE-LTF field, Data field, and PE field. The HE TB PPDU format may consist of L-STF field, L-LTF field, L-SIG field, RL-SIG field, HE-SIG-A field, HE-STF field, HE-LTF field, Data field, and PE field. HE ER SU PPDU (High-Efficiency Extended Range Single User PPDU) is HE ER SU PPDU is a PPDU transmitted in PPDU format and may be a PPDU that transmits a single PSDU. HE SU PPDU (High-Efficiency Single User PPDU) is transmitted in HE SU PPDU format. It is a PPDU, and may be a PPDU that transmits a single PSDU. HE TB PPDU (High-Efficiency Trigger Based PPDU) is a PPDU that is transmitted in HE TB PPDU format, and may be a PPDU that transmits a single PSDU. It may be a PPDU to be transmitted. HE MU PPDU (High-Efficiency Multi-User PPDU) may be a PPDU transmitted in HE MU PPDU format.

[0197] 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 is an EHT PPDU format used for transmissions that are not responses to a trigger frame. t may also be used. EHT MU PPDU may transmit one or more PSDUs. EHT TB PPDU may be an EHT PPDU format used to transmit a response to a trigger frame. EHT TB PPDU may transmit one PSDU. EHT MU PPDU format may include L-STF field, L-LTF field, L-SIG field, RL-SIG field, U-SIG field, EHT-SIG field It may consist of 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, and an L-SIG field. It may consist of a RD, RL-SIG field, U-SIG field, EHT-STF field, EHT-LTF field, Data field, and PE field.

[0198] 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 is a transmission that is not a response to a trigger frame using the UHR PPDU format. A PPDU may be used for the following: A UHR MU PPDU may transmit one or more PSDUs. A UHR TB PPDU may be a PPDU used to transmit a response 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 have an L-STF field, an L-LTF field, an L-SIG field, an RL-SIG field, a U-SIG field, and a UHR-SIG field. The UHR MU PPDU format may consist of fields other than those mentioned above. For example, the UHR TB PPDU format may consist of fields such as L-STF, L-LTF, and L-SIG. RL-SIG field, U-SIG field, UHR-STF field, UHR-LTF field, Data It may consist of 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 It may also be HT PPDU. The UHR PPDU format may contain the same fields as the HT PPDU format. UHR PPDU may also be called VHT PPDU. UHR PPDU may also be 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 also be HE PPDU. UHR PPDU format It may contain the same fields as the HE PPDU format. UHR PPDU may be called EHT PPDU. UHR PPDU may be EHT PPDU. UHR PPDU format may contain the same fields as the EHT PPDU format.

[0199] 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 to 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 also be a PHY transmission format that duplicates 20MHz non-HT transmission using two adjacent 20MHz channels. 80MHz non-HT Duplicate may be a PHY transmission format that duplicates 20MHz non-HT transmission on four adjacent 20MHz channels. 160MHz non-HT duplicate may be a PHY transmission format that duplicates 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 is a PHY transmission format that duplicates a 20MHz non-HT transmission on sixteen adjacent 20MHz channels. That's fine.

[0200] non-HT duplicate frame is non-HT of physical layer (PHY) protocol date unit (PPDU) The frame may also be transmitted as a duplicate. A non-HT PPDU (non-high throughput physical layer protocol date unit) is a PPDU transmitted from the PHY, and is in the TXVECOTR FORMAT. The parameters may be values ​​other than those specified. For example, a non-HT PPDU is a PPDU sent from the PHY where the TXVECOTR FORMAT parameter is either HT_MF, HT_GF, or VHT. It is not necessary for the parameters to be equal to the specified values. For example, a non-HT PPDU may be a PPDU sent from a DSSS PHY, HR / DSSS PHY, OFDM PHY, or ERP PHY, where the TXVECTOR 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 where the TXVECTOR FORMAT parameter is NON_HT and the CH_BANDWIDTH parameter is NON_HT_CBW40, CBW40, CBW80, CBW160, or CBW80+80, or CBW320. For example, a non-HT duplicate PPDU may be a PPDU where the TXVECTOR FORMAT parameter is NON_HT, CH_BANDWIDTH The parameters may be NON_HT_CBW40, CBW40, CBW80, CBW160, CBW80+80, or CBW320, and the PPDU may be sent from an HT PHY or VHT PHY.

[0201] The AP may send a Trigger frame. For example, the Trigger frame may be in the Control frame. It is acceptable. For example, a trigger frame may be one where the Type subfield of the Frame Control field in the MAC header indicates Control and the subtype subfield indicates Trigger. 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. The STA may send a trigger frame. The trigger frame is a Date frame. This is also acceptable. The trigger frame may be a management frame.

[0202] A trigger frame allocates resources for one or more TB PPDU transmissions and requests A trigger frame may also solicit resources. The trigger frame may also transmit other information necessary for the responding STA to send 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. The trigger frame contains the Frame Control field, Duration field, RA field, TA field, Common Info field, and User Info List field. It may consist of a padding field, an FCS field, etc. Common Info field The data includes the HE variant Common Info field, the EHT variant Common Info field, and the UHR The variant Common Info field may also be used. The Common Info field is a Trigger field. It may include subfields such as Type subfield, UL BW subfield, and CS Required subfield.

[0203] In MU-RTS Trigger frames, the Duration / ID field indicates the pending frame being sent. The estimated time required (in microseconds), one CTS frame, and the requested TB if necessary. The time to send the PPDU, the time to send an acknowledgment for the requested TB PPDU if necessary, and the applicable IFS may be set. In the 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 if necessary, and the applicable IFS. It may be configured to include a SIFS that can be used.

[0204] The Duration / ID field of the CTS frame sent in response to the MU-RTS Trigger frame is derived from the Duration / ID field of the MU-RTS Trigger frame that triggered the CTS frame. The difference in time (in microseconds) between the end of the PPDU containing the frame and the end of the PPDU containing the CTS frame. It may be set to the value after subtracting the value.

[0205] If the CTS frame is a response to the RTS frame, the RA field of the CTS frame may be set to the address of the TA field of the RTS frame, where Individual / Group is set to 0. If the frame is the first frame in the frame exchange, the RA field contains the sender's MAC address. A dress may be set if the CTS frame is a response to the MU-RTS Trigger frame. The RA field of the CTS frame is set to the address of the TA field of the MU-RTS Trigger frame. It may also be used.

[0206] 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 is a single PSDU (Physical Layer Service Date Unit). They may be transmitted. For example, MU PPDU (Multi-User PPDU) may be used to transmit one or more PSDSs.

[0207] 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. This is also acceptable. If the value of the Trigger Type subfield is 2, the Trigger frame variant may be MU-BAR. In other words, if the value of the Trigger Type subfield is 2, the Trigger frame format may be MU-BAR Trigger frame format. In this case, the Trigger frame variant may be MU-RTS. That is, if the value of the Trigger Type subfield is 3, the Trigger frame format is MU-RTS. It is also acceptable. If the value of the Trigger Type subfield is 4, the Trigger frame variant is Buffer It could also be a Status Report Poll (BSRP). In other words, the value of the Trigger Type subfield. If the value is 1, the Trigger frame format may be the BSRP Trigger frame format.

[0208] 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.

[0209] 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. The UL BW subfield in the HE variant 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. The UL BW subfield in the EHT variant 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 is 40MHz. It may also be the case that when the UL BW subfield is 2 and the UL BW Extension subfield is 0, the bandwidth of the EHT TB PPDU may be 80MHz. When the UL BW subfield is 3 and the UL BW Extension subfield is 1, the bandwidth of the EHT TB PPDU may be 160MHz. When the BW Extension subfield is 2, the bandwidth of the EHT TB PPDU may be 320MHz. When the UL BW subfield is 3 and the UL BW Extension subfield is 3, the bandwidth of the EHT TB PPDU may be 320MHz. The UL BW Extension subfield is the UL Bandwidth Extension subfield. It may also be referred to as eld. The UL Bandwidth Extension subfield, along with the UL BW subfield in the Common Info field, may indicate the bandwidth of the requested TB PPDU.

[0210] 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 the HE variant User Info field. The User Info field may also be the EHT variant User Info field. The HE variant User Info field may also be the User Info field. The EHT variant User Info field may also be the User Info field. The HE variant User Info field may also be referred to as the User Info field. The EHT variant User Info field may also be referred to as the User Info field.

[0211] 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 from 1 to 2007, the User Info field may assign associated AIDs equal to the value of the AID12 subfield. It may be addressed to the STA. For example, if the AID12 subfield is from 2008 to 2044, Reserved This may also be the case. For example, if the AID12 subfield is 2045, the User Info field is associated with One or more consecutive RA-RUs may be assigned to an STA that has not been reserved. For example, if the AID12 subfield is 2046, it may be an Unallocated RU. For example, if the AID12 subfield is between 2047 and 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 Disallowed in the User Info field to indicate the start of a Padding field.

[0212] 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 will be set to 0 if the RU Allocation is primary 80 MHz. It may be set to 0 to indicate that it applies to the channel, and to 1 to indicate that 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 RUs to the RU index may be defined in a Table. If the UL BW subfield indicates 40MHz, the mapping of RUs 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 is a Table in which the B7-B1 mapping of the RU Allocation subfield for a Trigger frame that is not a MU-RTS Trigger frame is defined. It is also acceptable. Figure 15 shows the mapping of RU to the RU index when the UL BW subfield is 20 MHz. It may also be a Table with a defined group.

[0213] Figure 14 shows an example of the size and arrangement of RUs using an RU Allocation subfield and an UL BW subfield according to one aspect of this embodiment. The B7-B1 mapping of the RU Allocation subfield is The RU size and RU index may be determined from a defined table. For example, B7-B1 of the RU Allocation subfield may indicate 0, and the UL BW subfield may indicate 20MHz, 40MHz, 80MHz, 80+80MHz, or If the frequency is 160MHz, the RU size may be 26, and the RU index may be RU1. Here, the 0 to 8 in B7-B1 of the RU Allocation subfield correspond to RU1 to RU9 in the RU index, respectively. I can accommodate that. In other words, if B7-B1 of the RU Allocation subfield is 0, it corresponds to RU1, and if it is 1, it corresponds to RU2. It corresponds to RU3 in case 2, RU4 in case 3, and RU5 in case 4. If it's 5, it corresponds to RU6; if it's 6, it corresponds to RU7; if it's 7, it corresponds to RU8; and if it's 8... In this case, it may also correspond to RU9.

[0214] Figure 14 shows an example of the size and arrangement of RUs using an RU Allocation subfield and an UL BW subfield according to one aspect of this embodiment. The B7-B1 mapping of the RU Allocation subfield is The RU size and RU index may be determined from a defined table. For example, B7-B1 of the RU Allocation subfield may indicate 0, and the UL BW subfield may indicate 20MHz, 40MHz, 80MHz, 80+80MHz, or If the frequency is 160MHz, the RU size may be 26, and the RU index may be RU1. Here, the 0 to 8 in B7-B1 of the RU Allocation subfield correspond to RU1 to RU9 in the RU index, respectively. I can accommodate that. In other words, if B7-B1 of the RU Allocation subfield is 0, it corresponds to RU1, and if it is 1, it corresponds to RU2. In the case of 2, it corresponds to RU3, in the case of 3, it corresponds to RU4, in the case of 4, it corresponds to RU5, in the case of 5, it corresponds to RU6, in the case of 6, it corresponds to RU7, in the case of 7, it corresponds to RU8, and in the case of 8 In this case, it may also correspond to RU9.

[0215] Figure 15 shows an example of a table defining the mapping between RU index and RU when the UL BW subfield is 20 MHz according to one aspect of this embodiment. For example, RU type is 26-tone RU Furthermore, in the case of RU1, 26 tones with subcarrier indices from -121 to -96 are used for PPDU transmission. It may be used. 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, the subcarrier index is -122 to -2, and Furthermore, 242-tones from 2 to 122 may be used for PPDU transmission. Subcarrier index 0 may correspond to a DC tone. In Figure 14, when 61 is shown in the RU Allocation subfield and 20MHz in the UL BW subfield, the RU size corresponds to 242 and the RU index corresponds to RU1. In Figure 15, when 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.

[0216] 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 of a Trigger frame that is not a MU-RTS Trigger frame may be defined in a Table. If the UL BW subfield indicates 20MHz, the mapping of RUs to the RU index may be defined in a Table. If the UL BW subfield indicates 40MHz, the mapping of RUs 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.

[0217] RU in the User Info field of a trigger frame that is not a MU-RTS trigger frame, which is an EHT variant. The Allocation subfield may identify the size and location of the RU or MRU, along with the UL BW subfield in the Common Info field, the UL BW Extension subfield in the Special User Info field, and the PS160 subfield in 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 in 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.

[0218] RU size may be the number of tones. A tone may be a subcarrier. Number of tones This 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 is Other values ​​are also acceptable. For example, the subcarrier spacing of a non-HT PPDU may be 78.125 kHz. For example, the subcarrier spacing of an HT PPDU may be 78.125 kHz. For example, the subcarrier spacing of a VHT PPDU may be 78.125 kHz. For example, the subcarrier spacing of an HE PPDU may be 78.125 kHz. For example, the subcarrier spacing of an EHT PPDU is It may also be 78.125 kHz. For example, the subcarrier spacing of a UHR PPDU may be 78.125 kHz. For example, the subcarrier spacing of a non-HT PPDU may be 312.5 kHz. For example, the subcarrier spacing of the HT PPDU may be 312.5 kHz. The carrier interval may be 312.5 kHz. For example, the subcarrier interval of HE PPDU may be 312.5 kHz. For example, the subcarrier interval of EHT PPDU may be 312.5 kHz. For example, the subcarrier spacing for a UHR PPDU may be 312.5 kHz. Different subcarrier spacings may be used for each PPDU. For example, the subcarrier spacing for non-HT PPDU, HT PPDU, and VHT PPDU may be 78.125 kHz, while the subcarrier spacing for HE PPDU, EHT PPDU, and UHR PPDU may be 312.5 kHz.

[0219] 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).

[0220] 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 20MHz channel, primary 40MHz channel, and 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, and primary 80MHz channel. When indicating primary 160MHz, 80+80MHz, and 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 to 0 to indicate the primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, and primary 160MHz channel. .

[0221] 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). Example For example, the first bit of the RU Allocation subfield (the leading bit, most significant bit, MSB: Most Significant Bit) may be B0. The second bit of the RU Allocation subfield may be B1. Good. The 3rd bit of the RU Allocation subfield may be B2. The 4th bit of the RU Allocation subfield may be B3. The 5th bit of the RU Allocation subfield may be B4. The 6th bit of the RU Allocation subfield may be B5. The 7th bit of the RU Allocation subfield may be B6. The 8th bit of the RU Allocation subfield (the last bit, least significant bit, LSB: Last Significant Bit) may be B7. For example, the 1st bit of the RU Allocation subfield (the leading bit, most significant bit, MSB: Most Significant Bit) may be B7. The 2nd bit of the RU Allocation subfield may be B6. The 3rd bit of the RU Allocation subfield may be B5. The 4th bit of the RU Allocation subfield may be B4. The 5th bit of the RU Allocation subfield may be B3. The 6th bit of the RU Allocation subfield may be B2. The 7th bit of the RU Allocation subfield may be B1. The 8th bit of the RU Allocation subfield (the last bit, least significant bit, LSB: Last Significant Bit) may be B0. The correspondence between the RU Allocation subfield and B0-B7 may be other than those described above.

[0222] The RU Allocation subfield B7-B1 (B7 to B1) 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 among the primary 40MHz channel or primary 80MHz channel, then 61. ― If the primary 20MHz channel is the second lowest frequency 20MHz channel in the primary 40MHz channel or primary 80MHz channel, then 62. ― If the primary 20MHz channel is the third lowest frequency 20MHz channel in the primary 80MHz channel, then 63. ― If the primary 20MHz channel is the fourth lowest frequency 20MHz channel in the primary 80MHz channel, then 64.

[0223] When AP requests STA to transmit CTS in response to MU-RTS, in the MU-RTS RU allocation subfield, 61, 62, 63, to request STA to transmit CTS on the primary 20MHz channel, Alternatively, it may indicate 64. STA is the RU allocation subfield of the MU-RTS transmitted from AP. If 61, 62, 63, or 64 is indicated, CTS may be transmitted on the primary 20MHz channel. If the primary 20MHz channel is the only 20MHz channel, RU The allocation subfield may be set to 61. The only 20MHz channel may be when the operating channel width is 20MHz. The only 20MHz channel may be when the MU-RTS channel width is 20MHz. If the primary 20MHz channel is the lowest frequency 20MHz channel among the primary 40MHz channels, the RU allocation subfield is set to 61. This is also possible. 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, In addition, 61 may be set in the RU allocation subfield. The primary 20MHz channel is primary If the 40MHz channel is the second lowest frequency 20MHz 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. It may be determined that the primary 20MHz channel is the second most frequent channel in the primary 160MHz channel. For low frequency 20MHz channels, 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, In addition, 63 may be set in the RU allocation subfield. The primary 20MHz channel is primary In the case of the 80MHz channel, if it is the 20MHz channel, which is the fourth lowest frequency, RU allocation The 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. It may be set. A value other than those mentioned above may be set in the RU allocation subfield to indicate the primary 20MHz channel.

[0224] The RU Allocation subfield B7-B1 (B7 to B1) 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, then 65. ― If the primary 40MHz channel is the second lowest frequency in the primary 80MHz channel, then 66.

[0225] When the AP requests the STA to transmit a CTS in response to the MU-RTS, it requests the STA to transmit the CTS on the primary 40MHz channel by specifying 65 or 66 in the RU allocation subfield of the MU-RTS. It may be shown. STA is the RU allocation subfield of the MU-RTS transmitted from AP, 65 or 6 If 6 is indicated, CTS may be transmitted on the primary 40MHz channel. If the primary 40MHz channel is the only 40MHz channel, the RU allocation subfield may be set to 65. The primary 40MHz channel is the lowest frequency 40MHz channel on the primary 80MHz channel. In some cases, 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. This may be set. The primary 40MHz channel is the second primary 160MHz channel. Even if the RU allocation subfield is set to 66, if the frequency is a low 40MHz channel... Good. If the primary 40MHz channel is the third lowest frequency 40MHz channel in the primary 160MHz channel, a predetermined value may be set in 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 in the RU allocation subfield. A value other than those mentioned above may be set in the RU allocation subfield to indicate the primary 40MHz channel.

[0226] 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). It may be done. B7-B1 of the RU Allocation subfield is the PPDU that transmits the MU-RTS Trigger frame. If the bandwidth of the PPDU transmitting the MU-RTS Trigger frame is less than 320MHz, it may be set to 68 to indicate the primary 80MHz channel and the secondary 80MHz channel, or if the bandwidth of the PPDU transmitting the MU-RTS Trigger frame is 320MHz, it may be set to indicate the primary 160MHz channel. B7-B1 of the RU Allocation subfield may be set to 68 to indicate the primary 80MHz channel and the secondary 80MHz channel if the bandwidth of the PPDU transmitting the MU-RTS Trigger frame is less than 320MHz. B7-B1 of the RU Allocation subfield may be set to 68 to indicate the primary 160MHz channel if the bandwidth of the PPDU transmitting the MU-RTS Trigger frame is 320MHz. B7-B1 of the RU Allocation subfield may be set to 69 to indicate the 320MHz channel.

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

[0228] When AP requests STA to transmit CTS in response to MU-RTS, AP may indicate 68 in the RU allocation subfield of MU-RTS to request STA to transmit CTS on the primary 160MHz channel. If 68 is indicated in the RU allocation subfield of MU-RTS transmitted from AP, STA will respond. The AP may transmit a CTS on the primary 160MHz channel. When the AP requests the STA to transmit a CTS in response to the 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. The STA may transmit a CTS on the primary 80MHz channel and the secondary 80MHz channel if it has received a 68 in the RU allocation subfield of the MU-RTS transmitted from the AP. primary 80MHz CTS transmission on the main channel and secondary 80MHz channel may also be transmitted on the 80+80MHz channel.

[0229] If the AP requests the STA to transmit a CTS in response to the MU-RTS, it will instruct the STA to transmit on the 320MHz channel. To request a CTS transmission, the RU allocation subfield of the MU-RTS may indicate 69. If the RU allocation subfield of the MU-RTS transmitted from the AP indicates 69, the STA will transmit at 320MHz. You may also send CTS via channel.

[0230] 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 settings for B7-B1 of the RU Allocation subfield. 1601, 1602, 1603, 1604, 1605, 1606, 1607, and 1608 may be 20MHz channels. 09, 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 also be indicated as 80 MHz in the UL BW subfield. 1612 may be the case where 160MHz or 80+80MHz is indicated in the UL BW subfield. 1613 may be the case where B0 in the RU Allocation subfield is 0. 1614 is RU The Allocation subfield B0 may also indicate 1. 1615, 1616, 1617, 1618, 1619, 1620, 1621, and 1622 are CTS frames sent. These may be the channels that are designated as such. Any of 1615, 1616, 1617, 1618, 1619, 1620, 1621, or 1622 may be indicated in the RU Allocation subfield. 1615, 1616, 1617, or 1618 may be the 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 indicated in the RU Allocation subfield, the STA may transmit the CTS using the primary 20MHz channel. RU Allocation If a predetermined value (e.g., 65 or 66) is indicated in the 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 specific value (e.g., 68) is indicated in the RU Allocation subfield, then STA The CTS may be transmitted 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 given value may be 61. If the primary 20MHz channel is the second lowest frequency among the primary 40MHz channel or primary 80MHz channel, the given 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 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, AP transmits a MU-RTS Trigger frame with one of the bandwidths 1609, 1610, 1611, or 1612, and indicates 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 transmits a CTS on the indicated channel. You can believe it.

[0231] Figure 17 shows an example of B7-B1 of the RU Allocation subfield for MU-RTS Trigger frames of various bandwidths according to one aspect of this embodiment. 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 of various bandwidths. 170 1, 1702, 1703, 1704, 1705, 1706, 1707, 1708, 170 9, 1710, 1711, 1712, 1713, 1714, 1715, 1716 may be 20MHz channels. 1717, 1718, 1719, 1720, 1721 are The bandwidth of the PPDU carrying the MU-RTS trigger frame may also be 1717, 1718. 1719, 1720, and 1721 may be values ​​shown using the UL BW subfield and UL BW Extension subfield (if present). 1717 is the value shown when 20MHz is indicated using the UL BW subfield and UL BW Extension subfield (if present). It is also possible that 1718 may indicate 40MHz using the UL BW subfield and the UL BW Extension subfield (if present). 1719 may indicate UL BW subfield and If 80MHz is indicated using the UL BW Extension subfield (if present) It is also possible that 1720 indicates the primary 160MHz channel or 80+80MHz using the UL BW subfield and UL BW Extension subfield (if present). 1721 may indicate 320MHz using the UL BW subfield and UL BW Extension subfield (if present). 1722 may indicate that B0 in the RU Allocation subfield is 0. 1723 may indicate that B0 in the RU Allocation subfield is 1. 1724 may indicate that PS160 is 0. 1725 may indicate that PS160 is 0. 1726, 1727, 1728, 1729, 1730, 1731, 1732, 1733, 1734 are the channels on which the CTS frame is transmitted. It is also possible that any of 1726, 1727, 1728, 1729, 1730, 1731, 1732, 1733, or 1734 is indicated in the RU Allocation subfield. 1726, 1727, 1728, and 1729 may be primary 20MHz channels. 1730, 1731 may be the primary 40MHz channel. 1732 may be the primary 80MHz channel. 1733 may be the primary 160MHz channel or 80+80MHz. 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 value (e.g., 65 or 66) is indicated, 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, In addition, 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 69) is indicated, 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 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 If it is a number, the given value may be 63. If the primary 20MHz channel is the fourth lowest frequency in the primary 80MHz channel, the given value may be 64. If the primary 40MHz channel is the only 40MHz channel, or primary In the case of the lowest frequency channel, 40MHz, within the 80MHz channel, the given value is 65. It may exist. The primary 40MHz channel is the second lowest in the primary 80MHz channel. If it is a frequency, the given value may be 66. For example, AP transmits MU-RTS trigger frames with one of the bandwidths of 1717, 1718, 1719, 1720, or 1721. And, for each of one or more STAs, in the RU Allocation subfield 1726, 1727 The channel may be one of the following: 1728, 1729, 1730, 1731, 1732, 1733, or 1734, and each STA may transmit a CTS on the indicated channel.

[0232] The MU-RTS Trigger / CTS frame exchange procedure involves the AP (Application Processor) receiving the TXOP (Transaction Operated by the Trigger Operator). It may be possible to initiate and protect TXOP frame exchanges. AP It sends a MU-RTS Trigger frame and simultaneously requests a CTS frame response from one or more STAs. That's good too.

[0233] Figure 18 is a diagram showing an example of the exchange of MU-RTS and simultaneous CTS response according to one aspect of this embodiment. Figure 18 may be an example of NAV setting for MU-RTS and / or CTS. 1801 may be AP operation (receive, transmit, etc.). 1802 is STA#1 operation (receive, transmit). (etc.) may also be the operation of STA#2 (receiving, transmitting, etc.). 1803 may also be the operation of STA#2 (receiving, transmitting, etc.). 1804 refers to the operation (receiving, transmitting, etc.) of one or more STAs other than STA#1 and STA#2. 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 sends to the AP after receiving 1808. i. 1810 may also be a PPDU that STA#2 sends to AP after receiving 1808. For example , 1809 may be a TB PPDU for AP. For example, 1810 may be a TB PPDU for AP. For example, 1809 is an acknowledgment for AP It may also include a TB PPDU. For example, 1810 may include a TB PPDU containing an acknowledgment to the AP. 1811 is a TB PPDU other than STA#1 and STA#2 that received 1805. 1803 may be a NAV maintained by STA#1 or STA#2. 1812 may be a NAV maintained by an STA other than STA#1 or STA#2 that received 1806 or 1807. For example, 1801 may be the operation of 202 in Figure 2 (receive, transmit, etc.). For example, 1802 may be the operation of 203 in Figure 2 (receive, transmit, etc.). For example, 1803 may be the operation of 204 in Figure 2 (receive, transmit, etc.). For example, 1803 may be the operation of 207 in Figure 2 (receive, transmit, etc.).

[0234] In each 20MHz channel occupied by a PPDU containing a MU-RTS Trigger frame, the sender of the MU-RTS Trigger frame sends a CTS frame response to at least one STA occupying the 20MHz channel. You may request a signal. The sender of the MU-RTS Trigger frame may request the STA to send a CTS frame response on a 20MHz channel that is not occupied by the PPDU containing the MU-RTS Trigger frame. This is not required. After sending the 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 sent 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 failed, and if the MU-RTS Trigger frame initiated TXOP, the AP will... The quacking procedure may be initiated. 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. Prior to the PHY-RXEND.indication primitive, the MAC may receive a CTS frame from the STA addressed by the MU-RTS Trigger frame. If a signal is received, the transmission of the MU-RTS Trigger frame is interpreted as successful, and the continuation of the frame exchange sequence may be permitted. If any other type of frame is received, the MU-RTS Trigger This may be interpreted as a failure to send the frame. In this case, the AP processes the received frame and, if the MU-RTS Trigger frame initiated a TXOP, may initiate a 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 performs PIFS recovery. Alternatively, you may perform a backoff procedure.

[0235] When STA receives a MU-RTS Trigger frame, 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 AID12 subfield is Equal to the 12th LSB of the STA's AID, the MU-RTS Trigger frame is transmitted by the AP to which the STA is associated, or the STA is associated with the AP corresponding to a nontransmitted BSSID. The Rx Control Frame To MultiBSS subfield of the HE Capabilities element sent by STA By setting this to 1, if the TA field indicates support for receiving a Control frame set to the transmitted BSSID, the User Info field will be addressed to the STA when sent by the AP corresponding to the transmitted BSSID. — 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.

[0236] The ED-based CCA and virtual CS functions respond to the received trigger frame. If CS is required beforehand, it may be used to determine the medium state. The 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 the medium indication from the physical CS and virtual CS (i.e., the 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 does not need to consider the basic NAV when deciding whether to respond to a trigger frame sent from the AP to which the STA is associated. It is also possible that the STA is configured by the frame transmitted from the AP that sent the trigger frame. Unless otherwise specified, the NAV may be considered when determining whether an STA should respond to a Trigger frame sent by an AP that is not associated with it, via the UORA (UL OFDMA-based Radom Access) procedure. The STA may also consider the intra-BSS NAV associated with the AP when determining whether to respond to a Trigger frame sent by another AP that contains an RU assignment for an unassociated STA. For an STA requested to send by a Trigger frame, if the STA does not consider the NAV, the virtual CS may indicate idle. For an STA requesting transmission, if the NAV counters of all NAVs considered by the STA are 0, the virtual CS may indicate idle. Otherwise, the virtual CS may indicate busy. Good. 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 as a response to the Trigger frame. In this case, the STA uses energy detect after receiving the PPDU containing the Trigger frame (i.e., during the SIFS). It senses medium and detects energy in subchannels including at least the UL assignment of STA. It may be done. The sensed subchannel may consist of one or more 20 MHz channels. Good. STA is idle when the 20MHz channel containing the RU assigned in the trigger frame is idle. If deemed to exist, the requested PPDU may be sent. The STA will send the assigned RU. If it detects that all 20MHz channels, including this one, are not idle, it will not transmit. This is also acceptable. If the trigger frame is a MU-RTS trigger frame, the requested PPDU (solicited PPDU) may be a non-HT PPDU or a non-TH duplicate PPDU. In this case, the requested PPDU (solicited PPDU) may be a TB PPDU. The CS required subfield of the MU-RTS Trigger frame may be set to 1.

[0237] For example, if STA receives a MU-RTS Trigger frame, and several conditions are met, CTS A frame response may be sent. If several conditions are not met, the STA does not need to send a CTS frame response.

[0238] The RU Allocation subfield in the User Info field addressed to STA indicates that the CTS frame response is primary 20MHz. It may indicate whether the transmission is on 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 is non - May be transmitted as HT PPDU or non-HT duplicate PPDU. MU-RTS Trigger frame The CTS frame transmitted in response may be transmitted at a rate of 6 Mb / s using a non-HT PPDU or a non-HT duplicate PPDU, where the TXVECTOR parameter SCRAMBLER_INITIAL_VALUE is 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 using the 20 MHz 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 the CTS frame response to the MU-RTS Trigger frame. When sending a CTS frame response to, the TXVECTOR parameter CH_BANDWIDTH_IN_NON_HT is They do not need to exist. The Power Management subfield and More Data subfield of the CTS frame sent as a response to the MU-RTS Trigger frame may be set to 0.

[0239] The CTS may be sent as a PPDU. For example, the CTS may be sent as a non-HT PPDU. For example, CTS may be transmitted in a non-HT duplicate PPDU. CTS may be transmitted in a PPDU other than the aforementioned PPDU. It may be sent.

[0240] Figure 19 shows the MU-RTS trigger frame in a 40MHz channel according to one aspect of this embodiment. This figure shows an example of simultaneous CTS frame response exchange. 1901 may be an AP operation (transmit, receive, etc.). 1902 is an STA#1 operation ( It may also be (transmit, receive, etc.). 1903 was the operation of STA#2 (transmit, receive, etc.) It is also acceptable. 1904 may be a 40MHz channel. AP, STA#1, and STA#2 are the same channel. It may operate on channel (1904). 1901, 1902, and 1903 may operate on the same channel (1904). 1905 may be on the primary 20MHz channel. i. 1905 may be a common channel for 1901, 1902, and 1903. 1906 may be a MU-RTS Trigger frame sent to STA#1 and STA#2. 1906 may be a MU-RTS Trigger transmitted on the primary 40MHz channel with a 40MHz non-HT duplicate PPDU. It may also be a frame. 1906 indicates CTS transmission on the primary 20MHz channel to STA#1. STA#2 may be instructed to transmit a CTS on the primary 40MHz channel. 1906 requests STA#1 to transmit a CTS frame on the primary 20MHz channel using a non-HT PPDU, and instructs STA2 to transmit a CTS frame on the primary 40MHz channel using a 40MHz non-HT duplicate PPDU. You may request that this be done. 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 on a non-HT PPDU as indicated in MU-RTS. 1908 may be a CTS transmission from STA#2 to AP. 1908 is on the primary 40MHz channel (1904) may be a CTS transmitted in 40MHz non-HT duplicate PPDU. 1908 may be a CTS to AP transmitted in 40MHz non-HT duplicate PPDU as shown in MU-RTS. For example, 1901 may be the operation (receive, transmit, etc.) of 202 in Figure 2. For example, 1902 may be the operation (receive, transmit, etc.) of 203 in Figure 2. For example, 1903 may be the operation (receive, transmit, etc.) of 204 in Figure 2.

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

[0242] STA and / or AP are 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. The following may be transmitted: The 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.

[0243] 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 transmits the Trigger frame in the wireless transmitter / receiver unit AU6. The AP may also transmit a PPDU containing a Trigger frame using the radio transmitter / receiver AU6. The AP may transmit a PPDU containing a Trigger frame containing a RU Allocation subfield using the radio transmitter / receiver AU6. The AP may receive a CTS using the radio transmitter / receiver AU6. The AP may receive a PPDU containing a CTS using the radio transmitter / receiver AU6. The AP may receive a CTS on the channel indicated by the RU Allocation of the Trigger frame using the radio transmitter / receiver AU6. The AP may receive a PPDU containing a CTS on the channel indicated by the RU Allocation of the Trigger frame using the radio transmitter / receiver AU6. The STA receives a Trigger frame using the radio transmitter / receiver SU6. The STA may receive a PPDU containing a Trigger frame with the wireless transmit / receive unit SU6. The STA may receive a PPDU containing a Trigger frame containing an RU Allocation subfield with the wireless transmit / receive unit SU6. The STA determines the RU Allocation subfield of the Trigger frame with the frame processing unit SU7. STA may determine the RU Allocation subfield of the Trigger frame in the MAC layer processing unit SU4. STA may determine the channel to transmit the CTS from the RU Allocation subfield of the Trigger frame in the frame processing unit SU7. 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. STA may transmit the CTS with the wireless transmit / receive unit SU6. STA may transmit a PPDU containing the CTS with the wireless transmit / receive unit SU6. STA may transmit the CTS on the channel indicated by the RU Allocation of the Trigger frame with the wireless transmit / receive unit SU6. Good. The STA may transmit a PPDU including the CTS on the channel indicated by the RU Allocation of the Trigger frame using the wireless transmitter / receiver SU6.

[0244] 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.

[0245] “primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary Indicates whether the transmission is on the 160MHz channel, 80+80MHz channel, 320MHz channel, NPCA primary channel, NPCA primary 40MHz channel, or NPCA primary 80MHz channel. "shi" is 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. It may be the case that "two channels are shown". In other words, if AP is the RU allocation subfield of MU-RTS, there may be only one type of channel that can be shown for one STA. For example The AP may be a MU-RTS containing multiple User Info fields, where the RU allocation subfield indicates the primary 20MHz channel for STA#1 and the RU allocation subfield indicates the primary 40MHz channel for STA#2.

[0246] To indicate the NPCA primary channel, NPCA primary 40MHz channel, or primary 80MHz channel, the B0 value of the RU Allocation subfield may be set to 0. To indicate the NPCA primary channel, NPCA primary 40MHz channel, or primary 80MHz channel, the B0 value of the RU Allocation subfield may be set to 1. The B0 value of the RU Allocation subfield is NPCA The B0 subfield of the RU Allocation subfield may be set to 0 to indicate the primary MHz channel, NPCA primary 40MHz channel, and NPCA primary 80MHz channel. The PS160 subfield of the User Info field may be set to 0 to indicate the NPCA primary MHz channel, NPCA primary 40MHz channel, and NPCA primary 80MHz channel. The PS160 subfield of 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.

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

[0248] The RU Allocation subfields B7-B1 (B7 to B1) 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 primary 80MHz channel, then 65. — The NPCA primary 40MHz channel is the second lowest frequency in the primary 80MHz channel. In that case, 66.

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

[0250] The RU Allocation subfield B7-B1 (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 among 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 among the NPCA primary 40MHz channel or NPCA primary 80MHz channel If it is the lowest frequency 20MHz channel, then 61. - If the primary 20MHz channel is the second lowest frequency among the primary 40MHz channel or primary 80MHz channel, or if the NPCA primary channel is the second lowest frequency among 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 For low frequencies, it's 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 For low frequencies, it's 64.

[0251] The RU Allocation subfields B7-B1 (B7 to B1) 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 among the primary 80MHz channels, or if the NPCA primary 40MHz channel is the only 40MHz channel, or the lowest frequency 40MHz channel among the primary 80MHz channels, 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 primary 80MHz channel, 66.

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

[0253] The B7-B1 (from B7 to B1) subfield of the RU Allocation subfield is the NPCA primary channel, as follows: It may be set to indicate that — A predetermined value if the NPCA primary channel is the only 20MHz channel, or the lowest frequency 20MHz channel among 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 the NPCA primary 80MHz channel. — A predetermined value when the NPCA primary channel is the third lowest frequency in the NPCA primary 80MHz channel. — A predetermined value when the NPCA primary channel is the fourth lowest frequency in the NPCA primary 80MHz channel.

[0254] The RU Allocation subfields B7-B1 (B7 to B1) 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 among the primary 80MHz channels. — The NPCA primary 40MHz channel is the second lowest frequency in the primary 80MHz channel. If so, the predetermined value.

[0255] B7-B1 of the RU Allocation subfield are designated to indicate the NPCA primary 80MHz channel. The values ​​may be set to the following values. B7-B1 of the RU Allocation subfield may be set to predetermined values ​​to indicate the NPCA primary and NPCA secondary 80MHz channels (NPCA primary 80MHz channel and NPCA secondary 80MHz channel).

[0256] When the AP requests the STA to transmit a CTS in response to the MU-RTS, it may indicate a predetermined value in the RU allocation subfield of the MU-RTS to request the STA to transmit the CTS on the NPCA primary channel. The STA will then respond to the RU allocation subfield of the MU-RTS transmitted from the AP, which will indicate a predetermined value. If so, CTS may be transmitted 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 case where the NPCA operating channel width is 20MHz. The only 20MHz channel is MU-RTS The channel width may be 20MHz. If the NPCA primary channel is the lowest frequency 20MHz channel in the NPCA primary 40MHz channel, 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 in the NPCA primary 80MHz channel, 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 in the NPCA operating channel, a predetermined value (e.g., 61, or (Other values ​​may be set.) If the NPCA primary channel is the 20MHz channel with the second lowest frequency among the NPCA primary 40MHz channels, then the RU allocation subfield A predetermined value (for example, 62, or any other value) may be set. The NPCA primary channel is the 20MHz channel, which is the second lowest frequency channel in the NPCA primary 80MHz channel. In this case, a predetermined value (e.g., 62, or any other value) may be set in the RU allocation subfield. If the NPCA primary channel is the 20MHz channel with the second lowest frequency among the NPCA operating channels, a predetermined value (e.g., 62, . The specified value may be the same as the value used to indicate the 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.

[0257] When AP requests STA to transmit CTS in response to MU-RTS, AP may indicate a predetermined value in the RU allocation subfield of MU-RTS to request STA to transmit CTS on the NPCA primary 40MHz channel. If indicated, CTS may be transmitted on the NPCA primary 40MHz channel. If the NPCA primary 40MHz channel is the only 40MHz channel, RU allocation subf A predetermined value (e.g., 65, or any other value) may be set for ield. (only 40MHz) The channel may have an NPCA operating channel width of 20MHz. The only 40MHz channel may have a MU-RTS channel width of 40MHz. If the NPCA primary 40MHz channel is the lowest frequency 40MHz channel among the NPCA primary 80MHz 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 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. Or other values ​​may be set. NPCA primary 40MHz channel is NPCA primary In the case of the 80MHz channel, if it is the second lowest frequency channel, 40MHz channel, RU allocation A predetermined value (e.g., 66, or another value) may be set in the 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. It may also be possible. The specified values ​​indicate a primary 20MHz channel, primary 40MHz channel, primary 80MHz channel, primary 160MHz channel, 80+80MHz channel, or 320MHz channel. The value may be different from the value intended for that purpose.

[0258] When AP requests STA to transmit CTS in response to MU-RTS, AP may indicate a predetermined value (e.g., 67, or another value) in the RU allocation subfield of MU-RTS to request STA to transmit CTS on the NPCA primary 80MHz channel. STA then receives the MU-RTS transmitted from AP. If a predetermined value (e.g., 67, or any other value) is indicated in the RU allocation subfield, CTS may be transmitted on the NPCA primary 80MHz channel. The predetermined value is 1 or more integers. It may be a number. The specified value may be the same value as the 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.

[0259] When an AP requests the STA to transmit a CTS in response to MU-RTS, it indicates a predetermined value (e.g., 68, or some other 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. This is also acceptable. STA is the RU allocation subfield of the MU-RTS transmitted from AP, with a predetermined value (e.g., For example, if 68 or any other value is indicated, CTS may be transmitted on a 160MHz channel that includes the NPCA primary channel but does not include the primary channel. The specified value may be an integer greater than or equal to 1. The specified value may be the same value as the 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 a different value 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] In the RU Allocation subfield of MU-RTS, the predetermined value for indicating the NPCA primary channel is the same as the predetermined value for indicating the primary 20MHz channel (e.g., 61, 62, 62, or 64). A value may be used. In the RU Allocation subfield of MU-RTS, a predetermined value for indicating the NPCA primary channel may be different from a predetermined value for indicating the primary 20MHz channel. It may be. In the RU Allocation subfield of MU-RTS, the predetermined value for indicating the NPCA primary 40MHz channel is the predetermined value for indicating the primary 40MHz channel (e.g., 65 or 66 The same value as ) may be used. A predetermined value in the RU Allocation subfield of MU-RTS to indicate the NPCA primary 40MHz channel. The value used for the primary 40MHz channel may differ from the predetermined value used for the primary 40MHz channel. In the RU Allocation subfield of MU-RTS, the predetermined value used for the 80MHz channel in NPCA may be the same value used for the predetermined value used for the primary 80MHz channel (e.g., 67). In the RU Allocation subfield of MU-RTS, a predetermined setting for indicating the 80MHz channel in NPCA. The value used may be different from the predetermined value used to indicate the primary 80MHz channel.

[0261] A primitive containing parameters indicating that NPCA should be performed may be issued. A primitive containing a parameter indicating this may be issued by MAC or PHY. For example, NPCA A primitive containing a parameter indicating that NPCA should be performed may be a PHY-CONFIG.request primitive, a PHY-CONFIG.confirm primitive, etc. A parameter indicating that NPCA should be performed may be called NPCA_flag. If NPCA_flag does not exist, a primitive containing NPCA_flag is issued. It may not be present. If NPCA_flag exists, the primitive containing NPCA_flag is It may be issued if available.

[0262] The RU Allocation subfield B7-B1 (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 among the primary 40MHz channel or primary 80MHz channel and NPCA_flag does not exist, or if the NPCA primary channel is the only 20MHz channel (only 20MHz channel), or the lowest frequency 20MHz channel in the NPCA primary 40MHz channel or NPCA primary 80MHz channel where NPCA_flag exists, then 61. ― If the primary 20MHz channel is the second lowest frequency in the primary 40MHz channel or primary 80MHz channel and NPCA_flag does not exist, or if the NPCA primary channel is the second lowest frequency in the NPCA primary 40MHz channel or NPCA primary 80MHz channel If the frequency is low and NPCA_flag is present, the value is 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, then 64.

[0263] The RU Allocation subfields B7-B1 (B7 to B1) 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 among the primary 80MHz channels and NPCA_flag does not exist, or if the NPCA primary 40MHz channel is the only 40MHz channel, or the lowest frequency 40MHz channel among the primary 80MHz channels If NPCA_flag exists, the value is 65. - If the primary 40MHz channel is the second lowest frequency in the primary 80MHz channel and NPCA_flag does not exist, or if the NPCA primary 40MHz channel is the second lowest frequency in the primary 80MHz channel and NPCA_flag exists, then 66.

[0264] 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 67 to indicate the primary 80MHz channel and secondary 80MHz channel if NPCA_flag does not exist, or NPCA_flag It may be set to 68 to indicate a 160MHz channel if one exists.

[0265] 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 also contain a field indicating that carrier sensing is performed on the NPCA primary channel and that the MU-RTS Trigger frame is being transmitted. For example, the Common Info field in the MU-RTS Trigger frame. The field may include an indication that carrier sensing is being performed on the NPCA primary channel and that a MU-RTS trigger frame is being transmitted. The AP performs carrier sensing on the NPCA primary channel and transmits MU-RTS on one or more channels, including the NPCA primary channel. If sending, it may indicate that it is sending MU-RTS via the NPCA primary channel. The AP will indicate that it is sending MU-RTS via the NPCA primary channel if a PHY-CONFIG.request primary containing information about NPCA has been issued. It is also acceptable to say, “Transmitting MU-RTS via NPCA primary channel” is equivalent to “NPCA primary channel This can be considered synonymous with "carrier sensing is performed on the channel and MU-RTS trigger frames are being sent." "MU-RTS is being sent via the primary channel" is equivalent to "primary channel This can be considered synonymous with "performing carrier sensing and transmitting a MU-RTS trigger frame." For example, STA receives a MU-RTS and the MU-RTS is transmitted via the NPCA primary channel. When indicating this, the RU Allocation subfield is shown relative to the NPCA primary channel. You may make that judgment. For example, STA receives MU-RTS, and MU-RTS communicates via the NPCA primary channel. If it does not indicate that it was transmitted as such, the RU Allocation subfield may be determined to be based on the primary channel. For example, if an AP transmits MU-RTS over the NPCA primary channel and requests the STA to transmit CTS on a channel that includes the NPCA primary channel, the MU-RTS may include information about the NPCA. For example, information about the NPCA may be on the NPCA primary channel After carrier sensing, it may indicate that MU-RTS is being transmitted. That is, it may include the NPCA primary channel or not. If the STA receives MU-RTS and it contains information about NPCA, it may determine that it is being transmitted via the NPCA primary channel and transmit a CTS on the channel containing the NPCA primary channel indicated in the RU Allocation subfield. If the STA receives MU-RTS and it does not contain information about NPCA, If not, it is determined that it is being transmitted via the primary channel, and in the RU Allocation subfield... A CTS may be transmitted on the channel containing the indicated primary channel. If the 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 exists... The NPCA indicate field indicates that MU-RTS is being transmitted via the NPCA primary channel. It may also indicate that MU-RTS is not being transmitted via 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 via the NPCA primary channel. For example, the NPCA indicate field is defined by 1 bit, and if 0 is indicated in the NPCA indicate field, it means that MU-RTS is not being transmitted via the NPCA primary channel. If the NPCA indicate field is set to 1, it may indicate that MU-RTS is being transmitted via the NPCA primary channel. For example, if NPCA indicate is not present, even if the NPCA indicate field is not present in MU-RTS. good.

[0266] The RU Allocation subfield B7-B1 (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 among the primary 40MHz channel or primary 80MHz channel and there is no NPCA indicate, or if the NPCA primary channel is the only 20MHz channel, or the NPCA primary 40MHz channel or NPCA If it is the lowest frequency 20MHz channel in the primary 80MHz channel and an NPCA indicator is present, then it is 61. — The primary 20MHz channel is used by the primary 40MHz channel or primary 80MHz channel. If the second lowest frequency is and there is no NPCA indicate, or if the NPCA primary channel is the second lowest frequency in the NPCA primary 40MHz channel or NPCA primary 80MHz channel If the frequency is low and an NPCA indicator is present, then 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.

[0267] The RU Allocation subfields B7-B1 (B7 to B1) 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 there is no NPCA indicate, or if the NPCA primary 40MHz channel is the second lowest frequency in the primary 80MHz channel and there is an NPCA indicate, 66.

[0268] 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 secondary 80MHz channel when no NPCA indicator is present, or to indicate the 160MHz channel when an NPCA indicator is present. .

[0269] There may be a set of candidate channels for when a CTS is sent in response to MU-RTS. The set of candidate channels when a CTS is sent in response to MU-RTS is one or It may consist of multiple types of channels, as indicated in the RU Allocation subfield of MU-RTS. The channel may be one of the candidate set. The supplementary set includes the primary 20MHz channel and / or primary 40MHz channel and / or primary 80MHz channel and / or primary 160MHz channel and / or 80+80MHz channel and / or 320MHz channel and / or NPCA primary channel and / or may consist of an NPCA primary 40MHz channel and / or an NPCA primary 80MHz channel. For example, a candidate set of 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, and a 320MHz channel. For example, the channels on which the CTS is transmitted The set of candidates is NPCA primary channel, NPCA primary 40MHz channel, NPCA primary It may consist of an 80MHz channel and a 160MHz channel. For example, the channel on which CTS is transmitted The candidate channel 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, and an NPCA primary channel. For example, the candidate channel set for 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 assigns one channel from the candidate set to one or more STAs in the RU allocation subfield of the MU-RTS. Each can be notified. The set of candidates changes depending on the Operating channel width value. This is also acceptable. For example, when the operating channel width is 40MHz, the set of candidates is primary 20. It may consist of a MHz channel and a primary 40MHz 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, 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 It may be configured as an 80MHz channel. The set of candidates may change depending on the value of the NPCA Operating channel width. For example, if the NPCA Operating channel width is 160MHz, the set of candidates may consist of the NPCA primary channel, the NPCA primary 40MHz channel, the NPCA primary 80MHz channel, and the 160MHz channel. For example, if the NPCA Operating channel width is 80MHz, the set of candidates may consist of the NPCA primary channel, the NPCA primary 40MHz channel, and the 80MHz channel. The set of candidates may be configured by the Operating channel width and the NPCA Operating channel width. In NPCA, from the set of candidates determined by the NPCA Operating channel width or a predefined set... The channel on which CTS is transmitted may be indicated. Each set of candidates may be composed of the Operating channel width. The set of candidates may be predefined. The set of candidates is based on the Operating channel width and / or NPCA operating channel width. Therefore, it may be determined. The operating channel width is the operating channel width of the AP. It may be present. 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 it will be transmitted on 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.

[0270] 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 also consist of a primary 20MHz channel, a primary 40MHz channel, a primary 80MHz channel, a primary 160MHz channel, and a 320MHz channel.

[0271] 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 in the RU Allocation subfield. 01, 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 STA and / or AP may be a 160MHz channel. 2001, 2002, 2003, 2004, 2005, 2006, 2007, and 2008 are operating channels. This is also acceptable. 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. It may be present. The STA and / or AP may transmit MU-RTS with a bandwidth of 2009, 2010, 2011, or 2012 after carrier sensing on the primary channel. 2009, 2010, 2011, and 2012 may be values ​​indicated in the UL BW subfield. 2009 may be a value of 20 MHz indicated in the UL BW subfield. 10 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 in the UL BW subfield. This may also indicate 80+80MHz. 2013, 2014, 2015, 2016, 2017, 2018, 2019, and 2020 are the channels on which CTS frames are transmitted. It may also be the case that any of 2013, 2014, 2015, 2016, 2017, 2018, 2019, or 2020 is 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 on the primary 40MHz channel. 2019 may be on the primary 80MHz channel. 2020 may be on 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. i. If a predetermined value is indicated in the RU Allocation subfield, the STA may transmit CTS using an operating channel width of 160 MHz. In Figure 20, the NPCA operating channel width may be an 80 MHz channel. In Figure 20, the NPCA operating channel width of the STA and / or AP may be an 80 MHz channel. 2005, 2006, 2007, and 2008 may be NPCA operating channels. 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 transmit MU-RTS with bandwidth 2021, 2022, or 2023 after carrier sensing on the NPCA primary channel. You may send this. 2021, 2022, and 2023 may be values ​​indicated in the UL BW subfield in NPCA. 2021 is a value indicated as 20MHz in the UL BW subfield in NPCA. This may also be the case. In 2022, 40MHz was shown in the UL BW subfield at NPCA. This may also be the case. In 2023, 80 MHz was shown in the UL BW subfield at NPCA. It may also be the case that 2024, 2025, 2026, and 2027 are channels on which CTS frames are transmitted in NPCA. 2024 or 2025 may be the NPCA primary channel. 2026 is the NPCA primary 40MHz channel. It may also be the 80MHz channel. If the value is indicated, the STA may transmit the CTS using the NPCA primary channel. RU If a predetermined value is shown in the Allocation subfield, STA will be the NPCA primary 40MHz channel. CTS may be transmitted using . If a predetermined value is indicated in the RU Allocation subfield, the STA may transmit CTS using 80 MHz of the NPCA operating channel. For example, AP may transmit a MU-RTS Trigger frame with a bandwidth of 2009, 2010, 2011, or 2012, and to each of one or more STAs, indicate one of 2013, 2014, 2015, 2016, 2017, 2018, 2019, or 2020 in the RU Allocation subfield, and each STA may transmit CTS on the indicated channel. In NPCA, AP may transmit a MU-RTS Trigger frame with a bandwidth of 2021, 2022, or 2023, and to each of one or more STAs, indicate one of 2024 in the RU Allocation subfield. The STA may indicate one of the following: 2001, 2025, 2026, or 2027, and each STA may transmit 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. To request the STA to transmit CTS on the primary 20MHz channel, the AP indicates 2013 in the RU Allocation subfield of MU-RTS and instructs the STA to transmit CTS on the primary 40MHz channel. To request this, indicate 2017 in the RU Allocation subfield of MU-RTS, and to request CTS transmission on the primary 80MHz channel to STA, indicate 2019 in the RU Allocation subfield of MU-RTS. It may also be shown that 2008 is the NPCA primary channel, 2024 is the NPCA primary channel, 2026 is the NPCA primary 40MHz channel, and 2027 is the 80MHz channel. It is also acceptable. In NPCA, the AP indicates 2024 in the MU-RTS RU Allocation subfield to request the STA to transmit CTS on the NPCA primary channel, 2026 in the MU-RTS RU Allocation subfield to request the STA to transmit CTS on the NPCA primary 40MHz channel, and 20 in the MU-RTS RU Allocation subfield to request the STA to transmit CTS on the 80MHz channel. You may also indicate 27.

[0272] 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.

[0273] Figure 21 shows an example of the process for determining the channel to transmit the CTS according to one aspect of this embodiment. The STA may receive the MU-RTS (S2101). The STA may indicate the channel for CTS transmission in the RU Allocation subfield of the received MU-RTS (S2102). The 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. 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.

[0274] 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.

[0275] As explained above, AP can indicate CTS transmission on a channel that includes the NPCA primary channel but does not include the primary channel in MU-RTS. STA can indicate CTS transmission on a channel that includes the NPCA primary channel but does not include the primary channel. This invention enables STA and AP to perform frame exchange between MU-RTS and CTS in NPCA.

[0276] The programs that run on 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) during processing. It is stored in Memory, 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. It can be done.

[0277] 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.

[0278] 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, CD-ROMs, and hard disks built into computer systems. It refers to a storage device.

[0279] 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.

[0280] 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.

[0281] Furthermore, the base station device 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 device 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 device. In addition, the terminal device related to the above-described embodiment can also communicate with the base station device as an assembly.

[0282] Furthermore, some or all of the terminal device and base station device in the above-described embodiment may be implemented as an LSI, which is typically an integrated circuit, or as a chipset. Each functional block of the device and base station equipment may be individually chipped, or some or all of them may be integrated into a single chip. Furthermore, the method of integrated circuit implementation is not limited to LSIs; dedicated circuits or general-purpose circuits may also be used. It could also be implemented using a processor. Furthermore, advances in semiconductor technology could lead to the development of integrated circuits that replace LSIs. If such technology emerges, it will also be possible to use integrated circuits based on that technology.

[0283] 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 terminal devices or communication devices for AV equipment, kitchen equipment, cleaning and washing machines, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0284] 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, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of this 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. [Explanation of Symbols]

[0285] SU1, AU1 Antenna Section SU2, AU2 RF section SU3, AU3 Physical Layer Processing Unit SU4, AU4 MAC layer processing unit SU5 Upper Layer Packet Processing Unit SU6, AU6 Wireless Transceiver Unit SU7, AU7 Frame Processing Unit AU5 DSAF section

Claims

1. It includes a receiver that receives a MU-RTS Trigger frame containing the RU adjustment subfield, The RU Allocation subfield 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. The RU Allocation subfield is the primary 20MHz channel or the NPCA primary The channel is indicated, and the RU Allocation subfield is set to a first value if the NPCA primary channel is only a 20MHz channel, or the lowest frequency 20MHz channel of the NPCA primary 40MHz channel or NPCA primary 80MHz channel. Terminal device.

2. The RU Allocation subfield is such that the primary 20MHz channel is only a 20MHz channel. The terminal device according to claim 1, wherein the first value is set if it is the 20MHz channel with the lowest frequency of the primary 40MHz channel or the primary 80MHz channel.

3. The RU Allocation subfield is such that the primary 20MHz channel is only a 20MHz channel. Alternatively, the terminal device according to claim 1, wherein a second value is set if it is the 20MHz channel with the lowest frequency of the primary 40MHz channel or the primary 80MHz channel.

4. The aforementioned NPCA primary channel is used when the primary 20MHz channel is busy, The channel on which sensing is performed, the NPCA primary 40MHz channel is a 40MHz channel that includes the NPCA primary channel but does not include the primary channel, and the NPCA primary 80MHz channel includes the NPCA primary channel but does not include the primary channel. The terminal device according to claim 1, wherein the channel is 80 MHz.

5. The CTS transmitted in response to the MU-RTS Trigger frame is non-HT or non-HT The terminal device according to claim 1, which transmits in duplicate PPDU.

6. It includes a transmitter that sends a MU-RTS Trigger frame including the RU allocation subfield, The RU Allocation subfield 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. The RU Allocation subfield is the primary 20MHz channel or the NPCA primary The channel is indicated, and the RU Allocation subfield is set to a first value if the NPCA primary channel is only a 20MHz channel, or the lowest frequency 20MHz channel of the NPCA primary 40MHz channel or NPCA primary 80MHz channel. Base station equipment.

7. A communication method for base station equipment, comprising a receiving unit that receives a MU-RTS Trigger frame including a RU allocation subfield, The RU Allocation subfield 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. The RU Allocation subfield is the primary 20MHz channel or the NPCA primary A communication method comprising indicating a channel, wherein the RU Allocation subfield is set to a first value if the NPCA primary channel is only a 20MHz channel, or the lowest frequency 20MHz channel of the NPCA primary 40MHz channel or NPCA primary 80MHz channel.

Images