Base station equipment, terminal equipment, and communication method

Abstract

This invention provides base station equipment, terminal equipment, and communication methods that enable efficient communication in a wireless LAN system. [Solution] In a wireless LAN system, the terminal is equipped with a receiving unit that receives a trigger frame, the trigger frame includes a User Info field, the User Info field includes a RU Allocation subfield and a PS160 subfield, and the PHY RU or MRU index is determined using a predetermined value determined from a first configuration, the first configuration indicates the frequency order of the NPCA primary 80MHz channel and the NPCA secondary 80MHz channel.

Description

[Technical Field]

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

[0002] The IEEE (The Institute of Electrical and Electronics Engineers Inc.) is considering ways to increase the speed and improve the efficiency of wireless LAN (Local Area Network) communication and frequency utilization. Currently, standardization of IEEE 802.11bn, the successor to IEEE 802.11be, has begun. [Prior art documents] [Non-patent literature]

[0003] IEEE802.11-23 / 2005r0, Intel Corp, “Non-primary channel access (NPCA)”, November 2023. [Overview of the project] [Problems that the invention aims to solve]

[0004] The present invention provides a terminal device, a base station device, and a communication method that enable efficient communication. [Means for solving the problem]

[0005] (1) A first aspect of the present invention is a terminal device comprising a receiving unit that receives a trigger frame The Trigger frame includes a User Info field, the User Info field includes an RU Allocation subfield and a PS160 subfield, and the RU Allocation subfield has a predetermined bit A terminal device that determines a predetermined value from the PS160 subfield and the first configuration, and uses the predetermined value to determine the PHY RU or MRU index, wherein the first configuration indicates the frequency order of the NPCA primary 80MHz channel and the NPCA secondary 80MHz channel, the NPCA primary 80MHz channel is indicated by NP80, and the NPCA secondary 80MHz channel is indicated by NS80.

[0006] (2) A second aspect of the present invention is a communication method for use in a terminal device, comprising the step of receiving a trigger frame, the trigger frame comprising a User Info field, the User Info field comprising a RU Allocation subfield and a PS160 subfield, determining a predetermined value from a predetermined bit of the RU Allocation subfield, the PS160 subfield, and a first Configuration, and using the predetermined value to determine a PHY RU or MRU index, the first Configuration indicating the frequency order of an NPCA primary 80MHz channel and an NPCA secondary 80MHz channel, the NPCA primary 80MHz channel being represented by NP80 and the NPCA secondary 80MHz channel being represented by NS80. [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] This figure shows an example of a table of encodings for the RU Allocation subfield of the User Info field according to one aspect of this embodiment. [Figure 15] This figure shows an example of a Lookup Table for N according to one aspect of this embodiment. [Figure 16] This figure shows an example of the mapping of the PHY RU index to RU according to one aspect of this embodiment. [Figure 17]This figure shows an example of a Lookup Table for N in NPCA according to one aspect of this embodiment. [Figure 18] This figure shows an example of the process for determining the PHY RU index of STA according to one aspect of this embodiment. [Figure 19] This figure shows an example of the process for sending a trigger frame by an AP according to one aspect of this embodiment. [Modes for carrying out the invention]

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

[0010] "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 a PLME.

[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 basic 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 distance between direct 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 (ESS) are used for non-GLK operations. It may be a mechanism for extending connectivity for [the purpose]. GLK operation uses a bridge. 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 transmitted via 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 related to the physical layer function (PHY function) on the converted baseband signal. The signal that has undergone processing at the physical layer in the physical layer processing unit SU3 is sent to the MAC layer processing unit SU4. The MAC layer processing unit SU4 performs processing related to the MAC layer function (MAC function) on the baseband signal. The signal that has undergone processing at the MAC layer in the MAC layer processing unit SU4 is sent as an upper layer packet to the upper layer packet processing unit SU5. The upper layer packet processing unit SU5 performs processing related to the upper layer function on the upper layer packet extracted from the received signal.

[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 processes MA After processing in the C layer, the frame is subjected to processing related to the physical layer's functions. 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), This may include spatial mapping (including transmit beamforming), spacetime block coding (STBC), low-density parity checking (LDPC) coding, and antenna selection (ASEL). HT STA The permitted PPDU formats may be non-HT format, HT-mixed format, and HT-greenfield format. In an HT STA, the PPDU may be transmitted with a 20 MHz bandwidth. In an HT STA, the PPDU may be transmitted with a 40 MHz bandwidth. An HT STA may have MAC functionality including frame aggregation, several block ack features, low-power multipole (PSMP) operation, reverse direction (RD), and protection mechanisms to support coexistence with non-HT STAs. 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 support for DL ​​and UL OFDMA (Up Link Orthogonal Frequency Division Multiple Access). 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 be support for the AP's OMI (Operating Mode Indication) responder and OMI initiator. The main MAC function of HE STA that is not present in HT STA or VHT STA may be support for the AP's individual TWT (Target Wake Time). The main MAC function of HE STA that is not present in HT STA or VHT STA may be support for non-AP STA's two NAV operation.

[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, UHR STA may be HE STA at 2.4GHz. For example, UHR STA may be HT STA at 2.4GHz. 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 and / or an HT Operation element. VHT BSS is VHT The Beacon frame transmitted by the STA may be a BSS containing a VHT Capabilities element and / or a VHT Operation element. The HE BSS may be a BSS containing a HE Capabilities element and / or an HE Operation element in the Beacon frame transmitted by the HE STA. The EHT BSS may be a Beacon frame transmitted by the HE STA The (beacon) frame may be a BSS that includes an EHT Capabilities element and / or an EHT Operation element. A UHR BSS may be a BSS in which the Beacon frame transmitted by the UHR STA includes a UHR Capabilities element and / or a UHR Operation element. For example, an HT BSS may consist of an STA that supports the capabilities of the HT STA. For example, a VHT BSS may consist of a VHT STA It may consist of STAs that support the capability of HE. For example, HE BSS may consist of STAs that support the capability of HE. For example, EHT BSS may consist of STAs that support the capability of EHT. For example, UHR BSS may consist of STAs that support the capability of UHR. It may also consist of ported 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). The information may be distributed in this manner. The MAC frame in the STA may be processed by the MAC layer processing unit SU4. The MAC frame in the 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] A field may be a field. A field may be a field. A subfield may be a subfield. A subfield may be a subfield. A field may be a subfield. A subfield may be a field. A subfield may be a field. A field may be a subfield.

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

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

[0054] Figure 5 shows an example of a MAC frame format according to one aspect of this embodiment. In Figure 5, the MAC frame format may consist of a MAC header, a Frame Body, and an FCS. In 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.

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

[0056] 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. It is also acceptable. If 10 is set in the Type subfield, the frame type is a Data frame. That's fine.

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

[0058] The subtype 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.

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

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

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

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

[0063] For example, 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.

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

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

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

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

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

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

[0070] A VHT operation element may be sent in a Management frame. A VHT operation element may be sent in a Control frame. A VHT operation element may be sent in a Data frame. For example, a VHT operation element may be sent in a Beacon frame. For example, 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.

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

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

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

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

[0075] HE operation elements may be sent in a Management frame. HE operation elements may be sent in a Control frame. HE operation elements may be sent in a Data frame. For example, 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.

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

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

[0078] The 6GHz Operation Information field in the HE Operation element format may provide channel and bandwidth information related to 6GHz operation. The 6GHz Operation Information field format 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 and may be set to 0 for 20MHz, 1 for 40MHz, 2 for 80MHz, or 3 for 80+80MHz or 160MHz.

[0079] The EHT Operation element format may also be an Operation element for controlling an EHT STA operating in an EHT BSS. When operating in the 2.4GHz band, an EHT STA in an EHT BSS may be controlled by an HT Operation element, an HE Operation element, and an EHT Operation element. 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.

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

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

[0082] Figure 6 shows an example of an A-MSDU according to one aspect of this embodiment. In Figure 6, the MAC frame format may consist of a MAC header, a Frame Body, and an FCS. Here, the MAC header consists of a Frame Control field, a Duration field, an Address1 field, an Address2 field, an Address3 field, a Sequence Control field, and an Address4 field. It may be configured in the QoS Control field. The MAC frame format may be 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.

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

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

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

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

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

[0088] Figure 9 shows an example of a PPDU according to one aspect of this embodiment. In Figure 9, L-STF and L-LTF may be added to the PPDU in the PHY layer. In Figure 9, the PPDU 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.

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

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

[0091] The time interval may differ depending on the type of IFS. For example, PIFS 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.

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

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

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

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

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

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

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

[0099] The basic method of accessing MACs used by STAs may be DFC (Distributed Coordination Function). DCF 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.

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

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

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

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

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

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

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

[0107] A QoS facility may include an additional coordinating function called HCF (Hybrid Coordination Function), which is only available in a QoS network configuration. HCF may be implemented in all QoS STAs. HCF 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.

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

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

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

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

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

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

[0114] 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 A message (1004) may be sent. Here, the backoff counter may be determined between 0 and CW. CW may be a value selected from a series of values from aCWmin or more to aCWmax or less. The channel may be referred to as a radio medium.

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

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

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

[0118] The physical carrier sense function in the STA may be controlled by the physical layer processing unit SU3. The virtual carrier sense function in the STA may be controlled by the MAC layer processing unit SU4. The physical carrier sense function 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.

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

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

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

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

[0123] Career sense (CS) may be performed through both physical and virtual mechanisms. Good. Carrier sense may also be called a carrier sense mechanism. A virtual carrier sense mechanism is implemented by distributing reservation information that notifies of the advance use of a medium. Exchanging RTS frames and CTS frames before the actual data frame may be one means of distributing the medium 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.

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

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

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

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

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

[0129] Channel bonding may transmit using one or more 20MHz channels. Alternatively, channel bonding may transmit using multiple 20MHz channels. Channel bonding may transmit using multiple adjacent 20MHz channels. Channel bonding may also be 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.

[0130] 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. Alternatively, the primary 80 channel may be an 80MHz channel on which an 80MHz PPDU is transmitted in a 160MHz or 80+80MHz BSS. The primary 160MHz channel may be on a 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.

[0131] The primary channel may also be referred to as the BSS primary channel.

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

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

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

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

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

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

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

[0139] STA may determine the channel frequency. AP may determine the channel frequency. Good. To determine the channel frequency, use the primary channel (primary 20MHz channel). and / or secondary 20MHz channel and / or secondary 40MHz channel and / or secondary 80MHz channel and / or secondary 160MHz channel and / or Alternatively, this may involve determining (defining) the center frequencies 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. Determining the channel frequency is the primary channel (primary 20MHz channel) and / or secondary 20MHz channel and / or secondary 40MHz channel and / or secondary 80MHz channel and / or secondary 160MHz channel and / or NPCA primary channel and / or NPCA secondary channel This may involve determining (defining) the locations of the daily 20MHz channel and / or the NPCA secondary 40MHz channel and / or the NPCA secondary 80MHz channel.

[0140] f c,idx0 This may be dot11CurrentChannelCenterFrequencyIndex0. dot11CurrentChannelCenterFrequencyIndex0 may indicate the channel center frequency for 20MHz, 40MHz, 80MHz, or 160MHz channels. dot11CurrentChannelCenterFrequencyIndex0 may indicate the center frequency of frequency segment 0, which includes the primary channel, for an 80+80MHz channel. In other words, f c,idx0 This value may represent the channel center frequency for 20MHz, 40MHz, 80MHz, or 160MHz channels, and may also represent the center frequency of the frequency segment including the primary channel for 80+80MHz channels.

[0141] f c,idx1This may be dot11CurrentChannelCenterFrequencyIndex1. dot11CurrentChannelCenterFrequencyIndex1 may indicate the center frequency of frequency segment 1 that does not include the primary channel for an 80+80MHz channel. In other words, f c,idx1 This value may also represent the center frequency of frequency segment 1, which does not include the primary channel, for an 80+80MHz channel.

[0142] f P20,idx This could be dot11CurrentPrimaryChannel. dot11CurrentPrimaryChannel may indicate the position of the primary 20MHz channel. That is, f P20,idx f may be a value indicating the position of the primary 20MHz channel. CH,start is dot11ChannelStartingFactor ×500kHz is also acceptable. CH,start This may be the channel starting frequency. The channel starting frequency may be dot11ChannelStartingFactor × 500kHz. dot11ChannelStartingFactor may be indicated by the Operating Class field. dot11CurrentChannelWidth may indicate the channel width. dot11CurrentChannelWidth is configurable. The values ​​may be for 20MHz, 40MHz, 80MHz, 160MHz, and 80+80MHz channels.

[0143] dot11CurrentChannelWidth may be notified by an information element. dot11CurrentChannelWidth may be notified by a VHT operation element. dot11CurrentChannelWidth may be notified by an HE operation element. dot11CurrentChannelWidth may be notified in the VHT Operation Information field of a VHT operation element. dot11CurrentChannelWidth may be notified in the VHT Operation Information field of an HE operation element , may be notified. dot11CurrentChannelWidth may be notified in the 6GHz Operation Information field of the HE operation element. dot11CurrentChannelWidth may be notified in the Channel Width subfield included in the VHT Operation Information field. dot11CurrentChannelCenterFrequencyIndex0 may be notified in the information element. dot11CurrentChannelCenterFrequencyIndex0 is notified in the VHT operation element. This is also acceptable. dot11CurrentChannelCenterFrequencyIndex0 may be an HE operation element, and may be notified. dot11CurrentChannelCenterFrequencyIndex0 is a VHT operation element It may be notified in the VHT Operation Information field. dot11CurrentChannelCenterFrequencyIndex0 may be notified in the VHT Operation Information field of the HE operation element. dot11CurrentChannelCenterFrequencyIndex0 may be notified in the 6GHz Operation Information field of the HE operation element. dot11CurrentChannelCenterFrequencyIndex0 may be notified in Channel Center FrequencySegment 0 included in the VHT Operation Information field. dot11CurrentChannelCenterFrequencyIndex1 may be notified in the information element. dot11CurrentChannelCenterFrequencyIndex1 is It may also be notified in the VHT operation element. dot11CurrentChannelCenterFrequencyIndex1 may also be notified in the HE operation element. dot11CurrentChannelCenterFrequencyIndex1 is notified in the VHT Operation Information field of the VHT operation element. It may be done. dot11CurrentChannelCenterFrequencyIndex1 is the VH of the HE operation element. T Operation Information field may be notified. dot11CurrentChannelCenterFrequencyIndex1 is notified in the 6GHz Operation Information field of the HE operation element. It may also be. dot11CurrentChannelCenterFrequencyIndex1 may be notified by Channel Center Frequency Segment 1 included in the VHT Operation Information field.

[0144] Information regarding the channel frequency may include dot11CurrentChannelCenterFrequencyIndex0 and / or and / or dot11CurrentChannelCenterFrequencyIndex1 and / or dot11CurrentChannelWidth and / or dot11CurrentPrimaryChannel and / or dot11ChannelStartingFactor, etc. Information other than the foregoing may also be information regarding the channel frequency.

[0145] When dot11CurrentChannelWidth is 20 MHz, f P20,idx may be f c,idx0 That is, when dot11CurrentChannelWidth is 20 MHz, f P20,idx = f c,idx0 may be. When dot11CurrentChannelWidth is greater than 20 MHz, the relationship between f P20,idx and f c,idx0 may be f P20,idx = f c,idx0 -4·(N 20MHz / 2 - n p20 ) + 2. N 20MHz may be 2 when dot11CurrentChannelWidth indicates 40 MHz. N 20MHz may be 4 when dot11CurrentChannelWidth indicates 80 MHz or 80 + 80 MHz. N 20MHz may be 8 when dot11CurrentChannelWidth indicates 160 MHz. n p20 is 0 or more and N 20MHzIntegers in the range of -1 or less That's fine.

[0146] When dot11CurrentChannelWidth is 40MHz, 80MHz, 160MHz, or 80+80MHz, the primary 20MHz channel is f CH,start +5 × f P20,idx It may also be a channel with a bandwidth of 20 MHz centered around MHz. When dot11CurrentChannelWidth is 40 MHz, 80 MHz, 160 MHz, or 80+80 MHz, the secondary 20 MHz channel is f CH,start +5 × f S20,idx A channel with a bandwidth of 20 MHz centered around MHz is also acceptable. S20,idx is, n p20 If f is an even number, P20,idx +4 That's fine. f S20,idx is, n p20 If f is an odd number, P20,idx -4 is also acceptable.

[0147] When dot11CurrentChannelWidth is 80MHz, 160MHz, or 80+80MHz, primary 40MHz channel is f CH,start +5 × f P40,idx It was a channel with a bandwidth of 40 MHz centered around MHz. It is also acceptable. When dot11CurrentChannelWidth is 80MHz, 160MHz, or 80+80MHz, the secondary 40MHz channel is f CH,start +5 × f S40,idx A 40MHz bandwidth centered around MHz It may also be a channel. P40,idx is, f P40,idx =f c,idx0 -8·(N 20MHz / 4-n p40 ) + 4 is also acceptable. S40,idx is, n p40 If f is an even number,P40,idx You can also refer to +8. S40,idx teeth , n p40 If f is an odd number, P40,idx -8 is also acceptable. p40 is FLOOR(n p20 Even if / 2) Good. In other words, n p40 is, n p20 The floor function may also be / 2. For example, n p40 is, n p20 It can also be the largest integer not exceeding / 2. For example, n p20 If the value of n is 5, p20 / 2 is 2.5 FLOOR(n p20 The value of ( / 2) may also be 2.

[0148] When dot11CurrentChannelWidth is 160MHz, the primary 80MHz channel is f CH,start +5 ×f P80,idx It may also be a channel with a bandwidth of 80 MHz centered around MHz. When dot11CurrentChannelWidth is 160 MHz, the secondary 80 MHz channel is f CH,start +5 × f S80,idx A channel with a bandwidth of 80 MHz centered around MHz is also acceptable. P80,idx is, f P80,idx =f c,idx0 -16·(N 20MHz / 8-n p80 ) + 8 is also acceptable. S80,idx is, n p80 If f is an even number, P80,idx +16 is also acceptable. S80,idx is, n p80 If f is an odd number, P80,idx -16 is also acceptable. p80 is FLOOR(n p20 It may also be n ( / 4). p80 is, n p20 The floor function may be / 4 For example, n p80 is, np20 May also be the largest integer not exceeding 1 / 4. For example, when n p20 has a value of 5, n p20 / 4 is 1.25, and the value of FLOOR(n p20 / 4) may be 1.

[0149] When dot11CurrentChannelWidth is 80 + 80 MHz, the primary 80 MHz channel is a channel with a bandwidth of 80 MHz centered at f CH,start + 5×f P80,idx MHz, and f P80,idx is f c,idx0 and may be. When dot11CurrentChannelWidth is 80 + 80 MHz, the secondary 80 MHz channel is a channel with a bandwidth of 80 MHz centered at f + 5×f CH,start MHz, and f S80,idx is f S80,idx and may be. c,idx1

[0150] f c,idx0 may be dot11EHTCurrentChannelCenterFrequencyIndex0. dot11EHTCurrentChannelCenter FrequencyIndex0 may indicate the position of the channel center frequency for 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320 MHz channels as well. The value range of dot11EHTCurrentChannelCenterFrequencyIndex0 may be from 1 to 13 for 2.4 GHz, from 1 to 200 for 5 GHz, and from 1 to 233 for 6 GHz. f P20,idx ​This may be dot11CurrentPrimaryChannel. dot11CurrentPrimaryChannel may indicate the position of the primary 20MHz channel. The range of values ​​for dot11CurrentPrimaryChannel is relative to 2.4GHz. For GHz, the range may be 1 to 13, 1 to 200 for 5 GHz, and 1 to 233 for 6 GHz. In other words, f P20,idx f may be a value indicating the position of the primary 20MHz channel. CH,start This may be dot11ChannelStartingFactor × 500kHz. dot11ChannelStartingFactor may be represented by the Operating Class field. dot11ChannelStartingFactor is channel starting frequency f CH,start It may be used to define the channel width. dot11EHTCurrentChannelWidth may indicate the channel width. The configurable values ​​for dot11EHTCurrentChannelWidth may be 20MHz, 40MHz, 80MHz, 160MHz, and 320MHz channels.

[0151] dot11EHTCurrentChannelWidth may be notified in operation information. dot11EHTCurrentChannelWidth may be notified in the EHT operation element. dot11EHTCurrentChannelWidth may be notified in the EHT operation Information field of the EHT operation element. It may also be. dot11EHTCurrentChannelWidth may be notified in the field within the Control subfield of the EHT operation Information field. dot11EHTCurrentChannelWidth may be notified in the Channel Width field within the Control subfield. dot11EHTCurrentChannelCenterFrequencyIndex0 may be notified in the operation information. dot11EHTCurrentChannelCenterFrequencyIndex0 may be notified in the EHT operation element. dot11EHTCurrentChannelCenterFrequencyIndex0 may be notified in the EHT operation Information field of the EHT operation element. dot11EHTCurrentChannelCenterFrequencyIndex0 may be notified in the CCFS0 subfield of the EHT operation Information field.

[0152] When dot11EHTCurrentChannelWidth is 20 MHz, f P20,idx may be c,idx0 as well. That is, when dot11EHTCurrent ChannelWidth is 20 MHz, f P20,idx = f c,idx0 may be. When dot11EHTCurrentChannelWidth is 40 MHz, 80 MHz, or 160 MHz, f P20,idx and f c,idx0 The relationship of may be f P20,idx = f c,idx0 -4·(N 20MHz / 2 - n p20 ) + 2 may be. When dot11EHTCurrentChannelWidth is 320 MHz, f P20,idx and c,idx0 The relationship of f may beP20,idx =f c,idx0 -4·(N 20MHz / 2-n p20 ) + 2 is also acceptable. Here, N 20MHz is 16 That's also fine. In other words, N 20MHz n = 16 is also acceptable. p20 This corresponds to the primary 20MHz channel with dot11EHTCurrentChannelCenterFrequencyIndex0 and dot11EHTCurrentChannelWidth values. It may also be an integer indicating the position of n. p20 The range is 0 to N 20MHz It may be -1 or less. When dot11EHTCurrentChannelWidth is 40MHz, 80MHz, 160MHz, or 320MHz, f P20,idx and f S20,idx The relationship is n p20 If f is an even number, S20,idx =f P20,idx +4, n p20 If f is an odd number, S20,idx =f P20,idx -4 is also acceptable. When dot11EHTCurrentChannelWidth is 80MHz, 160MHz, or 320MHz, f P40,idx and f c,idx0 The relationship is f P40,idx =f c,idx0 -8·(N 20MHz / 4-n p40 ) + 4, and f P40,idx and f S40,idx The relationship is n p40 If f is an even number, S40,idx =f P40,idx +8, n p40 If f is an odd number, S40,idx =f P40,idx -8 is also acceptable. When dot11EHTCurrentChannelWidth is 160MHz or 320MHz, f P80,idx oh call f c,idx0 The relationship is f P80,idx =f c,idx0 -16·(N20MHz / 8-n p80 ) + 8, and f P80,idx and f S80,idx The relationship is n p80 If f is an even number, S80,idx =f P80,idx +16, n p80 But strange In the case of numbers, f S80,idx =f P80,idx It may also be -16. When dot11CurrentChannelWidth is 320MHz, the primary 160MHz channel is f CH,start +5 × f P160,idx The 160MHz band is centered around MHz. It may also be a channel with bandwidth. When dot11CurrentChannelWidth is 320MHz, the secondary 160MHz channel is f CH,start +5 × f S160,idx A 160MHz bandwidth centered around MHz It may also be a channel. P160,idx is, f P160,idx =f c,idx0 -32·(N 20MHz / 16-n p160 ) + 16 is also acceptable. S160,idx is, n p160 If f is an even number, P160,idx +32 is also acceptable. S160,idx is, n p160 If f is an odd number, P160,idx -32 is also acceptable. p160 is FLOOR(n p20 It may also be / 8). In other words, n p80 is, n p20 The floor function could also be n p80 is, n p20 It may also be the largest integer not exceeding / 8. For example, n p20 If the value of n is 8, p20 / 8 is 1, and FLOOR(n p20 The value of ( / 8) may be 1.

[0153] STA is fP20,idx and / or f c,idx0 and / or f c,idx1 and / or f CH,start and / or channel width (dot11CurrentChannelWidth) and / or f S20,idx and / or f P40,idx and / or f S40,idx and / or f P80,idx and / or f S80,idx and / or f P160,idx and / or f S160,idx You may use this to determine (define) the center frequencies 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.

[0154] dot11NPCACurrentChannelCenterFrequencyIndex may represent the channel center frequency of the channel width in NPCA. dot11NPCACurrentChannelCenterFrequencyIndex is f NPCA,idx It may also be: dot11NPCACurrentChannelWidth may indicate the channel width in NPCA. dot11NPCACurrentPrimary Channel may indicate the location of the NPCA primary channel. dot11NPCACurrentPrimaryChannel is f NP20,idx It is also acceptable. f NP20,idx and f NPCA,idx The relationship may be defined in advance. When dot11NPCACurrentChannelWidth is 20MHz, f NP20,idx =f NPCA,idx This may also be the case. When dot11NPCACurrentChannelWidth is greater than 20MHz, fNP20,idx and f NPCA,idx The relationship is f NP20,idx ,f NPCA,idx , may be defined using A, B, C, D, E. For example, f NP20,idx and f NPCA,idx The relationship is f NP20,idx =f NPCA,idx -A·(B / CD)+E is also acceptable. NP20,idx and f NPCA,idx The relationship may be defined by an expression other than those mentioned above. For example, A, C, and E may be integers. B is N 20MHz It may also be B, which may change depending on the value of dot11NPCACurrentChannelWidth. D may be an integer in the range of 0 or more and B-1 or less. D is , n p20 It may also be the case that when dot11NPCACurrentChannelWidth is a predetermined value, NPCA primary (20MHz) channel is f CH,start +5 × f NP20,idx It may also be a channel with a bandwidth of 20 MHz centered around MHz. When dot11NPCACurrentChannelWidth is a predetermined value, the NPCA secondary 20 MHz channel is f CH,start +5 × f NS20,idx A channel with a bandwidth of 20 MHz centered around MHz is also acceptable. NS20,idx If D is even, then f NP20,idx +F, and if D is odd, f NP20,idx -F is also acceptable. F may be an integer. When dot11NPCACurrentChannelWidth is a predetermined value, the NPCA primary 40MHz channel is f CH,start +5 × f NP40,idx Centered around MHz The channel may have a bandwidth of 40 MHz. dot11NPCACurrentChannelWidth is predetermined When the value is f, the NPCA secondary 40MHz channel is f CH,start +5 × f NS40,idxA channel with a bandwidth of 40 MHz centered around MHz is also acceptable. NP40,idx and f NPCA,idx The relationship may be defined in advance. NP40,idx and f NPCA,idx The relationship is f NP40,idx ,f NPCA,idx , may be defined using G, B, H, I, J. For example, f NP40,idx =f NPCA,idx -G·(B / HI)+J is also acceptable. NP20,idx and f NPCA,idx The relationship between G, H, and J may be defined by equations other than those mentioned above. I may be an integer. I may be FLOOR(D / K). K may be an integer. . f NS40,idx If I is even, then f NP40,idx +L, and if D is odd, f NP40,idx -L It may exist. L may be an integer. dot11NPCACurrentChannelWidth is a predetermined value At that time, the NPCA primary 80MHz channel is f CH,start +5 × f NP80,idx It may also be a channel with a bandwidth of 80 MHz centered around MHz. When dot11NPCACurrentChannelWidth is a predetermined value, The NPCA secondary 80MHz channel is f CH,start +5 × f NS80,idx A channel with a bandwidth of 80 MHz centered around MHz is also acceptable. NP80,idx and f NPCA,idx The relationship may be defined in advance. NP80,idx and f NPCA,idx The relationship is f NP80,idx ,f NPCA,idx Using M, B, N, O, P It may be defined as f NP80,idx =f NPCA,idx It may also be -M·(B / NO)+P. M, N, and P may be integers. O may be FLOOR(D / Q). Q is an integer. That's good too.NS80,idx If O is even, then f NP80,idx +R, and if O is odd, f NP80,idx -R is also acceptable. R may be an integer. The NPCA primary 40MHz channel is a 40MHz channel consisting of the NPCA primary channel and the NPCA secondary 20MHz channel. It is also acceptable. The NPCA primary 80MHz channel is an 80MHz channel composed of the NPCA primary channel, the NPCA secondary 20MHz channel, and the NPCA secondary 40MHz channel. It may be present. dot11NPCACurrentChannelCenterFrequencyIndex and / or dot11NPCACurrentChannelWidth and / or dot11NPCACurrentPrimaryChannel may be information about channel frequency. Information other than that mentioned above may be information about channel frequency. The AP may also transmit a frame containing an information element that includes dot11NPCACurrentChannelCenterFrequencyIndex and / or dot11NPCACurrentChannelWidth and / or dot11NPCACurrentPrimaryChannel. The STA may receive a frame containing an information element that includes dot11NPCACurrentChannelCenterFrequencyIndex and / or dot11NPCACurrentChannelWidth and / or dot11NPCACurrentPrimaryChannel. The information element may be, for example, an NPCA operation element, a UHR operation element, etc. The predetermined values ​​are 20MHz, 40MHz, 80MHz, 80+80MHz, 160MHz, and 320MHz. It may be the case that dot11NPCACurrentChannelCenterFrequencyIndex is dot11CurrentChannelCenterFrequencyIndex0 or dot11CurrentChannelCenterFrequencyIndex0 Good. dot11NPCACurrentChannelWidth can also be dot11NPCACurrentChannelWidth.

[0155] dot11NPCACurrentChannelCenterFrequencyIndex may represent the channel center frequency of the channel width in NPCA. dot11NPCACurrentChannelCenterFrequencyIndex is f NPCA,idx It may also be: dot11NPCACurrentChannelWidth may indicate the channel width in NPCA. dot11NPCACurrentPrimary Channel may indicate the location of the NPCA primary channel. dot11NPCACurrentPrimaryChannel is f NP20,idx It is also acceptable. f NP20,idx and f NPCA,idx The relationship may be defined in advance. When dot11NPCACurrentChannelWidth is 20MHz, f NP20,idx =f NPCA,idx This may also be the case. When dot11NPCACurrentChannelWidth is greater than 20MHz, f NP20,idx and f NPCA,idx The relationship is f NP20,idx ,f NPCA,idx, may be defined using A, B, C, D, E. For example, f NP20,idx and f NPCA,idx The relationship is f NP20,idx =f NPCA,idx -A·(B / CD)+E is also acceptable. NP20,idx and f NPCA,idx The relationship may be defined by an expression other than those mentioned above. For example, A, C, and E may be integers. B is N 20MHz It may also be B, which may change depending on the value of dot11NPCACurrentChannelWidth. D may be an integer in the range of 0 or more and B-1 or less. D is , n p20 It may also be the case that when dot11NPCACurrentChannelWidth is a predetermined value, NPCA primary (20MHz) channel is f CH,start +5 × f NP20,idx It may also be a channel with a bandwidth of 20 MHz centered around MHz. When dot11NPCACurrentChannelWidth is a predetermined value, the NPCA secondary 20 MHz channel is f CH,start +5 × f NS20,idx A channel with a bandwidth of 20 MHz centered around MHz is also acceptable. NS20,idx If D is even, then f NP20,idx +F, and if D is odd, f NP20,idx -F is also acceptable. F may be an integer. When dot11NPCACurrentChannelWidth is a predetermined value, the NPCA primary 40MHz channel is f CH,start +5 × f NP40,idx Centered around MHz The channel may have a bandwidth of 40 MHz. dot11NPCACurrentChannelWidth is predetermined When the value is f, the NPCA secondary 40MHz channel is f CH,start +5 × f NS40,idx A channel with a bandwidth of 40 MHz centered around MHz is also acceptable. NP40,idx and f NPCA,idxThe relationship may be defined in advance. NP40,idx and f NPCA,idx The relationship is f NP40,idx ,f NPCA,idx , may be defined using G, B, H, I, J. For example, f NP40,idx =f NPCA,idx -G·(B / HI)+J It's fine. NP20,idx and f NPCA,idx The relationship between G, H, and J may be defined by equations other than those mentioned above. I may be an integer. I may be FLOOR(D / K). K may be an integer. . f NS40,idx If I is even, then f NP40,idx +L, and if D is odd, f NP40,idx -L It may exist. L may be an integer. dot11NPCACurrentChannelWidth is a predetermined value At that time, the NPCA primary 80MHz channel is f CH,start +5 × f NP80,idx It may also be a channel with a bandwidth of 80 MHz centered around MHz. When dot11NPCACurrentChannelWidth is a predetermined value, the NPCA secondary 80 MHz channel is f CH,start +5 × f NS80,idx A channel with a bandwidth of 80 MHz centered around MHz is also acceptable. NP80,idx and f NPCA,idx The relationship may be defined in advance. NP80,idx and f NPCA,idx The relationship is f NP80,idx ,f NPCA,idx Using M, B, N, O, P It may be defined as f NP80,idx =f NPCA,idx It may also be -M·(B / NO)+P. M, N, and P may be integers. O may be FLOOR(D / Q). Q is an integer. That's good too. NS80,idx If O is even, then f NP80,idx +R, and if O is odd, f NP80,idx-R is also acceptable. R may be an integer. The NPCA primary 40MHz channel is a 40MHz channel consisting of the NPCA primary channel and the NPCA secondary 20MHz channel. It is also acceptable. The NPCA primary 80MHz channel is an 80MHz channel composed of the NPCA primary channel, the NPCA secondary 20MHz channel, and the NPCA secondary 40MHz channel. It may be present. dot11NPCACurrentChannelCenterFrequencyIndex and / or dot11NPCACurrentChannelWidth and / or dot11NPCACurrentPrimaryChannel may be information about channel frequency. Information other than that mentioned above may be information about channel frequency. The AP may also transmit a frame containing an information element that includes dot11NPCACurrentChannelCenterFrequencyIndex and / or dot11NPCACurrentChannelWidth and / or dot11NPCACurrentPrimaryChannel. The STA may receive a frame containing an information element that includes dot11NPCACurrentChannelCenterFrequencyIndex and / or dot11NPCACurrentChannelWidth and / or dot11NPCACurrentPrimaryChannel. The information element may be, for example, an NPCA operation element, a UHR operation element, etc. The predetermined values ​​are 20MHz, 40MHz, 80MHz, 80+80MHz, 160MHz, and 320MHz. It may be the case that dot11NPCACurrentChannelCenterFrequencyIndex is dot11CurrentChannelCenterFrequencyIndex0 or dot11CurrentChannelCenterFrequencyIndex0 Good. dot11NPCACurrentChannelWidth can also be dot11NPCACurrentChannelWidth.

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

[0157] 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. It is also acceptable. The PHY-CCA.indication primitive may include a channel-list parameter. The STATE parameter of the PHY-CCA.indication primitive may have 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. The STATE parameter value of the PHY-CCA.indication primitive may be BUSY if it indicates that the channel is unavailable in the PHY's evaluation of the channel. Otherwise, the STATE parameter value of the 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 is It may include a set of channels that indicate the G channel. In other words, the CCA is performed by 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.

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

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

[0160] 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."

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

[0162] 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. You may issue a primary(PHY-CCA.indication(BUSY,{primary})). STA is primar On the y channel, when the channel state changes from busy to idle, a primitive (PHY-CCA.indication(IDLE,{primary})) may be issued to indicate that the primary channel is idle. On the primary channel, if a primitive (PHY-CCA.indication(BUSY,{primary}))) is issued to indicate 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.

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

[0164] An 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 certain percentage or higher (e.g., 90% or higher) and the power of the preamble or PPDU measured within the primary 20 MHz 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.

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

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

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

[0168] The PHY issues PHY-CCA.indication(BUSY,{primary}), PHY-CCA.indication(BUSY,{secondary}), and PHY-CCA.Indication (BUSY, {secondary40}) primitives when there are no conditions for such primary signals and in an idle operating channel width of 160MHz or 80+80MHz, the secondary If any signal greater than -56dBm exists within the 80 MHz channel, the PHY-CCA.indication(BUSY, {secondary80}) primitive is issued. The PHY issues the PHY-CCA.indication(BUSY,{primary}), PHY-CCA.indication(BUSY,{secondary}), and PHY-CCA. Indication (BUSY, {secondary40}) primitives when the conditions for these are not met and the 160MHz or 80+80 channel is idle. In a MHz operating channel width, if an 80 MHz preamble or PPDU of -69 dBm or higher is detected with a probability of 90% or higher within the secondary 80 MHz channel within the aCCAMidTime period, the PHY-CCA.indication(BUSY, {secondary80}) primitive is issued. The PHY issues the PHY-CCA.indication(BUSY,{primary}), PHY-CCA.indication(BUSY,{secondary}), and PHY-CCA. Indication (BUSY, {secondary40}) primitive when there are no conditions for such a primitive to be issued, and in an idle 160 MHz or 80+80 MHz operating channel width, if a 40 MHz preamble or PPDU of -72 dBm or higher is detected in any 40 MHz subchannel of the secondary 80 MHz channel within the aCCAMidTime period If detected with a probability of 90% or more within the specified period, PHY-CCA.indication(BUSY, {secondary80}) The PHY issues a primitive. The PHY issues PHY-CCA.indication(BUSY,{primary}), PHY-CCA.indication(BUSY,{secondary}), and PHY-CCA. Indication (BUSY, {secondary40}) primitives when there are no conditions for such a primitive to be issued, and in an idle 160MHz or 80+80MHz operating channel width, a 20MHz preamble or PPDU is detected at -72dBm or higher with a probability of more than 90% within the aCCAMidTime period in any 20MHz subchannel of the secondary 80MHz channel. In this case, the PHY-CCA.indication(BUSY, {secondary80}) primitive is issued. Here, -56dBm, -69dBm, and -72dBm are thresholds for determining whether the channel is idle or busy. That's fine.

[0169] The threshold may be compared to the signal level of the receiving antenna. In STA, the threshold is compared The signal level may be the signal level received by the antenna unit SU1. The signal level compared to the threshold may be the level of the signal received by the antenna unit AU1. stomach.

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

[0171] 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 a signal, and in idle operating channel widths of 40MHz, 80MHz, 160MHz, and 80+80MHz, a 20MHz preamble of -72dBm or higher is detected on the secondary 20MHz channel. 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.

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

[0173] 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 conditions for issuing a PHY-CCA.indication primitive with the STATUS parameter set to BUSY are not met, and if there is no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, and no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}, and if, in an idle operating channel width of 160MHz or 80+80MHz, an 80 MHz preamble or PPDU of -69 dBm or higher is detected in the secondary 80 MHz channel with a probability of 90% or higher within the aCCAMidTime period, the PHY will issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 80}.The PHY issues a PHY-CCA.indication primitive with the STATUS parameter set to BUSY, and if there is no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, and no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}, then in an idle operating channel width of 160MHz or 80+80MHz, any 40MHz subchannel 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 STATUS parameter is set to BUSY, and the channel-list parameter is set to BUSY. PHY issues a PHY-CCA.indication primitive with meter set to {secondary 80}. PHY issues a PHY-CCA.indication primitive with the STATUS parameter set to BUSY, and if there is no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, or if there is no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}, then 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}.

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

[0175] 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 This may also be referred to as the primary channel. Operations related to NPCA may also be referred to as NPCA operations. For example, an operation that accesses via the NPCA primary channel may be referred to as an NPCA operation. Operations other than those mentioned above may also be referred to as NPCA operations.

[0176] For example, NPCA may also be called ACA (Alternate Primary Channel). The channel may be referred to as the ACA primary channel or the Alternate primary channel. The NPCA secondary channel may be referred to as the ACA secondary channel or the Alternate secondary channel. For example, NPCA may be referred to as TACA (Temporary Alternate Channel Access). The NPCA primary channel may be referred to as the TACA primary channel. The secondary channel may also be called the TACA secondary channel. For example, NPCA is TS It may also be called A (Temporary Subchannel Access). The NPCA primary channel may also be called the TSA primary channel. The NPCA secondary channel may also be called the TSA secondary channel. For example, NPCA may be called TS (Temporary Subchannel). NPCA The primary channel may also be called the TS primary channel. The NPCA secondary channel may also be called the TS secondary channel. For example, the NPCA may be called the TPC (Temporary Primary Channel). The NPCA primary channel may also be called the Temporary primary channel. The NPCA primary channel may also be called the TPC primary channel. The NPCA secondary channel may also be called the TPC secondary channel. For example, NPCA may be called ISA (Interim Subchannel Access). The NPCA primary channel may also be called the ISA primary channel. The NPCA secondary channel may also be called the ISA secondary channel. For example, NPCA may be called IS (Interim Subchannel). The NPCA primary channel may also be called the IS primary channel. The NPCA secondary channel may also be called the IS secondary channel. For example, NPCA may be called IPC (Interim Primary Channel). The NPCA primary channel may also be called the IPC primary channel or Interim primary channel. The NPCA secondary channel may also be called the IPC secondary channel or Interim secondary channel.

[0177] AP and / or STA may perform NPCA (Non Primary Channel Access). This may be an action to access other channels while the primary channel is busy due to OBSS traffic. For example, OBSS traffic may be a PPDU received from OBSS. OBSS traffic may 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. You may decide on the related actions.

[0178] In other words, the NPCA primary channel is accessed while the primary channel is busy. It may also be a channel for that purpose. The NPCA primary channel may also be a channel for channel access while NAV is set on the primary channel. The channel may be a channel for channel access while the basic NAV is set on the primary channel. The NPCA primary channel may be a channel for channel access while the primary channel is busy by the OBSS PPDU. The NPCA primary channel may be a channel for channel access while the NAV is set on the primary channel by the OBSS PPDU It may be a channel for accessing the network. The time while the NAV is set may be referred to as the time while the NAV is maintained. Channel access may be a backoff procedure. Channel access may be EDCA. Channel access may be EDCAF. Channel access may also be via CCA.

[0179] The STA may switch to the NPCA primary channel for NPCA operation if the value of the last received or transmitted NPCA operation Information Present field corresponding to its BSS is equal to a predetermined value and one or more of the following conditions are met. For example, if the STA receives a PPDU and receives the PHY-RXSTART.indication primitive of the HE / EHT / UHR PPDU on the BSS primary channel, and the following conditions are met, the NPCA primary channel may switch You can switch to this. a. PPDU is classified as inter-BSS PPDU by STA. b. The remaining period of the PPDU is the last received or transmitted NPCA Minimum corresponding to that BSS. It is greater than the value shown in the Duration Threshold field. c. The 20 / 40 / 80 / 160MHz channels occupied by the PPDU are the bandwidth fee of the PPDU's PHY preamble. Identified by STA based on the channel allocation of the band and the corresponding bandwidth, and occupied by PPDU The channel does not overlap with the NPCA primary channel.

[0180] In NPCA operation, the transmission of STA's PPDU on the NCPA primary channel includes at least the NPCA primary channel, is a channel within the AP's BSS bandwidth, and does not include channels occupied by inter-BSS traffic that cause the STA to switch from the BSS primary channel to the NPCA primary channel, nor does it include punctured channels.

[0181] AP includes an information element containing information related to Non Primary Channel Access. A frame may be sent. When performing Non Primary Channel Access, the AP sends a frame containing an information element that includes information related to Non Primary Channel Access. 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 indicates that Non Primary Channel Access is disabled, Non Primary Channel Access will not be performed. For example, the UHR operation element may indicate information for controlling the UHR STA. For example, the UHR operation element may indicate information for Non Primary Channel Access. The tion element may consist of one or more fields. The UHR operation element may include a field indicating the Element ID. The 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.

[0182] The management frame may include UHR Capabilities and / or UHR operations. The Beacon frame may include UHR Capabilities and / or UHR operations. The Association Request frame may include UHR Capabilities and / or UHR operations. The Association Response frame may include UHR Capabilities and / or UHR operations. The Reassociation Request frame may include UHR Capabilities and / or UHR operations. The Reassociation Response frame may include UHR Capabilities and / or UHR operations. The Probe Request frame may include UHR Capabilities and / or UHR operations. The Probe Response frame may include UHR Capabilities and / or UHR operations. UHR Capabilities are UHR It may also be called the Capabilities element. UHR Operation is the UHR Operation element. It may also be called by this name.

[0183] The UHR capabilities element may include several fields used to advertise the UHR capabilities of the UHR STA. For example, the UHR capabilities element may consist of an Element ID field, a Length field, an Element ID Extension field, a UHR MAC Capabilities Information field, and other fields. The UHR MAC Capabilities Information field may include an NPCA Supported field. The NPCA Supported field indicates whether the STA supports NPCA operations. This may also be indicated. The NPCA Supported field may be a 1-bit field. For example, if the NPCA Supported field is 1, it may indicate that the NPCA operation is supported. Good. If the NPCA Supported field is 0, it may indicate that the NPCA operation is not supported.

[0184] The operation of the UHR STA may be controlled by the UHR operation element. When operating in the 2.4GHz band, the operation of the UHR STA within the BSS may be controlled by the HT operation element and / or the VHT operation element and / or the HE operation element and / or the EHT operation element and / or the UHR operation element. Operation of the UHR STA within the BSS When operating in the 5GHz band, it may be controlled by an HT operation element and / or a VHT operation element and / or an HE operation element and / or an EHT operation element and / or a UHR operation element. The operation of the UHR STA in the BSS is When operating in the 6GHz band, it may be controlled by an HT operation element and / or a VHT operation element and / or a HE operation element and / or an EHT operation element and / or a UHR operation element.

[0185] A UHR operation element may consist of fields such as Element ID, Length, Element ID Extension, UHR Operation Parameters, and UHR Operation Information. For example, the UHR Operation Parameters field may include the NPCA Operation Information Present field. The NPCA Operation Information Present field indicates whether NPCA operation is enabled on the AP that sends this field. It may also be indicated. The NPCA Operation Information Present field may indicate whether the NPCA Operation Information field exists in the UHR Operation Information field. For example, a value of 1 in the NPCA Operation Information Present field may indicate that the NPCA operation is enabled and that the NPCA Operation Information field exists in the UHR Operation Information field. If this value is 0, it may indicate that NPCA operation is not enabled and that the NPCA Operation Information field does not exist in the UHR Operation Information field. The NPCA Operation Information field may include the NPCA Primary channel field, NPCA Minimum Duration Threshold field, NPCA Switching Delay field, NPCA Switch Back Delay field, etc. The NPCA Primary channel, NPCA Minimum Duration Threshold, NPCA Switching Delay, and NPCA Switch Back Delay fields may be fields other than the NPCA Operation Information field. This may be contained within a subfield, element, or frame. The NPCA primary channel field is switched for the NPCA AP and its associated NPCA STA to perform the NPCA operation. The channel number of the secondary channel within the BSS bandwidth corresponding to the channel may also be indicated. The NPCA Minimum Duration Threshold field may indicate the minimum duration of inter-BSS activity. Good. The NPCA Minimum Duration Threshold field is defined as the NPCA STA being connected to the NPCA primary channel. Before switching and performing the NPCA operation, it must be indicated on the BSS primary channel. The minimum duration of the Inter-BSS activity may be indicated. For example, the Inter-BSS activity may be Inter-BSS PPDU or Inter-BSS TXOP. The NPCA Switching Delay field is STA Or the time required for the AP to switch from the BSS primary channel to the NPCA primary channel. The NPCA Switching Delay field may be shown in units of 4 microseconds. The NPCA Switch Back Delay field may show the time required for the STA or AP to switch from the NPCA primary channel to the BSS primary channel. The NPCA Switching Delay field may be shown in units of 4 microseconds.

[0186] An STA that supports NPCA operation may also be called an NPCA STA. Supporting APs may also be referred to as NPCA APs. For example, an NPCA STA sets the NPCA Supported field in the UHR MAC Capabilities Information field of the UHR Capabilities element to 1. This is also acceptable. For example, NPCA AP sets the NPCA Operation Information Present field to 1. By doing so, the NPCA operation of BSS may be enabled. NPCA AP sets the NPCA Operation Information Present field to 0 to indicate that the NPCA operation is disabled. It is also possible to do so. The NPCA AP includes the NPCA operation information field in the UHR operation element, and the NPCA AP uses the NPCA Switching Delay field and the NPCA Switch Back Delay field. NPCA Switching Delay and NPCA Switch Back Delay may be indicated respectively. STAs that support NPCA operation pass NPCA Switching Delay and NPCA Switch Back Delay through the frame. It is acceptable to know. NPCA APs use untriggered UL transmissions on the NPCA primary channel. You may enable or disable it. The NPCA Operation Information field is NPCA Primary This may include fields such as the channel field, NPCA Minimum Duration Threshold field, NPCA Switching Delay field, and NPCA Switch Back Delay field. If the value of the NPCA Operation InformationPresent field received later is 0, the NPCA STA does not need to switch to the NPCA primary channel for the NPCA operation. If the value of the NPCA Operation InformationPresent field transmitted last is 0, the NPCA AP will not switch to the NPCA primary channel for the NPCA operation. Therefore, it is not necessary to switch to the NPCA primary channel.

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

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

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

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

[0191] 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. NPCA secondary channels may be defined as an NPCA secondary 20MHz channel, an NPCA secondary 40MHz channel, and an NPCA secondary 80MHz channel. The NPCA secondary 20MHz channel may be a 20MHz channel related to the NPCA primary channel. 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 possible that the NPCA secondary 80MHz channel is an 80MHz channel in the NPCA other than the NPCA primary 80MHz channel with a 160MHz bandwidth. The NPCA secondary channel may be referred to in ways other than "NPCA secondary channel". For example, the NPCA secondary channel may be called a secondary secondary channel. NPCA secondary 20MHz channel The NPCA secondary 20MHz channel may be referred to by a name other than "NPCA secondary 20MHz channel." For example, the NPCA secondary 20MHz channel may be referred to as "secondary secondary 20MHz channel." The NPCA secondary 40MHz channel may be referred to by a name other than "NPCA secondary 40MHz channel." For example, the NPCA secondary 40MHz channel is referred to as the secondary secondary 40MHz channel. It is also acceptable to refer to the NPCA secondary 80MHz channel by a different name. For example, the NPCA secondary 80MHz channel may be called the secondary secondary 80MHz channel. In NPCA, the NPCA primary channel is the channel It is also acceptable if the access information is provided.

[0192] The NPCA primary 20MHz channel may be a 20MHz channel used in NPCA for transmission and / or reception and / or carrier sensing. The NPCA primary 40MHz channel may be a 40MHz channel used in NPCA for transmission and / or reception and / or carrier sensing. The NPCA primary 80MHz channel may be an 80MHz channel used in NPCA for transmission and / or reception and / or carrier sensing. It is also acceptable. The NPCA primary 160MHz channel is used for transmitting and / or receiving in NPCA. It may also be a 160MHz channel used for transmission and / or carrier sensing. The NPCA secondary 20MHz channel is used in NPCA for transmission and / or reception and / or carrier sensing. The NPCA secondary 40MHz channel may be a 20MHz channel used for sensing. The NPCA secondary 80MHz channel may be an 80MHz channel used for transmitting and / or receiving and / or carrier sensing in the NPCA. The NPCA secondary 160MHz channel may be a 20MHz channel used for transmitting and / or receiving and / or carrier sensing in the NPCA. / or it may be a 160MHz channel used for carrier sensing.

[0193] 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 on the Operating channel. For example, a Beacon may not be transmitted on the NPCA Operating channel. The NPCA operating channel may be a channel within the operating channel.

[0194] 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 An NPCA primary 40MHz channel may be configured. The NPCA primary 80MHz channel is a channel within the NPCA operating channel and may be a 40MHz channel that includes the NPCA primary channel but does not include the primary channel. The NPCA operating channel width may have a smaller bandwidth than the operating channel width.

[0195] 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. It 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 a transmission with a channel width of 80 MHz transmitted using 1308, 1307, 1306, and 1305. Here, 1308, 1307, and 1305 may each be NPCA secondary channels. The 80 MHz transmission 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 that constitute 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 that constitute the NPCA secondary 40MHz channel, and notify the STA in a frame. The AP may also notify the STA that 80MHz is the NPCA operating channel width. The AP may, The AP may notify the STA of an 80MHz channel consisting 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.

[0196] 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. This 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.

[0197] 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 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. It may be an entry to indicate the channel state. NPCA secondary20 may be an entry to indicate that the NPCA secondary 20MHz 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 to indicate the channel state of the NPCA secondary 40MHz channel. NPCA secondary40 may indicate 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.

[0198] 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. A MAC layer that receives a PHY-CCA.indication primitive with STATUS IDLE and channel-list parameter {NPCA primary} may determine that the NPCA primary channel is idle and the primary channel is busy. A MAC layer that receives a PHY-CCA.indication primitive with STATUS BUSY and channel-list parameter {NPCA primary} may determine that the NPCA primary channel is busy. A MAC layer that receives a PHY-CCA.indication primitive with STATUS BUSY and channel-list parameter {NPCA primary} may determine that both the NPCA primary channel and the primary channel are busy. The channel-list parameter {NPCA primary} may also be called {secondary primary}. 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.

[0199] STA or AP is related to the PHY-CCA indication primitive of the NPCA secondary channel. It may be issued. The PHY-CCA.indication primitive associated with the NPCA secondary channel may be issued to indicate to the PHY (physical layer) that the NPCA secondary channel is idle or busy. {NPCA secondary} may be a channel-list parameter for the NPCA secondary channel. For example, if the NPCA secondary channel is idle, The physical layer of the STA or AP may issue a PHY-CCA.indication primitive with STATUS = IDLE and channel-list parameter = {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 with STATUS = BUSY and channel-list parameter = {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.

[0200] A table may be defined to define the meaning of the channel-list parameter entries in PHY-CCA.indication. For example, the meaning of Channel-list parameter entry{NPCA primary} may indicate that STA is busy on the NPCA primary channel. For example, the meaning of Channel-list parameter entry{NPCA secondary} may indicate that STA is busy on the NPCA secondary channel. For example, the meaning of channel-list parameter entry{NPCA secondary} may indicate that STA is busy on both the NPCA secondary channel and the primary channel. For example, the meaning of channel-list parameter entry{NPCA secondary20} may indicate that STA is busy on the NPCA secondary 20MHz channel. For example, the meaning of channel-list parameter entry{NPCA secondary20} may indicate that STA is busy 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.

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

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

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

[0204] 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 more It may contain multiple parameters.

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

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

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

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

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

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

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

[0212] The PHY-RXEND.indication primitive may be a primitive used by the PHY to indicate to the local MAC entity that the currently received PPDU has completed. The PHY-RXEND.indication primitive may include the RXERROR parameter, which indicates NoError or an error state. One or more values ​​may be transmitted. The RXERROR parameter may represent NoError, FormatViolation, CarrierLost, UnsupportedRate, or Filtered. NoError may be used to indicate that no errors occurred during the PHY's receiving process. FormatViolation indicates 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.

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

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

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

[0216] 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. TB PPDU may also be referred to as PPDU. TB PPDU may also be called PPDU.

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

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

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

[0220] 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 This refers to the NPCA primary channel or the NPCA secondary 20MHz channel or the NPCA secondary 4 When the AP receives the PPDU on the 0MHz channel or the NPCA secondary 80MHz channel, it may issue a PHY-RXSTART.indication primitive. 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, when the AP 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, it may issue a PHY-RXSTART.indication primitive. 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.

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

[0222] 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, PHY Header, and PSDU. The non-HT PPDU format may consist of a PHY Preamble, SIGNAL, and DATA. DATA may consist of a SERVICE field, PSDU, Tail, and Pad Bits. SIGNAL is the RATE field. 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.

[0223] 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 tone of the L-STF field The number 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 is 48, and the number of tones in the L-LTF field is 104. 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.

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

[0225] EHT PPDU may also be EHT TB PPDU. EHT TB PPDU may be referred to as EHT PPDU. EHT PPDU may also be EHT MU PPDU. EHT MU PPDU may be referred to as EHT PPDU. EHT MU PPDU may be an EHT PPDU format used for transmissions that are not responses to a trigger frame. EHT MU PPDU may transmit one or more PSDUs. EHT TB PPDU may be an EHT PPDU format used for transmitting responses to a trigger frame. EHT TB PPDU may transmit one PSDU. The EHT MU PPDU format includes L-STF field, L-LTF field, L-SIG field, RL-SIG field, U-SIG field, and 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.

[0226] 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. It may be a PPDU used for... UHR MU PPDU may transmit one or more PSDUs. UHR TB PPDU may be a PPDU used to transmit a response to a Trigger frame using the UHR PPDU format. UHR TB PPDU may transmit one PSDU. UHR TB PPDU may transmit multiple PSDUs. For example, the UHR MU PPDU format may have an L-STF field, L-LTF Field, L-SIG Field, RL-SIG Field, U-SIG Field, 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.

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

[0228] 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 and the CH_BANDWIDTH parameter is NON_HT_CBW40, CBW40, CBW80, CBW160, or CBW80+80, or CBW320. 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.

[0229] 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 have a Type subfield in the Frame Control field within the MAC header that indicates Control, and a subtype subfield that 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.

[0230] 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 resources for sending one or more TB PPDUs. A MU-RTS trigger frame may allocate resources for one or more PPDUs that are not TB PPDUs.

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

[0232] A trigger frame may consist of fields such as Frame Control, Duration, RA, TA, Common Info, User Info List, padding, and FCS. A trigger frame may also include fields other than those mentioned above.

[0233] The User Info List field may have one or more variants. For example, it may have a Special User Info field, an HE variant User Info field, an EHT variant User Info field, a UHR variant User Info field, etc. There may be fields. The length of all User Info fields within the User Info List field of the Trigger frame may be the same. The length of all User Info fields within the User Info List field of the Trigger frame may be different. The User Info field addressed to STA may be an HE variant User Info field, an EHT variant User Info field, or a UHR variant User Info field. It may also be a User Info field other than those mentioned above. For example, in a Trigger frame, User If a specific bit in the Info field (e.g., B39) is set to a certain value (e.g., 0) and a specific bit in the Common Info field (e.g., B54) is set to a certain value (e.g., 1), then the User Info field may be an HE variant addressed to EHT or UHR. In this case, it may be an EHT variant or a UHR variant. Certain bits (e.g., B39) in the HE variant User Info field may be reserved for HE STA. Certain bits (e.g. For example, B39) is a value determined by the EHT AP in the HE variant User Info field (for example). If set to 0), and if it is an EHT variant User Info field, even if it is a PS160 subfield That's good. For example, if a certain bit in the User Info field is set to a certain value in the Trigger frame, and a certain bit in the Common Info field is set to a certain value, the User Info field may be an HE variant, an EHT variant, or a UHR variant. The certain bit (e.g., B39) is set to a certain value (e.g., 0) by the UHR AP in the case of an HE variant User Info field. ) is set to, and if it is the EHT variant User Info field, it may be the PS160 subfield. For example, a Table may define valid combinations of certain bits in the Common Info field (e.g., B54 and B55), certain bits in the User Info field (e.g., B39), the presence of a Special User Info field in the Trigger frame, a variant of the User Info field, and the corresponding TB PPDU type. For example, the certain bits may be any of B0 through B63. It may also be any bit. For example, a value may be 0, 1, 2, or 3.

[0234] The Common Info field may be an HE variant Common Info field, an EHT variant Common Info field, or a UHR variant Common Info field. The Common Info field may also be a Trigger Type subfield and / or an UL Length subfield and / Alternatively, More TF subfield, and / or CS Required subfield, and / or UL BW subfield, and / or GI And HE-LTF Type subfield and / or MU-MIMO HE-LTF Mode subfield and / or Number Of HE-LTF Symbols And Midamble Periodicity subfield and / or UL STBC subfield and / or LDPC Extra Symbol Segment subfield and / or AP Tx Power subfield and / or Pre-FEC Padding Factor subfield and / or PE Disambiguity subfield and / or UL It may include subfields such as Spatial Reuse subfield and / or Doppler subfield and / or UL HE-SIG-A2 Reserved subfield and / or Reserved subfield and / or Trigger Dependent Common Info subfield and / or GI And HE-LTF Type / TXS Mode subfield and / or GI And EHT-LTF Type / TXS Mode subfield and / or Number Of HE / EHT-LTF Symbols subfield and / or HE / EHT P160 subfield and / or Special User Info Field Flag subfield and / or EHT Reserved subfield and / or GI And UHR-LTF Type / TXS Mode subfield and / or Number Of HE / EHT / UHR-LTF Symbols subfield and / or HE / EHT / UHR P160 subfield and / or Special User Info Field Flag subfield and / or EHT Reserved subfield and / or UHR Reserved subfield.

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

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

[0237] 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 in the HE TB PPDU. For example, if the UL BW subfield value is 0, it may be 20 MHz. If the UL BW subfield value is 1, it may be 40 MHz. If the UL BW subfield value is 2, it may be 80 MHz. If the UL BW subfield value is 3, it may be 80+80 MHz or 160 MHz. The UL BW subfield in the EHT variant Common Info field, together with the UL BW Extension subfield in the Special User Info field, is used in the EHT TB PPD. The bandwidth of the U-SIG field of U may be indicated. The UL BW subfield of the UHR variant Common Info field may indicate the bandwidth of the U-SIG field of the UHR TB PPDU together with the UL BW Extension subfield of the Special User Info field. For example, if the UL BW subfield is 0 When the UL BW Extension subfield is 0, the bandwidth of the TB PPDU may be 20 MHz. When the UL BW subfield is 1 and the UL BW Extension subfield is 0, the bandwidth of the TB PPDU may be 40 MHz. When the UL BW subfield is 2 and the UL BW Extension subfield is 0, the bandwidth of the TB PPDU may be 80 MHz. When the UL BW subfield is 3 and the UL BW Extension subfield is 1, the bandwidth of the TB PPDU may be 160 MHz. When the UL BW subfield is 3 and the UL BW Extension subfield is 2, the bandwidth of the TB PPDU may be 320 MHz. When the UL BW subfield is 3 and the UL BW Extension subfield is 3, the bandwidth of the TB PPDU may be 320 MHz. The UL BW Extension subfield may also be called the UL Bandwidth Extension subfield. Good. The UL Bandwidth Extension subfield may, together with the UL BW subfield in the Common Info field, indicate the bandwidth of the requested TB PPDU. The TB PPDU is the EHT TB PPDU. That's fine. TB PPDU may also be UHR TB PPDU.

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

[0239] The HE / EHT P160 subfield of the EHT variant Common Info field is required at Primary 160MHz. The HE / EHT P160 subfield of the EHT variant Common Info field may be set to 0 to indicate that the requested TB PPDU is an EHT TB PPDU. It may be set to 1 to indicate that it is a TB PPDU. The Special User Info Field Flag subfield of the EHT variant Common Info field is set to 0, and the EHT variant Common Info It may also indicate that the Trigger frame containing the field contains the Special User Info field. The Trigger Dependent Common Info subfield of the Common Info field may exist based on the value of the Trigger Type field.

[0240] The Special User Info field may be a User Info field that conveys extended shared information not provided by the Common Info field, rather than user-specific information. The Special User Info field may be identified by an AID12 value of 2007 and may exist in a Trigger frame generated by the AP. The AP does not have to use the value 2007 as the AID of the associated STA. The length of the Special User Info field is equal to the length of other User Info fields present in the same Trigger frame. It may be the same as the other field. The length of the Special User Info field may differ from the length of other User Info fields present in the same Trigger frame. If present, the Special User Info field may be placed immediately after the Common Info field in the Trigger frame and may convey information from the U-SIG field of the requested TB PPDU.

[0241] Special User Info field is AID12 subfield, PHY Version Identifier subfield, UL Bandwidth Extension subfield, EHT Spatial Reuse 1 subfield, EHT Spatial Reuse 2 It may consist of subfields such as U-SIG Disregard And Validate subfield, Reserved subfield, Trigger Dependent User Info subfield, UHR Spatial Reuse 1 subfield, UHR Spatial Reuse 2 subfield, etc. The UL Bandwidth Extension subfield may indicate the bandwidth of the requested TB PPDU together with the UL BW subfield in the Common Info field. The PHY Version Identifier subfield may indicate the PHY version of the requested TB PPDU. The PHY Version Identifier subfield may indicate the PHY version of the requested TB PPDU other than the HE TB PPDU. For example, EHT may be indicated. UHR may be indicated.

[0242] 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. These include the AID12 subfield, RU Allocation subfield, UL FEC Coding Type subfield, UL HE MCS subfield, UL DCM subfield, SS Allocation / RA-RU Information subfield, UL Target Receive Power subfield, and Trigger Dependent User Info subfield. It may consist of subfields such as UL EHT MCS, SS Allocation, PS160, and UL UHR-MCS. The User Info field is an HE variant User Info field. It is also acceptable. The User Info field may be an EHT variant User Info field. The User Info field may be a UHR variant User Info field. The HE variant User Info field may be a User Info field. The EHT variant User Info field may be a User Info field. The HE variant User Info field may be called a User Info field. The EHT variant User Info field may be called a User Info field. UHR variant User The Info field may also be called the User Info field. The User Info field may also be called the Special User Info field.

[0243] 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. The encoding of the AID12 subfield may differ for each Variant. The AID12 subfield may be encoded according to a different Table definition for each Variant. For example, the AID12 subfield of the HE variant User Info field may be a value between 1 and 2007. The AID12 subfield of the EHT variant User Info field may be a value between 1 and 2006. The AID12 subfield of the UHR variant User Info field may be a value between 1 and 2006.

[0244] 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. i. If the UL BW subfield indicates 20MHz, the mapping of RU to the RU index may be defined in a Table. If the UL BW subfield indicates 40MHz, the mapping of RU to the RU index may be defined in a Table. If the UL BW subfield indicates 80MHz, 160MHz, or 80+80MHz, the mapping of RU to the RU index may be defined in a Table. When the UL BW subfield indicates 20MHz If the UL BW subfield indicates 40MHz, or if the UL BW subfield indicates 80MHz, 160MHz, or 80+80MHz, the mapping of RUs to the RU index may be defined in the respective Table. The RU size and location may be identified by the RU Allocation subfield in the HE variant User Info field and the UL BW subfield in the Common Info field.

[0245] 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) The icant 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.

[0246] The RU Allocation subfield of the EHT variant User Info field or UHR variant User Info field in the trigger frame may identify the size and location of the RU or MRU, along with the UL BW subfield of the Common Info field, the UL BW Extension subfield of the Special User Info field, and the PS160 subfield of the EHT variant User Info field or UHR variant User Info field. The mapping of B7 to B1 of the RU Allocation subfield and the settings of B0 and PS160 subfield of the RU Allocation subfield of the EHT variant User Info field or UHR variant User Info field may be defined in a table (Figure 14). Here, the bandwidth is obtained from the defined combination of UL BW subfield and UL BW Extension subfield, and X1 and N This may be obtained from a Table (Lookup Table, Figure 15). N, and / or X1 is It may be used to determine the PHY RU or MRU.

[0247] Figure 14 shows the RU Allocation subfield of the User Info field according to one aspect of this embodiment. This figure shows an example of an encoding table. Figure 14 may also be referred to as the Table. Figure 14 may also be a diagram showing a portion of the encoding table for the RU Allocation subfield of the User Info field. Figure 14 may be used (defined) to identify the size and location of the RU or MRU and / or the PHY RU or MRU index, along with the RU Allocation subfield of the EHT variant User Info field or UHR variant User Info field of the Trigger frame, and / or the UL BW subfield of the Common Info field and / or the UL BW Extension subfield of the Special User Info field and / or the PS160 subfield of the EHT variant User Info field or UHR variant User Info field. B7 to B1 of the RU Allocation subfield Mapping and RU of EHT variant User Info field or UHR variant User Info field The settings for the B0 and PS160 subfields of the Allocation subfield may be defined in Figure 14. The RU or MRU size and RU or MRU index are derived from B7-B1 and bandwidth of the RU Allocation subfield. This may be determined. For example, if B7-B1 of the RU Allocation subfield shows 0 and the bandwidth is When indicating 20MHz, 40MHz, 80MHz, 160MHz, or 320MHz, the RU or MRU size is 26. The RU or MRU index may be RU1. Here, the RU Allocation subfield is B7-B1. The values ​​from 0 to 8 may correspond to RU1 to RU9 of the RU or MRU index, respectively. In other words, if B7-B1 of the RU Allocation subfield is 0, it corresponds to RU1; if it is 1, it corresponds to RU2; and if it is 2... If it's RU3, it corresponds to RU4; if it's RU4, it corresponds to RU5; if it's RU6, it corresponds to RU7; if it's RU7, it corresponds to RU8; and if it's RU9. It is permissible. The PHY RU or MRU index can be set to a predetermined value (e.g., 37, 16, 8, 4, 2, 1). ), and / or, N, and / or, X1, and / or, RU index, and / or Alternatively, it may be determined from the MRU index. For example, the PHY RU or MRU index may be determined by the 37 × N + RU index. The PHY RU or MRU index may also be determined by the 16 × N + RU index. The PHY RU or MRU index may be determined by the N+RU index. The PHY RU or MRU index is X The PHY RU or MRU index may be determined by 1 + RU index. The PHY RU or MRU index may be determined by the RU index. The PHY RU or MRU index may be determined by 12 × N + MRU index. The PHY RU or MRU index may be determined by 4 × X1 + MRU index. The PHY RU or MRU index may be determined by the MRU index. The PHY RU or MRU index may be determined by methods other than those described above. PS160 subfield, and / or B0 of the RU Allocation subfield, and / or B7-B1 of the RU Allocation subfield, and / or Bandwidth, and / or RU or MRU size, and The method (formula) for determining the PHY RU or MRU index may differ depending on the value of the RU or MRU index.

[0248] The B0 value of the RU Allocation subfield may be set to 0 to indicate that RU or MRU allocation is applied to the primary 80MHz channel when the PS160 subfield is 0 and the RU or MRU size is 996 tones or less, and may be set to 1 to indicate that RU allocation is applied to the secondary 80MHz channel of the primary 160MHz. The B0 value of the RU Allocation subfield may be set to 0 to indicate that RU or MRU allocation is applied to the lower 80MHz of the secondary 160MHz when the PS160 subfield is 1 and the RU or MRU size is 996 tones or less. The PS160 subfield may be set to 1 to indicate that the RU or MRU allocation applies to the upper 80 MHz of the secondary 160 MHz. If the size of the RU or MRU is 2 × 996 tones or less, the PS160 subfield may be set to 0 to indicate that the RU or MRU allocation applies to the primary 160 MHz channel, and to 1 to indicate that the RU or MRU allocation applies to the secondary 160 MHz channel. Otherwise, the PS160 subfield may be used together with the RU Allocation subfield to indicate the RU or MRU index. The PHY RU or MRU index in the Table (Figure 14) may indicate the assigned RU or MRU index. A PPDU extending above 160 MHz may consist of multiple 80 MHz frequency subblocks. The tone plan and RU allocation for each 80MHz frequency subblock are based on the 80 MHz PPDU. It can be the same as this.

[0249] Figure 15 shows an example of a Lookup Table for N according to one aspect of this embodiment. This may be a diagram showing the Lookup Tables for N and X1. Figure 15 may be referred to as the Table. Figure 15 may be referred to as the Lookup Table. Figure 15 is the Configuration and / or Based on B0 of the PS160 and / or RU allocation subfield, X0 and / or X1 It may be a Table used (defined) to determine the name and / or N. For example, the Configuration may be determined based on the primary 80MHz channel and / or the secondary 80MHz channel and / or the secondary 160MHz channel determined by the channel frequency. For example, the Configuration may be determined based on the primary 80MHz channel and / or the secondary 80MHz channel and / or the secondary 160MHz channel determined by the channelization.

[0250] The table (Lookup table, Figure 15) may show N with different configurations. N may be equal to 2 × X1 + X0. When the bandwidth is 80 MHz or less, PS160, B0, X0, and X1 are set to 0. This may be done. If the bandwidth is 160MHz or less, PS160 and X1 are set to 0, and X0 is set to 0 to indicate that RU or MRU allocation is applied to the lower 80MHz frequency subblock. It is determined that RU or MRU allocation is applied to the upper 80MHz frequency subblock. It may be set to 1 to indicate that RU or MRU allocation applies to the lower 160MHz segment, and it may be set to 1 to indicate that RU or MRU allocation applies to the upper 160MHz segment. Within the 160MHz segment, X0 is allocated RU or MRU in the lower 80MHz frequency sub-segment. It may be set to 0 to indicate that it applies to the lock, and to 1 to indicate that the RU or MRU allocation applies to the upper 80MHz frequency subblock. The Configuration may indicate the frequency order of the primary 80MHz channel, secondary 80MHz channel, and secondary 160MHz channel. The order from left to right is from lower frequency to higher frequency. The order may be indicated. The primary 80MHz channel may be indicated by P80. Secondary The 80MHz channel may be denoted as S80. The secondary 160MHz channel may be denoted as S160. For example, [P80 S80] may indicate that the primary 80MHz channel is located at a lower frequency and the secondary 80MHz channel is located at a higher frequency. [S160 P80 S80] may indicate that the secondary 160MHz channel is located at the lowest frequency, the primary 80MHz channel is located at the second lowest frequency, and the secondary 80MHz channel is located at the third lowest frequency. This is also acceptable. P80 may be a value corresponding to the center frequency of the primary 80MHz channel. S80 may be a value corresponding to the index of the primary 80MHz channel. S80 may be a value corresponding to the center frequency of the secondary 80MHz channel. S80 may be a value corresponding to the index of the secondary 80MHz channel.

[0251] The B0 and PS160 subfields of the RU Allocation subfield may indicate the 80 MHz frequency subblock where the RU or MRU is located, in the case of 26-tone RU, 52-tone RU, 106-tone RU, 242-tone RU, 484-tone RU, 996-tone RU, 52+26-tone RU, and 106+26-tone RU. The 80 MHz frequency subblock is indicated in the corresponding PHY RU or MRU index column of the Table (Figure 14) The values ​​may be derived based on the following: The PS160 subfield value may indicate the 160 MHz segment in which the RU or MRU is located, in the case of 2×996 tone RU, 996+484 tone MRU, and 996+484+242 tone MRU. In the case of 4×996 tone RU, 2×996+484 tone MRU, 3×996 tone MRU, and 3×996+484 tone MRU, the description of the RU or MRU index may be the same as the description of the PHY RU or MRU index for the 320 MHz channel.

[0252] If the bandwidth is 20 MHz, the mapping of the PHY RU index to RU may be defined in ascending order in the Table. The Table may define the RU data and pilot subcarrier index within the 20 MHz PPDU. If the bandwidth is 40 MHz, the mapping of the PHY RU index to RU may be defined in ascending order in the Table. The topping may be defined in ascending order in the Table. The Table contains data for RUs within a 40MHz PPDU. A pilot subcarrier index may also be defined. If the bandwidth is 80 MHz, the mapping of the PHY RU index to RU may be defined in ascending order in the Table. The Table may define the RU data and pilot subcarrier index within the 80 MHz PPDU. If the bandwidth is 160 MHz, the mapping of the PHY RU index to RU may be defined in ascending order in the Table. Good. The table defines the RU data and pilot subcarrier index within the 160MHz PPDU. Alternatively, if the bandwidth is 320 MHz, the mapping of the PHY RU index to RU may be defined in ascending order in the Table. The Table may define the RU data and pilot subcarrier index within the 320 MHz PPDU. Different Tables may be defined for each bandwidth.

[0253] If the bandwidth is 20 MHz, the mapping of the PHY RU index to the MRU is shown in the Table. The index may be defined in ascending order. The table may define the index of small-size MRUs within a 20 MHz PPDU. If the bandwidth is 40 MHz, the mapping of the PHY RU index to MRU may be defined in ascending order in the table. The table defines the index of small-size MRUs within a 40 MHz PPDU. It may be defined as follows: If the bandwidth is 80 MHz, the mapping of the PHY RU index to MRU may be defined in ascending order in multiple tables. The table may define the index of small-size MRUs in an 80 MHz PPDU. The table may define the index of large-size MRUs in an 80 MHz PPDU. It is also acceptable. If the bandwidth is 160 MHz, the mapping of the PHY RU index to the MRU is The tables may be defined in ascending order. The tables are small-size MRUs within a 160MHz PPDU. You may define an index for . The Table may define an index for large-size MRUs within a 160 MHz PPDU. If the bandwidth is 320 MHz, the mapping of the PHY RU index to MRU is The tables may be defined in ascending order. The tables are small-size MRUs within a 320MHz PPDU. An index may be defined. The Table may define an index for large-size MRUs within a 320MHz PPDU.

[0254] RU location is for 20MHz, 40MHz, 80MHz, 160MHz, and 320MHz PPDU, It may be fixed as defined in each Table. In each Table, a subcarrier index of 0 may correspond to the DC tone. A negative subcarrier index corresponds to a tone lower than the DC tone. It corresponds to subcarriers of higher frequencies, and a positive subcarrier index corresponds to frequencies higher than the DC tone. It may also support subcarriers.

[0255] MRU is 26 tone RU, 52 tone RU, 106 tone RU, 242 tone RU, 484 tone RU, 996 tone RU RUs may consist of RUs and selected combinations of multiple RUs of 2 × 996 tone. RUs the same size as or larger than a 242 tone RU may be defined as large size RUs, and RUs smaller than a 242 tone RU may be defined as small size RUs. Small size RUs may be combined only with other small size RUs to form small size MRUs. Large size RUs may be combined only with other large size RUs to form large size MRUs.

[0256] The RU size may also be the number of tones. The RU size may be 26 tones, 52 tones, 106 tones, 242 tones, 484 tones, 996 tones, etc. A tone may also be a subcarrier. The number of tones may also 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. Subcarrier The interval may be a value other than those mentioned above. For example, the subcarrier interval of a non-HT PPDU may be 78.125 kHz. For example, the subcarrier interval of an HT PPDU may be 78.125 kHz. For example, the subcarrier interval of a VHT PPDU may be 78.125 kHz. For example, the subcarrier interval of an HE PPDU may be 78.125 kHz. For example, the subcarrier interval of an EHT PPDU The interval may be 78.125 kHz. For example, the subcarrier interval of a UHR PPDU may be 78.125 kHz. For example, the subcarrier interval of a non-HT PPDU may be 312.5 kHz. For example, the subcarrier spacing of HT PPDU may be 312.5 kHz. For example, VHT PPDU The subcarrier spacing may be 312.5 kHz. For example, the subcarrier spacing of HE PPDU The subcarrier interval may be 312.5 kHz. For example, the subcarrier interval of an EHT PPDU may be 312.5 kHz. For example, the subcarrier interval of a UHR PPDU may be 312.5 kHz. Different subcarrier intervals may be used for each PPDU. For example, the subcarrier interval of non-HT PPDU, HT PPDU, and VHT PPDU may be 78.125 kHz, while the subcarrier interval of HE PPDU, EHT PPDU, and UHR PPDU may be 312.5 kHz.

[0257] Figure 16 shows an example of the mapping of PHY RU index to RU according to one aspect of this embodiment. Figure 16 may be a Table that defines the mapping of PHY RU index to RU when the bandwidth is 160 MHz and the RU type (RU size) is 26 tone RU. Figure 16 may define the RU data and pilot subcarrier index in a 160 MHz PPDU. Figure 16 may be referred to as a Table. Tables of mapping PHY RU index to RU for other bandwidths may be defined. For example, Tables for 20 MHz, 40 MHz, 80 MHz, and 320 MHz may be defined respectively. Tables of mapping PHY RU index to RU for other RU types may be defined. The same RU (RU index) may be used for different RU types. Different tones may be assigned and mapped to the same RU (RU index) for different RU types. For example, RU1 for RU type 26 tone This corresponds to [-1011: -986], and RU1, which has 52 tones, may also correspond to [-1011: -96-]. For example, if the PHY RU index is 1, RU1[-1011:-986] in Figure 16 may correspond. The STA may determine the value of the PHY RU index based on the received Trigger frame (e.g., PHY RU index 1) and then send a TB PPDU using the corresponding RU (e.g., RU1) from the Table. The AP may use the value of the PHY RU index associated with the Trigger frame it sent (e.g., PHY RU index 1). From there, the corresponding RU (e.g., RU1) may receive a TB PPDU. -1011 may be a subcarrier index. -986 may be a subcarrier index. For example, [-1011: -986] means 26 subcarriers from subcarrier index -1011 to subcarrier index -986. It can also taste good. For example, even if the subcarrier index is indexed within the bandwidth Good. The subcarrier index may be indexed within the BSS bandwidth. The subcarrier index may be indexed within the PPDU bandwidth. In addition to the above, su The bcarrier index may be indexed.

[0258] For example, when the STA receives a trigger frame, it may determine the PHY RU index based on Figures 14 and 15, and then determine the mapping to the RU corresponding to the determined PHY RU index from Figure 16. In other words, when the STA receives a trigger frame, it may determine the PS160 subfield of the trigger frame. Determine the RU size and RU index from the RU Allocation subfield and / or UL BW subfield and / or UL BW Extension subfield and / or bandwidth; determine N and / or X1 and / or X0 from B0 in the Configuration and PS160 subfield and RU Allocation subfield; and determine the PHY RU index from the RU index and N and / or X1. Alternatively, the corresponding RU (data subcarrier) may be determined from the determined PHY RU index, / RU size, and / or bandwidth. For example, if the bandwidth is determined to be 160 MHz, the RU type to be 26 tone, and the PHY RU index to be 38 from Figures 14 and 15, then the [13:38] of RU38 in Figure 16 can be used. You may use this to send a TB PPDU. For example, the AP assigns the RU of the TB PPDU to the STA. In addition, the Trigger frame's PS160 subfield, RU Allocation subfield, UL BW subfield, UL BW You may also set the value of the Extension subfield. In other words, AP will set the PS160 subfield, RU Allocation subfield, UL BW subfield, and UL BW Extension subfield of the Trigger frame so that the PHY RU index becomes 38 from Figures 14 and 15 in order to assign RU38 in Figure 16 to STA. You may set a value.

[0259] AP may set or determine the values ​​of the RU Allocation subfield and / or PS160 subfield and / or UL BW subfield and / or UL BW Extension subfield of the Trigger frame in the frame processing unit AU7. AP may set or determine the values ​​of the RU Allocation subfield and / or PS160 subfield and / or UL BW subfield and / Alternatively, the AP may set or determine the value of the UL BW Extension subfield. The AP may set or determine the values ​​of the RU Allocation subfield and / or PS160 subfield and / or UL BW subfield and / or UL BW Extension subfield of the Trigger frame in the frame processing unit AU7 or the MAC layer processing unit AU4 to assign the RHY RU index to the STA. The AP may, The wireless transmitter / receiver AU6 may transmit a trigger frame. The AP may transmit a PPDU containing the trigger frame using the wireless transmitter / receiver AU6. The AP may transmit the RU Allocation subfield and / Alternatively, a PPDU containing a trigger frame including the PS160 subfield may be transmitted. The AP transmits wirelessly. The receiver AU6 may receive the TB PPDU. The AP may receive the TB PPDU with the RU allocated in the RU Allocation subfield and / or PS160 subfield of the Trigger frame at the radio transmitter / receiver AU6. The AP may receive a PPDU containing a TB PPDU with the RU allocated in the RU Allocation subfield and / or PS160 subfield of the Trigger frame at the radio transmitter / receiver AU6. The STA may receive the Trigger frame at the radio transmitter / receiver SU6. The STA receives the PPDU containing the Trigger frame at the radio transmitter / receiver SU6. The STA may receive a PPDU containing a Trigger frame containing the RU Allocation subfield and / or PS160 subfield in the wireless transmit / receive unit SU6. The STA may determine the RU Allocation subfield and / or PS160 subfield of the Trigger frame in the frame processing unit SU7. The STA may determine the RU Allocation subfield and / or PS160 subfield of the Trigger frame in the MAC layer processing unit SU4. The STA may determine the RU Allocation subfield and / or PS160 subfield of the Trigger frame. In the SU7 processing unit, the RU Allocation subfield and / or the PS160 subfield and / or The PHY RU index may be determined from the bandwidth and / or Configuration. The STA may determine the PHY RU index and TB PPDU from the Trigger frame in the MAC layer processing unit SU4. The STA may transmit the TB PPDU in the wireless transmit / receive unit SU6. The STA may determine the PHY RU index and TB PPDU from the Trigger frame in the wireless transmit / receive unit SU6. You may send TB PPDUs related to the PHY RU index determined based on this.

[0260] An AP sending a Trigger frame on the NPCA primary channel may indicate the RU index value that uses the NPCA primary channel as the reference primary channel. The Trigger frame may also include an explicit indication that it is being sent on the NPCA primary channel. If carrier sense is being performed on the NPCA primary channel, the Trigger frame should include the NPCA primary You may include an explicit indication that it is being sent on a channel. For example, explicit The indication may be shown using one or more fields and / or subfields of the trigger frame.

[0261] The PHY RU index may be determined in different ways depending on whether the trigger frame is received on the primary channel or on the NPCA primary channel. The PHY RU index may be determined using different values ​​depending on whether the trigger frame is received on the primary channel or on the NPCA primary channel.

[0262] Even if STA receives a trigger frame and sends a TB PPDU with the RU corresponding to the RHY RU index, Good. In NPCA, when STA receives a trigger frame, it uses TB with the RU corresponding to the RHY RU index. You may send a PPDU. The STA uses the received Trigger frame and Table to perform a PHY RU The index may be determined. The STA may determine the PHY RU index using the field and / or subfield of the received Trigger frame and the Configuration. The STA receives Using the field and / or subfield of the trigger frame, and the Configuration, A predetermined value (e.g., N, X0, X1) may be determined. The STA uses the field and / or subfield of the received Trigger frame and the predetermined value (e.g., N, X0, X1) to determine the PHY RU index. The STA may determine the PHY RU index. The STA may use a Table (e.g., Figures 14, 15, and 17) to determine the PHY RU index. The STA may use a Table (e.g., Figures 15 and 17) to determine a given value (e.g., N, X0, X1). The STA may use a Table (e.g., Figure 16) to determine the RU mapping corresponding to the determined PHY RU index.

[0263] The STA may receive a Trigger frame. The STA may determine the PHY RU index based on the Trigger frame. The STA will determine the field and / or subfield included in the Trigger frame. Based on the field and / or subfield included in the trigger frame and the configuration, a predetermined value (e.g., N, X1, X0) may be determined. The STA may determine the PHY RU index based on the field and / or subfield included in the trigger frame and the configuration. The STA determines the RU corresponding to the PHY RU index. It may be fixed. The STA may send the TB PPDU assigned in the Trigger frame.

[0264] The STA receives a Trigger frame, which includes a User Info field, which includes a RU Allocation subfield and a PS160 subfield, which includes predetermined bits of the RU Allocation subfield, the PS160 subfield, and the first Configuration A predetermined value is determined, and the PHY RU or MRU index is determined using the predetermined value. The first configuration consists of an NPCA primary 80MHz channel and an NPCA secondary 80MHz channel. The frequency order is shown, and the NPCA primary 80MHz channel may be denoted by NP80, and the NPCA secondary 80MHz channel may be denoted by NS80. For example, the first configuration may correspond to the configuration in Figure 17. For example, a given bit may be B0. For example, the predetermined value may be N. The STA may receive a trigger frame, determine a predetermined value from the RU Allocation subfield and PS160 subfield and the first Configuration contained in the User Info field of the trigger frame, and use the predetermined value to determine the PHY RU or MRU index. The first Configuration indicates the frequency order of the NPCA primary 80MHz channel and the NPCA secondary 80MHz channel, where the NPCA primary 80MHz channel is indicated by NP80. The NPCA secondary 80MHz channel may be indicated by NS80.

[0265] Figure 17 is a diagram showing an example of a Lookup Table for N in NPCA according to one aspect of this embodiment. Yes. Figure 17 may be a diagram showing a lookup table of N and X1 in NPCA. The table (lookup table, Figure 17) may show N with a different configuration. N is equal to 2 × X1 + X0. The Configuration may also indicate the frequency order of the NPCA primary 80MHz channel and the NPCA secondary 80MHz channel. The NPCA primary 80MHz channel may be denoted as NP80, and the NPCA secondary 80MHz channel may be denoted as NS80. For example, [NP80 NS80] is The NPCA primary 80MHz channel is located at a lower frequency, while the NPCA secondary 80MHz channel... It may be indicated that el is located at a higher frequency. Based on the Table, X0 and / or X1 and / or N may be determined from B0 of the bandwidth and / or Configuration and PS160 subfield and / or RU Allocation subfield. X1 may represent 0, 1, 2, or 3. X0 may represent 0, 1, 2, or 3. N is It may show 0, 1, 2, or 3. The Outputs of the Table (X0, X1, N) are shown in Figure 17. Other patterns may be defined. For example, bandwidth is 20MHz and Configuration is NP80. When PS160 is 0 and B0 is 0, N may be a value other than 0. For example, when bandwidth is 20MHz, Configuration is NP80, PS160 is 0, and B0 is 0, X1 and / or X0 may be a value other than 0. NP80 may be a value corresponding to the center frequency of the NPCA primary 80MHz channel. NP80 may also be a value corresponding to the index of the NPCA primary 80MHz channel. NS80 may be a value corresponding to the center frequency of the NPCA secondary 80MHz channel. NS80 may also be a value corresponding to the index of the NPCA secondary 80MHz channel.

[0266] A predetermined value may be determined from a predetermined bit in the RU Allocation subfield, the PS160 subfield, and the second Configuration. The second Configuration indicates the frequency order of the primary and secondary 80MHz and 160MHz channels, where the primary 80MHz channel is P80 The second configuration is shown as follows: The secondary 80MHz channel may be shown as S80. The Configuration may correspond to Figure 15. For example, the given value may be N. For example, the given bit may be B0. The second Configuration and the first Configuration may be defined in different tables. The second Configuration and the first Configuration may be defined in a single table.

[0267] Certain bits in the RU Allocation subfield are set to 0 to indicate that RU or MRU allocation is applied to the primary 80MHz channel or the NPCA primary 80MHz channel. This applies to the secondary 80MHz channel or the NPCA essential 80MHz channel. A value of 1 may be set to indicate that. For example, a given bit may be B0. Explicit indication that the trigger frame is being transmitted on the NPCA primary channel. If an explicit indication is included that the trigger frame is being transmitted on the NPCA secondary channel, a certain bit in the RU Allocation subfield may be set to 0 to indicate that the RU or MRU allocation is applied to the NPCA primary 80MHz channel. That's good too.

[0268] The NPCA primary channel is used when the primary channel is busy, and carrier sensing is performed on it. The channel is such that the NPCA primary 80MHz channel may be an 80MHz channel that includes the NPCA primary channel but does not include the primary channel.

[0269] The trigger frame may be transmitted on the NPCA primary channel.

[0270] The AP includes a transmission unit that transmits a trigger frame, the trigger frame includes a User Info field, the User Info field includes a RU Allocation subfield and a PS160 subfield, and determines a predetermined value from a predetermined bit of the RU Allocation subfield, the PS160 subfield, and a first Configuration, and uses the predetermined value to determine the PHY RU or MRU index. The first configuration is defined as having the frequency order of the NPCA primary 80MHz channel and the NPCA secondary 80MHz channel, where the NPCA primary 80MHz channel is indicated by NP80. The NPCA secondary 80MHz channel may be indicated by NS80. For example, the first configuration may correspond to the configuration in Figure 17. For example, a given bit may be B0. For example, a given value may be N.

[0271] A communication method for a terminal device, comprising the step of receiving a trigger frame, the trigger The frame may include a User Info field, the User Info field includes a RU Allocation subfield and a PS160 subfield, and the communication method may include determining a predetermined value from a predetermined bit of the RU Allocation subfield, the PS160 subfield, and a first Configuration, and using the predetermined value to determine a PHY RU or MRU index, the first Configuration indicating the frequency order of an NPCA primary 80MHz channel and an NPCA secondary 80MHz channel, the NPCA primary 80MHz channel being indicated by NP80 and the NPCA secondary 80MHz channel being indicated by NS80.

[0272] Figures 17 and 16 may be defined in a single table. The configuration may show the frequency order of the primary 80MHz channel and / or secondary 80MHz channel and / or secondary 160MHz channel and / or NPCA primary 80MHz channel and / or NPCA secondary 80MHz channel. The primary 80MHz channel and / or NPCA primary 80MHz channel may be denoted by P80. The secondary 80MHz channel and / or NPCA secondary 80MHz channel may be denoted by S80. This may be indicated by S160. The order from left to right may indicate an order from low frequency to high frequency. It indicates that the trigger frame was transmitted on the NPCA primary channel. In this case, P80 may be the NPCA primary 80MHz channel. If the trigger frame is indicated to have been transmitted on the NPCA primary channel, S80 may be the NPCA secondary 80MHz channel.

[0273] In NPCA operation, the B0 subfield of RU Allocation may be set to 0 to indicate that RU or MRU allocation is applied to the NPCA primary 80MHz channel, or to 1 to indicate that it is applied to the NPCA secondary 80MHz channel. It may be set to 0 to indicate that it applies to the 40MHz channel, and to 1 to indicate that it applies to the NPCA secondary 40MHz channel. In NPCA operation, the PS160 subfield may be set to a predetermined value (e.g., 0 or 1). In NPCA operation, the PS160 subfield may be set to 0 to indicate the NPCA primary 80MHz channel, and to 1 to indicate the NPCA secondary 80MHz channel. In NPCA operation, the PS160 subfield may be interpreted as different subfields. For example, in NPCA operation, the PS160 subfield may be interpreted as the trigger frame being on the NPCA primary channel. It may be used to indicate that something is being sent.

[0274] Even if the value of N is the same for the Trigger frame received on the NPCA primary channel and the Trigger frame received on the primary channel, the case where the Trigger frame is received on the primary channel and the NPCA When a trigger frame is received on the primary channel, the frequency position may be different. Even if the value of N is the same for the Trigger frame received on the NPCA primary channel and the Trigger frame received on the primary channel, the frequency position will be the same whether the Trigger frame is received on the primary channel or on the NPCA primary channel. Good. In other words, when the trigger frame received on the primary channel shows a bandwidth of 160MHz, a PHY RU index of 1, and an RU type of 26 tone, and when the trigger frame received on the NPCA primary channel shows a bandwidth of 160MHz, a PHY RU index of 1, and an RU type of 26 tone, The subcarrier's frequency position may be different. Trigger received on the primary channel. If the frame shows a bandwidth of 160MHz, a PHY RU index of 1, and a RU type of 26 tone, and the trigger frame received on the NPCA primary channel shows a bandwidth of 160MHz and a PHY RU index of 1 Even if the RU type is indicated as 26 tones, the frequency positions of the subcarrier may be the same.

[0275] Figure 18 shows an example of the process for determining the PHY RU index of STA according to one aspect of this embodiment. This is a diagram. STA is, The NPCA primary channel may receive a trigger frame (S1801). The STA may determine the PHY RU index in the NPCA based on the received trigger frame (S1802).

[0276] Figure 19 is a diagram showing an example of the process of sending a trigger frame by an AP according to one aspect of this embodiment. Yes. The AP may determine the PHY RU index to assign to the STA (S1901). The AP may send a trigger frame to notify the STA of the determined PHY RU index (S1902). .

[0277] As described above, in NPCA, the AP can assign a RU to the STA in the trigger frame. The STA can determine the PHY RU index or MRU index from the trigger frame received on the NPCA primary channel and transmit the TB PPDU. This invention allows the STA and AP to... In NPCA, it is possible to assign RUs and send TB PPDUs.

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

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

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

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

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

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

[0284] Furthermore, some or all of the terminal device and base station device in the above-described embodiments may be implemented as LSIs, which are typically integrated circuits, or as chipsets. Each functional block of the 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 creation 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.

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

[0286] 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]

[0287] 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 trigger frame, The aforementioned Trigger frame includes a User Info field, and the User Info field includes a RU Allocation subfield and a PS160 subfield. A predetermined value is determined from a predetermined bit in the RU Allocation subfield, the PS160 subfield, and the first Configuration, and the PHY RU or MRU index is determined using the predetermined value. Determined, The first configuration described above includes an NPCA primary 80MHz channel and an NPCA secondary 80MHz channel. The frequency order of the channels is indicated by NP80 for the NPCA primary 80MHz channel and NS80 for the NPCA secondary 80MHz channel. Terminal device

2. The terminal device according to claim 1, wherein a predetermined value is determined from a predetermined bit of the RU Allocation subfield, the PS160 subfield, and a second Configuration, the second Configuration indicating the frequency order of primary and secondary 80MHz and 160MHz channels, the primary 80MHz channel being indicated by P80 and the secondary 80MHz channel being indicated by S80. Place.

3. The predetermined bits in the RU Allocation subfield are set to 0 to indicate that the RU or MRU allocation is applied to the primary 80MHz channel or the NPCA primary 80MHz channel. Applicable to the secondary 80MHz channel or NPCA secondary 80MHz channel. The terminal device according to claim 1, wherein 1 is set to indicate that

4. The aforementioned NPCA primary channel, when the primary channel is busy, uses carrier sense The terminal device according to claim 1, wherein the channel in which the operation is performed is an 80MHz channel that includes the NPCA primary channel but does not include the primary channel.

5. The trigger frame is transmitted on the NPCA primary channel by the terminal according to claim 1. Device.

6. It includes a transmission unit that sends a trigger frame, The aforementioned Trigger frame includes a User Info field, and the User Info field includes a RU Allocation subfield and a PS160 subfield. A predetermined value is determined from a predetermined bit in the RU Allocation subfield, the PS160 subfield, and the first Configuration, and the PHY RU or MRU index is determined using the predetermined value. Determined, The first configuration described above includes an NPCA primary 80MHz channel and an NPCA secondary 80MHz channel. The frequency order of the channels is indicated by NP80 for the NPCA primary 80MHz channel and NS80 for the NPCA secondary 80MHz channel. Base station equipment.

7. A communication method for terminal devices, comprising the step of receiving a trigger frame, The aforementioned Trigger frame includes a User Info field, and the User Info field includes a RU Allocation subfield and a PS160 subfield. A predetermined value is determined from a predetermined bit in the RU Allocation subfield, the PS160 subfield, and the first Configuration, and the PHY RU or MRU index is determined using the predetermined value. Determined, The first configuration described above includes an NPCA primary 80MHz channel and an NPCA secondary 80MHz channel. A communication method that includes indicating the frequency order of channels, where the NPCA primary 80MHz channel is denoted as NP80 and the NPCA secondary 80MHz channel is denoted as NS80.

Images