Base station device, terminal device, and communication method

Abstract

A base station device, a terminal device, and a communication method are provided that realize efficient communication in a LAN-less system that performs non-primary channel access (NPCA). [Solution] In NPCA, an access point (AP) requests a Trigger Based PHY Protocol Data Unit (TB PPDU) from a station (STA), receives the requested TB PPDU from the STA on the NPCA primary channel, and the AP's PHY (physical layer) issues a PHY-RXSTART.indication primitive.

Description

[Technical Field]

[0001] The present invention relates to a base station device, a terminal 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, is underway (see Non-Patent Document 1). ). [Prior art documents] [Non-patent literature]

[0003] IEEE802.11-23 / 2005r0, Intel Corp, “Non-primary channel access (NPCA)”, November 2023. Summary of the Invention [Problem to be solved by the invention]

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

[0005] (1) A first aspect of the present invention is a base station device, which includes a processing unit that issues a PHY-RXSTART.indication primitive, and when NPCA is being performed, the base station device issues a TB PPDU unless it is a TB PPDU requested by an AP. and the base station device issues the PHY-RXSTART.indication primitive for a PPDU that overlaps with the NPCA primary channel.

[0006] (2) A second aspect of the present invention is a communication method used in a base station device, comprising the step of issuing a PHY-RXSTART.indication primitive, and when NPCA is being performed, issuing the PHY-RXSTART.indication primitive for a PPDU that overlaps with the NPCA primary channel, unless it is a TB PPDU requested by the AP. [Effects of the Invention]

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

[0008] [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 one 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 PPDU reception on an NPCA primary channel according to one aspect of this embodiment. [Figure 15] FIG. 10 is a diagram illustrating an example of TB PPDU reception in an NPCA according to an aspect of this embodiment. [Figure 16] FIG. 10 is a diagram illustrating an example of a process for issuing a PHY-RXSTART.indication primitive according to one aspect of this embodiment. [Figure 17] FIG. 10 is a diagram illustrating an example of a process for issuing a PHY-RXSTART.indication primitive for a TB PPDU according to one aspect of this embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

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

[0011] The wireless LAN system in this embodiment includes an access point (AP) and a station. 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.

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

[0013] 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 STA 103, STA 104, and AP 102. may be referred to as a BSS.

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

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

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

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

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

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

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

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

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

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

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

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

[0026] An addressable unit may be a station (STA). Physical and operational Characteristics may be defined by a modifier placed before the STA term. 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.

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

[0028] 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 may be handled by the access entity. In this case, the frame may conceptually pass through the DS.

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

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

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

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

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

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

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

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

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

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

[0039] 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. The main MAC function of the VHT STA is to support A-MPDU padding of the VHT PPDU. The VHT STA may support S-MPDU as its primary MAC function. The VHT STA may support bandwidth indication response as its primary MAC function. 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

[0040] The operating channel width is the channel width that the STA can currently receive. It is also possible.

[0041] A High Efficiency (HE) STA may also be a VHT STA if it operates in the 5 GHz band. A 20 MHz-only HE STA may not support 40 MHz and 80 MHz channel widths. Support for a 20 MHz operating channel width may be mandatory for an HE STA. A 20 MHz-only non-AP HE STA 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.

[0042] 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 a HE STA in 2.4 GHz. An EHT STA may use operation elements for HT and / or VHT and / or HE STAs.

[0043] An Ultra High Reliability (UHR) STA may operate in the 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 a HE STA in 2.4 GHz. For example, a UHR STA may be a HT STA in 2.4 GHz. A UHR STA may support Non Primary Channel Access. A UHR STA may use operation elements for a HT, a VHT, a HE STA, and / or a UHR STA. That is, a UHR STA may be controlled by a HT operation element, a VHT operation element, a HE operation element, a EHT operation element, and / or a UHR operation element.

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

[0045] 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 composed of STAs that are

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

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

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

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

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

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

[0052] 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 includes a Frame Control field, a Duration field, an Address 1 field, an Address 2 field, an Address 3 field, a Sequence Control field, It may be configured with an Address 4 field and a QoS Control field. The MAC frame format may be MPDU.

[0053] 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 The Frame Control field of the MAC header may be composed of subfields such as a More data subfield, a Protected Frame subfield, a +HTC subfield, a Control Frame Extension subfield, a Compressed SSID Present subfield, an ANO Present subfield, a BSS BW subfield, a Security subfield, and an AP PM subfield. 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

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

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

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

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

[0058] 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 present, the subtype may be Reassociation Request. In the Type subfield, If a Management frame is indicated 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.

[0059] The Beacon frame may be a frame containing information such as the Beacon period and SSID. The Beacon 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.

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

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

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

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

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

[0065] The HT Operation element consists of an Element ID field, a Length field, and a Primary Channel field. The HT Operation information field and Basic HT-MCS Set field define 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. The STA Channel Width field may define the channel width that the STA can use for transmission. The STA Channel Width field may be set to 0 for 20 MHz. The STA Channel Width field may allow the use of any channel within the supported channel width set. 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.

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

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

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

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

[0070] 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, it may indicate the channel center frequency index of the primary 80MHz channel of the VHT BSS.

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

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

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

[0074] 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 the VHT Operation Information field is present in the HE Operation element, and may be set to 0 otherwise. The 6GHz Operation Information Present field indicates that the 6GHz Operation Information It may be set to 1 to indicate the presence of the tion field, or 0 otherwise.

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

[0076] The 6 GHz Operation Information field of the HE Operation element format may provide channel and bandwidth information related to 6 GHz operation. The 6 GHz Operation Information field format includes a Primary channel field, a Control field, a Channel Center Frequency Segment 0 field, and a Channel Center Frequency Segment 1 field. , 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.

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

[0078] The EHT Operation element format consists of 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 define the center frequency of the 20 MHz channel, 40 MHz channel, or 80 MHz channel in 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. may index the center frequency of a 320 MHz channel for a 320 MHz BSS bandwidth.

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

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

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

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

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

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

[0085] PPDU consists of PHY preamble, PHY header, PSDU (PHY Service Data Unit), etc. The PPDU may be assigned L-STF, L-LTF, and L-SIG. The PPDU may be assigned HT-STF, HT-LTF, and HT-SIG. The PPDU may be assigned 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.

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

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

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

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

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

[0091] The Priority Inter Frame Space (PIFS) may be used to control access to the medium to obtain priority access. The PIFS may also be used to perform Clear Channel Assessment (CCA) of the secondary 20 MHz channel, secondary 40 MHz channel, and secondary 80 MHz channel before transmitting on 40 MHz, 80 MHz, or 160 MHz.

[0092] CCA (Clear Channel Assessment) is the determination of the current usage of the wireless medium. CCA is a function at the physical layer that determines the current usage of the wireless medium. The CCA may be referred to as a CCA function.

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

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

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

[0096] 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 DCF may be a function that must be implemented in all STAs.

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

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

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

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

[0101] A STA wishing to start transmitting data or management frames using DCF must wait until the medium is busy. A STA may use a carrier sense mechanism to determine the medium / idle state. If the medium is busy, the STA may 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.

[0102] The contention window parameter may take on an 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.

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

[0104] 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 be an Enhanced Distributed Channel Access (EDCA) 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.

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

[0106] 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 uses four UPs to support the delivery of traffic using the UP of a STA. An AC (Access Category) may be defined. The AC is the access category that a QoS STA can use on 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.

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

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

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

[0110] 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 EDCA. If you do this, you may acquire a TXOP.

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

[0112] The carrier sense mechanism uses the NAV (Network Allocation Vector) status and STA transmission The NAV may be a mechanism for determining whether the medium is busy or idle, combining the physical carrier sensing of the receiver with the NAV. The NAV may be maintained by each STA and may be an indicator of the period during which the STA does not initiate transmission onto the wireless medium, regardless of whether the STA's Clear Channel Assessment (CCA) function senses the medium as busy.

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

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

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

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

[0117] A STA may maintain two NAVs. An AP may maintain two NAVs. The two NAVs may be intra-BSS NAV and basic NAV. Intra-BSS NAV is determined by intra-BSS PPDU. The basic NAV may be updated by an inter-BSS PPDU. The basic NAV may be updated by a PPDU that cannot be classified as an intra-BSS PPDU or an inter-BSS PPDU. A STA that maintains two NAVs may use the virtual CS in A virtual CS indication may indicate that the medium is idle. That is, for a STA that maintains two NAV timers, if both the Intra-BSS NAV and basic NAV timers are zero, the virtual CS indication may indicate that the medium is idle. If at least one of the two NAV timers is non-zero, the virtual CS indication may indicate that the medium is busy. That is, a STA or AP that maintains two NAVs must ensure that the virtual CS indication indicates that the medium is busy if at least the Intra-BSS NAV or basic NAV timer is not 0. It may be shown.

[0118] The NAV may be a basic NAV. The NAV may be an intra-BSS NAV. basic NAV The NAV may be a NAV. The Intra-BSS NAV may be a NAV. The NAV is called basic NAV. NAV may be referred to as intra-BSS NAV. Basic NAV may be referred to as NAV. Intra-BSS NAV may be referred to as NAV.

[0119] 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 a Duration field that 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.

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

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

[0122] 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 the STA. 1104 may be a timeline of the operation of the AP or the STA.

[0123] The STA or AP may perform a frame exchange. The exchange is when the STA or AP sends an RTS and the STA or AP sends a CTS in response to the RTS. For example, the frame exchange may be a case where the STA or AP transmits a Trigger frame, and the STA or AP transmits a CTS in response to the Trigger frame. For example, the frame exchange may be In this case, the STA or AP sends an MU-RTS, and the STA or AP sends a CTS in response to the MU-RTS. For example, the trigger frame is used by the AP to allocate a resource unit (RU) to a STA. The Trigger frame may be a frame that includes at least the Common Info field and / or the User Info List field. The Common Info field is used to identify the STAs. The User Info List field may contain zero or more User Info fields. The User Info field is used to assign an RU to each STA. For example, the User Info field may include an RU allocation subfield.

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

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

[0126] 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, an 80MHz channel does not include a 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.

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

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

[0129] When channel bonding is performed, the STA performs the backoff procedure on the primary 20MHz channel. In the secondary channel, channel sensing may be performed in the PIFS immediately before transmission. For example, in FIG. 12, the STA transmits with a 160 MHz channel width. A backoff procedure may be performed, and channel sensing may be performed for a PIFS period immediately before transmission in 1202, 1203, 1204, 1205, 1206, 1207, and 1208.

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

[0131] The center frequency of the Primary 20 MHz 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 6 GHz 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 6 GHz 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.

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

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

[0134] 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 a STATE parameter. The PHY-CCA.indication primitive may include at least a channel-list parameter. The PHY-CCA.indication primitive may include at least a STATE and a channel-list parameter. The STATE parameter value of the PHY-CCA.indication primitive may be BUSY if the PHY's evaluation of the channels indicates that the channels are unavailable. Otherwise, the STATE parameter value of the PHY-CCA.indication primitive may be IDLE. If the STA is in the IDLE state, the channel-list parameter is not present. Type of PHY operating If the CCA is determined by a single channel, the channel-list parameter must be Otherwise, the channel-list parameter may contain a set of busy channels, i.e., the CCA is not performed by multiple channels. If determined to be BUSY, the channel-list parameter may be present. For example, the channel-list parameter entry may indicate primary, secondary, secondary40, and secondary80. The STATE parameter may also be referred to as the STATUS parameter. The STATUS parameter may also be referred to as the STATE parameter.

[0135] The PHY-CCA.indication primitive may include a channel-list parameter. The channel-list parameter may include one entry. An entry is a set of entries. A set of entries may be defined. The set of entries may be referred to as channel-list parameter entries. For example, the set of entries may include primary, secondary, secondary40, secondary80, primary1, primary2, secondary2, secondary4, and secondary8.

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

[0137] The PHY-CCA.indication primitive may be generated (issued) when the channel state changes from idle to busy, when the channel state changes from busy to idle, or when an entry in the channel-list parameter changes. "Execute" may be synonymous with "create a primitive." "Create a primitive" may be synonymous with "publish a primitive."

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

[0139] 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, when the state of the primary channel (1201) changes from idle to busy, the STA 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.

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

[0141] 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 channel is above a predetermined value (e.g., above -82 dBm), the STA may issue a PHY-CCA.indication(BUSY, {primary}) primitive within aCCATime. That is, the STA may issue a PHY-CCA.indication(BUSY, {primary}) primitive when it receives a non-HT duplicate or PPDU above -82 dBm on the primary 20 MHz channel. -82 dBm may be the threshold for determining whether the channel is idle or busy.

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

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

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

[0145] 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 The PHY shall issue the PHY-CCA.indication(BUSY, {secondary80}) primitive if any signal greater than -56 dBm is present in the 80 MHz channel. The PHY shall issue the PHY-CCA.indication(BUSY,{primary}), PHY-CCA.indication(BUSY,{secondary}), or PHY-CCA.Indication(BUSY, {secondary40}) primitive when an 80 MHz preamble or PPDU greater than -69 dBm is detected in the secondary 80 MHz channel with a probability of 90% or greater within aCCAMidTime in an idle 160 MHz or 80+80 MHz operating channel width. 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.

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

[0147] A STA with an operation channel width of W MHz can receive a small amount of data with an operation channel width of W MHz. Detect the start of a PPDU occupying at least the primary 20MHz channel with a probability of more than a specified percentage (e.g., 90% or more), and measure the power of the preamble or PPDU measured within the primary 20MHz channel. is greater than or equal to a predetermined value (e.g., greater than or equal to -82 dBm), the STA may issue a PHY-CCA.indication with the STATUS parameter set to BUSY within aCCATime. That is, a STA may issue a PHY-CCA.indication(BUSY) primitive upon receiving a preamble or PPDU greater than -82 dBm on the primary 20 MHz channel. The receiver may issue a PHY-CCA.indication with the STATUS parameter set to BUSY for any signal on the primary 20 MHz channel that exceeds a threshold (e.g., -62 dBm) that is a predetermined value (e.g., 20 dB) higher than the sensitivity of the minimum modulation and coding rate within aCCATime from the signal's arrival at the receiver antenna. If the Operation channel width is greater than or equal to 20 MHz, the channel-list parameter may be present and set to {primary}. Following the indication, the receiver shall not issue a PHY-CCA.indication primitive with the STATUS parameter set to IDLE or a PHY-CCA.indication with a modified channel-list parameter while the threshold continues to be exceeded.

[0148] The PHY issues the PHY-CCA.indication primitive with the STATUS parameter set to BUSY. If no conditions exist and the operating channel width is 40MHz, 80MHz, 160MHz, or 80+80MHz in an idle state, any signal in the secondary 20MHz channel will reach the receiver antenna. If the signal level exceeds the threshold of -62 dBm or more within aCCATime after the PHY-CCA.indication primitive is set to BUSY and the channel-list parameter is set to {secondary}, The PHY issues the PHY-CCA.indication primitive with the STATUS parameter set to BUSY. When there are no conditions to issue a 20MHz preamble, and the operating channel width is 40MHz, 80MHz, 160MHz, or 80+80MHz in an idle state, the secondary 20MHz channel must be at least -72dBm. If a PPDU is detected with a probability of 90% or greater within a CCAMidTime period, the receiver shall issue a PHY-CCA.indication primitive with the STATUS parameter set to IDLE, or with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}. Following an indication, while the threshold continues to be exceeded, the receiver shall issue a PHY-CCA.indication primitive with the STATUS parameter set to IDLE, or with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40} or {secondary 80}. The set PHY-CCA.indication primitive is not issued.

[0149] The PHY issues the PHY-CCA.indication primitive with the STATUS parameter set to BUSY. If no condition exists and there is no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, then in the idle operating channel width of 80MHz, 160MHz, or 80+80MHz, Any signal that reaches the receiver antenna must exceed the threshold of -59 dBm or greater within aCCATime. If the PHY receives a BUSY signal, it issues a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}. If there are no conditions for issuing a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, and there is no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, and a 40 MHz preamble or PPDU of -72 dBm or higher is detected on the secondary 40 MHz channel with a probability of 90% or higher within the aCCAMidTime period in an idle 80 MHz, 160 MHz, or 80+80 MHz operating channel width, the PHY shall issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}. If there are no conditions for issuing a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, the PHY shall issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}. In the 80MHz, 160MHz, or 80+80MHz operating channel width in the 40MHz secondary channel, a 20MHz preamble or PPDU of -72dBm or more is If the indication is detected with a probability of 90% or greater within a CCAMidTime period, the receiver shall issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}. Following an indication, while the threshold continues to be exceeded, the receiver shall issue a PHY-CCA.indication primitive with the STATUS parameter set to IDLE, or a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 80}. No primitives will be issued.

[0150] The PHY issues the PHY-CCA.indication primitive with the STATUS parameter set to BUSY. condition, and the STATUS parameter set to BUSY, and the PHY-CCA.indication primitive with the channel-list parameter set to {secondary}, and the STATUS parameter set to BUSY. If there is no PHY-CCA.indication primitive with the channel-list parameter set to {secondary 40}, and if there is any signal of -56 dBm or higher in the secondary 80 MHz channel in an idle 160 MHz or 80+80 MHz operating channel width, the PHY issues a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 80}. If there is no PHY-CCA.indication primitive with the -list parameter set to {secondary} and no PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}, and if an 80 MHz preamble or PPDU at -69 dBm or higher is detected in the secondary 80 MHz channel with a probability of 90% or higher within aCCAMidTime in an idle 160 MHz or 80+80 MHz operating channel width, a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 80} is issued. The PHY shall issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY, and when there are no PHY-CCA.indication primitives with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary}, and no PHY-CCA.indication primitives with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}, and when in an idle 160 MHz or 80+80 MHz operating channel width, the PHY shall issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}, and when there are no PHY-CCA.indication primitives with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40} ... in an idle 160 MHz or 80+80 MHz operating channel width, the PHY shall issue a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}. If a 40MHz preamble or PPDU at -72 dBm or higher is detected on the channel with a probability of 90% or higher within the aCCAMidTime period, the PHY issues a PHY-CCA.indication primitive with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 80}. The PHY issues a PHY-CCA.indication primitive with the STATUS parameter set to BUSY if there are no PHY-CCA.indication primitives with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 40}. If, in an idle state with an operating channel width of 160 MHz or 80+80 MHz, a 20 MHz preamble or PPDU is detected on any 20 MHz subchannel of the secondary 80 MHz channel at a level above -72 dBm with a probability of more than 90% within aCCAMidTime, a PHY-CCA.indication primitive shall be issued with the STATUS parameter set to BUSY and the channel-list parameter set to {secondary 80}.

[0151] A STA with an operation channel width of W MHz can receive a small amount of data with an operation channel width of W MHz. Detect the start of a PPDU occupying at least the primary 20MHz channel with a probability of more than a specified percentage (e.g., 90% or more), and measure the power of the preamble or PPDU measured within the primary 20MHz channel. is greater than a predetermined value (for example, greater than -82 dBm), a STA may issue a PHY-CCA.indication with the STATUS parameter set to BUSY within the aCCATime period. In other words, a STA may issue a PHY-CCA.indication(BUSY) primitive when it receives a preamble or PPDU greater than -82 dBm on the primary 20 MHz channel. If the Operating channel width is greater than 20 MHz, the Channel-list The parameter may be present and set to {primary}. A PHY-CCA.indication with the STATUS parameter set to BUSY may be issued for any signal that exceeds the -62 dBm threshold on the primary 20 MHz channel within aCCATime after the signal arrives.

[0152] 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 while the primary channel is busy due to OBSS traffic. The NPCA primary channel may be called something other than the NPCA primary channel. For example, the NPCA primary channel may be called a secondary primary channel. Access may be CCA. Access may be a backoff procedure. Access may be EDCA. For example, while the primary channel is busy, this refers to the period during which NAV is set (maintained) on the primary channel. For example, "while the primary channel is busy" may be a period during which the backoff procedure is not performed on the primary channel. For example, "while the primary channel is busy" may be This may be the period indicated by the received PPDU. may be referred to as "when the primary channel is busy." "While the primary channel is busy" may be rephrased as "when the primary channel is busy."

[0153] In the present invention, the AP and / or STA performs NPCA (Non Primary Channel Access). NPCA may be an operation for accessing another channel while the primary channel is busy due to OBSS traffic. For example, OBSS traffic may be a PPDU received from the OBSS. OBSS traffic may be an inter-BSS PPDU. OBSS traffic may be a case where NAV is set. OBSS traffic may be a case where basic NAV is set. OBSS traffic may be an OBSS frame exchange. The AP and / or STA may perform a backoff procedure on another channel while the primary channel is busy due to OBSS traffic. For example, the channel on which the backoff procedure is performed while the primary channel is busy due to OBSS traffic may be referred to as the NPCA primary channel, secondary primary channel, etc. The name of the channel on which the backoff procedure is performed while the primary channel is busy may be a name other than those mentioned above. In other words, the AP and / or STA may perform a backoff procedure on the NPCA primary channel when the primary channel becomes busy due to OBSS traffic. The AP and / or STA may perform backoff procedures on the NPCA primary channel while the NAV is set on the primary channel by the OBSS PPDU. Once the backoff procedure is complete on the NPCA primary channel, the AP and / or STA may transmit on one or more channels, including the NPCA primary channel but not the primary channel. The AP and / or STA may transition to the primary channel before the end of the NAV period. The AP may transmit information related to NPCA primary channel access in a frame. The STA may determine an action related to NPCA primary channel access based on the frame received from the AP.

[0154] In other words, the NPCA primary channel is used to access the channel while the primary channel is busy. The NPCA primary channel may be the channel for channel access while the NAV is set on the primary channel. The channel may be a channel for channel access while basic NAV is set on the primary channel. The NPCA primary channel may be a channel for channel access while the primary channel is busy by the OBSS PPDU. The NPCA primary channel may be a channel for channel access while NAV is set on the primary channel by the OBSS PPDU. The channel access may be a channel for accessing the mobile station. The period during which the NAV is set may be referred to as the period during which the NAV is maintained. The channel access may be a backoff procedure. The channel access may be EDCA. The channel access may be EDCAF. The channel access may be CCA.

[0155] 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 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. 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 of 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 position of the NPCA primary channel of Non Primary Channel Access. The UHR operation element may include a field for indicating the channel width of 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 of 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.

[0156] The information related to Non-Primary Channel Access may be information indicating the location of at least the NPCA primary channel. The information related to Non-Primary Channel Access may be information indicating the location of the NPCA primary channel and / or the NPCA secondary 20MHz channel and / or the NPCA secondary 40MHz channel and / or the NPCA secondary 80MHz channel. If the operating channel width includes at least the NPCA primary channel, the AP In this case, the STA may transmit frames containing information related to Non Primary Channel Access. If the frame received from the AP contains information related to Non Primary Channel Access, it determines that at least the NPCA primary channel exists in the operating channel width. That is, if the frame received from the AP contains information related to Non-Primary Channel Access, the STA may perform Non-Primary Channel Access. If the frame received from the AP does not contain information related to Non-Primary Channel Access, the STA may determine that the NPCA primary channel does not exist in the operating channel width. In other words, the STA receives information related to Non Primary Channel Access in the frame from the AP. If the information is not included, it may be determined that non-primary channel access is not performed.

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

[0158] 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 A channel may also be referred to as a secondary 80 MHz channel. , it may be the case that channel access is performed on the NPCA primary channel.

[0159] FIG. 13 is a diagram illustrating an example of a backoff procedure on an NPCA primary channel according to one aspect of this embodiment. 1301, 1302, 1303, 1304, 1305, 1306, 1307, and 1308 may each be a 20 MHz channel. FIG. 13 may be a diagram of an STA or AP operating with a channel width of 160 MHz. 1301 may be a primary channel. 1306 may be an NPCA primary channel. 1309 may be a STA or AP. The frame 1309 may be a frame transmitted by another STA or AP that is received by the AP. The frame 1309 may be a frame transmitted by a STA or AP that belongs to an OBSS and is received by the STA or AP. For example, 1309 may be an RTS frame. 1309 may be a CTS frame. 1309 may be a Data frame. 1309 may be a PPDU. 1309 may be a PPDU received from a STA or AP belonging to an OBSS. 1301 may be a period during which the primary channel is busy. 1310 may be a period during which the NAV is set (maintained). 1311 may be a backoff procedure (backoff counter, contention window, DCF, EDCA). 1312 may be a PPDU transmission. For example, when a STA or AP receives 1309 in 1301, it may set 1310 in 1301 for the period indicated by the Duration field of 1309. The STA sets 1310 in 1301. If the STA moves to 1306, it may move to 1306. If the STA moves to 1306, it may move to 1311. The STA may start 1312 after 1311 is completed. For example, when the STA performs the operation of FIG. 13, the STA is 204 in FIG. 2, and 1309 is The frame may be transmitted by 207. Figure 13 is a diagram of an AP operating at 160 MHz. For example, when the AP performs the operation of FIG. 13, the AP operates as 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 a transmission using the NPCA primary channel of 1306, the NPCA secondary 20 MHz channel of 1305, and the NPCA secondary 40 MHz channel consisting of 1307 and 1308. In other words, if the backoff procedure is performed in 1301, In this case, 1305, 1306, 1307 and 1308 are secondary 80MHz channels. In Non-Primary Channel Access, when a backoff procedure is performed in 1306, 1305 may be an NPCA secondary 20MHz channel, and 1307 and 1308 may be channels that constitute an NPCA secondary 40MHz channel. The AP determines whether 1305 within the Operating channel width is an NPCA secondary 20MHz channel. , 1305 is the NPCA primary channel, 1307 and 1308 are NPCA secondary The STA may determine that 1305 in the Operating channel width is the NPCA secondary 20 MHz channel, 1305 is the NPCA primary channel, 1307 and 1308 are the NPCA secondary 20 MHz channel, and notify the STA in the frame. 308 may determine that the channels constitute an NPCA secondary 40 MHz channel.

[0160] The STA may generate a PHY-CCA.indication primitive in the physical layer processing unit SU3. Even if the PHY-CCA.indication primitive generated by the physical layer processing unit SU3 is indicated to the MAC layer processing unit SU4, The AP may generate a PHY-CCA.indication primitive in the physical layer processing unit AU3. The PHY-CCA.indication primitive generated by the physical layer processing unit AU3 is indicated to the MAC layer processing unit AU4. The PHY-CCA.indication primitive may include a channel-list parameter. The channel-list parameter may include one entry. An entry is a set of entries. A set of entries may be defined. The set of entries may be referred to as channel-list parameter entries. For example, the channel-list parameter entries may include an entry to indicate that the NPCA primary channel is busy. That is, the PHY-CCA.indication primitive includes a channel-list parameter, and the channel- The list parameter contains one entry, which is one of a set of entries. The set of entries may include at least a first entry, and the first entry may indicate that the NPCA primary channel is busy.

[0161] For example, a set of entries may contain NPCA primary and / or NPCA secondary and / or or NPCA secondary 20 and / or NPCA secondary 40 and / or NPCA secondary 80. That is, NPCA primary and / or NPCA secondary and / or NPCA secondary 20 and / or NPCA secondary 40 and / or NPCA secondary 80 A channel-list parameter entry may be defined that includes NPCA primary. NPCA primary may be the value of entry. NPCA primary is used to indicate the channel status of the NPCA primary channel. NPCA primary indicates that the NPCA primary channel is busy. NPCA primary may also indicate that the primary channel is busy. NPCA secondary may be the value of entry. NPCA secondary "secondary" may be an entry for indicating the channel status of the NPCA secondary channel. "NPCA secondary" may be an entry for indicating that the NPCA secondary channel is busy. "NPCA secondary" may further indicate that the primary channel is busy. "NPCA secondary" may indicate that the NPCA primary channel is idle. "secondary20" may be the value of an entry. "NPCA secondary20" indicates the channel status of the NPCA secondary 20MHz channel. NPCA secondary20 may be an entry indicating the channel status of the NPCA secondary 20MHz channel. NPCA secondary20 may be an entry indicating that the NPCA secondary 20MHz channel is busy. NPCA secondary20 may further indicate that the primary channel is busy. NPCA secondary20 may indicate that the NPCA primary channel is idle. secondary40 may be the value of an entry. NPCA secondary40 may be an entry indicating the channel status of the NPCA secondary 40MHz channel. NPCA secondary40 may be an entry indicating that the NPCA secondary 40MHz channel is busy. NPCA secondary40 may be an entry indicating that the primary channel is busy. NPCA secondary40 may further indicate that the NPCA primary channel and the NPCA secondary 20MHz channel are idle. secondary80 may be the value of an entry. NPCA secondary80 may be an entry indicating the channel state of the NPCA secondary 80MHz channel. NPCA secondary80 may be an entry indicating that the NPCA secondary 80MHz channel is busy. NPCA secondary80 may further indicate that the primary channel is busy. NPCA secondary80 may be an entry indicating that the NPCA primary channel, the NPCA secondary 20MHz channel, and the NPCA secondary 40MHz channel are idle. For example, a set of entries may include primary, secondary, secondary40, secondary80, primary1, primary2, secondary2, secondary4, secondary8 , and / or NPCA primary and / or NPCA secondary and / or NPCA secondary 20 and / or NPCA secondary 40 and / or NPCA secondary 80 Good. That is, primary, secondary, secondary40, secondary80, primary1, primary2, secondary2, secondary4, secondary8, and / or NPCA primary and / or NPCA secondary and / or NPCA secondary 20 and / or NPCA secondary 40 and / Alternatively, channel-list parameter entries may be defined that include NPCA secondary 80. The value of entry, NPCA primary, may be referred to as secondary primary. An NPCA primary may be called an anchor primary. The value of an entry in the NPCA secondary may be called a secondary secondary. The value of an entry in the NPCA secondary may be called an anchor secondary. The NPCA secondary value of the entry may be referred to in a way other than the above. The NPCA secondary value of the entry may be referred to as secondary secondary value 20. The NPCA secondary value of the entry may be referred to as anchor secondary value 20. The NPCA secondary value of the entry may be referred to in a way other than the above. The NPCA secondary value of the entry may be referred to as secondary secondary value 40. The NPCA secondary value of the entry may be referred to as anchor secondary value 40. The NPCA secondary value of the entry may be referred to in a way other than the above. The NPCA secondary 80 that is the value of the entry may be referred to as the secondary secondary 80. The NPCA secondary 80 that is the value of the entry may be referred to as the anchor secondary 80. The entry value NPCA secondary80 may be called in a way other than that described above.

[0162] A STA or AP issues a PHY-CCA.indication primitive associated with the NPCA primary channel. The PHY-CCA.indication primitive associated with the NPCA primary channel may be This may be issued by the PHY (physical layer) to indicate to the MAC that the primary channel is idle or busy. {NPCA primary} may be a channel-list parameter for the NPCA primary channel. For example, if the NPCA primary channel is idle, the STA or AP The physical layer may issue a PHY-CCA.indication primitive with a STATUS of IDLE and a channel-list parameter of {NPCA primary}. That is, PHY-CCA.indication(IDLE, {NPCA For example, if the NPCA primary channel is busy, the physical layer of the STA or AP may issue a PHY-CCA.indication primitive with a STATUS of BUSY and a channel-list parameter indicating {NPCA primary}. In other words, a PHY-CCA.indication(BUSY, {NPCA primary}) primitive may be issued. The associated PHY-CCA.indication primitive may be issued only if NPCA is being performed. If the MAC layer receives a PHY-CCA.indication primitive with STATUS set to IDLE and the channel-list parameter set to {NPCA primary}, it may determine that the NPCA primary channel is idle. A MAC layer that receives a PHY-CCA.indication primitive with STATUS set to IDLE and a channel-list parameter indicating {NPCA primary} may determine that the NPCA primary channel is idle and the primary channel is busy. A MAC layer that receives a PHY-CCA.indication primitive with STATUS set to BUSY and a channel-list parameter indicating {NPCA primary} may determine that the NPCA primary channel is busy. A MAC layer that receives a PHY-CCA.indication primitive with STATUS set to BUSY and a channel-list parameter indicating {NPCA primary} may determine that the NPCA primary channel and the primary channel are busy. The channel-list parameter {NPCA primary} may be referred to as {secondary primary}. The MAC layer may determine that the NPCA primary channel is busy if the channel-list parameter is set to NPCA primary. The MAC layer may determine that the channel-list parameter is set to NPCA primary. If the NPCA primary channel is busy, Good too.

[0163] The STA or AP shall transmit the PHY-CCA.indication primitive associated with the NPCA secondary channel. The PHY-CCA.indication primitive associated with the NPCA secondary channel may be issued by the PHY (physical layer) to indicate to the MAC that the NPCA secondary channel is idle or busy. {NPCA secondary} may be the channel-list parameter for the NPCA secondary channel. For example, if the NPCA secondary channel is idle, the physical layer of the STA or AP may issue a PHY-CCA.indication primitive with a STATUS of IDLE and a channel-list parameter indicating {NPCA secondary}. That is, the PHY-CCA.indication(IDLE, {NPCA secondary}) primitive may be issued. For example, if the NPCA secondary channel is busy, the physical layer of the STA or AP may issue a PHY-CCA.indication primitive with a STATUS of BUSY and a channel-list parameter indicating {NPCA secondary}. That is, the PHY-CCA.indication(BUSY, {NPCA secondary}) primitive may be issued. A PHY-CCA.indication primitive associated with a secondary channel may be issued when NPCA is performed. A PHY-CCA.indication primitive associated with an NPCA secondary channel may be issued when the NPCA primary channel is idle. A PHY-CCA.indication primitive associated with an NPCA secondary channel may be issued when the NPCA primary channel is not busy. The MAC layer that receives a PHY-CCA.indication primitive with STATUS set to IDLE and a channel-list parameter indicating {NPCA secondary} shall determine whether the NPCA secondary channel is active. When the MAC layer receives a PHY-CCA.indication primitive with STATUS set to IDLE and the channel-list parameter set to {NPCA secondary}, it may determine that the channel is in the NPCA primary channel. The nel and NPCA secondary channel may be determined to be idle. And when the MAC layer receives the PHY-CCA.indication primitive whose channel-list parameter indicates {NPCA secondary}, the MAC layer determines that the NPCA primary channel and the NPCA secondary channel are idle. When the MAC layer receives a PHY-CCA.indication primitive with STATUS set to BUSY and the channel-list parameter set to {NPCA secondary}, it may determine that the NPCA secondary channel is busy. When the MAC layer receives a PHY-CCA.indication primitive with STATUS set to BUSY and the channel-list parameter set to {NPCA secondary}, it may determine that the NPCA primary channel is idle and the NPCA secondary channel is busy. When the MAC layer receives a PHY-CCA.indication primitive with STATUS set to BUSY and the channel-list parameter set to {NPCA secondary}, it may determine that the NPCA primary channel is idle. The NPCA determines that the secondary and primary channels are busy. The MAC layer may determine that the NPCA secondary channel is busy if the channel-list parameter is set to NPCA secondary. The MAC layer may determine that the NPCA secondary channel and the primary channel are busy if the channel-list parameter is set to NPCA secondary. For example, the channel-list parameter {NPCA secondary} may be referred to as {secondary secondary}. The channel-list parameter {NPCA secondary} may be referred to in other ways.

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

[0165] A STA may issue (generate) a PHY-RXSTART.indication primitive. An AP may issue (generate) a PHY-RXSTART.indication primitive. The PHY-RXSTART.indication primitive indicates that the PHY (physical layer) has issued a valid start of a PPDU containing a valid PHY header. The PHY-RXSTART.indication primitive may indicate to the local MAC entity that a PPDU start has been received. The PHY-RXSTART.indication primitive may not be generated until the PHY has determined the PPDU format (e.g., a VHT PPDU starting with an HT PHY header).

[0166] The STA may generate a PHY-RXSTART.indication primitive in the physical layer processing unit SU3. The PHY-RXSTART.indication primitive generated by the physical layer processing unit SU3 is sent to the MAC layer processing unit SU4. The AP generates a PHY-RXSTART.indication primitive in the physical layer processing unit AU3. The AP may indicate the PHY-RXSTART.indication primitive generated by the physical layer processing unit AU3 to the MAC layer processing unit AU4.

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

[0168] 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 contain multiple parameters.

[0169] The syntax of a frame, MPDU, or A-MPDU is to be transmitted with certain TXVECTOR parameters or received with certain RXVECTOR parameters. , A-MPDU)。 Syntax of the form "a PPDU is transmitted with certain TXVECTOR parameters" or "a PPDU is received with certain RXVECTOR parameters" may be understood to refer to the TXVECTOR or RXVECTOR parameters, respectively, corresponding to the PSDU included in the PPDU.

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

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

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

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

[0174] The TXVECTOR and / or RXVECTOR of the UHR PHY may include additional parameters related to the operating mode of the UHR PHY, e.g., may have a FORMAT parameter etc.

[0175] The PHY-RXSTART.indication primitive may be generated by the local PHY entity to the MAC sublayer when the PHY successfully validates the PHY header at the start of a new PPDU. After generating the PHY-RXSTART.indication primitive, the PHY may maintain physical medium busy status for the period required for the PHY to transfer a frame of the indicated LENGTH at the indicated DATARATE. The physical medium busy status is not maintained until the PHY-RXEND.indication(CarrierLost) primitive or PHY-RXEND.indication(FormatViolation) primitive is generated at the end of the period. It may be generated and maintained by the PHY before completion of the PHY-RXSTART.indication primitive. When the MAC entity receives the ACK, the MAC may prepare a new receive flow.

[0176] The PHY-RXEND.indication may be a primitive for the PHY to indicate to the local MAC entity that the currently receiving PPDU is complete. The PHY-RXEND.indication primitive may include an RXERROR parameter. The RXERROR parameter may carry one or more values ​​indicating NoError or an error condition. The RXERROR parameter may indicate NoError, FormatViolation, CarrierLost, UnsupportedRate, or Filtered. NoError may be used to indicate that no errors occurred during the PHY's receiving process. FormatViolation may be used to indicate that the receiving CarrierLost may be used to indicate that the carrier was lost during reception of the received PSDU, preventing further processing of the PSDU. UnsupportedRate may be used to indicate that an unsupported rate was exceeded during reception of the received PPDU. This may be used to indicate that an unspecified data rate was detected. Filtered may be used to indicate that the PPDU was filtered due to the conditions set in PHYCONFIG_VECTOR during reception of the PPDU.

[0177] A STA or AP may issue a PHY-RXSTART.indication primitive when it receives a duplicate PPDU on the primary channel. A STA's PHY or an AP's PHY may issue a PHY-RXSTART.indication primitive when it receives a duplicate PPDU on the primary channel. Alternatively, the AP may send PHY-RXSTART.indication prim for PPDUs that do not overlap with the primary channel. The PHY of the STA or the PHY of the AP does not overlap with the primary channel. The PHY-RXSTART.indication primitive need not be issued for a PPDU that does not include the primary channel. The PPDU that overlaps the primary channel may be a PPDU that includes at least the primary channel. The PPDU that overlaps the primary channel may be a PPDU that is transmitted using at least the primary channel. The PPDU that overlaps the primary channel may be a PPDU whose transmitted frequency overlaps with the frequency of the primary channel.

[0178] 12, for example, a STA or an AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with 1201. For example, a STA or an AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU transmitted using 1201. For example, a STA or an AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU transmitted using 1201 and 1202. For example, a STA or an AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU transmitted using 1201, 1202, 1203, and 1204. That is, a STA Alternatively, an STA or AP may issue a PHY-RXSTART.indication primitive upon receiving a PPDU transmitted using 1201. For example, an STA or AP may not issue a PHY-RXSTART.indication primitive upon receiving a PPDU that does not overlap with 1201. For example, an STA or AP may not issue a PHY-RXSTART.indication primitive upon receiving a PPDU transmitted using only 1202. For example, an STA or AP may not issue a PHY-RXSTART.indication primitive upon receiving a PPDU transmitted using only 1203. When a PPDU transmitted using 204 is received, the STA or AP does not need to issue the PHY-RXSTART.indication primitive. When received, the PHY-RXSTART.indication primitive does not need to be issued.

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

[0180] The AP may request one or more STAs to transmit a TB (Trigger Based) PPDU. The AP uses a Trigger frame to notify one or more STAs of the transmission of a TB PPDU. The Trigger frame may be used to request one or more TB PPDU transmissions and to allocate resources for one or more TB PPDU transmissions. When a STA receives a Trigger frame from the AP, it may transmit a TB PPDU based on the information included in the received Trigger frame. The Trigger frame is used by the AP to realize UL MU (Multi-User) transmission. The Trigger frame may be used for OFDMA transmission. The TB PPDU may be a PPDU. The TB PPDU may be referred to as a PPDU.

[0181] In FIG. 12, for example, the AP does not receive the TB PPDU that it requested. The PHY-RXSTART.indication primitive does not have to be issued for a non-overlapping PPDU. For example, the AP may receive a TB PPDU that it requested and issue a PHY-RXSTART.indication primitive for a PPDU that does not overlap with 1201. For example, the AP may request the STA to send a TB PPDU to 1202. The AP may issue the PHY-RXSTART.indication primitive upon receiving a PPDU from a STA using 1202. For example, the AP may assign a TB PPDU to 1203 and 1204. The AP may then issue the PHY-RXSTART.indication primitive upon receiving a PPDU from a STA using 1203 and 1204. For example, the AP may send a TB PPDU to the STA using 1205 and 1206, 1207, and 1208, and the AP assigns 1205 and 1209 from the STA. The STA may issue the PHY-RXSTART.indication primitive upon receiving a PPDU using 6, 1207, or 1208. The PPDU transmitted by the STA may be a TB PPDU.

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

[0183] A STA or AP may not issue the PHY-RXSTART.indication primitive for PPDUs that do not overlap with the primary channel and / or the NPCA primary channel. A STA or AP shall issue the PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the NPCA primary channel. In NPCA, a STA may issue the PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the primary channel but overlaps with the NPCA primary channel. In NPCA, an AP may issue the PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the primary channel but overlaps with the NPCA primary channel. Upon receiving this, the STA may issue the PHY-RXSTART.indication primitive. In NPCA, an AP may not issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the NPCA primary channel. In NPCA, an AP may not issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the NPCA primary channel. The primary channel and the NPCA primary channel may be different channels. The PHY may issue a PHY-RXSTART.indication primitive. The PHY of a STA may issue a PHY-RXSTART.indication primitive. The PHY of an AP may issue a PHY-RXSTART.indication primitive.

[0184] For a PPDU requested by an AP, the AP may issue a PHY-RXSTART.indication primitive upon receiving the PPDU on the NPCA primary channel. The AP may issue a PHY-RXSTART.indication primitive for the PPDU that does not overlap with the primary channel or the NPCA primary channel. The AP may not issue a PHY-RXSTART.indication primitive for the PPDU that does not overlap with the primary channel or the NPCA primary channel. An AP may issue a PHY-RXSTART.indication primitive upon receiving the PPDU on the NPCA primary channel, the NPCA secondary 20 MHz channel, the NPCA secondary 40 MHz channel, or the NPCA secondary 80 MHz channel. An AP may assign a PPDU to a STA and issue a PHY-RXSTART.indication primitive upon receiving the PPDU assigned to the STA on the NPCA primary channel, the NPCA secondary 20 MHz channel, the NPCA secondary 40 MHz channel, or the NPCA secondary 80 MHz channel. In NPCA, an AP may issue a PHY-RXSTART.indication primitive upon receiving the PPDU on the NPCA primary channel, the NPCA secondary 20 MHz channel, the NPCA secondary 40 MHz channel, or the NPCA secondary 80 MHz channel for a PPDU requested by the AP. That is, in NPCA, an AP assigns a PPDU to a STA and issues a PHY-RXSTART.indication primitive upon receiving the PPDU on the NPCA primary channel, the NPCA secondary 20 MHz channel, the NPCA secondary 40 MHz channel, or the NPCA secondary 80 MHz channel. and receive the PPDU assigned to the STA on the NPCA primary channel, the NPCA secondary 20 MHz channel, the NPCA secondary 40 MHz channel, or the NPCA secondary 80 MHz channel. In NPCA, the AP issues a PHY-RXSTART.indication primitive for the PPDU that does not overlap with the primary channel. In NPCA, APs may use a primary channel or a channel that does not overlap with the NPCA primary channel. The PHY-RXSTART.indication primitive need not be issued for the PPDU that is not In NPCA, if the PPDU is requested by the AP, the AP may issue a PHY-RXSTART.indication primitive upon receiving the PPDU that does not overlap with the NPCA primary channel. In NPCA, if the PPDU is not requested by the AP, the AP may not issue a PHY-RXSTART.indication primitive for a PPDU that does not overlap with the NPCA primary channel. The primary channel and the NPCA primary channel may be different channels. The PHY may issue the PHY-RXSTART.indication primitive. The PHY of the STA may issue the PHY-RXSTART.indication primitive. The PHY of the AP may issue the PHY-RXSTART.indication primitive.

[0185] FIG. 14 illustrates an example of PPDU reception on an NPCA primary channel according to one aspect of the present embodiment. Channels 1401, 1402, 1403, 1404, 1405, 1406, 1407, and 1408 may each be 20 MHz channels. FIG. 14 may also illustrate STAs and / or APs operating at 160 MHz. Channel 1401 may be the primary channel. 1408 may be an NPCA primary channel. 1409 may be OBSS traffic. STA and / or AP may perform NPCA by 1409 while 1401 is busy. The STA and / or AP may receive and / or transmit and / or perform channel access on 1408 while 1401 is busy by 1409. The STA and / or AP may receive and / or transmit and / or perform channel access on one or more channels including 1408 while 1401 is busy by 1409. The STA and / or AP may receive and / or transmit and / or perform channel access on one or more channels including 1408 in the NPCA. and / or may perform channel access. 1410 may be a PPDU that overlaps with 1408. 1410 may be a PPDU that includes at least 1408. 1410 may be a PPDU transmitted using at least 1408. The AP may issue a PHY-RXSTART.indication primitive upon receiving 1410. The STA and / or AP may not issue a PHY-RXSTART.indication primitive upon receiving a PPDU that does not overlap with 1408. In other words, the STA and / or AP may not issue a PHY-RXSTART.indication primitive upon receiving a PPDU that was transmitted without using (including) 1408. Here, for example, the STA that performs the operation of FIG. 14 may be 204 in FIG. 2. For example, the AP performing the operation of Fig. 14 may be 202 in Fig. 2. For example, 1409 may be the transmission of 207 in Fig. 2. For example, 1410 may be the transmission of 204 in Fig. 2. For example, 1410 may be the transmission of 207 in Fig. 2.

[0186] FIG. 15 is a diagram illustrating an example of TB PPDU reception in the NPCA according to one aspect of the present embodiment. 1501, 1502, 1503, 1504, 1505, 1506, 1507, and 1508 may each be a 20 MHz channel. FIG. 15 may be a diagram of an STA and / or AP operating at 160 MHz. 1501 may be the primary channel. 1502 1503 and 1504 may constitute a secondary 40MHz channel. 1505, 1506, 1507, and 1508 may constitute a secondary 40MHz channel. 1508 is an NPCA primary channel. 1507 may be an NPCA secondary 20MHz channel. 1505 and 1506 may constitute an NPCA secondary 40MHz channel. 1509 may be OBSS traffic. STA and / or AP may use 1509 to notify 1501 that it is busy while 1501 is busy. NPCA may be performed. The STA and / or AP may perform NPCA while 1501 is busy by 1509. ,The STA and / or AP receive, and / or transmit, and / or, ,at 1508. The STA and / or AP may perform channel access. While busy, the STA and / or AP may receive on one or more channels, including 1508. , and / or transmission and / or channel access. The STA and / or the AP may receive, transmit, and / or access one or more channels including 1508 in the NPCA. 1510 may be a Trigger frame transmitted by the AP. Upon receiving 1501, the STA sends PHY-RXSTART.in The STA receives 1501, which overlaps with 1508. 1510 may be a Trigger frame sent by the AP to STA1, STA2, and STA3. 1511 may be a Trigger frame sent by the AP to STA1. 1511 may be the TB PPDU assigned to the NPCA primary channel (1508). STA1 may transmit 1511 as requested by the AP. 1512 may be a TB PPDU assigned by the AP to STA2. 1512 may be a 20 MHz transmission using the NPCA secondary 20 MHz channel (1507). STA2 may transmit 1512 as requested by the AP. 1513 may be a TB PPDU assigned by the AP to STA3. 1513 may be a 40 MHz transmission using the NPCA secondary 40 MHz channel (1505 and 1506). STA3 may transmit 1513 as requested by the AP. The AP may issue a PHY-RXSTART.indication primitive upon receiving 1511. The AP may issue a PHY-RXSTART.indication primitive upon receiving 1512. The AP may issue a PHY-RXSTART.indication primitive upon receiving 1513.

[0187] Unless the AP PHY receives a TB PPDU requested by the AP, the PHY may not issue the PHY-RXSTART.indication primitive for PPDUs that do not overlap with the primary channel and / or NPCA primary. For a TB PPDU requested by the AP, the PHY may issue the PHY-RXSTART.indication primitive for PPDUs received on the primary channel, secondary 20 MHz channel, secondary 40 MHz channel, secondary 80 MHz channel, NPCA primary channel, NPCA secondary 20 MHz channel, NPCA secondary 40 MHz channel, or NPCA secondary 80 MHz channel. The PHY may issue the PHY-RXSTART.indication primitive. The PHY may be the PHY (physical layer) of the STA. The PHY may be the PHY (physical layer) of the AP. The STA PHY may issue the PHY-RXSTART.indication primitive. The AP PHY may issue the PHY-RXSTART.indication primitive. The TB PPDU may be a HE TB PPDU. TB PPDU is , EHT TB PPDU. The TB PPDU may be a UHR TB PPDU.

[0188] While performing NPCA, the AP may not issue the PHY-RXSTART.indication primitive for PPDUs that do not overlap with the NPCA primary channel unless the AP's PHY receives a TB PPDU requested by the AP. While performing NPCA, the AP may issue the PHY-RXSTART.indication primitive for PPDUs received on the NPCA primary channel, NPCA secondary 20MHz channel, NPCA secondary 40MHz channel, or NPCA secondary 80MHz channel for a TB PPDU requested by the AP. While performing NPCA, the AP may request a TB PPDU from the STA. However, the PHY receives PPDUs other than the TB PPDU requested by the STA on the NPCA primary channel, NPCA secondary 20MHz channel, NPCA secondary 40MHz channel, and NPCA secondary 80MHz channel. In this case, the PHY-RXSTART.indication primitive does not need to be issued. The AP requests a TB PPDU from the STA while performing NPCA, and the PHY may issue the PHY-RXSTART.indication primitive for PPDUs other than the TB PPDU received from the STA on the NPCA primary channel, NPCA secondary 20MHz channel, NPCA secondary 40MHz channel, or NPCA secondary 80MHz channel. The PHY may issue a PHY-RXSTART.indication primitive. The PHY may be the PHY (physical layer) of the STA. The PHY may be the PHY (physical layer) of the AP. The PHY of the STA may issue a PHY-RXSTART.indication primitive. The PHY of the AP may issue a PHY-RXSTART.indication primitive. The TB PPDU may be an HE TB PPDU. The TB PPDU may be an EHT TB PPDU. The TB PPDU may be a UHR TB PPDU.

[0189] Unless the AP's PHY receives the requested PPDU from the AP, the PHY will continue to use the primary channel and / or or for PPDUs that do not overlap with the NPCA primary channel, PHY-RXEARLYSIG.indication and The PHY may not issue the PHY-RXSTART.indication primitive. The AP may issue both the PHY-RXEARLYSIG.indication primitive and the PHY-RXSTART.indication primitive for the TB PPDU that it has requested while performing NPCA. Unless a PPDU is received, the PHY will not use the primary channel and / or the NPCA primary channel. The PHY may not issue the PHY-RXEARLYSIG.indication and PHY-RXSTART.indication primitives for PPDUs that do not overlap with the primary channel and / or NPCA primary channel. The PHY may not issue the PHY-RXEARLYSIG.indication and PHY-RXSTART.indication primitives for PPDUs that do not overlap with the primary channel and / or NPCA primary channel. While the STA is performing NPCA, the PHY may not issue the PHY-RXEARLYSIG.indication and PHY-RXSTART.indication primitives for PPDUs that do not overlap with the primary channel and / or NPCA primary channel. The PHY may issue the PHY-RXSTART.indication primitive. The PHY may issue the PHY-RXSTART.indication primitive for PPDUs that do not overlap with the primary channel and / or NPCA primary channel. The PHY may be the PHY (physical layer) of the AP. The PHY of the STA may issue the PHY-RXSTART.indication primitive. The PHY of the AP may issue the PHY-RXSTART.indication primitive. The TB PPDU may be an HE TB PPDU. The TB PPDU may be an EHT TB PPDU. The TB PPDU may be a UHR TB PPDU.

[0190] When not performing NPCA, a STA may issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the primary channel. When not performing NPCA, a STA may not issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the primary channel. When not performing NPCA, a STA may not issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the NPCA primary channel. When not performing NPCA, a STA may not issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the NPCA primary channel. When not performing NPCA, a STA may not issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the primary channel but overlaps with the NPCA primary channel. When not performing NPCA, a STA may not issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the primary channel but overlaps with the NPCA primary channel. When not performing NPCA, a STA may not issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the primary channel but overlaps with the NPCA primary channel. When not performing NPCA, a STA may issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the primary channel and overlaps with the NPCA Primary channel.When not performing NPCA, a STA may issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the primary channel and does not overlap with the NPCA Primary channel.

[0191] When performing NPCA, a STA may issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the NPCA Primary channel. When performing NPCA, a STA may not issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the NPCA Primary channel. When performing NPCA, a STA may not issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the Primary channel. A STA may not issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the NPCA Primary channel. If a STA is performing NPCA, it does not need to issue the PHY-RXSTART.indication primitive if it receives a PPDU that does not overlap with the primary channel. When a STA receives a PPDU that does not overlap with the NPCA primary channel but overlaps with the primary channel, it may not issue the PHY-RXSTART.indication primitive. When a STA is performing NPCA, it may not issue the PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the NPCA primary channel but overlaps with the primary channel. When a STA is performing NPCA, it may issue the PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the NPCA primary channel but overlaps with the primary channel. When a STA is performing NPCA, it may issue the PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the NPCA primary channel but does not overlap with the primary channel.

[0192] When not performing NPCA, the AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the Primary channel. When not performing NPCA, the AP may not issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the Primary channel. When not performing NPCA, the AP may not issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the NPCA Primary channel. When not performing NPCA, the AP may not issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the NPCA Primary channel. An AP may not issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the primary channel but overlaps with the NPCA Primary channel when not performing NPCA. An AP may not issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the primary channel but overlaps with the NPCA Primary channel when not performing NPCA. An AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU that does not overlap with the primary channel but overlaps with the NPCA Primary channel when not performing NPCA. An AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the primary channel but does not overlap with the NPCA Primary channel when not performing NPCA. An AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the primary channel but does not overlap with the NPCA Primary channel when not performing NPCA. An AP may issue a PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the primary channel but does not overlap with the NPCA Primary channel when not performing NPCA. An AP may issue a PHY-RXSTART.indication primitive when it receives a TB requested by an AP when not performing NPCA. For a TB PPDU, the AP may issue a PHY-RXSTART.indication primitive upon receiving the TB PPDU on the primary channel, the secondary 20 MHz channel, the secondary 40 MHz channel, or the secondary 80 MHz channel.

[0193] When performing NPCA, the AP may issue a PHY-RXSTART.indication primitive if it receives a PPDU that overlaps with the NPCA Primary channel. When performing NPCA, the AP may not issue a PHY-RXSTART.indication primitive if it receives a PPDU that does not overlap with the NPCA Primary channel. When performing NPCA, the AP may not issue a PHY-RXSTART.indication primitive if it receives a PPDU that overlaps with the Primary channel. When performing NPCA, an AP may not issue a PHY-RXSTART.indication primitive if it receives a PPDU that does not overlap with the primary channel. When performing NPCA, an AP may not issue a PHY-RXSTART.indication primitive if it receives a PPDU that does not overlap with the NPCA primary channel but overlaps with the primary channel. When performing NPCA, an AP may not issue a PHY-RXSTART.indication primitive if it receives a PPDU that does not overlap with the NPCA primary channel but overlaps with the primary channel. When performing NPCA, an AP may not issue a PHY-RXSTART.indication primitive if it receives a PPDU that does not overlap with the NPCA primary channel but overlaps with the primary channel. The AP may issue the PHY-RXSTART.indication primitive when it receives a PPDU that overlaps with the NPCA primary channel and does not overlap with the primary channel when performing NPCA. When performing NPCA, the AP may issue the PHY-RXSTART.indication primitive when it receives a TB PPDU on the NPCA primary channel, the NPCA secondary 20 MHz channel, the NPCA secondary 40 MHz channel, or the NPCA secondary 80 MHz channel for TB PPDUs requested by the AP.

[0194] "While NPCA is being performed" may be a period of time during which channel access and / or reception and / or transmission occurs on one or more channels including at least the NPCA primary channel while the primary channel is busy with OBSS traffic. "When ... NPCA is being performed. "While NPCA is being performed" may be referred to as "in NPCA operation." "While not NPCA is being performed" may be a period of time during which channel access and / or reception and / or transmission occurs on one or more channels including at least the NPCA primary channel while the primary channel is busy with OBSS traffic. This may be a period during which the channel is accessed and / or received and / or transmitted on the channel. If NPCA is not performed, the channel is accessed and / or transmitted on one or more channels, including at least the primary channel. It may be a case where channel access and / or reception and / or transmission is performed on the channel. Figure 13 may be a case where NPCA is performed. Figure 14 may be a case where NPCA is performed. Figure 15 may be a case where NPCA is performed.

[0195] 16 is a diagram illustrating an example of a process of issuing a PHY-RXSTART.indication primitive according to one aspect of the present embodiment. In the NPCA, a STA or an AP issues a PHY-RXSTART.indication primitive that overlaps with the NPCA primary channel. The STA or AP receives a PPDU (S1601). The PHY (physical layer) of the STA or AP issues a PHY-RXSTART.indication primitive (S1602).

[0196] FIG. 17 is a diagram illustrating an example of a process of issuing a PHY-RXSTART.indication primitive for a TB PPDU according to an aspect of the present embodiment. In NPCA, the AP issues a PHY-RXSTART.indication primitive to a STA to request a TB PPDU. The AP receives the (requested) TB PPDU from the STA on the NPCA primary channel (S1701). The PHY (physical layer) of the AP issues a PHY-RXSTART.indication primitive (S1703). In NPCA, the AP requests a TB PPDU from the STA (S1701). The AP may receive a TB PPDU from the NPCA primary channel, and / or the NPCA secondary 20 MHz channel, and / or the NPCA secondary 40 MHz channel, and / or the NPCA secondary 80 MHz channel (S1702), and the PHY (physical layer) of the AP may issue a PHY-RXSTART.indication primitive (S1703).

[0197] As described above, in the embodiment of the present invention, the PHY (physical layer) of the STA and AP issues the PHY-RXSTART.indication primitive when receiving a PPDU on the NPCA primary channel, the NPCA secondary 20 MHz channel, the NPCA secondary 40 MHz channel, or the NPCA secondary 80 MHz channel. This invention allows the STA and AP to issue the PHY-RXSTART.indication primitive when receiving a PPDU in the NPCA.

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

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

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

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

[0202] 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 cause the terminal device to perform the operations and processes described in the above embodiments using the processor. The base station 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 base station device to perform the operations and processes described in the above embodiments.

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

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

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

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

[0207] 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. If the PPDU is a TB PPDU requested by the AP, the PPDU that overlaps with the NPCA primary channel is not preceded by a PHY-RXSTART.indication primitive. A base station device that issues the PHY-RXSTART.indication primitive.

2. The base station apparatus according to claim 1 , wherein the PPDU does not overlap with a primary channel.

3. The base station apparatus according to claim 1 , wherein, when NPCA is not performed, the PHY-RXSTART.indication primitive is issued for a PPDU that overlaps with the primary channel.

4. When NPCA is being performed, the TB PPDU requested by the AP is transmitted on the NPCA primary channel. The base station device issues the PHY-RXSTART.indication primitive in response to the received PPDU.

5. A terminal device comprising a processing unit that issues a PHY-RXSTART.indication primitive, and when performing NPCA, not issuing the PHY-RXSTART.indication primitive for a PPDU that does not overlap with an NPCA primary channel.

6. The terminal device according to claim 5 , wherein the PHY-RXSTART.indication primitive is issued for a PPDU that overlaps with the NPCA Primary channel.

7. A communication method for a base station device, comprising: issuing a PHY-RXSTART.indication primitive; and, when NPCA is being performed, issuing the PHY-RXSTART.indication primitive for a PPDU that overlaps with an NPCA primary channel unless the PPDU is a TB PPDU requested by an AP. Including communication methods.

Images