Terminal, base-station device, and communication method

Abstract

To achieve efficient communication in a wireless LAN system.SOLUTION: It is determined whether or not an informationelement related to NonPrimaryChannelAccess has been received and an informationelement related to NonPrimaryChannelAccess has been received from an AP belonging to a different BSS, and in a case where a plurality of conditions are satisfied, the NAV is not updated, and one of the plurality of conditions is a condition that an informationelement related to NonPrimaryChannelAccess has not been received from the AP belonging to the different BSS.SELECTED DRAWING: Figure 14

Description

[Technical Field]

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

[0002] The Institute of Electrical and Electronics Engineers Inc. (IEEE) is currently studying ways to increase the speed and efficiency of frequency usage in wireless LAN (Local Area Network) communications. Currently, standardization of IEEE802.11bn, the successor to IEEE802.11be, has begun. Summary of the Invention [Problem to be solved by the invention]

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

[0004] (1) A first aspect of the present invention is a terminal device, comprising: a receiving unit that receives an information element related to Non-Primary Channel Access; and a control unit that determines whether or not an information element related to Non-Primary Channel Access has been received from an AP that belongs to a different BSS. If multiple conditions are met, the NAV is not updated, and one of the multiple conditions is A terminal device that does not receive information elements related to Non-Primary Channel Access from an AP that belongs to a different BSS.

[0005] (2) A second aspect of the present invention is a communication method used in a terminal device, comprising the steps of receiving an information element related to Non-Primary Channel Access, and determining whether or not the information element related to Non-Primary Channel Access has been received from an AP belonging to a different BSS. and determining whether or not the NAV is updated if a plurality of conditions are met. One of the conditions is that the APs belonging to the different BSSs are related to Non Primary Channel Access. A communication method under the condition that no information element corresponding to the specified condition has been received. [Effects of the Invention]

[0006] An efficient wireless communication system can be realized. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram illustrating an example of a wireless LAN system according to an aspect of the present embodiment. [Figure 2] FIG. 10 is a diagram illustrating an example of an OBSS according to an aspect of the present embodiment. [Figure 3] FIG. 10 is a diagram illustrating an example of the configuration of an STA according to an aspect of the present embodiment. [Figure 4] FIG. 10 is a diagram illustrating an example of a configuration of an AP according to an aspect of the present embodiment. [Figure 5] FIG. 2 is a diagram illustrating an example of a MAC frame format according to an aspect of the present embodiment. [Figure 6] FIG. 10 is a diagram illustrating an example of an A-MSDU according to one aspect of this embodiment. [Figure 7] FIG. 2 is a diagram illustrating an example of an A-MPDU according to an aspect of the present embodiment. [Figure 8] FIG. 10 is a diagram illustrating an example of fragmentation according to an aspect of an embodiment. [Figure 9] FIG. 2 is a diagram illustrating an example of a PPDU according to an aspect of the present embodiment. [Figure 10] FIG. 10 illustrates an example of a backoff procedure according to an aspect of the present embodiment. [Figure 11] FIG. 2 is a diagram illustrating an example of a NAV according to an aspect of the present embodiment. [Figure 12] FIG. 10 is a diagram illustrating an example of channel bonding according to one aspect of the present embodiment. [Figure 13] FIG. 10 is a diagram illustrating an example of a backoff procedure on an NPCA primary channel of a STA according to one aspect of this embodiment. [Figure 14] FIG. 10 is a diagram illustrating an example of a process related to a NAV update according to an aspect of the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, an embodiment of the present invention will be described.

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

[0010] The wireless LAN system in this embodiment includes an access point (AP) and a station. A network consisting of an access point and stations is called a Basic Service Set (BSS). A wireless LAN system may be composed of one or more stations. When the wireless LAN system is composed of two or more STAs, the wireless LAN system may be called a BSS.

[0011] The access point (AP) may be called a base station device. It may also be referred to as a terminal device.

[0012] FIG. 1 is a diagram illustrating an example of a wireless LAN system according to an aspect of the present embodiment. The wireless LAN system includes a station 103, a station 104, and an access point 102. may be referred to as a BSS.

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

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

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

[0016] An AP may be an entity that contains one STA and provides associated STA(s) access to distribution system services (DSS) over the wireless medium. An AP may contain a STA and a distribution system access function (DSAF). An AP may also be referred to as a STA. That is, the AP may also be a STA.

[0017] A non-AP STA (non-access point station) may be a STA that is not contained within an AP. For example, a non-AP STA may be a HT STA. A non-AP STA may be a VHT STA. A non-AP STA may be a HE STA. A non-AP STA may be an EHT STA. The non-AP STA may be a UHR STA. The non-AP STA is a STA other than the above-mentioned STA. A non-AP STA may also be referred to as an STA.

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

[0019] A BSS may be a set of STAs that have successfully synchronized using JOIN service primitives and one STA that has used the START primitive. For example, MLME-JOIN.confirm may be used as a JOIN service primitive. MLME-JOIN.confirm confirms synchronization with the BSS. As a JOIN service primitive, MLME-JOIN.request may be used. MLME-JOIN.request is a primitive to request synchronization with the BSS. For example, MLME-START.request may be used as the START primitive. MLME-START.request may be a primitive for a MAC entity to request that a new BSS be started. The primitive is an internal signal in the STA or AP. The internal signal here may be an internal signal used for information exchange between entities in different layers or different protocols, such as between an SME and an MLME, between an SME and a PLME, or between an MLME and a PLME.

[0020] An ESS is a set of one or more interconnected BSSs that appears as a single BSS at the Logical Link Control (LLC) layer of a STA associated with any of these BSSs. An Extended Service Set (ESS) may have a connection path via a WM between one of the APs that are members of the ESS and a non-AP STA. The communication areas (coverage) of multiple BSSs may partially overlap in an ESS. The distance between multiple BSSs may be large, and an ESS may access the coverage area covered by multiple BSSs as a wider coverage area. In other words, the communication area of ​​an ESS may be the same as or wider than the communication area of ​​a single BSS. The communication area formed by an ESS is called an ESA (Extended Service Area). This may be done.

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

[0022] FIG. 2 is a diagram showing an example of an OBSS according to one aspect of this embodiment. In FIG. 2, 202 201 may be AP#1. 203 may be STA#1. 204 may be STA#2. 201 may be BSS#1 consisting of 202, 203, and 204. 203 may be synchronized with 202. 204 may be synchronized with 202. 206 may be AP#2. 207 may be STA#3. 208 may be STA#4. 205 may be BSS#2 consisting of 206, 207, and 208. 207 may be 201 may be synchronized with 206. 208 may be synchronized with 206. 202 may not be synchronized with 207. 202 may not be synchronized with 208. 206 may not be synchronized with 203. 206 may not be synchronized with 204. 201 and 205 may be BSSs operating on the same channel. 205 may be considered an OBSS for 201. 201 may be considered an OBSS for 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.

[0023] A BSA may be a region that contains members of a BSS. A BSA may contain members of other BSSs. For example, in FIG. 2, 201 is a BSA that contains 203, 204, and 207. Here, 207 may be a member of another BSS.

[0024] An IBSS (Independent Basic Service Set) is a BSS that forms a self-contained network and does not provide access to the DS.

[0025] An addressable unit may be a station (STA). Physical and operational Characteristics may be defined by a modifier placed before the term STA. For example, in the case of location or mobility, the addressable unit is a fixed STA. ), mobile STA, and mobility STA. A STA is a destination that can be addressed, but does not (generally) have to be at a fixed location. It can have a number of different characteristics, each of which contributes to its function. For example, a single addressable unit may simultaneously have the characteristics of a portable STA, a QoS STA, a dependent STA, and a hidden STA. That's fine.

[0026] The architecture is designed to provide a WLAN that supports STA mobility transparently to higher layers. A BSS may consist of several interacting components. A BSS may be the basic building block of a LAN. The range over which member STAs of a BSS can communicate may be considered a coverage area. The set of all possible directional transmissions by member STAs is called a coverage area. , which may be referred to as BSA.

[0027] Physical limitations may determine the distance between direct STAs. An infrastructure BSS may be part of a network consisting of multiple BSSs. The architectural component for interconnecting infrastructure BSSs may be a DS for non-General Link (non-GLK) operation. The DS and Extended Service Set (ESS) may be mechanisms for extending connectivity for non-GLK operation. GLK operation may be achieved using bridges. The wireless medium and the DSM (Distribution System Medium) may be logically separated. Each logical medium may be used for different architectures. Recognizing that multiple media are logically distinct is key to understanding the flexibility of the architecture. The architecture is specified independently of the physical characteristics of a particular implementation. The DS provides the logical services required for address-to-destination mapping and seamless integration of multiple BSSs. The AP may enable support for mobile devices by providing the STA functionality and DSAF. The BSS is an entity with a Distribution System Access Function (BSS) that may provide associated STAs with access to the Distribution System over the wireless medium. Data between the BSS and the Distribution System is transmitted via the AP. The AP may contain STAs that are addressable on the wireless medium using their STA addresses. 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 the uncontrolled port, and It may be processed by the access entity. If the controlled port is authorized, the frame may conceptually pass through the DS.

[0028] DS and Infrastructure BSS allow wireless networks of any size and complexity. This network may be called an ESS (Extended Service Set). An ESS is a set of infrastructure BSSs connected by the same SSID, and may be connected by a DS. An ESS does not have to include a DS. To the LLC layer, an ESS is an IBSS. STAs within an ESS can communicate, and mobile STA(s) can A BSS may move between BSSs transparently to the LLC (within the same ESS). This may be commonly used to arrange coverage within a physical area. In an ESS, BSSs may be physically separated. In an ESS, BSSs may be logically separated. In ESS, the BSSs are physically co-located. This may be done to provide redundancy. In an ESS, one or more IBSS(s) or ESS(s) may be physically co-located with one or more ESS(s).

[0029] 3 is a diagram showing an example of the device configuration of an STA according to one aspect of this embodiment. 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 is a unit that combines 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 receives a wireless signal via the antenna unit SU1. Receive the number.

[0030] 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 physical layer processing in the physical layer processing unit SU3 is sent to the MAC layer processing unit SU4. The MAC layer processing unit SU4 performs processing related to the MAC layer function (MAC function) on the baseband signal. The signal that has undergone MAC layer processing 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 packets extracted from the received signal.

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

[0032] 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. The PLME and MLME provide their own layer management service interfaces. The PLME and MLME may be controlled by a Station Management Entity (SME), which is an entity independent of the layers. The PLME, MLME, and SME may be included in the frame processing unit SU7.

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

[0034] The signal received by the RF unit AU2 is converted into a baseband signal and sent to the physical layer processing unit AU3. The physical layer processing unit AU3 performs processing related to the physical layer function on the converted baseband signal. The signal that has undergone physical layer processing in the physical layer processing unit AU3 is sent to the MAC layer processing unit AU4. The MAC layer processing unit AU4 performs processing related to the MAC layer functions on the baseband signal. The signal that has undergone MAC layer processing in the MAC layer processing unit AU4 is sent to the DSAF unit AU5 as an upper layer packet. The DSAF unit AU5 performs the following on the upper layer packet extracted from the received signal: The DSAF unit AU5 performs processing related to the functions of the upper layer. In addition, the DSAF unit AU5 provides the upper layer packets to the DS. Good too.

[0035] The DSAF unit AU5 may acquire the upper layer packet from the DS. The DSAF unit AU5 performs processing related to the function of the upper layer when transmitting the upper layer packet. The packet is sent to the MAC layer processing unit AU4. The MAC layer processing unit AU4 processes the upper layer packet for MAC layer functions. The frame that has undergone MAC layer processing in the MAC layer processing unit AU4 (the 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 physical layer functions on frames that have been processed in the MAC layer. The frames sent from the physical layer processing unit AU3 to the RF unit AU2 are converted into RF signals and transmitted as wireless signals via the antenna unit AU1.

[0036] The processing of the physical layer processing unit AU3 may be controlled by the PLME. The processing of the MAC processing unit AU4 may be controlled by the MLME. The PLME and the MLME are entities independent of each other in terms of layers. The PLME, MLME and SME may be controlled by the frame processing unit AU7. It may be included.

[0037] HT STA (High-Throughput STA) is measured at the MAC data service access point (SAP). An HT STA may provide PHY and MAC functionality capable of supporting a specified throughput of 100 Mb / s or greater. An HT STA may also be a QoS STA. HT features may be utilized by an HT STA associated with a High-Throughput AP (HT AP). A subset of HT features may be used between two HT STAs that are members of the same IBSS. Some PHY features that distinguish HT STAs from non-HT STAs are Multiple-Input Multiple-Output (MIMO) operation, Spatial Multiplexing (SM), Spatial mapping (including transmit beamforming), space-time block coding (STBC), low-density parity check (LDPC) coding, and antenna selection (ASEL) may be used. PPDU formats permitted for HT STAs may be non-HT format, HT-mixed format, and HT-greenfield format. PPDUs may be transmitted in a 20 MHz bandwidth in HT STAs. PPDUs may be transmitted in a 40 MHz bandwidth in HT STAs. HT STAs may have MAC functionality including frame aggregation, several block ack features, power-saving multi-poll (PSMP) operation, reverse direction (RD), and protection mechanisms to support coexistence with non-HT STAs. good.

[0038] A VHT STA (Very High-Throughput STA) supports the following functions in addition to those supported by a HT STA: The VHT STA may be an HT STA that supports VHT functionality. The VHT STA's primary PHY functionality may support channel widths of 40 MHz and 80 MHz. The VHT STA's primary PHY functionality may support VHT single-user (SU) PPDUs. The VHT STA's primary PHY functionality may support 160 MHz and and 80+80 MHz channel widths may be supported. VHT multi-user (MU) PPDUs may be supported as the primary PHY function of the VHT STA. A-MPDU padding of VHT PPDU may be supported as the main MAC function of the VHT STA. S-MPDU may be supported as the main MAC function of the VHT STA. Response to bandwidth indication may be supported as the main MAC function of the VHT STA. The VHT function does not need to be present in the HT STA. A subset of VHT capabilities may be used by VHT STAs associated with the same IBSS. It may be used between two VHT STAs that are members of the

[0039] A High Efficiency (HE) STA may also be a VHT STA if it operates in the 5 GHz band. 20MHz-only HE STAs may not support 40MHz and 80MHz channel widths. Support for 20 MHz operating channel width may be mandatory for HE STAs. 20 MHz-only non-AP HE STAs may support 40 MHz and 80 MHz operating channel widths. For HE STA, the operating channel widths of 160 MHz and 80+80 MHz may be required. Support for 4 or more spatial streams may be optional. An HE STA may also be an HT STA. A key PHY feature of an HE STA that is not present in an HT or VHT STA may be support for DL ​​and UL OFDMA (Up Link Orthogonal Frequency Division Multiple Access). A key PHY feature of an HE STA that is not present in an HT or VHT STA may be support for an HE AP that supports more than four spatial streams when MU-MIMO (Multi-User Multiple Input Multiple Output) is performed across the entire PPDU bandwidth. Supports DL MU-MIMO (Down Link Multi User Multiple Input Multiple Output) The main PHY functions of the HE STA that are not present in the HT STA or VHT STA are Support for DL ​​MU-MIMO reception may be available for HE STAs, which do not exist in HT or VHT STAs. The main MAC function of an HE STA that is not present in an HT STA or a VHT STA may be support for an individual TWT (Target Wake Time) of an AP. The main MAC function of an HE STA that is not present in an HT STA or a VHT STA may be support for two NAV operation of a non-AP STA.

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

[0041] An Ultra High Reliability (UHR) STA may operate in a band between 1 GHz and 7.250 GHz. For example, a UHR STA may be an EHT STA in 5 GHz and 6 GHz. For example, a UHR STA may be an HE STA in 5 GHz and 6 GHz. For example, a UHR STA may be a VHT STA in 5 GHz and 6 GHz. For example, a UHR STA may be an HE STA in 2.4 GHz. For example, a UHR STA may be an HT STA in 2.4 GHz. A UHR STA may support Non Primary Channel Access. A UHR STA may be a HT and / or may use operation elements for VHT, HE STA, and / or UHR STA. That is, a UHR STA may be controlled by a HT operation element, a VHT operation element, a HE operation element, an EHT operation element, and / or a UHR operation element. A UHR STA may receive information related to Non-Primary Channel Access transmitted from the AP. A UHR STA may receive information related to Non-Primary Channel Access transmitted from other STAs.

[0042] APs and STAs within a BSS may transmit based on Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA). The CSMA / CA protocol is designed to reduce the probability of collisions between multiple STAs accessing the medium at the most likely points. It may be a protocol that is used.

[0043] An HT BSS may be a BSS in which a Beacon frame transmitted by an HT STA includes an HT Capabilities element. A VHT BSS may be a BSS in which a Beacon frame transmitted by a VHT STA includes a VHT Operation element. An HE BSS is a BSS in which a Beacon frame transmitted by an HE STA includes an HE Operation element. An EHT BSS may be a BSS in which a Beacon frame transmitted by an HE STA includes an EHT Operation element. For example, an HT BSS may support the capability of an HT STA. For example, a VHT BSS may be configured with STAs that support the VHT STA capability. For example, a HE BSS may be configured with STAs supporting HE capabilities. For example, an EHT BSS may consist of STAs that support the EHT capability. It may be configured with STAs that are

[0044] In this embodiment, the STA may be, for example, an HT STA, a VHT STA, an HE STA, an EHT STA, or a UHR STA. The STA may be a STA other than the above-mentioned STAs.

[0045] The AP and STA can communicate with each other using multiple frame types with a common frame format. A frame may be defined in each of the physical layer, MAC layer, and Logical Link Control (LLC) layer.

[0046] A MAC frame may be a unit of data exchanged between MAC entities. A synonym for a MAC frame may be MPDU. A MAC Protocol Data Unit (MPDU) may be a unit of data exchanged between two peer MAC entities using a physical layer (PHY) data service. A synonym for MPDU may be MAC frame. A MAC Service Data Unit (MSDU) is a unit of data exchanged between MAC Service Access Points (SAPs). 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. A MAC frame in the AP may be processed by a MAC layer processing unit AU4, and a MAC frame in the AP may be processed by a frame processing unit AU7.

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

[0048] 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 every frame. It may be configured.

[0049] The MAC header consists of a Frame Control field, a Duration / ID field, and an Address1 field. The MAC header may consist of the following fields: Address 1 field, Address 2 field, Address 3 field, Sequence Control field, Address 4 field, QoS Control field, HT Control field, etc. The MAC header may consist of all of the above fields. The MAC header may consist of some of the above fields.

[0050] 5 is a diagram showing an example of a MAC frame format according to one aspect of this embodiment. In FIG. 5, the MAC frame format may be composed of a MAC header, a Frame Body, and an FCS. In the above, the MAC header may be configured with 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.

[0051] The Frame Control field of the MAC header contains the Protocol Version subfield, Type subfield, and Subfield, Subtype subfield, To DS subfield, From DS subfield , More Fragments subfield, Retry subfield, Power Management subfield field, 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 The Frame Control field of the MAC header may be composed of subfields such as The field may consist of some of the above subfields. The Frame Control field of the MAC header may consist of all of the above subfields. The Frame Control field in the MAC header has specific subfields depending on the frame type. It may also be composed of a combination of

[0052] The type of the frame may be indicated by the Type subfield included in the Frame Control field of the MAC header. The frame type may be defined as Control frame, Management frame, or Data frame. In the Type subfield, either Control frame, Management frame, or Data frame is specified. 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. If the Type subfield is set to 10, the frame type may be a Data frame.

[0053] The management frame may be a frame for managing the connection status between devices, the control frame may be a frame for managing the communication status between devices, and the data frame may be a frame containing actual transmission data.

[0054] The frame subtype may be indicated by the Subtype subfield included in the Frame Control field of the MAC header. The 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. Subtypes other than those mentioned above may also be defined.

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

[0056] For example, the Type subfield indicates a Management frame, and the Subtype subfield indicates a Management frame. If the Type subfield is set to 0000, the subtype may be Association Request. The Type subfield indicates a Management frame, and the Subtype subfield is set to 0001. If set, the subtype may be an Association Response. In the field, a Management frame is indicated and the Subtype subfield is set to 0010. If the Type subfield indicates a Management frame and the Subtype subfield is set to 0011, the subtype may be a Reassociation Response. 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 Management frame is indicated in the Type subfield and the Subtype subfield is set to 0100, the subtype may be Probe Request. If a Management frame is indicated in the Type subfield and the Subtype subfield is set to 0101, the subtype is Probe Response. The Type subfield indicates the Management frame, and the Subtype subfield indicates the If the value in the parameter is set to 1000, the subtype may be Beacon.

[0057] The beacon frame may be a frame containing information such as the beacon period and SSID. The on frame may be a frame periodically transmitted to STAs within a BSS. The Association Response frame may be a frame containing information such as a Status code. The Association Response frame may be a frame transmitted in response to a received Association request frame. The Reassociation Response frame may be a frame containing information such as a Status code. The Reassociation Response frame may be a frame sent in response to a received Reassociation Request frame. The Probe Response frame may be a The Probe Response frame may be a frame that includes information such as the beacon period, SSID, etc. The Probe Response frame may be a frame that is transmitted in response to a received Probe Request frame.

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

[0059] For example, if 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, the subtype may be QoS Data.

[0060] The Frame body field of the MAC frame format may consist of fields and elements defined for each management frame subtype. The fields and elements are: They are displayed in the specified relative order, and non-existent fields or elements may be skipped. If an STA encounters an unrecognized element ID in the frame body of a received management frame, it ignores that element and continues parsing the rest of the management frame body (if any) for additional elements with recognizable element IDs. That is, the Frame body of a management frame may contain one or more elements.

[0061] The element format of each element included in the Frame body is the Element ID field, Length field, Element ID Extension field, information field, etc. The Information field may contain information specific to the element. For example, if the Element ID is 61, it may indicate an element for HT Operation. For example, the Element For example, if the Element 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.

[0062] The Operation element may be information for controlling the operation of a STA within a BSS. The Operation element may be composed of multiple fields.

[0063] 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 be defined as the Secondary Channel Offset field. The Secondary Channel Offset field may be configured with a STA Channel Width field, etc. The Secondary Channel Offset field may indicate the offset of the secondary channel relative to the primary channel. If the Secondary Channel Offset field is set to 1, the secondary channel may be located above the primary channel. If the Secondary Channel Offset field is set to 3, The secondary channel may be located below the primary channel. If the Secondary Channel Offset field is set to 0, the secondary channel may not exist. l The 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 20 MHz ... In this case, it may be set to 1. The operation of the HT STA(s) in the BSS may be controlled by the HT Operation element. That is, the HT Operation element may be an operation element that controls the operation of the HT STA(s) in the BSS.

[0064] The HT operation element may be transmitted in a Management frame. The HT operation element may be transmitted in a Control frame. The HT operation element may be transmitted in a Data frame. For example, the HT operation element may be transmitted in a Beacon frame. For example, the HT operation element may be transmitted in an Association Response frame. For example, the HT operation element may be transmitted in a Reassociation Response frame. For example, the HT operation element may be transmitted in a Probe Response frame.

[0065] The VHT Operation element consists of an Element ID field, a Length field, and a VHT Operation The VHT Operation information field may be defined in the Basic VHT-MCS and NSS Set fields. 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 the VHT STA(s) within the BSS may be controlled by the HT Operation element and the VHT Operation element. That is, the VHT Operation element controls the operation of the VHT STA(s) within the BSS. It may also be an operation element that controls the operation.

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

[0067] The Channel Width field in the VHT Operation information field is used for HT operation. Together with the STA channel width field in the element, the BSS bandwidth may be defined. The Channel Width field may be set to 0 for 20 MHz or 40 MHz BSS bandwidth. 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 3 for 80+80MHz BSS bandwidth. May be set to 3. Values ​​in the range 4 to 255 in the Channel Width field are reserved. may be.

[0068] Channel Center Frequency Segment 0 field in the VHT Operation information field The field is for a VHT BSS of 20MHz, 40MHz, 80MHz, 160MHz, or 80+80 MHz. You may define the center frequency in the Channel Center Frequency Segment 0 field. For a BSS bandwidth of 20 MHz, 40 MHz, or 80 MHz, the Channel Center Frequency Segment 0 field may indicate the 20 MHz, 40 MHz, or 80 MHz channel center frequency index at which the VHT BSS operates. The Channel Center Frequency Segment 0 field may indicate the 20 MHz, 40 MHz, or 80 MHz channel center frequency index at which the VHT BSS operates. If set to 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 indicates the channel center frequency index of the 160 MHz BSS. If the bandwidth and Channel Width subfield is 2, the 160MHz channel on which VHT BSS operates The channel center frequency index of the Channel Center Frequency Segment may be indicated. The 0 field is a BSS bandwidth of 80 + 80MHz and the Channel Width subfield is 1 or 3. In this case, even if the channel center frequency index of the primary 80MHz channel of the VHT BSS is shown, good.

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

[0070] The HE Operation element format consists of an Element ID field, a Length field, and an Element ID Extension field, HE Operation Parameter field, BSS Color Information field, Basic HE-MCS And NSS Set field, VHT Operation Information field field, Max Co-Hosted BSSID Indicator field, 6GHz Operation Information field When operating in the 2.4 GHz band, the HE STAs in the HE BSS may be controlled by the HT Operation element and the HE Operation element. When operating in the 5 GHz band, the HE STAs in the HE BSS may be controlled by the HT Operation element, the VHT Operation element ( When operating in the 6 GHz band, the HE STAs in the HE BSS may be controlled by the HE Operation element. That is, the HE Operation element may be an operation element that controls the operation of the HE STAs in the BSS.

[0071] The HE operation element may be transmitted in a Management frame. The HE operation element may be transmitted in a Control frame. The HE operation element may be transmitted in a Data frame. For example, the HE operation element may be transmitted in a Beacon frame. For example, the HE operation element may be transmitted in an Association Response frame. For example, the HE operation element may be transmitted in a Reassociation Response frame. For example, the HE operation element may be transmitted in a Probe Response frame.

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

[0073] The BSS Color Information field format of the HE Operation element format may be configured with a BSS Color subfield, a Partial BSS Color subfield, a BSS Color Disabled subfield, and the like.

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

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

[0076] 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. The EHT Operation Information field may be composed 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 20 MHz EHT BSS bandwidth. The Channel Width subfield may define 1 for a 40 MHz EHT BSS bandwidth. The Channel Width subfield may define 2 for an 80 MHz EHT BSS bandwidth. The Channel Width subfield For 160MHz EHT BSS bandwidth, 3 may be defined. The CCFS0 subfield may define a value of 4 for 320MHz EHT BSS bandwidth. 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 indicate the channel center frequency index of the 20 MHz channel, 40 MHz channel, or 80 MHz channel on which the EHT BSS operates for a 20 MHz BSS bandwidth, a 40 MHz BSS bandwidth, or an 80 MHz BSS bandwidth. The CCFS0 subfield may indicate the channel center frequency index of the primary 80 MHz channel for a 160 MHz BSS bandwidth. The CCFS0 subfield may indicate the channel center frequency index of the primary 160 MHz channel for a 320 MHz BSS bandwidth. The CCFS1 subfield may define the center frequency of the 160 MHz EHT BSS or the 320 MHz EHT BSS. The CCFS1 subfield may be set to 0 for a 20 MHz BSS bandwidth, a 40 MHz BSS bandwidth, or an 80 MHz BSS bandwidth. For a 160 MHz BSS bandwidth, the CCFS1 subfield may contain the index of the center frequency of the 160 MHz channel. is the index of the center frequency of the 320MHz channel for the 320MHz BSS bandwidth. Good too.

[0077] An 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 an MSDU and padding of 0 to 3. In this case, the A-MSDU subframe header may contain a DA field, a SA field, and a Length field. The DA and SA fields may contain values ​​passed in the MA-UNITDATA.request and MAUNITDATA.indication primitives. The Length field contains the length of the MSDU. It may also contain the length in octets (i.e., 8-bit units).

[0078] FIG. 6 is a diagram showing an example of an A-MSDU according to one aspect of this embodiment. In FIG. 6, the MAC frame format may be composed of a MAC header, a Frame Body, and an FCS. Here, the MAC header may be composed 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 an MPDU. The Frame Body may consist of n A-MSDU subframes. Each A-MSDU may consist of an A-MSDU subframe header, an MSDU, and Padding. The A-MSDU subframe header is It may consist of a field, an SA field, and a Length field.

[0079] An A-MPDU (Aggregate MPDU) is a sequence of one or more A-MPDU subframes and a variable amount of EOF Each A-MPDU subframe may optionally be followed by an MPDU delimiter. An A-MPDU 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 four octets. The EOF Padding field may consist of the EOF Padding subframe field and the EOF Padding Octets field. The A-MPDU pre-EOF padding may refer to the contents of the A-MPDU, not including the EOF Padding field. The MPDU delimiter is the EOF field, the Reserved field, and the MPDU It may consist of a Length field, a CRC field, and a Delimiter Signature field. good.

[0080] 7 is a diagram illustrating an example of an A-MPDU according to one aspect of the present embodiment. In FIG. 7, the A-MPDU may be composed 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 include an EOF field, a Reserved field, 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.

[0081] MSDU or MMPDU (MAC Management Protocol Data Unit) into smaller MAC level frames The process of dividing the frame into MPDUs may be called fragmentation. Fragmenting and reassembling MSDUs or MMPDUs carried in individually addressed MPDUs It may be done.

[0082] FIG. 8 is a diagram showing an example of fragmentation according to one aspect of this embodiment. The MSDU may be fragmented into n pieces. The MSDU is divided into n Frame Bodies, and a MAC HDR (header) and CRC (Cyclic Redundancy Check) are added to each Frame Body. That's fine.

[0083] PPDU consists of PHY preamble, PHY header, PSDU (PHY Service Data Unit), etc. The PPDU may be given L-STF, L-LTF, and L-SIG. The PPDU may be given HT-STF, HT- The PPDU may contain VHT-STF, VHT-LTF, VHT-SIG-A, and VHT-SIG-B. The PPDU may be given HE-STF, HE-LTF, HE-SIG-A, and HE-SIG-B. The PPDU may be given HT-STF, HT-LTF, and HT-SIG in addition to L-STF, L-LTF, and L-SIG. PPDU includes VHT-STF, VHT-LTF, VHT-SIG-A, and VHT-SIG-B in addition to L-STF, L-LTF, and L-SIG. In addition to L-STF, L-LTF, and L-SIG, HE-STF, HE-LTF, HE-SIG-A, and HE-SIG-B may be added to the PPDU.

[0084] 9 is a diagram illustrating an example of a PPDU according to an aspect of the present embodiment. In FIG. 9, the PPDU may be provided with an L-STF and an L-LTF in the PHY layer. In FIG. 9, the PPDU includes a PSDU, a PHY It may be composed of a preamble, PHY header, tail, and padding. Here, the PSDU may be an A-MPDU in the MAC sublayer. The A-MPDU may be composed of multiple MAC frame formats. Here, one MAC frame format may be composed of a MAC header field, an A-MSDU field, and an FCS field.

[0085] The time interval between frames may be referred to as an IFS (Inter Frame Space). The STA may determine whether the medium is idle by using the carrier sensing function at the specified time interval. That is, the STA may perform carrier sensing for the IFS period to determine whether the medium is idle.

[0086] A plurality of types of IFS may be defined, such as Reduced Inter Frame Space (RIFS), Short Inter Frame Space (SIFS), Priority Inter Frame Space (PIFS), DCF Inter Frame Space (DIFS), Arbitration Inter Frame Space (AIFS), Extended Inter Frame Space (EIFS), Short Beamforming Inter Frame Space (SBIFS), Beam Refinement Inter Frame Space (BRPIFS), Medium Beamforming Inter Frame Space (MBIFS), and Long Beamforming Inter Frame Space (LBIFS).

[0087] The time intervals may differ depending on the type of IFS. For example, a PIFS may have a longer time interval than a SIFS. DIFS may be an IFS with a longer time interval than PIFS. IFS The type of IFS may provide a priority level for accessing the wireless medium, i.e., an IFS with a short time interval may be an IFS with a high priority level for accessing the wireless medium.

[0088] SIFS (Short Inter Frame Space) is the last symbol or signal of the previous frame. It may be the time from the end of the extension (if present) to the first symbol of the preamble of the next frame being seen on the wireless medium.

[0089] Priority Inter Frame Space (PIFS) may be used to control access to the medium to obtain priority access. PIFS may also be used to perform CCA on the secondary 20 MHz channel, secondary 40 MHz channel, and secondary 80 MHz channel before transmission on 40 MHz, 80 MHz, and 160 MHz channels.

[0090] The DCF Inter Frame Space (DIFS) may be used by STAs operating using DCF to transmit data frames (MPDUs) and management frames (MMPDUs). After a STA using DCF receives a frame correctly, it determines by the carrier sense (CS) mechanism that the medium is idle on a TxDIFS slot boundary and the value of the STA's backoff counter is 0. If it is zero, transmission may occur.

[0091] The Arbitration Inter Frame Space (AIFS) may be used for QoS STAs that access the medium using EDCAF.

[0092] EIFS (Extended Inter Frame Space) is a DCF that identifies frames with an incorrect FCS value. It may be used if, after receiving it, the medium is immediately determined to be idle.

[0093] The basic MAC access method used by the STAs may be the Distributed Coordination Function (DFC). The DCF ensures that the same coordination is used by each STA in the BSS when the network is operational. The function logic may be a coordination function for the class that is always active. DCF is a 1-way CSMA / CA The DCF may be a function that must be implemented in all STAs.

[0094] To transmit, a STA senses the medium to determine if another STA is transmitting. If the medium is not busy, the STA may transmit. If interrupted, the STA will postpone until the current transmission is completed.

[0095] In the CSMA / CA distributed algorithm, a specified There is a gap of a specified duration between frame exchange sequences. The gap of a specified duration between frame exchange sequences may be referred to as an IFS. A transmitting STA ensures that the medium is idle for a required period before attempting to transmit. The required period may be a gap of a specified duration between frame exchange sequences. The required period may be referred to as an IFS. .

[0096] A STA must reset its backoff counter before attempting to transmit again after a postponement or immediately after a successful transmission. The backoff counter may be initialized to a random value. The STA may decrement the backoff counter once for each aSlotTime period while the medium is idle. aSlotTime may be the time length of a slot. The slot time here may be the time of a slot used by the MAC to define the IFS. Also, aSlotTime may be a predetermined time length. It may be a fixed time length (for example, in microseconds).

[0097] The basic medium access protocol may be DCF. DCF is a protocol that combines CSMA / CA and medium Through the use of random backoff counters after a green state, medium All individually addressed traffic uses immediate positive acknowledgment (Ack frame) and if no Ack frame is received, the sender Retransmissions are scheduled by the STA. Multiple STAs wait for the medium to become available. The point at which the medium goes from busy to idle is where collisions are most likely. This is why a random backoff procedure is needed to resolve medium contention. A STA's transmission may interfere (collision) with the transmission of another STA even if the carrier sense function (CS function) indicates that the medium is not busy. Interference occurs when the expected It may also be determined if a response frame is not received.

[0098] A STA wishing to initiate transmission of data or management frames using DCF may use the carrier sense mechanism to determine the busy / idle state of the medium. If the medium is busy, the STA shall continue without interruption for the IFS until the medium is determined to be idle. Here, the type of IFS is determined by whether the last transition to idle state was received correctly on the medium. If the result is due to the detection of an unread frame, it may be EIFS. Otherwise, it may be IFS. The type may be DIFS. After the medium is idle in a DIFS or EIFS, the STA may generate a random backoff count for additional deferral time before transmitting. However, if the backoff counter already contains a non-zero value, no random selection of a value may be performed. The backoff counter may be a pseudo-random integer drawn from a uniform distribution between [0, CW], where CW is an integer within the range of values ​​aCWmin and aCWmax, which are characteristics of the PHY. The CW may be equal to or greater than aCWmin and may be equal to or less than aCWmax. The CW may be referred to as a contention window.

[0099] The contention window parameter may take the initial value of aCWmin. The contention window takes on the next value in the series with each failed MPDU transmission attempt and increment of any STA's retries until the contention window reaches the value of aCWmax. The contention window maintains the value of aCWmax until aCWmax is reached, at which point the contention window is reset. If a data frame or management frame is successfully transmitted, the contention window may be reset to aCWmin. If the SSRC reaches dot11ShortRetryLimit, the contention window may be reset to aCWmin. The set of contention window values ​​may be in ascending order as integer powers of 2 minus 1, starting from the PHY-specific aCWmin value and continuing up to the PHY-specific aCWmax. For example, if aCWmin is 7 and aCWmax is 255, the set of contention windows may be 7, 15, 31, 63, and 127. , 255.

[0100] For example, in the case of OFDM PHY characteristics with 20 MHz channel spacing, aSlotTime may be 9 μs, in the case of OFDM PHY characteristics with 20 MHz channel spacing, aCWmin may be 15, and in the case of OFDM PHY characteristics with 20 MHz channel spacing, aCWmax may be 1023.

[0101] The QoS facility may include an additional coordination function called Hybrid Coordination Function (HCF), which is available only in QoS network configurations. The HCF may be implemented in all QoS STAs. The HCF combines aspects of contention-based and contention-free access methods and coordinates the provision of prioritized and parameterized QoS access to the wireless medium for QoS STAs. It is fully functional and continues to support non-QoS STAs for best-effort forwarding. The HCF may use EDCA (Enhanced Distributed Channel Access). Both HCCA (HCF controlled channel access) and HCCA (HCF controlled channel access) The HCF may include functionality provided by the EDCA mechanism for contention-based forwarding. A contention-based channel access method called a contention-free system may be used. The transfer may use a control channel access method called the HCCA mechanism.

[0102] HCCA (HCF Controlled Channel Access) is an individually addressed downlink QoS STA contention for transmission, uplink transmission, and direct link transmission It may also be a channel access mechanism used by a Hybrid Coordinator (HC) to coordinate the use of the free medium.

[0103] The EDCA mechanism uses eight different User Priorities (UPs) to provide STAs with access to the wireless medium. It may provide differentiated distributed access. The UP is UP is the upper part of the MAC. The UP may be assigned to an MSDU at the layer. The UP may take any value from 0 to 7. The EDCA mechanism may define four Access Categories (ACs) to support the delivery of traffic using the UP of a STA. An AC specifies the QoS STA can use to access a channel. AC may be a label for a common set of EDCA parameters used to compete for access rights and transmit MSDUs at a particular priority. AC may take on any of the values ​​AC_BE, AC_BK, AC_VI, and AC_VO. AC_BE, AC_BK, AC_VI, and AC_VO may indicate access categories corresponding to best effort, background, video, and voice, respectively.

[0104] QoS (Quality of Service) facilities are parameterized and prioritized. Enhancements, channel access rules, and frame forwarding used to provide a consistent QoS It may be a protocol, a frame exchange sequence, or a managed object. The QoS AP may be an AP that supports the QoS function. The QoS BSS may be a BSS that provides QoS functionality. may include a QoS AP.

[0105] The Enhanced Distributed Channel Access Function (EDCAF) may be a logical function within a QoS STA that uses EDCA to determine when frames in a transmit queue with an associated AC are allowed to transmit over the wireless medium. There may be one EDCAF per AC. DCFs and HCFs may be defined to operate within the same BSS.

[0106] Each EDCAF may maintain a backoff counter measured in backoff slots. When the backoff procedure is invoked, the backoff counter is counted up with a uniform distribution from 0 to CW. It may be set to a randomly selected integer value. AIFS may be defined as AIFSN × aSlotTime + aSIFSTime. For example, in the OFDM PHY characteristics, for 20 MHz channel spacing, aSlotTime may be 9 μs and aSIFSTime may be 16 μs. AIFSN may be different for each AC. For example, if AC is AC_BK, AIFSN may be 7. If AC is AC_BE, AIFSN may be 3. If AC is AC_VI, AIFSN may be 2. If AC is AC_VO, AIFSN may be 2. CW may be in ascending order as integer values ​​calculated by subtracting 1 from a power of 2, starting from a PHY-specific CWmin value and continuing to a PHY-specific CWmax. CWmin and CWmax may be different 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. For OFDM PHY characteristics with 20 MHz channel spacing, aCWmin may be 15. For OFDM PHY characteristics with 20 MHz channel spacing, aCWmax may be 1023. A STA may decrement its backoff counter once for each aSlotTime period while the medium is idle. Each time an MPDU transmission attempt fails, any STA's retries increase, taking the next value in the sequence.

[0107] In HCF, the basic unit of allocation of transmission rights to the wireless medium may be a TXOP (Transmission Opportunity). A TXOP (Transmission Opportunity) is a transmission opportunity that a particular QoS STA can use to exchange frames on the wireless medium. A TXOP may be a time interval during which a STA has the right to initiate a TXOP sequence. A TXOP may be defined by a start time and a maximum duration. A TXOP may be acquired by EDCA. That is, a STA may acquire a TXOP from an EDCA. If you do this, you may acquire a TXOP.

[0108] FIG. 10 is a diagram illustrating an example of a backoff procedure according to one aspect of the present embodiment. In FIG. 10, the horizontal axis may represent time. 1001 may represent a transmission from STA#1. 02 may be an IFS. 1003 may be a backoff counter. 100 3 may be referred to as a contention window. 1004 is a transmission of STA#2. In FIG. 10, STA#2 may detect 1001 on the channel. While STA#2 detects 001, it may determine that the channel is busy. In other words, 1001 may be the period during which the channel is determined to be busy. STA#2 performs carrier sensing. STA#2 may execute the 1001 period and determine whether the channel is busy. If it determines that the channel is idle, it may perform carrier sensing during the period 1002. For example, 1002 may be DIFS. 1002 may be AIFS. STA#2 If the channel is idle during the period of 1002, STA#2 may start 1003. 1003 decrements the backoff counter while the channel is idle. For example, six backoff counters may be generated in 1003. While the channel is idle, the backoff counter is decremented, and when the backoff counter reaches 0, STA#2 stops transmitting. The backoff counter may be determined to be between 0 and CW, where CW may be a value selected from a range of values ​​between aCWmin and aCWmax. The channel may be referred to as a wireless medium.

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

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

[0111] The NAV may be a counter that counts down at a constant rate to 0. The STA may indicate that the virtual carrier sense is idle if the NAV counter is 0. The STA may indicate that the virtual carrier sense is busy if the NAV counter is not 0. The physical carrier sense function and the virtual carrier sense function may be used to determine the state of the medium. If either the physical carrier sense function or the virtual carrier sense function indicates busy, the medium may be considered busy. If both the physical carrier sense function and the virtual carrier sense function indicate idle, the medium may be considered idle. The virtual carrier sense function may also be referred to as NAV. Yes. NAV may be provided by every MAC. The NAV counter may be referred to as the NAV timer.

[0112] The physical carrier sensing function in the STA may be controlled by the physical layer processing unit SU3. The virtual carrier sensing 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. The NAV in the AP may be controlled by the MAC layer processing unit AU4.

[0113] A STA may set NAV if the address field of the received frame is not its own address. A STA shall set NAV in a PSDU if it receives at least one valid frame in the PSDU. The STA may update its NAV using any valid Duration field information of the received frame. The STA may update its NAV if the value indicated by the Duration field of the received frame is greater than the current NAV value. The STA may update its NAV if the RA (address) of the received frame is the same as its own MAC address. If they are equal, the NAV is not updated.

[0114] Carrier sense (CS) may be performed through both physical and virtual mechanisms. Carrier sense may also be referred to as a carrier sense function. Carrier sense may also be referred to as a carrier sense mechanism. A virtual carrier sense mechanism is realized by delivering reservation information that notifies advance notice of medium use. Exchanging RTS and CTS frames before the actual data frames may be one of the means of delivering medium reservation information. The RTS and CTS frames are used before the actual data frames. and Duration field, which defines the period for which the medium is reserved to transmit the Ack frame. It may contain an RTS frame (sent by the originating STA) or a CTS frame (sent by the destination STA). The STA receiving the request (transmitted by the originating STA) processes the medium reservation. Even if a frame is not available, it can know that it intends to use the medium to transmit a data frame. The medium reservation information is stored in the Duration / ID field of individually addressed frames. The Duration / ID field indicates the time (duration) for which the medium is reserved. The Duration / ID field may indicate the amount of medium reserved, ending in the immediately following Ack frame. In the case of a fragment sequence, the Duration / ID field is the time the medium is reserved until the end of the Ack frame following the next fragment. The RTS / CTS mechanism may also work in the case of overlapping BSSs using the same channel. The medium reservation mechanism may work across BSS boundaries.

[0115] The RTS (Request To Send) frame format consists of a Frame Control field, a Duration field, and a The RTS frame format may contain the following fields: field, 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. The RA field of the RTS frame indicates the intended direct transmission of the pending individually addressed frame. It may be the address of the STA that is the recipient. The TA field may be the address of the STA that sends the RTS frame or the bandwidth signal TA of the STA that sends the RTS frame.

[0116] The CTS (Clear To Send) frame format is the Frame Control field and Duration field. The Duration field of a CTS frame format sent in response to an RTS frame may be the Duration field of the immediately preceding RTS frame minus the time required to send the CTS frame and its corresponding SIFS. In other words, it may be the time required to send the pending data or management frame, one Ack frame, and two SIFS. If the CTS frame is the first frame of an exchange and the pending data Or, if the management frame requires acknowledgment, the Duration field specifies the time required to transmit the pending data or management frame, two SIFS, and one Ack frame. The CTS frame is the first frame of the exchange and may be pending If the data or management frame in question does not require immediate acknowledgment, the Duration field shall be the time required to transmit the pending data or management frame plus one SIFS. If the CTS frame is a response to an RTS frame, the RA field of the CTS frame The field contains the address of the TA field of the RTS frame, and the individual / group bit is set to 0. If the CTS frame is the first frame in a frame exchange, the RA field may be set to The MAC address of the sender may be set in the field.

[0117] FIG. 11 is a diagram illustrating an example of a NAV according to one aspect of the present embodiment. The axis may be time. For example, 1101 may be a timeline of the operation of AP#1. 1102 may be a timeline of the operation of STA#1. 1103 may be a timeline of the operation of AP#2. 1104 may be a timeline of the operation of STA#2. 1101, 1102, 1103, and 1104 may be timelines on the same channel. 1105 may be an RTS frame. 1106 may be the NAV period of AP#1. 1107 may be a CTS frame. 1108 may be the NAV period of STA#2. 1109 may be a Data frame. 1110 may be an AcK frame. 1111 may be an IFS. 1112 may be a contention window. STA#1 may also use 1105 to send a backoff counter or a backoff procedure. When AP#1 receives 1105, it sends the RTS for the period indicated in the Duration field. AP#2 may set 1106 after receiving 1105. AP#2 sends 1107 to STA#1. When STA#2 receives 1107, it may set 1108 for the period indicated in the Duration field of the CTS. When STA#1 receives 1107, it may send 1109. When AP#2 receives 1109, it may send 1110 to STA#1. When 1106 ends, AP#1 may start 1112 if the channel is idle in 1111. STA#2 When 1108 ends, STA#1 may start 1112 if the channel is idle at 1111. The interval between 1105 and 1107 may be an IFS. AP#2 may transmit 1107 if the channel is idle during the IFS period before transmitting 1107. The interval between 1107 and 1109 may be an IFS. STA#1 may transmit 1109 if the channel is idle during the IFS period before transmitting 1109. The interval between 1109 and 1110 may be an IFS. AP#2 sends 1110 if the channel is idle for the IFS period before sending 1110. Here, for example, AP#1 may be 202 in FIG. 2. For example, STA#1 may be 207 in FIG. 2. For example, AP#2 may be 206 in FIG. 2. For example, STA#2 may be 2088 in FIG. 1102 may be a timeline of the operation of the AP or the STA. 1103 may be a timeline of the operation of the AP or STA. 1104 may be a timeline of the operation of the AP or the STA.

[0118] Channel bonding may involve transmission using one or more 20 MHz channels. Alternatively, channel bonding may involve transmission using multiple 20 MHz channels. Channel bonding may involve transmission using multiple adjacent 20 MHz channels. Channel bonding may also be referred to as channel aggregation. Channel bonding is effective because it uses multiple channels simultaneously to transmit data. The bandwidth increases, and data transmission speeds increase. may include a primary channel and one or more secondary channels, and channel bonding may be performed using more than one of these channels.

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

[0120] 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 40 MHz, 80 MHz, 160 MHz, or 80+80 MHz BSS may be referred to as a secondary 20 MHz channel. A secondary 20 MHz channel may be a 20 MHz channel adjacent to a primary 20 MHz channel in a 40 MHz BSS. A secondary 20 MHz channel may be a channel that combines with a primary 20 MHz channel to form a 40 MHz channel in a 40 MHz BSS. A secondary 20 MHz channel may be a channel that combines with a primary 20 MHz channel to form a 40 MHz channel in an 80 MHz BSS. The secondary 20 MHz channel may be a 20 MHz channel adjacent to the 20 MHz channel. The secondary 20 MHz channel may be a channel that combines with the primary 20 MHz channel to form a primary 40 MHz channel in an 80 MHz BSS. The secondary 20 MHz channel may be a 20 MHz channel adjacent to the primary 20 MHz channel in a 160 MHz or 80+80 MHz BSS. The secondary 20 MHz channel may be a 20 MHz channel that combines with the primary 20 MHz channel in a 160 MHz or 80+80 MHz BSS. A secondary 40 MHz channel may be a 40 MHz channel adjacent to the primary 40 MHz channel to form an 80 MHz channel in an 80 MHz BSS. A secondary 40 MHz channel may be a 40 MHz channel adjacent to the primary 40 MHz channel to form a primary 80 MHz channel in a 160 MHz or 80+80 MHz BSS. A secondary 80 MHz channel may be a 40 MHz channel adjacent to the primary 40 MHz channel to form a 160 MHz or 80+80 MHz BSS. In an 80+80MHz BSS, the 80MHz channel does not include the primary 20MHz channel. A secondary 80MHz channel may be used in combination with a primary 80MHz channel to provide 160MHz or The secondary 160 MHz channel may be a 160 MHz channel that does not include a primary 20 MHz channel and that, in a 320 MHz BSS, forms a 320 MHz channel in combination with the primary 160 MHz channel of the 320 MHz EHT BSS.

[0121] A non-primary channel is any 20MHz channel other than the primary 20MHz channel in a 40MHz channel, 80MHz channel, 160MHz channel, 80+80MHz channel, or 320MHz channel. It may also be a

[0122] FIG. 12 is a diagram illustrating an example of channel bonding according to one aspect of this embodiment. In FIG. 12, 1201, 1202, 1203, 1204, 1205, 1206, 1207, and 1208 may each be a 20 MHz channel. FIG. 12 may be a channel configuration of a BSS operating with a 160 MHz channel width. 1201 may be a primary 20MHz channel. 1201 may be referred to as a primary channel. 1202 may be a secondary 20MHz channel. 1203 and A secondary 40 MHz channel may be configured from 1205, 1206, and 1204. A secondary 80 MHz channel may be configured from 1202, 1207, and 1208. 03, 1204, 1205, 1206, 1207, and 1208 are called secondary channels. This may be done.

[0123] The Operating class is an index into a set of values ​​for radio operation in a regulatory domain. The value of Operating class is the frequency for the channel number, the channel that can be used, The value of the operating class may indicate the center frequency of the channel and the maximum channel width that can be used. is the Channel starting frequency, Channel Spacing, Channel A channel set may also refer to a set of channels. It may be a list of integer channel numbers valid for the operating class. Channel Spacing is the maximum bandwidth of one frequency segment allowed by the operating class. The Operating class value may be transmitted in a frame. For example, the Operating class value may be transmitted in a Beacon frame. The Operating class value may be transmitted in a Probe Response frame. The value of Operating class may be an Operating class index.

[0124] The center frequency of the Primary 20MHz channel may be determined by Channel starting frequency + 5 × dot11CurrentPrimaryChannel. dot11CurrentPrimaryChannel may be the channel number of the primary channel. The STA may determine dot11CurrentPrimaryChannel from the Operation element included in the frame received from the AP. The STA may determine dot11CurrentPrimaryChannel from information in the Primary Channel field included in the HT Operation element. The STA may determine dot11CurrentPrimaryChannel from information in the Primary channel field in the 6GHz Operation Information field included in the HE Operation element. For example, a STA that receives a Beacon frame from an AP may determine dot11CurrentPrimaryChannel from information in the Primary channel field in the 6GHz Operation Information field included in the HE Operation element. 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 x 500 kHz. dot11ChannelStartingFactor may be indicated in the Operating Class field.

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

[0126] In channel bonding, a STA may perform a backoff procedure on the primary channel and sense and transmit on the secondary channels for a PIFS period. The bandwidth of the transmission may be determined by the CCA status of the nonprimary channels during the PIFS prior to the transmission.

[0127] The PHY-CCA.indication primitive may be a primitive indicating the current state of the medium from the PHY to the MAC entity. The PHY-CCA.indication primitive contains the STATE parameter. The PHY-CCA.indication primitive may include a channel-list parameter. The STATE parameter of the PHY-CCA.indication primitive may be one of two values: BUSY (busy) or IDLE (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 is used when the PHY evaluates the channels and finds that the channels are unavailable. If the STA is in the IDLE state, the parameter value may be BUSY. Otherwise, the parameter value of the PHY-CCA.indication primitive STATE may be IDLE. If the STA is in the IDLE state, the channel-list parameter is not present. If the CCA is determined by a single channel due to the type of PHY operating, the channel-list parameter is not present. Otherwise, the channel-list parameter may contain a set indicating busy channels. That is, if the CCA is determined by multiple channels and is BUSY, the channel-list parameter is For example, the entries in the Channel-list parameter may indicate primary, secondary, secondary40, and secondary80.

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

[0129] The PHY-CCA.indication primitive may be generated when the state of a channel changes from idle to busy, or when the state of a channel changes from busy to idle, or when an entry in the channel-list parameter changes.

[0130] When the MAC receives a PHY-CCA.indication with the channel-list parameter present, it determines which channel If the channel-list parameter entry of PHY-CCA.indication is primary, it may be determined that there are no idle channels. If the channel-list parameter entry of PHY-CCA.indication is secondary, it may be determined that the primary channel is idle. If the channel-list parameter entry of PHY-CCA.indication is secondary40, the primary channel and secondary 20MHz channel are determined to be idle. If the channel-list parameter entry of PHY-CCA.indication is secondary80 , the primary channel, the secondary 20MHz channel, and the secondary 40MHz channel are active. It may be determined to be idle.

[0131] For example, in FIG. 12, 1201 may be a primary channel. 1202 may be a secondary channel (secondary 20 MHz channel). 1203 and 1204 The secondary 40MHz channel may be configured with 1205, 1206, 1207, and In other words, the bandwidth is 160 MHz. In FIG. 12, the primary channel is 1201, the secondary channel (secondary 20 MHz channel) is 1201, the secondary 40 MHz channel is 1203 and 1204, the secondary 80 MHz channel is 1205, 1206, 1207, and For example, the STA may be configured with a primary channel (1201) and a channel When the state of a channel changes from idle to busy, it indicates that the primary channel is busy. An STA may issue a primitive(PHY-CCA.indication(BUSY,{primary})) indicating that the primary channel is idle when the channel state changes from busy to idle on the primary channel. If a primitive(PHY-CCA.indication(BUSY,{primary})) indicating that the primary channel is idle is issued on the primary channel, it may be determined that there is no idle channel. If the primary channel is idle, the STA may issue a primitive related to the secondary channel (1202). If the secondary channel (secondary 20MHz channel) is idle, the STA may issue a primitive (PHY-CCA.indication(IDLE,{secondary})) indicating that the secondary channel is idle. If the secondary channel is busy, the STA may issue a primitive (PHY-CCA.indication(BUSY,{secondary})) indicating that the secondary channel (secondary 20MHz channel) is busy. PHY-CCA.indication(IDLE,{secondary}) may indicate that both the primary channel and the secondary channel are idle. PHY-CCA.indication(BUSY,{secondary}) indicates that the primary channel is idle and the secondary channel is busy. A STA may issue a primitive related to the secondary 40MHz channel (consisting of 1202 and 1204) when the primary channel and secondary 20MHz channel are idle. A STA may issue a primitive related to the secondary 40MHz channel (consisting of 1202 and 1204) when the secondary 40MHz channel is idle. If the secondary 40MHz channel is busy, 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,{secondary40}) The primary channel, secondary channel, and secondary 40MHz channel are idle. PHY-CCA.indication(IDLE,{secondary 40}) may indicate that the primary and secondary channels are idle and the secondary 40 MHz channel is busy. The STA may If the secondary 40MHz channel is idle, the STA may issue a primitive related to the secondary 80MHz channel (consisting of 1205 to 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. is busy, it may issue primitive(PHY-CCA.indication(BUSY,{secondary80})) indicating 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.

[0132] The STA may determine the PHY-CCA.indication primitive in the physical layer processing unit SU3. Even if the PHY-CCA.indication primitive determined by the physical layer processing unit SU3 is indicated to the MAC layer processing unit SU4, The AP may issue a PHY-CCA.indication primitive in the physical layer processing unit AU3. The PHY-CCA.indication primitive determined by the physical layer processing unit AU3 is indicated to the MAC layer processing unit AU4. Good too.

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

[0134] The receiver shall, within aCCATime from the arrival of the signal at the receiver antenna, verify that the sensitivity of the primary 20 MHz channel is less than the minimum modulation and coding rate by a predetermined amount (e.g., 20 dB). In response to any signal above the high threshold (-62 dBm), the receiver issues a PHY-CCA.indication(BUSY, {primary}) primitive. Thereafter, while the threshold remains above the receiver, the receiver will not issue a PHY-CCA.indication(BUSY, {secondary}), PHY-CCA.indication(BUSY, {secondary40}), PHY-CCA.indication(BUSY, {secondary80}), or PHY-CCA.indication(IDLE) primitive. That is, the receiver may issue a PHY-CCA.indication(BUSY, {primary}) primitive upon receiving any signal above -62 dBm on the primary 20 MHz channel. -62 dBm may be the threshold for determining whether the channel is idle or busy.

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

[0136] The PHY shall not issue any signal within the secondary 40 MHz channel in an idle operating channel width of 80 MHz, 160 MHz, or 80+80 MHz unless a condition exists to issue the PHY-CCA.indication(BUSY, {primary}) or PHY-CCA.indication(BUSY, {secondary}) primitive. If the signal exceeds the threshold of -59 dBm or greater within aCCATime after arriving at the receiver antenna, the PHY shall issue a PHY-CCA.indication(BUSY, {secondary40}) primitive. In this case, the PHY shall not issue a PHY-CCA.indication(BUSY, {secondary80}) primitive or a PHY-CCA.indication(IDLE) primitive. The PHY shall issue a PHY-CCA.indication(BUSY, {primary}) primitive if, in an idle 80 MHz, 160 MHz, or 80+80 MHz operating channel width, 90% or more of the 40 MHz preambles or PPDUs are -72 dBm or greater on the secondary 40 MHz channel within aCCAMidTime. If detected with probability , PHY PHY-CCA.indication(BUSY, {secondary40}) primitive The PHY issues PHY-CCA.indication(BUSY, {primary}) and PHY-CCA.indication(BUSY, {secondary}) There is no condition to issue a primitive, and the idle 80MHz, 160MHz, Or, in an operating channel width of 80+80MHz, a 20MHz preamble or PPDU of -72dBm or more is transmitted in any 20MHz subchannel of a secondary 40MHz channel within a CCAMidTime. If detected with a probability of 90% or more within the period, the PHY issues the PHY-CCA.indication(BUSY, {secondary40}) primitive. -72dBm may be the threshold for determining whether the channel is idle or busy.

[0137] The PHY shall not issue the PHY-CCA.indication(BUSY,{primary}), PHY-CCA.indication(BUSY,{secondary}), or PHY-CCA.Indication(BUSY,{secondary40}) primitives, and shall not issue the secondary If there is any signal above -56 dBm in the 80 MHz channel, the PHY issues the PHY-CCA.indication(BUSY, {secondary80}) primitive. ), PHY-CCA.indication(BUSY,{secondary}), PHY-CCA.Indication(BUSY, {secondary40}) primitive does not exist, and an 80 MHz preamble or PPDU at -69 dBm or greater is detected in the secondary 80 MHz channel with a probability of 90% or greater within aCCAMidTime period in an idle 160 MHz or 80+80 MHz operating channel width, the PHY-CCA.indication(BUSY, {secondary80}) primitive shall be issued. The PHY shall not issue a PHY-CCA.indication(BUSY,{primary}), PHY-CCA.indication(BUSY,{secondary}), or PHY-CCA.Indication(BUSY, {secondary40}) primitive, and in an idle 160 MHz or 80+80 MHz operating channel width, receive a 40 MHz preamble or PPDU of -72 dBm or higher in any 40 MHz subchannel of the secondary 80 MHz channel within the aCCAMidTime If detected with a probability of 90% or more within the period, PHY-CCA.indication(BUSY, {secondary80}) The PHY issues a PHY-CCA.indication(BUSY,{primary}), PHY-CCA.indication(BUSY,{secondary}), or PHY-CCA.Indication(BUSY,{secondary40}) primitive when there are no conditions that would cause the PHY to issue such a primitive, and when, in an idle 160 MHz or 80+80 MHz operating channel width, a 20 MHz preamble or PPDU is detected at or above -72 dBm in any 20 MHz subchannel of the secondary 80 MHz channel with a probability of greater than 90% within aCCAMidTime. If so, it issues the PHY-CCA.indication(BUSY, {secondary80}) primitive, where -56 dBm, -69 dBm, and -72 dBm are the thresholds for determining whether the channel is idle or busy. That's fine.

[0138] The threshold may be compared to the signal level of the receiving antenna. The signal level to be transmitted may be the level of the signal received by the antenna unit SU1. The signal level compared with the threshold value may be the level of the signal received by the antenna unit AU1. stomach.

[0139] A STA may perform spatial reuse. Spatial reuse may be the transmission of a PPDU under specific conditions. Spatial reuse may be the transmission of a PPDU under specific conditions when a PPDU that prevents transmission is detected. Spatial reuse may be the transmission of a PPDU under specific conditions when a PPDU is received and If certain conditions are met, the NAV update based on that PPDU will not be performed and a back-off procedure and For example, spatial reuse operations may be performed to distinguish signals from overlapping BSSs (OBSSs) and manage interference, allowing for more frequent medium reuse between OBSSs in dense deployment scenarios. Spatial reuse may have two independent spatial reuse modes: OBSS PD-based spatial reuse and PSR-based spatial reuse. APs participating in spatial reuse send Beacon requests. A Beacon request / report pair may request associated non-AP STAs to collect information about their neighbors. A Beacon request / report pair allows a STA to request a list of APs that can receive Beacons on a specified channel from another STA. The Beacon request / report may provide a means for the requesting STA to obtain the Beacon, probe response, and measurement pilot information received from the responding STA. The AP may send a measurement mode notification in the Beacon request to associated STAs. A STA shall not configure modes that it does not explicitly support via the RM Enabled Capabilities element. The RM Enabled Capabilities element may advertise the STA's support for radio measurements. An AP sending a Beacon request may request that non-AP STAs collect information about BSSs that match a specific BSSID and / or SSID. An AP sending a Beacon request shall In addition, non-AP STAs can be requested to generate reports only on the channels on which the requesting AP is operating or on channels to which the requesting AP is considering switching. The AP sending the Beacon request helps determine the BSS color information of neighboring APs. To do this, even if a non-AP STA is requested to include the Operation element of the neighboring AP, good.

[0140] OBSS PD-based spatial reuse may have two operation types: The first type is to ignore inter-BSS PPDUs using Non-SRG OBSS PD level under certain conditions. The second type may allow a STA to ignore inter-BSS PPDUs identified as SRG PPDUs using the SRG OBSS PD level under certain conditions. The non-SRG OBSS PD Min offset may be fixed and defined in the specification. The SRG OBSS PD Min offset may be defined by the AP. A STA may operate using one of the two types, neither type, or both types simultaneously. In other words, a STA may operate using only the non-SRG OBSS PD level (the first type). A STA may , the STA may operate using only the SRG OBSS PD level (second type). The STA may operate using both the non-SRG OBSS PD level and the SRG OBSS PD level. The STA may operate without using either the non-SRG OBSS PD level or the SRG OBSS PD level.

[0141] A STA may receive a frame including a Spatial Reuse Parameter Set element. An AP may receive a frame including a Spatial Reuse Parameter Set element. The Spatial Reuse Parameter Set element may provide information required by the STA when implementing OBSS PD-based spatial reuse and PSR-based spatial reuse. For example, the Spatial Reuse Parameter Set element may be included in a frame such as a Beacon frame, an Association Response frame, a Reassociation Response frame, or a Probe Response frame. It may also be included in a frame other than the above. The Spatial Reuse Parameter Set element includes an Element ID This parameter may consist of the following fields: Non-SRG OBSS PD Max Offset, Length, Element ID Extension, SR control, Non-SRG OBSS PD Max Offset (if present), SRG OBSS PD Min Offset (if present), SRG OBSS PD Max Offset (if present), SRG BSS Color Bitmap (if present), and SRG Partial BSSID Bitmap (if present). The Non-SRG OBSS PD Max Offset field may contain an unsigned integer that is added to -82 dBm to generate the value of the Non-SRG OBSS PD Max parameter. The SRG OBSS PD Min Offset field generates the value of the SRG OBSS PD Min parameter. The SRG OBSS PD Max Offset field may contain an unsigned integer that is added to -82 dBm to produce the value of the SRG OBSS PD Max parameter. The SRG BSS Color Bitmap field is used to determine which BSS the transmitting STA is a member of. The SRG Partial BSSID Bitmap field may be a bitmap indicating the BSS color values ​​used by members of the SRG of which the transmitting STA is a member. The SRG Partial BSSID Bitmap field may be a bitmap indicating the partial BSSID values ​​used by members of the SRG of which the transmitting STA is a member.

[0142] The SR control field is the PSR Disallowed subfield, Non-SRG OBSS PD SR Disallowed The PSR Disallowed subfield of the SR control field may consist of the following: Is PSR-based SR transmission permitted for non-AP STAs associated with the AP that sent this element? If the PSR Disallowed subfield is 1, PSR-based SR transmission is allowed. When the PSR Disallowed subfield is 0, PSR-based SR transmission is not allowed. The Non-SRG OBSS PD SR subfield of the SR control field may indicate whether Non-SRG OBSS PD SR transmission is permitted for non-AP STAs associated with the AP that transmitted this element. When the Non-SRG OBSS PD SR subfield is 1, Non-SRG OBSS PD SR transmission is permitted. When the Non-SRG OBSS PD SR subfield is 0, Non-SRG OBSS PD SR transmission is allowed. The Non-SRG Offset Present subfield of the SR control field may indicate whether the Non-SRG OBSS PD Max Offset field is present in the Spatial Reuse Parameter Set element. When the Non-SRG Offset Present subfield is 1, the Non-SRG OBSS PD Max Offset field is present. When the SRG Information Present subfield is 1, the Non-SRG OBSS PD Max Offset field is not present. The SRG Information Present subfield of the SR control field may indicate whether the SRG OBSS PD Min Offset field and the SRG OBSS PD Max Offset field are present. The SRG Information Present subfield may indicate whether the SRG OBSS PD Min Offset field, SRG OBSS PD Max Offset field, SRG BSS Color Bitmap field, and SRG Partial BSSID Bitmap field are present in the Spatial Reuse Parameter Set element. When the SRG Information Present subfield is 1, the SRG OBSS PD Min Offset field and SRG OBSS PD Max Offset field are present. Set field, SRG BSS Color Bitmap field, SRG Partial BSSID Bitmap field When the SRG Information Present subfield is 0, the SRG OBSS PD Min Offset field, SRG OBSS PD Max Offset field, SRG BSS Color Bitmap field, and SRG Partial BSSID Bitmap field are not present. The HESIGA_Spatial_reuse_value15_allowed subfield of the SR control field may indicate whether non-AP STAs associated with the AP that transmitted this element can set the TXVECTOR parameter SPATIAL_REUSE to PSR_AND_NON_SRG_OBSS_PD_PROHIBITED.

[0143] The PHY may provide an interface to the MAC. The MAC may provide an interface to the PHY. This interface may include a TXVECTOR and an RXVECTOR. MAC The PHY may use TXVECTOR to provide per-PPDU transmission parameters to the PHY. The PHY may use RXVECTOR to notify the MAC of the parameters of the received PPDU. TXVECTOR may be one or more may include multiple parameters. TXVECTOR parameters may include LENGTH, DATARATE, PREAMBLE_TYPE, CH_BANDWIDTH_IN_NON_HT, CH_BANDWIDTH, BSS_COLOR, SPATIAL_REUSE, etc. RXVECTOR may include one or more parameters. RXVECTOR parameters may include LENGTH, DATARATE, PREAMBLE_TYPE, CH_BANDWIDTH_IN_NON_HT, CH_BANDWIDTH, BSS_COLOR, SPATIAL_REUSE, etc.

[0144] The content of the Spatial Reuse field may be included in the TXVECTOR parameter SPATIAL_REUSE of the PPDU indicating spatial reuse information. PSR_DISALLOW may be used to prohibit PSR-based spatial reuse during the transmission of the corresponding PPDU. PSR_AND_NON_SRG_OBSS_PD_PROHIBITED may be used to prohibit both PSR-based spatial reuse and non-SRG OBSS PD-based spatial reuse during the transmission of the corresponding PPDU. The TXVECTOR parameter SPATIAL_REUSE and the RXVECTOR parameter SPATIAL_REUSE specify the spatial reuse parameter value. For example, the TXVECTOR parameter SPATIAL_REUSE may indicate one of PSR_DISALLOW, SR_RESTRICTED, SR_DELAYED, or PSR_AND_NON_SRG_OBSS_PD_PROHIBITED. If a STA allows OBSS PD based spatial reuse only after the end of the PPDU, the STA may set the TXVECTOR parameter SPATIAL_REUSE in the PPDU to SR_DELAYED. If OBSS PD based spatial reuse is permitted before termination, the TXVECTOR parameter SPATIAL_REUSE in the PPDU may be set to SR_RESTRICTED.

[0145] A STA may classify a received PPDU as an inter-BSS PPDU if at least one of the following conditions is true: RXVECTOR parameter BSS_COLOR is not 0, and the BSS color of the BSS to which the STA is a member is Not Ra. The PPDU is sent with the BSSID[39:47] of the BSS to which the STA is associated, or the same BSS to which the STA belongs. If the BSSID is equal to BSSID[39:47] of any other BSS in the Multiple BSSID Set or Co-host BSSID Set PPDUs with RXVECTOR parameter GROUP_ID set to 0. The PPDU is a PPDU in which the partial BSS Color field of the latest HE operation element is 1, the RXVECTOR parameter PARTIAL_AID[5:8] is not equal to the four LSBs of the BSS color advertised by the BSS of which the STA, for which dot11PartialBSSColorImplemented is true, is a member, and the RXVECTOR parameter GROUP_ID is equal to 63. The PPDU is either a PPDU with RXVECTOR parameter UPLINK_FLAG equal to 0 or a HE MU PPDU, and the STA is the AP. The PPDU carries a frame with a BSSID field whose value is not the BSSID of the BSS to which the STA is associated, nor is it the BSSID of any other BSS in the same multiple BSSID set or co-host BSSID set to which that BSS belongs, nor is it a wildcard BSSID. The PPDU carries a frame without a BSSID field, but with both an RA field and a TA field, both of which are equal to the BSSID of the BSS to which the STA is associated, and to the BSSIDs of other BSSs in the same multi-BSSID set or co-host BSSID set to which that BSS belongs. do not have.

[0146] A STA may classify a received PPDU as an intra-BSS PPDU if at least one of the following conditions is true: · The RXVECTOR parameter BSS_COLOR of the PPDU carrying the frame is the BSS color of the BSS of which the STA is a member, or the BSS color of the TDLS link to which the STA belongs if the STA is a non-AP associated STA. ·The PPDU is a VHT PPDU, and the RXVECTOR parameter PARTIAL_AID is equal to the BSSID[39:47] of the BSS to which the STA is associated or of any other BSS in the same multi-BSSID set or co-host BSSID set to which that BSS belongs, and the RXVECTOR parameter GROUP_ID is equal to 0. The PPDU is a VHT PPDU, and the RXVECTOR parameter PARTIAL_AID[5:8] is the BSS color announced by the BSS to which the STA is a member, with dot11PartialBSSColorImplemented set to true. , the RXVECTOR parameter GROUP_ID is equal to 63, and the Partial BSS Color field of the latest HE Operation element is 1. The PPDU is sent with the RA, TA, or BSSID field value of the BSS, or the BSS to which the STA is associated, or or carries frames equal to the BSSID of another BSS in the same multi-BSSID set or co-host BSSID set to which the BSS belongs. The PPDU carries a control frame with no TA field and an RA field value that matches the saved TXOP holder address of the BSS to which the STA is associated or of another BSS in the same multi-BSSID set or co-host BSSID set to which that BSS belongs.

[0147] If the received PPDU satisfies both the intra-BSS and inter-BSS conditions based on the MAC address information of the frame contained in the received PPDU, the received PPDU is classified as an intra-PPDU. The received PPDU satisfies the intra-BSS condition using the RXVECTOR parameter BSS_COLOR, If the inter-BSS condition using the MAC address information of the frame included in the PPDU is also satisfied, the classification using the MAC address information may be prioritized. If so, the RXVECTOR parameter BSS_COLOR of the PPDU may not be used to classify the PPDU.

[0148] For example, an intra-BSS PPDU may be a PPDU received from a STA or AP that belongs to the same BSS, or an intra-BSS PPDU may be a PPDU received from a synchronized STA or AP. For example, an inter-BSS PPDU may be a PPDU received from a STA or AP that belongs to a different BSS. An inter-BSS PPDU may be a PPDU received from an unsynchronized STA or AP. For example, in FIG. 2, the PPDU received by 204 from 202 or 203 may be an intra-BSS PPDU. For example, in FIG. 2, the PPDU received by 202 from 203 or 204 may be an intra-BSS PPDU. For example, in FIG. 2, the PPDU received by 204 from 207 or 206 may be an inter-BSS PPDU. For example, in FIG. 2, the PPDU received by 202 from 207 or 206 may be an inter-BSS PPDU. For example, in FIG. 2, the PPDU received by 207 from 202 or 204 may be an inter-BSS PPDU. For example, in FIG. 2, the PPDU received by 207 from 206 or 208 may be an intra-BSS PPDU. An inter-BSS PPDU may also be an OBSS PPDU. The OBSS PPDU may be an inter-BSS PPDU. The inter-BSS PPDU may also be referred to as an OBSS PPDU.

[0149] The PHY-RXSTART.indication primitive may notify the local MAC entity that the PHY has received a valid start of a PPDU containing a valid PHY header. The PHY-RXSTART.indication primitive may provide an RXVECTOR, which may represent a list of parameters that the PHY provides to the local MAC entity upon receiving a valid PHY header. The PHY-RXSTART.indication primitive indicates that the PHY should correctly align the PHY header at the start of a new PPDU. Whenever a PHY is verified, it may be generated from the local PHY entity to the MAC sublayer. After generating the HY-RXSTART.indication primitive, a frame of the specified length is The physical medium may remain busy for the period required to transfer at the specified DATARATE ( (i.e., do not generate a PHY-CCA.indication(IDLE) primitive). The PHY entity may issue a PHY-RXEARLYSIG.indication primitive to begin receiving the U-SIG field and identify the PPDU version based on the PHY Version Identifier field in the U-SIG field. The PHY may not issue either a PHY-RXEARLYSIG.indication primitive or a PHY-RXSTART.indication primitive in response to a PPDU that does not overlap with the primary channel unless the AP's PHY receives an EHT TB PPDU requested by the AP. The PHY may issue both a PHY-RXEARLYSIG.indication primitive and a PHY-RXSTART.indication primitive for a PPDU requested by the AP. Good too.

[0150] The PHY-CCARESET.request primitive is a request from the MAC sublayer to the local PHY entity to reset the PHY to the state appropriate for the end of a received frame and may be a primitive to turn IPI reporting on or off using the IPI-STATE parameter. may be present if dot11RadioMeasurementActivated is true. IPI (Idle Power Indicator) may be a physical layer (PHY) indication of the total channel power (noise and interference) measured on the channel of the receive antenna connector when the STA is in idle state, i.e., not transmitting or receiving frames. The PHY-CCARESET.request primitive may be generated by the MAC sublayer for the local PHY entity at the end of NAV and at a specified time after each MAC slot boundary. The PHY-CCARESET.request primitive may also be generated by the MAC sublayer for the local PHY entity if the conditions for spatial reuse are met.

[0151] In Non-SRG OBSS PD level operation, the PHY (physical layer) of the STA receives the PPDU. If a STA issues a PHY-RXEARLYSIG.indication or a PHY-RXSTART.indication following a PHY-CCA.indication(BUSY), the MAC (MAC sublayer) of the STA shall consider the first, second, and third conditions. If all of the first, fourth, fifth, sixth, and seventh conditions are met, the STA may issue a PHY-CCARESET.request primitive before the end of the PPDU without updating the NAV timer based on that PPDU, or may treat the PPDU as not received for NAV timer purposes (without updating the NAV timer). The first condition is that the STA has the TXVECTOR parameter SPATIAL REUSE present and has not set the TXVECTOR parameter SPATIAL_REUSE to the value PSR_AND_NON_SRG_OBSS_PD_PROHIBITED in any PPDUs that the STA transmitted in the current Beacon period and the previous Beacon period. The second condition is that the Non-SRG OBSS PD SR Disallowed subfield of the most recent Spatial Reuse Parameter Set element received from the associated AP is 0, or a non-AP STA that has not received a Spatial Reuse Parameter Set element from its associated AP, or the STA is an AP and has sent the most recent Spatial Reuse Parameter Set element Non-SRG OBSS PD SR Disallowed subfield is 0, or the STA is an AP and Spatial Reuse is enabled. The third condition is that the received PPDU is an inter-BSS PPDU and not a non-HT PPDU carrying a response frame, or if the received PPDU contains a CTS, the PHY-CCA.indication changes from BUSY to IDLE within the PIFS immediately preceding the received CTS. RTS frame in which a transition occurs and the transition is discarded according to OBSS PD based spatial reuse The fourth condition is that the STA is operating at the SRG OBSS PD level and the received PPDU is not an SRG PPDU, or the STA is not operating at the SRG OBSS PD level. The fifth condition is that the RXVECTOR parameter of the received PPDU is SPATIAL_REUSE (existing). The sixth condition is that the PSR_AND_NON_SRG_OBSS_PD_PROHIBITED parameter (if present) is not set to PSR_AND_NON_SRG_OBSS_PD_PROHIBITED. , L-STF or L-LTF field of PPDU, or PHY SYNC field, shortSYNC field field, or Long PHY SYNC field (whichever is present) determines the PHY-CCA.indication. The received signal strength level measured from the STA (used for the OBSS PD level) is below the non-SRG OBSS PD level. The seventh condition is that the (received) PPDU has an RA field equal to the STA MAC address. non-HE PPDU carrying a Public Action frame, non-HE PPDU carrying a Public Action frame, NDP Announcement frame In other words, in non-SRG OBSS PD level operation, the STA shall not transmit PPDUs carrying a ENT frame or a Fine Timing Measurement frame, nor a non-HE NDP. If received and multiple conditions are met, the PPDU may be ignored without updating the NAV.

[0152] In non-SRG OBSS PD level operation, the STA must be able to transmit the HE sounding NDP or HE TB. SR does not need to be performed on the feedback NDP. In non-SRG BSS PD level operation, the frame is identified as an inter-BSS PPDU. If the signal is transmitted at a power of 3 dB (power boost of 3 dB), subtract 3 dB from the received signal strength measured from the L-STF or L-LTF field of the PPDU and use it to determine the PHY-CCA.indication. In non-SRG OBSS PD level operation, if the (received) PPDU is a HE SU PPDU or a HE ER SU PPDU and the RXVECTOR parameter SPATIAL_REUSE indicates SR_DELAYED, the PHY-CCARESET.request The primitive may be issued at the end of the PPDU. If the STA allows OBSS PD based spatial reuse only after the end of the PPDU, the STA may set the TXVECTOR parameter SPATIAL_REUSE in the PPDU to SR_DELAYED. In non-SRG OBSS PD level operation, the primitive may be issued at the end of the received PPDU. If a PHY-CCARESET.request primitive is issued before the end of the TXOP and a TXOP is started within the duration of the received PPDU, the duration of the TXOP and the PPDU transmission within that TXOP shall be the same as the duration of the received PPDU, if the received PPDU is a HE MU PPDU and the RXVECTOR parameter SPATIAL_REUSE indicates SR_RESTRICTED. If a STA allows OBSS PD based spatial reuse before the end of the PPDU, it may set the TXVECTOR parameter SPATIAL_REUSE in the PPDU to SR_RESTRICTED. STAs that ignore PPDUs according to the procedure for non-SRG OBSS PD level operation are This may be considered as implementing PD-based spatial reuse.

[0153] In SRG OBSS PD level operation, when the PHY (physical layer) of a STA issues a PHY-RXEARLYSIG.indication or a PHY-RXSTART.indication following a PHY-CCA.indication(BUSY) upon receiving a PPDU, the MAC (MAC sublayer) of the STA shall, if all of the first, second, and third conditions are met, not update the NAV timer based on the PPDU and shall The PHY-CCARESET.request primitive may be issued before the end of the PPDU, or the PPDU may be treated as not received for NAV timer purposes (the NAV timer is not updated). The first condition is that the received PPDU is an SRG PPDU. The second condition is that the PPDU's L-STF or L-LTF field, or the PHY SYNC field, shortSYNC field, or Long PHY SYNC field is not set. The received signal strength level, as measured from the field (if any is present and used to determine the PHY-CCA.indication), is below the SRG OBSS PD level. The (received) PPDU is not a non-HE PPDU carrying a frame with the RA field equal to the STA MAC address, a non-HE PPDU carrying a Public Action frame, a non-HE PPDU carrying an NDP Announcement frame or a Fine Timing Measurement frame, or a non-HE NDP. In other words, in SRG OBSS PD level operation, a STA may receive a PPDU and ignore it without updating its NAV if multiple conditions are met.

[0154] In SRG OBSS PD level operation, a STA does not have to perform SR on the HE sounding NDP or the HE TB feedback NDP. In SRG OBSS PD level operation, if a frame is transmitted in a HE ER SU PPDU identified as an inter-BSS PPDU (the power of the L-STF / L-LTF symbols is boosted by 3 dB), the power measured from the L-STF or L-LTF field of the PPDU shall be Subtract 3 dB from the received signal strength and use it to determine the PHY-CCA indication. The power difference may be corrected by comparing with the OBSS PD level. In SRG OBSS PD level operation, if the (received) PPDU is a HE SU PPDU or HE ER SU PPDU and the RXVECTOR parameter SPATIAL_REUSE indicates SR_DELAYED, the PHY-CCARESET.request primitive may be issued at the end of the PPDU. In SRG OBSS PD level operation, if the PHY-CCARESET.request primitive is issued before the end of the received PPDU and the TXOP If the received PPDU is a HE MU PPDU and the RXVECTOR parameter SPATIAL_REU If the SE indicates SR_RESTRICTED, the duration of the TXOP and the PPDU transmission within that TXOP may be limited to the duration of the received PPDU.

[0155] When using OBSS PD-based spatial reuse, the STA maintains the OBSS PD level and adjusts the transmission power. The OBSS PD level may be adjusted depending on the PPDU_BW value obtained from the input and received PPDU. The PD level is that of Non-SRG OBSS PD level operation and SRG OBSS PD level operation. The OBSS PD level may be set for each STA. The OBSS PD level may be adjusted based on OBSS_PDmin, OBSS_PDmax, TX_PWRref, TX_PWR, and PPDU_BW. TX_PWRref may be a predefined value. For example, TX_PWRref may be defined as 21 dBm for non-AP STAs. TX_PWRref may be defined as 21 dBm or 25 dBm for AP STAs. TX_PWR is the minimum value for all APs. PPDU_BW may be the total transmit power (dBm) at the transmit antenna connector of the antenna. PPDU_BW may be determined using the received RXVECTOR parameter. PPDU_BW may be determined based on CH_BANDWIDTH if CH_BANDWIDTH is present in the received RXVECTOR parameter. PPDU_BW may be determined based on CH_BANDWIDTH if CH_BANDWIDTH is not present in the received RXVECTOR parameter but CH_BANDWIDTH_IN_NOT_HT is present. PPDU_BW may be determined based on CH_BANDWIDTH_IN_NOT_HT if CH_BANDWIDTH is not present in the received RXVECTOR parameter but CH_BANDWIDTH_IN_NOT_HT is present. If CH_BANDWIDTH and CH_BANDWIDTH_IN_NOT_HT are present in the received RXVECTOR parameter, the PPDU_BW may be determined based on the DATARATE. For example, if CH_BANDWIDTH or CH_BANDWIDTH_IN_NOT_HT indicates CBW20, HT_CBW20, or NON_HT_CBW20, the PPDU_BW may be 20 MHz. If CH_BANDWIDTH or CH_BANDWIDTH_IN_NOT_HT indicates CBW40, HT_CBW40, or NON_HT_CBW40, the PPDU_BW may be 40 MHz. If CH_BANDWIDTH or CH_BANDWIDTH_IN_NOT_HT indicates CBW80, HE-CBW-PUNC80-PRI, or HE-CBW-PUNC80-SEC, the PPDU_BW may be 80 MHz. CH_BANDWIDTH If CH_BANDWIDTH_IN_NOT_HT indicates CBW160, CBW80+80, HE-CBW-PUNC160-PRI20, HE-CBW-PUNC80+80-PRI20, HE-CBW-PUNC160-SEC40, or HE-CBW-PUNC80+80-SEC40, then PPDU_BW may be 160 MHz. If DATARATE is 1, 2, 5.5, or 11, PPDU_BW may be 20 MHz. OBSS_PDmin is the Non-SRG OBSS PD Min. It may also be referred to as OBSS_PDmax, Non-SRG OBSS PD Max. Non-SRG OBSS PD Min and Non-SRG OBSS PD Max are determined by the Non-SRG OBSS PD SR Disallowed field and / or the Non-SRG Offset Present field in the Spatial Reuse Parameter Set element, and The Non-SRG OBSS PD Min and / or Non-SRG OBSS PD Max Offset fields may be used to determine the Non-SRG OBSS PD Min and / or Non-SRG OBSS PD Max. For example, if a Spatial Reuse Parameter Set element is not received, Non-SRG OBSS PD Min may be −82 (dBm) and Non-SRG OBSS PD Max may be −62 (dBm). For example, if the Non-SRG OBSS PD SR Disallowed field in the Spatial Reuse Parameter Set element indicates 0 and the Non-SRG Offset Present field indicates 0, Non-SRG OBSS PD Min and Non-SRG OBSS PD Max may be −62 (dBm). For example, if the Non-SRG OBSS PD SR Disallowed field in the Spatial Reuse Parameter Set element indicates 0 and the Non-SRG Offset Present field indicates 1, Non-SRG OBSS PD Min and Non-SRG OBSS PD Max may be used. In this case, Non-SRG OBSS PD Min may be -82 (dBm) and Non-SRG OBSS PD Max may be -82 + Non-SRG OBSS PD Max Offset (dBm). For example, if the Non-SRG OBSS PD SR Disallowed field in the Spatial Reuse Parameter Set element is 1 and the Non-SRG Offset Present field is not present, If not, Non-SRG OBSS PD Min may be -82 (dBm), and Non-SRG OBSS PD Max may be -82 (dBm). OBSS_PDmin may be referred to as SRG OBSS PD Min. OBSS_PDmax may also be referred to as SRG OBSS PD Max. SRG OBSS PD Min and SRG OBSS PD Max may be determined using the SRG Information Present field and / or the SRG OBSS PD Min Offset field and / or the SRG OBSS PD Max Offset field in the Spatial Reuse Parameter Set element. For example, if a Spatial Reuse Parameter Set element is not received, or Or, if SRG information does not exist, the STA cannot determine that the PPDU is an SRG. , the STA may not determine the SRG OBSS PD Min and SRG OBSS PD Max. That is, the SRG OBSS PD Min and SRG OBSS PD Max may be N / A. For example, if the SRG Information Present field is 0, the STA may not determine the SRG OBSS PD Min and SRG OBSS PD Max. That is, SRG OBSS PD Min and SRG OBSS PD Max may be N / A. For example, When the Information Present field is 1, the SRG OBSS PD Min may be −82+SRG OBSS PD Min Offset (dBm), and the SRG OBSS PD Max may be −82+SRG OBSS PD Man Offset (dBm).

[0156] If the STA ignores the inter-BSS PPDU, the STA may resume EDCAF procedures after the PHY-CCARESET.request primitive is sent, unless the medium is indicated as BUSY.

[0157] STAs subject to non-SRG OBSS PD level operation and SRG OBSS PD level operation: The following additional conditions may be observed: If the RXVECTOR parameter SPATIAL_REUSE of an EHT SU transmission indicates SR_DELAYED, the PHY-CCARESET.request primitive may be issued at the end of the PPDU. If the PHY-CCARESET.request primitive is issued before the end of the received PPDU and a TXOP is initiated within the duration of the received PPDU, if the received PPDU is an EHT MU PPDU addressed to multiple STAs and the RXVECTOR parameter SPATIAL_REUSE indicates SR_RESTRICTED, the duration of the TXOP and the PPDU transmissions within that TXOP may be limited to the duration of the received PPDU. The reception parameter used to determine whether the OBSS PD level is below the non-SRG or SRG OBSS PD level. The signal strength level shall be determined by the L-STF or L-LTF field in at least one of the nonpunctured 20 MHz subchannels of the PPDU, or the PHY SYNC field, shortSYNC field, or Long The PHY SYNC field is used to determine whether the PHY-CCA.indication is present. The received signal strength level may be measured in dBm / 20 MHz from the field of interest. Which of these 20 MHz sub-channels the received signal strength level is measured on may vary depending on the implementation.

[0158] In the present invention, a non-primary channel access (NPCA) primary channel may be defined. The NPCA primary channel is accessed while the primary channel is busy. The NPCA primary channel may be a channel that is accessed by OBSS traffic while the primary channel is busy. The NPCA primary channel may be called something other than the NPCA primary channel. For example, the NPCA primary channel may be called the secondary primary channel.

[0159] In the present invention, the AP and / or STA performs NPCA (Non Primary Channel Access). NPCA may be an operation to access other channels while the primary channel is busy due to OBSS traffic. For example, OBSS traffic may be PPDUs received from the OBSS. OBSS traffic may be inter-BSS PPDUs. The AP and / or STA may perform a backoff procedure on other channels while the primary channel is busy due to OBSS traffic. For example, backoff may occur while the primary channel is busy due to OBSS traffic. The channel on which the procedure is performed is 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. The OBSS traffic may be called by other names. If the primary channel becomes busier, the NPCA primary channel performs a backoff procedure. APs and / or STAs may receive NAV information from the OBSS PPDU on the primary channel. The AP and / or STA may perform a backoff procedure on the NPCA primary channel during the period when the backoff procedure is completed on the NPCA primary channel. The AP may transmit on one or more channels, including but not limited to the primary channel. and / or the STA may switch to the primary channel before the NAV period expires. The AP may transmit information related to NPCA primary channel access in a frame. The STA determines the operation related to NPCA primary channel access based on the frame received from the AP. may be determined.

[0160] When a STA or AP is idle on the primary channel, it will If the primary channel is busy, the STA or AP may sense 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. If the primary channel is busy due to OBSS traffic, the STA or AP may sense 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. For example, the OBSS traffic may be an 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. The AP must have at least one NPCA primary channel and no primary channel. Reception may be performed on multiple channels.

[0161] A STA or AP may transmit using multiple channels in NPCA. When a STA or AP transmits using multiple channels in NPCA, the STA or AP performs a backoff procedure on the NPCA primary channel and then transmits the desired number of channels on the NPCA secondary channel immediately before transmission. The NPCA secondary channel may be a channel other than the NPCA primary channel for transmitting using multiple channels in the NPCA. The NPCA secondary channel may be defined as an NPCA secondary 20MHz channel, an NPCA secondary 40MHz channel, or an NPCA secondary 80MHz channel. The NPCA secondary 20MHz channel may be a 20MHz channel related to the NPCA primary channel. For example, when transmitting in the 40 MHz bandwidth in the NPCA, a STA or AP 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 associated with the NPCA primary channel. For example, when transmitting in an 80 MHz bandwidth in NPCA, a STA or AP may transmit using an NPCA primary channel, an NPCA secondary 20 MHz channel, and an NPCA secondary 40 MHz channel. The NPCA secondary 40 MHz channel is divided into two 20 MHz channels. An NPCA secondary 80 MHz channel may be an 80 MHz channel associated with an NPCA primary channel. For example, when transmitting in the 160 MHz bandwidth in NPCA, an STA or AP may transmit using the NPCA primary channel, an NPCA secondary 20 MHz channel, an NPCA secondary 40 MHz channel, and an NPCA secondary 80 MHz channel. An NPCA secondary 80 MHz channel may be composed of four 20 MHz channels. An NPCA secondary channel may be referred to as something other than an NPCA secondary channel. For example, an NPCA secondary channel may be referred to as a secondary secondary channel. An NPCA secondary 20 MHz channel may be referred to by a name other than an NPCA secondary 20 MHz channel. For example, an NPCA secondary 20 MHz channel may be referred to as a secondary secondary 20 MHz channel. An NPCA secondary 40 MHz channel may be referred to by a name other than an NPCA secondary 40 MHz channel. For example, an NPCA secondary 40 MHz channel may be referred to as a secondary secondary 40 MHz channel. An NPCA secondary 80 MHz channel may be referred to by a name other than an NPCA secondary 40 MHz channel. It may be referred to as a secondary 80MHz channel, e.g., NPCA secondary 80MHz The channel may also be referred to as a secondary 80 MHz channel.

[0162] FIG. 13 illustrates a backoff procedure on the NPCA primary channel of a STA according to one aspect of the present embodiment. 13 is a diagram showing an example of a 160 MHz channel. 1301, 1302, 1303, 1304, 1305, 1306, 1307, and 1308 may each be a 20 MHz channel. 1309 may be a frame transmitted by another STA or AP that is received by the STA. 1309 may be a frame transmitted by a STA or AP that belongs to an OBSS that is received by the STA. For example, 1309 may be an RTS frame. 1309 may be a CTS frame. 1309 may be a Data frame. 130 may be the NAV. 1311 is the backoff procedure (backoff counter, 1312 may be a frame transmission. When the STA receives 1309 in 1301, it sends the expected time indicated by the Duration field of 1309. 1301 to 1310 may be set between 1301 and 1310. When 1301 to 1310 is set, the STA If the STA moves to 1306, it starts 1311 in 1306. When 1311 is completed, the STA may start 1312. Here, for example, 2. The STA that performs the operation of FIG. 13 is 204 in FIG. 2. 1309 is the same as the STA that performs the operation of FIG. 13 may be a frame transmitted by 207. FIG. 13 may be a diagram of an AP operating at 160 MHz. For example, FIG. 13 shows the operation of 202 in FIG. 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 be NPCA secondary channels. The 80 MHz transmission may be transmitted using 13 Transmission may be via the NPCA primary channel 06, the NPCA secondary 20 MHz channel 1305, and the NPCA secondary 40 MHz channel consisting of 1307 and 1308.

[0163] The AP includes an information element containing information related to Non-Primary Channel Access. When performing Non-Primary Channel Access, the AP transmits a frame including an information element containing information related to Non-Primary Channel Access. The AP may send a frame containing an information element containing information related to Non Primary Channel Access to indicate to the STAs in the BSS whether Non Primary Channel Access is enabled or disabled. The AP must not use Non Primary Channel Access in its own BSS. If the information element does not include information related to Non Primary Channel Access, the frame to be transmitted does not need to include information related to Non Primary Channel Access. An information element including information related to Non Primary Channel Access may be called an NPCA operation element. For example, an information element including information related to Non Primary Channel Access may be called a UHR operation element. An information element including information related to Non Primary Channel Access may be called by a name other than those mentioned above. An Element ID for an NPCA operation element may be set. An Element ID for a UHR operation element may be set. For example, the NPCA operation element may indicate information for Non Primary Channel Access. The NPCA operation element may be composed of one or more fields. The NPCA operation element may include a field indicating an Element ID. The NPCA operation element may include a field indicating whether Non Primary Channel Access is enabled or disabled. The NPCA operation element may indicate the NPCA operation for Non Primary Channel Access. A field may be included to indicate the location of the primary channel. The element contains a field to indicate the channel width of Non Primary Channel Access. Fields other than those mentioned above may be included in the NPCA operation element. For example, when a STA receives a frame including an NPCA operation element from an AP, it may perform Non Primary Channel Access. When a STA receives a frame including an NPCA operation element from an AP, it may perform Non Primary Channel Access using the information indicated in the fields of the NPCA operation element. When a STA receives a frame including an NPCA operation element from an AP, it may perform Non Primary Channel Access using the information indicated in the fields of the NPCA operation element. If a STA receives a frame containing the NPCA operation element from the AP, indicating that Non-Primary Channel Access is enabled, the STA may perform Non-Primary Channel Access. If the STA does not receive a frame containing If a frame including an NPCA operation element is received from a UHR STA and indicates that Non Primary Channel Access is disabled, Non Primary Channel Access is not performed. For example, the UHR operation element may indicate information for controlling a UHR STA. For example, the UHR operation element may indicate information for Non Primary Channel Access. The UHR operation element may be composed of one or more fields. The UHR operation element may include a field indicating an Element ID. The UHR operation element determines whether information related to Non Primary Channel Access is included in the UHR operation element. The UHR operation element may include a field indicating whether Non Primary Channel Access is enabled or disabled. The UHR operation element may include a field for indicating the position of the NPCA primary channel for Primary Channel Access. If the UHR operation element indicates that information related to Non-Primary Channel Access is included in the UHR operation element, it may include a field for indicating the position of the NPCA primary channel for Non-Primary Channel Access. The UHR operation element may include a field for indicating the channel width for Non-Primary Channel Access. If the UHR operation element indicates that information related to Non-Primary Channel Access is included in the UHR operation element, it may include a field for indicating the channel width for Non-Primary Channel Access. Fields other than those mentioned above may be included in the UHR operation element. For example, when a STA receives a frame including a UHR operation element from an AP, it may perform Non-Primary Channel Access. The STA may perform Non-Primary Channel Access when receiving a frame including a UHR operation element from the AP. If a STA receives a frame including a UHR operation element from the AP, it may perform Non-Primary Channel Access using the information indicated in the UHR operation element field. If a STA receives a frame including a UHR operation element from the AP and the UHR operation element indicates that Non-Primary Channel Access is enabled, it may perform Non-Primary Channel Access. If a STA does not receive a frame including a UHR operation element from the AP, it may perform Non-Primary Channel Access. If the STA receives a frame including a UHR operation element from the AP and indicates that Non-Primary Channel Access is disabled, the STA does not perform Non-Primary Channel Access. If the received UHR operation element includes information related to Non-Primary Channel Access, the STA If the STA receives a UHR operation element, the STA may perform Non-Primary Channel Access if the information related to Non-Primary Channel Access is included in the UHR operation element. If it indicates that it is not included, Non Primary Channel Access is not performed.

[0164] For example, in FIG. 1, 102 may transmit a frame including an information element containing information related to Non Primary Channel Access to a STA in BSS (101). 102 and 104 may receive a frame including an information element containing information related to Non-Primary Channel Access. That is, 102 may perform Non-Primary Channel Access based on the transmitted information related to Non-Primary Channel Access. 102 and 104 may perform Non-Primary Channel Access using the received information related to Non-Primary Channel Access. For example, 102 may not include information related to Non-Primary Channel Access in the frame to be transmitted. 103 and 104 may receive a frame including an information element containing information related to Non-Primary Channel Access from 102. In other words, 102 does not transmit a frame containing an information element that includes information related to Non Primary Channel Access. If not, 102, 103, and 104 do not perform Non Primary Channel Access. For example, 102 may transmit a frame including an NPCA operation element to STAs in BSS (101). 103 and 104 may receive a frame including an NPCA operation element. That is, 102 may perform Non Primary Channel Access based on the transmitted NPCA operation element. 103 and 104 may perform Non Primary Channel Access using the received NPCA operation element. 102 may indicate whether Non Primary Channel Access is enabled or disabled in the NPCA operation element. 103 and 104 may determine whether Non Primary Channel Access is enabled or disabled based on the received NPCA operation element. For example, 102 may transmit a frame including a UHR operation element to STAs in BSS (101). 103 and 104 may receive a frame including a UHR operation element. 102 may transmit a frame including a UHR operation element to STAs belonging to 101. In the UHR operation element, if the user indicates that Non Primary Channel Access is enabled, 103 and 104 are fields indicating whether or not information related to Non Primary Channel Access exists in the received UHR operation element. This field indicates whether information related to Non Primary Channel Access exists. If it is indicated that Non Primary Channel Access is disabled, Non Primary Channel Access may be performed. 102 is a field indicating whether or not information related to Non Primary Channel Access exists in the UHR operation element when indicating that Non Primary Channel Access is disabled for the STA belonging to 101, and indicates that information related to Non Primary Channel Access does not exist. 103 and 104 indicate that information related to Non Primary Channel Access does not exist in the Non Primary Channel Access in the received UHR operation element. If the field indicating whether or not related information exists indicates that there is no information related to Non Primary Channel Access, Non Primary Channel Access is not performed. Here, 103 and 104 may be UHR STAs. For example, when 103 is a UHR STA and 104 is an EHT STA, the information related to Non Primary Channel Access transmitted by 102 is When 103 and 104 receive a frame containing an information element containing information to , 103 can obtain information related to Non Primary Channel Access, and 104 may not be able to obtain information related to Non Primary Channel Access. When 103 is a UHR STA and 104 is an EHT STA, 103 and 104 receive a frame including an information element containing information related to Non Primary Channel Access transmitted by 102. 103 and 104 may then be able to obtain information related to Non Primary Channel Access.

[0165] The STA or AP may determine whether a frame transmitted by an AP belonging to another BSS includes an information element containing information related to Non Primary Channel Access. For example, In Figure 2, 204 and 202 may belong to a different BSS than 206. is a frame containing an information element containing information related to Non Primary Channel Access. 204 and 202 may receive a frame containing an information element containing information related to Non Primary Channel Access transmitted by 206, and The information related to Non-Primary Channel Access of a BSS (205) different from the BSS (201) that 206 is connected to can be known. For example, if the frame transmitted by 206 contains an information element including information related to Non-Primary Channel Access, 205 may determine that Non-Primary Channel Access will be performed. For example, if the frame transmitted by 206 does not contain an information element including information related to Non-Primary Channel Access, 205 may determine that Non-Primary Channel Access will not be performed.

[0166] The TXVECTOR parameter may include information related to Non-Primary Channel Access. For example, the information related to Non-Primary Channel Access included in the TXVECTOR parameter may be referred to as NON_PRIMARY_CHANNEL_ACCESS. The information related to Non-Primary Channel Access included in the TXVECTOR parameter may be referred to as the TXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS. Information related to Non-Primary Channel Access included in the RXVECTOR parameter For example, information related to Non Primary Channel Access included in the RXVECTOR parameter may be referred to as NON_PRIMARY_CHANNEL_ACCESS. Information related to Non Primary Channel Access included in the RXVECTOR parameter may be referred to as the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS. NON_PRIMARY_CHANNEL_ACCESS may indicate that Non Primary Channel Access is enabled. NON_PRIMARY_CHANNEL_ACCESS may indicate that Non Primary Channel Access is disabled. NON_PRIMARY_CHANNEL_ACCESS For example, a STA or AP may set the TXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS to NPCA_ENABLED to indicate that Non Primary Channel Access is enabled. In other words, if a STA or AP sets the TXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS to NPCA_ENABLED, the STA or AP Or, the AP may enable Non Primary Channel Access. For example, Alternatively, the AP may set the TXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS to NPCA_DISABLED to indicate that Non Primary Channel Access is disabled. If the AP sets the TXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS to NPCA_DISABLED, the STA or AP may disable Non Primary Channel Access. For example, a STA or AP may set the TXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS to NPCA_PROHIBIT to indicate that Non-Primary Channel Access is prohibited. If the STA or AP sets the TXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS to NPCA_PROHIBIT, When setting this, the STA or AP prohibits Non Primary Channel Access. For example, if the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of a received PPDU is set to NPCA_ENABLED, the STA or AP may determine that the STA or AP that sent the PPDU has Non Primary Channel Access enabled. For example, if the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of a received PPDU is set to NPCA_DISABLED, the STA or AP may determine that the STA or AP that sent the PPDU has Non Primary Channel Access disabled. For example, if NPCA_PROHIBIT is set in the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of a received PPDU, the STA or AP may determine that the STA or AP that transmitted the PPDU prohibits Non-Primary Channel Access. If the STA or AP does not perform Non-Primary Channel Access, the STA or AP may not include NON_PRIMARY_CHANNEL_ACCESS in the TXVECTOR parameter. If NON_PRIMARY_CHANNEL_ACCESS is not present in the RXVECTOR parameter of a received PPDU, the STA or AP may determine that the STA or AP that transmitted the PPDU does not perform Non-Primary Channel Access.

[0167] For example, in FIG. 1, 102 is the TXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS 102 may indicate that it has enabled Non Primary Channel Access when it transmits a PPDU with NPCA_ENABLED set in the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS. If so, 102 may determine that Non-primary Channel Access is enabled. 103 sets the TXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS to NPCA_ENABLED and transmits the PPDU. 102 may indicate that Non Primary Channel Access is enabled if the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the PPDU received from 103 is set to NPCA_ENABLED. 102 and 104 may determine that Non Primary Channel Access is enabled if 102 transmits a PPDU with the TXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS set to NPCA_DISABLED. 103 and 104 may indicate that the access is disabled. 102 may determine that Non-Primary Channel Access is disabled if the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the PPDU received from 103 is set to NPCA_DISABLED. 103 may indicate that Non-Primary Channel Access is disabled if 103 transmits a PPDU with TXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS set to NPCA_DISABLED. 102 and 104 may determine that Non-Primary Channel Access is disabled if 102 transmits a PPDU with RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS set to NPCA_DISABLED. 102 may indicate that Non-Primary Channel Access is prohibited if 102 transmits a PPDU with TXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS set to NPCA_PROHIBIT. 103 and 104 may determine that 102 prohibits non-primary channel access when NPCA_PROHIBIT is set in the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the PPDU received from 102. 103 may indicate that non-primary channel access is prohibited when transmitting a PPDU with NPCA_PROHIBIT set in the TXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS. 102 and 104 may determine that 103 prohibits non-primary channel access when NPCA_PROHIBIT is set in the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the PPDU received from 103.

[0168] A STA or AP receives a PPDU sent by a STA or AP belonging to another BSS, and The RXVECTOR parameter of NON_PRIMARY_CHANNEL_ACCESS (if present) from the PPDU transmission The Non Primary Channel Access setting of the original STA or AP may be determined. For example, see Figure 2. In this example, 204 may belong to a different BSS than 206 and 207. RXVECTOR parameter of PPDU received from 207 NON_PRIMARY_CHANNEL_ACCESS (if present) If NPCA_ENABLED is set in the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the PPDU received from 207, 204 determines that Non Primary Channel Access is enabled. 204 may determine the Non Primary Channel Access setting of 206 from the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS (if present) of the PPDU received from 206. If NPCA_PROHIBIT is set in the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the PPDU received from 207, 204 may determine that 207 prohibits Non Primary Channel Access. 202 determines the setting of Non Primary Channel Access of 207 from the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS (if it exists) of the PPDU received from 207. If NPCA_ENABLED is set in the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the PPDU received from 207, 202 determines whether NPCA_ENABLED is set in the Non Primary Channel 202 may determine that Non Primary Channel Access is valid. 202 may determine the setting of Non Primary Channel Access of 206 from the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS (if present) of the PPDU received from 206. 202 may determine that 207 prohibits Non Primary Channel Access if NPCA_PROHIBIT is set in the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the PPDU received from 207.

[0169] The STA or AP shall update its NAV only based on the conditions of Non-SRG OBSS PD level operation. In addition to the conditions for Non-SRG OBSS PD level operation, a STA or AP may not update its NAV when all or any of the following conditions are met: stomach. The STA or AP has not received an information element related to Non-Primary Channel Access from a non-associated AP, or the STA or AP has received an information element related to Non-Primary Channel Access from a non-associated AP. ·NPCA_ENABLED is set in the RXVECTOR parameter NON_PRIMARY_CHANNLE_ACCESS (if present) of the received PPDU.

[0170] The associated AP of an STA may be an AP that belongs to the same BSS. The associated AP of an STA may be an AP that is synchronized with the STA. For example, in FIG. 2, The associated AP of 204 may be 202. The associated AP of 207 may be 206. The non-associated AP of the STA may be an AP belonging to a different BSS. The non-associated AP of the STA may be an unsynchronized AP. For example, in FIG. 2, the non-associated AP of 204 is 206. The non-associated APs of 207 may be 202. The non-associated AP of 202 may be an AP of a different BSS. The non-associated AP of 206 may be 202. The non-associated AP of 206 may be 202. may be out-of-sync APs.

[0171] The STA may receive parameters for Non-Primary Channel Access and spatial reuse from the associated AP. The AP may transmit parameters for Non-Primary Channel Access and spatial reuse to the STA in the BSS. In other words, the STA and the AP may perform both Non-Primary Channel Access and spatial reuse. If both Non-Primary Channel Access and spatial reuse are configured by the associated AP, the STA may use the parameters. In this case, the STA may perform either Non-Primary Channel Access or Spatial reuse depending on the conditions. The AP sets both Non-Primary Channel Access and Spatial reuse for related STAs (synchronized STAs) in the BSS, and the AP may perform Non-Primary Channel Access depending on the conditions. The STA and AP may perform either Non-Primary Channel Access or Spatial Reuse when they receive a PPDU and update their NAV. The STA and AP may perform Spatial Reuse when they receive a PPDU and do not update their NAV.

[0172] The STA may receive an information element related to Non-Primary Channel Access in the wireless transceiver unit SU6. The STA may determine in the frame processing unit SU7 whether or not it has received an information element related to Non-Primary Channel Access from an AP belonging to a different BSS. If multiple conditions are met, the STA may not need to update its NAV. One of the multiple conditions is Alternatively, the condition may be that an information element regarding Non-Primary Channel Access has not been received from an AP belonging to a different BSS. The AP may receive the information element regarding Non-Primary Channel Access in the radio transceiver unit AU6. The AP may determine in the frame processing unit AU7 whether or not an information element regarding Non-Primary Channel Access has been received from an AP belonging to a different BSS. The AP may not need to update the NAV if multiple conditions are met. One of the multiple conditions may be that an information element regarding Non-Primary Channel Access has not been received from an AP belonging to a different BSS. The condition may be that no information element relating to Access has been received.

[0173] The STA may receive an information element related to Non-Primary Channel Access in the wireless transceiver unit SU6. The STA may determine in the frame processing unit SU7 whether or not it has received an information element related to Non-Primary Channel Access from an AP belonging to a different BSS. If multiple conditions are met, the STA may not need to update its NAV. One of the multiple conditions is Alternatively, the condition may be that the AP has received an information element related to Non-Primary Channel Access from an AP belonging to a different BSS. The AP may receive the information element related to Non-Primary Channel Access in the wireless transceiver unit AU6. The AP may receive the information element related to Non-Primary Channel Access in the frame processing unit AU7. In this case, the AP may determine whether it has received an information element related to Non-Primary Channel Access from an AP belonging to a different BSS. If multiple conditions are met, the AP does not update the NAV. One of the conditions is that the APs belonging to different BSSs are not allowed to send non-primary channel The condition may be that an information element relating to Access has been received.

[0174] The STA or AP may update the NAV if the Duration field of the received frame is greater than the current NAV value. The STA or AP may update the NAV if the Duration field of the received frame is greater than the current NAV value and if any one of the conditions is not met. In OBSS PD-based spatial reuse, a STA or AP may not update its NAV if the Duration field of a received frame is greater than the current NAV value and if multiple conditions are met. In OBSS PD-based spatial reuse, a STA or AP may not update its NAV if multiple conditions are met, even if the Duration field of the received frame is greater than the current NAV value. A STA or AP that receives at least one valid frame in a PSDU may update its NAV if the information in the valid Duration field in the PSDU is not met. The information may be used to update the NAV.

[0175] In non-SRG OBSS PD level operation, the STA and / or AP may determine whether to update the NAV by taking into account information related to non-primary channel access. The information related to non-primary channel access may be an information element related to non-primary channel access. For example, the information element related to non-primary channel access may be an NPCA operation element, a UHR operation element, etc. In non-SRG OBSS PD level operation, the PHY (physical layer) of the STA or AP may determine whether to update the NAV by taking into account information related to non-primary channel access. When receiving a PHY-CCA.indication(BUSY) followed by a PHY-RXEARLYSIG.indication or a PHY-RXSTART.indication, the MAC (MAC sublayer) of the STA or AP satisfies the first condition: The second condition, the third condition, the fourth condition, the fifth condition, the sixth condition, the seventh condition, and If all of the eighth condition is met, the STA may issue a PHY-CCARESET.request primitive before the end of the PPDU without updating the NAV timer based on the PPDU, or may treat the PPDU as not received for NAV timer purposes (without updating the NAV timer). The first condition is that the STA must be in a state where the TXVECTOR parameter SPATIAL REUSE is present and the STA is in a state where the current Beacon All PPDUs sent during this period and the previous Beacon period do not have the TXVECTOR parameter SPATIAL_REUSE set to the value PSR_AND_NON_SRG_OBSS_PD_PROHIBITED. , the Non-SRG OBSS PD SR Disallowed subfield of the latest Spatial Reuse Parameter Set element received from the associated AP is 0, or the Spatial Reuse Parameter Set element has not been received from the associated AP. A non-AP STA has not received a Spatial Reuse Parameter Set element, or the STA is an AP and the Non-SRG OBSS PD SR Disallowed subfield of the most recent Spatial Reuse Parameter Set element it transmitted is 0, or the STA is an AP and has not transmitted a Spatial Reuse Parameter Set element. The third condition is that the received PPDU is an inter-BSS PPDU and not a non-HT PPDU carrying a response frame, or If the received PPSU contains a CTS, the PHY-CCA.indication transition from BUSY to IDLE occurs within the PIFS immediately before the received CTS, and the transition is used for OBSS PD based spatial reuse. This corresponds to the end of an inter-BSS PPDU containing a discarded RTS frame. The fourth condition is that the STA is operating at the SRG OBSS PD level and the received PPDU is not an SRG PPDU, or the STA is not operating at the SRG OBSS PD level. The fifth condition is that the RXVECTOR parameter SPATIAL_REUSE (if present) of the received PPDU is not set to PSR_AND_NON_SRG_OBSS_PD_PROHIBITED. The sixth condition is that the received signal strength level, measured from the L-STF or L-LTF fields of the PPDU, or the PHY SYNC field, shortSYNC field, or Long PHY SYNC field (whichever is present and used to determine the PHY-CCA.indication), is below the non-SRG OBSS PD level. The seventh condition is that the (received) PPDU is not a non-HE PPDU carrying a frame whose RA field is equal to the STA MAC address, a non-HE PPDU carrying a Public Action frame, a non-HE PPDU carrying an NDP Announcement frame or a Fine Timing Measurement frame, or a non-HE NDP. The eighth condition may be that the STA or AP has not received an information element related to Non-Primary Channel Access from a non-associated AP. In other words, if the STA or AP has received an information element related to Non-Primary Channel Access from a non-associated AP, the eighth condition is not met and the NAV may be updated. If the eighth condition is not met, the STA or AP may update the NAV and perform Non-Primary Channel Access. If the STA does not receive any information element related to Non-Primary Channel Access from a non-associated AP, the eighth condition is met, and if any other condition is met, If all of the above are met, the NAV may not be updated. For example, the eighth condition may be combined with the second condition to form a single condition.

[0176] For example, "information element related to Non Primary Channel Access is received" "Not transmitting information element related to Non Primary Channel Access" may mean that a frame including an NPCA operation element has not been received. For example, "No information element related to Non Primary Channel Access has been received" can be , the NPCA operation element is received and the NPCA operation element indicates invalid. For example, "no information element related to Non Primary Channel Access is transmitted" may be a case where an NPCA operation element is transmitted and the NPCA operation element indicates invalid. For example, "no information element related to Non Primary Channel Access is received" may be a case where an information element related to Non Primary Channel Access is transmitted and the NPCA operation element indicates invalid. For example, "no information element related to Non Primary Channel Access is transmitted" may mean that a frame including a UHR operation element is not transmitted. For example, "no information element related to Non Primary Channel Access is received" may mean that a frame including a UHR operation element is not transmitted. and there is information related to Non Primary Channel Access in the UHR operation element The field indicating whether or not to transmit information related to Non Primary Channel Access may indicate that there is no information related to Non Primary Channel Access. For example, "No information element related to Non Primary Channel Access is transmitted" means that an NPCA operation element is transmitted, And there is information related to Non Primary Channel Access in the UHR operation element. Alternatively, the field indicating whether or not information related to Non Primary Channel Access is present may indicate that there is no information related to Non Primary Channel Access.

[0177] In non-SRG OBSS PD level operation, the STA and / or AP may determine whether to update the NAV by taking into account information related to non-primary channel access. The information related to non-primary channel access may be an RXVECTOR parameter related to non-primary channel access. For example, the RXVECTOR parameter may be NON_PRIMARY_CHANNEL_ACCESS. In non-SRG OBSS PD level operation, the PHY of the STA or AP may be When the physical layer issues a PHY-RXEARLYSIG.indication or a PHY-RXSTART.indication following a PHY-CCA.indication(BUSY) upon receiving a PPDU, the MAC (MAC sublayer) of the STA or AP shall check whether any of the following conditions are met: first, second, third, fourth, fifth, sixth, or If the seventh and eighth conditions are all met, the STA may issue a PHY-CCARESET.request primitive before the end of the PPDU without updating the NAV timer based on the PPDU, or may treat the PPDU as not received for NAV timer purposes (without updating the NAV timer). The second condition is that the Non-SRG OBSS PD SR Disallowed subfield of the Spatial Reuse Parameter Set element most recently received from the associated AP is 0, or the Spatial Reuse Parameter Set element has not been received from the associated AP. A non-AP STA that has not received a Reuse Parameter Set element, or a STA that is an AP and is sending The Non-SRG OBSS PD SR Disallowed subfield of the most recently received Spatial Reuse Parameter Set element is 0, or the STA is an AP and has sent a Spatial Reuse Parameter Set element. The third condition is that the received PPDU is an inter-BSS PPDU and not a non-HT PPDU carrying a response frame, or if the received PPDU contains a CTS, the If a PHY-CCA.indication transition from BUSY to IDLE occurs within the PIFS of the BSS, and the transition corresponds to the end of an inter-BSS PPDU containing an RTS frame that has been discarded according to the BSS PD based spatial reuse. The fourth condition is that the STA is operating at the SRG OBSS PD level and the received PPDU is not an SRG PPDU, or the STA is not operating at the SRG OBSS PD level. The fifth condition is that the RXVECTOR parameter SPATIAL_REUSE (if present) of the received PPDU is not set to PSR_AND_NON_SRG_OBSS_PD_PROHIBITED. The sixth condition is that the received PPDU has a SPATIAL_REUSE value measured from the L-STF or L-LTF fields of the PPDU, or the PHY SYNC, shortSYNC, or Long PHY SYNC fields (whichever is present and used to determine the PHY-CCA.indication). The signal strength level is below the non-SRG OBSS PD level. ) PPDU is a non-HE PPDU carrying a frame with the RA field equal to the STA MAC address, Public The eighth condition is that the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS (if present) is set to NPCA_ENABLED. In other words, the eighth condition is that the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the received PPDU is set to NPCA_PROHIBIT or NPCA_DISABLED. If the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS is present in the received PPDU, If the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the received PPDU is set to NPCA_ENABLED, the eighth condition is not met and the NAV may be updated. If the eighth condition is not met, the STA or AP may update the NAV and perform Non Primary Channel Access. If the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the received PPDU is set to NPCA_PROHIBIT or NPCA_DISABLED, or if the received PPDU If the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS does not exist, the eighth condition is met. If the above conditions are met and all other conditions are satisfied, the NAV may not be updated. The condition may be configured together with other conditions to form a single condition. For example, the eighth condition may be configured together with the sixth condition to form a single condition. The PPDU related to the eighth condition may be any PPDU. The PPDU related to the eighth condition may be any PPDU received from a STA or AP belonging to the same BSS as the STA or AP. The PPDU related to the eighth condition may be any PPDU received from a STA or AP belonging to a different BSS (OBSS) from the STA or AP. The PPDU related to the eighth condition may be the same PPDU as the third condition and / or the fifth condition. The PPDU related to the eighth condition may be a PPDU different from the third condition and / or the fifth condition.

[0178] In the Non-SRG OBSS PD level operation, the STA and / or AP may determine whether to update the NAV by taking into account information related to Non-Primary Channel Access. The information related to Non-Primary Channel Access may be an information element related to Non-Primary Channel Access and an RXVECTOR parameter related to Non-Primary Channel Access. For example, the information element related to Non-Primary Channel Access is , NPCA operation element, UHR operation element, etc. For example, an RXVECTOR parameter related to Non-Primary Channel Access may be the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS, etc. In Non-SRG OBSS PD level operation, when the PHY (physical layer) of a STA or AP issues a PHY-RXEARLYSIG.indication or a PHY-RXSTART.indication following a PHY-CCA.indication(BUSY) upon receiving a PPDU, the MAC (MAC sublayer) of the STA or AP may issue a PHY-CCARESET.request primitive before the end of the PPDU without updating the NAV timer based on the PPDU if all of the first, second, third, fourth, fifth, sixth, seventh, eighth, and ninth conditions are met, or may consider the PPDU as not having been received for purposes of the NAV timer. The first condition is that the STA must have the TXVECTOR parameter SPATIAL REUSE and must have the same NAV timer as the current Beacon period and the previous Beacon period. The STA does not set the TXVECTOR parameter SPATIAL_REUSE to the value PSR_AND_NON_SRG_OBSS_PD_PROHIBITED in any transmitted PPDU. The second condition is that the Non-SRG OBSS PD SR Disallowed subfield of the most recent Spatial Reuse Parameter Set element received from the associated AP is 0, or the STA is a non-AP STA that has not received a Spatial Reuse Parameter Set element from the associated AP, or the STA is an AP and the Non-SRG OBSS PD SR Disallowed subfield of the most recent Spatial Reuse Parameter Set element it transmitted is 0, or the STA is an AP and has not transmitted a Spatial Reuse Parameter Set element. The third condition is that the received PPDU is an inter-BSS PPDU. If the received PPDU is not a non-HT PPDU carrying a response frame, or if the received PPDU contains a CTS, the PHY-CCA.indication transition from BUSY to IDLE must occur within the PIFS time immediately preceding the received CTS. The transition includes RTS frames that are discarded according to OBSS PD based spatial reuse. The fourth condition is that the STA is operating at the SRG OBSS PD level and the received PPDU is not an SRG PPDU, or the STA is not operating at the SRG OBSS PD level. The fifth condition is that the RXVECTOR parameter SPATIAL_REUSE (if present) in the received PPDU is The sixth condition is that the PPDU L-STF or L-LTF field of the PHY, or PHY SYNC field, shortSYNC field, or or Long PHY SYNC field (whichever is present) to determine the PHY-CCA.indication. The received signal strength level measured from the STA (used in the OBSS PD level) is below the non-SRG OBSS PD level. The seventh condition is that the (received) PPDU is a frame with the RA field equal to the STA MAC address. a non-HE PPDU carrying a Public Action frame, a non-HE PPDU carrying an NDP Announcement frame or a Fine Timing Measurement frame, or a non-HE NDP The eighth condition is that the STA does not receive information elements related to Non-Primary Channel Access from a non-associated AP, or the STA that is an AP does not transmit information elements related to Non-Primary Channel Access. In other words, if a STA receives an information element related to Non-Primary Channel Access from a non-associated AP, or if a STA that is an AP transmits an information element related to Non-Primary Channel Access, then Article 8 If the eighth condition is not met, the STA or AP may update the NAV and perform Non Primary Channel Access. For example, the eighth condition may be configured together with the second condition to form a single condition. The ninth condition is when the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS (if present) is not set to NPCA_ENABLED. That is, the ninth condition is when the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the received PPDU is set to NPCA_PROHIBIT or NPCA_DISABLED, or when the If the received PPDU does not have the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS, If the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the received PPDU is set to NPCA_ENABLED, the ninth condition is not met, so the NAV may be updated. If the ninth condition is not met, the AP updates the NAV and performs Non-Primary Channel Access. If the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS in the received PPDU is set to NPCA_PROHIBIT or NPCA_DISABLED, or if the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS is not present in the received PPDU, the NAV may not be updated if the ninth condition is met and all other conditions are met. For example, the ninth condition may be configured as one condition in combination with the sixth condition. The PPDU related to the ninth condition may be any PPDU. The PPDU related to the ninth condition may be any PPDU received from a STA or AP that belongs to the same BSS as itself. The PPDU related to the ninth condition may be any PPDU received from a STA or AP that belongs to a BSS different from itself (OBSS). ) or any PPDU received from an AP. The PPDU related to the ninth condition may be the same PPDU as the third condition and / or the fifth condition. The PPDU related to the ninth condition may be a different PPDU from the third condition and / or the fifth condition.

[0179] In non-SRG OBSS PD level operation, the STA and / or AP may determine whether to update the NAV by taking into account information related to non-primary channel access. The information related to non-primary channel access may be an information element related to non-primary channel access. For example, the information element related to non-primary channel access may be an NPCA operation element, a UHR operation element, etc. In non-SRG OBSS PD level operation, the PHY (physical layer) of the STA or AP may determine whether to update the NAV by taking into account information related to non-primary channel access. When receiving a PHY-CCA.indication(BUSY) followed by a PHY-RXEARLYSIG.indication or a PHY-RXSTART.indication, the MAC (MAC sublayer) of the STA or AP satisfies the first condition: The second condition, the third condition, the fourth condition, the fifth condition, the sixth condition, the seventh condition, and If all of the eighth condition is met, the STA may issue a PHY-CCARESET.request primitive before the end of the PPDU without updating the NAV timer based on the PPDU, or may treat the PPDU as not received for NAV timer purposes (without updating the NAV timer). The first condition is that the STA must be in a state where the TXVECTOR parameter SPATIAL REUSE is present and the STA is in a state where the current Beacon All PPDUs sent during this period and the previous Beacon period do not have the TXVECTOR parameter SPATIAL_REUSE set to the value PSR_AND_NON_SRG_OBSS_PD_PROHIBITED. , the Non-SRG OBSS PD SR Disallowed subfield of the latest Spatial Reuse Parameter Set element received from the associated AP is 0, or the Spatial Reuse Parameter Set element has not been received from the associated AP. A non-AP STA has not received a Spatial Reuse Parameter Set element, or the STA is an AP and the Non-SRG OBSS PD SR Disallowed subfield of the most recent Spatial Reuse Parameter Set element it transmitted is 0, or the STA is an AP and has not transmitted a Spatial Reuse Parameter Set element. The third condition is that the received PPDU is an inter-BSS PPDU and not a non-HT PPDU carrying a response frame, or If the received PPSU contains a CTS, the PHY-CCA.indication transition from BUSY to IDLE occurs within the PIFS immediately before the received CTS, and the transition is used for OBSS PD based spatial reuse. This corresponds to the end of an inter-BSS PPDU containing a discarded RTS frame. The fourth condition is that the STA is operating at the SRG OBSS PD level and the received PPDU is not an SRG PPDU, or the STA is not operating at the SRG OBSS PD level. The fifth condition is that the RXVECTOR parameter SPATIAL_REUSE (if present) of the received PPDU is not set to PSR_AND_NON_SRG_OBSS_PD_PROHIBITED. The sixth condition is that the received signal strength level, measured from the L-STF or L-LTF fields of the PPDU, or the PHY SYNC field, shortSYNC field, or Long PHY SYNC field (whichever is present and used to determine the PHY-CCA.indication), is below the non-SRG OBSS PD level. The seventh condition is that the (received) PPDU is not a non-HE PPDU carrying a frame whose RA field is equal to the STA MAC address, a non-HE PPDU carrying a Public Action frame, a non-HE PPDU carrying an NDP Announcement frame or a Fine Timing Measurement frame, or a non-HE NDP. The eighth condition may be that the STA or AP receives an information element related to Non-Primary Channel Access from a non-associated AP. In other words, if the STA or AP does not receive an information element related to Non-Primary Channel Access from a non-associated AP, the eighth condition is not met, and the NAV may be updated. If the eighth condition is not met, the STA or AP may update the NAV and perform Non-Primary Channel Access. If the STA receives an information element related to Non-Primary Channel Access from a non-associated AP, the eighth condition is met, and other conditions are met. If all conditions are met, the NAV may not be updated. For example, the eighth condition may be configured as one condition together with the second condition.

[0180] For example, "information element related to Non Primary Channel Access is received" "Having received an information element related to Non Primary Channel Access" may be a case where a frame including an NPCA operation element is being received. "Having transmitted an information element related to Non Primary Channel Access" may be a case where a frame including an NPCA operation element is being transmitted. For example, "Having received an information element related to Non Primary Channel Access" may be a case where an NPCA operation element is received and the NPCA operation element indicates that it is valid. For example, "Has received an information element related to Non Primary Channel Access" may mean that an NPCA operation element has been transmitted and the NPCA operation element indicates that it is valid. For example, "Has received an information element related to Non Primary Channel Access" may mean that a frame including a UHR operation element has been received. For example, "Has transmitted an information element related to Non Primary Channel Access" may mean that a frame including a UHR operation element has been transmitted. For example, "Has received an information element related to Non Primary Channel Access" may mean that a UHR operation element has been received and that the field indicating whether or not information related to Non Primary Channel Access exists in the UHR operation element indicates that information related to Non Primary Channel Access exists. For example, "Sending" means sending an NPCA operation element and Alternatively, the field indicating whether or not information related to Non Primary Channel Access exists may indicate that information related to Non Primary Channel Access exists.

[0181] In the Non-SRG OBSS PD level operation, the STA and / or AP may determine whether to update the NAV by taking into account information related to Non-Primary Channel Access. The information related to Non-Primary Channel Access may be an information element related to Non-Primary Channel Access and an RXVECTOR parameter related to Non-Primary Channel Access. For example, the information element related to Non-Primary Channel Access is , NPCA operation element, UHR operation element, etc. For example, Non P The RXVECTOR parameter related to Primary Channel Access may be the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS, etc. In Non-SRG OBSS PD level operation, when the PHY (physical layer) of a STA or AP issues a PHY-RXEARLYSIG.indication or a PHY-RXSTART.indication following a PHY-CCA.indication(BUSY) upon receiving a PPDU, the MAC (MAC sublayer) of the STA or AP may issue a PHY-CCARESET.request primitive before the end of the PPDU without updating the NAV timer based on that PPDU if all of the first, second, third, fourth, fifth, sixth, seventh, eighth, and ninth conditions are met, or may consider the PPDU as not having been received for purposes of the NAV timer. The first condition is that the STA must have the TXVECTOR parameter SPATIAL REUSE and must have the same NAV timer as the current Beacon period and the previous Beacon period. The STA does not set the TXVECTOR parameter SPATIAL_REUSE to the value PSR_AND_NON_SRG_OBSS_PD_PROHIBITED in any transmitted PPDU. The second condition is that the Non-SRG OBSS PD SR Disallowed subfield of the most recent Spatial Reuse Parameter Set element received from the associated AP is 0, or the STA is a non-AP STA that has not received a Spatial Reuse Parameter Set element from the associated AP, or the STA is an AP and the Non-SRG OBSS PD SR Disallowed subfield of the most recent Spatial Reuse Parameter Set element it transmitted is 0, or the STA is an AP and has not transmitted a Spatial Reuse Parameter Set element. The third condition is that the received PPDU is an inter-BSS PPDU. If the received PPDU is not a non-HT PPDU carrying a response frame, or if the received PPDU contains a CTS, the PHY-CCA.indication transition from BUSY to IDLE must occur within the PIFS time immediately preceding the received CTS. The transition includes RTS frames that are discarded according to OBSS PD based spatial reuse. The fourth condition is that the STA is operating at the SRG OBSS PD level and the received PPDU is not an SRG PPDU, or the STA is not operating at the SRG OBSS PD level. The fifth condition is that the RXVECTOR parameter SPATIAL_REUSE (if present) in the received PPDU is The sixth condition is that the PPDU L-STF or L-LTF field of the PHY, or PHY SYNC field, shortSYNC field, or or Long PHY SYNC field (whichever is present) to determine the PHY-CCA.indication. The received signal strength level measured from the STA (used in the OBSS PD level) is below the non-SRG OBSS PD level. The seventh condition is that the (received) PPDU is a frame with the RA field equal to the STA MAC address. a non-HE PPDU carrying a Public Action frame, a non-HE PPDU carrying an NDP Announcement frame or a Fine Timing Measurement frame, or a non-HE NDP The eighth condition may be that the STA receives an information element related to Non-Primary Channel Access from a non-associated AP. That is, if the STA does not receive an information element related to Non-Primary Channel Access from a non-associated AP, the eighth condition is not met and the NAV may be updated. If the eighth condition is not met, the STA or AP may update the NAV and perform Non-Primary Channel Access. The eighth condition may be configured as one condition together with another condition. For example, the eighth condition may be configured as one condition together with the second condition. The ninth condition is configured as one condition by combining the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS( In other words, the ninth condition may be when the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the received PPDU is set to NPCA_PROHIBIT or NPCA_DISABLED, or when the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS is not present in the received PPDU. If NPCA_ENABLED is set in the parameter NON_PRIMARY_CHANNEL_ACCESS, the ninth condition applies. If the 9th condition is not met, the STA or AP may update the NAV and perform Non-Primary Channel Access. If the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the received PPDU is set to NPCA_PROHIBIT or NPCA_DISABLED, or if the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the received PPDU is set to NPCA_PROHIBIT or NPCA_DISABLED, the STA or AP may update the NAV and perform Non-Primary Channel Access. If there is no ninth condition, then the NAV is The ninth condition may be configured as a single condition in combination with other conditions. For example, the ninth condition may be configured as a single condition in combination with the sixth condition. The PPDU related to the ninth condition may be any PPDU. The PPDU related to the ninth condition may be any PPDU received from a STA or AP belonging to the same BSS as the ninth condition. The PPDU related to the ninth condition may be any PPDU received from a STA or AP belonging to a different BSS (OBSS) from the ninth condition. The PPDU related to the ninth condition may be the same PPDU as the 3rd condition and / or the 5th condition. The PPDU related to the ninth condition may be a PPDU different from the 3rd condition and / or the 5th condition.

[0182] A STA or AP shall not update its NAV solely based on the condition of SRG OBSS PD level operation. In addition to the conditions for SRG OBSS PD level operation, a STA or AP may not update its NAV when all and / or any of the following conditions are met: stomach. The STA or AP has not received an information element related to Non-Primary Channel Access from a non-associated AP, or the STA or AP has received an information element related to Non-Primary Channel Access from a non-associated AP. ·NPCA_ENABLED is set in the RXVECTOR parameter NON_PRIMARY_CHANNLE_ACCESS (if present) of the received PPDU.

[0183] In SRG OBSS PD level operation, the STA and / or AP may decide whether to update the NAV by taking into account information related to Non-Primary Channel Access. The information related to Non-Primary Channel Access may be an information element related to Non-Primary Channel Access. For example, the information element related to Non-Primary Channel Access may be an NPCA operation element, a UHR operation element, etc. In SRG OBSS PD level operation, the PHY (physical layer) of the STA or AP determines whether to update the NAV by receiving a PPDU. If a STA or AP issues a PHY-RXEARLYSIG.indication or a PHY-RXSTART.indication following a PHY-CCA.indication(BUSY), the MAC (MAC sublayer) of the STA or AP shall satisfy the first condition, the second condition, and If all three of the above conditions are met, it is acceptable to issue a PHY-CCARESET.request primitive before the end of the PPDU without updating the NAV timer based on that PPDU. or the PPDU may be treated as not received for purposes of the NAV timer. (The NAV timer is not updated.) The first condition is that the received PPDU is an SRG PPDU. The second condition is that The condition is the L-STF or L-LTF field of the PPDU, or the PHY SYNC field, shortSYNC field. field, or Long PHY SYNC field (whichever is present) determines the PHY-CCA.indication. The received signal strength level measured from the STA (used to determine the STA MAC address) is below the SRG OBSS PD level. The third condition is that the (received) PPDU has an RA field equal to the STA MAC address. The fourth condition is that the STA is not receiving a Non-HE PPDU from a non-associated AP. In other words, if the STA receives an information element related to Non-Primary Channel Access from a non-associated AP, the fourth condition is not met and the NAV may be updated. If the fourth condition is not met, the STA or AP may update the NAV and perform Non-Primary Channel Access. If the STA does not receive an information element related to Non-Primary Channel Access from a non-associated AP, If the fourth condition is met, and all other conditions are met, the NAV is updated. The fourth condition may not necessarily be set. The fourth condition may be configured as a single condition in combination with other conditions. For example, the fourth condition may be configured as a single condition in combination with the first condition.

[0184] In the SRG OBSS PD level operation, the STA and / or AP may determine whether to update the NAV by taking into account information related to Non-Primary Channel Access. The information related to Non-Primary Channel Access may be determined by the RXVECTOR associated with Non-Primary Channel Access. For example, it may be the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS. In SRG OBSS PD level operation, the PHY (physical layer) of the STA or AP ) indicates that the PHY-CCA.indication(BUSY) is followed by the PHY-RXEARLYSIG.indication upon receiving a PPDU. When issuing a PHY-RXSTART.indication, the MAC (MAC sublayer) of the STA or AP may issue a PHY-CCARESET.request primitive before the end of the PPDU without updating the NAV timer based on the PPDU if all of the first, second, third, and fourth conditions are met, or may treat the PPDU as not received for NAV timer purposes (without updating the NAV timer). The first condition is that the received PPDU is an SRG PPDU. The second condition is that the L-STF or L-LTF field of the PPDU, or the PHY SYNC field, The received signal strength level measured from the PHY-CCA.indication, shortSYNC field, or Long PHY SYNC field (whichever is present and used to determine the PHY-CCA.indication) is below the SRG OBSS PD level. The third condition is that the (received) PPDU is not a non-HE PPDU carrying a frame with the RA field equal to the STA MAC address, a non-HE PPDU carrying a Public Action frame, a non-HE PPDU carrying an NDP Announcement frame or a Fine Timing Measurement frame, or a non-HE NDP. The fourth condition may be that the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS (if present) is not set to NPCA_ENABLED. The fourth condition is that the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the received PPDU is This may occur if NPCA_PROHIBIT or NPCA_DISABLED is set in PPDU_ID or if the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS is not present in the received PPDU. NPCA_ENABLED is set in the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the PPDU. If the fourth condition is not met, the NAV may be updated. If the fourth condition is not met, the STA or AP may update the NAV and perform Non Primary Channel Access. If the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS in the received PPDU is set to NPCA_PROHIBIT or NPCA_DISABLED, or if the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS is not present in the received PPDU, the NAV may not be updated if the fourth condition is met and all other conditions are met. The fourth condition is combined with the other conditions to form a single The fourth condition may be configured as a condition. For example, the fourth condition may be configured as a single condition in accordance with the first condition. The PPDU related to the fourth condition may be any PPDU. The PPDU related to the fourth condition may be any PPDU received from a STA or AP belonging to the same BSS as the PPDU itself. The PPDU related to the fourth condition may be any PPDU received from a STA or AP belonging to a different BSS (OBSS) from the PPDU itself. The PPDU related to the fourth condition may be the same PPDU as the PPDU related to the first condition. The PPDU related to the fourth condition may be a different PPDU from the PPDU related to the first condition.

[0185] In SRG OBSS PD level operation, the STA and / or AP may determine whether to update the NAV by taking into account information related to Non-Primary Channel Access. The information related to Non-Primary Channel Access may be an information element related to Non-Primary Channel Access and an RXVECTOR parameter related to Non-Primary Channel Access. For example, the information element related to Non-Primary Channel Access may be an NPCA operation element, a UHR operation element, etc. For example, the RXVECTOR parameter related to Non-Primary Channel Access may be the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS, etc. In SRG OBSS PD level operation, when the PHY (physical layer) of the STA or AP issues a PHY-RXEARLYSIG.indication or a PHY-RXSTART.indication following a PHY-CCA.indication(BUSY) upon receiving a PPDU, the MAC (MAC sublayer) of the STA or AP may determine whether to update the NAV by taking into account the first, second, third, fourth, and fifth conditions. If all of the above conditions are met, the NAV timer is not updated based on the PPDU, and the The PHY-CCARESET.request primitive may be issued before the NAV timer For purposes of the first The first condition is that the received PPDU is an SRG PPDU. The second condition is that the L-STF or L-LTF field of the PPDU, or the PHY SYNC field, short SYNC field, or Long PHY SYNC field The received signal strength level, as measured from the PHY-CCA.indication field (if any) is below the SRG OBSS PD level. ) PPDU is a non-HE PPDU carrying a frame with the RA field equal to the STA MAC address, Public The STA does not receive any of the following: a non-HE PPDU carrying an Action frame, a non-HE PPDU carrying an NDP Announcement frame or a Fine Timing Measurement frame, or a non-HE NDP. The fourth condition may be that the STA does not receive an information element related to Non-Primary Channel Access from a non-associated AP. In other words, if the STA receives an information element related to Non-Primary Channel Access from a non-associated AP, the fourth condition is not met and the NAV may be updated. If the fourth condition is not met, the STA or AP may update the NAV and continue to use the Non-Primary Channel Access even if the STA performs Non-Primary Channel Access. The fourth condition may be configured together with other conditions to form a single condition. For example, the fourth condition may be configured together with the first condition to form a single condition. The fifth condition is when the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS (if present) is set to NPCA_ENABLED. In other words, the fifth condition is that NPCA_PROHIBIT or NPCA_DISABLED is set in the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the received PPDU. or if the received PPDU has the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS. It may not exist. If the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the received PPDU is set to NPCA_ENABLED, the fifth condition is not met and the NAV may be updated. If the fifth condition is not met, the STA or AP may update the NAV and perform Non Primary Channel Access. If the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the received PPDU is set to NPCA_PROHIBIT or NPCA_DISABLED, or if the received If the received PPDU does not have the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS, If the condition is met and all other conditions are met, the NAV may not be updated. The fifth condition may be configured together with other conditions to form one condition. For example, the fifth condition may be configured together with the first condition to form one condition. The PPDU related to the fifth condition may be any PPDU. The PPDU related to the fifth condition may be a PPDU that is in the same BSS as itself. The PPDU related to the fifth condition may be any PPDU received from a STA or AP belonging to a BSS (OBSS) different from the own PPDU. The PPDU related to the fifth condition may be the same PPDU as the PPDU related to the first condition, or may be a different PPDU from the PPDU related to the first condition.

[0186] In SRG OBSS PD level operation, the STA and / or AP may decide whether to update the NAV by taking into account information related to Non-Primary Channel Access. The information related to Non-Primary Channel Access may be an information element related to Non-Primary Channel Access. For example, the information element related to Non-Primary Channel Access may be an NPCA operation element, a UHR operation element, etc. In SRG OBSS PD level operation, the PHY (physical layer) of the STA or AP determines whether to update the NAV by receiving a PPDU. If a STA or AP issues a PHY-RXEARLYSIG.indication or a PHY-RXSTART.indication following a PHY-CCA.indication(BUSY), the MAC (MAC sublayer) of the STA or AP shall satisfy the first condition, the second condition, and If all three of the above conditions are met, it is acceptable to issue a PHY-CCARESET.request primitive before the end of the PPDU without updating the NAV timer based on that PPDU. or the PPDU may be treated as not received for purposes of the NAV timer. (The NAV timer is not updated.) The first condition is that the received PPDU is an SRG PPDU. The second condition is that The condition is the L-STF or L-LTF field of the PPDU, or the PHY SYNC field, shortSYNC field. field, or Long PHY SYNC field (whichever is present) determines the PHY-CCA.indication. The received signal strength level measured from the STA (used to determine the STA MAC address) is below the SRG OBSS PD level. The third condition is that the (received) PPDU has an RA field equal to the STA MAC address. The fourth condition is that the STA is not receiving a Non-HE PPDU from a non-associated AP. In other words, if the STA does not receive an information element related to Non-Primary Channel Access from a non-associated AP, the fourth condition is not met and the NAV may be updated. If the fourth condition is not met, the STA or AP may update the NAV and perform Non-Primary Channel Access. If the STA receives an information element related to Non-Primary Channel Access from a non-associated AP, the fourth condition is not met. If this condition is met and all other conditions are met, the NAV will not be updated. The fourth condition may be configured as one condition in combination with another condition. For example, the fourth condition may be configured as one condition in combination with the first condition.

[0187] In SRG OBSS PD level operation, the STA and / or AP may determine whether to update the NAV by taking into account information related to Non-Primary Channel Access. The information related to Non-Primary Channel Access may be an information element related to Non-Primary Channel Access and an RXVECTOR parameter related to Non-Primary Channel Access. For example, the information element related to Non-Primary Channel Access may be an NPCA operation element, a UHR operation element, etc. For example, the RXVECTOR parameter related to Non-Primary Channel Access may be the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS, etc. In SRG OBSS PD level operation, when the PHY (physical layer) of the STA or AP issues a PHY-RXEARLYSIG.indication or a PHY-RXSTART.indication following a PHY-CCA.indication(BUSY) upon receiving a PPDU, the MAC (MAC sublayer) of the STA or AP may determine whether to update the NAV by taking into account the first, second, third, fourth, and fifth conditions. If all of the above conditions are met, the NAV timer is not updated based on the PPDU, and the The PHY-CCARESET.request primitive may be issued before the NAV timer For purposes of the first The first condition is that the received PPDU is an SRG PPDU. The second condition is that the L-STF or L-LTF field of the PPDU, or the PHY SYNC field, short SYNC field, or Long PHY SYNC field The received signal strength level, as measured from the PHY-CCA.indication field (if any) is below the SRG OBSS PD level. ) PPDU is a non-HE PPDU carrying a frame with the RA field equal to the STA MAC address, Public The STA does not have a non-HE PPDU carrying an Action frame, a non-HE PPDU carrying an NDP Announcement frame or a Fine Timing Measurement frame, or a non-HE NDP. The fourth condition may be that the STA receives an information element related to Non-Primary Channel Access from a non-associated AP. In other words, if the STA does not receive an information element related to Non-Primary Channel Access from a non-associated AP, the fourth condition is not met and the NAV may be updated. If the fourth condition is not met, the STA or AP may update the NAV and determine whether or not the STA is performing Non-Primary Channel Access. The fourth condition may be configured together with other conditions to form a single condition. For example, the fourth condition may be configured together with the first condition to form a single condition. The fifth condition is when the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS (if present) is set to NPCA_ENABLED. In other words, the fifth condition is that NPCA_PROHIBIT or NPCA_DISABLED is set in the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the received PPDU. or if the received PPDU has the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS. It may not exist. If the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the received PPDU is set to NPCA_ENABLED, the fifth condition is not met and the NAV may be updated. If the fifth condition is not met, the STA or AP may update the NAV and perform Non Primary Channel Access. If the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS of the received PPDU is set to NPCA_PROHIBIT or NPCA_DISABLED, or if the received If the received PPDU does not have the RXVECTOR parameter NON_PRIMARY_CHANNEL_ACCESS, If the condition is met and all other conditions are met, the NAV may not be updated. The fifth condition may be combined with other conditions to form one condition. For example, The condition may be configured as one condition in accordance with the first condition. The PPDU related to the fifth condition may be any PPDU. The PPDU related to the fifth condition may be any PPDU that is in the same BSS as itself. The PPDU related to the fifth condition may be any PPDU received from a STA or AP belonging to a BSS (OBSS) different from the own PPDU. The PPDU related to the fifth condition may be the same PPDU as the PPDU related to the first condition, or may be a different PPDU from the PPDU related to the first condition.

[0188] FIG. 14 is a diagram illustrating an example of a process related to a NAV update according to an aspect of this embodiment. The STA or AP receives a PPDU (S1401). The STA or AP receives a plurality of PPDUs related to a NAV update. The STA or AP determines whether the above conditions are met (S1402). If it is determined that the conditions related to the NAV update are not met (S1402: NO), the STA or AP updates the NAV (S1403). If so (S1402: YES), the STA or AP does not update the NAV (S1403).

[0189] As described above, in the embodiment of the present invention, when determining whether to update the NAV, the STA or AP considers the Non Primary Channel Access transmitted from the AP belonging to a different BSS. According to the present invention, the STA and / or AP may use information that belongs to different BSSs. The NAV update condition is the information related to Non Primary Channel Access sent from the AP. If multiple conditions are met, the NAV is not updated. If even one of the conditions is met, the NAV is not updated. If not, update the NAV.

[0190] The base station device and the program operating in the terminal device according to the embodiment of the present invention may be a program (a program that makes a computer function) that controls a CPU (Central Processing Unit) or the like so as to realize the functions of the above-described embodiment of the present invention. Information handled by these devices is temporarily stored in RAM (Random Access Memory) during processing. The data is then stored in various ROMs such as Flash ROM (Read Only Memory) or HDD (Hard Disk Drive), and is read, modified, and written by the CPU as needed. can be.

[0191] Note that the terminal device and part of the base station device in the above-described embodiments may be realized by a computer, in which case a program for realizing the control function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read by a computer system and executed.

[0192] 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 an OS and peripheral devices. Also, the term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, CD-ROMs, and hard disks built into a computer system. This refers to a storage device.

[0193] Furthermore, the term "computer-readable recording medium" may include a medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, or a medium that stores a program for a certain period of time, such as a volatile memory within a computer system that serves as a server or client in such a case. The program may also be one that realizes part of the above-mentioned functions, or one that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

[0194] The terminal device may comprise 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 use a processor to cause the terminal device to perform the operations and processes described in the above embodiments. The base station device may include 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 use a processor to cause the base station device to perform the operations and processes described in the above embodiments.

[0195] Furthermore, the base station device in the above-described embodiments can also be realized as a collection (device group) consisting of multiple devices. Each of the devices constituting the device group may have some or all of the functions or functional blocks of the base station device according to the above-described embodiments. The device group may have all of the functions or functional blocks of the base station device. Furthermore, the terminal devices according to the above-described embodiments can also communicate with the base station device as a collection.

[0196] Furthermore, the terminal device and the base station device in the above-described embodiments may be implemented in part or in whole as an LSI, which is typically an integrated circuit, or as a chipset. Each functional block of the equipment and base station equipment may be individually integrated into a chip, or part or all of them may be integrated into a chip. The integrated circuit method is not limited to LSI, but may be a dedicated circuit or a general-purpose circuit. It may be realized by a processor. Also, with the advancement of semiconductor technology, integrated circuits will replace LSI. When such technology emerges, it may be possible to use integrated circuits based on that technology.

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

[0198] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the invention. Furthermore, the present invention is susceptible to various modifications 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 the present invention. Furthermore, configurations in which elements described in the above embodiments are substituted with elements that achieve the same effect are also included. [Explanation of symbols]

[0199] SU1, AU1 antenna section SU2, AU2 RF section SU3, AU3 physical layer processing section SU4, AU4 MAC layer processing section SU5 Upper layer packet processing unit SU6, AU6 radio transceiver SU7, AU7 frame processing section AU5 DSAF section

Claims

1. A receiver that receives information elements related to Non-Primary Channel Access and a different a control unit that determines whether an information element related to Non Primary Channel Access has been received from an AP that belongs to the BSS, and if a plurality of conditions are met, the NAV is not updated; A terminal device in which one of the plurality of conditions is a condition that an information element related to Non Primary Channel Access is not received from an AP belonging to the different BSS.

2. The Duration field of the received frame is greater than the current NAV value, and 2. The terminal device according to claim 1, wherein the NAV is updated if any one of the conditions is not met. terminal equipment.

3. The Duration field of the received frame is greater than the current NAV value, and The terminal device according to claim 1, wherein the NAV is not updated if the number of conditions is met.

4. A receiver that receives information elements related to Non-Primary Channel Access and a different a control unit that determines whether an information element related to Non Primary Channel Access has been received from an AP that belongs to the BSS, and if a plurality of conditions are met, the NAV is not updated; A base station device, wherein one of the plurality of conditions is a condition that an information element related to Non Primary Channel Access is not received from an AP belonging to the different BSS.

5. receiving an information element regarding Non Primary Channel Access; and determining whether an information element relating to Non-Primary Channel Access has been received from an AP belonging to a different BSS, and if a plurality of conditions are met, updating of the NAV is not performed. First, one of the plurality of conditions is that the APs belonging to the different BSSs are not receiving Non Primary Channel A communication method under the condition that no information element related to Access has been received.

Images